date:20180609

Bug#901185: me too

2018-06-09 Thread Andreas Metzler

On 2018-06-10 積丹尼 Dan Jacobson  wrote:
> Oops. I mean just:
> Setting up exim4-config (4.91-5) ...
> /etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command 
> not found

Hello,

Are you running bash (or other stuff) from experimental? IIRC there is
some breakage there.

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#901185: me too

2018-06-09 Thread 積丹尼 Dan Jacobson

Oops. I mean just:
Setting up exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command 
not found

Bug#901185: me too

2018-06-09 Thread 積丹尼 Dan Jacobson

Setting up exim4-config (4.91-5) ...
/var/lib/dpkg/info/exim4-config.postinst: line 330: export: 
`dc_eximconfig_configtype dc_other_hostnames dc_local_interfaces dc_readhost 
dc_relay_domains dc_minimaldns dc_relay_nets dc_smarthost CFILEMODE 
dc_use_split_config dc_hide_mailname dc_mailname_in_oh dc_localdelivery': not a 
valid identifier
dpkg: error processing package exim4-config (--configure):

Bug#896295: Tensorflow is missing

2018-06-09 Thread Lumin

Hello Debian-Science folks,

Please feel free to CC me if you need any input about deep learning.

> From: Andreas Tille
> the description says:
> 
>  ...  Alternatively, Keras could run on Google's
>  TensorFlow (not yet available in Debian, but coming up).
> 
> Is there some estimated time frame to package TensorFlow?

No estimated time frame for it. TensorFlow provides bazel build for
linux and cmake build for windows.  Bazel itself is blocking for years,
and a DD, Paul Liu, who worked on it in the past had said that it was
hard to deal with. I guess the bazel build system is still blocking
currently.
 
> If not please try to deactivate this alternative since the package does
> not work as this bug report explains.

I'd suggest patching upstream source to use Theano as the default
backend, and comment it clearly in the descriptions.

> From: Stephen Sinclair
> Regarding Tensorflow packaging I do not know, someone on debian-science
> mentioned difficulties with its build system. I do hope these are
> resolvable but it seems to be a big issue.

That so-called "someone" was me, actually. Bazel build is actually a big
issue, and I have no plan to patch the windows cmake build in a
reasonable time frame.

You may have found that Debian-team holds a tensorflow repo on Salsa,
but that's merely an old copy of upstream code.
https://salsa.debian.org/science-team/tensorflow

I'm currently maintaing several TensorFlow dependencies. Hope that
They will be helpful sometime in the future.

farmhash
gemmlowp
highwayhash

The full list of dependency can be found in the third_part directory
of tensorflow source.

Bug#901116: marked as done (sane-backends-extras: FTBFS when built with dpkg-buildpackage -A)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sun, 10 Jun 2018 01:05:16 +
with message-id 
and subject line Bug#901116: fixed in sane-backends-extras 1.0.22.6
has caused the Debian Bug report #901116,
regarding sane-backends-extras: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
901116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sane-backends-extras
Version: 1.0.22.5
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
configure.ac:511: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1084: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4211: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5343: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:143: _LT_SETUP is expanded from...
m4/libtool.m4:69: LT_INIT is expanded from...
m4/libtool.m4:107: AC_PROG_LIBTOOL is expanded from...

[... snipped ...]

make[3]: Entering directory '/<>/backend'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/sane'
 /bin/bash ../libtool --silent   --mode=install /usr/bin/install -c   
libsane-geniusvp2.la libsane-ls5000.la 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/sane'
libtool: warning: remember to run 'libtool --finish 
/usr/lib/x86_64-linux-gnu/sane'
make  install-data-hook
make[4]: Entering directory '/<>/backend'
rm -f /<>/debian/tmp/usr/lib/x86_64-linux-gnu/sane/libsane.*
test -z "/etc/sane.d" || /bin/mkdir -p "/<>/debian/tmp/etc/sane.d"
test -z "/etc/sane.d/dll.d" || /bin/mkdir -p 
"/<>/debian/tmp/etc/sane.d/dll.d"
installing geniusvp2.conf in /etc/sane.d/geniusvp2.conf...
for dir in  ; do \
  /bin/bash ../mkinstalldirs /<>/debian/tmp/usr/share/sane/${dir} 
; \
  done
make[4]: Leaving directory '/<>/backend'
make[3]: Leaving directory '/<>/backend'
make[2]: Leaving directory '/<>/backend'
Making install in doc
make[2]: Entering directory '/<>/doc'
make[3]: Entering directory '/<>/doc'
make[3]: Nothing to be done for 'install-exec-am'.
test -z "/usr/share/man/man5" || /bin/mkdir -p 
"/<>/debian/tmp/usr/share/man/man5"
installing sane-geniusvp2.5 in /usr/share/man/man5/sane-geniusvp2.5...
make[3]: Leaving directory '/<>/doc'
make[2]: Leaving directory '/<>/doc'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# remove wrong libsane.so.1 symlink
rm -f debian/libsane-extras/usr/lib/x86_64-linux-gnu/sane/libsane.so.1
# remove damn rpath
find debian/libsane-extras/usr/lib/x86_64-linux-gnu/sane -name "libsane-*.so.1" 
-exec chrpath -d {} \;
find: 'debian/libsane-extras/usr/lib/x86_64-linux-gnu/sane': No such file or 
directory
debian/rules:36: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:16: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-indep and 
override_dh_install-arch.

Thanks.
--- End Message ---
--- Begin Message ---
Source: sane-backends-extras
Source-Version: 1.0.22.6

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated sane-backends-extras 
package)

(This message was generated automatically at

Bug#901191: libfabric-bin: missing Breaks+Replaces: libfabric1 (<< 1.6)

2018-06-09 Thread Andreas Beckmann

Package: libfabric-bin
Version: 1.6.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libfabric-bin.
  Preparing to unpack .../libfabric-bin_1.6.1-1_amd64.deb ...
  Unpacking libfabric-bin (1.6.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfabric-bin_1.6.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/fi_info', which is also in package libfabric1 
1.5.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libfabric-bin_1.6.1-1_amd64.deb


cheers,

Andreas


libfabric1=1.5.3-1_libfabric-bin=1.6.1-1.log.gz
Description: application/gzip

Bug#901190: libcob4-dev: removal of libcob4-dev makes files disappear from libcob1-dev

2018-06-09 Thread Andreas Beckmann

Package: libcob4-dev
Version: 2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libcob1-dev
  # (1)
  apt-get install libcob4-dev
  apt-get remove libcob4-dev
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/include/libcob.h
  /usr/include/libcob/common.h
  /usr/include/libcob/exception.def

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior
https://www.debian.org/doc/debian-policy/ (old: footnotes.html#f53)
[footnote permalink broken (#879048), search for /To see why/]

The libcob4-dev package has the following relationships with libcob1-dev:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libcob1-dev

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

0m19.8s ERROR: FAIL: After purging files have disappeared:
  /usr/include/libcob.h  owned by: libcob4-dev
  /usr/include/libcob/common.h   owned by: libcob4-dev
  /usr/include/libcob/exception.def  owned by: libcob4-dev

0m19.8s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libcob1-dev.listnot owned


cheers,

Andreas


libcob1-dev=1.1-2+b2_libcob4-dev=2.2-1.log.gz
Description: application/gzip

Bug#901189: timidity,timidity-el: both packages ship the manpages

2018-06-09 Thread Andreas Beckmann

Package: timidity,timidity-el
Version: 2.14.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package timidity-el.
  Preparing to unpack .../timidity-el_2.14.0-2_all.deb ...
  Unpacking timidity-el (2.14.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/timidity-el_2.14.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/ja/man1/timidity.1.gz', which is also in 
package timidity 2.14.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/timidity-el_2.14.0-2_all.deb

The following files are shipped by both packages:

usr/share/man/ja/man1/timidity.1.gz
usr/share/man/ja/man5/timidity.cfg.5.gz
usr/share/man/man1/timidity.1.gz
usr/share/man/man5/timidity.cfg.5.gz


cheers,

Andreas


timidity=2.14.0-2_timidity-el=2.14.0-2.log.gz
Description: application/gzip

Bug#900511: marked as done (libcurl4 Conflicts: libcurl3)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sun, 10 Jun 2018 00:54:04 +0100
with message-id <20180609235404.GA24375@pinky>
and subject line Re: Bug#900511: libcurl4 Conflicts: libcurl3
has caused the Debian Bug report #900511,
regarding libcurl4 Conflicts: libcurl3
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.)

-- 
900511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcurl4
Version: 7.60.0-2
Severity: serious

libcurl4 conflicts with libcurl3, which violates the stated purpose of
the "must" clause at Policy 8.1 (to allow multiple versions of a shared
library to be co-installable), even though it doesn't violate the letter
of the must (binary package name must change when SONAME changes).
Without the second sentence at Policy 8.1, the MUST requirement serves
no purpose, so I have given this severity serious.

This means that, regardless of what Debian does with packages depending
on libcurl, libcurl4 cannot be installed if the user has third party or
home brew software that requires libcurl3.

I found this because I have netsurf-gtk installed, which Depends:
libcurl3.  netsurf-gtk is currently the same version in stable and
unstable, but has been removed from testing.

...Marvin

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Mon, Jun 04, 2018 at 12:33:09AM +0200, Richard B. Kreckel wrote:
> On Sat, 2 Jun 2018 23:14:40 +0300 Adrian Bunk  wrote:
> > libcurl3 is not part of buster, and using libraries from previous 
> > releases that are no longer present in a new stable Debian release is 
> > not strictly supported - it works most of the time, but when problems
> > are reported a Breaks/Conflicts against that library is usually the
> > solution.
> 
> Yeah, I have read this:
> https://salsa.debian.org/debian/curl/merge_requests/2.
> 
> Still, the question remains: Why can different libssl packages coexist
> fine (even if they are from a previous Debian version) but libcurl
> packages cannot?

This transition has already been discussed at length in #858398, but long story
short, both libcurl3 and libcurl4 provide the "libcurl.so.4" library (libcurl3
did so for historical reasons), so both packages can't be installed at the same
time. On the other hand the libssl packages provide different libraries
("libssl.so.1.0.2" and "libssl.so.1.1") so they are co-installable.

Cheers

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

Processed: unarchiving 693396, unarchiving 860952

2018-06-09 Thread Debian Bug Tracking System

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

> unarchive 693396
Bug #693396 {Done: Ben Hutchings } [rar] rar: static & 
dynamic executables mix
Unarchived Bug 693396
> unarchive 860952
Bug #860952 {Done: Ben Hutchings } [rar] Statically 
linked to glibc, in breach of policy and copyright
Unarchived Bug 860952
> thanks
Stopping processing here.

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

Processed: tagging 900791

2018-06-09 Thread Debian Bug Tracking System

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

> tags 900791 + buster sid
Bug #900791 [xserver-xorg-input-mouse] xserver-xorg-input-mouse: FTBFS with 
newer xserver
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: Re: Bug#901185: exim4-config: fails to install

2018-06-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + moreinfo
Bug #901185 [exim4-config] exim4-config: fails to install
Added tag(s) moreinfo.

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

Bug#901185: exim4-config: fails to install

2018-06-09 Thread Adam D. Barratt

Control: tags -1 + moreinfo

On Sun, 2018-06-10 at 00:17 +0200, Eric Valette wrote:
> ParamÃ©trage de exim4-config (4.91-5) ...
> /etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype
> : commande introuvable
> /etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype
> : commande introuvable
> 

That doesn't make huge amounts of sense, at least at first glance.

update-exim4.conf, which is what will be being called here, sources
update-exim4.conf.conf, but that shouldn't be leading to "command not
found" errors.

The mention of line 32 is also interesting, as the standard file
appears to be 31 lines long.

Could you share the content of the file on the relevant machine,
please?

Regards,

Adam

Bug#901185: exim4-config: fails to install

2018-06-09 Thread Eric Valette

Package: exim4-config
Version: 4.91-5
Severity: grave
Justification: renders package unusable

apt-get -f install
Lecture des listes de paquets... Fait
Construction de l'arbre des dÃ©pendances   
Lecture des informations d'Ã©tat... Fait
0 mis Ã  jour, 0 nouvellement installÃ©s, 0 Ã  enlever et 2 non mis Ã  jour.
4 partiellement installÃ©s ou enlevÃ©s.
AprÃ¨s cette opÃ©ration, 0 o d'espace disque supplÃ©mentaires seront utilisÃ©s.
ParamÃ©trage de exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype : 
commande introuvable
/etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype : 
commande introuvable
dpkg: erreur de traitement du paquet exim4-config (--configure)Â :
 installed exim4-config package post-installation script subprocess returned 
error exit status 127
dpkg: des problÃ¨mes de dÃ©pendances empÃªchent la configuration de exim4-baseÂ 
:
 exim4-base dÃ©pend de exim4-config (>= 4.82) | exim4-config-2Â ; cependantÂ :
 Le paquet exim4-config n'est pas encore configurÃ©.
  Le paquet exim4-config-2 n'est pas installÃ©.
  Le paquet exim4-config qui fournit exim4-config-2 n'est pas encore configurÃ©.

dpkg: erreur de traitement du paquet exim4-base (--configure)Â :
 problÃ¨mes de dÃ©pendances - laissÃ© non configurÃ©
dpkg: des problÃ¨mes de dÃ©pendances empÃªchent la configuration de exim4Â :
 exim4 dÃ©pend de exim4-base (>= 4.91-5)Â ; cependantÂ :
 Le paquet exim4-base n'est pas encore configurÃ©.
 exim4 dÃ©pend de exim4-base (<< 4.91-5.1)Â ; cependantÂ :
 Le paquet exim4-base n'est pas encore configurÃ©.



-- Package-specific info:
Exim version 4.91 #4 built 09-Jun-2018 16:10:39
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated

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

Kernel: Linux 4.14.48 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages exim4-config depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66

exim4-config recommends no packages.

exim4-config suggests no packages.

-- Configuration Files:
/etc/exim4/passwd.client [Errno 13] Permission non accordÃ©e: 
'/etc/exim4/passwd.client'

-- debconf information excluded

Bug#900457: marked as done (yade: FTBFS and Debci failure with NumPy 1.14)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 21:37:19 +
with message-id 
and subject line Bug#900457: fixed in yade 2018.02b-2
has caused the Debian Bug report #900457,
regarding yade: FTBFS and Debci failure with NumPy 1.14
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.)


-- 
900457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yade
Version: 2018.02b-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the recent upload of python-numpy on 2018-05-05, yade has been
failing its autopkgtests [1] and has now also started to FTBFS in
unstable [2] with several errors similar to the following:

FAIL: saveDataTxt (yade.plot)
Doctest: yade.plot.saveDataTxt
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 2226, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for yade.plot.saveDataTxt
  File 
"/build/1st/yade-2018.02b/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/plot.py",
line 614, in saveDataTxt

Regards
Graham


[1] https://ci.debian.net/packages/y/yade/unstable/amd64/
[2] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/yade.html
--- End Message ---
--- Begin Message ---
Source: yade
Source-Version: 2018.02b-2

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated yade 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, 09 Jun 2018 23:16:40 +0200
Source: yade
Binary: yade libyade python-yade yade-doc
Architecture: source
Version: 2018.02b-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libyade- Platform for discrete element modeling. Libraries
 python-yade - Platform for discrete element modeling. Python bindings
 yade   - Platform for discrete element modeling
 yade-doc   - Platform for discrete element modeling. Documentation
Closes: 890237 900457
Changes:
 yade (2018.02b-2) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * [4cf8d3c] Drop debug info for mips/mipsel. (Closes: #890237)
 .
   [ Anton Gladky ]
   * [b87e33b] Use tar.gz instead of failing bz2 in doctest. (Closes: #900457)
   * [37a6e5b] Add tilda to debhelper version number
   * [20d3a2e] Set Standards-Version to 4.1.4
   * [ec2b9f9] Fix compilation with the newer sphinx.
Checksums-Sha1:
 be2bb8383afe4eb705f325e2d2da02cfee3f15b0 2928 yade_2018.02b-2.dsc
 e75d96762fd77bb85300cdaf80e59fac2935c1bf 21332 yade_2018.02b-2.debian.tar.xz
 10e9531ab86982ba39eb430696d6e6c8e5af4956 27934 yade_2018.02b-2_source.buildinfo
Checksums-Sha256:
 01139ae43a2f033bec2301b84d8e78342cba96921e552a75abab4f93c35828b6 2928 
yade_2018.02b-2.dsc
 dd0c586e9d6824ff9c5fdcfc6ec0955f9ebef08eb5a4c899208b5eefe07688b2 21332 
yade_2018.02b-2.debian.tar.xz
 14ca5373d92ab30b409cf3d75b11aea10fb2cde8f1e234aebd17918e7586cfbd 27934 
yade_2018.02b-2_source.buildinfo
Files:
 86b06f31d35ce61a68ee9022ab805fea 2928 science optional yade_2018.02b-2.dsc
 9adf7b160006503755ef6b11a0ccce62 21332 science optional 
yade_2018.02b-2.debian.tar.xz
 2974d7716dd09cb422163935f8eec9c6 27934 science optional 
yade_2018.02b-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlscQ+AACgkQ0+Fzg8+n
/wZ+MQ/9FK3vOkihVSJfDhfWxT0dB7B3HIZ1cUkNynikjGRge+dTCLvVMtA9FRAX
p831yAPICdwMPXjgzlY+qKGclLx8EuWRuNhej/vayrrmrt2xZPVKT9GMleUqT4+l
3tWq3M+Lwv6JBQyfh15S1OoR5Lze+vXLhThfrJZrt1jvtMroxX8fX1+rG/4q0U3L
sAQjEaQQKMTYUXb0GUqe39IUdq2oBdKciapx0z6ZodmHhjiHYSI1WmFTJbi8b24P
Rn+ST6hjE/zIqwWpKAO5l+9Wg99o91IuI/jrosb9LTLe+UFSCBvRp1j+YiPoF0Dr
PgBZ1v6uh7CyWj6SNUbeW5RS7Oj6bxGnqfOQKxNd1O4zogCczw9mgpsKkXp5DL/m
4bNIE+8uK/cBTCL2c2mCW+kEPYicL4FwfAWGJz4hXdPs6C2phpFkzjmwxPoRm94d
IjDZsWiwLBKbDrHiRSjQjFPJt30M65yyVMLHLH7PiwU8zqvQxr3prn2+yiwjW+wA

Bug#854167: marked as done (src:python-cartopy: Version 0.14.x is not compatible with matplotlib>=2.0 / owslib>=0.14)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 21:00:13 +
with message-id 
and subject line Bug#854167: fixed in python-cartopy 0.16.0+dfsg1-1
has caused the Debian Bug report #854167,
regarding src:python-cartopy: Version 0.14.x is not compatible with 
matplotlib>=2.0 / owslib>=0.14
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.)


-- 
854167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cartopy
Version: 0.14.2+dfsg1-1
Severity: serious

After discussing it with upstream [1], the version of cartopy currently
packaged in Stretch (0.14.2) should not be released alongside the
packaged matplotlib (2.0) and owslib (0.14), because the codebase is
known to be incompatible with their respective versions.

It is still uncertain whether version 0.15.0 will have support for
matplotlib>=2.0, so we might have to wait for a subsequent release
(0.15.1 or 0.16.x?) to get a fully working cartopy package.

[1] https://github.com/SciTools/cartopy/issues/838

Ghis


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

Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: python-cartopy
Source-Version: 0.16.0+dfsg1-1

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

Debian distribution maintenance software
pp.
Antonio Valentino  (supplier of updated 
python-cartopy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 08 Jun 2018 20:18:37 +
Source: python-cartopy
Binary: python-cartopy python3-cartopy python-cartopy-data
Architecture: source all amd64
Version: 0.16.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Antonio Valentino 
Description:
 python-cartopy - Cartographic library for Python 2
 python-cartopy-data - cartographic library for Python (package data)
 python3-cartopy - Cartographic library for Python 3
Closes: 854167 889931
Changes:
 python-cartopy (0.16.0+dfsg1-1) unstable; urgency=medium
 .
   [ Antonio Valentino ]
   * New upstream release (Closes: #854167).
   * Update copyright file.
   * Set compat to 11.
   * New python-cartopy-data package for common data files.
   * Standard version bump to 4.1.4:
 - remove get-orig-source target from debian/rules
   * debian/control
 - update maintainer field (python-cartopy is now maintained by the
   debian-gis team)
 - updated Vcs-* fields
 - update dependency list
 - drop ancient X-Python3-Version field
 - add Antonio Valentino to uploaders
   * debian/tests/control
 - switch to pytest
   * debian/patches
 - refresh and renumber all patches
 - new patches to improve compatibility with proj v5
   (Closes: #889931). See also
   https://github.com/OSGeo/proj.4/issues/985,
   https://github.com/OSGeo/proj.4/issues/941 and
   https://github.com/SciTools/cartopy/issues/1071)
   * debian/rules
 - switch to pytst
 .
   [ Bas Couwenberg ]
   * Update Repository URL to use HTTPS in upstream metadata.
   * Update Homepage URL to use HTTPS.
   * Reorder dependencies.
   * Capitalize first letter in short description.
   * Update watch file to handle common issues.
   * Update copyright file, changes:
 - Use standalone license paragraphs
 - Fix PSF license terms (Python-2.0)
 - Use standard public-domain license shortname
   * Update gbp.conf conform the Debian GIS Policy.
   * Refresh patches.
   * Align paths in install and link files.
Checksums-Sha1:
 1e3474a7d7d6537764907867292f545ae4aaf18d 2699 python-cartopy_0.16.0+dfsg1-1.dsc
 696637893f71c7cadd5b8653d34e969bd2aab732 8822359 
python-cartopy_0.16.0+dfsg1.orig.tar.gz
 d57911a83d51119ebbeaf17b5b37981c6845d978 8568 
python-cartopy_0.16.0+dfsg1-1.debian.tar.xz

Bug#889931: marked as done (python-cartopy FTBFS with proj 5.0.0)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 21:00:13 +
with message-id 
and subject line Bug#889931: fixed in python-cartopy 0.16.0+dfsg1-1
has caused the Debian Bug report #889931,
regarding python-cartopy FTBFS with proj 5.0.0
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.)


-- 
889931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cartopy
Version: 0.14.2+dfsg1-2
Severity: important
Tags: upstream
User: debian-...@lists.debian.org
Usertags: proj-5.0

Dear Maintainer,

Your package FTBFS due to missing compatibility with Proj 5.0.0:

 ==
 FAIL: cartopy.tests.crs.test_mercator.test_central_longitude
 --
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
 self.test(*self.arg)
   File 
"/build/python-cartopy-0.14.2+dfsg1/.pybuild/pythonX.Y_2.7/build/cartopy/tests/crs/test_mercator.py",
 line 72, in test_central_longitude
 [-20037508, -15496570, 20037508, 18764656], decimal=0)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 563, in 
assert_almost_equal
 return assert_array_almost_equal(actual, desired, decimal, err_msg)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 962, in 
assert_array_almost_equal
 precision=decimal)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 778, in 
assert_array_compare
 raise AssertionError(msg)
 AssertionError: 
 Arrays are not almost equal to 0 decimals
 
 (mismatch 25.0%)
  x: array([-20037508., -15496571., -20037508.,  18764656.])
  y: array([-20037508, -15496570,  20037508,  18764656])
 
 ==
 FAIL: cartopy.tests.crs.test_robinson.test_transform_point
 --
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
 self.test(*self.arg)
   File 
"/build/python-cartopy-0.14.2+dfsg1/.pybuild/pythonX.Y_2.7/build/cartopy/tests/crs/test_robinson.py",
 line 49, in test_transform_point
 assert_arr_almost_eq(result, (2376187.27182751, 7275317.81573085), _TOL)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 962, in 
assert_array_almost_equal
 precision=decimal)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 778, in 
assert_array_compare
 raise AssertionError(msg)
 AssertionError: 
 Arrays are not almost equal to 7 decimals
 
 (mismatch 100.0%)
  x: array([ 2376187.2757334,  7275317.7120387])
  y: array([ 2376187.2718275,  7275317.8157309])
 
 ==
 FAIL: cartopy.tests.crs.test_robinson.test_transform_points
 --
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
 self.test(*self.arg)
   File 
"/build/python-cartopy-0.14.2+dfsg1/.pybuild/pythonX.Y_2.7/build/cartopy/tests/crs/test_robinson.py",
 line 66, in test_transform_points
 [[2376187.27182751, 7275317.81573085, 0]], _TOL)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 962, in 
assert_array_almost_equal
 precision=decimal)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 778, in 
assert_array_compare
 raise AssertionError(msg)
 AssertionError: 
 Arrays are not almost equal to 7 decimals
 
 (mismatch 66.67%)
  x: array([[ 2376187.2757334,  7275317.7120387,0.   ]])
  y: array([[ 2376187.2718275,  7275317.8157309,0.   ]])
 
 ==
 FAIL: test_default (cartopy.tests.crs.test_transverse_mercator.TestOSNI)
 --
 Traceback (most recent call last):
   File 
"/build/python-cartopy-0.14.2+dfsg1/.pybuild/pythonX.Y_2.7/build/cartopy/tests/crs/test_transverse_mercator.py",
 line 104, in test_default
 386984.15347340))
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 962, in 
assert_array_almost_equal
 precision=decimal)
   File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 778, in 
assert_array_compare
 raise AssertionError(msg)
 AssertionError: 
 Arrays are

Bug#899481: marked as done (dnstap-ldns: Invalid maintainer address pkg-dns-de...@lists.alioth.debian.org)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 19:34:59 +
with message-id 
and subject line Bug#899481: fixed in dnstap-ldns 0.2.0-4
has caused the Debian Bug report #899481,
regarding dnstap-ldns: Invalid maintainer address 
pkg-dns-de...@lists.alioth.debian.org
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.)


-- 
899481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dnstap-ldns
Version: 0.2.0-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of dnstap-ldns,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package dnstap-ldns since the list address
pkg-dns-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-dns-de...@lists.alioth.debian.org is 10.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: dnstap-ldns
Source-Version: 0.2.0-4

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

Debian distribution maintenance software
pp.
Eric Dorland  (supplier of updated dnstap-ldns 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, 09 Jun 2018 15:13:56 -0400
Source: dnstap-ldns
Binary: dnstap-ldns
Architecture: source
Version: 0.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: dnstap-ldns packagers 
Changed-By: Eric Dorland 
Description:
 dnstap-ldns - Utility that can decode dnstap encoded files
Closes: 899481
Changes:
 dnstap-ldns (0.2.0-4) unstable; urgency=medium
 .
   * Update maintainer field post-alioth turndown (Closes: 899481)
   * Standards-Version to 4.1.4.1
Checksums-Sha1:
 f73b82d5c6918adba471d7ef8093332cebd64221 2018 dnstap-ldns_0.2.0-4.dsc
 618de73bc5573aa598fc6c06bf9c267f0046f484 5076 dnstap-ldns_0.2.0-4.debian.tar.xz
 36dd20d6ecb2860994b1b59a594336b96d87 6512 
dnstap-ldns_0.2.0-4_amd64.buildinfo
Checksums-Sha256:
 b3092cd1b37f3d4c9a9982edd4ac12cc62c295e286b9a1058940d52506ec5bfa 2018 
dnstap-ldns_0.2.0-4.dsc
 f8811d97169dcec5c5d7b8dc1aa0ad58398fecd6f6865072b6a05250b3d42ab7 5076 
dnstap-ldns_0.2.0-4.debian.tar.xz
 5b8e5d7339ea940f8a21ffe5a644399f2d86bfadf903e6ad8770f831a10de099 6512 
dnstap-ldns_0.2.0-4_amd64.buildinfo
Files:
 2694b8b3665b0935aacfa517fbd8b24c 2018 net optional dnstap-ldns_0.2.0-4.dsc
 74e82537d2bb6c5ea49b6ec29067f808 5076 net optional 
dnstap-ldns_0.2.0-4.debian.tar.xz
 292c043ddf8c7e7b0a8d0ef212171561 6512 net

Processed: retitle 809252 to node-cli: CVE-2016-10538 ...

2018-06-09 Thread Debian Bug Tracking System

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

> retitle 809252 node-cli: CVE-2016-10538
Bug #809252 [node-cli] node-cli: insecure use of temporary files
Changed Bug title to 'node-cli: CVE-2016-10538' from 'node-cli: insecure use of 
temporary files'.
> forwarded 809252 https://github.com/node-js-libs/cli/issues/81
Bug #809252 [node-cli] node-cli: CVE-2016-10538
Ignoring request to change the forwarded-to-address of bug#809252 to the same 
value
> thanks
Stopping processing here.

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

Bug#901001: python3-minimal should Pre-Depend on python3.N-minimal

2018-06-09 Thread Steve Langasek

On Sat, Jun 09, 2018 at 06:39:19PM +0200, Matthias Klose wrote:
> On 09.06.2018 18:31, Matthias Klose wrote:
> > On 09.06.2018 11:55, Philipp Kern wrote:
> > > On 6/9/18 7:20 AM, Steve Langasek wrote:
> > > > - the package is being upgraded; it is in the common case (when no 
> > > > python
> > > >    module names have been dropped from within the package) less 
> > > > important to
> > > >    run py3clean because the same files will be recreated shortly 
> > > > afterwards
> > > >    by py3compile from the new postinst.

> > > What's the consequence from deleting the files and only recreating them
> > > later? Longer startup time of the interpreter in that short window?

> > yes, that's the only thing.

> > > Because if it's worse, it'd be good to have py3clean only delete the
> > > obsolete files in the postinst?

> but as written in the bug report, there is another solution, to have
> py3clean search for the interpreter it uses, and which doesn't need the
> pre-dependency.

Is the following scenario a concern that we should take into consideration?

 - a core library that python3.5-minimal (or libpython3.5-minimal) depends
   on has an ABI change and must be renamed, with a conflicts on the old
   package name.
 - new python-minimal is unpacked. /usr/bin/python is a dangling symlink.
 - python3.5-minimal is removed due to the conflict.
 - python3.6-minimal is not yet unpacked, because ordering is not
   guaranteed.
 - python3-foo module is removed due to another conflict.  The prerm fails
   because py3clean can find no version of python3 interpreter on the disk.

The pre-depends would address this case, by enforcing the configuration of
python3.6-minimal before unpacking python-minimal (and before removing
python3.5-minimal).  It does constrain apt's solver, but as long as apt can
find a solution, that's ok.

It may be an ignorable hypothetical, since the set of libraries that
python3.5-minimal + libpython3.5-minimal depends on is quite small, and they
are all very stable and well-maintained upstream (zlib, libexpat1, libc6,
libssl).

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#897548: marked as done (yabause: FTBFS: dh_install: missing files, aborting)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 18:21:01 +
with message-id 
and subject line Bug#897548: fixed in yabause 0.9.14-3
has caused the Debian Bug report #897548,
regarding yabause: FTBFS: dh_install: missing files, aborting
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.)


-- 
897548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yabause
Version: 0.9.14-2.1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[2]: Nothing to be done for 'preinstall'.
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "None"
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/ar.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/de.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/es.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/fr.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/it.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/lt.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/nl.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/pt.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/pt_BR.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/ru.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/sv.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/zh_CN.yts
> -- Installing: /<>/debian/tmp/usr/share/yabause/yts/zh_TW.yts
> -- Installing: /<>/debian/tmp/usr/bin/yabause-qt
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/yabause-qt.desktop
> -- Installing: /<>/debian/tmp/usr/share/man/man1/yabause-qt.1
> -- Installing: /<>/debian/tmp/usr/share/pixmaps/yabause.png
> make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
>dh_install
> dh_install: Cannot find (any matches for) "usr/bin/yabause-gtk" (tried in ., 
> debian/tmp)
> 
> dh_install: yabause-gtk missing files: usr/bin/yabause-gtk
> dh_install: Cannot find (any matches for) 
> "usr/share/applications/yabause-gtk.desktop" (tried in ., debian/tmp)
> 
> dh_install: yabause-gtk missing files: 
> usr/share/applications/yabause-gtk.desktop
> dh_install: Cannot find (any matches for) "usr/share/man/man1/yabause-gtk.1" 
> (tried in ., debian/tmp)
> 
> dh_install: yabause-gtk missing files: usr/share/man/man1/yabause-gtk.1
> dh_install: missing files, aborting
> make: *** [debian/rules:12: binary] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/yabause_0.9.14-2.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: yabause
Source-Version: 0.9.14-3

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated yabause 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, 09 Jun 2018 18:15:32 +0200
Source: yabause
Binary: yabause yabause-common yabause-gtk yabause-qt
Architecture: source
Version: 0.9.14-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 yabause- beautiful and under-rated Saturn emulator
 yabause-common - beautiful and under-rated Saturn emulator - common files
 yabause-gtk - beautiful and under-rated Saturn emulator - Gtk port
 yabause-qt - beautiful and under-rated Saturn emulator - Qt port
Closes: 897548
Changes:

Bug#901158: marked as done (postgis: FTBFS: testsuite failure)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 17:51:37 +
with message-id 
and subject line Bug#901158: fixed in postgis 2.4.4+dfsg-2
has caused the Debian Bug report #901158,
regarding postgis: FTBFS: testsuite failure
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.)


-- 
901158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgis
Version: 2.4.4+dfsg-1
Severity: serious

This package fails to build from source on current sid/amd64.

   ### /tmp/pgis_reg/test_50_diff ###
  --- rt_gdalwarp_expected  2018-04-06 05:05:52.0 +
  +++ /tmp/pgis_reg/test_50_out 2018-06-09 14:27:15.049036062 +
  @@ -19,8 +19,8 @@
   0.17|993309|243|243|1|50.000|50.000|0.000|0.000|950760.000|1396957.000|t|t|t
   
0.18|992163|10|10|1|1000.000|-1000.000|3.000|3.000|-500030.000|60.000|t|t|t
   
0.19|993310|12|12|1|1009.894|-1009.894|3.000|3.000|950691.792|1409281.783|t|t|t
  
-0.2|993309|12|12|1|1009.916|-1009.916|0.000|0.000|950762.305|1409088.896|t|t|t
  
-0.20|993309|12|12|1|1009.916|-1009.916|1.000|3.000|950742.107|1409088.896|t|t|t
  
+0.2|993309|12|12|1|1009.876|-1009.876|0.000|0.000|950808.447|1409091.640|t|t|t
  
+0.20|993309|12|12|1|1009.876|-1009.876|1.000|3.000|950788.250|1409091.640|t|t|t
   0.21|993310|24|24|1|500.000|500.000|3.000|3.000|950657.188|1397356.783|t|t|t
   0.22|993310|26|26|1|500.000|500.000|0.000|6.000|950452.000|1396632.000|t|t|t
   0.23|984269|12|8|1|0.012|-0.012|0.000|0.000|-107.029|50.206|t|t|t
  @@ -63,12 +63,12 @@
   
1.9|992163|11|10|1|1000.000|-1000.000|0.000|0.000|-51.000|60.000|t|t|t
   
2.1|993310|12|12|1|1009.894|-1009.894|0.000|0.000|950732.188|1409281.783|t|t|t
   2.10|993310|24|24|1|500.000|500.000|0.000|0.000|950732.188|1397281.783|t|t|t
  
-2.11|993309|121|121|1|100.000|100.000|0.000|0.000|950762.305|1396988.896|t|t|t
  
+2.11|993309|121|121|1|100.000|100.000|0.000|0.000|950808.447|1396991.640|t|t|t
   2.12|993310|6|6|1|2000.000|2000.000|0.000|0.000|950732.188|1397281.783|t|t|t
   2.13|993310|8|8|1|1500.000|1500.000|0.000|0.000|950732.188|1397281.783|t|t|t
   2.14|993310|24|24|1|500.000|500.000|0.000|0.000|950732.188|1397281.783|t|t|t
   2.15|993310|16|16|1|750.000|750.000|0.000|0.000|950732.188|1397281.783|t|t|t
  
-2.2|993309|12|12|1|1009.916|-1009.916|0.000|0.000|950762.305|1409088.896|t|t|t
  
+2.2|993309|12|12|1|1009.876|-1009.876|0.000|0.000|950808.447|1409091.640|t|t|t
   2.3|994269|12|8|1|0.012|-0.012|0.000|0.000|-107.029|50.206|t|t|t
   2.4|
   
2.5|993310|12|12|1|1009.894|-1009.894|0.000|0.000|950732.188|1409281.783|t|t|t
   ### end of log dumps ###
  make[1]: *** [debian/rules:200: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>/postgis-2.4.4+dfsg'
  make: *** [debian/rules:111: build] Error 2
 
Full build log attached.
-- 
Niko Tyni   nt...@debian.org


postgis_amd64-2018-06-09T14:19:48Z.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: postgis
Source-Version: 2.4.4+dfsg-2

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated postgis 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, 09 Jun 2018 19:11:01 +0200
Source: postgis
Binary: postgis postgis-gui postgis-doc liblwgeom-2.4-0 liblwgeom-dev 
postgresql-10-postgis-2.4 postgresql-10-postgis-2.4-scripts 
postgresql-10-postgis-scripts
Architecture: source amd64 all
Version: 2.4.4+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 liblwgeom-2.4-0 - PostGIS "Lightweight Geometry" library
 liblwgeom-dev - PostGIS "Lightweight Geometry" library - Development files
 postgis- Geographic objects support for PostgreSQL
 postgis-doc - Geographic objects support for PostgreSQL -- documentation
 postgis-gui - Geographic objects support for PostgreSQL -- GUI programs
 postgresql-10-postgis-2.4 - Geographic objects support for PostgreSQL

Bug#901099: marked as done (libatlas-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libatlas-base-dev/README)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 17:34:30 +
with message-id 
and subject line Bug#901099: fixed in atlas 3.10.3-7
has caused the Debian Bug report #901099,
regarding libatlas-doc: fails to upgrade from 'stretch' - trying to overwrite 
/usr/share/doc/libatlas-base-dev/README
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.)


-- 
901099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libatlas-doc
Version: 3.10.3-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libatlas-doc.
  Preparing to unpack .../libatlas-doc_3.10.3-6_all.deb ...
  Unpacking libatlas-doc (3.10.3-6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatlas-doc_3.10.3-6_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libatlas-base-dev/README', which is also 
in package libatlas-base-dev 3.10.3-1+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libatlas-doc_3.10.3-6_all.deb


This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libatlas-base-dev=3.10.3-1+b1_libatlas-doc=3.10.3-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: atlas
Source-Version: 3.10.3-7

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated atlas 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, 09 Jun 2018 19:07:12 +0200
Source: atlas
Binary: libatlas3-base libatlas-base-dev libatlas-test libatlas-doc
Architecture: source
Version: 3.10.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sébastien Villemot 
Description:
 libatlas-base-dev - Automatically Tuned Linear Algebra Software, generic static
 libatlas-doc - Automatically Tuned Linear Algebra Software, documentation
 libatlas-test - Automatically Tuned Linear Algebra Software, test programs
 libatlas3-base - Automatically Tuned Linear Algebra Software, generic shared
Closes: 901099
Changes:
 atlas (3.10.3-7) unstable; urgency=medium
 .
   * libatlas-doc: add Breaks+Replaces libatlas-base-dev (<< 3.10.3-6~)
 Thanks to Andreas Beckmann (Closes: #901099)
Checksums-Sha1:
 672b425f9c41ff7d32ff47c1f6e060ccc76551e1 2190 atlas_3.10.3-7.dsc
 91a1c1dce7c619cf46e18cd91973cb1bc446ab74 159608 atlas_3.10.3-7.debian.tar.xz
 6fdbb7199531f80d64e34c23da802ac6fd9981c9 9179 atlas_3.10.3-7_amd64.buildinfo
Checksums-Sha256:
 38d22cbcc3e2169160bac19097596d6b266b439146176e3c45bababe75ab135a 2190 
atlas_3.10.3-7.dsc
 1f78f051476cd4e0efd9e67732ca5a9d0440f85a5e5a6a1fea4fc0dd683ecc56 159608 
atlas_3.10.3-7.debian.tar.xz
 8583aab958a1fbc4b9cb376bba1d6d9daa19b115f57b34d85d7c230c5b94aac9 9179 
atlas_3.10.3-7_amd64.buildinfo
Files:
 d07f0196c07a1dac06b436c904ae5297 2190 devel optional atlas_3.10.3-7.dsc
 7e1ccfc6ceae209c126b73790eaa7326 159608 devel optional 
atlas_3.10.3-7.debian.tar.xz
 c3db5541749a568ecfb2d2c7ff0c8c9f 9179 devel optional 
atlas_3.10.3-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlscDAEACgkQLOzpNQ7O
vko9dQ//VGQL+qqS3NQG2EEwLl6flOQISeMtBtolsYzl7s4WoIHk8n/iNI4xP+x0
qRz4y2oU4RnX35yESOGNY+l30wGuiiijaRtiqC+goI/gXHEdqJwKX3gv8nBqBK1L
0zg14mJR/PneQWgvnAAEdGk64Ceutcbx6kSyXgb1sGBcVY82vIQYMZjUeuPBf6ci
GVnmBijsIyHEbAc13LIhW+QFhPZNAQll6D3aEmRqfczh7SEBxFaInjUUjeH/Xtn2

Bug#896741: marked as done (themole: missing build dependency on dh-python)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 17:20:29 +
with message-id 
and subject line Bug#896741: fixed in themole 0.3-2
has caused the Debian Bug report #896741,
regarding themole: missing build dependency on dh-python
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.)


-- 
896741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: themole
Version: 0.3-1
Severity: serious
Tags: buster sid

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

...
 fakeroot debian/rules clean
dh clean --with python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 7) line 
1.
BEGIN failed--compilation aborted at (eval 7) line 1.

make: *** [debian/rules:5: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: themole
Source-Version: 0.3-2

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

Debian distribution maintenance software
pp.
Raúl Benencia  (supplier of updated themole 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: Mon, 04 Jun 2018 14:33:38 -0700
Source: themole
Binary: themole
Architecture: source
Version: 0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Raúl Benencia 
Changed-By: Raúl Benencia 
Description:
 themole- automatic SQL injection exploitation tool
Closes: 896741
Changes:
 themole (0.3-2) unstable; urgency=medium
 .
   * Add missing build dependency. (Closes: #896741)
   * Update old references in debian/control.
   * Add Vcs fields.
   * Update debhelper compat level. No modifications were required.
   * Fix insecure-copyright-format-uri.
   * Update Standards-Version. No modifications were required.
Checksums-Sha1:
 bcf8c906e090ea77f0385ed2ed1ecb9365855c6d 1819 themole_0.3-2.dsc
 b4d8151d0ff49752d5b81ab1f59d84f4893173d6 2908 themole_0.3-2.debian.tar.xz
 f4ba688285165d9577c698a734be45c4c66ef19b 5845 themole_0.3-2_source.buildinfo
Checksums-Sha256:
 95d3585771a6e4261211ede8d18438a2dcac7240646c2d6e5a027127a28516b1 1819 
themole_0.3-2.dsc
 4d53d3280a24afb5def5eb0abf9b33418b5e748833d48d4fedc9b0831cccad4b 2908 
themole_0.3-2.debian.tar.xz
 3e82114fe655f8adbb90511bd617f11819da3b469eb83a8a9905261451a973f0 5845 
themole_0.3-2_source.buildinfo
Files:
 6557afd413a3b2ba4157d30af4fa3e95 1819 web optional themole_0.3-2.dsc
 d54ac57978c14e3bd3ca0a8f2f984a8a 2908 web optional themole_0.3-2.debian.tar.xz
 83d276e911268dd6571a8b4531d9ae86 5845 web optional 
themole_0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAlscBuwACgkQq2RfQGKG
p9DpcRAAsOApZKyIb07UtO7T5gcEa55XipyA+7FErNB+hnVzERNuaPLiqWbEPVjD
wcJK/m4VPvOdR0NozS0eLFs67EkZshmK5RyncRNnUMjR23C4DJZpKeWNpd73/nNQ
wDeTno3zFfY1vNPmadOvDAyiyu4P8Q2Qalnc0zYx5dxvxvwZrEiNwyC9e8QlzRUe
uj9dZ9Ypp/F5S8i5A+xRallx6YNrhyOaXTpGeAbCVj9ucDpS71KagTXhnQUCZ5nE
yfqAyfwswKA0kpfNmTgCk5eak/xT+W58D+iEGD+Tl+tay9600HDYw59wgE9B+DGU
/wRLyKVjLXktbA5iFEoY3ViQJLcqnKfCO3xoxJokA9fztwBMB4PPOiagwDjpSwIF
nuSlS85B9VJO8zmMkOSpADrruiSBVtlsVbJUWI5pB25xz8gauCl0ks/UJ35XUK5o
N1DA0ogvUaZLUW1Wkyh6v/tjDF1W+muiJsVGkLKhW76NZjUj0LEdaUDgb1H6Z77y
yOdzupcwqT0bD5Fz0mQxraOzHdvrwNOplMvcO7gb2j5vnkjPlyTaBjve5pUbETtO
7j1CYybxNEBFG7I1rRbtyU9k4VQZfCVWn8b5M67mNGzwDh8BOduFhU3Lnta3rKWG
YcrzvRbdMj7AAfErCZix3e9NfZibh35sfxnX/gKHTNOmI8uOxTQ=
=4EfS
-END PGP SIGNATURE End Message ---

Bug#901001: python3-minimal should Pre-Depend on python3.N-minimal

2018-06-09 Thread Matthias Klose


On 09.06.2018 18:31, Matthias Klose wrote:

On 09.06.2018 11:55, Philipp Kern wrote:

On 6/9/18 7:20 AM, Steve Langasek wrote:

- the package is being upgraded; it is in the common case (when no python
   module names have been dropped from within the package) less important to
   run py3clean because the same files will be recreated shortly afterwards
   by py3compile from the new postinst.


What's the consequence from deleting the files and only recreating them
later? Longer startup time of the interpreter in that short window?


yes, that's the only thing.


Because if it's worse, it'd be good to have py3clean only delete the
obsolete files in the postinst?

Kind regards
Philipp Kern





but as written in the bug report, there is another solution, to have py3clean 
search for the interpreter it uses, and which doesn't need the pre-dependency.

Bug#896592: marked as done (val-and-rick FTBFS with gdc 8)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 16:35:35 +
with message-id 
and subject line Bug#896592: fixed in val-and-rick 0.1a.dfsg1-6
has caused the Debian Bug report #896592,
regarding val-and-rick FTBFS with gdc 8
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.)


-- 
896592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: val-and-rick
Version: 0.1a.dfsg1-5
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/val-and-rick.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/val-and-rick-0.1a.dfsg1'
dh_auto_build -- DFLAGS="-frelease"
make -j1 DFLAGS=-frelease
make[2]: Entering directory '/build/1st/val-and-rick-0.1a.dfsg1'
gdc -o val-and-rick -Iimport -Isrc -Wno-deprecated -frelease -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro import/SDL.d import/SDL_active.d 
import/SDL_audio.d import/SDL_byteorder.d import/SDL_cdrom.d 
import/SDL_copying.d import/SDL_endian.d import/SDL_error.d import/SDL_events.d 
import/SDL_getenv.d import/SDL_joystick.d import/SDL_keyboard.d 
import/SDL_keysym_.d import/SDL_mixer.d import/SDL_mouse.d import/SDL_mutex.d 
import/SDL_quit.d import/SDL_rwops.d import/SDL_syswm.d import/SDL_thread.d 
import/SDL_timer.d import/SDL_types.d import/SDL_version_.d import/SDL_video.d 
import/bulletml.d import/opengl.d import/openglu.d src/abagames/util/actor.d 
src/abagames/util/bulletml/bullet.d src/abagames/util/bulletml/bulletsmanager.d 
src/abagames/util/iterator.d src/abagames/util/logger.d 
src/abagames/util/math.d src/abagames/util/prefmanager.d 
src/abagames/util/rand.d src/abagames/util/sdl/displaylist.d 
src/abagames/util/sdl/gamemanager.d src/abagames/util/sdl/input.d 
src/abagames/util/sdl/luminous.d src/abagames/util/sdl/mainloop.d 
src/abagames/util/sdl/pad.d src/abagames/util/sdl/recordableinput.d 
src/abagames/util/sdl/screen.d src/abagames/util/sdl/screen3d.d 
src/abagames/util/sdl/sdlexception.d src/abagames/util/sdl/sound.d 
src/abagames/util/sdl/texture.d src/abagames/util/tokenizer.d 
src/abagames/util/vector.d src/abagames/vr/barrage.d src/abagames/vr/boot.d 
src/abagames/vr/bulletactor.d src/abagames/vr/bulletactorpool.d 
src/abagames/vr/bulletimpl.d src/abagames/vr/bullettarget.d 
src/abagames/vr/crystal.d src/abagames/vr/enemy.d src/abagames/vr/explosion.d 
src/abagames/vr/field.d src/abagames/vr/gamemanager.d src/abagames/vr/letter.d 
src/abagames/vr/particle.d src/abagames/vr/prefmanager.d 
src/abagames/vr/replay.d src/abagames/vr/screen.d src/abagames/vr/shape.d 
src/abagames/vr/ship.d src/abagames/vr/shot.d src/abagames/vr/soundmanager.d 
src/abagames/vr/stagemanager.d src/abagames/vr/title.d -lSDL -lGL -lGLU 
-lSDL_mixer -lbulletml
cc1d: warning: command line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ 
but not for D
cc1d: warning: command line option '-Wdate-time' is valid for 
C/C++/Fortran/ObjC/ObjC++ but not for D
src/abagames/util/rand.d:8:16: error: module stream is in file 'std/stream.d' 
which cannot be read
 private import std.stream;
^
import path[0] = /usr/include/d
import path[1] = /usr/lib/gcc/x86_64-linux-gnu/8/include/d
import path[2] = /build/1st/val-and-rick-0.1a.dfsg1/import
import path[3] = /build/1st/val-and-rick-0.1a.dfsg1/src
make[2]: *** [Makefile:8: val-and-rick] Error 1


See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894610#12 for background.
--- End Message ---
--- Begin Message ---
Source: val-and-rick
Source-Version: 0.1a.dfsg1-6

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated val-and-rick 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, 09 Jun 2018 17:55:40 +0200
Source: val-and-rick
Binary: val-and-rick val-and-rick-data
Architecture: source
Version: 0.1a.dfsg1-6
Distribution: unstable
Urgency:

Bug#901001: python3-minimal should Pre-Depend on python3.N-minimal

2018-06-09 Thread Matthias Klose


On 09.06.2018 11:55, Philipp Kern wrote:

On 6/9/18 7:20 AM, Steve Langasek wrote:

- the package is being upgraded; it is in the common case (when no python
   module names have been dropped from within the package) less important to
   run py3clean because the same files will be recreated shortly afterwards
   by py3compile from the new postinst.


What's the consequence from deleting the files and only recreating them
later? Longer startup time of the interpreter in that short window?


yes, that's the only thing.


Because if it's worse, it'd be good to have py3clean only delete the
obsolete files in the postinst?

Kind regards
Philipp Kern

Bug#896631: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 16:05:18 +
with message-id 
and subject line Bug#896631: fixed in python-cryptography 2.2.2-1
has caused the Debian Bug report #896631,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
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.)


-- 
896631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx
Version: 1.7.2-1
Severity: serious
Control: affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat 
src:julia src:mako src:prospector src:pyevolve src:pymvpa2 
src:python-cryptography src:python-expyriment src:python-numpy src:python-scipy

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alembic.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bcfg2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bottleneck.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/julia.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mako.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prospector.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyevolve.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-expyriment.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-numpy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlalchemy.html

Example (from alembic):

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/alembic-0.9.7'
sphinx-build -b html docs/build 
/build/1st/alembic-0.9.7/debian/alembic/usr/share/doc/alembic/html
Running Sphinx v1.7.2

Extension error:
Could not import extension changelog (exception: cannot import name 'Directive')
make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2
--- End Message ---
--- Begin Message ---
Source: python-cryptography
Source-Version: 2.2.2-1

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

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated 
python-cryptography 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, 09 Jun 2018 16:28:09 +0200
Source: python-cryptography
Binary: python-cryptography python3-cryptography python-cryptography-doc
Architecture: source
Version: 2.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Tristan Seligmann 
Description:
 python-cryptography - Python library exposing cryptographic recipes and 
primitives (Pyt
 python-cryptography-doc - Python library exposing cryptographic recipes and 
primitives (doc
 python3-cryptography - Python library exposing cryptographic recipes and 
primitives (Pyt
Closes: 884484 896631 901076
Changes:
 python-cryptography (2.2.2-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
 .
   [ Tristan Seligmann ]
   * New upstream release (closes: #901076).
 - Fixed compatibility with newer Sphinx (closes: #896631).
   * Populate debian/upstream/metadata.
   * Bump Standards-Version to 4.1.4 (no changes).
   * Bump debhelper compat level to 11.
   * Tighten vectors dependency for autopkgtests (closes: #884484).
Checksums-Sha1:
 c5a4462a16b8b89cbd8c8571a382987b0ef4fa6f 3310 python-cryptography_2.2.2-1.dsc

Bug#901158: postgis: FTBFS: testsuite failure

2018-06-09 Thread Sebastiaan Couwenberg

Control: tags -1 upstream
Control: forwarded -1 https://trac.osgeo.org/postgis/ticket/4104

On 06/09/2018 05:05 PM, Niko Tyni wrote:
> This package fails to build from source on current sid/amd64.

Thanks for reporting this issue, I've forwarded it upstream.

In the mean time I'll likely skip this test or ignore the failure(s).

Kind Regards,

Bas

Processed: Re: Bug#901158: postgis: FTBFS: testsuite failure

2018-06-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 upstream
Bug #901158 [postgis] postgis: FTBFS: testsuite failure
Added tag(s) upstream.
> forwarded -1 https://trac.osgeo.org/postgis/ticket/4104
Bug #901158 [postgis] postgis: FTBFS: testsuite failure
Set Bug forwarded-to-address to 'https://trac.osgeo.org/postgis/ticket/4104'.

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

Bug#896591: marked as done (tumiki-fighters FTBFS with gdc 8)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 15:20:11 +
with message-id 
and subject line Bug#896591: fixed in tumiki-fighters 0.2.dfsg1-9
has caused the Debian Bug report #896591,
regarding tumiki-fighters FTBFS with gdc 8
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.)


-- 
896591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tumiki-fighters
Version: 0.2.dfsg1-8
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/tumiki-fighters-0.2.dfsg1'
dh_auto_build -- DFLAGS="-frelease"
make -j1 DFLAGS=-frelease
make[2]: Entering directory '/build/1st/tumiki-fighters-0.2.dfsg1'
gdc -o tumiki-fighters -Wno-deprecated -Iimport -Isrc -frelease -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro import/SDL.d import/SDL_active.d 
import/SDL_audio.d import/SDL_byteorder.d import/SDL_cdrom.d 
import/SDL_copying.d import/SDL_endian.d import/SDL_error.d import/SDL_events.d 
import/SDL_getenv.d import/SDL_joystick.d import/SDL_keyboard.d 
import/SDL_keysym_.d import/SDL_mixer.d import/SDL_mouse.d import/SDL_mutex.d 
import/SDL_quit.d import/SDL_rwops.d import/SDL_syswm.d import/SDL_thread.d 
import/SDL_timer.d import/SDL_types.d import/SDL_version_.d import/SDL_video.d 
import/bulletml.d import/opengl.d import/openglu.d 
src/abagames/tf/attractmanager.d src/abagames/tf/barragemanager.d 
src/abagames/tf/boot.d src/abagames/tf/bulletactor.d 
src/abagames/tf/bulletactorpool.d src/abagames/tf/bulletinst.d 
src/abagames/tf/bullettarget.d src/abagames/tf/damagegauge.d 
src/abagames/tf/enemy.d src/abagames/tf/enemyspec.d src/abagames/tf/field.d 
src/abagames/tf/fragment.d src/abagames/tf/gamemanager.d 
src/abagames/tf/letterrender.d src/abagames/tf/mobileletter.d 
src/abagames/tf/morphbullet.d src/abagames/tf/particle.d 
src/abagames/tf/prefmanager.d src/abagames/tf/scoresign.d 
src/abagames/tf/screen.d src/abagames/tf/ship.d src/abagames/tf/soundmanager.d 
src/abagames/tf/splinter.d src/abagames/tf/stagemanager.d 
src/abagames/tf/stuckenemy.d src/abagames/tf/tumiki.d 
src/abagames/tf/tumikiset.d src/abagames/util/actor.d 
src/abagames/util/actorpool.d src/abagames/util/bulletml/bullet.d 
src/abagames/util/bulletml/bulletsmanager.d src/abagames/util/csv.d 
src/abagames/util/iterator.d src/abagames/util/logger.d 
src/abagames/util/prefmanager.d src/abagames/util/rand.d 
src/abagames/util/sdl/gamemanager.d src/abagames/util/sdl/input.d 
src/abagames/util/sdl/mainloop.d src/abagames/util/sdl/pad.d 
src/abagames/util/sdl/screen.d src/abagames/util/sdl/screen3d.d 
src/abagames/util/sdl/sdlexception.d src/abagames/util/sdl/sound.d 
src/abagames/util/sdl/texture.d src/abagames/util/vector.d -lSDL -lGL 
-lSDL_mixer -lbulletml
cc1d: warning: command line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ 
but not for D
cc1d: warning: command line option '-Wdate-time' is valid for 
C/C++/Fortran/ObjC/ObjC++ but not for D
src/abagames/util/rand.d:8:16: error: module stream is in file 'std/stream.d' 
which cannot be read
 private import std.stream;
^
import path[0] = /usr/include/d
import path[1] = /usr/lib/gcc/x86_64-linux-gnu/8/include/d
import path[2] = /build/1st/tumiki-fighters-0.2.dfsg1/import
import path[3] = /build/1st/tumiki-fighters-0.2.dfsg1/src
make[2]: *** [Makefile:8: tumiki-fighters] Error 1


See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894610#12 for background.
--- End Message ---
--- Begin Message ---
Source: tumiki-fighters
Source-Version: 0.2.dfsg1-9

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated tumiki-fighters 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, 09 Jun 2018 16:52:29 +0200
Source: tumiki-fighters
Binary:

Bug#898917: marked as done (ruby2.5: FTBFS with cowbuilder, requires network access)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 15:20:03 +
with message-id 
and subject line Bug#898917: fixed in ruby2.5 2.5.1-2
has caused the Debian Bug report #898917,
regarding ruby2.5: FTBFS with cowbuilder, requires network access
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.)


-- 
898917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby2.3
Version: 2.3.3-1+deb9u2
Severity: serious

Other than the Failures in #889117, current ruby2.3 package fails to
build due to Rinda TestRingFinger and TestRingServer trying to access
network ressources:

…
  6) Error:
Rinda::TestRingFinger#test_make_socket_ipv4_multicast:
Errno::ENETUNREACH: Network is unreachable - connect(2) for 239.0.0.1:7647
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `connect'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `make_socket'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:782:in 
`test_make_socket_ipv4_multicast'

  7) Error:
Rinda::TestRingFinger#test_make_socket_ipv4_multicast_hops:
Errno::ENETUNREACH: Network is unreachable - connect(2) for 239.0.0.1:7647
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `connect'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `make_socket'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:809:in 
`test_make_socket_ipv4_multicast_hops'

  8) Error:
Rinda::TestRingServer#test_make_socket_ipv4_multicast:
Errno::ENODEV: No such device - setsockopt(2)
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `setsockopt'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `make_socket'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:626:in 
`test_make_socket_ipv4_multicast'

  9) Error:
Rinda::TestRingServer#test_ring_server_ipv4_multicast:
Errno::ENODEV: No such device - setsockopt(2)
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `setsockopt'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `make_socket'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:108:in `block in initialize'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:106:in `each'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:106:in `initialize'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:667:in `new'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:667:in 
`test_ring_server_ipv4_multicast'

15919 tests, 2236057 assertions, 5 failures, 4 errors, 82 skips
…

I am preparing a commit to solve this in the stretch git branch.

cheers,

Santiago


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_CO:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby2.5
Source-Version: 2.5.1-2

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby2.5 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, 09 Jun 2018 11:50:20 -0300
Source: ruby2.5
Binary: ruby2.5 libruby2.5 ruby2.5-dev ruby2.5-doc
Architecture: source
Version: 2.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Description:
 libruby2.5 - Libraries necessary to run Ruby 2.5
 ruby2.5- Interpreter of object-oriented scripting language Ruby
 ruby2.5-dev - Header files for compiling extension modules for the Ruby 2.5
 ruby2.5-doc - Documentation for Ruby 2.5
Closes: 896509 898917 899267
Changes:
 ruby2.5 (2.5.1-2) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * debian/tests/control: ignore output on stderr
   * debian/tests/bundled-gems: only fail on missing gems. Only warn if version
 found is not new enough
   * libruby2.5: add dependency on ruby-xmlrpc
 .
   [ Samuel

Bug#898917: Bug #898917 in ruby marked as pending

2018-06-09 Thread santiagorr

Control: tag -1 pending

Hello,

Bug #898917 in ruby reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/ruby-team/ruby/commit/ee59abd23dfae33f2afcd54b6f17d9432a8a9fab


Exclude Rinda TestRingFinger and TestRingServer test units requiring network 
access

Closes: #898917

Signed-off-by: Santiago R.R 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/898917

Bug#901121: marked as done (turing: missing dependency on python3-matplotlib)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 15:09:05 +
with message-id 
and subject line Bug#901121: fixed in turing 0.10~beta-2
has caused the Debian Bug report #901121,
regarding turing: missing dependency on python3-matplotlib
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.)


