Your message dated Tue, 31 Jan 2006 23:32:09 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349036: fixed in libnjb 2.2.5-2
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; 20 Jan 2006 17:45:55 +0000
>From [EMAIL PROTECTED] Fri Jan 20 09:45:55 2006
Return-path: <[EMAIL PROTECTED]>
Received: from zproxy.gmail.com ([64.233.162.199])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1F00Kh-0004QX-DE
        for [EMAIL PROTECTED]; Fri, 20 Jan 2006 09:45:55 -0800
Received: by zproxy.gmail.com with SMTP id 8so513837nzo
        for <[EMAIL PROTECTED]>; Fri, 20 Jan 2006 09:45:54 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        
h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        
b=Ey4GmxEaeToqEB5BGHG3asLNeOCs/b1fid+T6359pOvE3TETqaZcQLSTTzOByHbQO2DfWOIELcXXxmNg2nXQRlNMlIAGRWIYhr6B3YC6Hs075AQW55t3q/pfIgLoR494h4/KYniS6QPEN5AwLgNtXF8KPQSp5w616FSJ1X9xj30=
Received: by 10.65.213.5 with SMTP id p5mr1609006qbq;
        Fri, 20 Jan 2006 09:45:54 -0800 (PST)
Received: by 10.64.253.1 with HTTP; Fri, 20 Jan 2006 09:45:54 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 20 Jan 2006 10:45:54 -0700
From: Shaun Jackman <[EMAIL PROTECTED]>
Reply-To: Shaun Jackman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libnjb: hotplug does not work with
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: libnjb
Version: 2.2.4-2
Severity: serious
Justification: renders package unusable
Submitter: kaouete <[EMAIL PROTECTED]>

---------- Forwarded message ----------
From: kaouete <[EMAIL PROTECTED]>
Date: 2006-01-18 10:01
Subject: Bug#337790: acknowledged by developer (Bug#337790: fixed in
libnjb 2.2.4-2)
To: [EMAIL PROTECTED]

i am sorry to say this, but i think you did not completely test what you
added to this package.

i tested and it doesnt work. (or it work like it was working
before, but it is not enough with last etch libusb)
The problem is that there is 2 file to change their
permissions :
the one in /dev/bus/usb and the one in /proc/bus/usb

this is what you have in udev logs when you plug your nomad :
HOTPLUG_TIME=3D'Wed Jan 18 17:53:51 CET 2006'
UDEV_LOG=3D3
ACTION=3Dadd
OLDPWD=3D/
SEQNUM=3D1615
DEVPATH=3D/devices/pci0000:00/0000:00:03.3/usb4/4-5
SUBSYSTEM=3Dusb
PHYSDEVDRIVER=3Dusb
UDEVD_EVENT=3D1
PHYSDEVBUS=3Dusb

HOTPLUG_TIME=3D'Wed Jan 18 17:53:52 CET 2006'
UDEV_LOG=3D3
ACTION=3Dadd
OLDPWD=3D/
SEQNUM=3D1616
DEVPATH=3D/devices/pci0000:00/0000:00:03.3/usb4/4-5/4-5:1.0
SUBSYSTEM=3Dusb
MODALIAS=3Dusb:v041Ep411Bd0001dcFFdscFFdpFFicFFiscFFipFF
TYPE=3D255/255/255
INTERFACE=3D255/255/255
PRODUCT=3D41e/411b/1
UDEVD_EVENT=3D1
PHYSDEVBUS=3Dusb
DEVICE=3D/proc/bus/usb/004/003

HOTPLUG_TIME=3D'Wed Jan 18 17:53:52 CET 2006'
UDEV_LOG=3D3
DEVNAME=3D/dev/bus/usb/004/003
ACTION=3Dadd
OLDPWD=3D/
SEQNUM=3D1617
MAJOR=3D189
DEVPATH=3D/class/usb_device/usbdev4.3
SUBSYSTEM=3Dusb_device
MINOR=3D386
PHYSDEVPATH=3D/devices/pci0000:00/0000:00:03.3/usb4/4-5
PHYSDEVDRIVER=3Dusb
UDEVD_EVENT=3D1
PHYSDEVBUS=3Dusb

