Debian Bug report logs - #787480
build with iptables support

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <id@joeyh.name>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: build with iptables support

Date: Mon, 1 Jun 2015 20:27:38 -0400

[Message part 1 (text/plain, inline)]

Package: systemd
Version: 220-3
Severity: normal
File: systemd-networkd

I'm trying to use systemd-networkd with systemd-nspawn --private-network --port
now that a systemd supporting this feature has convenently landed in unstable
early. ;)

Jun 01 20:14:03 clam systemd-networkd[4629]: ve-t3: Could not enable IP masquerading: Operation not supported

Seems that networkd needs to be linked to libiptc.so for that to work.

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.113+nmu3
ii  libacl1         2.2.52-2
ii  libapparmor1    2.9.2-3
ii  libaudit1       1:2.4-1+b1
ii  libblkid1       2.26.2-6
ii  libc6           2.19-18
ii  libcap2         1:2.24-8
ii  libcap2-bin     1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.3-2
ii  libkmod2        20-1
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libmount1       2.26.2-6
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2
ii  libsystemd0     220-3
ii  mount           2.26.2-6
ii  sysv-rc         2.88dsf-59.2
ii  udev            220-3
ii  util-linux      2.26.2-6

Versions of packages systemd recommends:
ii  dbus            1.8.18-1
ii  libpam-systemd  220-3

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- Configuration Files:
/etc/systemd/journald.conf changed [not included]
/etc/systemd/logind.conf changed [not included]

-- no debconf information

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Joey Hess <id@joeyh.name>, 787480@bugs.debian.org

Subject: Re: Bug#787480: build with iptables support

Date: Tue, 02 Jun 2015 02:39:23 +0200

[Message part 1 (text/plain, inline)]

Hi Joey

Am 02.06.2015 um 02:27 schrieb Joey Hess:
> Package: systemd
> Version: 220-3
> Severity: normal
> File: systemd-networkd
> 
> I'm trying to use systemd-networkd with systemd-nspawn --private-network --port
> now that a systemd supporting this feature has convenently landed in unstable
> early. ;)
> 
> Jun 01 20:14:03 clam systemd-networkd[4629]: ve-t3: Could not enable IP masquerading: Operation not supported
> 
> Seems that networkd needs to be linked to libiptc.so for that to work.

We were reluctant to link against libiptc, since that would mean a
dependency on iptables, which is about 4M of additional disk space which
even minimal systems would have to install.

Given the recent upstream discussions [1] to switch to nftables, we will
probably wait a bit, until things have settled, before turning this
feature on. Hope that makes sense.

Cheers,
Michael

[1]
http://lists.freedesktop.org/archives/systemd-devel/2015-June/032661.html

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #15 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Joey Hess <id@joeyh.name>, 787480@bugs.debian.org

Subject: Re: Bug#787480: build with iptables support

Date: Tue, 02 Jun 2015 02:41:36 +0200

[Message part 1 (text/plain, inline)]

Am 02.06.2015 um 02:39 schrieb Michael Biebl:
> Given the recent upstream discussions [1] to switch to nftables, we will
...
> [1]
> http://lists.freedesktop.org/archives/systemd-devel/2015-June/032661.html

That was the wrong link. Here's the correct one:
http://lists.freedesktop.org/archives/systemd-devel/2015-May/032531.html


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #20 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <id@joeyh.name>

To: Michael Biebl <biebl@debian.org>

Cc: 787480@bugs.debian.org

Subject: Re: Bug#787480: build with iptables support

Date: Tue, 2 Jun 2015 00:06:49 -0400

[Message part 1 (text/plain, inline)]

Michael Biebl wrote:
> We were reluctant to link against libiptc, since that would mean a
> dependency on iptables, which is about 4M of additional disk space which
> even minimal systems would have to install.
> 
> Given the recent upstream discussions [1] to switch to nftables, we will
> probably wait a bit, until things have settled, before turning this
> feature on. Hope that makes sense.

Isn't libnftnl0 bigger than iptables anyway?

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #25 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Joey Hess <id@joeyh.name>, 787480@bugs.debian.org

