Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)
reassign 677582 gcc-4.7-base 4.7.2-2
reopen 677582
thanks
On 2012-09-21 14:22, Andreas Beckmann wrote:
[...]
I'm now trying to add these Breaks to gcc-4.7-base, that can't be held
back, hopefully.
Attached is a diff that finally fixes this upgrade issue, hopefully.
gcc-4.7-base isn't that optional as gcc-4.4-base, so it can't be held
back, actually enforcing the Breaks vs. ancient gcj. I looked a bit into
the history where these Breaks originated, and since gcc-4.7-base Breaks
old versions of gcc-4.6-base, I think it would be the right thing to do
and add the Breaks vs. 4.4, too.
* gcc-4.7-base: ensure smooth upgrades from squeeze by adding
Breaks: gcj-4.4-base ( 4.4.6-9~), gnat-4.4-base ( 4.4.6-3~)
as in gcc-4.4-base (multiarch patches re-worked in 4.6.1-8/4.4.6-9).
Fixes some squeeze-wheezy upgrade paths where apt chooses to hold back
gcc-4.4-base and keep gcj-4.4-base installed instead of upgrading
gcc-4.4-base and removing the obsolete gcj-4.4-base (Andreas Beckmann).
(Closes: #677582)
The recent changes on gcc-4.4 that attempted to fix this issue by
upgrading Breaks to Conflicts could be reverted, but they can be left as
is as they won't do harm (should just add a lintian warning for a
versioned Conflicts).
I tested this patch with piuparts upgrade tests (squeeze-sid) on a
selection of the affected java packages (there are about 60-70 in total,
checked around 10 from different sources), and all passed once I added
an extra repository with the updated gcc-4.7 packages.
Andreas
diff -u gcc-4.7-4.7.2/debian/changelog gcc-4.7-4.7.2/debian/changelog
--- gcc-4.7-4.7.2/debian/changelog
+++ gcc-4.7-4.7.2/debian/changelog
@@ -1,3 +1,16 @@
+gcc-4.7 (4.7.2-2.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * gcc-4.7-base: ensure smooth upgrades from squeeze by adding
+ Breaks: gcj-4.4-base ( 4.4.6-9~), gnat-4.4-base ( 4.4.6-3~)
+as in gcc-4.4-base (multiarch patches re-worked in 4.6.1-8/4.4.6-9).
+Fixes some squeeze-wheezy upgrade paths where apt chooses to hold back
+gcc-4.4-base and keep gcj-4.4-base installed instead of upgrading
+gcc-4.4-base and removing the obsolete gcj-4.4-base (Andreas Beckmann).
+(Closes: #677582)
+
+ -- Andreas Beckmann deb...@abeckmann.de Sat, 22 Sep 2012 01:31:33 +0200
+
gcc-4.7 (4.7.2-2) unstable; urgency=low
* Fix PR tree-optimization/54563 (), PR target/54564 (fma builtin fix),
diff -u gcc-4.7-4.7.2/debian/control gcc-4.7-4.7.2/debian/control
--- gcc-4.7-4.7.2/debian/control
+++ gcc-4.7-4.7.2/debian/control
@@ -18,7 +18,7 @@
Priority: required
Depends: ${misc:Depends}
Replaces: ${base:Replaces}
-Breaks: gcj-4.6-base ( 4.6.1-4~), gnat-4.6 ( 4.6.1-5~), dehydra (=
0.9.hg20110609-2)
+Breaks: gcj-4.4-base ( 4.4.6-9~), gnat-4.4-base ( 4.4.6-3~), gcj-4.6-base
( 4.6.1-4~), gnat-4.6 ( 4.6.1-5~), dehydra (= 0.9.hg20110609-2)
Description: GCC, the GNU Compiler Collection (base package)
This package contains files common to all languages and libraries
contained in the GNU Compiler Collection (GCC).
diff -u gcc-4.7-4.7.2/debian/control.m4 gcc-4.7-4.7.2/debian/control.m4
--- gcc-4.7-4.7.2/debian/control.m4
+++ gcc-4.7-4.7.2/debian/control.m4
@@ -105,7 +105,7 @@
Priority: PRI(required)
Depends: ${misc:Depends}
Replaces: ${base:Replaces}
-Breaks: gcj-4.6-base ( 4.6.1-4~), gnat-4.6 ( 4.6.1-5~), dehydra (=
0.9.hg20110609-2)
+Breaks: gcj-4.4-base ( 4.4.6-9~), gnat-4.4-base ( 4.4.6-3~), gcj-4.6-base
( 4.6.1-4~), gnat-4.6 ( 4.6.1-5~), dehydra (= 0.9.hg20110609-2)
Description: GCC, the GNU Compiler Collection (base package)
This package contains files common to all languages and libraries
contained in the GNU Compiler Collection (GCC).
Bug#687869: libgsm0710: diff for NMU version 1.2.2-1.1
Control: tags 687869 + patch Control: tags 687886 + patch Hi The attached patch should fix this issue. I'm only attaching the patch but have not done any further action. Sebastian do you have time to do the upload? Regards, Salvatore diff -Nru libgsm0710-1.2.2/debian/changelog libgsm0710-1.2.2/debian/changelog --- libgsm0710-1.2.2/debian/changelog 2012-05-25 20:26:48.0 +0200 +++ libgsm0710-1.2.2/debian/changelog 2012-09-22 09:14:01.0 +0200 @@ -1,3 +1,15 @@ +libgsm0710 (1.2.2-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Replace documentation directory with symlink. +Replace documentation directory for libgsm0710-dbg and libgsm0710-dev +with a symlink. When updating from Squeeze to Wheezy +/usr/share/doc/libgsm0710-dbg and /usr/share/doc/libgsm0710-dev resulted +in empty directories with no copyright file (which is violating Debian +policy 10.5). (Closes: #687869, #687886) + + -- Salvatore Bonaccorso car...@debian.org Sat, 22 Sep 2012 09:13:53 +0200 + libgsm0710 (1.2.2-1) unstable; urgency=low [ Simon Busch ] diff -Nru libgsm0710-1.2.2/debian/libgsm0710-dbg.postinst libgsm0710-1.2.2/debian/libgsm0710-dbg.postinst --- libgsm0710-1.2.2/debian/libgsm0710-dbg.postinst 1970-01-01 01:00:00.0 +0100 +++ libgsm0710-1.2.2/debian/libgsm0710-dbg.postinst 2012-09-22 09:14:01.0 +0200 @@ -0,0 +1,18 @@ +#!/bin/sh + +set -e + +# Replace documentation directory with symlink +docdir=/usr/share/doc/libgsm0710-dbg +if [ -d $docdir ] [ ! -L $docdir ]; then +if rmdir $docdir 2/dev/null; then +ln -sf libgsm0710-0 $docdir +fi +fi + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 diff -Nru libgsm0710-1.2.2/debian/libgsm0710-dev.postinst libgsm0710-1.2.2/debian/libgsm0710-dev.postinst --- libgsm0710-1.2.2/debian/libgsm0710-dev.postinst 1970-01-01 01:00:00.0 +0100 +++ libgsm0710-1.2.2/debian/libgsm0710-dev.postinst 2012-09-22 09:14:01.0 +0200 @@ -0,0 +1,18 @@ +#!/bin/sh + +set -e + +# Replace documentation directory with symlink +docdir=/usr/share/doc/libgsm0710-dev +if [ -d $docdir ] [ ! -L $docdir ]; then +if rmdir $docdir 2/dev/null; then +ln -sf libgsm0710-0 $docdir +fi +fi + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 signature.asc Description: Digital signature
Processed: libgsm0710: diff for NMU version 1.2.2-1.1
Processing control commands: tags 687869 + patch Bug #687869 [libgsm0710-dev] libgsm0710-dev: copyright file missing after upgrade (policy 12.5) Added tag(s) patch. tags 687886 + patch Bug #687886 [libgsm0710-dbg] libgsm0710-dbg: copyright file missing after upgrade (policy 12.5) Added tag(s) patch. -- 687869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687869 687886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687886 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: libgsm0710: diff for NMU version 1.2.2-1.1
Processing control commands: tags 687869 + patch Bug #687869 [libgsm0710-dev] libgsm0710-dev: copyright file missing after upgrade (policy 12.5) Ignoring request to alter tags of bug #687869 to the same tags previously set tags 687886 + patch Bug #687886 [libgsm0710-dbg] libgsm0710-dbg: copyright file missing after upgrade (policy 12.5) Ignoring request to alter tags of bug #687886 to the same tags previously set -- 687869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687869 687886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687886 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#668026: A bit more info
It seems that the build failure boils down to:
configure:22252: checking if dev/usb/usb.h uses new naming convention
configure:22277: i486-kfreebsd-gnu-g++ -c -g -O2 -D_FORTIFY_SOURCE=2
conftest.cpp 5
conftest.cpp: In function 'int main()':
conftest.cpp:43:46: error: invalid use of incomplete type 'struct
main()::usb_ctl_request'
conftest.cpp:43:25: error: forward declaration of 'struct
main()::usb_ctl_request'
configure:22283: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME libusb
| #define PACKAGE_TARNAME libusb
| #define PACKAGE_VERSION 0.1.12
| #define PACKAGE_STRING libusb 0.1.12
| #define PACKAGE_BUGREPORT
| #define PACKAGE libusb
| #define VERSION 0.1.12
| #define LIBUSB_MAJOR_VERSION 0
| #define LIBUSB_MINOR_VERSION 1
| #define LIBUSB_MICRO_VERSION 12
| #define LIBUSB_INTERFACE_AGE 4
| #define LIBUSB_BINARY_AGE 8
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| #define BSD_API 1
| #define LINUX_API 0
| #define DARWIN_API 0
| #define STDC_HEADERS 1
| #define HAVE_VPRINTF 1
| #define HAVE_LIMITS_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_VALUES_H 1
| #define HAVE_VALUES_H 1
| #define HAVE_MEMMOVE 1
| /* end confdefs.h. */
| #include dev/usb/usb.h
| int
| main ()
| {
|
|int a = ((struct usb_ctl_request *)0L)-ucr_addr
|
| ;
| return 0;
| }
configure:22294: result: no
While the successful 2011 build of libusb 2:0.1.12-20 says:
checking if dev/usb/usb.h uses new naming convention... yes
I've verified that changing
#ifdef HAVE_OLD_DEV_USB_USB_H
to
#if 0
in bsd.c makes the package build OK on kfreebsd.
I think this means that usb_ctl_request used to be declared in dev/usb/usb.h
with a ucr_addr member, but is now removed altogether, which configure.in
(incorrectly) interprets as having old naming convention.
Perhaps kfreebsd-kernel-headers maintainer(s) can provide some confirmation of
my theory and maybe an explanation on the reasons for removal.
--
Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/
GnuPG: 2048R/02F946FC 35E9 1344 9F77 5F43 13DD 6423 DBF4 80C6 02F9 46FC
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)
Processing commands for cont...@bugs.debian.org:
reassign 677582 gcc-4.7-base 4.7.2-2
Bug #677582 {Done: Matthias Klose d...@debian.org} [gcc-4.4-base]
gcc-4.4-base: upgrade problems since removal of gcj-4.4
Bug reassigned from package 'gcc-4.4-base' to 'gcc-4.7-base'.
No longer marked as found in versions gcc-4.4/4.4.7-1.
No longer marked as fixed in versions gcc-4.4/4.4.7-3.
Bug #677582 {Done: Matthias Klose d...@debian.org} [gcc-4.7-base]
gcc-4.4-base: upgrade problems since removal of gcj-4.4
Marked as found in versions gcc-4.7/4.7.2-2.
reopen 677582
Bug #677582 {Done: Matthias Klose d...@debian.org} [gcc-4.7-base]
gcc-4.4-base: upgrade problems since removal of gcj-4.4
Bug reopened
Ignoring request to alter fixed versions of bug #677582 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
677582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677582
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#688210: marked as done (condor: Multiple security issues)
Your message dated Sat, 22 Sep 2012 07:47:45 + with message-id e1tfkrf-0002zn...@franck.debian.org and subject line Bug#688210: fixed in condor 7.8.4~dfsg.1-1 has caused the Debian Bug report #688210, regarding condor: Multiple security issues 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.) -- 688210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: condor Severity: grave Tags: security Justification: user security hole Please see here for details: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3490 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3491 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3492 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3493 Cheers, Moritz ---End Message--- ---BeginMessage--- Source: condor Source-Version: 7.8.4~dfsg.1-1 We believe that the bug you reported is fixed in the latest version of condor, 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 688...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hanke m...@debian.org (supplier of updated condor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 21 Sep 2012 20:56:32 +0200 Source: condor Binary: condor condor-dev condor-doc condor-dbg libclassad-dev libclassad3 Architecture: source amd64 all Version: 7.8.4~dfsg.1-1 Distribution: experimental Urgency: low Maintainer: Condor Developers condor-deb...@cs.wisc.edu Changed-By: Michael Hanke m...@debian.org Description: condor - distributed workload management system condor-dbg - distributed workload management system - debugging symbols condor-dev - distributed workload management system - development files condor-doc - distributed workload management system - documentation libclassad-dev - Condor classads expression language - development library libclassad3 - Condor classads expression language - runtime library Closes: 685892 688210 Changes: condor (7.8.4~dfsg.1-1) experimental; urgency=low . * New upstream bug fix release (missed 7.8.3). This release addresses four security-related issues, as well as numerous other bug fixes (Closes: #688210): - Security Item: Some code that was no longer used was removed. The presence of this code could expose information which would allow an attacker to control another user's job. (CVE-2012-3493) - Security Item: Some code that was no longer used was removed. The presence of this code could have lead to a Denial-of-Service attack which would allow an attacker to remove another user's idle job. (CVE-2012-3491) - Security Item: Filesystem (FS) authentication was improved to check the UNIX permissions of the directory used for authentication. Without this, an attacker may have been able to impersonate another submitter on the same submit machine. (CVE-2012-3492) - Security Item: Although not user-visible, there were multiple updates to remove places in the code where potential buffer overruns could occur, thus removing potential attacks. None were known to be exploitable. - Security Item: Although not user-visible, there were updates to the code to improve error checking of system calls, removing some potential security threats. None were known to be exploitable. - The full changelog listing numerous additional bugs is available at http://research.cs.wisc.edu/condor/manual/v7.8/9_3Stable_Release.html * Added patch to fix a FTBFS on alpha, due to missing getpid syscall. Courtesy of Michael Cree mc...@orcon.net.nz (Closes: #685892). Checksums-Sha1: 1e0b1fb78f47dee8056df0255a83807912bdf10c 2632 condor_7.8.4~dfsg.1-1.dsc 5d49894b62a83ffbe5ea593c5e50752442a5ad96 8162567 condor_7.8.4~dfsg.1.orig.tar.gz fcce390f5c59c8b76f62d51ca4e6aa987932beb6 85853 condor_7.8.4~dfsg.1-1.debian.tar.gz d43a4db4f1435da459491996cddbb6a52dbc2eac 5039606 condor_7.8.4~dfsg.1-1_amd64.deb 50f59dd4da715dd2a505f62a8e5e7afd859fdc15 459560 condor-dev_7.8.4~dfsg.1-1_amd64.deb c9db312f5a72c57e1018d2a6aed237dea06e4d96
Bug#685360: [PATCH 1/1] HID: Fix missing Unifying device issue
On Fri, 21 Sep 2012, Nestor Lopez Casado wrote: This patch fixes an issue introduced after commit 4ea5454203d991ec After that commit, hid-core silently discards any incoming packet that arrives while any hid driver's probe function is being executed. This broke the enumeration process of hid-logitech-dj, that must receive control packets in-band with the mouse and keyboard packets. Discarding mouse or keyboard data at the very begining is usually fine, but it is not the case for control packets. This patch forces a re-enumeration of the paired devices when a packet arrives that comes from an unknown device. Based on a patch originally written by Benjamin Tissoires. Signed-off-by: Nestor Lopez Casado nlopezca...@logitech.com I am now applying it, will be pushing to Linus very soon, and am also marking it for stable 3.2+ Thanks to everyone involved. -- Jiri Kosina SUSE Labs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: block 688372 by 587749 Bug #688372 [wnpp] ITP: bzr-tweet -- Bazaar commit and push tweet plugin 688372 was not blocked by any bugs. 688372 was not blocking any bugs. Added blocking bug(s) of 688372: 613698, 609041, 617983, and 587749 -- Stopping processing here. Please contact me if you need assistance. -- 688372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688372 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#688374: gforge-shell-postgresql: postinst fails after cp: target `//etc/nss-pgsql-root.conf' is not a directory
Package: gforge-shell-postgresql Version: 5.2~rc1+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. The first problem was that the database was not reachable, but that didn't cause the postinst to abort ... From the attached log (scroll to the bottom...): Setting up gforge-shell-postgresql (5.2~rc1+1) ... PHP Warning: pg_pconnect(): Unable to connect to PostgreSQL server: FATAL: password authentication failed for user gforge FATAL: password authentication failed for user gforge in /usr/share/gforge/common/include/database-pgsql.php on line 76 PHP Notice: Use of undefined constant SYS_DB_PRIMARY - assumed 'SYS_DB_PRIMARY' in /usr/share/gforge/common/include/database-pgsql.php on line 127 PHP Warning: pg_last_error() expects parameter 1 to be resource, string given in /usr/share/gforge/common/include/database-pgsql.php on line 504 PHP Warning: pg_pconnect(): Unable to connect to PostgreSQL server: FATAL: password authentication failed for user gforge FATAL: password authentication failed for user gforge in /usr/share/gforge/common/include/database-pgsql.php on line 76 PHP Notice: Use of undefined constant SYS_DB_PRIMARY - assumed 'SYS_DB_PRIMARY' in /usr/share/gforge/common/include/database-pgsql.php on line 127 PHP Warning: pg_last_error() expects parameter 1 to be resource, string given in /usr/share/gforge/common/include/database-pgsql.php on line 504 PHP Warning: pg_pconnect(): Unable to connect to PostgreSQL server: FATAL: password authentication failed for user gforge FATAL: password authentication failed for user gforge in /usr/share/gforge/common/include/database-pgsql.php on line 76 PHP Notice: Use of undefined constant SYS_DB_PRIMARY - assumed 'SYS_DB_PRIMARY' in /usr/share/gforge/common/include/database-pgsql.php on line 127 PHP Warning: pg_last_error() expects parameter 1 to be resource, string given in /usr/share/gforge/common/include/database-pgsql.php on line 504 PHP Warning: pg_pconnect(): Unable to connect to PostgreSQL server: FATAL: password authentication failed for user gforge FATAL: password authentication failed for user gforge in /usr/share/gforge/common/include/database-pgsql.php on line 76 PHP Notice: Use of undefined constant SYS_DB_PRIMARY - assumed 'SYS_DB_PRIMARY' in /usr/share/gforge/common/include/database-pgsql.php on line 127 PHP Warning: pg_last_error() expects parameter 1 to be resource, string given in /usr/share/gforge/common/include/database-pgsql.php on line 504 Installing chroot environnement at FusionForge Could Not Connect to Database: . cp: target `//etc/nss-pgsql-root.conf' is not a directory dpkg: error processing gforge-shell-postgresql (--configure): subprocess installed post-installation script returned error exit status 1 cheers, Andreas gforge-plugin-scmgit_5.2~rc1+1.log.gz Description: GNU Zip compressed data
Bug#688375: ntlmaps: modifies conffiles (policy 10.7.3): /etc/ntlmaps/server.cfg
Package: ntlmaps Version: 0.9.9.0.1-11.1 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/ntlmaps/server.cfg cheers, Andreas ntlmaps_0.9.9.0.1-11.1.log.gz Description: GNU Zip compressed data
Bug#687579: abby: neither works with current clive nor with current
clone 687579 -1 retitle 687579 cclive: upgrade breaks abby without declaring so # incomplete dependencies severity 687579 serious reassign 687579 cclive 0.7.9-1 #tags -1 +notsqueeze tags -1 + wheezy sid experimental quit Axel Beckert wrote: starting up abby for the first time on Wheezy shows an error error: /usr/bin/cclive: Not c/clive or it is an unsupported version of it, gustavo panizzo gfa wrote: i did some testing today, and found out abby needs squeeze version of ccive to work. Thanks! Marking so. cclive maintainers: known problem? Any hints for tracking it down? Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: abby: neither works with current clive nor with current
Processing commands for cont...@bugs.debian.org: clone 687579 -1 Bug #687579 [abby] abby: neither works with current clive nor with current cclive version Bug 687579 cloned as bug 688376 retitle 687579 cclive: upgrade breaks abby without declaring so Bug #687579 [abby] abby: neither works with current clive nor with current cclive version Changed Bug title to 'cclive: upgrade breaks abby without declaring so' from 'abby: neither works with current clive nor with current cclive version' # incomplete dependencies severity 687579 serious Bug #687579 [abby] cclive: upgrade breaks abby without declaring so Severity set to 'serious' from 'grave' reassign 687579 cclive 0.7.9-1 Bug #687579 [abby] cclive: upgrade breaks abby without declaring so Bug reassigned from package 'abby' to 'cclive'. No longer marked as found in versions abby/0.4.7-1. Ignoring request to alter fixed versions of bug #687579 to the same values previously set Bug #687579 [cclive] cclive: upgrade breaks abby without declaring so Marked as found in versions cclive/0.7.9-1. #tags -1 +notsqueeze tags -1 + wheezy sid experimental Bug #688376 [abby] abby: neither works with current clive nor with current cclive version Added tag(s) sid, wheezy, and experimental. quit Stopping processing here. Please contact me if you need assistance. -- 687579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687579 688376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688376 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: ferm: modifies conffiles (policy 10.7.3): /etc/default/ferm
Processing control commands: found -1 2.0.7-1 Bug #688377 [ferm] ferm: modifies conffiles (policy 10.7.3): /etc/default/ferm Marked as found in versions ferm/2.0.7-1. -- 688377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688377 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#688377: ferm: modifies conffiles (policy 10.7.3): /etc/default/ferm
Package: ferm Version: 2.1-2 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 2.0.7-1 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/ferm cheers, Andreas ferm_2.1-2.log.gz Description: GNU Zip compressed data
Processed: gom: modifies conffiles (policy 10.7.3): /etc/default/gom
Processing control commands: found -1 0.30.2-5 Bug #688378 [gom] gom: modifies conffiles (policy 10.7.3): /etc/default/gom Marked as found in versions gom/0.30.2-5. -- 688378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688378 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#688378: gom: modifies conffiles (policy 10.7.3): /etc/default/gom
Package: gom Version: 0.30.2-5.3 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 0.30.2-5 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/gom cheers, Andreas gom_0.30.2-5.3.log.gz Description: GNU Zip compressed data
Processed: openvas-server: modifies conffiles (policy 10.7.3): /etc/openvas/openvasd.conf
Processing control commands: found -1 2.0.3-3 Bug #688379 [openvas-server] openvas-server: modifies conffiles (policy 10.7.3): /etc/openvas/openvasd.conf Marked as found in versions openvas-server/2.0.3-3. -- 688379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688379 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#688379: openvas-server: modifies conffiles (policy 10.7.3): /etc/openvas/openvasd.conf
Package: openvas-server Version: 2.0.3-6 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 2.0.3-3 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/openvas/openvasd.conf cheers, Andreas openvas-server_2.0.3-6.log.gz Description: GNU Zip compressed data
Processed: CVE assigned
Processing commands for cont...@bugs.debian.org: retitle 688008 monkey: CVE-2012-4443: CGI scripts executed without dropping RUID/RGID root Bug #688008 [monkey] monkey: CGI scripts executed without dropping RUID/RGID root Changed Bug title to 'monkey: CVE-2012-4443: CGI scripts executed without dropping RUID/RGID root' from 'monkey: CGI scripts executed without dropping RUID/RGID root' End of message, stopping processing here. Please contact me if you need assistance. -- 688008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688008 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#688381: nanourl: postrm mixes remove and purge actions
Package: nanourl Version: 0.1-7.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, the postinst script of your package looks plainly wrong: == rm -f /etc/nanourl/* this needs to be done during purge only and never when the package is just removed if /etc/nanourl/apache.conf is the only file you need to remove, you won't even need extra code for this as thats a conffile and removed by dpkg. == rm -rf /var/lib/mysql/nanoDB WTF? You don't delete databases that way. And you would never issue a DROP DATABASE in postrm remove, only during purge. http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html And I don't even dare to take a look at the postinst script ... piuparts caught this this during a test install nanourl remove nanourl (don't purge!) install nanourl Now /etc/nanourl/apache.conf is missing. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688229: Burning data DVD looks successful but mounting fails with ISOFS: Unable to identify CD-ROM format.
Dear Thomas, I am sorry for my late reply. Also I am CCing just to be sure. If you get the message twice because you subscribed to the report, please tell me. Am Donnerstag, den 20.09.2012, 22:51 +0200 schrieb Thomas Schmitt: brasero (libisofs)DEBUG : Processed 2119108 of 2119108 KB (100 %) It went well, at least as far as libisofs was involved. So this is not the problem with premature end after 50 %. And it is not the riddling CD problem, where Brasero CDs are unreadable, whereas xorriso burned CDs are ok. Great! BraseroLibburn Async SYNCHRONIZE CACHE succeeded after 0.8 seconds ... BraseroLibburn Closing track 01 (absolute track number 1) BraseroLibburn Async CLOSE TRACK SESSION succeeded after 0.4 seconds BraseroLibburn Closing session BraseroLibburn Async CLOSE TRACK SESSION succeeded after 5.3 seconds These messages stem from libburn. They indicate that it saw no severe error message from the drive and that it finished the burn run. I cannot tell, though, how many data were passed through libburn. [ 9103.816252] ISOFS: Unable to identify CD-ROM format. What do you get from dd if=/dev/sr1 bs=2048 skip=16 count=1 | od -c With a valid ISO image, the output should begin by 000 001 C D 0 0 1 and consist of up to 128 lines of text. $ dd if=/dev/sr1 bs=2048 skip=16 count=1 | od -c 1+0 Datensätze ein 1+0 Datensätze aus 2048 Bytes (2,0 kB) kopiert, 0,00199071 s, 1,0 MB/s 000 \0 0 034 001 \0 \0 001 034 0 F 034 + \0 \0 + 020 034 F p \t 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 040 034 \0 I \0 M \0 G \0 _ \0 2 \0 4 \0 2 \0 060 8 \0 . \0 J \0 P \0 G \0 ; \0 1 \0 \0 100 224 ! 001 \0 \0 001 ! 224 @ 276 + \0 \0 + 276 @ 120 p \t 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 034 \0 140 I \0 M \0 G \0 _ \0 2 \0 4 \0 2 \0 9 \0 160 . \0 J \0 P \0 G \0 ; \0 1 \0 \0 \f ' 200 001 \0 \0 001 ' \f u S - \0 \0 - S u p \t 220 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 034 \0 I \0 240 M \0 G \0 _ \0 2 \0 4 \0 3 \0 0 \0 . \0 260 J \0 P \0 G \0 ; \0 1 \0 \0 267 , 001 \0 300 \0 001 , 267 016 y 037 \0 \0 037 y 016 p \t 023 022 320 1 ! \0 \0 \0 \0 001 \0 \0 001 034 \0 I \0 M \0 340 G \0 _ \0 2 \0 4 \0 3 \0 2 \0 . \0 J \0 360 P \0 G \0 ; \0 1 \0 \0 247 0 001 \0 \0 001 400 0 247 340 I \0 \0 I 340 p \t 023 022 1 ! 420 \0 \0 \0 \0 001 \0 \0 001 034 \0 I \0 M \0 G \0 440 _ \0 2 \0 4 \0 3 \0 3 \0 . \0 J \0 P \0 460 G \0 ; \0 1 \0 \0 361 4 001 \0 \0 001 4 361 500 005 G \0 \0 G 005 p \t 023 022 1 ! \0 \0 520 \0 \0 001 \0 \0 001 034 \0 I \0 M \0 G \0 _ \0 540 2 \0 4 \0 3 \0 4 \0 . \0 J \0 P \0 G \0 560 ; \0 1 \0 \0 372 8 001 \0 \0 001 8 372 252 020 600 ! \0 \0 ! 020 252 p \t 023 022 1 ! \0 \0 \0 \0 620 001 \0 \0 001 034 \0 I \0 M \0 G \0 _ \0 2 \0 640 4 \0 3 \0 5 \0 . \0 J \0 P \0 G \0 ; \0 660 1 \0 \0 035 = 001 \0 \0 001 = 035 252 261 035 \0 700 \0 035 261 252 p \t 023 022 1 ! \0 \0 \0 \0 001 \0 720 \0 001 034 \0 I \0 M \0 G \0 _ \0 2 \0 4 \0 740 3 \0 7 \0 . \0 J \0 P \0 G \0 ; \0 1 \0 760 \0 324 @ 001 \0 \0 001 @ 324 ; 206 % \0 \0 % 0001000 206 ; p \t 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 0001020 034 \0 I \0 M \0 G \0 _ \0 2 \0 4 \0 3 \0 0001040 8 \0 . \0 J \0 P \0 G \0 ; \0 1 \0 \0 0001060 205 E 001 \0 \0 001 E 205 M 255 \0 \0255 M 0001100 p \t 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 034 \0 0001120 I \0 M \0 G \0 _ \0 2 \0 4 \0 3 \0 9 \0 0001140 . \0 J \0 P \0 G \0 ; \0 1 \0 \0 [ J 0001160 001 \0 \0 001 J [ 250 P \0 \0 P 250 p \t 0001200 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 034 \0 I \0 0001220 M \0 G \0 _ \0 2 \0 4 \0 4 \0 0 \0 . \0 0001240 J \0 P \0 G \0 ; \0 1 \0 \0 246 N 001 \0 0001260 \0 001 N 246 q K \0 \0 K q p \t 023 022 0001300 1 ! \0 \0 \0 \0 001 \0 \0 001 034 \0 I \0 M \0 0001320 G \0 _ \0 2 \0 4 \0 4 \0 1 \0 . \0 J \0 0001340 P \0 G \0 ; \0 1 \0 \0 p S 001 \0 \0 001 0001360 S p 340 034 $ \0 \0 $ 034 340 p \t 023 022 1 ! 0001400 \0 \0 \0 \0 001 \0 \0 001 034 \0 I \0 M \0 G \0 0001420
Processed: affects 688250, found 688250 in mono-apache-server1/2.6.5-3, found 688250 in mono-xsp1/2.6.5-3 ...
Processing commands for cont...@bugs.debian.org: affects 688250 + mono-apache-server1 mono-xsp1 gclcvs Bug #688250 [piuparts] piuparts: bug for tracking modifies conffiles bugs for packages in squeeze that have been removed afterwards Added indication that 688250 affects mono-apache-server1, mono-xsp1, and gclcvs found 688250 mono-apache-server1/2.6.5-3 Bug #688250 [piuparts] piuparts: bug for tracking modifies conffiles bugs for packages in squeeze that have been removed afterwards The source mono-apache-server1 and version 2.6.5-3 do not appear to match any binary packages Marked as found in versions mono-apache-server1/2.6.5-3. found 688250 mono-xsp1/2.6.5-3 Bug #688250 [piuparts] piuparts: bug for tracking modifies conffiles bugs for packages in squeeze that have been removed afterwards The source mono-xsp1 and version 2.6.5-3 do not appear to match any binary packages Marked as found in versions mono-xsp1/2.6.5-3. found 688250 gclcvs/2.7.0-101 Bug #688250 [piuparts] piuparts: bug for tracking modifies conffiles bugs for packages in squeeze that have been removed afterwards Marked as found in versions gclcvs/2.7.0-101. found 688348 2.9-55 Bug #688348 [mirror] mirror: modifies installed files during postinst for license conformance, causing debsums to report modifications Marked as found in versions mirror/2.9-55. found 687858 3.13 Bug #687858 [tasksel-data] tasksel-data: copyright file missing after upgrade (policy 12.5) Marked as found in versions tasksel/3.13. found 687875 0.9.3-3 Bug #687875 [gnunet-server] gnunet-server: copyright file missing after upgrade (policy 12.5) Marked as found in versions gnunet/0.9.3-3. found 687881 0.9.3-3 Bug #687881 [gnunet-client] gnunet-client: copyright file missing after upgrade (policy 12.5) Marked as found in versions gnunet/0.9.3-3. found 687883 0.9.3-3 Bug #687883 [gnunet-dbg] gnunet-dbg: copyright file missing after upgrade (policy 12.5) Marked as found in versions gnunet/0.9.3-3. user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was deb...@abeckmann.de). usertags 688288 piuparts There were no usertags set. Usertags are now: piuparts. thanks Stopping processing here. Please contact me if you need assistance. -- 687858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687858 687875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687875 687881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687881 687883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687883 688250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688250 688288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688288 688348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688348 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#688229: Burning data DVD looks successful but mounting fails with ISOFS: Unable to identify CD-ROM format.
Hi, Paul Menzel wrote: $ dd if=/dev/sr1 bs=2048 skip=16 count=1 | od -c ... 000 \0 0 034 001 \0 \0 001 034 0 F 034 + \0 \0 + 020 034 F p \t 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 040 034 \0 I \0 M \0 G \0 _ \0 2 \0 4 \0 2 \0 060 8 \0 . \0 J \0 P \0 G \0 ; \0 1 \0 \0 100 224 ! 001 \0 \0 001 ! 224 @ 276 + \0 \0 + 276 @ 120 p \t 023 022 1 ! \0 \0 \0 \0 001 \0 \0 001 034 \0 140 I \0 M \0 G \0 _ \0 2 \0 4 \0 2 \0 9 \0 160 . \0 J \0 P \0 G \0 ; \0 1 \0 \0 \f ' This does not look like an ISO 9660 Primary Volume Descriptor but rather like a snippet from a Joliet directory tree. Read as 16 bit characters one can recognize IMG_2428.JPG and IMG_2429.JPG. They are announced to start at blocks 72752 (decimal) and 74132 (decimal). Sizes are 2825286 and 2866752 bytes. ... if i decoded these little endian 32-bit numbers correctly: 0 034 001 \0 IMG_2428.JPG, Location of Extent F 034 + \0 IMG_2428.JPG, Data Length 224 ! 001 \0 IMG_2429.JPG, Location of Extent @ 276 + \0 IMG_2429.JPG, Data Length (The layout of directory records is documented in ECMA-119, 9.1. Joliet deviates from this layout mainly by using 16-bit characters for File Identifier.) I really wonder how this could get to block 16 of the medium. Brasero did order libisofs to produce a Joliet tree. But it should be stored several blocks after block 16. Before Joliet there should be volume descriptors and the ISO 9660 + Rock Ridge tree. It is clear that no reader software wants to accept this as ISO 9660 filesystem. Guessing from this single block content, i would expect that a few hundred kilobytes of the image start have not been written onto the medium. Most simple explanation for this would be that they were not transmitted from libisofs to libburn. But i riddle how this could be possible. PS: Is there any way to rescue the broken media, that means to correctly finish the burning process? The medium is irreversibly closed. The problem seems to be in lost data blocks. (One could try to retrieve the JPEGs. If the loss is only about data at the image start, then it should be possible to guess names from the remaining part of the Joliet tree.) $ dvd+rw-mediainfo /dev/sr1 The output looks totally normal. Medium is ok. I think I forgot to add that the burner and the same DVD medium were used successfully with for example K3b and I also think xorriso. We have no special indication of any malfunction of burner or medium. There are just not the right bytes stored at the right block addresses. A further test with xorriso would be welcome. Just to be sure. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)
I don't want this in gcc-4.7. Please provide a patch for gcc-defaults. This should work as well. On 22.09.2012 09:23, Andreas Beckmann wrote: reassign 677582 gcc-4.7-base 4.7.2-2 reopen 677582 thanks On 2012-09-21 14:22, Andreas Beckmann wrote: [...] I'm now trying to add these Breaks to gcc-4.7-base, that can't be held back, hopefully. Attached is a diff that finally fixes this upgrade issue, hopefully. gcc-4.7-base isn't that optional as gcc-4.4-base, so it can't be held back, actually enforcing the Breaks vs. ancient gcj. I looked a bit into the history where these Breaks originated, and since gcc-4.7-base Breaks old versions of gcc-4.6-base, I think it would be the right thing to do and add the Breaks vs. 4.4, too. * gcc-4.7-base: ensure smooth upgrades from squeeze by adding Breaks: gcj-4.4-base ( 4.4.6-9~), gnat-4.4-base ( 4.4.6-3~) as in gcc-4.4-base (multiarch patches re-worked in 4.6.1-8/4.4.6-9). Fixes some squeeze-wheezy upgrade paths where apt chooses to hold back gcc-4.4-base and keep gcj-4.4-base installed instead of upgrading gcc-4.4-base and removing the obsolete gcj-4.4-base (Andreas Beckmann). (Closes: #677582) The recent changes on gcc-4.4 that attempted to fix this issue by upgrading Breaks to Conflicts could be reverted, but they can be left as is as they won't do harm (should just add a lintian warning for a versioned Conflicts). I tested this patch with piuparts upgrade tests (squeeze-sid) on a selection of the affected java packages (there are about 60-70 in total, checked around 10 from different sources), and all passed once I added an extra repository with the updated gcc-4.7 packages. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688330: gcc-4.7-base: WTF are you doing to the binary packages?
On 21.09.2012 21:42, Thorsten Glaser wrote: Philipp Kern dixit: I think you could work on your politeness and adjust the tone of your mails. Right. I know that formulating is not one of my better skills. I don't think Matthias had an malicious intent here, to hurt you and induce suffering. Yes, of course not. I think it was merely a human mistake of believing that a simple changelog mistake can be fixed after a quite long gcc build. right, just forgot to include the regenerated .diff.gz into the upload. Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645656: marked as done (gnome-core: please re-soften the network-manager-gnome dependency)
Your message dated Sat, 22 Sep 2012 10:17:32 + with message-id e1tfmmc-0004ft...@franck.debian.org and subject line Bug#645656: fixed in meta-gnome3 1:3.4+2 has caused the Debian Bug report #645656, regarding gnome-core: please re-soften the network-manager-gnome dependency 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.) -- 645656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-core Version: 1:3.0+2 Severity: minor Hello, in the gnome2 - gnome3 transition gnome's dependency to network-manager-gnome and hence all the network-manager-bloat moved (and hardened) from gnome recommends network-manager-gnome to gnome-core depends network-manager-gnome Was this intentional? The Debian ChangeLog doesn't state anything about it. And would it be a big issue to soften this back to recommends? Thanks for your work best regards Mario -- Jene, die grundlegende Freiheit aufgeben wuerden, um eine geringe voruebergehende Sicherheit zu erwerben, verdienen weder Freiheit noch Sicherheit. -- Benjamin Franklin (1706-1790) signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: meta-gnome3 Source-Version: 1:3.4+2 We believe that the bug you reported is fixed in the latest version of meta-gnome3, 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 645...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josselin Mouette j...@debian.org (supplier of updated meta-gnome3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 22 Sep 2012 11:58:56 +0200 Source: meta-gnome3 Binary: gnome-core gnome gnome-desktop-environment gnome-platform-devel gnome-core-devel gnome-devel gnome-dbg gnome-api-docs Architecture: source all amd64 Version: 1:3.4+2 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Josselin Mouette j...@debian.org Description: gnome - Full GNOME Desktop Environment, with extra components gnome-api-docs - API reference documentation for the GNOME libraries gnome-core - GNOME Desktop Environment -- essential components gnome-core-devel - GNOME Desktop Environment -- development components gnome-dbg - debugging symbols for the GNOME desktop environment gnome-desktop-environment - The GNOME Desktop Environment - transitional package gnome-devel - GNOME Desktop Environment -- development tools gnome-platform-devel - GNOME development platform Closes: 645656 681757 Changes: meta-gnome3 (1:3.4+2) unstable; urgency=low . * Depend on g-tweak-tool, it is too useful to be left out. * Update epochs on a pair of dependencies. * Add architecture tweaks for unavailable packages: rygel, aisleriot, seed. Closes: #681757. * Move network-manager dependency to gnome. Only recommend it in gnome-core. This should be in compliance with the Crusade. Closes: #645656. Checksums-Sha1: ab29a98d42a9f7479a422787a755e7c7f4613d83 1535 meta-gnome3_3.4+2.dsc 8d3f487929f8646d07f05df7c5f4bb18eb71f174 23051 meta-gnome3_3.4+2.tar.gz 8efdc3227995ddf208e35c9055df5374c9a1d78c 19380 gnome-desktop-environment_3.4+2_all.deb 60e04f4d3998d9a35addd972e7469f09972b3f37 19434 gnome-devel_3.4+2_all.deb f067020fba59e5dccd960c6ef39e68855fe3a311 19570 gnome-api-docs_3.4+2_all.deb b9640739ae7ffc17c96cb124bd496bd9260bac9c 20796 gnome-core_3.4+2_amd64.deb 1f17028c21e9d55ef63006fc2345e0d7f5a53df1 20770 gnome_3.4+2_amd64.deb 004c3007ed4118f35fcbfc8798cd2456587f9359 19616 gnome-platform-devel_3.4+2_amd64.deb fa2ccb797ae5a6493c8bab9ff4fd1af714f7e31c 20136 gnome-core-devel_3.4+2_amd64.deb 99d92cf338af2455095f98603ed80afa827f1290 19452 gnome-dbg_3.4+2_amd64.deb Checksums-Sha256: a9c275c6fcaec97e3c6b028ba0e00a4a4e30db1f8fc343e114d614528541f2c2 1535 meta-gnome3_3.4+2.dsc 5e68233522a80f479d642c1d3f716e03f61eb2659d4d4d9703e1b72e8f075c92 23051 meta-gnome3_3.4+2.tar.gz e0782c02c65d59c256265df6ff2620c8e51c76688b564d84acfcc1475b5d13a9 19380
Bug#681757: marked as done (uninstallable meta-packages (prevents testing migration))
Your message dated Sat, 22 Sep 2012 10:17:32 + with message-id e1tfmmc-0004fx...@franck.debian.org and subject line Bug#681757: fixed in meta-gnome3 1:3.4+2 has caused the Debian Bug report #681757, regarding uninstallable meta-packages (prevents testing migration) 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.) -- 681757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: meta-gnome3 Version: 1:3.4+1 Severity: serious Due to additional dependencies that were added recently, the gnome meta packages are no longer installable on all architectures: gnome/armel unsatisfiable Depends: aisleriot (= 3.4) gnome/armhf unsatisfiable Depends: aisleriot (= 3.4) gnome/ia64 unsatisfiable Depends: aisleriot (= 3.4) This is due to guile-2.0 failing to build on those architectures. [1] Afaics no bug has been filed for guile-2.0 about those build failures. gnome-core-devel/ia64 unsatisfiable Depends: libseed-gtk3-dev (= 3.2) gnome-core-devel/mips unsatisfiable Depends: libseed-gtk3-dev (= 3.2) seed has been broken on those architectures for a while and I don't expect a fix any time soon. gnome/s390x unsatisfiable Depends: rygel-preferences (= 0.14) gnome/s390x unsatisfiable Depends: rygel-playbin gnome/s390x unsatisfiable Depends: rygel-tracker failing test suite on s390x. Andreas doesn't expect any users on s390x so didn't put any effort in investigating this issue. At this point, I'd probably just arch-qualify those dependencies and exclude those archs. [1] https://buildd.debian.org/status/package.php?p=guile-2.0 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: meta-gnome3 Source-Version: 1:3.4+2 We believe that the bug you reported is fixed in the latest version of meta-gnome3, 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 681...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josselin Mouette j...@debian.org (supplier of updated meta-gnome3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 22 Sep 2012 11:58:56 +0200 Source: meta-gnome3 Binary: gnome-core gnome gnome-desktop-environment gnome-platform-devel gnome-core-devel gnome-devel gnome-dbg gnome-api-docs Architecture: source all amd64 Version: 1:3.4+2 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Josselin Mouette j...@debian.org Description: gnome - Full GNOME Desktop Environment, with extra components gnome-api-docs - API reference documentation for the GNOME libraries gnome-core - GNOME Desktop Environment -- essential components gnome-core-devel - GNOME Desktop Environment -- development components gnome-dbg - debugging symbols for the GNOME desktop environment gnome-desktop-environment - The GNOME Desktop Environment - transitional package gnome-devel - GNOME Desktop Environment -- development tools gnome-platform-devel - GNOME development platform Closes: 645656 681757 Changes: meta-gnome3 (1:3.4+2) unstable; urgency=low . * Depend on g-tweak-tool, it is too useful to be left out. * Update epochs on a pair of dependencies. * Add architecture tweaks for unavailable packages: rygel, aisleriot, seed. Closes: #681757. * Move network-manager dependency to gnome. Only recommend it in gnome-core. This should be in compliance with the Crusade. Closes: #645656. Checksums-Sha1: ab29a98d42a9f7479a422787a755e7c7f4613d83 1535 meta-gnome3_3.4+2.dsc 8d3f487929f8646d07f05df7c5f4bb18eb71f174 23051 meta-gnome3_3.4+2.tar.gz 8efdc3227995ddf208e35c9055df5374c9a1d78c 19380 gnome-desktop-environment_3.4+2_all.deb 60e04f4d3998d9a35addd972e7469f09972b3f37 19434 gnome-devel_3.4+2_all.deb f067020fba59e5dccd960c6ef39e68855fe3a311 19570
Processed: reassign to gcc-defaults
Processing commands for cont...@bugs.debian.org: reassign 677582 gcc-defaults Bug #677582 [gcc-4.7-base] gcc-4.4-base: upgrade problems since removal of gcj-4.4 Bug reassigned from package 'gcc-4.7-base' to 'gcc-defaults'. No longer marked as found in versions gcc-4.7/4.7.2-2. Ignoring request to alter fixed versions of bug #677582 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 677582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677582 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 688128
Processing commands for cont...@bugs.debian.org: tags 688128 + patch Bug #688128 [autokey-gtk] autokey-gtk: does not start Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 688128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688128 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#682481: gnome-shell: epiphany shouldn't be the default browser
Hi, Le lundi 23 juillet 2012 à 10:46 +0200, Julien Cristau a écrit : The default browser should be one that has at least vaguely credible security support, IMO. epiphany doesn't qualify, chromium or iceweasel probably would. Since this is security related, I’d appreciate to have the input of the security team on this matter. I’d prefer to set the default as chromium, since it would avoid a security regression (lack of keyring support in iceweasel) and integrates a bit better with GNOME (since it uses webkit, although a different flavor). Is that OK with you? (I am completely appalled by the fact we don’t even have ONE decent browser for GNOME in the archive, but there’s nothing you can do.) Cheers, -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682481: gnome-shell: epiphany shouldn't be the default browser
On Sat, Sep 22, 2012 at 01:23:01PM +0200, Josselin Mouette wrote: Hi, Le lundi 23 juillet 2012 à 10:46 +0200, Julien Cristau a écrit : The default browser should be one that has at least vaguely credible security support, IMO. epiphany doesn't qualify, chromium or iceweasel probably would. Since this is security related, I’d appreciate to have the input of the security team on this matter. I’d prefer to set the default as chromium, since it would avoid a security regression (lack of keyring support in iceweasel) and integrates a bit better with GNOME (since it uses webkit, although a different flavor). Is that OK with you? (I am completely appalled by the fact we don’t even have ONE decent browser for GNOME in the archive, but there’s nothing you can do.) I think that is a very good idea: In Wheezy it is planned to always build the latest chromium release in stable-security. This will ensure that there's always a secure and technically up-to-date browser. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 668026
Processing commands for cont...@bugs.debian.org: tags 668026 + patch pending Bug #668026 [src:libusb] libusb: FTBFS[kfreebsd]: error: 'struct usb_ctl_request' has no member named 'request' Added tag(s) pending and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 668026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668026 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#668026: Patch
The attached patch fixes the FTBFS. -- Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/ GnuPG: 2048R/02F946FC 35E9 1344 9F77 5F43 13DD 6423 DBF4 80C6 02F9 46FC diff -Nru libusb-0.1.12/debian/changelog libusb-0.1.12/debian/changelog --- libusb-0.1.12/debian/changelog 2012-06-03 17:31:31.0 +0100 +++ libusb-0.1.12/debian/changelog 2012-09-22 13:41:35.0 +0100 @@ -1,3 +1,12 @@ +libusb (2:0.1.12-23+nmu1) unstable; urgency=low + + * Fix kfreebsd-* FTBFS: ignore the result of the (BSD-only) +HAVE_OLD_DEV_USB_USB_H configure check, which started misbehaving in 2012. +We ignore the system-provided API in favour of an embedded copy of a header +file anyway (closes: #668026). + + -- Marcin Owsiany porri...@debian.org Sat, 22 Sep 2012 12:36:29 + + libusb (2:0.1.12-23) unstable; urgency=low * Enable the patches in debian/patches/series. diff -Nru libusb-0.1.12/debian/patches/06_bsd.diff libusb-0.1.12/debian/patches/06_bsd.diff --- libusb-0.1.12/debian/patches/06_bsd.diff2011-12-31 10:43:17.0 + +++ libusb-0.1.12/debian/patches/06_bsd.diff2012-09-22 13:35:40.0 +0100 @@ -1,6 +1,8 @@ a/bsd.c -+++ b/bsd.c -@@ -39,7 +39,7 @@ +Index: libusb-0.1.12/bsd.c +=== +--- libusb-0.1.12.orig/bsd.c 2012-09-22 12:28:40.0 + libusb-0.1.12/bsd.c2012-09-22 12:35:17.0 + +@@ -39,14 +39,22 @@ #include sys/time.h #include sys/ioctl.h @@ -9,8 +11,26 @@ #include usbi.h #ifdef HAVE_CONFIG_H /dev/null -+++ b/freebsd-usb.h + #include config.h + #endif + +-#ifdef HAVE_OLD_DEV_USB_USB_H ++/* ++ * Since the Debian version includes freebsd-usb.h instead of ++ * dev/usb/usb.h, the API provided by the latter file does not matter. The ++ * configure check gives false positives as of 2012, but rather than fixing a ++ * check for something we don't use anyway, just unconditionally skip those ++ * definitions. ++ * #ifdef HAVE_OLD_DEV_USB_USB_H ++ */ ++#if 0 + /* + * It appears some of the BSD's (OpenBSD atleast) have switched over to a + * new naming convention, so we setup some macro's for backward +Index: libusb-0.1.12/freebsd-usb.h +=== +--- /dev/null 1970-01-01 00:00:00.0 + libusb-0.1.12/freebsd-usb.h2012-09-22 12:28:40.0 + @@ -0,0 +1,706 @@ +/*$NetBSD: usb.h,v 1.69 2002/09/22 23:20:50 augustss Exp $*/ +/*$FreeBSD: src/sys/dev/usb/usb.h,v 1.47.2.1.2.1 2009/04/15 03:14:26 kensmith Exp $*/
Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)
On 2012-09-22 12:08, Matthias Klose wrote: I don't want this in gcc-4.7. Please provide a patch for gcc-defaults. This should work as well. That won't work, just tried it. The only package from gcc-defaults that could be involved in the problematic upgrade paths is gcj-jre-headless and that will be held back together with gcc-4.4-base after adding Breaks: gcj-4.4-base ( 4.4.6-9~) The problem only manifests for a few java libraries (and their rdepends, that cannot be tested due to these failures): libcharva1-java 1.1.4-5 libcobra-java 0.98.4-4 libcrimson-java 1:1.1.3-11 libdtdparser-java 1.21a-5 libexml-java 0.0.20080703-4 libflute-java 1:1.1.6-3 libgcj-bc 4.7.1-1 libgdcm-java 2.2.1-1 libglpk-java 1.0.18-1 libgui-commands-java 1.1.43-6 libhsqldb-java 1.8.0.10-14 libjazzy-java 0.5.2-1 libjboss-aspects-java 4.2.3.GA-7 libjboss-classloader-java 2.0.6.GA-2 libjboss-cluster-java 4.2.3.GA-7 libjboss-connector-java 4.2.3.GA-7 libjboss-deployers-java 2.0.4.GA-2 libjboss-deployment-java 4.2.3.GA-7 libjboss-ejb3-java 4.2.3.GA-7 libjboss-ejb3x-java 4.2.3.GA-7 libjboss-integration-java 5.0.3.GA-2 libjboss-j2ee-java 4.2.3.GA-7 libjboss-jms-java 4.2.3.GA-7 libjboss-jmx-java 4.2.3.GA-7 libjboss-management-java 4.2.3.GA-7 libjboss-messaging-java 4.2.3.GA-7 libjboss-metadata-java 2.0.3.GA-1 libjboss-microcontainer-java 2.0.10.GA-2 libjboss-naming-java 4.2.3.GA-7 libjboss-reflect-java 2.0.3.GA-1 libjboss-security-java 4.2.3.GA-7 libjboss-server-java 4.2.3.GA-7 libjboss-system-java 4.2.3.GA-7 libjboss-test-java 4.2.3.GA-7 libjboss-transaction-java 4.2.3.GA-7 libjboss-vfs-java 2.0.1.GA-2 libjboss-web-services-java 0.0+svn5660+dak2-3 libjboss-webservices-java 4.2.3.GA-7 libjboss-xml-binding-java 2.0.3.GA-2 libjempbox-java 1:1.7.0+dfsg-3 libjgoodies-animation-java 1.2.0-5 libjgoodies-binding-java 2.1.0-1 libjmathtex-java 0.7~pre-6 libjmdns-java 3.4.1-2 libjorbis-java 0.0.17-2 libjrosetta-java 1.0.4-4 libjspeex-java 0.9.7-3 liblaf-plugin-java 1.0-2 libmp3spi-java 1.9.5-1 libsaxon-java 1:6.5.5-8 libsetools-java 3.3.7-3 libswing-layout-java 1.0.4-2 libvecmath-java 1.5.2-3 libvtk-java 5.8.0-13+b1 libxml-commons-resolver1.1-java 1.2-7 libxml-java 1.1.6.dfsg-3 libxmlgraphics-commons-java 1.4.dfsg-4 and my proposed gcc-4.7-base patch fixes all of them, just verified Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 668026 in 2:0.1.12-20
Processing commands for cont...@bugs.debian.org: found 668026 2:0.1.12-20 Bug #668026 [src:libusb] libusb: FTBFS[kfreebsd]: error: 'struct usb_ctl_request' has no member named 'request' Marked as found in versions libusb/2:0.1.12-20. thanks Stopping processing here. Please contact me if you need assistance. -- 668026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668026 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#650742: marked as done (dh_testdir: debian/control has a duplicate entry for pcc-for-)
Your message dated Sat, 22 Sep 2012 13:27:49 + (UTC) with message-id pine.bsm.4.64l.1209221326290.6...@herc.mirbsd.org and subject line pcc needs multiarch aware dpkg has caused the Debian Bug report #650742, regarding dh_testdir: debian/control has a duplicate entry for pcc-for- 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.) -- 650742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pcc Severity: serious Justification: FTBFS Hi, Thanks for packaging pcc ! I cannot build pcc on my squeeze system, it fails with: dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: source package pcc dpkg-buildpackage: source version 1.1.0~DEVEL+20110422-1 dpkg-buildpackage: source changed by Thorsten Glaser t...@mirbsd.de dpkg-buildpackage: host architecture amd64 dpkg-source --before-build pcc-1.1.0~DEVEL+20110422 fakeroot debian/rules clean test -e debian/control.in mksh debian/control.in debian/control dh_testdir dh_testdir: debian/control has a duplicate entry for pcc-for- make: *** [clean] Error 9 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Thanks ! -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Hi, I’m closing this, as the pcc in experimental needs an already multiarch-aware dpkg to build (even though it cannot cope with a multiarch debian, which I’m working on right now), so it’s no candidate for squeeze. (I don’t even promise it’ll work on wheezy, but right now I don’t see why it shouldn’t, once I’m done with it.) bye, //mirabilos -- Natureshadow Dann mach ich git annex copy --to shore und fertig ist das Natureshadow das ist ja viel cooler als ownCloud ... mirabilos sag ich doch Natureshadow ja wieso stimmt das denn immer was du sagst ...---End Message---
Bug#668026: marked as done (libusb: FTBFS[kfreebsd]: error: 'struct usb_ctl_request' has no member named 'request')
Your message dated Sat, 22 Sep 2012 13:32:52 + with message-id e1tfppe-0007sh...@franck.debian.org and subject line Bug#668026: fixed in libusb 2:0.1.12-23+nmu1 has caused the Debian Bug report #668026, regarding libusb: FTBFS[kfreebsd]: error: 'struct usb_ctl_request' has no member named 'request' 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.) -- 668026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libusb Version: 2:0.1.12-21 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: x86_64-kfreebsd-gnu-gcc -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 -Werror -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -MT bsd.lo -MD -MP -MF .deps/bsd.Tpo -c ../bsd.c -fPIC -DPIC -o .libs/bsd.o ../bsd.c: In function 'usb_set_altinterface': ../bsd.c:236:7: error: 'struct usb_alt_interface' has no member named 'interface_index' ../bsd.c:237:7: error: 'struct usb_alt_interface' has no member named 'alt_no' ../bsd.c: In function 'usb_control_msg': ../bsd.c:457:6: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:458:6: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:459:3: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:459:3: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:459:3: error: left-hand operand of comma expression has no effect [-Werror=unused-value] ../bsd.c:460:3: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:460:3: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:460:3: error: left-hand operand of comma expression has no effect [-Werror=unused-value] ../bsd.c:461:3: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:461:3: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:461:3: error: left-hand operand of comma expression has no effect [-Werror=unused-value] ../bsd.c:463:6: error: 'struct usb_ctl_request' has no member named 'data' ../bsd.c:464:6: error: 'struct usb_ctl_request' has no member named 'flags' ../bsd.c:480:10: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c:480:10: error: 'struct usb_ctl_request' has no member named 'request' ../bsd.c: In function 'usb_os_find_devices': ../bsd.c:541:7: error: 'struct usb_device_info' has no member named 'addr' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: left-hand operand of comma expression has no effect [-Werror=unused-value] ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: value computed is not used [-Werror=unused-value] ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: left-hand operand of comma expression has no effect [-Werror=unused-value] ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named 'devnames' ../bsd.c:547:9: error: 'struct usb_device_info' has no member named
Bug#687869: marked as done (libgsm0710-dev: copyright file missing after upgrade (policy 12.5))
Your message dated Sat, 22 Sep 2012 13:32:36 + with message-id e1tfpoy-0007za...@franck.debian.org and subject line Bug#687869: fixed in libgsm0710 1.2.2-2 has caused the Debian Bug report #687869, regarding libgsm0710-dev: copyright file missing after upgrade (policy 12.5) 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.) -- 687869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libgsm0710-dev Version: 1.2.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 libgsm0710-dev/1.2.2-1 A test with piuparts revealed that package libgsm0710-dev misses the copyright file after an upgrade from squeeze to wheezy, which is a violation of Policy 12.5 : http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/libgsm0710-dev/ is just an empty directory. The output produced by piuparts can be found here : http://piuparts.debian.org/squeeze2wheezy/fail/libgsm0710-dev_1.2.2-1.log Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile ---End Message--- ---BeginMessage--- Source: libgsm0710 Source-Version: 1.2.2-2 We believe that the bug you reported is fixed in the latest version of libgsm0710, 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 687...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Reichel s...@debian.org (supplier of updated libgsm0710 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 22 Sep 2012 15:20:40 +0200 Source: libgsm0710 Binary: libgsm0710-0 libgsm0710-dev libgsm0710-dbg Architecture: source amd64 Version: 1.2.2-2 Distribution: unstable Urgency: low Maintainer: Debian FreeSmartphone.Org Team pkg-fso-ma...@lists.alioth.debian.org Changed-By: Sebastian Reichel s...@debian.org Description: libgsm0710-0 - Implementation of the 3GPP GSM 07.10 multiplexing protocol libgsm0710-dbg - debugging symbols for use with libgsm0710 libgsm0710-dev - development files for use with libgsm0710 Closes: 687869 687886 Changes: libgsm0710 (1.2.2-2) unstable; urgency=low . [ Salvatore Bonaccorso ] * Replace documentation directory with symlink. Replace documentation directory for libgsm0710-dbg and libgsm0710-dev with a symlink. When updating from Squeeze to Wheezy /usr/share/doc/libgsm0710-dbg and /usr/share/doc/libgsm0710-dev resulted in empty directories with no copyright file (which is violating Debian policy 10.5). (Closes: #687869, #687886) Checksums-Sha1: 77fd0efb7691d45b353fc029ad889b9e4eddc557 2104 libgsm0710_1.2.2-2.dsc 78a6158a9b5ed8c3238bb3a3d3aa628dc4296608 3641 libgsm0710_1.2.2-2.debian.tar.gz 285fe6aeff42af1e99ae8594caa75c7a7a3c5535 9608 libgsm0710-0_1.2.2-2_amd64.deb 08525c11828a870e10cafc9df15901895f40b60c 4046 libgsm0710-dev_1.2.2-2_amd64.deb b846bf1c066867c8561d8daa73cb2e192a5c49e1 12436 libgsm0710-dbg_1.2.2-2_amd64.deb Checksums-Sha256: 16db28952883ddcf0c5d098073702bc890ef4330bfe53691a3c008c219765246 2104 libgsm0710_1.2.2-2.dsc 8ed4487e07a0f9703f4c6d55266f8242aaf7b761bbff43aa46c7e469f7f056bc 3641 libgsm0710_1.2.2-2.debian.tar.gz e05fff2cd202e47334cbe5c5a1c2ccf2cde29074766f2c7f2298db22b8b044a4 9608 libgsm0710-0_1.2.2-2_amd64.deb ff2a54e8ea3d73ee1239a1116cb76772f40ebd83ba5c4f7a717107e062b46020 4046 libgsm0710-dev_1.2.2-2_amd64.deb 9b109d5a6b4a9352549642d9c49ae0778ffe08b4d146cf2b3ccb57ed6f1955ce 12436 libgsm0710-dbg_1.2.2-2_amd64.deb Files: 5b4efa89f29b8cbbe5f4d92b55aea102 2104 libs extra libgsm0710_1.2.2-2.dsc d8cb7030566058980e6e81581509dd88 3641 libs extra libgsm0710_1.2.2-2.debian.tar.gz 794cf146090572a0d73a7ac04e9d7aa5 9608 libs extra libgsm0710-0_1.2.2-2_amd64.deb 7c05945adeb73d9949cec5049af83b29 4046 libdevel extra libgsm0710-dev_1.2.2-2_amd64.deb b6b5b99c0ae966110f0df95aa89df305 12436 debug extra libgsm0710-dbg_1.2.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQXbyYAAoJENju1/PIO/qa0KwP/RBRkP4r3X9OaL0Hx5T64+zd E7oMGi4kPGVbT2LsXfJdMBwEsiNT8JHmQdWPCuComcdK0XBoVKuHtlrGCmjWetnE
Bug#687886: marked as done (libgsm0710-dbg: copyright file missing after upgrade (policy 12.5))
Your message dated Sat, 22 Sep 2012 13:32:36 + with message-id e1tfpoy-0007zd...@franck.debian.org and subject line Bug#687886: fixed in libgsm0710 1.2.2-2 has caused the Debian Bug report #687886, regarding libgsm0710-dbg: copyright file missing after upgrade (policy 12.5) 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.) -- 687886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libgsm0710-dbg Version: 1.2.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 libgsm0710-dbg/1.2.2-1 A test with piuparts revealed that package libgsm0710-dbg misses the copyright file after an upgrade from squeeze to wheezy, which is a violation of Policy 12.5 : http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/libgsm0710-dbg/ is just an empty directory. The output produced by piuparts can be found here : http://piuparts.debian.org/squeeze2wheezy/fail/libgsm0710-dbg_1.2.2-1.log Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile ---End Message--- ---BeginMessage--- Source: libgsm0710 Source-Version: 1.2.2-2 We believe that the bug you reported is fixed in the latest version of libgsm0710, 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 687...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Reichel s...@debian.org (supplier of updated libgsm0710 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 22 Sep 2012 15:20:40 +0200 Source: libgsm0710 Binary: libgsm0710-0 libgsm0710-dev libgsm0710-dbg Architecture: source amd64 Version: 1.2.2-2 Distribution: unstable Urgency: low Maintainer: Debian FreeSmartphone.Org Team pkg-fso-ma...@lists.alioth.debian.org Changed-By: Sebastian Reichel s...@debian.org Description: libgsm0710-0 - Implementation of the 3GPP GSM 07.10 multiplexing protocol libgsm0710-dbg - debugging symbols for use with libgsm0710 libgsm0710-dev - development files for use with libgsm0710 Closes: 687869 687886 Changes: libgsm0710 (1.2.2-2) unstable; urgency=low . [ Salvatore Bonaccorso ] * Replace documentation directory with symlink. Replace documentation directory for libgsm0710-dbg and libgsm0710-dev with a symlink. When updating from Squeeze to Wheezy /usr/share/doc/libgsm0710-dbg and /usr/share/doc/libgsm0710-dev resulted in empty directories with no copyright file (which is violating Debian policy 10.5). (Closes: #687869, #687886) Checksums-Sha1: 77fd0efb7691d45b353fc029ad889b9e4eddc557 2104 libgsm0710_1.2.2-2.dsc 78a6158a9b5ed8c3238bb3a3d3aa628dc4296608 3641 libgsm0710_1.2.2-2.debian.tar.gz 285fe6aeff42af1e99ae8594caa75c7a7a3c5535 9608 libgsm0710-0_1.2.2-2_amd64.deb 08525c11828a870e10cafc9df15901895f40b60c 4046 libgsm0710-dev_1.2.2-2_amd64.deb b846bf1c066867c8561d8daa73cb2e192a5c49e1 12436 libgsm0710-dbg_1.2.2-2_amd64.deb Checksums-Sha256: 16db28952883ddcf0c5d098073702bc890ef4330bfe53691a3c008c219765246 2104 libgsm0710_1.2.2-2.dsc 8ed4487e07a0f9703f4c6d55266f8242aaf7b761bbff43aa46c7e469f7f056bc 3641 libgsm0710_1.2.2-2.debian.tar.gz e05fff2cd202e47334cbe5c5a1c2ccf2cde29074766f2c7f2298db22b8b044a4 9608 libgsm0710-0_1.2.2-2_amd64.deb ff2a54e8ea3d73ee1239a1116cb76772f40ebd83ba5c4f7a717107e062b46020 4046 libgsm0710-dev_1.2.2-2_amd64.deb 9b109d5a6b4a9352549642d9c49ae0778ffe08b4d146cf2b3ccb57ed6f1955ce 12436 libgsm0710-dbg_1.2.2-2_amd64.deb Files: 5b4efa89f29b8cbbe5f4d92b55aea102 2104 libs extra libgsm0710_1.2.2-2.dsc d8cb7030566058980e6e81581509dd88 3641 libs extra libgsm0710_1.2.2-2.debian.tar.gz 794cf146090572a0d73a7ac04e9d7aa5 9608 libs extra libgsm0710-0_1.2.2-2_amd64.deb 7c05945adeb73d9949cec5049af83b29 4046 libdevel extra libgsm0710-dev_1.2.2-2_amd64.deb b6b5b99c0ae966110f0df95aa89df305 12436 debug extra libgsm0710-dbg_1.2.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQXbyYAAoJENju1/PIO/qa0KwP/RBRkP4r3X9OaL0Hx5T64+zd E7oMGi4kPGVbT2LsXfJdMBwEsiNT8JHmQdWPCuComcdK0XBoVKuHtlrGCmjWetnE
Bug#623952: pcc: cannot cope with M-A, has file conflict
Hi, I’m working on pcc (again) and will probably be able to take care of these two issues soonish, too. (Not tagging as pending because the current CVS commits aren’t yet sufficient.) bye, //mirabilos -- In traditional syntax ' is ignored, but in c99 everything between two ' is handled as character constant. Therefore you cannot use ' in a preproces- sing file in c99 mode. -- Ragge No faith left in ISO C99, undefined behaviour, etc. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623953: cross-pcc needs cross-binutils
retitle 623953 cross-pcc needs cross-binutils severity 623953 wishlist thanks Hi, there still seems to be no consensus regarding this, but with (only) my “pcc maintainer” hat on, by mentioning it in the README.Debian file how to build those cross compilers, I think my part is done, especially considering that the Wiki page is updated now to point to precompiled binaries from Emdebian, and we can even put some pcc-specific information on it. In general DD terms, uploading cross-binutils might be discussed, but that doesn’t scale due to n² complexity: we currently have 14 Debian and 7 Debian-Ports architectures, and pcc currently works on 2 (amd64, i386) out of an upstream-named 5 (+ mips, mipsel, powerpc; with some sort of ARM and hppa being a possibility) ones, so pcc alone would need 2*21-2=40 cross-binutils uploaded right now, 5*21-5=100 eventually with 7*21-7=140 a possibility, and for the general case we need 21²-21=420 cross-binutils binary packages, so I understand the reluctance for that. bye, //mirabilos -- Natureshadow Dann mach ich git annex copy --to shore und fertig ist das Natureshadow das ist ja viel cooler als ownCloud ... mirabilos sag ich doch Natureshadow ja wieso stimmt das denn immer was du sagst ... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cross-pcc needs cross-binutils
Processing commands for cont...@bugs.debian.org: retitle 623953 cross-pcc needs cross-binutils Bug #623953 [pcc-for-x86-64-linux-gnu] pcc-for-x86-64-linux-gnu: depends on an unavailable package Changed Bug title to 'cross-pcc needs cross-binutils' from 'pcc-for-x86-64-linux-gnu: depends on an unavailable package' severity 623953 wishlist Bug #623953 [pcc-for-x86-64-linux-gnu] cross-pcc needs cross-binutils Severity set to 'wishlist' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 623953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623953 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#687869: [pkg-fso-maint] Bug#687869: libgsm0710: diff for NMU version 1.2.2-1.1
On Sat, Sep 22, 2012 at 09:22:53AM +0200, Salvatore Bonaccorso wrote: The attached patch should fix this issue. I'm only attaching the patch but have not done any further action. Sebastian do you have time to do the upload? Thanks for the patch. I just uploaded the change as 1.2.2-2. -- Sebastian signature.asc Description: Digital signature
Processed: severity of 688075 is minor
Processing commands for cont...@bugs.debian.org: severity 688075 minor Bug #688075 [mc] mc 3:4.8.3-8 broke `~' directory completition Severity set to 'minor' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 688075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688075 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: bug 688075 is forwarded to https://www.midnight-commander.org/ticket/2898
Processing commands for cont...@bugs.debian.org: forwarded 688075 https://www.midnight-commander.org/ticket/2898 Bug #688075 [mc] mc 3:4.8.3-8 broke `~' directory completition Set Bug forwarded-to-address to 'https://www.midnight-commander.org/ticket/2898'. thanks Stopping processing here. Please contact me if you need assistance. -- 688075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688075 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#668026: libusb upload to testing-proposed-updates
Hello, I've already NMUed libusb 2:0.1.12-23+nmu1 to sid to fix RC bug #668026 there. However I've also discovered the bug is present in the version currently in testing (2:0.1.12-20). I suppose the changes in -21 to -23 are not meant/eligible for inclusion in testing, so I'd like to upload 2:0.1.12-20+nmu1 (interdiff attached) to testing-proposed-updates. Please let me know if this looks good. regards, -- Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/ GnuPG: 2048R/02F946FC 35E9 1344 9F77 5F43 13DD 6423 DBF4 80C6 02F9 46FC diff -Nru libusb-0.1.12/debian/changelog libusb-0.1.12/debian/changelog --- libusb-0.1.12/debian/changelog 2011-12-31 00:52:03.0 + +++ libusb-0.1.12/debian/changelog 2012-09-22 15:02:30.0 +0100 @@ -1,3 +1,13 @@ +libusb (2:0.1.12-20+nmu1) testing-proposed-updates; urgency=low + + * Non-maintainer upload. + * Fix kfreebsd-* FTBFS: ignore the result of the (BSD-only) +HAVE_OLD_DEV_USB_USB_H configure check, which started misbehaving in 2012. +We ignore the system-provided API in favour of an embedded copy of a header +file anyway (closes: #668026). + + -- Marcin Owsiany porri...@debian.org Sat, 22 Sep 2012 15:01:25 +0100 + libusb (2:0.1.12-20) unstable; urgency=low * Add symbols files. diff -Nru libusb-0.1.12/debian/patches/06_bsd.diff libusb-0.1.12/debian/patches/06_bsd.diff --- libusb-0.1.12/debian/patches/06_bsd.diff2011-12-31 10:43:17.0 + +++ libusb-0.1.12/debian/patches/06_bsd.diff2012-09-22 14:22:30.0 +0100 @@ -1,6 +1,8 @@ a/bsd.c -+++ b/bsd.c -@@ -39,7 +39,7 @@ +Index: libusb-0.1.12/bsd.c +=== +--- libusb-0.1.12.orig/bsd.c 2012-09-22 14:21:07.0 +0100 libusb-0.1.12/bsd.c2012-09-22 14:22:24.954862503 +0100 +@@ -39,14 +39,22 @@ #include sys/time.h #include sys/ioctl.h @@ -9,8 +11,26 @@ #include usbi.h #ifdef HAVE_CONFIG_H /dev/null -+++ b/freebsd-usb.h + #include config.h + #endif + +-#ifdef HAVE_OLD_DEV_USB_USB_H ++/* ++ * Since the Debian version includes freebsd-usb.h instead of ++ * dev/usb/usb.h, the API provided by the latter file does not matter. The ++ * configure check gives false positives as of 2012, but rather than fixing a ++ * check for something we don't use anyway, just unconditionally skip those ++ * definitions. ++ * #ifdef HAVE_OLD_DEV_USB_USB_H ++ */ ++#if 0 + /* + * It appears some of the BSD's (OpenBSD atleast) have switched over to a + * new naming convention, so we setup some macro's for backward +Index: libusb-0.1.12/freebsd-usb.h +=== +--- /dev/null 1970-01-01 00:00:00.0 + libusb-0.1.12/freebsd-usb.h2012-09-22 14:21:07.0 +0100 @@ -0,0 +1,706 @@ +/*$NetBSD: usb.h,v 1.69 2002/09/22 23:20:50 augustss Exp $*/ +/*$FreeBSD: src/sys/dev/usb/usb.h,v 1.47.2.1.2.1 2009/04/15 03:14:26 kensmith Exp $*/
Bug#687869: [pkg-fso-maint] Bug#687869: libgsm0710: diff for NMU version 1.2.2-1.1
Hi Sebastian On Sat, Sep 22, 2012 at 03:29:51PM +0200, Sebastian Reichel wrote: On Sat, Sep 22, 2012 at 09:22:53AM +0200, Salvatore Bonaccorso wrote: The attached patch should fix this issue. I'm only attaching the patch but have not done any further action. Sebastian do you have time to do the upload? Thanks for the patch. I just uploaded the change as 1.2.2-2. Cool thank you! p.s.: there was unfortunately a typo in my changelog entry, should have been policy 12.5. Btw, you can apply a similar fix for the bugs in [1]. I have not investigated, but they should go all in the same direction. [1]: http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=pkg-fso-maint%40lists.alioth.debian.org;severity=serious Regards, Salvatore signature.asc Description: Digital signature
Bug#688410: nginx: Don't fail installing nginx-{naxsi, light, full, extras} if /etc/nginx/sites-* doesn't exist
Package: nginx-extras
Version: 1.2.1-2.2
Severity: serious
Tags: patch
Justification: 6
Hi!
When installing nginx-{naxsi,light,full,extras} the postinst scripts
create a symlink in /etc/nginx/sites-enabled/default from
/etc/nginx/sites-available/default if /etc/nginx/sites-enabled/default
doesn't exist. This script does not check if /etc/nginx/sites-enabled or
/etc/nginx/sites-available are in existance.
This results in breakage of these packages when installing them on an
existing nginx configuration without sites-enabled/sites-available.
The attached patch should fix this by testing wether or not
sites-enabled/sites-available do exist and only then also will create
the symbolic link.
Hope it helps,
Andreas Marschke.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nginx-extras depends on:
ii libc6 2.13-35
ii libexpat1 2.1.0-1
ii libgd2-noxpm2.0.36~rc1~dfsg-6.1
ii libgeoip1 1.4.8+dfsg-3
ii liblua5.1-0 5.1.5-4
ii libpam0g1.1.3-7.1
ii libpcre31:8.30-5
ii libperl5.14 5.14.2-13
ii libssl1.0.0 1.0.1c-4
ii libxml2 2.8.0+dfsg1-5
ii libxslt1.1 1.1.26-13
ii nginx-common1.2.1-2.2
ii perl5.14.2-13
ii perl-base [perlapi-5.14.2] 5.14.2-13
ii zlib1g 1:1.2.7.dfsg-13
nginx-extras recommends no packages.
nginx-extras suggests no packages.
-- no debconf information
diff --git a/debian/nginx-extras.postinst b/debian/nginx-extras.postinst
index 0bef8e1..71583d7 100644
--- a/debian/nginx-extras.postinst
+++ b/debian/nginx-extras.postinst
@@ -3,7 +3,9 @@ set -e
case $1 in
configure)
-if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]; then
+if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]
+ [ -d /etc/nginx/sites-enabled ]
+ [ -d /etc/nginx/sites-available ]; then
ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default
fi
;;
diff --git a/debian/nginx-full.postinst b/debian/nginx-full.postinst
index 0bef8e1..20c4def 100644
--- a/debian/nginx-full.postinst
+++ b/debian/nginx-full.postinst
@@ -3,7 +3,8 @@ set -e
case $1 in
configure)
-if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]; then
+if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]
+ [ -d /etc/nginx/sites-enabled ] [ -d /etc/nginx/sites-available ]; then
ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default
fi
;;
diff --git a/debian/nginx-light.postinst b/debian/nginx-light.postinst
index 0bef8e1..0268e82 100644
--- a/debian/nginx-light.postinst
+++ b/debian/nginx-light.postinst
@@ -3,7 +3,9 @@ set -e
case $1 in
configure)
-if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]; then
+if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]
+ [ -d /etc/nginx/sites-enabled ]
+ [ -d /etc/nginx/sites-available ]; then
ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default
fi
;;
diff --git a/debian/nginx-naxsi.postinst b/debian/nginx-naxsi.postinst
index 0bef8e1..0268e82 100644
--- a/debian/nginx-naxsi.postinst
+++ b/debian/nginx-naxsi.postinst
@@ -3,7 +3,9 @@ set -e
case $1 in
configure)
-if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]; then
+if [ -z $2 ] [ ! -e /etc/nginx/sites-enabled/default ]
+ [ -d /etc/nginx/sites-enabled ]
+ [ -d /etc/nginx/sites-available ]; then
ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default
fi
;;
Bug#687857: linux-atm: diff for NMU version 1:2.5.1-1.5
tags 687857 + pending
thanks
Dear maintainer,
I've prepared an NMU for linux-atm (versioned as 1:2.5.1-1.5) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru linux-atm-2.5.1/debian/changelog linux-atm-2.5.1/debian/changelog
--- linux-atm-2.5.1/debian/changelog 2012-07-03 03:03:50.0 +0200
+++ linux-atm-2.5.1/debian/changelog 2012-09-22 16:18:14.0 +0200
@@ -1,3 +1,13 @@
+linux-atm (1:2.5.1-1.5) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Correct directory in libatm1-dev.postinst.
+Correct the directory checked for the directory symlink migration to be
+/usr/share/doc/libatm1-dev for the libatm1-dev binary package. It
+wrongly refered to /usr/share/doc/atm-tools. (Closes: #687857)
+
+ -- Salvatore Bonaccorso car...@debian.org Sat, 22 Sep 2012 11:03:25 +0200
+
linux-atm (1:2.5.1-1.4) unstable; urgency=low
* Non-maintainer upload.
diff -Nru linux-atm-2.5.1/debian/libatm1-dev.postinst linux-atm-2.5.1/debian/libatm1-dev.postinst
--- linux-atm-2.5.1/debian/libatm1-dev.postinst 2011-10-30 15:35:30.0 +0100
+++ linux-atm-2.5.1/debian/libatm1-dev.postinst 2012-09-22 16:18:14.0 +0200
@@ -3,12 +3,15 @@
upgrade_quirks() {
[ $2 ] || return 0
- dpkg --compare-versions $2 lt 1:2.5.1-1.3 || return 0
+ dpkg --compare-versions $2 lt 1:2.5.1-1.5 || return 0
# replaced by a symlink in 1:2.5.1-1.3, but dpkg fails to do it on upgrades
- if [ -d /usr/share/doc/atm-tools -a ! -L /usr/share/doc/atm-tools ] ; then
-rmdir /usr/share/doc/atm-tools
-ln -s /usr/share/doc/libatm1 /usr/share/doc/atm-tools
+ # furthermore the postinst had a bug in 1:2.5.1-1.4 handling wrongly the
+ # /usr/share/doc/libatm1-dev directory (it refered to /usr/share/doc/atm-tools
+ # previously
+ if [ -d /usr/share/doc/libatm1-dev -a ! -L /usr/share/doc/libatm1-dev ] ; then
+rmdir /usr/share/doc/libatm1-dev
+ln -s /usr/share/doc/libatm1 /usr/share/doc/libatm1-dev
fi
return 0
signature.asc
Description: Digital signature
Processed: linux-atm: diff for NMU version 1:2.5.1-1.5
Processing commands for cont...@bugs.debian.org: tags 687857 + pending Bug #687857 [libatm1-dev] libatm1-dev: copyright file missing after upgrade (policy 12.5) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 687857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687857 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 668757
Processing commands for cont...@bugs.debian.org:
tags 668757 + patch
Bug #668757 [netdisco-backend,netdisco-frontend] netdisco-{back,front}end:
creates system user in /home
Added tag(s) patch.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
668757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668757
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#688413: accountsservice: Makes gnome-shell crash
Package: accountsservice Version: 0.6.21-6 Severity: serious Justification: Must be fixed for wheezy Switching users makes gnome-shell crash with this error: #0 0x7f70c5ea06c9 in g_cancellable_is_cancelled ( cancellable=0x7f70c4a30660) at /tmp/buildd/glib2.0-2.33.12+really2.32.3/./gio/gcancellable.c:296 No locals. #1 0x7f70a7555d86 in on_get_unix_user_finished (object=optimized out, result=0x4f93660, data=0x4e56240) at act-user-manager.c:1028 proxy = optimized out new_session = 0x4e56240 error = 0x0 uid = optimized out #2 0x7f70c5ed93f7 in g_simple_async_result_complete (simple=0x4f93660) at /tmp/buildd/glib2.0-2.33.12+really2.32.3/./gio/gsimpleasyncresult.c:767 current_source = 0x7f70980e4f90 current_context = 0x0 __PRETTY_FUNCTION__ = g_simple_async_result_complete #3 0x7f70c5f3177a in reply_cb (connection=optimized out, res=optimized out, user_data=0x4f93660) at /tmp/buildd/glib2.0-2.33.12+really2.32.3/./gio/gdbusproxy.c:2614 simple = 0x4f93660 value = optimized out error = 0x38cfe60 fd_list = 0x2740a00 This code is introduced by a patch you added: 9001-manage_pending_ck_calls_with_cancellable.patch Obviously something is wrong with the cancellable management, because new_session-cancellable exists but is not a valid GCancellable. I tried with accountsservice 0.6.24 in experimental, but it is much worse since it entirely prevents gnome-shell from starting up. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages accountsservice depends on: ii dbus 1.6.2-2 ii libaccountsservice00.6.21-6 ii libc6 2.13-35 ii libglib2.0-0 2.33.12+really2.32.3-2 ii libpolkit-gobject-1-0 0.105-1 accountsservice recommends no packages. Versions of packages accountsservice suggests: ii gnome-control-center 1:3.4.2-2 -- no debconf information -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655804: Patch
X-Debbugs-CC: Jakub Wilk jw...@debian.org Here's a patch that follows the first piece of Jakub's advice. diff -u update-manager-0.200.5/debian/changelog update-manager-0.200.5/debian/changelog --- update-manager-0.200.5/debian/changelog +++ update-manager-0.200.5/debian/changelog @@ -1,3 +1,11 @@ +update-manager (0.200.5-2+nmu1) unstable; urgency=low + + * Non-maintainer upload. + * Avoid manipulating the documentation build directory to not step on +sphinx's toes (closes: #655804). + + -- Marcin Owsiany porri...@debian.org Sat, 22 Sep 2012 15:34:35 +0100 + update-manager (0.200.5-2) unstable; urgency=medium * locale.format_suffix.patch: replace locale.format() calls with diff -u update-manager-0.200.5/debian/rules update-manager-0.200.5/debian/rules --- update-manager-0.200.5/debian/rules +++ update-manager-0.200.5/debian/rules @@ -14,11 +14,12 @@ -mkdir -p $(CURDIR)/doc/source/_static $(MAKE) -C $(CURDIR)/doc html mkdir -p $(CURDIR)/debian/tmp/usr/share/doc/update-manager-doc - -rm $(CURDIR)/doc/build/html/_static/jquery.js - ln -s /usr/share/javascript/jquery/jquery.js \ - $(CURDIR)/doc/build/html/_static/jquery.js cp -r $(CURDIR)/doc/build/html \ $(CURDIR)/debian/tmp/usr/share/doc/update-manager-doc +# Avoid manipulating the documentation build directory: Bug#655804 + -rm $(CURDIR)/debian/tmp/usr/share/doc/update-manager-doc/html/_static/jquery.js + ln -s /usr/share/javascript/jquery/jquery.js \ + $(CURDIR)/debian/tmp/usr/share/doc/update-manager-doc/html/_static/jquery.js # copied from CDBS; I cannot use gnome.mk, for it includes autotools.mk # although this package does not use autotools; the build, thus, fails. only in patch2: unchanged: --- update-manager-0.200.5.orig/debian/pycompat +++ update-manager-0.200.5/debian/pycompat @@ -0,0 +1 @@ +2 The pycompat thing was added automatically by the build AFAICT. -- Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/ GnuPG: 2048R/02F946FC 35E9 1344 9F77 5F43 13DD 6423 DBF4 80C6 02F9 46FC -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 655804
Processing commands for cont...@bugs.debian.org: tags 655804 + patch Bug #655804 [src:update-manager] update-manager: FTBFS: Error: `/usr/share/sphinx/themes/basic/static/jquery.js` and `/build/update-manager-OCasPf/update-manager-0.200.5/doc/build/html/_static/jquery.js` are the same file Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 655804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655804 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#678140: Two tiff issues: CVE-2012-2113 / CVE-2012-2088
Lee Garrett lgarr...@programmfabrik.de wrote:
AFAICS stable is still affected by both CVEs. Can you confirm this?
Patches are available in the Ubuntu natty version of libtiff4.
Yes, I can confirm. Sorry about that. I checked against the natty
package, and there are quite a few CVEs that we seem to have missed. I
think probably these were not affected in the version in unstable, and I
lost track of not having backported or considered them for stable. I
have a new version of tiff (tiff-3.9.4-5+squeeze5) built against squeeze
that is ready to upload. I've attached a patch from squeeze4 to
squeeze5. The only changes were either adding some new patches (the
ones mentioned in the changelog) or replacing some old patches that were
affected by the new ones. This happened for two patches, and I checked
the diffs to make sure the changes were actually the same. As always, I
didn't touch any other aspect of the packages. I literally just
replaced the patch files and the series file and updated the changelog.
Please let me know whether I should do the upload or whether you will
prepare a package for stable-security based on the attached patch.
Thanks!
--
Jay Berkenbilt q...@debian.org
diff -urN ../tiff-3.9.4-5+squeeze4/debian/changelog ./debian/changelog
--- ../tiff-3.9.4-5+squeeze4/debian/changelog 2012-04-02 11:41:13.0 -0400
+++ ./debian/changelog 2012-09-22 12:05:39.852315189 -0400
@@ -1,3 +1,18 @@
+tiff (3.9.4-5+squeeze5) stable-security; urgency=high
+
+ * Added several additional security patches taken from the Ubuntu Natty
+(11.04) tiff package.
+
+CVE-2010-2482
+CVE-2010-2595
+CVE-2010-2597
+CVE-2010-2630
+CVE-2010-4665
+CVE-2012-2113
+CVE-2012-3401
+
+ -- Jay Berkenbilt q...@debian.org Sat, 22 Sep 2012 11:51:18 -0400
+
tiff (3.9.4-5+squeeze4) stable-security; urgency=high
* CVE-2012-1173
diff -urN ../tiff-3.9.4-5+squeeze4/debian/patches/CVE-2010-2482.patch ./debian/patches/CVE-2010-2482.patch
--- ../tiff-3.9.4-5+squeeze4/debian/patches/CVE-2010-2482.patch 1969-12-31 19:00:00.0 -0500
+++ ./debian/patches/CVE-2010-2482.patch 2011-03-03 11:16:07.0 -0500
@@ -0,0 +1,52 @@
+Description: fix denial of service via invalid td_stripbytecount field
+Origin: upstream, r1.24.2.7, r1.14.2.5
+Bug: http://bugzilla.maptools.org/show_bug.cgi?id=1996
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/597246
+
+Index: tiff-3.9.4/libtiff/tif_ojpeg.c
+===
+--- tiff-3.9.4.orig/libtiff/tif_ojpeg.c 2011-03-03 10:40:33.0 -0500
tiff-3.9.4/libtiff/tif_ojpeg.c 2011-03-03 10:41:33.0 -0500
+@@ -1918,8 +1918,14 @@
+ {
+ if (sp-in_buffer_file_pos=sp-file_size)
+ sp-in_buffer_file_pos=0;
++ else if (sp-tif-tif_dir.td_stripbytecount==NULL)
++ sp-in_buffer_file_togo=sp-file_size-sp-in_buffer_file_pos;
+ else
+ {
++ if (sp-tif-tif_dir.td_stripbytecount == 0) {
++TIFFErrorExt(sp-tif-tif_clientdata,sp-tif-tif_name,Strip byte counts are missing);
++return(0);
++ }
+ sp-in_buffer_file_togo=sp-tif-tif_dir.td_stripbytecount[sp-in_buffer_next_strile];
+ if (sp-in_buffer_file_togo==0)
+ sp-in_buffer_file_pos=0;
+Index: tiff-3.9.4/tools/tiffsplit.c
+===
+--- tiff-3.9.4.orig/tools/tiffsplit.c 2011-03-03 10:41:02.0 -0500
tiff-3.9.4/tools/tiffsplit.c 2011-03-03 10:41:36.0 -0500
+@@ -237,7 +237,10 @@
+ tstrip_t s, ns = TIFFNumberOfStrips(in);
+ uint32 *bytecounts;
+
+- TIFFGetField(in, TIFFTAG_STRIPBYTECOUNTS, bytecounts);
++ if (!TIFFGetField(in, TIFFTAG_STRIPBYTECOUNTS, bytecounts)) {
++ fprintf(stderr, tiffsplit: strip byte counts are missing\n);
++ return (0);
++ }
+ for (s = 0; s ns; s++) {
+ if (bytecounts[s] (uint32)bufsize) {
+ buf = (unsigned char *)_TIFFrealloc(buf, bytecounts[s]);
+@@ -267,7 +270,10 @@
+ ttile_t t, nt = TIFFNumberOfTiles(in);
+ uint32 *bytecounts;
+
+- TIFFGetField(in, TIFFTAG_TILEBYTECOUNTS, bytecounts);
++ if (!TIFFGetField(in, TIFFTAG_TILEBYTECOUNTS, bytecounts)) {
++ fprintf(stderr, tiffsplit: tile byte counts are missing\n);
++ return (0);
++ }
+ for (t = 0; t nt; t++) {
+ if (bytecounts[t] (uint32) bufsize) {
+ buf = (unsigned char *)_TIFFrealloc(buf, bytecounts[t]);
diff -urN ../tiff-3.9.4-5+squeeze4/debian/patches/CVE-2010-2595.patch ./debian/patches/CVE-2010-2595.patch
--- ../tiff-3.9.4-5+squeeze4/debian/patches/CVE-2010-2595.patch 1969-12-31 19:00:00.0 -0500
+++ ./debian/patches/CVE-2010-2595.patch 2011-03-03 11:18:28.0 -0500
@@ -0,0 +1,31 @@
+Description: fix denial of service via invalid ReferenceBlackWhite values
+Origin: upstream, libtiff/tif_color.c r1.12.2.2
+Bug: http://bugzilla.maptools.org/show_bug.cgi?id=2208
+
+Index: tiff-3.9.4/libtiff/tif_color.c
+===
Bug#688433: biomaj: modifies conffiles (policy 10.7.3): /etc/biomaj/db_properties/global.properties
Package: biomaj Version: 1.2.0-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /usr/share/biomaj/bin/env.sh /etc/biomaj/db_properties/global.properties cheers, Andreas biomaj_1.2.0-7.log.gz Description: GNU Zip compressed data
Bug#688435: dotlrn: modifies conffiles (policy 10.7.3): /etc/dotlrn/config.tcl
Package: dotlrn Version: 2.5.0+dfsg-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/dotlrn/config.tcl cheers, Andreas dotlrn_2.5.0+dfsg-8.log.gz Description: GNU Zip compressed data
Bug#688436: ampache: postrm remove deletes configuration and logfiles
Package: ampache Version: 3.6-git408e713+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed that your package deletes conffiles and logfiles during postrm purge. This is a violation of policy 10.7.3 and 10.8. dpkg will take care of deleting conffiles during purge - there is no need to handle /etc/cron.daily/ampache /etc/logrotate.d/ampache manually. Cheers, Andreas ampache_3.6-git408e713+dfsg-2.log.gz Description: GNU Zip compressed data
Bug#688233: /usr/bin/uim-module-manager: modifies conffiles (policy 10.7.3): /etc/uim/installed-modules.scm, /etc/uim/loader.scm
Hi Dai, I had a short glance over your patch. You probably should add to uim-data Breaks: uim-MODULE ( FIXEDVERSION~) for all module packages that used the path /etc/uim You need to get rid of the conffiles that are still known to dpkg after an upgrade. dpkg-maintscript-helper may help you with this. Therefore you should move the moving part to the preinst and call dpkg-maintscript-helper after your manual moving to /var (or better let dh_installdeb generate the code, you just need to add something to debian/uim-data.maintscript). Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681680: mediathekview: finds only 1376 out of 57537 movies
Hi Markus, On Fri, Sep 14, 2012 at 12:56:24AM +0200, Markus Koschany wrote: 647...@bugs.debian.org, b.tho...@fh-muenster.de, christoph.mar...@uni-mainz.de Bcc: Subject: Re: Bug#681680: mediathekview: finds only 1376 out of 57537 movies Reply-To: In-Reply-To: 20120913211149.ga25...@bogon.sigxcpu.org On Thu, 13. Sep 23:11 Guido Günther a...@sigxcpu.org wrote: Any news on getting this one uploaded? If the maintainer is inacitive I'd be happy to review the package and NMU. Cheers, -- Guido Hello Guido! I'm still waiting for someone to review my package. So i'm glad that you want to help. Please go ahead. Christoph Martin had sponsored MediathekView in the past and he suggested that he intended to test the package. That was three weeks ago. I guess he is busy at the moment. B.Thomas or Thomas B. is the maintainer of Mediathekview but also busy. He indicated that someone else should take responsibility for MV. [1] There are three options and i'm not sure which one is the best. 1. Uploading 2.6.1 to unstable and hoping that the release team will unblock it for Testing. Then uploading 3.0.0 to experimental. 2. Removing MV completely from wheezy and uploading 3.0.0 to unstable. I'd go for this one. Everything besides 3.0 doesn't seem to work that well ant I tthnk it's hard to maintain 2.6 for the next years. We can then ask for a freeze exception for 3.0 - if it doesn't happen so be it. Can you point me to your current 3.0.0 package for ease of reviewing? Cheers, -- Guido 3. Uploading 3.0.0 to unstable in the hope that it gets unblocked. Option 3 is rather unlikely. I'm not sure whether version 2.6.1 is something someone might use for the next three years. It's functional but outdated. But perhaps it's better than nothing. So far Regards Markus [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681680#42 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: user debian...@lists.debian.org, usertagging 688351, found 657146 in 7.2.6+dfsg-14, affects 677065 ...
Processing commands for cont...@bugs.debian.org: user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was deb...@abeckmann.de). usertags 688351 piuparts There were no usertags set. Usertags are now: piuparts. found 657146 7.2.6+dfsg-14 Bug #657146 [tango-common] tango-common: unowned files after purge (policy 6.8, 10.8) Marked as found in versions tango/7.2.6+dfsg-14. affects 677065 + ndoutils-nagios3-mysql Bug #677065 [ndoutils-common] ndoutils-common: fails to purge - command ucf in postrm not found Added indication that 677065 affects ndoutils-nagios3-mysql reassign 687196 release.debian.org Bug #687196 [eucalyptus] eucalyptus: Please unblock Eucalyptus Bug reassigned from package 'eucalyptus' to 'release.debian.org'. No longer marked as found in versions 3.1.0-8. Ignoring request to alter fixed versions of bug #687196 to the same values previously set affects 688233 + uim-hangul Bug #688233 [uim-utils] /usr/bin/uim-module-manager: modifies conffiles (policy 10.7.3): /etc/uim/installed-modules.scm, /etc/uim/loader.scm Added indication that 688233 affects uim-hangul thanks Stopping processing here. Please contact me if you need assistance. -- 657146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657146 677065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677065 687196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687196 688233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688233 688351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688351 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#688441: 3.2.0 ext3 and ext4 failing in Xen VM domU
Package: linux-image-3.2.0-3-amd64 Version: 3.2.21-3 Severity: serious Leaves root filesystem in read-only state, some users have reported root filesystem corruption (see below), so I have marked this as serious I have a dom0 running Xen (standard squeeze installation) and several domU VM instances I've upgraded one of those domU VMs from squeeze to wheezy. Kernel 3.2.0 was installed as part of the upgrade. Access to all filesystems has been unstable. They often come up in read-only mode. I've discovered the same problem discussed here: http://askubuntu.com/questions/126631/why-do-i-get-disk-i-o-errors-booting-the-3-2-kernel-on-a-xen-vps-server The discussion ends with a suggestion to add barrier=0 - that seems to fix the problem for me (so far). My dom0 system doesn't report any errors with the disk. If I shut down the domU and fsck the filesystems from the dom0, they all appear perfectly healthy. [4.787445] EXT3-fs (xvda2): using internal journal [4.940826] loop: module loaded [6.296639] blkfront: barrier: empty write xvda3 op failed [6.296654] blkfront: xvda3: barrier or flush: disabled [6.388461] blkfront: barrier: empty write xvda1 op failed [6.388472] blkfront: xvda1: barrier or flush: disabled [8.843840] kjournald starting. Commit interval 5 seconds [8.881033] EXT3-fs (xvda1): using internal journal [8.881046] EXT3-fs (xvda1): mounted filesystem with ordered data mode [8.916063] kjournald starting. Commit interval 5 seconds [8.948698] EXT3-fs (xvda3): using internal journal [8.948722] EXT3-fs (xvda3): mounted filesystem with ordered data mode [ 10.152007] blkfront: barrier: empty write xvda2 op failed [ 10.152023] blkfront: xvda2: barrier or flush: disabled [ 10.152035] end_request: I/O error, dev xvda2, sector 633144 [ 10.152043] end_request: I/O error, dev xvda2, sector 633144 [ 10.152050] Buffer I/O error on device xvda2, logical block 79143 [ 10.152056] lost page write due to I/O error on xvda2 [ 10.152085] Aborting journal on device xvda2. [ 10.305595] EXT3-fs (xvda2): error: ext3_journal_start_sb: Detected aborted journal [ 10.305617] EXT3-fs (xvda2): error: remounting filesystem read-only -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683695: libdrm-nouveau1a: when using Nvidia Gtx 550 Ti card boot stops at populating /dev
On Sat, Sep 22, 2012 at 1:04 AM, Dick Thomas wrote: still a noob to debian so daren't do that yet as I don't want to get flamed but thank you for the suggestions :) Flaming is somewhat less prevalent in debian nowadays, so please try to not worry about that. Would you mind at least trying the 3.5 kernel from the experimental repository so we can confirm that would be a solution to the problem? Thanks, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 687818
Processing commands for cont...@bugs.debian.org: tags 687818 + pending Bug #687818 [tomcat6] tomcat6: postinst modifies conffile /etc/logrotate.d/tomcat6 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 687818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687818 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: Set bug as found in the release
Processing commands for cont...@bugs.debian.org: found 688151 2.0.0rc2-2 Bug #688151 [fwknop] [CVE 2012-4434, 4435, 4436] fwknop: Multiple security issues There is no source info for the package 'fwknop' at version '2.0.0rc2-2' with architecture '' Unable to make a source version for version '2.0.0rc2-2' Marked as found in versions 2.0.0rc2-2. found 688151 2.0.2-1 Bug #688151 [fwknop] [CVE 2012-4434, 4435, 4436] fwknop: Multiple security issues There is no source info for the package 'fwknop' at version '2.0.2-1' with architecture '' Unable to make a source version for version '2.0.2-1' Marked as found in versions 2.0.2-1. thanks Stopping processing here. Please contact me if you need assistance. -- 688151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688151 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#688268: marked as done (Kernel Panic -- how to continue)
Your message dated Sat, 22 Sep 2012 19:18:40 + with message-id e1tfvds-ek...@franck.debian.org and subject line Bug#688268: fixed in kfreebsd-9 9.0-6 has caused the Debian Bug report #688268, regarding Kernel Panic -- how to continue 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.) -- 688268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kfreebsd-image-9.0-2-amd64 Version: 9.0-6 Severity: serious Hi! Christoph Egger christ...@debian.org writes: Steven Chamberlain ste...@pyro.eu.org writes: On 18/09/12 17:11, Christoph Egger wrote: We're seeing a kernel panic [0] here (triggered be calling `pfctl -f somefile`) quite deterministically. This is happeniong on a Debian 9.0-2 Kernel + if_bce. I'd like to get this fixed so I'm curious on how to best continue. I looked up pfr_update_stats in http://fxr.watson.org/fxr/ident?v=FREEBSD9 and then had a look at the upstream SVN log for the source file. I think I got lucky. I notice this recent fix to initialise a variable used in that function, so this is probably it: http://svnweb.freebsd.org/base?view=revisionamp;sortby=revamp;sortdir=downamp;revision=236364 This bugfix was accepted in 9.1-RC1 but hopefully we can apply it to 9.0. This sounds perfectly in line with one of the other admins observing this to somehow go away by dropping the counters from some table in the pf config. I'll try to get a patched kernel and see if it goes away. This patch indeed fixes the panic. It applies cleanly also on our 9.0 kernel. Please consider adding this patch. Regards Christoph [0] http://random.christoph-egger.org/bce_pf_bt.jpg -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kfreebsd-image-9.0-2-amd64 depends on: ii devd 9.0+ds1-7 ii freebsd-utils 9.0+ds1-7 ii kbdcontrol 9.0+ds1-7 ii kldutils 9.0+ds1-7 kfreebsd-image-9.0-2-amd64 recommends no packages. kfreebsd-image-9.0-2-amd64 suggests no packages. ---End Message--- ---BeginMessage--- Source: kfreebsd-9 Source-Version: 9.0-6 We believe that the bug you reported is fixed in the latest version of kfreebsd-9, 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 688...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Egger christ...@debian.org (supplier of updated kfreebsd-9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 22 Sep 2012 11:32:52 -0700 Source: kfreebsd-9 Binary: kfreebsd-source-9.0 kfreebsd-headers-9.0-2 kfreebsd-image-9.0-2-686-smp kfreebsd-image-9-686-smp kfreebsd-headers-9.0-2-686-smp kfreebsd-headers-9-686-smp kfreebsd-image-9.0-2-amd64 kfreebsd-image-9-amd64 kfreebsd-headers-9.0-2-amd64 kfreebsd-headers-9-amd64 kernel-image-9.0-2-amd64-di nic-modules-9.0-2-amd64-di nic-wireless-modules-9.0-2-amd64-di nic-shared-modules-9.0-2-amd64-di serial-modules-9.0-2-amd64-di ppp-modules-9.0-2-amd64-di cdrom-modules-9.0-2-amd64-di scsi-core-modules-9.0-2-amd64-di scsi-modules-9.0-2-amd64-di scsi-extra-modules-9.0-2-amd64-di plip-modules-9.0-2-amd64-di floppy-modules-9.0-2-amd64-di loop-modules-9.0-2-amd64-di ipv6-modules-9.0-2-amd64-di nls-core-modules-9.0-2-amd64-di ext2-modules-9.0-2-amd64-di isofs-modules-9.0-2-amd64-di ntfs-modules-9.0-2-amd64-di reiserfs-modules-9.0-2-amd64-di xfs-modules-9.0-2-amd64-di fat-modules-9.0-2-amd64-di zfs-modules-9.0-2-amd64-di nfs-modules-9.0-2-amd64-di nullfs-modules-9.0-2-amd64-di md-modules-9.0-2-amd64-di parport-modules-9.0-2-amd64-di sata-modules-9.0-2-amd64-di acpi-modules-9.0-2-amd64-di i2c-modules-9.0-2-amd64-di crypto-modules-9.0-2-amd64-di crypto-dm-modules-9.0-2-amd64-di mmc-core-modules-9.0-2-amd64-di mmc-modules-9.0-2-amd64-di sound-modules-9.0-2-amd64-di zlib-modules-9.0-2-amd64-di kfreebsd-image-9.0-2-486 kfreebsd-image-9-486 kfreebsd-headers-9.0-2-486
Bug#650454: marked as done (checkgmail: keeps popping up login window but fails to log in)
Your message dated Sat, 22 Sep 2012 19:32:04 + with message-id e1tfvqq-00031e...@franck.debian.org and subject line Bug#650454: fixed in checkgmail 1.13+svn43-2+squeeze0.1 has caused the Debian Bug report #650454, regarding checkgmail: keeps popping up login window but fails to log in 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.) -- 650454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: checkgmail Version: 1.13+svn43-2 Severity: grave Justification: renders package unusable Dear Maintainer, checkgmail appears unusable at present, since it fails to log in. Sadly I do not know when this problem appeared since it has been a while since I last used checkgmail. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages checkgmail depends on: ii libcrypt-blowfish-perl2.12-1+b2 ii libcrypt-ssleay-perl 0.57-2+b3 ii libfreezethaw-perl0.5001-1 ii libgtk2-perl 2:1.223-1+b2 ii libgtk2-trayicon-perl 0.06-1+b2 ii libgtk2.0-0 2.24.8-2 ii libwww-perl 6.03-1 ii libxml-simple-perl2.18-3 ii perl [libcompress-zlib-perl] 5.14.2-6 Versions of packages checkgmail recommends: ii libcrypt-simple-perl 0.06-6 checkgmail suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: checkgmail Source-Version: 1.13+svn43-2+squeeze0.1 We believe that the bug you reported is fixed in the latest version of checkgmail, 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 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Nieder jrnie...@gmail.com (supplier of updated checkgmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 19 Aug 2012 17:28:49 -0700 Source: checkgmail Binary: checkgmail Architecture: source all Version: 1.13+svn43-2+squeeze0.1 Distribution: stable Urgency: low Maintainer: Sandro Tosi mo...@debian.org Changed-By: Jonathan Nieder jrnie...@gmail.com Description: checkgmail - alternative Gmail Notifier for Linux via Atom feeds Closes: 650454 Changes: checkgmail (1.13+svn43-2+squeeze0.1) stable; urgency=low . * Non-maintainer upload * debian/patches/60_bts650454_send_galx_as_cookie.dpatch - fix auth problem with GMail by passing GALX in the cookie; thanks to Johan Sandblom for the report; Closes: #650454 Checksums-Sha1: bc22448705bd9d72e9041093db80ff5851b08657 1741 checkgmail_1.13+svn43-2+squeeze0.1.dsc 4c10b96cd511c6b368cfd3adb2e4a872dc88aac8 11231 checkgmail_1.13+svn43-2+squeeze0.1.diff.gz 5791ca7cadce79b9f00adb440843c10b78304181 69816 checkgmail_1.13+svn43-2+squeeze0.1_all.deb Checksums-Sha256: 7ffc49dc86cfd5f2e541f2d8ec91c9713b8d05f662f7ca9e136bfc29982b9366 1741 checkgmail_1.13+svn43-2+squeeze0.1.dsc c70bcc704fc3c2d0050c23cf657c375b353902487d47faa83da8b9b143d4a662 11231 checkgmail_1.13+svn43-2+squeeze0.1.diff.gz 657be732f293bfde2c62e18b47afe6f2e8c76013c684fa620d07a9509fa2cbb4 69816 checkgmail_1.13+svn43-2+squeeze0.1_all.deb Files: ac9b2d46aef4def686cd08950afad6dd 1741 mail optional checkgmail_1.13+svn43-2+squeeze0.1.dsc 9d7a485acb191bc02113f60fda2867e0 11231 mail optional checkgmail_1.13+svn43-2+squeeze0.1.diff.gz 144a3ce1a79b4bbab5e7a2eed9d2f211 69816 mail optional checkgmail_1.13+svn43-2+squeeze0.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQXcDHAAoJELgqIXr9/gnyTlwP/3dbgL+JhuGPpbl9OUYO+I+K vb+NQCy2a46PcX3hiANIobscJh5soKG+NW5gbWi3rvF1fbzP4ziM8NeRPFiiOdTG hoK213lJGRS5OP+fJggQr7okAR6adtsBZKwghUuNW8nnrqlV0KjuqbfqcZJx00gQ mioUOGhwQBtTZQg7InzBQoDXHZRVP1fcW0fFcNmvhlU/p4MSGm/bQijDK2fHykXY 3UWddBptLZJJoPxOsRuvd+/bRCvlHnY0WUOFiuz/OxY2FJy5Z+nS5EIhmScu+Ytg
Bug#688374: gforge-shell-postgresql: postinst fails after cp: target `//etc/nss-pgsql-root.conf' is not a directory
Andreas Beckmann dixit: The first problem was that the database was not reachable, but that didn't cause the postinst to abort ... Oh well, that too. Roland fixed that upstream yesterday, I’ll make a new upload soon then. (To get into non-RC-buggy shape for jessie ;) But really, your piuparts environment seems to be strange, discovering all sorts of weird scenarios. Admittedly, FF is heavy on environmental dependencies/assumptions… bye, //mirabilos -- Natureshadow Dann mach ich git annex copy --to shore und fertig ist das Natureshadow das ist ja viel cooler als ownCloud ... mirabilos sag ich doch Natureshadow ja wieso stimmt das denn immer was du sagst ... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685360: [PATCH 1/1] HID: Fix missing Unifying device issue
On Sat, 22 Sep 2012, Jiri Kosina wrote: This patch fixes an issue introduced after commit 4ea5454203d991ec After that commit, hid-core silently discards any incoming packet that arrives while any hid driver's probe function is being executed. This broke the enumeration process of hid-logitech-dj, that must receive control packets in-band with the mouse and keyboard packets. Discarding mouse or keyboard data at the very begining is usually fine, but it is not the case for control packets. This patch forces a re-enumeration of the paired devices when a packet arrives that comes from an unknown device. Based on a patch originally written by Benjamin Tissoires. Signed-off-by: Nestor Lopez Casado nlopezca...@logitech.com I am now applying it, will be pushing to Linus very soon Now in Linus' tree and marked for stable. Thanks, -- Jiri Kosina SUSE Labs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688436: ampache: postrm remove deletes configuration and logfiles
Package: ampache Version: 3.6-git408e713+dfsg-2 Followup-For: Bug #688436 Andreas, Thanks for the bug report. I have a fixed version of ampache on m.d.n, it can be found at http://mentors.debian.net/debian/pool/main/a/ampache/ampache_3.6-git408e713+dfsg-3.dsc Best regards Charlie Smotherman -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ampache depends on: ii ampache-common 3.6-git408e713+dfsg-2 ii debconf [debconf-2.0] 1.5.46 ii fonts-freefont-ttf [ttf-freefont] 20120503-1 ii libapache2-mod-php55.4.4-7 ii libjs-prototype1.7.0-2 ii libnusoap-php 0.7.3-4 ii libphp-phpmailer 5.1-1 ii libphp-snoopy 1.2.4-2 ii php-gettext1.0.11-1 ii php5 5.4.4-7 ii php5-cli 5.4.4-7 ii php5-mysql 5.4.4-7 ii php5-xmlrpc5.4.4-7 ii ttf-freefont 20120503-1 Versions of packages ampache recommends: pn ampache-themes none ii apache2-mpm-prefork 2.2.22-11 Versions of packages ampache suggests: ii eyed3 0.6.18-1 pn faad none ii mysql-server 5.5.24+dfsg-8 pn php5-gd none pn phpmyadminnone pn vorbis-tools none -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681680: mediathekview: finds only 1376 out of 57537 movies
Hi Markus, Am 11.09.2012 13:28, schrieb Markus Koschany: On 23.08.2012 19:08, Christoph Martin wrote: I could successfully build 2.6.1. I will test it soon. Christoph Hi Christoph i've slightly updated Mediathekview-3.0.0. I removed Anleitung.pdf (included it twice) and switched to Debian's new copyright format. To ease testing i have created an archive with reprepro. I couldn't find any show-stoppers so far. New download location: 2.6.1 dget -x ftp://46.182.19.209/debian/pool/main/m/mediathekview/mediathekview_2.6.1-1.dsc 3.0.0 dget -x ftp://46.182.19.209/debian/pool/main/m/mediathekview/mediathekview_3.0.0-1.dsc Can i assist you with testing or answer any questions? I just hat the time to do some testing with 3.0.0. The first problem I had, is that medithekview wants to execute /usr/share/mediathekview/bin/flv.sh but it is installed in /usr/share/mediathekview/. So you either have to change ./src/mediathek/tool/GuiFunktionenProgramme.java or ./debian/mediathekview.install Christoph signature.asc Description: OpenPGP digital signature
Bug#682013: NFS error on FAI client
I just wanted to mention that I was also having problems with failed fai-setup and the patches resolved the problem for me, but I then I got the dracut nfs error when attempting to boot a client. Chrooting into nfsroot and trying to regenerate the initrd with the nfs module fails for me because it was trying to load modules from my host's kernel version (/lib/modules/2.6.32-5-amd64), but fai is using 3.2.0-3-amd64. To resolve I made a symbolic link pointing /lib/modules/2.6.32-5-amd64 to /lib/modules/3.2.0-3-amd64 regenerated the initrd and then copied it over to /srv/tftp/fai/ From there I was able to boot the client without the nfs error. If anyone else is having the same problem I hope this helps. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612918: Bug#688084: Please consider tagging #612918 wheezy-ignore
On Sat, Sep 22, 2012 at 2:31 PM, Jonathan Nieder wrote: Hi Michael, Michael Gilbert wrote: Bug #612918 involves a violation of the FHS (using a file in /etc as a state file), thus violating debian policy. Apparently there was going to be some involved upstream work to correct the problem, but after over a year, that appears not to have happened. Given that and the fact that practically speaking, its only really problematic in a read-only /etc environment, and users in that situation can choose a different network manager anyway, I think it would be appropriate to ignore it for wheezy until that upstream work actually gets done. Wouldn't an alternative be to simply use a symlink or patch to move wicd's list of networks under /var? That's an interesting thought, and apparently there is already some precedent for that. For example: $ ls -l /etc/xdg/menus/debian-menu.menu lrwxrwxrwx 1 root root 40 Jan 17 2010 /etc/xdg/menus/debian-menu.menu - /var/lib/menu-xdg/menus/debian-menu.menu Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 688441 is important
Processing commands for cont...@bugs.debian.org: severity 688441 important Bug #688441 [linux-image-3.2.0-3-amd64] 3.2.0 ext3 and ext4 failing in Xen VM domU Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 688441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688441 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#681680: mediathekview: finds only 1376 out of 57537 movies
Hi Guido and Christoph, On Sat, 22. Sep 19:19 Guido Günther a...@sigxcpu.org wrote: 2. Removing MV completely from wheezy and uploading 3.0.0 to unstable. I'd go for this one. Everything besides 3.0 doesn't seem to work that well ant I tthnk it's hard to maintain 2.6 for the next years. We can then ask for a freeze exception for 3.0 - if it doesn't happen so be it. That sounds reasonable. Can you point me to your current 3.0.0 package for ease of reviewing? I've uploaded the current 3.0.0 package to mentors.debian.net. dget -x http://mentors.debian.net/debian/pool/main/m/mediathekview/mediathekview_3.0.0-1.dsc I have also changed the install path of the flv.sh helper script to /usr/share/mediathekview/bin. My initial intention was to create a better Programmset for Linux and eventually to get completely rid of flv.sh. One can also change the path to flv.sh under Programmset. Each of these sets is basically a xml file which can be downloaded from the official homepage. In fact the flv.sh file isn't included in the sources of version 3.0.0 and has been added later. Thank you both. I'm ready to get this bug fixed. Regards, Markus signature.asc Description: Digital signature
Bug#680467: marked as done (Versioned Breaks (and Recommends) on lilo is missing epoch)
Your message dated Sun, 23 Sep 2012 02:47:10 + with message-id e1tfcdu-ul...@franck.debian.org and subject line Bug#680467: fixed in linux-2.6 2.6.32-46 has caused the Debian Bug report #680467, regarding Versioned Breaks (and Recommends) on lilo is missing epoch 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.) -- 680467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux-2.6 Version: 2.6.32-45 Severity: serious Jakub Wilk spotted that the minimum version number specified for lilo (22.8-8.2~) does not include the epoch (1:), which means that we don't actually require it to be upgraded and #593683 was never fully fixed. Ben. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-46 We believe that the bug you reported is fixed in the latest version of linux-2.6, 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 680...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 23 Sep 2012 04:22:37 +0900 Source: linux-2.6 Binary: linux-tools-2.6.32 linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-5 linux-base linux-libc-dev linux-headers-2.6.32-5-all linux-headers-2.6.32-5-all-alpha linux-headers-2.6.32-5-common linux-image-2.6.32-5-alpha-generic linux-headers-2.6.32-5-alpha-generic linux-image-2.6.32-5-alpha-smp linux-headers-2.6.32-5-alpha-smp linux-image-2.6.32-5-alpha-legacy linux-headers-2.6.32-5-alpha-legacy linux-headers-2.6.32-5-all-amd64 linux-image-2.6.32-5-amd64 linux-headers-2.6.32-5-amd64 linux-image-2.6.32-5-amd64-dbg linux-headers-2.6.32-5-common-openvz linux-image-2.6.32-5-openvz-amd64 linux-headers-2.6.32-5-openvz-amd64 linux-image-2.6.32-5-openvz-amd64-dbg linux-headers-2.6.32-5-common-vserver linux-image-2.6.32-5-vserver-amd64 linux-headers-2.6.32-5-vserver-amd64 linux-image-2.6.32-5-vserver-amd64-dbg linux-headers-2.6.32-5-common-xen linux-image-2.6.32-5-xen-amd64 linux-headers-2.6.32-5-xen-amd64 linux-image-2.6.32-5-xen-amd64-dbg xen-linux-system-2.6.32-5-xen-amd64 linux-headers-2.6.32-5-all-armel linux-image-2.6.32-5-iop32x linux-headers-2.6.32-5-iop32x linux-image-2.6.32-5-ixp4xx linux-headers-2.6.32-5-ixp4xx linux-image-2.6.32-5-kirkwood linux-headers-2.6.32-5-kirkwood linux-image-2.6.32-5-orion5x linux-headers-2.6.32-5-orion5x linux-image-2.6.32-5-versatile linux-headers-2.6.32-5-versatile linux-headers-2.6.32-5-all-hppa linux-image-2.6.32-5-parisc linux-headers-2.6.32-5-parisc linux-image-2.6.32-5-parisc-smp linux-headers-2.6.32-5-parisc-smp linux-image-2.6.32-5-parisc64 linux-headers-2.6.32-5-parisc64 linux-image-2.6.32-5-parisc64-smp linux-headers-2.6.32-5-parisc64-smp linux-headers-2.6.32-5-all-i386 linux-image-2.6.32-5-486 linux-headers-2.6.32-5-486 linux-image-2.6.32-5-686 linux-headers-2.6.32-5-686 linux-image-2.6.32-5-686-bigmem linux-headers-2.6.32-5-686-bigmem linux-image-2.6.32-5-686-bigmem-dbg linux-image-2.6.32-5-openvz-686 linux-headers-2.6.32-5-openvz-686 linux-image-2.6.32-5-openvz-686-dbg linux-image-2.6.32-5-vserver-686 linux-headers-2.6.32-5-vserver-686 linux-image-2.6.32-5-vserver-686-bigmem linux-headers-2.6.32-5-vserver-686-bigmem linux-image-2.6.32-5-vserver-686-bigmem-dbg linux-image-2.6.32-5-xen-686 linux-headers-2.6.32-5-xen-686 linux-image-2.6.32-5-xen-686-dbg xen-linux-system-2.6.32-5-xen-686 linux-headers-2.6.32-5-all-ia64 linux-image-2.6.32-5-itanium linux-headers-2.6.32-5-itanium linux-image-2.6.32-5-mckinley linux-headers-2.6.32-5-mckinley
