Processed: libopenraw1v5: Try to overwrite file in libopenraw1

Processing commands for cont...@bugs.debian.org: > owner 802471 s...@debian.org Bug #802471 [libopenraw1v5] libopenraw1v5: Try to overwrite file in libopenraw1 Bug #802590 [libopenraw1v5] cannot upgrade from libopenraw1 to libopenraw1v5 Owner recorded as s...@debian.org. Owner recorded as

Processed: Re: Bug#801598: nvidia-graphics-drivers: nvidia devices created with permissions 0666 on boot

Processing control commands: > severity -1 normal Bug #801598 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: nvidia devices created with permissions 0666 on boot Severity set to 'normal' from 'serious' -- 801598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801598 Debian Bug

Bug#801598: nvidia-graphics-drivers: nvidia devices created with permissions 0666 on boot

Control: severity -1 normal On 2015-10-12 13:53, Andreas Beckmann wrote: > Even though /etc/modprobe.d/nvidia-kernel-common.conf sets the > permissions and owner to root:video 0660, the devices are created > acessible by all local users: root:root 0666. I've reverted back to upstreams default

Processed: Re: Bug#801598: nvidia-graphics-drivers: nvidia devices created with permissions 0666 on boot

Processing control commands: > severity -1 normal Bug #801869 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: setting /dev/nvidia* to root:video 0660 breaks gdm3, sddm, ... Severity set to 'normal' from 'serious' -- 801869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801869 Debian

Bug#801844: [systemd] Sudden Unbootable System

Am 18.10.2015 um 11:02 schrieb David Baron: > Spontaneously gave it a try today and ... it > booted successfully! > > Did have an "invalid mount point" error up > front but does not show on journalctl or > dmesg. > Please provide full error messages in context. If necessary take a

Bug#802318: scoop: FTBFS: test break on Python 3.5 in reproducible builds CI

Control: severity -1 normal Since current Scoop now builds again in reproducible builds CI I'm lowering the severity of this bug. Nevertheless, it may be that something which can be improved has been triggered, so I leave it open. DS -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4

Processed: scoop: FTBFS: test break on Python 3.5 in reproducible builds CI

Processing control commands: > severity -1 normal Bug #802318 [src:scoop] scoop: FTBFS: test break on Python 3.5 in reproducible builds CI Severity set to 'normal' from 'serious' -- 802318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802318 Debian Bug Tracking System Contact

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

On Wed, Oct 21, 2015 at 16:10:50 -0700, Scott Mcdermott wrote: > Julien Cristau on 2015/10/21 +0200 @20:48:56: > > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > > > > > This upgrade has broken X startup for me. Here is how > > > I start X (as ordinary user): > > > > > > exec setsid

Bug#799948: Plasma desktop is unable to start (black screen - panic)

On Tue, Oct 20, 2015 at 11:31:05PM +0100, Luca Boccassi wrote: > Could you please make sure that both your user and your DM user (sddm I > believe?) are in the video group and try again and report the result? Yes, this solves the problem, but it is ridiculous. First of all it is security

Bug#802611: subversion: Core dump of "svn diff -c 102".

Package: subversion Version: 1.9.2-1 Severity: serious 100% reproduced. bash# svn diff -c 109 Segmentation fault (core dumped) bash# gdb /usr/bin/svn core GNU gdb (Debian 7.10-1) 7.10 This GDB was configured as "x86_64-linux-gnu". Reading symbols from /usr/bin/svn...Reading symbols from

Bug#799948: Plasma desktop is unable to start (black screen - panic)

On 21 October 2015 at 17:15, Vladimir Stavrinov wrote: > OK, but what happened recently with 0.6.x version? Do You want to > say, that ordinary user always had had write access to nvidia device? Yes. That is what we were trying to fix: device nodes are created by default by

Bug#799948: Plasma desktop is unable to start (black screen - panic)

On 2015-10-21 17:39, Vladimir Stavrinov wrote: > explains nothing about this. There are no answer to the question: > what for glx requires write access to video device for normal live > user? This is something new in world fashion. Why only glx require > this? How do other video works without

