Bug#917124: lvm2 logical volumes are not properly initialized

Am 27.12.18 um 23:09 schrieb Ben Caradoc-Davies: > And I am also please to report that the two-minute wait on shutdown seen > here after upgrade to 240-1 and also after upgrade to 240-2 occurs only > on the first shutdown after upgrade: >

Bug#917124: lvm2 logical volumes are not properly initialized

Am 27.12.18 um 22:59 schrieb Ben Caradoc-Davies: > Thanks, Michael. Confirmed fixed for me in 240-2. Thanks for the confirmation. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital

Bug#917167: Bug #917167 in systemd marked as pending

Control: tag -1 pending Hello, Bug #917167 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:

Bug#917195: Bug #917195 in systemd marked as pending

Control: tag -1 pending Hello, Bug #917195 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:

Bug#917215: Bug #917215 in systemd marked as pending

Control: tag -1 pending Hello, Bug #917215 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:

Bug#917124: Bug #917124 in systemd marked as pending

Control: tag -1 pending Hello, Bug #917124 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:

Bug#917215: systemd: FTBFS on armel and armhf (failing test)

Control: forwarded -1 https://github.com/systemd/systemd/issues/11248 Hi, thanks for the bug report. Am 24.12.18 um 09:31 schrieb Salvatore Bonaccorso: > Source: systemd > Severity: serious > Justification: FTBFS > > Hi > > systemd/240-1 FTBFS on armel and armhf due to one failing test >

Bug#917195: FTBFS on mips(el): expected ‘dev_t *’ {aka ‘long long unsigned int *’} but argument is of type ‘long unsigned int *’

Source: systemd Version: 240-1 Severity: serious User: debian-m...@lists.debian.org Usertags: mipsel mips Forwarded: https://github.com/systemd/systemd/issues/11247 The latest upstream release of systemd fails to build on mips/mipsel with the following error message: [346/1708] cc

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Control: forcemerge -1 917168 917173 Control: severity -1 grave Am 23.12.18 um 18:27 schrieb Baptiste BEAUPLAT: > Dear maintainers, > > This issue seems related to #917168, feel free to merge it. > > For the 100% cpu, I think the problem is here in kinit: > >

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Control: tags -1 + moreinfo Am 23.12.18 um 17:11 schrieb Eric Valette: > Package: systemd > Version: 240-1 > Severity: critical > Justification: breaks unrelated software > > After upgrading to 240 version, all my system started to take ages to boot. > It seems related to disk mapping first and

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 01:40 schrieb Michael Biebl: > Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies: >> Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed >> Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator >> failed. >> Dec 23

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Control: retitle -1 lvm2 logical volumes are not properly initialized Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies: >> Can you provide a verbose debug log as requested in my previous reply? > > "journalctl -alb" output attached to my previous email. Please let me > know if you require Ok,

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies: > On 23/12/2018 13:11, Michael Biebl wrote: >> Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies: >>> Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to >>> boot an 4.18.0-3-amd64 initramfs to get a workin

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies: > Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed > Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator failed. > Dec 23 13:07:52 ripley systemd[376]: > /lib/systemd/system-generators/lvm2-activation-generator

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies: > Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to > boot an 4.18.0-3-amd64 initramfs to get a working system.) So 4.18 works and 4.19 fails? > Attached photo shows console after failure. Plymouth LUKS passphrase > entry has

Bug#917124: systemd: local-fs.target fails with result 'dependency'

control: tags -1 + moreinfo Am 23.12.18 um 00:35 schrieb Ben Caradoc-Davies: > Package: systemd > Version: 240-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > after upgrade to systemd 240-1, local-fs.target fails with result > 'dependency', > causing

Bug#916900: Fails to install: installed dash package post-installation script subprocess returned error exit status 1

Package: dash Version: 0.5.10.2-3 Severity: serious When running "debootstrap sid /path/to/chroot", dash fails to install Setting up dash (0.5.10.2-3) ... dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x No diversion 'diversion of

Bug#916319: dash: Update dpkg-divert usage

