[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#304513: marked as done (RFP: kernel-patch-v4l2-2.4 -- video4linux2 patch against 2.4 kernels)

Your message dated Sat, 08 Jul 2006 11:59:59 -0600
with message-id <E1FzH5z-0007aP-1E@merkel.debian.org>
and subject line WNPP bug closing
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)
--- Begin Message --- 
Package: wnpp

* Package name    : kernel-patch-v4l2-2.4
  Version         : 2.4.26-1
  Upstream Author : Gerd Knorr <kraxel@bytesex.org>
* URL             : http://dl.bytesex.org/patches/
* License         : GPL
  Description     : video4linux2 patch against 2.4 kernels


For the reason that I need to use another module that is only existing 
for 2.4 kernels I'm stuck with 2.4 on one system.

I do not know how high the interest is in having this in Debian, but my
intention is to give creating packages for myself a try. I am however
already a bit stuck.

Is there a guide somewhere on how to create kernel-patch packages? There
is nothing on it in the developers reference as far as I can see,
neither did I find anything in the policy manual, and google turns out
fruit less as well.

Of course a kernel-patch package should place it's diffs in
/usr/src/kernel-patches/diffs/ and have some appropriate apply and
unapply scripts, but what are the exact requirements of those scripts?

Any help would be appreciated.
--
/Martin

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Hello,

This is an automatic mail sent to close the RFP you have reported or 
are involved with.

Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

reopen 304513
thanks bts

Further comments on the work done in the bug sent to
304513@bugs.debian.org would be truly welcomed.
Anyway, 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: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>.

--- End Message ---
Reply to: