Bug#747259: [Help] gfortran problem: Cannot assign to a named constant

Hi, any idea how to resolve this gfortran problem: Automatic builds of abinit with gfortran 4.8.2 (as unstable uses these days) have been failing: gfortran -DHAVE_CONFIG_H -I. -I../.. -I../../src/incs -I../../src/incs -I/«BUILDDIR»/abinit-7.6.3+dfsg/fallbacks/exports/include -ffree-form -J

Bug#755761: gdm3: Unable to start KDE after last gdm3 upgrade

On Sat, 9 Aug 2014 23:29:29 +0200 Andreas Henriksson wrote: > On Sat, Aug 09, 2014 at 10:11:32PM +0200, Andreas Henriksson wrote: > > I was notified that kde4libs has a debug package, so please try > getting a backtrace with the kdelibs5-dbg package installed. That should > hopefully be enoug

Processed: lower severity

Processing commands for cont...@bugs.debian.org: > severity 758488 important Bug #758488 [python3.4] python3: float conversion broken on s390x Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 758488: http://bugs.debian.org

Processed: reassign 758488 to python3.4

Processing commands for cont...@bugs.debian.org: > reassign 758488 python3.4 Bug #758488 [python3-minimal] python3: float conversion broken on s390x Bug reassigned from package 'python3-minimal' to 'python3.4'. No longer marked as found in versions python3-defaults/3.4.1-1. Ignoring request to alt

Processed: libpulse0 kills the mighty chromium browser... without a hint as to who is to blame

Processing commands for cont...@bugs.debian.org: > reassign 758556 libpulse0 Bug #758556 [chromium] chromium: library upgrade causes sigabrt Bug reassigned from package 'chromium' to 'libpulse0'. No longer marked as found in versions chromium-browser/36.0.1985.103-1. Ignoring request to alter fixe

Bug#758725: package mrpt_1:1.2.1-1 FTBFS on i386, amd64, mips*

Hi Jurica, Please, hopefully these two patches can solve all named semaphore errors: 1) https://github.com/jlblancoc/mrpt/commit/9a878c0950edd8ca7de6f4584f920c4e0db05ecc 2) https://github.com/jlblancoc/mrpt/commit/289498fc34703c2fcf6b61e72c3311144e5fb570 Cheers, JL On Wed, Aug 20, 2014 at 7:

Bug#758756: libgcrypt20: missing udeb: libgcrypt20-udeb

Package: libgcrypt20 Version: 1.6.1-2 Severity: serious Justification: breaks some rdepends Hi, I think we discussed some libgcrypt11/libgcrypt20 udeb things lately, but maybe something was lost along the way. Anyway, libgcrypt20's shlibs file contains: | libgcrypt 20 libgcrypt20 (>=1.6.0-0) | ud

Bug#758755: libcryptsetup4-udeb: depends on libgcrypt20-udeb, which doesn't exist

Package: libcryptsetup4-udeb Version: 2:1.6.6-1 Severity: grave Justification: renders package unusable Hi, your package is no longer installable, because it now depends on libgcrypt20-udeb, which is nowhere to be found. This means at least these packages are uninstallable: partman-crypto-dm

Bug#757830: marked as done (udev init script creates /dev/stdout as plain file (custom kernel w/o initramfs))

Your message dated Wed, 20 Aug 2014 22:34:45 + with message-id and subject line Bug#757830: fixed in systemd 208-8 has caused the Debian Bug report #757830, regarding udev init script creates /dev/stdout as plain file (custom kernel w/o initramfs) to be marked as done. This means that you cl

Processed: Bug#756759 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 756759 pending Bug #756759 {Done: Jelmer Vernooij } [src:samba] samba: CVE-2014-3560: Remote code execution in nmbd Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 756759: http://bugs.de

Bug#751929: marked as done (gdb-doc uninstallable on Jessie alongside gdb and or gdbserver)

Your message dated Wed, 20 Aug 2014 18:05:06 -0400 with message-id <878umix1f1@naesten.mooo.com> and subject line Re: Bug#751929: gdb-doc uninstallable on Jessie alongside gdb and or gdbserver has caused the Debian Bug report #751929, regarding gdb-doc uninstallable on Jessie alongside gdb and

Bug#756759: marked as pending

