Bug#777931: marked as done (ktp-common-internals: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 05:33:39 +
with message-id 
and subject line Bug#777931: fixed in ktp-common-internals 0.9.0-2
has caused the Debian Bug report #777931,
regarding ktp-common-internals: ftbfs with GCC-5
to be marked as done.

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

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


-- 
777931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ktp-common-internals
Version: 0.8.1-4
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/ktp-common-internals_0.8.1-4_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
  _ZN3KTp14ContactFactory6createERKN2Tp8FeaturesE@Base 0.8.0
  _ZN3KTp14ContactFactoryC1ERKN2Tp8FeaturesE@Base 0.8.0
  _ZN3KTp14ContactFactoryC2ERKN2Tp8FeaturesE@Base 0.8.0
- _ZN3KTp14ContactFactoryD0Ev@Base 0.8.0
- _ZN3KTp14ContactFactoryD1Ev@Base 0.8.0
- _ZN3KTp14ContactFactoryD2Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp14ContactFactoryD0Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp14ContactFactoryD1Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp14ContactFactoryD2Ev@Base 0.8.0
  _ZN3KTp14GlobalPresence11qt_metacallEN11QMetaObject4CallEiPPv@Base 0.8.0
  _ZN3KTp14GlobalPresence11qt_metacastEPKc@Base 0.8.0
  _ZN3KTp14GlobalPresence11setPresenceERKN2Tp8PresenceE@Base 0.8.0
@@ -70,9 +70,9 @@
  _ZN3KTp14GlobalPresence26onRequestedPresenceChangedEv@Base 0.8.0
  _ZN3KTp14GlobalPresenceC1EP7QObject@Base 0.8.0
  _ZN3KTp14GlobalPresenceC2EP7QObject@Base 0.8.0
- _ZN3KTp14GlobalPresenceD0Ev@Base 0.8.0
- _ZN3KTp14GlobalPresenceD1Ev@Base 0.8.0
- _ZN3KTp14GlobalPresenceD2Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp14GlobalPresenceD0Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp14GlobalPresenceD1Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp14GlobalPresenceD2Ev@Base 0.8.0
  
_ZN3KTp14MessageContextC1ERKN2Tp9SharedPtrINS1_7AccountEEERKNS2_INS1_11TextChannelEEE@Base
 0.8.0
  
_ZN3KTp14MessageContextC2ERKN2Tp9SharedPtrINS1_7AccountEEERKNS2_INS1_11TextChannelEEE@Base
 0.8.0
  _ZN3KTp14MessageContextD0Ev@Base 0.8.0
@@ -272,9 +272,9 @@
  _ZN3KTp7Contact21invalidateAvatarCacheEv@Base 0.8.0
  
_ZN3KTp7ContactC1EPN2Tp14ContactManagerERKNS1_17ReferencedHandlesERKNS1_8FeaturesERK4QMapI7QString8QVariantE@Base
 0.8.0
  
_ZN3KTp7ContactC2EPN2Tp14ContactManagerERKNS1_17ReferencedHandlesERKNS1_8FeaturesERK4QMapI7QString8QVariantE@Base
 0.8.0
- _ZN3KTp7ContactD0Ev@Base 0.8.0
- _ZN3KTp7ContactD1Ev@Base 0.8.0
- _ZN3KTp7ContactD2Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp7ContactD0Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp7ContactD1Ev@Base 0.8.0
+#MISSING: 0.8.1-4# _ZN3KTp7ContactD2Ev@Base 0.8.0
  _ZN3KTp7Message11setPropertyEPKcRK8QVariant@Base 0.8.0
  _ZN3KTp7Message12appendScriptERK7QString@Base 0.8.0
  _ZN3KTp7Message17appendMessagePartERK7QString@Base 0.8.0
@@ -430,6 +430,6 @@
  _ZTVN3KTp7ContactE@Base 0.8.0
  _ZTVN3KTp7MessageE@Base 0.8.0
  (c++)"non-virtual thunk to KTp::CircularCountdown::~CircularCountdown()@Base" 
0.8.0
- (c++)"non-virtual thunk to KTp::Contact::~Contact()@Base" 0.8.0
+#MISSING: 0.8.1-4# (c++)"non-virtual thunk to KTp::Contact::~Contact()@Base" 
0.8.0
  (c++)"non-virtual thunk to KTp::ContactInfoDialog::~ContactInfoDialog()@Base" 
0.8.0
  (c++)"non-virtual thunk to KTp::PersistentContact::~PersistentContact()@Base" 
0.8.0
dh_makeshlibs: failing due to earlier errors
make: *** [binary-arch] Error 2
debian/rules:4: recipe for target 'binary-arch' failed
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2
--- End 

Bug#801101: marked as done (manila-scheduler: fails to install, trying to overwrite other packages files: /usr/bin/manila-scheduler)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 15:40:41 +
with message-id 
and subject line Bug#801101: fixed in manila 1.0.0~rc1-2
has caused the Debian Bug report #801101,
regarding manila-scheduler: fails to install, trying to overwrite other 
packages files: /usr/bin/manila-scheduler
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.)


