[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#374253: ifplugd: Annoying "dpkg --compare-versions" warnings upon installation

Hi Sukant,

On 06/06/18 01:21 -0500, Sukant Hajra said ...
> the output of an installation.  The problem seems to be the postinst
> script which has some "dpkg --compare-versions" calls.  I briefly looked
> at the script, but didn't figure out what exactly is wrong.

The script looks OK to me too.  I wonder if this was a minor bug in the
dpkg version in use then (I did not dig deeper).  Are you still able to
reproduce this problem?

> Preconfiguring packages ...
> dpkg: --compare-versions takes three arguments: <version> <relation> <version>
> Setting up ifplugd (0.28-2) ...
> dpkg: --compare-versions takes three arguments: <version> <relation> <version>

I was reading Debian policy (6.7 Details of configuration) and noticed

  "When we configure a package (this happens with dpkg --install and dpkg
  --configure), we first update any conffiles and then call:

       postinst configure most-recently-configured-version

  No attempt is made to unwind after errors during configuration. If the
  configuration fails, the package is in a "Failed Config" state, and an
  error message is generated.

  If there is no most recently configured version dpkg will pass a null
  argument. [41]"

And we are checking 'if [ -z "$2" ]' which would be true in case of a
fresh install (which is what your scenario is). 

I recently took up maintenance of ifplugd and since this is a fairly old
bug, if you are not able to reproduce to it, I would be inclined to
close it.  Please do let me know :)



Y Giridhar Appaji Nag | http://www.appaji.net/

Attachment: signature.asc
Description: Digital signature

Reply to: