Bug#889804: flashplugin-nonfree: Does not work anymore because adobe site have moved to https and script does not hanlde redirect

[Eric Valette]

Package: flashplugin-nonfree
Version: 1:3.7
Severity: grave
Justification: renders package unusable

update-flashplugin-nonfree --status
Flash Player version installed on this system  : 28.0.0.161
link to Adobe Flash Player not found on http://www.adobe.com/ at 
get-upstream-version.pl line 58.
ERROR: failed to get upstream version
More information might be available at:
  http://wiki.debian.org/FlashPlayer


-- Package-specific info:
Debian version: buster/sid
Architecture: amd64
Package version: 1:3.7
Adobe Flash Player version: [@LNX 28,0,0,161
MD5 checksums:
99bbfc9d1c2977c7d8f86f4d3fc830a4  
/var/cache/flashplugin-nonfree/adobewebpage.html
f953c34ab0b018d448221c3f5fa9bbd5  
/usr/lib/flashplugin-nonfree/libflashplayer.so
Alternatives:
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
lrwxrwxrwx 1 root root 34 Aug 21  2016 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.30-2
ii  ca-certificates20170717
ii  debconf [debconf-2.0]  1.5.65
ii  gnupg  2.2.4-2
ii  gnupg2 2.2.4-2
ii  libatk1.0-02.26.1-3
ii  libcairo2  1.15.10-1
ii  libcurl3-gnutls7.58.0-2
ii  libfontconfig1 2.12.6-0.1
ii  libfreetype6   2.8.1-1
ii  libgcc11:7.3.0-1
ii  libglib2.0-0   2.55.1-1
ii  libgtk2.0-02.24.32-1
ii  libnspr4   2:4.18-1
ii  libnss32:3.35-2
ii  libpango1.0-0  1.40.14-1
ii  libstdc++6 7.3.0-1
ii  libx11-6   2:1.6.4-3
ii  libxext6   2:1.3.3-1+b2
ii  libxt6 1:1.1.5-1
ii  wget   1.19.4-1

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  firefox-esr52.6.0esr-2
ii  fonts-dejavu   2.37-1
pn  hal-flash  
pn  iceweasel  
ii  konqueror-nsplugins4:16.08.3-1
pn  ttf-mscorefonts-installer  
ii  ttf-xfree86-nonfree4.2.1-5

-- no debconf information

Bug#889740: Info received (Bug#889740: thunderbird: Faulty apparmor configuration)

[Marcin Owsiany]

FTR https://qa.debian.org/bls/packages/x/xmotd.html summarizes them nicely.

Bug#889740: thunderbird: Faulty apparmor configuration

[Marcin Owsiany]

The issue is caused by lack of getTimeStampName declaration in xmotd.c. The
implicit declaration assumed instead causes the pointer to buf to be cast
to an int, in turn causing some truncation of bits which are non-zero in
this case of a static buffer placed in a far location in address space
(probably in some special section when hardening is used). utime() detects
this and returns EFAULT.

The build log shows plenty of warnings, some of which might have a similar
effect.

Processed: Re: Bug#889740: thunderbird: Faulty apparmor configuration

[Debian Bug Tracking System]

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

> retitle 889740 crashes when built with hardening
Bug #889740 [xmotd] thunderbird: Faulty apparmor configuration
Changed Bug title to 'crashes when built with hardening' from 'thunderbird: 
Faulty apparmor configuration'.
> severity 889740 serious
Bug #889740 [xmotd] crashes when built with hardening
Severity set to 'serious' from 'normal'
> Thanks
Stopping processing here.

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

Bug#879789: intercal still can't link in stretch

[Quantum]

Dear Maintainer,

I installed intercal from the stretch repository last night and noticed
that it still can't compile anything. I manually pulled in the buster
package and it works. Can the latest version be backported to stretch?

Regards,

Quantum

Bug#883352: php-doctrine-cache-bundle FTBFS: test failures

[Nish Aravamudan]

This is related to Symfony internal changes.

https://github.com/doctrine/DoctrineCacheBundle/issues/101

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#877130: highwayhash: FTBFS with GCC 7: symbols files need to be updated

[Lumin]

On 7 February 2018 at 00:27, Andreas Beckmann  wrote:
> The new upstream snapshot probably cuased further symbol changes:

Indeed and thanks. I was just waiting for an upstream build fix for ppc64el.



-- 
Best,

Bug#886944: python3-regex: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Nicholas D Steeves]

Hi Sandro,

Would you like a patch for current_version-new_revision or for
new_upstream_version-1?  I assumed the latter, and send two patches
also assuming that you'd squash them.  Of course I'd be happy to
squash them myself and rewrite the messages.  Whatever you prefer :-)

Hi Andreas,

On Wed, Feb 07, 2018 at 12:50:05AM +0100, Andreas Beckmann wrote:
> On 2018-02-06 23:01, Nicholas D Steeves wrote:
> > On Tue, Feb 06, 2018 at 04:02:07PM -0500, Sandro Tosi wrote:
> >>patch is welcome, NMU is not; feel free to upload the patch to this bug
> >>and i'll take care of the upload. thanks for working on this Debian bug
> > 
> > That's fair.  The main thing I'd like to avoid is the autoremoval of
> > rdepending packages ;-)
> 
> You already reset the timer by keeping the discussion in this bug alive ;-)

That's a relief!

> > I pushed to the following remote and have also
> > attached the patches (see commit messages for more info):
> > https://salsa.debian.org/sten-guest/python-regex.git
> 
> Assuming the next upload will be versioned 0.1.20171212-2, the version
> in the .maintscript files needs to be 0.1.20171212-2~, i.e. you want
> ""+"~".
> That version will also be OK if a new upstream release comes with the
> fix, but not for a NMU (that would be versioned 0.1.20171212-1.1 and you
> would need to use 0.1.20171212-1.1~ in that case).

Touché.  I originally tested new upstream version, then reworked it
for a minimal NMU, then reworked the commits into what I hoped would
potentially be useful to someone who happened to wonder how to fix a
similar bug.

> You should squash the two patches, the separation just causes
> confusion.

I'll do this (if necessary) as soon as I hear back from Sandro about
his preference.  Ah, yes, and now I see how it would have been best to use
0.1.20171212-2~ in the first patch.

> There is no need to bump the version in the .maintscript files for
> further uploads to buster (unless you need more bugfixes to the d-m-h
> calls) (or unless you are uploading new upstream releases to stretch).
> There are only two cases while upgrading: upgrading from a version
> without the fix (e.g. stretch or 0.1.20171212-1) or a version with the
> fix (in that case the migration can be skipped)

Thank you for clearing this up, I might be inductively challenged
haha!  Might you be willing to add something to this effect to
dpkg-maintscript-helper(1)?

> regarding the commit message:
> 
> >Maintscripts had:
> > symlink_to_dir pathname new-target
> 
> There is no such thing as a "new-target" for symlink_to_dir.
> I think the maintscripts had "symlink_to_dir pathname current-package".

Yes d-m-h(1) has
symlink_to_dir /path/name old-target [prior-version [package]]

It took longer than I'd like to admit to realise that symlink_to_dir
functions like this.  eg, for /path/name

cd /path
ln -s name symlink-name (aka: new-target)

corresponds to

dir_to_symlink /path/name symlink-name

which is reversed with

symlink_to_dir /path/name symlink-name (aka: old-target)
  |
where this is not the new_dir_name  <-|

For some reason I kept seeing

symlink_to_dir /existing/symlink-name new_dir_name

> PS: I would likely have sponsored a delayed NMU, after several rounds of
> revision  ;-)

Thank you for your support :-) On the topic of rounds of revision,
because a package-dbg depends on package ${binary:Version}, should all
package-dbgs do this:

dir_to_symlink /path/package-dbg package ?

similarly to how automatic -dbgsym packages are handled?  If so, I
think my patch can be improved by adding this operation to each of the
-dbg.maintscripts.


Regards,
Nicholas


signature.asc
Description: PGP signature

Processed: Re: highwayhash: FTBFS with GCC 7: symbols files need to be updated

[Debian Bug Tracking System]

Processing control commands:

> found -1 0~20180103-geeea446-1
Bug #877130 {Done: Mo Zhou } [src:highwayhash] 
highwayhash: FTBFS with GCC 7: symbols files need to be updated
Marked as found in versions highwayhash/0~20180103-geeea446-1; no longer marked 
as fixed in versions highwayhash/0~20180103-geeea446-1 and reopened.

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

Bug#877130: highwayhash: FTBFS with GCC 7: symbols files need to be updated

[Andreas Beckmann]

Followup-For: Bug #877130
Control: found -1 0~20180103-geeea446-1

The new upstream snapshot probably cuased further symbol changes:

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



Andreas

Processed: lyx: python errors while building ngspice

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ngspice
Bug #889793 [lyx] lyx: python errors while building ngspice
Added indication that 889793 affects src:ngspice

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

Bug#889793: lyx: python errors while building ngspice

[Andreas Beckmann]

Package: lyx
Version: 2.2.3-4
Severity: serious
Control: affects -1 src:ngspice

Hi,

while rebuilding non-free I noticed that ngspice started to FTBFS with
som lyx python errors in the logfile:

[...]
+Indexing TeX files... 
  File "/usr/share/lyx/scripts/TeXFiles.py", line 112
print(root.replace('\\', '/') + '/' + file, file=out)
^
SyntaxError: invalid syntax

done
+checking list of modules...
[...]
LyX: Done!
Warning: An error ocurred in 490, 
Traceback (most recent call last):
  File "/usr/share/lyx/lyx2lyx/lyx2lyx", line 88, in 
main()
  File "/usr/share/lyx/lyx2lyx/lyx2lyx", line 82, in main
doc.convert()
  File "/usr/share/lyx/lyx2lyx/LyX.py", line 586, in convert
conv(self)
  File "/usr/share/lyx/lyx2lyx/lyx_2_2.py", line 1177, in convert_origin
origin = str(origin, sys.getfilesystemencoding())
TypeError: str() takes at most 1 argument (2 given)
Error: Conversion script failed

/build/ngspice-27/build/manual/manual.lyx is from an older version of LyX and 
the lyx2lyx script failed to convert it.
LyX failed to load the following file: /build/ngspice-27/build/manual/manual.lyx
debian/rules:83: recipe for target 'build-indep' failed
make: [build-indep] Error 1 (ignored)
cd build/manual && lyx -userdir ./.lyx -batch --export pdf2 manual.lyx 
Warning: An error ocurred in 490, 
Traceback (most recent call last):
  File "/usr/share/lyx/lyx2lyx/lyx2lyx", line 88, in 
main()
  File "/usr/share/lyx/lyx2lyx/lyx2lyx", line 82, in main
doc.convert()
  File "/usr/share/lyx/lyx2lyx/LyX.py", line 586, in convert
conv(self)
  File "/usr/share/lyx/lyx2lyx/lyx_2_2.py", line 1177, in convert_origin
origin = str(origin, sys.getfilesystemencoding())
TypeError: str() takes at most 1 argument (2 given)
Error: Conversion script failed

/build/ngspice-27/build/manual/manual.lyx is from an older version of LyX and 
the lyx2lyx script failed to convert it.
LyX failed to load the following file: /build/ngspice-27/build/manual/manual.lyx
debian/rules:83: recipe for target 'build-indep' failed
make: [build-indep] Error 1 (ignored)
[...]
cp -a /build/ngspice-27/build/manual/*.png \
/build/ngspice-27/debian/tmp/usr/share/doc/ngspice-doc/html
cp: cannot stat '/build/ngspice-27/build/manual/*.png': No such file or 
directory
debian/rules:125: recipe for target 'install-indep' failed
make: *** [install-indep] Error 1
[...]

If that is actually an error in ngspice, feel free to reassign
the bug there.


Andreas


ngspice_27-1.log.gz
Description: application/gzip

Bug#888654: mpv: CVE-2018-6360

[James Cowgill]

Hi,

On 06/02/18 18:08, Luciano Bello wrote:
> On 2018-02-03 09:13, James Cowgill wrote:
>> Unlike the backport for 0.27 which was fairly straightforward, the
>> backport for 0.23 required significant changes and I ended up rewriting
>> half of it. This means I am less confident about catching all the cases
>> to fix this bug. It would be good if anyone could check it over.
> 
> I tested the PoC (probably as you) and seems fixed. I tried to cover
> under branches and they also look sanitized. I feel as confident as
> somebody can be that the patch is complete. It seems functionally safe.
> 
> Thanks for your work, please upload.

Thanks for testing! I've uploaded it.

James



signature.asc
Description: OpenPGP digital signature

Bug#886944: python3-regex: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

On 2018-02-06 23:01, Nicholas D Steeves wrote:
> On Tue, Feb 06, 2018 at 04:02:07PM -0500, Sandro Tosi wrote:
>>patch is welcome, NMU is not; feel free to upload the patch to this bug
>>and i'll take care of the upload. thanks for working on this Debian bug
> 
> That's fair.  The main thing I'd like to avoid is the autoremoval of
> rdepending packages ;-)

You already reset the timer by keeping the discussion in this bug alive ;-)

> I pushed to the following remote and have also
> attached the patches (see commit messages for more info):
> https://salsa.debian.org/sten-guest/python-regex.git

Assuming the next upload will be versioned 0.1.20171212-2, the version
in the .maintscript files needs to be 0.1.20171212-2~, i.e. you want
""+"~".
That version will also be OK if a new upstream release comes with the
fix, but not for a NMU (that would be versioned 0.1.20171212-1.1 and you
would need to use 0.1.20171212-1.1~ in that case).

There is no need to bump the version in the .maintscript files for
further uploads to buster (unless you need more bugfixes to the d-m-h
calls) (or unless you are uploading new upstream releases to stretch).
There are only two cases while upgrading: upgrading from a version
without the fix (e.g. stretch or 0.1.20171212-1) or a version with the
fix (in that case the migration can be skipped)

You should squash the two patches, the separation just causes confusion.

regarding the commit message:

>Maintscripts had:
> symlink_to_dir pathname new-target

There is no such thing as a "new-target" for symlink_to_dir.
I think the maintscripts had "symlink_to_dir pathname current-package".


Andreas

PS: I would likely have sponsored a delayed NMU, after several rounds of
revision  ;-)

Processed: tagging 888129

[Debian Bug Tracking System]

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

> tags 888129 + upstream fixed-upstream
Bug #888129 [src:ruby-json-spec] ruby-json-spec: FTBFS on ruby2.5: 
Fixnum/Integer
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 888129 is forwarded to https://github.com/collectiveidea/json_spec/pull/99

[Debian Bug Tracking System]

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

> forwarded 888129 https://github.com/collectiveidea/json_spec/pull/99
Bug #888129 [src:ruby-json-spec] ruby-json-spec: FTBFS on ruby2.5: 
Fixnum/Integer
Set Bug forwarded-to-address to 
'https://github.com/collectiveidea/json_spec/pull/99'.
> thanks
Stopping processing here.

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

Bug#889510: marked as done (ruby-rspec: FTBFS with ruby2.5)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 23:05:49 +
with message-id 
and subject line Bug#889510: fixed in ruby-rspec 3.7.0c1e0m0s1-1
has caused the Debian Bug report #889510,
regarding ruby-rspec: FTBFS with ruby2.5
to be marked as done.

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

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


-- 
889510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec
Version: 3.5.0c3e0m0s0-1
Severity: serious
Tags: sid buster experimental
Justification: fails to build from source
Control: found -1 3.6.0c0e0m0s0-1~exp1
Control: block 888531 with -1

Hi,

ruby-rspec in both sid and experimental FTBFS due to test failures
with ruby2.5 as the default.

Please see attached sid buildlog for the details of the failures, it's
hard for me to provide a batter excerpt than

  ERROR: Test "ruby2.5" failed. Exiting.


Andreas


ruby-rspec.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-rspec
Source-Version: 3.7.0c1e0m0s1-1

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-rspec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Feb 2018 21:24:13 +0100
Source: ruby-rspec
Binary: ruby-rspec ruby-rspec-core ruby-rspec-expectations ruby-rspec-mocks 
ruby-rspec-support
Architecture: source
Version: 3.7.0c1e0m0s1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-rspec - Behaviour Driven Development framework for Ruby - metapackage
 ruby-rspec-core - Behaviour Driven Development framework for Ruby - core
 ruby-rspec-expectations - Behaviour Driven Development framework for Ruby - 
expectations
 ruby-rspec-mocks - Behaviour Driven Development framework for Ruby - mocks
 ruby-rspec-support - Behaviour Driven Development framework for Ruby - support
Closes: 889510
Changes:
 ruby-rspec (3.7.0c1e0m0s1-1) unstable; urgency=medium
 .
   * New upstream version 3.7.0c1e0m0s1
   * Refresh patches and gemspecs
   * Remove disable_coderay_highlight_specs.patch (patched file removed
 upstream)
   * Add upstream patches to fix tests with ruby2.5 (Closes: #889510)
   * Bump Standards-Version to 4.1.3 (no changes needed)
   * Delete leftover gemspec files in debian/ interfering with upstream ones
   * Use DEB_VERSION_UPSTREAM in debian/rules instead of parsing the changelog
Checksums-Sha1:
 e48e378c159b98b7d887fdc0cde1701c7d37f3ed 2136 ruby-rspec_3.7.0c1e0m0s1-1.dsc
 a5415749ac11a4f90d80e1c762210ba8857e 822989 
ruby-rspec_3.7.0c1e0m0s1.orig.tar.gz
 f593c9b5bb3d4608fd238300487ab8e55168c016 19656 
ruby-rspec_3.7.0c1e0m0s1-1.debian.tar.xz
 c2ab8b48be53d0ea84d953e7890e29f74f6ef1dc 7861 
ruby-rspec_3.7.0c1e0m0s1-1_source.buildinfo
Checksums-Sha256:
 85e41147a726cad94cd43109810f280d857edded7ea2ac50c115b354afc8bb44 2136 
ruby-rspec_3.7.0c1e0m0s1-1.dsc
 cadeae3034ebcc016aaad7abce07343c7651baace2fba7c575850417cac56c43 822989 
ruby-rspec_3.7.0c1e0m0s1.orig.tar.gz
 90e3c306a25c8df3631241b26f0d16fd2c4b58de0a4595c5b4ac9baae9aa50d2 19656 
ruby-rspec_3.7.0c1e0m0s1-1.debian.tar.xz
 ad2c91d74379af2272fa920b15eab55921460a20faf16d67a2b6d50679fbdea6 7861 
ruby-rspec_3.7.0c1e0m0s1-1_source.buildinfo
Files:
 8a2db95b13510c4bb37c21540a8eddaf 2136 ruby optional 
ruby-rspec_3.7.0c1e0m0s1-1.dsc
 7938838488a7da82d00b599a48869934 822989 ruby optional 
ruby-rspec_3.7.0c1e0m0s1.orig.tar.gz
 069676d5212eb3edaf5c5a7679e13fe3 19656 ruby optional 
ruby-rspec_3.7.0c1e0m0s1-1.debian.tar.xz
 c7b25aabb9be376394ca9de9e900259f 7861 ruby optional 
ruby-rspec_3.7.0c1e0m0s1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlp6L7cACgkQia+CtznN
IXrpQQf/ViZFAcJw9Wt++sFBVwC+4WT08W+beFZlpTe+BjI+REIr3w4DDF2GCxFf

Processed: Bug #889510 in ruby-rspec marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889510 [src:ruby-rspec] ruby-rspec: FTBFS with ruby2.5
Ignoring request to alter tags of bug #889510 to the same tags previously set

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

Bug#889510: Bug #889510 in ruby-rspec marked as pending

[boutil]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-rspec/commit/458198a3bbb6f4c8ffc2c89169e5232201ee9754


Add upstream patches to fix tests with ruby2.5 (Closes: #889510)



(this message was generated automatically)
-- 
Greetings

Bug#809964: all my passwords are gone

[Martin Steigerwald]

severity 809964 normal
kthxbye

Dear Tomas,

Tomas Pospisek - 06.02.18, 21:38:
> originally I've posted this as a follow up to
> #863844, however #809964 seems to be the more appropriate place.

please refrain from raising the severity of unrelated bugs to critical.

It won´t help you towards a solution. Please read my comment to

kwalletmanager: Migration does not work and restarts at every login
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863844#15

And ask in debian-kde mailing list for help on how to complete the migration.

It is not beneficial to discuss this in the bug tracker, so please use user 
support mailing list for finding help with this upstream issue.

The aim of the Qt/KDE team is to remove Qt4 for next Debian release. So there 
are no plans on making kwalletmanager from KDE SC 4 and kwalletmanager5 from 
Plasma 5 co-installable.

Thanks,
-- 
Martin

Processed: Re: Bug#809964: all my passwords are gone

[Debian Bug Tracking System]

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

> severity 809964 normal
Bug #809964 [kwalletmanager] [kwalletmanager] Manager from kde 4 and 5 should 
be co-installable
Severity set to 'normal' from 'critical'
> kthxbye
Stopping processing here.

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

Processed: Re: Bug#886944: python3-regex: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #886944 [python3-regex] python3-regex: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
Added tag(s) patch.

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

Bug#886944: python3-regex: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Nicholas D Steeves]

Control: tags -1 patch

Hi Sandro,

On Tue, Feb 06, 2018 at 04:02:07PM -0500, Sandro Tosi wrote:
>patch is welcome, NMU is not; feel free to upload the patch to this bug
>and i'll take care of the upload. thanks for working on this Debian bug

That's fair.  The main thing I'd like to avoid is the autoremoval of
rdepending packages ;-) I pushed to the following remote and have also
attached the patches (see commit messages for more info):
https://salsa.debian.org/sten-guest/python-regex.git

Cheers,
Nicholas

>On Tue, Feb 6, 2018 at 3:54 PM, Nicholas D Steeves 
>wrote:
> 
>  Hi Andreas,
>  On Mon, Feb 05, 2018 at 06:32:35PM -0500, Nicholas D Steeves wrote:
>  > Hi Andreas and Sandro,
>  >
>  > On Thu, Jan 11, 2018 at 05:04:13PM +0100, Andreas Beckmann wrote:
>  > > Followup-For: Bug #886944
>  > > Control: affects -1 + python-regex-dbg
>  > >
>  > > Hi,
>  > >
>  > > similar issue in python-regex-dbg:
>  > >
>  > > 0m33.5s ERROR: FAIL: silently overwrites files via directory
>  symlinks:
>  > >   /usr/share/doc/python-regex-dbg/Features.html (python-regex-dbg)
>  != /usr/share/doc/python-regex/Features.html (python-regex)
>  > >     /usr/share/doc/python-regex-dbg -> python-regex
>  > >   /usr/share/doc/python-regex-dbg/Features.rst.gz
>  (python-regex-dbg) != /usr/share/doc/python-regex/Features.rst.gz
>  (python-regex)
>  > >     /usr/share/doc/python-regex-dbg -> python-regex
>  > >   /usr/share/doc/python-regex-dbg/README (python-regex-dbg) !=
>  /usr/share/doc/python-regex/README (python-regex)
>  > >     /usr/share/doc/python-regex-dbg -> python-regex
>  > >   /usr/share/doc/python-regex-dbg/UnicodeProperties.txt.gz
>  (python-regex-dbg) !=
>  /usr/share/doc/python-regex/UnicodeProperties.txt.gz (python-regex)
>  > >     /usr/share/doc/python-regex-dbg -> python-regex
>  > >   /usr/share/doc/python-regex-dbg/changelog.Debian.gz
>  (python-regex-dbg) != /usr/share/doc/python-regex/changelog.Debian.gz
>  (python-regex)
>  > >     /usr/share/doc/python-regex-dbg -> python-regex
>  > >   /usr/share/doc/python-regex-dbg/copyright (python-regex-dbg) !=
>  /usr/share/doc/python-regex/copyright (python-regex)
>  > >     /usr/share/doc/python-regex-dbg -> python-regex
>  > >
>  > > and probably python3-regex-dbg as well, although that does not get
>  > > tested by piuparts as long as python3-regex fails.
>  > >
>  > >
>  > > Andreas
>  >
>  > I'll attempt to fix this evening, because if calibre is removed from
>  > testing than my planned backport will be in jeopardy.  If I succeed
>  > I'll prepare an NMU, but in any case I'll reply to this bug with my
>  > results.
>  >
>  > Cheers,
>  > Nicholas
> 
>  Solved it!  I'll prepare a minimal NMU later today.  Would you please
>  consider sponsoring the upload (I'll CC you for the RFS)?
> 
>  Regards,
>  Nicholas
> 
>--
>Sandro "morph" Tosi
>My website: http://sandrotosi.me/
>Me at Debian: http://wiki.debian.org/SandroTosi
>G+: https://plus.google.com/u/0/+SandroTosi
From d7bcc37b3f9361413495e181159b4d9db317d524 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Tue, 6 Feb 2018 15:43:34 -0500
Subject: [PATCH 1/2] Correct errors in maintscripts. (Closes: #886944)

From dpkg-maintscript-helper(1):
 symlink_to_dir pathname old-target

Maintscripts had:
 symlink_to_dir pathname new-target
---
 debian/python-regex-dbg.maintscript  | 2 +-
 debian/python3-regex-dbg.maintscript | 2 +-
 debian/python3-regex.maintscript | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/python-regex-dbg.maintscript b/debian/python-regex-dbg.maintscript
index 06d5276..f3c7bd1 100644
--- a/debian/python-regex-dbg.maintscript
+++ b/debian/python-regex-dbg.maintscript
@@ -1 +1 @@
-symlink_to_dir /usr/share/doc/python-regex-dbg python-regex-dbg 0.1.20171212-1
+symlink_to_dir /usr/share/doc/python-regex-dbg python-regex 0.1.20171212-1~
diff --git a/debian/python3-regex-dbg.maintscript b/debian/python3-regex-dbg.maintscript
index cb7b44f..62674c9 100644
--- a/debian/python3-regex-dbg.maintscript
+++ b/debian/python3-regex-dbg.maintscript
@@ -1 +1 @@
-symlink_to_dir /usr/share/doc/python3-regex-dbg python3-regex-dbg 0.1.20171212-1
+symlink_to_dir /usr/share/doc/python3-regex-dbg python-regex 0.1.20171212-1~
diff --git a/debian/python3-regex.maintscript b/debian/python3-regex.maintscript
index 899180d..c476fdd 100644
--- a/debian/python3-regex.maintscript
+++ b/debian/python3-regex.maintscript
@@ -1 +1 @@
-symlink_to_dir /usr/share/doc/python3-regex python3-regex 0.1.20171212-1
+symlink_to_dir /usr/share/doc/python3-regex python-regex 0.1.20171212-1~
-- 
2.11.0

From e11e4ceecb1a0192825201f0aa80371d9c2ec890 Mon Sep 17 00:00:00 2001
From: 

Processed (with 3 errors): upgrading to jessie seems to lead to dataloss

[Debian Bug Tracking System]

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

> severity 809964 critical
Bug #809964 [kwalletmanager] [kwalletmanager] Manager from kde 4 and 5 should 
be co-installable
Severity set to 'critical' from 'normal'
> 
Unknown command or malformed arguments to command.
> justification for severity critical: after the upgrade from jessie to
Unknown command or malformed arguments to command.
> stretch I have no more access to the passwords stored in kwallet.
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#867195: marked as done (haskell-secret-sharing FTBFS: Haddock failed (no modules?), refusing to create empty documentation package.)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 21:20:02 +
with message-id 
and subject line Bug#867195: fixed in ghc 8.0.2-11
has caused the Debian Bug report #867195,
regarding haskell-secret-sharing FTBFS: Haddock failed (no modules?), refusing 
to create empty documentation package.
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.)


-- 
867195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-secret-sharing
Version: 1.0.0.3-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes haskell-secret-sharing FTBFS:

https://tests.reproducible-builds.org/debian/history/haskell-secret-sharing.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/haskell-secret-sharing.html

...
/usr/bin/haddock 
'@dist-ghc/doc/html/secret-sharing/haddock-response16816927771714636915.txt' 
'--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'

src/Crypto/SecretSharing/Internal.hs:129:52: warning: [-Wtype-defaults]
* Defaulting the following constraints to type `Integer'
(Integral a0)
  arising from a use of `fromIntegral'
  at src/Crypto/SecretSharing/Internal.hs:129:52-68
(Num a0)
  arising from the literal `1021'
  at src/Crypto/SecretSharing/Internal.hs:129:65-68
* In the second argument of `($)', namely `fromIntegral 1021'
  In the expression: primeField $ fromIntegral 1021
  In the untyped splice: $(primeField $ fromIntegral 1021)
Haddock coverage:
  62% ( 10 / 16) in 'Crypto.SecretSharing.Internal'
  Missing documentation for:
 (src/Crypto/SecretSharing/Internal.hs:46)
 (src/Crypto/SecretSharing/Internal.hs:54)
 (src/Crypto/SecretSharing/Internal.hs:57)
 (src/Crypto/SecretSharing/Internal.hs:58)
encodeByte (src/Crypto/SecretSharing/Internal.hs:96)
decodeByte (src/Crypto/SecretSharing/Internal.hs:104)
 100% (  4 /  4) in 'Crypto.SecretSharing'
haddock: internal error: renameType: HsSpliceTy
CallStack (from HasCallStack):
  error, called at 
utils/haddock/haddock-api/src/Haddock/Interface/Rename.hs:266:30 in 
main:Haddock.Interface.Rename
Haddock failed (no modules?), refusing to create empty documentation package.
/usr/share/cdbs/1/class/hlibrary.mk:173: recipe for target 
'build-haddock-stamp' failed
make: *** [build-haddock-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 8.0.2-11

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated ghc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Feb 2018 14:01:18 -0700
Source: ghc
Binary: ghc ghc-prof ghc-doc
Architecture: source
Version: 8.0.2-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Sean Whitton 
Description:
 ghc- The Glasgow Haskell Compilation system
 ghc-doc- Documentation for the Glasgow Haskell Compilation system
 ghc-prof   - Profiling libraries for the Glasgow Haskell Compilation system
Closes: 867195
Changes:
 ghc (8.0.2-11) unstable; urgency=medium
 .
   [ Ilias Tsitsimpis ]
   * Change Priority to optional. Since Debian Policy version 4.0.1,
 priority extra has been deprecated.
   * Use the HTTPS form of the copyright-format URL
   * Modify d/watch and Source field in d/copyright to use HTTPS
   * Declare compliance with Debian policy 4.1.1
 .
   [ Sean Whitton ]
   * Add fix-hssplicety.patch (Closes: #867195).
Checksums-Sha1:
 18983a52c0e942d88f01b6b3502ea002094aea66 2355 ghc_8.0.2-11.dsc
 b4fafc38fc774553d88a27cb0fc06c921281aa2e 51608 ghc_8.0.2-11.debian.tar.xz
 a89b9fa2a6e98b1d2cf0fdc0e790e32b9565f2c6 6196 ghc_8.0.2-11_source.buildinfo
Checksums-Sha256:
 f0c116416f139233a1d8c8bf0238aa84dbc599796c86c42d9af25a9f33993076 2355 
ghc_8.0.2-11.dsc
 

Bug#854696: marked as done (sanlock: error in wdmd.service systemd unit file)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 21:21:10 +
with message-id 
and subject line Bug#854696: fixed in sanlock 3.6.0-2
has caused the Debian Bug report #854696,
regarding sanlock: error in wdmd.service systemd unit file
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.)


-- 
854696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sanlock
Version: 3.3.0-2
Severity: normal


Dear Maintainer,

here is the problem:

# systemd-analyze verify /lib/systemd/system/wdmd.service
wdmd.service: Command /lib/systemd/systemd-wdmd is not executable: No such file 
or directory


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

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

Versions of packages sanlock depends on:
ii  adduser  3.115
ii  libaio1  0.3.110-3
ii  libblkid12.29.1-1
ii  libc62.24-9
ii  libsanlock1  3.3.0-2
ii  libuuid1 2.29.1-1

sanlock recommends no packages.

sanlock suggests no packages.

-- no debconf information

-- 
Laurent.
--- End Message ---
--- Begin Message ---
Source: sanlock
Source-Version: 3.6.0-2

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

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

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

Debian distribution maintenance software
pp.
Milan Zamazal  (supplier of updated sanlock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Feb 2018 21:34:07 +0100
Source: sanlock
Binary: sanlock libsanlock-client1 libsanlock1 libsanlock-dev python-sanlock
Architecture: source amd64
Version: 3.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Milan Zamazal 
Changed-By: Milan Zamazal 
Description:
 libsanlock-client1 - Shared storage lock manager (client library)
 libsanlock-dev - Shared storage lock manager (development files)
 libsanlock1 - Shared storage lock manager (shared library)
 python-sanlock - Python bindings to shared storage lock manager
 sanlock- Shared storage lock manager
Closes: 854696 888721
Changes:
 sanlock (3.6.0-2) unstable; urgency=medium
 .
   * Add sanlock user to disk group only after the user is created, thanks
 to Christian Ehrhardt; closes: #888721.
   * Create missing systemd-wdmd file, thanks to Christian Ehrhardt;
 closes: #854696.
Checksums-Sha1:
 52b562cca447e0bd184e2d93694a13dec48e0a60 2027 sanlock_3.6.0-2.dsc
 de4e72e62ac48ff49e36d9b9a738b1ceb34c3fb2 8276 sanlock_3.6.0-2.debian.tar.xz
 01a729f32a8ded60e6cdf19054cf3f67fe8c47f5 26620 
libsanlock-client1-dbgsym_3.6.0-2_amd64.deb
 7bb3adb4ec08a12897bd693ba713095286b2e73e 13332 
libsanlock-client1_3.6.0-2_amd64.deb
 165dea24fc8fd47f7e05da284515b0e5f055983d 10432 libsanlock-dev_3.6.0-2_amd64.deb
 dd59cd4679088aea761c96617ca3d43529d67e49 102208 
libsanlock1-dbgsym_3.6.0-2_amd64.deb
 fb58ed4458bf4fc80c916eab8e4d782592260783 42140 libsanlock1_3.6.0-2_amd64.deb
 e90f1a5a8c26f38c3c0864e931662d90523e543e 26484 
python-sanlock-dbgsym_3.6.0-2_amd64.deb
 761c5a2b622c0ca6d3d913c00028ce14876b828b 14892 python-sanlock_3.6.0-2_amd64.deb
 808be18b48519a87236fa6d42ad43a94360a2d5d 252248 
sanlock-dbgsym_3.6.0-2_amd64.deb
 9640b58ee164614b6905a51287dce80a57746923 8576 sanlock_3.6.0-2_amd64.buildinfo
 6f877fe140affe1533dac246c665245ba2e64be7 113236 sanlock_3.6.0-2_amd64.deb
Checksums-Sha256:
 19835ac679b9fadf487e3e8bd27e83a222384ae67955eaeb404e656dfe776fac 2027 
sanlock_3.6.0-2.dsc
 825e30fc0b0dd089c55a16ae737fa2be771ccce8d75c721e6dfc0b5913671331 8276 
sanlock_3.6.0-2.debian.tar.xz
 19cbd236d376513c66f920cc355a463f69778b2fe951def2d07f90b2eac692d1 26620 
libsanlock-client1-dbgsym_3.6.0-2_amd64.deb
 1141954d9092bd425c8fa843576d2e6f425ee34f672bc8235e610df016644ba0 13332 

Bug#888721: marked as done (sanlock uninstallable due to ordering of user handling in postinst)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 21:21:11 +
with message-id 
and subject line Bug#888721: fixed in sanlock 3.6.0-2
has caused the Debian Bug report #888721,
regarding sanlock uninstallable due to ordering of user handling in postinst
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.)


-- 
888721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sanlock
Version: 3.6.0-1
Severity: grave

Hi,
since the following change in the last upload:
  * Add `sanlock' user to `disk' group, thanks to Charlie Smurthwaite;
closes: #888102.
sanlock became uninstallable.

What happens is:
# apt install sanlock
[...]
Setting up sanlock (3.6.0-1) ...
addgroup: The user `sanlock' does not exist.
dpkg: error processing package sanlock (--configure):

The error itself is rather trivial, it is the ordering of actions in
the postinst:
It is atm (simplified)
1. addgroup sanlock disk
2. adduser sanlock

And of these #1 fails since only after #2 the sanlock user would be around.
This might have been missed since on an upgrade things are fine with
the user already existing, but the issue makes sanlock effectively
uninstallable - therefore grave severity.

Fix was tested by repackaging:

  apt-get download sanlock
  dpkg-deb -x sanlock_3.6.0-1_amd64.deb sanlock
  dpkg-deb -e sanlock_3.6.0-1_amd64.deb sanlock/DEBIAN
  vim sanlock/DEBIAN/postinst
Change order of user creation and adding to the group.
  dpkg-deb -b sanlock sanlock_3.6.0-2_amd64.deb
  dpkg -i sanlock_3.6.0-2_amd64.deb

Note, by being uninstallable it also breaks dependent packages like
e.g. atm the build of a new libvirt.

The required change is just to move the addgroup below the useradd like:


Author: Christian Ehrhardt 
Date:   Mon Jan 29 07:10:59 2018 +0100

d/sanlock.postinst: run addgroup after creating the user

Signed-off-by: Christian Ehrhardt 

diff --git a/debian/sanlock.postinst b/debian/sanlock.postinst
index ccbf821..3c1895a 100755
--- a/debian/sanlock.postinst
+++ b/debian/sanlock.postinst
@@ -40,9 +40,6 @@ case "$1" in
if ! getent group sanlock >/dev/null; then
addgroup --quiet --system sanlock
fi
-   if ! { getent group disk | grep --quiet '\'; }; then
-   addgroup --quiet sanlock disk
-   fi

if ! getent passwd sanlock >/dev/null; then
adduser --quiet \
@@ -56,6 +53,9 @@ case "$1" in
--gecos "sanlock" \
sanlock
fi
+   if ! { getent group disk | grep --quiet '\'; }; then
+   addgroup --quiet sanlock disk
+   fi

;;
--- End Message ---
--- Begin Message ---
Source: sanlock
Source-Version: 3.6.0-2

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

Debian distribution maintenance software
pp.
Milan Zamazal  (supplier of updated sanlock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Feb 2018 21:34:07 +0100
Source: sanlock
Binary: sanlock libsanlock-client1 libsanlock1 libsanlock-dev python-sanlock
Architecture: source amd64
Version: 3.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Milan Zamazal 
Changed-By: Milan Zamazal 
Description:
 libsanlock-client1 - Shared storage lock manager (client library)
 libsanlock-dev - Shared storage lock manager (development files)
 libsanlock1 - Shared storage lock manager (shared library)
 python-sanlock - Python bindings to shared storage lock manager
 sanlock- Shared storage lock manager
Closes: 854696 888721
Changes:
 sanlock (3.6.0-2) unstable; urgency=medium
 .
   * Add sanlock user to disk group only after the user is created, thanks
 to Christian Ehrhardt; closes: #888721.
   * Create missing systemd-wdmd file, thanks to Christian Ehrhardt;
 closes: #854696.
Checksums-Sha1:
 

Bug#888145: marked as done (r10k: FTBFS on ruby2.5: undefined method `features' for Rugged:Module)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 21:09:45 +
with message-id 
and subject line Bug#888145: fixed in r10k 2.6.2-1
has caused the Debian Bug report #888145,
regarding r10k: FTBFS on ruby2.5: undefined method `features' for Rugged:Module
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.)


-- 
888145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r10k
Version: 2.6.1-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Finished in 7.41 seconds (files took 0.74599 seconds to load)
707 examples, 0 failures, 3 pending

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/build/r10k-2.6.1/debian/r10k/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/r10k/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb  
--exclude-pattern ./spec/unit/forge/module_release_spec.rb
...*...FFF.*.*...# terminated with exception (report_on_exception is true):
/build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:53:in `select': 
closed stream (IOError)
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:53:in 
`rescue in pump'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:48:in 
`pump'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:30:in 
`block in start'
# terminated with exception (report_on_exception is true):
:74:in `__read_nonblock': stream closed in another thread 
(IOError)
from :74:in `read_nonblock'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:49:in 
`pump'
from /build/r10k-2.6.1/lib/r10k/util/subprocess/runner/pump.rb:30:in 
`block in start'
...

Pending: (Failures listed here are expected and do not affect your suite's 
status)

...

Failures:

  1) R10K::Git explicitly setting the provider under c-based rubies sets the 
current provider if the provider exists and is functional
 Failure/Error: if !::Rugged.features.include?(transport)

 NoMethodError:
   undefined method `features' for Rugged:Module
 # ./lib/r10k/git.rb:31:in `block (2 levels) in '
 # ./lib/r10k/git.rb:30:in `each'
 # ./lib/r10k/git.rb:30:in `block in '
 # ./lib/r10k/git.rb:92:in `provider='
 # ./spec/unit/git_spec.rb:59:in `block (4 levels) in '

  2) R10K::Git retrieving the current provider under c-based rubies uses the 
default if a provider has not been set
 Failure/Error: raise R10K::Error, _("Git provider '%{name}' is not 
functional.") % {name: name}

 R10K::Error:
   Git provider 'rugged' is not functional.
 # ./lib/r10k/git.rb:89:in `provider='
 # ./lib/r10k/git.rb:106:in `provider'
 # ./spec/unit/git_spec.rb:77:in `block (4 levels) in '

  3) R10K::Git retrieving the current provider under c-based rubies uses an 
explicitly set provider
 Failure/Error: if !::Rugged.features.include?(transport)

 NoMethodError:
   undefined method 

Bug#886944: python3-regex: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Sandro Tosi]

patch is welcome, NMU is not; feel free to upload the patch to this bug and
i'll take care of the upload. thanks for working on this Debian bug

On Tue, Feb 6, 2018 at 3:54 PM, Nicholas D Steeves 
wrote:

> Hi Andreas,
>
> On Mon, Feb 05, 2018 at 06:32:35PM -0500, Nicholas D Steeves wrote:
> > Hi Andreas and Sandro,
> >
> > On Thu, Jan 11, 2018 at 05:04:13PM +0100, Andreas Beckmann wrote:
> > > Followup-For: Bug #886944
> > > Control: affects -1 + python-regex-dbg
> > >
> > > Hi,
> > >
> > > similar issue in python-regex-dbg:
> > >
> > > 0m33.5s ERROR: FAIL: silently overwrites files via directory symlinks:
> > >   /usr/share/doc/python-regex-dbg/Features.html (python-regex-dbg) !=
> /usr/share/doc/python-regex/Features.html (python-regex)
> > > /usr/share/doc/python-regex-dbg -> python-regex
> > >   /usr/share/doc/python-regex-dbg/Features.rst.gz (python-regex-dbg)
> != /usr/share/doc/python-regex/Features.rst.gz (python-regex)
> > > /usr/share/doc/python-regex-dbg -> python-regex
> > >   /usr/share/doc/python-regex-dbg/README (python-regex-dbg) !=
> /usr/share/doc/python-regex/README (python-regex)
> > > /usr/share/doc/python-regex-dbg -> python-regex
> > >   /usr/share/doc/python-regex-dbg/UnicodeProperties.txt.gz
> (python-regex-dbg) != /usr/share/doc/python-regex/UnicodeProperties.txt.gz
> (python-regex)
> > > /usr/share/doc/python-regex-dbg -> python-regex
> > >   /usr/share/doc/python-regex-dbg/changelog.Debian.gz
> (python-regex-dbg) != /usr/share/doc/python-regex/changelog.Debian.gz
> (python-regex)
> > > /usr/share/doc/python-regex-dbg -> python-regex
> > >   /usr/share/doc/python-regex-dbg/copyright (python-regex-dbg) !=
> /usr/share/doc/python-regex/copyright (python-regex)
> > > /usr/share/doc/python-regex-dbg -> python-regex
> > >
> > > and probably python3-regex-dbg as well, although that does not get
> > > tested by piuparts as long as python3-regex fails.
> > >
> > >
> > > Andreas
> >
> > I'll attempt to fix this evening, because if calibre is removed from
> > testing than my planned backport will be in jeopardy.  If I succeed
> > I'll prepare an NMU, but in any case I'll reply to this bug with my
> > results.
> >
> > Cheers,
> > Nicholas
>
> Solved it!  I'll prepare a minimal NMU later today.  Would you please
> consider sponsoring the upload (I'll CC you for the RFS)?
>
> Regards,
> Nicholas
>



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#889759: leptonlib: CVE-2018-3836: gplotMakeOutput Command Injection Vulnerability

[Salvatore Bonaccorso]

Source: leptonlib
Version: 1.71-2.1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for leptonlib.

CVE-2018-3836[0]:
gplotMakeOutput Command Injection Vulnerability

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-3836
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3836
[1] https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0516

Regards,
Salvatore

Processed: Re: Bug#867195: haskell-secret-sharing FTBFS: Haddock failed (no modules?), refusing to create empty documentation package.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ghc
Bug #867195 [src:haskell-secret-sharing] haskell-secret-sharing FTBFS: Haddock 
failed (no modules?), refusing to create empty documentation package.
Bug reassigned from package 'src:haskell-secret-sharing' to 'ghc'.
No longer marked as found in versions haskell-secret-sharing/1.0.0.3-3.
Ignoring request to alter fixed versions of bug #867195 to the same values 
previously set
> tag -1 +pending
Bug #867195 [ghc] haskell-secret-sharing FTBFS: Haddock failed (no modules?), 
refusing to create empty documentation package.
Added tag(s) pending.

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

Bug#867195: haskell-secret-sharing FTBFS: Haddock failed (no modules?), refusing to create empty documentation package.

[Sean Whitton]

control: reassign -1 ghc
control: tag -1 +pending

Hello,

On Tue, Jul 04 2017, Adrian Bunk wrote:

> Some recent change in unstable makes haskell-secret-sharing FTBFS:
> [...]

This is a bug in haddock, fixed upstream.[1]  I'm preparing an upload of
ghc (where Debian's haddock hangs out) with the patch applied.

[1]  
https://github.com/haskell/haddock/pull/745/commits/4209b7bc85bcd7734490df40bfbf6f64e9b39da3

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#886944: python3-regex: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Nicholas D Steeves]

Hi Andreas,

On Mon, Feb 05, 2018 at 06:32:35PM -0500, Nicholas D Steeves wrote:
> Hi Andreas and Sandro,
> 
> On Thu, Jan 11, 2018 at 05:04:13PM +0100, Andreas Beckmann wrote:
> > Followup-For: Bug #886944
> > Control: affects -1 + python-regex-dbg
> > 
> > Hi,
> > 
> > similar issue in python-regex-dbg:
> > 
> > 0m33.5s ERROR: FAIL: silently overwrites files via directory symlinks:
> >   /usr/share/doc/python-regex-dbg/Features.html (python-regex-dbg) != 
> > /usr/share/doc/python-regex/Features.html (python-regex)
> > /usr/share/doc/python-regex-dbg -> python-regex
> >   /usr/share/doc/python-regex-dbg/Features.rst.gz (python-regex-dbg) != 
> > /usr/share/doc/python-regex/Features.rst.gz (python-regex)
> > /usr/share/doc/python-regex-dbg -> python-regex
> >   /usr/share/doc/python-regex-dbg/README (python-regex-dbg) != 
> > /usr/share/doc/python-regex/README (python-regex)
> > /usr/share/doc/python-regex-dbg -> python-regex
> >   /usr/share/doc/python-regex-dbg/UnicodeProperties.txt.gz 
> > (python-regex-dbg) != /usr/share/doc/python-regex/UnicodeProperties.txt.gz 
> > (python-regex)
> > /usr/share/doc/python-regex-dbg -> python-regex
> >   /usr/share/doc/python-regex-dbg/changelog.Debian.gz (python-regex-dbg) != 
> > /usr/share/doc/python-regex/changelog.Debian.gz (python-regex)
> > /usr/share/doc/python-regex-dbg -> python-regex
> >   /usr/share/doc/python-regex-dbg/copyright (python-regex-dbg) != 
> > /usr/share/doc/python-regex/copyright (python-regex)
> > /usr/share/doc/python-regex-dbg -> python-regex
> > 
> > and probably python3-regex-dbg as well, although that does not get
> > tested by piuparts as long as python3-regex fails.
> > 
> > 
> > Andreas
> 
> I'll attempt to fix this evening, because if calibre is removed from
> testing than my planned backport will be in jeopardy.  If I succeed
> I'll prepare an NMU, but in any case I'll reply to this bug with my
> results.
> 
> Cheers,
> Nicholas

Solved it!  I'll prepare a minimal NMU later today.  Would you please
consider sponsoring the upload (I'll CC you for the RFS)?

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#887695: nfs-utils: diff for NMU version 1:1.3.4-2.2

[Adrian Bunk]

Control: tags 887695 + pending

Dear maintainer,

I've prepared an NMU for nfs-utils (versioned as 1:1.3.4-2.2) and 
uploaded it to DELAYED/15. 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 nfs-utils-1.3.4/debian/changelog nfs-utils-1.3.4/debian/changelog
--- nfs-utils-1.3.4/debian/changelog	2017-03-20 17:07:55.0 +0200
+++ nfs-utils-1.3.4/debian/changelog	2018-02-06 21:20:36.0 +0200
@@ -1,3 +1,14 @@
+nfs-utils (1:1.3.4-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with glibc 2.26,
+thanks to Juhani Numminen. (Closes: #887695)
+  * Update the build dependency from the obsolete dh-systemd.
+  * Stop using bzip2 for source compression,
+the default xz compresses better.
+
+ -- Adrian Bunk   Tue, 06 Feb 2018 21:20:36 +0200
+
 nfs-utils (1:1.3.4-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru nfs-utils-1.3.4/debian/control nfs-utils-1.3.4/debian/control
--- nfs-utils-1.3.4/debian/control	2016-12-15 15:30:00.0 +0200
+++ nfs-utils-1.3.4/debian/control	2018-02-06 21:20:36.0 +0200
@@ -3,7 +3,7 @@
 Section: net
 Maintainer: Debian kernel team 
 Uploaders: Anibal Monsalve Salazar , Ben Hutchings , Steve Langasek , Daniel Pocock 
-Build-Depends: debhelper (>= 7), libwrap0-dev, libevent-dev, libnfsidmap-dev (>= 0.24), libkrb5-dev, libblkid-dev, libkeyutils-dev, pkg-config, libldap2-dev, libcap-dev, libtirpc-dev (>= 0.2.4-2~), libdevmapper-dev, dh-autoreconf, libmount-dev, libsqlite3-dev, dh-systemd
+Build-Depends: debhelper (>= 9.20160709), libwrap0-dev, libevent-dev, libnfsidmap-dev (>= 0.24), libkrb5-dev, libblkid-dev, libkeyutils-dev, pkg-config, libldap2-dev, libcap-dev, libtirpc-dev (>= 0.2.4-2~), libdevmapper-dev, dh-autoreconf, libmount-dev, libsqlite3-dev
 Standards-Version: 3.9.8
 Homepage: http://linux-nfs.org/
 Vcs-Git: git://anonscm.debian.org/collab-maint/nfs-utils.git
diff -Nru nfs-utils-1.3.4/debian/gbp.conf nfs-utils-1.3.4/debian/gbp.conf
--- nfs-utils-1.3.4/debian/gbp.conf	2016-12-15 15:30:00.0 +0200
+++ nfs-utils-1.3.4/debian/gbp.conf	2018-02-06 21:20:36.0 +0200
@@ -6,4 +6,3 @@
 # Options only affecting git-buildpackage
 [git-buildpackage]
 sign-tags = True
-compression = bzip2
diff -Nru nfs-utils-1.3.4/debian/patches/0001-rpc.c-added-include-file-so-UINT16_MAX-is-defined.patch nfs-utils-1.3.4/debian/patches/0001-rpc.c-added-include-file-so-UINT16_MAX-is-defined.patch
--- nfs-utils-1.3.4/debian/patches/0001-rpc.c-added-include-file-so-UINT16_MAX-is-defined.patch	1970-01-01 02:00:00.0 +0200
+++ nfs-utils-1.3.4/debian/patches/0001-rpc.c-added-include-file-so-UINT16_MAX-is-defined.patch	2018-02-06 21:19:05.0 +0200
@@ -0,0 +1,25 @@
+From ba03a02c2fd912f370e1f55de921a403bf5f9247 Mon Sep 17 00:00:00 2001
+From: Steve Dickson 
+Date: Thu, 22 Jun 2017 12:56:41 -0400
+Subject: rpc.c: added include file so UINT16_MAX is defined.
+
+Signed-off-by: Steve Dickson 
+---
+ support/nsm/rpc.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/support/nsm/rpc.c b/support/nsm/rpc.c
+index 4e5f40e..0a8e56f 100644
+--- a/support/nsm/rpc.c
 b/support/nsm/rpc.c
+@@ -38,6 +38,7 @@
+ #include 
+ #include 
+ 
++#include 
+ #include 
+ #include 
+ #include 
+-- 
+2.11.0
+
diff -Nru nfs-utils-1.3.4/debian/patches/series nfs-utils-1.3.4/debian/patches/series
--- nfs-utils-1.3.4/debian/patches/series	2016-12-17 12:47:35.0 +0200
+++ nfs-utils-1.3.4/debian/patches/series	2018-02-06 21:20:34.0 +0200
@@ -10,3 +10,4 @@
 unbreak-gssd-rpc_pipefs-run.patch
 28-nfs-utils_env-location.patch
 29-start-statd-fd-9.patch
+0001-rpc.c-added-include-file-so-UINT16_MAX-is-defined.patch
diff -Nru nfs-utils-1.3.4/debian/source/options nfs-utils-1.3.4/debian/source/options
--- nfs-utils-1.3.4/debian/source/options	2016-12-15 15:30:00.0 +0200
+++ nfs-utils-1.3.4/debian/source/options	2018-02-06 21:20:36.0 +0200
@@ -1,3 +1 @@
-compression = "bzip2"
-compression-level = 9
 extend-diff-ignore = "(^|/)(config.sub|config.guess|Makefile.in|configure|config.log|aclocal.m4|ltmain.sh|aclocal/libtool.m4)$"

Processed: nfs-utils: diff for NMU version 1:1.3.4-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 887695 + pending
Bug #887695 [src:nfs-utils] nfs-utils FTBFS with glibc 2.26
Added tag(s) pending.

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

Processed: libffado: diff for NMU version 2.3.0-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 887781 + pending
Bug #887781 [src:libffado] libffado FTBFS with glibc 2.26
Added tag(s) pending.

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

Bug#887781: libffado: diff for NMU version 2.3.0-5.1

[Adrian Bunk]

Control: tags 887781 + pending

Dear maintainer,

I've prepared an NMU for libffado (versioned as 2.3.0-5.1) and uploaded 
it to DELAYED/15. 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 libffado-2.3.0/debian/changelog libffado-2.3.0/debian/changelog
--- libffado-2.3.0/debian/changelog	2017-11-12 12:55:33.0 +0200
+++ libffado-2.3.0/debian/changelog	2018-02-06 21:14:14.0 +0200
@@ -1,3 +1,11 @@
+libffado (2.3.0-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with glibc 2.26,
+thanks to Juhani Numminen. (Closes: #887781)
+
+ -- Adrian Bunk   Tue, 06 Feb 2018 21:14:14 +0200
+
 libffado (2.3.0-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru libffado-2.3.0/debian/patches/glibc-2.26.patch libffado-2.3.0/debian/patches/glibc-2.26.patch
--- libffado-2.3.0/debian/patches/glibc-2.26.patch	1970-01-01 02:00:00.0 +0200
+++ libffado-2.3.0/debian/patches/glibc-2.26.patch	2018-02-06 21:14:09.0 +0200
@@ -0,0 +1,14 @@
+Description: Backport upstream fix for FTBFS with glibc 2.26
+Bug-Debian: https://bugs.debian.org/887781
+Forwarded: http://subversion.ffado.org/changeset/2710
+
+--- libffado-2.3.0.orig/src/libutil/PosixMessageQueue.h
 libffado-2.3.0/src/libutil/PosixMessageQueue.h
+@@ -35,6 +35,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ namespace Util
+ {
diff -Nru libffado-2.3.0/debian/patches/series libffado-2.3.0/debian/patches/series
--- libffado-2.3.0/debian/patches/series	2017-11-11 16:20:31.0 +0200
+++ libffado-2.3.0/debian/patches/series	2018-02-06 21:13:11.0 +0200
@@ -4,3 +4,4 @@
 powerpcspe.patch
 gcc7.patch
 dbus_with_gcc7.patch
+glibc-2.26.patch

Bug#888182: oops

[Hilko Bengen]

Control: reopen -1
Control: fixed 889686 1.1.28-3

Sorry, I mixed up the bug number in the changelog. This ought to fix it.

Cheers,
-Hilko

Processed: oops

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #888182 {Done: Hilko Bengen } [qemu-system-arm] 
qemu-system-arm: qemu-system-arm crashes when run as part of the nbdkit 
testsuite
'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 nbdkit/1.1.28-3.
> fixed 889686 1.1.28-3
Bug #889686 [src:nbdkit] nbdkit build-depends on various kernel images
The source 'nbdkit' and version '1.1.28-3' do not appear to match any binary 
packages
Marked as fixed in versions nbdkit/1.1.28-3.

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

Processed: Re: src:alot: Please drop "Use file-magic instead of python-magic" patch, alot will FTBFS soon

[Debian Bug Tracking System]

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

> # NMU uploaded to delayed
> tags 889293 pending
Bug #889293 [src:alot] alot: FTBFS: Please drop "Use file-magic instead of 
python-magic" patch
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#889558: marked as done (qtcreator: (Build-)Depends on obsolete libbotan1.10-dev)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 19:05:18 +
with message-id 
and subject line Bug#889558: fixed in qtcreator 4.5.0-3
has caused the Debian Bug report #889558,
regarding qtcreator: (Build-)Depends on obsolete libbotan1.10-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.)


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

Dear Maintainer,

your package qtcreator (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris
--- End Message ---
--- Begin Message ---
Source: qtcreator
Source-Version: 4.5.0-3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Feb 2018 15:41:41 -0300
Source: qtcreator
Binary: qtcreator qtcreator-data qtcreator-doc
Architecture: source
Version: 4.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 qtcreator  - integrated development environment (IDE) for Qt
 qtcreator-data - application data for Qt Creator IDE
 qtcreator-doc - documentation for Qt Creator IDE
Closes: 889558
Changes:
 qtcreator (4.5.0-3) unstable; urgency=medium
 .
   * Switch back to using the embedded botan's code. Version 1.10 will get
 removed from the archive. QTCREATORBUG-19745 was filed against upstream
 to improve this situation (Closes: #889558).
 - Remove botan build dependency.
   * Refresh patches.
Checksums-Sha1:
 5059a5c4dbbabb2b7de9f1b2095be437eb56ce6c 2833 qtcreator_4.5.0-3.dsc
 a11a9d66b08a39eb1ae0387b3ebc6b45e74d1863 19772 qtcreator_4.5.0-3.debian.tar.xz
 5ca08ec191d99de5ede577b40c3dd016b7918308 5503 
qtcreator_4.5.0-3_source.buildinfo
Checksums-Sha256:
 3194ac67899279bd047c80ba792b1607552549f87064ce86459e984871811b44 2833 
qtcreator_4.5.0-3.dsc
 3358dab305d22caf6116b527b9ccc882179156a655b7540c8827623bfdf166c1 19772 
qtcreator_4.5.0-3.debian.tar.xz
 4fa6c92e9246615013f52e8f394b37078c2f004b518ad313920bcc7a7a181cb5 5503 
qtcreator_4.5.0-3_source.buildinfo
Files:
 87512862f8579397e28ff7865b2a6de5 2833 devel optional qtcreator_4.5.0-3.dsc
 7fde49924b3e7efcf8eb928f0b6104a6 19772 devel optional 
qtcreator_4.5.0-3.debian.tar.xz
 cc67de16f64c4cb40fa6920d799bea1b 5503 devel optional 
qtcreator_4.5.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAlp591AUHGxpc2FuZHJv
QGRlYmlhbi5vcmcACgkQq2RfQGKGp9BXMA/9EX2uyBA5hghfOhQQBYp3bzctKO6S
1g2APfkpsfqhtkn9zdm3KnG6DT+gvRL+qZlQ9Te825Ro0KJanzaCbMkHWX9AL+PV
Zi8NhW2gIBUunEjoydZ9qB4MhEWVUg3lOJ3DCciIfj7+ijJJSvqHWBcTBpMOeEno
PBEHl9p7dGttYgtlxW4rbWvjx7VoOpXqEZQ9nVeZ6WsDbE7Ae2z0f03KiWMNOxtv
or1LihIvS9CImLpSMeUfSvEz1aDF1Zz03yJxXW5mgDJ8VJpg36PlF6c3Z7Q3m72s
OfkOZ6am/fH7mpIUy4R5juL1xRbd2YjrSaC9zmtCmRB48+QGq/TBFljwCzjgpMiQ
I8Y80GbHyYRN8vcZsYOHxRlpJfy3TOfaxu3In1ZXDBY0uuv+ezMNneHMNq9sYcsC
X/zkohF8KOvahhD2x3QDFKI5yUL7Yoe5mMcLAO/43AlcMKReY0PmbtFkgmL/4Szz
6bAQoDivYWSA/ans13g4g4Art8jxn0fqEtRMB6l0cne7Vp68lOdth1HDLeN32vFw
RydFZmjxTWzUZp2CIw+seIqshp/zlDoDbuc+n9z9UXq1AH8TTZ8dZQm9e1+6+hAI
68NTXLwa3sqEiTd16K3CATLyde+LvODsygdGVpGs/XjpWaThVMw7udX5KjcBTXjU
y5sTkxDT4a0v8Ic=
=Q6pT
-END PGP SIGNATURE End Message ---

Bug#888182: marked as done (qemu-system-arm: qemu-system-arm crashes when run as part of the nbdkit testsuite)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 18:50:38 +
with message-id 
and subject line Bug#888182: fixed in nbdkit 1.1.28-3
has caused the Debian Bug report #888182,
regarding qemu-system-arm: qemu-system-arm crashes when run as part of the 
nbdkit testsuite
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.)


-- 
888182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-arm
Version: 1:2.11+dfsg-1
Severity: grave

Dear Maintainer,

I just got an nbdkit build failure from the armhf autobuilders. The
test-suite uses libguestfs and spawns qemu-system-arm which is killed by
SIGSEGV. Please see
https://buildd.debian.org/status/fetch.php?pkg=nbdkit=armhf=1.1.28-1=1516723989=0
for the build log.

I re-ran the check in an armhf porterbox chroot (abel) and got the
output below. I don't see any useful output after starting
qemu-system-arm, but at least the command line parameters are visible.

,
| $ LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 make check
| [...]
| guestfish -N fs -m /dev/sda1 write /hello.txt "hello,world"
| libguestfs: trace: set_verbose true
| libguestfs: trace: set_verbose = 0
| libguestfs: create: flags = 0, handle = 0x10e8ee8, program = guestfish
| libguestfs: trace: disk_create "test1.img" "raw" 104857600 
"preallocation:sparse"
| libguestfs: trace: disk_create = 0
| libguestfs: trace: set_pgroup true
| libguestfs: trace: set_pgroup = 0
| libguestfs: trace: add_drive "test1.img" "format:raw"
| libguestfs: trace: add_drive = 0
| libguestfs: trace: is_config
| libguestfs: trace: is_config = 1
| libguestfs: trace: launch
| libguestfs: trace: get_tmpdir
| libguestfs: trace: get_tmpdir = "/tmp"
| libguestfs: trace: version
| libguestfs: trace: version = 
| libguestfs: trace: get_backend
| libguestfs: trace: get_backend = "direct"
| libguestfs: launch: program=guestfish
| libguestfs: launch: version=1.36.11
| libguestfs: launch: backend registered: unix
| libguestfs: launch: backend registered: uml
| libguestfs: launch: backend registered: libvirt 
| libguestfs: launch: backend registered: direct  
| libguestfs: launch: backend=direct
| libguestfs: launch: tmpdir=/tmp/libguestfsZiGbYj
| libguestfs: launch: umask=0022
| libguestfs: launch: euid=2596
| libguestfs: is_openable: /dev/kvm: No such file or directory
| libguestfs: trace: get_backend_setting "force_tcg"
| libguestfs: trace: get_backend_setting = NULL (error)
| libguestfs: trace: get_cachedir
| libguestfs: trace: get_cachedir = "/var/tmp"
| libguestfs: begin building supermin appliance   
| libguestfs: run supermin
| libguestfs: command: run: /usr/bin/supermin
| libguestfs: command: run: \ --build
| libguestfs: command: run: \ --verbose
| libguestfs: command: run: \ --if-newer
| libguestfs: command: run: \ --lock /var/tmp/.guestfs-2596/lock
| libguestfs: command: run: \ --copy-kernel
| libguestfs: command: run: \ -f ext2
| libguestfs: command: run: \ --host-cpu arm
| libguestfs: command: run: \ /usr/lib/arm-linux-gnueabihf/guestfs/supermin.d
| libguestfs: command: run: \ -o /var/tmp/.guestfs-2596/appliance.d
| supermin: version: 5.1.19
| supermin: package handler: debian/dpkg
| supermin: acquiring lock on /var/tmp/.guestfs-2596/lock
| supermin: if-newer: output does not need rebuilding
| libguestfs: finished building supermin appliance
| libguestfs: begin testing qemu features
| libguestfs: trace: get_cachedir
| libguestfs: trace: get_cachedir = "/var/tmp"
| libguestfs: checking for previously cached test results of 
/usr/bin/qemu-system-
| arm, in /var/tmp/.guestfs-2596
| libguestfs: loading previously cached test results
| libguestfs: QMP parse error: parse error: premature EOF\n 
  \n (right here) --^\n (ignored)
| libguestfs: qemu version: 2.11
| libguestfs: qemu mandatory locking: yes
| libguestfs: trace: get_sockdir
| libguestfs: trace: get_sockdir = "/tmp"
| libguestfs: finished testing qemu features
| libguestfs: trace: get_backend_setting "gdb"
| libguestfs: trace: get_backend_setting = NULL (error)
| libguestfs: command: run: dmesg | grep -Eoh 'lpj=[[:digit:]]+'
| dmesg: read kernel buffer failed: Operation not permitted
| libguestfs: read_lpj_from_dmesg: external command exited with error status 1
| libguestfs: read_lpj_from_files: no boot messages files are readable
| [00050ms] /usr/bin/qemu-system-arm \
| -global virtio-blk-device.scsi=off \
| -enable-fips \
| -nodefaults \
| -display none \
| -machine virt,accel=kvm:tcg \
| -m 

Bug#889748: diagnostics FTBFS: FAIL: stacktrace

[Adrian Bunk]

Source: diagnostics
Version: 0.3.3-12
Severity: serious

Some recent change in unstable makes diagnostics FTBFS:

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

...
/usr/bin/make  check-TESTS
make[11]: Entering directory 
'/build/1st/diagnostics-0.3.3/diagnostics/extensions/stacktrace'
make[12]: Entering directory 
'/build/1st/diagnostics-0.3.3/diagnostics/extensions/stacktrace'
FAIL: stacktrace

Testsuite summary for diagnostics 0.3.3

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See diagnostics/extensions/stacktrace/test-suite.log
Please report to christ...@schallhart.net

Makefile:904: recipe for target 'test-suite.log' failed
make[12]: *** [test-suite.log] Error 1

Bug#888160: marked as done (ruby-memfs: FTBFS on ruby2.5: No such file or directory - /test-file)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 18:35:57 +
with message-id 
and subject line Bug#888160: fixed in ruby-memfs 1.0.0-1
has caused the Debian Bug report #888160,
regarding ruby-memfs: FTBFS on ruby2.5: No such file or directory - /test-file
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.)


-- 
888160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-memfs
Version: 0.5.0-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Failures:

  1) FileUtils.copy_entry when +src+ does not exist raises an exception
 Failure/Error: find(path) || fail(Errno::ENOENT, path)

 Errno::ENOENT:
   No such file or directory - /test-file
 # ./lib/memfs/file_system.rb:64:in `find!'
 # ./lib/memfs/file/stat.rb:56:in `initialize'
 # ./lib/memfs/file.rb:137:in `new'
 # ./lib/memfs/file.rb:137:in `lstat'
 # ./spec/fileutils_spec.rb:300:in `block (5 levels) in '
 # ./spec/spec_helper.rb:21:in `block (2 levels) in '
 # ./spec/fileutils_spec.rb:299:in `block (4 levels) in '

  2) FileUtils.rm_f calls rm with +:force+ set to true
 Failure/Error: described_class.rm_f('test')

 TypeError:
   superclass mismatch for class File
 # ./spec/fileutils_spec.rb:886:in `block (3 levels) in '

  3) FileUtils.rm_rf calls rm with +:force+ set to true
 Failure/Error: described_class.rm_rf('test')

 TypeError:
   superclass mismatch for class File
 # ./spec/fileutils_spec.rb:921:in `block (3 levels) in '

  4) FileUtils.rmdir when a directory is not empty ignores errors
 Failure/Error: expect { described_class.rmdir('/test-dir') }.not_to 
raise_error

 TypeError:
   superclass mismatch for class File
 # ./spec/fileutils_spec.rb:946:in `block (4 levels) in '

  5) FileUtils.rmdir when a directory is not empty doesn't remove the directory
 Failure/Error: fail Errno::ENOTEMPTY, path unless directory.empty?

 Errno::ENOTEMPTY:
   Directory not empty - /test-dir
 # ./lib/memfs/file_system.rb:121:in `rmdir'
 # ./lib/memfs/dir.rb:84:in `rmdir'
 # ./spec/fileutils_spec.rb:950:in `block (4 levels) in '

Finished in 0.47079 seconds (files took 1.03 seconds to load)
784 examples, 5 failures, 7 pending

Failed examples:

rspec ./spec/fileutils_spec.rb:298 # FileUtils.copy_entry when +src+ does not 
exist raises an exception
rspec ./spec/fileutils_spec.rb:884 # FileUtils.rm_f calls rm with +:force+ set 
to true
rspec ./spec/fileutils_spec.rb:919 # FileUtils.rm_rf calls rm with +:force+ set 
to true
rspec ./spec/fileutils_spec.rb:945 # FileUtils.rmdir when a directory is not 
empty ignores errors
rspec ./spec/fileutils_spec.rb:949 # FileUtils.rmdir when a directory is not 
empty doesn't remove the directory

[Coveralls] Outside the CI environment, not sending data.
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-memfs-0.5.0/debian/ruby-memfs 
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-memfs.log

Please fix it!

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: ruby-memfs
Source-Version: 1.0.0-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 

Bug#888654: mpv: CVE-2018-6360

[Luciano Bello]

On 2018-02-03 09:13, James Cowgill wrote:
> Unlike the backport for 0.27 which was fairly straightforward, the
> backport for 0.23 required significant changes and I ended up rewriting
> half of it. This means I am less confident about catching all the cases
> to fix this bug. It would be good if anyone could check it over.

I tested the PoC (probably as you) and seems fixed. I tried to cover
under branches and they also look sanitized. I feel as confident as
somebody can be that the patch is complete. It seems functionally safe.

Thanks for your work, please upload.

/luciano



signature.asc
Description: OpenPGP digital signature

Bug#888160: Bug #888160 in ruby-memfs marked as pending

[sbadia]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-memfs/commit/f8399e22456cfa750cbb2f869e824eec98c6b571


d/patches: Import upstream fixes for FileUtils on Ruby 2.5 (Closes: #888160)



(this message was generated automatically)
-- 
Greetings

Processed: Bug #888160 in ruby-memfs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888160 [src:ruby-memfs] ruby-memfs: FTBFS on ruby2.5: No such file or 
directory - /test-file
Added tag(s) pending.

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

Bug#889336: marked as done (dnsmasq cannot be started with systemd 237-1)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 17:49:51 +
with message-id 
and subject line Bug#889336: fixed in dnsmasq 2.78-2
has caused the Debian Bug report #889336,
regarding dnsmasq cannot be started with systemd 237-1
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.)


-- 
889336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnsmasq
Version: 2.78-1
Severity: grave
Tags: upstream

After upgrading from systemd 236-3+b1 to 237-1, the service cannot be started
anymore getting following error in syslog (Tested on multiple (sid) machines):

Feb 03 10:47:35 pcname systemd[1]: Starting dnsmasq - A lightweight DHCP and
caching DNS server...
Feb 03 10:47:35 pcname dnsmasq[2720]: dnsmasq: syntax check OK.
Feb 03 10:47:35 pcname dnsmasq[2739]: started, version 2.78 cachesize 150
Feb 03 10:47:35 pcname dnsmasq[2739]: compile time options: IPv6 GNU-getopt
DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
inotif
Feb 03 10:47:35 pcname dnsmasq[2739]: read /etc/hosts - 30 addresses
Feb 03 10:47:35 pcname systemd[1]: dnsmasq.service: Permission denied while
opening PID file or unsafe symlink chain: /run/dnsmasq/dnsmasq.pid
Feb 03 10:49:06 pcname systemd[1]: dnsmasq.service: Start-post operation timed
out. Stopping.
Feb 03 10:49:06 pcname dnsmasq[2739]: exiting on receipt of SIGTERM
Feb 03 10:49:06 pcname systemd[1]: dnsmasq.service: Failed with result
'timeout'.
Feb 03 10:49:06 pcname systemd[1]: Failed to start dnsmasq - A lightweight DHCP
and caching DNS server.

Regards



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

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

Versions of packages dnsmasq depends on:
ii  dnsmasq-base 2.78-1
ii  init-system-helpers  1.51
ii  lsb-base 9.20170808
ii  netbase  5.4

dnsmasq recommends no packages.

Versions of packages dnsmasq suggests:
pn  resolvconf  

-- Configuration Files:
/etc/default/dnsmasq [Errno 2] No such file or directory: '/etc/default/dnsmasq'
/etc/dnsmasq.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dnsmasq
Source-Version: 2.78-2

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

Debian distribution maintenance software
pp.
Simon Kelley  (supplier of updated dnsmasq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 6 Feb 2018 17:21:30 +
Source: dnsmasq
Binary: dnsmasq dnsmasq-base dnsmasq-utils
Architecture: source amd64 all
Version: 2.78-2
Distribution: unstable
Urgency: high
Maintainer: Simon Kelley 
Changed-By: Simon Kelley 
Description:
 dnsmasq- Small caching DNS proxy and DHCP/TFTP server
 dnsmasq-base - Small caching DNS proxy and DHCP/TFTP server
 dnsmasq-utils - Utilities for manipulating DHCP leases
Closes: 889336
Changes:
 dnsmasq (2.78-2) unstable; urgency=high
 .
* Change ownership of pid file, to keep systemd happy. (closes: #889336)
Checksums-Sha1:
 6bbf12749823850945da6a91b0f685a1233de01c 1876 dnsmasq_2.78-2.dsc
 722fa2dbf470f13a6ea6e0199e6c86886797 23676 dnsmasq_2.78-2.diff.gz
 d103073a0329e88c80665800f7914f2d45e4f1a7 425868 dnsmasq-base_2.78-2_amd64.deb
 4d2fbe0ee9d67a7b8253dcd679b50a775712da2d 23732 dnsmasq-utils_2.78-2_amd64.deb
 49571f864e1c442464b903c9db01ca235d29bfa6 16088 dnsmasq_2.78-2_all.deb
 f115e0b01efd3f02d87d48b219b2a419d58e63c4 5468 dnsmasq_2.78-2_amd64.buildinfo
Checksums-Sha256:
 1227f9d779f2bf1669749f5bf1a22a7dc48f10ac1e3f2b26aedcae34683adb53 1876 
dnsmasq_2.78-2.dsc
 

Bug#889610: tesseract-ocr-srp-latn: uninstallable in sid: Depends: tesseract-srp (>= 3.99) which is unknown

[Jeff Breidenbach]

Thanks will fix ASAP.

On Sun, Feb 4, 2018 at 3:08 PM, Andreas Beckmann  wrote:

> Package: tesseract-ocr-srp-latn
> Version: 4.00~git15-45ed289-5
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package is no longer
> installable in sid:
>
> The following packages have unmet dependencies:
>  tesseract-ocr-srp-latn : Depends: tesseract-srp (>= 3.99) which is a
> virtual package and is not provided by any available package
>
>
> Cheers,
>
> Andreas
>

Bug#884670: marked as done (2to3 binary moved to it's own 2to3 package)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 16:52:42 +
with message-id 
and subject line Bug#884670: fixed in sqlparse 0.2.4-0.1
has caused the Debian Bug report #884670,
regarding 2to3 binary moved to it's own 2to3 package
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.)


-- 
884670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sqlparse
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.
--- End Message ---
--- Begin Message ---
Source: sqlparse
Source-Version: 0.2.4-0.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated sqlparse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Feb 2018 17:27:17 +0100
Source: sqlparse
Binary: python-sqlparse python3-sqlparse pypy-sqlparse python-sqlparse-doc 
sqlformat
Architecture: source
Version: 0.2.4-0.1
Distribution: unstable
Urgency: medium
Maintainer: Andriy Senkovych 
Changed-By: Matthias Klose 
Description:
 pypy-sqlparse - non-validating SQL parser for PyPy
 python-sqlparse - non-validating SQL parser for Python 2
 python-sqlparse-doc - documentation for non-validating SQL parser in Python
 python3-sqlparse - non-validating SQL parser for Python 3
 sqlformat  - SQL formatting utility
Closes: 884670 889007
Changes:
 sqlparse (0.2.4-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version.
   * Build-depend on 2to3. Closes: #884670.
   * Add 2to3 to autopkg test depends. Closes: #889007.
   * Bump standards version.
   * Mark python-sqlparse-doc as M-A: foreign.
   * Build-depend on python3-sphinx instead of python-sphinx.
Checksums-Sha1:
 ee63c437f4973616bfc529d5bcf3cfcfe02a6253 2535 sqlparse_0.2.4-0.1.dsc
 7def27ec3131bd36818e61416b7e4074e1400b8e 61614 sqlparse_0.2.4.orig.tar.gz
 9deb430a694c15123ea539eb10bcd6a892e49c94 6404 sqlparse_0.2.4-0.1.debian.tar.xz
 a982180a527ce40423d09bcaa63291bbd6a26fed 7259 
sqlparse_0.2.4-0.1_source.buildinfo
Checksums-Sha256:
 ef3a05c4517dea7c88acdfe644e4f9dc18fa889538dbe08875ee40caf566ebf6 2535 
sqlparse_0.2.4-0.1.dsc
 ce028444cfab83be538752a2ffdb56bc417b7784ff35bb9a3062413717807dec 61614 
sqlparse_0.2.4.orig.tar.gz
 1c3363dd6807c7a6c31b8413bbbe31855d7982811de6595949343eb382e648e5 6404 
sqlparse_0.2.4-0.1.debian.tar.xz
 871e95b601f21522bfcc6de722a80795e2fe8a6b3d23c47052ade5a9f2ea6851 7259 
sqlparse_0.2.4-0.1_source.buildinfo
Files:
 eec1eb8f5b42e0ee9bfd3ac6a2cfb2b4 2535 python optional sqlparse_0.2.4-0.1.dsc
 8f753105167f35ea94ae6387e8af152f 61614 python optional 
sqlparse_0.2.4.orig.tar.gz
 5951a0b7f2024bd38aa580fe25d78a4f 6404 python optional 
sqlparse_0.2.4-0.1.debian.tar.xz
 8c2dc0c5c36c1651e369dada40845ef6 7259 python optional 
sqlparse_0.2.4-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlp52SYQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9QuUD/9dllcfAW3nT706OK1Xsy8DTIJ+ZKbG7Cbh
gapnARA2BwUn2yUavaC7ciCSzDU3nTvBMMuBgEbjCaeyRr8+cFiVIE0PIUSauSpf
lymEcIyX5InYdfRSuVHu/XvMwWHoML6C5qXwwhjhfLOjRuolrhyWyc3UJbDmezZF
kBjpMtKtvlVlDlgWZO0Whh415jDRxefHxRyrSrZJLC0iHbGoVIkv2Ee0ljerccUh
laV5Qm245fQcvnv9p8Z+dW/sCag1uMhs18d4xNXvCT2d11mWY1T2I4cxWRMLROyx
YPTSJ38DuOSGygKWcpBksMkqyh7hfj7iCYk/5W+NqB4xa1N4JEdQW/D6CStFczui
oNWn8yekJGwfaO2b5uZ0+6jraBxOraZg+gwaKSdqCB9sqddnNVumIeHgslcCX8Vi
7gwsZGEuGdJcbkj675iNvZvsG2KfNC60bA/8Di7tN3B7+X1Eo2x5wsCnyuK6a9nH
Zt9P4KvARtwr8YfXOW5PCS1XXqwjT0YaL+p0Dj3PA2ISHgjdlnwdBT5ZKjFJlJ98
qWPBO8AobkWA3Bux0ewnqpbh/fMip443ClCGkavkcaBQzpnrIO5mAT/T450HFw68
6VwOjchb3EX/63kuJSBfdERZrNeJqAgqNgM+Q+1UUUJI/2MeYh7d3l5nUbzSoPAe
6F3JxyENNw==
=CPjK
-END PGP SIGNATURE End 

Bug#885283: marked as done (ganyremote: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 16:50:16 +
with message-id 
and subject line Bug#885283: fixed in ganyremote 7.0-1
has caused the Debian Bug report #885283,
regarding ganyremote: Depends on unmaintained pygtk
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.)


-- 
885283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganyremote
Version: 6.3.3-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: ganyremote
Source-Version: 7.0-1

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

Debian distribution maintenance software
pp.
Philipp Huebner  (supplier of updated ganyremote package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Feb 2018 17:43:40 +0100
Source: ganyremote
Binary: ganyremote
Architecture: source all
Version: 7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Philipp Huebner 
Changed-By: Philipp Huebner 
Description:
 ganyremote - GTK+ frontend for anyRemote
Closes: 885283
Changes:
 ganyremote (7.0-1) unstable; urgency=medium
 .
   * New upstream version 7.0
   * Switched from python-gtk2 to python-gobject (Closes: #885283)
   * Updated Standards-Version: 4.1.3 (no changes needed)
   * Updated Vcs-* fields in debian/control
   * Updated debian/copyright
Checksums-Sha1:
 239565eadc3115bc19c0db5de8458ea9e4fe56aa 1882 ganyremote_7.0-1.dsc
 08d64cad66f6f49f06373374e17714cac2e4e6ed 314148 ganyremote_7.0.orig.tar.gz
 2260e59d59bfd148537c48918976a01576f0b6d9 3248 ganyremote_7.0-1.debian.tar.xz
 b04b041c335632cd11a86304157e818540118d52 72092 ganyremote_7.0-1_all.deb
 c2f7cd4ba9fbe3786bb49ee6330059417e5c440d 5782 ganyremote_7.0-1_amd64.buildinfo
Checksums-Sha256:
 8b5306e82dffd2d767989b5cabd192b65c725cd2f0b622f50b172a28c66f3b91 1882 
ganyremote_7.0-1.dsc
 6c0bf4153817ea7b3140fc21b04d6276957c0e69f2dec1330fc80c677751fff3 314148 
ganyremote_7.0.orig.tar.gz
 9642ba451a4bea73aced5e322d3a79d1f51496319cc1a7f0be7e47153be016aa 3248 
ganyremote_7.0-1.debian.tar.xz
 13a3f5cde2bbcc5fd4bea4542214b2213ddadf2a5eebf4ff969313b38ed8c2a4 72092 
ganyremote_7.0-1_all.deb
 941c50a7714ea0f9073b4163d2d653d7a557f610bccaa14bb64d7245ed3ce203 5782 
ganyremote_7.0-1_amd64.buildinfo
Files:
 52c54089d7b4a6ae87071bf823bfcd41 1882 gnome optional ganyremote_7.0-1.dsc
 605adcd54cd13fe63d18e8371cf31f95 314148 gnome optional 
ganyremote_7.0.orig.tar.gz
 a2fbf42e17b3c0c91960c016247d554d 3248 gnome optional 
ganyremote_7.0-1.debian.tar.xz
 1c8fd48be62be97e1ca6822c5d06eb63 72092 gnome optional ganyremote_7.0-1_all.deb
 b5450f7248590ab899c2a2fd616cd2bc 5782 gnome optional 
ganyremote_7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAlp524YVHGRlYmFsYW5j
ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0cF1kQALJ/9wTIQfdQUW8NCc+PR/eB90GG
QLA/EXZr7REIv4OTqyM01W3dtg6IAatT5XYMbel6ay6ayo5j/LOAG2blCh+uiB6n
rv0HAiwz7w34jVJC9ncT1KNL+0A+Ggsvk9aNx58mU5mlYNxxw0Gd4Tcn+hmW0G0o
GlTa+De0aalCpSJ45IlJ9zRGwV183L/dci/MZHH8v2j+3PwZqBn7uc6ZfG/Hqyfx
xMfVuNogZ5nJ1n45E6d1lLMMED8EdpBEC8HuWUYNNHKqw/5nQYaUS3ntzgUie89l
3QtHC7g+DI8HyKItIGmmfDZiAV3JstskqefOYphrF1wjWGJDw9xxka8bWBDsjLib
X+3HA4Rqn0eGg0midA7atHijAiMp2sRUQAJbs6AenHV/SbdNa9qtGBYE344eZUzD
OcoVcHdNrqLEU79pXsTBP0qTd/38p8Wn52XDsuVE8RPWul4g9pX3jOMVH5JvIUev

Bug#889602: marked as done (python-cloudkitty: uninstallable in sid: Depends: python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 16:35:39 +
with message-id 
and subject line Bug#889602: fixed in cloudkitty 6.0.0-3
has caused the Debian Bug report #889602,
regarding python-cloudkitty: uninstallable in sid: Depends: python-sqlalchemy 
(< 1.1.0) but 1.1.11+ds1-1 is to be installed
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.)


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

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

The following packages have unmet dependencies:
 python-cloudkitty : Depends: python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 is 
to be installed


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: cloudkitty
Source-Version: 6.0.0-3

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated cloudkitty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Feb 2018 16:58:29 +0100
Source: cloudkitty
Binary: cloudkitty-api cloudkitty-common cloudkitty-doc cloudkitty-processor 
python-cloudkitty
Architecture: source all
Version: 6.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 cloudkitty-api - OpenStack Rating as a Service - API server
 cloudkitty-common - OpenStack Rating as a Service - common files
 cloudkitty-doc - OpenStack Rating as a Service - Documentation
 cloudkitty-processor - OpenStack Rating as a Service - processor
 python-cloudkitty - OpenStack Rating as a Service - Python library
Closes: 889602
Changes:
 cloudkitty (6.0.0-3) unstable; urgency=medium
 .
   * Added logrotate file.
   * Add patch to allow SQLA >= 1.1 (Closes: #889602).
   * Add missing templates.pot.
Checksums-Sha1:
 3e4acb92616b3aca51c0ee3923a18d41d670ea68 3129 cloudkitty_6.0.0-3.dsc
 e1135b21139e47301e760b78cfcf78de2b635727 7652 cloudkitty_6.0.0-3.debian.tar.xz
 d1789b7d9183a22d08d7efdf9dfb7a2e1b096d4b 13480 cloudkitty-api_6.0.0-3_all.deb
 1bbe91e44b49467fcb3786cb3393524067f63ca8 24876 
cloudkitty-common_6.0.0-3_all.deb
 c3559c3989c6fef995ed9880ac362b75589262b9 96820 cloudkitty-doc_6.0.0-3_all.deb
 52a1adc0baf7a4943dd4336747cb3a7c095d863b 4920 
cloudkitty-processor_6.0.0-3_all.deb
 79dc124c362e9f1b160cb33c64b536fee0e496e4 15679 
cloudkitty_6.0.0-3_amd64.buildinfo
 7d1e85e061b4722d51596267ca251bfe7e792640 88680 
python-cloudkitty_6.0.0-3_all.deb
Checksums-Sha256:
 6a1323e78275a8ef10d089ae5628ee6264a5e4ae19127cbd500b2b3aac78c31b 3129 
cloudkitty_6.0.0-3.dsc
 b339b6f1ea9bd1acfe589ee5b667afdd8f8d483a47c5bbacbb3fc7034b60d1e5 7652 
cloudkitty_6.0.0-3.debian.tar.xz
 e0ce6d31777b5cfd8fbf571e834103e7712766833b328556b9775b4eda8d3bbc 13480 
cloudkitty-api_6.0.0-3_all.deb
 611c1cf3daf21fcc881978f5ca6ac42f6c9ba933b5caf2b8879dd1aa590fe377 24876 
cloudkitty-common_6.0.0-3_all.deb
 92196cf5f5c74a4fb3961079e394d2948837827f6782fec30cc616de19559eaf 96820 
cloudkitty-doc_6.0.0-3_all.deb
 826fe98653bcb30176bb469ebaf9e5ea65611f98d6c6ee08dabced4d71a444e0 4920 
cloudkitty-processor_6.0.0-3_all.deb
 2ffa53f326da66a5c1d8cb9bed2a97228bdeb154dcc4214c294bdb7a4bd5446d 15679 
cloudkitty_6.0.0-3_amd64.buildinfo
 59e08ca0724ab780896240573aef5f003fb17be433fbbf0501041d33f8f1bc8c 88680 
python-cloudkitty_6.0.0-3_all.deb
Files:
 d6920f84bbf44d55010b98caaa153712 3129 net optional cloudkitty_6.0.0-3.dsc
 c9723dd56d7eabe1936918e3fa3b5289 7652 net optional 
cloudkitty_6.0.0-3.debian.tar.xz
 40153d9600a4cf785f16468a69067994 13480 net optional 
cloudkitty-api_6.0.0-3_all.deb
 619a206d85803d8504ac13ef5308359a 24876 net optional 
cloudkitty-common_6.0.0-3_all.deb
 397b47286e6c9bc528117c8b9857ace0 96820 doc optional 
cloudkitty-doc_6.0.0-3_all.deb
 

Bug#884222: marked as done (valabind: Fails to build with vala 0.38)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 15:52:57 +
with message-id 
and subject line Bug#884222: fixed in valabind 1.5.0-1
has caused the Debian Bug report #884222,
regarding valabind: Fails to build with vala 0.38
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.)


-- 
884222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: valabind
Version: 0.10.0-3
Severity: serious
Forwarded: https://github.com/radare/valabind/issues/43

I did a test-rebuild of vala reverse-dependencies with vala 0.38.4
from Debian experimental.

https://launchpad.net/~jbicha/+archive/ubuntu/vala38/+packages?batch=185

valabind is the only non-Ubuntu specific package to fail to build.

valabind has one reverse build dependency: radare2.

Since vala 0.38 is part of the GNOME 3.26 release, we would like to
upload vala 0.38 to unstable soon.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: valabind
Source-Version: 1.5.0-1

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated valabind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Feb 2018 10:25:08 -0500
Source: valabind
Binary: valabind
Architecture: source
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Reichel 
Changed-By: Jeremy Bicha 
Description:
 valabind   - converts vapi files to SWIG, C++, GIR or GEAR files
Closes: 884222
Changes:
 valabind (1.5.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
   * Update debian/watch
   * Drop obsolete Debian Vala Team as Maintainer
   * Update Vcs fields for migration to https://salsa.debian.org/
   * Build with vala 0.38 (Closes: #884222)
   * Drop git_build-with-vala036.patch: Applied in new release
   * Cherry-pick drop_superfluous_copies.patch to fix build with vala 0.38
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 b505cf536321e13e4c4b60dd8a9b46898d0b05bb 1826 valabind_1.5.0-1.dsc
 bcd13725989b3097bb772da1f31707126e0014de 140665 valabind_1.5.0.orig.tar.gz
 9534d486f9e807cae0c55c12d25ee094c69d50ad 68900 valabind_1.5.0-1.debian.tar.xz
 a131297df8f9a169f7ec563867e8d5bf349cbc2d 7342 valabind_1.5.0-1_source.buildinfo
Checksums-Sha256:
 5ccd0d2c1e029e5d8f14463445d4ca9f7ffd89351db24e5a8f471eb8ab018875 1826 
valabind_1.5.0-1.dsc
 6dd9483bdf26359689141d7cc5b60bf4a45ce32d64691d5cb8b922e1ec5ed8db 140665 
valabind_1.5.0.orig.tar.gz
 6a236758edf75baacbd4f625cd345cca499a333c9dae26df852567d765d1f64a 68900 
valabind_1.5.0-1.debian.tar.xz
 bfc29e1cf877b71a865281aaf3439545376cf79dae16dfb70d8601ed375c31e7 7342 
valabind_1.5.0-1_source.buildinfo
Files:
 488af22593e1cd1bbc9f766429061a5e 1826 devel optional valabind_1.5.0-1.dsc
 00136079260b6e41aa35ed1ff7a0c490 140665 devel optional 
valabind_1.5.0.orig.tar.gz
 3ab50f4b8f33e983b657eef30fd9a35c 68900 devel optional 
valabind_1.5.0-1.debian.tar.xz
 be6ff8a1927834561cf51d1cd06b38e7 7342 devel optional 
valabind_1.5.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaeckdAAoJEOZsd1rr/mx9BOgP/RibRMHLj+KTOTfYWYlJHQuj
KjzI08lOrXWdGkNgU83QAmpq87Fo2iQzOJtqz55DN6ulkdYMHTSfb0YX2CR8iChd
dPjI4l1ooNFuifUWGeGx/bsHsceDlsVjtycqVexuu6Ih9xYBnjs1xp/78bjc1E/a
KAm8SaDpMeU63S7H5uWYBli8WDSH29116TL3jGiNkNUp7An8HDNzJ8j52bbLC/OV
xetVf6L3W4XfXSud7nbnaH2dheRJCBN4CM7qSV/VZgYjaibwq/H7j/yKrsPwrz4U
w5/aPNMLkC1LtPKKftdGnAXswvO3ergK4kOny6Nz0cD3pL46gK4nj8V0jxw7yZIo
A4yqDeJRv+BNzMW1rnfE1+ANG0TOWMb3P0XnnJVV+9Ao1S5KhWcoVwa1LA9daDOb
jQTPrhDbQe8HJoYY3EfJWVXbe/TtY2JUfhTaEpYHhN502sFLb95mX5UuVIHd5zjt
EkyrxHE0KCm66QCwE3fARninzOoi29qlPb6tA1zhLL9aBETXtm/gps9Dm5xXF3mk
0LVaWamGfrzgczHIDUEbJz3lU0KAuDH5aHCVGLhPJk5p96F2E4q841rXuugU/NEr
yle/bcu8CtAb4Qixi7BNqBuBcGsar5lVcbdETqDhpm8CJd9vy578sqn1ulJt6dAm
v/Dv0UlZVVoReJlkhiwx
=47Ky
-END PGP SIGNATURE End Message ---

Bug#853627: marked as done (qdbm: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 15:51:31 +
with message-id 
and subject line Bug#853627: fixed in qdbm 1.8.78-6.2
has caused the Debian Bug report #853627,
regarding qdbm: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qdbm
Version: 1.8.78-6.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/qdbm_1.8.78-6.1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 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-7/porting_to.html

[...]
CGCDGODCGGGOGOCKCDCODDCOOGGKCOCOCGDDCGOCGO (3250)
KOKOGGKKKCGCCOGKDCKKCCGCKCDDDOOKKGCCODKGDOKDCGGOKO (3300)
CCODGOKKDOCCDODCGGKDGDCDKCGCDGOKKDKKDOCDKGODKGDDOD (3350)
OCCCDOODCCGKOOKDKGDODOOOKOGOGGDDOOOCKDOCCGDKCGOKKK (3400)
KCCKCCKCGOGDGGOOOKDCDCGKGOOGKCKKGDODDCGCGDGDCDCGOK (3450)
COKGKDDKKCDCDDGOGCCOGGOGDGOGDDKCCKCKKKCOODKCCKGGOD (3500)
GOKDKGCKGKCDCOKKGDKGGOODCOKCKDKGCCGOGCKGKDDDGKOGCD (3550)
DKODOKCKDOGDOKDGODOKOODKGCGGOODDKOGCDOKDODDDCGOOOC (3600)
GCGDKKCKKDDCKODDKDOGGOKCCOKKGCKGGDGCDKOGODGGKGCDGC (3650)
GOGGOCKOGCODOCKCDCDOKDCGKDCOKCGDGKCDDDCKODCKCOOGKC (3700)
GDKCGKGKOGDGCDDKOKDKGGOGDOCOGGKOKKDCDKCCKKOKGK (3750)
KODKKKDCOOOGKOCGDGCKGKODKCKCKDGOKDGKOKGCCKCKCO (3800)
KGGGCDGDOKKOCDCCDOOGGKKODKCGOGOOOGKGDOKKCDDOGKODDD (3850)
DCKDDDKDCOOCODDDKGOOCCDCCOKDOGOCOKGKGGDGOGDKKCKODC (3900)
CCCDDOGKDGKGGOOCOGKOOKGDOGCOOKGKDKGCDOOKCGGDGCGCCC (3950)
KODKDGKOCCGOGKGDKCOKGDCGKDKOKKGCCGKGOODDDOGDCO (4000)
GODGDGCDDOGGKGKDODGDDOKGKKOCGOKCKCGDGDDOGOGDCGCDDC (4050)
COKDDKGKCGDKOKCKCCDGDDGKGGCCOKGCDGDGKCDODDOOCGDDGG (4100)
OGKKDDKCKGDDODGDDOKOKKODCCOOCOKCKKGODCCKDCDGCGOKCC (4150)
CGDOOKDDGGKCKKKGOOKOODCKDDKDGGDDKCCGKGKCDOGGDC (4200)
KKOOODCDOOCCDCOOGKGKOGGCKKGCDCCDOKKDDGDCDCODCCCOOD (4250)
DGKGCOKDKOOCGKDKKOKKGOGOCCKOODOKKDOKCKGGCOGGCC (4300)
OGCODDCCDKGCDGKDGKCCDCDKCKKOCOOGODDCOOGCKKDCDOKGKG (4350)
KOGCOOGGKOKKOCKKOODDDCOCGCGOCODOGKODOKOKCDCGOOCKOD (4400)
DCKODKCCKOODKKGCCCKCCGDODOCKGGDKDCDDKKGOKGCDGKOCDG (4450)
ODOKKGKGOGKOGDGDODDDCGOCCKDOOCOGDCGGKGOGDOOGKO (4500)
OKGKDDKGDKKOOGGCKCCKDGCDDGOGOGDGCKKKCDGCCGCDGD (4550)
CDDGCGDOOCCOOCOGODKCOKKOGKOOCDKCDOKOKGCDDOCDKDOGCD (4600)
CKDCKGDDGDDGGOOGDCDDOGCKKDGKDKCCCGDKKKGGGOCKGDKGDD (4650)
OOODDOKKOCDODCDDKKCDCGCDODGCDDOGODDOCGCCOOGDKGGCDG (4700)
DCOGCCGKKOCOCKDDGCKDGGKDOKKCDDCCCGGGDKCGGDGKDCCKOK (4750)
KODOCCGCGODOCGCDCGOGKCKCGGKGDKGCDGCKDDCGOKCOKKDCOK (4800)
CCCDCCCGCKGGOKCKCCOCGOODDGOCKCGOCKKCKGCCGKCOGKCCKC (4850)
ODOCDCKOCGDGOODKOKCGKDCCDKDOGOCKGKCDCKKCKGGCCCDKOK (4900)
GOGCKOODGGOGCDGOKCDKCKKDCKDCKGGGCOCOGOKCDKGKKKDCOD (4950)
CCDGDDDOGGODKCDKOOGKDKOOGGOOOGOKODDCCOKOKDOKODDCCO (5000)
Matching records ... ok
ok

rm -rf casket*
LD_LIBRARY_PATH=.:/lib:/usr/lib:/usr/lib:/<>/junkhome/lib:/usr/local/lib
  ./odtest write casket 500 50 5000

  name=casket  dnum=500  wnum=50  pnum=5000  ibnum=-1  idnum=-1  cbnum=-1  
csiz=-1

.Makefile:257: recipe for target 'check' failed
make[1]: *** [check] Segmentation fault
make[1]: Leaving directory '/<>'
debian/rules:65: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: qdbm
Source-Version: 1.8.78-6.2

We believe that the bug you reported is fixed in the 

Bug#889539: pandas FTBFS: test failures

[Lumin]

Hi Andreas,

On 6 February 2018 at 11:10, Andreas Tille  wrote:

> you did a really good job on latest pandas issues.  Do you think you can
> have a look at this problem as well?

I found no related upsteam issue about the failed tests. However there are
some links that might be useful:

https://stackoverflow.com/questions/40659212/futurewarning-elementwise-comparison-failed-returning-scalar-but-in-the-futur
https://stackoverflow.com/questions/15777951/how-to-suppress-pandas-future-warning

I noticed these lines [1] in the test log. The failures seem to be
numpy issues again
according to the stackoverflow answers.

Apart from that, the pandas packaging needs a patch [2] to reduce
autopkgtest failures.


> BTW, to upgrade pandas to the latest upstream version python-moto is
> needed.  I prepared the packaging (#777089) and may be there is only a
> minor issue to finalise this (see [1]).  It might be a sensible strategy
> To upgrade to latest pandas upstream to not spent to much time on the
> old code - however, I have no idea about compatibility issues of all of
> its rdepends.

I checked and tried to build that package. Feedbacks were sent in
another mail. I think the 0.20.3-12 upload is not necessary as long as
we manage to build the new pandas before the removal, because
there is no obvious bug in pandas itself -- the patch for -12 will be
workarounds to those external problems.


[1] 
debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/dtypes/test_missing.py::test_array_equivalent_compat
  /usr/lib/python2.7/dist-packages/numpy/core/numeric.py:2604:
FutureWarning: elementwise == comparison failed and returning scalar
instead; this will raise an error or perform elementwise comparison in
the future.
return bool(asarray(a1 == a2).all())

debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/frame/test_analytics.py::TestDataFrameAnalytics::()::test_corr_int_and_boolean
  /usr/lib/python2.7/dist-packages/scipy/stats/stats.py:3577:
RuntimeWarning: invalid value encountered in double_scalars
size * (size - 1) * (size - 2))

debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_boxplot_method.py::TestDataFramePlots::()::test_boxplot_legacy
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)

debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_boxplot_method.py::TestDataFramePlots::()::test_boxplot_axis_limits
  /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57:
FutureWarning: reshape is deprecated and will raise in a subsequent
release. Please use .values.reshape(...) instead
return getattr(obj, method)(*args, **kwds)

debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_datetimelike.py::TestTSPlot::()::test_irreg_hf
  /usr/lib/python2.7/dist-packages/matplotlib/cbook/deprecation.py:106:
MatplotlibDeprecationWarning: Adding an axes using the same arguments
as a previous axes currently reuses the earlier instance.  In a future
version, a new instance will always be created and returned.
Meanwhile, this warning can be suppressed, and the future behavior
ensured, by passing a unique label to each axes instance.
warnings.warn(message, mplDeprecation, stacklevel=1)
  

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 888911 libmpfr6
Bug #888911 {Done: Matthias Klose } [src:giac] giac test 
failures with mpfr 4.0.0 on several architectures
Bug reassigned from package 'src:giac' to 'libmpfr6'.
No longer marked as found in versions giac/1.2.3.57+dfsg1-2.
No longer marked as fixed in versions 1.2.3.57+dfsg1-2+b4.
> forcemerge 888422 888911
Bug #888422 [libmpfr6] Mixing libmpfr4 and libmpfr6 doesn't work well
Bug #888422 [libmpfr6] Mixing libmpfr4 and libmpfr6 doesn't work well
Added tag(s) sid and buster.
Bug #888911 {Done: Matthias Klose } [libmpfr6] giac test 
failures with mpfr 4.0.0 on several architectures
888912 was blocked by: 888459 888911
888912 was not blocking any bugs.
Removed blocking bug(s) of 888912: 888911
Bug reopened
Ignoring request to alter fixed versions of bug #888911 to the same values 
previously set
Marked as found in versions mpfr4/4.0.0-5.
Merged 888422 888911
> affects 888422 src:giac
Bug #888422 [libmpfr6] Mixing libmpfr4 and libmpfr6 doesn't work well
Bug #888911 [libmpfr6] giac test failures with mpfr 4.0.0 on several 
architectures
Added indication that 888422 affects src:giac
Added indication that 888911 affects src:giac
> thanks
Stopping processing here.

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

Bug#881580: googleearth-package: Generated package is uninstallable, and application unrunnable

[Arturo Borrero Gonzalez]

On Sun, 12 Nov 2017 22:18:54 -0800 Dima Kogan  wrote:
> Package: googleearth-package
> Version: 1.2.2dima1
> Severity: grave
>
> Hi. I'm installing googleearth on a recent Debian/sid on amd64. Clearly
> I need to have the i386 foreign arch enabled. It'd be nice if the
> install explicitly told unsuspecting users this, but whatever.
>

I was able to use native amd64 by just replacing all the Depends with
the matching amd64 package.

> The generated package Depends:lbs-core even though this package is no
> longer a part of Debian. Removing this, I can make a googleearth package
> that I can install.
>

Probably 'lsb-compat' should be used.

> At that point I can't run the application though. To make it work, I
> needed to
>
> 1. install libqtcore4:i386 libqtgui4:i386 libqt4-network:i386 
> libqtwebkit4:i386 libglu1-mesa:i386
>This list is likely incomplete; it's just what I was missing
>
> 2. The i386 linker the application requires is /lib/ld-lsb.so.3. This
>presumably lived in lsb-core at one point, but it no longer does. I
>can fake it with
>
>  sudo ln -fs /lib/ld-linux.so.2 /lib/ld-lsb.so.3
>

Apart of that (or perhaps same kind of issue):

% googleearth
/usr/lib/googleearth/googleearth-bin: error while loading shared
libraries: libfontconfig.so.1: cannot open shared object file: No such
file or directory


% /usr/lib/googleearth/googleearth-bin
/usr/lib/googleearth/googleearth-bin: error while loading shared
libraries: libgoogleearth_free.so: cannot open shared object file: No
such file or directory

More link problems. Not sure if they could be related to the hack I
did to install into amd64 without the foreign arch enabled.

Bug#887924: slurm-drmaa FTBFS with slurm-llnl 17.11.2-1

[Dominique Belhachemi]

This happens due to a recent change in debian/libslurm-dev.install

https://anonscm.debian.org/git/collab-maint/slurm-llnl.git/commit/debian/libslurm-dev.install?id=08c387553a95e9a4a38047c82cf69a4f733cee0d

Anyway, I am thinking about removing the slurm-drmaa package from the
Debian archive. The popcon count is below 10.

-Dominique

Bug#888911: marked as done (giac test failures with mpfr 4.0.0 on several architectures)

[Debian Bug Tracking System]

Your message dated Tue, 6 Feb 2018 15:24:32 +0100
with message-id 
and subject line Re: giac test failures with mpfr 4.0.0 on several architectures
has caused the Debian Bug report #888911,
regarding giac test failures with mpfr 4.0.0 on several architectures
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.)


-- 
888911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:giac
Version: 1.2.3.57+dfsg1-2
Severity: serious
Tags: sid buster

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

failing tests at least on the release architectures amd64 and armhf.
--- End Message ---
--- Begin Message ---
Version: 1.2.3.57+dfsg1-2+b4

now fixed, built using mpfr4 4.0.1 rc2.--- End Message ---

Bug#885920: [firefox] Firefox window doesn't show under wayland

[Flykt, Patrik]

On Thu, 1 Feb 2018 10:40:46 +0100 Sylvestre Ledru
 wrote:
> Wayland support for Firefox is considered as basic from fx59:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=635134#c86


That explains it. Verified that Firefox works on GNOME/X11, enforcing
GDK_BACKEND=x11 doesn't help either with wayland. Seems I need to wait
for newer Firefox versions and use X11 meanwhile.

Processed: bug 888160 is forwarded to https://github.com/simonc/memfs/issues/27

[Debian Bug Tracking System]

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

> forwarded 888160 https://github.com/simonc/memfs/issues/27
Bug #888160 [src:ruby-memfs] ruby-memfs: FTBFS on ruby2.5: No such file or 
directory - /test-file
Set Bug forwarded-to-address to 'https://github.com/simonc/memfs/issues/27'.
> thanks
Stopping processing here.

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

Bug#889730: virtualbox-dkms: No rule to make target '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/linux/SUPDrv-linux.o'

[Martin Haase]

Package: virtualbox-dkms
Version: 5.2.6-dfsg-3
Severity: grave
Justification: renders package unusable

The issue arose after I upgraded from kernel version 4.13 to 4.14.

The problem has been addressed in bug report #886747. However I can't
verify the alleged solution, since the URL mentioned in the report
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474) is invalid.

I followed the advice to upgrade the kbuild package, but to no avail.

Here's the make.log:

Tue Feb  6 14:16:38 CET 2018
make: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
  AR  /var/lib/dkms/virtualbox/5.2.6/build/built-in.o
  make[4]: *** No rule to make target
'/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/linux/SUPDrv-linux.o',
needed by '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/vboxdrv.o'.
Stop.
make[4]: *** Waiting for unfinished jobs
  AR  /var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/built-in.o
  /usr/src/linux-headers-4.14.0-3-common/scripts/Makefile.build:578:
recipe for target '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv' failed
make[3]: *** [/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv] Error 2
/usr/src/linux-headers-4.14.0-3-common/Makefile:1525: recipe for
target '_module_/var/lib/dkms/virtualbox/5.2.6/build' failed
make[2]: *** [_module_/var/lib/dkms/virtualbox/5.2.6/build] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.14.0-3-amd64'




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

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_GB.ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.3-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  5.2.6-dfsg-3

virtualbox-dkms suggests no packages.

-- no debconf information

Processed: Re: Bug#889724: gcc-7: ICE building tbb

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gcc.gnu.org/PR84233
Bug #889724 [gcc-7] gcc-7: ICE building tbb
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR84233'.
> tags -1 + upstream
Bug #889724 [gcc-7] gcc-7: ICE building tbb
Added tag(s) upstream.
> severity -1 important
Bug #889724 [gcc-7] gcc-7: ICE building tbb
Severity set to 'important' from 'serious'

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

Bug#888879: rheolef FTBFS on several architectures: test runs forever

[Pierre Saramito]

Hi Adrian and Andreas,

Ok, no poblems, I will check this issue.

True, the "make check" test suite was not run before in the
Debian enviromnent. 


This "make check" test suite was developped for managing the 
upstream version source code: it runs a
very long sequence of non-regression test suite.
It runs via "mpirun" and could have non-portability issues
on some architecture. Some possible patch could be to run the
test suite in sequential mode :
   make MPIRUN="" check

 Could you please decrease the severity of this bug, e.g. 
 to normal, as there is no obstacle to build the package.


I have only access to "amd64" achitectures in my lab:
 
 Please could you explain me how to access to access to
 the others machines/architectures used by the Debian team ?
 How to have a login on these machines ?

Thank you for your help maintaining the Debian package,

Pierre
--
pierre.saram...@imag.fr
Directeur de Recherche CNRS
Laboratoire Jean Kuntzmann, Grenoble, France
http://ljk.imag.fr/membres/Pierre.Saramito

- Mail original -
De: "Andreas Tille" 
À: 888...@bugs.debian.org, "PIERRE SARAMITO" 
Envoyé: Mardi 6 Février 2018 11:59:19
Objet: Re: Bug#79: rheolef FTBFS on several architectures: test runs forever

Hi Pierre,

as I mentioned on Debian Science maintainers list[1] this problem does
not come unexpected.  Pierre, could you please confirm whether you keep
on maintaining this package and will check this issue?

>From my uneducated perspective the test failures always existed but the
test were simply not run before.  Thus a first course of action might be
to ask ftpmaster for removal of those architectures where rheolef does
not build and reduce severity of the bug to say "important".

Please note that I do not have any time resources to work on this
package.

Kind regards

  Andreas.

[1] 
https://lists.alioth.debian.org/pipermail/debian-science-maintainers/2018-January/057544.html

On Tue, Jan 30, 2018 at 10:24:18PM +0200, Adrian Bunk wrote:
> Source: rheolef
> Version: 6.7-5
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=rheolef=sid
> 
> ...
>   mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> left >/dev/null 2>/dev/null
>   mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> left >/dev/null 2>/dev/null
>   mpirun -np 3 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> left >/dev/null 2>/dev/null
>   mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> right >/dev/null 2>/dev/null
>   mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> right >/dev/null 2>/dev/null
> E: Build killed with signal TERM after 150 minutes of inactivity
> 
> 
> I've reproduced this on i386, two processes are running
> forever (aborted after 6 hours on a fast CPU) with 100% CPU.
> 
> Backtraces:
> 
> Thread 3 (Thread 0xf50ffb40 (LWP 29032)):
> #0  0xf7ed6db9 in __kernel_vsyscall ()
> #1  0xf70fabd3 in __GI___poll (fds=0xf47005d0, nfds=2, timeout=360) at 
> ../sysdeps/unix/sysv/linux/poll.c:29
> #2  0xf5caed4a in poll (__timeout=360, __nfds=2, __fds=0xf47005d0) at 
> /usr/include/i386-linux-gnu/bits/poll2.h:46
> #3  poll_dispatch (base=0x578eb9c0, tv=0xf50f9bfc) at poll.c:165
> #4  0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, 
> flags=) at event.c:1630
> #5  0xf5c6b3bd in progress_engine (obj=0x578eb950) at 
> runtime/opal_progress_threads.c:105
> #6  0xf5df6316 in start_thread (arg=0xf50ffb40) at pthread_create.c:465
> #7  0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
> 
> Thread 2 (Thread 0xf5ac5b40 (LWP 29031)):
> #0  0xf7ed6db9 in __kernel_vsyscall ()
> #1  0xf71053fa in __GI_epoll_pwait (epfd=7, events=0x578ea930, maxevents=32, 
> timeout=-1, set=0x0)
> at ../sysdeps/unix/sysv/linux/epoll_pwait.c:42
> #2  0xf710569a in epoll_wait (epfd=7, events=0x578ea930, maxevents=32, 
> timeout=-1)
> at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
> #3  0xf5ca199a in epoll_dispatch (base=0x578ea7a0, tv=0x0) at epoll.c:407
> #4  0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, 
> flags=) at event.c:1630
> #5  0xf5af23eb in progress_engine (obj=0x578ea7a0) at 
> src/util/progress_threads.c:52
> #6  0xf5df6316 in start_thread (arg=0xf5ac5b40) at pthread_create.c:465
> #7  0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
> 
> Thread 1 (Thread 0xf5b4fe00 (LWP 29002)):
> #0  0xf7ed67f5 in ?? ()
> #1  0xf7ed6b43 in __vdso_clock_gettime ()
> #2  0xf7112961 in __GI___clock_gettime (clock_id=1, tp=0xffb74194) at 
> ../sysdeps/unix/clock_gettime.c:115
> #3  0xf5cc3297 in opal_timer_linux_get_usec_clock_gettime () at 
> timer_linux_component.c:197
> #4  0xf5c669c3 in opal_progress () at runtime/opal_progress.c:197
> #5  0xf74b5e05 in sync_wait_st (sync=) at 
> ../opal/threads/wait_sync.h:80
> #6  ompi_request_default_wait_all (count=2, requests=0xffb742e4, 
> statuses=0x0) 

Bug#889724: gcc-7: ICE building tbb

[Matthias Klose]

Control: forwarded -1 https://gcc.gnu.org/PR84233
Control: tags -1 + upstream
Control: severity -1 important

On 06.02.2018 12:24, Adrian Bunk wrote:
> Package: gcc-7
> Version: 7.2.0-18
> Severity: serious
> Control: affects -1 src:tbb
> 
> $ g++ -c -O1 test_eh_algorithms.ii
> ../../src/test/test_eh_algorithms.cpp: In function 'void 
> TestParallelLoopAux() [with ParForBody = SimpleParForBody; Partitioner = 
> const tbb::simple_partitioner':
> ../../src/test/test_eh_algorithms.cpp:162:6: internal compiler error: 
> Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.

can be worked around with -O0.

Processed: correcting severity (888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #888549 [chrome-gnome-shell] chrome-gnome-shell: Please don't use /etc/opt, 
it's not FHS-compliant
Severity set to 'serious' from 'normal'
> affects -1 src:debian-edu
Bug #888549 [chrome-gnome-shell] chrome-gnome-shell: Please don't use /etc/opt, 
it's not FHS-compliant
Added indication that 888549 affects src:debian-edu

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

Bug#889642: marked as done (jdeb FTBFS: [ERROR] testClearSign(org.vafer.jdeb.signing.PGPSignerTestCase))

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 12:50:42 +
with message-id 
and subject line Bug#889642: fixed in jdeb 1.6-2
has caused the Debian Bug report #889642,
regarding jdeb FTBFS: [ERROR] 
testClearSign(org.vafer.jdeb.signing.PGPSignerTestCase)
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.)


-- 
889642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jdeb
Version: 1.6-1
Severity: serious

Some recent change in unstable makes jdeb FTBFS:

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

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.vafer.jdeb.maven.DataTestCase
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.851 s 
- in org.vafer.jdeb.maven.DataTestCase
[INFO] Running org.vafer.jdeb.DebMakerTestCase
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 s 
- in org.vafer.jdeb.DebMakerTestCase
[INFO] Running org.vafer.jdeb.DataBuilderTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.14 s - 
in org.vafer.jdeb.DataBuilderTestCase
[INFO] Running org.vafer.jdeb.ant.AntSelectorTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043 s 
- in org.vafer.jdeb.ant.AntSelectorTestCase
[INFO] Running org.vafer.jdeb.ant.DebAntTaskTestCase
[INFO] Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.86 s 
- in org.vafer.jdeb.ant.DebAntTaskTestCase
[INFO] Running org.vafer.jdeb.producers.DataProducerFilesTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.467 s 
- in org.vafer.jdeb.producers.DataProducerFilesTestCase
[INFO] Running org.vafer.jdeb.producers.DataProducerPathTemplateTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.vafer.jdeb.producers.DataProducerPathTemplateTestCase
[INFO] Running org.vafer.jdeb.signing.PGPSignerTestCase
[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.58 s 
<<< FAILURE! - in org.vafer.jdeb.signing.PGPSignerTestCase
[ERROR] testClearSign(org.vafer.jdeb.signing.PGPSignerTestCase)  Time elapsed: 
0.58 s  <<< FAILURE!
org.junit.ComparisonFailure: 
expected:<...-
Version: BCPG v1.5[8]

??...> but was:<...-
Version: BCPG v1.5[9]

??...>
at 
org.vafer.jdeb.signing.PGPSignerTestCase.testClearSign(PGPSignerTestCase.java:68)

[INFO] Running org.vafer.jdeb.signing.DebMakerTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.199 s 
- in org.vafer.jdeb.signing.DebMakerTestCase
[INFO] Running org.vafer.jdeb.debian.ChangesFileTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.vafer.jdeb.debian.ChangesFileTestCase
[INFO] Running org.vafer.jdeb.debian.PackageControlFileTestCase
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 s 
- in org.vafer.jdeb.debian.PackageControlFileTestCase
[INFO] Running org.vafer.jdeb.debian.ControlFieldTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.vafer.jdeb.debian.ControlFieldTestCase
[INFO] Running org.vafer.jdeb.mapping.LsMapperTestCase
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.vafer.jdeb.mapping.LsMapperTestCase
[INFO] Running org.vafer.jdeb.changes.TextfileChangesProviderTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.vafer.jdeb.changes.TextfileChangesProviderTestCase
[INFO] Running org.vafer.jdeb.utils.FilteredFileTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s 
- in org.vafer.jdeb.utils.FilteredFileTestCase
[INFO] Running org.vafer.jdeb.utils.UtilsTestCase
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 s 
- in org.vafer.jdeb.utils.UtilsTestCase
[INFO] Running org.vafer.jdeb.utils.InformationInputStreamTestCase
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.vafer.jdeb.utils.InformationInputStreamTestCase
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   
PGPSignerTestCase.testClearSign:68->Assert.assertEquals:144->Assert.assertEquals:115
 expected:<...-
Version: BCPG v1.5[8]

??...> but was:<...-
Version: BCPG 

Bug#888629: marked as done (smuxi: Unnecessary Build-Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 12:51:10 +
with message-id 
and subject line Bug#888629: fixed in smuxi 1.0.7-2
has caused the Debian Bug report #888629,
regarding smuxi: Unnecessary Build-Depends on old GNOME libraries
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.)


-- 
888629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smuxi
Version: 1.0.7-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui libgnome gnome-vfs-removal
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package has apparently unnecessary Build-Depends on these
libraries:

 libart2.0-cil-dev
 libgnome-vfs2.0-cil-dev
 libgnome2.0-cil-dev

Please remove these Build-Depends. (No patch attached but this seems a
pretty trivial fix.)

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: smuxi
Source-Version: 1.0.7-2

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

Debian distribution maintenance software
pp.
Victor Seva  (supplier of updated smuxi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Feb 2018 13:25:41 +0100
Source: smuxi
Binary: smuxi smuxi-engine smuxi-frontend-gnome smuxi-frontend-stfl
Architecture: source all
Version: 1.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Mirco Bauer 
Changed-By: Victor Seva 
Description:
 smuxi  - graphical IRC client
 smuxi-engine - Engine libraries for Smuxi (IRC, Twitter, XMPP, Campfire, JabbR)
 smuxi-frontend-gnome - GNOME frontend for Smuxi
 smuxi-frontend-stfl - STFL frontend for Smuxi (experimental)
Closes: 888629
Changes:
 smuxi (1.0.7-2) unstable; urgency=medium
 .
   * remove old libgnome build dependencies (Closes: #888629)
   * fix debian-watch-uses-insecure-uri lintian warning
   * update debian/copyright
   * fix autotools-pkg-config-macro-not-cross-compilation-safe
Checksums-Sha1:
 cffe0d29b7006f46581f1644ba6c67380c06d10e 2799 smuxi_1.0.7-2.dsc
 96946934fe1299bc5666bce5cc5213f81c797d4d 14072 smuxi_1.0.7-2.debian.tar.xz
 60c787677e828f31ea913709399ad0f058c4349e 1670052 smuxi-engine_1.0.7-2_all.deb
 5e49d7eb260a5926056b623976aaeade1e4473b6 554964 
smuxi-frontend-gnome_1.0.7-2_all.deb
 b30778000f88651a6ac7ab57e16f36ffa7895794 33272 
smuxi-frontend-stfl_1.0.7-2_all.deb
 3df54527339ce6a0e7296327b47027b637ee5f7e 13340 smuxi_1.0.7-2_all.deb
 d0b877f8785c3eb52570980f3e026036684ea504 21888 smuxi_1.0.7-2_amd64.buildinfo
Checksums-Sha256:
 644de29e120ab56988c0e3476e346806af5ea41ab5c6d8164184c368bd025f42 2799 
smuxi_1.0.7-2.dsc
 86dde3f1a9165ad7d386cd8358364e4672d93f400c13e0da735766e5648956de 14072 
smuxi_1.0.7-2.debian.tar.xz
 1dba871d9d6ae9d11046a2494b3b88bf8680db722979b7e2072644d18c29723e 1670052 
smuxi-engine_1.0.7-2_all.deb
 bc9dabbf6918fd264fb9944b0cca1e0f4751004b094749762494cbc41bc2 554964 
smuxi-frontend-gnome_1.0.7-2_all.deb
 edc862d0e9b9f99c5a97da191b41780774d5ddda2421e81bad5a3458ff3bf9cc 33272 
smuxi-frontend-stfl_1.0.7-2_all.deb
 e39f927d73f96d47c620698b5e9b30ea0ca465c6503a53afb24f377a88d4ac32 13340 
smuxi_1.0.7-2_all.deb
 af31498bd0eee4241d967a883e4ecf976dd6190d75a07dfbaa86d91ededd7a38 21888 
smuxi_1.0.7-2_amd64.buildinfo
Files:
 02bce185c5cb81f72da41e6d2287a69a 2799 gnome optional smuxi_1.0.7-2.dsc
 5426a30c6258a8c7fe5fc23d17bc0c9b 14072 gnome optional 
smuxi_1.0.7-2.debian.tar.xz
 cfe082317dbf0e46131bb5062aa1e58f 1670052 gnome optional 
smuxi-engine_1.0.7-2_all.deb
 09c0f16f24fd76d2a09667416e1699d5 554964 gnome optional 
smuxi-frontend-gnome_1.0.7-2_all.deb
 bbb0dcc2e08b66fa74f852e68de25f47 33272 gnome optional 
smuxi-frontend-stfl_1.0.7-2_all.deb
 85bae194088636ba320b0778bca2cf72 

Processed: Pending fixes for bugs in the jdeb package

[Debian Bug Tracking System]

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

> tag 889642 + pending
Bug #889642 [src:jdeb] jdeb FTBFS: [ERROR] 
testClearSign(org.vafer.jdeb.signing.PGPSignerTestCase)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#889642: Pending fixes for bugs in the jdeb package

[pkg-java-maintainers]

tag 889642 + pending
thanks

Some bugs in the jdeb package are closed in revision
b3bd8c061208bf5db85c2c9859318114daed3f2b in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jdeb.git/commit/?id=b3bd8c0

Commit message:

Update 01_fix_testcase_bouncycastle.patch to fix FTBFS with Bouncycastle 
1.59.

Closes: #889642
Thanks: Adrian Bunk for the report.

Bug#882975: marked as done (android-tools FTBFS with glibc 2.25)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 12:05:33 +
with message-id 
and subject line Bug#882975: fixed in android-tools 5.1.1.r38-1.1
has caused the Debian Bug report #882975,
regarding android-tools FTBFS with glibc 2.25
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.)


-- 
882975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-tools
Version: 5.1.1.r38-1
Severity: serious

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

...
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:215:0,
 from /usr/include/stdlib.h:291,
 from 
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:18:
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
error: initializer element is not constant
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:67:18: 
note: in expansion of macro 'cpu_to_le32'
 .magic = cpu_to_le32(FUNCTIONFS_DESCRIPTORS_MAGIC),
  ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
note: (near initialization for 'descriptors.header.magic')
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:67:18: 
note: in expansion of macro 'cpu_to_le32'
 .magic = cpu_to_le32(FUNCTIONFS_DESCRIPTORS_MAGIC),
  ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
error: initializer element is not constant
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:68:19: 
note: in expansion of macro 'cpu_to_le32'
 .length = cpu_to_le32(sizeof(descriptors)),
   ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
note: (near initialization for 'descriptors.header.length')
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:68:19: 
note: in expansion of macro 'cpu_to_le32'
 .length = cpu_to_le32(sizeof(descriptors)),
   ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
error: initializer element is not constant
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:136:18: 
note: in expansion of macro 'cpu_to_le32'
 .magic = cpu_to_le32(FUNCTIONFS_STRINGS_MAGIC),
  ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
note: (near initialization for 'strings.header.magic')
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:136:18: 
note: in expansion of macro 'cpu_to_le32'
 .magic = cpu_to_le32(FUNCTIONFS_STRINGS_MAGIC),
  ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
error: initializer element is not constant
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:137:19: 
note: in expansion of macro 'cpu_to_le32'
 .length = cpu_to_le32(sizeof(strings)),
   ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
note: (near initialization for 'strings.header.length')
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:137:19: 
note: in expansion of macro 'cpu_to_le32'
 .length = cpu_to_le32(sizeof(strings)),
   ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
error: initializer element is not constant
 #define cpu_to_le32(x)  htole32(x)
 ^
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:138:22: 
note: in expansion of macro 'cpu_to_le32'
 .str_count = cpu_to_le32(1),
  ^~~
/build/1st/android-tools-5.1.1.r38/system/core/adb/usb_linux_client.c:38:25: 
note: (near initialization for 'strings.header.str_count')
 #define cpu_to_le32(x)  htole32(x)
 ^

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

[Adam Majer]

On 02/05/2018 09:13 PM, Lisandro Damián Nicanor Pérez Meyer wrote:

It seems that qt creator is the only real package preventing the botan
removal, so please go ahead with it. I'll make qtcreator use it's internal
copy for the moment being.



Or maybe stop using Botan altogether? I think it only affects a few plugins?

- Adam

Processed: gcc-7: ICE building tbb

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:tbb
Bug #889724 [gcc-7] gcc-7: ICE building tbb
Added indication that 889724 affects src:tbb

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

Bug#889539: pandas FTBFS: test failures

[Andreas Tille]

Hi Lumin,

you did a really good job on latest pandas issues.  Do you think you can
have a look at this problem as well?

BTW, to upgrade pandas to the latest upstream version python-moto is
needed.  I prepared the packaging (#777089) and may be there is only a
minor issue to finalise this (see [1]).  It might be a sensible strategy
To upgrade to latest pandas upstream to not spent to much time on the
old code - however, I have no idea about compatibility issues of all of
its rdepends.

Kind regards

Andreas.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777089#129

-- 
http://fam-tille.de

Bug#888879: rheolef FTBFS on several architectures: test runs forever

[Andreas Tille]

Hi Pierre,

as I mentioned on Debian Science maintainers list[1] this problem does
not come unexpected.  Pierre, could you please confirm whether you keep
on maintaining this package and will check this issue?

>From my uneducated perspective the test failures always existed but the
test were simply not run before.  Thus a first course of action might be
to ask ftpmaster for removal of those architectures where rheolef does
not build and reduce severity of the bug to say "important".

Please note that I do not have any time resources to work on this
package.

Kind regards

  Andreas.

[1] 
https://lists.alioth.debian.org/pipermail/debian-science-maintainers/2018-January/057544.html

On Tue, Jan 30, 2018 at 10:24:18PM +0200, Adrian Bunk wrote:
> Source: rheolef
> Version: 6.7-5
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=rheolef=sid
> 
> ...
>   mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> left >/dev/null 2>/dev/null
>   mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> left >/dev/null 2>/dev/null
>   mpirun -np 3 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> left >/dev/null 2>/dev/null
>   mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> right >/dev/null 2>/dev/null
>   mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
> right >/dev/null 2>/dev/null
> E: Build killed with signal TERM after 150 minutes of inactivity
> 
> 
> I've reproduced this on i386, two processes are running
> forever (aborted after 6 hours on a fast CPU) with 100% CPU.
> 
> Backtraces:
> 
> Thread 3 (Thread 0xf50ffb40 (LWP 29032)):
> #0  0xf7ed6db9 in __kernel_vsyscall ()
> #1  0xf70fabd3 in __GI___poll (fds=0xf47005d0, nfds=2, timeout=360) at 
> ../sysdeps/unix/sysv/linux/poll.c:29
> #2  0xf5caed4a in poll (__timeout=360, __nfds=2, __fds=0xf47005d0) at 
> /usr/include/i386-linux-gnu/bits/poll2.h:46
> #3  poll_dispatch (base=0x578eb9c0, tv=0xf50f9bfc) at poll.c:165
> #4  0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, 
> flags=) at event.c:1630
> #5  0xf5c6b3bd in progress_engine (obj=0x578eb950) at 
> runtime/opal_progress_threads.c:105
> #6  0xf5df6316 in start_thread (arg=0xf50ffb40) at pthread_create.c:465
> #7  0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
> 
> Thread 2 (Thread 0xf5ac5b40 (LWP 29031)):
> #0  0xf7ed6db9 in __kernel_vsyscall ()
> #1  0xf71053fa in __GI_epoll_pwait (epfd=7, events=0x578ea930, maxevents=32, 
> timeout=-1, set=0x0)
> at ../sysdeps/unix/sysv/linux/epoll_pwait.c:42
> #2  0xf710569a in epoll_wait (epfd=7, events=0x578ea930, maxevents=32, 
> timeout=-1)
> at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
> #3  0xf5ca199a in epoll_dispatch (base=0x578ea7a0, tv=0x0) at epoll.c:407
> #4  0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, 
> flags=) at event.c:1630
> #5  0xf5af23eb in progress_engine (obj=0x578ea7a0) at 
> src/util/progress_threads.c:52
> #6  0xf5df6316 in start_thread (arg=0xf5ac5b40) at pthread_create.c:465
> #7  0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
> 
> Thread 1 (Thread 0xf5b4fe00 (LWP 29002)):
> #0  0xf7ed67f5 in ?? ()
> #1  0xf7ed6b43 in __vdso_clock_gettime ()
> #2  0xf7112961 in __GI___clock_gettime (clock_id=1, tp=0xffb74194) at 
> ../sysdeps/unix/clock_gettime.c:115
> #3  0xf5cc3297 in opal_timer_linux_get_usec_clock_gettime () at 
> timer_linux_component.c:197
> #4  0xf5c669c3 in opal_progress () at runtime/opal_progress.c:197
> #5  0xf74b5e05 in sync_wait_st (sync=) at 
> ../opal/threads/wait_sync.h:80
> #6  ompi_request_default_wait_all (count=2, requests=0xffb742e4, 
> statuses=0x0) at request/req_wait.c:221
> #7  0xf750640d in ompi_coll_base_allreduce_intra_recursivedoubling 
> (sbuf=0x57951030, rbuf=0x57a9b400, count=2, 
> dtype=0xf7565140 , op=0xf7573e60 , 
> comm=0xf7569520 , 
> module=0x57976fa0) at base/coll_base_allreduce.c:225
> #8  0xe991f640 in ompi_coll_tuned_allreduce_intra_dec_fixed (sbuf=0x57951030, 
> rbuf=0x57a9b400, count=2, 
> dtype=0xf7565140 , op=0xf7573e60 , 
> comm=0xf7569520 , 
> module=0x57976fa0) at coll_tuned_decision_fixed.c:66
> #9  0xf74c5b77 in PMPI_Allreduce (sendbuf=0x57951030, recvbuf=0x57a9b400, 
> count=2, 
> datatype=0xf7565140 , op=0xf7573e60 , 
> comm=0xf7569520 )
> at pallreduce.c:107
> #10 0xf7b476cf in boost::mpi::detail::all_reduce_impl std::plus > (comm=..., 
> in_values=0x57951030, n=n@entry=2, out_values=0x57a9b400) at 
> /usr/include/boost/mpi/collectives/all_reduce.hpp:36
> #11 0xf7b58fc0 in boost::mpi::all_reduce int> > (out_values=, n=2, 
> in_values=, comm=..., op=...) at 
> /usr/include/boost/mpi/collectives/all_reduce.hpp:93
> #12 rheolef::mpi_assembly_begin > >, rheolef::disarray_rep rheolef::distributed, std::allocator >::message_type, 
> 

Bug#889719: python-yowsup-common: Missing Breaks+Replaces on python-yowsup (<< 2.5.7-1~)

[Adrian Bunk]

Package: python-yowsup-common
Version: 2.5.7-2
Severity: serious

Unpacking python-yowsup-common (2.5.7-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-SUZNpz/32-python-yowsup-common_2.5.7-2_all.deb (--unpack):
 trying to overwrite '/usr/share/yowsup/common/mime.types/mime.types', which is 
also in package python-yowsup 2.5.0~git20160904.d69c1ff-1

Processed: Add affects on the src:

[Debian Bug Tracking System]

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

> affects 889710 src:arch-test
Bug #889710 [binutils-mingw-w64-i686] arch-test FTBFS: i686-w64-mingw32-ld: 
cannot find -lkernel32
Added indication that 889710 affects src:arch-test
> thanks
Stopping processing here.

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

Bug#889698: nss 3.35 now defaults to SQL database, broke certmonger/mod_nss/dogtag/freeipa

[Timo Aaltonen]

On 06.02.2018 10:33, Mike Hommey wrote:
> On Tue, Feb 06, 2018 at 09:16:05AM +0200, Timo Aaltonen wrote:
>> Package: nss
>> Severity: grave
>>
>> Hi, please revert this commit which switched the default certificate 
>> database format to SQL:
>>
>> https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3
>>
>> Several packages are not ready for it yet, including but likely not limited 
>> to:
>>
>> certmonger
>> libapache2-mod-nss
>> dogtag-pki
>> freeipa
>>
>> respective upstreams are working on it but getting everything merged will 
>> take a month or two.
> 
> Can you be more specific in how this affects those packages? Because
> AFAIR, this is supposed to kind of be transparent.

For example it changes how certutil is run, which would now need a
'dbm:'(?) prefix when accessing an old DB like when setting up Freeipa
as shown here:

https://bugs.launchpad.net/bugs/1746947

and it also breaks an installed Dogtag instance though I don't know how
exactly:

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

these all use an internal cert DB.

-- 
t

Processed: retitle 889710 to arch-test FTBFS: i686-w64-mingw32-ld: cannot find -lkernel32 ..., affects 889710 ...

[Debian Bug Tracking System]

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

> retitle 889710 arch-test FTBFS: i686-w64-mingw32-ld: cannot find -lkernel32
Bug #889710 [src:arch-test] arch-test FTBFS: i686-w64-mingw32-ld: cannot find
Changed Bug title to 'arch-test FTBFS: i686-w64-mingw32-ld: cannot find 
-lkernel32' from 'arch-test FTBFS: i686-w64-mingw32-ld: cannot find'.
> reassign 889710 binutils-mingw-w64-i686
Bug #889710 [src:arch-test] arch-test FTBFS: i686-w64-mingw32-ld: cannot find 
-lkernel32
Bug reassigned from package 'src:arch-test' to 'binutils-mingw-w64-i686'.
No longer marked as found in versions arch-test/0.9-1.
Ignoring request to alter fixed versions of bug #889710 to the same values 
previously set
> affects 889710 arch-test
Bug #889710 [binutils-mingw-w64-i686] arch-test FTBFS: i686-w64-mingw32-ld: 
cannot find -lkernel32
Added indication that 889710 affects arch-test
> found 889710 2.29.1-13+8
Bug #889710 [binutils-mingw-w64-i686] arch-test FTBFS: i686-w64-mingw32-ld: 
cannot find -lkernel32
Marked as found in versions binutils-mingw-w64/8.
> thanks
Stopping processing here.

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

Processed: Re: Bug#889710: arch-test FTBFS: x86_64-w64-mingw32-ld: cannot find -lkernel32

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 arch-test FTBFS: i686-w64-mingw32-ld: cannot find
Bug #889710 [src:arch-test] arch-test FTBFS: x86_64-w64-mingw32-ld: cannot find 
-lkernel32
Changed Bug title to 'arch-test FTBFS: i686-w64-mingw32-ld: cannot find' from 
'arch-test FTBFS: x86_64-w64-mingw32-ld: cannot find -lkernel32'.

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

Bug#889710: arch-test FTBFS: x86_64-w64-mingw32-ld: cannot find -lkernel32

[Stephen Kitt]

Control: retitle -1 arch-test FTBFS: i686-w64-mingw32-ld: cannot find 
-lkernel32

Control: reassign -1 binutils-mingw-w64-i686
Control: affects -1 arch-test

Hi Adrian,

Le 06/02/2018 09:25, Adrian Bunk a écrit :

Some recent change in unstable makes arch-test FTBFS:

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

This might be a regression somewhere in the MinGW packages,
maintainer is Cc'ed.


Thanks for the report, this is indeed a recent regression in binutils 
(2.29.1-10 works, 2.29.1-13 doesn’t). I should use arch-test as an 
autopkgtest...


Regards,

Stephen

Bug#885818: marked as done (alltray: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 09:19:42 +
with message-id 
and subject line Bug#885818: fixed in alltray 0.71b-1.1
has caused the Debian Bug report #885818,
regarding alltray: Depends on gconf
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.)


-- 
885818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alltray
Version: 0.71b-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: alltray
Source-Version: 0.71b-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated alltray package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Jan 2018 10:27:47 +0200
Source: alltray
Binary: alltray
Architecture: source
Version: 0.71b-1.1
Distribution: unstable
Urgency: low
Maintainer: Ignace Mouzannar 
Changed-By: Adrian Bunk 
Description:
 alltray- Dock any program into the system tray
Closes: 885818
Changes:
 alltray (0.71b-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Disable gconf support. (Closes: #885818)
Checksums-Sha1:
 ddde4af1d8a6bb7f2ee3102a5298d1811bec0a7b 1903 alltray_0.71b-1.1.dsc
 f0ecc0211ac7cbcd933b06be192e6a61589086bd 4320 alltray_0.71b-1.1.debian.tar.xz
Checksums-Sha256:
 a18e3e4430083eb19e8746767a9d2835a0bcbe77181783bc55d29667211536ca 1903 
alltray_0.71b-1.1.dsc
 230aebdd8ca5d23b6f3d26c0282e1984d07815fcd96849c233262e933b03509c 4320 
alltray_0.71b-1.1.debian.tar.xz
Files:
 cdf4e66c32d898e1dcf31a78825f8453 1903 x11 optional alltray_0.71b-1.1.dsc
 e5a3088a183a87201785cd1ad9c39012 4320 x11 optional 
alltray_0.71b-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlpsOHEACgkQiNJCh6LY
mLHlEA/+IODPJicFVmmn52H672r64+/D3Qm2a+/+Y2gW4PkudTpsXt/Ra57Ug8l6
6UhsKQyskGzap4hCq/9ZYPvLYfW1Rf+fuEvcAMTGwhXJ5fFReLiTn5FdBunifcl/
zxI/DG/6Md89e4n9mT3V4kHgQFNmxI7lgSAy1PmFdoS9SmkIMHbe7uQ6YRs3Mps0
XsecRujzTg0WVPbFvtKqkYV2GJRbery3J8XdKfiXu1lpUrcvq0rPnvkALBkJAFuj
SWY/Ce5e0rnDP1ShO0MHGLQePn3SD6SuBd/yTCzQI6ImXQ/sERtR9lkyY8IUjAe/
3qNr/DpaLl5k5UvRjMc7GswksLfLsMjS24ZyMffivUnT2dv4qCNxVET9vqwqxvjE
NleiknIWNSa029gog2buvZ2eb/EdwiOcpPYOgQeIibD6AChArPjN+ZMHL2Ee31Tv
LzpQiIwyqv+a7ZUk8bI9Yofa52fkzgE58Oy33hSRkyhgRoyBFTpahi4yLzjTyTac
5UvM8iHpf/7igyB65xklROwnozrMONxaHnE7/dgq8g8v5uYpoeJ9xntUui0Xyo0e
gvN5VJwEbqUk+Knu2pLNA2rz5Ir0slL3+Xz9XdiF1VAkNAV9jOKGYRYrFdTVGwaz
aQ4pjogs1hoaZxBHgnc96edjaO/KwdrZi5tSmB6Kfcn38hy7jHE=
=cNaH
-END PGP SIGNATURE End Message ---

Bug#889712: adblock-plus: adblockplus deprecated, replaced by adblockpluschrome

[Andreas Tille]

Source: adblock-plus
Version: 2.9.1+dfsg-1
Severity: grave
Justification: renders package unusable

Hi,

since firefox 57 adblock-plus does not work any more.  Upstream page[1]
says:

  This codebase is deprecated, it will not work with Firefox 57 and
  above. As of Adblock Plus 3.0, Adblock Plus for Firefox is based on the
  adblockpluschrome repository[2].

I tried to build adblockpluschrome using the current packaging code adapted
to the new version but my build attempt failed with

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/adblock-plus-3.0.2'
TZ=UTC python build.py build --release
Traceback (most recent call last):
  File "build.py", line 10, in 
import buildtools.build
ImportError: No module named buildtools.build
debian/rules:7: recipe for target 'override_dh_auto_build' failed
...

I have not done much besides adapting the watch file, removing most of
the quilt patches since patches files vanished and adapting patch
0004-Drop-dependency-check.patch by refreshing.  If you want me to
commit this in some branch to save you a minimum of work I can do so.

I have no idea how to proceed with the lacking Python module (may this
one[3] ??) - there might be a chance to do without this.  If you need
help and think [3] is essential I would volunteer to package this to
help steping forward with this issue.

Kind regards

 Andreas.

[1] https://github.com/adblockplus/adblockplus
[2] https://github.com/adblockplus/adblockpluschrome
[3] https://pypi.python.org/pypi/buildtools

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 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

Bug#882023: marked as done (php-stomp FTBFS with PHP 7.1)

[Debian Bug Tracking System]

Your message dated Tue, 6 Feb 2018 09:43:19 +0100
with message-id <351ce95d-33c4-41b0-b45c-9c3a6db71...@sury.org>
and subject line Re: [Pkg-php-pecl] Bug#882023: php-stomp 2.0.1 does support 
PHP 7.1
has caused the Debian Bug report #882023,
regarding php-stomp FTBFS with PHP 7.1
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.)


-- 
882023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-stomp
Version: 2.0.0+1.0.9-1
Severity: serious
Tags: buster sid

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

...
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c: In function 
'zif_stomp_read_frame':
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:966:9: error: 
'zend_fcall_info {aka struct _zend_fcall_info}' has no member named 
'function_table'; did you mean 'function_name'?
 fci.function_table = >function_table;
 ^~
 function_name
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:967:8: error: 
'zend_fcall_info {aka struct _zend_fcall_info}' has no member named 
'symbol_table'
 fci.symbol_table = NULL;
^
In file included from /usr/include/php/20160303/Zend/zend_globals.h:28:0,
 from /usr/include/php/20160303/Zend/zend_compile.h:688,
 from /usr/include/php/20160303/Zend/zend_modules.h:26,
 from /usr/include/php/20160303/Zend/zend_API.h:27,
 from /usr/include/php/20160303/main/php.h:40,
 from /build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:25:
/usr/include/php/20160303/Zend/zend_globals_macros.h:46:33: error: 
'zend_executor_globals {aka struct _zend_executor_globals}' has no member named 
'scope'
 # define EG(v) (executor_globals.v)
 ^
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:983:25: note: in 
expansion of macro 'EG'
 fcc.calling_scope = EG(scope);
 ^~
Makefile:195: recipe for target 'php_stomp.lo' failed
make[2]: *** [php_stomp.lo] Error 1
--- End Message ---
--- Begin Message ---
Version: 2.0.1+1.0.9-2

I have uploaded a fixed version, but didn’t add the bug number to the changelog.

Ondrej
--
Ondřej Surý
ond...@sury.org



> On 16 Dec 2017, at 15:29, Adrian Bunk  wrote:
> 
> Control: tags -1 fixed-upstream
> 
> php-stomp 2.0.1 does support PHP 7.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
> 
> ___
> Pkg-php-pecl mailing list
> pkg-php-p...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-pecl--- End Message ---

Bug#889689: marked as done (pytest-arraydiff: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 6 Feb 2018 09:37:48 +0100
with message-id <64a60b60-96f8-a76d-9ac6-8f8b3d65b...@debian.org>
and subject line Re: Bug#889689: pytest-arraydiff: Incomplete debian/copyright?
has caused the Debian Bug report #889689,
regarding pytest-arraydiff: Incomplete debian/copyright?
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.)


-- 
889689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-arraydiff
Version: 0.2-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Ole Streicher 

Hi,

I just ACCEPTed pytest-arraydiff from NEW but noticed it was missing 
attribution in debian/copyright for at least src/jsonrpc-version-macros.h.

(This is not 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
   `-
--- End Message ---
--- Begin Message ---
Hi Chris,

On 06.02.2018 09:35, Chris Lamb wrote:
> Hi Ole,
>> Hmm, there is no file src/jsonrpc-version-macros.h in the
>> pytest-arraydiff source
> 
> Odd. :/  Please re-upload and ping me via email when it hits NEW
> again. Sorry about this. 

No need; you accepted it. That was just the RC bug you filed afterwards.
I'll take the freedom to close it then.

Best

Ole--- End Message ---

Bug#889689: pytest-arraydiff: Incomplete debian/copyright?

[Chris Lamb]

Hi Ole,
> Hmm, there is no file src/jsonrpc-version-macros.h in the
> pytest-arraydiff source

Odd. :/  Please re-upload and ping me via email when it hits NEW
again. Sorry about this. 


Best wishes,

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

Bug#889698: nss 3.35 now defaults to SQL database, broke certmonger/mod_nss/dogtag/freeipa

[Mike Hommey]

On Tue, Feb 06, 2018 at 09:16:05AM +0200, Timo Aaltonen wrote:
> Package: nss
> Severity: grave
> 
> Hi, please revert this commit which switched the default certificate database 
> format to SQL:
> 
> https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3
> 
> Several packages are not ready for it yet, including but likely not limited 
> to:
> 
> certmonger
> libapache2-mod-nss
> dogtag-pki
> freeipa
> 
> respective upstreams are working on it but getting everything merged will 
> take a month or two.

Can you be more specific in how this affects those packages? Because
AFAIR, this is supposed to kind of be transparent.

Mike

Bug#889710: arch-test FTBFS: x86_64-w64-mingw32-ld: cannot find -lkernel32

[Adrian Bunk]

Source: arch-test
Version: 0.9-1
Severity: serious

Some recent change in unstable makes arch-test FTBFS:

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

...
   dh_auto_build
make -j15
make[1]: Entering directory '/build/1st/arch-test-0.9'
x86_64-linux-gnu-as --64 amd64.s -o amd64.o
x86_64-linux-gnu-as --x32 x32.s -o x32.o
x86_64-linux-gnu-as --32 i386.s -o i386.o
i686-w64-mingw32-as win32.s -o win32.o
x86_64-w64-mingw32-as win64.s -o win64.o
mips-linux-gnu-as -32 -EB mips.s -o mips.o
mips-linux-gnu-as -32 -EL mips.s -o mipsel.o
mips-linux-gnu-as -n32 -EB mipsn32.s -o mipsn32.o
mips-linux-gnu-as -n32 -EL mipsn32.s -o mipsn32el.o
mips-linux-gnu-as -64 -EB mips64.s -o mips64.o
mips-linux-gnu-as -64 -EL mips64.s -o mips64el.o
x86_64-linux-gnu-as --64 solaris-amd64.s -o illumos-amd64.o
x86_64-linux-gnu-as --64 solaris-amd64.s -o kfreebsd-amd64.o
x86_64-linux-gnu-as --32 kfreebsd-i386.s -o kfreebsd-i386.o
powerpc-linux-gnu-as -a32 powerpc.s -o powerpc.o
i686-w64-mingw32-ld -s win32.o -lkernel32 -o arch-test-win32
x86_64-w64-mingw32-ld -s win64.o -lkernel32 -o arch-test-win64
x86_64-linux-gnu-ld -melf_x86_64 -s kfreebsd-amd64.o -o arch-test-kfreebsd-amd64
i686-w64-mingw32-ld: cannot find -lkernel32
mips-linux-gnu-ld -melf32btsmip -s mips.o -o arch-test-mips
Makefile:56: recipe for target 'arch-test-win32' failed
make[1]: *** [arch-test-win32] Error 1
make[1]: *** Waiting for unfinished jobs
x86_64-linux-gnu-ld -melf_x86_64 -s amd64.o -o arch-test-amd64
x86_64-linux-gnu-ld -melf32_x86_64 -s x32.o -o arch-test-x32
mips-linux-gnu-ld -melf32btsmipn32 -s mipsn32.o -o arch-test-mipsn32
mips-linux-gnu-ld -melf64btsmip -s mips64.o -o arch-test-mips64
mips-linux-gnu-ld -melf32ltsmip -s mipsel.o -o arch-test-mipsel
mips-linux-gnu-ld -melf32ltsmipn32 -s mipsn32el.o -o arch-test-mipsn32el
x86_64-linux-gnu-ld -melf_x86_64 -s illumos-amd64.o -o arch-test-illumos-amd64
x86_64-w64-mingw32-ld: cannot find -lkernel32


This might be a regression somewhere in the MinGW packages,
maintainer is Cc'ed.

Bug#889707: golang-gopkg-macaroon-bakery.v2 FTBFS: cannot find package "github.com/juju/schema"

[Adrian Bunk]

Source: golang-gopkg-macaroon-bakery.v2
Version: 0.0~git20171221.21d9e9a-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-gopkg-macaroon-bakery.v2=all=0.0~git20171221.21d9e9a-3=1517898861=0

...
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-gopkg-macaroon-bakery.v2-0.0\~git20171221.21d9e9a/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-gopkg-macaroon-bakery.v2-0.0\~git20171221.21d9e9a/obj-x86_64-linux-gnu/src\"
 -v -p 4 gopkg.in/macaroon-bakery.v2/bakery 
gopkg.in/macaroon-bakery.v2/bakery/checkers 
gopkg.in/macaroon-bakery.v2/bakery/identchecker 
gopkg.in/macaroon-bakery.v2/bakery/internal/macaroonpb 
gopkg.in/macaroon-bakery.v2/bakery/mgorootkeystore 
gopkg.in/macaroon-bakery.v2/bakerytest gopkg.in/macaroon-bakery.v2/httpbakery 
gopkg.in/macaroon-bakery.v2/httpbakery/agent 
gopkg.in/macaroon-bakery.v2/httpbakery/form 
gopkg.in/macaroon-bakery.v2/internal/httputil
src/gopkg.in/juju/environschema.v1/fields.go:14:2: cannot find package 
"github.com/juju/schema" in any of:
/usr/lib/go-1.9/src/github.com/juju/schema (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/juju/schema (from 
$GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-gopkg-macaroon-bakery.v2-0.0\~git20171221.21d9e9a/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-gopkg-macaroon-bakery.v2-0.0\~git20171221.21d9e9a/obj-x86_64-linux-gnu/src\"
 -v -p 4 gopkg.in/macaroon-bakery.v2/bakery 
gopkg.in/macaroon-bakery.v2/bakery/checkers 
gopkg.in/macaroon-bakery.v2/bakery/identchecker 
gopkg.in/macaroon-bakery.v2/bakery/internal/macaroonpb 
gopkg.in/macaroon-bakery.v2/bakery/mgorootkeystore 
gopkg.in/macaroon-bakery.v2/bakerytest gopkg.in/macaroon-bakery.v2/httpbakery 
gopkg.in/macaroon-bakery.v2/httpbakery/agent 
gopkg.in/macaroon-bakery.v2/httpbakery/form 
gopkg.in/macaroon-bakery.v2/internal/httputil returned exit code 1
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1

Bug#889704: runc FTBFS: kill.go:44:12: undefined: unix.SIGUNUSED

[Adrian Bunk]

Source: runc
Version: 1.0.0~rc4+dfsg1-5
Severity: serious

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

...
github.com/urfave/cli
github.com/opencontainers/runc
# github.com/opencontainers/runc
src/github.com/opencontainers/runc/kill.go:44:12: undefined: unix.SIGUNUSED
github.com/opencontainers/runc/contrib/cmd/recvtty
github.com/opencontainers/runc/libcontainer/devices
github.com/opencontainers/runc/libcontainer/integration
github.com/opencontainers/runc/libcontainer/xattr
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/<>/runc-1.0.0\~rc4\+dfsg1/_build/src\" 
-asmflags=\"-trimpath=/<>/runc-1.0.0\~rc4\+dfsg1/_build/src\" -v -p 1 
-tags "apparmor seccomp" github.com/opencontainers/runc 
github.com/opencontainers/runc/contrib/cmd/recvtty 
github.com/opencontainers/runc/libcontainer 
github.com/opencontainers/runc/libcontainer/apparmor 
github.com/opencontainers/runc/libcontainer/cgroups 
github.com/opencontainers/runc/libcontainer/cgroups/fs 
github.com/opencontainers/runc/libcontainer/cgroups/rootless 
github.com/opencontainers/runc/libcontainer/cgroups/systemd 
github.com/opencontainers/runc/libcontainer/configs 
github.com/opencontainers/runc/libcontainer/configs/validate 
github.com/opencontainers/runc/libcontainer/criurpc 
github.com/opencontainers/runc/libcontainer/devices 
github.com/opencontainers/runc/libcontainer/integration 
github.com/opencontainers/runc/libcontainer/keys 
github.com/opencontainers/runc/libcontainer/nsenter gi
 thub.com/opencontainers/runc/libcontainer/seccomp 
github.com/opencontainers/runc/libcontainer/specconv 
github.com/opencontainers/runc/libcontainer/stacktrace 
github.com/opencontainers/runc/libcontainer/system 
github.com/opencontainers/runc/libcontainer/user 
github.com/opencontainers/runc/libcontainer/utils 
github.com/opencontainers/runc/libcontainer/xattr returned exit code 2
debian/rules:36: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Bug#889705: golang-gopkg-juju-environschema.v1 FTBFS: cannot find package "github.com/juju/schema"

[Adrian Bunk]

Source: golang-gopkg-juju-environschema.v1
Version: 0.0~git20151104.7359fc7-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-gopkg-juju-environschema.v1=all=0.0~git20151104.7359fc7-3=1517898791=0

...
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-gopkg-juju-environschema.v1-0.0\~git20151104.7359fc7/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-gopkg-juju-environschema.v1-0.0\~git20151104.7359fc7/obj-x86_64-linux-gnu/src\"
 -v -p 4 gopkg.in/juju/environschema.v1 gopkg.in/juju/environschema.v1/form
src/gopkg.in/juju/environschema.v1/fields.go:14:2: cannot find package 
"github.com/juju/schema" in any of:
/usr/lib/go-1.9/src/github.com/juju/schema (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/juju/schema (from 
$GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-gopkg-juju-environschema.v1-0.0\~git20151104.7359fc7/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-gopkg-juju-environschema.v1-0.0\~git20151104.7359fc7/obj-x86_64-linux-gnu/src\"
 -v -p 4 gopkg.in/juju/environschema.v1 gopkg.in/juju/environschema.v1/form 
returned exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1

Bug#889703: praat FTBFS on 64bit big endian: test failures

[Adrian Bunk]

Source: praat
Version: 6.0.37-1
Severity: serious

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

...
104 tests passed, 102 ok
Failed test(s):

test_SpeechSynthesizer.praat
test_bss_twoSoundsMixed.praat
debian/rules:90: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889702: reptyr FTBFS: test failure

[Adrian Bunk]

Source: reptyr
Version: 0.6.2-1.1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
if ! [ -f /dev/tty0 ]; \
then echo disable tests; \
else dh_auto_test; \
fi
disable tests
if ! [ -f /proc/sys/kernel/yama/ptrace_scope ] || \
  [ "$(cat /proc/sys/kernel/yama/ptrace_scope)" = 0 ]; then \
  dh_auto_test; \
fi \

make -j4 test
make[2]: Entering directory '/<>'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror -D_GNU_SOURCE -g -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o test/victim.o test/victim.c
cc -Wl,-z,relro -Wl,-z,now  test/victim.o   -o test/victim
python test/basic.py
Traceback (most recent call last):
  File "test/basic.py", line 10, in 
reptyr.expect("ECHO: world")
  File "/usr/lib/python2.7/dist-packages/pexpect/spawnbase.py", line 321, in 
expect
timeout, searchwindowsize, async)
  File "/usr/lib/python2.7/dist-packages/pexpect/spawnbase.py", line 345, in 
expect_list
return exp.expect_loop(timeout)
  File "/usr/lib/python2.7/dist-packages/pexpect/expect.py", line 105, in 
expect_loop
return self.eof(e)
  File "/usr/lib/python2.7/dist-packages/pexpect/expect.py", line 50, in eof
raise EOF(msg)
pexpect.exceptions.EOF: End Of File (EOF). Exception style platform.

command: ./reptyr
args: ['./reptyr', '30493']
buffer (last 100 chars): ''
before (last 100 chars): 'd stop.\r\n[-] Unable to stat /dev/console\r\nUnable 
to attach to pid 30493: No such file or directory\r\n'
after: 
match: None
match_index: None
exitstatus: 1
flag_eof: True
pid: 30494
child_fd: 6
closed: False
timeout: 30
delimiter: 
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile("ECHO: world")
Makefile:23: recipe for target 'test' failed
make[2]: *** [test] Error 1