Bug#802611: Updating from 1.9.2-1 to 1.9.2-2 doesn't help, downgrading to stable 1.8.10-6+deb8u1 does.

Updating from 1.9.2-1 to 1.9.2-2 doesn't help, downgrading to stable 1.8.10-6+deb8u1 does. On 1.9.2-2 get same error: (gdb) bt #0 strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x7fe07c0da786 in svn_path_join_internal (base=0x0, component=0x7fe07d060148

Bug#801844: [systemd] Sudden Unbootable System

- Original Message -From: Michael Biebl Date: Wednesday, October 21, 2015 4:30 pmSubject: Re: Bug#801844: [systemd] Sudden Unbootable SystemTo: David Baron , 801...@bugs.debian.org> Am 18.10.2015 um 11:02 schrieb David Baron:> > Spontaneously gave

Bug#787368: marked as done ([acl2] Some sources are not included in your package)

Your message dated Wed, 21 Oct 2015 16:21:03 + with message-id and subject line Bug#787368: fixed in acl2 7.1dfsg-1 has caused the Debian Bug report #787368, regarding [acl2] Some sources are not included in your package to be marked as done. This means

Bug#799948: Plasma desktop is unable to start (black screen - panic)

On Wed, Oct 21, 2015 at 05:50:22PM +0200, Andreas Beckmann wrote: > The driver is a non-free blob. I have no clue how it works :-) Kicks nvidia ass. Non-free blob is always headache. Will it be sensitive for nvida if all Linux user will boycott them not buying their hardware? OK, but what

Bug#800923: marked as done (libcorosync-common-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/include/corosync/corodefs.h)

Your message dated Wed, 21 Oct 2015 16:21:45 + with message-id and subject line Bug#800923: fixed in corosync 2.3.5-2 has caused the Debian Bug report #800923, regarding libcorosync-common-dev: fails to upgrade from 'jessie' - trying to overwrite

Bug#802550: marked as done (x264: FTBFS on mipsel: Error: opcode not supported on this processor: mips2 (mips2) `addvi.b $w0, $w1, 1')

Your message dated Wed, 21 Oct 2015 16:27:48 + with message-id and subject line Bug#802550: fixed in x264 2:0.148.2601+gita0cd7d3-2 has caused the Debian Bug report #802550, regarding x264: FTBFS on mipsel: Error: opcode not supported on this processor:

Bug#802287: kdenlive: Kdenlive for Debian 8 fails to load

Am 19.10.2015 um 04:31 schrieb Joe McEntire: > Package: kdenlive > Version: 0.9.2-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >

Bug#796887: marked as done (libmodule-info-perl: FTBFS with perl 5.22: test failures)

Your message dated Wed, 21 Oct 2015 16:25:04 + with message-id and subject line Bug#796887: fixed in libmodule-info-perl 0.35.07-1 has caused the Debian Bug report #796887, regarding libmodule-info-perl: FTBFS with perl 5.22: test failures to be marked as

Processed: merge libopenraw

Processing commands for cont...@bugs.debian.org: > merge 802471 802590 Bug #802471 [libopenraw1v5] libopenraw1v5: Try to overwrite file in libopenraw1 Bug #802590 [libopenraw1v5] cannot upgrade from libopenraw1 to libopenraw1v5 Bug #802590 [libopenraw1v5] cannot upgrade from libopenraw1 to

Processed: tagging 787453

Processing commands for cont...@bugs.debian.org: > # tests fail under 5.22 > tags 787453 - fixed-upstream Bug #787453 [src:libdata-alias-perl] libdata-alias-perl: FTBFS with perl 5.22 Removed tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#801844: marked as done ([systemd] Sudden Unbootable System)

Your message dated Wed, 21 Oct 2015 19:10:18 +0200 with message-id <5627c6fa.50...@debian.org> and subject line Re: Bug#801844: [systemd] Sudden Unbootable System has caused the Debian Bug report #801844, regarding [systemd] Sudden Unbootable System to be marked as done. This means that you claim

Bug#802619: attic: Unrecoverable data integrity error after running out of disk space

Package: attic Version: 0.13-1 Severity: grave Tags: upstream Justification: causes data loss I ran into "attic: Error: Data integrity error" after running out of disk space. That resulted in the attic repository becoming unrecoverable and unusable. This issue has been reported upstream:

Bug#802115: marked as done (wxglade: FTBFS: ImportError: No module named setuptools)

Your message dated Wed, 21 Oct 2015 18:20:11 + with message-id and subject line Bug#802115: fixed in wxglade 0.7.1~rc1-2 has caused the Debian Bug report #802115, regarding wxglade: FTBFS: ImportError: No module named setuptools to be marked as done. This

Bug#787453: libdata-alias-perl: FTBFS with perl 5.22

Hi, I'm the Data-Alias maintainer. Data-Alias has been updated for Perl 5.22, in Data-Alias-1.19, now on CPAN. However, I've had reports from two separate users describing test failures of D-A-1.19 on vendor versions of Perl 5.22, one Debian and one Fedora. These new test failures are

Bug#802611: subversion: Core dump of "svn diff -c 102".

On Oct 21, 2015 12:00 PM, "Oleksandr Gavenko" wrote: > > 100% reproduced. > > bash# svn diff -c 109 Is this a public repository? Cheers, James

Bug#802487: aide crash (SIGSEGV) at beginning

severity 802487 important tags 802487 +unreproducible +moreinfo forcemerge 802487 776001 thanks On Tue, Oct 20, 2015 at 03:49:51PM +0200, jpp wrote: > My version af "aide" crash at beginning with a SIGSEGV, even if I try "aide > --help'. I tried to reproduce this on a fresh minimal Debian wheezy

Bug#799948: Plasma desktop is unable to start (black screen - panic)

On Wed, Oct 21, 2015 at 05:34:32PM +0100, Luca Boccassi wrote: > default by upstream (and by udev) with 666 permissions, so world I hate such gys. They want more: 777. They say: "give me 777 and everything will work. They don't need any other user than root. This is microsoft heritage in mind.

Processed: block 802414 by 800788

Processing commands for cont...@bugs.debian.org: > block 802414 by 800788 Bug #802414 [src:python-requirements-detector] python-requirements-detector: FTBFS: AttributeError: 'Call' object has no attribute 'starargs' 802414 was not blocked by any bugs. 802414 was not blocking any bugs. Added

Bug#794137: marked as done (FTBFS: 56 tests fail: wrong number of arguments (0 for 1+) in `stub_status')

Your message dated Wed, 21 Oct 2015 17:19:03 + with message-id and subject line Bug#794137: fixed in atig 0.4.5-2 has caused the Debian Bug report #794137, regarding FTBFS: 56 tests fail: wrong number of arguments (0 for 1+) in `stub_status' to be marked

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

On Tue, Oct 20, 2015 at 14:46:44 -0700, Scott Mcdermott wrote: > Package: xserver-xorg-legacy > Version: 2:1.17.2-3 > Severity: grave > > I recently did an upgrade of X, which broke it on my machine. > Here are old (working) and new (broken) versions that apt-get > installed, as shown in

Processed (with 1 error): Re: Bug#802487: aide crash (SIGSEGV) at beginning

Processing commands for cont...@bugs.debian.org: > severity 802487 important Bug #802487 [aide] aide crash (SIGSEGV) at beginning Severity set to 'important' from 'grave' > tags 802487 +unreproducible +moreinfo Bug #802487 [aide] aide crash (SIGSEGV) at beginning Added tag(s) unreproducible. Bug

Bug#802618: xinit: no keyboard/mouse support after yesterdays's upgrade

On Wed, Oct 21, 2015 at 20:12:01 +0200, Andreas Metzler wrote: > Control: reassign 802618 xserver-xorg-core 2:1.17.2-2 > Control: severity 802618 serious > Control: retitle 802618 keyboard/mouse support broken - mising dep on > libpam-systemd? > > On 2015-10-21 Andreas Metzler