Control: severity -1 minor Am 20.12.18 um 04:31 schrieb Michael Biebl: . > Errors were encountered while processing: > dash > > Bumping the bug report to serious given this failure. > > Hm, probably better to file a new bug report with proper version tracking to prevent

Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

Control: severity -1 wishlist Control: retitle -1 allow crediting the seed file for some entropy Control: forwarded -1 https://github.com/systemd/systemd/pull/10621 On Sat, 15 Dec 2018 09:17:46 +0100 Stefan Fritsch wrote: > reassign 914297 systemd > affects 914297 apache2 > thanks > > On

Bug#916678: systemd: Caught , dumped core as pid 2097

Control: severity -1 important Control: tags -1 moreinfo Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn: > | systemd[1]: Caught , dumped core as pid 2097. Please try to get a backtrace following https://wiki.debian.org/HowToGetABacktrace Thanks, Michael -- Why is it that all of the

Bug#914957: [Pkg-shadow-devel] Bug#914957: login: removal of pts/* from /etc/securetty wasn't applied in stretch

On Sat, 8 Dec 2018 21:57:11 +0100 =?UTF-8?B?QsOhbGludCBSw6ljemV5?= wrote: > While I believe securetty should be disabled by default Fwiw, I agree that securetty is a bad idea and should be removed from the default pam configuration. There is a login-standing bug report, documenting that

Bug#907409: casync: diff for NMU version 2+20180321-2.1

Am 30.11.2018 um 13:47 schrieb Adrian Bunk: > Control: tags 907409 + pending > > Dear maintainer, > > I've prepared an NMU for casync (versioned as 2+20180321-2.1) and > uploaded it to DELAYED/14. Please feel free to tell me if I should > cancel it. Feel free to upload without delay. Thanks

Bug#914657: [Pkg-net-snmp-devel] Bug#914657: Acknowledgement (stdout is flodded with debug messages)

Hi Craig Am 26.11.18 um 12:46 schrieb Craig Small: > Hi Michael, >   Thanks for looking into this for me. It does seem that if you have a > setup that includes libsnmp30 but not snmp then this problem will occur. > > Looking through the changelog, I can see that snmp.conf has bounced > between

Bug#913984: FTBFS: test-suite failure on armel: daqueue-dirty-shutdown

On Sun, 18 Nov 2018 01:23:10 +0100 Michael Biebl wrote: > Source: rsyslog > Version: 8.39.0-1 > Severity: serious > Forwarded: https://github.com/rsyslog/rsyslog/issues/2122 > > The test-suite fails on armel for the daqueue-dirty-shutdown test > https://buildd.debian.org

Bug#913984: FTBFS: test-suite failure on armel: daqueue-dirty-shutdown

Source: rsyslog Version: 8.39.0-1 Severity: serious Forwarded: https://github.com/rsyslog/rsyslog/issues/2122 The test-suite fails on armel for the daqueue-dirty-shutdown test https://buildd.debian.org/status/fetch.php?pkg=rsyslog=armel=8.39.0-1=1540991734=0 FAIL: daqueue-dirty-shutdown

Bug#913983: FTBFS: test-suite failure on mipsel: imfile-truncate

Source: rsyslog Version: 8.39.0-1 Severity: serious Forwarded: https://github.com/rsyslog/rsyslog/issues/3232 The test-suite fails on mipsel: https://buildd.debian.org/status/fetch.php?pkg=rsyslog=mipsel=8.39.0-1=1540989122=0 FAIL: imfile-truncate =

Bug#913620: Happened before in #905187

Thanks for the updated patch. Am 14.11.18 um 15:12 schrieb Felipe Sateler: > Thanks. Please find an attached patch. However, I don't think this makes > a practical difference for debian packages, since they run configure > only once per builddir. True. That said, I wanted to post it here since I

Bug#913620: Happened before in #905187

On Tue, 13 Nov 2018 01:27:41 -0800 Kunal Mehta wrote: > This is the same regression as #905187 - is there a good way we can > prevent this from happening again? Fwiw, reprroducible-builds.org now also contains a merged-usr variation, which also found this particular problem:

Bug#913620: Happened before in #905187

