Control: reassign -1 python3-dbusmock 0.18.3-2
Control: affects -1 src:network-manager
Am 09.01.20 um 14:15 schrieb Thomas Haller:
> I think you also need
>
> https://github.com/martinpitt/python-dbusmock/commit/776b131e2b50cc3d1a0a52d683f1de721c9b7fbe
> Did you include that patch as well?
Hi Martin, hi Thomas
Am 09.01.20 um 10:00 schrieb Thomas Haller:
> On Wed, 2020-01-08 at 23:40 +0100, Martin Pitt wrote:
>> Hello Michael and Thomas,
>>
>> Michael Biebl [2020-01-08 19:42 +0100]:
>>>> The latest update of network-manager causes an autopkgte
On Sun, 29 Dec 2019 13:35:35 +0100 Michael Biebl wrote:
> Package: network-manager, python-dbusmock
> Version: 1.22.2-1
> Severity: serious
>
> The latest update of network-manager causes an autopkgtest regression in
> python-dbusmock.
>
> https://ci.debian.net/data/aut
Hi everyone
On Mon, 06 Jan 2020 19:14:46 +0100 Vincent Bernat wrote:
> So, I suppose this is a because of randomizatio of the MAC address on
> wifi networks. I don't see anytrhing special in the NEWS file about
> this. Previously, the hardware MAC address was used to do the DHCP
> request.
>
>
Can you provide a full, verbose debug log:
https://wiki.gnome.org/Projects/NetworkManager/Debugging
Which dhcp client do you use: internal, isc-dhcp-client, ...?
signature.asc
Description: OpenPGP digital signature
Package: network-manager, python-dbusmock
Version: 1.22.2-1
Severity: serious
The latest update of network-manager causes an autopkgtest regression in
python-dbusmock.
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/3793816/log.gz
Control: affects -1 src:systemd
As you can see, this now causes FTBFS on reproducible-builds.org
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html
signature.asc
Description: OpenPGP digital signature
Package: libip4tc-dev
Version: 1.8.4-1
Severity: serious
Hi,
for some background, see the related bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946149#10
libiptc.pc was moved from libiptc-dev to libip4tc-dev and
libiptc-dev is now an empty dummy package (which is scheduled to be
Package: python3-nftables
Version: 0.9.3-1
Severity: serious
Hi Arturo,
thanks for packaging 0.9.3 so promptly.
Today I wanted to update firewalld to 0.8.0, which makes use of
python3-nftables. Unfortunately, I ran into problems. At first I
suspected that firewalld is buggy, but then it turned
Am 02.12.19 um 12:37 schrieb Matthew Vernon:
> Hi,
>
> I've pushed a -2 with a patch from upstream that fixes an ARM issue; I'm
> not sure it'll be what we need, but we'll see.
>
Thank you.
Is see that you made a binary upload for i386.
Those binary uploads can not migrate to testing (anymore):
Source: pcre2
Version: 10.34-1
Severity: serious
Hi,
pcre2 FTBFS on armel:
https://buildd.debian.org/status/fetch.php?pkg=pcre2=armel=10.34-1=1574962559=0
FAIL: RunTest
=
PCRE2 C library tests using test data from ./testdata
PCRE2 version 10.34 2019-11-21
Testing 8-bit
Control: severity -1 normal
Control: retitle -1 udev aborts processing rules on failures
Am 19.11.19 um 02:18 schrieb Michael Biebl:
> Am 19.11.19 um 00:56 schrieb Klaumi Klingsporn:
>> That leaves me with the question: Why the hell on my
>> amd64-system (with i386 enabled onl
Am 19.11.19 um 00:56 schrieb Klaumi Klingsporn:
> That leaves me with the question: Why the hell on my
> amd64-system (with i386 enabled only as
> foreign-architecture) the i386 version of libinput-bin was
> installed?
I'm puzzled as well how so many users ended up with a non-native
Am 18.11.19 um 11:24 schrieb Michael Biebl:
> Can you all check if you have the i386 version of libinput-bin installed
> (by accident) on your amd64 system?
>
.. and if installing the amd64 version via
apt install libinput-bin:amd64
helps
--
Why is it that all of the instrument
Can you all check if you have the i386 version of libinput-bin installed
(by accident) on your amd64 system?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
For everyone affected by this issue, can you please answer this question:
Did you reboot after the upgrade?
Is the problem reproducible after the reboot or only directly after the
upgrade?
signature.asc
Description: OpenPGP digital signature
Control: severity -1 normal
Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in
Control: tags -1 + moreinfo
Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in
On Wed, 30 Oct 2019 13:22:14 + Ian Jackson
wrote:
> The bulk of the bug is a discussion about the general approach to
> allowing Debian users to choose between systemd and elogind (and,
> therefore, allowing them to run desktoppy kind of software without
> systemd). As discussed it seems
Control: tag -1 pending
Hello,
Bug #935300 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:
On Mon, 9 Sep 2019 14:25:31 +0200 Gianfranco Costamagna
wrote:
> Source: nftables
> Version: 0.9.2-1
> Severity: serious
> Justification: breaks another package from working correctly
>
> Hello, according to firewalld upstream devs, we need 2 commits to fixup their
> test failures.
> I also
Package: openjdk-8-jdk-headless
Version: 8u232-b07-1
Severity: serious
Hi,
the latest upgrade of openjdk failed due to a file conflict:
Vorbereitung zum Entpacken von
.../25-openjdk-8-jdk-headless_8u232-b07-1_amd64.deb ...
Entpacken von openjdk-8-jdk-headless:amd64 (8u232-b07-1) über
Package: texlive-latex-extra
Version: 2019.20190830-1
Severity: serious
Hi,
today's upgrade failed with the following error message:
Entpacken von texlive-latex-extra (2019.20190930-1) über (2019.20190830-1) ...
dpkg: Fehler beim Bearbeiten des Archivs
[somehow messed up the CC list, s/pkg-gnome/pkg-systemd/]
Am 01.09.19 um 14:44 schrieb Alan Jenkins:
> On 01/09/2019 12:52, Michael Biebl wrote:
>> On 01.09.19 13:24, Alan Jenkins wrote:
>>> Package: gnustep-base-runtime
>>> Version: 1.26.0-4
>>>
On 01.09.19 13:52, Michael Biebl wrote:
> I guess gnustep-base-runtime explicitly needs to remove the existing
> /etc/rc?.d/???gdomap symlinks on upgrades in preinst (possibly guarded
> by a check which reads the old /etc/default/gdomap and tests if
> ENABLED=NO) so they can be properl
On 01.09.19 13:24, Alan Jenkins wrote:
> Package: gnustep-base-runtime
> Version: 1.26.0-4
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Dear Maintainer,
>
> I had "gnustep-base-runtime" installed on my system, probably as a
> dependency of "unar".
>
> When I
Am 31.08.19 um 16:43 schrieb Michael Biebl:
> So instead I tried reverting the following commit which was in the vicinity:
>
> commit 7ad178cea388dd1ffc9ac17ae2fecae32c8443b3
> Author: Rainer Gerhards
> Date: Wed Jul 31 11:36:27 2019 +0200
>
> omfile bugfix: race fi
On Wed, 21 Aug 2019 19:27:34 +0200 Rainer Gerhards
wrote:
> I had a look but to me it seems we actually run out file handles. No
> failure indication.
>
> Is this run in parallel? If so, how many tasks?
>
I'm running the test-suite with the --no-parallel option, so no parallel
tests.
It
On Fri, 30 Aug 2019 18:57:11 +0200 Michael Biebl wrote:
> Am 30.08.19 um 11:04 schrieb Simon McVittie:
> > Control: tags -1 + bullseye sid
> >
> > On Fri, 23 Aug 2019 at 10:04:28 +0200, Michael Biebl wrote:
> >> Setting up fuse (2.9.9-1) ...
> >> dpkg: err
Am 30.08.19 um 11:04 schrieb Simon McVittie:
> Control: tags -1 + bullseye sid
>
> On Fri, 23 Aug 2019 at 10:04:28 +0200, Michael Biebl wrote:
>> Setting up fuse (2.9.9-1) ...
>> dpkg: error processing package fuse (--configure):
>> installed fuse package post-ins
Package: cinnamon
Version: 4.0.10-1
Severity: serious
Trying to run cinnamon-settings, I get
$ cinnamon-settings
Traceback (most recent call last):
File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 620,
in
window = MainWindow()
File
.
Need to get 72.3 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian sid/main amd64 fuse amd64 2.9.9-1 [72.3 kB]
Fetched 72.3 kB in 0s (219 kB/s)
[master ba9ff87] saving uncommitted changes in /etc prior to apt run
Author: Michael
Am 21.08.19 um 17:43 schrieb Sven Joachim:
> On 2019-08-21 15:43 +0200, Ivo De Decker wrote:
>
>> Hi,
>>
>> On 8/21/19 3:14 PM, Michael Biebl wrote:
>>> Am 21.08.19 um 14:39 schrieb Ivo De Decker:
>>>> package: src:rsyslog
>>>> ve
Am 21.08.19 um 14:39 schrieb Ivo De Decker:
> package: src:rsyslog
> version: 8.1908.0-1
> severity: serious
> tags: ftbfs
>
> Hi,
>
> The latest version of rsyslog in unstable fails on s390x:
>
> https://buildd.debian.org/status/package.php?p=rsyslog
It's a test-suite failure. Seems the
Control: tag -1 pending
Hello,
Bug #934992 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: reassign -1 systemd 241-7
Am 18.08.19 um 18:39 schrieb Michael Biebl:
> Am 18.08.19 um 17:18 schrieb Michael Biebl:
>> I've created an LXC container via
>> autopkgtest-build-lxc debian bullseye
>> and got the same autopkgtest failure using this container.
Am 18.08.19 um 13:01 schrieb Andreas Henriksson:
> So apparently polkitd is not running after the first reboot attempt. I
> have no clue why or how to investigate why so I guess I'll leave that to
> the professionals.
>
> Maybe it would be useful to change the test to do
> "pidof polkitd || fail"
Am 18.08.19 um 17:18 schrieb Michael Biebl:
> Am 17.08.19 um 21:23 schrieb Paul Gevers:
>> Source: network-manager, systemd
>> Control: found -1 network-manager/1.20.0-1
>> Control: found -1 network-manager/1.19.90-2
>> Control: found -1 systemd/241-7
>> Severity
Am 17.08.19 um 21:23 schrieb Paul Gevers:
> Source: network-manager, systemd
> Control: found -1 network-manager/1.20.0-1
> Control: found -1 network-manager/1.19.90-2
> Control: found -1 systemd/241-7
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User:
Bringing Vincent into the loop here.
Vincent, can you gather the information Beniamino is asking for?
Am 08.08.19 um 09:51 schrieb Beniamino Galvani:
> On Wed, Aug 07, 2019 at 05:00:01PM +0200, Michael Biebl wrote:
>> Full downstream bug report at
>> https://bugs.debian.org/cgi-bi
Am 07.08.19 um 11:24 schrieb Vincent Lefevre:
> On 2019-08-06 22:24:49 +0200, Michael Biebl wrote:
>> Ok, so the current state of affairs is:
>>
>> dhcp=dhclient works always
>> dhcp=internal (the default) fails (sometimes)
>>
>> ?
>
> That's rig
Am 06.08.19 um 15:49 schrieb Vincent Lefevre:
> On 2019-08-06 15:27:19 +0200, Vincent Lefevre wrote:
>> Now, I'll try to see if I can reproduce the failure with dhcp.conf.
>
> I tried a dozen of times, but I couldn't.
>
Ok, so the current state of affairs is:
dhcp=dhclient works always
Am 06.08.19 um 15:35 schrieb Felipe Sateler:>
>
> On Tue, Aug 6, 2019 at 3:15 AM Michael Biebl # systemctl restart rpcbind.service rpcbind.socket
>
> Job for rpcbind.socket failed.
> See "systemctl status rpcbind.socket" and "journalctl -xe&quo
Control: tags -1 + moreinfo
Can you try and switch to dhclient instead of the internal one.
$ cat /etc/NetworkManager/conf.d/dhcp.conf
[main]
dhcp=dhclient
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Am 06.08.19 um 09:15 schrieb Michael Biebl:
> Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
>> rpcbind (1.2.5-5) unstable; urgency=medium
>> .
>>* debian/rules: Add --no-restart-after-upgrade option to
>> dh_installsystemd to avoid race
Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
> rpcbind (1.2.5-5) unstable; urgency=medium
> .
>* debian/rules: Add --no-restart-after-upgrade option to
> dh_installsystemd to avoid race condition at rpcbind.socket
> initialization (Closes: #933268)
Package: rpcbind
Version: 1.2.5-4
Severity: serious
Hi,
during an upgrade from -3 to -4, I got the following failure (sorry for
the German locale)
rpcbind (1.2.5-4) wird eingerichtet ...
Neue Version der Konfigurationsdatei /etc/init.d/rpcbind wird installiert ...
Job for rpcbind.socket failed.
Hi
Am 21.07.19 um 21:58 schrieb Guilhem Moulin:
> Now that libblockdev uses crypt_keyslot_change_by_passphrase() there is
> AFAICT nothing more to be done on the libblockdev or udisks2 side with
> respect to that bug. But maybe the Changelog entry for libblockdev
> 2.20-7+deb10u1 should be
Hi Guilhem, hi intrigeri,
first of all, thanks for debugging this issue and this excellent bug report!
On Sat, 20 Jul 2019 17:24:21 -0300 Guilhem Moulin
wrote:
> However as far as libblockdev is concerned, FWIW I fully support
> intrigeri's cherry-pick of upstream's 34ed7be. Adding a key slot
Am 01.07.19 um 10:29 schrieb Paul Menzel:
> On 30.06.19 15:58, Michael Biebl wrote:
>> I too have two keyboard layouts configured and this happens to me as
>> well, under GNOME/Xorg and afaics is simply me pressing by accident
>> Windows/Super + Space. This is the s
On Sun, 30 Jun 2019 14:35:47 +0200 Paul Menzel
wrote:
> Package: gnome-shell
> Version: 3.30.2-9
> Severity: serious
That feels vastly exaggerated. That aside...
> Dear Debian folks,
>
>
> With Debian Sid/unstable with the default GNOME session, that means
> Wayland is used, and with two
Hi Ivo
Am 24.06.19 um 00:46 schrieb Ivo De Decker:
> Control: tags -1 buster-ignore
>
> Hi,
>
> On Fri, Jun 21, 2019 at 07:42:00PM +0200, Michael Biebl wrote:
>> As former maintainer of pm-utils, I don't want to see pm-utils released
>> with buster.
>
> acpi-
Control: severity -1 important
Hi Raphael
On Wed, 19 Jun 2019 22:33:21 +0200 Michael Biebl wrote:
> Hi Raphael,
>
> On Tue, 11 Jun 2019 15:51:14 +0200 Raphael Hertzog
> wrote:
> > Hi,
> >
> > On Wed, 05 Jun 2019, Michael Biebl wrote:
> > > systemd-netwo
Am 21.06.19 um 20:05 schrieb Adam Borowski:
> On Fri, Jun 21, 2019 at 07:42:00PM +0200, Michael Biebl wrote:
>> Package: pm-utils
>> Version: 1.4.1-18
>> Severity: serious
>>
>> As former maintainer of pm-utils, I don't want to see pm-utils released
>> wit
Package: pm-utils
Version: 1.4.1-18
Severity: serious
As former maintainer of pm-utils, I don't want to see pm-utils released
with buster.
pm-utils is a set of hacks/scripts which back in the days were necessary
to successfully suspend/hibernate your system.
Nowadays, those hacks do more more
Am 20.06.19 um 11:25 schrieb Jonathan Carter:
> I just have a small proposal:
>
> Selecting "Gnome on Xorg" is really easy from GDM for anyone who has
> trouble on Wayland. It might be worth while adding that to the release
> notes so that users who are not quite ready for Wayland yet know that
>
Hi everyone
Am 20.06.19 um 11:12 schrieb Iain Lane:
>> I've left some comments on
>> https://salsa.debian.org/gnome-team/gdm/merge_requests/8 regarding the
>> technical side of the proposed change.
> Someone could probably look in Ubuntu's gdm3 package to see what we're
> doing. We provide
On Wed, 19 Jun 2019 22:16:58 +0200 Ansgar Burchardt wrote:
> Jonathan Dowland writes:
> > So far as I am aware there is still radio silence from active GNOME
> > packaging team members regarding this issue. No comment yet on the
> > patch I adapted, positive or negative; this bug (#927667)
Hi Raphael,
On Tue, 11 Jun 2019 15:51:14 +0200 Raphael Hertzog
wrote:
> Hi,
>
> On Wed, 05 Jun 2019, Michael Biebl wrote:
> > systemd-networkd.service in v241 is locked down more tightly then v232.
> > It might be worth a try to comment out the hardening features one by
Control: severity -1 normal
Am 07.06.19 um 00:55 schrieb Adam Borowski:
> Source: systemd
> Version: 241-5
> Severity: critical
> Justification: breaks the whole system
>
>
> When trying to switch to any other init system (and d-i offers no way to
> start with anything but systemd), prerm
Am 05.06.19 um 14:03 schrieb Raphael Hertzog:
> Hi,
>
> On Wed, 05 Jun 2019, Michael Biebl wrote:
>> What's the status of this bug?
>
> No progress.
>
>> Can you reproduce it with v242 from experimental?
>
> Yes.
>
>> I guess upstream is wai
On Fri, 24 May 2019 09:30:50 +0200 =?utf-8?q?Rapha=C3=ABl_Hertzog?=
wrote:
> Package: systemd
> Version: 241-3
> Severity: serious
> File: systemd-networkd
> User: de...@kali.org
> Usertags: origin-kali
>
> I upgraded an (OVH) dedicated server to Debian buster with systemd 241-3 and
> while it
Control: forcemerge 921267 -1
Am 28.05.19 um 00:59 schrieb Kathryn Tolsen:
> Package: systemd
> Version: 241-3
> Severity: Serious
>
> All systemd services are failing to start, best guess is, this is
> related to:
>
> https://github.com/systemd/systemd/issues/11810
This is already fixed in
Control: tag -1 pending
Hello,
Bug #929229 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 24.05.19 um 02:24 schrieb Paul Emmerich:
> Package: systemd-journal-remote
> Version: 241-3
> Severity: grave
> Justification: renders package unusable
> Tags: newcomer
>
> Dear Maintainer,
>
> we are maintaining a Debian
Looks like a regression introduced by commit
9d41a057d9643505942628c919869a7019646276 which missed to add "C" to getopts
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Package: e2fsprogs
Version: 1.45.1-2
Severity: serious
File: /lib/systemd/system/e2scrub_reap.service
During the latest update, I got this failure:
e2scrub_all.service is a disabled or a static unit not running, not starting it.
Job for e2scrub_reap.service failed because the control process
Am 19.05.19 um 21:13 schrieb S R Wright:
> Is this confined to systemd 241-4? Will back-revving to 241-3 be a
> sufficient workaround?
It will. To satisfy dependencies, you'll need to downgrade libsystemd0
as well (and libpam-systemd, libnss-systemd, systemd-* in case you have
those installed)
Hi Jonathan,
besides the excellent summary from Simon, I can mainly provide some
personal feedback. Every now and then, I try the GNOME/Wayland session,
but so far I've always switched back to GNOME/Xorg.
My biggest gripe is
https://bugzilla.gnome.org/show_bug.cgi?id=745032
I.e. mouse animation
Control: tag -1 pending
Hello,
Bug #927008 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:
Package: grub-efi-amd64-bin
Version: 1+2.02+dfsg1+16
Severity: serious
grub-efi-amd64-bin depends on grub-common_2.02+dfsg1-16 but only
grub-common_2.02+dfsg1-17 is available in the archive.
Regards,
Michael
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy:
Am 15.04.19 um 22:18 schrieb Michael Biebl:
> Using debhelper compat level 12, you are able to completely decouple
> dh_installinit and dh_installsystemd which would give you the ability to
> implement what you want afaics.
From debhelper's changelog:
debhelper (12.1) unstable; urgen
Hi Sam
Am 15.04.2019 um 20:38 schrieb Sam Hartman:
> control: severity -1 serious
>
> justification: libvirtd upgrades from stretch to buster break causing
> apt to fail and requiring the admin to get the systemd units into a
> consistent state before things can continue
>
>
> Unfortunately
Am 14.04.19 um 14:51 schrieb Steinar H. Gunderson:
> On Sun, Apr 14, 2019 at 01:33:43PM +0200, Michael Biebl wrote:
>> What's the output of
>> reportbug --template systemd
>> reportbug --template libpam-systemd
>
> Attaching.
Hm, something is borked in the encoding
Control: tags -1 moreinfo unreproducible
Doesn't look like libpam-systemd is properly installed
> dbus-update-activation-environment: systemd --user not found, ignoring
> --systemd argument
> cinnamon-session[23689]: WARNING: t+0,00945s: Could not get session id for
> session. Check that
Control: tags -1 moreinfo
Am 07.04.19 um 18:51 schrieb Andy Ruddock:
> Package: systemd
> Severity: critical
>
> I'm running Windows 10 (Home edition - up to date) on the desktop, with
> Virtualbox (v6.0.4).
> I've used both the netinst CD & the testing DVD (downloaded today -
> 07/Apr/2019) to
Control: severity -1 wishlist
The dependency seems correct.
policykit without a working logind session seems pretty much useless.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital
Am 10.03.19 um 17:54 schrieb Michael Biebl:
> Am 10.03.19 um 17:36 schrieb Harlan Lieberman-Berg:
>> On Sun, Mar 10, 2019 at 12:29 PM Michael Biebl wrote:
>>> Can you provide the output of
>>> systemctl status certbot.timer
>>> journalctl -u certbot.timer
Am 10.03.19 um 18:23 schrieb Harlan Lieberman-Berg:
> On Sun, Mar 10, 2019 at 1:19 PM Michael Biebl wrote:
>> Let's bump this to serious. I think you should consider making another
>> stable upload for this.
>> As users have pointed out, systems which aren't rebooted regularl
Am 06.03.19 um 13:17 schrieb Dan Poltawski:
> We are seeing this bug on the jessie ( systemd 215-17+deb8u10) and it's
> extremely serious, leading to systemd-journald eventually consuming all
> memory on the system. Is there a fix for jessie incoming?
jessie is oldstable and no longer
Am 15.01.19 um 14:59 schrieb Michal Hocko:
> [3.563937] e1000e :00:1f.6 lan0: renamed from eth0
>
Seems I can reproduce the issue, so there is no need on your side to
further debug debug this.
Will forward this to the upstream bug tracker.
--
Why is it that all of the instruments
Control: severity -1 important
I'm downgrading this to non-RC, as I'm not convinced this is actually a
bug in udev
Am 15.01.19 um 09:08 schrieb Axel Beckert:
> Control: found -1 239-15
>
> Hi Michael,
>
> Michael Biebl wrote:
>> Am 12.01.19 um 01:02 schrieb Axel Beckert
On Sat, 12 Jan 2019 14:54:09 +0100 Axel Beckert wrote:
> I don't have local access to the affected machine for the weekend and
> hence won't be able to test reboots before Monday again, though.
>
> I'm though also keen to know if a downgrade to udev 239 will make it
> more stable again, so I'll
Am 14.01.19 um 19:45 schrieb Isaac Gelado:
> When I got the initramfs shell I also typed
>
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
>
> and tried to continue the boot process, but it failed. Then I typed
>
> udevadm trigger --type=devices
Am 13.01.19 um 10:46 schrieb intrigeri:
> Hi!
>
> In Tails we're shipping systemd/stretch-backports. We will freeze our
> code base (and the APT repositories we use) on Jan 18 for our next
> major release, so in the current state of things we would ship
> 239-12~bpo9+1, which is vulnerable to
Control: tag -1 pending
Hello,
Bug #918841 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: tag -1 pending
Hello,
Bug #918848 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: tag -1 pending
Hello,
Bug #917607 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:
Please also tar up /etc/udev/rules.d and /lib/udev/rules.d and attach it
to the bug report.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Am 12.01.19 um 01:02 schrieb Axel Beckert:
> Control: reopen -1
> Control: found -1 240-3
> *sigh* I'm sorry to say, but it just happened again with udev 240-3
> and kernel 4.20-1~exp1.
Would be good to know, if it also happens with 239-15 or if it's caused
by some other update.
Tbh, udevd or
2019-01-11 17:22:13.0 +0100
@@ -1,3 +1,9 @@
+python-xmp-toolkit (2.0.1+git20140309.5437b0a-6) UNRELEASED; urgency=medium
+
+ * Update to libexempi8
+
+ -- Michael Biebl Fri, 11 Jan 2019 17:22:13 +0100
+
python-xmp-toolkit (2.0.1+git20140309.5437b0a-5) unstable; urgency=medium
On Thu, 10 Jan 2019 06:55:32 +0100 Axel Beckert wrote:
> Version: 240-3
>
> Hi Michael,
>
> I luckily can no more reproduce this with udev 240-3 and kernel
> 4.19.13-1 or 4.20-1~exp1.
Ok, thanks for testing.
> Since I can no more reproduce this with the versions above and I'm
> also affected
On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
wrote:
> Source: systemd
> Version: 204-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Control: found -1 232-25+deb9u6
> Control: found -1 240-2
>
> Hi,
>
> The following vulnerability was published for
Am 09.01.19 um 22:45 schrieb Michael Biebl:
> Should CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866 be handled
> separately, i.e. do you plan to file separate bug reports?
Hm, for some reason I only received #918848 just now.
So that part of my question is moot.
Regards,
Michael
-
On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
wrote:
> Source: systemd
> Version: 204-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Control: found -1 232-25+deb9u6
> Control: found -1 240-2
>
> Hi,
>
> The following vulnerability was published for
Am 09.01.19 um 07:32 schrieb Axel Beckert:
> Package: udev
> Version: 240-2
Is this specific to version 240-2?
Could you try downgrading udev to either 239-15 or 240-1 and report back
with the results.
Thanks,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
Control: tags -1 moreinfo unreproducible
Am 09.01.19 um 11:16 schrieb Axel Beckert:
> Hi,
>
> Axel Beckert wrote:
>> I have no idea why this is happening, but several packages use "udevadm
>> control --reload-rules" in their postinst (e.g. fuse) and if that's run,
>> all process except init are
Control: tag -1 pending
Hello,
Bug #917633 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 28.12.18 um 07:04 schrieb Ben Hutchings:
> And if you downgrade udev and libudev1 to version 239-15, that will
> trigger an update of the 4.19 initramfs (only) and you should then be
> able to boot with Linux 4.19.
Or upgrade to udev 240-2, which should fix this issue.
signature.asc
Am 28.12.18 um 09:40 schrieb Rafał Olejnik:
> lvm2-activation-generator: lvmconfig failed
>
> lvm2-activation-generator: Activation generator failed.
Those error messages are unrelated to this particular issue. They are
caused by the latest lvm2 update.
See
301 - 400 of 2789 matches
Mail list logo
