kernel-image-2.4.22-1-k7 apm and usb-uhci problems

[Marcel Kolaja]

Hello,

I have upgraded kernel to kernel-image-2.4.22-1-k7 on my Sarge. But
I found problems with apm and usb-uhci modules. The modules cannot be
loaded into the kernel. Messages from bootlogd:

Sat Sep 27 20:08:47 2003: Loading modules: parport parport_pc apm 
/lib/modules/2.4.22-1-k7/kernel/arch/i386/kernel/apm.o: init_module: No such 
device
Sat Sep 27 20:08:47 2003: Hint: insmod errors can be caused by incorrect module 
parameters, including invalid IO or IRQ parameters.
Sat Sep 27 20:08:47 2003:   You may find more information in syslog or the 
output from dmesg
Sat Sep 27 20:08:47 2003: 
/lib/modules/2.4.22-1-k7/kernel/arch/i386/kernel/apm.o: insmod 
/lib/modules/2.4.22-1-k7/kernel/arch/i386/kernel/apm.o failed
Sat Sep 27 20:08:47 2003: 
/lib/modules/2.4.22-1-k7/kernel/arch/i386/kernel/apm.o: insmod apm failed

Sat Sep 27 20:08:51 2003: Loading usb-uhci module.
Sat Sep 27 20:08:51 2003: 
/lib/modules/2.4.22-1-k7/kernel/drivers/usb/host/usb-uhci.o: init_module: No 
such device
Sat Sep 27 20:08:51 2003: Hint: insmod errors can be caused by incorrect module 
parameters, including invalid IO or IRQ parameters.
Sat Sep 27 20:08:51 2003:   You may find more information in syslog or the 
output from dmesg
Sat Sep 27 20:08:51 2003: 
/lib/modules/2.4.22-1-k7/kernel/drivers/usb/host/usb-uhci.o: insmod 
/lib/modules/2.4.22-1-k7/kernel/drivers/usb/host/usb-uhci.o failedSat Sep 27 
20:08:51 2003: /lib/modules/2.4.22-1-k7/kernel/drivers/usb/host/usb-uhci.o: 
insmod usb-uhci failed

I tried to load the uhci module, but it cannot be loaded too. With
kernel-image-2.4.21-4-k7 both apm and usb-uhci work fine. I guess this
behavior of 2.4.22-1-k7 is a bug. Shall I file a bug report?


Regards,

Marcel Kolaja
Debian GNU/Linux Power User http://www.debian.org/
--
"MS is a lot better at making money than it is at making good operating
systems."   -- Linus Torvalds

[VACATION] .au Sydney 29.9(Today)/30.9

[Florian Lohoff]

Hi,
i am in Sydney for Today and Tomorrow - So if any Debian enthusiasts is
willing to go out for a Beer or Keysigning ...

Flo
-- 
Florian Lohoff  [EMAIL PROTECTED] +49-171-2280134
Heisenberg may have been here.


pgpszBaWXKKTM.pgp
Description: PGP signature

Bug#213223: ITP: ogg-vorbis-header-perl -- An interface to Ogg Vorbis information and comments

[Amit Shah]

Package: wnpp
Version: unavailable; reported 2003-09-29
Severity: wishlist

* Package name: ogg-vorbis-header-perl
  Version : 0.03
  Upstream Author : Dan Pemstein <[EMAIL PROTECTED]>
* URL : 
http://search.cpan.org/CPAN/authors/id/D/DB/DBP/Ogg-Vorbis-Header-0.03.tar.gz
* License : GPL
  Description : An interface to Ogg Vorbis information and comments

 This module presents an object-oriented interface to Ogg Vorbis files
 which allows user to view Vorbis info and comments and to modify or
 add comments.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux magrathea 2.6.0-test5 #45 Mon Sep 22 13:54:23 IST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Re: x48

[Uwe Steinmann]

