Bug#906789: Launchpad Bug#1784103 remove yapf from cosmic (Debian Bug#906789: missing python3-pkg-resources dependency)

[Nicholas D Steeves]

Hi Matthias,

I just wanted to let you know that I'm working with Ana to get yapf
into a good state ASAP.  On a PR on salsa she writes that she plans to
upload the fixes after next Thursday.

I don't know when the final sync from Debian will be, but I hope this
means the yapf and its rdeps won't be cut from Ubuntu 18.10.  P.S. I
maintain Elpy, one of yapf's rdeps, and if any Ubuntu users find bugs
in Elpy then I plan to fix them in Debian without delay.

https://bugs.launchpad.net/ubuntu/+source/elpy/+bug/1784103

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

[Hector Oron]

On Tue, Jul 03, 2018 at 10:09:56AM +0200, Antoine R. Dumont wrote:
> Package: python3-celery
> Version: 4.1.0-4
> Severity: serious
> Hello,
> 
> Setting up python3-celery (4.2.0-1) ...
>   File "/usr/lib/python3/dist-packages/celery/backends/redis.py", line 22
> from . import async, base
>   ^
> SyntaxError: invalid syntax
> 
>   File "/usr/lib/python3/dist-packages/celery/backends/rpc.py", line 20
> from .async import AsyncBackendMixin, BaseResultConsumer
>   ^
> SyntaxError: invalid syntax
> 
> dpkg: error processing package python3-celery (--configure):
>  installed python3-celery package post-installation script subprocess
>  returned error exit status 1

I have submitted a backported patch from upstream as MR#1 in salsa:
https://salsa.debian.org/python-team/modules/celery/merge_requests/1

I have been able to build the package and install it, I have not done any 
further testing.

Regards,
 Héctor Orón Martínez


signature.asc
Description: PGP signature

Processed: tagging 902900

[Debian Bug Tracking System]

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

> tags 902900 + patch
Bug #902900 [python3-celery] python3-celery: python3-celery fails to install 
with Python 3.7
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#907752: marked as done (slick-greeter: lightdm-vala must be build dependency without alternative)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 21:34:26 +
with message-id 
and subject line Bug#907752: fixed in slick-greeter 1.2.2-2
has caused the Debian Bug report #907752,
regarding slick-greeter: lightdm-vala must be build dependency without 
alternative
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.)


-- 
907752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slick-greeter
Version: 1.2.2-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/slick-greeter.html

