Your message dated Mon, 14 Apr 2008 23:21:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line rtlinux has been removed from Debian, closing #297712
has caused the Debian Bug report #297712,
regarding rtlinux doesn't seem prepared for kernel-package
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 [EMAIL PROTECTED]
immediately.)
--
297712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=297712
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: rtlinux
Version: 3.1pre3-2
One of the reasons for using Debian is the lack of messyness when having
everything installed with packages, including kernel images.
For normal kernels, make-kpkg from kernel-package makes a terrific job
at creating new kernel-image packages with friends.
In a perfect world it should be possible to easily create those packages
for RTLinux patched kernels too. However the README.Debian gives no help
on how it could be done.
Although I don't fully understand what is done when a rtlinux patch is
applied to the kernel I assume it messes to much with the core internals
to be enough for RTLinux to provide a /usr/src/modules/ directory, but
the modules should be able to build from such a directory?
Creating a simple shell script to check that kernel version and patch
versions correspond would help. And after that patching the kernel to
produce a tree suitable to run make-kpkg in.
I'm willing to help. Please tell me how.
--
/Martin
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 3.1pre3-3+rm
The rtlinux package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/365717 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
Barry deFreese
--- End Message ---
