Bug#771406: libuuid1 postinst uses groupmod, but doesn't depend on passwd

[Ivo De Decker]

package: libuuid1
version: 2.25.2-3
severity: serious

Hi,

The postinst of libuuid1 uses the groupmod command in certain situations. This
only works if passwd is installed, but there is no dependency.

An example of the failure:

https://buildd.debian.org/status/fetch.php?pkg=qemuarch=amd64ver=2.1%2Bdfsg-8stamp=1417200448

Preparing to unpack .../libuuid1_2.25.2-3_amd64.deb ...
Unpacking libuuid1:amd64 (2.25.2-3) over (2.25.2-2) ...
Setting up libuuid1:amd64 (2.25.2-3) ...
/var/lib/dpkg/info/libuuid1:amd64.postinst: 15: 
/var/lib/dpkg/info/libuuid1:amd64.postinst: groupmod: not found
dpkg: error processing package libuuid1:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 libuuid1:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Cheers,

Ivo


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

Bug#769716: iceweasel: downloads Cisco's OpenH264 video codec

[Chuck Peters]

Mike Hommey said:
 
 a) it's not in any release of Debian, and it's not in any upcoming
 release of Debian either. It's in a package from experimental.

I had no idea I was running experimental packages on a machine with 
wheezy and a few wheezy-backports (openssh-server and 
debian-security-support).  I followed the directions at 
http://mozilla.debian.net/:
Add to sources.list:
deb http://mozilla.debian.net/ wheezy-backports iceweasel-release
$ apt-get update
$ apt-get install -t wheezy-backports iceweasel

So I have iceweasel 33.1-1~bpo70+1 installed.