...
Making all in src
make[3]: Entering directory '/build/1st/slick-greeter-1.2.2/src'
rm -f logo_generator_vala.stamp && echo stamp > logo_generator_vala.stamp-t
rm -f slick_greeter_vala.stamp && echo stamp > slick_greeter_vala.stamp-t
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac -D HAVE_GTK_3_20_0 --debug 
--pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg 
liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 
--target-glib 2.32  -C logo-generator.vala
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac -D HAVE_GTK_3_20_0 --debug 
--pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg 
liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 
--target-glib 2.32  -C config.vapi fixes.vapi xsync.vapi animate-timer.vala 
background.vala cached-image.vala cairo-utils.vala email-autocompleter.vala 
dash-box.vala dash-button.vala dash-entry.vala fadable.vala fadable-box.vala 
fading-label.vala flat-button.vala greeter-list.vala idle-monitor.vala 
list-stack.vala main-window.vala menu.vala menubar.vala prompt-box.vala 
session-list.vala remote-login-service.vala settings.vala shutdown-dialog.vala 
toggle-box.vala slick-greeter.vala user-list.vala user-prompt-box.vala
error: Package `liblightdm-gobject-1' not found in specified Vala API 
directories or GObject-Introspection GIR directories
Compilation failed: 1 error(s), 0 warning(s)
make[3]: *** [Makefile:968: logo_generator_vala.stamp] Error 1



This is caused by the following in the build dependencies:
   lightdm-vala (>= 1.18.3) | gir1.2-lightdm-1 (>= 1.22)


The package always needs lightdm-vala (and the required version
is already in stable), please remove the gir1.2-lightdm-1
alternative.
--- End Message ---
--- Begin Message ---
Source: slick-greeter
Source-Version: 1.2.2-2

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

Debian distribution maintenance software
pp.
David Mohammed  (supplier of updated slick-greeter 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 01 Sep 2018 17:28:59 +0100
Source: slick-greeter
Binary: slick-greeter
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: David Mohammed 
Changed-By: David Mohammed 
Description:
 slick-greeter - Slick-looking LightDM greeter
Closes: 907752
Changes:
 slick-greeter (1.2.2-2) unstable; urgency=medium
 .
   * Packaging Changes
 - control: bump Standards-Version; changed rules to add
   verbose compilation
 - control: change alternate for lightdm-vala to resolve
   FTBS (Closes: #907752)
   The alternate ensures the same package builds both on Ubuntu
   and Debian
 - Add patch 0001-background.vala-Fix-build-with-vala-0.41.91.patch
   to ensure package build with vala 0.41.91
 - rules: Add override for dh-missing to fail if missing files;
   this ensures we are ready for compat 12
 - copyright: clarify that debian source tarball is missing upstream
   debian packaging folder which has been replaced by ours.
Checksums-Sha1:
 9b458807edcc9c48b2be13cf5ef47392a2fc51c4 2153 slick-greeter_1.2.2-2.dsc
 42919887e9b2f11ab8420d1bf9b0a912ba8dec65 243988 slick-greeter_1.2.2.orig.tar.gz
 504859d724292edb9d9ec6d34b4f1fdbddb55680 10664 
slick-greeter_1.2.2-2.debian.tar.xz
 38c00ff9fca0d11b620d9b3ccd345efaa3bfdd95 17430 

Bug#904615: marked as done (python3-rpyc: fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 20:49:11 +
with message-id 
and subject line Bug#904615: fixed in rpyc 4.0.2-1
has caused the Debian Bug report #904615,
regarding python3-rpyc: fails to install with Python 3.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.)


-- 
904615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-rpyc
Version: 3.4.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

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

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

  Setting up python3-rpyc (3.4.4-1) ...
File "/usr/lib/python3/dist-packages/rpyc/__init__.py", line 50
  from rpyc.utils.helpers import async, timed, buffiter, BgServingThread, 
restricted
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/rpyc/core/__init__.py", line 5
  from rpyc.core.async import AsyncResult, AsyncResultTimeout
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/rpyc/core/protocol.py", line 15
  from rpyc.core.async import AsyncResult
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/rpyc/utils/helpers.py", line 101
  def async(proxy):
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-rpyc (--configure):
   installed python3-rpyc package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   python3-rpyc


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-rpyc=3.4.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rpyc
Source-Version: 4.0.2-1

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

Debian distribution maintenance software
pp.
Carl Suster  (supplier of updated rpyc 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: Tue, 14 Aug 2018 18:35:11 +1000
Source: rpyc
Binary: python3-rpyc python-rpyc-doc
Architecture: source
Version: 4.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Carl Suster 
Description:
 python-rpyc-doc - transparent and symmetric Remote Python Call library -- 
documenta
 python3-rpyc - transparent and symmetric Remote Python Call library -- Python3 
m
Closes: 893611 904615
Changes:
 rpyc (4.0.2-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/control: Remove ancient X-Python3-Version field
 .
   [ Carl Suster ]
   * New upstream release (Closes: #904615).
   * Recommend python3-gevent to support the new gevent server (however this
 feature is currently disabled due to crashes that are not yet understood).
   * Build-Depend on python3-gevent for the corresponding test (however this
 test is currently disabled to match upstream CI configuration).
   * Make the build reproducible by applying the patch provided by Chris Lamb
 (Closes: #893611).
   * Build-Depend on python3-sphinx-rtd-theme which is now used by the docs.
   * Stop cleaning up (in debian/rules) screencasts and CI image from docs that
 no longer exist upstream.
   * Remove GitHub "fork me" banner from documentation.
   * Update Standards-Version to 4.2.0 (no changes needed).
   * Mark the doc package as M-A: foreign as per multiarch hinter.
   * Add upstream metadata file.
   * Bump debhelper compat to 11.
Checksums-Sha1:
 5da2eaa44ac1b77d2fd0647c8b2b977dc2c4bfc2 2071 rpyc_4.0.2-1.dsc
 4527f284e8be8d990dbe72d867929939410cd881 56 rpyc_4.0.2.orig.tar.gz
 7eff9f54738a35ffae4d1cec29068a3ce9d9086f 5816 rpyc_4.0.2-1.debian.tar.xz
 d3a11e1af9295539a67ac931d5e12456d320 7576 rpyc_4.0.2-1_amd64.buildinfo

Processed: Re: Bug#907381: python-sphinx: missing dependency on python-stemmer

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:bzr 2.7.0+bzr6622-11
Bug #907381 [python-sphinx] python-sphinx: missing dependency on python-stemmer
Bug reassigned from package 'python-sphinx' to 'src:bzr'.
No longer marked as found in versions sphinx/1.7.7-1.
Ignoring request to alter fixed versions of bug #907381 to the same values 
previously set
Bug #907381 [src:bzr] python-sphinx: missing dependency on python-stemmer
Marked as found in versions bzr/2.7.0+bzr6622-11.
> affects -1 - src:bzr
Bug #907381 [src:bzr] python-sphinx: missing dependency on python-stemmer
Removed indication that 907381 affects src:bzr
> retitle -1 bzr: FTBFS with Sphinx ≥ 1.7.7-1, needs build-dep on python-stemmer
Bug #907381 [src:bzr] python-sphinx: missing dependency on python-stemmer
Changed Bug title to 'bzr: FTBFS with Sphinx ≥ 1.7.7-1, needs build-dep on 
python-stemmer' from 'python-sphinx: missing dependency on python-stemmer'.

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

Bug#907381: python-sphinx: missing dependency on python-stemmer

[Dmitry Shachnev]

Control: reassign -1 src:bzr 2.7.0+bzr6622-11
Control: affects -1 - src:bzr
Control: retitle -1 bzr: FTBFS with Sphinx ≥ 1.7.7-1, needs build-dep on 
python-stemmer

Hi Adrian and bzr maintainers,

On Sat, Sep 01, 2018 at 08:05:34PM +0300, Adrian Bunk wrote:
> You already fixed ubuntu-packaging-guide, and this is the only one 
> I found in addition to bzr.
>
> So reassigning this bug to bzr sounds like an option.

Thanks, doing so then.

Note for bzr maintainers: search in non-English Sphinx projects has been
disabled for several releases. Now I finally re-enabled it, but projects
which use non-English language or html_search_language [1] need to depend
on python-stemmer or python3-stemmer.

[1]: 
http://www.sphinx-doc.org/en/master/usage/configuration.html#confval-html_search_language

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 904017 gsettings-qt
Bug #904017 [src:gsettings-qt] gsettings-qt: FTBFS with Qt 5.11.1 in 
Experimental
Bug reassigned from package 'src:gsettings-qt' to 'gsettings-qt'.
No longer marked as found in versions gsettings-qt/0.1+17.10.20170824-4 and 
gsettings-qt/1.1.8.8-1.
Ignoring request to alter fixed versions of bug #904017 to the same values 
previously set
> forcemerge 905059 904017
Bug #905059 {Done: Yanhao Mo } [gsettings-qt] gsettings-qt: 
FTBFS with Qt 5.11.1
Bug #904017 [gsettings-qt] gsettings-qt: FTBFS with Qt 5.11.1 in Experimental
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as fixed in versions gsettings-qt/0.1+17.10.20170824-6.
Merged 904017 905059
> thanks
Stopping processing here.

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

Bug#907757: marked as done (libedataserverui1.2-dev: missing dependency on libecal1.2-dev)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 19:18:59 +
with message-id 
and subject line Bug#907757: fixed in evolution-data-server 3.29.92-2
has caused the Debian Bug report #907757,
regarding libedataserverui1.2-dev: missing dependency on libecal1.2-dev
to be marked as done.

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

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


-- 
907757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libedataserverui1.2-dev
Version: 3.29.92-1
Severity: serious
Control: affects -1 src:gnome-contacts

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-contacts.html

...
Called `/usr/bin/pkg-config --cflags libedataserverui-1.2` -> 1


meson.build:44:0: ERROR:  Could not generate cargs for libedataserverui-1.2:


dh_auto_configure: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/gnome-contacts 
-Dwith-cheese=yes returned exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
--- End Message ---
--- Begin Message ---
Source: evolution-data-server
Source-Version: 3.29.92-2

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated evolution-data-server 
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: Sat, 01 Sep 2018 15:04:46 -0400
Source: evolution-data-server
Binary: evolution-data-server evolution-data-server-common 
evolution-data-server-tests evolution-data-server-dev evolution-data-server-doc 
libedataserver-1.2-23 libedataserver1.2-dev gir1.2-edataserver-1.2 
libedataserverui-1.2-2 libedataserverui1.2-dev gir1.2-edataserverui-1.2 
libcamel-1.2-62 libcamel1.2-dev gir1.2-camel-1.2 libebook-1.2-19 
libebook1.2-dev gir1.2-ebook-1.2 libedata-book-1.2-25 libedata-book1.2-dev 
gir1.2-ebookcontacts-1.2 libebook-contacts-1.2-2 libebook-contacts1.2-dev 
libecal-1.2-19 libecal1.2-dev libedata-cal-1.2-29 libedata-cal1.2-dev 
libebackend-1.2-10 libebackend1.2-dev
Architecture: source
Version: 3.29.92-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 evolution-data-server - evolution database backend server
 evolution-data-server-common - architecture independent files for Evolution 
Data Server
 evolution-data-server-dev - Development files for evolution-data-server 
(metapackage)
 evolution-data-server-doc - Documentation files for the Evolution Data Server 
libraries
 evolution-data-server-tests - Installed tests for the evolution database 
backend server
 gir1.2-camel-1.2 - GObject introspection for the Camel library
 gir1.2-ebook-1.2 - GObject introspection for the EBook library
 gir1.2-ebookcontacts-1.2 - GObject introspection for the EBook Contacts library
 gir1.2-edataserver-1.2 - GObject introspection for the EDataServer library
 gir1.2-edataserverui-1.2 - GObject introspection for the EDataServerUI library
 libcamel-1.2-62 - Evolution MIME message handling library
 libcamel1.2-dev - Development files for libcamel
 libebackend-1.2-10 - Utility library for evolution data servers
 libebackend1.2-dev - Utility library for evolution data servers (development 
files)
 libebook-1.2-19 - Client library for evolution address books
 libebook-contacts-1.2-2 - Client library for evolution contacts books
 libebook-contacts1.2-dev - Client library for evolution contacts books 
(development files)
 libebook1.2-dev - Client library for evolution address books (development 
files)
 libecal-1.2-19 - Client library for evolution calendars
 libecal1.2-dev - Client library for evolution calendars (development files)
 libedata-book-1.2-25 - Backend library for evolution address books
 libedata-book1.2-dev - Backend library for evolution address books 
(development files)
 libedata-cal-1.2-29 - Backend library for evolution 

Bug#905107: gnome-shell-pomodoro: global.screen is not available in GNOME Shell 3.29

[Joseph Herlant]

Hi Simon,

Sorry for the late, I just saw this bug.
Thanks for forwarding it upstream. I'll work on a PR for that this weekend.

Joseph

Bug#907171: prometheus FTBFS:

[Adrian Bunk]

Control: severity -1 normal

On Mon, Aug 27, 2018 at 07:18:30PM +0100, Martín Ferrari wrote:
> On 27/08/18 17:08, Adrian Bunk wrote:
> 
> > How often did you try?
> > 
> > I would say the probability to hit is somewhere around 50%:
> > https://tests.reproducible-builds.org/debian/history/prometheus.html
> 
> I just tried 20 builds, while using desktop applications that put some
> extra strain on tHE CPU, and none failed..

It didn't fail this way on the buildds, so I agree that whatever 
triggers this problem does not look RC right now.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: Bug#907171: prometheus FTBFS:

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #907171 [src:prometheus] prometheus FTBFS:
Severity set to 'normal' from 'serious'

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

Processed: tagging 907763

[Debian Bug Tracking System]

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

> tags 907763 + buster sid
Bug #907763 [src:ant-contrib] ant-contrib: FTBFS in buster/sid (failing tests)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#907381: python-sphinx: missing dependency on python-stemmer

[Adrian Bunk]

On Mon, Aug 27, 2018 at 01:31:36PM +0300, Dmitry Shachnev wrote:
> Hi Adrian!

Hi Dmitry!

> On Mon, Aug 27, 2018 at 11:20:20AM +0300, Adrian Bunk wrote:
> > Package: python-sphinx
> > Version: 1.7.7-1
> > Severity: serious
> > Control: affects -1 src:bzr
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/bzr.html
> >
> > ...
> > Exception occurred:
> >   File "/usr/lib/python2.7/dist-packages/sphinx/search/es.py", line 14, in 
> > 
> > import Stemmer
> > ImportError: No module named Stemmer
> 
> I did not want to make pystemmer a hard dependency because this only affects
> non-English documentation.
> 
> Indeed it is my bad that I did not check what packages will be broken with
> this, but maybe you can estimate how many of them got broken now? If it is
> < 10 source packages, I would rather file bugs on them.

You already fixed ubuntu-packaging-guide, and this is the only one 
I found in addition to bzr.

So reassigning this bug to bzr sounds like an option.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Bug#890307: tortoisehg: needs update for mercurial 4.6

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream patch pending
Bug #890307 [tortoisehg] tortoisehg: needs update for mercurial 4.6
Added tag(s) patch, fixed-upstream, and pending.

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

Processed: block 907015 with 907351

[Debian Bug Tracking System]

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

> block 907015 with 907351
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
907015 was blocked by: 898801 907049 900160 907135 900153 907278 907118 906981 
907031 898804 907055 907427 897652 895959 907215 906955 907219 900982 907340 
907491 897658 897643 900158 907216 898807 891625 900152 898805 898800 898802 
898803 900156 906997 900154 907079 907518 900161 907033 907022 907528 897651 
907339 907028 891665 900159 900157 907168
907015 was not blocking any bugs.
Added blocking bug(s) of 907015: 907351
> thanks
Stopping processing here.

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

Processed: severity of 907351 is serious

[Debian Bug Tracking System]

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

> severity 907351 serious
Bug #907351 [tor] tor: TLS error while constructing a TLS context: dh key too 
small (in SSL routines:ssl3_ctx_ctrl:---)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#907767: mozplugger seems to be useless now

[Adrian Bunk]

Package: mozplugger
Version: 1.14.5-2
Severity: serious
Tags: buster sid

As far as I can see, not a single one of the 15 (sic) browser packages
in the dependencies does both still exist in unstable and still work
with mozplugger.

Processed: limit source to gnomint, tagging 631768, tagging 885817, tagging 855200

[Debian Bug Tracking System]

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

> limit source gnomint
Limiting to bugs with field 'source' containing at least one of 'gnomint'
Limit currently set to 'source':'gnomint'

> tags 631768 + pending
Bug #631768 [gnomint] gnomint saved window size after using the quit button is 
out of range
Added tag(s) pending.
> tags 885817 + pending
Bug #885817 [src:gnomint] gnomint: Depends on gconf
Added tag(s) pending.
> tags 855200 + pending
Bug #855200 [gnomint] gnomint: segfault when exporting private keys
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#907765: honeysql-clojure: FTBFS in buster/sid (Could not locate honeysql/format_test__init.class or honeysql/format_test.clj on classpath.)

[Santiago Vila]

Package: src:honeysql-clojure
Version: 0.8.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper --with jh_maven_repo_helper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
cat debian/header.html > /<>/CHANGES.html
sed -i'' -e 's#@TITLE@#0.8.2#g' /<>/CHANGES.html
markdown /<>/CHANGES.md >> /<>/CHANGES.html
cat debian/footer.html >> /<>/CHANGES.html
cat debian/header.html > /<>/README.html
sed -i'' -e 's#@TITLE@#Honey SQL#g' /<>/README.html
markdown /<>/README.md >> /<>/README.html
cat debian/footer.html >> /<>/README.html
jar cf honeysql.jar -C src .
mkdir -p /<>/doc/html && mv /<>/*.html 
/<>/doc/html
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
(cd test && find . -name '*.cljc' | \
xargs clojure -cp /<>/honeysql.jar)
Exception in thread "main" java.io.FileNotFoundException: Could not locate 
honeysql/format_test__init.class or honeysql/format_test.clj on classpath. 
Please check that namespaces with dashes use underscores in the Clojure file 
name., compiling:(/<>/test/./honeysql/core_test.cljc:1:1)
at clojure.lang.Compiler.load(Compiler.java:7526)
at clojure.lang.Compiler.loadFile(Compiler.java:7452)
at clojure.main$load_script.invokeStatic(main.clj:278)
at clojure.main$script_opt.invokeStatic(main.clj:338)
at clojure.main$script_opt.invoke(main.clj:333)
at clojure.main$main.invokeStatic(main.clj:424)
at clojure.main$main.doInvoke(main.clj:387)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.lang.Var.applyTo(Var.java:702)
at clojure.main.main(main.java:37)
Caused by: java.io.FileNotFoundException: Could not locate 
honeysql/format_test__init.class or honeysql/format_test.clj on classpath. 
Please check that namespaces with dashes use underscores in the Clojure file 
name.
at clojure.lang.RT.load(RT.java:463)
at clojure.lang.RT.load(RT.java:426)
at clojure.core$load$fn__9115.invoke(core.clj:6046)
at clojure.core$load.invokeStatic(core.clj:6045)
at clojure.core$load.doInvoke(core.clj:6029)
at clojure.lang.RestFn.invoke(RestFn.java:408)
at clojure.core$load_one.invokeStatic(core.clj:5848)
at clojure.core$load_one.invoke(core.clj:5843)
at clojure.core$load_lib$fn__9060.invoke(core.clj:5888)
at clojure.core$load_lib.invokeStatic(core.clj:5887)
at clojure.core$load_lib.doInvoke(core.clj:5868)
at clojure.lang.RestFn.applyTo(RestFn.java:142)
at clojure.core$apply.invokeStatic(core.clj:659)
at clojure.core$load_libs.invokeStatic(core.clj:5925)
at clojure.core$load_libs.doInvoke(core.clj:5909)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.core$apply.invokeStatic(core.clj:659)
at clojure.core$require.invokeStatic(core.clj:5947)
at clojure.core$require.doInvoke(core.clj:5947)
at clojure.lang.RestFn.invoke(RestFn.java:457)
at 
honeysql.core_test$eval2694$loading__9001__auto2695.invoke(core_test.cljc:1)
at honeysql.core_test$eval2694.invokeStatic(core_test.cljc:1)
at honeysql.core_test$eval2694.invoke(core_test.cljc:1)
at clojure.lang.Compiler.eval(Compiler.java:7062)
at clojure.lang.Compiler.eval(Compiler.java:7051)
at clojure.lang.Compiler.load(Compiler.java:7514)
... 9 more
make[1]: *** [debian/rules:26: override_dh_auto_test] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/honeysql-clojure.html

In reproducible builds it seems to be random, but I tried to build it 50 times
on GCE n1-standard-1 machines today and it failed each and every time.
If you need a test machine to reproduce please say so.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#907766: node-chokidar: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:node-chokidar
Version: 1.7.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha --exit --reporter spec


  chokidar
✓ should expose public API methods
fs.watch (non-polling)
  watch a directory
✓ should produce an instance of chokidar.FSWatcher
✓ should expose public API methods
✓ should emit `add` event when file was added (57ms)
✓ should emit `addDir` event when directory was added (56ms)
✓ should emit `change` event when file was changed
✓ should emit `unlink` event when file was removed (104ms)
✓ should emit `unlinkDir` event when a directory was removed (53ms)
✓ should emit `unlink` and `add` events when a file is renamed (156ms)
✓ should emit `add`, not `change`, when previously deleted file is 
re-added (161ms)
✓ should not emit `unlink` for previously moved files (404ms)
✓ should survive ENOENT for missing subdirectories
✓ should notice when a file appears in a new directory
✓ should watch removed and re-added directories (1514ms)
  watch individual files
✓ should detect changes
✓ should detect unlinks (156ms)
✓ should detect unlink and re-add (257ms)
✓ should ignore unwatched siblings (55ms)
  renamed directory
✓ should emit `add` for a file in a renamed directory (1017ms)
  watch non-existent paths
✓ should watch non-existent file and detect add (56ms)
✓ should watch non-existent dir and detect addDir/add (106ms)
  watch glob patterns
✓ should correctly watch and emit based on glob input (62ms)
✓ should respect negated glob patterns (156ms)
✓ should traverse subdirs to match globstar patterns (216ms)
✓ should resolve relative paths with glob patterns (72ms)
✓ should correctly handle conflicting glob patterns (158ms)
✓ should correctly handle intersecting glob patterns (58ms)
✓ should not confuse glob-like filenames with globs (103ms)
✓ should treat glob-like directory names as literal directory names 
when globbing is disabled (64ms)
✓ should treat glob-like filenames as literal filenames when globbing 
is disabled (51ms)
✓ should not prematurely filter dirs against complex globstar 
patterns (62ms)
✓ should emit matching dir events
  watch symlinks
✓ should watch symlinked dirs
✓ should watch symlinked files
✓ should follow symlinked files within a normal dir
✓ should watch paths with a symlinked parent
✓ should not recurse indefinitely on circular symlinks
✓ should recognize changes following symlinked dirs
✓ should follow newly created symlinks (57ms)
✓ should watch symlinks as files when followSymlinks:false
✓ should watch symlinks within a watched dir as files when 
followSymlinks:false (310ms)
✓ should not reuse watcher when following a symlink to elsewhere 
(115ms)
✓ should properly match glob patterns that include a symlinked dir
  watch arrays of paths/globs
✓ should watch all paths in an array
✓ should accommodate nested arrays in input
✓ should throw if provided any non-string paths
  watch options
ignoreInitial
  false
✓ should emit `add` events for preexisting files
✓ should emit `addDir` event for watched dir
✓ should emit `addDir` events for preexisting dirs
  true
✓ should ignore inital add events (51ms)
✓ should ignore add events on a subsequent .add() (1002ms)
✓ should notice when a file appears in an empty directory
✓ should emit a change on a preexisting file as a change
✓ should not emit for preexisting dirs when depth is 0 (418ms)
ignored
  ✓ should check ignore after stating
  ✓ should not choke on an ignored watch path
  ✓ should ignore the contents of ignored dirs (359ms)
  ✓ should allow regex/fn ignores (57ms)
depth
  ✓ should not recurse if depth is 0
  ✓ should recurse to specified depth (66ms)
  ✓ should respect depth setting when following symlinks (65ms)
  ✓ should respect depth setting when following a new symlink
  ✓ should correctly handle dir events when depth is 0 (68ms)
atomic
  ✓ should ignore vim/emacs/Sublime swapfiles (906ms)
  ✓ should ignore stale tilde files (53ms)
cwd
  

Bug#907763: ant-contrib: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:ant-contrib
Version: 1.0~b3+svn177-9
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with maven-repo-helper
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/ant-contrib-1.0~b3+svn177'
dh_auto_build -- jar
ant -propertyfile ./debian/ant.properties -Duser.name debian jar
Buildfile: /<>/ant-contrib-1.0~b3+svn177/build.xml

init:

configure:

resolve:

classpath-ivy:

classpath-no-ivy:

classpath:

compile:
[mkdir] Created dir: /<>/ant-contrib-1.0~b3+svn177/target/classes
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:113: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7
[javac] Compiling 111 source files to 
/<>/ant-contrib-1.0~b3+svn177/target/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 7
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 warning
 [copy] Copying 2 files to 
/<>/ant-contrib-1.0~b3+svn177/target/classes

jar:
  [jar] Building jar: 
/<>/ant-contrib-1.0~b3+svn177/target/ant-contrib.jar

BUILD SUCCESSFUL
Total time: 4 seconds
make[1]: Leaving directory '/<>/ant-contrib-1.0~b3+svn177'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/ant-contrib-1.0~b3+svn177'
dh_auto_build -- test
ant -propertyfile ./debian/ant.properties -Duser.name debian test
Buildfile: /<>/ant-contrib-1.0~b3+svn177/build.xml

init:

configure:

resolve:

classpath-ivy:

classpath-no-ivy:

classpath:

compile:
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:113: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7

compile-tests:
[mkdir] Created dir: 
/<>/ant-contrib-1.0~b3+svn177/target/test-classes
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:127: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7
[javac] Compiling 25 source files to 
/<>/ant-contrib-1.0~b3+svn177/target/test-classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 7
[javac] 1 warning
 [copy] Copying 74 files to 
/<>/ant-contrib-1.0~b3+svn177/target/test-classes

gump-safe-test:

init:

configure:

resolve:

classpath-ivy:

classpath-no-ivy:

classpath:

compile:
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:113: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7

compile-tests:
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:127: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7

jar:

run-test:
[junit] Testsuite: net.sf.antcontrib.design.VerifyDesignTest
[junit] Tests run: 41, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
8.467 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.AntCallBackTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.252 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.AssertTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.423 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.ForTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.138 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.ForeachTaskTest
[junit] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.659 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.IfTaskTest
[junit] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.588 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.OutOfDateTest

Bug#907764: golang-github-hashicorp-raft: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-hashicorp-raft
Version: 1.0.0+git20180118.077966db-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-hashicorp-raft-1.0.0\+git20180118.077966db/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-hashicorp-raft-1.0.0\+git20180118.077966db/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/hashicorp/raft github.com/hashicorp/raft/bench
github.com/hashicorp/golang-lru/simplelru
github.com/hashicorp/go-immutable-radix
github.com/armon/go-metrics
github.com/hashicorp/go-msgpack/codec
github.com/hashicorp/raft
github.com/hashicorp/raft/bench
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/hashicorp/raft github.com/hashicorp/raft/bench
=== RUN   TestCommitment_setVoters
--- PASS: TestCommitment_setVoters (0.00s)
=== RUN   TestCommitment_match_max
--- PASS: TestCommitment_match_max (0.00s)
=== RUN   TestCommitment_match_nonVoting
--- PASS: TestCommitment_match_nonVoting (0.00s)
=== RUN   TestCommitment_recalculate
--- PASS: TestCommitment_recalculate (0.00s)
=== RUN   TestCommitment_recalculate_startIndex
--- PASS: TestCommitment_recalculate_startIndex (0.00s)
=== RUN   TestCommitment_noVoterSanity
--- PASS: TestCommitment_noVoterSanity (0.00s)
=== RUN   TestCommitment_singleVoter
--- PASS: TestCommitment_singleVoter (0.00s)
=== RUN   TestConfiguration_Configuration_Clone
--- PASS: TestConfiguration_Configuration_Clone (0.00s)
=== RUN   TestConfiguration_configurations_Clone
--- PASS: TestConfiguration_configurations_Clone (0.00s)
=== RUN   TestConfiguration_hasVote
--- PASS: TestConfiguration_hasVote (0.00s)
=== RUN   TestConfiguration_checkConfiguration
--- PASS: TestConfiguration_checkConfiguration (0.00s)
=== RUN   TestConfiguration_nextConfiguration_table
--- PASS: TestConfiguration_nextConfiguration_table (0.00s)
=== RUN   TestConfiguration_nextConfiguration_prevIndex
--- PASS: TestConfiguration_nextConfiguration_prevIndex (0.00s)
=== RUN   TestConfiguration_nextConfiguration_checkConfiguration
--- PASS: TestConfiguration_nextConfiguration_checkConfiguration (0.00s)
=== RUN   TestConfiguration_encodeDecodePeers
--- PASS: TestConfiguration_encodeDecodePeers (0.00s)
=== RUN   TestConfiguration_encodeDecodeConfiguration
--- PASS: TestConfiguration_encodeDecodeConfiguration (0.00s)
=== RUN   TestDiscardSnapshotStoreImpl
--- PASS: TestDiscardSnapshotStoreImpl (0.00s)
=== RUN   TestDiscardSnapshotSinkImpl
--- PASS: TestDiscardSnapshotSinkImpl (0.00s)
=== RUN   TestFileSnapshotStoreImpl
--- PASS: TestFileSnapshotStoreImpl (0.00s)
=== RUN   TestFileSnapshotSinkImpl
--- PASS: TestFileSnapshotSinkImpl (0.00s)
=== RUN   TestFileSS_CreateSnapshotMissingParentDir
--- PASS: TestFileSS_CreateSnapshotMissingParentDir (0.14s)
raft_test.go:101: 21:34:33.261773 [INFO] snapshot: Creating new 
snapshot at /tmp/raft068757217/raft335529164/snapshots/3-10-1533504873261.tmp
=== RUN   TestFileSS_CreateSnapshot
--- PASS: TestFileSS_CreateSnapshot (0.50s)
raft_test.go:101: 21:34:33.401289 [INFO] snapshot: Creating new 
snapshot at /tmp/raft997309883/snapshots/3-10-1533504873401.tmp
raft_test.go:101: 21:34:33.534238 [WARN] snapshot: Found temporary 
snapshot: 3-10-1533504873401.tmp
=== RUN   TestFileSS_CancelSnapshot
--- PASS: TestFileSS_CancelSnapshot (0.13s)
raft_test.go:101: 21:34:33.899206 [INFO] snapshot: Creating new 
snapshot at /tmp/raft437327838/snapshots/3-10-1533504873899.tmp
=== RUN   TestFileSS_Retention
--- PASS: TestFileSS_Retention (2.67s)
raft_test.go:101: 21:34:34.032449 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-10-1533504874032.tmp
raft_test.go:101: 21:34:34.591751 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-11-1533504874591.tmp
raft_test.go:101: 21:34:35.192120 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-12-1533504875192.tmp
raft_test.go:101: 21:34:35.691391 [INFO] snapshot: reaping snapshot 
/tmp/raft011354021/snapshots/3-10-1533504874032
raft_test.go:101: 21:34:35.691859 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-13-1533504875691.tmp
raft_test.go:101: 21:34:36.206487 [INFO] snapshot: reaping snapshot 
/tmp/raft011354021/snapshots/3-11-1533504874591
raft_test.go:101: 21:34:36.206936 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-14-1533504876206.tmp
raft_test.go:101: 21:34:36.703417 [INFO] snapshot: reaping snapshot 

Bug#907761: etcd-fs: FTBFS in buster/sid (cannot use file (type *etcdFile) as type nodefs.File in return argument)

[Santiago Vila]

Package: src:etcd-fs
Version: 0.0+git20140621.0.395eacb-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --buildsystem=golang --with=golang --builddirectory=_build
   dh_update_autotools_config -a -O--buildsystem=golang 
-O--builddirectory=_build
   dh_autoreconf -a -O--buildsystem=golang -O--builddirectory=_build
   dh_auto_configure -a -O--buildsystem=golang -O--builddirectory=_build
   dh_auto_build -a -O--buildsystem=golang -O--builddirectory=_build
cd _build && go install 
-gcflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 
-asmflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 -v -p 1 github.com/xetorthio/etcd-fs github.com/xetorthio/etcd-fs/src/etcdfs
github.com/hanwen/go-fuse/splice
golang.org/x/sys/unix
github.com/hanwen/go-fuse/fuse
github.com/hanwen/go-fuse/fuse/nodefs
github.com/hanwen/go-fuse/fuse/pathfs
github.com/coreos/go-etcd/etcd
github.com/xetorthio/etcd-fs/src/etcdfs
# github.com/xetorthio/etcd-fs/src/etcdfs
src/github.com/xetorthio/etcd-fs/src/etcdfs/file.go:21:3: cannot use file (type 
*etcdFile) as type nodefs.File in return argument:
*etcdFile does not implement nodefs.File (missing GetLk method)
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 
-asmflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 -v -p 1 github.com/xetorthio/etcd-fs github.com/xetorthio/etcd-fs/src/etcdfs 
returned exit code 2
make: *** [debian/rules:12: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The above error also happens here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/etcd-fs.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#907762: postbooks: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:postbooks
Version: 4.11.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --builddirectory=. --parallel
   dh_update_autotools_config -a -O--builddirectory=. -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
# FIXME: find will not fail on error!
find . -name '*.ts' -exec lrelease {} \;
Updating './share/dict/xTuple.ja.qm'...
Generated 12957 translation(s) (10490 finished and 2467 unfinished)
Ignored 8016 untranslated source text(s)
Updating './share/dict/xTuple.fr_ca.qm'...
Generated 17547 translation(s) (15814 finished and 1733 unfinished)
Ignored 3424 untranslated source text(s)
Updating './share/dict/xTuple.et_ee.qm'...

[... snipped ...]

 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note:   template 
argument deduction/substitution failed:
adjustmentTrans.cpp:34:89: note:   candidate expects 3 arguments, 4 provided
   connect(_adjustmentTypeGroupInt,SIGNAL(buttonClicked(int)), this, 
SLOT(sPopulateQty()));

 ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QAction:1,
 from guiclient.h:14,
 from adjustmentTrans.h:14,
 from adjustmentTrans.cpp:11:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: candidate: 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType) [with Func1 = const char*; Func2 = const char*]':
adjustmentTrans.cpp:34:89:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: error: no type named 
'type' in 'struct std::enable_if'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note:   template 
argument deduction/substitution failed:
adjustmentTrans.cpp:34:89: note:   candidate expects 3 arguments, 4 provided
   connect(_adjustmentTypeGroupInt,SIGNAL(buttonClicked(int)), this, 
SLOT(sPopulateQty()));

 ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QAction:1,
 from guiclient.h:14,
 from adjustmentTrans.h:14,
 from adjustmentTrans.cpp:11:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 

Bug#907760: hgview FTBFS with mercurial 4.7

[Adrian Bunk]

Source: hgview
Version: 1.9.0-1.1
Severity: serious
Tags: buster sid ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hgview.html

...
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
dh_auto_clean: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_clean: This feature will be removed in compat 12.
python setup.py clean -a
Traceback (most recent call last):
  File "setup.py", line 60, in 
from hgviewlib.__pkginfo__ import modname, version, license, description, \
  File "/build/1st/hgview-1.9.0/hgviewlib/__init__.py", line 26, in 
demandimport.ignore.append('roman')
AttributeError: 'module' object has no attribute 'ignore'
dh_auto_clean: python setup.py clean -a returned exit code 1
make: *** [debian/rules:18: clean] Error 1

Processed: affects 906355

[Debian Bug Tracking System]

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

> affects 906355 src:form-history-control
Bug #906355 [mozilla-devscripts] dh_webext: SyntaxError: invalid syntax
Added indication that 906355 affects src:form-history-control
> thanks
Stopping processing here.

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

Processed: Re: dh_webext: SyntaxError: invalid syntax

[Debian Bug Tracking System]

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

> affects 906355 form-history-control
Bug #906355 [mozilla-devscripts] dh_webext: SyntaxError: invalid syntax
Added indication that 906355 affects form-history-control
>
End of message, stopping processing here.

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

Processed: dh_webext: SyntaxError: invalid syntax

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 2.0.3.2+dfsg-1
Bug #906355 [src:form-history-control] form-history-control: FTBFS in 
buster/sid (SyntaxError: invalid syntax)
No longer marked as found in versions form-history-control/2.0.3.2+dfsg-1.
> reassign -1 mozilla-devscripts
Bug #906355 [src:form-history-control] form-history-control: FTBFS in 
buster/sid (SyntaxError: invalid syntax)
Bug reassigned from package 'src:form-history-control' to 'mozilla-devscripts'.
Ignoring request to alter found versions of bug #906355 to the same values 
previously set
Ignoring request to alter fixed versions of bug #906355 to the same values 
previously set
> found -1 mozilla-devscripts/0.49
Bug #906355 [mozilla-devscripts] form-history-control: FTBFS in buster/sid 
(SyntaxError: invalid syntax)
Marked as found in versions mozilla-devscripts/0.49.
> retitle -1 dh_webext: SyntaxError: invalid syntax
Bug #906355 [mozilla-devscripts] form-history-control: FTBFS in buster/sid 
(SyntaxError: invalid syntax)
Changed Bug title to 'dh_webext: SyntaxError: invalid syntax' from 
'form-history-control: FTBFS in buster/sid (SyntaxError: invalid syntax)'.

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

Bug#906355: dh_webext: SyntaxError: invalid syntax

[Juhani Numminen]

Control: notfound -1 2.0.3.2+dfsg-1
Control: reassign -1 mozilla-devscripts
Control: found -1 mozilla-devscripts/0.49
Control: retitle -1 dh_webext: SyntaxError: invalid syntax

On Fri, 17 Aug 2018 11:19:38 + Santiago Vila  wrote:> I 
tried to build this package in buster but it failed:
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with webext
>dh_update_autotools_config -i
>dh_autoreconf -i
>create-stamp debian/debhelper-build-stamp
>  fakeroot debian/rules binary-indep
> dh binary-indep --with webext
>dh_testroot -i
>dh_prep -i
>debian/rules override_dh_webext
> make[1]: Entering directory '/<>/form-history-control-2.0.3.2+dfsg'
> dh_webext . form-history-control
>   File "/usr/bin/dh_webext", line 64
> print(self_script + ":", *args)
>  ^
> SyntaxError: invalid syntax
[...]
> The build was made with "dpkg-buildpackage -A" in my autobuilder.
> Most probably, it also fails here in reproducible builds:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/form-history-control.html

Dear maintainer,

Reassigning to mozilla-devscripts since dh_webext causes the FTBFS
in form-history-control.

Trying to invoke dh_webext on my system running testing looks like this:

$ dh_webext
  File "/usr/bin/dh_webext", line 64
print(self_script + ":", *args)
 ^
SyntaxError: invalid syntax

$ dh_webext --help
  File "/usr/bin/dh_webext", line 64
print(self_script + ":", *args)
 ^
SyntaxError: invalid syntax

Python 3 interpreter works a bit better:

$ python3 /usr/bin/dh_webext
usage: dh_webext [-h] [-p PACKAGE] [-I ARG] [-v] PATH [NAME]
dh_webext: error: the following arguments are required: PATH

$ python3 /usr/bin/dh_webext --help
usage: dh_webext [-h] [-p PACKAGE] [-I ARG] [-v] PATH [NAME]

Debhelper command to install an unpacked WebExtension

positional arguments:
  PATH  Path to the main directory. (Default: .)
  NAME  Short name of the extension.

optional arguments:
  -h, --helpshow this help message and exit
  -p PACKAGE, --package PACKAGE
calculate substvars only for the specified PACKAGE
  -I ARG, --dh-install-arg ARG
extra arguments to pass to dh_install
  -v, --verbose print more information


With best regards,
Juhani

Bug#907759: taopm in unstable is broken

[Adrian Bunk]

Package: taopm
Version: 1.0-4
Severity: serious

$ tao test

|Tao (c) 1996-2000 Mark Pearson|
| Sound Synthesis with Physical Models |


Parsing "test.tao"

Error in line 3 of "test.tao": 
Circle c(800 Hz
 ^
If this error message doesn't help, try checking
for missing ;'s or ...'s on, or just before line 3
/usr/bin/tao: 113: /usr/bin/tao: Syntax error: Bad fd number
$ 


Works after downgrading the to package in stretch.

Bug#789129: closed by Tiago Bortoletto Vaz (Bug#789129: fixed in taopm 1.0-4)

[Adrian Bunk]

Control: reopen -1

On Tue, Jul 31, 2018 at 12:09:05PM +, Debian Bug Tracking System wrote:
>...
>  taopm (1.0-4) unstable; urgency=medium
>  .
>* Depends on libxi-dev. Thanks to Philip Chung & John O'Hagan.
>  (Closes: #789129)
>...

This added a build dependency, not a dependency.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: Bug#789129 closed by Tiago Bortoletto Vaz (Bug#789129: fixed in taopm 1.0-4)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #789129 {Done: Tiago Bortoletto Vaz } [taopm] taopm: 
Taopm instruments fail to compile
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions taopm/1.0-4.

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

Bug#907718: python-dateutil breaks python-vobject autopkgtest

[Guido Günther]

Hi,
On Sat, Sep 01, 2018 at 02:54:25PM +0300, Adrian Bunk wrote:
> Control: reassign -1 src:python-dateutil 2.7.3-1
> Control: retitle -1 python-dateutil: RRULE UNTIL values must be specified in 
> UTC when DTSTART is timezone-aware
> Control: severity -1 serious
> Control: affects -1 python-dateutil python3-dateutil src:python-vobject 
> src:python-icalendar

Thanks!

> 
> On Fri, Aug 31, 2018 at 09:41:32PM +0200, Paul Gevers wrote:
> > Source: python-dateutil, python-vobject
> > Control: found -1 python-dateutil/2.7.3-1
> > Control: found -1 python-vobject/0.9.5-2
> > X-Debbugs-CC: debian...@lists.debian.org
> > User: debian...@lists.debian.org
> > Usertags: breaks needs-update
> > 
> > Dear maintainers,
> > 
> > With a recent upload of python-dateutil the autopkgtest of
> > python-vobject started to fail in testing. I copied some of the output
> > below.
> >...
> 
> This also causes FTBFS, the first two seen are:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-icalendar.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-vobject.html
> 
> I strongly suspect that there will also be runtime issues with other 
> packages using python-dateutil currently in stretch and buster, so even 
> in case this is considered a bug in reverse dependencies there will 
> still be Breaks required in python{,3}-dateutil against packages in 
> stretch and buster that got broken (unless it was only a broken test).

This was broken by efba12d3 due to

https://github.com/dateutil/dateutil/issues/620

so we likely want reverse deps to catch up and fix this.
Cheers,
 -- Guido

Processed: severity of 789129 is serious

[Debian Bug Tracking System]

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

> severity 789129 serious
Bug #789129 {Done: Tiago Bortoletto Vaz } [taopm] taopm: 
Taopm instruments fail to compile
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 907754

[Debian Bug Tracking System]

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

> tags 907754 + ftbfs
Bug #907754 [src:webdis] webdis: FTBFS on i386, mips64el
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#907757: libedataserverui1.2-dev: missing dependency on libecal1.2-dev

[Adrian Bunk]

Package: libedataserverui1.2-dev
Version: 3.29.92-1
Severity: serious
Control: affects -1 src:gnome-contacts

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-contacts.html

...
Called `/usr/bin/pkg-config --cflags libedataserverui-1.2` -> 1


meson.build:44:0: ERROR:  Could not generate cargs for libedataserverui-1.2:


dh_auto_configure: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/gnome-contacts 
-Dwith-cheese=yes returned exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2

Processed: libedataserverui1.2-dev: missing dependency on libecal1.2-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gnome-contacts
Bug #907757 [libedataserverui1.2-dev] libedataserverui1.2-dev: missing 
dependency on libecal1.2-dev
Added indication that 907757 affects src:gnome-contacts

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

Processed: block 907616 with 907664

[Debian Bug Tracking System]

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

> block 907616 with 907664
Bug #907616 [src:budgie-desktop] budgie-desktop: needs modification for Mutter 
3.30
907616 was not blocked by any bugs.
907616 was blocking: 906015
Added blocking bug(s) of 907616: 907664
> thanks
Stopping processing here.

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

Bug#902721: marked as done (CVE-2018-1000539)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 12:47:08 +
with message-id 
and subject line Bug#902721: fixed in ruby-json-jwt 1.6.2-1+deb9u1
has caused the Debian Bug report #902721,
regarding CVE-2018-1000539
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.)


-- 
902721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-json-jwt
Severity: grave
Tags: security

This was assigned CVE-2018-1000539:
https://github.com/nov/json-jwt/pull/62
https://github.com/nov/json-jwt/commit/3393f394f271c87bd42ec23c300727b4437d1638

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: ruby-json-jwt
Source-Version: 1.6.2-1+deb9u1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-json-jwt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 18 Aug 2018 23:32:06 +0530
Source: ruby-json-jwt
Binary: ruby-json-jwt
Architecture: source all
Version: 1.6.2-1+deb9u1
Distribution: stretch-security
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-json-jwt - JSON Web Token and its family in Ruby
Closes: 902721
Changes:
 ruby-json-jwt (1.6.2-1+deb9u1) stretch-security; urgency=medium
 .
   * Fixes: CVE-2018-1000539 (Closes: #902721)
Checksums-Sha1:
 414b750ecdbb9f18bca32aff6ce6a40e807b9ed4 2221 ruby-json-jwt_1.6.2-1+deb9u1.dsc
 da6c80c938ee3bff65d86928eceb78e68f0ccbc3 21870 ruby-json-jwt_1.6.2.orig.tar.gz
 42b81bba0d98b5e291d6b3344c5d678b680f5ac3 3180 
ruby-json-jwt_1.6.2-1+deb9u1.debian.tar.xz
 37a7913df92d0c377d9e1821e4d1e6ad0c1e 9160 
ruby-json-jwt_1.6.2-1+deb9u1_all.deb
 9310a7786c747006b79f7ad8268de0de360511d6 7600 
ruby-json-jwt_1.6.2-1+deb9u1_amd64.buildinfo
Checksums-Sha256:
 b0efdf4b17e4359dab6b172ddfec93483fcad31e46027b41fb4d52c39991e441 2221 
ruby-json-jwt_1.6.2-1+deb9u1.dsc
 bc10d11254d60aa84c539d2a69ffcd2611535dc42120a0e6a242f63d4bcc7d7c 21870 
ruby-json-jwt_1.6.2.orig.tar.gz
 ddfed631888079c0887b9fa43f1f24512594004ab65fe442b19f19ae5c956d25 3180 
ruby-json-jwt_1.6.2-1+deb9u1.debian.tar.xz
 02a4fcb7e56562f40c2b4808e4bfd3e27b765cb78a844dd4a97377d3751a95c2 9160 
ruby-json-jwt_1.6.2-1+deb9u1_all.deb
 d57f5fe221e41bb29f0a0a096e7dad1c83397c9734c60d6be0f67c028598316d 7600 
ruby-json-jwt_1.6.2-1+deb9u1_amd64.buildinfo
Files:
 003bf9b15f417749d56a10b19ea146b3 2221 ruby optional 
ruby-json-jwt_1.6.2-1+deb9u1.dsc
 aecdd332419f64d9aca527ddbf946a93 21870 ruby optional 
ruby-json-jwt_1.6.2.orig.tar.gz
 2879d7b377e3aac09cca241f346a45c2 3180 ruby optional 
ruby-json-jwt_1.6.2-1+deb9u1.debian.tar.xz
 431b4c72b1490d70a95ae110fc81a6a8 9160 ruby optional 
ruby-json-jwt_1.6.2-1+deb9u1_all.deb
 38d3b4cb30a31df599605d65dfb58f1b 7600 ruby optional 
ruby-json-jwt_1.6.2-1+deb9u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlt4ZvsACgkQzh+cZ0US
wirUzg/8CE6Z/V/WluVi0Yiu46gDELGjlTdS56Y1AMOwgbwG8q0fzGghP2cmHe7/
1xjTAWQ6TK8AhnCuYm3rJQ81x/3vWFHwPioSWhGQXSjbvTBjV3z06gWYQ+ipl0tT
oiffo1NRpbAg57IPAxxDci3P1rwqAKX3O+wzjNIDIySOkj04ICTUM0GplgQlj907
yCEtC0QYsS7x0Bkf47nobq+JdGgnts1XPNgp+oteGN7ITui9dDIf1kAbFyDEMgoO
FAVdUyQwqzVF671qxdegc2zqwcj1ZdmTlRj2pe7ZHtD4ID6Ypw2qiQFmJHKMXLaX
imtLgDvtr+aZrEC75QlYA4LgskKcjtCwpcvTHD+kPMdXfI8fcKfvhbqWRdN3tb6v
3hKQTVOvUFsawnN1lfm4crv+M7VSjmiogo/k0yZiNxbUj9fGqVyE63qWNoqspTHI
k23Vf0P5W14Kn9VpKoI9TFOzcQjKxaKVuhtoj3A61kyurf1D9W9RyDDLl6CSTKbu
M4XbQLo3AUbgN/hjRBNweSqp0rlqtJf1UqEO3vX2Tz0xq6WyZTw3S2GiZwlzEYGN
LBHTiYHBkmHwwhG1QtlivDJ4c5Wb7aE1QKT+ZV75FURwtCDSW22jtVYci3RUCZOO
zbsIzpzjlfYiGL7ucKJAlgMTINENi+eVmYtRFfFxChZrqgS9dc8=
=z3QF
-END PGP SIGNATURE End Message ---

Bug#894970: marked as done (tomcat8: missing Depends on libservlet3.1-java)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 12:47:10 +
with message-id 
and subject line Bug#867247: fixed in tomcat8 8.5.14-1+deb9u3
has caused the Debian Bug report #867247,
regarding tomcat8: missing Depends on libservlet3.1-java
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.)


-- 
867247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tomcat8
Version: 8.5.14-1+deb9u2
Severity: grave
Justification: renders package unusable

Without libservlet3.1-java installed, deploying a simple WAR fails:

05-Apr-2018 16:25:18.310 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /var/lib/tomcat8/webapps/ROOT
05-Apr-2018 16:25:19.252 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/el-api-3.0.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/el-api-3.0.jar (No such file or 
directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:225)
at java.util.zip.ZipFile.(ZipFile.java:155)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at 
org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1898)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1126)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5105)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at 
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1107)
at 
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1841)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

05-Apr-2018 16:25:19.256 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/jsp-api-2.3.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/jsp-api-2.3.jar (No such file 
or directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:225)
at java.util.zip.ZipFile.(ZipFile.java:155)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at 
org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1898)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1126)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5105)

Bug#867247: marked as done (tomcat8: Package tomcat8 or libtomcat8-java should depends package libservlet3.1-java)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 12:47:10 +
with message-id 
and subject line Bug#867247: fixed in tomcat8 8.5.14-1+deb9u3
has caused the Debian Bug report #867247,
regarding tomcat8: Package tomcat8 or libtomcat8-java should depends package 
libservlet3.1-java
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.)


-- 
867247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tomcat8
Version: 8.5.16-1
Severity: normal
Tags: patch

Dear Tomcat Maintainers,

t the moment a whole installation of the tomcat8 packages does not require the 
installation of libservlet3.1-java caused by missing of a dependency within the 
control file.

The following error messages occured in catalina.out after Tomcat has been 
started.

5-Jul-2017 05:44:03.147 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/el-api-3.0.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/el-api-3.0.jar (No such file or 
directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:219)
at java.util.zip.ZipFile.(ZipFile.java:149)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262)
at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:104)
at 
org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:101)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at 
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1144)
at 
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1878)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

05-Jul-2017 05:44:03.147 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/jsp-api-2.3.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/jsp-api-2.3.jar (No such file 
or directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:219)
at java.util.zip.ZipFile.(ZipFile.java:149)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262)
at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:104)
at 
org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:101)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at 

Bug#877457: marked as done (trafficserver-dev: missing Depends: trafficserver (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 12:47:11 +
with message-id 
and subject line Bug#877457: fixed in trafficserver 7.0.0-6+deb9u2
has caused the Debian Bug report #877457,
regarding trafficserver-dev: missing Depends: trafficserver (= 
${binary:Version})
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.)


-- 
877457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trafficserver-dev
Version: 7.0.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m23.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/trafficserver/libtsutil.so -> libtsutil.so.7.0.0
  /usr/lib/trafficserver/libtsmgmt.so -> libtsmgmt.so.7.0.0
  /usr/lib/trafficserver/libtsconfig.so -> libtsconfig.so.7.0.0
  /usr/lib/trafficserver/libatscppapi.so -> libatscppapi.so.7.0.0


Given that these are in a package subdirectory, maybe they are not intended
to be used by other packages and should not have .so links in the -dev
package at all.

Otherwise if would probably be useful to split out to shared libraries
into (a) separate package(s).


cheers,

Andreas


trafficserver-dev_7.0.0-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 7.0.0-6+deb9u2

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

Debian distribution maintenance software
pp.
Jean Baptiste Favre  (supplier of updated trafficserver 
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, 29 Aug 2018 16:01:52 +0200
Source: trafficserver
Binary: trafficserver trafficserver-experimental-plugins trafficserver-dev
Architecture: source amd64
Version: 7.0.0-6+deb9u2
Distribution: stretch-security
Urgency: high
Maintainer: Aron Xu 
Changed-By: Jean Baptiste Favre 
Description:
 trafficserver - fast, scalable and extensible HTTP/1.1 compliant caching proxy 
se
 trafficserver-dev - Apache Traffic Server Software Developers Kit (SDK)
 trafficserver-experimental-plugins - experimental plugins for Apache Traffic 
Server
Closes: 877457
Changes:
 trafficserver (7.0.0-6+deb9u2) stretch-security; urgency=high
 .
   * Add patches for CVE-2108-1318, CVE-2108-8004, CVE-2108-8005, CVE-2108-8040
   * Fixes trafficserver-dev dependencies. Closes: #877457
Checksums-Sha1:
 16d986c9d9efd3e67161fd4fa5eb4b8cb337bea0 2705 trafficserver_7.0.0-6+deb9u2.dsc
 88a0c6a83fe99c6c67206464c526df2295c61128 1201752 
trafficserver_7.0.0-6+deb9u2.debian.tar.xz
 6fb5023dd5fa598cfca86697a849f5df7153fd4e 38221920 
trafficserver-dbgsym_7.0.0-6+deb9u2_amd64.deb
 57d289ee05119e4b8097c208af6706c5dae23fda 1082380 
trafficserver-dev_7.0.0-6+deb9u2_amd64.deb
 c399b4cd1c8c7d512df25a564f3d640b9a37c7c7 2263938 
trafficserver-experimental-plugins-dbgsym_7.0.0-6+deb9u2_amd64.deb
 eb91a362e1f312df303ae3efbb260abe918f058e 289538 
trafficserver-experimental-plugins_7.0.0-6+deb9u2_amd64.deb
 3f9d4eb52cb0cde687f88fcbc1204cfa6f5c1bd8 15499 
trafficserver_7.0.0-6+deb9u2_amd64.buildinfo
 7528a3d135d143194dc10d23b5d983fbbfe25d52 2718222 
trafficserver_7.0.0-6+deb9u2_amd64.deb
Checksums-Sha256:
 25b65a5c37f3c08737e609a3068b25e637f3c353f4737ba4988b603d8cddeb42 2705 
trafficserver_7.0.0-6+deb9u2.dsc
 371d483e0e2be718e0e122e0a6b5fc2b1e93b7b27741e8bf932d941eb6122f2b 1201752 
trafficserver_7.0.0-6+deb9u2.debian.tar.xz
 7a171da20b1e6f706bb275989a1510c709f55d440fe697c742f74d70694adc5d 38221920 
trafficserver-dbgsym_7.0.0-6+deb9u2_amd64.deb
 31cbe48dbda90e3b98e7a0fc76106552d7dd764123dfdbea85322fc474e3504c 1082380 
trafficserver-dev_7.0.0-6+deb9u2_amd64.deb
 0e46121725bc5a7125b647381ef23451b699d2b93106948b7caf388e5f2154c9 2263938 
trafficserver-experimental-plugins-dbgsym_7.0.0-6+deb9u2_amd64.deb
 389fe322e983a673aad2bc2eb1d4ec71d11ab9e20851fc60efe3ab334fe6d9a3 289538 
trafficserver-experimental-plugins_7.0.0-6+deb9u2_amd64.deb
 

Bug#907754: webdis: FTBFS on i386, mips64el

[Mattia Rizzolo]

Source: webdis
Version: 0.1.4+dfsg-1
Severity: serious

Dear maintainer,

the package FTBFS on the buildds on i386 and mips64el:

https://buildd.debian.org/status/fetch.php?pkg=webdis=i386=0.1.4%2Bdfsg-1=1535395313=0
|...
|   debian/rules override_dh_auto_test
|make[1]: Entering directory '/<>/webdis-0.1.4+dfsg'
|/<>/webdis-0.1.4+dfsg/debian/test.sh /usr/bin/make test
|Generating config files..
|Starting redis-server..
|25930:C 27 Aug 18:41:41.949 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
|25930:C 27 Aug 18:41:41.950 # Redis version=4.0.11, bits=32, commit=, 
modified=0, pid=25930, just started
|25930:C 27 Aug 18:41:41.950 # Configuration loaded
|Starting webdis..
|webdis is listening on port 44739
|Running test commands: /usr/bin/make test
|make[2]: Entering directory '/<>/webdis-0.1.4+dfsg'
|python tests/basic.py
|..EE..
|==
|ERROR: test_list (__main__.TestCustom)
|List responses with custom format
|--
|Traceback (most recent call last):
|  File "tests/basic.py", line 95, in test_list
|self.query('RPUSH/hello/a/b/c')
|  File "tests/basic.py", line 20, in query
|return urllib2.urlopen(r)
|  File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
|return opener.open(url, data, timeout)
|  File "/usr/lib/python2.7/urllib2.py", line 435, in open
|response = meth(req, response)
|  File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
|'http', request, response, code, msg, hdrs)
|  File "/usr/lib/python2.7/urllib2.py", line 473, in error
|return self._call_chain(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
|result = func(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
|raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
|HTTPError: HTTP Error 503: Service Unavailable
|
|==
|ERROR: test_separator (__main__.TestCustom)
|Separator in list responses with custom format
|--
|Traceback (most recent call last):
|  File "tests/basic.py", line 103, in test_separator
|self.query('RPUSH/hello/a/b/c')
|  File "tests/basic.py", line 20, in query
|return urllib2.urlopen(r)
|  File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
|return opener.open(url, data, timeout)
|  File "/usr/lib/python2.7/urllib2.py", line 435, in open
|response = meth(req, response)
|  File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
|'http', request, response, code, msg, hdrs)
|  File "/usr/lib/python2.7/urllib2.py", line 473, in error
|return self._call_chain(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
|result = func(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
|raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
|HTTPError: HTTP Error 503: Service Unavailable
|
|--
|Ran 22 tests in 0.062s
|
|FAILED (errors=2)
|make[2]: *** [Makefile:66: test] Error 1
|make[2]: Leaving directory '/<>/webdis-0.1.4+dfsg'
|Shutting down webdis..
|Stopped webdis (pid 25933).
|Shutting down redis-server..
|Stopped redis-server (pid 25931).
|make[1]: *** [debian/rules:39: override_dh_auto_test] Error 2
|make[1]: Leaving directory '/<>/webdis-0.1.4+dfsg'
|make: *** [debian/rules:19: binary-arch] Error 2
|dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


https://buildd.debian.org/status/fetch.php?pkg=webdis=mips64el=0.1.4%2Bdfsg-1=1535805316=0
|...
|   debian/rules override_dh_auto_test
|make[1]: Entering directory '/<>/webdis-0.1.4+dfsg'
|/<>/webdis-0.1.4+dfsg/debian/test.sh /usr/bin/make test
|Generating config files..
|Starting redis-server..
|6182:C 01 Sep 10:04:49.962 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
|6182:C 01 Sep 10:04:49.962 # Redis version=4.0.11, bits=64, commit=, 
modified=0, pid=6182, just started
|6182:C 01 Sep 10:04:49.962 # Configuration loaded
|Starting webdis..
|webdis is listening on port 44557
|Running test commands: /usr/bin/make test
|make[2]: Entering directory '/<>/webdis-0.1.4+dfsg'
|python tests/basic.py
|..
|--
|Ran 22 tests in 0.273s
|
|OK
|python tests/limits.py
|..
|--
|Ran 2 tests in 2.629s
|
|OK
|./tests/pubsub -p 44557
|E: Build killed with signal TERM after 150 minutes of inactivity


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  

Bug#907752: slick-greeter: lightdm-vala must be build dependency without alternative

[Adrian Bunk]

Source: slick-greeter
Version: 1.2.2-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/slick-greeter.html

...
Making all in src
make[3]: Entering directory '/build/1st/slick-greeter-1.2.2/src'
rm -f logo_generator_vala.stamp && echo stamp > logo_generator_vala.stamp-t
rm -f slick_greeter_vala.stamp && echo stamp > slick_greeter_vala.stamp-t
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac -D HAVE_GTK_3_20_0 --debug 
--pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg 
liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 
--target-glib 2.32  -C logo-generator.vala
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac -D HAVE_GTK_3_20_0 --debug 
--pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg 
liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 
--target-glib 2.32  -C config.vapi fixes.vapi xsync.vapi animate-timer.vala 
background.vala cached-image.vala cairo-utils.vala email-autocompleter.vala 
dash-box.vala dash-button.vala dash-entry.vala fadable.vala fadable-box.vala 
fading-label.vala flat-button.vala greeter-list.vala idle-monitor.vala 
list-stack.vala main-window.vala menu.vala menubar.vala prompt-box.vala 
session-list.vala remote-login-service.vala settings.vala shutdown-dialog.vala 
toggle-box.vala slick-greeter.vala user-list.vala user-prompt-box.vala
error: Package `liblightdm-gobject-1' not found in specified Vala API 
directories or GObject-Introspection GIR directories
Compilation failed: 1 error(s), 0 warning(s)
make[3]: *** [Makefile:968: logo_generator_vala.stamp] Error 1



This is caused by the following in the build dependencies:
   lightdm-vala (>= 1.18.3) | gir1.2-lightdm-1 (>= 1.22)


The package always needs lightdm-vala (and the required version
is already in stable), please remove the gir1.2-lightdm-1
alternative.

Processed: Re: Bug#907718: python-dateutil breaks python-vobject autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:python-dateutil 2.7.3-1
Bug #907718 [src:python-dateutil, src:python-vobject] python-dateutil breaks 
python-vobject autopkgtest
Bug reassigned from package 'src:python-dateutil, src:python-vobject' to 
'src:python-dateutil'.
No longer marked as found in versions python-dateutil/2.7.3-1 and 
python-vobject/0.9.5-2.
Ignoring request to alter fixed versions of bug #907718 to the same values 
previously set
Bug #907718 [src:python-dateutil] python-dateutil breaks python-vobject 
autopkgtest
Marked as found in versions python-dateutil/2.7.3-1.
> retitle -1 python-dateutil: RRULE UNTIL values must be specified in UTC when 
> DTSTART is timezone-aware
Bug #907718 [src:python-dateutil] python-dateutil breaks python-vobject 
autopkgtest
Changed Bug title to 'python-dateutil: RRULE UNTIL values must be specified in 
UTC when DTSTART is timezone-aware' from 'python-dateutil breaks python-vobject 
autopkgtest'.
> severity -1 serious
Bug #907718 [src:python-dateutil] python-dateutil: RRULE UNTIL values must be 
specified in UTC when DTSTART is timezone-aware
Severity set to 'serious' from 'normal'
> affects -1 python-dateutil python3-dateutil src:python-vobject 
> src:python-icalendar
Bug #907718 [src:python-dateutil] python-dateutil: RRULE UNTIL values must be 
specified in UTC when DTSTART is timezone-aware
Added indication that 907718 affects python-dateutil, python3-dateutil, 
src:python-vobject, and src:python-icalendar

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