Subject: Re: Bug#787480: build with iptables support

Date: Tue, 2 Jun 2015 06:13:33 +0200

[Message part 1 (text/plain, inline)]

Joey Hess [2015-06-02  0:06 -0400]:
> Michael Biebl wrote:
> > We were reluctant to link against libiptc, since that would mean a
> > dependency on iptables, which is about 4M of additional disk space which
> > even minimal systems would have to install.
> > 
> > Given the recent upstream discussions [1] to switch to nftables, we will
> > probably wait a bit, until things have settled, before turning this
> > feature on. Hope that makes sense.
> 
> Isn't libnftnl0 bigger than iptables anyway?

In a minimal sid schroot:

  # apt-get install libnftnl0
  [...]
  The following NEW packages will be installed:
    libjansson4 libmnl0 libmxml1 libnftnl0
  Need to get 125 kB of archives.
  After this operation, 472 kB of additional disk space will be used.

  # apt-get install iptables
  [...]
  The following NEW packages will be installed:
    iptables libnfnetlink0 libxtables10
  Need to get 358 kB of archives.
  After this operation, 3818 kB of additional disk space will be used.

So getting libiptc it's a whole magnitude bigger.

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

[signature.asc (application/pgp-signature, inline)]

Message #34 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Dimitri John Ledkov <xnox@debian.org>

To: 787480@bugs.debian.org, Martin Pitt <martin.pitt@ubuntu.com>

Subject: Re: Bug#787480: build with iptables support

Date: Thu, 23 Jul 2015 12:21:47 +0100

On Tue, 2 Jun 2015 06:13:33 +0200 Martin Pitt <mpitt@debian.org> wrote:
> Joey Hess [2015-06-02  0:06 -0400]:
> > Michael Biebl wrote:
> > > We were reluctant to link against libiptc, since that would mean a
> > > dependency on iptables, which is about 4M of additional disk space which
> > > even minimal systems would have to install.
> > >
> > > Given the recent upstream discussions [1] to switch to nftables, we will
> > > probably wait a bit, until things have settled, before turning this
> > > feature on. Hope that makes sense.
> >
> > Isn't libnftnl0 bigger than iptables anyway?

So libiptc gets linked into nspawn & networkd only. I do agree that it
is optional feature.

debian default policy is to provide and enable most options.

Is networkd/nspawn part of the core package? Maybe we can simply split
them out into a separate package?
I don't think on minimal systems networkd is needed.

If we in-vision that networkd is / will-be required on minimal
systems, I would want to have an alternative build available of
networkd & nspawn with firewall support enabled. (could be something
like update-alternatives, or e.g. systemd-networkd-firewall.service
that conflicts with normal networkd units or whatever.)

The current plan upstream it seems to bring fire-walling into the
core, such that e.g. units will be able to declare which ports and
things they can access. If that will be the case, we'd be pressed to
include firewalling in the core anyway.

Pitti, can we get libiptc enabled as Ubuntu vendor option? I'm
experimenting with using networkd alone for all the things.

Regards,

Dimitri.

Message #39 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Dimitri John Ledkov <xnox@debian.org>, 787480@bugs.debian.org, Martin Pitt <martin.pitt@ubuntu.com>

Subject: Re: Bug#787480: build with iptables support

Date: Thu, 23 Jul 2015 13:32:02 +0200

[Message part 1 (text/plain, inline)]

Am 23.07.2015 um 13:21 schrieb Dimitri John Ledkov:
> If we in-vision that networkd is / will-be required on minimal
> systems, I would want to have an alternative build available of
> networkd & nspawn with firewall support enabled. (could be something
> like update-alternatives, or e.g. systemd-networkd-firewall.service
> that conflicts with normal networkd units or whatever.)

I think it would be highly confusing to have two builds of
systemd-networkd with different feature sets and bringing
update-alternatives into the mix wouldn't help. So I'm not sure we want
this.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #44 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Dimitri John Ledkov <xnox@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: 787480@bugs.debian.org, Martin Pitt <martin.pitt@ubuntu.com>

