Bug#235866: marked as done (lintian: False positives: postrm-does-not-call-updatemenus/postinst-does-not-call-updatemenus)
reopen 235866
thanks
If you didn't understand the explaination: that's because I wanted to
close an totally different lintian bug with it :)
Sorry, lintian has too many bugs, *sigh*, and that's what we're trying
to solve...
--Jeroen
On Thu, Mar 04, 2004 at 06:03:23PM -0800, Debian Bug Tracking System wrote:
> Your message dated Fri, 5 Mar 2004 02:28:13 +0100
> with message-id <20040305012813.GH1466@A-Eskwadraat.nl>
> and subject line Then don't do that
> 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; 2 Mar 2004 21:38:03 +0000
> >From maulkin@halon.org.uk Tue Mar 02 13:38:03 2004
> Return-path: <maulkin@halon.org.uk>
> Received: from 82-38-206-197.cable.ubr05.shef.blueyonder.co.uk (vivacia.halon.org.uk) [82.38.206.197]
> by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
> id 1AyHaV-000570-00; Tue, 02 Mar 2004 13:38:03 -0800
> Received: by vivacia.halon.org.uk (Postfix, from userid 1000)
> id 9AF5D3E54F; Tue, 2 Mar 2004 21:37:59 +0000 (GMT)
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> From: Neil McGovern <maulkin@halon.org.uk>
> To: Debian Bug Tracking System <submit@bugs.debian.org>
> Subject: lintian: False positives:
> postrm-does-not-call-updatemenus/postinst-does-not-call-updatemenus
> X-Mailer: reportbug 2.49
> Date: Tue, 02 Mar 2004 21:37:58 +0000
> Message-Id: <[🔎] 20040302213759.9AF5D3E54F@vivacia.halon.org.uk>
> Delivered-To: submit@bugs.debian.org
> X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_01
> (1.212-2003-09-23-exp) on spohr.debian.org
> X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
> version=2.60-bugs.debian.org_2004_03_01
> X-Spam-Level:
>
> Package: lintian
> Version: 1.22.11
> Severity: normal
> Tags: sid
>
> The follwing errors are produced:
> E: limewire: postinst-does-not-call-updatemenus usr/lib/menu/limewire
> N:
> N: Since the package installs a file in either /usr/lib/menu or
> N: /etc/menu-methods, the package should probably call the update-menus
> N: command in it's postinst script.
> N:
> N: For example, use the following code in your maintainer script:
> N: if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
> N:
> E: limewire: postrm-does-not-call-updatemenus usr/lib/menu/limewire
> N:
> N: Since the package installs a file in either /usr/lib/menu or
> N: /etc/menu-methods, the package should probably call the update-menus
> N: command in it's postrm script.
> N:
> N: For example, use the following code in your maintainer script:
> N: if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
> N:
>
> However, these do actually exist in debian/postrm and debian/postinst:
> [maulkin@vivacia:/home/debian/limewire-3.8.5] $ grep update-menus debian/*
> debian/changelog: * Add call to update-menus in postinst and postrm.
> debian/postinst: if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
> debian/postrm: if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
>
> Many thanks,
> Neil McGovern
> -- System Information:
> Debian Release: testing/unstable
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.0
> Locale: LANG=en_GB, LC_CTYPE=en_GB
>
> Versions of packages lintian depends on:
> ii binutils 2.14.90.0.7-5 The GNU assembler, linker and bina
> ii diffstat 1.34-1 produces graph of changes introduc
> ii file 4.07-2 Determines file type using "magic"
> ii man-db 2.4.2-10 The on-line manual pager
> ii perl 5.8.3-2 Larry Wall's Practical Extraction
>
> -- no debconf information
>
> ---------------------------------------
> Received: (at 235866-done) by bugs.debian.org; 5 Mar 2004 01:28:14 +0000
> >From jeroen@wolffelaar.nl Thu Mar 04 17:28:14 2004
> Return-path: <jeroen@wolffelaar.nl>
> Received: from a-eskwadraat.nl [131.211.34.218] (mail)
> by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
> id 1Az48M-0005BM-00; Thu, 04 Mar 2004 17:28:14 -0800
> Received: from jeroen by A-Eskwadraat.nl with local (Exim 3.35 #1 (Debian))
> id 1Az48L-0005Hg-00
> for <235866-done@bugs.debian.org>; Fri, 05 Mar 2004 02:28:13 +0100
> Date: Fri, 5 Mar 2004 02:28:13 +0100
> To: 235866-done@bugs.debian.org
> Subject: Then don't do that
> Message-ID: <20040305012813.GH1466@A-Eskwadraat.nl>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> User-Agent: Mutt/1.3.28i
> X-Habeas-SWE-1: winter into spring
> X-Habeas-SWE-2: brightly anticipated
> X-Habeas-SWE-3: like Habeas SWE (tm)
> X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
> X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
> X-Habeas-SWE-6: email in exchange for a license for this Habeas
> X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
> X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
> X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
> From: Jeroen van Wolffelaar <jeroen@wolffelaar.nl>
> Delivered-To: 235866-done@bugs.debian.org
> X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_01
> (1.212-2003-09-23-exp) on spohr.debian.org
> X-Spam-Status: No, hits=-8.0 required=4.0 tests=HABEAS_SWE autolearn=no
> version=2.60-bugs.debian.org_2004_03_01
> X-Spam-Level:
>
> Hi,
>
> Please simply don't do that. Simply ship those files executable, even
> though it doesn't make sense, you shouldn't employ such tricks to
> prevent it, if users want to shoot themselves in the foot by trying to
> launch something while installing/deinstalling, well, they should do so.
> It doesn't have any negative result, other than 'it doesn't work then'.
>
> If you insist, install an override.
>
> Closing this bug...
> --Jeroen
>
> --
> Jeroen van Wolffelaar
> Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
> http://Jeroen.A-Eskwadraat.nl
--
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
Reply to: