Bug#739416: transition: ruby1.8 removal
On 2014-03-01 06:06, Antonio Terceiro wrote: [...] This is now fixed, it should be safe to remove ruby1.8 now. 888- [...] $ dak rm -s testing -Rn ruby1.8 [...] Checking reverse dependencies... # Broken Depends: dns323-firmware-tools: dns323-firmware-tools libfilesystem-ruby: libfilesystem-ruby1.8 ruby-bdb: ruby-bdb ruby-nora: ruby-nora # Broken Build-Depends: libfilesystem-ruby: ruby1.8 ruby1.8-dev ruby-nora: ruby1.8 ruby1.8-dev xdotool: ruby1.8 Dependency problem found. 888- As mentioned on IRC; removing dns323-firmware-tools breaks d-i. Also, xdotool is just a successful armhf build away from disappearing from the list. For the record, you can ask dak to remove more than one package at the time: $ dak rm -nR -s testing ruby1.8 dns323-firmware-tools \ libfilesystem-ruby ruby-bdb ruby-nora -- Checking reverse dependencies... # Broken Build-Depends: debian-installer: dns323-firmware-tools xdotool: ruby1.8 Dependency problem found. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5311d812.7020...@thykier.net
Bug#739416: transition: ruby1.8 removal
On Tue, Feb 18, 2014 at 07:56:57PM -0500, James McCoy wrote: On Tue, Feb 18, 2014 at 08:29:35PM +0100, Julien Cristau wrote: Removing subversion doesn't seem reasonable. The sid version might be fixed (I haven't checked), but it FTBFS. So that'll need to be taken care of first. One of the FTBFS appears to be a transient issue. A gb would likely fix it, but the others are related to #735446. Upstream's next release (due this week) fix that. I've been monitoring the release process, so I should be able to get it uploaded to Debian ASAP once it's officially released. The only potential complication would be if the libdb5.1-dev package disappears in the mean time as Ondřej intends[0]. I haven't finished the bdb 5.3 work as I wanted to touch base with Peter on it. 0: 139230.17282.82981781.6e443...@webmail.messagingengine.com If needed, I could look at backporting the upstream commits to fix the FTBFS, but I'd prefer to put that effort into ensuring I can get the next 1.8.x uploaded when it's out. This is now fixed, it should be safe to remove ruby1.8 now. 888- $ cat $(which dak) #!/bin/sh ssh mirror.ftp-master.debian.org dak $@ $ dak rm -s testing -Rn ruby1.8 Will remove the following packages from testing: libruby1.8 | 1.8.7.358-10 | amd64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc libruby1.8-dbg | 1.8.7.358-10 | amd64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc libtcltk-ruby1.8 | 1.8.7.358-10 | amd64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc ri1.8 | 1.8.7.358-10 | all ruby1.8 | 1.8.7.358-10 | source, amd64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc ruby1.8-dev | 1.8.7.358-10 | amd64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc ruby1.8-examples | 1.8.7.358-10 | all ruby1.8-full | 1.8.7.358-10 | all Maintainer: akira yamada ak...@debian.org --- Reason --- -- Checking reverse dependencies... # Broken Depends: dns323-firmware-tools: dns323-firmware-tools libfilesystem-ruby: libfilesystem-ruby1.8 ruby-bdb: ruby-bdb ruby-nora: ruby-nora # Broken Build-Depends: libfilesystem-ruby: ruby1.8 ruby1.8-dev ruby-nora: ruby1.8 ruby1.8-dev xdotool: ruby1.8 Dependency problem found. 888- -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#739416: transition: ruby1.8 removal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear release team, The Ruby team is working to be able to not ship ruby1.8 with Jessie for quite a while. This is being tracked since DebConf13 at https://release.debian.org/transitions/html/ruby1.8-removal.html We underwent a huge amount of effort to make sure everything that was relevant was fixed, and at this point -- ignoring packages not in testing and ruby1.8 itself -- we have only 6 packages in bad state, which can always be fixed and get back to testing. So I would like to remove ruby1.8 from testing now. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#739416: transition: ruby1.8 removal
On Tue, Feb 18, 2014 at 10:04:38 -0300, Antonio Terceiro wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear release team, The Ruby team is working to be able to not ship ruby1.8 with Jessie for quite a while. This is being tracked since DebConf13 at https://release.debian.org/transitions/html/ruby1.8-removal.html We underwent a huge amount of effort to make sure everything that was relevant was fixed, and at this point -- ignoring packages not in testing and ruby1.8 itself -- we have only 6 packages in bad state, which can always be fixed and get back to testing. So I would like to remove ruby1.8 from testing now. Removing subversion doesn't seem reasonable. The sid version might be fixed (I haven't checked), but it FTBFS. So that'll need to be taken care of first. Cheers, Julien signature.asc Description: Digital signature
Bug#739416: transition: ruby1.8 removal
On Tue, Feb 18, 2014 at 08:29:35PM +0100, Julien Cristau wrote: Removing subversion doesn't seem reasonable. The sid version might be fixed (I haven't checked), but it FTBFS. So that'll need to be taken care of first. One of the FTBFS appears to be a transient issue. A gb would likely fix it, but the others are related to #735446. Upstream's next release (due this week) fix that. I've been monitoring the release process, so I should be able to get it uploaded to Debian ASAP once it's officially released. The only potential complication would be if the libdb5.1-dev package disappears in the mean time as Ondřej intends[0]. I haven't finished the bdb 5.3 work as I wanted to touch base with Peter on it. 0: 139230.17282.82981781.6e443...@webmail.messagingengine.com If needed, I could look at backporting the upstream commits to fix the FTBFS, but I'd prefer to put that effort into ensuring I can get the next 1.8.x uploaded when it's out. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org signature.asc Description: Digital signature