Bug#794723: [Pkg-utopia-maintainers] Bug#794723: Policykit crashes systemd

Am 21.10.2015 um 08:33 schrieb Martin Pitt: > Hello Michael, > > Michael Biebl [2015-10-21 1:45 +0200]: >> any particular reason why you didn't just use >> systemctl (un)mask --runtime > > No particular one, but that looks a bit nicer indeed, and the code > paths are already guarded with [ -d

Bug#787453: libdata-alias-perl: FTBFS with perl 5.22

Niko Tyni wrote: >However, building Data-Alias-1.19 with clang works even on our packaged >perl 5.22.0-4. So the perl build doesn't seem to matter that much. Thanks, that's a very useful set of results. Compiler used to build D-A matters. It must be doing something hacky at the C language level

Bug#801610: marked as done (libogg-vorbis-decoder-perl: FTBFS: Failed test 'raw_total')

Your message dated Wed, 21 Oct 2015 18:48:53 + with message-id and subject line Bug#801610: fixed in libogg-vorbis-decoder-perl 0.9-3 has caused the Debian Bug report #801610, regarding libogg-vorbis-decoder-perl: FTBFS: Failed test 'raw_total' to be

Bug#787453: libdata-alias-perl: FTBFS with perl 5.22

On Wed, Oct 21, 2015 at 06:22:28PM +0100, Zefram wrote: > It would be really helpful if someone with a failing setup would > try figuring out which part of the perl build makes the difference. > Something I haven't yet tried varying is the C compiler. I'm using Debian > gcc 4.7.2-5, which

Bug#800322: upstream fix

the upstream code has fixed the vmhgfs problem up to Linux 4.2 with 9.10.3 open-vm-tools release. https://github.com/vmware/open-vm-tools/tree/stable-9.10.3 thanks.

Bug#800399: marked as done (libsigc++-2.0: C++11 features in headers but no -std=c++11 in pkg-config)

Your message dated Wed, 21 Oct 2015 21:23:31 + with message-id and subject line Bug#800399: fixed in libsigc++-2.0 2.6.1-3 has caused the Debian Bug report #800399, regarding libsigc++-2.0: C++11 features in headers but no -std=c++11 in pkg-config to be

Bug#800371: marked as done (glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config)

Your message dated Wed, 21 Oct 2015 22:38:00 +0200 with message-id <5627f7a8.7020...@debian.org> and subject line Re: glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config has caused the Debian Bug report #800371, regarding glibmm2.4: C++11 features in headers but no -std=c++11 in

Bug#801645: marked as done (gnome-shell-extension-suspend-button: Update needed for GNOME 3.18)

Your message dated Wed, 21 Oct 2015 21:22:40 + with message-id and subject line Bug#801645: fixed in gnome-shell-extension-suspend-button 0~git20150615-2 has caused the Debian Bug report #801645, regarding gnome-shell-extension-suspend-button: Update

Bug#790298: marked as done (foxeye: FTBFS with glibc 2.21 and gcc-5)

Your message dated Wed, 21 Oct 2015 21:22:20 + with message-id and subject line Bug#790298: fixed in foxeye 0.10.2-1 has caused the Debian Bug report #790298, regarding foxeye: FTBFS with glibc 2.21 and gcc-5 to be marked as done. This means that you

Bug#802506: marked as done (Not compatible with gnome-shell 3.18)

Your message dated Wed, 21 Oct 2015 21:22:35 + with message-id <e1zp0qb-vy...@franck.debian.org> and subject line Bug#802506: fixed in gnome-shell-extension-autohidetopbar 20151021-1 has caused the Debian Bug report #802506, regarding Not compatible with gnome-shell 3.18 to be

Bug#802636: Make a bootable USB with SYNC command when the ISO source from USB, then both of USB become bootable

