Processed: fixed 816780 in 1.4.20-1.1+deb7u1, fixed 816780 in 1.4.20-1.1+deb8u1

[Debian Bug Tracking System]

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

> fixed 816780 1.4.20-1.1+deb7u1
Bug #816780 [src:roundup] roundup: CVE-2014-6276: information leak
Marked as fixed in versions roundup/1.4.20-1.1+deb7u1.
> fixed 816780 1.4.20-1.1+deb8u1
Bug #816780 [src:roundup] roundup: CVE-2014-6276: information leak
Marked as fixed in versions roundup/1.4.20-1.1+deb8u1.
> thanks
Stopping processing here.

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

Bug#816780: roundup: CVE-2014-6276: information leak

[Salvatore Bonaccorso]

Source: roundup
Version: 1.4.20-1
Severity: grave
Tags: security upstream fixed-upstream wheezy jessie stretch sid

Hi

https://www.debian.org/security/2016/dsa-3502:
|Ralf Schlatterbeck discovered an information leak in roundup, a
|web-based issue tracking system. An authenticated attacker could use
|it to see sensitive details about other users, including their hashed
|password.

The purpose of this bug is to have a RC bug for roundup. roundup has
long seen any new upstream releases. 

>From Kai Storbeck it looks the way forward would be to have roundup
removed for unstable and stretch. Kai can you confirm that this is
still the plan vs. update to new upstream releases?

If so can you fill afer discussion with the Python App team a removal
request?

Regards,
Salvatore

Bug#816315: [pkg-uWSGI-devel] Bug#816315: #816315 - uwsgi - please support ruby2.3

[Antonio Terceiro]

On Fri, Mar 04, 2016 at 12:42:53AM +0100, Jonas Smedegaard wrote:
> Quoting Christian Hofstaedtler (2016-03-03 22:47:48)
> > May I suggest dropping the exact ruby version from the package name, 
> > so it doesn't have to go through NEW for 2.4, 2.5, ...?
> > 
> > I see uwsgi-plugin-rbthreads already doesn't encode the version in the 
> > package name.
> 
> You sure may suggest it (explicitly too - was arguably already 
> implicitly hinted at by the bugreport), and yes there is indeed 
> inconsistency across the uwsgi packages.
> 
> The aim is, however, the opposite: For each library with multiple 
> concurrent versions - even if only a single of them reaching stable at 
> any point in time - have correspondent uwsgi packages (and then 
> additionally have a convenience package linkest against current "main" 
> version).

I insist: please stop doing that. This unecessarily slows down the Ruby
transitions as uwsgi cannot be just binNMUed to be updated.

There are other 130 packages with Ruby native extensions that work just
fine with a single Ruby package providing the native libraries for the
currently supported Ruby versions in a single binary package.

Ah and it also wastes FTP master time when processing binNEW.

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature

Bug#815775: #815775: zeroc-ice: FTBFS against ruby2.3

[Chris Knadle]

zeroc-ice seems to build fine without listing libmono2.0-cil and mono-gmcs
in the Build-Depends.

NMU prepared; debdiff attached.

P.S. the maintainers for zeroc-ice in Debian have not been heard from in
some time.  (2 years)  :-(

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us
diff -Nru zeroc-ice-3.5.1/debian/changelog zeroc-ice-3.5.1/debian/changelog
--- zeroc-ice-3.5.1/debian/changelog2015-11-21 02:41:17.0 -0500
+++ zeroc-ice-3.5.1/debian/changelog2016-03-04 23:17:37.0 -0500
@@ -1,3 +1,16 @@
+zeroc-ice (3.5.1-6.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
+- Remove dependencies to fix FTBFS bug:
+ libmono2.0-cil,
+ mono-gmcs
+  (Closes: #815775)
+  [Note: the Ubuntu source packages zeroc-ice upstream ships have
+   far fewer Build-Depends.]
+
+ -- Christopher Knadle   Fri, 04 Mar 2016 21:54:19 
-0500
+
 zeroc-ice (3.5.1-6.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru zeroc-ice-3.5.1/debian/control zeroc-ice-3.5.1/debian/control
--- zeroc-ice-3.5.1/debian/control  2015-11-19 23:39:06.0 -0500
+++ zeroc-ice-3.5.1/debian/control  2016-03-04 21:59:26.0 -0500
@@ -18,7 +18,6 @@
   ruby,
   libqt4-dev,
 Build-Depends-Indep: mono-devel | c-sharp-2.0-compiler,
-libmono2.0-cil,
 pkg-config,
 default-jdk | java-gcj-compat,
 libjgoodies-looks-java (>= 2.5.2),
@@ -27,7 +26,6 @@
 libdb5.3-java (>= 5.1.4~) | libdb-java (>= 5.1.4~),
 ant,
 ant-optional,
-mono-gmcs,
 cli-common-dev (>= 0.8~)
 Standards-Version: 3.9.6
 Homepage: http://www.zeroc.com/

Processed: block 816486 with 816775

[Debian Bug Tracking System]

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

> block 816486 with 816775
Bug #816486 [src:sup-mail] sup-mail: FTBFS: builder.rb:89:in `run': rake 
failed, exit code 1 (Gem::InstallError)
816486 was not blocked by any bugs.
816486 was not blocking any bugs.
Added blocking bug(s) of 816486: 816775
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: #816486: sup-mail: FTBFS: builder.rb:89

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #816486 [src:sup-mail] sup-mail: FTBFS: builder.rb:89:in `run': rake 
failed, exit code 1 (Gem::InstallError)
Added tag(s) confirmed.
> block -1 816775
Unknown command or malformed arguments to command.


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

Bug#816486: #816486: sup-mail: FTBFS: builder.rb:89

[Christian Hofstaedtler]

Control: tags -1 + confirmed
Control: block -1 816775

Thank you for your report.

Apparently we missed ruby-xapian in the 2.3 transition :-(

Best,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Processed: retitle 815798 to gitlab: not installable because of locale issue

[Debian Bug Tracking System]

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

> retitle 815798 gitlab: not installable because of locale issue
Bug #815798 [gitlab] (no subject)
Changed Bug title to 'gitlab: not installable because of locale issue' from 
'(no subject)'
> thanks
Stopping processing here.

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

Bug#816205: [Pkg-php-pecl] Bug#816205: php-igbinary: Incomplete copyright information

[Luke Faraone]

On 29 February 2016 at 13:40, Ondřej Surý  wrote:
> Luke, thanks for catching this. The work you do (as ftp-masters group)
> is really appreciated and admired.

Happy to be of service. And thanks to you for taking care of unloved
packages :)

  -- Luke

Bug#816700: foomatic-filters-beh and cups-filters: error when trying to install together

[Jörg Frings-Fürst]

reasign 816700 cups-filters 1.8.2-3

Hi,

beh is part of foomatic-filters before the old old stable release 
4.0.5-6.

Therefor cups-filters must correkt this bug.

CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54538 Bausendorf

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#804316: marked as done (FTBFS: error: ‘SSLv3_method’ undeclared here)

[Debian Bug Tracking System]

Your message dated Sat, 05 Mar 2016 00:22:36 +
with message-id 
and subject line Bug#811434: Removed package(s) from unstable
has caused the Debian Bug report #804316,
regarding FTBFS: error: ‘SSLv3_method’ undeclared here
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.)


-- 
804316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby2.1
Version: 2.1.5-4
Severity: serious

I get the following errors when I want to rebuild ruby2.1:

[...]
ossl_ssl.c:137:27: error: ‘SSLv3_method’ undeclared here (not in a function)
 OSSL_SSL_METHOD_ENTRY(SSLv3),
   ^
ossl_ssl.c:115:69: note: in definition of macro ‘OSSL_SSL_METHOD_ENTRY’
 #define OSSL_SSL_METHOD_ENTRY(name) { #name, (SSL_METHOD 
*(*)(void))name##_method }
 ^
ossl_ssl.c:138:27: error: ‘SSLv3_server_method’ undeclared here (not in a 
function)
 OSSL_SSL_METHOD_ENTRY(SSLv3_server),
   ^
ossl_ssl.c:115:69: note: in definition of macro ‘OSSL_SSL_METHOD_ENTRY’
 #define OSSL_SSL_METHOD_ENTRY(name) { #name, (SSL_METHOD 
*(*)(void))name##_method }
 ^
ossl_ssl.c:139:27: error: ‘SSLv3_client_method’ undeclared here (not in a 
function)
 OSSL_SSL_METHOD_ENTRY(SSLv3_client),
   ^
ossl_ssl.c:115:69: note: in definition of macro ‘OSSL_SSL_METHOD_ENTRY’
 #define OSSL_SSL_METHOD_ENTRY(name) { #name, (SSL_METHOD 
*(*)(void))name##_method }
 ^
Makefile:281: recipe for target 'ossl_ssl.o' failed
make[4]: *** [ossl_ssl.o] Error 1

This is probably due to the openssl transition, and this affects it:

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

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.1.5-4+rm

Dear submitter,

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

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

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

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

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

Bug#800030: marked as done (ruby-opengraph-parser: FTBFS: OpenGraph#initialize with body should parse body instead of downloading it)

[Debian Bug Tracking System]

Your message dated Sat, 05 Mar 2016 00:20:37 +
with message-id 
and subject line Bug#816752: Removed package(s) from unstable
has caused the Debian Bug report #800030,
regarding ruby-opengraph-parser: FTBFS: OpenGraph#initialize with body should 
parse body instead of downloading it
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.)


-- 
800030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-opengraph-parser
Version: 0.2.3+gh-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-opengraph-parser fails to build from source in unstable/amd64:

  [..]

  Failed examples:
  
  rspec ./spec/lib/open_graph_spec.rb:89 # OpenGraph#initialize with
  body should parse body instead of downloading it
  
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  failed
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-opengraph-parser-0.2.3+gh/debian/ruby-opengraph-parser
  returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-opengraph-parser_0.2.3+gh-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Sep 18 21:03:33 GMT+12 2015
I: pbuilder-time-stamp: 1442653413
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), gem2deb (>= 0.7.4~), ruby-rspec, 
ruby-nokogiri, ruby-addressable
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20206 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on gem2deb (>= 0.7.4~); however:
  Package gem2deb is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-rspec; however:
  Package ruby-rspec is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-nokogiri; however:
  Package ruby-nokogiri is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-addressable; however:
  Package ruby-addressable is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  ca-certificates{a} devscripts{a} dh-python{a} gem2deb{a} 
  gem2deb-test-runner{a} libexpat1{a} libgmp-dev{a} libgmpxx4ldbl{a} 
  libmpdec2{a} libpython3-stdlib{a} libpython3.4-minimal{a} 
  libpython3.4-stdlib{a} libruby2.1{a} libruby2.2{a} libssl1.0.0{a} 
  libxslt1.1{a} libyaml-0-2{a} mime-support{a} openssl{a} python3{a} 
  python3-chardet{a} python3-debian{a} python3-minimal{a} 
  python3-pkg-resources{a} 

Bug#816584: Processed: Re: Bug#816584: libraw1394: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

[Norbert Preining]

severity 816584 important
tags 816584 + pending
thanks

Hi everyone,

the dependency on texlive-generic-recommended got lost during
transition, will be fixed in the next upload.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#815734: regression: ESS cannot be compiled

[Norbert Preining]

Dear all,

down here at Debian we got another bug report about a FTBFS, which
went away when switching to an older version of texinfo.tex:

On Thu, 03 Mar 2016, Dirk Eddelbuettel wrote:
> Ok, the obvious fix of fattening the source directory with a working copy of
> texinfo.tex did the trick.

I have reduced the problematic case to the following minimal example:

\input texinfo   @c -*-texinfo-*-
@setfilename ess.info
@settitle ESS -- Emacs Speaks Statistics

@macro ESS{ARG}
@acronym{ESS\ARG\}
@end macro

@ESS{}: bad

@ESS{[R]}: good

@bye

The output is:
./bla.texi:9: Argument of @gobblespaces has an extra }.
 
@par 
 
   }
@doacronym ...#3@finish ->{@selectfonts @lsize #1}
  @def @temp {#2}@ifx @temp ...
l.1 @acronym{ESS@gobblespaces }
   @texinfoc
@scanmacro ...atspaces }@scantokens {#1@texinfoc }
  @aftermacro 
l.9 @ESS{}
  : bad
? 

Can anyone comment on this?

Thanks a lot

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Processed: Re: Processed: Re: Bug#816584: libraw1394: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

[Debian Bug Tracking System]

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

> severity 816584 important
Bug #816584 [texlive-htmlxml] libraw1394: FTBFS: ! LaTeX Error: File `ulem.sty' 
not found.
Severity set to 'important' from 'serious'
> tags 816584 + pending
Bug #816584 [texlive-htmlxml] libraw1394: FTBFS: ! LaTeX Error: File `ulem.sty' 
not found.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#816737: Broken after recent upgrade

[Aurelien Jarno]

control: tag -1 + moreinfo

On 2016-03-04 14:10, Philipp Klaus Krause wrote:
> Package: libc6
> Severity: Serious
> 
> Yesterday, I tred to upgrade libc6 on my Debian GNU/testing system. But
> it didn't work. The packages are marked as broken in synaptic. Today, I
> tried apt-get -f install, but it fails too:

While the issue appears when installing libc6, I really doubt it is an
issue with this package.

> root@notebook4:/home/philipp# LANG=C apt-get -f install
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Correcting dependencies... Done
> The following packages were automatically installed and are no longer
> required:
>   gtk2-engines libglewmx1.10 libgtkglext1-dev libintl-perl libjsoncpp0v5
> libopenraw1v5 libpangox-1.0-dev libsigc++-1.2-5c2 libusb-1.0-0:i386
> lockfile-progs
>   qemu-kvm
> Use 'apt autoremove' to remove them.
> The following additional packages will be installed:
>   libc6 libc6:i386 libc6-i686:i386
> Suggested packages:
>   glibc-doc glibc-doc:i386 libc-l10n:i386 locales:i386
> The following packages will be upgraded:
>   libc6 libc6:i386 libc6-i686:i386
> 3 upgraded, 0 newly installed, 0 to remove and 950 not upgraded.
> 4 not fully installed or removed.
> Need to get 0 B/6181 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n]
> debconf: Perl may be unconfigured (Unknown regexp modifier "/g" at
> /usr/share/perl/5.22/Text/Wrap.pm line 31, at end of line
> BEGIN not safe after errors--compilation aborted at
> /usr/share/perl/5.22/Text/Wrap.pm line 35.
> Compilation failed in require at /usr/share/perl5/Debconf/Template.pm
> line 10.

Your perl installation seems completely broken. Have you done anything
related with it recently?

> Philipp
> 
> P.S.: How can I get my system back into a useable state? Since the
> failure is on de-configuring, I guess, I can't go back to an older
> version either?

You should try to reinstall perl. Something like "apt-get install
--reinstall perl perl-base perl-modules-5.22" might help.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Re: Bug#816737: Broken after recent upgrade

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #816737 [libc6] Broken after recent upgrade
Added tag(s) moreinfo.

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

Bug#816757: marked as done (lzop: Does not build on powerpc)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 23:44:16 +
with message-id 
and subject line Bug#816757: fixed in lzop 1.03-3.2
has caused the Debian Bug report #816757,
regarding lzop: Does not build on powerpc
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.)


-- 
816757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lzop
Version: 1.03-3
Severity: grave

After my upload of lzop/1.03-3.1, it turns out that lzop no longer
builds on powerpc, with a large number of errors like

,
| compress.o: In function `__ACC_UA_GET_LE16':
| /home/bengen/lzop-1.03/src/miniacc.h:2881: multiple definition of 
`__ACC_UA_GET_LE16'
| lzop.o:/home/bengen/lzop-1.03/src/miniacc.h:2881: first defined here
`

However, this has nothing to do with the NMU -- the previous version
lzop/1.03-3 which does not use dh-autoreconf fails in unstable, too,
while lzop/1.03-3.1 builds just fine on jessie.

-Hilko
--- End Message ---
--- Begin Message ---
Source: lzop
Source-Version: 1.03-3.2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated lzop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Mar 2016 00:27:26 +0100
Source: lzop
Binary: lzop
Architecture: source
Version: 1.03-3.2
Distribution: unstable
Urgency: medium
Maintainer: Peter Eisentraut 
Changed-By: Hilko Bengen 
Description:
 lzop   - fast compression program
Closes: 816757
Changes:
 lzop (1.03-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Patch src/miniacc.h to fix FTBFS on powerpc (Closes: #816757)
Checksums-Sha1:
 4c7fc3cb9ef8b17c40ad856c3670be92e0797454 1697 lzop_1.03-3.2.dsc
 404f3a73fdcb61a1ec2099389a5d367f904b7012 3488 lzop_1.03-3.2.debian.tar.xz
Checksums-Sha256:
 bc914422d65fcf1ceaf8cdb8fa0cc041251fc83721123cc215cd98c08a0c4bb1 1697 
lzop_1.03-3.2.dsc
 0828f3524e5aa38423e3b29a69743a632f96f5c229b6d5c3707c76c3ed6e0a60 3488 
lzop_1.03-3.2.debian.tar.xz
Files:
 2d6df3338e3c14751f590200151f0fdf 1697 utils optional lzop_1.03-3.2.dsc
 2e9aeb78814a8e1b0e553e45b1dd1180 3488 utils optional 
lzop_1.03-3.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJW2hoOAAoJEHW3EGNcITp+w9AP/ROCXB+fO8CeXT4UjRBhKna9
yczA/65ha0kDM2zOf4IUgjBefpRp8ZWA6LGrYGa8zM/R4QTCVeftyc05s76vuGpO
87ZYPwHFwoZ40+MDsq2Ovo66uh0QBRlnlTHZ8YgFIOo+T/UL+8c3AXp+4RKYe0h5
tx0LZ7ezcm5N3gKn8P4vLwHi7aus3lxBHqn2EvCqgGbWOpOaJBkYflH1fwnTAm+C
pXSS2wV3JdRQCkO9/Jrp1E/tsHOAhCL23s3xviobU2XKDyVvAL10keNRVEPqRvHV
jvmc3S/ThaNJz+89UQh7uq/D8xoNTsbLpX1qJC7Jc+LdKnc1bUGGK9CcBFotQMT4
9dUKOVjm/K0XYCky1jC95LGT/5qnwx6z01aKI5nNH8PnjTjsbEGinIVLRkq2oaj1
koUNDM17A8o5u3987HoNztgznCVl3xHy5v1NixpV9btRh65W3URL/rCXhOUh2yum
yd5cnbVJz5z313LFNOTJPIzv5GPopbPXThUNr/wdV58w+xHa1zGXinl23Cwltbal
Krix9ks/+QO79BARimzLuqsj7KiXmgYU7bWp2u8V6oANw9N+IdpGjTkk9rWUL1k8
+CZtxaV5DkZ5PcEpxRPD24dXuOVqx64vvAVpe1jB+aPK5GO7Fa9gqNwYZKKXOfab
+zYyv/OhxRtqJasvcwWg
=AMqy
-END PGP SIGNATURE End Message ---

Bug#811470: marked as done (mdp: FTBFS: TypeError: Call constructor takes either 0 or 3 positional arguments)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 23:44:28 +
with message-id 
and subject line Bug#811470: fixed in mdp 3.4-1
has caused the Debian Bug report #811470,
regarding mdp: FTBFS: TypeError: Call constructor takes either 0 or 3 
positional arguments
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.)


-- 
811470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdp
Version: 3.3+git19-g4ec2f29-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,

mdp fails to build from source in unstable/amd64:

  [..]

  _pytest.python:1546: in parsefactories
  >   holderobj = node_or_obj.obj
  _pytest.python:205: in fget
  >   self._obj = obj = self._getobj()
  _pytest.python:344: in _getobj
  >   return self._memoizedcall('_obj', self._importtestmodule)
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.python:353: in _importtestmodule
  >   mod = self.fspath.pyimport(ensuresyspath=True)
  py._path.local:532: in pyimport
  >   ???
  :969: in _find_and_load
  >   ???
  :954: in _find_and_load_unlocked
  >   ???
  :892: in _find_spec
  >   ???
  :873: in _find_spec_legacy
  >   ???
  _pytest.assertion.rewrite:136: in find_module
  >   ???
  _pytest.assertion.rewrite:206: in _rewrite_test
  >   ???
  _pytest.assertion.rewrite:259: in rewrite_asserts
  >   ???
  _pytest.assertion.rewrite:370: in run
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:448: in visit_Assert
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:572: in visit_Compare
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:563: in visit_Attribute
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:434: in generic_visit
  >   ???
  _pytest.assertion.rewrite:397: in display
  >   ???
  _pytest.assertion.rewrite:403: in helper
  >   ???
  E   TypeError: Call constructor takes either 0 or 3 positional arguments
  ___ ERROR collecting test_scikits.py 
___
  _pytest.runner:121: in __init__
  >   ???
  _pytest.main:366: in _memocollect
  >   ???
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.main:366: in 
  >   ???
  _pytest.python:347: in collect
  >   self.session._fixturemanager.parsefactories(self)
  _pytest.python:1546: in parsefactories
  >   holderobj = node_or_obj.obj
  _pytest.python:205: in fget
  >   self._obj = obj = self._getobj()
  _pytest.python:344: in _getobj
  >   return self._memoizedcall('_obj', self._importtestmodule)
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.python:353: in _importtestmodule
  >   mod = self.fspath.pyimport(ensuresyspath=True)
  py._path.local:532: in pyimport
  >   ???
  :969: in _find_and_load
  >   ???
  :954: in _find_and_load_unlocked
  >   ???
  :892: in _find_spec
  >   ???
  :873: in _find_spec_legacy
  >   ???
  _pytest.assertion.rewrite:136: in find_module
  >   ???
  _pytest.assertion.rewrite:206: in _rewrite_test
  >   ???
  _pytest.assertion.rewrite:259: in rewrite_asserts
  >   ???
  _pytest.assertion.rewrite:370: in run
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:448: in visit_Assert
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:572: in visit_Compare
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:434: in generic_visit
  >   ???
  _pytest.assertion.rewrite:397: in display
  >   ???
  _pytest.assertion.rewrite:403: in helper
  >   ???
  E   TypeError: Call constructor takes either 0 or 3 positional arguments
  ___ ERROR collecting test_svm_classifier.py 

  _pytest.runner:121: in __init__
  >   ???
  _pytest.main:366: in _memocollect
  >   ???
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.main:366: in 
  >   ???
  _pytest.python:347: in collect
  >   self.session._fixturemanager.parsefactories(self)
  _pytest.python:1546: in parsefactories
  >   holderobj = node_or_obj.obj
  _pytest.python:205: in fget
  >   self._obj = obj = 

Bug#795116: marked as done (ruby-simple-navigation: FTBFS: undefined method `stub!')

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 23:00:26 +
with message-id 
and subject line Bug#795116: fixed in ruby-simple-navigation 4.0.3-1
has caused the Debian Bug report #795116,
regarding ruby-simple-navigation: FTBFS: undefined method `stub!'
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.)


-- 
795116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-simple-navigation
Version: 3.11.0-1
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:

Failures:

  1) SimpleNavigation::Adapters::Padrino link_to should delegate to context
 Failure/Error: SimpleNavigation::Adapters::Padrino.new(@context)
 NoMethodError:
   undefined method `request' for 
