Bug#714295: Data corruption when using INIC-1623TA2 controller
Hello, On Sun, Jun 30, 2013 at 03:49:24PM +0100, Ben Hutchings wrote: So this does seem to be a fault in either this card or the driver. Can you suggest any further tests that Martin could do? Unfortunately, I don't have any idea. That driver never really matured enough. I couldn't find enough information and no one from initio responded, so -- tejun -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: downgrade severity for the moment
Processing control commands: severity -1 important Bug #713146 [libxml2] libxml 2.9.0 XPath evaluation issue Severity set to 'important' from 'serious' -- 713146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713146: downgrade severity for the moment
Control: severity -1 important I'm downgrading the severity to important for the moment to allow testing migration as I see the impact of this issue is quite limited. Thanks, Aron -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714595: liballegro4.2-dev: not installable in sid
Package: liballegro4.2-dev Version: 2:4.4.2-2.1 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hi, liballegro4.2-dev is not installable in sid since it depends on liballegro4.4 (= 2:4.4.2-2.1). However, the version of liballegro4.4 available in sid (on most architetures) is 2:4.4.2-3. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701308: libpam-unix2: ftbfs with GCC-4.8
Control: tag -1 patch pending
I had a look at the source for libpam-unix2, and am not quite sure what
the problem is, but suspect there is a missing semicolon after the calls
to __libc_lock_define_initialized().
This patch might fix it. Uploading to test the theory and try to keep
the package in testing.
--- src/read-files.c.orig 2013-07-01 09:01:37.0 +0200
+++ src/read-files.c2013-07-01 09:08:05.0 +0200
@@ -341,7 +341,7 @@
char *buffer, size_t buflen, int *errnop)
{
/* Locks the static variables in this file. */
- __libc_lock_define_initialized (static, lock)
+ __libc_lock_define_initialized (static, lock);
enum nss_status status;
FILE *stream = NULL;
@@ -371,7 +371,7 @@
char *buffer, size_t buflen, int *errnop)
{
/* Locks the static variables in this file. */
- __libc_lock_define_initialized (static, lock)
+ __libc_lock_define_initialized (static, lock);
enum nss_status status;
FILE *stream = NULL;
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: libpam-unix2: ftbfs with GCC-4.8
Processing control commands: tag -1 patch pending Bug #701308 [src:libpam-unix2] libpam-unix2: ftbfs with GCC-4.8 Added tag(s) pending and patch. -- 701308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714458: ghc-mod: Error:No entry for target has .ident directive in /usr/lib/ghc/settings
Control: retitle -1 ghc-mod needs to be tied to GHC version Control: tag -1 + confirmed jessie Hi, I don’t know ghc-mod very well, but Am Samstag, den 29.06.2013, 17:49 +0200 schrieb Paolo Inaudi: Bad interface file: /usr/lib/ghc/base-4.5.0.0/Prelude.himismatched interface file versions (wanted 7063, got 7041) it seems that ghc-mod only works with the GHC version it is built with (here, 7.6.3), while you have 7.4.1. So * ghc-mod needs a Depends: added on the correct GHC version and * we need to rebuild ghc-mod in testing, probably via testing-proposed-updates. Kiwamu, can you take care of that? Thanks, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Processed: Re: ghc-mod: Error:No entry for target has .ident directive in /usr/lib/ghc/settings
Processing control commands: retitle -1 ghc-mod needs to be tied to GHC version Bug #714458 [ghc-mod] ghc-mod: Error:No entry for target has .ident directive in /usr/lib/ghc/settings Changed Bug title to 'ghc-mod needs to be tied to GHC version' from 'ghc-mod: Error:No entry for target has .ident directive in /usr/lib/ghc/settings' tag -1 + confirmed jessie Bug #714458 [ghc-mod] ghc-mod needs to be tied to GHC version Added tag(s) confirmed and jessie. -- 714458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714596: jenkins build-depends on itself: impossible to bootstrap
Package: jenkins Version: 1.480.3+dfsg-1~exp2 Severity: serious Hi James, I've been trying to build a Wheezy backport of Jenkins, and I almost succeeded, until it went down to build Jenkins itself. Jenkins Build-Depends: on libjenkins-plugin-parent-java, but this package is in fact one of the binaries made by the jenkins source package. The same way, jenkins-instance-identity and jenkins-ssh-cli-auth both build-depends on libjenkins-plugin-parent-java, but jenkins build-depends on jenkins-instance-identity and jenkins-ssh-cli-auth. Because of the above, it is impossible to bootstrap Jenkins from scratch. Thanks for maintaining this complicated software in Debian, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714514: marked as done (libsasl2-dev does not depends against libsasl2-2 package)
Your message dated Mon, 01 Jul 2013 07:48:15 + with message-id e1utyqn-00038b...@franck.debian.org and subject line Bug#714514: fixed in cyrus-sasl2 2.1.25.dfsg1-12 has caused the Debian Bug report #714514, regarding libsasl2-dev does not depends against libsasl2-2 package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 714514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libsasl2-dev Version: 2.1.25.dfsg1-11 Severity: serious Hi, The libsasl2-dev is missing a dependency against libsasl2-2, this makes libvirt package FTBFS. In the past libsasl-2 was pulled by libsasl2-modules but this is not the case anymore in version -11. An explicit dependency should be added. Cheers Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libsasl2-dev depends on: ii libc6-dev 2.17-7 ii libsasl2-modules 2.1.25.dfsg1-11 libsasl2-dev recommends no packages. libsasl2-dev suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: cyrus-sasl2 Source-Version: 2.1.25.dfsg1-12 We believe that the bug you reported is fixed in the latest version of cyrus-sasl2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 714...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated cyrus-sasl2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 09:25:05 +0200 Source: cyrus-sasl2 Binary: sasl2-bin cyrus-sasl2-doc libsasl2-2 libsasl2-modules libsasl2-modules-ldap libsasl2-modules-otp libsasl2-modules-sql libsasl2-modules-gssapi-mit libsasl2-dev libsasl2-modules-gssapi-heimdal cyrus-sasl2-dbg cyrus-sasl2-mit-dbg cyrus-sasl2-heimdal-dbg Architecture: source amd64 all Version: 2.1.25.dfsg1-12 Distribution: unstable Urgency: low Maintainer: Debian Cyrus SASL Team pkg-cyrus-sasl2-debian-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: cyrus-sasl2-dbg - Cyrus SASL - debugging symbols cyrus-sasl2-doc - Cyrus SASL - documentation cyrus-sasl2-heimdal-dbg - Cyrus SASL - debugging symbols for Heimdal modules cyrus-sasl2-mit-dbg - Cyrus SASL - debugging symbols for MIT modules libsasl2-2 - Cyrus SASL - authentication abstraction library libsasl2-dev - Cyrus SASL - development files for authentication abstraction lib libsasl2-modules - Cyrus SASL - pluggable authentication modules libsasl2-modules-gssapi-heimdal - Pluggable Authentication Modules for SASL (GSSAPI) libsasl2-modules-gssapi-mit - Cyrus SASL - pluggable authentication modules (GSSAPI) libsasl2-modules-ldap - Cyrus SASL - pluggable authentication modules (LDAP) libsasl2-modules-otp - Cyrus SASL - pluggable authentication modules (OTP) libsasl2-modules-sql - Cyrus SASL - pluggable authentication modules (SQL) sasl2-bin - Cyrus SASL - administration programs for SASL users database Closes: 714514 Changes: cyrus-sasl2 (2.1.25.dfsg1-12) unstable; urgency=low . * Change depend on libsasl2-modules to libsasl2-2 in libsasl2-dev (Closes: #714514) Checksums-Sha1: 86584363e6a805162a605b3f4e577b551e1710b4 2560 cyrus-sasl2_2.1.25.dfsg1-12.dsc 51cca046dfdb6b3679ba13a150a9098f708e22cf 107106 cyrus-sasl2_2.1.25.dfsg1-12.debian.tar.gz a9010d18b419c093dc6c67451a84782c99315a8b 184396 sasl2-bin_2.1.25.dfsg1-12_amd64.deb 1cac04522a73cf99adba3a77d32d9958fdcc1a7d 113172 cyrus-sasl2-doc_2.1.25.dfsg1-12_all.deb a0ec3502519e1569fc2b70529f25118ecee79065 108586 libsasl2-2_2.1.25.dfsg1-12_amd64.deb 8f85e797092bd075b193419c05709e58e5cf6669 122672 libsasl2-modules_2.1.25.dfsg1-12_amd64.deb 17b8010ef676501d12fa2ebde7c2f69f115a1d30 64238 libsasl2-modules-ldap_2.1.25.dfsg1-12_amd64.deb 17590d2a461dd2149cd1da93ad30bc6a71426181 88674
Bug#711789: grads: unbuildable (build-dependencies conflict)
And attached is exact debdiff of what I have just uploaded to DELAYED/0. O. On Thu, Jun 27, 2013 at 10:48 AM, Ondřej Surý ond...@debian.org wrote: Package: src:grads Followup-For: Bug #711789 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear maintainer, please apply attached patch to use libtiff5-alt-dev instead of libtiff5-dev. The libtiff5-dev libtiff4-dev conflicts makes downstream packages (namely grads) unbuildable and it's blocking the libgd2 transition. I plan to NMU the package if I don't hear from you soon (it's RC severity bug). The changes I did are minimal - the other option would be to make upstream configure.ac to use pkg-config (which would be more elegant, but also more intrusive). Thanks, O. - -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHL/GkACgkQ9OZqfMIN8nPcogCfSd/WByakSLYRqY4MJhHPOdKU ajoAn2bNUscvb0F06wYhsd3qVhJhwpfg =hw+h -END PGP SIGNATURE- -- Ondřej Surý ond...@sury.org libgeotiff-dfsg_1.3.0+dfsg-3.1.debdiff Description: Binary data
Processed: Re: libpam-unix2: ftbfs with GCC-4.8
Processing control commands: tags -1 - pending patch Bug #701308 [src:libpam-unix2] libpam-unix2: ftbfs with GCC-4.8 Removed tag(s) pending and patch. -- 701308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701308: libpam-unix2: ftbfs with GCC-4.8
Control: tags -1 - pending patch [Petter Reinholdtsen] This patch might fix it. Uploading to test the theory and try to keep the package in testing. Actually, while trying to upload I discovered that the real problem is that the __libc_lock_define_initialized() macro is no longer provided by bits/libc-lock.h in libc6-dev. I am not sure how to fix that. I suspect the entire lock handling need to be rewritten. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701308: pam-unix2 no longer build with latest glibc headers
Hi, Thorsten. I was looking at a build failure for libpam-unix2 in the latest Debian build environment, and discovered that the problem is that it is using a set of lock macros no longer provided by libc. I fetched the latest version from URL: ftp://ftp.suse.com/pub/people/kukuk/pam/pam_unix2/ . This is the build error with version 2.6: read-files.c: In function 'files_getspnam_r': read-files.c:344:3: warning: implicit declaration of function '__libc_lock_define_initialized' [-Wimplicit-function-declaration] read-files.c:344:35: error: expected expression before 'static' read-files.c:345:3: error: expected ';' before 'enum' read-files.c:348:3: warning: implicit declaration of function '__libc_lock_lock' [-Wimplicit-function-declaration] read-files.c:348:21: error: 'lock' undeclared (first use in this function) read-files.c:348:21: note: each undeclared identifier is reported only once for each function it appears in read-files.c:350:3: error: 'status' undeclared (first use in this function) read-files.c:364:3: warning: implicit declaration of function '__libc_lock_unlock' [-Wimplicit-function-declaration] read-files.c: In function 'files_getpwnam_r': read-files.c:374:35: error: expected expression before 'static' read-files.c:375:3: error: expected ';' before 'enum' read-files.c:378:21: error: 'lock' undeclared (first use in this function) read-files.c:380:3: error: 'status' undeclared (first use in this function) read-files.c:397:1: warning: control reaches end of non-void function [-Wreturn-type] read-files.c: In function 'files_getspnam_r': read-files.c:367:1: warning: control reaches end of non-void function [-Wreturn-type] Perhaps time to make a new release? If you consider making a new release, please see if some of the Debian patches available from URL: http://sources.debian.net/src/libpam-unix2/1:2.4.1-6/debian/patches should be included. All of them seem to apply cleanly to 2.6 even if they were written for 2.4.1. Information about the Debian package is available from URL: http://packages.qa.debian.org/libp/libpam-unix2.html . -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 714545 to gnome-shell, forcibly merging 712861 714545
Processing commands for cont...@bugs.debian.org:
reassign 714545 gnome-shell 3.4.2-8
Bug #714545 [gnome] gnome doesn't start
Bug reassigned from package 'gnome' to 'gnome-shell'.
No longer marked as found in versions meta-gnome3/1:3.8+2.
Ignoring request to alter fixed versions of bug #714545 to the same values
previously set
Bug #714545 [gnome-shell] gnome doesn't start
Marked as found in versions gnome-shell/3.4.2-8.
forcemerge 712861 714545
Bug #712861 {Done: Emilio Pozuelo Monfort po...@debian.org} [gnome-shell]
gnome-bluetooth: Breaks gnome-shell: GnomeBluetoothApplet.KillswitchState is
undefined
Bug #712926 {Done: Ludovic Lebègue ludo...@lebegue.org} [gnome-shell]
gnome-shell: Execution of main.js threw exception: TypeError:
GnomeBluetoothApplet.KillswitchState is undefined
Bug #714545 [gnome-shell] gnome doesn't start
Severity set to 'serious' from 'grave'
Marked Bug as done
Added tag(s) sid and jessie.
Bug #712926 {Done: Ludovic Lebègue ludo...@lebegue.org} [gnome-shell]
gnome-shell: Execution of main.js threw exception: TypeError:
GnomeBluetoothApplet.KillswitchState is undefined
Merged 712861 712926 714545
thanks
Stopping processing here.
Please contact me if you need assistance.
--
712861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712861
712926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712926
714545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701250: Camitk Debian package needs some love [was: Candidates for removal from testing (2013-06-30)]
Hi Emmanuel,
as you can read below camitk needs some love. If you have trouble
caring for it it is perfectly fine to contact the list Debian Med list
and ask for help. I just wanted to make sure you are aware of this
problem.
It might be a good idea to use the package tracking system to subscribe
this package.
Kind regards
Andreas.
- Forwarded message from Niels Thykier ni...@thykier.net -
Date: Sun, 30 Jun 2013 23:32:18 +0200 (CEST)
From: Niels Thykier ni...@thykier.net
To: debian-de...@lists.debian.org
Cc: debian-rele...@lists.debian.org
Subject: Candidates for removal from testing (2013-06-30)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
We are considering removing the following packages from testing as
they have unfixed RC bugs filed against them. The packages can be
found in the attached dd-list.
The packages have been selected based on the following criteria:
- The package had at least one RC bug without activity for the past
14 days.
- If a bug is assigned to multiple packages, both packages will
be affected[1].
- The RC bug affects both unstable and testing.
- The affected package does not have any reverse dependencies in
testing.
- One of their RC bugs had FTBFS in their title. (*)
- The source package had a popcon inst value of 500 or less. (*)
(*) These extra filter rules was applied to keep the list down. The
original list was 246.
If the relevant RC bugs in the affected packages (those listed in
FTBFS-w-popcon-lt-500.txt) are not dealt with before the 8th of
July, the packages will be removed from testing. Note that dealt
with may also include downgrading a severity-inflated bug or fixing
affected versions in the BTS.
For reference, the original list is also included.
Thanks,
Niels (on behalf of the Release Team)
PS: This mail has been BCC'ed to pkg@packages.debian.org for
packaged listed in FTBFS-w-popcon-lt-500.txt.
8 FTBFS-w-popcon-lt-500.txt 8
BUG [SRC]: TITLE
#712367 [bashdb]: bashdb: FTBFS: manuals build fails against textinfo5 because
some incompatibles changes wrt 4.13 and below (some warnings have turned into
errors)
#711787 [falconpl]: falconpl: FTBFS on mipsen
#701412 [prelude-manager]: prelude-manager: ftbfs with eglibc-2.17
#712329 [epix]: epix: FTBFS: manuals build fails against textinfo5 because some
incompatibles changes wrt 4.13 and below (some warnings have turned into errors)
#710633 [orafce]: orafce: FTBFS: plvlex.c:209:3: error: too many arguments to
function 'orafce_sql_yyparse'
#707399 [gedit-valencia-plugin]: gedit-valencia-plugin: FTBFS:
GIRepository-2.0.gir:240.11-240.30: error: expected start element of `parameter'
#710614 [bip]: bip: FTBFS: lex.l:19:6: error: conflicting types for 'yyparse'
#701319 [massxpert]: massxpert: ftbfs with GCC-4.8
#701334 [openvrml]: openvrml: ftbfs with GCC-4.8
#701328 [nwchem]: nwchem: ftbfs with GCC-4.8
#701367 [toonloop]: toonloop: ftbfs with GCC-4.8
#712321 [oneliner-el]: oneliner-el: FTBFS: manuals build fails against
textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings
have turned into errors)
#701411 [prelude-lml]: prelude-lml: ftbfs with eglibc-2.17
#701348 [rnahybrid]: rnahybrid: ftbfs with GCC-4.8
#710636 [mididings]: mididings: FTBFS: src/python_caller.cc:151:42: error:
expected unqualified-id before numeric constant
#701438 [charybdis]: charybdis: ftbfs with eglibc-2.17
#708692 [dnsjava]: FTBFS: requires internet connectivity
#712344 [cfi]: cfi: FTBFS: Package babel Error: Unknow option `swedish'. Either
you misspelled it
#707373 [libccaudio2]: libccaudio2: FTBFS: friends.cpp:1189:25: error:
'ACCESS_DIRECTORY' is not a member of 'ucommon::fsys'
#701300 [ivtools]: ivtools: ftbfs with GCC-4.8
#701428 [turnserver]: turnserver: ftbfs with eglibc-2.17
#712349 [cdk]: cdk: FTBFS: This CDK release requires Ant 1.7.1 or better
#701342 [psychtoolbox-3]: psychtoolbox-3: ftbfs with GCC-4.8
#707411 [zoneminder]: zoneminder: FTBFS: zm_local_camera.cpp:742:49: error:
invalid conversion from '__u32 {aka unsigned int}' to 'v4l2_buf_type'
[-fpermissive]
#712327 [freepops]: freepops: FTBFS: Package babel Error: You haven't specified
a language option.
#711628 [libhttp-daemon-ssl-perl]: libhttp-daemon-ssl-perl: FTBFS: test failure
#701317 [mailavenger]: mailavenger: ftbfs with GCC-4.8
#711367 [python-django-localeurl]: python-django-localeurl: FTBFS:
NoReverseMatch: 'url' requires a non-empty first argument
#701298 [ion]: ion: ftbfs with GCC-4.8
#701281 [gcc-msp430]: gcc-msp430: ftbfs with GCC-4.8
#707420 [sdpnetstat]: sdpnetstat: FTBFS: strip.c:24:28: fatal error:
linux/if_strip.h: No such file or directory
#710501 [avinfo]: avinfo: FTBFS: ass.tab.h:104:5: error: conflicting types for
'yyparse'
#707501 [rpy]: rpy: FTBFS: grep: ecrm1095.log: No such file or directory
#708808 [nant]: nant: FTBFS: [csc] Cannot open assembly
'/usr/lib/mono/4.0/dmcs.exe': No such file or directory.
#706176 [openjpa]: FTBFS with hsqldb
Bug#714295: Data corruption when using INIC-1623TA2 controller
Hello, On Sun., 2013-06-30 at 23:17 -0700, Tejun Heo wrote: Unfortunately, I don't have any idea. That driver never really matured enough. I couldn't find enough information and no one from initio responded, so Thank you Tejun and Ben, that's totally suxx. I'm gonna try to contact them too, but I doubt it's gonna change anything :( I was hopping that we could turn on some logging so that we understand, at least, what is happening (even if we can't solve it), and I could then have made some tests by modifying code, recompiling module, ... If the driver could cause data loss, shouldn't it be flagged as experimental? In the meantime, I'm probably going to purchase a new SATA card :( Thanks again guys for your hard work! I really appreciate! Martin -- Martin Braure de Calignon signature.asc Description: This is a digitally signed message part
Bug#714545: gnome doesn't start
Package: gnome-shell Version: 3.4.2-8 Followup-For: Bug #714545 Dear Maintainer, I'm also affected by this bug. But downgrading the mentioned packages didn't solve the problem for me. Which version of the packages are required? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (900, 'stable'), (600, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backe 0.16.0-4 ii gconf-service 3.2.6-1 ii gir1.2-accountsservice-1.00.6.30-2 ii gir1.2-caribou-1.00.4.4-1 ii gir1.2-clutter-1.01.10.8-2 ii gir1.2-folks-0.6 0.6.9-1+b1 ii gir1.2-freedesktop1.36.0-2+b1 ii gir1.2-gconf-2.0 3.2.6-1 ii gir1.2-gcr-3 3.8.2-3 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.36.0-2+b1 ii gir1.2-gmenu-3.0 3.8.0-2 ii gir1.2-gnomebluetooth-1.0 3.8.0-1 ii gir1.2-gtk-3.03.4.2-6 ii gir1.2-mutter-3.0 3.4.1-7 ii gir1.2-networkmanager-1.0 0.9.8.0-5 ii gir1.2-pango-1.0 1.32.5-5+b1 ii gir1.2-polkit-1.0 0.105-3 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.12 0.20.2-2 ii gir1.2-telepathylogger-0.20.4.0-1 ii gir1.2-upowerglib-1.0 0.9.20-2 ii gjs 1.32.0-5+b1 ii gnome-bluetooth 3.8.0-1 ii gnome-icon-theme-symbolic 3.8.2.2-2 ii gnome-settings-daemon 3.4.2+git20121218.7c1322-3+deb7u1 ii gnome-shell-common3.4.2-8 ii gnome-themes-standard 3.4.2-2.1 ii gsettings-desktop-schemas 3.4.2-3 ii libatk1.0-0 2.8.0-2 ii libc6 2.17-6 ii libcairo-gobject2 1.12.14-4 ii libcairo2 1.12.14-4 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.10.8-2 ii libcogl-pango01.10.2-7 ii libcogl9 1.10.2-7 ii libcroco3 0.6.8-2 ii libdbus-1-3 1.6.12-1 ii libdbus-glib-1-2 0.100.2-1 ii libebook-1.2-13 3.4.4-3 ii libecal-1.2-113.4.4-3 ii libedataserver-1.2-16 3.4.4-3 ii libedataserverui-3.0-13.4.4-3 ii libfolks250.6.9-1+b1 ii libgck-1-03.8.2-3 ii libgconf-2-4 3.2.6-1 ii libgcr-3-13.8.2-3 ii libgdk-pixbuf2.0-02.28.2-1 ii libgee2 0.6.8-1 ii libgirepository-1.0-1 1.36.0-2+b1 ii libgjs0b [libgjs0-libmozjs185-1.0]1.32.0-5+b1 ii libgl1-mesa-glx [libgl1] 8.0.5-6 ii libglib2.0-0 2.36.3-2 ii libgnome-keyring0 3.4.1-1 ii libgnome-menu-3-0 3.8.0-2 ii libgstreamer0.10-00.10.36-1.2 ii libgtk-3-03.4.2-6 ii libical0 0.48-2 ii libjson-glib-1.0-00.14.2-1 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4+b1 ii libmutter03.4.1-7 ii libnm-glib4 0.9.8.0-5 ii libnm-util2 0.9.8.0-5 ii libnspr4 2:4.10-1 ii libnspr4-0d 2:4.10-1 ii libp11-kit0 0.18.3-2 ii libpango-1.0-01.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpolkit-agent-1-0 0.105-3 ii libpolkit-gobject-1-0 0.105-3 ii libpulse-mainloop-glib0 2.0-6.1 ii libpulse0 2.0-6.1 ii libsoup2.4-1 2.38.1-2 ii libstartup-notification0 0.12-3 ii libtelepathy-glib00.20.2-2 ii libtelepathy-logger2 0.4.0-1 ii libx11-6 2:1.6.0-1 ii libxcomposite1
Bug#701438: marked as done (charybdis: ftbfs with eglibc-2.17)
Your message dated Mon, 01 Jul 2013 09:01:13 + with message-id e1utzyz-00067z...@franck.debian.org and subject line Bug#701438: fixed in charybdis 3.4.2-1 has caused the Debian Bug report #701438, regarding charybdis: ftbfs with eglibc-2.17 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:charybdis Version: 3.3.0-7.1 Severity: important Tags: sid jessie User: debian-gl...@lists.debian.org Usertags: ftbfs-glibc-2.17 The package fails to build in a test rebuild on at least amd64 with eglibc-2.17, but succeeds to build with eglibc-2.13. The severity of this report may be raised before the jessie release. The test rebuild was done together with GCC-4.8, so some issues might be caused by the updated GCC as well. sigio.c:238:17: error: storage size of 'si' isn't known The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/charybdis_3.3.0-7.1_unstable_gcc48.log The last lines of the build log are at the end of this report. To install eglibc from experimental, apt-get -t experimental install libc6-dev To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev [...] mv -f .deps/gnutls.Tpo .deps/gnutls.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT nossl.lo -MD -MP -MF .deps/nossl.Tpo -c -o nossl.lo nossl.c mv -f .deps/nossl.Tpo .deps/nossl.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT event.lo -MD -MP -MF .deps/event.Tpo -c -o event.lo event.c mv -f .deps/event.Tpo .deps/event.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT ratbox_lib.lo -MD -MP -MF .deps/ratbox_lib.Tpo -c -o ratbox_lib.lo ratbox_lib.c mv -f .deps/ratbox_lib.Tpo .deps/ratbox_lib.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT rb_memory.lo -MD -MP -MF .deps/rb_memory.Tpo -c -o rb_memory.lo rb_memory.c mv -f .deps/rb_memory.Tpo .deps/rb_memory.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT linebuf.lo -MD -MP -MF .deps/linebuf.Tpo -c -o linebuf.lo linebuf.c mv -f .deps/linebuf.Tpo .deps/linebuf.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT snprintf.lo -MD -MP -MF .deps/snprintf.Tpo -c -o snprintf.lo snprintf.c mv -f .deps/snprintf.Tpo .deps/snprintf.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT tools.lo -MD -MP -MF .deps/tools.Tpo -c -o tools.lo tools.c mv -f .deps/tools.Tpo .deps/tools.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT helper.lo -MD -MP -MF .deps/helper.Tpo -c -o helper.lo helper.c mv -f .deps/helper.Tpo .deps/helper.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT devpoll.lo -MD -MP -MF .deps/devpoll.Tpo -c -o devpoll.lo devpoll.c mv -f .deps/devpoll.Tpo .deps/devpoll.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I. -I../include -I/usr/include/p11-kit-1 -g -O2 -Wall -MT epoll.lo -MD -MP -MF .deps/epoll.Tpo -c -o epoll.lo epoll.c epoll.c: In function 'rb_epoll_sched_event_signalfd': epoll.c:400:23: warning: argument to 'sizeof' in 'memset' call is the same expression as the destination; did you mean to remove the addressof? [-Wsizeof-pointer-memaccess] memset(ev, 0, sizeof(ev)); ^ mv -f .deps/epoll.Tpo .deps/epoll.Plo /bin/bash ../libtool --silent --tag=CC --mode=compile gcc
Bug#714545: (no subject)
Ok, downgrading to the following versions worked for me: libnm-gtk0 0.9.8.2-1 libnm-gtk-common 0.9.8.2-1 network-manager-gnome 0.9.8.2-1 gnome-bluetooth 3.4.2-1 gir1.2-gnomebluetooth-1.0 3.4.2-1 libgnome-bluetooth11:amd64 can be removed (I didn't realize they where in the brackets in message #10) I got the packages from: http://snapshot.debian.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682826: marked as done (ilisp: creates world writable directory /usr/lib/ilisp)
Your message dated Mon, 01 Jul 2013 09:20:29 + with message-id e1utahd-gl...@franck.debian.org and subject line Bug#682826: fixed in ilisp 5.12.0+cvs.2004.12.26-18 has caused the Debian Bug report #682826, regarding ilisp: creates world writable directory /usr/lib/ilisp to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 682826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ilisp Version: 5.12.0+cvs.2004.12.26-17 Severity: grave Tags: security Justification: user security hole User: debian...@lists.debian.org Usertags: piuparts Hi, ilisp creates the following directory drwxrwxrwx 2 root root 300 Jul 22 22:03 /usr/lib/ilisp with this postinst snippet: chmod 777 /usr/lib/ilisp # Required so that users can build .fasl files That directory contains symlinks to various *.lisp files which may now be replaced by any local user... I don't use ilisp, I don't speak lisp, I just wrote the piuparts check for world writable directories :-) Andreas ---End Message--- ---BeginMessage--- Source: ilisp Source-Version: 5.12.0+cvs.2004.12.26-18 We believe that the bug you reported is fixed in the latest version of ilisp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 682...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter b...@debian.org (supplier of updated ilisp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 09:48:08 +0100 Source: ilisp Binary: ilisp ilisp-doc Architecture: source all Version: 5.12.0+cvs.2004.12.26-18 Distribution: unstable Urgency: low Maintainer: Barak A. Pearlmutter b...@debian.org Changed-By: Barak A. Pearlmutter b...@debian.org Description: ilisp - Emacs interface to LISP implementations ilisp-doc - Documentation for ILISP package Closes: 680646 682826 68 Changes: ilisp (5.12.0+cvs.2004.12.26-18) unstable; urgency=low . * add emacs24 support (closes: #680646) * update some constructs that annoy the elisp compiler * stop making /etc/ilisp/ilisp-keybindings.el a conf file (closes: #68) * restrict writes in global .fasl directory to group ilisp (closes: #682826) Checksums-Sha1: 387490153b8f78cc2f6ac862b8f7e053a49e2571 1396 ilisp_5.12.0+cvs.2004.12.26-18.dsc d656b6cdb0a9bcbaaeb0f56bac8bc74ccf0e3773 103662 ilisp_5.12.0+cvs.2004.12.26-18.debian.tar.gz 145aa5ca44879921706aae43139a06ab4cc9fbbc 268574 ilisp_5.12.0+cvs.2004.12.26-18_all.deb 7c5b95a442906a3a1aa0dfe7bcef1488fd02f6c9 357968 ilisp-doc_5.12.0+cvs.2004.12.26-18_all.deb Checksums-Sha256: 1412858a9c52d2b525470df6c4355fcade9b61388e18d22a6bebf82fe12b3761 1396 ilisp_5.12.0+cvs.2004.12.26-18.dsc eb504e5b99a2081d30a87226ceeb0fa259a466ac64812daddb57e957c13f0025 103662 ilisp_5.12.0+cvs.2004.12.26-18.debian.tar.gz 9b281a875c938c6e2700047da187dfa3ad0577be62976b8c49922872c9c74690 268574 ilisp_5.12.0+cvs.2004.12.26-18_all.deb d9304b5e12957ca3cada98c73564933b003120486f8252695478caff2f3b307b 357968 ilisp-doc_5.12.0+cvs.2004.12.26-18_all.deb Files: 5d4dd882ac481c6efc4fe521c4d18dda 1396 devel optional ilisp_5.12.0+cvs.2004.12.26-18.dsc 257fcf4750023e14af72e9114a8561c2 103662 devel optional ilisp_5.12.0+cvs.2004.12.26-18.debian.tar.gz aae2b66c4ad4bcfde0e8d13f684f13d3 268574 devel optional ilisp_5.12.0+cvs.2004.12.26-18_all.deb 75fb8b2baf67a47d06418498a1dbe12c 357968 doc optional ilisp-doc_5.12.0+cvs.2004.12.26-18_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHRSAIACgkQLz4Gnv7CP7IoDgCfQ+Ru13kF37I8w5+tfrARAtm/ 2CkAnjy46Ep22hyR/m/ya9sz7V+D88ma =RIhm -END PGP SIGNATUREEnd Message---
Bug#714603: python3-morse-simulator: fails to upgrade from wheezy - trying to overwrite /usr/lib/python3/dist-packages/morse/__init__.py
Package: morse-simulator,python3-morse-simulator Version: 1.0.1-2.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package python3-morse-simulator. Unpacking python3-morse-simulator (from .../python3-morse-simulator_1.0.1-2.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/python3-morse-simulator_1.0.1-2.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/morse/__init__.py', which is also in package morse-simulator 0.5.2-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas morse-simulator_1.0.1-2.1.log.gz Description: GNU Zip compressed data
Bug#701348: marked as done (rnahybrid: ftbfs with GCC-4.8)
Your message dated Mon, 01 Jul 2013 09:20:52 +
with message-id e1utai1-vf...@franck.debian.org
and subject line Bug#701348: fixed in rnahybrid 2.1.1-2
has caused the Debian Bug report #701348,
regarding rnahybrid: ftbfs with GCC-4.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
701348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:rnahybrid
Version: 2.1.1-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.8
The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.
XXX
The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/rnahybrid_2.1.1-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.
To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev
The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.
[...]
rnaeffective.c:288:16: warning: incompatible implicit declaration of built-in
function 'strlen' [enabled by default]
seqlen = strlen(query_sq);
^
rnaeffective.c:299:20: warning: incompatible implicit declaration of built-in
function 'strchr' [enabled by default]
index_one = (int) strchr(alphabet,letter_one);
^
rnaeffective.c:299:14: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
index_one = (int) strchr(alphabet,letter_one);
^
rnaeffective.c:300:14: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
index_two = (int) strchr(alphabet,letter_two);
^
rnaeffective.c:303:22: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
freq_di[index_one-(int) alphabet][index_two-(int) alphabet]++;
^
rnaeffective.c:303:48: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
freq_di[index_one-(int) alphabet][index_two-(int) alphabet]++;
^
rnaeffective.c:346:15: warning: incompatible implicit declaration of built-in
function 'strlen' [enabled by default]
for (i=0; istrlen(alphabet); i++) {
^
rnaeffective.c:436:6: warning: incompatible implicit declaration of built-in
function 'strcpy' [enabled by default]
strcpy(x, );
^
rnaeffective.c:437:6: warning: incompatible implicit declaration of built-in
function 'strcat' [enabled by default]
strcat(x, target_sq);
^
rnaeffective.c:565:6: warning: incompatible implicit declaration of built-in
function 'strcpy' [enabled by default]
strcpy(x, );
^
rnaeffective.c:566:6: warning: incompatible implicit declaration of built-in
function 'strcat' [enabled by default]
strcat(x, target_sq);
^
x86_64-linux-gnu-gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -Wl,-z,defs -o RNAeffective rnaeffective.o
hybrid_core.o numerical.o energy.o input.o fasta.o random.o mt19937-1.o plot.o
-lg2 -lm
make[3]: Leaving directory `/«PKGBUILDDIR»/src'
Making all in man
make[3]: Entering directory `/«PKGBUILDDIR»/man'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/«PKGBUILDDIR»/man'
make[3]: Entering directory `/«PKGBUILDDIR»'
make[3]: Leaving directory `/«PKGBUILDDIR»'
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: Leaving directory `/«PKGBUILDDIR»'
debian/rules override_dh_auto_test
make[1]: Entering directory `/«PKGBUILDDIR»'
src/RNAhybrid -s 3utr_worm -t examples/cel-hbl-1.fasta -q
examples/cel-let-7.fasta
make[1]: *** [override_dh_auto_test] Segmentation fault
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
---End Message---
---BeginMessage---
Source: rnahybrid
Source-Version: 2.1.1-2
We believe that the bug you reported is fixed in the latest version of
rnahybrid, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
Bug#688888: marked as done (ilisp: modifies conffiles (policy 10.7.3): /etc/ilisp/ilisp-keybindings.el)
Your message dated Mon, 01 Jul 2013 09:20:29 + with message-id e1utahd-gs...@franck.debian.org and subject line Bug#68: fixed in ilisp 5.12.0+cvs.2004.12.26-18 has caused the Debian Bug report #68, regarding ilisp: modifies conffiles (policy 10.7.3): /etc/ilisp/ilisp-keybindings.el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 68: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=68 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ilisp Version: 5.12.0+cvs.2004.12.26-17 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/ilisp/ilisp-keybindings.el cheers, Andreas ilisp_5.12.0+cvs.2004.12.26-17.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: ilisp Source-Version: 5.12.0+cvs.2004.12.26-18 We believe that the bug you reported is fixed in the latest version of ilisp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 688...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter b...@debian.org (supplier of updated ilisp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 09:48:08 +0100 Source: ilisp Binary: ilisp ilisp-doc Architecture: source all Version: 5.12.0+cvs.2004.12.26-18 Distribution: unstable Urgency: low Maintainer: Barak A. Pearlmutter b...@debian.org Changed-By: Barak A. Pearlmutter b...@debian.org Description: ilisp - Emacs interface to LISP implementations ilisp-doc - Documentation for ILISP package Closes: 680646 682826 68 Changes: ilisp (5.12.0+cvs.2004.12.26-18) unstable; urgency=low . * add emacs24 support (closes: #680646) * update some constructs that annoy the elisp compiler * stop making /etc/ilisp/ilisp-keybindings.el a conf file (closes: #68) * restrict writes in global .fasl directory to group ilisp (closes: #682826) Checksums-Sha1: 387490153b8f78cc2f6ac862b8f7e053a49e2571 1396 ilisp_5.12.0+cvs.2004.12.26-18.dsc d656b6cdb0a9bcbaaeb0f56bac8bc74ccf0e3773 103662 ilisp_5.12.0+cvs.2004.12.26-18.debian.tar.gz 145aa5ca44879921706aae43139a06ab4cc9fbbc 268574 ilisp_5.12.0+cvs.2004.12.26-18_all.deb 7c5b95a442906a3a1aa0dfe7bcef1488fd02f6c9 357968 ilisp-doc_5.12.0+cvs.2004.12.26-18_all.deb Checksums-Sha256: 1412858a9c52d2b525470df6c4355fcade9b61388e18d22a6bebf82fe12b3761 1396 ilisp_5.12.0+cvs.2004.12.26-18.dsc eb504e5b99a2081d30a87226ceeb0fa259a466ac64812daddb57e957c13f0025 103662 ilisp_5.12.0+cvs.2004.12.26-18.debian.tar.gz 9b281a875c938c6e2700047da187dfa3ad0577be62976b8c49922872c9c74690 268574 ilisp_5.12.0+cvs.2004.12.26-18_all.deb
Bug#710917: quantum-common: fails to upgrade from 'testing' - trying to overwrite /usr/bin/quantum-*-agent
Followup-For: Bug #710917 The problem persists: Preparing to replace quantum-common 2012.1-1 (using .../quantum-common_2013.1.2-1_all.deb) ... Unpacking replacement quantum-common ... dpkg: error processing /var/cache/apt/archives/quantum-common_2013.1.2-1_all.deb (--unpack): trying to overwrite '/usr/bin/quantum-linuxbridge-agent', which is also in package quantum-plugin-linuxbridge-agent 2012.1-5+deb70u1 dpkg: considering deconfiguration of python-quantum, which would be broken by installation of quantum-plugin-linuxbridge-agent ... dpkg: yes, will deconfigure python-quantum (broken by quantum-plugin-linuxbridge-agent) Preparing to replace quantum-plugin-linuxbridge-agent 2012.1-5+deb70u1 (using .../quantum-plugin-linuxbridge-agent_2013.1.2-1_all.deb) ... invoke-rc.d: policy-rc.d denied execution of stop. De-configuring python-quantum ... E: namespace:121: cannot remove /usr/lib/python2.6/dist-packages/quantum/__init__.py Unpacking replacement quantum-plugin-linuxbridge-agent ... dpkg: considering deconfiguration of quantum-common, which would be broken by installation of python-quantum ... dpkg: yes, will deconfigure quantum-common (broken by python-quantum) Preparing to replace python-quantum 2012.1-5+deb70u1 (using .../python-quantum_2013.1.2-1_all.deb) ... E: namespace:121: cannot remove /usr/lib/python2.6/dist-packages/quantum/__init__.py E: namespace:121: cannot remove /usr/lib/python2.7/dist-packages/quantum/__init__.py De-configuring quantum-common ... Unpacking replacement python-quantum ... Replacing files in old package quantum-common ... Errors were encountered while processing: /var/cache/apt/archives/quantum-common_2013.1.2-1_all.deb Package: quantum-common Version: 2013.1.2-1 Installed-Size: 303 Replaces: quantum-server (= 2012.2~rc1~20120907.1154-0ubuntu1) Breaks: quantum-server (= 2012.2~rc1~20120907.1154-0ubuntu1) missing Breaks+Replaces: quantum-plugin-linuxbridge-agent ( xxx), quantum-plugin-openvswitch-agent ( xxx) Cheers, Andreas quantum-plugin-openvswitch-agent_2013.1.2-1.log.gz Description: GNU Zip compressed data
Bug#714547: gnome-panel: Gnome-panel does not appear
This is probably due to the incompatibility between gnome-bluetooth 3.8.1-1 and gnome-shell 3.4.2-8 as reported in bug 712861. Uppgrading package gnome-shell-common to version 3.4.2-9 (currenly in sid but not yet in testing) seems to fix the problem. /Örjan
Bug#714609: astromenace: missing Depends: xz-utils
Package: astromenace Version: 1.3.1+repack-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package astromenace. (Reading database ... 7531 files and directories currently installed.) Unpacking astromenace (from .../astromenace_1.3.1+repack-2_amd64.deb) ... Setting up astromenace (1.3.1+repack-2) ... tar (child): xz: Cannot exec: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now dpkg: error processing astromenace (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: astromenace xz-utils was recently demoted from required to standard, therefore packages using it must depend on xz-utils. cheers, Andreas astromenace_1.3.1+repack-2.log.gz Description: GNU Zip compressed data
Bug#711789: marked as done (grads: unbuildable (build-dependencies conflict))
Your message dated Mon, 01 Jul 2013 09:48:41 + with message-id e1utaiv-0008hm...@franck.debian.org and subject line Bug#711789: fixed in libgeotiff-dfsg 1.3.0+dfsg-3.1 has caused the Debian Bug report #711789, regarding grads: unbuildable (build-dependencies conflict) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 711789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: grads Version: 2:2.0.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) grads (= 2:2.0.1-1) build-depends on one of: - libgeotiff-dev (= 1.3.0+dfsg-3) libgeotiff-dev (= 1.3.0+dfsg-3) depends on one of: - libtiff5-dev (= 4.0.2-6) libtiff4-dev (= 3.9.6-11) and libtiff5-dev (= 4.0.2-6) conflict libgd-dev (= 2.1.0~rc2-1) depends on one of: - libtiff4-dev (= 3.9.6-11) libgd2-xpm-dev (= 2.1.0~rc2-1) depends on one of: - libgd-dev (= 2.1.0~rc2-1) grads (= 2:2.0.1-1) build-depends on one of: - libgd2-xpm-dev (= 2.1.0~rc2-1) - libgd-dev (= 2.1.0~rc2-1) Arguably libgeotiff's fault, but. Cheers, Julien signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: libgeotiff-dfsg Source-Version: 1.3.0+dfsg-3.1 We believe that the bug you reported is fixed in the latest version of libgeotiff-dfsg, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 711...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated libgeotiff-dfsg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 27 Jun 2013 10:24:57 +0200 Source: libgeotiff-dfsg Binary: libgeotiff-dev libgeotiff2 geotiff-bin Architecture: source amd64 Version: 1.3.0+dfsg-3.1 Distribution: unstable Urgency: low Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: geotiff-bin - the GeoTIFF library -- tools libgeotiff-dev - the GeoTIFF library -- development files libgeotiff2 - the GeoTIFF library -- run-time files Closes: 711789 Changes: libgeotiff-dfsg (1.3.0+dfsg-3.1) unstable; urgency=low . * Non-maintainer upload. * Build-depend libtiff5-alt-dev, to allow smooth tiff transition (Closes: #711789) * Remove useless chrpath from libtiff5-alt-dev usage Checksums-Sha1: 1cfad91706cb06277406878d86cf3ab079fd3805 1586 libgeotiff-dfsg_1.3.0+dfsg-3.1.dsc 2d6d24ea0e2497a63c68ef1afbeb24a69552c8cb 6762 libgeotiff-dfsg_1.3.0+dfsg-3.1.debian.tar.gz 52cbf4867426beba2bff5d020b8be44a5934 119280 libgeotiff-dev_1.3.0+dfsg-3.1_amd64.deb 064bb21c32b69a36ebbe948c46ec42a60efc4057 78900 libgeotiff2_1.3.0+dfsg-3.1_amd64.deb 733896dadcdd288c35129ad9b45ab05de460fb4e 48976 geotiff-bin_1.3.0+dfsg-3.1_amd64.deb Checksums-Sha256: add098918795faba91cccdefd6ea07a72a332cdda4bc5d8110d67054e5590360 1586 libgeotiff-dfsg_1.3.0+dfsg-3.1.dsc b8e5042957740d39b79845d0f768237d227f2f176f09f4a53950bc8a2095e7e3 6762 libgeotiff-dfsg_1.3.0+dfsg-3.1.debian.tar.gz a7fcfa29798907fcd71a9b5a804ccb8cecf4ae9f5c199671820619270f6e288d 119280 libgeotiff-dev_1.3.0+dfsg-3.1_amd64.deb 128792cf364e2090b6215b85e6d3876b12bc46221915434f5b9b7a5b7e07a6d4 78900 libgeotiff2_1.3.0+dfsg-3.1_amd64.deb 0f9ef04d42dc78c3d173e6d697c2deaa82557e42ca10c699da75956031a62010 48976 geotiff-bin_1.3.0+dfsg-3.1_amd64.deb Files: 332670a4678910eeb439ce997472e8a5 1586 science extra libgeotiff-dfsg_1.3.0+dfsg-3.1.dsc c858eb19ccb40fbbca2d8707eff60bd5 6762 science extra libgeotiff-dfsg_1.3.0+dfsg-3.1.debian.tar.gz a68ce7da2a798fbea1af260685721d2d 119280 libdevel extra libgeotiff-dev_1.3.0+dfsg-3.1_amd64.deb dbe199ddf109918b41c3e80d3ba55e3f 78900 libs extra libgeotiff2_1.3.0+dfsg-3.1_amd64.deb c43392f4df1f3a5d7740fda97904429b 48976 science extra geotiff-bin_1.3.0+dfsg-3.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHRTiYACgkQ9OZqfMIN8nP8tQCZASVjdfG8ve2gYuUMAGWkhAnG A6oAoJkCnf869dBSBdfL6dQbEzfgfuC5 =eO03 -END PGP SIGNATUREEnd Message---
Bug#707450: marked as done (sipwitch: FTBFS: ../inc/sipwitch/service.h:111:14: error: 'id' was not declared in this scope)
Your message dated Mon, 01 Jul 2013 09:50:48 + with message-id e1utaky-0001cl...@franck.debian.org and subject line Bug#707450: fixed in sipwitch 1.6.1-1 has caused the Debian Bug report #707450, regarding sipwitch: FTBFS: ../inc/sipwitch/service.h:111:14: error: 'id' was not declared in this scope to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 707450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sipwitch Version: 1.2.4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../inc -DOSIP_MT -DHAVE_PTHREAD -Wno-long-long -DNEW_STDCPP -pthread -fno-check-new -finline -fvisibility=hidden -DUCOMMON_VISIBILITY=1 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o service.lo service.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../inc -DOSIP_MT -DHAVE_PTHREAD -Wno-long-long -DNEW_STDCPP -pthread -fno-check-new -finline -fvisibility=hidden -DUCOMMON_VISIBILITY=1 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c service.cpp -fPIC -DPIC -o .libs/service.o In file included from service.cpp:20:0: ../inc/sipwitch/service.h: In member function 'void sipwitch::service::keyclone::reset(const char*)': ../inc/sipwitch/service.h:111:14: error: 'id' was not declared in this scope ../inc/sipwitch/service.h: In static member function 'static bool sipwitch::service::isLinked(sipwitch::service::keynode*)': ../inc/sipwitch/service.h:263:23: error: 'sipwitch::service::keynode' has no member named 'isLeaf' service.cpp: In member function 'void sipwitch::service::keyclone::splice(sipwitch::service::keyclone*)': service.cpp:214:5: error: 'parent' was not declared in this scope service.cpp:216:28: error: 'class sipwitch::service::keyclone' has no member named 'child' make[3]: *** [service.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/sipwitch_1.2.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: sipwitch Source-Version: 1.6.1-1 We believe that the bug you reported is fixed in the latest version of sipwitch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard d...@jones.dk (supplier of updated sipwitch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 01 Jul 2013 11:37:18 +0200 Source: sipwitch Binary: sipwitch libsipwitch-dev libsipwitch1-dbg libsipwitch1 sipwitch-cgi Architecture: source amd64 Version: 1.6.1-1 Distribution: unstable Urgency: low Maintainer: Jonas Smedegaard d...@jones.dk Changed-By: Jonas Smedegaard d...@jones.dk Description: libsipwitch-dev - secure peer-to-peer SIP VoIP server - development files libsipwitch1 - secure peer-to-peer SIP VoIP server - shared libraries libsipwitch1-dbg - secure peer-to-peer SIP VoIP server - debug symbols sipwitch - secure peer-to-peer VoIP server for the SIP protocol sipwitch-cgi - secure peer-to-peer SIP VoIP server - CGI XML-RPC interface Closes: 679392 679393 707450 Changes: sipwitch (1.6.1-1) unstable; urgency=low . [ upstream ] * New release. + ucommon abi 6 support. + drop switchview (moved to standalone package). + usage of new context aware intermediary voip functions. + fixes for official exosip2 4.0. + improved ssl configure
Bug#710637: marked as done (sipwitch: FTBFS: ../inc/sipwitch/service.h:111:14: error: 'id' was not declared in this scope)
Your message dated Mon, 01 Jul 2013 09:50:48 + with message-id e1utaky-0001cl...@franck.debian.org and subject line Bug#707450: fixed in sipwitch 1.6.1-1 has caused the Debian Bug report #707450, regarding sipwitch: FTBFS: ../inc/sipwitch/service.h:111:14: error: 'id' was not declared in this scope to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 707450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sipwitch Version: 1.2.4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../inc -DHAVE_PTHREAD -Wno-long-long -DNEW_STDCPP -pthread -fno-check-new -finline -fvisibility=hidden -DUCOMMON_VISIBILITY=1 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o service.lo service.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../inc -DHAVE_PTHREAD -Wno-long-long -DNEW_STDCPP -pthread -fno-check-new -finline -fvisibility=hidden -DUCOMMON_VISIBILITY=1 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c service.cpp -fPIC -DPIC -o .libs/service.o In file included from service.cpp:20:0: ../inc/sipwitch/service.h: In member function 'void sipwitch::service::keyclone::reset(const char*)': ../inc/sipwitch/service.h:111:14: error: 'id' was not declared in this scope ../inc/sipwitch/service.h: In static member function 'static bool sipwitch::service::isLinked(sipwitch::service::keynode*)': ../inc/sipwitch/service.h:263:23: error: 'sipwitch::service::keynode' has no member named 'isLeaf' service.cpp: In member function 'void sipwitch::service::keyclone::splice(sipwitch::service::keyclone*)': service.cpp:214:5: error: 'parent' was not declared in this scope service.cpp:216:28: error: 'class sipwitch::service::keyclone' has no member named 'child' make[3]: *** [service.lo] Error 1 The full build log is available from: http://deiv.vzpla.net/logs/2013/05/29/sipwitch_1.2.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: sipwitch Source-Version: 1.6.1-1 We believe that the bug you reported is fixed in the latest version of sipwitch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard d...@jones.dk (supplier of updated sipwitch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 01 Jul 2013 11:37:18 +0200 Source: sipwitch Binary: sipwitch libsipwitch-dev libsipwitch1-dbg libsipwitch1 sipwitch-cgi Architecture: source amd64 Version: 1.6.1-1 Distribution: unstable Urgency: low Maintainer: Jonas Smedegaard d...@jones.dk Changed-By: Jonas Smedegaard d...@jones.dk Description: libsipwitch-dev - secure peer-to-peer SIP VoIP server - development files libsipwitch1 - secure peer-to-peer SIP VoIP server - shared libraries libsipwitch1-dbg - secure peer-to-peer SIP VoIP server - debug symbols sipwitch - secure peer-to-peer VoIP server for the SIP protocol sipwitch-cgi - secure peer-to-peer SIP VoIP server - CGI XML-RPC interface Closes: 679392 679393 707450 Changes: sipwitch (1.6.1-1) unstable; urgency=low . [ upstream ] * New release. + ucommon abi 6 support. + drop switchview (moved to standalone package). + usage of new context aware intermediary voip functions. + fixes for official exosip2 4.0. + improved ssl configure check. . [ Jonas Smedegaard ]
Bug#711789: grads: unbuildable (build-dependencies conflict)
Updated debdiff (I had to remove useless RPATH to make lintian happy). On Mon, Jul 1, 2013 at 9:53 AM, Ondřej Surý ond...@debian.org wrote: And attached is exact debdiff of what I have just uploaded to DELAYED/0. O. On Thu, Jun 27, 2013 at 10:48 AM, Ondřej Surý ond...@debian.org wrote: Package: src:grads Followup-For: Bug #711789 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear maintainer, please apply attached patch to use libtiff5-alt-dev instead of libtiff5-dev. The libtiff5-dev libtiff4-dev conflicts makes downstream packages (namely grads) unbuildable and it's blocking the libgd2 transition. I plan to NMU the package if I don't hear from you soon (it's RC severity bug). The changes I did are minimal - the other option would be to make upstream configure.ac to use pkg-config (which would be more elegant, but also more intrusive). Thanks, O. - -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHL/GkACgkQ9OZqfMIN8nPcogCfSd/WByakSLYRqY4MJhHPOdKU ajoAn2bNUscvb0F06wYhsd3qVhJhwpfg =hw+h -END PGP SIGNATURE- -- Ondřej Surý ond...@sury.org -- Ondřej Surý ond...@sury.org libgeotiff-dfsg_1.3.0+dfsg-3.1.debdiff Description: Binary data
Bug#714547: Upgrade to gnome-shell and gnome-shell-common 3.4.2-8 solved
Upgrade to gnome-shell and gnome-shell-common 3.4.2-9 fixed! -- O___ - Marcelo Luiz de Laia c/ /'_ - Diamantina (*) \(*)- Minas Gerais ~- Brazil ^- Linux user number 487797 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 714547 to gnome-shell, forcibly merging 712861 714547
Processing commands for cont...@bugs.debian.org:
reassign 714547 gnome-shell
Bug #714547 [gnome-panel] gnome-panel: Gnome-panel does not appear
Bug reassigned from package 'gnome-panel' to 'gnome-shell'.
No longer marked as found in versions gnome-panel/3.4.2.1-5.
Ignoring request to alter fixed versions of bug #714547 to the same values
previously set
forcemerge 712861 714547
Bug #712861 {Done: Emilio Pozuelo Monfort po...@debian.org} [gnome-shell]
gnome-bluetooth: Breaks gnome-shell: GnomeBluetoothApplet.KillswitchState is
undefined
Bug #712926 {Done: Ludovic Lebègue ludo...@lebegue.org} [gnome-shell]
gnome-shell: Execution of main.js threw exception: TypeError:
GnomeBluetoothApplet.KillswitchState is undefined
Bug #714545 {Done: Emilio Pozuelo Monfort po...@debian.org} [gnome-shell]
gnome doesn't start
Bug #714547 [gnome-shell] gnome-panel: Gnome-panel does not appear
Severity set to 'serious' from 'critical'
Marked Bug as done
Marked as found in versions gnome-shell/3.4.2-8.
Added tag(s) sid and jessie.
Bug #712926 {Done: Ludovic Lebègue ludo...@lebegue.org} [gnome-shell]
gnome-shell: Execution of main.js threw exception: TypeError:
GnomeBluetoothApplet.KillswitchState is undefined
Bug #714545 {Done: Emilio Pozuelo Monfort po...@debian.org} [gnome-shell]
gnome doesn't start
Merged 712861 712926 714545 714547
thanks
Stopping processing here.
Please contact me if you need assistance.
--
712861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712861
712926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712926
714545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714545
714547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: user debian...@lists.debian.org, usertagging 711739, fixed 711739 in 4.1-1, found 668751 in 1.1.1-6 ...
Processing commands for cont...@bugs.debian.org:
user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
usertags 711739 piuparts
There were no usertags set.
Usertags are now: piuparts.
fixed 711739 4.1-1
Bug #711739 [xul-ext-foxyproxy-standard] xul-ext-foxyproxy-standard:
uninstallable in sid, jessie and wheezy
Marked as fixed in versions foxyproxy/4.1-1.
found 668751 1.1.1-6
Bug #668751 [liquidsoap] liquidsoap: unowned directory after purge:
/usr/share/liquidsoap
Marked as found in versions liquidsoap/1.1.1-6.
found 710917 2013.1.2-1
Bug #710917 {Done: Thomas Goirand tho...@goirand.fr} [quantum-common]
quantum-common: fails to upgrade from 'testing' - trying to overwrite
/usr/bin/quantum-*-agent
Marked as found in versions quantum/2013.1.2-1 and reopened.
found 699647 1.3.5~rc3-1
Bug #699647 [proftpd-mod-geoip] proftpd-mod-geoip:
/usr/lib/proftpd/mod_geoip.so missing after upgrade from sid
Marked as found in versions proftpd-dfsg/1.3.5~rc3-1.
reassign 666839 libapache2-mod-fastcgi 2.4.7~0910052141-1
Bug #666839 [libapache-mod-fastcgi] libapache-mod-fastcgi: sourceful transition
towards Apache 2.4
Bug reassigned from package 'libapache-mod-fastcgi' to 'libapache2-mod-fastcgi'.
No longer marked as found in versions 2.4.7~0910052141-1.
Ignoring request to alter fixed versions of bug #666839 to the same values
previously set
Bug #666839 [libapache2-mod-fastcgi] libapache-mod-fastcgi: sourceful
transition towards Apache 2.4
Marked as found in versions libapache-mod-fastcgi/2.4.7~0910052141-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
666839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666839
668751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668751
699647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699647
710917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710917
711739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 714264 to libclutter-1.0-0, tagging 714264
Processing commands for cont...@bugs.debian.org: reassign 714264 libclutter-1.0-0 1.10.8-2 Bug #714264 [gnome-shell] CVE-2013-2190: screen unlocked after resuming due to crash Bug reassigned from package 'gnome-shell' to 'libclutter-1.0-0'. Ignoring request to alter found versions of bug #714264 to the same values previously set Ignoring request to alter fixed versions of bug #714264 to the same values previously set Bug #714264 [libclutter-1.0-0] CVE-2013-2190: screen unlocked after resuming due to crash Marked as found in versions clutter-1.0/1.10.8-2. tags 714264 + sid jessie experimental Bug #714264 [libclutter-1.0-0] CVE-2013-2190: screen unlocked after resuming due to crash Added tag(s) sid, experimental, and jessie. #this bug is assign upstream to clutter thanks Stopping processing here. Please contact me if you need assistance. -- 714264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 714264
Processing commands for cont...@bugs.debian.org: tags 714264 + wheezy security Bug #714264 [libclutter-1.0-0] CVE-2013-2190: screen unlocked after resuming due to crash Added tag(s) wheezy and security. thanks Stopping processing here. Please contact me if you need assistance. -- 714264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706758: marked as done (python2.6 broken on squeeze-wheezy upgrade if unpacked before dependencies)
Your message dated Mon, 01 Jul 2013 10:13:07 + with message-id e1utb6z-7e...@franck.debian.org and subject line Bug#714116: Removed package(s) from unstable has caused the Debian Bug report #706758, regarding python2.6 broken on squeeze-wheezy upgrade if unpacked before dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-scientific Version: 2.8-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + python-mpi python Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'wheezy' fails. From the attached log (scroll to the bottom...): The following NEW packages will be installed: ... libssl1.0.0 ... Selecting previously deselected package python2.7-minimal. (Reading database ... 8561 files and directories currently installed.) Unpacking python2.7-minimal (from .../python2.7-minimal_2.7.3-6_i386.deb) ... Preparing to replace python-mpi 2.8-1.2 (using .../python-mpi_2.8-4_all.deb) ... INFO: using unknown version '/usr/bin/python2.7' (debian_defaults not up-to-date?) Unpacking replacement python-mpi ... Preparing to replace python2.6 2.6.6-8+b1 (using .../python2.6_2.6.8-1.1_i386.deb) ... Unpacking replacement python2.6 ... Preparing to replace python2.6-minimal 2.6.6-8+b1 (using .../python2.6-minimal_2.6.8-1.1_i386.deb) ... Unpacking replacement python2.6-minimal ... Preparing to replace python-scientific 2.8-1.2 (using .../python-scientific_2.8-4_all.deb) ... /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: error processing /var/cache/apt/archives/python-scientific_2.8-4_all.deb (--unpack): subprocess new pre-removal script returned error exit status 127 configured to not write apport reports /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 Processing triggers for python-support ... /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: error processing python-support (--unpack): subprocess installed post-installation script returned error exit status 127 configured to not write apport reports Errors were encountered while processing: /var/cache/apt/archives/python-scientific_2.8-4_all.deb python-support Python (indirectly) depends on libssl1.0.0, but that was not yet unpacked while the newer python* already got unpacked. There were also similar problems where python was a dangling symlink and not usable at all... cheers, Andreas python-mpi_2.8-4.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Version: 2.6.8-2+rm Dear submitter, as the package python2.6 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/714116 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#710645: [ni...@thykier.net: Candidates for removal from testing (2013-06-30)]
Hi Luis,
I wonder whether you are aware of bug #710645 and whether you have some
solution for this problem. I'd bet it is simple for a C++ programmer.
If you have trouble fixing it please state this explicitly and ask for
help on the Debian Med mailing list.
I'd recommend subscribing the package in the Package Tracking System.
Kind regards
Andreas.
- Forwarded message from Niels Thykier ni...@thykier.net -
Date: Sun, 30 Jun 2013 23:32:18 +0200 (CEST)
From: Niels Thykier ni...@thykier.net
To: debian-de...@lists.debian.org
Cc: debian-rele...@lists.debian.org
Subject: Candidates for removal from testing (2013-06-30)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
We are considering removing the following packages from testing as
they have unfixed RC bugs filed against them. The packages can be
found in the attached dd-list.
The packages have been selected based on the following criteria:
- The package had at least one RC bug without activity for the past
14 days.
- If a bug is assigned to multiple packages, both packages will
be affected[1].
- The RC bug affects both unstable and testing.
- The affected package does not have any reverse dependencies in
testing.
- One of their RC bugs had FTBFS in their title. (*)
- The source package had a popcon inst value of 500 or less. (*)
(*) These extra filter rules was applied to keep the list down. The
original list was 246.
If the relevant RC bugs in the affected packages (those listed in
FTBFS-w-popcon-lt-500.txt) are not dealt with before the 8th of
July, the packages will be removed from testing. Note that dealt
with may also include downgrading a severity-inflated bug or fixing
affected versions in the BTS.
For reference, the original list is also included.
Thanks,
Niels (on behalf of the Release Team)
PS: This mail has been BCC'ed to pkg@packages.debian.org for
packaged listed in FTBFS-w-popcon-lt-500.txt.
8 FTBFS-w-popcon-lt-500.txt 8
BUG [SRC]: TITLE
#712367 [bashdb]: bashdb: FTBFS: manuals build fails against textinfo5 because
some incompatibles changes wrt 4.13 and below (some warnings have turned into
errors)
#711787 [falconpl]: falconpl: FTBFS on mipsen
#701412 [prelude-manager]: prelude-manager: ftbfs with eglibc-2.17
#712329 [epix]: epix: FTBFS: manuals build fails against textinfo5 because some
incompatibles changes wrt 4.13 and below (some warnings have turned into errors)
#710633 [orafce]: orafce: FTBFS: plvlex.c:209:3: error: too many arguments to
function 'orafce_sql_yyparse'
#707399 [gedit-valencia-plugin]: gedit-valencia-plugin: FTBFS:
GIRepository-2.0.gir:240.11-240.30: error: expected start element of `parameter'
#710614 [bip]: bip: FTBFS: lex.l:19:6: error: conflicting types for 'yyparse'
#701319 [massxpert]: massxpert: ftbfs with GCC-4.8
#701334 [openvrml]: openvrml: ftbfs with GCC-4.8
#701328 [nwchem]: nwchem: ftbfs with GCC-4.8
#701367 [toonloop]: toonloop: ftbfs with GCC-4.8
#712321 [oneliner-el]: oneliner-el: FTBFS: manuals build fails against
textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings
have turned into errors)
#701411 [prelude-lml]: prelude-lml: ftbfs with eglibc-2.17
#701348 [rnahybrid]: rnahybrid: ftbfs with GCC-4.8
#710636 [mididings]: mididings: FTBFS: src/python_caller.cc:151:42: error:
expected unqualified-id before numeric constant
#701438 [charybdis]: charybdis: ftbfs with eglibc-2.17
#708692 [dnsjava]: FTBFS: requires internet connectivity
#712344 [cfi]: cfi: FTBFS: Package babel Error: Unknow option `swedish'. Either
you misspelled it
#707373 [libccaudio2]: libccaudio2: FTBFS: friends.cpp:1189:25: error:
'ACCESS_DIRECTORY' is not a member of 'ucommon::fsys'
#701300 [ivtools]: ivtools: ftbfs with GCC-4.8
#701428 [turnserver]: turnserver: ftbfs with eglibc-2.17
#712349 [cdk]: cdk: FTBFS: This CDK release requires Ant 1.7.1 or better
#701342 [psychtoolbox-3]: psychtoolbox-3: ftbfs with GCC-4.8
#707411 [zoneminder]: zoneminder: FTBFS: zm_local_camera.cpp:742:49: error:
invalid conversion from '__u32 {aka unsigned int}' to 'v4l2_buf_type'
[-fpermissive]
#712327 [freepops]: freepops: FTBFS: Package babel Error: You haven't specified
a language option.
#711628 [libhttp-daemon-ssl-perl]: libhttp-daemon-ssl-perl: FTBFS: test failure
#701317 [mailavenger]: mailavenger: ftbfs with GCC-4.8
#711367 [python-django-localeurl]: python-django-localeurl: FTBFS:
NoReverseMatch: 'url' requires a non-empty first argument
#701298 [ion]: ion: ftbfs with GCC-4.8
#701281 [gcc-msp430]: gcc-msp430: ftbfs with GCC-4.8
#707420 [sdpnetstat]: sdpnetstat: FTBFS: strip.c:24:28: fatal error:
linux/if_strip.h: No such file or directory
#710501 [avinfo]: avinfo: FTBFS: ass.tab.h:104:5: error: conflicting types for
'yyparse'
#707501 [rpy]: rpy: FTBFS: grep: ecrm1095.log: No such file or directory
#708808 [nant]: nant: FTBFS: [csc] Cannot open assembly
'/usr/lib/mono/4.0/dmcs.exe': No such file or directory.
#706176 [openjpa]:
Bug#713683: marked as done (mia: FTBFS: ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::set_row(int, itpp::Vecdouble const, double)')
Your message dated Mon, 01 Jul 2013 12:29:10 +0200 with message-id 1372674550.14392.1.ca...@febe.die.upm.es and subject line a new upload of it++ fixed the bug has caused the Debian Bug report #713683, regarding mia: FTBFS: ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::set_row(int, itpp::Vecdouble const, double)' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mia Version: 2.0.9-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++0x -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -Wl,-z,relro -Wl,--as-needed CMakeFiles/mia-3dimagestats.dir/3dimagestats.cc.o -o mia-3dimagestats -L/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/../mia/core -L/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/../mia/2d -L/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/../mia/3d -rdynamic ../mia/3d/libmia3d-2.0.so.8.0.1 -lboost_regex-mt -lboost_filesystem-mt -lboost_system-mt -lpthread -ldl ../mia/2d/libmia2d-2.0.so.8.0.1 ../mia/core/libmiacore-2.0.so.8.0.1 -lboost_regex-mt -lboost_filesystem-mt -lboost_system-mt -lpthread -ldl ../gsl++/libmiagsl-2.0.so.8.0.1 -lgsl -lgslcblas -lm -ltbb -lfftw3f -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0 -Wl,-rpath,/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/../mia/core:/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/../mia/2d:/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/../mia/3d:/«PKGBUILDDIR»/obj-x86_64-linux-gnu/mia/3d:/«PKGBUILDDIR»/obj-x86_64-linux-gnu/mia/2d:/«PKGBUILDDIR»/obj-x86_64-linux-gnu/mia/core:/«PKGBUILDDIR»/obj-x86_64-linux-gnu/gsl++: ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::set_row(int, itpp::Vecdouble const, double)' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::set_mixing_series(unsigned long, std::vectorfloat, std::allocatorfloat const)' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::set_approach(int)' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::get_mix(unsigned long) const' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::get_incomplete_mix(unsigned long, std::setunsigned long, std::lessunsigned long, std::allocatorunsigned long const) const' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::set_max_iterations(int)' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::run(unsigned long, std::vectorstd::vectorfloat, std::allocatorfloat , std::allocatorstd::vectorfloat, std::allocatorfloat )' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::CICAAnalysis(unsigned long, unsigned long)' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::run_auto(int, int, float)' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::get_delta_feature(std::setunsigned long, std::lessunsigned long, std::allocatorunsigned long const, std::setunsigned long, std::lessunsigned long, std::allocatorunsigned long const) const' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::get_mixing_curves() const' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::get_partial_mix(unsigned long, std::setunsigned long, std::lessunsigned long, std::allocatorunsigned long const) const' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::get_feature_row(unsigned long) const' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::~CICAAnalysis()' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::normalize_Mix()' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::normalize_ICs()' ../mia/3d/libmia3d-2.0.so.8.0.1: undefined reference to `mia::CICAAnalysis::get_ncomponents() const' collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/mia_2.0.9-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
Processed: raising severity, gcc-4.4 and gnat-4.4 scheduled for removal
Processing control commands: severity -1 serious Bug #695303 [src:ghdl] ghdl: Please change Build-Depends: gnat-4.4 to gnat-4.6 Severity set to 'serious' from 'important' retitle -1 ghdl: Please change Build-Depends: gnat-4.4 to gnat-4.8 Bug #695303 [src:ghdl] ghdl: Please change Build-Depends: gnat-4.4 to gnat-4.6 Changed Bug title to 'ghdl: Please change Build-Depends: gnat-4.4 to gnat-4.8' from 'ghdl: Please change Build-Depends: gnat-4.4 to gnat-4.6' -- 695303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713326: turnin-ng: FTBFS: error: cannot copy tree 'build/scripts-2.7': not a directory
owner 713326 ! tag 713326 + pending thanks As for the actual cause of the FTBFS (cannot copy tree), that's been fixed. An upload will occur once the following is also fixed. On Sat, Jun 22, 2013 at 02:42:04PM +0200, Lucas Nussbaum wrote: ./gpl-2.0.texi:286: This command can appear only outside of any environment, no t in environment @enumerate. There appears to have been a change in texinfo that breaks the parsing of gpl-2.0.texi (from the GNU website[0]). Fixing this requires moving the WARRANTY @header command ounside of the @enumerate environment. This means ending and restarting the enumerate environment, with @enumerate resuming at the appropriate integer. Unfortunately, this isn't possible with current texinfo due to Debian bug #714533 [1]. Best wishes, Ryan [0] http://www.gnu.org/licenses/gpl-2.0.texi [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714533 -- |_)|_/ Ryan Kavanagh | Debian Developer | \| \ http://ryanak.ca/ | GPG Key 4A11C97A signature.asc Description: Digital signature
Processed: Re: Bug#713326: turnin-ng: FTBFS: error: cannot copy tree 'build/scripts-2.7': not a directory
Processing commands for cont...@bugs.debian.org: owner 713326 ! Bug #713326 [src:turnin-ng] turnin-ng: FTBFS: error: cannot copy tree 'build/scripts-2.7': not a directory Owner recorded as Ryan Kavanagh r...@debian.org. tag 713326 + pending Bug #713326 [src:turnin-ng] turnin-ng: FTBFS: error: cannot copy tree 'build/scripts-2.7': not a directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 713326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 714264 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=701974
Processing commands for cont...@bugs.debian.org: forwarded 714264 https://bugzilla.gnome.org/show_bug.cgi?id=701974 Bug #714264 [libclutter-1.0-0] CVE-2013-2190: screen unlocked after resuming due to crash Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=701974'. thanks Stopping processing here. Please contact me if you need assistance. -- 714264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: primus bug triaging
Processing commands for cont...@bugs.debian.org: # #712666 already affects the current version in testing, so it really # shouldn't be blocking migrating to testing as it's not a regression found 712666 0~20130527-1 Bug #712666 [primus] primus: fatal: failed to load PRIMUS_LOAD_GLOBAL Marked as found in versions primus/0~20130527-1. thanks Stopping processing here. Please contact me if you need assistance. -- 712666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug 710733
Processing commands for cont...@bugs.debian.org: tags 710733 pending Bug #710733 [monsterz-data,monsterz] monsterz-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/games/monsterz/graphics/icon.png Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 710733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 713520 in syfi/1.0.0.dfsg-1
Processing commands for cont...@bugs.debian.org: found 713520 syfi/1.0.0.dfsg-1 Bug #713520 [src:syfi] syfi: FTBFS: Could NOT find PythonLibs Marked as found in versions syfi/1.0.0.dfsg-1. thanks Stopping processing here. Please contact me if you need assistance. -- 713520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714617: Lingot: several vulnerabilities
Package: Lingot
version: 0.9.1-2
Severity: critical
Dear Maintainer,
Several vulnerabilites was found in the latest version of lingot as explained
further below :
[1] :: [File] = lingot-config.c , [Lines] 192 ~ 197 :
if ((fp = fopen(filename, w)) == NULL) {
char buff[100]; // = if i select a filename larger than [100 - 26] and
lead the program to here, program will crash.
sprintf(buff, error saving config file %s , filename);
perror(buff);
return;
}
##
[2] :: [File] = lingot.c , [Lines] 41 , 85 ~ 86 , 108 ~ 109 , 127 ~ 131 :
41 : char CONFIG_FILE_NAME[100];
85 ~ 86 :
sprintf(CONFIG_FILE_NAME, %s/ CONFIG_DIR_NAME DEFAULT_CONFIG_FILE_NAME,
getenv(HOME));
108 ~ 109 :
sprintf(CONFIG_FILE_NAME, %s/%s%s.conf, getenv(HOME),
CONFIG_DIR_NAME, optarg);
127 ~ 131 :
char config_dir[100];
sprintf(config_dir, %s/.lingot/, getenv(HOME));
printf(creating directory %s ...\n, config_dir);
mkdir(config_dir, 0777); // creo el directorio.
printf(creating file %s ...\n, CONFIG_FILE_NAME);
if i change $HOME to a larger one , Lingot will crash here .
##
[3] :: [File] = lingot-config.h , [Lines] 41 ~ :
41 :
struct _LingotConfig {
audio_system_t audio_system;
char audio_dev[3][80]; // = !!!
...
at this section if i manually set
AUDIO_DEV_ALSA = plguhw:0 = AUDIO_DEV_ALSA =
plguhw...AA:0
program crashes here.
##
[4] :: [File] = lingot-config.h , [Lines] ?? :
251 : void lingot_config_load(LingotConfig* config, char* filename) {
273 ~ 283 :
# define MAX_LINE_SIZE 100
char char_buffer[MAX_LINE_SIZE];
if ((fp = fopen(filename, r)) == NULL) {
sprintf(char_buffer,
error opening config file %s, assuming default values ,
filename); // = !!!
perror(char_buffer);
return;
}
and because of MAX_LINE_SIZE if i select a larger filename , program crashes
here .
also is in 192 ~ 197 !
##
If i can help in the fixing process please let me know.
Thank you,
Hamid Zamani
Bug#714618: lyx or tex go into an endless loop building mapy.pdf
Package: src:pycode-browser Version: 20120614+git+b041dd2-3 Severity: serious Tags: jessie sid Trying to re-build the package on i386, lyx or tex go into an endless loop, always restarting the tex run: [...] Output written on mapy.pdf (110 pages, 3784832 bytes). Transcript written on mapy.log. This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) restricted \write18 enabled. entering extended mode (./mapy.tex LaTeX2e 2011/06/27 [...] so mapy.pdf is written, then it gets built again. Had this seen on the Ubuntu buildds, but can reproduce it on unstable/i386 as well. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712666: Info received (Bug#712666: primus: fatal: failed to load PRIMUS_LOAD_GLOBAL)
On Fri, Jun 21, 2013 at 2:52 AM, Mathieu Malaterre ma...@debian.org wrote:
# breaking a 'should' req from §8.6
tags 712666 serious
thanks
On Fri, Jun 21, 2013 at 11:42 AM, Vincent Cheng vincentc1...@gmail.com
wrote:
On Wed, Jun 19, 2013 at 2:28 AM, Mathieu Malaterre ma...@debian.org wrote:
On Wed, Jun 19, 2013 at 11:21 AM, Vincent Cheng vincentc1...@gmail.com
wrote:
On Tue, Jun 18, 2013 at 5:50 AM, Mathieu Malaterre ma...@debian.org
wrote:
I would say that d/control is incomplete, it should read:
Package: primus-libs
Architecture: i386 amd64
Depends: ${shlibs:Depends}, ${misc:Depends}, libglapi-mesa
Here is what i see:
$ strings /usr/lib/primus/libGL.so.1 | grep glapi
libglapi.so.0
Comments ?
Why does dpkg-shlibdeps not add libglapi-mesa as a dependency / how
can I get dpkg-shlibdeps to do that? I'd much rather avoid hardcoding
dependencies if at all possible.
Simply because the lib is never linked in. It is dlopen'ed:
$ grep -r PRIMUS_LOAD_GLOBAL *
libglfork.cpp:needed_global(dlopen(getconf(PRIMUS_LOAD_GLOBAL),
RTLD_LAZY | RTLD_GLOBAL)),
dpkg-shlibdeps simply read the output of readelf -d /usr/lib/bla.so.
So in this case yes you have to explicitly add the Depends yourself
-IMHO-. Maybe there are other way to do it, but I do not know.
HTH
After a short conversation with upstream [1], I believe that this is
more likely than not some sort of packaging issue with mesa. Mesa in
all currently supported versions of Debian is built with
--enable-shared-glapi, so theoretically libgl1-mesa-glx (which
contains mesa's libGL.so.1) should pull in libglapi-mesa
automatically. That's definitely the case on my current jessie/sid
system:
$ apt-cache depends libgl1-mesa-glx | grep glapi
Depends: libglapi-mesa
i.e. we shouldn't have to declare an explicit dependency on libglapi-mesa.
libglapi-mesa only appears in wheezy, ref:
http://packages.debian.org/unstable/libglapi-mesa
Ack, so primus isn't going to work on squeeze as-is. Hmmm...if you'd
still like to see bumblebee and co. backported to squeeze, I suppose
you could try using virtualgl instead. However, it's not packaged yet
(on my todo list, but you're welcome to take over if you want), and
it'd also require backporting of its dependencies (libjpeg-turbo,
which I imagine wouldn't be trivial to backport).
Your package thus:
1. does not work on oldstable (squeeze), and any derivatives at that point
2. does not list a required dependency (what if the ABI changes ?)
3. any new arch added to debian (or derivatives), where mesa is built
with --disable-shared-glapi will not work
As described in the bug report upstream, this is a clear dependency
and is a requirerment. I do not understand why you would not want to
clarify that at debian/control level...
As far as I understand, what upstream is trying to say is that there's
simply no valid way to express primus' dependencies using
debian/control syntax. Just because libglapi-mesa exists as a package
and is installed, doesn't mean that primus will actually be
functional. As an example (provided by upstream, just paraphrasing
here), the mesa maintainers could one day stop building mesa opengl
with --enable-shared-glapi, and still provide libglapi-mesa as a
package (e.g. by building mesa OpenGL ES with --enable-shared-glapi
instead), then primus would be installable with libglapi-mesa as a
dependency, but still be broken.
Again, AFAIU upstream's argument boils down to it simply being
impossible to clarify that at debian/control level, that just
because libglapi-mesa is installable, does not guarantee that primus
would work, so depending on libglapi-mesa serves no purpose.
As for point (2):
amonakov: libglapi is an implementation detail of Mesa. primus does
not depend on libglapi itself (there is no documented public interface
to depend on
So I guess that in effect, primus can break at any time, and adding a
dependency on libglapi-mesa does nothing to stop this from happening?
I understand (1) (3) should be very rare event. However (2) is
pretty clear, see §8.6 Dependencies between the library and other
packages
http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-depends
[Other packages which use a shared library (for example using
dlopen()) should compute appropriate dependencies using these files at
build time as well.]
A bit of a tangent, but should != must.
Regards,
Vincent
(And sorry for that very long delay in between this and my last reply)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710645: marked as done (sitplus: FTBFS: mod_camera.h:177:32: error: expected unqualified-id before numeric constant)
Your message dated Mon, 01 Jul 2013 11:19:49 + with message-id e1utc97-00054x...@franck.debian.org and subject line Bug#710645: fixed in sitplus 1.0.3-4 has caused the Debian Bug report #710645, regarding sitplus: FTBFS: mod_camera.h:177:32: error: expected unqualified-id before numeric constant to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 710645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sitplus Version: 1.0.3-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. It's a problem in boost which is fixed in 1.50. TIME_UTC is a C11 macro that colides with boost::TIME_UTC. In Boost 1.50, this constant was renamed to TIME_UTC_. To fix it just use the new symbol name. Relevant part: /«PKGBUILDDIR»/include/spcore/pinimpl.h:359:23: required from 'boost::intrusive_ptrconst spcore::CTypeAny spcore::CInputPinReadWriteTDATA, TCOMPONENT::Read() const [with TDATA = spcore::SimpleTypespcore::CTypeIntContents; TCOMPONENT = mod_camera::CameraConfig]' /«PKGBUILDDIR»/src/mod_camera/mod_camera.cpp:430:2: required from here /«PKGBUILDDIR»/include/spcore/baseobj.h:143:13: note: 'void boost::intrusive_ptr_add_ref(const spcore::IBaseObject*)' declared here, later in the translation unit make[3]: *** [src/mod_camera/CMakeFiles/spmod_camera.dir/mod_camera.cpp.o] Error 1 The full build log is available from: http://deiv.vzpla.net/logs/2013/05/29/sitplus_1.0.3-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: sitplus Source-Version: 1.0.3-4 We believe that the bug you reported is fixed in the latest version of sitplus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitrijs Ledkovs dmitrij.led...@ubuntu.com (supplier of updated sitplus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 Jul 2013 11:54:14 +0100 Source: sitplus Binary: sitplus sitplus-data Architecture: source amd64 all Version: 1.0.3-4 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Dmitrijs Ledkovs dmitrij.led...@ubuntu.com Description: sitplus- Free software framework for ludic-therapeutic activities sitplus-data - Data files for Sitplus, a framework for ludic-therapeutic activit Closes: 710645 Changes: sitplus (1.0.3-4) unstable; urgency=low . * Team upload. * Remove deprecated V4L2_CID_[HV]CENTER controls. * Use boost::TIME_UTC_. (Closes: #710645) * Added missing libs to link, fixing FTBFS on ubuntu. Checksums-Sha1: 96ac0a68dbb7eef0544f199cc39f4574f63e1e73 2365 sitplus_1.0.3-4.dsc cf6a07ce316df6760962eb50db3a819299bb9dbd 17874800 sitplus_1.0.3.orig.tar.gz 99f0e03cd45f3414e56cd53a15585ea84911c8e9 10976 sitplus_1.0.3-4.debian.tar.gz 459543f16c9f0f178e9d3e436a818cfa53f18124 1126486 sitplus_1.0.3-4_amd64.deb aa28071a71c3603fd5dd0f6241b7e5d1046f5e0c 17047218 sitplus-data_1.0.3-4_all.deb Checksums-Sha256: dea772f665fc30ad752123e9d876fdd0faa81e934e284c87bc925ff6aaa79d05 2365 sitplus_1.0.3-4.dsc 083e07d7a8f4efc54af6a325a1c2bc353d728f9b8b87f8b98c96a7e8b9112027 17874800 sitplus_1.0.3.orig.tar.gz 3e413eecf2cd68802b8cad98f912dfc2f8558c6c0ccd96975a4001e220464d63 10976 sitplus_1.0.3-4.debian.tar.gz 4e08493467f36f00f28bc019d4c90e208aebdf91e5a2e9f788fcb7571a12aa38 1126486 sitplus_1.0.3-4_amd64.deb 9dad20e42667dae18d13e9bb0068c139b3c8d8df42e3fb88abeec7798c62d54d 17047218 sitplus-data_1.0.3-4_all.deb Files: d72acae32241e16e80b875f1f6e8c076 2365 misc
Bug#701323: marked as done (mod-gearman: ftbfs with GCC-4.8)
Your message dated Mon, 01 Jul 2013 12:10:37 +0200 with message-id 87a9m67fqa@dagon.fnord.no and subject line Not related to gcc migration has caused the Debian Bug report #701323, regarding mod-gearman: ftbfs with GCC-4.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:mod-gearman Version: 1.3.6-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. XXX The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/mod-gearman_1.3.6-1_unstable_gcc48.log The last lines of the build log are at the end of this report. To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues might be caused by the updated glibc. [...] test -z /usr/lib/mod_gearman || /bin/mkdir -p /«PKGBUILDDIR»/debian/tmp/usr/lib/mod_gearman /usr/bin/install -c -m 644 mod_gearman.so '/«PKGBUILDDIR»/debian/tmp/usr/lib/mod_gearman' ( cd '/«PKGBUILDDIR»/debian/tmp/usr/lib/mod_gearman' ranlib mod_gearman.so ) /bin/bash /«PKGBUILDDIR»/install-sh -c -m 755 worker/mod_gearman_p1.pl /«PKGBUILDDIR»/debian/tmp/usr/share/mod_gearman/mod_gearman_p1.pl Installation completed: p1file: /«PKGBUILDDIR»/debian/tmp/usr/share/mod_gearman/mod_gearman_p1.pl /bin/bash /«PKGBUILDDIR»/install-sh -c -d /«PKGBUILDDIR»/debian/tmp/var/lib/log/mod_gearman /bin/bash /«PKGBUILDDIR»/install-sh -c -m 644 extras/shared.conf /«PKGBUILDDIR»/debian/tmp/usr/share/mod_gearman/shared.conf /bin/bash /«PKGBUILDDIR»/install-sh -c -m 644 extras/standalone_worker.conf /«PKGBUILDDIR»/debian/tmp/usr/share/mod_gearman/standalone_worker.conf /bin/bash /«PKGBUILDDIR»/install-sh -c -m 644 contrib/gearman_proxy.pl /«PKGBUILDDIR»/debian/tmp/usr/share/mod_gearman/gearman_proxy.pl Installation completed: neb module: /«PKGBUILDDIR»/debian/tmp/usr/lib/mod_gearman/mod_gearman.o worker: /«PKGBUILDDIR»/debian/tmp/usr/bin/mod_gearman_worker init script:/«PKGBUILDDIR»/debian/tmp/etc/init.d/mod_gearman_worker check bin: /«PKGBUILDDIR»/debian/tmp/usr/bin/check_gearman send bin: /«PKGBUILDDIR»/debian/tmp/usr/bin/send_gearman send multi bin: /«PKGBUILDDIR»/debian/tmp/usr/bin/send_multi just add the broker line to your nagios.cfg: broker_module=/«PKGBUILDDIR»/debian/tmp/usr/lib/mod_gearman/mod_gearman.o config=/«PKGBUILDDIR»/debian/tmp/etc/mod_gearman_neb.conf configuration: neb module: /«PKGBUILDDIR»/debian/tmp/etc/mod_gearman_neb.conf worker: /«PKGBUILDDIR»/debian/tmp/etc/mod_gearman_worker.conf rm -f /«PKGBUILDDIR»/debian/tmp/usr/lib/mod_gearman/mod_gearman.so make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' rm -f debian/mod-gearman/usr/share/mod_gearman/shared.conf rm -f debian/mod-gearman/usr/share/mod_gearman/standalone_worker.conf chmod 644 /«PKGBUILDDIR»/debian/tmp/usr/share/mod_gearman/mod_gearman_p1.pl help2man --no-info --section=8 --version-string=mod_gearman_worker 1.3.6-1 \ --help-option=-h --include=/«PKGBUILDDIR»/debian/help2man.include \ -n Agent that runs active checks from a gearman queue \ /«PKGBUILDDIR»/debian/tmp/usr/bin/mod_gearman_worker \ /«PKGBUILDDIR»/debian/mod_gearman_worker.8 help2man: can't get `-h' info from /«PKGBUILDDIR»/debian/tmp/usr/bin/mod_gearman_worker Try `--no-discard-stderr' if option outputs to stderr make[1]: *** [override_dh_auto_install] Error 139 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Version: 1.3.6-1 Control: tags -1 unreproducible This does not look
Bug#713070: [Pkg-puppet-devel] Bug#713070: puppetmaster-passenger: fails to upgrade from testing to sid
Andreas Beckmann a...@debian.org writes:
Preserving user changes to /etc/apache2/sites-available/puppetmaster.conf
(renamed from /etc/apache2/sites-available/puppetmaster)...
mv: cannot stat '/etc/apache2/sites-available/puppetmaster.conf': No such
file or directory
dpkg: error processing puppetmaster-passenger (--configure):
subprocess installed post-installation script returned error exit status 1
Thanks.
After an enlightening chat with a fellow DD, it appeared that
/etc/apache/sites-available/puppetmaster{,.conf} is not a conffile (a
file in /etc/ shipped by the package), but a configuration file (just a
file in /etc. It is created by the package .postinst script, but that's
beside the point in this case).
The use of dpkg-maintscript-helper will be rolled back before the next
version of puppet in unstable, as it only works on conffiles. Also, it
has an unhelpful (but not incorrect) error message which confused this
issue for a bit…
--
Stig Sandbeck Mathisen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714609: astromenace: missing Depends: xz-utils
Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package astromenace. (Reading database ... 7531 files and directories currently installed.) Unpacking astromenace (from .../astromenace_1.3.1+repack-2_amd64.deb) ... Setting up astromenace (1.3.1+repack-2) ... tar (child): xz: Cannot exec: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now dpkg: error processing astromenace (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: astromenace xz-utils was recently demoted from required to standard, therefore packages using it must depend on xz-utils. As we can see in dpkg changelog [1] for version 1.16.4: * Add support for liblzma to handle .xz and .lzma compressed files, and switch to it instead of using xz-utils. This removes the xz-utils Pre-Depends from dpkg. Thanks to Jonathan Nieder jrnie...@gmail.com. I am wondering why it was not used. Any ideas? [1] http://ftp-master.metadata.debian.org/changelogs//main/d/dpkg/dpkg_1.16.10_changelog Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701250: Camitk Debian package needs some love [was: Candidates for removal from testing (2013-06-30)]
Hi Emmanuel, On Mon, Jul 01, 2013 at 01:37:15PM +0200, Emmanuel Promayon wrote: Dear Andreas, we were busy to release CamiTK 3.2. This was done last Thursday. Version 3.2 fixed the problem of the compilation on c++11 compliant compiler. In the case of our code it was a STL structure that needed some update (obsolete std::make_pair.. has to be replaced with std::pair..). I quickly checked in a chroot using sid+gcc 4.8 and the upstream fix seems to work. I will make sure that every other things for 3.2 is ok on sid and commit the new changes to the debian-med svn (I need to do some update on the copyright file mostly). I hope to have finish that before the end of the week (and hopefully way before the 8th July deadline) I will update the watch file now to facilitate the process. Let me know if this sounds ok or if you would more information about what I intend to do / the speed it needs to be done. Sounds like a reasonable plan. The only thing that would deserve some enhancement for the future is that it helps if you publish this plan straight to the bug report a bit earlier because this saves us from developing heart attacks in fearing to loose a package in testing. ;-) Kind regards and thanks for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701250: Camitk Debian package needs some love [was: Candidates for removal from testing (2013-06-30)]
Dear Andreas,
we were busy to release CamiTK 3.2. This was done last Thursday. Version
3.2 fixed the problem of the compilation on c++11 compliant compiler.
In the case of our code it was a STL structure that needed some update
(obsolete std::make_pair.. has to be replaced with std::pair..).
I quickly checked in a chroot using sid+gcc 4.8 and the upstream fix
seems to work.
I will make sure that every other things for 3.2 is ok on sid and commit
the new changes to the debian-med svn (I need to do some update on the
copyright file mostly).
I hope to have finish that before the end of the week (and hopefully way
before the 8th July deadline)
I will update the watch file now to facilitate the process.
Let me know if this sounds ok or if you would more information about
what I intend to do / the speed it needs to be done.
Kind regards,
Emmanuel
On 01/07/13 10:39, Andreas Tille wrote:
Hi Emmanuel,
as you can read below camitk needs some love. If you have trouble
caring for it it is perfectly fine to contact the list Debian Med list
and ask for help. I just wanted to make sure you are aware of this
problem.
It might be a good idea to use the package tracking system to subscribe
this package.
Kind regards
Andreas.
- Forwarded message from Niels Thykier ni...@thykier.net -
Date: Sun, 30 Jun 2013 23:32:18 +0200 (CEST)
From: Niels Thykier ni...@thykier.net
To: debian-de...@lists.debian.org
Cc: debian-rele...@lists.debian.org
Subject: Candidates for removal from testing (2013-06-30)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
We are considering removing the following packages from testing as
they have unfixed RC bugs filed against them. The packages can be
found in theattached dd-list.
The packages have been selected based on the following criteria:
- The package had at least one RC bug without activity for the past
14 days.
- If a bug is assigned to multiple packages, both packages will
be affected[1].
- The RC bug affects both unstable and testing.
- The affected package does not have any reverse dependencies in
testing.
- One of their RC bugs had FTBFS in their title. (*)
- The source package had a popcon inst value of 500 or less. (*)
(*) These extra filter rules was applied to keep the list down. The
original list was 246.
If the relevant RC bugs in the affected packages (those listed in
FTBFS-w-popcon-lt-500.txt) are not dealt with before the 8th of
July, the packages will be removed from testing. Note that dealt
with may also include downgrading a severity-inflated bug or fixing
affected versions in the BTS.
For reference, the original list is also included.
Thanks,
Niels (on behalf of the Release Team)
PS: This mail has been BCC'ed to pkg@packages.debian.org for
packaged listed in FTBFS-w-popcon-lt-500.txt.
8 FTBFS-w-popcon-lt-500.txt 8
BUG [SRC]: TITLE
#712367 [bashdb]: bashdb: FTBFS: manuals build fails against textinfo5 because
some incompatibles changes wrt 4.13 and below (some warnings have turned into
errors)
#711787 [falconpl]: falconpl: FTBFS on mipsen
#701412 [prelude-manager]: prelude-manager: ftbfs with eglibc-2.17
#712329 [epix]: epix: FTBFS: manuals build fails against textinfo5 because some
incompatibles changes wrt 4.13 and below (some warnings have turned into errors)
#710633 [orafce]: orafce: FTBFS: plvlex.c:209:3: error: too many arguments to
function 'orafce_sql_yyparse'
#707399 [gedit-valencia-plugin]: gedit-valencia-plugin: FTBFS:
GIRepository-2.0.gir:240.11-240.30: error: expected start element of `parameter'
#710614 [bip]: bip: FTBFS: lex.l:19:6: error: conflicting types for 'yyparse'
#701319 [massxpert]: massxpert: ftbfs with GCC-4.8
#701334 [openvrml]: openvrml: ftbfs with GCC-4.8
#701328 [nwchem]: nwchem: ftbfs with GCC-4.8
#701367 [toonloop]: toonloop: ftbfs with GCC-4.8
#712321 [oneliner-el]: oneliner-el: FTBFS: manuals build fails against
textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings
have turned into errors)
#701411 [prelude-lml]: prelude-lml: ftbfs with eglibc-2.17
#701348 [rnahybrid]: rnahybrid: ftbfs with GCC-4.8
#710636 [mididings]: mididings: FTBFS: src/python_caller.cc:151:42: error:
expected unqualified-id before numeric constant
#701438 [charybdis]: charybdis: ftbfs with eglibc-2.17
#708692 [dnsjava]: FTBFS: requires internet connectivity
#712344 [cfi]: cfi: FTBFS: Package babel Error: Unknow option `swedish'. Either
you misspelled it
#707373 [libccaudio2]: libccaudio2: FTBFS: friends.cpp:1189:25: error:
'ACCESS_DIRECTORY' is not a member of 'ucommon::fsys'
#701300 [ivtools]: ivtools: ftbfs with GCC-4.8
#701428 [turnserver]: turnserver: ftbfs with eglibc-2.17
#712349 [cdk]: cdk: FTBFS: This CDK release requires Ant 1.7.1 or better
#701342 [psychtoolbox-3]: psychtoolbox-3: ftbfs with GCC-4.8
#707411 [zoneminder]: zoneminder: FTBFS: zm_local_camera.cpp:742:49: error:
invalid conversion from '__u32 {aka unsigned
Bug#675231: Rc bug for Psad
Hi Gregor, Do you think you would have time to fix the RC bug against psad? I have not found the time to work on it yet, and as I am going to be on holidays by the end on the week, it will still be opened for some weeks. I should have taken more time to fix it but I have focused on fwknop so far. Regards, -- Franck -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713791: (no subject)
On So, 30 Jun 2013, Hilmar Preuße wrote: Could you fix this? Done. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701250: Camitk Debian package needs some love [was: Candidates for removal from testing (2013-06-30)]
Sounds like a reasonable plan. The only thing that would deserve some enhancement for the future is that it helps if you publish this plan straight to the bug report a bit earlier because this saves us from developing heart attacks in fearing to loose a package in testing. ;-) Duly noted. Sorry for wasting some of your time (and your heart!) by not writing my intention about bugs (especially this RC bugs). In fact I wanted to do that much earlier (before the 3.2 release) and publish a patch, which I see now might have been a better way. I am still learning a lot thanks to debian-med (and still in my MoM in fact!). Thank you again for your work and vigilance! Emmanuel -- Emmanuel Promayon UJF-Grenoble 1, CNRS, TIMC-IMAG UMR 5525 (équipe GMCAO) Institut de l'Ingénierie de l'Information de Santé Faculté de Médecine - 38706 La Tronche cedex - France Tel. +33/0 456 52 00 03 - Fax. +33/0 456 52 00 55 - B7 smime.p7s Description: S/MIME Cryptographic Signature
Bug#714617: Lingot: several vulnerabilities
severity 714617 normal
thanks
thank you for your report.
the problems you identify are bugs, but I think 'critical' is far to high,
there is no security risk as lingot runs unpriviledged, and most of the
problems are only triggered by active action.
I'm currently quite overwhelmed with real life so I won't have time to look
at this before a while,
if you want to submit a patch, Ill be happy to review it and apply.
thanks.
On 1 July 2013 08:05, Hamid Zamani m...@hamidx9.ir wrote:
Package: Lingot
version: 0.9.1-2
Severity: critical
Dear Maintainer,
Several vulnerabilites was found in the latest version of lingot as
explained further below :
[1] :: [File] = lingot-config.c , [Lines] 192 ~ 197 :
if ((fp = fopen(filename, w)) == NULL) {
char buff[100]; // = if i select a filename larger than [100 -
26] and lead the program to here, program will crash.
sprintf(buff, error saving config file %s , filename);
perror(buff);
return;
}
##
[2] :: [File] = lingot.c , [Lines] 41 , 85 ~ 86 , 108 ~ 109 , 127 ~ 131 :
41 : char CONFIG_FILE_NAME[100];
85 ~ 86 :
sprintf(CONFIG_FILE_NAME, %s/ CONFIG_DIR_NAME
DEFAULT_CONFIG_FILE_NAME,
getenv(HOME));
108 ~ 109 :
sprintf(CONFIG_FILE_NAME, %s/%s%s.conf, getenv(HOME),
CONFIG_DIR_NAME, optarg);
127 ~ 131 :
char config_dir[100];
sprintf(config_dir, %s/.lingot/, getenv(HOME));
printf(creating directory %s ...\n, config_dir);
mkdir(config_dir, 0777); // creo el directorio.
printf(creating file %s ...\n, CONFIG_FILE_NAME);
if i change $HOME to a larger one , Lingot will crash here .
##
[3] :: [File] = lingot-config.h , [Lines] 41 ~ :
41 :
struct _LingotConfig {
audio_system_t audio_system;
char audio_dev[3][80]; // = !!!
...
at this section if i manually set
AUDIO_DEV_ALSA = plguhw:0 = AUDIO_DEV_ALSA =
plguhw...AA:0
program crashes here.
##
[4] :: [File] = lingot-config.h , [Lines] ?? :
251 : void lingot_config_load(LingotConfig* config, char* filename) {
273 ~ 283 :
# define MAX_LINE_SIZE 100
char char_buffer[MAX_LINE_SIZE];
if ((fp = fopen(filename, r)) == NULL) {
sprintf(char_buffer,
error opening config file %s, assuming default values ,
filename); // = !!!
perror(char_buffer);
return;
}
and because of MAX_LINE_SIZE if i select a larger filename , program
crashes here .
also is in 192 ~ 197 !
##
If i can help in the fixing process please let me know.
Thank you,
Hamid Zamani
--
Niv Sardi
Bug#701304: Root cause is #701377 (fixed)
The root cause of this is a bug in boost.thread (#701377). Since this bug has been fixed, libavg should build again as well. -- Any technology distinguishable from magic is insufficiently advanced. Ulrich von Zadow | +49-172-7872715 Jabber: co...@c-base.org Skype: uzadow -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 701744 in linux/2.6.32-48, found 701744 in linux-2.6/2.6.32-48
Processing commands for cont...@bugs.debian.org: notfound 701744 linux/2.6.32-48 Bug #701744 [src:linux] [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures The source linux and version 2.6.32-48 do not appear to match any binary packages No longer marked as found in versions linux/2.6.32-48. found 701744 linux-2.6/2.6.32-48 Bug #701744 [src:linux] [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures Marked as found in versions linux-2.6/2.6.32-48. thanks Stopping processing here. Please contact me if you need assistance. -- 701744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#714617: Lingot: several vulnerabilities
Processing commands for cont...@bugs.debian.org: severity 714617 normal Bug #714617 [lingot] Lingot: several vulnerabilities Severity set to 'normal' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 714617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676441: A patch for fixing bug #676441
On 30/06/2013 11:07, Shuxiong Ye wrote:
Hi, I make a patch to fix this bug.
In a cowbuilder, it is failing with: does it sound familar ?
thanks
freeze-compile:
Compiling 79 source files to /tmp/buildd/zeroc-ice-3.4.2/java/lib
freeze-jar:
Building jar: /tmp/buildd/zeroc-ice-3.4.2/java/lib/Freeze.jar
Updating jar: /tmp/buildd/zeroc-ice-3.4.2/java/lib/Freeze.jar
Updating jar: /tmp/buildd/zeroc-ice-3.4.2/java/lib/Freeze.jar
icegridadmin-compile:
Compiling 103 source files to /tmp/buildd/zeroc-ice-3.4.2/java/lib
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ListTreeNode.java:157:
type javax.swing.ComboBoxModel does not take parameters
javax.swing.ComboBoxModelObject createComboBoxModel()
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ListTreeNode.java:162:
type javax.swing.ComboBoxModel does not take parameters
javax.swing.ComboBoxModelObject createComboBoxModel(Object item)
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/SessionKeeper.java:1173:
type javax.swing.JComboBox does not take parameters
private JComboBoxString _alias = new JComboBoxString();
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ServerInstanceEditor.java:218:
type javax.swing.JComboBox does not take parameters
private JComboBoxObject _template = new JComboBoxObject();
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ServiceInstanceEditor.java:227:
type javax.swing.JComboBox does not take parameters
private JComboBoxObject _template = new JComboBoxObject();
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/AdapterEditor.java:606:
type javax.swing.JComboBox does not take parameters
private JComboBoxObject _id = new JComboBoxObject(new Object[]
{DEFAULT_ADAPTER_ID});
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/AdapterEditor.java:607:
type javax.swing.JComboBox does not take parameters
private JComboBoxObject _replicaGroupId = new JComboBoxObject();
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ListTreeNode.java:170:
type javax.swing.AbstractListModel does not take parameters
class ComboBoxModel extends javax.swing.AbstractListModelObject
implements javax.swing.ComboBoxModelObject
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ListTreeNode.java:170:
type javax.swing.ComboBoxModel does not take parameters
class ComboBoxModel extends javax.swing.AbstractListModelObject
implements javax.swing.ComboBoxModelObject
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ServerInstancePropertySetEditor.java:66:
type javax.swing.JComboBox does not take parameters
private JComboBoxObject _id = new JComboBoxObject();
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/ApplicationPane.java:252:
warning:
[deprecation] EMPTY_BORDER in com.jgoodies.forms.factories.Borders has
been deprecated
leftScroll.setBorder(Borders.EMPTY_BORDER);
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ListTreeNode.java:213:
cannot find symbol
symbol : method
fireContentsChanged(IceGridGUI.Application.ListTreeNode.ComboBoxModel,int,int)
location: class IceGridGUI.Application.ListTreeNode.ComboBoxModel
fireContentsChanged(this, -1, -1);
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/SessionKeeper.java:761:
warning: [deprecation] setDefaultDialogBorder() in
com.jgoodies.forms.builder.PanelBuilder has been deprecated
builder.setDefaultDialogBorder();
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/SessionKeeper.java:762:
warning: [deprecation] setRowGroupingEnabled(boolean) in
com.jgoodies.forms.builder.DefaultFormBuilder has been deprecated
builder.setRowGroupingEnabled(true);
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/SessionKeeper.java:763:
warning: [deprecation]
setLineGapSize(com.jgoodies.forms.layout.ConstantSize) in
com.jgoodies.forms.builder.DefaultFormBuilder has been deprecated
builder.setLineGapSize(LayoutStyle.getCurrent().getLinePad());
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/SessionKeeper.java:788:
warning: [deprecation] setDefaultDialogBorder() in
com.jgoodies.forms.builder.PanelBuilder has been deprecated
builder.setDefaultDialogBorder();
^
/tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/SessionKeeper.java:789:
warning: [deprecation] setRowGroupingEnabled(boolean) in
com.jgoodies.forms.builder.DefaultFormBuilder has been deprecated
builder.setRowGroupingEnabled(true);
^
Processed: Re: dopewars: FTBFS: cp: cannot stat '/usr/share/automake-1.11/mkinstalldirs': No such file or directory
Processing commands for cont...@bugs.debian.org: tags 713188 pending Bug #713188 [src:dopewars] dopewars: FTBFS: cp: cannot stat '/usr/share/automake-1.11/mkinstalldirs': No such file or directory Added tag(s) pending. thank you Stopping processing here. Please contact me if you need assistance. -- 713188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714494: ed in /bin
Hi, moving ed back to /bin and making a symlink /usr/bin/ed@ - /bin/ed is, of course, also valid if this helps to fix red. bye, //mirabilos -- 15:41⎜Lo-lan-do:#fusionforge Somebody write a testsuite for helloworld :-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676441: A patch for fixing bug #676441
Most errors look like icegridadmin-compile: Compiling 103 source files to /tmp/buildd/zeroc-ice-3.4.2/java/lib /tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ListTreeNode.java:157: typeComboBoxModel does not take parameters javax.swing.ComboBoxModelObject createComboBoxModel() But in java7[1], javax.swing.ComboBoxModel takes parameters, while in java6[2], no parameters. [1] http://docs.oracle.com/javase/7/docs/api/javax/swing/ComboBoxModel.html [2] http://docs.oracle.com/javase/6/docs/api/javax/swing/ComboBoxModel.htmlhttp://docs.oracle.com/javase/7/docs/api/javax/swing/ComboBoxModel.html are you sure the compile environment is java7? -- Sincerely Shuxiong Ye School of Electronics Engineering and Computer Science, Peking University
Bug#713794: vtk: FTBFS: make[2]: *** [Wrapping/CMakeFiles/vtkWrapPython.dir/all] Error 2
On 26 June 2013 08:59, Julien Cristau julien.cris...@logilab.fr wrote: On Tue, Jun 25, 2013 at 22:34:11 +0100, Dmitrijs Ledkovs wrote: tag 713794 patch pending thanks Uploaded into delayed/5 queue. Your patch is missing a versioned dependency on python2.7 (and dpkg-dev 1.16.1). It's also terrible that the path isn't detected automatically. I disagree that versioned build-dependency on dpkg-dev is required, and it's wrong for uploads to be rejected on that basis. Also, please explain why a versioned dependency on python2.7 is needed, and whether you mean build-dep or dep. FindPythonLibs.cmake module correctly detects proper python paths and can be hinted which version should be preferred (in case when multiple pythons are available). It's terrible that maintainer/upstream did not choose to use standard cmake interface. I just provided a minimal patch to resolve the issue. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676441: A patch for fixing bug #676441
On 01/07/2013 15:12, Shuxiong Ye wrote: Most errors look like icegridadmin-compile: Compiling 103 source files to /tmp/buildd/zeroc-ice-3.4.2/java/lib /tmp/buildd/zeroc-ice-3.4.2/java/src/IceGridGUI/Application/ListTreeNode.java:157: typeComboBoxModel does not take parameters javax.swing.ComboBoxModelObject createComboBoxModel() But in java7[1], javax.swing.ComboBoxModel takes parameters, while in java6[2], no parameters. [1] http://docs.oracle.com/javase/7/docs/api/javax/swing/ComboBoxModel.html [2] http://docs.oracle.com/javase/6/docs/api/javax/swing/ComboBoxModel.html http://docs.oracle.com/javase/7/docs/api/javax/swing/ComboBoxModel.html are you sure the compile environment is java7? No. I used openjdk 6. We need the code to be built with java 6 and 7. Not only 7... (we are still using Java 6 in Debian by default) S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701304: marked as done (libavg: ftbfs with GCC-4.8)
Your message dated Mon, 1 Jul 2013 14:31:47 +0100
with message-id
canbhlugqp9dffu8frqx1aj1ceb9zohuehedmmjphy+jzzrc...@mail.gmail.com
and subject line Re: libavg: ftbfs with GCC-4.8
has caused the Debian Bug report #701304,
regarding libavg: ftbfs with GCC-4.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
701304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:libavg
Version: 1.7.1-2
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.8
The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.
configure: error: boost.thread not found. Aborting.
The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/libavg_1.7.1-2_unstable_gcc48.log
The last lines of the build log are at the end of this report.
To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev
The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.
[...]
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking dependency style of g++... gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking how to run the C preprocessor... gcc -E
checking dependency style of gcc... gcc3
checking for library containing clock_gettime... none required
checking for xml2-config... /usr/bin/xml2-config
checking for xml2... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PANGOFT2_CFLAGS... -pthread -I/usr/include/pango-1.0
-I/usr/include/freetype2 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include
checking for PANGOFT2_LIBS... -lpangoft2-1.0 -lpango-1.0 -lfreetype
-lfontconfig -lgobject-2.0 -lglib-2.0
checking for freetype-config... /usr/bin/freetype-config
checking for freetype... yes
checking for GDK_PIXBUF_CFLAGS... -pthread -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/libpng12 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include
checking for GDK_PIXBUF_LIBS... -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0
checking for LIBRSVG_CFLAGS... -pthread -I/usr/include/librsvg-2.0
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo -I/usr/include/libpng12
-I/usr/include/pixman-1 -I/usr/include/freetype2
checking for LIBRSVG_LIBS... -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lcairo
-lgobject-2.0 -lglib-2.0
checking for FONTCONFIG_CFLAGS...
checking for FONTCONFIG_LIBS... -lfontconfig
checking for FFMPEG_CFLAGS...
checking for FFMPEG_LIBS... -lswscale -lavformat -lavcodec -lavutil
checking libavformat/avformat.h usability... yes
checking libavformat/avformat.h presence... yes
checking for libavformat/avformat.h... yes
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/site-packages
checking for headers required to compile python extensions... found
checking for libpython2.7... found
checking whether the compiler implements namespaces... yes
checking whether the Boost::Thread library is available... no
configure: error: boost.thread not found. Aborting.
make: *** [debian/stamp-configure2.7] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error
Processed: Re: epiphany-browser: domainname not checked on https
Processing commands for cont...@bugs.debian.org: severity 702976 critical Bug #702976 [epiphany-browser] epiphany-browser: domainname not checked on https Severity set to 'critical' from 'important' stop Stopping processing here. Please contact me if you need assistance. -- 702976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714609: dpkg and xz compression
Hi Dpkg Developers, Today I received the bug report [1] about problem with installing of my package astromenace which uses xz compression. Could anyone comment this bug report? It looks as the problem in dpkg. [1] http://bugs.debian.org/cgi-bin/714609 (Please Cc: me, I am not subscribed.) Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: dpkg and xz compression
Processing control commands: tags 714609 + confirmed Bug #714609 [astromenace] astromenace: missing Depends: xz-utils Added tag(s) confirmed. -- 714609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714609: dpkg and xz compression
control: tags 714609 + confirmed Today I received the bug report [1] about problem with installing of my package astromenace which uses xz compression. Could anyone comment this bug report? It looks as the problem in dpkg. Sorry, it is my fault. I have just remembered that tar is used in astromenace.postinst. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714609: dpkg and xz compression
Hi Boris, Am Montag, den 01.07.2013, 17:13 +0300 schrieb Boris Pek: Sorry, it is my fault. I have just remembered that tar is used in astromenace.postinst. as far as I understand the issue, xz support has been added to dpkg. That means that dpkg can now extract deb packages that have been compressed with xz. That does not mean, however, that you can rely on xz being available in the postinst of your package -- astromenace in this specific case. Quite the contrary, native support for the xz format in dpkg means that it is no more necessary for the xz utility to be installed by default. Therefore, if your package needs it, it should depend on it. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714609: astromenace: missing Depends: xz-utils
On 2013-07-01 13:41, Boris Pek wrote:
As we can see in dpkg changelog [1] for version 1.16.4:
not a dpkg problem
I am wondering why it was not used. Any ideas?
Your postinst runs
tar xJf ${DATA_DIR}/RAW_VFS_DATA.tar.xz
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714650: libzrtpcpp: CVE-2013-2221 CVE-2013-2222 CVE-2013-2223
Package: libzrtpcpp Severity: grave Tags: security Hi, please see here http://blog.azimuthsecurity.com/2013/06/attacking-crypto-phones-weaknesses-in.html This was fixed here: https://github.com/wernerd/ZRTPCPP/commit/c8617100f359b217a974938c5539a1dd8a120b0e Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713121: marked as done (libscalar-does-perl: FTBFS: unsatisfiable build-dependency: perl (= 5.16) but 5.14.2-21 is to be installed)
Your message dated Mon, 01 Jul 2013 15:05:39 + with message-id e1utfff-0001im...@franck.debian.org and subject line Bug#713121: fixed in libscalar-does-perl 0.200-1 has caused the Debian Bug report #713121, regarding libscalar-does-perl: FTBFS: unsatisfiable build-dependency: perl (= 5.16) but 5.14.2-21 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libscalar-does-perl Version: 0.102-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install libscalar-does-perl build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-libscalar-does-perl-dummy : Depends: perl (= 5.16) but 5.14.2-21 is to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/libscalar-does-perl_0.102-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: libscalar-does-perl Source-Version: 0.200-1 We believe that the bug you reported is fixed in the latest version of libscalar-does-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard d...@jones.dk (supplier of updated libscalar-does-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 01 Jul 2013 15:50:40 +0200 Source: libscalar-does-perl Binary: libscalar-does-perl Architecture: source all Version: 0.200-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Jonas Smedegaard d...@jones.dk Description: libscalar-does-perl - like ref() but useful Closes: 713121 Changes: libscalar-does-perl (0.200-1) unstable; urgency=low . WAITS-FOR: libpath-tiny-perl # already in NEW . [ upstream ] * New release. + Document relationship with Type::Tiny. + Skip tests involving given/when, smart match, and lexical $_ in Perl = 5.17. + Deprecate Scalar::Does::MooseTypes. + Use Exporter::TypeTiny instead of Sub::Exporter. + Use Type::Tiny and Types::Standard to perform type checking for built-in Scalar::Does roles, and also Scalar::Does::MooseTypes roles. . [ Jonas Smedegaard ] * Add README.source emphasizing control.in file as *not* a show-stopper for contributions, referring to wiki page for details. * Use anonscm.debian.org URL for Vcs-Git. * Add git URL as alternate source. * Stop tracking md5sum of upstream tarball. * Update package relations: + (Build-)depend on libtype-tiny-perl (not libsub-exporter-perl). + Build-depend on libpath-tiny-perl and libmoosex-types-perl: Optionally used in testsuite. + Stop provide/conflict/replace libio-detect-perl: No longer in Debian. * Update
Bug#701319: marked as done (massxpert: ftbfs with GCC-4.8)
Your message dated Mon, 01 Jul 2013 15:33:58 + with message-id e1utg74-000639...@franck.debian.org and subject line Bug#701319: fixed in massxpert 3.4.1-1 has caused the Debian Bug report #701319, regarding massxpert: ftbfs with GCC-4.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:massxpert Version: 3.4.0-1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. qtconcurrentfilter.h:108:47: error: typedef 'Iterator' locally defined but not used [-Werror=unused-local-typedefs] The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/massxpert_3.4.0-1_unstable_gcc48.log The last lines of the build log are at the end of this report. To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues might be caused by the updated glibc. [...] from /«PKGBUILDDIR»/gui/../lib/oligomer.hpp:43, from /«PKGBUILDDIR»/gui/../lib/oligomerList.hpp:48, from /«PKGBUILDDIR»/gui/cleaveOligomerTableView.hpp:47, from /«PKGBUILDDIR»/gui/cleaveOligomerTableViewMimeData.hpp:47, from /«PKGBUILDDIR»/gui/cleaveOligomerTableViewMimeData.cpp:42: /usr/include/qt4/QtCore/qtconcurrentfilter.h: In function 'QtConcurrent::ThreadEngineStartervoid QtConcurrent::filterInternal(Sequence, KeepFunctor, ReduceFunctor)': /usr/include/qt4/QtCore/qtconcurrentfilter.h:108:47: error: typedef 'Iterator' locally defined but not used [-Werror=unused-local-typedefs] typedef typename Sequence::const_iterator Iterator; ^ cc1plus: all warnings being treated as errors cc1plus: all warnings being treated as errors make[3]: *** [gui/CMakeFiles/massxpert.dir/calculatorRecorderDlg.cpp.o] Error 1 make[3]: *** [gui/CMakeFiles/massxpert.dir/atomDefDlg.cpp.o] Error 1 cc1plus: all warnings being treated as errors cc1plus: all warnings being treated as errors make[3]: *** [gui/CMakeFiles/massxpert.dir/cleaveOligomerTableView.cpp.o] Error 1 make[3]: *** [gui/CMakeFiles/massxpert.dir/calculatorWnd.cpp.o] Error 1 In file included from /usr/include/qt4/QtCore/QtCore:94:0, from /usr/include/qt4/QtXml/QtXml:3, from /«PKGBUILDDIR»/gui/../lib/isotope.hpp:45, from /«PKGBUILDDIR»/gui/../lib/atom.hpp:48, from /«PKGBUILDDIR»/gui/../lib/atomCount.hpp:48, from /«PKGBUILDDIR»/gui/../lib/formula.hpp:47, from /«PKGBUILDDIR»/gui/../lib/monomer.hpp:49, from /«PKGBUILDDIR»/gui/../lib/sequence.hpp:47, from /«PKGBUILDDIR»/gui/../lib/oligomer.hpp:43, from /«PKGBUILDDIR»/gui/../lib/oligomerList.hpp:48, from /«PKGBUILDDIR»/gui/cleaveOligomerTableViewModel.hpp:48, from /«PKGBUILDDIR»/gui/cleaveOligomerTableViewModel.cpp:41: /usr/include/qt4/QtCore/qtconcurrentfilter.h: In function 'QtConcurrent::ThreadEngineStartervoid QtConcurrent::filterInternal(Sequence, KeepFunctor, ReduceFunctor)': /usr/include/qt4/QtCore/qtconcurrentfilter.h:108:47: error: typedef 'Iterator' locally defined but not used [-Werror=unused-local-typedefs] typedef typename Sequence::const_iterator Iterator; ^ cc1plus: all warnings being treated as errors make[3]: *** [gui/CMakeFiles/massxpert.dir/application.cpp.o] Error 1 cc1plus: all warnings being treated as errors make[3]: *** [gui/CMakeFiles/massxpert.dir/calculatorChemPadDlg.cpp.o] Error 1 cc1plus: all warnings being treated as errors make[3]: *** [gui/CMakeFiles/massxpert.dir/cleaveOligomerTableViewMimeData.cpp.o] Error 1 cc1plus: all warnings being treated as errors make[3]: *** [gui/CMakeFiles/massxpert.dir/cleavageDlg.cpp.o] Error 1 cc1plus: all warnings being treated as errors make[3]: *** [gui/CMakeFiles/massxpert.dir/cleaveOligomerTableViewModel.cpp.o] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/debian/build-arch' make[2]: ***
Bug#713243: marked as done (libcatalyst-perl: FTBFS: tests failed)
Your message dated Mon, 01 Jul 2013 16:18:12 + with message-id e1utgns-0005i2...@franck.debian.org and subject line Bug#713243: fixed in libcatalyst-perl 5.90030-1 has caused the Debian Bug report #713243, regarding libcatalyst-perl: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libcatalyst-perl Version: 5.90015-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/*.t t/aggregate/*.t t/01use.t . ok t/aggregate.t . skipped: No test aggregation requested t/aggregate/c3_appclass_bug.t . ok t/aggregate/c3_mro.t .. ok t/aggregate/caf_backcompat.t .. ok t/aggregate/catalyst_test_utf8.t .. ok t/aggregate/custom_live_component_controller_action_auto_doublebug.t .. ok t/aggregate/custom_live_path_bug.t ok t/aggregate/deprecated_test_import.t .. ok t/aggregate/deprecated_test_unimported.t .. ok t/aggregate/error_page_dump.t . ok t/aggregate/live_component_controller_action_action.t . ok t/aggregate/live_component_controller_action_auto.t ... ok t/aggregate/live_component_controller_action_begin.t .. ok t/aggregate/live_component_controller_action_chained.t ok t/aggregate/live_component_controller_action_chained2.t ... ok # Failed test 'Unserialize Catalyst::Request' # at t/aggregate/live_component_controller_action_default.t line 66. # Failed test 'Arguments ok' # at t/aggregate/live_component_controller_action_default.t line 70. # Structures begin differing at: # $got = undef # $expected = ARRAY(0x3cf1f20) # Looks like you failed 2 tests of 16. t/aggregate/live_component_controller_action_default.t Dubious, test returned 2 (wstat 512, 0x200) Failed 2/16 subtests t/aggregate/live_component_controller_action_detach.t . ok t/aggregate/live_component_controller_action_die_in_end.t . ok t/aggregate/live_component_controller_action_end.t ok t/aggregate/live_component_controller_action_forward.t ok t/aggregate/live_component_controller_action_global.t . ok t/aggregate/live_component_controller_action_go.t . ok t/aggregate/live_component_controller_action_index.t .. ok t/aggregate/live_component_controller_action_index_or_default.t ... ok t/aggregate/live_component_controller_action_inheritance.t ok t/aggregate/live_component_controller_action_local.t .. ok t/aggregate/live_component_controller_action_multipath.t .. ok t/aggregate/live_component_controller_action_path.t ... ok t/aggregate/live_component_controller_action_path_matchsingle.t ... ok t/aggregate/live_component_controller_action_private.t ok Can't call method captures on an undefined value at t/aggregate/live_component_controller_action_regexp.t line 82. # Looks like you planned 38 tests but ran 17. # Looks like your test exited with 255 just after 17. t/aggregate/live_component_controller_action_regexp.t . Dubious, test returned 255 (wstat 65280, 0xff00) Failed 21/38 subtests Parsing of undecoded UTF-32 at /«PKGBUILDDIR»/blib/lib/Catalyst/Test.pm line 314. t/aggregate/live_component_controller_action_streaming.t .. ok t/aggregate/live_component_controller_action_visit.t .. ok t/aggregate/live_component_controller_actionroles.t ... ok t/aggregate/live_component_controller_anon.t .. ok t/aggregate/live_component_controller_args.t .. ok
Processed: notfound 707191 in llvm-toolchain-3.2/1:3.2repack-2
Processing commands for cont...@bugs.debian.org:
notfound 707191 llvm-toolchain-3.2/1:3.2repack-2
Bug #707191 {Done: Sylvestre Ledru sylves...@debian.org} [lldb-3.2] lldb-3.2:
lldb exits without doing anything
No longer marked as found in versions llvm-toolchain-3.2/1:3.2repack-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
707191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714552: marked as done (FTBFS: missing build-dependency on python3-d2to1)
Your message dated Mon, 01 Jul 2013 17:18:22 +
with message-id e1uthk6-0003d7...@franck.debian.org
and subject line Bug#714552: fixed in python-pbr 0.5.16-4
has caused the Debian Bug report #714552,
regarding FTBFS: missing build-dependency on python3-d2to1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
714552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-pbr
Version: 0.5.16-3
Severity: serious
Justification: fails to build from source
python-pbr fails to build from source because it doesn't build-depend
on python3-d2to1.
When the build system fails to find d2to1 it tries to download the module
from PyPI. This obviously fails without a network connection.
As package builds must not rely on external network connectivity the
build-dependency on python3-d2to1 is necessary.
Build log:
set -ex; python3.2 setup.py build; python3.3 setup.py build;
+ python3.2 setup.py build
Download error on http://pypi.python.org/simple/d2to1/: [Errno -2] Name or
service not known -- Some packages may not be found!
Download error on http://pypi.python.org/simple/d2to1/: [Errno -2] Name or
service not known -- Some packages may not be found!
Couldn't find index page for 'd2to1' (maybe misspelled?)
Download error on http://pypi.python.org/simple/: [Errno -2] Name or service
not known -- Some packages may not be found!
No local packages or download links found for d2to1=0.2.10,0.3
Traceback (most recent call last):
File setup.py, line 21, in module
d2to1=True)
File /usr/lib/python3.2/distutils/core.py, line 109, in setup
_setup_distribution = dist = klass(attrs)
File /usr/lib/python3/dist-packages/setuptools/dist.py, line 221, in
__init__
self.fetch_build_eggs(attrs.pop('setup_requires'))
File /usr/lib/python3/dist-packages/setuptools/dist.py, line 245, in
fetch_build_eggs
parse_requirements(requires), installer=self.fetch_build_egg
File /usr/lib/python3/dist-packages/pkg_resources.py, line 586, in resolve
dist = best[req.key] = env.best_match(req, self, installer)
File /usr/lib/python3/dist-packages/pkg_resources.py, line 832, in
best_match
return self.obtain(req, installer) # try and download/install
File /usr/lib/python3/dist-packages/pkg_resources.py, line 844, in obtain
return installer(requirement)
File /usr/lib/python3/dist-packages/setuptools/dist.py, line 295, in
fetch_build_egg
return cmd.easy_install(req)
File /usr/lib/python3/dist-packages/setuptools/command/easy_install.py,
line 616, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for
Requirement.parse('d2to1=0.2.10,0.3')
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory `/tmp/buildd/python-pbr-0.5.16'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
---End Message---
---BeginMessage---
Source: python-pbr
Source-Version: 0.5.16-4
We believe that the bug you reported is fixed in the latest version of
python-pbr, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 714...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand z...@debian.org (supplier of updated python-pbr package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 02 Jul 2013 01:00:52 +0800
Source: python-pbr
Binary: python-pbr python3-pbr
Architecture: source all
Version: 0.5.16-4
Distribution: unstable
Urgency: low
Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org
Changed-By: Thomas Goirand z...@debian.org
Description:
python-pbr - inject useful and sensible default behaviors into setuptools - Py
python3-pbr - inject useful and sensible default behaviors into setuptools - Py
Closes: 714552
Changes:
python-pbr (0.5.16-4) unstable; urgency=low
.
* Build-Depends: on python3-d2to1 (Closes: #714552).
Checksums-Sha1:
3989a5ecbd29410c1077cd0bc54c9a409d9464cf 1800 python-pbr_0.5.16-4.dsc
e8052910ec4b17bf7eac6baebf1df38b6ae8b778 3714 python-pbr_0.5.16-4.debian.tar.gz
Bug#675231: Rc bug for Psad
On Mon, 01 Jul 2013 13:58:51 +0200, Franck Joncourt wrote: Do you think you would have time to fix the RC bug against psad? I have not found the time to work on it yet, and as I am going to be on holidays by the end on the week, it will still be opened for some weeks. I should have taken more time to fix it but I have focused on fwknop so far. Hey, why not looking at this nasty bug again :) Ok, so first of all I can (unsurprisingly) reproduce it with Andreas' recipe. And I think I found a solution; preinst scripts can also be called as preinst install old-version so we can just extend the condition and should be done. In my test with the same steps this works (and the upgrade case of course till works too). No guarantees about side effects :) If this looks good to both of you I'm happy to upload if you can't do it in the next days. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Tracy Chapman: Open Arms diff -Nru psad-2.2.1/debian/changelog psad-2.2.1/debian/changelog --- psad-2.2.1/debian/changelog 2013-01-06 11:38:52.0 +0100 +++ psad-2.2.1/debian/changelog 2013-07-01 19:15:26.0 +0200 @@ -1,3 +1,14 @@ +psad (2.2.1-2.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Fix prompting due to modified conffiles which were not modified by +the user: +d/psad.preinst: also revert changes to conffile when we install with an +old version. +(Closes: #675231) + + -- gregor herrmann gre...@debian.org Mon, 01 Jul 2013 18:56:46 +0200 + psad (2.2.1-2) unstable; urgency=low * Enabled back the kmsgsd daemon. diff -Nru psad-2.2.1/debian/psad.preinst psad-2.2.1/debian/psad.preinst --- psad-2.2.1/debian/psad.preinst 2013-01-06 11:38:52.0 +0100 +++ psad-2.2.1/debian/psad.preinst 2013-07-01 19:36:36.0 +0200 @@ -34,14 +34,19 @@ rm $conffile.old } -if [ $1 = upgrade ]; then +if [ $1 = upgrade -o $1 = install ]; then # Revert changes added to the configuration file by the postinst script # if we are upgrading from a version which changed it (#688891) +# or if we are installed with a prior version (#675231) if [ -n $2 ] dpkg --compare-versions 2.2-3 gt $2 ; then update_conf _CHANGEME_ HOSTNAME /etc/psad/psad.conf fi +fi + +if [ $1 = upgrade ]; then + # This script is only intended to fix bug #497574. # We check for an upgrade from Psad older than 2.1.5 and remove the old # Psad process if needed. signature.asc Description: Digital signature
Bug#713447: marked as done (imagination: FTBFS: ld: imagination-support.o: undefined reference to symbol 'g_module_symbol')
Your message dated Mon, 01 Jul 2013 17:48:04 + with message-id e1uticq-0001au...@franck.debian.org and subject line Bug#713447: fixed in imagination 3.0-3 has caused the Debian Bug report #713447, regarding imagination: FTBFS: ld: imagination-support.o: undefined reference to symbol 'g_module_symbol' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: imagination Version: 3.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add explicitly the offending lib to LD flags. Relevant part: gcc -DPACKAGE_NAME=\imagination\ -DPACKAGE_TARNAME=\imagination\ -DPACKAGE_VERSION=\3.0\ -DPACKAGE_STRING=\imagination\ 3.0\ -DPACKAGE_BUGREPORT=\http://sourceforge.net/tracker/\?group_id=244319\atid=1125540\; -DPACKAGE_URL=\\ -DPACKAGE=\imagination\ -DVERSION=\3.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DREVISION=\r1\ -DGETTEXT_PACKAGE=\imagination\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -DPACKAGE_LIB_DIR=\/usr/lib/x86_64-linux-gnu\ -DPACKAGE_DATA_DIR=\/usr/share\ -DPACKAGE_LOCALE_DIR=\/usr/share/locale\ -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -D_FORTIFY_SOURCE=2 -DDATADIR=\/usr/share\ -g -Wall -c -o imagination-img_sox.o `test -f 'img_sox.c' || echo './'`img_sox.c img_sox.c: In function 'output_flow': img_sox.c:34:10: warning: unused variable 'len' [-Wunused-variable] size_t len = sox_write( global-output, ibuf, *isamp ); ^ CCLD imagination /usr/bin/ld: imagination-support.o: undefined reference to symbol 'g_module_symbol' /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/imagination_3.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: imagination Source-Version: 3.0-3 We believe that the bug you reported is fixed in the latest version of imagination, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Starr-Bochicchio a...@debian.org (supplier of updated imagination package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 30 Jun 2013 12:32:54 -0400 Source: imagination Binary: imagination imagination-common Architecture: source amd64 all Version: 3.0-3 Distribution: unstable Urgency: low Maintainer: Andrew Starr-Bochicchio a...@debian.org Changed-By: Andrew Starr-Bochicchio a...@debian.org Description: imagination - DVD slide show maker imagination-common - DVD slide show maker - common files Closes: 713447 Changes: imagination (3.0-3) unstable; urgency=low . * Promote libav suggests to recommends as they are in main now, and bump versions for 0.8. * lib_underlinkage.patch: Fix FTBFS by adding missing lib
Bug#710917: marked as done (quantum-common: fails to upgrade from 'testing' - trying to overwrite /usr/bin/quantum-*-agent)
Your message dated Mon, 01 Jul 2013 18:04:21 + with message-id e1utisb-00069s...@franck.debian.org and subject line Bug#710917: fixed in quantum 2013.1.2-2 has caused the Debian Bug report #710917, regarding quantum-common: fails to upgrade from 'testing' - trying to overwrite /usr/bin/quantum-*-agent to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 710917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: quantum-common Version: 2013.1.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + quantum-plugin-openvswitch-agent quantum-plugin-linuxbridge-agent Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace quantum-common 2012.1-1 (using .../quantum-common_2013.1.1-3_all.deb) ... Unpacking replacement quantum-common ... dpkg: error processing /var/cache/apt/archives/quantum-common_2013.1.1-3_all.deb (--unpack): trying to overwrite '/usr/bin/quantum-openvswitch-agent', which is also in package quantum-plugin-openvswitch-agent 2012.1-5+deb70u1 Preparing to replace quantum-common 2012.1-1 (using .../quantum-common_2013.1.1-3_all.deb) ... Unpacking replacement quantum-common ... dpkg: error processing /var/cache/apt/archives/quantum-common_2013.1.1-3_all.deb (--unpack): trying to overwrite '/usr/bin/quantum-linuxbridge-agent', which is also in package quantum-plugin-linuxbridge-agent 2012.1-5+deb70u1 cheers, Andreas quantum-plugin-openvswitch-agent_2013.1.1-3.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: quantum Source-Version: 2013.1.2-2 We believe that the bug you reported is fixed in the latest version of quantum, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated quantum package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Jun 2013 15:43:28 +0800 Source: quantum Binary: python-quantum quantum-server quantum-common quantum-plugin-cisco quantum-plugin-nec quantum-plugin-nec-agent quantum-plugin-bigswitch quantum-plugin-hyperv quantum-plugin-brocade quantum-plugin-plumgrid quantum-plugin-metaplugin quantum-plugin-nicira quantum-l3-agent quantum-dhcp-agent quantum-metadata-agent quantum-lbaas-agent quantum-plugin-openvswitch quantum-plugin-openvswitch-agent quantum-plugin-linuxbridge quantum-plugin-linuxbridge-agent Architecture: source all Version: 2013.1.2-2 Distribution: unstable Urgency: low Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-quantum - OpenStack virtual network service - python library quantum-common - OpenStack virtual network service - common quantum-dhcp-agent - Quantum is a virtual network service for Openstack - (dhcp agent) quantum-l3-agent - Quantum is a virtual network service for Openstack - (l3 agent) quantum-lbaas-agent - Quantum is a virtual network service for Openstack - LBaaS agent quantum-metadata-agent - Quantum is a virtual network service for Openstack - metadata age quantum-plugin-bigswitch - Quantum virtual network service - BigSwitch plugin quantum-plugin-brocade - Quantum is a virtual network service for Openstack - Brocade plug quantum-plugin-cisco - OpenStack virtual network service - Cisco plugin quantum-plugin-hyperv - Quantum virtual network service - Hyper-V plugin quantum-plugin-linuxbridge - OpenStack virtual network service - Linux bridge plugin quantum-plugin-linuxbridge-agent - OpenStack virtual network service - Linux bridge agent quantum-plugin-metaplugin - Quantum virtual network service - metaplugin
Bug#710635: (no subject)
The problem will be fixed in the next release, version 0.3.1 which is due in two or three weeks ; I'll package it as soon as it is available. Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714133: marked as done (python-qpid: CVE-2013-1909)
Your message dated Mon, 01 Jul 2013 19:03:41 + with message-id e1utjo1-0002ss...@franck.debian.org and subject line Bug#714133: fixed in qpid-python 0.22-1 has caused the Debian Bug report #714133, regarding python-qpid: CVE-2013-1909 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 714133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-qpid Severity: grave Tags: security Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-1909 for details. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: qpid-python Source-Version: 0.22-1 We believe that the bug you reported is fixed in the latest version of qpid-python, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 714...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barry deFreese bdefre...@debian.org (supplier of updated qpid-python package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 10:14:06 -0400 Source: qpid-python Binary: python-qpid Architecture: source all Version: 0.22-1 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Barry deFreese bdefre...@debian.org Description: python-qpid - Python bindings for qpid/mlib Closes: 706292 714133 Changes: qpid-python (0.22-1) unstable; urgency=low . * QA upload. * New upstream release. (Closes: #714133). + Includes fix for CVE-2013-1909. * Can now import qpid. (Closes: #706292). * License has been resolved upstream so include AMPQ specs. * Fix capitalization in package description. * Bump debhelper build-dep and compat to 9. * Bump Standards Version to 3.9.4. Checksums-Sha1: e77c44f9d91d52fd7aabbc9382ca49a8ee5c8a84 1119 qpid-python_0.22-1.dsc ba237a93f8f92bd846747846a2948abf3ca87791 211711 qpid-python_0.22.orig.tar.gz ad23b9cb7d32d0981da365480dc5c0c22e5643f2 2820 qpid-python_0.22-1.debian.tar.gz 3cafa208132ea528691d3b8f8666acbc00b6bcf1 165494 python-qpid_0.22-1_all.deb Checksums-Sha256: 37e90eb4332c50cefde38a0d1c1b945b3349a99c54d6a35e44a1d55894ebc137 1119 qpid-python_0.22-1.dsc 6bb9cd50497ab6f7d1ebc16119dbe2bd0d24109bfa0a5a5ae064165d5430ed6e 211711 qpid-python_0.22.orig.tar.gz a21a3645e1c5db09b19b77c4baf68bb53270d8ab7d99581d87c51ef815f87cf7 2820 qpid-python_0.22-1.debian.tar.gz 0b122a7a2e55caa2abe47ec19c39bee83d2423c1d9f67bfe7e6a9aae701986f4 165494 python-qpid_0.22-1_all.deb Files: 51120491298c728710fded6c595bc2b4 1119 python extra qpid-python_0.22-1.dsc e7d088a4cf55fe3dc246bd613bcf4460 211711 python extra qpid-python_0.22.orig.tar.gz a71b740d4c7cd26f7e8e4c7ac5685cc8 2820 python extra qpid-python_0.22-1.debian.tar.gz d5bba66b89d5750c9d126801d58be7e8 165494 python extra python-qpid_0.22-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHRmuwACgkQ5ItltUs5T35P6gCg55lPW1TanVEyKkUVcRRGeApy fpMAnjxr2GDU0/IODwEue0FhUrjefpSa =TKF4 -END PGP SIGNATUREEnd Message---
Bug#706292: marked as done (qpid-python: python can't import qpid)
Your message dated Mon, 01 Jul 2013 19:03:41 + with message-id e1utjo1-0002sn...@franck.debian.org and subject line Bug#706292: fixed in qpid-python 0.22-1 has caused the Debian Bug report #706292, regarding qpid-python: python can't import qpid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: src: qpid-python version: 0.16+repack-1 severity: serious I apologize for this. I accidentally hit the trigger before I'd finished testing these changes. python -c import qpid is currently broken because of that. Again, I'm sorry, and I'll fix it. Best wishes, Mike ---End Message--- ---BeginMessage--- Source: qpid-python Source-Version: 0.22-1 We believe that the bug you reported is fixed in the latest version of qpid-python, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 706...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barry deFreese bdefre...@debian.org (supplier of updated qpid-python package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 10:14:06 -0400 Source: qpid-python Binary: python-qpid Architecture: source all Version: 0.22-1 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Barry deFreese bdefre...@debian.org Description: python-qpid - Python bindings for qpid/mlib Closes: 706292 714133 Changes: qpid-python (0.22-1) unstable; urgency=low . * QA upload. * New upstream release. (Closes: #714133). + Includes fix for CVE-2013-1909. * Can now import qpid. (Closes: #706292). * License has been resolved upstream so include AMPQ specs. * Fix capitalization in package description. * Bump debhelper build-dep and compat to 9. * Bump Standards Version to 3.9.4. Checksums-Sha1: e77c44f9d91d52fd7aabbc9382ca49a8ee5c8a84 1119 qpid-python_0.22-1.dsc ba237a93f8f92bd846747846a2948abf3ca87791 211711 qpid-python_0.22.orig.tar.gz ad23b9cb7d32d0981da365480dc5c0c22e5643f2 2820 qpid-python_0.22-1.debian.tar.gz 3cafa208132ea528691d3b8f8666acbc00b6bcf1 165494 python-qpid_0.22-1_all.deb Checksums-Sha256: 37e90eb4332c50cefde38a0d1c1b945b3349a99c54d6a35e44a1d55894ebc137 1119 qpid-python_0.22-1.dsc 6bb9cd50497ab6f7d1ebc16119dbe2bd0d24109bfa0a5a5ae064165d5430ed6e 211711 qpid-python_0.22.orig.tar.gz a21a3645e1c5db09b19b77c4baf68bb53270d8ab7d99581d87c51ef815f87cf7 2820 qpid-python_0.22-1.debian.tar.gz 0b122a7a2e55caa2abe47ec19c39bee83d2423c1d9f67bfe7e6a9aae701986f4 165494 python-qpid_0.22-1_all.deb Files: 51120491298c728710fded6c595bc2b4 1119 python extra qpid-python_0.22-1.dsc e7d088a4cf55fe3dc246bd613bcf4460 211711 python extra qpid-python_0.22.orig.tar.gz a71b740d4c7cd26f7e8e4c7ac5685cc8 2820 python extra qpid-python_0.22-1.debian.tar.gz d5bba66b89d5750c9d126801d58be7e8 165494 python extra python-qpid_0.22-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHRmuwACgkQ5ItltUs5T35P6gCg55lPW1TanVEyKkUVcRRGeApy fpMAnjxr2GDU0/IODwEue0FhUrjefpSa =TKF4 -END PGP SIGNATUREEnd Message---
Bug#713115: marked as done (liborcus: FTBFS: build-dependency not installable: libmdds-dev)
Your message dated Mon, 1 Jul 2013 21:24:08 +0200 with message-id 20130701192408.ga14...@rene-engelhard.de and subject line Re: Bug#713115: liborcus: FTBFS: build-dependency not installable: libmdds-dev has caused the Debian Bug report #713115, regarding liborcus: FTBFS: build-dependency not installable: libmdds-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: liborcus Version: 0.3.0-7 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install liborcus build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-liborcus-dummy : Depends: libmdds-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/liborcus_0.3.0-7_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- [ sorry, just saw the bug today... ] Hi, On Sat, Jun 22, 2013 at 01:37:23PM +0200, Lucas Nussbaum wrote: The following packages have unmet dependencies: sbuild-build-depends-liborcus-dummy : Depends: libmdds-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/liborcus_0.3.0-7_unstable.log Which is totally saying nothing except the above (surprise, NOT!) I suspect a temporary sid breakage there, libmdds-dev is (and was then) there: libmdds-dev | 0.7.1-3 | jessie | all libmdds-dev | 0.7.1-3 | sid | all Especially as LO uploaded later (2013-06-24) found it fine: https://buildd.debian.org/status/logs.php?pkg=libreofficever=1%3A4.1.0~rc1-1suite=experimental Please, a bit more care... Regards, Rene---End Message---
Bug#713115: liborcus: FTBFS: build-dependency not installable: libmdds-dev
Hi, On Mon, Jul 01, 2013 at 09:24:08PM +0200, Rene Engelhard wrote: I suspect a temporary sid breakage there, libmdds-dev is (and was then) there: libmdds-dev | 0.7.1-3 | jessie | all libmdds-dev | 0.7.1-3 | sid | all Or - as I just mentioned on IRC, sorry forgot that here: 21:25 _rene_ lucas: ping? about your archive rebuilds, is that all in clean chroots? or do you reuse some chroots? 21:25 -!- Myon [~m...@myon.noc.oftc.net] has joined #debian-devel 21:26 _rene_ lucas: I only can explain 713115 by apt insisting on keeping libboost-dev 21:26 _rene_ lucas: due to gcc 4.8 etc. (boost 1.49 was fixed far later than needed) mdds etc. already build-dep on libboost1.53-dev 21:26 _rene_ lucas: which of course conflicts against anything wanting libboost-dev Especially as LO uploaded later (2013-06-24) found it fine: https://buildd.debian.org/status/logs.php?pkg=libreofficever=1%3A4.1.0~rc1-1suite=experimental Just tried here (current sid, amd64): root@frodo:/# apt-get install libmdds-dev Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libboost1.53-dev libicu48 Suggested packages: libboost1.53-doc libboost-atomic1.53-dev libboost-chrono1.53-dev libboost-context1.53-dev libboost-date-time1.53-dev libboost-exception1.53-dev libboost-filesystem1.53-dev libboost-graph1.53-dev libboost-graph-parallel1.53-dev libboost-iostreams1.53-dev libboost-locale1.53-dev libboost-math1.53-dev libboost-mpi1.53-dev libboost-mpi-python1.53-dev libboost-program-options1.53-dev libboost-python1.53-dev libboost-random1.53-dev libboost-regex1.53-dev libboost-serialization1.53-dev libboost-signals1.53-dev libboost-system1.53-dev libboost-test1.53-dev libboost-thread1.53-dev libboost-timer1.53-dev libboost-wave1.53-dev xsltproc doxygen docbook-xml docbook-xsl default-jdk fop The following NEW packages will be installed: libboost1.53-dev libicu48 libmdds-dev 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 9842 kB/14.7 MB of archives. After this operation, 120 MB of additional disk space will be used. And if you say but 4.1.0 in experimental use liborcus 0.5.1 and mdds 0.8.1 from experimental, sure, but that shouldn't affect it. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 675231
Processing commands for cont...@bugs.debian.org: tags 675231 + patch Bug #675231 [psad] psad: prompting due to modified conffiles which were not modified by the user Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 675231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713115: liborcus: FTBFS: build-dependency not installable: libmdds-dev
reopen 713115 thanks Hi, On Mon, Jul 01, 2013 at 09:33:02PM +0200, Rene Engelhard wrote: On Mon, Jul 01, 2013 at 09:24:08PM +0200, Rene Engelhard wrote: I suspect a temporary sid breakage there, libmdds-dev is (and was then) there: libmdds-dev | 0.7.1-3 | jessie | all libmdds-dev | 0.7.1-3 | sid | all Or - as I just mentioned on IRC, sorry forgot that here: 21:25 _rene_ lucas: ping? about your archive rebuilds, is that all in clean chroots? or do you reuse some chroots? 21:25 -!- Myon [~m...@myon.noc.oftc.net] has joined #debian-devel 21:26 _rene_ lucas: I only can explain 713115 by apt insisting on keeping libboost-dev 21:26 _rene_ lucas: due to gcc 4.8 etc. (boost 1.49 was fixed far later than needed) mdds etc. already build-dep on libboost1.53-dev 21:26 _rene_ lucas: which of course conflicts against anything wanting libboost-dev Which - thanks DonKult for opening my eyes on IRC - I simply forgot about the version skew - is because liborcus build-deps on libmdds-dev (depends on 1.53) and liboost-dev (1.49 right now). Will make orcus also explicitely use 1.53... Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#713115: liborcus: FTBFS: build-dependency not installable: libmdds-dev
Processing commands for cont...@bugs.debian.org:
reopen 713115
Bug #713115 {Done: Rene Engelhard r...@debian.org} [src:liborcus] liborcus:
FTBFS: build-dependency not installable: libmdds-dev
Bug reopened
Ignoring request to alter fixed versions of bug #713115 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
713115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714595: liballegro4.2-dev: not installable in sid
Hi, the dev package is now called liballegro4-dev. If you still think there is a bug, please explain again. Cheers, Tobias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714699: libvirt: CVE-2013-2218: crash when listing network interfaces with filters
Package: libvirt Version: 1.0.6-1 Severity: grave Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for libvirt. CVE-2013-2218[0]: crash when listing network interfaces with filters The issue was fixed with commit [1] and introduced previously with [2]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2218 http://security-tracker.debian.org/tracker/CVE-2013-2218 [1] http://libvirt.org/git/?p=libvirt.git;a=commit;h=244e0b8cf15ca2ef48d82058e728656e6c4bad11 [2] http://libvirt.org/git/?p=libvirt.git;a=commit;h=7ac2c4fe624f30f2c8270116513fa2ddab07631f Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713068: marked as done (k3d: FTBFS (gdk/gdkglcontext.h: No such file or directory))
Your message dated Mon, 1 Jul 2013 21:57:39 +0100 with message-id CAPQ4b8kf677=p3vxybcxg+hdlpofhevow+4ppturbne177i...@mail.gmail.com and subject line Re: Bug#713068: k3d: FTBFS (gdk/gdkglcontext.h: No such file or directory) has caused the Debian Bug report #713068, regarding k3d: FTBFS (gdk/gdkglcontext.h: No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: k3d Version: 0.8.0.2-19 Severity: serious Tags: jessie sid Hi, k3d FTBFS on all architectures where it was binNMUed for the cgal transition. From the amd64 build log: [ 16%] Building CXX object k3dsdk/ngui/CMakeFiles/k3dsdk-ngui.dir/auto_property_page.cpp.o cd /«PKGBUILDDIR»/obj-mips-linux-gnu/k3dsdk/ngui /usr/bin/c++ -DK3D_HAVE_EXPAT -DK3D_HAVE_SIGC_2_0 -Dk3dsdk_ngui_EXPORTS -g -O2 -Wformat -Werror=format-security -pipe -Wall -frounding-math -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/k3dsdk/gil -I/«PKGBUILDDIR»/obj-mips-linux-gnu/k3dsdk -I/usr/include/glibmm-2.4 -I/usr/lib/mips-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/mips-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/mips-linux-gnu/glib-2.0/include -I/usr/include/uuid -I/usr/include/giomm-2.4 -I/usr/lib/mips-linux-gnu/giomm-2.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/lib/mips-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/harfbuzz -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/cairomm-1.0/include-o CMakeFiles/k3dsdk-ngui.dir/auto_property_page.cpp.o -c /«PKGBUILDDIR»/k3dsdk/ngui/auto_property_page.cpp In file included from /«PKGBUILDDIR»/k3dsdk/ngui/auto_property_page.cpp:34:0: /«PKGBUILDDIR»/k3dsdk/ngui/document_state.h:34:30: fatal error: gdk/gdkglcontext.h: No such file or directory compilation terminated. Full logs available via https://buildd.debian.org/status/package.php?p=k3d Regards, Adam ---End Message--- ---BeginMessage--- Control: notfound -1 0.8.0.2-20 2013/6/22 Adam D. Barratt a...@adam-barratt.org.uk: Source: k3d Version: 0.8.0.2-19 Severity: serious Tags: jessie sid Hi, k3d FTBFS on all architectures where it was binNMUed for the cgal transition. From the amd64 build log: [ 16%] Building CXX object k3dsdk/ngui/CMakeFiles/k3dsdk-ngui.dir/auto_property_page.cpp.o cd /«PKGBUILDDIR»/obj-mips-linux-gnu/k3dsdk/ngui /usr/bin/c++ -DK3D_HAVE_EXPAT -DK3D_HAVE_SIGC_2_0 -Dk3dsdk_ngui_EXPORTS -g -O2 -Wformat -Werror=format-security -pipe -Wall -frounding-math -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/k3dsdk/gil -I/«PKGBUILDDIR»/obj-mips-linux-gnu/k3dsdk -I/usr/include/glibmm-2.4 -I/usr/lib/mips-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/mips-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/mips-linux-gnu/glib-2.0/include -I/usr/include/uuid -I/usr/include/giomm-2.4 -I/usr/lib/mips-linux-gnu/giomm-2.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/lib/mips-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/harfbuzz -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/cairomm-1.0/include-o CMakeFiles/k3dsdk-ngui.dir/auto_property_page.cpp.o -c /«PKGBUILDDIR»/k3dsdk/ngui/auto_property_page.cpp In file included from /«PKGBUILDDIR»/k3dsdk/ngui/auto_property_page.cpp:34:0: /«PKGBUILDDIR»/k3dsdk/ngui/document_state.h:34:30: fatal error: gdk/gdkglcontext.h: No such file or directory compilation terminated. Full logs available via https://buildd.debian.org/status/package.php?p=k3d Thanks for the report. This seems to have been caused by the dependency libgtkglext, fixed in this upload:
Bug#714609: marked as done (astromenace: missing Depends: xz-utils)
Your message dated Mon, 01 Jul 2013 21:03:09 + with message-id e1utlfd-0002gs...@franck.debian.org and subject line Bug#714609: fixed in astromenace 1.3.1+repack-3 has caused the Debian Bug report #714609, regarding astromenace: missing Depends: xz-utils to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 714609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: astromenace Version: 1.3.1+repack-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package astromenace. (Reading database ... 7531 files and directories currently installed.) Unpacking astromenace (from .../astromenace_1.3.1+repack-2_amd64.deb) ... Setting up astromenace (1.3.1+repack-2) ... tar (child): xz: Cannot exec: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now dpkg: error processing astromenace (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: astromenace xz-utils was recently demoted from required to standard, therefore packages using it must depend on xz-utils. cheers, Andreas astromenace_1.3.1+repack-2.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: astromenace Source-Version: 1.3.1+repack-3 We believe that the bug you reported is fixed in the latest version of astromenace, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 714...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boris Pek tehn...@debian.org (supplier of updated astromenace package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 22:02:35 +0300 Source: astromenace Binary: astromenace Architecture: source i386 Version: 1.3.1+repack-3 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Boris Pek tehn...@debian.org Description: astromenace - hardcore 3D space shooter with spaceship upgrade possibilities Closes: 714609 Changes: astromenace (1.3.1+repack-3) unstable; urgency=low . * Add temporary patch debian/patches/08_do_not_touch_home_dir.patch: Without this patch AstroMenace creates directory ~/.config/astromenace/ during generation of gamedata.vfs file. When sudo is used for package installation, this created directory is owned by root, so game settings cannot be saved by user. (LP: #1181847) * Add xz-utils to astromenace dependencies. (Closes: #714609) * Fix lintian note desktop-entry-lacks-keywords-entry. Checksums-Sha1: 5875a6742a53cb5cde474e6093be81c48b100f2b 2183 astromenace_1.3.1+repack-3.dsc 157af8405d435d826025f3fa3bf378367e5e7d14 8672 astromenace_1.3.1+repack-3.debian.tar.xz a2ee4550bd6491629525643ff0742a3fb00d3fe3 300982 astromenace_1.3.1+repack-3_i386.deb Checksums-Sha256: aa821228f6d07e0f9f06046be8dbd79274b004fc528375a2bf924d361bb0460f 2183 astromenace_1.3.1+repack-3.dsc 1beb186cce32813948e94322cfac77ee1821be972fb740996372de2568a92044 8672 astromenace_1.3.1+repack-3.debian.tar.xz ff339a99687b4cb283cf40202a332f1936b02139a60d67fc5fe1591926b2486f 300982 astromenace_1.3.1+repack-3_i386.deb Files: fd83517b2c68c2ae84205fa7c1740184 2183 contrib/games optional astromenace_1.3.1+repack-3.dsc fee99e0da861fdc492fdecfbd6baa578 8672 contrib/games optional astromenace_1.3.1+repack-3.debian.tar.xz 65879e21dccd030dcf2a5a8aafc75c7a 300982 contrib/games optional astromenace_1.3.1+repack-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJR0dV/AAoJENABW9Eo85J4/rwP/3iszSPAyMPwD1LvCjzIHwAW m52KZsf8YI/4dFBRM4N73lPaNMHIIvOM0aDaX85uU0YwaBn74kY3PiZp7nGFfERB
Bug#713569: marked as done (liblangtag: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o): undefined reference to symbol '__pthread_unregister_cancel@
Your message dated Mon, 01 Jul 2013 21:04:23 + with message-id e1utlgp-0003jd...@franck.debian.org and subject line Bug#713569: fixed in liblangtag 0.5.1-2 has caused the Debian Bug report #713569, regarding liblangtag: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o): undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: liblangtag Version: 0.5.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add explicitly the offending lib to LD flags. Relevant part: gcc -DHAVE_CONFIG_H -I. -I.. -I../liblangtag -I.. -DTEST_DATADIR=\/«PKGBUILDDIR»/data\ -DTEST_MODDIR=\/«PKGBUILDDIR»/extensions/.libs\ -D__LANGTAG_COMPILATION -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -c main.c /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -Wl,-z,relro -o check-extlang check-extlang.o main.o-Wl,-z,relro ../liblangtag/liblangtag.la -lcheck_pic -lrt -lm libtool: link: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -Wl,-z -Wl,relro -o .libs/check-extlang check-extlang.o main.o -Wl,-z -Wl,relro ../liblangtag/.libs/liblangtag.so -lcheck_pic -lrt -lm /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o): undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3' /lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/liblangtag_0.5.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: liblangtag Source-Version: 0.5.1-2 We believe that the bug you reported is fixed in the latest version of liblangtag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard r...@debian.org (supplier of updated liblangtag package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 21:35:29 +0200 Source: liblangtag Binary: liblangtag-dev liblangtag1 liblangtag-gobject0 gir1.2-langtag-0.5 liblangtag-common liblangtag-doc Architecture: source amd64 all Version: 0.5.1-2 Distribution: unstable Urgency: low Maintainer: Rene Engelhard r...@debian.org Changed-By: Rene Engelhard r...@debian.org Description: gir1.2-langtag-0.5 - library to access tags for identifying languages - introspection liblangtag-common - library to access tags for identifying languages -- data liblangtag-dev
Bug#713115: marked as done (liborcus: FTBFS: build-dependency not installable: libmdds-dev)
Your message dated Mon, 01 Jul 2013 21:04:30 + with message-id e1utlgw-0003oj...@franck.debian.org and subject line Bug#713115: fixed in liborcus 0.3.0-8 has caused the Debian Bug report #713115, regarding liborcus: FTBFS: build-dependency not installable: libmdds-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: liborcus Version: 0.3.0-7 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install liborcus build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-liborcus-dummy : Depends: libmdds-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/liborcus_0.3.0-7_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: liborcus Source-Version: 0.3.0-8 We believe that the bug you reported is fixed in the latest version of liborcus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard r...@debian.org (supplier of updated liborcus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 22:01:05 +0200 Source: liborcus Binary: liborcus-dev liborcus-0.4-0 Architecture: source amd64 Version: 0.3.0-8 Distribution: unstable Urgency: low Maintainer: Rene Engelhard r...@debian.org Changed-By: Rene Engelhard r...@debian.org Description: liborcus-0.4-0 - library for processing spreadsheet documents liborcus-dev - library for processing spreadsheet documents -- development Closes: 713115 Changes: liborcus (0.3.0-8) unstable; urgency=low . * use libboost-system1.53-dev explicitly as libmdds-dev does, too - and otherwise we have conflicting build-deps (closes: #713115) Checksums-Sha1: 586a6f669d827b2c9813cc240bf8120d091c443b 1828 liborcus_0.3.0-8.dsc 6e4bfce029bef642499b37660a2062c4c219c882 3788 liborcus_0.3.0-8.debian.tar.gz b1789805d342a59c539f3ea236b58b0337643f1f 384344 liborcus-dev_0.3.0-8_amd64.deb 48c30c0b135b1160779e2e6220c8e661c378a68f 213314 liborcus-0.4-0_0.3.0-8_amd64.deb Checksums-Sha256: 96e7fb591a16e558c940f33b52bf11fd52e6dd3504f281e1442096e4310f4d29 1828 liborcus_0.3.0-8.dsc b73ce0cba0587b715b1c1628b465e41ef5bf16bc81c5ba2f456f4b86813dd26b 3788 liborcus_0.3.0-8.debian.tar.gz 355b6f7f3c570a52f69ce1ec33aea860c25576dcf941dee263a76efb55e4fc95 384344 liborcus-dev_0.3.0-8_amd64.deb edf321a766390272a1f43a1878652f7fce4cca6691769fd23d78d593b2bb0796 213314 liborcus-0.4-0_0.3.0-8_amd64.deb Files: dac0960b1dca64027d0a05812c67012a 1828 libs optional liborcus_0.3.0-8.dsc a17cd9f48d035918324154d9e52e0baf 3788 libs optional liborcus_0.3.0-8.debian.tar.gz 7884920db241a7818d064b4a57818211 384344 libdevel optional liborcus-dev_0.3.0-8_amd64.deb
Bug#713115: marked as done (liborcus: FTBFS: build-dependency not installable: libmdds-dev)
Your message dated Mon, 01 Jul 2013 21:04:38 + with message-id e1utlh4-0003vy...@franck.debian.org and subject line Bug#713115: fixed in liborcus 0.5.1-3 has caused the Debian Bug report #713115, regarding liborcus: FTBFS: build-dependency not installable: libmdds-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: liborcus Version: 0.3.0-7 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install liborcus build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-liborcus-dummy : Depends: libmdds-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/liborcus_0.3.0-7_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: liborcus Source-Version: 0.5.1-3 We believe that the bug you reported is fixed in the latest version of liborcus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard r...@debian.org (supplier of updated liborcus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Jul 2013 22:14:48 +0200 Source: liborcus Binary: liborcus-dev liborcus-0.6-0 Architecture: source amd64 Version: 0.5.1-3 Distribution: experimental Urgency: low Maintainer: Rene Engelhard r...@debian.org Changed-By: Rene Engelhard r...@debian.org Description: liborcus-0.6-0 - library for processing spreadsheet documents liborcus-dev - library for processing spreadsheet documents -- development Closes: 713115 Changes: liborcus (0.5.1-3) experimental; urgency=low . * merge liborcus 0.3.0-8: + use libboost-system1.53-dev explicitly as libmdds-dev does, too - and otherwise we have conflicting build-deps (closes: #713115) * merge from 0.5.1-2ubuntu1: + hotfix for autotools boost brokeness Checksums-Sha1: 68a7512c025824fe204fa4f2a35143c1a4f66aa4 1828 liborcus_0.5.1-3.dsc 24ccd5baffa5ff479ee548fb65f52d46439046d0 3979 liborcus_0.5.1-3.debian.tar.gz 5cca75818803cd7890b71b7b3540ebde6bf648af 445362 liborcus-dev_0.5.1-3_amd64.deb 76dd577cf7389a5c24e8b75ca2126d5d9af87fe9 315196 liborcus-0.6-0_0.5.1-3_amd64.deb Checksums-Sha256: 0240406a36b25c355c888fcdaa2c37dc7f01f74290821e19664212657bd8587a 1828 liborcus_0.5.1-3.dsc d490099136f020f17a53f007e8b7ff389c64648b2648502ee38dce785f4321c7 3979 liborcus_0.5.1-3.debian.tar.gz 33e54c72fa3402b69b07d5efe721dabb99f050113843c00ff4a3129d67af2fe3 445362 liborcus-dev_0.5.1-3_amd64.deb 124e53028b8b11318ecab7dca8515068311faa5bf1550f021f29536c2268bd0d 315196 liborcus-0.6-0_0.5.1-3_amd64.deb Files: 8c14f52d8a6fc111f1cd061cd36cb219 1828 libs optional liborcus_0.5.1-3.dsc 159875a31175fe651c85feb0a1bbcf4b 3979 libs optional
Bug#713339: marked as done (nted: FTBFS: automake: warning: autoconf input should be named 'configure.ac', not 'configure.in')
Your message dated Mon, 01 Jul 2013 21:07:22 + with message-id e1utlji-00043a...@franck.debian.org and subject line Bug#713339: fixed in nted 1.10.18-5 has caused the Debian Bug report #713339, regarding nted: FTBFS: automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: nted Version: 1.10.18-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' autoreconf aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' automake: warnings are treated as errors configure.in:35: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged. configure.in:35: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead, configure.in:35: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files. automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' /usr/share/automake-1.13/am/library.am: warning: 'libchords.a': linking libraries using a non-POSIX /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in 'configure.in' chords/Makefile.am:24: while processing library 'libchords.a' /usr/share/automake-1.13/am/library.am: warning: 'libcommands.a': linking libraries using a non-POSIX /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in 'configure.in' commands/Makefile.am:24: while processing library 'libcommands.a' /usr/share/automake-1.13/am/library.am: warning: 'libdialogs.a': linking libraries using a non-POSIX /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in 'configure.in' dialogs/Makefile.am:24: while processing library 'libdialogs.a' /usr/share/automake-1.13/am/library.am: warning: 'libidiotseditor.a': linking libraries using a non-POSIX /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in 'configure.in' idiotseditor/Makefile.am:24: while processing library 'libidiotseditor.a' autoreconf: automake failed with exit status: 1 make[1]: *** [override_dh_auto_configure] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/nted_1.10.18-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: nted Source-Version: 1.10.18-5 We believe that the bug you reported is fixed in the latest version of nted, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gilles Filippini p...@debian.org (supplier of updated nted package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 Jul 2013 21:48:59 +0200 Source: nted Binary: nted nted-doc Architecture: source i386 all Version: 1.10.18-5 Distribution: unstable Urgency: low Maintainer: Gilles Filippini p...@debian.org Changed-By: Gilles Filippini p...@debian.org Description: nted - Musical score editor nted-doc - NtEd documentation Closes: 697531 697611 713339 Changes: nted (1.10.18-5) unstable; urgency=low . * Revert part of patch warnings which broke PDF and PS export (closes: #697531). Thanks to Ingo Hadan and Jan Rathmann. * Force absolute path for fileref in docbook files (closes: #697611). The default relative path is correct (../docimages/) but yelp doesn't
