Bug#796843: marked as done (python-clang-3.8 and python-clang-3.7: error when trying to install together)

Your message dated Thu, 27 Aug 2015 13:21:58 + with message-id e1zux7u-0002ww...@franck.debian.org and subject line Bug#796843: fixed in llvm-toolchain-3.7 1:3.7~+rc4-1 has caused the Debian Bug report #796843, regarding python-clang-3.8 and python-clang-3.7: error when trying to install

Bug#779803: marked as done (smuxi performs autoconnect on first startup)

Your message dated Thu, 27 Aug 2015 13:34:38 + with message-id e1zuxka-00056i...@franck.debian.org and subject line Bug#779803: fixed in smuxi 1.0-2 has caused the Debian Bug report #779803, regarding smuxi performs autoconnect on first startup to be marked as done. This means that you claim

Processed: Cant reproduce

Processing commands for cont...@bugs.debian.org: fixed 796669 8.4.3-7 Bug #796669 [tix] tix compiled against tk-8.5 instead of tk-8.6 Marked as fixed in versions tix/8.4.3-7. thanks Stopping processing here. Please contact me if you need assistance. -- 796669:

Processed: limit source to apt, tagging 796999, tagging 796459, tagging 796070

Processing commands for cont...@bugs.debian.org: limit source apt Limiting to bugs with field 'source' containing at least one of 'apt' Limit currently set to 'source':'apt' tags 796999 + pending Bug #796999 [apt] apt: segmentation fault Added tag(s) pending. tags 796459 + pending Bug #796459

Bug#796669: Cant reproduce

fixed 796669 8.4.3-7 thanks I cannot reproduce the above step from a debian/strech amd64 installation, using 8.4.3-7. It seems the fix was done in 8.4.3-6. marking as fixed. I'll leave the bug open for now.

Bug#796811: marked as done (python-lldb-3.8 and python-lldb-3.7: error when trying to install together)

Your message dated Thu, 27 Aug 2015 13:21:58 + with message-id e1zux7u-0002ws...@franck.debian.org and subject line Bug#796811: fixed in llvm-toolchain-3.7 1:3.7~+rc4-1 has caused the Debian Bug report #796811, regarding python-lldb-3.8 and python-lldb-3.7: error when trying to install

Bug#795818: add patch

Control: tags -1 + patch patch at http://launchpadlibrarian.net/215701133/libindi_1.0.0-2_1.0.0-2ubuntu1.diff.gz

Processed: add patch

Processing control commands: tags -1 + patch Bug #795818 [src:libindi] libindi: FTBFS on arm64: symbols mismatch Added tag(s) patch. -- 795818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 795844

Processing commands for cont...@bugs.debian.org: tags 795844 + pending Bug #795844 [cdimage.debian.org] armel and armhf images missing kernel and initramfs Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 795844:

Bug#789875: subsurface: FTBFS in experimental

On Thu, Aug 27, 2015 at 09:08:03AM +0200, Sylvestre Ledru wrote: Le 27/08/2015 05:33, Michael Gilbert a écrit : On Wed, Aug 26, 2015 at 7:11 PM, Linus Torvalds wrote: So quite frankly, the fact that Debian people now attack Dirk, who has been bending over backwards over these kinds of

Bug#796892: #796892: ftp.debian.org: Broken Sources.bz2 file for at least 3 repositories

Hi, According to Axel Beckert this has been fixed in a recent push to the mirrors: https://lists.debian.org/debian-mirrors/2015/08/msg6.html It seems to work for me, so maybe this bug should be closed. Thanks to everyone involved for fixing this! G'luck, Peter -- Peter Pentchev

Bug#796892: marked as done (ftp.debian.org: Broken Sources.bz2 file for at least 3 repositories)