Subject: Re: Bug#787480: build with iptables support

Date: Thu, 23 Jul 2015 15:47:02 +0100

On 23 July 2015 at 12:32, Michael Biebl <biebl@debian.org> wrote:
> Am 23.07.2015 um 13:21 schrieb Dimitri John Ledkov:
>> If we in-vision that networkd is / will-be required on minimal
>> systems, I would want to have an alternative build available of
>> networkd & nspawn with firewall support enabled. (could be something
>> like update-alternatives, or e.g. systemd-networkd-firewall.service
>> that conflicts with normal networkd units or whatever.)
>
> I think it would be highly confusing to have two builds of
> systemd-networkd with different feature sets and bringing
> update-alternatives into the mix wouldn't help. So I'm not sure we want
> this.
>

So split networkd into stand-alone package, and enable iptables-dev
dependency. It's not enabled by default service, is it? Thus should
not be installed together with init, given the deps it wants / pulls
in. And from the bug reports there is clearly demand for full
functionality to be available from networkd. Looks like win-win,
minimal install is kept minimal, yet optional component is fully
featured.

-- 
Regards,

Dimitri.

Message #51 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Jamie McClelland <jm@mayfirst.org>

To: 787480@bugs.debian.org

Subject: please add iptables support to networkd

Date: Tue, 12 Jan 2016 09:25:25 -0500

[Message part 1 (text/plain, inline)]

Is there any update on this issue, like an estimate of when we might
expect nftables support to be available in systemd-networkd or nspawn in
Debian?

I just spent a few hours moving my network configuration to networkd
before I realized that it's just not possible without masquerading.

jamie

-- 
May First/People Link
Growing networks to build a just world
http://www.mayfirst.org
https://support.mayfirst.org

OpenPGP Key: http://current.workingdirectory.net/pages/identity/ 
xmpp: jamie@im.mayfirst.org

[signature.asc (application/pgp-signature, inline)]

Message #56 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Mario Lang <mlang@debian.org>

To: 787480@bugs.debian.org

Subject: Ping?

Date: Thu, 09 Jun 2016 01:44:37 +0200

[Message part 1 (text/plain, inline)]

Hi.

I just discovered IPMasquerade= in systemd.network(5) which is exactly
what I need to set up a Bluetooth PAN Access Point.  The config
*would* be straight forward via systemd-networkd (bt-pan related setup
not included):

/etc/systemd/network/pan.netdev:
[NetDev]
Name=pan
Kind=bridge
ForwardDelaySec=0

/etc/systemd/network/pan.network:
[Match]
Name=pan

[Network]
Address=10.2.1.1/24
DHCPServer=yes
IPMasquerade=yes


However, during testing I realized that while IPMasquerade= is
documented in systemd.network(5), it is a noop on Debian.

It would be nice if we could get this bug fixed before the release.
Preferably by enabling iptable support in systemd.

If this is not possible (which would be quite sad, given how convenient
this feature actually is), I suggest we at least remove IPMasquerade=
From the manpage (or augment it with a note that this feature is not
available) to avoid confusing users (like me).

-- 
CYa,
  ⡍⠁⠗⠊⠕

[signature.asc (application/pgp-signature, inline)]

Message #61 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Mario Lang <mlang@debian.org>, 787480@bugs.debian.org

Subject: Re: Bug#787480: Ping?

Date: Thu, 9 Jun 2016 01:56:56 +0200

[Message part 1 (text/plain, inline)]

Am 09.06.2016 um 01:44 schrieb Mario Lang:
> It would be nice if we could get this bug fixed before the release.
> Preferably by enabling iptable support in systemd.

I guess this would need someone asking the iptables maintainer to split
out /lib/libip(4|6)tc.so into a separate library package, so we don't
need to pull in all of iptables into every installed system (as
mentioned before this increases the footprint by 4M).

Someone willing to ask the iptables maintainers if this would be feasible?

Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #66 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Mario Lang <mlang@debian.org>, 787480@bugs.debian.org

Subject: Re: Bug#787480: Ping?

