Source: systemd
Version: 232-10
Severity: serious
User: [email protected]
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/machine-id, which is why the test suite was
non-fatal [2]. If you install systemd in the chroot (which sets up
/etc/machine-id) mips64el fails exactly like mips and mipsel, i.e. the
following two tests segfault:
../build-aux/test-driver: line 107: 26379 Segmentation fault "$@" > $log_file 2>&1
FAIL: test-bus-marshal
../build-aux/test-driver: line 107: 27445 Segmentation fault "$@" > $log_file 2>&1
FAIL: test-libsystemd-sym
Building the package on a porter pox (eller: mipsel, mips64el, minkus:
mips), the problem is 100% reproducible.
dmesg shows
[7368858.796075]
do_page_fault(): sending SIGSEGV to test-bus-marsha for invalid read access from 000000000064658b
[7368858.806215] epc = 0000000077e19058 in
[7368858.829057] libsystemd-shared-232.so[77dda000+180000]
[7368858.832726] ra = 0000000077e19078 in
[7368858.845049] libsystemd-shared-232.so[77dda000+180000]
[7368895.490458]
do_page_fault(): sending SIGSEGV to test-libsystemd for invalid read access from 000000000064658b
[7368895.500588] epc = 0000000077b85f44 in
[7368895.524124] libsystemd.so.0.17.0[77b77000+82000]
[7368895.527490] ra = 0000000077b85f64 in
[7368895.536107] libsystemd.so.0.17.0[77b77000+82000]
The initial test builds on the porter machines were using
binutils_2.27.90.20170113-1. As I suspected a binutils problem, I
upgraded to the recently uploaded
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 regression in binutils at a first
glance. In the past, systemd built reasonably reliably on mips* [3].
Dear mips porters, it would be great if you can have a look. Can you
confirm these findings or is there something else causing these issues?
I've also CCed the binutils maintainers so they are aware of this
problem. Maybe they have an idea what's going wrong.
Regards,
Michael
[1] https://buildd.debian.org/status/package.php?p=systemd&suite=sid
[2] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules#n357
[3] https://buildd.debian.org/status/logs.php?pkg=systemd&arch=mipsel
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.126
ii udev 232-10
-- no debconf information
Acknowledgement sent
to Michael Biebl <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Sat, 14 Jan 2017 17:18:03 GMT) (full text, mbox, link).
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 regression in binutils at a first
> glance. In the past, systemd built reasonably reliably on mips* [3].
A notable difference (aside from binutils) between the sid and stretch
chroot is gcc-6, which is at version 6.2.1-5 in stretch and 6.3.0-2 in
unstable.
I couldn't test this combination (old binutils + new gcc) on the porter
boxes though.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Acknowledgement sent
to Christian Hofstaedtler <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Sun, 15 Jan 2017 13:15:05 GMT) (full text, mbox, link).
Subject: Re: #851412: libsystemd segfaults on mips64el
Date: Sun, 15 Jan 2017 14:12:06 +0100
Control: affects -1 + pdns pdns-recursor
Hi,
pdns and pdns-recursor link against libsystemd, and this bug causes
both of them to just segfault on startup on mips64el.
Tiny reproducer:
(sid_mips64el-dchroot)zeha@eller:~$ cat foo.c
int main() {
}
(sid_mips64el-dchroot)zeha@eller:~$ make foo LDFLAGS=-lsystemd
cc -lsystemd foo.c -o foo
(sid_mips64el-dchroot)zeha@eller:~$ gdb --args foo
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
This GDB was configured as "mips64el-linux-gnuabi64".
Type "show configuration" for configuration details.
Reading symbols from foo...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/zeha/foo
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mips64el-linux-gnuabi64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (warning: GDB can't find the start of the function at 0xfff7f2fd27.
GDB is unable to find the start of the function at 0xfff7f2fd27
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0xfff7f2fd27 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
fp=0x1) at iofclose.c:48
48 iofclose.c: No such file or directory.
(gdb) bt full
#0 _IO_new_fclose (fp=0x1) at iofclose.c:48
status = <optimized out>
#1 0x000000fff7f2fd28 in ?? () from /lib/mips64el-linux-gnuabi64/libsystemd.so.0
No symbol table info available.
(gdb) quit
A debugging session is active.
Inferior 1 [process 11890] will be killed.
Quit anyway? (y or n) y
(sid_mips64el-dchroot)zeha@eller:~$ ls -la /etc/machine-id
ls: cannot access '/etc/machine-id': No such file or directory
PS: libsystemd does not appear to have a -dbgsym package.
--
christian hofstaedtler <[email protected]>
Acknowledgement sent
to Michael Biebl <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Sun, 15 Jan 2017 18:12:03 GMT) (full text, mbox, link).
Am 15.01.2017 um 14:12 schrieb Christian Hofstaedtler:
>
> PS: libsystemd does not appear to have a -dbgsym package.
>
It does, at least on amd64
libsystemd0-dbgsym:
Installed: (none)
Candidate: 232-10
Version table:
232-10 500
500 http://debug.mirrors.debian.org/debian-debug
unstable-debug/main amd64 Packages
Did you miss the "0" ?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Acknowledgement sent
to Christian Hofstaedtler <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Sun, 15 Jan 2017 18:18:03 GMT) (full text, mbox, link).
Subject: Re: Bug#851412: #851412: libsystemd segfaults on mips64el
Date: Sun, 15 Jan 2017 19:15:24 +0100
* Michael Biebl <[email protected]> [170115 19:09]:
> Am 15.01.2017 um 14:12 schrieb Christian Hofstaedtler:
> > PS: libsystemd does not appear to have a -dbgsym package.
> >
>
> It does, at least on amd64
>
> libsystemd0-dbgsym:
> Installed: (none)
> Candidate: 232-10
> Version table:
> 232-10 500
> 500 http://debug.mirrors.debian.org/debian-debug
> unstable-debug/main amd64 Packages
>
> Did you miss the "0" ?
No; appears to be some other, unidentified issue with the mips64el
schroot on eller.d.o.
Best,
-ch
--
,''`. Christian Hofstaedtler <[email protected]>
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
Added indication that 851412 affects gnome-online-accounts and xrdp
Request was from Christian Hofstaedtler <[email protected]>
to [email protected].
(Mon, 16 Jan 2017 16:15:06 GMT) (full text, mbox, link).
Acknowledgement sent
to gregor herrmann <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Tue, 17 Jan 2017 14:27:02 GMT) (full text, mbox, link).
Subject: Re: Bug#851412: #851412: libsystemd segfaults on mips64el
Date: Tue, 17 Jan 2017 15:25:07 +0100
Control: affects -1 src:iodine
On Sun, 15 Jan 2017 14:12:06 +0100, Christian Hofstaedtler wrote:
> Control: affects -1 + pdns pdns-recursor
>
> pdns and pdns-recursor link against libsystemd, and this bug causes
> both of them to just segfault on startup on mips64el.
I'm pretty sure that the build failure of iodine on mips64el:
https://buildd.debian.org/status/fetch.php?pkg=iodine&arch=mips64el&ver=0.7.0-7&stamp=1484496165
is caused by the same issue. ("-l systemd" comes from the `sh ../src/osflags Linux link`
in the last line before the segfault.)
Cheers,
gregor
--
.''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- BOFH excuse #123: user to computer ratio too high.
Acknowledgement sent
to Michael Biebl <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Wed, 18 Jan 2017 08:21:08 GMT) (full text, mbox, link).
clone 851412 -1
reassign -1 binutils
forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21054
retitle -1 Forced local symbol rearranging messes up GOT
Hi James
Am 17.01.2017 um 12:18 schrieb James Cowgill:
> On 17/01/17 09:10, Michael Biebl wrote:
>> Am 17.01.2017 um 10:02 schrieb Michael Biebl:
>>> Hi there,
>>>
>>> as additional input, please have a look at [1] which just recently
>>> popped up. There seem to be still unresolved issues with binutils on
>>> mips*.
>>
>> I haven't reassigned this bug report to binutils yet, as I wanted to
>> have confirmation from the mips porters that it's a binutils bug.
>> They sort-of already confirmed it on IRC but wanted to look into it more
>> closely first. In any case, I've CCed them, so maybe they can respond to
>> #850887 or #851412
>
> I had a closer look yesterday and it looks like a bug in the gold
> linker. You may be able to workaround it by using the bfd linker on mips.
>
> Upstream bug:
> https://sourceware.org/bugzilla/show_bug.cgi?id=21054
Thanks a lot for your input and for having a look at this issue.
We had a discussion on #debian-release, which I'm quoting for
completeness sake:
<mbiebl> aurel32: are we sure systemd is the only package affected by this?
<aurel32> mbiebl: no it's not only systemd
<aurel32> mbiebl: there are some conditions to have the issue, which is
to use the gold linker
<aurel32> so that's not that many packages given bfd is the default
<aurel32> in addition you need to have symbols with hidden visibility
<aurel32> so clearly we'll have to rebuild a few packages when it's
fixed on the binutils side, but we don't have 2.5 weeks of binaries
<nthykier> aurel32: can we easily compile a list of "gold linker" consumers?
<aurel32> mbiebl: i think having the workaround in systemd will help to
not accumulate too much packages in the queue
<mbiebl> aurel32: I guess as a first step, I'll clone the current
systemd bug and reassign it binutils
<aurel32> nthykier: 1) we can parse the build logs from the last 3 weeks
<aurel32> nthykier: 2) i think there is a way to identify the broken
binaries
<mbiebl> aurel32: and I'll apply the workaround for systemd
<aurel32> mbiebl: ok, thanks
<mbiebl> ifneq ($(filter $(DEB_BUILD_ARCH), mips mipsel mips64el),)
<mbiebl> export DEB_LDFLAGS_MAINT_APPEND = -Wl,-fuse-ld=bfd
<mbiebl> endif
<mbiebl> does that look ok?
<aurel32> it looks fine to me
We plan on uploading src:systemd today with this workaround applied
until binutils is properly fixed.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Acknowledgement sent
to YunQiang Su <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Wed, 18 Jan 2017 08:51:05 GMT) (full text, mbox, link).
Subject: Re: Bug#851412: FTBFS on mips*, tests fail with SIGSEGV
Date: Wed, 18 Jan 2017 16:46:51 +0800
On Sun, Jan 15, 2017 at 1:15 AM, Michael Biebl <[email protected]> wrote:
> 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 regression in binutils at a first
>> glance. In the past, systemd built reasonably reliably on mips* [3].
>
> A notable difference (aside from binutils) between the sid and stretch
> chroot is gcc-6, which is at version 6.2.1-5 in stretch and 6.3.0-2 in
> unstable.
> I couldn't test this combination (old binutils + new gcc) on the porter
> boxes though.
>
I tried to build a package libsystemd0-dbgsym, and test it with gdb,
it seems all binary linked with libsystemd will fail.
root@thor:/tmp# gdb /usr/bin/top
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips64el-linux-gnuabi64".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/top...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/top
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (fp=0x1) at iofclose.c:48
48 iofclose.c: No such file or directory.
(gdb) bt
#0 _IO_new_fclose (fp=0x1) at iofclose.c:48
#1 0x000000fff7c96d28 in _init () from
/lib/mips64el-linux-gnuabi64/libsystemd.so.0
#2 0x000000fff7fdb9d0 in call_init (l=0xfff7fc4120,
argc=argc@entry=1, argv=argv@entry=0xfffffff5c8,
env=env@entry=0xfffffff5d8) at dl-init.c:58
#3 0x000000fff7fdbba8 in call_init (env=0xfffffff5d8,
argv=0xfffffff5c8, argc=1, l=<optimized out>) at dl-init.c:30
#4 _dl_init (main_map=0xfff7fff848, argc=<optimized out>,
argv=0xfffffff5c8, env=0xfffffff5d8) at dl-init.c:120
#5 0x000000fff7fca450 in _dl_start_user () from /lib64/ld.so.1
Backtrace stopped: frame did not save the PC
It seems that binutils generate bad shared lib.
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
--
YunQiang Su
Acknowledgement sent
to YunQiang Su <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <[email protected]>.
(Wed, 18 Jan 2017 08:54:06 GMT) (full text, mbox, link).
Subject: Re: Bug#851412: FTBFS on mips*, tests fail with SIGSEGV
Date: Wed, 18 Jan 2017 16:50:02 +0800
On Sun, Jan 15, 2017 at 1:15 AM, Michael Biebl <[email protected]> wrote:
> 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 regression in binutils at a first
>> glance. In the past, systemd built reasonably reliably on mips* [3].
>
> A notable difference (aside from binutils) between the sid and stretch
> chroot is gcc-6, which is at version 6.2.1-5 in stretch and 6.3.0-2 in
> unstable.
> I couldn't test this combination (old binutils + new gcc) on the porter
> boxes though.
>
I tried to build a package libsystemd0-dbgsym, and test it with gdb,
it seems all binary linked with libsystemd will fail.
root@thor:/tmp# gdb /usr/bin/top
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips64el-linux-gnuabi64".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/top...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/top
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (fp=0x1) at iofclose.c:48
48 iofclose.c: No such file or directory.
(gdb) bt
#0 _IO_new_fclose (fp=0x1) at iofclose.c:48
#1 0x000000fff7c96d28 in _init () from
/lib/mips64el-linux-gnuabi64/libsystemd.so.0
#2 0x000000fff7fdb9d0 in call_init (l=0xfff7fc4120,
argc=argc@entry=1, argv=argv@entry=0xfffffff5c8,
env=env@entry=0xfffffff5d8) at dl-init.c:58
#3 0x000000fff7fdbba8 in call_init (env=0xfffffff5d8,
argv=0xfffffff5c8, argc=1, l=<optimized out>) at dl-init.c:30
#4 _dl_init (main_map=0xfff7fff848, argc=<optimized out>,
argv=0xfffffff5c8, env=0xfffffff5d8) at dl-init.c:120
#5 0x000000fff7fca450 in _dl_start_user () from /lib64/ld.so.1
Backtrace stopped: frame did not save the PC
It seems that binutils generate bad shared lib.
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
--
YunQiang Su
Reply sent
to Michael Biebl <[email protected]>:
You have taken responsibility.
(Wed, 18 Jan 2017 13:24:04 GMT) (full text, mbox, link).
Notification sent
to Michael Biebl <[email protected]>:
Bug acknowledged by developer.
(Wed, 18 Jan 2017 13:24:04 GMT) (full text, mbox, link).
Source: systemd
Source-Version: 232-11
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 18 Jan 2017 12:38:54 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-11
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers <[email protected]>
Changed-By: Michael Biebl <[email protected]>
Description:
libnss-myhostname - nss module providing fallback resolution for the current hostname
libnss-mymachines - nss module to resolve hostnames for local container instances
libnss-resolve - nss module to resolve names via systemd-resolved
libnss-systemd - nss module providing dynamic user and group name resolution
libpam-systemd - system and service manager - PAM module
libsystemd-dev - systemd utility library - development files
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
systemd - system and service manager
systemd-container - systemd container/nspawn tools
systemd-coredump - tools for storing and retrieving coredumps
systemd-journal-remote - tools for sending and receiving remote journal logs
systemd-sysv - system and service manager - SysV links
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 851412851445851475851492851688
Changes:
systemd (232-11) unstable; urgency=medium
.
[ Martin Pitt ]
* Fix RestrictAddressFamilies=
Backport upstream fix for setting up seccomp filters to fix
RestrictAddressFamilies= on non-amd64 architectures. Drop the hack from
debian/rules to remove this property from unit files.
See #843160
* Use local machine-id for running tests during package build.
Since "init" and thus "systemd" are not part of debootstrap any more,
some buildd chroots don't have an /etc/machine-id any more. Port the old
Add-env-variable-for-machine-ID-path.patch to the current code, use a
local machine-id again, and always make test suite failures fatal.
(Closes: #851445)
.
[ Michael Biebl ]
* gpt-auto-generator: support LUKS encrypted root partitions
(Closes: #851475)
* Switch to bfd linker on mips*
The gold linker is currently producing broken libraries on mips*
resulting in segfaults for users of libsystemd. Switch to bfd until
binutils has been fixed. (Closes: #851412)
* Revert "core: turn on specifier expansion for more unit file settings"
The expansion of the % character broke the fstab-generator and
specifying the tmpfs size as percentage of physical RAM resulted in the
size being set to 4k. (Closes: #851492)
* Drop obsolete Conflicts, Breaks and Replaces
* Require systemd-shim version which supports v232.
See #844785
.
[ Ondřej Nový ]
* Redirect try-restart in init-functions hook (Closes: #851688)
Checksums-Sha1:
9af57d671256e028d31b84acf3e9ae0e61c4bfd6 4657 systemd_232-11.dsc
93213b4925191090d9a72e7a62c26119a533b1f5 165696 systemd_232-11.debian.tar.xz
Checksums-Sha256:
58afdac0dc043c418d89a4e78145b29436f9669900420903bbc7a9c05422e527 4657 systemd_232-11.dsc
36b8dfd74dd934b6119883a575eb03732f8f05710137767a83a82405ee09dfbd 165696 systemd_232-11.debian.tar.xz
Files:
8e63bcc7aa9bafa78ffd3cdd53b9bdcd 4657 admin optional systemd_232-11.dsc
8448a426aef454dbe34797ab641c2c68 165696 admin optional systemd_232-11.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlh/ZuAACgkQauHfDWCP
ItyxNQ/+Jr/jv9Xu+l0jjmZd7WhnpGQpUMEx1adIHnxlpBansj+cGv60FXp9oECz
HUmKB/vOdNP3PqnA4k+rY8fJAPTqTATYNe1jBj2AkXKO5QYh6NQipyjOuXPF8XP1
XwyEIJ/GTtFganaa1f6xqpqraTQ5XjBzM98blTfkXnYHEq/XDP2m323WtNYOZek1
r41jE9iPPzUGI90HPBj4Xrg0QWxkmwOCUY3n7ctLp4/3lfYSgB+Hed2QbsNLfMEX
3FFPDAwgsMEdyPm5V9uYXOGzRBckS2W3qDwf5ws95s6o3xANwILZhSp6PUgV5iSO
HrFxWpQgu+JyS3BJm0mmO5zKa/Pwha8h+rYtvSvy+prYE70FIky6FOEqyeU44qXk
rQ/HJsLQu38FBc/kBtWY6KhTWvu1QjikwlkwJWmN+O0gqKGj3aSYt6JXo1EMSL/a
TJh6MaWVE2QRE7uo/4amV3Kvp47D2bsHp2gTscgmc4UsjBWa6vBd1IOVzxxoFYVX
iA5F1zzkx4Kssz2JGIjxpV5Y0IZ0w2lD0ZCLADj5KVX22A4Rj8BinMlKrVvxasWj
N4RtGTmY6J45oNVSnIqJqhjMdqrEXMUBdKhYtf91UweGqLP7ZLMzhnnAsOrC0ao8
99VDjkrxbgFts6gkCQH+UZ3yf9fFshRezITRK5Z2XwK8D71zifo=
=t0iK
-----END PGP SIGNATURE-----
Reply sent
to Michael Biebl <[email protected]>:
You have taken responsibility.
(Wed, 18 Jan 2017 13:24:05 GMT) (full text, mbox, link).
Notification sent
to Sébastien Villemot <[email protected]>:
Bug acknowledged by developer.
(Wed, 18 Jan 2017 13:24:05 GMT) (full text, mbox, link).
Reply sent
to Michael Biebl <[email protected]>:
You have taken responsibility.
(Wed, 18 Jan 2017 13:24:06 GMT) (full text, mbox, link).
Notification sent
to Boyuan Yang <[email protected]>:
Bug acknowledged by developer.
(Wed, 18 Jan 2017 13:24:06 GMT) (full text, mbox, link).
Reply sent
to Michael Biebl <[email protected]>:
You have taken responsibility.
(Wed, 18 Jan 2017 13:24:06 GMT) (full text, mbox, link).
Notification sent
to Niko Tyni <[email protected]>:
Bug acknowledged by developer.
(Wed, 18 Jan 2017 13:24:07 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.