-- 
901121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: turing
Version: 0.10~beta-1
Severity: serious

Dear Maintainer,

Launching turing on the command line yields:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-lbrenta'
NoneType: None
Traceback (most recent call last):
  File "/usr/share/turing/src/main.py", line 86, in 
from forms import mainwindow
  File "/usr/share/turing/src/forms/mainwindow.py", line 15, in 
from matplotlib.axes import Axes
ModuleNotFoundError: No module named 'matplotlib'

Installing the package python3-matplotlib solves this problem.

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

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

Versions of packages turing depends on:
ii  python3 3.6.5-3
ii  python3-altgraph0.15~repack0-2
ii  python3-autopep81.3.5-2
ii  python3-cycler  0.10.0-1
ii  python3-dateutil2.6.1-1
ii  python3-docutils0.14+dfsg-3
ii  python3-future  0.15.2-4
ii  python3-jedi0.11.1-1
ii  python3-kiwisolver  1.0.1-2
ii  python3-macholib1.9+repack0-1
ii  python3-numpy   1:1.14.3-2
ii  python3-parso   0.1.1-1
ii  python3-pefile  2017.11.5-2
ii  python3-pep81.7.1-1
ii  python3-pyflakes1.6.0-1
ii  python3-pygments2.2.0+dfsg-1
ii  python3-pyparsing   2.2.0+dfsg1-2
ii  python3-pyqt5   5.10.1+dfsg-2
ii  python3-tz  2018.4-1

