Control: severity -1 important
Seems to pass pretty reliably on debci, thus downgrading to important.
https://ci.debian.net/packages/u/upower/
Regards,
Michael
On Wed, 24 Apr 2024 23:34:48 +0500 Andrey Rakhmatullin
wrote:
Package: upower
Version: 1.90.3-1
Severity: serious
Control:
Am 29.04.24 um 14:03 schrieb Michael Biebl:
It appears that this is a regression introduced in util-linux 2.40-7.
The udisks2 test suite passes with 2.40-6.
So I assume it's one of the upstream changes from
"""
* Import upstream stable/v2.40 up to
a8aa0b5f154a44557f5bae5a4
Am 28.04.24 um 18:20 schrieb Chris Hofstaedtler:
Source: udisks2
Version: 2.10.1-6
Severity: serious
Hi,
udisks2's autopkgtest fails when tried together with util-linux 2.40. An
example can be seen here:
https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/
537s
Control: tag -1 pending
Hello,
Bug #1068936 in libcanberra 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:
Please see the related MR
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/75
By dropping the hand-written maintscript code, we should mitigate this
problem, as the problematic code would not be run on upgrades.
In addition, the generated maintscript code used "|| true", so
Am 15.03.24 um 19:55 schrieb Michael Biebl:
Control: tags -1 - patch
On Wed, 13 Mar 2024 13:01:49 + Mark Hindley
wrote:
Control: tags -1 patch
I also bumped into this whilst rebuilding src:policykit-1 yesterday.
There is an upstream patch[1], but it doesn't fix the build for me; I
Control: tags -1 - patch
On Wed, 13 Mar 2024 13:01:49 + Mark Hindley wrote:
Control: tags -1 patch
I also bumped into this whilst rebuilding src:policykit-1 yesterday.
There is an upstream patch[1], but it doesn't fix the build for me; I think it
is patching the wrong files.The problem
Package: qemu-system-data
Version: 1:8.2.1+ds-2
Severity: serious
During the lastest upgrade, I get
Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive
Control: severity -1 important
Hi
On Wed, 28 Feb 2024 18:49:00 +0100 Michael Biebl wrote:
Source: lvm2
Version: 2.03.22-1
Severity: serious
Hi,
filing this issue with severity RC to prevent testing migration.
It appears the new LVM release breaks both systemd and multipath-tools's
Source: lvm2
Version: 2.03.22-1
Severity: serious
Hi,
filing this issue with severity RC to prevent testing migration.
It appears the new LVM release breaks both systemd and multipath-tools's
autopkgtest suite
https://ci.debian.net/packages/m/multipath-tools/testing/amd64/43382441/
Am 05.02.24 um 11:29 schrieb Michael Biebl:
Am 04.02.24 um 19:31 schrieb Steve Langasek:
Source: volume-key
Version: 0.3.12-5
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes
Am 02.02.24 um 08:45 schrieb Steve Langasek:
Hi Michael,
On Thu, Feb 01, 2024 at 06:34:13PM +0100, Michael Biebl wrote:
Am 01.02.24 um 18:00 schrieb Steve Langasek:
Source: libnma
Version: 1.10.6-2
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian
Am 04.02.24 um 19:31 schrieb Steve Langasek:
Source: volume-key
Version: 0.3.12-5
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear
Am 01.02.24 um 18:00 schrieb Steve Langasek:
Source: libnma
Version: 1.10.6-2
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
Control: tag -1 pending
Hello,
Bug #1054783 in libpwquality 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:
Control: tag -1 pending
Hello,
Bug #1057220 in systemd 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:
Am 21.12.23 um 11:50 schrieb Christoph Berg:
Re: Helmut Grohne
Is it ok to call upgrade scenarios failures that cannot be reproduced
using apt unsupported until we no longer deal with aliasing?
If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug)
with no action calling the
Am 09.12.23 um 00:53 schrieb JP Pozzi:
Hello,
Here the result :
grep users /etc/group /etc/gshadow
/etc/group:users:x:100:
/etc/gshadow:users:*::suricata
You appear to have a mismatch between /etc/group and /etc/gshadow.
Either your user "suricata" is listed in both or none.
Not sure how
Am 08.12.23 um 18:48 schrieb Michael Biebl:
On Fri, 08 Dec 2023 17:30:23 +0100 JPP wrote:
Package: systemd
Version: 252.19-1~deb12u1
Severity: serious
Tags: d-i
Justification: normal
Dear Maintainer,
I get a problem upgrading the system, systemd fails to configure :
sudo dpkg --configure
On Fri, 08 Dec 2023 17:30:23 +0100 JPP wrote:
Package: systemd
Version: 252.19-1~deb12u1
Severity: serious
Tags: d-i
Justification: normal
Dear Maintainer,
I get a problem upgrading the system, systemd fails to configure :
sudo dpkg --configure systemd
Setting up systemd (252.19-1~deb12u1)
Package: ubuntu-keyring
Version: 2023.11.28.1-0.1
Severity: serious
Preparing to unpack .../ubuntu-keyring_2023.11.28.1-0.1_all.deb ...
Unpacking ubuntu-keyring (2023.11.28.1-0.1) over (2020.06.17.1-1) ...
dpkg: error processing archive
Control: severity -1 normal
Control: block -1 1055067
Am 20.11.23 um 13:25 schrieb Vincent Lefevre:
On 2023-11-20 12:42:14 +0100, Vincent Lefevre wrote:
I suspect that nm-dhcp-helper has been added because it is now needed.
But it doesn't work due to the "Permission denied".
If I understand
Control: tag -1 pending
Hello,
Bug #1056108 in systemd 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:
Hi Thomas
Am 17.11.23 um 10:12 schrieb Thomas Lange:
I've already included the upstream patch to the git master branch of
dracut on salsa. The next dracut release in Debian will include the
fix.
Great, thanks. I assume this version will be 059-5 ?
OpenPGP_signature.asc
Description:
I've filed a corresponding bug report against systemd, so users are
notified of this issue and the package doesn't migrate to testing
prematurely:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056108
We will add a versioned Breaks against dracut to systemd to ensure that
dracut users
Package: systemd
Version: 255~rc2-1
Severity: serious
The addition of systemd-executor breaks dracut in a bad way.
It generates an unbootable initrd.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056059
Filing with RC severity to notify users and to prevent testing
migration.
We
Am 27.10.23 um 13:45 schrieb Vincent Lefevre:
Package: dbus
Version: 1.14.10-2
Severity: critical
Justification: breaks the whole system
dbus 1.14.10-2 makes the machine extremely slow (this affects the
boot, login, the su command, and package installation at least),
and it freezes on shutdown.
Control: tag -1 pending
Hello,
Bug #1053898 in rsyslog 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:
Source: rsyslog
Version: 8.2310.0-1
Severity: serious
X-Debbugs-Cc: Richard Lewis
The latest update of rsyslog enabled various systemd hardening and
security features, specifically:
CapabilityBoundingSet=CAP_BLOCK_SUSPEND CAP_CHOWN CAP_LEASE CAP_NET_ADMIN
CAP_NET_BIND_SERVICE CAP_SYS_RESOURCE
Control: severity -1 important
Am 01.09.23 um 00:37 schrieb Michael Biebl:
On Thu, 24 Aug 2023 17:18:35 +0200 Paul Gevers wrote:
Source: upower 1.90.2-4
Severity: serious
Tags: sid trixie
X-Debbugs-CC: b...@debian.org
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1
Control: severity -1 important
Am 09.09.23 um 14:20 schrieb intrigeri:
Hi again,
Thank you all for working both on workarounds for Debian CI and on
a proper upstream Linux kernel fix. Impressive cross-team work! :)
+1
At this stage it seems clear that the bug and the corresponding ideal
Am 04.09.23 um 20:23 schrieb Mathias Gibbens:
On Mon, 2023-09-04 at 01:00 -0700, John Johansen wrote:
I took a quick look through v6.1..v6.3.1
there is a patch that I think is the likely fix, it first landed in v6.2
1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets
Am 03.09.23 um 10:50 schrieb Paul Gevers:
Hi,
On 03-09-2023 02:56, Michael Biebl wrote:
ng?
Do the debci maintainers / lxc maintainers / release team have any
preference regarding a/, b/ and c/ ?
One part of me likes the ci.d.n infrastructure to run stable as an
example of "eat you
On Thu, 24 Aug 2023 17:18:35 +0200 Paul Gevers wrote:
Source: upower 1.90.2-4
Severity: serious
Tags: sid trixie
X-Debbugs-CC: b...@debian.org
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1 src:libgudev
Dear maintainer(s),
With a recent upload of upower, the
Control: tags -1 + patch
Please find attached a patch which should be sufficient to address this
issue. I can offer to NMU, in case you are busy.
Regards,
Michael
diff --git a/debian/scripts/suspend/cryptsetup-suspend-wrapper b/debian/scripts/suspend/cryptsetup-suspend-wrapper
index
Package: cryptsetup-suspend
Version: 2:2.6.1-4
Severity: serious
The cryptsetup-suspend wrapper makes unconditional use of the
/lib/systemd/system-sleep directory.
This directory was removed from the systemd package as a result of the
discussion in
Am 17.07.23 um 13:07 schrieb Michael Biebl:
So, instead of changing the dependency from libblockdev-crypto2 to
libblockdev-crypto3, you might consider dropping the dependency
altogether, as clevis-udisks2 already depends on udisks2 and
clevis-crypto2 doesn't actually use libblockdev-crypto
On Thu, 13 Jul 2023 07:59:45 +0200 Christoph Biedl
wrote:
Control: Tags 1040924 +pending
Jeremy Bícha wrote...
> Yes, it's a transition. Sorry that it didn't follow the recommended procedure.
Thanks for the clarification. New version is underway, I'd like to do
some thourough testing,
Package: picom
Version: 10.2-1
Severity: serious
picom adds an autostart file which makes it automatically start on
session login.
Today I noticed that journald/rsyslog ran while and my logs were flodded
with the following messages (I was logged into a GNOME session at that
time):
Jul 13
Package: libnvme-dev
Version: 1.4-3
Severity: serious
The libnvme.pc declares the following dependencies:
Requires.private: json-c >= 0.13, openssl >= 1.1.0, libkeyutils
Those need to be added to the Depends of libnvme-dev, otherwise
pkgconfig will fail to e.g. resolve cflags.
# pkgconf
Control: tag -1 pending
Hello,
Bug #1038762 in systemd 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:
Am 21.06.23 um 03:02 schrieb Michael Biebl:
Am 21.06.23 um 02:34 schrieb Lyndon Brown:
The latest package update (to unstable) has broken login keyboard-
layout support. I'm marking this as critical due to the chaotic
potential for locking many users out of their accounts / systems, some
Am 21.06.23 um 02:34 schrieb Lyndon Brown:
The latest package update (to unstable) has broken login keyboard-
layout support. I'm marking this as critical due to the chaotic
potential for locking many users out of their accounts / systems, some
of whom unlike myself may have no clue what's wrong
[trimmed the list of CCs]
Am 30.05.23 um 13:36 schrieb Jochen Sprickerhof:
# find / -name e2scrub_reap.service
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/e2scrub_reap.service
/var/lib/systemd/deb-systemd-helper-enabled/default.target.wants/e2scrub_reap.service
The title of this bug report is highly misleading.
Let's see what's actually happening here:
bullseye chroot:
# find /etc/systemd/system/ -name e2scrub_reap.service
/etc/systemd/system/default.target.wants/e2scrub_reap.service
bookworm chroot:
# find /etc/systemd/system/ -name
Control: reassign -1 e2fsprogs
Am 14.05.23 um 11:30 schrieb Andreas Beckmann:
On 09/05/2023 17.48, Michael Biebl wrote:
Andreas, you filed this with RC severity with the justification that
systemd units are not enabled. I don't see that, so could you please
clarify.
What I could find out so
On Fri, 5 May 2023 13:38:52 +0200 Michael Biebl wrote:
Am 05.05.23 um 11:14 schrieb Luca Boccassi:
> On Fri, 05 May 2023 11:04:29 +0200 Andreas Beckmann
>> This is a new systemd unit in package e2fsprogs.
It's not, both bullseye and bookworm ship this file in e2fsprogs. The
d
Am 05.05.23 um 11:14 schrieb Luca Boccassi:
On Fri, 05 May 2023 11:04:29 +0200 Andreas Beckmann
This is a new systemd unit in package e2fsprogs.
It's not, both bullseye and bookworm ship this file in e2fsprogs. The
difference is this
bullseye:
cat
Control: severity -1 wishlist
Control: retitle -1 document log rotation on non-default inits
Am 16.02.23 um 15:41 schrieb Matthew Vernon:
Package: rsyslog
Version: 8.2212.0-1
Severity: serious
Hi,
When removing the systemv init scripts from rsyslog (which can be
managed by
Hi Otto
Am 05.02.23 um 17:55 schrieb Otto Kekäläinen:
This is now solved on
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31
Mangling the maintainers scripts of another package is a delicate issue
as it's often fragile and can cause hard to debug failures in corner
Am 30.01.23 um 07:59 schrieb Otto Kekäläinen:
The only problem there is that on purge deb-systemd-helper and
update-rc.d will disable the service, but that is not based on package
ownership.
The maintainer scripts will act on files which effectively no longer
belong to this package. That's
Am 29.01.2023 um 04:12 schrieb Otto Kekäläinen:
Hi!
I managed now to reproduce this. The purge step is not relevant, but
simply the upgrade itself.
...
-> upgrade successful, but service stopped working - the service file
has no executable bit anymore.
That's only half of the bug report.
Am 21.01.23 um 21:28 schrieb Otto Kekäläinen:
Hi!
I have been frantically trying to reproduce the issue you reported.
It's trivial to reproduce:
Have the versioned mariadb packages installed (say from unstable), then
make an apt full-upgrade, which will install the new unversioned ones
and
Konfigurationsdateien von mariadb-server-10.6 (1:10.6.11-2) ...
Löschen der Konfigurationsdateien von mariadb-client-10.6 (1:10.6.11-2) ...
[master 28eeae9] committing changes in /etc made by "aptitude"
Author: Michael Biebl
12 files changed, 80 deletions(-)
delete mode 10064
Control: reassign -1 kexec-tools
Am 10.01.23 um 20:34 schrieb KOLANICH:
Package: systemd
Version: 252.4-1
Severity: grave
So do kexec-tools if a user has chosen to use it for
reboots during package configuration.
Either of the following can cause fs corruption (to the point one has to
use
Source: cmucl
Version: 21d-1.1
Severity: serious
Tags: ftbfs
Trying to build cmucl (on i386) fails with the following error:
FORTIFY_SOURCE=2 -c -o interrupt.o ../../src/lisp/interrupt.c
../../src/lisp/interrupt.c:408:6: error: variable length array declaration not
allowed at file scope
char
Control: severity -1 wishlist
Control: tags -1 + wontfix
Hello
Am 28.12.22 um 19:55 schrieb Michael Tokarev:
Package: systemd
Version: 252.2-2~bpo11+1
Severity: serious
I just come across a situation where my notebook does not let me in while
I'm in a place where network is not available.
Control: tag -1 pending
Hello,
Bug #1025908 in systemd 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:
Control: tags -1 + moreinfo unreproducible
Control: severity -1 normal
Am 23.11.22 um 13:18 schrieb Andreas Metzler:
Source: volume-key
Version: 0.3.12-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hello,
volume-key FTBFS on
Control: severity -1 normal
Control: notforwarded -1
Am 16.11.22 um 22:54 schrieb Daniel Serpell:
Package: network-manager-openvpn
Version: 1.10.2-1
Severity: normal
Dear maintainer,
After upgrading to 1.10.2-1, I can't connect to the VPN anymore.
This is the logs from NetworkManager:
Control: tags -1 + moreinfo
Am 30.10.22 um 13:34 schrieb Salvo "LtWorf" Tomaselli:
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up systemd (252~rc3-2) ...
systemd-machine-id-setup: error while loading shared libraries:
libsystemd-shared-251.so: cannot open shared object
Source: cockpit
Version: 276.1-1
Severity: serious
cockpit seems to fail its test suite on the aforementioned architectures
on armel:
~
(cockpit-bridge:13294): cockpit-bridge-WARNING **: 11:53:58.528: couldn't
create runtime dir: /run/user/2952: Permission denied
cockpit-bridge-Message:
On Mon, 17 Oct 2022 22:13:47 +0300 Michael Tokarev wrote:
16.10.2022 08:04, Adrian Bunk wrote:
...
> With 0.10.3-1 vulkan is a new requirement, breaking the qemu build again:
>
https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A7.1%2Bdfsg-2%2Bb1=1665894634=0
>
> The complete list
Am 17.10.22 um 15:33 schrieb Nilesh Patra:
affects 1021895 src:ionit
close 1021923
stop
Hi Michael,
On Mon, 17 Oct 2022 13:56:40 +0200 Michael Biebl wrote:
Source: ionit
Version: 0.5.0-1
Severity: serious
Tags: ftbfs
ionit FTBFS in unstable
test_pylint (tests.test_pylint.PylintTestCase
Source: prometheus-openstack-exporter
Version: 0.1.4-2
Severity: serious
Tags: ftbfs
prometheus-openstack-exporter FTBFS in unstable
dpkg-source --before-build .
fakeroot debian/rules clean
dh clean --with systemd,python3 --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I:
Source: networking-mlnx
Version: 1:16.0.0-3
Severity: serious
Tags: ftbfs
networking-mlnx FTBFS in unstable
It appears to be trigger lots of test suite failures and is killed
eventually
Traceback (most recent call last):
File "/<>/networking_mlnx/journal/journal.py", line 91, in
Source: ionit
Version: 0.5.0-1
Severity: serious
Tags: ftbfs
ionit FTBFS in unstable
test_pylint (tests.test_pylint.PylintTestCase)
Test: Run pylint on Python source code. ... Running following command:
/usr/bin/python3.10 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/ionit tests
Source: console-setup
Version: 1.210
Severity: serious
Tags: ftbfs
console-setup FTBFS in unstable
gzip -9n >/acm/VISCII.acm >/<>/acm/VISCII.acm.gz
umask 022; /<>/Fonts/bdf2psf --log
/<>/Fonts/Arabic-Fixed15.log
/<>/Fonts/bdf/9x15-IL2.bdf+/<>/Fonts/bdf/9x15.bdf+/<>/Fonts/bdf/9x15c.bdf
Source: buildbot
Version: 3.5.0-1
Severity: serious
Tags: ftbfs
buildbot FTBFS in unstable
[ERROR]
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1660,
in _inlineCallbacks
result = current_context.run(gen.send, result)
File
Source: salt
Version: 3004.1+dfsg-2
Severity: serious
Tags: ftbfs
salt FTBFS in unstable
make[2]: Entering directory '/<>/doc'
rm -rf _build/*
test -d 'locale' && find locale/ -name *.mo -exec rm {} \; || true
make[2]: Leaving directory '/<>/doc'
dh_auto_clean
I: pybuild base:240: python3.10
Control: severity -1 normal
Control: tags -1 unreproducible
Control: close -1
Am 12.10.22 um 21:38 schrieb Matteo Settenvini:
Okay, I retried and I cannot reproduce it now.
I think what happened is:
* my system was hanging at the beginning due to some unrelated problem
with video (mesa).
*
Am 12.10.22 um 20:18 schrieb Michael Biebl:
Please remove "debug" from the kernel command line and capture the log
messages
I meant to say "quiet".
You can also add "systemd.log_level=debug" to increase the verbosity.
See man kernel-command-line.
OpenPGP_
On Wed, 12 Oct 2022 19:39:40 +0200 Matteo Settenvini
wrote:
Package: udev
Version: 251.5-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
I have a root partition (separate from the boot partition) which is
encrypted with LUKS and unlocked at boot.
After an
/22, 12:44 AM, "Paul Gevers" wrote:
Hi Michael
On 29-08-2022 14:23, Michael Biebl wrote:
> As you are probably aware, this issue is known and tracked in [1].
Which I added as a blocker and mentioned in my message, so yes.
> The
> package FTBFS after enabling the test suite.
control: severity -1 normal
control: tags -1 + moreinfo unreproducible
control: retitle -1 apt incorrectly prefer usr-is-merged
Am 21.09.22 um 15:12 schrieb Craig Sanders:
reopen 1020290
severity 1020290 critical
stop
There's no need to repeat (again!) what i've already said.
Unfortunately
Control: severity -1 important
On Sat, 23 Jul 2022 18:04:43 +0200 Jan Kiszka
wrote:
Upstream patch proposal sent:
https://sourceforge.net/p/gnu-efi/mailman/message/37684742/
Thanks for that, Jan.
Seems your patch was rejected unfortunately.
I couldn't quite follow the reasoning of the
Package: libnma0
Version: 1.10.0-1
Severity: serious
Forwarded: https://gitlab.gnome.org/GNOME/libnma/-/issues/17
Filing as RC to prevent testing migration.
After upgrading libnma from 1.8.40 to 1.10.0, nm-connection-editor
shows the following broken behaviour when
trying to edit a connection: a
issue is related to the
synchronization between atop and atopacctd. I am looking into it further
and will keep this thread updated.
I am looking forward to have a fix for this for s390x.
-Dipak
On 30/08/22, 12:44 AM, "Paul Gevers" wrote:
Hi Michael
On 29-08-2022 14:23, Michael Biebl wrote:
&
Hi Paul
Am 27.08.22 um 13:49 schrieb Paul Gevers:
Source: exempi
Version: 2.6.1-2
Severity: serious
Control: close -1 2.6.2-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1014061
Dear maintainer(s),
The Release Team considers
Control: reopen -1
Control: severity -1 important
Control: clone -1 -2
Control: reassign -2 kodi
Control: retitle -2 please ship firewalld service files
Control: block -1 by -2
Am 24.07.22 um 08:12 schrieb Christian Marillat:
> But why firewalld install services for packages not installed ?
>
>
Control: tag -1 pending
Hello,
Bug #1014115 in systemd 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:
Am 04.07.22 um 13:13 schrieb Luca Boccassi:
On Mon, 4 Jul 2022 at 11:55, Michael Biebl wrote:
Am 04.07.22 um 12:36 schrieb Luca Boccassi:
I have uploaded i-s-h, should we close this one now?
I've seen the upload. Thanks!
I was debating with myself whether systemd-homed should get
Am 04.07.22 um 12:36 schrieb Luca Boccassi:
I have uploaded i-s-h, should we close this one now?
I've seen the upload. Thanks!
I was debating with myself whether systemd-homed should get a tightened,
versioned Depends on i-s-h to prevent this issue from happening.
This would make a
Am 02.07.22 um 18:30 schrieb Luca Boccassi:
On Fri, 1 Jul 2022 at 20:20, Michael Biebl wrote:
Am 30.06.22 um 22:31 schrieb Luca Boccassi:
The problem is some files leftover, no? Just delete them in the
postinst or postrm?
My main motivation is to "stop the bleeding" as quickly a
Am 30.06.22 um 22:31 schrieb Luca Boccassi:
The problem is some files leftover, no? Just delete them in the
postinst or postrm?
My main motivation is to "stop the bleeding" as quickly as possible.
If we continue to create those broken state files, we'd have to keep
those postinst/postrm
Am 30.06.22 um 18:18 schrieb Michael Biebl:
Am 30.06.22 um 17:31 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:44, Michael Biebl wrote:
Am 30.06.22 um 16:32 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote:
Am 30.06.22 um 16:13 schrieb Luca Boccassi:
On Thu
Am 30.06.22 um 16:32 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote:
- masking a service upon uninstallation
This is a sad reality, as packages still ship legacy SysV init scripts
which are conffiles and would suddenly become active if a package is
removed
Am 30.06.22 um 17:31 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:44, Michael Biebl wrote:
Am 30.06.22 um 16:32 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote:
Am 30.06.22 um 16:13 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote
Am 30.06.22 um 16:32 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote:
Am 30.06.22 um 16:13 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote:
Am 30.06.22 um 14:26 schrieb Michael Biebl:
This might be a bug in i-s-h, but filing against
Am 30.06.22 um 16:13 schrieb Luca Boccassi:
On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote:
Am 30.06.22 um 14:26 schrieb Michael Biebl:
This might be a bug in i-s-h, but filing against systemd-homed for
now.
systemd-homed.service:
[Install]
WantedBy=multi-user.target
Alias=dbus
Source: exempi
Version: 2.6.1-2
Severity: serious
User: debian-s...@lists.debian.org
Forwarded: https://gitlab.freedesktop.org/libopenraw/exempi/-/issues/23
X-Debbugs-Cc: debian-s...@lists.debian.org
In the latest upload of exempi 2.6.1-2 I've enabled the test suite which
is now run during
Am 22.06.22 um 11:49 schrieb Julien Cristau:
On Wed, Jun 22, 2022 at 10:50:48AM +0200, Michael Biebl wrote:
Marking as RC, as it causes a FTBFS
Not using -Wl,--fatal-warnings might be a workaround for systemd until
gnu-efi fixes this?
Yeah, I'll probably add a workaround like
diff
Package: gnu-efi
Version: 3.0.13+git20210716.269ef9d-2
Severity: serious
Forwarded: https://sourceforge.net/p/gnu-efi/bugs/28/
Hi,
since the latest update of binutils to 2.38.50.20220615,
the systemd source package fails to build:
```
$ ninja -C build/
ninja: Entering directory `build/'
Am 10.06.22 um 23:31 schrieb Michael Biebl:
On Fri, 10 Jun 2022 18:38:15 +0200 Julian Andres Klode
wrote:
AFAIU, systemd-boot also ships its own integration which conflicts with
sicherboot, as both would try to install kernels
Not (yet). Atm, systemd-boot(-efi) simply contains the split out
On Fri, 10 Jun 2022 18:38:15 +0200 Julian Andres Klode
wrote:
AFAIU, systemd-boot also ships its own integration which conflicts with
sicherboot, as both would try to install kernels
Not (yet). Atm, systemd-boot(-efi) simply contains the split out files
from systemd without any additional
Control: reassign -1 systemd
Control: severity -1 important
Control: affects -1 binfmt-support
Hi Facundo,
what you see here is a race condition between binfmt-support.service and
systemd-binfmt.service.
E.g. qemu installs binfmt config files for both binfmt-support and
systemd-binfmt leading
On Wed, 25 May 2022 10:34:15 +0200 Michael Biebl wrote:
Source: bolt
Version: 0.9.2-1
Severity: serious
bolt currently FTBFS during dh_auto_test and also fails its autopktest.
This is due to a change in systemd v251.
See https://github.com/systemd/systemd/issues/23499 where this is being
Source: bolt
Version: 0.9.2-1
Severity: serious
bolt currently FTBFS during dh_auto_test and also fails its autopktest.
This is due to a change in systemd v251.
See https://github.com/systemd/systemd/issues/23499 where this is being
discussed.
-- System Information:
Debian Release:
Am 20.05.22 um 11:29 schrieb Bernhard Schmidt:
Hi Michael,
Am 19.05.22 um 16:03 schrieb Michael Biebl:
On Sun, 15 May 2022 16:02:48 +0300 Adrian Bunk wrote:
Version: 2.6.0~git20220510+dco-1
openvpn (2.6.0~git20220510+dco-1) experimental; urgency=medium
...
* Build against OpenSSL 3.0
On Sun, 15 May 2022 16:02:48 +0300 Adrian Bunk wrote:
Version: 2.6.0~git20220510+dco-1
openvpn (2.6.0~git20220510+dco-1) experimental; urgency=medium
...
* Build against OpenSSL 3.0
-- Bernhard Schmidt Fri, 13 May 2022 00:01:35 +0200
Berni, would you mind uploading this version to
1 - 100 of 2788 matches
Mail list logo
