Your message dated Wed, 14 Sep 2005 13:02:21 -0500 (CDT)
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Nov 2003 13:56:47 +0000
>From [EMAIL PROTECTED] Tue Nov 11 07:56:45 2003
Return-path: <[EMAIL PROTECTED]>
Received: from gluck.debian.org [192.25.206.10]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AJZ0e-0001oe-00; Tue, 11 Nov 2003 07:56:44 -0600
Received: from mail.uni-kl.de [131.246.137.52]
by gluck.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AJZ0e-0004QH-00; Tue, 11 Nov 2003 06:56:44 -0700
Received: from mailgate1.uni-kl.de (mailgate1.uni-kl.de [131.246.120.5])
by mail.uni-kl.de (8.12.8/8.12.8) with ESMTP id hABDufrk006127;
Tue, 11 Nov 2003 14:56:42 +0100 (MET)
Received: from mailinf.rhrk.uni-kl.de (mailinf.rhrk.uni-kl.de [131.246.137.54])
by mailgate1.uni-kl.de (8.12.10/8.12.10) with ESMTP id hABDufQo019383;
Tue, 11 Nov 2003 14:56:41 +0100
Received: from domino.informatik.uni-kl.de ([EMAIL PROTECTED] [131.246.161.19])
by mailinf.rhrk.uni-kl.de (8.12.6/8.12.6) with ESMTP id hABDufqi010625;
Tue, 11 Nov 2003 13:56:41 GMT
Received: from zombie.inka.de (rotes255.wohnheim.uni-kl.de [131.246.178.65])
by domino.informatik.uni-kl.de (8.11.7/8.11.6) with ESMTP id
hABDuf925183;
Tue, 11 Nov 2003 14:56:41 +0100 (MET)
Received: from inet by zombie.inka.de with local (Exim 4.24)
id 1AJZ0G-0007IJ-Bo; Tue, 11 Nov 2003 14:56:20 +0100
Date: Tue, 11 Nov 2003 14:56:20 +0100
From: Eduard Bloch <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Sven Luther <[EMAIL PROTECTED]>
Subject: ITP: debian-kernel-ng -- new packagement base for system kernels
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Sender: Eduard Bloch <[EMAIL PROTECTED]>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mail.uni-kl.de id
hABDufrk006127
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-9.2 required=4.0
tests=BAYES_20,HAS_PACKAGE,QUOTED_EMAIL_TEXT
version=2.53-bugs.debian.org_2003_11_9
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_9
(1.174.2.15-2003-03-30-exp)
Package: wnpp
Severity: wishlist
Well, I will make this an ITP before another one under Millan drug gets
the idea to take the package names away.
Package: debian-kernel-ng (any may be others)
Upstream Author: debian-kernel@lists.debian.org (ML needs to be created f=
irst)
Description: infrastructure for creation and installation of System kerne=
ls
debian-kernel should become a project to extend and improve the current
toolchain around the kernel package installation and creation. It will
combine ideas from http://debian.linuxwiki.de/DebianKernel/Plan with
that listed below. The project should become a separate mailing list. It
has already be requested in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D219826 and I hope to
achieve agreement with the submitter of #219826.
----- Forwarded message from Eduard Bloch <[EMAIL PROTECTED]> -----
Date: Mon, 10 Nov 2003 17:11:45 +0100
From: Eduard Bloch <[EMAIL PROTECTED]>
Subject: create new Debian-Kernel project (was: ITP: linux -- Linux 2.4 k=
ernel)
To: debian-devel@lists.debian.org, [EMAIL PROTECTED]
Mail-Followup-To: debian-devel@lists.debian.org, [EMAIL PROTECTED]
#include <hallo.h>
* Jamie Wilkinson [Mon, Nov 10 2003, 06:54:22PM]:
> >The fact of the too generic package name was mentioned before within
> >other arguments against your "linux" package. IIRC you prefered not to
> >answer to it but refered to an URL which did not contain the answers.
>=20
> 'linux' is a perfect name for the package. The tarballs contain that v=
ery
> name.
Note that the name is choosen not only to attract the user, but also to
catch that who blindly use "apt-get source linux". The user wouldn't get
the well-known and good kernel-source packages but something which is
under control of Robert. Further, what they would get is not a clean
source but something with debian/ dir inside which would confuse
make-kpkg. I would not mind if he had called it "linux-rmh" or such.
> >> 2) I use the upstream name. If you don't like it, bitch upstream.
> >
> >Sorry, how much did you drink to find an answer like this one? If Linu=
s
> >changes the package name (which is unlikely to happen ;)), I am sure y=
ou
> >would rename your ITP to follow him.
>=20
> Are you implying that you make up names for the software that you packa=
ge,
> rather than use the name given to it by upstream? I believe you don't.
Ah, that is a good base to start a discussion. Of course it is better to
keep the upstreams name but make exceptions if they are too generic, to
confusing or to offensive (though we did already accept such ones, eg.
"pornview" ;)).
> Given that there's a possibility that Debian will include non-linux ker=
nels
> in the future. In that case, calling the linux kernel package
> 'kernel-image' doesn't give a lot of room for the other kernels to live=
in.
> Calling the package 'linux' makes it pretty clear which software it is
> packaging.
I would not call any package "linux" or "freebsd", not even in the
source package name. In fact, for a future development of debian-kernel
packaging, I have written something down few days ago.
...=20
# create debian-kernel mailing list, found a new project called
# debian-kernel alias DK. Keep the project files in a project-internal
# repository unless the stuff is mature enough to see the daylight of Si=
d,
# post-sarge.
In addition to the others plan on the mentioned Wiki page, we need
following packages:
linux-kernel-setup: setup utility for the Linux kernel packages created
by the debian-kernel project
(s/linux/Hurd/ or *BSD)
linux-initrd-builder: adapted version of initrd-tools; supposed to
work with d-k kernel packages but not limited to t=
hem
=20
packages following the following naming strategy:
linix-kernel-source-2.4.XY: basicaly the upstream source
=20
lk-patch-essential-2.4.XY: hot fixes like for security issues,
compiling problems etc.
=20
lk-patch-recommended-2.4.XY: important but optional patches like
initrd-on-cramfs fix <discuss that>,
vesafb-as-module, bigphysarea...
lk-patch-suggested-2.4.XY: sensible patches but not sensible for
everyone: ipsec backports,
dk-meta-linux-2.4.23: meta package with dependencies/conflicts
to keep the *-2.4.XY packages above in =
sync
The binary kernel packages would not be longer distributed with
auto-installing script and all the modules inside. Instead, they would us=
e
the <linux|...>-kernel-setup utility. No longer one big package, but crea=
te:
linux-kernel-$KVERS: meta package with strong dependency on lki-$KVERS an=
d
maybe some modules packages, see below.
linux-kernel-image-$KVERS: the image itself, including System.map, config=
, etc.
linux-modules-general-$KVERS: all the general modules, including common
componentes like scsi-hd/cd support used by
usb/firewire/... drivers
linux-modules-ide-$KVERS: includes all the low-level ide drivers
linux-modules-scsi-$KVERS: same for scsi
linux-modules-usb-...: ...
linux-modules-firewire-...: ...
linux-modules-multimedia-...: sound drivers, v4l, joystick drivers, etc.
<end-of-brainstorming>
I am open for discussions about that.
MfG,
Eduard.
--=20
Was die neuen Unwissenden holen m=FCssen:
Siemens-Lufthaken
--=20
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
.org
----- End forwarded message -----
--=20
Wie man sein Kind nicht nennen sollte:=20
Mel Sack=20
---------------------------------------
Received: (at 220210-done) by bugs.debian.org; 14 Sep 2005 18:02:27 +0000
>From [EMAIL PROTECTED] Wed Sep 14 11:02:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-201-129-37-187.prod-infinitum.com.mx (cerdita.damog.net)
[201.129.37.187]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EFbaS-0000vp-00; Wed, 14 Sep 2005 11:02:24 -0700
Received: by cerdita.damog.net (Postfix, from userid 1000)
id 11576107855; Wed, 14 Sep 2005 13:02:21 -0500 (CDT)
To: [EMAIL PROTECTED]
Subject: WNPP bug closed
Cc: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Date: Wed, 14 Sep 2005 13:02:21 -0500 (CDT)
From: [EMAIL PROTECTED] (David Moreno Garza)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 270
Hello,
This an automatic message sent to owners of inactive ITPs on the Debian
Bug Tracking System.
I'm closing your bug because of the following reasons:
- It is older than 600 days old.
- It haven't had any activity recently.
- The amount of ITPs on the Debian BTS is huge and we need to
clean up a bit the place.
If your bug shouldn't be closed, you are more than free to re-open it,
for example, if you still have intentions to package the software in
question or the like. To re-open it, you simply have to mail
[EMAIL PROTECTED] with a body text like this:
reopen 123456
thanks bts
Replacing '123456' for the number of your ITP bug. The subject of the
mail is ignored. Or if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.
This is the first mass wnpp closing that will be done. The next close
will be done on inactive ITPs older than 450 days and finally, the
ones older than 365 days (an automatic script will close *inactive*
ITPs when they reach one year old).
A similar process will be applied to the RFP wnpp bugs in the next
days.
Thanks for your cooperation,
David Moreno Garza <[EMAIL PROTECTED]>.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