tag 756759 pending thanks Hello, Bug #756759 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: http://git.debian.org/?p=pkg-samba/samba.git;a=commitdiff;h=b69f22a --- commit b69f22abc3e3d01667578f5bc96a3a7dbe9ccd

Bug#745518: marked as done (Please migrate to lcms2)

Your message dated Wed, 20 Aug 2014 22:03:44 + with message-id and subject line Bug#745518: fixed in devil 1.7.8-9 has caused the Debian Bug report #745518, regarding Please migrate to lcms2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#745518: Please migrate to lcms2

On Tue, Aug 19, 2014 at 11:47:24PM +0200, Markus Koschany wrote: > On 19.08.2014 22:45, Moritz Mühlenhoff wrote: > [...] > > Thanks for the additional investigation, shall I sponsor the upload for > > you or do you have a regular sponsor? > > > > Hi Moritz, > > I wouldn't mind if you sponsored t

Bug#758619: more complete backtrace

On 20/08/2014 22:46, Simon McVittie wrote: Did you upgrade a package recently that could have triggered this, i.e. related to Python, GLib, Gtk 2 or reportbug? I would be interested to know why this is new. Because I use the glib/gtk from experimental I guess. And you could have noticed it by

Bug#757735: marked as done (gtk-gnutella: Segfault at start)

Your message dated Wed, 20 Aug 2014 21:07:54 + with message-id and subject line Bug#757735: fixed in gtk-gnutella 1.1.0-2 has caused the Debian Bug report #757735, regarding gtk-gnutella: Segfault at start to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#754830: marked as done (bluez: rfcomm and bluetoothd fail to start)

Your message dated Wed, 20 Aug 2014 21:04:27 + with message-id and subject line Bug#754830: fixed in bluez 5.21-3 has caused the Debian Bug report #754830, regarding bluez: rfcomm and bluetoothd fail to start to be marked as done. This means that you claim that the problem has been dealt with

Bug#758619: more complete backtrace

Did you upgrade a package recently that could have triggered this, i.e. related to Python, GLib, Gtk 2 or reportbug? I would be interested to know why this is new. Some analysis below. I think this is probably a pygtk bug, but there is a workaround that reportbug could use. On 20/08/14 12:15, VAL

Processed: tagging 757830

Processing commands for cont...@bugs.debian.org: > tags 757830 + pending Bug #757830 [udev] udev init script creates /dev/stdout as plain file (custom kernel w/o initramfs) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 757830: http://bugs.

Bug#757589: marked as done (elastix: FTFBFS against insighttoolkit 4.6)

Your message dated Wed, 20 Aug 2014 14:16:24 -0500 with message-id <20140820191624.ga10...@sumost.ca> and subject line Fixed by ITK 4.6.0-3 upload has caused the Debian Bug report #757589, regarding elastix: FTFBFS against insighttoolkit 4.6 to be marked as done. This means that you claim that the

Bug#758531: Better looking patch

Felipe Sateler writes: > (Why did you not CC the bug? Please CC the bug if not intentional) > > On Wed, Aug 20, 2014 at 10:46 AM, Krzysztof A. Sobiecki > wrote: >> Felipe Sateler writes: >> >>> Hi, >>> >>> On Wed, Aug 20, 2014 at 8:58 AM, Krzysztof A. Sobiecki >>> wrote: A better looking

Bug#756651: marked as done (gpgme1.0: CVE-2014-3564: heap-based buffer overflow in gpgsm status handler)

Your message dated Wed, 20 Aug 2014 19:02:05 + with message-id and subject line Bug#756651: fixed in gpgme1.0 1.2.0-1.4+deb7u1 has caused the Debian Bug report #756651, regarding gpgme1.0: CVE-2014-3564: heap-based buffer overflow in gpgsm status handler to be marked as done. This means that

Bug#718624: Binary package?

I just ran into this problem. I tried building the package myself, but I was unable to (got some message saying 'dh_auto_clean: invalid or non-existing path to the source directory: qt'). Probably just my inexperience in building from source. Anyway, if the bug is solved by this patch, could I

Bug#747670: marked as done (cryptsetup should depend on a version of cryptsetup-bin that support --type option)

