Bug#843809: check that executables don't link to libraries in /usr is broken wrt libsystemd-shared

Martin Pitt [2016-11-09 22:55 +0100]: > +1 on dropping the check again. Done so in git, FTR. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: PGP signature

Bug#806922: Problems with item delivery, n.148413537384

Hello, We could not deliver your parcel. Shipment Label is attached to this email. Nabil Smedick - Area Manager FedEx , CA Yours trully FedEx.doc Description: MS-Word document ___ Pkg-systemd-maintainers mailing list

Bug#843809: check that executables don't link to libraries in /usr is broken wrt libsystemd-shared

Hello Michael, Michael Biebl [2016-11-09 22:23 +0100]: > >> Dunno, maybe we should just drop the check again. Thoughts? +1 on dropping the check again. It has always been an approximation anyway, and the last time this got broken through a libaudit library update [1], not a systemd upload, so

Processed: retitle 843809 to check that executables don't link to libraries in /usr does not consider libsystemd-shared and is broken with merged-usr

Processing commands for cont...@bugs.debian.org: > retitle 843809 check that executables don't link to libraries in /usr does > not consider libsystemd-shared and is broken with merged-usr Bug #843809 [src:systemd] check that executables don't link to libraries in /usr is broken wrt

Bug#843809: check that executables don't link to libraries in /usr is broken wrt libsystemd-shared

Am 09.11.2016 um 22:11 schrieb Ansgar Burchardt: > Michael Biebl writes: >> But now we have a different issue, ldd thinks, that liblz4 is in /lib.: > [...] >> This is because of merged-usr. This more or less renders the whole check >> useless once we build in a chroot which has been created with

Bug#843809: check that executables don't link to libraries in /usr is broken wrt libsystemd-shared

Michael Biebl writes: > But now we have a different issue, ldd thinks, that liblz4 is in /lib.: [...] > This is because of merged-usr. This more or less renders the whole check > useless once we build in a chroot which has been created with > debootstrap --merged-usr > > Dunno, maybe we should

Bug#843809: check that executables don't link to libraries in /usr is broken wrt libsystemd-shared

Am 09.11.2016 um 21:18 schrieb Michael Biebl: > In a chroot, systemd and libsytemd-shared are not installed. > We probably need to override LD_LIBRARY_PATH and point it to > debian/systemd/lib/systemd/ This patch works to find libsystemd-shared: > --- a/debian/rules > +++ b/debian/rules > @@

Bug#843809: check that executables don't link to libraries in /usr is broken wrt libsystemd-shared

Source: systemd Version: 232-3 Am 09.11.2016 um 19:15 schrieb Michael Biebl: > The /lib/systemd/systemd binary itself links against libsystemd-shared > (interestingly, our debian/rules check seems to not have caught this). Fwiw, I figured out what's going wrong here: + env -u LD_PRELOAD ldd

Bug#832010: Please enable LZ4 compression

Am 21.07.2016 um 19:28 schrieb Yuri D'Elia: > On Thu, Jul 21 2016, Michael Biebl wrote: >> And in Debian we build against libxz, so xz compression is used for core >> files. > > Indeed, and it's pretty slow. > >> What would we gain by switching from xz to lz4. Can you provide

Good day My Dear. Greetings in the name of our Lord Jesus Christ . Amen. In brief introduction, my name is Mrs. Modese Dossongui, I am 59 years old, my late husband who was a nuclear power plant engin

___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: tagging 832010

Processing commands for cont...@bugs.debian.org: > tags 832010 - moreinfo Bug #832010 [systemd-coredump] Please enable LZ4 compression Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 832010:

Bug#843761: invoke-rc.d: Kill 600 birds with one stone (a.k.a. automatic policy-rc.d for init-less chroots)

Package: init-system-helpers Version: 1.46 Severity: normal Tags: patch X-Debbugs-CC: Chris Lamb , Niels Thykier Dear Maintainer, As discussed on IRC we seem to agree that an init-less chroot which does not have a policy-rc.d blocking service actions isn't a

Bug#843544: marked as done (systemd-container: Wrong exit code from /usr/bin/systemd-nspawn makes rkt fail)

Your message dated Wed, 09 Nov 2016 09:33:57 + with message-id and subject line Bug#843544: fixed in systemd 232-3 has caused the Debian Bug report #843544, regarding systemd-container: Wrong exit code from /usr/bin/systemd-nspawn makes rkt fail to be

Bug#843433: marked as done (Wrong paths for /bin/mount when compiled on merged-usr system)

Your message dated Wed, 09 Nov 2016 09:33:57 + with message-id and subject line Bug#843433: fixed in systemd 232-3 has caused the Debian Bug report #843433, regarding Wrong paths for /bin/mount when compiled on merged-usr system to be marked as done. This

Bug#843070: marked as done (systemd: systemd-delta is confused after usrmerge)

Your message dated Wed, 09 Nov 2016 09:33:56 + with message-id and subject line Bug#843070: fixed in systemd 232-3 has caused the Debian Bug report #843070, regarding systemd: systemd-delta is confused after usrmerge to be marked as done. This means that

systemd_232-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 09 Nov 2016 09:34:45 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libsystemd0

Processing of systemd_232-3_source.changes

systemd_232-3_source.changes uploaded successfully to localhost along with the files: systemd_232-3.dsc systemd_232-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-systemd-maintainers mailing

Bug#843433: Wrong paths for /bin/mount when compiled on merged-usr system

Control: tag -1 pending Hello Felipe, Felipe Sateler [2016-11-06 15:49 -0300]: > The following patch appears to fix the issue: This looks fine to me, thanks for this! I'll apply it to git and upload 232-3 ASAP, as both this and the unified cgroup thing break things pretty badly. Martin --

Processed: severity of 843537 is normal ...

Processing commands for cont...@bugs.debian.org: > severity 843537 normal Bug #843537 [systemd] Fails to start dovecot/resolved with NAMESPACE spawning error Severity set to 'normal' from 'serious' > retitle 843537 units that use seccomp filtering do not work with old kernels Bug #843537