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
log 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-sshbridge.patch:
+Use valid host name in tes
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/216
Control: tag -1 upstream pending
Hello all,
Thorsten Glaser [2024-03-20 3:05 +]:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed
> only with _FILE_OFFSET_BITS=64"
>26 | # error
Control: severity 1061370 grave
Control: forcemerge -1 1061370
Matthias Klose [2024-02-01 8:30 +0100]:
> please don't file duplicate reports, see #1061370
Ah, sorry -- it wasn't clear from the title that it was about this problem, nor
was it RC. Marking a duplicate, so that it's easier to find.
Package: libatomic1
Version: 14-20240127-1
Severity: grave
Justification: breaks a lot of unrelated packages
Hello,
yesterday's cockpit armel build failed [1] on armel like this in the
./configure test for the PCP library:
| configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2
Control: tag -1 pending
Hallo Matthias,
Matthias Klose [2024-01-29 21:27 +0100]:
> 636s NO TESTS RAN (skipped=4)
> 637s autopkgtest [01:57:06]: test upstream: ---]
> 637s autopkgtest [01:57:06]: test upstream: - - - - - - - - - - results - -
> - - - - - - - -
> 637s upstream
I can't make head or tail of this. aa-complain still enforces deny
rules, there is no (discoverable) way to log deny rules, and
grep -r deny /etc/apparmor.d | grep virt | grep -v /sys | grep -v /dev
doesn't show anything which would apply to /var/lib/libvirt/.
`aa-disable
Control: retitle -1 libvirt-daemon: Deleting external snapshot for non-running
system VM fails with AppArmor
when stracing libvirt, this is what happens:
6557 openat(AT_FDCWD, "/var/lib/libvirt/images/test2.qcow2", O_RDWR|O_CLOEXEC)
= -1 EACCES (Permission denied)
6557 sendmsg(13,
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
: #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
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
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
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
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
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
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:
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
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
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:
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
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
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
>
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
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
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
appropriate 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:26.0
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
/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 authenticated remote DoS through
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 some
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
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
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
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
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:
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.
>
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 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
>
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
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
Hello Vagrant,
CC'ing the upstream maintainers, in case I speak nonsense here.
Vagrant Cascadian [2022-12-04 16:45 -0800]:
> In libssh 0.10.x versions, DSA support is deprecated and disabled by
> default.
This was indeed intended [1].
> This causes test suite failures when building guile-ssh
Control: tag -1 fixed-upstream pending
Hello again,
Martin Pitt [2022-10-26 6:04 +0200]:
> Argh, this keeps haunting us. We already tried to fix that in [1] and [2], but
> no way. Why must glib be so unpredictable?
> [2] https://github.com/cockpit-project/cockpit/pull/17755
Never
Hello Michael, hello Lis,
Michael Biebl [2022-10-26 1:41 +0200]:
> cockpit seems to fail its test suite on the aforementioned architectures
Thanks for the report!
> on armel:
> ~
> Bail out! GLib-FATAL-WARNING: GChildWatchSource: Exit status of a child
> process was requested but
Hello Bastian,
Bastian Germann [2022-09-06 14:21 +0200]:
> Please update libssh to the latest 0.10.x version.
> This has many added features including official OpenSSL 3 support.
Indeed, it's been on my radar for a while. I held it back as there was quite a
serious regression with handling old
Martin Pitt [2022-07-26 11:58 +0200]:
> A fresh installation of rpcbind fails to start the service:
This can also be seen on package installation [1]:
Setting up rpcbind (1.2.6-5) ...
/usr/lib/tmpfiles.d/rpcbind.conf:2: Failed to resolve user '_rpc': No such
process
Martin
[1] ht
Package: rpcbind
Version: 1.2.6-4
Severity: serious
A fresh installation of rpcbind fails to start the service:
systemd[1]: Starting RPC bind portmap service...
rpcbind[314]: cannot get uid of '_rpc': Success
systemd[1]: rpcbind.service: Main process exited, code=exited,
Control: tag -1 upstream fixed-upstream pending
Control: forwarded -1 https://github.com/martinpitt/python-dbusmock/pull/138
Hello Mike,
Mike Gabriel [2022-07-18 20:59 +]:
> Ratchanan from the UBports dev team has very recently fixed all unit tests
> in (lomiri-)indicator-network against
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/martinpitt/python-dbusmock/pull/139
Ça va Lucas,
Lucas Nussbaum [2022-07-16 15:32 +0200]:
> > ==
> > FAIL: test_options
Control: forwarded -1 https://github.com/sgallagher/sscg/pull/60
Control: tag -1 upstream pending
Hello Bo,
Bo YU [2022-07-03 10:33 +0800]:
> The sscg package has a ftbfs issue on riscv64 arch, the full buildd
> log is here:
>
>
Hello Simon,
Simon McVittie [2022-05-18 11:13 +0100]:
> autopkgtest has a significant amount of code to deal with Ubuntu 'click'
> packages, mostly contributed by Martin Pitt (who I'm aware no longer
> works for Canonical, but I'm cc'ing him for context).
>
> However, click s
Control: reassign -1 openssl 3.0.2-1
Control: affects -1 sscg 3.0.2-1
Control: tag -1 fixed-upstream
Kurt Roeckx [2022-05-15 23:05 +0200]:
> It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247
Indeed, thank you! Updating bug status.
I see openssl 3.0.3-4 is supposed to
Control: tag -1 upstream confirmed
Control: retitle -1 sscg FTBFS with OpenSSL 3.0.3
Adrian Bunk [2022-05-14 9:48 +0300]:
> https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1
>
> ...
> 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11
> SIGSEGV
> 04:32:21
Package: freeipa-client
Version: 4.9.8-1+b1
Installing the IPA client is broken due to some chrony FUBAR [1], but I worked
around that with a mock service:
| # cat /run/systemd/system/chrony.service
| [Service]
| Type=oneshot
| ExecStart=/bin/true
| # systemctl unmask chrony
After that, joining
Package: freeipa-client
Version: 4.9.8-1+b1
Despite several attempts to fix it [1][2], interaction with chrony is still
broken on current Debian testing.
freeipa-client Recommends: chrony, so it is installed by default. Trying to
join a domain on a clean system:
| # ipa-client-install --domain
Package: bind9-dnsutils
Version: 1:9.18.0-2
Querying DNS for a particular record type should look roughly like this:
| # nslookup -type=SRV localhost
| Server: 172.27.0.3
| Address: 172.27.0.3#53
|
| *** Can't find localhost: No answer
That's the case with
Control: reassign -1 libvirt 7.0.0-3
Control: forcemerge 1006324 -1
Hello Simon,
Simon Kobyda [2022-03-18 14:48 +0100]:
> ERRORinternal error: process exited while connecting to monitor:
> 2022-03-18T13:45:43.472848Z qemu-system-x86_64: -blockdev
>
Control: tag -1 upstream fixed-upstream
Control: forwarded -1 https://github.com/sgallagher/sscg/pull/51
Hello Sebastian,
Sebastian Andrzej Siewior [2022-02-27 23:36 +0100]:
> Your package is failing to build using OpenSSL 3.0 with the
> following error:
Thanks for the report! This got fixed
Control: tag -1 upstream
Control: forwarded -1 https://gitlab.com/libvirt/libvirt/-/merge_requests/140
I forwarded the tested fix to an upstream PR.
Martin
Control: reassign -1 libvirt-daemon-system 8.0.0-1
Control: found -1 7.0.0-3
Sorry for the merry-go-round -- the AppArmor profiles are actually shipped by
libvirt-daemon-system (libvirt source package).
Control: reassign -1 apparmor 3.0.4-2
Control: found -1 apparmor 2.13.6-10
Thanks for the report!
I cleaned up the reproducer a bit: Drop the line breaks, automate the
firmware='efi' bit, and create the missing novell.iso; it just needs to exist,
it does not have to have any actual content for
Package: pcp
Version: 5.2.6-1
Severity: important
Tags: upstream fixed-upstream
Hello,
Debian stable's pcp version has a rather annoying bug: after a while,
pmlogger.service fails to start up:
systemd[1]: pmlogger.service: Failed with result 'protocol'.
systemd[1]: Failed to start
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/16928
I sent an upstream PR to add the missing node_modules/ copyrights. If there is
anything else wrong, I'll need more information (see my previous reply).
Thanks!
Martin
tag -1 moreinfo
Hallo Thorsten,
Thorsten Alteholz [2022-02-05 9:40 +]:
> please rework your debian/copyright. Especially everything from node_modules
> seems to be missing. Please also check other releases.
The webpack bits in dist/ are autogenerated, and we have spent quite some
effort to
Control: tag -1 pending
Hello Simon,
Simon McVittie [2022-01-08 19:02 +]:
> librsvg 2.52.x has deprecated Rsvg.Handle.render_cairo, which causes
> scour's autopkgtest to fail
Thanks for the excellent report! Fixed in
Control: tag -1 pending
Hello Helmut,
Helmut Grohne [2021-12-25 9:31 +0100]:
> + * Reduce Build-Depends for architecture bootstrap. (Closes: #-1)
Thank you, much appreciated! I pushed the changes [1], as two separate
commits. I'll still do some maintenance updates (lintian looks pretty sad),
Control: retitle -1 pam_sss messes up existing /var/log/sssd/p11_child.log
permissions
Control: reassign -1 libpam-sss 2.6.1-1
Control: severity -1 important
Turns out this is both much simpler to reproduce and also much more severe --
one doesn't actually need all the certificate setup and
Package: sssd-dbus
Version: 2.6.1-1
I am testing the new FindByValidCertificate() infopipe API from 2.6.1, to
provide safe certificate authentication for cockpit. During that I ran into a
curious bug, where triggering p11-kit validation in sssd messes up the
permissions of
Control: tag -1 pending
Control: tag 991324 pending
Control: tag 991884 pending
Hello Martin-Éric,
> +micro-httpd (20140814-2.1) unstable; urgency=medium
Thanks! Reading https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983232#15
scared me a bit (users shouldn't use edit --full normally, and
Package: libvirt-daemon
Version: 7.6.0-1
Since the upgrade of Debian 11 to current testing, libvirt has a regression: It
does not recognize veth devices as "nodedevs" (devices available on the host
and known by libvirt) any more. This breaks assigning them to VMs for
networking or PXE booting.
Control: tag -1 pending
Hello José,
José Miguel Gonçalves [2021-10-04 10:29 +0100]:
> I would like to try cockpit-machines v251 in bullseye but that is currently
> not possible because, while cockpit v251 package is released in
> bullseye-backports, cockpit-machines is not.
> Please build
Control: severity -1 normal
Control: tag -1 unreproducible moreinfo
Hello Friedemann,
Friedemann Schorer [2021-10-03 23:40 +0200]:
> Severity: serious
That feels inflated to me. The package builds fine in official buildds [1], in
upstream CI (which uses pbuilder) and locally in a debian-sid
Control: reassign -1 bolt 0.9.1-1
Control: affects -1 umockdev
Control: tag -1 upstream pending
Control: forwarded -1
https://gitlab.freedesktop.org/bolt/bolt/-/merge_requests/246
Hello Christian,
as I mentioned on the LP bug already, I noticed that bolt regression and sent
an upstream fix for
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 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
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
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
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: cockpit-machines
Version : 241
Upstream Author : Cockpit development team
* URL : https://github.com/cockpit-project/cockpit-machines/
* License : LGPL-2.1+
Description
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: 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
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: 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.
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: 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.
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
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: 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,
1 - 100 of 3108 matches
Mail list logo
