Bug#877672: [systemd] System Stalled at Pam-nologon

Control: tags -1 moreinfo unreproducible Am 04.10.2017 um 08:21 schrieb David Baron: > Package: systemd > Version: 234-3 > Severity: critical > > --- Please enter the report below this line. --- > This touches systemd because of concurrent boot threads but actual bug may be > elsewhere! > >

Bug#873778: Fix for the mozjs52 build on armel

Am 01.10.2017 um 20:03 schrieb Simon McVittie: > Control: clone -1 -2 Control: retitle -2 FTBFS on mips64el: various > test failures > > On Sat, 23 Sep 2017 at 12:29:08 +0200, Emilio Pozuelo Monfort wrote: >> Let's track the mips64el failure in a different bug, as it's >> completely different

Bug#877322: git-buildpackage: FTBFS: openjade:E: cannot open "/usr/share/gtk-doc/data/gtk-doc.dsl" (No such file or directory)

Hi Guido Am 30.09.2017 um 17:04 schrieb Guido Günther: > On Sat, Sep 30, 2017 at 04:32:46PM +0200, Andreas Beckmann wrote: >> openjade:E: cannot open "/usr/share/gtk-doc/data/gtk-doc.dsl" (No such file >> or directory) > > The gtk-doc package dropped the stylesheet in 1.26. gtk-doc maintainers

Bug#862758: Switch from gir1.2-networkmanager-1.0 to gir1.2-nm-1.0

Am 28.09.2017 um 19:47 schrieb Michael Biebl: > Please consider applying the patch I provided in my previous email. See the attached diff. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff --git a/debian/control b/debian/cont

Bug#877085: [Pkg-utopia-maintainers] Bug#877085: network-manager installation crashes debian buster

Control: tags -1 + moreinfo Am 28.09.2017 um 16:04 schrieb andy: > Package: network-manager > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the

Bug#877068: gvfs: version 1.34 breaks xdg-mime query filetype

Am 28.09.2017 um 13:55 schrieb Emilio Pozuelo Monfort: > On 28/09/17 13:38, Michael Biebl wrote: >> Updating xdg-utils to the latest upstream version 1.1.2 would include >> that fix. Unfortunately the Debian xdg-utils package seems to be >> unmaintained atm. > >

Bug#877068: gvfs: version 1.34 breaks xdg-mime query filetype

Am 28.09.2017 um 13:27 schrieb Michael Biebl: > There are two issues to fix here: we need to fix the bashism in gvfs and > we should update xdg-utils to use gio directly. This is already fixed upstream in xdg-utils by https://cgit.freedesktop.org/xdg/xdg-utils/comm

Bug#877068: gvfs: version 1.34 breaks xdg-mime query filetype

Am 28.09.2017 um 13:27 schrieb Michael Biebl: > if [ "$1" == "--help" ] || [ "$1" == "-h" ]; then > Unfortunately there is a bashism in the script above which breaks --help > ("==" should be replaced by "="). gvfs-info is appa

Bug#877068: gvfs: version 1.34 breaks xdg-mime query filetype

Am 28.09.2017 um 12:54 schrieb definetti: > Package: gvfs > Version: 1.30.4-1+b1 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > upon upgrading to gvfs 1.34.0-2, commands like xdg-mime query filetype, that > depend on it, no longer work. This causes

Bug#876615: librsvg FTBFS with gtk-doc-tools 1.26: gtkdoc-scangobj: error: unrecognized arguments: --nogtkinit

Control: tags -1 patch fixed-upstream Am 24.09.2017 um 01:43 schrieb Adrian Bunk: > gtkdoc-scangobj: error: unrecognized arguments: --nogtkinit Fixed upstream by https://git.gnome.org/browse/librsvg/commit/?id=dfe34c8757debd07d4ef2f6f0381b2bcac1addc0 -- Why is it that all of the instruments

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: Bug#876342: avahi-daemon: upgrade failed: failed to configure

Am 21.09.2017 um 20:05 schrieb Vincent Lefevre: > On 2017-09-21 18:47:40 +0200, Michael Biebl wrote: >> Can you provide steps how to reproduce the issue? I've upgraded avahi on >> several systems and did not run into this particular problem. > > I don't know whether

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: avahi-daemon: upgrade failed: failed to configure