turing recommends no packages.

turing suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: turing
Source-Version: 0.10~beta-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated turing 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, 09 Jun 2018 15:52:25 +0200
Source: turing
Binary: turing
Architecture: source all
Version: 0.10~beta-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 turing - assistant to learn algorithms and programming languages
Closes: 901121
Changes:
 turing (0.10~beta-2) unstable; urgency=medium
 .
   * added a dependency on python3-matplotlib. Closes: #901121
Checksums-Sha1:
 75df71340e69a1d1a88601cae1d64a21b817a113 1847 turing_0.10~beta-2.dsc
 333973be2d7939c95adc5dd74b55f27208c5ee38 10820 turing_0.10~beta-2.debian.tar.xz
 bf94b381e23ded26b6c3f32cb0ae59a8a87c90cc 2778588 turing_0.10~beta-2_all.deb
 dc588f82ad698adfac294ddafa7f250d4449e6eb 5909 
turing_0.10~beta-2_amd64.buildinfo
Checksums-Sha256:
 267120c162dfec35368f760b32cb444e0334f530e30c1f3b3d30e71fc3d7d987 1847 
turing_0.10~beta-2.dsc
 1dd2959466c7a6e541fc3db4dd27d56f82fe4bf1c75e4449cd996fd9e3204773 10820 