#
 # ./lib/simple_navigation/adapters/sinatra.rb:14:in `initialize'
 # ./spec/lib/simple_navigation/adapters/padrino_spec.rb:6:in `new'
 # ./spec/lib/simple_navigation/adapters/padrino_spec.rb:6:in 
`create_adapter'
 # ./spec/lib/simple_navigation/adapters/padrino_spec.rb:13:in `block (2 
levels) in '

  2) SimpleNavigation::Adapters::Padrino content_tag should delegate to context
 Failure/Error: SimpleNavigation::Adapters::Padrino.new(@context)
 NoMethodError:
   undefined method `request' for 
#
 # ./lib/simple_navigation/adapters/sinatra.rb:14:in `initialize'
 # ./spec/lib/simple_navigation/adapters/padrino_spec.rb:6:in `new'
 # ./spec/lib/simple_navigation/adapters/padrino_spec.rb:6:in 
`create_adapter'
 # ./spec/lib/simple_navigation/adapters/padrino_spec.rb:13:in `block (2 
levels) in '

  3) SimpleNavigation::Adapters::Rails self.register should call set_env
 Failure/Error: @context.stub!(:controller => @controller)
 NoMethodError:
   undefined method `stub!' for 
#
 # ./spec/lib/simple_navigation/adapters/rails_spec.rb:12:in `block (2 
levels) in '

  4) SimpleNavigation::Adapters::Rails self.register should extend the 
ActionController::Base with the Helpers
 Failure/Error: @context.stub!(:controller => @controller)
 NoMethodError:
   undefined method `stub!' for 
#
 # ./spec/lib/simple_navigation/adapters/rails_spec.rb:12:in `block (2 
levels) in '

...

422 examples, 356 failures

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 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)
--- End Message ---
--- Begin Message ---
Source: ruby-simple-navigation
Source-Version: 4.0.3-1

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated ruby-simple-navigation 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Mar 2016 16:18:54 -0300
Source: ruby-simple-navigation
Binary: ruby-simple-navigation
Architecture: source
Version: 4.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Sebastien Badia 
Description:
 ruby-simple-navigation - Library to create navigations for Ruby web 
applications
Closes: 769788 795116
Changes:
 ruby-simple-navigation (4.0.3-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Cédric Boutillier ]
   * Run wrap-and-sort on packaging files.
 .
   [ Sebastien Badia ]
   * Refresh Debian packaging using dh-make-ruby (and fix install)
   * Imported Upstream version (Closes: #795116)
   * Bumped up compat version to 9
   * 

Bug#814198: marked as done (csmith: FTBFS: platform.cpp:78:10: error: impossible constraint in 'asm')

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 22:35:39 +
with message-id 
and subject line Bug#814198: fixed in csmith 2.2.0-2
has caused the Debian Bug report #814198,
regarding csmith: FTBFS: platform.cpp:78:10: error: impossible constraint in 
'asm'
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.)


-- 
814198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: csmith
Version: 2.2.0-1
Severity: serious
Justification: fails to build from source

Hi,

csmith FTBFS on some architecture.

arm64:  
https://buildd.debian.org/status/fetch.php?pkg=csmith=arm64=2.2.0-1=1454715566

MIPS: 
https://buildd.debian.org/status/fetch.php?pkg=csmith=mips=2.2.0-1=1454824019

Please fix this problem.

Best regards,
 Nobuhiro
--
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
--- End Message ---
--- Begin Message ---
Source: csmith
Source-Version: 2.2.0-2

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated csmith package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Mar 2016 02:42:39 +0900
Source: csmith
Binary: csmith libcsmith0 libcsmith-dev libcsmith0-dbg
Architecture: source amd64
Version: 2.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Description:
 csmith - generator of random C programs
 libcsmith-dev - generator of random C programs (development files)
 libcsmith0 - generator of random C programs (runtime library)
 libcsmith0-dbg - generator of random C programs (debugging symbols)
Closes: 814198
Changes:
 csmith (2.2.0-2) unstable; urgency=medium
 .
   [Matthias Klose]
   * Apply patches taken from Fedora:
 - Fix build on all arches by adding fallback implementation for getting
   initial seed. (Closes: #814198)
 - Use system header files.
   * Fix build on ppc64el.
Checksums-Sha1:
 341b1b670057ac095706c8e3610865ab234cc576 2017 csmith_2.2.0-2.dsc
 d81fdeae4da225502261195727e95d0d122b3c43 3588 csmith_2.2.0-2.debian.tar.xz
 8c8944537e0f9a4e8164a486466443e33b211dca 308922 csmith_2.2.0-2_amd64.deb
 523db7c88b42c568e473edb7f8a049e9bdfcf404 15890 libcsmith-dev_2.2.0-2_amd64.deb
 c8e227f85c7d84b42999c16a901f3ca1986148b9 5394384 
libcsmith0-dbg_2.2.0-2_amd64.deb
 cb76c350bea4afdf6fd962eebe9862a6631e 6996 libcsmith0_2.2.0-2_amd64.deb
Checksums-Sha256:
 e301f3f8553341c9b5921dee1c3ba944e020594016e79776991ba9f083768e3a 2017 
csmith_2.2.0-2.dsc
 79a005fb6c3ccbfe7e081a1cc63a21e709eaa31ab6d45070c3d25c8ee0867486 3588 
csmith_2.2.0-2.debian.tar.xz
 7942b8917d933c405074ed9e116720a6c202c954c8f5bd66f1af11558084588b 308922 
csmith_2.2.0-2_amd64.deb
 fd8cbb7f6d1f129140cf93efe6884eb5e02c6be29a961baed7c21283b59607d4 15890 
libcsmith-dev_2.2.0-2_amd64.deb
 8d1c302e2d82179ca486f5c0cf0501faf418125f9a4ca068c5002da406b5a6ed 5394384 
libcsmith0-dbg_2.2.0-2_amd64.deb
 0ebe2ec89feb77e68b822d07b20f584efaedd849197fc2fd8082d8e6699516e8 6996 
libcsmith0_2.2.0-2_amd64.deb
Files:
 9b9e95a04a9754e223e302929d6aefc1 2017 devel optional csmith_2.2.0-2.dsc
 c3609d1ca0065d4c2f18050d740d3e79 3588 devel optional 
csmith_2.2.0-2.debian.tar.xz
 b32d74abb94d8a3203fe4d26b4e694bd 308922 devel optional csmith_2.2.0-2_amd64.deb
 305810f76f9dd34abd79308c32e4755b 15890 libdevel optional 
libcsmith-dev_2.2.0-2_amd64.deb
 ff34d781d842d6910ffaf32ed37c92cb 5394384 debug extra 
libcsmith0-dbg_2.2.0-2_amd64.deb
 fec1ede92e358e46b0c723d9dc75aa6f 6996 libs optional 
libcsmith0_2.2.0-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW2eyEAAoJEDIkf7tArR+ma/cQAIBi0DqCmGnkI3jyM3PySZ7q
CinSZ9j7BzI6F+5kq1SyW73kUvUr1FerRLxhE6GYTGPLgnG1ThXdAS71IE5x3MXk
mxYiF03npvZglJLVQqpn6QmSCJwGFuyZPHFzjERJ4SoDFI4SW/IoKWA6mWx/6sjU
u64ZF+18snNCYvxSHM5dH6fEFhoesZyW3QtsZbrQQOXCJ6vvUyq6y1+LBcAu2pPi

Bug#816759: minissdpd: The minissdpd daemon is affected by an improper validation of array index vulnerability

[Salva Peiró]

Package: minissdpd
Version: 1.2.20130907-3
Justification: renders package unusable
Severity: grave
Tags: security patch

Dear Maintainer,

The following bug report provides the technical description and bug fixes
and has been extracted from the detailed security advisory
at http://speirofr.appspot.com/files/advisory/SPADV-2016-02.md

Best,

Vulnerability details
=

The minissdpd daemon (version: 1.2.20130907-3) contains a
improper validation of array index vulnerability (CWE-129)
when processing requests sent to the Unix socket at /var/run/minissdpd.sock
the Unix socket can be accessed by an unprivileged user to send invalid
request causes an out-of-bounds memory access that crashes the minissdpd
daemon.

Technical Details
=

The vulnerability can be triggered by a local unprivileged user performs
the following request:

$ echo -en '\x04\x01\x60\x8f\xff\xff\xff\x7f\x0a' | nc.openbsd -U
/var/run/minissdpd.sock

The request is processed by the processRequest() function at minissdpd.c
which identifies the request of type=4, and performs the parsing of the
"new service" request, the decoding of the length of the usn field
performed at
line 663, sets l = 0x, with p = buf+4, and n = 9, the negative
length
l=-1 passes the check at line 664 with (buf+4-1) < (buf + 9), continuing
with
the allocation of the usn field at line 673, that initialises newserv->usn =
malloc(0), where in the case of Linux malloc(3) the allocator returns a
pointer
that can be later passed to free().  The line 668 attempts to copy
0x
bytes from the message pointer p to newserv->usn, that causes the daemon to
perform an out-of-bound memory access writing outside the allocated buffer.

~~~
663 DECODELENGTH_CHECKLIMIT(l, p, buf + n);
664 if(p+l > buf+n) {
665 syslog(LOG_WARNING, "bad request (length encoding)");
666 goto error;
667 }
...
673 newserv->usn = malloc(l + 1);
674 if(!newserv->usn) {
675 syslog(LOG_ERR, "cannot allocate memory");
676 goto error;
677 }
668 memcpy(newserv->usn, p, l);
~~~

The problem is the incorrect validation on the length returned by the
DECODELENGTH_CHECKLIMIT macro at line 664, that does not consider negative
length values. The fix of the length has already been applied to the
upstream
minissdpd repository see [2], the bug happens at multiple locations after
the
DECODELENGTH_CHECKLIMIT macro that also need to be fixed:

~~~
  DECODELENGTH_CHECKLIMIT(l, p, buf + n);
- if(p+l > buf+n) {
+ if(l > (unsigned)(buf+n-p)) {
 syslog(LOG_ERR, "cannot allocate memory");
 goto error;
  }
~~~

After performing the corrections of the length check the minissdpd daemon
properly detects the invalid negative values and performs error handling.
However, the error handling code at line 753 attempts to free the undefined
memory contents that newserv = malloc() allocated at line 642.

~~~
753 if(newserv) {
754 free(newserv->st);
755 free(newserv->usn);
756 free(newserv->server);
757 free(newserv->location);
758 free(newserv);
759 newserv = NULL;
760 }
~~~

The issue is corrected by applying initialising the contents of the newserv
to zero [3].
That causes free() to correctly operate when freeing the uninitialised
struct fields.

~~~
642 newserv = malloc(sizeof(struct service));
643 if(!newserv) {
644 syslog(LOG_ERR, "cannot allocate memory");
645 goto error;
646 }
+   memset(newserv, 0, sizeof(struct service));
~~~

Solution


Apply the proposed fixes, contained in the patch below.

~~~
>From 2f6746a0c00872b977cc81452d77463aa39609e7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Salva=20Peir=C3=B3?= 
Date: Fri, 4 Mar 2016 12:38:18 +0100
Subject: [PATCH] Fix minissdpd.c handling of request with negative length

---
 minissdpd.c | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/minissdpd.c b/minissdpd.c
index 520a6c5..1cd079e 100644
--- a/minissdpd.c
+++ b/minissdpd.c
@@ -555,7 +555,7 @@ void processRequest(struct reqelem * req)
type = buf[0];
p = buf + 1;
DECODELENGTH_CHECKLIMIT(l, p, buf + n);
-   if(p+l > buf+n) {
+   if(l > (unsigned)(buf+n-p)) {
syslog(LOG_WARNING, "bad request (length encoding)");
goto error;
}
@@ -644,6 +644,7 @@ void processRequest(struct reqelem * req)
syslog(LOG_ERR, "cannot allocate memory");
goto error;
}
+   memset(newserv, 0, sizeof(struct service));
if(containsForbiddenChars(p, l)) {
syslog(LOG_ERR, "bad request (st contains forbidden chars)");
goto error;
@@ -661,7 +662,7 @@ void processRequest(struct reqelem * req)
goto error;
}
DECODELENGTH_CHECKLIMIT(l, p, buf + n);
-   if(p+l 

Bug#816757: lzop: Does not build on powerpc

[Hilko Bengen]

Package: lzop
Version: 1.03-3
Severity: grave

After my upload of lzop/1.03-3.1, it turns out that lzop no longer
builds on powerpc, with a large number of errors like

,
| compress.o: In function `__ACC_UA_GET_LE16':
| /home/bengen/lzop-1.03/src/miniacc.h:2881: multiple definition of 
`__ACC_UA_GET_LE16'
| lzop.o:/home/bengen/lzop-1.03/src/miniacc.h:2881: first defined here
`

However, this has nothing to do with the NMU -- the previous version
lzop/1.03-3 which does not use dh-autoreconf fails in unstable, too,
while lzop/1.03-3.1 builds just fine on jessie.

-Hilko

Bug#816756: Useless in Debian

[David Prévot]

Package: php-pimple
Version: 1.1.1-1
Severity: serious

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing, and not let it block the PHP 7.0 transition. ]

I packaged php-pimle as used by owncloud, but owncloud is going away,
see #816376. There is a priori little point to ship php-pimple in a
stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature

Bug#815734: regression: ESS cannot be compiled

[Dirk Eddelbuettel]

Just a quick 'thumbs up' from here -- it is actually quite remarkable that we
do maintain buildability of these pieces over so many years and decaded, and
I really appreciate how we're going calmly about the business of maintaining
that tradition.

Thanks to Norbert for distilling that minimal example out of the larger ESS
documentation, and to the texinfo folks for looking at it.

Cheers, Dirk

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

Bug#798934: marked as done (ruby-ffi-rzmq: FTBFS: Testsuite hangs ("broke out of wait_for_device loop"))

[Debian Bug Tracking System]

Your message dated Fri, 4 Mar 2016 23:05:35 +0100
with message-id <20160304220535.GA22830@esfahan>
and subject line unreproducible
has caused the Debian Bug report #798934,
regarding ruby-ffi-rzmq: FTBFS: Testsuite hangs ("broke out of wait_for_device 
loop")
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.)


-- 
798934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ffi-rzmq
Version: 2.0.1-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-ffi-rzmq fails to build from source in unstable/amd64:

  [..]
 
  
┌──┐
  │ Run tests for ruby2.1 from debian/ruby-tests.rb 
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-ffi-rzmq-2.0.1/debian/ruby-ffi-rzmq/usr/lib/ruby/vendor_ruby:.
  ruby2.1 debian/ruby-tests.rb
  
*.F..F..FFF..FFF..FFF..FFF..FFF..FFF..FFF..FFF..FF..create
  streamer device and running...
  broke out of wait_for_device loop
  device exited
  .create streamer device and running...
  broke out of wait_for_device loop
  device exited

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-ffi-rzmq_2.0.1-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Sep 10 22:14:25 GMT+12 2015
I: pbuilder-time-stamp: 1441966465
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), gem2deb (>= 0.4.1~), ruby-ffi-rzmq-core, 
libzmq3, ruby-rspec (>= 2.6~)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20260 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on gem2deb (>= 0.4.1~); however:
  Package gem2deb is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-ffi-rzmq-core; however:
  Package ruby-ffi-rzmq-core is not installed.
 pbuilder-satisfydepends-dummy depends on libzmq3; however:
  Package libzmq3 is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-rspec (>= 2.6~); however:
  Package ruby-rspec is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  ca-certificates{a} devscripts{a} dh-python{a} gem2deb{a} 
  gem2deb-test-runner{a} libexpat1{a} 

Bug#794139: marked as done (FTBFS: test_: converting CoffeeScript should produce JS. (TestCoffeeScript) fails)

[Debian Bug Tracking System]

Your message dated Fri, 4 Mar 2016 23:00:04 +0100
with message-id <20160304220004.GA10160@esfahan>
and subject line unreproducible
has caused the Debian Bug report #794139,
regarding FTBFS: test_: converting CoffeeScript should produce JS. 
(TestCoffeeScript) 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.)


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

Dear Maintainer,

The package fails to build:

Failure: test_: converting CoffeeScript should produce JS. (TestCoffeeScript)
[..]
diff:
  (function() {
- 
$(function() {
  var cube, cubes, list, num, square;
  list = [1, 2, 3, 4, 5];
  square = function(x) {
return x * x;
  };
  cube = function(x) {
return square(x) * x;
  };
  cubes = (function() {
?   var _i, _len, _results;
?  
?   _results = [];
? 
?   for (_i = 0, _len = list.length; _i < _len; _i++) {
?  
? num = list[_i];
? _results.push(math.cube(num));
?   
}
?   return _results;
?   
  })();
  if (typeof elvis !== "undefined" && elvis !== null) {
return alert("I knew it!");
  }
});
  
  }).call(this);
  
? Encoding: UTF-8
?S  ASCII

Maybe the coffeescript compiler has changed?

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Control: tag -1 unreproducible
Control: notfound -1 3.0.1+dfsg-1

Hi

I cannot reproduce the bug. I am thus closing this bug. Probably a
transient bug in one of the dependencies. Feel free to reopen if 
it becomes applicable again.

Cheers,

Cédric


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

Bug#816755: fglrx-atieventsd: disappearing mouse

[Richard Jasmin]

Package: fglrx-atieventsd
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Not sure how to fix this one, Ive only encountered it with the pre-packaged
driver for Jessie.

Once you get beyond the broker then broke state that either downgrading Xorg in
Stretch or installing fglrx in Jessie you get to this point.

[fix at this stage: aticonfig --initial again, you borked something in your
config. --or at least I did, but I cant see how.]

What happens is this:
The mouse is here...and then it isnt. This seems the most relevant package.
When the mouse goes, it runs away and hides(disappear, literally..the mouse OFF
feature) and wont come back. Clicking will not help you. The keyboard then
begins to act funny and semi-non responsive. And by funny, its not guaranteed
to alt-tab or otherwise navigate.

No, your wireless have not failed you. Your batteries are FINE.

But the system knows youre there. You can switch to a vterm and kill off X. For
now, until the mouse decides to hide again. Killing X will only bring back the
mouse for the login screen. Until it hides again. Rebooting will not help much
either.

Whack CTRL-ALT-DEL and away we gofor now. Until you login to X again...then
the mouse wants to hide.

Also:
text resolution is higher on open driver then fglrx in the vterm for some
reason

I will see further if I can replicate this issue. The driver I have is BETA
level but has been patched to run up to X 1.17 and kernel 4.3x. Original source
of the driver pre-patch was for fedora 22 at kernel v 4.0.4. The kernel header
sources were not available to build for a newer kernel for some reason. The
installer will refuse beyond X 1.17. Might be able to fudge the driver to work
for stretch.(and hopefully fedora 23)

The second you purge fglrx, the disappearing mouse issue goes away.




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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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)

Bug#815734: regression: ESS cannot be compiled

[Martin Maechler]

On Fri, Mar 4, 2016 at 10:38 PM, Gavin Smith  wrote:
>> > I have reduced the problematic case to the following minimal example:
>
> Thank you for taking the time to do this, Norbert.
>
>> From these two facts I'd declare that the new texinfo.tex that
>> you have in Debian is broken.
>> (Yes, that is a strong statement; but still breaking something
>>  that worked dozens of year w/o problems needs VERY good arguments
>>  before you can call it "progress" !!)
>
> No-one's said that breaking this usage is progress. It wasn't intended
> and we will fix it.
>
> The problem comes from trying to support the Texinfo macro facility,
> the different ways that it's been used in different documents and
> managing multiple incompatible implementations of it. It's caused
> problems ever since it was introduced, maybe about 20 years ago.
> Evidently these problems aren't at an end yet, despite hope. When the
> fix is finalized I'll add this breaking usage to our test file to
> prevent it breaking again.

Thanks a lot, Gavin!  The above sounds very good to me,
I'm sorry for my former misunderstanding..

Best regards,  and thank you for all the efforts to make info /
texinfo even more 'future-proof'!

Martin

Bug#784699: marked as done (ruby-i18n: random test failures during build)

[Debian Bug Tracking System]

Your message dated Fri, 4 Mar 2016 22:40:47 +0100
with message-id <20160304214046.gb28...@percival.namespace.at>
and subject line Re: #784699: ruby-i18n: random test failures during build
has caused the Debian Bug report #784699,
regarding ruby-i18n: random test failures during build
to be marked as done.

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

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


-- 
784699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-i18n
Version: 0.6.11-2
Severity: normal

Hi,

When building ruby-i18n, there are various random test failures:

  1) Failure:
I18nFallbacksApiTest#test_lookup:_given_an_array_of_keys_it_translates_all_of_them
 
[/«PKGBUILDDIR»/debian/ruby-i18n/usr/lib/ruby/vendor_ruby/i18n/tests/lookup.rb:52]:
--- expected
+++ actual
@@ -1 +1 @@
-["bar", "baz"]
+"translation missing: de.foo.baz"



  2) Failure:
I18nFallbacksApiTest#test_lookup:_given_a_missing_key,_no_default_and_no_raise_option_it_returns_an_error_message
 
[/«PKGBUILDDIR»/debian/ruby-i18n/usr/lib/ruby/vendor_ruby/i18n/tests/lookup.rb:33]:
--- expected
+++ actual
@@ -1 +1 @@
-"translation missing: en.missing"
+"translation missing: de.missing"


It takes several attempts to get a successful build (apparently it's worse when
using sbuild, than when using git-buildpackage).

Lucas

-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'), 
(300, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-trunk-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 ruby-i18n depends on:
ii  ruby1:2.1.5
ii  ruby2.1 [ruby-interpreter]  2.1.5-2+deb8u1

ruby-i18n recommends no packages.

ruby-i18n suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 ruby-i18n/0.7.0-2

Marking this as fixed as I can't reproduce it in unstable. If the
problem persists, please reopen.

Thanks,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  ` End Message ---

Bug#808515: marked as done (ruby-test-after-commit: FTBFS: undefined method `[]=' for nil:NilClass)

[Debian Bug Tracking System]

Your message dated Fri, 4 Mar 2016 18:41:17 -0300
with message-id <20160304214117.gh4...@baloo.sebian.fr>
and subject line Re: ruby-test-after-commit: FTBFS: undefined method `[]=' for 
nil:NilClass
has caused the Debian Bug report #808515,
regarding ruby-test-after-commit: FTBFS: undefined method `[]=' for nil:NilClass
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.)


-- 
808515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-test-after-commit
Version: 0.2.3+gh-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

DEPRECATION WARNING: Currently, Active Record suppresses errors raised within 
`after_rollback`/`after_commit` callbacks and only print them to the logs. In 
the next version, these errors will no longer be suppressed. Instead, the 
errors will propagate normally just like in other Active Record callbacks.

You can opt into the new behavior and remove this warning by setting:

  config.active_record.raise_in_transactional_callbacks = true

 (called from  at 
/ruby-test-after-commit-0.2.3+gh/spec/database.rb:141)
DEPRECATION WARNING: Currently, Active Record suppresses errors raised within 
`after_rollback`/`after_commit` callbacks and only print them to the logs. In 
the next version, these errors will no longer be suppressed. Instead, the 
errors will propagate normally just like in other Active Record callbacks.

You can opt into the new behavior and remove this warning by setting:

  config.active_record.raise_in_transactional_callbacks = true

 (called from  at 
/ruby-test-after-commit-0.2.3+gh/spec/database.rb:158)
DEPRECATION WARNING: Currently, Active Record suppresses errors raised within 
`after_rollback`/`after_commit` callbacks and only print them to the logs. In 
the next version, these errors will no longer be suppressed. Instead, the 
errors will propagate normally just like in other Active Record callbacks.

You can opt into the new behavior and remove this warning by setting:

  config.active_record.raise_in_transactional_callbacks = true

 (called from  at 
/ruby-test-after-commit-0.2.3+gh/spec/database.rb:175)
.*F

...

Failures:

  1) TestAfterCommit fires on create
 Failure/Error: Car.create
 NoMethodError:
   undefined method `commit_records' for nil:NilClass
 # ./lib/test_after_commit.rb:31:in `test_commit_records'
 # ./lib/test_after_commit.rb:18:in `ensure in block in 
transaction_with_transactional_fixtures'
 # ./lib/test_after_commit.rb:20:in `block in 
transaction_with_transactional_fixtures'
 # ./lib/test_after_commit.rb:9:in `transaction_with_transactional_fixtures'
 # ./spec/test_after_commit_spec.rb:18:in `block (2 levels) in '
 # ./spec/spec_helper.rb:25:in `block (2 levels) in '

  2) TestAfterCommit fires on update
 Failure/Error: car = Car.create
 NoMethodError:
   undefined method `[]=' for nil:NilClass
 # ./lib/test_after_commit.rb:72:in `sync_with_transaction_state'
 # ./lib/test_after_commit.rb:12:in `block in 
transaction_with_transactional_fixtures'
 # ./lib/test_after_commit.rb:9:in `transaction_with_transactional_fixtures'
 # ./spec/test_after_commit_spec.rb:23:in `block (2 levels) in '
 # ./spec/spec_helper.rb:25:in `block (2 levels) in '


...

Failed examples:

rspec ./spec/test_after_commit_spec.rb:17 # TestAfterCommit fires on create
rspec ./spec/test_after_commit_spec.rb:22 # TestAfterCommit fires on update
rspec ./spec/test_after_commit_spec.rb:29 # TestAfterCommit fires on 
update_attribute
rspec ./spec/test_after_commit_spec.rb:36 # TestAfterCommit does not fire on 
rollback
rspec ./spec/test_after_commit_spec.rb:43 # TestAfterCommit does not fire on 
ActiveRecord::RecordInvalid
rspec ./spec/test_after_commit_spec.rb:50 # TestAfterCommit does not fire 
multiple times in nested transactions
rspec ./spec/test_after_commit_spec.rb:61 # TestAfterCommit fires when 
transaction block returns from method
rspec ./spec/test_after_commit_spec.rb:66 # TestAfterCommit does not raises 
errors
rspec ./spec/test_after_commit_spec.rb:90 # TestAfterCommit returns on create 
and on create of associations
rspec ./spec/test_after_commit_spec.rb:95 # TestAfterCommit returns on create 
and on create of associations without after_commit
rspec ./spec/test_after_commit_spec.rb:100 # TestAfterCommit calls callbacks in 

Bug#815734: regression: ESS cannot be compiled

[Gavin Smith]

> > I have reduced the problematic case to the following minimal example:

Thank you for taking the time to do this, Norbert.

> From these two facts I'd declare that the new texinfo.tex that
> you have in Debian is broken.
> (Yes, that is a strong statement; but still breaking something
>  that worked dozens of year w/o problems needs VERY good arguments
>  before you can call it "progress" !!)

No-one's said that breaking this usage is progress. It wasn't intended
and we will fix it.

The problem comes from trying to support the Texinfo macro facility,
the different ways that it's been used in different documents and
managing multiple incompatible implementations of it. It's caused
problems ever since it was introduced, maybe about 20 years ago.
Evidently these problems aren't at an end yet, despite hope. When the
fix is finalized I'll add this breaking usage to our test file to
prevent it breaking again.

Processed: Re: ruby-test-after-commit: FTBFS: undefined method `[]=' for nil:NilClass

[Debian Bug Tracking System]

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

> fixed 808515 0.4.2-1
Bug #808515 [src:ruby-test-after-commit] ruby-test-after-commit: FTBFS: 
undefined method `[]=' for nil:NilClass
The source 'ruby-test-after-commit' and version '0.4.2-1' do not appear to 
match any binary packages
Marked as fixed in versions ruby-test-after-commit/0.4.2-1.
> thanks
Stopping processing here.

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

Processed: severity of 816751 is important

[Debian Bug Tracking System]

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

> severity 816751 important
Bug #816751 [src:linux] linux-image-3.16.0-4-amd64: Boot hangs at ata_piix 
message under 3.16.x, but works with 3.2.x
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#815734: regression: ESS cannot be compiled

[Gavin Smith]

On 4 March 2016 at 04:01, Norbert Preining  wrote:
> The output is:
> ./bla.texi:9: Argument of @gobblespaces has an extra }.

I got the same. I think it's easy enough to fix. The only possible
problem is that this error comes about due to an attempt to remove
whitespace from the start of a macro argument when the macro only
takes one argument. To fix, this would be removed, so any whitespace
after the opening brace of the macro invocation wouldn't be ignored. I
think this is okay, because people will only expect spaces following
commas separating macro arguments to be discarded. In the past, spaces
were trimmed at the beginning and end of macro arguments regardless of
the number of arguments they took, but this broke when the macro
argument had newlines which had to be significant (as far as I
remember).

Bug#816751: linux-image-3.16.0-4-amd64: Boot hangs at ata_piix message under 3.16.x, but works with 3.2.x

[Chad House]

Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

This machine had been running with an up-to-date version of Wheezy for
over a year. Following a dist-upgrade to Jessie, it no longer boots
under the 3.16.x kernel, seeming to hang when loading/initializing the
ATA library. The last boot message refers to ata_piix (see below).

It boots and runs fine under the 3.2.x LTS kernel, however.

-- Package-specific info:
** Kernel log: boot messages should be attached

Last line in kernel log is:

 ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ]

** Model information

Jetway JBC372F36W Intel Atom N2600 Compact Fanless Barebone

See: http://www.logicsupply.com/jbc372f36w/

sys_vendor:  Jetway
product_name:
product_version:
chassis_vendor:
chassis_version:
bios_vendor: American Megatrends Inc.
bios_version: 4.6.4
board_vendor:  Jetway
board_name:  JBC372F36W
board_version:  JBC372F36W-2600-B

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor D2xxx/N2xxx
DRAM Controller [8086:0bf1] (rev 04)
Subsystem: Intel Corporation Device [8086:1999]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
SERR-  [disabled]
Capabilities: 
Kernel driver in use: gma500

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High
Definition Audio Controller [8086:27d8] (rev 02)
Subsystem: Jetway Information Co., Ltd. Device [16f3:a621]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- 
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express
Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express
Port 2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express
Port 3 [8086:27d4] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express
Port 4 [8086:27d6] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #1 [8086:27c8] (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation NM10/ICH7 Family USB UHCI Controller
#1 [8086:27c8]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- 
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev e2) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
Reset- 

Bug#800057: marked as done (ruby-thread-safe: FTBFS: non_concurrent_cache_backend.rb:10: [BUG] Segmentation fault at 0x00000000000018)

[Debian Bug Tracking System]

Your message dated Fri, 4 Mar 2016 22:18:51 +0100
with message-id <20160304211851.ga28...@percival.namespace.at>
and subject line Re: #800057: ruby-thread-safe: FTBFS
has caused the Debian Bug report #800057,
regarding ruby-thread-safe: FTBFS: non_concurrent_cache_backend.rb:10: [BUG] 
Segmentation fault at 0x18
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.)


-- 
800057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-thread-safe
Version: 0.3.3-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-thread-safe fails to build from source in unstable/amd64:

  [..]
  
  
┌──┐
  │ Run tests for ruby2.1 from debian/ruby-test-files.yaml  
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby:.
  ruby2.1 -ryaml -e
  YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ \|f\|\
  require\ f\ \}
  Loaded suite -e
  Started
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/non_concurrent_cache_backend.rb:10:
  [BUG] Segmentation fault at 0x18
  ruby 2.1.5p273 (2014-11-13) [x86_64-linux-gnu]
  
  -- Control frame information
  ---
  c:0011 p: s:0061 e:60 CFUNC  :[]
  c:0010 p:0011 s:0057 e:56 METHOD
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/non_concurrent_cache_backend.rb
  c:0009 p:0009 s:0053 e:52 METHOD
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/mri_cache_backend.rb:19
  c:0008 p:0015 s:0048 e:47 METHOD
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:64
  c:0007 p:0058 s:0041 e:40 METHOD
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:358
  c:0006 p:0067 s:0030 e:29 BLOCK 
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:387
  [FINISH]
  c:0005 p: s:0026 e:25 CFUNC  :times
  c:0004 p:0027 s:0023 e:22 METHOD
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:381
  c:0003 p:0074 s:0014 e:13 METHOD
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:343
  c:0002 p:0026 s:0004 e:03 BLOCK 
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:330
  [FINISH]
  c:0001 p: s:0002 e:01 TOP[FINISH]
  
  -- Ruby level backtrace information
  
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:330:in
  `block (2 levels) in run_thread_loop'
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:343:in
  `setup_sync_and_start_loop'
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:381:in
  `_add_remove_indiscriminate_loop_outer_multiple_keys'
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:381:in
  `times'
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:387:in
  `block in _add_remove_indiscriminate_loop_outer_multiple_keys'
  /tmp/buildd/ruby-thread-safe-0.3.3/test/test_cache_loops.rb:358:in
  `_add_remove_indiscriminate_loop_inner_multiple_keys'
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:64:in
  `put_if_absent'
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/mri_cache_backend.rb:19:in
  `compute_if_absent'
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/non_concurrent_cache_backend.rb:10:in
  `[]'
  
/tmp/buildd/ruby-thread-safe-0.3.3/debian/ruby-thread-safe/usr/lib/ruby/vendor_ruby/thread_safe/non_concurrent_cache_backend.rb:10:in
  `[]'
  
  -- C level backtrace information
  ---
  /usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1(+0x18c9a7)
  [0x7fa0772949a7]
  /usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1(+0x18ca73)
  [0x7fa077294a73]
  /usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1(+0x6d633)
  [0x7fa077175633]
  /usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1(rb_bug+0xb3)
  [0x7fa077175ca3]
  

Bug#816586: marked as done (ruby-riddle: FTBFS: sphinx.rb:28:in `setup_mysql': uninitialized constant Sphinx::Mysql2 (NameError))

[Debian Bug Tracking System]

Your message dated Fri, 4 Mar 2016 22:10:45 +0100
with message-id <20160304211045.ga28...@percival.namespace.at>
and subject line Re: #816586: ruby-riddle: FTBFS
has caused the Debian Bug report #816586,
regarding ruby-riddle: FTBFS: sphinx.rb:28:in `setup_mysql': uninitialized 
constant Sphinx::Mysql2 (NameError)
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.)


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

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

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/debian/ruby-riddle/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-riddle/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*_spec.rb
  
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/support/sphinx.rb:28:in
 `setup_mysql': uninitialized constant Sphinx::Mysql2 (NameError)
from 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/spec_helper.rb:11:in
 `block in '
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/spec_helper.rb:7:in
 `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/riddle_spec.rb:1:in
 `'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `'
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/debian/ruby-riddle
 returned exit code 1
  debian/rules:16: 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-riddle.1.5.12-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Control: fixed -1 ruby-riddle/1.5.12-3

Fixed this by making the testsuite actually work in the first place
instead of ignoring the result on 2.2.