Your message dated Thu, 27 Aug 2015 15:32:31 +0200 with message-id 20150827133231.ga21...@home.ouaza.com and subject line Re: Bug#796892: #796892: ftp.debian.org: Broken Sources.bz2 file for at least 3 repositories has caused the Debian Bug report #796892, regarding ftp.debian.org: Broken

Processed (with 1 errors): forcibly merging 796190 796258

Processing commands for cont...@bugs.debian.org: forcemerge 796190 796258 Bug #796190 {Done: Lucas Nussbaum lu...@debian.org} [pajeng] pajeng: FTBFS without Internet connection Unable to merge bugs because: package of #796258 is 'src:pajeng' not 'pajeng' Failed to forcibly merge 796190: Did not

Bug#797077: didjvu: FTBFS: XMP tests fail

* Jakub Wilk jw...@debian.org, 2015-08-27, 18:53: I have a feeling that the recent binNMU of pyexiv2 (Build against libexiv2-14) broke something... pyexiv2 is deprecated upstream, so one possible solution for Debian is to disable this backend completely. -- Jakub Wilk

Bug#777921: itksnap: ftbfs with GCC-5

Building this package today (and for several weeks now) has been blocked by libinsighttoolkit4-dev being not installable in sid. There seems to be no bug report against libinsighttoolkit4-dev so so .. As aptitude tells me The following packages have unmet dependencies: libstdc++6 : Breaks:

Processed: found 794933 in 2.4.10-10

Processing commands for cont...@bugs.debian.org: found 794933 2.4.10-10 Bug #794933 [apache2-suexec-custom] apache2-suexec-custom: prompting due to modified conffiles which were not modified by the user: /etc/apache2/conf-available/security.conf Marked as found in versions apache2/2.4.10-10.

Bug#797087: debian-design: FTBFS: reclass unexpectedly returned exit value 7

Source: debian-design Version: 3 Severity: serious Tags: sid stretch Justification: FTBFS This package FTBFS in a clean sid chroot: cd content/desktop/animation/ \ boxer compose \ --nodedir /«PKGBUILDDIR»/nodes \ --skeldir /«PKGBUILDDIR»/skel \

Bug#785300: xul-ext-pentadactyl: pentadactyl not compatible with iceweasel 38.0-1

Hi, On Thu, Aug 27, 2015 at 07:17:16AM -0400, David Prévot wrote: Whatever way you wish to follow, can you please take action now? “The next point release […] is scheduled for Saturday, September 5th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding

Processed: Change submitter

Processing commands for cont...@bugs.debian.org: submitter 790320 Martin Michlmayr t...@hpe.com Bug #790320 [libtommath] FTBFS: bad LaTeX usage (float here) Changed Bug submitter to 'Martin Michlmayr t...@hpe.com' from 'Martin Michlmayr t...@hp.com' submitter 790442 Martin Michlmayr

Processed: limit source to mozilla-noscript, tagging 797043

Processing commands for cont...@bugs.debian.org: limit source mozilla-noscript Limiting to bugs with field 'source' containing at least one of 'mozilla-noscript' Limit currently set to 'source':'mozilla-noscript' tags 797043 + pending Bug #797043 [xul-ext-noscript] xul-ext-noscript: menu no

Bug#797077: didjvu: FTBFS: XMP tests fail

Source: didjvu Version: 0.6-1 Severity: serious Justification: fails to build from source didjvu FTBFS in unstable: | + python2.7 /usr/bin/nosetests --all-modules --verbose [...] | tests.test_xmp.test_metadata.test_empty(libxmp_backend, exiv2_checker) ... SKIP: [Errno 2] No such file or

Processed: [bts-link] source package pyfai

Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package pyfai # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org

Bug#797077: didjvu: FTBFS: XMP tests fail

On 27.08.2015 19:02, Jakub Wilk wrote: * Jakub Wilk jw...@debian.org, 2015-08-27, 18:53: I have a feeling that the recent binNMU of pyexiv2 (Build against libexiv2-14) broke something... pyexiv2 is deprecated upstream, so one possible solution for Debian is to disable this backend

