Bug#824868: gtk+3.0: FTBFS: cp: cannot stat 'AUTHORSREADME': No such file or directory

Control: reassign -1 cdbs Control: reassign 824831 cdbs Control: forcemerge 824831 -1 Control: found -1 0.4.133 Control: fixed -1 0.4.137 Am 20.05.2016 um 17:52 schrieb Daniel Schepler: > Source: gtk+3.0 > Version: 3.20.4-1 > Severity: serious > X-Debbugs-CC: CDBS Hackers

Bug#824831: gtkspell3: FTBFS: cp: cannot stat './AUTHORSREADME': No such file or directory

Am 20.05.2016 um 13:17 schrieb Jonas Smedegaard: > Quoting Jonas Smedegaard (2016-05-20 12:59:21) >> Quoting Emilio Pozuelo Monfort (2016-05-20 12:38:11) >>> Looks like in the past this called: >>> >>> dh_installdocs -plibgtkspell3-3-0 ./README ./AUTHORS >>> dh_installdocs -plibgtkspell3-3-dev

Bug#824704: Needs to be updated for gnome-shell 3.20

Control: reassign -1 gnome-shell-extension-redshift 3.18.1-1 Re-assigning to the correct package name On Wed, 18 May 2016 22:50:03 +0200 Michael Biebl <bi...@debian.org> wrote: > Package: gnome-shell-extenstion-redshift > Version: 3.18.1-1 > Severity: serious > > Hi, >

Bug#824704: Needs to be updated for gnome-shell 3.20

Package: gnome-shell-extenstion-redshift Version: 3.18.1-1 Severity: serious Hi, gnome-shell has been updated to version 3.20 in unstable. Your package declares a dependency on gnome-shell << 3.19 and is therefor no longer installable. Please update gnome-shell-extension-redshift to support

Bug#808866: (snappy:15699): Clutter-CRITICAL **: The Clutter backend is not a X11 backend

On Wed, 23 Dec 2015 23:40:59 +0100 Julian Andres Klode wrote: > Package: snappy > Severity: grave > > Trying to run snappy just fails: > > (snappy:15699): GLib-GObject-CRITICAL **: g_object_set: assertion > 'G_IS_OBJECT (object)' failed > No media set. You can drag and drop a

Bug#824585: libgnomekbd: FTBFS: find: 'doc': No such file or directory

Control: reassign -1 cdbs 0.4.132 Hi Chris, thanks for your bug report. This is a regression in cdbs, thus reassigning. Am 17.05.2016 um 21:04 schrieb Chris Lamb: > dpkg-buildpackage: info: source package libgnomekbd > dpkg-buildpackage: info: source version 3.6.0-1 > dpkg-buildpackage:

Bug#822529: gdm3: retries to often / to fast on errors

Control: tags -1 moreinfo On Fri, 6 May 2016 16:52:33 +0200 Laurent Bigonville wrote: > Do you think it's a regression from 3.18? TBH, I think I already saw > this behavior in the past. Tobias, can you please answer this question, i.e. try 3.18 from testing and see if that

Bug#819096: Frequent hangs/crashes when changing network configuration

Control: severity -1 important Hi Ben On Fri, 25 Mar 2016 08:50:04 + Simon McVittie wrote: > On Wed, 23 Mar 2016 at 15:48:33 +, Ben Hutchings wrote: > > If I change the network configuration through the right hand menu in > > GNOME Shell it may hang for 10 seconds or

Bug#816739: rsyslog-gnutls: imtcp/TLS hangs on dropped packages

On Thu, 10 Mar 2016 17:23:50 +0100 Luca BRUNO wrote: > On Wednesday, March 09, 2016 09:09:42 PM you wrote: > > > I don't have the setup to test this. So if you want to see this fixed in > > stable, it would be great if you can apply the upstream fix on top of > > 8.4.2 and test

Bug#808518: Please port to clutter-gst-3.0

Am 16.05.2016 um 15:47 schrieb Michael Biebl: > Fwiw, there is a new upstream release 1.0.0 available which has been > ported to clutter-3.0 [1] Small correction: version 1.0.0 does not contain that commit as can be seen at https://git.gnome.org/browse/snappy/log/ Based on 1.0.0, it

Bug#824426: FTBFS against libical2

Source: syncevolution Version: 1.4.99.4-5 Severity: serious Hi, during the libical transition [1], your package syncevolution was rebuilt and it now FTBFS: libtool: link: g++ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0

Bug#803415: FTBFS: test-suite fails on various architectures in testCallbackTransferFull

Control: severity -1 important I've decided to make the test-suite failures non-fatal again, as gjs was blocking important updates in other packages from reaching testing. Thus downgrading the severity. We currently also have another, gobject-introspection 1.48 related, regression in gjs:

Bug#822790: FTBFS with gtk >= 3.20

Source: gnome-dictionary Version: 3.20.0-1 Severity: serious Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=765674 gnome-dictionary requires gtk+ >= 3.20 for gdk_seat_get_pointer() and gdk-display-get-default-seat() Otherwise it will FTBFS like on mipsel

Bug#820785: transmission: FTBFS: m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: glib_DEFUN

Am 27.04.2016 um 16:02 schrieb Sandro Tosi: > On Mon, Apr 25, 2016 at 6:23 PM, Michael Biebl <bi...@debian.org> wrote: >> This was apparently triggered by a change in libglib2.0-dev. > > thanks Michael to check this! is there any preferred way to address it > or should w

Bug#822657: gnome-music: Crash at launch

Control: severity -1 serious Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=765598 Am 26.04.2016 um 09:19 schrieb Ognyan Kulev: > Package: gnome-music > Version: 3.20.0-2 > Justification: renders package unusable > Severity: grave > > After upgrading gnome-music from 3.18 to

Bug#820785: transmission: FTBFS: m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: glib_DEFUN

This was apparently triggered by a change in libglib2.0-dev. Chris, do you have an idea how many packages are affected? Have you done a full archive rebuild since 23 Mar 2016, when glib20 2.48.0-1 was uploaded to unstable? Regards, Michael -- Why is it that all of the instruments seeking

Bug#821274: libsoup2.4-1: 2.54 upgrade breaks caldav/webdav support in evolution

Am 17.04.2016 um 19:16 schrieb Alban Browaeys: > Package: libsoup2.4 > Version: 2.54.0.1-1 > Followup-For: Bug #821274 > > Dear Maintainer, > There caldav is broken too. > > "CALDAV_DEBUG=all /usr/lib/evolution/evolution-calendar-factory" , when I > enable a caldav source back in the evolution

Bug#819682: libpwquality-tools: package should depend on cracklib-runtime

Control: severity -1 normla Control: tags -1 + moreinfo unreproducible On Fri, 01 Apr 2016 03:04:25 +0800 sharuzzaman wrote: > Package: libpwquality-tools > Version: 1.2.3-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > 1. install

Bug#821865: FTBFS on various architectures with -Werror=format-security

Source: totem Version: 3.20.1-1 Severity: serious totem FTBFS on various architectures https://buildd.debian.org/status/package.php?p=totem Those build failures are caused by -Werror=format-security -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy:

Bug#821863: Do not release with stretch

Source: liboobs Version: 3.0.0-2 Severity: serious liboobs is dead and no longer maintained properly (upstream and downstream) We shouldn't release stretch with this package, so I'm filing this RC bug. Eventually we should remove it from the archive completely. -- System Information: Debian

Bug#821862: Do not release with stretch

Source: system-tools-backends Version: 2.10.2-2 Severity: serious system-tools-backends is dead and no longer maintained properly (upstream and downstream) We shouldn't release stretch with this package, so I'm filing this RC bug. Eventually we should remove it from the archive completely. --

Bug#816530: gnome-logs: FTBFS: ? tag-missing : not specified

Version: 3.20.1-1 Package is building fine now, see [1], so I'm closing this bug report. Regards, Michael [1] https://buildd.debian.org/status/package.php?p=gnome-logs -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#821857: FTBFS with gtk+ < 3.20

Source: gnome-contacts Version: 3.19.91-1 Severity: serious Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=765147 gnome-contacts needs gtk+ >= 3.20 to compile successfully See https://buildd.debian.org/status/fetch.php?pkg=gnome-contacts=mipsel=3.19.91-1=1461065031 -- System

Bug#821337: FTBFS on mipsel(64), gtk+3.0-3.20.3/testsuite/reftests/button-wrapping.ui: FAIL

Hi mips(el) porters, we currently have a test-suite failure on mips(64)el for gtk+3.0 3.20 where we could use your help to track this down, as this will block the GNOME 3.20 transition. I've also forwarded this upstream [1] Thanks, Michael On Sun, 17 Apr 2016 21:39:35 +0200 Michael Biebl <

Bug#803104: yelp: FTBFS: Segmentation fault

Control: severity -1 important Control: yelp: FTBFS: Segmentation fault in gtk-doc if no $DISPLAY I've disabled the gtk-doc generation during build and we use the pre-generated files shipped by upstream for now. I'll keep this bug open as I want to switch on --enable-gtk-doc at some point when

Bug#803104: yelp: FTBFS: Segmentation fault

On Mon, 26 Oct 2015 21:50:40 + Chris Lamb wrote: > yelp fails to build from source in unstable/amd64. (Whilst it segfaults, > I think this actually is due to the lack of an $DISPLAY - see the > warnings. Perhaps something like xvfb is needed?) > > [..] > >

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

Control: reassign -1 yelp-tools Control: found -1 3.18.0-1 Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=765215 On Sun, 14 Jun 2015 21:19:42 + "Chris West \(Faux\)" wrote: > Source: entangle > Version: 0.7.0-3 > Severity: important > > Dear

Bug#821274: libsoup2.4-1: 2.54 upgrade breaks caldav/webdav support in evolution

Am 17.04.2016 um 20:24 schrieb Michael Biebl: >>> I've tried downgrading the packages to 2.52 and it does fix the problem. >>> It might be an issue in evolution requiring a binNMU or even a patch, no >>> idea, so feel free to reassign if needed. .. > Downgradin

Bug#821347: FTBFS on mipsel and s390x: test suite failures

Source: libsecret Version: 0.18.5-1 Severity: serious libsecret has test suite failure ons mipsel and s390x [1] mipsel: FAIL: test-session 4 /session/ensure-async-aes FAIL: test-collection 18 /collection/delete-sync s390x: FAIL: test-collection 18 /collection/delete-sync the build gets stuck

Bug#821337: FTBFS on mipsel(64), gtk+3.0-3.20.3/testsuite/reftests/button-wrapping.ui: FAIL

Source: gtk+3.0 Version: 3.20.3-1 Severity: serious The package FTBFS on mips(el). The test-suite on fails in gtk-reftest, specifically gtk+3.0-3.20.3/testsuite/reftests/button-wrapping.ui: FAIL This seems to happen reproducibly, also on porterboxes (tried on etler). I haven't further

Bug#821122: [libgtk-3-dev] Missing dependencies accordingly to pkg-config

Control: reassign -1 libgdk-pixbuf2.0-dev Control: forcemerge 819779 -1 Am 15.04.2016 um 20:53 schrieb Alexandre Pereira Nunes: > Removing -L /usr/lib/x86_64-linux-gnu from libs for gmodule-no-export-2.0 > Searching for 'gdk-pixbuf-2.0' private requirement 'libpng16' > Looking for package

Bug#821122: [libgtk-3-dev] Missing dependencies accordingly to pkg-config

Am 15.04.2016 um 20:34 schrieb Alexandre Pereira Nunes: > Package: libgtk-3-dev > Version: 3.18.9-1 > Severity: grave > > $ pkg-config gtk+-3.0 --cflags > > Package libpng16 was not found in the pkg-config search path. > Perhaps you should add the directory containing `libpng16.pc' > to the

Bug#819779: gdk-pixbuf: libgdk-pixbuf2.0-dev depends on libpng-dev but gdk-pixbuf2.0.pc requires libpng12-dev

Am 14.04.2016 um 14:16 schrieb peter green: >> >> * ships a gdk-pixbuf2.0.pc that requires libpng12.pc; >> * depends on libpng-dev which: >>- on experimental, is a real package that does not ship libpng12.pc >> but only libpng16.pc and libpng.pc; >>- on unstable, is provided by

Bug#820568: tracker: searches fail with "no such module: fts5"

Control: severity -1 normal Am 10.04.2016 um 03:48 schrieb Sam Morris: > Package: tracker > Version: 1.8.0-2 > Severity: grave > Justification: renders package unusable > > Searches fail with the following error: > > $ tracker search test > Could not get search results, no such

Bug#820095: Bug: libgdk-pixbuf2.0-dev: Please relax dependency with

Am 05.04.2016 um 15:13 schrieb Hideki Yamane: > On Tue, 5 Apr 2016 14:38:10 +0200 Rene Engelhard wrote: >> No, this is wrong, and still would get the build failure. >> >> The correct solution iy to make gdk-pixbuf mention libpng.pc in Requires, >> which would work for both 12

Bug#819975: Fails to start

Package: gnome-characters Version: 3.20.0-1 Severity: grave Since the upgrade to 3.20.0, gnome-characters fails to start. There is no output on stdout/stderr, but in the journal I get: Apr 04 15:27:13 pluto org.gnome.Characters[2091]: (org.gnome.Characters:12455): Gjs-WARNING **: JS ERROR:

Bug#819886: gtk-doc-tools: /usr/bin/gtkdoc-mkpdf always exits with an error

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=764543 Hi Andreas, thanks for your bug report. Am 03.04.2016 um 15:54 schrieb Andreas Metzler: > So cleanexit() is supposed to take an exitcode as argument but ignores it and > exits with 1 instead. Obviously the function

Bug#819779: gdk-pixbuf: libgdk-pixbuf2.0-dev depends on libpng-dev but gdk-pixbuf2.0.pc requires libpng12-dev

Am 03.04.2016 um 09:49 schrieb Gianfranco Costamagna: > control: severity -1 important > > Hi Tanguy, sorry for the late reply > > On 02/04/2016 10:41, Tanguy Ortoo wrote: >> Package: libgdk-pixbuf2.0-dev >> Version: 2.32.3-1.2 >> Severity: grave >> Justification: renders package unusable >> >

Bug#819779: marked as done (gdk-pixbuf: libgdk-pixbuf2.0-dev depends on libpng-dev but gdk-pixbuf2.0.pc requires libpng12-dev)

Am 02.04.2016 um 12:39 schrieb Debian Bug Tracking System: > As discussed on IRC the problem you're experiencing is a pbuilder > bug and not an issue in the package itself. I don't think this is the case and there is a genuine bug. The libpng version gdk-pixbuf was compiled against, is encoded in

Bug#812469: gedit is failing to start: ERROR:../../gi/pygi-cache.c:338:_arg_cache_new_for_interface: code should not be reached

Control: severity -1 important Control: tags -1 unreproducible On Sun, 24 Jan 2016 13:14:01 +0530 Pirate Praveen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > package: gedit > version: 3.18.3-1 > severity: grave > justification: makes it unusable > > >

Bug#816739: rsyslog-gnutls: imtcp/TLS hangs on dropped packages

Am 04.03.2016 um 17:45 schrieb Luca Bruno: > Package: rsyslog-gnutls > Version: 8.4.2-1+deb8u2 > Severity: grave > Tags: patch upstream > Justification: causes non-serious data loss > > I have a log-aggregating server using rsyslog to receive multiple > streams (both UDP and TCP), including some

Bug#815020: breaks coredump handling for systems without systemd-coredump

Am 19.02.2016 um 05:32 schrieb Josh Triplett: > severity 815020 grave > thanks > > On Wed, 17 Feb 2016 21:25:43 -0300 Felipe Sateler wrote: >> On 17 February 2016 at 21:03, Wouter Verhelst wrote: >>> An alternative solution would be that systemd-sysv

Bug#815056: libtesseract4: fails to upgrade from libtesseract3

On Thu, 18 Feb 2016 11:09:04 +0100 IOhannes m zmoelnig wrote: > Package: libtesseract4 > Version: 3.04.01-1 > Severity: serious > Justification: Policy 7.4 > > Dear Maintainer, > > libtesseract4 provides at least one identical file as libtesseract3 without > declaring a

Bug#814365: Xorg.0.log in question

Control: severity -1 normal Control: reassign -1 xserver-xorg-core Am 10.02.2016 um 22:09 schrieb Send Me: > [ 4033.331] (II) UnloadModule: "evdev" > [ 4033.331] (II) systemd-logind: releasing fd for 13:78 > [ 4033.331] (EE) systemd-logind: failed to release device: Connection is > closed > [

Bug#812371: nis: NIS is started before rpcbind since rpcbind was migrated to systemd

On Fri, 22 Jan 2016 13:03:00 -0800 Nye Liu wrote: > For some reason, even though $portmap is mentioned in /etc/init.d/nis as a > start prereq, ypbind is started BEFORE rpcbind. > > This causes ypbind to NEVER properly start, and the bind_wait obviously cannot > ever succeed. > >>

Bug#813297: gdm3: gdm is crashing and does not auto-start on system boot

Control: severity -1 important Am 31.01.2016 um 11:24 schrieb Rigved Rakshit: > Package: gdm3 > Version: 3.18.2-1 > Severity: grave > Justification: gdm is unusable > > Dear Maintainer, > > The following was tested on Oracle VirtualBox 4.3.18. > > Steps to reproduce: > 1. Install Jessie base

Bug#812863: udev: Postinst crashes when group input already exists.

Am 27.01.2016 um 11:59 schrieb Rogier Wolff: > Package: udev > Version: 204-5ubuntu20.15 > Severity: serious > Justification: Policy 2.3.4 > -- IRRELEVANT: reporting system != bug system --- Please don't do that. Now we don't know which version exactly is installed. Which

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

Am 21.01.2016 um 04:53 schrieb Christoph Anton Mitterer: > though. E.g. I wouldn't want to have everyone-may-access-everything Since Christoph Anton Mitterer keeps repeating that, I want to make sure that everyone else reading this bug report is aware that this is *not* true. With the default

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

Am 21.01.2016 um 04:18 schrieb Christoph Anton Mitterer: > On Thu, 2016-01-21 at 04:13 +0100, Michael Biebl wrote: >> This behaviour has been since 2000 or so, since at least the >> introduction of hal and pmount. > > Then one has still some 30 years before where it has bee

Bug#811662: init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d

Control: clone -1 Control: reassign -1 openrc Am 20.01.2016 um 01:46 schrieb Adam Borowski: > Package: init-system-helpers > Version: 1.25 > Severity: serious > Justification: Policy 7.4 > > Hi! > > Unpacking init-system-helpers (1.25) over (1.24) ... > dpkg: error processing archive >

Bug#811367: [systemd] Broken input in X11 after logging out

Control: severity -1 important Control: tags -1 moreinfo Am 18.01.2016 um 12:02 schrieb Alexey Feldgendler: > --- Please enter the report below this line. --- > I use slim as the graphical login manager. After boot, X11 starts, and > I can log in using slim's graphical login screen. > After

Bug#788729: closed by Michael Biebl <bi...@debian.org> (Re: [src:libgda5] Some sources are not included in your package)

Am 17.01.2016 um 14:52 schrieb roucaries bastien: > No see http://sources.debian.net/src/libgda4/4.0.12-1/tools/jquery.js/ > > Corrected at build time see debian/rules, but you need a repack Nah, got more important things to do then pointless repacks which make no practical difference. --

Bug#808151: systemd: failed to start remount root and kernel file system

Control: severity -1 important After further consideration, I'm downgrading this bug to important. It only happens for split-usr setups and is apparently hard to trigger, i.e. happens rarely due to race conditions. -- Why is it that all of the instruments seeking intelligent life in the

Bug#802095: libpeas: FTBFS: PyGIWarning: Peas was imported without specifying a version first.

Control: severity -1 important No further information was provided, thus downgrading the severity, as the issue is not reproducible here. On Fri, 13 Nov 2015 02:08:18 +0100 Michael Biebl <bi...@debian.org> wrote: > I tried to reproduce the build failure within an up-to-date amd64 sid &

Bug#810748: systemd does not mount /usr in initramfs, breaking split /usr

Control: severity -1 important Control: tags -1 + moreinfo Am 14.01.2016 um 00:04 schrieb Nis Martensen: >> If I read the code correctly, than this patch is the culprit: >>

Bug#810748: systemd does not mount /usr in initramfs, breaking split /usr

Am 14.01.2016 um 00:04 schrieb Nis Martensen: > If I read the code correctly, than this patch is the culprit: > http://sources.debian.net/src/systemd/215-17%2Bdeb8u2/debian/patches/Skip-filesystem-check-if-already-done-by-the-initram.patch/?hl=29#L29 > > When systemd is run in the initramfs

Bug#810785: ifupdown breaks debootstrap of Debian

Am 12.01.2016 um 10:23 schrieb Raphaël Hertzog: > The problem is that stretch still has systemd 228-2 and 228-4 is unlikely > to migrate quickly since it just got updated and seems to have a new RC bug. > > I'm not sure what's the best way forward... possibly upload something to >

Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

Am 09.01.2016 um 16:28 schrieb Martin Pitt: > Control: tag -1 pending > > Andreas Beckmann [2016-01-08 11:52 +0100]: >> Why can't this be fixed in a jessie point release? > > It can, but we can't guarantee that the jessie update will be > installed before dist-upgrading to wheezy. Right. >> So

Bug#809903: (no subject)

Control: tags -1 + moreinfo Hello Ian, your bug report doesn't contain anything. Can you please elaborate what your problem is. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP

Bug#808151: systemd: failed to start remount root and kernel file system

Am 05.01.2016 um 00:58 schrieb Michael Biebl: > Am 03.01.2016 um 16:21 schrieb Martin Pitt: >> https://github.com/systemd/systemd/commit/9d06297e26 >> >> Frank, Michael, if possible, it would be nice if you could confirm >> that this really fixes your case as well? &g

Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

Am 03.01.2016 um 17:11 schrieb 積丹尼 Dan Jacobson: > Package: udev > Version: 228-3 > Severity: grave > > Package installation Race Condition? Also filed bug 809743. > > Unpacking libpam-systemd:i386 (228-3) over (228-2+b1) ... > dpkg: considering deconfiguration of ifupdown, which would be broken

Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

Am 03.01.2016 um 18:22 schrieb 積丹尼 Dan Jacobson: >>>>>> "MB" == Michael Biebl <bi...@debian.org> writes: > MB> We can't unfortunately fix the existing udev.prerm of older versions, > MB> only make sure the new one no longer has the problem. > >

Bug#783297: [pkg-cryptsetup-devel] Bug#783297: breaks initramfs if BUSYBOX=n

Am 25.12.2015 um 14:46 schrieb Jonas Meurer: > Am 26.04.2015 um 01:35 schrieb Michael Biebl: >> On Sat, 25 Apr 2015 16:22:13 +0200 Michael Biebl <bi...@debian.org> wrote: >>> if the cryptsetup package is installed, it also installed a >>> initramfs-

Bug#808573: [Pkg-utopia-maintainers] Bug#808573: network-manager: undefined symbol: g_udev_enumerator_new

Am 21.12.2015 um 06:08 schrieb Mike Dupont: > /usr/sbin/NetworkManager --no-daemon > /usr/sbin/NetworkManager: symbol lookup error: > /usr/sbin/NetworkManager: undefined symbol: g_udev_enumerator_new Please send me the output from ldd /usr/sbin/NetworkManager -- Why is it that all of the

Bug#808289: proposed RM: upstart -- RoQA; unmaintained

On Fri, 18 Dec 2015 12:25:50 +0100 Ansgar Burchardt wrote: > I therefore suggest to remove the package. > > If there are no objections, I'll reassign this bug report to ftp.d.o in > a week or so. I'm not going to comment on whether to remove upstart or not. But if you do,

Bug#805640: clutter-gst-2.0: don't release with stretch

On Fri, 20 Nov 2015 15:53:28 +0100 Emilio Pozuelo Monfort wrote: > Source: clutter-gst-2.0 > Severity: serious > > Now that we have clutter-gst-3.0, we should remove clutter-gst-2.0 > before stretch is released. This bug should remind us about that. I've cherry-picked a patch

Bug#808151: systemd: failed to start remount root and kernel file system

Am 19.12.2015 um 16:27 schrieb Frank B. Brokken: > Dear Michael Biebl, you wrote: > >>> This information is available at https://www.icce.rug.nl/systemd in the >>> files >>> initramfs.debug and alb. >> >> Hm, unfortunately the journal dump is incompl

Bug#808151: systemd: failed to start remount root and kernel file system

Here is a more complete log excerpt for v228 (full log attached) > Dez 20 01:27:42 debian systemd[1]: -.mount: Changed dead -> mounted > Dez 20 01:27:42 debian systemd[1]: usr.mount: Changed dead -> mounted > Dez 20 01:27:42 debian systemd[1]: usr.mount: Unit is bound to inactive unit >

Bug#808151: systemd: failed to start remount root and kernel file system

Am 19.12.2015 um 12:40 schrieb Frank B. Brokken: > Dear Michael Biebl, you wrote: >> If you downgrade systemd/udev, does the problem go away? > > As I feared, downgrading is difficult because of the many reverse > dependencies. > > I looked at > > ftp://ftp.

Bug#808151: systemd: failed to start remount root and kernel file system

Am 19.12.2015 um 13:06 schrieb Frank B. Brokken: > Hi Michael, > > As announced in my previous e-mail: > >> I'll add the debug entry next (cf. your mail from Date: Fri, 18 Dec 2015 >> 03:15:15 +0100) and let you know the results. > > This information is available at

Bug#808151: systemd: failed to start remount root and kernel file system

Am 18.12.2015 um 13:34 schrieb Frank B. Brokken: >> I'm a bit confused by those logs. They show that sda5 have been mounted. >> >> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounting >> ext3 file system using the ext4 subsystem >> Dec 17 15:44:29 localhost.localdomain kernel:

Bug#808151: systemd: failed to start remount root and kernel file system

Am 18.12.2015 um 15:59 schrieb Frank B. Brokken: > Is there a way to determine that? What I do to upgrade the system is run > 'aptitude update' and then 'aptitude upgrade'. Is there a log somewhere that > tells me what packages and versions were updated at what moments in time? /var/log/dpkg.log

Bug#808305: Missing fwupd breaks upgrade functionality

Package: gnome-software Version: 3.18.3-2 Severity: serious Since upgrading to the version which enabled fwupd support, the upgrade functionality is broken when fwupd is not installed. I no longer get any notifications when new packages are awailable and when opening the Updates tab in the main

Bug#801156: marked as pending

Hi Guillem, Am 04.12.2015 um 03:25 schrieb Guillem Jover: > Hi! > > On Thu, 2015-11-26 at 04:54:50 +0100, Guillem Jover wrote: >> On Wed, 2015-11-25 at 00:59:25 +0100, Michael Biebl wrote: >>> I just encountered another instance of this issue. >>> While preparin

Bug#808361: FTBFS due to too loose build-depends

Source: python-letsencrypt Version: 0.1.1-1 Severity: serious The latest upload FTBFS [1]. Looking at the build log, python-acme 0.1.0-3 was installed and it looks like it actually needs python-acme >= 0.1.1: No local packages or download links found for acme==0.1.1 error: Could not find

Bug#808361: FTBFS due to too loose build-depends

Am 19.12.2015 um 02:05 schrieb Michael Biebl: > Source: python-letsencrypt > Version: 0.1.1-1 > Severity: serious > > The latest upload FTBFS [1]. > > Looking at the build log, python-acme 0.1.0-3 was installed and it looks > like it actually needs python-acme >=

Bug#808151: systemd: failed to start remount root and kernel file system

Am 17.12.2015 um 13:46 schrieb Frank B. Brokken: > Dear Michael Biebl, you wrote: > >> What happens afterwards? Are you dropped into the rescue shell? > > Afterwards (i.e., after the initial failure message) the system tries to > continue booting, but shows lots of failure

Bug#808151: systemd: failed to start remount root and kernel file system

Am 17.12.2015 um 16:24 schrieb Frank B. Brokken: > This time the debug shell prompt was available at tty9, although booting > failed. And in line with my previous findings, systemd-analyze and journalctl > weren't available, as they live in /usr/bin, and /usr hadn't been mounted. But Well, /usr

Bug#808151: systemd: failed to start remount root and kernel file system

Am 17.12.2015 um 22:38 schrieb Michael Biebl: > Am 17.12.2015 um 16:24 schrieb Frank B. Brokken: >> This time the debug shell prompt was available at tty9, although booting >> failed. And in line with my previous findings, systemd-analyze and journalctl >> weren't available,

Bug#808151: systemd: failed to start remount root and kernel file system

Am 16.12.2015 um 15:43 schrieb Frank B. Brokken: > Package: systemd > Version: 228-2 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > >* What led up to the situation? > > Last week, Tuesday Dec. 8 I upgraded this system. One of the packages that > were

Bug#801956: totem: fails with Warning **: Element 'scaletempo' is missing

Control: severity -1 important On Fri, 13 Nov 2015 01:52:13 +0100 Michael Biebl <bi...@debian.org> wrote: > I wonder if this is related to this issue. > > The scaletempo plugin is part of gstreamer1.0-plugins-good. > Can you attach the output of "gst-inspect-1.0 audiof

Bug#807617: FTBFS due to test-suite failures

Source: ifupdown Version: 0.8.2 Severity: serious Since version 0.8, the test-suite basically fails on all architectures as can be seen at https://buildd.debian.org/status/package.php?p=ifupdown=unstable I can reproduce the problem on amd64 with a pbuilder build. >From a cursory glance it looks

Bug#807281: crashes a lot

Package: librsvg2-2 Version: 2.40.12-1 Severity: grave The update from .11 to .12 causes a lot of crashes here. I noticed it due to dash-to-dock preferences no longer working [1] This is apparently caused by librsvg. The attached .svg can be used to make nautilus crash if the folder containing

Bug#805565: [Pkg-utopia-maintainers] Bug#805565: network-manager: ppp new upstream release; dh_ppp

Hi Am 04.12.2015 um 10:06 schrieb Chris Boot: > Control: severity serious > > Hi Michael, > > I have now uploaded ppp 2.4.7-1+1 to unstable, therefore the ppp plugin > this package ships is now broken in sid. Please upload a patched version > of your package as soon as possible. > > I would

Bug#806922: systemctl do not work for non-root

Control: severity -1 normal Control: tags -1 moreinfo Hi Am 03.12.2015 um 03:02 schrieb Juhapekka Tolvanen: > > juhtolv@heresy | to 03 joulu 2015 03:52:26 | 1 | pts/1.1 > /home/juhtolv > % systemctl --user status --all > Failed to get D-Bus connection: Yhteys torjuttu What's the output

Bug#801156: marked as pending

Hi Guillem! On Sun, 18 Oct 2015 03:40:50 + Guillem Jover wrote: > Control: tag 801156 pending > > Hi! > > Bug #801156 reported by you has been fixed in the Git repository. You can > see the changelog below, and you can check the diff of the fix at: > >

Bug#805642: avrdude: version 6.2. ser_open(): can't set attributes for device

Am 20.11.2015 um 17:40 schrieb Michael Biebl: > I have to admit I no longer have any hardware to test avrdude against. > I probably should give it up for adoption to someone who can. I went ahead and did just that: If anyone is interested in maintaining avrdude and can reasonabl

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

Am 19.11.2015 um 14:29 schrieb Felipe Sateler: > Control: tags -1 moreinfo > > On 19 November 2015 at 09:59, Lorenz Hübschle-Schneider > wrote: >> Package: systemd >> Version: 228-1 >> Severity: critical >> Justification: breaks the whole system >> >> Dear Maintainer,

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

Am 19.11.2015 um 15:16 schrieb Michael Biebl: > I can confirm, that with 227, "v /home" does not trigger a mount request > and with 228 "Q /home" does. Both q and Q trigger a mount request. -- Why is it that all of the instruments seeking intelligent life in the univ

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

Control: forwarded -1 https://github.com/systemd/systemd/issues/1959 Am 19.11.2015 um 15:18 schrieb Michael Biebl: > Am 19.11.2015 um 15:16 schrieb Michael Biebl: >> I can confirm, that with 227, "v /home" does not trigger a mount request >> and with 228 "Q /home&qu

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

Am 19.11.2015 um 14:54 schrieb Lorenz Hübschle-Schneider: > I will try re-upgrading later this afternoon and let it run for a longer > time, but the message was "$x sec / no limit". > > Felipe, are you referring to /usr/lib/tmpfiles.d/home.conf? I will try that > out as well. > > With a normal

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

Control: severity -1 important Am 19.11.2015 um 15:16 schrieb Michael Biebl: > Btw, how do you configure your network? NetworkManager or ifupdown? I tried with NetworkManager. This resulted in systemd-tmpfiles-setup.service and srv.mount failing during boot (I setup /srv as NFS automo

Bug#805481: One important omission

Hi Steve, Am 18.11.2015 um 16:52 schrieb Steven Capper: > I neglected to mention that this running under a QEMU virtual machine (same > error for both KVM acceleration on and off). > > I will dig into this a little bit here and will update if I find anything. Can you pinpoint the version when

Bug#805481: One important omission

Am 18.11.2015 um 18:35 schrieb Steven Capper: > Upgrading to 227-1 caused immediate segfaults and led to the same > unbootable machine. > > So it looks like something introduced 227-1. I would guess this was introduced by

Bug#805042: journal is killed every minute by watchdog

Am 13.11.2015 um 18:29 schrieb Michael Biebl: > Might be an incomplete fix for #1505 and maybe we need something like > https://github.com/systemd/systemd/issues/1804 I don't get this issue with daily build from trunk-ci. So I'm not sure if it's worth investigating further and

Bug#800496: evolution-ews: Unable to store Host URI / OAB URI

On Wed, 30 Sep 2015 09:13:36 +0200 Yusuf Iskenderoglu wrote: > Package: evolution-ews > Version: 3.16.3-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Currently, evolution cannot access EWS anymore and prevents me from using > company

Bug#804056: Re: Bug#804056: Systemd

Control: severity -1 important Since we didn't get any further feedback, I'm downgrading to important for now Am 05.11.2015 um 13:41 schrieb Felipe Sateler: > (Please keep the bug on CC) > > On 5 November 2015 at 08:10, mila_s wrote: >> Great Thankx! >> >> I am not registered

Bug#804908: service is not started under systemd

Am 12.11.2015 um 20:19 schrieb Michael Biebl: > That is a symlink though, which is only created if the user explicitly > runs "systemctl enable --user obex.service", which in my case will > result in > Created symlink from > /home/michael/.config/systemd/user/dbus-org.blu

Bug#800585: cheese does not specify all dependencies it require

Version: 3.18.1-2 On Thu, 1 Oct 2015 14:41:14 +0530 Pirate Praveen wrote: > package: cheese > version: 3.16.1-1 > severity: grave > reason: makes it unusable for its primary purpose > > When I start cheese, I get the following error > > Error during camera setup: One or more

Bug#803013: systemd should not destroy application created cgroups

Am 12.11.2015 um 22:29 schrieb Michael Biebl: > I would suggest that you raise this upstream at > https://github.com/systemd/issues/new, as it is not really Debian specific. Sorry, wrong URL: https://github.com/systemd/systemd/issues/new -- Why is it that all of the instruments s

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