trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: October 2014

Re: [trinity-devel] Divided libtool × libtool-bin

From: "Timothy Pearson" <kb9vqf@...>
Date: Fri, 31 Oct 2014 22:36:24 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> On 11/01/2014 12:04 PM, Michele Calgaro wrote:
>> On 11/01/2014 08:58 AM, Timothy Pearson wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA224
>>>
>>>> Hi all,
>>>>
>>>> we have another unwelcome message:
>>>>
>>>> libtool (2.4.2-1.11) unstable; urgency=medium
>>>>
>>>>    * Non-maintainer upload.
>>>>    * Drop libtool's dependency on libtool-bin.
>>>>    * Add libtool-bin dependency on libtool.
>>>>    * Make libtool Multi-Arch: foreign. Closes: #682045.
>>>>    * Bump standards version to 3.9.6.
>>>>
>>>>   -- Matthias Klose <doko@.........>  Tue, 14 Oct 2014 19:21:11 +0200
>>>>
>>>>
>>>> This means that the packages that need to building libtool will need
>>>> to
>>>> have a
>>>> set to variant dependency: "libtool-bin | libtool". I suggest to wait
>>>> for
>>>> a
>>>> change in tde-packaging before we know what all packages will be
>>>> affected.
>>>> Now I ran into this problem with pytdeextensions and bibletime. We
>>>> will
>>>> see
>>>> what will follow. We'll see whether it will be appropriate to wait for
>>>> the
>>>> change after RC1.
>>>>
>>>> --
>>>> Slávek
>>>
>>> Thanks for the heads up.  RC1 will *not* support Debian Jessie due to
>>> this
>>> change, but we will try to make R14 support Debian Jessie as of its
>>> release.
>>>
>>> This is incidentally why I don't like tracking unstable distros.  I
>>> know
>>> many users want to use Jessie (due to the age of the packages in
>>> Wheezy)
>>> but it's constantly being broken and we simply don't have the finances
>>> to
>>> rebuild the packages over and over and over again. :-(
>>>
>>> As an aside, please refrain from uploading any new packages to
>>> QuickBuild
>>> at this time.  After the RC1 builds are complete I will be taking it
>>> offline for long-overdue scheduled maintenance lasting one or two days.
>>>
>>> Tim
>>
>> I ran in the exact same problem during last night partial rebuild
>> (everything without the "applications" part).
>> Most of packages build anyway, so we can say that even though RC1 does
>> not support Jessie 100%, we are probably not far
>> away from there. Today I will run the remaining part, so by tomorrow I
>> should be able to say exactly how many packages
>> FTBFS due to the missing libtool (at the moment I found pytdeextensions,
>> haven't rebuilt bibletime yet).
>> IMO, if we end up with only two packages being the problem, we could
>> also consider to fix them for RC1, provided that
>> this does not trigger a "cascade rebuild" of several other packages on
>> the build farm.
>>
>> Cheers
>>    Michele
>>
>
> By the way, I forgot to say that Jessie will be frozen on Nov. 5, so after
> that it should be much more stable.
> Cheers
>    Michele

Good!  I appreciate the info.

Regarding rebuilds, if it's only a few packages affected we might be able
to squeeze them into RC1.  Bear in mind however that the build system will
be going down for a long-overdue maintenance overhaul shortly, so the
short-term focus should probably be on releasing and testing RC1 instead
of making it work 100% on Jessie.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iFYEARELAAYFAlRUVTgACgkQLaxZSoRZrGHW0gDeM3AAQD0Iz0EiDK4SMsRTtz+8
B99cNIKXpmS25ADghupPg3p2c1F80lRBzrfmnGtCKiF/X9qoqdlPEQ==
=p2NC
-----END PGP SIGNATURE-----