Package: coreutils Version: 8.23-4 Severity: critical Tags: d-i Hello, Debian Team. First, I do apologize if I have put this into the wrong category of bug report. Because I have to submit the package name, which is sync command is from the coreutils package. But it definitely related with

Bug#802458: marked as done (gnome-software: fails to upgrade from 'jessie' - trying to overwrite /usr/share/dbus-1/services/org.freedesktop.PackageKit.service)

Your message dated Wed, 21 Oct 2015 22:49:25 + with message-id and subject line Bug#802458: fixed in gnome-software 3.18.2-2 has caused the Debian Bug report #802458, regarding gnome-software: fails to upgrade from 'jessie' - trying to overwrite

Bug#775760: marked as done (openjdk-8 rejected due to wrong lintian warning)

Your message dated Wed, 21 Oct 2015 22:53:42 + with message-id and subject line Bug#775760: fixed in openjdk-8 8u66-b17-1 has caused the Debian Bug report #775760, regarding openjdk-8 rejected due to wrong lintian warning to be marked as done. This means

Bug#787453: libdata-alias-perl: FTBFS with perl 5.22

The compiler-dependent problem turned out to be some C-level undefined behaviour in the module, with insufficient sequence points around a variable mutation. The compilers differed in whether they performed the write before or after a call to a Perl core function (yylex()) that in 5.22 has come

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

Julien Cristau on 2015/10/21 +0200 @20:48:56: > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > > > This upgrade has broken X startup for me. Here is how > > I start X (as ordinary user): > > > > exec setsid env -i \ > > ... > > X :0 vt63 \ > > So one solution is to

Processed: Bumping severity to serious.

Processing commands for cont...@bugs.debian.org: > severity 786347 serious Bug #786347 [src:monav] monav: Please consider dropping qtmobility as build dependency Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 786347:

Bug#785855: Asked for it's removal

I have just asked for the removal of this package. -- If for every rule there is an exception, then we have established that there is an exception to every rule. If we accept "For every rule there is an exception" as a rule, then we must concede that there may not be an exception after all,

Processed: Re: Bug#802618: xinit: no keyboard/mouse support after yesterdays's upgrade

Processing control commands: > reassign 802618 xserver-xorg-core 2:1.17.2-2 Bug #802618 [xinit] xinit: no keyboard/mouse support after yesterdays's upgrade Bug reassigned from package 'xinit' to 'xserver-xorg-core'. No longer marked as found in versions xinit/1.3.4-3. Ignoring request to alter

Bug#802636: Make a bootable USB with SYNC command when the ISO source from USB, then both of USB become bootable

severity 802636 normal tag 802636 + moreinfo thanks Imam Kurniawan wrote: > First, I do apologize if I have put this into the wrong category of bug > report. > Because I have to submit the package name, which is sync command is from the > coreutils package. > But it definitely related with

Processed: Re: Bug#802636: Make a bootable USB with SYNC command when the ISO source from USB, then both of USB become bootable

Processing commands for cont...@bugs.debian.org: > severity 802636 normal Bug #802636 [coreutils] Make a bootable USB with SYNC command when the ISO source from USB, then both of USB become bootable Severity set to 'normal' from 'critical' > tag 802636 + moreinfo Bug #802636 [coreutils] Make a

Bug#802067: marked as done (django-shortuuidfield: FTBFS: ImportError: No module named 'shortuuid')

Your message dated Thu, 22 Oct 2015 01:18:54 + with message-id and subject line Bug#802067: fixed in django-shortuuidfield 0.1.2-4 has caused the Debian Bug report #802067, regarding django-shortuuidfield: FTBFS: ImportError: No module named 'shortuuid' to

Bug#802471: libopenraw1v5: Try to overwrite file in libopenraw1

Source: libopenraw Tags: patch Followup-For: Bug #802471 This works for me, tested installing libopenraw1v5 package. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux

Bug#802638: ntpd fails to start with "Cannot find user ID 113"

