Hello all,
Steve Langasek [2018-02-22 16:36 -0800]:
> > OK, so I suppose we could replace the check with
>
> > if running_systemd
> > wait for network-online.target
> > else
> > wait for runlevel 2
I modified Iain's initial patch and tested/applied:
hon-modules-team@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
python-dbusmock - mock D-Bus objects for tests (Python 2)
python3-dbusmock - mock D-Bus objects for tests (Python 3)
Changes:
python-dbusmock (0.17.1-1) unstable; urgency=medium
.
* New upst
hon-modules-t...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
python-dbusmock - mock D-Bus objects for tests (Python 2)
python3-dbusmock - mock D-Bus objects for tests (Python 3)
Changes:
python-dbusmock (0.17.1-1) unstable; urgency=medium
.
* New upst
cockpit-ws
Architecture: source amd64 all
Version: 162-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
co
cockpit-ws
Architecture: source amd64 all
Version: 162-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
co
ockpit-162-1.fc27
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/162
Take care,
Martin Pitt
signature.asc
Description: PGP signature
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubs
Antonio Terceiro [2018-02-21 10:39 -0300]:
> > Cheers! I reworked it a bit, applied the same strategy to LXC (which is
> > equally affected), tested it, and landed
> >
> >
> > https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=20f479254
>
> Aren't _all_ types of testbed
** Changed in: autopkgtest (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749736
Title:
autopkgtest-build-lxd fails to build artful/bionic containers
To
Steve Langasek [2018-02-16 11:12 -0800]:
> > > [ -n "$(ip route show to 0/0)" ]
>
> > This is better though, and works too. Please take a look at the attached
> > patch. Thanks! :-)
>
> Actually no, this is racy, because the route comes up before DNS resolution
> is in place.
I'm not actually
signed) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749736
Title:
autopkgtest-build-lxd fails to build artful/bionic containers
To manage notifications about this bug go
Hello all,
Iain Lane [2018-02-16 11:52 +]:
> > I wouldn't pick on any of these: network-online.target is a sloppily defined
> > shim for SysV init backwards compatibility, and may not ever get started (in
> > fact, that's the goal ☺); and the container might not use networkd, so I
> >
Public bug reported:
As per documentation, the `-B best` option should automatically select
the best backingstore, falling back all the way to dir.
But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:
$ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
Public bug reported:
As per documentation, the `-B best` option should automatically select
the best backingstore, falling back all the way to dir.
But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:
$ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
Thanks Gunnar, nice work! I cherry-picked the patches in
https://salsa.debian.org/systemd-team/systemd/commit/87f54958bc24 . The
debian/ changes were already in Debian master.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification
Thanks Gunnar, nice work! I cherry-picked the patches in
https://salsa.debian.org/systemd-team/systemd/commit/87f54958bc24 . The
debian/ changes were already in Debian master.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification
Thanks Gunnar, nice work! I cherry-picked the patches in
https://salsa.debian.org/systemd-team/systemd/commit/87f54958bc24 . The
debian/ changes were already in Debian master.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification
I propose to add a check for the default network route to the "is the container
up?" polling loop:
https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040158.html
** Changed in: autopkgtest (Ubuntu)
Status: New => Triaged
** Changed in: autopkgtest (Ubuntu)
Importance:
Hello Timo,
Timo Aaltonen [2018-02-15 16:50 +0200]:
> On 14.02.2018 22:03, Dimitri John Ledkov wrote:
> > Hi,
> >
> > I am on bionic and managed to build bionic container for testing using:
> >
> > $ autopkgtest-build-lxd ubuntu-daily:bionic/amd64
> >
> > Note this uses Ubuntu Foundations
I confirmed that the current "ninja -C build-deb/ systemd-pot" command
also builds a complete .pot file with policykit-1 installed
(unsurprisingly, as this also just calls gettext). So that part is fine.
What is really bad however, is to build-depend against policykit-1:
The following NEW
I confirmed that the current "ninja -C build-deb/ systemd-pot" command
also builds a complete .pot file with policykit-1 installed
(unsurprisingly, as this also just calls gettext). So that part is fine.
What is really bad however, is to build-depend against policykit-1:
The following NEW
I confirmed that the current "ninja -C build-deb/ systemd-pot" command
also builds a complete .pot file with policykit-1 installed
(unsurprisingly, as this also just calls gettext). So that part is fine.
What is really bad however, is to build-depend against policykit-1:
The following NEW
Thanks Gunnar for tracking this down! Adding a policykit-1 build
dependency requires some thought, as that also build-depends on systemd
[1], thus this is circular. Also, there was a lot of effort with making
systemd bootstrappable without excessive dependencies. But I think it's
fine to add this
Thanks Gunnar for tracking this down! Adding a policykit-1 build
dependency requires some thought, as that also build-depends on systemd
[1], thus this is circular. Also, there was a lot of effort with making
systemd bootstrappable without excessive dependencies. But I think it's
fine to add this
Thanks Gunnar for tracking this down! Adding a policykit-1 build
dependency requires some thought, as that also build-depends on systemd
[1], thus this is circular. Also, there was a lot of effort with making
systemd bootstrappable without excessive dependencies. But I think it's
fine to add this
Control: tag -1 pending
Hello Lars,
Lars Michelsen [2018-02-14 17:32 +]:
> systemd-sysv-install uses `ROOT` variable from environment when not set
> via `-r` and tries to execute update-rc.d chrooted to the content of
> this variable.
Thanks for the report! Fixed:
Control: tag -1 pending
Hello Lars,
Lars Michelsen [2018-02-14 17:32 +]:
> systemd-sysv-install uses `ROOT` variable from environment when not set
> via `-r` and tries to execute update-rc.d chrooted to the content of
> this variable.
Thanks for the report! Fixed:
@Gunnar: This patch does not actually work:
❱❱❱ xgettext -f "po/POTFILES.in" -o "build-deb/po/systemd.pot" --join-existing
xgettext: warning: file 'src/core/org.freedesktop.systemd1.policy.in.in'
extension 'policy' is unknown; will try C
xgettext: warning: file
@Gunnar: This patch does not actually work:
❱❱❱ xgettext -f "po/POTFILES.in" -o "build-deb/po/systemd.pot" --join-existing
xgettext: warning: file 'src/core/org.freedesktop.systemd1.policy.in.in'
extension 'policy' is unknown; will try C
xgettext: warning: file
@Gunnar: This patch does not actually work:
❱❱❱ xgettext -f "po/POTFILES.in" -o "build-deb/po/systemd.pot" --join-existing
xgettext: warning: file 'src/core/org.freedesktop.systemd1.policy.in.in'
extension 'policy' is unknown; will try C
xgettext: warning: file
I committed the first hunk to Debian, this makes sense:
https://salsa.debian.org/systemd-team/systemd/commit/18d8c2df133b8af
The second is too hackish for a permanent downstream delta, IMHO: This
should rather be fixed upstream, as upstream polkit (as well as Debian's
and Ubuntu's older versions)
I committed the first hunk to Debian, this makes sense:
https://salsa.debian.org/systemd-team/systemd/commit/18d8c2df133b8af
The second is too hackish for a permanent downstream delta, IMHO: This
should rather be fixed upstream, as upstream polkit (as well as Debian's
and Ubuntu's older versions)
I committed the first hunk to Debian, this makes sense:
https://salsa.debian.org/systemd-team/systemd/commit/18d8c2df133b8af
The second is too hackish for a permanent downstream delta, IMHO: This
should rather be fixed upstream, as upstream polkit (as well as Debian's
and Ubuntu's older versions)
cockpit-ws
Architecture: source
Version: 161-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux serv
Control: tag -1 pending
Hello Jonas,
Jonas Smedegaard [2018-02-10 15:22 +0100]:
> Now, please change package section of the scour package to be graphics.
Oops, thanks for pointing out. Done in git.
In the meantime, can you override the section in the archive, or should I file
a release.d.o bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 09 Feb 2018 22:27:43 +0100
Source: umockdev
Binary: umockdev libumockdev0 libumockdev-dev gir1.2-umockdev-1.0
Architecture: source amd64
Version: 0.11-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <
Hello Stef,
Stef Walter [2018-02-06 14:30 +0100]:
> I'd like to remove the following outdated repos from the
> https://github.com/cockpit-project/
Thanks for the cleanup!
these also look obsolete and should be removed:
https://github.com/cockpit-project/storaged
got "archived" > 2 years
project.org/running.html
Cockpit 161 is available in Fedora 27:
https://bodhi.fedoraproject.org/updates/cockpit-161-1.fc27
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/161
Take care,
Martin Pitt
signature.asc
Description: PGP signature
___
cockpit-ws
Architecture: source amd64 all
Version: 161-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
co
cockpit-ws
Architecture: source amd64 all
Version: 161-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
co
Hello all,
Our cockpit JS API documentation currently has some way outdated information
about jQuery [1], suggesting that users of the Cockpit API should always load
jQuery, and use the Cockpit bundled version. This hasn't been true for a long
time, and was just forgotten to be cleaned up. Also,
Hello Johannes,
Johannes Schauer [2018-01-12 14:27 +0100]:
> My central question: is it totally out of scope for autopkgtest to support
> modifying the underlying base image?
IMHO yes, as I laid out in my previous reply. I don't want autopkgtest to get
into the business of being a "VM manager",
Hello Michael, all,
Michael Vogt [2018-01-23 16:15 +0100]:
> There is no downside (AFAICS), the unit is conditiional on
> ConditionNeedsUpdate=/etc so it will never run on default Debian
> systems.
Agreed. It will mostly be dead weight in the systemd packages, but the new tool
isn't too big, and
Hello Michael, all,
Michael Vogt [2018-01-23 16:15 +0100]:
> There is no downside (AFAICS), the unit is conditiional on
> ConditionNeedsUpdate=/etc so it will never run on default Debian
> systems.
Agreed. It will mostly be dead weight in the systemd packages, but the new tool
isn't too big, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 23 Jan 2018 10:21:21 +0100
Source: scour
Binary: python-scour python3-scour scour
Architecture: source all
Version: 0.36-2
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <mp...@debian.org>
Changed-By:
cockpit-ws
Architecture: source amd64 all
Version: 160-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
co
Adrian Bunk [2018-01-23 16:53 +0200]:
> > ... so that after
> > the buster release I can remove the python-scour → scour dependency again.
>
> Nitpick:
> After buster python-scour will be removed (no Python 2 in bullseye).
So much the better! /me starts sharpening the knife :-)
Martin
Adrian Bunk [2018-01-23 16:53 +0200]:
> > ... so that after
> > the buster release I can remove the python-scour → scour dependency again.
>
> Nitpick:
> After buster python-scour will be removed (no Python 2 in bullseye).
So much the better! /me starts sharpening the knife :-)
Martin
Control: tag -1 pending
Hello Adrian and all,
Adrian Bunk [2018-01-23 7:54 +0200]:
> This is actually a bug in scour, where the scour binary and debhelper
> addon moved from python-scour to python3-scour.
>
> Neither is the right place.
>
> scour should go into an own binary package of the
Control: tag -1 pending
Hello Adrian and all,
Adrian Bunk [2018-01-23 7:54 +0200]:
> This is actually a bug in scour, where the scour binary and debhelper
> addon moved from python-scour to python3-scour.
>
> Neither is the right place.
>
> scour should go into an own binary package of the
Package: libvirt-daemon-system
Version: 3.10.0-1
Severity: minor
When operating VMs with libvirt and AppArmor installed, the Cockpit integration
tests commonly see these denials:
audit: type=1400 audit(1516609717.472:41): apparmor="DENIED"
operation="signal" profile="/usr/sbin/libvirtd"
Michael Biebl [2018-01-16 7:41 +0100]:
> Even with this fix though, we should imho make sure to have
> libnss-systemd installed by default.
> See the problem with Recommends and the initial bootstrap I mentioned
> earlier.
> What are we going to do about this?
Hmm, in Debian I don't think we
Michael Biebl [2018-01-16 7:41 +0100]:
> Even with this fix though, we should imho make sure to have
> libnss-systemd installed by default.
> See the problem with Recommends and the initial bootstrap I mentioned
> earlier.
> What are we going to do about this?
Hmm, in Debian I don't think we
Guido Günther [2018-01-15 12:14 +0100]:
> > > This seems to be caused by the fact that libnss-systemd is not a hard
> > > dependency of systemd. I'm not sure what the best solution is? Having a
> > > service that is enabled by fails to start looks weird though. Maybe
> > > providing a static user
Guido Günther [2018-01-15 12:14 +0100]:
> > > This seems to be caused by the fact that libnss-systemd is not a hard
> > > dependency of systemd. I'm not sure what the best solution is? Having a
> > > service that is enabled by fails to start looks weird though. Maybe
> > > providing a static user
Hello Dorian,
Dorian ROSSE [2018-01-10 9:35 +]:
> Since I have kernel 4.14.12 I have two errors :
>
> apparmor failed because It failed to start LSB the status exit code is 123
> and there is a error by program /etc/apparmor.d/usr.lib.snapd-confine.real in
> line 11 unable to open
cockpit-ws
Architecture: source amd64 all
Version: 159-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
co
in Fedora 27:
https://bodhi.fedoraproject.org/updates/cockpit-159-1.fc27
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/159
Take care,
Martin Pitt
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsub
Control: reassign -1 systemd 236-1
Control: forcemerge 885325 -1
Hello,
Marius Vollmer [2018-01-10 10:59 +0200]:
> Version: 1:7.6p1-2
>
> Mounting or unmounting filesystems from within a ssh session used to
> affect all processes, but now it only affects ssh sessions (all of them,
> not just
Hello all,
https://devconf.cz/ is approaching fast! As last year, we will host a Cockpit
Hackfest community meetup again. Please come join us if you want to learn about
how to create your own Cockpit pages, improve the existing ones, poke our
brains about how to do stuff, or simply say hello.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 07 Jan 2018 23:02:46 +0100
Source: umockdev
Binary: umockdev libumockdev0 libumockdev-dev gir1.2-umockdev-1.0
Architecture: source amd64
Version: 0.10-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <
Hello Johannes,
Johannes Schauer [2018-01-04 15:46 +0100]:
> my use case is: use the autopkgtest qemu backend with sbuild. This works
> well after having created the image with vmdebootstrap but after a while
> the image has to be persistently upgraded. It would be nice if you could
> either:
>
The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.
--
You received this bug notification because you are a member of Ubuntu
Touch
The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.
--
You received this bug notification because you are a member of Ubuntu
Touch
I locally ran Cockpit tests on our current Ubuntu 17.10 image and re-
confirm that I got the "disconnected path" error. I then upgraded the
ntp package to artful-proposed, and *that* violation is now gone. As
others already saw, I now get a test failure on
apparmor="DENIED" operation="open"
I locally ran Cockpit tests on our current Ubuntu 17.10 image and re-
confirm that I got the "disconnected path" error. I then upgraded the
ntp package to artful-proposed, and *that* violation is now gone. As
others already saw, I now get a test failure on
apparmor="DENIED" operation="open"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 23 Dec 2017 15:46:30 +0100
Source: scour
Binary: python-scour python3-scour
Architecture: source all
Version: 0.36-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <mp...@debian.org>
Changed-By: Martin Pi
Thanks Christian! Indeed this is rather hard to reproduce locally, but
that PR seems to address this. I'll let you know if it doesn't after it
lands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Christian! Indeed this is rather hard to reproduce locally, but
that PR seems to address this. I'll let you know if it doesn't after it
lands.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
it 158 is available in Fedora 27:
https://bodhi.fedoraproject.org/updates/cockpit-158-1.fc27
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/158
Take care,
Martin Pitt
signature.asc
Description: PGP signature
_
cockpit-ws
Architecture: source
Version: 158-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
cockpit-brid
Control: tag -1 patch -unreproducible
Michael Biebl [2017-10-23 18:22 +0200]:
> This is what I get when I *shut down* a VM in virt-manager:
> $ journalctl -f | grep DENIED
> Okt 23 18:20:31 pluto audit[8603]: AVC apparmor="DENIED"
> operation="open"
: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
gir1.2-upowerglib-1.0 - GObject introspection data for upower
libupower-glib-dev - abstraction for power management - development files
libupower-glib3 -
Christian: This bug now hit debian-testing (see
http://209.132.184.41/logs/pull-8219-20171206-214646-d2e9e141-verify-
debian-testing/log.html#2). Is there an upstream bug/patch mail for
reference, or are these Debian/Ubuntu downstream rules?
** Bug watch added: Debian Bug tracker #878203
Christian: This bug now hit debian-testing (see
http://209.132.184.41/logs/pull-8219-20171206-214646-d2e9e141-verify-
debian-testing/log.html#2). Is there an upstream bug/patch mail for
reference, or are these Debian/Ubuntu downstream rules?
** Bug watch added: Debian Bug tracker #878203
cockpit-ws
Architecture: source
Version: 157-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
cockpit-brid
he tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/157
Take care,
Martin Pitt
signature.asc
Description: PGP signature
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpi
Once you do this, these fallbacks should be cleaned up:
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L30
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L137
--
You received this bug
Once you do this, these fallbacks should be cleaned up:
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L30
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L137
--
You received this bug
Package: libvirt-daemon-system
Version: 3.9.0-1
Tags: patch
Since recent package updates in testing, handling VMs now causes AppArmor
violations about reading NSS related files:
| audit: type=1400 audit(1511825664.488:26): apparmor="DENIED" operation="open"
profile="virt-aa-helper"
-1.fc27
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/156
Take care,
Martin Pitt
signature.asc
Description: PGP signature
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe
cockpit-ws
Architecture: source amd64 all
Version: 156-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
cockpit- User interface for Linux servers
co
libsystemd0 libsystemd-dev udev
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source amd64
Version: 235-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@d
Patches backported into Debian packaging git:
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=9bba5469f2b95ea9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725348
Title:
Patches backported into Debian packaging git:
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=9bba5469f2b95ea9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Control: tag -1 pending
Martin Pitt [2017-10-11 22:37 +0200]:
> if there's any doubt in whether it's safe to remove, I think it's okay to not
> bother -- after all, a DynamicUser= unit will still use the existing system
> user if it exists, so there isn't that much gain in cleaning it
Control: tag -1 pending
Martin Pitt [2017-10-11 22:37 +0200]:
> if there's any doubt in whether it's safe to remove, I think it's okay to not
> bother -- after all, a DynamicUser= unit will still use the existing system
> user if it exists, so there isn't that much gain in cleaning it
Control: tag -1 pending
Michael Biebl [2017-10-11 18:41 +0200]:
> This one seems safe. v232 from stretch no longer ships the
> systemd-bus-proxyd service, so we can safely drop the useradd call and
> remove the obsolete system user account.
Agreed. Done in git.
Martin
Control: tag -1 pending
Michael Biebl [2017-10-11 18:41 +0200]:
> This one seems safe. v232 from stretch no longer ships the
> systemd-bus-proxyd service, so we can safely drop the useradd call and
> remove the obsolete system user account.
Agreed. Done in git.
Martin
es/cockpit-155-1.fc27
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/155
Take care,
Martin Pitt
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpi
hon-modules-t...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
python-dbusmock - mock D-Bus objects for tests (Python 2)
python3-dbusmock - mock D-Bus objects for tests (Python 3)
Closes: 836053
Changes:
python-dbusmock (0.17-1) unstable; urgency=medium
This still happens all the time, also in 17.10, reopening. I need to
find some time to create a reproducer that doesn't involve the Cockpit
tests.
** Changed in: libvirt (Ubuntu)
Status: Expired => Incomplete
** Changed in: libvirt (Ubuntu Xenial)
Status: Expired => Confirmed
--
This still happens all the time, also in 17.10, reopening. I need to
find some time to create a reproducer that doesn't involve the Cockpit
tests.
** Changed in: libvirt (Ubuntu)
Status: Expired => Incomplete
** Changed in: libvirt (Ubuntu Xenial)
Status: Expired => Confirmed
--
Nice work, thanks Christian!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729626
Title:
AppArmor denies access to /sys/block/*/queue/max_segments
To manage notifications about this bug go to:
Public bug reported:
Since Cockpit's "ubuntu stable" VM image got updated from Ubuntu 17.04
to 17.10, the libvirt tests now cause several instances of this AppArmor
denial:
Nov 02 10:19:28 unassigned-hostname audit[1347]: AVC apparmor="DENIED"
operation="open"
This also gets detected by the cockpit integration tests in
https://github.com/cockpit-project/cockpit/pull/7939, so I spent an hour
to create a minimal reproducer (attached), only to find that this is
already fixed in -proposed.
I confirm that with the -proposed package this works again. Thanks!
Public bug reported:
Merely installing and starting ntp.service in Ubuntu 17.10 now causes
this AppArmor violation:
audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
operation="sendmsg" info="Failed name lookup - disconnected path"
error=-13 profile="/usr/sbin/ntpd"
Public bug reported:
Merely installing and starting ntp.service in Ubuntu 17.10 now causes
this AppArmor violation:
audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
operation="sendmsg" info="Failed name lookup - disconnected path"
error=-13 profile="/usr/sbin/ntpd"
Hello Ximin, all,
Ximin Luo [2017-10-20 12:23 +0200]:
> These days one is able to mark build-dependencies that are needed to run tests
> by annotating the Build-Depends with .
>
> It would be nice to support a @testdeps@ syntax for Depends: in autopkgtest
> as a
> convenience alias for all of
901 - 1000 of 91297 matches
Mail list logo
