Bug#810365: [apt] Temporary failure resolving xxxx even when the network is up and running

[BogDan Vatra]

On Friday 08 January 2016 17:16:27 Julian Andres Klode wrote:
> On Fri, Jan 08, 2016 at 05:16:00PM +0100, Julian Andres Klode wrote:
> > Control: tag -1 moreinfo
> > 
> > On Fri, Jan 08, 2016 at 05:28:02PM +0200, Bogdan Vatra wrote:
> > > Package: apt
> > > Version: 1.1.10
> > > Severity: serious
> > > 
> > > --- Please enter the report below this line. ---
> > > The problem happens on an chrooted arm64 image on Android.
> > > 
> > > Commands log:
> > > 
> > > root@localhost:~# apt update
> > > Err:1 http://httpredir.debian.org/debian sid InRelease
> > > 
> > >   Temporary failure resolving 'httpredir.debian.org'
> > > 
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > All packages are up to date.
> > > W: Failed to fetch
> > > http://httpredir.debian.org/debian/dists/sid/InRelease
> > > Temporary failure resolving 'httpredir.debian.org'
> > > W: Some index files failed to download. They have been ignored, or old
> > > ones
> > > used instead.
> > 
> > Probably /etc/resolv.conf is not readable by _apt?
> 
> _apt being a username used by the fetching process.

Well it is world readable:

root@localhost:~# ls -l /etc/resolv.conf 
-rw-r--r--. 1 root root 43 Jan  8 14:57 /etc/resolv.conf

I think the problem is that apt is running under _apt user which on android it 
doesn't network permissions.

Is it possible to run at as root?

Yours,
BogDan.

Bug#805627: marked as done (red5: Transition to Groovy 2)

[Debian Bug Tracking System]

Your message dated Fri, 8 Jan 2016 15:34:09 -0300
with message-id 

and subject line Bug#805627: fixed in red5 1.0~svn4374-4.1
has caused the Debian Bug report #805627,
regarding red5: Transition to Groovy 2
to be marked as done.

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

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


-- 
805627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: red5
Version: 1.0~svn4374-4
Severity: normal
Tags: patch

Dear Maintainer,

Groovy 1.x is going to be removed soon and red5 has to switch to Groovy 2.
Please apply the patch attached.

Thank you,

Emmanuel Bourg
Index: debian/ant.properties
===
--- debian/ant.properties	(revision 555)
+++ debian/ant.properties	(working copy)
@@ -11,7 +11,7 @@
 /usr/share/java/commons-collections3.jar;\
 /usr/share/java/commons-beanutils.jar;\
 /usr/share/java/commons-codec.jar;\
-/usr/share/java/groovy.jar;\
+/usr/share/java/groovy-2.x.jar;\
 /usr/share/java/httpcore.jar;\
 /usr/share/java/httpcore-nio.jar;\
 /usr/share/java/httpclient.jar;\
Index: debian/changelog
===
--- debian/changelog	(revision 555)
+++ debian/changelog	(working copy)
@@ -1,3 +1,10 @@
+red5 (1.0~svn4374-5) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Transition to Groovy 2
+
+ -- Emmanuel Bourg   Fri, 20 Nov 2015 13:17:11 +0100
+
 red5 (1.0~svn4374-4) unstable; urgency=medium
 
   [ Emmanuel Bourg ]
Index: debian/control
===
--- debian/control	(revision 555)
+++ debian/control	(working copy)
@@ -7,8 +7,8 @@
  default-jdk-doc,
  docbook-xsl,
  glassfish-javaee,
- groovy,
- groovy-doc,
+ groovy2,
+ groovy2-doc,
  junit4 (>= 4.5),
  jython,
  libbcprov-java,
@@ -46,7 +46,7 @@
 Package: libred5-java
 Architecture: all
 Depends: glassfish-javaee,
- groovy,
+ groovy2,
  jython,
  libantlr-java,
  libaopalliance-java,
@@ -112,7 +112,7 @@
 Architecture: all
 Section: doc
 Depends: ${misc:Depends}
-Recommends: default-jdk-doc, groovy-doc, liblog4j1.2-java-doc, libmina2-java-doc
+Recommends: default-jdk-doc, groovy2-doc, liblog4j1.2-java-doc, libmina2-java-doc
 Suggests: libred5-java (= ${source:Version})
 Description: flash streaming server - documentation
  Red5 is a Java implementation of a Flash Media Server based on
Index: debian/patches/12_javadoc_links.diff
===
--- debian/patches/12_javadoc_links.diff	(revision 555)
+++ debian/patches/12_javadoc_links.diff	(working copy)
@@ -39,7 +39,7 @@
 +
 +
 +
-+
++
  		
  		
  		
Index: debian/red5-server.links
===
--- debian/red5-server.links	(revision 555)
+++ debian/red5-server.links	(working copy)
@@ -15,7 +15,7 @@
 /usr/share/java/commons-modeler.jar usr/share/red5/lib/com.springsource.org.apache.commons.modeler.jar
 /usr/share/java/commons-pool.jar usr/share/red5/lib/com.springsource.org.apache.commons.pool.jar
 /usr/share/java/xercesImpl.jar usr/share/red5/lib/com.springsource.org.apache.xerces.jar
-/usr/share/java/groovy.jar usr/share/red5/lib/com.springsource.org.codehaus.groovy.jar
+/usr/share/java/groovy-2.x.jar usr/share/red5/lib/com.springsource.org.codehaus.groovy.jar
 /usr/share/java/js.jar usr/share/red5/lib/com.springsource.org.mozilla.javascript.jar
 /usr/share/java/asm4.jar usr/share/red5/lib/com.springsource.org.objectweb.asm.jar
 /usr/share/java/asm4-commons.jar usr/share/red5/lib/com.springsource.org.objectweb.asm.commons.jar
--- End Message ---
--- Begin Message ---
Source: red5
Source-Version: 1.0~svn4374-4.1

I just uploaded the NMU prepared by Emmanuel to fix this bug.

-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche--- End Message ---

Bug#810365: [apt] Temporary failure resolving xxxx even when the network is up and running

[BogDan Vatra]

On Friday 08 January 2016 20:21:10 BogDan Vatra wrote:
> On Friday 08 January 2016 17:16:27 Julian Andres Klode wrote:
> > On Fri, Jan 08, 2016 at 05:16:00PM +0100, Julian Andres Klode wrote:
> > > Control: tag -1 moreinfo
> > > 
> > > On Fri, Jan 08, 2016 at 05:28:02PM +0200, Bogdan Vatra wrote:
> > > > Package: apt
> > > > Version: 1.1.10
> > > > Severity: serious
> > > > 
> > > > --- Please enter the report below this line. ---
> > > > The problem happens on an chrooted arm64 image on Android.
> > > > 
> > > > Commands log:
> > > > 
> > > > root@localhost:~# apt update
> > > > Err:1 http://httpredir.debian.org/debian sid InRelease
> > > > 
> > > >   Temporary failure resolving 'httpredir.debian.org'
> > > > 
> > > > Reading package lists... Done
> > > > Building dependency tree
> > > > Reading state information... Done
> > > > All packages are up to date.
> > > > W: Failed to fetch
> > > > http://httpredir.debian.org/debian/dists/sid/InRelease
> > > > Temporary failure resolving 'httpredir.debian.org'
> > > > W: Some index files failed to download. They have been ignored, or old
> > > > ones
> > > > used instead.
> > > 
> > > Probably /etc/resolv.conf is not readable by _apt?
> > 
> > _apt being a username used by the fetching process.
> 
> Well it is world readable:
> 
> root@localhost:~# ls -l /etc/resolv.conf
> -rw-r--r--. 1 root root 43 Jan  8 14:57 /etc/resolv.conf
> 
> I think the problem is that apt is running under _apt user which on android
> it doesn't network permissions.
> 
> Is it possible to run at as root?
> 

I "fixed" it by changing _apt UID to 0 :), but IMHO it is not the best 
solution... 

Yours,
BogDan.

Processed: block 808899 with 790978

[Debian Bug Tracking System]

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

> block 808899 with 790978
Bug #808899 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS: undefined reference to 
`pseudolocalize_string(std::__cxx11::basic_string const&)'
808899 was not blocked by any bugs.
808899 was not blocking any bugs.
Added blocking bug(s) of 808899: 790978
> thanks
Stopping processing here.

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

Processed (with 1 error): unblock 808899 with 791192

[Debian Bug Tracking System]

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

> unblock 808899 with 791192
Bug #808899 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS: undefined reference to 
`pseudolocalize_string(std::__cxx11::basic_string const&)'
808899 was blocked by: 791192
808899 was not blocking any bugs.
Removed blocking bug(s) of 808899: 791192
Failed to set blocking bugs of 808899: can't find location for 791192.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: block 809861 with 808899

[Debian Bug Tracking System]

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

> block 809861 with 808899
Bug #809861 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS with libpng16
809861 was not blocked by any bugs.
809861 was blocking: 650601
Added blocking bug(s) of 809861: 808899
> thanks
Stopping processing here.

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

Processed (with 1 error): block 808899 with 791192

[Debian Bug Tracking System]

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

> block 808899 with 791192
Bug #808899 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS: undefined reference to 
`pseudolocalize_string(std::__cxx11::basic_string const&)'
808899 was not blocked by any bugs.
808899 was not blocking any bugs.
Added blocking bug(s) of 808899: 791192
Failed to set blocking bugs of 808899: can't find location for 791192.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#808899: android-platform-frameworks-base: FTBFS: undefined reference to `pseudolocalize_string(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)'

[Tobias Frost]

Debugging into it: 
A rebuild of android-platform-build-21 seems to fix it.

-- 
tobi

Processed: unblock 808899 with 790978

[Debian Bug Tracking System]

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

> unblock 808899 with 790978
Bug #808899 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS: undefined reference to 
`pseudolocalize_string(std::__cxx11::basic_string const&)'
808899 was not blocked by any bugs.
808899 was not blocking any bugs.
Removed blocking bug(s) of 808899: 790978
> thanks
Stopping processing here.

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

Processed: android-platform-build: diff for NMU version 21-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 790978 + patch
Bug #790978 [src:android-platform-build] android-platform-build: library 
transition may be needed when GCC 5 is the default
Added tag(s) patch.

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

Bug#810473: yowsup-cli: Fails to register with "old_version"

[Manolo Díaz]

Package: yowsup-cli
Version: 2.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

There is no much to add to the subject. The complete output:

INFO:yowsup.common.http.warequest:{"status":"fail","reason":"old_version"}

status: fail
reason: old_version


Best Regards,
Manolo Díaz



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

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

Versions of packages yowsup-cli depends on:
ii  python  2.7.11-1
ii  python-libxml2  2.9.3+dfsg1-1
ii  python-yowsup   2.4-1

yowsup-cli recommends no packages.

yowsup-cli suggests no packages.

-- no debconf information

Bug#790978: android-platform-build: diff for NMU version 21-4.1

[Tobias Frost]

Control: tags 790978 + patch

Dear maintainer,

I've prepared an NMU for android-platform-build (versioned as 21-4.1). The diff
is attached to this message.

Regards.
diff -Nru android-platform-build-21/debian/changelog 
android-platform-build-21/debian/changelog
--- android-platform-build-21/debian/changelog  2014-11-25 13:02:07.0 
+0100
+++ android-platform-build-21/debian/changelog  2016-01-08 20:16:32.0 
+0100
@@ -1,3 +1,11 @@
+android-platform-build (21-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuilt for GCC-5 Transistion (Closes: #790978), adding
+a break against current aapt as suggested in the BTS.
+
+ -- Tobias Frost   Fri, 08 Jan 2016 20:16:32 +0100
+
 android-platform-build (21-4) unstable; urgency=low
 
   * include Breaks: and Replaces: to allow for proper upgrading
diff -Nru android-platform-build-21/debian/control 
android-platform-build-21/debian/control
--- android-platform-build-21/debian/control2014-11-25 12:51:32.0 
+0100
+++ android-platform-build-21/debian/control2016-01-08 20:15:41.0 
+0100
@@ -44,6 +44,7 @@
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
+Breaks: aapt (<= 21-2)
 Description: Android utility library for cross-platform tools
  Library providing utility functions to Android related tools. This is needed
  purely to get various Android utilities working.

Processed (with 1 error): usertagging 809861, unblock 650601 with 809861, forcibly merging 808899 809861

[Debian Bug Tracking System]

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

> usertags 809861 =
User is t...@debian.org
There were no usertags set.
Usertags are now: .
> unblock 650601 with 809861
Bug #650601 [release.debian.org] transition: libpng 1.6
650601 was blocked by: 809896 810172 809889 810177 810170 809937 809962 641889 
810168 810169 649798 636004 809892 809887 650489 810200 742559 809894 809873 
809921 662566 809885 809933 662444 810201 810174 809893 809907 662550 809949 
650571 648126 810185 810203 662522 809957 662407 809835 662416 649557 810195 
809938 809956 809950 743391 662334 810166 650581 810208 809833 662411 810175 
810193 810192 741891 809871 810187 809891 809897 810189 809953 809861 810207 
809936 809911 809943 662381 649552 662523 809954 809960 809863 662314 809880 
810181 636998 809947 641892 635946 809869 810167 662465 810194 809864 810205 
809940 742569 662443 809935 810171 809879 809948 809866 809860 810204 810202 
809859 810001 809886 809941 809945 810179 741894 810173 809883 809952 809836 
809874 648129 742560 635945 809946 809913 662554 809944 662273 809961 638812 
662530 650483 810206 810165 809884 810176 742655 810191 650563 810095 809898 
662556 809905 809872 649971 662476 741901 810180 810182 809909 810183 810178 
662437 809942 810209 809878 650484 809862 809904 809888 635704 809870 809910 
649547 650567 809934 662492 809958 810186 809882 809895 810188 810197 809890 
642265 662473 809959 809906 662421 810196 810190 809865 809881 809955 809868 
648131 809939 649546 809908 809867 809899 809951
650601 was blocking: 649556 649973
Removed blocking bug(s) of 650601: 809861
> forcemerge 808899 809861
Bug #808899 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS: undefined reference to 
`pseudolocalize_string(std::__cxx11::basic_string const&)'
Bug #809861 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS with libpng16
Severity set to 'serious' from 'important'
Failed to forcibly merge 808899: It is nonsensical for a bug to block itself 
(or a merged partner): 809861.

> thanks
Stopping processing here.

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

Processed: severity of 810365 is wishlist

[Debian Bug Tracking System]

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

> severity 810365 wishlist
Bug #810365 [apt] [apt] Temporary failure resolving   even when the network 
is up and running
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

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

Bug#804558: tweepy: FTBFS: ImportError: No module named {unittest2,vcr}

[Miguel Landaeta]

On Mon, Jan 4, 2016 at 6:43 AM, Carl Chenet  wrote:
> Hi Miguel,
>
> First of all, happy new year 2016!

Hi Carl, happy new year to you as well! :)

> [...]
>
> Tell me if I'm wrong but unittests executions are not mandatory by
> Debian policy while building a Debian package.

That's right, this is not mandatory.

>
> While waiting that somebody packages unittest2 and/or vcr for Debian,
> could you disable the unit tests while creating the Debian package of
> Tweepy? I've 2 more Debian package coming up and depending on
> python3-tweepy so that would help me *a lot*.
>
> Tell me if you need that I push the modifications in the debian/rules (I
> guess it's a simple override).

Let's do this:

* Can you file a wishlist bug on tweepy asking to enable the unit tests
during build time and maybe explain why that can't be enabled right now
and/or mark the bug as blocked by the unittest2 and/or vcr ITPs?

* Push and upload the changes to workaround the FTBFS.

I can't fix this bug right now because I'm about to begin my move to
another country and my workstation with my PGP key has some
connection problems during this week.

Thanks,
Miguel.

-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche

Bug#810475: python-astroid: Pylint 1.4.4 does not work with Astroid 1.4.x

[Johannes Weißl]

Package: python-astroid
Version: 1.4.3-1
Severity: grave
Justification: renders package unusable

The current versions of pylint (1.4.4) and python-astroid (1.4.3) in Debian
Stretch do not work together, causing errors like:

Problem importing module classes.py: cannot import name InferenceContext
E0602:...,...: ...: Undefined variable

See also
https://bitbucket.org/logilab/pylint/issues/720/problem-importing-module-classespy-cannot



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

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

Versions of packages python-astroid depends on:
ii  python-lazy-object-proxy  1.2.1-1
ii  python-logilab-common 1.0.2-1
ii  python-six1.10.0-1
ii  python-wrapt  1.8.0-5+b1
pn  python:any

python-astroid recommends no packages.

python-astroid suggests no packages.

-- no debconf information

Processed: block 650601 with 809861

[Debian Bug Tracking System]

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

> block 650601 with 809861
Bug #650601 [release.debian.org] transition: libpng 1.6
650601 was blocked by: 809893 810174 662554 650563 809859 809874 641889 810195 
649798 809836 810176 650567 662523 809962 662407 649557 809894 809948 809952 
742560 809940 809866 809887 810171 648129 650571 810178 809862 809908 662314 
662273 809935 742569 649971 809933 809946 810172 810194 810191 809913 635945 
742655 638812 810181 810201 810001 809886 662381 810192 809880 810173 809938 
810186 635946 810182 809957 741894 809873 809941 810175 662437 810189 642265 
809898 636004 810095 662421 662443 662522 810166 809888 810206 809951 809868 
810203 809885 810200 809950 810193 809954 810167 810196 810168 649546 809947 
649547 809871 809865 809897 810177 809944 809881 662556 809890 810165 809955 
809939 810204 809960 809942 810179 809833 809921 809864 810185 809911 662566 
809937 741891 809899 662476 809949 809860 809891 810197 662334 810183 809878 
809835 810170 810207 809906 662492 636998 810190 809945 650489 809883 809870 
641892 809943 810209 810205 809959 662465 809889 662473 742559 809884 809958 
809910 809869 809863 809907 809892 809882 741901 810180 809895 635704 809934 
809879 810187 743391 810169 649552 809896 650581 809956 662416 809936 662444 
809905 648126 810188 809867 662411 650484 810202 809961 809872 809953 662550 
809909 648131 662530 810208 809904 650483
650601 was blocking: 649556 649973
Added blocking bug(s) of 650601: 809861
> thanks
Stopping processing here.

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

Bug#790978: marked as done (android-platform-build: library transition may be needed when GCC 5 is the default)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 19:33:45 +
with message-id 
and subject line Bug#790978: fixed in android-platform-build 21-4.1
has caused the Debian Bug report #790978,
regarding android-platform-build: library transition may be needed when GCC 5 
is the default
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.)


-- 
790978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:android-platform-build
Version: 21-4
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
Source: android-platform-build
Source-Version: 21-4.1

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated android-platform-build 
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, 08 Jan 2016 20:16:32 +0100
Source: android-platform-build
Binary: zipalign android-libhost android-libhost-dev
Architecture: source amd64
Version: 21-4.1
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Tobias Frost 
Description:
 android-libhost - Android utility library for cross-platform tools
 android-libhost-dev - Android utility library for cross-platform tools - 
headers
 zipalign   - Align zip/jar/apk along byte boundaries
Closes: 790978
Changes:
 

Processed: severity of 809861 is important

[Debian Bug Tracking System]

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

> severity 809861 important
Bug #809861 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: FTBFS with libpng16
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#810478: konsole: can't start konsole

[Cosimo Morelli]

Package: konsole
Version: 4:15.08.3-1
Severity: critical
Justification: breaks the whole system

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

when I try to open konsole this message appears:

Cannot load library /usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd:
(/usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd.so

also the system freezes and I need to open a terminal and kill drkonqi



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

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

Versions of packages konsole depends on:
ii  konsole-kpart   4:15.08.3-1
ii  libc6   2.21-6
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configgui55.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libqt5core5a5.5.1+dfsg-12
ii  libqt5gui5  5.5.1+dfsg-12
ii  libqt5widgets5  5.5.1+dfsg-12
ii  libstdc++6  5.3.1-5

konsole recommends no packages.

konsole suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWkBo6AAoJEF8PzE63GYeQN/UP+gJXrpZvnWYvzIqaEb5UPWED
mdZTi/DPn5n6q/Fr4zSNoXP7Eg94rUaLEVVHLfopSSARsQGHv82xwo9HRAIChPSS
hd1z8MZu28M/1RNUjgO5kXdqHYU9hvj0ZRk4qUK2tuAi0TYSoqql8cy2bFPSdSOg
E9Cn+aA5HVhWJ/hJhS9RtgOrgaZPkMCgAdRboJJs4VSQlvpOuK2TzPB70x2w525T
tf++RbrpsFRPsMvh5n7hLWjr/PKbJWgXhQfmmhaQqUfXj8dfSEAh2rbruNtVI5SQ
OsuiKmob/fr1RmoFQHvwnrVerCW88Lkih1dTA2t0/68mb0GcB4tqzi/RTqwnyCFZ
oRjRhwFJmXxRM7ogfK32Gv67P74+DMX9nj/gJBL96zC/GNtDj1QQWWBlW2OAS6wq
fWHgG98wrRXdYXNo7pvlNmMtudqtXwKloKyPKkP/WobZnkukHabQDP+6H4IRqsUp
Np/tRS67+Yb6GorE0nbYMxcqwX2pkvepfKEfYf6LEc2hUmaMxSwefXsOJ83j4/DC
YM9OS8Q3/RZg3XdhDbfyQgO3iuu8mRhE2jqWqAvvPYl2FwxhRXHOm1jZjQO32Yc+
LghLLJ0ftDLnRipxwq33IWlXj0PbQXtqpcKUpf/2VZ/tURJN4eBTJyqoQEF9MsXU
YQNLT8Zf9EW4bSOvbLKl
=bmVO
-END PGP SIGNATURE-

Bug#810475: marked as done (python-astroid: Pylint 1.4.4 does not work with Astroid 1.4.x)

[Debian Bug Tracking System]

Your message dated Fri, 8 Jan 2016 20:00:40 +
with message-id 

and subject line Re: Bug#810475: python-astroid: Pylint 1.4.4 does not work 
with Astroid 1.4.x
has caused the Debian Bug report #810475,
regarding python-astroid: Pylint 1.4.4 does not work with Astroid 1.4.x
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.)


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

The current versions of pylint (1.4.4) and python-astroid (1.4.3) in Debian
Stretch do not work together, causing errors like:

Problem importing module classes.py: cannot import name InferenceContext
E0602:...,...: ...: Undefined variable

See also
https://bitbucket.org/logilab/pylint/issues/720/problem-importing-module-classespy-cannot



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

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

Versions of packages python-astroid depends on:
ii  python-lazy-object-proxy  1.2.1-1
ii  python-logilab-common 1.0.2-1
ii  python-six1.10.0-1
ii  python-wrapt  1.8.0-5+b1
pn  python:any

python-astroid recommends no packages.

python-astroid suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Jan 8, 2016 at 7:23 PM, Johannes Weißl  wrote:
> The current versions of pylint (1.4.4) and python-astroid (1.4.3) in Debian

the current version of pylint is 1.5.2-1, please upgrade.

-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi--- End Message ---

Processed: affects 810475 + pylint

[Debian Bug Tracking System]

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

> affects 810475 + pylint
Bug #810475 [python-astroid] python-astroid: Pylint 1.4.4 does not work with 
Astroid 1.4.x
Added indication that 810475 affects pylint
> thanks
Stopping processing here.

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

Bug#810360: marked as done (ugene: switch B-D to libprocps-dev)

[Debian Bug Tracking System]

Your message dated Sat, 09 Jan 2016 00:05:17 +
with message-id 
and subject line Bug#810360: fixed in ugene 1.20.0+dfsg-1
has caused the Debian Bug report #810360,
regarding ugene: switch B-D to libprocps-dev
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.)


-- 
810360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ugene
Version: 1.19.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

libprocps4-dev is history, please switch to libprocps-dev.


Andreas
--- End Message ---
--- Begin Message ---
Source: ugene
Source-Version: 1.20.0+dfsg-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ugene package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Jan 2016 19:35:14 +0100
Source: ugene
Binary: ugene ugene-data
Architecture: source
Version: 1.20.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 ugene  - integrated bioinformatics toolkit
 ugene-data - required data for UGENE - integrated bioinformatics toolkit