On Thu, Sep 25, 2003 at 07:38:28AM -0600, Hans Fugal wrote:
> Does anyone remember x48? It's an HP48 CPU emulator. It used to be
> packaged for debian, but was orphaned.
> 
> In order to do any emulation it needs a ROM, which you can download from
> your HP48 over the serial line. You can also get ROMs from [1]. 
> "HP graciously began allowing this to be downloaded in mid-2000." [1]
> I don't know exactly what this means by way of copyright and/or license,
> and I have emailed the webmaster of hpcalc.org to see if he knows any
> more details. I imagine ROMs won't be distributable. x48 itself is under
> the GPL.
> 
> x48 hasn't been maintained for about 4 years now, and didn't work very
> well on modern processors when I picked up the source (timing issues).
> But Eddie Dost, the original author, has graciously worked with me to
> get those issues resolved and it now works like a charm. 
> 
> So my question is, is there a problem with creating a package for a fine
> but mostly-unmaintained piece of software that does its job, when I
> myself have minimal familiarity with the code (or the HP48 processor
> itself)?
I would appreciate a package. I did one myself but never made it public.
Where can the fixed version be downloaded?

  Uwe

-- 
  MMK GmbH, Universitaetsstr. 11, 58097 Hagen
  [EMAIL PROTECTED]
  Tel: +2331 840446Fax: +2331 843920


signature.asc
Description: Digital signature

Re: Debian and the GNU Free documentation license

[Andreas Metzler]

Manoj Srivastava <[EMAIL PROTECTED]> wrote:
>Beginning in 2001, concerns regarding the compatibility of the
> GNU Free Documentation License with the Debian Free Software
> Guidelines came to the attention of the debian-legal mailing list.
[...]
>Unfortunately, most of this discussion has been confined to
> the debian-legal mailing list, with the result that people like me
> who do not follow debian-legal are not aware of the situation, and,
> for the most, do not know the details of the issue involved.

>If the concerns of the people on debian-legal are shared by
> the developer body at large, we may have a potentially serious
> issue. The first step to determine this is making people aware of
> the issues involved.  The next would be to see if we can reach a
> determination of the position the project at large want to take on
> this issue.
[...]
>Thanks for your patience. The URL of the document is:
> http://people.debian.org/%7Esrivasta/Position_Statement.xhtml>

Great work. But if this is supposed to be read by all dds it should
have gone to -announce, shouldn't it?
cu and- followed the respective discussions on -legal for some
time, but it is just repeating itself over and over
now -reas

Re: kernel-image-2.4.22-1-k7 apm and usb-uhci problems

[Herbert Xu]

Marcel Kolaja <[EMAIL PROTECTED]> wrote:
> 
> I tried to load the uhci module, but it cannot be loaded too. With
> kernel-image-2.4.21-4-k7 both apm and usb-uhci work fine. I guess this
> behavior of 2.4.22-1-k7 is a bug. Shall I file a bug report?

This has been reported many times already.

The solution is to either upgrade to 2.4.22-2 which has just entered
unstable or boot with acpi=off.
-- 
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Re: Debian should not modify the kernels!

[Marc Haber]

On Sun, 28 Sep 2003 20:32:36 -0400, Matt Zimmerman <[EMAIL PROTECTED]>
wrote:
>Hear, hear.  IPsec in particular is long overdue in the Linux kernel and I
>am glad to see it.

Please note that the 2.6 ipsec is unuseable. You can't filter traffic
that goes into or comes from a tunnel. That's a killer.

Greetings
Marc

-- 
-- !! No courtesy copies, please !! -
Marc Haber  |   " Questions are the | Mailadresse im Header
Karlsruhe, Germany  | Beginning of Wisdom " | Fon: *49 721 966 32 15
Nordisch by Nature  | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29

Re: Debian should not modify the kernels!

[Herbert Xu]

