Bug#736782: [src:roundcube] Sourceless file
❦ 8 mai 2014 12:19 +1000, Ben Finney ben+deb...@benfinney.id.au : I could not find the source of: roundcube 0.9.5-4 (source) program/js/jquery.min.js program/js/jstz.min.js plugins/jqueryui/js/jquery-ui-1.9.1.custom.min.js There are other non-source files which should not be redistributed without confidence they have corresponding source in Debian. The simpler course is just to remove all those non-source JavaScript files. The attached patches against the current Git “master” branch add a ‘debian/repack’ program and invoke it from ‘uscan’. jstz.min.js has no source at all and we need it. The jquery-ui from Debian will introduce some bugs. See #731499. I'll apply the patches anyway since they allow to move forward. -- panic(Unable to find empty mailbox for aha1542.\n); 2.2.16 /usr/src/linux/drivers/scsi/aha1542.c signature.asc Description: PGP signature
Bug#737803: chocolate-doom: FTBFS: race during parallel installation
Am Montag, den 05.05.2014, 23:15 -0700 schrieb Vincent Cheng: Don't forget that the Debian Games team has a sponsorship queue [1] that you can use if you're looking for a sponsor within the team; I aim to regularly check the queue for packages to sponsor. Alright, I have added my pending uploads there. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659878: Reasons for this bug to be RC are very vague
severity 659878 important thanks The rationale for setting this bug report as release critical is really vague for me. breaks other software hasn't been really explained in details : it breaks su for some specific uses of it, so it may fit the definition of important but certainly not the one of grave -- signature.asc Description: Digital signature
Processed: Reasons for this bug to be RC are very vague
Processing commands for cont...@bugs.debian.org: severity 659878 important Bug #659878 [login] cannot set terminal process group (-1): Inappropriate ioctl for device Bug #663200 [login] login: su -c breaks the shell's job control Severity set to 'important' from 'grave' Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 659878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659878 663200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663200 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#747393: libsdformat2 and libsdformat1: error when trying to install together
Package: libsdformat1,libsdformat2 Version: libsdformat1/1.4.11-1 Version: libsdformat2/2.0.0-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-05-08 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: Selecting previously unselected package libboost-system1.54.0:amd64. (Reading database ... 10937 files and directories currently installed.) Preparing to unpack .../libboost-system1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-system1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libboost-filesystem1.54.0:amd64. Preparing to unpack .../libboost-filesystem1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-filesystem1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libboost-program-options1.54.0:amd64. Preparing to unpack .../libboost-program-options1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-program-options1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libicu52:amd64. Preparing to unpack .../libicu52_52.1-3_amd64.deb ... Unpacking libicu52:amd64 (52.1-3) ... Selecting previously unselected package libboost-regex1.54.0:amd64. Preparing to unpack .../libboost-regex1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-regex1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libboost-thread1.54.0:amd64. Preparing to unpack .../libboost-thread1.54.0_1.54.0-5_amd64.deb ... Unpacking libboost-thread1.54.0:amd64 (1.54.0-5) ... Selecting previously unselected package libtinyxml2.6.2:amd64. Preparing to unpack .../libtinyxml2.6.2_2.6.2-2_amd64.deb ... Unpacking libtinyxml2.6.2:amd64 (2.6.2-2) ... Selecting previously unselected package libconsole-bridge0.2:amd64. Preparing to unpack .../libconsole-bridge0.2_0.2.5-2_amd64.deb ... Unpacking libconsole-bridge0.2:amd64 (0.2.5-2) ... Selecting previously unselected package liburdfdom-model-state0.2:amd64. Preparing to unpack .../liburdfdom-model-state0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-model-state0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package liburdfdom-model0.2:amd64. Preparing to unpack .../liburdfdom-model0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-model0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package liburdfdom-sensor0.2:amd64. Preparing to unpack .../liburdfdom-sensor0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-sensor0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package liburdfdom-world0.2:amd64. Preparing to unpack .../liburdfdom-world0.2_0.2.10+dfsg-1_amd64.deb ... Unpacking liburdfdom-world0.2:amd64 (0.2.10+dfsg-1) ... Selecting previously unselected package libsdformat1:amd64. Preparing to unpack .../libsdformat1_1.4.11-1_amd64.deb ... Unpacking libsdformat1:amd64 (1.4.11-1) ... Selecting previously unselected package liburdfdom-model-state0.3:amd64. Preparing to unpack .../liburdfdom-model-state0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-model-state0.3:amd64 (0.3.0-1) ... Selecting previously unselected package liburdfdom-model0.3:amd64. Preparing to unpack .../liburdfdom-model0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-model0.3:amd64 (0.3.0-1) ... Selecting previously unselected package liburdfdom-sensor0.3:amd64. Preparing to unpack .../liburdfdom-sensor0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-sensor0.3:amd64 (0.3.0-1) ... Selecting previously unselected package liburdfdom-world0.3:amd64. Preparing to unpack .../liburdfdom-world0.3_0.3.0-1_amd64.deb ... Unpacking liburdfdom-world0.3:amd64 (0.3.0-1) ... Selecting previously unselected package libsdformat2:amd64. Preparing to unpack .../libsdformat2_2.0.0-2_amd64.deb ... Unpacking libsdformat2:amd64 (2.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libsdformat2_2.0.0-2_amd64.deb (--unpack): trying to overwrite '/usr/share/sdformat/1.3/model.sdf', which is also in package libsdformat1:amd64 1.4.11-1 Errors were encountered while processing: /var/cache/apt/archives/libsdformat2_2.0.0-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync):
Bug#747397: policykit-1 forces using systemd and may break systems with sysvinit after update
Package: policykit-1 Version: 0.105-5 Severity: critical Justification: makes unrelated software on the system (or the whole system) break Hi, I have just found that new version of policykit-1 forces using systemd on users systems: $ sudo apt-get install policykit-1 -V --no-install-recommends Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libcryptsetup4 (1.6.4-4) libpam-systemd (204-10) systemd (204-10) systemd-sysv (204-10) Suggested packages: systemd-ui (3-2) The following packages will be REMOVED: sysvinit-core (2.88dsf-53) The following NEW packages will be installed: libcryptsetup4 (1.6.4-4) libpam-systemd (204-10) systemd (204-10) systemd-sysv (204-10) The following packages will be upgraded: policykit-1 (0.105-4 = 0.105-5) 1 upgraded, 4 newly installed, 1 to remove and 1 not upgraded. Need to get 1368 kB of archives. After this operation, 5175 kB of additional disk space will be used. Do you want to continue? [Y/n] It may be normal to use systemd by default on new Debian installations, but why users with already installed Debian should be forced to use it without alternatives? Have you checked what this serious change will not break users systems after updating from Wheezy to Jessie? Next, I have checked what I will lose if I will remove this package: $ sudo apt-get purge policykit-1 -V --no-install-recommends Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: aptdaemon* (1.1.1-3) colord* (1.0.6-1) policykit-1* (0.105-5) polkit-kde-1* (0.99.1-1) 0 upgraded, 0 newly installed, 4 to remove and 1 not upgraded. After this operation, 4279 kB disk space will be freed. Do you want to continue? [Y/n] And it looks that policykit-1 cannot be safely removed without losing convenient work in KDE. Please solve this issue somehow. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): gah
Processing commands for cont...@bugs.debian.org:
reopen 665720
Bug #665720 {Done: Jonathan Wiltshire j...@debian.org} [iptables-persistent]
iptables-persistent: unusable with systemd
Bug reopened
Ignoring request to alter fixed versions of bug #665720 to the same values
previously set
severity 665720 critical
Bug #665720 [iptables-persistent] iptables-persistent: unusable with systemd
Severity set to 'critical' from 'important'
done
Unknown command or malformed arguments to command.
End of message, stopping processing here.
Please contact me if you need assistance.
--
665720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): merge 708459 743270
Processing commands for cont...@bugs.debian.org:
merge 708459 743270
Bug #708459 [src:cairo-5c] cairo-5c: FTBFS: make[3]: *** [check-TESTS] Error 1
Unable to merge bugs because:
severity of #743270 is 'normal' not 'serious'
package of #743270 is 'cairo-5c' not 'src:cairo-5c'
Failed to merge 708459: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2f637e0)',
'requester', 'Yunqiang Su wzss...@gmail.com', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'CAKcpw6U3=m-en1AA72ieqTMhBWDzUKE+U9QyOY=gtxztkxe...@mail.gma...',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x2ee5390)', 'limit', 'HASH(0x2edb990)', 'common_control_options',
'ARRAY(0x2edb9d8)', 'errors', ...) called at /usr/lib/debbugs/service line 474
stop
Stopping processing here.
Please contact me if you need assistance.
--
708459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708459
743270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743270
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#747054: FTBFS: package javax.servlet.http does not exist
Hi, I've rebuilt eclipse package in current sid using pbuilder and didn't encounter any error. Can someone please confirm this bug is still relevant? Regards, Jakub -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745307: Re-assigning to OCamlgraph
On Wed, May 07, 2014 at 08:51:48PM +0100, Peter Michael Green wrote: This bug is due to an API change appeared in OCamlgraph 1.8.4 and then reverted back in 1.8.5. OCamlgraph 1.8.3 (present testing's version) is not affected. Am I correct in thinking that means that the binnmus for dose3 should be given back? If this means whether dose3 should be rebuild against ocamlgraph 1.8.5: yes, please ! -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744099: Not grave!
How this bug can be considered GRAVE? Read here: https://www.debian.org/Bugs/Developer#severities Marking this as grave is preventing the version 34.0.1847.132-1 migrating to testing, thus many people cannot install the newer version due to #746034. And how this bug is blocking #746034? They are completely unrelated, IMHO. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Debian BTS #744099 and #747342
Processing commands for cont...@bugs.debian.org:
severity 744099 normal
Bug #744099 [chromium] update chromium
Bug #747135 [chromium] chromium: FTBFS on i386 due to 32bit linker
Severity set to 'normal' from 'grave'
Severity set to 'normal' from 'grave'
unblock 746034 by 744099
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
746034 was blocked by: 744099 747135
746034 was not blocking any bugs.
Removed blocking bug(s) of 746034: 744099 and 747135
forcemerge 746034 747342
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
Bug #747342 [chromium] chromium won't install because dependency libudev0 is a
virtual package
Marked Bug as done
Marked as fixed in versions chromium-browser/34.0.1847.116-2.
Marked as found in versions chromium-browser/33.0.1750.152-1 and
chromium-browser/34.0.1847.116-1~deb7u1.
Added tag(s) sid and jessie.
Bug #747342 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium won't install because dependency libudev0 is a virtual
package
Ignoring request to alter fixed versions of bug #747342 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #747342 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium won't install because dependency libudev0 is a virtual
package
Ignoring request to alter fixed versions of bug #747342 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #747342 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium won't install because dependency libudev0 is a virtual
package
Ignoring request to alter fixed versions of bug #747342 to the same values
previously set
After four attempts, the following changes were unable to be made:
fixed_versions of #747342 is 'chromium-browser/34.0.1847.116-2' not
'34.0.1847.116-2'
Failed to forcibly merge 746034: Unable to modify bugs so they could be merged.
End of message, stopping processing here.
Please contact me if you need assistance.
--
744099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744099
746034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746034
747135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747135
747342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747342
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#747402: missing license in debian/copyright
Package: libguestfs Version: 1:1.26.1-3 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: gnulib/* to debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 4 errors): Re: Debian BTS #744099 and #747342
Processing commands for cont...@bugs.debian.org:
severity 747135 grave
Bug #747135 [chromium] chromium: FTBFS on i386 due to 32bit linker
Bug #744099 [chromium] update chromium
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'
block 746034 by 747135
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
746034 was not blocked by any bugs.
746034 was not blocking any bugs.
Added blocking bug(s) of 746034: 744099 and 747135
2014-05-08 11:57 GMT+02:00 Alessio alga...@gmail.com:
Unknown command or malformed arguments to command.
severity 744099 normal
Unknown command or malformed arguments to command.
unblock 746034 by 744099
Unknown command or malformed arguments to command.
forcemerge 746034 747342
Unknown command or malformed arguments to command.
End of message, stopping processing here.
Please contact me if you need assistance.
--
744099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744099
746034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746034
747135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747135
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#700758: bcrypt: Bcrypt exposes patterns in data, it is broken
On Wed, Apr 09, 2014 at 01:09:40PM +0200, Agustin Martin wrote:
On Mon, Apr 07, 2014 at 12:38:16PM +0200, Agustin Martin wrote:
If something Debian-only is to be done with this package to keep it
available, it could be disabling encryption, together with a descriptive
error message. This would be a minimal intervention and have the advantages
of (1) and (2).
This should be documented in the package description and would allow users
to decrypt already encrypted data (you never know where that may appear),
but not to encrypt.
What maintainer thinks about this?
Note that this package has been proposed for removal (See cc'ed
http://bugs.debian.org/740748), so if any action is intended to keep this
package in the archive it should happen soon.
Although my C skills are not good I played a bit with this.
I'd expected attached patch to handle the encryption disabling.
Since I heard nothing from maintainer I plan a 0-day NMU with attached
patch. I noticed that I still have some stuff encrypted with bcrypt and
would not like to prepare a personal package just to deal with those not yet
found.
ftpmasters, what should I do regarding removal bug #740748?
I plan to upload encription-disabled bcrypt package closing #700758, wait for
it to reach testing in case any problem appear and then reassign #740748 to
bcrypt and forcemerge it with #700758.
Do you prefer both bug reports being closed on upload?
--
Agustin
From 4de49e57ba2cf5261951841ac68c44b55cfabef1 Mon Sep 17 00:00:00 2001
From: Agustin Martin Domingo agmar...@debian.org
Date: Tue, 8 Apr 2014 18:56:40 +0200
Subject: [PATCH] Disable encryption support. See http://bugs.debian.org/700758
[Bcrypt exposes patterns in data, it is broken]
---
debian/changelog | 8 +
debian/control | 4 ++-
debian/patches/00list | 1 +
.../patches/04_main.c_abort-on-encryption.dpatch | 39 ++
debian/patches/05_big_files.dpatch | 0
5 files changed, 51 insertions(+), 1 deletion(-)
create mode 100755 debian/patches/04_main.c_abort-on-encryption.dpatch
mode change 100644 = 100755 debian/patches/05_big_files.dpatch
diff --git a/debian/changelog b/debian/changelog
index 6a4195d..4cd20b7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+bcrypt (1.1-8.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Disable RC broken encryption support (Closes: #700758). Make this a
+decrypt-only package for already created files.
+
+ -- Agustin Martin Domingo agmar...@debian.org Thu, 08 May 2014 11:46:38 +0200
+
bcrypt (1.1-8) unstable; urgency=low
* Additional RC bug closed with patch added version 1.1-7. Closes: #693460.
diff --git a/debian/control b/debian/control
index 62b2f6e..0365c77 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,9 @@ Standards-Version: 3.8.3
Package: bcrypt
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Cross platform file encryption utility using blowfish
+Description: Cross platform file encryption utility using blowfish (Decrypt only)
+ WARNING: decrypt-only Debian package. Encryption disabled.
+ See http://bugs.debian.org/700758.
Bcrypt is a cross platform file encryption utility. Encrypted files are
portable across all supported operating systems and processors. In addition
to encrypting your data, bcrypt will by default overwrite the original input
diff --git a/debian/patches/00list b/debian/patches/00list
index 052aff1..3401a60 100644
--- a/debian/patches/00list
+++ b/debian/patches/00list
@@ -1 +1,2 @@
+04_main.c_abort-on-encryption
05_big_files
diff --git a/debian/patches/04_main.c_abort-on-encryption.dpatch b/debian/patches/04_main.c_abort-on-encryption.dpatch
new file mode 100755
index 000..66ab07f
--- /dev/null
+++ b/debian/patches/04_main.c_abort-on-encryption.dpatch
@@ -0,0 +1,39 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 04_main.c_abort-on-encryption.dpatch by Agustin Martin agmar...@debian.org
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Disable encryption support. See http://bugs.debian.org/700758
+## DP: Bcrypt exposes patterns in data, it is broken]
+
+@DPATCH@
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' bcrypt~/main.c bcrypt/main.c
+--- bcrypt~/main.c 2014-04-08 18:38:59.0 +0200
bcrypt/main.c 2014-04-08 18:39:57.855694078 +0200
+@@ -51,6 +51,11 @@
+ exit(1);
+ }
+
++int abort_on_encryption() {
++ fprintf(stderr, Encryption support disabled. See http://bugs.debian.org/700758\n;);
++ exit(1);
++}
++
+ int parseArgs(int *argc, char **argv, BCoptions *options) {
+ signed char ch;
+ char *progname;
+@@ -141,6 +146,7 @@
+ if (memcmp(*infile+(strlen(*infile) - 4), .bfe, 4) == 0)
+ return(1);
+
++
Processed (with 5 errors): Re: Debian BTS #744099 and #747342
Processing commands for cont...@bugs.debian.org: unmerge 744099 Bug #744099 [chromium] update chromium Bug #747135 [chromium] chromium: FTBFS on i386 due to 32bit linker Disconnected #744099 from all other report(s). severity 744099 normal Bug #744099 [chromium] update chromium Severity set to 'normal' from 'grave' 2014-05-08 12:21 GMT+02:00 Alessio alga...@gmail.com: Unknown command or malformed arguments to command. severity 747135 grave Unknown command or malformed arguments to command. block 746034 by 747135 Unknown command or malformed arguments to command. Unknown command or malformed arguments to command. 2014-05-08 11:57 GMT+02:00 Alessio alga...@gmail.com: Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 744099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744099 747135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Re: Debian BTS #744099 and #747342
Processing commands for cont...@bugs.debian.org:
unblock 746034 by 744099
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
746034 was blocked by: 744099 747135
746034 was not blocking any bugs.
Removed blocking bug(s) of 746034: 744099
2014-05-08 12:44 GMT+02:00 Alessio alga...@gmail.com:
Unknown command or malformed arguments to command.
unmerge 744099
Unknown command or malformed arguments to command.
severity 744099 normal
Unknown command or malformed arguments to command.
Unknown command or malformed arguments to command.
2014-05-08 12:21 GMT+02:00 Alessio alga...@gmail.com:
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
746034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746034
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#747405: missing license in debian/copyright
Package: ruby-gnome2 Version: 2.2.0-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing license of: goocanvas/sample/demo-fifteen.rb goocanvas/sample/demo-primitives.rb goocanvas/sample/demo.rb to debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744809: marked as done (FTBFS: writes to file outside package build dir)
Your message dated Thu, 08 May 2014 11:00:30 + with message-id e1wim3y-9k...@franck.debian.org and subject line Bug#744809: fixed in ruby-gnome2 2.2.0-1 has caused the Debian Bug report #744809, regarding FTBFS: writes to file outside package build dir to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 744809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-gnome2 Version: 2.1.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, your package ruby-gnome2 failed to build from source during a test rebuild of all ruby related packages, with this output: + make install DESTDIR=/«PKGBUILDDIR»/debian/tmp sitelibdir=/usr/lib/ruby/vendor_ruby sitearchdir=/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0 make[2]: Leaving directory `/«PKGBUILDDIR»' make[2]: Entering directory `/«PKGBUILDDIR»' (cd 'glib2' make install) make[3]: Entering directory `/«PKGBUILDDIR»/glib2' (cd ext/glib2 make install) make[4]: Entering directory `/«PKGBUILDDIR»/glib2/ext/glib2' /usr/bin/install -c -m 644 /«PKGBUILDDIR»/glib2/ext/glib2/rbglib.h /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0 /usr/bin/install: cannot create regular file '/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/rbglib.h': Permission denied make[4]: *** [install-headers] Error 1 The full build log can be found at: http://aws-logs.debian.net/ftbfs-logs/ruby-14-4-14/logs/ruby-gnome2_2.1.0-1_unstable.log -ch ---End Message--- ---BeginMessage--- Source: ruby-gnome2 Source-Version: 2.2.0-1 We believe that the bug you reported is fixed in the latest version of ruby-gnome2, 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 744...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul van Tilburg pau...@debian.org (supplier of updated ruby-gnome2 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: Tue, 06 May 2014 15:31:04 +0200 Source: ruby-gnome2 Binary: ruby-atk ruby-atk-dbg ruby-cairo-gobject ruby-cairo-gobject-dbg ruby-clutter ruby-clutter-gstreamer ruby-clutter-gtk ruby-gdk-pixbuf2 ruby-gdk-pixbuf2-dbg ruby-gdk3 ruby-gdk3-dbg ruby-gio2 ruby-gio2-dbg ruby-glib2 ruby-glib2-dbg ruby-gnome2 ruby-gnome2-dev ruby-gobject-introspection ruby-gobject-introspection-dbg ruby-gstreamer ruby-gstreamer-dbg ruby-gtk2 ruby-gtk2-dbg ruby-gtk3 ruby-gtk3-dbg ruby-gtksourceview2 ruby-gtksourceview2-dbg ruby-gtksourceview3 ruby-gtksourceview3-dbg ruby-pango ruby-pango-dbg ruby-poppler ruby-poppler-dbg ruby-rsvg2 ruby-rsvg2-dbg ruby-vte ruby-vte-dbg ruby-vte3 ruby-vte3-dbg ruby-webkit-gtk ruby-webkit-gtk2 Architecture: source amd64 all Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Paul van Tilburg pau...@debian.org Description: ruby-atk - ATK bindings for the Ruby language ruby-atk-dbg - ATK bindings for the Ruby language (debugging symbols) ruby-cairo-gobject - CairoGObject bindings for the Ruby language ruby-cairo-gobject-dbg - CairoGObject bindings for the Ruby language (debugging symbols) ruby-clutter - Clutter bindings for the Ruby language ruby-clutter-gstreamer - Clutter-GStreamer bindings for the Ruby language ruby-clutter-gtk - Clutter-Gtk bindings for the Ruby language ruby-gdk-pixbuf2 - Gdk-Pixbuf 2 bindings for the Ruby language ruby-gdk-pixbuf2-dbg - Gdk-Pixbuf 2 bindings for the Ruby language (debugging symbols) ruby-gdk3 - GDK 3 bindings for the Ruby language ruby-gdk3-dbg - GDK 3 bindings for the Ruby language (debugging symbols) ruby-gio2 - GIO bindings for the Ruby language ruby-gio2-dbg - GIO bindings for the Ruby language (debugging symbols) ruby-glib2 - GLib 2 bindings for the Ruby language ruby-glib2-dbg - GLib 2 bindings for the Ruby language (debugging symbols) ruby-gnome2 - GNOME-related bindings for the Ruby language ruby-gnome2-dev - GNOME-related bindings for the Ruby language (development files) ruby-gobject-introspection - GObject
Bug#747410: meep: ignores errors from ./configure
Source: meep Version: 1.1.1-9 Severity: serious Your package ignores errors from ./configure. You shouldn't do that. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: meep: please migrate to guile-2.0
Processing commands for cont...@bugs.debian.org: severity 746007 serious Bug #746007 [meep] meep: please migrate to guile-2.0 Severity set to 'serious' from 'normal' retitle 746007 meep: FTBFS with guile-2.0 Bug #746007 [meep] meep: please migrate to guile-2.0 Changed Bug title to 'meep: FTBFS with guile-2.0' from 'meep: please migrate to guile-2.0' thanks Stopping processing here. Please contact me if you need assistance. -- 746007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746007 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#702005: Bug #702005: Where can i get more attention on this?
Ian Jackson writes (Re: Bug #702005: Where can i get more attention on this?): [some stuff to Luis Alejandro Martínez Faneyth l...@huntingbears.com.ve] Unfortunately, Luis's mail domain is hosted at Hotmail which hates chiark: l...@huntingbears.com.ve SMTP error from remote mail server after MAIL FROM:ijack...@chiark.greenend.org.uk SIZE=4130: host 3fd47c7f131f4ca31143ff3af72008.pamx1.hotmail.com [65.54.188.78]: 550 SC-002 (BAY0-PAMC1-F10) Unfortunately, messages from 212.13.197.229 weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. (I know of the causes of this; I disagree with Hotmail and resolving things is nontrivial.) So hopefully Luis will see my reply here on -devel or in the bug. Luis, if you want to email me, please use a different email address that doesn't go to Hotmail. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702005: Bug #702005: Where can i get more attention on this?
Luis Alejandro Martínez Faneyth writes (Bug #702005: Where can i get more attention on this?): I'm a little worried about bug #702005 and the lack of attention it's getting. This bug is marked as resolved, and indeed it has been resolved for jessie and sid, but not for wheezy. This bug breaks Python 2.7. Every person that tries to upgrade python2.7 and python2.7-minimal from version 2.7.3-6 to 2.7.3-6+deb7u2, is affected by this bug. It's not clear from your messages here on -devel exactly what you think the right next step is. Reading the bug report, I think you are suggesting that a particular patch should be backported to debian-stable. Please, can someone upload the fix to wheezy also? Or, how can i help? Thanks, Uploads to stable following the process documented here: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable So the next step would be to file a bug against release.debian.org asking for approval for inclusion of this patch in stable. That approval request should come with clear explanation (from first principles, aimed at someone who doesn't necessarily follow the intricacies of the python packaging), of both the bug and the fix. If you like I would be happy to review a draft of such an explanation if you were to write one. If you produce an explanation that satisfies me, and you get approval from the stable team, I would also be happy to review and sponsor your upload. If you would like to try to take the lead in this way, it's probably best to email me privately, perhaps CC the bug, with your drafts etc. I don't think debian-devel need to see all of this. This is affecting also every debian derivative based on stable, and is worth mentioning: Of course we should try to do a good job in stable, but of course one thing that a derivative can be expected to diverge on is questions of release management. Usually most of the work in backporting a fix is not in the technical work of preparing the package - it is in analysing whether the fix is appropriate for users or stable (and indeed, in persuading the relevant release managemers). Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747418: belle-sip: FTBFS on kfreebsd-i386 (internal error: belle_sdp.g : java.lang.NullPointerException)
Source: belle-sip Version: 1.3.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on kfreebsd-i386 in sid: https://buildd.debian.org/status/fetch.php?pkg=belle-siparch=kfreebsd-i386ver=1.3.0-1%2Bb1stamp=1399545979 /usr/bin/antlr3 -make -Xmultithreaded -fo . belle_sdp.g two-threaded DFA conversion error(10): internal error: belle_sdp.g : java.lang.NullPointerException org.antlr.analysis.DFAState.transition(DFAState.java:177) org.antlr.analysis.DFA.createMinMaxTables(DFA.java:500) org.antlr.analysis.DFA.createStateTables(DFA.java:435) org.antlr.codegen.CodeGenerator.genLookaheadDecision(CodeGenerator.java:653) org.antlr.grammar.v2.CodeGenTreeWalker.block(CodeGenTreeWalker.java:1018) org.antlr.grammar.v2.CodeGenTreeWalker.ebnf(CodeGenTreeWalker.java:1858) org.antlr.grammar.v2.CodeGenTreeWalker.element(CodeGenTreeWalker.java:1704) org.antlr.grammar.v2.CodeGenTreeWalker.alternative(CodeGenTreeWalker.java:1306) org.antlr.grammar.v2.CodeGenTreeWalker.block(CodeGenTreeWalker.java:1081) org.antlr.grammar.v2.CodeGenTreeWalker.rule(CodeGenTreeWalker.java:797) org.antlr.grammar.v2.CodeGenTreeWalker.rules(CodeGenTreeWalker.java:588) org.antlr.grammar.v2.CodeGenTreeWalker.grammarSpec(CodeGenTreeWalker.java:530) org.antlr.grammar.v2.CodeGenTreeWalker.grammar(CodeGenTreeWalker.java:348) org.antlr.codegen.CodeGenerator.genRecognizer(CodeGenerator.java:432) org.antlr.Tool.generateRecognizer(Tool.java:641) org.antlr.Tool.process(Tool.java:454) org.antlr.Tool.main(Tool.java:91) make[4]: *** [belle_sdpParser.c] Error 1 Cheers, Julien signature.asc Description: Digital signature
Bug#747420: libsword-dev: libsword.so is a broken symlink
Package: libsword-dev Version: 1.7.2+dfsg-1 Severity: grave Justification: renders package unusable libsword10 ships libsword.so.10. libsword-dev ships libsword.so as a symlink to libsword.so.9. Cheers, Julien signature.asc Description: Digital signature
Bug#715569: Ack
Just hit this bug also. Was testing out vroot, and had some weird issues (not chrooting), and it wasn't clear why. Then I found this report. Did rebuild the package with pbuilder and installed it. And now it just works fine! Could this package just be rebuild? Thanks Jean-Louis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745307: Re-assigning to OCamlgraph
Le 2014-05-07 21:51, Peter Michael Green a écrit : This bug is due to an API change appeared in OCamlgraph 1.8.4 and then reverted back in 1.8.5. OCamlgraph 1.8.3 (present testing's version) is not affected. Am I correct in thinking that means that the binnmus for dose3 should be given back? Yes. Thanks for the notice. I just did that now. Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702005: Bug #702005: Where can i get more attention on this?
Thanks, Ian. I will be following the steps you pinted out so that this fix lands on stable. I will email you privately in a couple of hours. Greetings, Luis. From: ijack...@chiark.greenend.org.uk Date: Thu, 8 May 2014 13:03:11 +0100 To: l...@huntingbears.com.ve CC: debian-de...@lists.debian.org; 702...@bugs.debian.org Subject: Re: Bug #702005: Where can i get more attention on this? Luis Alejandro Martínez Faneyth writes (Bug #702005: Where can i get more attention on this?): I'm a little worried about bug #702005 and the lack of attention it's getting. This bug is marked as resolved, and indeed it has been resolved for jessie and sid, but not for wheezy. This bug breaks Python 2.7. Every person that tries to upgrade python2.7 and python2.7-minimal from version 2.7.3-6 to 2.7.3-6+deb7u2, is affected by this bug. It's not clear from your messages here on -devel exactly what you think the right next step is. Reading the bug report, I think you are suggesting that a particular patch should be backported to debian-stable. Please, can someone upload the fix to wheezy also? Or, how can i help? Thanks, Uploads to stable following the process documented here: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable So the next step would be to file a bug against release.debian.org asking for approval for inclusion of this patch in stable. That approval request should come with clear explanation (from first principles, aimed at someone who doesn't necessarily follow the intricacies of the python packaging), of both the bug and the fix. If you like I would be happy to review a draft of such an explanation if you were to write one. If you produce an explanation that satisfies me, and you get approval from the stable team, I would also be happy to review and sponsor your upload. If you would like to try to take the lead in this way, it's probably best to email me privately, perhaps CC the bug, with your drafts etc. I don't think debian-devel need to see all of this. This is affecting also every debian derivative based on stable, and is worth mentioning: Of course we should try to do a good job in stable, but of course one thing that a derivative can be expected to diverge on is questions of release management. Usually most of the work in backporting a fix is not in the technical work of preparing the package - it is in analysing whether the fix is appropriate for users or stable (and indeed, in persuading the relevant release managemers). Ian. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/21355.29311.737503.869...@chiark.greenend.org.uk
Bug#742493: marked as done (Segfault with libmemcached11)
Your message dated Thu, 08 May 2014 13:26:16 + with message-id e1wiol2-0001yg...@franck.debian.org and subject line Bug#742493: fixed in pgmemcache 2.1.2-2 has caused the Debian Bug report #742493, regarding Segfault with libmemcached11 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.) -- 742493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postgresql-9.3-pgmemcache Version: 2.1.2-1+b1 Severity: grave The binnum to update the dependency from libmemcached10 to libmemcached11 seems to have broken the PostgreSQL module: http://ci.debian.net/data/unstable-amd64/packages/p/pgmemcache/2014-03-23.log Also in my chroot: test init ... ok test start_memcached ... ok test test ... FAILED (test process exited with exit code 2) test stop_memcached ... ok 2014-03-24 13:16:05 CET LOG: Serverprozess (PID 25224) wurde von Signal 11 beendet: Segmentation fault 2014-03-24 13:16:05 CET DETAIL: Der fehlgeschlagene Prozess führte aus: SELECT regexp_replace(memcache_stats(), 'pid:.*', '') AS memcache_stats; 2014-03-24 13:16:05 CET LOG: aktive Serverprozesse werden abgebrochen 2014-03-24 13:16:05 CET WARNUNG: breche Verbindung ab wegen Absturz eines anderen Serverprozesses 2014-03-24 13:16:05 CET DETAIL: Der Postmaster hat diesen Serverprozess angewiesen, die aktuelle Transaktion zurückzurollen und die Sitzung zu beenden, weil ein anderer Serverprozess abnormal beendet wurde und möglicherweise das Shared Memory verfälscht hat. ! psql:test.sql:2: SSL SYSCALL error: EOF detected ! psql:test.sql:2: connection to server was lost Christoph -- c...@df7cb.de | http://www.df7cb.de/ ---End Message--- ---BeginMessage--- Source: pgmemcache Source-Version: 2.1.2-2 We believe that the bug you reported is fixed in the latest version of pgmemcache, 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 742...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg christoph.b...@credativ.de (supplier of updated pgmemcache 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, 08 May 2014 13:55:14 +0200 Source: pgmemcache Binary: postgresql-9.3-pgmemcache Architecture: source amd64 Version: 2.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers pkg-postgresql-pub...@lists.alioth.debian.org Changed-By: Christoph Berg christoph.b...@credativ.de Description: postgresql-9.3-pgmemcache - PostgreSQL interface to memcached Closes: 742493 Changes: pgmemcache (2.1.2-2) unstable; urgency=medium . * Import cb06b448c534ac99ddd08f264e6f86162ddd6b72 from upstream: correct free function for memcached_stat_get_value (Closes: #742493) Checksums-Sha1: 194e5a8758778f0868e4306db1d42a597aa7035e 2132 pgmemcache_2.1.2-2.dsc d1c4b7aaa309306fc68379d2e9fd036dba417ee8 4556 pgmemcache_2.1.2-2.debian.tar.xz b32d8c1b336417cda5e1322183ab08eca313c6c9 20064 postgresql-9.3-pgmemcache_2.1.2-2_amd64.deb Checksums-Sha256: 511ffa0337ec02ef3b61841f5a6806e060c1560b358b28e1fd023f75792f2237 2132 pgmemcache_2.1.2-2.dsc 9fb25085c569effcff4bb5b76931c6df79b109c99f065dedbe8a1b32bcae103c 4556 pgmemcache_2.1.2-2.debian.tar.xz 25a6d42cfd8c3821860e6f29f7a676831eec68bb589a71db9c9dd02f3bee0f04 20064 postgresql-9.3-pgmemcache_2.1.2-2_amd64.deb Files: 09e5837b7ad2955c6b8abfb648b04c67 20064 database extra postgresql-9.3-pgmemcache_2.1.2-2_amd64.deb 91221eb97bed31d0c89601d7fac51fe7 2132 database extra pgmemcache_2.1.2-2.dsc 4c874ca36d465e19df35c0dd4de591c5 4556 database extra pgmemcache_2.1.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTa3pRAAoJEExaa6sS0qeu3CQQAIWvJmO7wi4LjQE1SOiv+PTh nfTOi0GOetDsT4z0o/Ng5FaLK5cmFf0bVP05WEDhosKn0DQvTqQCbZbt19tVSNDH sSq6l0jY3NdATRBNr7J4/SbK78XodrYNksahYoE8due9unuLpTEGp8MBCDxjxkaY N5SW6DcPozU8+9lnbb3gZDwnxsiJcNVRfnSWwHORrp4BSNHd5uwoSjmLNNdjAYgl iZL1c09eercwq5MIl8M9OPddSQYToohMCJ+v+zp+Xi8WQ9Izk9yAxHECgA/rE7Ps 7SJJ+Ntz+uVBXTJAyohXKfEufB13pvxu5MKQzHnc03XB3efrd9ivNPIjT1075aDC
Bug#742493: [Pkg-postgresql-public] Bug#742493: Bug#742493: pgmemcache segfaults with libmemcached11
Re: To Hannu Valtonen 2014-05-02 20140502135529.gb14...@msgid.df7cb.de
Re: Hannu Valtonen 2014-05-02 53639ce0.30...@ohmu.fi
Hi,
This has now been fixed by:
https://github.com/ohmu/pgmemcache/commit/47623a545be485d6dd1ffb917e990d267ad57f35
Hi,
we've had a closer look at this patch. Assuming pfree() is
PostgreSQL's free() variant (which I believe it is), it looks like
using pfree() was wrong in the first place, and the standard libc
free() should be used, whatever libmemcached version is used.
I think the following patch does the right thing:
Index: pgmemcache/pgmemcache.c
===
--- pgmemcache.orig/pgmemcache.c2014-05-08 15:25:30.260692035 +0200
+++ pgmemcache/pgmemcache.c 2014-05-08 15:27:13.164195600 +0200
@@ -818,10 +818,10 @@ static memcached_return_t server_stat_fu
{
char *value = memcached_stat_get_value(ptr, stat, *stat_ptr, rc);
appendStringInfo(context, %s: %s\n, *stat_ptr, value);
- libmc_stat_free(value);
+ free(value);
}
- pfree(list);
+ free(list);
return MEMCACHED_SUCCESS;
}
Index: pgmemcache/pgmemcache.h
===
--- pgmemcache.orig/pgmemcache.h2014-05-08 15:25:30.260692035 +0200
+++ pgmemcache/pgmemcache.h 2014-05-08 15:27:13.224195312 +0200
@@ -36,13 +36,6 @@
#undef PACKAGE_TARNAME
#undef PACKAGE_VERSION
-/* libmemcached 1.0.16 changed the allocation function for values returned
from memcached_stat_get_value */
-#if LIBMEMCACHED_VERSION_HEX = 0x0116
- #define libmc_stat_free free
-#else
- #define libmc_stat_free pfree
-#endif
-
void _PG_init(void);
void _PG_fini(void);
Do you plan to release a new version, or should I apply the patch to
the current version in Debian for now?
Christoph
--
c...@df7cb.de | http://www.df7cb.de/
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: LO 4.2 now in sid - bug now RC
Processing commands for cont...@bugs.debian.org: severity 743634 serious Bug #743634 [libreoffice-accessodf] libreoffice-accessodf: MessageBox API changed in LO 4.2 :/ Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 743634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: pacemaker: FTBFS: configure: error: Unable to support SNMP
Processing commands for cont...@bugs.debian.org: # the FTBFS also happens with the version in jessie, when trying to build it # in jessie or sid found 746141 1.1.7-2.1 Bug #746141 [src:pacemaker] pacemaker: FTBFS: configure: error: Unable to support SNMP Marked as found in versions pacemaker/1.1.7-2.1. thanks Stopping processing here. Please contact me if you need assistance. -- 746141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746141 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: mark 732424 serious
Processing commands for cont...@bugs.debian.org: severity 732424 serious Bug #732424 [gstreamer0.10] gstreamer0.10: deprecated option YYLEX_PARAM has been removed from bison leading to FTBFS Severity set to 'serious' from 'important' stop Stopping processing here. Please contact me if you need assistance. -- 732424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732424 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#747428: [xbmc] passwords are stored in plain xml file
Package: xbmc Version: 2:13.0+dfsg1-1 Severity: grave Tags: security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org Hi, I just add a webdav source in xbmc, so it asks for a username and password. But these informations are then stored in a plain XML file: ~/.xbmc/userdata/sources.xml, moreover a world readable file: adrien ~/ $ ls -l .xbmc/userdata/sources.xml -rw-r--r-- 1 adrien adrien 1006 mai8 16:34 .xbmc/userdata/sources.xml This file should be at least chmod 700 and the users should be informed that the password will be stored in a unsafe manner. Regards, Adrien --- System information. --- Architecture: amd64 Kernel: Linux 3.13-1-amd64 Debian Release: jessie/sid 900 testing security.debian.org 900 testing ftp.fr.debian.org 800 unstableftp.fr.debian.org 700 experimentalftp.fr.debian.org --- Package information. --- Depends(Version) | Installed -+-=== xbmc-bin (= 2:13.0+dfsg1-1) | 2:13.0+dfsg1-1 xbmc-bin ( 2:13.0+dfsg1-1.1~) | 2:13.0+dfsg1-1 mesa-utils | 8.1.0-2+b1 x11-utils| 7.7+1 fonts-dejavu-core| 2.34-1 OR ttf-dejavu-core | 2.34-1 fonts-roboto | 1:4.3-3 libjs-jquery | 1.7.2+dfsg-3 libjs-iscroll| 5.1.1+dfsg1-1 python-imaging | 2.3.0-2 python:any (= 2.7.5-5~) | Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#746577: closed by Michael Biebl bi...@debian.org (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)
On 05/06/2014 01:37 AM, Martin Pitt wrote: Zack Weinberg [2014-05-05 20:29 -0400]: I contend that, therefore, systemd-sysv, sysvinit-core, *and* systemd-shim (and upstart as well) (quotation marks indicate package names) should *all* be coinstallable; an upgrade from wheezy should install *both* systemd-sysv and systemd-shim if not already present, and leave sysvinit-core installed; and a mechanism independent of package management should control which init brings up the system on the next boot. Isn't the sysvinit package now meant to provide this selector? I don't know if it's debconfified or similar, but having such a selector package was the reason for moving the old sysvinit to s-core, wasn't it? The description does imply that that is the intent, but I would say that it doesn't *fullfill* that intent right now. It has no contents outside /usr/share/doc; its sole effect is by being Essential and declaring a Pre-Depends on sysvinit-core|upstart|systemd-sysv, thus ensuring that at least one of those packages is installed at all times. Meanwhile, all three of those packages ship /sbin/init (and a bunch of related files) and accordingly there are Conflicts and Breaks sufficient to ensure that *only* one of those three packages can be installed at any time. In other words, right now one may select among these three init systems by installing and removing packages, but it is not possible to have them all installed at the same time and select among them in some other fashion (e.g. changing what /sbin/init is symlinked to). And this is exactly what I consider to be a bug. [To reiterate, my primary rationale for considering this a bug is that if an upgrade switches you from sysvinit to systemd and this breaks the boot, it may be extremely difficult to recover, because you may be reduced to booting with init=/bin/sh, you probably will then need to download packages in order to undo the conversion, and it can be extremely difficult to bring up the network manually while booted with init=/bin/sh, e.g. if your only source of connectivity is a USB modem. A secondary rationale is that it will be significantly less hassle for daemon package maintainers to test their packages with more than one init system if they can have them all installed at the same time.] I did a bit more digging into how it works right now in response to Tolleef's message. First, systemd-shim currently doesn't conflict with systemd-sysv or systemd, or vice versa. I don't know how systemd-shim works. Does it properly get out of the way if the running PID 1 is in fact systemd? Yes, it does, that's how it was designed. It provides a D-BUS activatable, and heavily reduced, interface for things like suspend or setting the time zone. But if you run the real systemd, those D-BUS objects already exists, and thus the D-BUS .service file is entirely ignored. OK, that's good. Second, it might simplify matters to split the programs 'telinit', 'halt', 'poweroff', 'reboot', 'runlevel', and 'shutdown', and their manpages, to a separate package shared among all supported init implementations. Would that actually work? I thought that the implementation of these depended on the current init system in use? At least when I tried to move from upstart to sysvinit on a fresh vserver that I got recently, all these (reboot, etc.) were broken. My understanding is that they do all contain code specific to their own init system, but it shouldn't be *too* hard to write either shell wrappers or generic implementations that can detect the running init and behave appropriately. Some of this work may already have been done: at least, the systemd implementation of 'reboot' seems to be able to direct sysvinit /sbin/init to reboot. zw signature.asc Description: OpenPGP digital signature
Bug#742493: [Pkg-postgresql-public] Bug#742493: Bug#742493: pgmemcache segfaults with libmemcached11
Hi,
http://bazaar.launchpad.net/~tangent-trunk/libmemcached/1.0/revision/1121.1.13
You're misreading the change. Basically libmemcached stopped using the
custom memory allocator and changed to using malloc unconditionally,
breaking backwards compatibility. Before the change it used the custom
memory allocator which in our case was palloc.
- Hannu
On 8.5.2014 16.32, Christoph Berg wrote:
Re: To Hannu Valtonen 2014-05-02 20140502135529.gb14...@msgid.df7cb.de
Re: Hannu Valtonen 2014-05-02 53639ce0.30...@ohmu.fi
Hi,
This has now been fixed by:
https://github.com/ohmu/pgmemcache/commit/47623a545be485d6dd1ffb917e990d267ad57f35
Hi,
we've had a closer look at this patch. Assuming pfree() is
PostgreSQL's free() variant (which I believe it is), it looks like
using pfree() was wrong in the first place, and the standard libc
free() should be used, whatever libmemcached version is used.
I think the following patch does the right thing:
Index: pgmemcache/pgmemcache.c
===
--- pgmemcache.orig/pgmemcache.c2014-05-08 15:25:30.260692035 +0200
+++ pgmemcache/pgmemcache.c 2014-05-08 15:27:13.164195600 +0200
@@ -818,10 +818,10 @@ static memcached_return_t server_stat_fu
{
char *value = memcached_stat_get_value(ptr, stat, *stat_ptr, rc);
appendStringInfo(context, %s: %s\n, *stat_ptr, value);
- libmc_stat_free(value);
+ free(value);
}
- pfree(list);
+ free(list);
return MEMCACHED_SUCCESS;
}
Index: pgmemcache/pgmemcache.h
===
--- pgmemcache.orig/pgmemcache.h2014-05-08 15:25:30.260692035 +0200
+++ pgmemcache/pgmemcache.h 2014-05-08 15:27:13.224195312 +0200
@@ -36,13 +36,6 @@
#undef PACKAGE_TARNAME
#undef PACKAGE_VERSION
-/* libmemcached 1.0.16 changed the allocation function for values returned from memcached_stat_get_value */
-#if LIBMEMCACHED_VERSION_HEX = 0x0116
- #define libmc_stat_free free
-#else
- #define libmc_stat_free pfree
-#endif
-
void _PG_init(void);
void _PG_fini(void);
Do you plan to release a new version, or should I apply the patch to
the current version in Debian for now?
Christoph
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: policykit-1 forces using systemd and may break systems with sysvinit after update
Processing commands for cont...@bugs.debian.org:
forcemerge 747105 747397
Bug #747105 {Done: Michael Biebl em...@michaelbiebl.de} [policykit-1]
policykit-1: depends on systemd
Bug #747397 [policykit-1] policykit-1 forces using systemd and may break
systems with sysvinit after update
Marked Bug as done
Merged 747105 747397
thanks
Stopping processing here.
Please contact me if you need assistance.
--
747105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747105
747397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747397
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#744337: marked as done (gradle: FTBFS: java.lang.OutOfMemoryError: Java heap space)
Your message dated Thu, 8 May 2014 13:14:16 -0300
with message-id 20140508161416.ga20...@alice.nomadium.lan
and subject line Re: gradle: FTBFS: java.lang.OutOfMemoryError: Java heap space
has caused the Debian Bug report #744337,
regarding gradle: FTBFS: java.lang.OutOfMemoryError: Java heap space
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.)
--
744337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:gradle
Version: 1.4-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I tried to build some package with Gradle and it failed.
So, I checked gradle itself and I'm unable to build it as well.
It dies on me with some memory errors:
dpkg-source -b gradle-1.4
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building gradle using existing ./gradle_1.4.orig.tar.gz
dpkg-source: info: building gradle in gradle_1.4-2.debian.tar.xz
dpkg-source: info: building gradle in gradle_1.4-2.dsc
debian/rules build
dh build --with javahelper
dh_testdir
dh_auto_configure
jh_linkjars
debian/rules override_dh_auto_build
make[1]: Entering directory `/tmp/buildd/gradle-1.4'
find /usr/share/gradle -type l ! -exec test -r {} \; -print
mkdir /tmp/buildd/gradle-1.4/.gradlehome
gradle --project-prop finalRelease=true --stacktrace --offline assemble
java.lang.OutOfMemoryError: Java heap space
at java.util.ArrayList.init(ArrayList.java:144)
at
org.codehaus.groovy.reflection.GeneratedMetaMethod$DgmMethodRecord.loadDgmInfo(GeneratedMetaMethod.java:193)
at
org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.registerMethods(MetaClassRegistryImpl.java:155)
at
org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.init(MetaClassRegistryImpl.java:83)
at
org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.init(MetaClassRegistryImpl.java:61)
at groovy.lang.GroovySystem.clinit(GroovySystem.java:29)
at
org.gradle.api.internal.AbstractClassGenerator.generate(AbstractClassGenerator.java:100)
at
org.gradle.api.internal.ClassGeneratorBackedInstantiator.newInstance(ClassGeneratorBackedInstantiator.java:36)
at
org.gradle.initialization.DefaultGradleLauncherFactory.doNewInstance(DefaultGradleLauncherFactory.java:126)
at
org.gradle.initialization.DefaultGradleLauncherFactory.newInstance(DefaultGradleLauncherFactory.java:99)
at
org.gradle.initialization.DefaultGradleLauncherFactory.newInstance(DefaultGradleLauncherFactory.java:46)
at
org.gradle.launcher.exec.InProcessGradleLauncherActionExecuter.execute(InProcessGradleLauncherActionExecuter.java:38)
at
org.gradle.launcher.exec.InProcessGradleLauncherActionExecuter.execute(InProcessGradleLauncherActionExecuter.java:25)
at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:50)
at
org.gradle.api.internal.Actions$RunnableActionAdapter.execute(Actions.java:171)
at
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:201)
at
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:174)
at
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:170)
at
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:139)
at
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at org.gradle.launcher.Main.doAction(Main.java:48)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at org.gradle.launcher.Main.main(Main.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:50)
at
org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:32)
at org.gradle.launcher.GradleMain.main(GradleMain.java:26)
FAILURE: Build failed with an exception.
* What went wrong:
Build aborted because of an internal
Bug#742493: [Pkg-postgresql-public] Bug#742493: Bug#742493: pgmemcache segfaults with libmemcached11
Re: Hannu Valtonen 2014-05-08 536bad38.7090...@ohmu.fi
http://bazaar.launchpad.net/~tangent-trunk/libmemcached/1.0/revision/1121.1.13
You're misreading the change. Basically libmemcached stopped using the
custom memory allocator and changed to using malloc unconditionally,
breaking backwards compatibility. Before the change it used the custom
memory allocator which in our case was palloc.
Ok.
Still, shouldn't the other pfree(list) there be changed as well?
--- pgmemcache.orig/pgmemcache.c 2014-05-08 15:25:30.260692035 +0200
+++ pgmemcache/pgmemcache.c 2014-05-08 15:27:13.164195600 +0200
@@ -818,10 +818,10 @@ static memcached_return_t server_stat_fu
{
char *value = memcached_stat_get_value(ptr, stat, *stat_ptr, rc);
appendStringInfo(context, %s: %s\n, *stat_ptr, value);
- libmc_stat_free(value);
+ free(value);
}
- pfree(list);
+ free(list);
return MEMCACHED_SUCCESS;
}
Christoph
--
c...@df7cb.de | http://www.df7cb.de/
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747397: policykit-1 forces using systemd and may break systems with sysvinit after update
Hi, As explained on #747105 policykit-1 only depends against libpam-systemd which in turns depends against systemd-sysv | systemd-shim. But systemd package will be installed in any case. Not a big problem though... If you don't want to use systemd as PID1 you can install systemd-shim. Ok. But if I understand correctly policykit will be limited in functionality in this case. Which its functions will be lost? Also please in the future report bugs about actual breakage not hypothetical ones, thanks. Sorry, but I am a very cautious during updating system, especially when some changes may do my system unbootable. Maybe I will find time to check this update in VirtualBox later. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746577: closed by Michael Biebl bi...@debian.org (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)
On 05/06/2014 02:39 AM, Michael Stapelberg wrote: Hi Zack, Zack Weinberg za...@panix.com writes: Note that coinstallability is not enough -- the bulletproof procedure (e.g. update-init-system) must also be implemented, shipped, and documented. Your tone is way out of line. Who are you to tell us what we _must_ do? That’s not how it works. I apologize. I write like that because I do a lot of standards work. It's the RFC 2119 must, and in this context I don't mean anything more by it than that I personally consider this necessary for a satisfactory resolution of the bug I filed. Either you do the work and convince us we should merge it or you make suggestions. But you cannot tell us what we must do in our spare time. I am certainly prepared to do at least some of the work here, but since it involves coordinated changes to several different packages maintained by different groups, it seems best to get agreement on a plan first. zw signature.asc Description: OpenPGP digital signature
Bug#746577: closed by Michael Biebl bi...@debian.org (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)
On 05/06/2014 08:08 AM, Tollef Fog Heen wrote: ]] Zack Weinberg On Mon, May 5, 2014 at 5:40 PM, Tollef Fog Heen tfh...@err.no wrote: ]] Zack Weinberg Fundamentally what I want is a bulletproof procedure for reverting to sysvinit in case something goes wrong. Sounds like you're arguing that sysvinit-core should no longer ship /sbin/init, then, so systemd-sysv doesn't have to conflict with it. Wouldn't that make the sysvinit implementation of /sbin/init completely unavailable? This is an earnest question. I do not have access to package contents right now. No, to revert you'd boot with init=/sbin/sysvinit. Ah, I understand now. Yes, this + systemd-sysv and upstart *also* stop shipping /sbin/init (it becomes a symlink under control of the administrator) + documentation would be a satisfactory conclusion as far as I'm concerned. If we were to also move 'reboot' and friends to a shared utilities package, that might make the systemd-sysv package unnecessary. Ideally, also, if systemd is installed on a system that is currently running sysvinit, that doesn't change what /sbin/init points to; the administrator has to do that as a separate operation. This provides an additional bit of defense against unforeseen problems with local customizations -- the admin can look into them in their own time rather than immediately. Note that coinstallability is not enough -- the bulletproof procedure (e.g. update-init-system) must also be implemented, shipped, and documented. I have still not seen any reason whatsoever for this to be a command rather than just changing a configuration file. I have no problem with that. I suggested a command because I thought the switch might be more complicated than just changing what /sbin/init is symlinked to, but right now it looks to me like that should be enough. zw signature.asc Description: OpenPGP digital signature
Bug#746278: marked as done (owncloud-client: FTBFS: tests fail when ran in parallel)
Your message dated Thu, 08 May 2014 17:48:57 + with message-id e1wisrf-0007p8...@franck.debian.org and subject line Bug#746278: fixed in owncloud-client 1.6.0~beta2+dfsg-2 has caused the Debian Bug report #746278, regarding owncloud-client: FTBFS: tests fail when ran in parallel 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.) -- 746278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: owncloud-client Version: 1.5.3+dfsg-1 Severity: serious Justification: FTBFS Dear Maintainer, Your package FTBFS when built in parallel (triggered here with 4 processes). Extracts from the build log: | touch: cannot touch '/tmp/check/c_mkdirs/with/check/foobar.txt': No such file or directory | 0x100 != 0 | /tmp/buildd/owncloud-client-1.5.3+dfsg/csync/tests/std_tests/check_std_c_dir.c:43: error: Failure! | [ FAILED ] check_c_isdir_on_file_setup | [==] 7 test(s) run. | [ PASSED ] 6 test(s). | [ FAILED ] 1 test(s), listed below: | [ FAILED ] check_c_isdir_on_file_setup | The following tests FAILED: | 2 - check_std_c_dir (Failed) |11 - check_csync_log (Failed) |13 - check_csync_statedb_load (Failed) |18 - check_csync_statedb_query (Failed) The full build log can be found here: http://95.85.27.130/builds/owncloud-client_1.5.3+dfsg-1_amd64.build -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: owncloud-client Source-Version: 1.6.0~beta2+dfsg-2 We believe that the bug you reported is fixed in the latest version of owncloud-client, 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 746...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Knauß b...@sandroknauss.de (supplier of updated owncloud-client 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, 08 May 2014 02:07:35 +0200 Source: owncloud-client Binary: owncloud-client owncloud-client-doc libowncloudsync0 libowncloudsync-dev owncloud-client-l10n owncloud-client-cmd Architecture: source amd64 all Version: 1.6.0~beta2+dfsg-2 Distribution: experimental Urgency: medium Maintainer: ownCloud for Debian maintainers pkg-owncloud-maintain...@lists.alioth.debian.org Changed-By: Sandro Knauß b...@sandroknauss.de Description: libowncloudsync-dev - development files for owncloudsync libowncloudsync0 - ownCloudSync folder synchronization - libraries owncloud-client - folder synchronization with an ownCloud server - GUI owncloud-client-cmd - folder synchronization with an ownCloud server - cmd client owncloud-client-doc - ownCloudSync folder synchronization - documentation owncloud-client-l10n - ownCloudSync folder synchronization - localization Closes: 746278 Changes: owncloud-client (1.6.0~beta2+dfsg-2) experimental; urgency=medium . * Run the tests with --max-parallel=1 to fix FTBFS. (Closes: #746278) Thanks Dmitry Shachnev * Added patch to make doc parts installable. Checksums-Sha1: 7a779061a42ff42ebf9aac7885099fdf15f3d42a 2806 owncloud-client_1.6.0~beta2+dfsg-2.dsc bd29566a60bee0a0b954b9620bc18f9e1eb86789 15868 owncloud-client_1.6.0~beta2+dfsg-2.debian.tar.xz 305caa0cdf432667228d66a9ce0d335e71e4988d 371290 owncloud-client_1.6.0~beta2+dfsg-2_amd64.deb d0c4df9b2c0ed7d4b318116e2ae2aad8284c56d8 2455150 owncloud-client-doc_1.6.0~beta2+dfsg-2_all.deb 5caa73264d137908662bb1ad439c218688e54aa0 377248 libowncloudsync0_1.6.0~beta2+dfsg-2_amd64.deb c3f5fca903a8e325f30653b1065cbabd2fc51a7e 34110 libowncloudsync-dev_1.6.0~beta2+dfsg-2_amd64.deb feb9a8b2cfcae9504e2d8fcdb87137e4a7bf6033 218018 owncloud-client-l10n_1.6.0~beta2+dfsg-2_all.deb 9df0f81b77d7572d40d57e55541745616dacb07c 31762 owncloud-client-cmd_1.6.0~beta2+dfsg-2_amd64.deb Checksums-Sha256: 1d196b45a4d0e4aa3ddb4e12320e2687abea4a358fa764b6de491c0866edf4c9 2806 owncloud-client_1.6.0~beta2+dfsg-2.dsc d4f87e37f32efd00d321e1a3618e6e0ab0af2c866a84c6fca513f92100cf4035 15868 owncloud-client_1.6.0~beta2+dfsg-2.debian.tar.xz fbf2a775626d1fbc8f7a446c780a4a7328718842412570cc0dd903146cf137fe 371290
Bug#747441: billiard: FTBFS on kfreebsd
package: billiard version: 3.3.0.17-1 severity: serious Hi, The latest upload of billiard fails on kfreebsd-*, but built successfully before: https://buildd.debian.org/status/package.php?p=billiard Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747442: aptitude: progs run by aptitude (apt-listbugs, how-can-I-help block apt when they crash
Package: aptitude Version: 0.6.10 Severity: grave Justification: renders package unusable Dear Maintainer, the specific situation: - [ already filed as #747406 against ruby] -a ruby corruption is crashing both apt-listbugs AND how-can-I-help - thus aptitude returns a failure and does NOT install the desired packages - the apt system is now completely broken: these packages can not be removed and no others can be installed. - apt-get is also affected and no longer works. the general case --- important - any program run by aptitude (such as apt-listbugs or how-can-I-help) that crashes will break the apt system. - this is a critical bug: any type of failure in sub-programs should have NO effect on aptitude. The code should be changed so that any problem in sub-programs run by aptitude will have NO effect on aptitude (or apt-get). Otherwise the apt system is at risk from any such program The bug I have filed above is related to a collection of recent (the week up to today 2014-05-08) bugs in ruby. See that bug #747406 for more detail. HOWEVER, the problem is the general case: corruptions such as this ruby problem should have NO effect on aptitude. -- Package-specific info: Terminal: rxvt-unicode-256color $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.10 compiled at Feb 20 2014 18:22:07 Compiler: g++ 4.8.2 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.2.11 Ept support enabled. Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20140118 cwidget version: 0.5.17 Apt version: 4.12.0 aptitude linkage: linux-gate.so.1 (0xb778f000) libapt-pkg.so.4.12 = /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 (0xb7227000) libncursesw.so.5 = /lib/i386-linux-gnu/libncursesw.so.5 (0xb71ef000) libtinfo.so.5 = /lib/i386-linux-gnu/libtinfo.so.5 (0xb71cc000) libsigc-2.0.so.0 = /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 (0xb71c6000) libcwidget.so.3 = /usr/lib/i386-linux-gnu/libcwidget.so.3 (0xb70c2000) libept.so.1.aptpkg4.12 = /usr/lib/i386-linux-gnu/libept.so.1.aptpkg4.12 (0xb7069000) libxapian.so.22 = /usr/lib/sse2/libxapian.so.22 (0xb6e6f000) libz.so.1 = /lib/i386-linux-gnu/libz.so.1 (0xb6e55000) libsqlite3.so.0 = /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb6d96000) libboost_iostreams.so.1.54.0 = /usr/lib/i386-linux-gnu/libboost_iostreams.so.1.54.0 (0xb6d7d000) libpthread.so.0 = /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb6d61000) libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb6c75000) libm.so.6 = /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb6c2e000) libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb6c12000) libc.so.6 = /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb6a67000) libutil.so.1 = /lib/i386-linux-gnu/i686/cmov/libutil.so.1 (0xb6a63000) libdl.so.2 = /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb6a5e000) libbz2.so.1.0 = /lib/i386-linux-gnu/libbz2.so.1.0 (0xb6a4b000) liblzma.so.5 = /lib/i386-linux-gnu/liblzma.so.5 (0xb6a24000) libuuid.so.1 = /lib/i386-linux-gnu/libuuid.so.1 (0xb6a1e000) librt.so.1 = /lib/i386-linux-gnu/i686/cmov/librt.so.1 (0xb6a15000) /lib/ld-linux.so.2 (0xb779) -- System Information: Debian Release: jessie/sid Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) 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#725079: marked as done (ns2: FTBFS with upcoming changes in Tcl/Tk)
Your message dated Fri, 9 May 2014 02:09:29 +0800 with message-id CAMr=8w6UEb7OAR1o0=etl8z184zj-c6nr24ai8_znfu_buw...@mail.gmail.com and subject line has caused the Debian Bug report #725079, regarding ns2: FTBFS with upcoming changes in Tcl/Tk 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.) -- 725079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ns2 Version: 2.35+dfsg-1 Severity: normal Tags: patch Dear Maintainer, We plan the following changes to Tcl/Tk in Debian which affect your ns2 package: 1. Adding multiarch capabilities (in particular, moving libraries into /usr/lib/triplet). 2. Upgrading default Tcl/Tk version to 8.6. The new packages are already in experimental, so you can play with them. Due to the first change ns2 configure script can't find Tcl/Tk anymore, and since it's custom (doesn't use tclConfig.sh script with all the paths recorded during Tcl build) I can't suggest anything except patching. Moreover, I doubt these patches can be sent upstream (as they use DEB_HOST_MULTIARCH variable). The second change revealed two problems. Firstly, deprecated (and hidden in 8.6) Tcl_Interp result field is used in the code. Secondly, in 8.6 the return type of Tcl_GetHashKey has been changed from char* to void* which causes error when compiling. Here comes another patch with a quick hack suitable for old projects (definition of USE_INTERP_RESULT) and with converting the return value to (void*). The latter is legitimate because the keys in Tcl_GetHashKey calls are always null-terminated strings. I've attached the patch which helps ns2 to build with Tcl/Tk from experimental. -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru ns2-2.35+dfsg/debian/changelog ns2-2.35+dfsg/debian/changelog --- ns2-2.35+dfsg/debian/changelog 2012-06-14 23:17:11.0 +0400 +++ ns2-2.35+dfsg/debian/changelog 2013-10-01 11:22:28.0 +0400 @@ -1,3 +1,11 @@ +ns2 (2.35+dfsg-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Fixed FTBFS after adding multiarch capabilities to Tcl/Tk. + * Defined USE_INTERP_RESULT to quickfix FTBFS after upgrade Tcl/Tk to 8.6. + + -- Sergei Golovan sgolo...@debian.org Tue, 01 Oct 2013 11:22:18 +0400 + ns2 (2.35+dfsg-1) unstable; urgency=low * New upstream stable release. diff -Nru ns2-2.35+dfsg/debian/patches/0005-fix-for-multiarch-tcltk.patch ns2-2.35+dfsg/debian/patches/0005-fix-for-multiarch-tcltk.patch --- ns2-2.35+dfsg/debian/patches/0005-fix-for-multiarch-tcltk.patch 1970-01-01 03:00:00.0 +0300 +++ ns2-2.35+dfsg/debian/patches/0005-fix-for-multiarch-tcltk.patch 2013-10-01 11:02:30.0 +0400 @@ -0,0 +1,44 @@ +--- a/conf/configure.in.tcl b/conf/configure.in.tcl +@@ -199,6 +199,7 @@ + $x_libs \ + /usr/lib64 \ + /usr/lib \ ++ /usr/lib/$DEB_HOST_MULTIARCH \ + + + dnl Decide which set of .tcl library files to use +--- a/conf/configure.in.tk b/conf/configure.in.tk +@@ -163,7 +163,9 @@ + $x_libs/tk \ + $x_libs \ + /usr/lib64 \ +-/usr/lib ++/usr/lib \ ++ /usr/lib/$DEB_HOST_MULTIARCH \ ++ + + NS_BEGIN_PACKAGE(tk) + NS_CHECK_HEADER_PATH(tk.h,$TK_H_PLACES,$d,$TK_H_PLACES_D,V_INCLUDE_TK,tk) +--- a/configure b/configure +@@ -5641,6 +5641,7 @@ + $x_libs \ + /usr/lib64 \ + /usr/lib \ ++ /usr/lib/$DEB_HOST_MULTIARCH \ + + + +@@ -6208,7 +6209,9 @@ + $x_libs/tk \ + $x_libs \ + /usr/lib64 \ +-/usr/lib ++/usr/lib \ ++ /usr/lib/$DEB_HOST_MULTIARCH \ ++ + + + NS_PACKAGE_tk_UNDERWAY=false diff -Nru ns2-2.35+dfsg/debian/patches/0006-hack-for-tcl8.6.patch ns2-2.35+dfsg/debian/patches/0006-hack-for-tcl8.6.patch --- ns2-2.35+dfsg/debian/patches/0006-hack-for-tcl8.6.patch 1970-01-01 03:00:00.0 +0300 +++ ns2-2.35+dfsg/debian/patches/0006-hack-for-tcl8.6.patch 2013-10-01 11:58:50.0 +0400 @@ -0,0 +1,44 @@ +--- a/webcache/pagepool.cc b/webcache/pagepool.cc +@@ -658,7 +658,7 @@ + for (he = Tcl_FirstHashEntry(namemap_, hs); + he != NULL; + he
Bug#747442: [Aptitude-devel] Bug#747442: aptitude: progs run by aptitude (apt-listbugs, how-can-I-help block apt when they crash
Hi Stephen, Stephen McGregor wrote: Package: aptitude Version: 0.6.10 Severity: grave Justification: renders package unusable Dear Maintainer, the specific situation: - [ already filed as #747406 against ruby] - a ruby corruption is crashing both apt-listbugs AND how-can-I-help - thus aptitude returns a failure and does NOT install the desired packages - the apt system is now completely broken: these packages can not be removed and no others can be installed. - apt-get is also affected and no longer works. The last sentence rather sounds like an apt library issue than an aptitude issue. Or does it not happen if you only use apt-get? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733934: marked as done (libmikmatch-ocaml-dev: an attempt to compile a program using the provided library fails)
Your message dated Thu, 08 May 2014 19:04:00 +
with message-id e1witbs-0007st...@franck.debian.org
and subject line Bug#733934: fixed in mikmatch 1.0.7-1
has caused the Debian Bug report #733934,
regarding libmikmatch-ocaml-dev: an attempt to compile a program using the
provided library fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
733934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libmikmatch-ocaml-dev
Version: 1.0.6-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
I was using mikmatch library on Debian stable (Wheezy) and with GODI.
I have found out that in Debian testing (Jessie), the provided library
somehow cannot be used. The attempt to compile a program that tries to
link it fails.
* What exactly did you do (or not do) that was effective (or
ineffective)?
- I took a fresh Debian testing system.
- I installed some packages I wanted to use:
apt-get install libbatteries-ocaml-dev libsexplib-camlp4-dev
libmikmatch-ocaml-dev libfindlib-ocaml-dev libxml-light-ocaml-dev
libbin-prot-camlp4-dev
- and did this:
touch main.ml
ocamlfind c -c -syntax camlp4o -package mikmatch_pcre main.ml
* What was the outcome of this action?
- ocamlfind terminated with exit status 1
- ocamlfind did not generate executable binary
- ocamlfind printed the following:
Camlp4: Uncaught exception: Delete.Rule_not_found ((LIDENT ((_)),
patt: [ \as\ LEFTA\n [ SELF; \as\; a_LIDENT ]\n| \|\ LEFTA\n [ SELF;
\|\; SELF ]\n| \,\ LEFTA\n [ SELF; \,\; LIST1 NEXT SEP \,\ ]\n| \::\
RIGHTA\n [ SELF; \::\; SELF ]\n| \apply\ RIGHTA\n [ \lazy\; SELF\n |
ANTIQUOT ((\\ | \pat\ | \anti\), _)\n | patt_constr; SELF\n |
patt_constr ]\n| \simple\ LEFTA\n [ ANTIQUOT ((\\ | \pat\ | \anti\),
_)\n | ANTIQUOT (\tup\, _)\n | ANTIQUOT (\`bool\, _)\n | QUOTATION _\n
| \-\; a_INT\n | \-\; a_INT32\n | \-\; a_INT64\n | \-\;
a_NATIVEINT\n | \-\; a_FLOAT\n | \false\\n | \true\\n | \[\;
\]\\n | \[\; sem_patt_for_list; \::\; SELF; \]\\n | \[\;
sem_patt_for_list; \]\\n | \[|\; \|]\\n | \[|\; sem_patt; \|]\\n |
\{\; label_patt_list; \}\\n | \(\; \)\\n | \(\; \module\;
a_UIDENT; \)\\n | \(\; \module\; a_UIDENT; \:\; package_type; \)\\n
| \(\; SELF; \:\; ctyp
; \)\\n | \(\; SELF; \)\\n | \_\\n | \`\; a_ident\n | \#\;
type_longident\n | ident\n | a_INT\n | a_INT32\n | a_INT64\n |
a_NATIVEINT\n | a_FLOAT\n | a_STRING\n | a_CHAR; \..\; a_CHAR\n | a_CHAR
] ]))
Error while running external preprocessor Command line: camlp4 '-I'
'/usr/lib/ocaml/camlp4' '-I' '/usr/lib/ocaml/pcre' '-I' '/usr/lib/ocaml' '-I'
'/usr/lib/ocaml/mikmatch_pcre' '-parser' 'o' '-parser' 'op' '-printer' 'p'
'pcre.cma' 'unix.cma' 'pa_mikmatch_pcre.cma' 'main.ml' /tmp/ocamlppa8c5b2
* What outcome did you expect instead?
- ocamlfind should terminate with exit status 0
- ocamlfind should generate executable binary
(which in this case should do nothing)
*** End of the template - remove these lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
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 libmikmatch-ocaml-dev depends on:
ii camlp4 [camlp4-4.01.0] 4.01.0-3
ii libmikmatch-ocaml [libmikmatch-ocaml-lrjk2] 1.0.6-3
ii libpcre-ocaml-dev [libpcre-ocaml-dev-36gi0] 7.0.2-4
ii ocaml-nox [ocaml-nox-4.01.0] 4.01.0-3
Versions of packages libmikmatch-ocaml-dev recommends:
ii ocaml-findlib 1.4-2
libmikmatch-ocaml-dev suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: mikmatch
Source-Version: 1.0.7-1
We believe that the bug you reported is fixed in the latest version of
mikmatch, 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.
Mehdi Dogguy me...@debian.org (supplier of
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 747428 upstream Bug #747428 [xbmc] [xbmc] passwords are stored in plain xml file Added tag(s) upstream. forwarded 747428 http://trac.xbmc.org/ticket/15198 Bug #747428 [xbmc] [xbmc] passwords are stored in plain xml file Set Bug forwarded-to-address to 'http://trac.xbmc.org/ticket/15198'. thanks Stopping processing here. Please contact me if you need assistance. -- 747428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747428 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#747453: Arbitrary key size limitations causing hard-to-diagnose problems when establishing a connection
Source: openssl Severity: critical Tags: security patch OpenSSL contains a set of arbitrary limitations on the size of accepted key parameters that make unrelated software fail to establish secure connections. The problem was found while debugging a XMPP s2s connection issue where two servers with long certificate keys (8192 Bit RSA) failed to establish a secure connection because OpenSSL rejected the handshake. The attached two patches fix the following issues: 1. Remove the restriction on DSA/DHE parameters to allow for arbitrary size 2. Increase the maximum allowed size for transmitted (client/server) keys from 516 byte (e.g. 4096 bit RSA) to 8200 byte (e.g. 65536 bit RSA) The first issue was found with a server using GnuTLS that used DH parameters with 13337 bits for negotiating the session key. While a website test succeeded in determining the cipher configuration it failed to negotiate a session key and did not provide any reasonable error message back to the user. As the issue depended on the ciphers offered by the client a real client like a webbrowser would not be able to gracefully fall back to some other algorithm. Thus the only workaround would be to use no encryption which would be the worst of all alternatives. The second issue was found while debugging issues with two ejabberd instances that both used certificates with 8192 bit RSA. While both servers could correctly determine the opposite's server's connection parameters (using provided SRV records) and properly established a cleartext connection they unexpectedly and without proper diagnosis terminated the SSL connection after negotiating to upgrade to STARTTLS. After both parties sent their certificates the connection was suddently terminated without even providing a SSL fatal error alert - thus no useful information could be provided by the application layer. Only after increasing the maximum size for key parameters were both servers able to connect to each other. This once again demonstrates that you MUST NOT introduce statically compiled-in magic numbers to place arbitrary limits on the size of used parameters. Furthermore it should be noted that the parameters used are neither very large, nor do they require excessive processing power (about 1-2 seconds for one handshake on average). This might not be an option for everybody but is well within parameters that are to be expected in casually-paranoid setups. Please apply both patches ASAP and forward them to be included upstream. Kind regards, Benny Baumann -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (750, 'experimental'), (700, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf informationn Description: Increase the maximum size allowed for client/server certificate packages on the wire Author: Benny Baumann be...@geshi.org --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: Origin: vendor|upstream|other, url of original patch Bug: url in upstream bugtracker Bug-Debian: http://bugs.debian.org/bugnumber Bug-Ubuntu: https://launchpad.net/bugs/bugnumber Forwarded: no|not-needed|url proving that it has been forwarded Reviewed-By: name and email of someone who approved the patch Last-Update: -MM-DD --- openssl-1.0.1e.orig/ssl/s3_srvr.c +++ openssl-1.0.1e/ssl/s3_srvr.c @@ -2926,7 +2926,7 @@ int ssl3_get_cert_verify(SSL *s) SSL3_ST_SR_CERT_VRFY_A, SSL3_ST_SR_CERT_VRFY_B, -1, - 516, /* Enough for 4096 bit RSA key with TLS v1.2 */ + 8200, /* Enough for 65536 bit RSA key with TLS v1.2 */ ok); if (!ok) return((int)n); Description: Remove DSA/DH keysize restrictions Author: Benny Baumann be...@geshi.org --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: Origin: vendor|upstream|other, url of original patch Bug: url in upstream bugtracker Bug-Debian: http://bugs.debian.org/bugnumber Bug-Ubuntu: https://launchpad.net/bugs/bugnumber Forwarded: no|not-needed|url proving that it has been forwarded Reviewed-By: name and email of someone who approved the patch Last-Update: -MM-DD --- openssl-1.0.1e.orig/crypto/dsa/dsa.h +++ openssl-1.0.1e/crypto/dsa/dsa.h @@ -84,10 +84,6 @@ #endif #endif -#ifndef OPENSSL_DSA_MAX_MODULUS_BITS -# define OPENSSL_DSA_MAX_MODULUS_BITS 1 -#endif - #define DSA_FLAG_CACHE_MONT_P 0x01 #define DSA_FLAG_NO_EXP_CONSTTIME 0x02 /* new with 0.9.7h; the built-in DSA * implementation now uses constant time
Bug#747402: marked as done (missing license in debian/copyright)
Your message dated Thu, 08 May 2014 22:04:11 + with message-id e1wiwqf-000525...@franck.debian.org and subject line Bug#747402: fixed in libguestfs 1:1.26.2-1 has caused the Debian Bug report #747402, 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.) -- 747402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libguestfs Version: 1:1.26.1-3 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: gnulib/* to debian/copyright. Thanks! Thorsten ---End Message--- ---BeginMessage--- Source: libguestfs Source-Version: 1:1.26.2-1 We believe that the bug you reported is fixed in the latest version of libguestfs, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated libguestfs 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, 08 May 2014 18:01:38 +0200 Source: libguestfs Binary: guestfsd libguestfs-dev libguestfs0 libguestfs-gfs2 libguestfs-hfsplus libguestfs-jfs libguestfs-nilfs libguestfs-reiserfs libguestfs-rescue libguestfs-rsync libguestfs-xfs libguestfs-zfs libguestfs-tools libguestfs0-dbg python-guestfs python3-guestfs libguestfs-perl libguestfs-ocaml libguestfs-ocaml-dev erlang-guestfs libguestfs-java ruby-guestfs libguestfs-gobject-1.0-0 libguestfs-gobject-dev gir1.2-guestfs-1.0 lua-guestfs golang-guestfs-dev Architecture: source amd64 all Version: 1:1.26.2-1 Distribution: unstable Urgency: low Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org Description: erlang-guestfs - guest disk image management system - Erlang bindings gir1.2-guestfs-1.0 - guest disk image management system - GObject introspection files golang-guestfs-dev - guest disk image management system - Golang bindings guestfsd - Daemon to access to guest virtual machine through virtio serial libguestfs-dev - guest disk image management system - development headers libguestfs-gfs2 - guest disk image management system - GFS2 support libguestfs-gobject-1.0-0 - guest disk image management system - GObject bindings libguestfs-gobject-dev - guest disk image management system - GObject development headers libguestfs-hfsplus - guest disk image management system - HFS+ support libguestfs-java - guest disk image management system - Java bindings libguestfs-jfs - guest disk image management system - JFS support libguestfs-nilfs - guest disk image management system - NILFS v2 support libguestfs-ocaml - guest disk image management system - OCaml bindings libguestfs-ocaml-dev - guest disk image management system - OCaml development files libguestfs-perl - guest disk image management system - Perl bindings libguestfs-reiserfs - guest disk image management system - ReiserFS support libguestfs-rescue - guest disk image management system - virt-rescue enhancements libguestfs-rsync - guest disk image management system - rsync support libguestfs-tools - guest disk image management system - tools libguestfs-xfs - guest disk image management system - XFS support libguestfs-zfs - guest disk image management system - ZFS support libguestfs0 - guest disk image management system - shared library libguestfs0-dbg - guest disk image management system - debug symbols lua-guestfs - guest disk image management system - Lua bindings python-guestfs - guest disk image management system - Python bindings python3-guestfs - guest disk image management system - Python 3 bindings ruby-guestfs - guest disk image management system - Ruby bindings Closes: 747402 Changes: libguestfs (1:1.26.2-1) unstable; urgency=low . * New upstream version * Mention Gnulib and its license in copyright file (Closes: #747402) * Dropped patches that have been integrated upstream Checksums-Sha1: 0f8a1c98cc77fef552531b3377a69d41d4665654 5185 libguestfs_1.26.2-1.dsc
Bug#747457: acetoneiso: uninstallable on kfreebsd
package: acetoneiso version: 2.4-1 severity: serious Hi, It seems acetoneiso depends on fuse and fuse-iso. Both packages are not available on kfreebsd. Either the dependency needs to be removed on these architectures, or acetoneiso should switch back to linux-any. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747453: [Pkg-openssl-devel] Bug#747453: Arbitrary key size limitations causing hard-to-diagnose problems when establishing a connection
severity 747453 normal thanks I don't see how the severity of this is critical. On Thu, May 08, 2014 at 11:23:04PM +0200, Benny Baumann wrote: Source: openssl Severity: critical Tags: security patch OpenSSL contains a set of arbitrary limitations on the size of accepted key parameters that make unrelated software fail to establish secure connections. The problem was found while debugging a XMPP s2s connection issue where two servers with long certificate keys (8192 Bit RSA) failed to establish a secure connection because OpenSSL rejected the handshake. The attached two patches fix the following issues: 1. Remove the restriction on DSA/DHE parameters to allow for arbitrary size 2. Increase the maximum allowed size for transmitted (client/server) keys from 516 byte (e.g. 4096 bit RSA) to 8200 byte (e.g. 65536 bit RSA) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 747166 in 3.2.41-2
Processing commands for cont...@bugs.debian.org: # first common ancestor for stable and unstable # kernels back to 2.6.31 are also affected, but that was linux-2.6, not linux found 747166 3.2.41-2 Bug #747166 [linux] CVE-2014-0196: pty layer race condition memory corruption There is no source info for the package 'linux' at version '3.2.41-2' with architecture '' Unable to make a source version for version '3.2.41-2' Marked as found in versions 3.2.41-2. thanks Stopping processing here. Please contact me if you need assistance. -- 747166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747166 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#747459: new mercurial makes tortoisehg uninstallable
package: tortoisehg version: 2.11-1 severity: serious Hi, The new version of mercurial (3.0-1) makes tortoisehg uninstallable, as it depends on mercurial ( 2.10~) Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731399: marked as done (jocaml: needs update for ocaml 4.01.0)
Your message dated Thu, 08 May 2014 22:48:31 + with message-id e1wix79-0001x4...@franck.debian.org and subject line Bug#731399: fixed in jocaml 4.01.0-1 has caused the Debian Bug report #731399, regarding jocaml: needs update for ocaml 4.01.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.) -- 731399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jocaml Version: 3.12.1-1 Severity: serious Tags: jessie sid Control: block 718767 with -1 Hi, jocaml needs to be updated to ocaml 4.01.0. Cheers, -- Stéphane ---End Message--- ---BeginMessage--- Source: jocaml Source-Version: 4.01.0-1 We believe that the bug you reported is fixed in the latest version of jocaml, 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 731...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mehdi Dogguy me...@debian.org (supplier of updated jocaml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 May 2014 00:03:20 +0200 Source: jocaml Binary: jocaml jocaml-base Architecture: source amd64 Version: 4.01.0-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers debian-ocaml-ma...@lists.debian.org Changed-By: Mehdi Dogguy me...@debian.org Description: jocaml - OCaml extended for concurrent and distributed programming jocaml-base - Runtime system for JOCaml bytecode executables Closes: 731399 Changes: jocaml (4.01.0-1) unstable; urgency=medium . * New upstream release (Closes: #731399). - Remove 0002-Add-option-v-to-expunge-to-select-modules-to-filter-.patch (applied upstream). - Refresh remaining patch which removes Otyp_proc in order to have an outcometree.mli compatible with OCaml's. * Keep only JoCaml specific patches, and import OCaml patches from ocaml-source package. This lets jocaml package benefit from work done on the ocaml package, automatically. * Update jocaml.install.in, since some files moved around and are now under compiler-libs directory. * Make jocaml depend on ocaml-compiler-libs. Checksums-Sha1: bc313010495332bc829713d8f53c0170eb0ed17b 2131 jocaml_4.01.0-1.dsc 6249ff743187ddc0dba3290c17207aa7d72cccb8 2592333 jocaml_4.01.0.orig.tar.gz 0c24a72f505448bdd096b3e8c423c58456053121 25422 jocaml_4.01.0-1.diff.gz bd6d9bd3465a6eacf042329bab2fa5ddd37edc9f 2530084 jocaml_4.01.0-1_amd64.deb ab6cc25cc0bdd15815eecdb496c5e31cf40be905 272264 jocaml-base_4.01.0-1_amd64.deb Checksums-Sha256: f7b4edf23a03e8088bd78e85b5c9d8c42b1d683267de208049b85f34f2ec 2131 jocaml_4.01.0-1.dsc 8d83c8eb99329d6acb8bc891cbf0a8f5b2a4b788df776464fd94a61d0ea813e2 2592333 jocaml_4.01.0.orig.tar.gz 3275907b43f37b84b27b4c436fb950a5213f072af639f7818d4fe0682cb49db1 25422 jocaml_4.01.0-1.diff.gz 6b2546576f54315190caf69d7976e220c1743ff0a32cf872e93944a510ec732f 2530084 jocaml_4.01.0-1_amd64.deb ae0a5a2e71e0df746369bbd885c15d41afa7c05ba8f91b7514f33e9e80d5dba1 272264 jocaml-base_4.01.0-1_amd64.deb Files: 8267daf15d098e1b7082f0b07e1f 2530084 ocaml optional jocaml_4.01.0-1_amd64.deb e581d8e5c11b996f4c5fcff6384a4895 272264 ocaml optional jocaml-base_4.01.0-1_amd64.deb 4f35ba2ecc54810c09319c8996af9536 2131 ocaml optional jocaml_4.01.0-1.dsc ddb36ea5e1a820fc8fa2613009677c80 2592333 ocaml optional jocaml_4.01.0.orig.tar.gz 45b30788a9e2e680aae903c56dad58ac 25422 ocaml optional jocaml_4.01.0-1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJTbAGtAAoJEDO+GgqMLtj/d3oP/AzXrv8J+77nP1ZlVGNaBARD NjlUOZELUcBObeTKsrOuzucSjyAEHIaYkmc7dIRTYwp3tAf5T5DHgLFduw5krlAS YOhfWKvCY5xU7NALnYtATpk9EPTE6dfdAuk8sZF3fNCn4NiDGCU23DeveNxflwZE xbPliKdifnqgEwaBClVjqWAiI8VThSHOQfH9XjRd2cMtFtQogOUcCV6SSlQRhhvG AxwXFSZu7wzyZoxBPQuZebfz2sCg0DaDplq+4khTN3vGSiWPJfq4udO1d9lCam0w 9YBeiZu+55XyBL0ZMCNoKEV38pCuXCA+k3tUwE5rGLbwQo+PRGWbxRlLpDWYVGfP xn+dfl9OkBUJKDjeXgbuPirkXyr3ABF9t6aReUnoPWCHyQ4i0qgeNeA5UoR84RIy CurMMDDCMEl7YzNWoJWg6zP6i0Jx4FyVJvVyv/IdeTxlyokNblirNogFDmxDRdeM JVe1A5FDOw2zr0rrgjc1h06uT1hrdZuzURVf+DXoAdRUTmUuhkwukyojy76Bhnwz
Bug#747461: qpidd: postinst fails while running adduser
Package: qpidd Version: 0.16-7.1 Severity: grave Justification: renders package unusable postinst runs: adduser --system --home /var/run/qpid --group --no-create-home --disabled- password qpidd ... which errors out because /var/run/qpid doesn't exist and the postinst aborts. Repeating the postinst succeeds, because now qpidd entry exists in /etc/passwd. - Gus -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qpidd depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii libboost-program-options1.54.0 1.54.0-5 ii libc6 2.18-4 ii libgcc1 1:4.8.2-16 ii libibverbs1 1.1.7-1 ii libqpidbroker2 0.16-7.1 ii libqpidcommon2 0.16-7.1 ii librdmawrap20.16-7.1 ii libsasl2-modules2.1.26.dfsg1-9 ii libsslcommon2 0.16-7.1 ii libstdc++6 4.8.2-16 ii libxerces-c3.1 3.1.1-5 ii libxqilla6 2.3.0-1 ii sasl2-bin 2.1.26.dfsg1-9 qpidd recommends no packages. qpidd suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747453: Arbitrary key size limitations causing hard-to-diagnose problems when establishing a connection
Kurt Roeckx wrote: I don't see how the severity of this is critical. The severity level critical is defined as: makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. https://www.debian.org/Bugs/Developer This bug makes unrelated software on the system break (e.g. ejabberd, no communication was possible until _both_ sides had the supplied patch applied), and also could introduce security holes, as clients might fall back to unencrypted communication. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
