Processed: tagging 816528

[Debian Bug Tracking System]

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

> tags 816528 + pending
Bug #816528 [plasma-framework-dev] plasma-framework-dev: fails to upgrade from 
'sid' - trying to overwrite 
/usr/share/kdevappwizard/templates/qml-plasmoid.tar.bz2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Merging with existing numpy bug

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-numpy 1:1.11.0~b2-1
Bug #816574 [sunpy] FTBFS: object cannot be interpreted as an index
Bug reassigned from package 'sunpy' to 'python3-numpy'.
No longer marked as found in versions 0.6.1-2.
Ignoring request to alter fixed versions of bug #816574 to the same values 
previously set
Bug #816574 [python3-numpy] FTBFS: object cannot be interpreted as an index
Marked as found in versions python-numpy/1:1.11.0~b2-1.
> affects -1 sunpy
Bug #816574 [python3-numpy] FTBFS: object cannot be interpreted as an index
Added indication that 816574 affects sunpy
> forcemerge 813429 -1
Bug #813429 [python3-numpy] python-numpy: breaks the CI tests of some installed 
packages
Bug #813932 [python3-numpy] sunpy: FTBFS: IndexError: only integers, slices 
(`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays 
are valid indices
Bug #816369 [python3-numpy] TypeError: 'float' object cannot be interpreted as 
an index
Bug #816574 [python3-numpy] FTBFS: object cannot be interpreted as an index
Set Bug forwarded-to-address to 'Yes'.
Removed indication that 816574 affects sunpy
Bug #813932 [python3-numpy] sunpy: FTBFS: IndexError: only integers, slices 
(`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays 
are valid indices
Bug #816369 [python3-numpy] TypeError: 'float' object cannot be interpreted as 
an index
Merged 813429 813932 816369 816574

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

Bug#816574: Merging with existing numpy bug

[Ole Streicher]

Control: reassign -1 python3-numpy 1:1.11.0~b2-1
Control: affects -1 sunpy
Control: forcemerge 813429 -1

This is a known problem with the current numpy beta that will be fixed
when the final version comes out.

Bug#815960: marked as done (python-openalpr: Missing python interpreter depends)

[Debian Bug Tracking System]

Your message dated Thu, 03 Mar 2016 06:00:27 +
with message-id 
and subject line Bug#815960: fixed in openalpr 2.2.4-1
has caused the Debian Bug report #815960,
regarding python-openalpr: Missing python interpreter depends
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.)


-- 
815960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-openalpr
Version: 2.2.3-1
Severity: serious
Tags: patch
Justification: Policy 3.5

The python bindings require python to be installed to work, so they have to
depend on them.  Please see the attached patch for the standard pythonic way
to do this.