Marc Haber <[EMAIL PROTECTED]> wrote:
> 
> Please note that the 2.6 ipsec is unuseable. You can't filter traffic
> that goes into or comes from a tunnel. That's a killer.

That's not true.  Filtering for tunnels works just fine.

Transport mode filtering is indeed not supported.  But you can achieve
the same effect through IPSEC policies.

The only show stopper with tunnels is the lack of SNAT support.  Even
that isn't very difficult to resolve.

Cheers,
-- 
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Re: Building kernel modules for stock kernels is a hell of a job!

[Henning Makholm]

Scripsit Manoj Srivastava <[EMAIL PROTECTED]>

>   He said use the kernel-headers package, not
>  kernel-package. Any debian packaged module shall work with something
>  like:

>  ./debian/rules KVERS="2.4.21" KSRC="/usr/src/kernel-headers-2.4.21" 
> KPKG_DEST_DIR="../" KDREV="blah" kdist_image

Interesting. Just out of curiosity, where is that supposed to be
documented? Knowing this might have enabled me to make use of the
debian packaging [1] of a module I needed a couple of weeks ago, but I
could not find any applicable docs in either the kernel-package,
kernel-source-XXX or the module source itself.

(Btw, is it a bug for the debian/rules in a module package to run
dh_testroot from its 'build' target? I know it's not allowed in the
debian/rules in a _source_ package, but perhaps the conventions
for kernel-module packages are different).

[1] Actually ended up inserting the module source in the kernel
directory tree and patching Makefiles and Config.in's to trick
it into building together with a kernel image. Yuck.

-- 
Henning Makholm "However, the fact that the utterance by
   Epimenides of that false sentence could imply the
   existence of some Cretan who is not a liar is rather unsettling."

Re: x48

[Hans Fugal]

The patch is quite simple [1], and you can grab a patched version at
http://students.cs.byu.edu/~fugalh/x48-041f.tar.gz

1. search for "x48 patch fugal" on google groups.

* Uwe Steinmann [Mon, 29 Sep 2003 at 09:07 +0200]

> On Thu, Sep 25, 2003 at 07:38:28AM -0600, Hans Fugal wrote:
> > Does anyone remember x48? It's an HP48 CPU emulator. It used to be
> > packaged for debian, but was orphaned.
> > 
> > In order to do any emulation it needs a ROM, which you can download from
> > your HP48 over the serial line. You can also get ROMs from [1]. 
> > "HP graciously began allowing this to be downloaded in mid-2000." [1]
> > I don't know exactly what this means by way of copyright and/or license,
> > and I have emailed the webmaster of hpcalc.org to see if he knows any
> > more details. I imagine ROMs won't be distributable. x48 itself is under
> > the GPL.
> > 
> > x48 hasn't been maintained for about 4 years now, and didn't work very
> > well on modern processors when I picked up the source (timing issues).
> > But Eddie Dost, the original author, has graciously worked with me to
> > get those issues resolved and it now works like a charm. 
> > 
> > So my question is, is there a problem with creating a package for a fine
> > but mostly-unmaintained piece of software that does its job, when I
> > myself have minimal familiarity with the code (or the HP48 processor
> > itself)?
> I would appreciate a package. I did one myself but never made it public.
> Where can the fixed version be downloaded?
> 
>   Uwe
> 
> -- 
>   MMK GmbH, Universitaetsstr. 11, 58097 Hagen
>   [EMAIL PROTECTED]
>   Tel: +2331 840446Fax: +2331 843920




-- 
 Hans Fugal | De gustibus non disputandum est.
 http://hans.fugal.net/ | Debian, vim, mutt, ruby, text, gpg
 http://gdmxml.fugal.net/   | WindowMaker, gaim, UTF-8, RISC, JS Bach
-
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95  CB5E FC98 E8CD E0AA D460


pgpayOylONBtK.pgp
Description: PGP signature

Re: Building kernel modules for stock kernels is a hell of a job!

[David Z Maze]