Thank you for your report!

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  ` End Message ---

Processed: forcibly merging 815107 810958

[Debian Bug Tracking System]

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

> forcemerge 815107 810958
Bug #815107 {Done: Cédric Boutillier } [ruby-celluloid-fsm] 
ruby-celluloid-fsm: FTBFS - Could not find 'timers' (~> 4.0.0) - did find: 
[timers-4.1.1]
Bug #810958 [ruby-celluloid-fsm] ruby-celluloid-fsm: FTBFS: `to_specs': Could 
not find 'timers' (~> 4.0.0) - did find: [timers-4.1.1] (Gem::LoadError)
Marked Bug as done
Marked as fixed in versions ruby-celluloid-fsm/0.20.5-1.
Marked as found in versions ruby-celluloid-fsm/0.20.0-2.
Merged 810958 815107
> thanks
Stopping processing here.

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

Processed: reassign 810958 to ruby-celluloid-fsm

[Debian Bug Tracking System]

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

> reassign 810958 ruby-celluloid-fsm
Bug #810958 [src:ruby-celluloid-fsm] ruby-celluloid-fsm: FTBFS: `to_specs': 
Could not find 'timers' (~> 4.0.0) - did find: [timers-4.1.1] (Gem::LoadError)
Bug reassigned from package 'src:ruby-celluloid-fsm' to 'ruby-celluloid-fsm'.
No longer marked as found in versions ruby-celluloid-fsm/0.20.0-2.
Ignoring request to alter fixed versions of bug #810958 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 816161

[Debian Bug Tracking System]

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

> tags 816161 + confirmed
Bug #816161 [src:ruby-awesome-print] ruby-awesome-print: FTBFS: Aborted (core 
dumped)
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 815107 810958

[Debian Bug Tracking System]

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

> forcemerge 815107 810958
Bug #815107 {Done: Cédric Boutillier } [ruby-celluloid-fsm] 
ruby-celluloid-fsm: FTBFS - Could not find 'timers' (~> 4.0.0) - did find: 
[timers-4.1.1]
Unable to merge bugs because:
package of #810958 is 'src:ruby-celluloid-fsm' not 'ruby-celluloid-fsm'
Failed to forcibly merge 815107: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: bug 816161 is forwarded to https://bugs.ruby-lang.org/issues/12137

[Debian Bug Tracking System]

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

> forwarded 816161 https://bugs.ruby-lang.org/issues/12137
Bug #816161 [src:ruby-awesome-print] ruby-awesome-print: FTBFS: Aborted (core 
dumped)
Set Bug forwarded-to-address to 'https://bugs.ruby-lang.org/issues/12137'.
> thanks
Stopping processing here.

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

Bug#815451: initramfs-tools: Fails to install without busybox (Depends vs. Recommends)

[Ben Hutchings]

On Fri, 2016-03-04 at 09:03 +0900, Olaf Meeuwissen wrote:
[...]
> The initramfs.conf file says:
> 
> > 
> > # BUSYBOX: [ y | n ]
> > #
> > # Use busybox if available
> > #
> > 
> > BUSYBOX=y
> Something does not make sense unless there is a typo, s/not/now/, in
> Ben's initial comment.
> 
> I use the default initramfs.conf since my initial install.  I upgrade to
> initramfs-tools 0.123 and stuff breaks.  You definitely have a non-clean
> upgrade path here.

On the contrary, the default initramfs.conf has changed BUSYBOX=y to
BUSYBOX=auto.  You chose not to accept that.

> I'll fix my initramfs.conf manually but default setups that suddenly can
> no longer create initramfs images is scary at best.
> 
> Please make the postinst modify initramfs.conf to disable busybox unless
> available.  While at it, also update the comment.
[...]

I did that too.

Ben.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai Stevenson

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

Bug#816744: ruby-jeweler: missing dependencies

[Cédric Boutillier]

Package: ruby-jeweler
Version: 2.0.1-1
Severity: serious
Justification: cannot work without the correct dependencies

Hi!

Checking the Gemfile and the require statements contained in the files
of this package, I see that some dependencies are missing (and are even
not packaged): ruby-git and ruby-github-api (built from git and
github_api Ruby gems respectively).

Please package these and fix dependencies if you want to keep this
package in the archive.

Cheers,

Cédric

Bug#816742: libc6: sem_post/sem_wait not working for 32bit to 64bit inter-process communication

[Markus Friedrich]

Package: libc6
Version: 2.21
Severity: critical
Justification: breaks unrelated software

Inter-process communication between a 64bit and a 32bit process is not
working. At least pthread named semaphores are not working.
A sem_wait is not awaken if a corresponding sem_post is done on the other
side, which generated a dead lock.

This problem only exists if a 64bit process communicates with a 32bit
process but not for 32bit to 32bit communication or 64bit to 64bit
communication.
Moreover Debian 8.3 and all other tested distributions have no problem with
64bit to 32bit inter-process communication using pthread named semaphores.

The problem seems to be related to the (new) FUTEX_PRIVATE_FLAG flag of
futex. The sem_post command (for a named semaphore) seems to make a futex
system call using the FUTEX_PRIVATE_FLAG which seems to be wrong.

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

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

Bug#816739: rsyslog-gnutls: imtcp/TLS hangs on dropped packages

[Luca Bruno]

Package: rsyslog-gnutls
Version: 8.4.2-1+deb8u2
Severity: grave
Tags: patch upstream
Justification: causes non-serious data loss

I have a log-aggregating server using rsyslog to receive multiple
streams (both UDP and TCP), including some remote logs via TLS.

I'm experiencing a lock of the TLS receiver under normal usage,
and consequently the TLS-receiving thread of rsyslog using 100% CPU.

After some initial debugging, this seems to be the same upstream bug
as reported here: https://github.com/rsyslog/rsyslog/issues/318

This has been fixed in the latest upstream version:
https://github.com/rsyslog/rsyslog/pull/494

I think this basically affects all setups where rsyslog is used
as a TLS receiver, and results in losing logs on the receiving side
(and increased buffer pressure on senders).
Thus I'm reporting this at severity grave.
It would be great if this could be fixed for current stable version,
as rsyslog-gnutls is too buggy for production usage at the moment.

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

Kernel: Linux 4.3.0-0.bpo.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 rsyslog-gnutls depends on:
ii  libc6  2.19-18+deb8u3
ii  libgnutls-deb0-28  3.3.8-6+deb8u3
ii  libjson-c2 0.11-4
ii  rsyslog8.4.2-1+deb8u2

rsyslog-gnutls recommends no packages.

Versions of packages rsyslog-gnutls suggests:
ii  gnutls-bin  3.3.8-6+deb8u3

-- no debconf information

Bug#815666: Duplicate of #814982

[Lorenz Hübschle-Schneider]

Yes, that certainly seems possible as I mentioned in my initial
report. However, I can exclude the possibility of it being a duplicate
of #813687 after the upgrade to mutter 3.18.3.

Bug#816737: Broken after recent upgrade

[Philipp Klaus Krause]

Package: libc6
Severity: Serious

Yesterday, I tred to upgrade libc6 on my Debian GNU/testing system. But
it didn't work. The packages are marked as broken in synaptic. Today, I
tried apt-get -f install, but it fails too:

root@notebook4:/home/philipp# LANG=C apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer
required:
  gtk2-engines libglewmx1.10 libgtkglext1-dev libintl-perl libjsoncpp0v5
libopenraw1v5 libpangox-1.0-dev libsigc++-1.2-5c2 libusb-1.0-0:i386
lockfile-progs
  qemu-kvm
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libc6 libc6:i386 libc6-i686:i386
Suggested packages:
  glibc-doc glibc-doc:i386 libc-l10n:i386 locales:i386
The following packages will be upgraded:
  libc6 libc6:i386 libc6-i686:i386
3 upgraded, 0 newly installed, 0 to remove and 950 not upgraded.
4 not fully installed or removed.
Need to get 0 B/6181 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
debconf: Perl may be unconfigured (Unknown regexp modifier "/g" at
/usr/share/perl/5.22/Text/Wrap.pm line 31, at end of line
BEGIN not safe after errors--compilation aborted at
/usr/share/perl/5.22/Text/Wrap.pm line 35.
Compilation failed in require at /usr/share/perl5/Debconf/Template.pm
line 10.
BEGIN failed--compilation aborted at
/usr/share/perl5/Debconf/Template.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm
line 8.
BEGIN failed--compilation aborted at
/usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm
line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at (eval 1) line 4.
BEGIN failed--compilation aborted at (eval 1) line 4.
) -- aborting
(Reading database ... 388478 files and directories currently installed.)
Preparing to unpack .../libc6_2.21-9_amd64.deb ...
De-configuring libc6:i386 (2.21-8) ...
Unknown regexp modifier "/g" at /usr/share/perl/5.22/Text/Wrap.pm line
31, at end of line
BEGIN not safe after errors--compilation aborted at
/usr/share/perl/5.22/Text/Wrap.pm line 35.
Compilation failed in require at /usr/share/perl5/Debconf/Template.pm
line 10.
BEGIN failed--compilation aborted at
/usr/share/perl5/Debconf/Template.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm
line 8.
BEGIN failed--compilation aborted at
/usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm
line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing archive
/var/cache/apt/archives/libc6_2.21-9_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 255
Preparing to unpack .../archives/libc6_2.21-9_i386.deb ...
De-configuring libc6:amd64 (2.21-8) ...
Unknown regexp modifier "/g" at /usr/share/perl/5.22/Text/Wrap.pm line
31, at end of line
BEGIN not safe after errors--compilation aborted at
/usr/share/perl/5.22/Text/Wrap.pm line 35.
Compilation failed in require at /usr/share/perl5/Debconf/Template.pm
line 10.
BEGIN failed--compilation aborted at
/usr/share/perl5/Debconf/Template.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm
line 8.
BEGIN failed--compilation aborted at
/usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm
line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing archive
/var/cache/apt/archives/libc6_2.21-9_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 255
Processing triggers for libc-bin (2.21-9) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.21-9_amd64.deb
 /var/cache/apt/archives/libc6_2.21-9_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Philipp

P.S.: How can I get my system back into a useable state? Since the

Bug#815104: tag 815104 + fixed pending

[Benoit Mortier]

-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Bug#816357: jedit: FTBFS: XThis.java:128: error: cannot find symbol [..] NotSerializableException

[Markus Koschany]

Am 04.03.2016 um 14:40 schrieb tony mancill:
[...]
>> Hi tony,
>>
>> I can upload a new revision of bsh with this change later. I'm just wondering
>> why we need to use java.io.ObjectStreamException and
>> java.io.NotSerializableException explicitly because these classes are already
>> imported in bsh's XThis.java.
>>
>> import java.io.*;
>>
>> Anyway it doesn't change the intention of the patch and should be safe.
> 
> Hi Markus,
> 
> I ask myself that same question, and intend to look it up.  Perhaps
> because it's a nested inner class of XThis?
> 
> But one of the clues was that the original code specified the full class
> name for java.io.Serializable and not just Serializable.
> 
> I agree that it shouldn't affect the intention of patch and should be
> safe, but it is a bit puzzling.

I have just uploaded bsh with this change.

Cheers,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#816357: jedit: FTBFS: XThis.java:128: error: cannot find symbol [..] NotSerializableException

[Markus Koschany]

On Thu, 03. Mar 22:30 tony mancill  wrote:
> On 03/03/2016 12:49 PM, Markus Koschany wrote:
> > Am 03.03.2016 um 05:03 schrieb tony mancill:
> >> Control: -1 tag  + confirmed
> >> Control: -1 owner tmanc...@debian.org
> >>
> >> On 02/29/2016 11:05 PM, Chris Lamb wrote:
> >>> Source: jedit
> >>> Version: 5.3.0+dfsg-1
> >>> Severity: serious
> >>> Justification: fails to build from source
> >>
> >>>   [javac] 
> >>> /home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg/org/gjt/sp/jedit/bsh/XThis.java:128:
> >>>  error: cannot find symbol
> >>>   [javac] throw new NotSerializableException();
> >>
> >> Thanks for the bug report.  Looks like we have a bit of porting for the
> >> latest bsh upload.
> >>
> >
> > Sorry for the inconvenience. If there is more involved than importing
> > the missing class, please let me know and I try to fix it.
>
> Hi Markus,
>
> No inconvenience at all. The issue seems to be with the upstream patch
> for CVE-2016-2510, which drops the java.io.Serializable interface from
> the InvocationHandler, but then references the ObjectStreamException and
> NotSerializableException classes that package.
>
> I was able to get things working for jedit by applying the following
> patch (also attached), building a new bsh-src package locally, and using
> that for the jedit build.
>
> > diff -Nru bsh-2.0b4/debian/patches/CVE-2016-2510.patch 
> > bsh-2.0b4/debian/patches/CVE-2016-2510.patch
> > --- bsh-2.0b4/debian/patches/CVE-2016-2510.patch2016-03-02 
> > 20:24:07.0 -0800
> > +++ bsh-2.0b4/debian/patches/CVE-2016-2510.patch2016-03-03 
> > 22:10:57.0 -0800
> > @@ -35,8 +35,8 @@
> >  -  class Handler implements InvocationHandler, java.io.Serializable
> >  +  class Handler implements InvocationHandler
> > {
> > -+  private Object readResolve() throws ObjectStreamException {
> > -+  throw new NotSerializableException();
> > ++  private Object readResolve() throws 
> > java.io.ObjectStreamException {
> > ++  throw new java.io.NotSerializableException();
> >  +  }
> >  +
>
> So, if you're okay with the patch, could you apply it and upload an
> updated bsh?  Or do you mind if I do?

Hi tony,

I can upload a new revision of bsh with this change later. I'm just wondering
why we need to use java.io.ObjectStreamException and
java.io.NotSerializableException explicitly because these classes are already
imported in bsh's XThis.java.

import java.io.*;

Anyway it doesn't change the intention of the patch and should be safe.

Cheers,

Markus



signature.asc
Description: Digital signature

Bug#802812: gstreamer0.10 0.10.36-1.5 MIGRATED to testing

[Emilio Pozuelo Monfort]

On 03/03/16 23:00, Micha Lenk wrote:
> Hi,
> 
> Given Debian bug #802812 is open, the migration of gstreamer0.10 0.10.36-1.5 
> to testing just one day after its removal seems to be unintended.

Yes, that was unintended and due to the fact that #802812 was tagged "stretch".
I removed the package from testing once again and dropped that tag, so from now
on the package should stay out of testing.

Cheers,
Emilio

Bug#814944: [debian-mysql] Bug#814944: mariadb-connect-engine-10.0: ODBC support apparently not compiled in

[Otto Kekäläinen]

Tracked upstream as https://jira.mariadb.org/browse/MDEV-9684

Bug#815451: initramfs-tools: Fails to install without busybox (Depends vs. Recommends)

[Olaf Meeuwissen]

Just got bit by this this morning.

Ben Hutchings said:
> busybox is not required by the default configuration.  See the NEWS
> file.

OK, I check the NEWS file.  That says (for 0.121~rc1):

> If initramfs-tools is configured to use busybox but it is not
> installed, mkinitramfs will now fail.

Next I check my /etc/initramfs-tools/initramfs.conf.  I have kept my
/etc/ in git with etckeeper since the system's initial install.  The
file has never been changed since the initial install (2014-03-27,
network-less standard base install from Debian 7.4.0 netinst CD ISO,
initramfs-tools-0.109.1; switched to testing later).

The initramfs.conf file says:

> # BUSYBOX: [ y | n ]
> #
> # Use busybox if available
> #
>
> BUSYBOX=y

Something does not make sense unless there is a typo, s/not/now/, in
Ben's initial comment.

I use the default initramfs.conf since my initial install.  I upgrade to
initramfs-tools 0.123 and stuff breaks.  You definitely have a non-clean
upgrade path here.

I'll fix my initramfs.conf manually but default setups that suddenly can
no longer create initramfs images is scary at best.

Please make the postinst modify initramfs.conf to disable busybox unless
available.  While at it, also update the comment.  Another option is to
really do what that comment says, i.e. fix initramfs-tools to test for
busybox at run-time if BUSYBOX=y and act as if BUSYBOX=n when not found.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- EPSON AVASYS CORPORATION
   Free Software Foundation Associate Member since 2004-01-27
Support Free Software  https://my.fsf.org/donate
Join the Free Software Foundationhttps://my.fsf.org/join

Bug#799919: marked as done (asused stopped working because changed fields are missing in newer objects)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 19:19:23 +
with message-id 
and subject line Bug#799919: fixed in asused 3.72-12
has caused the Debian Bug report #799919,
regarding asused stopped working because changed fields are missing in newer 
objects
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.)


-- 
799919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asused
Version: 3.72-11
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
 Rabe obsoletes the changed field and added the created field. Asused re

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I changed the in.pm module to lokk ad cr instead of ch attribute

   * What was the outcome of this action?

 It works now again :-)

   * What outcome did you expect instead?





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

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

Versions of packages asused depends on:
ii  perl  5.20.2-6

asused recommends no packages.

asused suggests no packages.

-- no debconf information
--- in.pm.orig	2015-09-24 10:13:26.412669531 +0200
+++ in.pm	2015-09-24 10:26:50.724168595 +0200
@@ -355,6 +355,10 @@
 		# Changed
 		push(@{$in{'ch'}}, $value);
 		}
