Re: Scheduling 9.2
On Sun, Aug 27, 2017 at 04:48:14PM +0100, Jonathan Wiltshire wrote: >Hi, > >I'm working on dates for 9.2; by a two month cycle we're aiming for around >23rd September. How about one of: > >23rd/24th September >30th Septmber/1st October I'm out in San Francisco for the week ib between them. I can't do the first weekend, but might be able to do the second while jetlagged. Another weekend would be preferred, though >After discussion with Adam and Steve, we felt it made sense to work on 2 >months for stable and 4 months for oldstable; that way there isn't a month >3 to try and fit in betweens. So every other stable update will also be an >oldstable. WFM. -- Steve McIntyre, Cambridge, UK.st...@einval.com Who needs computer imagery when you've got Brian Blessed?
Please dak copy-installer 20170828, please force it into testing
Hi, FTPmasters, please sync the installer from sid to testing: dak copy-installer 20170828 (The mips64el build is missing because of gcc-7 fun: #873465) Release team, please force it into testing. KiBi. signature.asc Description: Digital signature
Re: Bug#873481: jessie-pu: package bind9/9.9.5.dfsg-9+deb8u13.1
Hi Adam, thanks for the quick response. On Mon, Aug 28, 2017, at 11:44, Adam D. Barratt wrote: > Control: tags -1 + confirmed d-i > > On Mon, 2017-08-28 at 11:03 +0200, Ondřej Surý wrote: > > this is the jessie counterpart of bind9 update to KSK-2017. > > > > No other change has been done to the package. > > Nonetheless, the udeb means that we need a d-i ack. Is there anything I need to do to help the process? > +bind9 (1:9.9.5.dfsg-9+deb8u13.1) jessie; urgency=high > > Upload numbers are simple integers - 1:9.9.5.dfsg-9+deb8u14, please. Lol, I had deb8u14 in the first compilation run, but changed it and recompiled it again :). Cheers, -- Ondřej SurýKnot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver
Re: Bug#873481: jessie-pu: package bind9/9.9.5.dfsg-9+deb8u13.1
Control: tags -1 + confirmed d-i On Mon, 2017-08-28 at 11:03 +0200, Ondřej Surý wrote: > this is the jessie counterpart of bind9 update to KSK-2017. > > No other change has been done to the package. Nonetheless, the udeb means that we need a d-i ack. +bind9 (1:9.9.5.dfsg-9+deb8u13.1) jessie; urgency=high Upload numbers are simple integers - 1:9.9.5.dfsg-9+deb8u14, please. Regards, Adam
Re: Bug#873479: stretch-pu: package bind9/1:9.10.3.dfsg.P4-12.3+deb9u3
Control: tags -1 + confirmed d-i On Mon, 2017-08-28 at 10:21 +0200, Ondřej Surý wrote: > this is the next update in the series of KSK-2017 RZ KSK rollover. > > Only the default keys have been updated. This looks fine to me, but will need a d-i ack due to the fact that the package generates a udeb. > This is the stretch part of the update. It also looks like that the > version in unstable need manual override to migrate to testing: > > * Not touching package due to block-udeb request by freeze (please > contact the d-i release manager if an update is needed) Indeed, there's a udeb freeze currently in order to try and prepare a d-i alpha for buster. That's somewhat outside the scope of the p-u request though. Regards, Adam
Re: Bug#873465: apt: wrongly reports failure on 'update' on mips64el, triggers d-i FTBFS
Hi Julian, And thanks for the swift answer. Julian Andres Klode(2017-08-28): > Hmm, shouldn't it also STRIP the -O2? I guess this would work too and > might be nicer? AFAICT the last -On wins, and it's been confirmed locally + on eller, so I considered myself fine with it. > ifeq ($(DEB_HOST_ARCH),mips64el) > DEB_BUILD_OPTIONS += noopt > endif > > (noopt also changes -O2 into -O0). Anyhow, feel free to upload an > NMU with ifeq ($(DEB_HOST_ARCH),mips64el) around either change. On second thought, I'm currently considering ignoring mips64el entirely for the first alpha release. I've asked other release team members what they think, so I might skip NMUing your package. I can test the noopt addition on eller and rerun a debian-installer build so that you have confirmation it builds fine with this change as well. KiBi. signature.asc Description: Digital signature
Re: Bug#873465: apt: wrongly reports failure on 'update' on mips64el, triggers d-i FTBFS
On Mon, Aug 28, 2017 at 07:50:34AM +0200, Cyril Brulebois wrote: > Control: tag -1 patch > > Cyril Brulebois(2017-08-28): > > Given apt 1.5~beta2 was uploaded on the evening of the 17th, it probably > > reached the archive on the 18th, and was first used in the build chroot > > for the 0030Z build on the 19th. I'm filing this against apt since it > > seems clear to me there were no actual download errors, but it also > > seems likely that apt might be encountering gcc-7 related > > miscompilations, see #871514. > > > > In any case, a speedy fix would be much appreciated, as this is a > > blocker for the D-I Buster Alpha 1 release (which has already been > > delayed way too much for other reasons). > > I've built apt with -O0 (it seems a more acceptable workaround than > going back to gcc-6), and setting PATH/LD_LIBRARY_PATH to point to its > debian/tmp directory, I've managed to get rid of the issue I was getting > when trying to build debian-installer, and even managed to get a full > build. > > Of course this generates a lot of noise in dpkg-gensymbols (end of the > build log attached), but since it didn't bail on me, I guess that's OK? > > Trivial patch for debian/rules attached; of course this can be limited > to mips64el, but I'd like to get a maintainer's opinion as to whether > that's an acceptable workaround for the time being. If it is, I can NMU. Hmm, shouldn't it also STRIP the -O2? I guess this would work too and might be nicer? ifeq ($(DEB_HOST_ARCH),mips64el) DEB_BUILD_OPTIONS += noopt endif (noopt also changes -O2 into -O0). Anyhow, feel free to upload an NMU with ifeq ($(DEB_HOST_ARCH),mips64el) around either change. -- Debian Developer - deb.li/jak | jak-linux.org - free software dev | Ubuntu Core Developer | When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you.
Re: Bug#873419: Debian non-free livecd does not have access to live installer after booting
reassign 873419 debian-installer thanks On Sun, Aug 27, 2017 at 08:43:19AM -0600, Arjun Krishnan wrote: > Package: debian-live-9.1.0-amd64-cinnamon+nonfree.iso > > Version: 9.1.0 > > X-Debbugs-CC: debian...@lists.debian.org > > The debian live cd boots off a usb stick created in the following way: > > 1. The usb stick has two partitions, one efi and one ext4 > 1. The efi partition has a grub2 shim that loads grub from the ext4 > partition. > 1. The ext4 partition has grub and the debian livecd iso > > This is a strange mechanism, but it helps me load different linux > distributions with a single > unified mechanism. The isos merely go in a single folder. > > Grub2 loads the debian livecd with the following entry > > menuentry 'debian livecd' { > set iso='debian-live-9.1.0-amd64-cinnamon+nonfree.iso' > loopback loop $iso > linux (loop)/live/vmlinuz-4.9.0-3-amd64 findiso=$iso > initrd (loop)/live/initrd.gz-4.9.0-3-amd64 > } > > Once the livecd loads, everything appears to work. BUT there is no way to > run > the installer at this stage. There is no `click here to install` on the > desktop. > I've tried pulling up a terminal, and apt-getting the installer. This > results in the following: > > $ sudo apt install debian-installer-launcher > $ sudo debian-installer-launcher > no suitable d-i initrd image found, aborting > umount /lib/live/installer: mountpoint not found > > Arjun
Processed: Re: Bug#873419: Debian non-free livecd does not have access to live installer after booting
Processing commands for cont...@bugs.debian.org: > reassign 873419 debian-installer Bug #873419 [debian-live-9.1.0-amd64-cinnamon+nonfree.iso] Debian non-free livecd does not have access to live installer after booting Warning: Unknown package 'debian-live-9.1.0-amd64-cinnamon+nonfree.iso' Bug reassigned from package 'debian-live-9.1.0-amd64-cinnamon+nonfree.iso' to 'debian-installer'. Ignoring request to alter found versions of bug #873419 to the same values previously set Ignoring request to alter fixed versions of bug #873419 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 873419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#873472: udhcpc (not uchcpc) in debian/tree/udhcpc/etc/udhcpc/default.script
Package: udhcpc Version: 1:1.22.0-19 Severity: minor Tags: patch There is a one-letter typo in the syslog tag in debian/tree/udhcpc/etc/udhcpc/default.script: log() { - logger -t "uchcpc[$PPID]" -p daemon.$1 "$interface: $2" + logger -t "udhcpc[$PPID]" -p daemon.$1 "$interface: $2" } Please fix it, so my logs are easier to grep ☺