trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2014

Re: [trinity-devel] compiz-fusion-plugins-*-trinity FTBFS patches (Jessie)

From: "Timothy Pearson" <kb9vqf@...>
Date: Fri, 12 Dec 2014 00:31:10 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> On Wednesday 10 of December 2014 05:00:20 Timothy Pearson wrote:
>> > On 2014/12/09 01:27 PM, Slávek Banko wrote:
>> >> On Tuesday 09 of December 2014 04:46:34 Michele Calgaro wrote:
>> >>> Tim, Slavek,
>> >>> over the weekend I did a full TDE rebuild in Jessie.
>> >>> The only two packages to fail were
>> compiz-fusion-plugins-main-trinity
>> >>> and
>> >>> compiz-fusion-plugins-extra-trinity, due to a missing depencency for
>> >>> libjpeg62-dev.
>> >>> The attached 'control' files fix the problem for both of them. Just
>> >>> rename
>> >>> the files back to 'control'.
>> >>>
>> >>> Cheers
>> >>>     Michele
>> >>
>> >> I believe that it is better to use a general dependence libjpeg-dev.
>> >> What do you think?
>> >
>> > That's probably better. Both libjpeg62-dev and libjpeg62-turbo-dev
>> > provides libjpeg-dev. I didn't try building using only a dependency on
>> > libjpeg-dev, but if there is no FTBFS in any distro, I would go for
>> it.
>> >
>> > Cheers
>> >    Michele
>>
>> Slavek, do you want to handle this by building on your PPA and I'll copy
>> to the main archive once the builds are complete?
>>
>> For R14.0.1 I will look into moving some of these older -deps packages
>> into the main GIT repositories.
>>
>> Tim
>>
>
> For a moment, all updated packages will be ready to copy:
> https://quickbuild.pearsoncomputing.net/~slavek-banko/+archive/ubuntu/deps-r14/+copy-packages?field.name_filter=compiz-fusion-plugins&field.include_binaries=COPY_BINARIES&batch=50

Thanks; copied.

> Here I would saw the question, what packages are useful and what packages
> we
> really want to maintain. For example, for such Compiz I'd rather doubted
> if
> we want it.

Not sure; if it still compiles why not?

> Some dependencies I consider to be temporary - such as lcms1, libept,
> libapt-front.

Correct.  These should not be included in GIT.

> Some dependencies are definite candidates for inclusion into the GIT - for
> example libr.

Correct again.  The fact that libr was not already in GIT was actually a
fairly serious oversight on my part; this will be fixed for our next SRU.

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

iFYEARELAAYFAlSKi60ACgkQLaxZSoRZrGF+fwDeJpxe7ozKOV3zYhGl1Wz5atjO
kr+UKryfqvankADgl1BRRyWH7ELEB9fhJAViY238kdI6UgTtZYHmEA==
=Qmmj
-----END PGP SIGNATURE-----