Henning Makholm <[EMAIL PROTECTED]> writes:

> Scripsit Manoj Srivastava <[EMAIL PROTECTED]>
>
>>  He said use the kernel-headers package, not
>>  kernel-package. Any debian packaged module shall work with something
>>  like:
>
>>  ./debian/rules KVERS="2.4.21" KSRC="/usr/src/kernel-headers-2.4.21" 
>> KPKG_DEST_DIR="../" KDREV="blah" kdist_image
>
> Interesting. Just out of curiosity, where is that supposed to be
> documented?

All of the information is in
/usr/share/doc/kernel-package/README.modules, though not with a single
command line like that as such.

> (Btw, is it a bug for the debian/rules in a module package to run
> dh_testroot from its 'build' target? I know it's not allowed in the
> debian/rules in a _source_ package, but perhaps the conventions
> for kernel-module packages are different).

I don't consider it a bug.  I do think the kdist and kdist_image
targets should reinvoke make under $(ROOT_CMD), though, just to be
sure.  The i2c-source debian/rules file has:

kdist_image:
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-modules
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean

kdist:
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-modules
dpkg-genchanges -b -e"$(KMAINT) <$(KEMAIL)>" -u"$(KSRC)/.." > $(CHFILE)
debsign -e"$(KMAINT) <$(KEMAIL)>" $(CHFILE)
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean

kdist_clean:
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean

...with some magic early on in the file to figure out the name of the
.changes file $(CHFILE).

-- 
David Maze [EMAIL PROTECTED]  http://people.debian.org/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
-- Abra Mitchell

Re: Debian and the GNU Free documentation license

[Manoj Srivastava]

On Mon, 29 Sep 2003 10:07:04 +0200, Andreas Metzler
<[EMAIL PROTECTED]> said:  

> Manoj Srivastava <[EMAIL PROTECTED]> wrote:
>> Thanks for your patience. The URL of the document is:
>> http://people.debian.org/%7Esrivasta/Position_Statement.xhtml>

> Great work. But if this is supposed to be read by all dds it should
> have gone to -announce, shouldn't it?

These are early days yet. We have just begun crafting this
 document, I am hoping people on -legal, who have studied the gfdl,
 would point out things missing, and add more concerete examples. The
 URL has been posted on debian-devel, debian-legal, and debian-vote.
 Anyone not reading any of these three lists probably does not want to
 be bothered by this as such an early stage.

When the document is further advanced, and we are closer to
 stating that we find the GFDL non free, I'll post again to -vote and
 -devel-announce. 

manoj
-- 
Everything should be built top-down, except this time.
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: Building kernel modules for stock kernels is a hell of a job!

[Manoj Srivastava]

On 29 Sep 2003 15:31:42 +0200, Henning Makholm <[EMAIL PROTECTED]> said: 

> Scripsit Manoj Srivastava <[EMAIL PROTECTED]>
>> He said use the kernel-headers package, not kernel-package. Any
>> debian packaged module shall work with something like:

>> ./debian/rules KVERS="2.4.21" KSRC="/usr/src/kernel-headers-2.4.21"
>> KPKG_DEST_DIR="../" KDREV="blah" kdist_image

> Interesting. Just out of curiosity, where is that supposed to be
> documented? Knowing this might have enabled me to make use of the
> debian packaging [1] of a module I needed a couple of weeks ago, but
> I could not find any applicable docs in either the kernel-package,
> kernel-source-XXX or the module source itself.

*Shrug*. This is a direct consequence of the way the
 kernel-package interacts with modules; and the details are in every
 kernel-package (/usr/share/doc/kernel-package/README.modules) and
 kernel-source package.  

patches and additional docs are always gladly received.

manoj
-- 
It is the quality rather than the quantity that matters. Lucius
Annaeus Seneca (4 B.C. - A.D. 65)
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: Accepted mini-dinstall 0.6.8 (all source)

