Приветы

___ 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: bug 807122 is forwarded to https://github.com/systemd/systemd/issues/2183

Processing commands for cont...@bugs.debian.org: > forwarded 807122 https://github.com/systemd/systemd/issues/2183 Bug #807122 [systemd] systemd-resolved: static dns entries Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/2183'. > thanks Stopping processing here.

Здравствуйте.

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

Bug#808151: systemd: failed to start remount root and kernel file system

Am 17.12.2015 um 13:46 schrieb Frank B. Brokken: > Dear Michael Biebl, you wrote: > >> What happens afterwards? Are you dropped into the rescue shell? > > Afterwards (i.e., after the initial failure message) the system tries to > continue booting, but shows lots of failure messages, eventually

Processed: bug 808222 is forwarded to https://github.com/systemd/systemd/issues/2186

Processing commands for cont...@bugs.debian.org: > forwarded 808222 https://github.com/systemd/systemd/issues/2186 Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists Set Bug forwarded-to-address to

Bug#808151: systemd: failed to start remount root and kernel file system

Dear Michael Biebl, you wrote: > What happens afterwards? Are you dropped into the rescue shell? Afterwards (i.e., after the initial failure message) the system tries to continue booting, but shows lots of failure messages, eventually grinding to a halt. No reboot (e.g. ctrl-alt-del) is possible

Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

Package: systemd-container Version: 227-2 Severity: important File: /usr/bin/systemd-nspawn systemd-nspawn --link-journal=host should accept an existing directory. root@iron:~# systemctl start systemd-nspawn@foo [ everything works ] root@iron:~# systemctl stop systemd-nspawn@foo root@iron:~#

Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

Control: severity -1 normal Control: tags -1 upstream Hi Am 17.12.2015 um 13:06 schrieb Matthias Urlichs: > Package: systemd-container > Version: 227-2 > Severity: important > File: /usr/bin/systemd-nspawn > > systemd-nspawn --link-journal=host should accept an existing directory. > Please

Processed: Re: Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

Processing control commands: > severity -1 normal Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists Severity set to 'normal' from 'important' > tags -1 upstream Bug #808222 [systemd-container] /usr/bin/systemd-nspawn:

Processed: propased patch should be enough

Processing commands for cont...@bugs.debian.org: > tags 804882 - moreinfo Bug #804882 [systemd] fix lsb hook reload for masked services Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 804882:

Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

On 17.12.2015 14:59, Michael Biebl wrote: > Control: severity -1 normal > Control: tags -1 upstream > > Hi > > Am 17.12.2015 um 13:06 schrieb Matthias Urlichs: >> Package: systemd-container >> Version: 227-2 >> Severity: important >> File: /usr/bin/systemd-nspawn >> >> systemd-nspawn

Bug#808151: systemd: failed to start remount root and kernel file system

Dear Michael Biebl, you wrote: > Am 17.12.2015 um 13:46 schrieb Frank B. Brokken: > > halt. No reboot (e.g. ctrl-alt-del) is possible and there's no rescue > > shell> > What exactly do you mean with halt? The systems completely locks up so > you can't use the keyboard and switch to tty9? No,

Bug#808222: Upstream bug

https://github.com/systemd/systemd/issues/2186 -- -- Matthias Urlichs ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#808151: systemd: failed to start remount root and kernel file system

Am 17.12.2015 um 16:24 schrieb Frank B. Brokken: > This time the debug shell prompt was available at tty9, although booting > failed. And in line with my previous findings, systemd-analyze and journalctl > weren't available, as they live in /usr/bin, and /usr hadn't been mounted. But Well, /usr

Processed: unarchiving 761909

Processing commands for cont...@bugs.debian.org: > unarchive 761909 Bug #761909 {Done: Martin Pitt } [systemd] systemd does not unmount nfs shares before bringing down the network interface Unarchived Bug 761909 > thanks Stopping processing here. Please contact me if you need

Bug#808151: systemd: failed to start remount root and kernel file system

Am 17.12.2015 um 22:38 schrieb Michael Biebl: > Am 17.12.2015 um 16:24 schrieb Frank B. Brokken: >> This time the debug shell prompt was available at tty9, although booting >> failed. And in line with my previous findings, systemd-analyze and journalctl >> weren't available, as they live in