Control: tags -1 moreinfo unreproducible Am 21.09.2017 um 10:28 schrieb Vincent Lefevre: > Package: avahi-daemon > Version: 0.7-3 > Severity: grave > Justification: renders package unusable > > The upgrade of avahi-daemon failed: > > Setting up avahi-daemon (0.7-3) ... > Installing new version

Bug#876070: [Pkg-utopia-maintainers] Bug#876070: libavahi-core7: Does not install

Control: tags -1 + moreinfo unreproducible Am 18.09.2017 um 09:02 schrieb Eric Valette: > Package: libavahi-core7 > Version: 0.7-1 > Severity: grave > Justification: renders package unusable > > apt-get -f install > Reading package lists... Done > Building dependency tree > Reading state

Bug#874693: Is this still an issue?

Am 17.09.2017 um 01:40 schrieb Dean Loros: > I see that gjs 1.50 has been released. Is this bug still applicable? Yes. Why do you think it should not be? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc

Bug#874693: breaks other packages

Package: gjs Version: 1.49.92-1 Severity: serious The version from experimental apparently breaks other packages like gnome-weather: [14:29:37] (org.gnome.Weather.Application:3731): Gjs-CRITICAL **: JS ERROR: SyntaxError: redeclaration of let copyright @

Bug#873627: [Pkg-utopia-maintainers] Bug#873627: Not really fixed

Am 31.08.2017 um 16:17 schrieb Lisandro Damián Nicanor Pérez Meyer: > reopen 873627 > severity 873627 serious > thanks > > I'm afraid this last upload does not fixes the issue. I don't know > what's the real problem but I had to go back to testing's udisks2 to > be able to use Plasma. It does

Bug#873716: closing 873716

close 873716 thanks

Bug#870171: Attributing the problem to NM after all

Control: tags -1 + moreinfo On Sun, 30 Jul 2017 20:22:07 +0200 "Eduard Bloch" wrote: > clone 849875 -1 > reassign -1 network-manager > retitle -1 WPA usage error: Invalid passphrase character > thanks > > On Sat, Jul 01, 2017 at 11:32:28PM +0200, Francesco Poli wrote: >

Bug#872598: udev-udeb: no input in graphical installer

Am 23.08.2017 um 23:57 schrieb Cyril Brulebois: > My NMU FTBFSes on mips64el: > > https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=234-2.1=1503523165=0 > > James Cowgill mentioned this gcc bug report: > https://bugs.debian.org/871514 > > so I think I might duplicate the

Bug#872598: udev-udeb: no input in graphical installer