Date: Thu, 9 Jun 2016 02:29:04 +0200

[Message part 1 (text/plain, inline)]

Am 09.06.2016 um 01:56 schrieb Michael Biebl:
> Am 09.06.2016 um 01:44 schrieb Mario Lang:
>> It would be nice if we could get this bug fixed before the release.
>> Preferably by enabling iptable support in systemd.
> 
> I guess this would need someone asking the iptables maintainer to split
> out /lib/libip(4|6)tc.so into a separate library package, so we don't
> need to pull in all of iptables into every installed system (as
> mentioned before this increases the footprint by 4M).
> 
> Someone willing to ask the iptables maintainers if this would be feasible?

I've just checked out the iptables sources and apparently this is in the
works:
https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=pkg-netfilter/pkg-netfilter.git;a=commitdiff;h=001e02b30dbe8fc2dba820abae4f710de2114133

Hasn't been uploaded yet, though.

The maintainer has decided to move the libraries back to /usr/lib.
This means our current check in debian/rules which tests if binaries
have been linked against libs from /usr will fail.

We could either ask the iptables maintainer to keep the libs in /lib or
exclude systemd-networkd from the check in debian/rules.

At some point, shuffling the libraries around becomes a nuisance. Maybe
we should only do that for /lib/systemd/systemd and eventually
/lib/systemd/systemd-udevd.

Thoughts?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #71 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Martin Pitt <mpitt@debian.org>, 787480@bugs.debian.org

Subject: Re: Bug#787480: Ping?

Date: Thu, 9 Jun 2016 10:58:29 +0200

[Message part 1 (text/plain, inline)]

Am 09.06.2016 um 07:57 schrieb Martin Pitt:
> Michael Biebl [2016-06-09  2:29 +0200]:
>> At some point, shuffling the libraries around becomes a nuisance. Maybe
>> we should only do that for /lib/systemd/systemd and eventually
>> /lib/systemd/systemd-udevd.
> 
> We got two RC bugs before we had this check, but I don't remember
> whether this was before the initramfs-tools change that mounts /usr.
> But even with that I'm sure that we have a very small number of users
> who believe that separate /usr without initramfs was ever supported,
> and I'm sort of tired about arguing against that..
> 
> Anyway, we can certainly trim that check a bit, but only these two
> aren't sufficient -- we at least need to cover the generators, fsck,
> networkd, reply-passwd, etc. -- seems easier and safer to whitelist
> programs like timesyncd or timedated which are safe.
> 
> Not sure where this linking would end up, I suppose in networkd? 

/lib/systemd/systemd-networkd and /usr/bin/systemd-nspawn if I checked
correctly.

That
> would then break with /usr being on the network and not using an
> initrd. As I said, I have very little sympathy for that, but see
> above..

Oh, the mythical /usr-on-NFS case. I don't see how that would work with
networkd anyway, it having a After=dbus.service…


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #76 received at 787480@bugs.debian.org (full text, mbox, reply):

From: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>

To: 787480@bugs.debian.org

Subject: about iptables vs nftables

Date: Thu, 9 Jun 2016 11:22:06 +0200

Hi,

I'm currently maintaining iptables and nftables in Debian, and I'm upstream
developer as well.

About the iptables vs nftables issue, the clear winner is nftables.

About the iptables package split for libiptc, yes that's a WIP.
Thanks Michael Biebl who is giving me a helping hand with that.

best regards.

-- 
Arturo Borrero González

Message #83 received at 787480-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: 787480-close@bugs.debian.org

Subject: Bug#787480: fixed in systemd 231-5

Date: Fri, 26 Aug 2016 10:55:13 +0000

