Bug#897800: marked as done (libvigraimpex: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sat, 11 Aug 2018 05:04:00 +
with message-id 
and subject line Bug#897800: fixed in libvigraimpex 
1.10.0+git20160211.167be93+dfsg-6
has caused the Debian Bug report #897800,
regarding libvigraimpex: ftbfs with GCC-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.)


-- 
897800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/libvigraimpex_1.10.0+git20160211.167be93+dfsg-5_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:441:1:
   required from 'static void vigra::pyGaussianDivergenceImpl::def(const char*, const Args&, const char*) [with Args = 
boost::python::detail::keywords<7>; T = double; int N = 3]'
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:441:1:
   required from 'static void vigra::pyGaussianDivergenceImpl::def(const char*, const Args&, const char*) [with Args = 
boost::python::detail::keywords<7>; T = double; int FROM = 2; int TO = 3]'
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:441:1:
   required from 'void vigra::pyGaussianDivergence::def(const char*, const Args&, const char*) 
const [with Args = boost::python::detail::keywords<7>; int FROM = 2; int TO = 
3; T1 = float; T2 = double; T3 = void; T4 = void; T5 = void; T6 = void; T7 = 
void; T8 = void; T9 = void; T10 = void; T11 = void; T12 = void]'
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/numpy_array_converters.hxx:804:5:
   required from 'typename 
std::enable_if::value, void>::type boost::python::multidef(const char*, const 
Functor&, const Args&, const char*) [with Functor = 
vigra::pyGaussianDivergence<2, 3, float, double>; Args = 
boost::python::detail::keywords<7>; typename 
std::enable_if::value, void>::type = void]'
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:744:114:
   required from here
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:435:37:
 error: no matching function for call to 
'gaussianDivergenceMultiArray(vigra::NumpyArray<3, vigra::TinyVector, vigra::StridedArrayTag>&, vigra::NumpyArray<3, vigra::Singleband, 
vigra::StridedArrayTag>&, vigra::ConvolutionOptions<3>&)'
In file included from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:46:
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_convolution.hxx:2258:1:
 note: candidate: 'template 
void vigra::gaussianDivergenceMultiArray(Iterator, Iterator, 
vigra::MultiArrayView, vigra::ConvolutionOptions)'
 gaussianDivergenceMultiArray(Iterator vectorField, Iterator vectorFieldEnd,
 ^~~~
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_convolution.hxx:2258:1:
 note:   template argument deduction/substitution failed:
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:435:37:
 note:   deduced conflicting types for parameter 'Iterator' 
('vigra::NumpyArray<3, vigra::TinyVector, vigra::StridedArrayTag>' 
and 'vigra::NumpyArray<3, vigra::Singleband, vigra::StridedArrayTag>')
 gaussianDivergenceMultiArray(array, res, opt);
 ^
In file included from 

Bug#905735: emacs-goodies-el: postinst failure due to missing lcomp.el

[Nicholas D Steeves]

Hi Sebastian,

On Thu, Aug 09, 2018 at 06:09:29PM -0500, Sebastian P. Luque wrote:
> On Wed, 8 Aug 2018 22:50:16 -0400,
> Nicholas D Steeves  wrote:
> 
> [...]
> 
> > It is highly probable that this bug occurred due to breaking changes
> > introduced with emacsen-common 3.0.2, rather than from removal of this
> > file.
> 
> But I have emacsen-common 2.0.8 installed as per the report.

Exactly.  Upgrading between goodies-old_version (built with 2.0.8) and
goodies-new_version (built with 3.0.2) fails when emacsen-common_3.0.2
is not first installed.  This is why emacs-goodies-el_40.1 now depends
on emacsen-common_3.0.2.

> >> -- System Information: Debian Release: buster/sid APT prefers testing
> >> APT policy: (990, 'testing'), (300, 'unstable') Architecture: amd64
> >> (x86_64) Foreign Architectures: i386
> 
> > I see you're mixing testing and unstable.  Are you willing to test an
> > upgrade to unversioned emacs?  It would be a valuable data-point to
> > solving this emacs-goodies-el bug!  If so, please use the following
> > procedure:
> 
> > # This bit returns goodies to the state it was for Stretch
> > apt purge --autoremove emacs-goodies-el
> > wget 
> > https://snapshot.debian.org/archive/debian/20161122T032842Z/pool/main/e/emacs-goodies-el/emacs-goodies-el_36.3_all.deb
> > # this next line might be paranoia
> > apt autoremove --purge
> > # and finally install the package
> > dpkg -i emacs-goodies-el_36.3_all.deb
> 
> > # This installs emacs-goodies-el from stretch, and will pull in the
> > new unversioned emacs.  Please note the list of packages, in case you
> > need to roll back.
> > apt install emacs-goodies-el=40.1
> 
> The last step failed for me:

My apologies, I failed to account for pinning priorities.  If you
wouldn't mind, would you please retry that series again, but instead
of a last step of "apt install emacs-goodies-el=40.1" try "apt install
-t unstable emacs-goodies-el=40.1"?

> ------
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  emacs-goodies-el : Depends: emacsen-common (>= 3.0.2) but 2.0.8 is to be 
> installed
> Recommends: elpa-bm but it is not installable
> E: Unable to correct problems, you have held broken packages.
> ------
> 
> But succeeded by letting it choose my default testing version of the
> package (40.0):

That makes sense.  See explanation above.

> ------
> $ sudo aptitude safe-upgrade 
> The following packages will be upgraded: 
>   emacs-goodies-el 
> 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/96.4 kB of archives. After unpacking 3,177 kB will be freed.
> Do you want to continue? [Y/n/?] y
> Reading changelogs... Done   
> (Reading database ... 682251 files and directories currently installed.)
> Preparing to unpack .../emacs-goodies-el_40.0_all.deb ...
> Remove emacs-goodies-el for emacs25
> remove/emacs-goodies-el: purging byte-compiled files for emacs25
> Unpacking emacs-goodies-el (40.0) over (36.3) ...
> Processing triggers for install-info (6.5.0.dfsg.1-4) ...
> Setting up emacs-goodies-el (40.0) ...
> Install emacsen-common for emacs25
> emacsen-common: Handling install of emacsen flavor emacs25
> Install emacs-goodies-el for emacs25
> install/emacs-goodies-el: Handling emacs25, logged in /tmp/elc_b2o0sx.log
> Building autoloads for emacs25 in 
> /usr/share/emacs25/site-lisp/emacs-goodies-el
> install/emacs-goodies-el: Deleting /tmp/elc_b2o0sx.log
>  
> Current status: 0 (-1) upgradable.
> ------
> 
> Thank you for your quick follow-up and hopefully this is useful.

You're welcome!  Thank you, yes, this has been unexpectedly useful!
If my previous working hypothesis was correct, then upgrading from
goodies 36.3 to 40.0 without emacsen-common-3.0.2 should fail, but
this didn't occur!

Consequently, it would seem that only upgrades from goodies 39.0 to
40.0 without emacsen-common-3.0.2 are affected.  Unfortunately 39.0
isn't doesn't seem to be available anymore, so I'm not sure how to
test this unless someone has a cached version
  https://snapshot.debian.org/binary/emacs-goodies-el

Thank you for confirming emacs-goodies-el stable2testing succeeds.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#905877: regression in 1.4: upgrades random packages from testing to experimental (doesn't respect pinning?)

[Paul Wise]

Package: unattended-upgrades
Version: 1.4
Severity: serious

Recently I have had unattended-upgrades upgrade random packages from
testing to experimental. If I downgrade the packages upgraded, I won't
get the same packages upgraded the next day. I run apt-show-versions
daily and save the output to my mail store. Using my mail store I found
that the first instance of this happening was on 2018-07-06, there were
earlier instances but they were from me manually installing packages
from experimental and u-u doing subsequent upgrades. I noticed that I
upgraded unattended-upgrades on that date from 1.3 to 1.4. I'm not
sure, but the changelog indicates some package candidate changes,
perhaps this caused the issue? I think this bug should be fixed before Debian 
releases buster, this could break some setups.

$ notmuch search --output files --format text0 subject:apt-show-versions AND 
experimental | xargs -0 grep -Zl ^+.*/experimental | xargs -0 grep ^Date:
grep: /home/pabs/mail/cur/1533911695.H364727P6217.chianamo:2,: No such file or 
directory
/home/pabs/mail/.archives.chianamo/cur/1533738479.H931450P19950.chianamo:2,S:Date:
 Wed, 08 Aug 2018 22:27:59 +0800
/home/pabs/mail/.archives.chianamo/cur/1533452480.H469089P20113.chianamo:2,S:Date:
 Sun, 05 Aug 2018 15:01:20 +0800
/home/pabs/mail/.archives.chianamo/cur/1532469048.H39195P10262.chianamo:2,S:Date:
 Wed, 25 Jul 2018 05:50:47 +0800
/home/pabs/mail/.archives.chianamo/cur/1532009473.H904807P26370.chianamo:2,S:Date:
 Thu, 19 Jul 2018 22:11:13 +0800
/home/pabs/mail/.archives.chianamo/cur/1531406466.H36620P31910.chianamo:2,S:Date:
 Thu, 12 Jul 2018 22:41:05 +0800
/home/pabs/mail/.archives.chianamo/cur/1531318643.H907159P2397.chianamo:2,S:Date:
 Wed, 11 Jul 2018 22:17:23 +0800
/home/pabs/mail/.archives.chianamo/cur/1531231937.H239897P6579.chianamo:2,S:Date:
 Tue, 10 Jul 2018 22:12:17 +0800
/home/pabs/mail/.archives.chianamo/cur/1531145728.H178673P15461.chianamo:2,S:Date:
 Mon, 09 Jul 2018 22:15:28 +0800
/home/pabs/mail/.archives.chianamo/cur/1530973747.H830435P12225.chianamo:2,S:Date:
 Sat, 07 Jul 2018 22:29:07 +0800
/home/pabs/mail/.archives.chianamo/cur/1530887497.H217865P26358.chianamo:2,S:Date:
 Fri, 06 Jul 2018 22:31:36 +0800
/home/pabs/mail/.archives.chianamo/cur/1528812402.H467547P3507.chianamo:2,S:Date:
 Tue, 12 Jun 2018 22:06:42 +0800
/home/pabs/mail/.archives.chianamo/cur/1528121929.H964004P25155.chianamo:2,S:Date:
 Mon, 04 Jun 2018 22:18:49 +0800
/home/pabs/mail/.archives.chianamo/cur/1527948341.H185749P9358.chianamo:2,S:Date:
 Sat, 02 Jun 2018 22:05:41 +0800
/home/pabs/mail/.archives.chianamo/cur/1527863815.H640051P20918.chianamo:2,S:Date:
 Fri, 01 Jun 2018 22:36:55 +0800
...

$ which-pkg-broke unattended-upgrades | grep -C3 'Jul *6'
libpython3.6-stdlib:amd64  Sun Jul  1 13:07:11 2018
python3.6-minimal  Sun Jul  1 13:07:14 2018
libpython3.6-minimal:amd64 Sun Jul  1 13:07:19 2018
unattended-upgradesFri Jul  6 21:03:10 2018
install-info   Sat Jul  7 12:22:43 2018
libapt-pkg5.0:amd64Mon Jul 16 15:38:37 2018
libapt-inst2.0:amd64   Mon Jul 16 15:38:43 2018

$ zgrep -B2 -A1 unattended-upgrades /var/log/apt/history.log.1.gz 
Start-Date: 2018-07-06  21:03:00
Requested-By: pabs (1000)
Upgrade: unattended-upgrades:amd64 (1.3, 1.4)
End-Date: 2018-07-06  21:03:21

unattended-upgrades (1.4) unstable; urgency=medium
...
  * Adjust candidates only for packages to be possibly installed
(Closes: #892028, #899366) (LP: #1396787)

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages unattended-upgrades depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  gir1.2-glib-2.01.56.1-1
ii  lsb-base   9.20170808
ii  lsb-release9.20170808
ii  powermgmt-base 1.33
ii  python33.6.5-3
ii  python3-apt1.6.2
ii  python3-gi 3.28.2-1+b1
ii  ucf3.0038
ii  xz-utils   5.2.2-1.3

Versions of packages unattended-upgrades recommends:
ii  anacron 2.3-24
ii  cron [cron-daemon]  3.0pl1-130

Versions of packages unattended-upgrades suggests:
ii  bsd-mailx  8.1.2-0.20160123cvs-4
ii  exim4-daemon-light [mail-transport-agent]  4.91-6
ii  needrestart3.3-1

-- debconf information:
* 

Bug#905198: python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Pierre-Elliott Bécue]

Le 10 août 2018 23:27:02 GMT+02:00, Andreas Beckmann  a écrit :
>Hi Pierre,
>
>On 2018-08-10 18:01, Pierre-Elliott Bécue wrote:
>> I tried to fix that in a separate branch on salsa[1], see
>specifically
>> commit 988d4f6[2]. Unfortunately, although I followed all the steps
>I'm
>> aware of, `sudo piuparts -d stretch -d buster
>> python-ldap-dbg_3.1.0-3_amd64.deb python-ldap_3.1.0-3_amd64.deb`
>still
>> returns the same error.
>
>3.1.0-3 sounds wrong if sid has only 3.1.0-1
>
>In the .maintscript you want the version 3.1.0-3~ since you also want
>to
>fix this on upgrades from the buggy versions that didn't do
>symlink_to_dir. (or -2~ if you plan to upload it as -2)
>
>The piuparts options --testdebs-repo, --bindmount and
>--distupgrade-to-testdebs might be helpful to test upgrading from
>stretch directly to the new packages (and then use -a python-ldap-dbg,
>don't pass .deb files).
>If it isn't clear from the documentation, a plain directory with *.deb
>and the corresponding Packages file (from dpkg-scanpackages . >
>Packages) can be given to both --testdebs-repo and --bindmount, no need
>to fiddle with a 'deb [trusted=yes] file://' prefix and ' ./' suffix
>for
>--testdebs-repo.   
>
>
>
>Andreas

Dear Andreas,

Indeed, the repo has a 3.1.0-2 tag but no upload was done. I fixed all this.

I'm not a DD yet, only a DM. Can you review and upload the latest version 
that's in salsa ?

https://salsa.debian.org/python-team/modules/python-ldap

Thanks !
-- 
PEB

Bug#903743: Should opennebula be removed?

[Moritz Mühlenhoff]

reassign 903743 ftp.debian.org
retitle 903743 RM: RoQA: opennebula - unmaintained, RC-buggy, not in stable
severity 903743 normal
thanks

On Fri, Jul 13, 2018 at 11:23:35PM +0200, Moritz Muehlenhoff wrote:
> Source: opennebula
> Severity: grave
> 
> Should opennebula be removed?
> 
> - No maintainer upload since 2015
> - RC-buggy due to OpenSSL 1.1
> - Already missed stretch
> 
> Unless there are any objections/fixes, I'd reassign this to ftp.debian.org 
> for removal in a few weeks.

No objections for a month, reassigning.

Cheers,
Moritz

Processed: Re: Should opennebula be removed?

[Debian Bug Tracking System]

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

> reassign 903743 ftp.debian.org
Bug #903743 [src:opennebula] Should opennebula be removed?
Bug reassigned from package 'src:opennebula' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #903743 to the same values 
previously set
Ignoring request to alter fixed versions of bug #903743 to the same values 
previously set
> retitle 903743 RM: RoQA: opennebula - unmaintained, RC-buggy, not in stable
Bug #903743 [ftp.debian.org] Should opennebula be removed?
Changed Bug title to 'RM: RoQA: opennebula - unmaintained, RC-buggy, not in 
stable' from 'Should opennebula be removed?'.
> severity 903743 normal
Bug #903743 [ftp.debian.org] RM: RoQA: opennebula - unmaintained, RC-buggy, not 
in stable
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#905198: python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Hi Pierre,

On 2018-08-10 18:01, Pierre-Elliott Bécue wrote:
> I tried to fix that in a separate branch on salsa[1], see specifically
> commit 988d4f6[2]. Unfortunately, although I followed all the steps I'm
> aware of, `sudo piuparts -d stretch -d buster
> python-ldap-dbg_3.1.0-3_amd64.deb python-ldap_3.1.0-3_amd64.deb` still
> returns the same error.

3.1.0-3 sounds wrong if sid has only 3.1.0-1

In the .maintscript you want the version 3.1.0-3~ since you also want to
fix this on upgrades from the buggy versions that didn't do
symlink_to_dir. (or -2~ if you plan to upload it as -2)

The piuparts options --testdebs-repo, --bindmount and
--distupgrade-to-testdebs might be helpful to test upgrading from
stretch directly to the new packages (and then use -a python-ldap-dbg,
don't pass .deb files).
If it isn't clear from the documentation, a plain directory with *.deb
and the corresponding Packages file (from dpkg-scanpackages . >
Packages) can be given to both --testdebs-repo and --bindmount, no need
to fiddle with a 'deb [trusted=yes] file://' prefix and ' ./' suffix for
--testdebs-repo.



Andreas

Processed: retitle 904570 to node-promise-retry: FTBFS missing build-dep node-sleep-promise

[Debian Bug Tracking System]

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

> retitle 904570 node-promise-retry: FTBFS missing build-dep node-sleep-promise
Bug #904570 [src:node-promise-retry] node-promise-retry: FTBFS missing 
build-dep node-promise-retry
Changed Bug title to 'node-promise-retry: FTBFS missing build-dep 
node-sleep-promise' from 'node-promise-retry: FTBFS missing build-dep 
node-promise-retry'.
> thanks
Stopping processing here.

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

Bug#859675: radsecproxy: Please migrate to openssl1.1 in Buster

[Moritz Mühlenhoff]

On Wed, Apr 05, 2017 at 09:56:21PM +0200, Sebastian Andrzej Siewior wrote:
> Package: radsecproxy
> Version: 1.6.7-1
> Severity: important
> Tags: sid buster fixed-upstream
> User: pkg-openssl-de...@lists.alioth.debian.org
> Usertags: openssl-1.1-trans
> control: forwarded -1 https://project.nordu.net/browse/RADSECPROXY-66
> 
> Please migrate to libssl-dev in the Buster cycle. The bug report about
> the FTBFS is #828527. The log of the FTBFS can be found at
>   
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/radsecproxy_1.6.7-1_amd64-20160529-1530

I've been going through the remaining OpenSSL 1.1 bugs and radsecproxy
appears to have been fixed in the latest 1.7.1 upstream release.

Cheers,
Moritz

Bug#904444: closed by Andreas Tille (Bug#904444: fixed in trnascan-se 2.0.0-2)

[Adrian Bunk]

On Sun, Aug 05, 2018 at 12:51:04AM +, Debian Bug Tracking System wrote:
>...
> Source: trnascan-se
> Binary: trnascan-se trnascan-se-common
> Architecture: source
>...

This package is in non-free, source-only uploads would only work after
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#non-free-buildd

Short-term, the best way forward would be a binary-only amd64 upload of 2.0.0-2.

cu
Adrian

-- 

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

Processed: tagging 903388

[Debian Bug Tracking System]

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

> tags 903388 + fixed-upstream
Bug #903388 [python3-libcloud] Failure to install with Python 3.7
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#905198: python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #905198 [python-ldap-dbg] python-ldap-dbg: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.

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

Bug#905198: python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Pierre-Elliott Bécue]

Control: tags -1 + pending

Le vendredi 10 août 2018 à 18:22:12+0200, Pierre-Elliott Bécue a écrit :
> Le vendredi 10 août 2018 à 18:01:11+0200, Pierre-Elliott Bécue a écrit :
> > Le mercredi 01 août 2018 à 14:23:42+0200, Andreas Beckmann a écrit :
> > > [python-ldap-dbg is a bad boy]
> > [not working properly]
> [Not so relevant stuff about multiarch]

Ok, found, thanks to mentors.

The package is ready. It'll be uploaded soon.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Processed: tagging 897867

[Debian Bug Tracking System]

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

> tags 897867 + ftbfs
Bug #897867 [src:spades] spades: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#904382: python3-doublex: fails to install with Python 3.7

[Pierre-Elliott Bécue]

Le mardi 24 juillet 2018 à 11:01:42+0200, David Villa a écrit :
> Hi Andreas:
> 
> I just fixed this issue with this module and it's available in the upstream
> repository [1]. Unfortunately when the Debian Python Modules Team changed the
> package building system to git-buildpackage, I stopped maintaining my packages
> for Debian. I have not had time to understand and apply the new system. I 
> would
> appreciate some help in making the conversion to the new package building
> system. 
> 
> Thank you

Hi David,

I'll be happy to help you.

What exactly would you like me to do? Explain the steps to go to
git-buildpackage? Do the work, commit & let you review? Someting else?

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#905859: async-http-client build depends on libnetty-3.9-java

[Adrian Bunk]

Source: async-http-client
Version: 1.6.5-5
Severity: serious
Control: block 888255 by -1

async-http-client build depends on libnetty-3.9-java,
which is scheduled for removal (see #888255).

Bug#905858: osmosis build depends on libnetty-3.9-java

[Adrian Bunk]

Source: osmosis
Version: 0.46-5
Severity: serious
Control: block 888255 by -1

osmosis build depends on libnetty-3.9-java,
which is scheduled for removal (see #888255).

Processed: osmosis build depends on libnetty-3.9-java

[Debian Bug Tracking System]

Processing control commands:

> block 888255 by -1
Bug #888255 [src:netty-3.9] RM? Upstream dropped support, security important, 
newer version packaged
888255 was blocked by: 890624
888255 was not blocking any bugs.
Added blocking bug(s) of 888255: 905858

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

Processed: libgpars-groovy-java build depends on libnetty-3.9-java

[Debian Bug Tracking System]

Processing control commands:

> block 888255 by -1
Bug #888255 [src:netty-3.9] RM? Upstream dropped support, security important, 
newer version packaged
888255 was blocked by: 890624 905859 905858
888255 was not blocking any bugs.
Added blocking bug(s) of 888255: 905860

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

Bug#905860: libgpars-groovy-java build depends on libnetty-3.9-java

[Adrian Bunk]

Source: libgpars-groovy-java
Version: 1.2.1-9
Severity: serious
Control: block 888255 by -1

libgpars-groovy-java build depends on libnetty-3.9-java,
which is scheduled for removal (see #888255).

Processed: async-http-client build depends on libnetty-3.9-java

[Debian Bug Tracking System]

Processing control commands:

> block 888255 by -1
Bug #888255 [src:netty-3.9] RM? Upstream dropped support, security important, 
newer version packaged
888255 was blocked by: 905858 890624
888255 was not blocking any bugs.
Added blocking bug(s) of 888255: 905859

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

Bug#904368: panoramisk: diff for NMU version 1.0-1.1

[Adrian Bunk]

Control: tags 904368 + patch
Control: tags 904368 + pending

Dear maintainer,

I've prepared an NMU for panoramisk (versioned as 1.0-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru panoramisk-1.0/debian/changelog panoramisk-1.0/debian/changelog
--- panoramisk-1.0/debian/changelog	2016-10-04 20:05:37.0 +0300
+++ panoramisk-1.0/debian/changelog	2018-08-10 23:47:57.0 +0300
@@ -1,3 +1,11 @@
+panoramisk (1.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add upstream fix for compatibility with Python 3.7.
+(Closes: #904368)
+
+ -- Adrian Bunk   Fri, 10 Aug 2018 23:47:57 +0300
+
 panoramisk (1.0-1) unstable; urgency=medium
 
   * Initial release. (Closes: #829504)
diff -Nru panoramisk-1.0/debian/patches/0001-python3.7-support-68.patch panoramisk-1.0/debian/patches/0001-python3.7-support-68.patch
--- panoramisk-1.0/debian/patches/0001-python3.7-support-68.patch	1970-01-01 02:00:00.0 +0200
+++ panoramisk-1.0/debian/patches/0001-python3.7-support-68.patch	2018-08-10 23:47:50.0 +0300
@@ -0,0 +1,31 @@
+From 2deada71295fe6c04564a52edf075c164c55942a Mon Sep 17 00:00:00 2001
+From: Quentin Dawans 
+Date: Fri, 20 Jul 2018 15:20:06 +0200
+Subject: python3.7 support (#68)
+
+Index: panoramisk-1.0/panoramisk/actions.py
+===
+--- panoramisk-1.0.orig/panoramisk/actions.py
 panoramisk-1.0/panoramisk/actions.py
+@@ -61,7 +61,7 @@ class Action(utils.CaseInsensitiveDict):
+ return True
+ elif msg.startswith('added') and msg.endswith('to queue'):
+ return True
+-elif msg.endswith('successfully queued') and self.async != 'false':
++elif msg.endswith('successfully queued') and self['async'] != 'false':
+ return True
+ elif self.as_list:
+ return True
+Index: panoramisk-1.0/panoramisk/manager.py
+===
+--- panoramisk-1.0.orig/panoramisk/manager.py
 panoramisk-1.0/panoramisk/manager.py
+@@ -209,7 +209,7 @@ class Manager(object):
+ ret = callback(self, event)
+ if (asyncio.iscoroutine(ret) or
+ isinstance(ret, asyncio.Future)):
+-asyncio.async(ret, loop=self.loop)
++asyncio.ensure_future(ret, loop=self.loop)
+ return matches
+ 
+ def close(self):
diff -Nru panoramisk-1.0/debian/patches/series panoramisk-1.0/debian/patches/series
--- panoramisk-1.0/debian/patches/series	2016-09-18 16:21:01.0 +0300
+++ panoramisk-1.0/debian/patches/series	2018-08-10 23:46:24.0 +0300
@@ -1 +1,2 @@
 0001-hardcode-version-in-docs-since-package-not-yet-insta.patch
+0001-python3.7-support-68.patch

Processed: panoramisk: diff for NMU version 1.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 904368 + patch
Bug #904368 [python3-panoramisk] python3-panoramisk: fails to install with 
Python 3.7
Added tag(s) patch.
> tags 904368 + pending
Bug #904368 [python3-panoramisk] python3-panoramisk: fails to install with 
Python 3.7
Added tag(s) pending.

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

Processed: tagging 902945

[Debian Bug Tracking System]

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

> tags 902945 + fixed-upstream
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Bug #902760 [src:igraph] python-igraph FTBFS with ARPACK 3.6
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 902945

[Debian Bug Tracking System]

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

> tags 902945 - help
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Bug #902760 [src:igraph] python-igraph FTBFS with ARPACK 3.6
Removed tag(s) help.
Removed tag(s) help.
> thanks
Stopping processing here.

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

Processed: bug 904361 is forwarded to https://github.com/aio-libs/aiopg/issues/436

[Debian Bug Tracking System]

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

> forwarded 904361 https://github.com/aio-libs/aiopg/issues/436
Bug #904361 [python3-aiopg] python3-aiopg: fails to install with Python 3.7
Set Bug forwarded-to-address to 'https://github.com/aio-libs/aiopg/issues/436'.
> thanks
Stopping processing here.

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

Processed: bug 904358 is forwarded to https://github.com/aio-libs/aiozmq/issues/132

[Debian Bug Tracking System]

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

> forwarded 904358 https://github.com/aio-libs/aiozmq/issues/132
Bug #904358 [python3-aiozmq] python3-aiozmq: fails to install with python 3.7
Set Bug forwarded-to-address to 'https://github.com/aio-libs/aiozmq/issues/132'.
> thanks
Stopping processing here.

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

Bug#903527: python-motor: diff for NMU version 1.2.3-1.1

[Adrian Bunk]

Control: tags 903527 + patch
Control: tags 903527 + pending

Dear maintainer,

I've prepared an NMU for python-motor (versioned as 1.2.3-1.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

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

diff -Nru python-motor-1.2.3/debian/changelog python-motor-1.2.3/debian/changelog
--- python-motor-1.2.3/debian/changelog	2018-05-29 14:30:50.0 +0300
+++ python-motor-1.2.3/debian/changelog	2018-08-10 23:31:48.0 +0300
@@ -1,3 +1,11 @@
+python-motor (1.2.3-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add upstream fix for compatibility with Python 3.7.
+(Closes: #903527)
+
+ -- Adrian Bunk   Fri, 10 Aug 2018 23:31:48 +0300
+
 python-motor (1.2.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru python-motor-1.2.3/debian/patches/0001-MOTOR-248-Don-t-use-async-as-variable-name.patch python-motor-1.2.3/debian/patches/0001-MOTOR-248-Don-t-use-async-as-variable-name.patch
--- python-motor-1.2.3/debian/patches/0001-MOTOR-248-Don-t-use-async-as-variable-name.patch	1970-01-01 02:00:00.0 +0200
+++ python-motor-1.2.3/debian/patches/0001-MOTOR-248-Don-t-use-async-as-variable-name.patch	2018-08-10 23:25:42.0 +0300
@@ -0,0 +1,49 @@
+From aced74e749bd22efdeef891e1f345ec1923403ae Mon Sep 17 00:00:00 2001
+From: "A. Jesse Jiryu Davis" 
+Date: Wed, 27 Jun 2018 22:47:48 -0400
+Subject: MOTOR-248 Don't use "async" as variable name
+
+In Python 3.7, "async" becomes a full-fledged keyword.
+---
+ motor/frameworks/asyncio/__init__.py | 5 -
+ test/asyncio_tests/__init__.py   | 6 +-
+ 2 files changed, 1 insertion(+), 10 deletions(-)
+
+diff --git a/motor/frameworks/asyncio/__init__.py b/motor/frameworks/asyncio/__init__.py
+index 098f24c..21bb3f0 100644
+--- a/motor/frameworks/asyncio/__init__.py
 b/motor/frameworks/asyncio/__init__.py
+@@ -26,11 +26,6 @@ import functools
+ import multiprocessing
+ from concurrent.futures import ThreadPoolExecutor
+ 
+-try:
+-from asyncio import ensure_future
+-except ImportError:
+-from asyncio import async as ensure_future
+-
+ CLASS_PREFIX = 'AsyncIO'
+ 
+ 
+diff --git a/test/asyncio_tests/__init__.py b/test/asyncio_tests/__init__.py
+index b5ed7b9..05d8642 100644
+--- a/test/asyncio_tests/__init__.py
 b/test/asyncio_tests/__init__.py
+@@ -20,13 +20,9 @@ import gc
+ import inspect
+ import os
+ import unittest
++from asyncio import ensure_future
+ from unittest import SkipTest
+ 
+-try:
+-from asyncio import ensure_future
+-except ImportError:
+-from asyncio import async as ensure_future
+-
+ from mockupdb import MockupDB
+ 
+ from motor import motor_asyncio
+-- 
+2.11.0
+
diff -Nru python-motor-1.2.3/debian/patches/series python-motor-1.2.3/debian/patches/series
--- python-motor-1.2.3/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ python-motor-1.2.3/debian/patches/series	2018-08-10 23:31:48.0 +0300
@@ -0,0 +1,2 @@
+0001-MOTOR-248-Don-t-use-async-as-variable-name.patch
+

Bug#897793: marked as done (libqtpas: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 20:35:30 +
with message-id 
and subject line Bug#897793: fixed in libqtpas 2.6~beta-5
has caused the Debian Bug report #897793,
regarding libqtpas: ftbfs with GCC-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.)


-- 
897793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libqtpas
Version: 2.6~beta-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/libqtpas_2.6~beta-4_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
Multiarch host: x86_64-linux-gnu
Install target: /<>/debian/tmp
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install --list-missing
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 12.
make[1]: Leaving directory '/<>'
   dh_installdocs -a -O--parallel
   dh_installchangelogs -a -O--parallel
   dh_perl -a -O--parallel
   dh_link -a -O--parallel
   dh_strip_nondeterminism -a -O--parallel
   dh_compress -a -O--parallel
   dh_fixperms -a -O--parallel
   dh_missing -a -O--parallel
   dh_strip -a -O--parallel
   dh_makeshlibs -a -O--parallel
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libqt5pas1/DEBIAN/symbols doesn't match 
completely debian/libqt5pas1.symbols
--- debian/libqt5pas1.symbols (libqt5pas1_2.6~beta-4_amd64)
+++ dpkg-gensymbolswQu4LP   2018-05-02 13:01:35.483355219 +
@@ -8396,6 +8396,7 @@
  QtVersion@Base 2.6~alpha
  _Z22QWindow_isActiveWindowP9QWindow__@Base 2.6~beta-2
  _Z22QWindow_setWindowTitleP9QWindow__Pv@Base 2.6~beta-2
+ 
_Z27qRegisterNormalizedMetaTypeIP7QActionEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBuiltInEE11DefinedTypeE@Base
 2.6~beta-4
  
(optional=templinst)_Z30copyPtrIntArrayToQListTemplateIP13QGraphicsItemEvPvR5QListIT_E@Base
 2.6~alpha
  
(optional=templinst)_Z30copyPtrIntArrayToQListTemplateIP13QStandardItemEvPvR5QListIT_E@Base
 2.6~alpha
  
(optional=templinst)_Z30copyPtrIntArrayToQListTemplateIP15QTreeWidgetItemEvPvR5QListIT_E@Base
 2.6~alpha
@@ -8820,10 +8821,10 @@
  (optional=templinst)_ZN5QListIiED1Ev@Base 2.6~alpha
  (optional=templinst)_ZN5QListIiED2Ev@Base 2.6~alpha
  
_ZN7QVectorI6QPointE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base
 2.6~alpha
- _ZN7QVectorI6QPointEC1Ei@Base 2.6~alpha
- _ZN7QVectorI6QPointEC2Ei@Base 2.6~alpha
- _ZN7QVectorI7QPointFEC1Ei@Base 2.6~alpha
- _ZN7QVectorI7QPointFEC2Ei@Base 2.6~alpha
+#MISSING: 2.6~beta-4# _ZN7QVectorI6QPointEC1Ei@Base 2.6~alpha
+#MISSING: 2.6~beta-4# _ZN7QVectorI6QPointEC2Ei@Base 2.6~alpha
+#MISSING: 2.6~beta-4# _ZN7QVectorI7QPointFEC1Ei@Base 2.6~alpha
+#MISSING: 2.6~beta-4# _ZN7QVectorI7QPointFEC2Ei@Base 2.6~alpha
  _ZN7QVectorIdE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base 
2.6~alpha
  _ZNK10QDrag_hook10metaObjectEv@Base 2.6~alpha
  _ZNK10QMenu_hook10metaObjectEv@Base 2.6~alpha
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:17: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2
--- End Message ---
--- Begin Message ---
Source: libqtpas
Source-Version: 2.6~beta-5

We believe that the bug you reported is fixed in the latest version of

Processed: python-motor: diff for NMU version 1.2.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 903527 + patch
Bug #903527 [python3-motor] python3-motor fails to install with Python 3.7 as 
suported version
Added tag(s) patch.
> tags 903527 + pending
Bug #903527 [python3-motor] python3-motor fails to install with Python 3.7 as 
suported version
Added tag(s) pending.

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

Bug#904652: pulseaudio: looses device and replace it with dummy package so no sound possible

[Felipe Sateler]

(Please keep the bug in CC)
On Fri, Aug 10, 2018 at 4:06 PM Meinolf Gödde  wrote:

> Hi,
>
> Here is the output.
>
> Hope you can find a hint.
>
> Greetings
>

Unfortunately it is not useful unless it is a log of the problem occurring.

Saludos


>
> Meinolf
>
> Am 07.08.2018 17:39 schrieb Felipe Sateler:
> > On Sat, Jul 28, 2018 at 8:24 AM Charlemagne Lasse <
> > charlemagnela...@gmail.com> wrote:
> >
> >> found 904652 11.1-5
> >> thanks
> >>
> >> > i didn't do anything.
> >> > Upgrading the system like always.
> >> > Suddenly there was no sound available.
> >>
> >> Change /etc/pulse/default.pa to automatically load module-alsa-sink on
> >> boot (module-udev-detect is broken and will not load the alsa-sink
> >> anymore)
> >>
> >> This is also a problem in buster (which is still using 11.1-5)
> >>
> >
> > Seems like pulseaudio is not starting. Please attach the output of
> > `pulseaudio - --daemonize=no`, without applying your workaround.



-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#902788: python3-minimal needs Breaks for software/modules broken by 3.7

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #902788 {Done: Matthias Klose } [python3.7] python3.7: 
needs Breaks for software/modules broken by 3.7 ("async" became a reserved 
keyword)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python3.7/3.7.0-3.

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

Bug#902788: python3-minimal needs Breaks for software/modules broken by 3.7

[Adrian Bunk]

Control: reopen -1

On Tue, Jul 03, 2018 at 05:21:29AM +0200, Matthias Klose wrote:
> Control: reassign -1 python3.7
> 
> On 30.06.2018 22:58, Adrian Bunk wrote:
> > Package: python3-minimal
> > Version: 3.6.6-1
> > Severity: serious
> > Control: block -1 by 902757 902631 902766 902646 902715 902650
> > Control: block 902582 by -1
> > 
> > Plenty of packages fail to work or even install with Python 3.7
> > for reasons like 'async' now being a keyword.
> > 
> > python3-minimal needs Breaks for against all versions of other
> > packages in stretch or buster that don't work with 3.7.
> 
> if at all, python3.7 needs these breaks, not the dependency packages.

It is actually python3.7-minimal that needs them, and they should be 
moved there:

# apt-get install python3-motor
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  python3.7-minimal
Use 'apt autoremove' to remove it.
Suggested packages:
  python3-aiohttp
The following packages will be REMOVED:
  python3-all python3-all-dev python3-coverage python3-hypothesis
  python3-numpy python3.7 python3.7-dev
The following NEW packages will be installed:
  python3-motor
0 upgraded, 1 newly installed, 7 to remove and 0 not upgraded.
Need to get 0 B/45.6 kB of archives.
After this operation, 17.6 MB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 797869 files and directories currently installed.)
Removing python3-all-dev (3.6.6-1) ...
Removing python3-all (3.6.6-1) ...
Removing python3-hypothesis (3.44.1-2) ...
Removing python3-coverage (4.5.1+dfsg.1-1) ...
Removing python3-numpy (1:1.14.5-1+b1) ...
Removing python3.7-dev (3.7.0-4) ...
Removing python3.7 (3.7.0-4) ...
Selecting previously unselected package python3-motor.
(Reading database ... 797288 files and directories currently installed.)
Preparing to unpack .../python3-motor_1.2.3-1_all.deb ...
Unpacking python3-motor (1.2.3-1) ...
Processing triggers for mime-support (3.61) ...
Processing triggers for desktop-file-utils (0.23-3) ...
Setting up python3-motor (1.2.3-1) ...
  File "/usr/lib/python3/dist-packages/motor/frameworks/asyncio/__init__.py", 
line 32
from asyncio import async as ensure_future
^
SyntaxError: invalid syntax

dpkg: error processing package python3-motor (--configure):
 installed python3-motor package post-installation script subprocess returned 
error exit status 1
Processing triggers for man-db (2.8.4-2) ...
Errors were encountered while processing:
 python3-motor
E: Sub-process /usr/bin/dpkg returned an error code (1)
# 

cu
Adrian

-- 

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

Processed: tagging 897768

[Debian Bug Tracking System]

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

> tags 897768 + ftbfs
Bug #897768 [src:hmat-oss] hmat-oss: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: fixed 903174 in 0.0~git20170830.ce3d4cfc-3

[Debian Bug Tracking System]

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

> fixed 903174 0.0~git20170830.ce3d4cfc-3
Bug #903174 {Done: Nobuhiro Iwamatsu } 
[src:golang-github-google-subcommands] golang-github-google-subcommands: FTBFS 
in buster/sid (dh_installdocs: Cannot find "README.rst")
Marked as fixed in versions 
golang-github-google-subcommands/0.0~git20170830.ce3d4cfc-3.
> thanks
Stopping processing here.

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

Bug#905292: marked as done (cysignals-tools: missing Depends: python3-distutils)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 19:18:49 +
with message-id 
and subject line Bug#905292: fixed in cysignals 1.6.7+ds-3
has caused the Debian Bug report #905292,
regarding cysignals-tools: missing Depends: python3-distutils
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.)


-- 
905292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cysignals-tools
Version: 1.6.7+ds-2
Severity: serious

$ /usr/bin/cysignals-CSI
Traceback (most recent call last):
  File "/usr/bin/cysignals-CSI", line 44, in 
from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils.spawn'


Andreas
--- End Message ---
--- Begin Message ---
Source: cysignals
Source-Version: 1.6.7+ds-3

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated cysignals 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, 10 Aug 2018 18:54:19 +
Source: cysignals
Binary: python-cysignals-pari python3-cysignals-pari python-cysignals-bare 
python3-cysignals-bare cysignals-tools python-cysignals-doc
Architecture: source
Version: 1.6.7+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Jerome Benoit 
Changed-By: Jerome Benoit 
Description:
 cysignals-tools - interrupt and signal handling for Cython -- tools
 python-cysignals-bare - interrupt and signal handling for Cython -- Python - 
bare
 python-cysignals-doc - interrupt and signal handling for Cython -- doc
 python-cysignals-pari - interrupt and signal handling for Cython -- Python - 
PARI/GP
 python3-cysignals-bare - interrupt and signal handling for Cython -- Python 3 
- bare
 python3-cysignals-pari - interrupt and signal handling for Cython -- Python 3 
- PARI/GP
Closes: 905292
Changes:
 cysignals (1.6.7+ds-3) unstable; urgency=medium
 .
   * RC bug fix release (Closes: #905292):
 - debian/control:
   - Build-Depends field, add python3-distutils;
   - cysignals-tools Package, Depends field, add python3-distutils.
   * Debianization:
 - debian/control:
   - Standards-Version, bump to 4.2.0 (no change);
 - debian/patches/*:
   d/p/upstream-autotoolization_pytoolization-harden-build_directory.patch ,
 clean up.
Checksums-Sha1:
 fc4b6e67f0cc429a52643afc604f4f6b311a5188 3590 cysignals_1.6.7+ds-3.dsc
 405e4952dc85bae0ee330cd32923ede2fba16b2d 13228 
cysignals_1.6.7+ds-3.debian.tar.xz
 dc4392665ffa531376a075435788ca3934ab18fe 8799 
cysignals_1.6.7+ds-3_source.buildinfo
Checksums-Sha256:
 1ec385efb56de1c09e8847217929e6eb3bfdd7f00ed4c51d1c0f68f32df06046 3590 
cysignals_1.6.7+ds-3.dsc
 0f5b23169731bf7f6761673eeb66950aeff1018e52b7e5a643a537fda3b63f9e 13228 
cysignals_1.6.7+ds-3.debian.tar.xz
 d63bd2838f09d0bec85d2be37378beaada5332d5bb56577370f510abfe87c1d0 8799 
cysignals_1.6.7+ds-3_source.buildinfo
Files:
 6ec1036ca6407c4c351d493a961c7ea8 3590 python optional cysignals_1.6.7+ds-3.dsc
 c998aa34786f995e5df08b06a80f16c6 13228 python optional 
cysignals_1.6.7+ds-3.debian.tar.xz
 d7ef4122e34d6bdc0c851f9a2fb3bd2e 8799 python optional 
cysignals_1.6.7+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAltt4sQVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLReQgAKlVI0CA3uQsfV++VRMPHO+De7Sw
FKi5+Zmehue+ayE5rYeUItlzt4ervDLx8BbW0eJdfa5/RTB7l4HQNSV98o1qztFO
OvBL0GvmXAGZF7lHkIaFznvMmumvkqlBANG2OwVQwnVSnBSORIIwkA3stL9JzKBK
4BfzhjrHVMmatRMYdE5QWjDNyO081KTj1xyvmU4yys39WR7NRlbtaLASU+jVEjTz
kv8P/XlW+NMcIFamcN/bE3wn+3xLFh62vBKGsQL6Tlzg9v+liPAuUidmO3F6bQpP
zi2OfIqzrv1btLs8PrPI0VVf5L9cMM25ebqhYs80IXocPlIOFuU34BvuOiw6W6M3
RFBHxLKokF3PVcX/A/xu2omm/KYc2VxzJ/JsF1c3YlFTBchiCsPEJl8lYiF/cSj2
nghGEHP2srd1QTJhsewzrcH8m3ikOMtERqvjSSmgFdGwmWJFQxGU3+M6OvftJZ2U
efdQKAIU60F/linz07fd2l8c8UeJENPWlod0J/IdCuh5z8a73XW4STAqbLXcLYSO
WjLaXELCIvVPdz7YvaVAO76nxjJnPWFO9mLnL/F9Wu0DMi8bifBuHPlwU5G4HtFr
GXgbYuYDnv73kB2zMKc/1CqJBAM0rC/ybhgXBWMemYY3+wEdOOeUtVHzMX/1AMyf

Bug#905198: python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Pierre-Elliott Bécue]

Le vendredi 10 août 2018 à 18:01:11+0200, Pierre-Elliott Bécue a écrit :
> Le mercredi 01 août 2018 à 14:23:42+0200, Andreas Beckmann a écrit :
> > [python-ldap-dbg is a bad boy]
> [not working properly]

Hmmm, python-ldap-dbg is Multi-Arch: same, could it be the source of the
problem?

Cheers,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#905198: python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Pierre-Elliott Bécue]

Le mercredi 01 août 2018 à 14:23:42+0200, Andreas Beckmann a écrit :
> [python-ldap-dbg is a bad boy]

Hi Andreas,

I tried to fix that in a separate branch on salsa[1], see specifically
commit 988d4f6[2]. Unfortunately, although I followed all the steps I'm
aware of, `sudo piuparts -d stretch -d buster
python-ldap-dbg_3.1.0-3_amd64.deb python-ldap_3.1.0-3_amd64.deb` still
returns the same error.

I asked for some help on d-mentors IRC channel, but if you find some time,
please could you review and help me determine what my mistake is?

Cheers!

[1] https://salsa.debian.org/python-team/modules/python-ldap/tree/fix_905198
[2] 
https://salsa.debian.org/python-team/modules/python-ldap/commit/988d4f6418fb16762cd10022db2399de4c9d0438

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#737921: WE PROVIDE BG, SBLC, MT103, POF, SKR, DISCOUNTING AND LOANS FOR YOUR PROJECTS.

[HALIFAX BANK]

Sir,

We Halifax Bank Plc provide Loans,BG,SBLC,MTN,POF,LC,SKR Discounting,Project
Funding,Letter of credit, and lots more for client all over the world.

Equally,we are ready to work with Brokers and financial consultants/consulting
firms in their respective countries.

we are equally ready to pay commission to those Brokers and financial
consultants/consulting firms.

For more information/detail contact us via E-mail:halifaxbnk...@gmail.com

Awaiting for your response.

Best Regards.

Advert Team.
Halifax Bank Plc.
244/246 High Street,Beckenham BR3 1DZ,
London, United Kingdom.

Processed: tagging 905831

[Debian Bug Tracking System]

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

> tags 905831 + ftbfs
Bug #905831 [ne10] Fails to build on armhf
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 905831

[Debian Bug Tracking System]

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

> tags 905831 + buster sid
Bug #905831 [ne10] Fails to build on armhf
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#905844: git-remote-hg: crash with recent mercurial: argument must be a string or a number, not 'changectx'

[Jonas Smedegaard]

Package: git-remote-hg
Version: 0.3-2
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After a recent update to mercurial, attempts at syncing fails:

LC_ALL=C git fetch upstream-git 
searching for changes
no changes found
ERROR: int() argument must be a string or a number, not 'changectx'
fatal: stream ends early
fast-import: dumping crash report to .git/fast_import_crash_12488
fatal: Error while running fast-import


It seems to be this upstream issue:
https://github.com/felipec/git-remote-hg/issues/72


 - Jonas

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

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

Versions of packages git-remote-hg depends on:
ii  git1:2.18.0-1
ii  mercurial  4.7-1
ii  python 2.7.15-3

git-remote-hg recommends no packages.

Versions of packages git-remote-hg suggests:
pn  git-doc  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlttn7oACgkQLHwxRsGg
ASF7uA//baOG8EdUMmM/TsBbSCBzCdYvsKo5PY29MeTyvhMWRhKGzKVwwoKs2C20
TCchG9J18T1U4fo1YE4igISAbwXhDlbm6JENFx1PnDwW+gZUkHSDs9awGfppnVMI
eJAY762m/KW6ZaXdnkyUERJU+wT7jBtD1kbWoLdOcBev1zlzJ28cIUDUFtnOEEx3
+vw9gu6wv4VhTLPIx5i4OFiXYepDz3I/ClG6NU6ol7o94v8e72myo0J1QomxnssO
8/FOd2OqZk/JU9TOlH8QSu2D50hV06UmlBYr+NDmwS9L+B/9Tx9RHn7fvW4/Joce
N63ISPQ6OiiK3HBRWhL1ULD1/jkgclbaEcYYQ0qJxWGZiE36PBu66hMYWtq95rxv
QKfwbg3oamyYb4YaGkeYRgJROKtLR7vrqDbxAzX/ByaYYZX21cprHS8i2BUN4RI4
pe2ifG/mQFij/RG7df6igUBrz0MGGJC7FjNnk9t1U6NBqDMEjx7p8R2nJerVC5En
qicsiRbCoTN9xZ7ulnIobKXuPMwSofz00hcFMUgVif22Q+g+Cu0FQ7Z665MakLHK
Jm+SFvJfXcSYMzF2ridwrhjsBaoOPWku6/VsN4g5JgcdNb1LE2NgD491GvkF/LZL
8HoJ3dPqQq6XjKXEbARVCYlzMfaAWeYh7D35gpvKoyy5R88K7X0=
=rT1r
-END PGP SIGNATURE-

Processed: tagging 897780

[Debian Bug Tracking System]

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

> tags 897780 + ftbfs
Bug #897780 [src:libbpp-core] libbpp-core: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897781

[Debian Bug Tracking System]

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

> tags 897781 + ftbfs
Bug #897781 [src:libbpp-phyl-omics] libbpp-phyl-omics: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897783

[Debian Bug Tracking System]

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

> tags 897783 + ftbfs
Bug #897783 [src:libbpp-qt] libbpp-qt: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897782

[Debian Bug Tracking System]

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

> tags 897782 + ftbfs
Bug #897782 [src:libbpp-popgen] libbpp-popgen: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#905841: libltdl-dev: dependency on specific automake version

[Amos Jeffries]

Package: libltdl-dev
Version: 2.4.6-2.1
Severity: grave

The update of automake to version 1.16 causes FTBFS in software using
libltdl-dev.

The libltdl-dev package installs a libtool/aclocal.m4 file which
contains a macro hard-coding the automake version used to build the
libtool sources.

Any software using libtoolize inherits the installed libtool/aclocal.m4
file as libltdl/aclocal.m4 which in turn then gets built into
libltdl/configure when the user software bootstrap's from configure.ac
files.

The end result is the following error whenever automake version differs
from the one libltdl-dev was built with:

cfgaux/missing: line 81: aclocal-1.15: command not found
WARNING: 'aclocal-1.15' is missing on your system.
 You should only need it if you modified 'acinclude.m4' or
 'configure.ac' or m4 files included by 'configure.ac'.
 The 'aclocal' program is part of the GNU Automake package:
 
 It also requires GNU Autoconf, GNU m4 and Perl in order to run:
 
 
 
make[1]: *** [Makefile:540: ../../libltdl/aclocal.m4] Error 127


As I write this Debian currently has "automake" from automake-1.16
sources, and "libltdl-dev" built when automake-1.15 was the current.

Repeating the bootstrap / autoreconf process in the software seeing this
error "resolves" the problem *if* (and only if) the automake and
libltdl-dev versions match. When the packages differ as Debian Sid
machines do right now the autoreconf will still pull in the outdated
libltdl-dev files and the FTBFS problem remains.


Please add a versioned Depends on the specific automake-1.X package used
to build libltdl-dev to prevent development machines installing newer
versions of automake before libltdl-dev is rebuilt to be compatible.


Thanks
AYJ

Bug#905836: Uninstallable on a Clean Sid - update-alternatives Fails to Create a Symbolic Link

[殷啟聰 | Kai-Chung Yan]

Package: openjdk-10-jre-headless
Version: 10.0.2+13-1
Severity: grave

This package fails to install on the Docker image "debian:sid-slim". The 
postinst fails to execute successfully. Below is the log:

```
seamlik@zenbook:~$ sudo docker run --rm -it debian:sid-slim bash
[sudo] password for seamlik: 
root@24f6024890b9:/# apt update
Get:1 http://cdn-fastly.deb.debian.org/debian sid InRelease [233 kB]
Get:2 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages [8195 kB]
Fetched 8427 kB in 15s (566 kB/s)   
   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
29 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@24f6024890b9:/# apt install openjdk-10-jre-headless
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  ca-certificates ca-certificates-java dbus fontconfig-config fonts-dejavu-core 
java-common
  krb5-locales libapparmor1 libavahi-client3 libavahi-common-data 
libavahi-common3 libbsd0
  libcups2 libdbus-1-3 libexpat1 libfontconfig1 libfreetype6 libgssapi-krb5-2 
libjpeg62-turbo
  libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libnspr4 
libnss3 libpcsclite1
  libpng16-16 libsqlite3-0 libssl1.1 libx11-6 libx11-data libxau6 libxcb1 
libxdmcp6 libxext6
  libxi6 libxrender1 libxtst6 lsb-base openssl sensible-utils ucf x11-common
Suggested packages:
  default-dbus-session-bus | dbus-session-bus default-jre cups-common krb5-doc 
krb5-user
  liblcms2-utils pcscd libnss-mdns fonts-dejavu-extra fonts-ipafont-gothic 
fonts-ipafont-mincho
  fonts-wqy-microhei | fonts-wqy-zenhei fonts-indic
The following NEW packages will be installed:
  ca-certificates ca-certificates-java dbus fontconfig-config fonts-dejavu-core 
java-common
  krb5-locales libapparmor1 libavahi-client3 libavahi-common-data 
libavahi-common3 libbsd0
  libcups2 libdbus-1-3 libexpat1 libfontconfig1 libfreetype6 libgssapi-krb5-2 
libjpeg62-turbo
  libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libnspr4 
libnss3 libpcsclite1
  libpng16-16 libsqlite3-0 libssl1.1 libx11-6 libx11-data libxau6 libxcb1 
libxdmcp6 libxext6
  libxi6 libxrender1 libxtst6 lsb-base openjdk-10-jre-headless openssl 
sensible-utils ucf
  x11-common
0 upgraded, 45 newly installed, 0 to remove and 29 not upgraded.
Need to get 50.1 MB of archives.
After this operation, 210 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://cdn-fastly.deb.debian.org/debian sid/main amd64 sensible-utils all 
0.0.12 [15.8 kB]
Get:2 http://cdn-fastly.deb.debian.org/debian sid/main amd64 lsb-base all 
9.20170808 [28.1 kB]
Get:3 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libapparmor1 amd64 
2.13-8 [91.3 kB]
Get:4 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libdbus-1-3 amd64 
1.12.10-1 [211 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libexpat1 amd64 
2.2.5-3 [96.8 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian sid/main amd64 dbus amd64 
1.12.10-1 [233 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian sid/main amd64 krb5-locales all 
1.16-2 [94.7 kB]
Get:8 http://cdn-fastly.deb.debian.org/debian sid/main amd64 ucf all 3.0038 
[67.8 kB]
Get:9 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libssl1.1 amd64 
1.1.0h-4 [1352 kB]
Get:10 http://cdn-fastly.deb.debian.org/debian sid/main amd64 openssl amd64 
1.1.0h-4 [744 kB]  
Get:11 http://cdn-fastly.deb.debian.org/debian sid/main amd64 ca-certificates 
all 20180409 [161 kB]
Get:12 http://cdn-fastly.deb.debian.org/debian sid/main amd64 java-common all 
0.68 [14.3 kB]   
Get:13 http://cdn-fastly.deb.debian.org/debian sid/main amd64 
libavahi-common-data amd64 0.7-4 [122 kB]
Get:14 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libavahi-common3 
amd64 0.7-4 [54.4 kB]
Get:15 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libavahi-client3 
amd64 0.7-4 [57.8 kB]
Get:16 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libkeyutils1 
amd64 1.5.9-9.3 [13.0 kB]
Get:17 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libkrb5support0 
amd64 1.16-2 [62.8 kB]
Get:18 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libk5crypto3 
amd64 1.16-2 [121 kB]   
Get:19 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libkrb5-3 amd64 
1.16-2 [316 kB]  
Get:20 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libgssapi-krb5-2 
amd64 1.16-2 [158 kB]
Get:21 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libcups2 amd64 
2.2.8-5 [322 kB]  
Get:22 http://cdn-fastly.deb.debian.org/debian sid/main amd64 liblcms2-2 amd64 
2.9-2 [145 kB]  
Get:23 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libjpeg62-turbo 
amd64 1:1.5.2-2+b1 [134 kB]
Get:24 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libpng16-16 amd64 
1.6.34-2 [288 kB]  
Get:25 

Bug#905788: marked as done (FTBFS: cannot find -lgpod)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 17:01:06 +0500
with message-id <20180810120106.gg1...@belkar.wrar.name>
and subject line Re: Bug#905788: Acknowledgement (FTBFS: cannot find -lgpod)
has caused the Debian Bug report #905788,
regarding FTBFS: cannot find -lgpod
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.)


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

Trying to build the package in a fresh sid sbuild chroot I get

libtool: warning: relinking '_gpod.la'
libtool: install: (cd /<>/build/python2.7/bindings/python;
/bin/bash "/<>/build/python2.7/libtool"  --tag CC --mode=relink
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -module -avoid-version -shared -Wl,-z,relro
-Wl,-O1 -Wl,--as-needed -o _gpod.la -rpath /usr/lib/python2.7/dist-
packages/gpod _gpod_la-gpod_wrap.lo -lgobject-2.0 -lsqlite3 -lplist -Wl,--
export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lxml2 -lgdk_pixbuf-2.0
-lgobject-2.0 -lglib-2.0 -lgobject-2.0 -lglib-2.0 ../../src/libgpod.la -inst-
prefix-dir /<>/debian/tmp)
Byte-compiling python modules (optimized versions) ...
__init__.pygtkpod.pyipod.py
Byte-compiling python modules (optimized versions) ...
gpod.py
libtool: relink: gcc -shared  -fPIC -DPIC  .libs/_gpod_la-gpod_wrap.o
-L/<>/debian/tmp/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-
gnu -lsqlite3 -lplist -lgmodule-2.0 -lxml2 -lgdk_pixbuf-2.0 -lgobject-2.0
-lglib-2.0 -lgpod  -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-O1
-Wl,--as-needed -Wl,--export-dynamic -pthread   -pthread -Wl,-soname
-Wl,_gpod.so -o .libs/_gpod.so
/usr/bin/ld: cannot find -lgpod
collect2: error: ld returned 1 exit status
libtool:   error: error: relink '_gpod.la' with the above command before
installing it



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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash

-- 
WBR, wRAR


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
This FTBFS only happens with dpkg-buildpackage -j so it is not a bug.

-- 
WBR, wRAR


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

Bug#886936: marked as done (icewm-lite: fails to install: update-alternatives: error: alternative path /usr/bin/icewm-lite doesn't exist)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 13:43:57 +0200
with message-id <87600ifnuq@turtle.gmx.de>
and subject line Re: Bug#886936: icewm-lite: fails to install: 
update-alternatives: error: alternative path /usr/bin/icewm-lite doesn't exist
has caused the Debian Bug report #886936,
regarding icewm-lite: fails to install: update-alternatives: error: alternative 
path /usr/bin/icewm-lite doesn't exist
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.)


-- 
886936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icewm-lite
Version: 1.4.3.0~pre-20171225-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package icewm-lite.
  (Reading database ... 
(Reading database ... 5150 files and directories currently installed.)
  Preparing to unpack .../icewm-lite_1.4.3.0~pre-20171225-1_amd64.deb ...
  Unpacking icewm-lite (1.4.3.0~pre-20171225-1) ...
  Setting up icewm-lite (1.4.3.0~pre-20171225-1) ...
  update-alternatives: error: alternative path /usr/bin/icewm-lite doesn't exist
  dpkg: error processing package icewm-lite (--configure):
   installed icewm-lite package post-installation script subprocess returned 
error exit status 2
  Errors were encountered while processing:
   icewm-lite


cheers,

Andreas


icewm-lite_1.4.3.0~pre-20171225-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: icewm
Version: 1.4.3.0~pre-20180809-1

On 2018-01-11 14:21 +0100, Andreas Beckmann wrote:

> Package: icewm-lite
> Version: 1.4.3.0~pre-20171225-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
>
> From the attached log (scroll to the bottom...):
>
>   Selecting previously unselected package icewm-lite.
>   (Reading database ... 
> (Reading database ... 5150 files and directories currently installed.)
>   Preparing to unpack .../icewm-lite_1.4.3.0~pre-20171225-1_amd64.deb ...
>   Unpacking icewm-lite (1.4.3.0~pre-20171225-1) ...
>   Setting up icewm-lite (1.4.3.0~pre-20171225-1) ...
>   update-alternatives: error: alternative path /usr/bin/icewm-lite doesn't 
> exist

This happened because /usr/bin/icewm-lite is a symlink to icewm, but the
icewm-lite package did not depend on icewm (which ships /usr/bin/icewm),
and so the symlink was dangling.

The missing dependency has been added in 1.4.3.0~pre-20180809-1, and I
have just verified that 1.4.3.0~pre-20180809-2 correctly installs in a
pbuilder chroot.  Would have been nice if debian/changelog had mentioned
something along those lines.

Cheers,
   Sven--- End Message ---

Bug#891434: grub-efi: System fails to boot after "No space left on device" on EFI variable storage

[Ralf Jung]

Just had this again, this time even after I repaired Debian, Windows disappeared
completely from the start menu.  I do not yet know how to get it back.

What does it take to get attention t a bug that completely breaks the system?

Kind regards,
Ralf

Bug#905831: Fails to build on armhf

[Sjoerd Simons]

Package: ne10
Version: 1.2.1-3
Severity: serious
Tags: patch
Justification: fails to build from source

As per
https://buildd.debian.org/status/fetch.php?pkg=ne10=armhf=1.2.1-3=1478897528=0
the build of ne10 fails on armhf. This is because it detects the build
environment as targetting aarch64. From the log:
  -- Target architecture : aarch64

Attached is the debdiff from a derivative we hvae which fixes the issue.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'proposed-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.18.0-rc4-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ne10-1.2.1/debian/changelog ne10-1.2.1/debian/changelog
--- ne10-1.2.1/debian/changelog 2016-10-18 19:01:22.0 +0200
+++ ne10-1.2.1/debian/changelog 2018-08-10 12:26:58.0 +0200
@@ -1,3 +1,9 @@
+ne10 (1.2.1-3co1) apertis; urgency=medium
+
+  * Fix build on armhf
+
+ -- Sjoerd Simons   Fri, 10 Aug 2018 12:26:58 +0200
+
 ne10 (1.2.1-3) unstable; urgency=medium
 
   * Update copyright file for modules/*
diff -Nru ne10-1.2.1/debian/rules ne10-1.2.1/debian/rules
--- ne10-1.2.1/debian/rules 2016-10-12 19:35:53.0 +0200
+++ ne10-1.2.1/debian/rules 2018-08-10 12:26:57.0 +0200
@@ -13,12 +13,19 @@
 # package maintainers to append LDFLAGS
 #export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
+ifeq ($(DEB_TARGET_GNU_CPU),arm)
+   NE10_LINUX_TARGET_ARCH = armv7
+else
+   NE10_LINUX_TARGET_ARCH = ${DEB_TARGET_GNU_CPU}
+endif
+
 %:
dh $@ 
 
 override_dh_auto_configure:
+   
dh_auto_configure -- \
-   -DNE10_LINUX_TARGET_ARCH=$(DEB_TARGET_GNU_CPU) \
+   -DNE10_LINUX_TARGET_ARCH=$(NE10_LINUX_TARGET_ARCH) \
-DGNULINUX_PLATFORM=ON \
-DNE10_BUILD_SHARED=ON
 

Bug#899117: marked as done (gnome-music: missing dependency gir1.2-goa-1.0)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 09:48:58 +
with message-id 
and subject line Bug#899117: fixed in gnome-music 3.28.2.1-2
has caused the Debian Bug report #899117,
regarding gnome-music: missing dependency gir1.2-goa-1.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.)


-- 
899117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-music
Version: 3.28.2.1-1
Severity: important

Dear Maintainer,

gnome-music does not start since 3.27.90-1 (at least for me it was that 
version). The error I get:

foo@bar:~$ gnome-music 
Traceback (most recent call last):
  File "/usr/bin/gnome-music", line 142, in 
sys.exit(main())
  File "/usr/bin/gnome-music", line 137, in main
return run_application()
  File "/usr/bin/gnome-music", line 123, in run_application
from gnomemusic.application import Application
  File "/usr/lib/python3/dist-packages/gnomemusic/application.py", line 40, in 

from gnomemusic.mpris import MediaPlayer2Service
  File "/usr/lib/python3/dist-packages/gnomemusic/mpris.py", line 28, in 

from gnomemusic.player import PlaybackStatus, RepeatType
  File "/usr/lib/python3/dist-packages/gnomemusic/player.py", line 53, in 

from gnomemusic.scrobbler import LastFmScrobbler
  File "/usr/lib/python3/dist-packages/gnomemusic/scrobbler.py", line 31, in 

gi.require_version('Goa', '1.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 130, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Goa not available

   * What led up to the situation?

I updated from 3.26.1-4 to 3.27.90-1 and it stopped working. I was not sure why 
and didn't bother looking into it. Since then my update log for gnome-music 
looks like following:

[UPGRADE] gnome-music:amd64 3.27.90-1 -> 3.27.92.1-1
[UPGRADE] gnome-music:amd64 3.27.92.1-1 -> 3.28.0-1
[UPGRADE] gnome-music:amd64 3.28.0-1 -> 3.28.0.1-1
[REINSTALL] gnome-music:amd64 3.28.0.1-1
[UPGRADE] gnome-music:amd64 3.28.0.1-1 -> 3.28.1-1
[UPGRADE] gnome-music:amd64 3.28.1-1 -> 3.28.2.1-1

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I just discovered that installing gir1.2-goa-1.0 solved the problem.

   * What was the outcome of this action?

It works now.


Please consider adding gir1.2-goa-1.0 to gnome-music's dependencies. I'm not 
sure why it needs it, it's not using anything related to goa (Gnome Online 
Accounts), but that's how it is.


Thank you for your work.

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

Kernel: Linux 4.16.0-1-amd64 (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)
LSM: AppArmor: enabled

Versions of packages gnome-music depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.28.0-2
ii  gir1.2-glib-2.0  1.56.1-1
ii  gir1.2-grilo-0.3 0.3.4-1
ii  gir1.2-gst-plugins-base-1.0  1.14.0-2
ii  gir1.2-gstreamer-1.0 1.14.0-1
ii  gir1.2-gtk-3.0   3.22.29-3
ii  gir1.2-mediaart-2.0  1.9.4-1
ii  gir1.2-notify-0.70.7.7-3
ii  gir1.2-totemplparser-1.0 3.26.0-2
ii  gir1.2-tracker-2.0   2.0.3-3
ii  gnome-settings-daemon3.28.1-1
ii  grilo-plugins-0.30.3.5-2+b1
ii  libc62.27-3
ii  libcairo-gobject21.15.10-3
ii  libcairo21.15.10-3
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.29-3
ii  libpango-1.0-0   1.42.0-1
ii  libpangocairo-1.0-0  1.42.0-1
ii  python3  3.6.4-1
ii  python3-gi   3.28.2-1
ii  python3-gi-cairo 3.28.2-1
ii  python3-requests 2.18.4-2
ii  tracker  2.0.3-3

gnome-music recommends no packages.

gnome-music suggests no packages.

-- no debconf 

Processed: Re: Bug#891063:

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413
Bug #891063 [emacs25] When run as root, emacs reads/writes dconf files in a 
non-root user's /run/user/XXX directory
Set Bug forwarded-to-address to 
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413'.

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

Bug#891063:

[Vincent Lefevre]

Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413

On 2018-08-10 01:09:13 -0500, Rob Browning wrote:
> Vincent Lefevre  writes:
> > "su -l" is not a solution as it reset the current working directory.
> > And one should still be able to run X applications after su.
> 
> Hmm, is that true?

-, -l, --login
Start  the shell as a login shell with an environment similar to
a real login:

   o  clears all the environment variables except TERM

   o  initializes the  environment  variables  HOME,  SHELL,
  USER, LOGNAME, and PATH

   o  changes to the target user's home directory
  ^^^

   o  sets  argv[0] of the shell to '-' in order to make the
  shell a login shell

The fact that it clears all the environment variables except TERM.
The fact that the LC_* environment variables are cleared may be
annoying too. BTW, there is no guarantee that TERM will still work
if TERMINFO is cleared! I sometimes use a user-defined TERM, so
that keeping TERMINFO is important in that case.

> I don't actually know, but the suggestion I'd often
> heard is to generally avoid running X applications much as root, but if
> I were going to, I'd use "su -", which (now that I look) does appear to
> handle at least XAUTHORITY -- though I'd still be wary.

As you can see above, XAUTHORITY is cleared too.

I also avoid running X applications, except Emacs.

> > But in any case, emacs shouldn't create files/directories if the
> > user hasn't explicitly asked it to do that.
> 
> I'd expect emacs to create various files via gtk, dbus, and other
> subsystems it uses, and it's certainly going to create bits like
> ~/.emacs and ~/.emacs.d if it needs to (for M-x customize, etc.).

I don't use M-x customize, certainly not as root. If the user doesn't
modify his configuration, there is no need to create such files.
Anyway, for ~/.emacs and ~/.emacs.d, there are no problems since
HOME is set to one for the target user, e.g. to "/root" (unless
-m or -p is used, but I've said that I do not use them).

> Whether or not it's doing it correctly is another question, but I'm not
> at all surprised that plain "su" with an X-based emacs frame (i.e. not
> "emacs -nw") has trouble.

Historically, there had never been any problem. AFAIK, it was assumed
that the only files that could be created automatically (e.g. caches)
would be under $HOME, but HOME is set to one for the target user,
avoiding issues.

The same bug was reported here against Fedora 25:

  https://bugzilla.redhat.com/show_bug.cgi?id=921689

and was closed a few years later due to Fedora 25 EOL.

I've also just seen

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732209

but this may be different as this is related to desktop environments
(potentially a more complex case to decide what to do).

> If you want to pursue this, I suspect you should pursue it upstream,
> or I'll plan to forward it later if you prefer.

I've just reported a bug upstream:

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#899117: Bug #899117 in gnome-music marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #899117 in gnome-music 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/gnome-team/gnome-music/commit/a802525d9129852dcfe889ea03acfdd766d3f5f4


Add missing dependency on gir1.2-goa-1.0

Closes: #899117



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/899117

Processed: Bug #899117 in gnome-music marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #899117 [gnome-music] gnome-music: missing dependency gir1.2-goa-1.0
Added tag(s) pending.

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

Bug#905816: [Pkg-mozext-maintainers] Bug#905816: xul-ext-form-history-control: rename to webext-form-history-control, set correct dependencies

[Michael Meskes]

> It has been redone as a web extension without renaming to webext-*.

Ah, ok, thanks for clarifying.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL


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

Bug#897798: marked as done (libunivalue: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 09:19:05 +
with message-id 
and subject line Bug#897798: fixed in libunivalue 1.0.3-7
has caused the Debian Bug report #897798,
regarding libunivalue: ftbfs with GCC-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.)


-- 
897798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libunivalue
Version: 1.0.3-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/libunivalue_1.0.3-4_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libunivalue0/DEBIAN/symbols doesn't match 
completely debian/libunivalue0.symbols
--- debian/libunivalue0.symbols (libunivalue0_1.0.3-4_amd64)
+++ dpkg-gensymbolsLB60QA   2018-05-02 13:28:24.907099687 +
@@ -4,7 +4,7 @@
  _Z10uvTypeNameN8UniValue5VTypeE@Base 1.0.2
 #MISSING: 1.0.3-2# 
_Z12getJsonTokenRNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERjPKc@Base 
1.0.2
  
_Z12getJsonTokenRNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERjPKcS8_@Base
 1.0.3-2~
- _ZN20JSONUTF8StringFilter16append_codepointEj@Base 1.0.3-2~
+#MISSING: 1.0.3-4# _ZN20JSONUTF8StringFilter16append_codepointEj@Base 1.0.3-2~
  _ZN20JSONUTF8StringFilter9push_backEh@Base 1.0.3-2~
  _ZN8UniValue10push_backVERKSt6vectorIS_SaIS_EE@Base 1.0.2
  
_ZN8UniValue11checkObjectERKSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS_5VTypeESt4lessIS6_ESaISt4pairIKS6_S7_EEE@Base
 1.0.2
@@ -44,23 +44,25 @@
  _ZNK8UniValueixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
1.0.2
  (arch-bits=32)_ZNK8UniValueixEj@Base 1.0.3-2~
  (arch-bits=64)_ZNK8UniValueixEm@Base 1.0.3-2~
-#MISSING: 1.0.3-2# 
(optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS0_S2_EERKS0_@Base
 1.0.2
+#MISSING: 1.0.3-4# 
(optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS0_S2_EERKS0_@Base
 1.0.2
  
(optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EE15_M_range_insertIN9__gnu_cxx17__normal_iteratorIPKS0_S2_vNS5_IPS0_S2_EET_SB_St20forward_iterator_tag@Base
 1.0.2
  
(optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 1.0.3-3~
-#MISSING: 1.0.3-3~# 
(optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EE19_M_emplace_back_auxIJRKS0_EEEvDpOT_@Base
 1.0.3-2~
+#MISSING: 1.0.3-4# 
(optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EE19_M_emplace_back_auxIJRKS0_EEEvDpOT_@Base
 1.0.3-2~
  (optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EED1Ev@Base 1.0.2
  (optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EED2Ev@Base 1.0.2
  (optional=templinst)_ZNSt6vectorI8UniValueSaIS0_EEaSERKS2_@Base 1.0.2
-#MISSING: 1.0.3-2# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS5_S7_EERKS5_@Base
 1.0.2
+#MISSING: 1.0.3-4# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS5_S7_EERKS5_@Base
 1.0.2
  
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 1.0.3-3~
-#MISSING: 1.0.3-3~# 

Bug#905578: Install script from emacs-goodies-el package failed

[Sean Whitton]

Hello,

On Tue 07 Aug 2018 at 09:28PM -0400, Nicholas D Steeves wrote:

> On Tue, Aug 07, 2018 at 10:12:25AM +0800, Sean Whitton wrote:
>> Hello,
>>
>> On Mon 06 Aug 2018 at 09:18AM -0400, Nicholas D Steeves wrote:
>>
>> > Thank you for not overriding the default apt behaviour of allowing
>> > upgrades to install additional recommended packages.  The Debian
>> > Emacsen team is in the process of transitioning emacs-goodies-el to a
>> > dummy transitional package that depends on a set of elpa-packages,
>> > which are more resistant to the type of issue [1] represents.
>>
>> Just to be clear, as a package maintainer you may not assume that
>> recommends will be installed.
>
> Yes, of course...
>
> In your opinion, should emacs-goodies-el use hard depends at this
> time?  Also, as a matter of policy, must dummy transitional packages
> use hard depends?

ISTM that it should be a Depends: relation.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#905816: [Pkg-mozext-maintainers] Bug#905816: xul-ext-form-history-control: rename to webext-form-history-control, set correct dependencies

[Paul Wise]

On Fri, 2018-08-10 at 10:24 +0200, Michael Meskes wrote:

> I doubt it magically becomes a web extension just because we rename the
> package. I haven't checked this particular extension, but if it has not
> been redone as a web extension it cane be removed. If it has, though,
> it needs to be updated to the latest version.

It has been redone as a web extension without renaming to webext-*.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#904403: marked as done (goiardi: fails to install: chown: cannot access '/var/lib/goiardi/lfs/*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 08:34:13 +
with message-id 
and subject line Bug#904403: fixed in goiardi 0.11.8-2
has caused the Debian Bug report #904403,
regarding goiardi: fails to install: chown: cannot access 
'/var/lib/goiardi/lfs/*': No such file or directory
to be marked as done.

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

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


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

Hi,

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

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

  Selecting previously unselected package goiardi.
  (Reading database ... 
(Reading database ... 4469 files and directories currently installed.)
  Preparing to unpack .../goiardi_0.11.8-1_amd64.deb ...
  Unpacking goiardi (0.11.8-1) ...
  Setting up goiardi (0.11.8-1) ...
  adduser: Warning: The home directory `/var/lib/goiardi' does not belong to 
the user you are currently creating.
  chown: cannot access '/var/lib/goiardi/lfs/*': No such file or directory
  dpkg: error processing package goiardi (--configure):
   installed goiardi package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   goiardi

cheers,

Andreas


goiardi_0.11.8-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: goiardi
Source-Version: 0.11.8-2

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

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

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated goiardi 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 09:41:14 +0200
Source: goiardi
Binary: goiardi golang-github-ctdk-goiardi-dev goiardi-doc
Architecture: source
Version: 0.11.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Jordi Mallach 
Description:
 goiardi- Chef server written in Go
 goiardi-doc - Documentation for Goiardi
 golang-github-ctdk-goiardi-dev - Golang library to interact with a chef server
Closes: 904403
Changes:
 goiardi (0.11.8-2) unstable; urgency=medium
 .
   * Do not chown /var/lib/goiardi/lfs contents, generated by the server
 (closes: #904403).
Checksums-Sha1:
 c6efe9ba201c32beb11169b519c3379ada1aad93 3093 goiardi_0.11.8-2.dsc
 9078c8e05d5310a698bca5adc638e4b4769b65a0 19892 goiardi_0.11.8-2.debian.tar.xz
 be9177d792555cda3aba4c38c61a2c474589d06a 6949 goiardi_0.11.8-2_source.buildinfo
Checksums-Sha256:
 ad2bfbf1469c367929dcd07930dfb5f2e54871f18a09e78b1c5c9f353068a009 3093 
goiardi_0.11.8-2.dsc
 f59e52e0573172da13288ab0b9bed49e3795112b11a140191db1b841831a3026 19892 
goiardi_0.11.8-2.debian.tar.xz
 3329f4f9fbdae9b69a9af68cd7618e2733b9e0a7fdcf19a7463d67a3303cd2a6 6949 
goiardi_0.11.8-2_source.buildinfo
Files:
 ba30fc1de2a1cf7c6c8609e44715888b 3093 admin optional goiardi_0.11.8-2.dsc
 758d8da017bf463105e84e88f28ac44d 19892 admin optional 
goiardi_0.11.8-2.debian.tar.xz
 b441c623c367b8fbc1095bce21fca87e 6949 admin optional 
goiardi_0.11.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAlttRM4RHGpvcmRpQGRl
Ymlhbi5vcmcACgkQJVAvb8vjywSO7xAAr0+ovvnZygkW8j63VcmSGuDCfoS8Y3YI
hlZ+U72ONSuDS07ABkMuuxJJoIJAG2KoiL+K1dV3Y32WLrFcA26AraXg8K2Z56rl
H/KhCyI3uJPXW+CTYyfAw52aDlzweJcb0k+9OKqQj3V47dK5vxpVuT+CP/PhyKk+
2RHKvoN0Ws4SCBdEBN4k2++mFxPsLXKGbLQbYq8q7hfIeHPrdlmwRiKlQYByp0iR
04I3+G10B7pVLRTMmWDfgWHVxZA6EY5nSOHJz6vP33L+UB01bVhpwN/1vTZScC63
1rHdeAiFeYsS/k/QKk1xxY9nZ4xIPxf9WXqI2W+u1c7SoBqLUQg19h4oEU0DmdIT
9por7IL3E7x532/7Be57sbufVYvhy9xD/c/8DkLY80Ko0cR/GVs1SDaLlgrr6ToL
nWQLnSPNHv5RlJG6NW3T0gBDr+REDFjOJzTQ5i79CYbBO5iYrM5FtAGCXdJs1HdG
U1F4Mn5x+5zI8Eh0n6tSNP+CnUSoORNMyGgAGytv247ehiFyqtolKgvuSErmO/EQ
UiPu6uDYNlHfJgrlBm5EYWz5YM2ufjWgMFqyVEPvKvjVoLhvVYY25N58r8lDtbTi

Bug#905682: marked as done (kido: FTBFS (can't find , which appears to now be in libnlopt-cxx-dev))

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 08:34:30 +
with message-id 
and subject line Bug#905682: fixed in kido 0.1.0+dfsg-3
has caused the Debian Bug report #905682,
regarding kido: FTBFS (can't find , which appears to now be in 
libnlopt-cxx-dev)
to be marked as done.

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

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


-- 
905682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kido
Version: 0.1.0+dfsg-2
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

kido fails to build in unstable right now due to the libnlopt-dev split.

cd /<>/kido-0.1.0+dfsg/build/kido/optimizer/nlopt && 
/usr/lib/ccache/c++  -DBOOST_TEST_DYN_LINK -DHAVE_BULLET_COLLISION 
-Dkido_optimizer_nlopt_EXPORTS -I/<>/kido-0.1.0+dfsg -isystem 
/usr/include/eigen3 -isystem /usr/include/bullet 
-I/<>/kido-0.1.0+dfsg/build  -Wall -fPIC -std=c++11 -g -O2 
-fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   
-I/usr/include/bullet -o CMakeFiles/kido-optimizer-nlopt.dir/NloptSolver.cpp.o 
-c /<>/kido-0.1.0+dfsg/kido/optimizer/nlopt/NloptSolver.cpp
In file included from 
/<>/kido-0.1.0+dfsg/kido/optimizer/nlopt/NloptSolver.cpp:39:
/<>/kido-0.1.0+dfsg/kido/optimizer/nlopt/NloptSolver.hpp:40:10: fatal 
error: nlopt.hpp: No such file or directory
 #include 
  ^~~
compilation terminated.
make[4]: *** 
[kido/optimizer/nlopt/CMakeFiles/kido-optimizer-nlopt.dir/build.make:66: 
kido/optimizer/nlopt/CMakeFiles/kido-optimizer-nlopt.dir/NloptSolver.cpp.o] 
Error 1
make[4]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
make[3]: *** [CMakeFiles/Makefile2:479: 
kido/optimizer/nlopt/CMakeFiles/kido-optimizer-nlopt.dir/all] Error 2
make[3]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
make[2]: *** [Makefile:144: all] Error 2
make[2]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
make[1]: *** [debian/rules:33: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/kido-0.1.0+dfsg'
make: *** [debian/rules:22: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (400, 'bionic-proposed'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- 
Kind regards,
Loong Jin
From 5b5b9f42177df7dbd3a91c38eddbd282e66f07b8 Mon Sep 17 00:00:00 2001
From: Chow Loong Jin 
Date: Wed, 8 Aug 2018 08:59:44 +0800
Subject: [PATCH] Exchange libnlopt-dev dependency for libnlopt-cxx-dev

/usr/include/nlopt.hpp has been moved into libnlopt-cxx-dev.
---
 debian/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 5488999..6a84e70 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Build-Depends: debhelper (>= 9.20151219),
libfcl-dev (>= 0.2.7),
libbullet-dev,
libassimp-dev (>= 3),
-   libnlopt-dev,
+   libnlopt-cxx-dev,
coinor-libipopt-dev,
freeglut3-dev,
libxi-dev,
@@ -365,7 +365,7 @@ Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends},
  libkido-dev,
  libkido-optimizer-nlopt0.1 (= ${binary:Version}),
- libnlopt-dev
+ libnlopt-cxx-dev
 Description: Kinematics Dynamics and Optimization Library - optimizer dev files
  KIDO is a collaborative, cross-platform, open source library created by the
  Georgia Tech Graphics Lab and Humanoid Robotics Lab. The library provides data
-- 
2.17.1



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: kido
Source-Version: 0.1.0+dfsg-3

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

Debian distribution 

Bug#905816: [Pkg-mozext-maintainers] Bug#905816: xul-ext-form-history-control: rename to webext-form-history-control, set correct dependencies

[Michael Meskes]

> Since the package no longer works with Firefox ESR 52 from Debian
> unstable and earlier, please rename it to webext-form-history-control 
> and set the dependencies to prevent installing it with Firefox ESR
> 52.

I doubt it magically becomes a web extension just because we rename the
package. I haven't checked this particular extension, but if it has not
been redone as a web extension it cane be removed. If it has, though,
it needs to be updated to the latest version.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL


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

Processed: tagging 897785

[Debian Bug Tracking System]

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

> tags 897785 + ftbfs
Bug #897785 [src:libbpp-seq-omics] libbpp-seq-omics: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#897727: marked as done (cp2k: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 11:23:00 +0300
with message-id <20180810082300.GA30561@localhost>
and subject line Re: Bug#897727: cp2k: ftbfs with GCC-8
has caused the Debian Bug report #897727,
regarding cp2k: ftbfs with GCC-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.)


-- 
897727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cp2k
Version: 5.1-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/cp2k_5.1-4_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
/<>/tools/build_utils/fypp -n 
/<>/src/base/base_hooks.F base_hooks.F90
mpif90 -c -g -Wall -O2 -ffast-math -funroll-loops -ftree-vectorize -ffree-form 
-ffree-line-length-none -D__GFORTRAN -D__FFTSG -D__FFTW3  -D__LIBINT 
-D__LIBINT_MAX_AM=6 -D__LIBDERIV_MAX_AM1=5 -D__LIBXC2 -D__parallel -D__BLACS 
-D__SCALAPACK -D__ELPA3 -I/usr/include/elpa/modules/ -I/usr/include 
-D__COMPILE_ARCH="\"Linux-x86_64-gfortran\"" -D__COMPILE_DATE="\"Wed May  2 
12:06:40 UTC 2018\"" -D__COMPILE_HOST="\"ip-172-31-12-4\"" 
-D__COMPILE_REVISION="\"svn:18091\"" -D__DATA_DIR="\"/usr/share/cp2k\"" 
-D__SHORT_FILE__="\"base/base_hooks.F\"" -I'/<>/src/base/' 
base_hooks.F90 
/<>/tools/build_utils/fypp -n 
/<>/src/acc/acc_stream.F acc_stream.F90
mpif90 -c -g -Wall -O2 -ffast-math -funroll-loops -ftree-vectorize -ffree-form 
-ffree-line-length-none -D__GFORTRAN -D__FFTSG -D__FFTW3  -D__LIBINT 
-D__LIBINT_MAX_AM=6 -D__LIBDERIV_MAX_AM1=5 -D__LIBXC2 -D__parallel -D__BLACS 
-D__SCALAPACK -D__ELPA3 -I/usr/include/elpa/modules/ -I/usr/include 
-D__COMPILE_ARCH="\"Linux-x86_64-gfortran\"" -D__COMPILE_DATE="\"Wed May  2 
12:06:40 UTC 2018\"" -D__COMPILE_HOST="\"ip-172-31-12-4\"" 
-D__COMPILE_REVISION="\"svn:18091\"" -D__DATA_DIR="\"/usr/share/cp2k\"" 
-D__SHORT_FILE__="\"acc/acc_stream.F\"" -I'/<>/src/acc/' 
acc_stream.F90 
/<>/tools/build_utils/fypp -n /<>/src/acc/acc_event.F 
acc_event.F90
mpif90 -c -g -Wall -O2 -ffast-math -funroll-loops -ftree-vectorize -ffree-form 
-ffree-line-length-none -D__GFORTRAN -D__FFTSG -D__FFTW3  -D__LIBINT 
-D__LIBINT_MAX_AM=6 -D__LIBDERIV_MAX_AM1=5 -D__LIBXC2 -D__parallel -D__BLACS 
-D__SCALAPACK -D__ELPA3 -I/usr/include/elpa/modules/ -I/usr/include 
-D__COMPILE_ARCH="\"Linux-x86_64-gfortran\"" -D__COMPILE_DATE="\"Wed May  2 
12:06:40 UTC 2018\"" -D__COMPILE_HOST="\"ip-172-31-12-4\"" 
-D__COMPILE_REVISION="\"svn:18091\"" -D__DATA_DIR="\"/usr/share/cp2k\"" 
-D__SHORT_FILE__="\"acc/acc_event.F\"" -I'/<>/src/acc/' 
acc_event.F90 
/<>/tools/build_utils/fypp -n 
/<>/src/acc/acc_devmem.F acc_devmem.F90
mpif90 -c -g -Wall -O2 -ffast-math -funroll-loops -ftree-vectorize -ffree-form 
-ffree-line-length-none -D__GFORTRAN -D__FFTSG -D__FFTW3  -D__LIBINT 
-D__LIBINT_MAX_AM=6 -D__LIBDERIV_MAX_AM1=5 -D__LIBXC2 -D__parallel -D__BLACS 
-D__SCALAPACK -D__ELPA3 -I/usr/include/elpa/modules/ -I/usr/include 
-D__COMPILE_ARCH="\"Linux-x86_64-gfortran\"" -D__COMPILE_DATE="\"Wed May  2 
12:06:40 UTC 2018\"" -D__COMPILE_HOST="\"ip-172-31-12-4\"" 
-D__COMPILE_REVISION="\"svn:18091\"" -D__DATA_DIR="\"/usr/share/cp2k\"" 
-D__SHORT_FILE__="\"acc/acc_devmem.F\"" -I'/<>/src/acc/' 
acc_devmem.F90 
/<>/src/acc/acc_devmem.F:353:0:

SUBROUTINE acc_devmem_info(free, avail)
 
Warning: 'acc_devmem_info' defined but not used [-Wunused-function]
/<>/tools/build_utils/fypp -n 
/<>/src/dbcsr/data/dbcsr_data_types.F dbcsr_data_types.F90
mpif90 -c -g -Wall -O2 -ffast-math -funroll-loops -ftree-vectorize -ffree-form 
-ffree-line-length-none -D__GFORTRAN 

Processed: affects 904825

[Debian Bug Tracking System]

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

> affects 904825 src:cp2k
Bug #904825 {Done: Alastair McKinstry } [src:openmpi] 
aces3 ftbfs in unstable
Added indication that 904825 affects src:cp2k
> thanks
Stopping processing here.

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

Bug#888356: retroarch: diff for NMU version 1.3.6+dfsg1-1.1

[Sebastian Ramacher]

On 2018-07-12 09:46:33, Sebastian Ramacher wrote:
> On 2018-07-12 02:24:12, Sérgio Benjamim wrote:
> > Hi,
> > 
> > There's a beta package for 1.7.3... you guys should improve it, instead
> > updating really really old versions ;)
> > https://mentors.debian.net/package/retroarch
> 
> Gianfranco, you are Sérgio's usual sponsor for retroarch. What's the status on
> that?

Gentle ping

Best
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#905130: hedgewars: FTBFS on armhf (tests fails))

[Julian Gilbey]

On Thu, Aug 09, 2018 at 08:59:25PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi Julian!
> 
> On Thu, 9 Aug 2018 at 20:56, Julian Gilbey  wrote:
> >
> > reopen 905130
> > thanks
> >
> > Hi Lisandro,
> >
> > I was going to make a report about hedgewars myself, as it seems that
> > this package is one of the factors blocking the Qt transition (see
> > https://release.debian.org/transitions/html/qtbase-abi-5-11-0.html).
> > And then I saw this bug report which looks like it was mistakenly
> > closed before being fixed.
> >
> > Thank you for taking responsibility for this - I do appreciate it!
> > I'm reopening the bug report in the meantime so that others can also
> > see it is still live.  When you have taken care of it and either fixed
> > the bug or removed hedgewars from armhf, then please feel free to
> > close it again.
> 
> Thanks, but I was not the one who closed it! ;-)

Oh, oops, sorry - it was Gianfranco!

Best wishes,

   Julian

Processed: tagging 899867, tagging 901117

[Debian Bug Tracking System]

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

> tags 899867 + pending
Bug #899867 [src:syslog-ng] syslog-ng: Invalid maintainer address 
syslog-ng-maintain...@lists.alioth.debian.org
Added tag(s) pending.
> tags 901117 + pending
Bug #901117 [src:syslog-ng] syslog-ng: FTBFS when built with dpkg-buildpackage 
-A
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#905409: upgrade of util-linux and login break the xhost command for other users

[Simon McVittie]

On Thu, 09 Aug 2018 at 21:06:37 +0200, Helge Kreutzmann wrote:
> +Further by default 
> +.B su
> +does not allow the commands to access the current X display.

This is perhaps misleading: su isn't allowing or denying anything, it's
the X server that isn't allowing other users to access it. Perhaps just
state the facts and let the user sort out the implications: "Unlike the
su implementation in Debian 9 and older releases, this su implementation
does not copy the X display address (DISPLAY) and credentials (XAUTHORITY)
to the commands"?

There are two situations with different behaviour and expectations:
escalating privileges from a non-root user to root, and changing/dropping
privileges from a user (whether root or not) to a different non-root user.

When escalating from an non-root user to root, the old su in src:shadow
copied the DISPLAY and XAUTHORITY variables to the root process. This
told X clients which X display they could use (DISPLAY), and also the
file containing credentials to use when authenticating to that display
(XAUTHORITY). The file whose name is the value of XAUTHORITY is normally
only readable by the user who owns the X display, but root can read it
anyway, because root is privileged and can exercise CAP_DAC_OVERRIDE. In
this situation, it is also unnecessary to defend against root being
able to escalate privileges to the invoking user (for instance via X
misconfiguration or via bugs like CVE-2016-2779), because root can do
that anyway.

(It hopefully goes without saying that running X applications as root
is not a good idea, both because X applications and the X display trust
each other and because GUI libraries are a huge attack surface.)

When switching from a user (root or not) to a different non-root user,
copying DISPLAY had the same effect as when escalating to root, but
copying XAUTHORITY would leave the target user's process trying to read
a file to which they do not normally have read access, so simply using
su was not sufficient even with the old src:shadow su, and setting
up access for the target user with xhost (or xauth) was additionally
required. In this situation, it normally *is* a concern if the target
user can escalate to the privileges of the invoking user, either via X
misconfiguration or via something like CVE-2016-2779: that would give
the target user abilities that they did not previously have, defeating
the value of using separate users.

> +Use ssh, e.g. "ssh -X -oForwardX11Trusted=no otheruser@localhost".

I don't actually know how much protection against keyloggers, input
injection, output capture etc. you get from ForwardX11Trusted=no;
you'd have to ask an X11 expert. It's also known to break some X apps
(and in particular it forbids use of the selection, i.e. copy/paste),
which is why Debian's ssh has been patched (since 2004, #237021) to
default to ForwardX11Trusted=yes when X-forwarding is used (the
upstream default is that -X implies -oForwardX11Trusted=no, and
-Y is equivalent to -X -oForwardX11Trusted=yes).

> +Allow \fBsu\fR explicit display access by issuing "xhost 
> +si:localuser:otheruser"

This is misleading: the display access granted by xhost is not limited
to the process tree rooted at su, but is granted to any (related or
unrelated) process whose uid is otheruser.

Perhaps "Allow X display access for processes running as \fIotheruser\fR
by issuing \fBxhost +si:localuser:\fIotheruser\fR"?

smcv

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[Chris Lamb]

Source: android-platform-external-boringssl
Version: 8.1.0+r23-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Kai-Chung Yan , 
ftpmas...@debian.org

Hi,

I just ACCEPTed android-platform-external-boringssl from NEW but 
noticed it was missing attribution in debian/copyright for at least 
Sun Microsystems, Nokia, Network Resonance, etc. etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Bug#905338: marked as done (snapper-gui: Namespace GtkSource not available)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 07:04:05 +
with message-id 
and subject line Bug#905338: fixed in snapper-gui 0git.960a94834f-2
has caused the Debian Bug report #905338,
regarding snapper-gui: Namespace GtkSource not available
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.)


-- 
905338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snapper-gui
Version: 0git.960a94834f-1
Severity: grave
Justification: renders package unusable

--8<---cut here---start->8---
$ snapper-gui
Traceback (most recent call last):
  File "/usr/bin/snapper-gui", line 11, in 
load_entry_point('snappergui==0.1', 'gui_scripts', 'snapper-gui')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 476, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2700, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2318, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/snappergui/__init__.py", line 5, in 

gi.require_version("GtkSource", "3.0")
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 130, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GtkSource not available
--8<---cut here---end--->8---

Installing gir1.2-gtksource-3.0 fixes this.

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages snapper-gui depends on:
ii  python3  3.6.6-1

snapper-gui recommends no packages.

snapper-gui suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: snapper-gui
Source-Version: 0git.960a94834f-2

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated snapper-gui 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, 10 Aug 2018 12:28:41 +0545
Source: snapper-gui
Binary: snapper-gui
Architecture: source all
Version: 0git.960a94834f-2
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Description:
 snapper-gui - graphical user interface for snapper
Closes: 905314 905338
Changes:
 snapper-gui (0git.960a94834f-2) unstable; urgency=medium
 .
   * [8ff17da5] Explain the reason for disabling tests.
 Thanks to Chris Lamb (Closes: #905314)
   * [260a61f0] Add dependency on gir1.2-gtksource-3.0.
 Thanks to Mykola Nikishov (Closes: #905338)
   * [c853fad4] Add debian/gbp.conf file
Checksums-Sha1:
 121f26d60439d5a719477a81d3479d5f1602ae05 1993 snapper-gui_0git.960a94834f-2.dsc
 482ea644a149c1d9ca8632c6db625d9f85fa459d 2052 
snapper-gui_0git.960a94834f-2.debian.tar.xz
 38aa31971df256c4bb2185e50d1b12416510c375 16408 
snapper-gui_0git.960a94834f-2_all.deb
 ef380f5c852a3277c5e3906963573dca02f5fa30 6512 
snapper-gui_0git.960a94834f-2_amd64.buildinfo
Checksums-Sha256:
 6201eb0e1a91f339a9de50d32520bcd5ce02f26fff73c73b876d02828a0e6b10 1993 
snapper-gui_0git.960a94834f-2.dsc
 8862b436c247466982a21d2e879cefee4369e026c879e2eec09a74922f0ac88a 2052 
snapper-gui_0git.960a94834f-2.debian.tar.xz
 47a8285629bfdbe0e804fcca6e2b550558bcfe0f82938dabde25ed2314b76e88 16408 
snapper-gui_0git.960a94834f-2_all.deb
 

Bug#902327: marked as done (isort: missing dependency on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 07:03:47 +
with message-id 
and subject line Bug#902327: fixed in isort 4.3.4+ds1-1.1
has caused the Debian Bug report #902327,
regarding isort: missing dependency on python3-pkg-resources
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.)


-- 
902327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: isort
Version: 4.2.5+ds1-2
Severity: serious

sid $ isort
Traceback (most recent call last):
  File "/usr/bin/isort", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

stretch $ isort
Traceback (most recent call last):
  File "/usr/bin/isort", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named 'pkg_resources'


Andreas
--- End Message ---
--- Begin Message ---
Source: isort
Source-Version: 4.3.4+ds1-1.1

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

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

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated isort package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Aug 2018 06:38:25 +
Source: isort
Binary: isort python-isort python3-isort
Architecture: source
Version: 4.3.4+ds1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Niels Thykier 
Description:
 isort  - utility for sorting Python imports
 python-isort - library for sorting Python imports (Python 2)
 python3-isort - library for sorting Python imports (Python 3)
Closes: 902327
Changes:
 isort (4.3.4+ds1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing dependency on python3-pkg-resources.  Thanks to
 Andreas Beckmann for reporting the issue.  (Closes: #902327)
   * Set Rules-Requires-Root to no as isort does not need
 (fake)root for producing the .debs.
   * Clean up .pytest_cache and isort.egg-info via d/clean to
 ensure that the package can build twice in a row.
Checksums-Sha1:
 4470a4847ae1b8bf419154a271be2a56092f5f4a 2243 isort_4.3.4+ds1-1.1.dsc
 7febdfe16172af963249afb28c7be2ff526cbdf5 4688 isort_4.3.4+ds1-1.1.debian.tar.xz
 2b71a89867614c03b06eca543c3bea54a0c2c189 7088 
isort_4.3.4+ds1-1.1_source.buildinfo
Checksums-Sha256:
 195ec3fb30ede8128f7a770cc7f40028a6550de9f77d41bc095d15cf39ac6444 2243 
isort_4.3.4+ds1-1.1.dsc
 ba3f6c18943e97cbd0c52ce322529ef6a52e4a5ec146d4843bf1729ef40010e0 4688 
isort_4.3.4+ds1-1.1.debian.tar.xz
 fd99bede7328d93dcfb2451ce2a2af34816f2a06f1efa28e951616340ad526aa 7088 
isort_4.3.4+ds1-1.1_source.buildinfo
Files:
 bc6c1b6fe119f4425be6c7389503b669 2243 python optional isort_4.3.4+ds1-1.1.dsc
 d45fc212c7b7cf00018520e1015a4592 4688 python optional 
isort_4.3.4+ds1-1.1.debian.tar.xz
 85ecd9d611c6494c88c5beff7fbd9e15 7088 python optional 
isort_4.3.4+ds1-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAltqj/IACgkQBUu7n32A
ZEKngA//WZ2GFWNHA4Ty7S2/S9BJyrRmNMNkCQV0hajQmR+O63U2VX/cmj+fx8tU
WvQ/5znUyQX11fXffFF0rB9b1GfwVWIVlPt63YdbAODiQdZ6ISksFEY5LgpLXWck
Bi0f9A0WXeT6Rk57I0Kn3HzUJ1zlvFPvcACYqSNKQC1eGnPEVvH0Lc0LF5eibs4Y
nCFFTJ2uadgnNq9eFdVZSUbjuNxoLDUznIqul/+KvtZCU1h3U29DI7GPBNhNUYFy
PqSgOZQFM1eLS90cJnk+DJXgwgzXE3j51zPxIacG06TGFYQBtjy56+je8l+SAIDM
p2NS3lX7H3PlBXjiZPiOrWo+WX5HBnpLxI/OUlPRnFMQ8dogIV+ihDriJwLWbhNj
6VqRnOSOUMa6Vd4avIyxqIFwNTEaOS2c7f5jbYbHkd0L6p2uj1XeKPezTtLTBqR+
2sY9TIfMfuzOtxA0QrstCjCIxf2KuoI4scnlJW4/yBVerAEntt6YUOsp1Y6grhGq
mD/ZvjCdL6uIQ6ZBFX68B3R0e2sQ+8YRHF2jlTrNX2DqS+MW8RxWroxaKQoU/3Nj
h8FbVbHbSqB6nBsknkR37MCojnaDSRyF3x9lTBVMBB3Jun+PmlBLQk8aF8URctTK
8+JMhTYPeQfaYPyWzRxwCKx3k8ishFdUqEi3v3fThWxWSlf6by0=
=VX8G
-END PGP SIGNATURE End Message ---

Bug#905229: marked as done (python3-stem: missing Depends: python3-distutils)

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 07:00:12 +
with message-id 
and subject line Bug#905229: fixed in python-stem 1.6.0-4~bpo9+1
has caused the Debian Bug report #905229,
regarding python3-stem: missing Depends: python3-distutils
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.)


-- 
905229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-stem
Version: 1.6.0-3
Severity: serious
Control: affects -1 onionshare

$ onionshare
Traceback (most recent call last):
  File "/usr/bin/onionshare", line 21, in 
import onionshare
  File "/usr/lib/python3/dist-packages/onionshare/__init__.py", line 24, in 

from .onion import *
  File "/usr/lib/python3/dist-packages/onionshare/onion.py", line 21, in 

from stem.control import Controller
  File "/usr/lib/python3/dist-packages/stem/control.py", line 265, in 
import stem.descriptor.microdescriptor
  File "/usr/lib/python3/dist-packages/stem/descriptor/__init__.py", line 55, 
in 
import stem.util.system
  File "/usr/lib/python3/dist-packages/stem/util/system.py", line 70, in 

import distutils.spawn
ModuleNotFoundError: No module named 'distutils.spawn'


Andreas
--- End Message ---
--- Begin Message ---
Source: python-stem
Source-Version: 1.6.0-4~bpo9+1

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

Debian distribution maintenance software
pp.
Ulises Vitulli  (supplier of updated python-stem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Aug 2018 21:07:44 -0300
Source: python-stem
Binary: python-stem python3-stem pypy-stem
Architecture: source all
Version: 1.6.0-4~bpo9+1
Distribution: stretch
Urgency: high
Maintainer: Ulises Vitulli 
Changed-By: Ulises Vitulli 
Description:
 pypy-stem  - Tor control library for PyPy
 python-stem - Tor control library for Python
 python3-stem - Tor control library for Python 3 series
Closes: 880960 903860 904454 904582 905229
Changes:
 python-stem (1.6.0-4~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
 .
 python-stem (1.6.0-4) unstable; urgency=medium
 .
   * Fix missing Depends: on python3-distutils for py3 pkg. Thanks anbe@!
 (Closes: #905229).
   * ACKed NMU from irl@.
   * Updated Standard-version to 4.2.0.0 (no changes needed).
   * Fix duplicated long pkg description.
   * Enhance local patch description.
   * Added watch file.
   * Added gpg upstream verification.
 .
 python-stem (1.6.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fixes for PyPy compatibility issues (Closes: #904582).
 .
 python-stem (1.6.0-3) unstable; urgency=medium
 .
   * Prepare package for pypy. Thanks IainRLearmonth! (Closes: #904454).
   * Install some stem usage examples.
   * Update Vcs-* control fields for move to salsa.debian.org.
   * Updated Standard-version to 4.1.5.0 (no changes needed).
   * Updated debhelper compat to 11.
   * Cosmetic update copyrights file.
 .
 python-stem (1.6.0-2) unstable; urgency=high
 .
   * Patch for py3.7 compat issues on reserved words (Closes: #903860).
 .
 python-stem (1.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix versioned py3.x dependency, thanks MatthiasKlose! (Closes: #880960).
   * Updated Standard-version to 4.1.1.1 (no changes needed).
   * Updated upstream changelog note on large file.
   * Update Vcs-Browser field to https one.
Checksums-Sha1:
 84f8833e65e92344667de5c784f563941c2acf20 2060 python-stem_1.6.0-4~bpo9+1.dsc
 a58af5f3a7b46bd97b834cfcc80cff320e43448a 9340 
python-stem_1.6.0-4~bpo9+1.debian.tar.xz
 46e8ec288687c9c57ef982d87b237ad79a952abe 260090 
pypy-stem_1.6.0-4~bpo9+1_all.deb
 41bd59e539df1c60ccbf03f3c2e2e7149dd0c850 260120 
python-stem_1.6.0-4~bpo9+1_all.deb
 5544aab98f509c7710a48937b1fc8cc9ed872ce6 7218 
python-stem_1.6.0-4~bpo9+1_amd64.buildinfo
 499941d4bab47b1a67c332f1302cd8a0e42a1cb7 260314 
python3-stem_1.6.0-4~bpo9+1_all.deb
Checksums-Sha256:
 

Bug#903860: marked as done (python3-stem: File "/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / self.method.async = self

[Debian Bug Tracking System]

Your message dated Fri, 10 Aug 2018 07:00:12 +
with message-id 
and subject line Bug#903860: fixed in python-stem 1.6.0-4~bpo9+1
has caused the Debian Bug report #903860,
regarding python3-stem: File 
"/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / 
self.method.async = self
/  ^
   /SyntaxError: invalid syntax
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.)


-- 
903860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-stem
Version: 1.6.0-1
Severity: serious
Tags: a11y
Justification: fails to build from source

Dear Maintainer,



   * What led up to the situation?
Package was pulled in as a dependency for nyx which is a dependency for tor-arm 
and onionshare
   * What exactly did you do (or not do) that was effective (or
 ineffective)?  Have tried purging and building from source.  Have dpkg 
--purge to reinstall the package but was also not effective. 
   * What was the outcome of this action?
Package still will not install
   * What outcome did you expect instead?
Hoping a rebuild would have helped



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

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 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: systemd (via /run/systemd/system)

Versions of packages python3-stem depends on:
ii  python3  3.6.6-1

python3-stem recommends no packages.

python3-stem suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-stem
Source-Version: 1.6.0-4~bpo9+1

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

Debian distribution maintenance software
pp.
Ulises Vitulli  (supplier of updated python-stem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Aug 2018 21:07:44 -0300
Source: python-stem
Binary: python-stem python3-stem pypy-stem
Architecture: source all
Version: 1.6.0-4~bpo9+1
Distribution: stretch
Urgency: high
Maintainer: Ulises Vitulli 
Changed-By: Ulises Vitulli 
Description:
 pypy-stem  - Tor control library for PyPy
 python-stem - Tor control library for Python
 python3-stem - Tor control library for Python 3 series
Closes: 880960 903860 904454 904582 905229
Changes:
 python-stem (1.6.0-4~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
 .
 python-stem (1.6.0-4) unstable; urgency=medium
 .
   * Fix missing Depends: on python3-distutils for py3 pkg. Thanks anbe@!
 (Closes: #905229).
   * ACKed NMU from irl@.
   * Updated Standard-version to 4.2.0.0 (no changes needed).
   * Fix duplicated long pkg description.
   * Enhance local patch description.
   * Added watch file.
   * Added gpg upstream verification.
 .
 python-stem (1.6.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fixes for PyPy compatibility issues (Closes: #904582).
 .
 python-stem (1.6.0-3) unstable; urgency=medium
 .
   * Prepare package for pypy. Thanks IainRLearmonth! (Closes: #904454).
   * Install some stem usage examples.
   * Update Vcs-* control fields for move to salsa.debian.org.
   * Updated Standard-version to 4.1.5.0 (no changes needed).
   * Updated debhelper compat to 11.
   * Cosmetic update copyrights file.
 .
 python-stem (1.6.0-2) unstable; urgency=high
 .
   * Patch for py3.7 compat issues on reserved words (Closes: #903860).
 .
 python-stem (1.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix versioned py3.x dependency, thanks MatthiasKlose! (Closes: #880960).
   * Updated Standard-version to 4.1.1.1 (no changes needed).
   * Updated upstream changelog note on large file.
   * Update Vcs-Browser field to https one.
Checksums-Sha1:
 

Bug#905818: dbusada: Incomplete debian/copyright?

[Chris Lamb]

Source: dbusada
Version: 0.4.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Reto Buerki , ftpmas...@debian.org

Hi,

I just ACCEPTed dbusada from NEW but noticed it was missing 
attribution in debian/copyright for at least Tero Koskinen?

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload. :)


Regards,

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

Bug#905767: emacs25: FTBFS due to test failures on arm64 in a binNMU against new version of libmagick

[Byung-Hee HWANG (황병희, 黃炳熙)]

Rob Browning  writes:

> Niels Thykier  writes:
>
>> Package: emacs25
>> Version: 25.2+1-6+b3
>> Severity: serious
>> Tags: ftbfs
>> Justification: fails to build from source
>
> This should be fixed in emacs 1:25.2+1-9, which hopefully will be able
> to completely replace emacs25 in sid/buster soon.

I'm happy to hear this news, because i'm using ARM64 chromebook;;;

-- 
^고맙습니다 _地平天成_ 감사합니다_^))//

Bug#905816: xul-ext-form-history-control: rename to webext-form-history-control, set correct dependencies

[Paul Wise]

Package: xul-ext-form-history-control
Version: 2.0.3.2+dfsg-1
Severity: serious

Since the package no longer works with Firefox ESR 52 from Debian
unstable and earlier, please rename it to webext-form-history-control and set 
the dependencies to prevent installing it with Firefox ESR 52.
Right now it doesn't work with firefox-esr from Debian unstable.

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages xul-ext-form-history-control depends on:
ii  libjs-jquery 3.2.1-1
ii  libjs-jquery-datatables  1.10.19+dfsg-1

xul-ext-form-history-control recommends no packages.

xul-ext-form-history-control suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#905815: ckermit fails to trap errors from make

[Helmut Grohne]

Source: ckermit
Version: 302-5.3
Severity: serious
Justification: policy section 4.6
Tags: upstream

ckermit does not trap errors from make. Failing to do so is prohibited
by the Debian policy section 4.6, because it can cause silent misbuilds
and makes debugging failures unnecessarily hard.

The cause is spread around the upstream makefile. For instance in the
linux+krb5+openssl target used by debian rules, the final "$(MAKE) linux
..." invocation is chained with ";". It then proceeds to checking for
missing files, but ultimately, the return code of the shell snipped is
always successful. A typical fix is putting "set -e; \" at the beginning
of such command chains. Though it needs to be fixed in a lot of places
here.

Helmut

Bug#891063:

[Rob Browning]

Vincent Lefevre  writes:

> "su -l" is not a solution as it reset the current working directory.
> And one should still be able to run X applications after su.

Hmm, is that true?  I don't actually know, but the suggestion I'd often
heard is to generally avoid running X applications much as root, but if
I were going to, I'd use "su -", which (now that I look) does appear to
handle at least XAUTHORITY -- though I'd still be wary.

That said, I have noticed that for the past "few" years, if I run emacs
in a terminal where I've become root via "su -" and I forget to specify
-nw, it does pop up the X frame.  Surprised me the first time.

> But in any case, emacs shouldn't create files/directories if the
> user hasn't explicitly asked it to do that.

I'd expect emacs to create various files via gtk, dbus, and other
subsystems it uses, and it's certainly going to create bits like
~/.emacs and ~/.emacs.d if it needs to (for M-x customize, etc.).

Whether or not it's doing it correctly is another question, but I'm not
at all surprised that plain "su" with an X-based emacs frame (i.e. not
"emacs -nw") has trouble.

If you want to pursue this, I suspect you should pursue it upstream, or
I'll plan to forward it later if you prefer.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Processed: found 905767 in 25.2+1-6

[Debian Bug Tracking System]

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

> found 905767 25.2+1-6
Bug #905767 [src:emacs25] emacs25: FTBFS due to test failures on arm64 in a 
binNMU against new version of libmagick
Marked as found in versions emacs25/25.2+1-6.
> thanks
Stopping processing here.

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