Bug#797070: [python-urllib3] Break python-requests and transitively vim-youcompleteme

Hello, On Thursday 27 of August 2015 17:08:24 Daniele Tricoli wrote: Hello Jan, thanks for this report! On Thursday 27 August 2015 16:44:14 Jan Hudec wrote: Downgrading python-urllib3 to 1.10.4-1 fixes the problem. There is no available upgrade to python-requests,

Bug#797068: goobook: depends on python-httplib2 v0.9, but crashes requiring v0.9.1.

Package: goobook Version: 1.9-1 Severity: grave Justification: renders package unusable The package goobook depends on python-httplib2 0.9+dfsg-2, but goobook the program has python-httplib2 0.9.1 as a requirement. This renders goobook unusable. -- System Information: Debian Release:

Bug#797070: [python-urllib3] Break python-requests and transitively vim-youcompleteme

Package: python-urllib3 Version: 1.11-1 Severity: serious --- Please enter the report below this line. --- After upgrade of python-urllib3 to 1.11-1, vim-youcompleteme requests fail with: Printing YouCompleteMe debug information... Error detected while processing function SNR100_DebugInfo:

Bug#797003: libical 1.0.1-0.1 has broken its ABI (again)

Control: block -1 by 797074 Hello Alexander Kurtz. Thanks for your bug report. On Wed, Aug 26, 2015 at 09:33:04PM +0200, Alexander Kurtz wrote: Package: libical-dev Version: 1.0.1-0.1 Severity: serious Hi, it seems that the latest upload of libical (1.0.1-0.1) has broken its ABI yet

Bug#796979: diaspora, devise and rails engines

On Thursday 27 August 2015 09:41 PM, Pirate Praveen wrote: This is caused by devise and I suspect our handling of this rails engine is buggy. Can someone help troubleshoot it? Switching to gem installed devise also throws the same error, so bug is somewhere else. If you need access to a test

Processed: forcibly merging 796190 796258

Processing commands for cont...@bugs.debian.org: forcemerge 796190 796258 Bug #796190 {Done: Lucas Nussbaum lu...@debian.org} [src:pajeng] pajeng: FTBFS without Internet connection Bug #796258 [src:pajeng] pajeng: FTBFS: Documentation generation tries to connect to the internet during build

Processed: Re: libical 1.0.1-0.1 has broken its ABI (again)

Processing control commands: block -1 by 797074 Bug #797003 [libical-dev] libical 1.0.1-0.1 has broken its ABI (again) 797003 was not blocked by any bugs. 797003 was not blocking any bugs. Added blocking bug(s) of 797003: 797074 -- 797003:

Bug#796979: diaspora, devise and rails engines

Hi, Last week I uploaded diaspora package to experimental (about 4 years of work by many contributors made this possible). After fixing a few dependency issues (some packages were not in the archive and for some versions had to tightened), all dependencies are satisfied both for debian package

Bug#796999: marked as done (apt: segmentation fault)

Your message dated Thu, 27 Aug 2015 16:37:32 + with message-id e1zv0ba-0001na...@franck.debian.org and subject line Bug#796999: fixed in apt 1.1~exp11 has caused the Debian Bug report #796999, regarding apt: segmentation fault to be marked as done. This means that you claim that the problem

Bug#797070: [python-urllib3] Break python-requests and transitively vim-youcompleteme

Hello Jan, thanks for this report! On Thursday 27 August 2015 16:44:14 Jan Hudec wrote: Downgrading python-urllib3 to 1.10.4-1 fixes the problem. There is no available upgrade to python-requests, python-requests-futures or vim-youcompleteme to fix the problem on their side. I can't test it

Bug#797076: libassa-3.5-5-dev: gratuitous -dev package name change

Package: libassa-3.5-5-dev Severity: serious Hi, libassa3.5-5-dev was renamed to libassa-3.5-5-dev, which makes reverse deps unbuildable. Please revert that change, there's no reason to rename the -dev package. Cheers, Julien signature.asc Description: Digital signature

