On 2017-03-23 14:12 -0300, Felipe Sateler wrote:
> However, I see the following in cached_setup_font:
>
> setfont '/etc/console-setup/cached_Lat15-Fixed16.psf.gz'
>
> if ls /dev/fb* >/dev/null 2>/dev/null; then
> for i in /dev/vcs[0-9]*; do
> { :
> setfont '/etc/console-set
On 2017-01-15 16:14 +0100, Pascal Dormeau wrote:
> Systemd does not mount tmpfs file systems with the correct size when
> the size is expressed in % of physical RAM in /etc/fstab.
>
> I guess it does not read at all the % character, and the size is read in
> bytes. size=5% or size=10% results into
On 2016-11-04 13:23 +0100, Sven Joachim wrote:
> Package: udev
> Version: 232-1
> Severity: important
>
> Upon upgrading from 231-10, systemd-udevd.service times out. Systemd
> tries to restart it in an endless loop, but to no avail.
> [...]
> Architecture: i386 (x86
Package: udev
Version: 232-1
Severity: important
Upon upgrading from 231-10, systemd-udevd.service times out. Systemd
tries to restart it in an endless loop, but to no avail.
,
| $ systemctl status systemd-udevd.service
| ● systemd-udevd.service - udev Kernel Device Manager
|Loaded: load
On 2016-03-13 23:09 -0400, Pat Hooper wrote:
> Package: systemd
> Version: 229-2
>
> Including a slash (/) in a partition label leads to systemd not being able
> to check the partition for errors. This in turn lead to problems accessing
> the partition (with no obvious acknowledgement of problems
On 2014-12-27 02:44 +0100, Michael Biebl wrote:
> It looks like we won't get initramfs-tools 0.118 with usr-mount support
> in the initramfs, as this created quite a few regressions which need to
> be dealt with first.
>
> I therefore think we need to workaround this issue in systemd and make
> su
Hi everyone,
with the latest util-linux in unstable depending on init-system-helpers,
perl is now part of the essential package closure set, bloating minimal
chroots by some 30 Megabytes.
Cheers,
Sven
___
Pkg-systemd-maintainers mailing list
Pkg
On 2014-09-18 16:10 +0200, Uoti Urpala wrote:
> I checked that this did not happen on a system I just updated from 204
> to 215; contents of /run/user/1000 remained unchanged after the upgrade.
Not here, upgrading from 208 to 215.
> Are you sure that the upgrade actually *removed* contents? A po
On 2014-07-03 13:22 +0200, Michael Biebl wrote:
> 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: ~)
>>
On 2014-06-14 19:37 +0200, Michael Biebl wrote:
> [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
Control: reopen -1
Closing bugs which render the system unbootable seems a bit premature to me.
On 2014-06-14 17:03 +0200, Michael Biebl wrote:
> Am 14.06.2014 16:55, schrieb Sven Joachim:
>> Control: reassign -1 systemd-sysv 204-6
>>
>> On 2014-06-14 16:18 +020
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
> switch back to sysvinit but found /sbin/init missing after a r
On 2014-05-16 17:33 +0200, Michael Biebl wrote:
> Incidentally we also discussed dropping the Conflicts from systemd-sysv
> and only keeping the Replaces (and this is also what sysvinit-core has
> done).
Which has its own problems, since nothing stops the admin from shooting
themselves in the foo
13 matches
Mail list logo