+		elsif($inetnum && $attr eq 'cr') {
+		# Created
+		push(@{$in{'cr'}}, $value);
+		}
 		elsif($inetnum && $attr eq 'so') {
 		# Source
 		$in{'so'} = $value;
@@ -373,14 +377,14 @@
 # Get creation date for valid inetnum object
 if($inetnum) {
 # Validate date
-my $date = $self->creationDate(@{$in{'ch'}});
+my $date = $self->creationDate(@{$in{'cr'}});
 	
 if($date) {
 $in{'created'} = $date;
 }
 else {
 $self->error($INVALID_DATE, 
- ("Invalid date in " . join('; ', @{$in{'ch'}})));
+ ("Invalid date in " . join('; ', @{$in{'cr'}})));
 
 push(@{$in{'warning'}}, ($self->error())[1]);
 }
@@ -560,7 +564,7 @@
 my @dateList;
 #don't trust the date from db
 foreach my $dateStr (@ch) {
-	if($dateStr =~ /(\d+)$/) {
+	if($dateStr =~ /([\d\-]+)(T.*)?$/) {
 	my $date = $1;
 return  unless ($date = checkmmDD($date)) ; #look if it is valid date
 push(@dateList, $date); #make list of valid dates
@@ -583,6 +587,8 @@
 my($yy, $mm, $dd, $utc, $yyActual, $mmActual, $ddActual, $date);
 my($sec, $min, $hour, $wday, $yday, $isdst); # Temp vars
 	
+	$MMdd =~ s/\-//g;
+	
 #MMDD
 if($MMdd =~ /^(\d{4})(\d{2})(\d{2})$/) {
 $yy = $1 - 1900;
@@ -655,6 +661,7 @@
   $dest->{'ac'} = []; # list of admin-c values
   $dest->{'tc'} = []; # list of tech-c values
   $dest->{'ch'} = []; # list of changed values
+  $dest->{'cr'} = []; # list of created values
   $dest->{'so'} = ''; # source 
   $dest->{'ml'} = []; # list of mnt-lower
   $dest->{'na'} = ''; # netname
--- End Message ---
--- Begin Message ---
Source: asused
Source-Version: 3.72-12

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated asused 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, 04 Mar 2016 15:52:16 -0300
Source: asused
Binary: asused
Architecture: source all
Version: 3.72-12
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Badia 
Changed-By: Sebastien Badia 
Description:
 

Bug#813359: xserver-xorg-input-aiptek: Compilation fails due to API change in xorg

[Julien Cristau]

On Thu, Mar  3, 2016 at 21:36:38 +0100, Tobias Schlemmer wrote:

> Package: xserver-xorg-input-aiptek
> Version: 1:1.4.1-1
> Followup-For: Bug #813359
> 
> Hi,
> 
> I got the driver to get compiled. The extra arguments are not used any more 
> and
> have been removed from xorg.
> 
Hi Tobias,

is the aiptek tablet not supported by any of the better maintained
drivers (libinput/evdev/wacom)?

Thanks,
Julien

Bug#815104: tag 815104 - patch

[Benoit Mortier]

-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Processed: tagging 813359

[Debian Bug Tracking System]

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

> tags 813359 + upstream patch
Bug #813359 [src:xserver-xorg-input-aiptek] xserver-xorg-input-aiptek: FTBFS: 
xf86Aiptek.c:296:17: error: too many arguments to function 'xf86PostKeyEvent'
Added tag(s) upstream and patch.
> thanks
Stopping processing here.

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

Bug#816699: [Debichem-devel] Bug#816699: libga-dev and libarmci-mpi-dev: error when trying to install together

[Michael Banck]

Hi,

On Fri, Mar 04, 2016 at 06:30:01AM +0100, Ralf Treinen wrote:
> 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 libarmci-mpi-dev.
> (Reading database ... 10939 files and directories currently installed.)
> Preparing to unpack .../libarmci-mpi-dev_0.0~git20160222-1_amd64.deb ...
> Unpacking libarmci-mpi-dev (0.0~git20160222-1) ...
> Selecting previously unselected package libga-dev.
> Preparing to unpack .../libga-dev_5.4~beta~r10636+dfsg-2_amd64.deb ...
> Unpacking libga-dev (5.4~beta~r10636+dfsg-2) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libga-dev_5.4~beta~r10636+dfsg-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/libarmci.a', which is also in 
> package libarmci-mpi-dev 0.0~git20160222-1
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/libga-dev_5.4~beta~r10636+dfsg-2_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Thanks for the report.  I guess it makes sense considering armci-mpi is
a reimplementation oft the libarmci.a library in GA.

The mid-term plan is to build GA against libarmci-dev, I guess we
should remove or rename the internal libarmci.a (plus its headers) from
libga-dev.


Michael

Bug#785714: kexec-tools is broken when using systemd, danger of filesystem corruption

[Daniel Baumann]

On 2016-03-03 21:48, Khalid Aziz wrote:

Is this issue happening for you on jessie or sid? Your original bug
report said Debian 8.0, so I have been focusing on jessie.


it happens on both, but primarily I'm testing sid.

Regards,
Daniel

Bug#814183: openmpi 1.10.2 is broken on powerpc

[Graham Inggs]

On 3 March 2016 at 13:47, Emilio Pozuelo Monfort  wrote:
> Might be related to #813722 / #814183.

Definitely.

ELPA built on poulenc and praetorius, but failed on powerpc-osuosl-01:

https://buildd.debian.org/status/logs.php?pkg=elpa=powerpc

Only looking at elpa >= 2015.05.001-1 since openmpi 1.10, and ignoring
failures quicker than 2.5 hours due to bugs in packaging.

Bug#815104: fusiondirectory: FTBFS due to patch fuzz

[Benoit Mortier]

On Thu, 18 Feb 2016 12:40:14 -0800 Nishanth Aravamudan
 wrote:
> Source: fusiondirectory
> Version: 1.0.8.8-3
> Severity: serious
> Tags: patch
> Justification: fails to build from source
> 
> Dear Maintainer,
> 
> While working on the PHP7.0 migration with Ubuntu, I ran into:
> 
> dpkg-source: info: building fusiondirectory using existing 
> ./fusiondirectory_1.0.8.8.orig-core.tar.gz 
> ./fusiondirectory_1.0.8.8.orig-plugins.tar.gz 
> ./fusiondirectory_1.0.8.8.orig.tar.gz
> patching file core/contrib/apache/fusiondirectory-apache.conf
> Hunk #1 FAILED at 1.
> 1 out of 1 hunk FAILED
> dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
> dpkg-source: info: if patch '2001_fusiondirectory-apache.patch' is correctly 
> applied by quilt, use 'quilt refresh' to update it
> 
> I believe this only is noticed now because the package hasn't been
> rebuilt recently?

hello,

fixed in the next pending upload.

Thanks for the report

-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Bug#816726: [youtube-dl] doesn't even start

[Alex Volkov]

Package: youtube-dl
Version: 2016.02.22-1
Severity: grave

--- Please enter the report below this line. ---

Gives me this in response to "youtube-dl --version"

Traceback (most recent call last):
  File "/usr/bin/youtube-dl", line 5, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
3138, in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
3124, in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
3151, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 652, 
in _build_master
ws = cls()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 645, 
in __init__
self.add_entry(entry)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 701, 
in add_entry
for dist in find_distributions(entry, True):
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2139, in find_on_path
path_item, entry, metadata, precedence=DEVELOP_DIST
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2521, in from_location
py_version=py_version, platform=platform, **kw
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2835, in _reload_version
md_version = _version_from_file(self._get_metadata(self.PKG_INFO))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2486, in _version_from_file
line = next(iter(version_lines), '')
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2654, in _get_metadata
for line in self.get_metadata_lines(name):
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2030, in get_metadata_lines
return yield_lines(self.get_metadata(name))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2025, in get_metadata
metadata = f.read()
  File "/usr/lib/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: 
invalid start byte



--- System information. ---
Architecture: amd64
Kernel:   Linux 4.3.0-1-amd64

Debian Release: stretch/sid
  990 stable  security.debian.org 
  990 stable  ftp.fi.debian.org 
  500 testing security.debian.org 
  500 testing ftp.fi.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
python-pkg-resources| 18.8-1
python (>= 2.7) | 2.7.11-1
python (<< 2.8) | 2.7.11-1


Recommends(Version) | Installed
===-+-
libav-tools | 
 OR ffmpeg  | 7:2.8.6-1+b1
libav-tools | 
 OR ffmpeg  (>= 4:0.6)  | 7:2.8.6-1+b1
 OR ffprobe | 
mplayer2| 2.0-728-g2c378c7-4+b2
 OR mplayer | 
rtmpdump| 2.4+20151223.gitfa8646d-1+b1


Package's Suggests field is empty.

Bug#816719: chealpix: FTBFS on mips: timed out

[Emilio Pozuelo Monfort]

Source: chealpix
Version: 3.11.4-2
Severity: serious

Your package failed to build on mips after 720 minutes of inactivity:

Log at

https://buildd.debian.org/status/fetch.php?pkg=chealpix=mips=3.11.4-2%2Bb1=1456747053

Emilio

Bug#815742: verbiste: diff for NMU version 0.1.42-2.1

[Tomasz Buchert]

On 03/03/16 08:23, Raúl Benencia wrote:
> Hi Tomasz,
> 
> On Thu, Mar 03, 2016 at 10:42:32AM +0100, Tomasz Buchert wrote:
> > thank you very much for this! Can you explain what the problem is? I
> > didn't have time to work on this recently. I'll upload the new version soon.
> 
> I'm glad to help! The patch it's pretty simple. The following test started
> failing recently:
> 
>   test "`echo asseoir | $(LU) ./french-conjugator | grep asseyerai,`" = 
> "assiérai, asseyerai, assoirai"
> 
> So, why did it started failing just now and no before? I did some research
> and the guilty turned out to be an update in the grep package, as it
> slightly changed its behaviour. With the new update, grep will detect the
> input as binary if it's in a different locale than the one it's currently
> running in. When this happens, grep will just output "binary file matches"
> instead of the line that matches the pattern, provoking a failure in the
> test.
> 
> Now, if you see the build log, the environment variable LU expands to
> LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8. That means, that
> no matter what, french-conjugator will produce its stdout with that
> encoding. So grep have to use the same encoding, and that's why I set up
> those variables in the override. Now, we can't assume that the encoding is
> installed on the build machine, so that's why I generate the locale. Piece
> of cake!
> 
> Cheers,
> Rul

Wow, this is surpring how they changed grep! Ok, I'm uploading this.

Tomasz


signature.asc
Description: PGP signature

Bug#812087: [pcscd]

[Ludovic Rousseau]

On Thu, 3 Mar 2016 09:30:36 +0100 Philippe Teuwen  wrote:

Hi Ludovic,


Hello Philippe,


I'm getting the same problem with my Debian Testing.

I'll try to generate more logs related to libusb as explained in the bug
thread but here are some things I noticed:


I also suspect a bug in libudev, not just libusb.

Can you rebuild pcscd as explained in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087#75 to enable libudev 
logs?


I've a Yubikey Neo-n plugged constantly.

When the 100% problem arises, nothing special in pcscd logs, even with
-f -a -d
cf attached log.
And pcscd and Yubikey remain fully functional despite the 100%.

Now the interesting bits:

Without the yubikey inserted the problem never occurs.

With the yubikey inserted there are two cases:

1) works as normal, the problem never arises

2) sometimes when yubikey gets inserted or when pcscd service is
restarted I get the following error in syslog:

pcscd[26168]:  ifdhandler.c:144:CreateChannelByNameOrChannel()
failed
pcscd[26168]: 0012 readerfactory.c:1097:RFInitializeReader() Open
Port 0x20 Failed (usb:1050/0115:libudev:0:/dev/bus/usb/001/025)
pcscd[26168]: 0002 readerfactory.c:372:RFAddReader() Yubico Yubikey
NEO U2F+CCID init failed.


What version of libccid do you use?

What was the pcscd log line just before CreateChannelByNameOrChannel() failed?


At this point besides those lines in syslog, yubikey is functional and
CPU is ok *but* starting from this situation, whenever there will be a
change on another usb port, no matter what (inserting or removing
anything, even a simple USB hub) => CPU goes to 100%
Restarting pcscd brings CPU back to normal till another USB
insert/remove event.


That is really interesting.

You can reproduce the problem even after a complete restart of pcscd.
So the problem may not be in libusb or pcscd but in libudev or another "system" 
component used by pcscd.

Another idea is to attach a debugger to pcscd and get a backtrace of all the 
threads when the CPU goes 100%.
That could help identify the function or library causing the issue.

Thanks

--
Dr. Ludovic Rousseau

Bug#816715: python-astropy: FTBFS with libcfitsio4

[Emilio Pozuelo Monfort]

Source: python-astropy
Version: 1.1.1-3
Severity: serious

Your package failed to build on every architecture when rebuilt against
libcfitsio4:

with fits.open(self.temp('test.fits')) as hdul:
>   assert (hdul['SCI'].data == cube).all()
E   assert ()
E+  where  = array([[[   0...dtype=float32) == array([[[   0dtype=float32)
E   Detailed information truncated, use "-vv" to show.all

Logs at:

https://buildd.debian.org/status/logs.php?pkg=python-astropy=1.1.1-3%2Bb1

Emilio

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Matt Fleming]

On Tue, 01 Mar, at 01:03:22AM, Alexis Murzeau wrote:
> 
> I've updated my additional debug code to dump all entries of virtual_map
> when calling SetVirtualAddressMap. (new diff of my changes in attachment:
> additionnal_printk_dump_SetVirtualAddressMap.diff)
> 
> I've run 3 tests with and without
> patch_x86-efi-build-our-own-page-table-structures:
> - Without the patch and with "efi=debug" kernel command line
> (attachment: dmesg_without_patch_efi_debug.txt)
> 
> - With the patch and with "efi=no_map,debug" command line (no crash)
> (attachment: dmesg_with_patch_efi_old_map_debug.txt)
> 
> - With the patch with "efi=debug earlyprintk=efi,keep" (crash but
> with logs)
> (attachment: dmesg_with_patch_efi_debug_photos.zip)
> 
> All of these tests are using kernels with CONFIG_EFI_PGT_DUMP enabled
> but "efi=no_map" seems to make efi_dump_pagetable not printing anything.
> 
> There is a difference in the page table dump, not sure if could be the
> cause of the crash:
> Without the patch (in dmesg_without_patch_efi_debug.txt):
> 0xaa20-0xaa7bf000   5884K RW  GLB x  pte
> 0xaa7bf000-0xaaabf000  3M RW  x  pte
> With the patch (in dmesg_with_patch_efi_debug_08.png in the zip file):
> 0xaa20-0xaaabf000   8956K RW  x  pte

It must have been a herculean effort to take photos of the screen
while the buggy kernel booted. Thank you!

I'm not really seeing anything jumping out as obviously wrong apart
from the fact that we don't have all of EFI_CONVENTIONAL_MEMORY mapped
in the buggy kernel.

Could you try this patch?

---

diff --git a/arch/x86/platform/efi/efi_64.c b/arch/x86/platform/efi/efi_64.c
index 49e4dd4a1f58..f5e77d240ff1 100644
--- a/arch/x86/platform/efi/efi_64.c
+++ b/arch/x86/platform/efi/efi_64.c
@@ -241,15 +241,6 @@ int __init efi_setup_page_tables(unsigned long pa_memmap, 
unsigned num_pages)
efi_scratch.use_pgd = true;
 
/*
-* When making calls to the firmware everything needs to be 1:1
-* mapped and addressable with 32-bit pointers. Map the kernel
-* text and allocate a new stack because we can't rely on the
-* stack pointer being < 4GB.
-*/
-   if (!IS_ENABLED(CONFIG_EFI_MIXED))
-   return 0;
-
-   /*
 * Map all of RAM so that we can access arguments in the 1:1
 * mapping when making EFI runtime calls.
 */
@@ -268,6 +259,15 @@ int __init efi_setup_page_tables(unsigned long pa_memmap, 
unsigned num_pages)
}
}
 
+   /*
+* When making calls to the firmware everything needs to be 1:1
+* mapped and addressable with 32-bit pointers. Map the kernel
+* text and allocate a new stack because we can't rely on the
+* stack pointer being < 4GB.
+*/
+   if (!IS_ENABLED(CONFIG_EFI_MIXED))
+   return 0;
+
page = alloc_page(GFP_KERNEL|__GFP_DMA32);
if (!page)
panic("Unable to allocate EFI runtime stack < 4GB\n");

Processed: Re: openmpi 1.10.2 is broken on powerpc

[Debian Bug Tracking System]

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

> unmerge 813722
Bug #813722 [src:openmpi] aces3: FTBFS on powerpc
Bug #814183 [src:openmpi] openmpi 1.10.2 is broken on powerpc
Disconnected #813722 from all other report(s).
> thanks
Stopping processing here.

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

Bug#816040: severity 816040 important

[Benoit Mortier]

-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Bug#816040: fusiondirectory depends on php5-imagick which is no longer built

[Benoit Mortier]

On Fri, 26 Feb 2016 21:22:37 + peter green  wrote:
> Package: fusiondirectory
> Severity: serious
> Version: 1.0.8.8-3
> 
> fusiondirectory depends on php5-imagick which is no longer built by the 
> source package php-imagick.
> 
> I'm not sure if you can just change the dependency to php-imagick or if 
> more work is needed.

Hello,

after more test i will lower the severity to important because it still
work perfectly in php5 sid but don't work in php7 sid.

for php7 compatibility other packages need to be changed as well

Cheers
-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Bug#816582: marked as done (kodi-pvr-vuplus: FTBFS: client.cpp:339:18: error: 'PVR_ADDON_CAPABILITIES {aka struct PVR_ADDON_CAPABILITIES}' has no member named 'bSupportsRecordingFolders')

[Debian Bug Tracking System]

Your message dated Thu, 03 Mar 2016 23:38:46 +
with message-id 
and subject line Bug#816582: fixed in kodi-pvr-vuplus 1.11.10+git20160220-1
has caused the Debian Bug report #816582,
regarding kodi-pvr-vuplus: FTBFS: client.cpp:339:18: error: 
'PVR_ADDON_CAPABILITIES {aka struct PVR_ADDON_CAPABILITIES}' has no member 
named 'bSupportsRecordingFolders'
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.)


-- 
816582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi-pvr-vuplus
Version: 1.10.7+git20150717-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,

kodi-pvr-vuplus fails to build from source in unstable/amd64:

  [..]

  
/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/src/client.cpp:
 In function 'PVR_ERROR GetAddonCapabilities(PVR_ADDON_CAPABILITIES*)':
  
/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/src/client.cpp:339:18:
 error: 'PVR_ADDON_CAPABILITIES {aka struct PVR_ADDON_CAPABILITIES}' has no 
member named 'bSupportsRecordingFolders'
 pCapabilities->bSupportsRecordingFolders   = true;
^
  CMakeFiles/pvr.vuplus.dir/build.make:65: recipe for target 
'CMakeFiles/pvr.vuplus.dir/src/client.cpp.o' failed
  make[3]: *** [CMakeFiles/pvr.vuplus.dir/src/client.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:102: recipe for target 'CMakeFiles/pvr.vuplus.dir/all' 
failed
  make[2]: *** [CMakeFiles/pvr.vuplus.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/obj-x86_64-linux-gnu'
  Makefile:152: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/obj-x86_64-linux-gnu'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:12: 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
   `-


kodi-pvr-vuplus.1.10.7+git20150717-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: kodi-pvr-vuplus
Source-Version: 1.11.10+git20160220-1

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated kodi-pvr-vuplus 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Mar 2016 14:44:41 +0100
Source: kodi-pvr-vuplus
Binary: kodi-pvr-vuplus
Architecture: source
Version: 1.11.10+git20160220-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi-pvr-vuplus - Vu+/Enigma2 PVR Addon for Kodi
Closes: 808751 816582
Changes:
 kodi-pvr-vuplus (1.11.10+git20160220-1) unstable; urgency=medium
 .
   * Imported Upstream version 1.11.10+git20160220 (Closes: #816582)
   * Bump standards version to 3.9.7
   * Switch to p8-platform from (cec-)platform
   * Extend package description (Closes: #808751)
Checksums-Sha1:
 833f5fdc2e74584dcd4bad8640ddb29adfdc33b0 2184 
kodi-pvr-vuplus_1.11.10+git20160220-1.dsc
 7e8719f60171b49fd1b9b1338f6989e127e0b4ba 67640 
kodi-pvr-vuplus_1.11.10+git20160220.orig.tar.xz
 cc71bd1a72d4d253d14ed24875bda486a9c7d3f0 3472 
kodi-pvr-vuplus_1.11.10+git20160220-1.debian.tar.xz
Checksums-Sha256:
 aa9d42e84be252d8f2d7e3611877b64f55d1cb3a14845c7a3dd3e0f41868568c 2184 

Bug#788108: Processed: severity of 788108 is serious, tagging 788108

[Lisandro Damián Nicanor Pérez Meyer]

On Monday 22 February 2016 11:45:56 Lisandro Damián Nicanor Pérez Meyer wrote:
> It was discussed in upstream's mailing list, but I'm on the phone now :(

According to 5.6.0's git repo:

 - [QTBUG-40702] Removed dependency towards libgeoclue. The plugin uses the
   GeoClue DBus interface.

I'm now working to disable the support in 5.5.1 to close this bug ASAP. We 
need to understand what we will need to depend upon for 5.6.

Laurent: does it rings you any bells?

-- 
 AlfaScorpii: podés converncerla a tu vieja que le esconda
el diccionario a el_machi? Cada vez que aprende una palabra nueva
busca cualquier excusa para usarla
 e-squizo: leí mi primer diccionario a los 5 años
[...]
 e-squizo: como mi vieja no aprenda lo suficiente de
hacking no veo como haria para bajar el sitio de la real academia
  Visto en #grulic, irc.freenode.net

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


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

Bug#816579: marked as done (arachne-pnr: FTBFS: src/chipdb.cc:852: void ChipDB::finalize(): Assertion `tile_pos_cell[t][pos] == 0' failed.)

[Debian Bug Tracking System]

Your message dated Thu, 03 Mar 2016 23:36:14 +
with message-id 
and subject line Bug#816579: fixed in arachne-pnr 0.1+20151224git1a4fdf9-1
has caused the Debian Bug report #816579,
regarding arachne-pnr: FTBFS: src/chipdb.cc:852: void ChipDB::finalize(): 
Assertion `tile_pos_cell[t][pos] == 0' failed.
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.)


-- 
816579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arachne-pnr
Version: 0~20150927gitefdb026-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,

arachne-pnr fails to build from source in unstable/amd64:

  [..]

  g++ -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
-Isrc -std=c++11 -Wall -Wshadow -Wsign-compare -Werror -fPIE -pie -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed -o bin/arachne-pnr src/arachne-pnr.o src/netlist.o 
src/blif.o src/pack.o src/place.o src/util.o src/io.o src/route.o src/chipdb.o 
src/location.o src/configuration.o src/line_parser.o src/pcf.o src/global.o 
src/constant.o src/designstate.o -lm
  mkdir -p share/arachne-pnr
  bin/arachne-pnr -d 1k -c /usr/share/fpga-icestorm/chipdb/chipdb-1k.txt 
--write-binary-chipdb share/arachne-pnr/chipdb-1k.bin
  seed: 1
  device: 1k
  read_chipdb /usr/share/fpga-icestorm/chipdb/chipdb-1k.txt...
  arachne-pnr: src/chipdb.cc:852: void ChipDB::finalize(): Assertion 
`tile_pos_cell[t][pos] == 0' failed.
  Makefile:25: recipe for target 'share/arachne-pnr/chipdb-1k.bin' failed
  make[1]: *** [share/arachne-pnr/chipdb-1k.bin] Aborted (core dumped)
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160303075549.jMwsadjjqr/arachne-pnr-0~20150927gitefdb026'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:11: 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
   `-


arachne-pnr.0~20150927gitefdb026-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: arachne-pnr
Source-Version: 0.1+20151224git1a4fdf9-1

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

Debian distribution maintenance software
pp.
Ruben Undheim  (supplier of updated arachne-pnr 
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, 03 Mar 2016 23:55:14 +0100
Source: arachne-pnr
Binary: arachne-pnr-chipdb arachne-pnr
Architecture: source
Version: 0.1+20151224git1a4fdf9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ruben Undheim 
Description:
 arachne-pnr - Place and route tool for iCE40 family FPGAs
 arachne-pnr-chipdb - Chip db files for arachne-pnr
Closes: 816579
Changes:
 arachne-pnr (0.1+20151224git1a4fdf9-1) unstable; urgency=medium
 .
   * New upstream version
 - Fixes FTBFS (Closes: #816579)
   * d/rules: Minor typo fix
   * d/patches/05_prevent_dependency_on_git.patch:
 - Set VER and GIT_REV explicitly
Checksums-Sha1:
 34220422597f1cc2d4b26ee8024b5052432770ab 2215 
arachne-pnr_0.1+20151224git1a4fdf9-1.dsc
 68b714552dd506eb4e4d34a1d5b167da818a0ed6 82919 
arachne-pnr_0.1+20151224git1a4fdf9.orig.tar.gz
 521f00d64351fc11772defd35bc3cbc9babd298c 4480 
arachne-pnr_0.1+20151224git1a4fdf9-1.debian.tar.xz
Checksums-Sha256:
 0a589e6ae284e8c7da9cea19f0bc889b338c3dc1612e0382a023b6b5c8ed882d 2215 
arachne-pnr_0.1+20151224git1a4fdf9-1.dsc
 76c822e0c2f0ecad565d04d4df9d850cd5659f06d6dfdcdccc225d0d85e70878 82919 
arachne-pnr_0.1+20151224git1a4fdf9.orig.tar.gz
 3379f5f6d3a6ca090a604072a26a66264b6b6d4e65995a6333460257b554302d 4480 
arachne-pnr_0.1+20151224git1a4fdf9-1.debian.tar.xz
Files:
 

Bug#816581: marked as done (kodi-pvr-mythtv: FTBFS: error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating')

[Debian Bug Tracking System]

Your message dated Thu, 03 Mar 2016 23:38:29 +
with message-id 
and subject line Bug#816581: fixed in kodi-pvr-mythtv 3.4.8+git20160301-1
has caused the Debian Bug report #816581,
regarding kodi-pvr-mythtv: FTBFS: error: 'PVR_TIMER {aka struct PVR_TIMER}' has 
no member named 'bIsRepeating'
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.)


-- 
816581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi-pvr-mythtv
Version: 2.8.0+git20151119-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,

kodi-pvr-mythtv fails to build from source in unstable/amd64:

  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:
 In member function 'PVR_ERROR PVRClientMythTV::GetTimers(ADDON_HANDLE)':
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1523:11:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 tag.bIsRepeating = meta.isRepeating;
 ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1534:11:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 tag.bIsRepeating = false;
 ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1614:9:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
   tag.bIsRepeating = false;
   ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:
 In member function 'MythRecordingRule 
PVRClientMythTV::PVRtoMythRecordingRule(const PVR_TIMER&)':
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1736:13:
 error: 'const PVR_TIMER {aka const struct PVR_TIMER}' has no member named 
'bIsRepeating'
 if (timer.bIsRepeating)
   ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:
 In member function 'PVR_ERROR PVRClientMythTV::UpdateTimer(const PVR_TIMER&)':
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1848:20:
 error: 'struct PVR_TIMER' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating && !newTimer.bIsRepeating)
  ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1848:46:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating && !newTimer.bIsRepeating)
^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1850:14:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
   newTimer.bIsRepeating = true;
^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1856:20:
 error: 'struct PVR_TIMER' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating != newTimer.bIsRepeating || 
old->second->iWeekdays != newTimer.iWeekdays)
  ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1856:45:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating != newTimer.bIsRepeating || 
old->second->iWeekdays != newTimer.iWeekdays)
   ^
  CMakeFiles/pvr.mythtv.dir/build.make:449: recipe for target 
'CMakeFiles/pvr.mythtv.dir/src/pvrclient-mythtv.cpp.o' failed
  make[3]: *** [CMakeFiles/pvr.mythtv.dir/src/pvrclient-mythtv.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:102: recipe for target 'CMakeFiles/pvr.mythtv.dir/all' 
failed
  make[2]: *** [CMakeFiles/pvr.mythtv.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/obj-x86_64-linux-gnu'
  Makefile:152: recipe for target 'all' failed
  make[1]: *** [all] 

Bug#815742: marked as done (verbiste: FTBFS: lt-french-deconjugator: unrecognized option '--unknown')

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 16:43:25 +
with message-id 
and subject line Bug#815742: fixed in verbiste 0.1.42-3
has caused the Debian Bug report #815742,
regarding verbiste: FTBFS: lt-french-deconjugator: unrecognized option 
'--unknown'
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.)


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

verbiste fails to build from source in unstable/amd64:

  [..]

  
/home/lamby/temp/cdt.20160224081748.Xb5VyRnZ98/verbiste-0.1.42/src/commands/.libs/lt-french-deconjugator:
 unrecognized option '--unknown'
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-conjugator --version`" = \
"french-conjugator 0.1.42"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`echo -e 'avr\xc3\xb2' | LIBDATADIR=../../data LANG=en_US.UTF-8 
LC_ALL=en_US.UTF-8 ./french-deconjugator --lang=it`" = "avere, indicative, 
future, 1, singular"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-deconjugator --lang=it partire | wc -l`" = 3
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-deconjugator --lang=it parto`"= "partire, indicative, present, 1, 
singular"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  Testing exit status when requesting help page:
  LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 ./french-conjugator 
--help 2>&1 >/dev/null
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-deconjugator --lang=it partisco`" = "partire, indicative, present, 1, 
singular"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  Testing exit status when passing unknown option:
  LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 ./french-conjugator 
--unknown 2>&1 >/dev/null; test "$?" = 1
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-deconjugator --lang=it avendo`" = "avere, gerund, present, 0, singular"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  
/home/lamby/temp/cdt.20160224081748.Xb5VyRnZ98/verbiste-0.1.42/src/commands/.libs/lt-french-conjugator:
 unrecognized option '--unknown'
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-conjugator --pronouns hacher | grep ^j | head -1`" = "je hache"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-conjugator --lang=it avere | grep eberro`" = "eberro"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-conjugator --lang=it --pronouns avere | grep -c 'che essi avessero'`" 
= 1
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-conjugator --pronouns habiter | grep ^j | head -1`" = "j'habite"
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  test "`LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
./french-conjugator --lang=it avere sentire partire | grep -c '^-$'`" = 4
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  LIBDATADIR=../../data LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 perl 
./check-infinitives.pl ../../data/verbs-it.xml
  perl: warning: Setting locale failed.
  perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = "en_US.UTF-8",
LANG = "en_US.UTF-8"
  are supported and installed on your system.
  perl: warning: Falling back to the standard locale ("C").
  /bin/bash ../../libtool  --tag=CXX   --mode=link g++ -I/usr/include/libxml2 
-I../../src -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -W 
-Wall  -Wl,-z,relro -o 

Bug#816518: marked as done (gitmagic: FTBFS: LaTeX Error: File `ulem.sty' not found.)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 17:20:38 +
with message-id <e1abtp4-00046k...@franck.debian.org>
and subject line Bug#816518: fixed in gitmagic 20160304-1
has caused the Debian Bug report #816518,
regarding gitmagic: FTBFS: LaTeX Error: File `ulem.sty' not found.
to be marked as done.

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

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


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

gitmagic fails to build from source in unstable/amd64:

  [..]

  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)))
  (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
  
  ! LaTeX Error: File `ulem.sty' not found.
  
  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)
  
  Enter file name: 
  ! Emergency stop.
   
   
  l.27 \RequirePackage
  {fancyhdr}^^M
  !  ==> Fatal error occurred, no output PDF file produced!
  Transcript written on pdfjadetex.log.
  mktexfmt [ERROR]: running `pdftex -ini   -jobname=pdfjadetex 
-progname=pdfjadetex *pdfjadetex.ini >&2 &2 

gitmagic.20140125-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: gitmagic
Source-Version: 20160304-1

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

Debian distribution maintenance software
pp.
Sebastien Badia <s...@sebian.fr> (supplier of updated gitmagic 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, 04 Mar 2016 12:01:25 -0300
Source: gitmagic
Binary: gitmagic
Architecture: source all
Version: 20160304-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Badia <s...@sebian.fr>
Changed-By: Sebastien Badia <s...@sebian.fr>
Description:
 gitmagic   - guide about Git version control system
Closes: 816518
Changes:
 gitmagic (20160304-1) unstable; urgency=medium
 .
   * d/control:
   Bump Standards-version (no changes)
   Switch to https and cgit for vcs-browser URL
   Update Vcs-git url (use https)
   Add missing BD (Closes: #816518)
   Bump Standards-Version to 3.9.7 (no changes)
   * d/copyright: Fix dep5 headers (no-dep5-copyright)
   * Imported Upstream version 20160304
   * d/patches:
   Remove un-needed breach-logo patch
   Add breach-generic patch (googlefonts)
   Refresh patchs and disable selflink js
Checksums-Sha1:
 9893b20d4b06b115161fff57ba290e7db5e934c0 2094 gitmagic_20160304-1.dsc
 b44f78f99c96e92464664d76e010ffef39b4066f 629266 gitmagic_20160304.orig.tar.gz
 663765f1b3690e6124b8d776c701b8fefc994737 4592 gitmagic_20160304-1.debian.tar.xz
 68355aedfe80347719d8c3f9364c798afc84fe71 279948 gitmagic_20160304-1_all.deb
Checksums-Sha256:
 0901f43c59d7a84ca11a38bc4ef180989e63b68c71fd1d3dca5c5ee927b1fc7e 2094 
gitmagic_20160304-1.dsc
 d6a9a4a8ead55ea0933803d18a378b755643435846d1c4087ea958110ddb836b 629266 
gitmagic_20160304.orig.tar.gz
 c29c3aa24397ff66aae2eff3a3170f4d34758afbf2d1957bcf76f7333dcea9b6 4592 
gitmagic_20160304-1.debian.tar.xz
 d366fe0abd3923a1638158e08102b32c0f502efe1d7a5621896544a39f91d26f 279948 
gitmagic_20160304-1_all.deb
Files:
 f5983cc22f0620eb38baf0dfd5c30d20 2094 doc optional gitmagic_20160304-1.dsc
 05a6257e604c754de8e48824dce2dbc8 629266 doc optional 
gitmagic_20160304.orig.tar.gz
 619dbe481f91acc9e21785187a1e780f 4592 doc optional 
gitmagic_20160304-1.debian.tar.xz
 9aca6b397ba5d5754a8691ebcabd0f36 279948 doc optional 
gitmagic_20160304-1_all.deb

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJW2b8tXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi

Bug#816572: marked as done (FTBFS: error: zero-length dictionary generated)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 07:50:17 +
with message-id 
and subject line Bug#816572: fixed in ispell 3.4.00-5
has caused the Debian Bug report #816572,
regarding FTBFS: error: zero-length dictionary generated
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.)


-- 
816572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ispell
Version: 3.4.00-4
Severity: serious

ispell fails to build in unstable:

> Finding flag marker.
> Generating roots and affixes.
> ../../ispell -wA -c -W0 -d /tmp/munchncQUfV7QXk/munch.o.hash -p /dev/null 
> failed with 141
> + rm -f english.sml+
> test -s english.sml+ \
>   ||  (echo 'error: zero-length dictionary generated'; \
> rm -f english.sml+; exit 1)
> error: zero-length dictionary generated
> ../english/Makefile:358: recipe for target 'english.sml+' failed
> make[6]: *** [english.sml+] Error 1
> make[6]: Leaving directory '/<>/languages/american'
> Makefile:266: recipe for target 'english.sml+' failed
> make[5]: *** [english.sml+] Error 2
> make[5]: Leaving directory '/<>/languages/american'
> make[5]: Entering directory '/<>/languages/american'
> make -f ../english/Makefile VARIANTS=american \
>   'EXTRADICT=debian-auto' 'SHELLDEBUG=+vx' \
>   'AFFIXES=../english/english.aff' \
>   english.med+
> make[6]: Entering directory '/<>/languages/american'
> + 
> PATH=../..:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + export PATH
> + ../../munchlist -T utf8 -v -l ../english/english.aff 
> /usr/share/dict/american-english english.0 english.1 american.0 american.1
> Collecting input.
> Finding flag marker.
> Generating roots and affixes.
> ../../ispell -wA -c -W0 -d /tmp/munchEEKlweEL5Y/munch.o.hash -p /dev/null 
> failed with 141
> + rm -f english.med+
> test -s english.med+ \
>   ||  (echo 'error: zero-length dictionary generated'; \
> rm -f english.med+; exit 1)
> error: zero-length dictionary generated
> ../english/Makefile:408: recipe for target 'english.med+' failed
> make[6]: *** [english.med+] Error 1
> make[6]: Leaving directory '/<>/languages/american'
> Makefile:294: recipe for target 'english.med+' failed
> make[5]: *** [english.med+] Error 2
> make[5]: Leaving directory '/<>/languages/american'
> make[5]: Entering directory '/<>/languages/american'
> make -f ../english/Makefile VARIANTS=american \
>   'EXTRADICT=debian-auto' 'SHELLDEBUG=+vx' \
>   'AFFIXES=../english/english.aff' \
>   english.lrg+
> make[6]: Entering directory '/<>/languages/american'
> + 
> PATH=../..:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + export PATH
> + ../../munchlist -T utf8 -v -l ../english/english.aff 
> /usr/share/dict/american-english-large english.0 english.1 english.2 
> american.0 american.1 american.2
> Collecting input.
> Finding flag marker.
> Generating roots and affixes.
> ../../ispell -wA -c -W0 -d /tmp/munchMXzSKfwTGE/munch.o.hash -p /dev/null 
> failed with 141
> + rm -f english.lrg+
> test -s english.lrg+ \
>   ||  (echo 'error: zero-length dictionary generated'; \
> rm -f english.lrg+; exit 1)
> error: zero-length dictionary generated
> ../english/Makefile:466: recipe for target 'english.lrg+' failed
> make[6]: *** [english.lrg+] Error 1
> make[6]: Leaving directory '/<>/languages/american'
> Makefile:322: recipe for target 'english.lrg+' failed
> make[5]: *** [english.lrg+] Error 2
> make[5]: Leaving directory '/<>/languages/american'
> make[5]: Entering directory '/<>/languages/american'
> make -f ../english/Makefile VARIANTS=american \
>   'EXTRADICT=debian-auto' 'SHELLDEBUG=+vx' \
>   'AFFIXES=../english/english.aff' \
>   english.xlg+
> make[6]: Entering directory '/<>/languages/american'
> + 
> PATH=../..:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + export PATH
> + ../../munchlist -T utf8 -v -l ../english/english.aff 
> /usr/share/dict/american-english-huge english.0 english.1 english.2 english.3 
> american.0 american.1 american.2
> Collecting input.
> 
> Word 'LLANFAIRPWLLGWYNGYLLGOGERYCHWYRNDROBWANTYSILIOGOGOGOCH' too long at 
> line 713 of makedent.c, truncated
> 
> Word 'LLANFAIRPWLLGWYNGYLLGOGERYCHWYRNDROBWANTYSILIOGOGOGOCH'S' too long 
> at line 713 of makedent.c, truncated
> Finding flag marker.
> Generating roots and affixes.
> ../../ispell -wA -c -W0 -d /tmp/munchRbTphPITxd/munch.o.hash -p /dev/null 
> failed with 141
> + rm -f english.xlg+
> test -s english.xlg+ \
>   ||  (echo 'error: zero-length dictionary generated'; \
>  

Bug#816527: marked as done (libtest-file-contents-perl: FTBFS with Text::Diff 1.44)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 01:26:52 +
with message-id 
and subject line Bug#816527: fixed in libtest-file-contents-perl 0.22-1
has caused the Debian Bug report #816527,
regarding libtest-file-contents-perl: FTBFS with Text::Diff 1.44
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.)


-- 
816527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtest-file-contents-perl
Version: 0.21-2
Severity: serious
Tags: upstream
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on ci.d.n., libtest-file-contents-perl fails some tests:
https://ci.debian.net/data/packages/unstable/amd64/libt/libtest-file-contents-perl/20160302_135058.autopkgtest.log.gz
(also confirmed locally).

The ci log at 
https://ci.debian.net/data/packages/unstable/amd64/libt/libtest-file-contents-perl/20160302_135058.log
shows:

- -libtext-diff-perl 1.43-1
+libtext-diff-perl 1.44-1

And indeed, Text:Diff's upstream Changes say:

1.44 2016-02-26 NEILB
- Fixed the handling of text without a trailing newline. This module now
  adds the same text that the diff tool does, "\n\\ No newline at end of
  file\n". Previously this module simply produced broken diffs when one or
  both files had no trailing newline. Fixed by Dave Rolsky. GitHub #1.


Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJW1wtEXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGK7QP/AkFNbG4SZN0I58m0whlBBwH
iyAmJ3dSLK9v8Ukyjyx36Qrf9YOGzrJXiqUiG9nEAK6/dTUo+3Z8+f8tEgEHBgwb
1pG92lQOK1ovBbvR/WLLC32gpg7pppQ/QCrAMH+cV8JghuLDNbue3ECziCGMpGOX
I5+uIwlBw4VEak0xz74FlYMp8ypZIuVLXMxWd2QQrAXd/2KNTlF0TunL8+nCaASi
4GdMa7IuB9MJWbxnGAzImj+sa1/jZv9B0MDnpQCdHtrF+L2oiP6B1SP0Uaogfsyi
5hk13zw99SM7gg0lrtK0DtCCBYbKb09pv5R/acOhzCk4xHLUfRYBoV7oSefeHgne
S+/9N/TMUtT8EO+Fu6V/50j+KSGdbJIuhYgdnHnEh6tVq5h/tMHupWq6BSnUmgra
g2bQGHfe/j7UHFTZ74JLBwAdNbVdVePpiqYrN0U4GA9h/1AKSEbCbMaS6IqMySkf
y3ayHDHm1XMTl/NNH4nmpQfnutqwK3ESpSsE2RFavpridygFWHe9uwVV/EOnW8b7
5snQP8Nm8HmXY8hWkid9+fYA1aVU5AjIMK4idVUwq6yK6zOVdyU7FBJeELgSchCo
OwYLdoL31O2Uj1r2pgom+0cQNlNTyxr6JOe5vWTwnh28hP5gOAOgNcAGSt1nnNmG
BpmdaqF61R1vq7XRfhgS
=1xIl
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libtest-file-contents-perl
Source-Version: 0.22-1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libtest-file-contents-perl 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, 04 Mar 2016 01:38:26 +0100
Source: libtest-file-contents-perl
Binary: libtest-file-contents-perl
Architecture: source
Version: 0.22-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 816527
Description: 
 libtest-file-contents-perl - Perl module for testing the contents of files
Changes:
 libtest-file-contents-perl (0.22-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * Import upstream version 0.22:
 Fixes "FTBFS with Text::Diff 1.44"
 (Closes: #816527)
   * Update years of upstream copyright.
   * Update debian/upstream/metadata.
   * Update build dependencies.
   * Bump debhelper compatibility level to 9.
   * Declare compliance with Debian Policy 3.9.7.
Checksums-Sha1: 
 a0f46cfd6e7b1c46ded91170d23aeb1d440fd607 2385 
libtest-file-contents-perl_0.22-1.dsc
 6d6f5b084f8ebf47dfde344df301c423ead64ec7 9926 
libtest-file-contents-perl_0.22.orig.tar.gz
 82d65101a29586aef6a6a30ce22db148f1bbcdc9 2360 
libtest-file-contents-perl_0.22-1.debian.tar.xz
Checksums-Sha256: 
 

Bug#816480: marked as done (ruby-clockwork: FTBFS: undefined method `describe' for DatabaseEvents::SyncPerformerTest:Class (NoMethodError))

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 01:32:25 +
with message-id 
and subject line Bug#816480: fixed in ruby-clockwork 1.2.0-3
has caused the Debian Bug report #816480,
regarding ruby-clockwork: FTBFS: undefined method `describe' for 
DatabaseEvents::SyncPerformerTest:Class (NoMethodError)
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.)


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

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

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081154.KgVaOYeOae/ruby-clockwork-1.2.0/debian/ruby-clockwork/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-clockwork/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  
/home/lamby/temp/cdt.20160302081154.KgVaOYeOae/ruby-clockwork-1.2.0/test/database_events/sync_performer_test.rb:26:in
 `': undefined method `describe' for 
DatabaseEvents::SyncPerformerTest:Class (NoMethodError)
from 
/home/lamby/temp/cdt.20160302081154.KgVaOYeOae/ruby-clockwork-1.2.0/test/database_events/sync_performer_test.rb:13:in
 `'
from 
/home/lamby/temp/cdt.20160302081154.KgVaOYeOae/ruby-clockwork-1.2.0/test/database_events/sync_performer_test.rb:11:in
 `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160302081154.KgVaOYeOae/ruby-clockwork-1.2.0/debian/ruby-clockwork
 returned exit code 1
  debian/rules:16: 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-clockwork.1.2.0-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-clockwork
Source-Version: 1.2.0-3

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

Debian distribution maintenance software
pp.
Thiago Ribeiro  (supplier of updated ruby-clockwork 
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, 03 Mar 2016 12:21:42 -0300
Source: ruby-clockwork
Binary: ruby-clockwork
Architecture: source
Version: 1.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Thiago Ribeiro 
Description:
 ruby-clockwork - scheduler process to replace cron
Closes: 816480
Changes:
 ruby-clockwork (1.2.0-3) unstable; urgency=medium
 .
   * Team Upload.
   * Add patch fix_test_with_minitest.patch (Closes: #816480)
   * Update packaging using dh-make-ruby -w
 - Bump Standards-Versio to 3.9.7 (no changes needed)
 - Set debhelper compatibility level to 9
 - use https:// in Vcs-* fields
Checksums-Sha1:
 ddcd9fdcd730ce04c9e929e2b4f9663b3b5852a6 1792 ruby-clockwork_1.2.0-3.dsc
 8a559c887d203ca18ff742db70a044450b88dd84 8780 
ruby-clockwork_1.2.0-3.debian.tar.xz
Checksums-Sha256:
 a54ce747628a8c45c673bb464ef8951ba3de5ceb37a734a73dc82a91a7f74a19 1792 
ruby-clockwork_1.2.0-3.dsc
 1ce5d4c927742f7a2f12db73b41d1495e827da7558646e53042a0bebc2ae872e 8780 
ruby-clockwork_1.2.0-3.debian.tar.xz
Files:
 

Bug#809771: marked as done (php-net-ldap2: FTBFS: This package.xml requires PEAR version 1.10.1 to parse properly, we are version 1.9.5)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 12:49:49 +
with message-id 
and subject line Bug#809771: fixed in php-net-ldap2 2.2.0-2
has caused the Debian Bug report #809771,
regarding php-net-ldap2: FTBFS: This package.xml requires PEAR version 1.10.1 
to parse properly, we are version 1.9.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.)


-- 
809771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-net-ldap2
Version: 2.2.0-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,

php-net-ldap2 fails to build from source in unstable/amd64:

  [..]

 dh_auto_install -O--buildsystem=phppear
/usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php-net-ldap2 -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P 
/home/lamby/temp/cdt.20160103134203.eRagGTOM5l/php-net-ldap2-2.2.0/debian/php-net-ldap2
 ./Net_LDAP2-2.2.0/package.xml
  This package.xml requires PEAR version 1.10.1 to parse properly, we are 
version 1.9.5
  Parsing of package.xml from file "./Net_LDAP2-2.2.0/package.xml" failed
  Cannot download non-local package "./Net_LDAP2-2.2.0/package.xml"
  install failed
  dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php-net-ldap2 -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P 
/home/lamby/temp/cdt.20160103134203.eRagGTOM5l/php-net-ldap2-2.2.0/debian/php-net-ldap2
 ./Net_LDAP2-2.2.0/package.xml returned exit code 1
  debian/rules:3: recipe for target 'binary' failed
  make: *** [binary] Error 10

  [..]

The full build log is attached.


Regards,

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


php-net-ldap2.2.2.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: php-net-ldap2
Source-Version: 2.2.0-2

We believe that the bug you reported is fixed in the latest version of
php-net-ldap2, 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.
Prach Pongpanich  (supplier of updated php-net-ldap2 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, 04 Mar 2016 19:25:40 +0700
Source: php-net-ldap2
Binary: php-net-ldap2
Architecture: source all
Version: 2.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Prach Pongpanich 
Description:
 php-net-ldap2 - ${phppear:summary}
Closes: 809771
Changes:
 php-net-ldap2 (2.2.0-2) unstable; urgency=medium
 .
   * Add Build-Depends on php-pear (>= 1.10.1) (Closes: #809771)
   * Bump standards version to 3.9.7
   * Update Build-depends on pkg-php-tools (>= 1.32) for PHP 7
Checksums-Sha1:
 6b62010e657ce461069f0f9867f72ad079e164f5 2077 php-net-ldap2_2.2.0-2.dsc
 2c83221171249ae830ba2b20aed0421feaa6e16d 2592 
php-net-ldap2_2.2.0-2.debian.tar.xz
 996c6885cf6d3b8cbb9fa7ce1244997baa6bf2a5 82386 php-net-ldap2_2.2.0-2_all.deb
Checksums-Sha256:
 c629a10c12563ed4e6b8427e5e5eb857a9c4c2cec5f48d0158a637fa35c963db 2077 
php-net-ldap2_2.2.0-2.dsc
 5b0cec4ba45892d6ac92e49e10315f989ebe88fbc8e7a04808f0641782cdb6b7 2592 
php-net-ldap2_2.2.0-2.debian.tar.xz
 75517463b9c26f3789e188afb69e7760a98ecd2388a630142e44606f12c11f99 82386 
php-net-ldap2_2.2.0-2_all.deb
Files:
 fef2f3635edf9e18dbd9c70416809d8f 2077 php optional php-net-ldap2_2.2.0-2.dsc
 1e3119281c32b098626a6528d2bc9ebb 2592 php optional 
php-net-ldap2_2.2.0-2.debian.tar.xz
 23ae3ddbc8332aa65dd3fb2e6e0a38ae 82386 php optional 

Bug#809766: marked as done (ruby-test-unit and ruby-rubysl-test-unit: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 13:17:29 +
with message-id 
and subject line Bug#816606: Removed package(s) from unstable
has caused the Debian Bug report #809766,
regarding ruby-test-unit and ruby-rubysl-test-unit: 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.)


-- 
809766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rubysl-test-unit,ruby-test-unit
Version: ruby-rubysl-test-unit/2.0.3-1
Version: ruby-test-unit/3.1.5-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-03
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:


Preconfiguring packages ...
Selecting previously unselected package libyaml-0-2:amd64.
(Reading database ... 10930 files and directories currently installed.)
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
Selecting previously unselected package libssl1.0.2:amd64.
Preparing to unpack .../libssl1.0.2_1.0.2e-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2e-1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2e-1_amd64.deb ...
Unpacking openssl (1.0.2e-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20151214_all.deb ...
Unpacking ca-certificates (20151214) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.6-1_all.deb ...
Unpacking ruby-power-assert (0.2.6-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.5-1_all.deb ...
Unpacking ruby-test-unit (3.1.5-1) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.8.3-1_all.deb ...
Unpacking ruby-minitest (5.8.3-1) ...
Selecting previously unselected package libruby2.2:amd64.
Preparing to unpack .../libruby2.2_2.2.3-2_amd64.deb ...
Unpacking libruby2.2:amd64 (2.2.3-2) ...
Selecting previously unselected package ruby2.2.
Preparing to unpack .../ruby2.2_2.2.3-2_amd64.deb ...
Unpacking ruby2.2 (2.2.3-2) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.2.4_all.deb ...
Unpacking ruby (1:2.2.4) ...
Selecting previously unselected package ruby-molinillo.
Preparing to unpack .../ruby-molinillo_0.2.3-1_all.deb ...
Unpacking ruby-molinillo (0.2.3-1) ...
Selecting previously unselected package ruby-net-http-persistent.
Preparing to unpack .../ruby-net-http-persistent_2.9-3_all.deb ...
Unpacking ruby-net-http-persistent (2.9-3) ...
Selecting previously unselected package ruby-thor.
Preparing to unpack .../ruby-thor_0.19.1-2_all.deb ...
Unpacking ruby-thor (0.19.1-2) ...
Selecting previously unselected package bundler.
Preparing to unpack .../bundler_1.10.6-2_all.deb ...
Unpacking bundler (1.10.6-2) ...
Selecting previously unselected package rake.
Preparing to unpack .../archives/rake_10.4.2-2_all.deb ...
Unpacking rake (10.4.2-2) ...
Selecting previously unselected package ruby-rubysl-test-unit.
Preparing to unpack .../ruby-rubysl-test-unit_2.0.3-1_all.deb ...
Unpacking ruby-rubysl-test-unit (2.0.3-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/ruby-rubysl-test-unit_2.0.3-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/ruby/vendor_ruby/test/unit.rb', which is also in 
package ruby-test-unit 3.1.5-1
Processing triggers for libc-bin (2.21-6) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/ruby-rubysl-test-unit_2.0.3-1_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 

Bug#808530: marked as done (ruby-foreigner: FTBFS: NoMethodError: undefined method `expects' for #<Foreigner::Sql2003Test::TestAdapter)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 13:12:51 +
with message-id 
and subject line Bug#816544: Removed package(s) from unstable
has caused the Debian Bug report #808530,
regarding ruby-foreigner: FTBFS: NoMethodError: undefined method `expects' for 
#http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-foreigner
Version: 1.7.4-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

┌──┐
│ Run tests for ruby2.2 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/ruby-foreigner-1.7.4/debian/ruby-foreigner/usr/lib/ruby/vendor_ruby:. 
ruby2.2 debian/ruby-tests.rb
DEPRECATION WARNING: You did not specify a value for the configuration option 
`active_support.test_order`. In Rails 5, the default value of this option will 
change from `:sorted` to `:random`.
To disable this warning and keep the current behavior, you can add the 
following line to your `config/environments/test.rb`:

  Rails.application.configure do
config.active_support.test_order = :sorted
  end

Alternatively, you can opt into the future behavior by setting this option to 
`:random`. (called from test_order at 
/usr/lib/ruby/vendor_ruby/active_support/test_case.rb:42)
Run options: --seed 52404

# Running:

..EEEE...DEPRECATION WARNING: `#capture(stream)` is 
deprecated and will be removed in the next release. (called from block in 
 at 
/ruby-foreigner-1.7.4/test/foreigner/connection_adapters/mysql_adapter_test.rb:6)
.

Finished in 0.081778s, 415.7594 runs/s, 427.9876 assertions/s.

  1) Error:
Foreigner::Sql2003Test#test_foreign_key_exists:
NoMethodError: undefined method `expects' for 
#

/ruby-foreigner-1.7.4/test/foreigner/connection_adapters/sql2003_test.rb:34:in 
`block in '
/usr/lib/ruby/vendor_ruby/minitest/test.rb:108:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:205:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:105:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:256:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:334:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:276:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:781:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:296:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:295:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:295:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:334:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:321:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:294:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:155:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:155:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:155:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:129:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:56:in `block in autorun'


  2) Error:
Foreigner::AdapterTest#test_load:
NoMethodError: undefined method `expects' for Foreigner::Adapter:Class
/ruby-foreigner-1.7.4/test/foreigner/adapter_test.rb:6:in `block in 
'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:108:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:205:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:105:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:256:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:334:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:276:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:781:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:296:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:295:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:295:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:334:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:321:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:294:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:155:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:155:in `map'

Bug#816315: [pkg-uWSGI-devel] Bug#816315: #816315 - uwsgi - please support ruby2.3

[Jonas Smedegaard]

Quoting Christian Hofstaedtler (2016-03-03 22:47:48)
> May I suggest dropping the exact ruby version from the package name, 
> so it doesn't have to go through NEW for 2.4, 2.5, ...?
> 
> I see uwsgi-plugin-rbthreads already doesn't encode the version in the 
> package name.

You sure may suggest it (explicitly too - was arguably already 
implicitly hinted at by the bugreport), and yes there is indeed 
inconsistency across the uwsgi packages.

The aim is, however, the opposite: For each library with multiple 
concurrent versions - even if only a single of them reaching stable at 
any point in time - have correspondent uwsgi packages (and then 
additionally have a convenience package linkest against current "main" 
version).

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#797256: marked as done (ruby-memcache-client: FTBFS: test_get_multi_with_server_failure fails)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 13:12:05 +
with message-id 
and subject line Bug#816538: Removed package(s) from unstable
has caused the Debian Bug report #797256,
regarding ruby-memcache-client: FTBFS: test_get_multi_with_server_failure 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.)


-- 
797256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-memcache-client
Version: 1.8.5-3
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:


┌──┐
│ Run tests for ruby2.2 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/ruby-memcache-client-1.8.5/debian/ruby-memcache-client/usr/lib/ruby/vendor_ruby:.
 ruby2.2 debian/ruby-tests.rb
Loaded suite test/test_mem_cache
Started
E
===
Error: test_cache_get_with_failover(TestMemCache): MemCache::MemCacheError: No 
servers available
/ruby-memcache-client-1.8.5/debian/ruby-memcache-client/usr/lib/ruby/vendor_ruby/memcache.rb:717:in
 `get_server_for_key'
/ruby-memcache-client-1.8.5/debian/ruby-memcache-client/usr/lib/ruby/vendor_ruby/memcache.rb:920:in
 `request_setup'
/ruby-memcache-client-1.8.5/debian/ruby-memcache-client/usr/lib/ruby/vendor_ruby/memcache.rb:885:in
 `with_server'
/ruby-memcache-client-1.8.5/debian/ruby-memcache-client/usr/lib/ruby/vendor_ruby/memcache.rb:246:in
 `get'
test/test_mem_cache.rb:208:in `test_cache_get_with_failover'
 205: 
 206: assert s1.alive?
 207: assert s2.alive?
  => 208: @cache.get('foo')
 209: assert s1.alive?
 210: assert !s2.alive?
 211:   end
===
A real memcached server must be running for performance testing
...A real memcached server must be running for testing flush_all
F
===
Failure: test_get_multi_with_server_failure(TestMemCache)
test/test_mem_cache.rb:187:in `test_get_multi_with_server_failure'
 184: assert s2.alive?
 185: # a maps to s1, the rest map to s2
 186: value = @cache.get_multi(['foo', 'bar', 'a', 'b', 'c'])
  => 187: assert_equal({'a'=>'0123456789'}, value)
 188: assert s1.alive?
 189: assert !s2.alive?
 190:   end
<{"a"=>"0123456789"}> expected but was
<{}>

diff:
? {"a"=>"0123456789"}
===
A real memcached server must be running for performance 
testing
..

Finished in 0.066686201 seconds.
--
75 tests, 154 assertions, 1 failures, 1 errors, 0 pendings, 0 omissions, 0 
notifications

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 1.8.5-3+rm

Dear submitter,

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

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

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

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

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

Bug#799188: marked as done (mdpress: Fails to start: private method `render' called)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 13:21:30 +
with message-id 
and subject line Bug#816659: Removed package(s) from unstable
has caused the Debian Bug report #799188,
regarding mdpress: Fails to start: private method `render' called
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.)


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

Dear Maintainer,

running `mdpress file.md` results in the following error:

/usr/bin/mdpress:90:in `render': private method `render' called for 
# (NoMethodError)

It seems that this has already been reported upstream:

https://github.com/egonSchiele/mdpress/issues/41

This renders the package unusable.

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

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

Versions of packages mdpress depends on:
ii  libjs-highlight   8.2+ds-4
ii  libjs-highlight.js [libjs-highlight]  8.2+ds-4
ii  libjs-impress 0.5.3-1
ii  libjs-mathjax 2.5.3-1
ii  ruby  1:2.1.5.1
ii  ruby-redcarpet3.2.3-1+b1
ii  ruby-trollop  2.0-2
ii  ruby2.1 [ruby-interpreter]2.1.5-4

Versions of packages mdpress recommends:
ii  fonts-lato  2.0-1

mdpress suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.0.17+debian-1+rm

Dear submitter,

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

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

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

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

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

Bug#794154: marked as done (FTBFS: undefined method `stub!' for Dir:Class)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 13:22:46 +
with message-id 
and subject line Bug#816668: Removed package(s) from unstable
has caused the Debian Bug report #794154,
regarding FTBFS: undefined method `stub!' for Dir:Class
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.)


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

Dear Maintainer,

The package fails to build:

Failures:

  1) Spork::Diagnoser.output_results outputs the results relative to the 
current directory
 Failure/Error: Dir.stub!(:pwd).and_return("/project_path")
 NoMethodError:
   undefined method `stub!' for Dir:Class
 # ./spec/spork/diagnoser_spec.rb:97:in `block (3 levels) in '



Finished in 1.36 seconds (files took 0.33898 seconds to load)
54 examples, 13 failures

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.9.2-2+rm

Dear submitter,

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

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

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

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

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

Bug#795763: marked as done (ruby-pdf-reader: FTBFS: configuration.rb:656:in `block in expect_with': :stdlib is not supported (ArgumentError))

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 00:13:00 +
with message-id 
and subject line Bug#795763: fixed in ruby-pdf-reader 1.4.0-1
has caused the Debian Bug report #795763,
regarding ruby-pdf-reader: FTBFS: configuration.rb:656:in `block in 
expect_with': :stdlib is not supported (ArgumentError)
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.)


-- 
795763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-pdf-reader
Version: 1.3.3-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-pdf-reader fails to build from source on unstable/amd64:

  [..]
  /usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner
  Running tests for ruby2.1 using debian/ruby-tests.rake ...
  
RUBYLIB=/tmp/buildd/ruby-pdf-reader-1.3.3/debian/ruby-pdf-reader/usr/lib/ruby/vendor_ruby:.
  ruby2.1 -rrake -e ARGV.unshift\(\"-f\",\
  \"debian/ruby-tests.rake\"\)\;\ Rake.application.run
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern
  spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
  /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:656:in `block in
  expect_with': :stdlib is not supported (ArgumentError)
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:635:in
`map'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:635:in
`expect_with'
from /tmp/buildd/ruby-pdf-reader-1.3.3/spec/spec_helper.rb:20:in
`block in '
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from /tmp/buildd/ruby-pdf-reader-1.3.3/spec/spec_helper.rb:19:in
`'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /tmp/buildd/ruby-pdf-reader-1.3.3/spec/buffer_spec.rb:3:in
`'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in
`setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in
`invoke'
from /usr/bin/rspec:4:in `'
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern
  spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-pdf-reader-1.3.3/debian/ruby-pdf-reader returned exit
  code 1
  debian/rules:18: recipe for target 'override_dh_auto_install' failed
  make[1]: *** [override_dh_auto_install] Error 1
  make[1]: Leaving directory '/tmp/buildd/ruby-pdf-reader-1.3.3'
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:

  
https://reproducible.debian.net/logs/unstable/amd64/ruby-pdf-reader_1.3.3-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Mon Jul 13 21:08:49 GMT+12 2015
I: pbuilder-time-stamp: 1436864929
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 

Bug#795678: marked as done (ruby-rspec-longrun: FTBFS: undefined method `cyan' for class `RSpec::Longrun::Formatter' (NameError))

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 13:19:08 +
with message-id 
and subject line Bug#816627: Removed package(s) from unstable
has caused the Debian Bug report #795678,
regarding ruby-rspec-longrun: FTBFS: undefined method `cyan' for class 
`RSpec::Longrun::Formatter' (NameError)
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.)


-- 
795678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec-longrun
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

ruby-rspec-longrun fails to build from source on unstable/amd64:

  [..]
  
┌──┐
  │ Run tests for ruby2.1 from debian/ruby-tests.rake   
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-rspec-longrun-1.0.1/debian/ruby-rspec-longrun/usr/lib/ruby/vendor_ruby:.
  rake2.1 -f debian/ruby-tests.rake
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern
  spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
  /tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:55:in
  `alias_method': undefined method `cyan' for class
  `RSpec::Longrun::Formatter' (NameError)
from

/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:55:in
`alias_missing_method'
from

/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:59:in
`'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:6:in
`'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:4:in
`'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:3:in
`'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun.rb:2:in
`'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1280:in
`block in requires='
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1280:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1280:in
`requires='
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:109:in
`block in process_options_into'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:108:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:108:in
`process_options_into'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:21:in
`configure'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:102:in
`setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in
`invoke'
from /usr/bin/rspec:4:in `'
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern
  spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-rspec-longrun-1.0.1/debian/ruby-rspec-longrun
  returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:

  
https://reproducible.debian.net/logs/unstable/amd64/ruby-rspec-longrun_1.0.1-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Jul 24 18:52:58 GMT+12 2015
I: pbuilder-time-stamp: 1437807178
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: 

Bug#794261: marked as done (FTBFS: contest.rb: `setup': wrong number of arguments (2 for 0) (ArgumentError))

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 13:18:09 +
with message-id 
and subject line Bug#816608: Removed package(s) from unstable
has caused the Debian Bug report #794261,
regarding FTBFS: contest.rb: `setup': wrong number of arguments (2 for 0) 
(ArgumentError)
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.)


-- 
794261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-literati
Version: 0.0.4~git.20130318.3b3ea30-2
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build:

/usr/bin/ruby2.1 -I"lib:lib:test" -I"/usr/lib/ruby/vendor_ruby" 
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/test_*.rb" 
/usr/lib/ruby/vendor_ruby/contest.rb:19:in `setup': wrong number of arguments 
(2 for 0) (ArgumentError)
from 
/usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/adapter.rb:27:in 
`included'
from /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit.rb:38:in 
`include'
from /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit.rb:38:in 
`activate'
from /usr/lib/ruby/vendor_ruby/mocha/integration.rb:8:in `map'
from /usr/lib/ruby/vendor_ruby/mocha/integration.rb:8:in `activate'
from /usr/lib/ruby/vendor_ruby/mocha/setup.rb:5:in `activate'
from /usr/lib/ruby/vendor_ruby/mocha/setup.rb:9:in `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/tmp/buildd/ruby-literati-0.0.4~git.20130318.3b3ea30/test/test_literati.rb:5:in 
`'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:10:in `block (2 
levels) in '
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:9:in `each'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:9:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `'
rake aborted!

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.0.4~git.20130318.3b3ea30-2+rm

Dear submitter,

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

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

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

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

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

Bug#788108: marked as done (qtlocation-opensource-src: Please switch to geoclue 2)

[Debian Bug Tracking System]

Your message dated Fri, 04 Mar 2016 05:06:47 +
with message-id 
and subject line Bug#788108: fixed in qtlocation-opensource-src 5.5.1-4
has caused the Debian Bug report #788108,
regarding qtlocation-opensource-src: Please switch to geoclue 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.)


-- 
788108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtlocation-opensource-src
Version: 5.3.2-2
Severity: important

Hi,

I would like to remove geoclue from the archive and
qtlocation is the only remaning non leaf package to use it.

The package should switch to geoclue 2 instead, not sure how far
upstream is regarding this.

Cheers,

Laurent Bigonville

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

Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: qtlocation-opensource-src
Source-Version: 5.5.1-4

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

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

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtlocation-opensource-src package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Mar 2016 23:29:49 -0300
Source: qtlocation-opensource-src
Binary: libqt5location5 libqt5positioning5 libqt5location5-plugins 
libqt5positioning5-plugins qml-module-qtlocation qml-module-qtpositioning 
qtlocation5-dev qtpositioning5-dev qtlocation5-examples qtpositioning5-examples 
qtlocation5-dbg qtpositioning5-dbg qtlocation5-doc qtpositioning5-doc 
qtlocation5-doc-html qtpositioning5-doc-html
Architecture: source
Version: 5.5.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 libqt5location5 - Qt Location module
 libqt5location5-plugins - Qt Location module - geolocation plugins
 libqt5positioning5 - Qt Positioning module
 libqt5positioning5-plugins - Qt Positioning module - position plugins
 qml-module-qtlocation - Qt Location QML module
 qml-module-qtpositioning - Qt Positioning QML module
 qtlocation5-dbg - Qt Location library debugging symbols
 qtlocation5-dev - Qt 5 Location development files
 qtlocation5-doc - Qt 5 Positioning documentation
 qtlocation5-doc-html - Qt 5 Positioning HTML documentation
 qtlocation5-examples - Qt 5 Location and Positioning examples
 qtpositioning5-dbg - transitional dummy package for qtlocation5-dbg
 qtpositioning5-dev - Qt 5 Positioning development files
 qtpositioning5-doc - transitional dummy package for qtlocation5-doc
 qtpositioning5-doc-html - transitional dummy package for qtlocation5-doc-html
 qtpositioning5-examples - transitional dummy package for qtlocation5-examples
Closes: 788108
Changes:
 qtlocation-opensource-src (5.5.1-4) unstable; urgency=medium
 .
   * Make qtlocation5-examples depend upon qml-module-qtlocation, required by 
some
 examples.
   * Remove GeoClue support (Closes: #788108). The code has not switched to
 GeoClue 2. On Qt 5.6 it seems to use DBus to connect to GeoClue, so this
 feature should come back soon.
Checksums-Sha1:
 e7b956f3ee1d777d0c3fb348090879296615cc96 3452 
qtlocation-opensource-src_5.5.1-4.dsc
 72c2035042b6b61fe9c53cd5aa8c0433058bf432 17556 
qtlocation-opensource-src_5.5.1-4.debian.tar.xz
Checksums-Sha256:
 a2a975f17a319c9a22ef79bc9318a192e6bfb4ea965c1ccc6eb9c18ed214ef29 3452 
qtlocation-opensource-src_5.5.1-4.dsc
 d0d38c0f5652e870d5f3db2edb69edcb1ea5a29abab07f00cbf26bd639ddd538 17556 
qtlocation-opensource-src_5.5.1-4.debian.tar.xz
Files:
 9ed9e88c5c4ba487339695a139059368 3452 libs optional 

Bug#799919: asused stopped working because changed fields are missing in newer objects

[Sebastien Badia]

tags 799919 pending
thanks

Hi Matthias,

Thanks for the patch and the bug report, and sorry for the late reply :-/
Just added for the next version of asused. Thanks!

https://anonscm.debian.org/cgit/collab-maint/asused.git/commit/?id=472d9b76587005d808766e6f2818ad00bd5d05b6

Seb


signature.asc
Description: PGP signature

Processed: closing 813982

[Debian Bug Tracking System]

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

> close 813982
Bug #813982 {Done: Yaroslav Halchenko } [src:python-mne] 
python-mne: FTBFS: IndexError: an index can only have a single ellipsis ('...')
Bug 813982 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#816357: jedit: FTBFS: XThis.java:128: error: cannot find symbol [..] NotSerializableException

[tony mancill]

On 03/04/2016 12:24 AM, Markus Koschany wrote:
> On Thu, 03. Mar 22:30 tony mancill  wrote:
>>> diff -Nru bsh-2.0b4/debian/patches/CVE-2016-2510.patch 
>>> bsh-2.0b4/debian/patches/CVE-2016-2510.patch
>>> --- bsh-2.0b4/debian/patches/CVE-2016-2510.patch2016-03-02 
>>> 20:24:07.0 -0800
>>> +++ bsh-2.0b4/debian/patches/CVE-2016-2510.patch2016-03-03 
>>> 22:10:57.0 -0800
>>> @@ -35,8 +35,8 @@
>>>  -  class Handler implements InvocationHandler, java.io.Serializable
>>>  +  class Handler implements InvocationHandler
>>> {
>>> -+  private Object readResolve() throws ObjectStreamException {
>>> -+  throw new NotSerializableException();
>>> ++  private Object readResolve() throws 
>>> java.io.ObjectStreamException {
>>> ++  throw new java.io.NotSerializableException();
>>>  +  }
>>>  +
>>
>> So, if you're okay with the patch, could you apply it and upload an
>> updated bsh?  Or do you mind if I do?
> 
> Hi tony,
> 
> I can upload a new revision of bsh with this change later. I'm just wondering
> why we need to use java.io.ObjectStreamException and
> java.io.NotSerializableException explicitly because these classes are already
> imported in bsh's XThis.java.
> 
> import java.io.*;
> 
> Anyway it doesn't change the intention of the patch and should be safe.

Hi Markus,

I ask myself that same question, and intend to look it up.  Perhaps
because it's a nested inner class of XThis?

But one of the clues was that the original code specified the full class
name for java.io.Serializable and not just Serializable.

I agree that it shouldn't affect the intention of patch and should be
safe, but it is a bit puzzling.

Thank you,
tony

P.S.  I'm leaving you on the cc: because my MX is having some issues
with bugs.debian.org at the moment.  Sorry if you get duplicates.



signature.asc
Description: OpenPGP digital signature

Bug#816357: jedit: FTBFS: XThis.java:128: error: cannot find symbol [..] NotSerializableException

[tony mancill]

On 03/03/2016 12:49 PM, Markus Koschany wrote:
> Am 03.03.2016 um 05:03 schrieb tony mancill:
>> Control: -1 tag  + confirmed
>> Control: -1 owner tmanc...@debian.org
>>
>> On 02/29/2016 11:05 PM, Chris Lamb wrote:
>>> Source: jedit
>>> Version: 5.3.0+dfsg-1
>>> Severity: serious
>>> Justification: fails to build from source
>>
>>>   [javac] 
>>> /home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg/org/gjt/sp/jedit/bsh/XThis.java:128:
>>>  error: cannot find symbol
>>>   [javac]   throw new NotSerializableException();
>>
>> Thanks for the bug report.  Looks like we have a bit of porting for the
>> latest bsh upload.
>>
> 
> Sorry for the inconvenience. If there is more involved than importing
> the missing class, please let me know and I try to fix it.

Hi Markus,

No inconvenience at all. The issue seems to be with the upstream patch
for CVE-2016-2510, which drops the java.io.Serializable interface from
the InvocationHandler, but then references the ObjectStreamException and
NotSerializableException classes that package.

I was able to get things working for jedit by applying the following
patch (also attached), building a new bsh-src package locally, and using
that for the jedit build.

> diff -Nru bsh-2.0b4/debian/patches/CVE-2016-2510.patch 
> bsh-2.0b4/debian/patches/CVE-2016-2510.patch
> --- bsh-2.0b4/debian/patches/CVE-2016-2510.patch  2016-03-02 
> 20:24:07.0 -0800
> +++ bsh-2.0b4/debian/patches/CVE-2016-2510.patch  2016-03-03 
> 22:10:57.0 -0800
> @@ -35,8 +35,8 @@
>  -class Handler implements InvocationHandler, java.io.Serializable 
>  +class Handler implements InvocationHandler
>   {
> -+private Object readResolve() throws ObjectStreamException {
> -+throw new NotSerializableException();
> ++private Object readResolve() throws 
> java.io.ObjectStreamException {
> ++throw new java.io.NotSerializableException();
>  +}
>  +

So, if you're okay with the patch, could you apply it and upload an
updated bsh?  Or do you mind if I do?

Cheers,
tony

diff -Nru bsh-2.0b4/debian/patches/CVE-2016-2510.patch bsh-2.0b4/debian/patches/CVE-2016-2510.patch
--- bsh-2.0b4/debian/patches/CVE-2016-2510.patch	2016-03-02 20:24:07.0 -0800
+++ bsh-2.0b4/debian/patches/CVE-2016-2510.patch	2016-03-03 22:10:57.0 -0800
@@ -35,8 +35,8 @@
 -	class Handler implements InvocationHandler, java.io.Serializable 
 +	class Handler implements InvocationHandler
  	{
-+		private Object readResolve() throws ObjectStreamException {
-+			throw new NotSerializableException();
++		private Object readResolve() throws java.io.ObjectStreamException {
++			throw new java.io.NotSerializableException();
 +		}
 +


signature.asc
Description: OpenPGP digital signature

Processed: Re: asused stopped working because changed fields are missing in newer objects

[Debian Bug Tracking System]

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

> tags 799919 pending
Bug #799919 [asused] asused stopped working because changed fields are missing 
in newer objects
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#815734: regression: ESS cannot be compiled

[Martin Maechler]

> Norbert Preining 
> on Fri, 4 Mar 2016 13:01:23 +0900 writes:

> Dear all,
> down here at Debian we got another bug report about a FTBFS, which
> went away when switching to an older version of texinfo.tex:

> On Thu, 03 Mar 2016, Dirk Eddelbuettel wrote:
>> Ok, the obvious fix of fattening the source directory with a working 
copy of
>> texinfo.tex did the trick.

> I have reduced the problematic case to the following minimal example:

> \input texinfo   @c -*-texinfo-*-
> @setfilename ess.info
> @settitle ESS -- Emacs Speaks Statistics

> @macro ESS{ARG}
> @acronym{ESS\ARG\}
> @end macro

> @ESS{}: bad

> @ESS{[R]}: good

> @bye

> The output is:
> ./bla.texi:9: Argument of @gobblespaces has an extra }.
>  
> @par 
>  
> }
> @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> @def @temp {#2}@ifx @temp ...
> l.1 @acronym{ESS@gobblespaces }
> @texinfoc
> @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> @aftermacro 
> l.9 @ESS{}
> : bad
> ? 

> Can anyone comment on this?

Yes:

- This macro use has always worked in the ESS sources for
  around 20 years maybe.
- It still works for me (with a TeX Live 2015 version of texinfo.tex
  that declares  'Loading texinfo [version 2015-07-01.07]'

>From these two facts I'd declare that the new texinfo.tex that
you have in Debian is broken.
(Yes, that is a strong statement; but still breaking something
 that worked dozens of year w/o problems needs VERY good arguments
 before you can call it "progress" !!)
 
Martin



ess-tst.texi
Description: Binary data

Processed: Now fixed upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #811106 [browser-plugin-gnash] browser-plugin-gnash: crashes with general 
protection error and fails to work
Added tag(s) patch.
> tags -1 + fixed-upstream
Bug #811106 [browser-plugin-gnash] browser-plugin-gnash: crashes with general 
protection error and fails to work
Added tag(s) fixed-upstream.

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

Bug#816699: libga-dev and libarmci-mpi-dev: error when trying to install together

[Ralf Treinen]

Package: libarmci-mpi-dev,libga-dev
Version: libarmci-mpi-dev/0.0~git20160222-1
Version: libga-dev/5.4~beta~r10636+dfsg-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-03-04
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 libarmci-mpi-dev.
(Reading database ... 10939 files and directories currently installed.)
Preparing to unpack .../libarmci-mpi-dev_0.0~git20160222-1_amd64.deb ...
Unpacking libarmci-mpi-dev (0.0~git20160222-1) ...
Selecting previously unselected package libga-dev.
Preparing to unpack .../libga-dev_5.4~beta~r10636+dfsg-2_amd64.deb ...
Unpacking libga-dev (5.4~beta~r10636+dfsg-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libga-dev_5.4~beta~r10636+dfsg-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libarmci.a', which is also in 
package libarmci-mpi-dev 0.0~git20160222-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libga-dev_5.4~beta~r10636+dfsg-2_amd64.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/lib/arm-linux-gnueabi/libarmci.a

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.