Bug#797020: ufw: FTBFS: False is not true

On 08/26/2015 06:16 PM, Chris Lamb wrote: ufw fails to build from source in unstable/amd64. Even with net-tools installed (for `netstat`) it fails in a similar way if that helps. ... The full build log is attached or can be viewed here:

Bug#796051: marked as done (django-oauth-toolkit: FTBFS: multiple test failures: AttributeError: encoding)

Your message dated Thu, 27 Aug 2015 19:48:57 + with message-id e1zv3ap-0004ri...@franck.debian.org and subject line Bug#796051: fixed in django-oauth-toolkit 0.9.0-1 has caused the Debian Bug report #796051, regarding django-oauth-toolkit: FTBFS: multiple test failures: AttributeError:

Bug#790442: FTBFS with new LaTeX: Unknown float option `H'.

On Mon, 29 Jun 2015 11:32:43 -0400 Martin Michlmayr t...@hp.com wrote: You're using the H float option. According to https://en.wikibooks.org/wiki/LaTeX/Floats,_Figures_and_Captions you need \usepackage{float} for that, but it seems simpler solution is to replace it with !h. Thanks for the

Bug#797088: dune-pdelab: FTBFS: undefined reference to `Dune::concatPaths

Source: dune-pdelab Version: 2.0.0-1 Severity: serious Tags: sid stretch Justification: FTBFS This package FTBFS in a clean sid chroot: libtool: link: g++ -std=c++11 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fpermissive -Wl,-z -Wl,relro -o .libs/testanalytic

Bug#797043: Bug#797079: wheezy-pu: package mozilla-noscript/2.6.8.19-1~deb7u2

David Prévot taf...@debian.org writes: + [ Kalle Olavi Niemitalo ] + * Temporarily allow scripts with recent iceweasel +(Closes: #797043) Those functions in noscriptService.js are used not only for setting up the menu (from which the user could temporarily whitelist sites), but also for

Bug#793991: [Pkg-pascal-devel] Bug#793991: Update on bug#793991: lazarus: armel and armhf builds stall

Hi Paul, On Fri, 2015-08-21 at 13:14 +0200, Paul Gevers wrote: Just so everybody can be aware, Graham and me here at Debconf15 have been working on a strategy to tackle this and I have been working on and off the last couple of days to work on the first track with mild success. Graham will

Bug#797095: amd64: netboot 2015-04-22, 2015-06-04, 2015-08-13 fail, wheezy succeeds

Package: debian-installer Version: 20150422+deb8u1 Severity: grave Justification: renders package unusable Dear Maintainer, summary --- amd64 netboot wheezy 2015-01-05 works amd64 netboot jessie 2015-04-22 fails amd64 netboot jessie 2015-06-04 fails amd64 netboot stretch 2015-08-13 fails

Bug#794990: marked as done (mrpt: ftbfs with new libstdc++ ABI)

Your message dated Thu, 27 Aug 2015 20:08:39 +0100 with message-id 20150827190839.ga3...@perpetual.pseudorandom.co.uk and subject line Re: Bug#794990: mrpt: ftbfs with new libstdc++ ABI has caused the Debian Bug report #794990, regarding mrpt: ftbfs with new libstdc++ ABI to be marked as done.

Bug#797090: konversation: FTBFS: *** No rule to make target '/usr/lib/libsoprano.so'

Source: konversation Version: 1.5-2 Severity: serious Tags: sid stretch Justification: FTBFS This package FTBFS in a clean sid chroot: [ 76%] Building CXX object src/CMakeFiles/konversation.dir/preferences_base.o cd src /usr/bin/c++ -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=26 -DKDE_DEPRECATED_WA

Bug#797089: ggcov: FTBFS: tests fail

Source: ggcov Version: 0.9-7 Severity: serious Tags: sid stretch Justification: FTBFS This package FTBFS in a clean sid chroot: Running tests hostname: kale date: 20150827T092647 uname -s: Linux uname -m: x86_64 uname -r: 4.1.0-1-amd64 head -1 /etc/os-release: PRETTY_NAME=Debian GNU/Linux

Bug#796953: fglrx-driver: Kernel 4.1 backport breaks fglrx in Jessie

On Thu, 2015-08-27 at 08:29 +0200, Rhonda D'Vine wrote: reopen 796953 Hi! * Julien Aubin julien.au...@gmail.com [2015-08-26 10:07:58 CEST]: Source: fglrx-driver Severity: critical Justification: breaks the whole system Hello, Update 4.1 of the Linux kernel has been

Bug#797095: PXE on hp server

HP ProLiant DL390 Gen 9, redscreen with testing/main/installer-amd64/20150813/images/netboot: debian-installer/amd64/pxelinux.0 If I replace ONLY pxelinux.0 with stable/main/installer-amd64/20150422+deb8u1/images/netboot: debian-installer/amd64/pxelinux.0 (but use all of the rest of testing)

Bug#797020: ufw: FTBFS: False is not true

Hi Jamie, ufw fails to build from source in unstable/amd64. Even with net-tools installed (for `netstat`) it fails in a similar way if that helps. ... Just to clarify, I tried installing net-tools just in case it was a trivial missing Build-Dependency issue. :) The full build log is