Closes: 810360
Changes:
 ugene (1.20.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
   * Build-Depends: libprocps-dev (instead of libprocps4-dev)
 Closes: #810360
   * add repacksuffix to d/watch
Checksums-Sha1:
 5625999d157561d292b3854a85a5be09859eac01 2311 ugene_1.20.0+dfsg-1.dsc
 b76b7906447949b5c7bc51ad56f3ec96786b4d1b 15803228 ugene_1.20.0+dfsg.orig.tar.xz
 a71faf44da4ecd0a0c2c16066e2a3240dbdcf99c 11076 
ugene_1.20.0+dfsg-1.debian.tar.xz
Checksums-Sha256:
 622f50dda46c6758c50c0a5593809f17627d41b9829a3f768f4d8e5d0786ad5f 2311 
ugene_1.20.0+dfsg-1.dsc
 b2019abd336325d9e459e3e104ca8dfddb3793de7ffc4ba2d39fd8bc44eea266 15803228 
ugene_1.20.0+dfsg.orig.tar.xz
 5892edfed6eb01d73a8241bf415b6ed50141ee5f5c12c7cf8caa8a31e3aa71d5 11076 
ugene_1.20.0+dfsg-1.debian.tar.xz
Files:
 98efa702b6b60bbcc058fb7f52e4ea62 2311 non-free/science optional 
ugene_1.20.0+dfsg-1.dsc
 b6afc6859396644056ca5c532c2a3e89 15803228 non-free/science optional 
ugene_1.20.0+dfsg.orig.tar.xz
 87659fe12eef1f3ddd9c56896b90948e 11076 non-free/science optional 
ugene_1.20.0+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWkEi0AAoJEFeKBJTRxkbRDW8P/2o3xJ9fhaOXywg71wfbhgg6
PwCY+0ejmZHtSwFrtJH2DuC5vj9Pt2x0CLyb0fJggUU5wxob7iLMR1QbgYWiiwse
ytrcpW3p6N0GynzbtvobwoygtCT4CvYk/Y2Xw5aPfWca0nf6/x/o+9qZbo3iwPMR
xxmUyQU3mvCe6qbm8koTCSQtGzSsivKaJamGq/goA1BZKq1E9rmCjPeXWsez24kG
5Pr4Ka7NTMHNrDoppciK79qzB94nOFCxzzLyG5gQAvJgx0ECDpP3IKT3XpcUesjr
0//cW1lR39a+kMgLoPSLnrRTfgHsmLuMLQao+2QYdSkYKqS8kecZRF5kmGuDWYl/
gNipmKSnv4+7oMp9Nnp1Dovom/26M6DFam6bf4LROhSU15znxGvJH8ZSDhCcr5d/
FKN2PeH/RaWWEsGtFAPwSi0NVSwgaxGo0qkTOvd3t1u8QmgfPqmQxuLbkl4JVcub
QGM4qPiW93sStYtJviS00YPz5lRUpYFuVNVWen8XRmMB/fJU91GUSyr1t1aI5Snk
Y2SHvbz7o/WmWccJnGlVyzPxVGvYWqwe9Z3dcqKzjjEmUh12gUiWjXGhqfm7nIK4
rf+Fb5rOuQZvOSZon4U1KwIQAqrhU7qtPTrqNKXN+sUXwdN2tv/YgU2zkv10MNf/
pEuGFzosXigzqgjHH8xL
=Ti2O
-END PGP SIGNATURE End Message ---

Bug#810491: netsurf-gtk: CVE-2015-7505 CVE-2015-7506 CVE-2015-7507 CVE-2015-7508

[Moritz Muehlenhoff]

Package: netsurf-gtk
Severity: grave
Tags: security
Justification: user security hole

Please see these:

CVE-2015-7508 [heap overflow]
http://source.netsurf-browser.org/libnsbmp.git/commit/?id=041df43bbe273b0829132b0b17d89a69da2927d4

CVE-2015-7507 [out-of-bounds read]
http://source.netsurf-browser.org/libnsbmp.git/commit/?id=49427b52ba41a1813e3822301612e2e170107efd

CVE-2015-7506 [out-of-bounds read]
http://source.netsurf-browser.org/libnsgif.git/commit/?id=088fa0819f1aeaf212a95caf7393a38c1640b5f0

CVE-2015-7505 [stack overflow]
http://source.netsurf-browser.org/libnsgif.git/commit/?id=a268d2c15252ac58c19f1b19771822c66bcf73b2

Cheers,
Moritz

Bug#808899: marked as done (android-platform-frameworks-base: FTBFS: undefined reference to `pseudolocalize_string(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 21:49:30 +
with message-id 
and subject line Bug#808899: fixed in android-platform-frameworks-base 21-2.1
has caused the Debian Bug report #808899,
regarding android-platform-frameworks-base: FTBFS: undefined reference to 
`pseudolocalize_string(std::__cxx11::basic_string const&)'
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.)


-- 
808899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-frameworks-base
Version: 21-2
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,

android-platform-frameworks-base fails to build from source in unstable/amd64:

  [..]
  g++ -O2 -fPIC -Wno-format-y2k -I../../include -I/usr/include/android -include 
/usr/include/android/arch/linux-x86/AndroidConfig.h -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  
-c -o ZipEntry.o ZipEntry.cpp
  g++ -O2 -fPIC -Wno-format-y2k -I../../include -I/usr/include/android -include 
/usr/include/android/arch/linux-x86/AndroidConfig.h -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  
-c -o ZipFile.o ZipFile.cpp
  g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o aapt AaptAssets.o 
Command.o CrunchCache.o FileFinder.o Main.o Package.o StringPool.o XMLNode.o 
ResourceFilter.o ResourceTable.o Images.o Resource.o SourcePos.o ZipEntry.o 
ZipFile.o -lrt -ldl -lpthread -lz -lexpat -lpng -L/usr/lib/android  -lcutils 
-lhost -llog -lutils -L../../libs/androidfw  -landroidfw 
  XMLNode.o: In function `parseStyledString(Bundle*, char const*, 
android::ResXMLTree*, android::String16 const&, android::String16*, 
android::Vector*, bool, bool)':
  
/home/lamby/temp/cdt.20151224075332.p4r7Xir37v/android-platform-frameworks-base-21/tools/aapt/XMLNode.cpp:214:
 undefined reference to `pseudolocalize_string(std::__cxx11::basic_string const&)'
  collect2: error: ld returned 1 exit status
  Makefile:25: recipe for target 'aapt' failed
  make[2]: *** [aapt] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151224075332.p4r7Xir37v/android-platform-frameworks-base-21/tools/aapt'
  Makefile:4: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151224075332.p4r7Xir37v/android-platform-frameworks-base-21'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:21: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


android-platform-frameworks-base.21-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: android-platform-frameworks-base
Source-Version: 21-2.1

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated 
android-platform-frameworks-base 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, 08 Jan 2016 20:53:54 +0100
Source: android-platform-frameworks-base
Binary: android-libandroidfw android-libandroidfw-dev aapt
Architecture: source amd64
Version: 21-2.1
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Tobias Frost 
Description:
 aapt   - Android Asset Packaging Tool
 android-libandroidfw - Android utility library
 android-libandroidfw-dev - Android utility library - Development files
Closes: 808899 809861 810166
Changes:
 android-platform-frameworks-base (21-2.1) unstable; urgency=medium

Bug#809136: Block borgbackup migration to stable for now

[Antoine Beaupré]

Source: borgbackup
Followup-For: Bug #809136

[TL;DR: keep borg in testing. let it be released with stable when
streth gets released. use backports to ensure compatibility works
across debian releases, if necessary (and it is not, right now!).]

Both as a user and developer of borg backup, I disagree with some of
the comments made of borg in this bug report.

Borg has actually shown great API stability since it forked from
Attic. The change that occured was necessary, and was well documented
in the release notes and the manual. (It should have been documented
in the NEWS.Debian file in the Debian package as well.) It is also the
*only* one that happened in over 15 releases since the fork from
Attic. We can even still convert older, prehistoric attic repositories
to borg without data loss.

Furthermore, this only concerns the backup remote RPC protocol. The
storage format is *still* compatible, all the way back to attic. If
you have a copy of your repository, you can still backup to and from
it. If your server is upgraded, it is true that you do need to upgrade
your client, however (and vice-versa).

But tons of backup software in Debian have that behavior: unison was
already mentionned, but rdiff-backup also has the same problems. That
is why we have backports: when the server side upgrades, we upgrade
the clients to the backports version. It's annoying, but it works, and
rdiff-backup has been in Debian for a long time. Those other backup
softwares are way more popular, sometimes by orders of magnitude, than
borg:

https://qa.debian.org/popcon.php?package=rdiff-backup
https://qa.debian.org/popcon.php?package=unison
https://qa.debian.org/popcon.php?package=borgbackup

Keeping borg from entering stable (or, more precisely, testing in this
case) is exactly what we *don't* want here. If we keep borg from
entering testing, we keep it from being backported. If we keep it from
being backported, we make it *harder* for people to run the same
version of borg across different versions of Debian. So we basically
make the Debian package useless, which means people won't use it and
will instead use the pip version.

Is that what we want?

I was looking at backporting borg from stretch to jessie, but if the
maintainers are going to remove it from stretch, i'm certainly not
going to bother, and that would be a shame...

Finally, keep in mind that this is a problem only in Debian, and only
if we have multiple, incompatible versions of borg in
Debian. (Non-debian installs can use virtualenvs to install as many
borg versions as they want.) Right now, we only have one version
(0.29.0-2), and it's compatible between unstable and testing. If
testing gets released right now, stable, testing and unstable are all
compatible, and we have absolutely no problem.

Furthermore, it's very likely that borg 1.0 gets released before
stretch, so all those arguments will be completely irrelevant because
borg *will* be API stable.

This, in short, is a non-isse right now. If 0.28 was in stable and
0.29 in testing, this would be a bug, but then the fix would be a
backport, not a removal from stable (which you can do, if you are
really stuck, anyways).

Now, can i open this bug about backporting? :)

a.

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

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

Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

[Andreas Beckmann]

On Sun, 3 Jan 2016 18:15:45 +0100 Michael Biebl  wrote:
> This bug as actually been fixed in 228-3 by
> 
> https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=ea089f29bbd2583545b5c1a83756feafacf2801f
> 
> We can't unfortunately fix the existing udev.prerm of older versions,
> only make sure the new one no longer has the problem.

Why can't this be fixed in a jessie point release?
So at least upgrades from up-to-date jessie would have a deconfigurable
udev.

In ifupdown, adding a
  Conflicts: udev (<< 228-3)
could convince dpkg to deconfigure the other package (i.e. ifupdown)
involved in this Breaks loop ... (but I haven't tested this).


Andreas

Bug#808693: marked as done (wtforms: FTBFS: tests.ext_django.tests.I18NTest fails)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 11:05:03 +
with message-id 
and subject line Bug#808693: fixed in wtforms 2.1-1
has caused the Debian Bug report #808693,
regarding wtforms: FTBFS: tests.ext_django.tests.I18NTest fails
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.)


-- 
808693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wtforms
Version: 2.0.2-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

test_parsing (tests.locale_babel.TestLocaleDecimal) ... ok
test_typeerror (tests.locale_babel.TestLocaleDecimal) ... ok

==
FAIL: test_django_translations (tests.ext_django.tests.I18NTest)
--
Traceback (most recent call last):
  File "/wtforms-2.0.2/tests/ext_django/tests.py", line 263, in 
test_django_translations
self.assertEqual(trans.gettext('Username'), u'Nombre de usuario')
AssertionError: u'Username' != u'Nombre de usuario'
- Username
+ Nombre de usuario


==
FAIL: test_i18n_form (tests.ext_django.tests.I18NTest)
--
Traceback (most recent call last):
  File "/wtforms-2.0.2/tests/ext_django/tests.py", line 274, in test_i18n_form
self.assertEqual(form.a.gettext('Username'), u'Nombre de usuario')
AssertionError: u'Username' != u'Nombre de usuario'
- Username
+ Nombre de usuario


--
Ran 199 tests in 0.388s

FAILED (failures=2)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/wtforms.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: wtforms
Source-Version: 2.1-1

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

Debian distribution maintenance software
pp.
Orestis Ioannou  (supplier of updated wtforms 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, 08 Dec 2015 00:59:56 +0100
Source: wtforms
Binary: python-wtforms python3-wtforms python-wtforms-doc
Architecture: source
Version: 2.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Orestis Ioannou 
Description:
 python-wtforms - flexible forms validation and rendering library for Python 2
 python-wtforms-doc - flexible forms validation and rendering library for 
Python (doc)
 python3-wtforms - flexible forms validation and rendering library for Python 3
Closes: 808693
Changes:
 wtforms (2.1-1) unstable; urgency=low
 .
   * Team upload.
 .
   * Drop django extension and hence django deps. This extensions
   is deprecated upstream in the 2.0 release and it is generating
   tests failures with the django in testing.
   * Use python-coverage to run tests Closes: #808693
   * Remove useless patches due to removing the django extension
   * New upstream release
Checksums-Sha1:
 a26f39f036ded81eb4b1478952200f8f905480b7 2295 wtforms_2.1-1.dsc
 1c38e49e8fa216fcf15e4ae3f30a22f6128530c1 148036 wtforms_2.1.orig.tar.gz
 5a969fa15846d47c43a2611c09913235260978ec 3832 wtforms_2.1-1.debian.tar.xz
Checksums-Sha256:
 

Bug#790535: fixed in sus 7.20160107

[Andreas Beckmann]

Hi David,

please fix this for jessie, too.

Rebuilding the sid package with an additional changelog stanza versioned
7.20160107~deb8u1 and targetting jessie should work fine.
The next jessie point release is scheduled for January 23rd, if you file
the jessie-pu request quickly you should be able to get the fix in there
(request, approval, upload will have to happen within the next week to
hit the window).

Thanks!


Andreas

Processed: found 810491 in 3.2+dfsg-2

[Debian Bug Tracking System]

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

> found 810491 3.2+dfsg-2
Bug #810491 [netsurf-gtk] netsurf-gtk: CVE-2015-7505 CVE-2015-7506 
CVE-2015-7507 CVE-2015-7508
Marked as found in versions netsurf/3.2+dfsg-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784613 [src:spyder] [spyder] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784514 [src:qgis] [qgis] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784612 [src:anki] [anki] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784610 [src:frescobaldi] [frescobaldi] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784616 [src:dff] [dff] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784615 [src:ninja-ide] [ninja-ide] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784614 [src:openlp] [openlp] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Bug#809568: marked as done (django-celery: FTBFS: ImportError: cannot import name get_cache)

[Debian Bug Tracking System]

Your message dated Sat, 09 Jan 2016 07:48:53 +
with message-id 
and subject line Bug#809568: fixed in django-celery 3.1.17-3
has caused the Debian Bug report #809568,
regarding django-celery: FTBFS: ImportError: cannot import name get_cache
to be marked as done.

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

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


-- 
809568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-celery
Version: 3.1.17-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

django-celery-3.1.17/docs/changelog.rst:117: WARNING: Inline interpreted text 
or phrase reference start-string without end-string.
/django-celery-3.1.17/docs/reference/djcelery.backends.cache.rst:9: WARNING: 
autodoc: failed to import module u'djcelery.backends.cache'; the following 
exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 385, in 
import_object
__import__(self.modname)
  File "/django-celery-3.1.17/djcelery/backends/cache.py", line 8, in 
from django.core.cache import cache, get_cache
ImportError: cannot import name get_cache
/django-celery-3.1.17/docs/reference/djcelery.backends.database.rst:9: WARNING: 
autodoc: failed to import module u'djcelery.backends.database'; the following 
exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 385, in 
import_object
__import__(self.modname)
  File "/django-celery-3.1.17/djcelery/backends/database.py", line 7, in 

from ..models import TaskMeta, TaskSetMeta
  File "/django-celery-3.1.17/djcelery/models.py", line 30, in 
class TaskMeta(models.Model):
  File "/usr/lib/python2.7/dist-packages/django/db/models/base.py", line 94, in 
__new__
app_config = apps.get_containing_app_config(module)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 239, in 
get_containing_app_config
self.check_apps_ready()
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 124, in 
check_apps_ready
raise AppRegistryNotReady("Apps aren't loaded yet.")
AppRegistryNotReady: Apps aren't loaded yet.



...




==
ERROR: test_discovery_with_broken (djcelery.tests.test_discovery.TestDiscovery)
--
Traceback (most recent call last):
  File "/django-celery-3.1.17/tests/../djcelery/tests/test_discovery.py", line 
44, in test_discovery_with_broken
autodiscover()
  File "/django-celery-3.1.17/tests/../djcelery/loaders.py", line 184, in 
autodiscover
for app in apps.get_app_configs()])
  File "/django-celery-3.1.17/tests/../djcelery/loaders.py", line 209, in 
find_related_module
return importlib.import_module('{0}.{1}'.format(app, related_name))
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/django-celery-3.1.17/tests/someapp/tasks.py", line 3, in 
from django.db.models import get_model
ImportError: cannot import name get_model

==
ERROR: Failure: ImportError (cannot import name get_model)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 420, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/django-celery-3.1.17/tests/someapp/tests.py", line 6, in 
from someapp.tasks import SomeModelTask
  File "/django-celery-3.1.17/tests/someapp/tasks.py", line 3, in 
from django.db.models import get_model
ImportError: cannot import name get_model

--
Ran 57 tests in 0.555s

FAILED (errors=4)
nosetests /django-celery-3.1.17/tests/../djcelery/tests  --verbosity=1
Creating test database for alias 'default'...
Destroying test database for alias 'default'...
E: pybuild pybuild:274: test: plugin custom 

Processed: reassign 808289 to ftp.debian.org, severity of 808289 is normal ...

[Debian Bug Tracking System]

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

> reassign 808289 ftp.debian.org
Bug #808289 [src:upstart] proposed RM: upstart -- RoQA; unmaintained
Bug reassigned from package 'src:upstart' to 'ftp.debian.org'.
No longer marked as found in versions upstart/1.11-5.
Ignoring request to alter fixed versions of bug #808289 to the same values 
previously set
> severity 808289 normal
Bug #808289 [ftp.debian.org] proposed RM: upstart -- RoQA; unmaintained
Severity set to 'normal' from 'serious'
> retitle 808289 RM: upstart -- RoQA; unmaintained
Bug #808289 [ftp.debian.org] proposed RM: upstart -- RoQA; unmaintained
Changed Bug title to 'RM: upstart -- RoQA; unmaintained' from 'proposed RM: 
upstart -- RoQA; unmaintained'
> thanks
Stopping processing here.

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

Bug#808108: marked as done (ecere-sdk needs an update for giflib 5)

[Debian Bug Tracking System]

Your message dated Fri, 8 Jan 2016 22:05:41 -0500
with message-id <56907905.90...@gmail.com>
and subject line Problem fixed by 0.44.13
has caused the Debian Bug report #808108,
regarding ecere-sdk needs an update for giflib 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.)


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

Package: src:ecere-sdk
Version: 0.44.10-1
Severity: serious
Tags: sid stretch upstream patch

Missed that package when preparing the giflib transition. The package fails to 
build with giflib 5. It looks like the new upstream 0.44.12 has the required fix.


Building 2nd stage ecere...
make[2]: Entering directory '/«PKGBUILDDIR»/ecere'
/«PKGBUILDDIR»/ecere/src/gfx/bitmaps/GIFFormat.ec:32:31: warning: not enough 
arguments for function DGifOpen (2 given, expected 3)
/«PKGBUILDDIR»/ecere/src/gfx/bitmaps/GIFFormat.ec:108:10: warning: not enough 
arguments for function DGifCloseFile (1 given, expected 2)
obj/release.linux/GIFFormat.c: In function 
'__ecereMethod___ecereNameSpace__ecere__gfx__bitmaps__GIFFormat_Load':
obj/release.linux/GIFFormat.c:1033:25: error: too few arguments to function 
'DGifOpen'
 GifFileType * gifFile = DGifOpen(f, (void 
*)(__ecereNameSpace__ecere__gfx__bitmaps__ReadData));

 ^
obj/release.linux/GIFFormat.c:579:15: note: declared here
 GifFileType * DGifOpen(void * userPtr, InputFunc readFunc, int * Error);
   ^
obj/release.linux/GIFFormat.c:1117:1: error: too few arguments to function 
'DGifCloseFile'

 DGifCloseFile(gifFile);
 ^
obj/release.linux/GIFFormat.c:581:5: note: declared here
 int DGifCloseFile(GifFileType * GifFile, int * ErrorCode);
 ^
Makefile:1548: recipe for target 'obj/release.linux/GIFFormat.o' failed
make[2]: *** [obj/release.linux/GIFFormat.o] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»/ecere'
Makefile:202: recipe for target 'ecere' failed
make[1]: *** [ecere] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
--- End Message ---
--- Begin Message ---

Package: ecere-sdk
Version: 0.44.13-1

Handling different number of arguments for Giflib 5.1+ has been fixed 
upstream since 0.44.11.

0.44.13 has been uploaded to unstable and awaiting migration to testing.--- End Message ---

Bug#659810: marked as done (udev-discover: uninstallable on kfreebsd-*)

[Debian Bug Tracking System]

Your message dated Sat, 09 Jan 2016 03:35:46 +
with message-id 
and subject line Bug#659810: fixed in udev-discover 0.2.2-1.1
has caused the Debian Bug report #659810,
regarding udev-discover: uninstallable on kfreebsd-*
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.)


-- 
659810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev-discover
Version: 0.2.2-1
Severity: serious

Hi,

udev-discover is uninstallable on kfreebsd-* due to its dependency on
python-gudev, which does not exist on those architectures.

Regards,

Adam



--- End Message ---
--- Begin Message ---
Source: udev-discover
Source-Version: 0.2.2-1.1

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

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto  (supplier of updated 
udev-discover package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 29 Dec 2015 10:37:33 -0200
Source: udev-discover
Binary: udev-discover
Architecture: source
Version: 0.2.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: J. Félix Ontañón 
Changed-By: Herbert Parentes Fortes Neto 
Description:
 udev-discover - Sysfs browsing tool focused on helping udev users and 
developers
Closes: 659810
Changes:
 udev-discover (0.2.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control:
   - dh-python added to Build-Depends.
   - Bumped Standards-Version to 3.9.6.
   - set Architecture: linux-any. (Closes: #659810)
 Thanks Adam D. Barratt.
   * debian/rules:
   - using clean target in the new format. dh_clean added to clean
 debian dir.
Checksums-Sha1:
 12696d8415fd3c3a153042590a4f3e178e89c157 1811 udev-discover_0.2.2-1.1.dsc
 a1f683c702033df8f37f7b06a9fab991faa8b746 2972 
udev-discover_0.2.2-1.1.debian.tar.xz
Checksums-Sha256:
 31d8e2ba06ac249946b2c76ce93b51441c20f73230de19806d0ba1045702b594 1811 
udev-discover_0.2.2-1.1.dsc
 761710969bb33fb2daa98b6aa75f9fc8015704c61565d6c16c3af6b7301ac988 2972 
udev-discover_0.2.2-1.1.debian.tar.xz
Files:
 f33bf866d4149be451dfbbf1bcc95feb 1811 gnome optional 
udev-discover_0.2.2-1.1.dsc
 8fda60818b945d85f1b1002b8165a091 2972 gnome optional 
udev-discover_0.2.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWgzLNAAoJEN5juccE6+nvGhUP/0r9YcoQUoy0BNM9ZeM6rMwc
zY2wF6AJTD/Iseh5gipFfEz5ew3LQFXPCY7EIwtzrkJ9C7GWRxWXy+sqK96cVNFH
pzejv8Vazt4UBBrU+ykCdYCO84Te5P+2Zp/nBgBF9fdHGSudMacOrOnM4rzVGfCp
4tnMj9GfQzkY9kEVqgCm9UGD+uUAJWLCcsz63Nz4FCnuk97lpEp8SfWPCnI/l5HV
E1xOzwotSreUbxQJi6DyMpiIdtim3mG80q8FKoW6EVIiAjncCJPuN1gYlEItfvxK
ep85IhqqeXbqFh5lJ5nZKo2mWalnCXtu5pjIpq+stE3gBw6lYMUwDkVAJOpzhVD3
0t/5xYQRzUSwx+BEqg/TPpyExI3+YOYCLv4odKgd/GX0ADUzKLOpuoFl0Q/BF9gX
F17h74q3xDG67XENNBSSXuWa2HM6x0OOQmZZscjVKgFI82l+LYWnO9dkGSCBz+YX
jGXuKvJo4IQ7sv+m8zzbbSQSJDvfVAQRvlkxFEaAm8XLWZogD/qVIheQeLLVWUef
EcOzb6INbe+b1yEbz7OuXdK33uKgemku/1wiUAh77qQrAViRQlAJFG/GW1OJS26G
DAc5/DTWiVEmC9i+pzH5ay+NoPY9bmKwugY4lXu69tHgH3i9ko+YeJt98Z4Mbckz
2wpQc18TWoplmkGFFbFm
=z0KB
-END PGP SIGNATURE End Message ---

Bug#807019: unison2.40.102: Segmentation fault

[Ashley Hooper]

Is it at all feasible to downgrade the installed version of ocaml 4.01.x on
Stretch? I am reliant on Unison 2.32 (due to that being the most recent
version available for another device I use).

I'm only seeing the 4.02 version available in the repos.

$ apt-cache madison ocaml
 ocaml |   4.02.3-5 | http://ftp.nz.debian.org/debian stretch/main
amd64 Packages
 ocaml |   4.02.3-5 | http://ftp.nz.debian.org/debian stretch/main
Sources

Bug#810162: marked as done (rake assets precompile fails with compass-rails sprockets issue)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 09:58:38 +
with message-id 
and subject line Bug#810162: fixed in ruby-compass-rails 2.0.5-5
has caused the Debian Bug report #810162,
regarding rake assets precompile fails with compass-rails sprockets issue
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.)


-- 
810162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: diaspora
version: 0.5.4.0+debian-2
severity: grave
justification: fail to install

log for rake assets:precompile attached

praveen@pod:/usr/share/diaspora$ sudo -E -u diaspora bundle exec rake
assets:precompile --trace 2>&1 | tee /tmp/assets-precompile.log

Note: We get to this error after fixing #809755 (reproduced by
0.5.5.1+debian-1 in git)
** Invoke assets:precompile (first_time)
** Invoke assets:environment (first_time)
** Execute assets:environment
** Invoke environment (first_time)
** Execute environment
Rack::SSL is enabled
/usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:24: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:25: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data_strict.rb:42: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/backend.rb:331: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:24: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:25: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data_strict.rb:42: warning: Enumerator.new without a block is deprecated; use Object#to_enum
/usr/lib/ruby/vendor_ruby/i18n-inflector/backend.rb:331: warning: Enumerator.new without a block is deprecated; use Object#to_enum
** Execute assets:precompile
rake aborted!
ArgumentError: wrong number of arguments (3 for 2)
/usr/lib/ruby/vendor_ruby/sprockets/cache/file_store.rb:81:in `set'
/usr/lib/ruby/vendor_ruby/sprockets/sass_cache_store.rb:14:in `_store'
/usr/lib/ruby/vendor_ruby/sass/cache_stores/base.rb:51:in `store'
/usr/lib/ruby/vendor_ruby/sass/engine.rb:414:in `_to_tree'
/usr/lib/ruby/vendor_ruby/sass/engine.rb:309:in `to_tree'
/usr/lib/ruby/vendor_ruby/sass/engine.rb:343:in `_dependencies'
/usr/lib/ruby/vendor_ruby/sass/engine.rb:331:in `dependencies'
/usr/lib/ruby/vendor_ruby/compass-rails/patches/sass_importer.rb:36:in `evaluate'
/usr/lib/ruby/vendor_ruby/tilt/template.rb:103:in `render'
/usr/lib/ruby/vendor_ruby/sprockets/legacy_tilt_processor.rb:25:in `call'
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:75:in `call_processor'
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:57:in `block in call_processors'
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:56:in `reverse_each'
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:56:in `call_processors'
/usr/lib/ruby/vendor_ruby/sprockets/loader.rb:254:in `load_from_unloaded'
/usr/lib/ruby/vendor_ruby/sprockets/loader.rb:206:in `block in load'
/usr/lib/ruby/vendor_ruby/sprockets/loader.rb:397:in `fetch_asset_from_dependency_cache'
/usr/lib/ruby/vendor_ruby/sprockets/loader.rb:190:in `load'
/usr/lib/ruby/vendor_ruby/sprockets/cached_environment.rb:20:in `block in initialize'
/usr/lib/ruby/vendor_ruby/sprockets/cached_environment.rb:47:in `yield'
/usr/lib/ruby/vendor_ruby/sprockets/cached_environment.rb:47:in `load'
/usr/lib/ruby/vendor_ruby/sprockets/bundle.rb:23:in `block in call'
/usr/lib/ruby/vendor_ruby/sprockets/utils.rb:183:in `dfs'
/usr/lib/ruby/vendor_ruby/sprockets/bundle.rb:24:in `call'
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:75:in `call_processor'
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:57:in `block in call_processors'
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:56:in `reverse_each'

Bug#809289: marked as done (ruby-rufus-scheduler: FTBFS: (Failed tests) Rufus::Scheduler#occurrences(time0, time1) respects :times for repeat jobs)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 09:58:49 +
with message-id 
and subject line Bug#809289: fixed in ruby-rufus-scheduler 3.1.10-2
has caused the Debian Bug report #809289,
regarding ruby-rufus-scheduler: FTBFS: (Failed tests) 
Rufus::Scheduler#occurrences(time0, time1) respects :times for repeat jobs
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.)


-- 
809289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rufus-scheduler
Version: 3.1.10-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,

ruby-rufus-scheduler fails to build from source in unstable/amd64:

  [..]
  
  Pending: (Failures listed here are expected and do not affect your suite's 
status)
  
1) Rufus::Scheduler#at accepts an ActiveSupport time thinggy
   # Not yet implemented
   # ./spec/schedule_at_spec.rb:143
  
2) Rufus::Scheduler#schedule_in accepts an ActiveSupport .from_now thinggy
   # Not yet implemented
   # ./spec/schedule_in_spec.rb:73
  
  Failures:
  
1) Rufus::Scheduler#occurrences(time0, time1) respects :times for repeat 
jobs
   Failure/Error: expect(h[j0].size).to eq(6)
 
 expected: 6
  got: 5
 
 (compared using ==)
   # ./spec/scheduler_spec.rb:610:in `block (3 levels) in '
  
  Finished in 3 minutes 24.2 seconds (files took 0.16485 seconds to load)
  346 examples, 1 failure, 2 pending
  
  Failed examples:
  
  rspec ./spec/scheduler_spec.rb:601 # Rufus::Scheduler#occurrences(time0, 
time1) respects :times for repeat jobs
  
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20151229004334.Bx3mvx0pKv/ruby-rufus-scheduler-3.1.10/debian/ruby-rufus-scheduler
 returned exit code 1
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ruby-rufus-scheduler.3.1.10-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-rufus-scheduler
Source-Version: 3.1.10-2

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

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated 
ruby-rufus-scheduler package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Jan 2016 18:58:10 +0530
Source: ruby-rufus-scheduler
Binary: ruby-rufus-scheduler
Architecture: source all
Version: 3.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Balasankar C 
Description:
 ruby-rufus-scheduler - job scheduler for Ruby
Closes: 809289
Changes:
 ruby-rufus-scheduler (3.1.10-2) unstable; urgency=medium
 .
   * Disable tests that caused random FTBFS (Closes: #809289)
 - Need to investigate more.
Checksums-Sha1:
 576c497d0256d4f63ea44ec91c44210747caa032 1824 ruby-rufus-scheduler_3.1.10-2.dsc
 c89b9eed75e7e1a4b37d5cc7fd2e0bc22ea726ee 2600 
ruby-rufus-scheduler_3.1.10-2.debian.tar.xz
 54259b2518f3f5ddfb286f5a4033f9b79d2428bc 36426 
ruby-rufus-scheduler_3.1.10-2_all.deb
Checksums-Sha256:
 b4e8a446b7cf30e70fa9a0d80736c515b69bb0291e3d5b13573626d3d97fa8bd 1824 
ruby-rufus-scheduler_3.1.10-2.dsc
 32797f7c595482b4866122dbad1b5f3d01ef5abd22853001e296cda59a11d564 2600 
ruby-rufus-scheduler_3.1.10-2.debian.tar.xz
 b7affc278685f6d05bf113a0af432057742a7e74fff206ad467cdecf57e64965 36426 
ruby-rufus-scheduler_3.1.10-2_all.deb
Files:
 37d421c828c43264f5025d7060d14c95 1824 ruby 

Bug#810129: marked as done (linux-source-4.3 and linux-grsec-source-4.3: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 09:51:31 +
with message-id 
and subject line Bug#810129: fixed in linux-grsec 4.3.3-5+grsec201601051958+1
has caused the Debian Bug report #810129,
regarding linux-source-4.3 and linux-grsec-source-4.3: error when trying to 
install together
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.)


-- 
810129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-grsec-source-4.3,linux-source-4.3
Version: linux-grsec-source-4.3/4.3.3-5+grsec201512282134+1
Version: linux-source-4.3/4.3.3-5
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-06
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package xz-utils.
(Reading database ... 10940 files and directories currently installed.)
Preparing to unpack .../xz-utils_5.1.1alpha+20120614-2.1_amd64.deb ...
Unpacking xz-utils (5.1.1alpha+20120614-2.1) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.25.90.20160101-1_amd64.deb ...
Unpacking binutils (2.25.90.20160101-1) ...
Selecting previously unselected package linux-grsec-source-4.3.
Preparing to unpack 
.../linux-grsec-source-4.3_4.3.3-5+grsec201512282134+1_all.deb ...
Unpacking linux-grsec-source-4.3 (4.3.3-5+grsec201512282134+1) ...
Selecting previously unselected package linux-source-4.3.
Preparing to unpack .../linux-source-4.3_4.3.3-5_all.deb ...
Unpacking linux-source-4.3 (4.3.3-5) ...
dpkg: error processing archive 
/var/cache/apt/archives/linux-source-4.3_4.3.3-5_all.deb (--unpack):
 trying to overwrite '/usr/src/linux-source-4.3.tar.xz', which is also in 
package linux-grsec-source-4.3 4.3.3-5+grsec201512282134+1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-source-4.3_4.3.3-5_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/src/linux-source-4.3.tar.xz

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: linux-grsec
Source-Version: 4.3.3-5+grsec201601051958+1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated linux-grsec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Jan 2016 09:52:41 +0100
Source: linux-grsec
Binary: linux-grsec-source-4.3 linux-grsec-support-4.3.0-1 
linux-headers-4.3.0-1-common-grsec linux-image-4.3.0-1-grsec-amd64 

Processed: reassign 810121 to os-prober, forcibly merging 788062 810121

[Debian Bug Tracking System]

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

> reassign 810121 os-prober
Bug #810121 [src:linux] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Bug reassigned from package 'src:linux' to 'os-prober'.
No longer marked as found in versions linux/3.16.7-ckt11-1+deb8u5.
Ignoring request to alter fixed versions of bug #810121 to the same values 
previously set
> forcemerge 788062 810121
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Severity set to 'critical' from 'important'
Marked as found in versions os-prober/1.65.
Added tag(s) pending.
Merged 788062 810121
> thanks
Stopping processing here.

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

Bug#810330: marked as done (pylint-django: FTBFS: ImportError: cannot import name 'YES')

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 11:47:24 +
with message-id 
<1452253644.1403546.486410298.5440f...@webmail.messagingengine.com>
and subject line Re: Bug#810330: Acknowledgement (pylint-django: FTBFS: 
ImportError: cannot import name 'YES')
has caused the Debian Bug report #810330,
regarding pylint-django: FTBFS: ImportError: cannot import name 'YES'
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.)


-- 
810330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint-django
Version: 0.6-2
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,

