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

Re: Some 'required' packages broken for powerpcspe port



On Jul 01, 2011, at 16:17, David Kuehling wrote:
> "Kyle" == Kyle Moffett <Kyle.D.Moffett@boeing.com> writes:
>>> 1. Nowadays some required packages depend on the metapackage
>>> 'multiarch-support' (e.g. 'libselinux1').  However
>>> 'multiarch-support' is only provided by newer eglibc packages, not by
>>> the eglibc package currently found in the powerpcspe archive (in
>>> suite 'unreleased')
>> 
>> That shouldn't be terribly hard to fix.  Really what needs to happen
>> is for someone with an existing sbuild chroot to figure out which
>> patches for those core dependencies are still missing from
>> upstream/Debian and get them merged.
>> 
>> It's on my To-Do list as soon as I finish porting to this X86
>> hardware.
> 
> Currently I have 1-2 days/week for work related to powerpcspe.  I could
> either use snapshot.debian.org to find the latest working state and
> stick to that, or try to forward-port your eglibc patches to the latest
> 'sid' version, maybe filing a few bug-reports for inclusion of the
> patches on the way.  Don't want to interfere with your TODO list (nor
> with Sebastian's), so feel free to tell me to keep my hands off libc :)

I would try to forward-port the eglibc patches from the "unreleased" repo
to the latest sid version and file new bugs (or update existing ones and
pester the maintainers).

My TODO list right now is completely out-of-date and I have to start over
with it as soon as I get the time to work on it, so feel free to work on
whatever you would like.

One of the first things I will need to do is upgrade my ancient buildds
and get them going again, so I will be more than happy with any of that
you manage to fix before I have to worry about :-D.

>>> 2. Some packages depend on metapackage perlapi-5.10.1
>>> (e.g. libtext-iconv-perl).  But only perlapi-5.12.3 is provided by
>>> package 'perl-base'.  The mistake is in the dependencies of packages
>>> like 'libtext-iconv-perl'.  Looking here:
>>> 
>>> http://packages.debian.org/sid/libtext-iconv-perl
>>> 
>>> I see that although all architectures have a package
>>> libtext-iconv-perl:1.7-2, the perlapi-* packages they depend on
>>> differ.  On arch 'powerpcspe' the dependency is on perlapi-5.10.1,
>>> while for 'powerpc' it's perlapi-5.12.3.  Maybe the dependency is
>>> automatically determined at built-time and a simple rebuild is going
>>> to fix it?
>> 
>> Yeah, that's a classic Debian package archive "transition".  The
>> version of the Perl API that a given binary Perl module depends on is
>> based on what version of Perl was installed when the package was
>> built.
>> 
>> Since our buildds have not really been actively maintained, we have
>> not been keeping track of those transitions and proactively upgrading
>> the packages like Perl to the newer versions.
> 
> So that means the problem is as good as fixed?

I wouldn't say it's "fixed".  What needs to happen is the buildds (the 
only one of which is running right now is Sebastian's) need to get
upgraded with the new Perl, then all of the affected packages need to
be binNMUed by somebody with access to wanna-build on debian-ports.org.

Each of the currently in-progress transitions has a status page here:
  http://release.debian.org/transitions/
  http://www.debian-ports.org/~iwamatsu/transition/

If you're interested in working on it, you can probably ask the
debian-ports.org admins (probably Aurelien Jarno, CCed) to give you
wanna-build access so you can schedule those binNMUs yourself.
Ideally you would just set up a buildd yourself and that way you could
also keep an eye on the binNMUs that you are scheduling.

Keep in mind that the wanna-build software is still a little raw from
a UI perspective and not very well documented at all.

Thanks again and good luck!

Cheers,
Kyle Moffett


Reply to: