Re: linux image for 12.2?
On Tue, 2023-08-08 at 11:53 -0500, Matt Zagrabelny wrote: > Greetings Debian Release Team, > > Thank you for your service to Debian users, it is appreciated! > > Are there plans to update the linux kernel for the 12.2 point > release? > > I'm hitting a bug that is fixed (commit 3de4d22cc9ac7) in 6.1.43 and > am hoping that the next point release will include that kernel. > There's basically always a kernel update in every point release, but the specific version and any additional patches included is up to the kernel maintainers; adding the -kernel list to CC. Regards, Adam
Bug#1044518: linux: "RIP: 0010:get_xsave_addr+0x9b/0xb0" stacktrace in early boot with -24 bullseye kernel
Source: linux Version: 5.10.179-5 User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team X-Debbugs-Cc: debian-ad...@lists.debian.org, a...@debian.org Hi, Since the kernels on both the host and guests were upgraded to 5.10.179-5 (from 5.10.179-3), the guests on one of our Ganeti clusters have been reporting as tainted. Looking at dmesg shows the following trace early in boot: [0.201347] RIP: 0010:get_xsave_addr+0x9b/0xb0 [0.201351] Code: 48 83 c4 08 5b e9 15 80 bc 00 80 3d 8d 7c 80 01 00 75 a8 48 c7 c7 97 de 6b b2 89 74 24 04 c6 05 79 7c 80 01 01 e8 f5 96 88 00 <0f> 0b 8b 74 24 04 eb 89 31 c0 e9 e6 7f bc 00 66 0f 1f 44 00 00 89 [0.201353] RSP: :b2c03ec8 EFLAGS: 00010282 [0.201356] RAX: RBX: b2e6a600 RCX: b2cb3768 [0.201358] RDX: c000efff RSI: efff RDI: 0247 [0.201359] RBP: b2e6a4a0 R08: R09: b2c03ce8 [0.201361] R10: b2c03ce0 R11: b2ccb7a8 R12: 0246 [0.201362] R13: R14: R15: [0.201365] FS: () GS:9588fbc0() knlGS: [0.201367] CS: 0010 DS: ES: CR0: 80050033 [0.201368] CR2: 9588f000 CR3: 8260a001 CR4: 007308b0 [0.201373] DR0: DR1: DR2: [0.201374] DR3: DR6: fffe0ff0 DR7: 0400 [0.201376] Call Trace: [0.201383] identify_cpu+0x51f/0x540 [0.201389] identify_boot_cpu+0xc/0x94 [0.201392] arch_cpu_finalize_init+0x5/0x47 [0.201395] start_kernel+0x4ec/0x599 [0.201401] secondary_startup_64_no_verify+0xb0/0xbb [0.201406] ---[ end trace d7d9074a88473cb2 ]--- The systems seem to be running OK, but the stacktrace presumably points to an issue somewhere. A sample kvm invocation for an affected guest is ganeti04 18354 30.1 0.5 6015620 1114084 ? Sl Aug11 832:22 /usr/bin/kvm -name geo1.debian.org -m 1024 -smp 2 -pidfile /var/run/ganeti/kvm-hypervisor/pid/geo1.debian.org -device virtio-balloon -daemonize -D /var/log/ganeti/kvm/geo1.debian.org.log -machine pc-i440fx-5.2 -monitor unix:/var/run/ganeti/kvm-hypervisor/ctrl/geo1.debian.org.monitor,server,nowait -serial unix:/var/run/ganeti/kvm-hypervisor/ctrl/geo1.debian.org.serial,server,nowait -usb -display none -cpu host -uuid 36cf5fbc-1414-4b27-874e-ea3153150aa9 -device virtio-rng-pci,bus=pci.0,addr=0x1e,max-bytes=1024,period=1000 -global isa-fdc.fdtypeA=none -netdev type=tap,id=nic-6e9afdf8-ccaf-42e8,fd=10 -device virtio-net-pci,id=nic-6e9afdf8-ccaf-42e8,bus=pci.0,addr=0xd,netdev=nic-6e9afdf8-ccaf-42e8,mac=aa:00:00:46:8f:08 -incoming tcp:172.29.182.13:8102 -qmp unix:/var/run/ganeti/kvm-hypervisor/ctrl/geo1.debian.org.qmp,server,nowait -qmp unix:/var/run/ganeti/kvm-hypervisor/ctrl/geo1.debian.org.kvmd,server,nowait -boot c -device virtio-blk-pci,id=disk-8a45befd-be45-4b75,bus=pci.0,addr=0xc,drive=disk-8a45befd-be45-4b75 -drive file=/var/run/ganeti/instance-disks/geo1.debian.org:0,format=raw,if=none,aio=threads,cache=none,discard=unmap,id=disk-8a45befd-be45-4b75,auto-read-only=off -runas ganeti04 It seems that buster guests on the same host are unaffected, with similar-looking command lines. The host's CPUs are Intel Xeon Silver 4110. Our other x86-64 clusters either use AMD CPUs (also with "-cpu host") or Xeon E5-2699 v3 CPUs, with "-cpu Haswell-noTSX". Regards, Adam
Bug#1044518: linux: "RIP: 0010:get_xsave_addr+0x9b/0xb0" stacktrace in early boot with -24 bullseye kernel
On Sun, 2023-08-13 at 18:21 +0100, Adam D. Barratt wrote: > Since the kernels on both the host and guests were upgraded to > 5.10.179-5 (from 5.10.179-3), the guests on one of our Ganeti > clusters > have been reporting as tainted. Looking at dmesg shows the following > trace early in boot: > I realised that a little bit more of the surrounding context from dmesg might help: [0.093383] kvm-guest: setup PV IPIs [0.094931] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.094968] clocksource: tsc-early: mask: 0x max_cycles: 0x1e33052aadd, max_idle_ns: 440795310221 ns [0.094974] Calibrating delay loop (skipped) preset value.. 4190.15 BogoMIPS (lpj=8380304) [0.095097] x86/cpu: User Mode Instruction Prevention (UMIP) activated [0.095106] [ cut here ] [0.095107] get of unsupported state [0.095120] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0 [0.095122] Modules linked in: [0.095126] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.0-24-amd64 #1 Debian 5.10.179-5 [0.095128] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [0.095131] RIP: 0010:get_xsave_addr+0x9b/0xb0 [0.095134] Code: 48 83 c4 08 5b e9 15 80 bc 00 80 3d 8d 7c 80 01 00 75 a8 48 c7 c7 97 de eb 94 89 74 24 04 c6 05 79 7c 80 01 01 e8 f5 96 88 00 <0f> 0b 8b 74 24 04 eb 89 31 c0 e9 e6 7f bc 00 66 0f 1f 44 00 00 89 [0.095136] RSP: :95403ec8 EFLAGS: 00010282 [0.095139] RAX: RBX: 9566a600 RCX: 954b3768 [0.095141] RDX: c000efff RSI: efff RDI: 0247 [0.095142] RBP: 9566a4a0 R08: R09: 95403ce8 [0.095144] R10: 95403ce0 R11: 954cb7a8 R12: 0246 [0.095145] R13: R14: R15: [0.095148] FS: () GS:911abec0() knlGS: [0.095149] CS: 0010 DS: ES: CR0: 80050033 [0.095151] CR2: 911a95801000 CR3: 13e0a001 CR4: 007308b0 [0.095155] DR0: DR1: DR2: [0.095156] DR3: DR6: fffe0ff0 DR7: 0400 [0.095158] Call Trace: [0.095166] identify_cpu+0x51f/0x540 [0.095171] identify_boot_cpu+0xc/0x94 [0.095174] arch_cpu_finalize_init+0x5/0x47 [0.095177] start_kernel+0x4ec/0x599 [0.095183] secondary_startup_64_no_verify+0xb0/0xbb [0.095188] ---[ end trace 438682bdad114415 ]--- [0.095288] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0 [0.095289] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0 [0.095296] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization Regards, Adam
Bug#1036543: [PATCH 5.10 076/529] crypto: ccp: Use the stack for small SEV command buffers
Control: close -1 5.10.191-1 On Fri, 2023-05-26 at 17:36 +0200, Ben Hutchings wrote: > On Wed, 2023-05-17 at 16:06 +0200, Greg Kroah-Hartman wrote: > > On Wed, May 17, 2023 at 04:02:35PM +0200, Greg Kroah-Hartman wrote: > > > On Wed, May 17, 2023 at 02:56:21PM +0200, Ben Hutchings wrote: [..] > > > Julien Cristau reported a regression in ccp - the > > > > WARN_ON_ONCE(!virt_addr_valid(data)) is now being triggered. I > > > > believe > > > > this was introduced by the above commit, which depends on: > > > > > > > > commit 8347b99473a313be6549a5b940bc3c56a71be81c > > > > Author: Sean Christopherson > > > > Date: Tue Apr 6 15:49:48 2021 -0700 > > > > > > > > crypto: ccp: Play nice with vmalloc'd memory for SEV > > > > command structs > > > > > > > > Ben. > > > > > > > > > > Thanks for letting me know, now queued up. > > > > Nope, now dropped, it breaks the build :( > > I've now looked further and found that we need both: > > d5760dee127b crypto: ccp: Reject SEV commands with mismatching > command buffer > 8347b99473a3 crypto: ccp: Play nice with vmalloc'd memory for SEV > command structs > > (Not yet tested; I'll ask Julien if he can do that.) > Having just upgraded several affected debian.org nodes, I'm happy to confirm that the 5.10.191-1 kernel resolves the issue for us. Regards, Adam
Upcoming stable point release (12.3)
Hi, The next point release for "bookworm" (12.3) is scheduled for Saturday, December 9th. Processing of new uploads into bookworm-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (12.5)
Hi, The next point release for "bookworm" (12.5) is scheduled for Saturday, February 10th. Processing of new uploads into bookworm-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (11.9)
Hi, The next point release for "bullseye" (11.9) is scheduled for Saturday, February 10th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: Upcoming stable point release (12.6)
On Fri, 2024-02-16 at 17:35 +, Jonathan Wiltshire wrote: > The next point release for "bookworm" (12.6) is scheduled for > Saturday, April 6th. Processing of new uploads into bookworm- > proposed-updates will be frozen during the preceeding weekend. Due to recent events, the point release has been postponed. A new date will be announced when possible. Regards, Adam
Bug#1071272: linux: building the bookworm-backports armhf kernel causes OOM on buildds
Source: linux Version: 6.7.12-1~bpo12+1 Severity: serious X-Debbugs-CC: debian-...@lists.debian.org X-Debbugs-CC: d...@debian.org Hi, armhf builds of the bookworm-backports kernel appear to have led to outages on several buildds recently. Each of arm-ubc-04, arm-ubc-05 and arm-ubc-06 (QEMU ganeti guests) stopped responding after starting to build the kernel, and had to be rebooted. The build logs stop are various points - two at different points during drivers/net, and one during the dpkg-deb runs at the end of the build. The one common factor appears to be that the system logs on each machine show the OOM killer being invoked during the build, initially killing syslog but subsequently schroot and many system processes. Each buildd has 12GB of RAM and 120GB of swap available. The issue also seems to be specific to the armhf build - arm-ubc-06 recently successfully built the armel build of the same kernel version. Please let us know if you need any further information. Regards, Adam
Upcoming stable point release (11.2)
Hi, The next point release for "bullseye" (11.2) is scheduled for Saturday, December 18th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.3)
Hi, The next point release for "bullseye" (11.3) is scheduled for Saturday, March 26th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (10.12)
Hi, The next point release for "buster" (10.12) is scheduled for Saturday, March 26th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.7)
Hi, The next point release for "bullseye" (11.7) is scheduled for Saturday, April 29th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.4)
Hi, The next point release for "bullseye" (11.4) is scheduled for Saturday, July 9th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.5)
Hi, The next point release for "bullseye" (11.5) is scheduled for Saturday, September 10th. Processing of new uploads into bullseye-proposed- updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (10.13)
Hi, The next - and final - point release for "buster" (10.13) is scheduled for Saturday, September 10th. Processing of new uploads into buster- proposed-updates will be frozen during the weekend of August 27th. Regards, Adam
Upcoming stable point release (11.6)
Hi, The next point release for "bullseye" (11.6) is scheduled for Saturday, December 17th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (8.3)
Hi, The next point release for "jessie" (8.3) is scheduled for Saturday, January 23rd. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (8.1)
Hi, The first point release for "jessie" (8.1) is scheduled for Saturday, June 6th. Stable NEW will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
Bug#780773: Please backport EDAC_IE31200 to Linux 3.16.x
On 2015-04-07 0:17, Ben Hutchings wrote: Bug #780773 requests backporting a new EDAC (Error Detection And Correction) driver that is wanted on some Intel-based servers. It seems to be simple to backport to 3.16, but I'm not sure whether it meets the release criteria. EDAC drivers are not needed for hardware enablement, but they are needed for logging of correctable ECC errors and detailed information about uncorrectable ECC errors, which is important for highly reliable systems. Please can I have an ack or nak from the release team? Assuming that this request is still current and wasn't just pre-release, this sounds like something I'd be happy to defer to your judgement on. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e84071c0540b02a7902eb98c1e214...@mail.adam-barratt.org.uk
Upcoming stable point release (8.2)
Hi, The next point release for "jessie" (8.2) is scheduled for Saturday, September 5th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
Upcoming oldstable point release (7.9)
Hi, The next point release for "wheezy" (7.9) is scheduled for Saturday, September 5th. Processing of new uploads into wheezy-proposed-updates will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
3.2.71-1 / 3.16.7-ckt17-1
Hi,
Thanks for uploading new kernels to {,o-}p-u.
Unfortunately, the wheezy upload FTBFS on i386 with a bunch of ABI
changes.
Looking at the diffstat for the jessie upload, there are many new files
along the lines of:
debian/linux-headers-3.16.0-0.bpo.4-4kc-malta.postinst
| 26
debian/linux-headers-3.16.0-0.bpo.4-586.postinst
| 26
debian/linux-headers-3.16.0-0.bpo.4-5kc-malta.postinst
| 26
[...]
debian/linux-image-3.16.0-0.bpo.4-versatile.postinst
| 649 ++
debian/linux-image-3.16.0-0.bpo.4-versatile.postrm
| 265
debian/linux-image-3.16.0-0.bpo.4-versatile.preinst
| 119 +
debian/linux-image-3.16.0-0.bpo.4-versatile.prerm
| 158 ++
debian/linux-image-3.16.0-0.bpo.4-versatile.templates
| 53
Was that intentional?
Regards,
Adam
Upcoming stable point release (7.8)
Hi, The next point release for "wheezy" (7.8) is scheduled for Saturday, January 10th. Stable NEW will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
Upcoming stable point release (7.6)
Hi, The next point release for "wheezy" (7.6) is scheduled for Saturday, July 12th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402513678.4620.13.ca...@jacala.jungle.funky-badger.org
Upcoming oldstable point release (6.0.10)
Hi, The next (and final) point release for "squeeze" (6.0.10) is scheduled for Saturday, July 19th. Oldstable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402513777.4620.15.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.60-1)
On Sun, 2014-06-29 at 04:14 +0100, Ben Hutchings wrote: > On Wed, 2014-06-11 at 16:39 +0100, Ben Hutchings wrote: > > I intend to upload linux version 3.2.60-1 to stable-proposed-updates at > > the weekend. Let me know if there's a reason not to do this. > > I've just uploaded now. The upload has since had some wider exposure as a result of being used as the basis for a security release. In the process, a few bugs have been reported regarding regressions in networking - for instance, #754173, #754197 and #754294. If it weren't for the security fix, I'd be inclined to suggest that we skip 3.2.60 at this point, to give us more time to address the regressions; that may still not be the worst idea, as it at least allows people to easily downgrade to the current stable kernel. Thoughts welcome. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1404928789.1894.6.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.60-1)
On Wed, 2014-07-09 at 19:29 +0100, Ben Hutchings wrote: > On Wed, 2014-07-09 at 18:59 +0100, Adam D. Barratt wrote: > > On Sun, 2014-06-29 at 04:14 +0100, Ben Hutchings wrote: > > > On Wed, 2014-06-11 at 16:39 +0100, Ben Hutchings wrote: > > > > I intend to upload linux version 3.2.60-1 to stable-proposed-updates at > > > > the weekend. Let me know if there's a reason not to do this. > > > > > > I've just uploaded now. > > > > The upload has since had some wider exposure as a result of being used > > as the basis for a security release. In the process, a few bugs have > > been reported regarding regressions in networking - for instance, > > #754173, #754197 and #754294. > > I think those are all the same bug. Quite possibly. > For what it's worth, my home router is running the new version without > any such problem. Thanks for the data point. > > If it weren't for the security fix, I'd be inclined to suggest that we > > skip 3.2.60 at this point, to give us more time to address the > > regressions; that may still not be the worst idea, as it at least allows > > people to easily downgrade to the current stable kernel. > > > > Thoughts welcome. > > As there aren't any major changes to hardware support in this version, > there will be little benefit from rebuilding the installer using > 3.2.60-1. So I'm OK with leaving wheezy as it is. We already rebuilt the installer purely as a part of our process, but I'd assumed that it would not be particularly affected by any of the regressions. > I'm hoping to be able to fix the regressions (probably with a revert) in > another security update by the time of the point release. That sounds good; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1404930921.1894.9.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.7)
Hi, The next point release for "wheezy" (7.7) is scheduled for Saturday, October 18th. Stable NEW will be frozen during the preceding weekend. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411585956.15708.2.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.63-1)
On Wed, 2014-09-24 at 03:54 +0100, Ben Hutchings wrote: > I intend to upload linux version 3.2.63-1 to stable-proposed-updates > later this week. This will include all the fixes that went into stable > updates 3.2.61-63 inclusive, including fixes for these security issues: [...] Flagged for acceptance in to p-u; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411926130.25283.10.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.63-1)
On Sun, 2014-09-28 at 18:42 +0100, Adam D. Barratt wrote:
> On Wed, 2014-09-24 at 03:54 +0100, Ben Hutchings wrote:
> > I intend to upload linux version 3.2.63-1 to stable-proposed-updates
> > later this week. This will include all the fixes that went into stable
> > updates 3.2.61-63 inclusive, including fixes for these security issues:
> [...]
>
> Flagged for acceptance in to p-u; thanks.
and built everywhere except s390{,x}, where it failed with an ABI
change.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1412015358.25283.14.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.63-1)
On Mon, 2014-09-29 at 23:24 +0100, Ben Hutchings wrote:
> On Mon, 2014-09-29 at 19:29 +0100, Adam D. Barratt wrote:
> > On Sun, 2014-09-28 at 18:42 +0100, Adam D. Barratt wrote:
> > > On Wed, 2014-09-24 at 03:54 +0100, Ben Hutchings wrote:
> > > > I intend to upload linux version 3.2.63-1 to stable-proposed-updates
> > > > later this week. This will include all the fixes that went into stable
> > > > updates 3.2.61-63 inclusive, including fixes for these security issues:
> > > [...]
> > >
> > > Flagged for acceptance in to p-u; thanks.
> >
> > and built everywhere except s390{,x}, where it failed with an ABI
> > change.
>
> We can ignore that change, but I forgot to do that. (We had the same
> build failure in 3.14.10-1.)
I've flagged 3.2.63-2, including the fix, for acceptance; thanks for the
quick turn-around.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1412055407.25283.19.ca...@jacala.jungle.funky-badger.org
Bug#602853: increasing severity as this is a blocker for many many sparc out there
user release.debian@packages.debian.org clone 602853 -1 severity -1 wishlist reassign -1 release-notes retitle -1 Document sparc console handover issues usertag 602853 + squeeze-can-defer tag 602853 + squeeze-ignore thanks On Mon, 2011-01-31 at 19:21 +0100, Fabio M. Di Nitto wrote: > severity 602853 grave > thanks Unfortunately it's rather late to get this fixed for the squeeze release, and definitely late for d-i. Incorporating a fix for 6.0.1 would be welcome, as would some text for the release notes (and/or d-i errata?); I've cloned a copy of the bug for the latter purpose. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1296512827.19354.864.ca...@hathi.jungle.funky-badger.org
Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1
On Tue, 2011-03-01 at 18:19 +, Ben Hutchings wrote: > On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: > > On Mon, Feb 28, 2011 at 04:53, Ben Hutchings wrote: > > ... > > > I know that I need to upload in time for the installer team to rebuild > > > the installer with the new kernel version, addressing the known issues > > > with the kernel used in 6.0.0. Please could you let me know what the > > > deadline is for that? > > ... > > > > It depends on the ETA for 6.0.1. I'd a week before the targeted date > > assuming it builds fine on all arches. For a confort level, I'd say a > > cuple of weeks like a good time for we to update the installer for it. > > OK, so what's the targeted date? We're still working out the precise details, but the general plan is to aim for 6.0.1 being during FTPMaster's upcoming meeting in Essen. That starts on the 21st so, working backwards, two weeks would take us to the coming weekend. If it's possible to get the source upload in by the end of the weekend, that would be great. Hopefully getting all the builds in for squeeze quickly will be no problem; we sometimes ended up cutting things rather fine in the past for lenny (e.g. arm taking several days to build and a race condition somewhere in the build setup process which meant some architectures needed three attempts at the build for some uploads). Otavio: other than lkdi and the d-i build itself (which I guess could be a binNMU this time?) which obviously need to come afterwards, are any of your other proposed uploads dependent on the timing of the kernel uploads? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1299007033.10572.59.ca...@hathi.jungle.funky-badger.org
Upcoming stable point release (7.3)
Hi, The next point release for "wheezy" (7.3) is scheduled for Saturday December 14th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386102648.3844.14.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.53-2)
On 2013-12-17 5:49, Ben Hutchings wrote: I screwed up the fix for CVE-2013-2929 in linux 3.2.53-1, making things worse *and* breaking legitimate apps (chromium). Please accept 3.2.53-2 into stable-proposed-updates (when it arrives - it will take another few minutes). Flagged for acceptance; thanks. (Unfortunately slightly too late for the current dinstall to pick it up.) Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/14b5978ecc827d7a81fd1970f7fd7...@mail.adsl.funky-badger.org
Upcoming stable point release (7.4)
Hi, The next point release for "wheezy" (7.4) is scheduled for Saturday February 8th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1390507736.6444.23.ca...@jacala.jungle.funky-badger.org
Upcoming oldstable point release (6.0.9)
Hi, The next point release for "squeeze" (6.0.9) is scheduled for Saturday February 15th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1390507759.6444.24.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.5)
Hi, The next point release for "wheezy" (7.5) is scheduled for Saturday, April 26th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1395609622.12119.11.ca...@jacala.jungle.funky-badger.org
Re: Next (old)stable point releases
On Mon, 2013-09-02 at 18:35 +0200, Joey Schulze wrote: > Jonathan Wiltshire wrote: [I don't appear to have Jonathan's mail - and nor do the list archives - so piggy-backing on Joey's.] > > We're much longer overdue for oldstable (February) than we are for stable > > (June); if we stagger them, should we consider oldstable first? It would quite probably be easier to do stable first, despite the above. We have a few packages in both p-u and o-p-u currently which are newer upstream versions (mostly via security), such that p-u > o-p-u > stable > oldstable. If the oldstable point release occurs first, we either have to not include those packages until 6.0.9 or temporarily have oldstable > stable, which is at best confusing. (We've been in the latter situation previously, for 5.0.9 / 6.0.3, and after some debate on the day decided to include the packages in any case; I'm not sure we should take that as precedent, however.) Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1378161699.18562.14.ca...@jacala.jungle.funky-badger.org
Re: Next (old)stable point releases
On Mon, 2013-08-19 at 14:59 +0100, Steve McIntyre wrote: > On Mon, Aug 19, 2013 at 03:55:14PM +0200, Julien Cristau wrote: > >we should start thinking about dates for the 7.2 and 6.0.8 point > >releases. Which week-ends in the coming months would work for > >ftpmaster, press and cd? (We'd need one date for stable and another > >later for oldstable.) Apologies for the delay from my side. [...] > >- Sep 7-8 That's obviously too close now. > >- Sep 28-29 I'm at a family event on that Saturday; it would be doable if someone else is available though. > >- Oct 12-13 > >- Oct 19-20 Either of those is fine for me. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1378246184.28836.91.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.2)
Hi, The next point release for "wheezy" (7.2) is scheduled for Saturday October 12th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1379877070.4765.26.ca...@jacala.jungle.funky-badger.org
Upcoming oldstable point release (6.0.8)
Hi, The next point release for "squeeze" (6.0.8) is scheduled for Saturday October 19th. Oldstable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1379877103.4765.27.ca...@jacala.jungle.funky-badger.org
Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))
[non-debian lists dropped] On Wed, 2013-06-05 at 20:46 +0100, Luke Kenneth Casson Leighton wrote: > what's the point of mentioning this? > > well, the point is: the expectation of the linux kernel developers is > that Everyone Must Convert To DeviceTree. [...] > thoughts and discussion appreciated. Somewhere other than debian-release, please. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1370462863.5745.6.ca...@jacala.jungle.funky-badger.org
Re: Updating Linux in wheezy
On Fri, 2013-06-07 at 03:26 +0100, Ben Hutchings wrote: > I realise there's now just a week before the point release, which > doesn't leave much time for updating the installer even if I upload > right now (which I'm not about to). Sorry for letting this slide. > Supposing I can upload on Saturday, could that new package get into the > installer, or at least into the point release? It's tight, but Saturday would be within the window we announced so should okay from that perspective; it could be interesting if any regressions appear. As wheezy's linux package also produces the kernel udebs, we should really have the kernel included in the point release be the same as the kernel that the installer's built with. CCing Cyril and -boot for any comments on that side. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1370580963.15198.28.ca...@jacala.jungle.funky-badger.org
Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)
On Fri, 2024-07-19 at 16:13 +0200, Diederik de Haas wrote: > [ adding debian-release to the list for some troubling observations ] > > On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote: > [...] > > Note that > > https://www.debian.org/releases/stable/amd64/apcs01.en.html > > does not recommend anything for the /boot partition. > > > > https://www.debian.org/releases/stable/amd64/apcs05.en.html says > > "25–50MB should suffice" (though this is probably not sufficient > > for most uses). > > > > https://linuxhint.com/boot-partition-size-debian/ says > > 256 MB / 512 MB for Debian 11. > > > > Mine has 512 MB (more that 10 times the recommended 25–50MB). > > Holy crap! Some quotes from the Stable documentation: > > "If you have a large IDE disk" > "This restriction doesn't apply if you have a BIOS newer than around > 1995–98" > Seeing the word "cylinder" all over the place ... > "CHS translation mode (“Large”)" = Cylinder/Head/Sector I presume? > > And then indeed "25–50MB should suffice" (for /boot/ partition). > > Maybe that document should be updated for this CENTURY? "That document" comes from src:installation-guide, which is maintained by the d-i team, not the Release Team. Regards, Adam
Upcoming stable point release (10.6)
Hi, The next point release for "buster" (10.6) is scheduled for Saturday September 26th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.7)
Hi, The next point release for "buster" (10.7) is scheduled for Saturday December 5th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.8)
Hi, The next point release for "buster" (10.8) is scheduled for Saturday February 6th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.1)
Hi, The first point release for "buster" (10.1) is scheduled for Saturday, September 7th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (9.10)
Hi, The next point release for "stretch" (9.10) is scheduled for Saturday, September 7th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
process-upload issue (was: Re: Bits from the Release Team: ride like the wind, Bullseye!)
[CC += ftpmaster]
On Mon, 2019-08-05 at 17:49 +0100, Ben Hutchings wrote:
> On Sun, 2019-07-21 at 10:55 -0300, Ivo De Decker wrote:
> [...]
> > We are aware that src:linux is a special case here. I added an
> > exception for the arch:all binaries from src:linux. When the next
> > ABI bump in unstable happens, feel free to let me know, so that I
> > can check if it works as expected.
>
> I uploaded a new version (5.2.6-1) to unstable today (11:35 UTC), and
> the upload was acknowledged (11:40 UTC) but it hasn't yet showed up
> in the NEW queue.
That looks like a problem on the archive side. The dak log suggests an
issue logging an issue with a .changes file:
20190805181929|process-upload|dak|exception|Traceback (most recent call last):
20190805181929|process-upload|dak|exception| File "/usr/local/bin/dak", line
228, in main
20190805181929|process-upload|dak|exception|module.main()
20190805181929|process-upload|dak|exception| File
"/srv/ftp-master.debian.org/dak/dak/process_upload.py", line 591, in main
20190805181929|process-upload|dak|exception|process_changes(changes_files)
20190805181929|process-upload|dak|exception| File
"/srv/ftp-master.debian.org/dak/dak/process_upload.py", line 502, in
process_changes
20190805181929|process-upload|dak|exception|Logger.log([filename, "Error
while loading changes: {0}".format(e)])
20190805181929|process-upload|dak|exception|UnicodeEncodeError: 'ascii' codec
can't encode character u'\ufffd' in position 223: ordinal not in range(128)
Regards,
Adam
Upcoming stable point release (10.4)
Hi, The next point release for "buster" (10.4) is scheduled for Saturday, May 9th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (9.13)
Hi, The next - and final - point release for "stretch" (9.13) is scheduled for Saturday, July 18th. Processing of new uploads into stretch- proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.5)
Hi, The next point release for "buster" (10.5) is scheduled for Saturday July 18th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
RFC: Clean-up of old kernel ABIs at point releases
[MFT and Reply-To set to debian-release, to try and avoid spamming too many people with the discussion] Hi, When the kernel ABI version has been increased between two point releases, we currently remove the old versions as part of the point release, to avoid carrying cruft. This has unfortunate side-effects for a number of use cases, including CI setups which immediately stop working as the packages they attempt to install no longer exist in the archive. If we were instead to change this policy to, for example, remove the packages after the subsequent point release instead, can anyone see any problems that this might cause, whether for tooling, tools or anything else? Regards, Adam
Re: Upcoming stable point release (10.5)
Hi, On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote: > The next point release for "buster" (10.5) is scheduled for Saturday > July 18th. Processing of new uploads into buster-proposed-updates > will be frozen during the preceding weekend. Unfortunately this has had to be delayed slightly. A new date will be announced soon. Regards, Adam
Re: Upcoming stable point release (10.5)
Hi, On Sun, 2020-07-12 at 15:37 +0100, Adam D. Barratt wrote: > On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote: > > The next point release for "buster" (10.5) is scheduled for > > Saturday July 18th. Processing of new uploads into buster-proposed- > > updates will be frozen during the preceding weekend. > > Unfortunately this has had to be delayed slightly. > > A new date will be announced soon. This will now be Saturday August 1st. Regards, Adam
Upcoming stable point release (10.10)
Hi, The next point release for "buster" (10.10) is scheduled for Saturday June 19th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.2)
Hi, The next point release for "buster" (10.2) is scheduled for Saturday, November 16th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.3)
Hi, The next point release for "buster" (10.3) is scheduled for Saturday, February 8th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (9.12)
Hi, The next point release for "stretch" (9.12) is scheduled for Saturday, February 8th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (10.11)
Hi, The next point release for "buster" (10.11) is scheduled for Saturday, October 9th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.1)`
Hi, The first point release for "bullseye" (11.1) is scheduled for Saturday, October 9th. Processing of new uploads into bullseye- proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.9)
Hi, The next point release for "buster" (10.9) is scheduled for Saturday March 27th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: Stable update of linux-2.6
On Sun, 2011-03-27 at 20:31 +0100, Ben Hutchings wrote: > There were a couple of regressions in linux-2.6 version 2.6.32-31 (i.e. > Debian 6.0.1) that should be fixed a.s.a.p: [...] > Either Dann or I will upload an update to stable-proposed-updates, > intended for early release through stable-updates. Unfortunately, the powerpc build reproducibly FTBFS: CC arch/powerpc/kernel/crash.o /build/buildd-linux-2.6_2.6.32-32-powerpc-emhBwA/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/crash.c: In function 'default_machine_crash_shutdown': /build/buildd-linux-2.6_2.6.32-32-powerpc-emhBwA/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/crash.c:448: error: implicit declaration of function 'crash_kexec_wait_realmode' make[6]: *** [arch/powerpc/kernel/crash.o] Error 1 make[5]: *** [arch/powerpc/kernel] Error 2 make[4]: *** [sub-make] Error 2 make[3]: *** [all] Error 2 make[3]: Leaving directory `/build/buildd-linux-2.6_2.6.32-32-powerpc-emhBwA/linux-2.6-2.6.32/debian/build/build_powerpc_none_powerpc' make[2]: *** [debian/stamps/build_powerpc_none_powerpc_plain] Error 2 make[1]: *** [build_powerpc_none_powerpc_real] Error 2 make[2]: Leaving directory `/build/buildd-linux-2.6_2.6.32-32-powerpc-emhBwA/linux-2.6-2.6.32' make: make[1]: Leaving directory `/build/buildd-linux-2.6_2.6.32-32-powerpc-emhBwA/linux-2.6-2.6.32' *** [debian/stamps/build-base] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301437578.12508.562.ca...@hathi.jungle.funky-badger.org
Bug#620124: linux-2.6: FTBFS: Please package linux-tools-2.6.38 on ppc64
severity 620124 wishlist thanks Hi, On Wed, 2011-03-30 at 20:25 +0900, Hiroyuki Yamamoto wrote: > Package: linux-2.6 > Version: 2.6.38-2 > Severity: serious > Tags: patch > > Please package linux-tools-2.6.38 on ppc64. ppc64 isn't an official Debian architecture, so this isn't at all RC. The severity's arguable, but it's not RC. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301484662.12508.2180.ca...@hathi.jungle.funky-badger.org
Re: Uploading linux-2.6 (2.6.38-3)
On Tue, 2011-04-05 at 23:35 +0100, Ben Hutchings wrote: > Version 2.6.38-2 had build failures on a couple of architectures. We > now have fixes for those, and a few other bugs. There is no pending > stable update for 2.6.38, so I intend to upload this in about 24 hours' > time if there are no objections. 2.6.38-3 migrated to testing during tonight's britney run. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1302474427.4931.9285.ca...@hathi.jungle.funky-badger.org
Re: Stable update of linux-2.6
On Tue, 2011-03-29 at 23:26 +0100, Adam D. Barratt wrote: > On Sun, 2011-03-27 at 20:31 +0100, Ben Hutchings wrote: > > There were a couple of regressions in linux-2.6 version 2.6.32-31 (i.e. > > Debian 6.0.1) that should be fixed a.s.a.p: > [...] > > Either Dann or I will upload an update to stable-proposed-updates, > > intended for early release through stable-updates. > > Unfortunately, the powerpc build reproducibly FTBFS: The kernel's now built everywhere; thanks for following up on that. As this is the first time that we've actively pushed a non-security stable kernel update outside of the point release route, we'd prefer that it be opened to testing from a wider selection of users than most p-u kernels receive. A mail to that effect will be sent to the debian-stable-announce list shortly, with the plan being to look at pushing to stable-updates over the weekend if no significant issues are reported beforehand. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1302672715.4928.3353.ca...@hathi.jungle.funky-badger.org
Re: Stable update of linux-2.6
On Wed, April 13, 2011 12:57, Ben Hutchings wrote: > On Wed, 2011-04-13 at 06:31 +0100, Adam D. Barratt wrote: >> The kernel's now built everywhere; thanks for following up on that. As >> this is the first time that we've actively pushed a non-security stable >> kernel update outside of the point release route, we'd prefer that it be >> opened to testing from a wider selection of users than most p-u kernels >> receive. >> >> A mail to that effect will be sent to the debian-stable-announce list >> shortly, with the plan being to look at pushing to stable-updates over >> the weekend if no significant issues are reported beforehand. > > I think there's still a Xen regression (since 2.6.32-31) to be fixed. Ah, okay; thanks for the update. Let's hold off with the push to stable-updates for now then. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3b65335c111db9876d66ff5d9bf3d3d9.squir...@adsl.funky-badger.org
Re: Stable update of linux-2.6
On Wed, 2011-04-13 at 12:57 +0100, Ben Hutchings wrote: > On Wed, 2011-04-13 at 06:31 +0100, Adam D. Barratt wrote: [...] > > > On Sun, 2011-03-27 at 20:31 +0100, Ben Hutchings wrote: > > > > There were a couple of regressions in linux-2.6 version 2.6.32-31 (i.e. > > > > Debian 6.0.1) that should be fixed a.s.a.p: [...] > > The kernel's now built everywhere; thanks for following up on that. As > > this is the first time that we've actively pushed a non-security stable > > kernel update outside of the point release route, we'd prefer that it be > > opened to testing from a wider selection of users than most p-u kernels > > receive. [...] > I think there's still a Xen regression (since 2.6.32-31) to be fixed. I'm assuming that's #621072, which it looks like a resolution has been found for? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303749327.3323.5870.ca...@hathi.jungle.funky-badger.org
Re: Stable update of linux-2.6
On Mon, 2011-04-25 at 17:37 +0100, Ben Hutchings wrote: > On Mon, 2011-04-25 at 17:35 +0100, Adam D. Barratt wrote: > > On Wed, 2011-04-13 at 12:57 +0100, Ben Hutchings wrote: > > > I think there's still a Xen regression (since 2.6.32-31) to be fixed. > > > > I'm assuming that's #621072, which it looks like a resolution has been > > found for? > > Right. Are there any other outstanding fixes or other blockers for a 2.6.32-34 upload? The approximate two-monthly schedule for stable point releases means that we should be aiming for 6.0.2 to be around the end of May, so it would be good to try and get a finalised kernel for that in the not-too-distant future. (fwiw, the next lenny point release - 5.0.9 - shouldn't be too far behind; we need to poke relevant people but I'm working on an estimated schedule of around mid-June). Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304196097.4138.6341.ca...@hathi.jungle.funky-badger.org
Re: Stable update of linux-2.6
On Sun, 2011-05-01 at 18:53 +0100, Ben Hutchings wrote: > On Sat, 2011-04-30 at 21:41 +0100, Adam D. Barratt wrote: > > Are there any other outstanding fixes or other blockers for a 2.6.32-34 > > upload? The approximate two-monthly schedule for stable point releases > > means that we should be aiming for 6.0.2 to be around the end of May, so > > it would be good to try and get a finalised kernel for that in the > > not-too-distant future. > > Let's upload what we have now for 2.6.32-34. I intend to backport some > new hardware support but we can put that in 2.6.32-35. I've just flagged -34 for acceptance at the next dinstall; thanks for the upload. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304534196.30332.59.ca...@hathi.jungle.funky-badger.org
Re: Scheduling of Debian 6.0.2
On Sat, 2011-05-21 at 16:55 +0100, Ben Hutchings wrote: > I understand that the plan is to release the next stable update in 'late > May', i.e. the next 10 days. That's what _should_ happen according to the rough schedule, yes. Sadly (or not so, depending on how you look at it), I haven't found the tuits to finalise the arrangements so there's relatively little chance of us precisely hitting that marker. (I have moved said arranging up my to-do list though). Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1306018478.3491.6930.ca...@hathi.jungle.funky-badger.org
Bug#622146: nfs-common: compatibility between squeeze and sid broken
On Fri, 2011-08-05 at 19:09 +0200, Philipp Kern wrote: > On Mon, Aug 01, 2011 at 01:34:34AM -0700, Steve Langasek wrote: > > I've attached the patches for both packages to this mail. Phil, is it ok > > for these to be uploaded to stable-proposed-updates? This fixes a bug that > > makes squeeze kerberized NFS servers unusable with newer clients (e.g., > > wheezy). > > Please go ahead. I really hope that the regression potential is low > for existing clients. Let's hope we find it out before the point > release. (The change in nfs-utils is streching the guidelines a bit.) The krb5 package was uploaded and I've (somewhat belatedly) marked it for acceptance at the next dinstall. What's the status of the nfs-utils upload? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1315150558.3540.3.ca...@hathi.jungle.funky-badger.org
Bug#622146: nfs-common: compatibility between squeeze and sid broken
On Mon, 2011-09-05 at 12:46 -0400, Sam Hartman wrote: > >>>>> "Adam" == Adam D Barratt writes: > > > Adam> The krb5 package was uploaded and I've (somewhat belatedly) > Adam> marked it for acceptance at the next dinstall. What's the > Adam> status of the nfs-utils upload? > > My guess is they were waiting for krb5. > Remember they have to increase build-depends for the krb5 you just > accepted. If it requires a versioned build-dependency, then both packages could just have been uploaded at the same time. Even if we accepted them both from p-u-NEW together, the buildds would have put nfs-common in to the "build-deps uninstallable" state until the necessary version of krb5 was available. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1315851892.7688.5.ca...@hathi.jungle.funky-badger.org
Re: Upcoming Point Releases
On Sun, 2011-09-11 at 23:59 +0100, Ben Hutchings wrote: > On Wed, 2011-09-07 at 21:30 +0200, Philipp Kern wrote: > > For Squeeze it would be cool to have the kernel in for testing end of > > next week (16/17th). The d-i upload should be there the middle of week > > 39, October 1st at the latest. > [...] > > I believe we're now ready to do the kernel update, having got most of > the security fixes done separately. I'm going to start a build now and > intend to upload tomorrow unless I hear any objection to this (or I find > a problem myself). Nobody appears to have objected, and it was uploaded. I've just marked the upload for acceptance at the next dinstall; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1315942075.28889.3.ca...@hathi.jungle.funky-badger.org
Re: Upcoming Point Releases
On Tue, 13 Sep 2011 20:27:55 +0100, Adam D. Barratt wrote:
On Sun, 2011-09-11 at 23:59 +0100, Ben Hutchings wrote:
I believe we're now ready to do the kernel update, having got most
of
the security fixes done separately. I'm going to start a build now
and
intend to upload tomorrow unless I hear any objection to this (or I
find
a problem myself).
Nobody appears to have objected, and it was uploaded. I've just
marked
the upload for acceptance at the next dinstall; thanks.
Unfortunately the upload FTBFS on several architectures.
The ia64 log contains a few "cast from pointer to integer of different
size" warnings, and dies with:
/build/buildd-linux-2.6_2.6.32-36-ia64-4ELC7i/linux-2.6-2.6.32/debian/build/source_ia64_none/drivers/net/e1000e/netdev.c:6214:
error: 'e1000_suspend' undeclared here (not in a function)
/build/buildd-linux-2.6_2.6.32-36-ia64-4ELC7i/linux-2.6-2.6.32/debian/build/source_ia64_none/drivers/net/e1000e/netdev.c:6214:
error: 'e1000_resume' undeclared here (not in a function)
make[8]: *** [drivers/net/e1000e/netdev.o] Error 1
make[7]: *** [drivers/net/e1000e] Error 2
make[6]: *** [drivers/net] Error 2
armel, mips{,el} and sparc all failed with:
/build/buildd-linux-2.6_2.6.32-36-armel-fnA8Ad/linux-2.6-2.6.32/debian/build/source_armel_none/drivers/net/e1000e/netdev.c:
In function '__e1000e_disable_aspm':
/build/buildd-linux-2.6_2.6.32-36-armel-fnA8Ad/linux-2.6-2.6.32/debian/build/source_armel_none/drivers/net/e1000e/netdev.c:5323:
error: implicit declaration of function 'pci_pcie_cap'
make[8]: *** [drivers/net/e1000e/netdev.o] Error 1
make[7]: *** [drivers/net/e1000e] Error 2
make[6]: *** [drivers/net] Error 2
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/0e2697d03ebc7231a5625abd56c33...@adsl.funky-badger.org
Bug#622146: nfs-common: compatibility between squeeze and sid broken
On Wed, 2011-10-26 at 09:05 +0200, Luk Claes wrote: [...] > >>>>>>> "Adam" == Adam D Barratt writes: > >> > >> > >> Adam> The krb5 package was uploaded and I've (somewhat belatedly) > >> Adam> marked it for acceptance at the next dinstall. What's the > >> Adam> status of the nfs-utils upload? [...] > Anyway, uploaded now. Flagged for acceptance at the next dinstall; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1319898422.26970.12.ca...@hathi.jungle.funky-badger.org
Re: Squeeze point release (6.0.6)
On Fri, 2012-09-07 at 21:43 +0200, Philipp Kern wrote: > I'd like to arrange a point release to be done as soon as feasible. > So I'd like to propose a bunch of weekends here: > > * Sep 22/23: I'm personally busy on the 23th > * Sep 29/30: ok from RT side This is looking like the favourite so far, which would mean having p-u ready and closed next weekend. > * Oct 6/7: Adam's busy for the weekend, hence we'd like to avoid that > if possible > * Oct 13/14: BSP attended by adsb/Sledge, not ideal to schedule it > there [...] > Dear Kernel team: Which changes are still pending for 6.0.6? When could > we get them into the archive? For 22nd we'd close p-u-NEW on the 15th, > which would leave us with a week. -kernel / -live ping? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1347706305.28617.40.ca...@jacala.jungle.funky-badger.org
Re: Squeeze point release (6.0.6)
On Tue, 2012-09-18 at 11:30 -0600, dann frazier wrote: > On Mon, Sep 17, 2012 at 03:58:13PM +0200, Philipp Kern wrote: > > ok, given the replies, let's settle on this: > > > > On Fri, Sep 07, 2012 at 09:43:03PM +0200, Philipp Kern wrote: > > > * Sep 29/30: ok from RT side [...] > Sorry, been travelling heavily for the past several days. We do have > some changes queued, and I should be able to get a kernel uploaded by > this weekend, but probably not sooner since I expect work to keep me > pretty busy throught the work week. Thanks for the upload; the builds seem to be going well. There don't seem to be any new d-i changes in git, so I assume we "just" need lkdi, a round of d-i binNMUs and then a d-i-n-i upload? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1348418361.21568.17.ca...@jacala.jungle.funky-badger.org
Re: Squeeze point release (6.0.6)
On Mon, 2012-09-24 at 09:01 +0900, dann frazier wrote: > On Sun, Sep 23, 2012 at 05:39:21PM +0100, Adam D. Barratt wrote: > > Thanks for the upload; the builds seem to be going well. There don't > > seem to be any new d-i changes in git, so I assume we "just" need lkdi, > > a round of d-i binNMUs and then a d-i-n-i upload? > > afaik, that's correct. Cool; thanks. All of the kernel builds are (finally) in now; would you have time to take care of the lkdi uploads? Cheers, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1348523640.6724.21.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.32-1)
On Fri, 2012-10-19 at 14:44 +0100, Ben Hutchings wrote:
> I intend to upload linux version 3.2.32-1 to unstable this weekend.
> This brings in various fixes from stable updates 3.2.{31,32} and
> elsewhere, and should fix the previous FTBFS on mips{,el}.
Unblocked after an ack from KiBi on IRC; thanks.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1351893577.21571.20.ca...@jacala.jungle.funky-badger.org
Re: Uploading linux (3.2.32-1)
On Sat, 2012-11-03 at 14:20 +, Ben Hutchings wrote:
> On Fri, 2012-11-02 at 21:59 +0000, Adam D. Barratt wrote:
> > On Fri, 2012-10-19 at 14:44 +0100, Ben Hutchings wrote:
> > > I intend to upload linux version 3.2.32-1 to unstable this weekend.
> > > This brings in various fixes from stable updates 3.2.{31,32} and
> > > elsewhere, and should fix the previous FTBFS on mips{,el}.
> >
> > Unblocked after an ack from KiBi on IRC; thanks.
>
> You should unblock linux-latest as well.
Yep:
linux-latest | 46 | testing | source
linux-latest | 46 | unstable | source
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1351953934.4348.14.ca...@jacala.jungle.funky-badger.org
Re: linux-2.6 update for stable?
On Sat, 2013-01-19 at 18:14 +, Ben Hutchings wrote: > On Sun, 2013-01-13 at 14:19 +0100, Philipp Kern wrote: > > am Sun, Jan 13, 2013 at 12:16:30AM + hast du folgendes geschrieben: > > > We have a huge number of important fixes from 2.6.32.60 pending in svn, > > > plus two SCSI driver updates (hpsa and megaraid_sas). [...] > > > SRMs, is it OK to upload at the moment? > > > > yes. The sooner the better. ;) > > I've now uploaded 2.6.32-47, with a few more bug fixes that I noticed. Flagged for acceptance in to p-u; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1358723163.24414.12.ca...@jacala.jungle.funky-badger.org
Re: Bug#652015: pu: package iotop/0.4-2
On Thu, 2011-12-15 at 09:56 +0800, Paul Wise wrote: > On Wed, 2011-12-14 at 19:25 +0000, Adam D. Barratt wrote: > > > Please go ahead; thanks. > > Uploaded. For the record, this was accepted earlier today. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1324139655.1324.14.ca...@hathi.jungle.funky-badger.org
Upcoming stable point release
Hi, The next point release for "squeeze" (6.0.4) is scheduled for Saturday January 28th. Stable NEW will be frozen during the preceeding weekend (21st/22nd). As usual, base-files can be uploaded at any point before the freeze. If there is a further kernel update planned for inclusion in the point release, it would be ideal if that could be uploaded over the coming weekend so that we can look at finalising the installer later next week. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b0343660143780d37f8c02ff126c5...@mail.adsl.funky-badger.org
Re: Upcoming stable point release
[trimmed CC list] On Sat, 2012-01-14 at 04:09 +, Ben Hutchings wrote: > On Wed, 2012-01-11 at 13:12 +0000, Adam D. Barratt wrote: > > If there is a further kernel update planned for inclusion in the point > > release, it would be ideal if that could be uploaded over the coming > > weekend so that we can look at finalising the installer later next week. > > There are some more important changes pending, including a fix for a > regression in 2.6.32-40 (currently in stable-proposed-updates). I can > probably make an upload this weekend, but cannot promise that a further > upload will not be needed. We need some testing of the isci driver > (added in 2.6.32-40) and more generally regression testing. Thanks for the -41 upload. I accepted that in to p-u earlier today. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1326740818.816.6.ca...@jacala.jungle.funky-badger.org
Re: Upcoming stable point release
[CC += -boot] On 16.01.2012 19:06, Adam D. Barratt wrote: On Sat, 2012-01-14 at 04:09 +, Ben Hutchings wrote: On Wed, 2012-01-11 at 13:12 +, Adam D. Barratt wrote: > If there is a further kernel update planned for inclusion in the point > release, it would be ideal if that could be uploaded over the coming > weekend so that we can look at finalising the installer later next week. There are some more important changes pending, including a fix for a regression in 2.6.32-40 (currently in stable-proposed-updates). I can probably make an upload this weekend, but cannot promise that a further upload will not be needed. We need some testing of the isci driver (added in 2.6.32-40) and more generally regression testing. Thanks for the -41 upload. I accepted that in to p-u earlier today. Are there any current plans for a -42 upload? Looking at SVN there only appears to be one change listed in the changelog and it didn't immediately sound like it would need an upload on its own. If -41 is looking to be the final kernel for the point release, we should look at getting lkdi and any other pending d-i changes sorted out (although if there are pending changes then they should really have been raised on -release by now...) Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c3f10939f5368f0a74e77ac1f843f...@mail.adsl.funky-badger.org
Re: Scheduling of Debian 6.0.2
On Sat, 2011-05-21 at 16:55 +0100, Ben Hutchings wrote: > I understand that the plan is to release the next stable update in 'late > May', i.e. the next 10 days. As you'll have noticed, that didn't happen. We are now looking at releasing 6.0.2 on June 25th, i.e. in a little over two weeks from now. > I'm working on network driver updates to support new hardware, and I > think that a reasonable amount of regression testing will require at > least a week from now. Please consider delaying the stable update so > that there is time to include these updates in the installer after > testing. How are things going? In order to ensure that we have time to get the kernel available on all architectures and then perform a respin of the installer to pull in the updated kernel, we work on a schedule of having the kernel uploaded two weeks before the point release - for 6.0.2, that would mean over the coming weekend. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1307559331.14057.11.ca...@hathi.jungle.funky-badger.org
Re: Scheduling of Debian 6.0.2
On Wed, 2011-06-08 at 20:05 +0100, Ben Hutchings wrote: > On Wed, Jun 08, 2011 at 07:55:31PM +0100, Adam D. Barratt wrote: > > On Sat, 2011-05-21 at 16:55 +0100, Ben Hutchings wrote: > > > I'm working on network driver updates to support new hardware, and I [...] > > How are things going? In order to ensure that we have time to get the > > kernel available on all architectures and then perform a respin of the > > installer to pull in the updated kernel, we work on a schedule of having > > the kernel uploaded two weeks before the point release - for 6.0.2, that > > would mean over the coming weekend. > > I've had a couple of positive but incomplete reports, and some code > review of tg3 changes from upstream. I've not committed any changes > to these drivers and as things stand I don't think it would be > reasonable to do so. Thanks for the update. Were there any other changes you were looking at getting in to the point release on top of the 2.6.32-34squeeze1 currently in p-u? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1307560235.14057.17.ca...@hathi.jungle.funky-badger.org
Re: Scheduling of Debian 6.0.2
On Wed, 2011-06-08 at 20:05 +0100, Ben Hutchings wrote: > On Wed, Jun 08, 2011 at 07:55:31PM +0100, Adam D. Barratt wrote: > > How are things going? In order to ensure that we have time to get the > > kernel available on all architectures and then perform a respin of the > > installer to pull in the updated kernel, we work on a schedule of having > > the kernel uploaded two weeks before the point release - for 6.0.2, that > > would mean over the coming weekend. > > I've had a couple of positive but incomplete reports, and some code > review of tg3 changes from upstream. I've not committed any changes > to these drivers and as things stand I don't think it would be > reasonable to do so. > > This weekend I'll be travelling. (As it happens, I'm going to the > Linux netconf.) Well, before the weekend would also be fine from our point of view, if feasible. ;-) >From a practical point-of-view, what are the chances that we could look at an upload by the start of next week? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1307573780.26588.6.ca...@hathi.jungle.funky-badger.org
Re: Updating linux-2.6 for point release 6.0.3
On Mon, 2011-08-15 at 03:05 +0100, Ben Hutchings wrote: > Finally, there is a pending security update for squeeze > (2.6.32-35squeeze1). I would like to see this released first so that > the s-p-u upload (2.6.32-36) can include its fixes. Is there an (E)ETA for the security release? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1313527755.12895.28.ca...@hathi.jungle.funky-badger.org
Bug#638068: busybox binary in initrd.img is incorrectly overwritten by klibc hook
On 15.01.2012 20:16, Ãmeric Maschino wrote: Le 15 janvier 2012 19:08, maximilian attems a écrit : Nice detective work.  So the next question is: why does klibc-utils on ia64 provide /usr/lib/klibc/bin/sh instead of sh.shared like other architectures? #439181  ia64 works only static Thanks for pointing this out. I'd also be interested to hear how /usr/lib/klibc/bin/sh behaves in general: e.g., could you try    ldd /usr/lib/klibc/bin/sh    /usr/lib/klibc/bin/sh -c 'echo hi' ? /me too. Okay, okay, your wish is my command ;-) emeric@longspeak:~$ ldd /usr/lib/klibc/bin/sh not a dynamic executable The above seems to be the most recent message in the bug log, other than a "me too" a few weeks ago. Has there been any progress towards getting this resolved? Unless I'm missing something, it sounds like a fairly large blocker to using Debian on ia64. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/01feac3ad06b8150c9d541461d7d3...@mail.adsl.funky-badger.org
Bug#638068: ia64 qualification for Wheezy
On Mon, 2012-05-28 at 22:20 +1000, Aníbal Monsalve Salazar wrote: > On Mon, May 28, 2012 at 01:05:58PM +0100, Adam D. Barratt wrote: > >On 23.05.2012 19:31, Adam D. Barratt wrote: > >>On Wed, 2012-05-16 at 13:19 +0100, Adam D. Barratt wrote: > >>>With the sound of the ever approaching freeze ringing loudly in our > >>>ears, we're (somewhat belatedly) looking at finalising the list of > >>>release architectures for the Wheezy release. [...] > >One thing that was bought to my attention in private mail is #638068 > >in initramfs-tools. > > I'm happy to test a possible fix for #638068 on my ia64 machines. > > Does someone have a hint about fixing it? Has there been any progress on that? It's not hugely useful to ship Debian on an architecture where one needs to hack the initrd in order to make machines boot. :-/ Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1339528545.31672.6.ca...@jacala.jungle.funky-badger.org
Re: Preparation for d-i beta 1
On 26.06.2012 16:35, Cyril Brulebois wrote: Cyril Brulebois (25/06/2012): - udeb freeze. debian-release, please put that back into place. Thanks already! Done. As discussed, I've enabled all of the blocks, including those in the "can be handled by britney" category. If people moan, I'll know where to point them. ;-) Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d60eed171d0b8385162433d8ff62e...@mail.adsl.funky-badger.org
Re: Preparation for d-i beta 1
On Wed, 2012-06-27 at 17:59 +0100, Ben Hutchings wrote: > On Tue, Jun 26, 2012 at 05:07:50PM +0100, Adam D. Barratt wrote: > > On 26.06.2012 16:35, Cyril Brulebois wrote: > > >Cyril Brulebois (25/06/2012): > > >> - udeb freeze. > > > > > >debian-release, please put that back into place. Thanks already! > > > > Done. > > > > As discussed, I've enabled all of the blocks, including those in the > > "can be handled by britney" category. If people moan, I'll know > > where to point them. ;-) [...] > So presumably there will be no testing migration of linux until after > d-i beta 1? I'm just wondering whether it's worth uploading right now > to fix the sparc FTBFS or whether this should be left until we have > other substantial changes. [mentioned on IRC, but for the record] The grand plan[tm] for beta1 includes a kernel migration, so having it build everywhere soon would be appreciated :-) Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1340821131.23069.3.ca...@jacala.jungle.funky-badger.org
6.0.7 planning
Hi, We're somewhat overdue with the next Squeeze point release (6.0.7) and it'd be good to get it done before the wheezy release, so that we can pull in some upgrade fixes. As an opening gambit, some proposed dates, all of which appear to currently work for me: February 23rd March 2nd March 9th Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1360513538.7444.29.ca...@jacala.jungle.funky-badger.org
Re: 6.0.7 planning
On 12.02.2013 13:08, Philipp Kern wrote: On Sun, Feb 10, 2013 at 04:25:38PM +, Adam D. Barratt wrote: We're somewhat overdue with the next Squeeze point release (6.0.7) and it'd be good to get it done before the wheezy release, so that we can pull in some upgrade fixes. As an opening gambit, some proposed dates, all of which appear to currently work for me: February 23rd March 2nd March 9th These all work for me. I will be sort of offline, however, from February 14th to (including) 17th, which looks like the preparation range for the first date. I think we've heard from everyone now, with there being a preference for the 23rd from the CD perspective. That means we'd be looking at closing p-u over the upcoming weekend, i.e. the 16 / 17th. That should be doable, if a little tighter than I'd normally like, assuming we can get the kernel upload done / accepted in time, to avoid last minute panic over lkdi / d-i builds; CCing -kernel for opinions. Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/433f65e1164f2af26d2c5d7e94856...@mail.adsl.funky-badger.org
Re: 6.0.7 planning
On 12.02.2013 02:15, Ben Hutchings wrote: One or other of us will then need to merge the squeeze-security branch into squeeze and upload -48 in time for the point release. Is there an ETA for that? Sorry for chasing, but if we're going to go for the 23rd (which is looking likely atm) we'd be looking at closing p-u-NEW over the weekend and could really do with announcing that asap. (So "it'll be uploaded to p-u-NEW over the weekend" should be fine, as we can then plan around that.) Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/bbb3e46ad36b298be8c82cca0b02a...@mail.adsl.funky-badger.org