Hi Felipe On Wed, 14 Nov 2018 10:42:55 -0300 Felipe Sateler wrote: > + SED=/bin/sed dh_auto_configure --builddirectory $${target}-build > $(PARALLEL) -- $$(eval echo \$${$${target}_config}); \ Reading

Bug#913729: [Pkg-utopia-maintainers] Bug#913729: wrong modinfo path if compiled on merged-usr system and executed on unmerged system

Am 14.11.18 um 13:18 schrieb Michael Biebl: > I.e. AC_PATH_PROG return the wrong path when built in a merged-usr > system. > I suspect that this particular problem is very widespread, so i was > wondering if we couldn't just address this once in the AC_PATH_PROG [1] > macro, by

Bug#913729: wrong modinfo path if compiled on merged-usr system and executed on unmerged system

Package: firewalld Version: 0.6.3-2 Severity: serious Trying to start firewalld, I get: Nov 14 13:05:04 pluto firewalld[1126]: WARNING: modinfo command is missing, not able to detect conntrack helpers. Nov 14 13:05:04 pluto firewalld[1126]: ERROR: Failed to load nf_conntrack module: Nov 14

Bug#913346: Subject: Re: libsane1: Cannot update libsane1

On Sun, 11 Nov 2018 09:07:05 +0100 Gianfranco Costamagna wrote: > Control: -1 severity serious > > > > > > Hi, > > > > libsane1 has been renamed to libsane. > > > > apt install libsane > > > > will remove libsane1 and install libsane which should resolve your issue. > > > > I beg to

Bug#912603: libsane1: discolored bar (genesys_gl847)

Control: forwarded -1 https://gitlab.com/sane-project/backends/issues/7 On Thu, 01 Nov 2018 18:04:55 + "Amy Kos" wrote: > Package: libsane1 > Version: 1.0.27-3 > Severity: normal > Tags: upstream > > Hi, > > GL847 chip based scanners produce a discolored or black bar in the middle of >

Bug#913125: missing requested rename of libsane

Am 07.11.18 um 16:49 schrieb Jörg Frings-Fürst: > severity 913125 serious > thanks > > Hi, > > Am Mittwoch, den 07.11.2018, 15:05 +0100 schrieb Michael Biebl: >> Control: severity -1 normal > >> Am 07.11.18 um 13:42 schrieb Michael Biebl: >>> The rem

Bug#913125: missing requested rename of libsane

Control: severity -1 normal Am 07.11.18 um 13:42 schrieb Michael Biebl: > The removal of toupper_ascii is strictly speaking an ABI break, but this > never was part of the public API (checking the header files of 1.0.25). > So no bumping the soname for the removal of toupper_ascii i

Bug#913125: missing requested rename of libsane

Am 07.11.18 um 14:40 schrieb Jörg Frings-Fürst: > and extract the symbols files from the resulting *.deb files. > > Both are attached. The symbols files you attached include the symbols for the backends. You need to exclude those. Picking the first symbol in your list as an example:

Bug#913125: missing requested rename of libsane

Am 07.11.18 um 13:53 schrieb Michael Biebl: > On Wed, 7 Nov 2018 13:42:00 +0100 Michael Biebl wrote: > >> I then built 1.0.27 with this symbols file, the result is: > > Let me add here, that many of those (new) symbols are not part of the > public API as declared in sane.

Bug#913125: missing requested rename of libsane

On Wed, 7 Nov 2018 13:42:00 +0100 Michael Biebl wrote: > I then built 1.0.27 with this symbols file, the result is: Let me add here, that many of those (new) symbols are not part of the public API as declared in sane.h, so should probably be hidden upstream or at least marked as optio

Bug#913125: missing requested rename of libsane

On Wed, 07 Nov 2018 12:57:49 +0100 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= wrote: > Hello, > > Am Mittwoch, den 07.11.2018, 11:27 +0100 schrieb Gianfranco Costamagna: > > control: tags -1 moreinfo > > > > Hello Jörg > > > > > with the upstream release 1.0.27 are some libraray functions > > >

Bug#908681: Possibly unnecessary tracking of symbols