Package: ntp Version: 1:4.2.8p4+dfsg-1 Severity: grave Justification: renders package unusable As per subject. This may well be a duplicate of #793745, however: - I am using the default ntp.conf shipped with the package, including the "rlimit memlock 0" line. - Downgrading to 4.2.8p3+dfsg-1

Bug#802590: cannot upgrade from libopenraw1 to libopenraw1v5

Package: libopenraw1v5 Version: 0.0.9-3.7 Severity: serious libopenraw1v5 does not properly handle its relationship with libopenraw1, causing conflicts like the one below: Preparing to unpack .../libopenraw1v5_0.0.9-3.7_amd64.deb ... Unpacking libopenraw1v5:amd64 (0.0.9-3.7) ... dpkg: error

Bug#802592: kdenlive: Kdenlive hangs after moving anything into a timeline

Package: kdenlive Version: 15.08.2-1 Severity: grave Dear Maintainer, 1. Start kdenlive 2. Right-click in Project Bin, -> Add Clip 3. Select any video, press ok. 4. Move it into Timeline in the bottom 5. Kdenlive is completely frozen. Thus, it is completely impossible to use kdenlive. --

Processed: merging 802471 802590

Processing commands for cont...@bugs.debian.org: > merge 802471 802590 Bug #802471 [libopenraw1v5] libopenraw1v5: Try to overwrite file in libopenraw1 Bug #802590 [libopenraw1v5] cannot upgrade from libopenraw1 to libopenraw1v5 Marked as found in versions libopenraw/0.0.9-3.6. Merged 802471

Bug#802645: openstack-doc-tools-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/openstack-doc-tools/cleanup/retf/disabled_rules.yaml

Package: openstack-doc-tools-common Version: 0.31.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + python-openstack-doc-tools Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in

Processed: openstack-doc-tools-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/openstack-doc-tools/cleanup/retf/disabled_rules.yaml

Processing control commands: > affects -1 + python-openstack-doc-tools Bug #802645 [openstack-doc-tools-common] openstack-doc-tools-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/openstack-doc-tools/cleanup/retf/disabled_rules.yaml Added indication that 802645 affects

Bug#802471: libopenraw1v5: Try to overwrite file in libopenraw1

Control: forcemerge -1 802644 Control: affects -1 + libopenraw-dev libgegl-0.3-0 tumbler-plugins-extra > Unpacking libopenraw1v5:i386 (0.0.9-3.6) ... > dpkg: error processing archive > /var/cache/apt/archives/libopenraw1v5_0.0.9-3.6_i386.deb (--unpack): > trying to overwrite

Processed: Re: libopenraw1v5: Try to overwrite file in libopenraw1

Processing control commands: > forcemerge -1 802644 Bug #802471 [libopenraw1v5] libopenraw1v5: Try to overwrite file in libopenraw1 Bug #802590 [libopenraw1v5] cannot upgrade from libopenraw1 to libopenraw1v5 Bug #802644 [libopenraw1v5] libopenraw1v5: conflict with libopenraw1 Severity set to

Bug#802646: libvolk1-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/i386-linux-gnu/cmake/volk/VolkConfig.cmake

Package: libvolk1-dev Version: 1.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + gnuradio-dev Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'stretch' fails

Processed: libvolk1-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/i386-linux-gnu/cmake/volk/VolkConfig.cmake

Processing control commands: > affects -1 + gnuradio-dev Bug #802646 [libvolk1-dev] libvolk1-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/i386-linux-gnu/cmake/volk/VolkConfig.cmake Added indication that 802646 affects gnuradio-dev -- 802646:

Processed: found 792176 in 5.5.44-0+deb8u1, found 801815 in 2.0.1-1 ..., user debian...@lists.debian.org ...

Processing commands for cont...@bugs.debian.org: > found 792176 5.5.44-0+deb8u1 Bug #792176 [mysql-server-5.5] mysql-server-5.5: uninstallable in sid Marked as found in versions mysql-5.5/5.5.44-0+deb8u1. > found 801815 2.0.1-1 Bug #801815 [plowshare] plowshare-modules and plowshare: error when