Bug#907741: marked as done (libefl-all-dev breaks by binNMU)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 11:34:13 +
with message-id 
and subject line Bug#907741: fixed in efl 1.20.7-7
has caused the Debian Bug report #907741,
regarding libefl-all-dev breaks by binNMU
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.)


-- 
907741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libefl-all-dev
Version: 1.20.7-6
Severity: serious

# apt-get install libecore-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libecore-dev : Depends: libefl-all-dev (>= 1.20.7-6) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.
#


Breaks+Replaces on (<< ${binary:Version}) is wrong when
the broken package is binary-all.

And these versions shouldn't be generated here at all,
these should be the fixed versions when the contents
moved to libefl-all-dev.
--- End Message ---
--- Begin Message ---
Source: efl
Source-Version: 1.20.7-7

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated efl 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: Sat, 01 Sep 2018 12:07:40 +0200
Source: efl
Binary: libeina1a libeina-bin libeina-dev libeet-dev libeet1 libeet-bin 
libelocation1 libephysics1 libevas1 libevas-bin libevas-dev libevas1-engines-x 
libevas1-engines-fb libevas1-engines-drm libevas1-engines-wayland libecore1 
libecore-audio1 libecore-avahi1 libecore-con1 libecore-drm2-1 libecore-evas1 
libecore-fb1 libecore-file1 libecore-imf1 libecore-input1 libecore-ipc1 
libecore-wl2-1 libecore-x1 libecore-bin libecore-dev libector1 libefl-all-dev 
libefreet1a libefreet-bin libefreet-dev libembryo-dev libembryo1 libembryo-bin 
libedje-bin libedje1 libedje-dev libeio1 libeio-dev libeeze1 libeeze-bin 
libeeze-dev libelua1 libelua-bin libemile1 libemotion1 libemotion-dev 
libethumb1 libethumb-client1 libethumb-client-bin libethumb-dev libeolian1 
libelput1 efl-doc libelementary1 libelementary-bin libelementary-data 
libelementary-dev libevas-loaders libemotion-players
Architecture: source
Version: 1.20.7-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Pkg-e Team 
Changed-By: Andreas Metzler 
Closes: 907741
Description: 
 efl-doc- Documentation for the Enlightenment Foundation Libraries
 libecore1  - Core abstraction layer for enlightenment DR 0.17
 libecore-audio1 - Ecore functions for audio playback and recording
 libecore-avahi1 - Ecore functions for dealing with Avahi mDNS/DNS-SD
 libecore-bin - Core abstraction layer for enlightenment DR 0.17 binary 
