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

Re: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8



On 2012-07-31 11:02, Niels Thykier wrote:
> On 2012-07-18 13:34, Goswin von Brederlow wrote:
>> [...]
>>
>> There are still 2 problems remaining: lestiff2 (patch in BTS) and cyrus-sasl
>> (needs a sourcefull upload to fix binNMU / multiarch problem).
>>
> 
> [...]
> 
> It is my understanding that lesstif2 is the last M-A conversion needed
> for ia32-libs.  Assuming the changes to lesstif2 and mtink are
> reasonable, cyrus-sasl just needs a "no-change" upload and ia32-libs is
> good to go.
> 

mtink is in testing, cyrus-sasl2 is fixed in sid with an unblock.
lesstif2 does not have an unblock, but assuming it got one, it could
migrate with the next Britney run.

>> [...]
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677762
>>
>> The number of issues have gone down but not far enough yet. Most
>> critical and trivial there is:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650777
>>
>> That one prevents ia32-libs-gtk to be installable with a dependency on
>> libgnomecanvas and 3rd party binaries still depend on that.
>>
>> [...]
> 
> 
> It seems like most of those bugs are libraries needing converted to M-A
> (i.e. usr/lib -> usr/lib/$MADIR) and #650777 is the "exception".
> 
> What do we "lose" if only the "trivial" bugs are fixed?  By trivial I
> mean only patches that add "Multi-Arch: $val" fields like #650777 (so no
> moving of libraries from usr/lib to usr/lib/$MADIR).
> 
> ~Niels
> 
>  [...]

I would still like to get an idea of what needs the last packages
unfixed packages.  Having reviewed some of the bugs, I realized that
some of them have no patches, liborbit2 seems to invovle plugins that
will most likely entangle "unrelated" packages, at least libbonobo has
an unanswered "interesting question"...

~Niels



Reply to: