Your message dated Sat, 30 Jun 2012 00:18:11 +0200
with message-id <20120629221810.GA32079@localhost>
and subject line Re: Bug#644312: fusioninventory-agent: /run transition: Please
update use of /dev/.udev
has caused the Debian Bug report #644312,
regarding fusioninventory-agent: /run transition: Please update use of
/dev/.udev
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
644312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644312
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: fusioninventory-agent
Severity: important
User: [email protected]
Usertags: run-transition udev
Hi!
/run is a new cross-distribution location for the storage of
transient state files, i.e. files containing run-time information
that may or may not need to be written early in the boot process and
which does not require preserving across reboots. [1] Support for
/run is an accepted release goal for wheezy.
A result of that change is, that udev no longer uses /dev/ to store
its runtime state file, i.e. the /dev/.udev/ directory, /dev/.udevdb
and /dev/.udev.tdb are gone and udev uses /run/udev/ now.
During an automated test your package fusioninventory-agent was
flagged to reference files/directories matching /dev/.udev A log of
this test can be found at [2].
In most cases checking for /dev/.udev is used to determine if udev is
active. This check no longer works with udev using /run/udev now.
In most cases, checking for udev being installed is not appropriate
and should be avoided.
Nowadays all reasonable systems either have udev installed or do not
need /dev to be managed (e.g. LXC, chroots): if your package only
needs to decide if MAKEDEV should be run then please just remove all
such code and assume that the device exists. If the package is only
useful when it reacts to uevents then it should probably depend on
udev. If checking for udev being active is really needed, then your
package needs to be updated to support this new location of the udev
database. If you have any doubts, please contact the udev maintainer
Marco d'Itri <[email protected]>.
[1] http://wiki.debian.org/ReleaseGoals/RunDirectory
[2]
http://wiki.debian.org/ReleaseGoals/RunDirectory#Packages_using_.2BAC
8-dev.2BAC8.udev
--- End Message ---
--- Begin Message ---
On Thu, Jan 19, 2012 at 10:49:29AM +0000, Roger Leigh wrote:
> On Tue, Oct 04, 2011 at 11:48:06PM +0200, [email protected] wrote:
> There is no "db" directory with the current version of udev, hence
> the function getDevicesFromUdev will always fail given that the
> glob will always fail. This is something that needs additional
> work. As the original bug report stated, using udev internals
> directly is a bad plan, given that they have now changed.
Hello Roger and Michael,
First, sorry for the delay. FusionInventory-Agent try various different
way to get information about the system.
I belive it's hameless to keep the current code. At worst glob() will
return an empty list.
Best regards,
--
Gonéri Le Bouder
signature.asc
Description: Digital signature
--- End Message ---
