Package: libvirt-daemon
Version: 10.0.0-1
When creating a trivial VM and doing an external snapshot if the VM is *not*
running,
deleting the snapshot fails. As root:
qemu-img create -f qcow2 /var/lib/libvirt/images/test1.qcow2 10G
virt-install --memory 50 --pxe --virt-type qemu --os-variant
** Tags added: jammy regression-release
** Tags removed: regression-release
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
linux-i
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-signed (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/2049689
Title:
linux-image-5.15.0-94-generic breaks partprobe o
: #1058214)
+
+ -- Martin Pitt Wed, 10 Jan 2024 08:16:54 +0100
+
sosreport (4.0-2) unstable; urgency=medium
* d/p/0003-systemd-prefer-resolvectl-over-systemd-resolve.patch:
diff -Nru sosreport-4.0/debian/patches/0004-unittest-assertEquals.patch
sosreport-4.0/debian/patches/0004-unittest
: #1058214)
+
+ -- Martin Pitt Wed, 10 Jan 2024 08:16:54 +0100
+
sosreport (4.0-2) unstable; urgency=medium
* d/p/0003-systemd-prefer-resolvectl-over-systemd-resolve.patch:
diff -Nru sosreport-4.0/debian/patches/0004-unittest-assertEquals.patch
sosreport-4.0/debian/patches/0004-unittest
Control: forwarded -1 https://github.com/sosreport/sos/pull/3467
Control: tag -1 upstream pending
Hello Lucas and Eric,
I sent an upstream fix for this to the PR above. Their CI didn't even spot that
error yet (argh big testing gaps).
This has been open for a month now. As this threatens to make
Control: forwarded -1 https://github.com/sosreport/sos/pull/3467
Control: tag -1 upstream pending
Hello Lucas and Eric,
I sent an upstream fix for this to the PR above. Their CI didn't even spot that
error yet (argh big testing gaps).
This has been open for a month now. As this threatens to make
Control: reassign -1 upower 1.90.2-7
Control: tag -1 fixed-upstream pending
The upower test adjustment landed upstream, I'll cherry-pick it into Debian.
Martin
Control: reassign -1 upower 1.90.2-7
Control: tag -1 fixed-upstream pending
The upower test adjustment landed upstream, I'll cherry-pick it into Debian.
Martin
Control: tag -1 upstream
Control: forwarded -1
https://gitlab.freedesktop.org/upower/upower/-/merge_requests/207
Hello Luca,
Luca Boccassi [2023-12-26 12:46 +0100]:
> Not sure whether it was a legitimate change and upower's tests need an
> update, or if it is a new bug, but 0.30.1-1 causes src:u
Control: tag -1 upstream
Control: forwarded -1
https://gitlab.freedesktop.org/upower/upower/-/merge_requests/207
Hello Luca,
Luca Boccassi [2023-12-26 12:46 +0100]:
> Not sure whether it was a legitimate change and upower's tests need an
> update, or if it is a new bug, but 0.30.1-1 causes src:u
Martin Pitt [2023-12-25 11:25 +0100]:
> The new upstream release plus regression fix have propagated to testing, to
> Ubuntu devel, and also is progressing well into Fedora. By now the tests have
> validated it enough for me to be confident in the fixes.
>
> I prepared the secu
Hello Sean and security team,
Sean Whitton [2023-12-24 9:12 +]:
> I have taken responsibility for fixing these CVEs in libssh in buster,
> as part of Freexian-funded LTS work. I would like to see if I can help
> get them fixed in bullseye & bookworm in parallel, to avoid a situation
> where
Hello Salvatore and all,
Salvatore Bonaccorso [2023-12-22 20:34 +0100]:
> On Fri, Dec 22, 2023 at 04:39:46PM +0100, Martin Pitt wrote:
> > Salvatore Bonaccorso [2023-12-22 13:20 +0100]:
> > > > However, the fix for CVE-2023-6004 caused a regression:
> > > > https:
Hello Salvatore,
Salvatore Bonaccorso [2023-12-22 13:20 +0100]:
> > However, the fix for CVE-2023-6004 caused a regression:
> > https://gitlab.com/libssh/libssh-mirror/-/issues/227
> > I will monitor this, and include the fix in the security upload once it is
> > available (or presumably they'll d
Hello Salvatore,
Salvatore Bonaccorso [2023-12-19 22:34 +0100]:
> The following vulnerability was published for libssh.
>
> CVE-2023-6004[0]:
> | ProxyCommand/ProxyJump features allow injection of malicious code
> | through hostname
I uploaded the new upstream security fix release 0.10.6 to unsta
Fun, this isn't even reliable. The first atttempt failed:
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-
logs/ubuntu-stable-20231219-223939.log
I retried the build now, no package or environment changes. Only daytime
and timing (race conditions). Perhaps some interaction with
Argh -- I missed the alternative truth in that rescue-ssh.target shell
code. So this message should pretty much *always* appear -- it's
nonsense to actually try and restart rescue-ssh.target in the postinst,
*always*.
But it is a red herring due to the || true. The upgrade failed on
something else
Public bug reported:
In our project we regularly build Ubuntu VM images for current 23.10
(stable). In https://github.com/cockpit-project/bots/issues/5691 we ran
into an upgrade failure of openssh-server. It starts with the current
cloud image and then apt upgrades it, with
"DEBIAN_FRONTEND=nonint
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-reconfigure openssh-server doesn't ask questions again
Status in openssh package in Ubuntu:
New
Bug d
We just ran into this in https://github.com/cockpit-
project/bots/issues/5691 when trying to refresh our Ubuntu 23.10 mantic
VM image. It starts with the current cloud image and then apt upgrades
it, with "DEBIAN_FRONTEND=noninteractive". openssh was updated a few
days ago indeed:
Setting up ope
Excellent, thanks Danilo for the super fast fix! ⭐
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong def
Excellent, thanks Danilo for the super fast fix! ⭐
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask
Control: tag -1 pending
Hello IOhannes,
IOhannes m zmoelnig [2023-12-13 8:57 +0100]:
> However, since 'scour' is not marked "Multi-Arch: foreign" (or "Multi-Arch:
> allowed") which makes it somewhat awkward to use when cross-building packages
> (that depend on 'scour').
>
> I would therefore lik
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
- ren
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
- ren
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
Hello Neftali,
Stef Walter [2023-12-11 10:01 +0100]:
> -- Forwarded message -
> Hello, I would like to participate in the cockpit development groups,
> first of all collaborating with the Spanish translations,
That would be great, ¡gracias! 😀
Cockpit is translated on weblate:
htt
I also tried
aa-disable usr.bin.crun
but that doesn't work either. I guess it's not really crun, but
profile="containers-default-0.50.1", but that is created dynamically --
it's not anywhere in /etc/apparmor.d/. I grepped the whole file system
for that:
grep: /usr/lib/podman/rootlessport: bi
I tried a more targeted workaround, with
aa-complain /etc/apparmor.d/usr.bin.crun
or alternatively (without apparmor-utils, which isn't on the default
cloud image):
sed -i '/flags=/ s/unconfined/complain/' /etc/apparmor.d/usr.bin.crun
but for some reason that breaks podman entirely:
# podm
Exact same fix uploaded to -proposed SRU review queue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2040488
Title:
loading lvm2 module crashes: udisks_module_lvm2_new: assertion
'
** Description changed:
[Impact]
Trying to load the lvm2 module crashes udisks immediately:
busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager
org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true
udisksd[5709]: cannot register existing type 'UDisksDaemo
add165ccc46008a17163f8
+
ProblemType: Crash
Architecture: amd64
Date: Wed Oct 25 12:13:14 2023
DistroRelease: Ubuntu 23.10
ExecutablePath: /usr/libexec/udisks2/udisksd
Package: udisks2 2.10.1-1ubuntu1
** Changed in: udisks2 (Ubuntu Mantic)
Status: New => In Progr
** Changed in: udisks2 (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: udisks2 (Ubuntu)
Status: New => Fix Committed
** Changed in: udisks2 (Ubuntu)
Importance: Undecided => High
** Changed in: udisks2 (Ubuntu Mantic)
Importance: Undecide
It's not related to the configure arguments, but to the linker flags.
The Ubuntu package build sets
LDFLAGS="-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects
-Wl,-z,relro -Wl,-z,now"
while Debian uses
LDFLAGS="-Wl,-z,relro -Wl,-z,now"
lto seems to work, but dropping the "-Wl,-Bsymbolic
Interesting! when I check out the source package, and build with the
above patch and like this:
./configure CFLAGS="-g -O0" --disable-gtk-docs --enable-lvm2
make -j4
sudo src/udisksd -rd --force-load-modules
then it loads the module just fine:
(udisksd:17050): udisks-WARNING **: 14:52:41.1
Comparing with Debian testing: Running
# /usr/libexec/udisks2/udisksd --debug --force-load-modules
udisks-Message: 10:34:44.696: udisks daemon version 2.10.1 starting
udisks-Message: 10:34:44.724: Acquired the name org.freedesktop.UDisks2 on the
system message bus
udisks-Message: 10:34:44.729: Lo
It's a bit easier to investigate with
/usr/libexec/udisks2/udisksd --debug --force-load-modules
There I've1 also seen it fail on the btrfs module, so it's not specific
to the LVM one.
It also happens with rebuilding the udisks source package (so not just
changed ABI)
I tried building upstre
Confirmed on current noble, same udisks2 version.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2040488
Title:
loading lvm2 module crashes: udisks_module_lvm2_new: assertion
'UDISK
Control: tag -1 pending
Hello,
Bug #1057148 in python-dbusmock reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/packages/python-dbusmock/-/commit/122
- Podman: Delete intermediate images
You can get Cockpit here:
http://cockpit-project.org/running.html
The new releases are available in Fedora 38 and 39.
Take care,
Martin Pitt
--
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
Public bug reported:
I tried to do this with `apport-cli
/var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending doesn't
do anything obvious. I run this from a cloud image over ssh, I really
don't have any GUI. So filing this manually.
Trying to load the lvm2 module crashes udisks immedia
Wim Bertels [2023-10-23 16:06 +]:
> if the manpages are generated correctly:
> https://manpages.debian.org/unstable/cockpit-ws/remotectl.8.en.html
> remotectl is present in unstable and testing as well?
No, it's not any more in testing and unstable:
https://packages.debian.org/trixie/amd64/co
Wim Bertels [2023-10-23 16:06 +]:
> if the manpages are generated correctly:
> https://manpages.debian.org/unstable/cockpit-ws/remotectl.8.en.html
> remotectl is present in unstable and testing as well?
No, it's not any more in testing and unstable:
https://packages.debian.org/trixie/amd64/co
Control: tag -1 wontfix
Hello Wim,
wim [2023-10-23 17:16 +0200]:
> it seems the remotectl command is missing (from bookworm and
> bookworm-backports)?
> (as it was included in bullseye, and is included in testing)
This is intended, see https://cockpit-project.org/blog/cockpit-252.html
Out of i
Control: tag -1 wontfix
Hello Wim,
wim [2023-10-23 17:16 +0200]:
> it seems the remotectl command is missing (from bookworm and
> bookworm-backports)?
> (as it was included in bullseye, and is included in testing)
This is intended, see https://cockpit-project.org/blog/cockpit-252.html
Out of i
can get Cockpit here:
http://cockpit-project.org/running.html
The new releases are available in Fedora 38 and 39.
Take care,
Martin Pitt
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpit
Hello Dan,
Dan Streetman [2023-10-05 13:09 -0400]:
> I just reviewed and approved the cockpit-* uploads to jammy-backports,
> looked fine and no concerns there, thanks!
Thanks!
> For the uploads to lunar-backports, we had decided on a policy of not
> accepting backports into non-LTS releases, un
Similar issue: https://gitlab.com/libvirt/libvirt/-/issues/548 . These
two may want a common fix with "allow qemu to read sysfs"?
** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #548
https://gitlab.com/libvirt/libvirt/-/issues/548
--
You received this bug notification because you are
Hello Dan and Boyuan,
Boyuan Yang [2023-10-01 18:49 -0400]:
> 在 2023-09-28星期四的 20:43 +0100，d...@daft.dog写道：
> > Hey,
> >
> > I hope this is the right place to ask.
> >
> > I noticed pmie_daily.service keeps failing to start on my bookworm box
> > running the cockpit back port with pcp running. A
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19407
Control: tag -1 upstream pending
Hello Helmut,
Helmut Grohne [2023-09-27 13:46 +0200]:
> We want to change the value of systemdsystemunitdir in systemd.pc to
> point below /usr. cockpit's upstream build system consumes th
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19407
Control: tag -1 upstream pending
Hello Helmut,
Helmut Grohne [2023-09-27 13:46 +0200]:
> We want to change the value of systemdsystemunitdir in systemd.pc to
> point below /usr. cockpit's upstream build system consumes th
Hello Dan,
sorry for the *really* late reply! I didn't get your original emails. In the
last years, my @ubuntu.com address became a 100% spam (thousands every month)
vs. 0% signal thing. Thanks to Sèbastien for the ping!
Dan Streetman [2023-03-26 13:53 -0400]:
> It seems you have been uploading t
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19232
Lucas Nussbaum [2023-08-13 16:33 +0200]:
> This package fails to build a source package after a successful build
> (dpkg-buildpackage ; dpkg-buildpackage -S).
> > dpkg-source: error: cannot
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19232
Lucas Nussbaum [2023-08-13 16:33 +0200]:
> This package fails to build a source package after a successful build
> (dpkg-buildpackage ; dpkg-buildpackage -S).
> > dpkg-source: error: cannot
Control: tag -1 upstream pending
Control: forwarded -1
https://github.com/cockpit-project/cockpit-podman/pull/1377
Lucas Nussbaum [2023-08-13 15:17 +0200]:
> > dpkg-source: info: building cockpit-podman using existing
> > ./cockpit-podman_74.orig.tar.xz
> > dpkg-source: info: local changes detec
Control: tag -1 upstream pending
Control: forwarded -1
https://github.com/cockpit-project/cockpit-machines/pull/1183
Lucas Nussbaum [2023-08-13 15:17 +0200]:
> > dpkg-source: info: building cockpit-machines using existing
> > ./cockpit-machines_296.orig.tar.xz
> > dpkg-source: info: local change
Control: tag -1 upstream pending
Control: forwarded -1
https://github.com/cockpit-project/cockpit-machines/pull/1183
Lucas Nussbaum [2023-08-13 15:17 +0200]:
> > dpkg-source: info: building cockpit-machines using existing
> > ./cockpit-machines_296.orig.tar.xz
> > dpkg-source: info: local change
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19188
Hello Helmut,
Helmut Grohne [2023-08-08 12:38 +0200]:
> cockpit-tests has a non-trivial aspect when it comes to finalizing the
> /usr-merge. As we move all files from / to /usr, we'll likely also move
> /lib/systemd/syste
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19188
Hello Helmut,
Helmut Grohne [2023-08-08 12:38 +0200]:
> cockpit-tests has a non-trivial aspect when it comes to finalizing the
> /usr-merge. As we move all files from / to /usr, we'll likely also move
> /lib/systemd/syste
Package: cloud.debian.org
Until https://cloud.debian.org/images/cloud/bookworm/daily/20230724-1451/ we
still had debian-12-{azure,ec2,generic,...}. But in
https://cloud.debian.org/images/cloud/bookworm/daily/20230725-1452/ and also
https://cloud.debian.org/images/cloud/bookworm/daily/20230726-1453
Package: cloud.debian.org
Until https://cloud.debian.org/images/cloud/bookworm/daily/20230724-1451/ we
still had debian-12-{azure,ec2,generic,...}. But in
https://cloud.debian.org/images/cloud/bookworm/daily/20230725-1452/ and also
https://cloud.debian.org/images/cloud/bookworm/daily/20230726-1453
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19092
Control: tag -1 pending
Hello Michael,
Michael Biebl [2023-07-10 22:37 +0200]:
> the latest update of libblockdev from version 2.28 to 3.0 has seen some
> major changes, among them an SONAME bump.
>
> Please test cockpit(
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19092
Control: tag -1 pending
Hello Michael,
Michael Biebl [2023-07-10 22:37 +0200]:
> the latest update of libblockdev from version 2.28 to 3.0 has seen some
> major changes, among them an SONAME bump.
>
> Please test cockpit(
One workaround that I found is to delete the [ntp] section from
/var/lib/ipa-client/sysrestore/sysrestore.state after joining.
sed -i '/\[ntp\]/,/^$/ d' /var/lib/ipa-client/sysrestore/sysrestore.state
Hello all,
Thorsten Glaser [2023-06-20 19:39 +]:
> Ideally, let debootstrap use its default if no pbuilderrc.
Yes, agreed.
Thanks,
Martin
Package: pbuilder
Version: 0.231
I am trying to create a pbuilder on today's amd64 cloud image.
`pbuilder --create --debug` eventually fails with
| + debootstrap --include=apt --cache-dir=/var/cache/pbuilder/aptcache/
--variant=buildd --force-check-gpg bookworm /var/cache/pbuilder/build/26079
Hello all,
I am testing the current debian-12-genericcloud-amd64-daily-20230619-1416.qcow2
image from https://cloud.debian.org/images/cloud/bookworm/daily/. This has
| # getent group netdev
| netdev:x:1002:debian
which is broken -- as soon as you try to install a package like wpasupplicant
or Ne
propriate at this point of the release cycle any more.
+
+ -- Martin Pitt Wed, 17 May 2023 19:56:56 +
+
libssh (0.10.5-1) unstable; urgency=high
[ Martin Pitt ]
diff -Nru libssh-0.10.5/debian/control libssh-0.10.5/debian/control
--- libssh-0.10.5/debian/control2023-05-10 06:00
propriate at this point of the release cycle any more.
+
+ -- Martin Pitt Wed, 17 May 2023 19:56:56 +
+
libssh (0.10.5-1) unstable; urgency=high
[ Martin Pitt ]
diff -Nru libssh-0.10.5/debian/control libssh-0.10.5/debian/control
--- libssh-0.10.5/debian/control2023-05-10 06:00
Cockpit here:
http://cockpit-project.org/running.html
The new releases are available in Fedora 37 and 38.
Or download the tarballs here:
https://github.com/cockpit-project/cockpit/releases/tag/
Take care,
Martin Pitt
___
cockpit-devel mailing list
Package: packagekit
Severity: important
Version: 1.2.6-4
With the latest update to Debian testing, existing installations lost the
`pkcon` program. We explicitly install `packagekit` into our VMs, and so far
this has always provided pkcon.
The recent release dropped the recommendation from the li
ibssh-0.10.4/debian/changelog 2022-09-19 08:41:22.0 +
+++ libssh-0.10.5/debian/changelog 2023-05-10 06:00:26.0 +
@@ -1,3 +1,26 @@
+libssh (0.10.5-1) unstable; urgency=high
+
+ [ Martin Pitt ]
+ * New upstream security release (thus high urgency):
+- Fix authe
ibssh-0.10.4/debian/changelog 2022-09-19 08:41:22.0 +
+++ libssh-0.10.5/debian/changelog 2023-05-10 06:00:26.0 +
@@ -1,3 +1,26 @@
+libssh (0.10.5-1) unstable; urgency=high
+
+ [ Martin Pitt ]
+ * New upstream security release (thus high urgency):
+- Fix authe
https://github.com/martinpitt/umockdev/issues/208
Thanks Heinrich!
** Bug watch added: github.com/martinpitt/umockdev/issues #208
https://github.com/martinpitt/umockdev/issues/208
** Changed in: umockdev (Ubuntu)
Status: New => In Progress
--
You received this bug notification becaus
Hello security team,
Martin Pitt [2023-05-10 8:19 +0200]:
> I'll attempt to backport the fixes for stable now.
> https://git.libssh.org/projects/libssh.git/log/?h=stable-0.9 has quite some
> changes before and beyond the actual security fix: some memory leak fixes,
> moving
Control: tag -1 pending
Hello Salvatore,
Salvatore Bonaccorso [2023-05-09 22:30 +0200]:
> The following vulnerabilities were published for libssh.
>
> CVE-2023-1667[0]:
> | Potential NULL dereference during rekeying with algorithm guessing
>
> CVE-2023-2283[1]:
> | Authorization bypass in pki_ver
Hello again,
I just locally reverted [1], and it's still the same, so that Debian patch
actually isn't to blame.
I also tried --prefix=/opt which then gets me /opt/local/{bin,lib}. So this
behaviour directly contradicts the --help documentation:
> --prefix Installation prefix wher
Hello all,
Is that patch even necessary still? In Fedora with python3-pip 2.22.3,
`sudo pip install python-dbusmock` installs into
/usr/local/lib/python3.11/site-packages/dbusmock/ , i.e. does not conflict
with /usr any more. They do have a more targetted protection of /usr [1], but
no general pat
Package: python3-pip
Version: 23.0.1+dfsg-1
My upstream project (cockpit) is soon going to deliver a new Python component,
where it installs a locally built wheel (i.e. some Python packages and
auto-generated executable wrappers) with
python3 -m pip install --no-index --force-reinstall --root
are
available in Fedora 37 and 38.
Highlights:
- webserver: Disallow direct URL logins with LoginTo=false
- Machines: Indicate need for shutdown
- Machines: Delete storage file when detaching disk
Take care,
Martin Pitt
___
cockpit-devel mailing list
Package: curl
Version: 7.88.1-7
Severity: important
Tags: upstream fixed-upstream
Upstream version 7.88 broke the `--unix` option. When doing something like
curl -k --unix /run/cockpit/sock https://dummy
it now fails with
curl: (7) Failed to connect to dummy port 443 after 0 ms: Couldn'
Control: reassign -1 sssd-common 2.8.2-3
Control: affects -1 podman
Control: retitle -1 sssd-common" subids nsswitch.conf entry breaks user
sub[ug]ids
Control: severity -1 serious
Matej Marusak [2023-04-03 14:00 +]:
> This is easily reproducible by:
> - Download newest image, e.g.
> https://
Control: reassign -1 sssd-common 2.8.2-3
Control: affects -1 podman
Control: retitle -1 sssd-common" subids nsswitch.conf entry breaks user
sub[ug]ids
Control: severity -1 serious
Matej Marusak [2023-04-03 14:00 +]:
> This is easily reproducible by:
> - Download newest image, e.g.
> https://
Control: retitle -1 podman: user containers are completely broken with sssd:
insufficient UIDs or GIDs available in user namespace
Matej Marusak [2023-04-03 14:00 +]:
> The original reproducer was not clear how important this failure is. It
> efectively means that rootless podman is unusable
Control: retitle -1 podman: user containers are completely broken with sssd:
insufficient UIDs or GIDs available in user namespace
Matej Marusak [2023-04-03 14:00 +]:
> The original reproducer was not clear how important this failure is. It
> efectively means that rootless podman is unusable
Hello Tadeusz,
Tadeusz Kasprzycki [2023-03-27 13:23 -]:
> My file log updates contains /var/log/apt/history.log. There are 17
> transakctions. In the cockpit, I see only 3 and the older ones are removed
> from the list
Unfortunately PackageKit and direct apt updates are tracked separately.
:
http://cockpit-project.org/running.html
The new releases are available in Fedora 37 and 38, see the links in the blog
post.
Take care,
Martin Pitt
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to
Hello Santiago,
Santiago Vila [2023-02-18 0:26 +0100]:
> Martin Pitt wrote:
> > The "flock: not found" is #1014662, but that is already present in our
> > current
> > image with cloud-initramfs-tools 0.18.debian8, and does not seem fatal. So
> > far
> &
Hello Santiago,
Santiago Vila [2023-02-18 0:26 +0100]:
> Martin Pitt wrote:
> > The "flock: not found" is #1014662, but that is already present in our
> > current
> > image with cloud-initramfs-tools 0.18.debian8, and does not seem fatal. So
> > far
> &
Hello Santiago,
Santiago Vila [2023-02-18 0:26 +0100]:
> Martin Pitt wrote:
> > The "flock: not found" is #1014662, but that is already present in our
> > current
> > image with cloud-initramfs-tools 0.18.debian8, and does not seem fatal. So
> > far
> &
image’s default command
You can get Cockpit here:
http://cockpit-project.org/running.html
Take care,
Martin Pitt
signature.asc
Description: PGP signature
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email
Hello Mark,
Mark Reynolds [2023-01-18 16:31 -0500]:
> So we've been using "superuser=true" for a long time now, and we have a
> customer issue where system users who have sudo rights don't seem to have
> privileges in Cockpit. Looking at the docs it does not mention "true"
> anymore, but "require
Package: cloud-initramfs-growroot
Version: 0.18.debian11
Severity: important
In our CI we recently tried to refresh our Debian testing image [1], which
exposed a regression: Trying to resize the image with
qemu-resize 20G
leads to a boot failure:
Begin: Running /scripts/init-premount .
Package: cloud-initramfs-growroot
Version: 0.18.debian11
Severity: important
In our CI we recently tried to refresh our Debian testing image [1], which
exposed a regression: Trying to resize the image with
qemu-resize 20G
leads to a boot failure:
Begin: Running /scripts/init-premount .
For the record, there's a very high chance that I am to blame for that
"runlevel" check. Back then that was simply the lowest common
denominator between sysvinit, upstart, and systemd. These days I agree
that `systemctl is-system-running` would be more appropriate.
--
You received this bug notifi
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/18000
Hey Simon,
Simon McVittie [2022-12-06 13:20 +]:
> This package has a Recommends on the transitional package policykit-1,
> which has been separated into polkitd, pkexec and (deprecated
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/18000
Hey Simon,
Simon McVittie [2022-12-06 13:20 +]:
> This package has a Recommends on the transitional package policykit-1,
> which has been separated into polkitd, pkexec and (deprecated
101 - 200 of 59181 matches
Mail list logo
