Your message dated Sat, 03 Dec 2011 11:32:35 +0100
with message-id <[email protected]>
and subject line Re: Bug#644323: pyudev: /run transition: Please update use of
/dev/.udev
has caused the Debian Bug report #644323,
regarding pyudev: /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.)
--
644323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644323
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pyudev
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 pyudev 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 ---
> pyudev-0.12/tests/test_core.py: assert context.run_path == '/run/udev'
I'm a bit confused: the bug says pyudev references /dev/.udev while the log
says /run/udev.
Anyway, this is just a file from the testsuite that we can't run during the
build.
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
