whoopsie.postinst rejects legal arguments

Bug #978436 reported by Colin Watson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whoopsie-daisy (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

case "$1" in
        configure)
[...]
        *)
                echo "postinst called with an unknown argument \`$1'" >&2
                exit 1
        ;;
esac

There are several legal arguments to postinst other than 'configure', and whoopsie needs to accept them even if it doesn't do anything special with them. I suggest replacing that case statement with 'if [ "$1" = configure" ]; then ...; fi'.

Evan (ev)
Changed in whoopsie-daisy (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package whoopsie-daisy - 0.1.30

---------------
whoopsie-daisy (0.1.30) precise; urgency=low

  * Stop rejecting legal arguments to the postinst (LP: #978436). Thanks
    Colin Watson!
 -- Evan Dandrea <email address hidden> Thu, 12 Apr 2012 09:00:26 +0100

Changed in whoopsie-daisy (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Toby Smithe (tsmithe) wrote :

Just running my daily update.. Don't you mean

if [ "$1" == "configure" ]; then

? Otherwise:

/var/lib/dpkg/info/whoopsie.postinst: 6: [: configure: unexpected operator

Revision history for this message
Toby Smithe (tsmithe) wrote :

(or rather,

if [ "$1" = "configure" ]; then ...

arg!)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.