[Mike Hommey]

On Monday 29 September 2003 19:32, Graham Wilson wrote:
> Changes:
>  mini-dinstall (0.6.8) unstable; urgency=low
[...]
>* Change DTD in manpage and manual to locally installed version.

Why do you need that ? (X|SG)ML catalogs are your friends...

Mike

Re: kernel-image-2.4.22-1-k7 apm and usb-uhci problems

[Marcel Kolaja]

On Mon, Sep 29, 2003 at 06:19:52PM +1000, Herbert Xu wrote:

> Marcel Kolaja <[EMAIL PROTECTED]> wrote:
> > 
> > I tried to load the uhci module, but it cannot be loaded too. With
> > kernel-image-2.4.21-4-k7 both apm and usb-uhci work fine. I guess this
> > behavior of 2.4.22-1-k7 is a bug. Shall I file a bug report?
> 
> This has been reported many times already.

Oh, I am sorry to report already reported bug. I tried to find whether the
bug is already reported, but did not find anything, and still cannot find.
Where can I find the bug report?

> The solution is to either upgrade to 2.4.22-2 which has just entered
> unstable or boot with acpi=off.

Thanks for your advice.

> Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>


Regards,

Marcel Kolaja
Debian GNU/Linux Power User http://www.debian.org/
--
"I think Debian's doing something wrong, `apt-get install pesticide'
doesn't seem to remove the bugs on my system!"   -- Mike Dresser

Re: Accepted mini-dinstall 0.6.8 (all source)

[Graham Wilson]

On Mon, Sep 29, 2003 at 08:28:16PM +0200, Mike Hommey wrote:
> On Monday 29 September 2003 19:32, Graham Wilson wrote:
> > Changes:
> >  mini-dinstall (0.6.8) unstable; urgency=low
> [...]
> >* Change DTD in manpage and manual to locally installed version.
> 
> Why do you need that ? (X|SG)ML catalogs are your friends...

Not in Debian at least. XML catalog support is a work-in-progress at
this point. Last time I checked, neither docbook-xsl or docbook-xml
registered themselves using update-xmlcatalog.

I've been meaning to write some patches...

-- 
gram


signature.asc
Description: Digital signature

Re: Debian should not modify the kernels!

[martin f krafft]

also sprach Herbert Xu <[EMAIL PROTECTED]> [2003.09.28.0012 +0200]:
> As I have said before, kernel-source's primary purpose is for
> building default Debian kernel images.  Thus it should contain all
> the patches necessary so that the images are uniform across
> architectures.

IPsec is not necessary.

> If someone wants to make a kernel-patch package out of it, go
> right ahead.

This is not responsible behaviour from a Debian maintainer, Herbert,
and you know it.

[...]
> This is simply unmaintainable due to the complex relationships between
> patches.

So you offload the work to others...

> In any case, the kernel-source package's README file should
> contain all the information you need to extract any particular
> patch that you're interested in.

We are not interested in a patch, we are interested in feature
backports being removed from kernel-source. Nowhere else does Debian
have feature backports, the entire security update system is
structured around the belief that this is *a bad thing*, and you are
just being a incredibly difficult and non-cooperative about it.

Are we going to need a formal vote to open your eyes?

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpfvD0U7YJdH.pgp
Description: PGP signature

Re: Building kernel modules for stock kernels is a hell of a job!

[Nicolas Boullis]

Hi,

On Mon, Sep 29, 2003 at 01:43:05PM -0400, David Z Maze wrote:

> I don't consider it a bug.  I do think the kdist and kdist_image
> targets should reinvoke make under $(ROOT_CMD), though, just to be
> sure.  The i2c-source debian/rules file has:
> 
> kdist_image:
> $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-modules
> $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
> 
> kdist:
> $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-modules
> dpkg-genchanges -b -e"$(KMAINT) <$(KEMAIL)>" -u"$(KSRC)/.." > 
> $(CHFILE)
> debsign -e"$(KMAINT) <$(KEMAIL)>" $(CHFILE)
> $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
> 
> kdist_clean:
> $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean

Are those $(MFLAGS) really useful?
I thought they were not because $(MAKE) also had the flags, but I'm not 
sure anymore...


Regards,

Nicolas

Resolvconf -- suggested reading before installing this :-)

[Osamu Aoki]

Hi,

On Sun, Sep 28, 2003 at 08:20:47PM -0500, Manoj Srivastava wrote:
> On Sun, 28 Sep 2003 21:49:28 +0200, Thomas Hood <[EMAIL PROTECTED]> said: 
> 
> > Manoj wrote:
> >> > I would be interested in knowing how you set it up equivalent to
> >> > cardctl scheme allows me to set up pcmcia networks.
> 
> > cardmgr's system of configuring things dependently upon
> > "scheme,socket,instance,hwaddr" is quite powerful but it is possible
> > to configure interfaces dependently on these variables using
> > ifupdown too (... though not so conveniently).  See below.
> 
>   One can also modify  /etc/pcmcia/network; line 109:
> 
> <  cat $RESOLV >> $RESOLV.N; mv $RESOLV.N $RESOLV
> >  cat $RESOLV >> $RESOLV.N; resolvconf -a $DEVICE < $RESOLV.N
> 
>   Anyway, I think I am goinf to use start_fn and stop_fn in
>  /etc/pcmcia/network.opts instead of using either hotplug or modifying
>  /etc/pcmcia/network;  I am already comfortable with my network.opts,
>  and it is all working together very nicely now.

I still use start_fn and stop_fn on my old note PC.  But as I read
Thomas' tutorial on dynamic "DEBIAN" network configuration, centralizing
configuration around /etc/network/interfaces as he proposes seems to
provide cleaner environment.

AJ's ifupdown package is quite interesting and very debian specific.
There were not much tutorials on this subject and many conventional
configuration procedures tend to cause some trouble with ifupdown if
they are not deployed very carefully.  Although he provide source to
make detailed source documentation, this key package practically comes
in very cryptic and short user manual page only. 

Whomever interested on this subject, Thomas' network set up tutorial
(draft) is available as "10 Network configuration":

  http://qref.sourceforge.net/Debian/reference/ch-gateway.en.html
   or
  http://www.debian.org/doc/manuals/reference/ch-gateway.en.html (older)

(Yes, he is rewriting my old small section with whole new section with
 very good overview.  Please tell Thomas about any problem in 10.1-10.8.
 Please understand this is on-going update.)

Osamu

Re: Building kernel modules for stock kernels is a hell of a job!

[Eduard Bloch]

#include 
* Nicolas Boullis [Mon, Sep 29 2003, 11:42:59PM]:

> On Mon, Sep 29, 2003 at 01:43:05PM -0400, David Z Maze wrote:
> 
> > I don't consider it a bug.  I do think the kdist and kdist_image
> > targets should reinvoke make under $(ROOT_CMD), though, just to be
> > sure.  The i2c-source debian/rules file has:

It is not a bug - there is AFAICS no way to tell make to run a rule
_twice_. You cannot say:

kdist_image: clean kdist_configure binary-modules clean

and expect the last "clean" in the list to be executed. Even the order
of the rules execution is not guaranteed when -j is used.

> > kdist:
> > $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-modules
> > dpkg-genchanges -b -e"$(KMAINT) <$(KEMAIL)>" -u"$(KSRC)/.." > 
> > $(CHFILE)
> > debsign -e"$(KMAINT) <$(KEMAIL)>" $(CHFILE)
> > $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean

Just for the record, module-assistant includes such things ready to be
sourced by other Makefiles.

> > kdist_clean:
> > $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
> 
> Are those $(MFLAGS) really useful?
> I thought they were not because $(MAKE) also had the flags, but I'm not 
> sure anymore...

