Processing commands for cont...@bugs.debian.org:
> forwarded 804832 https://github.com/systemd/systemd/issues/1967
Bug #804832 [systemd] systemd-networkd fails to configure IPv4 Bridge Network
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/1967'.
> thanks
Stopping proc
On Fri, Nov 20, 2015 at 12:10:20AM +0100, Michael Biebl wrote:
> Hi Zbigniew,
>
> just saw [1].
Yeah, I submitted https://fedoraproject.org/wiki/Changes/systemd_package_split
for greater visibility
(and also https://fedoraproject.org/wiki/Changes/systemd_file_triggers)
> I don't think we are goin
Hi Zbigniew,
just saw [1].
I don't think we are going to rename the udev package in Debian, but
once the package split is done in Fedora, I'll add a
Provides: systemd-udev
to th Debian udev package to improve the cross-distro experience.
Regards,
Michael
[1]
https://lists.fedoraproject.org/pipe
On Thu, 19 Nov 2015 19:18:05 +0100 Singer Michael wrote:
> Am Donnerstag, 19. November 2015, 18:42:58 schrieb Michael Biebl:
> > Am 19.11.2015 um 18:22 schrieb Singer Michael:
> > > What else can I do to turn-off this behavior? It had until a few days
ago
> > > still works, ie I was not logged ou
Am Donnerstag, 19. November 2015, 18:42:58 schrieb Michael Biebl:
> Am 19.11.2015 um 18:22 schrieb Singer Michael:
> > What else can I do to turn-off this behavior? It had until a few days ago
> > still works, ie I was not logged out of the execution of the command
> > "systemctl isolate multi-user
Am 19.11.2015 um 18:22 schrieb Singer Michael:
> What else can I do to turn-off this behavior? It had until a few days ago
> still works, ie I was not logged out of the execution of the command
> "systemctl isolate multi-user.target".
With which systemd version did it still work?
--
Why is it
Am Donnerstag, 19. November 2015, 17:52:54 schrieb Michael Biebl:
> Hm, gettys have IgnoreOnIsolate=yes set, so this shouldn't happen.
>
> If you remove libpam-systemd, and re-login, i.e. you don't have a logind
> session registered, do you still get logged out?
Hi Michael,
Sorry, but the removal
Am 19.11.2015 um 17:16 schrieb Singer Michael:
> Reproducible steps (variant 1):
> 1. system is booted into the grahical.target (including login on KDE desktop)
> 2. With the key combination CTRL-ALT-F1 switch to the text console (tty)
> 3. Login as root on the system
> 4. "systemctl isolate multi-
Am Mittwoch, 18. November 2015, 23:56:55 schrieb Michael Biebl:
> Am 18.11.2015 um 09:57 schrieb Singer Michael:
> > Package: systemd
> > Version: 227-3
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > When changing the target you will be logged out automatically, for
> > example, with the f
Hello,
On Thu, Nov 19, 2015 at 4:07 PM, Michael Biebl wrote:
> I just realized, that you use systemd-networkd and
> systemd-networkd-wait-online. With that setup I do indeed run into a
> real dead-lock.
Yes, I use systemd-networkd because it's perfectly adequate for my use
case and I have a (per
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/1961
Bug #805477 [systemd] systemd: Leak of scope units slowing down "systemctl
list-unit-files" and delaying logins
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/1961'.
--
805477
Control: forwarded -1 https://github.com/systemd/systemd/issues/1961
Am 19.11.2015 um 16:13 schrieb Julian Brost:
> I've built systemd 228-1 with that patch removed and I could still
> reproduce the problem.
>
> I could also reproduce it on Arch Linux with systemd 227, so the issue
> isn't specif
On 18.11.2015 21:27, Felipe Sateler wrote:
> Maybe this is related to a debian-specific patch[1]? Julian, could you
> try with this patch removed?
>
>
> [1]
> http://sources.debian.net/src/systemd/227-3/debian/patches/Revert-core-one-step-back-again-for-nspawn-we-actual.patch
I've built system
Am 19.11.2015 um 15:42 schrieb Michael Biebl:
> The boot did continue after 90 seconds though
> https://people.debian.org/~biebl/Debian%20Stretch.webm
>
> Given that, I'm downgrading the severity.
I just realized, that you use systemd-networkd and
systemd-networkd-wait-online. With that setup I d
Control: severity -1 important
Am 19.11.2015 um 15:16 schrieb Michael Biebl:
> Btw, how do you configure your network? NetworkManager or ifupdown?
I tried with NetworkManager.
This resulted in systemd-tmpfiles-setup.service and srv.mount failing
during boot (I setup /srv as NFS automount)
> -- L
Processing control commands:
> severity -1 important
Bug #805553 [systemd] systemd 228-1 fails to boot: hangs in Create Volatile
Files and Directories
Severity set to 'important' from 'critical'
--
805553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805553
Debian Bug Tracking System
Contac
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/1959
Bug #805553 [systemd] systemd 228-1 fails to boot: hangs in Create Volatile
Files and Directories
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/1959'.
--
805553: http://bugs.
Control: forwarded -1 https://github.com/systemd/systemd/issues/1959
Am 19.11.2015 um 15:18 schrieb Michael Biebl:
> Am 19.11.2015 um 15:16 schrieb Michael Biebl:
>> I can confirm, that with 227, "v /home" does not trigger a mount request
>> and with 228 "Q /home" does.
>
> Both q and Q trigger a
Am 19.11.2015 um 15:16 schrieb Michael Biebl:
> I can confirm, that with 227, "v /home" does not trigger a mount request
> and with 228 "Q /home" does.
Both q and Q trigger a mount request.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Ea
Am 19.11.2015 um 14:54 schrieb Lorenz Hübschle-Schneider:
> I will try re-upgrading later this afternoon and let it run for a longer
> time, but the message was "$x sec / no limit".
>
> Felipe, are you referring to /usr/lib/tmpfiles.d/home.conf? I will try that
> out as well.
>
> With a normal mo
On 19 November 2015 at 10:54, Lorenz Hübschle-Schneider
wrote:
> I will try re-upgrading later this afternoon and let it run for a longer
> time, but the message was "$x sec / no limit".
>
> Felipe, are you referring to /usr/lib/tmpfiles.d/home.conf? I will try that
> out as well.
Yes, that file.
I will try re-upgrading later this afternoon and let it run for a longer
time, but the message was "$x sec / no limit".
Felipe, are you referring to /usr/lib/tmpfiles.d/home.conf? I will try that
out as well.
With a normal mount I previously had cyclic dependency issues, as I want to
bind-mount a
Am 19.11.2015 um 14:29 schrieb Felipe Sateler:
> Control: tags -1 moreinfo
>
> On 19 November 2015 at 09:59, Lorenz Hübschle-Schneider
> wrote:
>> Package: systemd
>> Version: 228-1
>> Severity: critical
>> Justification: breaks the whole system
>>
>> Dear Maintainer,
>>
>> after the upgrade to s
Control: tags -1 moreinfo
On 19 November 2015 at 09:59, Lorenz Hübschle-Schneider
wrote:
> Package: systemd
> Version: 228-1
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> after the upgrade to systemd 228-1, my system failed to boot. It got stuck in
> "Cre
Processing control commands:
> tags -1 moreinfo
Bug #805553 [systemd] systemd 228-1 fails to boot: hangs in Create Volatile
Files and Directories
Added tag(s) moreinfo.
--
805553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805553
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Your message dated Thu, 19 Nov 2015 10:50:01 +
with message-id
and subject line Bug#805497: fixed in systemd 228-2
has caused the Debian Bug report #805497,
regarding update libseccomp build-depends
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 19 Nov 2015 11:37:45 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines
libnss-resolve libsystemd0 libs
systemd_228-2_source.changes uploaded successfully to localhost
along with the files:
systemd_228-2.dsc
systemd_228-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
___
Pkg-systemd-maintainers mailing
Am 19.11.2015 um 11:20 schrieb Martin Pitt:
> Just to conclude this for the mail archives: This has been resolved
> upstream in 228. networkd now only enables forwarding, never disables
> it, so the global control is back working:
>
> https://github.com/poettering/systemd/commit/765afd5c4dbc
\
Hello all,
Martin Pitt [2015-10-05 15:53 +0200]:
> upstream networkd (and in Debian up to now) defaults to IPForward=no
> (see man systemd.network), i. e. if you configure a network interface
> through networkd without explicitly setting IPForward=, the
> per-interface setting (/proc/sys/net/ipv{4
Hello Michael,
Michael Biebl [2015-11-19 10:51 +0100]:
> Martin, I see you bumped the dep to (>= 2.2.1-2). If we really want to
> support backports that should be 2.2.1-2~
My bad. Fixed.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.c
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/pull/1953
Bug #805514 [systemd] gitignore in sources ignores needed file
Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/1953'.
> tag -1 upstream confirmed
Bug #805514 [systemd] gitignore in sou
Control: forwarded -1 https://github.com/systemd/systemd/pull/1953
Control: tag -1 upstream confirmed
Hello Daniel,
Daniel Baumann [2015-11-19 2:21 +0100]:
> the top-level .gitignore file excludes all *.html files. This makes
> src/journal-remote/browse.html being excluded, which is a needed fil
Am 19.11.2015 um 10:35 schrieb Daniel Baumann:
> On 11/19/2015 10:18 AM, Michael Biebl wrote:
>> I don't expect the failure is because the lib was moved to /lib.
>
> it does. dh_shlibdeps bails with 'something is depending on /usr' which
> in that case is libseccomp (that in older versions (jessie
On 11/19/2015 10:18 AM, Michael Biebl wrote:
> I don't expect the failure is because the lib was moved to /lib.
it does. dh_shlibdeps bails with 'something is depending on /usr' which
in that case is libseccomp (that in older versions (jessie) was in
/usr/lib instead of /lib).
Regards,
Daniel
__
Your message dated Thu, 19 Nov 2015 10:21:25 +0100
with message-id <564d9495.9090...@debian.org>
and subject line Re: Bug#805481: One important omission
has caused the Debian Bug report #805481,
regarding systemd 227-2 SIGSEGV on boot on arm64
to be marked as done.
This means that you claim that t
Am 19.11.2015 um 08:21 schrieb Martin Pitt:
> Control: tag -1 pending
>
> Hello Daniel,
>
> Daniel Baumann [2015-11-19 2:32 +0100]:
>> True, but when building systemd on a system with too old libseccomp,
>> e.g. when backporting systemd to jessie, it FTBFS.
>
> Ah, that's a good reason to bump
Hi
Am 19.11.2015 um 02:32 schrieb Daniel Baumann:
> On 11/18/2015 09:22 PM, Michael Biebl wrote:
>> Unfortunately, bumping the build-depends on
>> libseccomp-dev has no effect. The generated dependency on libseccomp2
>> would still be the same.
>
> True, but when building systemd on a system with
On 18 November 2015 at 18:23, Michael Biebl wrote:
> Am 18.11.2015 um 18:35 schrieb Steven Capper:
> > Upgrading to 227-1 caused immediate segfaults and led to the same
> > unbootable machine.
> >
> > So it looks like something introduced 227-1.
>
> I would guess this was introduced by
>
>
> http
39 matches
Mail list logo
