Package: systemd
Version: 208.8
(note: for some reason reportbug originally inserted the package and
version into the subject ...)
Dear Maintainer,
* What led up to the situation?
I installed from a testing CD downloaded in early August. I
ran into login problems, but discovered I
Processing commands for cont...@bugs.debian.org:
found 760142 208-8
Bug #760142 [systemd] systemd: Assertions from systemd-logind on powerpc during
login, with continuing loop
Marked as found in versions systemd/208-8.
thanks
Stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
notfound 760142 208.8
Bug #760142 [systemd] systemd: Assertions from systemd-logind on powerpc during
login, with continuing loop
There is no source info for the package 'systemd' at version '208.8' with
architecture ''
Unable to make a source
Am 01.09.2014 11:04, schrieb Chris Tillman:
Activation of org.freedesktop.systemd1 timed out
There are quite a few more D-Bus services besides
org.freedesktop.systemd1 which time out.
It seems also that all services which use Type=dbus in their .service
file enter the failed state.
So
On Monday 01 September 2014 05:56 PM, Michael Biebl wrote:
By quickly glancing over the package, I also noted that you ship a
systemd .service file named multipathd.service but the SysV init scripts
are named /etc/init.d/multipath-tools and
/etc/init.d/multipath-tools-boot (not quite sure why
Am 01.09.2014 13:37, schrieb Michael Biebl:
Am 01.09.2014 13:25, schrieb Michael Biebl:
Am 01.09.2014 12:50, schrieb Ritesh Raj Sarraf:
I fixed this one by adding a build-dep to systemd dev library. But for
some reason, the build is failing on all architectures. But the same
builds fine in my
Package: dh-systemd
Version: 1.21
Severity: wishlist
debhelper(7) says:
COMMON DEBHELPER OPTIONS
The following command line options are supported by some debhelper
programs [...]
-Xitem, --exclude=item
Exclude an item from processing. This option may be used
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #759320 (http://bugs.debian.org/759320)
# Bug title: systemd fails to close user
On 09/01/2014 05:45 PM, Alexandre Detiste wrote:
Then, the file /etc/crontab would then not contains theses standard
boilerplate lines anymore
17 ** * * rootcd / run-parts --report /etc/cron.hourly
25 6* * * roottest -x /usr/sbin/anacron || ( cd / run-parts
--report
In native init scripts, we did a lot of check before starting and shutting
down the daemon. Things like checking the root device, or tiggering LVM
Volume Group activitation. They were easily done in shell.
What would the systemd team recommend for it ?
That probably depends on why you were
Am 01.09.2014 14:26, schrieb Michael Biebl:
Am 01.09.2014 13:37, schrieb Michael Biebl:
By quickly glancing over the package, I also noted that you ship a
systemd .service file named multipathd.service but the SysV init scripts
are named /etc/init.d/multipath-tools and
On 9/1/14, Michael Biebl bi...@debian.org wrote:
Am 01.09.2014 11:04, schrieb Chris Tillman:
Activation of org.freedesktop.systemd1 timed out
There are quite a few more D-Bus services besides
org.freedesktop.systemd1 which time out.
It seems also that all services which use Type=dbus
12 matches
Mail list logo
