)
Status: New => In Progress
** Changed in: bolt (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: umockdev (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hello Carlos,
carlos castro [2021-09-20 8:38 +0100]:
> I would like to use cockpit as and update manager for all my linux machines.
>
> My question is if i can only install this component, and if so how can i do
> it,
The minimum packages that you can install are cockpit-packagekit for the
se.
* Create a separate length for session_id.
Add 0004-CVE-2021-3634-Create-a-separate-length-for-session_i.patch and
0005-tests-Simple-reproducer-for-rekeying-with-different-.patch:
Backport fix and test from upstream 0.9.6 release.
CVE-2021-3634 (Closes: #993046)
-- Martin Pitt
Control: tag -1 pending
Control: notfound -1 0.7.3-2+deb9u2
Control: notfound -1 0.8.1-1~bpo9+1
Control: notfound -1 0.8.7-1+deb10u1
Salvatore Bonaccorso [2021-08-26 22:21 +0200]:
> CVE-2021-3634[0]:
> | Possible heap-buffer overflow when rekeying
Thanks for the report! For unstable/testing I am
Hello Mark,
I'm afraid I have no further idea about the original bug -- at this point I'd
need to try this code and reproduce. But..
Mark Reynolds [2021-08-26 8:54 -0400]:
> let cmd = [
> "/bin/sh",
>
Hello Mark,
Mark Reynolds [2021-08-25 12:38 -0400]:
> This code used to work for a long time, but now it stopped working as
> expected:
>
> let cmd = [
> "/bin/sh",
> "-c",
I can't possibly believe that ' vs. " has any actual influence about it -- this
makes absolutely no
/187
Take care,
Martin Pitt
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpit-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code
Indeed the open(2) manpage is misleading in that regard. The actual
definition in fcntl.h is like this:
extern int open (const char *__file, int __oflag, ...) __nonnull
((1));
(with a few variants, but they all use varargs). So I did the same in
umockdev for full header compatibility.
--
Indeed the open(2) manpage is misleading in that regard. The actual
definition in fcntl.h is like this:
extern int open (const char *__file, int __oflag, ...) __nonnull
((1));
(with a few variants, but they all use varargs). So I did the same in
umockdev for full header compatibility.
--
Dang, we already found a ppc64el SIGBUS issue in 0.16.0, which got fixed
in https://github.com/martinpitt/umockdev/commit/277c80243a . But this
is reported against 0.16.1 already.
There is a tiny chance that
https://github.com/martinpitt/umockdev/commit/264cabbb will magically
fix this, but
Dang, we already found a ppc64el SIGBUS issue in 0.16.0, which got fixed
in https://github.com/martinpitt/umockdev/commit/277c80243a . But this
is reported against 0.16.1 already.
There is a tiny chance that
https://github.com/martinpitt/umockdev/commit/264cabbb will magically
fix this, but
Hello Simon,
Simon Walter [2021-05-27 10:17 +0900]:
> I was trying to make it quicker to deploy for those who run it like this
> anyway, but I understand not wanting to be responsible for partially
> functioning software. In that case, shall I open a bug to make systemd a
> dependency?
This is
Hello Simon,
Simon Walter [2021-05-27 10:17 +0900]:
> I was trying to make it quicker to deploy for those who run it like this
> anyway, but I understand not wanting to be responsible for partially
> functioning software. In that case, shall I open a bug to make systemd a
> dependency?
This is
Hello Lev,
Lev Veyde [2021-05-20 17:10 +0300]:
> Yes, we have some issue with the latest version of oVirt node-ng, with
> users being unable to login into cockpit after the upgrade, and we're
> trying to debug this issue:
>
>
Control: tag -1 pending
Hello Andreas,
Andreas Beckmann [2021-05-20 21:52 +0200]:
> 5m1.4s ERROR: FAIL: Broken symlinks:
> /usr/share/cockpit/branding/opensuse/default-1920x1200.jpg ->
> ../../../wallpapers/default-1920x1200.jpg (cockpit-ws)
>
Control: tag -1 pending
Hello Andreas,
Andreas Beckmann [2021-05-20 21:52 +0200]:
> 5m1.4s ERROR: FAIL: Broken symlinks:
> /usr/share/cockpit/branding/opensuse/default-1920x1200.jpg ->
> ../../../wallpapers/default-1920x1200.jpg (cockpit-ws)
>
Hello cockpiteers,
in the wake of the #Freenodecalypse [1] we have moved our IRC channel to
#cockpit on https://libera.chat/.
For the occasional "hi" you can use a web client as well [2].
The web site [3] and wiki [4] have been updated.
[1]
Control: tag -1 pending
Paul Gevers [2021-03-27 21:43 +0100]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/f/fatrace/11288159/log.gz
>
> autopkgtest [23:08:44]: test fatrace-currentmount: [---
> ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not
>
Control: tag -1 pending
Paul Gevers [2021-03-27 21:43 +0100]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/f/fatrace/11288159/log.gz
>
> autopkgtest [23:08:44]: test fatrace-currentmount: [---
> ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not
>
I installed udisks2 2.9.2-1ubuntu1 from hirsute-proposed, and confirm
that both the manual test case above as well as cockpit's automatic
TestStorageFormat.testFormatTypes now succeed. Thank you Sebastien and
Robie!
** Tags removed: verification-needed verification-needed-hirsute
** Tags added:
I installed udisks2 2.9.2-1ubuntu1 from hirsute-proposed, and confirm
that both the manual test case above as well as cockpit's automatic
TestStorageFormat.testFormatTypes now succeed. Thank you Sebastien and
Robie!
** Tags removed: verification-needed verification-needed-hirsute
** Tags added:
** Changed in: libvirt (Ubuntu Hirsute)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications
/releases/tag/243
Take care,
Martin Pitt
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpit-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
Argh indeed, forgot about that one already -- I even looked at that
before, it's tracked here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=983751
But you knew that as well, in comment #4 -- So I hope this didn't take
too much time to track down. Merci beaucoup !
** Bug watch added: Debian
Argh indeed, forgot about that one already -- I even looked at that
before, it's tracked here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=983751
But you knew that as well, in comment #4 -- So I hope this didn't take
too much time to track down. Merci beaucoup !
** Bug watch added: Debian
Direct mkfs works:
# mkfs.vfat -I -n label /dev/vdb
mkfs.fat 4.2 (2021-01-31)
mkfs.fat: Warning: lowercase labels might not work properly on some systems
# blkid -p /dev/vdb
/dev/vdb: PTUUID="892240dd" PTTYPE="dos"
** Changed in: udisks2 (Ubuntu)
Status: Incomplete => New
--
You
Direct mkfs works:
# mkfs.vfat -I -n label /dev/vdb
mkfs.fat 4.2 (2021-01-31)
mkfs.fat: Warning: lowercase labels might not work properly on some systems
# blkid -p /dev/vdb
/dev/vdb: PTUUID="892240dd" PTTYPE="dos"
** Changed in: udisks2 (Ubuntu)
Status: Incomplete => New
--
You
Reproducer from scratch:
# download current cloud image
curl -L -O
https://cloud-images.ubuntu.com/daily/server/hirsute/current/hirsute-server-cloudimg-amd64.img
# nothing fancy, just admin:foobar and root:foobar
curl -L -O
Reproducer from scratch:
# download current cloud image
curl -L -O
https://cloud-images.ubuntu.com/daily/server/hirsute/current/hirsute-server-cloudimg-amd64.img
# nothing fancy, just admin:foobar and root:foobar
curl -L -O
@Reinhard:
> Unfortunately, I cannot confirm this on a freshly installed Ubuntu
20.04
I assume this was a typo and you really meant 21.04.
> and see what's the one that breaks podman.
That was easy, it's tuned. Full reproducer:
apt install -y tuned
podman run -it --rm -p 5000:5000 --name
Thanks Reinhard for trying! I'm running a standard cloud image (https
://cloud-images.ubuntu.com/daily/server/hirsute/current/hirsute-server-
cloudimg-amd64.img), but with some additional packages installed. I'll
go through them with a fine comb and see what's the one that breaks
podman.
(But
Forgot to mention, there is nothing useful in the journal. The only
message is this when the timeout happens:
Apr 23 15:12:35 ubuntu udisksd[3116]: Error synchronizing after
formatting with type `vfat': Timed out waiting for object
** Description changed:
There is a regression somewhere
I tried to run it in the foreground with
G_MESSAGES_DEBUG=all /usr/libexec/udisks2/udisksd
but still no messages aside from the timeout.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
I tried to run it in the foreground with
G_MESSAGES_DEBUG=all /usr/libexec/udisks2/udisksd
but still no messages aside from the timeout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925822
Public bug reported:
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
Forgot to mention, there is nothing useful in the journal. The only
message is this when the timeout happens:
Apr 23 15:12:35 ubuntu udisksd[3116]: Error synchronizing after
formatting with type `vfat': Timed out waiting for object
** Description changed:
There is a regression somewhere
Public bug reported:
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
Thanks Christian! Lesson learned -- for 21.10 I'll update our images a
few weeks *before* the release. (I found a handful of regressions so
far..)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
This regressed in 21.04 (hirsute) again. 1.4.0-2 was synced from Debian
(https://launchpad.net/ubuntu/+source/libvirt-dbus/+changelog) instead
of merged.
** Tags added: hirsute regression-release
** Changed in: libvirt-dbus (Ubuntu)
Status: Fix Released => Triaged
** Also affects:
Public bug reported:
This stopped working in 21.04:
podman run -it --rm -p 5000:5000 --name registry docker.io/registry:2
curl http://localhost:5000/v2/
The curl just hangs forever. This works fine in Ubuntu 20.10 with podman
2.0.6+dfsg1-1ubuntu1.
Outbound direction is also broken:
#
Control: tag -1 pending
Martin Pitt [2021-04-12 16:23 +0200]:
> * Package name: sscg
I packaged this at https://salsa.debian.org/debian/sscg and uploaded to
experimental. It's in the NEW queue now:
https://ftp-master.debian.org/new/sscg_2.6.2-1.html
Martin
Control: tag -1 pending
Martin Pitt [2021-04-12 16:23 +0200]:
> * Package name: sscg
I packaged this at https://salsa.debian.org/debian/sscg and uploaded to
experimental. It's in the NEW queue now:
https://ftp-master.debian.org/new/sscg_2.6.2-1.html
Martin
Package: wnpp
Severity: wishlist
Owner: Martin Pitt
* Package name: sscg
Version : 2.6.2
Upstream Author : Stephen Gallagher
* URL : https://github.com/sgallagher/sscg/
* License : GPL-3+ with OpenSSL exception
Description :
sscg is a utility to aid
Package: wnpp
Severity: wishlist
Owner: Martin Pitt
* Package name: sscg
Version : 2.6.2
Upstream Author : Stephen Gallagher
* URL : https://github.com/sgallagher/sscg/
* License : GPL-3+ with OpenSSL exception
Description :
sscg is a utility to aid
Package: wnpp
Severity: wishlist
Owner: Martin Pitt
* Package name: sscg
Version : 2.6.2
Upstream Author : Stephen Gallagher
* URL : https://github.com/sgallagher/sscg/
* License : GPL-3+ with OpenSSL exception
Description :
sscg is a utility to aid
Hello all,
Pierre-Elliott Bécue [2021-04-10 18:16 +0200]:
> After a careful thinking, I agree with Elena's opinion and would rather
> not make the vote private while it already has started.
Ulrike Uhlig [2021-04-10 18:20 +0200]:
> On 10.04.21 15:33, Didier 'OdyX' Raboud wrote:
> > Le vendredi, 9
Hello Sandro,
Sandro Tosi [2021-03-25 12:21 -0400]:
> That scares me. what will happen to the list of people who disagree
> with the ratification of the statement by Debian as a project? The
> people that are so strongly pushing for this (and many other) actions
> will have a list of (in their
Package: wnpp
Severity: wishlist
Owner: Martin Pitt
* Package name: cockpit-machines
Version : 241
Upstream Author : Cockpit development team
* URL : https://github.com/cockpit-project/cockpit-machines/
* License : LGPL-2.1+
Description
Package: wnpp
Severity: wishlist
Owner: Martin Pitt
* Package name: cockpit-machines
Version : 241
Upstream Author : Cockpit development team
* URL : https://github.com/cockpit-project/cockpit-machines/
* License : LGPL-2.1+
Description
Package: wnpp
Severity: wishlist
Owner: Martin Pitt
* Package name: cockpit-machines
Version : 241
Upstream Author : Cockpit development team
* URL : https://github.com/cockpit-project/cockpit-machines/
* License : LGPL-2.1+
Description
Hello Peter,
thanks for your investigations!
Der PCFreak [2021-03-12 22:56 +0100]:
> Actually the correct command to refresh is |pkcon refresh force|.
Oops, sorry, yes -- (non)intuitive syntax for the win :-/
> Setting a proxy within |/etc/PackageKit/PackageKit.conf| with |ProxyHTTP=|
> was
** Changed in: fatrace (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861053
Title:
no fatrace output in focal
Status in fatrace package in
** Changed in: fatrace (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861053
Title:
no fatrace output in focal
To manage notifications about this bug go
Hello PCFreak,
Der PCFreak [2021-03-12 9:17 +0100]:
> https://bugzilla.redhat.com/show_bug.cgi?id=1348843
>
> Any idea how to set a proxy for cockpit-packagekit or is packagekit still
> not supporting it?
That bugzilla's comment #14 says:
You need to set the ProxyHTTP= key in
Hello Fergal,
Fergal Cassidy [2021-03-01 17:07 -]:
> Id like to be able to connect to wifi access points directly within cockpit
> instead of having to launch a terminal and use nmcli commands.
> I dont get any wifi connection options. Is there something missing on my
> system?
There is
Control: tag -1 upstream fixed-upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/15438
Hello Nicolas,
Nicolas George [2021-02-25 12:27 +0100]:
> When trying for a read-only root filesystem, I am blocked by the fact
> that cockpit tries to write in /etc at
Control: tag -1 upstream fixed-upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/15438
Hello Nicolas,
Nicolas George [2021-02-25 12:27 +0100]:
> When trying for a read-only root filesystem, I am blocked by the fact
> that cockpit tries to write in /etc at
I've been scratching my head over this regression [1] for a while now,
in the context of running a hirsute container on a 20.04 host (in
particular, a GitHub workflow machine) In my case, the symptom is that
after upgrading glibc, `which` is broken; that of course also uses
faccessat(), similar to
I've been scratching my head over this regression [1] for a while now,
in the context of running a hirsute container on a 20.04 host (in
particular, a GitHub workflow machine) In my case, the symptom is that
after upgrading glibc, `which` is broken; that of course also uses
faccessat(), similar to
Hello Stéphane,
Stéphane List [2021-02-23 20:14 +0100]:
> Is there a clamav plugin available or in dev ?
Not known to/planned by our team. If you want to have a go at it, check out
https://cockpit-project.org/blog/creating-plugins-for-the-cockpit-user-interface.html
Control: reassign -1 debconf
Control: forcemerge 983200 -1
Hello again,
Martin Pitt [2021-02-23 15:48 +0100]:
> Philip Hands [2021-02-21 10:28 +0100]:
> > Rather than waiting for debconf to be updated to provide you with a new
> > image to
> > play with, I'd sugges
Control: reassign -1 debconf
Control: forcemerge 983200 -1
Hello again,
Martin Pitt [2021-02-23 15:48 +0100]:
> Philip Hands [2021-02-21 10:28 +0100]:
> > Rather than waiting for debconf to be updated to provide you with a new
> > image to
> > play with, I'd sugges
Hello Philip,
Philip Hands [2021-02-21 10:28 +0100]:
> Rather than waiting for debconf to be updated to provide you with a new image
> to
> play with, I'd suggest going to the source, and using the SVG here:
>
> https://www.debian.org/logos/openlogo-nd.svg
Thanks, very well spotted! That's
Hello Philip,
Philip Hands [2021-02-21 10:28 +0100]:
> Rather than waiting for debconf to be updated to provide you with a new image
> to
> play with, I'd suggest going to the source, and using the SVG here:
>
> https://www.debian.org/logos/openlogo-nd.svg
Thanks, very well spotted! That's
Control: tag -1 pending
Hello Helmut,
Helmut Grohne [2021-02-19 7:29 +0100]:
> As such I propose simply annotating the dependency :native and doing so is
> sufficient to make casync cross buildable. Please consider applying the
> attached patch.
Thanks for fixing that! I applied your patch to
Control: tag -1 pending
Hello Helmut,
Helmut Grohne [2021-02-19 7:29 +0100]:
> As such I propose simply annotating the dependency :native and doing so is
> sufficient to make casync cross buildable. Please consider applying the
> attached patch.
Thanks for fixing that! I applied your patch to
I now did exactly the same steps as above on an Ubuntu 20.04 VM, with
exactly the same results. This verifies 4.33-3ubuntu1.20.04.1.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Verification for groovy:
I took a 20.10 VM with current pollinate 4.33-3ubuntu1, and after
booting, pollinate.service is in state failed as per the bug
description.
I then updated to 4.33-3ubuntu1.20.10.1. The package update auto-
restarted pollinate.service, and it looked successful:
#
Control: reassign -1 network-manager 1.29.90-1
Control: tag -1 upstream fixed-upstream
Control: forwarded -1
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662
This eventually *did* turn out to be a bug in NetworkManager itself, and only
became visible now because of the
Control: reassign -1 network-manager 1.29.90-1
Control: tag -1 upstream fixed-upstream
Control: forwarded -1
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662
This eventually *did* turn out to be a bug in NetworkManager itself, and only
became visible now because of the
Control: reassign -1 network-manager 1.29.90-1
Control: tag -1 upstream fixed-upstream
Control: forwarded -1
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662
This eventually *did* turn out to be a bug in NetworkManager itself, and only
became visible now because of the
Martin Pitt [2021-02-14 11:41 +0100]:
> So this is some weird NM build system issue that breaks something for any tag
> (i.e. minor/micro version in configure.ac) >= 1.28.0. Note that the 1.28-rc*
> tags
> have version 1.27.x.
I checked out tag 1.30-rc1 (aka version 1.29.
Martin Pitt [2021-02-14 11:41 +0100]:
> So this is some weird NM build system issue that breaks something for any tag
> (i.e. minor/micro version in configure.ac) >= 1.28.0. Note that the 1.28-rc*
> tags
> have version 1.27.x.
I checked out tag 1.30-rc1 (aka version 1.29.
Hello all,
CC'ing Thomas, maybe he has some idea about this. Thomas, please see [0] for
the python-dbusmock failure that triggered this bug report.
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
>
Hello all,
CC'ing Thomas, maybe he has some idea about this. Thomas, please see [0] for
the python-dbusmock failure that triggered this bug report.
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
>
Control: reassign -1 0.22.0-1
Control: affects -1 network-manager
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
> test_one_wifi_with_accesspoints (__main__.TestNetworkManager) ... **
>
Control: reassign -1 0.22.0-1
Control: affects -1 network-manager
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
> test_one_wifi_with_accesspoints (__main__.TestNetworkManager) ... **
>
Control: reassign -1 0.22.0-1
Control: affects -1 network-manager
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
> test_one_wifi_with_accesspoints (__main__.TestNetworkManager) ... **
>
@Christian: Debian still needs/wants to support sysvinit. Of course
init.d scripts ought to create cache directories too (like munin,
mopidy, and others already do, but probably not all of them), but that
will be a bit more work. FHS applies to SysV init as well, so the same
reasoning still holds.
** Changed in: pollinate (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848923
Title:
pollinate.service fails to start: ERROR: should execute as the
> Where could we download one of them to check the state of that path in
there?
See comment #7:
git clone https://github.com/cockpit-project/bots/
bots/vm-run ubuntu-stable
But I suppose that's moot now :)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Indeed all our images clear up /var/cache [1]. Sorry, I forgot about
this bit before! An admin should always be able to rm -rf /var/cache,
reboot, and get a fully working system [2]. So if the pollinate data is
in any way precious, it should better be in /var/lib/pollinate then
(similar to
Thanks Christian! Interesting, the "ERROR: should execute as the
[pollinate] user" looks quite unrelated to any networking setup and
smelled like a package postinst/systemd unit bug.
I started trying to reproduce this outside of the Ubuntu CI, with a most
naïve
curl -O
Hello Tobias,
Matej Marusak [2021-02-04 17:59 +0100]:
> I assume this "list of remote hosts" is not the same list of hosts on which
> you use cockpit. When you need to store some database on the server just
> pick a well defined location and use that. (like
> /usr/share/myapp/database.db)
Please
I just tested on current 20.04 and 20.10 cloud images, still the same
bug. There was exactly one upload since then [1] which was trivial (just
updating the watch file).
[1] https://launchpad.net/ubuntu/+source/pollinate/+changelog
** Changed in: pollinate (Ubuntu)
Status: Incomplete =>
One more thing: That package hasn't worked in literally years, and is
also obsolete. QEMU has had `-device virtio-rng-pci` for a long time
now, libvirt uses it by default, and apparently most cloud providers use
that, too. So I suggest to remove the package from Ubuntu, but *at
least* from the
Control: notfound -1 2.1.1+dfsg1-4
Control: found -1 2.1.1+dfsg1-5
Control: found -1 2.2.1+dfsg1-1
Control: notfound 3.0.0~rc2+dfsg1-2
Control: tag -1 pending
Capturing the affected versions as per the initial report.
Control: notfound -1 2.1.1+dfsg1-4
Control: found -1 2.1.1+dfsg1-5
Control: found -1 2.2.1+dfsg1-1
Control: notfound 3.0.0~rc2+dfsg1-2
Control: tag -1 pending
Capturing the affected versions as per the initial report.
___
Pkg-go-maintainers mailing
Package: podman
Version: 2.1.1+dfsg1-5
A few days ago, our cockpit-podman tests started to fail on Debian testing [1]
(screenshot [2]) for committing images. This coincides with the testing update
of 2.1.1+dfsg1-4 (last known good version) to 2.1.1+dfsg1-6.
CLI reproducer (as root):
# start
Package: podman
Version: 2.1.1+dfsg1-5
A few days ago, our cockpit-podman tests started to fail on Debian testing [1]
(screenshot [2]) for committing images. This coincides with the testing update
of 2.1.1+dfsg1-4 (last known good version) to 2.1.1+dfsg1-6.
CLI reproducer (as root):
# start
Hello Elhamsadat,
Elhamsadat Azarian [2021-01-27 14:10 +0330]:
> i installed cockpit on a virtual machine and it work with other vm.
> i want to know if it could work with containers on docker host too?
> does cockpit server monitor containers on docker too?
Older releases such as RHEL/CentOS 7,
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/15223
Control: tag -1 upstream pending
Hello John,
Ugh, is HPPA know to have such a poor threading performance in general?
Thanks for doing the manual build!
> We either need to skip the test-tls-certfile on hppa or greatly
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/15223
Control: tag -1 upstream pending
Hello John,
Ugh, is HPPA know to have such a poor threading performance in general?
Thanks for doing the manual build!
> We either need to skip the test-tls-certfile on hppa or greatly
Hello Helmut,
Helmut Grohne [2020-12-30 8:44 +0100]:
> unfortunately, my NMU made cracklib2 FTBFS on various architectures. It
> turns out that the py_builddir_sh also needs the _PYTHON_* variables or
> it will disagree with them. I've immediately uploaded another to fix it.
> It further
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/15074
Hello Cesare,
Cesare Leonardi [2020-12-26 16:16 +0100]:
> For this reason I believe that cockpit package should at least
> recommend "sudo".
Thanks for your report! I sent a PR upstream to adjust the dependencies
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/15074
Hello Cesare,
Cesare Leonardi [2020-12-26 16:16 +0100]:
> For this reason I believe that cockpit package should at least
> recommend "sudo".
Thanks for your report! I sent a PR upstream to adjust the dependencies
Control: tag -1 fixed-upstream pending
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/115
Hello Lucas,
Lucas Nussbaum [2020-12-26 22:57 +0100]:
> > Bail out! ERROR:../tests/test-umockdev.c:1135:t_testbed_usb_lsusb:
> > assertion failed (exit_status == 0): (256 == 0)
I
Control: tag -1 fixed-upstream pending
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/115
Hello Lucas,
Lucas Nussbaum [2020-12-26 22:57 +0100]:
> > Bail out! ERROR:../tests/test-umockdev.c:1135:t_testbed_usb_lsusb:
> > assertion failed (exit_status == 0): (256 == 0)
I
Hello Helmut,
Helmut Grohne [2020-12-26 17:39 +0100]:
> given the prolonged silence on these bugs, I've uploaded a NMU with
> delay 10 fixing both and adding a Multi-Arch stanza. All of the changes
> seem quite safe to me. I've performed local test builds for various
> configurations (nocheck,
Hello Evgeni,
as this bug report is quite old, I first re-checked this with the versions in
testing from a few days ago:
qemu-system-x86 1:5.1+dfsg-4+b2
tuned2.10.0-1
linux-image-5.9.0-4-cloud-amd64 5.9.11-1
Without tuned, cirros boots,
301 - 400 of 91297 matches
Mail list logo
