Ack, thanks Thomas! Well, hopefully the devel-permissions@ PPU thread
concludes soon, then I don't need to bother you any more.
** Summary changed:
- Please backport cockpit 333 into oracular/noble/jammy
+ [BPO] Please backport cockpit 333 into oracular/noble/jammy
--
You received this bug noti
Ack, thanks Thomas! Well, hopefully the devel-permissions@ PPU thread
concludes soon, then I don't need to bother you any more.
** Summary changed:
- Please backport cockpit 333 into oracular/noble/jammy
+ [BPO] Please backport cockpit 333 into oracular/noble/jammy
--
You received this bug noti
I ran the test case on both 24.04 and 24.10 with the respective
released/proposed versions. I confirm that the AA violation is gone with
the update. I also ran the originally triggering cockpit test
TestHistoryMetrics.testEvents and confirm that with the proposed version
the denial is gone there as
I ran the test case on both 24.04 and 24.10 with the respective
released/proposed versions. I confirm that the AA violation is gone with
the update. I also ran the originally triggering cockpit test
TestHistoryMetrics.testEvents and confirm that with the proposed version
the denial is gone there as
I can still reproduce the AppArmor violation with both the reproducer
here as well as with cockpit's TestJournal.testLogLevel test that
originally caused me to report this. I updated to -3ubuntu9.1 from
noble-proposed, and I confirm that everything works as advertised -- no
more AA violations, and
I can still reproduce the AppArmor violation with both the reproducer
here as well as with cockpit's TestJournal.testLogLevel test that
originally caused me to report this. I updated to -3ubuntu9.1 from
noble-proposed, and I confirm that everything works as advertised -- no
more AA violations, and
Thanks Thomas! Right, I'm aware of the 2023 changes, and there has
indeed been some hubbub (like me continuing to self-approve while I
shouldn't have any more). But as far as I understood, I followed the
process since then -- uploading the backports and letting the backports
team approve them from
Thanks Thomas! Right, I'm aware of the 2023 changes, and there has
indeed been some hubbub (like me continuing to self-approve while I
shouldn't have any more). But as far as I understood, I followed the
process since then -- uploading the backports and letting the backports
team approve them from
Re-subscribing ~ubuntu-sponsors, which was somehow unsubscribed. This
should hopefully make it appear on http://sponsoring-reports.ubuntu.com/
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099668
T
Re-subscribing ~ubuntu-sponsors, which was somehow unsubscribed. This
should hopefully make it appear on http://sponsoring-reports.ubuntu.com/
.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/
Hello Jonathan,
Jonathan Aquilina via cockpit-devel [2025-03-12 4:46 +]:
> I will head over to the matrix channel, but in a quick question is there an
> official docker container available for cockpit? I am asking as that would be
> an ideal dev environment to work with.
Yes! Well, toolbox
Hello Jonathan,
Jonathan Aquilina [2025-03-11 14:04 +]:
> On my local machine I would still prefer to run a proper certificate and even
> on my home network I have looked into this.
>
> The issue is automated renewal and auto deployment to the infrastructure
> devices from cert bot.
>
> What
Hello Jonathan,
Jonathan Aquilina via cockpit-devel [2025-03-11 12:53 +]:
> Currently what web server does cockpit use or is it dependent on the server
> admin what cockpit uses?
cockpit-ws is an independent implementation of a web server. We can't just use
a standard one like nginx, as it d
Hello Jonathan,
changed the Subject to make it clearer that this is a different topic.
Jonathan Aquilina via cockpit-devel [2025-03-11 13:46 +]:
> Probably a stupid question here but what advantage does having its own custom
> created web server offer over something like nginx with reverse p
Attention: Please don't respond to this mail, but to the GitHub discussion
mentioned below.
Hello all,
the Cockpit team is currently investigating a redesign of Cockpit's web server,
which becomes slowly but surely more pressing. See [1] for details if you are
interested. A very interesting possi
Package: semodule-utils
Version: 3.8-1
Severity: serious
Hello,
The most recent semodule-utils update rendered the current
selinux-policy-default 2:2.20250115-1 uninstallable.
With the previous semodule-utils 3.7-1,
apt install --reinstall selinux-policy-default
works fine. But after updatin
Package: semodule-utils
Version: 3.8-1
Severity: serious
Hello,
The most recent semodule-utils update rendered the current
selinux-policy-default 2:2.20250115-1 uninstallable.
With the previous semodule-utils 3.7-1,
apt install --reinstall selinux-policy-default
works fine. But after updatin
Package: semodule-utils
Version: 3.8-1
Severity: serious
Hello,
The most recent semodule-utils update rendered the current
selinux-policy-default 2:2.20250115-1 uninstallable.
With the previous semodule-utils 3.7-1,
apt install --reinstall selinux-policy-default
works fine. But after updatin
** Patch added: "oracular debdiff"
https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+attachment/5859385/+files/cockpit_oracular.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
Hello Andreas, long time no see! Thanks for replying. I need to figure
out a new workflow for this, so thanks for the guidance.
> - BPO bug template[1]
See https://bugs.launchpad.net/xenial-backports/+bug/1686022
This has been good enough for many years, and the approval shouldn't
evaporate just
Hello Andreas, long time no see! Thanks for replying. I need to figure
out a new workflow for this, so thanks for the guidance.
> - BPO bug template[1]
See https://bugs.launchpad.net/xenial-backports/+bug/1686022
This has been good enough for many years, and the approval shouldn't
evaporate just
** Patch added: "jammy debdiff"
https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+attachment/5859383/+files/cockpit_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099668
** Patch added: "noble debdiff"
https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2099668/+attachment/5859384/+files/cockpit_noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099668
Public bug reported:
Cockpit has a standing backport approval since
https://bugs.launchpad.net/xenial-backports/+bug/1686022 . For the last
couple of years I have uploaded them myself, as I had been an Ubuntu
core developer from ~ 2004 until a few months ago. I voluntarily left
archive admin and c
Hello Mohammed,
Mohammed Sadiq [2025-02-14 15:39 +0530]:
> May I know the status of this ITP. I wish to have cockpit-files
> pacakged. If you don't have enough time to look into this, I would
> like to give this a try.
It has been packaged for a long time, and has been sitting in the NEW queu
Hello Mohammed,
Mohammed Sadiq [2025-02-14 15:39 +0530]:
> May I know the status of this ITP. I wish to have cockpit-files
> pacakged. If you don't have enough time to look into this, I would
> like to give this a try.
It has been packaged for a long time, and has been sitting in the NEW queu
Package: mdadm
Severity: important
Version: 4.3+20241202-1
The update from 20241108 to 20241202 caused a regression [1] with bitmaps. The
manpage still says
> When creating an array on devices which are 100G or larger, mdadm
> automatically adds an internal bitmap as it will usually be benefic
Yes, of course. Heck, this is over 10 years old. Any bug which is still
left by now probably counts as "API" now 😅
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Yes, of course. Heck, this is over 10 years old. Any bug which is still
left by now probably counts as "API" now 😅
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2
Yes, of course. Heck, this is over 10 years old. Any bug which is still
left by now probably counts as "API" now 😅
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/21397
Hello Helmut,
thanks for pointing out! I already dropped the cockpit-tests package completely
in upstream main (not released yet), but the file conflict was missing indeed.
Fixing in above
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/21397
Hello Helmut,
thanks for pointing out! I already dropped the cockpit-tests package completely
in upstream main (not released yet), but the file conflict was missing indeed.
Fixing in above
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/21397
Hello Helmut,
thanks for pointing out! I already dropped the cockpit-tests package completely
in upstream main (not released yet), but the file conflict was missing indeed.
Fixing in above
Thanks! I pulled that version into our image in
https://github.com/cockpit-project/bots/pull/7176 and it all works
again. So removing my regression-proposed flag. However, I didn't
actually validate the bug fix, so not moving to v-done.
** Tags removed: regression-proposed
--
You received this b
Thanks! I pulled that version into our image in
https://github.com/cockpit-project/bots/pull/7176 and it all works
again. So removing my regression-proposed flag. However, I didn't
actually validate the bug fix, so not moving to v-done.
** Tags removed: regression-proposed
--
You received this b
Thanks! I pulled that version into our image in
https://github.com/cockpit-project/bots/pull/7176 and it all works
again. So removing my regression-proposed flag. However, I didn't
actually validate the bug fix, so not moving to v-done.
** Tags removed: regression-proposed
--
You received this b
Thanks Nathan and Sebastien for the fast fix! However, it failed to
build on most arches:
https://launchpad.net/ubuntu/+source/policykit-1/124-2ubuntu1.24.10.2
(without a log..). So the above autopkgtest message is rather
misleading.
--
You received this bug notification because you are a member
Thanks Nathan and Sebastien for the fast fix! However, it failed to
build on most arches:
https://launchpad.net/ubuntu/+source/policykit-1/124-2ubuntu1.24.10.2
(without a log..). So the above autopkgtest message is rather
misleading.
--
You received this bug notification because you are a member
Thanks Nathan and Sebastien for the fast fix! However, it failed to
build on most arches:
https://launchpad.net/ubuntu/+source/policykit-1/124-2ubuntu1.24.10.2
(without a log..). So the above autopkgtest message is rather
misleading.
--
You received this bug notification because you are a member
This update breaks firewalld:
# firewall-cmd --list-services
ERROR:dbus.proxies:Introspect error on :1.12:/org/fedoraproject/FirewallD1:
dbus.exceptions.DBusException: org.freedesktop.PolicyKit1.Error.Failed: Action
org.fedoraproject.FirewallD1.info is not registered
Error: Action org.fedoraproj
This update breaks firewalld:
# firewall-cmd --list-services
ERROR:dbus.proxies:Introspect error on :1.12:/org/fedoraproject/FirewallD1:
dbus.exceptions.DBusException: org.freedesktop.PolicyKit1.Error.Failed: Action
org.fedoraproject.FirewallD1.info is not registered
Error: Action org.fedoraproj
This update breaks firewalld:
# firewall-cmd --list-services
ERROR:dbus.proxies:Introspect error on :1.12:/org/fedoraproject/FirewallD1:
dbus.exceptions.DBusException: org.freedesktop.PolicyKit1.Error.Failed: Action
org.fedoraproject.FirewallD1.info is not registered
Error: Action org.fedoraproj
Control: tag -1 fixed-upstream
The fix for this landed upstream now:
https://gitlab.com/qemu-project/qemu/-/commit/fbdea3d6c13d5a75895c287a004c6f1a6bf6c164
signature.asc
Description: PGP signature
Control: reassign -1 qemu 1:9.1.1+ds-4
Control: tag -1 upstream
Control: forwarded -1
https://www.mail-archive.com/qemu-devel@nongnu.org/msg1077089.html
Control: affects -1 libssh 0.11.1-1
Martin Pitt [2024-11-12 7:19 +0100]:
> Hello Sven,
>
> Sven Geuer [2024-11-11 18:54 +0100]:
>
Hello Sven,
Sven Geuer [2024-11-11 18:54 +0100]:
> Meanwhile I reviewed parts of the Qemu sources and came to the
> conclusion that Qemu calls libssh only as intended by libssh upstream,
> I could not detect any direct access to the changed structs. So,
> rebuilding Qemu might not be enough.
>
> M
Control: tag -1 upstream
Control: forwarded -1 https://gitlab.com/libssh/libssh-mirror/-/issues/280
Hello Sven,
Sven Geuer [2024-10-21 12:13 +0200]:
> To reproduce the issue on a amd64 machine
> * make sure you have sshd running
> * make sure sure can ssh to localhost
> * make sure you have ssh-a
Control: block -1 by 1080270
Hello Bastian,
Bastian Germann [2024-06-26 22:05 +0200]:
> Please drop the libssh-gcrypt-dev and libssh-gcrypt-4 packages as soon as no
> reverse dep is left.
> Upstream has deprecated the gcrypt flavor with v0.11 and only a few packages
> still depend on it.
> They
Package: libavformat60
Version: 7:6.1.1-5+b1
Hello Debian Multimedia Maintainers,
Bastian asked [1] for libssh to drop the gcrypt variant (libssh-gcrypt-4). It's
deprecated in libssh upstream, and with the recently changed OpenSSL license
there is no reason any more to have it.
The only remainin
Package: libavformat60
Version: 7:6.1.1-5+b1
Hello Debian Multimedia Maintainers,
Bastian asked [1] for libssh to drop the gcrypt variant (libssh-gcrypt-4). It's
deprecated in libssh upstream, and with the recently changed OpenSSL license
there is no reason any more to have it.
The only remainin
This was fixed upstream in https://github.com/cockpit-project/cockpit-
machines/commit/bc7d9a2d53297264a6d8f889ef238d08027aa6ef and is part of
cockpit-machines 315. Thus it is fixed in oneiric. For 24.04 you can get
version 316-1~bpo24.04.1 from official noble-backports.
** Changed in: cockpit-mac
These methods were introduced in
https://pagure.io/freeipa/c/0f9a8b7a15b911f443042061d795fcaa51f1a3c7 ,
and that triggers a strong déjà vu for me -- I've looked at this failure
in a different context already.
But https://launchpad.net/ubuntu/+source/python-cryptography in oracular
*is* version 42.
These methods were introduced in
https://pagure.io/freeipa/c/0f9a8b7a15b911f443042061d795fcaa51f1a3c7 ,
and that triggers a strong déjà vu for me -- I've looked at this failure
in a different context already.
But https://launchpad.net/ubuntu/+source/python-cryptography in oracular
*is* version 42.
Public bug reported:
I am currently enabling our Cockpit tests on oracular [1] (now after
feature freeze and well before release is a good time). The main
regression is with joining a FreeIPA domain.
The server runs a standard quay.io/freeipa/freeipa-
server:centos-9-stream container with a coupl
Public bug reported:
I am currently enabling our Cockpit tests on oracular [1] (now after
feature freeze and well before release is a good time). The main
regression is with joining a FreeIPA domain.
The server runs a standard quay.io/freeipa/freeipa-
server:centos-9-stream container with a coupl
Control: tag -1 pending
Hello Simon,
Simon McVittie [2024-08-22 9:17 +0100]:
> The pristine-tar branch is missing data for recent upstream releases.
Whoops, thanks for pointing out!
> Please consider using `gbp push` to push changes to all relevant branches.
That's not it -- my local pristine
Hello all,
three months ago, Firefox announced [1] that they are dropping support for the
Chrome Devtools Protocol, the browser automation protocol that we have used in
Cockpit's test API for many years. This finally happened in Firefox 129 [2],
which just recently made it into Fedora 40.
The new
Control: tag -1 upstream
Control: forwarded -1 https://gitlab.com/libvirt/libvirt/-/issues/660
Martin Pitt [2024-08-13 5:59 +0200]:
> However, the image log has the list of updated packages (at the bottom of
> [3]),
> and the most plausible one is
>
> libvirt-daemon (10.5.
Control: tag -1 confirmed
Laurent Bigonville [2024-07-24 15:39 +0200]:
> type=AVC msg=audit(1721828131.241:1176): apparmor="DENIED" operation="open"
> class="file" profile="libvirt-6fde45f5-ff7e-4277-87b9-123a8aa30c7e"
> name="/proc/sys/vm/max_map_count" pid=149623 comm="qemu-system-x86"
> requ
Control: tag -1 upstream fixed-upstream pending
Hello Petter,
Petter Reinholdtsen [2024-08-02 7:40 +0200]:
> The Appstream validation report the following problem with the metadata
> I submitted in BTS #1076991.
>
> Errors
>
> * gui-app-without-icon
[...]
I did that when I committed that up
OK, thanks for confirming!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
nsswitch.con
OK, thanks for confirming!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
nsswitch.conf "passwd" entry misses "sys
Control: tag -1 upstream fixed-upstream pending
Hello Petter,
Petter Reinholdtsen [2024-07-25 6:48 +0200]:
> +Description: Added AppStream metainfo XML with hardware provide info.
> + This allow isenkram to propose this package when the hardware is
> + present.
Thank you! However, despite this
Control: tag -1 upstream fixed-upstream pending
Hello Petter,
Petter Reinholdtsen [2024-07-25 6:14 +0200]:
> Where looking at the source of media-player-info, I came across some
> DeviceMatch entries in media-players/*.mpi which appear to be typos.
> Most entries have a usb: prefix, but a select
Hmm.. Installing libnss-systemd is supposed to add that line
automatically. Do you remember, did you happen to change nsswitch.cnf
manually somehow? backup/restore, Ansible, etc?
** Summary changed:
- cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but systemd
units still use cock
So can you please check `sudo journalctl -u cockpit-ws-user` ? That
should have the root cause of the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
cockpit-ws 321-1~bpo22.04.1
And can you pelase check that you have `libnss-systemd` installed (it's
a dependency of cockpit-ws) and that /etc/nsswitch.conf "passwd" line
includes "systemd"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
That's not an "old" username. cockpit-ws really needs two. "cockpit-ws"
uses DynamicUser=yes, while cockpit-wsinstance is a static user name
(for technical reasons). Is anything not working?
** Changed in: cockpit (Ubuntu)
Status: New => Incomplete
--
You received this bug notification be
That's because the two ARM architectures still didn't pick up the build:
https://launchpad.net/ubuntu/+source/cockpit/321-1~bpo24.04.1
This must be a bug in the buildd configuration --
https://launchpad.net/ubuntu/noble/arm64/+builds is empty, and even
https://launchpad.net/ubuntu/oracular/arm64/+
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org,
pkg-utopia-maintain...@lists.alioth.debian.org
Owner: Martin Pitt
X-Debbugs-Cc: Utopia Maintenance Team
Severity: wishlist
* Package name: cockpit-files
Version : 2
Upstream Contact: Martin Pitt
* URL
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org,
pkg-utopia-maintain...@lists.alioth.debian.org
Owner: Martin Pitt
X-Debbugs-Cc: Utopia Maintenance Team
Severity: wishlist
* Package name: cockpit-files
Version : 2
Upstream Contact: Martin Pitt
* URL
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org,
pkg-utopia-maintain...@lists.alioth.debian.org
Owner: Martin Pitt
X-Debbugs-Cc: Utopia Maintenance Team
Severity: wishlist
* Package name: cockpit-files
Version : 2
Upstream Contact: Martin Pitt
* URL
-2024-6126]
+
+ -- Martin Pitt Fri, 05 Jul 2024 06:15:50 +0200
+
cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
* Add 0001-ssh-Use-valid-host-name-in-test-sshbridge.patch:
diff -Nru
cockpit-287.1/debian/patches/0002-pam-ssh-add-Fix-insecure-killing-of-session-ssh-agen.patch
co
-2024-6126]
+
+ -- Martin Pitt Fri, 05 Jul 2024 06:15:50 +0200
+
cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
* Add 0001-ssh-Use-valid-host-name-in-test-sshbridge.patch:
diff -Nru
cockpit-287.1/debian/patches/0002-pam-ssh-add-Fix-insecure-killing-of-session-ssh-agen.patch
co
Package: lxc
Version: 1:5.0.2-1+deb12u2
I recently changed cockpit-ws' systemd unit from a static `adduser` to
`DynamicUser=yes`. This works great by and large (on Debian 12 and testing and
also all currently supported Ubuntu releases). But there's a failure when
running the autopkgtest in debci [
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/20543
Control: tag -1 patch pending
Hello Michael,
Michael Biebl [2024-06-03 14:39 +0200]:
> Jun 03 14:35:42 mars apparmor.systemd[1026]: AppArmor-Analysefehler f?r
> /etc/apparmor.d in profile /etc/apparmor.d/cockpit-desktop
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/20543
Control: tag -1 patch pending
Hello Michael,
Michael Biebl [2024-06-03 14:39 +0200]:
> Jun 03 14:35:42 mars apparmor.systemd[1026]: AppArmor-Analysefehler f?r
> /etc/apparmor.d in profile /etc/apparmor.d/cockpit-desktop
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/20543
Control: tag -1 patch pending
Hello Michael,
Michael Biebl [2024-06-03 14:39 +0200]:
> Jun 03 14:35:42 mars apparmor.systemd[1026]: AppArmor-Analysefehler f?r
> /etc/apparmor.d in profile /etc/apparmor.d/cockpit-desktop
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-failed verification-failed-noble
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Bug watch added: Debian Bug tracker #1053706
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053706
** Also affects: procps (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053706
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
Hello Cockpiteers,
Is anyone using https://github.com/cockpit-project/cockpit-certificates and
interesting in taking over its development and maintenance? From the cockpit
team's PoV it is rather abandoned, nobody uses it or is interested in it, and
we have too much to do and need to shed some loa
Hello all,
Is anyone using https://github.com/cockpit-project/cockpit-certificates and
interested in taking over development/maintenance?
This never made it into any distribution or even an official upstream release,
we have too much to do in Red Hat's Cockpit team, and we need to shed some
load.
Package: python3-ipaclient
Severity: important
Version: 4.11.1-2
Tags: upstream, fixed-upstream
Forwarded:
https://lists.fedorahosted.org/archives/list/freeipa-us...@lists.fedorahosted.org/thread/PLR7R2FIZXNOQFMT3XWMBK3UYI7FWVMY/
Hello,
A few days ago, python-cryptography 42.0 entered Debian tes
Thanks @ffesti ! So I suppose this should be closed upstream, and I'll create a
bugzilla instead?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3073#issuecomment-2092433241
You are receiving this because you are subscribed to this thr
This helped a lot, but it's still applying the user creation and `%attr()`
processing in the wrong order. I filed issue #3073 about it.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2432#issuecomment-2092096531
You are receiving this be
We are currently [trying to move our project to
systemd-sysusers](https://github.com/cockpit-project/cockpit/pull/20365), away
from manual `useradd` calls in the package's `%pre` script. The [rpm
manual](https://rpm-software-management.github.io/rpm/manual/users_and_groups.html)
claims
> Rpm
This was "fixed" in noble by clearing out noble-proposed, thanks! That
took care of the worst fallout.
** Changed in: python-gssapi (Ubuntu Noble)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
The recent no-change rebuild in
https://launchpad.net/ubuntu/+source/python-gssapi/1.8.2-1ubuntu2
regressed. With -1ubuntu1, the import works:
python3 -c 'import gssapi'
but with -1ubuntu2, it crashes with
Traceback (most recent call last):
File "", line 1, in
File "
There are no patches, it's a straight import of the source package into
Ubuntu. Ubuntu *does* have different compiler options than Debian, so
that may be a factor. Otherwise I'm in the same boat as you -- there's
only so much time I can throw at this (I've done full-time "investigate,
report, and t
ian/changelog
--- cockpit-287.1/debian/changelog 2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog 2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+ * Add 0001-ssh-Use-valid-host-name-in-test-ssh
ian/changelog
--- cockpit-287.1/debian/changelog 2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog 2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+ * Add 0001-ssh-Use-valid-host-name-in-test-ssh
ian/changelog
--- cockpit-287.1/debian/changelog 2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog 2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+ * Add 0001-ssh-Use-valid-host-name-in-test-ssh
Public bug reported:
One of our Cockpit integration tests [1] spotted an AppArmor regression
in rsyslogd. This is coincidental, the test passes and it doesn't do
anything with rsyslogd -- just something happens to happen in the
background to trigger this (and I can actually reproduce it locally
qu
Public bug reported:
One of our Cockpit integration tests [1] spotted an AppArmor regression
in rsyslogd. This is coincidental, the test passes and it doesn't do
anything with rsyslogd -- just something happens to happen in the
background to trigger this (and I can actually reproduce it locally
qu
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of FreeIPA,
which is subscrib
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/s
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/s
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/s
Confirmed in current noble.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1946244
Title:
When installing/uninstalling with realmd, uninstalling crashes with
ScriptError
Status in freeipa p
1 - 100 of 6202 matches
Mail list logo