Bug#797112: open-iscsi: Prevent testing migration

Package: open-iscsi Version: 2.0.873+git0.3b4b4500-10 Severity: serious I'm opening this RC bug so that open-iscsi doesn't migrate to testing, for two reasons: - we need to make a followup upload to fix the systemd WantedBy= target, and because of #797108 the old symlinks don't get removed.

Processed: block 797077 with 797119

Processing commands for cont...@bugs.debian.org: block 797077 with 797119 Bug #797077 [src:didjvu] didjvu: FTBFS: XMP tests fail 797077 was not blocked by any bugs. 797077 was not blocking any bugs. Added blocking bug(s) of 797077: 797119 thanks Stopping processing here. Please contact me if

Bug#797076: libassa-3.5-5-dev: gratuitous -dev package name change

libassa3.5-5-dev was renamed to libassa-3.5-5-dev, which makes reverse deps unbuildable. Please revert that change, there's no reason to rename the -dev package. The only reverse dep is granule, which I've prepared a new version of. I'm waiting for it to be uploaded. pgpiNgGDdPOFQ.pgp

Bug#797076: libassa-3.5-5-dev: gratuitous -dev package name change

That still doesn't make sense. You shouldn't rename the dev package, but if you do it shouldn't include a version... On August 27, 2015 11:11:52 PM CEST, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: libassa3.5-5-dev was renamed to libassa-3.5-5-dev, which makes

Bug#797076: libassa-3.5-5-dev: gratuitous -dev package name change

Okay, point taken. But now that it is renamed, should I really rename it again? On Thu, 27 Aug 2015 23:25:34 +0200 Julien Cristau jul...@cristau.org wrote: That still doesn't make sense. You shouldn't rename the dev package, but if you do it shouldn't include a version... On August 27,

Bug#797117: freefem++: missing build-dependency on libhdf5-dev

Source: freefem++ Version: 3.37.1-1 Severity: serious Justification: The uploaded binary packages weren't built into a clean chroot, causing an extra libhdf5-8 [amd64] dependency -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Trying to understand why freefem++ had 'Depends: libhdf5

Bug#797120: redshift-plasmoid: Not usable anymore in Plasma5

Package: redshift-plasmoid Version: 1.0-1 Severity: serious Tags: stretch sid Justification: Not usable anymore Hi! Plasma 5 has arrived to testing a few weeks ago and so all Plasma 4 widgets have become unusable. Please consider either porting this widget to Plasma5 or asking for it's removal

