Bug#677626: ceph - Unwarranted restriction of architectures
On Fri, Jun 15, 2012 at 15:33:56 +0200, Bastian Blank wrote: Package: ceph Version: 0.47.2-1 Severity: serious The ceph upload in NEW tells: | * Limit archs to build on as leveldb dependency doesn't support all. The leveldb package is clearly not restricted to specific architectures, so this is not allowed. Unless this gets fixed we'll have to remove ceph from wheezy. Which means qemu and qemu-kvm need to drop their build-deps on ceph packages. They can always be re-added if/when leveldb/ceph are fixed. Cc:ing the qemu/qemu-kvm maintainers. Cheers, Julien signature.asc Description: Digital signature
Bug#677626: ceph - Unwarranted restriction of architectures
On Sat, Jun 30, 2012 at 18:23:07 +, Laszlo Boszormenyi (GCS) wrote: It was fixed before accepted from the NEW queue. Built on all architectures where leveldb is built[1], except ia64. Closing this bug now. It's not fixed as long as it's not built on *all* archs. Julien, may you ask inside Google what's the status of #677645 [2]? How would I do that? You know as much as I do. Cheers, Julien signature.asc Description: Digital signature
Bug#677626: ceph - Unwarranted restriction of architectures
On Sun, 2012-06-17 at 19:16 +, Laszlo Boszormenyi (GCS) wrote: On Fri, 2012-06-15 at 15:33 +0200, Bastian Blank wrote: The ceph upload in NEW tells: | * Limit archs to build on as leveldb dependency doesn't support all. The leveldb package is clearly not restricted to specific architectures, so this is not allowed. While I agree with this, I don't see the point how leveldb and ceph will migrate to testing. The same way they always have? The requirement is that the package is up to date _on the architectures on which it has previously built_. Failure to build on architectures on which the package has never built is irrelevant. In my opinion, leveldb should be limited to architectures that it builds on. Do the porting in the background and enable others when they are ready. If I upload ceph and it can't be built because of leveldb doesn't support that particular architecture, then the effect is similar. I just put a job on buildds that it won't even start. They're really not the same. With both packages set to arch:any, ceph will indeed not build on any architecture where leveldb isn't available - that's presumably already the case though. This doesn't put any load on the buildds, as ceph will be marked as BD-Uninstallable on those architectures and not be available for a buildd to pick up. The difference comes when a future upload of leveldb (or a fix in one of its dependencies, or the toolchain, or the phase of the moon) means that it manages to build on a new architecture. With your solution, this requires a new upload of ceph in order to add the new architecture; with the package as arch:any, ceph automagically gets a build attempt on the new architecture with no intervention from anyone as the buildd software will notice that leveldb is now available. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677626: ceph - Unwarranted restriction of architectures
On Tue, 2012-06-19 at 21:33 +0100, Adam D. Barratt wrote: On Sun, 2012-06-17 at 19:16 +, Laszlo Boszormenyi (GCS) wrote: On Fri, 2012-06-15 at 15:33 +0200, Bastian Blank wrote: The ceph upload in NEW tells: | * Limit archs to build on as leveldb dependency doesn't support all. The leveldb package is clearly not restricted to specific architectures, so this is not allowed. While I agree with this, I don't see the point how leveldb and ceph will migrate to testing. The same way they always have? The requirement is that the package is up to date _on the architectures on which it has previously built_. Failure to build on architectures on which the package has never built is irrelevant. (Having hit send a little too soon) Note that whether you use an explicit architecture list or any, if the new set of architectures on which ceph builds drops support for some architectures then you'll need to ask ftp-master to remove the old binaries from unstable before the package can migrate. Making the package arch:any doesn't introduce the obstacle to migration, the restriction to a particular set of architectures (either explicitly or implicitly due to using an unported build-dependency) does. I assume from your comment that you're expecting that an explicitly architecture-restricted ceph would be eligible for testing migration with no further intervention; that's not the case, as detailed above. In my opinion, leveldb should be limited to architectures that it builds on. Do the porting in the background and enable others when they are ready. If I upload ceph and it can't be built because of leveldb doesn't support that particular architecture, then the effect is similar. I just put a job on buildds that it won't even start. They're really not the same. With both packages set to arch:any, ceph will indeed not build on any architecture where leveldb isn't available - that's presumably already the case though. This doesn't put any load on the buildds, as ceph will be marked as BD-Uninstallable on those architectures and not be available for a buildd to pick up. The difference comes when a future upload of leveldb (or a fix in one of its dependencies, or the toolchain, or the phase of the moon) means that it manages to build on a new architecture. With your solution, this requires a new upload of ceph in order to add the new architecture; with the package as arch:any, ceph automagically gets a build attempt on the new architecture with no intervention from anyone as the buildd software will notice that leveldb is now available. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677626: ceph - Unwarranted restriction of architectures
On Sun, Jun 17, 2012 at 07:16:21PM +, Laszlo Boszormenyi (GCS) wrote: On Fri, 2012-06-15 at 15:33 +0200, Bastian Blank wrote: The ceph upload in NEW tells: | * Limit archs to build on as leveldb dependency doesn't support all. The leveldb package is clearly not restricted to specific architectures, so this is not allowed. While I agree with this, I don't see the point how leveldb and ceph will migrate to testing. Not sure what you want to tell me. In my opinion, leveldb should be limited to architectures that it builds on. Right now it is supposed to build on any arch. With #677645 in the way it does. Bastian -- Without freedom of choice there is no creativity. -- Kirk, The return of the Archons, stardate 3157.4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677626: ceph - Unwarranted restriction of architectures
Hello everybody, and sorry for the late reply. On Sun, Jun 17, 2012 at 9:16 PM, Laszlo Boszormenyi (GCS) g...@debian.hu wrote: In short, what's the leveldb plans for Wheezy? Will it build on all archs? I'm going to test leveldb on powerpc and then I'll report my results to upstream. Hence I cannot promise it will be ready in time for Wheezy, of course I'll upload a patch as soon as a fix becomes available. See you soon, -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer | quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677626: ceph - Unwarranted restriction of architectures
Hi Bastian, Alessio, On Fri, 2012-06-15 at 15:33 +0200, Bastian Blank wrote: The ceph upload in NEW tells: | * Limit archs to build on as leveldb dependency doesn't support all. The leveldb package is clearly not restricted to specific architectures, so this is not allowed. While I agree with this, I don't see the point how leveldb and ceph will migrate to testing. In my opinion, leveldb should be limited to architectures that it builds on. Do the porting in the background and enable others when they are ready. If I upload ceph and it can't be built because of leveldb doesn't support that particular architecture, then the effect is similar. I just put a job on buildds that it won't even start. In short, what's the leveldb plans for Wheezy? Will it build on all archs? Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677626: ceph - Unwarranted restriction of architectures
Package: ceph Version: 0.47.2-1 Severity: serious The ceph upload in NEW tells: | * Limit archs to build on as leveldb dependency doesn't support all. The leveldb package is clearly not restricted to specific architectures, so this is not allowed. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