turing_0.10~beta-2.debian.tar.xz
 3d05c3681504515f0782b51dff8e0cdda244356074d31173b5850bebf564f2bb 2778588 
turing_0.10~beta-2_all.deb
 3f4e39b77ab4b61d8b39844407e6daf409b0e011e499482d73590fe192cde53f 5909 
turing_0.10~beta-2_amd64.buildinfo
Files:
 fc98ea2802c06478b1792f121d5d193e 1847 x11 optional turing_0.10~beta-2.dsc
 cd1c4a53b674e16cae086a01c763346a 10820 x11 optional 
turing_0.10~beta-2.debian.tar.xz
 d583a4746afa9de775a96c1d6f9d9853 2778588 x11 optional 
turing_0.10~beta-2_all.deb
 2cc621fdfd254312d227530b2e029466 5909 x11 optional 
turing_0.10~beta-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAlsb3UIACgkQHCgWkHE2

Processed: Bug #898917 in ruby marked as pending

2018-06-09 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #898917 [ruby2.5] ruby2.5: FTBFS with cowbuilder, requires network access
Added tag(s) pending.

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

Bug#901041: marked as done (libviennacl-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libviennacl-dev/README.gz)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 15:09:18 +
with message-id 
and subject line Bug#901041: fixed in viennacl 1.7.1+dfsg1-4
has caused the Debian Bug report #901041,
regarding libviennacl-doc: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/doc/libviennacl-dev/README.gz
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.)


