Re: console-tools vs kbd, fix listed in bug report?!
- To: email@example.com,
- Cc: firstname.lastname@example.org
- Subject: Re: console-tools vs kbd, fix listed in bug report?!
- From: Sam Vilain <email@example.com>
- Date: Thu, 4 Jan 2001 19:55:02 +0000
- Message-id: <E14EGTW-0001QEfirstname.lastname@example.org>
- In-reply-to: <E14Cmh6-0000Zzemail@example.com>
- References: <E14Cmh6-0000Zzfirstname.lastname@example.org>
As pointed out to me, bug #71768 has a workaround to my problem listed
in it. However, I find it quite appalling that a fix involving a one
character change to a source file, where the fix has been listed in
the bug report has not been pushed through, given its age.
The console-tools package has a huge number of bugs associated with
it, and given that it's a base package, that's not so good.
Is it possible for maintainers to share packages, perhaps? Then these
small things can get sorted quicker. Personally, I'd just love it if
the entire Debian core system was in CVS, with upstream updates being
merged in. This would also give the advantage of being able to do
OpenBSD style fixing of code; eg, one person finds a particular type
of bad coding practice, looks for it and fixes it throughout the code
base, and mails the authors to let them know about that bad coding
Or perhaps the bug tracking system just needs some rework to be a bit
nicer. I'm sure some people here have used Remedy's Action Response
System in a reasonably large environment, so why not pick it's best
features and stick them in; like some decent querying capabilities and
borrow some of its interface. Stick in the ability to assign bugs to
other people. Perhaps even a standalone client. Maybe even get some
"customer service" going, and draw up some guidelines for how long it
should take for bugs to be responded to, etc.
On Sun, 31 Dec 2000 17:54:56 +0000
Sam Vilain <email@example.com> wrote:
> Hi there,
> I'm using a non-standard keyboard that sends odd scancodes. I wrote
> a startup script that does a whole heap of "setkeycodes" commands,
> but I've found that the version of "setkeycodes" in the
> console-tools package does not work with kernel version 2.2+. The
> one with the "kbd" package works fine, but "kbd" seems to be a
> somewhat deprecated package.
> I found a bug relating to this; entitled "console-tools: setkeycode
> does not use right IOCTL", which could be it:
> And one entitled "setkeycodes completely broken";
> Is there any news on a fix?
Sam Vilain, firstname.lastname@example.org WWW: http://sam.vilain.net/
GPG public key: http://sam.vilain.net/sam.asc