> On Tuesday 18 of September 2012 17:23:19 Timothy Pearson wrote: >> > Dne út 18. záÅà 2012 Slávek Banko napsal(a): >> >> Tim, >> >> >> >> I tried to find some information about the problem with the >> concurrent >> >> installation libogg:amd64 and libogg:i386. And I find a little >> mystery. >> >> When I add a apt source nighlty-build-deps, this library is in the >> >> conflict when I try to install both in the aptitude. But if I >> download >> >> these packages and install both packages manually using dpkg, so the >> >> conflict does not occur. As the information about the conflict was >> >> somewhere in the information for apt. >> >> >> >> This would confirm the fact that when I install a library from my >> local >> >> apt source managed by reprepro, so the conflict does not occur. >> >> >> >> What could be wrong in apt source managed by Launchpad? >> >> Within the package clearly not the problem. >> >> >> >> Slavek >> > >> > 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. >> >> Tim >> >> > > Tim, > > please, what tool is used by Launchpad to generate apt sources > informations? > It would be possible to update only this tool? > > Slavek 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. Tim