Your message dated Fri, 23 Dec 2005 09:02:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#339975: fixed in libticables3 3.9.6-5
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 Nov 2005 00:08:45 +0000
>From [EMAIL PROTECTED] Sat Nov 19 16:08:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from gw02.mail.saunalahti.fi ([195.197.172.116])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EdclB-0003Bh-AF
        for [EMAIL PROTECTED]; Sat, 19 Nov 2005 16:08:45 -0800
Received: from angua.pieni.net (ip212-226-168-226.adsl.kpnqwest.fi 
[212.226.168.226])
        by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 786E4D7C6B
        for <[EMAIL PROTECTED]>; Sun, 20 Nov 2005 02:08:43 +0200 (EET)
Received: from [10.10.100.16] (unknown [10.10.100.16])
        (using TLSv1 with cipher RC4-MD5 (128/128 bits))
        (No client certificate requested)
        by angua.pieni.net (Postfix) with ESMTP id 2BAD76A70B
        for <[EMAIL PROTECTED]>; Sun, 20 Nov 2005 02:08:43 +0200 (EET)
Subject: libticables3: does not purge cleanly
From: Lars Wirzenius <[EMAIL PROTECTED]>
To: debian bugs <[EMAIL PROTECTED]>
Content-Type: text/plain
Date: Sun, 20 Nov 2005 02:08:42 +0200
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 
Content-Transfer-Encoding: 7bit
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: libticables3
Version: 3.9.6-3

When testing libticables3 with piuparts I get the following error:

0m7.1s ERROR: Package purging left files on system:
  /etc/udev
    owned by: libticables3
  /etc/udev/rules.d
    owned by: libticables3
  /etc/udev/rules.d/025_libticables.rules

My analysis: the postrm script tries to remove the link when the package
is purged, but this is too late: dpkg does not know about the link
in /etc/udev/rules.d, so it tries to remove the directories already when
the package is being removed, before it is being purged.

I guess the link should be removed already when the package is purged?
Alternatively, don't put /etc/udev/rules.d into the package, create it
in postinst (and remove in postrm).

-- 
Fundamental truth #1: Complexity is the enemy.


---------------------------------------
Received: (at 339975-close) by bugs.debian.org; 23 Dec 2005 17:16:55 +0000
>From [EMAIL PROTECTED] Fri Dec 23 09:16:55 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1EpqIv-0005Pl-Rg; Fri, 23 Dec 2005 09:02:05 -0800
From: Julien BLACHE <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#339975: fixed in libticables3 3.9.6-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 23 Dec 2005 09:02:05 -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: libticables3
Source-Version: 3.9.6-5

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

libticables3-dev_3.9.6-5_i386.deb
  to pool/main/libt/libticables3/libticables3-dev_3.9.6-5_i386.deb
libticables3_3.9.6-5.diff.gz
  to pool/main/libt/libticables3/libticables3_3.9.6-5.diff.gz
libticables3_3.9.6-5.dsc
  to pool/main/libt/libticables3/libticables3_3.9.6-5.dsc
libticables3_3.9.6-5_i386.deb
  to pool/main/libt/libticables3/libticables3_3.9.6-5_i386.deb



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.
Julien BLACHE <[EMAIL PROTECTED]> (supplier of updated libticables3 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: Fri, 23 Dec 2005 17:44:55 +0100
Source: libticables3
Binary: libticables3 libticables3-dev
Architecture: source i386
Version: 3.9.6-5
Distribution: unstable
Urgency: low
Maintainer: Julien BLACHE <[EMAIL PROTECTED]>
Changed-By: Julien BLACHE <[EMAIL PROTECTED]>
Description: 
 libticables3 - support library for Texas Instruments link cables
 libticables3-dev - support library for Texas Instruments link cables 
[development fi
Closes: 339975
Changes: 
 libticables3 (3.9.6-5) unstable; urgency=low
 .
   * debian/libticables3.postrm:
     + Remove /etc/udev on purge if empty (closes: #339975).
Files: 
 ebccbb9e64973619c1a787cd1964c342 722 libs optional libticables3_3.9.6-5.dsc
 b6969b7f6b80195b27d237e55fed5e12 6848 libs optional 
libticables3_3.9.6-5.diff.gz
 7dd890569c6e6915f4a158afbfa8aa7e 85002 libdevel optional 
libticables3-dev_3.9.6-5_i386.deb
 addd996bb7582e8e285392f1bccf995d 47206 libs optional 
libticables3_3.9.6-5_i386.deb

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

iD8DBQFDrCpkzWFP1/XWUWkRAq8VAJ46YjnwjiBCQeo3cZ4Htlt+K4ehswCgzmAR
56S+SThKFBNsykTP2Qv32Gw=
=gZ67
-----END PGP SIGNATURE-----


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

Reply via email to