utilities
 libecore-con1 - Ecore Connection Library
 libecore-dev - transitional EFL development package
 libecore-drm2-1 - Ecore functions for dealing with DRM2
 libecore-evas1 - Ecore Evas Wrapper Library
 libecore-fb1 - Ecore frame buffer system functions
 libecore-file1 - Ecore File Library
 libecore-imf1 - Ecore Input Method Framework module
 libecore-input1 - Ecore input module
 libecore-ipc1 - Ecore inter-process communication functions
 libecore-wl2-1 - Ecore functions for dealing with Wayland
 libecore-x1 - Ecore functions for dealing with the X Window System
 libector1  - Library that provides vector graphics capabilities for EFL
 libedje1   - Graphical layout and animation library
 libedje-bin - Various binaries for use with libedje
 libedje-dev - transitional EFL development package
 libeet1- Enlightenment DR17 file chunk reading/writing library
 libeet-bin - Enlightenment DR17 file chunk reading/writing utility
 libeet-dev - transitional EFL development package
 libeeze1 

Processed: bug 907431 is forwarded to https://github.com/mjambon/cppo/issues/61

[Debian Bug Tracking System]

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

> forwarded 907431 https://github.com/mjambon/cppo/issues/61
Bug #907431 [cppo] cppo's testsuite fails on arm{el,hf} and ppc64el
Set Bug forwarded-to-address to 'https://github.com/mjambon/cppo/issues/61'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#902631: devscripts: CI fails in unstable due to Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #902631 [src:astroid] astroid: Not compatible with Python 3.7
Added tag(s) patch.

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