On Fri, 19 Oct 2018 10:47:25 -0300 =?UTF-8?Q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= wrote: > Hi! I have been looking at this bug and then at the packaging and > installed files. > > dpkg -L libsane tells me that the *only* public library shipped is > /usr/lib//libsane.so.1 > > The rest

Bug#910015: User is in the plugdev group

Control: severity -1 normal On Mon, 01 Oct 2018 19:05:27 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > Package: adb > Version: 1:8.1.0+r23-1~stage1.2 > Severity: grave > > $ id > uid=1000(jidanni) gid=1000(jidanni) >

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

Am 01.10.2018 um 14:56 schrieb Jeremy Bicha: > On Sun, Sep 30, 2018 at 2:45 PM Michael Biebl wrote: >> Raising this issue of handling a missing ontologies file more gracefully >> with the tracker upstream developers seems like a reasonable idea and I >> would prefer this s

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

On Sun, 23 Sep 2018 14:33:36 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?= wrote: > Hello Christoph Anton Mitterer, > I just tried to reproduce this issue. > > It looks like this issue got introduced in upstream commit [1]. > There an error message got added that leads to an immediate process exit.

Bug#909455: Bug #909455 in systemd marked as pending

Control: tag -1 pending Hello, Bug #909455 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:

Bug#909455: Bug #909455 in systemd marked as pending

Control: tag -1 pending Hello, Bug #909455 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:

Bug#909356: [Pkg-utopia-maintainers] Bug#909356: iwd 0.8 not compatible with NM < 1.14

Am 22.09.18 um 12:41 schrieb Adrian Bunk: > On Sat, Sep 22, 2018 at 11:22:07AM +0200, Andreas Henriksson wrote: >> Package: iwd >> Version: 0.8-1 >> Severity: serious >> >> Filing this bug report to block iwd 0.8 from migrating to testing (yet). >> >> The NetworkManager support for iwd has been

Bug#852585: sg3-utils: Update udevadm path

On Tue, 20 Jun 2017 14:55:37 +0200 Michael Biebl wrote: > On Wed, 25 Jan 2017 14:42:36 +0100 bi...@debian.org wrote: > > Package: sg3-utils > > Version: 1.42-2 > > Severity: normal > > User: pkg-systemd-maintain...@lists.alioth.debian.org > > Usertags: udevadm &

Bug#852571: open-infrastructure-system-boot: Update udevadm path

On Sat, 9 Sep 2017 08:48:04 +0200 Daniel Baumann wrote: > tag 852571 pending > thanks > > got a few other changes to test, will upload new release tomorrow. Another friendly ping -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#852575: powerpc-utils: Update udevadm path

On Tue, 20 Jun 2017 15:01:54 +0200 Michael Biebl wrote: > On Wed, 25 Jan 2017 14:42:37 +0100 bi...@debian.org wrote: > > According to codesearch [1] your package powerpc-utils does hard-code the > > udevadm path as /sbin/udevadm. > > You might also consider not hard-c

Bug#908362: VMs fail to start with "Kernel does not provide mount namespace: Permission denied"

Package: libvirt-daemon-system Version: 4.6.0-2 Severity: grave Hi, with the kernel update to 4.18, I'm no longer able to start any VMs via libvirt/virt-manager. I get the following error: Error starting domain: internal error: child reported: Kernel does not provide mount namespace:

Bug#892738: consolekit: consolekit removal causes a regression

On Sat, 7 Apr 2018 12:13:03 +0200 (CEST) har...@a-little-linux-box.at wrote: > Dear Robert, Steve and Michael, > > how do you think about adding https://github.com/ConsoleKit2/ConsoleKit2 to > the archive as a maintained alternative to consolekit? Looking into packaging elogind might be a more

Bug#907940: gnome-boxes FTBFS with vala 0.42.0-1

