Bug#839884: [Pkg-utopia-maintainers] Bug#839884: Update hangs

Control: tags -1 moreinfo unreproducible Am 06.10.2016 um 07:18 schrieb Jörg Frings-Fürst: > Hi, > > more info: > > apt-get can't interrupted with STRG-C. > > After reboot I get: > > $ sudo apt-get dist-upgrade > [sudo] Passwort für jff: > E: Der dpkg-Prozess wurde unterbrochen; Sie müssen

Bug#839795: Acknowledgement (FTBFS, needs to be updated for liblognorm v2 and libfastjson)

Am 05.10.2016 um 16:35 schrieb Herbert Fortes: > owner 839795 ! > thanks > > I am checking the package. > > I will send the debian/changelog file > to this thread and probably will > be a delay/5. That's awesome. Thanks for taking care of the package. Fwiw, I've CCed you because I noticed that

Bug#839795: FTBFS, needs to be updated for liblognorm v2 and libfastjson

Source: sagan Version: 1.0.1-0.3 Severity: serious Tags: fixed-upstream liblognorm v2 is based on libfastjson and no longer json-c. sagan needs to be updated accordingly. The latest upstream release 1.1.2 has support for liblognorm >= 2.0.0 and libfastjson. -- System Information: Debian

Bug#834081: FTBFS on various architectures, test suite times out

Hi Pierre! On Fri, 12 Aug 2016 09:31:53 +0200 Michael Biebl <bi...@debian.org> wrote: > Source: liblognorm > Version: 2.0.1-1 > Severity: serious > > Hi, > > as can be seen on [1], the liblognorm package FTBFS on arm64, ppc64el > and s390x (some archs are still

Bug#839444: libgda5: FTBFS: tests failures annotations:

Hi Lucas! Am 04.10.2016 um 12:56 schrieb Lucas Nussbaum: > On 04/10/16 at 12:13 +0200, Andreas Henriksson wrote: >> On Tue, Oct 04, 2016 at 08:34:16AM +0200, Lucas Nussbaum wrote: >>> severity 839444 serious >>> thanks >> [...] If you can reproduce the problem, please provide a backtrace

Bug#839557: Package is empty (aside from man pages)

2.7.5-1 ii perl 5.24.1~rc3-3 ii po-debconf 1.0.19 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 2.201608 -- no debconf information >From bb6ac51c480a4bff3ebb3377ec583cae22538480 Mon Sep 17 00:00:00 2001 From: Michael Bi

Bug#838826: [Pkg-utopia-maintainers] Bug#838826: network-manager kills network on upgrade

Control: severity -1 important Am 28.09.2016 um 02:48 schrieb Michael Biebl: > Any news? Can you provide the requested information? Since I haven't received further information and can't reproduce the issue myself, I'm going to downgrade the severity. Unless I hear back from you, I'll cl

Bug#837745: xml-core: Makes packages to FTBFS with 'Unexpected debhelper version format'

Am 30.09.2016 um 16:17 schrieb Michael Biebl: > On Mon, 26 Sep 2016 14:38:42 +0100 Santiago Vila <sanv...@unex.es> wrote: >> On Mon, Sep 26, 2016 at 03:00:47PM +0200, gregor herrmann wrote: >> >>> Idea 1: remove this whole check; debhelper >= 9.20120909 is alrea

Bug#837745: xml-core: Makes packages to FTBFS with 'Unexpected debhelper version format'

On Mon, 26 Sep 2016 14:38:42 +0100 Santiago Vila wrote: > On Mon, Sep 26, 2016 at 03:00:47PM +0200, gregor herrmann wrote: > > > Idea 1: remove this whole check; debhelper >= 9.20120909 is already > > satisfied in oldstable, so this doesn't serve any purpose any more. > > I

Bug#837786: Possible solution

Am 28.09.2016 um 16:41 schrieb Mourad De Clerck: > On Tue, 27 Sep 2016 20:09:36 +0300 Svetlin Zarev wrote: >> I've fixed the issue on my side by removing CLUTTER_PAINT=disable- >> clipped-redraws:disable-culling from my /etc/environment > > ~$ cat /etc/X11/Xsession.d/10-clutter-hack > export

Bug#838826: [Pkg-utopia-maintainers] Bug#838826: network-manager kills network on upgrade

On Sun, 25 Sep 2016 15:45:54 +0200 Michael Biebl <bi...@debian.org> wrote: > Control: tags -1 moreinfo unreproducible > > Am 25.09.2016 um 14:59 schrieb Juha Jäykkä: > > Package: network-manager > > Version: 1.4.0-4 > > Severity: serious > > Justification:

Bug#838885: [gnome-shell-extensions] gnome-shell-extension-prefs: empty preferences window

Control: reassign -1 gnome-shell 3.22.0-1 Am 26.09.2016 um 06:12 schrieb Đặng Duy Sơn: > Package: gnome-shell-extensions > Version: 3.22.0-1 > Severity: normal > > --- Please enter the report below this line. --- > After upgrade gnome-shell-extensions from 3.21.92-1 to 3.22.0-1, >

Bug#838334: fixed in valadoc 0.30.0~git20160518-1

Am 26.09.2016 um 01:28 schrieb Sebastian Reichel: > Hi, > > On Mon, Sep 26, 2016 at 12:34:55AM +0200, Michael Biebl wrote: >> Thank you for fixing valadoc and valabind so quickly > > You are welcome. > >> and sorry for the short advance notice. > > No h

Bug#838334: fixed in valadoc 0.30.0~git20160518-1

Thank you for fixing valadoc and valabind so quickly and sorry for the short advance notice. I didn't expect to get a green light on the libvala transition so quickly. So kudos to the release team here as well. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

Am 25.09.2016 um 18:58 schrieb Julien Cristau: > On Sun, Sep 25, 2016 at 17:06:56 +0200, Michael Biebl wrote: >> Does this affect 4.7.2-1 as well, i.e. the current version in testing? > > The current version in testing is 4.6.4-1. Indeed. Somehow I was fooled by https://packages.

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

On Thu, 22 Sep 2016 07:51:36 +0200 Stefan Fritsch wrote: > Package: src:linux > Version: 4.7.4-2 > Severity: grave > Justification: renders package unusable > > When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my > filesystems fails to mount with: > >

Bug#838826: [Pkg-utopia-maintainers] Bug#838826: network-manager kills network on upgrade

Am 25.09.2016 um 14:59 schrieb Juha Jäykkä: > Versions of packages network-manager depends on: > pn libndp0 > pn libnm0 > pn libteamdctl0 Do you have an idea why these packages are listed as not available? If they are really not installed, then it

Bug#838826: [Pkg-utopia-maintainers] Bug#838826: network-manager kills network on upgrade

Control: tags -1 moreinfo unreproducible Am 25.09.2016 um 14:59 schrieb Juha Jäykkä: > Package: network-manager > Version: 1.4.0-4 > Severity: serious > Justification: makes the system unusable > > Dear Maintainer, > > Upon upgrade to 1.4.0-4, network-manager disconnects network connections >

Bug#838594: [Pkg-utopia-maintainers] Bug#838594: network-manager: FTBFS: ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: (nm_utils_file_is_private_key (path, NULL))

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771623 Am 2016-09-22 19:24, schrieb Chris Lamb: # ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: Hi Chris, thanks for the bug report. It's a known issue caused by the recent GnuTLS update. I've already filed

Bug#838431: systemd.postinst fails because the systemd-timesync user already exists when upgrading

Control: tags -1 moreinfo unreproducible Control: severity -1 important Am 21.09.2016 um 05:31 schrieb Grond: > Setting up systemd (215-17+deb8u5) ... > addgroup: The group `systemd-journal' already exists as a system group. > Exiting. > dpkg: error processing package systemd

Bug#838415: Wrong package name, installs typelib file into wrong directory

Package: gir1.2-urfkill-glib0 Version: 0.5.0-4 Severity: serious Hi, please follow /usr/share/doc/gobject-introspection/policy.txt when package typelib files. In case of gir1.2-urfkill-glib0, debian/gir1.2-urfkill-glib0.install is broken and installs the files as /usr/lib/Urfkill-0.5.typelib

Bug#838336: gnome-control-center: Keybinding panel fail to open

Am 20.09.2016 um 11:37 schrieb Raphael Hertzog: > Hi, > > On Tue, 20 Sep 2016, Michael Biebl wrote: >>> (gnome-control-center:24830): Gtk-CRITICAL **: Error building template >>> class 'CcKeyboardPanel' for an instance of type 'CcKeyboardPanel': &g

Bug#836426: Caused by libgtk-3-0 3.21

Am 20.09.2016 um 19:38 schrieb Josh Triplett: > On Thu, Sep 08, 2016 at 01:48:01PM +0200, Michael Biebl wrote: >> As for gnome-boxes, can you reproduce the problem with 3.21.3 from >> unstable? I just tested a local installation of debian 8.5 and that >> worked fine. I do

Bug#838336: gnome-control-center: Keybinding panel fail to open

Am 20.09.2016 um 04:44 schrieb mathieu rousseau: > Package: gnome-control-center > Version: 1:3.21.92-2 > Severity: grave > Justification: renders package unusable > > In gnome-control-center, the "keyboard" entry, for keybinding configuration > fail to open (and gnome-control-center close). The

Bug#838050: GDM3-only behaviour; Wayland not totally broken; bad tablets break even that

> > This breaks gnome-shell with all the Wacom and non-Wacom graphics > tablets I've tried, crashing gnome-shell at or shortly after the point > when they are connected. However the non-tablet USB devices I've tried > seem OK, including my (non-Wacom, non-pen, regular multitouch) > touchscreen.

Bug#837942: gtk-doc-tools: Missing dependency on pkg-config

Am 15.09.2016 um 19:58 schrieb Andreas Metzler: > Package: gtk-doc-tools > Version: 1.25-4 > Severity: serious > > gtk-doc-tools in experimental is lacking a dependency on pkg-config, > GTK_DOC_CHECK will fail if it is missing. > > --- > AC_DEFUN([GTK_DOC_CHECK], > [

Bug#837786: mutter: Issues repainting the display on mouse movement

Am 14.09.2016 um 17:16 schrieb JWM: > After upgrading my system this morning and restarting a new gnome-shell > session > (by rebooting), everything being displayed fails to repaint properly. > > Everytime I launch an application and try to move the window it leaves traces > (i.e., shadows of

Bug#838050: gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2

Am 17.09.2016 um 01:09 schrieb Erik Tews: > After startup, gdm doesn't show up and just shows a grey screen. Looking at > syslog reveals the reason: > > syslog:Sep 16 23:27:25 matte kernel: [ 172.983123] gnome-shell[3206]: > segfault > at 10 ip 7f8e7c85d6c4 sp 7ffd151d0a80 error 4 in

Bug#837738: Fails to start, Invalid property: GtkScrolledWindow.propagate-natural-height

Package: nautilus Version: 3.21.92-1 Severity: grave When running nautilus, one get's (nautilus:28168): Gtk-CRITICAL **: Error building template class 'NautilusToolbar' for an instance of type 'NautilusToolbar': .:194:52 Invalid property: GtkScrolledWindow.propagate-natural-height Segmentation

Bug#837727: gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92

Control: reassign gnome-shell-extension-top-icons-plus 15-2 On Wed, 14 Sep 2016 01:20:14 +0200 bi...@debian.org wrote: > Source: gnome-shell-extension-top-icon-plus > Version: 15-2 > Severity: serious > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: gnome-shell-3-22 > > Hi, >

Bug#837595: gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837593: gnome-shell-extension-redshift: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837594: gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837592: gnome-shell-extension-suspend-button: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837067: libsecret: FTBFS too much often (failing tests)

Control: retitle -1 libsecret: FTBFS - /collection/delete-sync failure Am 08.09.2016 um 14:40 schrieb Santiago Vila: > Package: src:libsecret > Version: 0.18.5-2 > Severity: serious > > Dear maintainer: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > (which is what

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

Am 08.09.2016 um 14:59 schrieb Sebastiaan Couwenberg: > On 09/08/2016 04:05 AM, Michael Biebl wrote: >> We've already seen the issue and forwarded to upstream. > > Due to the large number of affected packages that cannot be built until > gdk-pixbuf is fixed, please consider

Bug#837077: FTBFS, dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by debian/budgie-core/usr/bin/budgie-wm

Source: budgie-desktop Version: 10.2.6-1 Severity: serious Hi, after the recent upgrade of mutter to 3.21.x, budgie-desktop fails to build from source: dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by debian/budgie-core/usr/bin/budgie-wm (ELF format:

Bug#835737: gcr: FTBFS: Tests failures

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771052 Am 28.08.2016 um 11:33 schrieb Lucas Nussbaum: > Source: gcr > Version: 3.20.0-2 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20160828 qa-ftbfs > Justification: FTBFS on

Bug#835098: gcr: FTBFS: Missing build-depends on gnupg

Control: tags -1 + pending Am 22.08.2016 um 18:23 schrieb Michael Biebl: > Am 22.08.2016 um 15:04 schrieb Santiago Vila: >> >> To reproduce, please try to build the package on a chroot not having >> gnupg installed (neither gnupg1 or gnupg). >> >> The attached pa

Bug#836426: Caused by libgtk-3-0 3.21

Am 08.09.2016 um 03:23 schrieb Josh Triplett: > It seems appropriate for an issue that causes window contents to fail to > render, making gnome-boxes unusable with that version of GTK+. The emacs warnings don't look critical and are most likely something which needs to be addressed in emacs.

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771026 We've already seen the issue and forwarded to upstream. -- 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

Bug#836426: Caused by libgtk-3-0 3.21

On Wed, 7 Sep 2016 09:21:55 -0700 Josh Triplett wrote: > Control: reassign -1 libgtk-3-0 3.21.5-3 > Control: affects -1 gnome-boxes > Control: severity -1 serious > Control: forcemerge -1 832077 To me those two issues look not like they are related. After all, this one

Bug#837006: gnome-python-desktop: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

Hi Lucas, thanks for your bug report Am 07.09.2016 um 23:57 schrieb Lucas Nussbaum: >> touch debian/stamp-autotools-files >> /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation >> resolved from binary package "stamp-autotools". Stop. That looks like (yet another) cdbs

Bug#835550: [Pkg-utopia-maintainers] Bug#835550: network-manager: FTBFS on mips* and powerpc - NetworkManager segfaults

Hi James and Aurelien! Thanks for your detailed answers Am 27.08.2016 um 16:05 schrieb James Cowgill: > Adding _IO_stdin_used to the list of global symbols in > src/NetworkManager.ver (like the fix used in lua) seems to fix > everything. That should make the symbol visible to glibc again. That

Bug#835550: [Pkg-utopia-maintainers] Bug#835550: network-manager: FTBFS on mips* and powerpc - NetworkManager segfaults

Am 27.08.2016 um 10:16 schrieb Michael Biebl: > Hi > > Am 27.08.2016 um 01:52 schrieb James Cowgill: >> network-manager FTBFS on all mips arches and on powerpc with this error: > > >>> make[9]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins/ibft/tests

Bug#835550: [Pkg-utopia-maintainers] Bug#835550: network-manager: FTBFS on mips* and powerpc - NetworkManager segfaults

Hi Am 27.08.2016 um 01:52 schrieb James Cowgill: > network-manager FTBFS on all mips arches and on powerpc with this error: >> make[9]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins/ibft/tests' >> LD_BIND_NOW=1 LD_PRELOAD=./../.libs/libnm-settings-plugin-ibft.so >>

Bug#835098: gcr: FTBFS: Missing build-depends on gnupg

Am 22.08.2016 um 15:04 schrieb Santiago Vila: > Package: src:gcr > Version: 3.20.0-2 > Severity: serious > Tags: patch > > Dear maintainer: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do to build it) > but it failed:

Bug#835115: Uninstallable in sid, missing dependencies

Package: kio-extras Version: 4:16.04.2-1 Severity: serious Currently the kio-extras package is not installable in sid: # apt-get install kio-extras Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean

Bug#832713: closed by Martin Pitt <mp...@debian.org> (Bug#832893: fixed in systemd 231-2)

Am 15.08.2016 um 08:07 schrieb Michael Biebl: > Control: found -1 231-2 > > Am 15.08.2016 um 00:17 schrieb Rick Thomas: >> Sorry, it’s not fixed in 231-2… Please see attached boot log. > > Yeah, the revert was incomplete. > The service files in systemd use > MemoryD

Bug#832713: closed by Martin Pitt <mp...@debian.org> (Bug#832893: fixed in systemd 231-2)

Control: found -1 231-2 Am 15.08.2016 um 00:17 schrieb Rick Thomas: > Sorry, it’s not fixed in 231-2… Please see attached boot log. Yeah, the revert was incomplete. The service files in systemd use MemoryDenyWriteExecute=yes which is implemented using seccomp. So we need to revert

Bug#834121: FTBFS on various architectures, test suite times out

Source: liblognorm Version: 2.0.1-1 Severity: serious Hi, as can be seen on [1], the liblognorm package FTBFS on arm64, ppc64el and s390x (some archs are still building and might be affected as well). In all cases the build was killed after 150min due to inactivity when trying to build the test

Bug#834081: Missing dependency on libfastjson-dev

Package: liblognorm-dev Version: 2.0.1-1 Severity: serious Tags: patch Hi, liblognorm.pc has Requires: libfastjson Requires.private: libestr This means, the package needs a dependency on libestr-dev and libfastjson-dev. The package currently depends on libjson-c-dev, but not libfastjson-dev.

Bug#833487: systemd: Replaces file in systemd-container 230-1

Control: tags -1 + confirmed Am 05.08.2016 um 04:33 schrieb Matthias Urlichs: > Package: systemd > Version: 230-1 > Severity: serious > Justification: Missing Replaces: > > Unpacking systemd (231-1) over (230-1) ... > dpkg: error processing archive >

Bug#830842: State of Maps in Stable

Am 31.07.2016 um 14:52 schrieb James Rowan Lloyd: > Hi, > > I understand that this bug has been fixed upstream in the latest version > that is set to hit unstable. However, given that this bug affects all > versions, including stable, I'm wondering if there is any plan to patch > it and fix it in

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

Am 30.07.2016 um 20:47 schrieb Michael Biebl: > Am 30.07.2016 um 19:52 schrieb Felipe Sateler: >> On 29 July 2016 at 17:05, Michael Biebl <bi...@debian.org> wrote: >>> Am 29.07.2016 um 22:44 schrieb Michael Biebl: >>>> Package: init-system-helpers >&

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

Am 30.07.2016 um 19:52 schrieb Felipe Sateler: > On 29 July 2016 at 17:05, Michael Biebl <bi...@debian.org> wrote: >> Am 29.07.2016 um 22:44 schrieb Michael Biebl: >>> Package: init-system-helpers >>> Version: 1.41 >>> Severity: serious >>> >

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

Am 29.07.2016 um 23:10 schrieb Felipe Sateler: > I was going to ask this. I think we should register interest in > insserv in the reportbug configuration. Good idea. Added a bug-control script and pushed to master. -- Why is it that all of the instruments seeking intelligent life in the universe

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

Am 29.07.2016 um 22:44 schrieb Michael Biebl: > Package: init-system-helpers > Version: 1.41 > Severity: serious > > Running > update-rc.d foo disable > update-rc.d foo defaults > will create start symlinks although this should not happen for a > disabled service.

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

Package: init-system-helpers Version: 1.41 Severity: serious Running update-rc.d foo disable update-rc.d foo defaults will create start symlinks although this should not happen for a disabled service. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy:

Bug#832852: gnome-keyring: FTBFS: Tests failures

Hi Lucas! Am 29.07.2016 um 08:51 schrieb Lucas Nussbaum: > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): To me the relevant part seems to be /usr/bin/env: 'python': No such file or directory build/tap-driver is a python

Bug#832802: usage of network-pre.target results in systemd ordering cycle

Am 29.07.2016 um 09:17 schrieb Michael Biebl: > That's not a bug in systemd but in your service file. > If you want to run in early boot, you'll need to use > DefaultDependencies=yes and specify your dependencies/orderings carefully. I've filed an upstream RFE bug at [1]. Maybe they hav

Bug#832582: update-rc.d foo disable broken without insserv

Package: init-system-helpers Version: 1.40 Severity: serious In the latest upload, we dropped the insserv dependency and added some fallback code for SysV init scripts for the case where insserv is not installed [1]. Unfortunately, the disable case is not handled correctly. It removes all

Bug#830300: RE: Bug#830300: bug in mdadm

On Sat, 9 Jul 2016 19:47:07 +0300 =?utf-8?B?0JvRjtCx0LXQvSDQmtCw0YDQsNCy0LXQu9C+0LI=?= wrote: > Hi, > > The problem I am trying to solve is that my laptop (ASUS Zenbook UX301LAA) is > using Intel RAID0 setup: > > 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

Am 24.07.2016 um 17:47 schrieb Colin Watson: > Compromise proposal: how about I make it do nothing if libpam-systemd is > installed (e.g. "ConditionPathExists=!/usr/share/pam-configs/systemd", > which is probably the simplest available check without needing to deal > with multiarch paths), in

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

Am 24.07.2016 um 17:47 schrieb Colin Watson: > On Sun, Jul 24, 2016 at 01:38:25AM +0200, Michael Biebl wrote: >> I referenced in my other reply that the network.target ordering has just >> been added recently (in v230). So it is possible that previously there >> was still

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

Am 23.07.2016 um 12:29 schrieb Colin Watson: > On Sat, Jul 23, 2016 at 01:35:04AM +0200, Michael Biebl wrote: >> the addition of ssh-session-cleanup.service in the latest upload [1] is >> imho a bad idea. It's an aweful hack and besides, it also kills your SSH >> sessi

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

Hi Colin Am 23.07.2016 um 01:42 schrieb Michael Biebl: > See also the relevant upstream commit: > > https://github.com/systemd/systemd/commit/8c856804780681e135d98ca94d08afe247557770 > > This fix is part of v230. Before that, we had no proper ordering on > shutdown, so it w

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

See also the relevant upstream commit: https://github.com/systemd/systemd/commit/8c856804780681e135d98ca94d08afe247557770 This fix is part of v230. Before that, we had no proper ordering on shutdown, so it was indeed possible that some user sessions were not properly terminated before the

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

Package: openssh-server Version: 1:7.2p2-6 Severity: serious Hi, the addition of ssh-session-cleanup.service in the latest upload [1] is imho a bad idea. It's an aweful hack and besides, it also kills your SSH sessions on upgrades (thus severity RC). The proper fix is to use libpam-systemd.

Bug#796608: espeakup: diff for NMU version 1:0.71-27.1

Am 20.07.2016 um 01:03 schrieb Michael Biebl: > Right. I think this is the problem. Afair, systemd will try to read the > pid file as soon as the parent exits. That should happen *after* the > forked daemon process is ready and has written the pid file. > > See man dae

Bug#796608: espeakup: diff for NMU version 1:0.71-27.1

On Sun, 3 Jul 2016 17:55:42 -0300 Felipe Sateler wrote: > On 3 July 2016 at 16:44, Samuel Thibault wrote: > > Felipe Sateler, on Sun 03 Jul 2016 17:38:58 -0300, wrote: > >> On 3 July 2016 at 16:33, Samuel Thibault wrote: > >> >

Bug#831495: totem does not start, Aborted.

Am 16.07.2016 um 19:50 schrieb Kai Weber: > ❦ Michael Biebl <bi...@debian.org>: > >> Can you install the totem-dbgsym and related packages to get a more >> useful backtrace. > > It seems, totem-dbgsym is not available for amd64. I double checked > https://pac

Bug#831495: totem does not start, Aborted.

Am 16.07.2016 um 17:19 schrieb Kai Weber: > Package: totem > Version: 3.20.1-3 > Severity: grave > Justification: renders package unusable > > When starting totem the program does not start but exits directly with > "Aborted". I can provide more information if required. > > $ totem > Aborted

Bug#830300: RE: Bug#830300: bug in mdadm

On Sat, 9 Jul 2016 19:47:07 +0300 =?utf-8?B?0JvRjtCx0LXQvSDQmtCw0YDQsNCy0LXQu9C+0LI=?= wrote: > Hi, > > The problem I am trying to solve is that my laptop (ASUS Zenbook UX301LAA) is > using Intel RAID0 setup: > > 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Am 13.07.2016 um 18:28 schrieb Michael Biebl: > Am 13.07.2016 um 18:24 schrieb Michael Biebl: >> Turns out the problem is in init-system-helpers. >> In 1.35, invoke-rc.d was changed to use systemctl is-enabled. >> This doesn't work for sysv init scripts with v215. >

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Am 13.07.2016 um 18:24 schrieb Michael Biebl: > Turns out the problem is in init-system-helpers. > In 1.35, invoke-rc.d was changed to use systemctl is-enabled. > This doesn't work for sysv init scripts with v215. > As init-system-helpers is unpacked before systemd has

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Control: reassign -1 init-system-helpers Control: found -1 1.35 On Wed, 13 Jul 2016 16:15:56 +0200 Michael Biebl <bi...@debian.org> wrote: > Package: rpcbind > Version: 0.2.3-0.5 > Severity: serious > > During a dist-upgrade from jessie to stretch, the rpcbind package failed

Bug#830982: dist-upgrade from jessie to stretch fails: rpcbind.socket fails to start

Package: rpcbind Version: 0.2.3-0.5 Severity: serious During a dist-upgrade from jessie to stretch, the rpcbind package failed to upgrade cleanly: dpkg: error processing package rpcbind (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency

Bug#753510: fixed in liblognorm 1.0.1-3

Control: found -1 1.0.1-3 On Wed, 20 Aug 2014 13:19:46 + Pierre Chifflier wrote: nistrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Format: 1.8 > Date: Wed, 20 Aug 2014 14:58:53 +0200 > Source: liblognorm >

Bug#830800: FTBFS on arch:all

Source: php7.0 Version: 7.0.8-4 Severity: serious Hi, the php7.0 package FTBFS on arch:all https://buildd.debian.org/status/package.php?p=php7.0=unstable This means the php7.0 meta package is not built and the php package is therefor not installable. Michael -- System Information: Debian

Bug#811599: closing 811599

close 811599 1.14.0-1 thanks

Bug#827530: [pkg-cinnamon] Bug#827507: cinnamon-settings segfaults on entering power settings applet

Control: reassign -1 cinnamon-settings. On Thu, 23 Jun 2016 02:33:45 +0200 Michael Biebl <bi...@debian.org> wrote: > This was a deliberate change afaics: > https://cgit.freedesktop.org/upower/commit/?id=29c5c85f6bf2a163c8713641dba634910ee3cf49 > > Using UPowerGlib.Client.

Bug#829423: File conflict with libosinfo-1.0-0

=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) >From f3162d372bce811abb8176c856e047f258a97450 Mon Sep 17 00:00:00 2001 From: Michael Biebl <bi...@debian.org> Date: Sun, 3 Jul 2016 09:43:38 +0200 Subject: [PATCH] Mo

Bug#820641: [valac-vapi] Incorrect gtk+ 3 dependencies causing to compilation issues

Control: severity -1 important On Tue, 12 Apr 2016 09:55:09 +0200 Philip Rinn wrote: > Hi, > > indeed, very annoying. Corebird FTBFS in unstable due to this as well: > > corebird-1.2/src/widgets/BadgeRadioButton.c:106: undefined reference to >

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Am 30.06.2016 um 21:37 schrieb Eric Valette: > On 30/06/2016 21:32, Felipe Sateler wrote: >> On 30 June 2016 at 15:20, Eric Valette wrote: >>> On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello

Bug#828911: FTBFS on various architectures when generating the gtk-doc documentation

Source: tracker Version: 1.8.0-3 Severity: serious After applying the change as requested by Pino in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823268 the package FTBFS on various architectures: https://buildd.debian.org/status/package.php?p=tracker I suspect gtk-doc is not really safe

Bug#827530: [pkg-cinnamon] Bug#827507: cinnamon-settings segfaults on entering power settings applet

On Fri, 17 Jun 2016 15:21:23 +0200 Maximiliano Curia wrote: > up_client = UPowerGlib.Client() > has_lid = up_client.get_lid_is_present() > > > With the new version that snippet segfaults. I'm not well versed in the gi > internals but it seems to me that

Bug#827705: dependency loop between initscripts and sysvinit-utils causes dist-upgrade failure

On Mon, 20 Jun 2016 00:59:57 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 20.06.2016 um 00:47 schrieb Michael Biebl: > > Am 19.06.2016 um 23:39 schrieb Santiago Vila: > > > >> # apt-get upgrade > >> [...] > >> # apt-get dist-upgrade >

Bug#827639: gnome-settings-daemon: wrong owner of /run/user/1000/dconf/user causes X to freeze

Am 19.06.2016 um 01:11 schrieb Andreas Krueger: > Package: gnome-settings-daemon > Version: 3.14.2-3 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > [I am not sure against which package to file this bug report > (/var/log/messages > says

Bug#825818: gnome-terminal crash when dragging tab to another terminal

Am 14.06.2016 um 17:24 schrieb Antonio Terceiro: > Control: severity -1 grave > > On Mon, 30 May 2016 12:10:04 +0200 Riccardo Magliocchetti > wrote: >> Package: gnome-terminal >> Version: 3.20.2-1 >> Severity: important >> >> When dragging a tab to another

Bug#826366: [Pkg-utopia-maintainers] Bug#826366: Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

Thinking more about it, if we restore the /etc/resolv.conf file on stop, then there doesn't remain a good reason why NM uses a symlink in the first place and I guess upstream did have a reason why it used a distinct file in /var/run and a symlink. I guess at this point it's best to involve

Bug#826366: [Pkg-utopia-maintainers] Bug#826366: Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

Am 08.06.2016 um 11:47 schrieb Julian Gilbey: > Question: If the symlink is reverted to an empty file on stop, but the > /var/run version is kept intact, would NM pick it up again on restart, > just by recreating the symlink? Or does NM recreate the /var/run > version on startup anyway? The

Bug#826366: [Pkg-utopia-maintainers] Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

Am 05.06.2016 um 23:57 schrieb Christoph Anton Mitterer: > On Sun, 2016-06-05 at 23:44 +0200, Michael Biebl wrote: >> On remove/purge yes, it makes sense to turn it back into a real file > > but probably only if it's really a symlink to the path used by NM,.. > not e.g. when

Bug#826366: [Pkg-utopia-maintainers] Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

Hi Julian Am 05.06.2016 um 01:56 schrieb Julian Gilbey: > I have been having some problems with network-manager recently (as > reported in another bug report), so I thought I'd try out wicd > instead. I purged NM and the related packages, but wicd would not > work. I tracked down the reason:

Bug#826035: test-suite failures on 32bit architectures

Source: gnome-keyring Version: 3.20.0-2 Severity: serious Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=767122 As can be seen at https://buildd.debian.org/status/package.php?p=gnome-keyring the test-suite fails on various architectures The failing tests are

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

Control: reopen -1 Am 28.05.2016 um 20:57 schrieb Debian Bug Tracking System: > entangle seems to build fine now. > > Ubuntu's builders do not have networking access and entangle has > successfully built since November 2015. > > https://launchpad.net/ubuntu/+source/entangle/0.7.0-3 This bug

Bug#812369: rpcbind does not properly provide $portmap needed by /etc/init.d/nis

Hi On Fri, 22 Jan 2016 12:15:21 -0800 Nye Liu wrote: > /etc/init.d/nis depends on $portmap, which leads to two problems > > 1) rpcbind does not provide $portmap (only rpcbind.target) so nis/ypbind may > be >started before rpcbind > > 2) even if nis/ypbind is started AFTER

Bug#824999: src:gtk+3.0: unsatisfiable dependency on libgtk-3-common

Am 24.05.2016 um 02:15 schrieb Christoph Anton Mitterer: > Hey. > > libgtk-3-common is still missing from i386,... (but it's e.g. in > amd64)... any ideas? Or does that just take a while? Currently blocked by a cdbs regression which makes src:gtk+3.0 FTBFS, see #825135 Once that is fixed, the

Bug#824999: gtk+3.0: Architecture: all packages cannot be built

On Sun, 22 May 2016 20:27:48 +0200 Michael Biebl <bi...@debian.org> wrote: > This has been fixed in 3.20.5-2 and a corresponding upload of > adwaita-icon-theme. For completeness sake, here is the changelog gtk+3.0 (3.20.5-2) unstable; urgency=medium * Split gtk-update-icon-cache

Bug#747392: gtk+3.0 has a cycle build-depency on itself

Am 21.05.2016 um 18:56 schrieb Michael Biebl: > Maybe dropping the libgtk-3-bin dependency from adwaita-icon-theme is. > This needs someone to investigate how libgtk-3-0 behaves if there are no > cache files. After further consideration, the probably best solution is to split out /us

<    4   5   6   7   8   9   10   11   12   13   >