Bug#902631: devscripts: CI fails in unstable due to Python 3.7

[Nicolas Dandrimont]

Control: tags -1 + patch

* Thomas Goirand  [2018-08-25 22:02:51 +0200]:

> Hi Sando,
> 
> I do support uploading 2 source packages, one for py2, and one for py3.
> This is the most reasonable solution. Worst case, if that cannot be
> done, then we got to move forward and restore Py3 support (and
> eventually drop Py2), but I prefer the former solution.
> 
> The issue has been opened for nearly 2 months now, with nearly a month
> without any news, and this makes me a bit nervous, as I need the py3
> support to be restored.
> 
> What's holding you off more?

Hi,

As a proof of concept I've gone and done the changes needed to pull this off on
a fork of the git repo in my personal namespace.

https://salsa.debian.org/olasd/astroid

The astroid source package is in the master / upstream branches;
The astroid2 source package is in the astroid2 / upstream-1.x branches.

I had to do some wrangling of the astroid source package, to convert it to
pybuild, because the default setuptools buildsystem only works when python2 is
in the build depends.

I could see a point in splitting the git repositories but I don't think that's
very critical.

I'm happy to do a NMU in a week so that we can move forward with the split
package plan.

Cheers,
-- 
Nicolas Dandrimont

We come to bury DOS, not to praise it.
(Paul Vojta, vo...@math.berkeley.edu, paraphrasing a quote of Shakespeare)


signature.asc
Description: PGP signature

Bug#906775: marked as done (hamlib: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 10:33:58 +
with message-id 
and subject line Bug#906426: fixed in automake-1.16 1:1.16.1-1.1
has caused the Debian Bug report #906426,
regarding hamlib: FTBFS in buster/sid (makeinfo: command not found)
to be marked as done.

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

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


-- 
906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hamlib
Version: 3.1-8
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh_testdir
dh_autoreconf
aclocal: overwriting 'macros/libtool.m4' with '/usr/share/aclocal/libtool.m4'
aclocal: overwriting 'macros/ltoptions.m4' with 
'/usr/share/aclocal/ltoptions.m4'

[... snipped ...]

libtool: warning: '../src/libhamlib.la' has not been installed in '/usr/lib'
libtool: install: /usr/bin/install -c .libs/rotctld 
/<>/debian/tmp/usr/bin/rotctld
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 ../../tests/rigctl.1 ../../tests/rigctld.1 
../../tests/rigmem.1 ../../tests/rigsmtr.1 ../../tests/rigswr.1 
../../tests/rotctl.1 ../../tests/rotctld.1 
'/<>/debian/tmp/usr/share/man/man1'
make[3]: Leaving directory '/<>/build-2.7/tests'
make[2]: Leaving directory '/<>/build-2.7/tests'
Making install in doc
make[2]: Entering directory '/<>/build-2.7/doc'
Updating ../../doc/version.texi
make[3]: Entering directory '/<>/build-2.7/doc'
make[3]: Nothing to be done for 'install-exec-am'.
rm -rf hamlib.htp
if /bin/bash /<>/build-aux/missing makeinfo --html --no-headers 
--no-split  -I ../../doc \
 -o hamlib.htp ../../doc/hamlib.texi; \