-- 
801101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manila-scheduler
Version: 1.0.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package manila-scheduler.
  (Reading database ... 
(Reading database ... 15123 files and directories currently installed.)
  Preparing to unpack .../manila-scheduler_1.0.0~rc1-1_all.deb ...
  Unpacking manila-scheduler (1.0.0~rc1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manila-scheduler_1.0.0~rc1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/manila-scheduler', which is also in package 
manila-common 1.0.0~rc1-1
  Processing triggers for systemd (226-4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/manila-scheduler_1.0.0~rc1-1_all.deb


cheers,

Andreas


manila-scheduler_1.0.0~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: manila
Source-Version: 1.0.0~rc1-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated manila package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Oct 2015 14:20:36 +
Source: manila
Binary: python-manila manila-common manila-api manila-scheduler manila-share 
manila-doc
Architecture: source all
Version: 1.0.0~rc1-2
Distribution: experimental
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 manila-api - OpenStack shared file system as a service - API server
 manila-common - OpenStack shared file system as a service - common files
 manila-doc - OpenStack shared file system as a service - Doc
 manila-scheduler - OpenStack shared file system as a service - Scheduler server
 manila-share - OpenStack shared file system as a service - Share server
 python-manila - OpenStack shared file system as a service - Python libs
Closes: 801101
Changes:
 manila (1.0.0~rc1-2) experimental; urgency=medium
 .
   * Do not duplicate /usr/bin/manila-scheduler in both -common and -scheduler
 packages (Closes: #801101).
Checksums-Sha1:
 8f7641bd064b00d845cd5445b1e011c8353f8ccd 3647 manila_1.0.0~rc1-2.dsc
 d22797b78890629eaafbaa288dff18dd8fc73a06 5268 manila_1.0.0~rc1-2.debian.tar.xz
 b4705eec37b74e5a4b2493fc5bf0143a0fefb3e5 5016 manila-api_1.0.0~rc1-2_all.deb
 ecbd44015eea44e2c4136d039584c80d06d4b927 18470 
manila-common_1.0.0~rc1-2_all.deb
 898b629a4c91401fa20bc30e4805fe545af7a5ea 386622 manila-doc_1.0.0~rc1-2_all.deb
 f8868ebbe0d3cf41b7d904ce7882ecfda134f812 5002 
manila-scheduler_1.0.0~rc1-2_all.deb
 84eb151aaef1def829e45046193abf515ef94fa7 4976 manila-share_1.0.0~rc1-2_all.deb
 67563cc8548b4183bc40a37c23f58508d08dc5e5 518922 
python-manila_1.0.0~rc1-2_all.deb
Checksums-Sha256:
 cbb5cefc353fbd5c80d9e1e0fbf5c170621295f5419acf14244fe4ed59f740e8 3647 
manila_1.0.0~rc1-2.dsc
 b048d2fbbab4434830769fb6f571fbaaa498e39dbdaec12078f7112b2d42767d 5268 
manila_1.0.0~rc1-2.debian.tar.xz
 5640367912b323b1588605e5bd7dc0b4820e4b32f60cb4ec1c3c793f630975d1 5016 
manila-api_1.0.0~rc1-2_all.deb
 b533e0f34e1a8508f93536b9c9044420c99222db23cc9a61021a07ecae8531f2 18470 

Bug#796118: Re: Should djbdns be removed?

[Ondřej Surý]

> On Tue, Sep 08, 2015 at 08:29:18PM +0200, Moritz Mühlenhoff wrote:
> > On Wed, Aug 19, 2015 at 05:45:30PM +0200, Moritz Muehlenhoff wrote:
> > > djbdns is RC-buggy for many years now and was out of testing since 2009.
> > > Should we remove it from unstable?
> 
> No, I don't think so.

Any solid arguments supporting your opinion?

djbdns is RC buggy, upstream orphaned, outdated, has to be heavily
patched, doesn't support recent DNS standards and it still even carries
old J-ROOT IP address that was decommissioned a ***13*** years ago.

I myself started my DNS journey with djbdns years ago, and I always
loved the code-style. It's very well written, but the world has moved
on, and it's time to *let it go*. Just let it go and let it rest in
peace, Gerrit.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

Processed: tagging 800617

[Debian Bug Tracking System]

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

> # multiple confirmations
> tags 800617 - moreinfo unreproducible
Bug #800617 [gnome-keyring] Fails to provide secrets
Removed tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.

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

Bug#788957: marked as done (uwsgi: FTBFS: debian/rules:99: *** ERROR: multiple Ruby kinds not supported. Stop.)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 15:42:46 +
with message-id 
and subject line Bug#788957: fixed in uwsgi 2.0.11.1-1
has caused the Debian Bug report #788957,
regarding uwsgi: FTBFS: debian/rules:99: *** ERROR: multiple Ruby kinds not 
supported. Stop.
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.)


-- 
788957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uwsgi
Version: 2.0.7-1
Severity: serious
Tags: stretch sid experimental

uwsgi no longer builds in sid or experimental:
(tested in an up-to-date pbuilder environment)


I: Running cd tmp/buildd/*/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" 
dpkg-buildpackage -us -uc  -rfakeroot
dpkg-buildpackage: source package uwsgi
dpkg-buildpackage: source version 2.0.7-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Jonas Smedegaard 
dpkg-buildpackage: host architecture amd64
 dpkg-source --before-build uwsgi-2.0.7
 fakeroot debian/rules clean
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:99: *** ERROR: multiple Ruby kinds not supported.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
E: Failed autobuilding of package


and failed in experimental on the buildds as well:
https://buildd.debian.org/status/package.php?p=uwsgi=experimental


Andreas
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.11.1-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uwsgi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Oct 2015 15:18:21 +0200
Source: uwsgi
Binary: uwsgi uwsgi-dbg uwsgi-core uwsgi-emperor uwsgi-plugins-all 
uwsgi-infrastructure-plugins uwsgi-app-integration-plugins 
uwsgi-mongodb-plugins uwsgi-plugin-alarm-curl uwsgi-plugin-alarm-xmpp 
uwsgi-plugin-curl-cron uwsgi-plugin-emperor-pg uwsgi-plugin-glusterfs 
uwsgi-plugin-rados uwsgi-plugin-rbthreads uwsgi-plugin-fiber uwsgi-plugin-geoip 
uwsgi-plugin-graylog2 uwsgi-plugin-gevent-python uwsgi-plugin-greenlet-python 
uwsgi-plugin-asyncio-python uwsgi-plugin-asyncio-python3 
uwsgi-plugin-tornado-python uwsgi-plugin-gccgo uwsgi-plugin-jvm-openjdk-7 
uwsgi-plugin-jwsgi-openjdk-7 uwsgi-plugin-ring-openjdk-7 
uwsgi-plugin-servlet-openjdk-7 uwsgi-plugin-ldap uwsgi-plugin-lua5.1 
uwsgi-plugin-lua5.2 uwsgi-plugin-luajit uwsgi-plugin-mono uwsgi-plugin-psgi 
uwsgi-plugin-python uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.1 
uwsgi-plugin-router-access uwsgi-plugin-sqlite3 uwsgi-plugin-v8 
uwsgi-plugin-php uwsgi-plugin-xslt libapache2-mod-proxy-uwsgi 
libapache2-mod-proxy-uwsgi-dbg
 libapache2-mod-uwsgi libapache2-mod-uwsgi-dbg libapache2-mod-ruwsgi 
libapache2-mod-ruwsgi-dbg python-uwsgidecorators python3-uwsgidecorators
 uwsgi-extra
Architecture: source amd64 all
Version: 2.0.11.1-1
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Jonas Smedegaard 
Description:
 libapache2-mod-proxy-uwsgi - uwsgi proxy module for Apache2 (mod_uwsgi)
 libapache2-mod-proxy-uwsgi-dbg - debugging symbols for Apache2 mod_proxy_uwsgi
 libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
 libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi
 libapache2-mod-uwsgi - uwsgi module for Apache2 (mod_uwsgi)
 libapache2-mod-uwsgi-dbg - debugging symbols for Apache2 mod_uwsgi
 python-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 2)
 python3-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 3)
 uwsgi  - fast, self-healing application container 

Bug#800481: [Debian-med-packaging] Bug#800481: dcmtk: versioned -dev package makes transitions too painful

[Emilio Pozuelo Monfort]

Control: severity -1 important

On 03/10/15 11:55, Gert Wollny wrote:
> On Fri, 2015-10-02 at 15:57 +0200, Mathieu Malaterre wrote:
> 
>> Forgot to quote section §8.4 Development files
>>
>> https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s
>> -sharedlibs-dev
>>
>> [...]
>> If there are development files associated with a shared library, the
>> source package needs to generate a binary development package named
>> librarynamesoversion-dev, or if you prefer
>> [...]
>>
> 
> And the sentence continues 
> 
> [...] 
> , or if you prefer only to support one development version at a time,
> libraryname-dev. 
> [...]
> 
> IMHO adding the so-name to the -dev package makes only sense if the
> different -dev packages can co-exist, like , e.g., libgtk2.0-dev and
> libgtk3-dev, something that is clearly not the case for the 
> libdcmtkN-dev packages, because here we talk about a transition. 

Yes, exactly. It makes little sense to version the -dev package and change it
with every SONAME bump if you don't also rename the source package. In this
situation, transitions are unnecessarily hard because all the rdeps need
sourceful uploads. This bug was triggered because of this:

https://release.debian.org/transitions/html/auto-dcmtk.html

where all your rdeps build-dep on libdcmtk2-dev.

Perhaps the severity is inflated. I don't mind to downgrade this, but now you
have to either fix the rdeps (and do so for every transition, which is not nice)
or stop renaming the package. [Or let libdcmtk4-dev provide libdcmtk2-dev... but
that approach seems odd...]

Cheers,
Emilio

Processed: Re: [Debian-med-packaging] Bug#800481: dcmtk: versioned -dev package makes transitions too painful

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #800481 [src:dcmtk] dcmtk: versioned -dev package makes transitions too 
painful
Severity set to 'important' from 'serious'

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

Processed: bug 800873 is forwarded to https://github.com/rsyslog/rsyslog/issues/546

[Debian Bug Tracking System]

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

> forwarded 800873 https://github.com/rsyslog/rsyslog/issues/546
Bug #800873 [src:rsyslog] rsyslog: FTBFS due to failing tests
Set Bug forwarded-to-address to 'https://github.com/rsyslog/rsyslog/issues/546'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#799811: gcc-5: Segfaults with LD_BIND_NOW set in environment

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #799811 [gcc-5] gcc-5: Segfaults with LD_BIND_NOW set in environment
Severity set to 'serious' from 'important'

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

Bug#794929: dms-dr: fails to upgrade from 'jessie': Starting PostgreSQL 9.4 database server: dms main failed!

[Matt Grant]

Hi!

Is this not just a cascade failure because postgresql-common failed to upgrade?

Did you check postgresql-9.4 itself?

My gut tells me that is what you should first confirm

Regards,

Matt Grant



On Sat, 08 Aug 2015 11:03:57 +0200 Andreas Beckmann  wrote:
> Package: dms-dr
> Version: 1.0.3-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
> 
> >From the attached log (scroll to the bottom...):
> 
> [...]
>   Setting up postgresql-client-common (169) ...
>   Setting up postgresql-client-9.4 (9.4.4-1) ...
>   Setting up ssl-cert (1.0.36) ...
>   Setting up postgresql-common (169) ...
>   Starting PostgreSQL 9.4 database server: dms main failed!
>   invoke-rc.d: initscript postgresql, action "start" failed.
>   dpkg: error processing package postgresql-common (--configure):
>subprocess installed post-installation script returned error exit status 1
>   dpkg: dependency problems prevent configuration of postgresql-9.4:
>postgresql-9.4 depends on postgresql-common (>= 142~); however:
> Package postgresql-common is not configured yet.
>   
>   dpkg: error processing package postgresql-9.4 (--configure):
>dependency problems - leaving unconfigured
>   dpkg: dependency problems prevent configuration of dms-core:
>dms-core depends on postgresql-9.4; however:
> Package postgresql-9.4 is not configured yet.
>   
>   dpkg: error processing package dms-core (--configure):
>dependency problems - leaving unconfigured
>   dpkg: dependency problems prevent configuration of dms-dr:
>dms-dr depends on dms-core (= 1.0.3-2); however:
> Package dms-core is not configured yet.
>   
>   dpkg: error processing package dms-dr (--configure):
>dependency problems - leaving unconfigured
>   Setting up python3 (3.4.3-4) ...
>   Setting up python3-psycopg2 (2.6.1-1) ...
>   Setting up python3-magcode-core (1.4.7-3) ...
>   Setting up dh-python (2.20150728) ...
>   Processing triggers for libc-bin (2.19-19) ...
>   Errors were encountered while processing:
>postgresql-common
>postgresql-9.4
>dms-core
>dms-dr
> 
> 
> cheers,
> 
> Andreas

-- 
Matt Grant,  Debian and Linux Systems Administration and Consulting
Mobile: 021 0267 0578
Email: m...@mattgrant.net.nz

Bug#801078: elpa-js2-mode: js2-mode uninstallable due to wrong Breaks in elpa-js2-mode

[Vincent Bernat]

 ❦  6 octobre 2015 00:32 +0200, Axel Beckert  :

> js2-mode in Debian unstable is currently uninstallable as it depends on
> elpa-js2-mode and elpa-js2-mode has a "Breaks: js2-mode (<< 20150909-1)"
> instead of a "Breaks: js2-mode (<< 0~20150909-1)". (Note the missing
> "0~" in the first string.)

I don't remember why I did add the Breaks in the first place (the new
package doesn't share files with the old one). I'll upload a fix
shortly. Sorry for the inconvenience.
-- 
Avoid unnecessary branches.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#800629: telepathy-qt FTBFS: fatal error: gst/gstconfig.h: No such file or directory

[Alexandr Akulich]

Hello.

Probably this patch would help:
http://cgit.freedesktop.org/telepathy/telepathy-qt/commit/?id=ec4a3d62b68a57254515f01fc5ea3325ffb1dbfb

Bug#801091: spice: CVE-2015-5261: host memory access from guest using crafted images

[Salvatore Bonaccorso]

Source: spice
Version: 0.12.5-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for spice.

CVE-2015-5261[0]:
host memory access from guest using crafted images

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-5261
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1261889

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#800617: Fails to provide secrets

[peter]

On Sat, 03 Oct 2015 22:04:21 +0200 Mikhail Morfikov 
 wrote:

> Package: gnome-keyring
> Version: 3.18.0-1
> Followup-For: Bug #800617

> So I upgraded everything to sid version as it was before, and then I
> noticed that there's a new version of config files in
> /etc/xdg/autostart/ -- those with gnome* in their name. I had also
> some files in the ~/.config/autostart/ directory, so I removed them
> completely. After reboot, everything seems to be working as it supposed
> to.
>


Thanks for the information

After upgrading I removed  3 /etc/xdg/autostart/ -- those with gnome* in 
their name files


I did not have any  ~/.config/autostart/  files applicable to gnome*

I too seem to have everything ok now with browser and shutdown

cheers

Peter

Bug#797554: libzrtpcpp: GPL linked with OpenSSL without exception

[Niels Thykier]

On Mon, 31 Aug 2015 14:41:04 +0100 Dimitri John Ledkov
 wrote:
> Severity: serious
> Package: libzrtpcpp
> Version: 2.3.4-1
> 
> The packae is GPLv3, yet it links with OpenSSL without an exception.
> 
> Hence it is not-free.
> 
> Regards,
> 
> Dimitri.
> 
> 

I think you mean "non-distributable" (which is worse than "non-free").

Thanks,
~Niels

Bug#801089: spice: CVE-2015-5260: Insufficient validation of surface_id parameter can cause crash

[Salvatore Bonaccorso]

Source: spice
Version: 0.12.5-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for spice.

CVE-2015-5260[0]:
Insufficient validation of surface_id parameter can cause crash

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-5260
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1260822

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

p.s.: working on an update at least for jessie.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Processed: .

[Debian Bug Tracking System]

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

> tags 798534 confirmed
Bug #798534 [src:ruby-bert] ruby-bert ftbfs in unstable
Added tag(s) confirmed.
> tags 798535 confirmed
Bug #798535 [src:ruby-gsl] ruby-gsl ftbfs in unstable
Ignoring request to alter tags of bug #798535 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#798850: update resolved bug

[Simon Frei]

A recent upgrade resolved this bug, it can be closed.

Bug#799449: [pkg-apparmor] Processed: severity of 799449 is serious

[Felix Geyer]

Control: tags -1 - help

This issue is most likely caused by g++ bug #799811.

Felix

Processed: Re: [pkg-apparmor] Processed: severity of 799449 is serious

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - help
Bug #799449 [src:apparmor] apparmor: FTBFS: test suite segfaults on mips and 
mipsel
Removed tag(s) help.

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

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred!

[Axel Beckert]

Control: tag -1 + pending

Hi Peter,

peter green wrote:
> On 31/07/15 03:17, peter green wrote:
> > If/when I get a sucessful build I will upload to raspbian and post
> > a further update to this bug. No intent to NMU in Debian.
>
> After disabling octave support I ran into another less major issue.
> It seems that the package fails to build if tcl/tk 8.6 is installed
> because it gets confused about which version of tcl/tk it should be
> building for and ends up not building the tcl/tk support leading to
> a failure at the packaging stage. So I added some build-conflicts.
> 
> A debdiff for what I have uploaded to raspbian is attached,

Thanks a lot for this work.

> no intent to NMU in Debian.

But I do. I want to get the GNU Data Language (GDL) eco-system back
into Debian Testing.

I plan to soon-ish upload an NMU of plplot based on Peter's patch for
Raspbian plus also targetting https://bugs.debian.org/794857 (Non-free
Lenna image in upstream source.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred!

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #789619 [src:plplot] plplot: FTBFS: CMake Error at 
cmake/modules/pkg-config.cmake:97 (_pkg_check_modules_internal): 
_pkg_check_modules_internal Macro invoked with incorrect arguments
Added tag(s) pending.

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

Bug#779482: severity of 779482 is grave

[Gilles Filippini]

For the record, I've pinged upstream and proposed a patch for ppc64el.
The good news is they seem responsive [1].

[1] 

Unfortunately I couldn't test the usability of my patch yet, because I
didn't succeed with remote X display on ppc64el porterboxes :/

thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Processed: tagging 794857

[Debian Bug Tracking System]

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

> tags 794857 + pending
Bug #794857 [src:plplot] plplot: non DFSG file in the source package
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: bug 800794 is forwarded to https://github.com/pysam-developers/pysam/issues/164

[Debian Bug Tracking System]

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

> forwarded 800794 https://github.com/pysam-developers/pysam/issues/164
Bug #800794 [python-pysam] python-pysam: FTBFS on multiple archs due to cython 
error
Set Bug forwarded-to-address to 
'https://github.com/pysam-developers/pysam/issues/164'.
> thanks
Stopping processing here.

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

Processed: notfixed 796968 in gvfs-bin/1.24.2-1, fixed 796968 in 1.24.2-1, tagging 801071

[Debian Bug Tracking System]

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

> notfixed 796968 gvfs-bin/1.24.2-1
Bug #796968 {Done: Andreas Henriksson } [gvfs-bin] gvfs-bin: 
gvfs-open incorrectly altern uri before opening
The source gvfs-bin and version 1.24.2-1 do not appear to match any binary 
packages
No longer marked as fixed in versions gvfs-bin/1.24.2-1.
> fixed 796968 1.24.2-1
Bug #796968 {Done: Andreas Henriksson } [gvfs-bin] gvfs-bin: 
gvfs-open incorrectly altern uri before opening
Marked as fixed in versions gvfs/1.24.2-1.
> tags 801071 + sid stretch
Bug #801071 [minirok] Should this package be removed?
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#800920: marked as done (X segfaults during startup if fglrx is used)

[Debian Bug Tracking System]

Your message dated Tue, 6 Oct 2015 10:25:54 +0200
with message-id <56138592.5060...@debian.org>
and subject line Re: [Pkg-fglrx-devel] Bug#800920:
has caused the Debian Bug report #800920,
regarding X segfaults during startup if fglrx is used
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.)


-- 
800920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fglrx-driver
Version: 1:15.9-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Upgrading to fglrx 1:15.9-1 on a fully upgraded stretch system led to the
following reproducible error (segfault) on X startup (xinit in this case):

X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.1.0 x86_64 Debian
Current Operating System: Linux oot 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 
(2015-09-27) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 
root=UUID=1dbbda3f-cd01-4119-827e-59af3f1d9556 ro single nomodeset nopat
Build Date: 11 August 2015  10:51:15AM
xorg-server 2:1.17.2-1.1 (http://www.debian.org/support) 
Current version of pixman: 0.33.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  5 01:43:41 2015
(==) Using config file: "/etc/X1as 1/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
(EE) 
(EE) Backtrace:
(EE) 0: X (xorg_backtrace+0x4e) [0x55e58bb2a85e]
(EE) 1: X (0x55e58b977000+0x1b7aa9) [0x55e58bb2eaa9]
(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fa439f2b000+0x35180) 
[0x7fa439f60180]
(EE) 
(EE) Segmentation fault at address 0x0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Xorg.0.log contains no additional errors or warnings

I unsuccessfully tried fixing the problem by...
...regenerating xorg.conf with aticonfig --initial
...purging and reinstalling all fglrx related packages
...checking that all files on system have the correct checksum (debsums),
   including configuration files
...tried stable kernel 3.16 (dkms module compiles without problems)

I am using nomodeset and nopat
X works fine if fglrx is not specified as driver in xorg.conf.

The display shows a black screen with a cursor for a second and then switches
to black with display backlight. This is when the segfault happens. The system
remains responsive and returns to the VT (typing login info and reboot commands
leads to reboot), but the screen remains black.

-- Package-specific info:
Full fglrx package list:
ii  fglrx-atievent 1:15.9-1 amd64events daemon for the non-free AT
rc  fglrx-control  1:15.9-1 amd64control panel for the non-free AT
ii  fglrx-driver   1:15.9-1 amd64non-free ATI/AMD RadeonHD display
ii  fglrx-modules- 1:15.9-1 amd64dkms module source for the non-fr
ii  libfglrx:amd64 1:15.9-1 amd64non-free ATI/AMD RadeonHD display
ii  libfglrx:i386  1:15.9-1 i386 non-free ATI/AMD RadeonHD display
ii  libgl1-fglrx-g 1:15.9-1 amd64proprietary libGL for the non-fre
ii  libgl1-fglrx-g 1:15.9-1 i386 proprietary libGL for the non-fre
ii  libgl1-fglrx-g 1:15.9-1 i386 ATI/AMD binary OpenGL 32-bit libr

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1002:6810] (prog-if 00 
[VGA controller])
Subsystem: XFX Pine Group Inc. Device [1682:9275]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: fglrx_pci


DRM and fglrx Informations from dmesg:
[0.492636] Linux agpgart interface v0.103
[2.155225] fglrx: module license 

Bug#796371: blockdiag: FTBFS: unknown format: SVG

[Julien Cristau]

On Fri, Aug 21, 2015 at 16:16:20 +0100, Chris Lamb wrote:

> Source: blockdiag
> Version: 1.4.7-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> blockdiag fails to build from source in unstable/amd64.
> 
> Poking a bit, blockdiag cannot import itself correctly and thus the
> SVG/PDF/etc. drivers are not loaded during the testsuite:
> 
> src/blockdiag/imagedraw/__init__.py:
> 
> def init_imagedrawers(debug=False):
> for drawer in
> pkg_resources.iter_entry_points('blockdiag_imagedrawers'):
> 
> Not clear why.
> 
As far as I can tell, this is caused by a change in pybuild: instead of
running something like "python setup.py test" from the toplevel source
directory (which works), it runs "python2.7 -m nose" from
.pybuild/pythonX.Y_2.7/build.  The latter directory is missing
blockdiag.egg-info, which means pkg_resources doesn't find any entry
points.  I'm tempted to reassign this to dh-python.

Cheers,
Julien


signature.asc
Description: PGP signature

Bug#797961: ecryptfs-utils removed from testing

[Jon Ander Peñalba]

Hi,

ecryptfs-utils has been removed from testing due to this bug which I think
is a bit of an overkill.

I use this package daily, as all my users have a private directory
(ecryptfs-setup-private) and I don't really use ecryptfs-setup-swap, so
this bug does not affect me, but I'm losing a (IMO) very important
functionality with this package removal.

I've installed the package from sid, but getting it back to testing might
help other users.

Regards,

Bug#799948: glx-alternatives_0.6.1_source.changes ACCEPTED into unstable

[Andreas Beckmann]

On 2015-10-06 01:12, Diederik de Haas wrote:
> On Monday 05 October 2015 21:20:25 Debian FTP Masters wrote:
>> * Temporarily disable the nvidia-drm-outputclass.conf slave alternative.
>> (Closes: #799948)

That isn't a fix, this feature moved to experimental for further
investigation and the bug was reopened there

> How about bug nrs #800051, 800327, 800550 and 800705?
> They looked like the same issue to me and most confirmed that adding the DM 
> user to the video group fixed it (some haven't responded yet).

Having a workaround is nice but we are missing understanding why this
happens depending on the way X is configured for nvidia.


Andreas

Bug#801143: node-url-parse: uninstallable in sid: unsatisfiable dependencies

[Andreas Beckmann]

Package: node-url-parse
Version: 1.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

0m28.7s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmphsMVje', 'apt-get', '-y', 'install', 
'node-url-parse=1.0.2-1']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   node-url-parse : Depends: node-requires-port (>= 0.0.x) but it is not going 
to be installed
Depends: node-querystringify (>= 0.0.x) but it is not going 
to be installed
  E: Unable to correct problems, you have held broken packages.


The available versions:

 node-querystringify | 0.0.3-1 | stretch | source, all
 node-querystringify | 0.0.3-1 | sid | source, all
 node-requires-port  | 0.0.1-1 | stretch | source, all
 node-requires-port  | 0.0.1-1 | sid | source, all

do not satisfy the constraints.


Cheers,

Andreas

Bug#801159: libdjconsole{0,-dev}: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: libdjconsole0,libdjconsole-dev
Version: 0.1.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  jessie->stretch

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

0m56.9s ERROR: WARN: Inadequate results from running adequate!
  libdjconsole0:amd64: missing-copyright-file 
/usr/share/doc/libdjconsole0/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libdjconsole0/copyright
  # ls -lad /usr/share/doc/libdjconsole0
  drwxr-xr-x 2 root root 40 Sep 15 00:54 /usr/share/doc/libdjconsole0
  # ls -la /usr/share/doc/libdjconsole0/
  total 0
  drwxr-xr-x   2 root root   40 Sep 15 00:54 .
  drwxr-xr-x 106 root root 2240 Sep 15 00:54 ..


1m19.6s ERROR: WARN: Inadequate results from running adequate!
  libdjconsole-dev:amd64: missing-copyright-file 
/usr/share/doc/libdjconsole-dev/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libdjconsole-dev/copyright
  # ls -lad /usr/share/doc/libdjconsole-dev
  drwxr-xr-x 2 root root 40 Sep 25 20:19 /usr/share/doc/libdjconsole-dev
  # ls -la /usr/share/doc/libdjconsole-dev/
  total 0
  drwxr-xr-x   2 root root   40 Sep 25 20:19 .
  drwxr-xr-x 111 root root 2340 Sep 25 20:19 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libdjconsole0_0.1.3-2.log.gz
Description: application/gzip

Bug#801156: dpkg: sometimes does not pass old version to postinst on upgrade

[Guillem Jover]

Hi!

On Wed, 2015-10-07 at 01:10:33 +0200, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.18.3
> Severity: serious

> dpkg does not always properly pass the old version number when
> calling "postinst configure" on package upgrades, sometimes there
> is either no or an empty argument.

That's to be expected, the second argument is the last version that
got configured, if no version has ever been configured then the
argument is omitted. Checking now, this is documented in Debian
policy §6.7.

> I have two cases where an 'apt-get dist-upgrade' from jessie to
> stretch calls 'systemd.postinst configure' differently:
> * a minimal jessie chroot (incorrect behavior)
> * a minimal jessie chroot + bash-completion (correct behavior)

> So in these two cases completely different codepaths in the postinst are 
> taken.
> I don't know about other packages, since this is (so far) the only one leaving
> a visible trace from this mistreatment in piuparts. (Well, there are several
> other systemd symlink related problems that nobody managed to debug so far.)

> Attached are two logs where I did this upgrade test with piuparts, but
> it should be quite easy to reproduce it manually.

I've not checked the logs, but I'd assume that in the problematic case
the package has never been configured before, and as such the bug here
is on that specific package.

Thanks,
Guillem

Processed: Re: Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred!

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - pending
Bug #789619 [src:plplot] plplot: FTBFS: CMake Error at 
cmake/modules/pkg-config.cmake:97 (_pkg_check_modules_internal): 
_pkg_check_modules_internal Macro invoked with incorrect arguments
Removed tag(s) pending.

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

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred!

[Axel Beckert]

Control: tag -1 - pending

Hi,

Axel Beckert wrote:
> But I do. I want to get the GNU Data Language (GDL) eco-system back
> into Debian Testing.

While I've got it building fine on my local system, I fail to get it
built inside pbuilder, but I don't get which build-dependency is missing:

[ 78%] Linking D executable x29d
make[3]: Entering directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
[ 78%] Building D object examples/d/CMakeFiles/x30d.dir/x30d.o
[ 78%] Linking D executable x28d
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
[ 78%] Built target x26d
make[3]: Entering directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
Scanning dependencies of target x31d
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
make[3]: Entering directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
[ 78%] Building D object examples/d/CMakeFiles/x31d.dir/x31d.o
[ 78%] Built target x27d
make[3]: Entering directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
Scanning dependencies of target x33d
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
make[3]: Entering directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
[ 78%] Building D object examples/d/CMakeFiles/x33d.dir/x33d.o
collect2: error: ld returned 1 exit status
examples/d/CMakeFiles/x29d.dir/build.make:89: recipe for target 
'examples/d/x29d' failed
make[3]: *** [examples/d/x29d] Error 1
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
CMakeFiles/Makefile2:14389: recipe for target 
'examples/d/CMakeFiles/x29d.dir/all' failed
make[2]: *** [examples/d/CMakeFiles/x29d.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
[ 78%] Linking D executable x30d
collect2: error: ld returned 1 exit status
examples/d/CMakeFiles/x28d.dir/build.make:89: recipe for target 
'examples/d/x28d' failed
make[3]: *** [examples/d/x28d] Error 1
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
CMakeFiles/Makefile2:14351: recipe for target 
'examples/d/CMakeFiles/x28d.dir/all' failed
make[2]: *** [examples/d/CMakeFiles/x28d.dir/all] Error 2
collect2: error: ld returned 1 exit status
examples/d/CMakeFiles/x30d.dir/build.make:89: recipe for target 
'examples/d/x30d' failed
make[3]: *** [examples/d/x30d] Error 1
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
CMakeFiles/Makefile2:14427: recipe for target 
'examples/d/CMakeFiles/x30d.dir/all' failed
make[2]: *** [examples/d/CMakeFiles/x30d.dir/all] Error 2
[ 78%] Linking D executable x31d
[ 78%] Linking D executable x33d
collect2: error: ld returned 1 exit status
examples/d/CMakeFiles/x31d.dir/build.make:89: recipe for target 
'examples/d/x31d' failed
make[3]: *** [examples/d/x31d] Error 1
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
CMakeFiles/Makefile2:14465: recipe for target 
'examples/d/CMakeFiles/x31d.dir/all' failed
make[2]: *** [examples/d/CMakeFiles/x31d.dir/all] Error 2
collect2: error: ld returned 1 exit status
examples/d/CMakeFiles/x33d.dir/build.make:89: recipe for target 
'examples/d/x33d' failed
make[3]: *** [examples/d/x33d] Error 1
make[3]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
CMakeFiles/Makefile2:14503: recipe for target 
'examples/d/CMakeFiles/x33d.dir/all' failed
make[2]: *** [examples/d/CMakeFiles/x33d.dir/all] Error 2
make[2]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
Makefile:160: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/plplot-5.10.0+dfsg2/debian/build_tmp'
debian/rules:117: recipe for target 'build-arch-stamp' failed
make: *** [build-arch-stamp] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package

If I check the x29d binary which built fine outside the chroot, I only get this:

→ ldd debian/build_tmp/examples/d/x29d
linux-vdso.so.1 (0x7ffef47a2000)
libplplotd.so.12 => 
/home/abe/gnudatalanguage/plplot/debian/build_tmp/src/libplplotd.so.12 
(0x7fd6b23fc000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd6b20c3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fd6b1ea6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd6b1c9e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fd6b1a87000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd6b16de000)
libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7 
(0x7fd6b14d4000)
libshp.so.2 => /usr/lib/x86_64-linux-gnu/libshp.so.2 
(0x7fd6b12c4000)
libcsirocsa.so.0 => 
/home/abe/gnudatalanguage/plplot/debian/build_tmp/lib/csa/libcsirocsa.so.0 
(0x7fd6b10bc000)
libcsironn.so.0 => 
/home/abe/gnudatalanguage/plplot/debian/build_tmp/lib/nn/libcsironn.so.0 
(0x7fd6b0eb4000)

Bug#793791: [Pkg-anonymity-tools] Bug#793791: Bug#793791: torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes exactly 4 arguments (2 given)"

[Holger Levsen]

Hi,

On Freitag, 11. September 2015, Stéphane Glondu wrote:
> I cannot reproduce. Is this bug still on topic?
> > With any luck Debian will update some more packages and the problem
> > will just go away :)
> Maybe it happened...?

so, can anybody still reproduce in sid? I don't have such a test system…


cheers,
Holger


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

Bug#784041: [Pkg-anonymity-tools] Bug#784041: exceptions.OSError: [Errno 2] No such file or directory

[Holger Levsen]

Hi,

very quick, but probably better short now than in 4 days longer...

Tobias, thanks for spotting this!

On Dienstag, 6. Oktober 2015, u wrote:
> >> > I think it's 5f833d7 [1].

Georg too! :)

> I remember that there were quite some emails exchanged at some point
> about these two versions. Maybe Holger can explain again what prevented
> us from putting 0.2.0 into stable at the time?

the freeze... the changes were to big…
 
> And before we start fuddling around with this, we should migrate this
> package to the new pkg-privacy-maintainers list, instead of
> pkg-anonymity-tools. Aaaand i'd like to review the branch layout a bit,
> too. Maybe i can do that this week, so we can start working on this
> crippled package again ;)

well, there are two issues here: a.) how to move forward with the package, and 
b.) how to fix what's in jessie now, which just doesnt work at all.

And b.) is more urgent IMO, even though the workaround, installing from 
jessie-backports is trivial. So is 5f833d7 enough to fix 0.1.9-1+deb8u1 as 
it's in the archive?


cheers,
Holger


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

Bug#801156: dpkg: sometimes does not pass old version to postinst on upgrade

[Andreas Beckmann]

On 2015-10-07 02:23, Guillem Jover wrote:
> Hi!
> 
> On Wed, 2015-10-07 at 01:10:33 +0200, Andreas Beckmann wrote:
>> Package: dpkg
>> Version: 1.18.3
>> Severity: serious
> 
>> dpkg does not always properly pass the old version number when
>> calling "postinst configure" on package upgrades, sometimes there
>> is either no or an empty argument.
> 
> That's to be expected, the second argument is the last version that
> got configured, if no version has ever been configured then the
> argument is omitted. Checking now, this is documented in Debian
> policy §6.7.

> I've not checked the logs, but I'd assume that in the problematic case
> the package has never been configured before, and as such the bug here
> is on that specific package.

That is unlikely. Both tests start from the same chroot tarball
(debootstrapped about a month ago)

Right before packing it up the status was listed as

  ii  systemd   215-17+deb8u2amd64system and service manager

so I assume it has been configured during the debootstrap run.

If I enter that chroot with pbuilder login, the status of the systemd
package is listed as

Package: systemd
Status: install ok installed
Priority: important
Section: admin
Installed-Size: 13838
Maintainer: Debian systemd Maintainers

Architecture: amd64
Version: 215-17+deb8u2
Depends: libacl1 (>= 2.2.51-8), libaudit1 (>= 1:2.2.1), libblkid1 (>=
2.19.1), libcap2 (>= 1:2.10), libcryptsetup4 (>= 2:1.4.3), libkmod2 (>=
5~), libpam0g (>= 0.99.7.1), libselinux1 (>= 2.1.9), libsystemd0 (=
215-17+deb8u2), util-linux (>= 2.19.1-2), mount (>= 2.21), initscripts
(>= 2.88dsf-53.2), sysv-rc, udev (>= 208-8), acl, adduser, libcap2-bin
Pre-Depends: libc6 (>= 2.17), libgcrypt20 (>= 1.6.1), liblzma5 (>=
5.1.1alpha+20120614), libselinux1 (>= 1.32)
Recommends: libpam-systemd, dbus
Suggests: systemd-ui
Breaks: lsb-base (<< 4.1+Debian4), lvm2 (<< 2.02.104-1), systemd-shim
(<< 8-2)
Conflicts: klogd
Conffiles:
 /etc/dbus-1/system.d/org.freedesktop.hostname1.conf
f55c94d000b5d62b5f06d38852977dd1
 /etc/dbus-1/system.d/org.freedesktop.locale1.conf
5893ab03e7e96aa3759baceb4dd04190
 /etc/dbus-1/system.d/org.freedesktop.login1.conf
96bf488f3da8f0ca813cc78e71eeb605
 /etc/dbus-1/system.d/org.freedesktop.machine1.conf
d658acaf7192de735ab798c58ab149ae
 /etc/dbus-1/system.d/org.freedesktop.systemd1.conf
46533268285a0df22b1f1667ddc05642
 /etc/dbus-1/system.d/org.freedesktop.timedate1.conf
682369fbf3de26b21e775732c89a2bbe
 /etc/pam.d/systemd-user aebb8b8a2c698614b00961f327a683ef
 /etc/systemd/bootchart.conf 838a83315ad2f9d4c4b7f20b7475ba28
 /etc/systemd/journald.conf 51f19202dcc5aff6d2c3448dbf92f354
 /etc/systemd/logind.conf 747ae2312b6922546190bf806d8d12be
 /etc/systemd/resolved.conf 81a9c57d4eb587decc49040595674c5a
 /etc/systemd/system.conf 3d0e13a72d72acb55409a831b72a15e6
 /etc/systemd/timesyncd.conf 605e4f25097b8ea22f2f5cb3fde3f13c
 /etc/systemd/user.conf 9eaad8fbb7bb6230d4b28abb76b4e81c
Description: system and service manager
 systemd is a replacement for sysvinit.  It is dependency-based and


>> I have two cases where an 'apt-get dist-upgrade' from jessie to
>> stretch calls 'systemd.postinst configure' differently:
>> * a minimal jessie chroot (incorrect behavior)
>> * a minimal jessie chroot + bash-completion (correct behavior)

and starting from that chroot.tgz I can reproduce the two upgrade paths
with the differing behavior manually:

  apt-get install bash-completion  # only for the "correct" one
  sed -i s/jessie/stretch/ /etc/apt/sources.list
  apt-get update
  apt-get dist-upgrade


If the postinst is invoked correctly the configuration of systemd ends
with the removal of an obsolete conffile:

...
Unpacking systemd (226-3) over (215-17+deb8u2) ...
Setting up util-linux (2.27-3) ...
Setting up systemd (226-3) ...
...
Removing obsolete conffile
/etc/dbus-1/system.d/org.freedesktop.machine1.conf ...
...

If the postinst is incorrectly invoked like it were an initial install,
the obsolete conffile removal is missing.


if I start with

  apt-get install bash-completion
  apt-get purge bash-completion

I also get into the incorrect behavior.



You can find the chroot at people.debian.org: ~anbe/jessie_amd64.tar.gz
You may have to nuke the proxy setting in /etc/apt/apt.conf.d/piuparts
to test this yourself.



Andreas

Bug#451535: Bump

[Quentin]

Bump. This is a most annoying bug and it's been around for way too long.

Colin Watson suggested around 2011/09/09 that he had a workable fix.
Is it still true? Why wasn't it committed in the end? How can we move 
forward with this?


Cheers,
Quentin

Bug#801156: dpkg: sometimes does not pass old version to postinst on upgrade

[Andreas Beckmann]

The chroot was bootstrapped with

'debootstrap' '--variant=minbase' 
'--keyring=/usr/share/keyrings/debian-archive-keyring.gpg' '--components=main' 
'--arch=amd64' 'jessie' '/tmp/piupartss/tmpcNOJI3' 
'http://ftp.de.debian.org/debian'

and was slightly configured by piuparts to have e.g.

# cat /etc/apt/apt.conf.d/piuparts 
APT::Get::Assume-Yes "yes";
APT::Install-Recommends "0";
APT::Install-Suggests "0";
APT::Get::AllowUnauthenticated "No";
Acquire::PDiffs "false";
Acquire::http::Proxy "http://localhost:3128;;
Dpkg::Options {"--force-unsafe-io";};


Andreas

Bug#800794: marked as done (python-pysam: FTBFS on multiple archs due to cython error)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 09:37:41 +
with message-id 
and subject line Bug#800794: fixed in python-pysam 0.8.3+ds1-3
has caused the Debian Bug report #800794,
regarding python-pysam: FTBFS on multiple archs due to cython error
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.)


-- 
800794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pysam
Version: 0.8.3+ds1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

While rebuilding the package for the transition that adds python3.5 as a
supported python3 version it FTBFS on muliple archs.  Here's an example
log excerpt from ppc64el:

pysam/cbcf.c: At top level:
pysam/cbcf.c:47536:67: error: unknown type name ‘htsFormatCategory’
 static CYTHON_INLINE PyObject* 
__Pyx_PyInt_From_htsFormatCategory(htsFormatCategory value) {
   ^
pysam/cbcf.c:47562:64: error: unknown type name ‘htsExactFormat’
 static CYTHON_INLINE PyObject* __Pyx_PyInt_From_htsExactFormat(htsExactFormat 
value) {
^
pysam/cbcf.c:47614:64: error: unknown type name ‘htsCompression’
 static CYTHON_INLINE PyObject* __Pyx_PyInt_From_htsCompression(htsCompression 
value) {
^
error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:262: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:17: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25

It seems unrelated to python3.5.

Scott K
--- End Message ---
--- Begin Message ---
Source: python-pysam
Source-Version: 0.8.3+ds1-3

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

Debian distribution maintenance software
pp.
Afif Elghraoui  (supplier of updated python-pysam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Oct 2015 00:57:19 -0700
Source: python-pysam
Binary: python-pysam python3-pysam python-pysam-tests
Architecture: source all amd64
Version: 0.8.3+ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Afif Elghraoui 
Description:
 python-pysam - interface for the SAM/BAM sequence alignment and mapping format 
(
 python-pysam-tests - interface for the SAM/BAM sequence alignment and mapping 
format (
 python3-pysam - interface for the SAM/BAM sequence alignment and mapping 
format (
Closes: 800794
Changes:
 python-pysam (0.8.3+ds1-3) unstable; urgency=medium
 .
   * Backport upstream commit 6efb22b to permit building with Cython 0.23.x
 (Closes: 800794)
   * Revise lintian overrides.
Checksums-Sha1:
 5a55903a689d2b9a081fee5b034e175d74adc4bf 2387 python-pysam_0.8.3+ds1-3.dsc
 d5f24c716ed6bdb37f1c29b57dfd79c642077936 10448 
python-pysam_0.8.3+ds1-3.debian.tar.xz
 3285120839fd7e448c3f75f85db4f318c0b2f9f0 772396 
python-pysam-tests_0.8.3+ds1-3_all.deb
 58093637a54dc0ec8a4d35675110166f7e60a778 741132 
python-pysam_0.8.3+ds1-3_amd64.deb
 dc64005b40449f781f91956fefb100b6733cfa39 1099826 
python3-pysam_0.8.3+ds1-3_amd64.deb
Checksums-Sha256:
 8814798f6c792251e205a17cb325913f7285f6c8033b65b4e857886cec15 2387 
python-pysam_0.8.3+ds1-3.dsc
 67da700b7d4f9b7377c222bfecf8b58caa11c750c144cc250036c6ff63e4b709 10448 
python-pysam_0.8.3+ds1-3.debian.tar.xz
 08f1b2603ddfad9bcfc0839e4a360a3cef236a8b3bf4f4807ba445ea19ef41f3 772396 
python-pysam-tests_0.8.3+ds1-3_all.deb
 5d6f850a9f5311c4db431838377c061e153d169a8977519185e17a77c5495d0c 741132 
python-pysam_0.8.3+ds1-3_amd64.deb
 5b5f240ed372cd3f9314d38aaeab05f8bacf72b83e79a61e4ef3f57ff489dca4 1099826 
python3-pysam_0.8.3+ds1-3_amd64.deb
Files:
 

Bug#795178: fixed in ceph 0.94.3-1

[Gaudenz Steinlin]

Emilio Pozuelo Monfort  writes:

> [ explicit Cc's as this goes to a list that seems to be moderated... ]
>
> On Sat, 26 Sep 2015 16:39:46 +0200 Emilio Pozuelo Monfort  
> wrote:
>> Can we have this fixed in unstable as well? ceph currently fails to build 
>> there
>> and this is blocking various transitions.
>
> This is blocking the boost, icu, libleveldb and libsnappy transitions. I'll 
> try
> to look at NMU'ing this if you don't have the time.
>
> FWIW the version in experimental failed to build on armel, so just uploading
> that to sid wouldn't be the best solution... I'd prefer a targeted fix first 
> so
> we can finish those transitions.

I would prefer that too, but I don't have the capacity to port ceph
0.80.x to libboost1.58. Unless someone can provide a patch I'd go with
just uploading what we have in experimental to unstable.

I meant to do some more things before uploading to unstable (like using
the new UIDs for the daemons and proper systemd support), but as it's
blocking other transitions it's better to just upload to unstable soon.

I'm not sure how to best solve the build failure on armel. Jerasure does
runtime detection of ARM features, so NEON should be enabled for
machines that support it. The error suggests that the -mfloat-abi=softfp
compiler option needs to be set. But I'm not sure if this is the right
thing to do on armel. Some help is needed here.

Gaudenz

Bug#798049: scantailor FTBFS in current Sid

[Daniel Stender]

[Note: CCing to the AM because "tasks & skills" process of the DD application 
is going on]

In the meanwhile I've got deeper into the current Scantailor problem ...

It appears there is problem with Qt4 in combination with libboost [1,2]:


[30%] Built target interaction
make -f zones/CMakeFiles/zones.dir/build.make zones/CMakeFiles/zones.dir/depend
make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
[ 30%] Generating ZoneContextMenuInteraction.h.moc
cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/zones && 
/usr/lib/x86_64-linux-gnu/qt4/bin/moc 
@/«PKGBUILDDIR»/obj-x86_64-linux-gnu/zones/ZoneContextMenuInteraction.h.moc_parameters
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at 
"BOOST_JOIN"
make[3]: *** [zones/ZoneContextMenuInteraction.h.moc] Error 1
zones/CMakeFiles/zones.dir/build.make:70: recipe for target 
'zones/ZoneContextMenuInteraction.h.moc' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
make[2]: *** [zones/CMakeFiles/zones.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
CMakeFiles/Makefile2:809: recipe for target 'zones/CMakeFiles/zones.dir/all' 
failed


qsapecng had the same problem recently leading to FTBFS in the Reproducible 
Builds CI [3], patching
some relevant includes with a workaround [4]. I'm going to follow that model.

DS

[1] 
http://stackoverflow.com/questions/15455178/qt4-cgal-parse-error-at-boost-join

[2] https://bugreports.qt.io/browse/QTBUG-22829

[3] https://bugs.debian.org/78
qsapecng: FTBFS: Parse error at "BOOST_JOIN" 
src/CMakeFiles/qsapecng.dir/build.make

[4] 
https://sources.debian.net/src/qsapecng/2.0.0-8/debian/patches/boost_join_fix.patch

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

Processed: scantailor FTBFS in current Sid

[Debian Bug Tracking System]

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

> forwarded 798049 https://github.com/scantailor/scantailor/issues/165
Bug #798049 [scantailor] scantailor FTBFS in current Sid
Set Bug forwarded-to-address to 
'https://github.com/scantailor/scantailor/issues/165'.
> thanks
Stopping processing here.

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

Processed: scantailor FTBFS in current Sid

[Debian Bug Tracking System]

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

> tags 798049 - help
Bug #798049 [scantailor] scantailor FTBFS in current Sid
Removed tag(s) help.
> thanks
Stopping processing here.

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

Processed: bug 789619 is forwarded to http://sourceforge.net/p/plplot/bugs/164/

[Debian Bug Tracking System]

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

> # at least the octave part of this bug report
> forwarded 789619 http://sourceforge.net/p/plplot/bugs/164/
Bug #789619 [src:plplot] plplot: FTBFS: CMake Error at 
cmake/modules/pkg-config.cmake:97 (_pkg_check_modules_internal): 
_pkg_check_modules_internal Macro invoked with incorrect arguments
Set Bug forwarded-to-address to 'http://sourceforge.net/p/plplot/bugs/164/'.
> thanks
Stopping processing here.

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

Bug#801156: dpkg: sometimes does not pass old version to postinst on upgrade

[Andreas Beckmann]

Package: dpkg
Version: 1.18.3
Severity: serious

Hi Guillem,

dpkg does not always properly pass the old version number when
calling "postinst configure" on package upgrades, sometimes there
is either no or an empty argument.

I have two cases where an 'apt-get dist-upgrade' from jessie to
stretch calls 'systemd.postinst configure' differently:
* a minimal jessie chroot (incorrect behavior)
* a minimal jessie chroot + bash-completion (correct behavior)

I noticed this while analyzing some strange piuparts failures in jessie
to stretch upgrades. Unfortunately I neglected it for a long time since
I assumed to have hit a strange bug in some systemd support scripts:

1m41.2s ERROR: FAIL: After purging files have disappeared:
  /etc/dbus-1/system.d/org.freedesktop.machine1.conf.dpkg-remove not 
owned
  /etc/systemd/system/halt.target.wants/ not owned
  /etc/systemd/system/halt.target.wants/hwclock-save.service -> 
/lib/systemd/system/hwclock-save.service not owned
  /etc/systemd/system/poweroff.target.wants/ not owned
  /etc/systemd/system/poweroff.target.wants/hwclock-save.service -> 
/lib/systemd/system/hwclock-save.service not owned
  /etc/systemd/system/reboot.target.wants/   not owned
  /etc/systemd/system/reboot.target.wants/hwclock-save.service -> 
/lib/systemd/system/hwclock-save.service   not owned

Digging into this I found the systemd.postinst from stretch performing
cleanup of hwclock-save.service and removal of that obsolete conffile
- but strangely only sometimes:


# Cleanup hwclock-save.service, which was shipped in jessie.
if dpkg --compare-versions "$2" lt-nl "219-8"; then
   for t in reboot halt poweroff ; do
   rm -fv /etc/systemd/system/${t}.target.wants/hwclock-save.service
   rmdir --ignore-fail-on-non-empty /etc/systemd/system/${t}.target.wants 
2> /dev/null || true
   done
fi

#DEBHELPER#

(the #DEBHELPER# part gets several dkpm-maintscript-helper rm_conffile calls)


not here, which is wrong:


(Reading database ... 7446 files and directories currently installed.)
  Preparing to unpack .../systemd_226-3_amd64.deb ...
  Unpacking systemd (226-3) over (215-17+deb8u2) ...
  Setting up util-linux (2.27-3) ...
  Setting up systemd (226-3) ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.login1.conf ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.systemd1.conf ...
  Installing new version of config file /etc/pam.d/systemd-user ...
  Installing new version of config file /etc/systemd/bootchart.conf ...
  Installing new version of config file /etc/systemd/journald.conf ...
  Installing new version of config file /etc/systemd/logind.conf ...
  Installing new version of config file /etc/systemd/resolved.conf ...
  Installing new version of config file /etc/systemd/system.conf ...
  Installing new version of config file /etc/systemd/timesyncd.conf ...
  Installing new version of config file /etc/systemd/user.conf ...
  Created symlink from 
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service to 
/lib/systemd/system/systemd-timesyncd.service.
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  (Reading database ... 


but here, which is correct:


(Reading database ... 8034 files and directories currently installed.)
  Preparing to unpack .../systemd_226-3_amd64.deb ...
  Unpacking systemd (226-3) over (215-17+deb8u2) ...
  Setting up util-linux (2.27-3) ...
  Setting up systemd (226-3) ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.login1.conf ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.systemd1.conf ...
  Installing new version of config file /etc/pam.d/systemd-user ...
  Installing new version of config file /etc/systemd/bootchart.conf ...
  Installing new version of config file /etc/systemd/journald.conf ...
  Installing new version of config file /etc/systemd/logind.conf ...
  Installing new version of config file /etc/systemd/resolved.conf ...
  Installing new version of config file /etc/systemd/system.conf ...
  Installing new version of config file /etc/systemd/timesyncd.conf ...
  Installing new version of config file /etc/systemd/user.conf ...
  Created symlink from 
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service to 
/lib/systemd/system/systemd-timesyncd.service.
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 
...
  (Reading database ... 



So I rebuilt systemd with more debug output in the postinst script to see the 
following:


  (Reading database ... 7446 files and directories currently installed.)
  Preparing to unpack ..././systemd_226-4.1_amd64.deb ...
  Unpacking systemd (226-4.1) over (215-17+deb8u2) ...
  Setting up util-linux (2.27-3) ...
  Setting up systemd (226-4.1) ...
  

Bug#800629: [Pkg-kde-extras] Bug#800629: telepathy-qt FTBFS: fatal error: gst/gstconfig.h: No such file or directory

[Diane Trout]

On Tuesday, October 06, 2015 11:07:33 Alexandr Akulich wrote:
> Hello.
> 
> Probably this patch would help:
> http://cgit.freedesktop.org/telepathy/telepathy-qt/commit/?id=ec4a3d62b68a57
> 254515f01fc5ea3325ffb1dbfb
> 

Yes that patch did help.

I just pushed telepathy-qt -3 which includes it.

Diane

Bug#801101: manila-scheduler: fails to install, trying to overwrite other packages files: /usr/bin/manila-scheduler

[Andreas Beckmann]

Package: manila-scheduler
Version: 1.0.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package manila-scheduler.
  (Reading database ... 
(Reading database ... 15123 files and directories currently installed.)
  Preparing to unpack .../manila-scheduler_1.0.0~rc1-1_all.deb ...
  Unpacking manila-scheduler (1.0.0~rc1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manila-scheduler_1.0.0~rc1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/manila-scheduler', which is also in package 
manila-common 1.0.0~rc1-1
  Processing triggers for systemd (226-4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/manila-scheduler_1.0.0~rc1-1_all.deb


cheers,

Andreas


manila-scheduler_1.0.0~rc1-1.log.gz
Description: application/gzip

Processed: Re: Bug#800796: gnome-calendar: fails to start every time, "Error building template class" and segfault

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #800796 [gnome-calendar] gnome-calendar: fails to start every time, "Error 
building template class" and segfault
Severity set to 'grave' from 'important'

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

Bug#795178: fixed in ceph 0.94.3-1

[Emilio Pozuelo Monfort]

On 06/10/15 11:59, Gaudenz Steinlin wrote:
> Emilio Pozuelo Monfort  writes:
> 
>> [ explicit Cc's as this goes to a list that seems to be moderated... ]
>>
>> On Sat, 26 Sep 2015 16:39:46 +0200 Emilio Pozuelo Monfort  
>> wrote:
>>> Can we have this fixed in unstable as well? ceph currently fails to build 
>>> there
>>> and this is blocking various transitions.
>>
>> This is blocking the boost, icu, libleveldb and libsnappy transitions. I'll 
>> try
>> to look at NMU'ing this if you don't have the time.
>>
>> FWIW the version in experimental failed to build on armel, so just uploading
>> that to sid wouldn't be the best solution... I'd prefer a targeted fix first 
>> so
>> we can finish those transitions.
> 
> I would prefer that too, but I don't have the capacity to port ceph
> 0.80.x to libboost1.58. Unless someone can provide a patch I'd go with
> just uploading what we have in experimental to unstable.

There's a patch in this bug log, see

https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=ceph_0.94.2-2.1.debdiff;bug=795178;att=1

Is that not good enough?

> I meant to do some more things before uploading to unstable (like using
> the new UIDs for the daemons and proper systemd support), but as it's
> blocking other transitions it's better to just upload to unstable soon.
> 
> I'm not sure how to best solve the build failure on armel. Jerasure does
> runtime detection of ARM features, so NEON should be enabled for
> machines that support it. The error suggests that the -mfloat-abi=softfp
> compiler option needs to be set. But I'm not sure if this is the right
> thing to do on armel. Some help is needed here.

You can ask on the debian-...@lists.debian.org list.

Cheers,
Emilio

Bug#801106: sddm-greeter fails to start

[Andy Wood]

Package: sddm
Version: 0.12.0-4
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

Reboot after installing nvidia 340.93-3 (latest testing version).
I had tried stopping sddm; rmmod nvidia; and restarting again ... got the 
sddm-greeter would
not start error and hoped a reboot would fix.

The only way I could get a working plasma5 was to install and use 
lightdm/lightdm-kde-greeter.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sddm depends on:
ii  adduser   3.113+nmu3
ii  debconf [debconf-2.0] 1.5.57
ii  libc6 2.19-22
ii  libgcc1   1:5.2.1-17
ii  libpam0g  1.1.8-3.1
ii  libqt5core5a  5.4.2+dfsg-9
ii  libqt5dbus5   5.4.2+dfsg-9
ii  libqt5gui55.4.2+dfsg-9
ii  libqt5network55.4.2+dfsg-9
ii  libqt5qml55.4.2-6
ii  libqt5quick5  5.4.2-6
ii  libstdc++65.2.1-17
ii  libsystemd0   226-3
ii  libxcb-xkb1   1.10-3+b1
ii  libxcb1   1.10-3+b1
ii  qml-module-qtquick2   5.4.2-6
ii  sddm-theme-breeze [sddm-theme]4:5.4.1-1
ii  sddm-theme-circles [sddm-theme]   0.12.0-4
ii  sddm-theme-elarun [sddm-theme]0.12.0-4
ii  sddm-theme-maldives [sddm-theme]  0.12.0-4
ii  sddm-theme-maui [sddm-theme]  0.12.0-4

sddm recommends no packages.

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.4.1-1

-- debconf information excluded

Bug#801060: Fwd: Re: Bug#798256: transition: hdf5

[Gilles Filippini]

CCing #801060 for the record.

 Courriel original 
Objet: Re: Bug#798256: transition: hdf5
Date: 2015-10-06 12:59
De: Gilles Filippini 
À: Emilio Pozuelo Monfort 
Cc: 798...@bugs.debian.org, Emilio Pozuelo Monfort 

Le 2015-10-06 11:07, Emilio Pozuelo Monfort a écrit :

On 05/10/15 23:02, Gilles Filippini wrote:

Please tell me in case of anything left blocking the transition.


There's #801060.


This one is really annoying. Scilab could build on ppc64el, but it would 
be unusable anyway because of #798652, blocked by #779482.
Then I'm in favor of removing scilab from ppc64el rather than providing 
a useless fix. What do you think?


Thanks,

_g.

Bug#783169: google-drive-ocamlfuse

[Pietro Battiston]

I just want to signal that google-drive-ocamlfuse seems to work
reliably, has a Ubuntu package (which I'm using under Debian) and is
quite comfortable to use - just mounts the drive in the desired
position:
http://gdfuse.forge.ocamlcore.org/

Pietro

Bug#784859: Workaround considered annoying at best

[David Prévot]

Control: clone -1 -2
Control: retitle -2 Unsuitable for stable without proper maintenance
Control: block -2 by 766449

Hi,

On Fri, Sep 18, 2015 at 01:08:53PM +0200, Andreas Beckmann wrote:
> On 2015-09-18 11:36, "David Prévot" wrote:

> At least this "workaround" seems to have worked in the past.

Again, as previously pointed on this bug report, an upgrade to a newer
upstream version of its dependency (e.g., for security reason) in stable
will make this package uninstallable for no good reason.

> I don't mind doing rebuild-only QA uploads (since arch:all cannot be
> binNMUed), but I don't care about (or even use) ampache at all.

Then please don’t: keeping an outdated and unmaintained version of some
PHP scripts without anyone caring if it actually works or is secure is
not a service to our users.

> Please retitle the bug according to your wishes, right now it just calls
> for a rebuild.

It definitely doesn’t and there is more than a title in a bug report.
Anyway, cloning to expose the other problem pointed in this bug report.

Regards

David


signature.asc
Description: PGP signature

Bug#799948: Fwd: Re: Bug#801106: sddm-greeter fails to start

[Diederik de Haas]

On Tuesday 06 October 2015 11:54:15 Andy Wood wrote:
> Package: sddm
> ...
> Reboot after installing nvidia 340.93-3 (latest testing version).

See https://bugs.debian.org/799948

(workaround "adduser sddm video")


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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 800487 + pending
Bug #800487 [retext] retext crashes with a SIGSEGV
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#799948: glx-alternatives_0.6.1_source.changes ACCEPTED into unstable

[Diederik de Haas]

On Tuesday 06 October 2015 11:13:10 Andreas Beckmann wrote:
> On 2015-10-06 01:12, Diederik de Haas wrote:
> > How about bug nrs #800051, 800327, 800550 and 800705?
> > They looked like the same issue to me and most confirmed that adding the
> > DM user to the video group fixed it (some haven't responded yet).
> 
> Having a workaround is nice but we are missing understanding why this
> happens depending on the way X is configured for nvidia.

True, and I understand the temporary reversal as a workaround.

What I actually meant was: shouldn't those bugs be merged and/or marked as 
affecting package X/Y/Z? Because it looks like quite a number of bugs are 
being filed for what looks to be the same reason. 
Another one was filed just over an hour ago: 801106

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

Bug#796371: blockdiag: FTBFS: unknown format: SVG

[Piotr Ożarowski]

[Julien Cristau, 2015-10-06]
> As far as I can tell, this is caused by a change in pybuild: instead of
> running something like "python setup.py test" from the toplevel source
> directory (which works), it runs "python2.7 -m nose" from
> .pybuild/pythonX.Y_2.7/build.  The latter directory is missing
> blockdiag.egg-info, which means pkg_resources doesn't find any entry
> points.  I'm tempted to reassign this to dh-python.

I will definitely not go back to running tests from package root
directory (due to . in sys.path or 2to3 issues).

I might consider copying egg-info dir to the build dir, though.

What I suggest to do right now is adding this line to debian/rules:

export PYBUILD_BEFORE_TEST=cp -r foo.egg-info {build_dir}


and about `setup.py test` vs. `pythonX.Y -m nose` - I'd love to have a
standard API for running tests, but that's something you need to talk
with Python upstream
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Bug#801106: sddm-greeter fails to start

[Diederik de Haas]

On Tuesday 06 October 2015 11:54:15 Andy Wood wrote:
> Package: sddm
> ...
> Reboot after installing nvidia 340.93-3 (latest testing version).

See https://bugs.debian.org/799948

(workaround "adduser sddm video")


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

Bug#801112: python-biopython: FTBFS due to test failure with multiple python3 versions supported

[Scott Kitterman]

Source: python-biopython
Version: 1.65+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The package FTBFS with the following error during the binNMU to add python3.5
support:

==
ERROR: test_DocSQL (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_DocSQL
Traceback (most recent call last):
  File 
"/«BUILDDIR»/python-biopython-1.65+dfsg/.pybuild/pythonX.Y_3.5/build/Bio/DocSQL.py",
 line 33, in 
import MySQLdb
ImportError: No module named 'MySQLdb'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File 
"/«BUILDDIR»/python-biopython-1.65+dfsg/.pybuild/pythonX.Y_3.5/build/Tests/test_DocSQL.py",
 line 7, in 
import Bio.DocSQL
  File 
"/«BUILDDIR»/python-biopython-1.65+dfsg/.pybuild/pythonX.Y_3.5/build/Bio/DocSQL.py",
 line 35, in 
raise MissingPythonDependencyError("Install MySQLdb if you want to use "
Bio.MissingPythonDependencyError: Install MySQLdb if you want to use Bio.DocSQL.

I did verify that python-mysqldb is built with support for python3.5, so the
issue appears to be in this package.

Scott K

Processed: Not just ppc64

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #799694 [src:healpy] healpy: FTBFS on ppc64(el): No module named _tkinter
Severity set to 'serious' from 'important'

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

Bug#800487: marked as done (retext crashes with a SIGSEGV)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 11:48:50 +
with message-id 
and subject line Bug#800487: fixed in retext 5.2.1-1
has caused the Debian Bug report #800487,
regarding retext crashes with a SIGSEGV
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.)


-- 
800487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: retext
Version: 5.2.0-1
Severity: grave
Justification: renders package unusable

retext worked yesterday. Today it crashes. Attached is an strace output
file.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.1.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages retext depends on:
ii  python3-docutils0.12+dfsg-1
ii  python3-enchant 1.6.6-2
ii  python3-markdown2.6.2-1
ii  python3-markups 0.6.3-1
ii  python3-pygments2.0.1+dfsg-1.1
ii  python3-pyqt5   5.4.2+dfsg-1+b2
ii  python3-pyqt5.qtwebkit  5.4.2+dfsg-1+b2
pn  python3:any 

Versions of packages retext recommends:
ii  docutils-common   0.12+dfsg-1
ii  shared-mime-info  1.5-2

retext suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: retext
Source-Version: 5.2.1-1

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated retext package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Oct 2015 14:34:24 +0300
Source: retext
Binary: retext
Architecture: source
Version: 5.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Shachnev 
Changed-By: Dmitry Shachnev 
Description:
 retext - Simple text editor for Markdown and reStructuredText
Closes: 800487
Changes:
 retext (5.2.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes crash in xsettings code on 32-bit systems (closes: #800487).
Checksums-Sha1:
 8092860a920a20202fe14d3da79ec139f06c3194 2006 retext_5.2.1-1.dsc
 dbf8ab5de0be5355b5ddcb3ca2cdf6f605ab51ce 157119 retext_5.2.1.orig.tar.gz
 84a39b2e41ef3de1434fef5a7bff535b412e422d 12404 retext_5.2.1-1.debian.tar.xz
Checksums-Sha256:
 8d4007d4e8c8205fe27bf3dab9adb46f252a7828c6dc6195cb3a86612bdd2b91 2006 
retext_5.2.1-1.dsc
 02164ae2bba6f47a2ec5e11aa06aefbcd96bea1b84a96c5673dbe18d8ccb2a69 157119 
retext_5.2.1.orig.tar.gz
 dd792791a1a4a21bba585c8f190f22d08abf5a256d6733d46ee798425c63afad 12404 
retext_5.2.1-1.debian.tar.xz
Files:
 6c1c5cf0f250e7d8cf72e7109ed0230a 2006 editors optional retext_5.2.1-1.dsc
 4dfa51ec8a1d86ef02578d1cb3dc6750 157119 editors optional 
retext_5.2.1.orig.tar.gz
 231c8583354fd48f7b398682fb37e26d 12404 editors optional 
retext_5.2.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWE7JTAAoJENb+cQNj+F3T+cAP+wf+QOgKHCP1Gprb5Hj/BnRR
augfMRcpVNvKKhUFgw4WCWFd+oUo1p3r3ixyoIVgMYoGwwVNzWBl1yWsr3nfCVMj
Ei5LM5qA1KsPU9iLIP43Yaz8D4fpvNq8tZ7JL8ROpT1uuAqOyXpjVJj3yNMj0Yze
HXviOuKevEconkWwawPECNtPdLBu1KxcCUpdnH/aImAz2HSvAUo1/1SnwDtgFrnP
rJNMh5KghzrJ9QTHrVbv6Pd/3KJCVkJrIRlRIrl612rMpjfH59fXYQzM1k4wlbXM
EQjQ+SXRP4O2TAOoezYC9PpaUYMyA2EehoulOfK4UT6VDoSUtFcRj+gcqGfhJxfs
J0n2V4QndKLp+MEcshxFFQoV2a8+pTy+WxobRMc29lEzGN7rme+8nl8BB8JzEY6B
bXzlj3Qg6SmmX6PntaHThg8wDM3mBpj3QEADl+CZ7V/0g1SV7dRvlbWiekD5eDCB
SU2zStEoGgkRZJ4pQW4FNe6x3z0sMyKiq1oy/eW0LOk5scD9ldIvQCR6izPlaJ2C
FEbzg2VtjDESV1sFJ+O1Y1gUFz8/Yo8KkUWua5t5mMIsCc8IMcUa0CGkANwoAfLr
LVrFYvCPJmyLqMCqgOt6a161TQl8574onq225vsaPYDE69SkMFmyNC9Uqo7u4dS5
/VbsfoQOLLQL6hyT3hKx
=z9QX
-END PGP SIGNATURE End Message ---

Processed: astropy is not compatible to 1.0.5 yet

[Debian Bug Tracking System]

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

> reassign 800727 python3-astropy 1.0.4-1
Bug #800727 [src:python-cpl] python-cpl: FTBFS: ImportError: cannot import name 
'_compiler'
Bug reassigned from package 'src:python-cpl' to 'python3-astropy'.
No longer marked as found in versions python-cpl/0.7-4.
Ignoring request to alter fixed versions of bug #800727 to the same values 
previously set
Bug #800727 [python3-astropy] python-cpl: FTBFS: ImportError: cannot import 
name '_compiler'
Marked as found in versions python-astropy/1.0.4-1.
> affects 800727 python-cpl
Bug #800727 [python3-astropy] python-cpl: FTBFS: ImportError: cannot import 
name '_compiler'
Added indication that 800727 affects python-cpl
> retitle 800727 python3-astropy: Incompatible to Python-3.5
Bug #800727 [python3-astropy] python-cpl: FTBFS: ImportError: cannot import 
name '_compiler'
Changed Bug title to 'python3-astropy: Incompatible to Python-3.5' from 
'python-cpl: FTBFS: ImportError: cannot import name '_compiler''
> thanks
Stopping processing here.

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

Bug#801114: jakarta-jmeter: FTBFS in sid with cannot find symbol error

[Markus Koschany]

Package: src:jakarta-jmeter
Version: 2.11-3
Severity: serious

I just wanted to investigate the libcommons-net1-java dependency but
the package FTBFS in sid.

 [javac]
 
/build/jakarta-jmeter-2.11/src/components/org/apache/jmeter/assertions/SMIMEAssertion.java:150:
 error: cannot find symbol
 [javac] CertStore certs =
 s.getCertificatesAndCRLs("Collection", "BC"); // $NON-NLS-1$  //

Full build log is attached.

Markus


jakarta-jmeter_2.11-3_amd64.build.gz
Description: application/gzip

Bug#801114: marked as done (jakarta-jmeter: FTBFS in sid with cannot find symbol error)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 14:45:43 +0200
with message-id <5613c277.30...@gambaru.de>
and subject line Re: Bug#801114: jakarta-jmeter: FTBFS in sid with cannot find 
symbol error
has caused the Debian Bug report #801114,
regarding jakarta-jmeter: FTBFS in sid with cannot find symbol error
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.)


-- 
801114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jakarta-jmeter
Version: 2.11-3
Severity: serious

I just wanted to investigate the libcommons-net1-java dependency but
the package FTBFS in sid.

 [javac]
 
/build/jakarta-jmeter-2.11/src/components/org/apache/jmeter/assertions/SMIMEAssertion.java:150:
 error: cannot find symbol
 [javac] CertStore certs =
 s.getCertificatesAndCRLs("Collection", "BC"); // $NON-NLS-1$  //

Full build log is attached.

Markus


jakarta-jmeter_2.11-3_amd64.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Am 06.10.2015 um 14:39 schrieb Markus Koschany:
> Package: src:jakarta-jmeter
> Version: 2.11-3
> Severity: serious
> 
> I just wanted to investigate the libcommons-net1-java dependency but
> the package FTBFS in sid.

Sorry, my bad. A newer version of bouncycastle libraries was installed
on my system and they are obviously incompatible. The package works as
intended.

Closing.




signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: Bug#784859: Workaround considered annoying at best

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #784859 [ampache-common] Uninstallable in Sid: too strict version 
constraints
Bug 784859 cloned as bug 801116
> retitle -2 Unsuitable for stable without proper maintenance
Bug #801116 [ampache-common] Uninstallable in Sid: too strict version 
constraints
Changed Bug title to 'Unsuitable for stable without proper maintenance' from 
'Uninstallable in Sid: too strict version constraints'
> block -2 by 766449
Bug #801116 [ampache-common] Unsuitable for stable without proper maintenance
801116 was not blocked by any bugs.
801116 was not blocking any bugs.
Added blocking bug(s) of 801116: 766449

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

Bug#801112: marked as done (python-biopython: FTBFS due to test failure with multiple python3 versions supported)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 16:20:37 +
with message-id 
and subject line Bug#801112: fixed in python-biopython 1.65+dfsg-3
has caused the Debian Bug report #801112,
regarding python-biopython: FTBFS due to test failure with multiple python3 
versions supported
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.)


-- 
801112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biopython
Version: 1.65+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The package FTBFS with the following error during the binNMU to add python3.5
support:

==
ERROR: test_DocSQL (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_DocSQL
Traceback (most recent call last):
  File 
"/«BUILDDIR»/python-biopython-1.65+dfsg/.pybuild/pythonX.Y_3.5/build/Bio/DocSQL.py",
 line 33, in 
import MySQLdb
ImportError: No module named 'MySQLdb'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File 
"/«BUILDDIR»/python-biopython-1.65+dfsg/.pybuild/pythonX.Y_3.5/build/Tests/test_DocSQL.py",
 line 7, in 
import Bio.DocSQL
  File 
"/«BUILDDIR»/python-biopython-1.65+dfsg/.pybuild/pythonX.Y_3.5/build/Bio/DocSQL.py",
 line 35, in 
raise MissingPythonDependencyError("Install MySQLdb if you want to use "
Bio.MissingPythonDependencyError: Install MySQLdb if you want to use Bio.DocSQL.

I did verify that python-mysqldb is built with support for python3.5, so the
issue appears to be in this package.

Scott K
--- End Message ---
--- Begin Message ---
Source: python-biopython
Source-Version: 1.65+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-biopython package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Oct 2015 16:53:06 +0200
Source: python-biopython
Binary: python-biopython python3-biopython python-biopython-doc 
python-biopython-sql python3-biopython-sql
Architecture: source all amd64
Version: 1.65+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-biopython - Python library for bioinformatics (implemented in Python 2)
 python-biopython-doc - Documentation for the Biopython library
 python-biopython-sql - Biopython support for the BioSQL database schema 
(Python 2)
 python3-biopython - Python library for bioinformatics (implemented in Python 3)
 python3-biopython-sql - Biopython support for the BioSQL database schema 
(Python 3)
Closes: 801112
Changes:
 python-biopython (1.65+dfsg-3) unstable; urgency=medium
 .
   * Also run Tutorial test
   * Prefer Github as contact point
   * Build-Depends: python3-mysqldb
 Closes: #801112
Checksums-Sha1:
 dbf87c52af83271b69d8cf79cd9a2de07612d6b4 2916 python-biopython_1.65+dfsg-3.dsc
 ece3257b9c6e3eb7c5e0d138882576206d29de6d 13904 
python-biopython_1.65+dfsg-3.debian.tar.xz
 75f109fac9086e9225bd1cd3a42004a6e9754f03 10718410 
python-biopython-doc_1.65+dfsg-3_all.deb
 02e214470335d5d267cf2b5e700783eec10b4590 28212 
python-biopython-sql_1.65+dfsg-3_all.deb
 b371e6594668f2459835e915ed300fb21d5bbeaa 1182576 
python-biopython_1.65+dfsg-3_amd64.deb
 d2d6088abcd15be055cb335cb1e616efaa07ef73 28270 
python3-biopython-sql_1.65+dfsg-3_all.deb
 40d02161ce8495f3c6c6e8c4db139521060d2edd 1149886 
python3-biopython_1.65+dfsg-3_amd64.deb
Checksums-Sha256:
 27fe0117abd28f242dfae01c4d0b34e0c03a3e2dca855ce88b12bd030a5ac26c 2916 
python-biopython_1.65+dfsg-3.dsc

Bug#798820: marked as done (oar-restful-api: package in main depends on libapache2-mod-fastcgi which is in non-free)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 16:00:50 +
with message-id 
and subject line Bug#798820: fixed in oar 2.5.5-2
has caused the Debian Bug report #798820,
regarding oar-restful-api: package in main depends on libapache2-mod-fastcgi 
which is in non-free
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.)


-- 
798820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: oar-restful-api
Version: 2.5.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

oar-restful-api is not installable in sid/main since it depends on a
package outside main. This is a violation of policy 2.2.1.


Andreas
--- End Message ---
--- Begin Message ---
Source: oar
Source-Version: 2.5.5-2

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

Debian distribution maintenance software
pp.
Pierre Neyron  (supplier of updated oar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 Sep 2015 15:18:47 +0200
Source: oar
Binary: liboar-perl oar-common oar-server oar-server-mysql oar-server-pgsql 
oar-node oar-user oar-user-mysql oar-user-pgsql oar-web-status oar-doc 
oar-restful-api
Architecture: all amd64 source
Version: 2.5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Pierre Neyron 
Changed-By: Pierre Neyron 
Closes: 798820
Description: 
 liboar-perl - OAR batch scheduler common library package
 oar-common - OAR batch scheduler common package
 oar-doc- OAR batch scheduler documentation package
 oar-node   - OAR batch scheduler node package
 oar-restful-api - OAR web services
 oar-server-mysql - OAR batch scheduler MySQL server backend package
 oar-server - OAR batch scheduler server package
 oar-server-pgsql - OAR batch scheduler PostgreSQL server backend package
 oar-user-mysql - OAR batch scheduler MySQL user backend package
 oar-user   - OAR batch scheduler user package
 oar-user-pgsql - OAR batch scheduler PostgreSQL user backend package
 oar-web-status - OAR batch scheduler visualization tool package
Changes:
 oar (2.5.5-2) unstable; urgency=medium
 .
   * Rework the sections of the packages (mainly set to utils instead of 
science)
   * Set the archive area/section of the oar-restful-api package to contrib/net,
 since it depends on non-free packages (Closes: #798820)
   * Remove the oar-api transitional dummy package
   * Fix typos in oar-restful-api README.Debian file
   * Remove the overlib.js files from sources, because overLIB is not actually
 used and has copyright issues (broken URL in the copyright notice)
   * Fix upstream contact and remove overLIB artistic license in the copyright
 file
Checksums-Sha1: 
 d3aff9c9aba291e56fabcf404de2bb219431260f 2437 oar_2.5.5-2.dsc
 62686be5d6d0b01cdc86725ebdd0ae243e2ee09f 23156 oar_2.5.5-2.debian.tar.xz
 0ca39231247f83efaf7cab26f8e5db5bf51a0154 75048 liboar-perl_2.5.5-2_amd64.deb
 fb0406976e84328b372ab3d8dec0388c5314484b 63152 oar-common_2.5.5-2_amd64.deb
 f4805eba3fa84debd74ab9458270a567955da72d 2822830 oar-doc_2.5.5-2_all.deb
 f4bf610700f8a58bf96c7e00f2f309716ad1ae40 32304 oar-node_2.5.5-2_amd64.deb
 25462cd15bed2b380d9f9357f94324c3512f80fa 53248 
oar-restful-api_2.5.5-2_amd64.deb
 e4ef4636c3e008514233ce8d925d6234211107bd 20280 
oar-server-mysql_2.5.5-2_amd64.deb
 eca6930a0b8d9c81f68b2a388852743b44cf1e2c 20276 
oar-server-pgsql_2.5.5-2_amd64.deb
 22395f6cff11a7eca6e6cdd0cbc427684f71dcec 149566 oar-server_2.5.5-2_amd64.deb
 9959a081f9be32df92c9ba703bff6ed1c2439c05 20242 oar-user-mysql_2.5.5-2_amd64.deb
 9a3e6f634de5c3bd7c16268938af770076806db2 20244 oar-user-pgsql_2.5.5-2_amd64.deb
 8f269690a48434506207336eb97461b11c4342ab 67454 oar-user_2.5.5-2_amd64.deb
 1bf85611efd7ab4b98af530bfd6fd06b9ce1 53002 oar-web-status_2.5.5-2_all.deb
Checksums-Sha256: 
 97005b5b8d2abb7f0457408505be6acaf1b982c950056f63a5dfd32bd6962f42 2437 
oar_2.5.5-2.dsc
 

Processed: Re: Bug#801071: Should this package be removed?

[Debian Bug Tracking System]

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

> retitle 801071 Please remove minirok from the archive
Bug #801071 [minirok] Should this package be removed?
Changed Bug title to 'Please remove minirok from the archive' from 'Should this 
package be removed?'
> reassign 801071 ftp.debian.org
Bug #801071 [minirok] Please remove minirok from the archive
Bug reassigned from package 'minirok' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #801071 to the same values 
previously set
Ignoring request to alter fixed versions of bug #801071 to the same values 
previously set
> stop
Stopping processing here.

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

Bug#801142: fusionforge-plugin-scmcvs: fails to install: post-installation script returned error exit status 127

[Andreas Beckmann]

Package: fusionforge-plugin-scmcvs
Version: 6.0.2+20150918-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package fusionforge-plugin-scmcvs.
  (Reading database ... 
(Reading database ... 15546 files and directories currently installed.)
  Preparing to unpack .../fusionforge-plugin-scmcvs_6.0.2+20150918-1_all.deb ...
  Unpacking fusionforge-plugin-scmcvs (6.0.2+20150918-1) ...
  Setting up fusionforge-plugin-scmcvs (6.0.2+20150918-1) ...
  Running /usr/share/fusionforge/plugins/scmcvs/bin/install.sh configure
  Modifying inetd for cvs server
  CVS usual config is changed for gforge one
  invoke-rc.d: policy-rc.d denied execution of start.
  dpkg: error processing package fusionforge-plugin-scmcvs (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   fusionforge-plugin-scmcvs
  E: Sub-process /usr/bin/dpkg returned an error code (1)


adding set -x to the postinst script and running it again (and
interactively thsi time) results in


# LC_ALL=C  dpkg --configure --pending
Setting up fusionforge-plugin-scmcvs (6.0.2+20150918-1) ...
+ forge_get_config source_path
+ pluginctl=/usr/share/fusionforge/post-install.d/common/plugin.sh
+ /usr/share/fusionforge/post-install.d/common/plugin.sh scmcvs configure
Running /usr/share/fusionforge/plugins/scmcvs/bin/install.sh configure
Modifying inetd for cvs server
CVS usual config is changed for gforge one
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Configuring service: 
-

There are multiple entries in /etc/inetd.conf for the 'cvspserver' service.

Please confirm that you agree to disable these entries.

Disable inetd entries? y   


invoke-rc.d: policy-rc.d denied execution of force-reload.
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
invoke-rc.d: policy-rc.d denied execution of start.
dpkg: error processing package fusionforge-plugin-scmcvs (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 fusionforge-plugin-scmcvs


(answering "n" does not change the outcome)


(most of the other fusionforge packages now pass the piuparts tests)


cheers,

Andreas


fusionforge-plugin-scmcvs_6.0.2+20150918-1.log.gz
Description: application/gzip

Processed: retitle..

[Debian Bug Tracking System]

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

> retitle 801071 RM: minirok -- ROM; dead upstream; low popcpn; alternatives 
> available
Bug #801071 [ftp.debian.org] Please remove minirok from the archive
Changed Bug title to 'RM: minirok -- ROM; dead upstream; low popcpn; 
alternatives available' from 'Please remove minirok from the archive'
> --
Stopping processing here.

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

Bug#799948: 0.6.1 doesn't solves the problem

[Vladimir Stavrinov]

The problem still exists. See

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800938

###  Vladimir Stavrinov  ###

Bug#801071: Should this package be removed?

[Dato Simó]

retitle 801071 Please remove minirok from the archive
reassign 801071 ftp.debian.org
stop

Hello—

I agree with Moritz: let’s remove minirok from the archive.

I’m maintainer and upstream. I don’t have intentions to work on it
any further.

Thanks,

Moritz Muehlenhoff  writes:

> Package: minirok
> Severity: serious
>
> Should minirok be removed? It hasn't seen an upload
> since 2009, it's dead upstream (Debian maintainer is also
> upstream), popcon usage is marginal and it relies on
> obsolete gstreamer 0.10. Plus, there's plenty of alternatives
> in the archive.
>
> Please address the outstanding bugs or reassign this to
> ftp.debian.org for removal.
>
> Cheers,
> Moritz

Processed: Re: Bug#798773: postinst script handles comments in config file incorrectly

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #798773 [pdns-server] postinst script handles comments in config file 
incorrectly
Severity set to 'serious' from 'normal'

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