Opened 11 years ago

Closed 8 years ago

#42 closed defect (fixed)

cross architecture VEs

Reported by: Bryan Gartner Owned by: Bruno Cornec
Priority: major Milestone: 0.12.1
Component: pb Version: 0.9.6
Keywords: Cc:

Description

It seems there is an issue when using VE (like for an i386 VE on an x86_64 platform), that the uname -m returns that for the running kernel, which yields issues for PB and it's auto-detection and naming routines.

Change History (11)

comment:1 Changed 11 years ago by Bruno Cornec

Owner: set to Bruno Cornec
Status: newassigned

comment:2 Changed 11 years ago by Bruno Cornec

This seems to be a rinse error, where after extracting everything with the i386 arch correctly, then rinse calls yum, but yum updates with x86_64 packages :-(

comment:3 Changed 11 years ago by Bruno Cornec

Milestone: 0.9.70.9.8

comment:4 Changed 10 years ago by Bruno Cornec

Milestone: 0.9.90.9.10

Needs to be checked with rpmbootstrap

comment:5 Changed 9 years ago by Bruno Cornec

Milestone: 0.9.100.9.11

This problem is also happening with rpmbootstrap. I'll work on a fix for this case, at least for this combination.

comment:6 Changed 9 years ago by Bruno Cornec

An approach would be to force the nature of the distribution we are working with in some cases where it could be useful (LSB build in a non detected LSB env, or windwos build in a Linux VM, or change of arch like here).

The issue is now when to force it, and still benefiting from the automagic detection, which is so useful.

comment:7 Changed 9 years ago by Bruno Cornec

Milestone: 0.10.10.10.2

comment:8 Changed 9 years ago by Bruno Cornec

Milestone: 0.11.30.11.4

comment:9 Changed 8 years ago by Bruno Cornec

Milestone: 0.12.10.12.2

comment:10 Changed 8 years ago by Bruno Cornec

Milestone: 0.12.20.12.1

The recent addition of setarch usage in pb code may help solving that for 0.12.1

comment:11 Changed 8 years ago by Bruno Cornec

Resolution: fixed
Status: assignedclosed

This is now solved in the beta of 0.12.1 thanks to Eric Andersson's efforts.

Note: See TracTickets for help on using tickets.