then \
  rm -rf hamlib.html && mv hamlib.htp hamlib.html; \
else \
  rm -rf hamlib.htp; exit 1; \
fi
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[3]: *** [Makefile:499: hamlib.html] Error 1
make[3]: Leaving directory '/<>/build-2.7/doc'
make[2]: *** [Makefile:700: install-am] Error 2
make[2]: Leaving directory '/<>/build-2.7/doc'
make[1]: *** [Makefile:577: install-recursive] Error 1
make[1]: Leaving directory '/<>/build-2.7'
make: *** [debian/rules:64: install-base] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hamlib.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: automake-1.16
Source-Version: 1:1.16.1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated automake-1.16 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: Mon, 27 Aug 2018 16:40:12 +0300
Source: automake-1.16
Binary: automake
Architecture: source
Version: 1:1.16.1-1.1
Distribution: unstable
Urgency: high
Maintainer: Eric Dorland 
Changed-By: Adrian Bunk 
Description:
 automake   - Tool for generating GNU Standards-compliant Makefiles
Closes: 906426
Changes:
 automake-1.16 

Bug#906778: marked as done (guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 10:33:58 +
with message-id 
and subject line Bug#906426: fixed in automake-1.16 1:1.16.1-1.1
has caused the Debian Bug report #906426,
regarding guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not 
found)
to be marked as done.

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

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


-- 
906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:guile-gnome-platform
Version: 2.16.4-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
set -e;   mv ./build-aux/config.guess ./build-aux/config.guess.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.guess ./build-aux/config.guess;
set -e;   mv ./build-aux/config.sub ./build-aux/config.sub.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.sub ./build-aux/config.sub;
dh_autoreconf 
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'

[... snipped ...]

Making check in glib
make[4]: Entering directory '/<>/glib/doc/glib'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in guile-gnome-glib.info guile-gnome-glib.info-[0-9] 
guile-gnome-glib.info-[0-9][0-9] guile-gnome-glib.i[0-9] 
guile-gnome-glib.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo   -I . \
 -o guile-gnome-glib.info guile-gnome-glib.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./guile-gnome-glib.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[4]: *** [Makefile:470: guile-gnome-glib.info] Error 127
make[4]: Leaving directory '/<>/glib/doc/glib'
make[3]: *** [Makefile:399: check-recursive] Error 1
make[3]: Leaving directory '/<>/glib/doc'
make[2]: *** [Makefile:513: check-recursive] Error 1
make[2]: Leaving directory '/<>/glib'
make[1]: *** [Makefile:457: check-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113: 
debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-gnome-platform.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: automake-1.16
Source-Version: 1:1.16.1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated automake-1.16 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 

Bug#906426: marked as done (gnuchess: FTBFS: makeinfo: command not found (missing build-dependency on texinfo))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 10:33:58 +
with message-id 
and subject line Bug#906426: fixed in automake-1.16 1:1.16.1-1.1
has caused the Debian Bug report #906426,
regarding gnuchess: FTBFS: makeinfo: command not found (missing 
build-dependency on texinfo)
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.)


-- 
906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuchess
Version: 6.2.5-1
Severity: serious
Tags: ftbfs, patch
Justification: fails to build from source (but built successfully in the past)

Hi,

Building gnuchess in a current sid chroot fails with:


Making check in doc
make[2]: Entering directory '/<>/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/missing makeinfo --version) >/dev/null 2>&1; 
then \
  for f in gnuchess.info gnuchess.info-[0-9] gnuchess.info-[0-9][0-9] gnuchess.i
[0-9] gnuchess.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/missing makeinfo   -I . \
 -o gnuchess.info gnuchess.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./gnuchess.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[2]: *** [Makefile:382: gnuchess.info] Error 127


Same is observed on 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnuchess.html

Adding 'texinfo' to the build dependencies fixes the problem.

Complete build log attached.


-- dam


gnuchess_amd64-2018-08-17T10:32:23Z.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: automake-1.16
Source-Version: 1:1.16.1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated automake-1.16 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: Mon, 27 Aug 2018 16:40:12 +0300
Source: automake-1.16
Binary: automake
Architecture: source
Version: 1:1.16.1-1.1
Distribution: unstable
Urgency: high
Maintainer: Eric Dorland 
Changed-By: Adrian Bunk 
Description:
 automake   - Tool for generating GNU Standards-compliant Makefiles