the 2 last are the one we are interested in :
there is one SUBSYSTEM=3Dusb (the one you catch)
and another one SUBSYSTEM=3Dusb_device (the one all the app using
last etch libusb use)(see
http://packages.qa.debian.org/libu/libusb/news/1.html)

the thing is not to just catch them in the udev rule, but the
script have to take into account that there is different variable
names in the two cases : DEVICE for the first and DEVNAME for the
second.

While i am at it, i wanted to ask if it was not better to make
libnjb5 conflicts with libnjb-hotplug since the second is merged
in the first.

Thanks for reading me.

kaouete

---------------------------------------
Received: (at 349036-close) by bugs.debian.org; 1 Feb 2006 07:40:23 +0000
>From [EMAIL PROTECTED] Tue Jan 31 23:40:23 2006
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1F4CTJ-0003Da-RD; Tue, 31 Jan 2006 23:32:09 -0800
From: Shaun Jackman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#349036: fixed in libnjb 2.2.5-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 31 Jan 2006 23:32:09 -0800
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: libnjb
Source-Version: 2.2.5-2

We believe that the bug you reported is fixed in the latest version of
libnjb, which is due to be installed in the Debian FTP archive:

libnjb-dev_2.2.5-2_i386.deb
  to pool/main/libn/libnjb/libnjb-dev_2.2.5-2_i386.deb
libnjb-doc_2.2.5-2_all.deb
  to pool/main/libn/libnjb/libnjb-doc_2.2.5-2_all.deb
libnjb-examples_2.2.5-2_i386.deb
  to pool/main/libn/libnjb/libnjb-examples_2.2.5-2_i386.deb
libnjb5_2.2.5-2_i386.deb
  to pool/main/libn/libnjb/libnjb5_2.2.5-2_i386.deb
libnjb_2.2.5-2.diff.gz
  to pool/main/libn/libnjb/libnjb_2.2.5-2.diff.gz
libnjb_2.2.5-2.dsc
  to pool/main/libn/libnjb/libnjb_2.2.5-2.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Shaun Jackman <[EMAIL PROTECTED]> (supplier of updated libnjb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed,  1 Feb 2006 00:07:26 -0700
Source: libnjb
Binary: libnjb-doc libnjb-examples libnjb-dev libnjb5
Architecture: source i386 all
Version: 2.2.5-2
Distribution: unstable
Urgency: low
Maintainer: Shaun Jackman <[EMAIL PROTECTED]>
Changed-By: Shaun Jackman <[EMAIL PROTECTED]>
Description: 
 libnjb-dev - Creative Labs Nomad Jukebox library development files
 libnjb-doc - Creative Labs Nomad Jukebox library documentation
 libnjb-examples - Creative Labs Nomad Jukebox example binaries
 libnjb5    - Creative Labs Nomad Jukebox library
Closes: 349036
Changes: 
 libnjb (2.2.5-2) unstable; urgency=low
 .
   * Fix the udev rules script to support libusb 0.1.10a-22.
     Closes: #349036.
Files: 
 5656c9c3a2c3d7a9102fc62c11cb82d9 613 libs optional libnjb_2.2.5-2.dsc
 153bc146c9d4b78683aeb00bc3cb4837 3011 libs optional libnjb_2.2.5-2.diff.gz
 10f5fcda917671001f557e74981a4cc7 168228 libdevel optional 
libnjb-doc_2.2.5-2_all.deb
 00d9431eed8a90e20db2d51891500ceb 92032 libs optional libnjb5_2.2.5-2_i386.deb
 99b879319e06680618ec32d188b661ff 86254 libdevel optional 
libnjb-dev_2.2.5-2_i386.deb
 aed0daf631a4ec9c853ac125fe35fce7 46536 libdevel optional 
libnjb-examples_2.2.5-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD4GC6vFdYF1IwUUoRAjFAAJ9oVox4qyLRFNaQUuUuivx3HJEdrwCgwNrv
vN7Otz5MVZ/bquBQTOAatc8=
=FdT8
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to