MFLAGS are the flags that make got on the commandline. The calls above
copy the make call with options.

MfG,
Eduard.
-- 
Es ist offensichtlich, daß das menschliche Gehirn wie ein Computer
funktioniert.  Da es keine dummen Computer gibt, gibt es also auch
keine dummen Menschen.  Nur ein paar Leute, die unter Windows laufen.

some packages don't list their /etc/default/ file

[Dan Jacobson]

Some packages don't list their /etc/default/ file as part of the package:
# for i in /etc/default/*; do dpkg -S $i;done
dpkg: /etc/default/alsa not found.
aumix: /etc/default/aumix
cdrecord: /etc/default/cdrecord
libc6: /etc/default/devpts
dnsmasq: /etc/default/dnsmasq
dpkg: /etc/default/exim4 not found.
dpkg: /etc/default/fetchmail not found.
dpkg: /etc/default/hotplug not found.
initrd-tools: /etc/default/initrd-tools.sh
dpkg: /etc/default/iptables not found.
libnss-db: /etc/default/libnss-db
dpkg: /etc/default/noffle not found.
dpkg: /etc/default/rcS not found.
cdrecord: /etc/default/rscsi
spamassassin: /etc/default/spamassassin
ssh: /etc/default/ssh

Re: Bug#213127: ITP: extlib -- extended standard library for OCaml

[Anthony DeRobertis]

On Sunday, Sep 28, 2003, at 09:59 US/Eastern, Stefano Zacchiroli wrote:
Actually ExtLib contains modules implementing: enumeration over 
abstract
I suggest striking "actually"

Bug#78782: Vicodin, pain medication available eipwxnkcuxijoe a

[Ian Sylvester]

Vicodin ES 90 Tab Special.
-Free Doctors consultation
-No Rx Required
-Overnight Shipping
-Other Drugs Available Including SOMA, HYDROCODONE, LEVITRA...

Buy Now!
http://www.rxdiscountusa.biz/medical























take off list
http://www.rxdiscountusa.biz/a.html






yw ztou r zlvyq aqcwpcibx
g

Re: some packages don't list their /etc/default/ file

[Santiago Vila]

On Tue, 30 Sep 2003, Dan Jacobson wrote:

> Some packages don't list their /etc/default/ file as part of the package:
> # for i in /etc/default/*; do dpkg -S $i;done
> dpkg: /etc/default/alsa not found.
> aumix: /etc/default/aumix
> cdrecord: /etc/default/cdrecord
> libc6: /etc/default/devpts
> dnsmasq: /etc/default/dnsmasq
> dpkg: /etc/default/exim4 not found.
> dpkg: /etc/default/fetchmail not found.
> dpkg: /etc/default/hotplug not found.
> initrd-tools: /etc/default/initrd-tools.sh
> dpkg: /etc/default/iptables not found.
> libnss-db: /etc/default/libnss-db
> dpkg: /etc/default/noffle not found.
> dpkg: /etc/default/rcS not found.
> cdrecord: /etc/default/rscsi
> spamassassin: /etc/default/spamassassin
> ssh: /etc/default/ssh

You have just discovered a known fact: Not every configuration file
has to be a "conffile" in the dpkg sense.

Not shipping a configuration file inside the .deb and creating it in
the postinst a perfectly acceptable way of managing such file.

Re: Debian should not modify the kernels!

[Branden Robinson]

On Mon, Sep 29, 2003 at 11:06:00PM +0200, martin f krafft wrote:
> Nowhere else does Debian have feature backports,

That's not true.  Feature backports are occasionally incidental in, e.g,
XFree86 package updates when snatching a newer version of a driver for
its bugfixes, and the code has changed too much to make backporting the
bugfixes by themselves tedious.

> the entire security update system is
> structured around the belief that this is *a bad thing*, and you are
> just being a incredibly difficult and non-cooperative about it.