And this confirms the binary blob.
$ ls -l ~/.mozilla/firefox/*/gmp-gmpopenh264/1.1
  
total 1000  
 
-rw-r--r-- 1 cp cp 114 Sep  2 16:36 gmpopenh264.info
 
-rwxr-xr-x 1 cp cp 1018138 Sep  2 16:37 libgmpopenh264.so  

 b) everyone knows what's actually contained in that binary blob, since
 it's built from open source code, and the build is (supposed to be)
 reproductible.

I'll assume you meant s/knows/can confirm/ because I certainly don't 
know.

 So it's not as bad as you make it sound.

That's good to know!  However I think many of us would be more 
comfortable if the Debian systems built the source.

http://www.openh264.org/faq.html explains that In order for Cisco to be 
responsible for the MPEG LA licensing royalties for the module, Cisco 
must provide the packaging and distribution of this code in a binary 
module format (think of it like a plug-in, but not using the same APIs 
as existing plugins), in addition to several other constraints.

http://www.mpegla.com/main/programs/M2/Pages/Agreement.aspx says the 
license fee would be $2.00 per unit.  

http://www.mpegla.com/main/programs/M2/Pages/Agreement.aspx also says:

License Term

Coverage is from June 1, 1994 through the expiration of the MPEG-2 
Patent Portfolio Patents and may be voluntarily terminated by the 
Licensee after December 31, 2015 (Sections 6.1 and 6.4).


If what I am reading is correct, unless someone gets a MPEG LA License 
that allows Debian to distribute the source and binaries we may not see 
it until 2016 or perhaps later...  According to 
https://en.wikipedia.org/wiki/Term_of_patent#United_States the patent 
term is over, so how is it more than 20 years and why can't Debian 
distribute it now, ie. after June 1, 2014?


Chuck


-- 
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#769216: fixed in django-guardian 1.2.4+git20141127-0.1

[Debian Bug Tracking System]

Processing control commands:

 reopen -1
Bug #769216 {Done: Brian May b...@debian.org} [src:djangorestframework] 
djangorestframework: FTBFS in jessie: unsatisfiable build-dependencies: 
python-django-guardian (= 1.1.1), python3-django-guardian (= 1.1.1)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions django-guardian/1.2.4+git20141127-0.1.

-- 
769216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769216
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#769216: fixed in django-guardian 1.2.4+git20141127-0.1

[Ivo De Decker]

Control: reopen -1

Hi,

On Thu, Nov 27, 2014 at 12:18:49AM +, Brian May wrote:
  django-guardian (1.2.4+git20141127-0.1) experimental; urgency=low

* Fix test errors. Closes: #769216.

It looks like you closed the wrong bug. You probably meant #763222

Cheers,

Ivo


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

Bug#763222: marked as done (django-guardian: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Thu, 27 Nov 2014 00:18:49 +
with message-id e1xtmnj-0008lj...@franck.debian.org
and subject line Bug#769216: fixed in django-guardian 1.2.4+git20141127-0.1
has caused the Debian Bug report #763222,
regarding django-guardian: FTBFS: Tests failures
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.)


-- 
763222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: django-guardian
Version: 1.2.4-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
 make[2]: Entering directory '/«PKGBUILDDIR»/docs'
 sphinx-build -b html -d build/doctrees   . build/html
 Making output directory...
 Running Sphinx v1.2.3
 [NOTE] In order to build PDF you need rst2pdf with version =0.16
 loading pickled environment... failed: [Errno 2] No such file or directory: 
 '/«PKGBUILDDIR»/docs/build/doctrees/environment.pickle'
 building [html]: targets for 32 source files that are out of date
 updating environment: 32 added, 0 changed, 0 removed
 reading sources... [  3%] api/guardian.admin
 reading sources... [  6%] api/guardian.backends
 reading sources... [  9%] api/guardian.core
 reading sources... [ 12%] api/guardian.decorators
 reading sources... [ 15%] api/guardian.forms
 reading sources... [ 18%] api/guardian.management.commands
 reading sources... [ 21%] api/guardian.managers
 reading sources... [ 25%] api/guardian.mixins
 reading sources... [ 28%] api/guardian.models
 reading sources... [ 31%] api/guardian.shortcuts
 reading sources... [ 34%] api/guardian.templatetags.guardian_tags
 reading sources... [ 37%] api/guardian.utils
 reading sources... [ 40%] api/index
 reading sources... [ 43%] configuration
 reading sources... [ 46%] develop/changes
 reading sources... [ 50%] develop/example_project
 reading sources... [ 53%] develop/index
 reading sources... [ 56%] develop/overview
 reading sources... [ 59%] develop/supported-versions
 reading sources... [ 62%] develop/testing
 reading sources... [ 65%] index
 reading sources... [ 68%] installation
 reading sources... [ 71%] license
 reading sources... [ 75%] overview
 reading sources... [ 78%] userguide/admin-integration
 reading sources... [ 81%] userguide/assign
 reading sources... [ 84%] userguide/caveats
 reading sources... [ 87%] userguide/check
 reading sources... [ 90%] userguide/custom-user-model
 reading sources... [ 93%] userguide/index
 reading sources... [ 96%] userguide/performance
 reading sources... [100%] userguide/remove
 
 /«PKGBUILDDIR»/guardian/core.py:docstring of 
 guardian.core.ObjectPermissionChecker:18: WARNING: Field list ends without a 
 blank line; unexpected unindent.
 /«PKGBUILDDIR»/guardian/forms.py:docstring of 
 guardian.forms.BaseObjectPermissionsForm:5: WARNING: Field list ends without 
 a blank line; unexpected unindent.
 /«PKGBUILDDIR»/guardian/shortcuts.py:docstring of 
 guardian.shortcuts.get_objects_for_user:18: WARNING: Field list ends without 
 a blank line; unexpected unindent.
 looking for now-outdated files... none found
 pickling environment... done
 checking consistency... done
 preparing documents... done
 writing output... [  3%] api/guardian.admin
 writing output... [  6%] api/guardian.backends
 writing output... [  9%] api/guardian.core
 writing output... [ 12%] api/guardian.decorators
 writing output... [ 15%] api/guardian.forms
 writing output... [ 18%] api/guardian.management.commands
 writing output... [ 21%] api/guardian.managers
 writing output... [ 25%] api/guardian.mixins
 writing output... [ 28%] api/guardian.models
 writing output... [ 31%] api/guardian.shortcuts
 writing output... [ 34%] api/guardian.templatetags.guardian_tags
 writing output... [ 37%] api/guardian.utils
 writing output... [ 40%] api/index
 writing output... [ 43%] configuration
 writing output... [ 46%] develop/changes
 writing output... [ 50%] develop/example_project
 writing output... [ 53%] develop/index
 writing output... [ 56%] develop/overview
 writing output... [ 59%] develop/supported-versions
 writing output... [ 62%] develop/testing
 writing output... [ 65%] index
 writing output... [ 68%] installation
 writing output... [ 71%] license
 writing output... [ 75%] overview
 writing output... [ 78%] userguide/admin-integration
 writing output... [ 81%] userguide/assign
 writing output... [ 84%] userguide/caveats
 writing output... [ 87%] userguide/check
 

Processed: severity of 771116 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 severity 771116 serious
Bug #771116 [bluedevil] [bluedevil] Typo in a dependency - bluez-obezd instead 
of bluez-obexd
Severity set to 'serious' from 'normal'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771116
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#771407: server startup fails

[Michael Meskes]

Package: dovecot-imapd
Version: 1:2.2.13-7
Severity: grave

The latest update comments out cert locations which makes the server fail to 
restart again:

dovecot: imap-login: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM 
routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY

This means that a running imap service is no longer running after the upgrade
and cannot even be manually started until the config file has been fixed by
hand again.

Michael

-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages dovecot-imapd depends on:
ii  dovecot-core  1:2.2.13-7
ii  libbz2-1.01.0.6-7+b1
ii  libc6 2.19-13
ii  liblzma5  5.1.1alpha+20120614-2+b2
ii  ucf   3.0030
ii  zlib1g1:1.2.8.dfsg-2+b1

dovecot-imapd recommends no packages.

dovecot-imapd suggests no packages.

Versions of packages dovecot-imapd is related to:
ii  dovecot-core [dovecot-common]  1:2.2.13-7
pn  dovecot-dbgnone
pn  dovecot-devnone
pn  dovecot-gssapi none
ii  dovecot-imapd  1:2.2.13-7
pn  dovecot-ldap   none
pn  dovecot-lmtpd  none
pn  dovecot-managesieved   none
pn  dovecot-mysql  none
pn  dovecot-pgsql  none
pn  dovecot-pop3d  none
pn  dovecot-sieve  none
pn  dovecot-sqlite none

-- no debconf information


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

Bug#771341: segfaults in sqlite3_value_type while using from Python

[GCS]

On Fri, Nov 28, 2014 at 5:50 PM, Yaroslav Halchenko
deb...@onerussian.com wrote:
 Package: libsqlite3-0
 Version: 3.7.13-1+deb7u1
 Severity: serious

 Originally detected I believe on sid installation, but forgot to capture the
 version, I will try to replicate/report later.  But very consistent with 
 wheezy
 (from which I am reporting now).
 May you give me some details how it happened in Sid?

 Triggered by the backport fail2ban 0.9.1-1~nd70+1 (available from
 http://neuro.debian.net/debian-devel/ wheezy/main amd64 Packages  apt repo) it
 gets to
[...]
 The problem is, I don't see the segfault in the mentioned gdb output.

 unfortunately we haven't logged the sql queries so not sure on exact one, but 
 I
 think it was this one, which if executed from the shell seems to not cause the
 segfault...

 n {1..100}; do sqlite3 -list fail2ban.sqlite3 'SELECT ip, timeofban, data 
 FROM bans WHERE 1 AND jail=sshd AND ip=111.74.239.35 ORDER BY ip, 
 timeofban' /dev/null  echo success; done
 Then how often do you get segfault? Do you have any additional
information if it happens in a given daytime, when there are several
bots try to get into your system or anything else?

 Please help me to troubleshoot this one if more information is necessary
 to point the issue
 I'm the SQLite3 maintainer and not the fail2ban one. But please note
the changelog the version you use[1]:
 - 0.9 series is quite a big leap in development, especially since 0.8.6
   which made it to previous Debian stable wheezy.  Please consult upstream
   ChangeLog about changes

Did you check it, reviewed your configuration? Does a segfault happen
in other applications that link to SQLite3?

Regards,
Laszlo/GCS
[1] https://packages.qa.debian.org/f/fail2ban/news/20141028T041852Z.html


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

Bug#770982: Patch

[Paulo Assis]

Hi,

This is fixed in version 0.2.5.
source packages (signed) can be found here:
https://drive.google.com/folderview?id=0B0_qxcVSvJFMOTcyOFJRNkFaWjAusp=sharing

If someone can upload this, it would be appreciated.

Regards,
Paulo

2014-11-28 23:37 GMT+00:00 Matt Kraai kr...@ftbfs.org:
 Control: tags -1 + patch

 Hi,

 Here's a patch, partially extracted from upstream, that includes
 dynctrl-logitech.h in libwebcam0-dev:

 diff -Nru libwebcam-0.2.4/debian/libwebcam0-dev.install 
 libwebcam-0.2.4/debian/libwebcam0-dev.install
 --- libwebcam-0.2.4/debian/libwebcam0-dev.install   2013-11-01 
 16:49:24.0 -0700
 +++ libwebcam-0.2.4/debian/libwebcam0-dev.install   2014-11-28 
 15:32:56.0 -0800
 @@ -1,3 +1,4 @@
 +usr/include/dynctrl-logitech.h
  usr/include/webcam.h
  usr/lib/libwebcam.a
  usr/lib/libwebcam.so
 diff -Nru libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h 
 libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h
 --- libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h   1969-12-31 
 16:00:00.0 -0800
 +++ libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h   2014-11-28 
 15:29:48.0 -0800
 @@ -0,0 +1,13 @@
 +Index: libwebcam-0.2.4/libwebcam/CMakeLists.txt
 +===
 +--- libwebcam-0.2.4.orig/libwebcam/CMakeLists.txt  2013-10-31 
 14:47:36.0 -0700
  libwebcam-0.2.4/libwebcam/CMakeLists.txt   2014-11-28 15:29:32.063070089 
 -0800
 +@@ -103,7 +103,7 @@
 + )
 +
 + install (
 +-  FILES   ../common/include/webcam.h
 ++  FILES   ../common/include/webcam.h 
 ../common/include/dynctrl-logitech.h
 +   DESTINATION ${CMAKE_INSTALL_PREFIX}/include
 + )
 +
 diff -Nru libwebcam-0.2.4/debian/patches/series 
 libwebcam-0.2.4/debian/patches/series
 --- libwebcam-0.2.4/debian/patches/series   2013-11-01 16:49:24.0 
 -0700
 +++ libwebcam-0.2.4/debian/patches/series   2014-11-28 15:29:13.0 
 -0800
 @@ -0,0 +1 @@
 +install-dynctrl-logitech.h

 Would you like me to sponsor an upload containing it (or something
 like it)?

 --
 Matt


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

Bug#771417: bogus dpkg error, now endless loop on dbus configuration

[Eduard Bloch]

Package: dpkg
Version: 1.17.22
Severity: grave

Hello,

today I tried to dist-upgrade my system (sid) starting from a package
state of a couple of weeks ago. First apt reported a failed dpkg right
in the middle of the upgrade process without displaying any visible
error messages. Now when I run apt-get -f install or attempt to
install some missing package explicitly, it ends up in a loop where dpkg
runs maintainer scripts on dbus without end. Here is dpkg.log and some
console output:

2014-11-29 11:23:24 startup archives unpack
2014-11-29 11:23:28 upgrade debianutils:amd64 4.4 4.4+b1
2014-11-29 11:23:28 status half-configured debianutils:amd64 4.4
2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4
2014-11-29 11:23:28 status half-installed debianutils:amd64 4.4
2014-11-29 11:23:28 status triggers-pending man-db:amd64 2.7.0.2-2
2014-11-29 11:23:28 status half-installed debianutils:amd64 4.4
2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4+b1
2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4+b1
2014-11-29 11:23:28 trigproc man-db:amd64 2.7.0.2-2 keine
2014-11-29 11:23:28 status half-configured man-db:amd64 2.7.0.2-2
2014-11-29 11:23:31 status installed man-db:amd64 2.7.0.2-2
2014-11-29 11:23:32 startup packages configure
2014-11-29 11:23:32 configure debianutils:amd64 4.4+b1 keine
2014-11-29 11:23:32 status unpacked debianutils:amd64 4.4+b1
2014-11-29 11:23:32 status half-configured debianutils:amd64 4.4+b1
2014-11-29 11:23:32 status installed debianutils:amd64 4.4+b1
2014-11-29 11:23:32 startup archives unpack
2014-11-29 11:23:33 upgrade bash:amd64 4.3-11 4.3-11+b1
2014-11-29 11:23:33 status half-configured bash:amd64 4.3-11
2014-11-29 11:23:33 status unpacked bash:amd64 4.3-11
2014-11-29 11:23:33 status half-installed bash:amd64 4.3-11
2014-11-29 11:23:33 status triggers-pending menu:amd64 2.1.47
2014-11-29 11:23:33 status half-installed bash:amd64 4.3-11
2014-11-29 11:23:33 status triggers-pending install-info:amd64 5.2.0.dfsg.1-5
2014-11-29 11:23:33 status triggers-pending man-db:amd64 2.7.0.2-2
2014-11-29 11:23:34 status half-installed bash:amd64 4.3-11
2014-11-29 11:23:34 status triggers-awaited menu:amd64 2.1.47
2014-11-29 11:23:34 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:34 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:34 trigproc menu:amd64 2.1.47 keine
2014-11-29 11:23:34 status half-configured menu:amd64 2.1.47
2014-11-29 11:23:36 status installed menu:amd64 2.1.47
2014-11-29 11:23:36 trigproc install-info:amd64 5.2.0.dfsg.1-5 keine
2014-11-29 11:23:36 status half-configured install-info:amd64 5.2.0.dfsg.1-5
2014-11-29 11:23:38 status installed install-info:amd64 5.2.0.dfsg.1-5
2014-11-29 11:23:38 trigproc man-db:amd64 2.7.0.2-2 keine
2014-11-29 11:23:38 status half-configured man-db:amd64 2.7.0.2-2
2014-11-29 11:23:39 status installed man-db:amd64 2.7.0.2-2
2014-11-29 11:23:40 startup packages configure
2014-11-29 11:23:40 configure bash:amd64 4.3-11+b1 keine
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status half-configured bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status installed bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status triggers-pending menu:amd64 2.1.47
2014-11-29 11:23:40 status triggers-awaited menu:amd64 2.1.47
2014-11-29 11:23:40 trigproc menu:amd64 2.1.47 keine
2014-11-29 11:23:40 status half-configured menu:amd64 2.1.47
2014-11-29 11:23:42 status installed menu:amd64 2.1.47
2014-11-29 11:23:43 startup archives unpack
2014-11-29 11:23:44 upgrade bsdutils:amd64 1:2.25.2-2 1:2.25.2-3
2014-11-29 11:23:44 status half-configured bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status unpacked bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status half-installed bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status triggers-pending man-db:amd64 2.7.0.2-2
2014-11-29 11:23:44 status half-installed bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status unpacked bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:44 status unpacked bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:44 trigproc man-db:amd64 2.7.0.2-2 keine
2014-11-29 11:23:44 status half-configured man-db:amd64 2.7.0.2-2
2014-11-29 11:23:45 status installed man-db:amd64 2.7.0.2-2
2014-11-29 11:23:46 startup packages configure
2014-11-29 11:23:46 configure bsdutils:amd64 1:2.25.2-3 keine
2014-11-29 11:23:46 status unpacked bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:46 status half-configured bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:46 status installed bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:46 startup archives unpack
2014-11-29 11:23:47 upgrade libc-dev-bin:amd64 2.19-12 2.19-13
2014-11-29 11:23:47 status half-configured libc-dev-bin:amd64 2.19-12
2014-11-29 11:23:47 status unpacked libc-dev-bin:amd64 2.19-12
2014-11-29 11:23:47 status 

Bug#769100: marked as done (htcondor: unowned directory after purge (policy 6.8) violating FHS (policy 9.1) too: /var/cred_dir/)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 11:34:20 +
with message-id e1xugi8-0004r3...@franck.debian.org
and subject line Bug#769100: fixed in condor 8.2.3~dfsg.1-4
has caused the Debian Bug report #769100,
regarding htcondor: unowned directory after purge (policy 6.8) violating FHS 
(policy 9.1) too: /var/cred_dir/
to be marked as done.

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

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


-- 
769100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: htcondor
Version: 8.2.3~dfsg.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

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

0m40.7s ERROR: FAIL: Package purging left files on system:
  /var/cred_dir/ not owned

As putting stuff directly into /var also a violation of
http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1
I'm setting the severity to serious.


cheers,

Andreas


htcondor_8.2.3~dfsg.1-3.log.gz
Description: application/gzip
---End Message---
---BeginMessage---
Source: condor
Source-Version: 8.2.3~dfsg.1-4

We believe that the bug you reported is fixed in the latest version of
condor, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 769...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Hanke m...@debian.org (supplier of updated condor package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 29 Nov 2014 09:57:27 +0100
Source: condor
Binary: htcondor htcondor-dev htcondor-doc htcondor-dbg libclassad-dev 
libclassad7 condor condor-doc condor-dev condor-dbg
Architecture: source amd64 all
Version: 8.2.3~dfsg.1-4
Distribution: unstable
Urgency: medium
Maintainer: HTCondor Developers condor-deb...@cs.wisc.edu
Changed-By: Michael Hanke m...@debian.org
Description:
 condor - transitional dummy package
 condor-dbg - transitional dummy package
 condor-dev - transitional dummy package
 condor-doc - transitional dummy package
 htcondor   - distributed workload management system
 htcondor-dbg - distributed workload management system - debugging symbols
 htcondor-dev - distributed workload management system - development files
 htcondor-doc - distributed workload management system - documentation
 libclassad-dev - HTCondor classads expression language - development library
 libclassad7 - HTCondor classads expression language - runtime library
Closes: 766067 769100
Changes:
 condor (8.2.3~dfsg.1-4) unstable; urgency=medium
 .
   * Adjust mechanism to apply the default Debian configuration to cope with
 the removal of the monolithic configuration file in the 8.2.x series.
 The default configuration is now applied as a patch to the table of
 parameters in the HTCondor sources (Closes: #769100).
 The report of leaving behind an unowned directory is merely a symptom of
 this bug.
   * Adjust default configuration to make HTCondor work with Debian's
 ganglia (also see Ticket #4709). Thanks to Alex Waite for the fix.
   * Add Debconf template translation:
 - Dutch -- courtesy of Frans Spiesschaert frans.spiesscha...@yucom.be.
   (Closes: #766067)
Checksums-Sha1:
 0d90d0e8629ba92aad54db4cf5300c2713080d9a 3023 condor_8.2.3~dfsg.1-4.dsc
 6284f57724861ddee1ba81fdfe36d77a841aee37 69472 
condor_8.2.3~dfsg.1-4.debian.tar.xz
 a45d6cb57236889cc95651d9ccaef2e72359d72d 3999206 
htcondor_8.2.3~dfsg.1-4_amd64.deb
 5f538b5df8d370d6abae5a69f14ebc9982d16c77 267732 
htcondor-dev_8.2.3~dfsg.1-4_amd64.deb
 fd811b9087cc88b32f14f5221b78f007c716ea33 1025738 
htcondor-doc_8.2.3~dfsg.1-4_all.deb
 392a6a00b3e6dac9f5d92cf79d5fc284628b7e0b 33370284 
htcondor-dbg_8.2.3~dfsg.1-4_amd64.deb
 196d48e811fd0a8417fca1e8695577ef6cc7dc4f 247466 
libclassad-dev_8.2.3~dfsg.1-4_amd64.deb
 b000f43fd5d18fcbcf490d4bc6c59751dead4fb8 197732 
libclassad7_8.2.3~dfsg.1-4_amd64.deb
 fbb7aeba4d0f607e4f87939f5a45b85139bea364 14206 condor_8.2.3~dfsg.1-4_all.deb
 

Processed: tagging 562907

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 562907 + wontfix
Bug #562907 {Done: Andrew Starr-Bochicchio a...@debian.org} 
[python-lightblue] missing dependency on pybluez
Added tag(s) wontfix.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
562907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562907
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#762672: qt-at-spi: when this package is installed, other programs fail to run

[Samuel Thibault]

Control: severity -1 important

Hello,

lightdm-gtk-greeter has been fixed, both in Debian with a small hack,
and upstream with proper at-spi termination.  I believe the severity of
this bug can thus be downgraded to important, since it will not show up
in any normal conditions any more.

Samuel


-- 
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#762672: qt-at-spi: when this package is installed, other programs fail to run

[Debian Bug Tracking System]

Processing control commands:

 severity -1 important
Bug #762672 [qt-at-spi] qt-at-spi: when this package is installed, other 
programs fail to run
Severity set to 'important' from 'critical'

-- 
762672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762672
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: Fix security problems with cache directories

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 770689 + pending
Bug #770689 [python-pycuda] python-pycuda: Insecure temporary file creation for 
kernel cache
Added tag(s) pending.
 tags 770692 + pending
Bug #770692 [python-pyopencl] python-pyopencl: Insecure temporary file creation 
for kernel cache
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
770689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770689
770692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770692
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#727800: kmail: KMail goes bonkers following Qt update

[Shai Berger]

Hi, 

On Wednesday 26 November 2014 15:21:15 you wrote:
 
 Hi! As Sandro pointed out, this seems fixed in newer versions. Can you
 please test if this is still an issue for you?
 

I have no means to reconstruct the update as it was. I am using two systems: 
One of them is a sid which I keep updating. Upgrades ever since that woefull 
upgrade have been smooth as far as I can tell, although I haven't been 
watching closely -- ever since kmail2 came into sid, mail there has not been 
really reliable, so if I suddenly have a couple hundred more unread mails, I 
don't think I'd notice. The filters haven't been broken again, as far as I can 
remember.

The other system is mostly testing, but since I use kmail for all my critical 
mail, and kmail2 has not been production-ready (at least before 4.14, though I 
find it hard to trust even now) I have pinned kmail there; I am writing this 
message from kmail 1.13.7 on kde 4.14.2. 

I can try to copy the user from testing to sid and see how the upgrade goes, 
although this would be a lengthy process; would that be helpful?

On a side note -- I see that mails sent to the bug are no longer sent to the 
submitter automatically (except when sent to -submitter specifically); is 
this on purpose? It is a bit of a problem. Feel free to include my address 
explicitly in replies.

Thanks,
Shai.


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

Bug#768695: Bug #768695: statsmodels: FTBFS in jessie: ImportError: cannot import name DateRange

[Michael Banck]

Hi,

On Wed, Nov 26, 2014 at 11:57:41PM +0100, Michael Banck wrote:
 On Wed, Nov 26, 2014 at 05:47:57PM -0500, Yaroslav Halchenko wrote:
  Upload it without delay, and let's hope none off those  doesn't veil
  the actual problem in the code :-) 
 
 OK, I will sponsor that upload as well tomorrow.

Unfortunately, I did not get around to that yet, but was looking now.

The problem is: As -1.1 has already been uploaded and accepted in the
archive, what we need is -1.2 patch on top of that with a new changelog
and everything.

Tomasz, I will try to extract that from your two NMU diffs later today
if you don't get around sending a new patch until then.


Michael


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

Bug#770962: marked as done (X2Go Client: session profile dialog box too big)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 13:19:27 +
with message-id e1xuhvr-0003e6...@franck.debian.org
and subject line Bug#770962: fixed in x2goclient 4.0.3.1-1
has caused the Debian Bug report #770962,
regarding X2Go Client: session profile dialog box too big
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.)


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

Package: x2goclient
Version: 4.0.3.0-1
Severity: grave
X-Debbugs-Cc: o.schney...@phoca-gmbh.de

On smaller screens (1152x864 and below) or for people that run X11  
sessions with high DPI values (a11y) it is impossible to properly edit  
X2Go Session profiles with X2Go Client. Reason: the Settings tab of  
the session profile dialog box got clobbered with too many (new)  
session settings.


I already discussed this issue with upstream (Oleksandr Shneyder) and  
I am still waiting for a fixing commit to the upstream Git of X2Go  
Client.


For X2Go Client it is essential that one can thoroughly edit the  
session profile's Settings tab, thus marking this issue as grave.


Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpIlRAVDqsNH.pgp
Description: Digitale PGP-Signatur
---End Message---
---BeginMessage---
Source: x2goclient
Source-Version: 4.0.3.1-1

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

Debian distribution maintenance software
pp.
Mike Gabriel sunwea...@debian.org (supplier of updated x2goclient package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 27 Nov 2014 11:09:10 +0100
Source: x2goclient
Binary: x2goclient x2goplugin x2goplugin-provider x2goclient-dbg x2goplugin-dbg
Architecture: source amd64 all
Version: 4.0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: X2Go Packaging Team pkg-x2go-de...@lists.alioth.debian.org
Changed-By: Mike Gabriel sunwea...@debian.org
Description:
 x2goclient - X2Go Client application (Qt4)
 x2goclient-dbg - X2Go Client application (Qt4), debug symbols (client)
 x2goplugin - X2Go Client (Qt4) as browser plugin
 x2goplugin-dbg - X2Go Client application (Qt4), debug symbols (plugin)
 x2goplugin-provider - Provide X2Go Plugin via Apache webserver
Closes: 770962 770963
Changes:
 x2goclient (4.0.3.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix (cross-)user desktop sharing / helpdesk functionality (Closes:
   #770963).
 - Split up session profile dialog's Settings tab into a Input/Output
   tab and a media tab (Closes: #770962).
 - If a session broker is used with X2Go Client, allow configuration of
   audio settings through the broker.
 - Greatly improved man page.
 - Updated (upstream) translation files.
Checksums-Sha1:
 979026d4504a127eb0e6ecc08c18dc65542719e9 2346 x2goclient_4.0.3.1-1.dsc
 3f9e8932fa211fac725ef0b77d32b1a66f83bc3d 1539521 x2goclient_4.0.3.1.orig.tar.gz
 dfffa68fef69add529ff836af35ecadef5300c8f 310244 
x2goclient_4.0.3.1-1.debian.tar.xz
 933554d2f6d7fc05abdf4f54305f7e9b0a8e6b31 1189494 x2goclient_4.0.3.1-1_amd64.deb
 338cd5a7f9852ef07dcb5950fdfd67d02df4b43e 1205998 x2goplugin_4.0.3.1-1_amd64.deb
 31162c8367f8286eff3ca26250c10be3e6fed5e7 25840 
x2goplugin-provider_4.0.3.1-1_all.deb
 a6a026df3c085a242b23b2f44716cb99dcc5d36d 2883914 
x2goclient-dbg_4.0.3.1-1_amd64.deb
 90d1189a98541ad2c1bf98ee1833e554ae6304ed 3188160 
x2goplugin-dbg_4.0.3.1-1_amd64.deb
Checksums-Sha256:
 3421dea46e8fd007297b7a72e381f196e622e7dbeb6ece827d37772af58cb29f 2346 
x2goclient_4.0.3.1-1.dsc
 8a5a0d8112250ecc598a9811253081d16f87c17d0707e8f09671c7cb31942bad 1539521 
x2goclient_4.0.3.1.orig.tar.gz
 acba993860b95b38ea188d45a5a3024ede9e1f3c7f45ec030eb496a6d401ac02 310244 
x2goclient_4.0.3.1-1.debian.tar.xz
 99d50d4064b16ff70896574d50e8876ac9b3de90a73409c76836beefdf39af59 1189494 

Bug#770963: marked as done (X2Go Client: desktop sharing broken)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 13:19:27 +
with message-id e1xuhvr-0003ec...@franck.debian.org
and subject line Bug#770963: fixed in x2goclient 4.0.3.1-1
has caused the Debian Bug report #770963,
regarding X2Go Client: desktop sharing broken
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.)


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

Package: x2goclient
Version: 4.0.3.0-1
Severity: grave
Tag: patch

Recently in upstream we discovered that X2Go Client's desktop sharing  
feature is completely broken in 4.0.3.0 of X2Go Client (since the new  
clipboard mode feature got added).


A fix is available upstream [1].

Mike

[1]  
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=b6d31bace19ea693486f5db7c76314bea071fb58


--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpCTYrrNf3Pr.pgp
Description: Digitale PGP-Signatur
---End Message---
---BeginMessage---
Source: x2goclient
Source-Version: 4.0.3.1-1

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

Debian distribution maintenance software
pp.
Mike Gabriel sunwea...@debian.org (supplier of updated x2goclient package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 27 Nov 2014 11:09:10 +0100
Source: x2goclient
Binary: x2goclient x2goplugin x2goplugin-provider x2goclient-dbg x2goplugin-dbg
Architecture: source amd64 all
Version: 4.0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: X2Go Packaging Team pkg-x2go-de...@lists.alioth.debian.org
Changed-By: Mike Gabriel sunwea...@debian.org
Description:
 x2goclient - X2Go Client application (Qt4)
 x2goclient-dbg - X2Go Client application (Qt4), debug symbols (client)
 x2goplugin - X2Go Client (Qt4) as browser plugin
 x2goplugin-dbg - X2Go Client application (Qt4), debug symbols (plugin)
 x2goplugin-provider - Provide X2Go Plugin via Apache webserver
Closes: 770962 770963
Changes:
 x2goclient (4.0.3.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix (cross-)user desktop sharing / helpdesk functionality (Closes:
   #770963).
 - Split up session profile dialog's Settings tab into a Input/Output
   tab and a media tab (Closes: #770962).
 - If a session broker is used with X2Go Client, allow configuration of
   audio settings through the broker.
 - Greatly improved man page.
 - Updated (upstream) translation files.
Checksums-Sha1:
 979026d4504a127eb0e6ecc08c18dc65542719e9 2346 x2goclient_4.0.3.1-1.dsc
 3f9e8932fa211fac725ef0b77d32b1a66f83bc3d 1539521 x2goclient_4.0.3.1.orig.tar.gz
 dfffa68fef69add529ff836af35ecadef5300c8f 310244 
x2goclient_4.0.3.1-1.debian.tar.xz
 933554d2f6d7fc05abdf4f54305f7e9b0a8e6b31 1189494 x2goclient_4.0.3.1-1_amd64.deb
 338cd5a7f9852ef07dcb5950fdfd67d02df4b43e 1205998 x2goplugin_4.0.3.1-1_amd64.deb
 31162c8367f8286eff3ca26250c10be3e6fed5e7 25840 
x2goplugin-provider_4.0.3.1-1_all.deb
 a6a026df3c085a242b23b2f44716cb99dcc5d36d 2883914 
x2goclient-dbg_4.0.3.1-1_amd64.deb
 90d1189a98541ad2c1bf98ee1833e554ae6304ed 3188160 
x2goplugin-dbg_4.0.3.1-1_amd64.deb
Checksums-Sha256:
 3421dea46e8fd007297b7a72e381f196e622e7dbeb6ece827d37772af58cb29f 2346 
x2goclient_4.0.3.1-1.dsc
 8a5a0d8112250ecc598a9811253081d16f87c17d0707e8f09671c7cb31942bad 1539521 
x2goclient_4.0.3.1.orig.tar.gz
 acba993860b95b38ea188d45a5a3024ede9e1f3c7f45ec030eb496a6d401ac02 310244 
x2goclient_4.0.3.1-1.debian.tar.xz
 99d50d4064b16ff70896574d50e8876ac9b3de90a73409c76836beefdf39af59 1189494 
x2goclient_4.0.3.1-1_amd64.deb
 9651d1d59c6ddcdb45e00cbf1fc4a017191a6d1e23c0100fd1e0b2e9eda7d168 1205998 
x2goplugin_4.0.3.1-1_amd64.deb
 ced3934cd7fd64b298541e66f04546fbc17d9c31905799c764088af3013ad600 25840 
x2goplugin-provider_4.0.3.1-1_all.deb
 

Processed: severity of 771125 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # sorry for the back and forth, but mutt also crashes with set weed=yes when 
 inspecting the headers, so should possibly be RC
 severity 771125 serious
Bug #771125 [mutt] mutt: CVE-2014-9116: write_one_header can call 
mutt_substrdup with begin  end, leading to crash
Severity set to 'serious' from 'important'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771125
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#771369: marked as done (latex-mk: unsatisfied build-dependendcy in jessie )

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 14:46:24 +0100
with message-id 20141129134624.ga13...@ramacher.at
and subject line Re: Bug#771369: latex-mk: unsatisfied build-dependendcy in 
jessie
has caused the Debian Bug report #771369,
regarding latex-mk: unsatisfied build-dependendcy in jessie 
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.)


-- 
771369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: latex-mk
Severity: serious
Version: 2.1-1.2
Tags: jessie
User: trei...@debian.org
Usertags: edos-uninstallable

Hi, latex-mk has a Build-Depends-Indep on tgif. However, tgif is not
in jessie.

-Ralf.
---End Message---
---BeginMessage---
Version: 2.1-1.3

On 2014-11-28 21:53:53, Ralf Treinen wrote:
 Source: latex-mk
 Severity: serious
 Version: 2.1-1.2
 Tags: jessie
 User: trei...@debian.org
 Usertags: edos-uninstallable
 
 Hi, latex-mk has a Build-Depends-Indep on tgif. However, tgif is not
 in jessie.

This is fixed in 2.1-1.3 which should migrate in a couple of days. It's
already unblocked and is waiting to become 5 days old.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature
---End Message---

Bug#767907: Bug#767903: fixed in pcre3 1:8.36-1

[Ivo De Decker]

Control: reopen 767907

Hi,

On Mon, Nov 24, 2014 at 11:49:23PM +, Mark Baker wrote:
  pcre3 (1:8.36-1) unstable; urgency=medium
  .
* New upstream release
* Upped shlibs dependency to 8.35 (Closes: #767903)

[the changelog mentioned #767903, but the change was actually for #767907]

This doesn't fix #767907, as it doesn't include the epoch. It generates a
dependency on 'libpcre3 (= 8.35)', which is satisfied by libpcre 1:8.30-5
(the version is wheezy), which doesn't have the new symbols.

Also, as I mentioned in #767903, the new upstream version has to be reverted,
to allow the changes to migrate to jessie.

* Upstream patch for heap buffer overflow, CVE-2014-8964 (Closes: #770478)

Cheers,

Ivo


-- 
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#767903: fixed in pcre3 1:8.36-1

[Debian Bug Tracking System]

Processing control commands:

 reopen 767907
Bug #767907 {Done: Mark Baker m...@mnb.org.uk} [libpcre3] too lax shlibs 
dependency? (newly added pcre_stack_guard needs = 1:8.35)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pcre3/1:8.36-1.

-- 
767907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767907
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#771132: (no subject)

[Séverin Lemaignan]

Thanks for your report. MORSE 1.2.1 is indeed expected to support Blender 2.72.

For sanity check, can you post the output of `morse --version`?


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

Processed: merge

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 forcemerge 771092 771406
Bug #771092 [libuuid1] insighttoolkit: Build failure on sparc
Bug #771406 [libuuid1] libuuid1 postinst uses groupmod, but doesn't depend on 
passwd
Severity set to 'grave' from 'serious'
Added indication that 771406 affects insighttoolkit
Marked as found in versions util-linux/2.25.1-1.
Added tag(s) sid, moreinfo, and jessie.
Bug #771092 [libuuid1] insighttoolkit: Build failure on sparc
Marked as found in versions util-linux/2.25.2-3.
Merged 771092 771406
 retitle 771092 libuuid1 uses groupmod in postinst, but doesn't depend on 
 passwd
Bug #771092 [libuuid1] insighttoolkit: Build failure on sparc
Bug #771406 [libuuid1] libuuid1 postinst uses groupmod, but doesn't depend on 
passwd
Changed Bug title to 'libuuid1 uses groupmod in postinst, but doesn't depend on 
passwd' from 'insighttoolkit: Build failure on sparc'
Changed Bug title to 'libuuid1 uses groupmod in postinst, but doesn't depend on 
passwd' from 'libuuid1 postinst uses groupmod, but doesn't depend on passwd'
 thanks
Stopping processing here.

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

[Matt Kraai]

Hi,

On Sat, Nov 29, 2014 at 10:24:45AM +, Paulo Assis wrote:
 This is fixed in version 0.2.5.
 source packages (signed) can be found here:
 https://drive.google.com/folderview?id=0B0_qxcVSvJFMOTcyOFJRNkFaWjAusp=sharing
 
 If someone can upload this, it would be appreciated.

I can upload it, but I'm afraid that it won't be allowed into testing.
According to

 https://release.debian.org/jessie/freeze_policy.html

new upstream releases shouldn't be included, only fixes for bugs of
important severity or higher, as well as translation and documentation
fixes.

Would you mind if I made an non-maintainer upload based on the
following patch?  Would you prefer I sponsor an upload by you that
just fixes this bug?

diff -Nru libwebcam-0.2.4/debian/changelog libwebcam-0.2.4/debian/changelog
--- libwebcam-0.2.4/debian/changelog2013-11-01 16:49:24.0 -0700
+++ libwebcam-0.2.4/debian/changelog2014-11-29 06:52:05.0 -0800
@@ -1,3 +1,10 @@
+libwebcam (0.2.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install dynctrl-logitech.h (Closes: #770982)
+
+ -- Matt Kraai kr...@debian.org  Sat, 29 Nov 2014 06:52:05 -0800
+
 libwebcam (0.2.4-1) unstable; urgency=low
 
   * Bump to version 0.2.4 (Closes: #713548)
diff -Nru libwebcam-0.2.4/debian/libwebcam0-dev.install 
libwebcam-0.2.4/debian/libwebcam0-dev.install
--- libwebcam-0.2.4/debian/libwebcam0-dev.install   2013-11-01 
16:49:24.0 -0700
+++ libwebcam-0.2.4/debian/libwebcam0-dev.install   2014-11-28 
15:32:56.0 -0800
@@ -1,3 +1,4 @@
+usr/include/dynctrl-logitech.h
 usr/include/webcam.h
 usr/lib/libwebcam.a
 usr/lib/libwebcam.so
diff -Nru libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h 
libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h
--- libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h   1969-12-31 
16:00:00.0 -0800
+++ libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h   2014-11-28 
15:29:48.0 -0800
@@ -0,0 +1,13 @@
+Index: libwebcam-0.2.4/libwebcam/CMakeLists.txt
+===
+--- libwebcam-0.2.4.orig/libwebcam/CMakeLists.txt  2013-10-31 
14:47:36.0 -0700
 libwebcam-0.2.4/libwebcam/CMakeLists.txt   2014-11-28 15:29:32.063070089 
-0800
+@@ -103,7 +103,7 @@
+ )
+ 
+ install (
+-  FILES   ../common/include/webcam.h
++  FILES   ../common/include/webcam.h ../common/include/dynctrl-logitech.h
+   DESTINATION ${CMAKE_INSTALL_PREFIX}/include
+ )
+ 
diff -Nru libwebcam-0.2.4/debian/patches/series 
libwebcam-0.2.4/debian/patches/series
--- libwebcam-0.2.4/debian/patches/series   2013-11-01 16:49:24.0 
-0700
+++ libwebcam-0.2.4/debian/patches/series   2014-11-28 15:29:13.0 
-0800
@@ -0,0 +1 @@
+install-dynctrl-logitech.h

-- 
Matt


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

Processed: tagging 762638

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # For Stretch
 tags 762638 + jessie-ignore wheezy-ignore
Bug #762638 [src:perl] missing source: Configure
Added tag(s) jessie-ignore and wheezy-ignore.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762638
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#770692: marked as done (python-pyopencl: Insecure temporary file creation for kernel cache)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 15:22:39 +
with message-id e1xujr5-00013y...@franck.debian.org
and subject line Bug#770692: fixed in pyopencl 2014.1-3
has caused the Debian Bug report #770692,
regarding python-pyopencl: Insecure temporary file creation for kernel cache
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.)


-- 
770692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-pyopencl
Severity: grave
Tags: upstream security
Justification: user security hole

Dear Maintainer,

PyOpenCL creates a cache of compiled kernels in a predictable location in the
temporary directory. Assuming a system-wide /tmp, an attacker can exploit this.
This allows for arbitrary code execution on OpenCL devices (which could be a
CPU); the cache also contains a Python pickle file, which may allow another
route to arbitrary code execution.

https://github.com/pyopencl/pyopencl/pull/68 contains an upstream patch to fix
the issue by storing the cache in the XDG per-user cache directory instead of
the temporary temporary.

I happen to be running Ubuntu Trusty on the machine where I first discovered
this, but it presumably affects any UNIX system with a shared system temporary
directory.



-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-39-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: pyopencl
Source-Version: 2014.1-3

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

Debian distribution maintenance software
pp.
Tomasz Rybak tomasz.ry...@post.pl (supplier of updated pyopencl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Nov 2014 11:43:47 +0100
Source: pyopencl
Binary: python-pyopencl python-pyopencl-dbg python3-pyopencl 
python3-pyopencl-dbg python-pyopencl-doc
Architecture: source amd64 all
Version: 2014.1-3
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Rybak tomasz.ry...@post.pl
Changed-By: Tomasz Rybak tomasz.ry...@post.pl
Description:
 python-pyopencl - Python module to access OpenCL parallel computation API
 python-pyopencl-dbg - Python module to access OpenCL API (debug extensions)
 python-pyopencl-doc - module to access OpenCL parallel computation API 
(documentation)
 python3-pyopencl - Python 3 module to access OpenCL parallel computation API
 python3-pyopencl-dbg - Python 3 module to access OpenCL API (debug extensions)
Closes: 770692
Changes:
 pyopencl (2014.1-3) unstable; urgency=medium
 .
   * Add dependency to appdirs and use it to create cache directories
 (Closes: #770692).
   * Update Standards-Version to 3.9.6; no changes necessary.
Checksums-Sha1:
 95c9e090b278c974caa4cfcaeb1ac78c48158b92 2530 pyopencl_2014.1-3.dsc
 bab08938600546cf800fd3a7e7f34b626207f74d 11360 pyopencl_2014.1-3.debian.tar.xz
 aa5265d39e371911fccc63e965b2c339bf3ce0f9 355648 
python-pyopencl_2014.1-3_amd64.deb
 b586b016c2dc25e6a61e5739d7011228bb17883c 6260732 
python-pyopencl-dbg_2014.1-3_amd64.deb
 f2c05dc3d26c910b4fc2d0b5ff1b11e6ee4f0da2 355028 
python3-pyopencl_2014.1-3_amd64.deb
 f0f004712d3a7b995928986ac08a59dd6aff4375 4872768 
python3-pyopencl-dbg_2014.1-3_amd64.deb
 7386a0d5612f89aa3404e55a2ea6375b8a03e742 118992 
python-pyopencl-doc_2014.1-3_all.deb
Checksums-Sha256:
 e023d7334f367c06b8c75bc0d31759baa605caa5bf9b40407aab20d5c6427736 2530 
pyopencl_2014.1-3.dsc
 21548d78f880bdcd0273fdfecb29bf75690beb649c118635213495e0af9a46cb 11360 
pyopencl_2014.1-3.debian.tar.xz
 e208bfe9af25e90f69fd4c0d01536d6f08111ce37e69219f7bf4c271a9f64dc2 355648 
python-pyopencl_2014.1-3_amd64.deb
 95ece5e0d39fd4878e9791d4e39ccc3ddfd5819487c5bfdc6bc19229840c29ef 6260732 
python-pyopencl-dbg_2014.1-3_amd64.deb
 

Processed: severity of 769325 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # looks like the mail did not make it to control@
 severity 769325 important
Bug #769325 [mediatomb] mediatomb: Mediatomb does not work with systemd
Severity set to 'important' from 'grave'
 thanks
Stopping processing here.

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

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 reopen 768695
Bug #768695 {Done: Tomasz Buchert tomasz.buch...@inria.fr} [src:statsmodels] 
statsmodels: FTBFS in jessie: ImportError: cannot import name DateRange
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions statsmodels/0.4.2-1.1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
768695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768695
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#771341: segfaults in sqlite3_value_type while using from Python

[Yaroslav Halchenko]

Hi László,

Thanks for getting back to me

On Sat, 29 Nov 2014, László Böszörményi (GCS) wrote:
  Package: libsqlite3-0
  Version: 3.7.13-1+deb7u1
  Severity: serious

  Originally detected I believe on sid installation, but forgot to capture the
  version, I will try to replicate/report later.  But very consistent with 
  wheezy
  (from which I am reporting now).
  May you give me some details how it happened in Sid?

ok -- I will try to replicate again under sid (trickier since I have no sid on
publicly bombarded servers)

  Triggered by the backport fail2ban 0.9.1-1~nd70+1 (available from
  http://neuro.debian.net/debian-devel/ wheezy/main amd64 Packages  apt repo) 
  it
  gets to
 [...]
  The problem is, I don't see the segfault in the mentioned gdb output.

well -- I didn't think it would be useful since backtrace has that call
on top and you would just trust me ;) but here you go:

# gdb --args /usr/bin/python-dbg /usr/bin/fail2ban-server -s 
/var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -f
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/python-dbg...done.
(gdb) c
The program is not being run.
(gdb) r
Starting program: /usr/bin/python-dbg /usr/bin/fail2ban-server -s 
/var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -f
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
2014-11-24 08:52:18,796 fail2ban.server [29794]: INFOStarting 
Fail2ban v0.9.1
2014-11-24 08:52:26,467 fail2ban.server [29794]: INFOStopping all 
jails
[New Thread 0x752a4700 (LWP 29812)]
[New Thread 0x74aa3700 (LWP 29813)]
[New Thread 0x7fffe700 (LWP 29814)]
[Thread 0x752a4700 (LWP 29812) exited]
[Thread 0x7fffe700 (LWP 29814) exited]
[Thread 0x74aa3700 (LWP 29813) exited]
[New Thread 0x74aa3700 (LWP 29895)]
[New Thread 0x7fffe700 (LWP 29896)]
[New Thread 0x752a4700 (LWP 29897)]
[Thread 0x74aa3700 (LWP 29895) exited]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x752a4700 (LWP 29897)]
sqlite3_value_type (pVal=0x0) at sqlite3.c:63805
63805   sqlite3.c: No such file or directory.
(gdb)


  unfortunately we haven't logged the sql queries so not sure on exact one, 
  but I
  think it was this one, which if executed from the shell seems to not cause 
  the
  segfault...

  n {1..100}; do sqlite3 -list fail2ban.sqlite3 'SELECT ip, timeofban, data 
  FROM bans WHERE 1 AND jail=sshd AND ip=111.74.239.35 ORDER BY ip, 
  timeofban' /dev/null  echo success; done
  Then how often do you get segfault? 

once in few days

 Do you have any additional
 information if it happens in a given daytime, when there are several
 bots try to get into your system or anything else?

I will keep monitoring/analyzing more -- so far haven't spotted 

  Please help me to troubleshoot this one if more information is necessary
  to point the issue
  I'm the SQLite3 maintainer and not the fail2ban one

FWIW -- I am the Fail2ban maintainer... but fail2ban is just a 'trigger'
here -- it is a purely Python implementation so either it is sqlite3 or python
bindings which are at fault here

. But please note
 the changelog the version you use[1]:
  - 0.9 series is quite a big leap in development, especially since 0.8.6
which made it to previous Debian stable wheezy.  Please consult 
 upstream
ChangeLog about changes

 Did you check it, reviewed your configuration? 

configuration of ... fail2ban?  it is somewhat minimalistic -- just a single
jail, that is why my original suspicion of possibly incorrect locking for the
same DB across threads didn't get much of my mental support ;) Although there
is still also few threads  involved :

  Id   Target Id Frame 
* 7Thread 0x752a4700 (LWP 29897) python-dbg sqlite3_value_type 
(pVal=0x0) at sqlite3.c:63805
  6Thread 0x7fffe700 (LWP 29896) python-dbg 0x00525338 in 
PyEval_EvalCodeEx (co=0xbe9ca0, globals=
{'logMultiprocessing': 1, '__path__': ['/usr/lib/python2.7/logging'], 
'LogRecord': type at remote 0xc29c70, 'logProcesses': 1, 'addLevelName': 
function at remote 0xc6e6f0, '_addHandlerRef': function at remote 0xc70798, 
'WARNING': 30, 'fatal': function at remote 0xc751b0, 'currentframe': 
function at remote 0xc6e648, 'INFO': 20, '_startTime': float at remote 
0x9d38f8, '__file__': '/usr/lib/python2.7/logging/__init__.pyc', 
'BufferingFormatter': type at remote 0xc2aca0, 'NOTSET': 0, '_levelNames': 
{0: 'NOTSET', 'NOTICE': 25, 10: 'DEBUG', 

Processed: tagging 770793

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 770793 + pending
Bug #770793 {Done: Samuel Thibault sthiba...@debian.org} [eztrace] eztrace 
uses -march=armv7-a on all arm systems.
Added tag(s) pending.
 thanks
Stopping processing here.

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

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 770782 + pending
Bug #770782 {Done: Samuel Thibault sthiba...@debian.org} [litl] litl uses 
-march=armv7-a on all arm systems.
Added tag(s) pending.
 thanks
Stopping processing here.

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

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 767557 + pending
Bug #767557 {Done: Samuel Thibault sthiba...@debian.org} 
[libsocl-1.1-1,libsocl-contrib-1.1-1] libsocl-1.1-1,libsocl-contrib-1.1-1: 
error when trying to install together
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
767557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767557
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#769716: Info received (iceweasel: downloads Cisco's OpenH264 video codec)

[Christoph Anton Mitterer]

Honi soit qui mal y pense - CVE-2014-8001.

So no we already have the case of an accidental vulnerability in the
binary blob... who knows what's really behind that ;)

(And yes, Cisco/Mozilla claim in the meantime that this doesn't affect
the version spread in binary form - but again... has anyone trustworthy
verified this?)


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#770477: mate-themes: dark themes make parts of libreoffice unreadable

[Alex Goebel]

severity 770477 important
thanks

Setting appropriate (non-rc!) severity as suggested above.


--
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#770477: mate-themes: dark themes make parts of libreoffice unreadable

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 severity 770477 important
Bug #770477 [mate-themes] mate-themes: dark themes make parts of libreoffice 
unreadable
Severity set to 'important' from 'grave'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
770477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770477
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#769716: iceweasel: downloads Cisco's OpenH264 video codec

[Christoph Anton Mitterer]

On Sat, 2014-11-29 at 08:26 +, Chuck Peters wrote: 
 That's good to know!  However I think many of us would be more 
 comfortable if the Debian systems built the source.
Not sure whether this is so easy due to the patent issues. It seems the
license where the patent costs are paid by Cisco for everyone only cover
the blob.
OTOH, Debian already distributes many binary packages which likely
include stuff covered by patents (e.g. all other h264 codecs) and I
guess we silently assume that users will have to pay any license fees on
their own. So we could do so the same here.


The main problem in this whole case (apart form blobs / proprietary
software slipping unnoted into Debian) seems Mozilla's politics, which
more and more says goodbye to the values of FLOSS.


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#768695: Bug #768695: statsmodels: FTBFS in jessie: ImportError: cannot import name DateRange

[Michael Banck]

On Sat, Nov 29, 2014 at 02:11:48PM +0100, Michael Banck wrote:
 Hi,
 
 On Wed, Nov 26, 2014 at 11:57:41PM +0100, Michael Banck wrote:
  On Wed, Nov 26, 2014 at 05:47:57PM -0500, Yaroslav Halchenko wrote:
   Upload it without delay, and let's hope none off those  doesn't veil
   the actual problem in the code :-) 
  
  OK, I will sponsor that upload as well tomorrow.
 
 Unfortunately, I did not get around to that yet, but was looking now.
 
 The problem is: As -1.1 has already been uploaded and accepted in the
 archive, what we need is -1.2 patch on top of that with a new changelog
 and everything.
 
 Tomasz, I will try to extract that from your two NMU diffs later today
 if you don't get around sending a new patch until then.

I've uploaded the attached debdiff now.


Michael
diff -Nru statsmodels-0.4.2/debian/changelog statsmodels-0.4.2/debian/changelog
--- statsmodels-0.4.2/debian/changelog  2014-11-23 18:56:37.0 +0100
+++ statsmodels-0.4.2/debian/changelog  2014-11-29 16:33:12.0 +0100
@@ -1,3 +1,15 @@
+statsmodels (0.4.2-1.2) testing; urgency=medium
+
+  * Non-maintainer upload, incorporating changes by Tomasz Buchert.
+  * debian/patches/scipy-rvs-interface.patch: Removed again and ...
+  * debian/patches/testsuite-fixes.patch: ... folded into this patch, just
+raising a nose.SkipTest() for the problematic test case.
+  * debian/patches/testsuite-fixes.patch: Amended for test_discrete.py, also
+skipping this test case via raising a nose.SkipTest(), as it leads to a
+FTBFS error on i386 (Closes: #768695).
+ 
+ -- Michael Banck mba...@debian.org  Sat, 29 Nov 2014 16:19:51 +0100
+
 statsmodels (0.4.2-1.1) testing; urgency=medium
 
   * Non-maintainer upload.
diff -Nru statsmodels-0.4.2/debian/patches/scipy-rvs-interface.patch 
statsmodels-0.4.2/debian/patches/scipy-rvs-interface.patch
--- statsmodels-0.4.2/debian/patches/scipy-rvs-interface.patch  2014-11-23 
18:56:37.0 +0100
+++ statsmodels-0.4.2/debian/patches/scipy-rvs-interface.patch  1970-01-01 
01:00:00.0 +0100
@@ -1,128 +0,0 @@
-Description: remove tests that use uncompatible scipy interface
- The tests use an rvs method which has an incompatible
- interface. We remove these failing tests altogether.
-
 statsmodels-0.4.2.orig/statsmodels/sandbox/tests/test_gam.py
-+++ statsmodels-0.4.2/statsmodels/sandbox/tests/test_gam.py
-@@ -187,121 +187,3 @@ class TestAdditiveModel(BaseAM, CheckAM)
- const = res_gam.alpha + sum([ss.params[1] for ss in m.smoothers])
- #print const, slopes
- res1.params = np.array([const] + slopes)
--
--
--class BaseGAM(BaseAM, CheckGAM):
--
--def init(self):
--nobs = self.nobs
--y_true, x, exog = self.y_true, self.x, self.exog
--if not hasattr(self, 'scale'):
--scale = 1
--else:
--scale = self.scale
--
--f = self.family
--
--self.mu_true = mu_true = f.link.inverse(y_true)
--
--np.random.seed(8765993)
--#y_obs = np.asarray([stats.poisson.rvs(p) for p in mu], float)
--y_obs = self.rvs(mu_true, scale=scale, size=nobs) #this should work
--m = GAM(y_obs, x, family=f)  #TODO: y_obs is twice __init__ and fit
--m.fit(y_obs, maxiter=100)
--res_gam = m.results
--self.res_gam = res_gam   #attached for debugging
--self.mod_gam = m   #attached for debugging
--
--res_glm = GLM(y_obs, exog, family=f).fit()
--
--#Note: there still are some naming inconsistencies
--self.res1 = res1 = Dummy() #for gam model
--#res2 = Dummy() #for benchmark
--self.res2 = res2 = res_glm  #reuse existing glm results, will add 
additional
--
--#eta in GLM terminology
--res2.y_pred = res_glm.model.predict(res_glm.params, exog, linear=True)
--res1.y_pred = res_gam.predict(x)
--res1.y_predshort = res_gam.predict(x[:10]) #, linear=True)
--
--#mu
--res2.mu_pred = res_glm.model.predict(res_glm.params, exog, 
linear=False)
--res1.mu_pred = res_gam.mu
--
--#parameters
--slopes = [i for ss in m.smoothers for i in ss.params[1:]]
--const = res_gam.alpha + sum([ss.params[1] for ss in m.smoothers])
--res1.params = np.array([const] + slopes)
--
--
--class TestGAMPoisson(BaseGAM):
--
--def __init__(self):
--super(self.__class__, self).__init__() #initialize DGP
--
--self.family =  family.Poisson()
--self.rvs = stats.poisson.rvs
--
--self.init()
--
--class TestGAMBinomial(BaseGAM):
--
--def __init__(self):
--super(self.__class__, self).__init__() #initialize DGP
--
--self.family =  family.Binomial()
--self.rvs = stats.bernoulli.rvs
--
--self.init()
--
--class _estGAMGaussianLogLink(BaseGAM):
--#test failure, but maybe precision issue, not far off
--# np.mean(np.abs(tt.res2.mu_pred - tt.mu_true))
--#0.80409736263199649
--# np.mean(np.abs(tt.res2.mu_pred - 

Bug#770689: marked as done (python-pycuda: Insecure temporary file creation for kernel cache)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 16:19:16 +
with message-id e1xukjs-0007r7...@franck.debian.org
and subject line Bug#770689: fixed in pycuda 2014.1-3
has caused the Debian Bug report #770689,
regarding python-pycuda: Insecure temporary file creation for kernel cache
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.)


-- 
770689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-pycuda
Severity: grave
Tags: upstream security
Justification: user security hole

Dear Maintainer,

See https://github.com/inducer/pycuda/issues/54 for the upstream report of this
bug, which allows a local attacker to run arbitrary GPU code in the address
space of the victim's application. The link also contains a patch.

I happen to be running Ubuntu Trusty on the machine where I first discovered
this, but it presumably affects any UNIX system with a shared system temporary
directory.



-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-39-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: pycuda
Source-Version: 2014.1-3

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

Debian distribution maintenance software
pp.
Tomasz Rybak tomasz.ry...@post.pl (supplier of updated pycuda package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Nov 2014 11:56:04 +0100
Source: pycuda
Binary: python-pycuda python-pycuda-dbg python3-pycuda python3-pycuda-dbg 
python-pycuda-doc
Architecture: source amd64 i386 all
Version: 2014.1-3
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Rybak tomasz.ry...@post.pl
Changed-By: Tomasz Rybak tomasz.ry...@post.pl
Description:
 python-pycuda - Python module to access Nvidia‘s CUDA parallel computation API
 python-pycuda-dbg - Python module to access Nvidia‘s CUDA API (debug 
extensions)
 python-pycuda-doc - module to access Nvidia‘s CUDA computation API 
(documentation)
 python3-pycuda - Python 3 module to access Nvidia‘s CUDA parallel computation 
API
 python3-pycuda-dbg - Python 3 module to access Nvidia‘s CUDA API (debug 
extensions)
Closes: 770689
Changes:
 pycuda (2014.1-3) unstable; urgency=medium
 .
   * Add dependency to appdirs and use it to create cache directories
 (Closes: #770689).
Checksums-Sha1:
 f76b5256426389c1dbbbd215013654d5dfbc9974 2520 pycuda_2014.1-3.dsc
 67dfa60c62fa4b47bcf84e76c83a291258f129f1 9068 pycuda_2014.1-3.debian.tar.xz
 8951aabf3818022d4ec45c4a1662a43b5ed755ee 304682 
python-pycuda_2014.1-3_amd64.deb
 7b4b7faa54a373f6aef08fa0da3d0e0b3dc17f77 4466446 
python-pycuda-dbg_2014.1-3_amd64.deb
 711c5ed5c3aebdb32c077e013c40061f29a82aa9 306638 
python3-pycuda_2014.1-3_amd64.deb
 756e80e36a914152b6630448a9980ea17dc1c88d 4227392 
python3-pycuda-dbg_2014.1-3_amd64.deb
 04e0d8145d3810f0f28bab86adb02e7bfd9a6f8b 290830 python-pycuda_2014.1-3_i386.deb
 240e05c5d89a394268015009a52f04efee5a6c3a 3833192 
python-pycuda-dbg_2014.1-3_i386.deb
 3813de52f4c7fb34a679a751f1ab68d4ce3a8e7a 295882 
python3-pycuda_2014.1-3_i386.deb
 457a946a7f3882eefcf04825785e16710a2fe61e 3865026 
python3-pycuda-dbg_2014.1-3_i386.deb
 1bdb201a404831b25ff18cc3d1a3d1d96c30a4ca 121238 
python-pycuda-doc_2014.1-3_all.deb
Checksums-Sha256:
 bb05b8cee84696f31f1cd7efb7d055743de2763ee91cca74e6ab6c4899408f9d 2520 
pycuda_2014.1-3.dsc
 f5312a5f591662b81723cd46cbc80c5af6dbb94ef6924a8506ae0780f27a4dcb 9068 
pycuda_2014.1-3.debian.tar.xz
 ca16eb9adb14ea9379c1705fd381c3e9388031223c58f40f54b8af67f5678330 304682 
python-pycuda_2014.1-3_amd64.deb
 cc2e5122fd49c90f0ccab0977b2e3dcd3805eec673bbad62048544b1de01ea4b 4466446 
python-pycuda-dbg_2014.1-3_amd64.deb
 705403069432fd30956221aac74170a1853de5b14f3b4b2c7fecb6d4674e3fb1 306638 

Bug#770104: does seivot work on stable?

[Lars Wirzenius]

On Sun, Nov 23, 2014 at 05:00:01PM +0100, Holger Levsen wrote:
 Hi Lars, Antoine,
 
 does seivot work on stable or should it be removed there as well? If it works 
 this bug should be tagged sid...

Seivot should work acceptably on stable. The bug's been closed by now,
so I don't think tagging's relevant anymore, but I'll keep the tagging
in mind for next time. Thanks!

-- 
http://gtdfh.branchable.com/ -- GTD for hackers
http://obnam.org/ -- HAVE YOU BACKED UP TODAY?


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

Bug#751767: libBLT changes SONAME without changing package name

[Ivo De Decker]

Hi,

On Sat, Nov 15, 2014 at 02:37:43PM +0400, Sergei Golovan wrote:
 On Sat, Nov 15, 2014 at 12:50 PM, Julien Cristau jcris...@debian.org wrote:
 
  You can't keep a dummy package on SONAME changes, since it doesn't
  actually provide the ABI older versions of its rdeps expect.
 
 I've added 'Breaks' header for all packages that depended on the older
 library. Specifically it is:
 
 Breaks: tclspice ( 26-1~), tkdesk ( 2.0-9.2~), skycat (
 3.1.2+starlink1~b-7~), python-tk ( 2.7.8-1~), python3-tk (
 3.4.1-3~)
 
 This means that there will not be possible to upgrade blt (which pulls
 in the new library) and leave the dependent packages unapgraded.

But the packages currently in testing can be installed with the old blt
version, which doesn't work.

I unblocked the version of blt currently in unstable, to allow it to migrate
to testing. All that packages that depend on blt need to be rebuilt. I'm
scheduling binnmu's for them. Once that's done, you should do a new upload,
removing the blt binary package, as it would be wrong to keep it around (I'll
let you know when you can do the upload). Therefore, I'm not closing this bug
now.

Cheers,

Ivo


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

Bug#770695: Dovecot-core unable to finish its installation

[Tony Mantler]

I'm trying to install dovecot-core (1:2.2.13-7) and I do have valid 
certificates in /etc/dovecot/conf.d/10-ssl.conf and the postinst script is 
still hanging. I don't believe this bug is fixed.

--
Tony 'Nicoya' Mantler - Master of Code-fu
-- nic...@ubb.ca -- http://www.ubb.ca/ --


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

Bug#771449: Killer is killing logged in users

[Alexander Alemayhu]

Package: killer
Version: 0.90-11
Severity: serious

Dear Maintainer,

While logged in on a tjener I was logged out multiple times and was told by 
Petter that killer
killed me. He also mentioned the bug might be related to a change in ps.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)


signature.asc
Description: Digital signature

Bug#771163: marked as done (libreoffice: CVE-2014-9093)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 17:42:58 +
with message-id e1xum2s-0002hw...@franck.debian.org
and subject line Bug#771163: fixed in libreoffice 1:4.3.3-2
has caused the Debian Bug report #771163,
regarding libreoffice: CVE-2014-9093
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.)


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

Hi,
please see https://bugs.freedesktop.org/show_bug.cgi?id=86449 for the
bug report with a reproducer (which also crashes the version in wheezy).

4.3 fix by Caolan:
http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-4-3id=b4840d3632e4404bee4bd192a7db916cbad3a401

Cheers,
Moritz
---End Message---
---BeginMessage---
Source: libreoffice
Source-Version: 1:4.3.3-2

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

Debian distribution maintenance software
pp.
Rene Engelhard r...@debian.org (supplier of updated libreoffice package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 27 Nov 2014 12:00:02 +0100
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-writer libreoffice-calc 
libreoffice-impress libreoffice-draw libreoffice-math libreoffice-base-core 
libreoffice-base libreoffice-style-crystal libreoffice-style-oxygen 
libreoffice-style-tango libreoffice-style-hicontrast libreoffice-style-sifr 
libreoffice-style-galaxy libreoffice-gtk libreoffice-gtk3 libreoffice-gnome 
python-uno python3-uno libreoffice-officebean 
openoffice.org-dtd-officedocument1.0 libreoffice-script-provider-python 
libreoffice-script-provider-bsh libreoffice-script-provider-js 
libreoffice-pdfimport libreoffice-avmedia-backend-gstreamer 
libreoffice-avmedia-backend-vlc libreoffice-sdbc-firebird 
libreoffice-sdbc-hsqldb libreoffice-base-drivers libreoffice-l10n-af 
libreoffice-l10n-ar libreoffice-l10n-as libreoffice-l10n-ast 
libreoffice-l10n-be libreoffice-l10n-bg libreoffice-l10n-bn libreoffice-l10n-br 
libreoffice-l10n-bs
 libreoffice-l10n-ca libreoffice-l10n-cs libreoffice-l10n-cy 
libreoffice-l10n-da libreoffice-l10n-de libreoffice-l10n-dz libreoffice-l10n-el 
libreoffice-l10n-en-gb libreoffice-l10n-en-za libreoffice-l10n-eo 
libreoffice-l10n-es libreoffice-l10n-et libreoffice-l10n-eu libreoffice-l10n-fa 
libreoffice-l10n-fi libreoffice-l10n-fr libreoffice-l10n-ga libreoffice-l10n-gd 
libreoffice-l10n-gl libreoffice-l10n-gu libreoffice-l10n-he libreoffice-l10n-hi 
libreoffice-l10n-hr libreoffice-l10n-hu libreoffice-l10n-id libreoffice-l10n-is 
libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-ka libreoffice-l10n-kk 
libreoffice-l10n-km libreoffice-l10n-ko libreoffice-l10n-kmr 
libreoffice-l10n-lt libreoffice-l10n-lv libreoffice-l10n-mk libreoffice-l10n-mn 
libreoffice-l10n-ml libreoffice-l10n-mr libreoffice-l10n-nb libreoffice-l10n-ne 
libreoffice-l10n-nl libreoffice-l10n-nn libreoffice-l10n-nr 
libreoffice-l10n-nso libreoffice-l10n-oc libreoffice-l10n-om libreoffice-l10n-or
 libreoffice-l10n-pa-in libreoffice-l10n-pl libreoffice-l10n-pt 
libreoffice-l10n-pt-br libreoffice-l10n-ro libreoffice-l10n-ru 
libreoffice-l10n-rw libreoffice-l10n-si libreoffice-l10n-sk libreoffice-l10n-sl 
libreoffice-l10n-sr libreoffice-l10n-ss libreoffice-l10n-st libreoffice-l10n-sv 
libreoffice-l10n-ta libreoffice-l10n-te libreoffice-l10n-tg libreoffice-l10n-th 
libreoffice-l10n-tn libreoffice-l10n-tr libreoffice-l10n-ts libreoffice-l10n-ug 
libreoffice-l10n-uk libreoffice-l10n-uz libreoffice-l10n-ve libreoffice-l10n-vi 
libreoffice-l10n-xh libreoffice-l10n-zh-cn libreoffice-l10n-zh-tw 
libreoffice-l10n-zu libreoffice-presenter-console 
libreoffice-presentation-minimizer libreoffice-emailmerge libreoffice-l10n-ku 
libreoffice-help-en-us libreoffice-help-ca libreoffice-help-cs 
libreoffice-help-da libreoffice-help-de libreoffice-help-dz 

Bug#734505: Can we close twitter-recess bug #734505?

[W. Martin Borgert]

Julian, I tried with your example and it seems to work now.
Maybe the node-less is newer now than when you tried?

László, could you check and close the bug accordingly?

Thanks and cheers

PS: Too bad, this bug stopped the package from entering Jessie :~(


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

Bug#751767: libBLT changes SONAME without changing package name

[Sergei Golovan]

Hi Ivo,

On Sat, Nov 29, 2014 at 8:26 PM, Ivo De Decker iv...@debian.org wrote:

 But the packages currently in testing can be installed with the old blt
 version, which doesn't work.

Well, the concern is about the packages which are currently in wheezy
and depend on blt (= 2.4). They can be installed with blt currently
in jessie, which will break them. The packages which are currently in
testing can be installed only with BLT currently in testing or
unstable, and they work fine with both of these blt versions.


 I unblocked the version of blt currently in unstable, to allow it to migrate
 to testing. All that packages that depend on blt need to be rebuilt. I'm

It's not necessary, because they work fine as they are now. And they
can't be installed together with blt from wheezy (depend on
blt=2.5.3). So, after the new blt will hit testing partial upgrades
will not be possible either way.

 scheduling binnmu's for them. Once that's done, you should do a new upload,
 removing the blt binary package, as it would be wrong to keep it around (I'll
 let you know when you can do the upload). Therefore, I'm not closing this bug
 now.

I'm not going to remove the blt package. I want it to be installable
as easy as apt-get install blt. And I don't see how this is bad now
(except for not very pretty 'breaks' in its debian/control)..

Cheers!
-- 
Sergei Golovan


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

Bug#768764: marked as done (systempreferences.app: FTBFS in jessie: dh_install: libpreferencepanes1 missing files (usr/lib/GNUstep/Frameworks/*.framework/Resources), aborting)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 18:04:38 +
with message-id e1xumnq-0004s0...@franck.debian.org
and subject line Bug#768764: fixed in systempreferences.app 1.2.0-2
has caused the Debian Bug report #768764,
regarding systempreferences.app: FTBFS in jessie: dh_install: 
libpreferencepanes1 missing files 
(usr/lib/GNUstep/Frameworks/*.framework/Resources), aborting
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.)


-- 
768764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: systempreferences.app
Version: 1.2.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
 make[1]: Entering directory '/«PKGBUILDDIR»'
 This is gnustep-make 2.6.6. Type 'make print-gnustep-make-help' for help.
 Making all in PreferencePanes ...
 Making build-headers for framework PreferencePanes...
 Making all for framework PreferencePanes...
 make[4]: Nothing to be done for 'internal-framework-compile'.
  Copying resources into the framework wrapper...
 Warning: Resources/English.lproj not found - ignoring
 Making all in Modules ...
 Making all in TimeZone ...
 Making all for bundle TimeZone...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in Volumes ...
 Making all for bundle Volumes...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in FileSystem ...
 Making all for bundle FileSystem...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in ModifierKeys ...
 Making all for bundle ModifierKeys...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in Fonts ...
 Making all for bundle FontModule...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in Defaults ...
 Making all for bundle Defaults...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in Themes ...
 Making all for bundle Themes...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in Internet ...
 Making all for bundle InternetModule...
 make[6]: Nothing to be done for 'internal-bundle-compile'.
  Copying resources into the bundle wrapper...
 Making all in SystemPreferences ...
 Making all for app SystemPreferences...
 make[5]: Nothing to be done for 'internal-app-compile'.
  Copying resources into the app wrapper...
 Making install in PreferencePanes ...
 Making install for framework PreferencePanes...
  Creating /«PKGBUILDDIR»/debian/tmp//usr/lib/GNUstep/Frameworks...
  Creating /«PKGBUILDDIR»/debian/tmp//usr/include/GNUstep...
  Installing framework PreferencePanes...
  Installing headers...
 Making install in Modules ...
 Making install in TimeZone ...
 Making install for bundle TimeZone...
  Creating /«PKGBUILDDIR»/debian/tmp//usr/lib/GNUstep/Bundles...
  Installing bundle directory...
 Making install in Volumes ...
 Making install for bundle Volumes...
  Installing bundle directory...
 Making install in FileSystem ...
 Making install for bundle FileSystem...
  Installing bundle directory...
 Making install in ModifierKeys ...
 Making install for bundle ModifierKeys...
  Installing bundle directory...
 Making install in Fonts ...
 Making install for bundle FontModule...
  Installing bundle directory...
 Making install in Defaults ...
 Making install for bundle Defaults...
  Installing bundle directory...
 Making install in Themes ...
 Making install for bundle Themes...
  Installing bundle directory...
 Making install in Internet ...
 Making install for bundle InternetModule...
  Installing bundle directory...
 Making install in SystemPreferences ...
 Making install for app SystemPreferences...
  Creating /«PKGBUILDDIR»/debian/tmp//usr/lib/GNUstep/Applications...
  Installing bundle directory...
  Creating /«PKGBUILDDIR»/debian/tmp//usr/bin/
 make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_install
 dh_install: libpreferencepanes1 missing files 
 (usr/lib/GNUstep/Frameworks/*.framework/Resources), aborting
 debian/rules:13: recipe for target 'binary' failed
 make: 

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

[Shannon Dealy]

Package: s3ql
Version: 2.11.1+dfsg-1
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

While running rsync to backup data to an s3ql file system mounted from Amazon's
S3 services, the internet connection failed, resulting in the following 
error(s) from rsync:

   rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken 
pipe (32)
   rsync: write failed on file name removed: Software caused connection 
abort (103)
   rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9]
   rsync: connection unexpectedly closed (17298 bytes received so far) [sender]
   rsync error: error in rsync protocol data stream (code 12) at io.c(605) 
[sender=3.0.9]

I attempted to unmount the file system with the following result (twice):

   # umount.s3ql /media/server-external
   File system appears to have crashed.

I then forced it to unmount as follows:

   # fusermount -u -z /media/server-external

Then attempted to fsck the file system (twice - both gave the same result):

   fsck.s3ql s3://bucket name/file system prefix
   Enter file system encryption passphrase: 
   Starting fsck of s3://bucket name/file system prefix
   Using cached metadata.
   Remote metadata is outdated.
   Checking DB integrity...
   Creating temporary extra indices...
   Checking lost+found...
   Checking cached objects...
   Committing block 14 of inode 442809 to backend
   Committing block 16 of inode 442809 to backend
   Committing block 17 of inode 442809 to backend
   Committing block 15 of inode 442809 to backend
   Committing block 19 of inode 442809 to backend
   Committing block 18 of inode 442809 to backend
   Checking names (refcounts)...
   Checking contents (names)...
   Checking contents (inodes)...
   Checking contents (parent inodes)...
   Checking objects (reference counts)...
   Checking objects (backend)...
   ..processed 10 objects so far..
   Dropping temporary indices...
   Uncaught top-level exception:
   Traceback (most recent call last):
 File /usr/bin/fsck.s3ql, line 9, in module
   load_entry_point('s3ql==2.11.1', 'console_scripts', 'fsck.s3ql')()
 File /usr/lib/s3ql/s3ql/fsck.py, line 1189, in main
   fsck.check()
 File /usr/lib/s3ql/s3ql/fsck.py, line 85, in check
   self.check_objects_id()
 File /usr/lib/s3ql/s3ql/fsck.py, line 848, in check_objects_id
   self.conn.execute('INSERT INTO obj_ids VALUES(?)', (obj_id,))
 File /usr/lib/s3ql/s3ql/database.py, line 98, in execute
   self.conn.cursor().execute(*a, **kw)
 File src/cursor.c, line 231, in resetcursor
   apsw.ConstraintError: ConstraintError: PRIMARY KEY must be unique

Next I copied the entire Amazon bucket to a new bucket and attempted an fsck
on the copy, minus the locally cached file system data:

   # fsck.s3ql s3://new bucket name/file system prefix
   Enter file system encryption passphrase: 
   Starting fsck of s3://new bucket name/file system prefix
   Uncaught top-level exception:
   Traceback (most recent call last):
 File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 381, in 
_convert_legacy_metadata
   meta_new['data'] = meta['data']
   KeyError: 'data'

   During handling of the above exception, another exception occurred:

   Traceback (most recent call last):
 File /usr/bin/fsck.s3ql, line 9, in module
   load_entry_point('s3ql==2.11.1', 'console_scripts', 'fsck.s3ql')()
 File /usr/lib/s3ql/s3ql/fsck.py, line , in main
   param = backend.lookup('s3ql_metadata')
 File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 72, in lookup
   meta_raw = self._convert_legacy_metadata(meta_raw)
 File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 383, in 
_convert_legacy_metadata
   raise CorruptedObjectError('meta key data is missing')
   s3ql.backends.common.CorruptedObjectError: meta key data is missing


NOTE: I'm not sure about the exact implication of _convert_legacy_metadata
  in the traceback above, but this was NOT a legacy file system, it was 
  just created using s3ql 2.11.1 as it is cheaper to rebuild it than
  to pull 700 GB in the old copy down from Amazon to do the verify
  specified as part of the upgrade procedure from older versions.

At the time of this failure I had uploaded between 200 and 300 GB of
deduplicated/compressed data to the new file system.

As things currently stand, unless I have overlooked or misunderstood something
(which I consider entirely possible), this network connection failure has
resulted in 100% data loss unless fsck can be fixed in a manner which will
allow it to complete correctly and recover the file system data.  As I
maintain other backups, no actual data has been lost (so far), but this
makes s3ql unsafe to use and further attempts to backup my data to S3
pointless.

Regards,

Shannon Dealy

-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')

Bug#771417: bogus dpkg error, now endless loop on dbus configuration

[Ira Rice]

Could this just be related to bug 771290
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771290? Because holding
off on installing gnome-bluetooth, which would have caused me to trigger
that bug, made it so that I didn't encounter this bug, and dpkg appears to
work just fine.

To me, it just sounds like that update broke dbus, which in turn broke
dpkg, and because of that, dpkg is not what's causing the problem here.

Just my two cents, in any case.

Bug#771449: marked as done (Killer is killing logged in users)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 18:48:49 +
with message-id e1xun4b-0001xv...@franck.debian.org
and subject line Bug#771449: fixed in killer 0.90-12
has caused the Debian Bug report #771449,
regarding Killer is killing logged in users
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.)


-- 
771449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: killer
Version: 0.90-11
Severity: serious

Dear Maintainer,

While logged in on a tjener I was logged out multiple times and was told by 
Petter that killer
killed me. He also mentioned the bug might be related to a change in ps.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: killer
Source-Version: 0.90-12

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen p...@debian.org (supplier of updated killer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 29 Nov 2014 19:26:57 +0100
Source: killer
Binary: killer
Architecture: source all
Version: 0.90-12
Distribution: unstable
Urgency: low
Maintainer: Debian Edu Developers debian-...@lists.debian.org
Changed-By: Petter Reinholdtsen p...@debian.org
Description: 
 killer - Background job killer
Closes: 771449
Changes: 
 killer (0.90-12) unstable; urgency=low
 .
   [ Alexander Alemayhu ]
   * Handle ps format changes (Closes: #771449).
Checksums-Sha1: 
 719260996c1de55a6f9e5abab363923e5ab177c2 1311 killer_0.90-12.dsc
 dd5f8234d489fbdceb97fbd75b927a5d5a539006 8925 killer_0.90-12.debian.tar.gz
 568fca33178080d30145e7213830f6c7a938b989 27836 killer_0.90-12_all.deb
Checksums-Sha256: 
 f7153d6b34edec48be3eff9850c84ea5f56b478b853e21da05f301d75c647786 1311 
killer_0.90-12.dsc
 c77a2d39fa0e07967b009eb7fb30cf02dee924dd2ac8f524bff4a170466fd014 8925 
killer_0.90-12.debian.tar.gz
 6f11080935a1ecbf1dbd817ea3f7a1715883145852d37d09b103b97e2ff4025b 27836 
killer_0.90-12_all.deb
Files: 
 fa19b37c58da28dfa3c1d63e073eb1f3 1311 misc optional killer_0.90-12.dsc
 00aa78c050860b8de6d2f2b15c01e1e9 8925 misc optional 
killer_0.90-12.debian.tar.gz
 3591f19d4e70841743e61d876575663b 27836 misc optional killer_0.90-12_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQFUehBL20zMSyow1ykRAkWZAKCIP9Ha/qoPsn9aevI0WmfG5Fo4xACdFpwz
31K1VodK1pNJ50BBBAFmdG8=
=ycAm
-END PGP SIGNATUREEnd Message---

Bug#771454: libflite1: minimal version in symbols file too old

[Andreas Cadhalpun]

Package: libflite1
Version: 1.4-release-11
Severity: serious

Dear Maintainer,

the symbols file of libflite1 sets the minimal version for all symbols 
to 1.4-release. But apparently this is not correct:

If libflite1 1.4-release-8 is installed, ffmpeg does not work:

$ ffmpeg
ffmpeg: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libflite_cmu_us_slt.so.1: undefined symbol: 
usenglish_init


Installing libflite1 1.4-release-9 (or newer) fixes this.
Probably the fix for #746383 included in 1.4-release-9 is responsible 
for this.


I think the best way forward is to increase the minimal versions of all 
symbols to 1.4-release-9~ and rebuilt all reverse dependencies against a 
fixed version.


Best regards,
Andreas

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.17.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set 
to C)

Shell: /bin/sh linked to /bin/dash

Versions of packages libflite1 depends on:
ii  libasound2 1.0.28-1
ii  libc6  2.19-13
ii  multiarch-support  2.19-13

libflite1 recommends no packages.

Versions of packages libflite1 suggests:
pn  alsa-base  none

-- no debconf information


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

Processed: closing 769975

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # Actually a problem in insighttoolkit; builds fine now
 close 769975
Bug #769975 [src:plastimatch] pastimatch: FTBFS on several arches
Marked Bug as done
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
769975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769975
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#770695: Dovecot-core unable to finish its installation

[Jaldhar H. Vyas]

On Sat, 29 Nov 2014, Tony Mantler wrote:

I'm trying to install dovecot-core (1:2.2.13-7) and I do have valid 
certificates in /etc/dovecot/conf.d/10-ssl.conf and the postinst script 
is still hanging. I don't believe this bug is fixed.




No this is a different bug. :(  See #771334

--
Jaldhar H. Vyas jald...@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#770695: Dovecot-core unable to finish its installation

[Tony Mantler]

 On Nov 29, 2014, at 11:12 AM, Jaldhar H. Vyas jald...@debian.org wrote:
 
 On Sat, 29 Nov 2014, Tony Mantler wrote:
 
 I'm trying to install dovecot-core (1:2.2.13-7) and I do have valid 
 certificates in /etc/dovecot/conf.d/10-ssl.conf and the postinst script is 
 still hanging. I don't believe this bug is fixed.
 
 
 No this is a different bug. :(  See #771334

I don't think that's the problem I'm seeing. I have valid keys in the default 
locations, in /etc/dovecot/dovecot.pem and /etc/dovecot/private/dovecot.pem

I commented out the lines in /etc/dovecot/conf.d/10-ssl.conf and ran the 
package upgrade again, then re-enabled the lines in the conf file and my 
installation is now working with encryption enabled. The problem was definitely 
that the postinst script was hanging during upgrade.

--
Tony 'Nicoya' Mantler - Master of Code-fu
-- nic...@ubb.ca -- http://www.ubb.ca/ --


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

Bug#770695: Dovecot-core unable to finish its installation

[Jaldhar H. Vyas]

On Sat, 29 Nov 2014, Tony Mantler wrote:

I don't think that's the problem I'm seeing. I have valid keys in the 
default locations, in /etc/dovecot/dovecot.pem and 
/etc/dovecot/private/dovecot.pem


I commented out the lines in /etc/dovecot/conf.d/10-ssl.conf and ran the 
package upgrade again, then re-enabled the lines in the conf file and my 
installation is now working with encryption enabled. The problem was 
definitely that the postinst script was hanging during upgrade.


At the time the postinst was hanging, were ssl_key and ssl_cert commented 
out or not?  As I understand the current situation -7 is installing a new 
version of 10-ssl.conf with those lines commented out when they shouldn't 
be.  If they are not commented out and the postinst is still hanging then 
yes there is a (new?) problem.


--
Jaldhar H. Vyas jald...@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#769947: mate-terminal: Segfaults after update

[Alex Corcoles]

@Alex: do you think you could build mate-terminal from source with the
referenced patch included and confirm that the patch fixes your issues?


I tried, but I believe the necessary -dev packages are not yet in Debian:

$ ./autogen.sh
...
Requested 'mate-desktop-2.0 = 1.9.0' but version of mate-desktop-2.0 is 
1.8.1

...

if what's necessary to build is not too complex and it does not 
interfere with my system, I'm happy to try- but I'm not sure of the 
steps needed.


I also have a good workaround, so this issue is no longer so important 
to me.


--
   ___mail: alex at corcoles dot net
 {~._.~}   ICQ: 66791436
  ( Y )MSN: koalillo at fastmail dot fm
 ()~*~()Y!: koalillo
 (_)-(_)  http://alex.corcoles.net/


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

Bug#770695: Dovecot-core unable to finish its installation

[Tony Mantler]

 On Nov 29, 2014, at 11:58 AM, Jaldhar H. Vyas jald...@debian.org wrote:
 
 On Sat, 29 Nov 2014, Tony Mantler wrote:
 
 I don't think that's the problem I'm seeing. I have valid keys in the 
 default locations, in /etc/dovecot/dovecot.pem and 
 /etc/dovecot/private/dovecot.pem
 
 I commented out the lines in /etc/dovecot/conf.d/10-ssl.conf and ran the 
 package upgrade again, then re-enabled the lines in the conf file and my 
 installation is now working with encryption enabled. The problem was 
 definitely that the postinst script was hanging during upgrade.
 
 At the time the postinst was hanging, were ssl_key and ssl_cert commented out 
 or not?  As I understand the current situation -7 is installing a new version 
 of 10-ssl.conf with those lines commented out when they shouldn't be.  If 
 they are not commented out and the postinst is still hanging then yes there 
 is a (new?) problem.

When postinst was hanging, those lines were not commented out.


--
Tony 'Nicoya' Mantler - Master of Code-fu
-- nic...@ubb.ca -- http://www.ubb.ca/ --


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

Bug#770695: Dovecot-core unable to finish its installation

[Jaldhar H. Vyas]

On Sat, 29 Nov 2014, Tony Mantler wrote:


When postinst was hanging, those lines were not commented out.



And just to confirm, this was when upgrading from -6 to -7?

--
Jaldhar H. Vyas jald...@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#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

[Nikolaus Rath]

On 11/29/2014 09:49 AM, Shannon Dealy wrote:
 Package: s3ql
 Version: 2.11.1+dfsg-1
 Severity: critical
 Justification: causes serious data loss
 
 Dear Maintainer,
 
 While running rsync to backup data to an s3ql file system mounted from 
 Amazon's
 S3 services, the internet connection failed, resulting in the following 
 error(s) from rsync:
 
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: 
 Broken pipe (32)
rsync: write failed on file name removed: Software caused connection 
 abort (103)
rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9]
rsync: connection unexpectedly closed (17298 bytes received so far) 
 [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) 
 [sender=3.0.9]
 
 I attempted to unmount the file system with the following result (twice):
 
# umount.s3ql /media/server-external
File system appears to have crashed.

Thanks for the report! Could you please include the contents of your
~/.s3ql/mount.log file?


 As things currently stand, unless I have overlooked or misunderstood something
 (which I consider entirely possible), this network connection failure has
 resulted in 100% data loss unless fsck can be fixed in a manner which will
 allow it to complete correctly and recover the file system data.  

Chances are good that this can be done, so don't give up hope yet.


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


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

Bug#771461: /var/state/samhain/

[Jakub Wilk]

Package: samhain
Version: 3.1.0-6+b1
Severity: serious
Justification: Policy §9.1.1 (File System Structure)

$ find /var/state
/var/state
/var/state/samhain
/var/state/samhain/samhain_file

But there is no /var/state in FHS. All non-volatile package state should 
be in /var/lib/package instead.



-- System Information:
Debian Release: jessie/sid
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages samhain depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  libauparse01:2.4-1
ii  libc6  2.19-13
ii  libgcrypt201.6.2-4
ii  libgnutls-deb0-28  3.3.8-4
ii  libprelude21.0.0-11.4
ii  zlib1g 1:1.2.8.dfsg-2

--
Jakub Wilk


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

Bug#770695: Dovecot-core unable to finish its installation

[Tony Mantler]

 On Nov 29, 2014, at 12:16 PM, Jaldhar H. Vyas jald...@debian.org wrote:
 
 On Sat, 29 Nov 2014, Tony Mantler wrote:
 
 When postinst was hanging, those lines were not commented out.
 
 
 And just to confirm, this was when upgrading from -6 to -7?

No, it was probably a fair bit earlier than -6, I hadn't upgraded in a while.

--
Tony 'Nicoya' Mantler - Master of Code-fu
-- nic...@ubb.ca -- http://www.ubb.ca/ --


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

Bug#767584: segfaults when segfaults when a dot is used in the config as part of the hostname

[Simon Kainz]

Hello,

as I am currently going through NM, and one of my tasks was to try to
fix a bug and prepare a NMU, my AM suggested that i might as well
upload the result. Please see the attached debdiff, fixing #767584.

Regards,

Simon
diff -Nru apt-dater-1.0.1/debian/changelog apt-dater-1.0.1/debian/changelog
--- apt-dater-1.0.1/debian/changelog	2014-10-31 19:56:43.0 +
+++ apt-dater-1.0.1/debian/changelog	2014-11-20 12:59:54.0 +
@@ -1,3 +1,11 @@
+apt-dater (1.0.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fixes segfaults when a dot is used in the config file
+as part of the host identifier (Closes: #767584) 
+
+ -- Simon Kainz si...@familiekainz.at  Thu, 20 Nov 2014 13:47:38 +0100
+
 apt-dater (1.0.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru apt-dater-1.0.1/debian/patches/00_fix_segfaults_when_dot_in_conffile.patch apt-dater-1.0.1/debian/patches/00_fix_segfaults_when_dot_in_conffile.patch
--- apt-dater-1.0.1/debian/patches/00_fix_segfaults_when_dot_in_conffile.patch	1970-01-01 00:00:00.0 +
+++ apt-dater-1.0.1/debian/patches/00_fix_segfaults_when_dot_in_conffile.patch	2014-11-20 13:03:56.0 +
@@ -0,0 +1,83 @@
+Description: Fix segfaults if dots are used in the config file 
+ 
+This patch fixes the segault issue by using g_printerr() in favor 
+of g_error(), because the latter is used to report fatal errors (e.g
+assertion failures), followed by a core dump. 
+
+Author: Simon Kainz si...@familiekainz.at
+Bug-Debian: https://bugs.debian.org/767584
+
+---
+
+--- apt-dater-1.0.1.orig/src/apt-dater.c
 apt-dater-1.0.1/src/apt-dater.c
+@@ -123,7 +123,7 @@ int main(int argc, char **argv, char **e
+  cfg = initialConfig();
+ 
+  if(!(loadConfig(cfgfilename, cfg))) {
+-  g_error(_(Error on loading config file %s\n), cfgfilename);
++  g_printerr(_(Error on loading config file %s\n), cfgfilename);
+   exit(EXIT_FAILURE);
+  }
+ 
+--- apt-dater-1.0.1.orig/src/keyfiles.c
 apt-dater-1.0.1/src/keyfiles.c
+@@ -151,9 +151,9 @@ gboolean loadConfig(char *filename, CfgF
+ if(config_read_file(hcfg, filename) == CONFIG_FALSE) {
+ #ifdef HAVE_LIBCONFIG_ERROR_MACROS
+   const char *efn = config_error_file(hcfg);
+-  g_error (Error reading config file [%s:%d]: %s, (efn ? efn : filename), config_error_line(hcfg), config_error_text(hcfg));
++g_printerr (Error reading config file [%s:%d]: %s\n, (efn ? efn : filename), config_error_line(hcfg), config_error_text(hcfg));
+ #else
+-  g_error (Error reading config file %s!, filename);
++  g_printerr (Error reading config file %s!\n, filename);
+ #endif
+ 	config_destroy(hcfg);
+ 	return (FALSE);
+@@ -197,14 +197,14 @@ gboolean loadConfig(char *filename, CfgF
+ 
+ h = NULL;
+ if(config_setting_lookup_string(s_ssh, Cmd, (const char **) h) == CONFIG_FALSE) {
+-	g_error (%s: Config option SSH.Cmd not set!, filename);
++	g_printerr (%s: Config option SSH.Cmd not set!, filename);
+ 	return (FALSE);
+ }
+ lcfg-ssh_cmd = g_strdup(h);
+ 
+ h = NULL;
+ if(config_setting_lookup_string(s_ssh, SFTPCmd, (const char **) h) == CONFIG_FALSE) {
+-	g_error (%s: Config option SSH.SFTPCmd not set!, filename);
++	g_printerr (%s: Config option SSH.SFTPCmd not set!, filename);
+ 	return (FALSE);
+ }
+ lcfg-sftp_cmd = g_strdup(h);
+@@ -228,7 +228,7 @@ gboolean loadConfig(char *filename, CfgF
+ 	}
+ 	}
+ 	else {
+-	g_error (%s: setting %s must be a single string or an array of strings, filename, config_setting_name(s_addkeys));
++	g_printerr (%s: setting %s must be a single string or an array of strings, filename, config_setting_name(s_addkeys));
+ 	}
+ }
+ 
+@@ -295,9 +295,9 @@ GList *loadHosts (const char *filename)
+ if(config_read_file(hcfg, filename) == CONFIG_FALSE) {
+ #ifdef HAVE_LIBCONFIG_ERROR_MACROS
+   const char *efn = config_error_file(hcfg);
+-  g_error (Error reading host file [%s:%d]: %s, (efn ? efn : filename), config_error_line(hcfg), config_error_text(hcfg));
++  g_printerr (Error reading host file [%s:%d]: %s\n, (efn ? efn : filename), config_error_line(hcfg), config_error_text(hcfg));
+ #else
+-  g_error (Error reading host file %s!, filename);
++  g_printerr (Error reading host file %s!\n, filename);
+ #endif
+ 	config_destroy(hcfg);
+ 	return (FALSE);
+@@ -305,7 +305,7 @@ GList *loadHosts (const char *filename)
+ 
+ config_setting_t *cfghosts = config_lookup(hcfg, Hosts);
+ if(cfghosts == NULL) {
+-	g_error (%s: No Hosts entries found., filename);
++	g_printerr (%s: No Hosts entries found.\n, filename);
+ 	config_destroy(hcfg);
+ 	return (FALSE);
+ }
diff -Nru apt-dater-1.0.1/debian/patches/series apt-dater-1.0.1/debian/patches/series
--- apt-dater-1.0.1/debian/patches/series	1970-01-01 00:00:00.0 +
+++ apt-dater-1.0.1/debian/patches/series	2014-11-20 12:52:45.0 +
@@ -0,0 +1 @@
+00_fix_segfaults_when_dot_in_conffile.patch

Bug#771463: CVE-2014-8418 CVE-2014-8412 CVE-2014-8414 CVE-2014-8417

[Moritz Muehlenhoff]

Source: asterisk
Severity: grave
Tags: security

Please see
http://downloads.digium.com/pub/security/AST-2014-018.html
http://downloads.digium.com/pub/security/AST-2014-017.html
http://downloads.digium.com/pub/security/AST-2014-014.html
http://downloads.digium.com/pub/security/AST-2014-012.html

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#770982: Patch

[Paulo Assis]

Hi,

2014-11-29 14:55 GMT+00:00 Matt Kraai kr...@ftbfs.org:
 Hi,

 On Sat, Nov 29, 2014 at 10:24:45AM +, Paulo Assis wrote:
 This is fixed in version 0.2.5.
 source packages (signed) can be found here:
 https://drive.google.com/folderview?id=0B0_qxcVSvJFMOTcyOFJRNkFaWjAusp=sharing

 If someone can upload this, it would be appreciated.

 I can upload it, but I'm afraid that it won't be allowed into testing.
 According to

  https://release.debian.org/jessie/freeze_policy.html

 new upstream releases shouldn't be included, only fixes for bugs of
 important severity or higher, as well as translation and documentation
 fixes.

Argh! I wasn't aware of those timings.
In any case the new release should eventually go into unstable (after
the fix to 0.2.4).


 Would you mind if I made an non-maintainer upload based on the
 following patch?

I have no problem with this, I think it will also be faster.

Regards,
Paulo

 Would you prefer I sponsor an upload by you that
 just fixes this bug?

 diff -Nru libwebcam-0.2.4/debian/changelog libwebcam-0.2.4/debian/changelog
 --- libwebcam-0.2.4/debian/changelog2013-11-01 16:49:24.0 -0700
 +++ libwebcam-0.2.4/debian/changelog2014-11-29 06:52:05.0 -0800
 @@ -1,3 +1,10 @@
 +libwebcam (0.2.4-1.1) unstable; urgency=medium
 +
 +  * Non-maintainer upload.
 +  * Install dynctrl-logitech.h (Closes: #770982)
 +
 + -- Matt Kraai kr...@debian.org  Sat, 29 Nov 2014 06:52:05 -0800
 +
  libwebcam (0.2.4-1) unstable; urgency=low

* Bump to version 0.2.4 (Closes: #713548)
 diff -Nru libwebcam-0.2.4/debian/libwebcam0-dev.install 
 libwebcam-0.2.4/debian/libwebcam0-dev.install
 --- libwebcam-0.2.4/debian/libwebcam0-dev.install   2013-11-01 
 16:49:24.0 -0700
 +++ libwebcam-0.2.4/debian/libwebcam0-dev.install   2014-11-28 
 15:32:56.0 -0800
 @@ -1,3 +1,4 @@
 +usr/include/dynctrl-logitech.h
  usr/include/webcam.h
  usr/lib/libwebcam.a
  usr/lib/libwebcam.so
 diff -Nru libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h 
 libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h
 --- libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h   1969-12-31 
 16:00:00.0 -0800
 +++ libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h   2014-11-28 
 15:29:48.0 -0800
 @@ -0,0 +1,13 @@
 +Index: libwebcam-0.2.4/libwebcam/CMakeLists.txt
 +===
 +--- libwebcam-0.2.4.orig/libwebcam/CMakeLists.txt  2013-10-31 
 14:47:36.0 -0700
  libwebcam-0.2.4/libwebcam/CMakeLists.txt   2014-11-28 15:29:32.063070089 
 -0800
 +@@ -103,7 +103,7 @@
 + )
 +
 + install (
 +-  FILES   ../common/include/webcam.h
 ++  FILES   ../common/include/webcam.h 
 ../common/include/dynctrl-logitech.h
 +   DESTINATION ${CMAKE_INSTALL_PREFIX}/include
 + )
 +
 diff -Nru libwebcam-0.2.4/debian/patches/series 
 libwebcam-0.2.4/debian/patches/series
 --- libwebcam-0.2.4/debian/patches/series   2013-11-01 16:49:24.0 
 -0700
 +++ libwebcam-0.2.4/debian/patches/series   2014-11-28 15:29:13.0 
 -0800
 @@ -0,0 +1 @@
 +install-dynctrl-logitech.h

 --
 Matt


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

Bug#726093: python-scipy: CVE-2013-4251: weave /tmp and current directory issues

[Moritz Mühlenhoff]

On Wed, Oct 23, 2013 at 08:04:17AM +0200, Salvatore Bonaccorso wrote:
 Hi Julian,
 
 On Wed, Oct 23, 2013 at 01:16:36AM +0200, Julian Taylor wrote:
  On 22.10.2013 08:43, Salvatore Bonaccorso wrote:
   Hi Julian,
   
   Cc'ing Julian directly as per short discussion on IRC.
   
   On IRC you mentioned that you are looking at this issue. Did you had a
   chance to prepare the upload for unstable?
   
  
  I have prepared updates for unstable, wheezy and squeeze, which require
  sponsoring:
  
  http://anonscm.debian.org/viewvc/python-modules/packages/scipy/branches/
  
  for wheezy and squeeze a little extra checking if the
  packaging/versioning is done correctly is appreciated as this is my
  first stable update in debian.
  
  Tested the packages by running scipys testsuite and a couple weave
  commands on all supported python versions.
 
 Thanks for you update. I only had a look at the unstable version (so
 far at least), and looks good. I have uploaded it as provided by you.
 (Only small nitpick, please always include the CVE reference in the
 changelog as this will ease the work of the security team tracking
 the issues).
 
 For uploads to (old-)stable, please see [1]. (btw, the versioning
 0.7.2+dfsg1-1+squeeze1 for oldstable, and 0.10.1+dfsg2-1+deb7u1 for
 stable looks good).

This is still unfixed in Wheezy, do you still plan to fix this in a
Wheezy point update?

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#771466: CVE-2013-7108 CVE-2013-7205

[Moritz Muehlenhoff]

Package: nagios3
Severity: grave
Tags: security

Hi,
there are a few older Nagios security vulnerabilities which are still
open in the jessie version. Could you check with upstream on their
status?

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7108
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7205

The proposed upstream fix isn't yet present in 3.5.1:
http://sourceforge.net/p/nagios/nagioscore/ci/d97e03f32741a7d851826b03ed73ff4c9612a866/

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#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

[Shannon Dealy]

On Sat, 29 Nov 2014, Nikolaus Rath wrote:


On 11/29/2014 09:49 AM, Shannon Dealy wrote:

Package: s3ql
Version: 2.11.1+dfsg-1
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

While running rsync to backup data to an s3ql file system mounted from Amazon's
S3 services, the internet connection failed, resulting in the following

[snip]

Chances are good that this can be done, so don't give up hope yet.

Best,
-Nikolaus


Attached are both the mount and fsck log files, stripped of data from 
other (irrelevent) sessions and with slight mods to remove references to 
my S3 file system info (bucket/prefix).


I have left the original bucket and local cache unmodified except for 
whatever changes occured during my fsck attempt in case they can be of 
use in debugging this.


Regards,

Shannon C. Dealy   | DeaTech Research Inc.
de...@deatech.com  |- Custom Software Development -
USA Phone: +1 800-467-5820 |- Natural Building Instruction -
numbers  : +1 541-929-4089 |www.deatech.com2014-11-28 18:08:52.029 31159:MainThread (name)s.determine_threads: Using 8 
upload threads.
2014-11-28 18:08:52.032 31159:MainThread (name)s.main: Autodetected 4040 file 
descriptors available for cache entries
2014-11-28 18:09:00.435 31159:MainThread (name)s.get_metadata: Using cached 
metadata.
2014-11-28 18:09:00.439 31159:MainThread (name)s.main: Mounting filesystem...
2014-11-28 18:09:00.448 31163:MainThread (name)s.detach_process_context: 
Daemonizing, new PID is 31167
2014-11-29 02:14:44.787 31167:Thread-9 (name)s.wrapped: Encountered 
ConnectionTimedOut exception (send/recv timeout exceeded), retrying call to 
ObjectW.close for the 3-th time...
2014-11-29 10:49:36.636 31167:Thread-10 (name)s.excepthook: Uncaught top-level 
exception:
Traceback (most recent call last):
  File /usr/lib/s3ql/s3ql/mount.py, line 66, in run_with_except_hook
run_old(*args, **kw)
  File /usr/lib/python3.4/threading.py, line 868, in run
self._target(*self._args, **self._kwargs)
  File /usr/lib/s3ql/s3ql/block_cache.py, line 404, in _upload_loop
self._do_upload(*tmp)
  File /usr/lib/s3ql/s3ql/block_cache.py, line 431, in _do_upload
% obj_id).get_obj_size()
  File /usr/lib/s3ql/s3ql/backends/common.py, line 46, in wrapped
return method(*a, **kw)
  File /usr/lib/s3ql/s3ql/backends/common.py, line 258, in perform_write
return fn(fh)
  File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 477, in __exit__
self.close()
  File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 471, in close
self.fh.close()
  File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 636, in close
self.fh.close()
  File /usr/lib/s3ql/s3ql/backends/common.py, line 46, in wrapped
return method(*a, **kw)
  File /usr/lib/s3ql/s3ql/backends/s3c.py, line 845, in close
headers=self.headers, body=self.fh)
  File /usr/lib/s3ql/s3ql/backends/s3c.py, line 409, in _do_request
query_string=query_string, body=body)
  File /usr/lib/s3ql/s3ql/backends/s3c.py, line 642, in _send_request
headers=headers, body=BodyFollowing(body_len))
  File /usr/lib/python3/dist-packages/dugong/__init__.py, line 477, in 
send_request
self.timeout)
  File /usr/lib/python3/dist-packages/dugong/__init__.py, line 1361, in 
eval_coroutine
if not next(crt).poll(timeout=timeout):
  File /usr/lib/python3/dist-packages/dugong/__init__.py, line 504, in 
co_send_request
self.connect()
  File /usr/lib/python3/dist-packages/dugong/__init__.py, line 408, in connect
self._sock = socket.create_connection((self.hostname, self.port))
  File /usr/lib/python3.4/socket.py, line 509, in create_connection
raise err
  File /usr/lib/python3.4/socket.py, line 500, in create_connection
sock.connect(sa)
OSError: [Errno 113] No route to host
2014-11-29 10:50:11.907 31167:Thread-9 (name)s.exchook: Unhandled top-level 
exception during shutdown (will not be re-raised)
2014-11-29 10:50:11.907 31167:Thread-9 (name)s.excepthook: Uncaught top-level 
exception:
Traceback (most recent call last):
  File /usr/lib/s3ql/s3ql/mount.py, line 66, in run_with_except_hook
run_old(*args, **kw)
  File /usr/lib/python3.4/threading.py, line 868, in run
self._target(*self._args, **self._kwargs)
  File /usr/lib/s3ql/s3ql/block_cache.py, line 404, in _upload_loop
self._do_upload(*tmp)
  File /usr/lib/s3ql/s3ql/block_cache.py, line 431, in _do_upload
% obj_id).get_obj_size()
  File /usr/lib/s3ql/s3ql/backends/common.py, line 46, in wrapped
return method(*a, **kw)
  File /usr/lib/s3ql/s3ql/backends/common.py, line 258, in perform_write
return fn(fh)
  File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 477, in __exit__
self.close()
  File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 471, in close
self.fh.close()
  File /usr/lib/s3ql/s3ql/backends/comprenc.py, line 636, in close
self.fh.close()
  File /usr/lib/s3ql/s3ql/backends/common.py, line 46, in wrapped
return method(*a, **kw)
  File 

Bug#771470: ltsp-client-core: Kernel version sorting may result in booting obsolete kernel

[Vagrant Cascadian]

Package: ltsp-client-core
Version: 5.5.4-1
Severity: serious
Tags: patch

When upgrading an LTSP environment from Wheezy, LTSP's kernel sorting
rules generate a pxelinux.cfg/ltsp file that defaults to the -486
Wheezy kernel variant, instead of the -586 variant present in Jessie.
This results in clients booting an old kernel and quite possibly
missing security updates.

Additionally, if the configures IFCPU64=true in
/etc/ltsp/update-kernels.conf which should set up pxelinux entries to
boot the appropriate kernel based 32-bit, PAE or 64-bit machines, the
rules always pick the lowest common denominator for all the kernels
(and adding insult to injury, the lowest possible version).

I plan to upload a fixed version shortly...

The following patches were committed upstream, and should resolve this
issue:

From: Alkis Georgopoulos alk...@gmail.com
Date: Sat, 29 Nov 2014 17:51:04 +0200
Subject: [PATCH 15/17] Correctly sort kernel FLAVOR in increasing order and
 VERSION in decreasing.

---
 client/Debian/etc/ltsp/update-kernels.conf| 2 +-
 client/Debian/share/ltsp/cleanup.d/50-vmlinuz | 2 +-
 client/Ubuntu/etc/ltsp/update-kernels.conf| 2 +-
 client/share/ltsp/update-kernels  | 4 ++--
 server/ltsp-update-kernels| 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/client/Debian/etc/ltsp/update-kernels.conf 
b/client/Debian/etc/ltsp/update-kernels.conf
index b22e0a6..97131b5 100644
--- a/client/Debian/etc/ltsp/update-kernels.conf
+++ b/client/Debian/etc/ltsp/update-kernels.conf
@@ -28,7 +28,7 @@ CMDLINE_NBD=root=/dev/nbd0
 CMDLINE_AOE=root=/dev/etherd/e0.0
 
 # A sed expression that matches all kernels and returns $FILE $NAME $VERSION 
$FLAVOR
-# Example: ls /boot | sed -n $KERNEL_NAMES | sort -V -k 4,4  | sort -r -k 3,3
+# Example: ls /boot | sed -n $KERNEL_NAMES | sort -k 4,4V -k 3,3rV
 KERNEL_NAMES='s/\(vmlinu[xz]-\)\([^-]*-[^-]*-\)\(.*\)/ \1 \2 \3/p'
 
 # A sed expression that maps from a kernel name to an initrd name
diff --git a/client/Debian/share/ltsp/cleanup.d/50-vmlinuz 
b/client/Debian/share/ltsp/cleanup.d/50-vmlinuz
index 3a88d30..82fb818 100644
--- a/client/Debian/share/ltsp/cleanup.d/50-vmlinuz
+++ b/client/Debian/share/ltsp/cleanup.d/50-vmlinuz
@@ -14,7 +14,7 @@ INITRD_NAME=${INITRD_NAME:-'s/vmlinu[xz]/initrd.img/p'}
 
 read file name version flavor EOF
 $(find /boot/ -mindepth 1 -maxdepth 1 -type f -printf %f\n |
-sed -n $KERNEL_NAMES | sort -V -k 4,4  | sort -r -k 3,3)
+sed -n $KERNEL_NAMES | sort -k 4,4V -k 3,3rV)
 EOF
 initrd=$(echo $file | sed -n $INITRD_NAME)
 
diff --git a/client/Ubuntu/etc/ltsp/update-kernels.conf 
b/client/Ubuntu/etc/ltsp/update-kernels.conf
index 059cd68..6e3d2f8 100644
--- a/client/Ubuntu/etc/ltsp/update-kernels.conf
+++ b/client/Ubuntu/etc/ltsp/update-kernels.conf
@@ -28,7 +28,7 @@ CMDLINE_NBD=root=/dev/nbd0
 CMDLINE_AOE=root=/dev/etherd/e0.0
 
 # A sed expression that matches all kernels and returns $FILE $NAME $VERSION 
$FLAVOR
-# Example: ls /boot | sed -n $KERNEL_NAMES | sort -V -k 4,4  | sort -r -k 3,3
+# Example: ls /boot | sed -n $KERNEL_NAMES | sort -k 4,4V -k 3,3rV
 KERNEL_NAMES='s/\(vmlinu[xz]-\)\([^-]*-[^-]*-\)\(.*\)/ \1 \2 \3/p'
 
 # A sed expression that maps from a kernel name to an initrd name
diff --git a/client/share/ltsp/update-kernels b/client/share/ltsp/update-kernels
index 61e7eae..96310fb 100755
--- a/client/share/ltsp/update-kernels
+++ b/client/share/ltsp/update-kernels
@@ -67,7 +67,7 @@ kernel_split() {
 ;;
 esac
 done
-done | sed -n $KERNEL_NAMES | sort -V -k 4,4  | sort -r -k 3,3
+done | sed -n $KERNEL_NAMES | sort -k 4,4V -k 3,3rV
 
 eval $orig_flags
 }
@@ -102,7 +102,7 @@ cmdline_method_default=$(eval echo 
'$CMDLINE_'$boot_method_default)
 BOOTPROMPT_OPTS=$CMDLINE_LINUX_DEFAULTS $cmdline_method_default
 
 # A sed expression that matches all kernels and returns $FILE $NAME $VERSION 
$FLAVOR
-# Example: ls /boot | sed -n $KERNEL_NAMES | sort -V -k 4,4  | sort -r -k 3,3
+# Example: ls /boot | sed -n $KERNEL_NAMES | sort -k 4,4V -k 3,3rV
 KERNEL_NAMES=${KERNEL_NAMES:-'s/\(vmlinu[xz]-\)\([^-]*-[^-]*-\)\(.*\)/ \1 \2 
\3/p'}
 
 if [ -f /usr/lib/yaboot/yaboot ]; then
diff --git a/server/ltsp-update-kernels b/server/ltsp-update-kernels
index 4a71b2b..3e08149 100755
--- a/server/ltsp-update-kernels
+++ b/server/ltsp-update-kernels
@@ -151,7 +151,7 @@ link_kernel_flavors() {
 
 last_flavor=
 find $tftpname -mindepth 1 -maxdepth 1 -type f -printf %f\n \
-| sed -n $KERNEL_NAMES | sort -V -k 4,4  | sort -r -k 3,3 \
+| sed -n $KERNEL_NAMES | sort -k 4,4V -k 3,3rV \
 | while read file name version flavor; do
 if [ $flavor != $last_flavor ]; then
 initrd=$(echo $file | sed -n $INITRD_NAME)
-- 
2.1.3

From: Vagrant Cascadian vagr...@debian.org
Date: Sat, 29 Nov 2014 10:57:26 -0800
Subject: [PATCH 16/17] update-kernels: Fix issues with kernel version variant
 sorting by first looping on the preferred 

Bug#771471: scribus: Hyphenation in Scribus still doesn't work

[Ondra Kudlík]

Package: scribus
Version: 1.4.4+dfsg1-2+b1
Severity: grave
Justification: renders package unusable

Hi,

this is directly related to #762942 I'm opening new bug report as
previous is closed/archived.

Accroding to me severity is grave as Scribus is now unusable for
multiple languages (we know about Spanish and Czech but probably much
more). I know that only hyphenation is not working but Scribus is
desktop publishing software and without hyphenation it simply can't do
its job.

I don't think that new whishlist severity bug #771438 is enough to
solve this problem.

Please be also aware that this is regression. In Wheezy, there is no
problem with hyphenation at all. I'm not exactly sure how are
release-critical bugs decided but I think that Scribus is important
part of Debian distribution so important enought to fit in this
category.

Probably really important thing to know is that in LibreOffice,
hyphenation (at least Czech one) is working without any trouble.

Thanks for looking into this.

Kind Regards,

Kepi

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages scribus depends on:
ii  ghostscript9.06~dfsg-1.1+b1
ii  libc6  2.19-13
ii  libcairo2  1.14.0-2.1
ii  libcups2   1.7.5-9
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.5.2-2
ii  libgcc11:4.9.2-4
ii  libhunspell-1.3-0  1.3.3-3
ii  libhyphen0 2.8.8-2
ii  libjpeg62-turbo1:1.3.1-11
ii  liblcms2-2 2.6-3+b3
ii  libpodofo0.9.0 0.9.0-1.2+b2
ii  libpython2.7   2.7.9~rc1-1
ii  libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libstdc++6 4.9.2-4
ii  libtiff5   4.0.3-10+b3
ii  libxml22.9.2+dfsg1-1
ii  python-tk  2.7.8-2
pn  python:any none
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages scribus recommends:
ii  cups-bsd1.7.5-9
ii  fonts-liberation1.07.4-1
ii  hyphen-en-us [hyphen-hyphenation-patterns]  2.8.8-2
ii  hyphen-sh [hyphen-hyphenation-patterns] 1:3.3.0-4
ii  icc-profiles-free   2.0.1+dfsg-1
ii  ttf-bitstream-vera  1.10-8
ii  xfonts-scalable 1:1.0.3-1

Versions of packages scribus suggests:
ii  icc-profiles   2.0.1-1
pn  scribus-docnone
ii  scribus-template   1.2.4.1-2
ii  texlive-latex-recommended  2014.20141024-1

-- no debconf information


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

Bug#771449: Killer is killing logged in users

[Petter Reinholdtsen]

[Alexander Alemayhu]
 Dear Maintainer,

 While logged in on a tjener I was logged out multiple times and was
 told by Petter that killer killed me. He also mentioned the bug might
 be related to a change in ps.

I investigated, and discovered that when the username was 'skolelinux',
ps showed 'skolelin+' as the username, causing killer to fail to
understand the processes in question belonged to a logged in user.
Apparently procps changed the last few months to not print the uid for
usernames not fitting in the reserved space for usernames, and instead
truncate the username and adding a plus at the end.

I found a fix with the help from #debian-devel, where I tell ps to
always return uids by add 'n' to the command line.

The fix is commited to git and uploaded to unstable.  We need to ask the
release managers to allow this fix into Jessie to avoid breaking Debian
Edu completely.  With this bug in place, no user with a long username
can be logged in more than an hour.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#755202: Possibly related bug

[Martin Steigerwald]

Hello!

On my laptop I found

Bug#771077: changes mac address of eth0 of every disconnect

maybe what I found there is related to this bug?

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


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

Bug#765870: systemd-logind brings system to knees with RAM consumption

[John Goerzen]

I have not yet had the chance to migrate this system to boot with
systemd.  The problem is also not yet resolved.  However, the logind
processes now consume far less RAM:

$ ps auxww | grep logind
root   503  0.0  0.0  28388  2892 ?SNov27   0:00
/lib/systemd/systemd-logind
root  1665  0.0  0.0  28388  2996 ?SNov27   0:00
/lib/systemd/systemd-logind
root  1756  0.0  0.0  28388  2976 ?S16:18   0:00
/lib/systemd/systemd-logind
jgoerzen  3283  0.0  0.0  12720  2252 pts/4S+   16:56   0:00 grep logind
root  4260  0.0  0.0  28356  2900 ?SNov26   0:00
/lib/systemd/systemd-logind
root  4357  0.0  0.0  28388  2996 ?SNov28   0:00
/lib/systemd/systemd-logind
root  4861  0.0  0.0  28388  2916 ?S07:18   0:00
/lib/systemd/systemd-logind
root  4969  0.0  0.0  28388  2924 ?SNov28   0:00
/lib/systemd/systemd-logind
root  6062  0.0  0.0  28388  3020 ?SNov27   0:00
/lib/systemd/systemd-logind
root  7394  0.0  0.0  28536  3156 ?SNov27   0:00
/lib/systemd/systemd-logind
root 10347  0.0  0.0  28388  2940 ?SNov27   0:00
/lib/systemd/systemd-logind
root 11349  0.0  0.0  28388  2980 ?SNov28   0:00
/lib/systemd/systemd-logind
root 11368  0.0  0.0  28388  2924 ?SNov28   0:00
/lib/systemd/systemd-logind
root 13397  0.0  0.0  28388  3028 ?SNov27   0:00
/lib/systemd/systemd-logind
root 14562  0.0  0.0  28388  2988 ?SNov26   0:00
/lib/systemd/systemd-logind
root 15616  0.0  0.0  28388  3032 ?S09:19   0:00
/lib/systemd/systemd-logind
root 16399  0.0  0.0  28388  2968 ?SNov27   0:00
/lib/systemd/systemd-logind
root 17532  0.0  0.0  28388  2940 ?S00:19   0:00
/lib/systemd/systemd-logind
root 17807  0.0  0.0  28388  3024 ?SNov28   0:00
/lib/systemd/systemd-logind
root 20332  0.0  0.0  28388  3036 ?SNov27   0:00
/lib/systemd/systemd-logind
root 20692  0.0  0.0  28388  2952 ?SNov26   0:00
/lib/systemd/systemd-logind
root 21986  0.0  0.0  28388  2972 ?S12:17   0:00
/lib/systemd/systemd-logind
root 22824  0.0  0.0  28388  2940 ?SNov27   0:00
/lib/systemd/systemd-logind
root 23886  0.0  0.0  28388  3032 ?SNov28   0:00
/lib/systemd/systemd-logind
root 24545  0.0  0.0  28388  2980 ?S03:00   0:00
/lib/systemd/systemd-logind
root 26550  0.0  0.0  28388  3028 ?SNov27   0:00
/lib/systemd/systemd-logind
root 27408  0.0  0.0  28388  2956 ?SNov26   0:00
/lib/systemd/systemd-logind
root 27965  0.0  0.0  28388  2944 ?S14:17   0:00
/lib/systemd/systemd-logind
root 27978  0.0  0.0  28616  3136 ?SNov28   0:00
/lib/systemd/systemd-logind
root 30090  0.0  0.0  28388  2908 ?SNov28   0:00
/lib/systemd/systemd-logind
root 30738  0.0  0.0  28388  2912 ?S05:17   0:00
/lib/systemd/systemd-logind
root 31298  0.0  0.0  28388  2940 ?SNov27   0:00
/lib/systemd/systemd-logind

So the problem is not nearly so bad any more.

John

On 11/20/2014 03:11 PM, Sjoerd Simons wrote:
 Hey John,

 On Sun, Nov 09, 2014 at 06:13:30PM -0600, John Goerzen wrote:
 I will try this.  It is a bit complicated because the system in question
 is also running ZFS and there are some bugs with that boot, but I think
 I have worked them out enough.  It may take me a few days to find the
 time, however.
 Did you find the time to get this system booting with systemd? Would be great
 to further narrow it down.


 On 11/03/2014 08:43 PM, Michael Biebl wrote:
 Am 18.10.2014 um 21:49 schrieb John Goerzen:
 Package: systemd
 Version: 215-5+b1
 Severity: grave
 Justification: renders package unusable

 On investigating why my 8GB system, which was suddenly running extremely
 slow and maxed out on swap, I discovered numerous systemd-logind
 processes hogging RAM.  Specifically, 41 processes using 4278148KB (or
 roughly 4GB) of RAM.

 Here is some output from top:

 As John told me on IRC: He is running systemd-logind under systemd-shim
 on this particular system.
 On other systems, where systemd is PID 1 he does not experience this
 issue.
 I told him to find out the current running systemd-logind process which
 owns the org.freedesktop.login1 D-Bus name via
 dbus-send --system --dest=org.freedesktop.DBus --print-reply
 /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID
 string:org.freedesktop.login1

 and monitor that process via strace while periodically checking with the
 above command, when logind drops off the bus. So we can eventually see
 from the strace what happens at that time.

 Unfortunately, when stracing the process, John is no longer able to
 reproduce the issue, as he told on IRC.

 John, to narrow down the problem, could you please boot with
 init=/bin/systemd to verify if this 

Bug#771360: marked as done (CVE-2010-5109)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 23:04:26 +
with message-id e1xur3y-0004wu...@franck.debian.org
and subject line Bug#771360: fixed in claws-mail 3.11.1-2
has caused the Debian Bug report #771360,
regarding CVE-2010-5109
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.)


-- 
771360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: claws
Severity: grave
Tags: security

Hi,
claws-mail embeds a copy of libytnef:

| claws-mail (3.10.1-1) unstable; urgency=medium
|
|  - Remove libytnef dependency: it was assimilated (and modified)

But it's missing the security fix CVE-2010-5109, I'm attaching the
patch from src:libytnef

Can you please fix this for jessie and forward the patch upstream?

Cheers,
Moritz
Index: b/ytnef.c
===
--- a/ytnef.c
+++ b/ytnef.c
@@ -1328,7 +1328,7 @@
 
 comp_Prebuf.size = strlen(RTF_PREBUF);
 comp_Prebuf.data = calloc(comp_Prebuf.size, 1);
-strcpy(comp_Prebuf.data, RTF_PREBUF);
+memcpy(comp_Prebuf.data, RTF_PREBUF, comp_Prebuf.size);
 
 src = p-data;
 in = 0;
---End Message---
---BeginMessage---
Source: claws-mail
Source-Version: 3.11.1-2

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

Debian distribution maintenance software
pp.
Ricardo Mones mo...@debian.org (supplier of updated claws-mail package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Nov 2014 23:03:27 +0100
Source: claws-mail
Binary: claws-mail claws-mail-dbg libclaws-mail-dev claws-mail-plugins 
claws-mail-spamassassin claws-mail-pgpmime claws-mail-pgpinline 
claws-mail-smime-plugin claws-mail-bogofilter claws-mail-i18n claws-mail-doc 
claws-mail-tools claws-mail-extra-plugins claws-mail-acpi-notifier 
claws-mail-address-keeper claws-mail-archiver-plugin claws-mail-attach-remover 
claws-mail-attach-warner claws-mail-bsfilter-plugin claws-mail-clamd-plugin 
claws-mail-fancy-plugin claws-mail-feeds-reader claws-mail-fetchinfo-plugin 
claws-mail-gdata-plugin claws-mail-libravatar claws-mail-newmail-plugin 
claws-mail-mailmbox-plugin claws-mail-multi-notifier claws-mail-tnef-parser 
claws-mail-perl-filter claws-mail-pdf-viewer claws-mail-python-plugin 
claws-mail-spam-report claws-mail-vcalendar-plugin
Architecture: source amd64 all
Version: 3.11.1-2
Distribution: unstable
Urgency: high
Maintainer: Ricardo Mones mo...@debian.org
Changed-By: Ricardo Mones mo...@debian.org
Description:
 claws-mail - Fast, lightweight and user-friendly GTK+2 based email client
 claws-mail-acpi-notifier - Laptop's Mail LED control for Claws Mail
 claws-mail-address-keeper - Address keeper plugin for Claws Mail
 claws-mail-archiver-plugin - Archiver plugin for Claws Mail
 claws-mail-attach-remover - Mail attachment remover for Claws Mail
 claws-mail-attach-warner - Missing attachment warnings for Claws Mail
 claws-mail-bogofilter - Bogofilter plugin for Claws Mail
 claws-mail-bsfilter-plugin - Spam filtering using bsfilter for Claws Mail
 claws-mail-clamd-plugin - ClamAV socket-based plugin for Claws Mail
 claws-mail-dbg - Debug symbols for Claws Mail mailer
 claws-mail-doc - User documentation for Claws Mail mailer
 claws-mail-extra-plugins - Extra plugins collection for Claws Mail
 claws-mail-fancy-plugin - HTML mail viewer using GTK+2 WebKit
 claws-mail-feeds-reader - Feeds (RSS/Atom) reader plugin for Claws Mail
 claws-mail-fetchinfo-plugin - Add X-FETCH headers plugin for Claws Mail
 claws-mail-gdata-plugin - Access to GData (Google services) for Claws Mail
 claws-mail-i18n - Locale data for Claws Mail (i18n support)
 claws-mail-libravatar - Display sender avatar from a libravatar server
 claws-mail-mailmbox-plugin - mbox format mailboxes handler for Claws Mail
 claws-mail-multi-notifier - Various new mail notifiers for Claws Mail
 claws-mail-newmail-plugin - New mail logger plugin for Claws Mail
 claws-mail-pdf-viewer - PDF and PostScript attachment viewer for Claws Mail
 

Bug#766943: marked as done (systemd: server no longer gets networking after switching to systemd)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 23:04:33 +
with message-id e1xur45-0004yp...@franck.debian.org
and subject line Bug#766943: fixed in ifupdown 0.7.50
has caused the Debian Bug report #766943,
regarding systemd: server no longer gets networking after switching to systemd
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.)


-- 
766943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: systemd
Version: 215-5+b1
Severity: important


Hi.

Tonight I switched my last server still running with sysvinit to
systemd, since I've experience no major problems with it on my other
systems.

That server however, didn't come up anymore (i.e. not even pinging
back).
I've sent a Ctrl-Alt-Del event via the hosting company's web interface,
and it actually came back and I could log in.

The logs from syslog didn't show much interesting stuff, only that
apache httpd (which runs on that node) couldn't bind to the IPv4
addres.


I've rebooted another time then (and several more times since then), but
now it's back to no booting (or rather said: no networking - at least
the first time where it didn't work, syslog showed, that it actually
started up, and also got a clean shutdown).


I can't say much about the system or logs right now,... it's a physical
machine, IPv4 and v6 addresses, brought up via ifupdown using allow-auto
for eth0 in /e/n/interfaces.
It uses mdadm with a RAID1.

The only other special thing that I remember is, that I use
rootdelay=10
as a kernel parameter.
TBH, I forgot why, but there was something that the disks were detected
too lated and the initramfs could never mount the rootfs.
But that shoudln't affect systemd, right?




I write the bug already now, since it's really complicated to get
access to the server by other means,... hetzner (the company) does provide
some KVM interface, but that's implemented quite insecurely and it costs
when one needs it for a longer time.

So it would be great if you could already tell me in advance which logs
to look for, and which things to test.

Obviously I'll set systemd.log_level=debug at the kernel command line...
anything else?


Cheers,
Chris.

-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-57
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.25.2-2
ii  libc6   2.19-12
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-3
ii  libgcrypt20 1.6.2-4
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-5+b1
ii  sysv-rc 2.88dsf-57
ii  udev215-5+b1
ii  util-linux  2.25.2-2

Versions of packages systemd recommends:
ii  dbus1.8.8-2
ii  libpam-systemd  215-5+b1

Versions of packages systemd suggests:
ii  systemd-ui  3-2

-- Configuration Files:
/etc/systemd/logind.conf changed [not included]

-- no debconf information
---End Message---
---BeginMessage---
Source: ifupdown
Source-Version: 0.7.50

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

Debian distribution maintenance software
pp.
Andrew Shadura andre...@debian.org (supplier of updated ifupdown package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Nov 2014 14:32:32 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.7.50
Distribution: unstable
Urgency: medium
Maintainer: Andrew Shadura andre...@debian.org
Changed-By: Andrew Shadura andre...@debian.org
Description:
 ifupdown   - high level tools to configure network interfaces
Closes: 709378 741579 

Bug#765870: systemd-logind brings system to knees with RAM consumption

[Cameron Norman]

On Sat, Nov 29, 2014 at 2:57 PM, John Goerzen jgoer...@complete.org wrote:
 I have not yet had the chance to migrate this system to boot with
 systemd.  The problem is also not yet resolved.  However, the logind
 processes now consume far less RAM:

 [snip]

So you did reboot and the problem persisted? What kernel version are
you running (IIRC someone reported problems with 3.14 and
systemd-shim, however that was not definite)? And what does `loginctl
show-sessions` output?

Thank you,
--
Cameron Norman


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

Processed: tagging 771360, block 771360 with 771474

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 771360 + jessie fixed-upstream
Bug #771360 {Done: Ricardo Mones mo...@debian.org} [claws-mail-tnef-parser] 
CVE-2010-5109
Added tag(s) fixed-upstream and jessie.
 block 771360 with 771474
Bug #771360 {Done: Ricardo Mones mo...@debian.org} [claws-mail-tnef-parser] 
CVE-2010-5109
771360 was not blocked by any bugs.
771360 was not blocking any bugs.
Added blocking bug(s) of 771360: 771474
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771360
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#706877: Re: Bug#706877: insserv: breaks dist-upgrade by installing before packages fix their init scripts

[Marcelo Lacerda]

I have tried to install task-xfce-desktop, clementine, virtualbox on a 
fresh install of wheezy and do a dist upgrade while running virtualbox 
and clementine and I encounter no errors. Am I missing something?



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

Bug#727800: kmail: KMail goes bonkers following Qt update

[Lisandro Damián Nicanor Pérez Meyer]

On Saturday 29 November 2014 15:05:58 Shai Berger wrote:
 Hi,
 
 On Wednesday 26 November 2014 15:21:15 you wrote:
  Hi! As Sandro pointed out, this seems fixed in newer versions. Can you
  please test if this is still an issue for you?

[snip]

 I can try to copy the user from testing to sid and see how the upgrade goes,
 although this would be a lengthy process; would that be helpful?

Yes, this could really help. Please note that you should copy ~/.kde and 
*maybe* ~/.config to the new user. Thanks a lot!!!

 On a side note -- I see that mails sent to the bug are no longer sent to the
 submitter automatically (except when sent to -submitter specifically);

It never was as far as I remember :)

 is this on purpose?

Yes, sometimes mainatiners discuss the bug but it would be quite noisy for the 
submitter.

 It is a bit of a problem. Feel free to include my
 address explicitly in replies.

You can always subscribe to the bug by:

- Mailing nn-subscr...@bugs.debian.org where nn is the bug number
- Clicking on the subscribe link in the bug page (which will try to send the 
above mail).

-- 
You know it's love when you memorize her IP number to skip DNS overhead.
  Anonymous

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#727800: kmail: KMail goes bonkers following Qt update

[Lisandro Damián Nicanor Pérez Meyer]

Shai: please also note Diane's workaround: maybe restarting akonadi after the 
upgrade solves the issue.

That would be:

- Unlog from KDE
- Do the upgrade (in you case, create the new user and copy the data)
- Log in

Then wait some minutes, if you see the process doesn't ends open a console and 
restart akonadi.

I'm CCing Diane to see if I missed or made a mistake at some point.

Kinds regards, Lisandro.

-- 
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#770242: marked as done (rkhunter: upgrade/post-install errors)

[Debian Bug Tracking System]

Your message dated Sat, 29 Nov 2014 23:50:20 +
with message-id e1xurmo-00022h...@franck.debian.org
and subject line Bug#770242: fixed in rkhunter 1.4.2-0.4
has caused the Debian Bug report #770242,
regarding rkhunter: upgrade/post-install errors
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.)


-- 
770242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: rkhunter
Version: 1.4.2-0.3
Severity: important

During Wheezy to Jessie upgrade (1.4.0-1 -- 1.4.2-0.3) I encountered
the following error after when I've chosen to keep currently-installed
version of /etc/rkhunter.conf:


Invalid SCRIPTWHITELIST configuration option: Non-existent pathname: 
/usr/sbin/prelink
E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/rkhunter ]  
grep -qiE '^APT_AUTOGEN=.?(true|yes)' /etc/default/rkhunter; then 
/usr/share/rkhunter/scripts/rkhupd.sh; fi'
E: Sub-process returned an error code


It seems to be due to SCRIPTWHITELIST=/usr/sbin/prelink in default
/etc/rkhunter.conf installed by rkhunter/1.4.0-1.
I do not have prelink installed on my system and I've never changed this 
particular
configuration option.

I removed rkhunter (but did not purge it), deleted /etc/rkhunter.conf
and tried to install rkhunter again:


Selecting previously unselected package rkhunter.
(Reading database ... 339181 files and directories currently installed.)
Preparing to unpack .../rkhunter_1.4.2-0.3_all.deb ...
Unpacking rkhunter (1.4.2-0.3) ...
Processing triggers for man-db (2.7.0.2-3) ...
Setting up rkhunter (1.4.2-0.3) ...
grep: /etc/rkhunter.conf: No such file or directory
dpkg: error processing package rkhunter (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 rkhunter
Unable to find configuration file: /usr/local/etc/rkhunter.conf
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/rkhunter ]  
grep -qiE '^APT_AUTOGEN=.?(true|yes)' /etc/default/rkhunter; then 
/usr/share/rkhunter/scripts/rkhupd.sh; fi'
E: Sub-process returned an error code


Only purging and re-installing rkhunter was successful.

I did not dig deeper but it looks like something is broken in postinst
configuration handling...



--- System information. ---
Debian Release: jessie/sid

--- Package information. ---
Depends(Version) | Installed
-+-===
file | 1:5.20-2
net-tools| 1.60-26+b1
binutils | 2.24.90.20141023-1
ucf(= 0.28) | 3.0030
perl | 5.20.1-2


Recommends(Version) | Installed
===-+-===
default-mta | 
 OR mail-transport-agent| 
wget| 1.13.4-3+deb7u2
 OR curl| 7.38.0-3
 OR links   | 
 OR elinks  | 
 OR lynx| 2.8.9dev1-2
iproute | 1:3.16.0-2
unhide.rb   | 
 OR unhide  | 20121229-1+b1
lsof| 4.86+dfsg-1


Suggests  (Version) | Installed
===-+-===
bsd-mailx   | 8.1.2-0.20140825cvs-1
 OR mailutils   | 
 OR heirloom-mailx  | 
 OR mailx   | 
tripwire| 
libdigest-whirlpool-perl| 
liburi-perl | 1.64-1
libwww-perl | 6.08-1
powermgmt-base  | 1.31+nmu1


-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


signature.asc
Description: This is a digitally signed message part.
---End Message---
---BeginMessage---
Source: rkhunter
Source-Version: 1.4.2-0.4

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

Debian distribution maintenance software
pp.
Francois Marier franc...@debian.org (supplier of updated rkhunter 

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

[Nikolaus Rath]

On 11/29/2014 01:36 PM, Shannon Dealy wrote:
 On Sat, 29 Nov 2014, Nikolaus Rath wrote:
 
 On 11/29/2014 09:49 AM, Shannon Dealy wrote:
 Package: s3ql
 Version: 2.11.1+dfsg-1
 Severity: critical
 Justification: causes serious data loss

 Dear Maintainer,

 While running rsync to backup data to an s3ql file system mounted
 from Amazon's
 S3 services, the internet connection failed, resulting in the following
 [snip]
 Chances are good that this can be done, so don't give up hope yet.

 Best,
 -Nikolaus
 
 Attached are both the mount and fsck log files, stripped of data from
 other (irrelevent) sessions and with slight mods to remove references to
 my S3 file system info (bucket/prefix).
 
 I have left the original bucket and local cache unmodified except for
 whatever changes occured during my fsck attempt in case they can be of
 use in debugging this.

Great, thanks! It seems you've actually found three issues at once:

1. mount.s3ql not coping well with a failed internet connection (a no
route to host failure, to be precise, it copes quite well with other
failures)

2. fsck.s3ql not being able to fix the local database

3. A bug somewhere that prevents you from fsck'ing a copied bucket.

I'll look into this ASAP.


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


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

Bug#727800: kmail: KMail goes bonkers following Qt update

[Diane Trout]

The sequence for me was:

* do the upgrade
* log in
* the knotes upgrade script runs
* the kmail2 upgrade script runs
* akonadi goes a bit crazy toward the end of the kmail 2 
  upgrade script, but the upgrade script does report 
  upgrade complete
* after the upgrade finished then I restarted akonadi. 
  (Either by doing akonadictl restart or just logging out and back in).

Diane



On Saturday, November 29, 2014 20:48:33 Lisandro Damián Nicanor Pérez Meyer 
wrote:
 Shai: please also note Diane's workaround: maybe restarting akonadi after
 the upgrade solves the issue.
 
 That would be:
 
 - Unlog from KDE
 - Do the upgrade (in you case, create the new user and copy the data)
 - Log in
 
 Then wait some minutes, if you see the process doesn't ends open a console
 and restart akonadi.
 
 I'm CCing Diane to see if I missed or made a mistake at some point.
 
 Kinds regards, Lisandro.



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

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

[Nikolaus Rath]

On 11/29/2014 03:54 PM, Nikolaus Rath wrote:
 1. mount.s3ql not coping well with a failed internet connection (a no
 route to host failure, to be precise, it copes quite well with other
 failures)

This one is actually a bug in python-dugong. I have just fixed this in
https://bitbucket.org/nikratio/python-dugong/commits/36dc1863633b6fe38a02e5ba07dd3b0cf5deeb0f.

The fixed version is unlikely to make it into jessie, but it should be
possible to get a fixed fsck.s3ql into jessie that can clean up the
resulting mess.

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


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

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

[Nikolaus Rath]

On 11/29/2014 03:54 PM, Nikolaus Rath wrote:
 2. fsck.s3ql not being able to fix the local database

This one is more interesting. The traceback looks as if the backend (aka
S3) reports two objects with the same name (which I think should be
impossible). Since S3QL is using the object names as primary keys in a
table, this does not end well.

Could you apply the attached patch to /usr/lib/s3ql/s3ql/fsck.py and
check the original file system again (i.e., not the copy)?

It should crash at the same point as before, but create a file
object_list.txt in the current directory. Please attach that file to
this bug.


Thanks!
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«
diff --git a/src/s3ql/fsck.py b/src/s3ql/fsck.py
--- a/src/s3ql/fsck.py
+++ b/src/s3ql/fsck.py
@@ -829,6 +829,9 @@
 lof_id = self.conn.get_val(SELECT inode FROM contents_v 
WHERE name=? AND parent_inode=?, (blost+found, ROOT_INODE))
 
+# Debugging
+debug_fh = open('object_list.txt', 'w')
+
 # We use this table to keep track of the objects that we have seen
 self.conn.execute(CREATE TEMP TABLE obj_ids (id INTEGER PRIMARY KEY))
 try:
@@ -838,6 +841,8 @@
 sys.stdout.write('\r..processed %d objects so far..' % i)
 sys.stdout.flush()
 
+print(obj_name, file=debug_fh)
+
 # We only bother with data objects
 try:
 obj_id = int(obj_name[10:])

Bug#771177: Matt's patch fixes the problem

[Francois Marier]

I can confirm that Matt's patch fixes the problem. Thanks for extracting the
relevant bits from upstream!

Mehdi, I assume you're ok preparing a 0.39-2 and requesting a freeze
exception for jessie?

I'm happy to help with anything if it's useful.

Francois


signature.asc
Description: Digital signature

Bug#769716: Info received (iceweasel: downloads Cisco's OpenH264 video codec)

[Mike Hommey]

On Sat, Nov 29, 2014 at 04:39:33PM +0100, Christoph Anton Mitterer wrote:
 Honi soit qui mal y pense - CVE-2014-8001.
 
 So no we already have the case of an accidental vulnerability in the
 binary blob... who knows what's really behind that ;)
 
 (And yes, Cisco/Mozilla claim in the meantime that this doesn't affect
 the version spread in binary form - but again... has anyone trustworthy
 verified this?)

https://bugzilla.mozilla.org/show_bug.cgi?id=1105688#c3
You're free to replicate the verification.
Also note this code doesn't run unless you do webrtc calls in h264.

Mike


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

Bug#765870: systemd-logind brings system to knees with RAM consumption

[John Goerzen]

On 11/29/2014 05:09 PM, Cameron Norman wrote:
 On Sat, Nov 29, 2014 at 2:57 PM, John Goerzen jgoer...@complete.org wrote:
 I have not yet had the chance to migrate this system to boot with
 systemd.  The problem is also not yet resolved.  However, the logind
 processes now consume far less RAM:

 [snip]
 So you did reboot and the problem persisted? What kernel version are
Correct.
 you running (IIRC someone reported problems with 3.14 and
 systemd-shim, however that was not definite)? And what does `loginctl
$ uname -a
Linux hephaestus 3.16.0-4-amd64 #1 SMP Debian 3.16.7-2 (2014-11-06)
x86_64 GNU/Linux

 show-sessions` output?
Unknown operation show-sessions ;-)  Perhaps you meant list-sessions?

# loginctl list-sessions
   SESSIONUID USER SEAT   
c2  0 root seat0  
 1   1000 jgoerzen seat0  
  2456  0 root
  2457  0 root
  2458  0 root
  2459  0 root
  2460  0 root
  2461  0 root

8 sessions listed.


 Thank you,
 --
 Cameron Norman



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

Bug#771454: marked as done (libflite1: minimal version in symbols file too old)

[Debian Bug Tracking System]

Your message dated Sun, 30 Nov 2014 01:04:33 +
with message-id e1xuswd-0002vx...@franck.debian.org
and subject line Bug#771454: fixed in flite 1.4-release-12
has caused the Debian Bug report #771454,
regarding libflite1: minimal version in symbols file too old
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.)


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

Package: libflite1
Version: 1.4-release-11
Severity: serious

Dear Maintainer,

the symbols file of libflite1 sets the minimal version for all symbols 
to 1.4-release. But apparently this is not correct:

If libflite1 1.4-release-8 is installed, ffmpeg does not work:

$ ffmpeg
ffmpeg: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libflite_cmu_us_slt.so.1: undefined symbol: 
usenglish_init


Installing libflite1 1.4-release-9 (or newer) fixes this.
Probably the fix for #746383 included in 1.4-release-9 is responsible 
for this.


I think the best way forward is to increase the minimal versions of all 
symbols to 1.4-release-9~ and rebuilt all reverse dependencies against a 
fixed version.


Best regards,
Andreas

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.17.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set 
to C)

Shell: /bin/sh linked to /bin/dash

Versions of packages libflite1 depends on:
ii  libasound2 1.0.28-1
ii  libc6  2.19-13
ii  multiarch-support  2.19-13

libflite1 recommends no packages.

Versions of packages libflite1 suggests:
pn  alsa-base  none

-- no debconf information
---End Message---
---BeginMessage---
Source: flite
Source-Version: 1.4-release-12

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

Debian distribution maintenance software
pp.
Samuel Thibault sthiba...@debian.org (supplier of updated flite package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 30 Nov 2014 01:00:12 +0100
Source: flite
Binary: flite libflite1 flite1-dev
Architecture: source amd64
Version: 1.4-release-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team debian-accessibil...@lists.debian.org
Changed-By: Samuel Thibault sthiba...@debian.org
Description:
 flite  - Small run-time speech synthesis engine
 flite1-dev - Small run-time speech synthesis engine - development files
 libflite1  - Small run-time speech synthesis engine - shared libraries
Closes: 771454
Changes:
 flite (1.4-release-12) unstable; urgency=medium
 .
   * Drop the now-unused ghostscript build dependency.
   * Bump Standards-Version to 3.9.6 (no changes).
   * Bump symbols dependency to 1.4-release-9~, which introduced linking
 between flite libraries, thus making binaries not link against all flite
 libraries (Closes: #771454).
Checksums-Sha1:
 f42a6395473019b8adafbf553bb48276653eb966 2220 flite_1.4-release-12.dsc
 cb4ba5d3bdf9d24bbef2949f2200e79a205dd163 28756 
flite_1.4-release-12.debian.tar.xz
 93175574f497341ceb2a2ad85e490ea55cdb633d 235644 flite_1.4-release-12_amd64.deb
 32eace79ac65bb335e29c7b6d71c7b0cba911cff 13120466 
libflite1_1.4-release-12_amd64.deb
 0d7f924601ba100367311c1f4b27c3a999b181fa 12975552 
flite1-dev_1.4-release-12_amd64.deb
Checksums-Sha256:
 c11b97addf1f3d6b43d62c955447701edd8cc94cfceca09b72df5c8bf27f51d9 2220 
flite_1.4-release-12.dsc
 3e0381236210700078e50178eb9446a738fc01cdcbcdb59114d49b4a17e5da4a 28756 
flite_1.4-release-12.debian.tar.xz
 f6fb86cbc352b1dc3580c540627ad605318a7a28f457fb7c1ca88c6c42c6add8 235644 
flite_1.4-release-12_amd64.deb
 29c40314dab8822ece85899d6817128c69b38a664589c93d767c28135ea98067 13120466 
libflite1_1.4-release-12_amd64.deb
 c3f528f383855c7b3f55f44435e2454f39e7b1909f2d5ca2dfaa6f86e97868b7 12975552 
flite1-dev_1.4-release-12_amd64.deb
Files:
 e0300ebb7a63732e05d2c67b9a8809e0 2220 sound optional flite_1.4-release-12.dsc
 d3728dbb2374af14e02c52268358a55c 28756 

Bug#771480: c-icap: Segmentation Fault with libLLVM-3.0.so.1

[luskin]

Package: c-icap
Version: 1:0.1.6-1.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've added this logrotate file to my system:

--

/var/log/c-icap/*.log {
daily
compress
delaycompress
rotate 31
missingok
nocreate
sharedscripts
postrotate
test ! -e /var/run/c-icap/c-icap.pid || echo -n reconfigure  
/var/run/c-icap/c-icap.ctl
endscript
}

--

After last system update (2 days ago) I've this problem after each daily 
logrotate:

Nov 28 07:36:14 andromeda kernel: [375111.408129] c-icap[5693]: 
segfault at 20 ip 7f936dda29ca sp 7fff305d33e0 error 4 in 
libLLVM-3.0.so.1[7f936d3d+1301000]
Nov 29 07:36:17 andromeda kernel: [461352.882110] c-icap[32150]: 
segfault at 20 ip 7fca64edc9ca sp 7fff56132ca0 error 4 in 
libLLVM-3.0.so.1[7fca6450a000+1301000]
Nov 30 00:49:34 andromeda kernel: [523233.843037] c-icap[30766]: 
segfault at 20 ip 7f4504aa09ca sp 7fff430ad210 error 4 in 
libLLVM-3.0.so.1[7f45040ce000+1301000]
Nov 30 01:24:32 andromeda kernel: [525327.612150] c-icap[18178]: 
segfault at 7f708766001c ip 00413bfd sp 7fffdc654830 error 4 in 
c-icap[40+1e000]

It seems to be the reconfigure message to c-icap.ctl to cause the issue (I've 
invoked it manually and got the seg fault to syslog).

Any help?
For now I've bash-scripted a cron watchdog that checks c-icap running at every 
minute and, if needed, restarts it.
Anyway any hint is welcome.

Thank You
Luca



-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

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

Versions of packages c-icap depends on:
ii  adduser  3.113+nmu3
ii  libc62.13-38+deb7u6
ii  libdb5.1 5.1.29-5
ii  libicapapi0  1:0.1.6-1.1
ii  lsb-base 4.1+Debian8+deb7u1

c-icap recommends no packages.

Versions of packages c-icap suggests:
ii  libc-icap-mod-clamav1:0.1.6-1
ii  libc-icap-mod-urlcheck  1:0.1.6-1
ii  squid3  3.1.20-2.2+deb7u2

-- Configuration Files:
/etc/c-icap/c-icap.conf changed:
PidFile /var/run/c-icap/c-icap.pid
CommandsSocket /var/run/c-icap/c-icap.ctl
Timeout 300
MaxKeepAliveRequests 100
KeepAliveTimeout 600  
StartServers 3
MaxServers 10
MinSpareThreads 10
MaxSpareThreads 20
ThreadsPerChild 10
MaxRequestsPerChild  0
Port 1344 
User c-icap
Group nogroup
ServerAdmin luskin@andromeda.local
ServerName andromeda.local
TmpDir /tmp
MaxMemObject 1048576
DebugLevel 5
ModulesDir /usr/lib/c_icap
ServicesDir /usr/lib/c_icap
TemplateDir /usr/share/c_icap/templates/
TemplateDefaultLanguage en
LoadMagicFile /etc/c-icap/c-icap.magic
RemoteProxyUsers off
RemoteProxyUserHeader X-Authenticated-User
RemoteProxyUserHeaderEncoded on
ServerLog /var/log/c-icap/server.log
AccessLog /var/log/c-icap/access.log
Service echo srv_echo.so
Include srv_clamav.conf
Include srv_url_check.conf

/etc/default/c-icap changed:
START=yes
DAEMON_OPTS=-d 9


-- no debconf information


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

Bug#771417: dpkg: possible repeated messages on trigger processing errors

[Guillem Jover]

Control: severity -1 minor
Control: retitle -1 dpkg: possible repeated messages on trigger processing error

Hi!

On Sat, 2014-11-29 at 12:14:04 +0100, Eduard Bloch wrote:
 Package: dpkg
 Version: 1.17.22
 Severity: grave

 today I tried to dist-upgrade my system (sid) starting from a package
 state of a couple of weeks ago. First apt reported a failed dpkg right
 in the middle of the upgrade process without displaying any visible
 error messages.

That would be apt bug #765687.

 Now when I run apt-get -f install or attempt to
 install some missing package explicitly, it ends up in a loop where dpkg
 runs maintainer scripts on dbus without end. Here is dpkg.log and some
 console output:

And this seems to be related to apt bug #771428. I assume that if you
just run «dpkg --configure --pending» the problem will get sorted out.

If this cannot be fixed in apt, because it requires it to upgrade
itself first, then I guess making dbus switch to a noawaiting trigger
directive should work, and I don't think it needs the awaiting variant
so that would be a correct fix anyway.

 dpkg: dependency problems prevent processing triggers for dbus:
  dbus depends on libexpat1 (= 2.0.1); however:
   Package libexpat1:amd64 is not configured yet.
·
 dpkg: error processing package dbus (--configure):
  dependency problems - leaving triggers unprocessed
[…]
 dpkg: too many errors, stopping
 Errors were encountered while processing:
  dbus
[…]
  dbus
 Processing was halted because there were too many errors.
 E: Sub-process /usr/bin/dpkg returned an error code (1)

In any case the above duplicated error messages, is a known (at least
to me) minor issue that is caused by dpkg detecting the error for the
triggers case, but not making it known to the queue processor to avoid
trying to go on the same path and just quiting outright. Which in the
end gets stopped by the too many errors check dpkg has.

I left it as is, because a fix was going to be too intrusive at this
point of the freeze, and as this is always a problem in the packages
(a trigger cycle) or in the frontend, and the possible dpkg processing
loop always gets caught, it ends up being mostly a cosmetic issue.

Thanks,
Guillem


-- 
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#771417: dpkg: possible repeated messages on trigger processing errors

[Debian Bug Tracking System]

Processing control commands:

 severity -1 minor
Bug #771417 [dpkg] bogus dpkg error, now endless loop on dbus configuration
Severity set to 'minor' from 'grave'
 retitle -1 dpkg: possible repeated messages on trigger processing error
Bug #771417 [dpkg] bogus dpkg error, now endless loop on dbus configuration
Changed Bug title to 'dpkg: possible repeated messages on trigger processing 
error' from 'bogus dpkg error, now endless loop on dbus configuration'

-- 
771417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771417
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#766762: marked as done (upower: fatal memory leak on low battery)

[Debian Bug Tracking System]

Your message dated Sun, 30 Nov 2014 01:49:16 +
with message-id e1xutdu-0007s9...@franck.debian.org
and subject line Bug#766762: fixed in upower 0.99.1-3.1
has caused the Debian Bug report #766762,
regarding upower: fatal memory leak on low battery
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.)


-- 
766762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: upower
Version: 0.99.1-3
Severity: important

Hi,

twice now my notebook grinded to a halt cause upowerd consumed more than
1.5G of memory:

27460 root   20   0 1947396 1.630g   1396 S   0.0 45.7   2:18.29 upowerd

This appears to happen when the battery is running very low and upowerd
needs to kick in.

This seems to be a known bug upstream:

https://bugs.freedesktop.org/show_bug.cgi?id=82659

And a (draft) patch exists:

https://bugs.freedesktop.org/attachment.cgi?id=105169
https://bugs.freedesktop.org/attachment.cgi?id=105170


Michael

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages upower depends on:
ii  dbus   1.8.8-2
ii  libc6  2.19-11
ii  libdbus-1-31.8.8-2
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.42.0-2
ii  libgudev-1.0-0 215-5+b1
ii  libimobiledevice4  1.1.6+dfsg-3.1
ii  libplist2  1.11-3
ii  libupower-glib30.99.1-3
ii  libusb-1.0-0   2:1.0.19-1
ii  udev   215-5+b1

Versions of packages upower recommends:
ii  policykit-1  0.105-7

upower suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
Source: upower
Source-Version: 0.99.1-3.1

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

Debian distribution maintenance software
pp.
Michael Banck mba...@debian.org (supplier of updated upower package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 28 Nov 2014 16:24:34 +0100
Source: upower
Binary: upower upower-doc libupower-glib3 libupower-glib-dev 
gir1.2-upowerglib-1.0
Architecture: source amd64 all
Version: 0.99.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 
pkg-utopia-maintain...@lists.alioth.debian.org
Changed-By: Michael Banck mba...@debian.org
Description:
 gir1.2-upowerglib-1.0 - GObject introspection data for upower
 libupower-glib-dev - abstraction for power management - development files
 libupower-glib3 - abstraction for power management - shared library
 upower - abstraction for power management
 upower-doc - abstraction for power management - documentation
Closes: 766762
Changes:
 upower (0.99.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/git-fix-memleak.patch
 - Memleak fix.  Taken from upstream git head, commit 4221835f (Closes:
   #766762).
Checksums-Sha1:
 7757c4b3000a09a8203aee3cd380f427c9e86e13 2636 upower_0.99.1-3.1.dsc
 7c195c6a2f18d465012243c481e693eb0ac0ef85 15260 upower_0.99.1-3.1.debian.tar.xz
 386f0c3e8ce49c5f505b25761b4ff7e3ebf03918 88568 upower_0.99.1-3.1_amd64.deb
 d93dbf01a355ffc6103ad20408e0260ca3eac304 41080 upower-doc_0.99.1-3.1_all.deb
 796e5baf60fe97b5e6c259e72fffab74c55ba66b 47408 
libupower-glib3_0.99.1-3.1_amd64.deb
 42465a1afeedcdcdef2023c56b073755c12f8b9f 65744 
libupower-glib-dev_0.99.1-3.1_amd64.deb
 23dbac51330d772c0c765a88029b0fa6826688e1 16300 
gir1.2-upowerglib-1.0_0.99.1-3.1_amd64.deb
Checksums-Sha256:
 b6ebee7923f39bb6c532699556a839159feda0838e38e18f7f089d98f9d3fd86 2636 
upower_0.99.1-3.1.dsc
 6b63a78c9291160ace27daf5ed3c394dc97298d5117a14555bd6465780742406 15260 
upower_0.99.1-3.1.debian.tar.xz
 e8179e5ca089269367a88f15603c7ef09f6b15bb2635aa57ebcfae62b4490645 88568 
upower_0.99.1-3.1_amd64.deb
 

Bug#727800: kmail: KMail goes bonkers following Qt update

[Diane Trout]

Some more details about trying to debug this:

I did akonadictl restart in a terminal so I could see log messages from 
akonadi.

Then I ran /usr/bin/kmail-migrator --interactive 

After a bit it started constantly printing:

akonadi_maildispatcher_agent($pid)/libakonadi: Resource id's don't match: 
akonadi_mixedmaildir_resource_0 akonadi_maildir_resource_0

the kmail-migrator seems to be from kdepim-runtime and seems to be the binary 
automatically launched when you start kmail the first time after upgrading.

The mail spool had been configured with both imap and a local maildir.

Diane



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

Bug#771484: selinux-policy-default: GPG is totally broken

[Russell Coker]

Package: selinux-policy-default
Version: 2:2.20140421-7
Severity: grave
Justification: renders package unusable

gpg doesn't work on the command-line, gpg-agent can't be statted, and the
whole X login process that spawns gpg-agent doesn't work for most user roles.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages selinux-policy-default depends on:
ii  libpam-modules   1.1.8-3.1
ii  libselinux1  2.3-2
ii  libsepol12.3-2
ii  policycoreutils  2.3-1
ii  python   2.7.8-2
ii  selinux-utils2.3-2

Versions of packages selinux-policy-default recommends:
ii  checkpolicy  2.3-1
ii  setools  3.3.8-3.1

Versions of packages selinux-policy-default suggests:
pn  logchecknone
pn  syslog-summary  none

-- Configuration Files:
/etc/selinux/default/modules/active/file_contexts.local [Errno 13] Permission 
denied: u'/etc/selinux/default/modules/active/file_contexts.local'

-- no debconf information


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

Bug#758516: marked as done (Struts 1.2 should not be shipped with jessie)

[Debian Bug Tracking System]

Your message dated Sun, 30 Nov 2014 04:22:25 +
with message-id e1xuw1h-0008kg...@franck.debian.org
and subject line Bug#771464: Removed package(s) from unstable
has caused the Debian Bug report #758516,
regarding Struts 1.2 should not be shipped with jessie
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.)


-- 
758516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libstruts1.2-java
Severity: serious

Struts 1.x is EOLed upstream, it should not be included in jessie:
http://mail-archives.apache.org/mod_mbox/struts-announcements/201404.mbox/%3C535F5F52.4040108%40apache.org%3E

Cheers,
Moritz
---End Message---
---BeginMessage---
Version: 1.2.9-9+rm

Dear submitter,

as the package libstruts1.2-java has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/771464

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)---End Message---

Processed: fixed 771125 in 1.5.23-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 fixed 771125 1.5.23-2
Bug #771125 [mutt] mutt: CVE-2014-9116: write_one_header can call 
mutt_substrdup with begin  end, leading to crash
Marked as fixed in versions mutt/1.5.23-2.
 thanks
Stopping processing here.

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

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 found 771360 3.10.1-1
Bug #771360 {Done: Ricardo Mones mo...@debian.org} [claws-mail-tnef-parser] 
CVE-2010-5109
Marked as found in versions claws-mail/3.10.1-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771360
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#771496: overwrites user changes to configuration file /etc/dpkg-cross/cross-compile on upgrade (violates 10.7.3)

[Helmut Grohne]

Package: dpkg-cross
Version: 2.6.11
Severity: serious
Justification: policy 10.7.3
User: helm...@debian.org
Usertags: rebootstrap

When upgrading dpkg-cross, the file /etc/dpkg-cross/cross-compile is
overwritten by dpkg-cross.postinst regardless of what it contains. This
behaviour violates the Debian policy section 10.7.3.

Test case:

# apt-get install dpkg-cross
...
# echo # some change  /etc/dpkg-cross/cross-compile
# apt-get install --reinstall dpkg-cross
...
# grep some change /etc/dpkg-cross/cross-compile
#

The last command fails whereas it should succeed.

Helmut


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