Bug#797123: plasma-widget-veromix: Not usable anymore in Plasma5

Package: plasma-widget-veromix Version: 0.18.3-1.1 Severity: serious Tags: stretch sid Justification: Not usable anymore Hi! Plasma 5 has arrived to testing a few weeks ago and so all Plasma 4 widgets have become unusable. Please consider either porting this widget to Plasma5 or dropping this

Bug#797121: plasma-widget-yawp: Not usable anymore in Plasma5

Package: plasma-widget-yawp Version: 0.4.2-1 Severity: serious Tags: stretch sid Justification: Not usable anymore Hi! Plasma 5 has arrived to testing a few weeks ago and so all Plasma 4 widgets have become unusable. Please consider either porting this widget to Plasma5 or asking for it's

Bug#797135: gnome-software downloads updates automatically by default

Source: gnome-software Severity: critical Once installed the software downloads updates and makes the system do an uograde automatically without even asking the user for confirmation once. The default should be disabled and nor enabled or, at the very least, there should be a very big warning to

Bug#797132: gobject-introspection: missing -fPIC option when compiling

Package: gobject-introspection Version: 1.44.0-1+b2 Severity: serious Justification: makes other package FTBFS Hello, at-spi2-core currently FTBFS in sid, because of g-ir-scanner's way of compiling, here is what the log looks like: /usr/bin/g-ir-scanner --add-include-path=. --warn-all

Bug#796413: marked as done (alembic: FTBFS: ImportError (No module named pytest))

Your message dated Thu, 27 Aug 2015 09:51:27 + with message-id e1zutqb-0004yw...@franck.debian.org and subject line Bug#796413: fixed in alembic 0.7.6-2 has caused the Debian Bug report #796413, regarding alembic: FTBFS: ImportError (No module named pytest) to be marked as done. This means

Bug#794927: marked as done (openstack-dashboard: fails to install: django_pyscss.compressor.DjangoScssFilter: not found)

Your message dated Thu, 27 Aug 2015 09:56:34 + with message-id e1zutv8-0006qh...@franck.debian.org and subject line Bug#794927: fixed in horizon 2015.1.1-1 has caused the Debian Bug report #794927, regarding openstack-dashboard: fails to install: django_pyscss.compressor.DjangoScssFilter: not

Bug#797046: CVE-2015-5685: remote execution vulnerability in lazy_bdecode()

Source: libtorrent-rasterbar Severity: grave Tags: security patch Version: 0.14.10-2 Control: fixed -1 1.0.6-1 Hi, the following vulnerability was published for libtorrent-rasterbar. CVE-2015-5685[0]: | The lazy_bdecode function in BitTorrent DHT bootstrap server | (bootstrap-dht ) allows

Bug#793961: marked as done (timgm6mb-soundfont: fails to upgrade from 'testing' - trying to overwrite /usr/share/sounds/sf2/TimGM6mb.sf2)

Your message dated Thu, 27 Aug 2015 10:02:10 + with message-id e1zuu0y-00083c...@franck.debian.org and subject line Bug#793961: fixed in timgm6mb-soundfont 1.3-2 has caused the Debian Bug report #793961, regarding timgm6mb-soundfont: fails to upgrade from 'testing' - trying to overwrite

Bug#797047: kbookmarks: FTBFS: Updated symbols file needed with new default g++

Source: kbookmarks Version: 5.12.0-1 Severity: serious Tags: patch Hi, Currently kbookmarks FTBFS due to mismatches in the symbols for libkf5bookmarks5 built with the new gcc default. The attached patch provides updated symbols created when building with g++-5.2.1-15. Thanks!

Processed: CVE-2015-5685: remote execution vulnerability in lazy_bdecode()

Processing control commands: fixed -1 1.0.6-1 Bug #797046 [src:libtorrent-rasterbar] CVE-2015-5685: remote execution vulnerability in lazy_bdecode() Marked as fixed in versions libtorrent-rasterbar/1.0.6-1. -- 797046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797046 Debian Bug Tracking