Hi KiBi Am 23.08.2017 um 10:08 schrieb Cyril Brulebois: > Would you be OK with a minimal NMU to fix the missing file? This issue has > been blocking the D-I Buster Alpha 1 release for weeks already (even if it > hadn't been diagnosed and reported against udev-udeb until recently), and > I'd be

Bug#872598: udev-udeb: no input in graphical installer

Am 19.08.2017 um 14:38 schrieb Cyril Brulebois: > A timely fix would be appreciated, the breakage(s) in the graphical > installer prevented us from releasing debian-installer over the past few > weeks, and it would be great not to wait too long before we're able to do > so, esp. with linux

Bug#872598: udev-udeb: no input in graphical installer

Am 19.08.2017 um 10:14 schrieb Raphael Hertzog: > I wonder if it would be possible to have autopkgtest tests covering > udev-udeb... We'd be happy to ship such an autopkgtest. Help in that regard would be much appreciated. -- Why is it that all of the instruments seeking intelligent life in

Bug#872598: udev-udeb: no input in graphical installer

Am 19.08.2017 um 10:19 schrieb Michael Biebl: > Am 19.08.2017 um 04:59 schrieb Cyril Brulebois: >> >> I haven't looked into the changelog and actual changes (yet), but I'd be >> happy to get some input (no pun intended) from systemd maintainers. >> > > Maybe this

Bug#872598: udev-udeb: no input in graphical installer

Am 19.08.2017 um 04:59 schrieb Cyril Brulebois: > > I haven't looked into the changelog and actual changes (yet), but I'd be > happy to get some input (no pun intended) from systemd maintainers. > Maybe this is related:

Bug#870310: glib-mkenums: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 108: ordinal not in range(128)

Am 01.08.2017 um 00:34 schrieb Adrian Bunk: > Control: tags -1 - moreinfo > > On Tue, Aug 01, 2017 at 12:03:31AM +0200, Michael Biebl wrote: >> Control: tags -1 + moreinfo >> >> Am 31.07.2017 um 23:04 schrieb Adrian Bunk: >>> File "/usr/lib/python3.

Bug#870310: glib-mkenums: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 108: ordinal not in range(128)

Control: tags -1 + moreinfo Am 31.07.2017 um 23:04 schrieb Adrian Bunk: > File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode > return codecs.ascii_decode(input, self.errors)[0] > UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 108: > ordinal not in

Bug#869922: [Pkg-utopia-maintainers] Bug#869922: policykit-1: members of group sudo become root with pkexec while ignoring /etc/sudoers

Control: severity -1 normal Control: close -1 Am 27.07.2017 um 17:53 schrieb mviereck: > Package: policykit-1 > Version: 0.105-18 > Severity: grave > Tags: security > Justification: user security hole > > Dear Maintainer, > > If an unprivileged user is member of group sudo, he can achieve

Bug#826471: intltool: Unescaped left brace in regex is deprecated at /usr/bin/intltool-update line 1070

Am 05.06.2016 um 20:12 schrieb Niko Tyni: > Package: intltool > Version: 0.50.2-3 > Severity: normal > User: debian-p...@lists.debian.org > Usertags: perl-5.24-transition > > Building the inkscape package triggers deprecation warnings with Perl > 5.24 (currently in experimental), and probably

Bug#868695: [systemd] Have not had any LC_CTYPE on previous versions

Am 20.07.2017 um 09:14 schrieb David Baron: > Package: systemd > Version: 233-10 > > --- Please enter the report below this line. --- > I have not seen this env variable in ages. > Do I need to install something involving the getty systemd service to get it? > > Since I have lived without it so

Bug#868695: systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt

Am 17.07.2017 um 20:54 schrieb Robert Luberda: > Yes, LC_CTYPE and other LC_ variables are empty, because they are set > like this in /lib/systemd/system/getty@.service. Afaics, this was broken by https://github.com/systemd/systemd/pull/6023 Robert, can you try reverting the commit

Bug#868695: systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt

Am 17.07.2017 um 20:54 schrieb Robert Luberda: > Package: systemd > Version: 234-1 > Severity: critical > Justification: breaks unrelated software > > I usually login on tty1 via getty and then switch to X via startx. > After recent upgrade of systemd I can no longer ssh to any > host in X11,

Bug#868695: systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt

Am 17.07.2017 um 20:54 schrieb Robert Luberda: > Package: systemd > Version: 234-1 > Severity: critical > Justification: breaks unrelated software > > I usually login on tty1 via getty and then switch to X via startx. > After recent upgrade of systemd I can no longer ssh to any > host in X11,

Bug#868308: Acknowledgement (file conflict with libsane)

If the renaming from libsane to libsane1 was intentional, you need proper versioned Breaks/Replaces against the old libsane package. Be aware that this is technically a library transition, so before you upload to unstable, get in touch with the release managers. -- Why is it that all of the

Bug#868307: Acknowledgement (library package ships libtools .la files)

See http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-dev https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#library https://wiki.debian.org/ReleaseGoals/LAFileRemoval -- Why is it that all of the instruments seeking intelligent life in the universe are

Bug#868309: FTBFS on various architectures due to missing symbols

Source: sane-backends Version: 1.0.27-1~experimental1 Severity: serious The version in experimental fails to build on various architectures: @@ -7191,7 +7089,7 @@ sanei_constrain_value@Base 1.0.24 sanei_debug_dll@Base 1.0.25 sanei_debug_msg@Base 1.0.24 - sanei_debug_sanei_ab306@Base 1.0.25

Bug#868308: file conflict with libsane

Package: libsane1 Version: 1.0.27-1~experimental1 Severity: serious The libsane package in experimental was renamed from libsane to libsane1, yet it ships the same contents, e.g. /usr/lib/x86_64-linux-gnu/libsane.so.1 This leads to a file conflicts between the two packages and failure to

Bug#868307: library package ships libtools .la files

Package: libsane1 Version: 1.0.27-1~experimental1 Severity: serious The libsane1 package ships libtool .la files. Those should be dropped or added to the -dev package (preferrably dropped). The libtool .la files do not encode a soname version, so they will cause a file conflict on soname bumps

Bug#866531: systemd: networking.service fails with virtual interfaces

Control: severity -1 important Control: reassign -1 ifupdown Am 29.06.2017 um 23:46 schrieb BERTRAND Joël: > Package: systemd > Version: 233-9 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I have seen for a long time several issues with systemd. All of

Bug#866376: [Pkg-utopia-maintainers] Bug#866376: network-manager: Network-Manager cause kernel panic

If the kernel panics, this sounds like a driver/kernel issue. Which hardware and driver do you use? Ben, does this sound familiar? Should this issue be reassigned to the kernel? Am 29.06.2017 um 11:33 schrieb Dario Maiocchi: > Package: network-manager > Version: 1.6.2-3 > Severity: critical >

Bug#850291: gdm3: does not work without gnome-session

Am 28.06.2017 um 23:27 schrieb Michael Biebl: > Afaics, we have 3 options: > > 1/ Add a hard dependency on gnome-session to gdm3 > (this kind of makes the line > Depends: gnome-session | x-session-manager | x-window-manager | > x-terminal-emulator, > pointless, so t

Bug#850291: gdm3: does not work without gnome-session

Am 28.06.2017 um 23:27 schrieb Michael Biebl: > Am 28.06.2017 um 21:00 schrieb Michael Biebl: >> Marking this as RC (missing dependency to function properly). >> We should fix that in stretch via a point release. > > After some more discussion on IRC, we concl

Bug#850291: gdm3: does not work without gnome-session

Am 28.06.2017 um 21:00 schrieb Michael Biebl: > Marking this as RC (missing dependency to function properly). > We should fix that in stretch via a point release. After some more discussion on IRC, we concluded this is a result of the following upstream change: https://git.gnome.org/brow

Bug#865589: Ships a tmpfile in /usr and /etc, one overriding the other

Package: openvpn Version: 2.4.3-1 Severity: serious Hi, I just noticed that the latest openvpn update now ships a tmpfile in /etc: /etc/tmpfiles.d/openvpn.conf This is odd, since the package also ships: /usr/lib/tmpfiles.d/openvpn.conf tmpfiles in /etc/tmpfiles.d are reserved to the local

Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

Hi Am 12.06.2017 um 20:33 schrieb Andreas Beckmann: > Switching desktop-file-utils or/and shared-mime-info to -noawait > triggers does not solve the problem. So afaics there is nothing that can be done from the Debian GNOME team side, right? > I can confirm that the ca-certificates-java change

Bug#761658: reliably disable DNS resolving

Hi Am 14.06.2017 um 19:49 schrieb benaryorg: > As this is about the default nameservers to be used when there is > nothing else configured, how would I disable DNS resolution then? First of all, systemd-resolved is not used and enabled by default. If you actually do use systemd-resolved,

Bug#761658: urgency of a fix before stretch

Am 02.06.2017 um 16:46 schrieb Norbert Preining: >> Your reasoning is flawed. The Google DNS servers are not set as default. > > AC_ARG_WITH(dns-servers, > AS_HELP_STRING([--with-dns-servers=DNSSERVERS], > [Space-separated list of default DNS servers]), >

Bug#761658: urgency of a fix before stretch

Am 02.06.2017 um 16:32 schrieb Norbert Preining: > Dear maintainers, > > leaking information, whatsoever, is not acceptable in Debian, and against > policy, at least lintian errors out on many occasions with > privacy-foobar* > errors. > > Setting the default servers to Google is not

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

On Wed, 31 May 2017 13:26:36 -0400 Daniel Kahn Gillmor wrote: > I apologize for the oversight, and want to know if it'd be ok for me to > upload 2.1.2-9.2 using the attached debdiff. I've pushed a queue of > these changes into the "unstable" branch at >

Bug#781535: unarchiving 781535, found 781535 in 3.22.3-2

On Fri, 02 Jun 2017 01:49:49 +0200 Andreas Beckmann wrote: > unarchive 781535 > found 781535 3.22.3-2 > thanks Andreas, can you explain why you reopened this bug report? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from

Bug#863447: dh_install -X is ignored for --list/fail-missing

Am 31.05.2017 um 22:23 schrieb Iain Lane: > On Sat, May 27, 2017 at 12:51:38AM +0200, Michael Biebl wrote: >> I also note, that usr/share/doc/NetworkManager/examples/server.conf is >> actually installed via debian/network-manager.examples, which contains: >> debian/tmp/usr/sha

Bug#744753: anacron: Anacron not triggered when system resumes under systemd

helps with not overloading > the system when coming out of suspend. > Drop anacron-resume.service, as this service is no longer necessary. > (Closes: #744753) > > -- Michael Biebl <bi...@debian.org> Mon, 29 May 2017 18:36:12 +0200 I've attached the debdiff as

Bug#863387: Acknowledgement (dh produces incomplete binary packages)

Am 26.05.2017 um 05:48 schrieb Debian Bug Tracking System: > As you can see from the 10.3 log, a lot of helpers are not run, like > dh_installdirs, dh_bugfiles, dh_lintian, etc. Comparing the output, I see the following helpers are not run with 10.3: dh_installdirs dh_installman dh_bugfiles

Bug#863387: dh produces incomplete binary packages

Package: debhelper Version: 10.3 Severity: grave Hi, I just noticed that debhelper from experimental produces incomplete binary packages. I've attached log building init-system-helpers with 10.2.5 and 10.3 As you can see from the 10.3 log, a lot of helpers are not run, like dh_installdirs,

Bug#857573: Processed: Re: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

Am 18.05.2017 um 10:32 schrieb Christoph Biedl: > Michael Biebl wrote... > >> To mark as mountpoint as network mount, there is the _netdev mount >> option. > > While I can confirm this provides a sane and safe shutdown for a mounted > AoE-device, this works only

Bug#862591: libvte-2.91-0: xfce4-terminal crashes when dumping a lot of text

Control: tags -1 moreinfo unreproducible Control: severity -1 normal Am 14.05.2017 um 22:57 schrieb Brian Warner: > Package: libvte-2.91-0 > Version: 0.46.1-1 > Severity: grave > > There seems to be a bug in sid's libvte, such that dumping a large > amount of text to stdout in a short period of

Bug#857573: Processed: Re: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

Am 14.05.2017 um 11:36 schrieb Guus Sliepen: > Another option is to explicitly add a dependency on the network for a > given mount point in /etc/fstab, see the systemd.mount manpage. > Basically, the following should work: > > /dev/etherd/... /mountpoint ext4

Bug#862509: not a drop-in replacement for pkg-config, doesn't properly handle --define-variable

Package: pkgconf Version: 0.9.12-5 Severity: serious Hi, today I was puzzled by a package failing to build rather randomly https://buildd.debian.org/status/package.php?p=network-manager-pptp=experimental It turns out, some buildds installed pkgconf instead of pkg-config, which resulted in the

Bug#862490: systemd 232-22 hangs with watchdog timeout, kills self with SIGABRT

Control: tags -1 + moreinfo Am 13.05.2017 um 16:48 schrieb Mike Edwards: > Package: systemd > Version: 232-23 > Severity: critical > Justification: causes serious data loss > > * Note that this report applies to 232-22 - I just did an apt upgrade > immediately before filing this bug report. > >

Bug#861683: Install xserver-xorg-legacy by default for stretch

Am 10.05.2017 um 07:32 schrieb Moritz Muehlenhoff: > On Tue, May 02, 2017 at 07:39:37PM +0200, Michael Biebl wrote: >> Same is true for users of startx. They need the suid wrapper provided by >> xserver-xorg-legacy in such a case. such a case == a non-KMS driver being in use. &g

Bug#712612: gcr: diff for NMU version 3.20.0-5.1

Am 06.05.2017 um 10:43 schrieb Christoph Biedl: > Michael Biebl wrote... > >> Am 06.05.2017 um 00:00 schrieb Christoph Biedl: > >>> I've prepared an NMU for gcr (versioned as 3.20.0-5.1), upload to >>> DELAYED/5 will follow in a few hours. Please feel free

Bug#712612: gcr: diff for NMU version 3.20.0-5.1

Am 06.05.2017 um 00:00 schrieb Christoph Biedl: > Control: tags 712612 + patch > Control: tags 712612 + pending > > Chris Lamb wrote... > there are two files under a BSD license in build/valgrind/*. In addition the ocumentation has its own license in docs/reference/COPYING. > > Seems

Bug#861683: Package: installation-reports GNOME is not Working

On Mon, 1 May 2017 00:28:59 -0500 Gerardo Flores wrote: > Package:installation-reports > Boot method: (Virtual box) > > Image version: > RC3 > Date: Abril 29 20717 > Machine: Virtual BOX DELL Presicion and Lenovo

Bug#861683: Install xserver-xorg-legacy by default for stretch

Source: xorg Version: 1:7.7+18 Severity: serious With virtualbox-dkms gone for stretch, trying to install GNOME inside Virtualbox will lead to gdm failing to start, as it tries to run Xorg as unprivileged user. This requires a KMS compatible driver though. Same is true for users of startx. They

Bug#857995: respawn loop due to insufficient permissions

Am 02.05.2017 um 13:43 schrieb Michael Biebl: > After further investigation, this particular information is incorrect, > it seems. It's not the main gdm3 process which dies. So the respawning > is not done by systemd, but by the main gdm process: Which seems to be a result of the sess

Bug#857995: respawn loop due to insufficient permissions

Am 17.03.2017 um 01:06 schrieb Michael Biebl: > Am 17.03.2017 um 00:56 schrieb Michael Biebl: >> To reproduce the problem: >> >> reboot, login, logout, switch to console, login as root, systemctl >> restart gdm3. >> >> The result ist a constantly resp

Bug#857995: respawn loop due to insufficient permissions

On Thu, 23 Mar 2017 07:10:05 -0400 Jeremy Bicha wrote: > By the way, the constant respawn is really annoying when I install > stretch on VirtualBox. > > I use the latest stretch testing netboot iso to install. Then I need > to boot to a command line with Internet so I can

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

Hi Bernd Am 30.04.2017 um 05:53 schrieb Bernd Zeimetz: > Hi Michael, > > any news on that? I could upload an NMU if you thats okay for you. > Or is there anything else I can help with? The package is in collab-maint. If you can commit your changes there and make the upload, this would be great.

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

Am 26.04.2017 um 00:23 schrieb Bernd Zeimetz: > Hi, > >> Does this break existing services/packages in stretch? If so, which ones? >> I'm trying to evaluate if this RC or can be fixed for buster. > > yes. As mentioned, #856429 - run-vmblock\x2dfuse.mount from > open-vm-tools-desktop. Hm, but

Bug#861204: deb-systemd-invoke: fails to handle units with escaped characters

Hi Am 25.04.2017 um 22:09 schrieb Bernd Zeimetz: > Package: init-system-helpers > Version: 1.47 > Severity: serious > Tags: patch > > Hi, > > to fix #856429 I need to handle a unit with an escaped character > correctly in the maintainer scripts generated by dh_systemd*. > > Unfortunately

Bug#859262: Re: gnome-orca: Gets stuck if target app is busy

Am 19.04.2017 um 22:37 schrieb Niels Thykier: > Control: retitle -1 gnome-orca: Gets stuck if target app is busy > > Samuel Thibault: >> Niels Thykier, on mer. 19 avril 2017 20:19:00 +, wrote: >>> Time to hunt for some dbus experts who can tell us why a process might >>> fail to respond to a

Bug#781155: openbsd-inetd: openbsd-inetd.service should be the main service file

Am 11.04.2017 um 19:17 schrieb Michael Biebl: > Renaming the .service file so the SysV init script and systemd service > unit name align is a valid solution for this particular case. But then > again, we have other packages where the names don't align. That said, my recommendation

Bug#781155: openbsd-inetd: openbsd-inetd.service should be the main service file

Am 11.04.2017 um 18:01 schrieb Raphael Hertzog: > On Tue, 11 Apr 2017, Marco d'Itri wrote: >> On Apr 11, Niels Thykier wrote: >> >>> Are there any updates on this bug? If not, then we will be inclined to >> I do not think that there is anything I can or should do in >>

Bug#859885: No longer necessary, should not be released with stretch

control: clone -1 -2 reassign: -2 ftp.debian.org retitle: -2 RM: gnome-shell-extension-refreshwifi -- ROM; obsolete Am 08.04.2017 um 18:25 schrieb Jonathan Carter: > +1, package should be removed > > Last when I checked that extension, stretch hat a slightly older version > of Gnome that didn't

Bug#859885: No longer necessary, should not be released with stretch

Am 8. April 2017 18:25:06 MESZ schrieb Jonathan Carter : >+1, package should be removed > Should I reassign this bug to ftp.debian.org so the package is removed completely?

Bug#859885: No longer necessary, should not be released with stretch

Am 08.04.2017 um 17:10 schrieb Michael Biebl: > Package: gnome-shell-extension-refreshwifi > Version: 6.0-1 > Severity: serious > > Hi, > > this extensions was originally developed to work around a bug in > gnome-shell: > https://bugzilla.gnome.org/show_bug.cgi?id=7679

Bug#859885: No longer necessary, should not be released with stretch

Package: gnome-shell-extension-refreshwifi Version: 6.0-1 Severity: serious Hi, this extensions was originally developed to work around a bug in gnome-shell: https://bugzilla.gnome.org/show_bug.cgi?id=767918 This has been fixed in the mean time in gnome-shell 3.22.2 and that fix is available in

Bug#852059: [Pkg-dns-devel] Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long

On Mon, 3 Apr 2017 14:37:27 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 03.04.2017 um 13:32 schrieb Michael Biebl: > > In jessie, your opendnssec-signer SysV init script didn't use > > init-d-script, which would explain the regression in stretch. > > After

Bug#852059: [Pkg-dns-devel] Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long

Am 03.04.2017 um 13:32 schrieb Michael Biebl: > > /usr/sbin/invoke-rc.d doesn't have 15 char limit, so reassigning back to > opendnssec-signer. As mentioned earlier, this is most likely an issue in > /lib/init/init-d-script which is used under sysvinit or the init script > i

Bug#852059: [Pkg-dns-devel] Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long

Am 03.04.2017 um 12:43 schrieb Michael Biebl: > Am 03.04.2017 um 11:59 schrieb Ondřej Surý: >> Control: reassign -1 init-system-helpers >> Control: affects -1 opendnssec-signer opendnssec-enforcer >> Control: severity -1 serious >> >> Hi, >> >> I a

Bug#852059: [Pkg-dns-devel] Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long

Am 03.04.2017 um 13:32 schrieb Michael Biebl: > /usr/sbin/invoke-rc.d doesn't have 15 char limit, so reassigning back to > opendnssec-signer. As mentioned earlier, this is most likely an issue in > /lib/init/init-d-script which is used under sysvinit or the init script > itse

Bug#852059: [Pkg-dns-devel] Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long

Control: reassign -1 opendnssec-signer Control: found -1 1:2.0.4-2 Am 03.04.2017 um 11:59 schrieb Ondřej Surý: > Control: reassign -1 init-system-helpers > Control: affects -1 opendnssec-signer opendnssec-enforcer > Control: severity -1 serious > > Hi, > > I am quite certain this hasn't been

Bug#859419: non-functional after installation (service fails to start)

Package: opendnssec-enforcer Version: 1:2.0.4-2 Severity: serious After running apt-get install opendnssec-enforcer in a pristine Debian stretch test VM, the service is in a non-functional state. See attached screenshot -- System Information: Debian Release: 9.0 APT prefers unstable-debug

Bug#859418: non-functional after installation (service fails to start)

Package: opendnssec-signer Version: 1:2.0.4-2 Severity: serious After running apt-get install opendnssec-signer, the service fails to start. See attached screenshot from a test VM -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'),

Bug#852059: [Pkg-dns-devel] Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long

Am 03.04.2017 um 12:43 schrieb Michael Biebl: > Am 03.04.2017 um 11:59 schrieb Ondřej Surý: >> Control: reassign -1 init-system-helpers >> Control: affects -1 opendnssec-signer opendnssec-enforcer >> Control: severity -1 serious >> >> Hi, >> >> I a

Bug#852059: [Pkg-dns-devel] Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long

Am 03.04.2017 um 11:59 schrieb Ondřej Surý: > Control: reassign -1 init-system-helpers > Control: affects -1 opendnssec-signer opendnssec-enforcer > Control: severity -1 serious > > Hi, > > I am quite certain this hasn't been broken prior to stretch as it was > working before, so I am bumping

Bug#858214: glib2.0: FTBFS (assertion failed: "BRT" == "-03")

Am 19.03.2017 um 21:56 schrieb Santiago Vila: > Package: src:glib2.0 > Version: 2.50.3-1 > Severity: serious > > Dear maintainer: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > but it failed: > >

Bug#856024: Processed: Adding a conflict in systemd-sysv

Control: reassgin -1 molly-guard Control: found -1 0.6.4 Am 18.03.2017 um 19:11 schrieb Francois Marier: > Control: reassign -1 systemd-sysv > >> This looks like a genuine bug in molly-guard, > > Yes and that's tracked in bug #837928. > > The present bug is specifically about the interaction

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

Am 19.03.2017 um 17:48 schrieb Carsten Leonhardt: > Michael Biebl <bi...@debian.org> writes: > >> I don't remember seeing the test suite to get stuck completely (as it >> apparently did on kfreebsd-* now). > > It could well be a general problem of the kfreebsd bu

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

Am 19.03.2017 um 17:22 schrieb Carsten Leonhardt: > Hi, > >> The changes in 0.18.5-3 were supposed to fix #837067, i.e. the test >> suite failing to pass on a single CPU machine. >> >> Did you test that as well? > > I did now, on a virtual single CPU kfreebsd-amd64 machine. 6 test runs, > no

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

Am 19.03.2017 um 12:59 schrieb Carsten Leonhardt: > Michael Biebl <bi...@debian.org> writes: > >> If you are sure it fixes the issue, feel free to upload without delay. > > I've made a dozen test runs of the collection tests on arm64, all > passed. After double

Bug#855951: Bug #855951: libsecret: diff for NMU version 0.18.5-3.1

Hi Charsten Am 18.03.2017 um 19:57 schrieb Carsten Leonhardt: > Control: tags -1 patch pending > > Dear maintainer, > > I've prepared an NMU for libsecret (versioned as 0.18.5-3.1) and am > about to upload it to DELAYED/5. Please feel free to tell me if I should > delay it longer. > If you

Bug#856024: Processed: Adding a conflict in systemd-sysv

Am 18.03.2017 um 19:11 schrieb Francois Marier: > Control: reassign -1 systemd-sysv > >> This looks like a genuine bug in molly-guard, > > Yes and that's tracked in bug #837928. And why is that bug not treated as RC then? > The present bug is specifically about the interaction between >

Bug#854078: network-manager: nm-online returns before network devices got an address

I've updated the packages at [1] to 1.6.2-3~test0 including the patches from the th/device-wifi-wait-for-scan-bgo770938 branch. Would be great if you can give those packages a try and report back. Regards, Michael [1] deb [trusted=yes] https://people.debian.org/~biebl/nm ./ -- Why is it that

Bug#856024: Processed: Adding a conflict in systemd-sysv

Control: reassign -1 molly-guard Control: found -1 0.6.4 This looks like a genuine bug in molly-guard, so this RC bug should be assigned to molly-guard. Adding a Breaks to systemd-sysv is backwards. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed

Bug#857995: respawn loop due to insufficient permissions

Am 17.03.2017 um 00:56 schrieb Michael Biebl: > Package: gdm3 > Version: 3.22.1-2 > Severity: serious > > > To reproduce the problem: > > reboot, login, logout, switch to console, login as root, systemctl > restart gdm3. > > The result ist a constantly r

Bug#801990: gdm3: Keymap is forced to set US

Am 14.03.2017 um 10:05 schrieb Raphael Hertzog: > Control: severity -1 serious > Control: affects -1 gnome-shell > > I also see this for any fresh stretch install where I select the French > keyboard layout. On first start, the greeting screen (handled by > gnome-shell AFAIK) uses a default

Bug#856036: screen sharing is not working and vino is segfaulting when started manually

Control: severity -1 normal Control: tags -1 + moreinfo On Fri, 24 Feb 2017 19:31:24 +0530 Pirate Praveen wrote: > package: vino > version: 3.22.0-1 > severity: grave > justification: makes the package unuseable > > I'm not able to share desktop using vino (5900 socket is

Bug#788769: marked as done (entangle: FTBFS without networking: relax-ng: failed to load external entity [..] mallard-1.0.rng)

On Sun, 26 Feb 2017 17:00:22 +0100 Florian Schlichting wrote: > Control: tags -1 +patch > > Hi Michael, Berlin BSP here. > > Given that it's too late now to get a mallard-rng package into Stretch, > I suggest to ship the mallard-1.0.rng file as part of the yelp-tools > package

Bug#788769: marked as done (entangle: FTBFS without networking: relax-ng: failed to load external entity [..] mallard-1.0.rng)

Hi Florian, hi release team On Sun, 26 Feb 2017 17:00:22 +0100 Florian Schlichting wrote: > Control: tags -1 +patch > > Hi Michael, Berlin BSP here. > > Given that it's too late now to get a mallard-rng package into Stretch, > I suggest to ship the mallard-1.0.rng file as part

Bug#856630: Creates empty /etc/default/rcS

Hi Phil Am 03.03.2017 um 16:28 schrieb Philip Hands: > Michael Biebl <bi...@debian.org> writes: > >> Package: installation-reports >> Severity: normal >> >> I've installed a Stretch system using the rc2 installer. >> >> After a successful instal

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