There's a difference between security updates, proposed updates for
released versions of the Debian OS, and updates to unstable.

-- 
G. Branden Robinson|  The National Security Agency is
Debian GNU/Linux   |  working on the Fourth Amendment
[EMAIL PROTECTED] |  thing.
http://people.debian.org/~branden/ |  -- Phil Lago, Deputy XD, CIA


signature.asc
Description: Digital signature

Bug#213348: developers-reference: Binary-only NMU and dependencies

[Aurelien Jarno]

Package: developers-reference
Version: 3.3.3
Severity: wishlist

Hello,

I remarked that some binary-only NMU are breaking packages by making
them uninstallable. The problem occurs when a source package generate
more than one binary package, a few architecture dependant and a few
architecture independant, with strict dependenciess between them, ie 
using $(Source-Version).

If a binary-only NMU is done, the architecture dependant packages have
a different version than the architecture independant one. In that case,
binary-only NMU should be avoided, instead, the maintainer should be
asked to upload a new version.

Thus I propose the add the following paragraph to the Debian Developer's
Reference, section 5.10.2.1:

  ... available one).

  You have to make sure that doing a binary-only NMU won't render the
  package uninstallable. It could occur when a source package generates
  both architecture dependant and independant packages that depend on
  each other through $(Source-Version). In the later case, you may
  consider doing a source NMU.

  Despite ...

(Don't hesitate to fix my grammar/spelling in this paragraph, English 
is not my native language).

Cheers,
Aurelien


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux pc.aurel32 2.4.22 #1 mer sep 17 20:55:21 CEST 2003 i686
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (ignored: LC_ALL set to [EMAIL PROTECTED])

-- no debconf information

Bug#212049: ANTIVIRUS LA REGION - Virus encontrado (RECIPIENT)!

[euro]

  
 [EMAIL PROTECTED] intentaba mandar un e-mail con virus. 
-
 KAV report:
-
suspicion: Exploit.IFrame.FileDownload
cjoqm.exe   infected: I-Worm.Swen

-
This message redirect to [EMAIL PROTECTED] 

--- Begin Message ---
--- End Message ---

Bug#213353: ITP: python-ctypes -- python package to create and manipulate C data types

[Ganesan Rajagopal]

Package: wnpp
Version: unavailable; reported 2003-09-29
Severity: wishlist

* Package name: python-ctypes
  Version : 0.6.2
  Upstream Author : Thomas Heller <[EMAIL PROTECTED]>
* URL : http://starship.python.net/crew/theller/ctypes/
* License : MIT
  Description : python package to create and manipulate C data types

ctypes is a Python package to create and manipulate C data types in Python, 
and to call functions in dynamic link libraries/shared dlls. It allows 
wrapping these libraries in pure Python.
 
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux andlx-anamika 2.4.21 #1 Fri Jul 4 17:18:58 IST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Bug#213361: ITP: kbtin -- A text-based MUD client

[Adam Borowski]

Package: wnpp
Severity: wishlist

* Package name: kbtin
  Version : 1.0.5
  Upstream Author : Adam Borowski <[EMAIL PROTECTED]>
* URL : http://kbtin.sourceforge.net
* License : GPL
  Sponsor : Wanted
  Package : http://kbtin.sf.net/debian/
  Description : A text-based MUD client

KBtin is a fullscreen console MUD client based on the once-popular tintin++.
It is not limited for mudding, and can be used for running line-based local
programs like adventure, wumpus or mysqlclient.

Bug#212028: ANTIVIRUS LA REGION - Virus encontrado (RECIPIENT)!

[euro]

  
 [EMAIL PROTECTED] intentaba mandar un e-mail con virus. 
-
 KAV report:
-
suspicion: Exploit.IFrame.FileDownload
cjoqm.exe   infected: I-Worm.Swen

-
This message redirect to [EMAIL PROTECTED] 

--- Begin Message ---
--- End Message ---