Am 15.01.2017 um 01:43 schrieb Michael Biebl:
> We have three options
a/ b/ c/ d/
Apparently I can't count :-)
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
___
Source: systemd
Version: 232-10
Severity: important
While investigating #851412, I noticed that we have a couple of buildds,
where the test-suite fails but we ignore the error, because
/etc/machine-id does not exist.
In case of mips64el this did hide a real bug.
As init is no longer essential, th
这是一封 HTML 格式的邮件，请以网页方式查看邮件。
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processing commands for cont...@bugs.debian.org:
> forcemerge 792894 819156
Bug #792894 [isc-dhcp-server] systemd units for dhcp server (addressing ipv4
and ipv6)
Bug #792894 [isc-dhcp-server] systemd units for dhcp server (addressing ipv4
and ipv6)
Marked as found in versions isc-dhcp/4.3.1-6+d
Package: systemd
Version: 232-8
Severity: minor
File: /lib/systemd/systemd-journald
Hello,
W dniu 14.01.2017 o 18:58, Michael Biebl pisze:
> Am 14.01.2017 um 18:40 schrieb Jarek Kamiński:
>> #771122 explains that journald can't be restarted, as all stdout and
>> stderr fds used by daemons to log
Hi Jarek
Am 14.01.2017 um 18:40 schrieb Jarek Kamiński:
> Hello,
>
> #771122 explains that journald can't be restarted, as all stdout and
> stderr fds used by daemons to log would be lost. If I understand
> correctly, that was fixed in v219[1] though:
>> * systemd now provides a way to st
Hello,
#771122 explains that journald can't be restarted, as all stdout and
stderr fds used by daemons to log would be lost. If I understand
correctly, that was fixed in v219[1] though:
> * systemd now provides a way to store file descriptors
> per-service in PID 1.This is useful
Am 14.01.2017 um 18:02 schrieb Michael Biebl:
> binutils_2.27.90.20170114-1. Building in stretch chroot though was
> successful. So my observation is:
>
> binutils_2.27.90.20170114-1: fails
> binutils_2.27.90.20170113-1: fails
> binutils_2.27.51.20161220-1: ok
>
> So it looks like a mips related
Source: systemd
Version: 232-10
Severity: serious
User: debian-m...@lists.debian.org
Usertags: mips-port
Hi mips porters,
the latest upload of systemd FTBFS on mips* [1]. Contrary to what the
buildd status page shows, mips64el is also affected. The build chroot on
mips64el did not have a /etc/mac
Michael Fritscher writes:
> The problem is that if the system is on battery both on going to
> suspend and waking up, in 90% of the cases the system goes into
> suspend immediately again (few seconds). On the second try it works.
> I didn't set the system to go into suspend after some time...
Do y
Package: systemd
Version: 232-8
Severity: important
The box is running stretch, updated from jessie yesterday.
When the box shuts down, it unmounts all the filesystems.
When it gets to /var there is a warning: Failed unmounting /var
I wrote a little wrapper script to put in place of /bin/umou
While researching the issue, I also came across this blog[1] about
ensuring btrfs scan completes before mounts
Does that already happen by default in the latest versions of systemd on
Debian?
https://blogs.gentoo.org/remi/2014/12/05/gentoo-btrfs-arrays-and-systemd-a-public-service-announcement
I've posted the details below in the upstream bug report on Github as well.
This may be applicable to jessie users who have btrfs-tools v3.17-1.1
and/or manually created the /lib/udev/rules.d/99-btrfs.rules file
As a potentially workaround/solution, users can upgrade to btrfs-progs
v4.7.3-1 from
The systemd package from jessie-backports was installed, same problem
The whole system has been updated to stretch, the problem persists with
the systemd 230-7 package
As discussed in the upstream bug report, I've tested wrapping the mount
call with a script that uses strace, it shows that the m
Processing commands for cont...@bugs.debian.org:
> reassign 851253 libtool
Bug #851253 [src:systemd] libtool misdetects nios2 as os2
Bug reassigned from package 'src:systemd' to 'libtool'.
No longer marked as found in versions systemd/232-9.
Ignoring request to alter fixed versions of bug #851253
Control: reassign libtool
Control: retitle -1 libtool misdetects nios2 as os2
Control: tags -1 =
Control: affects -1 + src:systemd
On Fri, Jan 13, 2017 at 07:28:30PM +0100, Helmut Grohne wrote:
> Still I am very much interested in finding the real cause. Given that
> you suspect libtool, I went ah
Processing control commands:
> reassign libtool
Unknown command or malformed arguments to command.
> retitle -1 libtool misdetects nios2 as os2
Bug #851253 [src:systemd] bootstrap build failure: install: cannot stat
'build-deb/.libs/test-udev': No such file or directory
Changed Bug title to 'lib
17 matches
Mail list logo