pylint-django fails to build from source in unstable/amd64:

  [..]

  
  ==
  ERROR: pylint_django (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: pylint_django
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
  __import__(name)
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/__init__.py",
 line 3, in 
  from pylint_django import plugin
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/plugin.py",
 line 3, in 
  from pylint_django.augmentations import apply_augmentations
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/augmentations/__init__.py",
 line 11, in 
  from pylint_django.utils import node_is_subclass, PY3
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/utils.py",
 line 3, in 
  from astroid.bases import YES, Instance
  ImportError: cannot import name 'YES'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build;
 python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned 
exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
dupe, silly mail client

> 
> On Fri, 8 Jan 2016, at 11:45 AM, Debian Bug Tracking System wrote:
> > Thank you for filing a new Bug report with Debian.
> > 
> > This is an automatically generated reply to let you know your message
> > has been received.
> > 
> > Your message is being forwarded to the package maintainers and other
> > interested parties for their attention; they will reply in due course.
> > 
> > As you requested using X-Debbugs-CC, your message was also forwarded to
> >   reproducible-bui...@lists.alioth.debian.org
> > (after having been given a Bug report number, if it did not have one).
> > 
> > Your message has been sent to the package maintainer(s):
> >  Debian Python Modules Team 
> > 
> > If you wish to submit further information on this problem, please
> > send it to 810...@bugs.debian.org.
> > 
> > Please do not send mail to ow...@bugs.debian.org unless you wish
> > to report a problem with the Bug-tracking system.
> > 
> > -- 
> > 810330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810330
> > Debian Bug Tracking System
> > Contact ow...@bugs.debian.org with problems
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   ` End Message ---

Bug#810353: checkbox-ng: fails to upgrade from 'testing' - trying to overwrite /usr/bin/checkbox

[Andreas Beckmann]

Package: checkbox-ng
Version: 0.23-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
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...):

  Preparing to unpack .../checkbox-ng_0.23-1_all.deb ...
  Unpacking checkbox-ng (0.23-1) over (0.20.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/checkbox-ng_0.23-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/checkbox', which is also in package 
python3-checkbox-ng 0.20.1-1
  Preparing to unpack .../python3-checkbox-ng_0.23-1_all.deb ...
  Unpacking python3-checkbox-ng (0.23-1) over (0.20.1-1) ...
  Processing triggers for libc-bin (2.21-6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/checkbox-ng_0.23-1_all.deb


cheers,

Andreas


checkbox-ng_0.23-1.log.gz
Description: application/gzip

Bug#810351: libuim-plugins: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/uim/plugin/libuim-custom-enabler.so

[Andreas Beckmann]

Package: libuim-plugins
Version: 1:1.8.6-15exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
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 libuim-plugins.
  (Reading database ... 
(Reading database ... 7570 files and directories currently installed.)
  Preparing to unpack .../libuim-plugins_1%3a1.8.6-15exp1_amd64.deb ...
  Unpacking libuim-plugins (1:1.8.6-15exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libuim-plugins_1%3a1.8.6-15exp1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/uim/plugin/libuim-custom-enabler.so', which is also 
in package libuim-data 1:1.8.6-15
  Preparing to unpack .../uim-utils_1%3a1.8.6-15exp1_amd64.deb ...
  Unpacking uim-utils (1:1.8.6-15exp1) over (1:1.8.6-15) ...
  Preparing to unpack .../libuim-data_1%3a1.8.6-15exp1_all.deb ...
  Unpacking libuim-data (1:1.8.6-15exp1) over (1:1.8.6-15) ...
  Preparing to unpack .../uim-look_1%3a1.8.6-15exp1_all.deb ...
  Unpacking uim-look (1:1.8.6-15exp1) over (1:1.8.6-15) ...
  Preparing to unpack .../uim-common_1%3a1.8.6-15exp1_all.deb ...
  Unpacking uim-common (1:1.8.6-15exp1) over (1:1.8.6-15) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libuim-plugins_1%3a1.8.6-15exp1_amd64.deb


cheers,

Andreas


uim-look_1:1.8.6-15exp1.log.gz
Description: application/gzip

Processed: reassign 810084 to ftp.debian.org

[Debian Bug Tracking System]

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

> reassign 810084 ftp.debian.org
Bug #810084 [websvn] RM: websvn (RoQA; unmaintained, rc-buggy, inactive 
upstream, alternatives exist)
Bug reassigned from package 'websvn' to 'ftp.debian.org'.
No longer marked as found in versions websvn/2.3.3-1.3.
Ignoring request to alter fixed versions of bug #810084 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> found 810105  0.5.1.0-4
Bug #810105 [haskell-cabal-helper] ghc-mod: Looks for cabal-helper-wrapper 
binary in wrong place
There is no source info for the package 'haskell-cabal-helper' at version 
'0.5.1.0-4' with architecture ''
Unable to make a source version for version '0.5.1.0-4'
Marked as found in versions 0.5.1.0-4.
> thanks
Stopping processing here.

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

Bug#793465: libuser/1:0.60~dfsg-1.2 fix for CVE-2015-3245 and CVE-2015-3246

[Holger Levsen]

Hi Ghe, hi Tzafrir,

what are your plans on this bug? The bug has a patch, but you could also 
upload a new upstream version to fix this.

Currently this bug kicked out libuser from testing, which in turn prevents 
usermode from being in testing, which in turn prevents mock from being in 
testing, which is why I am concerned as I would like to run a recent mock 
version from jessie-backports…


cheers,
Holger


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

Processed: severity of 760695 is serious

[Debian Bug Tracking System]

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

> severity 760695 serious
Bug #760695 [tinc-gui] tinc-gui: Please update to use wxpython3.0
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 810105 - pending
Bug #810105 [ghc-mod] ghc-mod: Looks for cabal-helper-wrapper binary in wrong 
place
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#810342: taskd: fails to install: chown: cannot access '/var/lib/taskd/orgs': No such file or directory

[Andreas Beckmann]

Package: taskd
Version: 1.1.0+dfsg-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 taskd.
  (Reading database ... 
(Reading database ... 7411 files and directories currently installed.)
  Preparing to unpack .../taskd_1.1.0+dfsg-1_amd64.deb ...
  Unpacking taskd (1.1.0+dfsg-1) ...
  Processing triggers for systemd (228-3) ...
  Setting up taskd (1.1.0+dfsg-1) ...
  chown: cannot access '/var/lib/taskd/orgs': No such file or directory
  dpkg: error processing package taskd (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (228-3) ...
  Errors were encountered while processing:
   taskd


cheers,

Andreas

Bug#810105: Bug#809763: cabal-helper: no binary in cabal-helper package

[Sven Bartscher]

Control: reassign -1 haskell-cabal-helper

On Mon, 4 Jan 2016 16:29:22 +0100 Sven Bartscher
 wrote:
> On Sun, 3 Jan 2016 20:52:52 +0100
> Tomas Janousek  wrote:
> > Also, ghc-mod seems to expect cabal-helper in /usr/libexec:
> > 
> > > $ ghc-mod list
> > > ghc-mod: Could not find $libexecdir/cabal-helper-wrapper
> > > 
> > > If you are a developer set the environment variable
> > > `cabal_helper_libexecdir' to override $libexecdir[1]. The following will
> > > work in the cabal-helper source tree:
> > > 
> > > $ export cabal_helper_libexecdir=$PWD/dist/build/cabal-helper-wrapper
> > > 
> > > [1]: /usr/libexec
> > > 
> > > If you don't know what I'm talking about something went wrong with your
> > > installation. Please report this problem here:
> > > 
> > > https://github.com/DanielG/cabal-helper/issues  
> > 
> > Shall I open another bug or can you check that as well?
> 
> It would be good if you open another report for ghc-mod, so it won't
> migrate before its libexecdir is set to /usr/lib.

Searching through the code revealed, that the code for finding the
executable is actually in haskell-cabal-helper. *reassign*

Regards
Sven


pgpyOlt8phNDU.pgp
Description: Digitale Signatur von OpenPGP

Processed: Re: Bug#809763: cabal-helper: no binary in cabal-helper package

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 haskell-cabal-helper
Bug #810105 [ghc-mod] ghc-mod: Looks for cabal-helper-wrapper binary in wrong 
place
Bug reassigned from package 'ghc-mod' to 'haskell-cabal-helper'.
No longer marked as found in versions ghc-mod/5.4.0.0-1.
Ignoring request to alter fixed versions of bug #810105 to the same values 
previously set

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

Bug#810360: ugene: switch B-D to libprocps-dev

[Andreas Beckmann]

Package: ugene
Version: 1.19.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

libprocps4-dev is history, please switch to libprocps-dev.


Andreas

Bug#810336: wmanager: fails to install: post-installation script returned error exit status 1

[Andreas Beckmann]

Package: wmanager
Version: 0.2.1-13
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 wmanager.
  (Reading database ... 
(Reading database ... 9668 files and directories currently installed.)
  Preparing to unpack .../wmanager_0.2.1-13_amd64.deb ...
  Unpacking wmanager (0.2.1-13) ...
  Setting up wmanager (0.2.1-13) ...
  dpkg: error processing package wmanager (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   wmanager


cheers,

Andreas


wmanager_0.2.1-13.log.gz
Description: application/gzip

Bug#810343: minidlna: fails to install: chown: invalid user: 'minidlna:minidlna'

[Andreas Beckmann]

Package: minidlna
Version: 1.1.5+dfsg-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 minidlna.
  (Reading database ... 
(Reading database ... 7938 files and directories currently installed.)
  Preparing to unpack .../minidlna_1.1.5+dfsg-1_amd64.deb ...
  Unpacking minidlna (1.1.5+dfsg-1) ...
  Processing triggers for systemd (228-3) ...
  Setting up minidlna (1.1.5+dfsg-1) ...
  chown: invalid user: 'minidlna:minidlna'
  dpkg: error processing package minidlna (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (228-3) ...
  Errors were encountered while processing:
   minidlna


cheers,

Andreas


minidlna_1.1.5+dfsg-1.log.gz
Description: application/gzip

Processed: R crashes with "Illegal instruction" on mips

[Debian Bug Tracking System]

Processing control commands:

> affects -1 r-cran-ncdf4 r-cran-afex r-cran-coin r-cran-scales r-cran-ape 
> r-cran-rms r-cran-timeseries r-cran-dosefinding r-cran-maps r-cran-statmod
Bug #810357 [r-base-core] R crashes with "Illegal instruction" on mips
Added indication that 810357 affects r-cran-ncdf4, r-cran-afex, r-cran-coin, 
r-cran-scales, r-cran-ape, r-cran-rms, r-cran-timeseries, r-cran-dosefinding, 
r-cran-maps, and r-cran-statmod

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

Bug#810357: R crashes with "Illegal instruction" on mips

[Sébastien Villemot]

Package: r-base-core
Version: 3.2.3-1
Severity: grave
Control: affects -1 r-cran-ncdf4 r-cran-afex r-cran-coin r-cran-scales 
r-cran-ape r-cran-rms r-cran-timeseries r-cran-dosefinding r-cran-maps 
r-cran-statmod

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Dirk,

R crashes at startup with an "Illegal instruction" (tested on minkus, the mips
porterbox):

  (sid_mips-dchroot)sebastien@minkus:~$ R
  Illegal instruction

Here is a backtrace:

#0  machar (ibeta=0x77fc3bd0 , it=0x77fc3bd4 
, irnd=0x77fc3bd8 , ngrd=0x77fc3bdc 
, machep=0x77fc3be0 ,
negep=0x77fc3be4 , iexp=0x77fc3be8 , 
minexp=0x77fc3bec , maxexp=0x77fc3bf0 , 
eps=0x77fc3bf8 ,
epsneg=0x77fc3c00 , xmin=0x77fc3c08 , 
xmax=0x77fc3c10 ) at platform.c:3199
#1  0x77d1a570 in Init_R_Machine (rho=0x43054c) at platform.c:61
#2  0x77d1b48c in Init_R_Variables (rho=0x43054c) at platform.c:198
#3  0x77cf0198 in setup_Rmainloop () at main.c:840
#4  0x77cf0dfc in Rf_mainloop () at main.c:1012
#5  0x00400a00 in main (ac=1, av=0x7fff6574) at Rmain.c:29
#6  0x779b9f58 in __libc_start_main () from /lib/mips-linux-gnu/libc.so.6
#7  0x00400870 in _ftext ()

Incidentally, all CRAN packages FTBFS on mips (see above for the list of
currently affected packages).

Cheers,

- --
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWj7+KAAoJECzs6TUOzr5KeAMQAJb9i2A502nK2f0EoN0+ReR7
hJJlC8wBv0L2edlCjV6sE45Fa+bkpHrazC8JDoJpTeA6pcJ6HnzxAAOFNdoosHYk
IwPsOhQsdnlYxAYNBuSwTJHoTNBGBDkvMEvPrh6LuOvUPYPE42by5R3pO69cjfB2
+F0QzO0dCr4Abi4tBBW6T+4LvzhFRkVK1b+M7c+ZO6k7fSS5sqoZdbmpXSP00wWh
0WbhjmjDtQR9xd1ngAxpOUA7RHrBB3PCDagMF9cqo7UmjYFPcL8+Y5YeEuslnrPN
Ijf1p1SzWaFeBI2Hm+OPFU/6pCCEj/TwPKn+5VYSBIkFMe3HyUg+L1US1Vq3m3ca
+cAySL324DCG2CAmCHpotW4XwPzEGopKJI7VnNZYmlC7pIOi8gU4oPIN8NcysoCS
c7BcyEURBoM3D/lzMmQc+Iw38T1emQEFtrMMkwNVcXTdWjPOEkNn6605Hs57tiM0
OqTxgL8c779UUzdfv9QWSKBYfgqwNdTdORq9QDp5VeTLdcGRVslbRamozP3GanEp
HMVFLct4cvLdf0gXfpAaGTC0lK61kHQZuzTktoPZqx8PcC6Ib29WoxJisb42SIcR
ZwoKb26AKYoh/ksXvB4fW8Rg6pthsfm8iW4AXluknu6loaAbi3KpksbJNJtcY+fu
swmq6f2IybsfIXjMFYIh
=5kLR
-END PGP SIGNATURE-

Bug#810357: R crashes with "Illegal instruction" on mips

[Dirk Eddelbuettel]

Hi Seb,

On 8 January 2016 at 14:54, Sébastien Villemot wrote:
| Package: r-base-core
| Version: 3.2.3-1
| Severity: grave

That will deprive a couple (ten or hundred) thousand users of R because ...

| Control: affects -1 r-cran-ncdf4 r-cran-afex r-cran-coin r-cran-scales 
r-cran-ape r-cran-rms r-cran-timeseries r-cran-dosefinding r-cran-maps 
r-cran-statmod
| 
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA256
| 
| Hi Dirk,
| 
| R crashes at startup with an "Illegal instruction" (tested on minkus, the mips
| porterbox):
| 
|   (sid_mips-dchroot)sebastien@minkus:~$ R
|   Illegal instruction
| 
| Here is a backtrace:
| 
| #0  machar (ibeta=0x77fc3bd0 , it=0x77fc3bd4 
, irnd=0x77fc3bd8 , ngrd=0x77fc3bdc 
, machep=0x77fc3be0 ,
| negep=0x77fc3be4 , iexp=0x77fc3be8 
, minexp=0x77fc3bec , maxexp=0x77fc3bf0 
, eps=0x77fc3bf8 ,
| epsneg=0x77fc3c00 , xmin=0x77fc3c08 
, xmax=0x77fc3c10 ) at platform.c:3199
| #1  0x77d1a570 in Init_R_Machine (rho=0x43054c) at platform.c:61
| #2  0x77d1b48c in Init_R_Variables (rho=0x43054c) at platform.c:198
| #3  0x77cf0198 in setup_Rmainloop () at main.c:840
| #4  0x77cf0dfc in Rf_mainloop () at main.c:1012
| #5  0x00400a00 in main (ac=1, av=0x7fff6574) at Rmain.c:29
| #6  0x779b9f58 in __libc_start_main () from /lib/mips-linux-gnu/libc.so.6
| #7  0x00400870 in _ftext ()
| 
| Incidentally, all CRAN packages FTBFS on mips (see above for the list of
| currently affected packages).

... neither I not R Core have mips access, as this may become
release-critical and block R.  :-/

Dirk


| Cheers,
| 
| - --
|  .''`.Sébastien Villemot
| : :' :Debian Developer
| `. `' http://sebastien.villemot.name
|   `-  GPG Key: 4096R/381A7594
| 
| -BEGIN PGP SIGNATURE-
| Version: GnuPG v1
| 
| iQIcBAEBCAAGBQJWj7+KAAoJECzs6TUOzr5KeAMQAJb9i2A502nK2f0EoN0+ReR7
| hJJlC8wBv0L2edlCjV6sE45Fa+bkpHrazC8JDoJpTeA6pcJ6HnzxAAOFNdoosHYk
| IwPsOhQsdnlYxAYNBuSwTJHoTNBGBDkvMEvPrh6LuOvUPYPE42by5R3pO69cjfB2
| +F0QzO0dCr4Abi4tBBW6T+4LvzhFRkVK1b+M7c+ZO6k7fSS5sqoZdbmpXSP00wWh
| 0WbhjmjDtQR9xd1ngAxpOUA7RHrBB3PCDagMF9cqo7UmjYFPcL8+Y5YeEuslnrPN
| Ijf1p1SzWaFeBI2Hm+OPFU/6pCCEj/TwPKn+5VYSBIkFMe3HyUg+L1US1Vq3m3ca
| +cAySL324DCG2CAmCHpotW4XwPzEGopKJI7VnNZYmlC7pIOi8gU4oPIN8NcysoCS
| c7BcyEURBoM3D/lzMmQc+Iw38T1emQEFtrMMkwNVcXTdWjPOEkNn6605Hs57tiM0
| OqTxgL8c779UUzdfv9QWSKBYfgqwNdTdORq9QDp5VeTLdcGRVslbRamozP3GanEp
| HMVFLct4cvLdf0gXfpAaGTC0lK61kHQZuzTktoPZqx8PcC6Ib29WoxJisb42SIcR
| ZwoKb26AKYoh/ksXvB4fW8Rg6pthsfm8iW4AXluknu6loaAbi3KpksbJNJtcY+fu
| swmq6f2IybsfIXjMFYIh
| =5kLR
| -END PGP SIGNATURE-

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#810331: ussp-push: FTBFS: obex_main.c:200:27: error: 'OBEX_TRANS_CUST' undeclared

[Chris Lamb]

Source: ussp-push
Version: 0.11-2
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,

ussp-push fails to build from source in unstable/amd64:

  [..]

  Making all in src
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160108113958.fcrIUpMzLm/ussp-push-0.11/src'
  gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c -o obex_main.o 
obex_main.c
  obex_main.c: In function '__obex_connect':
  obex_main.c:200:27: error: 'OBEX_TRANS_CUST' undeclared (first use in this 
function)
if (!(handle = OBEX_Init(OBEX_TRANS_CUST, obex_event, 0))) {
 ^
  obex_main.c:200:27: note: each undeclared identifier is reported only once 
for each function it appears in
  obex_main.c: In function 'obex_push':
  obex_main.c:364:3: warning: implicit declaration of function 
'OBEX_CharToUnicode' [-Wimplicit-function-declaration]
 OBEX_CharToUnicode((uint8_t *) namebuf, (uint8_t *) name, name_len);
 ^
  Makefile:404: recipe for target 'obex_main.o' failed
  make[4]: *** [obex_main.o] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160108113958.fcrIUpMzLm/ussp-push-0.11/src'
  Makefile:397: recipe for target 'all-recursive' failed
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160108113958.fcrIUpMzLm/ussp-push-0.11'
  Makefile:329: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160108113958.fcrIUpMzLm/ussp-push-0.11'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:9: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160108113958.fcrIUpMzLm/ussp-push-0.11'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ussp-push.0.11-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#810348: node-mocks-http: unsatisfiable Depends: node-mime (= 1.3.4)

[Andreas Beckmann]

Package: node-mocks-http
Version: 1.4.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

There is node-mime (1.3.4-1) available, though.


cheers,

Andreas

Bug#810069: marked as done (elektra: FTBFS During Rebuild For Python3.5 Transition)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 08:57:08 -0500
with message-id <1477646.JmN89xAMDO@kitterma-e6430>
and subject line Re: Bug#810069: elektra: FTBFS During Rebuild For Python3.5 
Transition
has caused the Debian Bug report #810069,
regarding elektra: FTBFS During Rebuild For Python3.5 Transition
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.)


-- 
810069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elektra
Version: 0.8.14-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

While rebuilding elektra in a chroot modified so that python3.5 is the default
python3, the follosing test failure ocurred:

31/92 Test #31: testmod_python2 ..***Failed0.07 sec
PYTHON  TESTS
==

Testing simple variable passing...
There are 1 warnings
buffer is: warnings/#00
number: 11
description: open of plugin returned unsuccessfully (reason contains plugin, 
see other warnings for details)
ingroup: kdb
module: 
file: /home/test/elektra-0.8.14/src/libelektra/plugin.c
line: 296
reason: python2
reason: 
reason: 
/home/test/elektra-0.8.14/src/plugins/python2/../python/testmod_python.c:52: 
error in test_variable_passing: warnings in kdbOpen for plugin python2
number: 111
description: : python error
ingroup: : plugin
module: : python
at: /home/test/elektra-0.8.14/src/plugins/python2/../python/python.cpp:255
reason: : Unable to import kdb module
mountpoint: : 
configfile: : 
/home/test/elektra-0.8.14/src/plugins/python2/../python/testmod_python.c:52: 
error in test_variable_passing: error in kdbOpen for plugin python2
/home/test/elektra-0.8.14/src/plugins/python2/../python/testmod_python.c:52: 
fatal in test_variable_passing: could not open python2 plugin

Since this appears to be related to python2 and not python3 I don't think it
is due to the changed python3 version.

Scott K
--- End Message ---
--- Begin Message ---
On Thursday, January 07, 2016 04:39:09 PM Pino Toscano wrote:
> tag 810069 + moreinfo
> thanks
> 
> In data mercoledì 6 gennaio 2016 03:46:12, Scott Kitterman ha scritto:
> > Source: elektra
> > Version: 0.8.14-5
> > Severity: serious
> > Justification: fails to build from source (but built successfully in the
> > past)
> > 
> > While rebuilding elektra in a chroot modified so that python3.5 is the
> > default python3, the follosing test failure ocurred:
...
> > Since this appears to be related to python2 and not python3 I don't think
> > it is due to the changed python3 version.
> 
> Please provide a full log of the build, including all the installed
> packages and their versions. Just tried rebuilding elektra in a clean
> chroot (using builder), and it build fine.
> 
> Thanks,

I can't replicate it either.  I had test built a large number of packages in 
that chroot as part of the preparations for the transition, so I probably 
screwed something up.  Sorry for the bother and thanks for the quick reply,

Scott K

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

Bug#810329: pylint-django: FTBFS: ImportError: cannot import name 'YES'

[Chris Lamb]

Source: pylint-django
Version: 0.6-2
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,

pylint-django fails to build from source in unstable/amd64:

  [..]

  
  ==
  ERROR: pylint_django (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: pylint_django
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
  __import__(name)
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/__init__.py",
 line 3, in 
  from pylint_django import plugin
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/plugin.py",
 line 3, in 
  from pylint_django.augmentations import apply_augmentations
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/augmentations/__init__.py",
 line 11, in 
  from pylint_django.utils import node_is_subclass, PY3
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/utils.py",
 line 3, in 
  from astroid.bases import YES, Instance
  ImportError: cannot import name 'YES'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build;
 python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned 
exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


pylint-django.0.6-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#810330: pylint-django: FTBFS: ImportError: cannot import name 'YES'

[Chris Lamb]

Source: pylint-django
Version: 0.6-2
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,

pylint-django fails to build from source in unstable/amd64:

  [..]

  
  ==
  ERROR: pylint_django (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: pylint_django
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
  __import__(name)
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/__init__.py",
 line 3, in 
  from pylint_django import plugin
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/plugin.py",
 line 3, in 
  from pylint_django.augmentations import apply_augmentations
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/augmentations/__init__.py",
 line 11, in 
  from pylint_django.utils import node_is_subclass, PY3
File 
"/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build/pylint_django/utils.py",
 line 3, in 
  from astroid.bases import YES, Instance
  ImportError: cannot import name 'YES'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/home/lamby/temp/cdt.20160108114012.n6qebSTNBJ/pylint-django-0.6/.pybuild/pythonX.Y_3.5/build;
 python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned 
exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: tagging 808491, found 808874 in 20151023, tagging 809130, found 733693 in 0.6.1-6, tagging 733693 ...

[Debian Bug Tracking System]

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

> tags 808491 + sid stretch
Bug #808491 {Done: Gert Wollny } [src:insighttoolkit4] 
insighttoolkit4: FTBFS when build against gdcm-2.6.1
Added tag(s) sid and stretch.
> found 808874 20151023
Bug #808874 [src:debian-installer] debian-installer: FTBFS on i386: 586 vs. 686
Marked as found in versions debian-installer/20151023.
> tags 809130 + sid wontfix
Bug #809130 [src:ogre-1.8] ogre-1.8: FTBFS: "The following REQUIRED packages 
could NOT be located on your system: freetype"
Added tag(s) sid and wontfix.
> found 733693 0.6.1-6
Bug #733693 [ipkungfu] please do not depend on module-init-tools
Marked as found in versions ipkungfu/0.6.1-6.
> tags 733693 + sid stretch
Bug #733693 [ipkungfu] please do not depend on module-init-tools
Added tag(s) sid and stretch.
> tags 809225 + sid stretch
Bug #809225 [unison2.32.52] Segfault when using unison 2.32.52 in sid (both 
text and gtk versions)
Added tag(s) stretch and sid.
> tags 805835 + sid
Bug #805835 {Done: Michael Hanke } [src:voxbo] voxbo: Fails to 
build with GSL 2
Added tag(s) sid.
> tags 805814 + sid
Bug #805814 {Done: Michael Hanke } [src:mrtrix] mrtrix: Fails 
to build with GSL 2
Added tag(s) sid.
> found 810165 2.1.0-2
Bug #810165 [ants] ants: Please update dependency on libpng-dev
Marked as found in versions ants/2.1.0-2.
> found 802454 1.1.2-1
Bug #802454 [graphite-api] graphite-api: fails to purge: rm: cannot remove 
'/var/log/graphite-api /var/lib/graphite-api': No such file or directory
Marked as found in versions graphite-api/1.1.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
733693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733693
802454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802454
805814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805814
805835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805835
808491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808491
808874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808874
809130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809130
809225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809225
810165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#775118: marked as done (mock: makes dpkg explode after upgrade from sid to experimental)

[Debian Bug Tracking System]

Your message dated Fri, 8 Jan 2016 14:25:17 +0100
with message-id <201601081425.18503.hol...@layer-acht.org>
and subject line a typo prevented the bts from automatically closing this bug
has caused the Debian Bug report #775118,
regarding mock: makes dpkg explode after upgrade from sid to experimental
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', but after the upgrade to eperimental the
system is broken.

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

  Selecting previously unselected package mock.
  Preparing to unpack .../archives/mock_1.1.33-1_all.deb ...
  Unpacking mock (1.1.33-1) ...

  Setting up mock (1.1.33-1) ...

  Preparing to unpack .../archives/mock_1.2.3-1_all.deb ...
  Unpacking mock (1.2.3-1) over (1.1.33-1) ...
  Setting up mock (1.2.3-1) ...
  Installing new version of config file /etc/mock/epel-5-i386.cfg ...
[...]
  Installing new version of config file /etc/mock/site-defaults.cfg ...
  Installing new version of config file /etc/pam.d/mock ...
  dpkg-statoverride: warning: --update given but /var/lib/mock does not exist
  dpkg-statoverride: warning: --update given but /var/cache/mock does not exist

  The following NEW packages will be installed:
libapt-pkg4.15
  The following packages will be upgraded:
apt dash findutils grep insserv libdbus-1-3 libsystemd0 libudev1 systemd
systemd-sysv udev
  11 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
  Need to get 7522 kB of archives.
  After this operation, 7868 kB of additional disk space will be used.
[...]
  debconf: delaying package configuration, since apt-utils is not installed
  Fetched 7522 kB in 0s (39.8 MB/s)
  E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file 
or directory)
  dpkg: unrecoverable fatal error, aborting:
   unknown group 'mock' in statoverride file
  E: Sub-process /usr/bin/dpkg returned an error code (2)


The postinst script uses two different variables for the group name:
MOCK and GROUP, but only one of them is defined!


cheers,

Andreas


mock_1.2.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
version: 1.2.3-1.1

 mock (1.2.3-1.1) experimental; urgency=medium
 .
   * Non-maintainer upload.
   * Fix debian/postinst by adding the required dirs and using the correct
 variable. (Closes: ##775118) - patch by Guido Günther.


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

Processed: tagging 809970, user debian...@lists.debian.org, usertagging 809970, affects 809970

[Debian Bug Tracking System]

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

> tags 809970 + sid stretch
Bug #809970 [linphone] [linphone] fails to install
Added tag(s) sid and stretch.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 809970 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 809970 + linphone-nogtk
Bug #809970 [linphone] [linphone] fails to install
Added indication that 809970 affects linphone-nogtk
> thanks
Stopping processing here.

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

Bug#810354: libvisp-core-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/x86_64-linux-gnu/visp/vpFeaturePointPolar.h

[Andreas Beckmann]

Package: libvisp-core-dev
Version: 3.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libvisp-dev

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
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 libvisp-core-dev:amd64.
  Preparing to unpack .../libvisp-core-dev_3.0.0-1_amd64.deb ...
  Unpacking libvisp-core-dev:amd64 (3.0.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvisp-core-dev_3.0.0-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/include/x86_64-linux-gnu/visp/vpFeaturePointPolar.h', which is also in 
package libvisp-dev:amd64 2.10.0+dfsg-1+b1


cheers,

Andreas


libvisp-dev_3.0.0-1.log.gz
Description: application/gzip

Processed: libvisp-core-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/x86_64-linux-gnu/visp/vpFeaturePointPolar.h

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libvisp-dev
Bug #810354 [libvisp-core-dev] libvisp-core-dev: fails to upgrade from 
'testing' - trying to overwrite 
/usr/include/x86_64-linux-gnu/visp/vpFeaturePointPolar.h
Added indication that 810354 affects libvisp-dev

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

Bug#810358: [python-socks] python-socks should Replace: and Conflict: with python-pysocks

[Dererk]

Package: python-socks
Severity: grave

Dear python-socks/pysocks maintainer,

There appears to be a pkg transitioning name on python-pysocks to
python-socks, but no explicit replacing path on python-socks appears to
be set on either off them. This should be done by instructing to Replace
and Conflict with python-pysocks, etc:

(Reading database ... 185151 files and directories currently installed.)
Preparing to unpack .../python-socks_1.5.0+dfsg-3_all.deb ...
Unpacking python-socks (1.5.0+dfsg-3) ...
dpkg: error processing archive
/var/cache/apt/archives/python-socks_1.5.0+dfsg-3_all.deb (--unpack):
 trying to overwrite
'/usr/lib/python2.7/dist-packages/PySocks-1.5.0.egg-info', which is also
in package python-pysocks 1.5.0-2



Thanks!


Cheers,

Dererk

-- 
BOFH excuse #449:
greenpeace free'd the mallocs




signature.asc
Description: OpenPGP digital signature

Bug#810345: courier-authlib-{mysql, postgresql}: fails to install: invoke-rc.d: unknown initscript, /etc/init.d/courier-authdaemon not found.

[Andreas Beckmann]

Package: courier-authlib-mysql,courier-authlib-postgresql
Version: 0.66.4-2
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 courier-authlib-mysql.
  (Reading database ... 
(Reading database ... 7687 files and directories currently installed.)
  Preparing to unpack .../courier-authlib-mysql_0.66.4-2_amd64.deb ...
  Unpacking courier-authlib-mysql (0.66.4-2) ...
  Setting up courier-authlib-mysql (0.66.4-2) ...
  invoke-rc.d: unknown initscript, /etc/init.d/courier-authdaemon not found.
  dpkg: error processing package courier-authlib-mysql (--configure):
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   courier-authlib-mysql


cheers,

Andreas


courier-authlib-mysql_0.66.4-2.log.gz
Description: application/gzip

Bug#810355: lava-server: fails to upgrade from 'jessie': relation "linaro_django_xmlrpc_authtoken" already exists

[Andreas Beckmann]

Package: lava-server
Version: 2015.12-3
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...):

Applying linaro_django_xmlrpc.0001_initial...Traceback (most recent call 
last):
File "/usr/bin/lava-server", line 9, in 
  load_entry_point('lava-server==2015.12', 'console_scripts', 
'lava-server')()
File "/usr/lib/python2.7/dist-packages/lava_server/manage.py", line 125, in 
main
  run_with_dispatcher_class(LAVAServerDispatcher)
File "/usr/lib/python2.7/dist-packages/lava_tool/dispatcher.py", line 45, 
in run_with_dispatcher_class
  raise cls.run()
File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 153, 
in run
  raise SystemExit(cls().dispatch(args))
File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 143, 
in dispatch
  return command.invoke()
File "/usr/lib/python2.7/dist-packages/lava_server/manage.py", line 114, in 
invoke
  execute_from_command_line(['lava-server'] + self.args.command)
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 350, in execute_from_command_line
  utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 342, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 348, in run_from_argv
  self.execute(*args, **cmd_options)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 399, in execute
  output = self.handle(*args, **options)
File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", 
line 200, in handle
  executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
File "/usr/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
line 92, in migrate
  self._migrate_all_forwards(plan, full_plan, fake=fake, 
fake_initial=fake_initial)
File "/usr/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
line 121, in _migrate_all_forwards
  state = self.apply_migration(state, migration, fake=fake, 
fake_initial=fake_initial)
File "/usr/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
line 198, in apply_migration
  state = migration.apply(state, schema_editor)
File "/usr/lib/python2.7/dist-packages/django/db/migrations/migration.py", 
line 123, in apply
  operation.database_forwards(self.app_label, schema_editor, old_state, 
project_state)
File 
"/usr/lib/python2.7/dist-packages/django/db/migrations/operations/models.py", 
line 59, in database_forwards
  schema_editor.create_model(model)
File "/usr/lib/python2.7/dist-packages/django/db/backends/base/schema.py", 
line 284, in create_model
  self.execute(sql, params or None)
File "/usr/lib/python2.7/dist-packages/django/db/backends/base/schema.py", 
line 110, in execute
  cursor.execute(sql, params)
File "/usr/lib/python2.7/dist-packages/django/db/backends/utils.py", line 
64, in execute
  return self.cursor.execute(sql, params)
File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 97, in 
__exit__
  six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/lib/python2.7/dist-packages/django/db/backends/utils.py", line 
62, in execute
  return self.cursor.execute(sql)
  django.db.utils.ProgrammingError: relation "linaro_django_xmlrpc_authtoken" 
already exists
  
  dpkg: error processing package lava-server (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


lava-server_2015.12-3.log.gz
Description: application/gzip

Bug#809195: network-manager_1.0.10-1_amd64.deb does not update my I.P address correctly when I start my VPN

[Marco Frison]

Package: network-manager
Version: 1.0.10-1
Followup-For: Bug #809195

Seems it has been fixed in last network-manager release 1.0.10-2 as stated on 
archlinux bugstrack (https://bugs.archlinux.org/task/47535).

Hope it can be pushed fast to sid too; meanwhile you have to delete your 
default gateway manually and enter the new one using the route command.

Bug#810365: [apt] Temporary failure resolving xxxx even when the network is up and running

[Julian Andres Klode]

Control: tag -1 moreinfo

On Fri, Jan 08, 2016 at 05:28:02PM +0200, Bogdan Vatra wrote:
> Package: apt
> Version: 1.1.10
> Severity: serious
> 
> --- Please enter the report below this line. ---
> The problem happens on an chrooted arm64 image on Android.
> 
> Commands log:
> 
> root@localhost:~# apt update
> Err:1 http://httpredir.debian.org/debian sid InRelease
>   Temporary failure resolving 'httpredir.debian.org'
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> All packages are up to date.
> W: Failed to fetch http://httpredir.debian.org/debian/dists/sid/InRelease  
> Temporary failure resolving 'httpredir.debian.org'
> W: Some index files failed to download. They have been ignored, or old ones 
> used instead.
> 

Probably /etc/resolv.conf is not readable by _apt?

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Processed: Re: Bug#810365: [apt] Temporary failure resolving xxxx even when the network is up and running

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #810365 [apt] [apt] Temporary failure resolving   even when the network 
is up and running
Added tag(s) moreinfo.

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

Bug#810380: cryptsetup goes to an endless loop when shutting down the system

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: cryptsetup
Version: 2:1.7.0-1
Severity: critical

When I shut down my system or (more important) reboot it, it will run
into a endless loop after tellin "Stopping remaining crypto disks"
trying to stop all cryptfilesystems that are in /etc/crypttab (and only
them, not partitions mounted manually) to stop again and again.

That makes the whole system break as it will never end its shutdown and
so never come back online again.

The bug was introduced in the last update from version 2:1.6.6-5 to
2:1.7.0-1.

- -- Package-specific info:
- -- /proc/cmdline
root=/dev/md0 ro ide0=autotune ide1=autotune acpi=on vga=0x318 ipv6.disable=1 
video=ofonly intel_iommu=on 

- -- /etc/crypttab
# 
#swap0 /dev/sda2  /dev/random   
swap,cipher=blowfish-cbc-essiv:sha512
#swap1 /dev/sdb2  /dev/random   
swap,cipher=blowfish-cbc-essiv:sha512
swap0 /dev/sda2   /dev/urandom  
swap,cipher=blowfish-cbc-essiv:sha256,hash=sha256,size=56,noearly
swap1 /dev/sdb2   /dev/urandom  
swap,cipher=blowfish-cbc-essiv:sha256,hash=sha256,size=56,noearly
crypt0 UUID=5a26b56c-04c7-4e43-95d2-b03668f11513 none luks,noauto

- -- /etc/fstab
# HEADER: This file was autogenerated at Sat Jan 05 17:08:46 +0100 2013
# HEADER: by puppet.  While it can still be managed manually, it
# HEADER: is definitely not recommended.
# /etc/fstab: static file system information.
#
#  
 
LABEL=/   /   xfs   logbufs=8   
   1 1
/dev/mapper/swap0 noneswap  sw,pri=2
   0 0
/dev/mapper/swap1 noneswap  sw,pri=2
   0 0
# hidepid was introduced with kernel v3.3
proc  /proc   proc  hidepid=2,gid=adm   
   0  0
tmpfs /tmptmpfs nosuid,nodev,mode=1777  
   0  0
LABEL=/usr/usrbtrfs 
nodev,space_cache,autodefrag,compress  1  2
LABEL=/var/varbtrfs 
nosuid,space_cache,autodefrag,compress 1  2
LABEL=/usr/local  /usr/local  btrfs 
nosuid,nodev,space_cache,autodefrag,compress   1  2
LABEL=ikki_crypt  /home   btrfs 
nosuid,nodev,space_cache,autodefrag,compress,subvol=home,noauto1  0
LABEL=ikki_crypt  /misc   btrfs 
nosuid,space_cache,autodefrag,compress,subvol=misc,noauto  1  0
LABEL=ikki_crypt  /etc/secure btrfs 
nosuid,nodev,noexec,space_cache,autodefrag,compress,subvol=etc,noauto  1  0
LABEL=ikki_crypt  /root   btrfs 
nosuid,nodev,space_cache,autodefrag,compress,subvol=root,noauto1  0
#LABEL=MediaBackup/misc/MBackups  xfs   nosuid,nodev,noikeep
   1  2
tmpfs /media  tmpfs 
nosuid,nodev,noexec,mode=0755,size=10240k  0  0
/home/doshd   /dosvfat  noauto,loop,offset=32384
   0  0
/dev/sr0  /cdrom  auto  
ro,nosuid,nodev,group,gid=24,noauto0  0
#/dev/cdrom   /cdfs   cdfs  
ro,nosuid,nodev,group,gid=24,noauto0  0
#LABEL=hathi://hathi  ext2  ro  
   1  0
#/dev/sysvg/lv_hathi  /hathi  squashfs  ro  
   0  0
/dev/sdb6 /misc/baculaxfs   nosuid,nodev,noikeep
   1  2

- -- lsmod
Module  Size  Used by
fuse   86016  5
twofish_generic20480  0
ablk_helper16384  0
cryptd 20480  1 ablk_helper
twofish_x86_64_3way28672  1
lrw16384  1 twofish_x86_64_3way
glue_helper16384  1 twofish_x86_64_3way
twofish_x86_64 16384  1 twofish_x86_64_3way
twofish_common 24576  3 
twofish_generic,twofish_x86_64_3way,twofish_x86_64
xts16384  1 twofish_x86_64_3way
gf128mul   16384  2 lrw,xts
algif_skcipher 20480  0
af_alg 16384  1 algif_skcipher
oss_usb   110592  2
oss_hdaudio   151552  4
osscore   516096  4 oss_hdaudio,oss_usb
pktcdvd32768  1
binfmt_misc16384  1
drbg   24576  1

Bug#801784: marked as done (gitk de_DE.UTF-8: Error in startup script: bad menu entry index "Ansicht bearbeiten ...")

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 17:32:22 +0100
with message-id <87vb74vxpl@turtle.gmx.de>
and subject line Re: Bug#800576: gitk --all doesn’t work anymore in some locales
has caused the Debian Bug report #800576,
regarding gitk de_DE.UTF-8: Error in startup script: bad menu entry index 
"Ansicht bearbeiten ..."
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.)


-- 
800576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitk
Version: 1:2.6.1-1
Severity: grave

Hi,

running in a German locale, gitk is broken:

$ gitk
Error in startup script: bad menu entry index "Ansicht bearbeiten ..."
while executing
".bar.view entryconf [mca "Edit view..."] -state normal"
invoked from within
"if {$cmdline_files ne {} || $revtreeargs ne {} || $revtreeargscmd ne {}} {
# create a view for the files/dirs specified on the command line
se..."
(file "/usr/bin/gitk" line 12442)

The experimental version 1:2.6.1+next.20151009-1 has the same problem.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gitk depends on:
ii  git  1:2.6.1-1
ii  tk   8.6.0+8

gitk recommends no packages.

Versions of packages gitk suggests:
pn  git-doc  

-- no debconf information

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/
--- End Message ---
--- Begin Message ---
Source: git
Version: 1:2.7.0~rc3-1

On 2015-11-11 18:27 +0100, Jerome Robert wrote:

> This is fixed by 28de568 in the upstream repo [1].

The fix is included in the Debian package[2] as of version
1:2.7.0~rc3-1, hence I'm closing this bug.

> [1] git://ozlabs.org/~paulus/gitk.git

Cheers,
   Sven


2. 
http://repo.or.cz/git/debian.git/commit/28de56856a62a459cfb2276e517bac5af9147ab2--- End Message ---

Bug#800576: marked as done (gitk --all doesn’t work anymore in some locales)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 17:32:22 +0100
with message-id <87vb74vxpl@turtle.gmx.de>
and subject line Re: Bug#800576: gitk --all doesn’t work anymore in some locales
has caused the Debian Bug report #800576,
regarding gitk --all doesn’t work anymore in some locales
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.)


-- 
800576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitk
Version: 1:2.6.0-1
Severity: important

Dear Maintainer,

Hello, when I try to start gitk, I got an error message

:~/propellor$ gitk --all
Error in startup script: bad menu entry index "Éditer la vue..."
while executing
".bar.view entryconf [mca "Edit view..."] -state normal"
invoked from within
"if {$cmdline_files ne {} || $revtreeargs ne {} || $revtreeargscmd ne {}} {
# create a view for the files/dirs specified on the command line
se..."
(file "/usr/bin/gitk" line 12442)


cheers

Frederic

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

Kernel: Linux 4.2.0-1-586
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitk depends on:
ii  git  1:2.6.0-1
ii  tk   8.6.0+8

gitk recommends no packages.

Versions of packages gitk suggests:
pn  git-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: git
Version: 1:2.7.0~rc3-1

On 2015-11-11 18:27 +0100, Jerome Robert wrote:

> This is fixed by 28de568 in the upstream repo [1].

The fix is included in the Debian package[2] as of version
1:2.7.0~rc3-1, hence I'm closing this bug.

> [1] git://ozlabs.org/~paulus/gitk.git

Cheers,
   Sven


2. 
http://repo.or.cz/git/debian.git/commit/28de56856a62a459cfb2276e517bac5af9147ab2--- End Message ---

Bug#795343: zotero-standalone: Package stopped working after iceweasel upgrade.

[Adrien Grellier]

notfixed 795343 4.0.26.2-1
thanks

Hi,

I think the bug is not solved, as  I got this message with the latest version 
of zotero in Debian :

adrien ~/ $ zotero 
xulrunner not found, trying firefox instead.
Error: Platform version '43.0.4' is not compatible with
minVersion >= 31.0
maxVersion <= 40.*
adrien ~/ $ 

I also should notice that xul-ext-zotero is working well.

Regards,

Adrien

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

Bug#810365: [apt] Temporary failure resolving xxxx even when the network is up and running

[Bogdan Vatra]

Package: apt
Version: 1.1.10
Severity: serious

--- Please enter the report below this line. ---
The problem happens on an chrooted arm64 image on Android.

Commands log:

root@localhost:~# apt update
Err:1 http://httpredir.debian.org/debian sid InRelease
  Temporary failure resolving 'httpredir.debian.org'
Reading package lists... Done
Building dependency tree   
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://httpredir.debian.org/debian/dists/sid/InRelease  
Temporary failure resolving 'httpredir.debian.org'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.

root@localhost:~# ping httpredir.debian.org
PING httpredir.debian.org (5.153.231.35) 56(84) bytes of data.
64 bytes from httpredir-bm-01.debian.org (5.153.231.35): icmp_seq=1 ttl=56 
time=59.1 ms
^C
--- httpredir.debian.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 59.100/59.100/59.100/0.000 ms


root@localhost:~# wget http://httpredir.debian.org/debian/dists/sid/InRelease
--2016-01-08 15:22:56--  
http://httpredir.debian.org/debian/dists/sid/InRelease
Resolving httpredir.debian.org (httpredir.debian.org)... 176.9.184.93, 
128.31.0.66, 5.153.231.35, ...
Connecting to httpredir.debian.org (httpredir.debian.org)|176.9.184.93|:80... 
connected.
HTTP request sent, awaiting response... 302 Found
Location: http://debian.spnet.net/debian/dists/sid/InRelease [following]
--2016-01-08 15:22:56--  http://debian.spnet.net/debian/dists/sid/InRelease
Resolving debian.spnet.net (debian.spnet.net)... 212.36.0.70, 
2a01:288:4000:6::2
Connecting to debian.spnet.net (debian.spnet.net)|212.36.0.70|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 276935 (270K) [application/octet-stream]
Saving to: 'InRelease'

InRelease   100%[===>] 270.44K  --.-KB/sin 0.07s   

2016-01-08 15:22:56 (3.75 MB/s) - 'InRelease' saved [276935/276935]


root@localhost:~# cat /etc/apt/sources.list
deb http://httpredir.debian.org/debian sid main

root@localhost:~# cat /etc/resolv.conf 
nameserver 192.168.0.1
nameserver 8.8.8.8


root@localhost:~# ifconfig 
eth0: flags=4163  mtu 1500
inet 192.168.0.107  netmask 255.255.255.0  broadcast 192.168.0.255
inet6 fe80::204:4bff:fe48:245  prefixlen 64  scopeid 0x20
ether 00:04:4b:48:02:45  txqueuelen 1000  (Ethernet)
RX packets 78377  bytes 80657401 (76.9 MiB)
RX errors 0  dropped 6  overruns 0  frame 0
TX packets 46599  bytes 4291623 (4.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 0  (Local Loopback)
RX packets 21  bytes 3924 (3.8 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 21  bytes 3924 (3.8 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p2p-wlan0-0: flags=4163  mtu 1500
inet 192.168.49.1  netmask 255.255.255.0  broadcast 192.168.49.255
inet6 fe80::4:4bff:fe48:8243  prefixlen 64  scopeid 0x20
ether 02:04:4b:48:82:43  txqueuelen 1000  (Ethernet)
RX packets 16853  bytes 271789 (265.4 KiB)
RX errors 0  dropped 2  overruns 0  frame 0
TX packets 12445  bytes 258502 (252.4 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099  mtu 1500
ether 00:04:4b:48:02:43  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



root@localhost:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG20800 eth0
192.168.0.0 0.0.0.0 255.255.255.0   U 20800 eth0
192.168.49.00.0.0.0 255.255.255.0   U 0  00 p2p-
wlan0-0

root@localhost:~# mount  
/dev/block/sda1 on / type ext4 (rw,relatime,seclabel,data=ordered)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime,seclabel)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,seclabel,mode=755)
devpts on /dev/pts type devpts (rw,relatime,seclabel,mode=600)


Ping and wget works ok, it seems only apt can't use the network.

Yours,
BogDan.

Bug#810357: R crashes with "Illegal instruction" on mips

[Dirk Eddelbuettel]

On 8 January 2016 at 16:12, Sébastien Villemot wrote:
| Le vendredi 08 janvier 2016 à 08:59 -0600, Dirk Eddelbuettel a écrit :
| 
| > On 8 January 2016 at 14:54, Sébastien Villemot wrote:
| > | Package: r-base-core
| > | Version: 3.2.3-1
| > | Severity: grave
| > 
| > That will deprive a couple (ten or hundred) thousand users of R because ...
| 
| > ... neither I not R Core have mips access, as this may become
| > release-critical and block R.  :-/
| 
| Note that all newly uploaded CRAN packages are already blocked from
| migrating to testing, since they FTBFS on a release arch. And this does
| not depend on the severity of the present bug report.
| 
| Also note that, as a Debian developer, you have access to a mips machine
| (minkus.debian.org) with a sid chroot.

Thanks for the reminder. I have used that in the past for some of the
exotics, but the machines names tend to change, the procedures tend to
changes etc pp.

We can probably square this up.  It smells like something due to gcc-5 as the
same code worked for years.  Every now and then we do have to tell the
compiler to chill ...

| I'll try to see if I can help you on this issue (though I am largely
| ignorant on the R internals and on the mips specifics). You could also
| try to contact the MIPS porters list (debian-m...@lists.debian.org) to
| get some help.

Sure, thanks.  In the past sometimes I did hear back, and sometimes I did not.

Dirk
 
| Cheers,
| 
| -- 
|  .''`.Sébastien Villemot
| : :' :Debian Developer
| `. `' http://sebastien.villemot.name
|   `-  GPG Key: 4096R/381A7594

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#810357: R crashes with "Illegal instruction" on mips

[Sébastien Villemot]

Le vendredi 08 janvier 2016 à 09:35 -0600, Dirk Eddelbuettel a écrit :

> We can probably square this up.  It smells like something due to gcc-5 as the
> same code worked for years.  Every now and then we do have to tell the
> compiler to chill ...

That indeed looks like a compiler problem. I am going to recompile R
without optimization on the mips porterbox, to see if that helps.

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594

Processed: zotero-standalone: Package stopped working after iceweasel upgrade.

[Debian Bug Tracking System]

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

> notfixed 795343 4.0.26.2-1
Bug #795343 [zotero-standalone] zotero-standalone: Package stopped working 
after iceweasel upgrade.
No longer marked as fixed in versions zotero-standalone-build/4.0.26.2-1.
> thanks
Stopping processing here.

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

Bug#809595: marked as done (sendip: FTBFS: error: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp])

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 15:58:28 +
with message-id 
and subject line Bug#809595: fixed in sendip 2.5-7
has caused the Debian Bug report #809595,
regarding sendip: FTBFS: error: #warning "_BSD_SOURCE and _SVID_SOURCE are 
deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
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.)


-- 
809595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sendip
Version: 2.5-6
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

dh_testdir
/usr/bin/make PREFIX=/usr LDLOADLIBS=-lc
make[1]: Entering directory '/sendip-2.5'
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fsigned-char -pipe -Wall -Wpointer-arith -Wwrite-strings -Wstrict-prototypes 
-Wnested-externs -Winline -Werror -g -Wcast-align 
-DSENDIP_LIBS=\"/usr/lib/sendip\" -Wdate-time -D_FORTIFY_SOURCE=2  -c -o csum.o 
csum.c
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25:0,
 from csum.c:10:
/usr/include/features.h:148:3: error: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
 # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
   ^
cc1: all warnings being treated as errors
: recipe for target 'csum.o' failed
make[1]: *** [csum.o] Error 1
make[1]: Leaving directory '/sendip-2.5'
debian/rules:43: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/sendip.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: sendip
Source-Version: 2.5-7

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

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated sendip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Jan 2016 15:11:02 +
Source: sendip
Binary: sendip
Architecture: source amd64
Version: 2.5-7
Distribution: sid
Urgency: low
Maintainer: Jonathan McDowell 
Changed-By: Jonathan McDowell 
Description:
 sendip - Commandline tool to allow sending arbitrary IP packets
Closes: 809595
Changes:
 sendip (2.5-7) unstable; urgency=low
 .
   * Fix FTBFS with GCC 5. (closes: #809595)
Checksums-Sha1:
 3e7a4051e5dc0eb74aa7905e4af028dd3c49aadb 1658 sendip_2.5-7.dsc
 bbfea47b7ba26537d566d2058c7adb3e43a53025 4796 sendip_2.5-7.debian.tar.xz
 a2416a3caa3c2a8939ecb5671b6749bcfe94c416 82944 sendip-dbgsym_2.5-7_amd64.deb
 12ae781b2f7e66a64e491cff92b3b84c5b985fb6 41356 sendip_2.5-7_amd64.deb
Checksums-Sha256:
 3622ae96853033d34ef94da42d49244fc3a8d0eea26924c258253b141cd0e9b6 1658 
sendip_2.5-7.dsc
 3c8eac0cccf73d35991f0b3f6b9733b4e55642a109568af67e996bddc2a181c7 4796 
sendip_2.5-7.debian.tar.xz
 490f7529a40222c9e0626af36780e2afdd1a85e4ba9bd59a68466209b93d34ab 82944 
sendip-dbgsym_2.5-7_amd64.deb
 03b3fdab9c6178dd2d8157a4d9d1f7e2d37e719e3e9f526448c390c9fd52b018 41356 
sendip_2.5-7_amd64.deb
Files:
 29e356db2a65ab6080383dfc275fb62d 1658 net optional sendip_2.5-7.dsc
 ceb0ebec16384f94bb77bc8e335f9ae1 4796 net optional sendip_2.5-7.debian.tar.xz
 05bf3a9ca4f05ceddcd855ccc28f55f9 82944 debug extra 
sendip-dbgsym_2.5-7_amd64.deb
 1a00ae8a3ade3bcd09b420a48b46fe6e 41356 net optional sendip_2.5-7_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJWj9NhAAoJEP8WL8XPP7rREAsP/3pLFOQQ9nCkQZcrnB69ffeS
7+k1JQv9Gt4bUKpP5u56Qp1XbzyTT8OVG9eW+p3RO/YKzusqY5KVNB/oD0FbeGsu
GOZcKb7PJaychwNKMoXzx7A10P9O0WVGc6FrCSrvkinbguWGjKmWtYZ/YHj9RY2h

Bug#810365: [apt] Temporary failure resolving xxxx even when the network is up and running

[Julian Andres Klode]

On Fri, Jan 08, 2016 at 05:16:00PM +0100, Julian Andres Klode wrote:
> Control: tag -1 moreinfo
> 
> On Fri, Jan 08, 2016 at 05:28:02PM +0200, Bogdan Vatra wrote:
> > Package: apt
> > Version: 1.1.10
> > Severity: serious
> > 
> > --- Please enter the report below this line. ---
> > The problem happens on an chrooted arm64 image on Android.
> > 
> > Commands log:
> > 
> > root@localhost:~# apt update
> > Err:1 http://httpredir.debian.org/debian sid InRelease
> >   Temporary failure resolving 'httpredir.debian.org'
> > Reading package lists... Done
> > Building dependency tree   
> > Reading state information... Done
> > All packages are up to date.
> > W: Failed to fetch http://httpredir.debian.org/debian/dists/sid/InRelease  
> > Temporary failure resolving 'httpredir.debian.org'
> > W: Some index files failed to download. They have been ignored, or old ones 
> > used instead.
> > 
> 
> Probably /etc/resolv.conf is not readable by _apt?

_apt being a username used by the fetching process.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#810357: R crashes with "Illegal instruction" on mips

[Dirk Eddelbuettel]

On 8 January 2016 at 16:44, Sébastien Villemot wrote:
| Le vendredi 08 janvier 2016 à 09:35 -0600, Dirk Eddelbuettel a écrit :
| 
| > We can probably square this up.  It smells like something due to gcc-5 as 
the
| > same code worked for years.  Every now and then we do have to tell the
| > compiler to chill ...
| 
| That indeed looks like a compiler problem. I am going to recompile R
| without optimization on the mips porterbox, to see if that helps.

*Really* appreciate that. Am at work now and cannot dive into that.

We surely had these types of issues before, and I tend after some years
remove some of those flags.  The debian/rules is not my proudest moment (as
it is really cluttered) but you should find your way around for CFLAGS etc.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#796853: marked as done (python-bcrypt: passlib says this library is broken)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2016 15:57:49 +
with message-id 
and subject line Bug#796853: fixed in python-bcrypt 2.0.0-1
has caused the Debian Bug report #796853,
regarding python-bcrypt: passlib says this library is broken
to be marked as done.

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

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


-- 
796853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-bcrypt
Version: 0.4-2+b1
Severity: grave
Tags: security
Justification: renders package unusable

According to https://pythonhosted.org/passlib/history.html:

"It will now issue a PasslibSecurityWarning if the active backend is
vulnerable to the wraparound bug, and automatically enable a workaround
(py-bcrypt is known to be vulnerable as of v0.4)."

After running the tests, you get the following passlib warning:

/«PKGBUILDDIR»/passlib/handlers/bcrypt.py:320: UserWarning:
passlib.hash.bcrypt: Your installation of the 'pybcrypt' backend is
vulnerable to the bsd wraparound bug, and should be upgraded or replaced
with another backend (this warning will be fatal under passlib 1.7)
  "(this warning will be fatal under passlib 1.7)" % backend)

python-bcrypt is py-bcrypt 0.4
https://pypi.python.org/pypi/py-bcrypt/0.4

The recommended library to use is bcrypt:
https://pypi.python.org/pypi/bcrypt

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python-bcrypt depends on:
ii  libc6   2.19-18
ii  python  2.7.9-1

python-bcrypt recommends no packages.

python-bcrypt suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-bcrypt
Source-Version: 2.0.0-1

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

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated python-bcrypt 
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, 08 Jan 2016 15:07:04 +0100
Source: python-bcrypt
Binary: python-bcrypt python3-bcrypt
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Daniel Stender 
Description:
 python-bcrypt - password hashing library for Python
 python3-bcrypt - password hashing library for Python 3
Closes: 796853 803096
Changes:
 python-bcrypt (2.0.0-1) unstable; urgency=medium
 .
   [ Daniel Stender ]
   * New upstream release (Closes: #803096).
   * Switched upstream from py-bcrypt to pyuca/bcrypt (Closes: #796853).
   * deb/control:
 + changed Priority from "extra" to "optional".
 + added Daniel Stender to Uploaders.
 + added dh-python and python{,3}-cffi and to build depends.
 + bumped Standards-Version to 3.9.6 (no changes needed).
 + updated Homepage.
 + added Vcs-Git and Vcs-Browser.
 + removed extended infos in long description text concerning py-bcrypt,
   made short description easier, updated URI of the mentioned paper.
   * deb/copyright:
 + updated.
 + added Daniel Stender to copyright holders of debian/.
   * deb/rules:
 + added exports for DH_VERBOSE and DEB_BUILD_OPTIONS=nocheck.
 + build with Pybuild.
 + use override for dh_installdocs to contribute into both packages.
   * deb/watch:
 + watch bcrypt on Pypi.
   * Added:
 + deb/.git-dpm (Repo initialzed for Git-dpm).
 + deb/upstream/signing-key.asc.
   * Dropped:
 + deb/manpage and deb/python-bcrypt.1 (belonging to py-bcrypt).
 + deb/docs (using dh_installdocs in deb/rules).
 .
   [ Raphaël Hertzog ]
   * Add build-dependencies on 

Bug#809053: xindy FTBFS due to CPPFLAGS containing spaces

[Agustin Martin]

On Wed, Jan 06, 2016 at 10:25:34PM +0100, Agustin Martin wrote:
> No. Just googled a bit and just found a message in the xindy-dev list
> commenting that it might require some work, but without reply from
> Joachim Schrod. Someone fluent with clisp and sbcl might however find
> it easier. I vaguely remember something about xindy needing ffi, but I
> think recent sbcl has it.

Going back into time, IIRC this was only for ancient xindy, using an
external non lisp regexp library. I think this is no longer needed since
clisp started shipping its own REGEXP module.

Not sure how many clisp'isms are still present.

Regards,

-- 
Agustin

Bug#810357: R crashes with "Illegal instruction" on mips

[Julien Cristau]

On Fri, Jan  8, 2016 at 08:59:13 -0600, Dirk Eddelbuettel wrote:

> 
> Hi Seb,
> 
> On 8 January 2016 at 14:54, Sébastien Villemot wrote:
> | Package: r-base-core
> | Version: 3.2.3-1
> | Severity: grave
> 
> That will deprive a couple (ten or hundred) thousand users of R because ...
> 
> | Control: affects -1 r-cran-ncdf4 r-cran-afex r-cran-coin r-cran-scales 
> r-cran-ape r-cran-rms r-cran-timeseries r-cran-dosefinding r-cran-maps 
> r-cran-statmod
> | 
> | -BEGIN PGP SIGNED MESSAGE-
> | Hash: SHA256
> | 
> | Hi Dirk,
> | 
> | R crashes at startup with an "Illegal instruction" (tested on minkus, the 
> mips
> | porterbox):
> | 
> |   (sid_mips-dchroot)sebastien@minkus:~$ R
> |   Illegal instruction
> | 
> | Here is a backtrace:
> | 
> | #0  machar (ibeta=0x77fc3bd0 , it=0x77fc3bd4 
> , irnd=0x77fc3bd8 , ngrd=0x77fc3bdc 
> , machep=0x77fc3be0 ,
> | negep=0x77fc3be4 , iexp=0x77fc3be8 
> , minexp=0x77fc3bec , maxexp=0x77fc3bf0 
> , eps=0x77fc3bf8 ,
> | epsneg=0x77fc3c00 , xmin=0x77fc3c08 
> , xmax=0x77fc3c10 ) at platform.c:3199
> | #1  0x77d1a570 in Init_R_Machine (rho=0x43054c) at platform.c:61
> | #2  0x77d1b48c in Init_R_Variables (rho=0x43054c) at platform.c:198
> | #3  0x77cf0198 in setup_Rmainloop () at main.c:840
> | #4  0x77cf0dfc in Rf_mainloop () at main.c:1012
> | #5  0x00400a00 in main (ac=1, av=0x7fff6574) at Rmain.c:29
> | #6  0x779b9f58 in __libc_start_main () from /lib/mips-linux-gnu/libc.so.6
> | #7  0x00400870 in _ftext ()
> | 
> | Incidentally, all CRAN packages FTBFS on mips (see above for the list of
> | currently affected packages).
> 
> ... neither I not R Core have mips access, as this may become
> release-critical and block R.  :-/
> 
This is untrue.  You have access to debian's mips porterbox.

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances

Bug#810357: R crashes with "Illegal instruction" on mips

[Sébastien Villemot]

Le vendredi 08 janvier 2016 à 08:59 -0600, Dirk Eddelbuettel a écrit :

> On 8 January 2016 at 14:54, Sébastien Villemot wrote:
> | Package: r-base-core
> | Version: 3.2.3-1
> | Severity: grave
> 
> That will deprive a couple (ten or hundred) thousand users of R because ...

> ... neither I not R Core have mips access, as this may become
> release-critical and block R.  :-/

Note that all newly uploaded CRAN packages are already blocked from
migrating to testing, since they FTBFS on a release arch. And this does
not depend on the severity of the present bug report.

Also note that, as a Debian developer, you have access to a mips machine
(minkus.debian.org) with a sid chroot.

I'll try to see if I can help you on this issue (though I am largely
ignorant on the R internals and on the mips specifics). You could also
try to contact the MIPS porters list (debian-m...@lists.debian.org) to
get some help.

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594

Bug#810357: R crashes with "Illegal instruction" on mips

[Dirk Eddelbuettel]

On 8 January 2016 at 14:54, Sébastien Villemot wrote:
| Package: r-base-core
| Version: 3.2.3-1
| Severity: grave
| Control: affects -1 r-cran-ncdf4 r-cran-afex r-cran-coin r-cran-scales 
r-cran-ape r-cran-rms r-cran-timeseries r-cran-dosefinding r-cran-maps 
r-cran-statmod
| 
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA256
| 
| Hi Dirk,
| 
| R crashes at startup with an "Illegal instruction" (tested on minkus, the mips
| porterbox):
| 
|   (sid_mips-dchroot)sebastien@minkus:~$ R
|   Illegal instruction
| 
| Here is a backtrace:
| 
| #0  machar (ibeta=0x77fc3bd0 , it=0x77fc3bd4 
, irnd=0x77fc3bd8 , ngrd=0x77fc3bdc 
, machep=0x77fc3be0 ,
| negep=0x77fc3be4 , iexp=0x77fc3be8 
, minexp=0x77fc3bec , maxexp=0x77fc3bf0 
, eps=0x77fc3bf8 ,
| epsneg=0x77fc3c00 , xmin=0x77fc3c08 
, xmax=0x77fc3c10 ) at platform.c:3199
| #1  0x77d1a570 in Init_R_Machine (rho=0x43054c) at platform.c:61
| #2  0x77d1b48c in Init_R_Variables (rho=0x43054c) at platform.c:198
| #3  0x77cf0198 in setup_Rmainloop () at main.c:840
| #4  0x77cf0dfc in Rf_mainloop () at main.c:1012
| #5  0x00400a00 in main (ac=1, av=0x7fff6574) at Rmain.c:29
| #6  0x779b9f58 in __libc_start_main () from /lib/mips-linux-gnu/libc.so.6
| #7  0x00400870 in _ftext ()

That code does

a = one;
do {
a = a + a;
temp = a + one;
temp1 = temp - a;
}
while(temp1 - one == zero);

(You can see it from the r-devel repo here at
https://github.com/wch/r-source/blob/trunk/src/main/platform.c#L3091-L3097 )

I'd be inclined to call it compiler bug.  Shall we try without optimization?

Dirk
 
| Incidentally, all CRAN packages FTBFS on mips (see above for the list of
| currently affected packages).
| 
| Cheers,
| 
| - --
|  .''`.Sébastien Villemot
| : :' :Debian Developer
| `. `' http://sebastien.villemot.name
|   `-  GPG Key: 4096R/381A7594
| 
| -BEGIN PGP SIGNATURE-
| Version: GnuPG v1
| 
| iQIcBAEBCAAGBQJWj7+KAAoJECzs6TUOzr5KeAMQAJb9i2A502nK2f0EoN0+ReR7
| hJJlC8wBv0L2edlCjV6sE45Fa+bkpHrazC8JDoJpTeA6pcJ6HnzxAAOFNdoosHYk
| IwPsOhQsdnlYxAYNBuSwTJHoTNBGBDkvMEvPrh6LuOvUPYPE42by5R3pO69cjfB2
| +F0QzO0dCr4Abi4tBBW6T+4LvzhFRkVK1b+M7c+ZO6k7fSS5sqoZdbmpXSP00wWh
| 0WbhjmjDtQR9xd1ngAxpOUA7RHrBB3PCDagMF9cqo7UmjYFPcL8+Y5YeEuslnrPN
| Ijf1p1SzWaFeBI2Hm+OPFU/6pCCEj/TwPKn+5VYSBIkFMe3HyUg+L1US1Vq3m3ca
| +cAySL324DCG2CAmCHpotW4XwPzEGopKJI7VnNZYmlC7pIOi8gU4oPIN8NcysoCS
| c7BcyEURBoM3D/lzMmQc+Iw38T1emQEFtrMMkwNVcXTdWjPOEkNn6605Hs57tiM0
| OqTxgL8c779UUzdfv9QWSKBYfgqwNdTdORq9QDp5VeTLdcGRVslbRamozP3GanEp
| HMVFLct4cvLdf0gXfpAaGTC0lK61kHQZuzTktoPZqx8PcC6Ib29WoxJisb42SIcR
| ZwoKb26AKYoh/ksXvB4fW8Rg6pthsfm8iW4AXluknu6loaAbi3KpksbJNJtcY+fu
| swmq6f2IybsfIXjMFYIh
| =5kLR
| -END PGP SIGNATURE-

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org