Bug#676786: k3d: FTBFS: build-depends on libtiff5-dev | libtiff4-dev
2012/6/10 Julien Cristau : > On Sat, Jun 9, 2012 at 17:12:30 +0100, Manuel A. Fernandez Montecelo wrote: > >> 2012/6/9 Julien Cristau : >> > Buildds ignore | in build-dependencies. Please use the unversioned >> > libtiff-dev, it'll point to the right version. Using libtiff5-dev in >> > wheezy is discouraged, we want everything to move to symbol-versioned >> > libtiff4 first. >> >> Should I also do this for other packages that I "converted" to v5? > > Yes please. I'll do that then for k3d and other packages. Thanks both, for the report and the advice. Cheers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676786: k3d: FTBFS: build-depends on libtiff5-dev | libtiff4-dev
On Sat, Jun 9, 2012 at 17:12:30 +0100, Manuel A. Fernandez Montecelo wrote: > 2012/6/9 Julien Cristau : > > Buildds ignore | in build-dependencies. Please use the unversioned > > libtiff-dev, it'll point to the right version. Using libtiff5-dev in > > wheezy is discouraged, we want everything to move to symbol-versioned > > libtiff4 first. > > Should I also do this for other packages that I "converted" to v5? Yes please. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676786: k3d: FTBFS: build-depends on libtiff5-dev | libtiff4-dev
Hi, WRT Aurelien's message and the IRC log, a minor correction to your conversation: my package depends on (libtiff5-dev | libtiff4-dev), not (libtiff5-dev | libtiff-dev). libtiff-dev is *only* provided by libtiff4-dev [1], libtiff4 is in oldlibs [2] as I said -- that's why I wanted to "upgrade" to v5. There are ongoing (or recently finished) transitions with libpng and others, so I figured that this was another imminent one before the freeze. [1] $ aptitude show libtiff-dev No current or candidate version found for libtiff-dev Package: libtiff-dev State: not a real package Provided by: libtiff4-dev [2] $ apt-cache show libtiff4 | grep Section Section: oldlibs (Note: I only import from a single mirror and unstable, no funky stuff mixing repositories or apt-pinning). 2012/6/9 Julien Cristau : > Buildds ignore | in build-dependencies. Please use the unversioned > libtiff-dev, it'll point to the right version. Using libtiff5-dev in > wheezy is discouraged, we want everything to move to symbol-versioned > libtiff4 first. Should I also do this for other packages that I "converted" to v5? They don't seem to have trouble using v5. > libtiff4 being in oldlibs sounds like a bug to me. Who should point that to the maintainer? The release team? If I'm not mistaken, you're part of that team (Julien). Cheers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676786: k3d: FTBFS: build-depends on libtiff5-dev | libtiff4-dev
On Sat, Jun 9, 2012 at 12:42:28 +0100, Manuel A. Fernandez Montecelo wrote: > Hello Aurelien, > > 2012/6/9 Aurelien Jarno : > > Package: k3d > > Version: 0.8.0.2-17 > > Severity: serious > > Justification: fails to build from source (but built successfully in the > > past) > > > > k3d build depends on libtiff5-dev | libtiff4-dev, which conflicts with > > some of the depends on libmagick++-dev, rendering the package > > unbuildable. > > > > It should build-depends on libtiff-dev instead. > > Is there any document explaining why this problem happens? > Buildds ignore | in build-dependencies. Please use the unversioned libtiff-dev, it'll point to the right version. Using libtiff5-dev in wheezy is discouraged, we want everything to move to symbol-versioned libtiff4 first. libtiff4 being in oldlibs sounds like a bug to me. Cheers, Julien signature.asc Description: Digital signature
Bug#676786: k3d: FTBFS: build-depends on libtiff5-dev | libtiff4-dev
On Sat, Jun 09, 2012 at 12:42:28PM +0100, Manuel A. Fernandez Montecelo wrote: > Hello Aurelien, > > 2012/6/9 Aurelien Jarno : > > Package: k3d > > Version: 0.8.0.2-17 > > Severity: serious > > Justification: fails to build from source (but built successfully in the > > past) > > > > k3d build depends on libtiff5-dev | libtiff4-dev, which conflicts with > > some of the depends on libmagick++-dev, rendering the package > > unbuildable. > > > > It should build-depends on libtiff-dev instead. > > Is there any document explaining why this problem happens? > > I wanted to use libtiff5-dev because libtiff4-dev is in "oldlibs" now, so I > didn't want to depend on a deprecated library just to have to modify it later. > So I changed that to lt5-d alone, but with lt5-d it didn't build in my > pbuilder > because of the libmagic++-dev thing. > > Then I figured out that if I put both, it will use lt4-d while required by > libmagic++-dev, and lt5-d afterwards. And because libtiff-dev is only > provided > by v4: > > $ aptitude show libtiff-dev > No current or candidate version found for libtiff-dev > Package: libtiff-dev > State: not a real package > Provided by: libtiff4-dev > > > So this built fine in my pbuilder and the buildd for i386, I was wondering why > the others didn't process it. > > So, is there anything intrinsically wrong with my Build-Depends? > > Other than that, I think that libtiff5-dev should "Povides: libtiff-dev" as > well, so there would be a clear migration path without these problems. > I don't know all the details, it was the advised solution by the release team: 12:04 < aurel32> someone following the libtiff transition? 12:05 < aurel32> some packages are in a build -> give-back loop, due to indirect build-depends to both libtiff-dev and libtiff5-dev 12:05 < aurel32> and they conflict 12:05 < aurel32> is it correct that packages should use libtiff5-dev? 12:05 < aurel32> (imagemagick in that case) 12:15 < jcristau> aurel32: no 12:15 < aurel32> jcristau: ok, so what is the correct solution here? 12:16 < jcristau> have people stop using libtiff5 12:16 < aurel32> ok, so k3d should build-depends on libtiff-dev instead of libtiff5-dev? 12:16 < jcristau> yes -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676786: k3d: FTBFS: build-depends on libtiff5-dev | libtiff4-dev
Hello Aurelien, 2012/6/9 Aurelien Jarno : > Package: k3d > Version: 0.8.0.2-17 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > k3d build depends on libtiff5-dev | libtiff4-dev, which conflicts with > some of the depends on libmagick++-dev, rendering the package > unbuildable. > > It should build-depends on libtiff-dev instead. Is there any document explaining why this problem happens? I wanted to use libtiff5-dev because libtiff4-dev is in "oldlibs" now, so I didn't want to depend on a deprecated library just to have to modify it later. So I changed that to lt5-d alone, but with lt5-d it didn't build in my pbuilder because of the libmagic++-dev thing. Then I figured out that if I put both, it will use lt4-d while required by libmagic++-dev, and lt5-d afterwards. And because libtiff-dev is only provided by v4: $ aptitude show libtiff-dev No current or candidate version found for libtiff-dev Package: libtiff-dev State: not a real package Provided by: libtiff4-dev So this built fine in my pbuilder and the buildd for i386, I was wondering why the others didn't process it. So, is there anything intrinsically wrong with my Build-Depends? Other than that, I think that libtiff5-dev should "Povides: libtiff-dev" as well, so there would be a clear migration path without these problems. Cheers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676786: k3d: FTBFS: build-depends on libtiff5-dev | libtiff4-dev
Package: k3d Version: 0.8.0.2-17 Severity: serious Justification: fails to build from source (but built successfully in the past) k3d build depends on libtiff5-dev | libtiff4-dev, which conflicts with some of the depends on libmagick++-dev, rendering the package unbuildable. It should build-depends on libtiff-dev instead. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