Bug#796430: findbugs: FTBFS: error: PreorderVisitor is not abstract

On 08/21/2015 01:22 PM, Chris West (Faux) wrote: Source: findbugs Version: 2.0.3+repack-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC:

Bug#796953: fglrx-driver: Kernel 4.1 backport breaks fglrx in Jessie

reopen 796953 Hi! * Julien Aubin julien.au...@gmail.com [2015-08-26 10:07:58 CEST]: Source: fglrx-driver Severity: critical Justification: breaks the whole system Hello, Update 4.1 of the Linux kernel has been released in Jessie backports. The problem is that the fglrx driver did

Bug#796069: protobuf: FTBFS on mips{,el} (test suite failure)

On 27/08/15 05:16, Robert Edmonds wrote: It looks like you did a source-only upload, and it also looks like I have a debian/rules build-indep bug. Yeah, I just spotted that. With hindsight, approximately nothing is going to build successfully with build-indep until its maintainer has tested it,

Processed: Re: Bug#796600: libgtkmm-3.0-doc: Embedded copy of jquery without source or copyright mention

Processing control commands: reassign -1 doxygen Bug #796600 [libgtkmm-3.0-doc] libgtkmm-3.0-doc: Embedded copy of jquery without source or copyright mention Bug reassigned from package 'libgtkmm-3.0-doc' to 'doxygen'. No longer marked as found in versions gtkmm3.0/3.14.0-1. Ignoring request to

Bug#796600: libgtkmm-3.0-doc: Embedded copy of jquery without source or copyright mention

Control: reassign -1 doxygen Control: forcemerge 736432 -1 Am 23.08.2015 um 13:37 schrieb Michael Biebl: Am 23.08.2015 um 01:38 schrieb Luke Faraone: Package: libgtkmm-3.0-doc Version: 3.14.0-1 Severity: serious Justification: DFSG Hello, The upstream source tarball contains

Bug#793604: marked as done (gammaray: FTBFS against VTK 6.2)

Your message dated Thu, 27 Aug 2015 11:03:49 + with message-id e1zuuyd-0002ik...@franck.debian.org and subject line Bug#793604: fixed in gammaray 2.3.0-1 has caused the Debian Bug report #793604, regarding gammaray: FTBFS against VTK 6.2 to be marked as done. This means that you claim that

Processed: Re: [Pkg-mozext-maintainers] Bug#797043: xul-ext-noscript: dumbed down menu with iceweasel 38.2.0esr-1~deb7u1 cannot temporarily allow scripts

Processing control commands: severity -1 serious Bug #797043 [xul-ext-noscript] xul-ext-noscript: menu no longer shows script sources after iceweasel 38.2.0esr-1~deb7u1 security update in wheezy Severity set to 'serious' from 'normal' tags -1 patch Bug #797043 [xul-ext-noscript]

Bug#785300: xul-ext-pentadactyl: pentadactyl not compatible with iceweasel 38.0-1

Hi Michael, On Mon, Aug 24, 2015 at 12:19:09PM +0200, Michael Schutte wrote: I'm afraid that an update of dactyl in Jessie is unrealistic. […] It looks to me like a removal from stable is once again the most reasonable thing to do Whatever way you wish to follow, can you please take action

Bug#797037: shogun: FTBFS on mipsen

Source: shogun Version: 3.2.0-7.3 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: stretch sid Due to the use of clang++ which doesn't deal well with the new ABI tags used by recent g++, shogun no longer builds on mips/mipsel, see

Bug#795140: marked as done (hunspell-br: FTBFS: invalid dates in changelog)

Your message dated Thu, 27 Aug 2015 07:34:08 + with message-id e1zurhi-0004bm...@franck.debian.org and subject line Bug#795140: fixed in hunspell-br 0.12-2 has caused the Debian Bug report #795140, regarding hunspell-br: FTBFS: invalid dates in changelog to be marked as done. This means that

