Bug#755844: libudev.so.0.13.0: Re: libudev.so.0.13.0: applications crash in libudev (under memory pressure?)

2014-07-24 Thread Michal Suchanek
Excerpts from Marco d'Itri's message of Fri Jul 25 04:06:06 +0200 2014: > On Jul 24, Michal Suchanek wrote: > > > Apparently there are two versions of libudev linked in. > > > > Upgrading libudev-dev so it references libudev.so.1 resolves the > > problem. > > > > I am not sure if linking symbol

Bug#674755: Document actual tmpfs-systemd behaviour

2014-07-24 Thread Javier Barroso
Helllo, Replying to : " I read that like exactly the same expectation? see also man tmpfs " at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674755#68 I think should be fine to document how tmpfs work with systemd. So when you read tmpfs manpage in a system which is running systemd, you can

Bug#755844: libudev.so.0.13.0: Re: libudev.so.0.13.0: applications crash in libudev (under memory pressure?)

2014-07-24 Thread Michael Biebl
Am 25.07.2014 04:06, schrieb Marco d'Itri: > On Jul 24, Michal Suchanek wrote: > >> Apparently there are two versions of libudev linked in. >> >> Upgrading libudev-dev so it references libudev.so.1 resolves the >> problem. >> >> I am not sure if linking symbols from two different versions of libu

Bug#755844: libudev.so.0.13.0: Re: libudev.so.0.13.0: applications crash in libudev (under memory pressure?)

2014-07-24 Thread Marco d'Itri
On Jul 24, Michal Suchanek wrote: > Apparently there are two versions of libudev linked in. > > Upgrading libudev-dev so it references libudev.so.1 resolves the > problem. > > I am not sure if linking symbols from two different versions of libudev > should be prevented in some way. I am not sur

Processed: reassign 755844 to libudev1

2014-07-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 755844 libudev1 Bug #755844 [libudev0] libudev.so.0.13.0: applications crash in libudev (under memory pressure?) Bug reassigned from package 'libudev0' to 'libudev1'. No longer marked as found in versions udev/175-7.2. Ignoring request t

Bug#741252: marked as done (dh-systemd: please merge systemd2init to allow autogenerating shell init scripts)

2014-07-24 Thread Debian Bug Tracking System
Your message dated Fri, 25 Jul 2014 00:00:06 + with message-id and subject line Bug#741252: fixed in init-system-helpers 1.20 has caused the Debian Bug report #741252, regarding dh-systemd: please merge systemd2init to allow autogenerating shell init scripts to be marked as done. This means

init-system-helpers_1.20_amd64.changes ACCEPTED into unstable, unstable

2014-07-24 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 24 Jul 2014 23:49:57 +0200 Source: init-system-helpers Binary: init-system-helpers dh-systemd init Architecture: source all amd64 Version: 1.20 Distribution: unstable Urgency: medium Maintainer: pkg-systemd-maintai

init-system-helpers_1.20_amd64.changes is NEW

2014-07-24 Thread Debian FTP Masters
binary:init is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, an

Processing of init-system-helpers_1.20_amd64.changes