Your message dated Wed, 20 Aug 2014 18:18:40 + with message-id and subject line Bug#747670: fixed in cryptsetup 2:1.6.6-1 has caused the Debian Bug report #747670, regarding cryptsetup should depend on a version of cryptsetup-bin that support --type option to be marked as done. This means th

Bug#753178: marked as done (hfsutils: FTBFS: dpkg-source: error: expected ^--- in line 1 of diff `hfsutils-3.2.6/debian/patches/man-macros.diff')

Your message dated Wed, 20 Aug 2014 18:04:26 + with message-id and subject line Bug#753178: fixed in hfsutils 3.2.6-13 has caused the Debian Bug report #753178, regarding hfsutils: FTBFS: dpkg-source: error: expected ^--- in line 1 of diff `hfsutils-3.2.6/debian/patches/man-macros.diff' to be

Processed: Debian bug #756794

Processing commands for cont...@bugs.debian.org: > fixed 756794 vsftpd/3.0.2-16 Bug #756794 [src:vsftpd] vsftpd: FTBFS on kfreebsd-* The source vsftpd and version 3.0.2-16 do not appear to match any binary packages Marked as fixed in versions vsftpd/3.0.2-16. > -- Stopping processing here. Pleas

Bug#758725: package mrpt_1:1.2.1-1 FTBFS on i386, amd64, mips*

Thanks a lot for your interest in fixing this, Jurica! I'm the upstream maintainer of mrpt, and was becoming desperate trying to debug in mips* for my lack of experience in cross-buidling, qemu, etc. So, on the build errors in mips (and other big-endian platforms): I *suspect* that some errors may

Bug#756980: klavaro: conflict with libgtkdatabox-0.9.2-0-dev

Well, Klavaro has migrated to GTK3, but gtkdatabox not yet. That's why I (Klavaro's upstream) have integrated the most up to date version from the git repo of gtkdatabox into Klavaro. I suggest to include a "conflicts" field while the transition to GTK3 does not occur also with libgtkdatabox upstre

Bug#744705: marked as done ([glpi] [DFSG] Missing sources)

Your message dated Wed, 20 Aug 2014 16:48:52 + with message-id and subject line Bug#744705: fixed in glpi 0.84.7+dfsg.1-2 has caused the Debian Bug report #744705, regarding [glpi] [DFSG] Missing sources to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#758579: thinkfan: Post Installation, Start Script fails to Initialize

control: tags -1 + moreinfo Dear submitter, On Mon, Aug 18, 2014 at 06:09:11PM -0400, Stephen Allen wrote: > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > After installation one expects the start script to function - maybe systemd > related? After reading

Processed: Re: Bug#758579: thinkfan: Post Installation, Start Script fails to Initialize

Processing control commands: > tags -1 + moreinfo Bug #758579 [thinkfan] thinkfan: Post Installation, Start Script fails to Initialize Added tag(s) moreinfo. -- 758579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#758579: thinkfan: Post Installation, Start Script fails to Initialize

Processing control commands: > tags -1 + moreinfo Bug #758579 [thinkfan] thinkfan: Post Installation, Start Script fails to Initialize Ignoring request to alter tags of bug #758579 to the same tags previously set -- 758579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758579 Debian Bug Trac

Bug#758725: package mrpt_1:1.2.1-1 FTBFS on i386, amd64, mips*

