Am 10.05.2014 16:18, schrieb Zack Weinberg:
> Package: systemd
> Version: 204-10
> Severity: important
>
> I have /home spread over two entire disks using btrfs (applied directly to
> the physical disks; there is no intervening dm/LVM/whatever). These disks
> have no disklabels. They are referre
tags 747629 + moreinfo unreproducible
thanks
Am 10.05.2014 16:18, schrieb Zack Weinberg:
> Package: systemd
> Version: 204-10
> Severity: important
>
> I have /home spread over two entire disks using btrfs (applied directly to
> the physical disks; there is no intervening dm/LVM/whatever). These
severity 724602 serious
thanks
Am 11.05.2014 10:13, schrieb Andreas Metzler:
> On 2013-09-25 Julian Andres Klode wrote:
>> Package: dnsmasq
>> Version: 2.66-4
>> Severity: normal
>
>> dnsmasq currently does not enable its systemd unit in postinst. It should
>> probably use dh-systemd.
>
>> The
Am 11.05.2014 18:14, schrieb Zack Weinberg:
> Well, this is frustrating: now I can't reproduce the problem either.
> (Reverted /etc/fstab to its previous state, rebooted several times
> with no problems.)
>
> To me this suggests some sort of race condition inside udev, and
> perhaps I should just
Am 11.05.2014 18:51, schrieb Tollef Fog Heen:
>
> reassign 747743 openssh-server
> thanks
>
> ]] Julian Wollrath
>
>> I have the package openssh-server installed but disabled starting the server
>> daemon via 'update-rc.d ssh disable', since I do not need it running all the
>> time. When I swit
Am 13.05.2014 22:57, schrieb Nikita Pichugin:
> Package: systemd
> Version: 204-10
> Severity: important
>
> Dear Maintainer,
>
> I use a dualboot machine with Debian and Windows 8. I want the windows
> partition to automount on boot, so I added it to the /etc/fstab. The problem
> is
> that I ca
The following assumes you run policykit 0.105
Am 13.05.2014 09:57, schrieb Martin Steigerwald:
> merkaba:/etc/polkit-1> cat
> ./localauthority/50-local.d/org.freedesktop.upower.pkla
> [Suspend/hibernate permissions]
> Identity=unix-group:sudo
> Action=org.freedesktop.upower.hibernate;org.freedes
Am 13.05.2014 22:13, schrieb Michael Biebl:
>
> The following assumes you run policykit 0.105
>
> Am 13.05.2014 09:57, schrieb Martin Steigerwald:
>> merkaba:/etc/polkit-1> cat
>> ./localauthority/50-local.d/org.freedesktop.upower.pkla
>> [Suspend/hibern
tags 747939 + fixed-upstream
thanks
Am 15.05.2014 02:30, schrieb Michael Biebl:
>> See /usr/share/polkit-1/actions/org.freedesktop.login1.policy. What you
>> are looking for is
>> org.freedesktop.login1.hibernate-multiple-sessions
>
> I've also forwarded this to
&
Am 16.05.2014 16:26, schrieb David Kalnischkies:
> Package: systemd-sysv
> Version: 204-10
> Severity: serious
> Justification: triggers a debian-policy defined dpkg error (§7.4)
> X-Debbugs-CC: pkg-sysvinit-de...@lists.alioth.debian.org
>
> Hi *,
>
> I got a report (now…) that apt segfaults in a
Hi Wouter
Am 16.05.2014 23:05, schrieb Wouter Verhelst:
>
> It might be good for logind and acpi-support to coordinate better on
> this matter. If acpi-support has already suspended the machine, there is
> no need for logind to do the same (or vice versa).
See [0]. This bug has been open for a w
Am 19.05.2014 15:02, schrieb Martin Steigerwald:
> Am Dienstag, 13. Mai 2014, 22:13:09 schrieb Michael Biebl:
>> Am 13.05.2014 09:57, schrieb Martin Steigerwald:
>> org.freedesktop.login1.hibernate-multiple-sessions
>
> This also needs the according suspend action to
Any comments from the sysvinit maintainers?
I'm willing to work on a different solution (with your help) if you
don't consider the proposed patch as sufficient.
Since this is a rather serious bug, I will upload an NMU soonish otherwise.
Regards,
Michael
--
Why is it that all of the instruments
Am 18.05.2014 17:20, schrieb Christoph Anton Mitterer:
> In contrast to that, we have "passive" dependencies which the services
> themselves usually never check (or even cannot really check) for...
> typically such, which are security relevant.
I have no idea what you mean with passive dependencie
Am 25.05.2014 23:38, schrieb Dwayne Litzenberger:
> Package: systemd
> Version: 204-10
> Followup-For: Bug #674755
> Control: affects -1 + ubuntu-dev-tools
>
> This also breaks the mk-sbuild(1) tool from the ubuntu-dev-tools
> package.
>
Please file a bug against ubuntu-dev-tools to use /dev/sh
Hi,
Am 26.05.2014 13:03, schrieb Michael Meskes:
> Hi,
>
> I'm currently updating quota for quite a bit of things. But I'm at a loss as
> to
> what to do with /etc/init.d/quota. It seems, correct me if I'm wrong, that
> systemd comes with its own binary for quotacheck, which does not implement
Am 26.05.2014 10:38, schrieb Martin-Éric Racine:
> 2014-05-25 17:01 GMT+03:00 Michael Stapelberg :
>> Martin-Éric Racine writes:
>>> The output from init.d scripts is printed to console 3 consecutive times
>>> when systemd is pid 1.
>> Can you provide a screenshot please? I don’t have that.
>
> S
Am 26.05.2014 15:10, schrieb Patrick Häcker:
> Package: systemd
> Version: 208-1
> Severity: normal
>
> Dear Maintainer,
>
> I have a file
>> /etc/sysctl.d/98-save-power.conf
> containing the line
>> vm.dirty_writeback_centisecs = 1500
> which is used as an example to describe the bug in the foll
Am 26.05.2014 19:53, schrieb Michael Biebl:
> Am 26.05.2014 15:10, schrieb Patrick Häcker:
>> Package: systemd
>> Version: 208-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> I have a file
>>> /etc/sysctl.d/98-save-power.conf
>>
Am 26.05.2014 20:50, schrieb Patrick Häcker:
> I guess the value dirty_writeback_centisecs defaults to 500. Other values
> defined via sysctl have their (suspected) default value, too.
Which other values?
--
Why is it that all of the instruments seeking intelligent life in the
universe are poi
Am 26.05.2014 20:50, schrieb Patrick Häcker:
> I guess the value dirty_writeback_centisecs defaults to 500. Other values
> defined via sysctl have their (suspected) default value, too, after boot and
> only change to the desired value after restarting the service manually as
> described. Thus, I
Am 26.05.2014 20:50, schrieb Patrick Häcker:
vm.dirty_writeback_centisecs = 1500
>>> which is used as an example to describe the bug in the following.
>>>
>>> After boot,
cat /proc/sys/vm/dirty_writeback_centisecs
>>> returns
>>> 500,
>>
>> Do you use any power management tools, like acpi
Am 28.05.2014 15:54, schrieb Patrick Häcker:
> Thanks a lot, that fixed the problem. Sorry for reporting the bug with the
> wrong package. I'll report a separate bug to pm-utils as this is not a
> laptop,
I guess it's safe to simply uninstall pm-utils in this case.
--
Why is it that all of t
Am 30.05.2014 04:11, schrieb Nikolaus Rath:
> Package: systemd
> Version: 204-8
> Severity: grave
> Justification: causes non-serious data loss
>
> 'systemctl hibernate' (and probably other methods to hibernate when
> systemd is installed, I tested only the command) hibernates the system
> even if
Am 30.05.2014 17:58, schrieb Nikolaus Rath:
>
> - new kernel is silently installed by unattended-upgrades (apparently
> this happens even when the new package breaks the ABI) and becomes the
> default to be loaded by the bootloader
> - there's no visible indication that this happened, so I hiberna
Am 30.05.2014 18:34, schrieb Nikolaus Rath:
>>
>> The problem with simply doing nothing on hibernate when
>> /run/do-not-hibernate exists, is that this is also not visible to the
>> user since there there is no API to communicate that to the user why
>> hibernate did not succeed.
>
> Well, in my c
Am 31.05.2014 14:29, schrieb Elimar Riesebieter:
> severity 739190 grave
> forwarded 739190 pkg-systemd-maintainers@lists.alioth.debian.org
> thanks
>
>
> * Elimar Riesebieter [2014-02-16 17:42 +0100]:
>
>> Package: netenv
>> Version: 0.94.3-30
>> Severity: normal
>>
>> Don't know how to debug?
Am 31.05.2014 15:09, schrieb Michael Biebl:
> That leaves netdev.
> Tbh I don't know what to do about that. The password agents [2] were
> designed to prompt for passphrases, not to select from a list from
> pre-defined values. So they are not applicable to the case.
>
>
&
Am 01.06.2014 10:05, schrieb Francois Mescam:
> After entering the password (with NL it's the same) I obtain a line on
> tty9 :
> login[...]: FAILED LOGIN (1) on '/dev/tty1' for 'UNKNOWN' user not known
> to the underlying authetication
That looks odd. Do you have more information in the log fil
Am 31.05.2014 20:24, schrieb Michael Biebl:
> severity 750019 normal
> tags 750019 + moreinfo unreproducible
> thanks
>
> Am 31.05.2014 19:42, schrieb Francois Mescam:
> I can not reproduce the issue here.
I'm running 208-1 here. Maybe that's the reason I can'
Hi Jonathan,
On Sat, May 10, 2014 at 02:16:25PM +0100, Jonathan Wiltshire wrote:
> Control: severity -1 serious
>
> Hi,
>
> On Wed, May 07, 2014 at 06:20:02PM +0100, Jakub Warmuz wrote:
> > Unfortunately, I'm *unable to boot* the system with
> > netfilter-persistent systemd service enabled!
> >
On Mon, Apr 14, 2014 at 11:42:52AM +, Sam Morris wrote:
> Package: anacron
> Version: 2.3-19
> Severity: normal
> Tags: patch
>
> Anacron currently ships a pm-utils hook script that starts the service
> when the system is resumed. pm-utils hooks are not executed when the
> system resumes, havi
Am 03.06.2014 05:43, schrieb Michael Biebl:
> I would simplify the first solution a bit though, and simply run a
> try-restart on post, i.e. something like this
>
> #!/bin/bash
> [ "$1" = "post" ] && systemctl try-restart anacron.service
Actually, bett
Am 03.06.2014 05:56, schrieb Michael Biebl:
> Am 03.06.2014 05:43, schrieb Michael Biebl:
>
>> I would simplify the first solution a bit though, and simply run a
>> try-restart on post, i.e. something like this
>>
>> #!/bin/bash
>> [ "$1" = &qu
Package: dh-systemd
Version: 1.18
Severity: important
dh_systemd_start --restart-after-upgrade generates the following code in
postinst
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
deb-systemd-invoke try-restart ModemManager.service >/dev
Hi,
Am 04.06.2014 09:34, schrieb Martin Pitt:
> brltty's systemd unit unconditionally starts the service. This
> mis-matches the behaviour of the init.d file which checks
> RUN_BRLTTY in /etc/default/brltty. The attached debdiff adjusts the
> unit to do the same. It's not pretty, but seems to work
Am 05.06.2014 18:42, schrieb Ed Swierk:
> Package: systemd
> Version: 208-1
> Severity: normal
> X-Debbugs-CC: pkg-systemd-maintainers@lists.alioth.debian.org
>
>
> Dear Maintainer,
>
> During boot, certain services with Type=oneshot are started more than
> once. The set of affected services var
Am 06.06.2014 13:56, schrieb Michael Meskes:
> Hi Michael,
>
>> I think it’d be better if you posted what you already have and what
>> problem you are trying to solve.
>
> Sure, no problem. Here's what I have:
>
> ---
> [Unit]
> Description=Check And Enable File System Quotas
> Documentation=man
Am 06.06.2014 14:01, schrieb Petr Vorel:
> Package: systemd
> Followup-For: Bug #746358
>
> Dear Maintainer,
>
> I have NFS mounted by default in my /etc/fstab and I didn't suffer to this
> bug after
> upgrade.
How do you configure your network? Do you use ifupdown vi
/etc/network/interfaces an
Are you sure you are using the new script? What kind of error do you still
encounter?
On 7. Juni 2014 23:08:06 MESZ, david wrote:
>Unfortunately the new version of initscripts (2.88dsf-53.1)
>has a modified mountnfs script which reintroduces this bug.
>
>The patch in an earlier post had fixed
Am 08.06.2014 00:37, schrieb Jason Alavaliant:
> I've just tested the latest initscripts package (2.88dsf-53.1)
>
> Unfortunately the lines in adds to /etc/network/if-up.d/mountnfs ;
>
> --
> # Skip the mountnfs hook when being triggered by the networking SysV init
> # script and
On 8. Juni 2014 12:52:25 MESZ, Cristian Ionescu-Idbohrn
wrote:
>Source: systemd
>Severity: critical
>Justification: breaks unrelated software
>
>I've chosen to keep away from systemd and systemd related packages,
>but I haven't been paying enough attention and ended up with these
>packages inst
Am 19.05.2014 11:10, schrieb Erwan David:
> Package: systemd
> Version: 204-8
> Severity: normal
>
> systemd-logind writes logs in dmesg, making it rapidly unusable to get
> boot messages.
>
> logs should be sent elsewhere.
They are sent elsewhere, namely the journal. The kernel ring buffer is
o
Am 08.06.2014 00:37, schrieb Jason Alavaliant:
> I've just tested the latest initscripts package (2.88dsf-53.1)
Jason, could you please test again with 2.88dsf-53.2?
53.1 had an embarrasing formatting error.
--
Why is it that all of the instruments seeking intelligent life in the
universe are p
Hi,
Am 12.06.2014 21:53, schrieb Michael Stapelberg:
> Hi Michael,
>
> Sorry for the late response.
>
> Michael Biebl writes:
>> I.e., it has a special case for the initial installation and uses
>> start if ! -n "$2".
>>
>> We should do the sam
Am 14.06.2014 16:04, schrieb Michael Gold:
> Package: systemd
> Version: 204-10
> Severity: critical
>
> After installing systemd today and rebooting, I saw a few lines (not
> errors) about systemd-fsck on xfs filesystems, and then I was prompted
> for dm-crypt passwords for 4 disks that are not n
Am 14.06.2014 16:55, schrieb Sven Joachim:
> Control: reassign -1 systemd-sysv 204-6
>
> On 2014-06-14 16:18 +0200, Michael Gold wrote:
>
>> Package: sysvinit-core
>> Version: 2.88dsf-53.2
>> Severity: critical
>>
>> After a failed switch to systemd today (Debian bug #751585), I tried to
>> switc
Am 14.06.2014 16:59, schrieb Michael Gold:
> I didn't retry, and since I had some difficulty recovering (see bug
> #751589) I'd rather not do it on this system. I was thinking of trying
> in a VM but that might take a while.
Just install the systemd package (but not systemd-sysv) and keep
sysvi
Am 14.06.2014 16:59, schrieb Michael Gold:
> On Sat, Jun 14, 2014 at 16:27:36 +0200, Michael Biebl wrote:
>> Am 14.06.2014 16:04, schrieb Michael Gold:
>>> Package: systemd
>>> Version: 204-10
>>> Severity: critical
>>>
>>> After installi
Am 14.06.2014 17:15, schrieb Sven Joachim:
>> This is not going to happen as this conflicts with #748355.
>
> #748355 is about the conflict with sysvinit, not with sysvinit-core.
Fair enough. Using Conflicts: sysvinit-core in systemd-sysv would have
been the correct thing to do anyway, i.e. the f
tags 751589 + unreproducible
thanks
Am 14.06.2014 18:22, schrieb Michael Gold:
> On Sat, Jun 14, 2014 at 17:34:21 +0200, Michael Biebl wrote:
>> That said, I can not reproduce the sequence of events which make
>> /sbin/init dissappear.
>>
>> I've installed system
Am 14.06.2014 18:30, schrieb Michael Gold:
> Perhaps the options I want are "quiet" in crypttab and "nofail" in
> fstab, so they'll be mounted if available. With sysvinit most of them
> actually are automounted during startup--I have a udev script that runs
> cryptdisks_start when the disks are de
Am 14.06.2014 18:31, schrieb Michael Biebl:
> That said, even with that sequence of events /sbin/init is available here.
> I'm marking the bug as unreproducible until we have steps how we can
> reproduce the issue.
>
> root@pluto:/# apt-get remove systemd
> Readin
[Hit the send button a bit too early]
Am 14.06.2014 19:34, schrieb Michael Biebl:
> As I'm not able to reproduce the issue, I'm unable to test if replacing
> Breaks with Conflicts actually fixes this particular bug you are seeing.
Michael, could you test if you can reliably rep
Am 14.06.2014 22:41, schrieb Michael Gold:
> * after printing "Welcome to emergency mode!", it took a minute or two
>before a password prompt was shown; but that prompt died (I guess)
>without accepting any keyboard input, and after another few minutes I
>got another welcome message an
tags 751623 + fixed-upstream
thanks
Am 14.06.2014 22:51, schrieb Debian Bug Tracking System:
>> retitle -2 systemd: should print reason for starting emergency shell
> Bug #751623 [systemd] systemd: opens emergency shell after prompting for
> unnecessary dm-crypt passwords
> Changed Bug title to '
Am 15.06.2014 00:02, schrieb Michael Biebl:
> tags 751623 + fixed-upstream
> thanks
>
> Am 14.06.2014 22:51, schrieb Debian Bug Tracking System:
>>> retitle -2 systemd: should print reason for starting emergency shell
>> Bug #751623 [systemd] systemd: opens emergenc
Package: systemd
Version: 208-1
Severity: normal
When running "systemctl is-enabled" for SysV-only services I get the
following error message:
sudo systemctl is-enabled mysql.service
Failed to issue method call: No such file or directory
I thought we had fixed that in the past, so this might be
Am 15.06.2014 00:50, schrieb Michael Gold:
> On Sat, Jun 14, 2014 at 23:44:42 +0200, Michael Biebl wrote:
>> Am 14.06.2014 22:41, schrieb Michael Gold:
>>> * after printing "Welcome to emergency mode!", it took a minute or two
>>>before a password prom
Am 19.06.2014 18:18, schrieb Lionel Elie Mamane:
> Package: systemd
> Version: 204-8
> Severity: normal
>
> Just switched to systemd (installed systemd-sysv), on an up-to-date
> jessie system.
>
> On reboot, I notice:
>
> Jun 19 17:53:02 fort systemd-fsck[959]: /dev/mapper/fort-root is mounted.
Am 06.05.2014 09:32, schrieb Ole Bjørn Hessen:
>
> The symptom is that the machine will not normal boot.
> On console only this text is printed in an ever loop.
> At least for 146 seconds.
>
> I then power on/off and restart/boot into recover mode (single user).
> While single user I continue the
Am 06.05.2014 03:38, schrieb c d:
> Good,
>
> But some program figured out a new ip-address, after
> /etc/network/interfaces was commented out.
>
> The "...start job for LSB" was indeed affected by the
> /etc/network/interfaces not commented out.
>
This should be fixed now by initscripts 2.88
Am 21.06.2014 17:41, schrieb Peter Gervai:
> Reboot resulted an interesting view: endless rapid (10s per second) messages
> about
> [SKIP] ordering cycle found: D-Bus System Message Bus Socket
> and that's all. Obviously nothing can be done, Ctrl-Alt-Del not yet
> functioning, no further messages,
tags 752266 + moreinfo
thanks
Am 21.06.2014 23:32, schrieb Brainslug:
> Package: systemd
> Version: 204-8
> Severity: important
>
> I'm running jessie on a Dell M4800 laptop. I modified
> /etc/systemd/logind.conf to suspend when either the power or suspend key
> is pressed.
> This part is working
reassign 752266 acpi-support-base
forcemerge 738696 752266
thanks
Am 22.06.2014 21:45, schrieb Brainslug:
> Hi Michael,
>
> thanks for the quick reply. Indeed, the acpi-support-base package was
> installed and after removing it the system seems to be behaving
> normally, i.e. it properly re
forcemerge 751845 752104
thanks
Am 19.06.2014 18:18, schrieb Lionel Elie Mamane:
> Package: systemd
> Version: 204-8
> Severity: normal
>
> Just switched to systemd (installed systemd-sysv), on an up-to-date
> jessie system.
>
> On reboot, I notice:
>
> Jun 19 17:53:02 fort systemd-fsck[959]: /
Am 16.04.2014 22:06, schrieb Tollef Fog Heen:
> ]] Michael Biebl
>
>> I remember that we had a few issues in the past. One being that the
>> journal file was blown up incredibly causing important log data to be
>> "rotated away"
>
> We might want to make
Am 23.06.2014 07:49, schrieb Uoti Urpala:
>> Then I have learned (by browsing the logs) that systemd basically
>> unsupported on a system using /usr as a separate mount. I am sure
>> (pre|post)inst haven't mentioned that.
>
> Systemd does support setups where /usr is a separate partition, but such
Am 25.06.2014 14:41, schrieb Christoph Anton Mitterer:
> Package: systemd
> Version: 204-11
> Severity: important
>
>
> Hey.
>
> Not sure whether this is an issue of systemd or udev (probably even the
> later) but since both are in the same source package anyway... ;)
>
> Since 204-11 my system
reassign 752765 src:systemd
forcemerge 717491 752765
thanks
Am 26.06.2014 14:02, schrieb Tomas Janousek:
> Package: systemd
> Version: 204-8
> Severity: normal
>
> The manpage for systemd-suspend.service(8) advises users to put scripts in
> /usr/lib/systemd/system-sleep/, but these are ignored.
reassign 752744 xfce4-session
thanks
Am 26.06.2014 09:22, schrieb Norbert Preining:
> Package: systemd
> Version: 204-12
> Severity: normal
>
> HI systemd maintainers,
>
> everytime there is an upgrade of systemd, the suspend/reboot
> functionality in XFCE is just gone. No reaction, no change.
Am 13.06.2014 14:35, schrieb Salvo Tomaselli:
> Package: systemd
> Version: 204-10
> Severity: normal
>
> Dear Maintainer,
>
> due to some filesystem problems, everything on my system except for /home, was
> mounted as read-only.
> This caused journald to flood me with error messages, preventing
Am 27.06.2014 20:10, schrieb Lennart Poettering:
> Well, I know that much. But a service which needs to be restarted on
> cases like this sounds wrong. Thats a hack really. The service should
> just watch time changes and react correctly to that. i.e. use
> TFD_TIMER_CANCEL_ON_SET. THis will report
Am 18.02.2014 23:25, schrieb Michael Biebl:
> Package: systemd
> Version: 204-7
> Severity: wishlist
>
> Since dracut enables systemd support in its initramfs, we should
> probably trigger and update of the initramfs whenever systemd is
> installed/updated/removed.
>
>
Am 27.11.2013 11:27, schrieb Alessandro Ghedini:
>> To reproduce the issue, one can follow those steps:
>> - Make sure rsyslog is installed and running.
>> status: step1.txt
>> - rm -f /etc/systemd/system/syslog.service
>> - systemctl daemon-reload
>> status: step2.txt
>> - re-create symlink: s
Am 28.06.2014 18:32, schrieb Andrew Shadura:
> Hello,
>
> On Fri, 27 Jun 2014 21:13:40 +0200
> Michael Biebl wrote:
>
>> the udev package ships a udev rule [1], which runs ifup $INTERFACE via
>> the net.agent helper.
>
>> This seems to create a race with t
Hi there,
Am 29.06.2014 09:50, schrieb Michael Meskes:
>> Looking more closely, it seems the quota package only suggests the
>> rpcbind package, yet the quotarpc.service contains:
>>
>> Requires=rpcbind.service
>> After=rpcbind.service
>>
>> Requires means, the service will fail to start if the de
Package: dh-systemd
Version: 1.19
Am 29.06.2014 11:49, schrieb Michael Biebl:
> So quotarpc.service is only supposed to run if rpcbind is installed?
>
> I think what you want here then is Wants/After + a Condition [1].
> i.e.
>
> [Unit]
> Wants=rpcbind.service
&g
Am 29.06.2014 13:39, schrieb Michael Meskes:
>> Btw, I noticed that quotarpc is not enabled by default. Instead
>> dh_systemd creates two sections for quota.service
>>
>> # ls debian/*.service
>> debian/quota.quotarpc.service debian/quota.service
>
> This seems to be the result of a recent change
Am 01.07.2014 13:52, schrieb Tzafrir Cohen:
> Package: systemd
> Version: 44-11+deb7u4
> Severity: normal
>
> Dear Maintainer,
> I have installed systemd on this Wheezy laptop as well as on a test
> Jessie system and on both systems the system failed to later boot due to
> the same reason: the sys
Hi Steve,
this is a heads-up that we intend to upload 208 from experimental to
unstable as soon as 204-14 has migrated to testing.
This should happen within the next week.
I guess this will make this bug sort-of RC, but I'll leave it up to you
to bump it accordingly.
Will notify you again, once
Am 01.07.2014 21:20, schrieb Steve Langasek:
> Hi Michael,
>
> On Tue, Jul 01, 2014 at 05:37:55PM +0200, Michael Biebl wrote:
>> Am 01.07.2014 17:20, schrieb Thomas Weber:
>>> Or, taking a different perspective: now that the issue is known, what is
>>> done to
This affects both packages.
>> reassign 751589 systemd 204-6
> Bug #751589 {Done: Michael Biebl }
> [sysvinit-core,systemd-sysv] sysvinit-core: /sbin/init missing after
> switching from systemd to sysvinit
> Bug reassigned from package 'sysvinit-core,systemd-sysv' to '
Am 02.07.2014 16:15, schrieb VALETTE Eric OLNC/OLPS:
>
>> So we are probably hunting a kernel/systemd dependency that is not
>> listed in the page I indicated.
> Or I should go back to school and take a reading course :-(
> CONFIG_FHANDLE was not set on my Kernel (in the meantime I also upgraded
>
reassign 753379 udev
forcemerge 713877 753379
thanks
Am 02.07.2014 16:30, schrieb Holger Levsen:
> On Dienstag, 1. Juli 2014, Francewhoa wrote:
>> What led up to the situation?
>> • Steps to reproduce bug
>> 1. Insert any CD or DVD
>> 2. The CD or DVD is not automatically detected by the system
>
Am 02.07.2014 17:23, schrieb VALETTE Eric OLNC/OLPS:
> On 07/02/2014 05:01 PM, Michael Biebl wrote:
> Never saw a warning and never failed to install anything! I checked the
> test is there in 208 too and it is.
> I even did extract the code and tested it:
>
> needed_sym
Am 03.07.2014 11:16, schrieb Sam Morris:
> Package: systemd
> Version: 204-8~bpo70+1
> Severity: normal
>
> My desktop has been up for 31 days. Today I noticed I could no longer connect
>
>
Am 03.07.2014 09:09, schrieb VALETTE Eric OLNC/OLPS:
> Sorry this was not clear, I have just checked the scripts works and I did on
> kernel that had the CONFIG_FHANDLE already. So I do not understand why I
> never
> saw a warning.
Most likely the version you installed did not have this check.
Am 03.07.2014 12:33, schrieb Michael Biebl:
> Am 03.07.2014 09:09, schrieb VALETTE Eric OLNC/OLPS:
>> Sorry this was not clear, I have just checked the scripts works and I did on
>> kernel that had the CONFIG_FHANDLE already. So I do not understand why I
>> never
>&g
Am 03.07.2014 12:55, schrieb Matthias Urlichs:
> Package: systemd
> Version: 208-5
> Severity: normal
>
> While updating, systemd was updated before glibc.
>
> Needless to say, this does not work at all.
>
> # aptitude(wd: ~)
> Reading changelogs...
> apt-listchanges: Mailing smurf-chan.
Am 03.07.2014 13:03, schrieb Sam Morris:
> On Thu, Jul 03, 2014 at 12:30:14PM +0200, Michael Biebl wrote:
>> If dbus is running (and it apparently is), then it should be the process
>> listening on /var/run/dbus/system_bus_socket.
>
> I'm not sure about that... on an
Am 03.07.2014 13:56, schrieb Jakub Wilk:
> systemd-sysv was unpacked, but not configured yet. At this point, its
> dependencies were not required to be satisfied. So from POV of the
> package manager everything is in order here.
>
> Perhaps a Pre-Depends is missing somewhere; but it's hard to tel
Am 03.07.2014 13:55, schrieb Sven Joachim:
> It probably needs to use Pre-Depends to ensure that it's working during
> upgrades. Note that the same holds also for sysvinit-core, although it
> is currently less likely to hit the bug (it has "Priority: required" and
> does not exist in wheezy).
>
Am 03.07.2014 14:26, schrieb Ansgar Burchardt:
> Most essential packages should have this problem. I checked bash and it
> indeed has
>
> Pre-Depends: dash (>= 0.5.5.1-2.2), libc6 (>= 2.15), libtinfo5
>
> which comes from
>
> Pre-Depends: dash (>= 0.5.5.1-2.2), ${shlibs:Pre-Depends}, ${misc
Am 03.07.2014 14:35, schrieb Michael Biebl:
> Am 03.07.2014 14:26, schrieb Ansgar Burchardt:
>
>> Most essential packages should have this problem. I checked bash and it
>> indeed has
>>
>> Pre-Depends: dash (>= 0.5.5.1-2.2), libc6 (>= 2.15), libtinfo5
>&g
severity 753606 important
thanks
Hi Łukasz,
Am 03.07.2014 16:24, schrieb Łukasz Stelmach:
> Package: libsystemd-journal-dev
> Severity: grave
>
> Dear Maintainer,
>
> I've tried to install libsystemd-journal-dev=204-8~bpo70+1 from the
> wheezy-backports (libsystemd-id128-dev appears to have the
Am 03.07.2014 16:17, schrieb Michael Biebl:
> Attached is a proposed patch.
feedback on the patch would be appreciated.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signat
Am 03.07.2014 20:57, schrieb Michal Suchanek:
> Package: systemd
> Version: 204-14
> Followup-For: Bug #748056
>
> Hello,
>
> since this is a 'feature' I expect this is still present.
>
> I encountered this problem when one of my drive cables went loose and
> the drive became inaccessible.
>
>
Hi Gerrit,
Am 04.07.2014 13:50, schrieb Gerrit Pape:
> I hereby ask for help to add systemd support to these packages.
We (pkg-systemd team) can help you with that.
Let's follow up on the pkg-systemd mailing list.
In most cases adding a .service file is pretty simple.
If it's only about startin
Am 04.07.2014 14:34, schrieb Michael Biebl:
> Hi Gerrit,
>
> Am 04.07.2014 13:50, schrieb Gerrit Pape:
>> I hereby ask for help to add systemd support to these packages.
>
> We (pkg-systemd team) can help you with that.
>
> Let's follow up on the pkg-systemd
1 - 100 of 1596 matches
Mail list logo
