Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg
Package: python3-coverage Version: 3.7+dfsg.1-4 Severity: serious Justification: fails to install/upgrade Dear Maintainer, Today’s update of python3-coverage failed with: | Unpacking python3-coverage (3.7+dfsg.1-4+b1) over (3.7+dfsg.1-4) ... | dpkg: error processing archive /var/cache/apt/archives/python3-coverage_3.7+dfsg.1-4+b1_i386.deb (--unpack): | trying to overwrite '/usr/lib/python3/dist-packages/coverage/tracer.cpython-34dm-i386-linux-gnu.so', which is also in package python3-coverage-dbg 3.7+dfsg.1-4+b1 | Errors were encountered while processing: | /var/cache/apt/archives/python3-coverage_3.7+dfsg.1-4+b1_i386.deb Looks like both python3-coverage and python3-coverage-dbg ship that file (tracer.cpython-34dm-$MULTIARCH.so), while it should be only present in python3-coverage-dbg. The same applies to tracer.cpython-33dm-$MULTIARCH.so. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#738811: handbrake: crashes after source DVD is selected
That's funny. I didn't notice this option. As soon as I unchecked the box (and started using libdvdread) it works. So the problem was in dvdnav actually (or at least according to the checker box label). On Tue, Feb 25, 2014 at 7:53 AM, Dmitry Smirnov only...@member.fsf.orgwrote: Are you using dvdnav or libdvdread (check in File/Preferences/Advanced)? libdvdread used to be problematic in the past and once it was causing similar crash, see #688574. Unfortunately it looks like it hasn't been properly fixed which makes me wonder if it hit us again... -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B
Bug#738811: handbrake: crashes after source DVD is selected
Am Dienstag, den 25.02.2014, 09:51 +0100 schrieb Jan Korous: That's funny. I didn't notice this option. As soon as I unchecked the box (and started using libdvdread) it works. So the problem was in dvdnav actually (or at least according to the checker box label). Let's hope new new releases currently prepared at VLC bring some improvement. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738392: marked as done (proofgeneral: FTBFS: Latex errors)
Your message dated Tue, 25 Feb 2014 09:20:02 +
with message-id e1wiebg-0007lo...@franck.debian.org
and subject line Bug#738392: fixed in proofgeneral 4.3~pre130510-1.1
has caused the Debian Bug report #738392,
regarding proofgeneral: FTBFS: Latex errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
738392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: proofgeneral
Version: 4.3~pre130510-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
make[4]: Entering directory `/«PKGBUILDDIR»/doc'
texi2pdf ProofGeneral.texi
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
restricted \write18 enabled.
entering extended mode
(./ProofGeneral.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2013-09-11.11]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 14 February 2011
) localization, formatting, and turning on texinfo input format.)
./ProofGener
al-image.jpg [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
(Preface) Cross reference values unknown; you must run TeX again. [1] [2]
Chapter 1 [3] [4] [5] [6] [7] Chapter 2 [8] [9] [10] [11] [12] [13] [14]
[15] [16] [17]
Underfull \hbox (badness 1) in paragraph at lines 1683--1687
[]@textsl warning[]@textrm : this com-mand risks spoil-ing
syn-chro-niza-tion
if the test
[18] Chapter 3 [19] [20] [21] [22] [23] [24] [25] Chapter 4 [26] [27] [28]
[29] [30] Chapter 5 [31] [32] [33] [34] Chapter 6 [35] [36] Chapter 7 [37]
[38] [39] Chapter 8 [40] [41] [42] [43] [44] [45]
Underfull \hbox (badness 1) in paragraph at lines 3654--3657
[]@textrm This op-tion is com-pat-i-ble with `@texttt
proof-prog-name-ask[][]@
textrm '[]. No ef-fect if
[46] [47] [48] Chapter 9 [49] [50] [51] [52] Chapter 10 [53] [54] Chapter 11
[55] [56] [57] [58] [59] [60]
Underfull \hbox (badness 1) in paragraph at lines 4656--4658
[]@textrm After the sub-sti-tu-tion the com-mand can be changed in the
mini-bu
f-fer if
Underfull \hbox (badness 1) in paragraph at lines 4666--4668
[]@textrm This op-tion can be set/reset via menu `@texttt Coq - Settings -
C
onfirm External
kpathsea: Running mktextfm ecrm1095
mkdir: cannot create directory '././sbuild-nonexistent': Permission denied
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode;
input ecrm1095
This is METAFONT, Version 2.718281 (TeX Live 2013/Debian)
kpathsea: Running mktexmf ecrm1095
! I can't find file `ecrm1095'.
* ...ljfour; mag:=1; nonstopmode; input ecrm1095
Please type another input file name
! Emergency stop.
* ...ljfour; mag:=1; nonstopmode; input ecrm1095
Transcript written on mfput.log.
grep: ecrm1095.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input
ecrm1095' failed to make ecrm1095.tfm.
kpathsea: Appending font creation commands to missfont.log.
[61] [62] [63] Chapter 12 [64] [65] [66]
./ProofGeneral.texi:5154: Font @thisecfont=ecrm1095 at 11.0pt not loadable:
Met
ric (TFM) file not found.
to be read again
@thisecfont
@{-{@ifmonospace @else @ecfont
@fi @char 123}
l.5154 Inserts @@@{
text @} (anti-quotation).
?
./ProofGeneral.texi:5154: Emergency stop.
to be read again
@thisecfont
@{-{@ifmonospace @else @ecfont
@fi @char 123}
l.5154 Inserts @@@{
text @} (anti-quotation).
./ProofGeneral.texi:5154: == Fatal error occurred, no output PDF file
produce
d!
Transcript written on ProofGeneral.log.
/usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
make[4]: *** [ProofGeneral.pdf] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/02/08/proofgeneral_4.3~pre130510-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
Bug#739989: debian-installer-utils: log-output change breaks speech synthesis
On Tue, Feb 25, 2014 at 09:10:38AM +0300, Cyril Brulebois wrote: Did you see my follow-up mail[1]? It looks to me it does not only trigger the espeakup hang, but a whole bunch of other hangs. I did, but without data I didn't have time to trawl through looking for them. I'm not asserting that the cause for this is by any means unique to espeakup. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Probably related to Tilt API changes
Processing commands for cont...@bugs.debian.org:
severity 738393 normal
Bug #738393 [src:camping] camping: FTBFS: ERROR: Test ruby1.9.1 failed.
Severity set to 'normal' from 'serious'
affects 738488 camping
Bug #738488 {Done: Antonio Terceiro terce...@debian.org} [ruby-tilt]
ruby-tilt: Broke compatibility with all rdepends
Ignoring request to set affects of bug 738488 to the same value previously set
usertag 738393 +will-break-if-tilt-2.0-is-uploaded
User is pau...@debian.org
There were no usertags set.
Usertags are now: will-break-if-tilt-2.0-is-uploaded.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
738393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738393
738488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738488
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#738393: Probably related to Tilt API changes
severity 738393 normal affects 738488 camping usertag 738393 +will-break-if-tilt-2.0-is-uploaded thanks Hi, I'm pretty sure (looking at the timeline) that the build issues were due to Tilt suddenly changing it's API. This was fixed by a reupload of ruby-tilt 2.0.0+really1.4.1-1 but will break Camping again once Tilt 2.0.0 is really uploaded. For now, the FTBFS is no longer reproducible. Cheers, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740064: dhelp: Weekly cron job always fails.
Package: dhelp Version: 0.6.21+nmu3 Severity: grave Justification: renders package unusable Dear Maintainer, I will paste (last) mail I received - I received one each week. I didn't change standard configuration of this package so it is failing by default. I also deleted this package recently as it was blocking some updates/transitions. Date: Sun, 16 Feb 2014 06:47:13 + From: Cron Daemon root@localhost To: root@localhost Subject: Cron root@khaganate test -x /usr/sbin/anacron || ( cd / run-parts --report /etc/cron.weekly ) /etc/cron.weekly/dhelp: /usr/lib/ruby/vendor_ruby/debian.rb:24:in `require': no such file to load -- debian_version (LoadError) from /usr/lib/ruby/vendor_ruby/debian.rb:24 from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/cgimap.rb:23:in `require' from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/cgimap.rb:23 from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/html.rb:2:in `require' from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/html.rb:2 from /usr/sbin/dhelp_parse:28:in `require' from /usr/sbin/dhelp_parse:28 /usr/lib/ruby/vendor_ruby/debian.rb:24:in `require': no such file to load -- debian_version (LoadError) from /usr/lib/ruby/vendor_ruby/debian.rb:24 from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/cgimap.rb:23:in `require' from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/cgimap.rb:23 from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/html.rb:2:in `require' from /usr/lib/ruby/vendor_ruby/1.8/dhelp/exporter/html.rb:2 from /usr/sbin/dhelp_parse:28:in `require' from /usr/sbin/dhelp_parse:28 run-parts: /etc/cron.weekly/dhelp exited with return code 1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-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 Versions of packages dhelp depends on: ii doc-base 0.10.5 pn libdata-page-perl none ii libhtml-parser-perl 3.71-1+b1 ii liblocale-gettext-perl1.05-7+b2 ii libtemplate-perl 2.24-1.1+b1 ii liburi-perl 1.60-1 ii perl-modules 5.18.2-2 ii poppler-utils 0.22.5-4 pn pstotext none pn ruby-bdb | libdb-ruby1.8 none ii ruby-debian 0.3.8+b2 ii ruby-gettext 3.0.3-2 pn ruby1.8 none pn swish++ none ii ucf 3.0027+nmu1 Versions of packages dhelp recommends: ii chromium [www-browser] 32.0.1700.123-2 ii elinks [www-browser]0.12~pre6-4 ii midori [www-browser]0.4.3+dfsg-0.1 Versions of packages dhelp suggests: pn catdvi none pn httpd-cgi none pn info2www none pn man2html none -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org:
reassign maven-repo-helper 740001 74 739998
Unknown command or malformed arguments to command.
found 739998 1.8.6
Bug #739998 [src:cobertura] cobertura: FTBFS: Maven error
The source 'cobertura' and version '1.8.6' do not appear to match any binary
packages
Marked as found in versions cobertura/1.8.6.
found 74 1.8.6
Bug #74 [src:checkstyle] checkstyle: FTBFS: Maven error
The source 'checkstyle' and version '1.8.6' do not appear to match any binary
packages
Marked as found in versions checkstyle/1.8.6.
found 740001 1.8.6
Bug #740001 [src:openjpa] openjpa: FTBFS: Maven error
The source 'openjpa' and version '1.8.6' do not appear to match any binary
packages
Marked as found in versions openjpa/1.8.6.
merge 740001 74 739998
Bug #740001 [src:openjpa] openjpa: FTBFS: Maven error
Unable to merge bugs because:
package of #739998 is 'src:cobertura' not 'src:openjpa'
package of #74 is 'src:checkstyle' not 'src:openjpa'
Failed to merge 740001: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x18c7840)',
'requester', 'Emmanuel Bourg ebo...@apache.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '530c7752.7040...@apache.org',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', 'merge 740001 74
739998', 'clonebugs', 'HASH(0x180b2a0)', 'limit', 'HASH(0x1801810)',
'common_control_options', 'ARRAY(0x1801858)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
End of message, stopping processing here.
Please contact me if you need assistance.
--
739998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739998
74: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=74
740001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740001
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#736392: octave-plplot: FTBFS with Octave 3.8
trying to fix this in Ubuntu trusty (14.04), ... - applied the octave patch in swig2.0 (2.0.11-1ubuntu2) - plplot still fails to build, apparently with the very same error messages. https://launchpad.net/ubuntu/+source/plplot/5.9.9-5ubuntu8 Is there anything additional needed? Thanks, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736392: octave-plplot: FTBFS with Octave 3.8
Am 25.02.2014 12:08, schrieb Matthias Klose: trying to fix this in Ubuntu trusty (14.04), ... - applied the octave patch in swig2.0 (2.0.11-1ubuntu2) same with swig 2.0.12. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738424: marked as done (libraw: FTBFS: dpkg-gensymbols failures)
Your message dated Tue, 25 Feb 2014 12:00:07 + with message-id e1wiggb-00019n...@franck.debian.org and subject line Bug#738424: fixed in libraw 0.16.0-1 has caused the Debian Bug report #738424, regarding libraw: FTBFS: dpkg-gensymbols failures 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.) -- 738424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libraw Version: 0.15.4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140208 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' dh_makeshlibs -V 'libraw9 (= 0.15.1-1)' dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libraw9/DEBIAN/symbols doesn't match completely debian/libraw9.symbols.amd64 --- debian/libraw9.symbols.amd64 (libraw9_0.15.4-1_amd64) +++ dpkg-gensymbolsKal__d 2014-02-09 02:31:24.692183334 + @@ -1,5 +1,5 @@ libraw.so.9 libraw9 #MINVER# - .gomp_critical_user_dataupdate@Base 0.15.1 +#MISSING: 0.15.4-1# .gomp_critical_user_dataupdate@Base 0.15.1 _ZN16LibRaw_constants7xyz_rgbE@Base 0.15.1 _ZN16LibRaw_constants9d65_whiteE@Base 0.15.1 _ZN18LibRaw_byte_buffer10set_bufferEPvj@Base 0.15.1 @@ -380,7 +380,7 @@ libraw_version@Base 0.15.1 libraw_versionNumber@Base 0.15.1 libraw_r.so.9 libraw9 #MINVER# - .gomp_critical_user_dataupdate@Base 0.15.1 +#MISSING: 0.15.4-1# .gomp_critical_user_dataupdate@Base 0.15.1 _ZN16LibRaw_constants7xyz_rgbE@Base 0.15.1 _ZN16LibRaw_constants9d65_whiteE@Base 0.15.1 _ZN18LibRaw_byte_buffer10set_bufferEPvj@Base 0.15.1 dh_makeshlibs: dpkg-gensymbols -plibraw9 -Idebian/libraw9.symbols.amd64 -Pdebian/libraw9 -edebian/libraw9/usr/lib/x86_64-linux-gnu/libraw.so.9.0.0 -edebian/libraw9/usr/lib/x86_64-linux-gnu/libraw_r.so.9.0.0 returned exit code 1 make[1]: *** [override_dh_makeshlibs] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/02/08/libraw_0.15.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: libraw Source-Version: 0.16.0-1 We believe that the bug you reported is fixed in the latest version of libraw, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 738...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Falavigna dktrkr...@debian.org (supplier of updated libraw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2014 18:53:46 +0100 Source: libraw Binary: libraw10 libraw-bin libraw-dev libraw-doc Architecture: source amd64 all Version: 0.16.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Shotwell Maintainers pkg-shotwell-ma...@lists.alioth.debian.org Changed-By: Luca Falavigna dktrkr...@debian.org Description: libraw-bin - raw image decoder library (tools) libraw-dev - raw image decoder library (development files) libraw-doc - raw image decoder library (documentation) libraw10 - raw image decoder library Closes: 738424 Changes: libraw (0.16.0-1) unstable; urgency=medium . * New upstream release. * debian/control: - Re-add myself as Uploader. - Bump Standards-Version to 3.9.5. * debian/copyright: - Update license information. * debian/libraw10.symbol: - Renamed from libraw9.symbols.amd64 to match new binary, refreshed with the new symbols (Closes: #738424). Checksums-Sha1: 17a8326943bf83939f7059456c53df016e01e2e2 2042 libraw_0.16.0-1.dsc 492239aa209b1ddd1f030da4fc2978498c32a29b 1472935 libraw_0.16.0.orig.tar.gz
Processed: your mail
Processing commands for cont...@bugs.debian.org: reassign 739998 maven-repo-helper Bug #739998 [src:cobertura] cobertura: FTBFS: Maven error Bug reassigned from package 'src:cobertura' to 'maven-repo-helper'. No longer marked as found in versions cobertura/1.8.6 and cobertura/1.9.4.1+dfsg-3. Ignoring request to alter fixed versions of bug #739998 to the same values previously set reassign 74 maven-repo-helper Bug #74 [src:checkstyle] checkstyle: FTBFS: Maven error Bug reassigned from package 'src:checkstyle' to 'maven-repo-helper'. No longer marked as found in versions checkstyle/1.8.6 and checkstyle/5.7-1. Ignoring request to alter fixed versions of bug #74 to the same values previously set reassign 740001 maven-repo-helper Bug #740001 [src:openjpa] openjpa: FTBFS: Maven error Bug reassigned from package 'src:openjpa' to 'maven-repo-helper'. No longer marked as found in versions openjpa/1.8.6 and openjpa/2.2.2-1. Ignoring request to alter fixed versions of bug #740001 to the same values previously set found 739998 1.8.6 Bug #739998 [maven-repo-helper] cobertura: FTBFS: Maven error Marked as found in versions maven-repo-helper/1.8.6. found 74 1.8.6 Bug #74 [maven-repo-helper] checkstyle: FTBFS: Maven error Marked as found in versions maven-repo-helper/1.8.6. found 740001 1.8.6 Bug #740001 [maven-repo-helper] openjpa: FTBFS: Maven error Marked as found in versions maven-repo-helper/1.8.6. merge 740001 74 739998 Bug #740001 [maven-repo-helper] openjpa: FTBFS: Maven error Bug #739998 [maven-repo-helper] cobertura: FTBFS: Maven error Bug #74 [maven-repo-helper] checkstyle: FTBFS: Maven error Merged 739998 74 740001 End of message, stopping processing here. Please contact me if you need assistance. -- 739998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739998 74: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=74 740001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740001 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#733352: Bowtie and tophat fail to build with seqan = 1.4
Hi Manuel, since we uploaded seqan 1.4.x packages to Debian the packages bowtie and tophat failed to build while the build went fine with seqan 1.3. Since I personally have no idea how to fix this and neither bowtie nor tophat developers answered to our request I wonder whether some seqan developers who should know the API very good could possibly create a patch to get the two packages builded again. You can see the build failure log here: bowtie: https://bugs.debian.org/733398 tophat: https://bugs.debian.org/733352 Please also let us know if you have no idea how to fix this. In this case we would use a last fallback and reinject a versioned seqan1.3 package in addition to the latest version of seqan. Any help would be really appreciated Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733352: [Debian-med-packaging] Bug#733352: Bowtie and tophat fail to build with seqan = 1.4
На 25.2.2014 г. 15:30 ч., Andreas Tille написа: since we uploaded seqan 1.4.x packages to Debian the packages bowtie and tophat failed to build while the build went fine with seqan 1.3. Please also let us know if you have no idea how to fix this. In this case we would use a last fallback and reinject a versioned seqan1.3 package in addition to the latest version of seqan. bowtie package uses seqan 1.2 and I made series of patches to build it against seqan 1.3 http://anonscm.debian.org/viewvc/debian-med/trunk/packages/bowtie/trunk/debian/patches/. This weekend I'll work on patching bowtie to work with 1.4. Best regards, Ognyan Kulev -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738961: synaptic: Application is closing at the moment that any key is pressed
Dear Vogt, I run the debugging command and now is perfectly working! I couldn't make it crash. I'm so sorry, how ever is working fine. Also I have make a lot of updates, upgrades, so I'm not sure what happened. Let me know If can do something else for you! best regards On 20 February 2014 08:16, Michael Vogt m...@debian.org wrote: On Fri, Feb 14, 2014 at 10:51:58AM +0100, AndresBurbano wrote: Package: synaptic Version: 0.75.13 Severity: grave Tags: d-i Justification: causes non-serious data loss Thanks for your bugreport. Dear Maintainer, * What led up to the situation? I always develop in Debian, so I got a New PC, then I installed the latest version and when I use the synaptec for install some packages, I realized that every time pressed I key it was automatically closing the app. * What exactly did you do (or not do) that was effective (or ineffective)? I Open the application, Accept the Quick Introduction dialog, I put the cursor in the Quick filter and write the app name. At the first key that I press it get close. I tried several different keys(a, b, z, t..). However if I select the package with the mouse it install normally. [..] Would it be possible to get a gdb backtrace of the situation? For this you will need to open a terminal windows (like gnome-terminal) and run: $ sudo gdb synaptic [enter password] (gdb) run [make synaptic crash] (gdb) bt full and send me the output? Thanks, Michael -- *Andres BURBANO* RD 3D sensing Engineer *7 rue des Vignes, 78220 Virofly, France* *t * +33 130 24 19 28 *f* +33 130 24 70 15 *e* and...@shopline.fr *w* Shopline.fr http://shopline.fr/
Processed: Re: python3-coverage: overwrites file in python3-coverage-dbg
Processing control commands: tags -1 patch Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg Added tag(s) patch. -- 740053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740053 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#740053: python3-coverage: overwrites file in python3-coverage-dbg
Control: tags -1 patch
From the build log I noticed that this is an issue in python3_objcode_versions
definition:
dh [...] --exclude .cpython-3433dm-i386-linux-gnu.so
Attaching a patch that should fix the issue.
--
Dmitry Shachnev--- a/debian/rules
+++ b/debian/rules
@@ -28,7 +28,7 @@
# wildcard will *not* work. So we need to specify the exact substring for
# the Python 3 debug module filenames.
python3_objcode_versions = $(shell \
- printf %s ${PYTHON3_VERSIONS} | sed -e 's/\.//g')
+ printf %s\n ${PYTHON3_VERSIONS} | sed -e 's/\.//g')
DEB_HOST_MULTIARCH = $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
debug_object_exclude += $(foreach ver,${python3_objcode_versions}, \
.cpython-${ver}dm-${DEB_HOST_MULTIARCH}.so)
signature.asc
Description: OpenPGP digital signature
Bug#738569: gpointing-device-settings: Segfaults at startup, cannot get it to work
On Mon, Feb 10, 2014 at 12:18 -0600, Gunnar Wolf wrote:
All the output I get from running this is:
$ gpointing-device-settings
Segmentation fault
Valgrind reports several functions accessing memory that's already
been free'd by gpds_xinput_utils_get_device_info(), and that
function does look buggy:
XDeviceInfo *
gpds_xinput_utils_get_device_info (const gchar *device_name, GError **error)
{
...
if (!strcmp(device_infos[i].name, device_name)) {
XFreeDeviceList(device_infos);
return device_infos[i];
}
...
It works without segfaulting for me, but I think that's down to
chance, and possibly that I have only one pointing device
connected.
I'm wondering if this package should simply be dropped, and will
create another bug to discuss that.
Steve
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736392: octave-plplot: FTBFS with Octave 3.8
Am 25.02.2014 12:08, schrieb Matthias Klose: trying to fix this in Ubuntu trusty (14.04), ... - applied the octave patch in swig2.0 (2.0.11-1ubuntu2) - plplot still fails to build, apparently with the very same error messages. https://launchpad.net/ubuntu/+source/plplot/5.9.9-5ubuntu8 Is there anything additional needed? with a quickly updated 5.10.0, I don't see the build failure anymore, however the octave tests hang ... did work around it, and built some test packages at: https://launchpad.net/~doko/+archive/toolchain/+sourcepub/3940349/+listing-archive-extra tracking issues at https://bugs.launchpad.net/ubuntu/+source/plplot/+bug/1284689 could you point me at the changes required for 5.9.9 to build using octave-3.8? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: merging 734523 740064
Processing commands for cont...@bugs.debian.org: merge 734523 740064 Bug #734523 [dhelp] dhelp: Error while building the HTML tree Bug #740064 [dhelp] dhelp: Weekly cron job always fails. Merged 734523 740064 thanks Stopping processing here. Please contact me if you need assistance. -- 734523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734523 740064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740064 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#740086: python3-crypto: Ships files which are also present in python3-crypto-dbg
Package: python3-crypto Version: 2.6.1-3 Severity: serious Justification: uninstallable on arm archs Dear Maintainer, Currently python3-crypto ships debug extension files on arm*, which makes it uninstallable together with python3-crypto-dbg. See e.g.: https://packages.debian.org/sid/armhf/python3-crypto/filelist The *.*[!d]m*.so wildcard used in python3-crypto.install file is unreliable. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
Cyril Brulebois k...@debian.org (2014-02-13): [ TL;DR: d-i FTBFS on sparc, what do we do now? ] @Kurt: did anything change on the buildd setup side? Both lebrun and spontini got that FTBFS, while that wasn't the case before: https://buildd.debian.org/status/logs.php?pkg=debian-installerarch=sparc Ping? Failing a short resolution, I'm tempted to pretend sparc isn't an issue, and maybe ask for a migration to testing + dak copy-installer. @debian-release: would that sound reasonable? Ping? @ftpmasters: I'm not sure an out-of-date build is going to be OK on the dak side. What do you think? Ping? Mraw, KiBi. signature.asc Description: Digital signature
Bug#734768: marked as done (libopenni-sensor-pointclouds0: modifies conffiles (policy 10.7.3): /etc/openni/modules.xml)
Your message dated Tue, 25 Feb 2014 17:04:23 +
with message-id e1wilqd-0006ay...@franck.debian.org
and subject line Bug#734768: fixed in openni 1.5.4.0-7
has caused the Debian Bug report #734768,
regarding libopenni-sensor-pointclouds0: modifies conffiles (policy 10.7.3):
/etc/openni/modules.xml
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.)
--
734768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libopenni-sensor-pointclouds0,libopenni-sensor-primesense0
Version: 5.1.0.41.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
10.7.3: [...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time).
Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).
Further in 10.7.3: [...] must not ask unnecessary questions
(particularly during upgrades) [...]
If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also http://wiki.debian.org/DpkgConffileHandling
In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.
debsums reports modification of the following files,
from the attached log (scroll to the bottom...):
/etc/openni/modules.xml
If that file serves as some kind of module registry, it should be
placed in /var instead and not be shipped at all but managed (created,
updated, removed) by maintainer scripts only.
cheers,
Andreas
libopenni-sensor-pointclouds0_5.1.0.41.1-1.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: openni
Source-Version: 1.5.4.0-7
We believe that the bug you reported is fixed in the latest version of
openni, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 734...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hans-Christoph Steiner h...@eds.org (supplier of updated openni package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Feb 2014 11:29:08 -0500
Source: openni
Binary: libopenni0 libopenni-java openni-utils libopenni-dev openni-doc
Architecture: source amd64 all
Version: 1.5.4.0-7
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Hans-Christoph Steiner h...@eds.org
Description:
libopenni-dev - headers for OpenNI 'Natural Interaction' frameworks
libopenni-java - Java framework for sensor-based 'Natural Interaction'
libopenni0 - framework for sensor-based 'Natural Interaction'
openni-doc - developer documentation for OpenNI frameworks
openni-utils - debug and test utilities OpenNI framework
Closes: 734768 734894
Changes:
openni (1.5.4.0-7) unstable; urgency=low
.
[ Jochen Sprickerhof ]
* Add libopenni-sensor-pointclouds0 as an alternative
* Remove -j from make flags (fixes bug on arm)
* Move {licenses,modules}.xml to /var/lib/ni/ (Closes: #734768, #734894)
Checksums-Sha1:
d6649383e9a0702e587114fdab651301596ec43f 2401 openni_1.5.4.0-7.dsc
cf06b2f9c03937ce1e764606c7757fc34b4fcdf7 643520 openni_1.5.4.0-7.debian.tar.xz
d1b48a7af7063d4c6d5032adb8fa00836bee812a 283726 libopenni0_1.5.4.0-7_amd64.deb
0906eaea5e6e35ecfb9b8690c6c52f37594f6eb8 144222
Bug#734894: marked as done (libopenni-sensor-primesense0: modifies conffiles (policy 10.7.3): /etc/openni/modules.xml)
Your message dated Tue, 25 Feb 2014 17:04:23 +
with message-id e1wilqd-0006ae...@franck.debian.org
and subject line Bug#734894: fixed in openni 1.5.4.0-7
has caused the Debian Bug report #734894,
regarding libopenni-sensor-primesense0: modifies conffiles (policy 10.7.3):
/etc/openni/modules.xml
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.)
--
734894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libopenni-sensor-pointclouds0,libopenni-sensor-primesense0
Version: 5.1.0.41.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
10.7.3: [...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time).
Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).
Further in 10.7.3: [...] must not ask unnecessary questions
(particularly during upgrades) [...]
If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also http://wiki.debian.org/DpkgConffileHandling
In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.
debsums reports modification of the following files,
from the attached log (scroll to the bottom...):
/etc/openni/modules.xml
If that file serves as some kind of module registry, it should be
placed in /var instead and not be shipped at all but managed (created,
updated, removed) by maintainer scripts only.
cheers,
Andreas
libopenni-sensor-pointclouds0_5.1.0.41.1-1.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: openni
Source-Version: 1.5.4.0-7
We believe that the bug you reported is fixed in the latest version of
openni, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 734...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hans-Christoph Steiner h...@eds.org (supplier of updated openni package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Feb 2014 11:29:08 -0500
Source: openni
Binary: libopenni0 libopenni-java openni-utils libopenni-dev openni-doc
Architecture: source amd64 all
Version: 1.5.4.0-7
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Hans-Christoph Steiner h...@eds.org
Description:
libopenni-dev - headers for OpenNI 'Natural Interaction' frameworks
libopenni-java - Java framework for sensor-based 'Natural Interaction'
libopenni0 - framework for sensor-based 'Natural Interaction'
openni-doc - developer documentation for OpenNI frameworks
openni-utils - debug and test utilities OpenNI framework
Closes: 734768 734894
Changes:
openni (1.5.4.0-7) unstable; urgency=low
.
[ Jochen Sprickerhof ]
* Add libopenni-sensor-pointclouds0 as an alternative
* Remove -j from make flags (fixes bug on arm)
* Move {licenses,modules}.xml to /var/lib/ni/ (Closes: #734768, #734894)
Checksums-Sha1:
d6649383e9a0702e587114fdab651301596ec43f 2401 openni_1.5.4.0-7.dsc
cf06b2f9c03937ce1e764606c7757fc34b4fcdf7 643520 openni_1.5.4.0-7.debian.tar.xz
d1b48a7af7063d4c6d5032adb8fa00836bee812a 283726 libopenni0_1.5.4.0-7_amd64.deb
0906eaea5e6e35ecfb9b8690c6c52f37594f6eb8 144222
Bug#740097: nvidia-legacy-304xx-kernel-source: Module can not be loaded for Linux 3.13
Package: nvidia-legacy-304xx-kernel-source Version: 304.117-1 Severity: grave Justification: renders package unusable Upgrade to linux-image-3.13-1-amd64 made the nvidia module build fine by DKMS, but loading failes with the dmesg entry: kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0) Using linux-image-3.12-1-amd64 however works. -- Package-specific info: uname -a: Linux openmoko 3.12-1-amd64 #1 SMP Debian 3.12.9-1 (2014-02-01) x86_64 GNU/Linux /proc/version: Linux version 3.12-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-14) ) #1 SMP Debian 3.12.9-1 (2014-02-01) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 GCC version: gcc version 4.8.2 (Debian 4.8.2-16) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300] [10de:01d7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3839] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at c900 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at d000 (64-bit, prefetchable) [size=256M] Region 3: Memory at ca00 (64-bit, non-prefetchable) [size=16M] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: nvidia dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.336114] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.336114] vgaarb: loaded [0.336114] vgaarb: bridge control possible :01:00.0 [1.002380] fb0: VESA VGA frame buffer device [1.003103] Linux agpgart interface v0.103 [9.594070] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [9.695734] nvidia: module license 'NVIDIA' taints kernel. [9.739730] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=none [9.749182] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 [ 92.871990] NVRM: Your system is not currently configured to drive a VGA console [ 92.872050] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver [ 92.872057] NVRM: requires the use of a text-mode VGA console. Use of other console [ 92.872062] NVRM: drivers including, but not limited to, vesafb, may result in [ 92.872067] NVRM: corruption and stability problems, and is not supported. OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Feb 25 18:02 /etc/alternatives/glx - /usr/lib/nvidia lrwxrwxrwx 1 root root 48 Jun 26 2013 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu - /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 48 Jun 26 2013 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu - /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 41 Feb 25 18:02 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 41 Feb 25 18:02 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Feb 25 18:02 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Feb 25 18:02 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 49 Feb 25 18:02 /etc/alternatives/glx--libXvMCNVIDIA.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 51 Feb 25 18:02 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 57 Feb 25 18:02 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 59 Feb 25 18:02 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 49 Feb 25 18:02 /etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 51 Feb 25 18:02 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Feb 25 18:02 /etc/alternatives/glx--linux-libglx.so - /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Feb 25 18:02 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -
Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
On Thu, Feb 13, 2014 at 04:38:36PM +0300, Cyril Brulebois wrote: [ TL;DR: d-i FTBFS on sparc, what do we do now? ] Thomas Schmitt scdbac...@gmx.net (2013-12-10): Cyril Brulebois wrote: genisoimage: Error: './tmp/miniiso/cd_tree/boot/.' and './tmp/miniiso/cd_tree/boot/..' have the same ISO9660 name ''. [...] Probably some FS-dependent fun? Anyone would have a clue about it? Looks like an internal error of genisoimage. '.' should be mapped to a 0x00-byte in ECMA-119, '..' to 0x01. See ECMA-119, 6.8.2.2 Identification of directories. These names are reserved for that purpose. Any other colliding ECMA-119 names should be handled by mangling. Thanks, Thomas. @Kurt: did anything change on the buildd setup side? Both lebrun and spontini got that FTBFS, while that wasn't the case before: https://buildd.debian.org/status/logs.php?pkg=debian-installerarch=sparc Nothing changed recently. They've been using tar based chroots for at least 6 months I think. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740047: [Pkg-libvirt-maintainers] Bug#740047: virt-manager: lost all connections on upgrade to experimental
Hi Paul, On Tue, Feb 25, 2014 at 03:11:26PM +0800, Paul Wise wrote: On Tue, 2014-02-25 at 14:57 +0800, Paul Wise wrote: When I upgraded virt-manager from unstable to experimental, virt-manager forgot all the connection details I had stored. When I downgraded back to the version in unstable the connections reappeared again. This is triggered by the switch from gconf to gsettings. Upstream isn't shipping a .convert that maps the former to the later (see gsettings-data-convert). I'll try to find the time to stitch this together but please don't hold your breath. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
On 2014-02-25 17:56, Cyril Brulebois wrote: Cyril Brulebois k...@debian.org (2014-02-13): [...] Failing a short resolution, I'm tempted to pretend sparc isn't an issue, and maybe ask for a migration to testing + dak copy-installer. @debian-release: would that sound reasonable? Ping? [...] Mraw, KiBi. To my knowledge, there has been no visible attempt to keep sparc alive in testing and, indeed, no sparc porters objecting to this suggestion. Based on that, I would say it sounds entirely reasonable to ignore sparc. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738432: thin: looks for vendor_ruby multiarch libs in wrong location
Control: reassign -1 thin 1.3.1-4 Control: merge -1 737032 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740106: libraw: FTBFS on 32-bit platforms: symbols not quite as expected
Source: libraw Version: 0.15.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of libraw on 32-bit platforms such as i386 have been failing, because it winds up defining slightly different symbols than on 64-bit platforms, even with the (c++) construct; see, for instance, https://buildd.debian.org/status/fetch.php?pkg=librawarch=i386ver=0.16.0-1stamp=1393330466 Most, if not all, of the discrepancies appear to stem from the fact that size_t is (presumably for historical reasons) formally unsigned int rather than unsigned long on 32-bit platforms; although the types are de facto equivalent, C++ compilers treat them as distinct and mangle them differently. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): thin: looks for vendor_ruby multiarch libs in wrong location
Processing control commands:
reassign -1 thin 1.3.1-4
Bug #738432 [src:ruby-vegas] ruby-vegas: FTBFS: ERROR: Test ruby2.0 failed:
LoadError: cannot load such file --
/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser
Bug reassigned from package 'src:ruby-vegas' to 'thin'.
No longer marked as found in versions ruby-vegas/0.1.11-2.
Ignoring request to alter fixed versions of bug #738432 to the same values
previously set
Bug #738432 [thin] ruby-vegas: FTBFS: ERROR: Test ruby2.0 failed: LoadError:
cannot load such file --
/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser
Marked as found in versions thin/1.3.1-4.
merge -1 737032
Bug #738432 [thin] ruby-vegas: FTBFS: ERROR: Test ruby2.0 failed: LoadError:
cannot load such file --
/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser
Unable to merge bugs because:
severity of #737032 is 'important' not 'serious'
Failed to merge 738432: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1dd02f0)',
'requester', 'David Suárez david.sephi...@gmail.com', 'request_addr',
'738432-sub...@bugs.debian.org', 'request_msgid',
'1853993.M4TOJ1GTX6@sephirot', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', 'merge -1 737032',
'clonebugs', 'HASH(0x1de7a30)', 'limit', 'HASH(0x1de7c58)',
'common_control_options', 'ARRAY(0x1de7d30)', 'errors', ...) called at
/usr/lib/debbugs/process line 1039
--
737032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737032
738432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 739589 to multiple security flaws in migration stream processing
Processing commands for cont...@bugs.debian.org: retitle 739589 multiple security flaws in migration stream processing Bug #739589 [qemu] qemu: Multiple security issues Changed Bug title to 'multiple security flaws in migration stream processing' from 'qemu: Multiple security issues' thanks Stopping processing here. Please contact me if you need assistance. -- 739589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739589 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: tag 740086 + pending Bug #740086 [python3-crypto] python3-crypto: Ships files which are also present in python3-crypto-dbg Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 740086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740086 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#738432: thin: looks for vendor_ruby multiarch libs in wrong location
Control: severity 737032 serious Control: merge -1 737032 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: thin: looks for vendor_ruby multiarch libs in wrong location
Processing control commands: severity 737032 serious Bug #737032 [thin] thin: looks for vendor_ruby multiarch libs in wrong location Severity set to 'serious' from 'important' merge -1 737032 Bug #738432 [thin] ruby-vegas: FTBFS: ERROR: Test ruby2.0 failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser Bug #737032 [thin] thin: looks for vendor_ruby multiarch libs in wrong location Added tag(s) sid and jessie. Merged 737032 738432 -- 737032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737032 738432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#734268: linux-image-3.12-1-amd64: NFS-related crashes
Processing control commands: severity -1 critical Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Severity set to 'critical' from 'important' found -1 linux/3.12.6-2 Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Marked as found in versions linux/3.12.6-2. found -1 linux/3.13.4-1 Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Marked as found in versions linux/3.13.4-1. fixed -1 linux/3.11.10-1 Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Marked as fixed in versions linux/3.11.10-1. -- 734268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734268 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#738378: marked as done (freecontact: FTBFS: configure: error: Could not find a version of the library!)
Your message dated Tue, 25 Feb 2014 21:22:05 + with message-id e1wips1-0002c1...@franck.debian.org and subject line Bug#738378: fixed in freecontact 1.0.21-3 has caused the Debian Bug report #738378, regarding freecontact: FTBFS: configure: error: Could not find a version of the library! 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.) -- 738378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: freecontact Version: 1.0.21-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140208 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate configure: -O3 enables: -falign-functions -falign-jumps -falign-labels -falign-loops -fcaller-saves -fcombine-stack-adjustments -fcompare-elim -fcprop-registers -fcrossjumping -fcse-follow-jumps -fdefer-pop -fdevirtualize -fexpensive-optimizations -fforward-propagate -fgcse -fgcse-after-reload -fguess-branch-probability -fhoist-adjacent-loads -fif-conversion -fif-conversion2 -finline-functions -finline-functions-called-once -finline-small-functions -fipa-cp -fipa-cp-clone -fipa-profile -fipa-pure-const -fipa-reference -fipa-sra -fmerge-constants -foptimize-register-move -foptimize-sibling-calls -foptimize-strlen -fpeephole2 -fpredictive-commoning -fregmove -freorder-blocks -freorder-functions -frerun-cse-after-loop -fschedule-insns2 -fshrink-wrap -fsplit-wide-types -fstrict-aliasing -fthread-jumps -ftree-bit-ccp -ftree-builtin-call-dce -ftree-ccp -ftree-ch -ftree-copy-prop -ftree-copyrename -ftree-dce -ftree-dominator-opts -ftree-dse -ftree-fre -ftree-loop-distribute-patterns -ftree-partial-pre -ftree-pre -ftree-sink -ftree-slsr -ftree-sra -ftree-switch-conversion -ftree-tail-merge -ftree-ter -ftree-vectorize -ftree-vrp -funswitch-loops -fvect-cost-model checking for boostlib = 1.20.0... yes checking whether the Boost::Program_Options library is available... yes configure: error: Could not find a version of the library! The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/02/08/freecontact_1.0.21-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: freecontact Source-Version: 1.0.21-3 We believe that the bug you reported is fixed in the latest version of freecontact, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 738...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Kajan lka...@debian.org (supplier of updated freecontact package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Feb 2014 21:37:33 +0100 Source: freecontact Binary: freecontact libfreecontact0 libfreecontact0-dev libfreecontact0-dbg libfreecontact-doc Architecture: source amd64 all Version: 1.0.21-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Laszlo Kajan lka...@debian.org Description: freecontact - fast protein contact predictor libfreecontact-doc - documentation for libfreecontact libfreecontact0 - fast protein contact predictor library libfreecontact0-dbg - debugging symbols for libfreecontact libfreecontact0-dev - fast protein contact predictor library - development files Closes: 738378 Changes: freecontact (1.0.21-3) unstable; urgency=medium . [ Andreas Tille ] * debian/control: - cme fix dpkg-control - Priority: optional . [ Laszlo Kajan ] * Imported changes of 1.0.21-1ubuntu1: pass --with-boost-libdir to
Bug#738413: marked as done (ubuntu-dev-tools: FTBFS: Tests failed)
Your message dated Tue, 25 Feb 2014 21:29:28 +
with message-id e1wipza-0004av...@franck.debian.org
and subject line Bug#738413: fixed in ubuntu-dev-tools 0.152+nmu1
has caused the Debian Bug report #738413,
regarding ubuntu-dev-tools: FTBFS: Tests failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
738413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ubuntu-dev-tools
Version: 0.152
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
==
FAIL: test_good (ubuntutools.test.test_archive.DscVerificationTestCase)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mox.py, line 1870, in new_method
func(self, *args, **kwargs)
File /«PKGBUILDDIR»/ubuntutools/test/test_archive.py, line 60, in
test_good
'test-data/example_1.0-1.debian.tar.gz'))
AssertionError: False is not true
==
FAIL: test_md5 (ubuntutools.test.test_archive.DscVerificationTestCase)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mox.py, line 1870, in new_method
func(self, *args, **kwargs)
File /«PKGBUILDDIR»/ubuntutools/test/test_archive.py, line 84, in test_md5
self.test_good()
File /usr/lib/python2.7/dist-packages/mox.py, line 1870, in new_method
func(self, *args, **kwargs)
File /«PKGBUILDDIR»/ubuntutools/test/test_archive.py, line 60, in
test_good
'test-data/example_1.0-1.debian.tar.gz'))
AssertionError: False is not true
==
FAIL: test_sha1 (ubuntutools.test.test_archive.DscVerificationTestCase)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mox.py, line 1870, in new_method
func(self, *args, **kwargs)
File /«PKGBUILDDIR»/ubuntutools/test/test_archive.py, line 78, in
test_sha1
self.test_good()
File /usr/lib/python2.7/dist-packages/mox.py, line 1870, in new_method
func(self, *args, **kwargs)
File /«PKGBUILDDIR»/ubuntutools/test/test_archive.py, line 60, in
test_good
'test-data/example_1.0-1.debian.tar.gz'))
AssertionError: False is not true
==
FAIL: test_mirrors (ubuntutools.test.test_archive.LocalSourcePackageTestCase)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mox.py, line 1870, in new_method
func(self, *args, **kwargs)
File /«PKGBUILDDIR»/ubuntutools/test/test_archive.py, line 229, in
test_mirrors
pkg.pull()
File /«PKGBUILDDIR»/ubuntutools/archive.py, line 361, in pull
if self._download_file(url, name):
File /«PKGBUILDDIR»/ubuntutools/archive.py, line 324, in _download_file
in_ = self.url_opener.open(url)
File /usr/lib/python2.7/dist-packages/mox.py, line 985, in __call__
expected_method = self._VerifyMethodCall()
File /usr/lib/python2.7/dist-packages/mox.py, line 1043, in
_VerifyMethodCall
raise UnexpectedMethodCallError(self, expected)
UnexpectedMethodCallError: Unexpected method call. unexpected:- expected:+
-
OpenerDirector.open(u'http://mirror/pool/main/e/example/example_1.0-1.debian.tar.xz')
- None
? -
^
+
OpenerDirector.open('http://mirror/pool/main/e/example/example_1.0-1.debian.tar.gz')
- None
?
^
==
FAIL: test_pull (ubuntutools.test.test_archive.LocalSourcePackageTestCase)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mox.py, line 1870, in new_method
func(self, *args, **kwargs)
File /«PKGBUILDDIR»/ubuntutools/test/test_archive.py, line 205, in
test_pull
pkg.pull()
File
Bug#740111: icedtea-netx: NullPointerException in SwingUtilities.appContextGet
Package: icedtea-netx Version: 1.3.2-1 Severity: serious Tring to understand why the KGS Go client at http://files.gokgs.com/javaBin/cgoban.jnlp would not start: * default javaws (using openjdk-6) even explodes when passed no argument: $ /usr/lib/jvm/java-6-openjdk-amd64/bin/javaws Exception in thread main java.lang.NullPointerException at javax.swing.SwingUtilities.appContextGet(SwingUtilities.java:1859) at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1829) at javax.swing.JWindow.init(JWindow.java:185) at javax.swing.JWindow.init(JWindow.java:137) at net.sourceforge.jnlp.runtime.JNLPSecurityManager.init(JNLPSecurityManager.java:121) at net.sourceforge.jnlp.runtime.JNLPRuntime.initialize(JNLPRuntime.java:231) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:181) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:51) at java.security.AccessController.doPrivileged(Native Method) at net.sourceforge.jnlp.runtime.Boot.main(Boot.java:172) * using openjdk-7, the same call produces a usage message, but when launching against cgoban.jnlp the same NPE occurs, so I guess it is not specific to this particular app (hence the severity): $ /usr/lib/jvm/java-7-openjdk-amd64/bin/javaws /tmp/cgoban.jnlp Exception in thread main java.lang.NullPointerException at javax.swing.SwingUtilities.appContextGet(SwingUtilities.java:1859) at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1829) at javax.swing.JWindow.init(JWindow.java:185) at javax.swing.JWindow.init(JWindow.java:137) at net.sourceforge.jnlp.runtime.JNLPSecurityManager.init(JNLPSecurityManager.java:121) at net.sourceforge.jnlp.runtime.JNLPRuntime.initialize(JNLPRuntime.java:231) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:181) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:51) at java.security.AccessController.doPrivileged(Native Method) at net.sourceforge.jnlp.runtime.Boot.main(Boot.java:172) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.3.2-1 ii openjdk-6-jre6b30-1.13.1-1 ii openjdk-7-jre7u21-2.3.9-5 icedtea-netx recommends no packages. icedtea-netx 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#740111: Fixed in unstable
notfound 740111 1.4.2-1 thanks The problem does not happen with 1.4.2-1, currently in unstable. Works well with both openjdk 6 and 7. Sidenote: trying to install 1.4-3~deb7u2, it wanted to deinstall icedtea-6-plugin, so I did not test that one after all. Isn't that another bug ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Fixed in unstable
Processing commands for cont...@bugs.debian.org: notfound 740111 1.4.2-1 Bug #740111 [icedtea-netx] icedtea-netx: NullPointerException in SwingUtilities.appContextGet Ignoring request to alter found versions of bug #740111 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 740111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740111 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#740053: python3-coverage: overwrites file in python3-coverage-dbg
package python3-coverage notfound 740053 python3-coverage/3.7+dfsg.1-4 found 740053 python3-coverage/3.7+dfsg.1-4+b1 tags 740053 + confirmed thanks On 25-Feb-2014, Dmitry Shachnev wrote: Today’s update of python3-coverage (Which is “3.7+dfsg.1-4+b1”; I'm updating the bug report accordingly.) Looks like both python3-coverage and python3-coverage-dbg ship that file (tracer.cpython-34dm-$MULTIARCH.so), while it should be only present in python3-coverage-dbg. The same applies to tracer.cpython-33dm-$MULTIARCH.so. Thanks for this report. -- \ “Pinky, are you pondering what I'm pondering?” “I think so, | `\ Brain, but can the Gummi Worms really live in peace with the | _o__) Marshmallow Chicks?” —_Pinky and The Brain_ | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Processed: Re: Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg
Processing commands for cont...@bugs.debian.org: package python3-coverage Limiting to bugs with field 'package' containing at least one of 'python3-coverage' Limit currently set to 'package':'python3-coverage' notfound 740053 python3-coverage/3.7+dfsg.1-4 Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg The source python3-coverage and version 3.7+dfsg.1-4 do not appear to match any binary packages Ignoring request to alter found versions of bug #740053 to the same values previously set found 740053 python3-coverage/3.7+dfsg.1-4+b1 Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg The source python3-coverage and version 3.7+dfsg.1-4+b1 do not appear to match any binary packages Marked as found in versions python3-coverage/3.7+dfsg.1-4+b1. tags 740053 + confirmed Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 740053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740053 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 (with 1 errors): Re: Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg
Processing commands for cont...@bugs.debian.org: package python-coverage Limiting to bugs with field 'package' containing at least one of 'python-coverage' Limit currently set to 'package':'python-coverage' notfound 740053 python-coverage/3.7+dfsg.1-4 package: python3-coverage' does not match at least one of python-coverage Failed to remove found on 740053: limit failed for bugs: 740053. package python3-coverage Limiting to bugs with field 'package' containing at least one of 'python3-coverage' Limit currently set to 'package':'python3-coverage' found 740053 python3-coverage/3.7+dfsg.1-4+b1 Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg The source python3-coverage and version 3.7+dfsg.1-4+b1 do not appear to match any binary packages Ignoring request to alter found versions of bug #740053 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 740053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg
Processing commands for cont...@bugs.debian.org: notfound 740053 python-coverage/3.7+dfsg.1-4 Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg No longer marked as found in versions python-coverage/3.7+dfsg.1-4. found 740053 python3-coverage/3.7+dfsg.1-4+b1 Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg The source python3-coverage and version 3.7+dfsg.1-4+b1 do not appear to match any binary packages Ignoring request to alter found versions of bug #740053 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 740053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740053 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#740117: haveged: spinning
Package: haveged Version: 1.7c-1 Severity: grave Justification: renders package unusable Haveged is just spinning and not comming anywhere :( Been watching it for hours doing that. Uses one CPU at 100%. Upstream version 1.9.0 promisses improvements, although I have no idea if those address the problem I'm reporting. Strace shows it stuck in a select loop: 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages haveged depends on: ii init-system-helpers 1.17 ii libc62.18-3 ii libhavege1 1.7c-1 ii lsb-base 4.1+Debian12 haveged recommends no packages. haveged suggests no packages. -- Configuration Files: /etc/default/haveged changed: DAEMON_ARGS=-w 4096 -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740111: Fixed in unstable
fixed 740111 1.4.2-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Fixed in unstable
Processing commands for cont...@bugs.debian.org: fixed 740111 1.4.2-1 Bug #740111 [icedtea-netx] icedtea-netx: NullPointerException in SwingUtilities.appContextGet Marked as fixed in versions icedtea-web/1.4.2-1. thanks Stopping processing here. Please contact me if you need assistance. -- 740111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740111 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#740086: marked as done (python3-crypto: Ships files which are also present in python3-crypto-dbg)
Your message dated Tue, 25 Feb 2014 22:33:38 +
with message-id e1wiqzg-0004li...@franck.debian.org
and subject line Bug#740086: fixed in python-crypto 2.6.1-4
has caused the Debian Bug report #740086,
regarding python3-crypto: Ships files which are also present in
python3-crypto-dbg
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.)
--
740086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python3-crypto
Version: 2.6.1-3
Severity: serious
Justification: uninstallable on arm archs
Dear Maintainer,
Currently python3-crypto ships debug extension files on arm*, which makes
it uninstallable together with python3-crypto-dbg. See e.g.:
https://packages.debian.org/sid/armhf/python3-crypto/filelist
The *.*[!d]m*.so wildcard used in python3-crypto.install file is unreliable.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
---End Message---
---BeginMessage---
Source: python-crypto
Source-Version: 2.6.1-4
We believe that the bug you reported is fixed in the latest version of
python-crypto, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 740...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher sramac...@debian.org (supplier of updated python-crypto
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Feb 2014 23:16:33 +0100
Source: python-crypto
Binary: python-crypto python-crypto-dbg python3-crypto python3-crypto-dbg
python-crypto-doc
Architecture: source amd64 all
Version: 2.6.1-4
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Ramacher sramac...@debian.org
Changed-By: Sebastian Ramacher sramac...@debian.org
Description:
python-crypto - cryptographic algorithms and protocols for Python
python-crypto-dbg - cryptographic algorithms and protocols for Python (debug
extensio
python-crypto-doc - cryptographic algorithms and protocols for Python
(documentation)
python3-crypto - cryptographic algorithms and protocols for Python 3
python3-crypto-dbg - cryptographic algorithms and protocols for Python 3
(debug extens
Closes: 740086
Changes:
python-crypto (2.6.1-4) unstable; urgency=medium
.
* debian/python3-crypto{,-dbg}.install: Fix wildcards to not include debug
extensions with arm in the name in python3-crypto. (Closes: #740086)
- Extensions built for Python 3.2 are no longer handled, so this requires
python3-all-dev = 3.3.2-5.
* Use pybuild buildsystem:
- debian/control: Add dh-python to Build-Depends.
- debian/rules:
+ Pass --buildsystem=pybuild to dh.
+ Remove dh_auto_clean, dh_auto_build and dh_auto_install overrides.
+ Adapt dh_auto_test override for pybuild.
* Build documention in -indep targets:
- debian/control: Move python-docutils and python-epydoc to
Build-Depends-Indep.
- debian/rules: Build documentation in override_dh_auto_build-indep.
* debian/patches/deprecated-test-methods.patch: Replace deprecated unittest
methods. Python 3.3's and 3.4's 2to3 generate different files otherwise.
Checksums-Sha1:
c2a0f9e0a5ce6665c038a2a60eb77e8fdf664a47 2425 python-crypto_2.6.1-4.dsc
cc5c63686a39254a9d74e7de5d420c0ba3619f32 21008
python-crypto_2.6.1-4.debian.tar.xz
97e4f615791fe4e0ed69001b86e4bde6f6b1c753 255282 python-crypto_2.6.1-4_amd64.deb
3e8dad20a4bc76a3c8ea6a1512375efddf49ac27 577518
python-crypto-dbg_2.6.1-4_amd64.deb
c54aecc824386380602d8fc195087b124756254c 257356
python3-crypto_2.6.1-4_amd64.deb
6d255acec1a412af4315b5b6d3807cf1ac059bfc 1028298
python3-crypto-dbg_2.6.1-4_amd64.deb
e6ba0314e8f508d756e800b16d7f144beca2d0dc 87850
python-crypto-doc_2.6.1-4_all.deb
Checksums-Sha256:
a64f70a31c6245500629d0e59e065d8b75803fdd93d67f2de7700fc7c9ede674 2425
python-crypto_2.6.1-4.dsc
aa375bb3454a31472e8ae55ce061ee78ceaaf847bf8c5c04211c0ff170013dad 21008
python-crypto_2.6.1-4.debian.tar.xz
996a63ded2cccbc3b9036eb1eabaf1feb6cbeede5c9e8378de04904fbc632165 255282
python-crypto_2.6.1-4_amd64.deb
f3b615fc03cd8866a3eed788ce5c0f7deec93ad2cfa175e94394ef16af3313fb 577518
Processed: severity of 721721 is serious
Processing commands for cont...@bugs.debian.org: severity 721721 serious Bug #721721 [libpostgis-java] libpostgis-java: Installs incorrect symlink Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 721721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721721 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: merging 735865 735867 735868 735863 735860
Processing commands for cont...@bugs.debian.org: merge 735865 735867 735868 735863 735860 Bug #735865 [ruby-activesupport-3.2] ruby-rabl-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735860 [ruby-activesupport-3.2] ruby-rspec-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735863 [ruby-activesupport-3.2] ruby-markerb: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735867 [ruby-activesupport-3.2] ruby-foreigner: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735868 [ruby-activesupport-3.2] ruby-roxml: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Merged 735860 735863 735865 735867 735868 thanks Stopping processing here. Please contact me if you need assistance. -- 735860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735860 735863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735863 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 735867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735867 735868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 735865 to ruby-activesupport-3.2, reassign 735867 to ruby-activesupport-3.2 ...
Processing commands for cont...@bugs.debian.org: reassign 735865 ruby-activesupport-3.2 Bug #735865 [src:ruby-rabl-rails] ruby-rabl-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug reassigned from package 'src:ruby-rabl-rails' to 'ruby-activesupport-3.2'. No longer marked as found in versions ruby-rabl-rails/0.3.2-1. Ignoring request to alter fixed versions of bug #735865 to the same values previously set reassign 735867 ruby-activesupport-3.2 Bug #735867 [src:ruby-foreigner] ruby-foreigner: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug reassigned from package 'src:ruby-foreigner' to 'ruby-activesupport-3.2'. No longer marked as found in versions ruby-foreigner/1.4.1-1. Ignoring request to alter fixed versions of bug #735867 to the same values previously set reassign 735868 ruby-activesupport-3.2 Bug #735868 [src:ruby-roxml] ruby-roxml: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug reassigned from package 'src:ruby-roxml' to 'ruby-activesupport-3.2'. No longer marked as found in versions ruby-roxml/3.3.1-2. Ignoring request to alter fixed versions of bug #735868 to the same values previously set reassign 735863 ruby-activesupport-3.2 Bug #735863 [src:ruby-markerb] ruby-markerb: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug reassigned from package 'src:ruby-markerb' to 'ruby-activesupport-3.2'. No longer marked as found in versions ruby-markerb/1.0.1-1. Ignoring request to alter fixed versions of bug #735863 to the same values previously set reassign 735860 ruby-activesupport-3.2 Bug #735860 [src:ruby-rspec-rails] ruby-rspec-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug reassigned from package 'src:ruby-rspec-rails' to 'ruby-activesupport-3.2'. No longer marked as found in versions ruby-rspec-rails/2.13.2-2. Ignoring request to alter fixed versions of bug #735860 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 735860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735860 735863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735863 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 735867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735867 735868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 735868 to activesupport needs minitest, but does not require it explicitly ...
Processing commands for cont...@bugs.debian.org: retitle 735868 activesupport needs minitest, but does not require it explicitly Bug #735868 [ruby-activesupport-3.2] ruby-roxml: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735860 [ruby-activesupport-3.2] ruby-rspec-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735863 [ruby-activesupport-3.2] ruby-markerb: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735865 [ruby-activesupport-3.2] ruby-rabl-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug #735867 [ruby-activesupport-3.2] ruby-foreigner: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Changed Bug title to 'activesupport needs minitest, but does not require it explicitly' from 'ruby-roxml: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError)' Changed Bug title to 'activesupport needs minitest, but does not require it explicitly' from 'ruby-rspec-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError)' Changed Bug title to 'activesupport needs minitest, but does not require it explicitly' from 'ruby-markerb: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError)' Changed Bug title to 'activesupport needs minitest, but does not require it explicitly' from 'ruby-rabl-rails: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError)' Changed Bug title to 'activesupport needs minitest, but does not require it explicitly' from 'ruby-foreigner: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError)' found 735868 3.2.16-1 Bug #735868 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735860 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735863 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735865 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735867 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Marked as found in versions ruby-activesupport-3.2/3.2.16-1. Marked as found in versions ruby-activesupport-3.2/3.2.16-1. Marked as found in versions ruby-activesupport-3.2/3.2.16-1. Marked as found in versions ruby-activesupport-3.2/3.2.16-1. Marked as found in versions ruby-activesupport-3.2/3.2.16-1. thanks Stopping processing here. Please contact me if you need assistance. -- 735860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735860 735863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735863 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 735867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735867 735868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735868 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#740119: nemo: FTBFS with new gtk+ because of GTK_DISABLE_DEPRECATED
Source: nemo Version: 1.8.4-1 Severity: serious Your package FTBFS on sid since the gtk+3.0 update. That is because you're building with -DGTK_DISABLE_DEPRECATED (plus a few others). That is a bad idea to do in Debian (it is fine if upstream does it during development) because it can cause build failures like this when one of those libraries is updated. Emilio libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\Eel\ -I.. -I.. -pthread -I/usr/include/gtk-3.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libdrm -pthread -I/usr/include/gail-3.0 -I/usr/include/atk-1.0 -I/usr/include/gtk-3.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/libxml2 -I/usr/include/gnome-desktop-3.0 -I/usr/include/gsettings-desktop-schemas -DG_DISABLE_DEPRECATED -DGTK_DISABLE_D EPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DDATADIR=\/usr/share\ -DSOURCE_DATADIR=\../data\ -DGNOMELOCALEDIR=\/usr/share/locale\ -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c eel-glib-extensions.c -fPIC -DPIC -o .libs/eel-glib-extensions.o eel-canvas.c:3331:2: warning: 'gdk_threads_leave' is deprecated (declared at /usr/include/gtk-3.0/gdk/gdkthreads.h:48) [-Wdeprecated-declarations] GDK_THREADS_LEAVE (); ^ eel-editable-label.c: In function 'eel_editable_label_draw_cursor': eel-editable-label.c:1476:4: warning: 'gtk_draw_insertion_cursor' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkstylecontext.h:1140) [-Wdeprecated-declarations] gtk_draw_insertion_cursor (widget, ^ eel-editable-label.c:1488:8: warning: 'gtk_draw_insertion_cursor' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkstylecontext.h:1140) [-Wdeprecated-declarations] gtk_draw_insertion_cursor (widget, cr, ^ eel-editable-label.c: In function 'append_action_signal': eel-editable-label.c:3001:25: warning: initialization makes pointer from integer without a cast [enabled by default] GtkWidget *menuitem = gtk_image_menu_item_new_from_stock (stock_id, NULL); ^ eel-editable-label.c: In function 'popup_position_func': eel-editable-label.c:3043:3: warning: 'gtk_widget_get_requisition' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkwidget.h:788): Use 'gtk_widget_get_preferred_width and gtk_widget_get_preferred_height' instead [-Wdeprecated-declarations] gtk_widget_get_requisition (widget, req); ^ eel-editable-label.c: In function 'popup_targets_received': eel-editable-label.c:3097:55: error: 'GTK_STOCK_CUT' undeclared (first use in this function) append_action_signal (label, label-popup_menu, GTK_STOCK_CUT, cut_clipboard, ^ eel-editable-label.c:3097:55: note: each undeclared identifier is reported only once for each function it appears in eel-editable-label.c:3099:55: error: 'GTK_STOCK_COPY' undeclared (first use in this function) append_action_signal (label, label-popup_menu, GTK_STOCK_COPY, copy_clipboard, ^ eel-editable-label.c:3101:55: error: 'GTK_STOCK_PASTE' undeclared (first use in this function) append_action_signal (label, label-popup_menu, GTK_STOCK_PASTE, paste_clipboard, ^ eel-editable-label.c:3122:7: warning: 'gtk_im_multicontext_append_menuitems' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimmulticontext.h:67) [-Wdeprecated-declarations] gtk_im_multicontext_append_menuitems (GTK_IM_MULTICONTEXT (label-im_context), ^ make[3]: *** [eel-editable-label.lo] Error 1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686181: marked as done (Please allow translation of all debconf templates)
Your message dated Tue, 25 Feb 2014 23:03:19 + with message-id e1wir20-0007py...@franck.debian.org and subject line Bug#686181: fixed in icecast2 2.3.3-2 has caused the Debian Bug report #686181, regarding Please allow translation of all debconf templates 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.) -- 686181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: icecast2 Version: 2.3.2-9 Severity: serious Tags: patch Justification: Policy 3.9.1 Hi, A small typo in one of the templates (missing prepending underscore) prevent one screen to be translated. It would be pointless to fix this without a proper call for translation, so I'm proposing to take care of it on your behalf, starting in two days (or sooner if you ACK this proposal). d-l10n-english is xCC, in case they believe a proper review would worth it (but I doubt it given the “These templates have been reviewed by the debian-l10n-english team” header already present in those files). Regards David -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icecast2 depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.46 ii libc6 2.13-35 ii libcurl3-gnutls7.27.0-1 ii libogg01.3.0-4 ii libspeex1 1.2~rc1-6 ii libtheora0 1.1.1+dfsg.1-3.1 ii libvorbis0a1.3.2-1.3 ii libxml22.8.0+dfsg1-5 ii libxslt1.1 1.1.26-13 icecast2 recommends no packages. Versions of packages icecast2 suggests: pn ices2 none diff -ur icecast2-2.3.2.orig/debian/templates icecast2-2.3.2/debian/templates --- icecast2-2.3.2.orig/debian/templates 2011-12-05 07:42:56.0 -0400 +++ icecast2-2.3.2/debian/templates 2012-08-29 12:07:07.0 -0400 @@ -10,7 +10,7 @@ Template: icecast2/icecast-setup Type: boolean Default: false -Description: Configure Icecast2? +_Description: Configure Icecast2? Choose this option to set up passwords for Icecast2. Until these are configured the server will not be activated. . ---End Message--- ---BeginMessage--- Source: icecast2 Source-Version: 2.3.3-2 We believe that the bug you reported is fixed in the latest version of icecast2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 686...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felipe Sateler fsate...@debian.org (supplier of updated icecast2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Feb 2014 19:53:16 -0300 Source: icecast2 Binary: icecast2 Architecture: source amd64 Version: 2.3.3-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Felipe Sateler fsate...@debian.org Description: icecast2 - streaming media server Closes: 652050 653401 686181 686263 686280 686288 686444 686530 686591 686596 686607 686659 686691 686716 686773 Changes: icecast2 (2.3.3-2) unstable; urgency=low . * Team Upload. . [ Jonas Smedegaard ] * Add DEP3 header to patch 1001. * Remove debian/source/local-options: abort-on-upstream-changes and unapply-patches are default in dpkg-source since 1.16.1. * Drop obsolete NEWS file: Latest news more than 8 years ago. * Modernize CDBS usage: + Re-enable upstream tarball handling and copyright-check. + Drop unused local snippets. + Reorganize CDBS usage in rules file. + Drop obsolete README.cdbs-tweaks. * Extend copyright years for packaging, and add proper licensing header to rules file. * Rewrite copyright file, using DEP5 format. * Bump standards-version to 3.9.3. * Bump autotools to match versions used upstream. * suppress copyright-check of some images. *
Processed: found 735868 in 3.2.16-1
Processing commands for cont...@bugs.debian.org: found 735868 3.2.16-1 Bug #735868 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735860 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735863 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735865 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735867 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Ignoring request to alter found versions of bug #735868 to the same values previously set Ignoring request to alter found versions of bug #735860 to the same values previously set Ignoring request to alter found versions of bug #735863 to the same values previously set Ignoring request to alter found versions of bug #735865 to the same values previously set Ignoring request to alter found versions of bug #735867 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 735860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735860 735863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735863 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 735867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735867 735868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735868 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 735868 in 3.2.16-3+0
Processing commands for cont...@bugs.debian.org: notfound 735868 3.2.16-3+0 Bug #735868 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735860 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735863 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735865 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735867 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Ignoring request to alter found versions of bug #735868 to the same values previously set Ignoring request to alter found versions of bug #735860 to the same values previously set Ignoring request to alter found versions of bug #735863 to the same values previously set Ignoring request to alter found versions of bug #735865 to the same values previously set Ignoring request to alter found versions of bug #735867 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 735860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735860 735863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735863 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 735867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735867 735868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735868 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: fixed 735868 in 3.2.16-3+0
Processing commands for cont...@bugs.debian.org: fixed 735868 3.2.16-3+0 Bug #735868 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735860 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735863 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735865 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735867 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Marked as fixed in versions rails-3.2/3.2.16-3+0. Marked as fixed in versions rails-3.2/3.2.16-3+0. Marked as fixed in versions rails-3.2/3.2.16-3+0. Marked as fixed in versions rails-3.2/3.2.16-3+0. Marked as fixed in versions rails-3.2/3.2.16-3+0. thanks Stopping processing here. Please contact me if you need assistance. -- 735860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735860 735863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735863 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 735867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735867 735868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735868 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#737032: Bug in Debian patch
Control: tags -1 + confirmed This is likely a bug in fix_require_path_for_thin_parser.patch. Haven't looked closely if this can be fixed in a better way (i.e. without hardcoding locations, even though in 2.0 hardcoding would be less bad). -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Processed: Bug in Debian patch
Processing control commands: tags -1 + confirmed Bug #737032 [thin] thin: looks for vendor_ruby multiarch libs in wrong location Bug #738432 [thin] ruby-vegas: FTBFS: ERROR: Test ruby2.0 failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser Added tag(s) confirmed. Added tag(s) confirmed. -- 737032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737032 738432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738432 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#735865: marked as done (activesupport needs minitest, but does not require it explicitly)
Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id 20140225231854.GA6632@spin and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly 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.) -- 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-rabl-rails Version: 0.3.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/test_case.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/test_helper.rb:8:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/base_renderer_test.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:10:in `block (2 levels) in main' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:9:in `each' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:9:in `block in main' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `main' rake aborted! Command failed with status (1): [ruby -Ilib:test -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/**/*_test.rb ] -e:1:in `main' Tasks: TOP = default = test (See full trace by running task with --trace) ERROR: Test ruby1.9.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/ruby-rabl-rails_0.3.2-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--- Hi, rails-3.2 3.2.16-3+0 dropped the patch using minitest. I am therefore closing this bug. Cheers, Cédric---End Message---
Bug#735867: marked as done (activesupport needs minitest, but does not require it explicitly)
Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id 20140225231854.GA6632@spin and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly 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.) -- 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-foreigner Version: 1.4.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/test_case.rb:1:in `top (required)' from /«PKGBUILDDIR»/test/helper.rb:48:in `module:Foreigner' from /«PKGBUILDDIR»/test/helper.rb:47:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/foreigner/schema_dumper_test.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from debian/ruby-tests.rb:2:in `block in main' from debian/ruby-tests.rb:2:in `each' from debian/ruby-tests.rb:2:in `main' ERROR: Test ruby1.9.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/ruby-foreigner_1.4.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--- Hi, rails-3.2 3.2.16-3+0 dropped the patch using minitest. I am therefore closing this bug. Cheers, Cédric---End Message---
Bug#735860: marked as done (activesupport needs minitest, but does not require it explicitly)
Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id 20140225231854.GA6632@spin and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly 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.) -- 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-rspec-rails Version: 2.13.2-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:251:in `block in require' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:236:in `load_dependency' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:251:in `require' from /usr/lib/ruby/vendor_ruby/active_support/test_case.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/action_controller/test_case.rb:366:in `module:ActionController' from /usr/lib/ruby/vendor_ruby/action_controller/test_case.rb:7:in `top (required)' from /«PKGBUILDDIR»/lib/rspec/rails/example/controller_example_group.rb:9:in `module:ControllerExampleGroup' from /«PKGBUILDDIR»/lib/rspec/rails/example/controller_example_group.rb:6:in `module:Rails' from /«PKGBUILDDIR»/lib/rspec/rails/example/controller_example_group.rb:5:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:251:in `block in require' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:236:in `load_dependency' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:251:in `require' from /«PKGBUILDDIR»/lib/rspec/rails/example.rb:2:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:251:in `block in require' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:236:in `load_dependency' from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:251:in `require' from /«PKGBUILDDIR»/lib/rspec/rails.rb:16:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/spec/spec_helper.rb:8:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/spec/rspec/rails/assertion_adapter_spec.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:22:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in autorun' /usr/bin/ruby1.9.1 -S rspec ./spec/rspec/rails/assertion_adapter_spec.rb ./spec/rspec/rails/assertion_delegator_spec.rb ./spec/rspec/rails/configuration_spec.rb ./spec/rspec/rails/deprecations_spec.rb ./spec/rspec/rails/example/controller_example_group_spec.rb ./spec/rspec/rails/example/feature_example_group_spec.rb ./spec/rspec/rails/example/helper_example_group_spec.rb ./spec/rspec/rails/example/mailer_example_group_spec.rb ./spec/rspec/rails/example/model_example_group_spec.rb ./spec/rspec/rails/example/request_example_group_spec.rb ./spec/rspec/rails/example/routing_example_group_spec.rb ./spec/rspec/rails/example/view_example_group_spec.rb
Bug#735863: marked as done (activesupport needs minitest, but does not require it explicitly)
Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id 20140225231854.GA6632@spin and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly 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.) -- 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-markerb Version: 1.0.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/test_case.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/test_helper.rb:6:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/generator_test.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in main' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `main' rake aborted! Command failed with status (1): [ruby -Ilib:test -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/generator_test.rb test/markerb_test.rb ] -e:1:in `main' Tasks: TOP = default = test (See full trace by running task with --trace) ERROR: Test ruby1.9.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/ruby-markerb_1.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 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--- Hi, rails-3.2 3.2.16-3+0 dropped the patch using minitest. I am therefore closing this bug. Cheers, Cédric---End Message---
Bug#735868: marked as done (activesupport needs minitest, but does not require it explicitly)
Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id 20140225231854.GA6632@spin and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly 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.) -- 735865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-roxml Version: 3.3.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/test_case.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/test_helper.rb:1:in `top (required)' from /«PKGBUILDDIR»/test/unit/xml_text_test.rb:1:in `require_relative' from /«PKGBUILDDIR»/test/unit/xml_text_test.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in main' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `main' rake aborted! Command failed with status (1): [ruby -Ilib -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb ./test/unit/xml_text_test.rb ./test/unit/xml_required_test.rb ./test/unit/xml_object_test.rb ./test/unit/xml_namespace_test.rb ./test/unit/xml_name_test.rb ./test/unit/xml_initialize_test.rb ./test/unit/xml_hash_test.rb ./test/unit/xml_convention_test.rb ./test/unit/xml_bool_test.rb ./test/unit/xml_block_test.rb ./test/unit/xml_attribute_test.rb ./test/unit/to_xml_test.rb ./test/unit/deprecations_test.rb ./test/unit/definition_test.rb ] -e:1:in `main' Tasks: TOP = default = test (See full trace by running task with --trace) ERROR: Test ruby1.9.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/01/14/ruby-roxml_3.3.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Hi, rails-3.2 3.2.16-3+0 dropped the patch using minitest. I am therefore closing this bug. Cheers, Cédric---End Message---
Bug#738432: marked as done (ruby-vegas: FTBFS: ERROR: Test ruby2.0 failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser)
Your message dated Tue, 25 Feb 2014 23:50:23 + with message-id e1wirlx-0004xy...@franck.debian.org and subject line Bug#737032: fixed in thin 1.3.1-5 has caused the Debian Bug report #737032, regarding ruby-vegas: FTBFS: ERROR: Test ruby2.0 failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser 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.) -- 737032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-vegas Version: 0.1.11-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140208 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require': without environment - should raise an exception without --app-dir /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' /usr/lib/ruby/vendor_ruby/thin.rb:42:in `top (required)' /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' /usr/lib/ruby/vendor_ruby/rack/handler/thin.rb:1:in `top (required)' /«PKGBUILDDIR»/test/test_helper.rb:24:in `vegas' /«PKGBUILDDIR»/test/test_vegas_runner.rb:180:in `block (4 levels) in top (required)' /«PKGBUILDDIR»/test/test_vegas_runner.rb:177:in `block (3 levels) in top (required)' /«PKGBUILDDIR»/test/test_vegas_runner.rb:164:in `block (2 levels) in top (required)' /«PKGBUILDDIR»/test/test_vegas_runner.rb:15:in `block in top (required)' /«PKGBUILDDIR»/test/test_vegas_runner.rb:8:in `top (required)' /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' debian/ruby-tests.rb:2:in `main' 26 specifications (0 requirements), 0 failures, 26 errors ERROR: Test ruby2.0 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/02/08/ruby-vegas_0.1.11-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: thin Source-Version: 1.3.1-5 We believe that the bug you reported is fixed in the latest version of thin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 737...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hofstaedtler z...@debian.org (supplier of updated thin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Feb 2014 00:22:32 +0100 Source: thin Binary: thin thin1.8 Architecture: source amd64 all Version: 1.3.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Christian Hofstaedtler z...@debian.org Description: thin - fast and very simple Ruby web server thin1.8- Transitional package for thin Closes: 737032 Changes: thin (1.3.1-5) unstable; urgency=medium . * Team upload. * Use standard search path for thin_parser (Closes: #737032) Checksums-Sha1: 8d9e284a44a2a3b65a12a24a34d2697bed814539 2111 thin_1.3.1-5.dsc db27c8652bf0cbd31e779852e14639bcfb012d65 8112 thin_1.3.1-5.debian.tar.xz 4c3fc7743f2108a6857d33ebbad525e62ba1ee5a 49258 thin_1.3.1-5_amd64.deb 4934a95368b3ba28ca5e352606105661b5d521d4 10998 thin1.8_1.3.1-5_all.deb Checksums-Sha256: 35e3d490d0245a5e9144bd19104016806313bee453dc1e53d3ffba72995fa76e 2111 thin_1.3.1-5.dsc
Bug#737032: marked as done (thin: looks for vendor_ruby multiarch libs in wrong location)
Your message dated Tue, 25 Feb 2014 23:50:23 + with message-id e1wirlx-0004xy...@franck.debian.org and subject line Bug#737032: fixed in thin 1.3.1-5 has caused the Debian Bug report #737032, regarding thin: looks for vendor_ruby multiarch libs in wrong location 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.) -- 737032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: thin Version: 1.3.1-4 Severity: important Dear Maintainer, It looks as if ruby2.0 and thin disagree on where to find multiarch libs: kdienes@remus:~$ ruby --version ruby 2.0.0p353 (2013-11-22) [x86_64-linux-gnu] kdienes@remus:~$ dpkg -S thin_parser thin: /usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux/thin_parser.so thin: /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.0.0/thin_parser.so kdienes@remus:~$ thin /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require': cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser (LoadError) from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' from /usr/lib/ruby/vendor_ruby/thin.rb:42:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' from /usr/bin/thin:5:in `main' kdienes@remus:~$ ls /usr/lib/ruby/vendor_ruby/2.0.0/ kdienes@remus:~$ apt-cache policy thin kdienes@remus:/usr/lib/ruby/vendor_ruby/2.0.0$ sudo ln -s /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.0.0 x86_64-linux-gnu^C kdienes@remus:/usr/lib/ruby/vendor_ruby/2.0.0$ thin --version thin 1.3.1 codename Triple Espresso Thanks for your work on thin! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages thin depends on: ii libc6 2.17-97 ii libruby1.9.1 1.9.3.484-1 ii libruby2.02.0.0.353-1 ii ruby 1:1.9.3 ii ruby-daemons 1.1.9-1 ii ruby-eventmachine 1.0.3-4 ii ruby-rack1.4 [ruby-rack] 1.4.5-1 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-1 ii ruby2.0 [ruby-interpreter]2.0.0.353-1 thin recommends no packages. thin suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: thin Source-Version: 1.3.1-5 We believe that the bug you reported is fixed in the latest version of thin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 737...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Hofstaedtler z...@debian.org (supplier of updated thin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Feb 2014 00:22:32 +0100 Source: thin Binary: thin thin1.8 Architecture: source amd64 all Version: 1.3.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Christian Hofstaedtler z...@debian.org Description: thin - fast and very simple Ruby web server thin1.8- Transitional package for thin Closes: 737032 Changes: thin (1.3.1-5) unstable; urgency=medium . * Team upload. * Use standard search path for thin_parser (Closes: #737032) Checksums-Sha1: 8d9e284a44a2a3b65a12a24a34d2697bed814539 2111 thin_1.3.1-5.dsc db27c8652bf0cbd31e779852e14639bcfb012d65 8112 thin_1.3.1-5.debian.tar.xz 4c3fc7743f2108a6857d33ebbad525e62ba1ee5a 49258 thin_1.3.1-5_amd64.deb 4934a95368b3ba28ca5e352606105661b5d521d4 10998
Bug#739998: marked as done (cobertura: FTBFS: Maven error)
Your message dated Wed, 26 Feb 2014 00:04:32 + with message-id e1wirze-0006u5...@franck.debian.org and subject line Bug#74: fixed in maven-repo-helper 1.8.7 has caused the Debian Bug report #74, regarding cobertura: FTBFS: Maven error 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.) -- 74: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=74 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:cobertura Version: 1.9.4.1+dfsg-3 Severity: serious Justification: fails to build from source (but built successfully in the past) The full log is attached to this bug report. Relevant error message: dh_auto_install mh_installpom -plibcobertura-java /tmp/buildd/cobertura-1.9.4.1+dfsg/debian/cobertura.pom Exception in thread main java.lang.NullPointerException at org.debian.maven.repo.POMReader.readPom(POMReader.java:125) at org.debian.maven.repo.POMReader.readPom(POMReader.java:57) at org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226) at org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211) at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:74) at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:373) make[1]: *** [override_dh_auto_install] Error 1 make[1]: Leaving directory `/tmp/buildd/cobertura-1.9.4.1+dfsg' make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 E: Failed autobuilding of package I: unmounting dev/pts filesystem I: unmounting run/shm filesystem I: unmounting proc filesystem - Cleaning COW directory forking: rm -rf /var/cache/pbuilder/build//cow.16051 -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 Faith means not wanting to know what is true. -- Nietzsche cobertura_1.9.4.1+dfsg-3_amd64.build.gz Description: Binary data signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: maven-repo-helper Source-Version: 1.8.7 We believe that the bug you reported is fixed in the latest version of maven-repo-helper, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 740...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg ebo...@apache.org (supplier of updated maven-repo-helper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 26 Feb 2014 00:44:34 +0100 Source: maven-repo-helper Binary: maven-repo-helper Architecture: source all Version: 1.8.7 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: maven-repo-helper - Helper tools for including Maven metadata in Debian packages Closes: 74 Changes: maven-repo-helper (1.8.7) unstable; urgency=medium . * Fixed the parsing of the systemPath element (Closes: #74) Checksums-Sha1: 102042d788de896fcf164dfa52e76f81ffb5a240 1969 maven-repo-helper_1.8.7.dsc 58a2fa4f8791675604b9a6b0c83ecea5c21cd0ee 101688 maven-repo-helper_1.8.7.tar.xz dc912706f44039699805badddc808419bae04faa 131836 maven-repo-helper_1.8.7_all.deb Checksums-Sha256: a137128feff4ead3a740d94cbc027d42149327d6207d5df7ebdb8bd571e3d115 1969 maven-repo-helper_1.8.7.dsc 90284fd5ca8863f0872ef19859132ce770106d71bdf3170c130a1da23b73415f 101688 maven-repo-helper_1.8.7.tar.xz 1a0ab36f9b5f30ccab023ca02348a0032b9b74ea3dd84d1e71a906141fe7f702 131836 maven-repo-helper_1.8.7_all.deb Files: 5a832fe7562bedaf3d64c739568d2f21 1969 java optional maven-repo-helper_1.8.7.dsc 5eefc937034c8a40111f527aa052e106 101688 java optional maven-repo-helper_1.8.7.tar.xz
Bug#734268: linux-image-3.12-1-amd64: NFS-related crashes
Control: severity -1 important Control: tag -1 upstream I recognise it's a major problem for you but I'm afraid it's not strictly a critical severity. I found a similar bug report against Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1050206. That bug report has two patches which were supposed to fix it, and which worked for other reporters... but they are included in 3.13.4, so they apparently don't completely fix the bug. Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#734268: linux-image-3.12-1-amd64: NFS-related crashes
Processing control commands: severity -1 important Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Severity set to 'important' from 'critical' tag -1 upstream Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Added tag(s) upstream. -- 734268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734268 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#728139: marked as done (brutefir: FTBFS on kfreebsd-i386: fftw_convolver.c:(.text+0x5288): undefined reference to `convolver_sse_convolve_add')
Your message dated Wed, 26 Feb 2014 03:18:42 + with message-id e1wiv18-00068x...@franck.debian.org and subject line Bug#728139: fixed in brutefir 1.0m-1 has caused the Debian Bug report #728139, regarding brutefir: FTBFS on kfreebsd-i386: fftw_convolver.c:(.text+0x5288): undefined reference to `convolver_sse_convolve_add' 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.) -- 728139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: brutefir Version: 1.0l-1 Severity: serious Justifcation: fails to built (but built successfully in the past) brutefir fails to build on kfreebsd-i386: | gcc -L/usr/lib -Xlinker --allow-multiple-definition -o brutefir brutefir.o fftw_convolver.o bfconf.o bfrun.o firwindow.o emalloc.o shmalloc.o dai.o bfconf_lexical.o inout.o dither.o delay.o -lfftw3 -lfftw3f -lm -ldl | fftw_convolver.o: In function `convolver_convolve_add': | fftw_convolver.c:(.text+0x5288): undefined reference to `convolver_sse_convolve_add' | collect2: error: ld returned 1 exit status | make[2]: *** [brutefir] Error 1 Full build log is available at https://buildd.debian.org/status/fetch.php?pkg=brutefirarch=kfreebsd-i386ver=1.0l-1stamp=1381845349 Regards -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: brutefir Source-Version: 1.0m-1 We believe that the bug you reported is fixed in the latest version of brutefir, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 728...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felipe Sateler fsate...@debian.org (supplier of updated brutefir package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Feb 2014 22:42:05 -0300 Source: brutefir Binary: brutefir Architecture: source amd64 Version: 1.0m-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Felipe Sateler fsate...@debian.org Description: brutefir - software convolution engine Closes: 728139 Changes: brutefir (1.0m-1) unstable; urgency=medium . * Team Upload. . [ Jaromír Mikeš ] * Imported Upstream version 1.0m * Set dh/compat 9. * Bump Standards. * Add myself as uploader. * Patches refreshed. * Little fix in description. * Added patch partially fix hardening. * Added patch fix FTBFS on kfreebsd-i386 (Closes: #728139). . [ Felipe Sateler ] * Use gcc instead of ld directly to link. * Pass LDFLAGS to brutefir link. * Change _init functions to use constructor attributes instead * Enable parallel builds Checksums-Sha1: d5f26dfed6ddffdbe805615244e70cb43f69a7f1 2043 brutefir_1.0m-1.dsc 86d325f51e9679ffce6db17e6b288194a67369a2 246064 brutefir_1.0m.orig.tar.gz 495dda8bbccec6d52044cf23b751140d838d86fd 7328 brutefir_1.0m-1.debian.tar.xz 8368a698d95d8f5a27bb09e942c8656578289ce3 166196 brutefir_1.0m-1_amd64.deb Checksums-Sha256: 9a042af53323f1b22db3b6181b0c4601e8e35360d2a510ceeeb2d1a6e3b5f57b 2043 brutefir_1.0m-1.dsc 23b80500fc8687be338bc2654ecc509eccc06fe9372815361b65ed9b1807ccca 246064 brutefir_1.0m.orig.tar.gz 76df3db550141d5c8dd4e8b1a10e9e4281432e70247718c6655b32a503df1164 7328 brutefir_1.0m-1.debian.tar.xz 49630262f8e42d70804e74fcbe3bca11225bd8a3783b81cfa515d69a855a0a0f 166196 brutefir_1.0m-1_amd64.deb Files: 0a1eacb5ed95a87b078a09a3b5c593ef 2043 sound optional brutefir_1.0m-1.dsc 13e8fe1ad17a938c7ebfb3ecc0a18fd0 246064 sound optional brutefir_1.0m.orig.tar.gz 649cfa463722ac5430cf1b7a72305105 7328 sound optional brutefir_1.0m-1.debian.tar.xz 51f9ab370bffb243d7795ee54f036d6e 166196 sound optional brutefir_1.0m-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTDUfYAAoJEKO6uuJAjdbPaAAP/RF2Xn/kk4Ue3bFzhkv4ElR0 f7XG8mlAKYF7b8vCarv0G+TrexJcXfpWsDL90QEVbPCk2IEumMPsR5Q3GovIkA8/ YyZVBK4HRB8q26w/hW4P0zHbwMU5EP9t6sVUfw7dcrmobF5v+APGU26W4W/e04M9 BqLo6EWZ/WVttw4v/0dJOI195tpU5X3N1RcDR+I2Lr2jO6mieWZrFEimZq3P5mve k+Q2nAc0WnhDUvbp4LVogFnclBZ+Nhv/VdnQ3zhjuKE4Ds/1iXqajx/0tulpOZBk
Bug#737953: marked as done (itstool: FTBFS: configure: error: no suitable Python interpreter found)
Your message dated Wed, 26 Feb 2014 03:20:42 +
with message-id e1wiv34-0006pb...@franck.debian.org
and subject line Bug#737953: fixed in itstool 2.0.2-2
has caused the Debian Bug report #737953,
regarding itstool: FTBFS: configure: error: no suitable Python interpreter 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.)
--
737953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: itstool
Version: 2.0.2-1
Severity: serious
From my pbuilder build log:
...
debian/rules build
dh build
dh_testdir
dh_auto_configure
configure: WARNING: unrecognized options: --disable-maintainer-mode,
--disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for a Python interpreter with version = 2.6... none
configure: error: no suitable Python interpreter found
== config.log ==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by itstool configure 2.0.2, which was
generated by GNU Autoconf 2.66. Invocation command line was
$ ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libexecdir=${prefix}/lib/itstool --disable-maintainer-mode
--disable-dependency-tracking
## - ##
## Platform. ##
## - ##
hostname = frobozz
uname -m = x86_64
uname -r = 3.11-1-amd64
uname -s = Linux
uname -v = #1 SMP Debian 3.11.6-1+x32 (2013-10-29)
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
## --- ##
## Core tests. ##
## --- ##
configure:1720: checking for a BSD-compatible install
configure:1788: result: /usr/bin/install -c
configure:1799: checking whether build environment is sane
configure:1849: result: yes
configure:1990: checking for a thread-safe mkdir -p
configure:2029: result: /bin/mkdir -p
configure:2042: checking for gawk
configure:2072: result: no
configure:2042: checking for mawk
configure:2058: found /usr/bin/mawk
configure:2069: result: mawk
configure:2080: checking whether make sets $(MAKE)
configure:2102: result: yes
configure:2223: checking for a Python interpreter with version = 2.6
configure:2240: python -c import sys # split strings by '.' and convert to
numeric. Append some zeros # because we need at least 4 digits for the hex
conversion. # map returns an iterator in Python 3.0 and a list in 2.x minver =
list(map(int, '2.6'.split('.'))) + [0, 0, 0] minverhex = 0 # xrange is not
present in Python 3.0 and range returns an iterator for i in list(range(0, 4)):
minverhex = (minverhex 8) + minver[i] sys.exit(sys.hexversion minverhex)
./configure: line 2241: python: command not found
configure:2243: $? = 127
configure:2240: python2 -c import sys # split strings by '.' and convert to
numeric. Append some zeros # because we need at least 4 digits for the hex
conversion. # map returns an iterator in Python 3.0 and a list in 2.x minver =
list(map(int, '2.6'.split('.'))) + [0, 0, 0] minverhex = 0 # xrange is not
present in Python 3.0 and range returns an iterator for i in list(range(0, 4)):
minverhex = (minverhex 8) + minver[i] sys.exit(sys.hexversion minverhex)
./configure: line 2241: python2: command not found
configure:2243: $? = 127
configure:2240: python3 -c import sys # split strings by '.' and convert to
numeric. Append some zeros # because we need at least 4 digits for the hex
conversion. # map returns an iterator in Python 3.0 and a list in 2.x minver =
list(map(int, '2.6'.split('.'))) + [0, 0, 0] minverhex = 0 # xrange is not
present in Python 3.0 and range returns an iterator for i in list(range(0, 4)):
minverhex = (minverhex 8) + minver[i] sys.exit(sys.hexversion minverhex)
./configure: line 2241: python3: command not found
configure:2243: $? = 127
configure:2240: python3.0 -c import sys # split strings by '.' and convert to
numeric. Append some zeros # because we need at least 4 digits for the hex
conversion. # map returns an
Bug#733423: marked as done (ruby-activesupport-3.2 should depend on ruby-minitest or drop port-to-minitest.patch)
Your message dated Wed, 26 Feb 2014 03:23:35 + with message-id e1wiv5r-0007nn...@franck.debian.org and subject line Bug#733423: fixed in rails-3.2 3.2.17-1 has caused the Debian Bug report #733423, regarding ruby-activesupport-3.2 should depend on ruby-minitest or drop port-to-minitest.patch 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.) -- 733423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-fixture-builder Version: 0.3.6-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/active_support/test_case.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/active_record/test_case.rb:5:in `module:ActiveRecord' from /usr/lib/ruby/vendor_ruby/active_record/test_case.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/test_helper.rb:17:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/fixture_builder_test.rb:1:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in main' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `main' rake aborted! Command failed with status (1): [ruby -Ilib:test -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/fixture_builder_test.rb test/legacy_fixture_mode_fixture_generation_test.rb test/legacy_fixture_mode_test.rb test/namer_test.rb ] -e:1:in `main' Tasks: TOP = default = test (See full trace by running task with --trace) ERROR: Test ruby1.9.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/ruby-fixture-builder_0.3.6-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: rails-3.2 Source-Version: 3.2.17-1 We believe that the bug you reported is fixed in the latest version of rails-3.2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 733...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro terce...@debian.org (supplier of updated rails-3.2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Feb 2014 11:16:11 -0300 Source: rails-3.2 Binary: ruby-activesupport-3.2 ruby-activerecord-3.2 ruby-activeresource-3.2 ruby-activemodel-3.2 ruby-actionpack-3.2 ruby-actionmailer-3.2 ruby-railties-3.2 ruby-rails-3.2 rails3 Architecture: source all Version: 3.2.17-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Antonio Terceiro terce...@debian.org Description: rails3 - MVC ruby based framework geared for web application development ruby-actionmailer-3.2 - email composition, delivery, and receiving framework (part of Rai ruby-actionpack-3.2 - web-flow and rendering framework putting the VC in MVC (part of R
Bug#740139: gnome-maps fails to start
Package: gnome-maps Version: 3.10.2-1 Severity: grave Justification: renders package unusable Trying to start gnome-maps I get the following stderr output: JS ERROR: !!! Exception was: Gio.DBusError: Error calling StartServiceByName for org.freedesktop.GeoClue2: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 253 JS ERROR: !!! message = 'Error calling StartServiceByName for org.freedesktop.GeoClue2: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 253' JS ERROR: !!! fileName = '/usr/share/gjs-1.0/overrides/Gio.js' JS ERROR: !!! lineNumber = '250' JS ERROR: !!! stack = '0 anonymous(null)@/usr/share/gjs-1.0/overrides/Gio.js:250 1 anonymous(cancellable = null, asyncCallback = undefined, object = /org/freedesktop/GeoClue2/Manager, name = org.freedesktop.GeoClue2, bus = [object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:209 2 anonymous()@/usr/share/gnome-maps/js/geoclue.js:110 3 wrapper()@/usr/share/gjs-1.0/lang.js:213 4 anonymous()@/usr/share/gjs-1.0/lang.js:154 5 anonymous()@/usr/share/gjs-1.0/lang.js:248 6 anonymous(overlay = [object GObject_Object])@/usr/share/gnome- maps/js/mapView.js:87 7 wrapper([object GObject_Object])@/usr/share/gjs-1.0/lang.js:213 8 anonymous(app = [object GObject_Object])@/usr/share/gnome- maps/js/mainWindow.js:69 9 wrapper([object GObject_Object])@/usr/share/gjs-1.0/lang.js:213 10 anonymous([object GObject_Object])@/usr/share/gjs-1.0/lang.js:154 11 anonymous([object GObject_Object])@/usr/share/gjs-1.0/lang.js:248 12 anonymous()@/usr/share/gnome-maps/js/application.js:97 13 wrapper()@/usr/share/gjs-1.0/lang.js:213 14 anonymous()@/usr/share/gnome-maps/js/application.js:102 15 wrapper()@/usr/share/gjs-1.0/lang.js:213 16 start()@/usr/share/gnome-maps/js/main.js:28 17 TOP LEVEL@command line:1 ' Is it somehow possible to start the geoclue2 dbus service manually to try and debug this? Sincerly, Marcus Lundblad -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-maps depends on: ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1 ii geoclue-2.0 2.0.0-4 ii gir1.2-champlain-0.120.12.5-1 ii gir1.2-clutter-1.0 1.14.4-3 ii gir1.2-cogl-1.0 1.14.0-3 ii gir1.2-gdkpixbuf-2.0 2.30.5-1 ii gir1.2-geocodeglib-1.0 3.10.0-1 ii gir1.2-glib-2.0 1.36.0-2+b1 ii gir1.2-gtk-3.0 3.10.7-1 ii gir1.2-gtkchamplain-0.12 0.12.5-1 ii gir1.2-gtkclutter-1.01.4.4-3 ii gjs 1.36.1-2 gnome-maps recommends no packages. gnome-maps 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#740106: libraw: FTBFS on 32-bit platforms: symbols not quite as expected
Hi! When fixing the symbols files, please also have a look at the build logs for all the Debian ports which are affected as well [1]. Since the build logs all contain the necessary diffs for the symbols files, you have all the information you need to fix them. Here's a bug report which shows the respective problem on m68k for reference [2]. Thanks! Adrian [1] http://buildd.debian-ports.org/status/package.php?p=librawsuite=sid [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726969 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721621: [Pkg-nagios-devel] Bug#721621: dependency change s/libradiusclient-ng2/libfreeradius-client2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Daniel, Am 02.02.14 22:18, schrieb Daniel Pocock: Looks like argument 1 and 6 are new. They may or may not be needed, if we are lucky you can just insert 0 for missing arguments and it will emulate the old behavior but that is not something I would to guess, I would need to check the API. Let me know if there is no answer from upstream and then I can look inside. looks like from the upstream side is actually more work to do on the infrastructure then on the code side and this maybe not get fixed shortterm. If you want to push things forward, feel free to have a look on it. Many thanks, Jan. - -- Never write mail to w...@spamfalle.info, you have been warned! - -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAlMNm88ACgkQ9u6Dud+QFyTpZwCfcWTNSTmPumlJQxj2RlQ8HATw zOAAoIniNdhfH/FwLqq9dE1CrC8CvOfh =N3Vm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739286: marked as done (Buiuld-depends on radiusclient-ng, scheduled to be removed)
Your message dated Wed, 26 Feb 2014 07:49:06 + with message-id e1wizeo-00070c...@franck.debian.org and subject line Bug#739286: fixed in kamailio 4.1.1-4 has caused the Debian Bug report #739286, regarding Buiuld-depends on radiusclient-ng, scheduled to be removed 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.) -- 739286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ftp.debian.org src:radiusclient-ng is replaced by the new src:freeradius-client Upstream explain it here: http://freeradius.org/freeradius-client/ (see History) The new src package is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717324 and has been uploaded to the queue ---End Message--- ---BeginMessage--- Source: kamailio Source-Version: 4.1.1-4 We believe that the bug you reported is fixed in the latest version of kamailio, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 739...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tzafrir Cohen tzaf...@debian.org (supplier of updated kamailio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 26 Feb 2014 08:36:12 +0200 Source: kamailio Binary: kamailio kamailio-dbg kamailio-geoip-modules kamailio-sqlite-modules kamailio-json-modules kamailio-memcached-modules kamailio-lua-modules kamailio-mono-modules kamailio-python-modules kamailio-redis-modules kamailio-mysql-modules kamailio-postgres-modules kamailio-cpl-modules kamailio-radius-modules kamailio-unixodbc-modules kamailio-presence-modules kamailio-perl-modules kamailio-snmpstats-modules kamailio-xmpp-modules kamailio-xml-modules kamailio-carrierroute-modules kamailio-berkeley-modules kamailio-berkeley-bin kamailio-ldap-modules kamailio-ims-modules kamailio-utils-modules kamailio-sctp-modules kamailio-java-modules kamailio-tls-modules kamailio-outbound-modules kamailio-websocket-modules kamailio-dnssec-modules kamailio-autheph-modules Architecture: source amd64 Version: 4.1.1-4 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org Changed-By: Tzafrir Cohen tzaf...@debian.org Description: kamailio - very fast and configurable SIP proxy kamailio-autheph-modules - authentication using ephemeral credentials module for Kamailio kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program kamailio-berkeley-modules - Berkeley database module for Kamailio kamailio-carrierroute-modules - carrierroute module for Kamailio kamailio-cpl-modules - CPL module (CPL interpreter engine) for Kamailio kamailio-dbg - very fast and configurable SIP proxy [debug symbols] kamailio-dnssec-modules - contains the dnssec module kamailio-geoip-modules - contains the geoip module kamailio-ims-modules - IMS module for Kamailio kamailio-java-modules - contains the app_java module kamailio-json-modules - Json parser and jsonrpc modules for Kamailio kamailio-ldap-modules - LDAP modules for Kamailio kamailio-lua-modules - contains the app_lua module kamailio-memcached-modules - Provides the memcached module, an interface to the memcached serv kamailio-mono-modules - contains the app_mono module kamailio-mysql-modules - MySQL database connectivity module for Kamailio kamailio-outbound-modules - Outbound module for Kamailio kamailio-perl-modules - Perl extensions and database driver for Kamailio kamailio-postgres-modules - PostgreSQL database connectivity module for Kamailio kamailio-presence-modules - SIMPLE presence modules for Kamailio kamailio-python-modules - contains the app_python module kamailio-radius-modules - RADIUS modules for Kamailio kamailio-redis-modules - Redis database connectivity module for Kamailio kamailio-sctp-modules - sctp module for Kamailio kamailio-snmpstats-modules - SNMP AgentX subagent module for Kamailio kamailio-sqlite-modules - SQLite database connectivity module for Kamailio kamailio-tls-modules - contains the TLS kamailio transport module kamailio-unixodbc-modules - unixODBC database connectivity module for Kamailio