Package: mrpt Version: 1:1.2.1-1 Severity: serious Tags: sid Justification: FTBFS User: debian-mips-dev-disc...@lists.alioth.debian.org Hello, package mrpt_1:1.2.1-1 FTBFS on i386, amd64, mips* with the following message, but was previously built successfully on i386, amd64: i386 log: [---

Bug#758496: [Debian-astro-maintainers] Bug#758496: stellarium: Fails to start

On 20/08/14 15:59, Alexander Wolf wrote: > This is very odd, because OpenGL 3.0 contains OpenGL Shading Language 1.30 > and on this parameters Stellarium should work with guarantees. > > -- > With best regards, Alexander Exactly, this only reinforces my idea that it is not about GPU. @Martin, I

Bug#689109: Bug #689109 is now fixable

I have uploaded a new version of asterisk, which now Provides asterisk-$$AST_BUILDOPT_SUM, so bug #689109 should now be fixable. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Reopen #689109

Processing commands for cont...@bugs.debian.org: > notfixed 689109 asterisk/1:11.12.0~dfsg-1 Bug #689109 {Done: Jeremy Lainé } [asterisk-espeak] asterisk-espeak: app_espeak fails to load The source asterisk and version 1:11.12.0~dfsg-1 do not appear to match any binary packages No longer marked

Bug#689109: marked as done (asterisk-espeak: app_espeak fails to load)

Your message dated Wed, 20 Aug 2014 15:20:13 + with message-id and subject line Bug#689109: fixed in asterisk 1:11.12.0~dfsg-1 has caused the Debian Bug report #689109, regarding asterisk-espeak: app_espeak fails to load to be marked as done. This means that you claim that the problem has bee

Bug#758531: Better looking patch

Hi, On Wed, Aug 20, 2014 at 8:58 AM, Krzysztof A. Sobiecki wrote: > A better looking patch to disable parallel builds > > --- pulseaudio-5.0.orig/src/Makefile.am > +++ pulseaudio-5.0/src/Makefile.am > @@ -2195,3 +2195,4 @@ coverage: > endif > > .PHONY: massif update-all update-ffmpeg update-map

Bug#757676: marked as done (src:orthanc: full license text of CC-BY not included)

Your message dated Wed, 20 Aug 2014 13:34:58 + with message-id and subject line Bug#757676: fixed in orthanc 0.8.2+dfsg-1 has caused the Debian Bug report #757676, regarding src:orthanc: full license text of CC-BY not included to be marked as done. This means that you claim that the problem h

Bug#758687: uninstallable: xorg-server 1.16 transition

On 20/08/14 03:59, Cyril Brulebois wrote: > your package needs an update for the transition to xorg-server 1.16 > which happened in July. This is something any uploading DD can help with. Please could someone build and upload xserver-xorg-video-nv 1:2.1.20-3 on kfreebsd-amd64 and kfreebsd-i386, f

Bug#753510: marked as done (liblognorm1 - Conflicts against liblognorm0 without justification)

Your message dated Wed, 20 Aug 2014 13:19:46 + with message-id and subject line Bug#753510: fixed in liblognorm 1.0.1-3 has caused the Debian Bug report #753510, regarding liblognorm1 - Conflicts against liblognorm0 without justification to be marked as done. This means that you claim that th

Bug#758531: Better looking patch

A better looking patch to disable parallel builds --- pulseaudio-5.0.orig/src/Makefile.am +++ pulseaudio-5.0/src/Makefile.am @@ -2195,3 +2195,4 @@ coverage: endif .PHONY: massif update-all update-ffmpeg update-map-file coverage +.NOTPARALLEL: and a patch to disable tests as memblock-test fails

Bug#754359: marked as done (trousers: FTBFS on hurd-i386 and kfreebsd-any)

Your message dated Wed, 20 Aug 2014 12:49:32 + with message-id and subject line Bug#754359: fixed in trousers 0.3.13-2 has caused the Debian Bug report #754359, regarding trousers: FTBFS on hurd-i386 and kfreebsd-any to be marked as done. This means that you claim that the problem has been de

Bug#758643: lxc-create creates vulnerable system in default debian template

On 08/20/2014 10:55 AM, Ondřej Surý wrote: > So instead of improving the default debian template and fixing it for > everyone you just fixed the issue in your own code. That's not the way > we are ought to do the packaging instead of assuming bad faith, you could go with what really happened:

Bug#758585: marked as done (codelite: FTBFS on mips and mipsel due to lack of lldb-3.4-dev there)

Your message dated Wed, 20 Aug 2014 13:32:08 +0100 (BST) with message-id <691459220.13168.1408537928261.open-xcha...@oxbaltgw37.schlund.de> and subject line Bug #758585: codelite: FTBFS on mips and mipsel due to lack of lldb-3.4-dev there has caused the Debian Bug report #758585, regarding codeli

Bug#758688: [Pkg-libvirt-maintainers] Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed

Control: severity -1 important On Wed, Aug 20, 2014 at 12:25:09PM +0200, Guido Günther wrote: > > aptitude dist-upgrade failed at libvirt-daemon-system 1.2.7-9. > > What versions where you upgrading from? I think i do see the problem but want > to be sure. from 1.2.7-8. [cut] Preparing to unpa

Processed: Re: [Pkg-libvirt-maintainers] Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed

Processing control commands: > severity -1 important Bug #758688 [libvirt-daemon-system] libvirt-daemon-system (1.2.7-9) dist-upgrade failed Severity set to 'important' from 'grave' -- 758688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758688 Debian Bug Tracking System Contact ow...@bugs.

Bug#758688: From Which Version I Do The Upgrade

Hi! I tried it from 1.2.7-8 and have the same problem CU Michael Ott -- ,''`. : :' : Michael Ott `. `'e-mail: michael at king-coder dot de `- signature.asc Description: This is a digitally signed message part

Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed

Package: libvirt-daemon-system Version: 1.2.7-9 Followup-For: Bug #758688 I personally guess the prerm script assumes virtlockd service is up: deb-systemd-invoke stop virtlockd.socket virtlockd.service >/dev/null The installation can continue after the following command: deb-syste

Bug#758619: more complete backtrace

gdb --args python /usr/bin/reportbug -b --no-check-available libpulse0 GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute i

Bug#758640: [Python-modules-team] Bug#758640: python-celery-common: /usr/bin/celery wants 3.1.12 for 3.1.13 package

On 20 Aug 2014 00:24, "Eric Leblond" wrote: > Running celery binary results in an error and traceback: Thank you for your report. I hope to look into this tomorrow. (Celery is still usable, and works fine with django-celery; just the binaries won't work)

Bug#748671: marked as done (libnss-sss: Multiarch package removes configuration without reference counting)

Your message dated Wed, 20 Aug 2014 11:00:13 + with message-id and subject line Bug#748671: fixed in sssd 1.11.6-1 has caused the Debian Bug report #748671, regarding libnss-sss: Multiarch package removes configuration without reference counting to be marked as done. This means that you clai

Bug#758705: missing license in debian/copyright

Package: gnome-shell-pomodoro Version: 0.10.2-4 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: gnome-shell-pomodoro-0.10.2\vapi\libcanberra.vapi to debian/copyright. Thanks! T

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 746863 -moreinfo Bug #746863 {Done: Gianfranco Costamagna } [gccxml] insighttoolkit4: ftbfs with GCC-4.9 Ignoring request to alter tags of bug #746863 to the same tags previously set > thanks Stopping processing here. Please contact me if y

Bug#758688: [Pkg-libvirt-maintainers] Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed

On Mi., 20. Aug. 2014 06:20:50 CEST, d...@debian.org wrote: > Package: libvirt-daemon-system > Version: 1.2.7-9 > Severity: grave > > Dear Maintainer, > > aptitude dist-upgrade failed at libvirt-daemon-system 1.2.7-9. What versions where you upgrading from? I think i do see the problem but want

Bug#728955: libatomic-ops: patch from Ubuntu

Package: libatomic-ops Version: 7.4.2-1 Followup-For: Bug #728955 User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, the same problem occurs on ppc64el and here is a patch that provides : - a fix from Ubuntu - support for quilt patches with debian/source/format Hope that hel

Bug#757786: marked as done (pgrouting needs update to postgresql-9.4)

Your message dated Wed, 20 Aug 2014 10:00:06 + with message-id and subject line Bug#757786: fixed in pgrouting 2.0.0-3 has caused the Debian Bug report #757786, regarding pgrouting needs update to postgresql-9.4 to be marked as done. This means that you claim that the problem has been dealt w

Bug#758619: requested additional info

reportbug --template libgtk2.0-0 *** Welcome to reportbug.  Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect.

Bug#758699: mercurial-git: AttributeError: 'gitrepo' object has no attribute 'changegroup'

Package: mercurial-git Version: 0.4.0-2 Severity: grave I can't clone any git repository: $ hg clone git://anonscm.debian.org/collab-maint/pdf2djvu.git destination directory: pdf2djvu requesting all changes ** Unknown exception encountered with possibly-broken third-party extension git ** which

Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked

On Tue, 19 Aug 2014 at 12:08:39 +0200, Jan Binder wrote: > reportbug just aborts with exit code 134 when it is started. ... > > Attempt to unlock mutex that was not locked I can't reproduce this: "reportbug reportbug" (with the default text-mode UI) and "reportbug --ui=gtk2 reportbug" both seem to

Bug#758697: trying to overwrite shared '/usr/bin/policyeditor', which is different from other instances of package icedtea-netx:i386

Package: icedtea-netx Version: 1.5-2 Severity: grave Hello, got this error installing icedtea plugin for i386 (on an amd64 machine) apt-get install icedtea-netx:i386 Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The follow

Bug#758496: [Debian-astro-maintainers] Bug#758496: stellarium: Fails to start

This is very odd, because OpenGL 3.0 contains OpenGL Shading Language 1.30 and on this parameters Stellarium should work with guarantees. -- With best regards, Alexander

Bug#758643: lxc-create creates vulnerable system in default debian template

On Tue, Aug 19, 2014, at 18:39, Daniel Baumann wrote: > tag 758643 pending > forwarded 758643 https://github.com/lxc/lxc/issues/302 > thanks > > On 08/19/2014 05:10 PM, Ondřej Surý wrote: > > Attached is a simple fix that generates random password using pwgen > > package. > > my lxc-debconfig pre

Bug#758496: [Debian-astro-maintainers] Bug#758496: stellarium: Fails to start

Addendum: With LIBGL_ALWAYS_SOFTWARE=1 stellarium stderr changed as follows: 10,13c10,13 < OpenGL versions supported: "1.1, 1.2, 1.3, 1.4, 1.5, 2.0, 2.1, 3.0" < Driver version string: "3.0 Mesa 10.2.5" < GL vendor is "VMware, Inc." < GL renderer is "Gallium 0.4 on llvmpipe (LLVM 3.4, 128

Bug#758496: [Debian-astro-maintainers] Bug#758496: stellarium: Fails to start

I tried LIBGL_ALWAYS_SOFTWARE=1 stellarium The bug is still there, no change. Regards, Martin Am Mi 20 Aug 2014 10:18:00 CET schrieb Tomasz Buchert: Hi guys, I suspect it may have nothing to do with OpenGL. Could you please run this: LIBGL_ALWAYS_SOFTWARE=1 stellarium -- To UNSUBS

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 757120 important Bug #757120 [googleearth-package] The package doesn't build the debian file Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 757120: http://bugs.

Bug#757120: #757120: The package doesn't build the debian file

Hi Vincent > Il Martedì 19 Agosto 2014 10:20, Vincent Cheng ha scritto: > > On Tue, 5 Aug 2014 14:45:13 +0100 Gianfranco Costamagna > wrote: >>  Package: googleearth-package >>  Version: 1.1.0 >>  Severity: serious >>  Justification: makes the program almost useless >> >>  tags:patch >> >>

Bug#758496: [Debian-astro-maintainers] Bug#758496: stellarium: Fails to start

On 18/08/14 16:27, Martin Ziegler wrote: > Yes, libqt4-opengl ist installed, djview4 depends on it. > > When I saw #757150 [stellarium: Fails to display], I > removed libqt4-opengl and djview4. Unfortunately this did not help. > > > Regards > > Martin > Hi guys, I suspect it may have nothing

Processed: your mail

Processing commands for cont...@bugs.debian.org: > found 736038 4.1.1~ds0-2 Bug #736038 [src:photoprint] please build-depend on libtiff-dev, not libtiff4-dev The source 'photoprint' and version '4.1.1~ds0-2' do not appear to match any binary packages Marked as found in versions photoprint/4.1.1~

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reopen 736038 Bug #736038 {Done: Tobias Frost } [src:photoprint] please build-depend on libtiff-dev, not libtiff4-dev 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#758648: marked as done (mapsembler2 and discosnp: error when trying to install together)

Your message dated Wed, 20 Aug 2014 07:04:17 + with message-id and subject line Bug#758648: fixed in mapsembler2 2.2.1+dfsg-2 has caused the Debian Bug report #758648, regarding mapsembler2 and discosnp: error when trying to install together to be marked as done. This means that you claim tha

Bug#752963: marked as done (libxmltooling-java: FTBFS - missing artifact org.apache.maven.plugins:maven-javadoc-plugin:pom:2.9.1)

Your message dated Wed, 20 Aug 2014 07:03:57 + with message-id and subject line Bug#752963: fixed in libxmltooling-java 1.4.2-4 has caused the Debian Bug report #752963, regarding libxmltooling-java: FTBFS - missing artifact org.apache.maven.plugins:maven-javadoc-plugin:pom:2.9.1 to be marked