2014-07-24 Thread Debian FTP Masters
init-system-helpers_1.20_amd64.changes uploaded successfully to localhost along with the files: init-system-helpers_1.20_all.deb dh-systemd_1.20_all.deb init_1.20_amd64.deb init-system-helpers_1.20.dsc init-system-helpers_1.20.tar.xz Greetings, Your Debian queue daemon (running

Bug#755968: libpam-systemd: should depend on dbus

2014-07-24 Thread Ansgar Burchardt
Package: libpam-systemd Version: 208-6 Severity: normal libpam-systemd has a dependency on systemd-sysv (or systemd-shim) to ensure logind is available, but it has no dependency on dbus. However if dbus is not installed, it cannot talk to logind... systemd itself should probably also recommend db

Bug#755904: libpam-systemd: error in log after upgrade

2014-07-24 Thread Michael Biebl
Am 24.07.2014 22:59, schrieb Benoit Friry: After a reboot your problem will be gone. > > No more error in log after reboot. Bug report can be closed. > >>> Is there any other way to fix that without rebooting? >> >> Unfortunately not. The new logind requires systemd as PID 1, which >> means

Bug#755904: libpam-systemd: error in log after upgrade

2014-07-24 Thread Benoit Friry
>>> After a reboot your problem will be gone. No more error in log after reboot. Bug report can be closed. >> Is there any other way to fix that without rebooting? > > Unfortunately not. The new logind requires systemd as PID 1, which > means you need to reboot. Not a good news. :( I used the

Processed: Re: no core dumps and hard to diagnose

2014-07-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 739071 Bug #739071 [systemd] no core dumps and hard to diagnose Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 739071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739071 Deb

Bug#755904: marked as done (libpam-systemd: error in log after upgrade)

2014-07-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Jul 2014 16:01:00 +0200 with message-id <53d1119c.9000...@debian.org> and subject line Re: Bug#755904: libpam-systemd: error in log after upgrade has caused the Debian Bug report #755904, regarding libpam-systemd: error in log after upgrade to be marked as done. This mea

Bug#755904: libpam-systemd: error in log after upgrade

2014-07-24 Thread Benoit Friry
After upgrade, I get lots of error in auth.log: Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument >> >>> Is systemd-logind running? >> >> # ps -ef|grep -v grep|grep systemd root 5244 1 0 juin29 >> ? 00:00:47 /lib

Bug#755904: libpam-systemd: error in log after upgrade

2014-07-24 Thread Michael Biebl
Am 24.07.2014 15:20, schrieb Benoit Friry: > Bonjour, > >>> After upgrade, I get lots of error in auth.log: >>> Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to >>> create session: Invalid argument > >> Is systemd-logind running? > > # ps -ef|grep -v grep|grep systemd > r

Bug#755904: libpam-systemd: error in log after upgrade

2014-07-24 Thread Benoit Friry
Bonjour, >> After upgrade, I get lots of error in auth.log: >> Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to >> create session: Invalid argument > Is systemd-logind running? # ps -ef|grep -v grep|grep systemd root 5244 1 0 juin29 ? 00:00:47 /lib/systemd

libsystemd-dummy_208-2_kfreebsd-amd64.changes ACCEPTED into unstable

2014-07-24 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 24 Jul 2014 14:42:20 +0200 Source: libsystemd-dummy Binary: libsystemd-daemon-dev Architecture: source kfreebsd-amd64 Version: 208-2 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers C

Processing of libsystemd-dummy_208-2_kfreebsd-amd64.changes

2014-07-24 Thread Debian FTP Masters
libsystemd-dummy_208-2_kfreebsd-amd64.changes uploaded successfully to localhost along with the files: libsystemd-daemon-dev_208-2_kfreebsd-amd64.deb libsystemd-dummy_208-2.dsc libsystemd-dummy_208-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.or

Bug#755904: libpam-systemd: error in log after upgrade

2014-07-24 Thread Michael Biebl
Hi, Am 24.07.2014 14:10, schrieb Benoit Friry: > Package: libpam-systemd > Version: 208-6 > Severity: minor > > Dear Maintainer, > > After upgrade, I get lots of error in auth.log: > Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create > session: Invalid argument > Is

Bug#755904: libpam-systemd: error in log after upgrade

2014-07-24 Thread Benoit Friry
Package: libpam-systemd Version: 208-6 Severity: minor Dear Maintainer, After upgrade, I get lots of error in auth.log: Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument I think I encountered the same behaviour previously, and it was solved

libsystemd-dummy_208-1_kfreebsd-amd64.changes ACCEPTED into unstable, unstable

2014-07-24 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 02 Jun 2014 02:48:48 +0200 Source: libsystemd-dummy Binary: libsystemd-daemon-dev Architecture: source kfreebsd-amd64 Version: 208-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers C

Comments regarding libsystemd-dummy_208-1_kfreebsd-amd64.changes

2014-07-24 Thread Ansgar Burchardt
Hi, src/sd-shutdown.h is licensed under LGPL-2.1+. Please include that information in d/copyright. I think it would also be good if there was an explicit license for the Debian packaging. Ansgar ___ Pkg-systemd-maintainers mailing list Pkg-systemd-m

Bug#725815: marked as done ([systemd-sysv] CIFS-mounts in fstab with comment=x-systemd and automount delay shutdown)

2014-07-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Jul 2014 11:11:31 +0200 with message-id <2076303.vKpoE7FCeV@ilyena> and subject line Re: [systemd-sysv] CIFS-mounts in fstab with comment=x-systemd and automount delay shutdown has caused the Debian Bug report #725815, regarding [systemd-sysv] CIFS-mounts in fstab with c

Bug#755512: marked as done (systemd-sysv: Can not normal /sbin/shutdown (even as root))

2014-07-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Jul 2014 10:39:19 +0200 with message-id <1829180.BqcB3HCH6J@ilyena> and subject line Re: systemd 208-6 conflicts with ulatencyd has caused the Debian Bug report #755373, regarding systemd-sysv: Can not normal /sbin/shutdown (even as root) to be marked as done. This means