Bug#798547: marked as done (actdiag: FTBFS: TypeError: coercing to Unicode: need string or buffer, bool found)

Your message dated Thu, 22 Oct 2015 03:34:48 + with message-id and subject line Bug#798547: fixed in actdiag 0.5.3-5 has caused the Debian Bug report #798547, regarding actdiag: FTBFS: TypeError: coercing to Unicode: need string or buffer, bool found to

Bug#794723: [Pkg-utopia-maintainers] Bug#794723: Policykit crashes systemd

Hello Michael, Michael Biebl [2015-10-21 1:45 +0200]: > any particular reason why you didn't just use > systemctl (un)mask --runtime No particular one, but that looks a bit nicer indeed, and the code paths are already guarded with [ -d /run/systemd/system ]. Changed this to systemctl now and

Processed: tagging 787453

Processing commands for cont...@bugs.debian.org: > tags 787453 + fixed-upstream Bug #787453 [src:libdata-alias-perl] libdata-alias-perl: FTBFS with perl 5.22 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 787453:

Bug#785930: RM: bognor-regis -- ROM; Dead upstream

Package: ftp.debian.org Severity: wishlist Dear ftp-masters, Please remove bognor-regis. Bognor-regis is basically a background daemon that plays music and maintain a playlist. So on Mobile/Tablet/Desktop devices, they just need to re-create the GUI and use dbus to call that daemon doing the

Bug#802456: marked as done (clang-tidy-3.6: fails to upgrade from 'testing' - trying to overwrite /usr/lib/llvm-3.6/bin/clang-tidy)

Your message dated Wed, 21 Oct 2015 06:51:38 + with message-id and subject line Bug#802456: fixed in llvm-toolchain-3.6 1:3.6.2-3 has caused the Debian Bug report #802456, regarding clang-tidy-3.6: fails to upgrade from 'testing' - trying to overwrite

Bug#794723: marked as done (Policykit crashes systemd)

Your message dated Wed, 21 Oct 2015 06:52:40 + with message-id and subject line Bug#794723: fixed in policykit-1 0.113-2 has caused the Debian Bug report #794723, regarding Policykit crashes systemd to be marked as done. This means that you claim that the

Bug#801733: fine in sid

build-depends works fine in sid. what are the build dependencies failing in strech?

Bug#801733: Fwd: fine in sid

build-depends works fine in sid. what are the build dependencies failing in strech?

Bug#801733: fine in sid

On Wed, Oct 21, 2015 at 10:10:07AM +, olivier sallou wrote: > build-depends works fine in sid. > what are the build dependencies failing in strech? Due to #775254 python-mysqldb 1.3.4 does not migrate and thus python3-mysqldb is missing in testing. I'm working on this right now. Kind

Bug#801889: marked as done (Build-Depends on no longer existing packages)

Your message dated Wed, 21 Oct 2015 10:22:02 + with message-id and subject line Bug#801889: fixed in gnome-do 0.95.3-4 has caused the Debian Bug report #801889, regarding Build-Depends on no longer existing packages to be marked as done. This means that

Bug#802527: [Pkg-javascript-devel] Bug#802527: twitter-bootstrap3: FTBFS: less: SyntaxError: Cannot find module 'source-map'

Quoting Chris West (Faux) (2015-10-20 00:14:50) > The package fails to build: > > # Mimic less from Gruntfile > lessc --strict-math=on \ > --source-map-url=bootstrap.css.map \ > --source-map=dist/css/bootstrap.css.map \ > less/bootstrap.less dist/css/bootstrap.css >

Bug#799724: marked as done (cyrus-replication broken / wrong connection)

Your message dated Wed, 21 Oct 2015 10:21:43 + with message-id and subject line Bug#799724: fixed in cyrus-imapd-2.4 2.4.17+nocaldav-2 has caused the Debian Bug report #799724, regarding cyrus-replication broken / wrong connection to be marked as done.

Bug#801835: marked as done (libexchangemapi-1.0-dev impossible dependencies.)

