Bug#596670: unblock: perdition/1.19~rc3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package perdition Perdition 1.19~rc4-1 includes several important fixes and I would like it considered for inclusion in Squeeze. As it coincides with an upstream release (1.19-rc4) it also contains one or two (minor) changes that don't strictly meet the criteria for the freeze. All such changes are minor. And are mainly changes that were committed upstream before the freeze hardened. As both the upstream and Debian maintainer I would be most grateful if these could be let through. An annotated list of all the changes between 1.19~rc3-1 (= upstream 1.19-rc3) and 1.19~rc4-1 (= upstream 1.19-rc4) is as follows. The upstream changelog can be found at http://hg.vergenet.net/perdition/perdition/ changeset: 871:c232fe1163d0 tag: v1.19-rc4 user:Simon Horman ho...@verge.net.au date:Mon Sep 13 16:12:52 2010 +0900 summary: Perdition 1.19-rc4 This simply updates configure.ac, debian/changelog and perdition.spec.in. changeset: 870:11a92ae20bcc user:Simon Horman ho...@verge.net.au date:Mon Sep 13 16:09:55 2010 +0900 summary: rpm: binary dependency on libvanessa_socket2 (= 0.0.12) From a Debian point of view, this is a source-only change although it relates to Debian bug #592459. changeset: 869:055be8c2db1f user:Simon Horman ho...@verge.net.au date:Mon Sep 13 16:06:31 2010 +0900 summary: Debian: binary dependency on libvanessa-socket2 (= 0.0.12) This relates to Debian bug #592459 changeset: 868:3981109ea6ba user:Simon Horman ho...@verge.net.au date:Mon Sep 13 16:01:09 2010 +0900 summary: Debian: There is a typo in the changelog for 1.19~rc3-2 This relates to Debian bug #592459 changeset: 867:86df56cded53 user:Christophe Ségui christophe.se...@math.univ-toulouse.fr date:Thu Sep 09 21:34:24 2010 +0900 summary: Correct parsing of NIS map This is a bug that I believe is worthy of fixing for Squeeze changeset: 866:975801678a3d user:Simon Horman ho...@verge.net.au date:Fri Aug 20 17:13:22 2010 +0900 summary: perdition(8): Clean up introduction This is a documentation change changeset: 857:e17ec8401d34 tag: debian-1.19~rc3-2 user:Simon Horman ho...@verge.net.au date:Tue Aug 17 16:18:08 2010 +0900 summary: Debian: Update standards version from 3.9.0 to 3.9.1 Self explanatory, I realise that strictly this isn't freeze material, but it was committed upstream before the freeze became harder. changeset: 856:baeb40f36e7d parent: 849:2493da66045b user:Simon Horman ho...@verge.net.au date:Tue Aug 17 15:45:13 2010 +0900 summary: Debian: BuildDepend on libvanessa-logger-dev (= 0.0.12) This was included in 1.19~rc3-2. There is some discussion of it in Debian bug #592459. It is needed in order for 1.19-rc3 and rc4 to compile. changeset: 855:263c96021ef9 user:Simon Horman ho...@verge.net.au date:Tue Aug 03 09:56:05 2010 +0900 summary: Allocate enough space for fromv This is a bug that I believe is worthy of fixing for Squeeze. The bug is a segmentation fault on start bug for certain configuration combinations. changeset: 854:aeff92473a55 user:Simon Horman ho...@verge.net.au date:Sat Jul 31 14:23:46 2010 +0900 summary: Fix build failure if pam libraries aren't installed This doesn't effect Debian as BuildDependencies ensure that pam is always installed at build time. As such, I realise that strictly this isn't freeze material, but it was committed upstream before the freeze became harder. changeset: 853:2178a5528029 user:Joachim Sehlstedt u...@newstyledata.net date:Fri Jul 30 16:02:17 2010 +0900 summary: Load configuration file before setting logger options This is a bug that I believe is worthy of fixing for Squeeze. The problem is that for some configuration parameters may be ignored. changeset: 852:1718ccb586e9 user:Simon Horman ho...@verge.net.au date:Fri Jul 30 12:08:30 2010 +0900 summary: Don't assign the result of SSLv23_method() This removes a build warning. As such, I realise that strictly this isn't freeze material, but it was committed upstream before the freeze became harder. changeset: 851:d4ec17993901 user:Joachim Sehlstedt u...@newstyledata.net date:Fri Jul 30 11:54:28 2010 +0900 summary: Document --managesieve_capability in man page This is a documentation change. unblock perdition/1.19~rc4-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (190, 'unstable') Architecture: i386 (i686)
Re: Bringing the 2.6.13 (and beyond) kernel to sid, solving ramdisk generations issues and stuff.
On Sat, Oct 15, 2005 at 01:13:31PM +0200, Sven Luther wrote: On Sat, Oct 15, 2005 at 01:07:38PM +0200, Bastian Blank wrote: On Sat, Oct 15, 2005 at 12:19:04PM +0200, Sven Luther wrote: the plan for solving the ramdisk issues is done in three stages, current svn 2.6.13 packages implement stage 1, i have patches for both initrd-tools and initramfs-tools in svn, and the yaird folk adapted it for yaird, so we may go ahead and upload those nextly (if it could be in by monday, that would be nice). I will work on the last stage, the kernel-package patch, this WE, and do an NMU since Manoj is unavailable for the next times and asked us to do so. initramfs-tools waits for mklibs. Well, we can go ahead with yaird for now, what is the mklibs issue ? Or can mklibs be disabled for now ? Broken but being worked on : s390 Broken gcc or inline assembly, the IBM people expect the later. Hope that I get a fix from them at monday. Ok, as said, if not, it can wait for -3. The other issue is that 2.6.14 is scheduled for release in the not so distant future, so we may skip uploading .13-3 to unstable and go for .14-1 directly, depending on status of newly introduced breakage in .14 and such. I vote for the later. Hehe, but this does suppose we create now another branch and start porting the patches and configs, i see nobody volunteering to do that. I vote for not creating another breach. I vote for moving to .14 (or some -rc variant thereof). Its unlikelty to make much difference on the initrd front and saves duplication of effort that is inherent in the more branches approach. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 kernel packaging
On Mon, Jun 20, 2005 at 11:11:34AM -0400, Jurij Smakov wrote: On Mon, 20 Jun 2005, Horms wrote: Excellent. Kernels outside the d-k repo are already out in the cold. I don't see that moving forward with this makes their situation any better, or any worse. Common source package currently provides linux-source, linux-tree and linux-patch binary packages with functionality equivalent to corresponding kernel- packages. So the arches not controlled by d-k team would need to just change their build-deps. Ok, understood. I hadn't thought about that, but I don't think that is an unreasonable inconvenience for non d-k team package maintainers. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ABI-changing kernel security fixes for sarge
Hi, I am finally nearing the bottom of my todo list for the up and coming release of kernel-source-2.4.27 2.4.27-9. And to date, the only ABI change I have is for CAN-2005-0449, as per my mail yesterday. http://lists.debian.org/debian-boot/2005/03/msg00689.html To the best of my knowledge 2.6.8 is in the same position - I worked with Andres Salomon on the fix that went in there, and the fix that was pulled out, and they are the same fixes as for 2.4.27. I am quite comfortable with doing a post-sarge security update for this if the d-i team feels this is the best approach. Though it is a remote exploit, and that needs to be taken into due consideration. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing Sarge on Alpha
On Thu, Jul 22, 2004 at 12:15:41PM +0900, Horms wrote: On Wed, Jul 21, 2004 at 02:07:02PM -0700, Steve Langasek wrote: Hi Horms, On Wed, Jul 21, 2004 at 09:14:34PM +0900, Horms wrote: On Wed, Jul 21, 2004 at 01:50:09PM +0200, maximilian attems wrote: it was a pci fix patch from Herbert Xu that b0rks, hch has thrown it out for 2.6.7-1. you may want to look at #253787. Thanks, that does sill seem to be present. I will rectify this in the SVN tree ASAP and it should be fixed in the next release, likely kernel-source-2.4.26-4. Thanks for the quick response to this issue. What is the expected timeline for this kernel-source package to be uploaded? If there are no objections from other members of the kernel team I can have this ready today or tomorrow. (Likely tomorrow as I have a full day today and I don't want to rush and make some silly mistake.) What is the expected timeline for kernel-image packages built from these sources to be uploaded? I can make i386 kernel-images available at the same time as the kernel-source. I don't handle other architectures so I can't speak for them. It didn't atke me as long as I expected to do my other chores and get the new packages ready. I have put them _tempoarily_ up on http://debian.vergenet.net/ There is a new kernel-source-2.4.26 package, 2.4.26-4 and a new kernel-image-2.4.26-i386 package, also 2.4.26-4. There are no changes to the kernel-image package, other than building it against the new kernel-source. The change log for the kernel-source package is: * Fix stack allocation in crypt(). Patch by Herbert Xu (closes: #257120) . crypto/cipher.c * Reversed patch to PCI initialisation code on Alpha Patch by Herbert Xu, Steve Langasek (closes: #253787) . arch/alpha/kernel/core_cia.c If there are no objections from the kernel-team I plan to upload these tomorrow. Feel free to test, build other binary packages etc... I do not plan to make any changes to this unless something _bad_ crops up. But It would be probably best not to upload a kernel-image package that is built from kernel-source-2.4.26-2.4.26-4, just in case there is a last minute change. -- Horms
Re: Installing Sarge on Alpha
On Wed, Jul 21, 2004 at 02:07:02PM -0700, Steve Langasek wrote: Hi Horms, On Wed, Jul 21, 2004 at 09:14:34PM +0900, Horms wrote: On Wed, Jul 21, 2004 at 01:50:09PM +0200, maximilian attems wrote: it was a pci fix patch from Herbert Xu that b0rks, hch has thrown it out for 2.6.7-1. you may want to look at #253787. Thanks, that does sill seem to be present. I will rectify this in the SVN tree ASAP and it should be fixed in the next release, likely kernel-source-2.4.26-4. Thanks for the quick response to this issue. What is the expected timeline for this kernel-source package to be uploaded? If there are no objections from other members of the kernel team I can have this ready today or tomorrow. (Likely tomorrow as I have a full day today and I don't want to rush and make some silly mistake.) What is the expected timeline for kernel-image packages built from these sources to be uploaded? I can make i386 kernel-images available at the same time as the kernel-source. I don't handle other architectures so I can't speak for them. I'm sorry that I didn't realize this bug had been closed. The release team is currently working on putting together an aggressive schedule for the sarge freeze, and there's agreement that this is a bug that needs to be fixed before debian-installer can be frozen. To meet our current tentative release schedule, we need a fixed kernel-image-2.4.26-1-generic to reach unstable by 31July. Do you have time for the necessary uploads? If not, is there anything I can do to help? I would need some hand-holding to get up to speed on exactly how kernel packages are prepared, but I'm happy to help with alpha builds of the actual kernel-images, if nothing else. Including this bug, I am only aware of 3 bugs against kernel-source-2.4.26 of particular concern. (that does not mean I won't look into the other bugs against the package, just that they are not a priority) 253787 (this bug): Fix pending as per this discussion. 257120 (ipsec):Fix in SVN already 257001 (m68k): m68k is known to be higly problematic on 2.4 After some discussion on debian-kernel I plan to mark it as wontfix. If you are aware of other problems please send them to debian-kernel. I will endevour to look into them ASAP. -- Horms