Source: systemd
Source-Version: 231-5

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 787480@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@debian.org> (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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 26 Aug 2016 10:58:07 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source amd64
Version: 231-5
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
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
 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: 744301 787480 830257 834148
Changes:
 systemd (231-5) unstable; urgency=medium
 .
   [ Iain Lane ]
   * Let graphical-session-pre.target be manually started (LP: #1615341)
 .
   [ Felipe Sateler ]
   * Add basic version of git-cherry-pick
   * Replace Revert-units-add-a-basic-SystemCallFilter-3471.patch with upstream
     patch
   * sysv-generator: better error reporting. (Closes: #830257)
 .
   [ Martin Pitt ]
   * 73-usb-net-by-mac.rules: Test for disabling 80-net-setup-link.rules more
     efficiently. Stop calling readlink at all and just test if
     /etc/udev/rules.d/80-net-setup-link.rules exists -- a common way to
     disable an udev rule is to just "touch" it in /etc/udev/rule.d/ (i. e.
     empty file), and if the rule is customized we cannot really predict anyway
     if the user wants MAC-based USB net names or not. (LP: #1615021)
   * Ship kernel-install (Closes: #744301)
   * Add debian/extra/kernel-install.d/60-initrd.install.
     This kernel-install drop-in copies the initrd of the selected kernel to
     the EFI partition.
   * bootctl: Automatically detect ESP partition.
     This makes bootctl work with Debian's /boot/efi/ mountpoint without having
     to explicitly specify --path.
     Patches cherry-picked from upstream master.
   * systemd.NEWS: Point out that alternatively rcS scripts can be moved to
     rc[2-5]. Thanks to Petter Reinholdtsen for the suggestion!
 .
   [ Michael Biebl ]
   * Enable iptables support (Closes: #787480)
   * Revert "logind: really handle *KeyIgnoreInhibited options in logind.conf"
     The special 'key handling' inhibitors should always work regardless of
     any *IgnoreInhibited settings – otherwise they're nearly useless.
     Update man pages to clarify that *KeyIgnoreInhibited only apply to a
     subset of locks (Closes: #834148)
Checksums-Sha1:
 9b3d64fd8ecb2907af733db7b80a7b1d3ef532b4 4436 systemd_231-5.dsc
 c91d51f2bbfc4eea6bfd5a1706d4a9b6bdb9877b 129864 systemd_231-5.debian.tar.xz
 da1e15a67e5b262449f37732f19163c840523c74 87528 libnss-myhostname-dbgsym_231-5_amd64.deb
 863eae25851f80648dd6634c0e7a6f34cdfdbe04 94168 libnss-myhostname_231-5_amd64.deb
 af1808cdb49663a25a6c9571ecd578fd6c911241 432054 libnss-mymachines-dbgsym_231-5_amd64.deb
 3777658036cb9e62d0dbc79d02a313322046b071 175640 libnss-mymachines_231-5_amd64.deb
 33e8c13f09c6914f20105d6749e1c686e05632de 428054 libnss-resolve-dbgsym_231-5_amd64.deb
 bdcac4d1c89213b7c03a67a0044af0f4f01cee6e 175024 libnss-resolve_231-5_amd64.deb
 f1432c0b4859df74464bbf4354da0735273f4c6c 421866 libpam-systemd-dbgsym_231-5_amd64.deb
 288f240c43905c86104fb7849f84e8356f3aaab1 177020 libpam-systemd_231-5_amd64.deb
 eb651735699b583117408ca8bba7e7ccb9edaf7f 224202 libsystemd-dev_231-5_amd64.deb
 17d13d138463067ed90a98a31921d7a0893a0c89 660490 libsystemd0-dbgsym_231-5_amd64.deb
 7e9457db8d1049a3036f345714249ed53a333ac7 267688 libsystemd0_231-5_amd64.deb
 f9f608671fb186dfe57a0f99a06b44eefceeae39 513108 libudev-dev-dbgsym_231-5_amd64.deb
 996f6a33ffb69e4077d29122231122bf8f613169 249034 libudev-dev_231-5_amd64.deb
 29078fd7986a25f8a936c17d24af370105ff81b8 157930 libudev1-dbgsym_231-5_amd64.deb
 58f08616c301a03929ea33793daa445a2ae25249 48486 libudev1-udeb_231-5_amd64.udeb
 42da2d93d5e2686d22f2f357a336b934e0189ef1 113784 libudev1_231-5_amd64.deb
 5d0375e82db514a99c3a3504eeaf9bca624f7910 471698 systemd-container-dbgsym_231-5_amd64.deb
 0981e28e04895a84a0e3077756a9553784f0b963 274582 systemd-container_231-5_amd64.deb
 1a71f18631da4ab13c48d45a3c77b4ded9c4eb51 66732 systemd-coredump-dbgsym_231-5_amd64.deb
 2c4afa85fd4f513520df2c962426faae9f743132 97652 systemd-coredump_231-5_amd64.deb
 6f159d1812c63d4f4e1de40a30604429ab1bc5bd 5755220 systemd-dbgsym_231-5_amd64.deb
 b0711e01c5b62f27ea244093c97ec36d5d6371c3 110236 systemd-journal-remote-dbgsym_231-5_amd64.deb
 ea423dce32a5bac958ba05ca118df7d0d863e3d7 116818 systemd-journal-remote_231-5_amd64.deb
 ba4324e6217e4c027cbf0af79ee7dafdaab42536 70408 systemd-sysv_231-5_amd64.deb
 07ce09d11f5fa99e03714c6d902ba84ca482b9a6 2364560 systemd_231-5_amd64.deb
 4c2d7d1a285a807605bf943c8cd9110edd757461 1316188 udev-dbgsym_231-5_amd64.deb
 3ea2d8ebe6c6bcbd35a5d0f6a10e8c8ce3548194 271646 udev-udeb_231-5_amd64.udeb
 9ae9d0c0a80c58e88154da1685a2ec12b055e8bb 1077622 udev_231-5_amd64.deb
Checksums-Sha256:
 a5acf6b2f8e8fc70a71ea8ac94c084084da634beab313199e5f8545dc3d44557 4436 systemd_231-5.dsc
 1978c5709dad9f6412318be953ae9e0734e31ea5501b2b015a40222a76ba2569 129864 systemd_231-5.debian.tar.xz
 f4750c6d20a56dc8073233a9ea161957b6f9488e428821e88b4304cd83c34f23 87528 libnss-myhostname-dbgsym_231-5_amd64.deb
 5433a2c4a380bece1b4ffe6d34603625c50b5f539009e8eae104102e33d19dc1 94168 libnss-myhostname_231-5_amd64.deb
 9c1f0038182485c20f735db331c1cbf0e346b1ce7010a761a83c3203caaa4526 432054 libnss-mymachines-dbgsym_231-5_amd64.deb
 f756e84200d0602fb9902bb3edfae87249e40b67396b9ed5fb1b672d2792ca43 175640 libnss-mymachines_231-5_amd64.deb
 5a7b78d35cb4b37d1ad64bae6b82678284e075cef87d16f2877e9f7687cc35de 428054 libnss-resolve-dbgsym_231-5_amd64.deb
 4448df79c70f945b2ddf4e6079796e18e8c02831d9448dc02014ee7daf792808 175024 libnss-resolve_231-5_amd64.deb
 57126844e4666639727ffcc9e8a31f5b7840bb2634179ffe47cf3d541286f35e 421866 libpam-systemd-dbgsym_231-5_amd64.deb
 0883a113d052820dc9711adfdcdce8b8d58f19ea9c693d19044ef34c44d17dd7 177020 libpam-systemd_231-5_amd64.deb
 16901b2d9c80c5b89517f35037bccba2a77232b313d3f31bab1c4f47a0a0e787 224202 libsystemd-dev_231-5_amd64.deb
 0304c34ab84c226c2079e8f535934680ede5a17534b752f1d292d48b02a4ef6a 660490 libsystemd0-dbgsym_231-5_amd64.deb
 c5b636ad523cea0da51734497e0abb542cf710db7794f09abd71fa5b574e41a3 267688 libsystemd0_231-5_amd64.deb
 90e5a83be7933e51c4ce952b38bfed2468bfef25617d8b5e9fe1c0041a8662ac 513108 libudev-dev-dbgsym_231-5_amd64.deb
 f241275bb346a0f2a5c87196585e67a59e6a694aeccf353dd015122b1048ea32 249034 libudev-dev_231-5_amd64.deb
 85fca3d2adf27297ae974cbb50f90c169f09d6f169c03a789c335ed53b12155c 157930 libudev1-dbgsym_231-5_amd64.deb
 cbb885de2a3b225831007cb594d77ec53de662dc417f914c07f556a81ce0bf7f 48486 libudev1-udeb_231-5_amd64.udeb
 7b689418a761816e2ec1edc0e3160c89b16db67b84605689650d78e36a1c185a 113784 libudev1_231-5_amd64.deb
 14573431b89aa740a52d55549f5f3178e4345d239909c550525f327aad9198eb 471698 systemd-container-dbgsym_231-5_amd64.deb
 9ce6102dd86dcac8f6a5a3229ded2540bf8ce49fb89e17e49851cb63f25e5495 274582 systemd-container_231-5_amd64.deb
 759180cb417e98dc142dac0a4c1c54c5f12f2d04a3ef39bf25ca625b7e3a5527 66732 systemd-coredump-dbgsym_231-5_amd64.deb
 1afe84e150d255cc01a966f7402bd00f499a5fc71baea0f2a244edd22dac7958 97652 systemd-coredump_231-5_amd64.deb
 1046d36a0eda5b5329e57bfdd6c89ea8b17e456d390627bad0ce36c3cf8b08bb 5755220 systemd-dbgsym_231-5_amd64.deb
 22eeca8e777e7c1e50bae7d39a3c9b8d6e459169988984b3afda8dd8042fda5b 110236 systemd-journal-remote-dbgsym_231-5_amd64.deb
 1962b0e376481478ce22975f70a1fc89624d02f9b096e35394429a835382a5f1 116818 systemd-journal-remote_231-5_amd64.deb
 3a4a0f3ba4c5191d7ee1cd9d846bbf7500a5e5f79002a65af07f0e7874fffbb9 70408 systemd-sysv_231-5_amd64.deb
 10209c5b5de9309d4d9cf9dd2a238658e1ed5fa26c31d3fdf20236017f67ba4c 2364560 systemd_231-5_amd64.deb
 912c1c71ea72dab7536f0d134568fd6a9ea298c920e70d3587bcde0b5dc93b02 1316188 udev-dbgsym_231-5_amd64.deb
 615d2d42ab9bb07951d2e01f1d723b5e773221d3cd512d144c49dae166809751 271646 udev-udeb_231-5_amd64.udeb
 c9230dfc8bfc4515cd5d46f7bdc41faac5c41ed18a472018bc6f532d3fee947e 1077622 udev_231-5_amd64.deb
Files:
 00da560372b1018929686d8e0b202374 4436 admin optional systemd_231-5.dsc
 9809fe33921deae2967c571272ab6261 129864 admin optional systemd_231-5.debian.tar.xz
 496446c1e755897fd8a44278ecae25f0 87528 debug extra libnss-myhostname-dbgsym_231-5_amd64.deb
 edae379085ab6eb9d0268aebafeac48e 94168 admin extra libnss-myhostname_231-5_amd64.deb
 7c34fd389501a4dd66103409fc348b56 432054 debug extra libnss-mymachines-dbgsym_231-5_amd64.deb
 5da75f9bc69480bdc9c2ef0bbd1a665c 175640 admin extra libnss-mymachines_231-5_amd64.deb
 c4febc5aed281279653878f14bfdce91 428054 debug extra libnss-resolve-dbgsym_231-5_amd64.deb
 ab34ae5928e8db7a9a05d8c0477e1f37 175024 admin extra libnss-resolve_231-5_amd64.deb
 610b8bf4d08a414dc20c5d94db9b227a 421866 debug extra libpam-systemd-dbgsym_231-5_amd64.deb
 5f3f6826047ffd5b408e68329a909f6f 177020 admin optional libpam-systemd_231-5_amd64.deb
 3fb9c52907f4052017ee3be23623d082 224202 libdevel optional libsystemd-dev_231-5_amd64.deb
 ff5696a7ade2b7b8455a1687d62e8ea6 660490 debug extra libsystemd0-dbgsym_231-5_amd64.deb
 616e35b78cca423539ad25be6c1e51dd 267688 libs optional libsystemd0_231-5_amd64.deb
 3b219416adedd503980ba55c6b25ae22 513108 debug extra libudev-dev-dbgsym_231-5_amd64.deb
 1c075812bf73b88a08e78e106f525805 249034 libdevel optional libudev-dev_231-5_amd64.deb
 29d2bebd67fcaa5a59946fd53c1280be 157930 debug extra libudev1-dbgsym_231-5_amd64.deb
 2734eb9b60d70f3597fcd99403d2095d 48486 debian-installer optional libudev1-udeb_231-5_amd64.udeb
 29a6ea2796816be864fe36debe3184fa 113784 libs important libudev1_231-5_amd64.deb
 f343d6539dd8447c1347525fe8a188d5 471698 debug extra systemd-container-dbgsym_231-5_amd64.deb
 ec2ff3a09942f8031c750dcbe33cbcd5 274582 admin optional systemd-container_231-5_amd64.deb
 cec931d47687bf0fb26a83f2f903e754 66732 debug extra systemd-coredump-dbgsym_231-5_amd64.deb
 abf7ac816ec3980eb6766cd5c31541a0 97652 admin optional systemd-coredump_231-5_amd64.deb
 09b0fdf76abc85a59daa48467fda5bf2 5755220 debug extra systemd-dbgsym_231-5_amd64.deb
 cd640fa57365afc3d2bf948f0d1ef17f 110236 debug extra systemd-journal-remote-dbgsym_231-5_amd64.deb
 56c2f54e7fa7794f7965653abb9087bc 116818 admin optional systemd-journal-remote_231-5_amd64.deb
 6eeb6bcdc7e25279deb5e4d0684f198a 70408 admin important systemd-sysv_231-5_amd64.deb
 5c124a820ef92432cbe2c25fa759f2ab 2364560 admin important systemd_231-5_amd64.deb
 bfab971b699552bbc863ecfcd6ec400e 1316188 debug extra udev-dbgsym_231-5_amd64.deb
 af705333e310acfd0753978c58fbeec7 271646 debian-installer optional udev-udeb_231-5_amd64.udeb
 9e7c37244c040c25eb844bffae23e6e3 1077622 admin important udev_231-5_amd64.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXwBqGAAoJENFO8V2v4RNH+vQP/31TMVscsPZfCnFryCkDXwOc
xKZ18bO0kGTBdKOnDMiCEe3R2aFqQJX8DpAf9LY6NUaRZrNDWGQH/6vQqcLusyp5
mRPWzg7C+lCTPmRsmsdLh76lWr+BYG8eVt3tOeLzIB9LjC+MEoUoZFUKVVlaUFIZ
WAFBxBaFJPj0AmuPM92WbQ9CIiZjIh20B1UG8nOzir6xgXLV7ZV/ihMyYqbrzLR2
Ez784LzaMyn+g7GwS05Z3L8sAXW3Rco5I1HJQeZ2wgTy6bCiN9QxUGz9/2BO6hyG
adR8bakJACGr6GmiqCgU9SFybf1IHYhYfZAmmsSMrLlkX/FOhrYb1j+1vkq16Nix
2wquXaeLUrYm2+kDAG1y0vmwW849byDZiZt+/Sa85hR2n6t/wA+Dho53infEDT7N
gemleD4KHJaTlaFdrnwFG/X4m3Efp4/mpkSxsfADqvuODHXvw/YZpNkHs0x3alGS
NPMTmgIPitIXE4BOyl4gC6aAFdQ4Lxzlt3+wtULOLP2AkMpAeFzcxDSigmS6xKXB
F8x2u3x1fDBGjxh0vmpd97e7c4S05XWLr03WvV36jFIHyv+pVeoxqLoVOhmq/vFJ
XunNSdsxSBF5l1Z/6dsGbS5usf7j0tb6guafT65k0hq/DecbVKEv9ZnApiVtda+B
CaLI1UhVf2FN2RX5cmsR
=xIwW
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.