3 Jun
2014
3 Jun
'14
8:34 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Timothy Pearson wrote:
Now that we're on this topic. Does Trinity also really need its own
python-sip (and python-sip-dbg) packages?
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1012
Thanks,
Julius
Dreding up an ancient thread here since I got bitten by this bug two years
later...
It seems that there was a time when the official Ubuntu Precise multiarch
buildroots were broken, and the only symptom was multiarch failures such
as this one. A simple binary rebuild against the new buildroot seems to
have resolved the problem on my end:
https://quickbuild.pearsoncomputing.net/~trinity/+archive/trinity-nightly-b…
Tim
On
Tuesday 18 of September 2012 17:23:19 Timothy Pearson wrote:
The proper solution is to remove the broken libogg package from the
build-dependencies repository. I still have not completed a full build
test with libogg-dev-la removed, so I don't know if this is feasible
yet. > Dne út 18. zářà 2012 Slávek Banko
napsal(a):
> I can confirm that in the Packages downloaded from the apt sources
from
> PPA really missing information: Multi-Arch: same. Although in
> packages
> this information is provided.
This would seem to be a Launchpad bug; not sure if it has been fixed
(or
even reported!) upstream.
> Note: I noticed that for R14 is dependency libogg-dev-la replaced to
> libogg-dev. Tim, please, it caused some complications? It can also be
> used for 3.5.13.1?
I have not yet completed an R14 rebuild set with the dependency
changed;
I
still expect some packages to fail and require patching.
please, what tool is used by Launchpad to generate apt sources
informations?
It would be possible to update only this tool?
Slavek -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlOOMW4ACgkQLaxZSoRZrGFIKADgqvVRXOkGRC7uu8Xw1TsE69s7
4Jnca+bPlFPuxgDghfTnacsvFjWoMydPIAdd3T8wMhNQ5v5KvHsc1A==
=AwgP
-----END PGP SIGNATURE-----