Your message dated Wed, 21 Oct 2015 10:21:55 + with message-id and subject line Bug#801835: fixed in evolution-mapi 3.18.0-4 has caused the Debian Bug report #801835, regarding libexchangemapi-1.0-dev impossible dependencies. to be marked as done. This

Bug#775254: Debian Python Modules Team - please inject the attached debdiff of NMU into your VCS

Hi, I just uploaded a NMU to fix this bug. Please inject the debdiff into VCS. BTW, I noticed that at least the changelog entry for 1.2.3-2.1 is missing in the changelog - please verify that all changes are taken over. Kind regards Andreas. -- http://fam-tille.de diff -Nru

Bug#775254: marked as done (python-mysqldb-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

Your message dated Wed, 21 Oct 2015 12:34:21 + with message-id and subject line Bug#775254: fixed in python-mysqldb 1.3.4-2.1 has caused the Debian Bug report #775254, regarding python-mysqldb-dbg: unhandled symlink to directory conversion:

Bug#802471: libopenraw1v5: Try to overwrite file in libopenraw1

Package: libopenraw1v5 Version: 0.0.9-3.7 Followup-For: Bug #802471 Dear Maintainer, it seems an attempt has been made to fix this problem, by adding Replaces/Conflicts stanzas. Unfortunately these stanzas are wrong, as they currently make 'libopenraw1v5' replace 'libopenraw1v5' and replace

Bug#801413: polarssl: CVE-2015-5291: Remote attack on clients using session tickets or SNI

Hi, On Tue, 2015-10-20 at 19:37 +0200, Florian Weimer wrote: > * James Cowgill: [...] > > One thing which was suggested was to use 1.3.14 and then disable at > > compile time all the new features which may affect the ABI and then > > revert the SONAME change, but is doing that actually allowed

Bug#794723: marked as done (Policykit crashes systemd)

Your message dated Wed, 21 Oct 2015 06:18:50 + with message-id and subject line Bug#794723: fixed in policykit-1 0.105-13 has caused the Debian Bug report #794723, regarding Policykit crashes systemd to be marked as done. This means that you claim that

Bug#799948: Plasma desktop is unable to start (black screen - panic)

On Oct 21, 2015 08:54, "Miguel A. Rojas" wrote: > > On 10/21/2015 12:22 AM, Luca Boccassi wrote: >>> >>> Hi Miguel, >>> >>> The reason I'm asking is because I can't reproduce any problems on GDM, >>> with any software that uses GLX or other libraries, after adding the >>>

Bug#802563: [debian-mysql] Bug#802563: mysql-5.6: Multiple security fixes from the October 2015 CPU

Hi, someone just has to tag and upload mysql-5.6 All work has already been done on git. Cheers B On Wed, Oct 21, 2015 at 7:30 AM Salvatore Bonaccorso wrote: > Source: mysql-5.6 > Version: 5.6.25-4 > Severity: grave > Tags: security upstream fixed-upstream > > Hi > > As

Bug#801695: clang-3.6 segfaults on hello world on arm64

Ok, closing. As -2 is just a rebuild of clang 3.6 without any change to the binary, I don't think it was a clang issue (or maybe the version of gcc used to build -1 which was misscompiling clang arm64) S

Processed: bug 802035 is forwarded to https://github.com/schweikert/fping/issues/85

Processing commands for cont...@bugs.debian.org: > forwarded 802035 https://github.com/schweikert/fping/issues/85 Bug #802035 {Done: Axel Beckert } [fping] fping segfaults on amd64 Set Bug forwarded-to-address to 'https://github.com/schweikert/fping/issues/85'. > thanks Stopping

Bug#799948: Plasma desktop is unable to start (black screen - panic)

On 10/21/2015 12:22 AM, Luca Boccassi wrote: Hi Miguel, The reason I'm asking is because I can't reproduce any problems on GDM, with any software that uses GLX or other libraries, after adding the workaround. But I noticed something looking again at the system info you forwarded, the only user