Scott K
diff -Nru openalpr-2.2.3/debian/changelog openalpr-2.2.3/debian/changelog
--- openalpr-2.2.3/debian/changelog	2016-01-24 17:27:18.0 -0500
+++ openalpr-2.2.3/debian/changelog	2016-02-25 23:25:49.0 -0500
@@ -1,3 +1,10 @@
+openalpr (2.2.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh-python to generate proper depends for python-openalpr
+
+ -- Scott Kitterman   Thu, 25 Feb 2016 23:25:02 -0500
+
 openalpr (2.2.3-1) unstable; urgency=low
 
   * Changed Debian config to build on all architectures (Closes: #812176)
diff -Nru openalpr-2.2.3/debian/control openalpr-2.2.3/debian/control
--- openalpr-2.2.3/debian/control	2016-01-24 15:34:14.0 -0500
+++ openalpr-2.2.3/debian/control	2016-02-25 23:28:28.0 -0500
@@ -4,7 +4,8 @@
 Maintainer: Matthew Hill 
 Build-Depends: debhelper (>= 9), git, cmake, quilt, 
  libtesseract-dev, libleptonica-dev, liblog4cplus-dev,
- libcurl3-dev, uuid-dev, libopencv-dev, default-jdk
+ libcurl3-dev, uuid-dev, libopencv-dev, default-jdk,
+ python, dh-python
 Standards-Version: 3.9.6
 Homepage: https://github.com/openalpr/openalpr
 Vcs-Browser: https://github.com/openalpr/openalpr
@@ -102,7 +103,7 @@
 Package: python-openalpr
 Section: python
 Architecture: any
-Depends: libopenalpr-dev (= ${binary:Version}), ${misc:Depends}
+Depends: libopenalpr-dev (= ${binary:Version}), ${python:Depends}, ${misc:Depends}
 Description: Python binding for OpenALPR library
  OpenALPR is an open source Automatic License Plate Recognition library written
  in C++. The library analyzes images and identifies license plates. The output
diff -Nru openalpr-2.2.3/debian/rules openalpr-2.2.3/debian/rules
--- openalpr-2.2.3/debian/rules	2016-01-24 15:34:14.0 -0500
+++ openalpr-2.2.3/debian/rules	2016-02-25 23:26:14.0 -0500
@@ -29,7 +29,7 @@
 
 # main packaging script based on dh7 syntax
 %:
-	dh $@ --sourcedirectory=src --with quilt
+	dh $@ --sourcedirectory=src --with quilt,python2
 
 override_dh_auto_configure:
 	dh_auto_configure -- \
--- End Message ---
--- Begin Message ---
Source: openalpr
Source-Version: 2.2.4-1

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

Debian distribution maintenance software
pp.
Matthew Hill  (supplier of updated openalpr 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: Sun, 28 Feb 2016 09:51:25 -0500
Source: openalpr
Binary: libopenalpr2 libopenalpr-dev libopenalpr-data openalpr openalpr-daemon 
openalpr-utils python-openalpr python3-openalpr
Architecture: source all amd64
Version: 2.2.4-1
Distribution: unstable
Urgency: low
Maintainer: Matthew Hill 
Changed-By: Matthew Hill 
Description:
 libopenalpr-data - Runtime data for the OpenALPR library
 libopenalpr-dev - Development files for the OpenALPR library
 libopenalpr2 - Automated License Plate Recognition library (OpenALPR)
 openalpr   - Command line program to operate the OpenALPR library
 openalpr-daemon - Daemon to run OpenALPR in the background
 openalpr-utils - Utilities for the OpenALPR library
 python-openalpr - Python binding for OpenALPR library
 python3-openalpr - Python 3 binding for OpenALPR library
Closes: 812738 813290 815959 815960 815961

Processed: tagging 816357

[Debian Bug Tracking System]

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

> tags 816357 + confirmed
Bug #816357 [src:jedit] jedit: FTBFS: XThis.java:128: error: cannot find symbol 
[..] NotSerializableException
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: owner 816357

[Debian Bug Tracking System]

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

> owner 816357 tmanc...@debian.org
Bug #816357 [src:jedit] jedit: FTBFS: XThis.java:128: error: cannot find symbol 
[..] NotSerializableException
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

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.

tony

Bug#808610: libxapian22: xapian database corruption causes recollindex loop

[Eric Wong]

Olly Betts  wrote:
> On Thu, Mar 03, 2016 at 01:52:45AM +, Eric Wong wrote:
> > 
> > I would greatly appreciate a backport to fix this in Jessie.
> 
> A backport would only fix it for people who take special action and
> install from backports (that said, it's probably time to do a backport
> so there's a more up to date upstream version easily available for
> those who want it).

Errm, sorry, I meant "backport" as a general term for getting
a patch into jessie for all jessie users.
I forgot the Debian meaning of it is slightly different.

> In https://trac.xapian.org/ticket/645 the recoll upstream
> maintainer indicated that this happens with 1.2.8 too, and
> wheezy has 1.2.12-2 currently, so this issue also affects
> wheezy.

Interesting.  I haven't used Xapian extensively, but have never
seen problems on wheezy using the same hardware that was able
to reproduce the bug on jessie.

Bug#814626: chasen: causes installation failure in naist-jdic

[Takatsugu Nokubi]

On Sat, 13 Feb 2016 15:37:43 +0100 Andreas Beckmann  wrote:
> You shouldn't use dpkg-architecture from maintainer scripts
> but resolve the architecture specific bits at package build time.

This problem was fixed in 2.4.5-24.

Bug#814626: marked as done (chasen: causes installation failure in naist-jdic)

[Debian Bug Tracking System]

Your message dated Thu, 3 Mar 2016 12:54:21 +0900
with message-id 

Bug#816574: FTBFS: object cannot be interpreted as an index

[Martin Michlmayr]

Package: sunpy
Version: 0.6.1-2
Severity: serious

sunpy fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> # level operations
> return img.reshape(img.shape[0] / dimensions[0],
>dimensions[0],
>img.shape[1] / dimensions[1],
> >  dimensions[1])
> E   TypeError: 'numpy.float64' object cannot be interpreted as an index

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Processed: Re: Bug#808610: libxapian22: xapian database corruption causes recollindex loop

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -moreinfo
Bug #808610 {Done: Olly Betts } [libxapian22] libxapian22: 
xapian database corruption causes recollindex loop
Removed tag(s) moreinfo.
> tags -1 +wheezy
Bug #808610 {Done: Olly Betts } [libxapian22] libxapian22: 
xapian database corruption causes recollindex loop
Added tag(s) wheezy.
> severity -1 grave
Bug #808610 {Done: Olly Betts } [libxapian22] libxapian22: 
xapian database corruption causes recollindex loop
Severity set to 'grave' from 'important'

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

Bug#816572: FTBFS: error: zero-length dictionary generated

[Martin Michlmayr]

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'; \
> rm -f english.xlg+; exit 1)
> error: zero-length dictionary generated
> ../english/Makefile:526: recipe for target 'english.xlg+' failed
> make[6]: *** [english.xlg+] Error 1
> make[6]: Leaving directory '/<>/languages/american'
> Makefile:350: recipe for target 'english.xlg+' failed
> make[5]: *** [english.xlg+] Error 2
> make[5]: Leaving directory '/<>/languages/american'
> Makefile:138: recipe for target 'all' failed
> make[4]: *** [all] Error 2
> make[4]: Leaving directory '/<>/languages/american'
> + exit 1
> Makefile:444: recipe for target 'language-subdirs' failed
> make[3]: *** [language-subdirs] Error 1
> make[3]: Leaving directory '/<>'
> Makefile:313: recipe for target 'all-languages' failed
> make[2]: *** [all-languages] Error 2
> make[2]: Leaving directory '/<>'
> dh_auto_build: make -j1 CC=gcc CFLAGS=-Wdate-time 

Bug#816050: evolution bug fixed?

[Sam Morris]

severity 816050 normal
forwarded 816050 https://bugzilla.gnome.org/show_bug.cgi?id=762759
thanks

On Wed, 2016-03-02 at 14:00 +0100, Andreas Henriksson wrote:
> Hello Sam Morris!
> 
> Please check if you can still reproduce the problem you reported
> in the just uploaded 3.18.5.1-1 version and report back!
> 
> Regards,
> Andreas Henriksson

Hi Andreas, the new version doesn't fix the crash, but I discovered the
cause: my user did not have permission to access the ~/.cache
directory(!)

-- 
Sam Morris 
CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9



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

Processed: Re: Bug#816050: evolution bug fixed?

[Debian Bug Tracking System]

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

> severity 816050 normal
Bug #816050 [evolution] evolution: Crash on launch in e_mail_display_init 
(camel-data-cache.c:248)
Severity set to 'normal' from 'grave'
> forwarded 816050 https://bugzilla.gnome.org/show_bug.cgi?id=762759
Bug #816050 [evolution] evolution: Crash on launch in e_mail_display_init 
(camel-data-cache.c:248)
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=762759'.
> thanks
Stopping processing here.

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

Bug#816565: Useless in Debian

[David Prévot]

Package: php-crypt-blowfish
Version: 1.1.0~RC2-4
Severity: serious
Tags: sid stretch

[ 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. ]

php-crypt-blowfish has been introduced as an Horde dependency, became an
ownCloud dependency, but no packages depends on it anymore (except
owncloud version 7 that is going away anyway, see #816376). Upstream
hasn’t seen activity in years, and alternatives exist, see e.g.,
php-phpseclib).

Regards

David


signature.asc
Description: PGP signature

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

[Khalid Aziz and Shuah Khan]

On 02/26/2016 01:13 PM, Daniel Baumann wrote:
> Hi,
> 
> thanks for maintaining kexec-tools, however, kexec-tools reliably and
> reproducibly trashes my root filesystem *on* *every* *reboot*.
> 
> can this be finally fixed please?
> 
> Regards,
> Daniel
> 

Hi Daniel,

I have not been able to reproduce this bug and that has been the
limiting factor in being able to fix it. I have tried this on 3
different machines and kexec reboot always unmounts the root filesystem
correctly before reboot. I am doing a fresh install on another machine
and will spend some time trying to reproduce it. I appreciate your
patience with me.

Thanks,
Khalid

Bug#816561: marked as done (libvotca-tools3: missing Breaks+Replaces against libvotca-tools2 (<< 1.3))

[Debian Bug Tracking System]

Your message dated Thu, 03 Mar 2016 00:21:39 +
with message-id 
and subject line Bug#816561: fixed in votca-tools 1.3.0-2
has caused the Debian Bug report #816561,
regarding libvotca-tools3: missing Breaks+Replaces against libvotca-tools2 (<< 
1.3)
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libvotca-tools3.
  Preparing to unpack .../libvotca-tools3_1.3.0-1_amd64.deb ...
  Unpacking libvotca-tools3 (1.3.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvotca-tools3_1.3.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man7/votca-tools.7.gz', which is also in 
package libvotca-tools2 1.2.4-1.1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to unpack .../libudev1_229-1_amd64.deb ...
  Unpacking libudev1:amd64 (229-1) over (228-6) ...
  Processing triggers for libc-bin (2.21-9) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libvotca-tools3_1.3.0-1_amd64.deb


cheers,

Andreas


libvotca-tools-dev_1.3.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: votca-tools
Source-Version: 1.3.0-2

We believe that the bug you reported is fixed in the latest version of
votca-tools, 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.
Michael Banck  (supplier of updated votca-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 03 Mar 2016 01:04:19 +0100
Source: votca-tools
Binary: libvotca-tools-dev libvotca-tools3
Architecture: source
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 libvotca-tools-dev - VOTCA's tools library, development kit
 libvotca-tools3 - VOTCA's tools library
Closes: 816561
Changes:
 votca-tools (1.3.0-2) unstable; urgency=medium
 .
   * debian/control (libvotca-tools3): Added Breaks and Replaces on
 libvotca-tools2 (Closes: #816561).
Checksums-Sha1:
 792d82b4459c772ea01ffd18393af06ff82748a8 2194 votca-tools_1.3.0-2.dsc
 e9a8c68edff33b1f058a91b34c20aa04474ca301 3264 votca-tools_1.3.0-2.debian.tar.xz
Checksums-Sha256:
 e3d9c1ec201d933d5c41ad72eb361742737501d4f463fe9b816f3aba71cf8f9e 2194 
votca-tools_1.3.0-2.dsc
 fdb3a109e40da8c3a0b7ecb4b03fd2bc82aebddd70b1e92a4d7587930ac6808e 3264 
votca-tools_1.3.0-2.debian.tar.xz
Files:
 34ed0591c137ebbdd4768dd011bc2faf 2194 libs optional votca-tools_1.3.0-2.dsc
 e08a590bdd50486ffbc1151721a1fffa 3264 libs optional 
votca-tools_1.3.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW13+ZAAoJENxoaie0NIGwQaoP/ieQQJEKQLY7GKIMHH+UIN7F
70dxhFSKxhC9fYZXWw+/mA72ulZt9Pc3J5iEXadCvvL/CqCwY63qBB5oQPI32umW
YqJiaLYiMC8NLWs7xzF/WbYPoYqEQsCazISMh9jV1w5tv4b6CoX8X0X2Cp/6DpVh
8vLVInOVmt76q+0mj20zkUq30S4QkYGxkptfVIwi08GsU6XO0bK7g4EH2RGwOYkO
IicRdXD/oPf+3jVEdecErA5XovW8JfCJuODSKsyMTfoSFwzS+BsAgps1V1clE0N3
TZH+YF86TM5yRK9fpqaeRxkiZV6PLrnHAqmsrhzkzJMWoYc78Wpb9aiKEoyq7WSA
FYDcb4Tyi9ywbrRHPbjP3MVXBTxCg2OwuJp0z/VQjkvGXl20plCrAfdpk323BvB6
RG84TN06zQglvTWGLyZaLXQMTt6UYI93WqnY2czoCFJPWhHCaeccgWDg532d0cXU
fdB8EVHJix4UtX7PhnNb9lflJU9y4nkZwjqAWmyoOCbS2mpqLoJ2a3e3kP+3SSne
vPCcyAP1nuAl0RhOV96pc9e7BoaT6VcRpSubTazOGCDyW7hy6ISkOZ34l4FegVuP
R0o5JZnK85DaoNM3oARPIZEtZ6V0+iRbF5g5F7/G361/1Sh40r6vWkDCUjVH/a3n

Bug#816288: marked as done (Missing Build-Depends and Depends on php-xml)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 23:28:54 +
with message-id 
and subject line Bug#816288: fixed in pkg-php-tools 1.32
has caused the Debian Bug report #816288,
regarding Missing Build-Depends and Depends on php-xml
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.)


-- 
816288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkg-php-tools
Version: 1.31
Severity: serious
Tags: patch

Hi,

I rebuild php-net-ldap2 against with php-pear/1:1.10.1 (#809771) and get error:

[..]
 dpkg-source --before-build php-net-ldap2-2.2.0
 fakeroot debian/rules clean
dh clean --buildsystem=phppear --with phppear
   dh_testdir -O--buildsystem=phppear
   dh_auto_clean -O--buildsystem=phppear
PHP Fatal error:  Uncaught Error: Call to undefined function
Pkgtools\Phppear\simplexml_load_file() in
/usr/share/php/pkgtools/phppear/source.php:76
[..]


Regard,
Prach
diff --git a/debian/control b/debian/control
index db39ff5..cdceb9c 100644
--- a/debian/control
+++ b/debian/control
@@ -7,14 +7,15 @@ Build-Depends: debhelper (>= 9),
perl,
php-pear,
php-cli,
-   php-json
+   php-json,
+   php-xml
 Vcs-Git: git://anonscm.debian.org/pkg-php/pkg-php-tools.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-php/pkg-php-tools.git;a=summary
 Standards-Version: 3.9.6
 
 Package: pkg-php-tools
 Architecture: all
-Depends: debhelper, php-pear, php-cli, php-json, ${misc:Depends}
+Depends: debhelper, php-pear, php-cli, php-json, php-xml,${misc:Depends}
 Suggests: dh-make
 Description: various packaging tools and scripts for PHP packages
  Provide an easy way to package PHP PEAR, PECL and Composer packages: Run
--- End Message ---
--- Begin Message ---
Source: pkg-php-tools
Source-Version: 1.32

We believe that the bug you reported is fixed in the latest version of
pkg-php-tools, 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.
Mathieu Parent  (supplier of updated pkg-php-tools 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: Wed, 02 Mar 2016 22:46:31 +0100
Source: pkg-php-tools
Binary: pkg-php-tools
Architecture: source all
Version: 1.32
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Mathieu Parent 
Description:
 pkg-php-tools - various packaging tools and scripts for PHP packages
Closes: 814858 815988 816288
Changes:
 pkg-php-tools (1.32) unstable; urgency=medium
 .
   [ Ondřej Surý ]
   * Convert package to PHP 7.0 naming (Closes: #814858)
   * Make php-common always unversioned (for now)
   * Use preg_replace instead of ereg_replace
 .
   [ Mathieu Parent ]
   * Fix test on unversioned php-common
   * extensions DOM, SimpleXML, WDDX, XML, and XSL are now in php-xml:
 - fix Build-Depends and Depends (Closes: #816288)
 - fix overrides
   * Extensions bcmath, bz2, mbstring, soap and zip are no longer builtin
 (Closes: #815988)
   * Standards-Version: 3.9.7: no change
   * Use secure Vcs-* fields
Checksums-Sha1:
 a9436f8a959102deb66ddbde505af43a9900f98a 1733 pkg-php-tools_1.32.dsc
 e84a225284574d42c78d1dadc47ba0df3217b797 37584 pkg-php-tools_1.32.tar.xz
 f0d8b0f3e80a9aee07b839837d49ae30c03b10fa 37986 pkg-php-tools_1.32_all.deb
Checksums-Sha256:
 9f28a669f979dbac7bd579397cd2c8c0fa8318152879d98a59e50591ac6cdaaf 1733 
pkg-php-tools_1.32.dsc
 ed10837bf379fdfef4a12b8ba29a499f61d6d570e5c6853103d7916b1fcda38a 37584 
pkg-php-tools_1.32.tar.xz
 136963467d30dd8e20c8146a70cc530cfc3df0b34885a0e0bb5001f1088af0f9 37986 
pkg-php-tools_1.32_all.deb
Files:
 d04f3963e0e031e41f9a84e3410db88a 1733 php extra pkg-php-tools_1.32.dsc
 ab5bc53dc03a75fedcd4cf29e083a474 37584 php extra pkg-php-tools_1.32.tar.xz
 e9fa4ea73bcefa9f928dd209de07cec8 37986 php extra pkg-php-tools_1.32_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#814858: marked as done (Please, be ready for PHP 7.0 transition)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 23:28:54 +
with message-id 
and subject line Bug#814858: fixed in pkg-php-tools 1.32
has caused the Debian Bug report #814858,
regarding Please, be ready for PHP 7.0 transition
to be marked as done.

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

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


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

Package: phing
Version: 2.13.0-1
Severity: serious
Tags: sid stretch

phing depends on php5-xdebug, which is not available anymore, it should depend 
on php-xdebug (not providing php5-xdebug)
--- End Message ---
--- Begin Message ---
Source: pkg-php-tools
Source-Version: 1.32

We believe that the bug you reported is fixed in the latest version of
pkg-php-tools, 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.
Mathieu Parent  (supplier of updated pkg-php-tools 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: Wed, 02 Mar 2016 22:46:31 +0100
Source: pkg-php-tools
Binary: pkg-php-tools
Architecture: source all
Version: 1.32
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Mathieu Parent 
Description:
 pkg-php-tools - various packaging tools and scripts for PHP packages
Closes: 814858 815988 816288
Changes:
 pkg-php-tools (1.32) unstable; urgency=medium
 .
   [ Ondřej Surý ]
   * Convert package to PHP 7.0 naming (Closes: #814858)
   * Make php-common always unversioned (for now)
   * Use preg_replace instead of ereg_replace
 .
   [ Mathieu Parent ]
   * Fix test on unversioned php-common
   * extensions DOM, SimpleXML, WDDX, XML, and XSL are now in php-xml:
 - fix Build-Depends and Depends (Closes: #816288)
 - fix overrides
   * Extensions bcmath, bz2, mbstring, soap and zip are no longer builtin
 (Closes: #815988)
   * Standards-Version: 3.9.7: no change
   * Use secure Vcs-* fields
Checksums-Sha1:
 a9436f8a959102deb66ddbde505af43a9900f98a 1733 pkg-php-tools_1.32.dsc
 e84a225284574d42c78d1dadc47ba0df3217b797 37584 pkg-php-tools_1.32.tar.xz
 f0d8b0f3e80a9aee07b839837d49ae30c03b10fa 37986 pkg-php-tools_1.32_all.deb
Checksums-Sha256:
 9f28a669f979dbac7bd579397cd2c8c0fa8318152879d98a59e50591ac6cdaaf 1733 
pkg-php-tools_1.32.dsc
 ed10837bf379fdfef4a12b8ba29a499f61d6d570e5c6853103d7916b1fcda38a 37584 
pkg-php-tools_1.32.tar.xz
 136963467d30dd8e20c8146a70cc530cfc3df0b34885a0e0bb5001f1088af0f9 37986 
pkg-php-tools_1.32_all.deb
Files:
 d04f3963e0e031e41f9a84e3410db88a 1733 php extra pkg-php-tools_1.32.dsc
 ab5bc53dc03a75fedcd4cf29e083a474 37584 php extra pkg-php-tools_1.32.tar.xz
 e9fa4ea73bcefa9f928dd209de07cec8 37986 php extra pkg-php-tools_1.32_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW12HUAAoJEK4DmARmaB+lQrIP/0iEVnunnBK6ZJbBr2wHgn79
YhrZWx0RgJZLWocWm0qi3aRFkCZ4lII2kZlWK/2ZNSLoIpuDD1vudyP1EECkwycF
gGHc+GWWwRm5jr73+nqCMFe5+ocjTpSwqg6Cuw3ZTAy04v3ZAr+KuNVxrpG80i+A
VQqwIu98UECR/l0ALzBPKZic1fCX0DPMfGqIjZKci0IDAGPPSN2P83GiWul+Cw1M
/TblBTHTei0vMQiGlwoKtIDugwVv+gerKR2aM6FhKVEiArNz/GIsWxuPUvAdHudP
2SjL6mFOmqAVUURb72G7CzuanVX/D4WYAYpwuKBfD0Stf16g8YGpby7IFM7ym5jz
ogCWTPplO+FpdBXi2awEBfXwjbJDrxuNiWkpBsglvNIL1Rxw+HSn7UFysNEuNDnZ
iAFG4Uj5po7Hdk0YIZ/DBeZgpFnukMzwYTYYfE/Y+bcOlGZ81wF3QiTG2OJDkLGI
3aDImsTz6x1l3p3ytNqqgBkFwAD1nnlD6c4y8XKOo7O/TbgRab0pBU6FbtLbdQlj
likYCkgS/enk14Rohp8ghcg+TSZxUrKL8lgNGQkMqsaKiThdh8Ve7UDwjXBhwqUt
q3FrNTFD1Nw0vF6aJnq04i55qEwPFbCvSXcFrYqnfHSUsWYVxOmPCfWSpgTVbkhf
5smZBozEibr1ETxoHS3h
=MGAG
-END PGP SIGNATURE End Message ---

Bug#816561: libvotca-tools3: missing Breaks+Replaces against libvotca-tools2 (<< 1.3)

[Andreas Beckmann]

Package: libvotca-tools3
Version: 1.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libvotca-tools3.
  Preparing to unpack .../libvotca-tools3_1.3.0-1_amd64.deb ...
  Unpacking libvotca-tools3 (1.3.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvotca-tools3_1.3.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man7/votca-tools.7.gz', which is also in 
package libvotca-tools2 1.2.4-1.1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to unpack .../libudev1_229-1_amd64.deb ...
  Unpacking libudev1:amd64 (229-1) over (228-6) ...
  Processing triggers for libc-bin (2.21-9) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libvotca-tools3_1.3.0-1_amd64.deb


cheers,

Andreas


libvotca-tools-dev_1.3.0-1.log.gz
Description: application/gzip

Bug#794161: marked as done (FTBFS: undefined method `share_as' for RSpec::ExampleGroups::FencedCodeBlock::Basic:Class (NoMethodError))

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 22:15:23 +
with message-id 
and subject line Bug#794161: fixed in ruby-bluefeather 0.41-4
has caused the Debian Bug report #794161,
regarding FTBFS: undefined method `share_as' for 
RSpec::ExampleGroups::FencedCodeBlock::Basic: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.)


-- 
794161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-bluefeather
Version: 0.41-3
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 -Ku /usr/bin/rspec --pattern spec/\*.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': 
undefined method `share_as' for 
RSpec::ExampleGroups::FencedCodeBlock::Basic:Class (NoMethodError)
from /tmp/buildd/ruby-bluefeather-0.41/spec/code-block.rb:33:in `block 
(2 levels) in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /tmp/buildd/ruby-bluefeather-0.41/spec/code-block.rb:32:in `block 
in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in 
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 
levels) in expose_example_group_alias_globally'
from /tmp/buildd/ruby-bluefeather-0.41/spec/code-block.rb:24: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 -Ku /usr/bin/rspec --pattern spec/\*.rb failed
ERROR: Test "ruby2.1" failed. Exiting.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-bluefeather.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 ---
Source: ruby-bluefeather
Source-Version: 0.41-4

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

Debian distribution maintenance software
pp.
Lucas Albuquerque Medeiros de Moura  (supplier of 
updated ruby-bluefeather 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: Wed, 02 Mar 2016 14:05:40 -0300
Source: ruby-bluefeather
Binary: ruby-bluefeather
Architecture: source
Version: 0.41-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Albuquerque Medeiros de Moura 
Description:
 ruby-bluefeather - Extend Markdown Converter written in 

Bug#814809: [pkg-php-pear] Bug#814809: Moving forward with the PHP 7.0 transition [Was: phing depends on php5-xdebug, which is not available anymore]

[Mathieu Parent]

2016-02-22 20:43 GMT+01:00 Mathieu Parent :
[...]
> i.e we need php-pear to pass NEW (which include the needed fix |1])

Now that php-pear is in sid, I've uploaded newer pkg-php-tools.

Remaining lintian warnings:
E: pkg-php-tools: php-script-but-no-phpX-cli-dep usr/bin/pkgtools
E: pkg-php-tools: php-script-but-no-phpX-cli-dep
usr/share/pkg-php-tools/scripts/phppkginfo


Also, the phpunit tests need to be fixed.

Regards

-- 
Mathieu

Bug#814589: otrs2: source-less files; undocumented copyrights/licenses; abuse of lintian-overrides; systematic DFSG violations

[Dmitry Smirnov]

Dear Patrick,

On Wed, 2 Mar 2016 12:36:46 PM Patrick Matthäi wrote:
> Am 15.02.2016 um 14:14 schrieb Dmitry Smirnov:
> > And this is why I provided some hints how you can address those problems
> > in my bug report. This is why I wrote to you after when I stabilised
> > "ckeditor" so you could use it.
> 
> I can use it, until ckeditor OR otrs upstreams broke it again, like with
> jquery.

Thank you for checking. I think using bundled ckeditor is not an option 
because it is source-less and shipped as minified blobs.
jQuery is a lot easier to handle because it is just one file.


> Also it would prevent backports of otrs to jessie.

I'm already working on that. "ckbuilder" is in backports/NEW and once 
accepted I'll upload "ckeditor" (which I need in backports for one of my 
packages as well).


> >> and mostly it is not possible to replace the
> >> libjs thirdparty foo with the packages from Debian, mostly because of
> >> version missmatches.

As I've said, you don't have to replace all bundled JS libraries with system 
ones as it might make package needlessly fragile and difficult to backport.

What you have to do is to find original/uncompressed JS files and ship them 
in "debian/missing-sources" ideally replacing minified files as well.
It is easy to do and safe and it will help your package to comply with DFSG 
requirements. 


> You reported a very general bug about the whole javascript mess.
> Replacing ckeditor will not solve the other problems or all those
> minified files and so on.

You have to start somewhere don't you? I'm not even Otrs2 user (let alone 
maintainer) so why do expect more from me?


> Investing work in removing those files will not realy help and just
> burden the whole packaging and eat time to fix realy serious issues -
> like embedded libs.

I think DFSG compliance is not optional in Debian.
Shipping missing sources in "debian/missing-sources" shouldn't take too much 
effort... Did you consider this option?

-- 
Regards,
 Dmitry Smirnov.

---

Odious ideas are not entitled to hide from criticism behind the human
shield of their believers' feelings.
-- Richard Stallman


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

Bug#815685: marked as done (libxs: update for libpgm 5.2 transition)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 22:01:17 +
with message-id 
and subject line Bug#815685: fixed in libxs 1.2.0-2
has caused the Debian Bug report #815685,
regarding libxs: update for libpgm 5.2 transition
to be marked as done.

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

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


-- 
815685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxs
Version: 1.2.0-1.1
Severity: serious
Tags: patch
Justification: FTBFS and holds back libpgm transition

The package is FTBFS now, as it looks for the previous soname of
libpgm. The fix is simple, change configure.in to look for the 5.2
soname. For clarity, patch is attached. It's tested and works as
expected.Description: look for libpgm 5.2
 Simply update the version number to look for in configure.in
Author: Laszlo Boszormenyi (GCS) 
Forwarded: no
Last-Update: 2016-02-23

---

--- libxs-1.2.0.orig/configure.ac
+++ libxs-1.2.0/configure.ac
@@ -473,7 +473,7 @@ AS_IF([test "x$with_pgm_ext" != "xno"],
 # Build with system openpgm
 AS_IF([test "x$with_system_pgm_ext" != "xno"], [
 m4_ifdef([PKG_CHECK_MODULES], [
-PKG_CHECK_MODULES([OpenPGM], [openpgm-5.1 >= 5.1])
+PKG_CHECK_MODULES([OpenPGM], [openpgm-5.2 >= 5.2])
 AC_DEFINE([XS_HAVE_OPENPGM], [1], [Have OpenPGM extension])
 LIBXS_EXTRA_CXXFLAGS="$OpenPGM_CFLAGS $LIBXS_EXTRA_CXXFLAGS"
 ],
--- End Message ---
--- Begin Message ---
Source: libxs
Source-Version: 1.2.0-2

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

Debian distribution maintenance software
pp.
Robert Edmonds  (supplier of updated libxs 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: Wed, 02 Mar 2016 16:00:49 -0500
Source: libxs
Binary: libxs-dev libxs2
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Robert Edmonds 
Changed-By: Robert Edmonds 
Description:
 libxs-dev  - Crossroads I/O lightweight messaging layer (development files)
 libxs2 - Crossroads I/O lightweight messaging layer (shared library)
Closes: 715128 754324 815685
Changes:
 libxs (1.2.0-2) unstable; urgency=medium
 .
   [ Laszlo Boszormenyi (GCS) ]
   * configure.ac: Update for libpgm 5.2 transition (Closes: #815685)
 .
   [ Robert Edmonds ]
   * debian/control: Update Maintainer
   * debian/control: Update Vcs-Browser
   * debian/control: Delete Homepage
   * debian/control: Bump Standards-Version to 3.9.7 (no changes)
   * debian/: Remove libxs-compat-libzmq* packages (Closes: #715128)
   * configure.ac: Disable -Werror, don't FTBFS due to compiler diagnostics
 (Closes: #754324)
   * debian/gbp.conf: New
   * debian/: Run "wrap-and-sort -sabt"
   * debian/: Remove libxs2-dbg package
   * debian/compat: 8 -> 9
   * debian/*.install: Update for multi-arch paths
Checksums-Sha1:
 c2d8c7a401eb74cffb11581b0b8c062322cf0af4 1876 libxs_1.2.0-2.dsc
 4c05b0380d642a483c9498846afc0f2e07c2cd0b 4784 libxs_1.2.0-2.debian.tar.xz
Checksums-Sha256:
 15ab38b4287ac81e4643c63a395c2c693615aa545f0f3f55dc678425b54fc0cf 1876 
libxs_1.2.0-2.dsc
 c07b083b65e2570ff3de90ccd4eb3b2c3bd2832045724429fe51b04d5fe010af 4784 
libxs_1.2.0-2.debian.tar.xz
Files:
 03742af86d581aabb8d15527e66e2b51 1876 libs optional libxs_1.2.0-2.dsc
 ee6517b7bb35ead015f601200ea547ef 4784 libs optional libxs_1.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJW11a+AAoJEAGBerCq9s2uXj8P/iG5YRmRI2djt9OCZw1kW82b
yhiAKGeDKWMQjfMpnll76RfBEa+lQZpuFPTsvQ4ZzfpZ3APilAqnAM2zvlCidZMT
1nyGaaM677uZMpNLcaC7g9g3brdn/1ya2Qr0nBKX1tu31bWnUfMi4yYtL+eQMzBO
OluOZ6gsxdKyzvBz58hPpS9MpUgzfYYpFW56YIoU5rwiM2a3H0WW8zrUcr1DMpOt
qTyCsTem88Lr+HsiC8eDMUE7TGokI9rp3Hmd5W+S8ihhcz0H8b0GhXd7lV7dDIFw
DutKBFU3ph5zuNJRxdzpmd6NSneFGoa5RBW+52qEXT0RhK1NJIcSJDXuMEJ3kpDx
EFZSzxEQMx9q42DPlTRNw/3BhDkikbrLaLF4pRzWTnMar8vpBMXw35CsQzilSKQb
RQfRl3yHInn4qaP40XMLKcFmSksofJVIheVsoJyc9kFuu6yXMCpZKwFprkb1cpgM

Processed: severity of 816533 is important

[Debian Bug Tracking System]

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

> severity 816533 important
Bug #816533 [xpra] [xpra] Does not start: Error starting Xvfb: [Errno 2] No 
such file or directory
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#816533: [xpra] Does not start: Error starting Xvfb: [Errno 2] No such file or directory

[Dmitry Smirnov]

On Wed, 2 Mar 2016 06:13:56 PM Bruno Kleinert wrote:
> Severity: grave

Please don't panic and use correct severity levels:

https://www.debian.org/Bugs/Developer#severities


> xpra fails to start for me since a couple of days:

There were no recent upload of Xpra so the problem is likely to be somewhere 
else...

-- 
All the best,
 Dmitry Smirnov.


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

Bug#816492: [debian-mysql] Bug#816492: galera-3: Galera fails to build with pbuilder for armhf (on amd64)

[Otto Kekäläinen]

Severity: wishlist

Please note that galera-3 in Debian is available only in unstable and
testing at the moment:
https://packages.debian.org/search?keywords=galera-3=names=all=all

Filing a bug about Jessie is a whishlist type of an issue as galera-3
is not available on Jessie. Galera builds fine on all Debian platforms
it has been published for in official Debian repositories.

Bug#810506: Opinion about linux-grsec in a stable release

[Yves-Alexis Perez]

On mer., 2016-03-02 at 20:06 +0100, Moritz Muehlenhoff wrote:
> Before considering that, did anyone approch grsecurity whether we can get
> access to the grsecurity stable patches? We would most definitely have Debian
> funds to become grsecurity sponsors to obtain access to stable patches.

I think that'd be something nice anyway, but…
> 
> Whether that's possible/desirable by grsecurity is the question, though:
> Having the stable patches in Debian would make them available to the
> general public (including those sleazy embedded companies which made them
> change their distribution scheme).

Indeed, I didn't even bother to ask because when you gain access to the stable
patches, you commit yourself to not make them available publicly, which is
obviously exactly what we would do.

Regards,
-- 
Yves-Alexis



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

Bug#816482: marked as done (ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError))

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 19:56:59 +
with message-id 
and subject line Bug#816482: fixed in ruby-acts-as-list 0.7.2-4
has caused the Debian Bug report #816482,
regarding ruby-acts-as-list: FTBFS: `require': cannot load such file -- 
bundler/setup (LoadError)
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.)


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

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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-acts-as-list.0.7.2-3.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-acts-as-list
Source-Version: 0.7.2-4

We believe that the bug you reported is fixed in the latest version of
ruby-acts-as-list, 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 

Processed: found 809766 in ruby-test-unit/3.1.7-2

[Debian Bug Tracking System]

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

> found 809766 ruby-test-unit/3.1.7-2
Bug #809766 [ruby-rubysl-test-unit,ruby-test-unit] ruby-test-unit and 
ruby-rubysl-test-unit: error when trying to install together
Marked as found in versions ruby-test-unit/3.1.7-2.
> thanks
Stopping processing here.

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

Processed: severity of 816545 is serious, severity of 816546 is serious

[Debian Bug Tracking System]

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

> severity 816545 serious
Bug #816545 [ruby-innertube] ruby-innertube: FTBFS with ruby2.2
Severity set to 'serious' from 'normal'
> severity 816546 serious
Bug #816546 [ruby-markerb] ruby-markerb: FTBFS on ruby2.2
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#810506: Opinion about linux-grsec in a stable release

[Moritz Muehlenhoff]

On Wed, Mar 02, 2016 at 10:09:47AM +0100, Yves-Alexis Perez wrote:
> Hi teams,
> 
> [first of all, I'm writing this with my linux-grsec hat, not my Debian
> security team member hat, obviously]
> 
> As you may know, src:linux-grsec was accepted in unstable earlier this year.
> As a quick summary, this is a source linux package (forked from and
> periodically rebased against src:linux) which generates a linux kernel with
> the grsecurity hardening patch (the patch is mostly about fighting memory
> corruptions bugs, but not only, I won't enter into details here to keep it
> short, but more information can be found in the ITP bug #605090).
> 
> When the package was accepted to unstable, I filed #810506 with severity
> serious in order to prevent it to migrate to testing, because I wasn't really
> sure it'd be fit for stable.
> 
> There are two main aspects for this:
> 
> - it's a new Linux kernel source package, next to the existing src:linux, so
> that means code duplication
> - due to the grsecurity release model, it's likely that it won't be possible
> to stick with a major kernel version (4.3 right now, 4.4 upcoming), we would
> have to upgrade to the latest major release (using stable uploads)

Before considering that, did anyone approch grsecurity whether we can get
access to the grsecurity stable patches? We would most definitely have Debian
funds to become grsecurity sponsors to obtain access to stable patches.

Whether that's possible/desirable by grsecurity is the question, though:
Having the stable patches in Debian would make them available to the
general public (including those sleazy embedded companies which made them
change their distribution scheme).

(However a determined, GPL violating embedded company who wants access to
the stable patches would likely find a way anyway)

Cheers,
Moritz

Bug#797255: marked as done (ruby-mathml: FTBFS: rspec3 port needed(?): expected true to respond to `true?` or perhaps you meant `be true` or `be_truthy`)

[Debian Bug Tracking System]

Your message dated Wed, 2 Mar 2016 19:53:03 +0100
with message-id <20160302185303.GA32511@esfahan>
and subject line fixed by upload of 0.14-4
has caused the Debian Bug report #797255,
regarding ruby-mathml: FTBFS: rspec3 port needed(?): expected true to respond 
to `true?` or perhaps you meant `be true` or `be_truthy`
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.)


-- 
797255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mathml
Version: 0.14-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.1 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/ruby-mathml-0.14/debian/ruby-mathml/usr/lib/ruby/vendor_ruby:. rake2.1 
-f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
F..F.F.FFF..FF..F.FFF.F..F...

Failures:

  1) MathML::Element #display_style and #as_display_style
 Failure/Error: e.display_style.should be_true
   expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
 # ./spec/math_ml/element_spec.rb:9:in `block (2 levels) in '

  2) MathML::LaTeX::Macro #parse
 Failure/Error: lambda{@m.parse('\newcommand{notcommand}{}')}.should 
raise_parse_error("Need newcommand.", '\\newcommand{', "notcommand}{}")
 ArgumentError:
   wrong number of arguments (1 for 3+)
 # ./spec/util.rb:11:in `new'
 # ./spec/util.rb:11:in `raise_parse_error'
 # ./spec/math_ml/latex/macro_spec.rb:32:in `block (2 levels) in '

  3) MathML::LaTeX::Macro #expand_command
 Failure/Error: lambda{@m.expand_command("paramcom", ["12"])}.should 
raise_parse_error("Need more parameter.", "", "")
 ArgumentError:
   wrong number of arguments (1 for 3+)
 # ./spec/util.rb:11:in `new'
 # ./spec/util.rb:11:in `raise_parse_error'
 # ./spec/math_ml/latex/macro_spec.rb:76:in `block (2 levels) in '

...

  26) MathML::LaTeX::Parser#symbol_table should return default symbol module 
numeric character reference version when set by requiring should be true
  Failure/Error: require("math_ml/symbol/character_reference").should 
be_true
expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
  # ./spec/math_ml/latex/parser_spec.rb:574:in `block (5 levels) in '

Deprecation Warnings:

Using `should` from rspec-expectations' old `:should` syntax without explicitly 
enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly 
enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` 
instead. Called from /ruby-mathml-0.14/spec/math_ml/element_spec.rb:5:in `block 
(2 levels) in '.

...

ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install /ruby-mathml-0.14/debian/ruby-mathml 
returned exit code 1
debian/rules:10: recipe for target 'override_dh_auto_install' failed

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Control: fixed -1 0.14-4
Control: notfound -1 0.14-4

Hi,

This bug has been fixed by the upload of ruby-mathml 0.14-4.

Changes:
 ruby-mathml (0.14-4) unstable; urgency=medium
 .
   * Team upload.
   * Fix tests for rspec version 3.3.0.
   * Fix custom matcher definition for rspec version 3.3.0.
   * Fix test require for autopkgtest.
   * debian/compat: Bump to bersion 9, silence lintian warning.
   * debian/control: Update vcs-git link to https, silence lint
+ian warning.
   * debian/control: Update vcs-browser link to https, silence
+lintian warning.
   * debian/control: Update standards-version to 3.9.7, silence
+lintian
 warning.
   * debian/control: Update deb-helper to require version >= 9.

I am thus closing this bug.

Cheers,

Cédric


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

Bug#788546: Sorry for late answer, got no notification on your posting

[Ingo]

Das mit den Locales hat es nicht gebracht, da ist sowohl auf dem nas als
auch auf dem PC die gleiche:

PC:$ echo $LANG
de_DE.utf8

nas: $ echo $LANG
de_DE.UTF-8

But a workaround is documented in this Bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790880
which has been merged here. This states:

Using "mount.nfs" instead allows  mounting by a user:

Executing mount.nfs as a user with full path does not respect the
mountpoint as configured in fstab:

~$ /sbin/mount.nfs leo:/Bilder
~$ mount.nfs: no mount point provided

Adding the mountpoint works for both mount and umount:

~$ /sbin/mount.nfs leo:/Bilder /home/ingo/leo.Bilder
~$ /sbin/umount.nfs /home/ingo/leo.Bilder

That's why I assigned it also to Package: mount.

Today I checkes in Stretch: still the same issue.

Processed: tagging 816527

[Debian Bug Tracking System]

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

> # in git, cf. the github issue
> tags 816527 + fixed-upstream
Bug #816527 [src:libtest-file-contents-perl] libtest-file-contents-perl: FTBFS 
with Text::Diff 1.44
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#755600: marked as done (djagios: Please ensure it works with Django 1.7)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 18:19:29 +
with message-id 
and subject line Bug#755600: fixed in djagios 0.1.3+dfsg-5
has caused the Debian Bug report #755600,
regarding djagios: Please ensure it works with Django 1.7
to be marked as done.

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

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


-- 
755600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: djagios
Version: 0.1.3+dfsg-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django17

Hello,

your package djagios depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.
--- End Message ---
--- Begin Message ---
Source: djagios
Source-Version: 0.1.3+dfsg-5

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated djagios 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 02 Mar 2016 14:53:46 -0300
Source: djagios
Binary: djagios
Architecture: source all
Version: 0.1.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Giovani Augusto Ferreira 
Changed-By: Giovani Augusto Ferreira 
Description:
 djagios- tool to help configure nagios written in Django
Closes: 755600
Changes:
 djagios (0.1.3+dfsg-5) unstable; urgency=medium
 .
   * debian/control:
  - Bumped dependency for python-django to >= 1.7.7 (Closes: #755600)
  - Updated Vcs-* fields.
Checksums-Sha1:
 4e260b4ddb3988563116e1bb51f8bd72dc8f2a2a 1901 djagios_0.1.3+dfsg-5.dsc
 730754960d4bc8e1c4ac4ac9d5458cdb3a592bb2 3188 
djagios_0.1.3+dfsg-5.debian.tar.xz
 71e7e15b4908a98ab1677e3c640f26eb56309797 37832 djagios_0.1.3+dfsg-5_all.deb
Checksums-Sha256:
 d229eabc402f3f31d7370bd2d6f33ddafebc1232fdffd64bee778ad4a627a762 1901 
djagios_0.1.3+dfsg-5.dsc
 df77ea6366ed454e7c97aacdc975de082ec9d41d9a41e837bb2a32ad93d94fa5 3188 
djagios_0.1.3+dfsg-5.debian.tar.xz
 f510eef524bf2b6d6f418fba9e766251c0c1ef0446a5a8c57aeef88088588b22 37832 
djagios_0.1.3+dfsg-5_all.deb
Files:
 8bd5064027ab1e843ab6f650abc4b45e 1901 admin optional djagios_0.1.3+dfsg-5.dsc
 f4f4ea38b1f08d3ce6c5468feb595602 3188 admin optional 
djagios_0.1.3+dfsg-5.debian.tar.xz
 393533dae790198a59830214a6c320df 37832 admin optional 
djagios_0.1.3+dfsg-5_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#816535: Missing dependencies

[Adam Majer]

Package: libbotan1.10-dev
Version: 1.10.12-1
Severity: serious

libbotan1-10-dev is missing dependencies. config requires quite a few libraries,

   $ botan-config-1.10 --libs
   -lbotan-1.10 -lbz2 -lcrypto -ldl -lgmp -lpthread -lrt -lz

but these are not listed,

Depends: libbotan-1.10-1 (= 1.10.12-1)

Please add required -dev dependencies to the -dev package.

Thanks,
Adam


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

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

Versions of packages libbotan1.10-dev depends on:
ii  libbotan-1.10-1  1.10.12-1

libbotan1.10-dev recommends no packages.

libbotan1.10-dev suggests no packages.

-- no debconf information

Bug#815118: marked as done (ruby-rspec-expectations: FTBFS - undefined method `color_enabled=')

[Debian Bug Tracking System]

Your message dated Wed, 2 Mar 2016 18:54:58 +0100
with message-id <20160302175458.GB9107@esfahan>
and subject line not applicable
has caused the Debian Bug report #815118,
regarding ruby-rspec-expectations: FTBFS - undefined method `color_enabled='
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.)


-- 
815118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rspec-expectations
Version: 2.14.2-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
/usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-expectations/ruby-rspec-expectations-2.14.2/debian/ruby-rspec-expectations/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-expectations/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-rspec-expectations/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-expectations/ruby-rspec-expectations-2.14.2/spec/spec_helper.rb:5:in
 `block in ': undefined method `color_enabled=' for 
# (NoMethodError)
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-expectations/ruby-rspec-expectations-2.14.2/spec/spec_helper.rb:3:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-expectations/ruby-rspec-expectations-2.14.2/spec/rspec/expectations/differ_spec.rb:5: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.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-expectations/ruby-rspec-expectations-2.14.2/debian/ruby-rspec-expectations
 returned exit code 1
debian/rules:15: recipe for target 'binary' failed


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


ruby-rspec-expectations-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
This source package has been removed from the archive (#816323).
I am thus closing this bug.

Thanks,

Cédric



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

Bug#815118: wrong bug number

[Cédric Boutillier]

I meant #816324


signature.asc
Description: PGP signature

Bug#815117: marked as done (ruby-rspec-core: FTBFS - tests fail with NoMethodError: undefined method `run')

[Debian Bug Tracking System]

Your message dated Wed, 2 Mar 2016 18:54:06 +0100
with message-id <20160302175406.GA9107@esfahan>
and subject line not applicable
has caused the Debian Bug report #815117,
regarding ruby-rspec-core: FTBFS - tests fail with NoMethodError: undefined 
method `run'
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.)


-- 
815117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rspec-core
Version: 2.14.7-2
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
/usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-core/ruby-rspec-core-2.14.7/debian/ruby-rspec-core/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-core/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-rspec-core/usr/share/rubygems-integration/all
 ruby2.2 debian/ruby-tests.rb
Run options:
  include {:focus=>true}
  exclude {:ruby=>#}

All examples were filtered out; ignoring {:focus=>true}
F
An error occurred 
  NoMethodError: undefined method `run' for 
#
  occurred at 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-core/ruby-rspec-core-2.14.7/lib/rspec/core/example_group.rb:390:in
 `block in run_examples'

FF

Failures:

  1) RSpec::Core::BacktraceCleaner with no patterns keeps all lines
 Failure/Error: Unable to find matching line from backtrace
 NameError:
   undefined method `orig_run' for class `RSpec::Core::Example'
 # ./spec/support/sandboxed_mock_space.rb:42:in `alias_method'
 # ./spec/support/sandboxed_mock_space.rb:42:in `block in sandboxed'
 # ./spec/support/sandboxed_mock_space.rb:40:in `class_eval'
 # ./spec/support/sandboxed_mock_space.rb:40:in `ensure in sandboxed'
 # ./spec/support/sandboxed_mock_space.rb:46:in `sandboxed'
 # debian/ruby-tests.rb:9:in `'

[...]
No examples found.


Finished in 0.7 seconds
0 examples, 0 failures
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-rspec-core/ruby-rspec-core-2.14.7/debian/ruby-rspec-core
 returned exit code 1
debian/rules:23: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


ruby-rspec-core-build-log.txt.gz
Description: application/gunzip


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

This source package has been removed from the archive (#816323).
I am thus closing this bug.

Thanks,

Cédric


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

Bug#816533: [xpra] Does not start: Error starting Xvfb: [Errno 2] No such file or directory

[Bruno Kleinert]

Package: xpra
Version: 0.15.8+dfsg-1+b1
Severity: grave

--- Please enter the report below this line. ---
Hi there,

xpra fails to start for me since a couple of days:

(0)fuddl@flutschi:~$ xpra start --no-daemon  --start=/usr/bin/gnome-terminal
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Failed to rename log file "/home/fuddl/.xpra/Xorg.S14576.log" to 
"/home/fuddl/.xpra/Xorg.S14576.log": No such file or directory

X.Org X Server 1.18.1
Release Date: 2016-02-08
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux flutschi 4.4.0-1-amd64 #1 SMP Debian 4.4.2-3 
(2016-02-21) x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-1-amd64 
root=/dev/mapper/vg0-root ro splash
Build Date: 09 February 2016  11:06:03AM
xorg-server 2:1.18.1-1 (http://www.debian.org/support) 
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/home/fuddl/.xpra/Xorg.S14576.log", Time: Wed Mar  2 17:58:53 
2016
(++) Using config file: "/etc/xpra/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Using display number provided by Xorg: :1
2016-03-02 17:58:53,290 Error starting Xvfb: [Errno 2] No such file or directory

This drops me back to the prompt with an Xorg process running in the
background. Installing the package xvfb does not help.

Greetings - Fuddl

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

Debian Release: stretch/sid
  500 unstableftp.uni-erlangen.de 
1 experimentalftp.uni-erlangen.de 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.





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

Bug#816530: gnome-logs: FTBFS: ? tag-missing : not specified

[Daniel Schepler]

Source: gnome-logs
Version: 3.18.1-1
Severity: serious

>From my pbuilder build log:

...
Making check in po
make[3]: Entering directory '/build/gnome-logs-3.18.1/po'
INTLTOOL_EXTRACT="/usr/bin/intltool-extract" XGETTEXT="/usr/bin/xgettext" 
srcdir=. /usr/bin/intltool-update --gettext-package gnome-logs --pot
rm -f missing notexist
srcdir=. /usr/bin/intltool-update -m
if [ -r missing -o -r notexist ]; then \
  exit 1; \
fi
make[3]: Leaving directory '/build/gnome-logs-3.18.1/po'
make[3]: Entering directory '/build/gnome-logs-3.18.1'
LC_ALL=C /usr/bin/intltool-merge  -x -u -c ./po/.intltool-merge-cache ./po 
data/org.gnome.Logs.appdata.xml.in data/org.gnome.Logs.appdata.xml
Found cached translation database
Merging translations into data/org.gnome.Logs.appdata.xml.
CREATED data/org.gnome.Logs.appdata.xml
if test -f "data/org.gnome.Logs.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate 
${d}data/org.gnome.Logs.appdata.xml; fi \
&& touch data/org.gnome.Logs.appdata.valid
data/org.gnome.Logs.appdata.xml: 
(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.

(appstream-util:7391): dconf-CRITICAL **: unable to create directory 
'/nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
FAILED:
? tag-missing   :  not specified
Validation of files failed
Makefile:2124: recipe for target 'data/org.gnome.Logs.appdata.valid' failed
make[3]: *** [data/org.gnome.Logs.appdata.valid] Error 1
make[3]: Leaving directory '/build/gnome-logs-3.18.1'
Makefile:1472: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/build/gnome-logs-3.18.1'
Makefile:1941: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/build/gnome-logs-3.18.1'
dh_auto_test: make -j1 check returned exit code 2
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#816529: libmpc: FTBFS: required file 'config/compile' not found

[Daniel Schepler]

Source: libmpc
Version: 2:0.1~r475-1
Severity: serious

>From my pbuilder build log:

...
 debian/rules build
test -x debian/rules
mkdir -p "."

WARNING: copyright-check disabled - touch debian/copyright_hints to enable.

touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
dh_autoreconf 
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
aclocal: warning: couldn't open directory 'm4': No such file or directory
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:10: installing 'config/compile'
configure.in:11: installing 'config/config.guess'
configure.in:11: installing 'config/config.sub'
configure.in:6: installing 'config/install-sh'
configure.in:6: installing 'config/missing'
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
libmpcdec/Makefile.am: installing 'config/depcomp'
dpkg-query: package 'autoheader' is not installed and no information is 
available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
cd . && libtoolize -c -f
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
cd . && aclocal-1.15 -I m4
aclocal-1.15: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . && `which 
autoconf2.69 || which autoconf`; fi
if [ -e ./Makefile.am ]; then cd . &&  automake-1.15  ; fi
automake-1.15: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:10: error: required file 'config/compile' not found
configure.in:10:   'automake --add-missing' can install 'compile'
configure.in:6: error: required file 'config/missing' not found
configure.in:6:   'automake --add-missing' can install 'missing'
automake-1.15: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
libmpcdec/Makefile.am: error: required file 'config/depcomp' not found
libmpcdec/Makefile.am:   'automake --add-missing' can install 'depcomp'
/usr/share/cdbs/1/class/autotools-files.mk:62: recipe for target 
'debian/stamp-autotools-files' failed
make: *** [debian/stamp-autotools-files] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#816495: marked as done ([pysatellites] Does not contain executable)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 16:28:47 +
with message-id 
and subject line Bug#816495: fixed in pysatellites 2.4-1
has caused the Debian Bug report #816495,
regarding [pysatellites] Does not contain executable
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.)


-- 
816495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pysatellites
Version: 2.3-2
Severity: serious

Hi.

$ dpkg -L pysatellites
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/pysatellites
/usr/share/doc/pysatellites/changelog.gz
/usr/share/doc/pysatellites/changelog.Debian.gz
/usr/share/doc/pysatellites/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/pysatellites.1.gz

(or, if you prefer,
https://packages.debian.org/sid/all/pysatellites/filelist)

There are no executables in the package! :-)

Probably just a missing install line.

Thanks, Giovanni.


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.4.0-trunk-amd64

Debian Release: stretch/sid
  500 unstablerepos.fds-team.de
  500 unstableftp.ch.debian.org
  500 stable  dl.google.com
  500 sid linux.dropbox.com
1 experimentalftp.ch.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Giovanni Mascellani 
PhD Student - Scuola Normale Superiore, Pisa, Italy

http://poisson.phc.unipi.it/~mascellani



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pysatellites
Source-Version: 2.4-1

We believe that the bug you reported is fixed in the latest version of
pysatellites, 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.
Georges Khaznadar  (supplier of updated pysatellites 
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: Wed, 02 Mar 2016 16:36:01 +0100
Source: pysatellites
Binary: pysatellites python-satellites
Architecture: source all
Version: 2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 pysatellites - simulates the launching of satellites
 python-satellites - transitional package to upgrade to the newer pysatellites
Closes: 816495
Changes:
 pysatellites (2.4-1) unstable; urgency=medium
 .
   * removed setup.py, so only the Makefile is taken in account.
   * added a file debian/pysatellites.install. Closes: #816495
   * assigned Section: oldlibs/python for the transitionall package.
Checksums-Sha1:
 1d98f7368ee2cf026bbd478821f4f696feef3ec5 1798 pysatellites_2.4-1.dsc
 7da4322773b3c18587502aa4c144d94a00ddeeb4 44196 pysatellites_2.4.orig.tar.xz
 e2eafac094d0807d0f6b80caf0cb6a59ceef3b0d 3328 pysatellites_2.4-1.debian.tar.xz
 ca7ceadbc585915bf7288cf02ad4880d5daca08a 2482296 pysatellites_2.4-1_all.deb
 16a8473383c55beba3a85bb74d616a5a94db18c9 4276 python-satellites_2.4-1_all.deb
Checksums-Sha256:
 5fed3743c804b6a0414314119fa2f17f7352f6d9f4993e88d3a1daeb7e615ed4 1798 
pysatellites_2.4-1.dsc
 bfb5840739604a075f7d78c66831df49ec5dcb7be13ff8c041949adacf84d466 44196 
pysatellites_2.4.orig.tar.xz
 8ad164d55aa7e7447e39ec221afbcb198f41377009274655ad8df25ca48788a8 3328 
pysatellites_2.4-1.debian.tar.xz
 89d4df3aa10f299df515806ef00916f3c5d27767eca57321053c9b4eb708da62 2482296 
pysatellites_2.4-1_all.deb
 43335c5349d42d3decedcaa9d0c056f2a0f8901b1bd36c8656d2d612aee5d215 4276 
python-satellites_2.4-1_all.deb
Files:
 377de5b71033f697dbefb7be85c3355e 1798 x11 extra pysatellites_2.4-1.dsc
 8e78894f1541303feb802730ae21fa87 44196 x11 extra pysatellites_2.4.orig.tar.xz
 24a1d56a53beea5d0ca3e4923b4e6976 3328 x11 extra 
pysatellites_2.4-1.debian.tar.xz
 d5d78cb14cc8e748a662b24543accead 2482296 x11 extra pysatellites_2.4-1_all.deb
 beff02f3f7ee5bc6f09ca7b82cf02a28 4276 x11 extra python-satellites_2.4-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: 815798

[Debian Bug Tracking System]

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

> tag 815798 - unreproducible
Bug #815798 [gitlab] (no subject)
Removed tag(s) unreproducible.
> tag 815798 + patch
Bug #815798 [gitlab] (no subject)
Added tag(s) patch.
>
End of message, 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#816528: plasma-framework-dev: fails to upgrade from 'sid' - trying to overwrite /usr/share/kdevappwizard/templates/qml-plasmoid.tar.bz2

[Andreas Beckmann]

Package: plasma-framework-dev
Version: 5.19.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package plasma-framework-dev.
  Preparing to unpack .../plasma-framework-dev_5.19.0-1_amd64.deb ...
  Unpacking plasma-framework-dev (5.19.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/plasma-framework-dev_5.19.0-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/kdevappwizard/templates/qml-plasmoid.tar.bz2', which is also in 
package kapptemplate 4:15.12.1-1


cheers,

Andreas

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

[Raúl Benencia]

Control: tags 815742 + patch
Control: tags 815742 + pending

Dear Tomasz,

I've prepared an NMU for verbiste (versioned as 0.1.42-2.1). As I don't
have privileges to upload it to DELAYED, I've uploaded it to the mentors
repository.

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/verbiste

Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/v/verbiste/verbiste_0.1.42-2.1.dsc

Regards,
Rul
diff -Nru verbiste-0.1.42/debian/changelog verbiste-0.1.42/debian/changelog
--- verbiste-0.1.42/debian/changelog	2015-11-01 11:17:31.0 -0800
+++ verbiste-0.1.42/debian/changelog	2016-03-01 23:47:38.0 -0800
@@ -1,3 +1,10 @@
+verbiste (0.1.42-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due to failing test (Closes: #815742)
+
+ -- Raúl Benencia   Tue, 01 Mar 2016 23:43:03 -0800
+
 verbiste (0.1.42-2) unstable; urgency=medium
 
   * Fix missing dependency (Closes: #803682)
diff -Nru verbiste-0.1.42/debian/control verbiste-0.1.42/debian/control
--- verbiste-0.1.42/debian/control	2015-11-01 11:17:31.0 -0800
+++ verbiste-0.1.42/debian/control	2016-03-01 23:18:39.0 -0800
@@ -7,6 +7,7 @@
libgnomeui-dev,
libmate-panel-applet-dev,
libxml-parser-perl,
+   locales,
pkg-config
 Standards-Version: 3.9.6
 Homepage: http://sarrazip.com/dev/verbiste.html
diff -Nru verbiste-0.1.42/debian/rules verbiste-0.1.42/debian/rules
--- verbiste-0.1.42/debian/rules	2015-11-01 11:17:31.0 -0800
+++ verbiste-0.1.42/debian/rules	2016-03-01 23:47:52.0 -0800
@@ -9,5 +9,13 @@
 override_dh_installdocs:
 	dh_installdocs -A README LISEZMOI HACKING
 
+override_dh_auto_test:
+	mkdir -p debian/tmp/locale/
+	localedef -f UTF-8 -i en_US ./debian/tmp/locale/en_US.UTF-8/
+	LOCPATH=$(CURDIR)/debian/tmp/locale/ \
+	LANG=en_US.UTF-8 \
+	LC_ALL=en_US.UTF-8 \
+	dh_auto_test
+
 %:
 	dh $@ --parallel --with autoreconf


signature.asc
Description: PGP signature

Processed: verbiste: diff for NMU version 0.1.42-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 815742 + patch
Bug #815742 [src:verbiste] verbiste: FTBFS: lt-french-deconjugator: 
unrecognized option '--unknown'
Added tag(s) patch.
> tags 815742 + pending
Bug #815742 [src:verbiste] verbiste: FTBFS: lt-french-deconjugator: 
unrecognized option '--unknown'
Added tag(s) pending.

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

Bug#815798: (no subject)

[Gaetano Guerriero]

tag 815798 - unreproducible
tag 815798 + patch

Reproducible in my system.

su postgres -c 'psql gitlab_production -c \\d' was outputting "No relations
found." in localized format (I have LANG=it_IT.UTF-8), breaking the test and
skipping database setup.

Forcing LANG=C in psql execution fixed in my case.


--- a/debian/rake-tasks.sh
+++ b/debian/rake-tasks.sh
@@ -18,7 +18,7 @@
   }
 fi
 echo "Initializing database..."
-if [ "$(su postgres -c 'psql gitlab_production -c \\d')" = \
+if [ "$(su postgres -c 'LANG=C psql gitlab_production -c \\d')" = \
 "No relations found." ]; then
   su ${gitlab_user} -s /bin/sh -c 'bundle exec rake gitlab:setup \
   RAILS_ENV=production force=yes'

Processed: bug 816527 is forwarded to https://github.com/theory/test-file-contents/issues/2

[Debian Bug Tracking System]

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

> forwarded 816527 https://github.com/theory/test-file-contents/issues/2
Bug #816527 [src:libtest-file-contents-perl] libtest-file-contents-perl: FTBFS 
with Text::Diff 1.44
Set Bug forwarded-to-address to 
'https://github.com/theory/test-file-contents/issues/2'.
> thanks
Stopping processing here.

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

Bug#816527: libtest-file-contents-perl: FTBFS with Text::Diff 1.44

[gregor herrmann]

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-

Processed: tagging 816248, bug 816248 is forwarded to https://github.com/squizlabs/PHP_CodeSniffer/pull/906

[Debian Bug Tracking System]

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

> tags 816248 + upstream
Bug #816248 [php-codesniffer] php-codesniffer: add dependency on split php-xml 
package
Added tag(s) upstream.
> forwarded 816248 https://github.com/squizlabs/PHP_CodeSniffer/pull/906
Bug #816248 [php-codesniffer] php-codesniffer: add dependency on split php-xml 
package
Set Bug forwarded-to-address to 
'https://github.com/squizlabs/PHP_CodeSniffer/pull/906'.
> thanks
Stopping processing here.

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

Bug#815864: (no subject)

[Barry Warsaw]

Attached is the patch that fixes this problem; it has already been forwarded
to Matthias.  The potentially controversial bit is the new dependency on
virtualenv, which is required to pick up the pip wheel.  Alternatively, we
could split python-virtualenv into a separate -support binary package, but
that of course would have to go through NEW.
diff --git a/debian/changelog b/debian/changelog
index 469d204..27eead3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+python3.5 (3.5.1-6ubuntu3~test0) UNRELEASED; urgency=medium
+
+  * d/patches/ensurepip-disabled.diff: Provide more debugging when the
+ensurepip command fails.
+  * d/patches/ensurepip-wheels.diff: Update for compatibility with latest
+python-pip packages.
+  * d/control.in: Add virtualenv to Depends of pythonX.Y-venv.
+
+ -- Barry Warsaw   Mon, 29 Feb 2016 16:45:06 -0500
+
 python3.5 (3.5.1-6ubuntu2) xenial; urgency=medium
 
   * python3.5-venv: Drop the dependency on python-pip-whl, depend on
diff --git a/debian/control.in b/debian/control.in
index 3999830..bb5ac65 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -38,7 +38,7 @@ Architecture: any
 Multi-Arch: allowed
 Priority: @PRIO@
 Depends: @PVER@ (= ${binary:Version}),
- python-pip-whl (>= 8.0.2-7), ${shlibs:Depends}, ${misc:Depends}
+ python-pip-whl (>= 8.0.2-7), virtualenv, ${shlibs:Depends}, ${misc:Depends}
 Breaks: python3-pip (<< 1.5.6-4)
 Description: Interactive high-level object-oriented language (pyvenv binary, version @VER@)
  Python is a high-level, interactive, object-oriented language. Its @VER@ version
diff --git a/debian/patches/ensurepip-disabled.diff b/debian/patches/ensurepip-disabled.diff
index 7fbc575..1226e2e 100644
--- a/debian/patches/ensurepip-disabled.diff
+++ b/debian/patches/ensurepip-disabled.diff
@@ -1,10 +1,8 @@
 # DP: Disable ensurepip for the system installation, only enable it for virtual environments.
 
-Index: b/Lib/ensurepip/__init__.py
-===
 --- a/Lib/ensurepip/__init__.py
 +++ b/Lib/ensurepip/__init__.py
-@@ -8,6 +8,34 @@ import tempfile
+@@ -8,6 +8,34 @@
  
  __all__ = ["version", "bootstrap"]
  
@@ -39,7 +37,7 @@ Index: b/Lib/ensurepip/__init__.py
  
  # pip currently requires ssl support, so we try to provide a nicer
  # error message when that is missing (http://bugs.python.org/issue19744)
-@@ -68,6 +96,11 @@ def bootstrap(*, root=None, upgrade=Fals
+@@ -68,6 +96,11 @@
  
  Note that calling this function will alter both sys.path and os.environ.
  """
@@ -51,11 +49,9 @@ Index: b/Lib/ensurepip/__init__.py
  if altinstall and default_pip:
  raise ValueError("Cannot use altinstall and default_pip together")
  
-Index: b/Lib/venv/__init__.py
-===
 --- a/Lib/venv/__init__.py
 +++ b/Lib/venv/__init__.py
-@@ -254,7 +254,24 @@ class EnvBuilder:
+@@ -252,7 +252,28 @@
  # intended for the global Python environment
  cmd = [context.env_exe, '-Im', 'ensurepip', '--upgrade',
  '--default-pip']
@@ -65,7 +61,9 @@ Index: b/Lib/venv/__init__.py
 +# following command will produce an unhelpful error.  Let's make it
 +# more user friendly.
 +try:
-+subprocess.check_output(cmd, stderr=subprocess.STDOUT)
++subprocess.check_output(
++cmd, stderr=subprocess.STDOUT,
++universal_newlines=True)
 +except subprocess.CalledProcessError:
 +print("""\
 +The virtual environment was not created successfully because ensurepip is not
@@ -76,7 +74,9 @@ Index: b/Lib/venv/__init__.py
 +
 +You may need to use sudo with that command.  After installing the python3-venv
 +package, recreate your virtual environment.
-+""")
++
++Failing command: {}
++""".format(cmd))
 +sys.exit(1)
  
  def setup_scripts(self, context):
diff --git a/debian/patches/ensurepip-wheels.diff b/debian/patches/ensurepip-wheels.diff
index 930e013..aae0dac 100644
--- a/debian/patches/ensurepip-wheels.diff
+++ b/debian/patches/ensurepip-wheels.diff
@@ -1,5 +1,3 @@
-Index: b/Lib/ensurepip/__init__.py
-===
 --- a/Lib/ensurepip/__init__.py
 +++ b/Lib/ensurepip/__init__.py
 @@ -1,3 +1,4 @@
@@ -7,7 +5,7 @@ Index: b/Lib/ensurepip/__init__.py
  import os
  import os.path
  import pkgutil
-@@ -8,13 +9,9 @@ import tempfile
+@@ -8,13 +9,9 @@
  __all__ = ["version", "bootstrap"]
  
  
@@ -22,7 +20,7 @@ Index: b/Lib/ensurepip/__init__.py
  try:
  import ssl
  except ImportError:
-@@ -26,8 +23,8 @@ else:
+@@ -26,8 +23,9 @@
  pass
  
  _PROJECTS = [
@@ -30,10 +28,11 @@ Index: b/Lib/ensurepip/__init__.py
 -("pip", _PIP_VERSION),
 +"setuptools",
 +"pip",
++"pkg_resources",
  ]
  
  
-@@ -45,7 +42,10 @@ def version():
+@@ -45,7 +43,10 @@
  """
  Returns a 

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 815864 python3.5
Bug #815864 [python3-venv] python3-venv: unable to create a virtual environment
Bug reassigned from package 'python3-venv' to 'python3.5'.
No longer marked as found in versions python3-defaults/3.5.1-2.
Ignoring request to alter fixed versions of bug #815864 to the same values 
previously set
>
End of message, stopping processing here.

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

Processed: Re: [m...@debian.org] Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #812668 [mailfilter] mailfilter: FTBFS - error: no match for 'operator='
Added tag(s) patch.

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

Bug#816517: boxbackup: FTBFS: TEST FAILURE: Condition [::system("perl testfiles/testrequests.pl") == 0]

[Chris Lamb]

Source: boxbackup
Version: 0.11.1~r2837-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,

boxbackup fails to build from source in unstable/amd64:

  [..]

  Waiting for bbackupd to try to access the store:  done.
  .Starting server: ../../bin/bbackupd/bbackupd  
testfiles/bbackupd-snapshot.conf
  Waiting for server to start:  done.
  Waiting for just before bbackupd recovers: 
...
 done.
  Waiting for bbackupd to recover: .. done.
  .Starting server: ../../bin/bbackupd/bbackupd  testfiles/bbackupd.conf
  Waiting for server to start:  done.
  Waiting for just before bbackupd recovers: 

 done.
  Waiting for bbackupd to recover: .. done.
  
   Replace symlink with directory, add new directory
  Waiting for bbackupd to sync the changes:  done.
  
   Replace directory with symlink
  Waiting for bbackupd to sync the changes:  done.
  
   Replace symlink with directory (which was a symlink)
  Waiting for bbackupd to sync the changes:  done.
  
   Put it all back to how it was
  Waiting for bbackupd to sync the changes:  done.
  
   Rename over existing untracked file
  Waiting for untracked files to be old enough: . done.
  Waiting for bbackupd to sync the untracked files:  done.
  Waiting for bbackupd to sync the untracked files again:  done.
  
   Rename over existing tracked file
  Waiting for tracked files to be old enough: . done.
  Waiting for bbackupd to sync the tracked files again:  done.
  
   Rename an existing file over a deleted file
  Waiting for bbackupd to sync:  done.
  
   Add files with old times, update attributes of one to latest time
  Waiting for bbackupd to sync old files:  done.
  
   Modify existing file, but change timestamp to rather old
  
   Add files and dirs for exclusion test
  
   Check that exclude/alwaysinclude commands actually work
  
   Add unreadable files
  Waiting for bbackupd to try to sync unreadable file:  done.
  
   Continuously update file, check isn't uploaded
  
  READ: WARNING: Local file 'testfiles/TestDir1/continousupdate' exists, but 
remote file '/Test1/continousupdate' does not.
  
   Keep on continuously updating file, check it is uploaded eventually
  
  READ: WARNING: Local file 'testfiles/TestDir1/continousupdate' has different 
attributes to store file '/Test1/continousupdate'.
  READ: WARNING: Local file 'testfiles/TestDir1/continousupdate' has different 
contents to store file '/Test1/continousupdate'.
  
   Delete directory, change attributes
  Waiting for bbackupd to sync deletion of directory:  done.
  
   Restore files and directories
  
  ..
  
   Try to restore to a path that doesn't exist
  
   Add files with current time
  Waiting for bbackupd to sync new files:  done.
  
   Rename directory
  Waiting for bbackupd to sync renamed directory:  done.
  WARNING: Quick compare used -- file attributes are not checked.
  
   Rename files
  Waiting for bbackupd to sync renamed files:  done.
  
   Create a file with timestamp way ahead in the future
  Waiting for bbackup to sync future file:  done.
  
   Change client store marker
  
   Check change of store marker pauses daemon
  Waiting for bbackupd to detect changed store marker: .. done.
  Waiting for bbackupd to recover: 
..
 done.
  
   Interrupted restore
  
   Interrupted restore
  
   Resume restore
  
  
   Check restore deleted files
  ..
  .Starting server: ../../bin/bbackupd/bbackupd  testfiles/bbackupd.conf
  Waiting for server to start:  done.
  Waiting for bbackupd to sync everything: .. done.
  .Waiting for server to die (pid 9855): . done.
  PASSED
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160302134814.WwW1qclgK1/boxbackup-0.11.1~r2837/test/httpserver'
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160302134814.WwW1qclgK1/boxbackup-0.11.1~r2837/lib/httpserver'
[CXX] HTTPQueryDecoder.cpp
[CXX] HTTPRequest.cpp
[CXX] HTTPResponse.cpp
[CXX] HTTPServer.cpp
[CXX] S3Client.cpp
[CXX] S3Simulator.cpp
[CXX] autogen_HTTPException.cpp
[CXX] cdecode.cpp
[CXX] cencode.cpp
[AR]  ../../debug/lib/httpserver/httpserver.a
[RANLIB]  

Bug#812638: gbirthday: diff for NMU version 0.6.10-0.1

[Gianfranco Costamagna]

Control: tags 812638 + patch
Control: tags 812638 + pending

Dear maintainer,

I've prepared an NMU for gbirthday (versioned as 0.6.10-0.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

The new upstream release just includes the debian patch, so I imported
it to simplify the packaging.

you can see attached the debdiff.

cheers,

Gianfranco
diff -Nru gbirthday-0.6.9/debian/changelog gbirthday-0.6.10/debian/changelog
--- gbirthday-0.6.9/debian/changelog2015-12-29 09:54:32.0 +0100
+++ gbirthday-0.6.10/debian/changelog   2016-03-02 15:11:55.0 +0100
@@ -1,3 +1,13 @@
+gbirthday (0.6.10-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Upload to unstable.
+  * New upstream release (Closes: #812638)
+  * Bump Standards-Version to 3.9.7: no changes needed.
+  * Drop patch remove-too-early-import: upstream
+
+ -- Gianfranco Costamagna   Wed, 02 Mar 2016 
15:09:20 +0100
+
 gbirthday (0.6.9-0.1) experimental; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gbirthday-0.6.9/debian/control gbirthday-0.6.10/debian/control
--- gbirthday-0.6.9/debian/control  2015-12-28 17:57:34.0 +0100
+++ gbirthday-0.6.10/debian/control 2016-03-02 15:09:58.0 +0100
@@ -10,7 +10,7 @@
python-gtk2,
python-nose
 X-Python-Version: >= 2.6
-Standards-Version: 3.9.6
+Standards-Version: 3.9.7
 Homepage: http://gbirthday.sf.net/
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/gbirthday.git
 Vcs-Git: git://anonscm.debian.org/collab-maint/gbirthday.git
diff -Nru gbirthday-0.6.9/debian/patches/remove-too-early-import 
gbirthday-0.6.10/debian/patches/remove-too-early-import
--- gbirthday-0.6.9/debian/patches/remove-too-early-import  2015-12-28 
18:17:45.0 +0100
+++ gbirthday-0.6.10/debian/patches/remove-too-early-import 1970-01-01 
01:00:00.0 +0100
@@ -1,14 +0,0 @@
-Description: remove this duplicated import, which is done too early and 
outside of the try/except block
-Author: Mattia Rizzolo 
-Forwarded: yes, to Jérôme 
-Last-Update: 2015-12-28
-
 a/src/gb
-+++ b/src/gb
-@@ -1,6 +1,5 @@
- #!/usr/bin/python
- '''import main function from gbirthday and execute it'''
--from gbirthday import main
- try:
- from gbirthday import main
- except ImportError:
diff -Nru gbirthday-0.6.9/debian/patches/series 
gbirthday-0.6.10/debian/patches/series
--- gbirthday-0.6.9/debian/patches/series   2015-12-28 18:21:46.0 
+0100
+++ gbirthday-0.6.10/debian/patches/series  2016-03-02 15:10:49.0 
+0100
@@ -1,2 +1 @@
 01_deactivate-nosetests.patch
-remove-too-early-import
diff -Nru gbirthday-0.6.9/Changelog gbirthday-0.6.10/Changelog
--- gbirthday-0.6.9/Changelog	2015-12-16 23:15:07.0 +0100
+++ gbirthday-0.6.10/Changelog	2015-12-29 12:42:42.0 +0100
@@ -1,3 +1,7 @@
+0.6.10
+
+- Fix to minor fix in last release...
+
 0.6.9
 
 - Minor fixes related to installation
diff -Nru gbirthday-0.6.9/debian/changelog gbirthday-0.6.10/debian/changelog
--- gbirthday-0.6.9/debian/changelog	2015-12-29 09:54:32.0 +0100
+++ gbirthday-0.6.10/debian/changelog	2016-03-02 15:11:55.0 +0100
@@ -1,3 +1,13 @@
+gbirthday (0.6.10-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Upload to unstable.
+  * New upstream release (Closes: #812638)
+  * Bump Standards-Version to 3.9.7: no changes needed.
+  * Drop patch remove-too-early-import: upstream
+
+ -- Gianfranco Costamagna   Wed, 02 Mar 2016 15:09:20 +0100
+
 gbirthday (0.6.9-0.1) experimental; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gbirthday-0.6.9/debian/control gbirthday-0.6.10/debian/control
--- gbirthday-0.6.9/debian/control	2015-12-28 17:57:34.0 +0100
+++ gbirthday-0.6.10/debian/control	2016-03-02 15:09:58.0 +0100
@@ -10,7 +10,7 @@
python-gtk2,
python-nose
 X-Python-Version: >= 2.6
-Standards-Version: 3.9.6
+Standards-Version: 3.9.7
 Homepage: http://gbirthday.sf.net/
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/gbirthday.git
 Vcs-Git: git://anonscm.debian.org/collab-maint/gbirthday.git
diff -Nru gbirthday-0.6.9/debian/patches/remove-too-early-import gbirthday-0.6.10/debian/patches/remove-too-early-import
--- gbirthday-0.6.9/debian/patches/remove-too-early-import	2015-12-28 18:17:45.0 +0100
+++ gbirthday-0.6.10/debian/patches/remove-too-early-import	1970-01-01 01:00:00.0 +0100
@@ -1,14 +0,0 @@
-Description: remove this duplicated import, which is done too early and outside of the try/except block
-Author: Mattia Rizzolo 
-Forwarded: yes, to Jérôme 
-Last-Update: 2015-12-28
-
 a/src/gb
-+++ b/src/gb
-@@ -1,6 +1,5 @@
- #!/usr/bin/python
- '''import main function from gbirthday and execute it'''
--from gbirthday import main
- try:
- from gbirthday import 

Bug#816518: gitmagic: FTBFS: LaTeX Error: File `ulem.sty' not found.

[Chris Lamb]

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

Processed: gbirthday: diff for NMU version 0.6.10-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 812638 + patch
Bug #812638 [gbirthday] gbirthday: FTBFS - build-depends on non-existent 
package python-support
Added tag(s) patch.
> tags 812638 + pending
Bug #812638 [gbirthday] gbirthday: FTBFS - build-depends on non-existent 
package python-support
Added tag(s) pending.

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

Bug#812668: [m...@debian.org] Bug#812668: mailfilter: FTBFS - error: no match for 'operator='

[Elimar Riesebieter]

Control: tags -1 patch

* Andreas Bauer  [2016-02-29 16:52 +0100]:

> Hi Elimar, Michael,
> 
> just letting you know that in SVN is a release candidate of 0.8.4 of
> mailfilter, which hopefully fixes the issue.  It's a bit ugly, hence I
> want to keep testing it for a while, before I release - say, 1 or 2
> weeks.
> 
> Hope it will still be able to keep the package in Debian this way.  If
> either of you is curious, you could grab it from SVN and rebuild, etc.
> 
>   https://sourceforge.net/p/mailfilter/code/HEAD/tree/

I have cherry picked the respective patch and can confirm that
mailfilter builds fine on i386, ppc32 and amd64. I've build my own
package with the patch attached for testing.

Thanks Andreas for contribution ;-)

Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)
Author: Andreas Bauer 
Subject: Fix compilation issues stemming from flex >= 2.6.0, which no longer
 uses pointers for yyin, but references it seems.
Last-Update: 2016-03-02
Index: mailfilter-0.8.3/ChangeLog
===
--- mailfilter-0.8.3.orig/ChangeLog
+++ mailfilter-0.8.3/ChangeLog
@@ -1,6 +1,13 @@
 Mailfilter ChangeLog
 -=-=-=-=-=-=-=-=-=-=
 
+Mon Feb 29 16:44:08 CET 2016 baueran
+
+- src/rcfile.ll: yyin is now a reference. So use different ifstream
+ pointer and pass it on.
+- src/pop3.cc: FlexLexer::switch_stream no longer has 2nd argument
+   optional, it seems.  So pass NULL as second object.
+
 Sat May 17 19:21:57 CEST 2014 baueran
 
  src/preferences.cc:
Index: mailfilter-0.8.3/configure.ac
===
--- mailfilter-0.8.3.orig/configure.ac
+++ mailfilter-0.8.3/configure.ac
@@ -26,7 +26,7 @@
 # Process this file with autoconf to produce a configure script.
 
 AC_PREREQ(2.54)
-AC_INIT(mailfilter, 0.8.3, [baue...@gmail.com])
+AC_INIT(mailfilter, 0.8.4, [baue...@gmail.com])
 AC_REVISION($Revision: 1.1.2.4.2.12 $)
 AC_SUBST(PACKAGE_COPYRIGHT)
 AC_DEFINE(PACKAGE_COPYRIGHT,
Index: mailfilter-0.8.3/NEWS
===
--- mailfilter-0.8.3.orig/NEWS
+++ mailfilter-0.8.3/NEWS
@@ -1,6 +1,13 @@
 Mailfilter NEWS (Summary)
 -=-=-=-=-=-=-=-=-=-=-=-=-
 
+mailfilter 0.8.4 (under development)
+
+  - Fix compilation issues stemming from flex >= 2.6.0, which no
+longer uses pointers for yyin, but references it seems.
+
+  - Minor other code fixes that relate to the above.
+
 mailfilter 0.8.3 (Sat May 17 19:37:27 CEST 2014)
 
   - (Hopefully) fixed Debian Bug #716522: mailfilter crashes
Index: mailfilter-0.8.3/src/pop3.cc
===
--- mailfilter-0.8.3.orig/src/pop3.cc
+++ mailfilter-0.8.3/src/pop3.cc
@@ -204,7 +204,7 @@ int POP3 :: invoke_msg_parser (const str
 	  stringstream cur_header;
 	  cur_header << *header;
 	  rfclexer = new rfcFlexLexer;
-	  rfclexer->switch_streams (_header);
+	  rfclexer->switch_streams (_header, NULL);
 	  int error = rfcparse ((void*) msg_header);
 	  delete rfclexer;
 	  return error;
Index: mailfilter-0.8.3/src/rcfile.ll
===
--- mailfilter-0.8.3.orig/src/rcfile.ll
+++ mailfilter-0.8.3/src/rcfile.ll
@@ -146,17 +146,21 @@ CTRL_CHAR	.
 	   cerr << yytext << "' could not be found." << endl;
 	   exit (-1);
 }
+
+	// yyin is now a std::istream& it seems. So the following no longer works:
+	// yyin = new ifstream (sub_file.c_str ());
+	std::ifstream* infile = new ifstream (sub_file.c_str ());
 
-yyin = new ifstream (sub_file.c_str ());
-
-if (!((ifstream*) yyin)->is_open ())
+	// if (!((std::ifstream*) yyin)->is_open ())
+if (!infile->is_open ())
 {
cerr << PACKAGE_NAME << ": Error: Nested rcfile '";
 	   cerr << sub_file << "' could not be opened." << endl;
 	   exit (-1);
 }
 
-yy_switch_to_buffer (yy_create_buffer (yyin, YY_BUF_SIZE));
+yy_switch_to_buffer (yy_create_buffer (infile, YY_BUF_SIZE));
+	// yy_switch_to_buffer (yy_create_buffer (yyin, YY_BUF_SIZE));
  }
  catch (...)
  {


signature.asc
Description: PGP signature

Bug#799433: Solution: comment out line 1 in /etc/mysql/debian.cnf

[Moritz Strohm]

Package: mysql-server-5.5
Version: 5.5.46-0+deb8u1
Followup-For: Bug #799433


Hello


I had the same problem: After installing mysql-server-5.5 via apt-get, the 
MySQL start script failed to load and it took it a while to figure out that it 
can't start MySQL. MySQL was already running and therefore a second MySQL 
service couldn't be started.

After killing the running MySQL service I did the same steps as Janusz: 
Commenting out the mentioned part in 
/var/lib/dpkg/info/mysql-server-5.5.postinst and calling update-rc.d and 
invoke-rc.d manually. update-rc.d worked but invoke-rc.d failed:

invoke-rc.d mysql start
[FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . 
. . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.


But a mysql service was running after invocation of invoke-rc.d. The syslog 
(/var/log/syslog) told me where the problem was:

Mar  2 14:46:43 Cubietruck /etc/init.d/mysql[13977]: 1 processes alive and 
'/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Mar  2 14:46:43 Cubietruck /etc/init.d/mysql[13977]: error: Found option 
without preceding group in config file: /etc/mysql/debian.cnf at line: 1
Mar  2 14:46:43 Cubietruck /etc/init.d/mysql[13977]: Fatal error in defaults 
handling. Program aborted


The first two lines of /etc/mysql/debian.cnf:

/bin/grep: /etc/mysql/debian.cnf: No such file or directory
# Automatically generated for Debian scripts. DO NOT TOUCH!


By commenting out the first line the problem was solved, MySQL runs fine since 
then:

invoke-rc.d mysql start
[ ok ] Starting MySQL database server: mysqld . ..
[info] Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly..


In conclusion, I think something in the automatic generation of 
/etc/mysql/debian.cnf went wrong and caused all this trouble.

Regards
Moritz Strohm



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.4.0 (SMP w/2 CPU cores)
Locale: LANG=nb_NO.utf8, LC_CTYPE=nb_NO.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mysql-server-5.5 depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  initscripts2.88dsf-59
ii  libc6  2.19-18+deb8u1
ii  libdbi-perl1.631-3+b1
ii  libgcc11:4.9.2-10
ii  libstdc++6 4.9.2-10
ii  lsb-base   4.1+Debian13+nmu1
ii  mysql-client-5.5   5.5.46-0+deb8u1
ii  mysql-common   5.5.46-0+deb8u1
ii  mysql-server-core-5.5  5.5.46-0+deb8u1
ii  passwd 1:4.2-3
ii  perl   5.20.2-3+deb8u1
ii  psmisc 22.21-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages mysql-server-5.5 recommends:
ii  libhtml-template-perl  2.95-1

Versions of packages mysql-server-5.5 suggests:
pn  mailx   
pn  tinyca  

-- debconf information excluded

Bug#800029: marked as done (ruby-em-synchrony: FTBFS: EventMachine::Protocols::Redis should yield until connection is ready)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 13:30:09 +
with message-id 
and subject line Bug#800029: fixed in ruby-em-synchrony 1.0.4-1
has caused the Debian Bug report #800029,
regarding ruby-em-synchrony: FTBFS: EventMachine::Protocols::Redis should yield 
until connection is ready
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.)


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

  [..]
  
  Failed examples:
  
  rspec ./spec/redis_spec.rb:5 # EventMachine::Protocols::Redis should
  yield until connection is ready
  rspec ./spec/remcached_spec.rb:6 # Memcached should yield until
  connection is ready
  rspec ./spec/remcached_spec.rb:30 # Memcached should fire multi
  memcached requests
  
  /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-em-synchrony-1.0.3/debian/ruby-em-synchrony returned
  exit code 1
  debian/rules:19: recipe for target 'override_dh_auto_install' failed

  [..]

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


https://reproducible.debian.net/logs/unstable/amd64/ruby-em-synchrony_1.0.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: Fri Sep  4 07:02:47 GMT+12 2015
I: pbuilder-time-stamp: 1441393367
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.5~), ruby-rspec, 
ruby-em-hiredis, ruby-activerecord, ruby-mysql2, ruby-em-http-request (>= 
1.1.2-2), ruby-remcached, ruby-mongo, ruby-amqp, ruby-amq-protocol, 
ruby-eventmachine, ruby-em-mongo, redis-server, memcached, mysql-server, 
ruby-em-redis, procps
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20262 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.5~); 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-em-hiredis; however:
  Package ruby-em-hiredis is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-activerecord; however:
  Package ruby-activerecord is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-mysql2; however:
  Package ruby-mysql2 is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-em-http-request (>= 1.1.2-2); 
however:
  Package ruby-em-http-request is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-remcached; however:
  Package ruby-remcached is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-mongo; however:
  Package ruby-mongo is not installed.
 pbuilder-satisfydepends-dummy depends on
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...

Bug#816050: evolution bug fixed?

[Andreas Henriksson]

Hello Sam Morris!

Please check if you can still reproduce the problem you reported
in the just uploaded 3.18.5.1-1 version and report back!

Regards,
Andreas Henriksson

Bug#815908: marked as done (ruby-github-linguist: FTBFS: install: cannot stat '[..]/ruby-github-linguist-4.7.2/bin/linguist': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 12:37:21 +
with message-id 
and subject line Bug#815908: fixed in ruby-github-linguist 4.7.2-2
has caused the Debian Bug report #815908,
regarding ruby-github-linguist: FTBFS:   install: cannot stat 
'[..]/ruby-github-linguist-4.7.2/bin/linguist': No such file or directory
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.)


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

  [..]


 dh_auto_install -O--buildsystem=ruby
dh_ruby --install 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist
 dh_ruby --install
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Install files 
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  install -d 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist/usr/bin
  install -D -m755 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/bin/linguist
 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist/usr/bin/linguist
  install: cannot stat 
'/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/bin/linguist':
 No such file or directory
  /usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': install -D -m755 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/bin/linguist
 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist/usr/bin/linguist
 (Gem2Deb::CommandFailed)
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:172:in `block in 
install_files'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:169:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:169:in 
`install_files'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:30:in 
`install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `block in 
install'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `install'
from /usr/bin/dh_ruby:94:in `'
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160225150719.LlpPnpiK8v/ruby-github-linguist-4.7.2/debian/ruby-github-linguist
 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-github-linguist.4.7.2-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-github-linguist
Source-Version: 4.7.2-2

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

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated 
ruby-github-linguist 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: Wed, 02 Mar 2016 10:07:58 +0530
Source: ruby-github-linguist
Binary: ruby-github-linguist
Architecture: source all
Version: 

Bug#816507: kodi: Wait for PVR addon updates with the migration to testing

[Balint Reczey]

Package: kodi
Version: 16.0+dfsg1-1
Severity: serious

Hi,

This bug is for preventing the migration of kodi to testing before PVR
addons are also ready.

Cheers,
Balint

Bug#805674: marked as done (ohcount: FTBFS: cp: cannot stat 'ruby/gestalt': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 12:22:20 +
with message-id 
and subject line Bug#805674: fixed in ohcount 3.0.0-8.1
has caused the Debian Bug report #805674,
regarding ohcount: FTBFS: cp: cannot stat 'ruby/gestalt': No such file or 
directory
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.)


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

dh_install --buildsystem=ruby --with ruby
install -d debian/ohcount/usr/lib/ruby/vendor_ruby/ohcount
install -d debian/ohcount/usr/bin
install -d debian/ohcount-doc/usr/share/doc/ohcount-doc
cp bin/ohcount debian/ohcount/usr/bin/
cp -R ruby/gestalt ruby/gestalt.rb ruby/ohcount.rb 
debian/ohcount/usr/lib/ruby/vendor_ruby/ohcount/
cp: cannot stat ‘ruby/gestalt’: No such file or directory
cp: cannot stat ‘ruby/gestalt.rb’: No such file or directory
cp: cannot stat ‘ruby/ohcount.rb’: No such file or directory
debian/rules:12: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/ohcount-3.0.0'

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

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

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

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated ohcount package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Mar 2016 22:02:31 +0100
Source: ohcount
Binary: ohcount ohcount-doc
Architecture: source
Version: 3.0.0-8.1
Distribution: unstable
Urgency: medium
Maintainer: Sylvestre Ledru 
Changed-By: Christian Hofstaedtler 
Description:
 ohcount- Source code line counter
 ohcount-doc - Source code line counter - Documentation
Closes: 805674
Changes:
 ohcount (3.0.0-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build system being broken by removal of deprecated "Config"
 object in Ruby 2.2. (Closes: #805674)
Checksums-Sha1:
 0891ef8e97c36d2a99262a331a33eeb27ae24706 1977 ohcount_3.0.0-8.1.dsc
 b3d9dc6069094af5bcf271afb80de89732d47f24 7348 ohcount_3.0.0-8.1.debian.tar.xz
Checksums-Sha256:
 b0a0557ac928c7456be671c25223d33d0f632e446c60431b67f3a2464d6e714b 1977 
ohcount_3.0.0-8.1.dsc
 fec47412c9ae4e619c4eebf148eacc2349eb58e5b53b9a3a40ec972bb8637fcd 7348 
ohcount_3.0.0-8.1.debian.tar.xz
Files:
 80461eaea9783a9cd72be6837c1aa7cf 1977 utils optional ohcount_3.0.0-8.1.dsc
 ab30b02e59b202ae6bed42320fdbed90 7348 utils optional 
ohcount_3.0.0-8.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW1gULAAoJEFwT1tuTBS4DhkAP/0lrJivJyIfD6cMUQ4Qd9sqY
6vUeUutk80d+cDiCOEEEkFjwSUUYDC0AoOlVp0UaPJ3xb3ekUOQR907vf/YAmkiw
k89MEsidrFTC5Bss28HFIunBbzFOAXWaCyWJYSXy9fPoxP9dYlzV0fLcmzsp+Tzo
Qa0tEJ0P7lwv0ueUHqdNshG2sGtSjGnbQXTiq50e/bNHmAyZt9UJiEGEutEeb/Sv
kRXroamdUgnhDGr8kstSYgyWcnsGMmPGh0OK2x8GH/kp3W8GC5SjyR5FOQ894hGU
auKpC1EabowJD7oR+5EeMmxKDKQbraumuhEwiBGtWNbMEBYyvpNTm0NWkJbWHVFq
eV/QNyG+Cym3yYzhGrzrFdcMYLVtHb0YgPUXY6q9KmZruFBO2QETiGPhhS4i1m7/
csjgQHnPVqIqY7t+cZ3oAEiD2lrpQrKvVPiH7lMi2fFllSL21cARD376MShS1zp8
IjYKiXYPY2+8suEdowN95saLwp977mO2OHYZoURdTuWr/gInNBuT1Mszax/w+otg
GO6yXFyQFSEXDcUR/m7dYwQ1o2iUMZUr0BT8PhwMUCMrer67B+/DX1gEIb8DM4Se
cbi+V73F9TXSpcdL0w7eSdpqYqPf61RjZsK6uRnazgH7uQq+kezpfs3KrGEEbIGI
9D9bjOaMa3fBzEhXohFi
=giqm
-END PGP SIGNATURE End Message ---

Bug#816257: marked as done (trocla: FTBFS: Self-signed certificate /CN=test creation failed: wrong argument)

[Debian Bug Tracking System]

Your message dated Wed, 2 Mar 2016 12:46:53 +0100
with message-id <20160302114653.gb22...@percival.namespace.at>
and subject line Re: #816257: trocla: FTBFS: Self-signed certificate
has caused the Debian Bug report #816257,
regarding trocla: FTBFS: Self-signed certificate /CN=test creation failed: 
wrong argument
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.)


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

trocla fails to build from source in unstable/amd64:

  [..]

  Failures:
  
1) Trocla password x509 password format should return a password hashed in 
the x509 format
   Failure/Error: 
@trocla.password('some_test',format,format_options[format]).should_not be_empty
   RuntimeError:
 Self-signed certificate /CN=test creation failed: wrong argument 
(OpenSSL::X509::Certificate)! (Expected kind of OpenSSL::X509::Name)
   # ./lib/trocla/formats/x509.rb:66:in `rescue in format'
   # ./lib/trocla/formats/x509.rb:61:in `format'
   # ./lib/trocla.rb:31:in `password'
   # ./spec/trocla_spec.rb:22:in `block (5 levels) in '
  
2) Trocla password x509 password format should return the same hashed for 
the x509 format on multiple invocations
   Failure/Error: 
(round1=@trocla.password('some_test',format,format_options[format])).should_not 
be_empty
   RuntimeError:
 Self-signed certificate /CN=test creation failed: wrong argument 
(OpenSSL::X509::Certificate)! (Expected kind of OpenSSL::X509::Name)
   # ./lib/trocla/formats/x509.rb:66:in `rescue in format'
   # ./lib/trocla/formats/x509.rb:61:in `format'
   # ./lib/trocla.rb:31:in `password'
   # ./spec/trocla_spec.rb:26:in `block (5 levels) in '
  
  Deprecation Warnings:
  
  Using `should` from rspec-expectations' old `:should` syntax without 
explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
:should }` instead. Called from 
/home/lamby/temp/cdt.20160229080919.Psq5c9dxod/trocla-0.1.2/spec/trocla/encryptions/ssl_spec.rb:24:in
 `block (3 levels) in '.
  
  
  If you need more of the backtrace for any of these deprecations to
  identify where to make the necessary changes, you can configure
  `config.raise_errors_for_deprecations!`, and it will turn the
  deprecation warnings into errors, giving you the full backtrace.
  
  1 deprecation warning total
  
  Finished in 1.24 seconds (files took 0.12851 seconds to load)
  63 examples, 2 failures
  
  Failed examples:
  
  rspec './spec/trocla_spec.rb[1:1:10:1]' # Trocla password x509 password 
format should return a password hashed in the x509 format
  rspec './spec/trocla_spec.rb[1:1:10:2]' # Trocla password x509 password 
format should return the same hashed for the x509 format on multiple invocations
  
  /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.20160229080919.Psq5c9dxod/trocla-0.1.2/debian/trocla 
returned exit code 1
  debian/rules:21: recipe for target 'override_dh_auto_install' failed
  make[1]: *** [override_dh_auto_install] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160229080919.Psq5c9dxod/trocla-0.1.2'
  debian/rules:18: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


trocla.0.1.2-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Control: fixed trocla/0.2.3-1

Thanks for submitting this report; I believe it's fixed in the new
trocla 0.2.3-1 upload. (And I forgot to add this bug to the
changelog.)

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

Bug#805674: ohcount: diff for NMU version 3.0.0-8.1

[Christian Hofstaedtler]

* Sylvestre Ledru  [160302 09:09]:
> Excellent, thanks! 
> No need to wait,  please upload it now :) 

Alright, rescheduled to 0-day.

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

Bug#816395: autopkgtest: build fails in OBS due to adt-run tests needing apt-get

[Antonio Terceiro]

Control: severity -1 normal

Hello Bob, thanks for your bug report.

On Tue, Mar 01, 2016 at 02:27:48PM +, Bob Ham wrote:
> Package: autopkgtest
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)

Sorry, this is not how it works. Debian packages are supposed to build
correctly on Debian. The fact that they build correctly elsewhere is a
nice to have, but a failing build on OBS is not by any means a serious
bug as far as Debian is concerned.

I am downgrading this bug report severity, what does _not_ mean we don't
want to fix it, just that it is not a blocker for a Debian release.

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature

Processed: Re: Bug#816395: autopkgtest: build fails in OBS due to adt-run tests needing apt-get

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #816395 {Done: Martin Pitt } [autopkgtest] autopkgtest: 
build fails in OBS due to adt-run tests needing apt-get
Severity set to 'normal' from 'serious'

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

Bug#814589: otrs2: source-less files; undocumented copyrights/licenses; abuse of lintian-overrides; systematic DFSG violations

[Patrick Matthäi]

Am 15.02.2016 um 14:14 schrieb Dmitry Smirnov:

I am aware of those issues, that is
also why the embedded-code-copies bug is marked as "need help".

And this is why I provided some hints how you can address those problems in
my bug report. This is why I wrote to you after when I stabilised "ckeditor"
so you could use it.
I can use it, until ckeditor OR otrs upstreams broke it again, like with 
jquery.

Also it would prevent backports of otrs to jessie.


and mostly it is not possible to replace the
libjs thirdparty foo with the packages from Debian, mostly because of
version missmatches.

Hold on, you are answering the least important concern. There are cases when
replacing bundled library with system one could be fragile or not suitable.
But you can't ship and use untrusted pre-minified upstream files with who-
knows-what...


You reported a very general bug about the whole javascript mess. 
Replacing ckeditor will not solve the other problems or all those 
minified files and so on.






Nobody is willed (or in my case able) to fix those
JS issues, which appear here and then with different versions in
different places (ugly JS sh..).

At least I gave you "ckeditor" didn't I? That's one less problem to deal
with...


See above.




If everything is simple for you and just replacements have to be done
(which is not the case) then I would be happy to welcome you on the
otrs-packaging board.

It is simple enough. Although some system libraries should be safe to use you
do not have to use only system libraries. But you have to get rid of non-DFSG
precompiled binaries.
I appreciate your invitation but unfortunately I have no time for otrs.


IMO minified files are not as evil as the embedded libs, which should be 
addressed first.






Just a short example:
With 5.0.1-2 I had to drop (and inform the security team) about removing
again the use of the libjs-jquery* packages from Debian, because of #802938

I agree that using "libjs-jquery-ui" package of different version than
bundled one is fragile.
Though with "libjs-jquery" you'd probably be safe as long as you do not cross
1.9.0 boundary. However you must not use pre-minified "jquery-ui.js" as it is
shipped in orig.tar. As very minimum you have to replace it with original
uncompressed version that you have to ship in "debian/missing-sources" and
ideally report pre-built binaries as bug to upstream. If you believe in
minification then you can minify on build time. You can not trust source-
less, unreadable, unmodifiable pre-built binaries. I suppose lintian already
warned you long before I did.

I wrote the following wiki page that I use when I make upstream bug reports
about minified binaries -- I hope you might find it useful:

 https://wiki.debian.org/onlyjob/no-minification



Investing work in removing those files will not realy help and just 
burden the whole packaging and eat time to fix realy serious issues - 
like embedded libs.


@Debian release team:
I would like to request a strech ignore for this bug. I am aware of 
these problems, but I am not able to fix them nor did anyone ever 
offered me help with this JS foo. If it would not be possible I had to 
resign otrs packaging in Debian.


--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#816080: [wajig] Segfault on wajig show command for some packages.

[Manuel A. Fernandez Montecelo]

2016-03-02 5:43 GMT+00:00 Paweł Różański :
 Does the crash happen only for the "not installed" packages and it's
 fine for the "installed" ones?  If so, it's #815581, fix to be released
 tomorrow or so.
>>>
>>> So I'm going to assume that this is the case and will merge the reports
>>> now.
>>
>> Didn't test throughly, as I waited for new version, but quick check
>> confirms, that bug indeed appears only for not installed packages.
>
> Just upgraded aptitude to 0.7.7-1. Both aptitude and wajig work fine, so
> solved. :-)
>
> Thank you!

That's good, thanks for the confirmation!

-- 
Manuel A. Fernandez Montecelo 

Bug#816495: [pysatellites] Does not contain executable

[Giovanni Mascellani]

Package: pysatellites
Version: 2.3-2
Severity: serious

Hi.

$ dpkg -L pysatellites
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/pysatellites
/usr/share/doc/pysatellites/changelog.gz
/usr/share/doc/pysatellites/changelog.Debian.gz
/usr/share/doc/pysatellites/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/pysatellites.1.gz

(or, if you prefer,
https://packages.debian.org/sid/all/pysatellites/filelist)

There are no executables in the package! :-)

Probably just a missing install line.

Thanks, Giovanni.


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.4.0-trunk-amd64

Debian Release: stretch/sid
  500 unstablerepos.fds-team.de
  500 unstableftp.ch.debian.org
  500 stable  dl.google.com
  500 sid linux.dropbox.com
1 experimentalftp.ch.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Giovanni Mascellani 
PhD Student - Scuola Normale Superiore, Pisa, Italy

http://poisson.phc.unipi.it/~mascellani



signature.asc
Description: OpenPGP digital signature

Bug#816492: galera-3: Galera fails to build with pbuilder for armhf (on amd64)

[Ramil Valitov]

Package: galera-3
Version: 25.3.13-2
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Failed to build Galera in pbuilder for armhf (Debian Jessie) on amd64.
I could successfully build Galera 2.3.6, however, I face problems building 
other versions. One of the problems is that all versions of Galera after 2.3.6 
and before 2.3.14 have the same debian/changelog file that refers to version 
2.3.6. The up-to-date version of this file is required, because it is used by 
the pbuilder to detect version of the package. So, in order to start a build 
(pass through the pbuilder's pre-build checks) I had to write the correct 
version into that file, e.g. 2.3.13-1 (quilt format) for Galera 2.3.13. After 
that the compilation of the Galera 2.3.13 finishes successfully, but the build 
process fails on builder unit tests (the last important lines of the build log):

g++ -o galera/tests/galera_check -Wl,-z,relro galera/tests/galera_check.o 
galera/tests/data_set_check.o galera/tests/key_set_check.o galera$
builder_unit_test(["galera/tests/galera_check.passed"], 
["galera/tests/galera_check"])
Running suite(s): DataSet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): KeySet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): WriteSet
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): write_set
100%: Checks: 8, Failures: 0, Errors: 0
Running suite(s): trx_handle
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): service_thd
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): ist
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
100%: Checks: 6, Failures: 0, Errors: 0
Running suite(s): saved_state
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
33%: Checks: 3, Failures: 1, Errors: 1
galera/tests/saved_state_check.cpp:48:E:saved_state:test_unsafe:0: (after this 
point) Received signal 11 (Segmentation fault)
galera/tests/saved_state_check.cpp:155:F:saved_state:test_corrupt:0: Failure 
'uuid == WSREP_UUID_UNDEFINED' occured
Total tests failed: 2
scons: *** [galera/tests/galera_check.passed] Error 1
scons: building terminated because of errors.
debian/rules:28: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

The log above was generated using qemu-user-static (1:2.1+dfsg-12+deb8u5a) - 
the default version in Debain Jessie. Then I upgraded this package to 
qemu-user-static (1:2.5+dfsg-4~bpo8+1) using jessie-backports repositories. The 
build in the newer environment gave similar results:

g++ -o galera/tests/galera_check -Wl,-z,relro galera/tests/galera_check.o 
galera/tests/data_set_check.o galera/tests/key_set_check.o galera$
builder_unit_test(["galera/tests/galera_check.passed"], 
["galera/tests/galera_check"])
Running suite(s): DataSet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): KeySet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): WriteSet
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): write_set
100%: Checks: 8, Failures: 0, Errors: 0
Running suite(s): trx_handle
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): service_thd
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): ist
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
100%: Checks: 6, Failures: 0, Errors: 0
Running suite(s): saved_state
33%: Checks: 3, Failures: 1, Errors: 1
galera/tests/saved_state_check.cpp:48:E:saved_state:test_unsafe:0: (after this 
point) Test timeout expired
galera/tests/saved_state_check.cpp:155:F:saved_state:test_corrupt:0: Failure 
'uuid == WSREP_UUID_UNDEFINED' occured
Total tests failed: 2
scons: *** [galera/tests/galera_check.passed] Error 1
scons: building terminated because of errors.
debian/rules:28: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

According to old Galera thread 
https://groups.google.com/forum/#!topic/codership-team/ZWwZYG78a6A on Google 
Groups this issue is related to timeouts defined for the tests. If the test 
goes too long (which may happen in VM), then it is considered to be failed. It 
was suggested to alter the string with tcase_set_timeout(tc, 120); call in file 
galera/galera/tests/saved_state_check.cpp. I tried increasing the value to 1200 
and even commenting out this command - no luck in both cases - I got the same 
errors.

Building the Galera on a real armhf device (under Debian jessie) is successful. 
So, the issue is related to 

Processed: user debian...@lists.debian.org, usertagging 816440, severity of 816440 is serious ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 816440 piuparts
There were no usertags set.
Usertags are now: piuparts.
> severity 816440 serious
Bug #816440 [openjdk-9-jdk] openjdk-9-jdk: file conflict jawt.h
Severity set to 'serious' from 'normal'
> found 798374 usrmerge/10
Bug #798374 [piuparts] usrmerge: cannot be tested with piuparts
Marked as found in versions usrmerge/10.
> thanks
Stopping processing here.

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

Bug#809764: marked as done (libqb6-dev and libqb-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 10:00:58 +
with message-id 
and subject line Bug#809764: fixed in webcamoid 6.2.0-4
has caused the Debian Bug report #809764,
regarding libqb6-dev and libqb-dev: 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.)


-- 
809764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqb-dev,libqb6-dev
Version: libqb-dev/0.17.2.real-4
Version: libqb6-dev/6.2.0-3
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:



Extracting templates from packages: 46%
Extracting templates from packages: 93%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libexpat1:amd64.
(Reading database ... 10930 files and directories currently installed.)
Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-7) ...
Selecting previously unselected package libpng12-0:amd64.
Preparing to unpack .../libpng12-0_1.2.54-1_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.54-1) ...
Selecting previously unselected package libfreetype6:amd64.
Preparing to unpack .../libfreetype6_2.6.1-0.1_amd64.deb ...
Unpacking libfreetype6:amd64 (2.6.1-0.1) ...
Selecting previously unselected package ucf.
Preparing to unpack .../archives/ucf_3.0031_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0031) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
Unpacking fonts-dejavu-core (2.35-1) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ...
Unpacking fontconfig-config (2.11.0-6.3) ...
Selecting previously unselected package libfontconfig1:amd64.
Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ...
Unpacking libfontconfig1:amd64 (2.11.0-6.3) ...
Selecting previously unselected package fontconfig.
Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ...
Unpacking fontconfig (2.11.0-6.3) ...
Selecting previously unselected package libmtdev1:amd64.
Preparing to unpack .../libmtdev1_1.1.5-1_amd64.deb ...
Unpacking libmtdev1:amd64 (1.1.5-1) ...
Selecting previously unselected package libgcrypt20:amd64.
Preparing to unpack .../libgcrypt20_1.6.4-4_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.4-4) ...
Processing triggers for libc-bin (2.21-6) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libgcrypt20:amd64 (1.6.4-4) ...
Processing triggers for libc-bin (2.21-6) ...
Selecting previously unselected package libsystemd0:amd64.
(Reading database ... 11145 files and directories currently installed.)
Preparing to unpack .../libsystemd0_228-3_amd64.deb ...
Unpacking libsystemd0:amd64 (228-3) ...
Selecting previously unselected package libxau6:amd64.
Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
Unpacking libxau6:amd64 (1:1.0.8-1) ...
Selecting previously unselected package libxdmcp6:amd64.
Preparing to unpack .../libxdmcp6_1%3a1.1.2-1_amd64.deb ...
Unpacking libxdmcp6:amd64 (1:1.1.2-1) ...
Selecting previously unselected package libxcb1:amd64.
Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
Unpacking libxcb1:amd64 (1.11.1-1) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
Unpacking libx11-data (2:1.6.3-1) ...
Selecting previously unselected package libx11-6:amd64.
Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
Unpacking libx11-6:amd64 (2:1.6.3-1) ...
Selecting previously unselected package libx11-xcb1:amd64.
Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
Selecting previously unselected package libxfixes3:amd64.
Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
Selecting previously unselected package libxdamage1:amd64.
Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
Unpacking libxdamage1:amd64 (1:1.1.4-2+b1) ...
Selecting previously unselected package libxext6:amd64.
Preparing to unpack .../libxext6_2%3a1.3.3-1_amd64.deb ...
Unpacking libxext6:amd64 (2:1.3.3-1) ...
Selecting previously unselected package libxshmfence1:amd64.
Preparing 

Bug#810959: marked as done (ruby-celluloid-extras: FTBFS: Could not find 'timers' (~> 4.0.0) - did find: [timers-4.1.1] (Gem::LoadError))

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 09:37:52 +
with message-id 
and subject line Bug#810959: fixed in ruby-celluloid-extras 0.20.5-1
has caused the Debian Bug report #810959,
regarding ruby-celluloid-extras: FTBFS: Could not find 'timers' (~> 4.0.0) - 
did find: [timers-4.1.1] (Gem::LoadError)
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.)


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

  [..]

  
GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-celluloid-extras/usr/share/rubygems-integration/all
 ruby2.2 -e gem\ \"celluloid-extras\"
  /usr/lib/ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 
'timers' (~> 4.0.0) - did find: [timers-4.1.1] (Gem::LoadError)
  Checked in 
'GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-celluloid-extras/usr/share/rubygems-integration/all',
 execute `gem env` for more information
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:1311:in `block in 
activate_dependencies'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:1300:in `each'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:1300:in 
`activate_dependencies'
from /usr/lib/ruby/2.2.0/rubygems/specification.rb:1282:in `activate'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_gem.rb:67:in `block 
in gem'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_gem.rb:66:in 
`synchronize'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_gem.rb:66:in `gem'
from -e:1:in `'
  bigdecimal (1.2.6)
  bundler (1.10.6)
  dotenv (2.0.2)
  hitimes (1.2.1)
  io-console (0.4.3)
  json (1.8.1)
  minitest (5.8.3)
  molinillo (0.2.3)
  nenv (0.2.0)
  net-http-persistent (2.9.4)
  power_assert (0.2.6)
  psych (2.0.8)
  rake (10.4.2)
  rdoc (4.2.0)
  rspec-logsplit (0.1.3)
  test-unit (3.1.5)
  thor (0.19.1)
  timers (4.1.1)
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160114092838.LkwFur3A4I/ruby-celluloid-extras-0.20.0/debian/ruby-celluloid-extras
 returned exit code 1
  debian/rules:18: 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-celluloid-extras.0.20.0-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-celluloid-extras
Source-Version: 0.20.5-1

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

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

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

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated 
ruby-celluloid-extras 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: Wed, 02 Mar 2016 14:25:08 +0530
Source: ruby-celluloid-extras
Binary: ruby-celluloid-extras
Architecture: source all
Version: 0.20.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Balasankar C 
Description:
 ruby-celluloid-extras - Celluloid expansion, testing, and example classes
Closes: 810959
Changes:
 ruby-celluloid-extras (0.20.5-1) unstable; urgency=medium
 .
   * New 

Bug#810506: Opinion about linux-grsec in a stable release

[Yves-Alexis Perez]

Hi teams,

[first of all, I'm writing this with my linux-grsec hat, not my Debian
security team member hat, obviously]

As you may know, src:linux-grsec was accepted in unstable earlier this year.
As a quick summary, this is a source linux package (forked from and
periodically rebased against src:linux) which generates a linux kernel with
the grsecurity hardening patch (the patch is mostly about fighting memory
corruptions bugs, but not only, I won't enter into details here to keep it
short, but more information can be found in the ITP bug #605090).

When the package was accepted to unstable, I filed #810506 with severity
serious in order to prevent it to migrate to testing, because I wasn't really
sure it'd be fit for stable.

There are two main aspects for this:

- it's a new Linux kernel source package, next to the existing src:linux, so
that means code duplication
- due to the grsecurity release model, it's likely that it won't be possible
to stick with a major kernel version (4.3 right now, 4.4 upcoming), we would
have to upgrade to the latest major release (using stable uploads)

Even with this caveat, it seems that there is still interest from people
(including me) to have src:linux-grsec included in a stable release. I asked
the backport team about this [1], and they were not thrilled about this
because backports are for packages to be included in the next Debian release
(although the discussion isn't really over at that point).

So I'm asking the security team and release team their opinion about this, in
order to have a somehow formal answer which can get archived here.

Do you think it'd be possible to have src:linux-grsec included in Stretch,
with the two main points above?

The answer doesn't need to be right now, in case you'd prefer seeing how
things evolve in unstable for some time.

Thank in advance,

[1] https://lists.debian.org/debian-backports/2016/01/msg00027.html
-- 
Yves-Alexis



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

Bug#816483: marked as done (ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError))

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 08:25:28 +
with message-id 
<1456907128.1398342.537103850.2d896...@webmail.messagingengine.com>
and subject line Closing dupes of #816482
has caused the Debian Bug report #816483,
regarding ruby-acts-as-list: FTBFS: `require': cannot load such file -- 
bundler/setup (LoadError)
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.)


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

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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
   `-
--- End Message ---
--- Begin Message ---
Argh, so sorry. If my mail client disconnects from the internet, it will send 
multiple copies for some bizarre reason. :(--- End Message ---

Bug#816485: marked as done (ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError))

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 08:25:28 +
with message-id 
<1456907128.1398342.537103850.2d896...@webmail.messagingengine.com>
and subject line Closing dupes of #816482
has caused the Debian Bug report #816485,
regarding ruby-acts-as-list: FTBFS: `require': cannot load such file -- 
bundler/setup (LoadError)
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.)


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

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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
   `-
--- End Message ---
--- Begin Message ---
Argh, so sorry. If my mail client disconnects from the internet, it will send 
multiple copies for some bizarre reason. :(--- End Message ---

Bug#816484: marked as done (ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError))

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2016 08:25:28 +
with message-id 
<1456907128.1398342.537103850.2d896...@webmail.messagingengine.com>
and subject line Closing dupes of #816482
has caused the Debian Bug report #816484,
regarding ruby-acts-as-list: FTBFS: `require': cannot load such file -- 
bundler/setup (LoadError)
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.)


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

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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
   `-
--- End Message ---
--- Begin Message ---
Argh, so sorry. If my mail client disconnects from the internet, it will send 
multiple copies for some bizarre reason. :(--- End Message ---

Bug#816486: sup-mail: FTBFS: builder.rb:89:in `run': rake failed, exit code 1 (Gem::InstallError)

[Chris Lamb]

Source: sup-mail
Version: 0.22.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,

sup-mail fails to build from source in unstable/amd64:

  [..]

  │ Build native extensions for ruby2.2   
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  /usr/bin/ruby2.2 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/home/lamby/temp/cdt.20160302081219.eEWOpOcf19/sup-mail-0.22.1 debian/sup-mail
  fatal: Not a git repository (or any parent up to mount point /home)
  Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
  /usr/bin/ruby2.2 mkrf_conf_xapian.rb
  xapian: installing xapian-ruby..
  xapian: platform specific dependencies..
  /usr/lib/ruby/2.2.0/rubygems/ext/builder.rb:89:in `run': rake failed, exit 
code 1 (Gem::InstallError)
from /usr/lib/ruby/2.2.0/rubygems/ext/rake_builder.rb:13:in `build'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:72:in 
`block in build_and_install'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:66:in 
`chdir'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:66:in 
`build_and_install'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:103:in 
`block in build_all_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:100:in 
`each'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:100:in 
`build_all_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:116:in 
`'
  /usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': /usr/bin/ruby2.2 
/usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/home/lamby/temp/cdt.20160302081219.eEWOpOcf19/sup-mail-0.22.1 debian/sup-mail 
(Gem2Deb::CommandFailed)
from /usr/lib/ruby/vendor_ruby/gem2deb.rb:67:in `run_ruby'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:37:in `block in 
install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:34:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:34:in 
`install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `block in 
install'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `install'
from /usr/bin/dh_ruby:94:in `'
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160302081219.eEWOpOcf19/sup-mail-0.22.1/debian/sup-mail 
returned exit code 1
  debian/rules:15: 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
   `-


sup-mail.0.22.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#816485: ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError)

[Chris Lamb]

Source: ruby-acts-as-list
Version: 0.7.2-3
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-acts-as-list fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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
   `-

Bug#816483: ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError)

[Chris Lamb]

Source: ruby-acts-as-list
Version: 0.7.2-3
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-acts-as-list fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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
   `-

Bug#816484: ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError)

[Chris Lamb]

Source: ruby-acts-as-list
Version: 0.7.2-3
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-acts-as-list fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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
   `-

Bug#816482: ruby-acts-as-list: FTBFS: `require': cannot load such file -- bundler/setup (LoadError)

[Chris Lamb]

Source: ruby-acts-as-list
Version: 0.7.2-3
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-acts-as-list fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
 ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
  /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
 `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from -e:1:in `block in '
from -e:1:in `each'
from -e:1:in `'
  WARNING: Test "ruby2.2" failed, but ignoring this test result.
  /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
  
  
┌──────────────────────────────────────────────────────────────────────────────â”
  │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
   │
  
└──────────────────────────────────────────────────────────────────────────────┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-acts-as-list/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\ \}
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2: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.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
 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-acts-as-list.0.7.2-3.unstable.amd64.log.txt.gz
Description: Binary data

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

[Chris Lamb]

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

Bug#805674: ohcount: diff for NMU version 3.0.0-8.1

[Sylvestre Ledru]

Excellent, thanks! 
No need to wait,  please upload it now :) 

Le 1 mars 2016 22:07:16 GMT+01:00, Christian Hofstaedtler  a 
écrit :
>Control: tags 805674 + patch
>Control: tags 805674 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for ohcount (versioned as 3.0.0-8.1) and
>uploaded it to DELAYED/2. Please feel free to tell me if I
>should delay it longer.
>
>Regards.
>diff -Nru ohcount-3.0.0/debian/changelog ohcount-3.0.0/debian/changelog
>--- ohcount-3.0.0/debian/changelog 2014-01-16 16:26:45.0 +0100
>+++ ohcount-3.0.0/debian/changelog 2016-03-01 22:03:36.0 +0100
>@@ -1,3 +1,11 @@
>+ohcount (3.0.0-8.1) unstable; urgency=medium
>+
>+  * Non-maintainer upload.
>+  * Fix build system being broken by removal of deprecated "Config"
>+object in Ruby 2.2. (Closes: #805674)
>+
>+ -- Christian Hofstaedtler   Tue, 01 Mar 2016
>22:02:31 +0100
>+
> ohcount (3.0.0-8) unstable; urgency=low
> 
>   * Remove the explicit dependency on ruby 1.8
>diff -Nru ohcount-3.0.0/debian/patches/rbconfig.patch
>ohcount-3.0.0/debian/patches/rbconfig.patch
>--- ohcount-3.0.0/debian/patches/rbconfig.patch1970-01-01
>01:00:00.0 +0100
>+++ ohcount-3.0.0/debian/patches/rbconfig.patch2016-03-01
>22:00:01.0 +0100
>@@ -0,0 +1,28 @@
>+Index: ohcount-3.0.0/build
>+===
>+--- ohcount-3.0.0.orig/build
> ohcount-3.0.0/build
>+@@ -114,12 +114,12 @@ run_test_suite()
>+ 
>+ build_ruby_bindings()
>+ {
>+- arch=`ruby -rmkmf -e 'print Config::expand(CONFIG["arch"])'`
>++ arch=`ruby -rmkmf -e 'print
>RbConfig::expand(RbConfig::CONFIG["arch"])'`
>+  echo "Generating Ruby bindings for $arch"
>+  sh -c "swig -ruby -o ruby/ohcount_wrap.c ruby/ohcount.i" || exit 1
>+  mkdir -p ruby/$arch
>+   sh -c "$cc $RB_SHARED ruby/ohcount_wrap.c $files -o
>ruby/$arch/$RB_SHARED_NAME \
>+--I`ruby -rmkmf -e 'print Config::expand(CONFIG["archdir"])'` \
>++-I`ruby -rmkmf -e 'print
>RbConfig::expand(RbConfig::CONFIG["archdir"])'` \
>+ -lpcre" || exit 1
>+   sh -c "cd test/unit/ruby && ruby ruby_test.rb" || exit 1
>+ }
>+@@ -156,7 +156,7 @@ then
>+   rm -f src/hash/*.c
>+   rm -f src/$SHARED_NAME
>+   rm -f ruby/$RB_SHARED_NAME
>+-  rm -rf ruby/`ruby -rmkmf -e 'print
>Config::expand(CONFIG["arch"])'`/*
>++  rm -rf ruby/`ruby -rmkmf -e 'print
>RbConfig::expand(RbConfig::CONFIG["arch"])'`/*
>+ else
>+   echo "Usage: build [all|ohcount|shared|tests|ruby|clean]"
>+ fi
>diff -Nru ohcount-3.0.0/debian/patches/series
>ohcount-3.0.0/debian/patches/series
>--- ohcount-3.0.0/debian/patches/series2014-01-16 19:21:49.0
>+0100
>+++ ohcount-3.0.0/debian/patches/series2016-03-01 21:59:13.0
>+0100
>@@ -2,3 +2,4 @@
> fix_null_dereference.patch
> txx_support.patch
> disabled_test_suite.patch
>+rbconfig.patch
>-- 
> ,''`.  Christian Hofstaedtler 
>: :' :  Debian Developer
>`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
>  `-