-- 
901041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libviennacl-doc
Version: 1.7.1+dfsg1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libviennacl-doc.
  Preparing to unpack .../libviennacl-doc_1.7.1+dfsg1-3_all.deb ...
  Unpacking libviennacl-doc (1.7.1+dfsg1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libviennacl-doc_1.7.1+dfsg1-3_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libviennacl-dev/README.gz', which is 
also in package libviennacl-dev 1.7.1+dfsg1-2

This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libviennacl-dev=1.7.1+dfsg1-2_libviennacl-doc=1.7.1+dfsg1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: viennacl
Source-Version: 1.7.1+dfsg1-4

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated viennacl 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, 09 Jun 2018 16:33:26 +0200
Source: viennacl
Binary: libviennacl-dev libviennacl-doc
Architecture: source
Version: 1.7.1+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libviennacl-dev - Scientific computing library written in C++ based on OpenCL
 libviennacl-doc - ViennaCL API and user documentation
Closes: 901041
Changes:
 viennacl (1.7.1+dfsg1-4) unstable; urgency=medium
 .
   * Team upload.
   * [113b0e5] Add Breaks/Replaces for the libviennacl-doc. (Closes: #901041)
Checksums-Sha1:
 86e71cbce4b182ad27ad433cc59e064e4c973795 2429 viennacl_1.7.1+dfsg1-4.dsc
 6d3ce9d48b0eae46f355b2cb36f38a57e39bc94b 1299512 
viennacl_1.7.1+dfsg1-4.debian.tar.xz
 0db5fa30660b278e1bdb822c01ce51ef046ae77d 10435 
viennacl_1.7.1+dfsg1-4_source.buildinfo
Checksums-Sha256:
 4ebcd000eade821919a3c27bad6e228d9f105cc5390a466384baa0d5dfdb411a 2429 
viennacl_1.7.1+dfsg1-4.dsc
 e351feb5530156620389576c0cf2bfe8533ea0900476206b3eb729bb2fc6f990 1299512 
viennacl_1.7.1+dfsg1-4.debian.tar.xz
 505027250ac9db155dc7d9f5f75aa0eddc970bffd18996ee915f96aa7ac14a64 10435 
viennacl_1.7.1+dfsg1-4_source.buildinfo
Files:
 6c6d55ed50866f20706285523c4aad4f 2429 science optional 
viennacl_1.7.1+dfsg1-4.dsc
 9f85424d9e289e86864eb27971acab9f 1299512 science optional 
viennacl_1.7.1+dfsg1-4.debian.tar.xz
 820f1fbc4ac51abc992bfab8d10a94fd 10435 science optional 
viennacl_1.7.1+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlsb5XwACgkQ0+Fzg8+n
/wZ2bA//fO+36QIX6QVaVYSzAkyEK/I+VTvi7cB+tP4OWTUk7gsuNSwmWrfszRaI
LedeDzxSrV1NRNXTVIriZSj4cmAQpzhai1wdIVSSdbjZdNCESj1rZFK0hc65wTVi
YuttrJtHu+ksP1c/n5zhS6zDlb2E5O7wtZWEHdmknd32rvCLzu8yT0Fv9MjwKNNI
UcCwXT+pQNizHSs6x9w/Pt9Pv8lYRa2CLcxQYSUxlmNtTU5jOiOTdOoskQz8SgVW
iseebeOeVPANSbV4dGKE+bJO4/UQghnpPS6XtTTnAXMu3vG/hpic01SgzI9Jro49
YlVqiXI8jLnNR6L20JyX6eBrxfy0vuPUiv6VoHQZ41ka9ZUbIXBe2uBtHxiQf9el
CIz4nOY6PYeCysBpFyCcmqrgoXqy/p856WGLwS40AzFiU+TdEvgtvCQvctRbURW2
wsPQtm2FDuAPA9RqKpXLssXXLpF40DMMRn78ypOUuE35tRuD8M3hPOMMgTG8anm0

Bug#900834: marked as done (perl: CVE-2018-12015: Archive::Tar: directory traversal)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 15:08:26 +
with message-id 
and subject line Bug#900834: fixed in perl 5.26.2-6
has caused the Debian Bug report #900834,
regarding perl: CVE-2018-12015: Archive::Tar: directory traversal
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.)


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

Source: perl
Version: 5.26.2-5
Tags: security

By default, the Archive::Tar module doesn't allow extracting files 
outside the current working directory. However, you can bypass this 
secure extraction mode easily by putting a symlink and a regular file 
with the same name into the tarball.


I've attached proof of concept tarball, which makes Archive::Tar create 
/tmp/moo, regardless of what the current working directory is:


  $ tar -tvvf traversal.tar.gz
  lrwxrwxrwx root/root 0 2018-06-05 18:55 moo -> /tmp/moo
  -rw-r--r-- root/root 4 2018-06-05 18:55 moo

  $ pwd
  /home/jwilk

  $ ls /tmp/moo
  ls: cannot access '/tmp/moo': No such file or directory

  $ perl -MArchive::Tar -e 'Archive::Tar->extract_archive("traversal.tar.gz")'

  $ ls /tmp/moo
  /tmp/moo

--
Jakub Wilk


traversal.tar.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.26.2-6

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

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

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Jun 2018 13:38:44 +0100
Source: perl
Binary: perl-base perl-doc perl-debug libperl5.26 libperl-dev perl-modules-5.26 
perl
Architecture: source
Version: 5.26.2-6
Distribution: unstable
Urgency: high
Maintainer: Niko Tyni 
Changed-By: Dominic Hargreaves 
Description:
 libperl-dev - Perl library: development files
 libperl5.26 - shared Perl library
 perl   - Larry Wall's Practical Extraction and Report Language
 perl-base  - minimal Perl system
 perl-debug - debug-enabled Perl interpreter
 perl-doc   - Perl documentation
 perl-modules-5.26 - Core Perl modules
Closes: 900834
Changes:
 perl (5.26.2-6) unstable; urgency=high
 .
   * [SECURITY] CVE-2018-12015: fix directory traversal vulnerability
 in Archive-Tar (Closes: #900834)
Checksums-Sha1:
 04a71eff631df54db5286fcbac58fc1ad7977c1d 2776 perl_5.26.2-6.dsc
 ebfd67b4bc36c0f89ed8a35af1a7cc5da76db7d3 167332 perl_5.26.2-6.debian.tar.xz
 9f080dfd0f0864a9c1e4df57f13f8433735e1186 5184 perl_5.26.2-6_source.buildinfo
Checksums-Sha256:
 8441ca46715247218cbc19cabd15126f4fbacd544b6ce6446ea7b2ba2541f16a 2776 
perl_5.26.2-6.dsc
 6b3a39b03e80498d7e0d02c544aa24d4d9fdfc4afd85a91375aa2685d882d178 167332 
perl_5.26.2-6.debian.tar.xz
 fd71e724ea48b4828c48af7104453780dc188328bcadeb7cf9593550bb14972f 5184 
perl_5.26.2-6_source.buildinfo
Files:
 99abfe79c6f0498735dc71dcdaf79714 2776 perl standard perl_5.26.2-6.dsc
 87a276b0bb1e43151a0e6490f130b22d 167332 perl standard 
perl_5.26.2-6.debian.tar.xz
 cb2a35df5f798150482b957eb6eeedf7 5184 perl standard 
perl_5.26.2-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJBBAEBCAArFiEEy0llJ/kAnyscGnbawAV+cU1pT7IFAlsb3zUNHGRvbUBlYXJ0
aC5saQAKCRDABX5xTWlPstsOD/9zRnfCTFseLXuoSG2rVhRTuKagm234vLJ0LXTY
Y0g2Ol7Ayw8ABgyifYWqJDFs3WL70xWKdB3eLYsCSQD6jOPbSoTK1UjsavxD7tFG
bk72lVaDF8bSam/KEBIH67Ysb5/Y1tfBz3aWVE5z2fTOTbNDcph0cgvOfJ0SnU5h
3PF1FnZBJ91jpW279AIlbv+s4JbQZXXt9eUiZKT6WZnX5dOoEYTPG1Ky/ttwZFXv
ZA6xlTe+pyTaKvlQHOnKv76i8vWm6geQNzYMTde/tUqWv2a72Oq/HTcb7PiBYT/7
0JsdN2rWgq1tpTqAQ51MSZM3RkOZlgzT+J43iO9mxat6okzgORbyqEPwABbKXopd
L90PdvWoapLQFjrx5mQgZV+nyO8WhLXOKWir0zpOAZ/CjOhh249GdJaLplGOn11u
IAp8POD4or67dZxRro1x7YdkTV8GX6vkhWtEcKr7CnTRCDeNhe9jD8QUSClqN+a/
G1dAo7gaOrEBSCwdyWOiSQmmZyFykWCOPjl3/HiHFaC5t8C+SP64Qc+U0UzTa28/
u8uvUZ0uekSt+KGScXVP7jsVt1i8AQP/xTCCynsCdmOYpiLoJ793FyG0+VB1lnYz
8uRnHqBqcdizIZMnXUWnfvxV0AGLzMB3RCQLOZhdD8tipnsSJIsOZ12eMPcYFC6H
gJCkzA==
=OI+z
-END PGP SIGNATURE End Message ---

Bug#901158: postgis: FTBFS: testsuite failure

2018-06-09 Thread Niko Tyni

Package: postgis
Version: 2.4.4+dfsg-1
Severity: serious

This package fails to build from source on current sid/amd64.

   ### /tmp/pgis_reg/test_50_diff ###
  --- rt_gdalwarp_expected  2018-04-06 05:05:52.0 +
  +++ /tmp/pgis_reg/test_50_out 2018-06-09 14:27:15.049036062 +
  @@ -19,8 +19,8 @@
   0.17|993309|243|243|1|50.000|50.000|0.000|0.000|950760.000|1396957.000|t|t|t
   
0.18|992163|10|10|1|1000.000|-1000.000|3.000|3.000|-500030.000|60.000|t|t|t
   
0.19|993310|12|12|1|1009.894|-1009.894|3.000|3.000|950691.792|1409281.783|t|t|t
  
-0.2|993309|12|12|1|1009.916|-1009.916|0.000|0.000|950762.305|1409088.896|t|t|t
  
-0.20|993309|12|12|1|1009.916|-1009.916|1.000|3.000|950742.107|1409088.896|t|t|t
  
+0.2|993309|12|12|1|1009.876|-1009.876|0.000|0.000|950808.447|1409091.640|t|t|t
  
+0.20|993309|12|12|1|1009.876|-1009.876|1.000|3.000|950788.250|1409091.640|t|t|t
   0.21|993310|24|24|1|500.000|500.000|3.000|3.000|950657.188|1397356.783|t|t|t
   0.22|993310|26|26|1|500.000|500.000|0.000|6.000|950452.000|1396632.000|t|t|t
   0.23|984269|12|8|1|0.012|-0.012|0.000|0.000|-107.029|50.206|t|t|t
  @@ -63,12 +63,12 @@
   
1.9|992163|11|10|1|1000.000|-1000.000|0.000|0.000|-51.000|60.000|t|t|t
   
2.1|993310|12|12|1|1009.894|-1009.894|0.000|0.000|950732.188|1409281.783|t|t|t
   2.10|993310|24|24|1|500.000|500.000|0.000|0.000|950732.188|1397281.783|t|t|t
  
-2.11|993309|121|121|1|100.000|100.000|0.000|0.000|950762.305|1396988.896|t|t|t
  
+2.11|993309|121|121|1|100.000|100.000|0.000|0.000|950808.447|1396991.640|t|t|t
   2.12|993310|6|6|1|2000.000|2000.000|0.000|0.000|950732.188|1397281.783|t|t|t
   2.13|993310|8|8|1|1500.000|1500.000|0.000|0.000|950732.188|1397281.783|t|t|t
   2.14|993310|24|24|1|500.000|500.000|0.000|0.000|950732.188|1397281.783|t|t|t
   2.15|993310|16|16|1|750.000|750.000|0.000|0.000|950732.188|1397281.783|t|t|t
  
-2.2|993309|12|12|1|1009.916|-1009.916|0.000|0.000|950762.305|1409088.896|t|t|t
  
+2.2|993309|12|12|1|1009.876|-1009.876|0.000|0.000|950808.447|1409091.640|t|t|t
   2.3|994269|12|8|1|0.012|-0.012|0.000|0.000|-107.029|50.206|t|t|t
   2.4|
   
2.5|993310|12|12|1|1009.894|-1009.894|0.000|0.000|950732.188|1409281.783|t|t|t
   ### end of log dumps ###
  make[1]: *** [debian/rules:200: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>/postgis-2.4.4+dfsg'
  make: *** [debian/rules:111: build] Error 2
 
Full build log attached.
-- 
Niko Tyni   nt...@debian.org


postgis_amd64-2018-06-09T14:19:48Z.build.gz
Description: application/gzip

Bug#894045: marked as done (libvncserver: CVE-2018-7225)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 15:06:32 +
with message-id 
and subject line Bug#894045: fixed in libvncserver 0.9.11+dfsg-1.1
has caused the Debian Bug report #894045,
regarding libvncserver: CVE-2018-7225
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.)


-- 
894045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvncserver
Version: 0.9.11+dfsg-1
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/LibVNC/libvncserver/issues/218

Hi,

the following vulnerability was published for libvncserver.

CVE-2018-7225[0]:
| An issue was discovered in LibVNCServer through 0.9.11.
| rfbProcessClientNormalMessage() in rfbserver.c does not sanitize
| msg.cct.length, leading to access to uninitialized and potentially
| sensitive data or possibly unspecified other impact (e.g., an integer
| overflow) via specially crafted VNC packets.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-7225
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7225
[1] https://github.com/LibVNC/libvncserver/issues/218

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libvncserver
Source-Version: 0.9.11+dfsg-1.1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libvncserver 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, 05 Jun 2018 14:43:47 +0200
Source: libvncserver
Binary: libvncclient1 libvncserver1 libvncserver-dev libvncserver-config 
libvncclient1-dbg libvncserver1-dbg
Architecture: source
Version: 0.9.11+dfsg-1.1
Distribution: unstable
Urgency: high
Maintainer: Peter Spiess-Knafl 
Changed-By: Markus Koschany 
Description:
 libvncclient1 - API to write one's own VNC server - client library
 libvncclient1-dbg - debugging symbols for libvncclient
 libvncserver-config - API to write one's own VNC server - library utility
 libvncserver-dev - API to write one's own VNC server - development files
 libvncserver1 - API to write one's own VNC server
 libvncserver1-dbg - debugging symbols for libvncserver
Closes: 894045
Changes:
 libvncserver (0.9.11+dfsg-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Fix CVE-2018-7225: Uninitialized and potentially sensitive data could be
 accessed by remote attackers because the msg.cct.length in rfbserver.c was
 not sanitized. (Closes: #894045)
Checksums-Sha1:
 24d0d5d3e284ff00633d82c94ff4f8282d6e7c6f 2557 libvncserver_0.9.11+dfsg-1.1.dsc
 8ac6f4f1afc0be5c10d12dfa8cbcdb459e999810 13448 
libvncserver_0.9.11+dfsg-1.1.debian.tar.xz
 4bea25e53d2cc6c98d85483b014e24ee51f24e93 7973 
libvncserver_0.9.11+dfsg-1.1_amd64.buildinfo
Checksums-Sha256:
 fcbf42e1e3bd3c12ab2f06001041e6045957596a995765781f4c2ba3477269dc 2557 
libvncserver_0.9.11+dfsg-1.1.dsc
 54b105ae3d2e958d8bf3db3f3eabc318af0c11327fabe58a3aff363e77f481a9 13448 
libvncserver_0.9.11+dfsg-1.1.debian.tar.xz
 b5ae2289af8bce401ad6ca651751e0c15b98f6c3e4a2b1ebc1defb97dbb6eff5 7973 
libvncserver_0.9.11+dfsg-1.1_amd64.buildinfo
Files:
 c8dee64e4bd7ccf117529a9d8084e078 2557 libs optional 
libvncserver_0.9.11+dfsg-1.1.dsc
 12ad2a36c39a2de61a70c611a67237a6 13448 libs optional 
libvncserver_0.9.11+dfsg-1.1.debian.tar.xz
 6f06736dad01e1c5695199fc570682e3 7973 libs optional 
libvncserver_0.9.11+dfsg-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlsb3zlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk9mIQALpWFMnNhpfjuB8JUClDnBboW2HP7xUh5NzI
wly6KrJF55HFgIWt9yK+XvoueDcsUYUpA+9DJ/vzShJpMJO4Ry1gRR+M9fK+b7F3

Bug#896141: msxpertsuite: binary-all FTBFS

2018-06-09 Thread Santiago Vila

While we are at it: Is this bug not already fixed?

https://buildd.debian.org/status/package.php?p=msxpertsuite

If it is, please close it with a Version string.

Thanks.

Processed: found 900834 in 5.28.0~rc2-1

2018-06-09 Thread Debian Bug Tracking System

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

> found 900834 5.28.0~rc2-1
Bug #900834 [src:perl] perl: CVE-2018-12015: Archive::Tar: directory traversal
Marked as found in versions perl/5.28.0~rc2-1.
> thanks
Stopping processing here.

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

Bug#896141: msxpertsuite: binary-all FTBFS

2018-06-09 Thread Santiago Vila

retitle 896141 msxpertsuite: FTBFS with new Tex Live packages
thanks

Hi.

The package FTBFS with and without "dpkg-buildpackage -A" so I'm
dropping the binary-all part from the subject.

(The old title was a little bit misleading to me since I am also
occasionally building the entire archive to catch those
"dpkg-buildpackage -A" bugs).

> > See the inputenc package documentation for explanation.
> > Type  H   for immediate help.
> > ...
> > l.122 ...\'Ecole Polytechnique} (Institut Européen
> >   de
> > ./preface.tex:122:  ==> Fatal error occurred, no output PDF file produced!
> > Transcript written on massxpert-doc.log.
> 
> Why doesn't the build stop at that point?

Very good point. I've just reported that separately as Bug #901154.

I guess that's probably the reason it fails in a different
way depending on "dpkg-buildpackage -A" being used or not.

Thanks.

Processed: Re: Bug#896141: msxpertsuite: binary-all FTBFS

2018-06-09 Thread Debian Bug Tracking System

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

> retitle 896141 msxpertsuite: FTBFS with new Tex Live packages
Bug #896141 [src:msxpertsuite] msxpertsuite: binary-all FTBFS
Changed Bug title to 'msxpertsuite: FTBFS with new Tex Live packages' from 
'msxpertsuite: binary-all FTBFS'.
> thanks
Stopping processing here.

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

Bug#901154: msxpertsuite: Does not trap errors in upstream Makefile

2018-06-09 Thread Santiago Vila

Package: msxpertsuite
Version: 5.3.0-1
Severity: serious

In Bug #896141, where the build fails because of new Tex Live,
Adrian Bunk points out why the build process does not stop
as soon as there is an error.

Quote:

> > ./preface.tex:122:  ==> Fatal error occurred, no output PDF file produced!
> > Transcript written on massxpert-doc.log.
>
> Why doesn't the build stop at that point?

This is in fact a violation of Policy 4.6, "Error trapping in makefiles":

https://www.debian.org/doc/debian-policy/#error-trapping-in-makefiles

so I'm reporting it here separately.


I have not tested it, but maybe the fix could be as easy as removing the
hyphen prefix from pdflatex command in these two Makefiles:

massxpert/user-manual/Makefile
minexpert/user-manual/Makefile

Thanks.

Bug#901102: marked as done (firehol-doc,firehol-tools-doc,fireqos-doc: fails to install, trying to overwrite other packages files)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 13:34:27 +
with message-id 
and subject line Bug#901102: fixed in firehol 3.1.5+ds1-1
has caused the Debian Bug report #901102,
regarding firehol-doc,firehol-tools-doc,fireqos-doc: fails to install, trying 
to overwrite other packages files
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.)


-- 
901102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firehol-doc,firehol-tools-doc,fireqos-doc
Version: 3.1.5+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package fireqos-doc.
  Preparing to unpack .../fireqos-doc_3.1.5+ds-2_all.deb ...
  Unpacking fireqos-doc (3.1.5+ds-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fireqos-doc_3.1.5+ds-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/fireqos/README', which is also in 
package fireqos 3.1.5+ds-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/fireqos-doc_3.1.5+ds-2_all.deb

  Selecting previously unselected package firehol-doc.
  Preparing to unpack .../firehol-doc_3.1.5+ds-2_all.deb ...
  Unpacking firehol-doc (3.1.5+ds-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/firehol-doc_3.1.5+ds-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/firehol/README', which is also in 
package firehol 3.1.5+ds-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/firehol-doc_3.1.5+ds-2_all.deb

  Selecting previously unselected package firehol-tools-doc.
  Preparing to unpack .../firehol-tools-doc_3.1.5+ds-2_all.deb ...
  Unpacking firehol-tools-doc (3.1.5+ds-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/firehol-tools-doc_3.1.5+ds-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/firehol-tools/README', which is also in 
package firehol-tools 3.1.5+ds-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/firehol-tools-doc_3.1.5+ds-2_all.deb


This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


fireqos=3.1.5+ds-2_fireqos-doc=3.1.5+ds-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: firehol
Source-Version: 3.1.5+ds1-1

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated firehol 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, 09 Jun 2018 13:29:02 +
Source: firehol
Binary: firehol firehol-doc fireqos fireqos-doc firehol-tools firehol-tools-doc 
firehol-common
Architecture: source
Version: 3.1.5+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Jerome Benoit 
Changed-By: Jerome Benoit 
Description:
 firehol- easy to use but powerful iptables stateful firewall (program)
 firehol-common - easy to use but powerful traffic suite (common library)
 firehol-doc - easy to use but powerful iptables stateful firewall (docs)
 firehol-tools - easy to use but powerful traffic suite (extra tools)
 firehol-tools-doc - easy to use but powerful traffic suite (extra tools docs)
 fireqos- easy to use but powerful traffic shaping tool (program)
 fireqos-doc - easy to use but powerful traffic shaping tool (docs)
Closes: 901102
Changes:
 firehol (3.1.5+ds1-1) unstable; urgency=medium
 .
   * RC bug fix release (Closes: #901102), redundant documents in

Bug#901100: [Debian-ha-maintainers] Bug#901100: cluster-glue-dev: missing Breaks+Replaces: cluster-glue (<< 1.0.12-8)

2018-06-09 Thread Valentin Vidic

On Sat, Jun 09, 2018 at 02:41:24PM +0200, Ferenc Wágner wrote:
> Are those .a (and .la) files really needed?  We mostly avoid shipping
> them, see:
> http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-dev
> https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#library
> https://wiki.debian.org/ReleaseGoals/LAFileRemoval

Yes, we should probably investigate if those static libs and
cluster-glue as a whole are used these days and remove what is
not needed anymore...

-- 
Valentin

Bug#901129: timidity: removes conffile belonging to timidity-daemon

2018-06-09 Thread Reiner Herrmann

On Sat, Jun 09, 2018 at 02:32:54PM +0200, Michael Biebl wrote:
> No, that's not what $PACKAGE in dpkg-maintscript-helper is used for.
> You can't "mark" a conffile as belonging to another package this way.

Maybe I misundertood something how it works internally.
But it has the effect that I desired, i.e. preserving changes after
the conffile is moved to the other package.

Without the last column:

$ dpkg -i timidity_2.13.2-41+b1_amd64.deb timidity-daemon_2.13.2-41_all.deb
...
$ echo "# some change" >> /etc/default/timidity
$ dpkg -i timidity_2.14.0-2+test1_amd64.deb 
timidity-daemon_2.14.0-2+test1_all.deb
...
$ grep change /etc/default/timidity
$

With the last column:

$ dpkg -i timidity_2.13.2-41+b1_amd64.deb timidity-daemon_2.13.2-41_all.deb
...
$ echo "# some change" >> /etc/default/timidity
$ dpkg -i timidity_2.14.0-2+test1_amd64.deb 
timidity-daemon_2.14.0-2+test1_all.deb
...
$ grep change /etc/default/timidity 
# some change
$


signature.asc
Description: PGP signature

Bug#900936: geoclue: Update to 2.4.10 breaks redshift

2018-06-09 Thread Zeeshan Ali

Hi,

Agent is required by default now but at the same time, we have enabled the 
demo-agent to be installed by default and to
auto-start on all non-GNOME desktops. It's been 5 years since geoclue2 was 
created, would be nice if other desktops
would implement an agent too. In the meantime, they can use the demo agent I 
wrote.

Bug#901100: cluster-glue-dev: missing Breaks+Replaces: cluster-glue (<< 1.0.12-8)

2018-06-09 Thread Ferenc Wágner

Andreas Beckmann  writes:

>   Unpacking cluster-glue-dev (1.0.12-9) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-iCxNhp/11-cluster-glue-dev_1.0.12-9_amd64.deb 
> (--unpack):
>trying to overwrite '/usr/lib/heartbeat/plugins/compress/bz2.a', which is 
> also in package cluster-glue 1.0.12-5

Hi Valentin,

Are those .a (and .la) files really needed?  We mostly avoid shipping
them, see:
http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-dev
https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#library
https://wiki.debian.org/ReleaseGoals/LAFileRemoval
-- 
Regards,
Feri

Bug#901129: timidity: removes conffile belonging to timidity-daemon

2018-06-09 Thread Michael Biebl

Am 09.06.2018 um 14:28 schrieb Reiner Herrmann:
> On Sat, Jun 09, 2018 at 02:16:14PM +0200, Michael Biebl wrote:
>> Why would the timidity package remove a conffile that belongs to another
>> package? That doesn't make sense to me.
> 
> Because the conffile removed from package A could be installed  / taken
> over by package B. As far as I understood it, it can be marked in this
> way to belong to package B. If it would just remove the file from A,
> the user's modifications would be lost.
> And testing upgrades with (un)modified files suggests that it works like
> this.


No, that's not what $PACKAGE in dpkg-maintscript-helper is used for.
You can't "mark" a conffile as belonging to another package this way.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#901129: timidity: removes conffile belonging to timidity-daemon

2018-06-09 Thread Reiner Herrmann

On Sat, Jun 09, 2018 at 02:16:14PM +0200, Michael Biebl wrote:
> Why would the timidity package remove a conffile that belongs to another
> package? That doesn't make sense to me.

Because the conffile removed from package A could be installed  / taken
over by package B. As far as I understood it, it can be marked in this
way to belong to package B. If it would just remove the file from A,
the user's modifications would be lost.
And testing upgrades with (un)modified files suggests that it works like
this.

Regards,
   Reiner

signature.asc
Description: PGP signature

Bug#901129: timidity: removes conffile belonging to timidity-daemon

2018-06-09 Thread Michael Biebl

Am 09.06.2018 um 13:36 schrieb Reiner Herrmann:
> Hi Sven and Michael,
> 
> thank you for the report and sorry for breaking it.
> 
>> specifically
>>
>> timidity.maintscript
>> rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon
>>
>> doesn't look correct either.
>> dpkg-maintscript-helper does not have support for moving conffiles from
>> one package to another (and why would you remove the conffile from
>> timidity-daemon, the package you moved the conffile into?)
> 
> I'm not removing it from timidity-daemon, but from timidity
> (timidity.maintscript). In the last column I'm marking timidity-daemon
> as the owner of the file.

Why would the timidity package remove a conffile that belongs to another
package? That doesn't make sense to me.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: '/usr/share/man/ja/man1/timidity.1.gz' is also in package timidity

2018-06-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + pending
Bug #901141 [timidity-el] '/usr/share/man/ja/man1/timidity.1.gz' is also in 
package timidity
Added tag(s) pending.

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

Bug#901141: '/usr/share/man/ja/man1/timidity.1.gz' is also in package timidity

2018-06-09 Thread Reiner Herrmann

Control: tags -1 + pending

Hi David,

thank you for the report.
The problem was that during arch:all-only builds, the manpages
were also installed (in the wrong package).
It is fixed in git:
 https://salsa.debian.org/debian/timidity/commit/3e5bff6

Kind regards,
   Reiner


signature.asc
Description: PGP signature

Bug#901129: timidity: removes conffile belonging to timidity-daemon

2018-06-09 Thread Reiner Herrmann

Hi Sven and Michael,

thank you for the report and sorry for breaking it.

> specifically
> 
> timidity.maintscript
> rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon
> 
> doesn't look correct either.
> dpkg-maintscript-helper does not have support for moving conffiles from
> one package to another (and why would you remove the conffile from
> timidity-daemon, the package you moved the conffile into?)

I'm not removing it from timidity-daemon, but from timidity
(timidity.maintscript). In the last column I'm marking timidity-daemon
as the owner of the file.
In my tests this also worked well, an unmodified file was just moved
to the timidity-daemon package, and a modified default file would also
stay intact (i.e., your changes are preserved after upgrade).
Without the last column the (modified) default file was removed during
upgrade and a fresh file was installed by timidity-daemon (your
modifications were lost).

I'm now just a bit puzzled why it didn't work in the same way for
the init.d file. Maybe because the other package (timidity-daemon) was
already the owner before (in the old version).

> Afaik, the best you can do is to have a versioned Breaks/Replaces
> against the package which previously shipped the conffile.

The conffiles also need to be cleaned up via a maintscript, because users
might not have the timidity-daemon package installed.

I think the init.d file should now be handled like this:
(Though this will lose changes made to the file before it was moved to the
other package (2.13.2-27, long before old-old-stable))

-rm_conffile/etc/init.d/timidity 2.14.0-2~timidity-daemon
+rm_conffile/etc/init.d/timidity 2.14.0-3~

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#901141: '/usr/share/man/ja/man1/timidity.1.gz' is also in package timidity

2018-06-09 Thread David Bremner

Package: timidity-el
Version: 2.14.0-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Preparing to unpack .../timidity-el_2.14.0-2_all.deb ...
ERROR: timidity-el is broken - called emacs-package-remove as a new-style 
add-on, but has no compat file.
Remove timidity-el for emacs
Unpacking timidity-el (2.14.0-2) over (2.13.2-41) ...
dpkg: error processing archive 
/var/cache/apt/archives/timidity-el_2.14.0-2_all.deb (--unpack):
 trying to overwrite '/usr/share/man/ja/man1/timidity.1.gz', which is also in 
package timidity 2.14.0-2
Errors were encountered while processing:
 /var/cache/apt/archives/timidity-el_2.14.0-2_all.deb


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

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

Versions of packages timidity-el depends on:
ii  emacsen-common  3.0.0
pn  timidity

timidity-el recommends no packages.

timidity-el suggests no packages.

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlsbtkkACgkQ8gKXHaSn
niyhzAv9FlaXmD/WjMPtu/HorpPzssOdcF4g1xp4mItfrf4dJaKtbqrjsD1szC89
AZVgQp0w9D+fhbwPEoilQ4MpYBbzxjp/BvWRWe4PEQMyzmXtqg0YLs3WC/mToIzo
mZBpOZfgKNzH7kBXXeoUskn+6u3ejglR92JuLNtOSc+nQrGqC/wqlU/M15r/OBII
kLIoY86MApR1nX5iOtwtXfG4MvhjCCHmcNdU7K3az5ObiByC8C+Z0rTWWsL2VnvF
iGZQ+FERhVVXCgwI/f1PdkDOfYp9ijNFpXro2TTTI/fwCyxZVTBZCe/rGKtYcnhX
0ozdquFYM/9GWrAgZiBRDubNBANBpd1SxgXKbIV2vJIJAIWGov17pwPThArgD/IZ
d97Rn57jS1OZ1Jj9VogXjM+2jcoZAPySSag3k/3zf/mBYCBbpRBpifG3wl3xf9Ih
F1M3PDoB922EK9IYIqg377Mtk/MC9lhuN1qify9viZvkC8rUZKbYkeUlx+tOaHop
uy0oHSv5
=tws/
-END PGP SIGNATURE-

Processed: severity of 900750 is important

2018-06-09 Thread Debian Bug Tracking System

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

> severity 900750 important
Bug #900750 [thunderbird] thunderbird: Launching Thunderbird completely locks 
my Xwindow session
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#901100: marked as done (cluster-glue-dev: missing Breaks+Replaces: cluster-glue (<< 1.0.12-8))

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 10:19:50 +
with message-id 
and subject line Bug#901100: fixed in cluster-glue 1.0.12-10
has caused the Debian Bug report #901100,
regarding cluster-glue-dev: missing Breaks+Replaces: cluster-glue (<< 1.0.12-8)
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.)


-- 
901100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cluster-glue-dev
Version: 1.0.12-9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package cluster-glue-dev.
  Preparing to unpack .../11-cluster-glue-dev_1.0.12-9_amd64.deb ...
  Unpacking cluster-glue-dev (1.0.12-9) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-iCxNhp/11-cluster-glue-dev_1.0.12-9_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/heartbeat/plugins/compress/bz2.a', which is 
also in package cluster-glue 1.0.12-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-iCxNhp/11-cluster-glue-dev_1.0.12-9_amd64.deb


According to the changelog, these files were moved in -8.


cheers,

Andreas


cluster-glue=1.0.12-5_cluster-glue-dev=1.0.12-9.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cluster-glue
Source-Version: 1.0.12-10

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

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated cluster-glue 
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, 09 Jun 2018 10:27:12 +0200
Source: cluster-glue
Binary: cluster-glue cluster-glue-dev liblrm2 libpils2 libplumb2 libplumbgpl2 
libstonith1 liblrm2-dev libpils2-dev libplumb2-dev libplumbgpl2-dev 
libstonith1-dev
Architecture: source
Version: 1.0.12-10
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Description:
 cluster-glue - Reusable cluster components for Linux HA
 cluster-glue-dev - Development files for the cluster glue components
 liblrm2- Reusable cluster libraries -- liblrm2
 liblrm2-dev - Reusable cluster development files -- liblrm
 libpils2   - Reusable cluster libraries -- libpils2
 libpils2-dev - Reusable cluster development files -- libpils2
 libplumb2  - Reusable cluster libraries -- libplumb2
 libplumb2-dev - Reusable cluster development files -- libplumb2
 libplumbgpl2 - Reusable cluster libraries -- libplumbgpl2
 libplumbgpl2-dev - Reusable cluster development files -- libplumbgpl2
 libstonith1 - Reusable cluster libraries -- libstonith1
 libstonith1-dev - Reusable cluster development files -- libstonith1
Closes: 901100
Changes:
 cluster-glue (1.0.12-10) unstable; urgency=medium
 .
   [ Edward Betts ]
   * Correct a spelling mistake.
 .
   [ Valentin Vidic ]
   * Add Breaks/Replaces after moving files (Closes: #901100)
Checksums-Sha1:
 8015e9824a298356274a909893ca7357684f454c 3288 cluster-glue_1.0.12-10.dsc
 82726ab8e121dafe288298011639d2415082ab52 23788 
cluster-glue_1.0.12-10.debian.tar.xz
 8c4ad6afe4f1ffdd912f2b086a174f6d3dfde253 9964 
cluster-glue_1.0.12-10_source.buildinfo
Checksums-Sha256:
 5e537516ecd838a0aabd20553bb6d22438f639b975f9f5b159c80a1a981a4eee 3288 
cluster-glue_1.0.12-10.dsc
 ab7db534a3800877f8580a825452374820d12c73ed9515272c26d9ce1ab57c37 23788 
cluster-glue_1.0.12-10.debian.tar.xz
 163e1032a579aa4d2c5388c3626b6caf7274f4e6c2f6412a51204093e0fe9a72 9964 
cluster-glue_1.0.12-10_source.buildinfo
Files:
 de2197d06e918faf452e503b37a8a949 3288 admin optional

Bug#901104: marked as done (chezscheme: FTBFS when built with dpkg-buildpackage -A)

2018-06-09 Thread Debian Bug Tracking System

Your message dated Sat, 09 Jun 2018 10:04:36 +
with message-id 
and subject line Bug#901104: fixed in chezscheme 9.5+dfsg-5
has caused the Debian Bug report #901104,
regarding chezscheme: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
901104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:chezscheme
Version: 9.5+dfsg-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/chezscheme-9.5+dfsg'
CC=x86_64-linux-gnu-gcc ./configure --workarea=build -m=ta6le --threads 
--installprefix=/usr --temproot=/<>/chezscheme-9.5+dfsg/debian/tmp
cp -a release_notes/ build/
cp -a csug/ build/
(echo "\def\INSERTREVISIONMONTHSPACEYEAR{}"; cat csug/copyright.stex) > \
build/csug/copyright.stex
make[1]: Leaving directory '/<>/chezscheme-9.5+dfsg'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/chezscheme-9.5+dfsg'
make -C build
make[2]: Entering directory '/<>/chezscheme-9.5+dfsg/build'
(cd c ; make)
ln -s ../../c/statics.c statics.c
ln -s ../../c/system.h system.h
ln -s ../../c/types.h types.h
ln -s ../../c/version.h version.h
ln -s ../../c/externs.h externs.h
ln -s ../../c/globals.h globals.h
ln -s ../../c/segment.h segment.h
ln -s ../../c/thread.h thread.h
ln -s ../../c/sort.h sort.h
x86_64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -m64 -msse2 
-Wpointer-arith -Wall -Wextra -Werror -Wno-implicit-fallthrough -O2 
-D_REENTRANT -pthread -g -O2 
-fdebug-prefix-map=/<>/chezscheme-9.5+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -DX86_64 -I../boot/ta6le statics.c
In file included from statics.c:18:0:
system.h:25:10: fatal error: zlib.h: No such file or directory
 #include "zlib.h"
  ^~~~
compilation terminated.
Makefile:29: recipe for target 'statics.o' failed
make[3]: *** [statics.o] Error 1
Makefile:20: recipe for target 'build' failed
make[2]: *** [build] Error 2
make[2]: Leaving directory '/<>/chezscheme-9.5+dfsg/build'
debian/rules:61: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/chezscheme-9.5+dfsg'
debian/rules:38: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".

The error does not happen with "dpkg-buildpackage".

Thanks.
--- End Message ---
--- Begin Message ---
Source: chezscheme
Source-Version: 9.5+dfsg-5

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

Debian distribution maintenance software
pp.
Göran Weinholt  (supplier of updated chezscheme 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, 09 Jun 2018 11:23:07 +0200
Source: chezscheme
Binary: chezscheme9.5 chezscheme9.5-dev chezscheme9.5-doc chezscheme
Architecture: source amd64 all
Version: 9.5+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Göran Weinholt 
Changed-By: Göran Weinholt 
Description:
 chezscheme - Reliable, high performance Scheme compiler
 chezscheme9.5 - Reliable, high performance Scheme compiler (version 9.5)
 chezscheme9.5-dev - Reliable, high performance Scheme compiler (C development 
files)
 chezscheme9.5-doc - Reliable, high performance Scheme compiler (documentation)
Closes: 901104
Changes:
 chezscheme (9.5+dfsg-5) unstable; urgency=medium
 .
   * Split -arch/-indep install and build targets to fix FTBFS.
 Thanks to Santiago Vila for the report (Closes: #901104)
Checksums-Sha1:

Bug#901001: python3-minimal should Pre-Depend on python3.N-minimal

2018-06-09 Thread Philipp Kern

On 6/9/18 7:20 AM, Steve Langasek wrote:
> - the package is being upgraded; it is in the common case (when no python
>   module names have been dropped from within the package) less important to
>   run py3clean because the same files will be recreated shortly afterwards
>   by py3compile from the new postinst.

What's the consequence from deleting the files and only recreating them
later? Longer startup time of the interpreter in that short window?
Because if it's worse, it'd be good to have py3clean only delete the
obsolete files in the postinst?

Kind regards
Philipp Kern

Bug#901136: can't remove if install fails

2018-06-09 Thread Peter Palfrader

Package: sreview-common
Version: 0.3.0-1~bpo.1
Severity: grave
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team


sreview-common failed to configure.

| Setting up sreview-common (0.3.0-1~bpo.1) ...
| usermod: user 'sreview' does not exist in /etc/passwd
| dpkg: error processing package sreview-common (--configure):
|  subprocess installed post-installation script returned error exit status 6
| dpkg: dependency problems prevent configuration of sreview-encoder:
|  sreview-encoder depends on sreview-common; however:
|   Package sreview-common is not configured yet.
| 
| dpkg: error processing package sreview-encoder (--configure):
...

Now we can't get rid of it anymore
| vittoria:~# apt-get purge sreview-detect sreview-master sreview-encoder 
sreview-web sreview-common
| 
| [..]
| After this operation, 165 kB disk space will be freed.
| Do you want to continue? [Y/n] 
| (Reading database ... 77344 files and directories currently installed.)
| Removing sreview-common (0.3.0-1~bpo.1) ...
| passwd: user 'sreview' does not exist in /etc/passwd
| dpkg: error processing package sreview-common (--remove):
|  subprocess installed pre-removal script returned error exit status 1
| usermod: user 'sreview' does not exist in /etc/passwd
| dpkg: error while cleaning up:
|  subprocess installed post-installation script returned error exit status 6
| Errors were encountered while processing:
|  sreview-common
| E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

2018-06-09 Thread Jose A. Fernandez Gonzalez

When I said ffmpeg I meant ffmpeg libraries, chromium depends on several
ffmpeg libraries (libavcodec, libavformat, libavutil, ...) and when I
comment that chromium-67 is looking for ffmpeg-4 is because in other
distros (archlinux, gentoo, ...) they are packaging chromium-67 pointing to
ffmpeg-4 (libavcodec, libavformat, libavutil, ... from ffmpeg-4).

$ LC_ALL=C apt depends chromium
chromium
  Depends: libasound2 (>= 1.0.16)
  Depends: libatk-bridge2.0-0 (>= 2.5.3)
  Depends: libatk1.0-0 (>= 1.12.4)
 |Depends: libavcodec57 (>= 7:3.4.2)  <<<-- (*)
  Depends: libavcodec-extra57 (>= 7:3.4.2) <<<-- (*)
  Depends: libavformat57 (>= 7:3.4.2) <<<-- (*)
  Depends: libavutil55 (>= 7:3.4.2)   <<<-- (*)
  Depends: libc6 (>= 2.27)
  Depends: libcairo2 (>= 1.6.0)
  Depends: libcups2 (>= 1.4.0)
  Depends: libdbus-1-3 (>= 1.9.14)
  Depends: libevent-2.1-6 (>= 2.1.8-stable)
  Depends: libexpat1 (>= 2.0.1)
  Depends: libflac8 (>= 1.3.0)
  Depends: libfontconfig1 (>= 2.12.6)
  Depends: libfreetype6 (>= 2.3.9)
  Depends: libgcc1 (>= 1:4.0)
  Depends: libgdk-pixbuf2.0-0 (>= 2.22.0)
  Depends: libglib2.0-0 (>= 2.31.8)
  Depends: libgtk-3-0 (>= 3.9.10)
  Depends: libharfbuzz0b (>= 1.6.0)
  Depends: libicu60 (>= 60.1-1~)
  Depends: libjpeg62-turbo (>= 1.5.0)
  Depends: liblcms2-2 (>= 2.2+git20110628)
  Depends: libminizip1 (>= 1.1)
  Depends: libnspr4 (>= 2:4.9-2~)
  Depends: libnss3 (>= 2:3.22)
  Depends: libopenjp2-7 (>= 2.2.0)
  Depends: libopus0 (>= 1.1)
  Depends: libpango-1.0-0 (>= 1.14.0)
  Depends: libpangocairo-1.0-0 (>= 1.14.0)
  Depends: libpng16-16 (>= 1.6.2-1)
  Depends: libpulse0 (>= 0.99.1)
  Depends: libre2-4 (>= 20160901)
  Depends: libsnappy1v5
  Depends: libstdc++6 (>= 6)
  Depends: libvpx5 (>= 1.6.0)
  Depends: libwebp6 (>= 0.5.1)
  Depends: libwebpdemux2 (>= 0.5.1)
  Depends: libwebpmux3 (>= 0.6.1-2)
  Depends: libx11-6 (>= 2:1.4.99.1)
  Depends: libx11-xcb1
  Depends: libxcb1 (>= 1.6)
  Depends: libxcomposite1 (>= 1:0.3-1)
  Depends: libxcursor1 (>> 1.1.2)
  Depends: libxdamage1 (>= 1:1.1)
  Depends: libxext6
  Depends: libxfixes3 (>= 1:5.0)
  Depends: libxi6 (>= 2:1.2.99.4)
  Depends: libxml2 (>= 2.7.4)
  Depends: libxrandr2 (>= 2:1.2.99.3)
  Depends: libxrender1
  Depends: libxslt1.1 (>= 1.1.25)
  Depends: libxss1
  Depends: libxtst6
  Depends: zlib1g (>= 1:1.2.2)
  Depends: chromium-common (= 67.0.3396.62-2)
  Conflicts: 
  Conflicts: 
  Conflicts: libsecret-1-0 (<< 0.18)
  Recommends: libgl1-mesa-dri
  Recommends: fonts-liberation
  Suggests: chromium-l10n
  Suggests: chromium-shell
  Suggests: chromium-driver

Regards.

Bug#901119: yodl: FTBFS when built with dpkg-buildpackage -A

2018-06-09 Thread Frank B. Brokken

Dear Santiago Vila, you wrote:

> Sorry, there was a typo in the bug report. I meant "buster" of course.

Ah, muy bien. Thanks for the clarification.

> The reason for this is that -A was never tried with the current
> version (4.02.00-2).
> 
> You can avoid this type of bugs to propagate to testing by uploading
> in source-only form (dpkg-buildpackage -S). That way we would get
> official build logs here for the arch:all autobuilder:
> 
> https://buildd.debian.org/status/package.php?p=yodl

Thx for the advice!

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#901119: yodl: FTBFS when built with dpkg-buildpackage -A

2018-06-09 Thread Santiago Vila

On Sat, Jun 09, 2018 at 08:30:02AM +0200, Frank B. Brokken wrote:
> Dear Santiago Vila, you wrote:
> > 
> > Package: src:yodl
> > Version: 4.02.00-2
> > Severity: serious
> > 
> > Dear maintainer:
> > 
> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > but it failed:
> 
> (etc)
> 
> Dear Santiago,
> 
> Thx for the bug report. I'll have a look at it asap. As a side note: As
> `stretch' is the current stable distribution I'm slightly curious as to what
> may be have caused this error. Maybe -A has never been used? Anyway, I'll
> check things out. Maybe it's only required to define the missing target in
> debian/rules :-)

Sorry, there was a typo in the bug report. I meant "buster" of course.

The reason for this is that -A was never tried with the current
version (4.02.00-2).

You can avoid this type of bugs to propagate to testing by uploading
in source-only form (dpkg-buildpackage -S). That way we would get
official build logs here for the arch:all autobuilder:

https://buildd.debian.org/status/package.php?p=yodl

Thanks.

Bug#900756: [Rd] Byte-compilation failure on different architectures / low-memory systems

2018-06-09 Thread Tomas Kalibera

It turned out slightly more complicated, the fallback to AST is was 
already in place, but memory available to malloc got exhausted via heap 
expansion. Messages starting "Error: compilation failed" mean there was 
an error while compiling, including out of memory, and that the AST will 
be used - so these are worth looking at but not fatal. The error message 
"cannot allocate buffer" was the real problem.


We have addressed that with Luke in R-devel and R-patched (more general 
fix might come later to R-devel only). Now there is a GC on the fallback 
path which should release some memory from R heap to be usable by malloc 
again. Also, the compiler needs a bit less memory when analyzing similar 
code patterns as those causing trouble in fBasics (solves the fBasics 
problems with "ulimit -v 100")


Best
Tomas

On 06/05/2018 08:59 PM, Dirk Eddelbuettel wrote:

On 4 June 2018 at 20:06, Tomas Kalibera wrote:
| thanks for the report. Access to the test system is not necessary, the
| memory requirements of the byte-code compiler are usually
| platform-independent and specifically with this package I can reproduce
| they are very high. We'll have a look what we can do, certainly there
| should at least be a way to recover and use the uncompiled version when
| memory allocation fails, this is already done by the JIT but not when
| compiling during installation. Before R or the package is patched, the
| only workaround for memory constrained systems is probably to disable
| byte-compilation of this package, as I read you are doing already.

Yes. And as a shortcut, we just turned it off unconditionally, ie on all
build architectures.  Worked fine as per

https://buildd.debian.org/status/package.php?p=fbasics

it has been built everywhere where we have R 3.5.0 (some 20 or so platforms).

The fix you suggest sounds ideal: if possible recover, and maybe WARN.

Dirk

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

2018-06-09 Thread Josef Kufner


Jose A. Fernandez Gonzalez wrote, on 8.6.2018 19:32:
[...] I think the problem is that chromium-67 is 
looking for ffmpeg-4 and the version available in Debian unstable is 
ffmpeg-3.4.2


There is no such dependency specified in the chromium package. That is 
certainly wrong.

Bug#901129: timidity: removes conffile belonging to timidity-daemon

2018-06-09 Thread Michael Biebl

The changes in
https://salsa.debian.org/debian/timidity/commit/3e768cabe537f2a8a22a51f4eb398a974fe15e25

specifically

timidity.maintscript
rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon

doesn't look correct either.
dpkg-maintscript-helper does not have support for moving conffiles from
one package to another (and why would you remove the conffile from
timidity-daemon, the package you moved the conffile into?)
Afaik, the best you can do is to have a versioned Breaks/Replaces
against the package which previously shipped the conffile.

Because moving conffiles is so badly supported, it should be avoided
whenever possible.
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

2018-06-09 Thread Lothar Braun

The problem persists with 67.0.3396.62-2.

Processed: Re: Bug#901114: python-coverage: FTBFS when built with dpkg-buildpackage -A

2018-06-09 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + confirmed
Bug #901114 [src:python-coverage] python-coverage: FTBFS when built with 
dpkg-buildpackage -A
Added tag(s) confirmed.

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

Bug#901114: python-coverage: FTBFS when built with dpkg-buildpackage -A

2018-06-09 Thread Ben Finney

Control: tags -1 + confirmed

On 09-Jun-2018, Santiago Vila wrote:

> I'm using "sbuild --arch-all --no-arch-any" on a clean chroot, which
> is what an official autobuilder would do to build the arch-indep
> packages.

Yes, thanks. That allows me to reproduce the behaviour.

> My feeling is that you are assuming some packages to be present when
> in fact they do not necessarily have to be present according to
> debian/control when building only the arch-independent packages.

Okay, I'll check into that.

-- 
 \   “Why, I'd horse-whip you if I had a horse.” —Groucho Marx |
  `\   |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#901119: yodl: FTBFS when built with dpkg-buildpackage -A

2018-06-09 Thread Frank B. Brokken

Dear Santiago Vila, you wrote:
> 
> Package: src:yodl
> Version: 4.02.00-2
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> but it failed:

(etc)

Dear Santiago,

Thx for the bug report. I'll have a look at it asap. As a side note: As
`stretch' is the current stable distribution I'm slightly curious as to what
may be have caused this error. Maybe -A has never been used? Anyway, I'll
check things out. Maybe it's only required to define the missing target in
debian/rules :-)

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#901129: timidity: removes conffile belonging to timidity-daemon

2018-06-09 Thread Sven Joachim

Package: timidity
Version: 2.14.0-2
Severity: serious

When upgrading timidity and timidity-daemon from 2.13.2-41 the following
happened (sorry for the German):

,
| Vorbereitung zum Entpacken von .../timidity_2.14.0-2_i386.deb ...
| Entpacken von timidity (2.14.0-2) über (2.13.2-41+b1) ...
| Vorbereitung zum Entpacken von .../timidity-daemon_2.14.0-2_all.deb ...
| Entpacken von timidity-daemon (2.14.0-2) über (2.13.2-41) ...
| Trigger für mime-support (3.60) werden verarbeitet ...
| Trigger für desktop-file-utils (0.23-3) werden verarbeitet ...
| Trigger für menu (2.1.47+b1) werden verarbeitet ...
| Trigger für systemd (238-5) werden verarbeitet ...
| Trigger für man-db (2.8.3-2) werden verarbeitet ...
| timidity (2.14.0-2) wird eingerichtet ...
| Neue Version der Konfigurationsdatei /etc/X11/app-defaults/TiMidity wird 
installiert ...
| Neue Version der Konfigurationsdatei 
/etc/X11/ja_JP.eucJP/app-defaults/TiMidity wird installiert ...
| Neue Version der Konfigurationsdatei /etc/timidity/timidity.cfg wird 
installiert ...
| Removing obsolete conffile /etc/init.d/timidity ...
| timidity-daemon (2.14.0-2) wird eingerichtet ...
| 
| Konfigurationsdatei »/etc/init.d/timidity«
|  ==> Gelöscht (von Ihnen oder von einem Skript) seit der Installation.
|  ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
|Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
| Y oder I : Die Version des Paket-Betreuers installieren
| N oder O : Die momentan installierte Version beibehalten
|D : Die Unterschiede zwischen den Versionen anzeigen
|Z : Eine Shell starten, um die Situation zu begutachten
|  Der Standardweg ist das Beibehalten der momentanen Version.
| Trigger für systemd (238-5) werden verarbeitet ...
`

And since I was not smart enough to type "Y" at the dpkg prompt I was
left with /etc/init.d/timidity.dpkg-dist which had to be renamed to
timidity again.  Hopefully this was enough to untangle the mess, but
getting asked about a conffile which I (TTBOMK) did not change looks
unacceptable to me in any case.


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

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

Versions of packages timidity depends on:
ii  libasound21.1.6-1
ii  libaudio2 1.9.4-6
ii  libc6 2.27-3
ii  libflac8  1.3.2-3
ii  libice6   2:1.0.9-2
ii  libjack0 [libjack-0.125]  1:0.125.0-3
ii  libncurses6   6.1+20180602-1
ii  libogg0   1.3.2-1+b1
ii  libpng16-16   1.6.34-1
ii  libsm62:1.2.2-1+b3
ii  libspeex1 1.2~rc1.2-1+b2
ii  libtinfo6 6.1+20180602-1
ii  libvorbis0a   1.3.6-1
ii  libvorbisenc2 1.3.6-1
ii  libx11-6  2:1.6.5-1
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  lsb-base  9.20170808
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages timidity recommends:
pn  fluid-soundfont-gm  
ii  timidity-daemon 2.14.0-2

Versions of packages timidity suggests:
pn  fluid-soundfont-gs  
ii  freepats20060219-1
pn  pmidi   

-- no debconf information

Bug#901128: primesieve: please bump library package name to libprimesieve9

2018-06-09 Thread Graham Inggs

Source: primesieve
Version: 7.0+ds-1
Severity: serious

Hi Maintainer

Upstream bumped the SONAME to libprimesieve.so.9, please bump the name
of the library package to libprimesieve9 in order to match.

You should have seen a package-name-doesnt-match-sonames [1] Lintian
warning while preparing the package.

Regards
Graham


[1] https://lintian.debian.org/tags/package-name-doesnt-match-sonames.html

73 matches

Mail list logo