Bug#706877: insserv: breaks dist-upgrade by installing before packages fix their init scripts
[Jamin Collins] Examples of this are: fetchmail and munin-node. The munin-node init script bug report is #680223. However, the updated package wasn't installed until after insserv. While I haven't found a bug report for the fetchmail issue, I did notice an updated init script being installed by it. Do you have any idea how to solve it for everyone? Would it help if insserv list a conflict or break on the problematic package versions to make sure they are upgraded first? Which package version should be listed like that? -- 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#724728: openjade: FTBFS: Undefined subroutine main::Getopts called at ../msggen.pl line 22.
Source: openjade Version: 1.4devel1-20.1 Severity: serious From my pbuilder build log: ... Making all in style make[3]: Entering directory `/tmp/buildd/openjade-1.4devel1/style' [ ! -f ../msggen.pl ] || /usr/bin/perl -w ../msggen.pl -l jstyleModule InterpreterMessages.msg Undefined subroutine main::Getopts called at ../msggen.pl line 22. make[3]: *** [InterpreterMessages.h] Error 2 make[3]: Leaving directory `/tmp/buildd/openjade-1.4devel1/style' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/openjade-1.4devel1' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/openjade-1.4devel1' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724730: openjade1.3: FTBFS: Undefined subroutine main::Getopts called at ./../msggen.pl line 22.
Source: openjade1.3 Version: 1.3.2-11.1 Severity: serious From my pbuilder build log: ... g++ -g -pipe -fpermissive -O2 -I. -I./../include -I/usr/include/OpenSP -I/usr/include/OpenSP/.. -I./../grove -I./../spgrove -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\openjade\ -DVERSION=\1.3.2\ -DSP_DEFINE_TEMPLATES=1 -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_LIMITS_H=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1 -DHAVE_ST_BLKSIZE=1 -DSIZEOF_SIZE_T=8 -DSIZEOF_UNSIGNED_INT=4 -DSP_HAVE_LOCALE=1 -DSP_HAVE_WCHAR=1 -DSP_HAVE_GETTEXT=1 -DSP_HAVE_BOOL=1 -DSP_ANSI_CLASS_INST=1 -DSP_HAVE_SOCKET=1 -DJADE_MIF=1 -DJADE_HTML=1 -DSP_MULTI_BYTE=1 -DHAVE_DLFCN_H=1 -DDEFAULT_SCHEME_BUILTINS=\/usr/share/sgml/openjade1.3/builtins.dsl\ -c Collector.cxx echo timestamp Collector.lo /usr/bin/perl -w ./../msggen.pl -l jstyleModule DssslAppMessages.msg Undefined subroutine main::Getopts called at ./../msggen.pl line 22. make[3]: *** [DssslAppMessages.h] Error 2 make[3]: Leaving directory `/tmp/buildd/openjade1.3-1.3.2/style' make[2]: *** [style] Error 2 make[2]: Leaving directory `/tmp/buildd/openjade1.3-1.3.2' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/openjade1.3-1.3.2' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: [gdm3] gdm does not start properly, cannot login via gdm
Package: gdm3 Version: 3.8.4-1 Severity: grave Hi, I updated to 3.8 today, and after restarting the gdm3, I cannot login anymore. Gdm3 somehow starts (graphics are visible) but the login field is missing. :0-slave.log says: -- ** (gdm-simple-slave:19770): WARNING **: Couldn't connect to system bus: Verbindung ist gescheitert:Datei oder Verzeichnis nicht gefunden (gdm-simple-slave:19770): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed :0-greeter.log has bazillions of lines like: (gnome-settings-daemon:19268): dconf-CRITICAL **: unable to create directory '/run/user/1000/dconf': Keine Berechtigung. dconf will not work properly. Switching to terminal and starting via startx works properly. This might be related to #681282. Thanks for packaging Gnome3, I'm sure keeping track of all the transitions is a hell of a job! Cheers, Bastian --- System information. --- Architecture: amd64 Kernel: Linux 3.10-3-amd64 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 stable repository.spotify.com 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+- libaccountsservice0(= 0.6.8) | 0.6.34-2 libatk1.0-0 (= 1.12.4) | 2.10.0-2 libaudit1(= 1:2.2.1) | 1:2.3.2-2 libc6 (= 2.14) | 2.17-93 libcairo-gobject2 (= 1.10.0) | 1.12.16-2 libcairo2 (= 1.2.4) | 1.12.16-2 libcanberra-gtk3-0 (= 0.25) | 0.30-2 libcanberra0 (= 0.2) | 0.30-2 libgdk-pixbuf2.0-0(= 2.22.0) | 2.28.2-1 libgdm1 (= 3.8.4-1) | 3.8.4-1 libglib2.0-0 (= 2.35.0) | 2.36.4-1 libgtk-3-0 (= 3.0.0) | 3.8.4-1 libpam0g(= 0.99.7.1) | 1.1.3-9 libpango-1.0-0(= 1.14.0) | 1.32.5-5+b1 libpangocairo-1.0-0 (= 1.14.0) | 1.32.5-5+b1 libselinux1 (= 1.32) | 2.1.13-2 libwrap0 (= 7.6-4~) | 7.6.q-24 libx11-6 | 2:1.6.1-1 libxau6 | 1:1.0.8-1 libxdmcp6 | 1:1.1.1-1 libxrandr2(= 2:1.2.99.3) | 2:1.4.1-1 dconf-gsettings-backend (= 0.12.1-2) | 0.16.1-1 debconf (= 0.5) | 1.5.51 OR debconf-2.0 | gir1.2-gdm3 (= 3.8.4-1) | 3.8.4-1 adduser | 3.113+nmu3 libpam-modules(= 0.72-1) | 1.1.3-9 libpam-runtime (= 0.76-13.1) | 1.1.3-9 gnome-session-bin(= 3.6) | 3.8.2.1-1 gnome-settings-daemon(= 3.2) | 3.8.5-1 gnome-shell | 3.8.4-1 policykit-1-gnome | 0.105-2 upower| 0.9.21-3 gnome-session | 3.8.2.1-1 OR x-session-manager | OR x-window-manager | OR x-terminal-emulator | lsb-base (= 3.2-14) | 4.1+Debian12 librsvg2-common | 2.36.4-2 accountsservice (= 0.6.12) | 0.6.34-2 gsettings-desktop-schemas | 3.8.0-1 libglib2.0-bin(= 2.35.0) | 2.36.4-1 dconf-cli (= 0.12.1-2) | 0.16.1-1 x11-common (= 1:7.6+11) | 1:7.7+3 x11-xserver-utils | 7.7+1 Recommends (Version) | Installed -+-=== zenity | 3.8.0-1 xserver-xephyr | 2:1.14.3-3 x11-xkb-utils| 7.7~1 xserver-xorg | 1:7.7+3 at-spi2-core | 2.10.0-1 gnome-icon-theme | 3.8.3-1 gnome-icon-theme-symbolic| 3.8.2.2-2 desktop-base (= 6) | Suggests (Version) | Installed ===-+-=== libpam-gnome-keyring| 3.8.2-2 gnome-orca | -- Bastian Venthur http://venthur.de Debian Developer venthur at 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#724070: python-docutils: FTBFS: Test failure in test_raw_url
severity 724070 normal tags 724070 - unreproducible retitle 724070 python-docutils: FTBFS: test_raw_url fails in case of NXDOMAIN DNS hijacking thanks Hey, On Wed, Sep 25, 2013 at 09:09:51AM -0700, Daniel Schepler wrote: It turns out my setting of preferences to opt out of broken redirection of nonexistent host names to a web search (HTTP only) had expired again. When I re-disabled it to fix DNS to properly return host not found errors, the build failure went away. So, feel free to downgrade the severity of this bug. Ugh, this nonsense. Thank you for the analysis; perhaps use of a .invalid domain will solve the issue. Cheers, Michael -- 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#724070: python-docutils: FTBFS: Test failure in test_raw_url
Processing commands for cont...@bugs.debian.org: severity 724070 normal Bug #724070 [src:python-docutils] python-docutils: FTBFS: Test failure in test_raw_url Severity set to 'normal' from 'serious' tags 724070 - unreproducible Bug #724070 [src:python-docutils] python-docutils: FTBFS: Test failure in test_raw_url Removed tag(s) unreproducible. retitle 724070 python-docutils: FTBFS: test_raw_url fails in case of NXDOMAIN DNS hijacking Bug #724070 [src:python-docutils] python-docutils: FTBFS: Test failure in test_raw_url Changed Bug title to 'python-docutils: FTBFS: test_raw_url fails in case of NXDOMAIN DNS hijacking' from 'python-docutils: FTBFS: Test failure in test_raw_url' thanks Stopping processing here. Please contact me if you need assistance. -- 724070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724070 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#720646: salome-kernel: FTBFS against boost 1.54 6 - potential Fix
Hi,
I tried to fix FTBS with boost 1.54 for the latest version 7.2.0
Applying the following patch seems to work... at least it compiles now.
It should be also working for 6.5.0
Best
C
--
Christophe TROPHIME
Research Engineer
LNCMI
CNRS - LNCMI
25, rue des Martyrs
BP 166
38042 GRENOBLE Cedex 9
FRANCE
CNRS
Tel : +33 (0)4 76 88 90 02
Fax : +33 (0) 4 76 88 10 01
Office U 19
M@il : christophe.troph...@lncmi.cnrs.fr
Index: salome-kernel/src/DF/DF_definitions.hxx
===
--- salome-kernel.orig/src/DF/DF_definitions.hxx 2013-09-26 19:41:24.0 +0200
+++ salome-kernel/src/DF/DF_definitions.hxx 2013-09-27 08:53:24.0 +0200
@@ -46,9 +46,10 @@
}
templateclass Y
-df_shared_ptr(df_shared_ptrY const r):
- boost::shared_ptrT(r,boost::detail::dynamic_cast_tag())
-{}
+df_shared_ptr(df_shared_ptrY const r)
+ {
+boost::dynamic_pointer_castT(r);
+ }
templateclass Y
df_shared_ptr operator=(df_shared_ptrY const r)
Index: salome-kernel/src/SALOMEDSClient/SALOMEDSClient_definitions.hxx
===
--- salome-kernel.orig/src/SALOMEDSClient/SALOMEDSClient_definitions.hxx 2013-09-26 19:41:24.0 +0200
+++ salome-kernel/src/SALOMEDSClient/SALOMEDSClient_definitions.hxx 2013-09-27 08:52:14.0 +0200
@@ -47,9 +47,10 @@
}
templateclass Y
-clt_shared_ptr(clt_shared_ptrY const r):
- boost::shared_ptrT(r,boost::detail::dynamic_cast_tag())
-{}
+clt_shared_ptr(clt_shared_ptrY const r)
+ {
+boost::dynamic_pointer_castT(r);
+ }
templateclass Y
clt_shared_ptr operator=(clt_shared_ptrY const r)
Bug#724642:
The problem is that exfalso updated to 3.0.2 but the plugins didn't (they aren't in sid) Downgrading quodlibet and exfalso to 2.4 should fix it for now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: Fixed?
The problem disappeared after further upgrading some gnome packages, removing some old cruft from the system and rebooting. Sorry that I can't be any more specific. Cheers, Bastian -- Bastian Venthur http://venthur.de Debian Developer venthur at 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#718588: marked as done (dhelp: transition to apache2.4)
Your message dated Fri, 27 Sep 2013 10:48:30 + with message-id e1vpvb4-0002sz...@franck.debian.org and subject line Bug#718588: fixed in dhelp 0.6.21+nmu3 has caused the Debian Bug report #718588, regarding dhelp: transition to apache2.4 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.) -- 718588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dhelp Version: 0.6.21+nmu2 Severity: serious Apache has been upgraded from version 2.2 to version 2.4, with the consequence that the /etc/apache2/conf.d directory is no longer supported. Please upgrade the package to support the new version! There is guidance available in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669837 for the phppgadmin package; dhelp will presumably be similar. If I were capable of providing a dhelp specific patch at the current time, I would, but I'm only just looking at the transition myself. Julian ---End Message--- ---BeginMessage--- Source: dhelp Source-Version: 0.6.21+nmu3 We believe that the bug you reported is fixed in the latest version of dhelp, 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 718...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey j...@debian.org (supplier of updated dhelp 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: Sun, 22 Sep 2013 11:07:22 +0100 Source: dhelp Binary: dhelp Architecture: source all Version: 0.6.21+nmu3 Distribution: unstable Urgency: low Maintainer: Georgios M. Zarkadas g...@member.fsf.org Changed-By: Julian Gilbey j...@debian.org Description: dhelp - online help system Closes: 718588 Changes: dhelp (0.6.21+nmu3) unstable; urgency=low . * Non-maintainer upload. * Fix apache2 2.4 issues: install different config files into /etc/apache2/conf.d and /etc/apache2/conf-available (for versions 2.2 and 2.4 respectively), and call apache2-maintscript-helper with correct parameters (Closes: #718588) Checksums-Sha1: 0cb2f9cfdefc6d494a002277915478127baf0bb2 900 dhelp_0.6.21+nmu3.dsc cf20cad43e214e4c06ece42e4a6648b287538754 77886 dhelp_0.6.21+nmu3.tar.gz fa43da7809ebf362b111c9bffefe1028f7c2b873 71444 dhelp_0.6.21+nmu3_all.deb Checksums-Sha256: 6c11073095c80fb9d68221377ba0a802aa02f8f58fd8320f7e95a79994ef7d51 900 dhelp_0.6.21+nmu3.dsc 6a3174366284fa94d19ea4dfd6dc3b4f8673a94ed47787192489b6f6f7cc61fb 77886 dhelp_0.6.21+nmu3.tar.gz cd5b4494461fd9fa0b15fb5d1166203274f7bd5d03d457e0f9ebc66d248d3e5e 71444 dhelp_0.6.21+nmu3_all.deb Files: 194d44fc2816b0abcb8edef08161b883 900 doc optional dhelp_0.6.21+nmu3.dsc b1ef9bf85b1a6b91ab33ebc1e67bc770 77886 doc optional dhelp_0.6.21+nmu3.tar.gz 4f0f28ee23d8d6af6c18a8ec85e57d04 71444 doc optional dhelp_0.6.21+nmu3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlI+xQ4ACgkQDU59w/205FleEwCgt6do7b9T3TxM/6QFaMaYDSrl LOgAn2DC8grFVvwVQkZ9vzS7gmjuowk2 =SSfw -END PGP SIGNATUREEnd Message---
Bug#694308: any update on adobe copyright in fonts in debian ?
Hi all, Looking forward to updaes. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724740: chicken: CVE-2013-4385
Package: chicken Severity: grave Tags: security Justification: user security hole This was assigned CVE-2013-4385: http://code.call-cc.org/cgi-bin/gitweb.cgi?p=chicken-core.git;a=commit;h=cd1b9775005ebe220ba11265dbf5396142e65f26 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#711236: epoch-lowering seems doable
Releasing ruby-rack 1:1.4.5 or newer seems doable if ruby-actionpack-4.0 and ruby-bcat dependencies are tightened to take the epoch into account. ...based on reverse dependencies, inspected on sid/amd64 as of today. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: severity of 724713 is serious
Processing commands for cont...@bugs.debian.org: # uninstallability is a serious issue severity 724713 serious Bug #724713 [jython] jython: Can not install Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 724713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724713 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#724744: 'apt-get source' does not stop if signatures can't be checked
Package: apt Version: 0.9.7.9 Severity: grave Tags: security Source packages are signed, therefore it's fair to expect 'apt-get source' to enforce signature verification. But it merely prints a warning and continues if it can't check a signature because of a missing key (e.g. when you forgot to install the developer keyring). This seems to be caused by dpkg-source needing the --require-valid-signature option to enable strict checking (*). Freenode's #debian suggested I should file a bug on 'apt' since it's the frontend, and set a 'wishlist' severity. However I decided to give it a 'grave' severity because Debian policy says that's appropriate when a package introduces a command that exposes the user accounts to attacks when ran ( http://release.debian.org/stable/rc_policy.txt ). I'm hoping this gets treated more seriously than 'wishlist' (**). The security hole in this case involves introducing a compromised source package on a Debian mirror. Then apt will happily take it, unpack it, patch stuff and possibly execute arbitrary code from it, without quitting if it can't check signatures. It breaks the reasonable assumption that the package manager will check source package signatures for official packages just as it checks binary packages. (*) I'd also argue --require-valid-signature is an incredibly poor default in itself, and that's what should be fixed. It essentially makes security a long option to a core Debian command and it's off by default. (**) I should remind you my somewhat related #722906 issue on downloads being exceedingly difficult to check correctly from non-Debian machines also got a 'wishlist' status (initially 'important' and not tagged as a security issue) and had its subject change to something more benign. I'm hoping my report was misunderstood. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717331: marked as done (gst-plugins-bad1.0: FTBFS on i386, kfreebsd-i386 and powerpc)
Your message dated Fri, 27 Sep 2013 14:00:12 +0200 with message-id 1380283212.2465.5.ca...@thor.lan and subject line Re: Bug#717331: gst-plugins-bad1.0: FTBFS on i386, kfreebsd-i386 and powerpc has caused the Debian Bug report #717331, regarding gst-plugins-bad1.0: FTBFS on i386, kfreebsd-i386 and powerpc 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.) -- 717331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gst-plugins-bad1.0 Version: 1.0.8-1 Severity: serious Tags: patch Hi, gst-plugins-bad1.0 FTBFS on i386, kfreebsd-i386 and powerpc like this: ... libtool: link: mv -f .libs/libgstmodplug.expT .libs/libgstmodplug.exp libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/powerpc-linux-gnu/4.6/../../../powerpc-linux-gnu/crti.o /usr/lib/gcc/powerpc-linux-gnu/4.6/crtbeginS.o .libs/libgstmodplug_la-gstmodplug.o -Wl,--as-needed -lgstreamer-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lmodplug -L/usr/lib/gcc/powerpc-linux-gnu/4.6 -L/usr/lib/gcc/powerpc-linux-gnu/4.6/../../../powerpc-linux-gnu -L/usr/lib/gcc/powerpc-linux-gnu/4.6/../../../../lib -L/lib/powerpc-linux-gnu -L/lib/../lib -L/usr/lib/powerpc-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/powerpc-linux-gnu/4.6/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/powerpc-linux-gnu/4.6/crtendS.o /usr/lib/gcc/powerpc-linux-gnu/4.6/../../../powerpc-linux-gnu/crtn.o -pthread -pthread -O2 -Wl,-z -Wl,relro -Wl,-z -Wl,defs -Wl,-O1 -pthread -pthread -Wl,-soname -Wl,libgstmodplug.so -Wl,-retain-symbols-file -Wl,.libs/libgstmodplug.exp -o .libs/libgstmodplug.so /usr/lib/powerpc-linux-gnu/libc_nonshared.a(stack_chk_fail_local.oS): In function `__stack_chk_fail_local': (.text+0x20): undefined reference to `__stack_chk_fail' collect2: ld returned 1 exit status make[4]: *** [libgstmodplug.la] Error 1 make[4]: Leaving directory `/«PKGBUILDDIR»/ext/modplug' make[3]: *** [modplug] Error 2 make[3]: Leaving directory `/«PKGBUILDDIR»/ext' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: *** [all] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»' ... This can be fixed by removing -Wl,--as-needed from debian/rules. Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 1.2.0-1 On Mo, 2013-08-26 at 09:05 +0200, Sebastian Dröge wrote: On Fr, 2013-07-19 at 15:34 +0200, Roland Stigge wrote: Source: gst-plugins-bad1.0 Version: 1.0.8-1 Severity: serious Tags: patch Hi, gst-plugins-bad1.0 FTBFS on i386, kfreebsd-i386 and powerpc like this: ... libtool: link: mv -f .libs/libgstmodplug.expT .libs/libgstmodplug.exp libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/powerpc-linux-gnu/4.6/../../../powerpc-linux-gnu/crti.o /usr/lib/gcc/powerpc-linux-gnu/4.6/crtbeginS.o .libs/libgstmodplug_la-gstmodplug.o -Wl,--as-needed -lgstreamer-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lmodplug -L/usr/lib/gcc/powerpc-linux-gnu/4.6 -L/usr/lib/gcc/powerpc-linux-gnu/4.6/../../../powerpc-linux-gnu -L/usr/lib/gcc/powerpc-linux-gnu/4.6/../../../../lib -L/lib/powerpc-linux-gnu -L/lib/../lib -L/usr/lib/powerpc-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/powerpc-linux-gnu/4.6/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/powerpc-linux-gnu/4.6/crtendS.o /usr/lib/gcc/powerpc-linux-gnu/4.6/../../../powerpc-linux-gnu/crtn.o -pthread -pthread -O2 -Wl,-z -Wl,relro -Wl,-z -Wl,defs -Wl,-O1 -pthread -pthread -Wl,-soname -Wl,libgstmodplug.so -Wl,-retain-symbols-file -Wl,.libs/libgstmodplug.exp -o .libs/libgstmodplug.so /usr/lib/powerpc-linux-gnu/libc_nonshared.a(stack_chk_fail_local.oS): In function `__stack_chk_fail_local': (.text+0x20): undefined reference to `__stack_chk_fail' collect2: ld returned 1 exit status I think this is a bug in the toolchain. The compiler did not make sure that all libraries required for the symbols that itself added are linked in. Also fixed since some time, or worked around. Toolchain people claimed it's not a bug on their side... whatever. signature.asc Description: This is a digitally signed message part ---End Message---
Processed: severity of 723179 is grave
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 723179 grave Bug #723179 [proftpd-dfsg] proftpd-dfsg: CVE-2013-4359 Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 723179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723179 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#724744: 'apt-get source' does not stop if signatures can't be checked
Control: severity -1 wishlist On Fri, Sep 27, 2013 at 2:05 PM, Eduard - Gabriel Munteanu edg...@gmail.com wrote: Source packages are signed, therefore it's fair to expect 'apt-get source' to enforce signature verification. But it merely prints a warning and continues if it can't check a signature because of a missing key (e.g. when you forgot to install the developer keyring). This seems to be caused by dpkg-source needing the --require-valid-signature option to enable strict checking (*). APT doesn't need to validate the signature of the source package to ensure it is indeed the source package the maintainer uploaded. The signature is used by dak (and other repository creators) to ensure what they get is coming indeed from someone they trust. Only if that is the case it is integrated into the archive. In the archive the files are indexed with their checksums in the Sources file, which is itself indexed in the (In)Release file which is (clear)signed by the maintainers of the repository: A key APT has available (which changes a lot less than the keys of people allowed to upload source packages as DDs get accepted and retire all the time and not to forget DMs … – also, those people can retire and therefore be removed from the keyrings, but their uploaded packages aren't magically invalid now). So given that we know the signature of the Release file is correct, we know that the checksums for Sources is correct and hence we can use the checksums included in that file to verify the integrity of files we download. No need to require all users to download multiple multi-MB big keyrings they have to constantly keep up-to-date just for such a basic operation. (I have the strong feeling that this is a duplicate, but I have no time now to check, just wanted to remove the RC-bug indicator so nobody is scared.) Best regards David Kalnischkies On Fri, Sep 27, 2013 at 2:05 PM, Eduard - Gabriel Munteanu edg...@gmail.com wrote: Package: apt Version: 0.9.7.9 Severity: grave Tags: security Source packages are signed, therefore it's fair to expect 'apt-get source' to enforce signature verification. But it merely prints a warning and continues if it can't check a signature because of a missing key (e.g. when you forgot to install the developer keyring). This seems to be caused by dpkg-source needing the --require-valid-signature option to enable strict checking (*). Freenode's #debian suggested I should file a bug on 'apt' since it's the frontend, and set a 'wishlist' severity. However I decided to give it a 'grave' severity because Debian policy says that's appropriate when a package introduces a command that exposes the user accounts to attacks when ran ( http://release.debian.org/stable/rc_policy.txt ). I'm hoping this gets treated more seriously than 'wishlist' (**). The security hole in this case involves introducing a compromised source package on a Debian mirror. Then apt will happily take it, unpack it, patch stuff and possibly execute arbitrary code from it, without quitting if it can't check signatures. It breaks the reasonable assumption that the package manager will check source package signatures for official packages just as it checks binary packages. (*) I'd also argue --require-valid-signature is an incredibly poor default in itself, and that's what should be fixed. It essentially makes security a long option to a core Debian command and it's off by default. (**) I should remind you my somewhat related #722906 issue on downloads being exceedingly difficult to check correctly from non-Debian machines also got a 'wishlist' status (initially 'important' and not tagged as a security issue) and had its subject change to something more benign. I'm hoping my report was misunderstood. -- To UNSUBSCRIBE, email to deity-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130927120511.GA3406@home -- 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#724744: 'apt-get source' does not stop if signatures can't be checked
Processing control commands: severity -1 wishlist Bug #724744 [apt] 'apt-get source' does not stop if signatures can't be checked Severity set to 'wishlist' from 'grave' -- 724744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724744 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#724228: pdf2djvu: FTBFS: make[1]: *** No rule to make target `Makefile.common'. Stop.
* David Suárez david.sephi...@gmail.com, 2013-09-22, 21:00: Relevant part (hopefully): fakeroot debian/rules clean dh clean --with autotools_dev --parallel dh_testdir -O--parallel dh_auto_clean -O--parallel make[1]: Entering directory `/«PKGBUILDDIR»' Makefile:8: Makefile.common: No such file or directory make[1]: *** No rule to make target `Makefile.common'. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 My understanding that this is because an unusual bit of upstream build system: Makefile always exists, but it doesn't work until the package is configured. Apparently dh_auto_* no longer likes such setup... Adding something like to debian/rules should fix the bug: override_dh_auto_clean: ! [ -f config.status ] || dh_auto_clean -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724746: tntnet: Default configuration exports whole filesystem via HTTP
Package: tntnet Version: 2.1-2 Severity: grave Dear Maintainer, the default configuration of the tntnet package contains this line: MapUrl ^/(.*)$ static@tntnet /$1 This causes the whole filesystem to be exported via HTTP, thus allowing all files readable by the user www-data on the whole system to be downloaded via HTTP. For example a GET request to http://hostname/etc/passwd will return the /etc/passwd file. The line should be changed like this: MapUrl ^/(.*)$ static@tntnet /var/www/$1 -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (1051, 'stable'), (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.4.60 (SMP w/16 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724228: pdf2djvu: FTBFS: make[1]: *** No rule to make target `Makefile.common'. Stop.
Thanks much for bug report and hint! Greetings, Daniel Stender On 27.09.2013 14:55, Jakub Wilk wrote: * David Suárez david.sephi...@gmail.com, 2013-09-22, 21:00: Relevant part (hopefully): fakeroot debian/rules clean dh clean --with autotools_dev --parallel dh_testdir -O--parallel dh_auto_clean -O--parallel make[1]: Entering directory `/«PKGBUILDDIR»' Makefile:8: Makefile.common: No such file or directory make[1]: *** No rule to make target `Makefile.common'. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 My understanding that this is because an unusual bit of upstream build system: Makefile always exists, but it doesn't work until the package is configured. Apparently dh_auto_* no longer likes such setup... Adding something like to debian/rules should fix the bug: override_dh_auto_clean: ! [ -f config.status ] || dh_auto_clean -- http://www.danielstender.com/blog/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724600: [Pkg-ime-devel] Bug#724600: ibus-table-latex: Can't switch to latex input method
Hi, FYI: ibus in testing had gone through 1.4 - 1.5 library transition. At the same time python binding method and its dependency situation has changed. On Wed, Sep 25, 2013 at 05:53:46PM +0200, frydo wrote: Package: ibus-table-latex Version: 1.3.0.20100528-3 Severity: grave Justification: renders package unusable It's not possible to switch to latex input method in Ibus. I can have the Hangul input method, but not the latex input method. 1.5.0.is.1.5.0.20130419-2 went to testing a bit too early. (Blame me.) Do you have ibus 1.5.3-7 (which is in testing today) Hmmm. This ibus-table-latex was not touched. Maybe I need to add python-ibus dependency to it for new situation. Can you check? If these do not work, I need to check. I guess this comes from a recent update, maybe one of ibus-table. I do not know how to use ibus-table-latex to test. Please let me know minimal case to test. Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 724600 is normal
Processing commands for cont...@bugs.debian.org: severity 724600 normal Bug #724600 [ibus-table-latex] ibus-table-latex: Can't switch to latex input method Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 724600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724600 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#724759: libplayer2: incorrect dependencies: libxine1-x | libxine2-x (hard), libxine2-vdr (suggested)
Package: libplayer2
Version: 2.0.1-2.1
Severity: serious
Tags: patch
libplayer2 depends on libxine1-x | libxine2-x. This is incorrect.
* It will be satisfied if libxine2-x is present, despite the package using
libxine1 and therefore needing libxine1-x.
* It will pull in libxine2 (well, libxine2-bin) anyway...
This is fixable by running dh_xine at build time (“dh --with xine $@” –
default behaviour is sufficient here) and having the package depend on
${xine-x:Depends}. (Advantage: works without change when adapting to
libxine2, covers possible future package name changes.)
Similarly, it suggests libxine2-vdr while depending on libxine1. This is
pointless unless it instead depends on libxine2 and should, therefore, be
removed for now.
--
| _ | Darren Salt, using Debian GNU/Linux (and Android)
| ( ) |
| X | ASCII Ribbon campaign against HTML e-mail
| / \ | http://www.asciiribbon.org/
Aleph sub alpha is the alpha'th aleph.
fix-xine-deps.patch
Description: Binary data
Bug#724768: glark: Does not work with ruby 1.9, but doesn't have according dependencies
Package: glark
Version: 1.8.0-1
Severity: grave
Justification: Wrong/missing dependency, does only work after changing a
system's ruby default version
Tags: wheezy jessie sid patch
Dear Maintainer,
while glark 1.8.0-1 seems to work fine on Debian Squeeze, it no more
does so on Wheezy:
$ glark
/usr/share/glark/glark.rb:135: warning: assigned but unused variable - srclines
/usr/share/glark/glark.rb:262: warning: assigned but unused variable - e
/usr/share/glark/glark.rb:351: warning: assigned but unused variable - e
/usr/share/glark/glark.rb:460: warning: assigned but unused variable - fname
/usr/share/glark/glark.rb:640: warning: assigned but unused variable - e
/usr/share/glark/glark.rb:816: warning: assigned but unused variable - str
/usr/share/glark/options.rb:501: warning: assigned but unused variable - e
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require':
/usr/share/glark/options.rb:81: formal argument cannot be an instance variable
(SyntaxError)
:set = Proc.new { |@after| },
^
/usr/share/glark/options.rb:87: formal argument cannot be an instance variable
:set = Proc.new { |@before| },
^
/usr/share/glark/options.rb:191: formal argument cannot be an instance variable
:set = Proc.new { |@directory| }
^
/usr/share/glark/options.rb:216: formal argument cannot be an instance variable
:set = Proc.new { |@split_as_path| }
^
/usr/share/glark/options.rb:221: formal argument cannot be an instance variable
:set = Proc.new { |@directory| }
^
/usr/share/glark/options.rb:234: formal argument cannot be an instance variable
:set = Proc.new { |@label| }
^
/usr/share/glark/options.rb:239: formal argument cannot be an instance variable
:set = Proc.new { |@match_limit| }
^
/usr/share/glark/options.rb:296: formal argument cannot be an instance variable
:set = Proc.new { |@size_limit| }
^
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/share/glark/glark.rb:20:in `top (required)'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/bin/glark:17:in `main'
$
(Adding parameters or command-line options make no difference at all.)
The default ruby version since Wheezy is 1.9.3. But even with installing
the ruby1.8 package and calling ruby1.8 /usr/bin/glark does not help.
The only thing which helps so far is installing ruby1.8 (but glark's
dependency unconditionally pulls in ruby 1.9.x) and then letting
/usr/bin/ruby point to ruby1.8 by running update-alternatives --config
ruby.
But that's just a short-term solution since ruby1.8 seems scheduled for
removal: http://release.debian.org/transitions/html/ruby1.8-removal.html
IMHO this bug should also be fixed in Wheezy as glark does not work on
Wheezy without changing the default ruby version and that's completely
up to the local administrator and no package must depend on that
decision.
Intermediately, this fix should also work for Jessie and Sid, but only
until Ruby 1.8 is removed.
The following patch fixes the issue:
diff -u glark-1.8.0/debian/control glark-1.8.0/debian/control
--- glark-1.8.0/debian/control
+++ glark-1.8.0/debian/control
@@ -8,7 +8,7 @@
Package: glark
Architecture: all
-Depends: ruby (= 1.6.7-3)
+Depends: ruby1.8
Description: pattern matching tool similar to grep
glark is a program like 'grep' to search for text in files. It can
be used from the command line or in scripts.
diff -u glark-1.8.0/debian/rules glark-1.8.0/debian/rules
--- glark-1.8.0/debian/rules
+++ glark-1.8.0/debian/rules
@@ -4,0 +5,5 @@
+
+install/glark::
+ sed -e 's/^exec ruby /exec ruby1.8 /;s/^#!ruby
/#!ruby1.8/;s:^#!/usr/bin/ruby :#!/usr/bin/ruby1.8 :' -i \
+ $(CURDIR)/debian/glark/usr/bin/glark \
+ $(CURDIR)/debian/glark/usr/share/glark/*.rb
-- 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=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages glark depends on:
ii ruby1:1.9.3
ii ruby1.8 [ruby] 1.8.7.358-7
glark recommends no packages.
glark suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683042: Blender: debian/copyright: No information of embedded external libraries
Hi, I am looking to join the Multimedia team soon. This bug looked like a nice one to start with for a new chum. Give me a few days, and then hopefully I can attach a patch with a fresh copyright file to the bug for review. Regards, Ross -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720796: gstreamer0.10-ffmpeg: FTBFS with libav9: gstffmpeg.h:63:1: error: unknown type name 'URLProtocol'
On So, 2013-09-22 at 14:52 +0200, Sebastian Ramacher wrote: On 2013-09-13 09:16:35, Sebastian Dröge wrote: On Fr, 2013-09-13 at 02:56 +0200, Sebastian Ramacher wrote: On 2013-09-12 14:00:43, Sebastian Dröge wrote: On Do, 2013-09-12 at 12:57 +0200, Sebastian Ramacher wrote: On 2013-09-09 20:53:03, Luk Claes wrote: Can/should this be removed in favour of gst-libav1.0? Yes it should probably be just removed. I plan to get rid of all of gstreamer 0.10 in the next months, so let's just let this one go now already :) testing removal hint added. That didn't work - there are reverse dependencies. Seems like gstreamer0.10-ffmpeg needs to be fixed. The rdepends should be ported to GStreamer 1.0 instead probably. Also most of these rdepends should at most Recommend the package. Sure, ideally they would be ported to use GStreamer 1.0 instead. But I'd rather not add yet another transition on top of the libav transition. I've started to backport the necessary changes for libav 9 from gst-libav1.0. I'm at a state where it compiles and appreciate another pair of eyes looking over it as the patch got really large. From skipping over it this patch looks good, you only remove support for paletted video formats and also some more changes are necessary to convert from the planar audio formats that are output by some decoders now to an interleaved audio format. Here is a new version of the patch. Support for paletted video formats should be back (as far as I can tell from gst-libav1.0's code *_set_palette was removed altogether and is no longer needed). Support for planar audio formats gives me headaches as too much has been changed. I've started to backport it for the encoder but failed to do so for the decoder. Yeah, there's a reason why we did a new version with improved API after many years of experience with annoyances and unneeded complications like that ;) Generally looks good the patch In gst-libav1.0 gst_ffmpegauddec_get_buffer gets a GstAudioInfo pointer from a GstAudioDecoder* instance. Where do I get that from in gstreamer-ffmpeg0.10? Or is there some other way to get the same information? The same questions also bugs me for the encoder. In 0.10 you could create (with later versions of 0.10) a GstAudioInfo from the GstCaps. See gst/audio/audio.h for the relevant functions. Since GstFFmpegDec is not a GstAudioDecoder, what's the proper replacement for gst_audio_decoder_allocate_output_buffer? (as used in gst-libav1.0's gst_ffmpegauddec_get_buffer) Just gst_buffer_new_and_alloc() signature.asc Description: This is a digitally signed message part
Bug#617613: marked as done (freecad: links with both GPL-licensed and GPL-incompatible libraries)
Your message dated Fri, 27 Sep 2013 19:48:46 + with message-id e1vpe1u-0006kl...@franck.debian.org and subject line Bug#617613: fixed in freecad 0.13.2580-dfsg-1 has caused the Debian Bug report #617613, regarding freecad: links with both GPL-licensed and GPL-incompatible libraries 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.) -- 617613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: freecad Version: 0.10.3247.dfsg-2 Severity: serious Justification: Policy 2.2.1 Hello Debian Science Maintainers, thanks for maintaining freecad. This package is mainly released under the terms of the GNU LGPL v2 or later, but includes some files released under the terms of the GNU GPL v2 or later, and, above all, links with libcoin60, which is released under the terms of the GNU GPL v2 (only) [1]. [1] http://packages.debian.org/changelogs/pool/main/c/coin3/coin3_3.1.3-1/libcoin60.copyright On the other hand, freecad links with libopencascade-*-6.3.0, which is released under the terms of the OCTPL v6.3: this license is itself acceptable [2] (from a DFSG point of view), but is GPLv2-incompatible, since it implements a copyleft mechanism and has no explicit GPL-compatibility clause. The GPL-incompatibility is acknowledged in Open CASCADE S.A.S. FAQ [3]: | 1) Is Open CASCADE Technology license GPL-compatible? | | No, it is not. OPEN CASCADE Company uses its own custom license. | However, it follows LGPL license in terms of its purpose and intent. [2] http://lists.debian.org/debian-legal/2007/12/msg00077.html [3] http://www.opencascade.org/occt/faq/ As a consequence, I would say that freecad (the binary package) is currently undistributable, as it links with both a GPLv2-licensed library and a GPLv2-incompatible one. AFAICT, there are three possible ways to fix this issue, in descending order of desirability. (A) Open CASCADE S.A.S. should be contacted and persuaded to re-license Open CASCADE Technology under GPLv2-compatible terms. (B) Open CASCADE Technology should be substituted with a GPLv2-compatible replacement, if any is available. (C) Coin3D copyright holder should contacted and asked to add a license exception to give permission to link Coin3D with code released under the OCTPL; this additional permission should be drafted along the lines of the template [4] suggested by the FSF. A similar exception is needed for GPL-licensed files in FreeCAD itself and should be asked to the corresponding copyright holders. [4] http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs Now, the half-good news. It seems that there's some possibility [5] that Open CASCADE Technology could be re-licensed under the terms of the LGPLv2.1: this would make it GPLv2-compatible (solution (A) above). [5] http://www.opencascade.org/org/forum/thread_15859/ I got in touch with upstream (Open CASCADE S.A.S.) via their web contact form [6] and got a somewhat encouraging reply. [6] http://www.opencascade.org/about/contacts/ This happened on April 2009, though. There has been no progress on the re-licensing of Open CASCADE since then: the management (of Open CASCADE S.A.S.) has not yet taken a decision on the matter. I have been going on contacting them periodically and asking them whether there's any progress, but, apparently, I am not persuasive enough... :-( I reported this on the debian-legal list [7][8]. [7] http://lists.debian.org/debian-legal/2009/10/msg0.html [8] http://lists.debian.org/debian-legal/2010/02/msg7.html Please note that Open CASCADE Technology version 6.5 has been recently released, but v6.5 of the license, despite having a much more accurate preamble, is substantially unchanged in its legally binding text. If nobody else helps me by contacting Open CASCADE S.A.S. and persuading them to re-license Open CASCADE Technology under the LGPLv2.1, I am afraid that the above-mentioned solution (A) will not be a viable option... :-( So, please, pretty please, help me in persuading Open CASCADE S.A.S. to switch to the GNU LGPL v2.1! I recommend involving FreeCAD upstream too in this persuasion effort. The more people get in touch with Open CASCADE S.A.S. and try to persuade them, the better. Thanks for any help you can provide. ---End Message--- ---BeginMessage--- Source: freecad Source-Version: 0.13.2580-dfsg-1 We believe that the bug you reported is fixed in the latest version of freecad, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous
Processed: Re: Bug#724678: RM: flightgear [kfreebsd-*] -- RoM; ANAIS due to missing systemd
Processing control commands: block 724678 by 724686 Bug #724678 [ftp.debian.org] RM: flightgear [kfreebsd-*] -- RoM; ANAIS due to missing systemd 724678 was not blocked by any bugs. 724678 was not blocking any bugs. Added blocking bug(s) of 724678: 724686 -- 724678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724678 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#719396: libcitygml: FTBFS: debian/gencontrol: 6: debian/gencontrol: Illegal number: 0~rc1
The code that fails is
LIBOSG_SHARE=`dpkg --get-selections|awk '{print $1}'|grep
libopenscenegraph[0-9]`
LIBOSG_VERSION=`dpkg -l $LIBOSG_SHARE |grep $LIBOSG_SHARE |sed 's/-/ /'
|awk '{print $3}'`
TMP1=`echo $LIBOSG_VERSION|awk -F '.' '{print $1}'`
TMP2=`echo $LIBOSG_VERSION|awk -F '.' '{print $2}'`
TMP3=`echo $LIBOSG_VERSION|awk -F '.' '{print $3}'`
TMP3=$((TMP3+1))
LIBOSG_VERSIONPLUS=$TMP1.$TMP2.$TMP3
echo $LIBOSG_VERSION
dh_gencontrol -- -Vlibosg-share=$LIBOSG_SHARE
-Vlibosg-static=libopenscenegraph-dev (=$LIBOSG_VERSION),
libopenscenegraph-dev ( $LIBOSG_VERSIONPLUS)
This seems to be trying to create a = relation on the current
libopenscenegraph upstream version and a relation on the next
libopenscenegraph upstream version assuming that libosg upstream
versions follow the pattern x.y.z where x y and z are integers.
However the current libosg upstream version is 3.2.0~rc1 . This means
that the code ends up trying to add 1 to 0~rc1 and fails.
I made two changes to this code in my patch.
1: I added code to strip stuff after the ~ before adding 1
2: I added a ~ to the generated next version. This ensures that if the
next upstream version has release candidates that they are properly
caught by the dependency relationship.
Note that this assumes that release candidates are sufficiently
compatible with the corresponding final versions. If they are not then a
stricter dependency check may be needed.
Debdiff attatched, no intent to NMU.
diff -Nru libcitygml-0.14+svn128/debian/changelog
libcitygml-0.14+svn128/debian/changelog
--- libcitygml-0.14+svn128/debian/changelog 2013-02-01 16:23:03.0
+
+++ libcitygml-0.14+svn128/debian/changelog 2013-09-27 17:13:01.0
+
@@ -1,3 +1,10 @@
+libcitygml (0.14+svn128-1+3p0p1+4+rpi1) jessie-staging; urgency=low
+
+ * Make code in debian/gencontrol handle releasecandidate version of
+openscenegraph correctly. (Closes: #719396)
+
+ -- Peter Michael Green plugw...@raspbian.org Fri, 27 Sep 2013 17:11:40
+
+
libcitygml (0.14+svn128-1+3p0p1+4) unstable; urgency=low
[Sebastian Ramacher]
diff -Nru libcitygml-0.14+svn128/debian/gencontrol
libcitygml-0.14+svn128/debian/gencontrol
--- libcitygml-0.14+svn128/debian/gencontrol2012-06-12 17:21:06.0
+
+++ libcitygml-0.14+svn128/debian/gencontrol2013-09-27 17:11:17.0
+
@@ -3,7 +3,8 @@
TMP1=`echo $LIBOSG_VERSION|awk -F '.' '{print $1}'`
TMP2=`echo $LIBOSG_VERSION|awk -F '.' '{print $2}'`
TMP3=`echo $LIBOSG_VERSION|awk -F '.' '{print $3}'`
+TMP3=`echo $TMP3|awk -F '~' '{print $1}'`
TMP3=$((TMP3+1))
-LIBOSG_VERSIONPLUS=$TMP1.$TMP2.$TMP3
+LIBOSG_VERSIONPLUS=$TMP1.$TMP2.$TMP3~
echo $LIBOSG_VERSION
dh_gencontrol -- -Vlibosg-share=$LIBOSG_SHARE
-Vlibosg-static=libopenscenegraph-dev (=$LIBOSG_VERSION),
libopenscenegraph-dev ( $LIBOSG_VERSIONPLUS)
Bug#713600: marked as done (mysql++: FTBFS: ld: cpool_cpool.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5')
Your message dated Fri, 27 Sep 2013 21:20:34 + with message-id e1vpfsk-0003ms...@franck.debian.org and subject line Bug#713600: fixed in mysql++ 3.2.0+pristine-1 has caused the Debian Bug report #713600, regarding mysql++: FTBFS: ld: cpool_cpool.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' 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.) -- 713600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mysql++ Version: 3.1.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: g++ -o cpool cpool_cpool.o-L. -lmysqlclient_r -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu -lmysqlpp_excommon -lmysqlpp /usr/bin/ld: cpool_cpool.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' /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/mysql++_3.1.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: mysql++ Source-Version: 3.2.0+pristine-1 We believe that the bug you reported is fixed in the latest version of mysql++, 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. Roberto C. Sanchez robe...@connexer.com (supplier of updated mysql++ 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: Thu, 26 Sep 2013 18:49:54 -0400 Source: mysql++ Binary: libmysql++-dev libmysql++3 libmysql++-doc Architecture: source all amd64 Version: 3.2.0+pristine-1 Distribution: unstable Urgency: low Maintainer: Athena Capital Research acr-deb...@athenacr.com Changed-By: Roberto C. Sanchez robe...@connexer.com Description: libmysql++-dev - MySQL C++ library bindings (development) libmysql++-doc - MySQL C++ library bindings (documentation and examples) libmysql++3 - MySQL C++ library bindings (runtime) Closes: 713600 Changes: mysql++ (3.2.0+pristine-1) unstable; urgency=low . * New upstream release + Repack source to remove unnecessary absolute symlink * Add linkage to pthread via LDFLAGS in debian/rules (Closes: #713600) * Drop 03_fix_linker_order.patch - part merged upstream part obsolete * Update to Standards-Version 3.9.4 (no changes) Checksums-Sha1: cc729beab6132f88cf6924c6be475f4b96f51e46 2001 mysql++_3.2.0+pristine-1.dsc cd82b6303ac32b660c10c276add2dbdbabce37d7 2179756 mysql++_3.2.0+pristine.orig.tar.gz 2f0bc7c37ddf76f948866df0dee1e0ce9b1868fc 105850 mysql++_3.2.0+pristine-1.debian.tar.gz 15a09f52ef1b7709ac87cf72d01eba0c81ec3163 742806 libmysql++-doc_3.2.0+pristine-1_all.deb ac237bdfd11caf78b68d355e2ffcd314f2a3c351 255936 libmysql++-dev_3.2.0+pristine-1_amd64.deb c0a6306332234d03e8b71cc39d446bff03533562 157394 libmysql++3_3.2.0+pristine-1_amd64.deb Checksums-Sha256: b5cdf7cb888a8772ca41e511047891a8067658a97d9a599b01bf4d8cc7ea373e 2001 mysql++_3.2.0+pristine-1.dsc 08de48199ed63a380674d1c48ebce8ebaf6d73cc9e7dc92eaa3a834b266726f3 2179756 mysql++_3.2.0+pristine.orig.tar.gz d363f44312b6afe540f3feeb60fb10ed870dfd20782ff263809143d6cb4c8f26 105850 mysql++_3.2.0+pristine-1.debian.tar.gz 69784e9b1049e4838c9e6aeb34eb3c66abc2c221e5eea32f7fff1e4fff755514 742806 libmysql++-doc_3.2.0+pristine-1_all.deb 356d6fc6407fc6115ab328d50c09bdbb76fdd6f1dfd4931ec167c076f876d8f2 255936 libmysql++-dev_3.2.0+pristine-1_amd64.deb
Bug#724112: marked as done (muroar: FTBFS: make[1]: *** No rule to make target `Makefile.conf'. Stop.)
Your message dated Fri, 27 Sep 2013 21:20:23 + with message-id e1vpfsz-0003ie...@franck.debian.org and subject line Bug#724112: fixed in muroar 0.1.12-3 has caused the Debian Bug report #724112, regarding muroar: FTBFS: make[1]: *** No rule to make target `Makefile.conf'. Stop. 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.) -- 724112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: muroar Version: 0.1.12-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean make[1]: Entering directory `/«PKGBUILDDIR»' Makefile:1: Makefile.conf: No such file or directory make[1]: *** No rule to make target `Makefile.conf'. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/muroar_0.1.12-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: muroar Source-Version: 0.1.12-3 We believe that the bug you reported is fixed in the latest version of muroar, 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 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi pmatth...@debian.org (supplier of updated muroar 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: Fri, 27 Sep 2013 22:24:21 +0200 Source: muroar Binary: libmuroar0 libmuroar0-dbg libmuroar-dev Architecture: source amd64 Version: 0.1.12-3 Distribution: unstable Urgency: high Maintainer: Patrick Matthäi pmatth...@debian.org Changed-By: Patrick Matthäi pmatth...@debian.org Description: libmuroar-dev - minimalist RoarAudio client library (development headers) libmuroar0 - minimalist RoarAudio client library libmuroar0-dbg - minimalist RoarAudio client library (debugging symbols) Closes: 724112 Changes: muroar (0.1.12-3) unstable; urgency=high . * Fix dh_auto_clean. Closes: #724112 Checksums-Sha1: cd2fad11d2b585b6c0d96bccd6b251691f849bb6 1845 muroar_0.1.12-3.dsc e68436998714d8044e951c6c2b27bf4e8087cc6c 3644 muroar_0.1.12-3.debian.tar.gz 5a5dc567f9b1ec8c34d3c635207db7329004c62f 15828 libmuroar0_0.1.12-3_amd64.deb 63293e8f9408c5075cbd20ee39e5ebc26e4131e2 22758 libmuroar0-dbg_0.1.12-3_amd64.deb 0810bb019fdc19b9615e5daa2714305b1a9ccf12 16322 libmuroar-dev_0.1.12-3_amd64.deb Checksums-Sha256: fb940f00592c17da0a52c746fcaaff4d55f9fbb04d12ee248bf94806a497a316 1845 muroar_0.1.12-3.dsc a05a5fcbce2c8ba7dbebee56d216cf7c5f362678d54ef254e8fffa02914a1c25 3644 muroar_0.1.12-3.debian.tar.gz 3440a2e8c26cc17eaa36ac345bd1fbcaa04b91d792b94db1e39637f6e0002b17 15828 libmuroar0_0.1.12-3_amd64.deb 816f342b9e47fcf174cb97a32eaab02963dbb8c3336b26cb3aa2484e8f5db402 22758 libmuroar0-dbg_0.1.12-3_amd64.deb 7b2c3a00c78b096904ef4877cc0cc2c49b18cd0e63ad4ce1250b376a648b2493 16322 libmuroar-dev_0.1.12-3_amd64.deb Files: 46a722662931529f837b9d05f1bb7ac7 1845 libs optional muroar_0.1.12-3.dsc 8537aa5c126f471060e6143b8fd82cf8 3644 libs optional muroar_0.1.12-3.debian.tar.gz 96cfd555b9168a76f9c644e4bbbccf01 15828 libs optional libmuroar0_0.1.12-3_amd64.deb 651700cec9b093d8f8db6ef5f5a58a2b 22758 debug extra libmuroar0-dbg_0.1.12-3_amd64.deb aa4a8a37e3d8ddcf67a55e6470577b2c 16322 libdevel optional libmuroar-dev_0.1.12-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJSReyuAAoJEBLZsEqQy9jkf6gP/jy4wBAC5HuBspLAs0EVqtFR
Bug#723959: marked as done (ckport: FTBFS: No rule to make target `Makefile.conf')
Your message dated Fri, 27 Sep 2013 21:19:13 + with message-id e1vpfrr-0002jx...@franck.debian.org and subject line Bug#723959: fixed in ckport 0.1~rc1-4 has caused the Debian Bug report #723959, regarding ckport: FTBFS: No rule to make target `Makefile.conf' 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.) -- 723959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ckport Version: 0.1~rc1-3 Severity: serious From my pbuilder build log: ... fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean make[1]: Entering directory `/tmp/buildd/ckport-0.1~rc1' Makefile:1: Makefile.conf: No such file or directory make[1]: *** No rule to make target `Makefile.conf'. Stop. make[1]: Leaving directory `/tmp/buildd/ckport-0.1~rc1' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: ckport Source-Version: 0.1~rc1-4 We believe that the bug you reported is fixed in the latest version of ckport, 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 723...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi pmatth...@debian.org (supplier of updated ckport 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: Fri, 27 Sep 2013 22:20:24 +0200 Source: ckport Binary: ckport ckport-database Architecture: source all Version: 0.1~rc1-4 Distribution: unstable Urgency: high Maintainer: Patrick Matthäi pmatth...@debian.org Changed-By: Patrick Matthäi pmatth...@debian.org Description: ckport - portability analysis and security checking tool ckport-database - portability analysis and security checking tool (Database files) Closes: 723959 Changes: ckport (0.1~rc1-4) unstable; urgency=high . * Fix dh_auto_clean. Closes: #723959 Checksums-Sha1: a00c97abd64ab7fb520a516a3c1e267cb54d0c3b 1764 ckport_0.1~rc1-4.dsc 5e2ea8a4f07feb8bb3af061395cb36a52873bb0c 2461 ckport_0.1~rc1-4.debian.tar.gz ca674884f0e5ec51a1b98d16aade5a179797b63c 8956 ckport_0.1~rc1-4_all.deb 5b860281165d95cf5c8886ec26a5c4424f9b66da 5772 ckport-database_0.1~rc1-4_all.deb Checksums-Sha256: 79cbb20ea7001f94de0cbb5c2caa54d759b03e52fd1778b5423a039fb4501622 1764 ckport_0.1~rc1-4.dsc 2eb19ca483a4b84f480d653a4d9b6208a504c869c25157c6bdb3192a4c81cc3a 2461 ckport_0.1~rc1-4.debian.tar.gz 8bbb90323e0ae1d101ae2ff530eac11e27ba62124e35143d7011497d3056fc87 8956 ckport_0.1~rc1-4_all.deb a8ec6dbef03db65abac8813c4a7b6de3a417558509a4b669b92248e5f46586b9 5772 ckport-database_0.1~rc1-4_all.deb Files: f81303440331f8394b8917999a645477 1764 devel optional ckport_0.1~rc1-4.dsc 9135568612a2945399570dcc8b1183bb 2461 devel optional ckport_0.1~rc1-4.debian.tar.gz 77bc5031d9e7de604a3e933e2787bd2c 8956 devel optional ckport_0.1~rc1-4_all.deb 1c313abca38b7b4d04bb129983190041 5772 devel optional ckport-database_0.1~rc1-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJSReyuAAoJEBLZsEqQy9jkaeQP/1Dxt+VPmmP2RN1t1YEir+Ei jj5QMBh7L8AahiVCW17oKXeMR3oMGBo+4lCGp5ATjB4h2CNctYV7dBtGAgWlzr47 GHzPJYGwBjzQz/sqidtvrc9S51DXpjDqXN/G8X+nrallxteJiQQNBSLTf566zMkb jmZf+RACIoz81DGh/Ck8JwIqEYhKaF/xueGcgd+OUC0/rpSTWz6oW0pSI3CyblHe iPTJK/urisAcsf3eY2bxIJTUt6X/Kqq1Y/VxJvrAgHS4qJPAMXqhFtxy3z0gkMJd h0dYJVzeDqwTx6vIqkV5QuQPktagQiS4F+VCuOu6vrdEFH0oh4Om2c0hX4VFHU4n e/aGO5WzE8fbEmqdZQ3O6f8Ew8IjGRdewQO6n3Ox5aj4aUiOMc5znfdI/+M/Fvo8 6AtTpfBiZASUGX5TCq3cRBVcifBoLf0HjQBySzpy9YL3uGH4bcAv/nez4nTIMclK thXjr+6rDffOz5zBeIUom4S0EyWfsUAUyavDgKnu605/XO/2YA4D0VdoJYX/6mYb FhbXjawJYX/FMg6PsbCSHRFb2GhBxSbCfWz2qBqtkxIJH9FwXWsWVyGvY16yCDNV pKSGL7Puo6mZF1hBMSvt9vr8vW45vgq6BHSTjzHYw7Y4S2RZzRVZ+JbuY9aUDm1p g0yvFsm8cpJeKai6gpxj =lgB1 -END PGP SIGNATUREEnd Message---
Bug#724217: marked as done (roarplaylistd: FTBFS: make[1]: *** No rule to make target `Makefile.conf'. Stop.)
Your message dated Fri, 27 Sep 2013 21:20:44 + with message-id e1vpfsu-0003ur...@franck.debian.org and subject line Bug#724217: fixed in roarplaylistd 0.1.7-3 has caused the Debian Bug report #724217, regarding roarplaylistd: FTBFS: make[1]: *** No rule to make target `Makefile.conf'. Stop. 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.) -- 724217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: roarplaylistd Version: 0.1.7-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean make[1]: Entering directory `/«PKGBUILDDIR»' Makefile:20: Makefile.conf: No such file or directory make[1]: *** No rule to make target `Makefile.conf'. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/roarplaylistd_0.1.7-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: roarplaylistd Source-Version: 0.1.7-3 We believe that the bug you reported is fixed in the latest version of roarplaylistd, 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 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi pmatth...@debian.org (supplier of updated roarplaylistd 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: Fri, 27 Sep 2013 22:34:59 +0200 Source: roarplaylistd Binary: roarplaylistd roarplaylistd-dev roarplaylistd-dbg roarplaylistd-tools roarplaylistd-codechelper-gst Architecture: source amd64 all Version: 0.1.7-3 Distribution: unstable Urgency: high Maintainer: Patrick Matthäi pmatth...@debian.org Changed-By: Patrick Matthäi pmatth...@debian.org Description: roarplaylistd - RoarAudio PlayList Daemon (RPLD) roarplaylistd-codechelper-gst - roarplaylistd helper script for GStreamer codecs roarplaylistd-dbg - RoarAudio PlayList Daemon (RPLD) (debugging symbols) roarplaylistd-dev - RoarAudio PlayList Daemon (RPLD) (plugin development files) roarplaylistd-tools - Tools to control RoarAudio PlayList Daemon (RPLD) Closes: 724217 Changes: roarplaylistd (0.1.7-3) unstable; urgency=high . * Fix dh_auto_clean. Closes: #724217 * Source /lib/lsb/init-functions in init script. Checksums-Sha1: ea7644ea5fb150d791636e3695af51392a480d9e 2067 roarplaylistd_0.1.7-3.dsc beddb0ded4e64e41c28e52f3c7e71fbd9afdba56 6833 roarplaylistd_0.1.7-3.debian.tar.gz 3f1351124339ac8edcffbe72c65ec1e7540b13ba 62572 roarplaylistd_0.1.7-3_amd64.deb 7f07130ca3d65364a477102961f4dd9f2105d198 10720 roarplaylistd-dev_0.1.7-3_all.deb 6017249e2c08cf8eac501948b7656c27ce1a9473 160524 roarplaylistd-dbg_0.1.7-3_amd64.deb f33a7639aef8b6c92f27dba085238e3d1177796c 15730 roarplaylistd-tools_0.1.7-3_all.deb 43258734c7c0b7e0ca67dd380383aa57dab8bffc 8280 roarplaylistd-codechelper-gst_0.1.7-3_all.deb Checksums-Sha256: da693eeb6b9bfaed76b9d670f33e1ef0a4bee22029570b30e8f4766ae27134f1 2067 roarplaylistd_0.1.7-3.dsc 05a322674f9320527589dfdf0b2f8406166a94a27715f692ec56b30cc5e5e0d3 6833 roarplaylistd_0.1.7-3.debian.tar.gz 32e0ea3d8eeac75a9c6ae148fc3bb44a93e37ee41929079bac1d1abadd185957 62572 roarplaylistd_0.1.7-3_amd64.deb 14491f89f9947c32f446dbd8c7bcf27282a84b58875429def69c5817ade6d50a 10720 roarplaylistd-dev_0.1.7-3_all.deb 39fe9ac842bb3eedc1d96818290e953bf67da9077a97821da14be3e2f9dc7ba3 160524 roarplaylistd-dbg_0.1.7-3_amd64.deb
Bug#724614: marked as done (txt2man: CVE-2013-1444: unsafe use of temporary files)
Your message dated Fri, 27 Sep 2013 21:20:50 +
with message-id e1vpft0-0003ww...@franck.debian.org
and subject line Bug#724614: fixed in txt2man 1.5.5-4.1
has caused the Debian Bug report #724614,
regarding txt2man: CVE-2013-1444: unsafe use of temporary files
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.)
--
724614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: txt2man
Version: 1.5.5-4
Severity: normal
Tags: patch pending security
Dear maintainer,
txt2man in all suites allows overwriting of arbitrary files by an unsafe
use of the file /tmp/. This was introduced by a Debian patch.
The fix for this is to remove the line:
echo $post /tmp/
which appears to be leftover debugging.
It is my intention to perform an NMU in two days if the bug remains
unfixed, and to then upload fixes for stable and oldstable. If you object,
please tell me as soon as possible.
If you fix the bug yourself, please include a reference to the assigned CVE
number, CVE-2013-1444.
Regards.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
diff -Nru txt2man-1.5.5/debian/changelog txt2man-1.5.5/debian/changelog
--- txt2man-1.5.5/debian/changelog 2011-04-11 10:37:22.0 +0100
+++ txt2man-1.5.5/debian/changelog 2013-09-25 19:08:15.0 +0100
@@ -1,3 +1,12 @@
+txt2man (1.5.5-4.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Fix CVE-2013-1444: insecure use of temporary files
+by removing apparant debug output from
+patches/debian-changes-1.5.5-2.1 (Closes: #nn)
+
+ -- Jonathan Wiltshire j...@debian.org Wed, 25 Sep 2013 19:07:07 +0100
+
txt2man (1.5.5-4) unstable; urgency=low
* Updated Standards version
diff -Nru txt2man-1.5.5/debian/patches/debian-changes-1.5.5-2.1 txt2man-1.5.5/debian/patches/debian-changes-1.5.5-2.1
--- txt2man-1.5.5/debian/patches/debian-changes-1.5.5-2.1 2011-04-11 10:37:22.0 +0100
+++ txt2man-1.5.5/debian/patches/debian-changes-1.5.5-2.1 2013-09-25 19:07:02.0 +0100
@@ -47,7 +47,7 @@
printf .EH ||%s||\n $volume
--- txt2man-1.5.5.orig/txt2man
+++ txt2man-1.5.5/txt2man
-@@ -139,11 +139,12 @@ do
+@@ -139,11 +139,11 @@ do
p) doprobe=1;;
I) itxt=$OPTARG§$itxt;;
B) btxt=$OPTARG;;
@@ -57,7 +57,6 @@
*) usage; exit;;
esac
done
-+echo $post /tmp/
shift $(($OPTIND - 1))
date=${date:-$(date +'%d %B %Y')}
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: txt2man
Source-Version: 1.5.5-4.1
We believe that the bug you reported is fixed in the latest version of
txt2man, 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 724...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan Wiltshire j...@debian.org (supplier of updated txt2man 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: Wed, 25 Sep 2013 21:29:29 +0100
Source: txt2man
Binary: txt2man
Architecture: source all
Version: 1.5.5-4.1
Distribution: unstable
Urgency: low
Maintainer: Fredrik Steen st...@debian.org
Changed-By: Jonathan Wiltshire j...@debian.org
Description:
txt2man- Converts flat ASCII text to man page format
Closes: 724614
Changes:
txt2man (1.5.5-4.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix CVE-2013-1444: insecure use of temporary files
by removing apparant debug output from
patches/debian-changes-1.5.5-2.1 (Closes: #724614)
Thanks: Patrick Cherry of Bytemark Hosting
Checksums-Sha1:
25daa9b4b0997c7cabdb591a964349cf61f788db 1874 txt2man_1.5.5-4.1.dsc
c28b2c4d130139339117e7bfc3aa114b5c79e7d5 4351 txt2man_1.5.5-4.1.debian.tar.gz
a080987e1d1dce38df4d352a35de235e8eaec63b 14612 txt2man_1.5.5-4.1_all.deb
Checksums-Sha256:
0dfdb5f34f2b5c8dbb8e00f19ae0e286092a917395c452c8935f86c7e2ad7beb 1874
txt2man_1.5.5-4.1.dsc
83df7276e75d6f5a8a942ae1a3b48578ca8908746a1abcd3aae4c8c120e34852 4351
txt2man_1.5.5-4.1.debian.tar.gz
Bug#724133: marked as done (cupt: FTBFS: POD errors)
Your message dated Fri, 27 Sep 2013 21:19:25 + with message-id e1vpfrd-0002sh...@franck.debian.org and subject line Bug#724133: fixed in cupt 2.5.11 has caused the Debian Bug report #724133, regarding cupt: FTBFS: POD errors 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.) -- 724133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cupt Version: 2.5.10 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/locale/pl/LC_MESSAGES/cupt.mo -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/locale/da/LC_MESSAGES/cupt.mo -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/locale/sk/LC_MESSAGES/cupt.mo -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/locale/fr/LC_MESSAGES/cupt.mo -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/locale/de/LC_MESSAGES/cupt.mo make[2]: Leaving directory `/«PKGBUILDDIR»' chrpath --delete /«PKGBUILDDIR»/debian/tmp/usr/bin/cupt # produce additional man pages for cupt /usr/bin/perl debian/install_pods pod2man --utf8 --name CUPT --section 1 doc/cupt.1.pod cupt.1 dh_installman -pcupt cupt.1 rm cupt.1 pod2man --utf8 --name CUPT.CONF --section 5 doc/cupt.conf.5.pod cupt.conf.5 dh_installman -pcupt cupt.conf.5 rm cupt.conf.5 doc/cupt.conf.5.pod around line 422: alternative text '--no-auto-remove/' contains non-escaped | or / POD document had syntax errors at /usr/bin/pod2man line 71. installing man page cupt.conf.5 failed at debian/install_pods line 16. make[1]: *** [override_dh_auto_install] Error 255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/cupt_2.5.10_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: cupt Source-Version: 2.5.11 We believe that the bug you reported is fixed in the latest version of cupt, 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 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eugene V. Lyubimkin jac...@debian.org (supplier of updated cupt 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: Fri, 27 Sep 2013 18:31:59 +0300 Source: cupt Binary: libcupt2-0 libcupt2-dev libcupt2-doc cupt libcupt2-0-downloadmethod-curl libcupt2-0-downloadmethod-wget Architecture: source amd64 all Version: 2.5.11 Distribution: unstable Urgency: low Maintainer: Cupt developers cupt-de...@lists.alioth.debian.org Changed-By: Eugene V. Lyubimkin jac...@debian.org Description: cupt - alternative front-end for dpkg -- console interface libcupt2-0 - alternative front-end for dpkg -- runtime library libcupt2-0-downloadmethod-curl - alternative front-end for dpkg -- libcurl download method libcupt2-0-downloadmethod-wget - alternative front-end for dpkg -- wget download method libcupt2-dev - alternative front-end for dpkg -- development files libcupt2-doc - alternative front-end for dpkg -- library documentation Closes: 724133 Changes: cupt (2.5.11) unstable; urgency=low . * doc: - man/cupt.conf.5: - Fixed '--no-auto-remove' reference syntax. Fixes building with recent pod2man. (Closes: #724133) Checksums-Sha1: 0f888ca412deb609e23624de583910ec8eb2b17e 1438 cupt_2.5.11.dsc 32fb2d85411d927f0a944bd8ea5bcd44e7e87c40 335606 cupt_2.5.11.tar.gz 57a0c7dcf33dcb9a588a36476a91444c8bc2048e 587926 libcupt2-0_2.5.11_amd64.deb 797bfdea60a4f624ceadd10c6978eb674cec3f6c 50634 libcupt2-dev_2.5.11_amd64.deb 58769312e4424ef5bad5aa40db8a6a9d653d7ecb 162276 libcupt2-doc_2.5.11_all.deb
Bug#723803: marked as done (visp: FTBFS on armhf, ppc, s390: Errors while running CTest)
Your message dated Fri, 27 Sep 2013 22:19:15 + with message-id e1vpgnx-0003lk...@franck.debian.org and subject line Bug#723803: fixed in visp 2.8.0-3 has caused the Debian Bug report #723803, regarding visp: FTBFS on armhf, ppc, s390: Errors while running CTest 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.) -- 723803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: visp Version: 2.8.0-2 Severity: serious Justification: fails to build (but built successfully in the past) Control: block 706798 by -1 visp fails to build on armhf, ppc and s390 with test suite failures: | export VISP_INPUT_IMAGE_PATH=/usr/share/visp-images-data/ \ | dh_auto_test -- -j1 | make[2]: Entering directory `/«PKGBUILDDIR»/obj-arm-linux-gnueabihf' | Running tests... | /usr/bin/ctest --force-new-ctest-process -j1 | Test project /«PKGBUILDDIR»/obj-arm-linux-gnueabihf | Start 1: servoSimu4Points | 1/105 Test #1: servoSimu4Points .***Failed 2.27 sec | libdc1394 error: Failed to initialize libdc1394 | |^ | /«PKGBUILDDIR»/obj-arm-linux-gnueabihf/data/wireframe-simulator/camera.bnd, line 20: | symbol '$' expected | | Start 2: servoSimuCylinder | 2/105 Test #2: servoSimuCylinder ***Failed 0.55 sec | libdc1394 error: Failed to initialize libdc1394 | |^ | /«PKGBUILDDIR»/obj-arm-linux-gnueabihf/data/wireframe-simulator/camera.bnd, line 20: | symbol '$' expected | | Start 3: servoSimuSphere | 3/105 Test #3: servoSimuSphere ..***Failed 0.58 sec | libdc1394 error: Failed to initialize libdc1394 | |^ | /«PKGBUILDDIR»/obj-arm-linux-gnueabihf/data/wireframe-simulator/camera.bnd, line 20: | symbol '$' expected | | Start 4: calibrateTsai | 4/105 Test #4: calibrateTsai Passed 0.63 sec | Start 5: simulateFourPoints2DCartesianCamVelocity | 5/105 Test #5: simulateFourPoints2DCartesianCamVelocity . Passed 0.01 sec | Start 6: simulateFourPoints2DPolarCamVelocity | 6/105 Test #6: simulateFourPoints2DPolarCamVelocity . Passed 0.01 sec | Start 7: simulateCircle2DCamVelocity | 7/105 Test #7: simulateCircle2DCamVelocity .. Passed 0.01 sec | Start 8: displaySequence | 8/105 Test #8: displaySequence .. Passed 3.76 sec | Start 9: displayGDI | 9/105 Test #9: displayGDI ... Passed 0.01 sec | Start 10: displayD3D | 10/105 Test #10: displayD3D ... Passed 0.01 sec | Start 11: displayGTK | 11/105 Test #11: displayGTK ... Passed 0.01 sec | Start 12: displayX | 12/105 Test #12: displayX . Passed 0.56 sec | Start 13: displayOpenCV | 13/105 Test #13: displayOpenCV Passed 0.54 sec | Start 14: displayXMulti | 14/105 Test #14: displayXMulti Passed 0.87 sec | Start 15: photometricVisualServoing | 15/105 Test #15: photometricVisualServoing Passed 9.62 sec | Start 16: homographyHartleyDLT2DObject | 16/105 Test #16: homographyHartleyDLT2DObject . Passed 0.53 sec | Start 17: homographyHLM2DObject | 17/105 Test #17: homographyHLM2DObject Passed 0.53 sec | Start 18: homographyHLM3DObject | 18/105 Test #18: homographyHLM3DObject Passed 0.53 sec | Start 19: homographyRansac2DObject | 19/105 Test #19: homographyRansac2DObject . Passed 0.58 sec | Start 20: imageDiskRW | 20/105 Test #20: imageDiskRW .. Passed 1.82 sec | Start 21: exponentialMap | 21/105 Test #21: exponentialMap ... Passed 0.52 sec | Start 22: BSpline | 22/105 Test #22: BSpline .. Passed 0.53 sec | Start 23: Nurbs | 23/105 Test #23: Nurbs Passed 0.54 sec | Start 24: parse-argv1 | 24/105 Test #24: parse-argv1 .. Passed 0.53 sec | Start 25: parse-argv2 | 25/105
Processed: tagging #724746 as security issue
Processing commands for cont...@bugs.debian.org: tag 724746 + security Bug #724746 [tntnet] tntnet: Default configuration exports whole filesystem via HTTP Added tag(s) security. kthxbye Stopping processing here. Please contact me if you need assistance. -- 724746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724746 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: FTBFS: test failures
Processing control commands: tags 723909 + confirmed Bug #723909 [src:jifty] FTBFS: test failures Added tag(s) confirmed. -- 723909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723909 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#723909: FTBFS: test failures
Control: tags 723909 + confirmed Damyans log snipped doesn't show it, but it't lots of subtests that fail without any specific output: t/00-load.t Failed 1/2 subtests t/01-dependencies.t ok t/01-test-mechanize.t .. Failed 6/6 subtests t/01-test-web.t Failed 5/5 subtests t/01-version_checks.t .. ok t/02-connect.t . Failed 6/6 subtests t/03-form-protocol.t ... ok t/03-is_passing-no_plan.t .. No subtests run t/03-is_passing.t .. Failed 7/7 subtests t/03-test-mailbox.t Failed 2/2 subtests t/04-test_file.t ... No subtests run t/05-dispatcher.t .. skipped: Not written yet t/06-forms.t ... Failed 24/24 subtests t/07-limit-actions.t ... Failed 21/21 subtests t/08-client.t .. ok t/09-url.t . Failed 6/6 subtests ... Not all of these are reproducible for me outside the chroot. Those that are turn out to be segfaults, and as far as I've investigated, they all look very similar and occur in libsqlite3: #0 0x7fbe1c61330e in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #1 0x7fbe1c613369 in sqlite3_db_filename () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #2 0x7fbe1c8c968d in sqlite_db_filename () from /usr/lib/perl5/auto/DBD/SQLite/SQLite.so #3 0x7fbe1c8bc45f in ?? () from /usr/lib/perl5/auto/DBD/SQLite/SQLite.so #4 0x7fbe1cf2df5f in XS_DBI_dispatch () from /usr/lib/perl5/auto/DBI/DBI.so #5 0x7fbe225cac86 in Perl_pp_entersub () from /usr/lib/libperl.so.5.18 #6 0x7fbe225c32d6 in Perl_runops_standard () from /usr/lib/libperl.so.5.18 #7 0x7fbe2255461c in Perl_call_sv () from /usr/lib/libperl.so.5.18 #8 0x7fbe1cf2e8c1 in XS_DBI_dispatch () from /usr/lib/perl5/auto/DBI/DBI.so #9 0x7fbe225cac86 in Perl_pp_entersub () from /usr/lib/libperl.so.5.18 #10 0x7fbe225c32d6 in Perl_runops_standard () from /usr/lib/libperl.so.5.18 #11 0x7fbe22554890 in Perl_call_sv () from /usr/lib/libperl.so.5.18 #12 0x7fbe22556967 in Perl_call_list () from /usr/lib/libperl.so.5.18 #13 0x7fbe2253ca5f in ?? () from /usr/lib/libperl.so.5.18 #14 0x7fbe2254df2c in Perl_newATTRSUB_flags () from /usr/lib/libperl.so.5.18 #15 0x7fbe2254ea80 in Perl_newATTRSUB () from /usr/lib/libperl.so.5.18 #16 0x7fbe22551099 in Perl_utilize () from /usr/lib/libperl.so.5.18 #17 0x7fbe22580665 in Perl_yyparse () from /usr/lib/libperl.so.5.18 #18 0x7fbe2255a69c in perl_parse () from /usr/lib/libperl.so.5.18 #19 0x00400d7b in main () So maybe this (and the other jifty FTBFS) is related to #723812 (libdbd-sqlite3-perl FTBFS in test suite)? Florian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724325: xserver-xorg-video-nv: FTBFS against xserver 1.14
Julien Cristau: On Wed, Sep 25, 2013 at 10:57:10 +, Robert Millan wrote: Petr Salinger: your package needs to be rebuilt against xorg-server 1.14. That most likely means pulling in a couple changes from upstream git HEAD. It suffices to put attached file into debian/patches/ and enlist it in debian/patches/series. Please, could some DD (Robert, please) do the upload. Ideally for both kfreebsd-*, as non-free is usually not auto-build. I'm on it. AFAICT only kbsd-amd64 was uploaded, not -i386? kfreebsd-i386 uploaded now. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 723812 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=89011
Processing commands for cont...@bugs.debian.org: forwarded 723812 https://rt.cpan.org/Public/Bug/Display.html?id=89011 Bug #723812 [libdbd-sqlite3-perl] FTBFS: fails test suite Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=89011'. thanks Stopping processing here. Please contact me if you need assistance. -- 723812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723812 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: Pending fixes for bugs in the libdbd-sqlite3-perl package
Processing commands for cont...@bugs.debian.org: tag 723812 + pending Bug #723812 [libdbd-sqlite3-perl] FTBFS: fails test suite Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 723812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723812 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#723812: Pending fixes for bugs in the libdbd-sqlite3-perl package
tag 723812 + pending thanks Some bugs in the libdbd-sqlite3-perl package are closed in revision 95028df6cbb2e433cfc6dc159c05f0bd0bb4034f in branch 'master' by Florian Schlichting The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libdbd-sqlite3-perl.git;a=commitdiff;h=95028df Commit message: Add fix-test-sort.patch, fix test failure by forcing sqlite to actually sort something (closes: #723812) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723812: marked as done (FTBFS: fails test suite)
Your message dated Sat, 28 Sep 2013 00:03:34 + with message-id e1vpi0u-fp...@franck.debian.org and subject line Bug#723812: fixed in libdbd-sqlite3-perl 1.40-2 has caused the Debian Bug report #723812, regarding FTBFS: fails test suite 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.) -- 723812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libdbd-sqlite3-perl Version: 1.40-1+b1 Severity: serious Justification: fails to build from source (but built successfully in the past) I'm afraid that your package fails to build with new sqlite3, the failing test is: t/53_status.t ... 1/? # Failed test 'num of sort: 0' # at t/53_status.t line 49. # Failed test 'num of sort: 0' # at t/53_status.t line 49. # Looks like you failed 2 tests of 16. t/53_status.t ... Dubious, test returned 2 # (wstat 512, 0x200) Failed 2/16 subtests I tried it on x32 and amd64. It's quite likely the real culprit is sqlite3, but I don't know the details of its interface well enough to debug it easily. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11.1-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdbd-sqlite3-perl depends on: ii libc6 2.17-92+b1 ii libdbi-perl [perl-dbdabi-94] 1.628-1+b1 ii libsqlite3-0 3.8.0.2-1 ii perl 5.18.1-4 ii perl-base [perlapi-5.18.1]5.18.1-4 libdbd-sqlite3-perl recommends no packages. libdbd-sqlite3-perl suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: libdbd-sqlite3-perl Source-Version: 1.40-2 We believe that the bug you reported is fixed in the latest version of libdbd-sqlite3-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 723...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Schlichting f...@debian.org (supplier of updated libdbd-sqlite3-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: SHA256 Format: 1.8 Date: Sat, 28 Sep 2013 01:50:51 +0200 Source: libdbd-sqlite3-perl Binary: libdbd-sqlite3-perl Architecture: source amd64 Version: 1.40-2 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Florian Schlichting f...@debian.org Description: libdbd-sqlite3-perl - Perl DBI driver with a self-contained RDBMS Closes: 723812 Changes: libdbd-sqlite3-perl (1.40-2) unstable; urgency=low . * Team upload * Add fix-test-sort.patch, fix test failure by forcing sqlite to actually sort something (closes: #723812) Checksums-Sha1: 135f4c5c6810b8d9397fac9389c4f48431b9ac03 2352 libdbd-sqlite3-perl_1.40-2.dsc d3c6a4b4d28f285835979697adf1ec9de09433a5 10232 libdbd-sqlite3-perl_1.40-2.debian.tar.gz 25bb5be7850110dc5bf5737aec6e1b6b08f3b8bf 110052 libdbd-sqlite3-perl_1.40-2_amd64.deb Checksums-Sha256: 66f1775fc58fa5d1e7c48dae4e71cb6b946c3ba09ce18b3b213f155ede09a2b2 2352 libdbd-sqlite3-perl_1.40-2.dsc 05020356cf56dd6be1dc6ca8732cce3a4389ed8ca0da656247899a3167c4581c 10232 libdbd-sqlite3-perl_1.40-2.debian.tar.gz 2456c916a8600d433d96a7582ec5cd3a0ea0e1ad50a2b13b469c5f70b31035f8 110052 libdbd-sqlite3-perl_1.40-2_amd64.deb Files: f8489bb081aebc56f4ac8c83b2b3a770 2352 perl optional libdbd-sqlite3-perl_1.40-2.dsc ae1bcfb0ba01eb3a957da2430dff7c3c 10232 perl optional libdbd-sqlite3-perl_1.40-2.debian.tar.gz 6c427035ea54e79ba7a76165218702cf 110052 perl optional libdbd-sqlite3-perl_1.40-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCAAGBQJSRho6AAoJEBKXO25y3Ae1aTYP/2IPr3WFfNCBVmtRysm5kQlU DaXuvAz0ojfBAM1x+izn5hJfTnb3TK8Z3efx7BXCPvTwaMvkCXqR2/goqCZViwjD DemR/UTMZyP94+CDG2G9qaP+0YXqs6Rp9XH51RN1ePB8dVFulzCH1YwRXO8Qo+49 b1SWzqCRiN/jBUTFYuTcnTsRS+37zEZWpLTj5hCcNFlK6smmykkv9EadVN93sQ4J
Processed: fixed 683188 in 1.7.9-1
Processing commands for cont...@bugs.debian.org: fixed 683188 1.7.9-1 Bug #683188 [python-subversion] API change in python-subversion breaks trac Bug #676176 [python-subversion] trac: Unable to show changeset : TypeError: expecting an integer for the buffer size Bug #680298 [python-subversion] svnmailer does not work in wheezy/sid environment and exits with error Marked as fixed in versions subversion/1.7.9-1. Marked as fixed in versions subversion/1.7.9-1. Marked as fixed in versions subversion/1.7.9-1. thanks Stopping processing here. Please contact me if you need assistance. -- 676176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676176 680298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680298 683188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683188 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#724800: Xlib: extension RANDR missing on display
Package: xvfb Version: 2:1.14.3-3 Severity: grave Justification: renders package unusable I can no longer use Xvfb or xvfb-run after upgrading. Below is the output of a scenario that worked prior to the upgrade. astrope@trevor:~$ Xvfb :1 [1] 25891 astrope@trevor:~$ Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension GLX [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! export DISPLAY=:1 astrope@trevor:~$ firefox (process:25902): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed Xlib: extension RANDR missing on display :1. I also tried it with the +extension RANDR with the same result. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
