Your message dated Sat, 1 Dec 2012 12:01:26 +0100 with message-id <20121201110126.GD5634@radis.cristau.org> and subject line Re: Bug#683792: unblock: libseccomp/1.0.0-1 has caused the Debian Bug report #683792, regarding unblock: libseccomp/1.0.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 683792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683792 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: libseccomp/1.0.0-1
- From: Kees Cook <kees@debian.org>
- Date: Fri, 03 Aug 2012 17:35:31 -0700
- Message-id: <20120804003531.24817.68767.reportbug@localhost6.localdomain6>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: freeze-exception Please unblock package libseccomp libseccomp just released their 1.0.0 version which has ABI changes over the earlier 0.1.0 release. This is a new library and no packages in Debian are currently build-depending on libseccomp, so the risk to the freeze is minimal. I'd like to have this 1.0.0 version in Debian for easier development work for people wanting to use libseccomp going forward. unblock libseccomp/1.0.0-1 -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-26-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: Kees Cook <kees@debian.org>, 683792-done@bugs.debian.org
- Subject: Re: Bug#683792: unblock: libseccomp/1.0.0-1
- From: Julien Cristau <jcristau@debian.org>
- Date: Sat, 1 Dec 2012 12:01:26 +0100
- Message-id: <20121201110126.GD5634@radis.cristau.org>
- In-reply-to: <20120915185931.GU5308@radis.cristau.org>
- References: <20120804003531.24817.68767.reportbug@localhost6.localdomain6> <20120915185931.GU5308@radis.cristau.org>
On Sat, Sep 15, 2012 at 20:59:31 +0200, Julien Cristau wrote: > On Fri, Aug 3, 2012 at 17:35:31 -0700, Kees Cook wrote: > > > Package: release.debian.org > > Severity: normal > > User: release.debian.org@packages.debian.org > > Usertags: freeze-exception > > > > Please unblock package libseccomp > > > > libseccomp just released their 1.0.0 version which has ABI changes over the > > earlier 0.1.0 release. This is a new library and no packages in Debian are > > currently build-depending on libseccomp, so the risk to the freeze is minimal. > > > > I'd like to have this 1.0.0 version in Debian for easier development work > > for people wanting to use libseccomp going forward. > > > Or we could just remove it from wheezy, if nothing's currently using it > in the distro... > I've done that, seeing how there was no followup and the 1.0.0 version is still in new. Newer libseccomp can hopefully live in wheezy-backports. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---