[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What is the status of multiarch?



On Wed, 27 Jun 2012 16:36:34 +0200, Claudius Hubig wrote:

> Hello Camaleón,
> 
> Camaleón <noelamac@gmail.com> wrote:
>> On Tue, 26 Jun 2012 23:20:05 +0200, Claudius Hubig wrote:
>> > It works quite nicely over here on a testing/sid system with the
>                                                  ^^^
> 
>> In the Spanish mailing list, a user reported a few days ago that he
>> completely messed up his full wheezy system when he tried to install
>> Wine
>                                 ^^^^^^
>> in his 64-bits installation.
> 
> I would assume that it is currently rather difficult to have a pure
> wheezy system with Multi-Arch, since some packages may still be trapped
> in unstable. For example, the multiarchified version of wine-bin only
> migrated to testing on 21 June.

Yes, and the problem started when he was going to upgrade his current 
working version of wine which I think it came from a native 64 bits 
compilation. After the wine migration to multiarch, it seems the package 
upgrade went finally fine but he experienced problems with package 
managers (apt and aptitude) after the update.

I lack the additional data that should be useful (well, "needed") to 
understand what it happened to him, that's why I suggested he goes to the 
BTS to analyze in deep the problem with the devs. Wheezy is going to be 
freezed in a couple of days and this multiarch problem scares me... a 
bit :-)
 
>> To be sincere, I'm a bit reluctant about the multiarch system. I would
>> prefer playing with it on virtual/testing machines and not yet over
>> production systems.
> 
> Neither wheezy nor sid systems are supposed to be production system and
> may break at any time.

Sure, I know, but by "production systems" I can also think in laptop 
computers or spare/secondary systems you run every day that, while not 
being essential for your daily work, these kind of problems are always a 
headache and something that needs to be fixed.

Greetings,

-- 
Camaleón


Reply to: