Bug#740565: redeclipse-data: should be in main
On Sun, Jul 27, 2014 at 6:30 AM, Markus Koschany a...@gambaru.de wrote: On 27.07.2014 10:23, Martin Erik Werner wrote: [...] As far as I see it, it is still uncertain whether redeclipse-data belonging in main is a correct assumption, a re-review of the content would be needed, from the previous discussion I think it is indeed *probable* that it would be found fit for main. I have reviewed redeclipse and redeclipse-data file-by-file. The patches are now attached to this bug report. The licenses are DFSG-free and there is not a single file that wouldn't abide by the rules. The only thing I noticed was a missing license paragraph about a few public domain images which I have added to debian/copyright. The paragraph about the Play* fonts could be removed because it appears you moved the font to a separate package, fonts-play. Otherwise the copyright file was accurate. Great, thanks for the patches! I'm sure you've realized by now that the fastest way to get stuff done in Debian is to do it yourself. ;) I don't think this is an RC bug, since keeping it in nonfree is actually the safer option (albeit a bad one should it be deemed unnecessary). No, this is, was and always will be RC. Fixing this issue during a regular upload was preferable but it seems there won't be another release in time before the freeze thus it was necessary to finally take action. No, it's not RC; see below. Imagine the gnome-shell maintainers decided to put their package into non-free because they felt it is safer. It would make all dependencies suddenly uninstallable. You simply can't make arbitrary decisions about the archive sections. Just because Red Eclipse is just a game makes the issue not smaller or less important. Yes, the gnome-shell maintainers can decide to put their packages into non-free if they so wish; doing so is not a Policy violation, even if it sounds ridiculous. And yes, it would make their dependencies uninstallable, which would indeed lead to RC bugs being filed against it and/or its dependencies (and would likely be followed by some heated flamewars on certain mailing lists). It's completely hypothetical, but the gnome-shell maintainers can move their package to non-free at any time, and only the CTTE can override them. There is no documented Policy about the term safer but the Policy is very precise about Debian's archive areas. [1] If your package is compliant with the DFSG it must be in main because this area comprises the Debian distribution. Otherwise other software, like my games-fps metapackage from the Debian Games Pure Blend, is not allowed to depend or recommend Red Eclipse. Since Red Eclipse is DFSG-free it is a Policy violation. Thus the severity must be serious. No, Policy §2.2 explicitly states that non DFSG compliant packages must go in non-free, but nothing about DFSG compliant packages being forced to be distributed in main. 2.2.1 only says that Every package in main must comply with the DFSG (Debian Free Software Guidelines), i.e. package in main - DFSG-compliant, _not_ the reverse. Policy doesn't forbid placing DFSG packages in contrib or non-free, as silly as it may sound, so this simply isn't a RC bug. Just to be clear, I don't object to placing DFSG-free packages in main; what I'm arguing against is inflating bug severity to accomplish your own personal release goals when the bug doesn't violate Policy. It may be important to you, but if it doesn't meet the definition of a RC bug, it's not a RC bug, and it's definitely not a release blocker. Now, just imagine if every maintainer and user decided to inflate the priority of their own pet bugs... Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740565: redeclipse-data: should be in main
On Sun, Jul 27, 2014 at 9:46 AM, Martin Erik Werner martinerikwer...@gmail.com wrote: On Sun, 2014-07-27 at 15:30 +0200, Markus Koschany wrote: On 27.07.2014 10:23, Martin Erik Werner wrote: [...] As far as I see it, it is still uncertain whether redeclipse-data belonging in main is a correct assumption, a re-review of the content would be needed, from the previous discussion I think it is indeed *probable* that it would be found fit for main. I have reviewed redeclipse and redeclipse-data file-by-file. The patches are now attached to this bug report. The licenses are DFSG-free and there is not a single file that wouldn't abide by the rules. The only thing I noticed was a missing license paragraph about a few public domain images which I have added to debian/copyright. The paragraph about the Play* fonts could be removed because it appears you moved the font to a separate package, fonts-play. Otherwise the copyright file was accurate. Thank you for the review, it is very much appreciated! Both font and P-D corrections looks correct (I previously think I let the P-D stuff fall through to the Files: * CC-BY-SA glob since they had been modified in Red Eclipse), but I think this makes more sense on second thought. I have pushed your changes to the git repos for redeclipse. Anyone up for sponsoring redeclipse and redeclipse-data for this change? Sure, put it on the team sponsor queue [1] and I'll take a look at it eventually (before the freeze, at worst) if nobody else does. Regards, Vincent [1] https://wiki.debian.org/Games/Sponsors/Queue -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 756081
Processing commands for cont...@bugs.debian.org: affects 756081 libanet0.1-dbg Bug #756081 [libanet0.1] libanet0.1: uninstallable on sid, needs update for gnat-4.9 Added indication that 756081 affects libanet0.1-dbg thanks Stopping processing here. Please contact me if you need assistance. -- 756081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756081 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: affects 756081
Processing commands for cont...@bugs.debian.org: affects 756081 libanet0.1-dev Bug #756081 [libanet0.1] libanet0.1: uninstallable on sid, needs update for gnat-4.9 Added indication that 756081 affects libanet0.1-dev thanks Stopping processing here. Please contact me if you need assistance. -- 756081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756081 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: affects 755016
Processing commands for cont...@bugs.debian.org: affects 755016 libapq-postgresql3.2.0-dev Bug #755016 [apq-postgresql] apq-postgresql: uninstallable on sid, needs update for gnat-4.9 Added indication that 755016 affects libapq-postgresql3.2.0-dev thanks Stopping processing here. Please contact me if you need assistance. -- 755016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755016 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: affects 755016
Processing commands for cont...@bugs.debian.org: affects 755016 libapq-postgresql3.2.0-dbg Bug #755016 [apq-postgresql] apq-postgresql: uninstallable on sid, needs update for gnat-4.9 Added indication that 755016 affects libapq-postgresql3.2.0-dbg thanks Stopping processing here. Please contact me if you need assistance. -- 755016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755016 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: affects 755014
Processing commands for cont...@bugs.debian.org: affects 755014 libapq3.2.0-dbg Bug #755014 [apq] apq: uninstallable on sid, needs update for gnat-4.9 Added indication that 755014 affects libapq3.2.0-dbg thanks Stopping processing here. Please contact me if you need assistance. -- 755014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755014 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: affects 755014
Processing commands for cont...@bugs.debian.org: affects 755014 libapq3.2.0-dev Bug #755014 [apq] apq: uninstallable on sid, needs update for gnat-4.9 Added indication that 755014 affects libapq3.2.0-dev thanks Stopping processing here. Please contact me if you need assistance. -- 755014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755014 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#756334: question
Do you have an alternative solution? Maybe this could be extracted directly to source package and updated with an script? --- Henri Salo signature.asc Description: Digital signature
Bug#752804: Perl 5.20 transition imminent
Hi, On 28/07/2014 22:37, Damyan Ivanov wrote: Control: severity -1 serious Perl 5.20 is planned to hit unstable around the 12th of August, at which point your package will become unbuildable and/or uninstallable. We plan to start doing NMUs to DELAYED/5 of all the packages which have a patch attached on or about 2nd of August, but a maintainer upload would be warmly appreciated. I will take care of the upload this WE (together with a new upstream version). The package is nearly ready. Regards, Vincent -- dam Debian Perl Group -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752348: marked as done (libhdate: hardcodes /usr/lib/perl5)
Your message dated Tue, 29 Jul 2014 06:48:56 +
with message-id e1xc1du-00062t...@franck.debian.org
and subject line Bug#752348: fixed in libhdate 1.6-2.1
has caused the Debian Bug report #752348,
regarding libhdate: hardcodes /usr/lib/perl5
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.)
--
752348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libhdate
Version: 1.6-2
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition
Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the vendorarch library path (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.
For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.
This package builds successfully with perl_5.20.0-1 from experimental,
but still installs the Perl files into /usr/lib/perl5 so they won't be
on the Perl search path anymore.
Please ask on the debian-perl list if you want help with this.
drwxr-xr-x root/root 0 2014-06-17 01:35 ./usr/lib/perl5/
drwxr-xr-x root/root 0 2014-06-17 01:35 ./usr/lib/perl5/auto/
drwxr-xr-x root/root 0 2014-06-17 01:35 ./usr/lib/perl5/auto/highlight/
-rw-r--r-- root/root 1043792 2014-06-17 01:35
./usr/lib/perl5/auto/highlight/highlight.so
-rw-r--r-- root/root 15627 2014-06-17 01:35 ./usr/lib/perl5/highlight.pm
--
Niko Tyni nt...@debian.org
---End Message---
---BeginMessage---
Source: libhdate
Source-Version: 1.6-2.1
We believe that the bug you reported is fixed in the latest version of
libhdate, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Damyan Ivanov d...@debian.org (supplier of updated libhdate package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 29 Jul 2014 06:38:35 +
Source: libhdate
Binary: libhdate-dev python-hdate libhdate-perl libhdate1
Architecture: source amd64
Version: 1.6-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hebrew Packaging Team
debian-hebrew-pack...@lists.alioth.debian.org
Changed-By: Damyan Ivanov d...@debian.org
Description:
libhdate-dev - Provides a library that help use hebrew dates (development
files)
libhdate-perl - Provides a library that help use hebrew dates (perl bindings)
libhdate1 - Provides a library that help use hebrew dates
python-hdate - Provides a library that help use hebrew dates (python bindings)
Closes: 752348
Changes:
libhdate (1.6-2.1) unstable; urgency=medium
.
[ Damyan Ivanov ]
* Non-maintainer upload with maintainer's permission
.
[ gregor herrmann ]
* Fix hardcodes /usr/lib/perl5
- use $Config{vendorarch} in debian/rules and debian/libhdate-perl.*
- make the latter two executable
(Closes: #752348)
Checksums-Sha1:
f8e8438052813212fa7b0a1dfdd049bc6c8b4b34 2239 libhdate_1.6-2.1.dsc
9f4fa4f8eefd4ee4e40bb24605c65a91558a0425 12528 libhdate_1.6-2.1.debian.tar.xz
92e953211bb9477e3b9df7c0d20828bacb446cc1 346470 libhdate-dev_1.6-2.1_amd64.deb
30b928cbc69df7c3353d70aa80950306cca57ac5 24734 python-hdate_1.6-2.1_amd64.deb
47cc24c1ddb86ab12e108093c295bfde6d553619 23992 libhdate-perl_1.6-2.1_amd64.deb
3dd96f641cd56d7174bfd770ee2ed444f132147e 61656 libhdate1_1.6-2.1_amd64.deb
Checksums-Sha256:
42a151c920bf11be999ebcc65159da610dcc4937d0a0c3c2c4bc116d787b034e 2239
libhdate_1.6-2.1.dsc
0a2ae01981899231adc78a90856e3c985e52cd2602afd64b63cb3c521cb20f2c 12528
libhdate_1.6-2.1.debian.tar.xz
17387336959d5c6710bebffaf7276e7c20aa07d08484e9af3ae1a07ee835b002 346470
libhdate-dev_1.6-2.1_amd64.deb
d997e92a96b5de21ed2f6c55f74e40ef52cb0a269e58db9e4e48bc0824346b1c 24734
python-hdate_1.6-2.1_amd64.deb
3ace009a343a8ca98963160c78b3bcd17fb63ec90e5ed153f4e9318781037225 23992
libhdate-perl_1.6-2.1_amd64.deb
21277f9a27040bcfb4bc063faf31a4f4f181e62b97733aa95d71730c1b538b9d 61656
Processed: Re: Bug#752804: Perl 5.20 transition imminent
Processing control commands: tags -1 pending Bug #752804 [src:owfs] owfs: hardcodes /usr/lib/perl5 Added tag(s) pending. -- 752804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752804 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#752804: Perl 5.20 transition imminent
Control: tags -1 pending -=| Vincent Danjean, 29.07.2014 08:49:34 +0200 |=- Hi, On 28/07/2014 22:37, Damyan Ivanov wrote: Control: severity -1 serious Perl 5.20 is planned to hit unstable around the 12th of August, at which point your package will become unbuildable and/or uninstallable. We plan to start doing NMUs to DELAYED/5 of all the packages which have a patch attached on or about 2nd of August, but a maintainer upload would be warmly appreciated. I will take care of the upload this WE (together with a new upstream version). The package is nearly ready. That's great! Marking as pending so that we skip it in the NMU campaign. -- dam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: NMU diff for libhdate 1.6-2.1
Processing control commands:
tags -1 pending
Bug #752348 {Done: Damyan Ivanov d...@debian.org} [libhdate] libhdate:
hardcodes /usr/lib/perl5
Added tag(s) pending.
--
752348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752348
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#752348: NMU diff for libhdate 1.6-2.1
Control: tags -1 pending
Attached is the NMU diff for the just uploaded libhdate 1.6-2.1,
produced by 'git diff'.
Note that debian/libhdate-perl.dirs and debian/libhdate-perl.install are
made executable, which may not be honoured by the 'patch' program when
applying the patch.
Cheers,
dam
diff --git a/debian/changelog b/debian/changelog
index 785cb63..dd174b6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+libhdate (1.6-2.1) unstable; urgency=medium
+
+ [ Damyan Ivanov ]
+ * Non-maintainer upload with maintainer's permission
+
+ [ gregor herrmann ]
+ * Fix hardcodes /usr/lib/perl5
+- use $Config{vendorarch} in debian/rules and debian/libhdate-perl.*
+- make the latter two executable
+(Closes: #752348)
+
+ -- Damyan Ivanov d...@debian.org Tue, 29 Jul 2014 06:38:35 +
+
libhdate (1.6-2) unstable; urgency=low
* Patch fix_3: fix an endless loop with hcal -3 (Closes: #692039).
diff --git a/debian/libhdate-perl.dirs b/debian/libhdate-perl.dirs
old mode 100644
new mode 100755
index 92105be..105d79d
--- a/debian/libhdate-perl.dirs
+++ b/debian/libhdate-perl.dirs
@@ -1 +1,3 @@
-usr/lib/perl5
+#!/usr/bin/perl -w
+use Config;
+print substr($Config{vendorarch}, 1) . \n;
diff --git a/debian/libhdate-perl.install b/debian/libhdate-perl.install
old mode 100644
new mode 100755
index c1a78d7..105d79d
--- a/debian/libhdate-perl.install
+++ b/debian/libhdate-perl.install
@@ -1 +1,3 @@
-usr/lib/perl5/*
+#!/usr/bin/perl -w
+use Config;
+print substr($Config{vendorarch}, 1) . \n;
diff --git a/debian/rules b/debian/rules
index 9900396..7593636 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,10 +1,12 @@
#!/usr/bin/make -f
+ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
+
%:
dh $* --with python2,autotools_dev
override_dh_auto_configure:
- dh_auto_configure -- --with-perl-sitelib-dir=/usr/lib/perl5
+ dh_auto_configure -- --with-perl-sitelib-dir=$(ARCHLIB)
override_dh_python2:
dh_python2 -s --no-guessing-versions
Bug#752711: marked as done (libpg-perl: hardcodes /usr/lib/perl5)
Your message dated Tue, 29 Jul 2014 07:18:56 +
with message-id e1xc1gw-0001zb...@franck.debian.org
and subject line Bug#752711: fixed in libpg-perl 1:2.1.1-5
has caused the Debian Bug report #752711,
regarding libpg-perl: hardcodes /usr/lib/perl5
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.)
--
752711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libpg-perl
Version: 1:2.1.1-4
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition
Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the vendorarch library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.
For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.
This package fails to build with perl_5.20.0-1 from experimental:
install -m 644 -D /«PKGBUILDDIR»/debian/libpg-perl/usr/lib/perl5/Pg.pm
/«PKGBUILDDIR»/debian/libpg-perl/usr/share/perl5/Pg.pm
install: cannot stat '/«PKGBUILDDIR»/debian/libpg-perl/usr/lib/perl5/Pg.pm':
No such file or directory
make: *** [binary-arch] Error 1
debian/rules:31: recipe for target 'binary-arch' failed
Please ask on the debian-perl list if you want help with this, and see
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
--
Niko Tyni nt...@debian.org
---End Message---
---BeginMessage---
Source: libpg-perl
Source-Version: 1:2.1.1-5
We believe that the bug you reported is fixed in the latest version of
libpg-perl, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt mp...@debian.org (supplier of updated libpg-perl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 29 Jul 2014 09:09:27 +0200
Source: libpg-perl
Binary: libpg-perl
Architecture: source amd64
Version: 1:2.1.1-5
Distribution: sid
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
pkg-postgresql-pub...@lists.alioth.debian.org
Changed-By: Martin Pitt mp...@debian.org
Description:
libpg-perl - Perl modules for PostgreSQL
Closes: 572670 752711
Changes:
libpg-perl (1:2.1.1-5) unstable; urgency=medium
.
* Import packaging into git-buildpackage, add Vcs-* tags.
* Set Maintainer to pkg-postgresql team. (Closes: #572670)
* Drop long-obsolete Conflicts/Replaces.
* Move to debhelper compat 9 and dh. This vastly simplifies debian/rules and
avoids hardcoded Perl paths. (Closes: #752711)
* Add missing ${misc:Depends}.
* Move to 3.0 (quilt) source format.
* Add autopkgtest.
* Add test_table_with_oids.patch: Create table with OIDs in test, as OIDs
are not created by default any more.
* Add test_fix_endcopy.patch: Fix $conn-endcopy test.
* Move to copyright format 1.0.
* Bump Standards-Version to 3.9.5.
Checksums-Sha1:
c585d0efab178145df7ba709a9bf36a2637952e6 1956 libpg-perl_2.1.1-5.dsc
8da70005c84fe5db3468e710720fa5ead9048a2d 3748 libpg-perl_2.1.1-5.debian.tar.xz
277fa7790b1584792e61e6c2bb4e7686e6902ca6 38960 libpg-perl_2.1.1-5_amd64.deb
Checksums-Sha256:
bc4e73cf39969d13e07b3caefdbd7e344e9c17a83b4ff8eaec3bc4f4dc45b071 1956
libpg-perl_2.1.1-5.dsc
fa3636ce42d845e627e7eb947f0298ada806c97c442ca144065437906d9cf814 3748
libpg-perl_2.1.1-5.debian.tar.xz
1c71a7d7fe9d8eb2d01e300ea5fda3302474df7ec79e27de9bde42f707185095 38960
libpg-perl_2.1.1-5_amd64.deb
Files:
104a370436ce931e80ca05710d1ea0ea 38960 perl optional
libpg-perl_2.1.1-5_amd64.deb
b4ef0420dd9cc5107cc5e7824842adda 1956 perl optional libpg-perl_2.1.1-5.dsc
f3a09bde55b33bbc8250c0aee6371292 3748 perl optional
libpg-perl_2.1.1-5.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJT10jmAAoJENFO8V2v4RNHVEsQAIq01Ru0wN9cPeV7NHRodi+6
udN8on4F5Ai/UAuQd1kALypGOBou2rUpuy6QppjveF+K0pqQTwvfs08+732d+qBD
Processed: severity of 756224 is wishlist
Processing commands for cont...@bugs.debian.org: # this bug is a feature request severity 756224 wishlist Bug #756224 [libnss-myhostname] libnss-myhostname: Causes apps that need FQDN to fail Severity set to 'wishlist' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 756224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756224 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#756224: libnss-myhostname: Causes apps that need FQDN to fail
Hi, Am Dienstag, den 29.07.2014, 00:22 -0400 schrieb Daniel Dickinson: Yeah but the guy claiming FQDN broken is the same Lennart who seems hell bent on destroying every *nix idiom. I wouldn't go by his opinion. and I won’t discuss technical issues on this level. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Processed: Re: [Pkg-haskell-maintainers] Bug#756334: Configure script downloads files from the Internet
Processing control commands: tag -1 + upstream confirmed Bug #756334 [hoogle] Configure script downloads files from the Internet Added tag(s) upstream and confirmed. -- 756334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756334 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#756334: [Pkg-haskell-maintainers] Bug#756334: Configure script downloads files from the Internet
Control: tag -1 + upstream confirmed Hi, Iustin Pop is working on this, and finding a solution together with upstream: https://github.com/ndmitchell/hoogle/issues/76 Greetings, Joachim Am Montag, den 28.07.2014, 23:02 +0200 schrieb Evgeny Kapun: Package: hoogle Version: 4.2.33-1+b1 Severity: critical Tags: security During configuration, hoogle postinst script attempts to download a file from the URL http://hackage.haskell.org/packages/hoogle.tar.gz and subsequently unpack it. Moreover, the integrity of this file is not verified. This leads to the following possible attacks: * An attacker controlling the user's network connection may indefinitely delay the configuration of hoogle package by supplying data at a very low rate, even if package files themselves are available from local source. * The same attacker may supply bogus data instead of the file. This may not only lead to hoogle behaving in an erroneous manner, but may also lead to a full system compromise. For example, the archive may contain a malicious executable file marked SUID root, and local unprivileged user (who also participates in the attack) may run this file after it is extracted. The archive may also contain symlinks and device nodes, which can also be used for attack. * The same attacker may supply a very large file, filling the system partition and achieving denial of service. He may also supply a small file which becomes very large after un-gzipping. My suggestion is that downloading files in a secure manner is hard, and maintainer scripts probably shouldn't be doing it. ___ Pkg-haskell-maintainers mailing list pkg-haskell-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#752974: xdotool: FTBFS - tests fail with EOFError: end of file reached
Is this failing test related to bug #740419 (Unreliable testsuite)? Should the bugs be merged? If the test suite is unreliable, perhaps running it during build should be optional, or at least not fatal when it fail? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756334: [Pkg-haskell-maintainers] Bug#756334: Configure script downloads files from the Internet
On Mon, Jul 28, 2014 at 11:02:53PM +0200, Evgeny Kapun wrote: My suggestion is that downloading files in a secure manner is hard, and maintainer scripts probably shouldn't be doing it. On Tue, Jul 29, 2014 at 09:27:34AM +0300, Henri Salo wrote: Do you have an alternative solution? Maybe this could be extracted directly to source package and updated with an script? Just to clarify both points above, if it's not clear from the discussion on the upstream bug: the current situation is not intended, it's just an accident resulting from the fact that upstream doesn't (yet) support an offline mode, and changes in the upstream behaviour resulted in our pre-unpacked files being ignored. Rest assured, this will get fixed, one way (better upstream support) or another (us patching upstream code so that it never downloads + pre-shipping). regards, iustin signature.asc Description: Digital signature
Bug#736787:
Hi, 2014-07-27 1:51 GMT+02:00 Balint Reczey bal...@balintreczey.hu: Control: tags -1 patch On 03/12/2014 09:54 PM, Mert Dirik wrote: Looks like it is fixed in upstream in commit 27420ad [1] by removing the offending files. New upstream version (1.5) should fix this bug. [1] https://github.com/mitchellh/vagrant/commit/27420ad2ee78caf1b1effc3eb27744ae2c288009 IMO the files still have to be removed from orig.tar.gz by repackaging it as 1.6.3+dfsg1 manually. I see 1.5.3 imported to packaging git, but it still has the files thus would not solve this RC bug. Antonio, do you plan releasing 1.6.3 with the problematic files removed from the source? The attached patch will remove the whole website dir from the source when using uscan --repack. I can push it to the packaging repository, but I did not want to do so before asking first. I have pushed the fix to the packaging repository and also created 1.5.3+dfsg1 with the website dir filtered out. Is there a package update in the plans? Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755315: [PKG-Openstack-devel] Bug#755315: [openstack-dev] [Trove] Should we stop using wsgi-intercept, now that it imports from mechanize? this is really bad!
On 07/28/2014 04:04 AM, Chris Dent wrote: On Mon, 28 Jul 2014, Thomas Goirand wrote: That's exactly the version which I've been looking at. The thing is, when I run the unit test with that version, it just bombs on me because mechanize isn't there. How would you feel about it being optionally available and for the tests for mechanize to only run for it if someone has aleady preinstalled mechanize? That is the tests will skip if import mechanize is an ImportError? While I'm not in love with mechanize, if it is a tool that _some_ people use, then I don't want wsgi-intercept to not be useful to them. Please let me know if you can release a new version of wsgi-intercept cleaned from any trace of mechanize, or if you think this can't be done. Let me know if the above idea can't work. Depending on your answer I'll either release a version as described, or go ahead and flush it. If you get back to me by tomorrow morning (UTC) I can probably get the new version out tomorrow too. Hi, Sorry, I couldn't reply earlier. Well, if at least mechanize really becomes optional, which means: no issue when running unit tests without it, and no issue when using it, then it may be ok from my point of view (eg: I wouldn't complain that much about it). However, from *your* perspective, I wouldn't advise that you keep using such a dangerous, badly maintained Python module. Saying that it's optional may look like you think mechanize is ok and you are vouching for it, when it really shouldn't be the case. Having clean, well maintained dependencies, is IMO very important for a given python module. It shows that you care no bad module gets in. Let me know whenever you have a new release, without mechanize as new dependency, or with it being optional. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752943: djangorestframework: FTBFS - Test label 'rest_framework.tests' does not refer to a test
Hi, Control: notfound -1 2.3.13-2 Control: close -1 Hi, On Wed, Jul 02, 2014 at 06:11:29AM +0900, Kouhei Maeda wrote: But this problem was unreproducible when I had created a new base.cow. (The other lintian errors occured.) I also cannot reproduce the problem in a clean, up-to-date chroot. Closing. My apologies for the late reply. Indeed this was an issue caused by my set up, even though there does seem to be a genuine problem here (but not an RC one; I'm leaving the bug closed for now and will let you judge). It's this bit of the code/configuration: http://sources.debian.net/src/djangorestframework/2.3.14-1/rest_framework/runtests/settings.py?hl=165,166#L166 As I had been building this from within jenkins, xmlrunner.extra.djangotestrunner.XMLTestRunner was used instead of the (default?) DiscoveryRunner. Apparently, however, the XMLTestRunner won't work for this test suite. Best, Michael pgpMp1yACN27l.pgp Description: PGP signature
Bug#756360: gdevilspie: maintainer address bounces
Source: gdevilspie Severity: serious Tags: sid X-Debbugs-Cc: Bart Martens ba...@debian.org [ CC'ed the last sponsor for the package in case he knows the maintainer. ] The maintainer address for gdevilspie bounces, see below. Ansgar On 07/28/2014 21:49, Mail Delivery System wrote: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: rac...@makeworld.com SMTP error from remote mail server after RCPT TO:rac...@makeworld.com: host inbound.makeworld.com.netsolmail.net [206.188.198.64]: 550 5.0.0 rac...@makeworld.com... User unknown -- This is a copy of the message, including all the headers. -- Return-path: dak-unp...@franck.debian.org Received: from franck.debian.org ([138.16.160.12]) from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=franck.debian.org,EMAIL=hostmas...@franck.debian.org (verified) by muffat.debian.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from dak-unp...@franck.debian.org) id 1XBqvl-00075v-Hg for rac...@makeworld.com; Mon, 28 Jul 2014 19:49:57 + Received: from dak-unpriv by franck.debian.org with local (Exim 4.80) (envelope-from dak-unp...@franck.debian.org) id 1XBqvk-ug-DR for rac...@makeworld.com; Mon, 28 Jul 2014 19:49:56 + To: rac...@makeworld.com From: Debian FTP Masters ftpmas...@ftp-master.debian.org Subject: Processing of gdevilspie_0.5-3.1_amd64.changes Date: Mon, 28 Jul 2014 19:49:56 + X-Debian: DAK X-DAK: DAK Precedence: bulk Auto-Submitted: auto-generated X-Debian-Package: gdevilspie Message-Id: e1xbqvk-ug...@franck.debian.org Sender: unprivileged ftp-master role account dak-unp...@franck.debian.org gdevilspie_0.5-3.1_amd64.changes uploaded successfully to localhost along with the files: gdevilspie_0.5-3.1_all.deb gdevilspie_0.5-3.1.dsc gdevilspie_0.5-3.1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722912: libclutter-1.0-0: apt does not find an upgrade path from wheezy to jessie
On Fri, 16 May 2014 at 12:26:10 +0200, Holger Levsen wrote: control: found -1 1.18.2-1 # see https://piuparts.debian.org/wheezy2jessie/fail/libclutter-1.0-0_1.18.2-1.log This appears to have been fixed in jessie's apt. Logs with wheezy's apt/0.9.7.9+deb7u2, and with jessie's apt/1.0.6 plus its dependencies (libc) on an otherwise wheezy system, follow. Does this look familiar to any apt maintainers? Looking at git history, I wonder whether propagate a negative score point along breaks/conflicts and/or check version before adding scores in resolver might be relevant? Should we be recommending that stable users upgrade to jessie's apt before upgrading to jessie, or should the relevant changes be backported into wheezy, or something? Or can the apt maintainers suggest a change to src:clutter-1.0 or src:cogl that would resolve this? I did try adding a local apt source in which I'd given libcogl20 a Breaks/Replaces on libcogl9 to try to prod apt in the right direction, but that wasn't effective. My test steps were: open a (mostly) minimal wheezy-amd64 chroot, apt-get update, apt-get install libclutter-1.0-0, change sources.list to point to jessie, apt-get update, apt-get dist-upgrade. (wheezy-amd64)% sudo apt-get -oDebug::pkgProblemResolver=true --dry-run dist-upgrade Reading package lists... Building dependency tree... Reading state information... Starting Starting 2 Investigating (0) libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) Broken libclutter-1.0-0:amd64 Breaks on libcogl9 [ amd64 ] 1.10.2-7 ( libs ) Considering libcogl9:amd64 0 as a solution to libclutter-1.0-0:amd64 0 Holding Back libclutter-1.0-0:amd64 rather than change libcogl9:amd64 Investigating (1) libcogl20 [ amd64 ] none - 1.18.2-1 ( libs ) Broken libcogl20:amd64 Breaks on libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) ( 1.17) Considering libclutter-1.0-0:amd64 0 as a solution to libcogl20:amd64 2 Upgrading libclutter-1.0-0:amd64 due to Breaks field in libcogl20:amd64 Investigating (1) libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) Broken libclutter-1.0-0:amd64 Breaks on libcogl9 [ amd64 ] 1.10.2-7 ( libs ) Considering libcogl9:amd64 0 as a solution to libclutter-1.0-0:amd64 0 Holding Back libclutter-1.0-0:amd64 rather than change libcogl9:amd64 Investigating (2) libcogl20 [ amd64 ] none - 1.18.2-1 ( libs ) Broken libcogl20:amd64 Breaks on libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) ( 1.17) Considering libclutter-1.0-0:amd64 0 as a solution to libcogl20:amd64 2 Upgrading libclutter-1.0-0:amd64 due to Breaks field in libcogl20:amd64 Investigating (2) libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) Broken libclutter-1.0-0:amd64 Breaks on libcogl9 [ amd64 ] 1.10.2-7 ( libs ) Considering libcogl9:amd64 0 as a solution to libclutter-1.0-0:amd64 0 Holding Back libclutter-1.0-0:amd64 rather than change libcogl9:amd64 Investigating (3) libcogl20 [ amd64 ] none - 1.18.2-1 ( libs ) Broken libcogl20:amd64 Breaks on libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) ( 1.17) Considering libclutter-1.0-0:amd64 0 as a solution to libcogl20:amd64 2 Upgrading libclutter-1.0-0:amd64 due to Breaks field in libcogl20:amd64 Investigating (3) libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) Broken libclutter-1.0-0:amd64 Breaks on libcogl9 [ amd64 ] 1.10.2-7 ( libs ) Considering libcogl9:amd64 0 as a solution to libclutter-1.0-0:amd64 0 Holding Back libclutter-1.0-0:amd64 rather than change libcogl9:amd64 Investigating (4) libcogl20 [ amd64 ] none - 1.18.2-1 ( libs ) Broken libcogl20:amd64 Breaks on libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) ( 1.17) Considering libclutter-1.0-0:amd64 0 as a solution to libcogl20:amd64 2 Upgrading libclutter-1.0-0:amd64 due to Breaks field in libcogl20:amd64 Investigating (4) libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) Broken libclutter-1.0-0:amd64 Breaks on libcogl9 [ amd64 ] 1.10.2-7 ( libs ) Considering libcogl9:amd64 0 as a solution to libclutter-1.0-0:amd64 0 Holding Back libclutter-1.0-0:amd64 rather than change libcogl9:amd64 Investigating (5) libcogl20 [ amd64 ] none - 1.18.2-1 ( libs ) Broken libcogl20:amd64 Breaks on libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) ( 1.17) Considering libclutter-1.0-0:amd64 0 as a solution to libcogl20:amd64 2 Upgrading libclutter-1.0-0:amd64 due to Breaks field in libcogl20:amd64 Investigating (5) libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) Broken libclutter-1.0-0:amd64 Breaks on libcogl9 [ amd64 ] 1.10.2-7 ( libs ) Considering libcogl9:amd64 0 as a solution to libclutter-1.0-0:amd64 0 Holding Back libclutter-1.0-0:amd64 rather than change libcogl9:amd64 Investigating (6) libcogl20 [ amd64 ] none - 1.18.2-1 ( libs ) Broken libcogl20:amd64 Breaks on libclutter-1.0-0 [ amd64 ] 1.10.8-2 - 1.18.2-2 ( libs ) ( 1.17) Considering libclutter-1.0-0:amd64 0 as a solution to libcogl20:amd64
Bug#755315: [openstack-dev] [PKG-Openstack-devel] Bug#755315: [Trove] Should we stop using wsgi-intercept, now that it imports from mechanize? this is really bad!
On Tue, 29 Jul 2014, Thomas Goirand wrote: Sorry, I couldn't reply earlier. No problem. However, from *your* perspective, I wouldn't advise that you keep using such a dangerous, badly maintained Python module. Saying that it's optional may look like you think mechanize is ok and you are vouching for it, when it really shouldn't be the case. Having clean, well maintained dependencies, is IMO very important for a given python module. It shows that you care no bad module gets in. I've pointed a couple of the other wsgi-intercept contributors to this thread to get their opinions on which way is the best way forward, I'd prefer not to make the decision solo. Let me know whenever you have a new release, without mechanize as new dependency, or with it being optional. It will be soon (a day or so). -- Chris Dent tw:@anticdent freenode:cdent https://tank.peermore.com/tanks/cdent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640604: marked as done (debsigs: installation fails: Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed!)
Your message dated Tue, 29 Jul 2014 12:29:37 +0200 with message-id 20140729102937.ga22...@gaara.hadrons.org and subject line Re: Bug#640604: debsigs: installation fails: Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed! has caused the Debian Bug report #640604, regarding debsigs: installation fails: Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 640604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debsigs Version: 0.1.17 Severity: serious User: debian...@lists.debian.org Usertags: instest-20110825 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting Starting 2 Done The following NEW packages will be installed: debsigs 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 11 not fully installed or removed. Need to get 52.9 kB of archives. After this operation, 184 kB of additional disk space will be used. Get:1 http://localhost/debian/ sid/main debsigs all 0.1.17 [52.9 kB] Fetched 52.9 kB in 0s (969 kB/s) Authenticating /var/cache/apt/archives/debsigs_0.1.17_all.deb ... debsig: Origin Signature check failed. This deb might not be signed. dpkg: error processing /var/cache/apt/archives/debsigs_0.1.17_all.deb (--unpack): Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed! configured to not write apport reports Errors were encountered while processing: /var/cache/apt/archives/debsigs_0.1.17_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) The full build log is available from: http://people.debian.org/~lucas/logs/2011/08/25/debsigs.log It is reproducible by installing your package in a clean chroot, using the debconf Noninteractive frontend, and priority: critical. This test was carried out using about 50 AMD64 nodes of the Grid'5000 platform. Internet was not accessible from the nodes. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Hi! On Thu, 2014-06-12 at 01:41:56 +0200, Guillem Jover wrote: On Mon, 2011-09-05 at 21:53:59 +0200, Lucas Nussbaum wrote: Package: debsigs Version: 0.1.17 Severity: serious User: debian...@lists.debian.org Usertags: instest-20110825 instest The following NEW packages will be installed: debsigs 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 11 not fully installed or removed. Need to get 52.9 kB of archives. After this operation, 184 kB of additional disk space will be used. Get:1 http://localhost/debian/ sid/main debsigs all 0.1.17 [52.9 kB] Fetched 52.9 kB in 0s (969 kB/s) Authenticating /var/cache/apt/archives/debsigs_0.1.17_all.deb ... debsig: Origin Signature check failed. This deb might not be signed. dpkg: error processing /var/cache/apt/archives/debsigs_0.1.17_all.deb (--unpack): Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed! configured to not write apport reports Errors were encountered while processing: /var/cache/apt/archives/debsigs_0.1.17_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) The full build log is available from: http://people.debian.org/~lucas/logs/2011/08/25/debsigs.log It is reproducible by installing your package in a clean chroot, using the debconf Noninteractive frontend, and priority: critical. No, It's not, this bug report seems bogus to me. In the log from the URL the packages start to fail to install just after debsig-verify gets unpacked, so this cannot really be a bug in debsigs, it could be at most a bug in either debsig-verify or dpkg. But as mentioned in the subsequent replies dpkg has shipped with no-debsig in its default dpkg.cfg file for a while. So my assumption is that the chroot used had an empty or custom dpkg.cfg w/o that option enabled, i.e. a problem in the setup. And no, there's no need for any signing of the debsigs package at all, because those would get rejected at this point in time anyway. As such this bug should be closed, but I'll leave that to the maintainer. It's a pitty though that the package got removed from stable due to a bogus bug report. :( Ok, closing now, so that the package can proceed to testing, and
Processed: Re: Bug#755513: nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1
Processing control commands: found -1 ocl-icd-libopencl1/2.1.3-4 Bug #755513 [nvidia-opencl-dev] nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1 The source ocl-icd-libopencl1 and version 2.1.3-4 do not appear to match any binary packages Marked as found in versions ocl-icd-libopencl1/2.1.3-4. -- 755513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755513 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#755513: nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1
Control: found -1 ocl-icd-libopencl1/2.1.3-4 But nvidia-opencl-dev conflicts with opencl-dev, and ocl-icd-liopencl1 conflicts with libopencl1. There is no explicit conflict between each other. As long as ocl-icd-liopencl1 is providing a file that conflicts with nvidia-opencl-dev, they should conflict with each other. If you install ocl-icd-opencl-dev *after* nvidia-cuda-toolkit, the problem does not occur. That's because ocl-icd-libopencl1 has Replaces: nvidia-libopencl1-dev Both packages simply having Replaces, and no Conflicts/Breaks, could work. # dpkg-deb -c /var/cache/apt/archives/ocl-icd-libopencl1_2.1.3-4_amd64.deb | grep libOpenCL.so -rw-r--r-- root/root 35200 2014-02-07 00:38 ./usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0 lrwxrwxrwx root/root 0 2014-02-07 00:38 ./usr/lib/x86_64-linux-gnu/libOpenCL.so - libOpenCL.so.1.0.0 lrwxrwxrwx root/root 0 2014-02-07 00:38 ./usr/lib/x86_64-linux-gnu/libOpenCL.so.1 - libOpenCL.so.1.0.0 # dpkg-deb -c /var/cache/apt/archives/nvidia-opencl-dev_5.5.22-4_amd64.deb | grep libOpenCL.so lrwxrwxrwx root/root 0 2014-05-25 01:36 ./usr/lib/x86_64-linux-gnu/libOpenCL.so - libOpenCL.so.1 # dpkg-deb -c /var/cache/apt/archives/nvidia-libopencl1_340.24-2_amd64.deb | grep libOpenCL -rw-r--r-- root/root 21712 2014-07-03 00:18 ./usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0 lrwxrwxrwx root/root 0 2014-07-20 10:31 ./usr/lib/x86_64-linux-gnu/libOpenCL.so.1 - libOpenCL.so.1.0.0 So, Either nvidia-libopencl1-dev should gain a Replaces: ocl-icd-libopencl1. Or ocl-icd-libopencl1 should Conflict on nvidia-libopencl1-dev, instead of Replacing it. The first option allows higher installability. The second option keeps all the relationships confined to ocl-icd-libopencl1, which is the package breaking policy (#679228). SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 640604 in debsigs/0.1.17
Processing commands for cont...@bugs.debian.org:
notfound 640604 debsigs/0.1.17
Bug #640604 {Done: Guillem Jover guil...@debian.org} [debsigs] debsigs:
installation fails: Verification on package
/var/cache/apt/archives/debsigs_0.1.17_all.deb failed!
No longer marked as found in versions debsigs/0.1.17.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
640604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640604
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#752075: daemontools-run: Add systemd support
Hi Michael, On Fri, Jul 18, 2014 at 08:06:11PM +0200, Michael Stapelberg wrote: Gerrit Pape p...@dbnbgs.smarden.org writes: I'm really not keen to add a dependency to daemontools-run, esp. not to the runit package, just for (un)installing and starting/stopping a service. I presume you mean init-system-helpers as the dependency you don???t want to add. Any dependency: $ apt-cache show runit |grep ^Depends $ apt-cache show daemontools-run |grep ^Depends Depends: daemontools ( 1:0.76) $ apt-cache show daemontools |grep ^Depends Depends: libc6 (= 2.7-1) $ Why isn't it as simple as installing the unit, and then?: systemd not installed || start service It is as simple as that. deb-systemd-invoke supports policy-rc.d, though, which your intended example (AIUI) does not. You???d make some users really unhappy if you break policy-rc.d with your package. I don't think so. The daemontools-run and runit packages don't include init scripts. policy-rc.d never had an effect on them, so nothing will break. systemd not installed || have service started by default When systemd is not installed, where does the logic for having the service started by default come from? While the actually relevant part of that is as simple as creating a symlink, there are some things make this entire process more complicated. Some of them come from the fact I hope this as simple as creating a symlink works out. that the enabled-state needs to be synchronized across init systems, i.e. what you do in systemd should also work for the sysvinit-fallback. This is not necessary for the packages in question. They have an inittab entry since many years SV:123456:respawn:/usr/sbin/runsvdir-start The whole purpose of the packages is to provide this service, no enabled-state is needed. $ apt-cache show runit |grep ^Description-en Description-en: system-wide service supervision $ apt-cache show daemontools-run |grep ^Description-en Description-en: daemontools service supervision $ Further, consider this (from the manpage of deb-systemd-helper): The enable action will only be performed once (when first installing the package). On the first enable, an state file is created which will be deleted upon purge. ???which enables administrators to disable units and not have them magically re-enabled on the next package upgrade. See above, I don't think this applies. Also, the dh-systemd/deb-systemd-helper combination properly handles mask-after-remove (i.e. remove but not purge). Anything wrong in this regard with my current implementation? In general, it???s hugely beneficial to Debian if packages use the same helpers/debhelper addons to build their maintainer scripts. Bugfixes and other improvements that we put into i-s-h will propagate to all packages without coordinating huge updates/fixes. You don???t need to think about all the intricacies of correctly handling unit files (in Debian!) because we already did it. We're different individuals in Debian and have different opinions. To me it's beneficial to Debian if there still exist packages not using debhelper, doing things differently than others, even than the masses, following KISS. I want to think about and understand how the inittab entry SV:123456:respawn:/usr/sbin/runsvdir-start translates most easily into a systemd service, now that I learned that this is necessary because systemd doesn't provide backward compatibility for such services. Let me also point out that _every_ system already has i-s-h installed these days, so there really is no cost in adding this dependency. That's not true. Just a few of my systems have this package pulled in, all of them have runit installed. Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 755513
Processing commands for cont...@bugs.debian.org: affects 755513 ocl-icd-libopencl1 Bug #755513 [nvidia-opencl-dev] nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1 Added indication that 755513 affects ocl-icd-libopencl1 thanks Stopping processing here. Please contact me if you need assistance. -- 755513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755513 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#756376: kontact immediately crashes (SIGSEGV) on startup
Package: libkontactinterface4 Version: 4:4.13.3-1 Severity: serious Justification: breaks Kontact, should not migrate to testing Forwarded: https://bugs.kde.org/show_bug.cgi?id=337876 Hi, see below. Downgrading myself fixes the problem for me, too. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- Forwarded message -- From: t...@online.de Message-ID: bug-337876-159046-ewfv7xy...@http.bugs.kde.org/ Sender: bugzilla_nore...@kde.org To: t.gla...@tarent.de Date: Tue, 29 Jul 2014 11:01:38 + Subject: [kontact] [Bug 337876] kontact immediately crashes (SIGSEGV) on startup Reply-To: bug-cont...@bugs.kde.org https://bugs.kde.org/show_bug.cgi?id=337876 t...@online.de changed: What|Removed |Added CC||t...@online.de --- Comment #1 from t...@online.de --- I have a similar setup (Debian unstable, amd64) and faced the same problem after my last update. I noted that libkontactinterface4 was updated from 4:4.12.4-1 to 4:4.13.3-1. Downgrading it back to 4:4.12.4-1 (using the package from debian testing) helped. It seems to be a debian packaging problem mixing up kde 4.12 and kde 4.13 stuff... -- You are receiving this mail because: You reported the bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752075: daemontools-run: Add systemd support
On Mon, Jul 28, 2014 at 02:36:06PM +0200, Michael Biebl wrote: Since you are going to do it your way anyway I'm not sure why you ask for feedback from us? It's like talking to a brick wall. Hi, I'm sorry that you feel this way. I also found our communication far from ideal, and after I refused to add a dependency to the daemontools-run and runit packages, it failed completely. To me this feels like do it your way, or no way. Since you're the specialists, there's still hope to get feedback other than On Tue, Jul 22, 2014 at 03:03:02PM +0200, Michael Biebl wrote: There is a reason, why we added the logic in a single place. On Tue, Jul 22, 2014 at 06:11:24PM +0200, Michael Stapelberg wrote: I'm not sure how we can state this more clearly: Use dh-systemd or you _will_ have bugs sooner or later. It is the most simple implementation that we could come up with. There also are reasons for my design choice. There are still various issues with the maintainer scripts code [1] Please tell me which ones. [1] aside from the fact that negative clauses make it unnecessarily hard to read. The fact is that people are different. To me this is most intuitively to read in set -e scripts. When does this script stop?: set -e true true false false || true false false false true || true false true false true || false true true || false true true false true false false and I see you dropped the .path unit again? Yes. I don't understand the question. On Tue, Jul 22, 2014 at 03:18:02PM +0200, Michael Biebl wrote: What about Ansgar's improvements/suggestions [1]? E.g. adding a Documentation= header, directly using svscan, etc? Thanks to Ansgar, I looked at them but currently don't want to do a bit more integration into systemd. KISS and provide the very same software experience to users of these packages under sysvinit, runit, and systemd. Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752075: daemontools-run: Add systemd support
Hi Michael, On Tue, Jul 22, 2014 at 06:11:24PM +0200, Michael Stapelberg wrote: I'm not sure how we can state this more clearly: Use dh-systemd or you _will_ have bugs sooner or later. It is the most simple implementation that we could come up with. sorry, we have different points of view, and I will definitely not switch my packages to debhelper. Sure, most probably there will be bugs sooner or later, considering that systemd intergration is still under development. But also for packages utilizing debhelper, maybe even more more so because the implementation is more complex. They'll probably go through binary NMUs. Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755787: marked as done (percona-xtrabackup: maintainer address bounces)
Your message dated Tue, 29 Jul 2014 11:34:14 + with message-id e1xc5fa-jf...@franck.debian.org and subject line Bug#755787: fixed in percona-xtrabackup 2.2.3-2 has caused the Debian Bug report #755787, regarding percona-xtrabackup: maintainer address bounces 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.) -- 755787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: percona-xtrabackup Severity: serious X-Debbugs-Cc: george.lo...@percona.com, jamesp...@debian.org The maintainer address for percona-xtrabackup bounces, see below. Ansgar On 07/23/2014 11:41, Mail Delivery Subsystem wrote: Hello ftpmas...@ftp-master.debian.org, We're writing to let you know that the group you tried to contact (dev-public) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post: * You might have spelled or formatted the group name incorrectly. * The owner of the group may have removed this group. * You may need to join the group before receiving permission to post. * This group may not be open to posting. If you have questions related to this or any other Google Group, visit the Help Center at http://support.google.com/a/percona.com/bin/topic.py?topic=25838. Thanks, percona.com admins - Original message - X-Received: by 10.70.100.106 with SMTP id ex10mr8775901pdb.73.1406108488022; Wed, 23 Jul 2014 02:41:28 -0700 (PDT) Return-Path: envel...@ftp-master.debian.org Received: from muffat.debian.org (muffat.debian.org. [2607:f8f0:610:4000:6564:a62:ce0c:1392]) by mx.google.com with ESMTPS id vd9si1909380pab.148.2014.07.23.02.41.27 for multiple recipients (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 23 Jul 2014 02:41:27 -0700 (PDT) Received-SPF: none (google.com: envel...@ftp-master.debian.org does not designate permitted sender hosts) client-ip=2607:f8f0:610:4000:6564:a62:ce0c:1392; Authentication-Results: mx.google.com; spf=neutral (google.com: envel...@ftp-master.debian.org does not designate permitted sender hosts) smtp.mail=envel...@ftp-master.debian.org Received: from franck.debian.org ([138.16.160.12]) from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=franck.debian.org,EMAIL=hostmas...@franck.debian.org (verified) by muffat.debian.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from envel...@ftp-master.debian.org) id 1X9t39-0001WX-7N; Wed, 23 Jul 2014 09:41:27 + Received: from dak by franck.debian.org with local (Exim 4.80) (envelope-from envel...@ftp-master.debian.org) id 1X9t37-0007Ml-Tt; Wed, 23 Jul 2014 09:41:25 + From: Debian FTP Masters ftpmas...@ftp-master.debian.org To: Percona XtraBackup Development Team mysql-...@percona.com, George Ormond Lorch III george.lo...@percona.com, jamesp...@debian.org X-DAK: dak process-upload X-Debian: DAK X-Debian-Package: percona-xtrabackup Precedence: bulk Auto-Submitted: auto-generated MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: percona-xtrabackup_2.2.3-1_amd64.changes ACCEPTED into unstable Message-Id: e1x9t37-0007ml...@franck.debian.org Sender: Archive Administrator d...@franck.debian.org Date: Wed, 23 Jul 2014 09:41:25 + Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 21 Jul 2014 16:04:36 -0700 Source: percona-xtrabackup Binary: percona-xtrabackup percona-xtrabackup-dbg percona-xtrabackup-test xtrabackup Architecture: source amd64 all Version: 2.2.3-1 Distribution: unstable Urgency: low Maintainer: Percona XtraBackup Development Team mysql-...@percona.com Changed-By: George Ormond Lorch III george.lo...@percona.com Description: percona-xtrabackup - Open source backup tool for InnoDB and XtraDB percona-xtrabackup-dbg - Debug symbols for Percona XtraBackup percona-xtrabackup-test - Test suite for Percona XtraBackup xtrabackup - Transitional package for percona-xtrabackup Closes: 751377 Changes: percona-xtrabackup (2.2.3-1) unstable; urgency=low . * New upstream release 2.2.3 (Closes: #751377). Checksums-Sha1: bf5c9d4da2f5e2cff994b2a2a6acd4be86db3434 2320 percona-xtrabackup_2.2.3-1.dsc 1d23f0bd767ebe59655a1b84e0c42688bc44c640 34584359 percona-xtrabackup_2.2.3.orig.tar.gz 5fbe8469fbd6c1042eb14b7739a7caf690db0f9b 13476
Bug#756382: libembperl-perl: FTBFS: #236 EmbperlObject/epobase.htm test failure: Error in Line 8
Package: libembperl-perl Version: 2.5.0-1 Severity: serious Tags: patch This package fails to build on current sid/amd64: Testing mod_perl mode... [...] #235 EmbperlObject/errdoc/epoerrdoc2.htm...ok #236 EmbperlObject/epobase.htm... Error in Line 8 Is: /p Should: /BODY/HTML Input: test/html/EmbperlObject/epobase.htm Output: test/tmp/out.htm Compared to:test/cmp/epobase.htm Log:test/tmp/test.log Testparameter: errors = 1 offline = 0 cgi = 0 ERRORS detected! NOT all tests have been passed successfully Makefile:1613: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 8 This diff shows the problem: --- test/cmp/epobase.htm2014-07-29 14:16:55.223944564 +0300 +++ test/tmp/out.htm2014-07-29 14:18:46.785998659 +0300 @@ -1,10 +1,9 @@ !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN -HTMLHEAD -TITLE403 Forbidden/TITLE -/HEADBODY -H1Forbidden/H1 -^.*?You don't have permission to access /embperl/EmbperlObject/epobase.htm -^on this server -/BODY/HTML - - +htmlhead +title403 Forbidden/title +/headbody +h1Forbidden/h1 +pYou don't have permission to access /embperl/EmbperlObject/epobase.htm +on this server.br / +/p +/body/html The apache2 error page was changed slightly by this upstream commit: https://github.com/apache/httpd/commit/4f8fc53c8f6df76a42ccc89275fcede72f9e https://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/modules/http/http_protocol.c?r1=1487127r2=1610328 which was included in apache2 2.4.10, recently uploaded in sid. Patch attached, this works for me with both 2.4.9 and 2.4.10. -- Niko Tyni nt...@debian.org From bcce23a15de55a39478f83a7923d8a89f681cc19 Mon Sep 17 00:00:00 2001 From: Niko Tyni nt...@debian.org Date: Tue, 29 Jul 2014 14:34:35 +0300 Subject: [PATCH] Adapt to an Apache 2.4.10 error page change The Forbidden error page was slightly changed by Apache commit https://github.com/apache/httpd/commit/4f8fc53c8f6df76a42ccc89275fcede72f9e https://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/modules/http/http_protocol.c?r1=1487127r2=1610328 breaking the EmbperlObject/epobase.htm test. The fix works with both the old and the new page format. --- test/cmp/epobase.htm | 1 + 1 file changed, 1 insertion(+) diff --git a/test/cmp/epobase.htm b/test/cmp/epobase.htm index ba29386..9d0269c 100644 --- a/test/cmp/epobase.htm +++ b/test/cmp/epobase.htm @@ -5,6 +5,7 @@ H1Forbidden/H1 ^.*?You don't have permission to access /embperl/EmbperlObject/epobase.htm ^on this server +^-/p /BODY/HTML -- 2.0.1
Bug#756383: missing license in debian/copyright
Package: adacgi Version: 1.6-18 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: adacgi.spec 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#756385: missing license in debian/copyright
Package: adasockets Version: 1.8.11-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: doc/adasockets.texi 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#753955: marked as done (adacgi1: not installable in sid)
Your message dated Tue, 29 Jul 2014 12:00:06 + with message-id e1xc64c-dq...@franck.debian.org and subject line Bug#753955: fixed in adacgi 1.6-18 has caused the Debian Bug report #753955, regarding adacgi1: not installable in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 753955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: adacgi1 Version: 1.6-17 Severity: grave User: trei...@debian.org Usertags: edos-uninstallable Hi, adacgi1 is not installable in sid, at least since 2014-05-02. The reason is that it depends both on gnat and gnat-4.6. However, gnat depends on gnat-4.9 which is in Conflict with gnat-4.6. -Ralf. ---End Message--- ---BeginMessage--- Source: adacgi Source-Version: 1.6-18 We believe that the bug you reported is fixed in the latest version of adacgi, 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 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Phil Brooke p...@debian.org (supplier of updated adacgi 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, 22 Jul 2014 13:46:45 +0100 Source: adacgi Binary: adacgi2 Architecture: source amd64 Version: 1.6-18 Distribution: unstable Urgency: medium Maintainer: Phil Brooke p...@debian.org Changed-By: Phil Brooke p...@debian.org Description: adacgi2- Ada CGI interface Closes: 753955 755007 Changes: adacgi (1.6-18) unstable; urgency=medium . * Update GNAT version to 4.9. Also rename to adacgi2 and bump ALIVERSION in debian/rules. (Closes: 755007, 753955.) * Bump to standards version 3.9.5. Checksums-Sha1: 0f55d4e190de68794b9a3e75da5b9ed0e69299ca 1661 adacgi_1.6-18.dsc 2403d1c1b314f658ada06251472335597eb9f9b9 4362 adacgi_1.6-18.diff.gz 979ae815526d289aaa5e7c3a366f1c7f73fd7a0b 82830 adacgi2_1.6-18_amd64.deb Checksums-Sha256: 12089d00d547f91239d158e1dbb6c801655c5d4daa6f04160ff425cd2da1c6e8 1661 adacgi_1.6-18.dsc 75e82f761056099bffe02c97e2f3680e0c0bf768d6bd569d8580383533d4e41e 4362 adacgi_1.6-18.diff.gz 6d0046dedf3f059be1f227922f746bbccc11b4e1e63cacbd91489ac1396948de 82830 adacgi2_1.6-18_amd64.deb Files: af2b293bb06bf39f0039b5e5d678e891 82830 web optional adacgi2_1.6-18_amd64.deb 10f779f7375d92c8828541273344f08c 1661 devel optional adacgi_1.6-18.dsc cad312f779f151048f6aa611e719423c 4362 devel optional adacgi_1.6-18.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJTznHUAAoJEIGdJ4oOb5kqPegP+gOaW/jQ2VMbOY8mfWYMN3+e 7CdDZZaxoUBS0pwjVkGUN2qalHXcxiMdOS/0XsfoXVDDGd3WdA2DgwDKmWKnqhAY HXewCxPYASAlpv73Ub28osLW20j2qjI2CLrqpUVz1mXPPA8cAeweGQ8dRgOfILoE yPytzC7a4FxQEkcMVM6K4Dm/bmBNj+OySJ8Ep8nrCOUl2DqCM27AvAebJ3L4Z5RH VbbagwV0TEHtMimBTKldnkgXtY8KUgxwqxdV/JEQSiI/KujYIQBKV4sWxCrKrUn8 g+9BpOfnY+W4bVE7b3aDH4RVdWTATlydluopLw+gDfts+BmjS4ns0dIqPOTlLyXs qRdJG1+UEkZXuuyuCQNufWxzoDHg3Uni0JI1q5w0O5zQ8pSrRTk9tGLNuLkx760o MJrUq4UfsMTiWnDPC5dH1n3W1+H5h9byO+L2kfNeGtA/SitrhX1QNUt2WYZMzf4H v5QSzH7k9qhmx9KBUC4G7Hv0y8FAms2wGYlCn4FPVSimJO3tIPVE1+zjrclEz9iO qFGvDxZ2N4ysE5bpeaXlA8w6Y/EFYTtnVcnHLZ95HCQ7mHPOWshtH2uLHzjNmwPF A7jU1DbodTLHI8UGdBrKfP781Cy0WgkAFId/nQz9WUqS+TaiN4OoHuzpp1PEdZeK tbciAOjQXloLWo7rK2bm =pKpk -END PGP SIGNATUREEnd Message---
Bug#755009: marked as done (adasockets: uninstallable on sid, needs update for gnat-4.9)
Your message dated Tue, 29 Jul 2014 12:00:07 +
with message-id e1xc64d-do...@franck.debian.org
and subject line Bug#755009: fixed in adasockets 1.8.11-1
has caused the Debian Bug report #755009,
regarding adasockets: uninstallable on sid, needs update for gnat-4.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
755009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: adasockets
Version: 1.8.10-2
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
This package depends on a old gnat version. Currently it doesn't build on
ppc64el because ppc64el support started on GCC/GNAT 4.8, so, I would like if
you can increase the gnat version on the dependencies, to a more recent version.
I am providing a patch that would do it for you, updating to gnat version 4.8.
On the other side, if you want to continue to use the current gnat version, you
can do something like:
-Depends: gnat-4-6
+Depends: gnat-4.6 [!ppc64el] | gnat-4.9 [ppc64el]
Thank you,
Breno
Index: adasockets-1.8.10/debian/control
===
--- adasockets-1.8.10.orig/debian/control
+++ adasockets-1.8.10/debian/control
@@ -3,11 +3,11 @@ Maintainer: Phil Brooke p...@debian.org
Section: devel
Priority: extra
Standards-Version: 3.9.3
-Build-Depends: gnat, gnat-4.6, debhelper (= 6.0.0), texinfo, texlive
+Build-Depends: gnat, gnat-4.8, debhelper (= 6.0.0), texinfo, texlive
Package: libadasockets4-dev
Architecture: any
-Depends: gnat, gnat-4.6, libadasockets4 (=${binary:Version}), ${misc:Depends}, dpkg (= 1.15.4) | install-info
+Depends: gnat, gnat-4.8, libadasockets4 (=${binary:Version}), ${misc:Depends}, dpkg (= 1.15.4) | install-info
Section: libdevel
Conflicts: adasockets, libadasockets0-dev, libadasockets-dev, libadasockets2-dev, libadasockets3-dev
Replaces: adasockets, libadasockets0-dev, libadasockets-dev, libadasockets2-dev, libadasockets3-dev
---End Message---
---BeginMessage---
Source: adasockets
Source-Version: 1.8.11-1
We believe that the bug you reported is fixed in the latest version of
adasockets, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Phil Brooke p...@debian.org (supplier of updated adasockets 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, 22 Jul 2014 13:54:04 +0100
Source: adasockets
Binary: libadasockets5-dev libadasockets5
Architecture: source amd64
Version: 1.8.11-1
Distribution: unstable
Urgency: medium
Maintainer: Phil Brooke p...@debian.org
Changed-By: Phil Brooke p...@debian.org
Description:
libadasockets5 - bindings for socket services in Ada
libadasockets5-dev - bindings for socket services in Ada
Closes: 755009
Changes:
adasockets (1.8.11-1) unstable; urgency=medium
.
* New upstream release.
* Update GNAT version to 4.9. Bump to ALIVERSION 5, with configure
and some files renamed as required. (Closes: #755009.)
* Add lintian override for Ada file (hardening-no-relro).
* Bump standards version to 3.9.5.
Checksums-Sha1:
ace19783b92ce6f1a30acc852bd37479cd2b23e8 1810 adasockets_1.8.11-1.dsc
3bff9709b1c7fa76c0c43ffb2ea4ae25cd3c63d4 751137 adasockets_1.8.11.orig.tar.gz
a6c8289e6395b6342f1b087a142ee2e0a99c01e0 23514 adasockets_1.8.11-1.diff.gz
04da5e8972745d2cdceec688670dd3ec343277fa 318374
libadasockets5-dev_1.8.11-1_amd64.deb
9d174c454c5d9126e1d9829a0dab414dde7451c5 33666
libadasockets5_1.8.11-1_amd64.deb
Checksums-Sha256:
aa0e49930e3dfa359920ea1f6727d38b788e742f3c23e09eaaefe46e5a45efb8 1810
adasockets_1.8.11-1.dsc
65f9dccb3a8c46a47e3f53eb42b4f3329a699ab410b60436d583575dd2bbfef6 751137
adasockets_1.8.11.orig.tar.gz
763ffe4fdf35cea68de7c0061359c5ac7902a5ec6446467a1ea4cd20bd590739 23514
adasockets_1.8.11-1.diff.gz
81790f25dc616ea3a0d396f7fff053b7c5842777418dccf78307abd0e50923d5 318374
libadasockets5-dev_1.8.11-1_amd64.deb
f5e7116b70364192c6e583e8029d1b921c1435875abd5d0027edf5f9794d73b9 33666
libadasockets5_1.8.11-1_amd64.deb
Files:
Bug#755360: marked as done (junior-tasks: tasks-desc(ription) is installed one directory to high)
Your message dated Tue, 29 Jul 2014 12:00:08 + with message-id e1xc64e-ev...@franck.debian.org and subject line Bug#755360: fixed in debian-junior 1.22 has caused the Debian Bug report #755360, regarding junior-tasks: tasks-desc(ription) is installed one directory to high 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.) -- 755360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: junior-tasks Version: 1.20 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Trying to install junior-applications via Tasksel * What exactly did you do (or not do) that was effective (or ineffective)? Install junior-tasks * What was the outcome of this action? Not as expected when running tasksel There were no Jr. tasks to be selected * What outcome did you expect instead? Jr. tasks to be selected. Easy to resolve; the debian-junior-tasks.desc is installed in /usr/share/tasksel/ For it to work it needs to be in /usr/share/tasksel/desc/ Just wanted to report this; hope this is not to cumbersome. Thank you for your efforts! -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 junior-tasks depends on: ii tasksel 3.14.1 junior-tasks recommends no packages. junior-tasks suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: debian-junior Source-Version: 1.22 We believe that the bug you reported is fixed in the latest version of debian-junior, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated debian-junior 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, 25 Jul 2014 09:20:05 +0200 Source: debian-junior Binary: junior-tasks junior-config junior-arcade junior-art junior-education junior-games-card junior-games-gl junior-games-net junior-games-sim junior-games-text junior-internet junior-math junior-programming junior-puzzle junior-sound junior-system junior-toys junior-typing junior-writing Architecture: source all Version: 1.22 Distribution: unstable Urgency: medium Maintainer: Debian Junior debian...@lists.debian.org Changed-By: Andreas Tille ti...@debian.org Description: junior-arcade - Debian Jr. arcade games junior-art - Debian Jr. Art junior-config - Debian Jr. Project common package junior-education - Debian Jr. education applications junior-games-card - Debian Jr. Card Games junior-games-gl - Debian Jr. 3D Games (hardware acceleration required) junior-games-net - Debian Jr. Network Games junior-games-sim - Debian Jr. Simulation Games junior-games-text - Debian Jr. Text Games junior-internet - Debian Jr. Internet tools junior-math - Debian Jr. educational math junior-programming - Debian Jr. programming junior-puzzle - Debian Jr. Puzzles junior-sound - Debian Jr. sound junior-system - Debian Jr. System tools junior-tasks - Debian Jr. tasks for tasksel junior-toys - Debian Jr. desktop toys junior-typing - Debian Jr. typing junior-writing - Debian Jr. writing Closes: 755360 Changes: debian-junior (1.22) unstable; urgency=medium . * Build-Depends: blends-dev (= 0.6.91) Closes: #755360 * Fix syntax in doudoulinux tasks and make them better readable by applying some grouping of dependencies * d/compat: 9 * d/control.stub - Standards-Version: 3.9.5 - canonical Vcs fields * d/source/format: 3.0 (native) Checksums-Sha1: 116ed401f0440568838aa9c6e6f8f3dd1c1ea241 2697 debian-junior_1.22.dsc 3f79ebb88b8bc904d28d0dca8a877a9d144a4399 21472 debian-junior_1.22.tar.xz 14d8c9bb1c5d59db9b39254613ac1f7fb72c99ed
Bug#735649: marked as done (ruby-amrita2: FTBFS: undefined method `to_a' for #String:0x0000000139e198 (NoMethodError))
Your message dated Tue, 29 Jul 2014 12:19:40 + with message-id e1xc6ny-00038w...@franck.debian.org and subject line Bug#756381: Removed package(s) from unstable has caused the Debian Bug report #735649, regarding ruby-amrita2: FTBFS: undefined method `to_a' for #String:0x000139e198 (NoMethodError) 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.) -- 735649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-amrita2 Severity: serious Usertags: ruby18-removal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, your packag does not work with newer rubies: Entering dh_ruby --install install -d /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/testsupport.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/testsupport.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/gettext.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/gettext.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/macro.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/macro.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/version.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/version.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/rails_bridge.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/rails_bridge.rb install -D -m644 /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/lib/amrita2/template.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1352:in `process_block': undefined method `to_a' for #String:0x000139e198 (NoMethodError) from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1335:in `process' from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1178:in `setup' from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2/usr/lib/ruby/vendor_ruby/amrita2/template.rb:1202:in `render_with' from /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/sample/hello/hello.rb:13:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from debian/ruby-tests.rb:1:in `main' ERROR: Test ruby1.9.1 failed. Exiting. dh_auto_install: dh_ruby --install /«BUILDDIR»/ruby-amrita2-2.0.2+dfsg.1/debian/ruby-amrita2 returned exit code 1 make: *** [binary] Error 1 Thanks, Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJS2PiDAAoJEPBM7/YBbP/QZ9AP/2HbFfC1UuOxVMzhjH+m1h1v ua7urlbzMxvzJTcLfnMNzoDtEE7NOSa1f/Zha9eReE6qTVALKhafesT0KF88GTJf 8lfnCtdeSDUB7OT1c7/JrGypiOvsukeEdrlyF49YO0YISrjHLlP304SNiAEeofoj JFxwOWYm1VU4izZ08S5Sl57u0VP3bJnBtQwJWdXvNmDsMU33Pa9pnQWMJV1pmuNM xv3bS8GVXk/McEP0GLPs8ITawAyQKAGeg9gtPbXa0UGoofts4n8Uv5Gwm8MWx2ZO aloBRCXuZE57PuwGBHpQXXBRmYhc0vBc3Et0bC11+/s+jMlUYrQFRnfcmJxC4HBz 3qN4Ht/p9olre4Lwyie5pp/A1b8EoL2CQMPhaNUOoPsxHnDFNVmhwjy/5TfcqMKu fcNSGBs8IJ+X4K5QE+DmslvfaJ1DqQM5sl7rJxyXdRgK3SiKU4Pj+nk21G8z1AQS BfIATOjMIBLvHMc45jU5fXGwOb/hCvvere5oijQr88WYbgkpcPpEBY7cGZbCWoND rSfMsy0gDwM2WvAUD5m3H3kc8X5u+ENaTnvLanXBZHpPIi7mDxakey15AJ1lc+iE kyV06izltKOA+mQN6fq/URbrfz6NweJMvBUKWff2TrdacxE84FzSgOPQ4NWI8yZI p4cnS9RdDhpXzv2bz4SZ =6nox -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Version: 2.0.2+dfsg.1-3+rm Dear submitter, as the package ruby-amrita2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/756381 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was
Bug#752796: marked as done (nginx: hardcodes /usr/lib/perl5)
Your message dated Tue, 29 Jul 2014 12:19:20 +
with message-id e1xc6ne-00034q...@franck.debian.org
and subject line Bug#752796: fixed in nginx 1.6.0-2
has caused the Debian Bug report #752796,
regarding nginx: hardcodes /usr/lib/perl5
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.)
--
752796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nginx
Version: 1.6.0-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition
Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the vendorarch library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.
For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.
This package fails to build with perl_5.20.0-1 from experimental:
dh_install -a
cp -a ./debian/build-full/objs/nginx debian/nginx-full/usr/sbin/
cp -a ./debian/build-light/objs/nginx debian/nginx-light/usr/sbin/
cp -a ./debian/build-extras/objs/nginx debian/nginx-extras/usr/sbin/
cp -a
debian/tmp/debian/build-extras/objs/src/http/modules/perl/blib/arch/auto/nginx/nginx.bs
debian/nginx-extras/usr/lib/perl5/auto/nginx/
cp: cannot stat
'debian/tmp/debian/build-extras/objs/src/http/modules/perl/blib/arch/auto/nginx/nginx.bs':
No such file or directory
dh_install: cp -a
debian/tmp/debian/build-extras/objs/src/http/modules/perl/blib/arch/auto/nginx/nginx.bs
debian/nginx-extras/usr/lib/perl5/auto/nginx/ returned exit code 1
make: *** [binary-arch] Error 2
One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.
Please ask on the debian-perl list if you want help with this, and see
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
--
Niko Tyni nt...@debian.org
---End Message---
---BeginMessage---
Source: nginx
Source-Version: 1.6.0-2
We believe that the bug you reported is fixed in the latest version of
nginx, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Kartik Mistry kar...@debian.org (supplier of updated nginx package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 29 Jul 2014 04:56:03 +
Source: nginx
Binary: nginx nginx-doc nginx-common nginx-full nginx-full-dbg nginx-light
nginx-light-dbg nginx-extras nginx-extras-dbg nginx-naxsi nginx-naxsi-dbg
nginx-naxsi-ui
Architecture: source all amd64
Version: 1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Kartik Mistry kar...@debian.org
Changed-By: Kartik Mistry kar...@debian.org
Description:
nginx - small, powerful, scalable web/proxy server
nginx-common - small, powerful, scalable web/proxy server - common files
nginx-doc - small, powerful, scalable web/proxy server - documentation
nginx-extras - nginx web/proxy server (extended version)
nginx-extras-dbg - nginx web/proxy server (extended version) - debugging
symbols
nginx-full - nginx web/proxy server (standard version)
nginx-full-dbg - nginx web/proxy server (standard version) - debugging symbols
nginx-light - nginx web/proxy server (basic version)
nginx-light-dbg - nginx web/proxy server (basic version) - debugging symbols
nginx-naxsi - nginx web/proxy server (version with naxsi)
nginx-naxsi-dbg - nginx web/proxy server (version with naxsi) - debugging
symbols
nginx-naxsi-ui - nginx web/proxy server - naxsi configuration front-end
Closes: 752796
Changes:
nginx (1.6.0-2) unstable; urgency=medium
.
[ gregor herrmann ]
* Patch from Gregor Herrmann gre...@debian.org:
Fix hardcodes /usr/lib/perl5:
- drop debian/nginx-extras.dirs, not needed, dh_install uses the
directories from
Bug#756389: libndp: CVE-2014-3554: buffer overflow
Source: libndp Version: 1.3-1 Severity: grave Tags: security upstream patch Hi, the following vulnerability was published for libndp. CVE-2014-3554[0]: buffer overflow If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-3554 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1118583 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704206: teem: FTBFS[any-i386]: testsuite failures
Hi, Based on the patch provided by Adam, the attached patch fixes FTBFS on ppc64el. It adds ppc64el to the arches using -ffp-contract=off. Hoping it helps, Erwan. diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-29 14:15:22.230885507 +0200 +++ b/debian/rules 2014-07-29 14:15:45.574884266 +0200 @@ -16,7 +16,7 @@ ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386)) CFLAGS += -ffloat-store endif -ifneq (,$(filter $(DEB_HOST_ARCH_CPU), powerpc ppc64 s390 s390x)) +ifneq (,$(filter $(DEB_HOST_ARCH_CPU), powerpc ppc64 ppc64el s390 s390x)) CFLAGS += -ffp-contract=off endif
Bug#747270: [Python-modules-team] Bug#747270: python-librabbitmq
On 2014-07-28 07:42, Brian May wrote: Seems like there was already an attempt to package 1.5.0 (1.5.2 is now current), based on changes in subversion. Did this not work out? It did work out to the point where one should be able to build the package, but I did not find the time to test it. I note that the debian/patches/fix_setup.patch has extensive changes to setup.py (this no longer applies cleanly). Cleaning should be relatively easy as this patch just drops all the unnecessary cruft required for building the embedded librabbitmq-c lib. In Debian all this is provided by the librabbitmq library. I also note that the version number was called 1.5.0+dfsg-1, which suggests you had to repackage the orig.tar.gz file - was this the case? See debian/copyright. I excluded the whole embedded librabbitmq-c library. Thus the +dfsg suffix. Cheers, -- Michael Fladischer Fladi.at signature.asc Description: OpenPGP digital signature
Bug#754173: [Tech] Debian kernel fix for routing regression in 3.2.60
Please reply to the bug address (754...@bugs.debian.org, 754...@bugs.debian.org or 754...@bugs.debian.org) to let us know whether this resolves the regression for you. Probably I keep version 3.2.57-3+deb7u2 till a fixed i386 binary is released. Anyway... thanks for your efforts, Ben. Gabor -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#754997: libembperl-perl: FTBFS with Perl 5.20: Test failures
Processing commands for cont...@bugs.debian.org: tag 754997 patch Bug #754997 [libembperl-perl] libembperl-perl: FTBFS with Perl 5.20: Test failures Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 754997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754997 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#754997: libembperl-perl: FTBFS with Perl 5.20: Test failures
tag 754997 patch
thanks
On Wed, Jul 16, 2014 at 09:50:09PM +0300, Niko Tyni wrote:
Package: libembperl-perl
Version: 2.5.0-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition
This package fails to build with Perl 5.20.0
(currently in experimental):
#113 includeerr2.htm...
Expected 2 more error(s) in logfile
Input: test/html/includeerr2.htm
Output: test/tmp/out.htm
Log:test/tmp/test.log
The attached patch adapts the test suite to a few Perl 5.20
diagnostics changes, fixing the build failure.
(I now notice that I didn't update MANIFEST for the new expected
output file, that should be probably done too for tidiness.)
--
Niko Tyni nt...@debian.org
From 5c9f464ab89a634dbc74369ac29c7c6e456fa5c8 Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Tue, 29 Jul 2014 15:21:29 +0300
Subject: [PATCH 2/2] Add compatibility with Perl 5.20
Two error messages have changed slightly, dropping the 'Might be a
multi-line string' notes.
According to https://rt.cpan.org/Public/Bug/Display.html?id=95335
this is due to upstream commit v5.19.3-296-gffdb8b1 so the conditionals
now look for 5.19.4 although this has only been tested with 5.20.0.
Bug: https://rt.cpan.org/Public/Bug/Display.html?id=95335
Bug-Debian: https://bugs.debian.org/754997
---
test.pl | 9 +-
test/cmp/includeerr2.htm520 | 69 +
2 files changed, 77 insertions(+), 1 deletion(-)
create mode 100644 test/cmp/includeerr2.htm520
diff --git a/test.pl b/test.pl
index 9714453..f19445e 100644
--- a/test.pl
+++ b/test.pl
@@ -435,9 +435,16 @@
'errors' = 9,
'version'= 2,
'repeat' = 2,
-'condition' = '$] = 5.018000',
+'condition' = '$] = 5.018000 $] 5.019400',
'cmpext' = '518',
},
+'includeerr2.htm' = {
+'errors' = 7,
+'version'= 2,
+'repeat' = 2,
+'condition' = '$] = 5.019400',
+'cmpext' = '520',
+},
'includeerr3.htm' = {
'errors' = 2,
'condition' = '$] 5.014000',
diff --git a/test/cmp/includeerr2.htm520 b/test/cmp/includeerr2.htm520
new file mode 100644
index 000..a755c10
--- /dev/null
+++ b/test/cmp/includeerr2.htm520
@@ -0,0 +1,69 @@
+HTMLHEADTITLEEmbperl Error/TITLE/HEADBODY bgcolor=#FF
+H1Internal Server Error/H1
+The server encountered an internal error or misconfiguration and was unable to complete your request.P
+^Please contact the server administrator,.*?and inform them of the time the error occurred, and anything you might have done that may have caused the error.PP
+table cellspacing='2' cellpadding='5'
+tr bgcolor='#ee'td
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+^\[\d+\]ERR: 32: Warning in Perl code: Use of uninitialized value \$Embperl::__\d+::param\[0\] in concatenation \(\.\) or string at .+incsub.htm line 6.
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+/td/tr
+tr bgcolor='#ee'td
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+^\[\d+\]ERR: 32: Warning in Perl code: Use of uninitialized value \$Embperl::__\d+::param\[0\] in concatenation \(\.\) or string at .+incsub.htm line 6.
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+/td/tr
+tr bgcolor='#ee'td
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+^\[\d+\]ERR: 32: Warning in Perl code: Use of uninitialized value \$Embperl::__\d+::param\[0\] in concatenation \(\.\) or string at .+incsub.htm line 6.
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+/td/tr
+tr bgcolor='#ee'td
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+^\[\d+\]ERR: 32: Warning in Perl code: Use of uninitialized value \$Embperl::__\d+::param\[0\] in concatenation \(\.\) or string at .+incsub.htm line 6.
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+/td/tr
+tr bgcolor='#ee'td
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+^\[\d+\]ERR: 24: Error in Perl code: Can't locate object method quot;isquot; via package quot;herequot; \(perhaps you forgot to load quot;herequot;\?\) at .+incerr.htm line 6.
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+/td/tr
+tr bgcolor='#ee'td
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+^\[\d+\]ERR: 32: Warning in Perl code: Unquoted string quot;tablequot; may clash with future reserved word at .+incerr.htm line 6.
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+/td/tr
+tr bgcolor='#ee'td
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+^\[\d+\]ERR: 32: Warning in Perl code: Unquoted string quot;tdquot; may clash with future reserved word at .+incerr.htm line 8.
+!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
+/td/tr
+tr
Processed: Pending fixes for bugs in the libembperl-perl package
Processing commands for cont...@bugs.debian.org: tag 756382 + pending Bug #756382 [libembperl-perl] libembperl-perl: FTBFS: #236 EmbperlObject/epobase.htm test failure: Error in Line 8 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 756382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756382 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#754997: Pending fixes for bugs in the libembperl-perl package
tag 754997 + pending thanks Some bugs in the libembperl-perl package are closed in revision 99a52ac51cba275dc0844093cedd88c0c62548d1 in branch 'master' by Damyan Ivanov The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libembperl-perl.git;a=commitdiff;h=99a52ac Commit message: add patch from Niko Tyni adapting tests to changed error messages in perl 5.20 Closes: #754997 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libembperl-perl package
Processing commands for cont...@bugs.debian.org: tag 754997 + pending Bug #754997 [libembperl-perl] libembperl-perl: FTBFS with Perl 5.20: Test failures Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 754997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754997 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#756382: Pending fixes for bugs in the libembperl-perl package
tag 756382 + pending thanks Some bugs in the libembperl-perl package are closed in revision f9e825e287fcdeab9052962e02770dc19dc6a984 in branch 'master' by Damyan Ivanov The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libembperl-perl.git;a=commitdiff;h=f9e825e Commit message: add patch from Niko Tyni adapting tests to changed error message in apache 2.4 Closes: #756382 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732424: (no subject)
This is also affecting ppc64el, as shown: http://ftp.unicamp.br/pub/ppc64el/debian/buildd-upstream/build_logs/logs/gstreamer0.10_0.10.36-1.2_ppc64el.build -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755513: nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1
On 29/07/2014 12:41, Stefano Rivera wrote:
The first option allows higher installability. The second option keeps
all the relationships confined to ocl-icd-libopencl1, which is the
package breaking policy (#679228).
Thanks Stefano. I had a closer look at ocl-icd and I think I am seeing
the real issue now.
Package ocl-icd-libopencl1 has both conflicts and replaces on
nvidia-libopencl1-dev, but this package no longer exists.
From what I can glean from the changelogs (excerpts follow), the
unversioned libOpenCL.so symlink was removed from package
nvidia-libopencl1-dev, built by nvidia-graphics-drivers, and is now
shipped in package nvidia-opencl-dev, built by nvidia-cuda-toolkit.
I attach a new patch for ocl-icd which seems to do the right thing now.
nvidia-graphics-drivers (256.53-2) experimental; urgency=low
* Drop libcuda1-dev and nvidia-libopencl1-dev packages, move libOpenCL.so
link to nvidia-libopencl1. libcuda1 and nvidia-libopencl1
Conflicts and
Replaces their old -dev packages for clean upgrades without
transitionals.
-- Andreas Beckmann deb...@abeckmann.de Mon, 11 Oct 2010 14:50:06 +0200
nvidia-graphics-drivers (304.88-7) unstable; urgency=low
* nvidia-libopencl1.links: Stop shipping libOpenCL.so, will be moved to
nvidia-opencl-dev.
-- Andreas Beckmann a...@debian.org Sat, 17 Aug 2013 14:41:44 +0200
nvidia-cuda-toolkit (5.0.35-7) unstable; urgency=low
* nvidia-opencl-dev: Provides/Conflicts/Replaces: opencl-dev.
* nvidia-opencl-dev: Set Multi-Arch: same.
- Ship libOpenCL.so symlink previously in nvidia-libopencl1.
(Closes: #719833)
- Tighten the dependency on nvidia-libopencl1.
* nvidia-cuda-toolkit: Allow opencl-dev as an alternative to
nvidia-opencl-dev. (Closes: #719834)
-- Andreas Beckmann a...@debian.org Sat, 17 Aug 2013 06:48:53 +0200
diff -Nru ocl-icd-2.1.3/debian/control ocl-icd-2.1.3/debian/control
--- ocl-icd-2.1.3/debian/control 2014-02-07 00:33:38.0 +0200
+++ ocl-icd-2.1.3/debian/control 2014-07-29 16:33:49.0 +0200
@@ -18,8 +18,8 @@
Provides: libopencl1, libopencl-1.1-1, libopencl-1.2-1
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
-Conflicts: libopencl1, amd-app, nvidia-libopencl1-dev
-Replaces: libopencl1, amd-app, nvidia-libopencl1-dev
+Conflicts: libopencl1, amd-app, nvidia-opencl-dev
+Replaces: libopencl1, amd-app, nvidia-opencl-dev
# To promote to an Recommends once an ICD is in main
Suggests: opencl-icd
Description: Generic OpenCL ICD Loader
Bug#740565: redeclipse-data: should be in main
On 29.07.2014 08:04, Vincent Cheng wrote: On Sun, Jul 27, 2014 at 6:30 AM, Markus Koschany a...@gambaru.de wrote: [...] Great, thanks for the patches! I'm sure you've realized by now that the fastest way to get stuff done in Debian is to do it yourself. ;) This and that taking the initiative and doing the work gets punished. [...] Imagine the gnome-shell maintainers decided to put their package into non-free because they felt it is safer. It would make all dependencies suddenly uninstallable. You simply can't make arbitrary decisions about the archive sections. Just because Red Eclipse is just a game makes the issue not smaller or less important. Yes, the gnome-shell maintainers can decide to put their packages into non-free if they so wish; doing so is not a Policy violation, even if it sounds ridiculous. And yes, it would make their dependencies uninstallable, which would indeed lead to RC bugs being filed against it and/or its dependencies (and would likely be followed by some heated flamewars on certain mailing lists). It's completely hypothetical, but the gnome-shell maintainers can move their package to non-free at any time, and only the CTTE can override them. What's your point here since you agree that moving the package to non-free would ultimately lead to RC bugs being filed? There is no documented Policy about the term safer but the Policy is very precise about Debian's archive areas. [1] If your package is compliant with the DFSG it must be in main because this area comprises the Debian distribution. Otherwise other software, like my games-fps metapackage from the Debian Games Pure Blend, is not allowed to depend or recommend Red Eclipse. Since Red Eclipse is DFSG-free it is a Policy violation. Thus the severity must be serious. No, Policy §2.2 explicitly states that non DFSG compliant packages must go in non-free, but nothing about DFSG compliant packages being forced to be distributed in main. I have heard the Debian Project is an association of individuals who have made common cause to create a free operating system and not a system of free software that they maintain in a repository called non-free and which is not part of the official Debian distribution. It is common sense that a DFSG compliant package must go in main because it does not fit the description of the non-free and contrib repositories. This is a very simple deduction and makes perfectly sense if you know that only [main] is considered part of the distribution. 2.2.1 only says that Every package in main must comply with the DFSG (Debian Free Software Guidelines), i.e. package in main - DFSG-compliant, _not_ the reverse. Policy doesn't forbid placing DFSG packages in contrib or non-free, as silly as it may sound, so this simply isn't a RC bug. Yes, it sounds silly and I disagree with your assumption. Even if this was true it would certainly violate the core and the spirit of the Policy. Just to be clear, I don't object to placing DFSG-free packages in main; what I'm arguing against is inflating bug severity to accomplish your own personal release goals when the bug doesn't violate Policy. It may be important to you, but if it doesn't meet the definition of a RC bug, it's not a RC bug, and it's definitely not a release blocker. Now, just imagine if every maintainer and user decided to inflate the priority of their own pet bugs... By now you should know my work and being aware that I have fixed quite a lot of RC bugs in this team. I have never inflated the severity of bugs and I don't create new ones purely on a whim when I am not convinced that this is the right thing to do. Having Red Eclipse in non-free again for Jessie makes the package unfit to release in my opinion thus I have raised the severity. In other words it is time to act. I am not thrilled to continue this discussion since we both agree that #740565 is a bug and we have a patch already. I would like doing real work again instead of arguing why free software should be in main. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#755993: marked as done (node-express-generator: uninstallable because of version number)
Your message dated Tue, 29 Jul 2014 16:34:11 + with message-id e1xcalr-0002lo...@franck.debian.org and subject line Bug#755993: fixed in node-express-generator 4.0.0-2 has caused the Debian Bug report #755993, regarding node-express-generator: uninstallable because of version number 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.) -- 755993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: node-express-generator Version: 4.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, There's only one version ofthis package, and it depends on an inexistant version of another package, node-express (it breaks 4.1.1-1 and the only version available is 4.1.1~dfsg-1). I was unable to install it, apparently it's just a minor problem with version numbers. Thanks, Xav -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Source: node-express-generator Source-Version: 4.0.0-2 We believe that the bug you reported is fixed in the latest version of node-express-generator, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Leo Iannacone l...@ubuntu.com (supplier of updated node-express-generator 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, 29 Jul 2014 18:21:04 +0200 Source: node-express-generator Binary: node-express-generator Architecture: source all Version: 4.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Leo Iannacone l...@ubuntu.com Description: node-express-generator - express applications generator Closes: 755993 Changes: node-express-generator (4.0.0-2) unstable; urgency=medium . * Relax node-express conflict version (Closes: #755993) Checksums-Sha1: b0d22e0421b850e04b7895f41479e17d55b813bb 2085 node-express-generator_4.0.0-2.dsc d9dc38fc4a81f40b18c936d9e7b3cc80e53c9624 5379 node-express-generator_4.0.0.orig.tar.gz 8ba6e8c862587aa99a241240dc51e4f095b3fd6c 2824 node-express-generator_4.0.0-2.debian.tar.gz a15b39be550d2d83e1df48445ad90320bf67ff95 7406 node-express-generator_4.0.0-2_all.deb Checksums-Sha256: b741364617f032b9f26743d876ff76c38d1538525bdb4f866b0050bb17060fa3 2085 node-express-generator_4.0.0-2.dsc 92564cd0e9089d14dcdea1c7db0beaa7e6d51a0fd20f6e889b4abc4a041f2955 5379 node-express-generator_4.0.0.orig.tar.gz 9f0f19fc5b51cf82bfdfcd7ab947694de5333dc6ab1263fac33f03e4ffbbcfdd 2824 node-express-generator_4.0.0-2.debian.tar.gz 0056ebabf6f7f4ef2f9a579ab8de0049d1072df2d053b53767606e8086a550af 7406 node-express-generator_4.0.0-2_all.deb Files: da6150ca0d0ef1237eed67a02842763c 7406 web extra node-express-generator_4.0.0-2_all.deb a7420f09d58dcde055ff9ccfc82af99c 2085 web extra node-express-generator_4.0.0-2.dsc d3c26d7b30d6878372fb69135fd782d7 5379 web extra node-express-generator_4.0.0.orig.tar.gz 788d255e9925806dfe3d020c3da8a20c 2824 web extra node-express-generator_4.0.0-2.debian.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT18tFAAoJEDMrlP7SgvwlLUQP/A0b7D9QffM5BRaQiGS4x1gU Emwd3Yli2pDutxVE0Ccn4lEFH73QXvFPqMdsAl7WFSqQ0xzDqcAbHMpb+5T63Zup AbqzVJgedfQszlhVLObh13kxN3wxAbkROITnEb/DBpRJHnDS8BN/MXYlWcHbq9Yp 2B64mXu8/w2zT2OJg356IOJUTEQkJGfgejr+lU3PF4/gdGOgD3TmXs1M5FBbiF9q sLGBUHpu53N/jHmiDR6oRJyFAN+fCOZYuMkJd1TqQXBchf9z7M3V8+ghqNpYZZ44 ZQfZLPXTJxiRcjYOLb/B5zDOkhhCprpcVk9V4M83mo/RjVArsRfB6Y5HnaXq27i0 A8N4Pit8esQbgxlN6sV+vvtMq5iIaUb4APg2zSBDMZeIepoRY67e8MxCq8lZLLno CvEqcLfF7JT6RpD+XjZ3UzBPuqX5OLGi/nIoUw6wVmt0+inibMlgv4eYJTZYuLbU R+bvpVQh5K1NFIcBgAeOFArStpzp/xfNao9a+Oj1s/6+t96GgELbI03KNjXUoSTC ++tnsfaFvsQIg0X6Pmcyz/+xTv9djzEihJIuh89CgfAVuMI/MLWgtf9XT92FrVBy 3ebQuSrIuXiv0AUXvn2zRfgR6n3k4mG6lJEvUAQx+UImQhjlWXNICWtunvz10Hs2
Bug#753057: marked as done (libinline-java-perl: broken symlinks when built under perl 5.20)
Your message dated Tue, 29 Jul 2014 16:49:00 + with message-id e1xcaac-0004lv...@franck.debian.org and subject line Bug#753057: fixed in libinline-java-perl 0.53-3 has caused the Debian Bug report #753057, regarding libinline-java-perl: broken symlinks when built under perl 5.20 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.) -- 753057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libxml-saxon-xslt2-perl Version: 0.007-3 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.20-transition This package fails to build from source with Perl 5.20 (currently in experimental): ResultL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -MTest::Harness -e undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', 'blib/arch') t/01basic.t Note: Transformer.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. Error: Could not find or load main class org.perl.inline.java.InlineJavaServer JVM taking more than 15 seconds to start, or died before Perl could connect. Increase config STARTUP_DELAY if necessary. at /usr/lib/x86_64-linux-gnu/perl5/5.20/Inline/Java.pm line 484. INIT failed--call queue aborted. # Looks like your test exited with 4 before it could output anything. Failed 1/1 test programs. 0/0 subtests failed. t/01basic.t .. 1..4 Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/4 subtests Test Summary Report --- t/01basic.t (Wstat: 1024 Tests: 0 Failed: 0) Non-zero exit status: 4 Parse errors: Bad plan. You planned 4 tests but ran 0. Files=1, Tests=0, 16 wallclock secs ( 0.07 usr 0.01 sys + 2.08 cusr 0.11 csys = 2.27 CPU) Result: FAIL It looks like libinline-java-perl might be at fault, but its test suite does pass with 5.20. -- Niko Tyni nt...@debian.org ---End Message--- ---BeginMessage--- Source: libinline-java-perl Source-Version: 0.53-3 We believe that the bug you reported is fixed in the latest version of libinline-java-perl, 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 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated libinline-java-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Jul 2014 18:40:14 +0200 Source: libinline-java-perl Binary: libinline-java-perl Architecture: source amd64 Version: 0.53-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libinline-java-perl - write Perl classes in Java Closes: 753057 Changes: libinline-java-perl (0.53-3) unstable; urgency=medium . * Team upload. * Fix broken symlinks when built under Perl 5.20. Since the vendorarch path differs, we can't use a fixed length for relative links. (Closes: #753057) Checksums-Sha1: a8c848f2634e91988a1c618aea3a20a09ed7a222 2231 libinline-java-perl_0.53-3.dsc c509b41831fcf280569662e0acddf627c0c48842 3864 libinline-java-perl_0.53-3.debian.tar.xz 4e025fba1265ccda742e3bd6800e3d3648eca52e 141544 libinline-java-perl_0.53-3_amd64.deb Checksums-Sha256: 0c5a7635793aea95edb772742b890218a535e18d9dc209a701f2b87f537a45a4 2231 libinline-java-perl_0.53-3.dsc 9f17917c3628a2b8d8fe119d304c736d441c79dcf43977a1d3686d9727d625e1 3864 libinline-java-perl_0.53-3.debian.tar.xz a6133e1282d3c498f8f50a2249dca9cff3507dc4973a4d2ccb133a4779a97135 141544 libinline-java-perl_0.53-3_amd64.deb Files: 726f3b2947ccc71d4d2de5306295bab9 141544 perl optional libinline-java-perl_0.53-3_amd64.deb d069ae1528be0bb0b039bc7640fa2b1b 2231 perl optional libinline-java-perl_0.53-3.dsc 4d7c1b491ce5bae15433c6f705cea7bb 3864 perl optional libinline-java-perl_0.53-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJT186cXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
Bug#753038: marked as done (libplack-test-anyevent-perl: FTBFS with Perl 5.20: alternative dependencies)
Your message dated Tue, 29 Jul 2014 19:13:09 +0200 with message-id 20140729171309.ga19...@jadzia.comodo.priv.at and subject line Re: Bug#753038: libplack-test-anyevent-perl: FTBFS with Perl 5.20: alternative dependencies has caused the Debian Bug report #753038, regarding libplack-test-anyevent-perl: FTBFS with Perl 5.20: alternative dependencies 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.) -- 753038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libplack-test-anyevent-perl Version: 0.05-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.20-transition This package fails to build from source with Perl 5.20 (currently in experimental) and sbuild: The following packages have unmet dependencies: sbuild-build-depends-libplack-test-anyevent-perl-dummy : Depends: perl ( 5.19) but 5.20.0-1 is to be installed E: Unable to correct problems, you have held broken packages. For some related discussion, see #752989 :) -- Niko Tyni nt...@debian.org ---End Message--- ---BeginMessage--- Version: 0.05-2 On Sat, 28 Jun 2014 20:21:20 +0300, Niko Tyni wrote: Package: libplack-test-anyevent-perl Version: 0.05-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.20-transition This package fails to build from source with Perl 5.20 (currently in experimental) and sbuild: The following packages have unmet dependencies: sbuild-build-depends-libplack-test-anyevent-perl-dummy : Depends: perl ( 5.19) but 5.20.0-1 is to be installed E: Unable to correct problems, you have held broken packages. Already fixed in 0.05-2, closing now. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Jimi Hendrix: Freedom signature.asc Description: Digital Signature ---End Message---
Bug#752989: marked as done (libio-callback-perl: FTBFS with Perl 5.20: alternative dependencies)
Your message dated Tue, 29 Jul 2014 19:18:15 +0200 with message-id 20140729171815.ga23...@jadzia.comodo.priv.at and subject line Re: Bug#752989: libio-callback-perl: FTBFS with Perl 5.20: alternative dependencies has caused the Debian Bug report #752989, regarding libio-callback-perl: FTBFS with Perl 5.20: alternative dependencies 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.) -- 752989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libio-callback-perl Version: 1.12-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.20-transition This package fails to build from source with Perl 5.20 (currently in experimental) and sbuild: The following packages have unmet dependencies: sbuild-build-depends-libio-callback-perl-dummy : Depends: perl ( 5.19) but 5.20.0-1 is to be installed E: Unable to correct problems, you have held broken packages. The problem is this dependency: Build-Depends: perl ( 5.19) | libmodule-build-perl (= 0.40), Perhaps something like this (untested) could work? Build-Depends: perl (= 5.17.1~) | libmodule-build-perl (= 0.40), libmodule-build-perl (The unversioned dependency would guarantee either a perl version with the bundled M::B, or a separate package. The versioned alternative would guarantee that the M::B version is new enough.) I suppose we'll have to teach lintian new tricks too at some point... -- Niko Tyni nt...@debian.org ---End Message--- ---BeginMessage--- Version: 1.12-2 On Sat, 28 Jun 2014 10:03:08 +0300, Niko Tyni wrote: Package: libio-callback-perl Version: 1.12-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.20-transition This package fails to build from source with Perl 5.20 (currently in experimental) and sbuild: The following packages have unmet dependencies: sbuild-build-depends-libio-callback-perl-dummy : Depends: perl ( 5.19) but 5.20.0-1 is to be installed E: Unable to correct problems, you have held broken packages. The problem is this dependency: Build-Depends: perl ( 5.19) | libmodule-build-perl (= 0.40), This bug is already fixed in 1.12-2; the whole discussion afterwards is about the question if the fix is the best possible :) (Closing the bug since the package builds and won't get in the way of the transition; future changes are always possible). Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Beatles signature.asc Description: Digital Signature ---End Message---
Bug#756389: libndp: CVE-2014-3554: buffer overflow
Hi, An updated package has been prepared. Just waiting for my sponsor to upload. Regards, Andrew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752470: marked as done (ekg2: hardcodes /usr/lib/perl5)
Your message dated Tue, 29 Jul 2014 17:48:39 +
with message-id e1xcbvv-0002i5...@franck.debian.org
and subject line Bug#752470: fixed in ekg2 1:0.4~pre+20120506.1-6
has caused the Debian Bug report #752470,
regarding ekg2: hardcodes /usr/lib/perl5
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.)
--
752470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: ekg2
Version: 1:0.4~pre+20120506.1-4
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition
Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the vendorarch library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.
For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.
This package fails to build with perl_5.20.0-1 from experimental:
dh_install -a -O--parallel
cp: cannot stat 'debian/tmp/usr/lib/perl5': No such file or directory
dh_install: cp -a debian/tmp/usr/lib/perl5
debian/ekg2-scripting-perl//usr/lib/ returned exit code 1
make: *** [binary-arch] Error 2
debian/rules:13: recipe for target 'binary-arch' failed
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit
status 2
One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.
Please ask on the debian-perl list if you want help with this, and see
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
--
Niko Tyni nt...@debian.org
---End Message---
---BeginMessage---
Source: ekg2
Source-Version: 1:0.4~pre+20120506.1-6
We believe that the bug you reported is fixed in the latest version of
ekg2, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated ekg2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Jul 2014 19:23:21 +0200
Source: ekg2
Binary: ekg2-core ekg2 ekg2-api-docs ekg2-dbg ekg2-gnupg ekg2-jabber
ekg2-scripting-python ekg2-scripting-perl ekg2-ui-gtk ekg2-ui-ncurses
Architecture: source amd64 all
Version: 1:0.4~pre+20120506.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
ekg2 - instant messenger and IRC client for UNIX systems
ekg2-api-docs - instant messenger and IRC client for UNIX systems - API
documenta
ekg2-core - instant messenger and IRC client for UNIX systems - main program
ekg2-dbg - instant messenger and IRC client for UNIX systems - debugging sym
ekg2-gnupg - instant messenger and IRC client for UNIX systems - GnuPG
ekg2-jabber - instant messenger and IRC client for UNIX systems - Jabber/XMPP
ekg2-scripting-perl - instant messenger and IRC client for UNIX systems - Perl
scriptin
ekg2-scripting-python - instant messenger and IRC client for UNIX systems -
Python script
ekg2-ui-gtk - instant messenger and IRC client for UNIX systems - GTK+ interfac
ekg2-ui-ncurses - instant messenger and IRC client for UNIX systems - ncurses
inter
Closes: 752470
Changes:
ekg2 (1:0.4~pre+20120506.1-6) unstable; urgency=medium
.
* QA upload.
* Fix hardcodes /usr/lib/perl5:
use a debian/ekg2-scripting-perl.install.in in file where a variable gets
replaced from debian/rules at build time with the value of
$Config{vendorarch}
(Closes: #752470)
Checksums-Sha1:
996d4040626ea87132bcbb6c1d4db3a4a233fc3e 2882 ekg2_0.4~pre+20120506.1-6.dsc
af56f8ace8690b4d4e1ddc7e3b7325d06832950d 20108
ekg2_0.4~pre+20120506.1-6.debian.tar.xz
56cc24836e9b857d1eb7563d978029ae55a53948 454312
ekg2-core_0.4~pre+20120506.1-6_amd64.deb
Bug#756422: collectd: needs new upload for protobuf-c transition
Package: collectd Severity: serious Version: 5.4.1-3 Hi, Per #755212, the protobuf-c package is transitioning to a new major version. This update requires the .pb-c.c / .pb-c.h files generated by the protobuf-c compiler to be re-generated using the new version. collectd ships .pb-c.h files generated by the protobuf-c-compiler in the collectd-dev package. Since this is an Architecture: all package, it can't be updated by a binNMU (AFAIK), so in order to accomplish the protobuf-c transition collectd needs to be re-built against the newer protobuf-c-compiler package and uploaded to the archive, hence the severity of this bug report. Note that ideally .pb-c.c / .pb-c.h files should be generated from the original source .proto files as needed, in order to avoid version skew between different versions of the protobuf-c header and the protobuf-c compiler. It may be possible to avoid shipping .pb-c.h files in /usr/include entirely and instead ship the original .proto files (e.g., in /usr/share?) if nothing actually depends on these header files. Also, collectd build-depends on libprotobuf-c0-dev. The -dev package has been renamed to libprotobuf-c-dev in protobuf-c 1.0.0-1, but for the time being the old package named is still provided. I would recommend changing your build-dependency from libprotobuf-c0-dev to libprotobuf-c-dev in the next upload as well. (Or libprotobuf-c-dev | libprotobuf-c0-dev if you want to preserve the ability to build the source package on wheezy.) Thanks! -- Robert Edmonds edmo...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 755212 with 756422
Processing commands for cont...@bugs.debian.org: block 755212 with 756422 Bug #755212 [release.debian.org] transition: protobuf-c 755212 was blocked by: 73 755548 755212 was not blocking any bugs. Added blocking bug(s) of 755212: 756422 thanks Stopping processing here. Please contact me if you need assistance. -- 755212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755212 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#750564: marked as done (missing license in debian/copyright)
Your message dated Tue, 29 Jul 2014 18:03:46 +
with message-id e1xcbky-00058u...@franck.debian.org
and subject line Bug#750564: fixed in obexftp 0.23-3
has caused the Debian Bug report #750564,
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.)
--
750564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: obexftp
Version: 0.23-2
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:
obexftp/*
bfb/*
to debian/copyright.
Thanks!
Thorsten
---End Message---
---BeginMessage---
Source: obexftp
Source-Version: 0.23-3
We believe that the bug you reported is fixed in the latest version of
obexftp, 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 750...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated obexftp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Jul 2014 19:51:27 +0200
Source: obexftp
Binary: obexftp libbfb0 libbfb0-dev libmulticobex1 libmulticobex1-dev
libobexftp0 libobexftp0-dev python-obexftp ruby-obexftp libobexftp-ruby
libobexftp-perl
Architecture: source amd64 all
Version: 0.23-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
libbfb0- bfb protocol library
libbfb0-dev - bfb protocol library - development files
libmulticobex1 - multi-protocol cable OBEX library
libmulticobex1-dev - multi-protocol cable OBEX library - development files
libobexftp-perl - perl binding to the object exchange file transfer library
libobexftp-ruby - Transitional package for ruby-obexftp
libobexftp0 - object exchange file transfer library
libobexftp0-dev - object exchange file transfer library - development files
obexftp- file transfer utility for devices that use the OBEX protocol
python-obexftp - Python binding to the object exchange file transfer library
ruby-obexftp - ruby binding to the object exchange file transfer library
Closes: 750564 752799
Changes:
obexftp (0.23-3) unstable; urgency=medium
.
* QA upload.
* Fix hardcodes /usr/lib/perl5:
dynamically set perl library path in debian/rules from $Config{vendorarch}
(Closes: #752799)
* Add missing license to debian/copyright.
(Closes: #750564)
Checksums-Sha1:
8de0836ddc9af88b363c561b4035b119f6de7ab1 2511 obexftp_0.23-3.dsc
1b98da97a92f34023bbb38ba54d22888779587d2 9244 obexftp_0.23-3.diff.gz
9e42a662579e56b5588106ae6c846505dcc51b2b 28068 obexftp_0.23-3_amd64.deb
75ce83d7f02fde680f5ed8facae2dc837fd7376b 17350 libbfb0_0.23-3_amd64.deb
882b46ba5a09c460afc00e0b4b65d7b263e51047 17810 libbfb0-dev_0.23-3_amd64.deb
3b127defa6a8624cc2e68c5c14f416e0316cfb13 14114 libmulticobex1_0.23-3_amd64.deb
3dbe835c7d513db13a7572b8246e18713adfa57f 13476
libmulticobex1-dev_0.23-3_amd64.deb
1739c143e9096962c42d9906bc3f7b8f6c3ee509 23546 libobexftp0_0.23-3_amd64.deb
11b65bfc76a5c7ba047416bc42d5e76de175aaed 68698 libobexftp0-dev_0.23-3_amd64.deb
a9839a116a0a1f802aa075d00f400f10841ccc6b 24636 python-obexftp_0.23-3_amd64.deb
24c2da1e677d97937f016e117244869e761d7ef7 20402 ruby-obexftp_0.23-3_amd64.deb
dd7f027fb8ec75dbf0826bee1dd554a41adf518c 10908 libobexftp-ruby_0.23-3_all.deb
1bd9c65c4f31b0285c67f7b94b227cf39b5f4586 24032 libobexftp-perl_0.23-3_amd64.deb
Checksums-Sha256:
5643d51ac40615e126b99f68593ac9bd54d8a4c69d371cabdcb0eb9a32107a93 2511
obexftp_0.23-3.dsc
b9a8aaa7c31d660f64a7b953551f5b17c567ff085f16eb649bb1127d768351c2 9244
obexftp_0.23-3.diff.gz
c03ceebc639c902636d42f0561b72150f0da8cf97f5fe83d704341449d7ba7c9 28068
obexftp_0.23-3_amd64.deb
a763651bd80b4a91ca4a3c3adc1c425a17984462bb5503173005dede01368bdc 17350
libbfb0_0.23-3_amd64.deb
816901ae588719c592c079cac00d27d89fd0f4961348941c0f2700b2c5b4d124 17810
libbfb0-dev_0.23-3_amd64.deb
74b33bb86ae1ddf68bc7f2f1d97c88c3fb960a3c848833356b956ef86c5898a1 14114
Bug#752799: marked as done (obexftp: hardcodes /usr/lib/perl5)
Your message dated Tue, 29 Jul 2014 18:03:46 +
with message-id e1xcbky-00058a...@franck.debian.org
and subject line Bug#752799: fixed in obexftp 0.23-3
has caused the Debian Bug report #752799,
regarding obexftp: hardcodes /usr/lib/perl5
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.)
--
752799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: obexftp
Version: 0.23-2
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition
Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the vendorarch library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.
For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.
This package fails to build with perl_5.20.0-1 from experimental:
dh_install --sourcedir=debian/tmp --autodest --fail-missing -X.la
dh_install: libobexftp-perl missing files (usr/lib/perl5/*), aborting
make: *** [binary-arch] Error 2
One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.
Please ask on the debian-perl list if you want help with this, and see
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
--
Niko Tyni nt...@debian.org
---End Message---
---BeginMessage---
Source: obexftp
Source-Version: 0.23-3
We believe that the bug you reported is fixed in the latest version of
obexftp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated obexftp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Jul 2014 19:51:27 +0200
Source: obexftp
Binary: obexftp libbfb0 libbfb0-dev libmulticobex1 libmulticobex1-dev
libobexftp0 libobexftp0-dev python-obexftp ruby-obexftp libobexftp-ruby
libobexftp-perl
Architecture: source amd64 all
Version: 0.23-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
libbfb0- bfb protocol library
libbfb0-dev - bfb protocol library - development files
libmulticobex1 - multi-protocol cable OBEX library
libmulticobex1-dev - multi-protocol cable OBEX library - development files
libobexftp-perl - perl binding to the object exchange file transfer library
libobexftp-ruby - Transitional package for ruby-obexftp
libobexftp0 - object exchange file transfer library
libobexftp0-dev - object exchange file transfer library - development files
obexftp- file transfer utility for devices that use the OBEX protocol
python-obexftp - Python binding to the object exchange file transfer library
ruby-obexftp - ruby binding to the object exchange file transfer library
Closes: 750564 752799
Changes:
obexftp (0.23-3) unstable; urgency=medium
.
* QA upload.
* Fix hardcodes /usr/lib/perl5:
dynamically set perl library path in debian/rules from $Config{vendorarch}
(Closes: #752799)
* Add missing license to debian/copyright.
(Closes: #750564)
Checksums-Sha1:
8de0836ddc9af88b363c561b4035b119f6de7ab1 2511 obexftp_0.23-3.dsc
1b98da97a92f34023bbb38ba54d22888779587d2 9244 obexftp_0.23-3.diff.gz
9e42a662579e56b5588106ae6c846505dcc51b2b 28068 obexftp_0.23-3_amd64.deb
75ce83d7f02fde680f5ed8facae2dc837fd7376b 17350 libbfb0_0.23-3_amd64.deb
882b46ba5a09c460afc00e0b4b65d7b263e51047 17810 libbfb0-dev_0.23-3_amd64.deb
3b127defa6a8624cc2e68c5c14f416e0316cfb13 14114 libmulticobex1_0.23-3_amd64.deb
3dbe835c7d513db13a7572b8246e18713adfa57f 13476
libmulticobex1-dev_0.23-3_amd64.deb
1739c143e9096962c42d9906bc3f7b8f6c3ee509 23546 libobexftp0_0.23-3_amd64.deb
Bug#756429: traceevent plugins installed in wrong directory
Package: linux-tools-3.14 Version: 3.14-1 Severity: serious Since version 3.14, perf builds and installs some plugins in /usr/lib/traceevent/plugins (or, on amd64, /usr/lib64/...). This will prevent coinstallation of linux-tools-version for multiple kernel versions. Also, Debian policy does not allow use of /lib64 and /usr/lib64. Ben. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-tools-3.14 depends on: ii libaudit1 1:2.3.7-1 ii libc6 2.19-7 ii libdw10.159-4 ii libelf1 0.159-4 ii libnuma1 2.0.9-1 ii libperl5.18 5.18.2-7 ii libpython2.7 2.7.8-3 ii libslang2 2.2.4-17 ii libunwind81.1-3 ii perl 5.18.2-7 pn python:anynone Versions of packages linux-tools-3.14 recommends: ii linux-base 3.6 Versions of packages linux-tools-3.14 suggests: pn linux-doc-3.14 none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754940: marked as done (mariadb-server-5.5: Multiple security issues from recent CPU)
Your message dated Tue, 29 Jul 2014 21:30:20 +0200 with message-id 20140729193020.GA20401@eldamar.local and subject line closing bug, CVEs fixed in 5.5.38 upstream has caused the Debian Bug report #754940, regarding mariadb-server-5.5: Multiple security issues from recent CPU 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.) -- 754940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mariadb-server-5.5 Severity: grave Tags: security Justification: user security hole These should affect MariaDB at least partly: http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html Cheers, Moritz ---End Message--- ---BeginMessage--- Source: mariadb-5.5 Source-Version: 5.5.38-1 CVEs fixed in MariaDB 5.5.38 upstream.---End Message---
Processed: Re: Bug#756325: CVE-2014-5044: gfortran integer overflows
Processing control commands: tags -1 moreinfo Bug #756325 [src:gcc-4.4, src:gcc-4.6, src:gcc-4.7, src:gcc-4.8, src:gcc-4.9] CVE-2014-5044: gfortran integer overflows Added tag(s) moreinfo. severity -1 wishlist Bug #756325 [src:gcc-4.4, src:gcc-4.6, src:gcc-4.7, src:gcc-4.8, src:gcc-4.9] CVE-2014-5044: gfortran integer overflows Severity set to 'wishlist' from 'serious' -- 756325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756325 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#756325: CVE-2014-5044: gfortran integer overflows
Control: tags -1 moreinfo Control: severity -1 wishlist Am 28.07.2014 um 22:10 schrieb Michael Gilbert:python-pyasn1-modules_0.0.5-0ubuntu3_source.changes package: src:gcc-4.4, src:gcc-4.6, src:gcc-4.7, src:gcc-4.8, src:gcc-4.9 severity: serious tags: security Several integer overflow issues affecting all gcc versions have been fixed in libgfortran: http://www.openwall.com/lists/oss-security/2014/07/23/7 Best wishes, maybe better wishful thinking? you should better stop filing security issues, and better spend your time replying to the ones where more information is needed. Florian Weimer is still listed as a member of the security team, although he doesn't seem to do *anything* for Debian currently (apparently employed by Red Hat). So please catch up within the debian-security team first where you have the better expertise, and pretty please don't bother anyone else before addressing this within the security team. thanks, and best wishes, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741785: (no subject)
I saw the same problem on ppc64el: http://ftp.unicamp.br/pub/ppc64el/debian/buildd-upstream/build_logs/logs/seed_3.8.1-1_ppc64el.build -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737921: [TLS1.2] gnutls only likes SHA1 and SHA256 certificates
I’ve built the patched gnutls26 (now as of 2.12.20-8+deb7u2)
package with pbuilder and briefly tested Exim (as of 4.80-7)
with the resulting libgnutls26, and seen no issues so far.
The resulting packages, both source (signed) and binary (along
with signed .changes files) are available from the following
location. (Should you decide to use these, /please take care/
to check .dsc and .changes signatures against my public key, and
binary packages against the .changes files.)
⋯✂⋯ /etc/apt/sources.list.d/99-am-1.org-1gray-test.list ⋯✂⋯
deb http://am-1.org/~ivan/mini-dinstall/ 1gray-test/$(ARCH)/
deb http://am-1.org/~ivan/mini-dinstall/ 1gray-test/all/
deb-src http://am-1.org/~ivan/mini-dinstall/ 1gray-test/source/
⋯✂⋯ /etc/apt/sources.list.d/99-am-1.org-1gray-test.list ⋯✂⋯
For the sake of completeness, the changes are also MIMEd.
--
FSF associate member #7257 http://boycottsystemd.org/
Public key fingerprint: 58F8 0F47 53F5 2EB2 F6A5 8916 3013 B6A0 230E 334A
diff -dru -- a/debian/changelog b/debian/changelog
--- a/debian/changelog 2014-05-31 14:28:44.0 +
+++ b/debian/changelog 2014-07-29 18:48:51.0 +
@@ -1,3 +1,13 @@
+gnutls26 (2.12.20-8+deb7u2.0+is.2) 1gray-misc; urgency=medium
+
+ * 12_no_sign_algo.diff: adapted from 1a02ec18e9e3 by Nikos
+Mavrogiannopoulos. Closes: #737921, #740160
+ * 42_no-more-gets.diff: do not assume that gets () is declared
+by the libc; adapted from
+https://lists.gnu.org/archive/html/bug-gnulib/2012-03/msg00186.html
+
+ -- Ivan Shmakov i...@siamics.net Tue, 29 Jul 2014 18:48:51 +
+
gnutls26 (2.12.20-8+deb7u2) wheezy-security; urgency=high
* 39_Prevent-memory-corruption.diff from upstream GIT. Fix memory corruption
Only in b/debian/patches: 12_no_sign_algo.diff
Only in b/debian/patches: 42_no-more-gets.diff
diff -dru -- a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series 2014-05-31 14:27:28.0 +
+++ b/debian/patches/series 2014-07-29 18:57:21.0 +
@@ -1,3 +1,4 @@
+12_no_sign_algo.diff
14_version_gettextcat.diff
16_unnecessarydep.diff
17_ignoretestsuitteerrors.diff
@@ -13,3 +14,4 @@
37_fix_rejection-of-v1-intermedi.diff
38_CVE-2014-0092.diff
39_Prevent-memory-corruption.diff
+42_no-more-gets.diff
This is an adaptation of the change made in 1a02ec18e9e3 and
subsequently amended (with regards to GNUTLS_CRT_OPENPGP.)
commit 6e4e6b0aa30acc8db68fcc19a9406abcfe44ae9c
Author: Nikos Mavrogiannopoulos n...@gnutls.org
Date: Thu Apr 21 00:21:56 2011 +0200
commit 1a02ec18e9e39f82cee7f9cff74e1f1574bac472
Author: Nikos Mavrogiannopoulos n...@gnutls.org
Date: Wed Apr 20 19:45:20 2011 +0200
Eliminated the need for sign_algo in gnutls_pcert_st. This means
that we don't follow RFC5246 by letter, but there wasn't any other
implementation using the sign_algorithm part of the certificate
selection, and this helps reduce complexity.
diff --git a/lib/auth/cert.c b/lib/auth/cert.c
index 275e9bf..39cf8ed 100644
--- a/lib/auth_cert.c
+++ b/lib/auth_cert.c
@@ -,29 +,18 @@ _gnutls_proc_x509_server_certificate (gnutls_session_t session,
if ((ret =
_gnutls_x509_raw_cert_to_gcert (peer_certificate_list
[j], tmp,
CERT_ONLY_EXTENSIONS)) 0)
{
gnutls_assert ();
goto cleanup;
}
- /* check if signature algorithm is supported */
- ret =
-_gnutls_session_sign_algo_enabled (session,
- peer_certificate_list
- [j].sign_algo);
- if (ret 0)
-{
- gnutls_assert ();
- goto cleanup;
-}
-
p += len;
}
if ((ret =
_gnutls_copy_certificate_auth_info (info,
peer_certificate_list,
peer_certificate_list_size)) 0)
{
@@ -2092,26 +2081,18 @@ _gnutls_server_select_cert (gnutls_session_t session,
*/
if (requested_algo == GNUTLS_PK_ANY ||
requested_algo == cred-cert_list[i][0].subject_pk_algorithm)
{
/* if cert type and signature algorithm matches
*/
/* *INDENT-OFF* */
if (session-security_parameters.cert_type
- == cred-cert_list[i][0].cert_type
- (cred-cert_list[i][0].cert_type == GNUTLS_CRT_OPENPGP
- || /* FIXME: make this a check for certificate
- type capabilities */
- !_gnutls_version_has_selectable_sighash
- (gnutls_protocol_get_version (session))
- ||
- _gnutls_session_sign_algo_requested
- (session, cred-cert_list[i][0].sign_algo) == 0))
+ == cred-cert_list[i][0].cert_type)
{
idx = i;
break;
}
/* *INDENT-ON* */
}
}
/* store the certificate pointer for
Bug#754788: marked as done (lavapdu-daemon: fails to install)
Your message dated Tue, 29 Jul 2014 21:21:45 + with message-id e1xceq9-0003sh...@franck.debian.org and subject line Bug#754788: fixed in lavapdu 0.0.3-2 has caused the Debian Bug report #754788, regarding lavapdu-daemon: fails to install 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.) -- 754788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lavapdu-daemon Version: 0.0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): The following NEW packages will be installed: lavapdu-daemon 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 13.7 kB of archives. After this operation, 115 kB of additional disk space will be used. Get:1 http://mirror.bm.debian.org/debian/ jessie/main lavapdu-daemon all 0.0.3-1 [13.7 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 13.7 kB in 0s (901 kB/s) Selecting previously unselected package lavapdu-daemon. (Reading database ... 7954 files and directories currently installed.) Preparing to unpack .../lavapdu-daemon_0.0.3-1_all.deb ... Unpacking lavapdu-daemon (0.0.3-1) ... Setting up lavapdu-daemon (0.0.3-1) ... invoke-rc.d: policy-rc.d denied execution of start. invoke-rc.d: policy-rc.d denied execution of start. No passwd entry for user 'postgres' No passwd entry for user 'postgres' /var/lib/dpkg/info/lavapdu-daemon.postinst: 18: /var/lib/dpkg/info/lavapdu- daemon.postinst: Failed to create database user: not found dpkg: error processing package lavapdu-daemon (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: lavapdu-daemon E: Sub-process /usr/bin/dpkg returned an error code (1) If needed, I could teach piuparts.d.o to start a postgresql server (for this package), but even without it must not fail like this. So I won't do this, before this bug isn't fixed ;) cheers, Holger Start: 2014-07-07 17:59:20 UTC Package: lavapdu-daemon Source: lavapdu Version: 0.0.3-1 Installed-Size: 112 Maintainer: Debian LAVA team pkg-linaro-lava-de...@lists.alioth.debian.org Architecture: all Replaces: lavapdu Depends: python (= 2.7), python ( 2.8), python-daemon, python-lockfile, python-pexpect, python-psycopg2, postgresql-client-common Conflicts: lavapdu Description: LAVA PDU control daemon Homepage: http://www.linaro.org/projects/test-validation/ Description-md5: c875df0cc051c098b99b9f7199f02b77 Section: net Priority: optional Filename: pool/main/l/lavapdu/lavapdu-daemon_0.0.3-1_all.deb Size: 13688 MD5sum: 757595682d4e8b364294f83fc663bbe7 SHA1: 1569f282de69b5aec84fcf38abd5b89388631dba SHA256: 4a421c7311695d72468a2611b56487bea150d68f635c3b3e91f5428042f8bbca Executing: sudo env PYTHONPATH=/srv/piuparts.debian.org/lib/python2.7/dist-packages timeout -s INT -k 5m 35m /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt lavapdu-daemon=0.0.3-1 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts is wrong. 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.59~201405301115~0.58-62-g352dac2 starting up. 0m0.0s INFO: Command line arguments: /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt lavapdu-daemon=0.0.3-1 0m0.0s INFO: Running on: Linux piu-slave-bm-a 3.2.0-4-amd64 #1 SMP
Bug#732424: NMU for gstreamer0.10, FTBFS due to changes in bison3
Control: tags -1 + pending Hi, I am preparing a NMU to fix the bugs above (see headers), with the fix proposed by Tobias Hansen picking a patch from upstream, and with immediate upload as per guidelines in [1] as soon as I get it to work -- since they are FTBFS and severity serious, open for many months and didn't receive any update from the maintainers. There is gstreamer1.0 since a few months ago in unstable, and perhaps is the one intended that packages use from now on, but many packages still build-depend on this one. Apart from the obvious problem of FTBFS for the architectures in which it was built in the past, this is a problem for ports being added recently (OpenRISC/or1k, ppc64el, ...) since they don't even have older versions to rely on, and many packages depend on them, so it's blocking a good portion of the archive to compile cleanly. [1] http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: NMU for gstreamer0.10, FTBFS due to changes in bison3
Processing control commands: tags -1 + pending Bug #732424 [gstreamer0.10] gstreamer0.10: deprecated option YYLEX_PARAM has been removed from bison leading to FTBFS Added tag(s) pending. -- 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
Processed: NMU for gstreamer0.10, FTBFS due to changes in bison3
Processing control commands: tags -1 + pending Bug #733362 [src:gstreamer0.10] gstreamer0.10: FTBFS: grammar.tab.c:1819:7: error: too few arguments to function 'priv_gst_parse_yylex' Added tag(s) pending. -- 733362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733362 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: tagging 732213
Processing commands for cont...@bugs.debian.org: tags 732213 + upstream Bug #732213 [kdepim-runtime] [kdepim-runtime] Kolab agent looses information about birthdays Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 732213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732213 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#756445: liblog4ada2-dev not installable in sid
Package: liblog4ada2-dev Version: 1.2-4 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable, liblog4ada2-dev is not installable in sid, on any architecture, since it depends both on gnat and gnat-4.6. Package gnat depends on gnat-4.9. which is in conflict with gnat-4.6. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754830: Second part of bug not fixed
Hi. The original reporter of this bug mentioned two issues, the invalid option passed to rfcomm issue, and the mising dev parameter message from rfcomm. The first issue has been fixed with the new release, but not the second. I'm experiencing the same bug with this new version, and because of it my bluetooth devices are not working. The issue seems to be that rfcomm can't see the bluetooth device, since rfcomm show all doesn't show anything (hcitool and hciconfig can see the device just fine). Since it was already mentioned in this bug I'm not sure if it's appropiate to continue here or if I should file a new bug about it. Either way I don't think bluez 5.x should go into testing before it's resovled. The bug is definetly in the bluez package, it'll start or stop working if I upgrade/downgrade between the version in sid and the verison in testing with no other change on my system. Please let me know about any info you need about my system to narrow down what the problem could be, and if I should file a new bug or continue here. Thanks, Andreas Eriksson
Bug#678054: iulib: FTBFS[kfreebsd]: fatal error: asm/types.h: No such file or directory
Hello, please consider uploading iulib/0.4.4+ds-2 to sid when it fixes the FTBFS. Currently, libiulib0 is not installable in sid on any architecture since it depends on libsdl-gfx1.2-4 (= 2.0.22); so a rebuild is needed. -Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 753890 is grave
Processing commands for cont...@bugs.debian.org: severity 753890 grave Bug #753890 [photofilmstrip] Depends: mencoder which is a virtual package. Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 753890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753890 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: macchanger: diff for NMU version 1.7.0-1.1
Processing commands for cont...@bugs.debian.org: tags 738460 + pending Bug #738460 [macchanger] macchanger: Randomization fails for final three octets Bug #740947 [macchanger] macchanger: Random mac feature fails in all of the random mac assigning options Added tag(s) pending. Added tag(s) pending. tags 740947 + pending Bug #740947 [macchanger] macchanger: Random mac feature fails in all of the random mac assigning options Bug #738460 [macchanger] macchanger: Randomization fails for final three octets Ignoring request to alter tags of bug #740947 to the same tags previously set Ignoring request to alter tags of bug #738460 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 738460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738460 740947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740947 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#738460: macchanger: diff for NMU version 1.7.0-1.1
tags 738460 + pending
tags 740947 + pending
thanks
Dear maintainer,
I've prepared an NMU for macchanger (versioned as 1.7.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
This is Theodore Ts'o's diff, with minor corrections to the changelog entry.
Regards,
Tim Retout
diff -Nru macchanger-1.7.0/debian/changelog macchanger-1.7.0/debian/changelog
--- macchanger-1.7.0/debian/changelog 2014-02-01 17:20:44.0 +
+++ macchanger-1.7.0/debian/changelog 2014-07-29 22:49:57.0 +0100
@@ -1,3 +1,13 @@
+macchanger (1.7.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix a grave security bug -- the macchanger program was fundamentally
+not working correctly due to a bug in the debian local patch
+08-fix_random_MAC_choice.patch. In fact, it was **breaking** the
+random MAC choice!?! (Closes: #738460, #740947)
+
+ -- Theodore Y. Ts'o ty...@mit.edu Sun, 06 Jul 2014 20:32:38 -0400
+
macchanger (1.7.0-1) unstable; urgency=medium
* New upstream release (Closes: #718849)
diff -Nru macchanger-1.7.0/debian/patches/08-fix_random_MAC_choice.patch
macchanger-1.7.0/debian/patches/08-fix_random_MAC_choice.patch
--- macchanger-1.7.0/debian/patches/08-fix_random_MAC_choice.patch
2014-02-01 17:20:44.0 +
+++ macchanger-1.7.0/debian/patches/08-fix_random_MAC_choice.patch
2014-07-29 22:49:36.0 +0100
@@ -12,6 +12,8 @@
src/main.c |1 +
2 files changed, 34 insertions(+), 19 deletions(-)
+Index: macchanger/src/mac.c
+===
--- macchanger.orig/src/mac.c
+++ macchanger/src/mac.c
@@ -41,6 +41,13 @@ mc_mac_dup (const mac_t *mac)
@@ -28,7 +30,7 @@
void
mc_mac_free (mac_t *mac)
-@@ -68,27 +75,34 @@ mc_mac_random (mac_t *mac, unsigned char
+@@ -68,27 +75,32 @@ mc_mac_random (mac_t *mac, unsigned char
* x1:, x3:, x5:, x7:, x9:, xB:, xD: and xF:
*/
@@ -36,9 +38,25 @@
- case 6:
- /* 8th bit: Unicast / Multicast address
- * 7th bit: BIA (burned-in-address) / locally-administered
-+ mac_t newmac;
-+ mc_mac_copy(mac, newmac);
-+
+- */
+- mac-byte[0] = (random()%255) 0xFC;
+- mac-byte[1] = random()%255;
+- mac-byte[2] = random()%255;
+- case 3:
+- mac-byte[3] = random()%255;
+- mac-byte[4] = random()%255;
+- mac-byte[5] = random()%255;
+- }
++ mac_t origmac;
++ mc_mac_copy(mac, origmac);
+
+- /* Handle the burned-in-address bit
+- */
+- if (set_bia) {
+- mac-byte[0] = ~2;
+- } else {
+- mac-byte[0] |= 2;
+- }
+ do {
+ switch (last_n_bytes) {
+ case 6:
@@ -55,33 +73,18 @@
+ }
+
+ /* Handle the burned-in-address bit
-*/
-- mac-byte[0] = (random()%255) 0xFC;
-- mac-byte[1] = random()%255;
-- mac-byte[2] = random()%255;
-- case 3:
-- mac-byte[3] = random()%255;
-- mac-byte[4] = random()%255;
-- mac-byte[5] = random()%255;
-- }
++ */
+ if (set_bia) {
+ mac-byte[0] = ~2;
+ } else {
+ mac-byte[0] |= 2;
+ }
-+ } while (mc_mac_equal (newmac, mac));
-
-- /* Handle the burned-in-address bit
-- */
-- if (set_bia) {
-- mac-byte[0] = ~2;
-- } else {
-- mac-byte[0] |= 2;
-- }
-+ mc_mac_copy(newmac, mac);
++ } while (mc_mac_equal (origmac, mac));
}
+Index: macchanger/src/main.c
+===
--- macchanger.orig/src/main.c
+++ macchanger/src/main.c
@@ -274,6 +274,7 @@ main (int argc, char *argv[])
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756450: ecryptfs-utils: home dir still readable by sudo after user logs out
Package: ecryptfs-utils Version: 99-1 Severity: grave Tags: security Justification: user security hole Hi! The bug is probably the same as reporte on OpenSUSE-bugs: http://lists.opensuse.org/archive/opensuse-bugs/2014-02/msg02515.html User A is sudo user User B is a normal user A is logged in. B want to user the PC in a secure and confidential manner, A lends the PC to B. B logs in, do stuff recorded in encrypted home, logs out, give back the PC to A thinking all his activity in home dir is encrypted and safe. But the home directory of the normal system user B that has just logged out is still readable by the sudo user A, who can read everything including still valid session cookies etc. Hence encrypts is a bit useless for shared computers. Thank you. jer...@jerome.cc -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ecryptfs-utils depends on: ii gettext-base0.18.1.1-9 ii keyutils1.5.5-3 ii libc6 2.13-38+deb7u3 ii libecryptfs099-1 ii libgpg-error0 1.10-3.1 ii libgpgme11 1.2.0-1.4 ii libkeyutils11.5.5-3 ii libnss3-1d 2:3.14.5-1 ii libpam-runtime 1.1.3-7.1 ii libpam0g1.1.3-7.1 ii libtspi10.3.9-3+wheezy1 ecryptfs-utils recommends no packages. Versions of packages ecryptfs-utils suggests: ii cryptsetup 2:1.4.3-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754830: Info received (Second part of bug not fixed)
Hi again. It seems that rfcomm bind all isn't a thing that works in bluez 5.x, by design, so I think that the bug here as far as debian is concerned is that the init script tries to run rfcomm at all. You now have to run rfcomm dev mac adress for each connection individually, the command doesn't accept 'all'. The reason my device doesn't work with 5.x seems more likely to be because it uses bluez-alsa and the bluez-alsa version in sid is still 4.x and not 5.x.
Bug#733362: marked as done (gstreamer0.10: FTBFS: grammar.tab.c:1819:7: error: too few arguments to function 'priv_gst_parse_yylex')
Your message dated Tue, 29 Jul 2014 22:18:59 + with message-id e1xcfjx-0003h4...@franck.debian.org and subject line Bug#733362: fixed in gstreamer0.10 0.10.36-1.3 has caused the Debian Bug report #733362, regarding gstreamer0.10: FTBFS: grammar.tab.c:1819:7: error: too few arguments to function 'priv_gst_parse_yylex' 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.) -- 733362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gstreamer0.10 Version: 0.10.36-1.2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /bin/bash ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../.. -I../.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wformat-nonliteral -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Waggregate-return -Wno-multichar -Wnested-externs -g-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wno-error -c -o libgstparse_la-grammar.tab.lo `test -f 'grammar.tab.c' || echo './'`grammar.tab.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -D_FORTIFY_SOURCE=2 -I../.. -I../.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wformat-nonliteral -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Waggregate-return -Wno-multichar -Wnested-externs -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wno-error -c grammar.tab.c -fPIC -DPIC -o .libs/libgstparse_la-grammar.tab.o grammar.tab.c: In function 'priv_gst_parse_yyparse': grammar.tab.c:1819:7: error: too few arguments to function 'priv_gst_parse_yylex' if (yychar == YYEMPTY) ^ ./grammar.y:39:5: note: declared here int priv_gst_parse_yylex (void * yylval_param , yyscan_t yyscanner); ^ make[5]: *** [libgstparse_la-grammar.tab.lo] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/gstreamer0.10_0.10.36-1.2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: gstreamer0.10 Source-Version: 0.10.36-1.3 We believe that the bug you reported is fixed in the latest version of gstreamer0.10, 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. Manuel A. Fernandez Montecelo m...@debian.org (supplier of updated gstreamer0.10 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Jul 2014 21:33:03 +0100 Source: gstreamer0.10 Binary: libgstreamer0.10-0 libgstreamer0.10-0-dbg libgstreamer0.10-dev gstreamer0.10-doc gstreamer0.10-tools gstreamer-tools gir1.2-gstreamer-0.10 Architecture: source all amd64 Version: 0.10.36-1.3 Distribution: unstable Urgency: medium Maintainer: Maintainers of GStreamer packages pkg-gstreamer-maintain...@lists.alioth.debian.org Changed-By: Manuel A. Fernandez Montecelo m...@debian.org Description: gir1.2-gstreamer-0.10 - Description: GObject introspection data for the GStreamer library gstreamer-tools - Tools for use with GStreamer
Bug#732424: marked as done (gstreamer0.10: deprecated option YYLEX_PARAM has been removed from bison leading to FTBFS)
Your message dated Tue, 29 Jul 2014 22:18:59 +
with message-id e1xcfjx-0003gy...@franck.debian.org
and subject line Bug#732424: fixed in gstreamer0.10 0.10.36-1.3
has caused the Debian Bug report #732424,
regarding gstreamer0.10: deprecated option YYLEX_PARAM has been removed from
bison leading to FTBFS
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.)
--
732424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gstreamer0.10
Version: 0.10.36-1.2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
While rebuilding Trusty with a recent version of bison it was noted that
the YYLEX_PARAM has finally been removed. This patch updates gstreamer
to use the replacement %lex-param:
* 99_YYLEX_PARAM-deprecated.patch: follow deprecation of YYLEX_PARAM
in favour of %lex-param. Fixes FTBFS following bison update.
Thanks for considering the patch.
-apw
-- System Information:
Debian Release: wheezy/sid
APT prefers trusty-updates
APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500,
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12.0-7-generic (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
diff -Nru gstreamer0.10-0.10.36/debian/patches/99_YYLEX_PARAM-deprecated.patch gstreamer0.10-0.10.36/debian/patches/99_YYLEX_PARAM-deprecated.patch
--- gstreamer0.10-0.10.36/debian/patches/99_YYLEX_PARAM-deprecated.patch 1970-01-01 01:00:00.0 +0100
+++ gstreamer0.10-0.10.36/debian/patches/99_YYLEX_PARAM-deprecated.patch 2013-12-17 19:15:21.0 +
@@ -0,0 +1,21 @@
+Description: switch to %lex-param
+ Follow deprecation of YYLEX_PARAM, switching to equivalent %lex-param.
+Author: Andy Whitcroft a...@canonical.com
+Last-Update: 2013-12-17
+
+--- gstreamer0.10-0.10.36.orig/gst/parse/grammar.y
gstreamer0.10-0.10.36/gst/parse/grammar.y
+@@ -1,3 +1,5 @@
++%lex-param {yyscan_t scanner}
++
+ %{
+ #include ../gst_private.h
+
+@@ -26,7 +28,6 @@
+ */
+
+ #define YYERROR_VERBOSE 1
+-#define YYLEX_PARAM scanner
+
+ #define YYENABLE_NLS 0
+
diff -Nru gstreamer0.10-0.10.36/debian/patches/series gstreamer0.10-0.10.36/debian/patches/series
--- gstreamer0.10-0.10.36/debian/patches/series 2013-12-12 07:36:19.0 +
+++ gstreamer0.10-0.10.36/debian/patches/series 2013-12-17 19:14:11.0 +
@@ -3,3 +3,4 @@
99_ltmain_as-needed.patch
01_fix_webcam_stream_play_hang.patch
99_update-libtool.patch
+99_YYLEX_PARAM-deprecated.patch
---End Message---
---BeginMessage---
Source: gstreamer0.10
Source-Version: 0.10.36-1.3
We believe that the bug you reported is fixed in the latest version of
gstreamer0.10, 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 732...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Manuel A. Fernandez Montecelo m...@debian.org (supplier of updated
gstreamer0.10 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Jul 2014 21:33:03 +0100
Source: gstreamer0.10
Binary: libgstreamer0.10-0 libgstreamer0.10-0-dbg libgstreamer0.10-dev
gstreamer0.10-doc gstreamer0.10-tools gstreamer-tools gir1.2-gstreamer-0.10
Architecture: source all amd64
Version: 0.10.36-1.3
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of GStreamer packages
pkg-gstreamer-maintain...@lists.alioth.debian.org
Changed-By: Manuel A. Fernandez Montecelo m...@debian.org
Description:
gir1.2-gstreamer-0.10 - Description: GObject introspection data for the
GStreamer library
gstreamer-tools - Tools for use with GStreamer
gstreamer0.10-doc - GStreamer core documentation and manuals
gstreamer0.10-tools - Tools for use with GStreamer
libgstreamer0.10-0 - Core GStreamer libraries and elements
libgstreamer0.10-0-dbg - Core GStreamer libraries and elements
libgstreamer0.10-dev - GStreamer core development files
Closes: 732424 733362
Bug#755346: parser: FTBFS: string3.h:51: undefined reference to `_pcre_default_tables'
Source: parser Version: 3.4.3-3 Followup-For: Bug #755346 These missing references are also a problem at runtime: $ apache2ctl configtest apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/parser3.load: Cannot load /usr/lib/apache2/modules/mod_parser3.so into server: /usr/lib/apache2/modules/mod_parser3.so: undefined symbol: _pcre_default_tables Action 'configtest' failed. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756389: marked as done (libndp: CVE-2014-3554: buffer overflow)
Your message dated Wed, 30 Jul 2014 01:03:34 + with message-id e1xciio-0003t8...@franck.debian.org and subject line Bug#756389: fixed in libndp 1.4-1 has caused the Debian Bug report #756389, regarding libndp: CVE-2014-3554: buffer overflow 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.) -- 756389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libndp Version: 1.3-1 Severity: grave Tags: security upstream patch Hi, the following vulnerability was published for libndp. CVE-2014-3554[0]: buffer overflow If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-3554 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1118583 Regards, Salvatore ---End Message--- ---BeginMessage--- Source: libndp Source-Version: 1.4-1 We believe that the bug you reported is fixed in the latest version of libndp, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Ayer a...@andrewayer.name (supplier of updated libndp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Jul 2014 06:34:39 -0700 Source: libndp Binary: libndp-dbg libndp-dev libndp-tools libndp0 Architecture: source amd64 Version: 1.4-1 Distribution: unstable Urgency: high Maintainer: Andrew Ayer a...@andrewayer.name Changed-By: Andrew Ayer a...@andrewayer.name Description: libndp-dbg - Library for Neighbor Discovery Protocol (debug symbols) libndp-dev - Library for Neighbor Discovery Protocol (development files) libndp-tools - Library for Neighbor Discovery Protocol (tools) libndp0- Library for Neighbor Discovery Protocol Closes: 754917 756389 Changes: libndp (1.4-1) unstable; urgency=high . * Fix grammatical/syntactic errors in extended description. Thanks to Filipus Klutiero (Closes: #754917) * Set single-debian-patch and add a patch header. * New upstream release. Fixes CVE-2014-3554. (Closes: #756389) Checksums-Sha1: 22ca9e28541c141abc6a496b93bcb217369b25d8 1972 libndp_1.4-1.dsc 1325e9458a8f801ba35783e1fc334fd26dc8de39 337802 libndp_1.4.orig.tar.gz f3c6af53586aa3df6cadc65317064ee0904fddbb 3080 libndp_1.4-1.debian.tar.xz 31e208c2a78ab488590ed8ab0088660ec2f8e591 36350 libndp-dbg_1.4-1_amd64.deb d5208c075abf39c69568b3273e4de9f2a4bc7979 11200 libndp-dev_1.4-1_amd64.deb f8bedae34ff3bc2cf105674e13e32eb506d0b5cf 9478 libndp-tools_1.4-1_amd64.deb a64cfef3bdd078292b537b906212e748f85ed19c 10314 libndp0_1.4-1_amd64.deb Checksums-Sha256: 5cc58efcb90a03c4d462c9dba0fd102ed7c59b919de8b963ef0c6dc669c60d3d 1972 libndp_1.4-1.dsc 3a0be247ec024bd72fe5b40ea9491519c4023c7faf078311196fab817b2fd55f 337802 libndp_1.4.orig.tar.gz 95bd5885ee3218796647142be17784f5740f6314d89bf049b096d83777a44caf 3080 libndp_1.4-1.debian.tar.xz 70eac452075a0ed6eb59e059aa971c5a69f1267ba17b46fca571856fa81541c8 36350 libndp-dbg_1.4-1_amd64.deb 47d0c588d2f01cfea189041cbcb2496fb67066fe0fbc8782663f14ee747a13b4 11200 libndp-dev_1.4-1_amd64.deb 4586e6df031708467cc649d312a5379f0bfc6077da3e33ae917f7306a7118407 9478 libndp-tools_1.4-1_amd64.deb ce7a4728e00d3728a7b14758373ebcca46a1ad18c3919482a94943bc7b14a5a2 10314 libndp0_1.4-1_amd64.deb Files: feb44b89ee54c79c4ff051f291831e03 36350 debug extra libndp-dbg_1.4-1_amd64.deb 43b59998a753999ca3bfcaeb692b108e 11200 libdevel optional libndp-dev_1.4-1_amd64.deb 13c446452b10cab7e3e09190b5f5e9e1 9478 net optional libndp-tools_1.4-1_amd64.deb 26ff46c33ce8b0226ecf76293b153790 10314 libs optional libndp0_1.4-1_amd64.deb 8cd3c8da947ffa35fabfbe796ab35bc0 1972 net optional libndp_1.4-1.dsc 52c708d4b8729ae6e3781b3737a85e16 337802 net optional libndp_1.4.orig.tar.gz 12b8a5fc72003f00778ea0665c1a4867 3080 net optional libndp_1.4-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT2EGeAAoJEGrh3w1gjyLcP9kP/iFWodFj0oks7+yQ0uZY/8hb WHjC72anuN15OKW10fHHemADlvsCAqqjpvJuR7b5/zR0fFJVCwXpbMFSv9tkrFjX
Bug#756460: ruby-activerecord-3.2: Uninstallable in sid
Package: ruby-activerecord-3.2 Version: 3.2.19-1 Severity: grave In a pbuilder chroot: root@frobozz:~# apt-get install ruby-activerecord-3.2 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ruby-activerecord-3.2 : Depends: ruby-arel (= 3.0.2~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@frobozz:~# apt-get install ruby-activerecord-3.2 ruby-arel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ruby-arel : Breaks: ruby-activerecord-3.2 but 3.2.19-1 is to be installed E: Unable to correct problems, you have held broken packages. This is making e.g. ruby-stringex unbuildable. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756464: upgrade-reports: [kfreebsd] dist-upgrade to jessie removes the kernel
Package: upgrade-reports Severity: critical Justification: breaks the whole system Dear Maintainer, When dist-upgrading a system to jessie, or running dist-upgrade on a freshly installed system (using the alpha 1 release of the installer), apt-get removes the kernel. This results in there being no kernel installed, and you can't exactly boot the system without a kernel, hence the severity. Using aptitude reveals that freebsd-net-tools Breaks: kfreebsd-image-9 To reproduce: Install Debian GNU/kFreeBSD jessie from tha alpha 1 netinstall cd. Run apt-get dist-upgrade Reboot and you will be stuck with a grub prompt. In case it matters, this bug was found running under a virtual machine (KVM). -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.2-1-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756465: maxima: Segmentation fault during startup
Package: maxima Version: 5.33.0-13 Severity: grave Justification: renders package unusable Dear Maintainer, when satrting up maxima I get a Segmentation fault straight away: cut -- jomo@mars [/home/jomo] maxima Unrecoverable error: Segmentation violation.. Segmentation fault jomo@mars [/home/jomo] cut -- gdb isn't showing useful information either as far as I can see: cut -- jomo@mars [/home/jomo] libdir=/usr/lib jomo@mars [/home/jomo] layout_autotools=true jomo@mars [/home/jomo] MAXIMA_DEFAULT_IMAGESDIR=/usr/lib/maxima/5.33.0 jomo@mars [/home/jomo] MAXIMA_IMAGESDIR=/usr/lib/maxima/5.33.0 jomo@mars [/home/jomo] MAXIMA_DEFAULT_LISP=gcl jomo@mars [/home/jomo] MAXIMA_LISP=gcl jomo@mars [/home/jomo] maxima_image_base=/usr/lib/maxima/5.33.0/binary-gcl/maxima jomo@mars [/home/jomo] gdb /usr/lib/maxima/5.33.0/binary-gcl/maxima GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/lib/maxima/5.33.0/binary-gcl/maxima...(no debugging symbols found)...done. (gdb) r Starting program: /usr/lib/maxima/5.33.0/binary-gcl/maxima warning: Could not load shared library symbols for linux-gate.so.1. Do you need set solib-search-path or set sysroot? Program received signal SIGSEGV, Segmentation fault. 0x000c367f in ?? () (gdb) where #0 0x000c367f in ?? () #1 0x000c8d22 in ?? () #2 0x000d6984 in ?? () #3 0x00020cc6 in ?? () #4 0x4b22aa63 in __libc_start_main (main=0x20c90, argc=1, argv=0xb4a4, init=0x31a0f0, fini=0x31a160, rtld_fini=0x4b1fcc90 _dl_fini, stack_end=0xb49c) at libc-start.c:287 #5 0x00021b4c in ?? () (gdb) cut -- And finally some valgrind output: cut -- jomo@mars [/home/jomo] valgrind /usr/lib/maxima/5.33.0/binary-gcl/maxima ==12381== Memcheck, a memory error detector ==12381== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==12381== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info ==12381== Command: /usr/lib/maxima/5.33.0/binary-gcl/maxima ==12381== --12381-- WARNING: Serious error when reading debug info --12381-- When reading debug info from /usr/lib/maxima/5.33.0/binary-gcl/maxima: --12381-- Can't make sense of .data section mapping ==12381== Syscall param rt_sigaction(act-sa_mask) points to uninitialised byte(s) ==12381==at 0x4B23F746: __libc_sigaction (sigaction.c:74) ==12381==by 0xC361B: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0xC8D21: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0x4B22AA62: (below main) (libc-start.c:287) ==12381== Address 0xbec2bf40 is on thread 1's stack ==12381== ==12381== Syscall param rt_sigaction(act-sa_mask) points to uninitialised byte(s) ==12381==at 0x4B23F746: __libc_sigaction (sigaction.c:74) ==12381==by 0xC3638: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0xC8D21: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0x4B22AA62: (below main) (libc-start.c:287) ==12381== Address 0xbec2bf40 is on thread 1's stack ==12381== ==12381== Invalid read of size 4 ==12381==at 0x4B274A4D: fflush (iofflush.c:40) ==12381==by 0xC8AC6: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381== Address 0x403e0aa0 is not stack'd, malloc'd or (recently) free'd ==12381== ==12381== Can't extend stack to 0x658790 during signal delivery for thread 1: ==12381== no stack segment ==12381== ==12381== Process terminating with default action of signal 11 (SIGSEGV) ==12381== Access not within mapped region at address 0x658790 ==12381==at 0x4B274A4D: fflush (iofflush.c:40) ==12381==by 0xC8AC6: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) cut -- Kind regards, Joerg. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (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/bash Versions of packages maxima depends on: ii libc6 2.19-7 ii libgmp10 2:6.0.0+dfsg-4 ii libreadline6 6.3-6 ii libx11-6 2:1.6.2-2 Versions of packages maxima recommends: ii gnuplot-x11 4.6.5-9 ii maxima-share 5.33.0-13 Versions of packages maxima suggests: ii maxima-doc
Processed: Re: tiptop: FTBFS on MIPS
Processing control commands: severity -1 serious Bug #756406 [tiptop] tiptop: FTBFS on MIPS Severity set to 'serious' from 'normal' -- 756406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756406 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
