Bug#670329: marked as done (argyll: FTBFS everywhere (icoms.h:45:19: fatal error: usb.h: No such file or directory))
Your message dated Wed, 25 Apr 2012 06:02:32 + with message-id and subject line Bug#670329: fixed in argyll 1.4.0-4 has caused the Debian Bug report #670329, regarding argyll: FTBFS everywhere (icoms.h:45:19: fatal error: usb.h: No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 670329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: argyll Version: 1.4.0-3 Severity: serious Justification: fails to build from source (but built successfully in the past) See https://buildd.debian.org/status/package.php?p=argyll Cheers, Julien signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: argyll Source-Version: 1.4.0-4 We believe that the bug you reported is fixed in the latest version of argyll, which is due to be installed in the Debian FTP archive: argyll-dbg_1.4.0-4_i386.deb to main/a/argyll/argyll-dbg_1.4.0-4_i386.deb argyll_1.4.0-4.debian.tar.gz to main/a/argyll/argyll_1.4.0-4.debian.tar.gz argyll_1.4.0-4.dsc to main/a/argyll/argyll_1.4.0-4.dsc argyll_1.4.0-4_i386.deb to main/a/argyll/argyll_1.4.0-4_i386.deb icc-utils_1.4.0-4_i386.deb to main/a/argyll/icc-utils_1.4.0-4_i386.deb libicc-dev_2.12+argyll1.4.0-4_i386.deb to main/a/argyll/libicc-dev_2.12+argyll1.4.0-4_i386.deb libicc2_2.12+argyll1.4.0-4_i386.deb to main/a/argyll/libicc2_2.12+argyll1.4.0-4_i386.deb libimdi-dev_1.4.0-4_i386.deb to main/a/argyll/libimdi-dev_1.4.0-4_i386.deb libimdi0_1.4.0-4_i386.deb to main/a/argyll/libimdi0_1.4.0-4_i386.deb 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 670...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Marillat (supplier of updated argyll 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 25 Apr 2012 07:46:07 +0200 Source: argyll Binary: argyll argyll-dbg icc-utils libicc-dev libicc2 libimdi-dev libimdi0 Architecture: source i386 Version: 1.4.0-4 Distribution: unstable Urgency: low Maintainer: Christian Marillat Changed-By: Christian Marillat Description: argyll - Color Management System, calibrator and profiler argyll-dbg - debugging symbols for argyll icc-utils - ICC profile I/O library libicc-dev - Development files for the ICC profile I/O library libicc2- ICC profile I/O library libimdi-dev - Development files for the IMDI library libimdi0 - Integer Multi-Dimensional Interpolation routines (IMDI) library Closes: 670329 Changes: argyll (1.4.0-4) unstable; urgency=low . * Should Build-Depends on libusb-dev (Closes: #670329). Checksums-Sha1: 3ea45b5fe56e50860152e171f0c5b771b6558921 1744 argyll_1.4.0-4.dsc 60d7fa6bfb8b9d5a0966444db7ad99a321e4008f 352635 argyll_1.4.0-4.debian.tar.gz 8e882c9b62903b30d3944347ba2bf967673b6e62 161506 libicc2_2.12+argyll1.4.0-4_i386.deb cb33e600d539a6bd38344abc814819d03727a8e3 186098 libicc-dev_2.12+argyll1.4.0-4_i386.deb e4165d2bbd5cadc57dc1ffd03f02df85d37e4fc4 4177492 argyll_1.4.0-4_i386.deb 32e8b1e256df0b69e67b80256ce2f8c7418dd527 3346260 argyll-dbg_1.4.0-4_i386.deb 148ac0a7452cf872349fd0bb4454772425b836e9 73518 icc-utils_1.4.0-4_i386.deb 8ee5d7730b69d9485a8a1c731338c652de54610c 216988 libimdi-dev_1.4.0-4_i386.deb 8ee30a385560093364d42916dbafe2211bbb9212 223656 libimdi0_1.4.0-4_i386.deb Checksums-Sha256: 3fcbd1b1f66c5bee98cd14e36fd2274fa51554d55d32151a16b6e5d0c20d5475 1744 argyll_1.4.0-4.dsc 786929ec25b459d808b9b5bef6d05114cdd8e9a7d7d487b519ecae3b0e26069b 352635 argyll_1.4.0-4.debian.tar.gz a04b0ef75b61c0ec668ec3d41c7bde643e46396b8106d2ea47cd66b3bf593514 161506 libicc2_2.12+argyll1.4.0-4_i386.deb 1ec4b4efbc0a6703420a5d10f7587d757d1ce3f2d15547dba5bb7e5c4b24326f 186098 libicc-dev_2.12+argyll1.4.0-4_i386.deb 918e4fc40183ed026f150390f69357debd2e5bdc68d61b41b094bf560f077918 4177492 argyll_1.4.0-4_i386.deb 29cfa9284787870c98a0bba6a70d23c6ba76aadce53f07ee67c16963da02fb59 3346260 argyll-dbg_1.4.0-4_i386.deb 70abfb33da7607ce2dce14c24b3336b5e26f23464662965954586e197a0e6d6e 73518 icc-utils_1.4.0-4_i386.deb f59d0062d61c79fbae8650b6859677d085920c03cb83b60629ee55d6ec49e615 216988 libimdi-dev_1.4.0-4_i386.deb 39e99f480ed561f
Bug#670317: closing 670317
# This was fixed with DSA-2454-2 close 670317 0.9.8o-4squeeze12 thanks Closing this bug as it was fixed with DSA-2454-2. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: closing 670317
Processing commands for cont...@bugs.debian.org: > # This was fixed with DSA-2454-2 > close 670317 0.9.8o-4squeeze12 Bug #670317 [src:openssl] openssl: ASN1 BIO incomplete fix (CVE-2012-2131) The source openssl and version do not appear to match any binary packages Marked as fixed in versions openssl/0.9.8o-4squeeze12. Bug #670317 [src:openssl] openssl: ASN1 BIO incomplete fix (CVE-2012-2131) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 670317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670317 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#670378: [src:slang2] wrong dh_makeshlibs argument
Package: src:slang2
Version: 2.2.4-8
Severity: serious
Tags: patch
Dear Alastair,
Due to wrong argument to dh_makeshlibs, slang2 causing FTBFS to other
packages, notably to 'mc'.
in debian/rules, instead of
dh_makeshlibs -a -V "libslang2 {>= 2.0.7-1}" --add-udeb="libslang2-udeb"
it should be
dh_makeshlibs -a -V "libslang2 (>= 2.0.7-1)" --add-udeb="libslang2-udeb"
(patch is attached)
If this would be OK with you, I'm happy to join as co-maintainer for this
package.
Thank you.
All the best,
Dmitry.
signature.asc
Description: This is a digitally signed message part.
--- a/debian/rules
+++ b/debian/rules
@@ -41,7 +41,7 @@
dh_installchangelogs -a changes.txt
override_dh_makeshlibs:
- dh_makeshlibs -a -V "libslang2 {>= 2.0.7-1}" --add-udeb="libslang2-udeb"
+ dh_makeshlibs -a -V "libslang2 (>= 2.0.7-1)" --add-udeb="libslang2-udeb"
override_dh_compress:
dh_compress -a -X.sl -Xslangfun.txt
Processed: forcibly merging 642988 603066
Processing commands for cont...@bugs.debian.org: > forcemerge 642988 603066 Bug #642988 [linux-2.6] linux-headers packages in experimental are often uninstallable Bug #603066 [linux-2.6] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Severity set to 'grave' from 'wishlist' There is no source info for the package 'linux-2.6' at version '2.6.34-1~experimental.1' with architecture '' Unable to make a source version for version '2.6.34-1~experimental.1' There is no source info for the package 'linux-2.6' at version '3.1.0~rc6-1~experimental.1' with architecture '' Unable to make a source version for version '3.1.0~rc6-1~experimental.1' Marked as found in versions 3.1.0~rc6-1~experimental.1. Added tag(s) experimental. Bug #642988 [linux-2.6] linux-headers packages in experimental are often uninstallable There is no source info for the package 'linux-2.6' at version '2.6.34-1~experimental.1' with architecture '' Unable to make a source version for version '2.6.34-1~experimental.1' There is no source info for the package 'linux-2.6' at version '3.1.0~rc6-1~experimental.1' with architecture '' Unable to make a source version for version '3.1.0~rc6-1~experimental.1' Marked as found in versions 2.6.34-1~experimental.1. Merged 603066 642988 > thanks Stopping processing here. Please contact me if you need assistance. -- 603066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603066 642988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642988 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#670374: gobject-introspection not multi-arch compatible
Package: gir1.2-packagekitglib-1.0 Version: 0.7.3-3 Severity: serious gobject-introspection does not (yet) support mulit-arch so you must not install the typelib files into multi-arch paths but they must go into /usr/lib/girepository-1.0/ instead. A typical way to achieve this is to update gir1.2-packagekitglib-1.0.install and use: usr/lib/*/girepository-1.0/*.typelib usr/lib/girepository-1.0/ -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669932: marked as done (gwc: Auto-built binaries contains /usr/buildd/ dir)
Your message dated Wed, 25 Apr 2012 01:34:30 + with message-id and subject line Bug#669932: fixed in gwc 0.21.17~dfsg0-2 has caused the Debian Bug report #669932, regarding gwc: Auto-built binaries contains /usr/buildd/ dir 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.) -- 669932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gwc Version: 0.21.17~dfsg0-1 Severity: serious Hi, I am filing this as serious because it smells like a build misconfiguration. The problem (as the subject suggests) is that the binary packages built on buildds contains: """ /usr/build/buildd-gwc_0.21.17~dfsg0-1-i386-ZCgRmK/gwc-0.21.17~dfsg0/debian/tmp/usr/share/gnome/help/gnome_wave_cleaner/C/gwc.html /usr/build/buildd-gwc_0.21.17~dfsg0-1-i386-ZCgRmK/gwc-0.21.17~dfsg0/debian/tmp/usr/share/gnome/help/gnome_wave_cleaner/C/gwc_qs.html /usr/build/buildd-gwc_0.21.17~dfsg0-1-i386-ZCgRmK/gwc-0.21.17~dfsg0/debian/tmp/usr/share/gnome/help/gnome_wave_cleaner/C/topic.dat """ (with slight variations between architectures). The amd64 packages are unaffected and I suspect these are the maintainer built packages, though I admit only checking a handful of architectures. ~Niels --- End Message --- --- Begin Message --- Source: gwc Source-Version: 0.21.17~dfsg0-2 We believe that the bug you reported is fixed in the latest version of gwc, which is due to be installed in the Debian FTP archive: gwc-dbg_0.21.17~dfsg0-2_amd64.deb to main/g/gwc/gwc-dbg_0.21.17~dfsg0-2_amd64.deb gwc_0.21.17~dfsg0-2.debian.tar.gz to main/g/gwc/gwc_0.21.17~dfsg0-2.debian.tar.gz gwc_0.21.17~dfsg0-2.dsc to main/g/gwc/gwc_0.21.17~dfsg0-2.dsc gwc_0.21.17~dfsg0-2_amd64.deb to main/g/gwc/gwc_0.21.17~dfsg0-2_amd64.deb 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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia (supplier of updated gwc 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Apr 2012 03:04:17 +0200 Source: gwc Binary: gwc gwc-dbg Architecture: source amd64 Version: 0.21.17~dfsg0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Alessio Treglia Description: gwc- Audio file denoiser gwc-dbg- Audio file denoiser (debug) Closes: 669932 Changes: gwc (0.21.17~dfsg0-2) unstable; urgency=medium . * debian/patches/0001-buildsystem.patch: - Fix installation path of GNOME stuff (Closes: #669932) Checksums-Sha1: e4d17613ad147a849473bcd3dc76ec661268da95 2128 gwc_0.21.17~dfsg0-2.dsc ea567ef381cf6e2036388bd35b756c5510a86dce 10413 gwc_0.21.17~dfsg0-2.debian.tar.gz 73648f6a6f97edaa31a39443a2834813957e67b9 199702 gwc_0.21.17~dfsg0-2_amd64.deb 7536f20c7c92549e304621f15c78ce5bb34a8e19 318698 gwc-dbg_0.21.17~dfsg0-2_amd64.deb Checksums-Sha256: a7c1d325a1233a772849e22ec87cb8bad098675a232e8f3286b882db73ff8318 2128 gwc_0.21.17~dfsg0-2.dsc f74ba13f2d6f6bc7d218c6fc724ba714b349e793f997fcab9d20716639a7202d 10413 gwc_0.21.17~dfsg0-2.debian.tar.gz 9029f297229a3455e06ceeb1aa8aeab31d76e530104ddb07cc33e500d9908e6b 199702 gwc_0.21.17~dfsg0-2_amd64.deb aef364fa4057689933a05a2985228e4cebd69f5d2c053c14ea123be6e5958ebf 318698 gwc-dbg_0.21.17~dfsg0-2_amd64.deb Files: 2a4c9c754e14527079726382742988a1 2128 sound optional gwc_0.21.17~dfsg0-2.dsc aa7eace567d4f59c8e2ddb166d4f77d8 10413 sound optional gwc_0.21.17~dfsg0-2.debian.tar.gz 802dd33a98918f98f0fa62603b69118f 199702 sound optional gwc_0.21.17~dfsg0-2_amd64.deb fb9377b2d28931e68b7f34d578b3cca9 318698 debug extra gwc-dbg_0.21.17~dfsg0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJPl06OAAoJEOikiuUxHXZaDw4P/22kNwoHdMu6FFf9iy9hj8/D 4DbttINpJgTSYPRfADjvVQIv2ELR989WPFF6AH961S+7CleYiMgvIm9uJWUBbmRs 1wdz5j+hGzIwdfFq+MZ+Hs8WJUqxaoLmOIPqNEcKrehIO2AeQdqyHwe38tnA1qwo 9Bp3a2/nSyWlTLhA5gsrNXJapO3p2/QtEk238LvwKk3kdPcHLEw76Iw3qTi5Kfw7 4abM14IZh6f2xBzyKmg9u8hygZUGN0ziyigcotuz3KA5uM2BJ0CidBTzVFE/smDT 9SNa0VajbZJc2xwoXP8KMUuEW5szfnjOf3BCH0fMYoarYIgakDBuXSVdAirVuawy z+3lU6ef59N5K9T31s9rRTC7jFYghk7Hozzev3evkNGMhO3DbWmWBFxsyoD1G/0/ i+JXRmauGXNc5OCFLJH/ClpOVU4ONDKZ/k7uW98r
Bug#635382: marked as done (latex-unicode sources and licensing)
Your message dated Wed, 25 Apr 2012 01:11:17 +
with message-id
and subject line Bug#635382: fixed in texlive-extra 2011.20120424-1
has caused the Debian Bug report #635382,
regarding latex-unicode sources and licensing
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.)
--
635382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-extra
Version: 2009-10
Severity: normal
Tags: patch
Near beginning of ucshyper.sty:
\ifx\pdfoutput\undefined
\PackageWarning{ucshyper}{ucshyper needs to be run with
pdflatex.\MessageBreak Disabling functionality}%
\expandafter\endinput\fi
This is buggy in several ways.
1) If another package loaded before ucshyper has used \@ifundefined
to test the value of pdfoutput, then it is redefined to \relax
instead of \undefined, and the above test will take the wrong
branch.
2) Even if 1) is fixed, this tests whether the TeX implementation
running is pdfTeX, while what it probably was intended to test for
is whether the output produced is PDF... In other words, this test
will not issue the warning if pdftex is running in DVI output mode;
this is what happens in Debian when one runs /usr/bin/tex or
/usr/bin/latex.
E.g. this document:
\documentclass{article}
\usepackage{ucshyper}
\begin{document}
foo
\end{document}
leads to this (La)TeX output (when run with plain latex):
LaTeX2e <2009/09/24>
(...)
Package hyperref Warning: Wrong driver `hpdftex.def';
(hyperref)pdfTeX is not running in PDF mode.
(hyperref)Using default driver.
*hyperref using default driver hdvips*
(...)
! Undefined control sequence.
\pdfstringdef ...@pdfstringtrue \PrerenderUnicode
{#2}\endgroup \fi \ucshype...
l.5 \end{document}
?
Luckily (as you probably already know), the ifpdf package takes care
of these details for you, so the above code should be replaced by
something like:
\RequirePackage{ifpdf}
\ifpdf\else%
\PackageWarning{ucshyper}{ucshyper needs to be run with
pdflatex.\MessageBreak Disabling functionality}%
\expandafter\endinput\fi
See /usr/share/doc/texlive-doc/generic/FAQ-en/html/FAQ-ifpdf.html and
/usr/share/doc/texlive-doc/latex/oberdiek/ifpdf.pdf for more details.
However, there is a third issue even with 1) and 2) solved.
3) ucshyper does not actually need the output mode to be PDF, nor the
TeX implementation to be pdfTeX. I just _removed_ the above test,
as well as the following line:
\RequirePackage[pdftex,unicode]{hyperref}
and then I produce DVI with hyperref's "dvipdfm" option (driver
hdvipdfm), run it through dvipdfm and ucshyper still does its job like
a charm. For example this document:
\documentclass{article}
\usepackage[utf8x]{inputenc}
\usepackage[dvipdfm,bookmarks=true,unicode=true]{hyperref}
\usepackage{ucshyper}
\begin{document}
\section{\texorpdfstring{\ensuremath\lambda{}}{λ}}
\end{document}
latex it, run dvipdfm over the dvi, and the \lambda looks fine in
evince's side panel (Index).
So possibly this test should be changed to something like:
\ifdefined\PrerenderUnicode\else%
\PackageWarning{ucshyper}{ucshyper needs to be run with
inputenc utf8x.\MessageBreak Disabling functionality}%
\expandafter\endinput\fi
_and_ still remove the
\RequirePackage[pdftex,unicode]{hyperref}
line so that users can choose their own hyperref driver freely. Maybe
add instead:
\ifdefined\hypersetup%
\hypersetup{unicode=true}%
\else%
\PackageWarning{ucshyper}{ucshyper needs to be loaded after
hyperref.\MessageBreak Disabling functionality}%
\expandafter\endinput%
\fi%
I'd be tempted to promote the warnings to errors, actually.
##
minimal input file
See above
##
other files
##
List of ls-R files
-rw-r--r-- 1 root root 1753 Jun 10 19:05 /var/lib/texmf/ls-R
-rw-rw-r-- 1 root staff 80 Jun 28 2010 /usr/local/share/texmf/ls-R
lrwxrwxrwx 1 root root 29 Jun 10 19:00 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 27 Oct 28 2010 /usr/share/texmf-texlive/ls-R ->
/var/lib/texmf/ls-R-TEXLIVE
lrwxrwxrwx 1 root root 27 Oct 28 2010 /usr/share/texmf-texlive/ls-R ->
/var/lib/texmf/ls-R-TEXLIVE
##
Config files
lrwxrwxrwx 1 root root 20 Jun 10 19:00 /usr/share/texmf/web2c/texmf.cnf ->
/etc/texmf/texmf.cnf
-rw-r--r-- 1 root root 10081 Jun 10 19:05 /var/lib/texmf/web2c/
Bug#670109: marked as done (texlive-xetex: removal of texlive-xetex makes files disappear from texlive-math-extra)
Your message dated Wed, 25 Apr 2012 01:05:43 + with message-id and subject line Bug#670109: fixed in texlive-base 2011.20120424-1 has caused the Debian Bug report #670109, regarding texlive-xetex: removal of texlive-xetex makes files disappear from texlive-math-extra 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.) -- 670109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: texlive-xetex Version: 2011.20120410-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and EDOS tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. The installation sequence to reproduce this problem is apt-get install texlive-math-extra # (1) apt-get install texlive-xetex apt-get remove texlive-xetex # (2) The list of installed files at points (1) and (2) should be identical, but the following files have disappeared: /usr/share/doc/texlive-doc/latex/realscripts/README /usr/share/doc/texlive-doc/latex/realscripts/realscripts.pdf /usr/share/texlive/texmf-dist/tex/latex/realscripts/realscripts.sty This is a serious bug violating policy 7.6, see http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces and also see the footnote that describes this incorrect behavior http://www.debian.org/doc/debian-policy/footnotes.html#f53 The texlive-xetex package has the following relationships with texlive-math-extra: Conflicts: n/a Breaks:n/a Replaces: texlive-math-extra (<= 2011.20120322-1) >From the attached log (scroll to the bottom...): 1m46.5s INFO: Warning: Package purging left files on system: /var/lib/texmf/web2c/xetex/not owned 1m46.5s ERROR: FAIL: After purging files have disappeared: /usr/share/doc/texlive-doc/latex/realscripts/READMEowned by: texlive-xetex /usr/share/doc/texlive-doc/latex/realscripts/realscripts.pdf owned by: texlive-xetex /usr/share/texlive/texmf-dist/tex/latex/realscripts/realscripts.styowned by: texlive-xetex 1m46.5s ERROR: FAIL: After purging files have been modified: /var/lib/dpkg/info/texlive-math-extra.list not owned /var/lib/texmf/ls-Rnot owned /var/lib/texmf/ls-R-TEXLIVEDISTnot owned /var/lib/texmf/web2c/fmtutil.cnf not owned The modified files are a consequence of the disappeared ones. cheers, Andreas texlive-math-extra=2011.20120322-1_texlive-xetex=2011.20120410-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: texlive-base Source-Version: 2011.20120424-1 We believe that the bug you reported is fixed in the latest version of texlive-base, which is due to be installed in the Debian FTP archive: texlive-base_2011.20120424-1.debian.tar.gz to main/t/texlive-base/texlive-base_2011.20120424-1.debian.tar.gz texlive-base_2011.20120424-1.dsc to main/t/texlive-base/texlive-base_2011.20120424-1.dsc texlive-base_2011.20120424-1_all.deb to main/t/texlive-base/texlive-base_2011.20120424-1_all.deb texlive-base_2011.20120424.orig.tar.gz to main/t/texlive-base/texlive-base_2011.20120424.orig.tar.gz texlive-common_2011.20120424-1_all.deb to main/t/texlive-base/texlive-common_2011.20120424-1_all.deb texlive-fonts-recommended-doc_2011.20120424-1_all.deb to main/t/texlive-base/texlive-fonts-recommended-doc_2011.20120424-1_all.deb texlive-fonts-recommended_2011.20120424-1_all.deb to main/t/texlive-base/texlive-fonts-recommended_2011.20120424-1_all.deb texlive-full_2011.20120424-1_all.deb to main/t/texlive-base/texlive-full_2011.20120424-1_all.deb texlive-generic-recommended_2011.20120424-1_all.deb to main/t/texlive-base/texlive-generic-recommended_2011.20120424-1_all.deb texlive-latex-base-doc_2011.20120424-1_all.deb to main/t/texlive-base/texlive-latex-base-doc_2011.20120424-1_all.deb texlive-latex-base_2011.20120424-1_all.deb to main/t/texlive-base/texlive-latex-base_2011.20120424-1_all.deb texlive-latex-recommended-doc_2011.20120424-1_all.deb to main/t/texlive-base/texlive-latex-recommended-doc_2011.20120424-1_all.deb texlive-latex-recommended_2011.20120424-1_all.deb to main/t/texlive-base/texlive-latex-recommended_2011.20120424-1_all.deb texlive-luatex_2011.20120424-1_all.deb to main/t/texlive-base/texlive-luatex_2011.20120424-1_all.deb texlive-metapost-doc_2011.20120424-1_all.deb to main/t/texlive-base/texlive-metapost-doc_2011.20120424-1_all.deb texlive-metapost_2011.20120424-1
Bug#669308: webkit: FTBFS[kfreebsd]: #error Unsupported Platform
Hi, Attached is an updated patch. I've done as Robert Millan suggested, and hopefully this may even allow building now on Hurd too (though I haven't tested that). I've tested that this allows webkit to compile now on kfreebsd-i386 (though my VM doesn't have enough memory to finish linking!) Regards, -- Steven Chamberlain ste...@pyro.eu.org Index: webkit-1.8.0/Source/ThirdParty/ANGLE/src/compiler/osinclude.h === --- webkit-1.8.0.orig/Source/ThirdParty/ANGLE/src/compiler/osinclude.h 2012-04-23 20:55:53.0 +0100 +++ webkit-1.8.0/Source/ThirdParty/ANGLE/src/compiler/osinclude.h 2012-04-23 20:57:46.167404121 +0100 @@ -15,7 +15,7 @@ #if defined(_WIN32) || defined(_WIN64) #define ANGLE_OS_WIN #elif defined(__APPLE__) || defined(__linux__) || \ - defined(__FreeBSD__) || defined(__OpenBSD__) || \ + defined(__FreeBSD__) || defined(__GLIBC__) || defined(__OpenBSD__) || \ defined(__sun) || defined(ANDROID) #define ANGLE_OS_POSIX #else
Bug#669537: marked as done (apparmor: FTBFS: pdflatex fails)
Your message dated Wed, 25 Apr 2012 00:47:22 + with message-id and subject line Bug#669537: fixed in apparmor 2.7.103-1 has caused the Debian Bug report #669537, regarding apparmor: FTBFS: pdflatex fails 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.) -- 669537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apparmor Version: 2.7.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/«PKGBUILDDIR»/parser/libapparmor_re' > bison -o parse.cc parse.y > g++ -g -O2 -pipe -Wall -Wsign-compare -Wmissing-field-initializers > -Wformat-security -Wunused-parameter -D_GNU_SOURCE -std=c++0x -c -o parse.o > parse.cc > g++ -g -O2 -pipe -Wall -Wsign-compare -Wmissing-field-initializers > -Wformat-security -Wunused-parameter -D_GNU_SOURCE -std=c++0x -c -o > expr-tree.o expr-tree.cc > g++ -g -O2 -pipe -Wall -Wsign-compare -Wmissing-field-initializers > -Wformat-security -Wunused-parameter -D_GNU_SOURCE -std=c++0x -c -o hfa.o > hfa.cc > g++ -g -O2 -pipe -Wall -Wsign-compare -Wmissing-field-initializers > -Wformat-security -Wunused-parameter -D_GNU_SOURCE -std=c++0x -c -o chfa.o > chfa.cc > g++ -g -O2 -pipe -Wall -Wsign-compare -Wmissing-field-initializers > -Wformat-security -Wunused-parameter -D_GNU_SOURCE -std=c++0x -c -o > aare_rules.o aare_rules.cc > ar -rcs libapparmor_re.a parse.o expr-tree.o hfa.o chfa.o aare_rules.o > make[2]: Leaving directory `/«PKGBUILDDIR»/parser/libapparmor_re' > rm -f ./libstdc++.a > ln -s `g++ -print-file-name=libstdc++.a` > g++ -g -O2 -pipe -Wall -Wsign-compare -Wmissing-field-initializers > -Wformat-security -Wunused-parameter -D_GNU_SOURCE -Wstrict-prototypes > -Wnested-externs -DPACKAGE=\"apparmor-parser\" > -DLOCALEDIR=\"/usr/share/locale\" -DSUBDOMAIN_CONFDIR=\"/etc/apparmor\" -o > apparmor_parser parser_common.o parser_include.o parser_interface.o > parser_lex.o parser_main.o parser_misc.o parser_merge.o parser_symtab.o > parser_yacc.o parser_regex.o parser_variable.o parser_policy.o parser_alias.o > \ > libapparmor_re/libapparmor_re.a libstdc++.a -static-libgcc -L. > /usr/bin/pod2man apparmor.d.pod --release="AppArmor 2.7.99" --center=AppArmor > --section=5 > apparmor.d.5 > /usr/bin/pod2man apparmor.pod --release="AppArmor 2.7.99" --center=AppArmor > --section=7 > apparmor.7 > /usr/bin/pod2man apparmor_parser.pod --release="AppArmor 2.7.99" > --center=AppArmor --section=8 > apparmor_parser.8 > /usr/bin/pod2man subdomain.conf.pod --release="AppArmor 2.7.99" > --center=AppArmor --section=5 > subdomain.conf.5 > /usr/bin/pod2man apparmor.vim.pod --release="AppArmor 2.7.99" > --center=AppArmor --section=5 > apparmor.vim.5 > /usr/bin/pod2html --header --css apparmor.css --infile=apparmor.d.pod > --outfile=apparmor.d.5.html > /usr/bin/pod2html --header --css apparmor.css --infile=apparmor.pod > --outfile=apparmor.7.html > /usr/bin/pod2html --header --css apparmor.css --infile=apparmor_parser.pod > --outfile=apparmor_parser.8.html > /usr/bin/pod2html --header --css apparmor.css --infile=subdomain.conf.pod > --outfile=subdomain.conf.5.html > /usr/bin/pod2html --header --css apparmor.css --infile=apparmor.vim.pod > --outfile=apparmor.vim.5.html > while pdflatex techdoc.tex > /dev/null 2>&1 || exit 1 ; \ > grep -q "Label(s) may have changed" techdoc.log; \ > do :; done > make[1]: *** [techdoc.pdf] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/apparmor_2.7.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: apparmor Source-Version: 2.7.103-1 We believe that the bug you reported is fixed in the latest version of apparmor, which is due to be installed in the Debian FTP archive: apparmor-docs_2.7.103-1_all.deb to main/a/apparmor/apparmor-docs_2.7.103-1_all.deb apparmor-notify_2.7.103-1_all.deb to main/a/apparmor/apparmor-notify_2.7.103-1_all.deb apparmor-profiles_2.7.103-1_all.deb to main/a/apparmor/apparmor-profiles_2.7.103-1_all.deb
Processed: re: libxslt: FTBFS: sed: can't read debian/tmp/usr/lib/*.la: No such, file or directory
Processing commands for cont...@bugs.debian.org: > tags 666333 +patch Bug #666333 [src:libxslt] libxslt: FTBFS: sed: can't read debian/tmp/usr/lib/*.la: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 666333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666333 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#605452:
I also have this problem. When, at first stratup, I configure the album's directories and Digikam starts to create the database, it crashesIf I launch digikam from Konsole, I've this output: mirko@darkstar:~$ digikam QLayout: Cannot add null widget to QVBoxLayout/ digikam: Fatal IO error: client killed KCrash: Application 'digikam' crashing... sock_file=/home/mirko/.kde/socket-darkstar/kdeinit4__0 [1]+ Stopped digikam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666333: libxslt: FTBFS: sed: can't read debian/tmp/usr/lib/*.la: No such, file or directory
tags 666333 +patch thanks This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Specifically the reason this fails is that a wildcard target in debian/rules matches build-arch. The attatched patch fixes the issue by explicity defining build-arch to be equivilent to build (the package doesn't build any arch independent packages so this seems like the most sensible thing to do). It also includes a NMU changelog entry, if I get no maintainer response then I may look for someone to sponsor this as a NMU. diff -ur libxslt-1.1.26/debian/changelog libxslt-1.1.26.new/debian/changelog --- libxslt-1.1.26/debian/changelog 2012-04-25 00:24:04.0 + +++ libxslt-1.1.26.new/debian/changelog 2012-04-25 00:37:40.0 + @@ -1,3 +1,10 @@ +libxslt (1.1.26-8.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix building with build-arch. Closes: 666333. + + -- Peter Michael Green Tue, 24 Apr 2012 23:23:50 + + libxslt (1.1.26-8) unstable; urgency=low * debian/rules: diff -ur libxslt-1.1.26/debian/rules libxslt-1.1.26.new/debian/rules --- libxslt-1.1.26/debian/rules 2012-04-25 00:24:04.0 + +++ libxslt-1.1.26.new/debian/rules 2012-04-24 23:23:41.0 + @@ -17,6 +17,10 @@ configure-main: CONFIGURE_FLAGS += --without-python configure-python%: CONFIGURE_FLAGS += --with-python=/usr/bin/$* +# We don't build any architecture independent packages so make build-arch do the same as +# Build. +build-arch: build + override_dh_auto_build: $(TARGETS:%=build-%) build-%: BUILD_DIR=build/$*
Bug#655643: marked as done (pymvpa: FTBFS: AttributeError: classify)
Your message dated Wed, 25 Apr 2012 00:18:56 + with message-id and subject line Bug#655643: fixed in pymvpa 0.4.8-1 has caused the Debian Bug report #655643, regarding pymvpa: FTBFS: AttributeError: classify 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.) -- 655643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pymvpa Version: 0.4.7-2 Severity: serious Justification: fails to build from source pymvpa FTBFS: | == | ERROR: testRegressionsClassifiers (mvpa.tests.test_regr.RegressionsTests) | -- | Traceback (most recent call last): | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/tests/tests_warehouse.py", line 72, in do_sweep | method(*args_, **kwargs_) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/tests/test_regr.py", line 111, in testRegressionsClassifiers | cverror = cv(ds) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/measures/base.py", line 105, in __call__ | result = self._call(dataset) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/algorithms/cvtranserror.py", line 190, in _call | result = transerror(split[1], split[0]) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/transerror.py", line 1309, in __call__ | self._precall(testdataset, trainingdataset) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/transerror.py", line 1265, in _precall | self.__clf.train(trainingdataset) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/base.py", line 394, in train | result = self._train(dataset) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/sg/svm.py", line 468, in _train | trained_labels = self.__svm.classify().get_labels() | File "/usr/lib/python2.7/dist-packages/modshogun.py", line 48833, in | __getattr__ = lambda self, name: _swig_getattr(self, LibSVR, name) | File "/usr/lib/python2.7/dist-packages/modshogun.py", line 59, in _swig_getattr | raise AttributeError(name) | AttributeError: classify | | == | ERROR: testCperClass (mvpa.tests.test_svm.SVMTests) | -- | Traceback (most recent call last): | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/tests/tests_warehouse.py", line 72, in do_sweep | method(*args_, **kwargs_) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/tests/test_svm.py", line 127, in testCperClass | e = cve(ds__) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/measures/base.py", line 105, in __call__ | result = self._call(dataset) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/algorithms/cvtranserror.py", line 190, in _call | result = transerror(split[1], split[0]) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/transerror.py", line 1310, in __call__ | error = self._call(testdataset, trainingdataset) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/transerror.py", line 1416, in _call | predictions = clf.predict(testdataset.samples) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/base.py", line 476, in predict | result = self._predict(data) | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/clfs/sg/svm.py", line 544, in _predict | values_ = self.__svm.classify() | File "/usr/lib/python2.7/dist-packages/modshogun.py", line 46028, in | __getattr__ = lambda self, name: _swig_getattr(self, LibSVM, name) | File "/usr/lib/python2.7/dist-packages/modshogun.py", line 59, in _swig_getattr | raise AttributeError(name) | AttributeError: classify | | == | ERROR: testFeatureSelectionClassifierWithRegression (mvpa.tests.test_clf.ClassifiersTests) | -- | Traceback (most recent call last): | File "/build/pymvpa-ZxRJAY/pymvpa-0.4.7/build/lib.linux-i686-2.7/mvpa/tests/test_clf.py", line 417, in testFeatureSelectionClassifierWithRegression | clf_reg.train(d
Bug#664663: marked as done (collabtive: prompting due to modified conffiles which where not modified by the user)
Your message dated Tue, 24 Apr 2012 18:00:56 -0500 with message-id <20120424230056.gk26...@gwolf.org> and subject line Re: collabtive: prompting due to modified conffiles which where not modified by the user has caused the Debian Bug report #664663, regarding collabtive: prompting due to modified conffiles which where not modified by the user 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.) -- 664663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: collabtive Version: 0.7.5-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." http://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In http://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): Setting up collabtive (0.7.5-5) ... Configuration file `/etc/collabtive/config.php' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** config.php (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing collabtive (--configure): EOF on stdin at conffile prompt cheers, Andreas collabtive_0.7.5-5.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Hi, While I agree with your bug report, this problem occurs only when upgrading from ≤ 0.7.5-3 to ≥ 0.7.5-4. That is, affected versions are not very likely to be present except in a small amount of systems in testing, and none in stable. I am closing this bug, not because it is not a real bug, but because of its very small impact (and the time that would most probably be invested in fixing it according to the letter). Please reopen if you disagree with me, and I'll (sigh) take a deep look at it. --- End Message ---
Bug#670169: [Pkg-sssd-devel] Bug#670169: empty lib{pam,nss}-sss packages
On Mon, Apr 23, 2012 at 11:26:55PM +0300, Timo Aaltonen wrote: > looks perfectly fine, since you are searching for the string > 'libpam-sss' from the installed files.. you want the -L switch. How embarrassing - thanks for pointing this out! -- 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 670338 is important
Processing commands for cont...@bugs.debian.org: > # hurd bugs are not RC > severity 670338 important Bug #670338 [libquicktime-dev] libquicktime-dev: FTBFS on hurd. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 670338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670338 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#670338: libquicktime-dev: FTBFS on hurd.
On Tue, Apr 24, 2012 at 19:02:51 +, Cyril Roelandt wrote: > Package: libquicktime-dev > Severity: serious > Tags: patch > Justification: fails to build from source > Bugs affecting non-release architectures never have a severity bigger than important. Cheers, Julien signature.asc Description: Digital signature
Bug#670338: libquicktime-dev: FTBFS on hurd.
Package: libquicktime-dev
Severity: serious
Tags: patch
Justification: fails to build from source
Dear Maintainer,
* What led up to the situation?
libquicktime FTBFS on hurd-i386 (cf.
http://people.debian.org/~sthibault/graph-top.txt). Building the source from
the git repository fails with :
lqt_codecinfo.c:614:21: error: 'PATH_MAX' undeclared (first use in this
function)
* What exactly did you do (or not do) that was effective (or
ineffective)?
The attached patches fix this issue and should be portable enough to be adopted
upstream.
WBR,
Cyril Roelandt.
-- System Information:
Debian Release: wheezy/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)
Kernel: GNU-Mach 1.3.99/Hurd-0.3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/src/lqt_codecinfo.c b/src/lqt_codecinfo.c
index a04b10a..1a95be6 100644
--- a/src/lqt_codecinfo.c
+++ b/src/lqt_codecinfo.c
@@ -601,7 +601,8 @@ static int scan_for_plugins(const char * plugin_dir, lqt_codec_info_t ** databas
{
char * pos;
int ret;
- char * filename;
+ char * filename = NULL;
+ size_t filename_len = 0, new_size = 0;
DIR * directory;
struct dirent * directory_entry;
struct stat status;
@@ -611,8 +612,6 @@ static int scan_for_plugins(const char * plugin_dir, lqt_codec_info_t ** databas
lqt_codec_info_t * video_codecs_end;
lqt_codec_info_t * audio_codecs_end;
- filename = malloc(PATH_MAX * sizeof(char));
-
/* Set the end pointers so we can quickly add codecs after */
@@ -662,6 +661,14 @@ static int scan_for_plugins(const char * plugin_dir, lqt_codec_info_t ** databas
/* Now, the file should be a valid plugin, construct the filename */
+new_size = strlen(plugin_dir) + strlen(directory_entry->d_name) + 2;
+if (new_size > filename_len)
+ {
+ filename_len = new_size;
+ filename = realloc(filename, filename_len);
+ if (!filename)
+exit(EXIT_FAILURE);
+ }
strcpy(filename, plugin_dir);
strcat(filename, "/");
strcat(filename, directory_entry->d_name);
diff --git a/utils/rechunk.c b/utils/rechunk.c
index 1e4be29..0266112 100644
--- a/utils/rechunk.c
+++ b/utils/rechunk.c
@@ -46,7 +46,7 @@ static char ** add_frames_from_file(char ** input_frames,
{
FILE * input;
char * pos;
- char filename[PATH_MAX+10];
+ char *filename = NULL;
input = fopen(list_filename, "r");
if(!input)
@@ -56,7 +56,7 @@ static char ** add_frames_from_file(char ** input_frames,
return (char**)0;
}
- while(fgets(filename, PATH_MAX+10, input))
+ while(getline(&filename, NULL, input) != -1)
{
/* Delete trailing '\n' and '\r' */
@@ -72,7 +72,10 @@ static char ** add_frames_from_file(char ** input_frames,
break;
if(pos == filename)
+{
+free(filename);
return input_frames;
+}
pos--;
}
@@ -83,6 +86,8 @@ static char ** add_frames_from_file(char ** input_frames,
input_frames = realloc(input_frames, sizeof(char*) * *total_input_frames);
input_frames[*total_input_frames - 1] = strdup(filename);
//fprintf(stderr, "Adding file %s\n", input_frames[*total_input_frames - 1]);
+free(filename);
+filename = NULL;
}
return input_frames;
}
Processed: user debian...@lists.debian.org, found 669278 in kde-plasma-desktop/5:74 ..., usertagging 670208 ...
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was deb...@abeckmann.de).
> found 669278 kde-plasma-desktop/5:74
Bug #669278 [phonon] please add phonon-backend-xine transitional package
The source kde-plasma-desktop and version 5:74 do not appear to match any
binary packages
Marked as found in versions kde-plasma-desktop/5:74.
> found 669278 kdebase-workspace/4:4.7.4-2
Bug #669278 [phonon] please add phonon-backend-xine transitional package
The source kdebase-workspace and version 4:4.7.4-2 do not appear to match any
binary packages
Marked as found in versions kdebase-workspace/4:4.7.4-2.
> found 669278 smokekde/4:4.7.4-1
Bug #669278 [phonon] please add phonon-backend-xine transitional package
Marked as found in versions smokekde/4:4.7.4-1.
> usertags 670208 piuparts
Bug#670208: minetest-common: Unable to upgrade as tool_woodshovel is also part
of minetest 0.3.1+dfsg-2
There were no usertags set.
Usertags are now: piuparts.
> affects 670208 + minetest
Bug #670208 [minetest-common] minetest-common: Unable to upgrade as
tool_woodshovel is also part of minetest 0.3.1+dfsg-2
Added indication that 670208 affects minetest
> found 656586 2.2-2
Bug #656586 [routino-www] fails to purge - rmdir: failed to remove
'/var/lib/routino/data': No such file or directory
Marked as found in versions routino/2.2-2.
> fixed 668748 0.15.23b-1
Bug #668748 {Done: Richard Nelson } [ifetch-tools]
ifetch-tools: unowned files after purge (policy 6.8, 10.8)
Marked as fixed in versions ifetch-tools/0.15.23b-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
656586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656586
668748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668748
669278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669278
670208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670208
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#650653: marked as done (tulip: FTBFS: No rule to make target `doc')
Your message dated Tue, 24 Apr 2012 21:50:01 + with message-id and subject line Bug#650653: fixed in tulip 3.6.0dfsg-2.1 has caused the Debian Bug report #650653, regarding tulip: FTBFS: No rule to make target `doc' 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.) -- 650653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tulip Version: 3.6.0dfsg-2 Severity: serious Justification: fails to build from source tulip FTBFS everywhere: |debian/rules build-indep | make[1]: Entering directory `/build/buildd-tulip_3.6.0dfsg-2-armel-j5X7Y0/tulip-3.6.0dfsg' | #dh build-indep | /usr/bin/make -C obj-* doc | make[2]: Entering directory `/build/buildd-tulip_3.6.0dfsg-2-armel-j5X7Y0/tulip-3.6.0dfsg/obj-arm-linux-gnueabi' | make[2]: *** No rule to make target `doc'. Stop. Full build log: https://buildd.debian.org/status/fetch.php?pkg=tulip&arch=armel&ver=3.6.0dfsg-2&stamp=1318940560 -- Jakub Wilk --- End Message --- --- Begin Message --- Source: tulip Source-Version: 3.6.0dfsg-2.1 We believe that the bug you reported is fixed in the latest version of tulip, which is due to be installed in the Debian FTP archive: libgzstreamtlp-3.6_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/libgzstreamtlp-3.6_3.6.0dfsg-2.1_amd64.deb libogdftlp-3.6_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/libogdftlp-3.6_3.6.0dfsg-2.1_amd64.deb libtulip-3.6_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/libtulip-3.6_3.6.0dfsg-2.1_amd64.deb libtulip-dev_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/libtulip-dev_3.6.0dfsg-2.1_amd64.deb libtulip-ogdf-3.6_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/libtulip-ogdf-3.6_3.6.0dfsg-2.1_amd64.deb libtulip-ogl-3.6_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/libtulip-ogl-3.6_3.6.0dfsg-2.1_amd64.deb libtulip-qt4-3.6_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/libtulip-qt4-3.6_3.6.0dfsg-2.1_amd64.deb tulip-doc_3.6.0dfsg-2.1_all.deb to main/t/tulip/tulip-doc_3.6.0dfsg-2.1_all.deb tulip_3.6.0dfsg-2.1.debian.tar.gz to main/t/tulip/tulip_3.6.0dfsg-2.1.debian.tar.gz tulip_3.6.0dfsg-2.1.dsc to main/t/tulip/tulip_3.6.0dfsg-2.1.dsc tulip_3.6.0dfsg-2.1_amd64.deb to main/t/tulip/tulip_3.6.0dfsg-2.1_amd64.deb 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 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Regis Boudin (supplier of updated tulip 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 23 Apr 2012 22:52:11 +0200 Source: tulip Binary: tulip tulip-doc libtulip-3.6 libtulip-dev libtulip-ogl-3.6 libtulip-qt4-3.6 libtulip-ogdf-3.6 libogdftlp-3.6 libgzstreamtlp-3.6 Architecture: source amd64 all Version: 3.6.0dfsg-2.1 Distribution: unstable Urgency: low Maintainer: Yann Dirson Changed-By: Regis Boudin Description: libgzstreamtlp-3.6 - gzstream shared library, built for Tulip libogdftlp-3.6 - Open Graph Drawing Framework shared library, built for Tulip libtulip-3.6 - Tulip graph library - core runtime libtulip-dev - Tulip graph library - core development files libtulip-ogdf-3.6 - Tulip graph library - OGDF runtime libtulip-ogl-3.6 - Tulip graph library - OpenGL runtime libtulip-qt4-3.6 - Tulip graph library - Qt/OpenGL GUI runtime tulip - System dedicated to the visualization of huge graphs tulip-doc - Documentation for the Tulip graph-visualization system Closes: 650653 662526 667401 Changes: tulip (3.6.0dfsg-2.1) unstable; urgency=low . * Non-maintainer upload. * Fix debian/rules, so the package compiles on the buildds. Closes: #650653. * Add gcc4.7_ftbfs patch to fix FTBFS with GCC 4.7. Closes: #667401. * Update Build-Depends on libpng-dev. Closes: #662526. * Bump debhelper Build-Depends to >= 9, as recommended by lintian. Checksums-Sha1: 9208d2f75a515fcb94ba68e1bdbc21a1ee543999 1852 tulip_3.6.0dfsg-2.1.dsc 3657896271991701e2ec22a31013870b3ad54dcd 23993 tulip_3.6.0dfsg-2.1.debian.tar.gz ce96514e6736ea942e487ecd4211135cad6536b2 7322712 tulip_3.6.0dfsg-2.1_amd64.deb 643cde3b47a150dd70650cd5a17716903e75d0e4 101216166 tulip-doc_3.6.0dfsg-2.1_all.deb 4c9a24e2f3c19ed1cac761eab97579350c9771f2 802488 libtulip-3.6_3.6.0dfsg-2.1_amd64.deb 1044cc1e3dbfdbab94ffdd1378
Bug#670329: argyll: FTBFS everywhere (icoms.h:45:19: fatal error: usb.h: No such file or directory)
Package: argyll Version: 1.4.0-3 Severity: serious Justification: fails to build from source (but built successfully in the past) See https://buildd.debian.org/status/package.php?p=argyll Cheers, Julien signature.asc Description: Digital signature
Bug#670328: gnustep-gui: FTBFS (say.m:17:12: error: variable 'outFile' set but not used [-Werror=unused-but-set-variable])
Source: gnustep-gui Version: 0.20.0-2.1 Severity: serious Justification: fails to build from source (but built successfully in the past) See https://buildd.debian.org/status/package.php?p=gnustep-gui Cheers, Julien signature.asc Description: Digital signature
Bug#669499: marked as done (rakudo: FTBFS: ld: cannot find -licuuc)
Your message dated Tue, 24 Apr 2012 21:22:50 + with message-id and subject line Bug#669499: fixed in rakudo 0.1~2012.01-1 has caused the Debian Bug report #669499, regarding rakudo: FTBFS: ld: cannot find -licuuc 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.) -- 669499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rakudo Version: 0.1~2011.07-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > cc -o src/pmc/perl6_group.so perl6_group.o src/pmc/*.o src/binder/bind.o > -fstack-protector -L/usr/local/lib -shared -L/usr/local/lib > -fstack-protector -fPIC -ldl -lm -lpthread -lcrypt -lrt -lreadline > -Wl,-z,relro -ldl -lm -L/usr/lib -licuuc -licudata -ldl -lm > /usr/bin/ld: cannot find -licuuc > /usr/bin/ld: cannot find -licudata > collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/rakudo_0.1~2011.07-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: rakudo Source-Version: 0.1~2012.01-1 We believe that the bug you reported is fixed in the latest version of rakudo, which is due to be installed in the Debian FTP archive: rakudo_0.1~2012.01-1.debian.tar.gz to main/r/rakudo/rakudo_0.1~2012.01-1.debian.tar.gz rakudo_0.1~2012.01-1.dsc to main/r/rakudo/rakudo_0.1~2012.01-1.dsc rakudo_0.1~2012.01-1_amd64.deb to main/r/rakudo/rakudo_0.1~2012.01-1_amd64.deb rakudo_0.1~2012.01.orig.tar.gz to main/r/rakudo/rakudo_0.1~2012.01.orig.tar.gz 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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessandro Ghedini (supplier of updated rakudo 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 24 Apr 2012 17:04:08 +0200 Source: rakudo Binary: rakudo Architecture: source amd64 Version: 0.1~2012.01-1 Distribution: unstable Urgency: low Maintainer: Debian Rakudo Maintainers Changed-By: Alessandro Ghedini Description: rakudo - Perl 6 implementation on top of Parrot virtual machine Closes: 653240 669499 Changes: rakudo (0.1~2012.01-1) unstable; urgency=low . * New upstream release * Depends on versioned parrot too (Closes: #653240) * Bump debhelper compat level to 9 * Update debian/copyright format as in Debian Policy 3.9.3 * Bump Standards-Version to 3.9.3 * Update upstream copyright years * (Build) depend on nqp too, update parrot version * Build depend on libicu-dev (Closes: #669499) * Email change: Alessandro Ghedini -> gh...@debian.org * Manually depend on parrotapi-X.Y.Z Checksums-Sha1: 642d22e499e94f1ed6bf532770998106ae5fd506 2051 rakudo_0.1~2012.01-1.dsc 2a0eda7af19949bce292dfed5b5d9093ae70a7c7 357676 rakudo_0.1~2012.01.orig.tar.gz 00bdf88b9c6c9c22f074f1214cbb9ea493987333 5713 rakudo_0.1~2012.01-1.debian.tar.gz 3952c908618f99bb24d30975da8f0f3d729ef11c 1986994 rakudo_0.1~2012.01-1_amd64.deb Checksums-Sha256: 90a321e22192faceb11002d654ad9ad1523ab4823e576b9bf0826214e65f3343 2051 rakudo_0.1~2012.01-1.dsc ebe34030e0c2fe02e4c8fc5f8b7dfdfacebbe8c957d7f276406935ea08231b3c 357676 rakudo_0.1~2012.01.orig.tar.gz 9532f01bf92cdcfae37236dca848168648e6a236e36e6e811e6d6bbb0fc302da 5713 rakudo_0.1~2012.01-1.debian.tar.gz a413971c847da38540aa26cf1b5e0ef988445147a3cba9f449de3d8564f52c71 1986994 rakudo_0.1~2012.01-1_amd64.deb Files: f73be42ce526d9aad208c0c7496945f4 2051 interpreters optional rakudo_0.1~2012.01-1.dsc 7ff47aa3712e87a9b47027348f94c892 357676 interpreters optional rakudo_0.1~2012.01.orig.tar.gz ef2e7226ae730cc8c9d6a878e57e1391 5713 interpreters optional rakudo_0.1~2012.01-1.debian.tar.gz
Bug#670291: marked as done (telepathy-glib: FTBFS on non-Linux if $HOME is inaccessible)
Your message dated Tue, 24 Apr 2012 20:56:50 + with message-id and subject line Bug#670291: fixed in telepathy-glib 0.18.1-2 has caused the Debian Bug report #670291, regarding telepathy-glib: FTBFS on non-Linux if $HOME is inaccessible 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.) -- 670291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: telepathy-glib Version: 0.18.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Package builds are not meant to write to $HOME, and some buildds (apparently including fasch for kfreebsd-amd64) enforce this by setting a $HOME which exists but is inaccessible. On Linux, D-Bus does not require access to $HOME, because clients of a DBusServer can prove their identities by using credentials-passing. On kFreeBSD, this is apparently not currently supported, at least by GDBus (from FreeBSD man pages, it should be, but maybe the implementation in GDBus is deficient or wrong?) and clients of the DBusServer are required to prove their identities by writing to ~/.dbus-keyrings. This isn't possible on fasch, causing a FTBFS: https://buildd.debian.org/status/fetch.php?pkg=telepathy-glib&arch=kfreebsd-amd64&ver=0.18.1-1&stamp=1334946724 Because GLib is involved, it might be necessary to set the Debian-specific environment variable G_HOME. S --- End Message --- --- Begin Message --- Source: telepathy-glib Source-Version: 0.18.1-2 We believe that the bug you reported is fixed in the latest version of telepathy-glib, which is due to be installed in the Debian FTP archive: gir1.2-telepathyglib-0.12_0.18.1-2_amd64.deb to main/t/telepathy-glib/gir1.2-telepathyglib-0.12_0.18.1-2_amd64.deb libtelepathy-glib-dev_0.18.1-2_amd64.deb to main/t/telepathy-glib/libtelepathy-glib-dev_0.18.1-2_amd64.deb libtelepathy-glib-doc_0.18.1-2_all.deb to main/t/telepathy-glib/libtelepathy-glib-doc_0.18.1-2_all.deb libtelepathy-glib0-dbg_0.18.1-2_amd64.deb to main/t/telepathy-glib/libtelepathy-glib0-dbg_0.18.1-2_amd64.deb libtelepathy-glib0_0.18.1-2_amd64.deb to main/t/telepathy-glib/libtelepathy-glib0_0.18.1-2_amd64.deb telepathy-glib_0.18.1-2.debian.tar.gz to main/t/telepathy-glib/telepathy-glib_0.18.1-2.debian.tar.gz telepathy-glib_0.18.1-2.dsc to main/t/telepathy-glib/telepathy-glib_0.18.1-2.dsc 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 670...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated telepathy-glib 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 24 Apr 2012 18:05:39 +0100 Source: telepathy-glib Binary: libtelepathy-glib0 libtelepathy-glib-dev libtelepathy-glib0-dbg libtelepathy-glib-doc gir1.2-telepathyglib-0.12 Architecture: source amd64 all Version: 0.18.1-2 Distribution: unstable Urgency: low Maintainer: Debian Telepathy maintainers Changed-By: Simon McVittie Description: gir1.2-telepathyglib-0.12 - GLib Telepathy connection manager library (GObject-Introspection) libtelepathy-glib-dev - GLib Telepathy connection manager library (headers) libtelepathy-glib-doc - GLib Telepathy library (documentation) libtelepathy-glib0 - Telepathy framework - GLib library libtelepathy-glib0-dbg - GLib Telepathy library (debug symbols) Closes: 670291 Changes: telepathy-glib (0.18.1-2) unstable; urgency=low . * Set a fake home directory for the tests, for the benefit of architectures where either GDBus or libdbus doesn't understand credentials-passing, causing D-Bus clients to write to ~/.dbus-keyrings (not allowed on buildds). (Closes: #670291) Checksums-Sha1: 537ce34a61c63d4d615143fa6b2d52d78d483d32 2766 telepathy-glib_0.18.1-2.dsc f49962ceb10952deb75f771b1e92f2536ab77ffc 31864 telepathy-glib_0.18.1-2.debian.tar.gz 164bf1706d7bb63cfa49893a4de1de693a4406ec 844218 libtelepathy-glib0_0.18.1-2_amd64.deb 3f04832437988fb415c3b492efb74f1d2b87074b 1348418 libtelepathy-glib-dev_0.18.1-2_amd64.deb ce9586d1787f0969043255649ec6b45d0ea0afb4 1564038 libtelepathy-glib0-dbg_0.18.1-2_amd64.deb 21605628b920a1eea999b5fcc441660f8dcbc6fc 1393312 libtel
Bug#669514: marked as done (slang2: broken shlibs)
Your message dated Tue, 24 Apr 2012 20:56:23 +
with message-id
and subject line Bug#669514: fixed in slang2 2.2.4-9
has caused the Debian Bug report #669514,
regarding slang2: broken shlibs
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.)
--
669514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slang2
Version: 2.2.4-8
Severity: serious
Hi,
in /var/lib/dpkg/info/libslang2:amd64.shlibs
libslang 2 libslang2 {>= 2.0.7-1}
that should be (), not {}
Lucas
--- End Message ---
--- Begin Message ---
Source: slang2
Source-Version: 2.2.4-9
We believe that the bug you reported is fixed in the latest version of
slang2, which is due to be installed in the Debian FTP archive:
libslang2-dev_2.2.4-9_i386.deb
to main/s/slang2/libslang2-dev_2.2.4-9_i386.deb
libslang2-modules_2.2.4-9_i386.deb
to main/s/slang2/libslang2-modules_2.2.4-9_i386.deb
libslang2-pic_2.2.4-9_i386.deb
to main/s/slang2/libslang2-pic_2.2.4-9_i386.deb
libslang2-udeb_2.2.4-9_i386.udeb
to main/s/slang2/libslang2-udeb_2.2.4-9_i386.udeb
libslang2_2.2.4-9_i386.deb
to main/s/slang2/libslang2_2.2.4-9_i386.deb
slang2_2.2.4-9.debian.tar.gz
to main/s/slang2/slang2_2.2.4-9.debian.tar.gz
slang2_2.2.4-9.dsc
to main/s/slang2/slang2_2.2.4-9.dsc
slsh_2.2.4-9_i386.deb
to main/s/slang2/slsh_2.2.4-9_i386.deb
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 669...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry (supplier of updated slang2 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 23 Apr 2012 21:06:29 +0100
Source: slang2
Binary: libslang2-dev libslang2 libslang2-pic libslang2-udeb slsh
libslang2-modules
Architecture: source i386
Version: 2.2.4-9
Distribution: unstable
Urgency: low
Maintainer: Alastair McKinstry
Changed-By: Alastair McKinstry
Description:
libslang2 - S-Lang programming library - runtime version
libslang2-dev - S-Lang programming library, development version
libslang2-modules - Shared modules for S-Lang language
libslang2-pic - S-Lang programming library, shared library subset kit
libslang2-udeb - S-Lang library for Debian Installer (udeb)
slsh - Interpreter for S-Lang language
Closes: 669514
Changes:
slang2 (2.2.4-9) unstable; urgency=low
.
* Fix wrong parens in control file. Closes: #669514.
Checksums-Sha1:
06478610a9e310595d154e57f28fbeabfece80c4 2041 slang2_2.2.4-9.dsc
418c49ff6257704a96d359a253b9cd3517d3a4c3 17450 slang2_2.2.4-9.debian.tar.gz
747e5d858c47dbbaca64280013b8620162fddac8 597394 libslang2-dev_2.2.4-9_i386.deb
cc92ad19c100bf65fe5c19374bbaebcbf9f2774b 573032 libslang2_2.2.4-9_i386.deb
743bd277ebc79ed8f075b3702f807ee21c4300df 545302 libslang2-pic_2.2.4-9_i386.deb
ad6fb885a505fc69ccf1bf10d6209d1b2037919a 355102
libslang2-udeb_2.2.4-9_i386.udeb
dcfbfa37a7eb7d786d272cba694a8d2ba17c0176 183072 slsh_2.2.4-9_i386.deb
5a1705f2eed6fb67710057e09495a876e92405ba 136374
libslang2-modules_2.2.4-9_i386.deb
Checksums-Sha256:
a6905aca4b1bea6da8d50c84d68f3118ea3c39456fd1b250322bc65dae1e2744 2041
slang2_2.2.4-9.dsc
8b62c3fcadd8412def00758468398c71da52ce47c0c425efe09c686f23575986 17450
slang2_2.2.4-9.debian.tar.gz
0445c22770884b37321b43c0e811a097ab3c8758d15acac55007f8adebc10752 597394
libslang2-dev_2.2.4-9_i386.deb
6beda6c0745773b269548f78e507a696ff5adf362eb69ee29d0cc8c637742493 573032
libslang2_2.2.4-9_i386.deb
bff52a0d0c7f135b3cafea9f24505fcf45dd2e5216b8fb806315951487f6824c 545302
libslang2-pic_2.2.4-9_i386.deb
78fc640cce429aa9dee8dcaf35329bdac61a765e5242825356573b82d65a4517 355102
libslang2-udeb_2.2.4-9_i386.udeb
239f0495ac64147db6745a97f89eea2ea29ac6d1b6d5fc717d22bfebacc1f58c 183072
slsh_2.2.4-9_i386.deb
446c0db8076046ee2a8dfc76410a5b4821a87e72bb2fd690cccfef194fc50392 136374
libslang2-modules_2.2.4-9_i386.deb
Files:
fedac2f1bc17e314f0597f3469904296 2041 devel optional slang2_2.2.4-9.dsc
418cac1bd4715d8cf204e4c0fd4d0364 17450 devel optional
slang2_2.2.4-9.debian.tar.gz
fce2cb7faad771b6eb0eaaf0d3f0548c 597394 libdevel optional
libslang2-dev_2.2.4-9_i386.deb
91ae47c7061221326bc751b033c8f657 573032 libs required
libslang2_2.2.4-9_i386.deb
f
Bug#669514: marked as done (slang2: broken shlibs)
Your message dated Tue, 24 Apr 2012 20:56:06 +
with message-id
and subject line Bug#669514: fixed in slang2 2.2.4-8.1
has caused the Debian Bug report #669514,
regarding slang2: broken shlibs
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.)
--
669514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slang2
Version: 2.2.4-8
Severity: serious
Hi,
in /var/lib/dpkg/info/libslang2:amd64.shlibs
libslang 2 libslang2 {>= 2.0.7-1}
that should be (), not {}
Lucas
--- End Message ---
--- Begin Message ---
Source: slang2
Source-Version: 2.2.4-8.1
We believe that the bug you reported is fixed in the latest version of
slang2, which is due to be installed in the Debian FTP archive:
libslang2-dev_2.2.4-8.1_amd64.deb
to main/s/slang2/libslang2-dev_2.2.4-8.1_amd64.deb
libslang2-modules_2.2.4-8.1_amd64.deb
to main/s/slang2/libslang2-modules_2.2.4-8.1_amd64.deb
libslang2-pic_2.2.4-8.1_amd64.deb
to main/s/slang2/libslang2-pic_2.2.4-8.1_amd64.deb
libslang2-udeb_2.2.4-8.1_amd64.udeb
to main/s/slang2/libslang2-udeb_2.2.4-8.1_amd64.udeb
libslang2_2.2.4-8.1_amd64.deb
to main/s/slang2/libslang2_2.2.4-8.1_amd64.deb
slang2_2.2.4-8.1.debian.tar.gz
to main/s/slang2/slang2_2.2.4-8.1.debian.tar.gz
slang2_2.2.4-8.1.dsc
to main/s/slang2/slang2_2.2.4-8.1.dsc
slsh_2.2.4-8.1_amd64.deb
to main/s/slang2/slsh_2.2.4-8.1_amd64.deb
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 669...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Cristau (supplier of updated slang2 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 24 Apr 2012 22:02:39 +0200
Source: slang2
Binary: libslang2-dev libslang2 libslang2-pic libslang2-udeb slsh
libslang2-modules
Architecture: source amd64
Version: 2.2.4-8.1
Distribution: unstable
Urgency: low
Maintainer: Alastair McKinstry
Changed-By: Julien Cristau
Description:
libslang2 - S-Lang programming library - runtime version
libslang2-dev - S-Lang programming library, development version
libslang2-modules - Shared modules for S-Lang language
libslang2-pic - S-Lang programming library, shared library subset kit
libslang2-udeb - S-Lang library for Debian Installer (udeb)
slsh - Interpreter for S-Lang language
Closes: 669514
Changes:
slang2 (2.2.4-8.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix broken shlibs (closes: #669514). While a parenthesis and a curly
bracket look similar, they're actually different characters. Who knew?
Checksums-Sha1:
5531689b2266046874f1d23e0148801fb0b974ef 2049 slang2_2.2.4-8.1.dsc
92ad7400ecc1457a9c7ba799cd2cf279945fd4d7 17510 slang2_2.2.4-8.1.debian.tar.gz
4ad7409f8c33765a535318f683cd9e5094af6190 627518
libslang2-dev_2.2.4-8.1_amd64.deb
ed3855e87a7a195f79987273dd9320bbaf826708 575150 libslang2_2.2.4-8.1_amd64.deb
65936dded8d47f5f3730077f10dc13ac6a4c4a19 537800
libslang2-pic_2.2.4-8.1_amd64.deb
0399155feb893e7803ceeb8894ef838853cb5ce3 356650
libslang2-udeb_2.2.4-8.1_amd64.udeb
1f1b9a8bb9466d91de8d520bfe431e48d11e1419 182434 slsh_2.2.4-8.1_amd64.deb
676d9e5ca768956b451bb3b94a6c8b6d59e5c5c4 141826
libslang2-modules_2.2.4-8.1_amd64.deb
Checksums-Sha256:
0cdcd5b98c88c271dac07e60dac5d4d2deec1bdf35baeff39027b87e1944fe4d 2049
slang2_2.2.4-8.1.dsc
531abd0ff5a9803fc53694c606e2c9c49fceaf9d74795179ca782718ab0aed01 17510
slang2_2.2.4-8.1.debian.tar.gz
078ce825d1a8fd4e559abac4fefc92648c4376ec472e4df7597e2dc2da4e9225 627518
libslang2-dev_2.2.4-8.1_amd64.deb
062f0dd84521cf72a2676179e5de07af5c35eaca5edf74199c8462fc6f2fa3c5 575150
libslang2_2.2.4-8.1_amd64.deb
4c4026d7c7ca43abd7f2f1a09b3b3966429f63cf43586c72dc4416551583a516 537800
libslang2-pic_2.2.4-8.1_amd64.deb
6eb6ad68785a771eb791c73ce905e501179f91cb479ca545bd3a13f9162e238d 356650
libslang2-udeb_2.2.4-8.1_amd64.udeb
2dea5462d965083f375e2a8807a9ca8cbafd7413494f21da7f178661899da259 182434
slsh_2.2.4-8.1_amd64.deb
c673326f31c01a0e61acc45a7d27faa1143186c8a34e3140cbd937ee47714574 141826
libslang2-modules_2.2.4-8.1_amd64.deb
Files:
74be5026cf2f3a7dd5c181b4abb6b7e7 2049 devel optional slang2_2.2.4-8.1.dsc
4128750b3300dc610bedccee1ff439c3 17510 deve
Bug#650653: NMU 3.6.0dfsg-2.1
Hi,
As tulip has FTBFS on all buildds for over 220 days, and the remaining
arch is not installable either, I'm about to upload a NMU fixing the
build, which includes also fixes for the FTBFS with GCC 4.7 (#667401),
as well as updating the libpng-dev build-dependency (#662526).
Please find the diff to -2.1 attached.
Thanks,
Regis
diff -Nru tulip-3.6.0dfsg/debian/changelog tulip-3.6.0dfsg/debian/changelog
--- tulip-3.6.0dfsg/debian/changelog 2011-09-09 22:58:34.0 +0200
+++ tulip-3.6.0dfsg/debian/changelog 2012-04-23 22:52:44.0 +0200
@@ -1,3 +1,13 @@
+tulip (3.6.0dfsg-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix debian/rules, so the package compiles on the buildds. Closes: #650653.
+ * Add gcc4.7_ftbfs patch to fix FTBFS with GCC 4.7. Closes: #667401.
+ * Update Build-Depends on libpng-dev. Closes: #662526.
+ * Bump debhelper Build-Depends to >= 9, as recommended by lintian.
+
+ -- Regis Boudin Mon, 23 Apr 2012 22:52:11 +0200
+
tulip (3.6.0dfsg-2) unstable; urgency=low
* Don't build docs for tulip-doc from build-arch, move java packages,
diff -Nru tulip-3.6.0dfsg/debian/control tulip-3.6.0dfsg/debian/control
--- tulip-3.6.0dfsg/debian/control 2011-09-05 22:43:32.0 +0200
+++ tulip-3.6.0dfsg/debian/control 2012-04-23 22:53:57.0 +0200
@@ -2,7 +2,7 @@
Section: graphics
Priority: optional
Maintainer: Yann Dirson
-Build-Depends: debhelper (>> 8), cmake, libqt4-dev, qt4-dev-tools, freeglut3-dev, docbook-to-man, libgl1-mesa-dev | libgl-dev, dh-buildinfo, libfreetype6-dev, libxml2-dev, libgle3-dev, libxml2-utils, graphviz, libjpeg-dev, libpng12-dev, libftgl-dev, libglew1.5-dev, libqt4-opengl-dev
+Build-Depends: debhelper (>= 9), cmake, libqt4-dev, qt4-dev-tools, freeglut3-dev, docbook-to-man, libgl1-mesa-dev | libgl-dev, dh-buildinfo, libfreetype6-dev, libxml2-dev, libgle3-dev, libxml2-utils, graphviz, libjpeg-dev, libpng-dev, libftgl-dev, libglew1.5-dev, libqt4-opengl-dev
Build-Depends-Indep: default-jre-headless, libsaxon-java, libxml-commons-resolver1.1-java, docbook-xsl, doxygen
Homepage: http://tulip-software.org/
Standards-Version: 3.9.1
diff -Nru tulip-3.6.0dfsg/debian/patches/gcc4.7_ftbfs tulip-3.6.0dfsg/debian/patches/gcc4.7_ftbfs
--- tulip-3.6.0dfsg/debian/patches/gcc4.7_ftbfs 1970-01-01 01:00:00.0 +0100
+++ tulip-3.6.0dfsg/debian/patches/gcc4.7_ftbfs 2012-04-23 21:27:50.0 +0200
@@ -0,0 +1,15 @@
+Description: Fix FTBFS with GCC 4.7
+ Add a missing include in the headers.
+Author: Regis Boudin
+
+--- tulip-3.6.0dfsg.orig/library/tulip/include/tulip/SimpleVector.h
tulip-3.6.0dfsg/library/tulip/include/tulip/SimpleVector.h
+@@ -21,6 +21,8 @@
+ #ifndef _SIMPLE_VECTOR_H_
+ #define _SIMPLE_VECTOR_H_
+
++#include
++
+ namespace tlp {
+
+ // SimpleVector
diff -Nru tulip-3.6.0dfsg/debian/patches/series tulip-3.6.0dfsg/debian/patches/series
--- tulip-3.6.0dfsg/debian/patches/series 2011-09-09 22:57:53.0 +0200
+++ tulip-3.6.0dfsg/debian/patches/series 2012-04-23 21:26:37.0 +0200
@@ -6,3 +6,4 @@
0006-Use-system-FTGL-not-the-one-shipped-in-thirtparty.patch
0007-Disable-python-binding.patch
0008-Use-Debian-packaged-jars.patch
+gcc4.7_ftbfs
diff -Nru tulip-3.6.0dfsg/debian/rules tulip-3.6.0dfsg/debian/rules
--- tulip-3.6.0dfsg/debian/rules 2011-09-09 23:08:06.0 +0200
+++ tulip-3.6.0dfsg/debian/rules 2012-04-23 19:32:20.0 +0200
@@ -7,26 +7,23 @@
override_dh_auto_configure:
dh_auto_configure -- -DCMAKE_SKIP_RPATH:BOOL=YES
-build-arch:
- dh $@ --parallel
+override_dh_auto_build-arch:
+ dh_auto_build -a --parallel
docbook-to-man debian/tulip.sgml > debian/tulip.1
-build-indep:
- #dh $@
+override_dh_auto_build-indep:
+ dh_auto_build -i
$(MAKE) -C obj-* doc
-install-indep: build-indep
- dh_prep -i
+override_dh_auto_install-indep:
+ dh_auto_install -i -- -C docs
mkdir -p debian/tmp/usr/share/doc/tulip-doc
set -e; for d in common userHandbook developerHandbook doxygen; do \
cp -a obj-*/docs/$$d debian/tmp/usr/share/doc/tulip-doc/ ;\
done
- dh_auto_install -- -C docs
- dh $@
-install-arch: build-arch
- dh_prep -a
+override_dh_auto_install-arch:
+ dh_auto_install -a
install -D debian/tulip.1 debian/tmp/usr/share/man/man1/tulip.1
- dh $@
override_dh_install:
dh_install --fail-missing
@@ -36,4 +33,3 @@
rm -f debian/tulip.1
rm -rf docs/doxygen/xml
-binary: binary-arch binary-indep ;
Bug#669566: marked as done (jackd2: FTBFS[kfreebsd]: waf configuration fails)
Your message dated Tue, 24 Apr 2012 20:50:49 +
with message-id
and subject line Bug#669566: fixed in jackd2 1.9.8~dfsg.3+20120418gitf82ec715-2
has caused the Debian Bug report #669566,
regarding jackd2: FTBFS[kfreebsd]: waf configuration fails
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.)
--
669566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jackd2
Version: 1.9.8~dfsg.3+20120418gitf82ec715
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the
past)
Hi,
Attached is the complete config.log file which may help to understand
this failure building jackd2 on GNU/kFreeBSD (or Hurd?) :
> ./waf configure --prefix=/usr --classic
> Setting top to :
> /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715
> Setting out to :
> /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/build
> Checking for header samplerate.h : not found
> The configuration failed
There does not seem to be any problem with samplerate.h (I'm able to
compile the testcase by hand), but rather, some problem with waf means
it can't compile anything at all. See the attached.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
# project jack (1.9.9) configured on Thu Apr 19 22:51:47 2012 by
# waf 1.6.11 (abi 98, python 20703c2 on gnukfreebsd8)
# using ./waf configure --prefix=/usr --classic
#
Setting top to
/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715
Setting out to
/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/build
Checking for header samplerate.h
==>
#include
int main() {
return 0;
}
<==
from /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/common: Test does not build: Traceback (most recent call last):
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Tools/c_config.py", line 445, in run_c_code
bld.compile()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Build.py", line 182, in compile
self.producer.start()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Runner.py", line 149, in start
self.refill_task_list()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Runner.py", line 98, in refill_task_list
self.outstanding.extend(self.biter.next())
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Build.py", line 396, in get_build_iterator
self.post_group()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Build.py", line 358, in post_group
f()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/extras/compat15.py", line 114, in post
return old_post(self)
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/TaskGen.py", line 110, in post
v()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/TaskGen.py", line 229, in process_source
self.get_hook(node)(self,node)
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/TaskGen.py", line 121, in get_hook
raise Errors.WafError("File %r has no mapping in %r (did you forget to load a waf tool?)"%(node,task_gen.mappings.keys()))
WafError: File /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/build/.conf_check_58def3ddbbfadb33f63d2b9b57b93f9c/test.c has no mapping in ['.obj', '.pc.in', '.o'] (did you forget to load a waf tool?)
not found
from /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/common: The configuration failed
--- End Message ---
--- Begin Message ---
Source: jackd2
Source-Version: 1.9.8~dfsg.3+20120418gitf82ec715-2
We believe that the bug you reported is fixed in the latest version of
jackd2, which is due to be installed in the Debian FTP archive:
jackd2-firewire_1.9.8~dfsg.3+20120418gitf82ec715-2_amd64.deb
to main/j/jackd2/jackd2-firewire_1.9.8~dfsg.3+20120418gitf82ec715-2_amd64.deb
jackd2_1.9.8~dfsg.3+20120418gitf82ec715-2.debian.tar.gz
to main/j/jackd2/jackd2_1.9.8~dfsg.3+20120418gitf82ec715-2.debian.tar.gz
jackd2_1.9.8~dfsg.3+20120418gitf82ec715-2.dsc
to main/j/jackd2/jackd2_1.9.8~dfsg.3+20120418gitf82ec715-2.dsc
jackd2_1.9.8~dfsg.3+20120418gitf82ec715-2_amd64.deb
to main/j/jackd2/jackd2_1.9.8~dfsg.3+20120418gitf82ec715-2_amd64.deb
libjack-jackd2-0_1.9.8~dfsg.3+20120418gitf82ec715-2_amd64.deb
to main/
Bug#669566: marked as done (jackd2: FTBFS[kfreebsd]: waf configuration fails)
Your message dated Tue, 24 Apr 2012 20:51:09 +
with message-id
and subject line Bug#669566: fixed in jackd2 1.9.8~dfsg.3+20120418gitf82ec715-3
has caused the Debian Bug report #669566,
regarding jackd2: FTBFS[kfreebsd]: waf configuration fails
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.)
--
669566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jackd2
Version: 1.9.8~dfsg.3+20120418gitf82ec715
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the
past)
Hi,
Attached is the complete config.log file which may help to understand
this failure building jackd2 on GNU/kFreeBSD (or Hurd?) :
> ./waf configure --prefix=/usr --classic
> Setting top to :
> /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715
> Setting out to :
> /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/build
> Checking for header samplerate.h : not found
> The configuration failed
There does not seem to be any problem with samplerate.h (I'm able to
compile the testcase by hand), but rather, some problem with waf means
it can't compile anything at all. See the attached.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
# project jack (1.9.9) configured on Thu Apr 19 22:51:47 2012 by
# waf 1.6.11 (abi 98, python 20703c2 on gnukfreebsd8)
# using ./waf configure --prefix=/usr --classic
#
Setting top to
/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715
Setting out to
/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/build
Checking for header samplerate.h
==>
#include
int main() {
return 0;
}
<==
from /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/common: Test does not build: Traceback (most recent call last):
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Tools/c_config.py", line 445, in run_c_code
bld.compile()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Build.py", line 182, in compile
self.producer.start()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Runner.py", line 149, in start
self.refill_task_list()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Runner.py", line 98, in refill_task_list
self.outstanding.extend(self.biter.next())
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Build.py", line 396, in get_build_iterator
self.post_group()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/Build.py", line 358, in post_group
f()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/extras/compat15.py", line 114, in post
return old_post(self)
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/TaskGen.py", line 110, in post
v()
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/TaskGen.py", line 229, in process_source
self.get_hook(node)(self,node)
File "/home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/waflib/TaskGen.py", line 121, in get_hook
raise Errors.WafError("File %r has no mapping in %r (did you forget to load a waf tool?)"%(node,task_gen.mappings.keys()))
WafError: File /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/build/.conf_check_58def3ddbbfadb33f63d2b9b57b93f9c/test.c has no mapping in ['.obj', '.pc.in', '.o'] (did you forget to load a waf tool?)
not found
from /home/steven/jackd2-1.9.8~dfsg.3+20120418gitf82ec715/common: The configuration failed
--- End Message ---
--- Begin Message ---
Source: jackd2
Source-Version: 1.9.8~dfsg.3+20120418gitf82ec715-3
We believe that the bug you reported is fixed in the latest version of
jackd2, which is due to be installed in the Debian FTP archive:
jackd2-firewire_1.9.8~dfsg.3+20120418gitf82ec715-3_amd64.deb
to main/j/jackd2/jackd2-firewire_1.9.8~dfsg.3+20120418gitf82ec715-3_amd64.deb
jackd2_1.9.8~dfsg.3+20120418gitf82ec715-3.debian.tar.gz
to main/j/jackd2/jackd2_1.9.8~dfsg.3+20120418gitf82ec715-3.debian.tar.gz
jackd2_1.9.8~dfsg.3+20120418gitf82ec715-3.dsc
to main/j/jackd2/jackd2_1.9.8~dfsg.3+20120418gitf82ec715-3.dsc
jackd2_1.9.8~dfsg.3+20120418gitf82ec715-3_amd64.deb
to main/j/jackd2/jackd2_1.9.8~dfsg.3+20120418gitf82ec715-3_amd64.deb
libjack-jackd2-0_1.9.8~dfsg.3+20120418gitf82ec715-3_amd64.deb
to main/
Processed: Re: [xml/sgml-pkgs] Bug#668672: libxml2: FTBFS: mv: cannot stat, `debian/tmp/usr/share/aclocal/libxml.m4': No such file or directory
Processing commands for cont...@bugs.debian.org:
> Found 668672 2.7.8.dfsg-7
Bug #668672 {Done: Aron Xu } [src:libxml2] libxml2: FTBFS: mv:
cannot stat `debian/tmp/usr/share/aclocal/libxml.m4': No such file or directory
Marked as found in versions libxml2/2.7.8.dfsg-7.
> Thanks
Stopping processing here.
Please contact me if you need assistance.
--
668672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668672
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#670317: openssl: ASN1 BIO incomplete fix (CVE-2012-2131)
Source: openssl Version: 0.9.8o-4squeeze11 Severity: grave Tags: security Justification: user security hole -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi It was announced that the fix for CVE-2012-2110 was incomplete [1]. It was assignet CVE-2012-2131 to this. Upstream CVS contains a fix for this at [2]. [1]: http://marc.info/?l=openssl-dev&m=133525318514423&w=2 [2]: http://cvs.openssl.org/chngview?cn=22479 Regards, Salvatore - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPlwyhAAoJEHidbwV/2GP+ETQP/2snwLPjocPYH56uRXZx5Ec9 WVjcn236/O4+rw5J3nCWjRBNOETxlkMaH/zUjLcfMEM4h4g3ST0ZRKIoi9qSJSvG CDS5/yGUYeIAr1D4QVLuF5lkfXICiDfB8Olykeq1eIGqDijmQNLI6KEnKdefW2Du 28KVE8fM014c3/+mJGD3ORb/aimfnp+htTEFCReKBxA3V1urrVrFmq/vjqSjtlHe ySIN2Wmmg+okx/s10l5B4h2MAMV0ipmjCqFqskTim3N1C9DLRXnONbY56Fn0UbRj IYBcuJ6Of686G5PFuIBLhrHRtgba1y0eVtMZNjlgcINcPsJNqShlUojY7kUTw/lL J4LzHJBLTwa6Ki1jhgUGCKlPbdMmAh2yoFh/XzOMZSAMaYJmQkaxupjjjkmKBefs jB6687mX+aLghoyAUbEnfFLZFFR2RED8Ddyt1c5xBKRNJoyC0QAaDK2flFSzuLao vXfYX98Hs4FVu2I/wyCoJg5gBayS3nx6lPiKbqOvQGiwEAJHdLRYBkfd28YhZwqI ZXj2QhKexQ+3A6oA0OzC9zjqLP/uQyUAEk0Z1o2tdvHvZXEyMZoMy6jA6QxgrrE4 MVy1x3ORMKE32qv+nqIxZF7B6vMssFQCyCT2RSGUBJu8vc4bknXZfLGXm5QLB5M8 kZ0vd+2F6Pw9W/ZKuo6m =YBqH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668457: [Monotone-debian] [Monotone-devel] Monotone tests failing under Debian automated building
Package: monotone Version: 1.0-4 Tags: patch Hi, On 04/24/2012 04:04 PM, Francis Russell wrote: > Ha, I've found it! monotone appears to be rewriting pluses to spaces in > its URLs: Yeah, monotone expects a correctly escaped URL as argument for the clone and netsync commands. But the test suite didn't expect parent paths that require escaping so far. I committed a fix upstream [1]. The corresponding patch is attached. Regards Markus Wanner [1] rev a0ed177b60caee5cf304c01d83e75812af1225e1, see https://code.monotone.ca/p/monotone/source/commit/a0ed177b60caee5cf304c01d83e75812af1225e1/ mtn-testsuite-fix.diff.gz Description: GNU Zip compressed data
Processed: slang2: diff for NMU version 2.2.4-8.1
Processing commands for cont...@bugs.debian.org: > tags 669514 + patch Bug #669514 [src:slang2] slang2: broken shlibs Added tag(s) patch. > tags 669514 + pending Bug #669514 [src:slang2] slang2: broken shlibs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 669514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669514 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#669514: slang2: diff for NMU version 2.2.4-8.1
tags 669514 + patch
tags 669514 + pending
thanks
Dear maintainer,
I've prepared an NMU for slang2 (versioned as 2.2.4-8.1) and
will upload it in a minute. Please find the diff attached.
Cheers,
Julien
diff -Nru slang2-2.2.4/debian/changelog slang2-2.2.4/debian/changelog
--- slang2-2.2.4/debian/changelog 2012-04-11 15:28:17.0 +0200
+++ slang2-2.2.4/debian/changelog 2012-04-24 22:02:44.0 +0200
@@ -1,3 +1,11 @@
+slang2 (2.2.4-8.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix broken shlibs (closes: #669514). While a parenthesis and a curly
+bracket look similar, they're actually different characters. Who knew?
+
+ -- Julien Cristau Tue, 24 Apr 2012 22:02:39 +0200
+
slang2 (2.2.4-8) unstable; urgency=low
* Fix broken multiarch in libslang2-modules
diff -Nru slang2-2.2.4/debian/rules slang2-2.2.4/debian/rules
--- slang2-2.2.4/debian/rules 2012-04-11 15:31:22.0 +0200
+++ slang2-2.2.4/debian/rules 2012-04-24 22:01:45.0 +0200
@@ -41,7 +41,7 @@
dh_installchangelogs -a changes.txt
override_dh_makeshlibs:
- dh_makeshlibs -a -V "libslang2 {>= 2.0.7-1}" --add-udeb="libslang2-udeb"
+ dh_makeshlibs -a -V "libslang2 (>= 2.0.7-1)" --add-udeb="libslang2-udeb"
override_dh_compress:
dh_compress -a -X.sl -Xslangfun.txt
signature.asc
Description: Digital signature
Bug#670313: linkchecker: FTBFS when not building arch-all linkchecker-web package
Source: linkchecker Version: 7.7-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of linkchecker (as on the autobuilders) covering only its architecture-dependent linkchecker binary package fail because they still try to populate debian/linkchecker-web, which doesn't exist: install -m 644 cgi-bin/lconline/*.html /.../linkchecker-7.7/debian/linkchecker-web/usr/share/linkchecker/lconline install: cannot create regular file `/.../linkchecker-7.7/debian/linkchecker-web/usr/share/linkchecker/lconline': No such file or directory make[1]: *** [override_dh_auto_install] Error 1 make[1]: Leaving directory `/.../linkchecker-7.7' make: *** [binary-arch] Error 2 Could you please conditionalize any such commands appropriately? (In this case, I'd also suggest installing to a relative path, as there's no need to specify an absolute one; that's just a matter of taste, though.) You can test the fix by running dpkg-buildpackage or your favorite wrapper with -B. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669724: marked as done (lxpanel: FTBFS[kfreebsd]: netstat plugin requires wireless-tools-devel)
Your message dated Tue, 24 Apr 2012 19:18:58 + with message-id and subject line Bug#669724: fixed in lxpanel 0.5.9-2 has caused the Debian Bug report #669724, regarding lxpanel: FTBFS[kfreebsd]: netstat plugin requires wireless-tools-devel 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.) -- 669724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lxpanel Version: 0.5.9-1 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: checking iwlib.h usability... no checking iwlib.h presence... no checking for iwlib.h... no configure: error: netstat plugin requires wireless-tools-devel Full build log at https://buildd.debian.org/status/fetch.php?pkg=lxpanel&arch=kfreebsd-i386&ver=0.5.9-1&stamp=1334939666 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer --- End Message --- --- Begin Message --- Source: lxpanel Source-Version: 0.5.9-2 We believe that the bug you reported is fixed in the latest version of lxpanel, which is due to be installed in the Debian FTP archive: lxpanel-dev_0.5.9-2_i386.deb to main/l/lxpanel/lxpanel-dev_0.5.9-2_i386.deb lxpanel_0.5.9-2.debian.tar.xz to main/l/lxpanel/lxpanel_0.5.9-2.debian.tar.xz lxpanel_0.5.9-2.dsc to main/l/lxpanel/lxpanel_0.5.9-2.dsc lxpanel_0.5.9-2_i386.deb to main/l/lxpanel/lxpanel_0.5.9-2_i386.deb 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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated lxpanel 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 24 Apr 2012 20:59:52 +0200 Source: lxpanel Binary: lxpanel lxpanel-dev Architecture: source i386 Version: 0.5.9-2 Distribution: unstable Urgency: low Maintainer: Debian LXDE Maintainers Changed-By: Daniel Baumann Description: lxpanel- LXDE panel lxpanel-dev - LXDE panel (development) Closes: 669724 Changes: lxpanel (0.5.9-2) unstable; urgency=low . * Omitting netstat plugin on non-linux, requires wireless-tools (Closes: #669724). Checksums-Sha1: f08f015ee1fe710c097dd28892f4c156ec60aac6 1536 lxpanel_0.5.9-2.dsc d5355fdd0978f4fb7d7ca0a9abf2ad79ce5cbbb4 11864 lxpanel_0.5.9-2.debian.tar.xz 7894496907c902b9c3bb02bfad218816e830ca74 420660 lxpanel_0.5.9-2_i386.deb ad604d18ed201f27f9ece980016cfae9b405f6c6 12778 lxpanel-dev_0.5.9-2_i386.deb Checksums-Sha256: 0dedcdc3cae751f4ad0f88add59741b3163351c2edf9c00b816af422ef4bfb20 1536 lxpanel_0.5.9-2.dsc 7d42d2c3846caa48390bf9c45ce0f50d9b207a15f9ae1138194afffaff78e479 11864 lxpanel_0.5.9-2.debian.tar.xz 6d9ef2142df3c5498239aef7815ac155948fede68d21bab9fd3c7c111611c8cb 420660 lxpanel_0.5.9-2_i386.deb fe92642685de81cf9ecd020a4e9b8a183175fb057c5c9888a1a25baa7aef1bc3 12778 lxpanel-dev_0.5.9-2_i386.deb Files: 45cf1428f550c7453af984fb49136669 1536 x11 optional lxpanel_0.5.9-2.dsc b1033e24a15aab1d706e2a4ac5b45ad8 11864 x11 optional lxpanel_0.5.9-2.debian.tar.xz 47ba07e40dd34797a848f06c4588504b 420660 x11 optional lxpanel_0.5.9-2_i386.deb e1f2d6d564ad515bce9e856176ba1251 12778 x11 optional lxpanel-dev_0.5.9-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk+W+UkACgkQ+C5cwEsrK54/cgCgmYJKF2A61Xs4I+Vws7cfgZDv BLkAn3niLL1vZ0e38QTCEIwMTyJJuRZ8 =F2bJ -END PGP SIGNATURE- --- End Message ---
Bug#668493: marked as done (drizzle: FTBFS on kfreeBSD-*)
Your message dated Tue, 24 Apr 2012 19:18:39 + with message-id and subject line Bug#668493: fixed in drizzle 1:7.1.33-stable-2 has caused the Debian Bug report #668493, regarding drizzle: FTBFS on kfreeBSD-* 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.) -- 668493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:drizzle Version: 1:7.1.32-rc-1 Severity: serious Recording the FTBFS on kfreeBSD. Logs: https://buildd.debian.org/status/fetch.php?pkg=drizzle&arch=kfreebsd-amd64&ver=1%3A7.1.32-rc-1&stamp=1334051953 https://buildd.debian.org/status/fetch.php?pkg=drizzle&arch=kfreebsd-i386&ver=1%3A7.1.32-rc-1&stamp=1334052115 Reason is that BSD does not support O_CLOEXEC. The bug has been filed upstream at https://bugs.launchpad.net/drizzle/+bug/978007 coldtobi -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.4 (SMP w/3 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Source: drizzle Source-Version: 1:7.1.33-stable-2 We believe that the bug you reported is fixed in the latest version of drizzle, which is due to be installed in the Debian FTP archive: drizzle-client_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-client_7.1.33-stable-2_amd64.deb drizzle-dbg_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-dbg_7.1.33-stable-2_amd64.deb drizzle-dev-doc_7.1.33-stable-2_all.deb to main/d/drizzle/drizzle-dev-doc_7.1.33-stable-2_all.deb drizzle-doc_7.1.33-stable-2_all.deb to main/d/drizzle/drizzle-doc_7.1.33-stable-2_all.deb drizzle-plugin-auth-file_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-auth-file_7.1.33-stable-2_amd64.deb drizzle-plugin-auth-http_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-auth-http_7.1.33-stable-2_amd64.deb drizzle-plugin-auth-ldap_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-auth-ldap_7.1.33-stable-2_amd64.deb drizzle-plugin-auth-pam_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-auth-pam_7.1.33-stable-2_amd64.deb drizzle-plugin-auth-schema_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-auth-schema_7.1.33-stable-2_amd64.deb drizzle-plugin-debug_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-debug_7.1.33-stable-2_amd64.deb drizzle-plugin-dev_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-dev_7.1.33-stable-2_amd64.deb drizzle-plugin-gearman-udf_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-gearman-udf_7.1.33-stable-2_amd64.deb drizzle-plugin-http-functions_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-http-functions_7.1.33-stable-2_amd64.deb drizzle-plugin-js_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-js_7.1.33-stable-2_amd64.deb drizzle-plugin-json-server_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-json-server_7.1.33-stable-2_amd64.deb drizzle-plugin-logging-gearman_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-logging-gearman_7.1.33-stable-2_amd64.deb drizzle-plugin-logging-query_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-logging-query_7.1.33-stable-2_amd64.deb drizzle-plugin-perf-dictionary_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-perf-dictionary_7.1.33-stable-2_amd64.deb drizzle-plugin-query-log_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-query-log_7.1.33-stable-2_amd64.deb drizzle-plugin-rabbitmq_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-rabbitmq_7.1.33-stable-2_amd64.deb drizzle-plugin-regex-policy_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-regex-policy_7.1.33-stable-2_amd64.deb drizzle-plugin-simple-user-policy_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-simple-user-policy_7.1.33-stable-2_amd64.deb drizzle-plugin-slave_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle-plugin-slave_7.1.33-stable-2_amd64.deb drizzle_7.1.33-stable-2.debian.tar.gz to main/d/drizzle/drizzle_7.1.33-stable-2.debian.tar.gz drizzle_7.1.33-stable-2.dsc to main/d/drizzle/drizzle_7.1.33-stable-2.dsc drizzle_7.1.33-stable-2_amd64.deb to main/d/drizzle/drizzle_7.1.33-stable-2_amd64.deb libdrizzle-dbg_7.1.33-stable-2_amd64.deb to main/d/drizzle/libdrizzle-dbg_7.1.33-stable-2_amd64.deb libdrizzle-dev_7.1.33-stable-2_all.deb to main/d/drizzle/libdrizzle
Bug#666648: slime: FTBFS: mkdir: cannot create directory `././sbuild-nonexistent': Permission denied
> "CE" == Christoph Egger writes: CE> This one looks like writing to $HOME which is not allowed and CE> will not fail in a cowbuilder environment normally. Would be CE> easy to test building with HOME=/something-not-existing Thanks for explanation, indeed it's the case. I'll try to set HOME to some of the package build directories as a workaround. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 660078, tagging 669537
Processing commands for cont...@bugs.debian.org: > tags 660078 + pending Bug #660078 [apparmor-notify] apparmor-notify: unnecessarily forbids usage to most users with misleading error message Added tag(s) pending. > tags 669537 + pending Bug #669537 [src:apparmor] apparmor: FTBFS: pdflatex fails Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 660078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660078 669537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669537 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#670304: condor: DO NOT MIGRATE YET
Source: condor Version: 7.7.6~dfsg.1-1 Severity: serious This bug is only here to prevent migration of Condor to testing before a 7.8 series package has been uploaded. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670208: minetest-common: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/minetest/tool_woodshovel.png
Package: minetest-common Version: 0.3.1+dfsg-3 Followup-For: Bug #670208 Hi, during a test with piuparts I noticed your package fails to upgrade from 'DISTRO1'. It installed fine in 'DISTRO1', then the upgrade to 'DISTRO2' fails because it tries to overwrite files that are owned by other packages without declaring a Breaks/Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces This problem is exposed during the upgrade of the 'EXPOSER' package, not by upgrading only the buggy package itself. In order to have piuparts automatically track this problem, I'll mark this bug as Affects/Found in the exposing package(s), too. >From the attached log (scroll to the bottom...): Selecting previously unselected package minetest-common. Unpacking minetest-common (from .../minetest-common_0.3.1+dfsg-3_all.deb) ... dpkg: error processing /var/cache/apt/archives/minetest-common_0.3.1+dfsg-3_all.deb (--unpack): trying to overwrite '/usr/share/minetest/tool_woodshovel.png', which is also in package minetest 0.3.1+dfsg-2 cheers, Andreas minetest_0.3.1+dfsg-3.log.gz Description: GNU Zip compressed data
Bug#670293: code-aster-{gui, run}: prompting due to modified conffiles which were not modified by the user
Package: code-aster-gui,code-aster-run Version: 1.10.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." http://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In http://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): Setting up code-aster-gui (1.10.4-1) ... Configuration file `/etc/codeaster/astkrc/prefs' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** prefs (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing code-aster-gui (--configure): EOF on stdin at conffile prompt Errors were encountered while processing: code-aster-gui Setting up code-aster-run (1.10.4-1) ... Installing new version of config file /etc/codeaster/aster ... Configuration file `/etc/codeaster/asrun' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** asrun (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing code-aster-run (--configure): EOF on stdin at conffile prompt Processing triggers for python-support ... configured to not write apport reports Errors were encountered while processing: code-aster-run cheers, Andreas code-aster-gui_1.10.4-1.log.gz Description: GNU Zip compressed data
Bug#670292: xemacs21-gnome-{, no-}mule{, -canna-wnn}: fails to upgrade from squeeze: apt-get dist-upgrade hangs forever
Package: xemacs21-gnome-mule,xemacs21-gnome-nomule,xemacs21-gnome-mule-canna-wnn Version: 21.4.22-3.2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): [...] 1m27.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp9G4jkK', 'apt-get', '-yf', 'dist-upgrade'] 21m27.0s ERROR: Terminating command due to excessive runtime 21m27.5s DUMP: * Command was terminated after exceeding runtime limit (1200 s) * 21m27.5s ERROR: Command failed (status=-15): ['chroot', '/tmp/piupartss/tmp9G4jkK', 'apt-get', '-yf', 'dist-upgrade'] [...] The test is terminated the same way for xemacs21-gnome-mule, xemacs21-gnome-nomule, xemacs21-gnome-mule-canna-wnn. I also tried to perform the upgrade manually in a minimal chroot as used by piuparts and see where it hangs, but instead I caught some failures from emacsen-common: [...] Setting up emacsen-common (1.4.23) ... emacsen-common: Handling install of emacsen flavor emacs emacsen-common: Handling install of emacsen flavor xemacs21 emacsen-common: byte-compiling for xemacs21 WARNING: Couldn't find obvious defaults for: data-directory mule-lisp-directory lisp-directory Perhaps some directories don't exist, or the XEmacs executable, /usr/bin/xemacs21 is in a strange place?Loading /usr/share/emacs/site-lisp/debian-startup... Loading 00debian... Error while loading 00debian: Symbol's function definition is void: loop Loading 00debian-vars... Symbol's function definition is void: batch-byte-compile xemacs exiting . emacs-package-install: /usr/lib/emacsen-common/packages/install/emacsen-common xemacs21 xemacs21 failed at /usr/lib/emacsen-common/emacs-package-install line 30, line 1. dpkg: error processing emacsen-common (--configure): subprocess installed post-installation script returned error exit status 255 [...] dpkg: dependency problems prevent configuration of xemacs21-gnome-mule: xemacs21-gnome-mule depends on xemacs21-mule; however: Package xemacs21-mule is not configured yet. dpkg: error processing xemacs21-gnome-mule (--configure): dependency problems - leaving unconfigured [...] cheers, Andreas xemacs21-gnome-mule_21.4.22-3.2+b1.log.gz Description: GNU Zip compressed data
Bug#670291: telepathy-glib: FTBFS on non-Linux if $HOME is inaccessible
Source: telepathy-glib Version: 0.18.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Package builds are not meant to write to $HOME, and some buildds (apparently including fasch for kfreebsd-amd64) enforce this by setting a $HOME which exists but is inaccessible. On Linux, D-Bus does not require access to $HOME, because clients of a DBusServer can prove their identities by using credentials-passing. On kFreeBSD, this is apparently not currently supported, at least by GDBus (from FreeBSD man pages, it should be, but maybe the implementation in GDBus is deficient or wrong?) and clients of the DBusServer are required to prove their identities by writing to ~/.dbus-keyrings. This isn't possible on fasch, causing a FTBFS: https://buildd.debian.org/status/fetch.php?pkg=telepathy-glib&arch=kfreebsd-amd64&ver=0.18.1-1&stamp=1334946724 Because GLib is involved, it might be necessary to set the Debian-specific environment variable G_HOME. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668172: Upstream author wants a separate bug for impress slide show problem.
see https://bugs.freedesktop.org/show_bug.cgi?id=47266 The bug is valid on both ATI (fixed in driver), Intel and Nvidia (not fixed). -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: user debian...@lists.debian.org, usertagging 669005, affects 669005, reopening 668748 ...
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was deb...@abeckmann.de).
> usertags 669005 piuparts
Bug#669005: uninstallable on sid (might just need require a rebuild)
There were no usertags set.
Usertags are now: piuparts.
> affects 669005 + shogun-python-static shogun-python-modular
> shogun-elwms-static
Bug #669005 [shogun-python-modular] uninstallable on sid (might just need
require a rebuild)
Added indication that 669005 affects shogun-python-static,
shogun-python-modular, and shogun-elwms-static
> reopen 668748
Bug #668748 {Done: Richard Nelson } [ifetch-tools]
ifetch-tools: unowned files after purge (policy 6.8, 10.8)
Bug reopened
Ignoring request to alter fixed versions of bug #668748 to the same values
previously set
> found 656216 4.1.2-5
Bug #656216 [xen-utils-common] xen-utils-common: unowned files after purge
(policy 6.8, 10.8)
Marked as found in versions xen/4.1.2-5.
> usertags 652934 - piuparts
Bug#652934: Packaging piuparts-server
Usertags were: piuparts.
Usertags are now: .
> affects 669278 + kde-plasma-desktop kde-plasma-netbook kdebase-workspace-bin
> kdebase-workspace kscreensaver-xsavers kscreensaver libsmokekde-dev
Bug #669278 [apt] E: Could not perform immediate configuration on
'phonon-backend-vlc'.
Added indication that 669278 affects kde-plasma-desktop, kde-plasma-netbook,
kdebase-workspace-bin, kdebase-workspace, kscreensaver-xsavers, kscreensaver,
and libsmokekde-dev
> found 669278 kde-plasma-desktop/5:74
Bug #669278 [apt] E: Could not perform immediate configuration on
'phonon-backend-vlc'.
The source kde-plasma-desktop and version 5:74 do not appear to match any
binary packages
Marked as found in versions kde-plasma-desktop/5:74.
> found 669278 kdebase-workspace/4:4.7.4-2
Bug #669278 [apt] E: Could not perform immediate configuration on
'phonon-backend-vlc'.
The source kdebase-workspace and version 4:4.7.4-2 do not appear to match any
binary packages
Marked as found in versions kdebase-workspace/4:4.7.4-2.
> found 669278 smokekde/4:4.7.4-1
Bug #669278 [apt] E: Could not perform immediate configuration on
'phonon-backend-vlc'.
Marked as found in versions smokekde/4:4.7.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
656216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656216
668748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668748
669005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669005
669278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669278
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#661122: bug#661122: cqrlog: ftbfs with fpc in sid
kefu chai said: >"David A Aitcheson" said: > >> #5 realise that cqrlog (1.2.2-2) has been superseded by cqrlog >> (1.3.1) thus your patch may be breaking more than it is fixing > >Ah! Sorry, I didn't notice that. But #661122 is marked as a RC bug in >unstable. That's why I tried to fix it. Anyway, I will stop here. FWIW ... There are debs of 1.3.1 on the cqrlog web-site at http://www.cqrlog.com/download -- Steve Kostecke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669516: marked as done (avifile: FTBFS: cp: cannot stat `debian/tmp/usr/lib/avifile-0.7/vidix/': No such file or directory)
Your message dated Tue, 24 Apr 2012 15:32:15 + with message-id and subject line Bug#669516: fixed in avifile 1:0.7.48~20090503.ds-10 has caused the Debian Bug report #669516, regarding avifile: FTBFS: cp: cannot stat `debian/tmp/usr/lib/avifile-0.7/vidix/': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 669516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: avifile Version: 1:0.7.48~20090503.ds-9.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[5]: Entering directory `/«PKGBUILDDIR»' > rm -f /«PKGBUILDDIR»/debian/tmp/usr/include/avifile > ln -s avifile-0.7 /«PKGBUILDDIR»/debian/tmp/usr/include/avifile > make[5]: Leaving directory `/«PKGBUILDDIR»' > make[4]: Leaving directory `/«PKGBUILDDIR»' > make[3]: Leaving directory `/«PKGBUILDDIR»' > make[2]: Leaving directory `/«PKGBUILDDIR»' > make[1]: Leaving directory `/«PKGBUILDDIR»' >dh_install > cp: cannot stat `debian/tmp/usr/lib/avifile-0.7/vidix/': No such file or > directory > dh_install: cp -a debian/tmp/usr/lib/avifile-0.7/vidix/ > debian/libavifile-0.7c2//usr/lib/avifile-0.7/ returned exit code 1 > make: *** [binary] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/avifile_0.7.48~20090503.ds-9.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: avifile Source-Version: 1:0.7.48~20090503.ds-10 We believe that the bug you reported is fixed in the latest version of avifile, which is due to be installed in the Debian FTP archive: avifile_0.7.48~20090503.ds-10.debian.tar.gz to main/a/avifile/avifile_0.7.48~20090503.ds-10.debian.tar.gz avifile_0.7.48~20090503.ds-10.dsc to main/a/avifile/avifile_0.7.48~20090503.ds-10.dsc libavifile-0.7-bin_0.7.48~20090503.ds-10_i386.deb to main/a/avifile/libavifile-0.7-bin_0.7.48~20090503.ds-10_i386.deb libavifile-0.7-common_0.7.48~20090503.ds-10_all.deb to main/a/avifile/libavifile-0.7-common_0.7.48~20090503.ds-10_all.deb libavifile-0.7-dev_0.7.48~20090503.ds-10_i386.deb to main/a/avifile/libavifile-0.7-dev_0.7.48~20090503.ds-10_i386.deb libavifile-0.7c2_0.7.48~20090503.ds-10_i386.deb to main/a/avifile/libavifile-0.7c2_0.7.48~20090503.ds-10_i386.deb 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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated avifile 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 24 Apr 2012 02:11:21 +0800 Source: avifile Binary: libavifile-0.7c2 libavifile-0.7-dev libavifile-0.7-bin libavifile-0.7-common Architecture: source i386 all Version: 1:0.7.48~20090503.ds-10 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Ying-Chun Liu (PaulLiu) Description: libavifile-0.7-bin - toolkit for libavifile libavifile-0.7-common - toolkit for libavifile libavifile-0.7-dev - development header files for libavifile libavifile-0.7c2 - shared libraries for AVI read/writing Closes: 669516 Changes: avifile (1:0.7.48~20090503.ds-10) unstable; urgency=low . * Multi-Arch support - Use debhelper 9 - Move common files to libavifile-0.7-common - Move toolkit to libavifile-0.7-bin * Bump Standards-Version to 3.9.3: nothing needs to be changed * Don't install vidix files. (Closes: #669516) * debian/copyright: use machine-readable 1.0 format Checksums-Sha1: 28f615b931156f380501da2129e3b29c93a79d8c 2169 avifile_0.7.48~20090503.ds-10.dsc 79568230944b4e586d1c0669bcdb04c6437f627c 25443 avifile_0.7.48~20090503.ds-10.debian.tar.gz b5f2fafcd4ac2d417a766003d8ddc3ab7d15
Bug#669557: ocropus: FTBFS: configure: error: Could not find tesseract! Choose --without-tesseract if you do not want to use it.
* Jeffrey Ratcliffe , 2012-04-23, 08:39: Does anyone have any objections to fixing this by uploaded 0.4.4 from experimental to unstable? Since the old UI is gone we should write a NEWS entry explaining briefly the new usage... Except that I have no idea how to use the new one myself. The manual is not very helpful (arguably it's was in the previous version either...) I tried "ocropus page ", but it crashed on every image I tried so far with: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted -- 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#668172: I have been bitten by this bug too
What worries me is that the upstream bug path leads to fix for radeon EXA, when I have the problem with nvidia cards and nvdia 295.40. So I won't get a fix for nvidia cards... And indeed disabling acceleration makes the problem vanish. --eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661122: bug#661122: cqrlog: ftbfs with fpc in sid
Hi Dave, I just found that the patch sent out yesterday is a wrong one, so here is the the right one. Le 24 avril 2012 08:47, David A Aitcheson a écrit : > > Kefu, > > #1 Arrrggg! > > #2 see http://www.freepascal.org/ for information on free pascal > > #3 see http://www.arrl.org/what-is-ham-radio for information about ham > radio in the USA > > #4 see http://www.cqrlog.com/ for information about the program you are > messing with > > #5 realise that cqrlog (1.2.2-2) has been superseded by cqrlog (1.3.1) > thus your patch may be breaking more than it is fixing Ah! Sorry, I didn't notice that. But #661122 is marked as a RC bug in unstable. That's why I tried to fix it. Anyway, I will stop here. > > > #6 goto #2, #3, #4, #5 again if not clearly understood else goto #7 Thanks for pointing me to these sites. I've been lookup docs at www.freepascal.com while fixing this issue. > > > On 04/23/2012 04:41 PM, Kefu Chai wrote: > > tag 661122 patch thanks hi, I am not quite familiar with free pascal > > or a ham radio. just came across this bug while looking for RC bugs. > > please find attached patch. > > #7 Where in the world are you? (just so we can point you to the ham > radio educators in your area) I am from Shanghai. have a good day, -- Regards Kefu Chai ftbfs-661122.diff Description: Binary data
Bug#659216: what to use in with the database connect url?
On Tue, Apr 24, 2012 at 03:22:40PM +0200, Jelle de Jong wrote: > I got a working psql command and what to do some smart things with > librebase, but cant figure out how to use the database url in the wizard!! It is a "conninfo" string as defined in http://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-PQCONNECTDB, which sends you back to http://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-PQCONNECTDBPARAMS; it is a space-separated list of keyword=value pairs. A more user-friendly prompt is in wishlist: https://bugs.freedesktop.org/43369 (I take patches) > psql -U username -h vps6.server.nl database > password For example, the equivalent of this psql command line is: host=vps6.server.nl dbname=database Then enter username and password in the LibreOffice dialogs for that. You can also hardcode the username (and also password) if you wish so: host=vps6.server.nl dbname=database user=HERE_THE_username password=HERE_THE_password Then, uncomment the "needs password" setting in LibreOffice. If you enter username and/or password in both the conninfo string (URL) and the LibreOffice prompts, I don't remember out the top of my head which one overrides the other one. -- Lionel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659216: what to use in with the database connect url?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I got a working psql command and what to do some smart things with librebase, but cant figure out how to use the database url in the wizard!! psql -U username -h vps6.server.nl database password ii libreoffice-base1:3.4.6-2 ii libreoffice-sdbc-postgresql 1:0.8.1+LibO3.4.6-2 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iJwEAQECAAYFAk+WqRoACgkQ1WclBW9j5HmH0gP/cx560ZyRXqax3G5KOb3T4rYe SsMuqfwjXOo0WFJ65dw0DJJnvVXyYJhGQQVO1MCRj2hipTSRAamdJFQBcOfM/RCD Ms2684iuwQYc4yp9cjnSytnDTYbg+1Qk11S7OzB3GOhVXEMuQHjbYf+gaxuKPS4J 4cJYDzdCTNjylUDNgVY= =MNem -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669531: marked as done (liblog4ada: FTBFS: ! LaTeX Error: File `url.sty' not found.)
Your message dated Tue, 24 Apr 2012 11:05:40 + with message-id and subject line Bug#669531: fixed in liblog4ada 1.2-3 has caused the Debian Bug report #669531, regarding liblog4ada: FTBFS: ! LaTeX Error: File `url.sty' not found. 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.) -- 669531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liblog4ada Version: 1.2-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«PKGBUILDDIR»/doc' > pdflatex -draftmode log4Ada.tex > This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2012/dev/Debian) > restricted \write18 enabled. > entering extended mode > (./log4Ada.tex > LaTeX2e <2011/06/27> > Babel and hyphenation patterns for english, dumylang, nohyphenation, > lo > aded. > (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls > Document Class: article 2007/10/19 v1.4h Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/pdftex-def/pdftex.def > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty)) > (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty) > (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def) > (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg) > > ! LaTeX Error: File `url.sty' not found. > > Type X to quit or to proceed, > or enter new name. (Default extension: sty) > > Enter file name: > ! Emergency stop. > > > l.4633 \let >\HyOrg@url\url^^M > ! ==> Fatal error occurred, no output PDF file produced! > Transcript written on log4Ada.log. > make[1]: *** [log4Ada.aux] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/liblog4ada_1.2-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: liblog4ada Source-Version: 1.2-3 We believe that the bug you reported is fixed in the latest version of liblog4ada, which is due to be installed in the Debian FTP archive: liblog4ada-dbg_1.2-3_amd64.deb to main/libl/liblog4ada/liblog4ada-dbg_1.2-3_amd64.deb liblog4ada-doc_1.2-3_all.deb to main/libl/liblog4ada/liblog4ada-doc_1.2-3_all.deb liblog4ada1_1.2-3_amd64.deb to main/libl/liblog4ada/liblog4ada1_1.2-3_amd64.deb liblog4ada2-dev_1.2-3_amd64.deb to main/libl/liblog4ada/liblog4ada2-dev_1.2-3_amd64.deb liblog4ada_1.2-3.debian.tar.gz to main/libl/liblog4ada/liblog4ada_1.2-3.debian.tar.gz liblog4ada_1.2-3.dsc to main/libl/liblog4ada/liblog4ada_1.2-3.dsc 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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Grave (supplier of updated liblog4ada 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 24 Apr 2012 12:37:16 +0200 Source: liblog4ada Binary: liblog4ada2-dev liblog4ada1 liblog4ada-dbg liblog4ada-doc Architecture: source amd64 all Version: 1.2-3 Distribution: unstable U
Bug#660488: miredo: FTBFS `pkglibdir' is not a legitimate directory for `PROGRAMS'
hi,
> > #661983 now claims to be fixed.
> It is was not fixed. Someone forgot to reopen it.
It seems that cdbs once fixed #661983, but revert to close #663082
which says:
> It looks more sensible to me, if cdbs-using packages that need a new
> automake resp pkglibexecdir set libexecdir explicitly to something
> like /usr/lib.
It seems that cdbs will not fix this anymore, so to fix your FTBFS
you will need to add
DEB_CONFIGURE_LIBEXECDIR = "\$${prefix}/lib/$(DEB_SOURCE_PACKAGE)"
to debian/rules after including autotools.mk, or switch buildsystems
other than cdbs.
P.S. I can't clone your git repository with 403 error. So, I haven't
try to your latest tree,
but anyway I hope to see that in unstable soon :-)
regards,
--
KURASHIKI Satoru
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670131: AttributeError: 'Version' object has no attribute 'policy_priority'
2012/4/24 Michael Vogt : > This should work with current sid but it will not work with older > version of python-apt. I added a check into do the code to not crash > if it runs with older versions of python-apt. Thanks. I realised after sending the report that severity "grave" was not justified due to the above reason. But still I think its an important fix for those that will want to use u-a > 0.76 in squeeze for at least two more years. Afterwards, probably the check could be removed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670228: CVE-2012-2125 CVE-2012-2126
Package: rubygems Severity: grave Tags: security Please see here for details and patches: http://www.openwall.com/lists/oss-security/2012/04/20/23 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#670156: xserver-xorg-core: input devices no longer detected
On Tue, Apr 24, 2012 at 03:07:23AM -0500, Jonathan Nieder wrote: > Roger Leigh wrote: > > > Should be relatively simple to fix--just don't clean /run when it's a > > tmpfs, but there's something subtly wrong with the logic we're using in > > /lib/init/bootlean. > > checkroot-bootclean.sh includes this gem: > rm -f /tmp/.clean /run/.clean /run/lock/.clean > clean_all > > Should this be made conditional on whether /run is a tmpfs? I'm not sure. We already created them conditionally if they were a tmpfs, so we should probably only remove them if they are older than the time the system booted, or not remove them at all. I'll have to think about it a little more. This looks like it's definitely the cause of the woes though. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661069: Bug#649448: radeon (evergreen): random-looking pattern of pixels when firmware not installed
Concerning the installer: There was no warning about the missing firmware for the graphics card. Thomas Kippenberg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669437: marked as done (lebiniou: FTBFS: gcc: error: unrecognized option '-V')
Your message dated Tue, 24 Apr 2012 08:47:38 + with message-id and subject line Bug#669437: fixed in lebiniou 3.18-1 has caused the Debian Bug report #669437, regarding lebiniou: FTBFS: gcc: error: unrecognized option '-V' 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.) -- 669437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lebiniou Version: 3.17-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc version 4.6.3 (Debian 4.6.3-4) > configure:3411: $? = 0 > configure:3400: gcc -V >&5 > gcc: error: unrecognized option '-V' > gcc: fatal error: no input files > compilation terminated. > configure:3411: $? = 4 > configure:3400: gcc -qversion >&5 > gcc: error: unrecognized option '-qversion' > gcc: fatal error: no input files > compilation terminated. > configure:3411: $? = 4 > configure:3431: checking whether the C compiler works > configure:3453: gcc-rdynamic conftest.c >&5 > configure:3457: $? = 0 > configure:3505: result: yes > configure:3508: checking for C compiler default output file name > configure:3510: result: a.out > configure:3516: checking for suffix of executables > configure:3523: gcc -o conftest-rdynamic conftest.c >&5 > configure:3527: $? = 0 > configure:3549: result: > configure:3571: checking whether we are cross compiling > configure:3579: gcc -o conftest-rdynamic conftest.c >&5 > configure:3583: $? = 0 > configure:3590: ./conftest > configure:3594: $? = 0 > configure:3609: result: no > configure:3614: checking for suffix of object files > configure:3636: gcc -c conftest.c >&5 > configure:3640: $? = 0 > configure:3661: result: o > configure:3665: checking whether we are using the GNU C compiler > configure:3684: gcc -c conftest.c >&5 > configure:3684: $? = 0 > configure:3693: result: yes > configure:3702: checking whether gcc accepts -g > configure:3722: gcc -c -g conftest.c >&5 > configure:3722: $? = 0 > configure:3763: result: yes > configure:3780: checking for gcc option to accept ISO C89 > configure:3844: gcc -c -g -O2 conftest.c >&5 > configure:3844: $? = 0 > configure:3857: result: none needed > configure:3888: checking for style of include used by make > configure:3916: result: GNU > configure:3942: checking dependency style of gcc > configure:4053: result: none > configure:4070: checking whether gcc and cc understand -c and -o together > configure:4101: gcc -c conftest.c -o conftest2.o >&5 > configure:4105: $? = 0 > configure:4111: gcc -c conftest.c -o conftest2.o >&5 > configure:4115: $? = 0 > configure:4126: cc -c conftest.c >&5 > configure:4130: $? = 0 > configure:4138: cc -c conftest.c -o conftest2.o >&5 > configure:4142: $? = 0 > configure:4148: cc -c conftest.c -o conftest2.o >&5 > configure:4152: $? = 0 > configure:4170: result: yes > configure:4253: checking for g++ > configure:4269: found /usr/bin/g++ > configure:4280: result: g++ > configure:4307: checking for C++ compiler version > configure:4316: g++ --version >&5 > g++ (Debian 4.6.3-4) 4.6.3 > Copyright (C) 2011 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > configure:4327: $? = 0 > configure:4316: g++ -v >&5 > Using built-in specs. > COLLECT_GCC=g++ > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6/lto-wrapper > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Debian 4.6.3-4' > --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs > --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr > --program-suffix=-4.6 --enable-shared --enable-linker-build-id > --with-system-zlib --libexecdir=/usr/lib --without-included-gettext > --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 > --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes > --enable-gnu-unique-object --enable-plugin --enable-objc-gc > --with-arch-32=i586 --with-tune=generic --enable-checking=release > --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu > Thread model: posix > gcc version 4.6.3 (Debian 4.6.3-4) > configure:4327: $? = 0 > configure:4316: g++ -V >&5 > g++: error: unrecognized option '-V' > g++: fatal error: no input files > compilation terminated.
Bug#670221: plptools: fails to install due to insserv rejecting the script header
Package: plptools Version: 1.0.9-2.3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install due to insserv rejecting the script header. Some notes are available from at http://wiki.debian.org/LSBInitScripts >From the attached log (scroll to the bottom...): Selecting previously unselected package plptools. (Reading database ... 6917 files and directories currently installed.) Unpacking plptools (from .../plptools_1.0.9-2.3_amd64.deb) ... Setting up plptools (1.0.9-2.3) ... insserv: Service fuse has to be enabled to start service plptools insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing plptools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: plptools This looks like an explicit dependency on fuse (or whichever package provides the 'fuse' service) is missing. This was working previously because some dependency chain fulfilled this, but other packages have changed and therefore this no longer works. cheers, Andreas plptools_1.0.9-2.3.log.gz Description: GNU Zip compressed data
Bug#669453: Fixed pending upload sponsor
Thanks. On Tue, Apr 24, 2012 at 2:12 PM, Chow Loong Jin wrote: > On 24/04/2012 08:59, Andrew Caudwell wrote: > > This has been fixed, I just need a debian maintainer to sponsor the > upload as my > > package co-maintainer is away at the moment (or wait a few weeks). > > Uploaded, tagged and pushed. > > > Cheers > > -- > Loong Jin > >
Bug#670156: xserver-xorg-core: input devices no longer detected
Roger Leigh wrote: > Should be relatively simple to fix--just don't clean /run when it's a > tmpfs, but there's something subtly wrong with the logic we're using in > /lib/init/bootlean. checkroot-bootclean.sh includes this gem: start|"") # Clean /tmp, /var/lock, /var/run. Remove the .clean files to # force initial cleaning. This is intended to allow cleaning # of directories masked by mounts while the system was # previously running, which would otherwise prevent them being # cleaned. rm -f /tmp/.clean /run/.clean /run/lock/.clean clean_all Should this be made conditional on whether /run is a tmpfs? Is a /run that is not a tmpfs a supported configuration? When /run is not a tmpfs, since version 167-2 udev doesn't use it, letting us narrowly escape trouble in that case. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: > # Tue Apr 24 08:03:33 UTC 2012 > # Tagging as pending bugs that are closed by packages in NEW > # http://ftp-master.debian.org/new.html > # > # Source package in NEW: libpostproc > tags 670052 + pending Bug #670052 [wnpp] ITP: libpostproc -- FFmpeg derived postprocessing library Added tag(s) pending. > # Source package in NEW: ruby-opengl > tags 650605 + pending Bug #650605 [libopengl-ruby1.9.1] libopengl-ruby1.9.1: undefined symbol: rb_str2cstr Added tag(s) pending. > # Source package in NEW: ruby-opengl > tags 651702 + pending Bug #651702 [src:libopengl-ruby] libopengl-ruby: transition to gem2deb packaging Added tag(s) pending. > # Source package in NEW: ffdiaporama > tags 669201 + pending Bug #669201 [wnpp] ITP: ffdiaporama -- Movie creator from photos and video clips Added tag(s) pending. > # Source package in NEW: href="http://packages.qa.debian.org/gridengine";>gridengine > tags 645193 + pending Bug #645193 [libdrmaa-dev] pbs-drmaa-dev and libdrmaa-dev: error when trying to install together Added tag(s) pending. > # Source package in NEW: href="http://packages.qa.debian.org/gridengine";>gridengine > tags 669284 + pending Bug #669284 [src:gridengine] gridengine: FTBFS with linux >3 Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 645193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645193 650605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650605 651702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651702 669201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669201 669284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669284 670052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670052 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: retitle 670217 to FTBFS against shiboken/pyside 1.1.1
Processing commands for cont...@bugs.debian.org: > retitle 670217 FTBFS against shiboken/pyside 1.1.1 Bug #670217 [pyside-mobility] (no subject) Changed Bug title to 'FTBFS against shiboken/pyside 1.1.1' from '(no subject)' > thanks Stopping processing here. Please contact me if you need assistance. -- 670217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670217 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#670131: marked as done (AttributeError: 'Version' object has no attribute 'policy_priority')
Your message dated Tue, 24 Apr 2012 07:33:06 +
with message-id
and subject line Bug#670131: fixed in unattended-upgrades 0.76.3
has caused the Debian Bug report #670131,
regarding AttributeError: 'Version' object has no attribute 'policy_priority'
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.)
--
670131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unattended-upgrades
Version: 0.76.2
Severity: grave
Justification: renders package unusable
Hi,
I upgraded u-a on one 32-bit server to test if another problem is fixed and
found that it doesn't work anymore:
| root@goliath:~# unattended-upgrades --debug
| INFO:root:Initial blacklisted packages: locales libc6-i686 libc-bin libc6
linux-image-2.6.32-5-486 linux-image-2.6.32-5-686-bigmem firmware-linux-free
linux-base libupsclient1 nut nut-cgi squid3-common squid3
| Initial blacklisted packages: locales libc6-i686 libc-bin libc6
linux-image-2.6.32-5-486 linux-image-2.6.32-5-686-bigmem firmware-linux-free
linux-base libupsclient1 nut nut-cgi squid3-common squid3
| INFO:root:Starting unattended upgrades script
| Starting unattended upgrades script
| INFO:root:Allowed origins are: ['o=Debian,a=stable',
'o=Debian,a=stable-updates', 'o=Debian,a=proposed-updates',
'origin=Debian,archive=stable,label=Debian-Security']
| Allowed origins are: ['o=Debian,a=stable', 'o=Debian,a=stable-updates',
'o=Debian,a=proposed-updates',
'origin=Debian,archive=stable,label=Debian-Security']
| Traceback (most recent call last):
| File "/usr/bin/unattended-upgrades", line 920, in
| main(options)
| File "/usr/bin/unattended-upgrades", line 699, in main
| allowed_origins=allowed_origins)
| File "/usr/bin/unattended-upgrades", line 70, in __init__
| self.adjust_candidate_versions()
| File "/usr/bin/unattended-upgrades", line 94, in adjust_candidate_versions
| if ver.policy_priority < 0:
| AttributeError: 'Version' object has no attribute 'policy_priority'
(on this system I do many u-a tests, that's why it has many packages
blacklisted)
Thanks
-- System Information:
Debian Release: 6.0.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 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 unattended-upgrades depends on:
ii apt 0.8.10.3+squeeze1 Advanced front-end for dpkg
ii apt-utils 0.8.10.3+squeeze1 APT utility programs
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii lsb-release 3.2-23.2squeeze1 Linux Standard Base version report
ii python2.6.6-3+squeeze6 interactive high-level object-orie
ii python-apt0.7.100.1+squeeze1 Python interface to libapt-pkg
ii ucf 3.0025+nmu1Update Configuration File: preserv
unattended-upgrades recommends no packages.
Versions of packages unattended-upgrades suggests:
pn bsd-mailx (no description available)
-- Configuration Files:
/etc/apt/apt.conf.d/50unattended-upgrades changed:
// Automatically upgrade packages from these origin patterns
Unattended-Upgrade::Origins-Pattern {
// Codename based matching:
// This will follow the migration of a release through different
// archives (e.g. from testing to stable and later oldstable).
// "o=Debian,n=squeeze";
// "o=Debian,n=squeeze-updates";
// "o=Debian,n=squeeze-proposed-updates";
// "o=Debian,n=squeeze,l=Debian-Security";
// Archive or Suite based matching:
// Note that this will silently match a different release after
// migration to the specified archive (e.g. testing becomes the
// new stable).
"o=Debian,a=stable";
"o=Debian,a=stable-updates";;
"o=Debian,a=proposed-updates";
"origin=Debian,archive=stable,label=Debian-Security";
};
// List of packages to not update
Unattended-Upgrade::Package-Blacklist {
// "vim";
// "libc6";
// "libc6-dev";
// "libc6-i686";
};
// This option allows you to control if on a unclean dpkg exit
// unattended-upgrades will automatically run
// dpkg --force-confold --configure -a
// The default is true, to ensure updates keep getting installed
//Unattended-Upgrade::AutoFixInterruptedDpkg "false";
// Split the upgrade into the smallest possible chunks so that
/
Bug#665068: marked as done (semidef-oct: FTBFS: error: No such file or directory)
Your message dated Tue, 24 Apr 2012 07:33:21 + with message-id and subject line Bug#669226: Removed package(s) from unstable has caused the Debian Bug report #665068, regarding semidef-oct: FTBFS: error: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 665068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: semidef-oct Version: 1:2003-10 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«PKGBUILDDIR»/SRC' > making get_matrix.o from get_matrix.cc > CXXFLAGS=-Wno-deprecated mkoctfile get_matrix.cc > rm -f get_matrix.oct > making get_real_scalar.o from get_real_scalar.cc > CXXFLAGS=-Wno-deprecated mkoctfile get_real_scalar.cc > rm -f get_real_scalar.oct > making get_vector.o from get_vector.cc > CXXFLAGS=-Wno-deprecated mkoctfile get_vector.cc > rm -f get_vector.oct > CXXFLAGS=-Wno-deprecated mkoctfile -Duserusage sp.cc get_matrix.o > get_real_scalar.o get_vector.o sp_src.c dgels.fdopgtr.f dspgv.f > dsptrd.f lse.f dlansp.f dpptrf.f dspmv.fdtpmv.flce.f dlantr.f > dspev.fdspr.f dtpsv.flde.f dlatrs.f dspgst.f dspr2.f > dtrcon.f > make[1]: Leaving directory `/«PKGBUILDDIR»/SRC' > Octave implementation of Vandenberghe and Boyd's semidef package > > [ 1] educational testing problem > [ 2] linear programming > [ 3] matrix norm minimization > [ 4] stability margin problem > [ 5] quit > > pick a number, any number: > educational testing problem: maximize the trace of a diagonal > matrix D > 0 such that A - D >=0 for a given positive definite > matrix A > > error: `run_cmd' undefined near line 16 column 4 > error: called from: > error: ./demosp.m at line 16, column 4 > error: No such file or directory > error: ignoring octave_execution_exception while preparing to exit > make: *** [build-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/21/semidef-oct_2003-10.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Version: 1:2003-10+rm Dear submitter, as the package semidef-oct has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/669226 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain) --- End Message ---
Processed: Re: xserver-xorg-core: input devices no longer detected
Processing commands for cont...@bugs.debian.org: > severity 669949 grave Bug #669949 [initscripts] sysvinit: Break X11: no more mouse and keyboard Bug #670156 [initscripts] xserver-xorg-core: input devices no longer detected Ignoring request to change severity of Bug 669949 to the same value. Ignoring request to change severity of Bug 670156 to the same value. > merge 669949 670156 Bug #669949 [initscripts] sysvinit: Break X11: no more mouse and keyboard Bug #670156 [initscripts] xserver-xorg-core: input devices no longer detected Bug #670156 [initscripts] xserver-xorg-core: input devices no longer detected Merged 669949 670156 > thanks Stopping processing here. Please contact me if you need assistance. -- 669949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669949 670156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670156 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#670156: xserver-xorg-core: input devices no longer detected
severity 669949 grave merge 669949 670156 thanks On Mon, Apr 23, 2012 at 09:14:06PM -0500, Jonathan Nieder wrote: > Brian Paterni wrote: > > > Aha! I only downgraded sysvinit and sysvinit-utils. With > > initscripts=2.88dsf-22.1, keyboard and mouse are functional once again. > > Thanks for testing. Reassigning. Thanks. This is definitely an issue with initscripts in experimental. I've narrowed this down to bootclean.sh cleaning /run. However, I've not yet got to the bottom of /why/ it's being cleaned at all. In current git, I've added additional .clean flagfiles to all tmpfs mounts. bootclean checks for the presence of these files and skips cleaning if they are present (it's done this for years). However... it's still cleaning in the presence of these files. So it's definitely broken in -23, but also still broken in git. Should be relatively simple to fix--just don't clean /run when it's a tmpfs, but there's something subtly wrong with the logic we're using in /lib/init/bootlean. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670217: (no subject)
Package: pyside-mobility Version: 0.2.3+git4~8118106-2 Severity: serious Tags: upstream I just tested to build it after the pyside/shiboken upload and it FTBFS as it searches for a generatorrunner plugin, which is not needed since shiboken 1.1.1. This will make it unbuildable in wheezy as soon as pyside and shiboken enter wheezy, hence serious. This is in the process to be reported to upstream (See https://bugreports.qt-project.org/browse/PYSIDE-58 e.g ). Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669392: marked as done (tetex-frogg: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2))
Your message dated Tue, 24 Apr 2012 07:23:34 + with message-id and subject line Bug#669412: Removed package(s) from unstable has caused the Debian Bug report #669392, regarding tetex-frogg: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2) 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.) -- 669392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tetex-frogg Version: 0.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails As putting files into /usr/local is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. >From the attached log (scroll to the bottom...): 0m53.8s ERROR: FAIL: Package purging left files on system: /usr/local/share/texmf/not owned /usr/local/share/texmf/ls-Rnot owned This problem is usually caused by running mktexlsr (or texhash) without path arguments from a maintainer script. The recommende solution is to switch to use dh_installtex and have this generate most (or perhaps even all) of the maintainer scripts content. Otherwise run mktexlsr with the tree as argument where the package installs its files, which is usually mktexlsr /usr/share/texmf There has been some further discussion about these bugs in this thread: http://lists.debian.org/debian-tex-maint/2012/04/msg00306.html Please have a look at the Debian-TeX-Policy (in the tex-common package) for the current practice of handling TeX packages. For further TeX packaging related questions contact debian-tex-ma...@lists.debian.org cheers, Andreas tetex-frogg_0.4-3.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Version: 0.4-3+rm Dear submitter, as the package tetex-frogg has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/669412 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain) --- End Message ---
Bug#670131: AttributeError: 'Version' object has no attribute 'policy_priority'
On Mon, Apr 23, 2012 at 12:41:01PM +0300, Teodor wrote:
> Package: unattended-upgrades
> Version: 0.76.2
> Severity: grave
> Justification: renders package unusable
Thanks for your bugreport.
This should work with current sid but it will not work with older
version of python-apt. I added a check into do the code to not crash
if it runs with older versions of python-apt.
Cheers,
Michael
> Hi,
>
> I upgraded u-a on one 32-bit server to test if another problem is fixed and
> found that it doesn't work anymore:
>
> | root@goliath:~# unattended-upgrades --debug
> | INFO:root:Initial blacklisted packages: locales libc6-i686 libc-bin libc6
> linux-image-2.6.32-5-486 linux-image-2.6.32-5-686-bigmem firmware-linux-free
> linux-base libupsclient1 nut nut-cgi squid3-common squid3
> | Initial blacklisted packages: locales libc6-i686 libc-bin libc6
> linux-image-2.6.32-5-486 linux-image-2.6.32-5-686-bigmem firmware-linux-free
> linux-base libupsclient1 nut nut-cgi squid3-common squid3
> | INFO:root:Starting unattended upgrades script
> | Starting unattended upgrades script
> | INFO:root:Allowed origins are: ['o=Debian,a=stable',
> 'o=Debian,a=stable-updates', 'o=Debian,a=proposed-updates',
> 'origin=Debian,archive=stable,label=Debian-Security']
> | Allowed origins are: ['o=Debian,a=stable', 'o=Debian,a=stable-updates',
> 'o=Debian,a=proposed-updates',
> 'origin=Debian,archive=stable,label=Debian-Security']
> | Traceback (most recent call last):
> | File "/usr/bin/unattended-upgrades", line 920, in
> | main(options)
> | File "/usr/bin/unattended-upgrades", line 699, in main
> | allowed_origins=allowed_origins)
> | File "/usr/bin/unattended-upgrades", line 70, in __init__
> | self.adjust_candidate_versions()
> | File "/usr/bin/unattended-upgrades", line 94, in adjust_candidate_versions
> | if ver.policy_priority < 0:
> | AttributeError: 'Version' object has no attribute 'policy_priority'
>
> (on this system I do many u-a tests, that's why it has many packages
> blacklisted)
>
> Thanks
>
>
> -- System Information:
> Debian Release: 6.0.4
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
> 'stable')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 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 unattended-upgrades depends on:
> ii apt 0.8.10.3+squeeze1 Advanced front-end for dpkg
> ii apt-utils 0.8.10.3+squeeze1 APT utility programs
> ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management
> sy
> ii lsb-release 3.2-23.2squeeze1 Linux Standard Base version
> report
> ii python2.6.6-3+squeeze6 interactive high-level
> object-orie
> ii python-apt0.7.100.1+squeeze1 Python interface to libapt-pkg
> ii ucf 3.0025+nmu1Update Configuration File:
> preserv
>
> unattended-upgrades recommends no packages.
>
> Versions of packages unattended-upgrades suggests:
> pn bsd-mailx (no description available)
>
> -- Configuration Files:
> /etc/apt/apt.conf.d/50unattended-upgrades changed:
> // Automatically upgrade packages from these origin patterns
> Unattended-Upgrade::Origins-Pattern {
> // Codename based matching:
> // This will follow the migration of a release through different
> // archives (e.g. from testing to stable and later oldstable).
> // "o=Debian,n=squeeze";
> // "o=Debian,n=squeeze-updates";
> // "o=Debian,n=squeeze-proposed-updates";
> // "o=Debian,n=squeeze,l=Debian-Security";
> // Archive or Suite based matching:
> // Note that this will silently match a different release after
> // migration to the specified archive (e.g. testing becomes the
> // new stable).
> "o=Debian,a=stable";
> "o=Debian,a=stable-updates";;
> "o=Debian,a=proposed-updates";
> "origin=Debian,archive=stable,label=Debian-Security";
> };
> // List of packages to not update
> Unattended-Upgrade::Package-Blacklist {
> //"vim";
> //"libc6";
> //"libc6-dev";
> //"libc6-i686";
> };
> // This option allows you to control if on a unclean dpkg exit
> // unattended-upgrades will automatically run
> // dpkg --force-confold --configure -a
> // The default is true, to ensure updates keep getting installed
> //Unattended-Upgrade::AutoFixInterruptedDpkg "false";
> // Split the upgrade into the smallest possible chunks so that
> // they can be interrupted with SIGUSR1. This makes the upgrade
> // a bit slower but it has the benefit that shutdown while a upgrade
> // is running is possible (with a small delay)
> //Unattended-Upgrade::MinimalSteps "true";
> // Install all unattended-upgrades when the machine is shuting down
> // instead of doing it in the background while the m
