Your message dated Sun, 21 Feb 2016 11:04:18 +0000 with message-id <20160221110418.GT6200@betterave.cristau.org> and subject line Re: Bug#756986: wheezy-pu: package debian-lan-config/0.13~bpo70+5 has caused the Debian Bug report #756986, regarding wheezy-pu: package debian-lan-config/0.13~bpo70+5 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.) -- 756986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756986 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: wheezy-pu: package debian-lan-config/0.13~bpo70+5
- From: "Andreas B. Mundt" <andi.mundt@web.de>
- Date: Mon, 04 Aug 2014 10:19:00 +0200
- Message-id: <20140804081900.3191.93217.reportbug@flashgordon>
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian.org@packages.debian.org Usertags: pu Dear release managers! I would like to ask for the permission to upload and the inclusion of the latest debian-lan-config package in the upcoming wheezy point release. The debian-lan-config package is kind of special, as it contains no 'program' in itself, but instructions (in a FAI config space) on how to build a composed system within debian, cf. <URL:https://wiki.debian.org/DebianLAN>. The package did not make it for the wheezy freeze and I provided it via backports after the release. However, with further improvements, it got less and less justified to use backports, as the wheezy package is not a strict 'backport' of the version in jessie, which is of course targeted at jessie. Content and history of the package is available here: <URL:http://anonscm.debian.org/cgit/collab-maint/debian-lan.git/log/?h=wheezy> The package should not pose any risk to the distribution, as it needs to be 'activated' manually to do anything at all. To get an idea, cf. <URL:http://anonscm.debian.org/cgit/collab-maint/debian-lan.git/tree/debian/README.Debian?h=wheezy>. Best regards and thanks for your consideration, Andi -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (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: "Andreas B. Mundt" <andi.mundt@web.de>, 756986-done@bugs.debian.org
- Subject: Re: Bug#756986: wheezy-pu: package debian-lan-config/0.13~bpo70+5
- From: Julien Cristau <jcristau@debian.org>
- Date: Sun, 21 Feb 2016 11:04:18 +0000
- Message-id: <20160221110418.GT6200@betterave.cristau.org>
- In-reply-to: <20140804081900.3191.93217.reportbug@flashgordon>
- References: <20140804081900.3191.93217.reportbug@flashgordon>
On Mon, Aug 4, 2014 at 10:19:00 +0200, Andreas B. Mundt wrote: > Package: release.debian.org > Severity: normal > Tags: wheezy > User: release.debian.org@packages.debian.org > Usertags: pu > > > Dear release managers! > > I would like to ask for the permission to upload and the inclusion of > the latest debian-lan-config package in the upcoming wheezy point > release. > We're not normally adding completely new packages post-release, and even less so now wheezy is almost EOL. Closing. Cheers, JulienAttachment: signature.asc
Description: PGP signature
--- End Message ---