Closes: 906426
Changes:
 automake-1.16 (1:1.16.1-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Remove 0008-SOURCE_DATE_EPOCH-support-for-mdate-sh.patch which
 broke mdate-sh, thanks to Andreas Metzler. (Closes: #906426)
Checksums-Sha1:
 fe83cee115edf7eb91b977eaebc0ef4dbee61b5c 2229 automake-1.16_1.16.1-1.1.dsc
 8b39560583b0b96cc31791df254f0515bd17d16f 14544 
automake-1.16_1.16.1-1.1.debian.tar.xz
Checksums-Sha256:
 cbde407313f7306389f323ef2ca07e77f9c344b420d3caded3733bced6080014 2229 
automake-1.16_1.16.1-1.1.dsc
 6dc062f382e582e711bba62a5ec9f34e6ac71f62e651a652e630d26e1d2f11c0 14544 
automake-1.16_1.16.1-1.1.debian.tar.xz
Files:
 75e58bc1f9023c5d77d6cb26da6ad103 2229 devel optional 
automake-1.16_1.16.1-1.1.dsc
 8c14f5b46932ac063af41130cc752ebb 14544 devel optional 
automake-1.16_1.16.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAluEBNkACgkQiNJCh6LY

Bug#906790: marked as done (libtasn1-6 FTBFS during arch-only: missing makeinfo)

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 10:33:58 +
with message-id 
and subject line Bug#906426: fixed in automake-1.16 1:1.16.1-1.1
has caused the Debian Bug report #906426,
regarding libtasn1-6 FTBFS during arch-only: missing makeinfo
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.)


-- 
906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtasn1-6
Version: 4.13-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

Doing an arch-only build of libtasn1-6 on amd64 fails. A build log ends
with:

| make[3]: Entering directory '/<>/doc'
| restore=: && backupdir=".am$$" && \
| am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
| rm -rf $backupdir && mkdir $backupdir && \
| if (/bin/bash /<>/build-aux/missing makeinfo --version) 
>/dev/null 2>&1; then \
|   for f in libtasn1.info libtasn1.info-[0-9] libtasn1.info-[0-9][0-9] 
libtasn1.i[0-9] libtasn1.i[0-9][0-9]; do \
| if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
|   done; \
| else :; fi && \
| cd "$am__cwd"; \
| if /bin/bash /<>/build-aux/missing makeinfo -I ../doc  -I . \
|  -o libtasn1.info libtasn1.texi; \
| then \
|   rc=0; \
|   CDPATH="${ZSH_VERSION+.}:" && cd .; \
| else \
|   rc=$?; \
|   CDPATH="${ZSH_VERSION+.}:" && cd . && \
|   $restore $backupdir/* `echo "./libtasn1.info" | sed 's|[^/]*$||'`; \
| fi; \
| rm -rf $backupdir; exit $rc
| /<>/build-aux/missing: line 81: makeinfo: command not found
| WARNING: 'makeinfo' is missing on your system.
|  You should only need it if you modified a '.texi' file, or
|  any other file indirectly affecting the aspect of the manual.
|  You might want to install the Texinfo package:
|  
|  The spurious makeinfo call might also be the consequence of
|  using a buggy 'make' (AIX, DU, IRIX), in which case you might
|  want to install GNU make:
|  
| make[3]: *** [Makefile:1097: libtasn1.info] Error 127
| make[3]: Leaving directory '/<>/doc'
| make[2]: *** [Makefile:1350: check-recursive] Error 1
| make[2]: Leaving directory '/<>/doc'
| make[1]: *** [Makefile:1027: check-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_test: make -j8 check VERBOSE=1 returned exit code 2
| make: *** [debian/rules:51: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build work, which is why reproducible doesn't see this issue. The
installation set does not include the texinfo package, which contains
makeinfo, and texinfo is not requested by Build-Depends. The earlier
builds on the buildds did not attempt to run makeinfo. Possibly this is
related to updating the version of autoconf?

Helmut
--- End Message ---
--- Begin Message ---
Source: automake-1.16
Source-Version: 1:1.16.1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated automake-1.16 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: Mon, 27 Aug 2018 16:40:12 +0300
Source: automake-1.16
Binary: automake
Architecture: source
Version: 1:1.16.1-1.1
Distribution: unstable
Urgency: high
Maintainer: Eric Dorland 
Changed-By: Adrian Bunk 
Description:
 automake   - Tool for generating GNU Standards-compliant Makefiles
Closes: 906426
Changes:
 automake-1.16 (1:1.16.1-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Remove 0008-SOURCE_DATE_EPOCH-support-for-mdate-sh.patch which
 broke mdate-sh, thanks to Andreas Metzler. (Closes: #906426)
Checksums-Sha1:
 fe83cee115edf7eb91b977eaebc0ef4dbee61b5c 2229 automake-1.16_1.16.1-1.1.dsc
 8b39560583b0b96cc31791df254f0515bd17d16f 14544 
automake-1.16_1.16.1-1.1.debian.tar.xz
Checksums-Sha256:
 cbde407313f7306389f323ef2ca07e77f9c344b420d3caded3733bced6080014 2229 
automake-1.16_1.16.1-1.1.dsc
 

Bug#906557: marked as done (ratpoison: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 10:33:58 +
with message-id 
and subject line Bug#906426: fixed in automake-1.16 1:1.16.1-1.1
has caused the Debian Bug report #906426,
regarding ratpoison: FTBFS in buster/sid (makeinfo: command not found)
to be marked as done.

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

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


-- 
906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ratpoison
Version: 1.4.8-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh_testdir
autoreconf -i
aclocal: installing 'm4/pkg.m4' from '/usr/share/aclocal/pkg.m4'
configure.ac:114: installing 'build-aux/compile'
configure.ac:24: installing 'build-aux/install-sh'
configure.ac:24: installing 'build-aux/missing'
doc/Makefile.am:20: installing 'build-aux/mdate-sh'
doc/Makefile.am:20: installing 'build-aux/texinfo.tex'
src/Makefile.am: installing 'build-aux/depcomp'
touch autoreconf-stamp
dh_testdir
./configure --build x86_64-linux-gnu \
--prefix=/usr --sysconfdir=/etc \

[... snipped ...]

make[1]: Entering directory '/<>'
Making install in src
make[2]: Entering directory '/<>/src'
make[3]: Entering directory '/<>/src'
 /bin/mkdir -p '/<>/debian/ratpoison/usr/bin'
  /usr/bin/install -c ratpoison '/<>/debian/ratpoison/usr/bin'
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
Making install in doc
make[2]: Entering directory '/<>/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in ratpoison.info ratpoison.info-[0-9] ratpoison.info-[0-9][0-9] 
ratpoison.i[0-9] ratpoison.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo   -I . \
 -o ratpoison.info ratpoison.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./ratpoison.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[2]: *** [Makefile:358: ratpoison.info] Error 127
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:413: install-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:105: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ratpoison.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: automake-1.16
Source-Version: 1:1.16.1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated automake-1.16 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 

Bug#906774: marked as done (dico: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 10:33:58 +
with message-id 
and subject line Bug#906426: fixed in automake-1.16 1:1.16.1-1.1
has caused the Debian Bug report #906426,
regarding dico: FTBFS in buster/sid (makeinfo: command not found)
to be marked as done.

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

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


-- 
906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dico
Version: 2.5-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_autoreconf -i
Copying file m4/glibc2.m4
Copying file m4/intdiv0.m4

[... snipped ...]

Making check in doc
make[3]: Entering directory '/<>/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in dico.info dico.info-[0-9] dico.info-[0-9][0-9] dico.i[0-9] 
dico.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo -I ../imprimatur -D 
DISTRIB  -I . \
 -o dico.info dico.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./dico.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[3]: *** [Makefile:1263: dico.info] Error 127
make[3]: Leaving directory '/<>/doc'
make[2]: *** [Makefile:1294: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:60: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dico.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: automake-1.16
Source-Version: 1:1.16.1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated automake-1.16 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: Mon, 27 Aug 2018 16:40:12 +0300
Source: automake-1.16
Binary: automake
Architecture: source
Version: 1:1.16.1-1.1
Distribution: unstable
Urgency: high
Maintainer: Eric Dorland 
Changed-By: Adrian Bunk 
Description:
 automake   - Tool for generating GNU Standards-compliant Makefiles
Closes: 906426
Changes:
 automake-1.16 (1:1.16.1-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Remove 0008-SOURCE_DATE_EPOCH-support-for-mdate-sh.patch which
 broke mdate-sh, thanks to Andreas Metzler. (Closes: #906426)

Bug#907714: marked as done (golang-x-text: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 09:48:59 +
with message-id 
and subject line Bug#907714: fixed in golang-x-text 0.3.0-2
has caused the Debian Bug report #907714,
regarding golang-x-text: FTBFS in buster/sid (failing tests)
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.)


-- 
907714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-x-text
Version: 0.3.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
golang.org/x/text golang.org/x/text/cases golang.org/x/text/collate 
golang.org/x/text/collate/build golang.org/x/text/currency 
golang.org/x/text/date golang.org/x/text/encoding 
golang.org/x/text/encoding/charmap golang.org/x/text/encoding/htmlindex 
golang.org/x/text/encoding/ianaindex golang.org/x/text/encoding/internal 
golang.org/x/text/encoding/internal/enctest 
golang.org/x/text/encoding/internal/identifier 
golang.org/x/text/encoding/japanese golang.org/x/text/encoding/korean 
golang.org/x/text/encoding/simplifiedchinese 
golang.org/x/text/encoding/traditionalchinese 
golang.org/x/text/encoding/unicode golang.org/x/text/encoding/unicode/utf32 
golang.org/x/text/feature/plural golang.org/x/text/internal 
golang.org/x/text/internal/catmsg golang.org/x/text/internal/cldrtree 
golang.org/x/text/internal/colltab golan
 g.org/x/text/internal/export/idna golang.org/x/text/internal/format 
golang.org/x/text/internal/gen golang.org/x/text/internal/number 
golang.org/x/text/internal/stringset golang.org/x/text/internal/tag 
golang.org/x/text/internal/testtext golang.org/x/text/internal/triegen 
golang.org/x/text/internal/ucd golang.org/x/text/internal/utf8internal 
golang.org/x/text/language golang.org/x/text/language/display 
golang.org/x/text/message golang.org/x/text/message/catalog 
golang.org/x/text/number golang.org/x/text/runes golang.org/x/text/search 
golang.org/x/text/secure golang.org/x/text/secure/bidirule 
golang.org/x/text/secure/precis golang.org/x/text/transform 
golang.org/x/text/unicode golang.org/x/text/unicode/bidi 
golang.org/x/text/unicode/cldr golang.org/x/text/unicode/norm 
golang.org/x/text/unicode/rangetable golang.org/x/text/unicode/runenames 
golang.org/x/text/width
golang.org/x/text
golang.org/x/text/internal/tag
golang.org/x/text/language
golang.org/x/text/internal
golang.org/x/text/transform
golang.org/x/text/unicode/norm
golang.org/x/text/cases

[... snipped ...]

=== RUN   TestNarrowSingleRunes
--- PASS: TestNarrowSingleRunes (0.03s)
=== RUN   TestNarrow
=== RUN   TestNarrow/empty
=== RUN   TestNarrow/short_source_1
=== RUN   TestNarrow/short_source_2
=== RUN   TestNarrow/incomplete_but_terminated_source_1
=== RUN   TestNarrow/incomplete_but_terminated_source_2
=== RUN   TestNarrow/exact_fit_dst
=== RUN   TestNarrow/exact_fit_dst_some_span
=== RUN   TestNarrow/empty_dst
=== RUN   TestNarrow/empty_dst_ascii
=== RUN   TestNarrow/short_dst_1
=== RUN   TestNarrow/short_dst_2
=== RUN   TestNarrow/ambiguous
=== RUN   TestNarrow/short_dst_fast_path
=== RUN   TestNarrow/short_dst_larger_buffer
=== RUN   TestNarrow/fast_path_alternation
--- PASS: TestNarrow (0.00s)
--- PASS: TestNarrow/empty (0.00s)
--- PASS: TestNarrow/short_source_1 (0.00s)
--- PASS: TestNarrow/short_source_2 (0.00s)
--- PASS: TestNarrow/incomplete_but_terminated_source_1 (0.00s)
--- PASS: TestNarrow/incomplete_but_terminated_source_2 (0.00s)
--- PASS: TestNarrow/exact_fit_dst (0.00s)
--- PASS: TestNarrow/exact_fit_dst_some_span (0.00s)
--- PASS: TestNarrow/empty_dst (0.00s)
--- PASS: TestNarrow/empty_dst_ascii (0.00s)
--- PASS: TestNarrow/short_dst_1 (0.00s)
--- PASS: TestNarrow/short_dst_2 (0.00s)
--- PASS: TestNarrow/ambiguous (0.00s)
--- PASS: TestNarrow/short_dst_fast_path (0.00s)
--- PASS: TestNarrow/short_dst_larger_buffer (0.00s)
--- PASS: TestNarrow/fast_path_alternation (0.00s)
=== RUN   ExampleTransformer_fold
--- PASS: ExampleTransformer_fold (0.00s)
=== RUN   ExampleTransformer_widen
--- 

Processed: severity of 897223 is serious

[Debian Bug Tracking System]

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

> severity 897223 serious
Bug #897223 [python-kmodpy] python-kmodpy breaks package system in multiarch 
setting
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#907741: libefl-all-dev breaks by binNMU

[Andreas Metzler]

On 2018-09-01 Adrian Bunk  wrote:
[...]
> Breaks+Replaces on (<< ${binary:Version}) is wrong when
> the broken package is binary-all.

> And these versions shouldn't be generated here at all,
> these should be the fixed versions when the contents
> moved to libefl-all-dev.

You are obviously right. Thanks and for report and diagnosis.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#902467: marked as done (golang-github-kardianos-osext: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 01 Sep 2018 09:03:53 +
with message-id 
and subject line Bug#902467: fixed in golang-github-kardianos-osext 
0.0~git20170510.0.ae77be6-6
has caused the Debian Bug report #902467,
regarding golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)
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.)


-- 
902467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-kardianos-osext
Version: 0.0~git20170510.0.ae77be6-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-kardianos-osext-0.0\~git20170510.0.ae77be6/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-kardianos-osext-0.0\~git20170510.0.ae77be6/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/kardianos/osext
github.com/kardianos/osext
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/kardianos/osext
=== RUN   TestPrintExecutable
--- PASS: TestPrintExecutable (0.00s)
osext_test.go:32: Executable: /tmp/go-build962600465/b001/osext.test
=== RUN   TestPrintExecutableFolder
--- PASS: TestPrintExecutableFolder (0.00s)
osext_test.go:39: Executable Folder: /tmp/go-build962600465/b001
=== RUN   TestExecutableFolder
--- PASS: TestExecutableFolder (0.00s)
=== RUN   TestExecutableMatch
--- PASS: TestExecutableMatch (0.00s)
=== RUN   TestExecutableDelete
--- FAIL: TestExecutableDelete (0.00s)
osext_test.go:135: Child returned 
"/tmp/go-build962600465/b001/osext.test (deleted)", not the same file as 
"/tmp/go-build962600465/b001/osext.test"
FAIL
FAILgithub.com/kardianos/osext  0.004s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/kardianos/osext returned exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-kardianos-osext.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-github-kardianos-osext
Source-Version: 0.0~git20170510.0.ae77be6-6

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated golang-github-kardianos-osext 
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: Sat, 01 Sep 2018 16:37:39 +0800
Source: golang-github-kardianos-osext
Binary: golang-github-kardianos-osext-dev
Architecture: source
Version: 0.0~git20170510.0.ae77be6-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Shengjing Zhu 
Description:
 golang-github-kardianos-osext-dev - Extend "os" package with Executable and 
ExecutableFolder
Closes: 902467
Changes:
 golang-github-kardianos-osext (0.0~git20170510.0.ae77be6-6) unstable; 
urgency=medium
 .
   * Team upload.
   * Update Team address to team+pkg-go@tracker.d.o.
   * Update Standards-Version to 

Bug#907741: libefl-all-dev breaks by binNMU

[Adrian Bunk]

Package: libefl-all-dev
Version: 1.20.7-6
Severity: serious

# apt-get install libecore-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libecore-dev : Depends: libefl-all-dev (>= 1.20.7-6) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.
#


Breaks+Replaces on (<< ${binary:Version}) is wrong when
the broken package is binary-all.

And these versions shouldn't be generated here at all,
these should be the fixed versions when the contents
moved to libefl-all-dev.

Bug#907714: golang-x-text: FTBFS in buster/sid (failing tests)

[Santiago Vila]

On Sat, Sep 01, 2018 at 03:31:00PM +0800, Shengjing Zhu wrote:
> (resend, forget to cc bts)
> 
> That's the one failed test,
> 
> --- FAIL: TestCountMallocs (0.00s)
> fmt_test.go:1443: Sprintf(""): got 3 allocs, want <=0
> fmt_test.go:1443: Sprintf("xxx"): got 4 allocs, want <=1
> fmt_test.go:1443: Sprintf("%x"): got 5 allocs, want <=2
> fmt_test.go:1443: Sprintf("%s"): got 5 allocs, want <=2
> fmt_test.go:1443: Sprintf("%x %x"): got 5 allocs, want <=3
> fmt_test.go:1443: Sprintf("%g"): got 7 allocs, want <=2
> fmt_test.go:1443: Fprintf(buf, "%s"): got 4 allocs, want <=1
> fmt_test.go:1443: Fprintf(buf, "%x %x %x"): got 4 allocs, want <=0
> 
> 
> It happens when you run tests with 1 process(GOMAXPROCS=1)
> 
> The upstream bug is https://github.com/golang/go/issues/23000
> 
> This test is to ensure max malloc times used, so I don't think the test
> is so important to kick packages out of testing.
> 
> Can we skip this test?

If you ask me, yes, that's definitely what I would do. I expect
packages to be buildable on any Debian setup on which Debian itself
may be installed, provided there is enough RAM and hard disk.

Thanks.

Bug#907714: golang-x-text: FTBFS in buster/sid (failing tests)

[Shengjing Zhu]

(resend, forget to cc bts)

That's the one failed test,

--- FAIL: TestCountMallocs (0.00s)
fmt_test.go:1443: Sprintf(""): got 3 allocs, want <=0
fmt_test.go:1443: Sprintf("xxx"): got 4 allocs, want <=1
fmt_test.go:1443: Sprintf("%x"): got 5 allocs, want <=2
fmt_test.go:1443: Sprintf("%s"): got 5 allocs, want <=2
fmt_test.go:1443: Sprintf("%x %x"): got 5 allocs, want <=3
fmt_test.go:1443: Sprintf("%g"): got 7 allocs, want <=2
fmt_test.go:1443: Fprintf(buf, "%s"): got 4 allocs, want <=1
fmt_test.go:1443: Fprintf(buf, "%x %x %x"): got 4 allocs, want <=0


It happens when you run tests with 1 process(GOMAXPROCS=1)

The upstream bug is https://github.com/golang/go/issues/23000

This test is to ensure max malloc times used, so I don't think the test
is so important to kick packages out of testing.

Can we skip this test?

-- 
Shengjing Zhu

Processed: bug 907714 is forwarded to https://github.com/golang/go/issues/23000

[Debian Bug Tracking System]

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

> forwarded 907714 https://github.com/golang/go/issues/23000
Bug #907714 [src:golang-x-text] golang-x-text: FTBFS in buster/sid (failing 
tests)
Set Bug forwarded-to-address to 'https://github.com/golang/go/issues/23000'.
> thanks
Stopping processing here.

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

Bug#905908: libGL.so.1: cannot open shared object file: No such file or directory when updating to 4.4.1~rc2-3

[Adrian Bunk]

On Sat, Sep 01, 2018 at 01:11:18AM +0200, Andreas Beckmann wrote:
>...
> Why does it need libGL.so.1 in a maintainer script anyway?

It doesn't need it for building the octave system package cache,
but one of the octave libraries is linked with libGL.

> Andreas

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed