Bug#701944: emacs23 fails to install due to /etc/emacs23 does exist for byte-compiling

2013-03-01 Thread Sven Joachim
On 2013-03-01 03:25 +0100, Daniel Dickinson wrote:

 Package: emacs23
 Version: 23.4+1-4
 Severity: serious
 Justification: broken install

 AIUI a package failing to install just because other packages are
 present is RC...or maybe it's the breaking package that's RC, however
 it's emacs23 that fails to install, the other package installs just
 fine without emacs present.  In any event I see:

 [snip]
 Install ccrypt for emacs23
 Install/ccrypt: Handling install for emacsen flavor emacs23
 Warning: List directory '/etc/emacs23' does not exist.
 Opening directory: No such file or directory, /etc/emacs23/site-start.d

That's the problem, /etc/emacs23/site-start.d is shipped in
emacs23-common and has somehow gone AWOL on your system.  You need to
figure out how that happened.

 ERROR: install script from ccrypt package failed
 dpkg: error processing emacs23 (--configure):
  subprocess installed post-installation script returned error exit status 1

 It would appear having ccrypt installed before emacs23 doesn't work.

Worked for me, it seems that some other package or script removed the
directory.  Reinstalling emacs23-common should bring it back.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701953: initramfs-tools: Missing modules prevent passphrase entry with usb keyboard

2013-03-01 Thread Bjørn Mork
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au writes:

 Package: initramfs-tools
 Version: 0.109
 Severity: critical
 Justification: breaks the whole system

Others will have to decide on that, but it seems a bit high to me. This
is an experimental kernel and you do hopefully not try to install it
without keeping a working version as well?


 I have a usb keyboard attached to a system with an unencrypted /boot and a
 LUKS-encrypted partition (LVM physical volume) containing the other
 filesystems. Today I installed linux-image-3.8-trunk-amd64
 (3.8-1~experimental.1). initramfs-tools created a corresponding initrd, as
 expected. Booting this kernel/initrd in grub2 resulted in a plymouth 
 passphrase
 entry screen, but a usb keyboard that did not work in any port. All keyboard
 lights were off. The system was thus unbootable without a non-usb keyboard
 (hence critical severity). Without a non-usb keyboard or backup grub entry 
 (3.7
 kernel with working initrd), I would have been unable to access my system
 without rescue media.

 This is a regression from the behaviour of initramfs-tools with 
 linux-image-3.7
 -trunk-amd64 (3.7.8-1~experimental.1).

 The failure appears identical to this:
 http://linux-kernel.2935.n7.nabble.com/PROBLEM-3-8-0-rc4-keyboard-failure-at-
 boot-tp585937p587518.html

 Workaround is to add the following modules to /etc/initramfs-tools/modules, as
 described in the link above:

 ehci_pci

Right.  This is quite possibly a result of this bug:
http://bugs.debian.org/700572


Bjørn


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701868: [Pkg-openssl-devel] Bug#701868: cannot connect to IRC server

2013-03-01 Thread Marcus Better

Do you know what IRC software is being used, and with which
library it links?

InspIRCd-1.1.22+Azeitao

So can you try with export OPENSSL_ia32cap=~0x202?

Yes, that fixes it.



--
Cheers,
Marcus


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701967: 7.0~rc1 release

2013-03-01 Thread Daniel Baumann
Package: debian-live
Severity: serious
Block -1 by 700798
Block -1 by 700797
Block -1 by 700798
Block -1 by 700800

pseudo-bug to track progress or lack thereof.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701134: php-soap: directory vs. symlink

2013-03-01 Thread Prach Pongpanich
tags 701134 + patch
thanks

Hello maintainer,

I have prepared a patch which solves the this bug.

php-pear:

usr/share/php/doc - ../doc/php-pear/PEAR
usr/share/php/../doc/php-pear - php5-common


Regards,

-- 
 ปรัชญ์ พงษ์พานิช
 Prach Pongpanich

 http://prach-public.blogspot.com


fix_701134.patch
Description: Binary data


Processed: Re: php-soap: directory vs. symlink

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 701134 + patch
Bug #701134 [php-soap] php-soap: directory vs. symlink conflict: 
/usr/share/php/doc
Added tag(s) patch.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
701134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701134
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: debian-live

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 Block 701967 by 700798
Bug #701967 [debian-live] 7.0~rc1 release
701967 was not blocked by any bugs.
701967 was not blocking any bugs.
Added blocking bug(s) of 701967: 700798
 Block 701967 by 700797
Bug #701967 [debian-live] 7.0~rc1 release
701967 was blocked by: 700798
701967 was not blocking any bugs.
Added blocking bug(s) of 701967: 700797
 Block 701967 by 700798
Bug #701967 [debian-live] 7.0~rc1 release
701967 was blocked by: 700798 700797
701967 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #701967 to the same blocks 
previously set
 Block 701967 by 700800
Bug #701967 [debian-live] 7.0~rc1 release
701967 was blocked by: 700798 700797
701967 was not blocking any bugs.
Added blocking bug(s) of 701967: 700800
 Block 701967 by 701969
Bug #701967 [debian-live] 7.0~rc1 release
701967 was blocked by: 700798 700797 700800
701967 was not blocking any bugs.
Added blocking bug(s) of 701967: 701969
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
701967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701967
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: debian-live

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 Block 701967 by 700796
Bug #701967 [debian-live] 7.0~rc1 release
701967 was blocked by: 700798 700797 700800 701969
701967 was not blocking any bugs.
Added blocking bug(s) of 701967: 700796
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
701967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701967
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: found 698916 in 3.4.2+dfsg-1

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 found 698916 3.4.2+dfsg-1
Bug #698916 {Done: Raphaël Hertzog hert...@debian.org} [wordpress] wordpress: 
CVE-2013-0235: pingback port scanning issue fixed in 3.5.1
Bug #698926 {Done: Raphaël Hertzog hert...@debian.org} [wordpress] wordpress: 
CVE-2013-0235: pingback port scanning issue fixed in 3.5.1
Bug #698928 {Done: Raphaël Hertzog hert...@debian.org} [wordpress] wordpress: 
CVE-2013-0235: pingback port scanning issue fixed in 3.5.1
Marked as found in versions wordpress/3.4.2+dfsg-1.
Marked as found in versions wordpress/3.4.2+dfsg-1.
Marked as found in versions wordpress/3.4.2+dfsg-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
698916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698916
698926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698926
698928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698928
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#701945: marked as done (ccrypt fails to install with emac23 due to /etc/emacs23/site-start.d does not exist)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 10:32:12 +0100
with message-id 87hakv5uub@turtle.gmx.de
and subject line /etc/emacs23/site-startd.d is supposed to exist
has caused the Debian Bug report #701945,
regarding ccrypt fails to install with emac23 due to /etc/emacs23/site-start.d 
does not exist
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.)


-- 
701945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: ccrypt
Version: 1.9-4
Severity: serious
Justification: Fails to install due to wrong path

/etc/emacs/site-start.d exists /etc/emacs23/stie-start.d does not.  This breaks 
ccrypt's install script and ccrypt fails to install.

emacs23 is successfully installed (after removed; it could not install with 
ccrypt installed due to this same error).


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ccrypt depends on:
ii  libc6  2.13-38

ccrypt recommends no packages.

ccrypt suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
Emacs add-on packages have the right to assume that the site-start.d for
the Emacs flavor in question exists, since it is shipped in the flavor's
-common package.  If that is not the case (see #701944), it is
unsurprising that installation fails.---End Message---


Bug#701949: elserv: fails to install with emacs33; cat -: No such file or directory during byte-compilation

2013-03-01 Thread Sven Joachim
Control: severity -1 normal
Control: severity 701952 normal

On 2013-03-01 04:59 +0100, Daniel Dickinson wrote:

 Package: elserv
 Version: 0.4.0+0.20011203cvs-17.1
 Severity: serious
 Justification: Fails to install

 elserv's install script is broken:

 Install elserv for emacs
 Install elserv for emacs23
 install/elserv: Handling emacs23, logged in /tmp/elc_xMv5B7.log   -- which 
 file is empty
 cat: -: No such files or directory
 ERROR: install script from elserv package failed
 dpkg: error processing elserver (--configure):
  subprocess installed post-installation script returned error exit status 1

Works for me, and apparently for everyone else.  Your emacs23
installation appears to be broken, see #701944.  Reinstall the
emacs23-common package and retry.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#701949: elserv: fails to install with emacs33; cat -: No such file or directory during byte-compilation

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 severity -1 normal
Bug #701949 [elserv] elserv: fails to install with emacs33; cat -: No such file 
or directory during byte-compilation
Severity set to 'normal' from 'serious'
 severity 701952 normal
Bug #701952 [debian-el] debian-el: fails to install due to heredoc failing; 
lazy evaluation and parentheses the culprit?
Severity set to 'normal' from 'serious'

-- 
701949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701949
701952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701952
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#700809: marked as done (python2.7: renders python2.7-dbg ( 2.7.3.1) unusable, causes FTBFS)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 10:03:38 +
with message-id e1ubmou-0005gb...@franck.debian.org
and subject line Bug#700809: fixed in python2.7 2.7.3-7
has caused the Debian Bug report #700809,
regarding python2.7: renders python2.7-dbg ( 2.7.3.1) unusable, causes FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
700809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python2.7
Version: 2.7.3-2
Severity: serious

The following change in 2.7.3-2 break python2.7-dbg 2.7.3-1 and
earlier versions:

python2.7 (2.7.3-2) unstable; urgency=low

  ...
  * Backport issue #13150: sysconfig no longer parses the Makefile and config.h
files when imported, instead doing it at build time.  This makes importing
sysconfig faster and reduces Python startup time by 20%.
  ...

python2.7-dbg doesn't have _sysconfigdata_d so running
python2.7-dbg fails with:

Traceback (most recent call last):
  File /usr/lib/python2.7/site.py, line 562, in module
main()
  File /usr/lib/python2.7/site.py, line 544, in main
known_paths = addusersitepackages(known_paths)
  File /usr/lib/python2.7/site.py, line 271, in addusersitepackages
user_site = getusersitepackages()
  File /usr/lib/python2.7/site.py, line 246, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
  File /usr/lib/python2.7/site.py, line 236, in getuserbase
USER_BASE = get_config_var('userbase')
  File /usr/lib/python2.7/sysconfig.py, line 591, in get_config_var
return get_config_vars().get(name)
  File /usr/lib/python2.7/sysconfig.py, line 490, in get_config_vars
_init_posix(_CONFIG_VARS)
  File /usr/lib/python2.7/sysconfig.py, line 374, in _init_posix
from _sysconfigdata import build_time_vars
  File /usr/lib/python2.7/_sysconfigdata.py, line 4, in module
from _sysconfigdata_d import *
ImportError: No module named _sysconfigdata_d

Since python2.7-dbg 2.7.3-1 depends on python2.7 (= 2.7.3-1), python2.7
should have a Breaks on python2.7-dbg ( 2.7.3-2) so that python2.7-dbg
isn't rendered unusable by upgrading python2.7 without upgrading
python2.7-dbg to a version = 2.7.3-2.

It might be also a good idea to change python2.7-dbg's dependency on
python2.7 to (= ${binary:Version}) as it's already done in experimental.

(I've observed this issue because of the build failure of python-crypto
2.6-4 on the ia64 buildd which has python2.7 2.7.3-5 and python2.7-dbg
2.7.3-1 installed [1])

Regards

[1] 
https://buildd.debian.org/status/fetch.php?pkg=python-cryptoarch=ia64ver=2.6-4stamp=1361116491
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: python2.7
Source-Version: 2.7.3-7

We believe that the bug you reported is fixed in the latest version of
python2.7, 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 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated python2.7 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, 01 Mar 2013 09:28:17 +0100
Source: python2.7
Binary: python2.7 python2.7-minimal libpython2.7 python2.7-examples 
python2.7-dev idle-python2.7 python2.7-doc python2.7-dbg
Architecture: source all amd64
Version: 2.7.3-7
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description: 
 idle-python2.7 - IDE for Python (v2.7) using Tkinter
 libpython2.7 - Shared Python runtime library (version 2.7)
 python2.7  - Interactive high-level object-oriented language (version 2.7)
 python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 python2.7-dev - Header files and a static library for Python (v2.7)
 python2.7-doc - Documentation for the high-level object-oriented language 
Python
 python2.7-examples - Examples for the Python language (v2.7)
 python2.7-minimal - Minimal subset of the Python language (version 2.7)
Closes: 700809
Changes: 
 python2.7 (2.7.3-7) unstable; urgency=low
 .
   * python2.7-dbg: Tighten dependency on python2.7. 

Bug#701976: ltt-control: FTBFS: /usr/bin/ld: tp.o: undefined reference to symbol 'rcu_dereference_sym'

2013-03-01 Thread Roland Stigge
Source: ltt-control
Version: 2.1.1-1
Severity: serious
Tags: patch sid
User: debian-powerpc...@breakpoint.cc
Usertags: powerpcspe

Hi,

ltt-control FTBFS on several arches like this:

[...]
make[4]: Entering directory `/«PKGBUILDDIR»/tests/tools/streaming'
  CC unit_tests.o
  CCLD   unit_tests
  CC gen-ust-events.o
  CC tp.o
  CCLD   gen-ust-events
/usr/bin/ld: tp.o: undefined reference to symbol 'rcu_dereference_sym'
/usr/bin/ld: note: 'rcu_dereference_sym' is defined in DSO 
/usr/lib/liburcu-bp.so.1 so try adding it to the linker command line
/usr/lib/liburcu-bp.so.1: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[4]: *** [gen-ust-events] Error 1
make[4]: Leaving directory `/«PKGBUILDDIR»/tests/tools/streaming'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»/tests/tools'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2cd 
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
[...]


The attached patch fixes this by autoreconf'ing.

Roland



-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)

Kernel: Linux 3.8.0 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -ruN ltt-control-2.1.1.orig/debian/control ltt-control-2.1.1/debian/control
--- ltt-control-2.1.1.orig/debian/control	2013-03-01 00:34:37.0 +0100
+++ ltt-control-2.1.1/debian/control	2013-03-01 10:48:43.238021748 +0100
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Jon Bernard jbern...@debian.org
 Build-Depends: debhelper (= 9), libpopt-dev, liburcu-dev (= 0.7.4),
-  liblttng-ust-dev (= 2.1.1-2)
+  liblttng-ust-dev (= 2.1.1-2), dh-autoreconf
 Standards-Version: 3.9.3
 Vcs-Git: git://git.debian.org/git/collab-maint/ltt-control.git
 Vcs-Browser: http://git.debian.org/?p=collab-maint/ltt-control.git;a=summary
diff -ruN ltt-control-2.1.1.orig/debian/rules ltt-control-2.1.1/debian/rules
--- ltt-control-2.1.1.orig/debian/rules	2013-03-01 00:34:37.0 +0100
+++ ltt-control-2.1.1/debian/rules	2013-03-01 10:48:26.430017571 +0100
@@ -3,7 +3,7 @@
 export DEB_BUILD_MAINT_OPTIONS := hardening=+all
 
 %:
-	dh $@
+	dh $@ --with autoreconf
 
 override_dh_auto_install:
 	# rename the bash completion file before installation


Processed: Re: Bug#701944: emacs23 fails to install due to /etc/emacs23 does exist for byte-compiling

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 severity -1 normal
Bug #701944 [emacs23] emacs23 fails to install due to /etc/emacs23 does exist 
for byte-compilingclone -1 ccrypt
Severity set to 'normal' from 'serious'
 tags -1 moreinfo
Bug #701944 [emacs23] emacs23 fails to install due to /etc/emacs23 does exist 
for byte-compilingclone -1 ccrypt
Added tag(s) moreinfo.

-- 
701944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701944
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#701944: emacs23 fails to install due to /etc/emacs23 does exist for byte-compiling

2013-03-01 Thread Sven Joachim
Control: severity -1 normal
Control: tags -1 moreinfo

On 2013-03-01 09:00 +0100, Sven Joachim wrote:

 On 2013-03-01 03:25 +0100, Daniel Dickinson wrote:

 Package: emacs23
 Version: 23.4+1-4
 Severity: serious
 Justification: broken install

 AIUI a package failing to install just because other packages are
 present is RC...or maybe it's the breaking package that's RC, however
 it's emacs23 that fails to install, the other package installs just
 fine without emacs present.  In any event I see:

 [snip]
 Install ccrypt for emacs23
 Install/ccrypt: Handling install for emacsen flavor emacs23
 Warning: List directory '/etc/emacs23' does not exist.
 Opening directory: No such file or directory, /etc/emacs23/site-start.d

 That's the problem, /etc/emacs23/site-start.d is shipped in
 emacs23-common and has somehow gone AWOL on your system.  You need to
 figure out how that happened.

Meanwhile, downgrading the severity.  If you find out that it was a
package which deleted this directory, please reassign the bug to that
package and set the severity back to serious.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#700718: marked as done (python-numpy: fails to upgrade from squeeze: prerm: 6: update-python-modules: not found)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 10:33:07 +
with message-id e1ubnh1-0006do...@franck.debian.org
and subject line Bug#700718: fixed in python-numpy 1:1.6.2-1.2
has caused the Debian Bug report #700718,
regarding python-numpy: fails to upgrade from squeeze: prerm: 6: 
update-python-modules: not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
700718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-numpy
Version: 1:1.6.2-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails.

From the attached log (scroll to the bottom...):

  Preparing to replace python-numpy 1:1.4.1-5 (using 
.../python-numpy_1%3a1.6.2-1.1_amd64.deb) ...
  /var/lib/dpkg/info/python-numpy.prerm: 6: update-python-modules: not found
  dpkg: warning: subprocess old pre-removal script returned error exit status 
127
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/prerm: 6: update-python-modules: not found
  dpkg: error processing 
/var/cache/apt/archives/python-numpy_1%3a1.6.2-1.1_amd64.deb (--unpack):
   subprocess new pre-removal script returned error exit status 127
  configured to not write apport reports
  /var/lib/dpkg/info/python-numpy.postinst: 6: update-python-modules: not found
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 127

Note that the attached log is from a squeeze - sid upgrade, but I
manually ran piuparts to test squeeze - wheezy(+new numpy) upgrades
which failed with exactly the same error.

This was observed while testing the upgrade of sixpac [contrib] from
squeeze, but I have now rescheduled all tests that might be affected by
the last mumpy upload ...


cheers,

Andreas


sixpack_1:0.68-1.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: python-numpy
Source-Version: 1:1.6.2-1.2

We believe that the bug you reported is fixed in the latest version of
python-numpy, 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 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot sebast...@debian.org (supplier of updated python-numpy 
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: Wed, 27 Feb 2013 10:33:24 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.6.2-1.2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 
python-modules-t...@lists.alioth.debian.org
Changed-By: Sébastien Villemot sebast...@debian.org
Description: 
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python3-numpy-dbg - Fast array facility to the Python language (debug 
extension)
Closes: 700718 700994
Changes: 
 python-numpy (1:1.6.2-1.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Remove Breaks relationships introduced in previous version. They break
 squeeze - wheezy upgrades. (Closes: #700718)
   * Install symlinks for Python 3 headers under /usr/include/python3.2mu (resp.
 python3.2dmu) instead of /usr/include/python3.2 (resp. python3.2_d),
 to avoid file versus symlink conflict. (Closes: #700994)
Checksums-Sha1: 
 5abe7750dcdd944b28861eb9c70f06fef15f95e0 2466 python-numpy_1.6.2-1.2.dsc
 33a947ef92ed673dc002ab5e98d8f0c72c3889d7 140465 
python-numpy_1.6.2-1.2.debian.tar.gz
 e308e2352519d2c6d5b990f310f1ad007af286a2 2632094 
python-numpy_1.6.2-1.2_amd64.deb
 76c53e3619eb817831d13f8a8cca18d90e0d8c30 6817794 
python-numpy-dbg_1.6.2-1.2_amd64.deb
 c48b62e70d8e90ff19b00d089e6597efe82fade4 1857910 
python3-numpy_1.6.2-1.2_amd64.deb
 539104dc18558a1b52a7794685a667d731c9c462 

Bug#700994: marked as done (python3-numpy: directory vs. symlink conflict: /usr/include/python3.2)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 10:33:07 +
with message-id e1ubnh1-0006dr...@franck.debian.org
and subject line Bug#700994: fixed in python-numpy 1:1.6.2-1.2
has caused the Debian Bug report #700994,
regarding python3-numpy: directory vs. symlink conflict: /usr/include/python3.2
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.)


-- 
700994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python3-numpy
Version: 1:1.6.2-1
Severity: serious

Hi,

while looking into #700782, we discovered that there is a symlink
vs. directory conflict between python3-numpy and python3.2-dev:
  python3.2-dev has /usr/include/python3.2 - python3.2mu
  python3-numpy ships /usr/include/python3.2/numpy
Please move the linked shipped as python3.2/numpy to python3.2mu.

# apt-get install python3-numpy
# apt-get install python3-dev
[...]
Setting up python3.2-dev (3.2.3-6) ...
WARNING: non-empty directory on upgrade: /usr/include/python3.2
total 0
lrwxrwxrwx 1 root root 56 May 30  2012 numpy -
../../lib/python3/dist-packages/numpy/core/include/numpy
Setting up python3-dev (3.2.3-5) ...
[...]

# ls -lad /usr/include/python*
drwxr-xr-x 2 root root   60 Feb 20 08:47 /usr/include/python3.2
drwxr-xr-x 2 root root   60 Feb 20 08:47 /usr/include/python3.2_d
drwxr-xr-x 2 root root 1900 Feb 20 08:47 /usr/include/python3.2mu

After fixing this in python3-numpy, please clone this a bug and
reassign to python3.2-dev to add an appropriate versioned Conflicts
against the buggy python-numpy3 versions. Breaks is probably not
sufficient to solve this file conflict, as apt could decide to
deconfigure (and not upgrade) python3-numpy before
installing/upgrading python3-dev.


Andreas
---End Message---
---BeginMessage---
Source: python-numpy
Source-Version: 1:1.6.2-1.2

We believe that the bug you reported is fixed in the latest version of
python-numpy, 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 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot sebast...@debian.org (supplier of updated python-numpy 
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: Wed, 27 Feb 2013 10:33:24 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.6.2-1.2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 
python-modules-t...@lists.alioth.debian.org
Changed-By: Sébastien Villemot sebast...@debian.org
Description: 
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python3-numpy-dbg - Fast array facility to the Python language (debug 
extension)
Closes: 700718 700994
Changes: 
 python-numpy (1:1.6.2-1.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Remove Breaks relationships introduced in previous version. They break
 squeeze - wheezy upgrades. (Closes: #700718)
   * Install symlinks for Python 3 headers under /usr/include/python3.2mu (resp.
 python3.2dmu) instead of /usr/include/python3.2 (resp. python3.2_d),
 to avoid file versus symlink conflict. (Closes: #700994)
Checksums-Sha1: 
 5abe7750dcdd944b28861eb9c70f06fef15f95e0 2466 python-numpy_1.6.2-1.2.dsc
 33a947ef92ed673dc002ab5e98d8f0c72c3889d7 140465 
python-numpy_1.6.2-1.2.debian.tar.gz
 e308e2352519d2c6d5b990f310f1ad007af286a2 2632094 
python-numpy_1.6.2-1.2_amd64.deb
 76c53e3619eb817831d13f8a8cca18d90e0d8c30 6817794 
python-numpy-dbg_1.6.2-1.2_amd64.deb
 c48b62e70d8e90ff19b00d089e6597efe82fade4 1857910 
python3-numpy_1.6.2-1.2_amd64.deb
 539104dc18558a1b52a7794685a667d731c9c462 4161850 
python3-numpy-dbg_1.6.2-1.2_amd64.deb
 04326eb7930b111d8d14fa88ee7a4c0cfeb434e1 5310448 
python-numpy-doc_1.6.2-1.2_all.deb
Checksums-Sha256: 
 12af1b8923a9a9bd784096ac0cd922adf2e2e9a5e747862cdd9c06e60c5c5b1e 2466 
python-numpy_1.6.2-1.2.dsc
 

Bug#701953: initramfs-tools: Missing modules prevent passphrase entry with usb keyboard

2013-03-01 Thread Michael Prokop
severity 701953 important
forcemerge 701953 700572
thanks

* Ben Caradoc-Davies [Fri Mar 01, 2013 at 02:04:20PM +0800]:
 Package: initramfs-tools
 Version: 0.109
 Severity: critical
 Justification: breaks the whole system

You're using a kernel from experimental with a non-standard setup,
this definitely doesn't qualify for severity 'critical', adjusting.

 I have a usb keyboard attached to a system with an unencrypted /boot and a
 LUKS-encrypted partition (LVM physical volume) containing the other
 filesystems. Today I installed linux-image-3.8-trunk-amd64
 (3.8-1~experimental.1). initramfs-tools created a corresponding initrd, as
 expected. Booting this kernel/initrd in grub2 resulted in a plymouth 
 passphrase
 entry screen, but a usb keyboard that did not work in any port. All keyboard
 lights were off. The system was thus unbootable without a non-usb keyboard
 (hence critical severity). Without a non-usb keyboard or backup grub entry 
 (3.7
 kernel with working initrd), I would have been unable to access my system
 without rescue media.
[...]

This is #700572, I'm trying to release an updated package.

regards,
-mika-


signature.asc
Description: Digital signature


Processed: Re: Bug#701953: initramfs-tools: Missing modules prevent passphrase entry with usb keyboard

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 701953 important
Bug #701953 [initramfs-tools] initramfs-tools: Missing modules prevent 
passphrase entry with usb keyboard
Severity set to 'important' from 'critical'
 forcemerge 701953 700572
Bug #701953 [initramfs-tools] initramfs-tools: Missing modules prevent 
passphrase entry with usb keyboard
Bug #700572 [initramfs-tools] initramfs-tools: The ehci-hcd module has been 
split into ehci-pci + ehci-hcd in Linux v3.8
Severity set to 'important' from 'normal'
Marked as found in versions initramfs-tools/0.109.
Bug #701953 [initramfs-tools] initramfs-tools: Missing modules prevent 
passphrase entry with usb keyboard
Marked as found in versions initramfs-tools/0.98.8.
Added tag(s) patch.
Merged 700572 701953
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700572
701953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701953
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#701991: maven3: CVE-2013-0253

2013-03-01 Thread Moritz Muehlenhoff
Package: maven3
Severity: grave
Tags: security
Justification: user security hole

Please see http://maven.apache.org/security.html for details.

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698294: [Pkg-puppet-devel] Bug#698294: diff for NMU 2.7.18-2.1

2013-03-01 Thread Stig Sandbeck Mathisen
Anton Gladky gl...@debian.org writes:

 I've prepared an NMU for puppet (versioned as 2.7.18-2.1) and uploaded
 it to DELAYED/5. Please feel free to tell me if I should delay it
 longer.

That patch was marked as Code Insufficient in the upstream bug tracker
two weeks ago at http://projects.puppetlabs.com/issues/7680#note-18

Please delay it until this is resolved by upstream.

-- 
Stig Sandbeck Mathisen s...@debian.org


pgp5kq9SM0JoQ.pgp
Description: PGP signature


Processed: tagging 698294

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 698294 - pending
Bug #698294 [puppet] puppet: Checksum mismatch when copying followed symlinks 
(upstream #7680)
Removed tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
698294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#700530: qt frames empty

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #700530 [src:qt4-x11] qt frames remain empty in kfreebsd since -10 to -11 
update
Ignoring request to alter tags of bug #700530 to the same tags previously set

-- 
700530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700530
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#700530: qt frames empty

2013-03-01 Thread Lisandro Damián Nicanor Pérez Meyer
Control: tag -1 moreinfo

Hi! A new version of xorg-server has been uploaded [0]. This should fix this 
issue. Would you mind checking that this is indeed the situation?

[0] http://packages.qa.debian.org/x/xorg-server/news/20130223T151839Z.html

Kinds regards, Lisandro.

-- 
When the winds of change are blowing, some people are building shelters, and
others are building windmills.
  Old Chinese Proverb

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Bug#701991: maven3: CVE-2013-0253

2013-03-01 Thread Gergely Nagy
Control: reassign -1 src:maven

Moritz Muehlenhoff j...@inutil.org writes:

 Package: maven3

There is no maven3 package, so I'm reassigning to maven, which does have
a version = 3, so I assume it is the package you meant to file the bug
against.

 Severity: grave
 Tags: security
 Justification: user security hole

 Please see http://maven.apache.org/security.html for details.

 Cheers,
 Moritz

-- 
|8]


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#701991: maven3: CVE-2013-0253

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 src:maven
Bug #701991 [maven3] maven3: CVE-2013-0253
Warning: Unknown package 'maven3'
Bug reassigned from package 'maven3' to 'src:maven'.
Ignoring request to alter found versions of bug #701991 to the same values 
previously set
Ignoring request to alter fixed versions of bug #701991 to the same values 
previously set

-- 
701991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701991
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: severity of 612293 is normal

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 612293 normal
Bug #612293 [installation-reports] installation-reports: hangs up trying floppy
Severity set to 'normal' from 'serious'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
612293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612293
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#690046: installation-reports: System unstable, page faults on A4-3300 APU

2013-03-01 Thread Julien Cristau
Control: tag -1 moreinfo
Control: severity -1 important

On Tue, Oct  9, 2012 at 14:24:07 +0100, Fred wrote:

 Package: installation-reports
 Severity: critical
 Justification: breaks the whole system
 
 System becomes unstable. Have tried both 32 bit and 64 bit installs with all 
 standard kernels offered with both 6.0.5 and 6.0.6 net-inst CD images.
 
 Stripped out all extraneous hardware but problem persists with just the 
 motherboard, APU and RAM.
 
 Here is a log extract of one of the faults:
 
 Oct  9 14:05:35 media kernel: [  148.633457] Pid: 5239, comm: factor Not 
 tainted 2.6.32-5-686 #1
 Oct  9 14:05:35 media kernel: [  148.633459] Call Trace:
 Oct  9 14:05:35 media kernel: [  148.633467]  [c108af7a] ? 
 bad_page+0xd7/0xeb
 Oct  9 14:05:35 media kernel: [  148.633471]  [c108c260] ? 
 get_page_from_freelist+0x2e7/0x3c7
 Oct  9 14:05:35 media kernel: [  148.633474]  [c108c601] ? 
 __alloc_pages_nodemask+0xf3/0x4d9
 Oct  9 14:05:35 media kernel: [  148.633478]  [c10a2d42] ? 
 anon_vma_prepare+0x32/0x8c
 Oct  9 14:05:35 media kernel: [  148.633481]  [c109be91] ? 
 handle_mm_fault+0x2ba/0x959
 Oct  9 14:05:35 media kernel: [  148.633484]  [c10a01a0] ? 
 do_brk+0x246/0x28e
 Oct  9 14:05:35 media kernel: [  148.633488]  [c1270da0] ? 
 do_page_fault+0x2f1/0x307
 Oct  9 14:05:35 media kernel: [  148.633491]  [c1270aaf] ? 
 do_page_fault+0x0/0x307
 Oct  9 14:05:35 media kernel: [  148.633493]  [c126f303] ? 
 error_code+0x73/0x78
 Oct  9 14:05:35 media kernel: [  148.633495] Disabling lock debugging due to 
 kernel taint
 
Hi, and sorry for the late answer.

Did you check the RAM in that machine?  This seems more likely to be
hardware failure than anything else as far as I can tell...

Cheers,
Julien


signature.asc
Description: Digital signature


Processed: Re: Bug#690046: installation-reports: System unstable, page faults on A4-3300 APU

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #690046 [installation-reports] installation-reports: System unstable, page 
faults on A4-3300 APU
Added tag(s) moreinfo.
 severity -1 important
Bug #690046 [installation-reports] installation-reports: System unstable, page 
faults on A4-3300 APU
Severity set to 'important' from 'critical'

-- 
690046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690046
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: severity of 683705 is normal

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 683705 normal
Bug #683705 [installation-reports] installation-report: Installer failing to 
boot from known-good media on known-good hardware
Severity set to 'normal' from 'grave'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
683705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683705
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: severity of 700976 is important

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 700976 important
Bug #700976 [installation-reports] debian-installer: Failed to boot installed 
UEFI system
Severity set to 'important' from 'critical'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700976
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: severity of 700656 is important

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 700656 important
Bug #700656 [installation-reports] installation-reports: Corrupt screens after 
grub menu with UEFI
Severity set to 'important' from 'critical'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700656
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: user release.debian....@packages.debian.org, tagging 694928, usertagging 694928, tagging 694986 ...

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
jcris...@debian.org).
 tags 694928 + wheezy-ignore
Bug #694928 [flash-kernel] flash-kernel: postinst modifies /etc/default/rcS
Added tag(s) wheezy-ignore.
 usertags 694928 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
 tags 694986 + wheezy-ignore
Bug #694986 [initscripts] flash-kernel: postinst modifies /etc/default/rcS
Added tag(s) wheezy-ignore.
 usertags 694986 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
694928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694928
694986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694986
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#691180: iptables: diff for NMU version 1.4.14-3.1

2013-03-01 Thread Julien Cristau
tags 691180 + patch
tags 691180 + pending
thanks

Dear maintainer,

I've prepared an NMU for iptables (versioned as 1.4.14-3.1) and
will upload it asap.  NMU diff attached.

Cheers,
Julien
diff -Nru iptables-1.4.14/debian/changelog iptables-1.4.14/debian/changelog
--- iptables-1.4.14/debian/changelog	2012-07-28 18:04:24.0 +0200
+++ iptables-1.4.14/debian/changelog	2013-03-01 14:50:46.0 +0100
@@ -1,3 +1,16 @@
+iptables (1.4.14-3.1) wheezy; urgency=low
+
+  [ Jonathan Nieder ]
+  * Non-maintainer upload.
+  * Add Breaks against iproute and xtables-addons-common versions
+that relied on libxtables4. Closes: #691180
+
+  [ Julien Cristau ]
+  * Have iptables provide libxtables7, and tell dh_makeshlibs to include that
+in generated dependencies.
+
+ -- Julien Cristau jcris...@debian.org  Fri, 01 Mar 2013 14:50:39 +0100
+
 iptables (1.4.14-3) unstable; urgency=low
 
   * Fixes iptables comment output error reported by Christoph Anton
diff -Nru iptables-1.4.14/debian/control iptables-1.4.14/debian/control
--- iptables-1.4.14/debian/control	2011-12-31 19:51:31.0 +0100
+++ iptables-1.4.14/debian/control	2013-03-01 14:47:00.0 +0100
@@ -9,6 +9,8 @@
 Package: iptables
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
+Provides: libxtables7
+Breaks: iproute ( 20120521-3), xtables-addons-common ( 1.42-2)
 Description: administration tools for packet filtering and NAT
  These are the user-space administration tools for the Linux
  kernel's netfilter and iptables. netfilter and iptables provide
diff -Nru iptables-1.4.14/debian/rules iptables-1.4.14/debian/rules
--- iptables-1.4.14/debian/rules	2012-04-22 15:49:25.0 +0200
+++ iptables-1.4.14/debian/rules	2013-03-01 14:49:33.0 +0100
@@ -13,6 +13,9 @@
 binary: binary-arch binary-indep
 binary-arch binary-indep: install
 
+override_dh_makeshlibs:
+	dh_makeshlibs -V'iptables, libxtables7'
+
 override_dh_shlibdeps:
 	dh_shlibdeps $(_shlibdeps)
 


signature.asc
Description: Digital signature


Processed: iptables: diff for NMU version 1.4.14-3.1

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 691180 + patch
Bug #691180 [iptables] connman: Connman won't run due to missing libxtables.so.7
Added tag(s) patch.
 tags 691180 + pending
Bug #691180 [iptables] connman: Connman won't run due to missing libxtables.so.7
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
691180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691180
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#700169: non-free license: requires to obey US export regulation even, when not in the US

2013-03-01 Thread Ansgar Burchardt
Hi,

I took a brief look at the upstream website. The download site [1]
points to two other pages for downloads ([2] and [3]), one of them
having the non-free license, the other a BSD/GPL dual-license.
Interestingly both of these ask to accept the non-free license...

They both contain a different link to a source tarball. I downloaded
both and compared them: they only differ in the license headers in the
individual files.

The files in acpica-unix-20130214.tar.gz have the non-free license.
The files in acpica-unix2-20130214.tar.gz have a 3-clause BSD license or
GPL-2:

 * Copyright (C) 2000 - 2013, Intel Corp.
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions, and the following disclaimer,
 *without modification.
 * 2. Redistributions in binary form must reproduce at minimum a disclaimer
 *substantially similar to the NO WARRANTY disclaimer below
 *(Disclaimer) and any redistribution must be conditioned upon
 *including a substantially similar Disclaimer requirement for further
 *binary redistribution.
 * 3. Neither the names of the above-listed copyright holders nor the names
 *of any contributors may be used to endorse or promote products derived
 *from this software without specific prior written permission.
 *
 * Alternatively, this software may be distributed under the terms of the
 * GNU General Public License (GPL) version 2 as published by the Free
 * Software Foundation.
 *
 * NO WARRANTY
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
 * AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR
 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
 * HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
 * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 * POSSIBILITY OF SUCH DAMAGES.


I tried replacing the date to get the version we currently have in
Debian, but only the tarball with the non-free license was available
from [4].

  [1] https://www.acpica.org/downloads/
  [2] https://www.acpica.org/downloads/unix_source_code.php
  [3] https://www.acpica.org/downloads/unix2_source_code.php
  [4] https://www.acpica.org/download/acpica-unix-20100528.tar.gz


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#700027: kfreebsd-kernel-headers: Redefinition of struct termios

2013-03-01 Thread Julien Cristau
On Thu, Feb  7, 2013 at 17:17:59 +0100, Guillem Jover wrote:

 I'm filing this to track the issue, and because I have to do some
 other stuff, if no one else has dealt with it by then I'll look into
 fixing and uploading the package.
 
Any news or ETA?

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#701838: nmu for security issues

2013-03-01 Thread Bdale Garbee
Michael Gilbert mgilb...@debian.org writes:

 I uploaded an nmu fixing the recent security issues.  Please see
 attached patch. 

Thanks.

Bdale


pgpE51sJkyUcl.pgp
Description: PGP signature


Processed: severity of 700158 is grave

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 severity 700158 grave
Bug #700158 [src:ganglia] ganglia: CVE-2013-0275 and CVE-2013-1770: several XSS 
flaws
Severity set to 'grave' from 'important'

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
700158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700158
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: severity of 634261 is important

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 634261 important
Bug #634261 [libc6] libc6: Bus Error in setbuf() only on sparc
Bug #688086 [libc6] iceape: [sparc] iceape stops with bus error
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
634261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634261
688086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688086
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: user release.debian....@packages.debian.org, tagging 700158, usertagging 700158

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
jcris...@debian.org).
 tags 700158 + wheezy-ignore
Bug #700158 [src:ganglia] ganglia: CVE-2013-0275 and CVE-2013-1770: several XSS 
flaws
Added tag(s) wheezy-ignore.
 usertags 700158 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700158
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#700169: non-free license: requires to obey US export regulation even, when not in the US

2013-03-01 Thread Ansgar Burchardt
I also checked the initial Debian package on snapshot.debian.org
(version 20050930-1). It also has only the non-free license in the
individual files, but states Dual GPLv2/ACPICA Licence in d/copyright.
It also has the BSD-3-clause-or-GPL-2 bit in d/copyright.

It's likely that it was already dual-licensed, but that this wasn't
documented in the tarball itself. I'm not sure why they now have two
tarballs instead of one with both licenses... The GNU General Public
License or via a separate license that may be more favorable to
commercial OSVs (from the FAQ) seems also wrong given there are *three*
licenses: the non-free one, a 3-clause BSD and the GPL-2.

Ansgar


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: user release.debian....@packages.debian.org, tagging 700527, usertagging 700527

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
jcris...@debian.org).
 tags 700527 + wheezy-ignore
Bug #700527 [libjs-jquery] libjs-jquery broken by movabletype-opensource  
5.1.4+dfsg-3~
Added tag(s) wheezy-ignore.
 usertags 700527 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700527
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 696661

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 696661 + pending
Bug #696661 [bind9] bind9 - Fails if openssl can't load the gost engine
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
696661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696661
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: closing 693015

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 close 693015
Bug #693015 [bind9] bind9: CVE-2012-4244 - A specially crafted Resource Record 
could cause named to terminate
Bug #693016 [bind9] bind9: CVE-2012-4244 - A specially crafted Resource Record 
could cause named to terminate
Marked Bug as done
Marked Bug as done
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
693015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693015
693016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693016
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#701185: CVE-2013-0200: Insecure temporary files

2013-03-01 Thread Sebastian Ramacher
Control: found -1 3.10.6-2+squeeze1
Control: found -1 3.12.6-3
Control: found -1 3.12.11-1

All versions that are currently in the archive are affected by this
bug.

On 2013-02-22 15:15:13, Moritz Muehlenhoff wrote:
 Package: hplip
 Severity: grave
 Tags: security
 Justification: user security hole
 
 Several further insecurely handled temporary files were discovered by Red Hat:
 https://www.redhat.com/archives/enterprise-watch-list/2013-February/msg00024.html
 
 I've extracted the patch from the RHEL update, it's attached to this mail.

The patch introduces one buffer overflow and an regression.

 diff -up hplip-3.12.4/prnt/hpcups/HPCupsFilter.cpp.CVE-2013-0200 
 hplip-3.12.4/prnt/hpcups/HPCupsFilter.cpp
 --- hplip-3.12.4/prnt/hpcups/HPCupsFilter.cpp.CVE-2013-0200   2013-01-22 
 10:57:13.651460928 +
 +++ hplip-3.12.4/prnt/hpcups/HPCupsFilter.cpp 2013-01-22 10:57:34.087541538 
 +
 @@ -637,19 +637,22 @@ int HPCupsFilter::processRasterData(cups
  {
  charszFileName[32];
  memset(szFileName, 0, sizeof(szFileName));
 -snprintf (szFileName, sizeof(szFileName), 
 /tmp/hpcupsfilterc_%d.bmp, current_page_number);
 +snprintf (szFileName, sizeof(szFileName), 
 /tmp/hpcupsfilterc_%d.bmp.XX, current_page_number);

If current_page_number is larger than 9, the last six characters of
szFileName won't be XX and hence mkstemp will fail with EINVAL.

 diff -up hplip-3.12.4/prnt/hpcups/SystemServices.cpp.CVE-2013-0200 
 hplip-3.12.4/prnt/hpcups/SystemServices.cpp
 --- hplip-3.12.4/prnt/hpcups/SystemServices.cpp.CVE-2013-0200 2012-04-10 
 09:32:37.0 +0100
 +++ hplip-3.12.4/prnt/hpcups/SystemServices.cpp   2013-01-22 
 10:57:34.088541545 +
 @@ -36,10 +36,12 @@ SystemServices::SystemServices(int iLogL
  m_fp = NULL;
  if (iLogLevel  SAVE_PCL_FILE)
  {
 + int fd;
  charfname[32];
 -sprintf(fname, /tmp/hpcups_job%d.out, job_id);
 -m_fp = fopen(fname, w);
 -chmod(fname, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
 +sprintf(fname, /tmp/hpcups_job%d.out.XX, job_id);

job_id  10 will cause a buffer overflow. According to cups' API
documentation job_id can be up to 2^31-1 [1].

The attached patch makes the buffers large enough. I'll prepare a NMU
later today if nobody beats me to it.

Regards

[1] http://www.cups.org/documentation.php/api-cups.html#PRINT_JOBS
-- 
Sebastian Ramacher
--- a/prnt/hpcups/HPCupsFilter.cpp
+++ b/prnt/hpcups/HPCupsFilter.cpp
@@ -656,21 +656,24 @@
 
 if (m_iLogLevel  SAVE_INPUT_RASTERS)
 {
-charszFileName[32];
+charszFileName[44];
 memset(szFileName, 0, sizeof(szFileName));
-snprintf (szFileName, sizeof(szFileName), /tmp/hpcupsfilterc_%d.bmp, current_page_number);
+snprintf (szFileName, sizeof(szFileName), /tmp/hpcupsfilterc_%d.bmp.XX, current_page_number);
 if (cups_header.cupsColorSpace == CUPS_CSPACE_RGBW ||
 cups_header.cupsColorSpace == CUPS_CSPACE_RGB)
 {
-cfp = fopen (szFileName, w);
-chmod (szFileName, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
+		int fd = mkstemp (szFileName);
+		if (fd != -1)
+		cfp = fdopen (fd, w);
 }
 if (cups_header.cupsColorSpace == CUPS_CSPACE_RGBW ||
 cups_header.cupsColorSpace == CUPS_CSPACE_K)
 {
-szFileName[17] = 'k';
-kfp = fopen (szFileName, w);
-chmod (szFileName, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
+		int fd;
+		snprintf (szFileName, sizeof(szFileName), /tmp/hpcupsfilterk_%d.bmp.XX, current_page_number);
+		fd = mkstemp (szFileName);
+		if (fd != -1)
+		kfp = fdopen (fd, w);
 }
 
 WriteBMPHeader (cfp, cups_header.cupsWidth, cups_header.cupsHeight, COLOR_RASTER);
--- a/prnt/hpcups/SystemServices.cpp
+++ b/prnt/hpcups/SystemServices.cpp
@@ -36,10 +36,12 @@
 m_fp = NULL;
 if (iLogLevel  SAVE_PCL_FILE)
 {
-charfname[32];
-sprintf(fname, /tmp/hpcups_job%d.out, job_id);
-m_fp = fopen(fname, w);
-chmod(fname, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
+	int	fd;
+charfname[40];
+sprintf(fname, /tmp/hpcups_job%d.out.XX, job_id);
+	fd = mkstemp (fname);
+	if (fd != -1)
+	m_fp = fdopen(fd, w);
 }
 }
 
--- a/prnt/hpijs/hpijs.cpp
+++ b/prnt/hpijs/hpijs.cpp
@@ -96,13 +96,12 @@
 
 if (pSS-m_iLogLevel  SAVE_PCL_FILE)
 {
+	int	fd;
 charszFileName[32];
-	sprintf (szFileName, /tmp/hpijs_%d.out, getpid());
-	pSS-outfp = fopen (szFileName, w);
-	if (pSS-outfp)
-	{
-	chmod (szFileName, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
-	}
+	sprintf (szFileName, /tmp/hpijs_%d.out.XX, getpid());
+	fd = mkstemp (szFileName);
+	if (fd != -1)
+	pSS-outfp = fdopen (fd, w);
 }
 }
 
--- a/prnt/hpps/hppsfilter.c
+++ b/prnt/hpps/hppsfilter.c

Processed: Re: Bug#701185: CVE-2013-0200: Insecure temporary files

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 found -1 3.10.6-2+squeeze1
Bug #701185 [hplip] CVE-2013-0200: Insecure temporary files
Marked as found in versions hplip/3.10.6-2+squeeze1.
 found -1 3.12.6-3
Bug #701185 [hplip] CVE-2013-0200: Insecure temporary files
Marked as found in versions hplip/3.12.6-3.
 found -1 3.12.11-1
Bug #701185 [hplip] CVE-2013-0200: Insecure temporary files
Marked as found in versions hplip/3.12.11-1.

-- 
701185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, breaking python entirely

2013-03-01 Thread Vincent Lefevre
Package: libpython2.7
Version: 2.7.3-7
Severity: grave
Justification: renders package unusable

When upgrading:

Preconfiguring packages ...
(Reading database ... 505540 files and directories currently installed.)
Preparing to replace libpython2.7 2.7.3-6 (using 
.../libpython2.7_2.7.3-7_amd64.deb) ...
Unpacking replacement libpython2.7 ...
Preparing to replace python2.7 2.7.3-6 (using .../python2.7_2.7.3-7_amd64.deb) 
...
Unpacking replacement python2.7 ...
dpkg: error processing /var/cache/apt/archives/python2.7_2.7.3-7_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/python2.7/lib-dynload/_hashlib.so', which is 
also in package python2.7-minimal 2.7.3-6
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to replace python2.7-minimal 2.7.3-6 (using 
.../python2.7-minimal_2.7.3-7_amd64.deb) ...
Unpacking replacement python2.7-minimal ...
Preparing to replace python-numpy 1:1.6.2-1.1 (using 
.../python-numpy_1%3a1.6.2-1.2_amd64.deb) ...
Unpacking replacement python-numpy ...
[...]
Errors were encountered while processing:
 /var/cache/apt/archives/python2.7_2.7.3-7_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
dpkg: dependency problems prevent configuration of libpython2.7:
 libpython2.7 depends on python2.7 (= 2.7.3-7); however:
  Version of python2.7 on system is 2.7.3-6.

dpkg: error processing libpython2.7 (--configure):
 dependency problems - leaving unconfigured
Setting up python2.7-minimal (2.7.3-7) ...
Installing new version of config file /etc/apt/apt.conf.d/50unattended-upgrades 
...
Setting up python-numpy (1:1.6.2-1.2) ...
Processing triggers for python-support ...
Errors were encountered while processing:
 libpython2.7


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, breaking python entirely

2013-03-01 Thread Vincent Lefevre
Probably a missing Breaks.

Doing the upgrade again solves the problem, but with various
intermediate errors about /usr/lib/python2.7/hashlib.py.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: user release.debian....@packages.debian.org, tagging 681147, usertagging 681147

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
jcris...@debian.org).
 tags 681147 + wheezy-ignore
Bug #681147 {Done: Andreas Beckmann a...@debian.org} [libmilter-dev] 
libmilter-dev: /u/s/d/libmilter-dev is a symlink to sendmail, but ships files 
in /u/s/d/libmilter-dev
Added tag(s) wheezy-ignore.
 usertags 681147 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
681147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681147
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#691180: marked as done (connman: Connman won't run due to missing libxtables.so.7)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 16:33:06 +
with message-id e1ubsto-0003ft...@franck.debian.org
and subject line Bug#691180: fixed in iptables 1.4.14-3.1
has caused the Debian Bug report #691180,
regarding connman: Connman won't run due to missing libxtables.so.7
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.)


-- 
691180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: connman
Version: 1.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
  I installed connman
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
  I ran `/etc/init.d/connman start` as root
   * What was the outcome of this action?
  It output:
 [] Starting Connection Manager:/usr/sbin/connmand: error while
loading shared libraries: libxtables.so.7: cannot open shared object file: No
such file or directory
  failed!
   * What outcome did you expect instead?
  Connman to start



-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages connman depends on:
ii  dbus  1.6.8-1
ii  iptables  1.4.16.3-1
ii  libc6 2.13-35
ii  libdbus-1-3   1.6.8-1
ii  libglib2.0-0  2.33.12+really2.32.4-2
ii  libgnutls26   2.12.20-1
ii  lsb-base  4.1+Debian7

Versions of packages connman recommends:
ii  bluez  4.99-2
ii  wpasupplicant  1.0-3

connman suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
Source: iptables
Source-Version: 1.4.14-3.1

We believe that the bug you reported is fixed in the latest version of
iptables, 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 691...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau jcris...@debian.org (supplier of updated iptables 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: Fri, 01 Mar 2013 14:50:39 +0100
Source: iptables
Binary: iptables iptables-dev
Architecture: source amd64
Version: 1.4.14-3.1
Distribution: wheezy
Urgency: low
Maintainer: Laurence J. Lane ljl...@debian.org
Changed-By: Julien Cristau jcris...@debian.org
Description: 
 iptables   - administration tools for packet filtering and NAT
 iptables-dev - iptables development files
Closes: 691180
Changes: 
 iptables (1.4.14-3.1) wheezy; urgency=low
 .
   [ Jonathan Nieder ]
   * Non-maintainer upload.
   * Add Breaks against iproute and xtables-addons-common versions
 that relied on libxtables4. Closes: #691180
 .
   [ Julien Cristau ]
   * Have iptables provide libxtables7, and tell dh_makeshlibs to include that
 in generated dependencies.
Checksums-Sha1: 
 bfacbb21fd095cd2ad56039afd5cf5095be55c47 1828 iptables_1.4.14-3.1.dsc
 a65ec4c15d12b4e85d5651fc5d22ae5664c0f150 44266 
iptables_1.4.14-3.1.debian.tar.gz
 18f2ce5b1be8bfa785aa731639624017c38d44f8 405276 iptables_1.4.14-3.1_amd64.deb
 7a962b91176613381177505eb5ec5b4a8f32e959 61960 
iptables-dev_1.4.14-3.1_amd64.deb
Checksums-Sha256: 
 b571be4ed889851c0dae0834ef5c0103259790b4b2eecaab0378253c77047eec 1828 
iptables_1.4.14-3.1.dsc
 060d668d790e5033a420ad5de84d065c2ffbf018348af25b9ddb7118d2daed07 44266 
iptables_1.4.14-3.1.debian.tar.gz
 858e27802305e5d583eca2ac06ce48bc5edeba51a301533f67170156841f113a 405276 
iptables_1.4.14-3.1_amd64.deb
 f9702d6c0820ef2bf7878cc6a7fd322dabb6497742f43a825127e2bf8f786bd3 61960 
iptables-dev_1.4.14-3.1_amd64.deb
Files: 
 1da98f307e4fd20836dfd87c00a29f33 1828 net important iptables_1.4.14-3.1.dsc
 9af799641d5d4dac261d0d3745eee1b8 44266 net important 
iptables_1.4.14-3.1.debian.tar.gz
 a2276aa141f65ec246f9b1234791e107 405276 net important 
iptables_1.4.14-3.1_amd64.deb
 2a1088dd520ed9b71206b82f5d65a580 61960 devel optional 
iptables-dev_1.4.14-3.1_amd64.deb

-BEGIN 

Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, breaking python entirely

2013-03-01 Thread Sven Joachim
Control: severity -1 serious
Control: reassign -1 python2.7 2.7.3-7

On 2013-03-01 17:05 +0100, Vincent Lefevre wrote:

 Probably a missing Breaks.

No, a missing Replaces in python2.7:

,
| Unpacking replacement python2.7 ...
| dpkg: error processing /var/cache/apt/archives/python2.7_2.7.3-7_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/python2.7/lib-dynload/_hashlib.so', which is 
also in package python2.7-minimal 2.7.3-6
`

The changelog does not mention this, so I have no idea whether moving
the file from python2.7-minimal to python2.7 was intentional or not.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, breaking python entirely

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 severity -1 serious
Bug #702005 [libpython2.7] libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, 
breaking python entirely
Severity set to 'serious' from 'grave'
 reassign -1 python2.7 2.7.3-7
Bug #702005 [libpython2.7] libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, 
breaking python entirely
Bug reassigned from package 'libpython2.7' to 'python2.7'.
No longer marked as found in versions python2.7/2.7.3-7.
Ignoring request to alter fixed versions of bug #702005 to the same values 
previously set
Bug #702005 [python2.7] libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, 
breaking python entirely
Marked as found in versions python2.7/2.7.3-7.

-- 
702005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702005
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#697230: asterisk: Two security issues: AST-2012-014 / AST-2012-015

2013-03-01 Thread Moritz Muehlenhoff
found 697230 1:1.8.13.1~dfsg-1
thanks

On Wed, Jan 02, 2013 at 10:56:43PM +0100, Salvatore Bonaccorso wrote:
 Package: asterisk
 Severity: grave
 Tags: security
 Justification: user security hole
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512
 
 Hi,
 
 the following vulnerabilities were published for asterisk.
 
 CVE-2012-5976[0]:
 Crashes due to large stack allocations when using TCP
 
 CVE-2012-5977[1]:
 Denial of Service Through Exploitation of Device State Caching
 
 If you fix the vulnerabilities please also make sure to include the
 CVE (Common Vulnerabilities  Exposures) ids in your changelog entry.
 
 For further information see:
 
 [0] http://security-tracker.debian.org/tracker/CVE-2012-5976
 [1] http://security-tracker.debian.org/tracker/CVE-2012-5977
 
 Please adjust the affected versions in the BTS as needed.
 
 According to the advisories all 1.8.x versions seems affected.

This is still unfixed in sid!

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: Re: asterisk: Two security issues: AST-2012-014 / AST-2012-015

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 found 697230 1:1.8.13.1~dfsg-1
Bug #697230 {Done: Tzafrir Cohen tzaf...@debian.org} [asterisk] asterisk: Two 
security issues: AST-2012-014 / AST-2012-015
Marked as found in versions asterisk/1:1.8.13.1~dfsg-1 and reopened.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
697230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697230
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#699396: marked as done (CVE-2013-0241 - qxl: synchronous io guest DoS)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 1 Mar 2013 17:53:13 +0100
with message-id 20130301165313.ge12...@inutil.org
and subject line Re: Bug#699396: CVE-2013-0241 - qxl: synchronous io guest DoS
has caused the Debian Bug report #699396,
regarding CVE-2013-0241 - qxl: synchronous io guest DoS
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.)


-- 
699396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: xserver-xorg-video-qxl
Severity: grave
Tags: security patch
Justification: user security hole

Hi there,
   Take a look to http://seclists.org/oss-sec/2013/q1/204
   Please, use CVE-2013-0241 to refer this issue.
   The Debian package in unstable looks affected. Can you check if the stable 
or 
testings are affected too?

Cheers,
luciano
---End Message---
---BeginMessage---
Version: 0.0.17-1

On Fri, Feb 01, 2013 at 12:57:02AM +0800, Liang Guo wrote:
 Hi, 
 
 On Thu, Jan 31, 2013 at 12:10:16AM +0100, Luciano Bello wrote:
  Package: xserver-xorg-video-qxl
  Severity: grave
  Tags: security patch
  Justification: user security hole
  
  Hi there,
 Take a look to http://seclists.org/oss-sec/2013/q1/204
 Please, use CVE-2013-0241 to refer this issue.
 The Debian package in unstable looks affected. Can you check if the 
  stable or 
  testings are affected too?
  
  Cheers,
  luciano
 Would you like to check xserver-xorg-video-qxl 0.0.17 is 
 affected? 
 
 According to http://seclists.org/oss-sec/2013/q1/204, this
 bug is fixed in commit 30b4b72cdbdf9f0e92a8d1c4e01779f60f15a741, 
 which is included in 0.0.17.

Closing the bug properly.

Cheers,
Moritz---End Message---


Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, breaking python entirely

2013-03-01 Thread Sven Joachim
On 2013-03-01 17:43 +0100, Sven Joachim wrote:

 Control: severity -1 serious
 Control: reassign -1 python2.7 2.7.3-7

 On 2013-03-01 17:05 +0100, Vincent Lefevre wrote:

 Probably a missing Breaks.

 No, a missing Replaces in python2.7:

 ,
 | Unpacking replacement python2.7 ...
 | dpkg: error processing /var/cache/apt/archives/python2.7_2.7.3-7_amd64.deb 
 (--unpack):
 |  trying to overwrite '/usr/lib/python2.7/lib-dynload/_hashlib.so', which is 
 also in package python2.7-minimal 2.7.3-6
 `

 The changelog does not mention this, so I have no idea whether moving
 the file from python2.7-minimal to python2.7 was intentional or not.

Apparently this file should not have been in -minimal in the first
place, and on i386 (and other architectures, it seems) it has been in
python2.7 even in version 2.7.3-6.  But on amd64, it has been in
python2.7-minimal which I find quite inexplicable.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: user release.debian....@packages.debian.org, tagging 699305, usertagging 699305

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
jcris...@debian.org).
 tags 699305 + wheezy-ignore
Bug #699305 [nip2] nip2: sRGB.icm is non-free
Added tag(s) wheezy-ignore.
 usertags 699305 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
699305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699305
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#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()

2013-03-01 Thread Andres Mejia
It looks like the crystalhd drivers are buggy with newer kernel
releases. I opt for removing the dkms package. I will do this over the
weekend.

On Thu, Feb 28, 2013 at 4:52 PM, thomas schorpp
thomas.scho...@gmail.com wrote:
 On 28.02.2013 20:41, Julien Cristau wrote:

 On Thu, Jan 31, 2013 at 19:25:50 +0100, tom schorpp wrote:

 Package: crystalhd-dkms
 Version: 1:0.0~git20110715.fdd2f19-7
 Severity: critical
 Tags: patch
 Justification: breaks the whole system

 Reproducible NULL pointer BUG at
 crystalhd-0.0~git20110715.fdd2f19/driver/linux/crystalhd_misc.c:515,
 triggered by adobe flash plugin from dmo repo, ffmpeg, mplayer, bino or
 other, mostly on heavy ioq usage
 or after FETCH_TIMEOUT and/or unclosed driver HANDLEs.

 Does the maintainer or somebody on pkg-multimedia plan on fixing this RC
 bug?  If not I'll consider a NMU removing the dkms package from
 crystalhd source.

 Cheers,
 Julien


 Known linux-media Maintainers

 STAGING - CRYSTAL HD VIDEO DECODER
 M:Naren Sankar nsan...@broadcom.com
 M:Jarod Wilson ja...@wilsonet.com
 M:Scott Davilla davi...@4pi.com
 M:Manu Abraham abraham.m...@gmail.com

 seem to have left the Broadcom's legacy driver code, focusing on the new
 linux-media staging driver, but limited time,
 one stated lately on the linux-media/LKML, nothing read from the others.
 I could adapt it to new kernel releases the next 2-3 years, but nothing
 more, not a experienced kernel driver coder,
 no debian package/policy maintaining motivation because I do not use dkms or
 debian kernels packages.

 If my last patch applies to Your codebase in the debian git repository (mine
 is from git.linuxtv.org, according to the
 git changelog more advanced in the gstreamer plugin, merge?) You may
 consider it

 hotfixed

 and release with known multithreading (gstreamer based transcoders/matroska
 demuxers) and PM ACPI S3 issues?
 Has not crashed here any more, nor notable side effects with usual playback
 use cases, including Totem (gstreamer).

 y
 tom

 ___
 pkg-multimedia-maintainers mailing list
 pkg-multimedia-maintain...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers



--
~ Andres


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, breaking python entirely

2013-03-01 Thread Vincent Lefevre
On 2013-03-01 17:56:33 +0100, Sven Joachim wrote:
 Apparently this file should not have been in -minimal in the first
 place, and on i386 (and other architectures, it seems) it has been in
 python2.7 even in version 2.7.3-6.  But on amd64, it has been in
 python2.7-minimal which I find quite inexplicable.

Was the amd64 version built under the same conditions?

BTW, I haven't received any of your two mail messages, neither
directly from you (as my address was in the To/Cc field), nor
via the 702005.bugs.debian.org list (as I'm subscribed to this
bug). There isn't any trace of connection for these two messages
in the logs of my mail server. I've just received the Processed:
mail via the 702005.bugs.debian.org list. I'm replying by using
bts show --mbox 702005.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#700027: kfreebsd-kernel-headers: Redefinition of struct termios

2013-03-01 Thread Guillem Jover
On Fri, 2013-03-01 at 15:14:32 +0100, Julien Cristau wrote:
 On Thu, Feb  7, 2013 at 17:17:59 +0100, Guillem Jover wrote:
 
  I'm filing this to track the issue, and because I have to do some
  other stuff, if no one else has dealt with it by then I'll look into
  fixing and uploading the package.

 Any news or ETA?

I've to finish up a dpkg upload pre-aproval request, hopefully today,
and then will get into this during the weekend, so that I can finally
request an unblock request for the inetutils security fix.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701224: marked as done (Safely prevent adverse impact if im-switch was removed but not purged)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 17:47:28 +
with message-id e1ubu3m-je...@franck.debian.org
and subject line Bug#701224: fixed in im-config 0.21
has caused the Debian Bug report #701224,
regarding Safely prevent adverse impact if im-switch was removed but not purged
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.)


-- 
701224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: im-config
Severity: important

This is a forward of the Ubuntu bug https://launchpad.net/bugs/1101836

The fix of http://bugs.debian.org/701181 meant inserting of a line of
code which prevents that /etc/X11/Xsession.d/80im-switch keeps being
sourced if the im-switch package is removed but not purged. This is
essential for im-config to work correctly.

However, if a user who has modified 80im-switch does not update before
replacing im-switch with im-config, 80im-switch will keep being sourced
and with that affect the im-config functionality adversely. One way to
prevent that from happening is to let im-config at installation insert a
line as just mentioned into 80im-switch, if it's not there already.
Attached please find a modified debian/postinst file which does just
that, and which we are about to use in Ubuntu.

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
#!/bin/sh
# postinst script for im-config
# vim: set sts=4 expandtab:

set -e

# version just before wheezy release
# 4045a8eeb0e9226cdd9f8a121ccf4c04  80im-config_launch 0.3 (stable initial)
# 8a4829f935b5561ca6e61bec6eb3893f  80im-config_launch 0.3+squeeze1 (stable), 
0.4
# b243876a16f7b87c397ceef626098069  80im-config_launch 0.5
# 5ef27261ac38d704d8f766da19635461  80im-config_launch 0.6-0.17 (testing, 
unstable)

case $1 in
configure)
IM_SWITCH_HOOK=/etc/X11/Xsession.d/80im-switch
IM_SWITCH_DISABLE_CODE='[ -x /usr/bin/im-switch ] || return 0'
if [ -f $IM_SWITCH_HOOK ] 
 [ $( head -1 $IM_SWITCH_HOOK ) != $IM_SWITCH_DISABLE_CODE ] 
 [ $( sed -n 15p $IM_SWITCH_HOOK ) != $IM_SWITCH_DISABLE_CODE ]
then
echo Disabling conflicting hook file: $IM_SWITCH_HOOK ...
sed -i 1 i $IM_SWITCH_DISABLE_CODE $IM_SWITCH_HOOK
fi
IM_CONFIG_HOOK=/etc/X11/Xsession.d/80im-config_launch
if [ -f $IM_CONFIG_HOOK ]; then
IM_CONFIG_HOOK_MD5SUM=$(md5sum  $IM_CONFIG_HOOK|cut -d ' ' -f 1)
case $IM_CONFIG_HOOK_MD5SUM in

4045a8eeb0e9226cdd9f8a121ccf4c04|8a4829f935b5561ca6e61bec6eb3893f|b243876a16f7b87c397ceef626098069|5ef27261ac38d704d8f766da19635461)
rm -f $IM_CONFIG_HOOK
;;

*)
echo ERROR: Unknown hook file exists: $IM_CONFIG_HOOK. 2
;;
esac
fi
;;

abort-upgrade|abort-remove|abort-deconfigure)
;;

*)
echo postinst called with unknown argument \`$1' 2
exit 1
;;
esac

# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.

#DEBHELPER#

exit 0

---End Message---
---BeginMessage---
Source: im-config
Source-Version: 0.21

We believe that the bug you reported is fixed in the latest version of
im-config, 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 701...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Osamu Aoki os...@debian.org (supplier of updated im-config 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: Tue, 26 Feb 2013 23:04:39 +0900
Source: im-config
Binary: im-config
Architecture: source all
Version: 0.21
Distribution: unstable
Urgency: low
Maintainer: Osamu Aoki os...@debian.org
Changed-By: Osamu Aoki os...@debian.org
Description: 
 im-config  - Input method configuration framework
Closes: 701224
Changes: 
 im-config (0.21) unstable; urgency=low
 .
   * Disable im-switch hook script if im-switch package is removed
 and im-config is installed.  Closes: #701224
Checksums-Sha1: 
 4fd1b070838f2b28133ed9ece5b2d9e40cb44983 877 im-config_0.21.dsc
 537d2657883f6ca3107b2d19aa8aec716532ba26 32997 

Bug#697617: jenkins: remote code execution vulnerability

2013-03-01 Thread Salvatore Bonaccorso
Hi

On Tue, Jan 08, 2013 at 02:06:39AM +0900, Nobuhiro Ban wrote:
 Package: jenkins
 Version: 1.447.2+dfsg-2
 Severity: grave
 Tags: security
 
 Dear Maintainer,
 
 The upstream vendor announced a security advisory, that is rated
 critical severity.
 
 See: 
 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04

Are there any news on this issue?

Regards,
Salvatore


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: hplip: diff for NMU version 3.12.6-3.1

2013-03-01 Thread Debian Bug Tracking System
Processing control commands:

 tags -1 + pending
Bug #701185 [hplip] CVE-2013-0200: Insecure temporary files
Added tag(s) pending.

-- 
701185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701185
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#701185: hplip: diff for NMU version 3.12.6-3.1

2013-03-01 Thread Sebastian Ramacher
Control: tags -1 + pending
thanks

Dear maintainer,

I've prepared an NMU for hplip (versioned as 3.12.6-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards
-- 
Sebastian Ramacher
diff -Nru hplip-3.12.6/debian/changelog hplip-3.12.6/debian/changelog
--- hplip-3.12.6/debian/changelog	2012-06-24 08:49:45.0 +0200
+++ hplip-3.12.6/debian/changelog	2013-03-01 18:41:56.0 +0100
@@ -1,3 +1,12 @@
+hplip (3.12.6-3.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * debian/patches/CVE-2013-0200.patch: Fix CVE-2013-0200 by applying the
+patch from Red Hat. Additionally increase the buffers to mitigate an
+regression and a buffer overflow. (Closes: #701185)
+
+ -- Sebastian Ramacher sramac...@debian.org  Fri, 01 Mar 2013 18:21:48 +0100
+
 hplip (3.12.6-3) unstable; urgency=low
 
   * [!linux-any] --enable-libusb01_build
diff -Nru hplip-3.12.6/debian/patches/CVE-2013-0200.patch hplip-3.12.6/debian/patches/CVE-2013-0200.patch
--- hplip-3.12.6/debian/patches/CVE-2013-0200.patch	1970-01-01 01:00:00.0 +0100
+++ hplip-3.12.6/debian/patches/CVE-2013-0200.patch	2013-03-01 18:52:39.0 +0100
@@ -0,0 +1,98 @@
+Description: fix for CVE-2013-0200 (insecure temporary files)
+Origin: vendor, ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Workstation/en/os/SRPMS/hplip-3.12.4-4.el6.src.rpm
+Last-Update: 2013-03-01
+Bug-Debian: http://bugs.debian.org/701185
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=902163
+
+--- a/prnt/hpcups/HPCupsFilter.cpp
 b/prnt/hpcups/HPCupsFilter.cpp
+@@ -656,21 +656,24 @@
+ 
+ if (m_iLogLevel  SAVE_INPUT_RASTERS)
+ {
+-charszFileName[32];
++charszFileName[44];
+ memset(szFileName, 0, sizeof(szFileName));
+-snprintf (szFileName, sizeof(szFileName), /tmp/hpcupsfilterc_%d.bmp, current_page_number);
++snprintf (szFileName, sizeof(szFileName), /tmp/hpcupsfilterc_%d.bmp.XX, current_page_number);
+ if (cups_header.cupsColorSpace == CUPS_CSPACE_RGBW ||
+ cups_header.cupsColorSpace == CUPS_CSPACE_RGB)
+ {
+-cfp = fopen (szFileName, w);
+-chmod (szFileName, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
++		int fd = mkstemp (szFileName);
++		if (fd != -1)
++		cfp = fdopen (fd, w);
+ }
+ if (cups_header.cupsColorSpace == CUPS_CSPACE_RGBW ||
+ cups_header.cupsColorSpace == CUPS_CSPACE_K)
+ {
+-szFileName[17] = 'k';
+-kfp = fopen (szFileName, w);
+-chmod (szFileName, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
++		int fd;
++		snprintf (szFileName, sizeof(szFileName), /tmp/hpcupsfilterk_%d.bmp.XX, current_page_number);
++		fd = mkstemp (szFileName);
++		if (fd != -1)
++		kfp = fdopen (fd, w);
+ }
+ 
+ WriteBMPHeader (cfp, cups_header.cupsWidth, cups_header.cupsHeight, COLOR_RASTER);
+--- a/prnt/hpcups/SystemServices.cpp
 b/prnt/hpcups/SystemServices.cpp
+@@ -36,10 +36,12 @@
+ m_fp = NULL;
+ if (iLogLevel  SAVE_PCL_FILE)
+ {
+-charfname[32];
+-sprintf(fname, /tmp/hpcups_job%d.out, job_id);
+-m_fp = fopen(fname, w);
+-chmod(fname, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
++	int	fd;
++charfname[40];
++sprintf(fname, /tmp/hpcups_job%d.out.XX, job_id);
++	fd = mkstemp (fname);
++	if (fd != -1)
++	m_fp = fdopen(fd, w);
+ }
+ }
+ 
+--- a/prnt/hpijs/hpijs.cpp
 b/prnt/hpijs/hpijs.cpp
+@@ -96,13 +96,12 @@
+ 
+ if (pSS-m_iLogLevel  SAVE_PCL_FILE)
+ {
++	int	fd;
+ charszFileName[32];
+-	sprintf (szFileName, /tmp/hpijs_%d.out, getpid());
+-	pSS-outfp = fopen (szFileName, w);
+-	if (pSS-outfp)
+-	{
+-	chmod (szFileName, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
+-	}
++	sprintf (szFileName, /tmp/hpijs_%d.out.XX, getpid());
++	fd = mkstemp (szFileName);
++	if (fd != -1)
++	pSS-outfp = fdopen (fd, w);
+ }
+ }
+ 
+--- a/prnt/hpps/hppsfilter.c
 b/prnt/hpps/hppsfilter.c
+@@ -92,10 +92,12 @@
+ g_fp_outdbgps = NULL;
+ if (g_savepsfile  SAVE_PS_FILE)
+ {
++	int	fd;
+ charsfile_name[FILE_NAME_SIZE] = {0};
+-sprintf(sfile_name, DBG_PSFILE, szjob_id);
+-g_fp_outdbgps= fopen(sfile_name, w);
+-chmod(sfile_name, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
++sprintf(sfile_name, DBG_PSFILE .XX, szjob_id);
++	fd = mkstemp (sfile_name);
++	if (fd != -1)
++	g_fp_outdbgps = fdopen(fd, w);
+ }
+ }
+ 
diff -Nru hplip-3.12.6/debian/patches/series hplip-3.12.6/debian/patches/series
--- hplip-3.12.6/debian/patches/series	2012-06-24 08:51:04.0 +0200
+++ hplip-3.12.6/debian/patches/series	2013-03-01 14:45:50.0 +0100
@@ -26,3 +26,4 @@
 hp-mkuri-libnotify-so-4-support.dpatch
 hpaio-option-duplex.diff
 debian-changes
+CVE-2013-0200.patch


signature.asc

Bug#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()

2013-03-01 Thread thomas schorpp

On 01.03.2013 18:36, Andres Mejia wrote:

It looks like the crystalhd drivers are buggy with newer kernel
releases. I opt for removing the dkms package. I will do this over the
weekend.


Top posting on list and removal announce without valid bug report for Your 
claimed issue and any confirmation?

Driver does not behave different from linux 3.2...3.7.1 here, see my posts on 
the linux-media list, xbmc people?

y
tom




On Thu, Feb 28, 2013 at 4:52 PM, thomas schorpp
thomas.scho...@gmail.com wrote:

On 28.02.2013 20:41, Julien Cristau wrote:


On Thu, Jan 31, 2013 at 19:25:50 +0100, tom schorpp wrote:


Package: crystalhd-dkms
Version: 1:0.0~git20110715.fdd2f19-7
Severity: critical
Tags: patch
Justification: breaks the whole system

Reproducible NULL pointer BUG at
crystalhd-0.0~git20110715.fdd2f19/driver/linux/crystalhd_misc.c:515,
triggered by adobe flash plugin from dmo repo, ffmpeg, mplayer, bino or
other, mostly on heavy ioq usage
or after FETCH_TIMEOUT and/or unclosed driver HANDLEs.


Does the maintainer or somebody on pkg-multimedia plan on fixing this RC
bug?  If not I'll consider a NMU removing the dkms package from
crystalhd source.

Cheers,
Julien



Known linux-media Maintainers

STAGING - CRYSTAL HD VIDEO DECODER
M:Naren Sankar nsan...@broadcom.com
M:Jarod Wilson ja...@wilsonet.com
M:Scott Davilla davi...@4pi.com
M:Manu Abraham abraham.m...@gmail.com

seem to have left the Broadcom's legacy driver code, focusing on the new
linux-media staging driver, but limited time,
one stated lately on the linux-media/LKML, nothing read from the others.
I could adapt it to new kernel releases the next 2-3 years, but nothing
more, not a experienced kernel driver coder,
no debian package/policy maintaining motivation because I do not use dkms or
debian kernels packages.

If my last patch applies to Your codebase in the debian git repository (mine
is from git.linuxtv.org, according to the
git changelog more advanced in the gstreamer plugin, merge?) You may
consider it

hotfixed

and release with known multithreading (gstreamer based transcoders/matroska
demuxers) and PM ACPI S3 issues?
Has not crashed here any more, nor notable side effects with usual playback
use cases, including Totem (gstreamer).

y
tom



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#700530: qt frames empty

2013-03-01 Thread Christoph Egger
Hi!

Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org writes:
 Control: tag -1 moreinfo

 Hi! A new version of xorg-server has been uploaded [0]. This should fix this 
 issue. Would you mind checking that this is indeed the situation?

 [0] http://packages.qa.debian.org/x/xorg-server/news/20130223T151839Z.html

Jep fixed!

Christoph


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698294: [Pkg-puppet-devel] Bug#698294: diff for NMU 2.7.18-2.1

2013-03-01 Thread Anton Gladky
Hi,

I have rescheduled an upload for 15-days. Or you want me to cancel it
completely?

Anton

On 03/01/2013 12:45 PM, Stig Sandbeck Mathisen wrote:
 
 That patch was marked as Code Insufficient in the upstream bug tracker
 two weeks ago at http://projects.puppetlabs.com/issues/7680#note-18
 
 Please delay it until this is resolved by upstream.
 




signature.asc
Description: OpenPGP digital signature


Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, breaking python entirely

2013-03-01 Thread Sven Joachim
On 2013-03-01 18:35 +0100, Vincent Lefevre wrote:

 On 2013-03-01 17:56:33 +0100, Sven Joachim wrote:
 Apparently this file should not have been in -minimal in the first
 place, and on i386 (and other architectures, it seems) it has been in
 python2.7 even in version 2.7.3-6.  But on amd64, it has been in
 python2.7-minimal which I find quite inexplicable.

 Was the amd64 version built under the same conditions?

Only the maintainer can know that, since he built that version.

 BTW, I haven't received any of your two mail messages, neither
 directly from you (as my address was in the To/Cc field), nor
 via the 702005.bugs.debian.org list (as I'm subscribed to this
 bug). There isn't any trace of connection for these two messages
 in the logs of my mail server. I've just received the Processed:
 mail via the 702005.bugs.debian.org list. I'm replying by using
 bts show --mbox 702005.

I received error messages from GMX that the mails could not be
delivered, but unfortunately have deleted them already. :-(
If the problem persists, I'll forward it to the bug.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#700530: marked as done (qt frames remain empty in kfreebsd since -10 to -11 update)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 1 Mar 2013 16:39:30 -0300
with message-id 201303011639.38007.lisan...@debian.org
and subject line Re: Bug#700530: qt frames empty
has caused the Debian Bug report #700530,
regarding qt frames remain empty in kfreebsd since -10 to -11 update
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.)


-- 
700530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: qt4-x11
Version: 4:4.8.2+dfsg-11
Severity: serious

Hi!

  Since I updated my kfreebsd testing system yesterday all qt based
applications only show an empty window. I also get X Errors about SHM
which unfortunately sound like the fix for CVE-2013-0254. I personally
won't have time to work on that issue at least until end of next week,
sorry.

Christoph

X Error: BadAccess (attempt to access private resource denied) 10
  Extension:140 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x10a
X Error: BadShmSeg (invalid shared segment parameter) 148
  Extension:140 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0x15b
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x1c0001a


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 10.0-0-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Version: 4:4.8.2+dfsg-11

This wasn't a qt bug after all :-)

-- 
Los comentarios o respuestas sobre SL en tono absolutista solo hacen aparecer
a la comunidad SL como una sarta de fanáticos que viven dentro de un
tupperware.
 Pablo Di Noto - GrULiC

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#702005: [mailer-dae...@gmx.de] Mail delivery failed: returning message to sender

2013-03-01 Thread Sven Joachim
---BeginMessage---
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error. The following address
failed:

vinc...@vinc17.net:
domain has no mail exchangers



--- The header of the original message is following. ---

Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan
 (mrigmx001) with ESMTP (Nemesis) id 0LpihM-1Ui73Y2viQ-00fUnz for
 vinc...@vinc17.net; Fri, 01 Mar 2013 20:43:10 +0100
Received: (qmail invoked by alias); 01 Mar 2013 19:43:10 -
Received: from p4FC61365.dip.t-dialin.net (EHLO turtle.gmx.de) [79.198.19.101]
  by mail.gmx.net (mp010) with SMTP; 01 Mar 2013 20:43:10 +0100
X-Authenticated: #28250155
X-Provags-ID: V01U2FsdGVkX1/J2pBqhdXJZjBDyoruS73WBogIadf73yBjb+WnaQ
dg/0ozeU7OCcGW
Received: by turtle.gmx.de (Postfix, from userid 1000)
id 830803F4CE; Fri,  1 Mar 2013 20:43:07 +0100 (CET)
From: Sven Joachim svenj...@gmx.de
To: Vincent Lefevre vinc...@vinc17.net
Cc: 702...@bugs.debian.org
Subject: Re: Bug#702005: libpython2.7: Upgrade to libpython2.7 2.7.3-7 fails, 
breaking python entirely
References: 20130301160035.ga13...@xvii.vinc17.org
20130301160516.gd5...@xvii.vinc17.org 87hakv3wai@turtle.gmx.de
878v673vpa@turtle.gmx.de
20130301173557.ga17...@xvii.vinc17.org
Date: Fri, 01 Mar 2013 20:43:07 +0100
In-Reply-To: 20130301173557.ga17...@xvii.vinc17.org (Vincent Lefevre's
message of Fri, 1 Mar 2013 18:35:57 +0100)
Message-ID: 87k3pq3nzo@turtle.gmx.de
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.93 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Y-GMX-Trusted: 0


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

---End Message---


Processed: severity of 680436 is important

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 680436 important
Bug #680436 [src:sra-sdk] sra-sdk: FTBFS: gcc/i386/atomic32.h:125:5: error: 
impossible constraint in 'asm'
Severity set to 'important' from 'serious'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
680436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680436
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#606993: No response from maintainer

2013-03-01 Thread Emilien Klein
Hi Marco Rodrigues and the Python Applications Packaging Team,

The subdownloader package you co-maintain has a grave bug [0] which
resulted in the package being removed from Testing more than 2 years
ago.

This bug has been fixed in version 2.0.18 (4 releases later than
2.0.14 packaged in Debian).
I've patched that specific bug and uploaded a NMU to mentors.d.n [1],
please review and upload.

Additionally, as I didn't get any answer back from you on any of my
emails over the last 4 months, I am wondering if you are still willing
to maintain this package? I would be willing to give a helping hand,
and get the newest version packaged (the one currently packaged is 2.5
years old).

Cheers,
   +Emilien
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606993
[1] http://mentors.debian.net/package/subdownloader


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#698294: [Pkg-puppet-devel] Bug#698294: diff for NMU 2.7.18-2.1

2013-03-01 Thread micah anderson
Anton Gladky gl...@debian.org writes:

 Hi,

 I have rescheduled an upload for 15-days. Or you want me to cancel it
 completely?

 Anton

 On 03/01/2013 12:45 PM, Stig Sandbeck Mathisen wrote:
 
 That patch was marked as Code Insufficient in the upstream bug tracker
 two weeks ago at http://projects.puppetlabs.com/issues/7680#note-18
 
 Please delay it until this is resolved by upstream.

As far as I know, there is no 'DELAYED/until this is resolved by
upstream' queue :)

Uploading something that upstream has deemed insufficient code, even to
DELAYED-15 doesn't seem like the right thing to do, especially since
this places an arbitrary deadling on upstream.

I think it best to cancel this upload until we have a clear fix from
upstream.

I understand that this issue impacts you and you would like a
resolution, but I think that the right thing to do here is to speed up
that resolution with upstream. Figure out what it is that is
insufficient in the code and get that resolved. 

Once upstream is happy with the code, then we can look at what needs to
be done to get this into Debian.



pgpgaFlnG1M2t.pgp
Description: PGP signature


Bug#606993: No response from maintainer

2013-03-01 Thread Marco Rodrigues
Hi Emilien,

Which e-mail did you try to contact me? goth...@sapo.pt? That one I really
don't check it =(

I'm not so active lately unfortunately, but I'm glad you want to help to
maintain it. You can perhaps ask someone from the Python Apps Team to
upload it for you.

Thanks for the help.

Best regards.

--
Marco Rodrigues
http://www.marblehole.com


On Fri, Mar 1, 2013 at 9:03 PM, Emilien Klein emilien+deb...@klein.stwrote:

 Hi Marco Rodrigues and the Python Applications Packaging Team,

 The subdownloader package you co-maintain has a grave bug [0] which
 resulted in the package being removed from Testing more than 2 years
 ago.

 This bug has been fixed in version 2.0.18 (4 releases later than
 2.0.14 packaged in Debian).
 I've patched that specific bug and uploaded a NMU to mentors.d.n [1],
 please review and upload.

 Additionally, as I didn't get any answer back from you on any of my
 emails over the last 4 months, I am wondering if you are still willing
 to maintain this package? I would be willing to give a helping hand,
 and get the newest version packaged (the one currently packaged is 2.5
 years old).

 Cheers,
+Emilien
 [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606993
 [1] http://mentors.debian.net/package/subdownloader



Processed: notfound 700996 in 5.2.0-1

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Bit of a fudge, but marking as fixed in binNMUs of a found version won't 
 really work either :-|
 notfound 700996 5.2.0-1
Bug #700996 {Done: Matthias Klose d...@debian.org} [python3-bsddb3] 
python3-bsddb3: directory vs. symlink conflict: /usr/include/python3.2
No longer marked as found in versions python-bsddb3/5.2.0-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: fixed 700996 in 5.2.0-1+b1

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 fixed 700996 5.2.0-1+b1
Bug #700996 {Done: Matthias Klose d...@debian.org} [python3-bsddb3] 
python3-bsddb3: directory vs. symlink conflict: /usr/include/python3.2
Marked as fixed in versions python-bsddb3/5.2.0-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700996
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#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()

2013-03-01 Thread thomas schorpp

On 01.03.2013 18:36, Andres Mejia wrote:

It looks like the crystalhd drivers are buggy with newer kernel
releases. I opt for removing the dkms package. I will do this over the
weekend.


Driver is maintainable and supported up to at least Linux 3.8 series, when 
we'll have 4.0 in debian stable, 2015?

schorpp@tom3:/mnt/data/usr/local/src/crystalhd/driver/linux$ make clean
rm -f *.map *.list *.o *.ko crystalhd.mod.c crystalhd_lnx.o crystalhd_misc.o 
crystalhd_cmds.o crystalhd_hw.o crystalhd_linkfuncs.o crystalhd_fleafuncs.o 
crystalhd_flea_ddr.o
schorpp@tom3:/mnt/data/usr/local/src/crystalhd/driver/linux$
schorpp@tom3:/mnt/data/usr/local/src/crystalhd/driver/linux$ make
make -C /lib/modules/3.8.1/build 
SUBDIRS=/mnt/data/usr/local/src/crystalhd/driver/linux modules
make[1]: Entering directory `/mnt/data/usr/local/src/linux-laststable'
  CC [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd_lnx.o
  CC [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd_misc.o
  CC [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd_cmds.o
  CC [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd_hw.o
  CC [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd_linkfuncs.o
  CC [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd_fleafuncs.o
  CC [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd_flea_ddr.o
  LD [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd.mod.o
  LD [M]  /mnt/data/usr/local/src/crystalhd/driver/linux/crystalhd.ko
make[1]: Leaving directory `/mnt/data/usr/local/src/linux-laststable'
schorpp@tom3:/mnt/data/usr/local/src/crystalhd/driver/linux$

Builds without warnings with my patches.

schorpp@tom3:~$ uname -a
Linux tom3 3.8.1 #12 SMP PREEMPT Fri Mar 1 20:41:00 CET 2013 x86_64 GNU/Linux
schorpp@tom3:~$ hellobcm
starting up
Running DIL (3.22.0) Version
DtsDeviceOpen: Opening HW in mode 0
Clock set to 180
Setting Color Mode to 1
try calls done
Unable to open input file
DtsAllocIoctlData Error
schorpp@tom3:~$ dmesg |grep crystal
[6.426460] Loading crystalhd v3.10.1
[6.426515] crystalhd :03:00.0: Starting Device:0x1612
[6.429600] crystalhd :03:00.0: irq 51 for MSI/MSI-X
[   99.896730] crystalhd :03:00.0: Opening new user[0] handle
[  102.604770] crystalhd :03:00.0: Closing user[0] handle via ioctl with 
mode 1c200
[  243.648468] crystalhd :03:00.0: Opening new user[0] handle
[  246.325373] crystalhd :03:00.0: Closing user[0] handle via ioctl with 
mode 1c200
[  334.105537] crystalhd :03:00.0: Opening new user[0] handle
[  336.776957] crystalhd :03:00.0: Closing user[0] handle via ioctl with 
mode 1c200
[  510.322855] crystalhd :03:00.0: Opening new user[0] handle
[  510.577299] crystalhd :03:00.0: Closing user[0] handle with mode 
[  510.781740] crystalhd :03:00.0: Opening new user[0] handle
[  511.036308] crystalhd :03:00.0: Closing user[0] handle with mode 
[  511.240825] crystalhd :03:00.0: Opening new user[0] handle
[  513.801093] crystalhd :03:00.0: [FMT CH] PIB:0 ff 420 6 2d0 162 2d0 0 0 0
[  513.921604] crystalhd :03:00.0: MISSING 3 PICTURES
[  514.587208] crystalhd :03:00.0: Closing user[0] handle via ioctl with 
mode 1c200
[  535.989772] crystalhd :03:00.0: Opening new user[0] handle
[  536.244314] crystalhd :03:00.0: Closing user[0] handle with mode 
[  536.448772] crystalhd :03:00.0: Opening new user[0] handle
[  536.703282] crystalhd :03:00.0: Closing user[0] handle with mode 
[  536.907816] crystalhd :03:00.0: Opening new user[0] handle
[  539.435257] crystalhd :03:00.0: [FMT CH] PIB:0 ff 420 6 2d0 162 2d0 0 0 0
[  539.508317] crystalhd :03:00.0: MISSING 3 PICTURES
[  616.455975] crystalhd :03:00.0: Closing user[0] handle via ioctl with 
mode 1c200
schorpp@tom3:~$

Loads and runs with Totem and MPlayer.

root@tom3:~# lspci -vvv -s 03:00.0 |grep Sta
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- 
SERR+ PERR- INTx-
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
DevSta:CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkSta:Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- 
BWMgmt- ABWMgmt-
UESta:DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq+ ACSViol-
CESta:RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
Status:InProgress-
Status:NegoPending- InProgress-
root@tom3:~#

Some non-fatal pci errors, but lspci is usually reporting incorrectly here or 
my old pci-e host is pretty incompatible.

So no technical reasons to drop the package?

y
tom


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact 

Processed: Bug#700880 change of tags / pending

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 700880 + pending
Bug #700880 [dlume] dlume: Using ampersand results in loss of data for the 
contactfield where the ampersand is used
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700880
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#696075: marked as done (lcl-utils: directory vs. symlink mess after squeeze = wheezy upgrade: /etc/lazarus)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 20:48:57 +
with message-id e1ubwsz-0007zy...@franck.debian.org
and subject line Bug#696075: fixed in lazarus 0.9.30.4-5
has caused the Debian Bug report #696075,
regarding lcl-utils: directory vs. symlink mess after squeeze = wheezy 
upgrade: /etc/lazarus
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.)


-- 
696075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lcl-utils
Version: 0.9.30.4-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during an upgrade test with piuparts I noticed your package installs
files over an existing symlink, overwriting files from another package
in a way that is not detected by dpkg:

0m44.0s INFO: dirname part contains a symlink:
  /etc/lazarus/environmentoptions.xml != 
/etc/lazarus-0.9.30.4/environmentoptions.xml (lcl-utils)
  /etc/lazarus/helpoptions.xml != /etc/lazarus-0.9.30.4/helpoptions.xml 
(lcl-utils)

Looks like /etc/lazarus was a symlink in squeeze and is a
directory in wheezy. Note that dpkg intentionally does not replace
directories with symlinks and vice versa.

This creates a serious mess with the conffiles in /etc ...

There are also some obsolete conffiles (could be false positives due to
this symlinkmess), look at dpkg-maintscript-helper for easy cleanup:

  OBSOLETE CONFFILE /etc/lazarus/helpoptions.xml REGISTERED BY lcl-utils 
(MODIFIED)
  OBSOLETE CONFFILE /etc/lazarus/environmentoptions.xml REGISTERED BY lcl-utils 
(MODIFIED)

and there are files left on the system after purge:

0m46.6s INFO: Warning: Package purging left files on system:
  /etc/lazarus.bak/  not owned
  /etc/lazarus.bak/environmentoptions.xmlnot owned
  /etc/lazarus.bak/helpoptions.xml   not owned


I didn't look at the maintainer scripts or the package to analyze what's
going on (or what was intended to happen).


Cheers,

Andreas


lcl-utils_0.9.30.4-1.1.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: lazarus
Source-Version: 0.9.30.4-5

We believe that the bug you reported is fixed in the latest version of
lazarus, 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 696...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Abou Al Montacir abou.almonta...@sfr.fr (supplier of updated lazarus 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: Fri, 29 Jan 2013 19:28:00 +0100
Source: lazarus
Binary: lazarus-0.9.30.4 lazarus-src-0.9.30.4 lazarus-ide-0.9.30.4 
lazarus-ide-gtk2-0.9.30.4 lazarus-ide-qt4-0.9.30.4 lcl-0.9.30.4 
lcl-utils-0.9.30.4 lcl-units-0.9.30.4 lcl-nogui-0.9.30.4 lcl-gtk2-0.9.30.4 
lcl-qt4-0.9.30.4 lazarus-doc-0.9.30.4 lazarus lazarus-src lazarus-ide 
lazarus-ide-gtk2 lazarus-ide-qt4 lcl lcl-utils lcl-units lcl-nogui lcl-gtk2 
lcl-qt4 lazarus-doc
Architecture: source amd64 all
Version: 0.9.30.4-5
Distribution: unstable
Urgency: low
Maintainer: Carlos Laviola clavi...@debian.org
Changed-By: Abou Al Montacir abou.almonta...@sfr.fr
Description: 
 lazarus- IDE for Free Pascal - SDK dependency package
 lazarus-0.9.30.4 - IDE for Free Pascal - suite
 lazarus-doc - IDE for Free Pascal - documentation dependency package
 lazarus-doc-0.9.30.4 - IDE for Free Pascal - documentation
 lazarus-ide - IDE for Free Pascal - common IDE files dependency package
 lazarus-ide-0.9.30.4 - IDE for Free Pascal - common IDE files
 lazarus-ide-gtk2 - IDE for Free Pascal - GTK+ version
 lazarus-ide-gtk2-0.9.30.4 - IDE for Free Pascal - GTK+ version
 lazarus-ide-qt4 - IDE for Free Pascal - IDE build on top of Qt backend 
dependency p
 lazarus-ide-qt4-0.9.30.4 - IDE for Free Pascal - Qt version
 lazarus-src - IDE for Free Pascal - LCL source code dependency package
 lazarus-src-0.9.30.4 - IDE for Free Pascal - LCL source code
 lcl- Lazarus Components Library - LCL dependency package
 lcl-0.9.30.4 - Lazarus Components Library - LCL suite
 lcl-gtk2   - Lazarus Components Library - GTK+ backend dependency package
 lcl-gtk2-0.9.30.4 - Lazarus Components Library - GTK+ backend
 lcl-nogui  - Lazarus Components Library - 

Bug#698827: marked as done (src:lazarus: builds binaries not listed in d/control)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 20:48:57 +
with message-id e1ubwsz-0007zf...@franck.debian.org
and subject line Bug#698827: fixed in lazarus 0.9.30.4-5
has caused the Debian Bug report #698827,
regarding src:lazarus: builds binaries not listed in d/control
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.)


-- 
698827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:lazarus
Version: 0.9.30.4-1.1
Severity: serious
Justification: 1

The .dsc says

  Source: lazarus
  Binary: lazarus, lazarus-src, lazarus-ide, lazarus-ide-gtk2, lazarus-ide-qt4, 
lcl, lcl-utils, lcl-units, lcl-nogui, lcl-gtk2, lcl-qt4, lazarus-doc
  Architecture: all i386 powerpc sparc amd64 armel armhf
  Version: 0.9.30.4-1.1

but additional binaries were included in the upload:

/srv/ftp-master.debian.org/queue/done/2012/06/15/lazarus_0.9.30.4-1.1_amd64.changes:
Files: 
 3367d401c2dbbc8052f9457275de00bc 2522 devel optional lazarus_0.9.30.4-1.1.dsc
 31dba864805eb6a6b8ef930ccbc9fc75 29317 devel optional 
lazarus_0.9.30.4-1.1.debian.tar.gz
 7ec2fd5593ae628f0583478aab54f787 6034398 devel optional 
lazarus-ide-0.9.30.4_0.9.30.4-1.1_amd64.deb
 a60c964c9fe1fee870b6cb05d5964226 6582310 devel optional 
lazarus-ide-gtk2-0.9.30.4_0.9.30.4-1.1_amd64.deb
 8694c72ec212fedad6db2c0103a6c921 19548 devel optional 
lazarus-ide-qt4-0.9.30.4_0.9.30.4-1.1_amd64.deb
 a60327f2da60c9c5392f2de5b1689b72 19310 devel optional 
lcl-0.9.30.4_0.9.30.4-1.1_amd64.deb
 864d4e6c7282939c2bc90fba796b2ff9 5411864 devel optional 
lcl-utils-0.9.30.4_0.9.30.4-1.1_amd64.deb
 25834d816e0c6cc1fb3d008b6f179f95 29071554 devel optional 
lcl-units-0.9.30.4_0.9.30.4-1.1_amd64.deb
 c1a3b8f5de0a06fe207447987f37107a 48278 devel optional 
lcl-nogui-0.9.30.4_0.9.30.4-1.1_amd64.deb
 b1297dab0b5483bad53e32f80101e046 1324586 devel optional 
lcl-gtk2-0.9.30.4_0.9.30.4-1.1_amd64.deb
 bb60b085595eb36979ca1c9619ffa671 19520 devel optional 
lcl-qt4-0.9.30.4_0.9.30.4-1.1_amd64.deb
 34e5e6bf0862d90ee892fee538fa4075 19252 devel optional 
lazarus-ide_0.9.30.4-1.1_amd64.deb
 98aa5525b2f6102f2eecab27afd941e6 19270 devel optional 
lazarus-ide-gtk2_0.9.30.4-1.1_amd64.deb
 4146d65774aeaad3ebe0c0699edd4a8a 19314 devel optional 
lazarus-ide-qt4_0.9.30.4-1.1_amd64.deb
 a10ee72f72fa2c8b74f26e85731fb501 19216 devel optional 
lcl_0.9.30.4-1.1_amd64.deb
 71c49bd8856f5ff1e9078472bed9ee23 19242 devel optional 
lcl-utils_0.9.30.4-1.1_amd64.deb
 40ac96689339c74f8b65c42dcfa32a76 19246 devel optional 
lcl-units_0.9.30.4-1.1_amd64.deb
 8a2ce505a64918941d1fbd131147ea6b 19268 devel optional 
lcl-nogui_0.9.30.4-1.1_amd64.deb
 0bd5ae2b695c45e498bed3dae480ca90 19252 devel optional 
lcl-gtk2_0.9.30.4-1.1_amd64.deb
 6316b8ec83b3242a32b944eebaff5ef5 19282 devel optional 
lcl-qt4_0.9.30.4-1.1_amd64.deb
 5d2053bd7fba0484150bcdfd178ff58c 19746 devel optional 
lazarus-0.9.30.4_0.9.30.4-1.1_all.deb
 15f6039102c8c33231b66551f44f6223 14069226 devel optional 
lazarus-src-0.9.30.4_0.9.30.4-1.1_all.deb
 c4514cd1ee9f38f77ccd50597ed0ee61 2994074 doc optional 
lazarus-doc-0.9.30.4_0.9.30.4-1.1_all.deb
 cdeeff18bd5834778c5e78cef67e808a 19248 devel optional 
lazarus_0.9.30.4-1.1_all.deb
 aa9bec4f8f789e275d64f470c7309012 19296 devel optional 
lazarus-src_0.9.30.4-1.1_all.deb
 ff524cba64d0d039599820f5f4d899ae 19304 doc optional 
lazarus-doc_0.9.30.4-1.1_all.deb

Ansgar
---End Message---
---BeginMessage---
Source: lazarus
Source-Version: 0.9.30.4-5

We believe that the bug you reported is fixed in the latest version of
lazarus, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Abou Al Montacir abou.almonta...@sfr.fr (supplier of updated lazarus 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: Fri, 29 Jan 2013 19:28:00 +0100
Source: lazarus
Binary: lazarus-0.9.30.4 lazarus-src-0.9.30.4 lazarus-ide-0.9.30.4 
lazarus-ide-gtk2-0.9.30.4 lazarus-ide-qt4-0.9.30.4 lcl-0.9.30.4 
lcl-utils-0.9.30.4 lcl-units-0.9.30.4 lcl-nogui-0.9.30.4 lcl-gtk2-0.9.30.4 
lcl-qt4-0.9.30.4 lazarus-doc-0.9.30.4 lazarus lazarus-src lazarus-ide 
lazarus-ide-gtk2 

Bug#698828: marked as done (src:lazarus: regenerates debian/control during build)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 20:48:57 +
with message-id e1ubwsz-0007zf...@franck.debian.org
and subject line Bug#698827: fixed in lazarus 0.9.30.4-5
has caused the Debian Bug report #698827,
regarding src:lazarus: regenerates debian/control during build
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.)


-- 
698827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:lazarus
Severity: serious

In at least version 0.9.30.4-1.1 and 0.9.30.4-4 debian/rules has a target
debian-files that is called during binary builds that will regenerate
debian/control.

I expect this to be the reason for the problem reported in #698827.

Ansgar
---End Message---
---BeginMessage---
Source: lazarus
Source-Version: 0.9.30.4-5

We believe that the bug you reported is fixed in the latest version of
lazarus, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Abou Al Montacir abou.almonta...@sfr.fr (supplier of updated lazarus 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: Fri, 29 Jan 2013 19:28:00 +0100
Source: lazarus
Binary: lazarus-0.9.30.4 lazarus-src-0.9.30.4 lazarus-ide-0.9.30.4 
lazarus-ide-gtk2-0.9.30.4 lazarus-ide-qt4-0.9.30.4 lcl-0.9.30.4 
lcl-utils-0.9.30.4 lcl-units-0.9.30.4 lcl-nogui-0.9.30.4 lcl-gtk2-0.9.30.4 
lcl-qt4-0.9.30.4 lazarus-doc-0.9.30.4 lazarus lazarus-src lazarus-ide 
lazarus-ide-gtk2 lazarus-ide-qt4 lcl lcl-utils lcl-units lcl-nogui lcl-gtk2 
lcl-qt4 lazarus-doc
Architecture: source amd64 all
Version: 0.9.30.4-5
Distribution: unstable
Urgency: low
Maintainer: Carlos Laviola clavi...@debian.org
Changed-By: Abou Al Montacir abou.almonta...@sfr.fr
Description: 
 lazarus- IDE for Free Pascal - SDK dependency package
 lazarus-0.9.30.4 - IDE for Free Pascal - suite
 lazarus-doc - IDE for Free Pascal - documentation dependency package
 lazarus-doc-0.9.30.4 - IDE for Free Pascal - documentation
 lazarus-ide - IDE for Free Pascal - common IDE files dependency package
 lazarus-ide-0.9.30.4 - IDE for Free Pascal - common IDE files
 lazarus-ide-gtk2 - IDE for Free Pascal - GTK+ version
 lazarus-ide-gtk2-0.9.30.4 - IDE for Free Pascal - GTK+ version
 lazarus-ide-qt4 - IDE for Free Pascal - IDE build on top of Qt backend 
dependency p
 lazarus-ide-qt4-0.9.30.4 - IDE for Free Pascal - Qt version
 lazarus-src - IDE for Free Pascal - LCL source code dependency package
 lazarus-src-0.9.30.4 - IDE for Free Pascal - LCL source code
 lcl- Lazarus Components Library - LCL dependency package
 lcl-0.9.30.4 - Lazarus Components Library - LCL suite
 lcl-gtk2   - Lazarus Components Library - GTK+ backend dependency package
 lcl-gtk2-0.9.30.4 - Lazarus Components Library - GTK+ backend
 lcl-nogui  - Lazarus Components Library - no GUI backend dependency package
 lcl-nogui-0.9.30.4 - Lazarus Components Library - no GUI backend
 lcl-qt4- Lazarus Components Library - Qt backend dependency package
 lcl-qt4-0.9.30.4 - Lazarus Components Library - Qt backend
 lcl-units  - Lazarus Components Library - backend independent components depen
 lcl-units-0.9.30.4 - Lazarus Components Library - backend independent 
components
 lcl-utils  - Lazarus Components Library - command line build tools dependency
 lcl-utils-0.9.30.4 - Lazarus Components Library - command line build tools
Closes: 696075 698385 698827 698828
Changes: 
 lazarus (0.9.30.4-5) unstable; urgency=low
 .
   * Fix detection of user choice about migration of configuration to
 alternatives system. (Closes: Bug#698385, Bug#696075)
   * Pass LDFLAGS to the linker, removes many lintian warnings.
   * Removed auto-generation of debian/control during build process as required
 by policy. (Closes: Bug#698827, Bug#698828)
Checksums-Sha1: 
 afdd81576c4f4c6b19fb44912310a04e352edb73 3215 lazarus_0.9.30.4-5.dsc
 b0a028e961c8f285a76766012a71b779739ebcee 42599 lazarus_0.9.30.4-5.debian.tar.gz
 d0b3c45da3959c33133cffeba0dc815cd7bbae3e 6015222 
lazarus-ide-0.9.30.4_0.9.30.4-5_amd64.deb
 7ab2b023e257dac77e1cf19d3e02243b4ed29b91 6581468 

Bug#698828: marked as done (src:lazarus: regenerates debian/control during build)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 20:48:57 +
with message-id e1ubwsz-0007zl...@franck.debian.org
and subject line Bug#698828: fixed in lazarus 0.9.30.4-5
has caused the Debian Bug report #698828,
regarding src:lazarus: regenerates debian/control during build
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.)


-- 
698828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:lazarus
Severity: serious

In at least version 0.9.30.4-1.1 and 0.9.30.4-4 debian/rules has a target
debian-files that is called during binary builds that will regenerate
debian/control.

I expect this to be the reason for the problem reported in #698827.

Ansgar
---End Message---
---BeginMessage---
Source: lazarus
Source-Version: 0.9.30.4-5

We believe that the bug you reported is fixed in the latest version of
lazarus, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Abou Al Montacir abou.almonta...@sfr.fr (supplier of updated lazarus 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: Fri, 29 Jan 2013 19:28:00 +0100
Source: lazarus
Binary: lazarus-0.9.30.4 lazarus-src-0.9.30.4 lazarus-ide-0.9.30.4 
lazarus-ide-gtk2-0.9.30.4 lazarus-ide-qt4-0.9.30.4 lcl-0.9.30.4 
lcl-utils-0.9.30.4 lcl-units-0.9.30.4 lcl-nogui-0.9.30.4 lcl-gtk2-0.9.30.4 
lcl-qt4-0.9.30.4 lazarus-doc-0.9.30.4 lazarus lazarus-src lazarus-ide 
lazarus-ide-gtk2 lazarus-ide-qt4 lcl lcl-utils lcl-units lcl-nogui lcl-gtk2 
lcl-qt4 lazarus-doc
Architecture: source amd64 all
Version: 0.9.30.4-5
Distribution: unstable
Urgency: low
Maintainer: Carlos Laviola clavi...@debian.org
Changed-By: Abou Al Montacir abou.almonta...@sfr.fr
Description: 
 lazarus- IDE for Free Pascal - SDK dependency package
 lazarus-0.9.30.4 - IDE for Free Pascal - suite
 lazarus-doc - IDE for Free Pascal - documentation dependency package
 lazarus-doc-0.9.30.4 - IDE for Free Pascal - documentation
 lazarus-ide - IDE for Free Pascal - common IDE files dependency package
 lazarus-ide-0.9.30.4 - IDE for Free Pascal - common IDE files
 lazarus-ide-gtk2 - IDE for Free Pascal - GTK+ version
 lazarus-ide-gtk2-0.9.30.4 - IDE for Free Pascal - GTK+ version
 lazarus-ide-qt4 - IDE for Free Pascal - IDE build on top of Qt backend 
dependency p
 lazarus-ide-qt4-0.9.30.4 - IDE for Free Pascal - Qt version
 lazarus-src - IDE for Free Pascal - LCL source code dependency package
 lazarus-src-0.9.30.4 - IDE for Free Pascal - LCL source code
 lcl- Lazarus Components Library - LCL dependency package
 lcl-0.9.30.4 - Lazarus Components Library - LCL suite
 lcl-gtk2   - Lazarus Components Library - GTK+ backend dependency package
 lcl-gtk2-0.9.30.4 - Lazarus Components Library - GTK+ backend
 lcl-nogui  - Lazarus Components Library - no GUI backend dependency package
 lcl-nogui-0.9.30.4 - Lazarus Components Library - no GUI backend
 lcl-qt4- Lazarus Components Library - Qt backend dependency package
 lcl-qt4-0.9.30.4 - Lazarus Components Library - Qt backend
 lcl-units  - Lazarus Components Library - backend independent components depen
 lcl-units-0.9.30.4 - Lazarus Components Library - backend independent 
components
 lcl-utils  - Lazarus Components Library - command line build tools dependency
 lcl-utils-0.9.30.4 - Lazarus Components Library - command line build tools
Closes: 696075 698385 698827 698828
Changes: 
 lazarus (0.9.30.4-5) unstable; urgency=low
 .
   * Fix detection of user choice about migration of configuration to
 alternatives system. (Closes: Bug#698385, Bug#696075)
   * Pass LDFLAGS to the linker, removes many lintian warnings.
   * Removed auto-generation of debian/control during build process as required
 by policy. (Closes: Bug#698827, Bug#698828)
Checksums-Sha1: 
 afdd81576c4f4c6b19fb44912310a04e352edb73 3215 lazarus_0.9.30.4-5.dsc
 b0a028e961c8f285a76766012a71b779739ebcee 42599 lazarus_0.9.30.4-5.debian.tar.gz
 d0b3c45da3959c33133cffeba0dc815cd7bbae3e 6015222 
lazarus-ide-0.9.30.4_0.9.30.4-5_amd64.deb
 7ab2b023e257dac77e1cf19d3e02243b4ed29b91 6581468 

Bug#698827: marked as done (src:lazarus: builds binaries not listed in d/control)

2013-03-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 Mar 2013 20:48:57 +
with message-id e1ubwsz-0007zl...@franck.debian.org
and subject line Bug#698828: fixed in lazarus 0.9.30.4-5
has caused the Debian Bug report #698828,
regarding src:lazarus: builds binaries not listed in d/control
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.)


-- 
698828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:lazarus
Version: 0.9.30.4-1.1
Severity: serious
Justification: 1

The .dsc says

  Source: lazarus
  Binary: lazarus, lazarus-src, lazarus-ide, lazarus-ide-gtk2, lazarus-ide-qt4, 
lcl, lcl-utils, lcl-units, lcl-nogui, lcl-gtk2, lcl-qt4, lazarus-doc
  Architecture: all i386 powerpc sparc amd64 armel armhf
  Version: 0.9.30.4-1.1

but additional binaries were included in the upload:

/srv/ftp-master.debian.org/queue/done/2012/06/15/lazarus_0.9.30.4-1.1_amd64.changes:
Files: 
 3367d401c2dbbc8052f9457275de00bc 2522 devel optional lazarus_0.9.30.4-1.1.dsc
 31dba864805eb6a6b8ef930ccbc9fc75 29317 devel optional 
lazarus_0.9.30.4-1.1.debian.tar.gz
 7ec2fd5593ae628f0583478aab54f787 6034398 devel optional 
lazarus-ide-0.9.30.4_0.9.30.4-1.1_amd64.deb
 a60c964c9fe1fee870b6cb05d5964226 6582310 devel optional 
lazarus-ide-gtk2-0.9.30.4_0.9.30.4-1.1_amd64.deb
 8694c72ec212fedad6db2c0103a6c921 19548 devel optional 
lazarus-ide-qt4-0.9.30.4_0.9.30.4-1.1_amd64.deb
 a60327f2da60c9c5392f2de5b1689b72 19310 devel optional 
lcl-0.9.30.4_0.9.30.4-1.1_amd64.deb
 864d4e6c7282939c2bc90fba796b2ff9 5411864 devel optional 
lcl-utils-0.9.30.4_0.9.30.4-1.1_amd64.deb
 25834d816e0c6cc1fb3d008b6f179f95 29071554 devel optional 
lcl-units-0.9.30.4_0.9.30.4-1.1_amd64.deb
 c1a3b8f5de0a06fe207447987f37107a 48278 devel optional 
lcl-nogui-0.9.30.4_0.9.30.4-1.1_amd64.deb
 b1297dab0b5483bad53e32f80101e046 1324586 devel optional 
lcl-gtk2-0.9.30.4_0.9.30.4-1.1_amd64.deb
 bb60b085595eb36979ca1c9619ffa671 19520 devel optional 
lcl-qt4-0.9.30.4_0.9.30.4-1.1_amd64.deb
 34e5e6bf0862d90ee892fee538fa4075 19252 devel optional 
lazarus-ide_0.9.30.4-1.1_amd64.deb
 98aa5525b2f6102f2eecab27afd941e6 19270 devel optional 
lazarus-ide-gtk2_0.9.30.4-1.1_amd64.deb
 4146d65774aeaad3ebe0c0699edd4a8a 19314 devel optional 
lazarus-ide-qt4_0.9.30.4-1.1_amd64.deb
 a10ee72f72fa2c8b74f26e85731fb501 19216 devel optional 
lcl_0.9.30.4-1.1_amd64.deb
 71c49bd8856f5ff1e9078472bed9ee23 19242 devel optional 
lcl-utils_0.9.30.4-1.1_amd64.deb
 40ac96689339c74f8b65c42dcfa32a76 19246 devel optional 
lcl-units_0.9.30.4-1.1_amd64.deb
 8a2ce505a64918941d1fbd131147ea6b 19268 devel optional 
lcl-nogui_0.9.30.4-1.1_amd64.deb
 0bd5ae2b695c45e498bed3dae480ca90 19252 devel optional 
lcl-gtk2_0.9.30.4-1.1_amd64.deb
 6316b8ec83b3242a32b944eebaff5ef5 19282 devel optional 
lcl-qt4_0.9.30.4-1.1_amd64.deb
 5d2053bd7fba0484150bcdfd178ff58c 19746 devel optional 
lazarus-0.9.30.4_0.9.30.4-1.1_all.deb
 15f6039102c8c33231b66551f44f6223 14069226 devel optional 
lazarus-src-0.9.30.4_0.9.30.4-1.1_all.deb
 c4514cd1ee9f38f77ccd50597ed0ee61 2994074 doc optional 
lazarus-doc-0.9.30.4_0.9.30.4-1.1_all.deb
 cdeeff18bd5834778c5e78cef67e808a 19248 devel optional 
lazarus_0.9.30.4-1.1_all.deb
 aa9bec4f8f789e275d64f470c7309012 19296 devel optional 
lazarus-src_0.9.30.4-1.1_all.deb
 ff524cba64d0d039599820f5f4d899ae 19304 doc optional 
lazarus-doc_0.9.30.4-1.1_all.deb

Ansgar
---End Message---
---BeginMessage---
Source: lazarus
Source-Version: 0.9.30.4-5

We believe that the bug you reported is fixed in the latest version of
lazarus, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Abou Al Montacir abou.almonta...@sfr.fr (supplier of updated lazarus 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: Fri, 29 Jan 2013 19:28:00 +0100
Source: lazarus
Binary: lazarus-0.9.30.4 lazarus-src-0.9.30.4 lazarus-ide-0.9.30.4 
lazarus-ide-gtk2-0.9.30.4 lazarus-ide-qt4-0.9.30.4 lcl-0.9.30.4 
lcl-utils-0.9.30.4 lcl-units-0.9.30.4 lcl-nogui-0.9.30.4 lcl-gtk2-0.9.30.4 
lcl-qt4-0.9.30.4 lazarus-doc-0.9.30.4 lazarus lazarus-src lazarus-ide 
lazarus-ide-gtk2 

Bug#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()

2013-03-01 Thread Julien Cristau
On Fri, Mar  1, 2013 at 21:38:54 +0100, thomas schorpp wrote:

 So no technical reasons to drop the package?
 
Until and unless the driver is in mainline, there's every reason to drop
it.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()

2013-03-01 Thread Julien Cristau
On Fri, Mar  1, 2013 at 12:36:03 -0500, Andres Mejia wrote:

 It looks like the crystalhd drivers are buggy with newer kernel
 releases. I opt for removing the dkms package. I will do this over the
 weekend.
 
Thanks.

Julien


signature.asc
Description: Digital signature


Bug#698294: [Pkg-puppet-devel] Bug#698294: diff for NMU 2.7.18-2.1

2013-03-01 Thread Anton Gladky
Ok, I canceled the upload.

We cannot postpone Wheezy-release, waiting for every upstream's
decision. If the solution works, why should not it be applied?
Otherwise the package should be removed from testing.

Cheers,

Anton


On 03/01/2013 09:15 PM, micah anderson wrote:
 As far as I know, there is no 'DELAYED/until this is resolved by
 upstream' queue :)
 
 Uploading something that upstream has deemed insufficient code, even to
 DELAYED-15 doesn't seem like the right thing to do, especially since
 this places an arbitrary deadling on upstream.
 
 I think it best to cancel this upload until we have a clear fix from
 upstream.
 
 I understand that this issue impacts you and you would like a
 resolution, but I think that the right thing to do here is to speed up
 that resolution with upstream. Figure out what it is that is
 insufficient in the code and get that resolved. 
 
 Once upstream is happy with the code, then we can look at what needs to
 be done to get this into Debian.




signature.asc
Description: OpenPGP digital signature


Bug#698294: [Pkg-puppet-devel] Bug#698294: Bug#698294: diff for NMU 2.7.18-2.1

2013-03-01 Thread Russ Allbery
Anton Gladky gl...@debian.org writes:

 Ok, I canceled the upload.

 We cannot postpone Wheezy-release, waiting for every upstream's
 decision. If the solution works, why should not it be applied?
 Otherwise the package should be removed from testing.

The problem is mildly obscure (many Puppet manifests, including very
complex and non-trivial ones, will never trigger this error condition) and
absolutely does not warrant removing the package from testing.  In fact,
I'm tempted to downgrade it to important again, although if there is a
tested upstream fix, I'd be in favor of applying it for wheezy.

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()

2013-03-01 Thread thomas schorpp

On 01.03.2013 21:55, Julien Cristau wrote:

On Fri, Mar  1, 2013 at 21:38:54 +0100, thomas schorpp wrote:


So no technical reasons to drop the package?


Until and unless the driver is in mainline, there's every reason to drop
it.
 


Well, then drop all the other non-mainline drivers dkms packages, too.

This is getting unserious, I wish You all much fun with more root holes in
closed source vdpau GPU drivers.

Thanks to Broadcom for the nice effort.

Bye,
tom


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#681659: #681659 pidgin-facebookchat: unusable without facebook so belongs in contrib

2013-03-01 Thread Timo Juhani Lindfors
Hi,

interesting interpretation. Is this any different from the AIM, Google
Talk and MSN plugins of pidgin?

-Timo


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701182: avelsieve: diff for NMU version 1.9.9-2.4

2013-03-01 Thread gregor herrmann
tags 701182 + pending
thanks

Dear maintainer,

I've prepared an NMU for avelsieve (versioned as 1.9.9-2.4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   NP: Supertramp: It's A Long Road
diff -Nru avelsieve-1.9.9/debian/changelog avelsieve-1.9.9/debian/changelog
--- avelsieve-1.9.9/debian/changelog	2012-09-09 17:57:18.0 +0200
+++ avelsieve-1.9.9/debian/changelog	2013-03-01 22:38:17.0 +0100
@@ -1,3 +1,13 @@
+avelsieve (1.9.9-2.4) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix Uses deprecated/removed session_unregister PHP function:
+new patch avelsieve-changeset-1091.patch, taken from upstream svn:
+replace deprecated/removed PHP functions.
+(Closes: #701182)
+
+ -- gregor herrmann gre...@debian.org  Fri, 01 Mar 2013 22:38:05 +0100
+
 avelsieve (1.9.9-2.3) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru avelsieve-1.9.9/debian/patches/avelsieve-changeset-1091.patch avelsieve-1.9.9/debian/patches/avelsieve-changeset-1091.patch
--- avelsieve-1.9.9/debian/patches/avelsieve-changeset-1091.patch	1970-01-01 01:00:00.0 +0100
+++ avelsieve-1.9.9/debian/patches/avelsieve-changeset-1091.patch	2013-02-24 16:09:19.0 +0100
@@ -0,0 +1,151 @@
+Description: update deprecated/removed PHP functions
+Origin: upstream, http://email.uoa.gr/avelsieve/changeset/1091 ,
+ http://email.uoa.gr/avelsieve/changeset/1113
+Bug: http://email.uoa.gr/avelsieve/ticket/269
+Bug-Debian: http://bugs.debian.org/701182
+Author: avel
+Reviewed-by: gregor herrmann gre...@debian.org
+Last-Update: 2013-02-24
+Applied-Upstream: yes, cf. Origin
+
+--- a/include/managesieve.lib.php
 b/include/managesieve.lib.php
+@@ -139,13 +139,13 @@
+ unset($this-error_raw);
+ 
+ $this-line=fgets($this-fp,1024);
+-$this-token = split( , $this-line, 2);
++$this-token = preg_split('/ /', $this-line, 2);
+ 
+ if($this-token[0] == NO){
+ /* we need to try and extract the error code from here.  There are two possibilites: one, that it will take the form of:
+NO (y) zzz or, two, NO {y} zzz */
+ $this-x = 0;
+-list($this-ltoken, $this-mtoken, $this-rtoken) = split( , $this-line. , 3);
++list($this-ltoken, $this-mtoken, $this-rtoken) = preg_split('/ /', $this-line. , 3);
+ if($this-mtoken[0] == {){
+ while($this-mtoken[$this-x] != } or $this-err_len  1){
+ $this-err_len = substr($this-mtoken, 1, $this-x);
+@@ -233,7 +233,7 @@
+atleast true for timsieved as it sits in 2.1.16, if someone has a 
+BYE (REFERRAL ...) example for later timsieved please forward it to 
+me and I'll code it in proper-like! - mlof...@wgops.com */
+-$this-reftok = split( , $this-token[1], 3);
++$this-reftok = preg_split('/ /', $this-token[1], 3);
+ $this-refsv = substr($this-reftok[1], 0, -2);
+ $this-refsv = substr($this-refsv, 1);
+ 
+@@ -438,7 +438,7 @@
+ //response.  They repsond as follows: Cyrus timsieved v1.0.0 SASL={PLAIN,}
+ //So, if we see IMPLEMENTATION in the first line, then we are done.
+ 
+-if(ereg(IMPLEMENTATION,$this-line))
++if(preg_match('/IMPLEMENTATION/',$this-line))
+ {
+   //we're on the Cyrus V2 or Cyrus V3 sieve server
+   while(sieve::status($this-line) == F_DATA){
+@@ -454,7 +454,7 @@
+   } else {
+   $this-cap_type=auth;
+   }
+-  $this-modules = split( , $this-item[1]);
++  $this-modules = preg_split('/ /', $this-item[1]);
+   if(is_array($this-modules)){
+   foreach($this-modules as $m)
+   $this-capabilities[$this-cap_type][strtolower($m)]=true;
+@@ -488,7 +488,7 @@
+ $this-modules = substr($this-item[1], strpos($this-item[1], {),strlen($this-item[1])-1);
+ 
+ //then split again at the ,  stuff.
+-$this-modules = split($this-modules, , );
++$this-modules = preg_split('/, /', $this-modules);
+  
+ //fill up our $this-modules property
+ if(is_array($this-modules)){
+@@ -884,7 +884,7 @@
+   $cap_type=auth;
+   }
+ 
+-  $this-modules = split(' ', $this-item[1]);
++  $this-modules = preg_split('/ /', $this-item[1]);
+   if(is_array($this-modules)){
+   foreach($this-modules as $m) {
+   $this-capabilities[$cap_type][strtolower($m)]=true;
+--- a/include/html_main.inc.php
 b/include/html_main.inc.php
+@@ -227,7 +227,7 @@
+  */
+ function clear_avelsieve_messages() {
+ 

Processed: avelsieve: diff for NMU version 1.9.9-2.4

2013-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 701182 + pending
Bug #701182 [avelsieve] avelsieve: Uses deprecated/removed session_unregister 
PHP function
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
701182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701182
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#699305: nip2: sRGB.icm is non-free

2013-03-01 Thread Jay Berkenbilt
Stuart Prescott stuart.presc...@bristol.ac.uk wrote:

 Package: nip2
 Version: 7.28.4-1
 Severity: serious
 Justification: DFSG3: must allow derived works

 Dear Maintainer,

 The file share/nip2/data/sRGB.icm is not licensed under the
 same terms as the rest of this package -- it is a file from HP and is not
 distributed under a free licence.

 . . .

I have alerted upstream about this issue so they can track it.  Since
there are ongoing discussions about possibly changing the license and
since this is being ignored for wheezy, other than alerting upstream,
I'm not planning on taking any immediate action.

-- 
Jay Berkenbilt q...@debian.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#700923: [Secure-testing-team] Bug#700923: pacemaker: CVE-2013-0281

2013-03-01 Thread Yves-Alexis Perez
On mar., 2013-02-19 at 12:35 +0100, Moritz Muehlenhoff wrote:
 Package: pacemaker
 Severity: grave
 Tags: security
 Justification: user security hole
 
 Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-0281 for 
 details
 and a link to the upstream fix.
 
 Due to the Wheezy freeze please apply a minimal fix and request an unblock 
 with
 the release managers.
 

Hi Moritz and HA packagers,

I took a look at this one, Red Hat bug links to the following commit:
https://github.com/ClusterLabs/pacemaker/commit/564f7cc2a51dcd2f28ab12a13394f31be5aa3c93
 which has:

 commit 564f7cc2a51dcd2f28ab12a13394f31be5aa3c93
 Author: David Vossel dvos...@redhat.com
 Date:   Sat Jan 5 00:19:59 2013 -0600
 
 High: core: Internal tls api improvements for reuse with future LRMD tls 
 bac
 
  cib/callbacks.c|   13 +-
  cib/callbacks.h|6 +-
  cib/notify.c   |2 +-
  cib/remote.c   |  326 ++
  include/crm_internal.h |   36 ++-
  lib/cib/cib_remote.c   |  290 ++-
  lib/common/mainloop.c  |1 +
  lib/common/remote.c|  723 
 
  tools/crm_mon.c|2 +-
  9 files changed, 939 insertions(+), 460 deletions(-)
 
I'm not quite sure something like that can really be accepted by the
release team at that point…

I have no idea if it's possible to only pick the timeout-related
changes, maybe asking upstream would help on this.

Regards,
-- 
Yves-Alexis


signature.asc
Description: This is a digitally signed message part


Bug#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()

2013-03-01 Thread Andres Mejia
On Fri, Mar 1, 2013 at 3:55 PM, Julien Cristau jcris...@debian.org wrote:
 On Fri, Mar  1, 2013 at 21:38:54 +0100, thomas schorpp wrote:

 So no technical reasons to drop the package?

 Until and unless the driver is in mainline, there's every reason to drop
 it.

 Cheers,
 Julien

I just checked the crystalhd driver in the mainline kernel. The driver
seems to be much better maintained over there than at linuxtv.org. See
[1].

I'm going to drop the driver from linuxtv.org. If after I drop the
package someone has some compelling reason to use the driver from
linuxtv.org, they can submit another bug to the crystalhd package and
explain why the linuxtv.org driver should be used.

1. 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/staging/crystalhd

--
~ Andres


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#699744: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/stylesheets/outages.css

2013-03-01 Thread Russ Allbery
Based on the bug discussion, I believe this bug against nagios3-cgi should
be closed.  The problem is with the dpkg database, and it doesn't sound
like there's anything the package needs to (or should do) to deal with
that issue; it's fixed by either dealing with the prompt during upgrade or
reinstalling the package.

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#696445: nslcd: Discards local modifications in nslcd.conf without warning

2013-03-01 Thread Russ Allbery
Should this bug be downgraded until it can be confirmed as reproducible?
I also looked through the postinst script and, while it's complex, I
didn't see any obvious way in which it could produce the behavior
described here.

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#690410: Puredata 0.43.2-4 crashing due to _FORTIFY_SOURCE with large patch

2013-03-01 Thread Russ Allbery
At this point in the release process, I really think upgrading with
_FORTIFY_SOURCE disabled is the correct fix.  Just increasing a buffer
size is usually not a good idea; that's the sort of change that can paper
over a deeper problem without actually solving it, just temporarily hiding
it.  At the least, I think it would require more testing than we would be
able to do at this point.

My recommendation is to apply the change suggested in the bug log to
disable _FORTIFY_SOURCE for the wheezy release, and then, post-wheezy,
upload the package with _FORTIFY_SOURCE enabled and possibly with the
buffer size increased (maybe after discussion with upstream).

Does that sound like the right move?  Would it be helpful for someone to
assist with an NMU?

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#688634: roundcube-sqlite upgrade causes serious data-loss

2013-03-01 Thread Russ Allbery
Hello folks,

After reviewing the bug discussion, I believe the correct thing to do here
is to remove the roundcube-sqlite package from wheezy entirely.  That will
block an upgrade from squeeze by forcing the admin to realize that they
have to switch database backends, which is exactly the desired behavior
(since there's no automated conversion process available).  That's much
better than a release note, since it blocks the upgrade until the admin
decides what they want to do.

Having a transitional package only makes sense when there is an automated
transition available, and there isn't one here.  The admin is going to
have to take manual database actions, so we should fail the upgrade until
they've done that and are prepared for the transition.

Does that make sense?  Do you need any help preparing that for wheezy?

(Of course, in an ideal world there would be an automated upgrade process,
but we're too late in the release cycle to develop one now.)

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



  1   2   >