Bug#679283: [xml/sgml-pkgs] Bug#679283: CVE-2012-2825
Will make an upload to fix the bug soon, and maybe we need to prepare a fix for stable? -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679280: [xml/sgml-pkgs] Bug#679280: CVE-2012-2807
tags 679280 + moreinfo thanks Hi, I'm still investigating the problem and more details about it are welcomed, please don't NMU for either unstable or stable. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [xml/sgml-pkgs] Bug#679280: CVE-2012-2807
Processing commands for cont...@bugs.debian.org: tags 679280 + moreinfo Bug #679280 [libxml2] CVE-2012-2807 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 679280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679280 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#675839: marked as done (boinc-app-seti: FTBFS[kfreebsd]: error: 'floor' was not declared in this scope)
Your message dated Thu, 28 Jun 2012 06:47:12 + with message-id e1sk8vu-0001nr...@franck.debian.org and subject line Bug#675839: fixed in boinc-app-seti 6.12~svn1306-1 has caused the Debian Bug report #675839, regarding boinc-app-seti: FTBFS[kfreebsd]: error: 'floor' was not declared in this scope to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 675839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:boinc-app-seti Version: 6.12~svn1305-2 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: vector/analyzeFuncs_sse.cpp: In function 'int sse1_ChirpData_ak(float (*)[2], float (*)[2], int, double, int, double)': vector/analyzeFuncs_sse.cpp:782:62: error: 'floor' was not declared in this scope vector/analyzeFuncs_sse.cpp: At global scope: vector/analyzeFuncs_sse.cpp:1299:91: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] vector/analyzeFuncs_sse.cpp:2252:82: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] vector/analyzeFuncs_sse.cpp:2265:1: warning: 'typedef' was ignored in this declaration [enabled by default] vector/analyzeFuncs_sse.cpp:2556:82: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] make[3]: *** [seti_boinc-analyzeFuncs_sse.o] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=boinc-app-setiarch=kfreebsd-amd64ver=6.12%7Esvn1305-2stamp=1338167773 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--- ---BeginMessage--- Source: boinc-app-seti Source-Version: 6.12~svn1306-1 We believe that the bug you reported is fixed in the latest version of boinc-app-seti, which is due to be installed in the Debian FTP archive: boinc-app-seti-dbg_6.12~svn1306-1_amd64.deb to main/b/boinc-app-seti/boinc-app-seti-dbg_6.12~svn1306-1_amd64.deb boinc-app-seti_6.12~svn1306-1.debian.tar.gz to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306-1.debian.tar.gz boinc-app-seti_6.12~svn1306-1.dsc to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306-1.dsc boinc-app-seti_6.12~svn1306-1_amd64.deb to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306-1_amd64.deb boinc-app-seti_6.12~svn1306.orig.tar.gz to main/b/boinc-app-seti/boinc-app-seti_6.12~svn1306.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 675...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steffen Moeller moel...@debian.org (supplier of updated boinc-app-seti 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, 29 May 2012 23:52:47 +0200 Source: boinc-app-seti Binary: boinc-app-seti boinc-app-seti-dbg Architecture: source amd64 Version: 6.12~svn1306-1 Distribution: unstable Urgency: low Maintainer: Debian BOINC Maintainers pkg-boinc-de...@lists.alioth.debian.org Changed-By: Steffen Moeller moel...@debian.org Description: boinc-app-seti - SETI@home application for the BOINC client boinc-app-seti-dbg - debug symbols for SETI@home Closes: 675839 Changes: boinc-app-seti (6.12~svn1306-1) unstable; urgency=low . * New upstream version. * Added inclusioncmath for kfreebsd (Closes: #675839) Checksums-Sha1: e801020aba9a4a0518bd79a4277401c5f6cbcab0 1618 boinc-app-seti_6.12~svn1306-1.dsc ccbcc3ecebc153a70f417bfe042ec23d157478ed 2832216 boinc-app-seti_6.12~svn1306.orig.tar.gz 13eb1dc43e5b7598548b4ba9b22eace12d3c5a10 11953 boinc-app-seti_6.12~svn1306-1.debian.tar.gz c5c5b960e67264d74fd54b66e211a5a8c4637833 379922 boinc-app-seti_6.12~svn1306-1_amd64.deb 7748eb603d9d063a17e45350478ed693d5c60e4f 2304744 boinc-app-seti-dbg_6.12~svn1306-1_amd64.deb Checksums-Sha256: 9195382e6f1f24279a66e192a320a136dedee018a5c55339678ee60f9717c41b 1618 boinc-app-seti_6.12~svn1306-1.dsc
Bug#614089: marked as done (nvidia-graphics-modules: needs updating to newer kernels)
Your message dated Thu, 28 Jun 2012 06:48:51 + with message-id e1sk8x5-0001z7...@franck.debian.org and subject line Bug#614089: fixed in nvidia-graphics-modules 302.17+1 has caused the Debian Bug report #614089, regarding nvidia-graphics-modules: needs updating to newer kernels 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.) -- 614089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nvidia-graphics-modules Version: 195.36.31+2 Severity: serious Hi, linux-2.6 is now at 2.6.37 in sid, so I'm looking at removing nvidia-graphics-modules from testing when the kernel gets ready to migrate. Filing this as a reminder. Cheers, Julien ---End Message--- ---BeginMessage--- Source: nvidia-graphics-modules Source-Version: 302.17+1 We believe that the bug you reported is fixed in the latest version of nvidia-graphics-modules, which is due to be installed in the Debian FTP archive: nvidia-graphics-modules_302.17+1.dsc to non-free/n/nvidia-graphics-modules/nvidia-graphics-modules_302.17+1.dsc nvidia-graphics-modules_302.17+1.tar.gz to non-free/n/nvidia-graphics-modules/nvidia-graphics-modules_302.17+1.tar.gz nvidia-kernel-2.6-486_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-486_302.17+1_i386.deb nvidia-kernel-2.6-686-pae_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-686-pae_302.17+1_i386.deb nvidia-kernel-2.6-amd64_302.17+1_amd64.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-amd64_302.17+1_amd64.deb nvidia-kernel-2.6-amd64_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-amd64_302.17+1_i386.deb nvidia-kernel-2.6-rt-686-pae_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-rt-686-pae_302.17+1_i386.deb nvidia-kernel-2.6-rt-amd64_302.17+1_amd64.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-2.6-rt-amd64_302.17+1_amd64.deb nvidia-kernel-3.2.0-3-486_302.17+1+2+3.2.21-2_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-486_302.17+1+2+3.2.21-2_i386.deb nvidia-kernel-3.2.0-3-686-pae_302.17+1+2+3.2.21-2_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-686-pae_302.17+1+2+3.2.21-2_i386.deb nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_amd64.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_amd64.deb nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-amd64_302.17+1+2+3.2.21-2_i386.deb nvidia-kernel-3.2.0-3-rt-686-pae_302.17+1+2+3.2.21-2_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-rt-686-pae_302.17+1+2+3.2.21-2_i386.deb nvidia-kernel-3.2.0-3-rt-amd64_302.17+1+2+3.2.21-2_amd64.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-3.2.0-3-rt-amd64_302.17+1+2+3.2.21-2_amd64.deb nvidia-kernel-486_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-486_302.17+1_i386.deb nvidia-kernel-686-pae_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-686-pae_302.17+1_i386.deb nvidia-kernel-amd64_302.17+1_amd64.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-amd64_302.17+1_amd64.deb nvidia-kernel-amd64_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-amd64_302.17+1_i386.deb nvidia-kernel-rt-686-pae_302.17+1_i386.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-rt-686-pae_302.17+1_i386.deb nvidia-kernel-rt-amd64_302.17+1_amd64.deb to non-free/n/nvidia-graphics-modules/nvidia-kernel-rt-amd64_302.17+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 614...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann deb...@abeckmann.de (supplier of updated nvidia-graphics-modules 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, 26 Jun 2012 11:01:35 +0200 Source: nvidia-graphics-modules Binary: nvidia-kernel-amd64 nvidia-kernel-2.6-amd64 nvidia-kernel-3.2.0-3-amd64 nvidia-kernel-486 nvidia-kernel-2.6-486 nvidia-kernel-3.2.0-3-486 nvidia-kernel-686-pae nvidia-kernel-2.6-686-pae
Bug#679283: [xml/sgml-pkgs] Bug#679283: CVE-2012-2825
On Donnerstag, 28. Juni 2012 08:42:54 Aron Xu wrote: Will make an upload to fix the bug soon, and maybe we need to prepare a fix for stable? The impact of this issue is rather low, can you fix this though a stable point update? http://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable We should fix CVE-2012-2807 though a DSA, though. Cheers, Moritz -- Moritz Mühlenhoff muehlenh...@univention.de Open Source Software Engineer Univention GmbH be open.fon: +49 421 22 232- 0 Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 http://www.univention.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662706: src:libmesh: unbuildable/uninstallable with newer petsc/slepc
Hi, I have just uploaded an new upstream release in Debian science svn that should solve the RC bug. This package needs some polishing but should be usable. Best C -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670908: deal.ii: FTBFS: include path for slepc missing
Hi, I have uploaded a patch to fix this issue in Debian science git. hope it helps C. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677883: FTBFS: Nonexistent build-dependency: libtrilinos-dev
Hi, this issue should be fixed with the new trilinos package 10.8.5 Best C -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678902: proposed sgml-base 1.16+nmu4 fixing #676717 and #678902
Dear dpkg maintainers, On Thu, Jun 28, 2012 at 02:05:56AM +0100, Ian Jackson wrote: I'm not convinced that a Pre-Depends is the best answer here. I think a better answer would be for the new dpkg to activate all file triggers when it first starts, and for sgml-base to simply use Depends. Will you be able to provide a version of dpkg that invokes all triggers in /etc when being upgraded from 1.16.4 in time for wheezy? See #678902 for why this is useful. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677714: wine-unstable: Incomplete upload of 1.5 for amd64
Dear maintainer, is this some sort of poor joke, or what is going on
here? After the latest update to 1.5.6-1, installing wine-unstable
results in installing two dummy, empty and absolutely useless packages
on amd64.
$ dpkg -L wine{,64-bin}-unstable
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libwine-unstable
/usr/share/doc/wine-unstable
/.
/usr
/usr/bin
/usr/bin/wine
/usr/share
/usr/share/doc
/usr/share/doc/libwine-unstable
/usr/share/doc/wine64-bin-unstable
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679368: pylucene: FTBFS python class name already in us
Source: pylucene Version: 3.5.0-1 Severity: serious Hi, Your package FTBFS in a sid chroot. The relevant part of the log appears to be: python2.6 -m jcc.__main__ --jar lucene-java-3.5.0/lucene/build/lucene-core-3.5.0.jar --jar lucene-java-3.5.0/lucene/build/contrib/analyzers/common/lucene-analyzers-3.5.0.jar --jar lucene-java-3.5.0/lucene/build/contrib/memory/lucene-memory-3.5.0.jar --jar lucene-java-3.5.0/lucene/build/contrib/highlighter/lucene-highlighter-3.5.0.jar --jar build/jar/extensions.jar --jar lucene-java-3.5.0/lucene/build/contrib/queries/lucene-queries-3.5.0.jar --jar lucene-java-3.5.0/lucene/build/contrib/grouping/lucene-grouping-3.5.0.jar --jar lucene-java-3.5.0/lucene/build/contrib/join/lucene-join-3.5.0.jar --jar lucene-java-3.5.0/lucene/build/contrib/facet/lucene-facet-3.5.0.jar --jar lucene-java-3.5.0/lucene/build/contrib/spellchecker/lucene-spellchecker-3.5.0.jar --output build-python2.6 --package java.lang java.lang.System java.lang.Runtime --package java.util java.util.Arrays java.util.HashMap java.util.HashSet java.text.SimpleDateFormat java.text.DecimalFormat java.text.Collator --packag e java.u til.regex --package java.io java.io.StringReader java.io.InputStreamReader java.io.FileInputStream --exclude org.apache.lucene.queryParser.Token --exclude org.apache.lucene.queryParser.TokenMgrError --exclude org.apache.lucene.queryParser.QueryParserTokenManager --exclude org.apache.lucene.queryParser.ParseException --exclude org.apache.lucene.search.regex.JakartaRegexpCapabilities --exclude org.apache.regexp.RegexpTunnel --exclude org.apache.lucene.analysis.cn.smart.AnalyzerProfile --python lucene --mapping org.apache.lucene.document.Document 'get:(Ljava/lang/String;)Ljava/lang/String;' --mapping java.util.Properties 'getProperty:(Ljava/lang/String;)Ljava/lang/String;' --sequence java.util.AbstractList 'size:()I' 'get:(I)Ljava/lang/Object;' --rename org.apache.lucene.search.highlight.SpanScorer=HighlighterSpanScorer --version 3.5.0 --module python/collections.py --module python/ICUNormalizer2Filter.py --module python/ICUFoldingFilter.py --module python/ICUTransformFilter.py --file s 16 --build Warning: renaming static method 'toString' on class java.lang.Integer to 'toString_' since it is shadowed by non-static method of same name. Warning: renaming static method 'getCurrentSegmentFileName' on class org.apache.lucene.index.SegmentInfos to 'getCurrentSegmentFileName_' since it is shadowed by non-static method of same name. Warning: renaming static method 'copy' on class org.apache.lucene.store.Directory to 'copy_' since it is shadowed by non-static method of same name. Warning: renaming static method 'isInfinite' on class java.lang.Double to 'isInfinite_' since it is shadowed by non-static method of same name. Warning: renaming static method 'isNaN' on class java.lang.Double to 'isNaN_' since it is shadowed by non-static method of same name. Warning: renaming static method 'toString' on class java.lang.Double to 'toString_' since it is shadowed by non-static method of same name. Warning: renaming static method 'getCommitUserData' on class org.apache.lucene.index.IndexReader to 'getCommitUserData_' since it is shadowed by non-static method of same name. Traceback (most recent call last): File /usr/lib/python2.6/runpy.py, line 122, in _run_module_as_main __main__, fname, loader, pkg_name) File /usr/lib/python2.6/runpy.py, line 34, in _run_code exec code in run_globals File /usr/lib/python2.6/dist-packages/jcc/__main__.py, line 104, in module cpp.jcc(sys.argv) File /usr/lib/python2.6/dist-packages/jcc/cpp.py, line 644, in jcc raise ValueError, (cls, 'python class name already in use, use --rename', name, pythonNames[name]) ValueError: (Class: class org.apache.lucene.analysis.nl.DutchStemmer, 'python class name already in use, use --rename', u'DutchStemmer', Class: class org.tartarus.snowball.ext.DutchStemmer) make[2]: *** [compile] Error 255 The full log is attached along with the output of dpkg -l (from the chroot). It is possibly related to the recent upload of jcc (2 days ago). ~Niels dpkg-buildpackage: source package pylucene dpkg-buildpackage: source version 3.5.0-1 dpkg-buildpackage: source changed by Dmitry Nezhevenko d...@dion.org.ua dpkg-source --before-build pylucene-3.5.0 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh clean --with python2 dh_testdir debian/rules override_dh_auto_clean make[1]: Entering directory `builddir/pylucene-3.5.0' rm -rf dist lucene.egg-info for inter in python2.6 python2.7; do \ PYTHON=$inter JCC=$inter -m jcc make clean || exit $? ; \ rm -rf build-$inter; \ done make[2]: Entering directory `builddir/pylucene-3.5.0' if test -f lucene-java-3.5.0/lucene/build.xml; then cd lucene-java-3.5.0/lucene; ant clean; fi Buildfile: builddir/pylucene-3.5.0/lucene-java-3.5.0/lucene/build.xml clean:
Bug#677565: msva-perl: Insecure dependency in socket while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 80
On Thu, Jun 28, 2012 at 12:49:17AM +0200, intrigeri wrote: Hi, Iain Lane wrote (27 Jun 2012 22:30:40 GMT) : Where can I find these commits? There: git://lair.fifthhorseman.net/~dkg/msva-perl (Yeah, I know, that's not obvious.) Got it, thanks. Seems to fix it indeed, and if the other commit fixes the Use of uninitialized value warning (looked at the code but didn't test it) then we might as well include that too IMHO. I guess getting a freeze unblock wouldn't be a problem for this, but we should nevertheless try and get uploaded before then. Can you ping dkg in #monkeysphere? Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] PhD student [ i...@cs.nott.ac.uk ] signature.asc Description: Digital signature
Processed: retitle 679368 to pylucene: FTBFS python class name already in use
Processing commands for cont...@bugs.debian.org: retitle 679368 pylucene: FTBFS python class name already in use Bug #679368 [src:pylucene] pylucene: FTBFS python class name already in us Changed Bug title to 'pylucene: FTBFS python class name already in use' from 'pylucene: FTBFS python class name already in us' thanks Stopping processing here. Please contact me if you need assistance. -- 679368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679368 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#674327: marked as done (yard: FTBFS: test failed)
Your message dated Thu, 28 Jun 2012 09:13:01 + with message-id e1skamb-0006op...@franck.debian.org and subject line Bug#674327: fixed in yard 0.8.2.1-1 has caused the Debian Bug report #674327, regarding yard: FTBFS: test failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 674327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: yard Version: 0.8.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 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»' dh_auto_install Entering dh_ruby --install install -d /«PKGBUILDDIR»/debian/yard/usr/bin install -D -m755 bin/yri /«PKGBUILDDIR»/debian/yard/usr/bin/yri install -D -m755 bin/yard /«PKGBUILDDIR»/debian/yard/usr/bin/yard install -D -m755 bin/yardoc /«PKGBUILDDIR»/debian/yard/usr/bin/yardoc install -d /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby install -D -m644 lib/yard/serializers/stdout_serializer.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/serializers/stdout_serializer.rb install -D -m644 lib/yard/serializers/yardoc_serializer.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/serializers/yardoc_serializer.rb install -D -m644 lib/yard/serializers/process_serializer.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/serializers/process_serializer.rb install -D -m644 lib/yard/serializers/file_system_serializer.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/serializers/file_system_serializer.rb install -D -m644 lib/yard/serializers/base.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/serializers/base.rb install -D -m644 lib/yard/verifier.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/verifier.rb install -D -m644 lib/yard/code_objects/root_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/root_object.rb install -D -m644 lib/yard/code_objects/method_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/method_object.rb install -D -m644 lib/yard/code_objects/constant_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/constant_object.rb install -D -m644 lib/yard/code_objects/extra_file_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/extra_file_object.rb install -D -m644 lib/yard/code_objects/module_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/module_object.rb install -D -m644 lib/yard/code_objects/base.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/base.rb install -D -m644 lib/yard/code_objects/class_variable_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/class_variable_object.rb install -D -m644 lib/yard/code_objects/extended_method_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/extended_method_object.rb install -D -m644 lib/yard/code_objects/proxy.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/proxy.rb install -D -m644 lib/yard/code_objects/namespace_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/namespace_object.rb install -D -m644 lib/yard/code_objects/class_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/class_object.rb install -D -m644 lib/yard/code_objects/macro_object.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/code_objects/macro_object.rb install -D -m644 lib/yard/rake/yardoc_task.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/rake/yardoc_task.rb install -D -m644 lib/yard/server/rack_adapter.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/server/rack_adapter.rb install -D -m644 lib/yard/server/webrick_adapter.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/server/webrick_adapter.rb install -D -m644 lib/yard/server/router.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/server/router.rb install -D -m644 lib/yard/server/templates/default/layout/html/setup.rb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/server/templates/default/layout/html/setup.rb install -D -m644 lib/yard/server/templates/default/layout/html/breadcrumb.erb /«PKGBUILDDIR»/debian/yard/usr/lib/ruby/vendor_ruby/yard/server/templates/default/layout/html/breadcrumb.erb
Bug#576972: Workaround implemented in atlas 3.8.4-8
Hi, It seems impossible to elegantly solve this bug without having hooks in update-alternatives (a wishlist bug is filed for that). In the meantime, a workaround has been implemented in order to minimize the incidence of this bug. Starting from version 3.8.4-8 of Atlas, the Lapack alternative provided by Atlas has a lower priority than the one provided by Netlib's reference Lapack. That means that the bug will never hit as long as the alternatives are left in automatic mode (which is the default). The downside is that one won't automatically benefit from the optimizations made by Atlas into Lapack, unless the alternative is manually modified. The decision to implement this solution has been made jointly by Sylvestre Ledru (maintainer), Julien Cristau (Release Team) and myself, during the Debian Science Sprint kindly sponsored by ESRF, Grenoble, France. -- Sébastien Villemot Researcher in Economics Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594 pgpfdNykkXVcb.pgp Description: PGP signature
Processed: severity
Processing commands for cont...@bugs.debian.org: package latexila Limiting to bugs with field 'package' containing at least one of 'latexila' Limit currently set to 'package':'latexila' severity 679376 grave Bug #679376 [latexila] latexila fails to start Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 679376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679376 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#677391: marked as done (latex-beamer: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2))
Your message dated Thu, 28 Jun 2012 09:36:36 +
with message-id e1skb9q-000444...@franck.debian.org
and subject line Bug#677391: fixed in latex-beamer 3.10-2
has caused the Debian Bug report #677391,
regarding latex-beamer: 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.)
--
677391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: latex-beamer
Version: 3.10-1
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
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
latex-beamer_3.10-1.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: latex-beamer
Source-Version: 3.10-2
We believe that the bug you reported is fixed in the latest version of
latex-beamer, which is due to be installed in the Debian FTP archive:
latex-beamer_3.10-2.diff.gz
to main/l/latex-beamer/latex-beamer_3.10-2.diff.gz
latex-beamer_3.10-2.dsc
to main/l/latex-beamer/latex-beamer_3.10-2.dsc
latex-beamer_3.10-2_all.deb
to main/l/latex-beamer/latex-beamer_3.10-2_all.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 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
OHURA Makoto oh...@debian.org (supplier of updated latex-beamer 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: Thu, 28 Jun 2012 18:11:26 +0900
Source: latex-beamer
Binary: latex-beamer
Architecture: source all
Version: 3.10-2
Distribution: unstable
Urgency: medium
Maintainer: OHURA Makoto oh...@debian.org
Changed-By: OHURA Makoto oh...@debian.org
Description:
latex-beamer - LaTeX class to produce presentations
Closes: 677391
Changes:
latex-beamer (3.10-2) unstable; urgency=medium
.
* Update Standards-Version.
* Drop debian/{postinst,postrm}, call dh_installtex in debian/rules,
and build depend on tex-common. This causes the package to
no longer create files in /usr/local (Closes: #677391).
* Update compatibility level of debhelper, 4 to 9.
* debian/rules: Add build-arch and build-indep targets.
* Drop debian/{preinst,prerm}, which are empty.
Checksums-Sha1:
b8a0bed86d4277313ea27c920e32ae00afb194ab 1038 latex-beamer_3.10-2.dsc
41f41524d8069a8db0a46f580ddcc480bade4816 3611 latex-beamer_3.10-2.diff.gz
ce8901604ea43edab756349c15ec916bfca64d77 2578804 latex-beamer_3.10-2_all.deb
Checksums-Sha256:
4476b31c85bc3320abac0fc444c56e941107b4f047c69ccf0b88086c4364624b 1038
latex-beamer_3.10-2.dsc
11c0d80cc5c7dd453ffb84f58cfcc6bebaabe68932f9d1c6f3b784fbaf081c85 3611
latex-beamer_3.10-2.diff.gz
285b0ebbc268f61c0880134e69886701394127f1b37ffd2f9d02a6f32e581b95 2578804
latex-beamer_3.10-2_all.deb
Files:
c020f697cf1b9e3ad2bb13599c06aebc 1038 tex optional latex-beamer_3.10-2.dsc
6f4d8681e52df18676f6f9a0ce57d4f9 3611 tex optional latex-beamer_3.10-2.diff.gz
056e85131e865d0491865aa445fb3e7d 2578804 tex optional
latex-beamer_3.10-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG
Processed: The fs caching problem is a big issue!
Processing commands for cont...@bugs.debian.org: severity 678956 grave Bug #678956 [owncloud] owncloud: Web File Browser: Duplicating folders Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 678956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678956 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#660260: Fwd: GDL seems to use non public symbols from plplot (Debian Wheezy freeze on Saturday)
Hi Sylwester, adding the Cc to the bug report and the others again. I just avoided all the Cc in my last mail because of the attachments (build log, etc.). On Thu, Jun 28, 2012 at 10:12:01AM +0200, Sylwester Arabas wrote: That's now in the CVS. Please test if it fixes the issue. Hrm, not sure if I got all files which belong to the patch. According to http://gnudatalanguage.cvs.sourceforge.net/viewvc/gnudatalanguage/gdl/src/?sortby=date I'd say Makefile.am, Makefile.in and plotting_surface.cpp have been modified and plot3d_nr.cpp has been removed. That's correct. Yeah, verified that this morning after my CVS checkout finally finished. ... Unfortunately it still doesn't build. It though fails elsewhere. Here's the relevant part inline with the whole log attached, too... Please try with the current CVS version: http://gnudatalanguage.cvs.sf.net/viewvc/gnudatalanguage/gdl/src/plotting_surface.cpp?r1=1.7r2=1.8sortby=date Will do, thanks for your effort. I was testing it yesterday on Debian with plplot 5.9.5-4. That's the version from Debian stable which AFAIK has no -fvisibility=hidden which causes the linking issues. I've just tested the current version with plplot 5.9.5-4 as well. After upgrading to 5.9.9-4 I have non-related linking problems: gdl-image.o: In function `lib::loadct(EnvT*)': /usr/local/src/gdl/src/image.cpp:90: undefined reference to `plstream::scmap1(int*, int*, int*, int)' gdl-plotting_xyouts.o: In function `lib::xyouts_call::old_body(EnvT*, GDLGStream*)': /usr/local/src/gdl/src/plotting_xyouts.cpp:256: undefined reference to `plP_mmpcy' /usr/local/src/gdl/src/plotting_xyouts.cpp:341: undefined reference to `plP_mmpcx' /usr/local/src/gdl/src/plotting_xyouts.cpp:328: undefined reference to `plstrl' /usr/local/src/gdl/src/plotting_xyouts.cpp:288: undefined reference to `plstrl' Yes, it fails at that point now for me, too: /bin/bash ../libtool --tag=CXX --mode=link x86_64-linux-gnu-g++ -g -O2 -Wl,-z,defs -fopenmp -lMagick++ -lMagickCore -rdynamic -Wl,-z,muldefs -o gdl gdl-allix.o gdl-assocdata.o gdl-basic_fun_cl.o gdl-basic_fun.o gdl-basic_fun_jmg.o gdl-basic_op.o gdl-basic_op_new.o gdl-basic_pro.o gdl-basic_pro_jmg.o gdl-CFMTLexer.o gdl-color.o gdl-convert2.o gdl-datatypes.o gdl-dcommon.o gdl-dcompiler.o gdl-default_io.o gdl-dinterpreter.o gdl-dnode.o gdl-dpro.o gdl-dstructdesc.o gdl-dstructgdl.o gdl-dvar.o gdl-envt.o gdl-extrat.o gdl-FMTIn.o gdl-FMTLexer.o gdl-fmtnode.o gdl-FMTOut.o gdl-FMTParser.o gdl-gdleventhandler.o gdl-gdlexception.o gdl-gdlgstream.o gdl-GDLInterpreter.o gdl-GDLLexer.o gdl-GDLParser.o gdl-gdlpsstream.o gdl-gdlsvgstream.o gdl-gdlpython.o gdl-GDLTreeParser.o gdl-gdlwinstream.o gdl-gdlxstream.o gdl-getfmtast.o gdl-graphics.o gdl-gsl_fun.o gdl-ifmt.o gdl-initct.o gdl-initsysvar.o gdl-io.o gdl-libinit_cl.o gdl-libinit.o gdl-libinit_jmg.o gdl-math_fun.o gdl-math_fun_jmg.o gdl-math_utl.o gdl-ncdf_att_cl.o gdl-ncdf_cl.o gdl-ncdf_dim_cl.o gdl-ncdf_var_cl.o gdl-new.o gdl-objects.o gdl-ofmt.o gdl-math_fun_ac.o gdl-libinit_ac.o gdl-math_fun_gm.o gdl-libinit_gm.o gdl-math_fun_ng.o gdl-libinit_ng.o gdl-plotting.o gdl-print.o gdl-print_tree.o gdl-read.o gdl-str.o gdl-terminfo.o gdl-topython.o gdl-typetraits.o gdl-hdf_fun.o gdl-hdf_pro.o gdl-magick_cl.o gdl-gdlwidget.o gdl-widget.o gdl-basegdl.o gdl-hdf5_fun.o gdl-libinit_mes.o gdl-file.o gdl-image.o gdl-gdljournal.o gdl-convol.o gdl-convol_inc0.o gdl-convol_inc1.o gdl-convol_inc2.o gdl-sigfpehandler.o gdl-gdlzstream.o gdl-arrayindex.o gdl-fftw.o gdl-mpi.o gdl-grib.o gdl-prognode.o gdl-prognode_lexpr.o gdl-prognodeexpr.o gdl-datatypesref.o gdl-lapack.o gdl-gshhs.o gdl-newprognode.o gdl-plotting_plot.o gdl-plotting_oplot.o gdl-plotting_device.o gdl-plotting_cursor.o gdl-plotting_contour.o gdl-plotting_surface.o gdl-plotting_axis.o gdl-plotting_plots.o gdl-plotting_xyouts.o gdl-plotting_polyfill.o gdl-plotting_windows.o gdl-plotting_convert_coord.o gdl-plotting_map_proj.o gdl-plotting_misc.o gdl-plotting_erase.o gdl-semshm.o gdl-gdl.o gdl-lapack.o /usr/lib/libantlr.a -L/usr/X11R6/lib64 -L/usr/X11R6/lib -lX11 -lmfhdfalt -lgslcblas -lgsl -lncurses -ldl -ldl -lreadline -lz -lgsl -lgslcblas -lplplotd -lplplotcxxd -L/usr/lib/x86_64-linux-gnu -pthread -L/usr/lib/x86_64-linux-gnu -lwx_gtk2u_richtext-2.8 -lwx_gtk2u_aui-2.8 -lwx_gtk2u_xrc-2.8 -lwx_gtk2u_qa-2.8 -lwx_gtk2u_html-2.8 -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 -lwx_baseu_xml-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8 -lMagick++ -lMagickCore -L/usr/lib/netcdf-3 -lnetcdf -L/usr/lib/hdf -lmfhdfalt -ldfalt -ljpeg -lz -L/usr/lib/hdf -L/usr/lib/hdf5 -lhdf5 -lfftw3 -lfftw3f -lpython2.7 -ludunits2 -lgrib_api -lps libtool: link: x86_64-linux-gnu-g++ -g -O2 -Wl,-z -Wl,defs -fopenmp -rdynamic -Wl,-z -Wl,muldefs -o gdl gdl-allix.o gdl-assocdata.o gdl-basic_fun_cl.o gdl-basic_fun.o gdl-basic_fun_jmg.o gdl-basic_op.o gdl-basic_op_new.o gdl-basic_pro.o gdl-basic_pro_jmg.o gdl-CFMTLexer.o gdl-color.o
Bug#677543: dependency not added
A couple of hours ago I did a upgrade of guake ( grep guake /var/log/aptitude shows me [UPGRADE] guake:amd64 0.4.2-10 - 0.4.3-2 ) and know i get: Traceback (most recent call last): File /usr/bin/guake, line 35, in module from xdg.DesktopEntry import DesktopEntry ImportError: No module named xdg.DesktopEntry when starting guake (guake worked fine in 0.4.2-10). Bug 677543 and 676629 (that are dups of each other) tell me that a dependency on python-xdg has been added in 0.4.3-2 but i believe this is not the case. the guake upgrade went fine here (I'm running wheezy) but python-xdg was not installed, also http://packages.debian.org/wheezy/guake doesn't list python-xdg as a dependency. Installing python-xdg fixes the bug, so could you add it as a dependency ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679376: Bug#679363: latexila window can't be resized
package latexila tag 679376 + moreinfo thanks Tanguy Ortolo, 2012-06-28 11:15+0200: This is a grave issue, and I think I reproduce it, only it is systematic here. Can you run latexila from a terminal emulator and send me the output when it fails to start? Well in fact I cannot reproduce it, latexila was failing here for local reasons (specifically, obsolete remaining GSettings schemas from an old local installation of LaTeXila). So, I rely on you for providing me the details. -- ,--. : /` ) Tanguy Ortolo xmpp:tan...@ortolo.eu irc://irc.oftc.net/Tanguy | `-'Debian Developer \_ signature.asc Description: Digital signature
Processed: Re: Bug#679376: Bug#679363: latexila window can't be resized
Processing commands for cont...@bugs.debian.org: package latexila Limiting to bugs with field 'package' containing at least one of 'latexila' Limit currently set to 'package':'latexila' tag 679376 + moreinfo Bug #679376 [latexila] latexila fails to start Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 679376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679376 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#679394: src:beast-mcmc: package name beast-doc already in use by src:beast
Source: beast-mcmc Version: 1.6.2-1 Severity: serious beast-mcmc builds the binary package beast-doc. However this is also built by the beast source package (and already was before beast-mcmc entered the archive). Please rename the binary. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679400: [deal.ii] FTBFS: call of overloaded constructor is ambiguous
Source: deal.ii Version: 7.1.0-1 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 thanks the deal.ii package builds fine with gcc-4.6/g++-4.6, but when building with gcc-4.7/g++-4.7, I get the following error messages: ==optimized==MT== fe/fe_values.cc /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc: In instantiation of 'void dealii::FEValuesBasedim, spacedim::maybe_invalidate_previous_present_cell(const typename dealii::Triangulationdim, spacedim::cell_iterator) [with int dim = 1; int spacedim = 1; typename dealii::Triangulationdim, spacedim::cell_iterator = dealii::TriaIteratordealii::CellAccessor1, 1 ]': /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.inst:2:17: required from here /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:3265:5: error: call of overloaded 'TriaIterator(std::auto_ptrconst dealii::FEValuesBase1::CellIteratorBase::element_type)' is ambiguous /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:3265:5: note: candidates are: In file included from /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.h:1322:0, from /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:23: /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.templates.h:172:1: note: dealii::TriaIterator template-parameter-1-1 ::TriaIterator(const dealii::TriaRawIteratorAccessor) [with Accessor = dealii::CellAccessor1, 1] /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.templates.h:165:1: note: dealii::TriaIterator template-parameter-1-1 ::TriaIterator(const dealii::TriaIterator template-parameter-1-1 ) [with Accessor = dealii::CellAccessor1, 1] /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc: In instantiation of 'void dealii::FEValuesBasedim, spacedim::maybe_invalidate_previous_present_cell(const typename dealii::Triangulationdim, spacedim::cell_iterator) [with int dim = 1; int spacedim = 2; typename dealii::Triangulationdim, spacedim::cell_iterator = dealii::TriaIteratordealii::CellAccessor1, 2 ]': /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.inst:15:17: required from here /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:3265:5: error: call of overloaded 'TriaIterator(std::auto_ptrconst dealii::FEValuesBase1, 2::CellIteratorBase::element_type)' is ambiguous /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:3265:5: note: candidates are: In file included from /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.h:1322:0, from /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:23: /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.templates.h:172:1: note: dealii::TriaIterator template-parameter-1-1 ::TriaIterator(const dealii::TriaRawIteratorAccessor) [with Accessor = dealii::CellAccessor1, 2] /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.templates.h:165:1: note: dealii::TriaIterator template-parameter-1-1 ::TriaIterator(const dealii::TriaIterator template-parameter-1-1 ) [with Accessor = dealii::CellAccessor1, 2] /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc: In instantiation of 'void dealii::FEValuesBasedim, spacedim::maybe_invalidate_previous_present_cell(const typename dealii::Triangulationdim, spacedim::cell_iterator) [with int dim = 2; int spacedim = 2; typename dealii::Triangulationdim, spacedim::cell_iterator = dealii::TriaIteratordealii::CellAccessor2, 2 ]': /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.inst:42:17: required from here /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:3265:5: error: call of overloaded 'TriaIterator(std::auto_ptrconst dealii::FEValuesBase2::CellIteratorBase::element_type)' is ambiguous /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:3265:5: note: candidates are: In file included from /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.h:1322:0, from /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:23: /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.templates.h:172:1: note: dealii::TriaIterator template-parameter-1-1 ::TriaIterator(const dealii::TriaRawIteratorAccessor) [with Accessor = dealii::CellAccessor2, 2] /tmp/buildd/deal.ii-7.1.0/include/deal.II/grid/tria_iterator.templates.h:165:1: note: dealii::TriaIterator template-parameter-1-1 ::TriaIterator(const dealii::TriaIterator template-parameter-1-1 ) [with Accessor = dealii::CellAccessor2, 2] /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc: In instantiation of 'void dealii::FEValuesBasedim, spacedim::maybe_invalidate_previous_present_cell(const typename dealii::Triangulationdim, spacedim::cell_iterator) [with int dim = 2; int spacedim = 3; typename dealii::Triangulationdim, spacedim::cell_iterator = dealii::TriaIteratordealii::CellAccessor2, 3 ]': /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.inst:55:17: required from here /tmp/buildd/deal.ii-7.1.0/source/fe/fe_values.cc:3265:5: error: call of overloaded 'TriaIterator(std::auto_ptrconst dealii::FEValuesBase2, 3::CellIteratorBase::element_type)' is ambiguous
Bug#660260: Fwd: GDL seems to use non public symbols from plplot (Debian Wheezy freeze on Saturday)
Hi Axel, On 28/06/12 12:19, Axel Beckert wrote: ... /home/abe/gnudatalanguage/gnudatalanguage/src/plotting_xyouts.cpp:260: undefined reference to `plP_mmpcy' /home/abe/gnudatalanguage/gnudatalanguage/src/plotting_xyouts.cpp:332: undefined reference to `plstrl' /home/abe/gnudatalanguage/gnudatalanguage/src/plotting_xyouts.cpp:345: undefined reference to `plP_mmpcx' /home/abe/gnudatalanguage/gnudatalanguage/src/plotting_xyouts.cpp:292: undefined reference to `plstrl' collect2: error: ld returned 1 exit status ... are the above critical for this week? Well, it's way easier to get it into Wheezy if I upload the package before the Freeze on Saturday evening. I can try to get it in later, but I can't promise it, I'm sorry. If more time helps to get the thing fixed for sure, I can ask the release team in advance for a freeze exception. But again no promises. I've just asked on plplot mailing list about it: https://sourceforge.net/projects/plplot/forums/forum/132889/topic/5389011 Both plstrl and plP_mmpcx are used in GDL to handle the WIDTH keyword to the XYOUTS procedure. That's surely not a vital feature of GDL so perhaps you can simply comment it out from the GDL source code for Debian packaging while waiting for a proper solution. Such patch would basically undo this commit: http://gnudatalanguage.cvs.sf.net/viewvc/gnudatalanguage/gdl/src/plotting.cpp?hideattic=0r1=1.127r2=1.128 HTH, Sylwester -- http://www.igf.fuw.edu.pl/~slayoo/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679376: Bug#679363: latexila window can't be resized
Patrick Winnertz, 2012-06-28 14:07+0200: okay, which details do you want to have? If I start latexila from cmd I've see basically no output there. I understood that latexila failed to start 9 times over 10, so I duplicated your bug report into two: #679376 - latexila fails to start #679363 - latexila window can't be resized However I was able to figure out some systematics in the behaviour.. to illustrate that I've made several screenshots - think this is easier than describing the issue with words. Yes, I understand, however you sent that to the wrong bug. I understand the problem in #679363 and I shall try to reproduce it. With #679376 (the current one) however, I am unable to reproduce and I would need the output of latexila when it fails to start. -- ,--. : /` ) Tanguy Ortolo xmpp:tan...@ortolo.eu irc://irc.oftc.net/Tanguy | `-'Debian Developer \_ signature.asc Description: Digital signature
Processed: Re: Bug#679376: Bug#679363: latexila window can't be resized
Processing commands for cont...@bugs.debian.org: package latexila Limiting to bugs with field 'package' containing at least one of 'latexila' Limit currently set to 'package':'latexila' forcemerge 679363 679376 Bug #679363 [latexila] latexila window can't be resized Bug #679363 [latexila] latexila window can't be resized Added tag(s) moreinfo. Bug #679376 [latexila] latexila fails to start Severity set to 'normal' from 'grave' Merged 679363 679376 thanks Stopping processing here. Please contact me if you need assistance. -- 679363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679363 679376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679376 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: your mail
Processing commands for cont...@bugs.debian.org: severity 651926 serious Bug #651926 [libdvdread4] segfault in libdvdread when opening directories Severity set to 'serious' from 'normal' severity 677493 serious Bug #677493 [src:libdvdread] libdvdread: Solving problems for 64bit systems Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 651926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651926 677493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677493 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#679122: manpages-de: FTBFS without internet access
Am 26.06.2012 15:37, schrieb Jeremy Bicha: It looks like manpages-de fails to build if english/download-packages.sh can't download packages from the Internet. This causes manpages-de to fail to build on Ubuntu or any builder without internet access. Hi Jeremy, thanks for the bug report, I'm working on a fix. Regards, Tobias signature.asc Description: OpenPGP digital signature
Bug#679409: lightdm: Fails to start on boot, invoke-rc.d lightdm start fails
Package: lightdm Version: 1.2.2-3 Severity: grave Justification: renders package unusable With sysvinit 2.88dsf-22.1, lightdm fails to start, and invoke-rd.d lightdm start fails with the message start: Job failed to start. Using startx does work, so the issue isn't with X. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.5-3 ii dbus 1.6.2-1 ii debconf [debconf-2.0] 1.5.44 ii libc6 2.13-33 ii libglib2.0-0 2.32.3-1 ii libpam0g 1.1.3-7.1 ii libxcb11.8.1-1 ii libxdmcp6 1:1.1.1-1 ii lightdm-gtk-greeter1.1.6-2 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+1 Versions of packages lightdm suggests: ii accountsservice 0.6.21-5 -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660260: Fwd: GDL seems to use non public symbols from plplot (Debian Wheezy freeze on Saturday)
Hi! Sylwester Arabas wrote: Both plstrl and plP_mmpcx are used in GDL to handle the WIDTH keyword to the XYOUTS procedure. That's surely not a vital feature of GDL so perhaps you can simply comment it out from the GDL source code for Debian packaging while waiting for a proper solution. Such patch would basically undo this commit: http://gnudatalanguage.cvs.sf.net/viewvc/gnudatalanguage/gdl/src/plotting.cpp?hideattic=0r1=1.127r2=1.128 Ok, with this advice I got at least one incremental build working. Yay! Now I'm trying to get a clean package out of it. :-) Will keep you informed. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679409: [Pkg-xfce-devel] Bug#679409: lightdm: Fails to start on boot, invoke-rc.d lightdm start fails
On jeu., 2012-06-28 at 23:27 +1000, James Tocknell wrote: Package: lightdm Version: 1.2.2-3 Severity: grave Justification: renders package unusable With sysvinit 2.88dsf-22.1, lightdm fails to start, and invoke-rd.d lightdm start fails with the message start: Job failed to start. Using startx does work, so the issue isn't with X. What if you downgrade to previous sysvinit? It looks to me like an issue there. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#618968: Ping - netgen license problems
begin quotation from Francesco Poli (in 20120625215725.69523c3a3df0a27f62672...@paranoici.org): On Mon, 25 Jun 2012 10:36:50 +0200 Arne Wichmann wrote: So, at least as far as I can see, there are a number of things to be done in various time frames: - Alert enough people to the problem (via debian-user, messages in the packaging, other mailing lists and similar means) I am not sure debian-user is the appropriate place for such a call for help... Well, if you are trying to reach your users, this seems to be a possible vector to me What do you mean by messages in the packaging? At least I get mails by apt-listchanges... Other tactics may also be available - but I am not the epigon of debian packaging. As far as other mailing lists are concerned, I tried to see if other debian-legal participants could join me in this persuasion effort, but I unfortunately received no reply: I do not think that debian-legal is a good starting point for a massive campaign. Maybe debian-science could be another appropriate mailing list, but I suspect that a good number of its participants are already aware of the issue, due to the various bug reports filed against packages maintained by the Debian Science team: #617613, #617931, and #618968 (that is to say, this one). A mail there might still help a bit. - Remove the package from debian if nothing happens. I am trying hard to avoid this, but I am failing to get help from other people... That's really frustrating! :-( *sigh* cu AW -- [...] If you don't want to be restricted, don't agree to it. If you are coerced, comply as much as you must to protect yourself, just don't support it. Noone can free you but yourself. (crag, on Debian Planet) Arne Wichmann (a...@linux.de) signature.asc Description: Digital signature
Bug#679416: Offlineimap duplicates messages
Package: offlineimap
Version: 6.5.4-2
Severity: grave
Justification: causes data loss / breaks integrity of mail archive
Offlineimap regularly duplicates messages, that's to say, it copies a message
twice from the remote host to the local folder. It then complains if a local
program (such as imapfilter) moves or deletes them.
This leads to data loss (i.e. loss of the integrity of my mail archive) since,
whenever imapfilter runs on such a state, it copies the duplicates to their
appropriate folders, and so I end up with duplicates of debian-devel messages
in my Debian.debian-devel folder, etc.
Attached offlineimap log:
| Account sync McGill:
| Next refresh in 13.0 minutes
| Thread-989:
| Syncing INBOX: Gmail - MappedIMAP
| Thread-988:
| Syncing INBOX: Gmail - MappedIMAP
| Thread-989:
| Copy message 341595 (1 of 2) RemoteGmail:INBOX - LocalGmail
| Copy message 341596 (2 of 2) RemoteGmail:INBOX - LocalGmail
| Thread-988:
| Copy message 341595 (1 of 2) RemoteGmail:INBOX - LocalGmail
| Copy message 341596 (2 of 2) RemoteGmail:INBOX - LocalGmail
| Thread-989:
| Deleting 3 messages (341591:341592,341594) in Gmail[INBOX]
| Thread-988:
| Deleting 3 messages (341591:341592,341594) in Gmail[INBOX]
| Thread-989:
| Adding flag S to 1 messages on INBOX
| Thread-988:
| Adding flag S to 1 messages on INBOX
| Syncing INBOX: Gmail - MappedIMAP
| Copy message -2 (1 of 2) LocalGmail:INBOX - RemoteGmail
| Copy message -1 (2 of 2) LocalGmail:INBOX - RemoteGmail
| Adding flag S to 1 messages on INBOX
| Account sync GMAIL:
| Next refresh in 10.0 minutes
SNIP ~ 4 minutes
In this 4 minute window, imapfilter was run.
| Account sync McGill:
| Next refresh in 8.0 minutes
| Thread-988:
| ERROR: ERROR in syncfolder for GMAIL folder INBOX: Traceback (most recent
call last):
| File /usr/lib/python2.7/dist-packages/offlineimap/accounts.py, line 388,
in syncfolder
| if localfolder.get_uidvalidity() == None:
| File /usr/lib/python2.7/dist-packages/offlineimap/folder/IMAP.py, line
78, in get_uidvalidity
| response('UIDVALIDITY') returned [None]!
| AssertionError: response('UIDVALIDITY') returned [None]!
|
| response('UIDVALIDITY') returned [None]!
| Thread-989:
| Syncing INBOX: Gmail - MappedIMAP
| Thread-988:
| Syncing INBOX: Gmail - MappedIMAP
| Thread-989:
| Copy message 341599 (1 of 3) RemoteGmail:INBOX - LocalGmail
| Copy message 341600 (2 of 3) RemoteGmail:INBOX - LocalGmail
| Thread-988:
| Copy message 341599 (1 of 3) RemoteGmail:INBOX - LocalGmail
| Thread-989:
| Copy message 341601 (3 of 3) RemoteGmail:INBOX - LocalGmail
| Thread-988:
| Copy message 341600 (2 of 3) RemoteGmail:INBOX - LocalGmail
| Copy message 341601 (3 of 3) RemoteGmail:INBOX - LocalGmail
| Thread-989:
| Deleting 2 messages (341595:341596) in MappedIMAP[INBOX]
| ERROR: Could not find UID for msg '341595' (f:'INBOX'. This is usually a bad
thing and should be reported on the mailing list.
| Deleting 4 messages (341546,341575,341597:341598) in Gmail[INBOX]
| Thread-988:
| Deleting 2 messages (341595:341596) in MappedIMAP[INBOX]
| ERROR: Could not find UID for msg '341595' (f:'INBOX'. This is usually a bad
thing and should be reported on the mailing list.
| Deleting 4 messages (341546,341575,341597:341598) in Gmail[INBOX]
My offlineimaprc is attached, and is available in its current incarnation
online[0]
[0]
https://github.com/ryanakca/ryanakca-dotfiles/blob/011775446e5af983e024b8c8bc0277d0d6ef850d/.offlineimaprc.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to es_ES.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages offlineimap depends on:
ii libjs-sphinxdoc 1.1.3+dfsg-4
ii python 2.7.3~rc2-1
ii python2.62.6.8-0.1
ii python2.72.7.3-1
Versions of packages offlineimap recommends:
pn python-sqlite none
Versions of packages offlineimap suggests:
ii doc-base 0.10.4
pn python-kerberos none
-- no debconf information
# Sample minimal config file. Copy this to ~/.offlineimaprc and edit to
# suit to get started fast.
[general]
metadata = ~/.offlineimap
accounts = GMAIL, QueensU, McGillSOCS, McGill
#, GMAIL
pythonfile=~/.offlineimap.py
# EIMEAR
maxsyncaccounts = 5
GMAIL Account Settings
[Account GMAIL]
localrepository = LocalGmail
remoterepository = RemoteGmail
autorefresh = 20
quick = 10
presynchook = imapfilter -c /home/ryan/.imapfilter/config.lua
postsynchook = imapfilter -c /home/ryan/.imapfilter/config.lua
/home/ryan/bin/run-mailcheck notmuch new
foldersort = mycmp
[Repository LocalGmail]
#type = Maildir
#localfolders = ~/.maildb/GMAIL
#restoreatime = no
type = IMAP
remotehost = localhost
remoteuser = ryan
remotepass = LOCAL_PASS
folderfilter = lambda folder: folder not in ['[Google Mail]/All
Bug#555168: Unclear license situation for (e)glibc locales provided by you
Hello, you are listed as contact person/author of the following locale: se_NO This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 this locale could strictly speaking not be part of Debian which would be a great loss. (Currently it is allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense this locale to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#555168: Unclear license situation for (e)glibc locales provided by you
Hello, you are listed as contact person/author of the following locale: shs_CA This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 this locale could strictly speaking not be part of Debian which would be a great loss. (Currently it is allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense this locale to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#555168: Unclear license situation for (e)glibc locales provided by you
Hello, you are listed as contact person/author of the following locale: sk_SK This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 this locale could strictly speaking not be part of Debian which would be a great loss. (Currently it is allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense this locale to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#555168: Unclear license situation for (e)glibc locales provided by you
Hello, you are listed as contact person/author of the following locale: sl_SI This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 this locale could strictly speaking not be part of Debian which would be a great loss. (Currently it is allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense this locale to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#678644: Upstream request: new upload or remove from archive (security reasons)
Package: zoph Followup-For: Bug #678644 Hi, FWIW zoph is orphaned now, feel free to adopt it: http://bugs.debian.org/679417 regards, -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (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#664915: marked as done (tcsh: FTBFS: test 122 Filename substitution failed)
Your message dated Thu, 28 Jun 2012 17:15:54 +0200
with message-id 20460.29994.728192.118...@malzmuehle.informatik.uni-koeln.de
and subject line
has caused the Debian Bug report #664915,
regarding tcsh: FTBFS: test 122 Filename substitution failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
664915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: tcsh
Version: 6.18.01-1
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:
gcc -o tcsh -Wl,-z,relro -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -D_FILE_OFFSET_BITS=64 -I.
-I. sh.o sh.dir.o sh.dol.o sh.err.o sh.exec.o sh.char.o sh.exp.o sh.file.o
sh.func.o sh.glob.o sh.hist.o sh.init.o sh.lex.o sh.misc.o sh.parse.o
sh.print.o sh.proc.o sh.sem.o sh.set.o sh.time.o glob.o mi.termios.o
ma.setp.o vms.termcap.o tw.help.o tw.init.o tw.parse.o tw.spell.o tw.comp.o
tw.color.o ed.chared.o ed.refresh.o ed.screen.o ed.init.o ed.inputl.o
ed.defns.o ed.xmap.o ed.term.o tc.alloc.o tc.bind.o tc.const.o tc.defs.o
tc.disc.o tc.func.o tc.nls.o tc.os.o tc.printf.o tc.prompt.o tc.sched.o
tc.sig.o tc.str.o tc.vers.o tc.who.o -ltermcap -lcrypt
make[3]: Entering directory `/«PKGBUILDDIR»/nls'
C
et
finnish
french
german
greek
italian
ja
pl
russian
spanish
ukrainian
make[3]: Leaving directory `/«PKGBUILDDIR»/nls'
make[2]: Leaving directory `/«PKGBUILDDIR»'
/usr/bin/make catalogs
make[2]: Entering directory `/«PKGBUILDDIR»'
make[3]: Entering directory `/«PKGBUILDDIR»/nls'
make[3]: Nothing to be done for `catalogs'.
make[3]: Leaving directory `/«PKGBUILDDIR»/nls'
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: Leaving directory `/«PKGBUILDDIR»'
debian/rules override_dh_auto_test
make[1]: Entering directory `/«PKGBUILDDIR»'
LS_COLORS= make check || (cat testsuite.log ; false)
make[2]: Entering directory `/«PKGBUILDDIR»'
{\
echo '# Signature of the current package.'; \
echo 'm4_define([AT_PACKAGE_NAME], [tcsh])';\
echo 'm4_define([AT_PACKAGE_TARNAME], [tcsh])'; \
echo 'm4_define([AT_PACKAGE_VERSION], [6.18.01])'; \
echo 'm4_define([AT_PACKAGE_STRING],[tcsh 6.18.01])';\
echo 'm4_define([AT_PACKAGE_BUGREPORT], [http://bugs.gw.com/])'; \
} ./tests/package.m4
autom4te --language=autotest -I ./tests \
./tests/testsuite.at -o tests/testsuite.tmp
mv tests/testsuite.tmp tests/testsuite
/bin/sh ./tests/testsuite
## ##
## tcsh 6.18.01 test suite. ##
## ##
1: beepcmd skipped (aliases.at:3)
2: cwdcmd ok
3: jobcmd skipped (aliases.at:19)
4: helpcommand skipped (aliases.at:20)
5: periodicskipped (aliases.at:21)
6: precmd skipped (aliases.at:22)
7: postcmd ok
8: shell ok
9: -b ok
10: -c ok
11: -d skipped (arguments.at:34)
12: -e ok
13: -f skipped (arguments.at:46)
14: -i ok
15: -l skipped (arguments.at:61)
16: -m skipped (arguments.at:65)
17: -q skipped (arguments.at:71)
18: -s ok
19: -t ok
20: -v ok
21: -x ok
22: -V skipped
(arguments.at:126)
23: -X skipped
(arguments.at:127)
24: --help skipped
Bug#679242: wvdial: Failed assertion on startup
Same problem here but using a Huawei E1556 datacard I fix this problem by downgrading the libwvstreams packages to the versions on «stable» * libwvstreams4.6-base * libwvstreams4.6-extras -- Aurelio Sanabria acá, el alquiler barato... ¡Viva la colifata! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679428: vfdata-morisawa5 is not installable
Package: morisawa
Version: 0.0.20020122-14
Severity: serious
Tags: sid wheezy
Hi,
Since last TeX transition, vfdata-morisawa5 became not installable. An
analysis of the problem reveals the following broken dependency chain:
Package morisawa cannot migrate:
Package morisawa: binary package vfdata-morisawa5/sparc cannot migrate.
Package vfdata-morisawa5/sparc: a dependency would not be satisfied:
- texlive-lang-cjk conflicts with vfdata-morisawa5 {vfdata-morisawa5
(sid)}
- vfdata-morisawa5 (sid) depends on ptex-bin {ptex-bin}
- ptex-bin depends on texlive-lang-cjk (= 2011) {texlive-lang-cjk}
(Note that sparc is not important here. It is just an example of an
architecture where the problem exists).
This issue is also preventing dvi2ps-fontdesc-morisawa5 from migrating
to testing. If those packages are not needed anymore (or don't work
anymore), please request their removal from the archive.
Regards,
--
Mehdi
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679430: FTBS on arm
Package: imagemagick Version: 8:6.7.7.2-1 Severity: serious Imagemagick FTBS on arm CC magick/magick_libMagickCore_la-draw.lo CC magick/magick_libMagickCore_la-effect.lo CC magick/magick_libMagickCore_la-enhance.lo CC magick/magick_libMagickCore_la-exception.lo CC magick/magick_libMagickCore_la-feature.lo CC magick/magick_libMagickCore_la-fourier.lo CC magick/magick_libMagickCore_la-fx.lo CC magick/magick_libMagickCore_la-gem.lo magick/gem.c:610:21: error: conflicting types for 'GenerateDifferentialNoise' ./magick/gem.h:30:3: note: previous declaration of 'GenerateDifferentialNoise' was here make[2]: *** [magick/magick_libMagickCore_la-gem.lo] Error 1 make[2]: Leaving directory `/build/buildd-imagemagick_6.7.7.9-1-armel-66TJ9D/imagemagick-6.7.7.9' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-imagemagick_6.7.7.9-1-armel-66TJ9D/imagemagick-6.7.7.9' make: *** [build-stamp] Error 2 Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679272: bcfg2-server: unescaped shell command issues in the Trigger plugin
Florian Weimer f...@deneb.enyo.de writes: * Arto Jantunen: In Debian (and all other distros I know of) the bcfg2 server runs as root, so in practice this is a remote root hole (limited to attackers who can connect to the bcfg2 server (protected by a password and/or an ssl key)). .dsc and .debian.tar.gz for a fixed package are attached. I'll upload the fix to unstable next. There's a spurious diff in the changelog: bcfg2 (1.0.1-3+squeeze1) stable-security; urgency=high * Apply patch from Chris St. Pierre to fix several problems with -unescaped shell commands (Closes: #640028). +unescaped shell commands But the actual patch seems fine. Please build without -sa and upload to security-master. Thanks! I have fixed the mistake in the changelog, built the package and uploaded the result. -- Arto Jantunen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679433: boinc-app-seti: FTBFS: build depends on unavailable libboinc-app-dev
Source: boinc-app-seti Version: 6.12~svn1306-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automatic builds of boinc-app-seti are failing because it declares a build dependency on libboinc-app-dev, which is completely unavailable AFAICT. (I don't even see it in NEW or experimental.) Listing boinc-dev as an alternative doesn't help, because Debian's autobuilders are generally configured to ignore alternative build dependencies for the sake of consistency. (They consider them only when explicit architecture tags rule out preferred alternatives.) Could you please adjust boinc-app-seti's build dependencies to leave off libboinc-app-dev, or at least favor boinc-dev? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679250: marked as done (live-boot-initramfs-tools: Booting from tftp failes with init: line 218: mountroot: not found)
Your message dated Thu, 28 Jun 2012 17:52:47 +0200
with message-id 4fec7dcf.5090...@affinitas.de
and subject line Bug#679250: live-boot-initramfs-tools: Booting from tftp
failes with init: line 218: mountroot: not found fixed in unstable
has caused the Debian Bug report #679250,
regarding live-boot-initramfs-tools: Booting from tftp failes with init: line
218: mountroot: 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.)
--
679250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: live-boot-initramfs-tools
Version: 3.0~a33-1
Severity: grave
Tags: patch
Justification: renders package unusable
Because of the restructuring of the live-boot package there are some
issues with the initramfs hook. I have added a patch, wich will fix the
mentioned error.
Best regards,
Lars Eric Scheidler
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-backports'), (50, 'unstable'),
(50, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (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
diff -Naur live-boot-3.0~a33.orig/backends/initramfs-tools/live.hook live-boot-3.0~a33/backends/initramfs-tools/live.hook
--- live-boot-3.0~a33.orig/backends/initramfs-tools/live.hook 2012-06-07 08:56:53.0 +0200
+++ live-boot-3.0~a33/backends/initramfs-tools/live.hook 2012-06-27 14:45:32.431953235 +0200
@@ -42,7 +42,7 @@
# Handling live-boot
-if [ ! -e /usr/share/live-boot ]
+if [ ! -e /lib/live/boot ]
then
echo W: live-boot-initramfs-tools (backend) installed without live-boot,
echo W: this initramfs will *NOT* have live support.
diff -Naur live-boot-3.0~a33.orig/backends/initramfs-tools/live.script live-boot-3.0~a33/backends/initramfs-tools/live.script
--- live-boot-3.0~a33.orig/backends/initramfs-tools/live.script 2012-06-07 08:56:53.0 +0200
+++ live-boot-3.0~a33/backends/initramfs-tools/live.script 2012-06-27 14:45:32.523953685 +0200
@@ -4,5 +4,5 @@
if [ -e /lib/live/boot.sh ]
then
- /lib/live/boot.sh ${@}
+ . /lib/live/boot.sh ${@}
fi
---End Message---
---BeginMessage---
severity 679250 normal
Source: live-boot
Source-Version: 3.0~a34-1
The problem seems to be fixed in unstable.
--
Affinitas GmbH | Kohlfurter Straße 41/43 | 10999 Berlin | Germany
Geschäftsführer:
Lukas Brosseder, David Khalil, Christian Vollmann, Kai Rieke
Eingetragen beim Amtsgericht Berlin, HRB 115958
---End Message---
Bug#677700: [pkg-bacula-devel] Bug#677700: bacula-director-mysql: fails to upgrade from testing - Table 'bacula.Version' doesn't exist
Hi there! On Sun, 24 Jun 2012 19:04:19 +0200, Adam D. Barratt wrote: On Sun, 2012-06-24 at 15:52 +0200, Luca Capello wrote: On Sat, 16 Jun 2012 11:49:34 +0200, Andreas Beckmann wrote: during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails. Actually, I was not able to install bacula-director-mysql_5.0.3-1+b1 on a clean wheezy (CD-1_20120618-04:55; d-i_20120508) with the default mysql-server, i.e. 5.5: Andreas's log also shows that failure: [...] I'm therefore marking the bug as found in the version in testing, as trying to install that on a current wheezy will already fail. (The offending syntax appears to be fixed in a mysql-5.5 patch in bacula 5.2.) Thank you for the notice, I did not completely read Andreas's log, my fault. If anyone has a /working/ 5.0.3 install that they could try upgrading to 5.2.6, that would be helpful, just to confirm. FWIW I have already planned to test that during DebCamp. Thx, bye, Gismo / Luca pgpPYUnT6KvSF.pgp Description: PGP signature
Bug#673430: downgrading severity
severity 673430 important thanks since gnome-boxes is the only rdep and it has been recompiled against the newer libvirt-glib, I'm downgrading the severity so both packages can migrate to testing -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: [bts-link] source package at-spi2-atk
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package at-spi2-atk # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #678026 (http://bugs.debian.org/678026) # Bug title: libatk-adaptor: insecure tempdir handling # * http://bugzilla.gnome.org/show_bug.cgi?id=678348 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 678026 + fixed-upstream Bug #678026 [libatk-adaptor] libatk-adaptor: insecure tempdir handling Added tag(s) fixed-upstream. usertags 678026 - status-NEW Bug#678026: libatk-adaptor: insecure tempdir handling Usertags were: status-NEW. Usertags are now: . usertags 678026 + status-RESOLVED resolution-FIXED Bug#678026: libatk-adaptor: insecure tempdir handling There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 678026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678026 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: downgrading severity
Processing commands for cont...@bugs.debian.org: severity 673430 important Bug #673430 [libvirt-glib] gnome-boxes: Missing libraries Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 673430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673430 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#677700: [pkg-bacula-devel] Bug#677700: bacula-director-mysql: fails to upgrade from testing - Table 'bacula.Version' doesn't exist
Hi there! On Sun, 24 Jun 2012 15:52:43 +0200, Luca Capello wrote: This is caused by the fact that there is no MySQL server running yet. While this could be solved via a Pre-Depends: in bacula-director-mysql, this is actually not possible because the MySQL server could be on a remote location. BTW, this happens to bacula-director-pgsql, too. I just got it again by this while testing the squeeze-backports package. At least I discovered that the above was already discussed in #605449. Thx, bye, Gismo / Luca pgpJFAiVktrTr.pgp Description: PGP signature
Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)
On Tue, 19 Jun 2012, Steve McIntyre wrote: More debugging results: * If I replace -Os with -O0 to disable optimisation, the crash goes away too. Suggests (maybe) a compiler bug here... nasty. :| * There's a real bug in the ARM assembly version of longjmp in usr/klibc/arch/arm/setjmp.S: it will always pass back its first argument as a return value, even if it's 0 (see the man page for more details). Oddly, the Thumb implementation in the same file *is* correct! care to cook up a patch, please? thank you. -- maks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679272: bcfg2-server: unescaped shell command issues in the Trigger plugin
On 28.06.2012 16:56, Arto Jantunen wrote: Florian Weimer f...@deneb.enyo.de writes: There's a spurious diff in the changelog: bcfg2 (1.0.1-3+squeeze1) stable-security; urgency=high * Apply patch from Chris St. Pierre to fix several problems with -unescaped shell commands (Closes: #640028). +unescaped shell commands But the actual patch seems fine. Please build without -sa and upload to security-master. Thanks! I have fixed the mistake in the changelog, built the package and uploaded the result. That upload appears to have hit ftp-master, rather than security-master, so the package is currently in proposed-updates; I've flagged that copy for rejection. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662236: marked as done (coinor-ipopt: hardcoded library dependencies on libmumps)
Your message dated Thu, 28 Jun 2012 17:17:34 + with message-id e1skilw-0005hd...@franck.debian.org and subject line Bug#662236: fixed in coinor-ipopt 3.10.2-1.1 has caused the Debian Bug report #662236, regarding coinor-ipopt: hardcoded library dependencies on libmumps 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.) -- 662236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: coinor-ipopt Version: 3.10.2-1 Severity: grave Shared library dependencies are handled by the shlibs mechanism, you must not hardcode library dependencies in the source debian/control. Right now coinor-ipopt is built against mumps 4.10.0 but depends on 4.9.2. Cheers, Julien signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: coinor-ipopt Source-Version: 3.10.2-1.1 We believe that the bug you reported is fixed in the latest version of coinor-ipopt, which is due to be installed in the Debian FTP archive: coinor-ipopt_3.10.2-1.1.debian.tar.gz to main/c/coinor-ipopt/coinor-ipopt_3.10.2-1.1.debian.tar.gz coinor-ipopt_3.10.2-1.1.dsc to main/c/coinor-ipopt/coinor-ipopt_3.10.2-1.1.dsc coinor-libipopt-dev_3.10.2-1.1_amd64.deb to main/c/coinor-ipopt/coinor-libipopt-dev_3.10.2-1.1_amd64.deb coinor-libipopt-doc_3.10.2-1.1_all.deb to main/c/coinor-ipopt/coinor-libipopt-doc_3.10.2-1.1_all.deb coinor-libipopt1-dbg_3.10.2-1.1_amd64.deb to main/c/coinor-ipopt/coinor-libipopt1-dbg_3.10.2-1.1_amd64.deb coinor-libipopt1_3.10.2-1.1_amd64.deb to main/c/coinor-ipopt/coinor-libipopt1_3.10.2-1.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 662...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Etienne Millon etienne.mil...@gmail.com (supplier of updated coinor-ipopt 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: Sat, 16 Jun 2012 12:39:43 +0200 Source: coinor-ipopt Binary: coinor-libipopt1 coinor-libipopt-dev coinor-libipopt-doc coinor-libipopt1-dbg Architecture: source all amd64 Version: 3.10.2-1.1 Distribution: unstable Urgency: low Maintainer: Roberto C. Sanchez robe...@connexer.com Changed-By: Etienne Millon etienne.mil...@gmail.com Description: coinor-libipopt-dev - Interior-Point Optimizer - header files coinor-libipopt-doc - Interior-Point Optimizer - documentation coinor-libipopt1 - Interior-Point Optimizer, for large-scale nonlinear optimization coinor-libipopt1-dbg - Interior-Point Optimizer - debugging symbols Closes: 662236 Changes: coinor-ipopt (3.10.2-1.1) unstable; urgency=low . * Non-maintainer upload. * Remove hardcoded dependency on libmumps (Closes: #662236). * Add missing dependencies on libmpi and libdl. Checksums-Sha1: 00aabbdbd8f498ff2680f1fccf0d8832d73b0483 2275 coinor-ipopt_3.10.2-1.1.dsc 01e9d20850d5226e2932fae1486de9e854fc135d 36568 coinor-ipopt_3.10.2-1.1.debian.tar.gz 9080e229b20361d4594a8becdb97c84735c2b41f 4325170 coinor-libipopt-doc_3.10.2-1.1_all.deb ab71e08b2e140bc5706574adbeef65fa67f9d2b6 830436 coinor-libipopt1_3.10.2-1.1_amd64.deb 45f0b4f39814ae4e010246acaa6a4d5de3cc4ffc 1840772 coinor-libipopt-dev_3.10.2-1.1_amd64.deb 0778548471fdec945be4f5be67a14d6e949700a2 9151868 coinor-libipopt1-dbg_3.10.2-1.1_amd64.deb Checksums-Sha256: 5138128369c92ca8f62c988f39589c6dc01624b957c6c36cdb72f9b39737b9b8 2275 coinor-ipopt_3.10.2-1.1.dsc 06c7529e0eddb89e39a398c11f3d23522dbca62f6e84ff48526f148e8fd32cff 36568 coinor-ipopt_3.10.2-1.1.debian.tar.gz ba57a4f6dfa2f3e7bc9016ae172a321469ff3d90ee56ca2e27279a1d9cff23c2 4325170 coinor-libipopt-doc_3.10.2-1.1_all.deb 7d216e982525514a1747cdf12ba3abf9f8715795e3d6c22ada8562d346546950 830436 coinor-libipopt1_3.10.2-1.1_amd64.deb 3b9af8f2ee8a16fa68933584da6fd0af7926e08256bc50a03857ede59d680655 1840772 coinor-libipopt-dev_3.10.2-1.1_amd64.deb a67b8d17e395ff3140dbedce3729245fb91625d30b258a53e2dc6468fc3d11dc 9151868 coinor-libipopt1-dbg_3.10.2-1.1_amd64.deb Files: 3f6f5c606349b0dc7d71d139049d5307 2275 science extra coinor-ipopt_3.10.2-1.1.dsc 49080aeedcccfe1c58f4bbb8d49ab000 36568 science extra coinor-ipopt_3.10.2-1.1.debian.tar.gz 665a52ff3e8330aa4e39ba6dab695e3c 4325170 doc extra
Bug#656421: marked as done (Please update to libnl3)
Your message dated Thu, 28 Jun 2012 17:20:17 + with message-id e1skio9-0005nb...@franck.debian.org and subject line Bug#656421: fixed in powertop 2.0-0.1 has caused the Debian Bug report #656421, regarding Please update to libnl3 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.) -- 656421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: powertop Version: 1.97-2 Severity: wishlist Tags: patch Hi, with more and more applications switching from libnl1 and libnl2 to libnl3 (most notably network-manager and wpasupplicant), it would be great if powertop could switch to the latest version of libnl as well. It is currently the only application on my system which is pulling in libnl2 as dependency. With the attached patch I could successfully build powertop against libnl3 3.2. I've done some basic tests and it seems to work fine, but of course I'd appreciate further review. Cheers, Michael -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages powertop depends on: ii libc6 2.13-24 ii libgcc1 1:4.6.2-11 ii libncursesw5 5.9-4 ii libnl-3-200 3.2.3-2 ii libnl-genl-3-200 3.2.3-2 ii libpci3 1:3.1.8-2 ii libstdc++64.6.2-11 ii libtinfo5 5.9-4 ii zlib1g1:1.2.3.4.dfsg-3 powertop recommends no packages. Versions of packages powertop suggests: pn cpufrequtils 007-2 pn laptop-mode-tools none -- no debconf information diff -Nru powertop-1.97/debian/control powertop-1.97/debian/control --- powertop-1.97/debian/control 2011-03-17 16:25:01.0 +0100 +++ powertop-1.97/debian/control 2012-01-19 09:11:25.0 +0100 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Patrick Winnertz win...@debian.org Uploaders: Jose Luis Rivas ghostba...@gmail.com -Build-Depends: cdbs, debhelper (= 5), libncursesw5-dev, libncurses5-dev, libnl2-dev, pkg-config, libpci-dev +Build-Depends: cdbs, debhelper (= 5), libncursesw5-dev, libncurses5-dev, libnl-3-dev, libnl-genl-3-dev, pkg-config, libpci-dev Standards-Version: 3.9.1 Homepage: http://www.linuxpowertop.org diff -Nru powertop-1.97/debian/patches/libnl3.patch powertop-1.97/debian/patches/libnl3.patch --- powertop-1.97/debian/patches/libnl3.patch 1970-01-01 01:00:00.0 +0100 +++ powertop-1.97/debian/patches/libnl3.patch 2012-01-19 09:12:35.0 +0100 @@ -0,0 +1,24 @@ +diff --git a/Makefile b/Makefile +index 0382fea..60f23d7 100644 +--- a/Makefile b/Makefile +@@ -24,6 +24,7 @@ OBJS += tuning/cpufreq.o tuning/ethernet.o tuning/iw.o tuning/wifi.o + + NL1FOUND := $(shell $(PKG_CONFIG) --atleast-version=1 libnl-1 echo Y) + NL2FOUND := $(shell $(PKG_CONFIG) --atleast-version=2 libnl-2.0 echo Y) ++NL3FOUND := $(shell $(PKG_CONFIG) --atleast-version=3.2 libnl-3.0 echo Y) + + ifeq ($(NL1FOUND),Y) + NLLIBNAME = libnl-1 +@@ -35,6 +36,11 @@ LIBS += -lnl-genl + NLLIBNAME = libnl-2.0 + endif + ++ifeq ($(NL3FOUND),Y) ++CFLAGS += -DCONFIG_LIBNL20 ++NLLIBNAME = libnl-3.0 libnl-genl-3.0 ++endif ++ + ifeq ($(NLLIBNAME),) + $(error Cannot find development files for any supported version of libnl) + endif diff -Nru powertop-1.97/debian/patches/series powertop-1.97/debian/patches/series --- powertop-1.97/debian/patches/series 2011-03-17 16:25:01.0 +0100 +++ powertop-1.97/debian/patches/series 2012-01-19 09:12:39.0 +0100 @@ -1,3 +1,4 @@ fix_prefix_in_manpage.patch fix_NR_perf_event_open_on_ia64.patch fix_csstoh_on_sparc +libnl3.patch ---End Message--- ---BeginMessage--- Source: powertop Source-Version: 2.0-0.1 We believe that the bug you reported is fixed in the latest version of powertop, which is due to be installed in the Debian FTP archive: powertop_2.0-0.1.debian.tar.gz to main/p/powertop/powertop_2.0-0.1.debian.tar.gz powertop_2.0-0.1.dsc to main/p/powertop/powertop_2.0-0.1.dsc powertop_2.0-0.1_amd64.deb to main/p/powertop/powertop_2.0-0.1_amd64.deb powertop_2.0.orig.tar.bz2 to main/p/powertop/powertop_2.0.orig.tar.bz2 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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian
Bug#679437: brewtarget: includes non-free images
Package: brewtarget Version: 1.2.4-1 Severity: serious Justification: Policy 2.2.1 Hello, according to its debian/copyright file [1], this package includes some images licensed under the terms of CC-by-nc-nd-v3.0: | Files: images/flag*.png | Copyright: 2009-2010, A68 Freelance Graphics Designs a68desi...@gmail.com | License: CC-BY-NC-ND-3.0 [1] http://packages.debian.org/changelogs/pool/main/b/brewtarget/current/copyright This license definitely fails to meet the DFSG (the major issues are with DFSG#1 and DFSG#3). Please replace these images with DFSG-free ones or move the package to the non-free archive. Moreover, the debian/copyright file [1] also states that Oxygen icons are licensed under the terms of CC-by-sa-v3.0: | Files: images/edit-copy.png images/document-print-preview.png |images/merge.png images/printer.png images/server-database.png | Copyright: David Vignoni et al. www.oxygen-icons.org | License: CC-BY-SA-3.0 Do I read correctly on the official website [2] that these icons are actually dual-licensed under the terms of CC-by-sa-v3.0 and the GNU LGPL ? [2] http://www.oxygen-icons.org/?page_id=4 If this is confirmed, please fix the debian/copyright file, since it is currently inaccurate. BTW, the full text of CC-by-sa-v3.0 must be included in the debian/copyright file, since it's not in /usr/share/common-licenses/ Finally, the debian/copyright file [1] states that restore.png is licensed under the terms of CC-by-v3.0: | Files: images/restore.png | Copyright: FatCow Web Hosting www.fatcow.com/free-icons | License: CC-BY-3.0 This *seems* to be correct, at a first glance, as the referenced website [3] says: | These icon sets are licensed under a Creative Commons | Attribution 3.0 License. [3] http://www.fatcow.com/free-icons Unfortunately the copyright holders seem to change their minds or to be very confused about the meaning of the license, as they state immediately after: | The icons may not be resold, sub-licensed, rented, transferred | or otherwise made available for use. This is clearly an additional non-free restriction (failing DFSG#1) not included in CC-by-v3.0 or otherwise a non-free interpretation of CC-by-v3.0: in either case, it means that the copyright holders did not license the image in a DFSG-free manner. Please replace the image with a DFSG-free one or move the package to the non-free archive. I hope these issues may be fixed soon. Thanks for your time. Bye. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671931: RM: libnl2 -- ROM; obsolete, unmaintained
reassign 671931 ftp.debian.org retitle 671931 RM: libnl2 -- ROM; obsolete, unmaintained block 671931 by 679438 thanks libnl2 is outdated and not maintained upstream anymore. All libnl2 users should upgrade to the current stable version libnl3. It should therefore not be released in wheezy and in the end be completely removed. All reverse dependencies have been updated and libphone-ui-shr just needs a simple binNMU, which I've requested as #679438. Re-assigning to ftp.debian.org to get the package removed. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: RM: libnl2 -- ROM; obsolete, unmaintained
Processing commands for cont...@bugs.debian.org: reassign 671931 ftp.debian.org Bug #671931 [libnl2] libnl2 should not be released in wheezy Bug reassigned from package 'libnl2' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #671931 to the same values previously set Ignoring request to alter fixed versions of bug #671931 to the same values previously set retitle 671931 RM: libnl2 -- ROM; obsolete, unmaintained Bug #671931 [ftp.debian.org] libnl2 should not be released in wheezy Changed Bug title to 'RM: libnl2 -- ROM; obsolete, unmaintained' from 'libnl2 should not be released in wheezy' block 671931 by 679438 Bug #671931 [ftp.debian.org] RM: libnl2 -- ROM; obsolete, unmaintained 671931 was not blocked by any bugs. 671931 was not blocking any bugs. Added blocking bug(s) of 671931: 679438 thanks Stopping processing here. Please contact me if you need assistance. -- 671931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671931 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#614907: Draft resolution for node+nodejs
Hi all, Sorry this is so long in coming. Here's the draft resolution for this issue, agreed at the last IRC meeting. I thought about including a statement censuring nodejs upstream for their unhelpful behavior around this issue, but we didn't actually discuss that at the IRC meeting so I don't know if there's a consensus and don't want to hold this up any further. === Resolution === The Technical Committee reaffirms the importance of preventing namespace collisions for programs in the distribution, while recognizing that compatibility with upstreams and with previous Debian releases is also important and that sometimes an imperfect balance must be struck between these three goals. The Committee therefore resolves that: 1. The nodejs package shall be changed to provide /usr/bin/nodejs, not /usr/bin/node. The package should declare a Breaks: relationship with any packages in Debian that reference /usr/bin/node. 2. The nodejs source package shall also provide a nodejs-legacy binary package at Priority: extra that contains /usr/bin/node as a symlink to /usr/bin/nodejs. No package in the archive may depend on or recommend the nodejs-legacy package, which is provided solely for upstream compatibility. This package declares shall also declare a Conflicts: relationship with the node package. 3. The node source package shall rename its binary to /usr/sbin/ax25-node, and its binary package to ax25-node. 4. The node source package shall continue to build a transitional 'node' binary package for compatibility with deployed Debian installations, which provides /usr/sbin/node as a symlink to /usr/sbin/ax25-node. This package shall declare a reciprocal Conflicts: relationship with the nodejs-legacy package. Other packages may reference the 'node' package as a dependency or recommendation, but are encouraged to transition to 'ax25-node'. 5. The maintainers of these packages are required to implement the above changes immediately in unstable. Failing that, the Technical Committee reserves the right to NMU to implement these changes. 6. Once the above changes are implemented, the packages shall be considered suitable for release with respect to the Debian policy on conflicting packages. === End Resolution === Draft Ballot: 1. Approve transition plan for node and nodejs 2. Further discussion I'll wait for feedback until 30 Jun 00:00:00 UTC before calling for a vote, in case there are bugs above. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#625828: libipc-sharelite-perl: FTBFS on armel: test failures
On Wed, Jun 27, 2012 at 12:20:05AM +0200, intrigeri wrote: shawn wrote (17 Jun 2012 03:13:04 GMT) : on 3.4 (custom) + sheevaplug: $ gcc -O0 625828.c $ ./a.out ok 1 - got 2000, expected 2000 I asked for more thorough testing, and shawn reported I ran it 500 times, it succeeded only 191 of those times. This seems to be another instance of VIVT L1 caching weirdness. The problem has been discussed years ago on the arm kernel mailing list (see [1]) and a patch has been proposed at that time. Apparently, that never made it into the kernel. I think what happens in the test program is the following: 1. When mapping 1 is initialized, it is cacheable (in L1 and L2) 2. When mapping 2 is initialized (by c = *shmaddr2;), both mappings become uncacheable (neither in L1 nor L2) since they belong to the same process. If they were cacheable, the two mappings could become incoherent within the same process. (Incoherencies between processes can be avoided by flushing the L1 cache at context switch. However, this is not possible within a process and thus, the kernel sets shared mappings to uncacheable) 3. The forked process only uses mapping 1, i.e. the mapping remains cacheable in this process. 4. Task switches between the two processes flush the L1 caches, but not the L2 cache. Since the original process does not use the L2 cache at all and the second process uses it, the processes have incoherent views. If this theory is true, the following should make the problem disappear (tested on kirkwood): 1. Don't initialize the second mapping by c = *shmaddr2; - The mapping remains cacheable in both processes. Problem goes away, as already stated in the original test program. 2. Initialize the second mapping in both processes. (Don't detach the second range and move c = *shmaddr2; to happen after the fork.) - The mappings are non-cacheable in both processes. Problem goes away. 3. Disable the L2 cache in both U-Boot and the kernel (requires to compile the kernel with CONFIG_CACHE_FEROCEON_L2=n) - L1 flushes now are sufficient to ensure coherency. Problem goes away. This seems to support my theory... The patch that was proposed in the thread mentioned above would render the mapping(s) of the second process uncacheable as there are already other uncacheable mappings (those of the original process). Thus, it leads to the situation described in 2 above and should fix the problem. Unfortunately, it does not apply to my current kernel (3.5-rc4) anymore. So, I could not test whether it really helps. - Simon [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2009-December/005471.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679220: marked as done (Conflicting with therion-doc, please add suitable Breaks/Conflicts)
Your message dated Thu, 28 Jun 2012 18:21:03 + with message-id e1skjkx-0002bi...@franck.debian.org and subject line Bug#679220: fixed in therion 5.3.9-4 has caused the Debian Bug report #679220, regarding Conflicting with therion-doc, please add suitable Breaks/Conflicts 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.) -- 679220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: therion-viewer Version: 5.3.9-3 Severity: serious Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: therion-viewer 1 upgraded, 0 newly installed, 0 to remove and 132 not upgraded. 544 not fully installed or removed. Need to get 0 B/537 kB of archives. After this operation, 2048 B of additional disk space will be used. Retrieving bug reports... Done Parsing Found/Fixed information... Done (Reading database ... 392581 files and directories currently installed.) Preparing to replace therion-viewer 5.3.9-1+b1 (using .../therion-viewer_5.3.9-3_i386.deb) ... Unpacking replacement therion-viewer ... dpkg: error processing /var/cache/apt/archives/therion-viewer_5.3.9-3_i386.deb (--unpack): trying to overwrite '/usr/share/doc-base/therion', which is also in package therion-doc 5.3.9-3 Processing triggers for menu ... Processing triggers for desktop-file-utils ... Errors were encountered while processing: /var/cache/apt/archives/therion-viewer_5.3.9-3_i386.deb -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages therion-viewer depends on: ii libc6 2.13-33 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.1-2 iu libgl1-mesa-glx [libgl1] 8.0.3-1 iu libglu1-mesa [libglu1]8.0.3-1 ii libjpeg8 8d-1 ii libpng12-01.2.49-1 ii libstdc++64.7.1-2 ii libvtk5.8 5.8.0-13 ii libwxbase2.8-02.8.12.1-11 ii libwxgtk2.8-0 2.8.12.1-11 iu libx11-6 2:1.5.0-1 iu therion 5.3.9-3 ii zlib1g1:1.2.7.dfsg-13 therion-viewer recommends no packages. therion-viewer suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: therion Source-Version: 5.3.9-4 We believe that the bug you reported is fixed in the latest version of therion, which is due to be installed in the Debian FTP archive: therion-doc_5.3.9-4_all.deb to main/t/therion/therion-doc_5.3.9-4_all.deb therion-viewer_5.3.9-4_amd64.deb to main/t/therion/therion-viewer_5.3.9-4_amd64.deb therion_5.3.9-4.debian.tar.gz to main/t/therion/therion_5.3.9-4.debian.tar.gz therion_5.3.9-4.dsc to main/t/therion/therion_5.3.9-4.dsc therion_5.3.9-4_amd64.deb to main/t/therion/therion_5.3.9-4_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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wookey woo...@debian.org (supplier of updated therion 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, 27 Jun 2012 19:21:53 +0100 Source: therion Binary: therion therion-viewer therion-doc Architecture: source amd64 all Version: 5.3.9-4 Distribution: unstable Urgency: low Maintainer: Wookey woo...@debian.org Changed-By: Wookey woo...@debian.org Description: therion- Cave surveying - 2D and 3D drawing software therion-doc - Documentation for Therion Cave surveying software therion-viewer - Cave surveying - 3D viewer for therion models Closes: 679220 Changes: therion (5.3.9-4) unstable; urgency=low . * Fix clash in doc-base names. (Closes: #679220) * Put missing therion book back and fix docbase names Checksums-Sha1: bc92dcb40fd5dcac0ea0333efea76c9ea54d6998 1329 therion_5.3.9-4.dsc c1e2de0faeacb8c112a841cb9dc2a9722e0e 19682 therion_5.3.9-4.debian.tar.gz
Bug#679444: nut-server: old nut initscript not removed on upgrade
Package: nut-server Version: 2.6.3-2 Severity: serious Hi, It seems that /etc/init.d/nut init script is not cleanup on upgrade (and the runlevel are still present too). nut-server package should delete it and remove the runlevel symlink on upgrade. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 677822 to nut-server, forcibly merging 679444 677822
Processing commands for cont...@bugs.debian.org:
reassign 677822 nut-server 2.6.3-2
Bug #677822 [nut] nut: Old /etc/init.d/nut is not removed,
/etc/init.d/nut-{server, client} fail to start
Bug reassigned from package 'nut' to 'nut-server'.
No longer marked as found in versions nut/2.6.4-1.
Ignoring request to alter fixed versions of bug #677822 to the same values
previously set
Bug #677822 [nut-server] nut: Old /etc/init.d/nut is not removed,
/etc/init.d/nut-{server, client} fail to start
Marked as found in versions nut/2.6.3-2.
forcemerge 679444 677822
Bug #679444 [nut-server] nut-server: old nut initscript not removed on upgrade
Bug #677822 [nut-server] nut: Old /etc/init.d/nut is not removed,
/etc/init.d/nut-{server, client} fail to start
Severity set to 'serious' from 'minor'
Merged 677822 679444
thanks
Stopping processing here.
Please contact me if you need assistance.
--
677822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677822
679444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679444
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#665221: Dancer-Plugin-Database bug + testcase
On Tue, 26 Jun 2012 05:23:41 +0200 intrigeri intrig...@boum.org wrote: OK. Then, I think we'll probably need to ask for a freeze exception. Therefore, it would help us (the Debian Perl Group) a lot if the minimal changes to fix this specific serious bug were well isolated, so that we can backport them independently and leave other changes alone. Just so you know, what would be perfect for us would be a bugfix-only release, but please don't make your life a pain because of us :) But perhaps a couple of days will end *before* the Wheezy freeze, who knows. I'm looking for a decent safe fix now; if I find one, I'll get a new release out tonight, hopefully that's not too late. If I do, I'll provide a link to the commit(s) which fix the issue, in case you need to backport only the changes. -- David Precious (bigpresh) dav...@preshweb.co.uk http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedinwww.preshweb.co.uk/facebook www.preshweb.co.uk/cpanwww.preshweb.co.uk/github -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677714: [pkg-wine-party] Bug#677714: wine-unstable: Incomplete upload of 1.5 for amd64
On Thu, Jun 28, 2012 at 3:48 AM, Jakub Moc rote:
Dear maintainer, is this some sort of poor joke, or what is going on
here?
No.
After the latest update to 1.5.6-1, installing wine-unstable
results in installing two dummy, empty and absolutely useless packages
on amd64.
$ dpkg -L wine{,64-bin}-unstable
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libwine-unstable
/usr/share/doc/wine-unstable
/.
/usr
/usr/bin
/usr/bin/wine
Try typing wine.
/usr/share
/usr/share/doc
/usr/share/doc/libwine-unstable
/usr/share/doc/wine64-bin-unstable
We could probably be better at being informative with a NEWS entry,
but its not really at the top of my list of things to do. I would
certainly be willing to apply an appropriate patch for that.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: clone, retitle and block
Processing commands for cont...@bugs.debian.org: clone 625828 -1 Bug #625828 [libipc-sharelite-perl] libipc-sharelite-perl: FTBFS on armel: test failures Bug 625828 cloned as bug 679449 reassign -1 src:linux Bug #679449 [libipc-sharelite-perl] libipc-sharelite-perl: FTBFS on armel: test failures Bug reassigned from package 'libipc-sharelite-perl' to 'src:linux'. No longer marked as found in versions libipc-sharelite-perl/0.17-1. Ignoring request to alter fixed versions of bug #679449 to the same values previously set retitle -1 shared memory problem on armel Bug #679449 [src:linux] libipc-sharelite-perl: FTBFS on armel: test failures Changed Bug title to 'shared memory problem on armel' from 'libipc-sharelite-perl: FTBFS on armel: test failures' block 625828 by -1 Bug #625828 [libipc-sharelite-perl] libipc-sharelite-perl: FTBFS on armel: test failures 625828 was not blocked by any bugs. 625828 was not blocking any bugs. Added blocking bug(s) of 625828: 679449 thanks Stopping processing here. Please contact me if you need assistance. -- 625828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625828 679449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679449 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: notfound 679449 in 0.17-1
Processing commands for cont...@bugs.debian.org: notfound 679449 0.17-1 Bug #679449 [src:linux] shared memory problem on armel The source linux and version do not appear to match any binary packages Ignoring request to alter found versions of bug #679449 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 679449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679449 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#625828: libipc-sharelite-perl: FTBFS on armel: test failures
Simon Baatz wrote (28 Jun 2012 18:21:28 GMT) : This seems to be another instance of VIVT L1 caching weirdness. The problem has been discussed years ago on the arm kernel mailing list (see [1]) and a patch has been proposed at that time. Apparently, that never made it into the kernel. Thanks a lot for your analysis. I've cloned that bug and reassigned the new one to src:linux: http://bugs.debian.org/679449 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677460: marked as done (libmeep-mpich2-dev and libmeep-lam4-dev: error when trying to install together)
Your message dated Thu, 28 Jun 2012 19:19:07 + with message-id e1skkf9-0007of...@franck.debian.org and subject line Bug#677460: fixed in meep-lam4 1.1.1-9 has caused the Debian Bug report #677460, regarding libmeep-mpich2-dev and libmeep-lam4-dev: error when trying to install together 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.) -- 677460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libmeep-lam4-dev,libmeep-mpich2-dev Version: libmeep-lam4-dev/1.1.1-8 Version: libmeep-mpich2-dev/1.1.1-8 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libgomp1 libfftw3-3 libquadmath0 libgfortran3 libblas3 libblas3gf libcr0 libgsl0ldbl liblapack3 liblapack3gf libharminv2 libmpich2-3 libhdf5-mpich2-7 libmeep-lam4-6 libmeep-lam4-dev libmeep-mpich2-6 libmeep-mpich2-dev Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libgomp1:amd64. (Reading database ... 10690 files and directories currently installed.) Unpacking libgomp1:amd64 (from .../libgomp1_4.7.0-13_amd64.deb) ... Selecting previously unselected package libfftw3-3:amd64. Unpacking libfftw3-3:amd64 (from .../libfftw3-3_3.3.2-3_amd64.deb) ... Selecting previously unselected package libquadmath0:amd64. Unpacking libquadmath0:amd64 (from .../libquadmath0_4.7.0-13_amd64.deb) ... Selecting previously unselected package libgfortran3:amd64. Unpacking libgfortran3:amd64 (from .../libgfortran3_4.7.0-13_amd64.deb) ... Selecting previously unselected package libblas3. Unpacking libblas3 (from .../libblas3_1.2.20110419-3_amd64.deb) ... Selecting previously unselected package libblas3gf. Unpacking libblas3gf (from .../libblas3gf_1.2.20110419-3_amd64.deb) ... Selecting previously unselected package libcr0. Unpacking libcr0 (from .../libcr0_0.8.4-2_amd64.deb) ... Selecting previously unselected package libgsl0ldbl. Unpacking libgsl0ldbl (from .../libgsl0ldbl_1.15+dfsg-1_amd64.deb) ... Selecting previously unselected package liblapack3. Unpacking liblapack3 (from .../liblapack3_3.4.1-1_amd64.deb) ... Selecting previously unselected package liblapack3gf. Unpacking liblapack3gf (from .../liblapack3gf_3.4.1-1_amd64.deb) ... Selecting previously unselected package libharminv2. Unpacking libharminv2 (from .../libharminv2_1.3.1-8_amd64.deb) ... Selecting previously unselected package libmpich2-3. Unpacking libmpich2-3 (from .../libmpich2-3_1.4.1-4_amd64.deb) ... Selecting previously unselected package libhdf5-mpich2-7. Unpacking libhdf5-mpich2-7 (from .../libhdf5-mpich2-7_1.8.8-9_amd64.deb) ... Selecting previously unselected package libmeep-lam4-6. Unpacking libmeep-lam4-6 (from .../libmeep-lam4-6_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-lam4-dev. Unpacking libmeep-lam4-dev (from .../libmeep-lam4-dev_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-mpich2-6. Unpacking libmeep-mpich2-6 (from .../libmeep-mpich2-6_1.1.1-8_amd64.deb) ... Selecting previously unselected package libmeep-mpich2-dev. Unpacking libmeep-mpich2-dev (from .../libmeep-mpich2-dev_1.1.1-8_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_amd64.deb (--unpack): trying to overwrite '/usr/include/meep.hpp', which is also in package libmeep-lam4-dev 1.1.1-8 Errors were encountered while processing: /var/cache/apt/archives/libmeep-mpich2-dev_1.1.1-8_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the
Bug#665221: Dancer-Plugin-Database bug + testcase
David Precious wrote (28 Jun 2012 18:42:19 GMT) : I'm looking for a decent safe fix now; if I find one, I'll get a new release out tonight, hopefully that's not too late. Tonight would be perfect. Thanks for working on it. If I do, I'll provide a link to the commit(s) which fix the issue, in case you need to backport only the changes. Emailing me and 665...@bugs.debian.org would be perfect :) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677714: [pkg-wine-party] Bug#677714: wine-unstable: Incomplete upload of 1.5 for amd64
2012/6/28 Michael Gilbert mgilb...@debian.org: Try typing wine. We could probably be better at being informative with a NEWS entry, but its not really at the top of my list of things to do. I would certainly be willing to apply an appropriate patch for that. Best wishes, Mike Well, the only patch I could offer here would be at least making the instructions *correct*. Since people installing wine-unstable hardly want to # apt-get install wine-bin:i386 to install the outdated stuff. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614907: Draft resolution for node+nodejs
[Whoops, forgot the magic header for packages.qa.d.o; resending.] Hi all, Sorry this is so long in coming. Here's the draft resolution for this issue, agreed at the last IRC meeting. I thought about including a statement censuring nodejs upstream for their unhelpful behavior around this issue, but we didn't actually discuss that at the IRC meeting so I don't know if there's a consensus and don't want to hold this up any further. === Resolution === The Technical Committee reaffirms the importance of preventing namespace collisions for programs in the distribution, while recognizing that compatibility with upstreams and with previous Debian releases is also important and that sometimes an imperfect balance must be struck between these three goals. The Committee therefore resolves that: 1. The nodejs package shall be changed to provide /usr/bin/nodejs, not /usr/bin/node. The package should declare a Breaks: relationship with any packages in Debian that reference /usr/bin/node. 2. The nodejs source package shall also provide a nodejs-legacy binary package at Priority: extra that contains /usr/bin/node as a symlink to /usr/bin/nodejs. No package in the archive may depend on or recommend the nodejs-legacy package, which is provided solely for upstream compatibility. This package declares shall also declare a Conflicts: relationship with the node package. 3. The node source package shall rename its binary to /usr/sbin/ax25-node, and its binary package to ax25-node. 4. The node source package shall continue to build a transitional 'node' binary package for compatibility with deployed Debian installations, which provides /usr/sbin/node as a symlink to /usr/sbin/ax25-node. This package shall declare a reciprocal Conflicts: relationship with the nodejs-legacy package. Other packages may reference the 'node' package as a dependency or recommendation, but are encouraged to transition to 'ax25-node'. 5. The maintainers of these packages are required to implement the above changes immediately in unstable. Failing that, the Technical Committee reserves the right to NMU to implement these changes. 6. Once the above changes are implemented, the packages shall be considered suitable for release with respect to the Debian policy on conflicting packages. === End Resolution === Draft Ballot: 1. Approve transition plan for node and nodejs 2. Further discussion I'll wait for feedback until 30 Jun 00:00:00 UTC before calling for a vote, in case there are bugs above. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#679316: starplot: FTBFS: No rule to make target `all'. Stop.
Hi Christoph, Thanks for your report, I am going to review this as soon as possible. I think it is due to build targets in debian/rules. Thank you, Francisco. On Wed, Jun 27, 2012 at 10:36:48PM +0200, Christoph Egger wrote: Package: src:starplot Version: 0.95.5-5 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: fakeroot debian/rules clean dh_testdir dh_testroot # Add here commands to clean up after the build process. [ ! -f Makefile ] || /usr/bin/make distclean rm -f build-stamp configure-stamp config.status config.log dh_clean debian/rules build-arch dh_testdir # Add here commands to compile the package. /usr/bin/make all CFLAGS=-Wall -pedantic -O2 -g CXXFLAGS=-Wall -pedantic -O2 -g \ INSTALLPGM= \ docdir=/usr/share/doc/starplot mandir=/usr/share/man sysconfdir=/etc make[1]: *** No rule to make target `all'. Stop. make[1]: Entering directory `/build/buildd-starplot_0.95.5-5-kfreebsd-amd64-Qf7IoR/starplot-0.95.5' make[1]: Leaving directory `/build/buildd-starplot_0.95.5-5-kfreebsd-amd64-Qf7IoR/starplot-0.95.5' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=starplotarch=kfreebsd-amd64ver=0.95.5-5stamp=1340824563 Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- Debian GNU/Linux Developer francisco AT debian.org GPG: public key ID 556ABA51 http://people.debian.org/~francisco/ signature.asc Description: Digital signature
Bug#665221: Dancer-Plugin-Database bug + testcase
On Thu, 28 Jun 2012 21:24:03 +0200 intrigeri intrig...@boum.org wrote: David Precious wrote (28 Jun 2012 18:42:19 GMT) : I'm looking for a decent safe fix now; if I find one, I'll get a new release out tonight, hopefully that's not too late. Tonight would be perfect. Thanks for working on it. If I do, I'll provide a link to the commit(s) which fix the issue, in case you need to backport only the changes. Emailing me and 665...@bugs.debian.org would be perfect :) Version 1.82 just headed to CPAN, containing a simple fix for this issue. The actual fix was: https://github.com/bigpresh/Dancer-Plugin-Database/commit/85e8cd06ff When caching a handle, if we were given a hashref of settings, we cache a reference to that hashref, too - so the original hashref of settings doesn't go out of scope while the handle is still cached. This simple change should do the job! Many thanks for reporting this issue to me and prompting me for a fix before Wheezy :) -- David Precious (bigpresh) dav...@preshweb.co.uk http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedinwww.preshweb.co.uk/facebook www.preshweb.co.uk/cpanwww.preshweb.co.uk/github -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676566: alacarte: 'gi.repository.GMenu' object has no attribute 'Separator'
the error still remains in alacarte 0.13.4-2 and gnome-menus 3.4.2-3 Traceback (most recent call last): File /usr/bin/alacarte, line 37, in module main() File /usr/bin/alacarte, line 34, in main app.run() File /usr/share/alacarte/Alacarte/MainWindow.py, line 65, in run self.loadMenus() File /usr/share/alacarte/Alacarte/MainWindow.py, line 204, in loadMenus self.on_menu_tree_cursor_changed(menu_tree) File /usr/share/alacarte/Alacarte/MainWindow.py, line 355, in on_menu_tree_cursor_changed self.loadItems(self.menu_store[menu_path][2], menu_path) File /usr/share/alacarte/Alacarte/MainWindow.py, line 224, in loadItems elif isinstance(item, GMenu.Separator): File /usr/lib/python2.7/dist-packages/gi/module.py, line 243, in __getattr__ return getattr(self._introspection_module, name) File /usr/lib/python2.7/dist-packages/gi/module.py, line 105, in __getattr__ self.__name__, name)) AttributeError: 'gi.repository.GMenu' object has no attribute 'Separator'
Bug#676566: alacarte: 'gi.repository.GMenu' object has no attribute 'Separator'
HI, On Thu, Jun 28, 2012 at 01:18:43PM -0700, Diazepan Medina wrote: the error still remains in alacarte 0.13.4-2 and gnome-menus 3.4.2-3 There is another patch which needs to be applied to alacarte. I'm just testing the new version and will upload it tonight if it's OK. If you want to patch it yourself, it's f3a41e14b3d7e30c1b3776f7b03a234ca6ebf4d8 from upstream. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] PhD student [ i...@cs.nott.ac.uk ] signature.asc Description: Digital signature
Bug#679447: libcoro-perl often segfaults
On Thu, Jun 28, 2012 at 10:51:28PM +0400, Dmitry E. Oboukhov wrote:
Package: libcoro-perl
Severity: grave
Version: 6.080
What version is that supposed to be? I suppose 6.080-2, and yes, it was a
mistake. Everything should be fixed in 6.080-3. Would you mind testing it just
to be sure? (you can find the new package at incoming.debian.org).
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
Bug#618968: Ping - netgen license problems
On Thu, 28 Jun 2012 16:07:33 +0200 Arne Wichmann wrote: begin quotation from Francesco Poli (in 20120625215725.69523c3a3df0a27f62672...@paranoici.org): On Mon, 25 Jun 2012 10:36:50 +0200 Arne Wichmann wrote: So, at least as far as I can see, there are a number of things to be done in various time frames: - Alert enough people to the problem (via debian-user, messages in the packaging, other mailing lists and similar means) I am not sure debian-user is the appropriate place for such a call for help... Well, if you are trying to reach your users, this seems to be a possible vector to me I am trying to reach people who may be able *and* willing to help me in persuading an upstream company to re-license a library under GPL-compatible terms. Many users are, unfortunately, totally uninterested in licensing issues. I am afraid that such a call for help would be ignored (or even considered annoying) on debian-user... What do you mean by messages in the packaging? At least I get mails by apt-listchanges... Other tactics may also be available - but I am not the epigon of debian packaging. You mean that netgen and other affected packages should mail to root@localhost saying please help to keep this package in Debian... ?!? I am afraid that this would annoy users and would therefore be counterproductive. As far as other mailing lists are concerned, I tried to see if other debian-legal participants could join me in this persuasion effort, but I unfortunately received no reply: I do not think that debian-legal is a good starting point for a massive campaign. As I said above, I need people with at least a bit of interest in licensing issues: debian-legal seemed to be the ideal starting point. Please note that I am a debian-legal regular myself... Maybe debian-science could be another appropriate mailing list, but I suspect that a good number of its participants are already aware of the issue, due to the various bug reports filed against packages maintained by the Debian Science team: #617613, #617931, and #618968 (that is to say, this one). A mail there might still help a bit. I am writing a message to debian-science and debian-legal right now. Let's hope to obtain some help this time... -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgp7QxFiUgT2l.pgp Description: PGP signature
Bug#679179: FTBFS on kfreebsd-*: Unknown how to get swap size for this OS
On Tue, Jun 26, 2012 at 23:27:09 +0200, Luca Falavigna wrote: Source: intel-gpu-tools Version: 1.1-1 Severity: serious Justification: fails to build from source intel-gpu-tools fails to build from source on kfreebsd-*, but built in the past: It should probably be removed... Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679063: marked as done (libmagickcore5-extra: file conflict with old libmagickcore5)
Your message dated Thu, 28 Jun 2012 20:50:12 + with message-id e1sklfi-000431...@franck.debian.org and subject line Bug#679063: fixed in imagemagick 8:6.7.7.10-1 has caused the Debian Bug report #679063, regarding libmagickcore5-extra: file conflict with old libmagickcore5 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.) -- 679063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libmagickcore5-extra Version: 8:6.7.7.9-1 Severity: serious There was a problem installing your package (sorry for the German): , | Vorbereitung zum Ersetzen von libmagickcore5-extra:i386 8:6.7.7.2-1 (durch .../libmagickcore5-extra_8%3a6.7.7.9-1_i386.deb) ... | Ersatz für libmagickcore5-extra:i386 wird entpackt ... | dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/libmagickcore5-extra_8%3a6.7.7.9-1_i386.deb (--unpack): | Versuch, »/usr/lib/i386-linux-gnu/ImageMagick-6.7.7/modules-Q16/coders/pango.la« zu überschreiben, welches auch in Paket libmagickcore5:i386 8:6.7.7.2-1 ist ` -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.4.4-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libmagickcore5-extra depends on: ii libbz2-1.0 1.0.6-3 ii libc6 2.13-33 ii libcairo2 1.12.2-2 ii libdjvulibre21 3.5.25.3-1 ii libfontconfig1 2.9.0-6 ii libfreetype62.4.2-2.1+squeeze4 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgomp14.7.1-2 ii libice6 2:1.0.8-2 ii libilmbase6 1.0.1-4 ii libjpeg88d-1 ii liblcms2-2 2.2+git20110628-2.2 ii liblqr-1-0 0.4.1-2 ii libltdl72.4.2-1.1 ii liblzma55.1.1alpha+20120614-1 ii libmagickcore5 8:6.7.7.9-1 ii libmagickwand5 8:6.7.7.9-1 ii libopenexr6 1.6.1-5 ii libpango1.0-0 1.30.0-1 ii librsvg2-2 2.36.1-1 ii libsm6 2:1.2.1-2 ii libtiff43.9.6-5 ii libwmf0.2-7 0.2.8.4-10 ii libx11-62:1.5.0-1 ii libxext62:1.3.1-2 ii libxml2 2.8.0+dfsg1-4 ii libxt6 1:1.1.3-1 ii multiarch-support 2.13-33 ii zlib1g 1:1.2.7.dfsg-13 libmagickcore5-extra recommends no packages. libmagickcore5-extra suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: imagemagick Source-Version: 8:6.7.7.10-1 We believe that the bug you reported is fixed in the latest version of imagemagick, which is due to be installed in the Debian FTP archive: imagemagick-common_6.7.7.10-1_all.deb to main/i/imagemagick/imagemagick-common_6.7.7.10-1_all.deb imagemagick-dbg_6.7.7.10-1_amd64.deb to main/i/imagemagick/imagemagick-dbg_6.7.7.10-1_amd64.deb imagemagick-doc_6.7.7.10-1_all.deb to main/i/imagemagick/imagemagick-doc_6.7.7.10-1_all.deb imagemagick_6.7.7.10-1.debian.tar.bz2 to main/i/imagemagick/imagemagick_6.7.7.10-1.debian.tar.bz2 imagemagick_6.7.7.10-1.dsc to main/i/imagemagick/imagemagick_6.7.7.10-1.dsc imagemagick_6.7.7.10-1_amd64.deb to main/i/imagemagick/imagemagick_6.7.7.10-1_amd64.deb imagemagick_6.7.7.10.orig.tar.bz2 to main/i/imagemagick/imagemagick_6.7.7.10.orig.tar.bz2 libmagick++-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagick++-dev_6.7.7.10-1_amd64.deb libmagick++5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagick++5_6.7.7.10-1_amd64.deb libmagickcore-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore-dev_6.7.7.10-1_amd64.deb libmagickcore5-extra_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore5-extra_6.7.7.10-1_amd64.deb libmagickcore5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore5_6.7.7.10-1_amd64.deb libmagickwand-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickwand-dev_6.7.7.10-1_amd64.deb libmagickwand5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickwand5_6.7.7.10-1_amd64.deb perlmagick_6.7.7.10-1_amd64.deb to main/i/imagemagick/perlmagick_6.7.7.10-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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien
Bug#679188: marked as done (libmagickcore5-extra: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/x86_64-linux-gnu/ImageMagick-6.7.7/modules-Q16/coders/pango.so)
Your message dated Thu, 28 Jun 2012 20:50:12 + with message-id e1sklfi-000434...@franck.debian.org and subject line Bug#679188: fixed in imagemagick 8:6.7.7.10-1 has caused the Debian Bug report #679188, regarding libmagickcore5-extra: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/x86_64-linux-gnu/ImageMagick-6.7.7/modules-Q16/coders/pango.so 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.) -- 679188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libmagickcore5-extra Version: 8:6.7.7.9-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' 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 'libmagickcore-dev' 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...): Unpacking replacement libmagickcore5-extra:amd64 ... dpkg: error processing /var/cache/apt/archives/libmagickcore5-extra_8%3a6.7.7.9-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/ImageMagick-6.7.7/modules-Q16/coders/pango.so', which is also in package libmagickcore5:amd64 8:6.7.7.2-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas libmagickcore-dev_8:6.7.7.9-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: imagemagick Source-Version: 8:6.7.7.10-1 We believe that the bug you reported is fixed in the latest version of imagemagick, which is due to be installed in the Debian FTP archive: imagemagick-common_6.7.7.10-1_all.deb to main/i/imagemagick/imagemagick-common_6.7.7.10-1_all.deb imagemagick-dbg_6.7.7.10-1_amd64.deb to main/i/imagemagick/imagemagick-dbg_6.7.7.10-1_amd64.deb imagemagick-doc_6.7.7.10-1_all.deb to main/i/imagemagick/imagemagick-doc_6.7.7.10-1_all.deb imagemagick_6.7.7.10-1.debian.tar.bz2 to main/i/imagemagick/imagemagick_6.7.7.10-1.debian.tar.bz2 imagemagick_6.7.7.10-1.dsc to main/i/imagemagick/imagemagick_6.7.7.10-1.dsc imagemagick_6.7.7.10-1_amd64.deb to main/i/imagemagick/imagemagick_6.7.7.10-1_amd64.deb imagemagick_6.7.7.10.orig.tar.bz2 to main/i/imagemagick/imagemagick_6.7.7.10.orig.tar.bz2 libmagick++-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagick++-dev_6.7.7.10-1_amd64.deb libmagick++5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagick++5_6.7.7.10-1_amd64.deb libmagickcore-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore-dev_6.7.7.10-1_amd64.deb libmagickcore5-extra_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore5-extra_6.7.7.10-1_amd64.deb libmagickcore5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore5_6.7.7.10-1_amd64.deb libmagickwand-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickwand-dev_6.7.7.10-1_amd64.deb libmagickwand5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickwand5_6.7.7.10-1_amd64.deb perlmagick_6.7.7.10-1_amd64.deb to main/i/imagemagick/perlmagick_6.7.7.10-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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès roucaries.bastien+deb...@gmail.com (supplier of updated imagemagick 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: Thu, 28 Jun 2012 17:44:21 +0200 Source: imagemagick Binary: imagemagick imagemagick-dbg imagemagick-common imagemagick-doc libmagickcore5 libmagickcore5-extra libmagickcore-dev libmagickwand5 libmagickwand-dev libmagick++5 libmagick++-dev perlmagick Architecture: source amd64 all Version: 8:6.7.7.10-1 Distribution: unstable Urgency: low Maintainer: ImageMagick Packaging Team pkg-gmagick-im-t...@lists.alioth.debian.org
Bug#679430: marked as done (FTBS on arm)
Your message dated Thu, 28 Jun 2012 20:50:12 + with message-id e1sklfi-000438...@franck.debian.org and subject line Bug#679430: fixed in imagemagick 8:6.7.7.10-1 has caused the Debian Bug report #679430, regarding FTBS on arm 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.) -- 679430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: imagemagick Version: 8:6.7.7.2-1 Severity: serious Imagemagick FTBS on arm CC magick/magick_libMagickCore_la-draw.lo CC magick/magick_libMagickCore_la-effect.lo CC magick/magick_libMagickCore_la-enhance.lo CC magick/magick_libMagickCore_la-exception.lo CC magick/magick_libMagickCore_la-feature.lo CC magick/magick_libMagickCore_la-fourier.lo CC magick/magick_libMagickCore_la-fx.lo CC magick/magick_libMagickCore_la-gem.lo magick/gem.c:610:21: error: conflicting types for 'GenerateDifferentialNoise' ./magick/gem.h:30:3: note: previous declaration of 'GenerateDifferentialNoise' was here make[2]: *** [magick/magick_libMagickCore_la-gem.lo] Error 1 make[2]: Leaving directory `/build/buildd-imagemagick_6.7.7.9-1-armel-66TJ9D/imagemagick-6.7.7.9' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-imagemagick_6.7.7.9-1-armel-66TJ9D/imagemagick-6.7.7.9' make: *** [build-stamp] Error 2 Bastien ---End Message--- ---BeginMessage--- Source: imagemagick Source-Version: 8:6.7.7.10-1 We believe that the bug you reported is fixed in the latest version of imagemagick, which is due to be installed in the Debian FTP archive: imagemagick-common_6.7.7.10-1_all.deb to main/i/imagemagick/imagemagick-common_6.7.7.10-1_all.deb imagemagick-dbg_6.7.7.10-1_amd64.deb to main/i/imagemagick/imagemagick-dbg_6.7.7.10-1_amd64.deb imagemagick-doc_6.7.7.10-1_all.deb to main/i/imagemagick/imagemagick-doc_6.7.7.10-1_all.deb imagemagick_6.7.7.10-1.debian.tar.bz2 to main/i/imagemagick/imagemagick_6.7.7.10-1.debian.tar.bz2 imagemagick_6.7.7.10-1.dsc to main/i/imagemagick/imagemagick_6.7.7.10-1.dsc imagemagick_6.7.7.10-1_amd64.deb to main/i/imagemagick/imagemagick_6.7.7.10-1_amd64.deb imagemagick_6.7.7.10.orig.tar.bz2 to main/i/imagemagick/imagemagick_6.7.7.10.orig.tar.bz2 libmagick++-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagick++-dev_6.7.7.10-1_amd64.deb libmagick++5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagick++5_6.7.7.10-1_amd64.deb libmagickcore-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore-dev_6.7.7.10-1_amd64.deb libmagickcore5-extra_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore5-extra_6.7.7.10-1_amd64.deb libmagickcore5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickcore5_6.7.7.10-1_amd64.deb libmagickwand-dev_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickwand-dev_6.7.7.10-1_amd64.deb libmagickwand5_6.7.7.10-1_amd64.deb to main/i/imagemagick/libmagickwand5_6.7.7.10-1_amd64.deb perlmagick_6.7.7.10-1_amd64.deb to main/i/imagemagick/perlmagick_6.7.7.10-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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès roucaries.bastien+deb...@gmail.com (supplier of updated imagemagick 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: Thu, 28 Jun 2012 17:44:21 +0200 Source: imagemagick Binary: imagemagick imagemagick-dbg imagemagick-common imagemagick-doc libmagickcore5 libmagickcore5-extra libmagickcore-dev libmagickwand5 libmagickwand-dev libmagick++5 libmagick++-dev perlmagick Architecture: source amd64 all Version: 8:6.7.7.10-1 Distribution: unstable Urgency: low Maintainer: ImageMagick Packaging Team pkg-gmagick-im-t...@lists.alioth.debian.org Changed-By: Bastien Roucariès roucaries.bastien+deb...@gmail.com Description: imagemagick - image manipulation programs imagemagick-common - image manipulation programs -- infrastructure imagemagick-dbg - debugging symbols for ImageMagick imagemagick-doc - document files of ImageMagick libmagick++-dev - object-oriented C++ interface to ImageMagick - development files libmagick++5 - object-oriented C++ interface to ImageMagick
Bug#679460: drbd8 - Fails to build two times in a row
Package: src:drbd8 Version: 2:8.3.13-1 Severity: serious drbd8 fails to build two times in a row. The clean target does not unmake modifications: | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building drbd8 using existing ./drbd8_8.3.13.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | drbd8-8.3.13/drbd/drbd_buildtag.c | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/drbd8_8.3.13-1.1.diff.FXc1Rg | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b drbd8-8.3.13 gave error exit status 2 Bastian -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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#678140: Two tiff issues: CVE-2012-2113 / CVE-2012-2088
Moritz Muehlenhoff muehlenh...@univention.de wrote: Package: tiff Severity: grave Tags: security Two new tiff issues have been repored to Red Hat bugzilla, please see these bugs for details: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-2088 https://bugzilla.redhat.com/show_bug.cgi?id=810551 (CVE-2012-2113) Cheers, Moritz Oops, somehow I managed to overlook this bug report. I uploaded tiff 4.0.2 a few days ago. I'll see if that includes these fixes and will see about backporting to the 3.x series. I'm not sure how soon I can do it. I have a very full weekend coming up, but I am at least now aware of the issue. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678792: marked as done (python-scrapy: FTBFS: ImportError: cannot import name uses_query)
Your message dated Thu, 28 Jun 2012 20:53:26 +
with message-id e1skliq-0004e1...@franck.debian.org
and subject line Bug#678792: fixed in python-scrapy 0.14.4-1
has caused the Debian Bug report #678792,
regarding python-scrapy: FTBFS: ImportError: cannot import name uses_query
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.)
--
678792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-scrapy
Version: 0.14.1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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»'
dh_auto_clean
Traceback (most recent call last):
File setup.py, line 93, in module
version = __import__('scrapy').__version__
File /«PKGBUILDDIR»/scrapy/__init__.py, line 18, in module
from scrapy.xlib import twisted_250_monkeypatches, urlparse_monkeypatches
File /«PKGBUILDDIR»/scrapy/xlib/urlparse_monkeypatches.py, line 1, in
module
from urlparse import urlparse, uses_netloc, uses_query
ImportError: cannot import name uses_query
dh_auto_clean: python setup.py clean -a returned exit code 1
make[1]: *** [override_dh_auto_clean] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/24/python-scrapy_0.14.1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: python-scrapy
Source-Version: 0.14.4-1
We believe that the bug you reported is fixed in the latest version of
python-scrapy, which is due to be installed in the Debian FTP archive:
python-scrapy-doc_0.14.4-1_all.deb
to main/p/python-scrapy/python-scrapy-doc_0.14.4-1_all.deb
python-scrapy_0.14.4-1.debian.tar.gz
to main/p/python-scrapy/python-scrapy_0.14.4-1.debian.tar.gz
python-scrapy_0.14.4-1.dsc
to main/p/python-scrapy/python-scrapy_0.14.4-1.dsc
python-scrapy_0.14.4-1_all.deb
to main/p/python-scrapy/python-scrapy_0.14.4-1_all.deb
python-scrapy_0.14.4.orig.tar.gz
to main/p/python-scrapy/python-scrapy_0.14.4.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 678...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ignace Mouzannar mouzan...@gmail.com (supplier of updated python-scrapy
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: Thu, 28 Jun 2012 23:41:01 +0400
Source: python-scrapy
Binary: python-scrapy python-scrapy-doc
Architecture: source all
Version: 0.14.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Ignace Mouzannar mouzan...@gmail.com
Description:
python-scrapy - Python web scraping and crawling framework
python-scrapy-doc - Python web scraping and crawling framework documentation
Closes: 678792
Changes:
python-scrapy (0.14.4-1) unstable; urgency=low
.
* New upstream release.
* debian/patches:
- 01_ftbs_easy_query.diff: corrects FTBS caused by the urlparse
Python module import. (Closes: #678792)
* debian/rules:
- Added exclude on *.egg files.
Checksums-Sha1:
23911f9ba446aa19c46d5872adfd992d44c2459f 2233 python-scrapy_0.14.4-1.dsc
927ead539873f04aba36ff01f784b270501e44f0 726253
python-scrapy_0.14.4.orig.tar.gz
8eef6cd0728971d82370dc7e6302777e16ecdb68 6812
python-scrapy_0.14.4-1.debian.tar.gz
5991853bf62b7df2d24fb413bf755422f7655caa 313872 python-scrapy_0.14.4-1_all.deb
348eda5634d71d4de782b819b570867f21e728cf 530964
python-scrapy-doc_0.14.4-1_all.deb
Checksums-Sha256:
bcdbcf8a0f8a994c8b5e38333a871c46c778318149153b7ff6a27f469b097f4e 2233
python-scrapy_0.14.4-1.dsc
8de12ac37136524ad2fb0d83db10736b03b1d445b6d4c492c053bec78f3d42e6 726253
python-scrapy_0.14.4.orig.tar.gz
Bug#659353: marked as done (drbd8-utils - Warns if version of kernel module and utils does not match)
Your message dated Thu, 28 Jun 2012 21:20:16 + with message-id e1skm8o-0007ns...@franck.debian.org and subject line Bug#659353: fixed in drbd8 2:8.3.13-1.1 has caused the Debian Bug report #659353, regarding drbd8-utils - Warns if version of kernel module and utils does not match 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.) -- 659353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: drbd8-utils Version: 2:8.3.9-1 Severity: important drbdadm warns if the version of the kernel module and the utils does not match: | DRBD module version: 8.3.11 |userland version: 8.3.9 | you should upgrade your drbd tools! The shipped ocf resource agent lets this message out on stderr on every call and it gets properly logged via syslog. I found around 1000 of this since the machine was upgraded two hours ago. As the kernel module is now independant of the utils, it can't longer make assumptions about the version. Either the protocol is stable within a given range and it should just accept that, or it is not. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: drbd8 Source-Version: 2:8.3.13-1.1 We believe that the bug you reported is fixed in the latest version of drbd8, which is due to be installed in the Debian FTP archive: drbd8-utils_8.3.13-1.1_amd64.deb to main/d/drbd8/drbd8-utils_8.3.13-1.1_amd64.deb drbd8_8.3.13-1.1.debian.tar.gz to main/d/drbd8/drbd8_8.3.13-1.1.debian.tar.gz drbd8_8.3.13-1.1.dsc to main/d/drbd8/drbd8_8.3.13-1.1.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 659...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank wa...@debian.org (supplier of updated drbd8 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: Thu, 28 Jun 2012 21:07:04 + Source: drbd8 Binary: drbd8-utils Architecture: source amd64 Version: 2:8.3.13-1.1 Distribution: unstable Urgency: low Maintainer: Debian DRBD Maintainers debian-ha-maintain...@lists.alioth.debian.org Changed-By: Bastian Blank wa...@debian.org Description: drbd8-utils - RAID 1 over tcp/ip for Linux utilities Closes: 659353 679266 679460 Changes: drbd8 (2:8.3.13-1.1) unstable; urgency=low . * Non-maintainer upload. * Fix name of udev rules file. (closes: #679266) * Disable module version warning for sublevel missmatch. (closes: #659353) * Disable regeneration of buildtags file. (closes: #679460) Checksums-Sha1: 3cba9e748437813852e4973a5cecd9a7167de879 1387 drbd8_8.3.13-1.1.dsc 9d7dfbc031ce87957cc961c5ba06d71dc45a9699 15142 drbd8_8.3.13-1.1.debian.tar.gz 407e7eadb38c1d99da8a992e587418c5db99d99b 251418 drbd8-utils_8.3.13-1.1_amd64.deb Checksums-Sha256: f60989abc429b89842fea8bdb5c192eed6a6538a1fe5123e4a10628791dbbbf6 1387 drbd8_8.3.13-1.1.dsc 3d3cd67296dde0147692e3b0c19014772dda0221e628505f3ca9ad75989e3f62 15142 drbd8_8.3.13-1.1.debian.tar.gz 4c26f507b85179953d3b188791825cd2dffd6ae8c17279ca4b8ce3a881302721 251418 drbd8-utils_8.3.13-1.1_amd64.deb Files: ab4acdedac3cc7d5177e83d4c559454e 1387 admin extra drbd8_8.3.13-1.1.dsc dae9073e38f96648a5132b38cd4a940e 15142 admin extra drbd8_8.3.13-1.1.debian.tar.gz b5e20343301286eb42fd10e605b1c127 251418 admin extra drbd8-utils_8.3.13-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk/sx/AACgkQLkAIIn9ODhHuDACg4rGCGNRwE3u2GMp49XR/Ki+T NQoAoKuhI7khaK+4KvnxUKp+mz+KjKes =xYfA -END PGP SIGNATURE- ---End Message---
Bug#679266: marked as done (drbd8-utils - Lost udev rules)
Your message dated Thu, 28 Jun 2012 21:20:16 + with message-id e1skm8o-0007ny...@franck.debian.org and subject line Bug#679266: fixed in drbd8 2:8.3.13-1.1 has caused the Debian Bug report #679266, regarding drbd8-utils - Lost udev rules 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.) -- 679266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: drbd8 Version: 2:8.3.13-1 Severity: serious drbd8-utils lost its udev rule. It is installed as /lib/udev/rules.d/65-drbd.rules.disabled and therefor ignored. Bastian -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: drbd8 Source-Version: 2:8.3.13-1.1 We believe that the bug you reported is fixed in the latest version of drbd8, which is due to be installed in the Debian FTP archive: drbd8-utils_8.3.13-1.1_amd64.deb to main/d/drbd8/drbd8-utils_8.3.13-1.1_amd64.deb drbd8_8.3.13-1.1.debian.tar.gz to main/d/drbd8/drbd8_8.3.13-1.1.debian.tar.gz drbd8_8.3.13-1.1.dsc to main/d/drbd8/drbd8_8.3.13-1.1.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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank wa...@debian.org (supplier of updated drbd8 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: Thu, 28 Jun 2012 21:07:04 + Source: drbd8 Binary: drbd8-utils Architecture: source amd64 Version: 2:8.3.13-1.1 Distribution: unstable Urgency: low Maintainer: Debian DRBD Maintainers debian-ha-maintain...@lists.alioth.debian.org Changed-By: Bastian Blank wa...@debian.org Description: drbd8-utils - RAID 1 over tcp/ip for Linux utilities Closes: 659353 679266 679460 Changes: drbd8 (2:8.3.13-1.1) unstable; urgency=low . * Non-maintainer upload. * Fix name of udev rules file. (closes: #679266) * Disable module version warning for sublevel missmatch. (closes: #659353) * Disable regeneration of buildtags file. (closes: #679460) Checksums-Sha1: 3cba9e748437813852e4973a5cecd9a7167de879 1387 drbd8_8.3.13-1.1.dsc 9d7dfbc031ce87957cc961c5ba06d71dc45a9699 15142 drbd8_8.3.13-1.1.debian.tar.gz 407e7eadb38c1d99da8a992e587418c5db99d99b 251418 drbd8-utils_8.3.13-1.1_amd64.deb Checksums-Sha256: f60989abc429b89842fea8bdb5c192eed6a6538a1fe5123e4a10628791dbbbf6 1387 drbd8_8.3.13-1.1.dsc 3d3cd67296dde0147692e3b0c19014772dda0221e628505f3ca9ad75989e3f62 15142 drbd8_8.3.13-1.1.debian.tar.gz 4c26f507b85179953d3b188791825cd2dffd6ae8c17279ca4b8ce3a881302721 251418 drbd8-utils_8.3.13-1.1_amd64.deb Files: ab4acdedac3cc7d5177e83d4c559454e 1387 admin extra drbd8_8.3.13-1.1.dsc dae9073e38f96648a5132b38cd4a940e 15142 admin extra drbd8_8.3.13-1.1.debian.tar.gz b5e20343301286eb42fd10e605b1c127 251418 admin extra drbd8-utils_8.3.13-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk/sx/AACgkQLkAIIn9ODhHuDACg4rGCGNRwE3u2GMp49XR/Ki+T NQoAoKuhI7khaK+4KvnxUKp+mz+KjKes =xYfA -END PGP SIGNATURE- ---End Message---
Bug#679322: marked as done (pdksh: add NEWS file for mksh transition)
Your message dated Thu, 28 Jun 2012 21:21:18 + with message-id e1skm9o-0007tm...@franck.debian.org and subject line Bug#679322: fixed in mksh 40.9.20120628-1 has caused the Debian Bug report #679322, regarding pdksh: add NEWS file for mksh transition 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.) -- 679322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pdksh Severity: serious Tags: pending As discussed in IRC today, pdksh symlinked to lksh should not transition to testing without a NEWS file detailing the transition and that users shall switch to mksh as login shell since lksh is not intended for interactive use. Will tackle this ASAP together with fixes for some more remaining issues, having reviewed the old pdksh bugs today. ---End Message--- ---BeginMessage--- Source: mksh Source-Version: 40.9.20120628-1 We believe that the bug you reported is fixed in the latest version of mksh, which is due to be installed in the Debian FTP archive: mksh_40.9.20120628-1.debian.tar.gz to main/m/mksh/mksh_40.9.20120628-1.debian.tar.gz mksh_40.9.20120628-1.dsc to main/m/mksh/mksh_40.9.20120628-1.dsc mksh_40.9.20120628.orig.tar.gz to main/m/mksh/mksh_40.9.20120628.orig.tar.gz pdksh_40.9.20120628-1_all.deb to main/m/mksh/pdksh_40.9.20120628-1_all.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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser t...@mirbsd.de (supplier of updated mksh 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: SHA384 Format: 1.8 Date: Thu, 28 Jun 2012 22:44:00 +0200 Source: mksh Binary: mksh pdksh Architecture: source all Version: 40.9.20120628-1 Distribution: unstable Urgency: low Maintainer: Thorsten Glaser t...@mirbsd.de Changed-By: Thorsten Glaser t...@mirbsd.de Description: mksh - MirBSD Korn Shell pdksh - transitional dummy package to migrate from pdksh to mksh Closes: 48453 220272 517009 679322 Changes: mksh (40.9.20120628-1) unstable; urgency=low . * The “meet a deadline” upload * Update to mksh-HEAD: - [tg] Legacy mksh: use “long”, not “int32_t”, for arithmetics - [tg] Legacy mksh: allow dummy set ±o emacs, gmacs, vi, … - [tg] fix trimming with positional parameters (Closes: #48453) - [tg] ensure that case end tokens are not mixed up (Closes: #220272) - [tg] make alias definitions in mksh -c work (Closes: #517009), hack * Show note about login shell transition in postinst (Closes: #679322) Checksums-Sha1: 7dfb29a4d64afb56db8e282be2db2a2cc0500cc1 2361 mksh_40.9.20120628-1.dsc ffd47929c3cfe2be6096238be4db234aef573d25 342384 mksh_40.9.20120628.orig.tar.gz e867c9d521e07f789bfc4fcd92b3ed1c0205dff7 70603 mksh_40.9.20120628-1.debian.tar.gz 457097c319d5a1c0013c61313cb8ba38296c346f 2674 pdksh_40.9.20120628-1_all.deb Checksums-Sha256: 47a2993ee16312af90b14a201535c9b18fb9e1ffb35a6eab80e981fafe9d8538 2361 mksh_40.9.20120628-1.dsc 734d4c6a6ede72067b9e092d2f07ddff41f20bbea54c42b2b111efb7d00ed9d7 342384 mksh_40.9.20120628.orig.tar.gz d70501fd76ad616b06360b8643a2eaa6a1180cefd7dedf89e70ee7fc47343389 70603 mksh_40.9.20120628-1.debian.tar.gz 1156b6521bd45662ac5d34fc5893dea525cd982295b342a92853c03c178d0578 2674 pdksh_40.9.20120628-1_all.deb Files: 324f7aa4ab18a330f667f419d3044b14 2361 shells optional mksh_40.9.20120628-1.dsc 964e92d258ed2957135e66062b54db7f 342384 shells optional mksh_40.9.20120628.orig.tar.gz 5ceb35e72f670c542fa22a24db0f704e 70603 shells optional mksh_40.9.20120628-1.debian.tar.gz e0e80322bdc44b1366b9a12ca7e9f0ee 2674 oldlibs extra pdksh_40.9.20120628-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MirBSD) iQIcBAEBCQAGBQJP7MRmAAoJEHa1NLLpkAfgUssP/1B7rCQMcUvc7AsnikL4eO8B Jlzh9hp3Ili07xYrAEZ4ZJG+nGyskiL43rflBkQXOONFCjMACa71YWP5jEdJFtEs OD3I77kVJlzBF3N/qrl9aFk+LBS2CBmK3wc0R+l71SElRH7IjpRdkSxYxNqyaWdJ 2+Hd6rXnO9krFs9nPLNzwUs2fmGMTvA5lT265qeyo2LQ3FaWghwTxjkIbFTlo5k7 CEpSNjBzQBGLUboMHM4ziZC2hM2LmQmYe8VXM3zytRdUnA/z3qrQk1mC46VPWb0w HgdAE1f22C65ppqw4cyEFrq4a3L9O/cpFZ81rFNR6z5vyxSoobJpopoI0HFFrX3p mqRicNFWgMgRWP12xCVL15gyjo+bJu80oTGSYF313wA01iyflP4r6Yv8prMBeOCk
Bug#679460: marked as done (drbd8 - Fails to build two times in a row)
Your message dated Thu, 28 Jun 2012 21:20:16 + with message-id e1skm8o-0007o2...@franck.debian.org and subject line Bug#679460: fixed in drbd8 2:8.3.13-1.1 has caused the Debian Bug report #679460, regarding drbd8 - Fails to build two times in a row 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.) -- 679460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:drbd8 Version: 2:8.3.13-1 Severity: serious drbd8 fails to build two times in a row. The clean target does not unmake modifications: | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building drbd8 using existing ./drbd8_8.3.13.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | drbd8-8.3.13/drbd/drbd_buildtag.c | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/drbd8_8.3.13-1.1.diff.FXc1Rg | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b drbd8-8.3.13 gave error exit status 2 Bastian -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: drbd8 Source-Version: 2:8.3.13-1.1 We believe that the bug you reported is fixed in the latest version of drbd8, which is due to be installed in the Debian FTP archive: drbd8-utils_8.3.13-1.1_amd64.deb to main/d/drbd8/drbd8-utils_8.3.13-1.1_amd64.deb drbd8_8.3.13-1.1.debian.tar.gz to main/d/drbd8/drbd8_8.3.13-1.1.debian.tar.gz drbd8_8.3.13-1.1.dsc to main/d/drbd8/drbd8_8.3.13-1.1.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 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank wa...@debian.org (supplier of updated drbd8 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: Thu, 28 Jun 2012 21:07:04 + Source: drbd8 Binary: drbd8-utils Architecture: source amd64 Version: 2:8.3.13-1.1 Distribution: unstable Urgency: low Maintainer: Debian DRBD Maintainers debian-ha-maintain...@lists.alioth.debian.org Changed-By: Bastian Blank wa...@debian.org Description: drbd8-utils - RAID 1 over tcp/ip for Linux utilities Closes: 659353 679266 679460 Changes: drbd8 (2:8.3.13-1.1) unstable; urgency=low . * Non-maintainer upload. * Fix name of udev rules file. (closes: #679266) * Disable module version warning for sublevel missmatch. (closes: #659353) * Disable regeneration of buildtags file. (closes: #679460) Checksums-Sha1: 3cba9e748437813852e4973a5cecd9a7167de879 1387 drbd8_8.3.13-1.1.dsc 9d7dfbc031ce87957cc961c5ba06d71dc45a9699 15142 drbd8_8.3.13-1.1.debian.tar.gz 407e7eadb38c1d99da8a992e587418c5db99d99b 251418 drbd8-utils_8.3.13-1.1_amd64.deb Checksums-Sha256: f60989abc429b89842fea8bdb5c192eed6a6538a1fe5123e4a10628791dbbbf6 1387 drbd8_8.3.13-1.1.dsc 3d3cd67296dde0147692e3b0c19014772dda0221e628505f3ca9ad75989e3f62 15142 drbd8_8.3.13-1.1.debian.tar.gz 4c26f507b85179953d3b188791825cd2dffd6ae8c17279ca4b8ce3a881302721 251418 drbd8-utils_8.3.13-1.1_amd64.deb Files: ab4acdedac3cc7d5177e83d4c559454e 1387 admin extra drbd8_8.3.13-1.1.dsc dae9073e38f96648a5132b38cd4a940e 15142 admin extra drbd8_8.3.13-1.1.debian.tar.gz b5e20343301286eb42fd10e605b1c127 251418 admin extra drbd8-utils_8.3.13-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk/sx/AACgkQLkAIIn9ODhHuDACg4rGCGNRwE3u2GMp49XR/Ki+T NQoAoKuhI7khaK+4KvnxUKp+mz+KjKes =xYfA -END PGP SIGNATURE- ---End Message---
Bug#679464: Missing copyright information
Source: isl Version: 0.08-1 Severity: serious debian/copyright file is incomplete: - interface/python.cc, interface/extract_interface.cc: 2-clause BSD - isl_qsort.c: Copied from glibc, LGPL-2.1 stands, but not the copyright holders - doc/chicago.bst: % Copyright (C) 1985, all rights reserved. % Copying of this file is authorized only if either % (1) you make absolutely no changes to your copy, including name, or % (2) if you do make changes, you name it something other than 'newapa.bst'. % There are undoubtably bugs in this style. If you make bug fixes, % improvements, etc. please let me know. My e-mail address is: %spen...@cgrg.ohio.state.edu or 71160.3...@compuserve.com This is, as far as I see, DFSG free, and valid, as the file was renamed. But nevertheless, this is definitely not LGPL-2.1. - isl_coalesce.c (and a couple of other files) has Copyright 2012 Ecole Normale Superieure -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (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#679460: drbd8 - Fails to build two times in a row
On Thu, Jun 28, 2012 at 10:50:34PM +0200, Bastian Blank wrote: drbd8 fails to build two times in a row. The clean target does not unmake modifications: I uploaded the pending NMU including a fix for this problem. Attached is the complete patch. Bastian -- Each kiss is as the first. -- Miramanee, Kirk's wife, The Paradise Syndrome, stardate 4842.6 diff -Nru drbd8-8.3.13/debian/changelog drbd8-8.3.13/debian/changelog --- drbd8-8.3.13/debian/changelog 2012-06-15 20:35:07.0 +0200 +++ drbd8-8.3.13/debian/changelog 2012-06-28 23:07:05.0 +0200 @@ -1,3 +1,13 @@ +drbd8 (2:8.3.13-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix name of udev rules file. (closes: #679266) + * Disable module version warning for sublevel missmatch. +(closes: #659353) + * Disable regeneration of buildtags file. (closes: #679460) + + -- Bastian Blank wa...@debian.org Thu, 28 Jun 2012 21:07:04 + + drbd8 (2:8.3.13-1) unstable; urgency=low * Update to latest version for Linux 3.2.0 diff -Nru drbd8-8.3.13/debian/patches/disable-buildtags drbd8-8.3.13/debian/patches/disable-buildtags --- drbd8-8.3.13/debian/patches/disable-buildtags 1970-01-01 01:00:00.0 +0100 +++ drbd8-8.3.13/debian/patches/disable-buildtags 2012-06-28 23:00:43.0 +0200 @@ -0,0 +1,25 @@ +Description: Disable regeneration of buildtags file +Author: Bastian Blank wa...@debian.org +Bug-Debian: http://bugs.debian.org/679460 + +--- +--- a/drbd/Makefile b/drbd/Makefile +@@ -106,8 +106,6 @@ + false;\ + fi + +-.PHONY: drbd_buildtag.c +- + drbd_buildtag.c: + @set -e; exec $@.new; \ + echo -e /* automatically generated. DO NOT EDIT. */; \ +@@ -132,7 +130,7 @@ + echo -e \t\t\ build by $$USER@$$HOSTNAME, `date +%F %T`\;\n}; \ + mv --force $@.new $@ + +- kbuild: drbd_buildtag.c ++ kbuild: + @rm -f .drbd_kernelrelease* + -test -f ../scripts/adjust_drbd_config_h.sh \ + KDIR=$(KDIR) O=$(O) $(SHELL) ../scripts/adjust_drbd_config_h.sh diff -Nru drbd8-8.3.13/debian/patches/disable-version-warning drbd8-8.3.13/debian/patches/disable-version-warning --- drbd8-8.3.13/debian/patches/disable-version-warning 1970-01-01 01:00:00.0 +0100 +++ drbd8-8.3.13/debian/patches/disable-version-warning 2012-06-27 15:31:05.0 +0200 @@ -0,0 +1,16 @@ +Description: Disable module version warning for sublevel missmatch +Author: Bastian Blank wa...@debian.org +Bug-Debian: http://bugs.debian.org/659353 + +--- +--- drbd8-8.3.13.orig/user/drbdadm_usage_cnt.c drbd8-8.3.13/user/drbdadm_usage_cnt.c +@@ -264,7 +264,7 @@ void warn_on_version_mismatch(void) + else if (cmp 0xff00) /* userland is newer minor version */ + msg = please don't mix different DRBD series.; + else/* userland is newer, but only differ in sublevel. */ +- msg = preferably kernel and userland versions should match.; ++ return; + + fprintf(stderr, DRBD module version: %u.%u.%u\n + userland version: %u.%u.%u\n%s\n, diff -Nru drbd8-8.3.13/debian/patches/series drbd8-8.3.13/debian/patches/series --- drbd8-8.3.13/debian/patches/series 2012-06-15 20:37:35.0 +0200 +++ drbd8-8.3.13/debian/patches/series 2012-06-28 22:57:57.0 +0200 @@ -1,2 +1,5 @@ 0001-init-interactive-debian-613654.patch 0002-dpkg-statoverride-instead-of-chgrp-chmod.patch +udev-rules-name +disable-version-warning +disable-buildtags diff -Nru drbd8-8.3.13/debian/patches/udev-rules-name drbd8-8.3.13/debian/patches/udev-rules-name --- drbd8-8.3.13/debian/patches/udev-rules-name 1970-01-01 01:00:00.0 +0100 +++ drbd8-8.3.13/debian/patches/udev-rules-name 2012-06-27 15:28:09.0 +0200 @@ -0,0 +1,16 @@ +Description: Fix name of udev rules file. (closes: #679266) +Author: Bastian Blank wa...@debian.org +Bug-Debian: http://bugs.debian.org/679266 + +--- +--- drbd8-8.3.13.orig/scripts/Makefile.in drbd8-8.3.13/scripts/Makefile.in +@@ -130,7 +130,7 @@ endif + install-udev: + ifeq ($(WITH_UDEV),yes) + mkdir -p $(DESTDIR)$(sysconfdir)/udev/rules.d +- install -m 644 drbd.rules $(DESTDIR)$(sysconfdir)/udev/rules.d/65-drbd.rules$(UDEV_RULE_SUFFIX) ++ install -m 644 drbd.rules $(DESTDIR)$(sysconfdir)/udev/rules.d/65-drbd.rules + endif + + install-bashcompletion:
Processed: Re: redmine: 500 Internal Server Error. Incompatible character encodings: ASCII-8BIT and UTF-8
Processing commands for cont...@bugs.debian.org: tag 678515 + confirmed Bug #678515 [redmine] redmine: 500 Internal Server Error. Incompatible character encodings: ASCII-8BIT and UTF-8 Added tag(s) confirmed. severity 678515 grave Bug #678515 [redmine] redmine: 500 Internal Server Error. Incompatible character encodings: ASCII-8BIT and UTF-8 Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 678515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678515 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#678575: wheezy has Icedove 10
Wheezy has stable Icedove 10, rather than one of later snapshots (I kind of refuse to call them releases). Thus, if you have an incompatible version of it, you have non-wheezy apt sources anyway. It would be nice to have a newer version of firetray, but only if it works with Icedove 10 as well. In any case, I wouldn't call this bug RC for wheezy. -- I was born an ugly, dumb and work-loving child, then an evil midwife replaced me in the crib. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 678269
Processing commands for cont...@bugs.debian.org: close 678269 0.12.1+git20120407.aaa852f-1 Bug #678269 [sup-mail] sup-mail: Sup doesnt start anymore on Sid with ruby1.9 Marked as fixed in versions sup-mail/0.12.1+git20120407.aaa852f-1. Bug #678269 [sup-mail] sup-mail: Sup doesnt start anymore on Sid with ruby1.9 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 678269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678269 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#678269: closing 678269
close 678269 0.12.1+git20120407.aaa852f-1 thanks Current version of sup-mail runs with Ruby 1.9.1, thus closing. -- Per -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667871: marked as done (gnustep-dl2: FTBFS with GCC-4.7)
Your message dated Thu, 28 Jun 2012 22:04:07 + with message-id e1skmop-00037z...@franck.debian.org and subject line Bug#667871: fixed in gnustep-dl2 0.12.0-9 has caused the Debian Bug report #667871, regarding gnustep-dl2: FTBFS with GCC-4.7 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.) -- 667871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gnustep-dl2 Version: 0.12.0-8 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least i386 with gcc-4.7/gobjc-4.7, but succeeds to build with gcc-4.6/gobjc-4.6. The severity of this report may be raised before the wheezy release. gcc-4.7 EOGenericRecord.m -c \ -MMD -MP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -g -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -fgnu-runtime -DDEBUG -fconstant-string-class=NSConstantString -I./. -I.. -I. -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ -o obj/EOControl.obj/EOGenericRecord.m.o EOGenericRecord.m: In function ‘+[EOGenericRecord eoFormatSizeDictionary:]’: EOGenericRecord.m:1467:24: warning: variable ‘processed’ set but not used [-Wunused-but-set-variable] EOGenericRecord.m: In function ‘-[NSObject(EOCalculateSize) eoGetSize]’: EOGenericRecord.m:1525:19: error: dereferencing pointer to incomplete type EOGenericRecord.m: In function ‘+[EOFault(EOCalculateSize) eoCalculateSizeWith:forFault:]’: EOGenericRecord.m:1621:26: error: dereferencing pointer to incomplete type make[5]: *** [obj/EOControl.obj/EOGenericRecord.m.o] Error 1 ---End Message--- ---BeginMessage--- Source: gnustep-dl2 Source-Version: 0.12.0-9 We believe that the bug you reported is fixed in the latest version of gnustep-dl2, which is due to be installed in the Debian FTP archive: gnustep-dl2-postgresql-adaptor_0.12.0-9_amd64.deb to main/g/gnustep-dl2/gnustep-dl2-postgresql-adaptor_0.12.0-9_amd64.deb gnustep-dl2-sqlite-adaptor_0.12.0-9_amd64.deb to main/g/gnustep-dl2/gnustep-dl2-sqlite-adaptor_0.12.0-9_amd64.deb gnustep-dl2_0.12.0-9.debian.tar.gz to main/g/gnustep-dl2/gnustep-dl2_0.12.0-9.debian.tar.gz gnustep-dl2_0.12.0-9.dsc to main/g/gnustep-dl2/gnustep-dl2_0.12.0-9.dsc gnustep-dl2_0.12.0-9_amd64.deb to main/g/gnustep-dl2/gnustep-dl2_0.12.0-9_amd64.deb libgnustep-dl2-0d_0.12.0-9_amd64.deb to main/g/gnustep-dl2/libgnustep-dl2-0d_0.12.0-9_amd64.deb libgnustep-dl2-dev_0.12.0-9_amd64.deb to main/g/gnustep-dl2/libgnustep-dl2-dev_0.12.0-9_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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Federico Gimenez Nieto fgime...@coit.es (supplier of updated gnustep-dl2 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: Wed, 27 Jun 2012 08:06:36 +0200 Source: gnustep-dl2 Binary: gnustep-dl2 libgnustep-dl2-0d libgnustep-dl2-dev gnustep-dl2-postgresql-adaptor gnustep-dl2-sqlite-adaptor Architecture: source amd64 Version: 0.12.0-9 Distribution: unstable Urgency: low Maintainer: Federico Gimenez Nieto fgime...@coit.es Changed-By: Federico Gimenez Nieto fgime...@coit.es Description: gnustep-dl2 - Objective-C Classes needed for Database Access gnustep-dl2-postgresql-adaptor - gnustep-dl2 adaptor to connect to PostgreSQL gnustep-dl2-sqlite-adaptor - gnustep-dl2 adaptor to connect to SQLite libgnustep-dl2-0d - bundle of runtime libraries for gnustep-dl2 libgnustep-dl2-dev - development files for gnustep-dl2 runtime libraries Closes: 667871 Changes: gnustep-dl2 (0.12.0-9) unstable; urgency=low . * gcc-4.7.patch by Yavor Doganov ya...@gnu.org (Closes: #667871) * debian/control: bumped Standards-Version: 3.9.3 * debian/rules: added -z relro to LDFLAGS to prevent hardening-no-relro * debian/copyright: updated date Checksums-Sha1: 0b583c5f4198ea05a2dc85f29b33030b57b74e62 2384 gnustep-dl2_0.12.0-9.dsc c674882b92a3653b22b95fd8c8dbb5ab2a7872e7 22332
Bug#678845: svn-buildpackage: svn-inject fails with subversion 1.7
[Stefano Rivera] Since upgrading to subversion 1.7, svn-inject no longer works: ... svn co svn+ssh://purcell/tmp/test/pycparser/trunk /tmp/tmp.jKa9wdfMh5/trunk svn: E125001: Couldn't determine absolute path of '.' svn: E02: No such file or directory mkdir -p /tmp/tmp.jKa9wdfMh5/trunk svn -m Creating trunk directory import /tmp/tmp.jKa9wdfMh5/trunk svn+ssh://purcell/tmp/test/pycparser/trunk svn: E125001: Couldn't determine absolute path of '.' svn: E02: No such file or directory Command 'svn -m Creating trunk directory import /tmp/tmp.jKa9wdfMh5/trunk svn+ssh://purcell/tmp/test/pycparser/trunk' failed in 'unknown', how to continue now? [Qri?]: q Aborting. That is svn complaining because, apparently, it is run inside a directory that has been deleted. How would I reproduce your bug - how did you invoke svn-inject? I tried, and could not. And I can't find where svn-bp _would_ delete the cwd while it is still the cwd. (I am not a svn-bp user, so I don't know the common use patterns.) The fact that svn aborts because it can't turn '.' into an absolute path is arguably a bug, which I've pinged upstream about. svn wants to canonicalize the paths it acts upon, and then report them relative to the current directory - that's why it attempts to getcwd(). In fact this is not relevant if you pass it absolute pathnames, as svn-inject does, but getting svn to look up the absolute cwd only when it is working on relative paths turns out to not be trivial. Peter -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679468: new epoch breaks all symlinks
Package: llvm Version: 1:3.0-12 Severity: grave Tags: patch Since the epoch was added to CV_LLVM, the computation of V_LLVM was not updated and all symbolic links are therefore broken, rendering the package unusable. I suggest changing: V_LLVM := $(shell echo $(CV_LLVM) | sed 's/-[^-]*$$//') into: V_LLVM := $(shell echo $(CV_LLVM) | sed 's/^[0-9]*://' | sed 's/-[^-]*$$//') -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages llvm depends on: ii llvm-3.0 3.0-9 ii llvm-runtime 1:3.0-12 llvm recommends no packages. llvm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669488: marked as done (python-django-voting: FTBFS: ImportError: cannot import name run_tests)
Your message dated Thu, 28 Jun 2012 22:40:32 + with message-id e1skno4-0005re...@franck.debian.org and subject line Bug#669488: fixed in python-django-voting 0.1-2 has caused the Debian Bug report #669488, regarding python-django-voting: FTBFS: ImportError: cannot import name run_tests 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.) -- 669488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-django-voting Version: 0.1-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[1]: Entering directory `/«PKGBUILDDIR»' set -e; \ cd voting/tests; \ for python in python2.7 python2.6; do \ PYTHONPATH=:../.. $python runtests.py; \ done Traceback (most recent call last): File runtests.py, line 4, in module from django.test.simple import run_tests ImportError: cannot import name run_tests make[1]: *** [override_dh_auto_test] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/python-django-voting_0.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: python-django-voting Source-Version: 0.1-2 We believe that the bug you reported is fixed in the latest version of python-django-voting, which is due to be installed in the Debian FTP archive: python-django-voting_0.1-2.debian.tar.gz to main/p/python-django-voting/python-django-voting_0.1-2.debian.tar.gz python-django-voting_0.1-2.dsc to main/p/python-django-voting/python-django-voting_0.1-2.dsc python-django-voting_0.1-2_all.deb to main/p/python-django-voting/python-django-voting_0.1-2_all.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. Bernhard Reiter ock...@raz.or.at (supplier of updated python-django-voting 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: Fri, 22 Jun 2012 02:21:19 +0200 Source: python-django-voting Binary: python-django-voting Architecture: source all Version: 0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Bernhard Reiter ock...@raz.or.at Description: python-django-voting - generic voting application for Django Closes: 669488 Changes: python-django-voting (0.1-2) unstable; urgency=medium . * debian/patches/django14, debian/patches/series: Fix for Django 1.4 compatibility (Closes: #669488) * debian/control: Bump Standards-Version to 3.9.2. * debian/copyright: Update to comply with copyright-format 1.0. Checksums-Sha1: 6852f0c8011cb52286aebb8f87b3fd5512e27164 2119 python-django-voting_0.1-2.dsc 3bf46fdfa4efb66703a8c81882f4b3bcfe61816f 5610 python-django-voting_0.1-2.debian.tar.gz 7485385d5faf8620f727743341118ffb263edb4d 17252 python-django-voting_0.1-2_all.deb Checksums-Sha256: e94f006e288933dcfed95613ac5629864310662ffa057bd9bd8fabca71ca4da3 2119 python-django-voting_0.1-2.dsc 2aaef9cf9749a85723a0329cbff8b1aba8ef60285403dea522504d47742d97a7 5610 python-django-voting_0.1-2.debian.tar.gz 48e856e2e741413cb483be22eafb0fd4968da1d1dbae4ca9ce2df312e90a8382 17252 python-django-voting_0.1-2_all.deb Files: 3f24a1f934201116aa57b7b8fe1e07a9 2119 python optional python-django-voting_0.1-2.dsc 94f1091be8f1e4ad14fadcbdb7e82c43 5610 python optional python-django-voting_0.1-2.debian.tar.gz c0d79b1cee8eb6686b60ff878ec7dfbe 17252 python optional python-django-voting_0.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP7NT0AAoJEEkIatPr4vMfdo4P/iM3QVRcS6EMsVyqZdDMIxj1