Bug#797038: clang: needs to know about C++11 ABI tag

Package: clang Version: 1:3.5-25 Severity: serious clang++ doesn't seem to know about the ABI tags used by g++ 5, in particular the c++11 tag used for functions returning std::string. This likely causes

Bug#797037: shogun: FTBFS on mipsen

On Thu, 27 Aug 2015 at 09:37:48 +0200, Julien Cristau wrote: Source: shogun Version: 3.2.0-7.3 Severity: serious Justification: fails to build from source (but built successfully in the past) Since shogun does not appear to be something that is very useful to run on a less powerful machine,

Bug#791264: qwtplot3d: library transition may be needed when GCC 5 is the default

On Mon, 24 Aug 2015 at 20:05:38 +0900, Satoru KURASHIKI wrote: I've prepared a patch which includes: - Ubuntu's changes for library transition - fix symbols for qt5 library It's meant for applying to the package which staged at mentors.debian.net:

Bug#793012: gmp-ecm: FTBFS on mipsel: bad assembly?

Hello, Please do note that sp.h patch, probably need to be included anyway. Because on mips 32bit UDItype was seen as 32 bit not 64 bit type as expected. Please, take this into consideration, before making final change. Thank you! Regards, Jurica

Bug#797040: xul-ext-gnome-keyring: Incompatible with iceweasel 38.2.0

Package: xul-ext-gnome-keyring Version: 0.6.11-3 Severity: grave Justification: renders package unusable Hallo, as previously reported for an older version https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788967 this now again applies for the current debian stable version. a more recent

Bug#789875: subsurface: FTBFS in experimental

Le 27/08/2015 05:33, Michael Gilbert a écrit : On Wed, Aug 26, 2015 at 7:11 PM, Linus Torvalds wrote: So quite frankly, the fact that Debian people now attack Dirk, who has been bending over backwards over these kinds of stupidities, is not a big surprise. I think it's in the Debian DNA to

Bug#791156: libpodofo: library transition may be needed when GCC 5 is the default

On Wed, 12 Aug 2015 at 11:18:40 +0200, Julien Cristau wrote: There are renamed public symbols involving std::list and std::string, so libpodofo0.9.0 needs to be renamed. A possible patch is available at https://launchpad.net/ubuntu/+source/libpodofo/0.9.0-1.2ubuntu1 I have made a

Bug#797077: didjvu: FTBFS: XMP tests fail

Checked it, when python-libxmp is available didjvu prefers it as default_backend over pyexiv2. For the new package (0.6.1-1) I've just removed the deps on python-pyexiv2 for now until exiv2 gets fixed, the tests just skip that when it's missing. I'm going to unblock this bug so that it could be

Bug#797131: udev kernel check during Wheezy-Jessie upgrade should happen earlier

Package: udev Version: 175-7.2 Severity: serious Justification: Policy 7.2 Dear Maintainer, * What led up to the situation? Upgrading my armhf system Wheezy-Jessie. Did the usual searches for dependencies and what-not. Did a pre-download, then ran the upgrade. About half the packages were

Processed: Re: Bug#797131: udev kernel check during Wheezy-Jessie upgrade should happen earlier

Processing control commands: severity 797131 minor Bug #797131 [udev] udev kernel check during Wheezy-Jessie upgrade should happen earlier Severity set to 'minor' from 'serious' -- 797131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797131 Debian Bug Tracking System Contact

Bug#797131: udev kernel check during Wheezy-Jessie upgrade should happen earlier

Control: severity 797131 minor On Aug 28, Andy Valencia ajv-691-118-1...@vsta.org wrote: If the kernel is not acceptable for the upgrade, it should be detected before the upgrade starts. The kernel check should not happen after the filesystem has been modified with some upgraded content. An