Bug#898593: xpn: Intent to remove from Debian

[David Paleino]

Please go ahead.

Thank you,
David


Il Lun 14 Mag 2018, 02:39 Jeremy Bicha  ha scritto:

> Source: xpn
> Version: 1.2.6-5.1
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs pygtk
> Tags: sid buster
>
> xpn depends on the unmaintained pygtk which the Debian GNOME team is
> trying to remove from Debian.
>
> It looks like xpn itself is unmaintained. Therefore, I intend to file a
> removal bug for xpn. Please reply immediately to let me know if you approve
> or object.
>
> References
> --
> https://bugs.debian.org/885496
> https://lists.debian.org/debian-devel/2018/02/msg00169.html
>
> Thanks,
> Jeremy Bicha
>

Bug#886065: Bug#732011: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

[Willem van den Akker]

hi Jeremy,,

Yes I am converting it to Gsettings.
Gtk3 not yet on my prio-list.

Greetings,
Willem

On Sun, 2018-05-13 at 21:18 -0400, Jeremy Bicha wrote:
> Willem, gyrus was removed from Debian Testing 3 months ago because it
> depends on gconf.
> 
> It has also been abandoned upstream.
> 
> Do you intend to at least port it away from gconf?
> 
> It would be helpful if you ported it to gtk3 also.
> 
> Otherwise, I think it would be better if we remove gyrus from Debian
> Unstable too.
> 
> References
> ---
> https://bugs.debian.org/886065
> https://git.gnome.org/browse/archive/gyrus/log/
> 
> Thanks,
> Jeremy Bicha
> 

Bug#886065: Bug#732011: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

[Willem van den Akker]

hi Jeremy,,

Yes I am converting it to Gsettings.
Gtk3 not yet on my prio-list.

Greetings,
Willem

On Sun, 2018-05-13 at 21:18 -0400, Jeremy Bicha wrote:
> > Willem, gyrus was removed from Debian Testing 3 months ago because
> > it
> > depends on gconf.
> > 
> > It has also been abandoned upstream.
> > 
> > Do you intend to at least port it away from gconf?
> > 
> > It would be helpful if you ported it to gtk3 also.
> > 
> > Otherwise, I think it would be better if we remove gyrus from
> > Debian
> > Unstable too.
> > 
> > References
> > ---
> > https://bugs.debian.org/886065
> > https://git.gnome.org/browse/archive/gyrus/log/
> > 
> > Thanks,
> > Jeremy Bicha
> > 

Bug#886382: fixed in amd64-microcode 3.20171205.1

[Henrique de Moraes Holschuh]

On Sun, 13 May 2018, Andreas Ziegler wrote:
> this bug's severity is marked "grave" but the changes haven't been
> backported to stable or oldstable yet.
> 
> Is there a valid reason?

Sure.  Nobody ever tell us it worked, so we don't fasttrack, which means
it will wait at *least* a couple months.

Now, if people tested this specific update on 0x800f12 processors (AMD
EPYC processors), and someone remembers to report to me that it works
well, I will do the backport.

> >* New microcode updates (closes: #886382):
> >  sig 0x00800f12, patch id 0x08001213, 2017-12-05
> >  Thanks to SuSE for distributing these ahead of AMD's official release!

Especially because we got the microcode update from some other source
than linux-firmware (where AMD deploys their microcode updates)...

-- 
  Henrique Holschuh

Bug#898598: jack-mixer: Depends on gconf

[Jeremy Bicha]

Source: jack-mixer
Version: 10-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 )

Please try to port your package away from gconf. Otherwise, please consider 
requesting that your package be removed from Debian to help us complete this 
goal.

Please note that jack-mixer has other important bugs for deprecated 
dependencies that we are trying to remove.

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html
https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#886065: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

[Jeremy Bicha]

Willem, gyrus was removed from Debian Testing 3 months ago because it
depends on gconf.

It has also been abandoned upstream.

Do you intend to at least port it away from gconf?

It would be helpful if you ported it to gtk3 also.

Otherwise, I think it would be better if we remove gyrus from Debian
Unstable too.

References
---
https://bugs.debian.org/886065
https://git.gnome.org/browse/archive/gyrus/log/

Thanks,
Jeremy Bicha

Bug#898593: xpn: Intent to remove from Debian

[Jeremy Bicha]

Source: xpn
Version: 1.2.6-5.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

xpn depends on the unmaintained pygtk which the Debian GNOME team is trying to 
remove from Debian.

It looks like xpn itself is unmaintained. Therefore, I intend to file a removal 
bug for xpn. Please reply immediately to let me know if you approve or object.

References
--
https://bugs.debian.org/885496
https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha

Processed: Re: Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #869191 [pristine-tar] pristine-tar: pristine-xz failed to reproduce build 
of ../util-linux_2.30.1.orig.tar.xz
Severity set to 'important' from 'grave'

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

Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

[Antonio Terceiro]

Control: severity -1 important

On Sun, May 13, 2018 at 03:00:44PM +0200, Alf Gaida wrote:
> Control: severity -1 grave
> 
> can confirm that the patch work fine.

sure, thanks for testing. I have applied the patch to the git
repository, and it will be available in the next upload.

However this has no influence over the severity of this bug.


signature.asc
Description: PGP signature

Bug#898591: lptools: Intent to remove from Debian

[Jeremy Bicha]

Source: lptools
Version: 0.2.0-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster
X-Debbugs-CC: x...@debian.org, jel...@debian.org

lptools depends on the unmaintained pygtk which the Debian GNOME team is trying 
to remove from Debian.

It looks like lptools itself is unmaintained. Therefore, I intend to file a 
removal bug for lptools. Please reply immediately to let me know if you approve 
or object.

References
--
https://bugs.debian.org/885518
https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha

Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

[Alf Gaida]

Only a remark - i'm not interested in severeties of bugs. But xz is a
common compression format - and one of the favoured in debian iirc. So
if a tool break the workflow for a common compression format i would see
this as serious or grave, what ever make it unfit for release and is a
RC bug. ymmv.

Anyways - i would like a "out of the box" working pristine-tar instead
of a surprise when trying to add upstream tarballs to the pristine-tar
branch. If setting the severety to important helps to speed up things
why not.

Cheers Alf



signature.asc
Description: OpenPGP digital signature

Bug#898589: yorick-yao: Intent to remove from Debian

[Jeremy Bicha]

Source: yorick-yao
Version: 5.4.0-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

yorick-yao depends on the unmaintained pygtk which the Debian GNOME team is 
trying to remove from Debian.

It looks like yorick-yao itself is unmaintained. Therefore, I intend to file a 
removal bug for yorick-yao. Please reply immediately to let me know if you 
approve or object.

References
--
https://bugs.debian.org/885506
https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha

Bug#896071: debootstrap fails to retrive Release file over https

[Philipp Kern]

Hideki,

On 4/24/18 3:29 PM, Raphael Hertzog wrote:
> On Mon, 23 Apr 2018, Hideki Yamane wrote:
>> On Sun, 22 Apr 2018 09:40:54 +1000
>> David Margerison  wrote:
  "$@" is extracted as '' and wget tries to fetch it and fails,
  then returns 1.
>>>
>>> Regarding the proposed fix, in general using $@ without quotes is fragile.
>>
>>  Most of the case, quotes is better. But in this case, "$@" is extracted like
 wget '' '' '' https://deb.debian.org/debian/dist/unstable/InRelease
>>  Then, it outputs
http://: Invalid host name.
http://: Invalid host name.
http://: Invalid host name.
>>  and returns 1.
> 
> I agree with David that using $@ without quotes is not a good idea.
> What you want is to not pass empty arguments to wgetprogress. So you should
> likely drop the quotes around the first 3 parameters on this line:
> if wgetprogress "$CHECKCERTIF" "$CERTIFICATE" "$PRIVATEKEY" 
> -O "$dest" "$from"; then
> 
> I'm suggesting only the first 3 since those are the variables that can be
> empty. And we want to keep the quote on "$dest" to be able to use path
> containing spaces (which you likely lost with your fix).
> 
> But even here it's not perfect since we loose the possibility to handle
> arguments containing spaces in the first 3 parameters. A complete fix would
> involve setting up the argument list manually:
> 
> set -- -O "$dest" "$from"
> if [ -n "$PRIVATEKEY" ]; then
> set -- "$PRIVATEKEY" "$@"
> fi
> if [ -n "$CERTIFICATE" ]; then
> set -- "$CERTIFICATE" "$@"
> fi
> if [ -n "$CHECKCERTIF" ]; then
> set -- "$CHECKCERTIF" "$@"
> fi
> if wgetprogress "$@"; then
> [...]
> 
> Here we should be safe even if those 3 variables do contain spaces.

any new about incorporating Raphael's suggestion? There's still a grave
bug opened against debootstrap right now (on a version that is in testing).

Kind regards and thanks
Philipp Kern

Bug#897975: [gdm3] Same here, more info

[rastersoft]

Package: gdm3
Version: 3.28.1-1

I have this same problem since about ten days. This weekend I decided to 
do a clean install and found that I was unable: I deleted the system 
partition, booted an USB with debian netinst version, installed stable 
with just gnome shell, and everything worked fine. After updating to 
SID, it broke and GDM didn't show.


I retried several times, but always had the same result.

I tried to install Ubuntu 18.04, and everything worked fine.

Suspecting a hardware problem I tried to install a Windows 10 and did 
some hardware checks, but everything worked. I took the opportunity of 
checking my SSD disk and updated the firmware, just in case.


Installed again Debian from scratch, but had the same result than 
before: stable worked, SID didn't work.


Installed again Debian from scratch but update to SID without installing 
the AMD microcode for my ATI graphics card... The same result.


Installed again Debian from scratch but updated to SID without 
installing the Intel microcode for my Intel i5-4440 cpu... the same result.


Tried to remove the ATI card and use only the integrated Intel graphic 
card... again the same result (both with and without the intel 
microcode): when installing the stable from scratch, all worked fine; 
after updating to SID, GDM failed.


Changed the power supply just in case... the same result.

Here comes the interesting bit: tried to do the installation from 
scratch in a "classic" hard disk (magnetic hard disk, with plates and 
heads) and everything worked fine.


Tried again installing only in the SSD (without connecting the classic 
hard disk) and GDM failed again.


Installed again from scratch in the magnetic hard disk, without the SSD 
connected, and again it worked.


Booted again from the SSD, removed the files 
"/var/lib/gmd3/.ICEAuthority*", restarted GDM, and it worked.


Maybe there is some kind of race condition due to a too fast boot?


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

Debian Release: buster/sid
500 unstable ftp.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-===
libaccountsservice0 (>= 0.6.37) | 0.6.45-1
libaudit1 (>= 1:2.2.1) | 1:2.8.3-1
libc6 (>= 2.14) | 2.27-3
libcanberra-gtk3-0 (>= 0.25) | 0.30-6
libcanberra0 (>= 0.2) | 0.30-6
libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.36.11-2
libgdm1 (= 3.28.1-1) | 3.28.1-1
libglib2.0-0 (>= 2.39.4) | 2.56.1-2
libgtk-3-0 (>= 3.0.0) | 3.22.30-1
libkeyutils1 (>= 1.5.9) | 1.5.9-9.2
libpam0g (>= 0.99.7.1) | 1.1.8-3.7
libselinux1 (>= 1.32) | 2.7-2+b2
libsystemd0 | 238-4
libwrap0 (>= 7.6-4~) | 7.6.q-27
libx11-6 | 2:1.6.5-1
libxau6 | 1:1.0.8-1+b2
libxcb1 | 1.13-1
libxdmcp6 | 1:1.1.2-3
debconf (>= 0.5) | 1.5.66
OR debconf-2.0 |
gir1.2-gdm-1.0 (= 3.28.1-1) | 3.28.1-1
adduser | 3.117
libpam-modules (>= 0.72-1) | 1.1.8-3.7
libpam-runtime (>= 0.76-13.1) | 1.1.8-3.7
libpam-systemd | 238-4
gnome-session-bin (>= 3.10) | 3.28.1-1
gnome-settings-daemon (>= 3.24) | 3.28.1-1
gnome-shell (>= 3.19.92) | 3.28.1-1
gnome-session | 3.28.1-1
OR x-session-manager |
OR x-window-manager |
OR x-terminal-emulator |
lsb-base (>= 3.2-14) | 9.20170808
librsvg2-common | 2.40.20-2
accountsservice (>= 0.6.35) | 0.6.45-1
policykit-1 (>= 0.105-5~) | 0.105-20
gsettings-desktop-schemas | 3.28.0-1
libglib2.0-bin (>= 2.35.0) | 2.56.1-2
dconf-cli (>= 0.20) | 0.28.0-2
dconf-gsettings-backend (>= 0.20) | 0.28.0-2
ucf | 3.0038
x11-common (>= 1:7.6+11) | 1:7.7+19
x11-xserver-utils | 7.7+8


Recommends (Version) | Installed
=-+-===
zenity | 3.28.1-1
xserver-xephyr | 2:1.19.6-1
x11-xkb-utils | 7.7+4
xserver-xorg | 1:7.7+19
at-spi2-core | 2.28.0-3
desktop-base (>= 6) | 9.0.5


Suggests (Version) | Installed
=-+-=
libpam-gnome-keyring | 3.28.0.2-1
gnome-orca | 3.28.1-1
libpam-fprintd (>= 0.8.0-2) |

--
Nos leemos
 RASTER(Linux user #228804)
ras...@rastersoft.com  http://www.rastersoft.com

Bug#897536: mustache.js: FTBFS: make[1]: rake: Command not found

[Pierre-Elliott Bécue]

Le vendredi 11 mai 2018 à 12:12:44+0200, Jonas Meurer a écrit :
> Control: tag -1 +moreinfo
> 
> Hello,
> 
> I just tried to reproduce the FTBFS and failed. rake is defined as
> build-dependency and correctly pulled in according to linked the build logs.
> 
> My best guess is that rake 12.3.1-2 had some bug that got fixed in 12.3.1-3.
> 
> Lucas, could you trigger another rebuild to see whether this got fixed
> by the latest rake upload?
> 
> In any case, it doesn't look like a bug in mustache.js package to me.
> 
> Cheers,

Indeed the rake issue is gone with the latest upload of rake.

Yet, [1] shows that mustache.js still FTBFS.

The reason seems to be that the mustache.js CLI takes too much time to do
its job in some tests on the build servers of the reproducible-builds
project. As the timeout of mocha testsuite is 2s, this leads to some
failures.

A fix should be designed. I see two solutions:

 1) In all describe statements of cli-test.js[2], add a more reasonable
timeout delay to mocha, such as
"""
describe('Mustache CLI', function () {
this.timeout(5000);
var expectedOutput;
[…]
"""
 2) Disable these tests.

It should be noted that tests that may fail based on a time-dependency
(timeout, time-based tests) are not fit for reproducibility tests.

Cheers.

[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mustache.js.html
[2] https://github.com/janl/mustache.js/blob/master/test/cli-test.js

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


signature.asc
Description: PGP signature

Processed: found 846938 in 6.10.1-1

[Debian Bug Tracking System]

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

> # Since upstream fixed it in 
> https://roy.marples.name/git/dhcpcd.git/commit/?id=93f3066bb0bc0974eab1943543205312a6b512ad
>  two days after the upstream release of 6.10.1 and debian has no other 
> patches than spelling fixes in 6.10.1-1, it can be assummed that this issue 
> is still present in 6.10.1-1.
> found 846938 6.10.1-1
Bug #846938 [src:dhcpcd5] dhcpcd5: CVE-2014-7913
Ignoring request to alter found versions of bug #846938 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 846938

[Debian Bug Tracking System]

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

> # Fixed in 
> https://roy.marples.name/git/dhcpcd.git/commit/?id=93f3066bb0bc0974eab1943543205312a6b512ad
>  which has been committed two days after the upstream release of 6.10.1 which 
> is the current upstream version in Debian (while the current upstream release 
> is 7.0.4), i.e. the bug is indeed still not yet included in Debian Unstable
> tags 846938 + fixed-upstream patch
Bug #846938 [src:dhcpcd5] dhcpcd5: CVE-2014-7913
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#898581: Remove pike7.8 from Debian?

[Jeremy Bicha]

Source: pike7.8
Version: 7.8.866-8.1
Severity: serious
Tags: buster sid

Debian 9 "Stretch" has both pike7.8 and pike8.0. In general, we try
not to have duplicate packages in Debian. Is there any reason we
shouldn't remove pike7.8 from Debian unstable now?

Thanks,
Jeremy Bicha

Bug#887856: Intel helding spectre microcode updates back

[Gero Treuner]

Hi all,

I found that (all) the Intel Microcode Update packages from 2018
don't contain the fixed version for my CPU Celeron N3450 (and others
with same CPUID 506c9: N3350 N4200 J3455 J4205). It doesn't benefit
from new commands IBRS/IBPB which indeed is reported so by
spectre-meltdown-checker.sh .

Output from the kernel:
microcode: microcode updated early to revision 0x2c, date = 2017-03-25

Revsion listed in Intel Microcode Update Guidance [1]: 2E

I use package version 3.20180425.1~bpo9+1, but it doesn't matter,
because the error is in upstream.

As a result of longer search I found a source proving that version 2E is
real in [2] - contains the expected fixes. But this must be included in
the official package from the processor manufacturer. According to a
thread in the Intel forum [3] there are more cases like this. While I
know how to replace the microcode file, many are supposedly not aware
about what is missing.

So please connect to (and/or blame at your option) Intel.


[1]
https://newsroom.intel.com/wp-content/uploads/sites/11/2018/04/microcode-update-guidance.pdf

[2]
https://github.com/platomav/CPUMicrocodes/blob/master/Intel/cpu506C9_plat03_ver002E_2017-11-22_PRD_2798C414.bin

[3]
https://communities.intel.com/message/542691#542691

Processed: bug 898578 is forwarded to https://github.com/RexOps/Rex/issues/1197

[Debian Bug Tracking System]

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

> forwarded 898578 https://github.com/RexOps/Rex/issues/1197
Bug #898578 [src:rex] libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS 
and autopkgtest failure)
Set Bug forwarded-to-address to 'https://github.com/RexOps/Rex/issues/1197'.
> thanks
Stopping processing here.

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

Processed: affects 898561

[Debian Bug Tracking System]

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

> affects 898561 + src:libyaml-perl
Bug #898561 [src:libmarc-transform-perl] libmarc-transform-perl: FTBFS with 
libyaml-perl >= 1.25-1 (test failures)
Added indication that 898561 affects src:libyaml-perl
> thanks
Stopping processing here.

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

Processed: libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS and autopkgtest failure)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libyaml-perl
Bug #898578 [src:rex] libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS 
and autopkgtest failure)
Added indication that 898578 affects src:libyaml-perl

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

Bug#898578: libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS and autopkgtest failure)

[gregor herrmann]

Source: rex
Version: 1.6.0-1
Severity: serious
Control: affects -1 src:libyaml-perl
User: debian...@lists.debian.org
Usertags: needs-update
Tags: upstream buster sid
Justification: fails to build from source

- Forwarded message from Paul Gevers <elb...@debian.org> -

From: Paul Gevers <elb...@debian.org>
To: libyaml-p...@packages.debian.org, r...@packages.debian.org
Subject: libyaml-perl/1.25-1 breaks rex/1.6.0-1 autopkgtest in testing
Date: Sun, 13 May 2018 19:29:44 +0100

Dear maintainers,

[This e-mail is automatically sent. V3.1 (20180513)]

tl;dr: libyaml-perl/1.25-1 breaks rex/1.6.0-1 autopkgtest in testing
see: https://ci.debian.net/packages/r/rex/testing/amd64/

…

- End forwarded message -

This also causes a build failure in rex:

YAML Error: Invalid element in map
   Code: YAML_LOAD_ERR_BAD_MAP_ELEMENT
   Line: 6
   Document: 1
 at /usr/share/perl5/YAML/Loader.pm line 361.
# Looks like your test exited with 255 just after 1.
t/report.t ... 
1..3
ok 1 - 'created report class' isa 'Rex::Report::Base'
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 2/3 subtests 
…
Test Summary Report
---
t/report.t (Wstat: 65280 Tests: 1 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 3 tests but ran 1.
Files=70, Tests=1519, 30 wallclock secs ( 0.33 usr  0.09 sys + 14.64 cusr  3.44 
csys = 18.50 CPU)
Result: FAIL
Failed 1/70 test programs. 0/1519 subtests failed.

When run manually:

# prove --blib --verbose t/report.t
t/report.t .. 
1..3
ok 1 - 'created report class' isa 'Rex::Report::Base'
not ok 2 - a new file was created.

#   Failed test 'a new file was created.'
#   at t/report.t line 55.
#  got: '0'
# expected: '1'
ok 3 - the file was not changed
# Looks like you failed 1 test of 3.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/3 subtests 

Test Summary Report
---
t/report.t (Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
Files=1, Tests=3,  1 wallclock secs ( 0.02 usr  0.01 sys +  0.26 cusr  0.05 
csys =  0.34 CPU)
Result: FAIL



Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: John Zorn & Masada: Abed-Nego


signature.asc
Description: Digital Signature

Bug#872894: marked as done (node-policyfile: autopkgtests fail with nodejs 6)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 20:57:59 +
with message-id 
and subject line Bug#872894: fixed in node-policyfile 0.0.6+ds-1
has caused the Debian Bug report #872894,
regarding node-policyfile: autopkgtests fail with nodejs 6
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.)


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

Source: node-policyfile
Version: 0.0.5-3
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful autopkgtest

Hi Maintainer

Since the upload of nodejs 6, node-policyfile's autopkgtests have been 
failing [1] with the following error:


autopkgtest [09:36:46]:  summary
require  FAIL stderr: (node:773) DeprecationWarning: 
process.EventEmitter is deprecated. Use require('events') instead.


I think the patch below is a reasonable workaround until upstream is 
updated.


--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,2 +1,3 @@
 Tests: require
 Depends: node-policyfile
+Restrictions: allow-stderr

Regards
Graham


[1] https://ci.debian.net/packages/n/node-policyfile/
--- End Message ---
--- Begin Message ---
Source: node-policyfile
Source-Version: 0.0.6+ds-1

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated node-policyfile 
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: Sun, 13 May 2018 21:46:27 +0200
Source: node-policyfile
Binary: node-policyfile
Architecture: source
Version: 0.0.6+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Description:
 node-policyfile - Flash Socket Policy File Server for Node.js
Closes: 872894 872903
Changes:
 node-policyfile (0.0.6+ds-1) unstable; urgency=medium
 .
   * Team upload
   [ Andreas Moog ]
   * Imported upstream release 0.0.6
 + Fixes autopkgtests (Closes: #872894)
   * debian/control:
 + Correct homepage field (Closes: #872903)
 + Use debhelper compat 11
 + Update to Standards-Version 4.1.4
 + Transition VCS-Uri to Salsa
 + Priority is optional
 + Add myself to Uploaders
   * debian/rules:
 + Remove unneeded get-orig-source target
   * debian/copyright:
 + Update copyright years
 + Use https uri
   * debian/install:
 + Upstream no longer has a separate lib directory
 .
   [ Bastien Roucariès ]
   * Fix copyright
   * Use git dpm (follow upstream)
   * Fix examples (drop patches use sed)
   * Add json file
   * Move to section javascript
   * Repack due to FTBFS documentation (need not yet packaged node-dox)
Checksums-Sha1:
 fabc14da2fe1961019aff32336edc36a3b71a567 2118 node-policyfile_0.0.6+ds-1.dsc
 f5e237a52bcc8f90e138ddd0ed84fb2c4c860dbb 8802 
node-policyfile_0.0.6+ds.orig.tar.gz
 9e84a128d44bc5c0240358b75c3eb47e61b9f3d9 3408 
node-policyfile_0.0.6+ds-1.debian.tar.xz
 20e68287fb460df6292014c0d1399e68817d295a 5946 
node-policyfile_0.0.6+ds-1_source.buildinfo
Checksums-Sha256:
 5b15872d81588f5fc62f508b7ea169ad8a23556753a7c28d45ac3ad028f345f8 2118 
node-policyfile_0.0.6+ds-1.dsc
 900cc34acb7db1a66dc4ce25840dfa1a3cb9954bcab0d83ed21d150c9c96d257 8802 
node-policyfile_0.0.6+ds.orig.tar.gz
 d2fee9766b385b08d467d2a0e87ff248a298b6f1863145246706d373b02c5334 3408 
node-policyfile_0.0.6+ds-1.debian.tar.xz
 a35f1dfe1adadf0d2745e658c30c1d20a996c356bf5d163b49c2dbba0c59f0bf 5946 
node-policyfile_0.0.6+ds-1_source.buildinfo
Files:
 2b6a3c4cda0296a3f097e739330eb11b 2118 javascript optional 
node-policyfile_0.0.6+ds-1.dsc
 a37b1d56af1866793f36cc28f8ec285f 8802 javascript optional 
node-policyfile_0.0.6+ds.orig.tar.gz
 28ee52f0ca1051211ad708960ab8fe94 3408 javascript optional 
node-policyfile_0.0.6+ds-1.debian.tar.xz
 04b79f89eb5346c041c17e0492d3a716 5946 javascript optional 
node-policyfile_0.0.6+ds-1_source.buildinfo

Bug#898076: marked as done (wget: CVE-2018-0494: cookie injection)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 20:53:18 +
with message-id 
and subject line Bug#898076: fixed in wget 1.16-1+deb8u5
has caused the Debian Bug report #898076,
regarding wget: CVE-2018-0494: cookie injection
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.)


-- 
898076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wget
Version: 1.19.4-1
Severity: grave
Tags: patch security upstream fixed-upstream

Hi,

The following vulnerability was published for wget.

CVE-2018-0494[0]:
cookie injection

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-0494
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0494
[1] 
https://git.savannah.gnu.org/cgit/wget.git/commit/?id=1fc9c95ec144499e69dc8ec76dbe07799d7d82cd

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wget
Source-Version: 1.16-1+deb8u5

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated wget 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: Sun, 06 May 2018 21:24:51 +0200
Source: wget
Binary: wget
Architecture: source
Version: 1.16-1+deb8u5
Distribution: jessie-security
Urgency: high
Maintainer: Noël Köthe 
Changed-By: Salvatore Bonaccorso 
Closes: 898076
Description: 
 wget   - retrieves files from the web
Changes:
 wget (1.16-1+deb8u5) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix cookie injection (CVE-2018-0494) (Closes: #898076)
Checksums-Sha1: 
 a0a2b72c4378cbe282e86488fa26b8cd9a108ba5 1938 wget_1.16-1+deb8u5.dsc
 3d414aff4cd836a0f1f5ed35af8b900cd64f7eb9 23544 wget_1.16-1+deb8u5.debian.tar.xz
Checksums-Sha256: 
 7b899a289fafd193a3f37f53eb539583330f2235e16916d007d8cd6387022265 1938 
wget_1.16-1+deb8u5.dsc
 14427e02817a510a7e43828ef87842c93cecc37397ebbed450df61d1d8f303da 23544 
wget_1.16-1+deb8u5.debian.tar.xz
Files: 
 419fe0b71ff73a89a1db3457998c6004 1938 web important wget_1.16-1+deb8u5.dsc
 e639bd7bb1e6a4ce3a84df02f953adb7 23544 web important 
wget_1.16-1+deb8u5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlrvV35fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E27EP+wVd4n8B69fxFOCwNbDUefJFXKna9hDr
TMB3lYzg9IkTJHmJSKL7lFGYIutneYYgXHydAE52l8ucoqiTYJ6FxfJuJUhVHD+f
OrvfM3R95GtWbvPNMSVk28Nw0AfUm05hjsQo6uG52eIyVC/DX2YuUWD2VNlZOuzv
S5O1a8vy5KYC1UY3p5ASaVmZNFuHHikDqoSOB+YdKK2us87e+7chIydsm6pImGU+
Ok6wPRYioL9j5roUMPsZPcp9YwI0f/oWgLsfogVieL7pbG4ewDSlFC73OYl1N4/v
4yrZjz/gLzvGmfMb3Cgh7GIlSoNHTiRb6OR+UfouMZReRjpqM6auX2kNnViqUcf/
fWY7J8cVxefOoeka95DnDLmXJiQGOBvb2rkj2KoAgvNd7Qe70DUfKBZWMOZoBzk2
PQjDQB7jtmlS24LhMgdgO+y5rObEIS5ZzRgbxHebgYwowRoHY5LLEX2XmsVY/0Gh
1cRQNPcPgmTrfbnVFBH3jydp1eFomF6loCzP785mnQTC+RtX3AfFJgYhI74pczj/
bcP1iwJ6IaURgTgXyvUGVe7quBoGlokgvoNowbZMDiAXfpFsfEuga8/O3eIHVRkQ
sKhDsAz3ASgHEzWKCYLZnct61kDmVRvFKX2RAJ9dqTk0mFBQpPPBgrT9y8DipNIj
AGkh8I5YVUJ9
=TIgD
-END PGP SIGNATURE End Message ---

Bug#896869: marked as done (bijiben FTBFS with meson 0.46.0)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 20:56:04 +
with message-id 
and subject line Bug#896869: fixed in bijiben 3.28.2-1
has caused the Debian Bug report #896869,
regarding bijiben FTBFS with meson 0.46.0
to be marked as done.

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

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


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

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

...
   dh_auto_test
make -j16 -Oline check VERBOSE=1
make[1]: Entering directory '/build/1st/bijiben-3.28.1'
/usr/bin/mesontest -C /build/1st/bijiben-3.28.1/_build
Error: This executable is no more. Use "meson test" instead.
make[1]: *** [Makefile:10: check] Error 1
--- End Message ---
--- Begin Message ---
Source: bijiben
Source-Version: 3.28.2-1

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated bijiben 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: Sun, 13 May 2018 16:21:43 -0400
Source: bijiben
Binary: bijiben
Architecture: source
Version: 3.28.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 bijiben- intuitive note editor integrated with GNOME 3
Closes: 896869
Launchpad-Bugs-Fixed: 1771022
Changes:
 bijiben (3.28.2-1) unstable; urgency=medium
 .
   * New upstream release (LP: #1771022) (Closes: #896869)
Checksums-Sha1:
 f40b6b34d89689d9840d634df027c5083600bbc8 2282 bijiben_3.28.2-1.dsc
 85e5c51341047cfa6ee00cd98452786e3d1a518e 679868 bijiben_3.28.2.orig.tar.xz
 a074bfe80bbb1f8991fefce96264b0165175b10c 10408 bijiben_3.28.2-1.debian.tar.xz
 a2dbd15a9b4daa809b09246052fbccdae18665e6 19489 
bijiben_3.28.2-1_source.buildinfo
Checksums-Sha256:
 0326fc08283876e2ea6dd22cff97513528cdd539fb99cb02ed95c04c0464316f 2282 
bijiben_3.28.2-1.dsc
 5a6ed663d0cc54725f6fb9c8e7626f12ccd34740f99eadfc11d5fb2bafc62dfc 679868 
bijiben_3.28.2.orig.tar.xz
 d0451f71fc616f46c1db32a8f2d98433a1730e059f9dffe09257205c2fae504b 10408 
bijiben_3.28.2-1.debian.tar.xz
 25bed3e52b523b45f773c2c78ec0e8737277854559c5cb8f8748496464fd16a3 19489 
bijiben_3.28.2-1_source.buildinfo
Files:
 1fef3be48461ece622eae8589edea3d7 2282 gnome optional bijiben_3.28.2-1.dsc
 77ee93ec1260bbfc362ff94e08603d01 679868 gnome optional 
bijiben_3.28.2.orig.tar.xz
 ae9c8d0101fe29c4114b17fd7af847be 10408 gnome optional 
bijiben_3.28.2-1.debian.tar.xz
 c7195bc47623eab50e2f44f6057d211b 19489 gnome optional 
bijiben_3.28.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlr4ntcACgkQ5mx3Wuv+
bH3KqhAAvgbl7Ve6oJyqQ43aTF5KYu81mC+XywBVkSSXUaJEEXbmT0N8uDicC81p
GCy97JDXxCVklRRVIDph48fySqn/4vq5mHPkvkP23qwVaa8QQl5cdOood33j7xji
TeKYIYh4tG9/s+MJMpolVwGMt+xKYuzK7l1bxH5orbJmj/cRP9m2S51hG/X0KSeB
d0kDT08woynBlDkd+nGrwcXIM1YnxQAT/+2FF5hQd9GMFiUFMCANQXGXJRY75N0K
eL0xkNPtS3M0urUkWUcFbehEopLBLGpQlJny1SnigfROGMHUt73AFMqZYf+n/H0P
1bdYXflVmqBX/1hYSajO8xFvUv4p9Sgm0dEvje2w7sYNkmzjGI+HINzFjRJ4NSXZ
wxPJu5vMcRyfIesu2qImlUzsqZtS3KjdexPWE5JzvMjP9J5Qppgz/i6stnmZCvT8
Q8Y+DlW94dZOAO/P5VO7ewnIzrxgcFxN5aUiFK/6ABh4QbqgFhAVYy99oowQ2nEK
OM3ayzezq3wzhed4xb8jXMZfL8P2jprFrCqOOjuxyoZPI1T6uUwmH+gySdkCnLAA
y+Z8zGfHs7QWRug7CMyQglBAUINuuwszxcmTPfL/E3UOPJ1tUef1XzpXqew7im+D
nOafnU6B5SWK3o87/PfA5P6x9pcOYuX5DoqNOCztAdb7ONrodR4=
=lu0h
-END PGP SIGNATURE End Message ---

Bug#893668: marked as done (adminer: CVE-2018-7667)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 20:51:51 +
with message-id 
and subject line Bug#893668: fixed in adminer 3.3.3-1+deb8u1
has caused the Debian Bug report #893668,
regarding adminer: CVE-2018-7667
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.)


-- 
893668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adminer
Version: 4.2.5-3
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerability was published for adminer.

CVE-2018-7667[0]:
| Adminer through 4.3.1 has SSRF via the server parameter.

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-7667


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: adminer
Source-Version: 3.3.3-1+deb8u1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated adminer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 May 2018 09:06:51 -0700
Source: adminer
Binary: adminer
Architecture: source all
Version: 3.3.3-1+deb8u1
Distribution: jessie
Urgency: high
Maintainer: Medhamsh V 
Changed-By: Chris Lamb 
Description:
 adminer- Web-based database administration tool
Closes: 893668
Changes:
 adminer (3.3.3-1+deb8u1) jessie; urgency=high
 .
   * CVE-2018-7667: Adminer allowed unauthenticated connections to be initiated
 to arbitrary systems and ports which could bypass external firewalls to
 identify internal hosts and/or perform port scanning of other servers.
 (Closes: #893668)
Checksums-Sha1:
 b31208291084d5c6087c18248f714cda05fa63d8 1851 adminer_3.3.3-1+deb8u1.dsc
 152c4969356d6330382d28dd22e6f16e0d9653bf 3404 
adminer_3.3.3-1+deb8u1.debian.tar.xz
 60a5a781ce2ba73955f1bd148598b08987606a1e 242238 adminer_3.3.3-1+deb8u1_all.deb
Checksums-Sha256:
 f02979dd83d45231319325ec33ee1c3956589a598fb15746910463e5aa8cef57 1851 
adminer_3.3.3-1+deb8u1.dsc
 168cbe44a91fc809a8ff37a5ac7f077252b00d75810b2a1c18500a0bee1f4f63 3404 
adminer_3.3.3-1+deb8u1.debian.tar.xz
 b836b655330e4966879b72e8779b766cc457ec3a65fd3de7a8e71556a957f7ff 242238 
adminer_3.3.3-1+deb8u1_all.deb
Files:
 4ef4480574c57b6ed93165e06414aea2 1851 web extra adminer_3.3.3-1+deb8u1.dsc
 fe7be26d19e366eb8667cd43dd01d080 3404 web extra 
adminer_3.3.3-1+deb8u1.debian.tar.xz
 5019c04c412f7f3e1a460f33b0e10f28 242238 web extra 
adminer_3.3.3-1+deb8u1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlrweeIACgkQHpU+J9Qx
HlhpdA//YHKcK623ufQYm+Ad4GJb986YEk1p2YZy7Nv31kcCtnZsutHqihcXlhPT
WQSKGEfmaCORXzhlqx+qOjmrG+3QZa943+vUmUWgzpVIF39s/JuE2YjHSW6M5yYU
+JJCrVJ4l7kezEdMwYWd2EqjBuXCShDeEtSE8ytPAIMNnICuPF02CwCoQPDsUoDM
nXAeSZQxUUskqaZWLKOWgu3i7n5tBqYAYoN36f4Tj1PEp+ou7i/EZ80Z2jmf6W65
X6eqVYxU7LjiAuzDeVRhYEiIuPpbSnAoBA5aL5OfIe7YjQyB3ICPCXwZ60DQSA0U
gsuZf4GuPCLahaYYxmNES3vPdc3rPVmVTYNIEyfsaPLUTbU+E9rGp8lq6hQbO6kM
3jxI5AVUl3h+JCTEw213lWzXdKUdi0grkBRSsPL8aS52r5gQvZ6aG4XNlsectest
S2Kg9iKv1zR0Lg1NSV3esjpMwEnHYpaiOwyhsMMV2I6Q5KneZn73eMK/P49ODdBg
xmtH2GK8At1U6fEuYMkgnHstcpIC/oog3ZvdAicTBCU1OkrVKLkJrxhGdb7OwmsO
szJvOvfx6Hlwp++C5ko/sIxMh7axcNBQE0VwA/U9kkik1ekpNmyl5SnYDY7q+nBo
XxCRtKS4z7SnbFmshjTzPyNrJYfIEpOuQ/2uQr4ZPnP2lDT/mz8=
=wlHB
-END PGP SIGNATURE End Message ---

Bug#898076: marked as done (wget: CVE-2018-0494: cookie injection)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 20:51:09 +
with message-id 
and subject line Bug#898076: fixed in wget 1.18-5+deb9u2
has caused the Debian Bug report #898076,
regarding wget: CVE-2018-0494: cookie injection
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.)


-- 
898076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wget
Version: 1.19.4-1
Severity: grave
Tags: patch security upstream fixed-upstream

Hi,

The following vulnerability was published for wget.

CVE-2018-0494[0]:
cookie injection

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-0494
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0494
[1] 
https://git.savannah.gnu.org/cgit/wget.git/commit/?id=1fc9c95ec144499e69dc8ec76dbe07799d7d82cd

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wget
Source-Version: 1.18-5+deb9u2

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated wget 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: Sun, 06 May 2018 21:08:15 +0200
Source: wget
Binary: wget wget-udeb
Architecture: source
Version: 1.18-5+deb9u2
Distribution: stretch-security
Urgency: high
Maintainer: Noël Köthe 
Changed-By: Salvatore Bonaccorso 
Closes: 898076
Description: 
 wget   - retrieves files from the web
 wget-udeb  - retrieves files from the web (udeb)
Changes:
 wget (1.18-5+deb9u2) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix cookie injection (CVE-2018-0494) (Closes: #898076)
Checksums-Sha1: 
 e583bd9815eb30b794a36bdd7a63503a2af639b6 2085 wget_1.18-5+deb9u2.dsc
 cf9db92ff7cccd07353f0fc330dd7a1653b1e335 23308 wget_1.18-5+deb9u2.debian.tar.xz
Checksums-Sha256: 
 613256e709fb78230402013e0f30c6cd9dfa441a3c705c96a6ecd419c5adde8a 2085 
wget_1.18-5+deb9u2.dsc
 8d98535e4062442c1eb0bcdb557551ee64323f09352528f741afd20ed81b09b1 23308 
wget_1.18-5+deb9u2.debian.tar.xz
Files: 
 95cd20d45d7e087c88ff1b60635363ae 2085 web important wget_1.18-5+deb9u2.dsc
 f562c4458ea3aa9213de3608db60f792 23308 web important 
wget_1.18-5+deb9u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlrvVRBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E9hgP/1CvC7g3BfYlQTiEuiutYLrx8dhYu0AC
AjBZxaUXqBKNf/TZ5a4gCXF8W2EKdBu/zw9dG3tGvVicJz2dom6bbaOMjt78B8KO
AhbV1Zew/0EkYhYJvLDoklE4wpIKCTLEBT2BT2Jicv0zIl6k9dUuIbgNZZHG4Q2K
RuC1rSKGbZLUiMIMAclbSCyDmF5H/4aVQc/NGr9C/TldWRRqG6a/g16eZ/TKkEXh
ouaMAbyj3gGh/evggCNG40qGdS81gC9MYGMLOQObpzWNMiVw4xtzRP9J3boUzK63
Rx+wg4sflfvUIyXe1D8zDmQcupm3mC3bwh2lypns5oH7phQPU+r5SG8ZvJ9bQeLz
VJ/niCPUwkk5u2EDvTsfSS0a5cnJMCBV9oHfAm+S6REIhQkLL1MMT6wwlQ6I1uQ9
97JJBElN1yWDReygsMSVq8qPd4mKMmMyC5LVCR3OxSMNjFGi4Pryi8bM9TyCGcLR
yzigR1p/rd9ytxkFN9igyCA1GPaq/4NQJjIPMJnRFcyjzIMknX2pmYsYlc6D3N3z
oTostbfAm4x4ikjARUyFPIV9uzQ/q+GTVUgg4CRIIz/3q9emIkKFN6fR4eW1x/pT
a3kSyJUrHWAyB3lUnZfqpRHMgHOxWAEec4Q1lcJeZmOLkv6BJWwNip0SxdYa39nJ
8u+c9Zv9r+ir
=l5Zj
-END PGP SIGNATURE End Message ---

Bug#898577: pytables: FTBFS - 56 tests fail with 'TypeError: a float is required'

[Gilles Filippini]

Source: pytables
Version: 3.4.3-1
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

pytables FTBFS on unstable during the tests step. 56 tests fail with errors 
like:

==
ERROR: test00_description (tables.tests.test_tables.RecArrayTwoWriteTestCase)
Checking table description and descriptive fields.
- --
Traceback (most recent call last):
  File 
"/<>/build/lib.linux-x86_64-2.7/tables/tests/test_tables.py", line 
138, in setUp
self.populateFile()
  File 
"/<>/build/lib.linux-x86_64-2.7/tables/tests/test_tables.py", line 
213, in populateFile
self.initRecArray()
  File 
"/<>/build/lib.linux-x86_64-2.7/tables/tests/test_tables.py", line 
207, in initRecArray
shape=self.expectedrows)
  File "/usr/lib/python2.7/dist-packages/numpy/core/records.py", line 847, in 
array
return fromrecords(obj, dtype=dtype, shape=shape, **kwds)
  File "/usr/lib/python2.7/dist-packages/numpy/core/records.py", line 708, in 
fromrecords
retval = sb.array(recList, dtype=descr)
TypeError: a float is required

Regards,

_g.


- -- System Information:
Distributor ID: PureOS
Description:PureOS GNU/Linux 8
Release:8
Codename:   green
Architecture: x86_64

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlr4msIACgkQ7+hsbH/+
z4MfyggApCe7IWvb2JQUOwpcyVH85TEqaZLZXTRDg4SuC/7WkQfbMj5A+Mh56QXP
BbQPRlIVzgR0jcrC+6VyLHqiKIAsaR4EUuLxP86rcWF4LFrn9I8tqjM/9OCv6zM0
XzSXQfcLXQuulqo01GYk0zB/Yt1PMod3hi76zLUui9UphTNZVx40/v+6iAkmCYko
9YAI0P7DQOtlBmSvePl/KawaiS8TUgeZv/pw9la5CAznlnOD22Pt2uowh7qm8uAO
FtRlt4eG/2/IL8gqS9hdPeeb+8iePOQVKnHDtf3iipvwBucFFsMa5FzEqcZRwLEk
2UdXhOimaAMrihNc6Lzq/T8OuJggLg==
=2eVK
-END PGP SIGNATURE-

Bug#895246: gconf: Intent to Adopt

[Jeremy Bicha]

On Sun, May 13, 2018 at 1:54 PM, Adrian Bunk  wrote:
> On Mon, Apr 30, 2018 at 06:47:41PM -0400, Jeremy Bicha wrote:
>> Why? Basically there are only two things left in Buster that depend on
>> gconf: eclipse and pulseaudio.
>
> Plus ~ 50 more in unstable.
>
>> Please be more specific about what software you are interested in that
>> requires gconf and why it can't be ported away from gconf this year.
>
> As I wrote:
>   It is not a good service to our users to rip gconf support
>   out of many packages for buster.
>
> This should be reverted in the packages where it was already done,
> shipping castrated packages in buster where the package in stretch was
> fully functional is not good, especially since there is no problem that
> would make it non-trivial to ship gconf in buster.

I don't think you really addressed my request: Which specific packages
have been removed from Testing solely because of gconf that you
believe should be in Buster and what is the reason they can't be
ported away from gconf this year?

By the way, I did announce the gconf removal on this list in February.
[1] Respectfully, you are the only one complaining about gconf's
removal.

It is not a service to our users to keep old libraries and software
around for additional Debian releases just because someone somewhere
might use some of it for something.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha

Processed: fixed 878999 in 3.5.2-2

[Debian Bug Tracking System]

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

> fixed 878999 3.5.2-2
Bug #878999 {Done: Andres Salomon } [src:protobuf] 
protobuf FTBFS on armhf/i386: testMergeFrom 
(google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault
Marked as fixed in versions protobuf/3.5.2-2.
> thanks
Stopping processing here.

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

Processed: forcibly merging 893138 898570

[Debian Bug Tracking System]

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

> forcemerge 893138 898570
Bug #893138 [jabref] jabref: fails to build and start with openjdk-9
Bug #893138 [jabref] jabref: fails to build and start with openjdk-9
Marked as found in versions jabref/3.8.1+ds-3.
Added tag(s) buster and sid.
Bug #898570 [jabref] jabref: Moreover, there is 4.2 now! Still no running 
jabref anywhere, since 3.5. No openjdk/-jfx or whatsoever anywhere.
Set Bug forwarded-to-address to 'https://github.com/JabRef/jabref/issues/2594'.
Severity set to 'serious' from 'important'
Added indication that 898570 affects src:jabref
Marked as found in versions jabref/3.8.2+ds-2.
Added tag(s) upstream.
Merged 893138 898570
> thanks
Stopping processing here.

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

Bug#898524: marked as done (FTBFS: unsatisfiable dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 18:21:02 +
with message-id 
and subject line Bug#898524: fixed in stylish-haskell 0.9.2.0-1
has caused the Debian Bug report #898524,
regarding FTBFS: unsatisfiable dependencies
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.)


-- 
898524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stylish-haskell
Version: 0.8.1.0-1
Severity: serious
Justification: fails to build from source
Tags: sid buster

Install stylish-haskell build dependencies (apt-based resolver)
---

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

The following packages have unmet dependencies:
 sbuild-build-depends-stylish-haskell-dummy : Depends: libghc-src-exts-dev (< 
1.20) but 1.20.2-2 is to be installed
  Depends: libghc-src-exts-prof (< 
1.20) but 1.20.2-2 is to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use


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

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: stylish-haskell
Source-Version: 0.9.2.0-1

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

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

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated stylish-haskell 
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: Sun, 13 May 2018 11:06:57 -0700
Source: stylish-haskell
Binary: stylish-haskell
Architecture: source
Version: 0.9.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Description:
 stylish-haskell - Haskell code prettifier
Closes: 898524
Changes:
 stylish-haskell (0.9.2.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #898524).
 - New build-deps on libghc-file-embed-{dev,prof}
   * Stop installing default config to /usr/share/stylish-haskell
 Now embedded in the executable.
 - Drop FILES section from manpage.
   * Update d/copyright:
 - Bump years
 - Add stanza for scripts/*
   (Not installed in our binary packages.)
 - Replace 'BSD3' with 'BSD-3-clause'.
Checksums-Sha1:
 62922b0b69ba883e46e63ab7ad04845ce55611f9 3083 stylish-haskell_0.9.2.0-1.dsc
 daf64589b3e9891733d8ec3a249fcb4a0166ca69 28904 
stylish-haskell_0.9.2.0.orig.tar.xz
 183c16546b1dc2f9f2ed1466addf8764ef22f8e5 4676 
stylish-haskell_0.9.2.0-1.debian.tar.xz
Checksums-Sha256:
 b1b22c856f00b98cf76bf11cd54f64317a5e96e8ead66ff1adf4b9660733798a 3083 
stylish-haskell_0.9.2.0-1.dsc
 ed8040b3f068071f41f03925b030de69e505ec58596f2737df58084b94228ec5 28904 
stylish-haskell_0.9.2.0.orig.tar.xz
 1bcb7e84ce598c84500bc946ae4e5db4c365845667e9d4d2b6566078a74a0b8d 4676 
stylish-haskell_0.9.2.0-1.debian.tar.xz
Files:
 4f20354c44c50eb6ca3742080a857623 3083 haskell optional 
stylish-haskell_0.9.2.0-1.dsc
 5854ec1b3a336d8b3ebfb7b29097e27a 28904 haskell optional 

Bug#895246: gconf: Intent to Adopt

[Adrian Bunk]

On Mon, Apr 30, 2018 at 06:47:41PM -0400, Jeremy Bicha wrote:
> On Sun, Apr 8, 2018 at 3:19 PM, Adrian Bunk  wrote:
> 
> Sorry for not replying more promptly.
> 
> > I hereby declare my intent to adopt gconf.
> 
> Why? Basically there are only two things left in Buster that depend on
> gconf: eclipse and pulseaudio.

Plus ~ 50 more in unstable.

> pulseaudio is being worked on upstream
> so I expect that to be resolved in time for Buster. Eclipse is a major
> headache as you know.
> 
> Please be more specific about what software you are interested in that
> requires gconf and why it can't be ported away from gconf this year.

As I wrote:
  It is not a good service to our users to rip gconf support
  out of many packages for buster.

This should be reverted in the packages where it was already done, 
shipping castrated packages in buster where the package in stretch was 
fully functional is not good, especially since there is no problem that 
would make it non-trivial to ship gconf in buster.

> Thanks,
> Jeremy Bicha

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

Bug#898572: wrong term in debian/copyright

[Thorsten Alteholz]

Package: keepass2-plugin-keepasshttp
Version: XXX
Severity: serious
thanks

As the license of this software is just GPL-3, please remove the 
term

  "or (at your option) any later version."
from your debian/copyright.

Thanks!
  Thorsten

Bug#898374: marked as done (gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 17:50:03 +
with message-id 
and subject line Bug#898374: fixed in gcc-8-cross 14
has caused the Debian Bug report #898374,
regarding gcc-8-cross: file conflicts with {gcc,g++,...}-8 on 
/usr/bin/-*-8
to be marked as done.

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

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


-- 
898374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8-cross
Version: 12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package gcc-8-x86-64-linux-gnu.
  Preparing to unpack .../16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb ...
  Unpacking gcc-8-x86-64-linux-gnu (8.1.0-1cross1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/x86_64-linux-gnu-gcc-8', which is also in 
package gcc-8 8.1.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-GsQJpd/01-cpp-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb
   
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb

Similar problems with cpp-8,g++-8,... as well as for gcc-7-cross and
{gcc,g++,...}-7.


cheers,

Andreas


gcc-8=8.1.0-1_gcc-8-x86-64-linux-gnu=8.1.0-1cross1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-8-cross
Source-Version: 14

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-8-cross package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 May 2018 12:58:53 -0400
Source: gcc-8-cross
Binary: gcc-8-cross-base gcc-8-x86-64-linux-gnu-base libgcc1-amd64-cross 
libgcc-8-dev-amd64-cross lib32gcc1-amd64-cross lib32gcc-8-dev-amd64-cross 
libx32gcc1-amd64-cross libx32gcc-8-dev-amd64-cross gcc-8-x86-64-linux-gnu 
gcc-8-multilib-x86-64-linux-gnu gcc-8-plugin-dev-x86-64-linux-gnu 
cpp-8-x86-64-linux-gnu g++-8-x86-64-linux-gnu g++-8-multilib-x86-64-linux-gnu 
libgomp1-amd64-cross lib32gomp1-amd64-cross libx32gomp1-amd64-cross 
libitm1-amd64-cross lib32itm1-amd64-cross libx32itm1-amd64-cross 
libatomic1-amd64-cross lib32atomic1-amd64-cross libx32atomic1-amd64-cross 
libasan5-amd64-cross lib32asan5-amd64-cross libx32asan5-amd64-cross 
libtsan0-amd64-cross liblsan0-amd64-cross lib32lsan0-amd64-cross 
libx32lsan0-amd64-cross libubsan1-amd64-cross lib32ubsan1-amd64-cross 
libx32ubsan1-amd64-cross libquadmath0-amd64-cross lib32quadmath0-amd64-cross 
libx32quadmath0-amd64-cross gobjc++-8-x86-64-linux-gnu 
gobjc++-8-multilib-x86-64-linux-gnu gobjc-8-x86-64-linux-gnu
 gobjc-8-multilib-x86-64-linux-gnu libobjc4-amd64-cross 
libobjc-8-dev-amd64-cross lib32objc4-amd64-cross lib32objc-8-dev-amd64-cross 
libx32objc4-amd64-cross libx32objc-8-dev-amd64-cross 
gfortran-8-x86-64-linux-gnu gfortran-8-multilib-x86-64-linux-gnu 
libgfortran5-amd64-cross libgfortran-8-dev-amd64-cross 
lib32gfortran5-amd64-cross lib32gfortran-8-dev-amd64-cross 
libx32gfortran5-amd64-cross libx32gfortran-8-dev-amd64-cross 
gccgo-8-x86-64-linux-gnu gccgo-8-multilib-x86-64-linux-gnu libgo13-amd64-cross 
lib32go13-amd64-cross libx32go13-amd64-cross libstdc++6-amd64-cross 
lib32stdc++6-amd64-cross libx32stdc++6-amd64-cross libstdc++-8-dev-amd64-cross 
libstdc++-8-pic-amd64-cross lib32stdc++-8-dev-amd64-cross 
libx32stdc++-8-dev-amd64-cross gdc-8-x86-64-linux-gnu 
gdc-8-multilib-x86-64-linux-gnu libgphobos-8-dev-amd64-cross 
libgphobos76-amd64-cross lib32gphobos-8-dev-amd64-cross 
lib32gphobos76-amd64-cross libx32gphobos-8-dev-amd64-cross 
libx32gphobos76-amd64-cross
 gnat-8-x86-64-linux-gnu 

Bug#898374: marked as done (gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 17:50:12 +
with message-id 
and subject line Bug#898374: fixed in gcc-8-cross 15
has caused the Debian Bug report #898374,
regarding gcc-8-cross: file conflicts with {gcc,g++,...}-8 on 
/usr/bin/-*-8
to be marked as done.

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

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


-- 
898374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8-cross
Version: 12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package gcc-8-x86-64-linux-gnu.
  Preparing to unpack .../16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb ...
  Unpacking gcc-8-x86-64-linux-gnu (8.1.0-1cross1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/x86_64-linux-gnu-gcc-8', which is also in 
package gcc-8 8.1.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-GsQJpd/01-cpp-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb
   
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb

Similar problems with cpp-8,g++-8,... as well as for gcc-7-cross and
{gcc,g++,...}-7.


cheers,

Andreas


gcc-8=8.1.0-1_gcc-8-x86-64-linux-gnu=8.1.0-1cross1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-8-cross
Source-Version: 15

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-8-cross package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 May 2018 12:58:53 -0400
Source: gcc-8-cross
Binary: gcc-8-cross-base gcc-8-x86-64-linux-gnu-base libgcc1-amd64-cross 
libgcc-8-dev-amd64-cross lib32gcc1-amd64-cross lib32gcc-8-dev-amd64-cross 
libx32gcc1-amd64-cross libx32gcc-8-dev-amd64-cross gcc-8-x86-64-linux-gnu 
gcc-8-multilib-x86-64-linux-gnu gcc-8-plugin-dev-x86-64-linux-gnu 
cpp-8-x86-64-linux-gnu g++-8-x86-64-linux-gnu g++-8-multilib-x86-64-linux-gnu 
libgomp1-amd64-cross lib32gomp1-amd64-cross libx32gomp1-amd64-cross 
libitm1-amd64-cross lib32itm1-amd64-cross libx32itm1-amd64-cross 
libatomic1-amd64-cross lib32atomic1-amd64-cross libx32atomic1-amd64-cross 
libasan5-amd64-cross lib32asan5-amd64-cross libx32asan5-amd64-cross 
libtsan0-amd64-cross liblsan0-amd64-cross lib32lsan0-amd64-cross 
libx32lsan0-amd64-cross libubsan1-amd64-cross lib32ubsan1-amd64-cross 
libx32ubsan1-amd64-cross libquadmath0-amd64-cross lib32quadmath0-amd64-cross 
libx32quadmath0-amd64-cross gobjc++-8-x86-64-linux-gnu 
gobjc++-8-multilib-x86-64-linux-gnu gobjc-8-x86-64-linux-gnu
 gobjc-8-multilib-x86-64-linux-gnu libobjc4-amd64-cross 
libobjc-8-dev-amd64-cross lib32objc4-amd64-cross lib32objc-8-dev-amd64-cross 
libx32objc4-amd64-cross libx32objc-8-dev-amd64-cross 
gfortran-8-x86-64-linux-gnu gfortran-8-multilib-x86-64-linux-gnu 
libgfortran5-amd64-cross libgfortran-8-dev-amd64-cross 
lib32gfortran5-amd64-cross lib32gfortran-8-dev-amd64-cross 
libx32gfortran5-amd64-cross libx32gfortran-8-dev-amd64-cross 
gccgo-8-x86-64-linux-gnu gccgo-8-multilib-x86-64-linux-gnu libgo13-amd64-cross 
lib32go13-amd64-cross libx32go13-amd64-cross libstdc++6-amd64-cross 
lib32stdc++6-amd64-cross libx32stdc++6-amd64-cross libstdc++-8-dev-amd64-cross 
libstdc++-8-pic-amd64-cross lib32stdc++-8-dev-amd64-cross 
libx32stdc++-8-dev-amd64-cross gdc-8-x86-64-linux-gnu 
gdc-8-multilib-x86-64-linux-gnu libgphobos-8-dev-amd64-cross 
libgphobos76-amd64-cross lib32gphobos-8-dev-amd64-cross 
lib32gphobos76-amd64-cross libx32gphobos-8-dev-amd64-cross 
libx32gphobos76-amd64-cross
 gnat-8-x86-64-linux-gnu 

Processed: affects 898501

[Debian Bug Tracking System]

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

> affects 898501 + debci
Bug #898501 [fonts-font-awesome] Broken symlinks
Added indication that 898501 affects debci
> thanks
Stopping processing here.

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

Bug#867256: marked as done (monitoring-plugins-basic: fails to install: Error: The new file apt.cfg does not exist!)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 17:37:46 +
with message-id 
and subject line Bug#867256: fixed in monitoring-plugins 2.2-4
has caused the Debian Bug report #867256,
regarding monitoring-plugins-basic: fails to install: Error: The new file 
apt.cfg does not exist!
to be marked as done.

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

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


-- 
867256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: monitoring-plugins-basic
Version: 2.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + nagios-nrpe-server

Hi,

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

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

  Selecting previously unselected package monitoring-plugins-basic.
(Reading database ... 4672 files and directories currently installed.)
  Preparing to unpack .../monitoring-plugins-basic_2.2-3_amd64.deb ...
  Unpacking monitoring-plugins-basic (2.2-3) ...
  Setting up monitoring-plugins-basic (2.2-3) ...
  Error: The new file apt.cfg does not exist!
  dpkg: error processing package monitoring-plugins-basic (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   monitoring-plugins-basic


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: monitoring-plugins
Source-Version: 2.2-4

We believe that the bug you reported is fixed in the latest version of
monitoring-plugins, 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.
Jan Wagner  (supplier of updated monitoring-plugins package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 May 2018 14:04:35 +0200
Source: monitoring-plugins
Binary: monitoring-plugins monitoring-plugins-common monitoring-plugins-basic 
monitoring-plugins-standard
Architecture: source i386 all
Version: 2.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Jan Wagner 
Description:
 monitoring-plugins - Plugins for nagios compatible monitoring systems 
(metapackage)
 monitoring-plugins-basic - Plugins for nagios compatible monitoring systems 
(basic)
 monitoring-plugins-common - Common files for plugins for nagios compatible 
monitoring
 monitoring-plugins-standard - Plugins for nagios compatible monitoring systems 
(standard)
Closes: 856676 867256 878769
Changes:
 monitoring-plugins (2.2-4) unstable; urgency=medium
 .
   * [97cb3c4] Drop symlinks to removed LEGAL file. (Closes: #856676)
   * [878ceb9] Using absolut paths when using ucf, debconf 1.5.62 changed it's
 behaviour (Closes: #867256)
   * [22de139] d/control: Update VCS-headers
   * [b024e21] d/control: Priority extra is deprecated, using optional
   * [9095923] d/control: Drop old nagios-plugins* transitional packages
 (Closes: #878769)
   * [6956bcc] d/control: Bump Standards-Version to 4.1.4.0, no changes needed
   * [d634e5a] d/functions: Fixing ucf register function
Checksums-Sha1:
 0f9aa6e7278f7c010bed217c8d95816059d6f7a8 2537 monitoring-plugins_2.2-4.dsc
 782ee59ed5be6136337cce32f48875fe8efba118 1590008 
monitoring-plugins_2.2.orig.tar.gz
 118e68919d5707840dc93adec4ea40697557038c 40584 
monitoring-plugins_2.2-4.debian.tar.xz
 375cac1b24e9f4e082e21cbb3000150ae21893f5 1324784 
monitoring-plugins-basic-dbgsym_2.2-4_i386.deb
 6999de893974560a19371f8f387ae2946f61dc58 302920 
monitoring-plugins-basic_2.2-4_i386.deb
 9a78dca7f1a4755a5c175d7d6629a73990e394ff 72256 
monitoring-plugins-common-dbgsym_2.2-4_i386.deb
 06db13dcfef69aefc330ecf3067a5e366adfe163 69804 
monitoring-plugins-common_2.2-4_i386.deb
 a9fc033e7d16da5118eb4569bd5e72a959a18f34 588632 
monitoring-plugins-standard-dbgsym_2.2-4_i386.deb
 298e01013fe920c2af2e641360171d1040bac72f 159152 
monitoring-plugins-standard_2.2-4_i386.deb
 

Bug#898501: Broken symlinks

[Antonio Terceiro]

On Sat, 12 May 2018 12:39:50 -0700 Sean Whitton  
wrote:
> Package: fonts-font-awesome
> Version: 5.0.10-1
> Severity: grave
> Control: affects -1 cider
> 
> Dear maintainer,
> 
> The latest upload introduces some new broken symlinks:
> 
>   fonts-font-awesome: broken-symlink 
> /usr/share/fonts-font-awesome/fonts/FontAwesome.otf -> 
> ../../fonts/opentype/font-awesome/FontAwesome.otf
>   fonts-font-awesome: broken-symlink 
> /usr/share/fonts-font-awesome/fonts/fontawesome-webfont.eot -> 
> ../../fonts/eot/font-awesome/fontawesome-webfont.eot
>   fonts-font-awesome: broken-symlink 
> /usr/share/fonts-font-awesome/fonts/fontawesome-webfont.svg -> 
> ../../fonts/svg/font-awesome/fontawesome-webfont.svg
>   fonts-font-awesome: broken-symlink 
> /usr/share/fonts-font-awesome/fonts/fontawesome-webfont.ttf -> 
> ../../fonts/truetype/font-awesome/fontawesome-webfont.ttf
>   fonts-font-awesome: broken-symlink 
> /usr/share/fonts-font-awesome/fonts/fontawesome-webfont.woff -> 
> ../../fonts/woff/font-awesome/fontawesome-webfont.woff
>   fonts-font-awesome: broken-symlink 
> /usr/share/fonts-font-awesome/fonts/fontawesome-webfont.woff2 -> 
> ../../fonts/woff/font-awesome/fontawesome-webfont.woff2
> 
> This causes builds of other packages to fail, e.g. like this:
> 
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/usr/share/mkdocs/themes/mkdocs_bootstrap/fonts/fontawesome-webfont.woff'
> 
> I think this will affect any package that build-depends on
> mkdocs-bootstrap, of which there are many, hence the severity.

not only that. there are 60+ packages that directly build-depend on
fonts-font-awesome, and these changes probably just broke most of them.

> If the intention was to remove all these links, which NEWS.Debian
> suggests it might have been, then the broken symlinks should still be
> removed, though the bug severity should be lowered.

I understand that upstream has strongly shaken things up with this new
release. However, is there any possibility of providing some backwards
compatibility?


signature.asc
Description: PGP signature

Bug#898374: marked as done (gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 17:19:39 +
with message-id 
and subject line Bug#898374: fixed in gcc-8-cross 13
has caused the Debian Bug report #898374,
regarding gcc-8-cross: file conflicts with {gcc,g++,...}-8 on 
/usr/bin/-*-8
to be marked as done.

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

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


-- 
898374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8-cross
Version: 12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package gcc-8-x86-64-linux-gnu.
  Preparing to unpack .../16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb ...
  Unpacking gcc-8-x86-64-linux-gnu (8.1.0-1cross1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/x86_64-linux-gnu-gcc-8', which is also in 
package gcc-8 8.1.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-GsQJpd/01-cpp-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb
   
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb

Similar problems with cpp-8,g++-8,... as well as for gcc-7-cross and
{gcc,g++,...}-7.


cheers,

Andreas


gcc-8=8.1.0-1_gcc-8-x86-64-linux-gnu=8.1.0-1cross1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-8-cross
Source-Version: 13

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-8-cross package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 May 2018 12:58:53 -0400
Source: gcc-8-cross
Binary: gcc-8-cross-base gcc-8-x86-64-linux-gnu-base libgcc1-amd64-cross 
libgcc-8-dev-amd64-cross lib32gcc1-amd64-cross lib32gcc-8-dev-amd64-cross 
libx32gcc1-amd64-cross libx32gcc-8-dev-amd64-cross gcc-8-x86-64-linux-gnu 
gcc-8-multilib-x86-64-linux-gnu gcc-8-plugin-dev-x86-64-linux-gnu 
cpp-8-x86-64-linux-gnu g++-8-x86-64-linux-gnu g++-8-multilib-x86-64-linux-gnu 
libgomp1-amd64-cross lib32gomp1-amd64-cross libx32gomp1-amd64-cross 
libitm1-amd64-cross lib32itm1-amd64-cross libx32itm1-amd64-cross 
libatomic1-amd64-cross lib32atomic1-amd64-cross libx32atomic1-amd64-cross 
libasan5-amd64-cross lib32asan5-amd64-cross libx32asan5-amd64-cross 
libtsan0-amd64-cross liblsan0-amd64-cross lib32lsan0-amd64-cross 
libx32lsan0-amd64-cross libubsan1-amd64-cross lib32ubsan1-amd64-cross 
libx32ubsan1-amd64-cross libquadmath0-amd64-cross lib32quadmath0-amd64-cross 
libx32quadmath0-amd64-cross gobjc++-8-x86-64-linux-gnu 
gobjc++-8-multilib-x86-64-linux-gnu gobjc-8-x86-64-linux-gnu
 gobjc-8-multilib-x86-64-linux-gnu libobjc4-amd64-cross 
libobjc-8-dev-amd64-cross lib32objc4-amd64-cross lib32objc-8-dev-amd64-cross 
libx32objc4-amd64-cross libx32objc-8-dev-amd64-cross 
gfortran-8-x86-64-linux-gnu gfortran-8-multilib-x86-64-linux-gnu 
libgfortran5-amd64-cross libgfortran-8-dev-amd64-cross 
lib32gfortran5-amd64-cross lib32gfortran-8-dev-amd64-cross 
libx32gfortran5-amd64-cross libx32gfortran-8-dev-amd64-cross 
gccgo-8-x86-64-linux-gnu gccgo-8-multilib-x86-64-linux-gnu libgo13-amd64-cross 
lib32go13-amd64-cross libx32go13-amd64-cross libstdc++6-amd64-cross 
lib32stdc++6-amd64-cross libx32stdc++6-amd64-cross libstdc++-8-dev-amd64-cross 
libstdc++-8-pic-amd64-cross lib32stdc++-8-dev-amd64-cross 
libx32stdc++-8-dev-amd64-cross gdc-8-x86-64-linux-gnu 
gdc-8-multilib-x86-64-linux-gnu libgphobos-8-dev-amd64-cross 
libgphobos76-amd64-cross lib32gphobos-8-dev-amd64-cross 
lib32gphobos76-amd64-cross libx32gphobos-8-dev-amd64-cross 
libx32gphobos76-amd64-cross
 gnat-8-x86-64-linux-gnu 

Processed: affects 898501

[Debian Bug Tracking System]

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

> affects 898501 src:goaccess
Bug #898501 [fonts-font-awesome] Broken symlinks
Added indication that 898501 affects src:goaccess
> thanks
Stopping processing here.

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

Processed: block 894159 with 888908

[Debian Bug Tracking System]

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

> block 894159 with 888908
Bug #894159 [release.debian.org] transition: icu
894159 was blocked by: 898369 898465
894159 was not blocking any bugs.
Added blocking bug(s) of 894159: 888908
> thanks
Stopping processing here.

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

Processed: block 891515 with 880003

[Debian Bug Tracking System]

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

> block 891515 with 880003
Bug #891515 [node-colormin] node-colormin : Depends: node-has (>= 1.0.1) but it 
is not installable
891515 was not blocked by any bugs.
891515 was not blocking any bugs.
Added blocking bug(s) of 891515: 880003
> thanks
Stopping processing here.

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

Processed: Re: Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #898556 [kwin-wayland] [kwin-wayland] Closing windows in Plasma Wayland 
crashes the entire session
Severity set to 'important' from 'grave'

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

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

[Maximiliano Curia]

Control: severity -1 important

¡Hola Alexander!

El 2018-05-13 a las 17:09 +0300, Alexander Kernozhitsky escribió:

Package: kwin-wayland
Version: 4:5.12.5-1
Severity: grave



I tried Plasma session on Wayland today. Closing a window in it crashes the
session and returns me back to SDDM.


I'm sorry to hear that, but most of the wayland support in Debian is in 
preview release mode, in fact, I think that that problem that you are 
reporting might be in xwayland or in a lower layer of the wayland stack (see 
#897390[1], for example).


I couldn't reproduce the issue in my machine. Is there any other wayland 
desktop session that does work for you?


Given this, I'm lowering the severity.

Happy hacking,

[1]: https://bugs.debian.org/897390
--
"It's a well-known fact that computing devices such as the abacus were 
invented thousands of years ago. But it's not well known that the first use of 
common computer protocol occurred in the Old Testament. This, of course, was 
when Moses aborted the Egyptians' process with a control-sea."

-- Tom Galloway (recs.arts.comics, February 1992)
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#897529: installation-guide is marked for autoremoval from testing

[Cyril Brulebois]

Hi,

Holger Wansing  (2018-05-10):
> Debian testing autoremoval watch  wrote:
> > installation-guide 20170614 is marked for autoremoval from testing on 
> > 2018-05-31
> > 
> > It is affected by these RC bugs:
> > 897529: installation-guide: FTBFS
> 
> This is because of the "ID xxx-yyy already defined" validation errors",
> which has already been reported in 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880210
> and which was already fixed in svn repo (oh, this is now git).
> 
> Maybe we should do an upload to get this fixed in the archive?

That would be a good idea (along with an extra commit to update Vcs-* to
salsa, see my latest reply in the salsa thread).

> However, that would be an upload for Buster (there's "Bump release
> name to buster" in the changelog).

I'm not sure why that would be an issue? The manual documents the buster
installation process (which shouldn't have changed too much?), but the
upload targets unstable as usual?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#897568: 4.16 breakage

[Chris Zubrzycki]

ZoL only breaks on kernel updates when the kernel changes the API/structures 
that it uses. ZFS 0.7.9 is released and fully supports all current kernels, and 
has some good bug fixes and feature upgrades. 

Processed: bug 898561 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=125307

[Debian Bug Tracking System]

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

> forwarded 898561 https://rt.cpan.org/Ticket/Display.html?id=125307
Bug #898561 [src:libmarc-transform-perl] libmarc-transform-perl: FTBFS with 
libyaml-perl >= 1.25-1 (test failures)
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=125307'.
> thanks
Stopping processing here.

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

Bug#894290: gradle should raise the source/target level to the minimum supported by the default JDK

[殷啟聰 | Kai-Chung Yan]

Control: reassign -1 gradle-debian-helper 1.6

I would say this is not the fault of Gradle itself, but it the tricks can be 
provided by `gradle-debian-helper`. We shouldn't modify the behavior of the 
build tools too much.

Let's keep the severity as is for now, as FTBFS is quite serious indeed.



signature.asc
Description: OpenPGP digital signature

Processed: Re: gradle should raise the source/target level to the minimum supported by the default JDK

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 gradle-debian-helper 1.6
Bug #894290 [gradle] gradle should raise the source/target level to the minimum 
supported by the default JDK
Bug reassigned from package 'gradle' to 'gradle-debian-helper'.
No longer marked as found in versions gradle/3.4.1-3.
Ignoring request to alter fixed versions of bug #894290 to the same values 
previously set
Bug #894290 [gradle-debian-helper] gradle should raise the source/target level 
to the minimum supported by the default JDK
Marked as found in versions gradle-debian-helper/1.6.

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

Bug#898561: libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures)

[gregor herrmann]

Source: libmarc-transform-perl
Version: 0.003006-2
Severity: serious
Tags: upstream buster sid
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libmarc-transform-perl's testsuite fails, both during build and
autopkgtest, with libyaml-perl >= 1.25-1:


perl Build test --verbose 1
Hexadecimal number > 0x non-portable at (eval 28) line 1.
Number found where operator expected at (eval 29) line 8, near ""I want) 
{$boolcond=1;$boolcondint=1; eval{ create("605"
(Missing operator before 605?)
String found where operator expected at (eval 29) line 8, near "605",{""
(Missing operator before ",{"?)
Bareword found where operator expected at (eval 29) line 8, near "",{"a"
(Missing operator before a?)
String found where operator expected at (eval 29) line 8, near "a"=>""
Hexadecimal number > 0x non-portable at (eval 58) line 1.
Number found where operator expected at (eval 59) line 8, near ""I want) 
{$boolcond=1;$boolcondint=1; eval{ create("605"
(Missing operator before 605?)
String found where operator expected at (eval 59) line 8, near "605",{""
(Missing operator before ",{"?)
Bareword found where operator expected at (eval 59) line 8, near "",{"a"
(Missing operator before a?)
String found where operator expected at (eval 59) line 8, near "a"=>""

#   Failed test ''
#   at t/test.t line 177.
#  got: 
'optionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value of the 401 conditions field||501:  
|a:foao|a:foo|b:baoar|b:update only the first b in condition's field 
501|c:updated value of all c in condition's field||501:  |c:1||502:  |a:I want 
"$"||502:  |a:this is the value of a subfield of a new 502 field||503:  
|a:babar|a:fee|b:mandatory b in condition's field||504:  |a:updated value of 
all 504a if exists|a:updated value of all 504a if exists||600:  |a:a 
string|a:first a subfield of this new 600 field|a:second a subfield of this new 
600 field|b:the 600b value||602: 2|a:a402a2||602:1 |a:a402a1||604:  
|a:foo|a:update only the first a in 604|b:openbar|c:New York||700:  |a:the a 
subfield of this mandatory 700 
field|b:beberoptionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value of the 401 conditions field||501:  
|a:foao|a:foo|b:baoar|b:update only the first b in condition's field 
501|c:updated value of all c in condition's field||501:  |c:1||502:  |a:I want 
"$"||502:  |a:this is the value of a subfield of a new 502 field||503:  
|a:babar|a:fee|b:mandatory b in condition's field||504:  |a:updated value of 
all 504a if exists|a:updated value of all 504a if exists||600:  |a:a 
string|a:first a subfield of this new 600 field|a:second a subfield of this new 
600 field|b:the 600b value||602: 2|a:a402a2||602:1 |a:a402a1||604:  
|a:foo|a:update only the first a in 604|b:openbar|c:New York||700:  |a:the a 
subfield of this mandatory 700 field|b:beber'
# expected: 
'optionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value of the 401 conditions field||501:  
|a:foao|a:foo|b:baoar|b:update only the first b in condition's field 
501|c:updated value of all c in condition's field||501:  |c:1||502:  |a:I want 
"$"||502:  |a:this is the value of a subfield of a new 502 field||503:  
|a:babar|a:fee|b:mandatory b in condition's field||504:  |a:updated value of 
all 504a if exists|a:updated value of all 504a if exists||600:  |a:a 
string|a:first a subfield of this new 600 field|a:second a subfield of this new 
600 field|b:the 600b value||602: 2|a:a402a2||602:1 |a:a402a1||604:  
|a:foo|a:update only the first a in 604|b:openbar|c:New York||605:  |a:"I want 
"$"" contain a $ sign||700:  |a:the a subfield of this mandatory 700 
field|b:beberoptionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value of the 401 conditions field||501:  
|a:foao|a:foo|b:baoar|b:update only the first b in condition's field 
501|c:updated value of all c in condition's field||501:  |c:1||502:  |a:I want 
"$"||502:  |a:this is the value of a subfield of a new 502 field||503:  
|a:babar|a:fee|b:mandatory b in condition's field||504:  |a:updated value of 
all 504a if exists|a:updated value of all 504a if exists||600:  |a:a 
string|a:first a subfield of this new 600 field|a:second a subfield of this new 
600 field|b:the 600b value||602: 2|a:a402a2||602:1 |a:a402a1||604:  
|a:foo|a:update only the first a in 604|b:openbar|c:New York||605:  |a:"I want 
"$"" contain a $ sign||700:  |a:the a subfield of this mandatory 700 
field|b:beber'
Number found where operator expected at (eval 179) line 8, near ""I want) 
{$boolcond=1;$boolcondint=1; eval{ create("604"

Bug#898542: qt4-x11: FTBFS with libicu60

[Lisandro Damián Nicanor Pérez Meyer]

El dom., 13 de may. de 2018 10:51, John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> escribió:

> Control: tags 898542 +patch
>
> On 05/13/2018 03:35 PM, John Paul Adrian Glaubitz wrote:
> > openSUSE seems to have a patch [1] we can use that is also already used
> > in Fedora. I'll test it.
>
> Attaching openSUSE's patch which fixes the problem for me.


The patch looks good. I won't be able to put my hands on it at very least
until tomorrow... If I get to. So if you want to do a NMU please go ahead.

Processed: Re: h5py: FTBFS with HDF5 1.10.2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #898526 [src:h5py] h5py: FTBFS with HDF5 1.10.2
Severity set to 'serious' from 'normal'
> retitle -1 h5py: FTBFS - FAIL: test_out_of_order_offsets
Bug #898526 [src:h5py] h5py: FTBFS with HDF5 1.10.2
Changed Bug title to 'h5py: FTBFS - FAIL: test_out_of_order_offsets' from 
'h5py: FTBFS with HDF5 1.10.2'.

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

Processed: ICU transition: ICU version is part of the boost ABI

[Debian Bug Tracking System]

Processing control commands:

> reassign 898465 src:icu 60.1-1
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
Ignoring request to reassign bug #898465 to the same package
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
Ignoring request to alter found versions of bug #898465 to the same values 
previously set
> retitle 898369 boost: ICU version used is part of the ABI
Bug #898369 [src:boost1.62] boost: ICU version used is part of the ABI
Ignoring request to change the title of bug#898369 to the same title
> retitle 898465 ICU must not migrate to testing before the boost ABI breakage 
> is resolved
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
Ignoring request to change the title of bug#898465 to the same title
> affects 898369 libmapnik3.0 viking
Bug #898369 [src:boost1.62] boost: ICU version used is part of the ABI
Ignoring request to set affects of bug 898369 to the same value previously set
> block 898465 by 898369
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
898465 was blocked by: 898369
898465 was blocking: 894159
Ignoring request to alter blocking bugs of bug #898465 to the same blocks 
previously set
> block 894159 by 898369 898465
Bug #894159 [release.debian.org] transition: icu
894159 was blocked by: 898369 898465
894159 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #894159 to the same blocks 
previously set

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

Processed: ICU transition: ICU version is part of the boost ABI

[Debian Bug Tracking System]

Processing control commands:

> reassign 898465 src:icu 60.1-1
Bug #898465 [viking] symbol lookup error: /usr/lib/libmapnik.so.3.0: undefined 
symbol
Bug reassigned from package 'viking' to 'src:icu'.
No longer marked as found in versions viking/1.6.2-3.
Ignoring request to alter fixed versions of bug #898465 to the same values 
previously set
Bug #898465 [src:icu] symbol lookup error: /usr/lib/libmapnik.so.3.0: undefined 
symbol
Marked as found in versions icu/60.1-1.
> retitle 898369 boost: ICU version used is part of the ABI
Bug #898369 [src:boost1.62] breaks ncmpcpp
Changed Bug title to 'boost: ICU version used is part of the ABI' from 'breaks 
ncmpcpp'.
> retitle 898465 ICU must not migrate to testing before the boost ABI breakage 
> is resolved
Bug #898465 [src:icu] symbol lookup error: /usr/lib/libmapnik.so.3.0: undefined 
symbol
Changed Bug title to 'ICU must not migrate to testing before the boost ABI 
breakage is resolved' from 'symbol lookup error: /usr/lib/libmapnik.so.3.0: 
undefined symbol'.
> affects 898369 libmapnik3.0 viking
Bug #898369 [src:boost1.62] boost: ICU version used is part of the ABI
Added indication that 898369 affects libmapnik3.0 and viking
> block 898465 by 898369
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
898465 was not blocked by any bugs.
898465 was not blocking any bugs.
Added blocking bug(s) of 898465: 898369
> block 894159 by 898369 898465
Bug #894159 [release.debian.org] transition: icu
894159 was not blocked by any bugs.
894159 was not blocking any bugs.
Added blocking bug(s) of 894159: 898369 and 898465

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

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

[Alexander Kernozhitsky]

Package: kwin-wayland
Version: 4:5.12.5-1
Severity: grave

I tried Plasma session on Wayland today. Closing a window in it crashes the 
session and returns me back to SDDM.

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

Debian Release: buster/sid
  990 testing ftp.by.debian.org 
  500 unstableftp.by.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-
==
kwayland-integration   | 5.12.1-1
kwin-common (= 4:5.12.5-1) | 
4:5.12.5-1
kwin-wayland-backend-drm   (= 4:5.12.5-1)  | 
4:5.12.5-1
 OR kwin-wayland-backend-fbdev (= 4:5.12.5-1)  | 
 OR kwin-wayland-backend-x11   (= 4:5.12.5-1)  | 
 OR kwin-wayland-backend-virtual   (= 4:5.12.5-1)  | 
 OR kwin-wayland-backend-wayland(= 4:5.12.5-1) | 
libcap2-bin| 
1:2.25-1.2
xwayland   | 
2:1.19.6-1
libc6(>= 2.14) | 
libcap2(>= 1:2.10) | 
libepoxy0 (>= 1.0) | 
libfontconfig1 (>= 2.12.6) | 
libfreetype6  (>= 2.6) | 
libkf5coreaddons5   (>= 5.2.0) | 
libkf5i18n5(>= 4.97.0) | 
libkf5idletime5(>= 5.13.0) | 
libkf5quickaddons5 (>= 5.26.0) | 
libkf5waylandclient5  (>= 4:5.5.0) | 
libkf5waylandserver5 (>= 4:5.1.1+git20141128.0009) | 
libkf5windowsystem5  (>= 5.7.0+git20150224.0052+15.04) | 
libkwineffects11 (>= 4:5.1.95+git20150122) | 
libqt5core5a   (>= 5.10.0) | 
libqt5dbus5(>= 5.9.0~) | 
libqt5gui5 (>= 5.10.1) | 
libqt5widgets5 (>= 5.9.0~) | 
libstdc++6  (>= 5) | 
libwayland-egl1(>= 1.15.0) | 
libxcb1| 
qtbase-abi-5-10-0  | 


Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
-
Alexander Kernozhitsky

Bug#898369: ICU transition: ICU version is part of the boost ABI

[Adrian Bunk]

Control: reassign 898465 src:icu 60.1-1
Control: retitle 898369 boost: ICU version used is part of the ABI
Control: retitle 898465 ICU must not migrate to testing before the boost ABI 
breakage is resolved
Control: affects 898369 libmapnik3.0 viking
Control: block 898465 by 898369
Control: block 894159 by 898369 898465

On Thu, May 10, 2018 at 06:06:08PM -0300, Thadeu Lima de Souza Cascardo wrote:
> Source: boost1.62
> Version: 1.62.0+dfsg-5+b2
> Severity: serious
> 
> After upgrading boost1.62 to 1.62.0+dfsg-5+b2, ncmpcpp does not start
> anymore.
> 
> $ ncmpcpp
> ncmpcpp: symbol lookup error: ncmpcpp: undefined symbol: 
> _ZNK5boost16re_detail_10620031icu_regex_traits_implementation12do_transformEPKiS3_PKN6icu_578CollatorE
>...

boost::re_detail_106200::icu_regex_traits_implementation::do_transform(int 
const*, int const*, icu_57::Collator const*) const

Yes, boost makes the ICU version it uses part of its ABI.

There is no obvious good way forward, the RC bug in ICU will ensure that 
the breakage won't migrate to testing before this got sorted out.

cu
Adrian

-- 

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

Processed: ICU transition: ICU version is part of the boost ABI

[Debian Bug Tracking System]

Processing control commands:

> reassign 898465 src:icu 60.1-1
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
Ignoring request to reassign bug #898465 to the same package
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
Ignoring request to alter found versions of bug #898465 to the same values 
previously set
> retitle 898369 boost: ICU version used is part of the ABI
Bug #898369 [src:boost1.62] boost: ICU version used is part of the ABI
Ignoring request to change the title of bug#898369 to the same title
> retitle 898465 ICU must not migrate to testing before the boost ABI breakage 
> is resolved
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
Ignoring request to change the title of bug#898465 to the same title
> affects 898369 libmapnik3.0 viking
Bug #898369 [src:boost1.62] boost: ICU version used is part of the ABI
Ignoring request to set affects of bug 898369 to the same value previously set
> block 898465 by 898369
Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI 
breakage is resolved
898465 was blocked by: 898369
898465 was blocking: 894159
Ignoring request to alter blocking bugs of bug #898465 to the same blocks 
previously set
> block 894159 by 898369 898465
Bug #894159 [release.debian.org] transition: icu
894159 was blocked by: 898369 898465
894159 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #894159 to the same blocks 
previously set

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

Bug#886382: fixed in amd64-microcode 3.20171205.1

[Andreas Ziegler]

Hi,

this bug's severity is marked "grave" but the changes haven't been
backported to stable or oldstable yet.

Is there a valid reason?

Regards

Andreas


On Wed, 10 Jan 2018 10:04:16 + Henrique de Moraes Holschuh
 wrote:
> Source: amd64-microcode
> Source-Version: 3.20171205.1
> 
> We believe that the bug you reported is fixed in the latest version of
> amd64-microcode, 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 886...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Henrique de Moraes Holschuh  (supplier of updated 
> amd64-microcode 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, 08 Jan 2018 12:19:57 -0200
> Source: amd64-microcode
> Binary: amd64-microcode
> Architecture: source amd64
> Version: 3.20171205.1
> Distribution: unstable
> Urgency: high
> Maintainer: Henrique de Moraes Holschuh 
> Changed-By: Henrique de Moraes Holschuh 
> Description:
>  amd64-microcode - Processor microcode firmware for AMD CPUs
> Closes: 886382
> Changes:
>  amd64-microcode (3.20171205.1) unstable; urgency=high
>  .
>* New microcode updates (closes: #886382):
>  sig 0x00800f12, patch id 0x08001213, 2017-12-05
>  Thanks to SuSE for distributing these ahead of AMD's official release!
>* Add IBPB support for family 17h AMD processors (CVE-2017-5715)
>* README: describe source for faml17h microcode update
>* Upload to unstable to match IBPB microcode support on Intel in Debian
>  unstable.
>* WARNING: requires at least kernel 4.15, 4.14.13, 4.9.76, 4.4.111 (or a
>  backport of commit f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf
>  "x86/microcode/AMD: Add support for fam17h microcode loading") otherwise
>  it will not be applied to the processor.
> Checksums-Sha1:
>  ea1c935c8439710b746c32888b66a78e99e23ccd 1695 
> amd64-microcode_3.20171205.1.dsc
>  fc2ece2b1c5a042f56304c6709c2c0add5dcb9aa 32584 
> amd64-microcode_3.20171205.1.tar.xz
>  25962539ebbfe4d04c118ba026ffc83dd004346c 5492 
> amd64-microcode_3.20171205.1_amd64.buildinfo
>  55efcf98ad106a71ecebf4902421d9cbd4b620fc 33552 
> amd64-microcode_3.20171205.1_amd64.deb
> Checksums-Sha256:
>  bf20678e4e523f759fed3564d4f417fa72889e874e723d0d56ed354cf9ae58df 1695 
> amd64-microcode_3.20171205.1.dsc
>  a38bc072f535a3d3c1bf4e9e545197aa5114e979e94ef7e4a67e615df2f853a7 32584 
> amd64-microcode_3.20171205.1.tar.xz

Processed: Re: Bug#898542: qt4-x11: FTBFS with libicu60

[Debian Bug Tracking System]

Processing control commands:

> tags 898542 +patch
Bug #898542 [src:qt4-x11] qt4-x11: FTBFS with libicu60
Added tag(s) patch.

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

Bug#898542: qt4-x11: FTBFS with libicu60

[John Paul Adrian Glaubitz]

Control: tags 898542 +patch

On 05/13/2018 03:35 PM, John Paul Adrian Glaubitz wrote:

openSUSE seems to have a patch [1] we can use that is also already used
in Fedora. I'll test it.


Attaching openSUSE's patch which fixes the problem for me.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
From: Fabian Vogt 
Subject: Fix build with ICU >= 59

ICU >= 59 requires C++11 for its header files.
Qt can't be compiled with -std=c++11 as a whole, so only enable
it for qlocale_icu.cpp.

Index: qt-everywhere-opensource-src-4.8.7/src/corelib/tools/tools.pri
===
--- qt-everywhere-opensource-src-4.8.7.orig/src/corelib/tools/tools.pri
+++ qt-everywhere-opensource-src-4.8.7/src/corelib/tools/tools.pri
@@ -102,7 +102,15 @@ contains(QT_CONFIG, zlib):include($$PWD/
 else:include($$PWD/../../3rdparty/zlib_dependency.pri)
 
 contains(QT_CONFIG,icu) {
-SOURCES += tools/qlocale_icu.cpp
+cpp11.name = cpp11
+cpp11.input = SOURCES_CPP11
+cpp11.dependency_type = TYPE_C
+cpp11.variable_out = OBJECTS
+cpp11.output = ${QMAKE_VAR_OBJECTS_DIR}${QMAKE_FILE_IN_BASE}$${first(QMAKE_EXT_OBJ)}
+cpp11.commands = $${QMAKE_CXX} $(CXXFLAGS) -std=c++11 $(INCPATH) -c ${QMAKE_FILE_IN} -o ${QMAKE_FILE_OUT}
+QMAKE_EXTRA_COMPILERS += cpp11
+
+SOURCES_CPP11 += tools/qlocale_icu.cpp
 DEFINES += QT_USE_ICU
 }
 

Processed: Re: Bug#898542: qt4-x11: FTBFS with libicu60

[Debian Bug Tracking System]

Processing control commands:

> tags 898542 +patch
Bug #898542 [src:qt4-x11] qt4-x11: FTBFS with libicu60
Ignoring request to alter tags of bug #898542 to the same tags previously set

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

Bug#898542: qt4-x11: FTBFS with libicu60

[John Paul Adrian Glaubitz]

On 05/13/2018 03:08 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
> I have not checked if other distros ship a patch for this (or maybe
> they switched to the embedded copy, if applicable). I will at some
> point but I can't promise being fast here.

openSUSE seems to have a patch [1] we can use that is also already used
in Fedora. I'll test it.

Adrian

> [1] 
> https://build.opensuse.org/package/view_file/KDE:Qt/libqt4/fix-build-icu59.patch?expand=1

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#898542: qt4-x11: FTBFS with libicu60

[Lisandro Damián Nicanor Pérez Meyer]

Hi John! This seems to be related to the icu transition, so CCing the bug.

On 13 May 2018 at 07:02, John Paul Adrian Glaubitz
 wrote:
> Source: qt4-x11
> Version: 4:4.8.7+dfsg-16
> Severity: serious
> Justification: fails to build from source
>
> Hi!
>
> qt4-x11 fails to build from source due to incompatible changes in libicu60:

Well unfortunately:

- No one seems to have checked this before starting the transition.
- qt4-x11 is dead upstream, so we do not have upstreams to try to get
a patch from.

I have not checked if other distros ship a patch for this (or maybe
they switched to the embedded copy, if applicable). I will at some
point but I can't promise being fast here.

So for a fast solution someone needs to come up with a patch I'm afraid.

Sorry for the bad news.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Processed: Re: Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #869191 [pristine-tar] pristine-tar: pristine-xz failed to reproduce build 
of ../util-linux_2.30.1.orig.tar.xz
Severity set to 'grave' from 'important'

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

Bug#897127: psensor FTBFS on i386/armhf: FAIL: test-cppcheck.sh

[Joachim Reichel]

See bug 898327.

  Joachim

Processed: found 898369 in 1.62.0+dfsg-5

[Debian Bug Tracking System]

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

> found 898369 1.62.0+dfsg-5
Bug #898369 [src:boost1.62] breaks ncmpcpp
Marked as found in versions boost1.62/1.62.0+dfsg-5.
> thanks
Stopping processing here.

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

Bug#855251: easytag corrupt ogg files

[James Cowgill]

Hi,

On 13/05/18 11:47, Bruno Kleinert wrote:
> Hi James,
> 
> unfortunately it doesn't seem fixed to me. I tried the following with
> 2.4.3-4:
>1. youtube-dl -x -f 'bestaudio' 'https://www.youtube.com/watch?v=ui_odI
>   vVIBE'
>2. Use soundconverter to convert it to Ogg Vorbis
>3. vorbisgain Flux\ Pavilion\ -\ Hold\ Me\ Close-ui_odIvVIBE.ogg (Add
>   replay gain tags)
>4. ogginfo Flux\ Pavilion\ -\ Hold\ Me\ Close-ui_odIvVIBE.ogg | grep
>   REPLAY (Confirm that the file contains replay gain tags)
>5. Use easytag to add Title tag "abcd" and save the file
>6. ogginfo Flux\ Pavilion\ -\ Hold\ Me\ Close-ui_odIvVIBE.ogg | grep
>   REPLAY (Won't output anything, replay gain tags got lost)
> 
> At least oggz-validate didn't complain about a broken Ogg file. Neither
> before, nor after editing it with easytag.

This is not the same bug. This bug is about easytag corrupting the audio
data in vorbis files whereas for you it looks like easytag has removed a
tag it (presumably) doesn't support. Could you file a separate bug?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#894642: marked as done (gst-plugins-espeak FTBFS with GStreamer 1.14)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 11:34:49 +
with message-id 
and subject line Bug#894642: fixed in gst-plugins-espeak 0.4.0-3.1
has caused the Debian Bug report #894642,
regarding gst-plugins-espeak FTBFS with GStreamer 1.14
to be marked as done.

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

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


-- 
894642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-espeak
Version: 0.4.0-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gst-plugins-espeak.html

...
/bin/bash ../libtool  --tag=CC --tag=disable-static  --mode=link gcc -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/orc-0.4 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -module -avoid-version -export-symbols-regex 
'^_*gst_plugin_desc$' -no-undefined -Wl,-z,relro -Wl,-O1 -Wl,-z,defs 
-Wl,--as-needed -o libgstespeak.la -rpath 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0 libgstespeak_la-espeak.lo 
libgstespeak_la-gstespeak.lo -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 
-lgstaudio-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0  -lespeak 
libtool: link: /usr/bin/nm -B  .libs/libgstespeak_la-espeak.o 
.libs/libgstespeak_la-gstespeak.o   | sed -n -e 's/^.*[
]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' | /bin/sed 
's/.* //' | sort | uniq > .libs/libgstespeak.exp
libtool: link: /bin/grep -E -e "^_*gst_plugin_desc$" ".libs/libgstespeak.exp" > 
".libs/libgstespeak.expT"
libtool: link: mv -f ".libs/libgstespeak.expT" ".libs/libgstespeak.exp"
libtool: link: echo "{ global:" > .libs/libgstespeak.ver
libtool: link:  cat .libs/libgstespeak.exp | sed -e "s/\(.*\)/\1;/" >> 
.libs/libgstespeak.ver
libtool: link:  echo "local: *; };" >> .libs/libgstespeak.ver
libtool: link:  gcc -shared  -fPIC -DPIC  .libs/libgstespeak_la-espeak.o 
.libs/libgstespeak_la-gstespeak.o   -lgstaudio-1.0 -lgstbase-1.0 
-lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lespeak  -pthread -pthread -g -O2 
-fstack-protector-strong -Wl,-z -Wl,relro -Wl,-O1 -Wl,-z -Wl,defs 
-Wl,--as-needed   -pthread -Wl,-soname -Wl,libgstespeak.so -Wl,-version-script 
-Wl,.libs/libgstespeak.ver -o .libs/libgstespeak.so
/usr/bin/ld:.libs/libgstespeak.ver:2: syntax error in VERSION script
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:420: libgstespeak.la] Error 1


GST_PLUGIN_LDFLAGS in configure.ac needs updating.
--- End Message ---
--- Begin Message ---
Source: gst-plugins-espeak
Source-Version: 0.4.0-3.1

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gst-plugins-espeak 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, 28 Apr 2018 20:07:37 +0300
Source: gst-plugins-espeak
Binary: gstreamer1.0-espeak
Architecture: source
Version: 0.4.0-3.1
Distribution: unstable
Urgency: low
Maintainer: Debian Sugar Team 
Changed-By: Adrian Bunk 
Description:
 gstreamer1.0-espeak - GStreamer plugin for eSpeak speech synthesis
Closes: 894642
Changes:
 gst-plugins-espeak (0.4.0-3.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS with GStreamer 1.14. (Closes: #894642)
Checksums-Sha1:
 191924ec42f50af930feaac02ab01496cb110466 2216 gst-plugins-espeak_0.4.0-3.1.dsc
 7d306707cea150bc93b38aaa47b3df61f041d74b 5952 
gst-plugins-espeak_0.4.0-3.1.debian.tar.xz
Checksums-Sha256:
 da988ea7d5626188ad1cf120ee62acc6dcb00e5ed1a24976f9b0249ad2b9e051 2216 
gst-plugins-espeak_0.4.0-3.1.dsc
 02279ed1339de467123d46cbdac4bcbec37ec9c0951d934c22d02312fdb92a00 5952 
gst-plugins-espeak_0.4.0-3.1.debian.tar.xz
Files:
 

Bug#898549: synergy FTBFS: No SOURCES given to target: gmock

[Adrian Bunk]

Source: synergy
Version: 1.8.8-stable+dfsg.1-1.1
Severity: serious

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

...
CMake Error at src/test/CMakeLists.txt:22 (add_library):
  Cannot find source file:

/usr/src/gmock/src/gmock-all.cc

  Tried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm
  .hpp .hxx .in .txx


CMake Error at src/test/CMakeLists.txt:22 (add_library):
  No SOURCES given to target: gmock

Bug#894642: [Pkg-sugar-devel] Bug#894642: gst-plugins-espeak: diff for NMU version 0.4.0-3.1

[Adrian Bunk]

On Mon, Apr 30, 2018 at 07:07:26AM +1000, James Cameron wrote:
> Will you be sending this upstream?
> 
> https://github.com/sugarlabs/gst-plugins-espeak

Not sure about that, they might want to implement an improved regex 
instead of my simple approach of removing the regex.

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

Bug#897519: marked as done (bcron: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 11:19:28 +
with message-id 
and subject line Bug#897519: fixed in bcron 0.11-1.2
has caused the Debian Bug report #897519,
regarding bcron: FTBFS: tests failed
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> sh tests.sh
> Test tests/sched-dst 0 * * * * 1081054860 failed:
> @@ -1,2 +1,2 @@
> -last: 1081054860 2004-04-04 00:01:00 EST
> -next: 1081058400 2004-04-04 01:00:00 EST
> +last: 1081054860 2004-04-04 01:01:00 EDT
> +next: 1081058400 2004-04-04 02:00:00 EDT
> 
> Test tests/sched-dst 0 * * * * 1081058460 failed:
> @@ -1,2 +1,2 @@
> -last: 1081058460 2004-04-04 01:01:00 EST
> +last: 1081058460 2004-04-04 02:01:00 EDT
>  next: 1081062000 2004-04-04 03:00:00 EDT
> 
> Test tests/sched-dst 0 * * * * 1099198860 failed:
> @@ -1,2 +1,2 @@
>  last: 1099198860 2004-10-31 01:01:00 EDT
> -next: 1099202400 2004-10-31 01:00:00 EST
> +next: 1099202400 2004-10-31 02:00:00 EDT
> 
> Test tests/sched-dst 0 * * * * 1099202460 failed:
> @@ -1,2 +1,2 @@
> -last: 1099202460 2004-10-31 01:01:00 EST
> -next: 1099206000 2004-10-31 02:00:00 EST
> +last: 1099202460 2004-10-31 02:01:00 EDT
> +next: 1099206000 2004-10-31 03:00:00 EDT
> 
> Test tests/sched-dst 0 * * * * 1099206060 failed:
> @@ -1,2 +1,2 @@
> -last: 1099206060 2004-10-31 02:01:00 EST
> -next: 1099209600 2004-10-31 03:00:00 EST
> +last: 1099206060 2004-10-31 03:01:00 EDT
> +next: 1099209600 2004-10-31 04:00:00 EDT
> 
> Test tests/sched-dst 0 0 * * * 1081054860 failed:
> @@ -1,2 +1,2 @@
> -last: 1081054860 2004-04-04 00:01:00 EST
> +last: 1081054860 2004-04-04 01:01:00 EDT
>  next: 1081137600 2004-04-05 00:00:00 EDT
> 
> Test tests/sched-dst 0 0 * * * 1081058460 failed:
> @@ -1,2 +1,2 @@
> -last: 1081058460 2004-04-04 01:01:00 EST
> +last: 1081058460 2004-04-04 02:01:00 EDT
>  next: 1081137600 2004-04-05 00:00:00 EDT
> 
> Test tests/sched-dst 0 0 * * * 1099195260 failed:
> @@ -1,2 +1,2 @@
>  last: 1099195260 2004-10-31 00:01:00 EDT
> -next: 1099285200 2004-11-01 00:00:00 EST
> +next: 1099281600 2004-11-01 00:00:00 EDT
> 
> Test tests/sched-dst 0 0 * * * 1099198860 failed:
> @@ -1,2 +1,2 @@
>  last: 1099198860 2004-10-31 01:01:00 EDT
> -next: 1099285200 2004-11-01 00:00:00 EST
> +next: 1099281600 2004-11-01 00:00:00 EDT
> 
> Test tests/sched-dst 0 0 * * * 1099202460 failed:
> @@ -1,2 +1,2 @@
> -last: 1099202460 2004-10-31 01:01:00 EST
> -next: 1099285200 2004-11-01 00:00:00 EST
> +last: 1099202460 2004-10-31 02:01:00 EDT
> +next: 1099281600 2004-11-01 00:00:00 EDT
> 
> Test tests/sched-dst 0 0 * * * 1099206060 failed:
> @@ -1,2 +1,2 @@
> -last: 1099206060 2004-10-31 02:01:00 EST
> -next: 1099285200 2004-11-01 00:00:00 EST
> +last: 1099206060 2004-10-31 03:01:00 EDT
> +next: 1099281600 2004-11-01 00:00:00 EDT
> 
> Test tests/sched-dst 0 1 * * * 1081054860 failed:
> @@ -1,2 +1,2 @@
> -last: 1081054860 2004-04-04 00:01:00 EST
> -next: 1081058400 2004-04-04 01:00:00 EST
> +last: 1081054860 2004-04-04 01:01:00 EDT
> +next: 1081141200 2004-04-05 01:00:00 EDT
> 
> Test tests/sched-dst 0 1 * * * 1081058460 failed:
> @@ -1,2 +1,2 @@
> -last: 1081058460 2004-04-04 01:01:00 EST
> +last: 1081058460 2004-04-04 02:01:00 EDT
>  next: 1081141200 2004-04-05 01:00:00 EDT
> 
> Test tests/sched-dst 0 1 * * * 1099198860 failed:
> @@ -1,2 +1,2 @@
>  last: 1099198860 2004-10-31 01:01:00 EDT
> -next: 1099288800 2004-11-01 01:00:00 EST
> +next: 1099285200 2004-11-01 01:00:00 EDT
> 
> Test tests/sched-dst 0 1 * * * 1099202460 failed:
> @@ -1,2 +1,2 @@
> -last: 1099202460 2004-10-31 01:01:00 EST
> -next: 1099288800 2004-11-01 01:00:00 EST
> +last: 1099202460 2004-10-31 02:01:00 EDT
> +next: 1099285200 2004-11-01 01:00:00 EDT
> 
> Test tests/sched-dst 0 1 * * * 1099206060 failed:
> @@ -1,2 +1,2 @@
> -last: 1099206060 2004-10-31 02:01:00 EST
> -next: 1099288800 2004-11-01 01:00:00 EST
> +last: 1099206060 2004-10-31 03:01:00 EDT
> +next: 1099285200 2004-11-01 01:00:00 EDT
> 
> Test tests/sched-dst 0 2 * * * 1081054860 failed:
> @@ -1,2 +1,2 @@
> -last: 1081054860 2004-04-04 00:01:00 EST
> -next: 1081062000 2004-04-04 03:00:00 EDT
> +last: 1081054860 2004-04-04 01:01:00 EDT
> 

Bug#855251: easytag corrupt ogg files

[Bruno Kleinert]

Am Sonntag, den 25.03.2018, 12:55 +0100 schrieb James Cowgill:
> Hi,
> 
> On 03/01/18 16:50, James Cowgill wrote:
> > On 16/02/17 01:02, Samuele Battarra wrote:
> > > Package: easytag
> > > Version: 2.4.3-1
> > > Severity: normal
> > > 
> > > Dear Maintainer,
> > > I have a ogg file encoded from a live cd, I split it to single
> > > tracks with oggsplt and then tag the tracks with easytag.
> > > When I play the files I hear a click at file change.
> > > The click is not present in files before the tagging and if I tag
> > > with kid3.
> > 
> > As you might have noticed, I have decided that the best way to fix
> > this
> > is to disable support for OGG and related media types in easytag
> > for the
> > time being. Solving this bug is apparently quite complex and while
> > the
> > upstream bug has been open for over a year, there has not been much
> > progress on it. I think it is better to have some version in buster
> > (which does not mangle your media files) than nothing at all.
> 
> I have just uploaded easytag 2.4.3-4 which reverts an upstream commit
> which I think will fix this (you will need to wait a few hours before
> it
> appears on the mirrors). It would be very useful if people could test
> it
> for me before I upload the fix to stable.
> 
> Thanks,
> James

Hi James,

unfortunately it doesn't seem fixed to me. I tried the following with
2.4.3-4:
   1. youtube-dl -x -f 'bestaudio' 'https://www.youtube.com/watch?v=ui_odI
  vVIBE'
   2. Use soundconverter to convert it to Ogg Vorbis
   3. vorbisgain Flux\ Pavilion\ -\ Hold\ Me\ Close-ui_odIvVIBE.ogg (Add
  replay gain tags)
   4. ogginfo Flux\ Pavilion\ -\ Hold\ Me\ Close-ui_odIvVIBE.ogg | grep
  REPLAY (Confirm that the file contains replay gain tags)
   5. Use easytag to add Title tag "abcd" and save the file
   6. ogginfo Flux\ Pavilion\ -\ Hold\ Me\ Close-ui_odIvVIBE.ogg | grep
  REPLAY (Won't output anything, replay gain tags got lost)

At least oggz-validate didn't complain about a broken Ogg file. Neither
before, nor after editing it with easytag.

Cheers - Bruno

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

Bug#890307: tortoisehg: needs update for mercurial 4.5

[Julien Cristau]

Control: found -1 4.5.3-1
Control: retitle -1 tortoisehg: needs update for mercurial 4.6

On Tue, Feb 13, 2018 at 10:54:42 +0100, Julien Cristau wrote:

> Package: tortoisehg
> Version: 4.4.1-1
> Severity: serious
> X-Debbugs-Cc: mithra...@mithrandi.net
> 
> tortoisehg is uninstallable in sid since mercurial was updated to 4.5.
> 
This was fixed for 4.5 a couple of weeks ago, but now 4.6 is out;
repurposing this bug.

Cheers,
Julien

Processed: Re: Bug#890307: tortoisehg: needs update for mercurial 4.5

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.5.3-1
Bug #890307 [tortoisehg] tortoisehg: needs update for mercurial 4.5
Marked as found in versions tortoisehg/4.5.3-1.
> retitle -1 tortoisehg: needs update for mercurial 4.6
Bug #890307 [tortoisehg] tortoisehg: needs update for mercurial 4.5
Changed Bug title to 'tortoisehg: needs update for mercurial 4.6' from 
'tortoisehg: needs update for mercurial 4.5'.

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

Processed: affects 898535

[Debian Bug Tracking System]

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

> affects 898535 libtinyxml2-6
Bug #898535 [src:tinyxml2] Incompatible ABI change without SONAME bump
Added indication that 898535 affects libtinyxml2-6
> thanks
Stopping processing here.

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

Bug#898547: papi-examples is not installable

[Adrian Bunk]

Package: papi-examples
Version: 5.6.0+git22-g4c23d555-1
Severity: serious

 papi-examples : Depends: libpapi-dev (< 5.6.0+git22-g4c23d555.~) but 
5.6.0+git22-g4c23d555-1 is to be installed

Bug#869994: work around solution

[Reto Schoch]

Your suggested workaround made me once again have a glimpse on the
developer's website and there I found at the top of the FAQ that he
meanwhile has a respond to this issue, namely:
perl 5.26 @INC error If you get something like this instead of the login
screen

Can't locate bin/mozilla/login.pl in @INC (@INC contains:
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at
/var/www/html/sql-ledger/login.pl line 119.

add the code below at the beginning of am.pl and login.pl if you have
symlinks to the other files in the root directory, otherwise add it to all
the scripts in the sql-ledger root directory

 BEGIN {
 push @INC, '.';
 }

Also the link inluded in message #10 is there. Unfortunately nothing is
said about the security implictions of his solution.

Am Sa., 12. Mai 2018 um 21:35 Uhr schrieb Tom Higgins :

> I ran into this problem myself and found myself reading this thread.
>
> In message #10 Gregor Herrmann posted a link about the removal of the
> current
> directory in perl-5.26.
>
> The solution to get it back is to add the following directive to the sql-
> ledger-httpd.conf file
>
> SetEnv PERL5LIB "."
>
>
> cheers,
>
> Tom Higgins
>
> --
> To unsubscribe, send mail to 869994-unsubscr...@bugs.debian.org.
>

Processed: Re: Bug#898502: ucommon: Please update symbols for riscv64 and ia64

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #898502 [src:ucommon] ucommon: Please update symbols for riscv64 and ia64
Severity set to 'normal' from 'serious'
> tags -1 patch
Bug #898502 [src:ucommon] ucommon: Please update symbols for riscv64 and ia64
Added tag(s) patch.

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

Bug#898502: ucommon: Please update symbols for riscv64 and ia64

[Adrian Bunk]

Control: severity -1 normal
Control: tags -1 patch

On Sat, May 12, 2018 at 10:00:13PM +0200, Manuel A. Fernandez Montecelo wrote:
> Source: ucommon
> Version: 7.0.0-12
> Severity: serious
> User: debian-ri...@lists.debian.org
> Usertags: riscv64
>...
> So, conjecturing a bit, to me it seems likely that it actually FTBFS in all
> arches, only that it was not detected because the last builds for these two 
> ones
> happend in the last <33 days, and for the rest many months ago (8+ months, all
> during the same days).

Builds for me on amd64.

Builds in reproducible on all 4 architectures:
https://tests.reproducible-builds.org/debian/history/ucommon.html

Lowering the severity.

> It's strange that symbols change in this way with the same GCC major version,
> the compiler was 7.2 when compiled in the other arches.  But the alternative
> explanation that the symbols are fine in all arches except in ia64 and riscv64
> is even more improbable IMO, given the additional coincidade of build dates.
>...

These have explicit architecture lists in the symbols file,
so not a real surprise when they also appear on new architectures.

A more robust solution is below.

cu
Adrian

--- debian/libucommon8.symbols.old  2018-05-13 09:18:17.048018630 +
+++ debian/libucommon8.symbols  2018-05-13 09:20:12.696017528 +
@@ -2166,16 +2166,8 @@
  (c++)"ucommon::String::unquote(char*, char const*)@Base" 7.0.0
  (c++)"ucommon::String::upper()@Base" 7.0.0
  (c++)"ucommon::String::upper(char*)@Base" 7.0.0
- (c++|arch=alpha sh4)"ucommon::String::vprintf(char const*, 
__va_list_tag)@Base" 7.0.0
- (c++|arch=amd64 kfreebsd-amd64 powerpc powerpcspe s390x 
x32)"ucommon::String::vprintf(char const*, __va_list_tag*)@Base" 7.0.0
- (c++|arch=hurd-i386 i386 kfreebsd-i386 ppc64 
ppc64el)"ucommon::String::vprintf(char const*, char*)@Base" 7.0.0
- (c++|arch=arm64 armel armhf)"ucommon::String::vprintf(char const*, 
std::__va_list)@Base" 7.0.0
- (c++|arch=hppa m68k mips mips64el mipsel 
sparc64)"ucommon::String::vprintf(char const*, void*)@Base" 7.0.0
- (c++|arch=alpha sh4)"ucommon::String::vscanf(char const*, 
__va_list_tag)@Base" 7.0.0
- (c++|arch=amd64 kfreebsd-amd64 powerpc powerpcspe s390x 
x32)"ucommon::String::vscanf(char const*, __va_list_tag*)@Base" 7.0.0
- (c++|arch=hurd-i386 i386 kfreebsd-i386 ppc64 
ppc64el)"ucommon::String::vscanf(char const*, char*)@Base" 7.0.0
- (c++|arch=arm64 armel armhf)"ucommon::String::vscanf(char const*, 
std::__va_list)@Base" 7.0.0
- (c++|arch=hppa m68k mips mips64el mipsel 
sparc64)"ucommon::String::vscanf(char const*, void*)@Base" 7.0.0
+ (c++|regex)"^ucommon::String::vprintf\(char const\*, (.+)\)@Base" 7.0.0
+ (c++|regex)"^ucommon::String::vscanf\(char const\*, (.+)\)@Base" 7.0.0
  (c++)"ucommon::String::~String()@Base" 7.0.0
  (c++|arch-bits=32)"ucommon::StringPager::StringPager(char**, unsigned 
int)@Base" 7.0.0
  (c++|arch-bits=64)"ucommon::StringPager::StringPager(char**, unsigned 
long)@Base" 7.0.0

Bug#898542: qt4-x11: FTBFS with libicu60

[John Paul Adrian Glaubitz]

Source: qt4-x11
Version: 4:4.8.7+dfsg-16
Severity: serious
Justification: fails to build from source

Hi!

qt4-x11 fails to build from source due to incompatible changes in libicu60:

g++ -c -include .pch/release-shared/QtCore -g -O2 
-fdebug-prefix-map=/<>/qt4-x11-4.8.7+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++98 
-I/usr/include/freetype2 -pthr
ead -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -O2 
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC 
-DQT_SHARED -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII 
-DQT_A
SCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER 
-DELF_INTERPRETER=\"/lib64/ld-linux-x86-64.so.2\" -DQLIBRARYINFO_EPOCROOT 
-DQT_USE_ICU -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -DQT_HAVE_MMX 
-DQT_HAVE_3DNOW -DQT_HA
VE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_HAVE_SSE3 -DQT_HAVE_SSSE3 
-DQT_HAVE_SSE4_1 -DQT_HAVE_SSE4_2 -DQT_HAVE_AVX -D_LARGEFILE64_SOURCE 
-D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++-64 -I. -I../../include 
-I../../include/QtCore -I.rc
c/release-shared -Iglobal -I../../tools/shared -I../3rdparty/harfbuzz/src 
-I../3rdparty/md5 -I../3rdparty/md4 -I.moc/release-shared -o 
.obj/release-shared/qlocale_icu.o tools/qlocale_icu.cpp
In file included from /usr/include/unicode/uversion.h:30:0,
 from tools/qlocale_icu.cpp:46:
/usr/include/unicode/umachine.h:347:13: error: 'char16_t' does not name a type; 
did you mean 'wchar_t'?
 typedef char16_t UChar;
 ^~~~
 wchar_t
In file included from tools/qlocale_icu.cpp:46:0:
/usr/include/unicode/uversion.h:167:55: error: 'UChar' does not name a type; 
did you mean 'QChar'?
 u_versionFromUString(UVersionInfo versionArray, const UChar *versionString);
   ^
   QChar
In file included from /usr/include/unicode/unorm.h:24:0,
 from /usr/include/unicode/ucol.h:17,
 from tools/qlocale_icu.cpp:47:
/usr/include/unicode/uiter.h:594:44: error: 'UChar' does not name a type; did 
you mean 'QChar'?
 uiter_setString(UCharIterator *iter, const UChar *s, int32_t length);
^
QChar

I first discovered this issue on m68k [1], but also made a test build on amd64
to make sure this bug is not an artifact.

I unfortunately don't have a patch yet to address this issue.

Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=qt4-x11=m68k=4%3A4.8.7%2Bdfsg-16=1526192657=0

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: bug 898535 is forwarded to https://github.com/leethomason/tinyxml2/issues/674

[Debian Bug Tracking System]

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

> forwarded 898535 https://github.com/leethomason/tinyxml2/issues/674
Bug #898535 [src:tinyxml2] Incompatible ABI change without SONAME bump
Set Bug forwarded-to-address to 
'https://github.com/leethomason/tinyxml2/issues/674'.
> thanks
Stopping processing here.

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

Bug#898518: marked as done (why silently dropped the ppc64el and s390x builds)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 09:24:35 +
with message-id 
and subject line Bug#898518: fixed in why 2.40-3
has caused the Debian Bug report #898518,
regarding why silently dropped the ppc64el and s390x builds
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.)


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

why silently dropped the ppc64el and s390x builds, the changelog doesn't tell a
word about it.  This hinders propagation of the package to testing.
--- End Message ---
--- Begin Message ---
Source: why
Source-Version: 2.40-3

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

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

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated why package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 May 2018 10:55:19 +0200
Source: why
Binary: why libwhy-coq
Architecture: source
Version: 2.40-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Description:
 libwhy-coq - Why library for Coq
 why- Software verification tool for C and Java
Closes: 898493 898518
Changes:
 why (2.40-3) unstable; urgency=medium
 .
   * Update Architecture to native archs of ocaml 4.05:
 - drop armel (closes: #898493)
 - restore ppc64el, s390x (closes: #898518)
 - add ppc64
Checksums-Sha1:
 4928f849ba50d6e6347df14ee1c0d11226ac1709 2374 why_2.40-3.dsc
 a21c16814b8a155176be1acab69ae9bc79ac9714 11872 why_2.40-3.debian.tar.xz
 0a903971875f1584480441ec1773271ad77e2454 8983 why_2.40-3_source.buildinfo
Checksums-Sha256:
 c918a172195b182159814aaae911ad50d64330e27e70f2002b7bbb6263a0aeee 2374 
why_2.40-3.dsc
 6b6a5bfd3338066549d3d6266dcc038d8119e78649fb2be1cc36a8735d29b928 11872 
why_2.40-3.debian.tar.xz
 9d5a6ccef4b4c780f765f9ac15173d2a6a85a1573bfa2bf6e405d8dda7cb29c4 8983 
why_2.40-3_source.buildinfo
Files:
 d4fead1e65dc55cef7baa877e6ec4508 2374 math optional why_2.40-3.dsc
 ac8df73fe9c614a256e80357f269067d 11872 math optional why_2.40-3.debian.tar.xz
 1e17ffe032d59c73e7c6af04c919543c 8983 math optional why_2.40-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAlr3/yQACgkQdFxHZtTK
zf+E+w//bgFe9eoLpvTyErFjcmtVPqFkz+ts+POXKT+NVA/DfOgtSmU7kBOzy2Sa
LrpHhGk+B3rU06mjPlwEz+nU7txaZe7OpSv0JGZxUzYX8mt339jQnjzM/Q/uNE4/
n2TCeFmTBoHXShna6NETz8x5aC7N8q/1ZBoT9+X85LEiaPUac81yyhHvtJ4oXcJS
LCieLXkdTv2xRjCSZXArcxWNdCu01OnyeO39chLTHuMzwI7xplzDLiKRgHAPjGgT
VLZfyT0mw/+Z5Is80Zhm8UKQkzmnFC8K0UhXGcWashX9SxRzWakVxg6ShLtSmO9+
3xFFG5C73oqtLWZI2OxZGGVHnpR3m4viYncfKZGbCiUrMMDgkV/lvMkrny3Cp2Dx
pHuyP1pXC0wCnM1qrRfxkavw6xuChZkd1iugmVVdTe0/X5yGU1f2nxZ/kZA5fZIc
yQMFLZ3hXq9RcKokBcfKh2JfGTuf7c6huHRIe77SliVaTX8O5EnTB0LTVPymGL04
3B3y3D7cfrTfdqipDYnWxY+Y4Kky85eVdDgYV1pexY07WfgN7yisUt272qwFyQ35
JYxhBVnmDCftqYT6RA75rwD92Y1z4jEspJ5QGG9ah8ACB5AAdKywbshnR3CimkgS
8bdnSvpAWAzTZ52j6EkkpiVh1Y690hIVXq9AdTO/uUKGMgup9BI=
=hIYz
-END PGP SIGNATURE End Message ---

Bug#898327: marked as done (cppcheck: *** stack smashing detected ***: terminated)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 09:21:31 +
with message-id 
and subject line Bug#898327: fixed in cppcheck 1.83-2
has caused the Debian Bug report #898327,
regarding cppcheck: *** stack smashing detected ***:  terminated
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.)


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

Package: cppcheck
Version: 1.83-1
Severity: grave

cppcheck seems to crash on every file:

  $ cppcheck /dev/null
  *** stack smashing detected ***:  terminated
  Aborted

Backtrace:

#0  0xf7fd5059 in __kernel_vsyscall ()
#1  0xf7adb5b2 in __libc_signal_restore_set (set=0xc2fc) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
#2  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
#3  0xf7adc9d1 in __GI_abort () at abort.c:79
#4  0xf7b1d273 in __libc_message (action=do_abort, fmt=) at 
../sysdeps/posix/libc_fatal.c:181
#5  0xf7bb606a in __GI___fortify_fail_abort (need_backtrace=false, msg=0xf7c2c0b3 
"stack smashing detected") at fortify_fail.c:33
#6  0xf7bb601b in __stack_chk_fail () at stack_chk_fail.c:29
#7  0x56799244 in __stack_chk_fail_local ()
#8  0x566b5303 in Library::load (this=0xcf98, exename=0xd799 "/usr/bin/cppcheck", 
path=0x567bab8f "std.cfg") at lib/library.cpp:116
#9  0x56777bf7 in CppCheckExecutor::tryLoadLibrary (destination=..., basepath=0xd799 
"/usr/bin/cppcheck", filename=0x567bab8f "std.cfg") at 
cli/cppcheckexecutor.cpp:1062
#10 0x5677a160 in CppCheckExecutor::check_internal (this=0xd384, 
cppcheck=..., argv=0xd5a4) at cli/cppcheckexecutor.cpp:814
#11 0x5677b9f4 in CppCheckExecutor::check (this=0xd384, argc=2, 
argv=0xd5a4) at cli/cppcheckexecutor.cpp:199
#12 0x56597f13 in main (argc=2, argv=0xd5a4) at cli/main.cpp:136


-- System Information:
Architecture: i386

Versions of packages cppcheck depends on:
ii  libc6 2.27-3
ii  libgcc1   1:8.1.0-1
ii  libpcre3  2:8.39-9
ii  libstdc++68.1.0-1
ii  libtinyxml2-6 6.2.0+dfsg-1
ii  python3   3.6.5-3
ii  python3-pygments  2.2.0+dfsg-1

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: cppcheck
Source-Version: 1.83-2

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

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

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

Debian distribution maintenance software
pp.
Joachim Reichel  (supplier of updated cppcheck package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 May 2018 10:29:45 +0200
Source: cppcheck
Binary: cppcheck cppcheck-gui
Architecture: source
Version: 1.83-2
Distribution: unstable
Urgency: medium
Maintainer: Joachim Reichel 
Changed-By: Joachim Reichel 
Description:
 cppcheck   - tool for static C/C++ code analysis (CLI)
 cppcheck-gui - tool for static C/C++ code analysis (GUI)
Closes: 898327
Changes:
 cppcheck (1.83-2) unstable; urgency=medium
 .
   * Add versioned Build-Depends: libtinyxml2-dev (>= 6.2.0+dfsg-1). The
 layout of tinyxml2::XMLDocument was changed between 6.0.0 and 6.2.0
 without bumping the SONAME (Closes: #898327).
Checksums-Sha1:
 2a5aaedd42ca544a7f1015e38e50cf2522120710 1959 cppcheck_1.83-2.dsc
 ed76329b2d6cc96f5314b8606e8f7d65b85da1fd 368552 cppcheck_1.83-2.debian.tar.xz
Checksums-Sha256:
 5165681ea14981abfb18176690a0114ed4b90a6201f50a8dbaab0d765aa50dbf 1959 
cppcheck_1.83-2.dsc
 5cca84200af9d8b010132b705bf8913f4c3fef088210c5bf3a562d809bd458dc 368552 
cppcheck_1.83-2.debian.tar.xz
Files:
 c3d34554e06fd19ba4aa02757528ba16 1959 devel optional cppcheck_1.83-2.dsc
 30eb4d7c366ab871ab7649adfc108236 368552 devel optional 
cppcheck_1.83-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAlr3/J8ACgkQuPr/HEOI
Z3HUJBAAhGZ8/IFl/r8sPI0glrPxeOHQZuTrpu5S07BW29MYgrvKJAwEUOiPp4qq
NOQjsMwnRN0DeDpiTer7bgya2fXQ0iAvwAglP3CB8uUJpSZjsWjV+pk2NO38bQ3Y
Z5yUhlH+uzM4svpQlKJsTl9ySzzv3l60kTvb+3f543N6XP6mwwXLU8pR5mX66WMh

Bug#898327: cppcheck: *** stack smashing detected ***: terminated

[Joachim Reichel]

Hi Jakub,

I confirm that the crash goes away if libtinyxml2-6 is downgraded to
6.0.0+dfsg-1. Thanks for finding the real cause!

I've filed bug 898535 against tinyxml2. I've added a versioned Build-Depends to
cppcheck as workaround.

  Joachim

Bug#896860: marked as done (lammps FTBFS with TeX Live 2018)

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 08:57:30 +
with message-id 
and subject line Bug#896860: fixed in lammps 0~20180510.gitaa1d815fe-2
has caused the Debian Bug report #896860,
regarding lammps FTBFS with TeX Live 2018
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.)


-- 
896860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lammps
Version: 0~20161109.git9806da6-7
Severity: serious
Tags: buster sid patch

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

...
! Package inputenc Error: Invalid UTF-8 byte sequence.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
 ...  
  
l.479 ...our header the same way. Otherwise, don�t
  
?


Fix is attached.
Description: Fix non-ASCII character in developer.tex
 This caused a FTBFS with TeX Live 2018.
Author: Adrian Bunk 

--- lammps-0~20161109.git9806da6.orig/doc/src/Developer/developer.tex
+++ lammps-0~20161109.git9806da6/doc/src/Developer/developer.tex
@@ -476,7 +476,7 @@ is the name of the class. This code allo
 when it parses input script. In addition, your fix header must be
 included in the file "style\_fix.h". In case if you use LAMMPS make,
 this file is generated automatically - all files starting with prefix
-fix\_ are included, so call your header the same way. Otherwise, donÕt
+fix\_ are included, so call your header the same way. Otherwise, don't
 forget to add your include into "style\_fix.h".
  
 Let's write a simple fix which will print average velocity at the end
--- End Message ---
--- Begin Message ---
Source: lammps
Source-Version: 0~20180510.gitaa1d815fe-2

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated lammps 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: Sun, 13 May 2018 10:09:09 +0200
Source: lammps
Binary: lammps lammps-doc
Architecture: source
Version: 0~20180510.gitaa1d815fe-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 lammps - Molecular Dynamics Simulator
 lammps-doc - Molecular Dynamics Simulator. Documentation and examples
Closes: 896860
Changes:
 lammps (0~20180510.gitaa1d815fe-2) unstable; urgency=medium
 .
   * [dfd9a8b] Fix FTBFS on most platforms. (Closes: #896860)
Checksums-Sha1:
 df39c27267ef076db48a4012df65b2b08aea7b2b 2233 
lammps_0~20180510.gitaa1d815fe-2.dsc
 f4c3c68ed17424d322352860eb23f27f52a51fb4 13948 
lammps_0~20180510.gitaa1d815fe-2.debian.tar.xz
 71c1072f80a697651e46a5a473f4fedf781af18e 7280 
lammps_0~20180510.gitaa1d815fe-2_source.buildinfo
Checksums-Sha256:
 b66bcfa953a66d42f9eef2506503784fceb2bb211c11f06c354237ab817e3fc4 2233 
lammps_0~20180510.gitaa1d815fe-2.dsc
 b8a35dbb04a03a6c1432069def868e97d7a965064ef2d29df8dda846ee9d065c 13948 
lammps_0~20180510.gitaa1d815fe-2.debian.tar.xz
 3b9d1a36548018a4aa04409e31d4dc89c8da070f3189a882c07d856707101697 7280 
lammps_0~20180510.gitaa1d815fe-2_source.buildinfo
Files:
 69caf4a56da24a2dbf611f09cd1506c0 2233 science optional 
lammps_0~20180510.gitaa1d815fe-2.dsc
 eb71e83d9cc1a437f22487ed5a197374 13948 science optional 
lammps_0~20180510.gitaa1d815fe-2.debian.tar.xz
 dece9374b06f80a92baab97746acadfe 7280 science optional 
lammps_0~20180510.gitaa1d815fe-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlr38xIACgkQ0+Fzg8+n
/wYMnw/+MsxhKAby3kIUIQE+0q/Z9UBJFuHRqpwAVKaovXryCJ4mjRudmz/836Cg
nYIfzYQVVJr1zeMoEfMaNjBTNIc4Mhhtx94lv+sSRfzWXsOPFwEUH5+78C9qsUw/
gFUkAeVvh2bofYatUWbcA2S3Oww5pk4VcVkXUMW9oDpHOPFHdP4kvaVHF/knZ2TM

Bug#898535: Incompatible ABI change without SONAME bump

[Joachim Reichel]

Source: tinyxml2
Version: 6.2.0+dfsg-1
Severity: grave
Tags: upstream

Hi,

the layout of tinyxml::XMLDocument has been changed between version 6.0.0 and
6.2.0 (addition of _parsingDepth member). Unfortunately, the SONAME has not
been bumped. This can cause applications built against version 6.0.0 to crash
when running with version 6.2.0. See bug 898327 for an example.

Please discuss this with upstream. Maybe they could release 6.2.1 with bumped
SONAME?

Please inform the reverse dependencies of tinyxml2 about the problem.

  Joachim

-- System Information:
Debian Release: 9.4
  APT prefers stable-debug
  APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), 
(700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Processed: affects 898501

[Debian Bug Tracking System]

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

> affects 898501 src:cider
Bug #898501 [fonts-font-awesome] Broken symlinks
Added indication that 898501 affects src:cider
> thanks
Stopping processing here.

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

Bug#866489: marked as done (twms: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Sun, 13 May 2018 07:35:35 +
with message-id 
and subject line Bug#866489: fixed in twms 0.06y-1
has caused the Debian Bug report #866489,
regarding twms: depends on obsolete python-imaging (replace with python3-pil or 
python-pil)
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.)


-- 
866489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:twms
Version: 0.05t-4
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: twms
Source-Version: 0.06y-1

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twms package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 May 2018 09:24:01 +0200
Source: twms
Binary: twms
Architecture: source
Version: 0.06y-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Description:
 twms   - tiny web map service
Closes: 866489
Changes:
 twms (0.06y-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #866489).
   * Refresh the patches.
   * Switch to Python 3.
   * Update debian/copyright.
   * Update the homepage.
   * Update Vcs-*.
Checksums-Sha1:
 d450203b28a413707314b5476cbac41903618142 1596 twms_0.06y-1.dsc
 13a9934146f32778c771ffa5af62a99267335edf 30018 twms_0.06y.orig.tar.gz
 4383655ae956cd436935b823e453b62cc17c2ac9 5168 twms_0.06y-1.debian.tar.xz
Checksums-Sha256:
 5f58ad6cb1325790974a77d91a9d677e8c00100798fa6df9381d63e5af92d664 1596 
twms_0.06y-1.dsc
 bc699f8a947d4e240c8a2b7944893bdf5690de8f57d633f8e2300cfc00e39a71 30018 
twms_0.06y.orig.tar.gz
 5412e9bfdf380faea666376ffc74ba080c160c477215e02f3e19e860568ae473 5168 
twms_0.06y-1.debian.tar.xz
Files:
 b892215960ddccf8f6924195e8746007 1596 science extra twms_0.06y-1.dsc
 21dc9ebc89930e864288da29dcb507f0 30018 science extra twms_0.06y.orig.tar.gz
 b93f1afec800b321103be6aac3644915 5168 science extra twms_0.06y-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlr36KsACgkQXkCM2RzY
OdLrwQf/frx6KtojxiYxERgIcugqM803FO9/H1w5jT6ZbQJBkEodwzsquqzTbRn1
uwTX4aJY8UG5OcOLWRWZd3P9syKKLyMh3AKhnB4YHKQAGHPOWdlwmV7kLiuy6uBc
G4UpxA0Bff9W/uGzG8ny3nldvUL/qt0m23lVQQ2aP2E6IPGFawLcgmgIN3jmKmpn
tf6PKI+D/7j/JUhZdEQ4EqPp1Du3txnxPoO1IKcMAdyqhvk5PDk1qLcqQo3sJUsI
/xvggrQYPWdJ2beeAq3kuYzzl13UGXlcrziY3JuArtyugdy/D+b+XTtcW6yrK/6G
+VdXq0l95JkNom9ICAOvA3FfqoamIQ==
=45Bp
-END PGP SIGNATURE End Message ---

Bug#896921: Salt 2017.7.5 has been released

[Dirk Heinrichs]

Hi,

could the version be bumped, then?

Thanks...

Dirk
-- 
Dirk Heinrichs 
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de



signature.asc
Description: OpenPGP digital signature