Am 08.09.18 um 00:08 schrieb Andreas Henriksson: > Control: tags -1 + pending > > Hello, > > The new 3.30.0 upstream release has been (mostly) perpared in git > which should fix this issue. It is however blocked by needing a > couple of new components packaged first (as the new version depends >

Bug#907998: gimp: Gimp does not load or crashes quickly

On 9/5/18 01:08, Attila Kinali wrote: > Package: gimp > Version: 2.10.6-2 > Severity: grave > Justification: renders package unusable > > Hi, > > No matter what I do, Gimp does not load properly. Most times it > just gets stuck on some routine on boot up. If it successfully > loads, then it

Bug#900269: ifupdown: last version breaks upgrade

On 9/2/18 16:42, Guus Sliepen wrote: > On Sun, Sep 02, 2018 at 03:34:46PM +0200, Michael Biebl wrote: > >> On Mon, 28 May 2018 11:08:00 +0200 Eric Valette >> wrote: >> >>> When upgrading, you're stuck with the last message in console "setting up >&

Bug#900269: ifupdown: last version breaks upgrade

On Mon, 28 May 2018 11:08:00 +0200 Eric Valette wrote: > When upgrading, you're stuck with the last message in console "setting up > ifupdown" and nothing else. The machine dropped its ip address but > seems to fails to acquire a new one. and stay like this for minutes. I'm suprised ifupdown

Bug#900269: ifupdown: last version breaks upgrade

On Thu, 7 Jun 2018 12:34:31 + Martin Hradil wrote: > This is caused by systemd-tty-ask-password-agent: > > rxvt-unicode(28371)-+-bash(28373)---sudo(14210)---dpkg(14211)---ifupdown.postin(14214)---systemctl(15338)---systemd-tty-ask(15342) > systemd-tty-ask-password-agent is a symptom, not

Bug#907466: Package doesn't ship xml files anymore

On 8/30/18 22:35, Dr. Tobias Quathamer wrote: > I would like to go through this list of packages and try to spot the > actual usage of the XML files. If there are only a few packages which > need to be fixed, it might still be doable before the freeze. From a > quick glance, there are a few false

Bug#907466: Package doesn't ship xml files anymore

Hi Tobias On 8/30/18 22:35, Dr. Tobias Quathamer wrote: > thanks for your investigation. I've deprecated those XML files more than > two years ago and thought that this time might suffice to switch over to > the JSON files. From past experience, unless you actively file bug reports, don't expect

Bug#907466: Package doesn't ship xml files anymore

On Wed, 29 Aug 2018 15:49:43 +0200 Michael Biebl wrote: > Possibly affected: > https://codesearch.debian.net/search?q=iso-codes.*xml The list might be even longer: https://codesearch.debian.net/search?q=iso_.*%5C.xml apper calibre choose-mirror cinnamon-control-center django-countries e

Bug#907466: Package doesn't ship xml files anymore

On Tue, 28 Aug 2018 11:58:46 +0200 Laurent Bigonville wrote: > Package: iso-codes > Version: 4.0-1 > Severity: serious > > Hi, > > Since 4.0-1, iso-codes package is not shipping the xml files anymore: > >* New upstream version 4.0 > - This new release does no longer include the XML

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

On 8/28/18 19:59, Felipe Sateler wrote: > On Tue, Aug 28, 2018, 14:00 Robbie Harwood > wrote: > This would make systemd-shim unusable. > > > Indeed. See bugs #901404 and #901405 for things that need to be fixed in > 10-4. Systemd-shim is currently broken,

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

Control: reassign -1 systemd-shim Control: forcemerge 903295 -1 On 8/28/18 18:56, Robbie Harwood wrote: > Package: libpam-systemd > Version: 238-5 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > (This bug has been reported also against systemd-shim: >

Bug#907306: configure: error: gdk-pixbuf-query-loaders not found in path

On 8/26/18 12:50, Simon McVittie wrote: > Looking at librsvg, it seems we might be able to reinstate > gdk-pixbuf-query-loaders in libgdk-pixbuf2.0-dev but rename it to > $(DEB_HOST_ARCH)-gdk-pixbuf-query-loaders, and then change librsvg to > use AC_CHECK_TOOL instead of AC_PATH_PROGS; or install

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:45 schrieb Michael Biebl: > Am 17.08.2018 um 15:37 schrieb Felipe Sateler: > >> Well, as long as we support the --skip-systemd-native, we can't drop the >> check :/  > > I don't understand. > I thought the idea was that dh_installsystemd would gen

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:37 schrieb Felipe Sateler: > Well, as long as we support the --skip-systemd-native, we can't drop the > check :/  I don't understand. I thought the idea was that dh_installsystemd would generate code to always pass --skip-systemd-native to invoke-rc.d? -- Why is it that

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:27 schrieb Felipe Sateler: > I'll revert the change to unbreak things soon. For the longer term, > maybe we can switch the check to  > > /lib/systemd/systemd-sysv-install is-enabled $service I wouldn't bother introducing new code here and simply revert the change to get the

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:24 schrieb Michael Biebl: > The problem is, that dh_installsystemd enables the service *after* a > start attempt has been made and > systemctl is-enabled checks for the state of the native service unit. > > With dh_systemd_enable/start, the enable part was b

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:13 schrieb Felipe Sateler: > Hmm. Commit 6f95680ffc9b1605841eb7d3d8eb92c790e6c73a looks like the > culprit of the regression. But I'd like to understand why this happens. > Shouldn't update-rc.d have enabled the service? The lldpad or corosync package ship a native systemd

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 14:53 schrieb Valentin Vidic: > On Fri, Aug 17, 2018 at 02:40:53PM +0200, Michael Biebl wrote: >> Could you add "set -x" to /usr/sbin/invoke-rc.d, then re-install the >> lldapd package and attach the output please. > > Sure, here it goes: Tha

Bug#862884: Disable libnm-glib support

Hi mike On Sat, 14 Apr 2018 00:45:10 -0700 Mike Miller wrote: > On Sat, Apr 14, 2018 at 01:02:45 +0200, Michael Biebl wrote: > > I intend to upload a new version of network-manager soonish which will > > drop libnm-glib/libnm-util. I'm thus bumping this issue to RC in

Bug#903224: udev: Fails to upgrade

Am 09.07.2018 um 02:22 schrieb Michael Biebl: > 2/ We remove the sandboxing features which trip up older systemd > versions. Specifically this is the commit which turns the seccomp > filters from a black into a whitelist. Specifically this would mean > removing > > System

Bug#903224: udev: Fails to upgrade

Am 08.07.2018 um 17:51 schrieb Michael Biebl: > Am 08.07.2018 um 17:42 schrieb Michael Biebl: >> Any ideas how we can convince apt to upgrade the packages in the correct >> order, ie. make sure that udev's postinst is run after systemd's >> postinst without adding a vers

Bug#903224: udev: Fails to upgrade

Am 08.07.2018 um 17:42 schrieb Michael Biebl: > Am 08.07.2018 um 08:54 schrieb Sven Joachim: >> On 2018-07-08 03:05 +0200, Michael Biebl wrote: >> >>> Control: tags -1 moreinfo unreproducible >>> >>> Am 08.07.2018 um 00:26 schrieb Kurt Roeckx: >>&g

Bug#903224: udev: Fails to upgrade

Am 08.07.2018 um 08:54 schrieb Sven Joachim: > On 2018-07-08 03:05 +0200, Michael Biebl wrote: > >> Control: tags -1 moreinfo unreproducible >> >> Am 08.07.2018 um 00:26 schrieb Kurt Roeckx: >>> Package: udev >>> Version: 239-5 >>> Severi

Bug#903224: udev: Fails to upgrade

Control: tags -1 moreinfo unreproducible Am 08.07.2018 um 00:26 schrieb Kurt Roeckx: > Package: udev > Version: 239-5 > Severity: serious > > Hi, > > When upgrading udev, it failed to upgrade, because udev didn't > want to start. I think there might be some ordering problem. Unfortunately I

Bug#902946: Fails to load autofs module through autofs4 alias

Control: severity -1 important Am 03.07.2018 um 23:08 schrieb Michael Biebl: > Am 03.07.2018 um 20:11 schrieb Ben Hutchings: >> Package: systemd >> Version: 239-1 >> Severity: serious >> >> Starting with Linux 4.18, the autofs4 kernel module is renamed >&g

Bug#902946: Fails to load autofs module through autofs4 alias

Hi Ben Am 03.07.2018 um 23:10 schrieb Ben Hutchings: > On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote: >> Is there a 4.18 kernel available where this can be tested? > > I've uploaded it to experimental and it's currently in NEW. I've forwarded this issue upstream an

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

Control: tags -1 moreinfo This is what I get when I build a package using pbuilder, which build-depends on policykit-1 (which in turn pulls in libpam-systemd): The following packages have unmet dependencies: systemd : Breaks: systemd-shim (< 10-4~) but 10-3 is to be installed The following

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

Am 04.07.2018 um 20:39 schrieb Helmut Grohne: > Package: libpam-systemd > Version: 239-4 > Severity: critical > Justification: makes gnupg2 ftbfs > User: helm...@debian.org > Usertags: rebootstrap > Control: affects -1 + src:gnupg2 > > A native(!) build of gnupg2 with sbuild and >

Bug#902946: Fails to load autofs module through autofs4 alias

Am 03.07.2018 um 23:10 schrieb Ben Hutchings: > On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote: >> Am 03.07.2018 um 20:11 schrieb Ben Hutchings: >>> Package: systemd >>> Version: 239-1 >>> Severity: serious >>> >>> Starting

Bug#902946: Fails to load autofs module through autofs4 alias

Am 03.07.2018 um 20:11 schrieb Ben Hutchings: > Package: systemd > Version: 239-1 > Severity: serious > > Starting with Linux 4.18, the autofs4 kernel module is renamed > to autofs, but retaining an 'autofs4' alias. > > Despite the presence of the alias, systemd fails to load the > autofs

Bug#902644: upower: Upower breaks power saving settings after upgrade to 0.99.8-1

Hi On Thu, 28 Jun 2018 21:55:01 -0300 Adilson dos Santos Dantas wrote: > Package: upower > Version: 0.99.8-1 > Severity: important > > Dear Maintainer, > > After upgrading upower to 0.99.8-1, my KDE power saving settings stops > working. > There is no reaction when I unplug and plug back my

Bug#902884: [Pkg-utopia-maintainers] Bug#902884: upowerd fails to start

Control: forcemerge 902411 -1 Am 02.07.2018 um 22:45 schrieb Eric Valette: > Package: upower > Version: 0.99.8-1 > Severity: grave > Justification: renders package unusable > > I had no upowerd daemon running on all my boxes: > > Jul 02 20:52:00 htpc1 systemd[1]: Starting Daemon for power

Bug#902015: systemd-cron: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/crontab

Control: severity -1 wishlist Am 29.06.2018 um 08:44 schrieb Alexandre Detiste: > Hi, > > I feel like the severity of this bug is much too high, > as it only concerns bcron-run versus systemd-cron; > not vixie cron (the santdard implementation) vs systemd-cron. > > I don't see how to cleanly

Bug#902185: Bug #902185 in systemd marked as pending

Control: tag -1 pending Hello, Bug #902185 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:

Bug#902287: systemctl unmask --runtime no longer supported

Package: systemd Version: 239-1 Severity: serious upstream has removed support for systemctl unmask --runtime [1] According to codesearch we currently have two packages in the archive using unmask --runtime: avahi and policykit-1

Bug#902185: udev: fails to configure with systemd 238-5

Hi Am 23.06.2018 um 10:40 schrieb Sven Joachim: > , > | $ systemctl status systemd-udevd.service > | ● systemd-udevd.service - udev Kernel Device Manager > |Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; > vendor preset: enabled) > |Active: failed (Result:

Bug#901129: timidity: removes conffile belonging to timidity-daemon

Am 09.06.2018 um 14:28 schrieb Reiner Herrmann: > On Sat, Jun 09, 2018 at 02:16:14PM +0200, Michael Biebl wrote: >> Why would the timidity package remove a conffile that belongs to another >> package? That doesn't make sense to me. > > Because the conffile removed

Bug#901129: timidity: removes conffile belonging to timidity-daemon

Am 09.06.2018 um 13:36 schrieb Reiner Herrmann: > Hi Sven and Michael, > > thank you for the report and sorry for breaking it. > >> specifically >> >> timidity.maintscript >> rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon >> >> doesn't look correct either. >>

Bug#901129: timidity: removes conffile belonging to timidity-daemon

The changes in https://salsa.debian.org/debian/timidity/commit/3e768cabe537f2a8a22a51f4eb398a974fe15e25 specifically timidity.maintscript rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon doesn't look correct either. dpkg-maintscript-helper does not have support for moving

Bug#900924: [Pkg-utopia-maintainers] Bug#900924: Bug#900924: [network-manager-gnome] segfault after upgrade to 1.8.12-1

Control: forcemerge 900869 -1 Am 07.06.2018 um 13:36 schrieb Shin Ice: > Hi, > > On Wed, Jun 06, 2018 at 09:43:12PM +0200, Michael Biebl wrote: >> >> Please test 1.8.12-2 and report back. It was uploaded a couple of >> minutes ago and should hit the mirrors soon. >

Bug#900924: [Pkg-utopia-maintainers] Bug#900924: [network-manager-gnome] segfault after upgrade to 1.8.12-1

Am 06.06.2018 um 20:54 schrieb Shin Ice: > Package: network-manager-gnome > Version: 1.8.12-1 > Severity: grave > > --- Please enter the report below this line. --- > > Hi, > > after upgrading network-manager-gnome and libnma0 to 1.8.12-1 I receive > a segfault every time I open the menu to

Bug#900095: FTBFS against xserver-xorg-core 1.20.0

Source: xserver-xorg-video-vmware Version: 13.2.1-1 Severity: serious The recent update of xserver-xorg-core to 1.20.0 makes the package FTBFS as can be seen by the latest binNMU https://buildd.debian.org/status/package.php?p=xserver-xorg-video-vmware make[3]: Entering directory '/<>/build/saa'

Bug#862757: Finished patched

Hi Diane On Sun, 06 May 2018 23:09:10 -0700 Diane Trout wrote: > Just for thoroughness. Here's the final patch that seems to be working. Thanks for updating the patch. Feel free to list yourself as the author of this patch. It feels kinda odd to have my name listed there when

Bug#862766: Remove libsocialweb from Debian? Was: Re: Port from libnm-glib to libnm

Am 11.05.2018 um 17:37 schrieb Jeremy Bicha: > libsocialweb depends on libnm-glib4 which is no longer built from > source. libsocialweb has no reverse dependencies and has been > abandoned upstream for years. Can we remove it from Debian now? bisho was the only rdep of libsocialweb and it was

Bug#898264: gnome-shell: Hold in unstable until bolt migrates to testing

Am 09.05.2018 um 14:59 schrieb Jeremy Bicha: > On Wed, May 9, 2018 at 8:48 AM, Michael Biebl <bi...@debian.org> wrote: >> Wouldn't a recommends in gnome (or gnome-core) be a better place? >> I suppose thunderbolt support requires support from other components as >> well,

Bug#898264: gnome-shell: Hold in unstable until bolt migrates to testing

Am 09.05.2018 um 14:17 schrieb Jeremy Bicha: > Source: gnome-shell > Version: 3.28.1-1 > Severity: serious > > gnome-shell has a new recommends on bolt. I don't think that we want > this update to migrate to Testing until bolt is there (so that the > recommended package will be automatically

Bug#897986: systemctl failures during dist-upgrade due to missing libcryptsetup.so.12

Am 05.05.2018 um 15:21 schrieb Michael Biebl: > The attached patch is also a bit too simplistic atm. We shouldn't > hard-code the upstream version number. Something like the attached patch might be more suitable. -- Why is it that all of the instruments seeking intelligent life in the un

Bug#897597: udev rules installed into wrong path

Package: casync Version: 2+20180321-1 Severity: serious It seems we install the udev rules file into the wrong path as usr/rules.d/75-casync.rules This happens because meson.build contains udevdir = dependency('udev', required : false).get_pkgconfig_variable('udevdir') udevrulesdir =

Bug#897436: Acknowledgement (broken nautilus integration)

Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://github.com/owncloud/client/issues/6393 Looks like this is known upstream and fixed by https://github.com/owncloud/client/pull/6397 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed

<    1   2   3   4   5   6   7   8   9   10   >