Bug#759997: marked as done (par2: filechecksummer.cpp crash introduced in 0.6.8)
Your message dated Thu, 11 Sep 2014 06:04:24 +
with message-id e1xrxuw-0005xr...@franck.debian.org
and subject line Bug#759997: fixed in par2cmdline 0.6.10-1
has caused the Debian Bug report #759997,
regarding par2: filechecksummer.cpp crash introduced in 0.6.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
759997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: par2cmdline
Version: 0.6.8-1
Severity: grave
Hi,
par2 0.6.8 introduces a major regression from 0.6.7; it crashes when
parsing certain kinds of damaged file sets. I've attached a test case
that reproduces the issue. This was found using the bup test suite; see
related Debian bug #759930.
Here is the output of 0.6.7's par2verify running on the damaged file
set:
edmonds@chase{0}:~/debian/tmp/par2-0.6.8-crash$ par2verify
pack-ea5f7f848340980493ed39f5b7173d956c680e43.par2
Loading pack-ea5f7f848340980493ed39f5b7173d956c680e43.par2.
Loaded 6 new packets
Loading pack-ea5f7f848340980493ed39f5b7173d956c680e43.vol000+200.par2.
Loaded 200 new packets including 200 recovery blocks
Loading pack-ea5f7f848340980493ed39f5b7173d956c680e43.par2.
No new packets found
There are 2 recoverable files and 0 other files.
The block size used was 4 bytes.
There are a total of 329 data blocks.
The total size of the data files is 1316 bytes.
Verifying source files:
Target: pack-ea5f7f848340980493ed39f5b7173d956c680e43.idx - damaged.
Found 266 of 275 data blocks.
Target: pack-ea5f7f848340980493ed39f5b7173d956c680e43.pack - damaged.
Found 3 of 54 data blocks.
Scanning extra files:
Repair is required.
2 file(s) exist but are damaged.
You have 269 out of 329 data blocks available.
You have 200 recovery blocks available.
Repair is possible.
You have an excess of 140 recovery blocks.
60 recovery blocks will be used to repair.
edmonds@chase{1}:~/debian/tmp/par2-0.6.8-crash$
Here is the output of 0.6.8's par2verify running on the damaged file
set:
edmonds@chase{0}:~/debian/tmp/par2-0.6.8-crash$ par2verify
pack-ea5f7f848340980493ed39f5b7173d956c680e43.par2
pack-ea5f7f848340980493ed39f5b7173d956c680e43.vol000+200.par2
Loading pack-ea5f7f848340980493ed39f5b7173d956c680e43.par2.
Loaded 6 new packets
Loading pack-ea5f7f848340980493ed39f5b7173d956c680e43.vol000+200.par2.
Loaded 200 new packets including 200 recovery blocks
Loading pack-ea5f7f848340980493ed39f5b7173d956c680e43.par2.
No new packets found
Loading pack-ea5f7f848340980493ed39f5b7173d956c680e43.vol000+200.par2.
No new packets found
There are 2 recoverable files and 0 other files.
The block size used was 4 bytes.
There are a total of 329 data blocks.
The total size of the data files is 1316 bytes.
Verifying source files:
par2verify: filechecksummer.cpp:85: bool FileCheckSummer::Jump(u64):
Assertion `distance = blocksize' failed.
zsh: abort (core dumped) par2verify
pack-ea5f7f848340980493ed39f5b7173d956c680e43.par2
edmonds@chase{134}:~/debian/tmp/par2-0.6.8-crash$
I've attached an archive of the damaged file set.
I would guess that this upstream commit is the culprit:
https://github.com/BlackIkeEagle/par2cmdline/commit/58c973496b21608d54246fd9c859bf8ccf0a9602
--
Robert Edmonds
edmo...@debian.org
par2-0.6.8-crash.tar.gz
Description: application/gzip
---End Message---
---BeginMessage---
Source: par2cmdline
Source-Version: 0.6.10-1
We believe that the bug you reported is fixed in the latest version of
par2cmdline, 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 759...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
JCF Ploemen (jcfp) li...@jcf.pm (supplier of updated par2cmdline 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, 10 Sep 2014 03:28:10 +0400
Source: par2cmdline
Binary: par2
Architecture: source
Version: 0.6.10-1
Distribution: unstable
Urgency: medium
Maintainer: JCF Ploemen (jcfp) li...@jcf.pm
Changed-By: JCF Ploemen (jcfp) li...@jcf.pm
Bug#758619:
Hi Version 6.5.1 is installed on my system and the bug is still there. = apt show reportbug Package: reportbug Version: 6.5.1 Installed-Size: 226 kB Maintainer: Reportbug Maintainers reportbug-ma...@lists.alioth.debian.org Depends: python, python:any (= 2.6~), apt, python-reportbug (= 6.5.1) Suggests: postfix | exim4 | mail-transport-agent, gnupg | pgp, debconf-utils ( 1.1.0), debsums (= 2.0.47), file ( 1.30), dlocate, python-urwid, python-gtk2, python-vte, python-gtkspell, xdg-utils, emacs22-bin-common | emacs23-bin-common, claws-mail (= 3.8.0) Homepage: http://alioth.debian.org/projects/reportbug/ Tag: devel::bugtracker, implemented-in::python, interface::commandline, mail::smtp, network::client, protocol::http, protocol::smtp, role::program, scope::utility, suite::debian, use::TODO, works-with-format::plaintext, works-with::bugs Section: utils Priority: standard Download-Size: 122 kB APT-Manual-Installed: yes APT-Sources: http://http.us.debian.org/debian/ unstable/main amd64 Packages Description: reports bugs in the Debian distribution reportbug is a tool designed to make the reporting of bugs in Debian and derived distributions relatively painless. Its features include: . * Integration with mutt and mh/nmh mail readers. * Access to outstanding bug reports to make it easier to identify whether problems have already been reported. * Automatic checking for newer versions of packages. * Optional automatic verification of integrity of packages via debsums. * Support for following-up on outstanding reports. * Optional PGP/GnuPG integration. . reportbug is designed to be used on systems with an installed mail transport agent, like exim or sendmail; however, you can edit the configuration file and send reports using any available mail server. . This package also includes the querybts script for browsing the Debian bug tracking system. = On execution : l@leonardo ~ % reportbug Attempt to unlock mutex that was not locked zsh: abort reportbug l@leonardo ~ % echo $? 134 l@leonardo ~ % signature.asc Description: This is a digitally signed message part
Bug#761151: lxmenu-data and lxlauncher: error when trying to install together
Package: lxlauncher,lxmenu-data Version: lxlauncher/0.2.3-1 Version: lxmenu-data/0.1.3-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-11 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 41% Extracting templates from packages: 83% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libgmp10:amd64. (Reading database ... 10869 files and directories currently installed.) Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-3_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-3) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-3_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2) ... Preparing to unpack .../libp11-kit0_0.20.3-2_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.3-2) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.1-2_amd64.deb ... Unpacking libtasn1-6:amd64 (4.1-2) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.7-2_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.7-2) ... Selecting previously unselected package libkeyutils1:amd64. Preparing to unpack .../libkeyutils1_1.5.9-5_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-5) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12.1+dfsg-9_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12.1+dfsg-9) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12.1+dfsg-9_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12.1+dfsg-9) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12.1+dfsg-9_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12.1+dfsg-9) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12.1+dfsg-9_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12.1+dfsg-9) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.1+dfsg1-4_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-4) ... Selecting previously unselected package libglib2.0-0:amd64. Preparing to unpack .../libglib2.0-0_2.40.0-5_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.40.0-5) ... Selecting previously unselected package libatk1.0-data. Preparing to unpack .../libatk1.0-data_2.12.0-1_all.deb ... Unpacking libatk1.0-data (2.12.0-1) ... Selecting previously unselected package libatk1.0-0:amd64. Preparing to unpack .../libatk1.0-0_2.12.0-1_amd64.deb ... Unpacking libatk1.0-0:amd64 (2.12.0-1) ... Selecting previously unselected package libavahi-common-data:amd64. Preparing to unpack .../libavahi-common-data_0.6.31-4_amd64.deb ... Unpacking libavahi-common-data:amd64 (0.6.31-4) ... Selecting previously unselected package libavahi-common3:amd64. Preparing to unpack .../libavahi-common3_0.6.31-4_amd64.deb ... Unpacking libavahi-common3:amd64 (0.6.31-4) ... Selecting previously unselected package libdbus-1-3:amd64. Preparing to unpack .../libdbus-1-3_1.8.6-2_amd64.deb ... Unpacking libdbus-1-3:amd64 (1.8.6-2) ... Selecting previously unselected package libavahi-client3:amd64. Preparing to unpack .../libavahi-client3_0.6.31-4_amd64.deb ... Unpacking libavahi-client3:amd64 (0.6.31-4) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6) ... Selecting previously unselected package libpng12-0:amd64. Preparing to unpack .../libpng12-0_1.2.50-2_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.50-2) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../libfreetype6_2.5.2-1.1_amd64.deb ... Unpacking libfreetype6:amd64 (2.5.2-1.1) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0030_all.deb ... Moving old data out of the way Unpacking ucf (3.0030) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../fonts-dejavu-core_2.34-1_all.deb ... Unpacking fonts-dejavu-core (2.34-1) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../fontconfig-config_2.11.0-6.1_all.deb ... Unpacking fontconfig-config (2.11.0-6.1) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../libfontconfig1_2.11.0-6.1_amd64.deb ...
Bug#759526: marked as done (not-yet-commons-ssl: CVE-2014-3604)
Your message dated Thu, 11 Sep 2014 06:34:25 + with message-id e1xrxxz-0001kv...@franck.debian.org and subject line Bug#759526: fixed in not-yet-commons-ssl 0.3.15-1 has caused the Debian Bug report #759526, regarding not-yet-commons-ssl: CVE-2014-3604 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.) -- 759526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: not-yet-commons-ssl Severity: grave Tags: security Justification: user security hole This was assigned CVE-2014-3604: http://lists.juliusdavies.ca/pipermail/not-yet-commons-ssl-juliusdavies.ca/2014-August/000832.html Cheers, Moritz ---End Message--- ---BeginMessage--- Source: not-yet-commons-ssl Source-Version: 0.3.15-1 We believe that the bug you reported is fixed in the latest version of not-yet-commons-ssl, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill tmanc...@debian.org (supplier of updated not-yet-commons-ssl 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: Wed, 10 Sep 2014 22:56:26 -0700 Source: not-yet-commons-ssl Binary: libnot-yet-commons-ssl-java libnot-yet-commons-ssl-java-doc Architecture: source all Version: 0.3.15-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: tony mancill tmanc...@debian.org Description: libnot-yet-commons-ssl-java - Not-yet-commons-SSL is a library to make SSL in Java easier libnot-yet-commons-ssl-java-doc - Documentation for Not-yet-commons-SSL Closes: 759526 Changes: not-yet-commons-ssl (0.3.15-1) unstable; urgency=medium . * Team upload. * New upstream release. - Fixes CVE-2014-3604. (Closes: #759526) * debian/control: - Add Vcs- fields; package is now available in pkg-java git. - Bump Standards-Version to 3.9.5. - Add build-deps needed for junit tests. * Use debhelper 9. * Enable unit tests. * Fix lintian warning in debian/copyright regarding MIT/X11 license. Checksums-Sha1: 19a6008f112eec469c2917b545c6d1516fb0aaf5 2283 not-yet-commons-ssl_0.3.15-1.dsc 80a97f9e4314b87204bf140a6596dbb06ec2f631 554171 not-yet-commons-ssl_0.3.15.orig.tar.bz2 0833b82696692dece693343e775addc34eb40fc8 5280 not-yet-commons-ssl_0.3.15-1.debian.tar.xz 4cf2b7d37fca1f303946fdaa5f33518cefd44d01 269028 libnot-yet-commons-ssl-java_0.3.15-1_all.deb 72991162c715612d834caa48594bf00dc648cd79 318106 libnot-yet-commons-ssl-java-doc_0.3.15-1_all.deb Checksums-Sha256: fdb2532e36aac30346f604078124ba6fb202b01ad429b94a17dc271d39703e72 2283 not-yet-commons-ssl_0.3.15-1.dsc 394fc7e791b74a15129d9a962968aa303da943ec7b71f0a13389d4bf7d892101 554171 not-yet-commons-ssl_0.3.15.orig.tar.bz2 7436963ed65c1d5da60f2a13a6b41d333b04482e533f9e35738fb41af901aeae 5280 not-yet-commons-ssl_0.3.15-1.debian.tar.xz 2afbb6434dd8f44ed872e9a066605241441a94c0fce7c4bc97063187bbd6f46c 269028 libnot-yet-commons-ssl-java_0.3.15-1_all.deb b451a1925b384d4beac68f3923be7c59607ae8ab15e57c8592c7900d11dd8846 318106 libnot-yet-commons-ssl-java-doc_0.3.15-1_all.deb Files: 086e692e60a347ef30716ea24077b6d5 269028 java optional libnot-yet-commons-ssl-java_0.3.15-1_all.deb b3901dad368a32e8595c866459145f01 318106 doc optional libnot-yet-commons-ssl-java-doc_0.3.15-1_all.deb 1859b78704e25c8a671a77ef2be01857 2283 java optional not-yet-commons-ssl_0.3.15-1.dsc 6ea7c615072b64b505e20425bf631753 554171 java optional not-yet-commons-ssl_0.3.15.orig.tar.bz2 1597499e22e13370243097efcd32658b 5280 java optional not-yet-commons-ssl_0.3.15-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUET3cAAoJECHSBYmXSz6W7TgQALc1vbj8f/PFuJ34R7Y1clH6 1WqTRBsyrTjhRGZRBVxfYDYSZNxoRXhQX0B7+MqRM6FVOzJRkbLXNpcBHfRIl7cZ C2McLIb0FJnr54DKklEx2qzH9XBVTFBTNuKJDllOe5Rzvu+IyEEf7qKHkeaVkqaY hn5D9ey+FSoyux9RI5w+nhas0qhOEXUz41OUn+GhPUG/8VBFYVZ8dcKP6fXZHupf JRzBbxDEE1Kx1bblk8nRMIAAx6M3pwwkwgBGx7tlkrI/nmnq+kT4iaLwDH4pBb0V SP4nRyZ2hmOmb42QjZ0s+pp36aroDKVrKoWChn6eF4/Xzo41xjPZ6nbJ6+CIzwof
Processed: reassign 761135 to archdetect
Processing commands for cont...@bugs.debian.org: reassign 761135 archdetect 1.100.0.exp.1 Bug #761135 [debian-installer] archdetect: package rename/package-type change breaks d-i builds Bug reassigned from package 'debian-installer' to 'archdetect'. No longer marked as found in versions debian-installer/20140802. Ignoring request to alter fixed versions of bug #761135 to the same values previously set Bug #761135 [archdetect] archdetect: package rename/package-type change breaks d-i builds Marked as found in versions hw-detect/1.100.0.exp.1. thanks Stopping processing here. Please contact me if you need assistance. -- 761135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761135 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#761107: Thanks for the repport
Hi Ralf, Thanks a lot for these bug reports. In fact, if I made the dependencies this way, it's because the python-xstatic-* packages really need to be tightly coupled, in terms of versionning, to the libjs package. So I wanted to make sure that the libjs packages don't get updates with updates of the python-xstatic packages as well. And that's exactly what's happening right now, with these 3 bug reports. So thanks again! I'm uploading fixes right now. Cheers, Thomas Goirand -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 761135
Processing commands for cont...@bugs.debian.org: # in NEW again tags 761135 + pending Bug #761135 [archdetect] archdetect: package rename/package-type change breaks d-i builds Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 761135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761135 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#761135: archdetect: package rename/package-type change breaks d-i builds
[Cyril Brulebois] Of course a failing d-i build means src:debian-installer FTBFS. What else would that be? Thanks for asking. To me, it could also mean a failing to build a ISO with d-i udebs on it. But I had already tested ISO builds, and thus was a bit unsure what was failing for you. Please explain how you managed to build installation images with a failing d-i build. The ISO build system understand and handle the provides header, and the ISO build is working as before the deb was introduced, as can be seen on for example URL: http://lists.alioth.debian.org/pipermail/debian-edu-commits/2014-September/008537.html . I'm not sure why you're insisting on the renaming. Please explain why you did that (see my first follow-up). Somehow I get the impression that you do not really want to understand why I did this change but just want a set of arguments to brush off before reverting it, but I hope it is just a language barrier issue. Anyway, here are the explanation why I introduced a archdetect deb and how the change have been tested so far. * A archdetect deb allow users on installed systems to figure out which kernel the installer want to install on a given machine. * The need for a normal deb for archdetect have been on the TODO list for years, see for example debian-installer/doc/TODO listing this entry in the Post-etch goals list: - real deb from archdetect udeb (luther) * The deb was already present in Ubuntu, under the name archdetect-deb. Adding the deb in Debian can reduce the diff with Ubuntu. * We normally in Debian name udebs with a -udeb postfix, and name packages after the binary they contain. Diverting from this common naming scheme should be avoided. This I decided to use the sensible name for the deb in Debian, and switch the udeb to have the name we commonly use for udebs in debian, package-udeb. * I knew d-i (anna-install and the rest of the d-i installation system) would handle the provides header, and tested this on a fresh install in a virtual machine before commiting the change. * I checked how many udebs were depending on archdetect (6, if I recall correctly), and new they would cope just fine with the change. * Knew the Debian archive would handle the rename, as udebs and debs have different name spaces, and we use the provides method with several library udebs already. So the change was tested and the installer was working as it should also after the rename. The only thing I didn't test was building the debian-installer source package itself, which broke as you correctly observed. The simple fix is to replace archdetect with archdetect-udeb, but a more proper fix is probably to teach the build of d-i initrds to understand the provides header, to ensure similar issues do not arise in the future. The simple fix is in look like this (commits 50506fe7643ecf44ccc388dab04e3c7fba085dcd and 9925e98994c4406b616e21d9db2703eca5b6ce32) in the debian-installer git repo: diff --git a/debian/changelog b/debian/changelog index a6d89a2..f732bcc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -29,6 +29,10 @@ debian-installer (2014) UNRELEASED; urgency=low - raise the xorriso build dependency to = 1.3.2-1~ on these architectures, for compatibility with grub-mkrescue in GRUB 2.02 + [ Petter Reinholdtsen ] + * Adjust package lists to cope with the archdetect-archdetect-udeb +rename, and remove the rename item from the TODO (Closes: #761135). + -- Cyril Brulebois k...@debian.org Sat, 02 Aug 2014 02:59:35 +0200 debian-installer (20140802) unstable; urgency=low diff --git a/build/pkg-lists/base b/build/pkg-lists/base index 4650288..12c66e2 100644 --- a/build/pkg-lists/base +++ b/build/pkg-lists/base @@ -2,7 +2,7 @@ # get them. busybox-udeb anna -archdetect +archdetect-udeb cdebconf-udeb cdebconf-priority di-utils diff --git a/build/pkg-lists/cdrom/m68k.cfg b/build/pkg-lists/cdrom/m68k.cfg index 61d6947..5ef5b33 100644 --- a/build/pkg-lists/cdrom/m68k.cfg +++ b/build/pkg-lists/cdrom/m68k.cfg @@ -7,4 +7,4 @@ console-setup-amiga-ekmap console-setup-ataritt-ekmap console-setup-udeb kbd-udeb -archdetect +archdetect-udeb diff --git a/build/pkg-lists/hd-media/m68k.cfg b/build/pkg-lists/hd-media/m68k.cfg index d9c75bb..0b61609 100644 --- a/build/pkg-lists/hd-media/m68k.cfg +++ b/build/pkg-lists/hd-media/m68k.cfg @@ -5,4 +5,4 @@ console-setup-amiga-ekmap console-setup-ataritt-ekmap console-setup-udeb kbd-udeb -archdetect +archdetect-udeb diff --git a/doc/TODO b/doc/TODO index ed6167b..f73f37e 100644 --- a/doc/TODO +++ b/doc/TODO @@ -147,7 +147,6 @@ Post-etch goals - low(er) mem (zboob) - uml for testing d-i (anton) - post reboot network configuration (cjwatson) - - real deb from archdetect udeb (luther) - integrate selinux installation into the installer, for a painless install (joeyh/manoj?) - add a xen server task (joeyh)
Bug#760874: openjpeg2
Control: reassign -1 src:openjpeg2 Control: affects -1 src:openjpeg openjpeg2 should superseed openjpeg at some point, but breaks the old 1.x API. I need to check what is the best course of actions to: 1. Provide the full tools from openjpeg2 2. Do not conflict with openjpeg 1.x (the main API in use still) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761135: archdetect: package rename/package-type change breaks d-i builds
Petter Reinholdtsen p...@hungry.com (2014-09-11): [Cyril Brulebois] Of course a failing d-i build means src:debian-installer FTBFS. What else would that be? Thanks for asking. To me, it could also mean a failing to build a ISO with d-i udebs on it. But I had already tested ISO builds, and thus was a bit unsure what was failing for you. That might be some kind of language barrier issue as you mentioned, but when I write “d-i build”, it's really about building d-i. If I want to talk about a cd/dvd/iso build, I write “cd/dvd/iso build”. Please explain how you managed to build installation images with a failing d-i build. The ISO build system understand and handle the provides header, and the ISO build is working as before the deb was introduced, as can be seen on for example URL: http://lists.alioth.debian.org/pipermail/debian-edu-commits/2014-September/008537.html . ACK. I'm not sure why you're insisting on the renaming. Please explain why you did that (see my first follow-up). Somehow I get the impression that you do not really want to understand why I did this change but just want a set of arguments to brush off before reverting it, but I hope it is just a language barrier issue. Certainly a communication problem somwhere since I'm asking about the *renaming* part, and you're talking about the whole changeset. Anyway, here are the explanation why I introduced a archdetect deb and how the change have been tested so far. * A archdetect deb allow users on installed systems to figure out which kernel the installer want to install on a given machine. * The need for a normal deb for archdetect have been on the TODO list for years, see for example debian-installer/doc/TODO listing this entry in the Post-etch goals list: - real deb from archdetect udeb (luther) This is the part I'm talking about: ,--- | * The deb was already present in Ubuntu, under the name | archdetect-deb. Adding the deb in Debian can reduce the diff with | Ubuntu. | * We normally in Debian name udebs with a -udeb postfix, and name | packages after the binary they contain. Diverting from this common | naming scheme should be avoided. This I decided to use the | sensible name for the deb in Debian, and switch the udeb to have | the name we commonly use for udebs in debian, package-udeb. `--- * I knew d-i (anna-install and the rest of the d-i installation system) would handle the provides header, and tested this on a fresh install in a virtual machine before commiting the change. * I checked how many udebs were depending on archdetect (6, if I recall correctly), and new they would cope just fine with the change. * Knew the Debian archive would handle the rename, as udebs and debs have different name spaces, and we use the provides method with several library udebs already. So the change was tested and the installer was working as it should also after the rename. The only thing I didn't test was building the debian-installer source package itself, which broke as you correctly observed. The simple fix is to replace archdetect with archdetect-udeb, but a more proper fix is probably to teach the build of d-i initrds to understand the provides header, to ensure similar issues do not arise in the future. I disagree that reusing package names across package types is a nice thing to do. I very strongly disagree that it's OK to try that when we're close to the freeze (and not at the very beginning of the release cycle, where it hurts less to upload disruptive changes). As I already mentioned, you had been told in advance more stuff would have to be adjusted! Sticking to naming schemes is nice, but that certainly shouldn't be a reason for renaming packages and generating more work! You could look at the file you modified: | # These udebs will be needed on nearly every image. Include this file | # to get them. | busybox-udeb | anna | archdetect | cdebconf-udeb | cdebconf-priority | di-utils | di-utils-reboot | di-utils-shell | libdebconfclient0-udeb | libdebian-installer4-udeb | libnss-dns-udeb | lowmemcheck | main-menu | rootskel | udpkg | rescue-check | env-preseed | pciutils-udeb | | #include udev | | libkmod2-udeb [linux] | kldutils-udeb [kfreebsd] *-udeb really isn't mandatory in any way! So yes, I reverted these changes since renaming is unwarranted, already broke things, and might break others; I'm not interested in dealing with possible fallouts due to cosmetics. KiBi. signature.asc Description: Digital signature
Processed: openjpeg2
Processing control commands: reassign -1 src:openjpeg2 Bug #760874 [src:openjpeg] openjpeg: some binary packages conflict with openjpeg2 Bug reassigned from package 'src:openjpeg' to 'src:openjpeg2'. No longer marked as found in versions openjpeg/1.5.2-2. Ignoring request to alter fixed versions of bug #760874 to the same values previously set affects -1 src:openjpeg Bug #760874 [src:openjpeg2] openjpeg: some binary packages conflict with openjpeg2 Added indication that 760874 affects src:openjpeg -- 760874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760874 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#761109: marked as done (python-xstatic-d3: not installable in sid)
Your message dated Thu, 11 Sep 2014 07:49:26 + with message-id e1xrz8a-00026x...@franck.debian.org and subject line Bug#761109: fixed in python-xstatic-d3 3.4.11-1 has caused the Debian Bug report #761109, regarding python-xstatic-d3: not installable in sid 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.) -- 761109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-xstatic-d3 Affects: python3-xstatic-d3 Version: 3.4.9-3 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hello, python-xstatic-d3 is currently not installable in sid since it depends on libjs-d3 ( 3.4.10). However, we have libjs-ds version 3.4.11-1 in sid since 2014-08-23. The same holds for the python3-xstatic-d3 package in the same source package. The dependency is hard-coded in debian/control. Cheers -Ralf. ---End Message--- ---BeginMessage--- Source: python-xstatic-d3 Source-Version: 3.4.11-1 We believe that the bug you reported is fixed in the latest version of python-xstatic-d3, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-xstatic-d3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Sep 2014 07:35:11 + Source: python-xstatic-d3 Binary: python-xstatic-d3 python3-xstatic-d3 Architecture: source all Version: 3.4.11-1 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-xstatic-d3 - D3 JS XStatic support - Python 2.x python3-xstatic-d3 - D3 JS XStatic support - Python 3.x Closes: 761109 Changes: python-xstatic-d3 (3.4.11-1) unstable; urgency=medium . * New package to match the new version of libjs-d3. (Closes: #761109). Checksums-Sha1: e6f9e662754ceb078a412fc6a616df1d01f81cc9 2194 python-xstatic-d3_3.4.11-1.dsc 77875e55a74d20d5ddb802817cf4e65adb3f7815 56556 python-xstatic-d3_3.4.11.orig.tar.xz 358901c634314188c18f646877d7aaae8c8d5052 3832 python-xstatic-d3_3.4.11-1.debian.tar.xz 9930f21fd0eae89fa5a94e40d4c4734779496d73 5344 python-xstatic-d3_3.4.11-1_all.deb e03905a11ef5ccd69c556385d8d0bc885b556ad5 5220 python3-xstatic-d3_3.4.11-1_all.deb Checksums-Sha256: 58f8952f85db3769f6c690bb20157736f02ff24dafef9a6687f5df90e9720635 2194 python-xstatic-d3_3.4.11-1.dsc d6204c43f7ba96e3545e21da9ae8304b85518341b76522c7bec9a9a778f5b46c 56556 python-xstatic-d3_3.4.11.orig.tar.xz a7448732dd55f40ec631efef91fdc077af2cfba7d668b240ce4a89e88abaa63a 3832 python-xstatic-d3_3.4.11-1.debian.tar.xz 292458d11dc03094419bd4b1d1a46562ed2fe9980a312983b422c7eb9e94ed4a 5344 python-xstatic-d3_3.4.11-1_all.deb 7f5f55585115796afe00455bf91298aec4ea1bccd4278b38e01303aa3548f8ec 5220 python3-xstatic-d3_3.4.11-1_all.deb Files: a813be8b2a9cdf4afb99dd5fb9266fde 5344 python optional python-xstatic-d3_3.4.11-1_all.deb b2af70efa54217efa39aa546daa93fdc 5220 python optional python3-xstatic-d3_3.4.11-1_all.deb 438fec1e1276c159ea32c2c61cade4bb 2194 python optional python-xstatic-d3_3.4.11-1.dsc 7de67662b867f831b17086ad73e3a1fd 56556 python optional python-xstatic-d3_3.4.11.orig.tar.xz 9fdc85f7cf751f0a721f5dc6686380e5 3832 python optional python-xstatic-d3_3.4.11-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUEVE1AAoJENQWrRWsa0P+yxIP/R2L7xyQjgu3uNa76Dx3KYDu JublxQXcaw+xb9F/+QvT8p2XRPXPTjxvabr+lHCnUmgTc8ywrRSFpHEQtu8fcXhv 9ERV9hWkSE7KH9fdFK/F5wAoHObiH41Z8VxfA/jbm9YCJR9B8SR6sJQLx+kTRoPC IYbGeYbq2051yvR47lKY9eksR7QY0vBX9gIzm4CaI/fkushfTAyKhV8GmQx3qWeV V0sz94pv7jkGqW8D6wNdL0xvCAcTtamdHljnPy2N4nzJJl0ZWJX8bJqD8ZhdhonO nQM/XMQV/YeM7Q9Z2mrSC3E75tRf7cx1rHAfoUFc/ty7fv/bYM6eZnSeCp/1cGWP CnXZKI6vYXJ2c1vkog8PVx11zqX1wAphL6wxzm4DzZFspimluCr30NBEe7zX5pNl 8n3xU3Gx9GzEf6BzTgd/fceQl+kW+Rn2wrODANV/cq2xl27fLUZBzjuAFePDM2wM iIrBBYaFx+gcduv49YKPD+LChAPpuiiq73dS1biWru85bXyuVst1d9cHHrTKTkrA YznPSiP/ckFl4lucgfGnd9nFUKx1qpFAJxMoy9qPt3fz3EpTmj7h9Vu7orBj4bur
Bug#761107: marked as done (python-xstatic-angular-mock: not installable in sid)
Your message dated Thu, 11 Sep 2014 07:49:18 + with message-id e1xrz82-00023t...@franck.debian.org and subject line Bug#761107: fixed in python-xstatic-angular-mock 1.2.23.1-1 has caused the Debian Bug report #761107, regarding python-xstatic-angular-mock: not installable in sid 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.) -- 761107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-xstatic-angular-mock Affects: python3-xstatic-angular-mock Version: 1.2.16.1-2 Severity: serious User: trei...@debian.org Usertags: edos-outdated Hello, (I think this is the last bug report of this kind for the moment :-) python-xstatic-angular-mock is currently not installable in sid since it depends on libjs-angularjs ( 1.2.17). However, we have libjs-angularjs version 1.2.23-1 in sid since 2014-08-23. The same holds for the python3-xstatic-angular-mock package in the same source package. The dependency is hard-coded in debian/control. Cheers -Ralf. ---End Message--- ---BeginMessage--- Source: python-xstatic-angular-mock Source-Version: 1.2.23.1-1 We believe that the bug you reported is fixed in the latest version of python-xstatic-angular-mock, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-xstatic-angular-mock package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Sep 2014 06:55:44 + Source: python-xstatic-angular-mock Binary: python-xstatic-angular-mock python3-xstatic-angular-mock Architecture: source all Version: 1.2.23.1-1 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-xstatic-angular-mock - Angular JS Mock XStatic support - Python 2.x python3-xstatic-angular-mock - Angular JS Mock XStatic support - Python 3.x Closes: 761107 Changes: python-xstatic-angular-mock (1.2.23.1-1) unstable; urgency=medium . * Producing new package as the libjs-angularjs package got updated. Thanks to Ralf Treinen trei...@free.fr for the bug report (Closes: #761107). Checksums-Sha1: 013e6a729096c254aa95a554f4e12455d31f6a40 2348 python-xstatic-angular-mock_1.2.23.1-1.dsc 950c891dacba18053bebf5941f23165e0574ec48 16740 python-xstatic-angular-mock_1.2.23.1.orig.tar.xz 724a1cc0969ed8a20f5bbfb1805f76f2cbb3d322 3632 python-xstatic-angular-mock_1.2.23.1-1.debian.tar.xz b7eb3dce39c44b9787a0f245d3246365027bcda2 20024 python-xstatic-angular-mock_1.2.23.1-1_all.deb d3467a5b372f3e3a058a095f5e611bf9c664806b 19934 python3-xstatic-angular-mock_1.2.23.1-1_all.deb Checksums-Sha256: 03a50f4e72bca0e864dec4748931037028b873a6a5d5b7326cb229f44c68e07c 2348 python-xstatic-angular-mock_1.2.23.1-1.dsc db60353cb094a8987b9c8a2637bfb9257cdaa0be408b440fa7f065e4c5e84d3a 16740 python-xstatic-angular-mock_1.2.23.1.orig.tar.xz 694d92133f5660576a8698a1cce41dbad0a016a3c818427475a639a3cbc4cd79 3632 python-xstatic-angular-mock_1.2.23.1-1.debian.tar.xz 40c9eb4ae12e1a7a0eeca774a57b68f8bf20af4330a3ac219a77ca08e2a78a1a 20024 python-xstatic-angular-mock_1.2.23.1-1_all.deb c4ba75921589a5657737cfc6703328fe113c9b44d7ceabebe3d2248e6f96ad35 19934 python3-xstatic-angular-mock_1.2.23.1-1_all.deb Files: a4eea77ea1286ea65114e97e2defba5c 20024 python optional python-xstatic-angular-mock_1.2.23.1-1_all.deb 468b22e75da2b43a0b5de4a994197720 19934 python optional python3-xstatic-angular-mock_1.2.23.1-1_all.deb 8c2d4213c8b81629669a8f068e45a30f 2348 python optional python-xstatic-angular-mock_1.2.23.1-1.dsc 20b375ac0a85eecef329a58e95708fa0 16740 python optional python-xstatic-angular-mock_1.2.23.1.orig.tar.xz da0a9efb462bd4edbaaacc38a64a30e2 3632 python optional python-xstatic-angular-mock_1.2.23.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUEUgRAAoJENQWrRWsa0P+bdAQAISF67Mi+eyvLEYZT/7pOYYc AuybxeCj9BiaXr7OqlB8WIg69QNqu3u/dAwXT5N+QMUJK8Zuvek9Jy1Qk+CCBqcZ
Bug#761135: archdetect: package rename/package-type change breaks d-i builds
[Cyril Brulebois] I disagree that reusing package names across package types is a nice thing to do. I very strongly disagree that it's OK to try that when we're close to the freeze (and not at the very beginning of the release cycle, where it hurts less to upload disruptive changes). Given that udebs and debs have different name spaces, I do not see any problem myself with dropping a name from one namespace and introducing it in another, which is what I did when I renamed archdetect to archdetect-udeb in the udeb namespace and introduced the archdetect name into the deb namespace. The freeze is two months away. I understand you see the freeze as very close, while I see it as a bit further away. I fully respect your view about the urgenzy, even if I do not quite share it. I believe fixing the d-i build could have been done this week (for example by uploading a new debian-installer package without the kernel change), and was prepared to get any required fixes in place as soon as possible. As I already mentioned, you had been told in advance more stuff would have to be adjusted! I noticed you mentioned IRC messages I hadn't seen before you mentioned them here in the mail, so I guess they were said while I was away from IRC. I had tested the change, but simply forgot to check the debian-installer initrd build. I am still sorry about this. Sticking to naming schemes is nice, but that certainly shouldn't be a reason for renaming packages and generating more work! You could look at the file you modified: [...] *-udeb really isn't mandatory in any way! Sure, but it is used when there is a deb and an udeb. The common naming then is package for the deb name space and package-udeb for the udeb namespace. I did not check them all, but as far as I can tell, the examples without the '-udeb' ending do not have a package in the deb namespace. So yes, I reverted these changes since renaming is unwarranted, already broke things, and might break others; I'm not interested in dealing with possible fallouts due to cosmetics. My approach would have been to fix the remaining issues and keep the archdetect and archdetect-udeb names, but I'm not starting competing for commits uploads over this and will try to find time for the fix after Jessie instead. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761135: archdetect: package rename/package-type change breaks d-i builds
Petter Reinholdtsen p...@hungry.com (2014-09-11): Given that udebs and debs have different name spaces, I do not see any problem myself with dropping a name from one namespace and introducing it in another, which is what I did when I renamed archdetect to archdetect-udeb in the udeb namespace and introduced the archdetect name into the deb namespace. Re-using package names has always been a pain, for users, for packages depending on them, for bug tracking purposes, for bisecting purposes (downloading older snapshots in an automated way, testing them), etc. This should be avoided. Always. Consistency with a naming scheme is not a reason good enough to outweigh the costs mentioned above. The freeze is two months away. I understand you see the freeze as very close, while I see it as a bit further away. I fully respect your view about the urgenzy, even if I do not quite share it. I believe fixing the d-i build could have been done this week (for example by uploading a new debian-installer package without the kernel change), and was prepared to get any required fixes in place as soon as possible. First thing first: I upload debian-installer only when it is needed, meaning we're targetting a release. Secondly, since the udeb change didn't reach testing, no, it wouldn't have worked. I know two months is a lot, somewhat. But there are many more important things to track already! So losing time, focus, and energy over such disruptive and avoidable changes is really not appreciated. As I already mentioned, you had been told in advance more stuff would have to be adjusted! I noticed you mentioned IRC messages I hadn't seen before you mentioned them here in the mail, so I guess they were said while I was away from IRC. No, you were in the middle of a conversation with Colin. I'm not going to copy/paste it because that'd be impolite, but you'll find it in your logs, 2014-09-09, around 10 UTC. Sticking to naming schemes is nice, but that certainly shouldn't be a reason for renaming packages and generating more work! You could look at the file you modified: [...] *-udeb really isn't mandatory in any way! Sure, but it is used when there is a deb and an udeb. The common naming then is package for the deb name space and package-udeb for the udeb namespace. I did not check them all, but as far as I can tell, the examples without the '-udeb' ending do not have a package in the deb namespace. That doesn't mean we have to enforce it. I'm pretty sure that someone 1. wanting to use archdetect 2. doing apt-get install archdetect can either press tab to try autocompletion, or use apt-cache search archdetect to discover the archdetect-deb package (if we ended up stealing this name from Ubuntu). So yes, I reverted these changes since renaming is unwarranted, already broke things, and might break others; I'm not interested in dealing with possible fallouts due to cosmetics. My approach would have been to fix the remaining issues and keep the archdetect and archdetect-udeb names, but I'm not starting competing for commits uploads over this and will try to find time for the fix after Jessie instead. Thanks. Mraw, KiBi. signature.asc Description: Digital signature
Bug#760769: subsurface: can't be installed due to missing libmarblewidget18
On 07/09/2014 19:39, Christoph Anton Mitterer wrote: Package: subsurface Version: 4.2-1.1 Severity: grave Justification: renders package unusable libmarblewidget18 is no longer in sid, and therefore the package can't be installed. yes, it seems that the libmarblewidget18 transition could have been managed better ... Please rebuild,... and also please move to unstable. I see no reason to have it in experimental only. Well, we had a reason. Subsurface 4.2 requires libgit2 and it was only available in experimental until last week. Cheers, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758839: contains non-free data
On 10-09-14 19:02, Stas wrote: I guess so, once you have your new release ready I'll try to upload an updated package that closes this bug as soon as work and real childs permit... :) Ok, I will make a new package tomorrow morning and post the link when ready. Here's the new 2.6.5 release with a sound file which now belongs to me :-) http://download.savannah.gnu.org/releases/childsplay/ Thanks for your fast replies and happy to see that e-mail missunderstandings have been solved. Greetings, Sergio -- Sergio Talens-Oliag s...@debian.org http://people.debian.org/~sto/ Key fingerprint = FA90 8E47 1AD3 7D7F 2363 D78F 821A EE0F D167 FBDF -- To unsubscribe, send mail to 758839-unsubscr...@bugs.debian.org. Regards, Stas Zytkiewicz -- Regards, Stas Zytkiewicz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759708: marked as done (imms: FTBFS against new audacious)
Your message dated Thu, 11 Sep 2014 09:19:52 + with message-id e1xs0xg-0005za...@franck.debian.org and subject line Bug#759708: fixed in imms 3.1.0~svn301-3.1 has caused the Debian Bug report #759708, regarding imms: FTBFS against new audacious 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.) -- 759708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: imms Version: 3.1.0~svn301-3 Severity: serious Your package FTBFS against new libaudcore from the new audacious, see https://buildd.debian.org/status/fetch.php?pkg=immsarch=amd64ver=3.1.0~svn301-3%2Bb1stamp=1409239333 Emilio ---End Message--- ---BeginMessage--- Source: imms Source-Version: 3.1.0~svn301-3.1 We believe that the bug you reported is fixed in the latest version of imms, 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 759...@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 imms 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, 10 Sep 2014 10:55:50 +0200 Source: imms Binary: imms-common imms-audacious Architecture: source amd64 Version: 3.1.0~svn301-3.1 Distribution: unstable Urgency: medium Maintainer: Artur R. Czechowski artu...@hell.pl Changed-By: Sebastian Ramacher sramac...@debian.org Description: imms-audacious - Unobtrusive, automatic, and learning audacious playlist manager imms-common - Unobtrusive, automatic, and learning playlist manager Closes: 759708 Changes: imms (3.1.0~svn301-3.1) unstable; urgency=medium . * Non-maintainer upload. * debian/control: - Add Build-Depends on libaudclient-dev which is now separate from audacious-dev. (Closes: #759708) - Tighten audacious-dev in Build-Depens to (= 3.5) to ensure that plugin_dir variable in the pkg-config file is available. * debian/rules: Use plugin_dir variable to determine plugin directory. Checksums-Sha1: f4eb9adc066126f4e1c137773b3446e9f80d358b 2048 imms_3.1.0~svn301-3.1.dsc 2a61be55883666ecec449fc86b3cb68920ef09cc 15024 imms_3.1.0~svn301-3.1.debian.tar.xz 8dbec6e51d59e16c2a9ddb6153ec16f25e953225 264110 imms-common_3.1.0~svn301-3.1_amd64.deb 6ee608201a9b02f07fc002cbe87cfa4617842c48 21374 imms-audacious_3.1.0~svn301-3.1_amd64.deb Checksums-Sha256: 1f491614a63c8567e2c7e01fdaf43dd5de6f45debd80227117147b4b9598aa63 2048 imms_3.1.0~svn301-3.1.dsc 205273b3165c7acf76a0cdad1f325a39e1157fd50dc27babd1c6cc2fc6a252ba 15024 imms_3.1.0~svn301-3.1.debian.tar.xz 208ed8e8fb45b2f598e490fcb2ebcc393050eec6509ab56378f8a87173b4223f 264110 imms-common_3.1.0~svn301-3.1_amd64.deb eb3b89ce60500df06bfcb2f1ae1e9c2da8f004ba613e10c0060cce6971c2a8e9 21374 imms-audacious_3.1.0~svn301-3.1_amd64.deb Files: 5b9367a1558af33d0d18a0889e12f951 264110 utils optional imms-common_3.1.0~svn301-3.1_amd64.deb 4ee51ed3dd644f053a28bb2936946092 21374 utils optional imms-audacious_3.1.0~svn301-3.1_amd64.deb f2a27a3241780d67d013cb830f16f060 2048 utils optional imms_3.1.0~svn301-3.1.dsc 262e90fec7da086b70e2a07131109e3e 15024 utils optional imms_3.1.0~svn301-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUEBPTAAoJEGny/FFupxmTyvoP/RLqreD5rBIPJmtck0D6eGJG sDe3heX5WNeWyKEtz55XhkHN55PcndXeN1DxDQRXSqN32GuxghSlTLYzv5AEWgMx 66KarNrlFNdWt0xUT4mTXXefCfAPkaEq24nRaMyIMLxuEo9LePHeB3LPCm38pBXf ZAE9TB/WwK52wHYMKvH1MzyCtPUNCpdRLXZhDiC45bQDTGQmxJ8bJxTP+UGnNorH j1J8BkK0N3GHB1O8z7T2OyLTwVu2VfoztcLj/Nrv1VTqxjGkngLb8ssdp6/mPTqM JZrwCX0bkrraf+rRvOrzuNNdXMqeL0ZlSM4yzVuhO7mOxqR2rNBg5R+RuGjTio6P ndJQ8v2jf8dVG28qlnIqCLTUTfsVCOBrZ3WeIdkUoTEiosMSbgakW/3wvlqx2fIu k/L5tYNiNgwIlvS3UKyE3z/WMWVlj178vi3Fh1dFdA9FjAlLFAo6LQULHEauSi4y f0jz9gJAqSHq/58Xy0r37Q27vMVZpbL0PPuWcclf2RZYsfAE4rtYzWVMBPlXSlUU Y0YqjHhW0NJH4GFoM8t/2bVNm5jLUI2AQ6aoEYhvRh2Mzvu9ZrfcHOkHh95VeSom lSXayom2a9gwRCf2ZdxRXiz0WtOz7t+SCeIJTNtVhqn0u2pICNw7hTwmG1TwnFI5 rJXkNXuNF7OQ+LsdSl7e =EZsa -END PGP SIGNATUREEnd Message---
Bug#754114: Bug#750557: pgadmin3: segmentation fault
Hi guys, I've just uploaded 1.20.0~beta1 to unstable. Could you check if you still see the pgadmin3 crashes there? It seems to work for me now. Packages on apt.postgresql.org should be available shortly in the *-pgdg-testing suites. Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#760769: marked as done (subsurface: can't be installed due to missing libmarblewidget18)
Your message dated Thu, 11 Sep 2014 09:34:50 + with message-id e1xs0ma-0001by...@franck.debian.org and subject line Bug#760769: fixed in subsurface 4.2-2 has caused the Debian Bug report #760769, regarding subsurface: can't be installed due to missing libmarblewidget18 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.) -- 760769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: subsurface Version: 4.2-1.1 Severity: grave Justification: renders package unusable libmarblewidget18 is no longer in sid, and therefore the package can't be installed. Please rebuild,... and also please move to unstable. I see no reason to have it in experimental only. Cheers, Chris. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages subsurface depends on: ii libc6 2.19-10 ii libdivecomputer0 0.4.2-1 ii libgcc11:4.9.1-12 ii libgit2-0 0.20.0-1 ii libmarblewidget18 4:4.13.3-2+b1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtwebkit4 2.3.2.dfsg-3 ii libsqlite3-0 3.8.6-1 ii libstdc++6 4.9.1-12 ii libxml22.9.1+dfsg1-4 ii libxslt1.1 1.1.28-2 ii libzip20.11.2-1.1 ii subsurface-data4.2-1.1 ii zlib1g 1:1.2.8.dfsg-2 subsurface recommends no packages. subsurface suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: subsurface Source-Version: 4.2-2 We believe that the bug you reported is fixed in the latest version of subsurface, 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 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru sylves...@debian.org (supplier of updated subsurface package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 04 Sep 2014 09:08:12 +0200 Source: subsurface Binary: subsurface subsurface-data Architecture: source amd64 all Version: 4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian running development group pkg-running-de...@lists.alioth.debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: subsurface - Logbook program for scuba divers subsurface-data - Shared data files for Subsurface Closes: 760769 Changes: subsurface (4.2-2) unstable; urgency=medium . * Now that libgit2 is in unstable, upload to unstable too (Closes: #760769) . [ Salvo 'LtWorf' Tomaselli ] * Backport MAX_PATH patch from upstream to build on Hurd * Updated debian/copyright to report the contact of the new upstream maintainer * Backport patch from upstream to add keywords in .desktop file to fix a lintian problem Checksums-Sha1: c589709d671bb089102d121ec32f83a5ac723226 2241 subsurface_4.2-2.dsc 8697649171eb9f93620227787776b99fe846b39c 87556 subsurface_4.2-2.debian.tar.xz 362af2bc3a9243fee26db689dd39a5cf252dea22 699880 subsurface_4.2-2_amd64.deb 19914850ec6897834d73813d1f1702045e17c642 2578170 subsurface-data_4.2-2_all.deb Checksums-Sha256: 13ed32fe914b83015dae38d6ddce054dfa717714dcb3e2548adf0395eb8d6aa7 2241 subsurface_4.2-2.dsc 97997747a2f9f82990cc47d7881fa5fe0773c2c0ea3f2f99b51c4fca132fcaeb 87556 subsurface_4.2-2.debian.tar.xz 4cfa165b1dd13ecbbdc55a493f9dfdabb13fff2624043a6b2ae2186ff1bfdb2b 699880 subsurface_4.2-2_amd64.deb 0a1fdc1943c3c3ebcebc637da235054ce28d3638f31332257a2e00498b483703 2578170 subsurface-data_4.2-2_all.deb Files: 294b0dea8613d35f6d1c272ace28cb5e 699880 utils optional subsurface_4.2-2_amd64.deb 4fd978cbeb54b06fa9cd00b890923205 2578170 utils optional subsurface-data_4.2-2_all.deb c716ac915f4cb3ca5259f0b95edaf734 2241 utils optional subsurface_4.2-2.dsc 60ebb2803b148c9a9122d6ed3236082c
Bug#754114: Bug#750557: pgadmin3: segmentation fault
On Thursday 11 September 2014 11:31:44 Christoph Berg wrote: Hi guys, I've just uploaded 1.20.0~beta1 to unstable. Could you check if you still see the pgadmin3 crashes there? It seems to work for me now. Packages on apt.postgresql.org should be available shortly in the *-pgdg-testing suites. Christoph Hi, updated and tested, but no joy ;-(. Check http://paste.kde.org/pnrcj16nt BogDan. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761135: marked as done (archdetect: package rename/package-type change breaks d-i builds)
Your message dated Thu, 11 Sep 2014 10:00:10 + with message-id e1xs1ag-0001wv...@franck.debian.org and subject line Bug#761135: fixed in hw-detect 1.102 has caused the Debian Bug report #761135, regarding archdetect: package rename/package-type change breaks d-i builds 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.) -- 761135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: archdetect Version: 1.100.0.exp.1 Severity: grave Justification: renders package unusable Petter, I'm not sure why you thought it would be a good idea to mix renaming and reusing udeb/deb package name, but one thing is pretty clear: you never tested a d-i build using those udebs. You would have otherwise noticed the mess you created. I'm not even going to ask about runtime tests… Please unbreak! KiBi. ---End Message--- ---BeginMessage--- Source: hw-detect Source-Version: 1.102 We believe that the bug you reported is fixed in the latest version of hw-detect, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois k...@debian.org (supplier of updated hw-detect package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Sep 2014 08:32:43 +0200 Source: hw-detect Binary: hw-detect ethdetect disk-detect driver-injection-disk-detect archdetect Architecture: source amd64 all Version: 1.102 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Cyril Brulebois k...@debian.org Description: archdetect - Hardware architecture detector (udeb) disk-detect - Detect disk drives (udeb) driver-injection-disk-detect - Detect OEM driver injection disks (udeb) ethdetect - Detect network hardware and load kernel drivers for it (udeb) hw-detect - Detect hardware and load kernel drivers for it (udeb) Closes: 761135 Changes: hw-detect (1.102) unstable; urgency=low . * Revert the archdetect vs. archdetect-udeb change (Closes: #761135). Reasons include: - Disruptive changes are not welcome so late in the release cycle (especially when little to nothing has to be gained). - No tests have been performed, since debian-installer starts failing to build from source. - Reusing a package name for a different package-type is a recipe for disaster. Checksums-Sha1: 674148bf3d429020f19d3e02d681c5ee06eda75b 2034 hw-detect_1.102.dsc ae94c3f9baa9222a164cfc1f6943053c2ce8cf99 179444 hw-detect_1.102.tar.xz b253df868deccb69f4e2f1fcede13dcdf9724587 128302 hw-detect_1.102_amd64.udeb 70e8c02a4d4b020555a22d5418d52e123fee3a50 36076 ethdetect_1.102_all.udeb 5a0289a768919d61cce5d0104f616cc7518224ca 27648 disk-detect_1.102_all.udeb 8eae703d8b2a5ac1ba10743a19a55f8dbd6e080c 15146 driver-injection-disk-detect_1.102_all.udeb 48d3691762a9cee908dc9bb49187e1db068e9aa5 2414 archdetect_1.102_amd64.udeb Checksums-Sha256: 3a3854867ade4052b6d5faa6fed80361d5b3c15fc0d35448142b4d5059ae1c86 2034 hw-detect_1.102.dsc 1280cbab6c430d2cd3958ef5eb5901d9c1efdaa448d6edba96d8dcb8e2779de9 179444 hw-detect_1.102.tar.xz bc4bdc8f393c28b330b90dbdd5699a519bd2a93a14929de4ad40b4b77cb5ec46 128302 hw-detect_1.102_amd64.udeb 7feafa832e6aa5424e87b5e6ba1fbf950b1438f19a719f54cc1b476865d23629 36076 ethdetect_1.102_all.udeb 9f737c85c18ee94399f469622bf3f1a5d8f78d054465713426cae60251f828bc 27648 disk-detect_1.102_all.udeb db0789415ae7f2445bd44c58c9c17f89b844ac31467c6d80403a73ae1c87bc30 15146 driver-injection-disk-detect_1.102_all.udeb 07cc785d56d366296f807b78384900d9d6324a5f95eba2a07f47257d13bf0dbd 2414 archdetect_1.102_amd64.udeb Files: 27b79e02d7e0a97938ea57f66b264f5a 128302 debian-installer standard hw-detect_1.102_amd64.udeb 9e4c4092042b7cd81bd97c10c7711669 36076 debian-installer optional ethdetect_1.102_all.udeb 395ab4c2122d029cc1d2a22f1b2a6c1c 27648 debian-installer optional disk-detect_1.102_all.udeb 9f58bdff7d2c5bd1bf50d37e3bbd9fe7 15146 debian-installer optional driver-injection-disk-detect_1.102_all.udeb
Bug#759940: marked as done (ganglia: FTBFS: make[3]: *** No rule to make target 'gmetad.service.in', needed by 'gmetad.service'. Stop.)
Your message dated Thu, 11 Sep 2014 10:19:08 + with message-id e1xs1t2-0008hf...@franck.debian.org and subject line Bug#759940: fixed in ganglia 3.6.0-3 has caused the Debian Bug report #759940, regarding ganglia: FTBFS: make[3]: *** No rule to make target 'gmetad.service.in', needed by 'gmetad.service'. Stop. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ganglia Version: 3.6.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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[3]: Entering directory '/«PKGBUILDDIR»/gmetad' x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -D_FORTIFY_SOURCE=2 -I../lib -I../gmond -I../include -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -Wall -D_REENTRANT -MT gmetad.o -MD -MP -MF .deps/gmetad.Tpo -c -o gmetad.o gmetad.c gmetad.c: In function 'main': gmetad.c:286:15: warning: variable 'last_metadata' set but not used [-Wunused-but-set-variable] apr_time_t last_metadata; ^ mv -f .deps/gmetad.Tpo .deps/gmetad.Po ../scripts/fixconfig cmdline.c.in x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -D_FORTIFY_SOURCE=2 -I../lib -I../gmond -I../include -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -Wall -D_REENTRANT -MT cmdline.o -MD -MP -MF .deps/cmdline.Tpo -c -o cmdline.o cmdline.c cmdline.c: In function 'cmdline_parser_internal': cmdline.c:444:7: warning: variable 'check_required' set but not used [-Wunused-but-set-variable] int check_required; ^ mv -f .deps/cmdline.Tpo .deps/cmdline.Po x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -D_FORTIFY_SOURCE=2 -I../lib -I../gmond -I../include -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -Wall -D_REENTRANT -MT data_thread.o -MD -MP -MF .deps/data_thread.Tpo -c -o data_thread.o data_thread.c mv -f .deps/data_thread.Tpo .deps/data_thread.Po x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -D_FORTIFY_SOURCE=2 -I../lib -I../gmond -I../include -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -Wall -D_REENTRANT -MT server.o -MD -MP -MF .deps/server.Tpo -c -o server.o server.c mv -f .deps/server.Tpo .deps/server.Po x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -D_FORTIFY_SOURCE=2 -I../lib -I../gmond -I../include -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -Wall -D_REENTRANT -MT process_xml.o -MD -MP -MF .deps/process_xml.Tpo -c -o process_xml.o process_xml.c process_xml.c: In function 'startElement_METRIC': process_xml.c:590:17: warning: variable 'carbon_ret' set but not used [-Wunused-but-set-variable] int i, edge, carbon_ret; ^ process_xml.c: In function 'start': process_xml.c:1011:8: warning: variable 'rc' set but not used [-Wunused-but-set-variable] int rc; ^ process_xml.c: In function 'end': process_xml.c:1221:8: warning: variable 'rc' set but not used [-Wunused-but-set-variable] int rc; ^ mv -f .deps/process_xml.Tpo .deps/process_xml.Po x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -D_FORTIFY_SOURCE=2 -I../lib -I../gmond -I../include -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -Wall -D_REENTRANT -MT rrd_helpers.o -MD -MP -MF .deps/rrd_helpers.Tpo -c -o rrd_helpers.o rrd_helpers.c mv -f .deps/rrd_helpers.Tpo .deps/rrd_helpers.Po x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -D_FORTIFY_SOURCE=2 -I../lib -I../gmond -I../include -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat
Bug#760903: marked as done (RM: drbd8 -- ROM; source package renamed to drbd-utils)
Your message dated Thu, 11 Sep 2014 10:28:18 + with message-id e1xs1bu-0003ib...@franck.debian.org and subject line Bug#760903: Removed package(s) from unstable has caused the Debian Bug report #760903, regarding RM: drbd8 -- ROM; source package renamed to drbd-utils to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:drbd8 Version: 2:8.4.4-1 Severity: serious drbd8-utils is built (in different versions) by both src:drbd8 and src:drbd-utils. The source package drbd8 should probably be removed for the archive as it has the lower version. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: drbd8 | 2:8.4.4-1 | source drbd8-utils | 2:8.4.4-1 | armel, armhf, i386, mips, mipsel, powerpc, s390x, sparc --- Reason --- ROM; source package renamed to drbd-utils -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 760...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/760903 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#761135: archdetect: package rename/package-type change breaks d-i builds
On Thu, Sep 11, 2014 at 09:33:13AM +0200, Cyril Brulebois wrote: I disagree that reusing package names across package types is a nice thing to do. I very strongly disagree that it's OK to try that when we're close to the freeze (and not at the very beginning of the release cycle, where it hurts less to upload disruptive changes). So, I think the best way to handle this longer-term would be: * upload hw-detect with a transitional package archdetect (Package-Type: udeb) Depends: archdetect-udeb * make sure everything copes well with that * at some later point (e.g. in jessie+1) introduce archdetect as a .deb I would like to have archdetect as a .deb; the archdetect-deb name I made up a while back in Ubuntu sucks and I wouldn't like to perpetuate it; I don't think there's a fundamental problem with reusing package names across package types, but in cases like this where it has coordination issues we should make some effort to smooth the transition rather than just going straight for it. -- 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
Bug#754114: Bug#750557: pgadmin3: segmentation fault
Le 11.09.2014 11:43, Bogdan Vatra a écrit : On Thursday 11 September 2014 11:31:44 Christoph Berg wrote: Hi guys, I've just uploaded 1.20.0~beta1 to unstable. Could you check if you still see the pgadmin3 crashes there? It seems to work for me now. Packages on apt.postgresql.org should be available shortly in the *-pgdg-testing suites. Christoph Hi, updated and tested, but no joy ;-(. Check http://paste.kde.org/pnrcj16nt BogDan. Same here, still segfaulting after right clicks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736066: Allow encfs into jessie?
Hi, due to bug #736066, encfs was removed from jessie. I'd think it would be better to allow encfs into jessie for the following reasons: The bug report is about security issues, but these are not security issues of the software (as in: you can somehow hack into the computer wich is running the software), but of the encryption algorithms used. So it can be compared to a package implementing md5: Yes, it's known that md5 is not secure any more, but that's not a reason to remove all packages implementing md5 from debian. One could argue that encfs shouldn't be used any longer to encrypt files, and therefore encfs is just not useful and can be removed. But many users will have legacy installations using encfs encrypted file systems, and will be surprised that they can't access them any more from jessie. So removing encfs will cause major inconveniences to some of our users. Therefore, I propose that encfs should be allowed into jessie. (What would be the right way to do that? Lower the severtiy of the bug? Add a jessie-ignore tag?) To notify users about the potential security issue, a NEWS file could be added, or one could add a warning to the output of the encfs command. Regards, Jan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761171: wagon2 fails to build in a non networked environment
Package: src:wagon2 Version: 2.6-1 Severity: serious Tags: sid jessie the tests fail without network access: [...] T E S T S --- Running org.apache.maven.wagon.providers.http.HugeFileDownloadTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.61 sec Running org.apache.maven.wagon.providers.http.HttpClientWagonTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.maven.wagon.providers.http.AbstractHttpClientWagonTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.052 sec FAILURE! Results : Tests in error: test(org.apache.maven.wagon.providers.http.AbstractHttpClientWagonTest): repo.maven.apache.org: Name or service not known Tests run: 6, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [...] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761172: libitext5-java tests fail in a non networked environment
Package: src:libitext5-java Version: 5.5.0-1 Severity: serious Tags: sid jessie causing a build failure. [...] Results : Tests in error: remoteGifTest(com.itextpdf.text.RemoteGifImageTest): itextpdf.com Tests run: 210, Failures: 0, Errors: 1, Skipped: 4 [...] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759939: makepp: FTBFS: tests failed
Hi everyone, I can reproduce the failure and confirmed that tests succeed with the new upstream release, which I'll upload shortly. Thanks, Max -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759838: padre: FTBFS: 16:52:40: Error: locale 'en_GB' cannot be set.
On Wed, 10 Sep 2014 13:51:41 +0200 Dominique Dumont d...@debian.org wrote: Looks like URI behavior was changed, but I cannot find any change in URI that might explain this. I'll check with padre upstream. Sorry. I was wrong. URI is fine. Padre::Browser::PseudoPerldoc is broken. This class does: # Even worse than monkey patching , copy paste [process sub] from Pod::Perldoc w/ edits # to avoid untrappable calls to 'exit' My gut feeling is that this test broke with perl 5.20 The help browser (F2 key) is no longer working on my system. All the best -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761174: plplot: FTBFS on kfreebsd-i386 reproducibly
Source: plplot Version: 5.10.0-0.1 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Hi, plplot FTBFS on kfreebsd-i386 (only) due to missing/broken ada compiler: https://buildd.debian.org/status/logs.php?pkg=plplotver=5.10.0-0.1arch=kfreebsd-i386 I was able to reproduce the issue in the sid chroot on fischer.debian.org. I noticed the following in the build log: -- WARNING: no working Ada compiler so disabling Ada bindings and examples. This is consistent with files missing to include in the built ada packages. There are tons of Ada warnings in the lines before that one. They are also in the build logs on buildd.debian.org linked above: -- Check for working Ada builder: /usr/bin/gnatmake -- Check for working Ada builder: /usr/bin/gnatmake -- broken CMake Error at /«PKGBUILDDIR»/cmake/modules/language_support/cmake/CMakeTestAdaCompiler.cmake:48 (MESSAGE): The Ada builder /usr/bin/gnatmake is not able to compile, bind, and link a simple test program. It fails with the following output: Change Dir: /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp Run Build Command:/usr/bin/make make[1]: Entering directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' /usr/bin/cmake -H/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp -B/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp/CMakeFiles /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp/CMakeFiles/progress.marks /usr/bin/make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/testadacompiler.dir/build.make CMakeFiles/testadacompiler.dir/depend make[3]: Entering directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' cd /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp /usr/bin/cmake -E cmake_depends Unix Makefiles /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp/CMakeFiles/testadacompiler.dir/DependInfo.cmake Scanning dependencies of target testadacompiler make[3]: Leaving directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/testadacompiler.dir/build.make CMakeFiles/testadacompiler.dir/build make[3]: Entering directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp/CMakeFiles 1 [100%] Building Ada object CMakeFiles/testadacompiler.dir/testadacompiler.o /usr/bin/gnatgcc -c /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp/testadacompiler.adb -o CMakeFiles/testadacompiler.dir/testadacompiler.o gnatgcc: error trying to exec 'gnat1': execvp: No such file or directory CMakeFiles/testadacompiler.dir/build.make:57: recipe for target 'CMakeFiles/testadacompiler.dir/testadacompiler.o' failed make[3]: *** [CMakeFiles/testadacompiler.dir/testadacompiler.o] Error 1 make[3]: Leaving directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' CMakeFiles/Makefile2:63: recipe for target 'CMakeFiles/testadacompiler.dir/all' failed make[2]: *** [CMakeFiles/testadacompiler.dir/all] Error 2 make[2]: Leaving directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' Makefile:75: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeTmp' CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:33 (enable_language) -- Configuring incomplete, errors occurred! See also /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeOutput.log. See also /«PKGBUILDDIR»/debian/build_tmp/language_tests/Ada/CMakeFiles/CMakeError.log. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (400, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15-trunk-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to
Processed: #759691 is fixed upstream
Processing commands for cont...@bugs.debian.org: tags 759691 fixed-upstream Bug #759691 [src:ck] ck: file ck_hclh is not cleaned by debian/rules clean Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 759691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759691 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#759939: marked as done (makepp: FTBFS: tests failed)
Your message dated Thu, 11 Sep 2014 12:19:45 + with message-id e1xs3ll-0005vl...@franck.debian.org and subject line Bug#759939: fixed in makepp 2.0.98.5-1 has caused the Debian Bug report #759939, regarding makepp: 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.) -- 759939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: makepp Version: 2.0.98.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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»' cd t PERL=/usr/bin/perl /usr/bin/perl run_tests.pl --hint passed aaasimple passed additional_dependencies passed build_cache This tests links and symbolic links, among other things. If your file system doesn't support either of these, you can try running this test with a workaround that consists in setting the environment variable MAKEPP_LN_CP to 1, 2 or 3. If you want to use the ln builtin later on, always set it. FAILED builtins: wrong file: /«PKGBUILDDIR»/t/builtins.log passed c_compilation passed changed_inputs passed conditionals passed directories passed dry_run_what_if passed esql passed extra_dependencies passed implicit_load passed include passed last_chance passed load_makefile passed log_graph passed loop passed make_makefile passed makeppreplay passed md5 passed only_targets passed parallel passed pattern_rule passed perl passed recursive_make passed recursive_rules passed recursive_variants passed repository passed rule_include passed signature passed special_chars_unix passed static_pattern passed target_specific passed variable_expansion passed variables_automatic passed verilog passed wildcard_repository Some failures, which possibly all have the same cause -- you are probably ok. In the /«PKGBUILDDIR»/t/ directory you will find details in the testname.log files and testname.failed directories. If you are trying to install from a makefile you configured, you need to touch .test_done in case you want to ignore the above failures. make[1]: *** [.test_done] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/makepp_2.0.98.3-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. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- Source: makepp Source-Version: 2.0.98.5-1 We believe that the bug you reported is fixed in the latest version of makepp, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Max Vozeler x...@debian.org (supplier of updated makepp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Sep 2014 11:05:12 +0200 Source: makepp Binary: makepp Architecture: source all Version: 2.0.98.5-1 Distribution: unstable Urgency: medium Maintainer: Max Vozeler x...@debian.org Changed-By: Max Vozeler x...@debian.org Description: makepp - GNU make compatible but reliable and simpler build tool Closes: 759939 Changes: makepp (2.0.98.5-1) unstable; urgency=medium . * New upstream release. - Fixes test failure (closes: #759939) * Fix pod2man syntax errors * Make Max the maintainer * Update to policy version 3.9.5 (no changes) Checksums-Sha1: 1151b1e411d3a3dac99c038814e150432d0d0b0c 1104 makepp_2.0.98.5-1.dsc b6088ec301feeec138060ce3d28ffc3f2cf31c0d 679356 makepp_2.0.98.5.orig.tar.gz
Processed: fixed
Processing commands for cont...@bugs.debian.org:
fixed 758051 6.3~svn681-4
Bug #758051 {Done: Daniel Pocock dan...@pocock.pro} [src:libphonenumber]
libphonenumber: FTBFS: invalid build-helper-maven-plugin version
Marked as fixed in versions libphonenumber/6.3~svn681-4.
End of message, stopping processing here.
Please contact me if you need assistance.
--
758051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758051
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#761174: plplot: FTBFS on kfreebsd-i386 reproducibly
On Thu, Sep 11, 2014 at 01:54:06PM +0200, Axel Beckert wrote: plplot FTBFS on kfreebsd-i386 (only) due to missing/broken ada compiler: https://buildd.debian.org/status/logs.php?pkg=plplotver=5.10.0-0.1arch=kfreebsd-i386 I was able to reproduce the issue in the sid chroot on fischer.debian.org. I noticed the following in the build log: -- WARNING: no working Ada compiler so disabling Ada bindings and examples. I notice popcon shows no installs at all of any sort for the plplot ada-related binary packages, so disabling them for all architectures (at least for jessie) may be a reasonable solution if this isn't easy to fix: https://qa.debian.org/popcon.php?package=plplot Not all users run popcon, but this does strongly suggest they aren't widely used currently. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761174: plplot: FTBFS on kfreebsd-i386 reproducibly
On 11/09/14 15:01, Olly Betts wrote: On Thu, Sep 11, 2014 at 01:54:06PM +0200, Axel Beckert wrote: plplot FTBFS on kfreebsd-i386 (only) due to missing/broken ada compiler: https://buildd.debian.org/status/logs.php?pkg=plplotver=5.10.0-0.1arch=kfreebsd-i386 I was able to reproduce the issue in the sid chroot on fischer.debian.org. I noticed the following in the build log: -- WARNING: no working Ada compiler so disabling Ada bindings and examples. I notice popcon shows no installs at all of any sort for the plplot ada-related binary packages, so disabling them for all architectures (at least for jessie) may be a reasonable solution if this isn't easy to fix: https://qa.debian.org/popcon.php?package=plplot Not all users run popcon, but this does strongly suggest they aren't widely used currently. This is probably a side-effect of #759407 which should be fixed. When that's fixed, plplot will probably build just fine on k-i. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 761174 with 759407
Processing commands for cont...@bugs.debian.org: block 761174 with 759407 Bug #761174 [src:plplot] plplot: FTBFS on kfreebsd-i386 reproducibly 761174 was not blocked by any bugs. 761174 was not blocking any bugs. Added blocking bug(s) of 761174: 759407 thanks Stopping processing here. Please contact me if you need assistance. -- 761174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761174 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#760366: gdm3: Stopped showing any users, no way to log in
Package: gdm3 Version: 3.12.2-4 Followup-For: Bug #760366 Dear Maintainer, same problem here. Since updating from gdm3 3.8.4-9 on the 3rd of September to 3.12.x there is no login-mask. I do have the debian-logo on both displays. On the main display I have the top-bar. It shows the day and time in the center and the symbols for accessibility, languge and LAN-speaker-shutdown. When opening the right-most dropdown i can adjust the volume, I see entries for wired and location and I have the shutdown-button (and it works). But I cannot log in. dmesg shows following messages: systemd-logind[2640]: Failed to start unit user@1000.service: Unknown unit: user@1000.service systemd-logind[2640]: Failed to start user service: Unknown unit: user@1000.service systemd-logind[2640]: New session 1 of user mots. systemd-logind[2640]: Failed to start unit user@0.service: Unknown unit: user@0.service systemd-logind[2640]: Failed to start user service: Unknown unit: user@0.service systemd-logind[2640]: New session 3 of user root. I found bug #724731: As suggested I checked libpam-systemd, it is installed. When switching to lightdm, as a workaround, I can login and everything seems to work (gnome3). But I would like to use gdm3. Updating to gdm3 3.12.2-4 (unstable) as reportbug suggested did not help. If I have to provide more details, I will gladly do. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3 ii adduser 3.113+nmu3 ii dconf-cli0.20.0-2 ii dconf-gsettings-backend 0.20.0-2 ii debconf [debconf-2.0]1.5.53 ii gir1.2-gdm3 3.12.2-4 ii gnome-session [x-session-manager]3.12.1-3 ii gnome-session-bin3.12.1-3 ii gnome-session-flashback [x-session-manager] 3.8.1-2 ii gnome-settings-daemon3.12.2-1+b1 ii gnome-shell 3.12.2-3 ii gnome-terminal [x-terminal-emulator] 3.12.3-2 ii gsettings-desktop-schemas3.12.2-1 ii libaccountsservice0 0.6.37-3 ii libaudit11:2.3.7-1 ii libc62.19-10 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-0 2.30.8-1 ii libgdm1 3.12.2-4 ii libglib2.0-0 2.40.0-5 ii libglib2.0-bin 2.40.0-5 ii libgtk-3-0 3.12.2-3+b1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam-systemd 208-8 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.3-2 ii libselinux1 2.3-2 ii libsystemd-daemon0 208-8 ii libsystemd-journal0 208-8 ii libsystemd-login0208-8 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp61:1.1.1-1 ii libxrandr2 2:1.4.2-1 ii lsb-base 4.1+Debian13 ii metacity [x-window-manager] 1:3.12.0-2 ii policykit-1 0.105-6.1 ii ucf 3.0030 ii x11-common 1:7.7+7 ii x11-xserver-utils7.7+3 ii xfce4-session [x-session-manager]4.10.1-8 ii xfce4-terminal [x-terminal-emulator] 0.6.3-1 ii xfwm4 [x-window-manager] 4.10.1-2 ii xterm [x-terminal-emulator] 310-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.12.0-2 ii desktop-base 7.0.3 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.0-2+b1 ii xserver-xorg 1:7.7+7 ii zenity 3.12.1-1.1 Versions of packages gdm3 suggests: ii gnome-orca3.12.2-1 ii libpam-gnome-keyring 3.12.2-1 -- Configuration Files: /etc/gdm3/Init/Default changed:
Processed: post-el: diff for NMU version 1:2.5-2.1
Processing control commands: tags 754039 + pending Bug #754039 [src:post-el] post-el: please switch to emacs24 Added tag(s) pending. -- 754039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754039 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#754039: post-el: diff for NMU version 1:2.5-2.1
Control: tags 754039 + pending
Hi,
I've prepared an NMU for post-el (versioned as 1:2.5-2.1) and uploaded
it to DELAYED/7. Please feel free to tell me if I should delay it
longer.
--
Matt
diff -u post-el-2.5/debian/changelog post-el-2.5/debian/changelog
--- post-el-2.5/debian/changelog
+++ post-el-2.5/debian/changelog
@@ -1,3 +1,10 @@
+post-el (1:2.5-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Depend on emacs instead of emacs23. (Closes: #754039)
+
+ -- Matt Kraai kr...@debian.org Thu, 11 Sep 2014 06:30:10 -0700
+
post-el (1:2.5-2) unstable; urgency=low
* post.el, debian/post-el.emacsen-startup: Fix for new mutt filename
diff -u post-el-2.5/debian/control post-el-2.5/debian/control
--- post-el-2.5/debian/control
+++ post-el-2.5/debian/control
@@ -10,7 +10,7 @@
Package: post-el
Architecture: all
-Depends: emacs23 | emacsen, ${misc:Depends}
+Depends: emacs | emacsen, ${misc:Depends}
Enhances: mutt, slrn
Suggests: emacs-goodies-el
Description: emacs major mode for editing mail
Processed (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org:
severity 720865 normal
Bug #720865 {Done: Friedrich Beckmann friedrich.beckm...@gmx.de} [src:pspp]
pspp: FTBFS with perl 5.18: test failures
Severity set to 'normal' from 'serious'
fixed 758088 0.8.3-2
Bug #758088 {Done: YunQiang Su wzss...@gmail.com} [pspp] pspp failed to run
test on mips64el
Marked as fixed in versions pspp/0.8.3-2.
reassign 758088 src:pspp
Bug #758088 {Done: YunQiang Su wzss...@gmail.com} [pspp] pspp failed to run
test on mips64el
Bug reassigned from package 'pspp' to 'src:pspp'.
No longer marked as found in versions pspp/0.7.9+git20120620-1.2.
No longer marked as fixed in versions pspp/0.8.3-2.
merge 720865 758088
Bug #720865 {Done: Friedrich Beckmann friedrich.beckm...@gmx.de} [src:pspp]
pspp: FTBFS with perl 5.18: test failures
Bug #758088 {Done: YunQiang Su wzss...@gmail.com} [src:pspp] pspp failed to
run test on mips64el
Marked as fixed in versions pspp/0.8.3-2.
Marked as found in versions pspp/0.7.9+git20120620-1.2.
Added tag(s) sid and jessie.
Bug #758088 {Done: YunQiang Su wzss...@gmail.com} [src:pspp] pspp failed to
run test on mips64el
Ignoring request to alter fixed versions of bug #758088 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #758088 {Done: YunQiang Su wzss...@gmail.com} [src:pspp] pspp failed to
run test on mips64el
Ignoring request to alter fixed versions of bug #758088 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #758088 {Done: YunQiang Su wzss...@gmail.com} [src:pspp] pspp failed to
run test on mips64el
Ignoring request to alter fixed versions of bug #758088 to the same values
previously set
After four attempts, the following changes were unable to be made:
fixed_versions of #758088 is 'pspp/0.8.3-2' not '0.8.3-2'
Failed to merge 720865: Unable to modify bugs so they could be merged.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
720865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720865
758088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758088
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#735453: [HELP] Can anybody try to upload libsbml (Was: Bug#735453: Changes to libsbml)
Hi Ivo,
[please always keep the bug report in CC since we are not just two
persons discussing private stuff]
On Thu, Sep 11, 2014 at 12:36:52PM +0200, Ivo Maintz wrote:
Andreas Tille ti...@debian.org schrieb :
The only idea I have why your successful built is not reproducible is
the fact that since we are working on the basis of a created
orig.tar.xz. Could you please confirm that you used
debian/rules get-orig-source
to create the orig.tar.xz and can you perhaps put this successful
tarball online somewhere to let us pick this one for another try?
Only to be shure, I just (re)did all steps, starting with
creating the tarball and including successful build the packages - no
problems so far :-(
However, here is _my_ tarball:
https://redult.goip.de/owncloud/public.php?service=filest=ad5ed796371fd80101357dc0930826d3
I realised significant differences between your any mine orig.tar.xz and
I'm to lazy to track the reasons down why some files in my tarball where
missing. I can confirm that the build works now (!!! :-)) but there is
some remaining issue:
E: libsbml5-perl: missing-dependency-on-perlapi
N:
N:This package includes a *.so file in /usr/lib/perl5, normally indicating
N:that it includes a binary Perl module. Binary Perl modules must depend
N:on perlapi-$Config{version} (from the Config module). If the package is
N:using debhelper, this problem is usually due to a missing dh_perl call
N:in debian/rules or a missing ${perl:Depends} substitution variable in
N:the Depends line in debian/control.
N:
N:Refer to Debian Perl Policy section 4.4.2 (Binary Modules) for details.
N:
N:Severity: serious, Certainty: certain
N:
N:Check: binaries, Type: binary, udeb
N:
Since we can not upload with a lintian error I'll take the following
action:
1. Upload source + build to my http://people.d.o space to enable
others reconstruct the build in a reproducible manner
2. Ask for help on debian-perl / debian-mentors list since I think
${perl:Depends} is properly set
If anybody might see the problem right now this would be great as well.
Kind regards
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#749365:
I have built this with the latest Oracle Java 8u20 JVM and the tests still randomly fail i.e. two out of three builds with Oracle Java 8 were successful. Which leads to two possible reasons for the failure: One of the build deps has been replaced with a later version and is causing the breakage. The last re-builds [un]luckily built successfully even though a sporadic test failure bug existed.
Bug#736066: Allow encfs into jessie?
Hallo, * Jan Niehusmann [Thu, Sep 11 2014, 12:12:08PM]: The bug report is about security issues, but these are not security issues of the software (as in: you can somehow hack into the computer wich is running the software), but of the encryption algorithms used. So it can be compared to a package implementing md5: Yes, it's known that md5 is not secure any more, but that's not a reason to remove all packages implementing md5 from debian. ... Therefore, I propose that encfs should be allowed into jessie. (What would be the right way to do that? Lower the severtiy of the bug? Add a jessie-ignore tag?) To notify users about the potential security issue, a NEWS file could be added, or one could add a warning to the output of the encfs command. In fact, that is what I considered as workaround, and even harder: add a debconf message with priority critical telling exactly those details. Unless someone cries out loudly I will continue with this plan in a couple of days. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr_GError(_GError*)'
On Tuesday 09 September 2014 19:27:11 Lisandro Damián Nicanor Pérez Meyer wrote: On Tuesday 09 September 2014 20:19:29 Steven Chamberlain wrote: Having touched Source/WTF/WTF.pri, I'm now stuck at this qmake error: cd Source/ make -f Makefile.QtWebKit qmake_all make[4]: Entering directory `«PKGBUILDDIR»/WebKitBuild/Release/Source' /usr/lib/x86_64-kfreebsd-gnu/qt5/bin/qmake «PKGBUILDDIR»/Source/api.pri CONFIG+=no_force_sse2 CONFIG+=release CONFIG-=debug CONFIG+=production_build -o Makefile.api Project ERROR: Module does not define version. Is it trying to regenerate makefiles because I've changed something they're generated from? But if I revert my change, it still does this. Does that imply some pre-existing problem in the build process... perhaps? *sad, confused* It's a quite hacked build system. I'll try in a clean build ASAP. I have also been pointed out that upstream might be able to take a look at this. Thanks *a lot* Steve for this :) Just set up a fresh VM with KFreeBSD-amd64 and using the previously suggested patch [1] worked for me to fix the build, see log [2]. Cheers, Andreas [1] http://homepages.upb.de/phoenixx/0001-Fix-build-on-KFreeBSD.patch [2] http://homepages.upb.de/phoenixx/kfreebsd-build.tar.gz PS: My setup slightly more verbose: * KFreeBSD installed from current Debian/SID to VirtualBox * got qtwebkit sources with apt-get source * applied patches with quilt push -a * used dpkg-buildpackage -b -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738515: marked as done (oath-toolkit: CVE-2013-7322: certain one-time-passwords not invalidated correctly)
Your message dated Thu, 11 Sep 2014 15:22:32 + with message-id e1xs6ce-0005ym...@franck.debian.org and subject line Bug#738515: fixed in oath-toolkit 2.4.1-1 has caused the Debian Bug report #738515, regarding oath-toolkit: CVE-2013-7322: certain one-time-passwords not invalidated correctly 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.) -- 738515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: oath-tookit Severity: grave Tags: security upstream Hi, the following vulnerability was published for oath-toolkit. It is to track the isse both in BTS and security tracker. CVE-2013-7322[0]: certain one-time-passwords not invalidated correctly A possible pach is found at [1]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] http://security-tracker.debian.org/tracker/CVE-2013-7322 [1] http://lists.nongnu.org/archive/html/oath-toolkit-help/2013-12/txtUm85v7Wqcy.txt Regards, Salvatore ---End Message--- ---BeginMessage--- Source: oath-toolkit Source-Version: 2.4.1-1 We believe that the bug you reported is fixed in the latest version of oath-toolkit, 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. Simon Josefsson si...@josefsson.org (supplier of updated oath-toolkit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Sep 2014 16:38:12 +0200 Source: oath-toolkit Binary: liboath-dev liboath0 oathtool oath-dbg libpam-oath Architecture: source Version: 2.4.1-1 Distribution: unstable Urgency: low Maintainer: OATH Toolkit Team oath-toolkit-h...@nongnu.org Changed-By: Simon Josefsson si...@josefsson.org Description: liboath-dev - Development files for the OATH Toolkit Liboath library liboath0 - OATH Toolkit Liboath library libpam-oath - OATH Toolkit libpam_oath PAM module oath-dbg - OATH Toolkit debugging symbols oathtool - OATH Toolkit oathtool command line tool Closes: 738515 744641 Changes: oath-toolkit (2.4.1-1) unstable; urgency=low . * New upstream release. - New symbols added. - Fixed CVE-2013-7322. Closes: #738515. - Disable PSKC builds until I found a sponsor. * Use dh-autoreconf. Closes: #744641. * Bump to Debian Policy version 3.9.5. * Add debian/upstream-signing-key.pgp and update watch file. Checksums-Sha1: 39c89812bca12ec0636b40fb3afdb064ef16a101 1880 oath-toolkit_2.4.1-1.dsc b0ca4c5f89c12c550f7227123c2f21f45b2bf969 4136649 oath-toolkit_2.4.1.orig.tar.gz 2168e75cb922af99cef24ad7c93bd4b415a71e55 15524 oath-toolkit_2.4.1-1.debian.tar.xz Checksums-Sha256: 534053d49d92c74b1270aaf8dafaf737245faa7632e770074c425bcc6880163a 1880 oath-toolkit_2.4.1-1.dsc 9bfa42cbc100eb6c43d2bf83e3badc51d9e6f4950a92e07513ae586d0c5e9b24 4136649 oath-toolkit_2.4.1.orig.tar.gz 688eacab2898d99966b1a505ec4277f1cfc4a923d286b1884d4bd0002b4224ae 15524 oath-toolkit_2.4.1-1.debian.tar.xz Files: 9c004a29c829521e6d9a1cb5c1aab0e5 1880 devel optional oath-toolkit_2.4.1-1.dsc 951bafd1d86e6013903c10be3b6623bb 4136649 devel optional oath-toolkit_2.4.1.orig.tar.gz 4f91ad6cb4a1e8153d34acd5acd4066b 15524 devel optional oath-toolkit_2.4.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUEboxAAoJEIYLf7sy+BGdVi0H/jChscvMDL/dls/lw4zgf4rZ FoOXW9dZBLUTNCwDp3ck7LVhvtLbZE11b5ski3OuCIj/WokSx/eyiqPWt19VQlzO T08XtfWQjDH6z+fVWjLPENF6CcHffrTJtxtyepzUdGqtzqsHRxwyr7GsxLtWvaBD do8AzCX0JmKFSDtE6IQyEi8sDVjr/pGvssMFxrcHjYQD+EHAMMAp9LRuhdr/pDll mGqfn42TJgjSbWAVaKa0sTppdb/b9cl6SGyIaoeG1xujA0l0dcYsvZVx5n8wceah mJdbuU6+RTPYDMZrqZk3EPHDjMN2s+7x3va+7Y1elp8r2eHcz70u6GTNETDw1Zc= =np95 -END PGP SIGNATUREEnd Message---
Bug#761193: libc++ fails to build on armel and armhf
Package: src:libc++
Version: 3.5-1
Severity: serious
Tags: sid jessie
the build system could also need some love to stop on errors.
make[1]: Entering directory '/build/libc++-_RtcTT/libc++-3.5'
cd libcxxabi/lib; ./buildit; ln -s libc++abi.so.1.0 libc++abi.so;\
ln -s libc++abi.so.1.0 libc++abi.so.1;
+ clang++ -c -g -O3 -fPIC -std=c++11 -stdlib=libc++ -fstrict-aliasing
-Wstrict-aliasing=2 -Wsign-conversion -Wshadow -Wconversion -Wunused-variable
-Wmissing-field-initializers -Wchar-subscripts -Wmismatched-tags
-Wmissing-braces -Wshorten-64-to-32 -Wsign-compare -Wstrict-aliasing=2
-Wstrict-overflow=4 -Wunused-parameter -Wnewline-eof -I../include
-I../../libcxx/include ../src/abort_message.cpp
+ clang++ -c -g -O3 -fPIC -std=c++11 -stdlib=libc++ -fstrict-aliasing
-Wstrict-aliasing=2 -Wsign-conversion -Wshadow -Wconversion -Wunused-variable
-Wmissing-field-initializers -Wchar-subscripts -Wmismatched-tags
-Wmissing-braces -Wshorten-64-to-32 -Wsign-compare -Wstrict-aliasing=2
-Wstrict-overflow=4 -Wunused-parameter -Wnewline-eof -I../include
-I../../libcxx/include ../src/cxa_aux_runtime.cpp
+ clang++ -c -g -O3 -fPIC -std=c++11 -stdlib=libc++ -fstrict-aliasing
-Wstrict-aliasing=2 -Wsign-conversion -Wshadow -Wconversion -Wunused-variable
-Wmissing-field-initializers -Wchar-subscripts -Wmismatched-tags
-Wmissing-braces -Wshorten-64-to-32 -Wsign-compare -Wstrict-aliasing=2
-Wstrict-overflow=4 -Wunused-parameter -Wnewline-eof -I../include
-I../../libcxx/include ../src/cxa_default_handlers.cpp
+ clang++ -c -g -O3 -fPIC -std=c++11 -stdlib=libc++ -fstrict-aliasing
-Wstrict-aliasing=2 -Wsign-conversion -Wshadow -Wconversion -Wunused-variable
-Wmissing-field-initializers -Wchar-subscripts -Wmismatched-tags
-Wmissing-braces -Wshorten-64-to-32 -Wsign-compare -Wstrict-aliasing=2
-Wstrict-overflow=4 -Wunused-parameter -Wnewline-eof -I../include
-I../../libcxx/include ../src/cxa_demangle.cpp
+ clang++ -c -g -O3 -fPIC -std=c++11 -stdlib=libc++ -fstrict-aliasing
-Wstrict-aliasing=2 -Wsign-conversion -Wshadow -Wconversion -Wunused-variable
-Wmissing-field-initializers -Wchar-subscripts -Wmismatched-tags
-Wmissing-braces -Wshorten-64-to-32 -Wsign-compare -Wstrict-aliasing=2
-Wstrict-overflow=4 -Wunused-parameter -Wnewline-eof -I../include
-I../../libcxx/include ../src/cxa_exception.cpp
../src/cxa_exception.cpp:261:24: error: unknown type name
'_Unwind_Control_Block'
static_cast_Unwind_Control_Block*(unwind_exception)-barrier_cache.bitpattern[0]);
^
../src/cxa_exception.cpp:261:65: error: member reference base type 'void' is not
a structure or union
static_cast_Unwind_Control_Block*(unwind_exception)-barrier_cache.bitpattern[0]);
^ ~
../src/cxa_exception.cpp:415:71: error: no member named 'barrier_cache' in
'_Unwind_Exception'
return
reinterpret_castvoid*(exception_header-unwindHeader.barrier_cache.bitpattern[0]);
~~ ^
3 errors generated.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752973: add patch
Control: tags -1 + patch build dependencies on libjcip-annotations-java and libmaven-javadoc-plugin-java are missing. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: add patch
Processing control commands: tags -1 + patch Bug #752973 [libopenws-java] libopenws-java: FTBFS - missing artifact net.jcip:jcip-annotations:jar:debian Added tag(s) patch. -- 752973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752973 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#761194: libjs-elycharts: no installable
Package: libjs-elycharts Version: 2.1.5+ds-1 Severity: grave Justification: renders package unusable Seems like I uploaded this package to soon: $ apt install libjs-elycharts ... libjs-elycharts : Depends: libjs-jquery (= 1.10.2) but 1.7.2+dfsg-3.2 is to be installed Depends: libjs-raphael (= 2.1.2) but it is not going to be installed Andreas, could you please check the dependencies? Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Processed:
Processing control commands: tags -1 help Bug #760874 [src:openjpeg2] openjpeg: some binary packages conflict with openjpeg2 Added tag(s) help. -- 760874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760874 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#760874:
Control: tags -1 help See: https://lists.debian.org/debian-mentors/2014/09/msg00225.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760874: openjpeg-tools missing ?
For some reason `openjpeg-tools` is not listed in your initial report. Is this an error ? should it also be part of the list ? Thx -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761198: scss._speedups fails to import on 64bit architectures
Package: src:python-scss Version: 1.2.0.post3-2 Severity: serious Tags: sid jessie $ python3 -c 'import scss._speedups' /usr/lib/python3/dist-packages/scss/__init__.py:86: RuntimeWarning: Scanning acceleration disabled (_speedups not found)! RuntimeWarning Traceback (most recent call last): File string, line 1, in module ImportError: /usr/lib/python3/dist-packages/scss/_speedups.cpython-34m-x86_64-linux-gnu.so: undefined symbol: PyString_FromStringAndSize -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759933: beignet: diff for NMU version 0.8-1.1
tags 759933 + pending
thanks
Dear maintainer,
I've prepared an NMU for beignet (versioned as (0.8-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
--
Julián Moreno Patiño
Debian Developer
.''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `' http://debian.org/
`- GPG Fingerprint:
C2C8 904E 314C D8FA 041D 9B00 D5FD FC15 6168 BF60
Registered GNU Linux User ID 488513
--- beignet-0.8/debian/changelog 2014-04-19 13:27:03.0 -0500
+++ beignet-0.8/debian/changelog 2014-09-11 11:02:49.0 -0500
@@ -1,3 +1,11 @@
+beignet (0.8-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Adjust clang Build-Depends. (Closes: #759933)
++ Thanks to Julian Wollrath for it.
+
+ -- Julián Moreno Patiño jul...@debian.org Thu, 11 Sep 2014 10:44:01 -0500
+
beignet (0.8-1) unstable; urgency=low
* New upstream release (Closes: #739534)
--- beignet-0.8/debian/control 2014-04-19 13:29:26.0 -0500
+++ beignet-0.8/debian/control 2014-09-11 10:43:33.0 -0500
@@ -4,11 +4,9 @@
Build-Depends: debhelper (= 9), cmake, pkg-config, python-minimal,
ocl-icd-dev, ocl-icd-opencl-dev,
libdrm-dev, libxfixes-dev, libxext-dev,
- llvm-3.4-dev | llvm-dev (= 1:3.4),
- clang-3.4 | clang (= 1:3.4) | clang (= 3.4),
- clang-3.4 | clang (= 1:3.4) | clang ( 1:0),
- libclang-3.4-dev | libclang-dev (= 1:3.4) | libclang-dev (= 3.4),
- libclang-3.4-dev | libclang-dev (= 1:3.4) | libclang-dev ( 1:0),
+ llvm-dev (= 1:3.4),
+ clang (= 1:3.4),
+ libclang-dev (= 1:3.4),
libgl1-mesa-dev (= 9) [!kfreebsd-any],
libegl1-mesa-dev (= 9) [!kfreebsd-any],
libgbm-dev (= 9) [!kfreebsd-any],
signature.asc
Description: Digital signature
Processed: tagging
Processing commands for cont...@bugs.debian.org: tags 759933 + pending Bug #759933 [src:beignet] beignet: FTBFS: /bin/sh: 1: clang: not found Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 759933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759933 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#736066: Allow encfs into jessie?
Hi Eduard, On Donnerstag, 11. September 2014, Eduard Bloch wrote: In fact, that is what I considered as workaround, and even harder: add a debconf message with priority critical telling exactly those details. I (probably too briefly) skimmed though the bug report, but couldn't find a usecase where an encrypted filestem container with broken crypto could be useful. Could you elaborate, please? cheers, Holger, curious signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#761194: libjs-elycharts: no installable
Processing control commands: tags -1 pending Bug #761194 [libjs-elycharts] libjs-elycharts: no installable Added tag(s) pending. -- 761194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761194 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#761194: libjs-elycharts: no installable
Control: tags -1 pending On Thu, Sep 11, 2014 at 05:43:14PM +0200, Sebastian Ramacher wrote: $ apt install libjs-elycharts ... libjs-elycharts : Depends: libjs-jquery (= 1.10.2) but 1.7.2+dfsg-3.2 is to be installed Depends: libjs-raphael (= 2.1.2) but it is not going to be installed Oh, oops. I forgot to test in a clean environment and in my working environment I had custom packages for raphael and jquery installed. I loosened the dependencies so that the package is installable and made sure to test functionality with the older versions. Sorry for not being more thorough. I pushed updated package to git, could you check and upload it, please? Cheers, Andreas -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 signature.asc Description: Digital signature
Bug#759838: Pending fixes for bugs in the padre package
tag 759838 + pending thanks Some bugs in the padre package are closed in revision 70bdb508a94c3f9a6f233917e78885e32adb0450 in branch 'master' by Dominique Dumont The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/padre.git/commit/?id=70bdb50 Commit message: patch Padre::Browser::PseudoDoc to fix FTBS (Closes: #759838) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the padre package
Processing commands for cont...@bugs.debian.org: tag 759838 + pending Bug #759838 [src:padre] padre: FTBFS: Failed test 'no warnings' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 759838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759838 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#760874: openjpeg-tools missing ?
On Thu, Sep 11, 2014 at 06:18:25PM +0200, Mathieu Malaterre wrote: For some reason `openjpeg-tools` is not listed in your initial report. Is this an error ? should it also be part of the list ? Yes it's an error? I made the list manually, and I forgot it. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736066: Allow encfs into jessie?
Hallo, * Holger Levsen [Thu, Sep 11 2014, 06:42:32PM]: Hi Eduard, On Donnerstag, 11. September 2014, Eduard Bloch wrote: In fact, that is what I considered as workaround, and even harder: add a debconf message with priority critical telling exactly those details. I (probably too briefly) skimmed though the bug report, but couldn't find a usecase where an encrypted filestem container with broken crypto could be useful. Could you elaborate, please? I though Jan has just described one. For example, taking a 10 year old CD with backups from your safe and trying to get the data back. Otherwise we should disable support for 1024b GPG keys ASAP so nobody could use them anymore. Regards, Eduard. signature.asc Description: Digital signature
Bug#761194: libjs-elycharts: no installable
On 2014-09-11 18:52:08, Andreas Moog wrote: Control: tags -1 pending On Thu, Sep 11, 2014 at 05:43:14PM +0200, Sebastian Ramacher wrote: $ apt install libjs-elycharts ... libjs-elycharts : Depends: libjs-jquery (= 1.10.2) but 1.7.2+dfsg-3.2 is to be installed Depends: libjs-raphael (= 2.1.2) but it is not going to be installed Oh, oops. I forgot to test in a clean environment and in my working environment I had custom packages for raphael and jquery installed. I loosened the dependencies so that the package is installable and made sure to test functionality with the older versions. Sorry for not being more thorough. I pushed updated package to git, could you check and upload it, please? Uploaded. Thanks for the very fast fix! Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#761194: marked as done (libjs-elycharts: no installable)
Your message dated Thu, 11 Sep 2014 17:49:01 + with message-id e1xs8up-0007qo...@franck.debian.org and subject line Bug#761194: fixed in elycharts.js 2.1.5+ds-2 has caused the Debian Bug report #761194, regarding libjs-elycharts: no installable 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.) -- 761194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libjs-elycharts Version: 2.1.5+ds-1 Severity: grave Justification: renders package unusable Seems like I uploaded this package to soon: $ apt install libjs-elycharts ... libjs-elycharts : Depends: libjs-jquery (= 1.10.2) but 1.7.2+dfsg-3.2 is to be installed Depends: libjs-raphael (= 2.1.2) but it is not going to be installed Andreas, could you please check the dependencies? Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: elycharts.js Source-Version: 2.1.5+ds-2 We believe that the bug you reported is fixed in the latest version of elycharts.js, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Moog andreas.m...@warperbbs.de (supplier of updated elycharts.js package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Sep 2014 18:36:18 +0200 Source: elycharts.js Binary: libjs-elycharts Architecture: source all Version: 2.1.5+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Andreas Moog andreas.m...@warperbbs.de Description: libjs-elycharts - Javascript library to generate static and interactive charts Closes: 761194 Changes: elycharts.js (2.1.5+ds-2) unstable; urgency=medium . * debian/control: - loosen dependencies on jquery and raphael, the package doesn't need the latest version. (Closes: #761194) Checksums-Sha1: 68eb399f6b04e8c7b1a6db22dd6051ab2afd 1988 elycharts.js_2.1.5+ds-2.dsc 40d63dbcb0ef084f45cf668ac9cfb50ac925e7d5 3104 elycharts.js_2.1.5+ds-2.debian.tar.xz 9eebb6b11f8941b6e77c7a4ae31763d885e9f572 56288 libjs-elycharts_2.1.5+ds-2_all.deb Checksums-Sha256: b6b4ee3a0901c09dd9c737a47a68e737345986c6c3e4ae8acf1b3c137e3b1e92 1988 elycharts.js_2.1.5+ds-2.dsc 59c6e78eefd879e7363d5340340d9b29c33801fbf4e2a670ae46ddf807aee6b3 3104 elycharts.js_2.1.5+ds-2.debian.tar.xz 6ec35e08341d95d12118835ce553037c6f78b4a7b025bfed1e3b624e9aefe004 56288 libjs-elycharts_2.1.5+ds-2_all.deb Files: 21b24a4a631da253e14a75268a0bc0b5 56288 web optional libjs-elycharts_2.1.5+ds-2_all.deb 212b1c6697fbe013386149d4e6b44005 1988 web optional elycharts.js_2.1.5+ds-2.dsc 72d4b80e33bd9013d768f25c7f4183e2 3104 web optional elycharts.js_2.1.5+ds-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUEd4TAAoJEGny/FFupxmTXtAQAMRilB8K2e7j0GOguG8hKT5F nnUlCdp32bPZJFlQ8HjKAaCUoNhRUyXwboAcdqhv00PXpNFiW48Y4vuBvEoEKI/7 nZNp06B0uQJIg2PfITgLSzKEHXAVlWBwpPiDE4rD1kZ6LgKnkzoWIsCUREMBCHdp 4TnQomO7ezKGaEGa79xPSm6Y/y623O8JUT6lRWL3qgu55GBD7j5sWq79OR1iSeGJ 2cUwXB8VfknZpzuqnaBmnezLNQB3OI4upv2eX7uIv4paFGX8LmU3aXz2VGLQpw4q itzzrZdU2iarJrvIKrxOzOqzlO5cqfMwQYschCGd+/DK2/lCEBgOXnVeAHvcIfJD rBBB3Zmnhm7GuAycUaTguwJmf4l4ImZwyFTEQtB3uJ5DfAJO5mCSm++J/5R+EKoA 5f7o9fHLxiFiIwiOvyrHjgPwiEX6XBwsdMoYGPTibDrEYDlWEmT8IZ0Fn+shchWy vFAGWTYTPHsrLIMGsMp8t+kg3m5HFkKn1P6zH5J38l6uFOLRjMPulczGvR9GRP0x racmw/elLhR8BvB4OjbHQv4iltb4nS+oiq5DyjzjDnqNpyRSp7J5mRhL1lJp6ru/ 4RnK4b5LJeIztXeWKRGAdoRM+sOC5WD8U7XsxpF9xLSA1yzlqT4UGwNCIhNqD2j+ UfxiiDfPitp6t7C0lunr =+78X -END PGP SIGNATUREEnd Message---
Processed: Removal of guile-1.8
Processing commands for cont...@bugs.debian.org:
severity 745991 serious
Bug #745991 [beast] beast: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 745994 serious
Bug #745994 {Done: Josue Abarca jmasli...@debian.org} [denemo] denemo: please
migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 745995 serious
Bug #745995 [dico] dico: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 745996 serious
Bug #745996 [drgeo] drgeo: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 745997 serious
Bug #745997 [freetalk] freetalk: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 761210 serious
Bug #761210 [g-wrap] g-wrap: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 745999 serious
Bug #745999 [gnubik] gnubik: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 746000 serious
Bug #746000 [gnurobots] gnurobots: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 746012 serious
Bug #746012 {Done: Matthias Klose d...@debian.org} [graphviz] graphviz:
please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 746001 serious
Bug #746001 [guile-cairo] guile-cairo: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 761211 serious
Bug #761211 [guile-gnome-platform] guile-gnome-platform: please migrate to
guile-2.0
Severity set to 'serious' from 'normal'
severity 746002 serious
Bug #746002 [guile-library] guile-library: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 746013 serious
Bug #746013 [libmatheval] libmatheval: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 746005 serious
Bug #746005 [lilypond] lilypond: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 746016 serious
Bug #746016 {Done: Torsten Landschoff tors...@debian.org} [swig2.0] swig2.0:
please migrate to guile-2.0
Severity set to 'serious' from 'normal'
severity 731787 serious
Bug #731787 {Done: Atsuhito KOHDA ko...@debian.org} [texmacs] texmacs: please
migrate to guile-2.0
Ignoring request to change severity of Bug 731787 to the same value.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
731787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731787
745991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745991
745994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745994
745995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745995
745996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745996
745997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745997
745999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745999
746000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746000
746001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746001
746002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746002
746005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005
746012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746012
746013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746013
746016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746016
761210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761210
761211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761211
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#746922: marked as done (xorp: ftbfs with GCC-4.9)
Your message dated Thu, 11 Sep 2014 19:10:26 +0100 with message-id 20140911181026.ga12...@calhariz.com and subject line Close xorp: ftbfs with GCC-4.9 has caused the Debian Bug report #746922, regarding xorp: ftbfs with GCC-4.9 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.) -- 746922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:xorp Version: 1.8.5-2 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.9 The package fails to build in a test rebuild on at least amd64 with gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The severity of this report may be raised before the jessie release. The full build log can be found at: http://people.debian.org/~doko/logs/failed-gcc49/xorp_1.8.5-2_unstable_gcc49.log The last lines of the build log are at the end of this report. To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-4.9/porting_to.html [...] g++ -o obj/x86_64-unknown-linux-gnu/libxipc/finder_msgs.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/finder_msgs.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/finder_tcp.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/finder_tcp.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/finder_tcp_messenger.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/finder_tcp_messenger.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/hmac.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/hmac.cc gcc -o obj/x86_64-unknown-linux-gnu/libxipc/hmac_md5.os -c -Wall -O2 -g3 -Werror -W -Wwrite-strings -Wbad-function-cast -Wmissing-prototypes -Wcast-qual -Wmissing-declarations -Wpointer-arith -Wcast-align -Wstrict-prototypes -Wnested-externs -pipe -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/hmac_md5.c g++ -o obj/x86_64-unknown-linux-gnu/libxipc/permits.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/permits.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/sockutil.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/sockutil.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_args.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_args.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_atom.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_atom.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_atom_encoding.os -c -O2 -g3 -Werror -W -Wall
Bug#759838: marked as done (padre: FTBFS: Failed test 'no warnings')
Your message dated Thu, 11 Sep 2014 18:21:09 +
with message-id e1xs8zv-0003rn...@franck.debian.org
and subject line Bug#759838: fixed in padre 1.00+dfsg-3
has caused the Debian Bug report #759838,
regarding padre: FTBFS: Failed test 'no warnings'
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.)
--
759838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: padre
Version: 1.00+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 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[3]: Entering directory '/«BUILDDIR»/padre-1.00+dfsg/winxs'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/«BUILDDIR»/padre-1.00+dfsg/winxs'
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -MTest::Harness
-e undef *Test::Harness::Switches; test_harness(0, 'inc', 'blib/lib',
'blib/arch') t/*.t t/perl/*.t t/python/*.t t/ruby/*.t t/java/*.t t/csharp/*.t
Xlib: extension RANDR missing on display :99.
# Tests find Wx: 0.9923 wxWidgets 3.0.1
# Failed test 'no warnings'
# at /usr/share/perl5/Test/NoWarnings.pm line 45.
# There were 2 warning(s)
# Previous test 26 'use Padre::Role::Task;'
# Module::Build will be removed from the Perl core distribution in the
next major release. Please install the separate libmodule-build-perl package.
It is being used at
/«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre/PluginBuilder.pm, line 32.
# at /usr/share/perl/5.20/deprecate.pm line 79.
# deprecate::import(undef, undef, deprecate) called at
/usr/share/perl/5.20/Module/Build.pm line 3
# Module::Build::BEGIN() called at /usr/share/perl/5.20/Module/Build.pm
line 3
# eval {...} called at /usr/share/perl/5.20/Module/Build.pm line 3
# require Module/Build.pm called at
/«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre/PluginBuilder.pm line 32
# Padre::PluginBuilder::BEGIN() called at
/usr/share/perl/5.20/Module/Build.pm line 3
# eval {...} called at /usr/share/perl/5.20/Module/Build.pm line 3
# require Padre/PluginBuilder.pm called at
/«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre.pm line 87
# eval {...} called at /«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre.pm line
87
# Padre::import(Padre, :everything) called at t/01_compile.t line 53
#
# --
# Previous test 26 'use Padre::Role::Task;'
# Possible precedence issue with control flow operator at
/«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre/Document/Perl/QuickFix/StrictWarnings.pm
line 71.
# at
/«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre/Document/Perl/QuickFix/StrictWarnings.pm
line 71.
# require Padre/Document/Perl/QuickFix/StrictWarnings.pm called at
/«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre.pm line 87
# eval {...} called at /«BUILDDIR»/padre-1.00+dfsg/blib/lib/Padre.pm line
87
# Padre::import(Padre, :everything) called at t/01_compile.t line 53
#
# Looks like you failed 1 test of 37.
t/01_compile.t .
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/37 subtests
Xlib: extension RANDR missing on display :99.
16:52:40: Warning: Cannot set locale to language English (U.K.).
16:52:40: Error: locale 'en_GB' cannot be set.
t/02_new.t . ok
t/03_db.t .. ok
t/04_config.t .. ok
Xlib: extension RANDR missing on display :99.
16:52:42: Warning: Cannot set locale to language English (U.K.).
16:52:42: Error: locale 'en_GB' cannot be set.
t/05_project.t . ok
Xlib: extension RANDR missing on display :99.
t/06_utils.t ... ok
t/07_version.t . ok
Xlib: extension RANDR missing on display :99.
t/08_style.t ... ok
t/09_search.t .. ok
Xlib: extension RANDR missing on display :99.
16:52:44: Warning: Cannot set locale to language English (U.K.).
16:52:44: Error: locale 'en_GB' cannot be set.
t/10_delta.t ... ok
t/11_svn.t . skipped: Not in an SVN checkout
t/12_mime.t ok
t/13_findinfiles.t . ok
t/14_warnings.t ok
Xlib: extension RANDR missing on display :99.
16:52:46: Warning: Cannot set locale to language English (U.K.).
16:52:46: Error: locale 'en_GB' cannot be set.
16:52:46: Warning: Cannot set locale to language German.
16:52:46: Error: locale 'de_DE' cannot be set.
16:52:46: Warning: Cannot set locale to language English
Processed: reassign 755761 to gdm3
Processing commands for cont...@bugs.debian.org: reassign 755761 gdm3 3.12.2-2 Bug #755761 [kde-workspace-bin] gdm3: Unable to start KDE after last gdm3 upgrade Bug reassigned from package 'kde-workspace-bin' to 'gdm3'. Ignoring request to alter found versions of bug #755761 to the same values previously set Ignoring request to alter fixed versions of bug #755761 to the same values previously set Bug #755761 [gdm3] gdm3: Unable to start KDE after last gdm3 upgrade Marked as found in versions gdm3/3.12.2-2. thanks Stopping processing here. Please contact me if you need assistance. -- 755761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755761 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#760935: perl: Crashing bug on trivial programs
tag 760935 unreproducible severity 760935 important thanks On Tue, Sep 09, 2014 at 09:10:13PM +0300, Niko Tyni wrote: On Tue, Sep 09, 2014 at 11:02:19AM +0200, Emmanuel Surleau wrote: Package: perl Version: 5.20.0-6 Severity: grave Justification: renders package unusable I have encountered a critical issue with both 5.20.0-6 and 5.20.1~rc2-1 versions of perl. How to reproduce: 09/09 10:29 ~/projects/integration_oed % perl -e 'use File::Find;' zsh: segmentation fault perl -e 'use File::Find;' As git-svn crashes systematically with an error code 139, git add -p is out of commission and apt-file crashes as well, I suspect this issue affects a lot more packages (which is also why I set the priority to 'grave'). Hi, that certainly doesn't crash here. This is most probably a local issue. If the perl package was this broken for everyone on amd64, I expect we'd have a lot more reports. As it is, 5.20.0-6 has been in sid for ten days and just migrated to testing. I'm tagging this is unreproducible for now and lowering the severity. I intend to close it later unless there's reason to believe it's more than local system corruption. Please keep 760...@bugs.debian.org at least cc'd on possible updates. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736066: Allow encfs into jessie?
On 11/09/2014 18:33, Eduard Bloch wrote: Otherwise we should disable support for 1024b GPG keys ASAP so nobody could use them anymore. Please also note, that the primary author (after a period of dormancy) is back and seems to be actively working on remediating the issues (cf. https://github.com/vgough/encfs). Best regards – Miroslaw Baran -- 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#760935: perl: Crashing bug on trivial programs
Processing commands for cont...@bugs.debian.org: tag 760935 unreproducible Bug #760935 [perl] perl: Crashing bug on trivial programs Added tag(s) unreproducible. severity 760935 important Bug #760935 [perl] perl: Crashing bug on trivial programs Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 760935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760935 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: Lowering the bug`s severity
Processing commands for cont...@bugs.debian.org: severity 741112 important Bug #741112 [libfreefoam1] libfreefoam1: libscotchDecomp.so.0.1.0 is GPL-licensed but links with GPL-incompatible library Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 741112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741112 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#741112: Lowering the bug`s severity
severity 741112 important thanks Same as here [1]. Waiting for a decision of FTP-masters. [1] https://bugs.debian.org/741196 Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755761: marked as done (gdm3: Unable to start KDE after last gdm3 upgrade)
Your message dated Thu, 11 Sep 2014 20:38:23 +0200 with message-id 20140911183823.gf13...@gnuservers.com.ar and subject line gdm3 blocks USR1 has caused the Debian Bug report #755761, regarding gdm3: Unable to start KDE after last gdm3 upgrade 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.) -- 755761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gdm3 Version: 3.12.2-2 Severity: critical Justification: breaks unrelated software After today's gdm3 upgrade on testing from 3.8 to 3.12, I'm unable to sucessfully logon onto my KDE4 setup. Here is what is happening here: after the gdm3 upgrade, if I try to start a KDE session by logging in, KDE hangs at the startup screen. Only the harddrive icon is shown. System remains responsive (can switch to VTs, can SSH in, mouse pointer still moves...). If I launch a task manager (like htop), there are about 3 kdeinit4 process in a tree: /usr/bin/kdeinit4 --oom-pipe 4 +kcminit_startup CPU load during this hang remains at zero. There is no disk activity present. For all effects the system sat there, idle. After poking a bit those hung kdeinit4 processes with GDB, if I kill the one with the following backtrace: #0 0x7f38346195c0 in __read_nocancel () at ../sysdeps/unix/syscall- template.S:81 #1 0x004070d5 in _start () KDE resumes startup as usual (it's almost always the second-to-last kdeinit4 process in the tree). Another workaround is to switch to a different login manager (be it kdm or LightDM), and in such case KDE starts up without incident, but these aren't really good options to me as I like using GDM. Yesterday's systemd-sysv update doesn't seem to be relevant to this case, as the older version of gdm3 worked fine until today, when I received the faulty upgrade. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.37-2 ii adduser 3.113+nmu3 ii dconf-cli0.20.0-2 ii dconf-gsettings-backend 0.20.0-2 ii debconf [debconf-2.0]1.5.53 ii gir1.2-gdm3 3.12.2-2 ii gnome-session [x-session-manager]3.12.1-3 ii gnome-session-bin3.12.1-3 ii gnome-session-flashback [x-session-manager] 3.8.0-3 ii gnome-settings-daemon3.12.2-1 ii gnome-shell 3.12.2-3 ii gnome-terminal [x-terminal-emulator] 3.12.3-1 ii gsettings-desktop-schemas3.12.2-1 ii kde-window-manager [x-window-manager]4:4.11.9-1 ii konsole [x-terminal-emulator]4:4.13.1-1 ii libaccountsservice0 0.6.37-2 ii libatk1.0-0 2.12.0-1 ii libaudit11:2.3.7-1 ii libc62.19-7 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgdm1 3.12.2-2 ii libglib2.0-0 2.40.0-3 ii libglib2.0-bin 2.40.0-3 ii libgtk-3-0 3.12.2-1+b1 ii libpam-modules 1.1.8-3 ii libpam-runtime 1.1.8-3 ii libpam-systemd 208-6 ii libpam0g 1.1.8-3 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii librsvg2-common 2.40.2-1 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-6 ii libsystemd-id128-0 208-6 ii libsystemd-journal0 208-6 ii libsystemd-login0208-6 ii libwrap0 7.6.q-25
Bug#736066: Allow encfs into jessie?
Hi, On Donnerstag, 11. September 2014, Eduard Bloch wrote: I though Jan has just described one. For example, taking a 10 year old CD with backups from your safe and trying to get the data back. seems useful indeed, thanks. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#761217: lgogdownloader: FTBFS: help2man: can't get `--help' info
Source: lgogdownloader Version: 2.17-1 Severity: serious Justification: fails to build from source Automatic builds of lgogdownloader have all been failing: help2man -N -i man/lgogdownloader.supplemental.groff -n downloader for GOG.com games and other files -o man/lgogdownloader.1 bin/Release/lgogdownloader help2man: can't get `--help' info from bin/Release/lgogdownloader Try `--no-discard-stderr' if option outputs to stderr make[1]: *** [after_release] Error 134 Makefile:101: recipe for target 'after_release' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:5: recipe for target 'build-arch' failed 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
Bug#761220: efreet: superseded by efl?
Source: efreet Version: 1.7.7-2 Severity: serious efreet and efl both build the following binary packages: - libefreet-dev - libfreet1 Given efl provide them in a higher version, I guess efreet should be removed from the archive. In the meantime it prevents the efreet package to be accepted in the archive: | Version check failed: | Your upload included the binary package libefreet1, version 1.7.7-2, for ppc64el, | however testing already has version 1.8.6-2. | Uploads to unstable must have a higher version than present in testing. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16-1-powerpc64le (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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736066: Allow encfs into jessie?
On Thu, 2014-09-11 at 19:33 +0200, Eduard Bloch wrote: I though Jan has just described one. For example, taking a 10 year old CD with backups from your safe and trying to get the data back. Another option would be to take the same approach that TrueCrypt did under (potentially) the same circumstances, and allow encfs into jessie - but only for read-only containers. That way, people can recover their data easily, but there's no risk of perpetuating a completely broken encryption layer. That'd be the best of both worlds, in my opinion. -- Harlan Lieberman-Berg ~hlieberman -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761225: subsurface: something is not right :(
Package: subsurface Version: 4.0.3-2.1+b1 Severity: grave Justification: renders package unusable # dpkg --get-selections | egrep libgit2 libgit2-21:amd64install libgit2-dev:amd64 install # apt-cache policy libgit2-dev libgit2-dev: Installed: 0.21.1-1 Candidate: 0.21.1-1 Version table: *** 0.21.1-1 0 500 http://ftp.se.debian.org/debian/ sid/main amd64 Packages 100 /var/lib/dpkg/status # dpkg -s libgit2-21:amd64 Package: libgit2-21 Version: 0.21.1-1 # dpkg -s libgit2-dev Package: libgit2-dev Version: 0.21.1-1 # apt-get install subsurface Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: subsurface : Depends: libgit2-0 (= 0.20.0) but it is not installable E: Unable to correct problems, you have held broken packages. I'm confused :( -- 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.16-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 subsurface depends on: ii libc6 2.19-10 ii libdivecomputer0 0.4.2-1 ii libgcc11:4.9.1-13 ii libmarblewidget19 4:4.14.0-2 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtwebkit4 2.3.2.dfsg-3 ii libsqlite3-0 3.8.6-1 ii libstdc++6 4.9.1-13 ii libxml22.9.1+dfsg1-4 ii libxslt1.1 1.1.28-2 ii libzip20.11.2-1.1 ii zlib1g 1:1.2.8.dfsg-2 subsurface recommends no packages. subsurface suggests no packages. -- 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#761217: lgogdownloader: FTBFS: help2man: can't get `--help' info
Hi Aaron, On Thu, 11 Sep 2014 14:47:08 -0400, Aaron M. Ucko u...@debian.org wrote: Automatic builds of lgogdownloader have all been failing: Thanks for taking the time to file this bug! help2man -N -i man/lgogdownloader.supplemental.groff -n downloader for GOG.com games and other files -o man/lgogdownloader.1 bin/Release/lgogdownloader help2man: can't get `--help' info from bin/Release/lgogdownloader Try `--no-discard-stderr' if option outputs to stderr make[1]: *** [after_release] Error 134 Makefile:101: recipe for target 'after_release' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:5: recipe for target 'build-arch' failed Could you please take a look? I have been, and I was rather bamboozled... The package built fine before I uploaded it to the archive (using pbuilder), and it builds fine on all the porterboxes I tried. It turns out lgogdownloader fails to run if $HOME is not set! I'll fix it ASAP... Regards, Stephen signature.asc Description: PGP signature
Bug#749519: marked as done (missing license in debian/copyright)
Your message dated Thu, 11 Sep 2014 21:23:53 + with message-id e1xsbql-0002fr...@franck.debian.org and subject line Bug#749519: fixed in gnome-screensaver 3.6.1-2 has caused the Debian Bug report #749519, regarding missing license in debian/copyright 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.) -- 749519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-screensaver Version: 3.4.1-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: src/s* to debian/copyright. Thanks! Thorsten ---End Message--- ---BeginMessage--- Source: gnome-screensaver Source-Version: 3.6.1-2 We believe that the bug you reported is fixed in the latest version of gnome-screensaver, 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 749...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie s...@debian.org (supplier of updated gnome-screensaver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Sep 2014 21:26:06 +0100 Source: gnome-screensaver Binary: gnome-screensaver Architecture: source amd64 Version: 3.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Simon McVittie s...@debian.org Description: gnome-screensaver - GNOME screen saver and locker Closes: 733059 749519 Changes: gnome-screensaver (3.6.1-2) unstable; urgency=medium . * Team upload * Add missing permissive license to debian/copyright (Closes: #749519) * Add a missing copyright holder while I'm there * Add patch from upstream to enable gnome-screensaver to be included in the autostart list for non-GNOME sessions, by requiring session files to include it in RequiredComponents if desired and removing its AutostartCondition (Closes: #733059) - depend on dh-autoreconf and gnome-common so we can autoreconfiscate - remove fallback - flashback patch, no longer relevant - Breaks versions of gnome-session-flashback that do not explicitly pull it in Checksums-Sha1: e9958281bf3c72c7229750fc7d87a7b26f27d7c6 2586 gnome-screensaver_3.6.1-2.dsc a7cdfe3a55c3c33ed7b63fd35465d54a87e88806 8580 gnome-screensaver_3.6.1-2.debian.tar.xz 7aa4d35de7735f853de078a768100b8e60ab2303 234552 gnome-screensaver_3.6.1-2_amd64.deb Checksums-Sha256: d982d4cf8ee7cc44763edaee8ef45775c2fe3bf2b376aff3a9e39b5227d360a0 2586 gnome-screensaver_3.6.1-2.dsc 644ccc7f9f7b78aae83d9f341b3987b332cfd1fde53f6be3aeab9b1c64ab621a 8580 gnome-screensaver_3.6.1-2.debian.tar.xz 12dc38edffe1ecdebf53d17e8f22ed6653446523112832edd9edac2bc824a81f 234552 gnome-screensaver_3.6.1-2_amd64.deb Files: 6ef5333693cb7719211eae452e8ea6af 234552 gnome optional gnome-screensaver_3.6.1-2_amd64.deb c705c297ff82d001d5173936a96ba867 2586 gnome optional gnome-screensaver_3.6.1-2.dsc c645747ef92fdd038fe6b16aeb7ed920 8580 gnome optional gnome-screensaver_3.6.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIVAwUBVBIKM03o/ypjx8yQAQiNfA/+MTQrLy4mr62x1cJxuNjLURri24w62mPx iJOFjjdc7Kfs1U/XFTdqGXJFXsiCOehu5CGThHTnP05IRHBI25gAHHrwLOMOHZKA bEkBriIbwdTtu3sPlIvl6orKDCdIVj1D4Z0u3QjX48Ac0/CbP/waT4+bwbqyCM9a QrLhUI1Tq+w+wo8jK+H1GRd3qA1IY4QtNw2FGiULCAlzA29czElt7WWAS6sc+Xh6 +mk8enw27Tg4OkfFKxLsKxh/4Aa/jjH/mbIBOScT6zxvpqFgpkEyH0vf9PPTwyxe a+SFDMimCKmhkBkOoXAG9iKVerogp8qIFpKV9l41j9+FT6h273lZFatB5Z5k5u8c dMQZT+d116/ErsX1gznGuHByQ/gEqEJ373y/b1Tr9NySgnhYBQlWyLTktyAnOuPL 6GXvM34BDumOY+LV45dUIrCTVv/6M6IDVD0uogIJa9LS438wO9B7PQyq3OBrxU4z ZN629Hf/2PW3NWLZoGwNdLJv+/hUw3Nr+WeOMTgYp8IwDCtZsZNRuuCjNPr2PJYE yN/0tzO2Zwa9kfnmzkFsaiwNv83+FqewIrxkhjSz/aaORJsjpm+5f53tCeV8FTb4 cxFtxY4s9w3YFOv5LI+G1nueGOfjVPf/afUlLEgIL5JD/kybQOWyyUkVRiDO1iIL xVDNO7aneM0= =wLoK -END PGP SIGNATUREEnd Message---
Bug#733059: marked as done (gnome-screensaver not working on all gnome-sessions)
Your message dated Thu, 11 Sep 2014 21:23:53 + with message-id e1xsbql-0002fl...@franck.debian.org and subject line Bug#733059: fixed in gnome-screensaver 3.6.1-2 has caused the Debian Bug report #733059, regarding gnome-screensaver not working on all gnome-sessions 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.) -- 733059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-screensaver Version: 3.6.1-1 Severity: critical Justification: breaks the whole system -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-screensaver depends on: ii dbus-x11 1.6.18-2 ii gnome-icon-theme 3.10.0-1 ii gnome-session-bin 3.8.4-3 ii gsettings-desktop-schemas 3.8.2-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libdbus-1-31.6.18-2 ii libdbus-glib-1-2 0.100.2-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-0 2.36.4-1 ii libgnome-desktop-3-7 3.8.4-2 ii libgnomekbd8 3.6.0-1 ii libgtk-3-0 3.8.6-1 ii libpam0g 1.1.3-9 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxklavier16 5.2.1-1 ii libxxf86vm11:1.1.3-1 Versions of packages gnome-screensaver recommends: ii gnome-power-manager 3.8.2-1 ii libpam-gnome-keyring 3.8.2-2 gnome-screensaver suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: gnome-screensaver Source-Version: 3.6.1-2 We believe that the bug you reported is fixed in the latest version of gnome-screensaver, 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. Simon McVittie s...@debian.org (supplier of updated gnome-screensaver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Sep 2014 21:26:06 +0100 Source: gnome-screensaver Binary: gnome-screensaver Architecture: source amd64 Version: 3.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Simon McVittie s...@debian.org Description: gnome-screensaver - GNOME screen saver and locker Closes: 733059 749519 Changes: gnome-screensaver (3.6.1-2) unstable; urgency=medium . * Team upload * Add missing permissive license to debian/copyright (Closes: #749519) * Add a missing copyright holder while I'm there * Add patch from upstream to enable gnome-screensaver to be included in the autostart list for non-GNOME sessions, by requiring session files to include it in RequiredComponents if desired and removing its AutostartCondition (Closes: #733059) - depend on dh-autoreconf and gnome-common so we can autoreconfiscate - remove fallback - flashback patch, no longer relevant - Breaks versions of gnome-session-flashback that do not explicitly pull it in Checksums-Sha1: e9958281bf3c72c7229750fc7d87a7b26f27d7c6 2586 gnome-screensaver_3.6.1-2.dsc a7cdfe3a55c3c33ed7b63fd35465d54a87e88806 8580 gnome-screensaver_3.6.1-2.debian.tar.xz 7aa4d35de7735f853de078a768100b8e60ab2303 234552 gnome-screensaver_3.6.1-2_amd64.deb Checksums-Sha256: d982d4cf8ee7cc44763edaee8ef45775c2fe3bf2b376aff3a9e39b5227d360a0 2586 gnome-screensaver_3.6.1-2.dsc 644ccc7f9f7b78aae83d9f341b3987b332cfd1fde53f6be3aeab9b1c64ab621a 8580 gnome-screensaver_3.6.1-2.debian.tar.xz 12dc38edffe1ecdebf53d17e8f22ed6653446523112832edd9edac2bc824a81f 234552 gnome-screensaver_3.6.1-2_amd64.deb Files: 6ef5333693cb7719211eae452e8ea6af 234552 gnome optional gnome-screensaver_3.6.1-2_amd64.deb c705c297ff82d001d5173936a96ba867 2586 gnome optional
Bug#760682: lvm2: debian/rules try to restart lvm2-monitor.socket which doesn't exist
Control: severity -1 important On Sat, Sep 06, 2014 at 09:21:01PM +0200, Laurent Bigonville wrote: This is causing issues as the maintainer script are trying to start/stop it: Please show _what_ issues it produces. Sure it is not right, but you forgot to show that it actually makes the package unusable. I tried re-installing it several times and it did not break. Bastian -- Actual war is a very messy business. Very, very messy business. -- Kirk, A Taste of Armageddon, stardate 3193.0 -- 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#760682: lvm2: debian/rules try to restart lvm2-monitor.socket which doesn't exist
Processing control commands: severity -1 important Bug #760682 [lvm2] lvm2: debian/rules try to restart lvm2-monitor.socket which doesn't exist Severity set to 'important' from 'serious' -- 760682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760682 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#761217: marked as done (lgogdownloader: FTBFS: help2man: can't get `--help' info)
Your message dated Thu, 11 Sep 2014 21:49:19 + with message-id e1xscex-000638...@franck.debian.org and subject line Bug#761217: fixed in lgogdownloader 2.17-2 has caused the Debian Bug report #761217, regarding lgogdownloader: FTBFS: help2man: can't get `--help' info 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.) -- 761217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lgogdownloader Version: 2.17-1 Severity: serious Justification: fails to build from source Automatic builds of lgogdownloader have all been failing: help2man -N -i man/lgogdownloader.supplemental.groff -n downloader for GOG.com games and other files -o man/lgogdownloader.1 bin/Release/lgogdownloader help2man: can't get `--help' info from bin/Release/lgogdownloader Try `--no-discard-stderr' if option outputs to stderr make[1]: *** [after_release] Error 134 Makefile:101: recipe for target 'after_release' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:5: recipe for target 'build-arch' failed Could you please take a look? Thanks! ---End Message--- ---BeginMessage--- Source: lgogdownloader Source-Version: 2.17-2 We believe that the bug you reported is fixed in the latest version of lgogdownloader, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt sk...@debian.org (supplier of updated lgogdownloader 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: Thu, 11 Sep 2014 23:17:00 +0200 Source: lgogdownloader Binary: lgogdownloader Architecture: source amd64 Version: 2.17-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Stephen Kitt sk...@debian.org Description: lgogdownloader - downloader for GOG.com files Closes: 761217 Changes: lgogdownloader (2.17-2) unstable; urgency=medium . * Avoid touching /home/steve if --help or --version are specified on the command-line. Closes: #761217. Checksums-Sha1: 715d343dff8a8b085eded7116615a371e5258e53 2020 lgogdownloader_2.17-2.dsc 165a34e5ddfa98f2468b786698f257348055ca12 3536 lgogdownloader_2.17-2.debian.tar.xz Checksums-Sha256: 975693d80f3b8fa8909fd5ceb91b66f00f4f9812dd59492d1076aab8bc18d2ec 2020 lgogdownloader_2.17-2.dsc 290c7e539fcdfb021832b65b57dd0465ed46eddfd97e8a6de7aa4ac4174c1175 3536 lgogdownloader_2.17-2.debian.tar.xz Files: e530bf14b4d67ea6cb1a847361bbf4c0 2020 web optional lgogdownloader_2.17-2.dsc 69bb76fef46c2b8c2addb25c07474584 3536 web optional lgogdownloader_2.17-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUEhRpAAoJEIDTAvWIbYOcehIQAIqMVJkSgL68ughG9gnyc7RM Nglv7hweyAGzez1cRQdwcF5y+mDJmkgPBZxXgSbJQQhj+Z/UlhZ5KbuTTvU/KOns NqvjiP3GSpFun54rr/x5o52t/5KKjxxj/rQpHCBUGOdpzSyQYH1E/d5rteDRT4q8 qB7G9l8HuctBFU0NsoAlz7M8H51xYE85dDlcXakK4dp+Sv2LS/TB69ebwd2MVoOb uAd0x6q74XB/Fq9/bET9Flu9QO2qxNQCmrLlWYwclySgv2YgNYgoJFoCpn8v3MiB 442Fl/j9GoBqbFJUU/wYbA0n7Bq0C7UauFw/QUy8x1eBrs9sFc/Izw0KNBRARAwd SMsDUjptmG828IJaye2Haw46vfv7LE/gjjC76yBNoBYdYMSkIYFRl/74D1i1SjeL JT9hbWF9+u3ArdyY7UeLqleYvlIIxyMAQgIXvJbVrUGZtqRhjY6vEBxVJbnIx28b pOZtQIr+BSWvyF8LuYMvTOTJpgO3qZvZZNXu9I8IcjyI4+bJPy++M0uXVgxVYUOE EusKZkBwhEQGYODNr+XDceslWUzqgTwrxCrzvpuPdJuMVsLbXa+UEKJx9bZlTYul 9N8cOujSVWIdX+gHpFnOZ/T5vT/vWOTFcLt9waqj0/QWAG6+qv6NWeACzOgaApL9 P85FynCvlHHWGL8qOcKP =lRAs -END PGP SIGNATUREEnd Message---
Bug#761234: openvpn: Openvpn connects to server but no data pass the tunel. Bad LZO decompression in server log
Package: openvpn Version: 2.3.3-1 Severity: grave Justification: renders package unusable I can connect to OpenVPN server (2.3.2), no data is passed thru the tunnel. I use networm-manager openvpn plugin. Tcpdump see packages traveling out the client's both on tun0 interface and client's eth interface. I can't see any traffic on servers's tun interface. Server's ethernet interface receives packets from client(encapsulated traffic). There is a lot of Bad LZO decompression header byte: 0 message in server log. Other clients (mostly Windows and Android) don't have such a problem. The tunnel worked on the same laptop before. Some update made the problem. I tried to use openvpn openvpn_2.2.1-8+deb7u2_amd64.deb without succes. Log from the server (After last line with VERIFY OK): hu Sep 11 23:59:57 2014 83.26.245.199:46853 WARNING: 'dev-type' is used inconsistently, local='dev-type tun', remote='dev-type tap' Thu Sep 11 23:59:57 2014 83.26.245.199:46853 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1542', remote='link-mtu 1578' Thu Sep 11 23:59:57 2014 83.26.245.199:46853 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532' Thu Sep 11 23:59:57 2014 83.26.245.199:46853 WARNING: 'mtu-dynamic' is present in remote config but missing in local config, remote='mtu-dynamic' Thu Sep 11 23:59:57 2014 83.26.245.199:46853 Data Channel Encrypt: Cipher 'BF- CBC' initialized with 128 bit key Thu Sep 11 23:59:57 2014 83.26.245.199:46853 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Thu Sep 11 23:59:57 2014 83.26.245.199:46853 Data Channel Decrypt: Cipher 'BF- CBC' initialized with 128 bit key Thu Sep 11 23:59:57 2014 83.26.245.199:46853 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Fri Sep 12 00:00:02 2014 83.26.245.199:46853 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA Fri Sep 12 00:00:02 2014 83.26.245.199:46853 [hieracium] Peer Connection Initiated with [AF_INET]83.26.245.199:46853 Fri Sep 12 00:00:02 2014 MULTI: new connection by client 'hieracium' will cause previous active sessions by this client to be dropped. Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect. Fri Sep 12 00:00:02 2014 MULTI_sva: pool returned IPv4=169.254.3.6, IPv6=(Not enabled) Fri Sep 12 00:00:02 2014 MULTI: Learn: 169.254.3.6 - hieracium/83.26.245.199:46853 Fri Sep 12 00:00:02 2014 MULTI: primary virtual IP for hieracium/83.26.245.199:46853: 169.254.3.6 Fri Sep 12 00:00:02 2014 hieracium/83.26.245.199:46853 Bad LZO decompression header byte: 0 Fri Sep 12 00:00:02 2014 hieracium/83.26.245.199:46853 Bad LZO decompression header byte: 0 Fri Sep 12 00:00:02 2014 hieracium/83.26.245.199:46853 Bad LZO decompression header byte: 0 Fri Sep 12 00:00:03 2014 hieracium/83.26.245.199:46853 Bad LZO decompression header byte: 0 Fri Sep 12 00:00:03 2014 hieracium/83.26.245.199:46853 Bad LZO decompression header byte: 0 . 645 variation(s) on previous 10 message(s) suppressed by --mute -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15.5MK (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openvpn depends on: ii debconf [debconf-2.0] 1.5.53 ii initscripts2.88dsf-53.4 ii iproute2 3.16.0-2 ii libc6 2.19-10 ii liblzo2-2 2.08-1 ii libpam0g 1.1.8-3.1 ii libpkcs11-helper1 1.11-1 ii libssl1.0.01.0.1i-2 Versions of packages openvpn recommends: ii easy-rsa 2.2.2-1 Versions of packages openvpn suggests: ii openssl 1.0.1i-2 pn resolvconf none -- debconf information: openvpn/create_tun: false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757031: marked as done (missing dependency on julia)
Your message dated Thu, 11 Sep 2014 22:34:20 + with message-id e1xscww-0004wf...@franck.debian.org and subject line Bug#757031: fixed in julia-factcheck 0.1.2-2 has caused the Debian Bug report #757031, regarding missing dependency on julia 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.) -- 757031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: julia-factcheck Version: 0.1.2-1 Severity: serious As per subject. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: julia-factcheck Source-Version: 0.1.2-2 We believe that the bug you reported is fixed in the latest version of julia-factcheck, 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 757...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey bal...@balintreczey.hu (supplier of updated julia-factcheck package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 12 Sep 2014 00:00:18 +0200 Source: julia-factcheck Binary: julia-factcheck Architecture: source all Version: 0.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Julia Team pkg-julia-de...@lists.alioth.debian.org Changed-By: Balint Reczey bal...@balintreczey.hu Description: julia-factcheck - Midje-like testing for Julia Closes: 757031 Changes: julia-factcheck (0.1.2-2) unstable; urgency=medium . * Depend on Julia (Closes: #757031) * Use canonical URIs in VCS fields Checksums-Sha1: 3cb197125801ffbf5d228b119167079b43a18fc2 1990 julia-factcheck_0.1.2-2.dsc dc651c267a05724394714109ca3ccaf58cbe9f8d 1872 julia-factcheck_0.1.2-2.debian.tar.xz 0d8e1753cc759f6d62fbae0eb2f494a64043c58a 7652 julia-factcheck_0.1.2-2_all.deb Checksums-Sha256: 33a8b3f795159dfde5a07f5e22d7d3e564b7866a6cbfca6dca3b764be7d14147 1990 julia-factcheck_0.1.2-2.dsc c6c6a16ae17438f90bce1539e7e714a443e0326dd9db4698d6a8f6072e1b88f5 1872 julia-factcheck_0.1.2-2.debian.tar.xz 144961e17fc24d57b631c86a6908b6a466d2417718452d697b3940b3103ae892 7652 julia-factcheck_0.1.2-2_all.deb Files: cf6302e55dfd6a80f37f99de21c2ae2d 7652 science extra julia-factcheck_0.1.2-2_all.deb 07b4fecee9657e9ba04566e139d2fa06 1990 science extra julia-factcheck_0.1.2-2.dsc 83b20c21d2bebb0bf8cd3ad676e6f31b 1872 science extra julia-factcheck_0.1.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUEh+UAAoJEPZk0la0aRp9U2YP/i7B0NIjCxP4f5QbrV3dsTSc ocb+DO69Cr9v6QtwlgLuopf6sWMDPDFpq1JJp8GDod0IBOwbm37iaGLSHRWKrGVv hJYNL2u8mYJOrw3dtT/+DYZvicRbgNHPsJ8mn+ofUVTaz1of8ES2zqoc0EE+Lbqy +Wj9bcXQDOGG9NUcLCXInpbjybkYHIXHzR6/AlvA23Dee3BQjja8dQyQ/soaoH0B T+WiFbS9x12CU4cUQSVejIjeD0RnLDNuQUSaWCELADjao95m4HZp3m0eeopUy2fz 94aAZ/C2UCnEyszX7Jn1rWiUsfGWCxOAlEhQeFROlec8rVJGC92SesGVSYz830Nu X7ok/vcSfdJbara/PJ1tVGN1Q34j0WV5hFo6wvlhbZdi9iyIQJ4H8m4sfQOGiLoz 7dLMngTie2ZY4/xpWCM/eY00eB6xuaa9Wz3s5pHTY3O1B/VCLdyWUSNC4aYsxZpT kNPc9U1jlubBUM2s1INg/ED/i6cksYmSzzHgewF6DpIcN7x+PXtNKcQW4ly8DVkj dJkUvONx1BtUgcFdOW3U1YPwfjs6pO2MIQ8Un3l3JVC5ccyKiWm9++BA9ul51a/M arZl8uqaDyR6PzxUStnfrnhHqMCU0iBZ/lxJTj81z8DNJST4qnWWFGvJ5DNkGktT sErX7bBp9OrivwLEXeqm =zmGR -END PGP SIGNATUREEnd Message---
Bug#760769: subsurface: can't be installed due to missing libmarblewidget18
Thanks for your efforts :-) Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#761241: gnome-maps: fail to start
Package: gnome-maps Version: 3.12.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, I get this error when starting gnome-maps: (gnome-maps:1330): Gdk-ERROR **: The program 'gnome-maps' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 313 error_code 8 request_code 155 (GLX) minor_code 31) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-maps depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii geoclue-2.0 2.1.8-1 ii gir1.2-champlain-0.120.12.8-1 ii gir1.2-clutter-1.0 1.18.4-2 ii gir1.2-cogl-1.0 1.18.2-2 ii gir1.2-gdkpixbuf-2.0 2.30.8-1 ii gir1.2-geocodeglib-1.0 3.12.2-1 ii gir1.2-glib-2.0 1.40.0-2 ii gir1.2-gtk-3.0 3.12.2-3+b1 ii gir1.2-gtkchamplain-0.12 0.12.8-1 ii gir1.2-gtkclutter-1.01.5.4-1 ii gjs 1.40.1-4 ii libc62.19-10 ii libgirepository-1.0-11.40.0-2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.40.1-4 ii libglib2.0-0 2.40.0-5 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#761245: icedove: STARTTLS regression: connection to SMTP server was lost in the middle of the transaction
Package: icedove Version: 31.0-3 Severity: serious Today I upgraded icedove 24.7.0-1~deb7u1 to 31.0-3 and immediately lost ability to send messages (connection security: STARTTLS): connection to SMTP server was lost in the middle of the transaction. Luckily I have access to server log where exim4 4.80-7 logged the following: TLS error on connection from [...] (gnutls_handshake): Could not negotiate a supported cipher suite. Downgrading icedove back to 24.7.0-1~deb7u1 fixed the problem. -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Bug#758714: marked as done (kiki: Please update to use wxpython3.0)
Your message dated Fri, 12 Sep 2014 01:48:45 +
with message-id e1xsfyf-0002ue...@franck.debian.org
and subject line Bug#758714: fixed in kiki 0.5.6-8.1
has caused the Debian Bug report #758714,
regarding kiki: Please update to use wxpython3.0
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.)
--
758714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: kiki
Version: 0.5.6-8
Severity: important
Tags: patch sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0
Control: block 755757 by -1
We're aiming to migrate the archive to using wxpython3.0 instead of
wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released.
I've rebuilt kiki with the attached patch and it seems to work.
I'm happy to NMU these changes.
Cheers,
Olly
diff -Nru kiki-0.5.6/debian/changelog kiki-0.5.6/debian/changelog
--- kiki-0.5.6/debian/changelog 2011-11-25 18:26:28.0 +1300
+++ kiki-0.5.6/debian/changelog 2014-08-21 00:00:14.0 +1200
@@ -1,3 +1,11 @@
+kiki (0.5.6-8.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update to use wxPython 3.0:
++ New patch: 04_wxpy3.0-compat.patch
+
+ -- Olly Betts o...@survex.com Wed, 20 Aug 2014 23:59:42 +1200
+
kiki (0.5.6-8) unstable; urgency=low
* debian/patch:
diff -Nru kiki-0.5.6/debian/control kiki-0.5.6/debian/control
--- kiki-0.5.6/debian/control 2011-11-19 06:54:49.0 +1300
+++ kiki-0.5.6/debian/control 2014-08-18 23:40:14.0 +1200
@@ -11,7 +11,7 @@
Package: kiki
Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-wxgtk2.8
+Depends: ${python:Depends}, ${misc:Depends}, python-wxgtk3.0
XB-Python-Version: ${python:Versions}
Description: tool for python regular expression testing
A free environment for regular expression testing (ferret). It allows
diff -Nru kiki-0.5.6/debian/patches/04_wxpy3.0-compat.patch kiki-0.5.6/debian/patches/04_wxpy3.0-compat.patch
--- kiki-0.5.6/debian/patches/04_wxpy3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ kiki-0.5.6/debian/patches/04_wxpy3.0-compat.patch 2014-08-20 23:59:21.0 +1200
@@ -0,0 +1,27 @@
+Description: Updates for wxPython 3.0
+ Allow wxPython 3.0 to be used.
+ Avoid deprecation warning (wx.InitAllImageHandlers() is a no-op under wxPython
+ 2.8, so removing it remains compatible with wxPython 2.8).
+Author: Olly Betts o...@survex.com
+Forwarded: no
+Last-Update: 2014-08-20
+
+--- a/kiki.py
b/kiki.py
+@@ -23,7 +23,7 @@
+
+
+ import wxversion
+-wxversion.select('2.8')
++wxversion.ensureMinimal('2.8')
+
+ import wx
+ import wx.html
+@@ -705,7 +705,6 @@
+ global settings
+ settings = Settings(dirname=.kiki, filename=kikicfg.py, debugfile=kikidebug)
+ Kiki = wx.PySimpleApp()
+-wx.InitAllImageHandlers()
+ mw = MyFrameWithEvents(None, -1, )
+ mw.icon()
+ Kiki.SetTopWindow(mw)
diff -Nru kiki-0.5.6/debian/patches/series kiki-0.5.6/debian/patches/series
--- kiki-0.5.6/debian/patches/series 2011-11-25 18:11:40.0 +1300
+++ kiki-0.5.6/debian/patches/series 2014-08-20 23:55:39.0 +1200
@@ -1,3 +1,4 @@
01_path_changes.diff
02_remove_wx.NotebookSizer.diff
03_setup.py.diff
+04_wxpy3.0-compat.patch
---End Message---
---BeginMessage---
Source: kiki
Source-Version: 0.5.6-8.1
We believe that the bug you reported is fixed in the latest version of
kiki, 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 758...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Olly Betts o...@survex.com (supplier of updated kiki package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 07 Sep 2014 01:19:05 +
Source: kiki
Binary: kiki
Architecture: source all
Version: 0.5.6-8.1
Distribution: unstable
Urgency: medium
Maintainer: Ignace Mouzannar mouzan...@gmail.com
Changed-By: Olly Betts o...@survex.com
Description:
kiki - tool for python regular expression testing
Closes: 758714
Changes:
kiki (0.5.6-8.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Update to use wxPython 3.0 (Closes: #758714):
+ New patch:
Bug#718154: unreproducible (re: psychopy: FTBFS: Tests failed)
Control: tags -1 -unreproducible On Thu, Oct 10, 2013 at 10:11:04PM +0900, Hideki Yamane wrote: I can't reproduce this bug under cowbuilder amd64 (both baremetal and KVM). see attached build log. It's completely reproducible if you use sbuild (it happens when rebuilding on my machine). The important difference is that sbuild sets HOME=/sbuild-nonexistent - see the User Environment: http://aws-logs.debian.net/ftbfs-logs/2013/07/26/psychopy_1.77.02.dfsg-1_unstable.log I'm not very familiar with cowbuilder, but if there's a way to set environment variables for the build with it, try setting HOME to a non-existent directory. Or add this near the start of debian/rules: export HOME=/sbuild-nonexistent A simple fix is probably to create a temporary directory and point HOME to it while running tests. That should fix the build with sbuild and is much better for reproducible tests than using someone's actual home directory. Cheers, Olly -- 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#718154: unreproducible (re: psychopy: FTBFS: Tests failed)
Processing control commands: tags -1 -unreproducible Bug #718154 [src:psychopy] psychopy: FTBFS: Tests failed Removed tag(s) unreproducible. -- 718154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718154 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#752973: marked as done (libopenws-java: FTBFS - missing artifact net.jcip:jcip-annotations:jar:debian)
Your message dated Fri, 12 Sep 2014 05:03:40 + with message-id e1xsj1i-0002zi...@franck.debian.org and subject line Bug#752973: fixed in libopenws-java 1.5.1-3 has caused the Debian Bug report #752973, regarding libopenws-java: FTBFS - missing artifact net.jcip:jcip-annotations:jar:debian 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.) -- 752973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopenws-java Version: 1.5.1-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] 1 required artifact is missing. for artifact: org.opensaml:openws:jar:1.5.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), shib-snapshot (https://build.shibboleth.net/nexus/content/repositories/snapshots), shib-release (https://build.shibboleth.net/nexus/content/groups/public) NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Fri Jun 27 23:35:13 UTC 2014 [INFO] Final Memory: 19M/1963M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael libopenws-java-build-log.txt.gz Description: application/gunzip pgpBXM1DG8Tjn.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: libopenws-java Source-Version: 1.5.1-3 We believe that the bug you reported is fixed in the latest version of libopenws-java, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill tmanc...@debian.org (supplier of updated libopenws-java 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: Thu, 11 Sep 2014 21:48:00 -0700 Source: libopenws-java Binary: libopenws-java libopenws-java-doc Architecture: source all Version: 1.5.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: tony mancill tmanc...@debian.org Description: libopenws-java - OpenWS libopenws-java-doc - Documentation for OpenWS Closes: 752973 Changes: libopenws-java (1.5.1-3) unstable; urgency=medium . * Team upload. * Add missing build-deps on libjcip-annotations-java and libmaven-javadoc-plugin-java to address FTBFS. (Closes: #752973) * Collapse Build-Depends-Indep into Build-Depends; the source package only builds arch:all binary packages. Checksums-Sha1: a636c36c2fe35a2586595e19381513d4fca667e5 2430 libopenws-java_1.5.1-3.dsc 65d0ac3f9052ed1d8e5d3df1165153ce93c5e668 3772 libopenws-java_1.5.1-3.debian.tar.xz 64d8b46d45c802f781902d51587fef2e9809c372 448694 libopenws-java_1.5.1-3_all.deb 231126ce65f6588c1566ffec66e117140e3a80e0 3235186 libopenws-java-doc_1.5.1-3_all.deb Checksums-Sha256: 7e2c1270e6a7e528aa7277fb25a2f96533e86ce368e628f4955693b93a7181f0 2430 libopenws-java_1.5.1-3.dsc 319ac76469c5fa7545a916e033c5676fcc9485332dbe12065405007db79b49ae 3772 libopenws-java_1.5.1-3.debian.tar.xz 942273a67cf244152b9eee0cac42fb583e330fa9d38cd8f271db116505deeb08 448694 libopenws-java_1.5.1-3_all.deb 1dcc71d5bc6bf977530227fb0e969c9b0724536c0ed151e2652ac0a2b01c402c 3235186 libopenws-java-doc_1.5.1-3_all.deb Files: 300d9373d0ff83e0702ebc4ba6844d22 448694 java optional libopenws-java_1.5.1-3_all.deb a6f8d7fe10547f9d484b0b9e8b5d52b2 3235186 doc optional libopenws-java-doc_1.5.1-3_all.deb 45045f1c9408fc98fb7f7e5535ad17b4 2430 java optional
