Shipping a file under /var in a package is normally incorrect.  In this
case it appears that the file is only ever used as a stamp file - its
contents never change, it's only an IPC mechanism between udev and
libvpd to trigger an update of the database on a device change.  So it
is not an outright packaging bug to ship this file in the package.

However, I don't understand how the absence of this file is causing a
problem.  The udev rule will always cause the stamp file to be created
on boot, or on the first device change after the installation of the
libvpd package.  If the file does not exist, then the database created
by the lsvpd package on install must already be up to date.  The
behavior of libvpd in this case appears to be correct.

And putting a file such as this into a shared library package means that
any new version of the library with a new ABI will have to declare a
Replaces: against the older versions of the library, which is not ideal
- however this problem already exists because of the udev rules file.

In any case, please explain why you believe the absence of this file is
a bug.

** Changed in: libvpd (Ubuntu)
       Status: New => Incomplete

** Changed in: libvpd (Ubuntu)
     Assignee: Taco Screen team (taco-screen-team) => Adam Conrad (adconrad)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492895

Title:
  Ubuntu 14.04.03 Missing file - run.vpdupdate in libvpd package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpd/+bug/1492895/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to