Processed: Toulbar2 issue is caused by doxygen 'cascade of FTBFS'

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Doxygen breaks toulbar2
Bug #920459 [src:toulbar2] toulbar2 ftbfs in unstable
Changed Bug title to 'Doxygen breaks toulbar2' from 'toulbar2 ftbfs in 
unstable'.
> affects 921779 toulbar2
Bug #921779 [src:doxygen] cascade of FTBFS
Added indication that 921779 affects toulbar2
> reassign -1 doxygen
Bug #920459 [src:toulbar2] Doxygen breaks toulbar2
Bug reassigned from package 'src:toulbar2' to 'doxygen'.
No longer marked as found in versions toulbar2/1.0.0+dfsg3-1.1 and 
toulbar2/1.0.0+dfsg3-1.
Ignoring request to alter fixed versions of bug #920459 to the same values 
previously set

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

Bug#920459: Toulbar2 issue is caused by doxygen 'cascade of FTBFS'

[Andreas Tille]

Control: retitle -1 Doxygen breaks toulbar2
Control: affects 921779 toulbar2
Control: reassign -1 doxygen

Hi,

I've verified the situation of the build failure and it
shows the typical problem caused by bug #921779.  Thus
I'm reassigning the bug to doxygen.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: Bug #922395 in smokeping marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #922395 [smokeping] smokeping: fails to stop and to upgrade: 
start-stop-daemon: matching only on non-root pidfile 
/var/run/smokeping/smokeping.pid is insecure
Added tag(s) pending.

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

Bug#922395: Bug #922395 in smokeping marked as pending

[LeLutin]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/smokeping/commit/69a945131f7f7a94e137c85fa957a029cecd8dc9


init.d: match on pidfile only prevents service stop (closes: #922395)

dpkg 1.19.3 introduced a new verification that prevents the service to
stop using the init script (and incidentally to run reconfigure
correctly): the pidfile is not owned by root:root, so s-s-d is wary of
relying only on this information to run a command as root with the
information within the file.

By matching the service more precisely, that is with pidfile and exec
name, start-stop-daemon is more at ease and performs service stop
action.

While changing that command, I also saw that the init script was not
reusing the $PIDFILE variable for the stop command. This could have
been a source of mistake if we ever had to change where the pidfile is
placed on the filesystem.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/922395

Bug#922395: smokeping: fails to stop and to upgrade: start-stop-daemon: matching only on non-root pidfile /var/run/smokeping/smokeping.pid is insecure

[Gabriel Filion]

On 2019-02-15 10:33 p.m., Gabriel Filion wrote:
> On 2019-02-15 7:53 a.m., Axel Beckert wrote:
>> sorry for the late report, but smokeping failed to configure (probably
>> after the recent upgrade) for a few days for me now:
>>
>> # dpkg --configure -a
>> Setting up smokeping (2.7.3-1) ...
>> apache2_invoke: Enable module cgi
>> [ ok ] Restarting Apache httpd web server: apache2
>> apache2_invoke smokeping: already enabled
>> [ ok ] Reloading Apache httpd web server: apache2.
>> [] Shutting down latency logger daemon: smokepingstart-stop-daemon: 
>> matching only on non-root pidfile /var/run/smokeping/smokeping.pid is 
>> insecure
> 
>> This seems to happen since dpkg 1.19.3. According changelog entry:
> 
> Thanks for bringing this to our attention!
> 
> dpkg 1.19.3 was migrated to testing only a couple days before smokeping
> 2.7.3-1, so maybe when Antoine and I were working on this release our
> tests were running on a previous dpkg version: I've tested out an
> install of smokeping on a fresh install with the init script but I
> didn't notice any error about the pid.
> 
> I'll run more tests to try and reproduce this.

I was able to reproduce this bug by switching an amd64 debian sid VM to
boot using sysvinit, and then to run "dpkg-reconfigure smokeping"

when using the systemd unit, the pid file is owned by root:root and
we're not encountering this issue.

I've found an example for a fix in #920466 that worked for me: adding
"--exec $DAEMON" to the s-s-d command that stops the daemon makes it
possible to stop the daemon without error.

I'll push this fix to salsa and ask for Antoine to review and upload.



signature.asc
Description: OpenPGP digital signature

Bug#921200: marked as done (vkd3d: misses dependency on libvulkan1)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 04:04:10 +
with message-id 
and subject line Bug#921200: fixed in vkd3d 1.1-3
has caused the Debian Bug report #921200,
regarding vkd3d: misses dependency on libvulkan1
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.)


-- 
921200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vkd3d
Version: 1.1-2
Severity: normal


[resend to the bts]

Hi Mike

On 02.02.19 08:56, Michael Gilbert wrote:
> On Fri, Feb 1, 2019 at 10:38 PM Jens Reyer wrote:
>> vkd3d has no runtime dependency on libvulkan1 or any other vulkan
>> related packages.  So with the currently existing package relationships
>> you can build vkd3d with newer vulkan and then install it next to wine
>> with older vulkan.[1]
> 
> This is an error in the packaging.  Vulkan is loaded via dlopen, so an
> explicit dependency is needed but missing.  That could be automated as
> is done in wine with sonames2elf.

Ah, now I understand, thanks! Filing this as a bug for now.

I had a first look into libvulkan1' symbols and (if I get this
correctly) it seems symbols get frequently dropped.  I'll have to talk
vulkan's maintainers about that.

Greets
jre
--- End Message ---
--- Begin Message ---
Source: vkd3d
Source-Version: 1.1-3

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated vkd3d 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, 16 Feb 2019 02:11:35 +
Source: vkd3d
Architecture: source
Version: 1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 919889 921200
Changes:
 vkd3d (1.1-3) unstable; urgency=medium
 .
   [ Jens Reyer ]
   * Update copyright info.
   * Add myself to uploaders.
   * Add Vcs fields to d/control.
   * Add "or later" to license LGPL-2.1.
   * Add Build-Depends-Package field to symbols files.
   * Strip unnecessary signature from upstream signing key.
   * Make build-dependency on libvulkan-dev versioned (closes: #919889).
 .
   [ Michael Gilbert ]
   * Include debian revision in the version string.
   * Add missing vulkan dependency (closes: #921200).
Checksums-Sha1:
 76d23236a5033af13e1ba22fc043dd8b1b83dab6 2879 vkd3d_1.1-3.dsc
 62925dd932273b3346ee286dc6b365f0e888a742 6172 vkd3d_1.1-3.debian.tar.xz
 70b9d1bb9a52c84da7077cafed78976ea0045b6a 6799 vkd3d_1.1-3_source.buildinfo
Checksums-Sha256:
 26271b3e5886a0fd82b503b81d878d6f652a56b34581b6df2409e16d001d0040 2879 
vkd3d_1.1-3.dsc
 2156de03a3403e0c9fc7db2cea3e2430a25d4fe579a22cd74614c2be13fb5c12 6172 
vkd3d_1.1-3.debian.tar.xz
 bbeaf6a965d05771ed0f02f1ca8b174a1744b75e3129bcccfcd1de2bea7c6100 6799 
vkd3d_1.1-3_source.buildinfo
Files:
 2a826f95420c0acd8d5fe1ff72b37dc7 2879 libs optional vkd3d_1.1-3.dsc
 479d209f672f65d550e1ca6b1e869f3a 6172 libs optional vkd3d_1.1-3.debian.tar.xz
 2c896dbb7f2e9b1de82cbcf2818960fc 6799 libs optional 
vkd3d_1.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAlxnifAACgkQuNayzQLW
9HOONB/+KqVN9nAGCGZMv1iZWGXxcMkRLnrVXtwJqNDNxb4MDpY5Avbclo6O92ON
cwQSUuQ5qAT2VfogxnCaAlo2xJnTW7sP/LanJQI/chHRv7n/n7CSffwfkfjN6ZPS
lCeW0vEd/lDSmVPt46Obil0zMR+IPf2qqy3JAyGj0Zk8IX7mXbkIRQ0PSzU0u7ow
edjRxt/UQMqGHPDAu4OeoqDDt2+qctvXgDMHEC5SzXXmlSugV7UR1v03UsKr6OnW
xqI7YWTDIPmQmQ5j1XusUnvtB6J7BYlpnk38VV4gfXXG3vuplR8ZokF6GYHSj2Lv
iOTjmvGl3IAPdHotSZn2YNgSDRLN98DUrwrvJJ37TitUNVeOGuyQwBG78rrSthGk
Y4oQtg750cqIiRN5Q3LAS3dbO5+6rIfvVvh8iKblFAZ3LmWXVNAg2GHjn4d8kWWs
C4OJLtSkC2t9Sa4APeLwzDmOwNwPrFmwgtEbjxbQAT4xRhOo7jaGV+6NkNEkWtJ2
V33VrhV4M9ANXAURqE62eRbbNOAaGI8wsV1j7rfyVsfuJZhrBy5VS/k/goRqkMq/
ynIM1nQrX9Aut54cbG6a3jvUosVZa4xTx9rV5S6qnb9rAQdcegmOhqZZsv5AVrC6
MyNQSNODU3pWIocEm8NZGjuggQgnQIXwXKe2mIoUrCvOpmPdzO0A4Yu5Dg1ZpMB6
O0+7XA5Kah5bHq81J/G9SmctahObxa/ZU3jVr0u1A7ItGm3vsNMCZ3btXZace6mp
tn869Hnui8gSRVZPoYQQMqYq1V2Ml8NEqk412TSWgW6Xiz1Mn66jDMmOcmDEs6Tb
GXtFhQvKy+Y8SliVOVMRjZZDy57lSdmxJQ8btFK44iS1/L8bRPennxMgYgBnp3zb

Bug#922395: smokeping: fails to stop and to upgrade: start-stop-daemon: matching only on non-root pidfile /var/run/smokeping/smokeping.pid is insecure

[Gabriel Filion]

Hello,

On 2019-02-15 7:53 a.m., Axel Beckert wrote:
> sorry for the late report, but smokeping failed to configure (probably
> after the recent upgrade) for a few days for me now:
> 
> # dpkg --configure -a
> Setting up smokeping (2.7.3-1) ...
> apache2_invoke: Enable module cgi
> [ ok ] Restarting Apache httpd web server: apache2
> apache2_invoke smokeping: already enabled
> [ ok ] Reloading Apache httpd web server: apache2.
> [] Shutting down latency logger daemon: smokepingstart-stop-daemon: 
> matching only on non-root pidfile /var/run/smokeping/smokeping.pid is insecure

> This seems to happen since dpkg 1.19.3. According changelog entry:

Thanks for bringing this to our attention!

dpkg 1.19.3 was migrated to testing only a couple days before smokeping
2.7.3-1, so maybe when Antoine and I were working on this release our
tests were running on a previous dpkg version: I've tested out an
install of smokeping on a fresh install with the init script but I
didn't notice any error about the pid.

I'll run more tests to try and reproduce this.



signature.asc
Description: OpenPGP digital signature

Processed: re: Wine + AnyRail 6.1 - messing up KDE Desktop

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #922207 [wine-development] Wine + AnyRail 6.1 - messing up KDE Desktop
Added tag(s) moreinfo.
> severity -1 minor
Bug #922207 [wine-development] Wine + AnyRail 6.1 - messing up KDE Desktop
Severity set to 'minor' from 'critical'

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

Bug#922207: Wine + AnyRail 6.1 - messing up KDE Desktop

[Michael Gilbert]

control: tag -1 moreinfo
control: severity -1 minor

This sounds a lot like this upstream bug:
https://bugs.winehq.org/show_bug.cgi?id=23676

It is in a different app and only seen with mesa and ati drivers, not
nvidia.  Which driver do you use?

Does AnyRail allow you to disable 3d rendering?

Best wishes,
Mike

Bug#915311: dumb-init FTBFS on mips*: test failures

[Shengjing Zhu]

Hi,

I've uploaded this NMU to DELAYED/2-day. Hope it works.

On Thu, Feb 14, 2019 at 1:03 AM Shengjing Zhu  wrote:
>
> diff -Nru dumb-init-1.2.2/debian/changelog dumb-init-1.2.2/debian/changelog
> --- dumb-init-1.2.2/debian/changelog2019-01-27 14:30:06.0 +0800
> +++ dumb-init-1.2.2/debian/changelog2019-02-14 00:50:21.0 +0800
> @@ -1,3 +1,10 @@
> +dumb-init (1.2.2-1.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Add patch to fix tests on slow machines. (Closes: #915311)
> +
> + -- Shengjing Zhu   Thu, 14 Feb 2019 00:50:21 +0800
> +
>  dumb-init (1.2.2-1) unstable; urgency=medium
>
>[ Ondřej Nový ]
> diff -Nru dumb-init-1.2.2/debian/patches/increase-test-sleep-time.patch 
> dumb-init-1.2.2/debian/patches/increase-test-sleep-time.patch
> --- dumb-init-1.2.2/debian/patches/increase-test-sleep-time.patch   
> 1970-01-01 08:00:00.0 +0800
> +++ dumb-init-1.2.2/debian/patches/increase-test-sleep-time.patch   
> 2019-02-14 00:50:21.0 +0800
> @@ -0,0 +1,18 @@
> +Description: increase test sleep time
> + The test will fail on some slow machines if the sleep time
> + is too short.
> +Author: Shengjing Zhu 
> +Bug-Debian: https://bugs.debian.org/915311
> +Last-Update: 2019-02-14
> +
> +--- dumb-init-1.2.2.orig/tests/child_processes_test.py
>  dumb-init-1.2.2/tests/child_processes_test.py
> +@@ -80,7 +80,7 @@ def spawn_process_which_dies_with_childr
> + # we need to sleep before the shell exits, or dumb-init might 
> send
> + # TERM to print_signals before it has had time to register 
> custom
> + # signal handlers
> +-'{python} -m testing.print_signals & sleep 0.1'.format(
> ++'{python} -m testing.print_signals & sleep 1'.format(
> + python=sys.executable,
> + ),
> + ),
> diff -Nru dumb-init-1.2.2/debian/patches/series 
> dumb-init-1.2.2/debian/patches/series
> --- dumb-init-1.2.2/debian/patches/series   2019-01-27 14:20:28.0 
> +0800
> +++ dumb-init-1.2.2/debian/patches/series   2019-02-14 00:46:35.0 
> +0800
> @@ -1 +1,2 @@
>  build.patch
> +increase-test-sleep-time.patch

-- 
Shengjing Zhu

Processed: Re: Bug#921680: ufw cannot determine iptables version, fails

[Debian Bug Tracking System]

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

> tags 921680 +moreinfo
Bug #921680 [ufw] ufw cannot determine iptables version, fails
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: Re: Bug#921680: ufw cannot determine iptables version, fails

[Debian Bug Tracking System]

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

> severity 921680 normal
Bug #921680 [ufw] ufw cannot determine iptables version, fails
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#921680: ufw cannot determine iptables version, fails

[Jamie Strandboge]

On Thu, 07 Feb 2019, PanaColina wrote:

> Package: ufw
> Version: 0.36-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> On clean new install of ufw, any ufw command
> (eg: "ufw status") results in:
> "ERROR: Couldn't determine iptables version"
> 
> Additional packages automatically installed at the same time:
>  iptables 1.8.2-3
>  libnftables0 0.9.0-2
>  libnftnl11 1.1.2-2
>  nftables 0.9.0-2
> 
> Assuming some conflict, I removed nftables and libnftables0, but error
> persists.
> 
> ufw is set as dependent on libnftnl11, and of course iptables
> 

I cannot reproduce this with the current 4.19 kernel or on an older 4.17 kernel
(like you have-- you may want to consider upgrading).

$ dpkg -l|grep -E '(ufw|iptables|nft)'|awk '{print $1, $2, $3}'
ii iptables 1.8.2-3
ii libnftables0:amd64 0.9.0-2
ii libnftnl11:amd64 1.1.2-2
ii libnftnl7:amd64 1.1.1-1
ii nftables 0.9.0-2
ii ufw 0.36-1

$ /sbin/iptables --version
iptables v1.8.2 (nf_tables)

$ sudo ufw status
Status: inactive

$ sudo ufw enable
Firewall is active and enabled on system startup

$ sudo ufw status
Status: active

To Action  From
-- --  
22/tcp ALLOW   Anywhere
22/tcp (v6)ALLOW   Anywhere (v6)


It continues to work with iptables-legacy (using update-alternatives; I updated
the alternative, ran ufw disable and rebooted):

$ /sbin/iptables --version
iptables v1.8.2 (legacy)

$ sudo ufw status
Status: inactive

$ sudo ufw enable
Firewall is active and enabled on system startup

$ sudo ufw status
Status: active

To Action  From
-- --  
22/tcp ALLOW   Anywhere
22/tcp (v6)ALLOW   Anywhere (v6)


What is the output of 'sudo /usr/share/ufw/check-requirements'?

What is the output of '/sbin/iptables --version'?


> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.17.17 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages ufw depends on:
> ii  debconf [debconf-2.0]  1.5.70
> ii  iptables   1.8.2-3
> ii  lsb-base   10.2018112800 
> ii  python33.7.2-1
> ii  ucf3.0038+nmu1
> 
> ufw recommends no packages.
> 
> Versions of packages ufw suggests:
> ii  rsyslog  8.40.0-1+b1
> 
> -- debconf information:
>   ufw/existing_configuration:
>   ufw/allow_known_ports:
>   ufw/enable: false
>   ufw/allow_custom_ports:
-- 
Jamie Strandboge | http://www.canonical.com


signature.asc
Description: PGP signature

Bug#921793: marked as done (mono-tools: FTBFS (error CS0618: Warning as Error))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 21:04:39 +
with message-id 
and subject line Bug#921793: fixed in mono-tools 4.2-3
has caused the Debian Bug report #921793,
regarding mono-tools: FTBFS (error CS0618: Warning as Error)
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.)


-- 
921793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mono-tools
Version: 4.2-2.2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autoreconf,xsp,cli
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   dh_autoreconf -i
sh: 1: ACLOCAL_FLAGS: not found
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libexecdir=\${prefix}/lib/mono-tools 
--disable-maintainer-mode --disable-dependency-tracking
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu

[... snipped ...]

Member Added: public readonly Gendarme.Framework.Helpers.MethodSignature 
Subscript;
Member Added: public readonly Gendarme.Framework.Helpers.MethodSignature Sort;
Member Added: public override void Initialize (Gendarme.Framework.IRunner 
runner);
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseIsOperatorRule
Member Added: public UseIsOperatorRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseStringEmptyRule
Member Added: public UseStringEmptyRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
New Type: Gendarme.Rules.Performance.UseTypeEmptyTypesRule
Member Added: public UseTypeEmptyTypesRule ();
Member Added: public Gendarme.Framework.RuleResult CheckMethod 
(Mono.Cecil.MethodDefinition method);
Members Added: 86, Members Deleted: 0
touch doc/generated/index.xml
mdoc assemble -f ecma -o doc/Gendarme.Rules.Performance doc/generated 
echo -e "\n\n\t\n\t\n" > 
doc/Gendarme.Rules.Performance.source 
make[5]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Performance'
make[4]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Performance'
Making all in Gendarme.Rules.Portability
make[4]: Entering directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability'
Making all in Test
make[5]: Entering directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability/Test'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability/Test'
make[5]: Entering directory 
'/<>/gendarme/rules/Gendarme.Rules.Portability'
/usr/bin/mono-csc -target:library -debug+ -d:TRACE -optimize+ -nowarn:1591  
-warn:4 -warnaserror+ -r:ICSharpCode.SharpZipLib.dll -r:System.Web.Services.dll 
-nowarn:1591 -doc:../../bin/Gendarme.Rules.Portability.dll.doc \
-r:/usr/lib/mono-cecil/Mono.Cecil.dll 
-r:/usr/lib/mono-cecil/Mono.Cecil.Mdb.dll 
-r:/usr/lib/mono-cecil/Mono.Cecil.Pdb.dll 
-r:/usr/lib/mono-cecil/Mono.Cecil.Rocks.dll -r:../../bin/Gendarme.Framework.dll 
-out:../../bin/Gendarme.Rules.Portability.dll ./DoNotHardcodePathsRule.cs 
./ExitCodeIsLimitedOnUnixRule.cs ./FeatureRequiresRootPrivilegeOnUnixRule.cs 
./MoMAWebService.cs ./MonoCompatibilityReviewRule.cs ./NewLineLiteralRule.cs 
../../AssemblyInfo.cs ./../../AssemblyStaticInfo.cs
./MonoCompatibilityReviewRule.cs(179,11): error CS0618: Warning as Error: 
`ICSharpCode.SharpZipLib.Zip.ZipInputStream' is obsolete: `This assembly has 
been deprecated. Please use https://www.nuget.org/packages/SharpZipLib/ 
instead.'
./MonoCompatibilityReviewRule.cs(179,35): error CS0618: Warning as Error: 
`ICSharpCode.SharpZipLib.Zip.ZipInputStream' is obsolete: `This assembly has 
been deprecated. Please use https://www.nuget.org/packages/SharpZipLib/ 
instead.'

Bug#918166: marked as done (Broken with Thunderbird 60)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 20:55:56 +
with message-id 
and subject line Bug#922403: Removed package(s) from unstable
has caused the Debian Bug report #918166,
regarding Broken with Thunderbird 60
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.)


-- 
918166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-google-tasks-sync
Version: 0.5.3-1
Severity: grave

Per the upstream homepage xul-ext-google-tasks-sync is incompatible with 
Thunderbird.

In fact, when installing the package it's not even listed in the addon manager.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 0.5.3-1+rm

Dear submitter,

as the package google-tasks-sync has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/922403

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#874882: marked as done ([freeplayer] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 20:56:27 +
with message-id 
and subject line Bug#922426: Removed package(s) from unstable
has caused the Debian Bug report #874882,
regarding [freeplayer] Future Qt4 removal from Buster
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.)


-- 
874882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeplayer
Version: 20070531+dfsg.1-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 20070531+dfsg.1-5+rm

Dear submitter,

as the package freeplayer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/922426

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#921131: marked as done (CVE-2018-10897)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 20:44:43 +
with message-id 
and subject line Bug#921131: fixed in yum-utils 1.1.31-2.2
has caused the Debian Bug report #921131,
regarding CVE-2018-10897
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.)


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

This was assigned CVE-2018-10897:
https://bugzilla.redhat.com/show_bug.cgi?id=1600221
https://github.com/rpm-software-management/yum-utils/commit/7554c0133eb830a71dc01846037cc047d0acbc2c
https://github.com/rpm-software-management/yum-utils/commit/6a8de061f8fdc885e74ebe8c94625bf53643b71c
https://github.com/rpm-software-management/yum-utils/pull/43

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Source: yum-utils
Source-Version: 1.1.31-2.2

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated yum-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Feb 2019 21:04:20 +0100
Source: yum-utils
Architecture: source
Version: 1.1.31-2.2
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Holger Levsen 
Closes: 921131
Changes:
 yum-utils (1.1.31-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch based on 7554c0133eb830a71dc01846037cc047d0acbc2c.
 Closes: #921131 / CVE-2018-10897
Checksums-Sha1:
 8a697eea5f210563935f676f4a781d687ce9782e 1929 yum-utils_1.1.31-2.2.dsc
 98d73ec36670ffef19b22b381749458a0e097a67 19300 
yum-utils_1.1.31-2.2.debian.tar.xz
 bc9c0ec1f4ac7aec523e2301b553046fb6ccc4f0 6275 
yum-utils_1.1.31-2.2_source.buildinfo
Checksums-Sha256:
 55ae360164264f3cdbb6112615fb375c0b64e29eb37625a9d1bbdc142e3d3a5f 1929 
yum-utils_1.1.31-2.2.dsc
 49ac28ce485752dbb985f935a4fa7d83018c29f00fe2775599a58bf32def0a36 19300 
yum-utils_1.1.31-2.2.debian.tar.xz
 798240ab2b63e90b22135116904061bff21458e3e30620ff959bb8aaf20b37b9 6275 
yum-utils_1.1.31-2.2_source.buildinfo
Files:
 a088a9f17edc1e9200548dedfed52834 1929 admin extra yum-utils_1.1.31-2.2.dsc
 25ee708b5d6d9a3cfe1ee102ced611b2 19300 admin extra 
yum-utils_1.1.31-2.2.debian.tar.xz
 3692d3cac19e8d1a6a0a84d654e50a4c 6275 admin extra 
yum-utils_1.1.31-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAlxnG+cACgkQCRq4Vgaa
qhzDCxAAmySI19mzCVpojOlqEMdwlyFTqWyz+YO4oVzNEn9tweGLnEMYunKRDfNB
ItpHJUycs/eLK5IYu/hdmBZXKwTnbPZG3xiCrX5kch1QB9Qx6uob9l6CX9D3IASt
FLNbyRzFfKNG/BTZgYTnouPg/Ncnd46HWIbOJGwBaRL6/HmVPgZYRsuWBBWZZ8j0
3FSMXFr6gWk3Xhp4Y+XipQPsd32Uu0//51qxVZXQiQlN8arFsydIQZJpsKnwLI3s
1UnksYtZeC6d953fgYR+ChMQRrqnAOHulzvIER52JCxnWmbXAsLkMP+LzA8KpD68
Doj4FcArE09ZwcpnetSeHUwHuDP4yoqprw8Qyb1qEJxRvtQZ7cqNIGv01IgrkbYK
WDSVBPlWnwAa0jb+m3kFjLn4+rD3oDVhvgsHf8Ujd6WoBFGn8xdUi0ddPF4mVdtX
usutdCNWeCMSSmq5ioA2DmjZU+xvKxibGx7ustTiiI1mCfaAxjmniOp7HdolsI+f
Bs16ww+RsONRkvF4DDZJQ6eZl87xICZqEaOkLzIziJ61J66TYySuziA7+a9F2+RA
YZmx9PY7IaIa2ZPVQOZAtYQ3hl40HYCd50tSzEv2UFD25M4h+O6z4km6Ep/Js1I0
8OOgLisqsJFfU07MZ+ni+S1PR2xjhgHeZa6FlVZ2Ky+qMkX7ZaE=
=IAHf
-END PGP SIGNATURE End Message ---

Bug#921902: marked as done (sdb: FTBFS (error CS1617: Invalid -langversion option `future'))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 19:35:42 +
with message-id 
and subject line Bug#921902: fixed in sdb 1.2-2
has caused the Debian Bug report #921902,
regarding sdb: FTBFS (error CS1617: Invalid -langversion option `future')
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh --with cli build-indep 
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mkdir -p dep/
dh_auto_build
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1
make[2]: Entering directory '/<>'
mkdir -p bin
cp LICENSE bin/LICENSE
mkdir -p bin
cp README.md bin/README
cp `pkg-config --variable=Sources mono-options` dep/Options.cs
cp `pkg-config --variable=Sources mono-lineeditor` dep/getline.cs
mkdir -p bin
cp `pkg-config --variable=Libraries mono-cecil` bin/
cp `pkg-config --variable=Libraries mono-debugger` bin/
mcs -debug -langversion:future -unsafe -warnaserror -keyfile:mono.snk -lib:bin 
-out:bin/sdb.exe -target:exe -r:Mono.Posix -r:Mono.Cecil.dll 
-r:Mono.Cecil.Mdb.dll -r:Mono.Debugger.Soft.dll -r:Mono.Debugging.dll 
-r:Mono.Debugging.Soft.dll -pkg:nrefactory dep/Options.cs dep/getline.cs 
src/Commands/AttachCommand.cs src/Commands/BacktraceCommand.cs 
src/Commands/BreakpointCommand.cs src/Commands/CatchpointCommand.cs 
src/Commands/ConfigCommand.cs src/Commands/ConnectCommand.cs 
src/Commands/ContinueCommand.cs src/Commands/DatabaseCommand.cs 
src/Commands/DecompileCommand.cs src/Commands/DirectoryCommand.cs 
src/Commands/DisassembleCommand.cs src/Commands/EnvironmentCommand.cs 
src/Commands/FrameCommand.cs src/Commands/HelpCommand.cs 
src/Commands/KillCommand.cs src/Commands/ListenCommand.cs 
src/Commands/PluginCommand.cs src/Commands/PrintCommand.cs 
src/Commands/QuitCommand.cs src/Commands/ResetCommand.cs 
src/Commands/RootCommand.cs src/Commands/RunCommand.cs 
src/Commands/SourceCommand.cs src/Com
 mands/StepCommand.cs src/Commands/ThreadCommand.cs 
src/Commands/WatchCommand.cs src/AssemblyInfo.cs src/Color.cs src/Command.cs 
src/CommandAttribute.cs src/CommandLine.cs src/Configuration.cs 
src/CustomLogger.cs src/Debugger.cs src/LibEdit.cs src/Log.cs 
src/MultiCommand.cs src/Plugins.cs src/Program.cs src/SessionKind.cs 
src/State.cs src/Utilities.cs
error CS1617: Invalid -langversion option `future'. It must be `ISO-1', 
`ISO-2', Default, Latest or value in range 1 to 7.2
make[2]: *** [Makefile:187: bin/sdb.exe] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:16: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: sdb
Source-Version: 1.2-2

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

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated sdb 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 

Bug#919831: Javadoc -link makes broken links if module name matches package name

[Markus Koschany]

Hi tony!

Am 15.02.19 um 15:42 schrieb tony mancill:
[...]
> Hi Markus,
> 
> We independently executed identical experiments, which I'm glad for,
> because I would have wanted some external verification before uploading
> any of this to unstable.  (I started building the r-build-deps of
> libplexus-languages-java using ratt, but my laptop isn't the best place
> to build 559 packages and many packages are FTBFS right now anyway due
> to the javadoc problems.)
> 
> I believe the comment in debian/README.source about updating src:maven
> is simply out of date.  I don't see any (obvious) versioned references
> to maven-javadoc-plugin in the current maven source package.

Ok, I have just removed README.source. I think it is a bit confusing.

> So I'm not sure what the next step is, other than continuing to watch
> commits to upstream maven-javadoc-plugin and see if I can figure out why
> 3.1.0~pre0-$foo doesn't work in our environment. 

I find that really strange because I thought the latest Git snapshot
would fix the bug.

> Or now that we're into the freeze, do we want to talk about actions with
> more far-reaching consequences?
> 
> Any thoughts on whether we should focus on fixing javadoc generation or
> look at other ways to mitigate the FTBFS?

Like burning all those -doc packages? :)

In my opinion we could ask Robert Scholte for advice. He is chairman of
Apache Maven and directly involved in fixing this bug. If he doesn't
know

However I think I have found a workaround, and we all love workarounds,
don't we.

In your initial post you pointed to a related bug report. [1] That made
me think and also read the fine Maven Javadoc documentation. There is an
option called detectJavaApiLink

https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink

If I add

detectJavaApiLink=false to debian/maven.properties in libparanamer-java,
the package builds from source again.

Maybe we should patch our tools and set this property to false and move
on for now? Hopefully in a few months this will just work again without
changing this option, when maven-javadoc-plugin et al. have been
catching up?

Cheers,

Markus


[1] https://github.com/oracle/opengrok/issues/2629




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#922179: shim-signed depends on packages not repos

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #922179 [shim-signed] shim-signed depends on packages not repos
Severity set to 'serious' from 'important'
> affects -1 src:debian-installer
Bug #922179 [shim-signed] shim-signed depends on packages not repos
Added indication that 922179 affects src:debian-installer

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

Bug#922355: marked as done (vmdb2: FTBFS in sid (LaTeX Error: File `lmodern.sty' not found))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 18:19:34 +
with message-id 
and subject line Bug#922355: fixed in vmdb2 0.13.2+git20190215-1
has caused the Debian Bug report #922355,
regarding vmdb2: FTBFS in sid (LaTeX Error: File `lmodern.sty' not found)
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with=python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/vmdb2-0.13.2+git20190214'
dh_auto_build
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/step_list.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/__init__.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/step_list_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/tags_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/spec.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/runcmd.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/unmount.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/unmount_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/version.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/state.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/spec_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/app.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/tags.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
creating 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/chroot_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/qemudebootstrap_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/__init__.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/lvm2_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/debootstrap_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/rootfs_cache_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/luks_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/grub_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/error_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/mkimg_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/apt_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/mount_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/mkfs_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/virtuals_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/partition_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/ansible_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/echo_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins

Bug#918598: marked as done (ruby-dalli FTBFS with rails 5.2)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 18:19:25 +
with message-id 
and subject line Bug#918598: fixed in ruby-dalli 2.7.9-1
has caused the Debian Bug report #918598,
regarding ruby-dalli FTBFS with rails 5.2
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.)


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

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

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

RUBYLIB=/build/1st/ruby-dalli-2.7.4/debian/ruby-dalli/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-dalli/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" -v
/build/1st/ruby-dalli-2.7.4/debian/ruby-dalli/usr/lib/ruby/vendor_ruby/dalli/server.rb:677:
 warning: assigned but unused variable - type
Testing with Rails 5.2.0
Using kgio socket IO
Run options: -v --seed 54285

# Running:

Testing 2.7.4 with ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux-gnu]
Found memcached 1.5.6 in PATH
user system  total
real
mixed:rails:dalli   3.688000   1.10   4.788000 ( 
17.288303)
mixed:rails-localcache:dalli  performance#test_0001_runs benchmarks = 
17.55 s = E


Error:
performance#test_0001_runs benchmarks:
NoMethodError: undefined method `normalize_key' for 
#


bin/rails test build/1st/ruby-dalli-2.7.4/test/benchmark_test.rb:25


Finished in 17.648526s, 0.0567 runs/s, 0. assertions/s.
1 runs, 0 assertions, 0 failures, 1 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" 
-v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-dalli-2.7.4/debian/ruby-dalli returned exit code 1
make: *** [debian/rules:6: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-dalli
Source-Version: 2.7.9-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Feb 2019 18:50:59 +0100
Source: ruby-dalli
Architecture: source
Version: 2.7.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Closes: 918598
Changes:
 ruby-dalli (2.7.9-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Antonio Terceiro ]
   * Remove myself from Uploaders:
 .
   [ Andrew Lee (李健秋) ]
   * debian/watch: fetch from upstream github instead.
 .
   [ Cédric Boutillier ]
   * Run wrap-and-sort on packaging files
   * New upstream version 2.7.9
 + support for rails 5.2 (Closes: #918598)
   * Bump debhelper compatibility level to 11
   * Use salsa.debian.org in Vcs-* fields
   * Bump Standards-Version to 4.3.0 (no changes needed)
   * Refresh 0001-test-suite-run-as-current-user.patch
   * Build-depend on ruby-appraisal, ruby-connection-pool, ruby-simplecov
   * Add patch to relax minimal rails version in gemspec
   * Add patch to correctly load dalli version in autopkgtest
Checksums-Sha1:
 6a848ce060b27c7987b55d67aecb8d045d5e5f94 1760 ruby-dalli_2.7.9-1.dsc
 4f8da3c1b4fdf1c642422893f89c284f785d8e92 51971 ruby-dalli_2.7.9.orig.tar.gz
 

Bug#920995: marked as done (spatialite: hangs during virtualknn test)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 18:05:38 +
with message-id 
and subject line Bug#920995: fixed in spatialite 5.0.0~beta0-1~exp2
has caused the Debian Bug report #920995,
regarding spatialite: hangs during virtualknn test
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.)


-- 
920995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spatialite
Version: 5.0.0~beta0-1~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

during a test rebuild of spatialite/experimental I noticed that it hangs
during the virtualknn test. After killing that process the build
continued and succeeded. I think this has so far happened more than
once, not sure if on amd64 or or i386 or both.


Andreas
--- End Message ---
--- Begin Message ---
Source: spatialite
Source-Version: 5.0.0~beta0-1~exp2

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated spatialite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Feb 2019 18:18:34 +0100
Source: spatialite
Binary: libspatialite-dev libspatialite7 libspatialite7-dbgsym 
libsqlite3-mod-spatialite libsqlite3-mod-spatialite-dbgsym
Architecture: source amd64
Version: 5.0.0~beta0-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 libspatialite-dev - Geospatial extension for SQLite - development files
 libspatialite7 - Geospatial extension for SQLite - libraries
 libsqlite3-mod-spatialite - Geospatial extension for SQLite - loadable module
Closes: 920995
Changes:
 spatialite (5.0.0~beta0-1~exp2) experimental; urgency=medium
 .
   * Bump Standards-Version to 4.3.0, no changes.
   * Add Build-Depends-Package field to symbols file.
   * Add upstream patch to fix virtualknn test hang.
 (closes: #920995)
Checksums-Sha1:
 a1cb9145e7de539dabe4f917ae246dd520876b23 2466 spatialite_5.0.0~beta0-1~exp2.dsc
 ed37be87469f845389e90e48c348ae8ff028e3b7 27040 
spatialite_5.0.0~beta0-1~exp2.debian.tar.xz
 da44f27b0887c99ba81a18ca60bf9d719eacdb36 1725608 
libspatialite-dev_5.0.0~beta0-1~exp2_amd64.deb
 c7c98451df6324cbd5d7159a0d43b5ef118abea1 3744600 
libspatialite7-dbgsym_5.0.0~beta0-1~exp2_amd64.deb
 5bb86d3b51a2cb69313380a6010ffd9f145f774a 1602528 
libspatialite7_5.0.0~beta0-1~exp2_amd64.deb
 ed69d6e7d04fd95b3d190e02e9cdf762ec6ba43a 4109080 
libsqlite3-mod-spatialite-dbgsym_5.0.0~beta0-1~exp2_amd64.deb
 ce0f9479c0954aa32f5c183c46ed1dacf956c663 1566656 
libsqlite3-mod-spatialite_5.0.0~beta0-1~exp2_amd64.deb
 7767bc1b6d1ba66cc20c2429a1dbc91affa3a72f 7927 
spatialite_5.0.0~beta0-1~exp2_amd64.buildinfo
Checksums-Sha256:
 6107abeab0a41352d357fbd5c78b725e9aa75b1b8daf4cc5927b4681c9bcc596 2466 
spatialite_5.0.0~beta0-1~exp2.dsc
 c73bb1d19ad79bf1017aed0a36e2334aa7ec05aea052a7019fa9f3872a0cd7be 27040 
spatialite_5.0.0~beta0-1~exp2.debian.tar.xz
 273c7b970a17bbef15e4b23989b7ad20a22fa222872b629000254df8a8db 1725608 
libspatialite-dev_5.0.0~beta0-1~exp2_amd64.deb
 65fd5d3a1de228232b8edd574eed5435aac8bb521c45d3983ac60c84743fdd2f 3744600 
libspatialite7-dbgsym_5.0.0~beta0-1~exp2_amd64.deb
 dfd7e9f5664b370bd8bc10b84684bfbcf4fbca98aca4dc7f83f2f1f6d3bdf5bc 1602528 
libspatialite7_5.0.0~beta0-1~exp2_amd64.deb
 3a1c63d9255f994ecf05d916267772c0361fe4e45d005d682625dd31b0ffed03 4109080 
libsqlite3-mod-spatialite-dbgsym_5.0.0~beta0-1~exp2_amd64.deb
 49d254635f12b8958cd1d516f41ebf06d33af0a6d01eaf5d3688e22e48034f79 1566656 
libsqlite3-mod-spatialite_5.0.0~beta0-1~exp2_amd64.deb
 af526daf1b6fd149d0d627b9661f49ec5cf04ab9e665ddebd5675dafccb57d9e 7927 
spatialite_5.0.0~beta0-1~exp2_amd64.buildinfo
Files:
 d2bc0de6460b24e631fe8abe0734fae0 2466 science optional 
spatialite_5.0.0~beta0-1~exp2.dsc
 fb92ddd0e4830a360ac5410cd4274fec 27040 science optional 
spatialite_5.0.0~beta0-1~exp2.debian.tar.xz
 119b27188272c8b5042c8fb9c1bc28f9 1725608 libdevel optional 

Processed: Re: Bug#920995: spatialite: hangs during virtualknn test

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #920995 [src:spatialite] spatialite: hangs during virtualknn test
Added tag(s) pending.

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

Bug#920995: spatialite: hangs during virtualknn test

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 2/10/19 9:24 PM, Sebastiaan Couwenberg wrote:
> On 1/31/19 2:17 PM, Bas Couwenberg wrote:
>> On 2019-01-31 13:36, Andreas Beckmann wrote:
>>> during a test rebuild of spatialite/experimental I noticed that it hangs
>>> during the virtualknn test. After killing that process the build
>>> continued and succeeded. I think this has so far happened more than
>>> once, not sure if on amd64 or or i386 or both.
>>
>> I've confirmed this issue in an amd64 experimental chroot, and forwarded
>> the issue upstream:
>>  
>> https://www.gaia-gis.it/fossil/libspatialite/tktview/2cad2f4b9df468fa062f624638d4ac6072611821
> 
> Upstream has tracked down the issue and committed a fix:
> 
>  https://www.gaia-gis.it/fossil/libspatialite/ci/90180e065dfdd8fa?sbs=0
> 
> A new (beta) release should be published next week, so I'll wait for
> that instead of adding a patch with the fix since the issue only affects
> the package in experimental.

The release hasn't happened yet, so I've added the patch.

A new upload to experimental will follow shortly.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#921795: marked as done (node-flagged-respawn: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 17:35:38 +
with message-id 
and subject line Bug#921795: fixed in node-flagged-respawn 1.0.1-1
has caused the Debian Bug report #921795,
regarding node-flagged-respawn: FTBFS (failing tests)
to be marked as done.

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

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


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

Dear maintainer:

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


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


  flaggedRespawn
isV8flags
  ✓ should return true when flag is in v8flags
  ✓ should ignore separator differences of "-" and "_"
  ✓ should return false when flag is not in v8flags

[... snipped ...]

 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  7) flaggedRespawn
   force and forbid respawning
 always forbid respawning with inner --no-respawning:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  8) flaggedRespawn
   force and forbid respawning
 should force respawning with node flags (array):
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  9) flaggedRespawn
   force and forbid respawning
 should force respawning with node flags (string):
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  10) flaggedRespawn
   force and forbid respawning
 should take priority to forbidding than forcing:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  11) flaggedRespawn
   cli args which are passed to app
 should pass args except v8flags, forced node flags, --no-respawning 
when respawned:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  12) flaggedRespawn
   cli args which are passed to app
 should pass args except v8flags, forced node flags, --no-respawning 
when not respawned:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 12
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-flagged-respawn.html

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-flagged-respawn
Source-Version: 1.0.1-1

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

Bug#911515: marked as done (dvtm: unsatisfiable dependency in stretch-backports: ncurses-term (>> 6.1+20180210-3))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 17:27:37 +
with message-id 
and subject line Re: dvtm in backports
has caused the Debian Bug report #911515,
regarding dvtm: unsatisfiable dependency in stretch-backports: ncurses-term (>> 
6.1+20180210-3)
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.)


-- 
911515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dvtm
Version: 0.15-3~bpo9+1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in stretch-backports:

 Package: dvtm
 Version: 0.15-3~bpo9+1
 Depends: libc6 (>= 2.14), libncursesw5 (>= 6), libtinfo5 (>= 6), ncurses-term 
(>> 6.1+20180210-3)

ncurses-term | 6.0+20161126-1+deb9u2 | stable | all
ncurses-term | 6.1+20180714-1| testing| all
ncurses-term | 6.1+20181013-1| unstable   | all


Cheers,

Andreas


dvtm_0.15-3~bpo9+1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---

[2019-02-06 17:02] Sven Joachim 
> Maybe you could re-add the missing terminfo files in the dvtm backport?
> In that case, they should be installed under /lib/terminfo rather than
> under /usr/share/terminfo to avoid clashes with the files in
> ncurses-term.

This is solution. Uploaded into stretch-backports. Thank you for
cooperation.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 - End Message ---

Processed: Bug #921795 in node-flagged-respawn marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #921795 [src:node-flagged-respawn] node-flagged-respawn: FTBFS (failing 
tests)
Added tag(s) pending.

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

Bug#921795: Bug #921795 in node-flagged-respawn marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #921795 in node-flagged-respawn reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-flagged-respawn/commit/a097c166ed7b1f74e6b6be6c4029678924a287e8


Switch test to pkg-js-tools and increase timeout

Closes: #921795


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/921795

Bug#922420: got an unexpected keyword argument 'bg'

[Enrico Zini]

Package: gandi-cli
Version: 1.2-1
Severity: serious

Hello,

trying to use the gandi CLI, I get this:

$ gandi ip detach 
Traceback (most recent call last):
  File "/usr/bin/gandi", line 11, in 
load_entry_point('gandi.cli==1.2', 'console_scripts', 'run-gandi')()
  File "/usr/share/gandi-cli/gandi/cli/__main__.py", line 8, in main
cli(obj={})
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
  File "/usr/share/gandi-cli/gandi/cli/core/cli.py", line 162, in invoke
click.Group.invoke(self, ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
TypeError: detach() got an unexpected keyword argument 'bg'

It looks like --background has been added to the command line parser,
but not to the function arguments to which the command line parser
result is sent.


Enrico

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gandi-cli depends on:
ii  python33.7.2-1
ii  python3-pkg-resources  40.7.1-1

gandi-cli recommends no packages.

gandi-cli suggests no packages.

-- no debconf information

Bug#922376: marked as done (can't find executable chromedriver-helper for gem chromedriver-helper)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 16:50:57 +
with message-id 
and subject line Bug#922376: fixed in ruby-chromedriver-helper 2.1.0-5
has caused the Debian Bug report #922376,
regarding can't find executable chromedriver-helper for gem chromedriver-helper
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.)


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

Package: ruby-chromedriver-helper
version: 2.1.0-1
Severity: serious
justification: unable use the package
Control: affects -1 ruby-rails

Bundler::GemRequireError: There was an error while trying to load the 
gem 'chromedriver-helper'.
Gem Load Error is: can't find executable chromedriver-helper for gem 
chromedriver-helper

Backtrace for gem load error is:
/usr/lib/ruby/vendor_ruby/bundler/rubygems_integration.rb:462:in `block 
in replace_bin_path'
/usr/lib/ruby/vendor_ruby/bundler/rubygems_integration.rb:493:in `block 
in replace_bin_path'

/usr/lib/ruby/vendor_ruby/chromedriver-helper.rb:4:in `'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:71:in 
`require'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:71:in 
`block in require_with_bootsnap_lfi'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/loaded_features_index.rb:65:in 
`register'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:70:in 
`require_with_bootsnap_lfi'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:79:in 
`require'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:81:in `block (2 levels) in 
require'

/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:76:in `each'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:76:in `block in require'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:65:in `each'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:65:in `require'
/usr/lib/ruby/vendor_ruby/bundler.rb:114:in `require'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'

/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:703:in `raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:104:in `block in 
load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in 
`standard_exception_handling'

/usr/lib/ruby/vendor_ruby/rake/application.rb:103:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:82:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in 
`standard_exception_handling'

/usr/lib/ruby/vendor_ruby/rake/application.rb:80:in `run'
/usr/bin/rake:27:in `'
Bundler Error Backtrace:
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'


Caused by:
Gem::Exception: can't find executable chromedriver-helper for gem 
chromedriver-helper
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'

(See full trace by running task with --trace)
--- End Message ---
--- Begin Message ---
Source: ruby-chromedriver-helper
Source-Version: 2.1.0-5

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated 
ruby-chromedriver-helper 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: Fri, 15 Feb 2019 12:15:00 -0200
Source: ruby-chromedriver-helper
Binary: ruby-chromedriver-helper

Bug#922389: marked as done (golang-protobuf-extensions: FTBFS (cannot find package "github.com/golang/protobuf/proto/testdata"))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 16:49:21 +
with message-id 
and subject line Bug#922389: fixed in golang-protobuf-extensions 1.0.1-1
has caused the Debian Bug report #922389,
regarding golang-protobuf-extensions: FTBFS (cannot find package 
"github.com/golang/protobuf/proto/testdata")
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.)


-- 
922389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-protobuf-extensions
Version: 1.0.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
github.com/matttproud/golang_protobuf_extensions/ext 
github.com/matttproud/golang_protobuf_extensions/pbtest 
github.com/matttproud/golang_protobuf_extensions/pbutil
github.com/matttproud/golang_protobuf_extensions/ext
github.com/matttproud/golang_protobuf_extensions/pbtest
errors
internal/race
internal/cpu
internal/bytealg
runtime/internal/atomic
runtime/internal/sys
runtime
sync/atomic
sync
io
math
math/bits
unicode/utf8
strconv
unicode
reflect
encoding/binary
bytes
bufio
encoding
encoding/base64
syscall
time
internal/poll
internal/syscall/unix
internal/testlog
os
fmt
sort
strings
unicode/utf16
encoding/json
log
github.com/golang/protobuf/proto
github.com/matttproud/golang_protobuf_extensions/pbutil
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/matttproud/golang_protobuf_extensions/ext 
github.com/matttproud/golang_protobuf_extensions/pbtest 
github.com/matttproud/golang_protobuf_extensions/pbutil
# github.com/matttproud/golang_protobuf_extensions/pbutil
src/github.com/matttproud/golang_protobuf_extensions/pbutil/all_test.go:22:2: 
cannot find package "github.com/golang/protobuf/proto/testdata" in any of:
/usr/lib/go-1.11/src/github.com/golang/protobuf/proto/testdata (from 
$GOROOT)

/<>/obj-x86_64-linux-gnu/src/github.com/golang/protobuf/proto/testdata
 (from $GOPATH)
FAILgithub.com/matttproud/golang_protobuf_extensions/pbutil [setup failed]
?   github.com/matttproud/golang_protobuf_extensions/ext[no test files]
?   github.com/matttproud/golang_protobuf_extensions/pbtest [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/matttproud/golang_protobuf_extensions/ext 
github.com/matttproud/golang_protobuf_extensions/pbtest 
github.com/matttproud/golang_protobuf_extensions/pbutil returned exit code 1
make: *** [debian/rules:6: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-protobuf-extensions.html

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-protobuf-extensions
Source-Version: 1.0.1-1

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated golang-protobuf-extensions 
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, 16 Feb 2019 00:26:27 +0800
Source: golang-protobuf-extensions

Processed: Re: Bug#922350: udevd does not start after reboot

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #922350 [udev] udevd does not start after reboot
Severity set to 'important' from 'serious'
> retitle -1 udev: can't start when architecture != systemd
Bug #922350 [udev] udevd does not start after reboot
Changed Bug title to 'udev: can't start when architecture != systemd' from 
'udevd does not start after reboot'.

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

Bug#922350: udevd does not start after reboot

[Felipe Sateler]

Control: severity -1 important
Control: retitle -1 udev: can't start when architecture != systemd

On Fri, Feb 15, 2019 at 4:19 AM Vincent Danjean  wrote:

> Le 15/02/2019 à 08:01, Vincent Danjean a écrit :
> > Le 14/02/2019 à 22:59, Felipe Sateler a écrit :
> >> Is udev by any chance i386 instead of amd64?
> >
> > I don't think so:
> > vdanjean@eyak:~$ apt-cache policy udev:i386
> > udev:i386:
> >   Installé : (aucun)
>
> However, systemd was installed as i386:
> vdanjean@eyak:~$ apt-cache policy systemd:i386
> systemd:i386:
>   Installé : 240-5
>   Candidat : 240-5
>  Table de version :
>  *** 240-5 500
> 500 http://ftp.fr.debian.org/debian testing/main i386 Packages
> 500 http://ftp.fr.debian.org/debian unstable/main i386 Packages
> 100 /var/lib/dpkg/status
>  239-12~bpo9+1 100
> 100 http://ftp.fr.debian.org/debian stretch-backports/main i386
> Packages
>  232-25+deb9u8 500
> 500 http://security.debian.org stretch/updates/main i386 Packages
>  232-25+deb9u6 500
> 500 http://ftp.fr.debian.org/debian stretch/main i386 Packages
> vdanjean@eyak:~$ apt-cache policy systemd:amd64
> systemd:
>   Installé : (aucun)
>   Candidat : 240-5
>  Table de version :
>  240-5 500
> 500 http://ftp.fr.debian.org/debian testing/main amd64 Packages
> 500 http://ftp.fr.debian.org/debian unstable/main amd64 Packages
>  239-12~bpo9+1 100
> 100 http://ftp.fr.debian.org/debian stretch-backports/main amd64
> Packages
>  232-25+deb9u8 500
> 500 http://security.debian.org stretch/updates/main amd64 Packages
>  232-25+deb9u6 500
> 500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages
>
> It probably comes from the fact that:
> 1) using apt-listbugs, I blocked the upgrade of systemd due to
>919231
> 2) the upgrade fails due to another package. So I've to go with
>'apt install -f'
> 3) 'apt install -f' alone was removing packages I would like to keep
>(such as digikam), so I forced some packages on the command line
> 4) due to (1), apt probably solved some problem by selecting the
>i386 version of systemd (I did not remark anything during the
>installation)
>
>   So, the severity can be lowered and I will test with a reboot
> as soon as possible.
>

I'm downgrading the severity and retitling.

-- 

Saludos,
Felipe Sateler

Bug#921892: marked as done (libtommath: fails to clean after build)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 16:05:09 +
with message-id 
and subject line Bug#921892: fixed in libtommath 1.1.0-3
has caused the Debian Bug report #921892,
regarding libtommath: fails to clean after build
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.)


-- 
921892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtommath
Version: 1.1.0-3~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libtommath/experimental fails to build twice in a row. Cleaning after
the first build fails with

 fakeroot debian/rules clean
dh clean
   dh_auto_clean
make -j3 clean
make[1]: Entering directory '/build/libtommath-1.1.0'
rm -f *.gcda *.gcno *.gcov *.bat *.o *.a *.obj *.lib *.exe *.dll etclib/*.o 
demo/demo.o test timing mpitest mtest/mtest mtest/mtest.exe \
*.idx *.toc *.log *.aux *.dvi *.lof *.ind *.ilg *.ps *.log *.s mpi.c 
*.da *.dyn *.dpi tommath.tex `find . -type f | grep [~] | xargs` *.lo *.la
rm -rf .libs/
make -C etc/ clean MAKE=make
make[2]: Entering directory '/build/libtommath-1.1.0/etc'
rm -f *.log *.o *.obj *.exe pprime tune mersenne drprime tune86 tune86l mont 
2kprime pprime.dat \
 *.da *.dyn *.dpi *~
make[2]: Leaving directory '/build/libtommath-1.1.0/etc'
make -C doc/ clean MAKE=make
make[2]: Entering directory '/build/libtommath-1.1.0/doc'
make -C pics/ clean MAKE=make
make[3]: Entering directory '/build/libtommath-1.1.0/doc/pics'
rm -rf *.ps *.pdf .xvpics
make[3]: Leaving directory '/build/libtommath-1.1.0/doc/pics'
rm -f *.idx *.toc *.log *.aux *.dvi *.lof *.ind *.ilg *.ps *.log tommath.tex
make[2]: Leaving directory '/build/libtommath-1.1.0/doc'
make[1]: Leaving directory '/build/libtommath-1.1.0'
   debian/rules override_dh_clean
make[1]: Entering directory '/build/libtommath-1.1.0'
dh_clean tommath.out debian/libtool
rm: cannot remove 'debian/libtool': Is a directory
dh_clean: rm -f -- debian/libtommath-docs.substvars 
debian/libtommath-dev.substvars debian/libtommath1.substvars tommath.out 
debian/libtool debian/files returned exit code 1
make[1]: *** [debian/rules:51: override_dh_clean] Error 2
make[1]: Leaving directory '/build/libtommath-1.1.0'
make: *** [debian/rules:21: clean] Error 2


Andreas


libtommath_1.1.0-3~exp1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libtommath
Source-Version: 1.1.0-3

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

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated libtommath package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Feb 2019 11:36:43 +0100
Source: libtommath
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Closes: 921699 921892
Changes:
 libtommath (1.1.0-3) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: (Closes: #921699)
 + Let dh_auto_build pass cross tools to make.
 + Honour DEB_BUILD_OPTIONS=nocheck.
 .
   [ Dominique Dumont ]
   * fix dh_clean call to clean libtool dir.
 Thanks to Andreas Beckmann for the report (Closes: 921892)
   * update dh_clean list
Checksums-Sha1:
 3de3d02a2a4c57df3202ec829c4c628cb9474a72 2379 libtommath_1.1.0-3.dsc
 7d10c77388a240d2e166cde4f312267ea4b29359 18536 libtommath_1.1.0-3.debian.tar.xz
 e5fc80aba951911e0b5269f1c4b14750d00f6e00 7912 
libtommath_1.1.0-3_source.buildinfo
Checksums-Sha256:
 38575b08a7006cd40ea0513553c9ea191f121907ebc7f98f696180bec2be925e 2379 
libtommath_1.1.0-3.dsc
 7ccd56de3bba35a1aa941f19998c6b643cd0a3d87b76f41860421449b573911e 18536 
libtommath_1.1.0-3.debian.tar.xz
 9975970e01421d4ef443c837f4059524a82a579a4de73dd287feb9d293a5feb3 7912 
libtommath_1.1.0-3_source.buildinfo
Files:
 7ba49f1d9d4f9ef75b28fb85d56f9797 2379 libs optional libtommath_1.1.0-3.dsc
 63e0e4258cabdfc729994cc3fb43b48e 18536 libs optional 

Bug#918823: Update on your bug report

[Richard Hartmann]

Hi Leopold,

did you have a chance to run the commands requested by Aurelien? This
bug is marked critical, but has been stale for more than a month, now.


Thanks,
Richard

Bug#922271: marked as done (camomile: ocaml-gettext build still fails, due to wrong search path caused by camomile build)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 15:49:29 +
with message-id 
and subject line Bug#922271: fixed in camomile 1.0.1-3
has caused the Debian Bug report #922271,
regarding camomile: ocaml-gettext build still fails, due to wrong search path 
caused by camomile build
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.)


-- 
922271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: camomile
Version: 1.0.1-2
Severity: grave

Dear Maintainer,

I just had a look at the still-failing builds of ocaml-gettext/0.3.7-1
with the pacakges produced by camomile/1.0.1-2. The logs don't show a
lot, just a Not_found exception:

,[ 
https://buildd.debian.org/status/fetch.php?pkg=ocaml-gettext=armel=0.3.7-1%2Bb3=1549887522=0
 ]
| make[2]: Entering directory '/<>/po'
| /<>/_build/bin/ocaml-gettext --action compile \
| --compile-output fr.mo fr.po
| Fatal error: exception Not_found
| make[2]: *** [Makefile:50: fr.mo] Error 2
| make[2]: Leaving directory '/<>/po'
| make[1]: *** [Makefile:28: all] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [/usr/share/cdbs/1/class/makefile.mk:77: 
debian/stamp-makefile-build] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
`

I was able to reproduce this error in a sid-amd64 chroot. Running
_build/bin/ocaml-gettext using strace shows that it goes looking for
general_category.mar in the directory that was used for installation on
the buildhost where camomile was being built:

,
| execve("_build/bin/ocaml-gettext", ["_build/bin/ocaml-gettext"], 
0x7fffaee13180 /* 23 vars */) = 0
:
: ...
:
| readlink("/proc/self/exe", 
"/home/bengen/src/deb/ocaml-gettext/_build/bin/ocaml-gettext", 256) = 59
| stat("/home/bengen/src/deb/ocaml-gettext/_build/bin/ocaml-gettext", 
{st_mode=S_IFREG|0755, st_size=3062688, ...}) = 0
| lseek(0, 0, SEEK_CUR)   = -1 ESPIPE (Illegal seek)
| mmap(NULL, 794624, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f2d65c49000
| brk(0x5559f5984000) = 0x5559f5984000
| lseek(1, 0, SEEK_CUR)   = -1 ESPIPE (Illegal seek)
| lseek(2, 0, SEEK_CUR)   = -1 ESPIPE (Illegal seek)
| mmap(NULL, 532480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f2d65bc7000
| mmap(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f2d65b86000
| openat(AT_FDCWD, 
"/build/camomile-1.0.1/debian/tmp/usr/share/database/general_category.mar", 
O_RDONLY) = -1 ENOENT (No such file or directory)
| write(2, "Fatal error: exception Not_found\n", 33) = 33
| exit_group(2)   = ?
| +++ exited with 2 +++
`

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Source: camomile
Source-Version: 1.0.1-3

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

Debian distribution maintenance software
pp.
Kyle Robbertze  (supplier of updated camomile package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Feb 2019 08:21:51 +0200
Source: camomile
Binary: libcamomile-ocaml-data libcamomile-ocaml-dev
Architecture: source all amd64
Version: 1.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Kyle Robbertze 
Description:
 libcamomile-ocaml-data - Unicode data for OCaml
 libcamomile-ocaml-dev - Unicode library for OCaml
Closes: 922271
Changes:
 camomile (1.0.1-3) unstable; urgency=medium
 .
   * Remove build path in compiled artifacts (Closes: #922271)
Checksums-Sha1:
 aaf10c9505df1c83e07e872ea26457d3c0514f6d 2226 camomile_1.0.1-3.dsc
 2bb600758a7ab83fbbfd8facb7375b974318c830 59960 camomile_1.0.1-3.debian.tar.xz
 90571ce5255ac305e445b4bc23cb3d8e72ccae09 6348 camomile_1.0.1-3_amd64.buildinfo
 b791ff5e618e22a01bba05d517d3d3a695ac114d 1628792 
libcamomile-ocaml-data_1.0.1-3_all.deb
 d1e2decf9a40e8fbead782b552063b42dc99208b 1965976 
libcamomile-ocaml-dev_1.0.1-3_amd64.deb
Checksums-Sha256:
 

Processed: found 921892 in 1.1.0-2

[Debian Bug Tracking System]

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

> found 921892 1.1.0-2
Bug #921892 [src:libtommath] libtommath: fails to clean after build
Marked as found in versions libtommath/1.1.0-2.
> thanks
Stopping processing here.

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

Bug#919831: Javadoc -link makes broken links if module name matches package name

[tony mancill]

On Wed, Feb 13, 2019 at 10:07:34PM +0100, Markus Koschany wrote:
> Hi,
> 
> Am 26.01.19 um 20:07 schrieb tony mancill:
> [...]
> > I'm trying to peel the onion and believe that this is a problem in the
> > maven-javadoc-plugin package.  I found the same issue for a project
> > outside of Debian, for example [1], which refers to a JIRA ticket for that
> > plugin [2].  There is a commit [3] referencing that JIRA on the master
> > branch of maven-javadoc-plugin.
> > 
> > I would like to try cherry-picking the fix onto our current version of
> > maven-javadoc-plugin to see if it resolves our issue.  Or if that gets
> > too complicated, we could look into updating to a snapshot of 3.1.0 (our
> > version would 3.1.0~foo), since it looks like all of these commits will
> > be part of 3.1.0 [4].
> > 
> > I'm not sure how much time I'll have to dedicate to this over the
> > weekend and so would be happy if someone fixes it before I get to it.
> 
> I have updated the maven-javadoc-plugin package to the latest Git
> snapshot and pushed the changes. An update of libplexus-languages-java
> was also necessary (currently in experimental) and tony already took
> care of it. I also had to add a compatibility patch for Debian's version
> of maven-artifact-transfer. A new upstream release just because of some
> minor refactoring seemed to be not the best way forward during the freeze.
> 
> Now I would have expected that libparanamer-java (#920750) just built
> fine again but it doesn't. According to README.source in
> maven-javadoc-plugin maven2-core (should be src:maven?) must be updated
> as well. I'm not sure what button I have to press to make this work
> right now. Any ideas?

Hi Markus,

We independently executed identical experiments, which I'm glad for,
because I would have wanted some external verification before uploading
any of this to unstable.  (I started building the r-build-deps of
libplexus-languages-java using ratt, but my laptop isn't the best place
to build 559 packages and many packages are FTBFS right now anyway due
to the javadoc problems.)

I believe the comment in debian/README.source about updating src:maven
is simply out of date.  I don't see any (obvious) versioned references
to maven-javadoc-plugin in the current maven source package.

So I'm not sure what the next step is, other than continuing to watch
commits to upstream maven-javadoc-plugin and see if I can figure out why
3.1.0~pre0-$foo doesn't work in our environment. 

Or now that we're into the freeze, do we want to talk about actions with
more far-reaching consequences?

Any thoughts on whether we should focus on fixing javadoc generation or
look at other ways to mitigate the FTBFS?

Thanks,
tony


signature.asc
Description: PGP signature

Bug#852575: marked as done (powerpc-utils: Update udevadm path)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 14:43:05 +
with message-id 
and subject line Bug#852575: fixed in powerpc-utils 1.3.2-1.1
has caused the Debian Bug report #852575,
regarding powerpc-utils: Update udevadm path
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.)


-- 
852575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: powerpc-utils
Version: 1.3.2-1
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: udevadm

Hi,

since Jessie, the udevadm binary is available as /bin/udevadm.
To not break existing scripts, which use the old /sbin/udevadm path,
the udev package currently ships a compat symlink which we would like
to drop eventually (in buster or buster+1).

According to codesearch [1] your package powerpc-utils does hard-code the
udevadm path as /sbin/udevadm.

Please change that to /bin/udevadm.

Thanks for considering.

Michael,
on behalf of the pkg-systemd team.

[1] https://codesearch.debian.net/search?q=%2Fsbin%2Fudevadm
--- End Message ---
--- Begin Message ---
Source: powerpc-utils
Source-Version: 1.3.2-1.1

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

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
powerpc-utils 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, 10 Feb 2019 14:35:38 +0100
Source: powerpc-utils
Architecture: source
Version: 1.3.2-1.1
Distribution: sid
Urgency: medium
Maintainer: Adam Conrad 
Changed-By: John Paul Adrian Glaubitz 
Closes: 852575
Changes:
 powerpc-utils (1.3.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * 03_udevadm_path.patch: Switch udevadm path prefix
 from /sbin to /bin (closes: #852575)
Checksums-Sha1:
 fac63ea016e1b2ba478347fcb42f66d04ad6f4e1 1992 powerpc-utils_1.3.2-1.1.dsc
 87ef4dae9c863d93c6155bdbf547f6bdab72e901 4908 
powerpc-utils_1.3.2-1.1.debian.tar.xz
 9c83fe33869d7f8ca5645dd24971b7a87826ef89 6014 
powerpc-utils_1.3.2-1.1_ppc64.buildinfo
Checksums-Sha256:
 be724864ccee76cfb235e47c30eb4d9eede65c262d42835d1d45994827577f47 1992 
powerpc-utils_1.3.2-1.1.dsc
 a526bd484cfcf65753927c82bd0ff006dc324f12d64ea062d5e37d15b210570e 4908 
powerpc-utils_1.3.2-1.1.debian.tar.xz
 9199b9fc1c138ec48ceace66ced51337c1c96ae3a8a0a6a49436f51edcea2f6f 6014 
powerpc-utils_1.3.2-1.1_ppc64.buildinfo
Files:
 b52054d8f7d719f896f0799618f11427 1992 utils important 
powerpc-utils_1.3.2-1.1.dsc
 9ab2423080cfd9e55913e54adbf88fb6 4908 utils important 
powerpc-utils_1.3.2-1.1.debian.tar.xz
 544259a8d4c758acf246a7eb76d9fde8 6014 utils important 
powerpc-utils_1.3.2-1.1_ppc64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlxgLVcACgkQdCY7N/W1
+RPyZg//fMUahH18M5V/P8c6icxinTcUvubrfZoWBiSEX7bbfS5zYTXPIDI7os7Z
SG4iuAJAiFENhrCjiSYpFot9B+6bb80ZKWiEWFmwyhULsawBvbbtDCkXweTm8Q3m
QCkbJdWxViXPw6pp3TxGFVv3PhbpRAN2/U+MJY5Hu1rVj6x8d+mT3Yhpji9LRQ2i
PloZMFE9ks210KeKkgl7E5gvhYoG7lVDHJ4S5MilYDB7TbvY05gQIXB+HD987x6f
dswzo+gxgGTXHMYorVChH4D5taNJnBuHNa/zLVY+/ovDiWaKQgWl+1S98VVeBMJB
RyWbzBp4x8WT1/uy2BaMvh4wK9R6uexY5zIXZV84jyPVmYUHyesYZ9laoyXuUOAt
TTQ64IFRgIohStzGN/dnlyaerr9sQOctwnMAcwywC6Jns9H/eVsTA21FXaGU+wqa
1pGKnaYnir5kuGYtRJZQm6xLLDdRftXDS6cy2im7onqNR3P8nbYlsx8VcV7mAn81
2Qj4L+MrVHa+5ZsbtUG6AyNYdS3egBQIECXRZZrSucAl/wMsKaMaG1xrAiSPj9Db
W7s7TSYfGFeGXaQjPsAPK9TJnmH9rkd1XUnMSI7O92hBiC4kOvCV5Tux9KZuy1Vc
NUvqiLisN99H24TGBrA13NDeEA7RNdpT0mZLUGCGgvXWN86n4zE=
=I6kN
-END PGP SIGNATURE End Message ---

Bug#922404: freeipmi install fails

[Karl Stenerud]

Package: freeipmi
Version: 1.6.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?

installing freeipmi

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

apt install freeipmi

   * What was the outcome of this action?

postinstall failed:

Setting up freeipmi-ipmidetect (1.6.3-1) ...
Job for ipmidetectd.service failed because the control process exited with
error code.
See "systemctl status ipmidetectd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript ipmidetectd, action "start" failed.
● ipmidetectd.service - IPMI Node Detection Monitoring Daemon
   Loaded: loaded (/lib/systemd/system/ipmidetectd.service; disabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-02-15 14:06:15 UTC;
5ms ago
  Process: 966 ExecStart=/usr/sbin/ipmidetectd $OPTIONS (code=exited,
status=1/FAILURE)

Feb 15 14:06:15 tester systemd[1]: Starting IPMI Node Detection Monitoring
Daemon...
Feb 15 14:06:15 tester ipmidetectd[966]: ipmidetectd: No nodes configured
Feb 15 14:06:15 tester systemd[1]: ipmidetectd.service: Control process
exited, code=exited, status=1/FAILURE
Feb 15 14:06:15 tester systemd[1]: ipmidetectd.service: Failed with result
'exit-code'.
Feb 15 14:06:15 tester systemd[1]: Failed to start IPMI Node Detection
Monitoring Daemon.
dpkg: error processing package freeipmi-ipmidetect (--configure):
 installed freeipmi-ipmidetect package post-installation script subprocess
returned error exit status 1

   * What outcome did you expect instead?

I expected postinstall to succeed

*** End of the template - remove these template lines ***

Note: This bug is also reported on launchpad:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1808637

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

Kernel: Linux 4.15.0-45-generic (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages freeipmi depends on:
ii  freeipmi-bmc-watchdog  1.6.3-1
ii  freeipmi-common1.6.3-1
ih  freeipmi-ipmidetect1.6.3-1
ii  freeipmi-tools 1.6.3-1

freeipmi recommends no packages.

freeipmi suggests no packages.

-- no debconf information

Bug#853443: hidrd: ftbfs with GCC-7

[Thierry fa...@linux.ibm.com]

On Mon, 4 Dec 2017 12:50:24 +0200 Juhani Numminen
 wrote:
> Control: tags -1 patch fixed-upstream
> 
> On Mon, 4 Dec 2017 10:23:34 +0200 Juhani Numminen 
>  wrote:
> > Upstream has committed some GCC-7-related fixes.
> > https://github.com/DIGImend/hidrd/commit/7e94881
> > https://github.com/DIGImend/hidrd/commit/e126127
> 
> I had a successful amd64 build with the two attached patches.
> 
> Cheers,
> Juhani

The problem still remains on ppc64el with gcc version 8.2.0

Bug#922376: can't find executable chromedriver-helper for gem chromedriver-helper

[Pirate Praveen]

On Fri, 15 Feb 2019 14:04:29 +0500 Pirate Praveen
 wrote:
> Package: ruby-chromedriver-helper
> version: 2.1.0-1
> Severity: serious
> justification: unable use the package
> Control: affects -1 ruby-rails
> 
> Bundler::GemRequireError: There was an error while trying to load the 
> gem 'chromedriver-helper'.
> Gem Load Error is: can't find executable chromedriver-helper for gem 
> chromedriver-helper


This was originally found in rails newapp autopkgtest and now the same
test is added an new-rails-app autopkgtest in ruby-chromedriver-helper
as well.

So to reproduce, just run autopkgtest with ruby-team/meta/build script.



signature.asc
Description: OpenPGP digital signature

Processed: reopening 922376

[Debian Bug Tracking System]

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

> reopen 922376
Bug #922376 {Done: Pirate Praveen } 
[ruby-chromedriver-helper] can't find executable chromedriver-helper for gem 
chromedriver-helper
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ruby-chromedriver-helper/2.1.0-2.
> thanks
Stopping processing here.

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

Processed: notfixed 922376 in 2.1.0-2

[Debian Bug Tracking System]

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

> notfixed 922376 2.1.0-2
Bug #922376 [ruby-chromedriver-helper] can't find executable 
chromedriver-helper for gem chromedriver-helper
Ignoring request to alter fixed versions of bug #922376 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#922395: smokeping: fails to stop and to upgrade: start-stop-daemon: matching only on non-root pidfile /var/run/smokeping/smokeping.pid is insecure

[Axel Beckert]

Package: smokeping
Version: 2.7.3-1
Severity: serious

Hi,

sorry for the late report, but smokeping failed to configure (probably
after the recent upgrade) for a few days for me now:

# dpkg --configure -a
Setting up smokeping (2.7.3-1) ...
apache2_invoke: Enable module cgi
[ ok ] Restarting Apache httpd web server: apache2
apache2_invoke smokeping: already enabled
[ ok ] Reloading Apache httpd web server: apache2.
[] Shutting down latency logger daemon: smokepingstart-stop-daemon: 
matching only on non-root pidfile /var/run/smokeping/smokeping.pid is insecure
 failed!
invoke-rc.d: initscript smokeping, action "restart" failed.
dpkg: error processing package smokeping (--configure):
 installed smokeping package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 smokeping
# ls -l /var/run/smokeping/smokeping.pid
-rw-r--r-- 1 smokeping smokeping 5 Jan 21 17:50 /var/run/smokeping/smokeping.pid

This seems to happen since dpkg 1.19.3. According changelog entry:

  * start-stop-daemon: Check whether standalone --pidfile use is secure.
Prompted by Michael Orlitzky .

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 3.18.0-trunk-rpi2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages smokeping depends on:
ii  adduser 3.118
ii  debianutils 4.8.6.1
ii  fping   4.1-1
ii  libcgi-fast-perl1:2.13-1
ii  libconfig-grammar-perl  1.12-2
ii  libdigest-hmac-perl 1.03+dfsg-2
ii  libjs-cropper   1.2.2-1
ii  libjs-prototype 1.7.1-3
ii  libjs-scriptaculous 1.9.0-2
ii  librrds-perl1.7.1-1
ii  libsnmp-session-perl1.14~git20130523.186a005-4
ii  liburi-perl 1.76-1
ii  libwww-perl 6.36-1
ii  lsb-base10.2018112800
ii  perl5.28.1-4
ii  postfix [mail-transport-agent]  3.3.2-1+b1
ii  ucf 3.0038+nmu1

Versions of packages smokeping recommends:
ii  apache2 [httpd-cgi]   2.4.38-2
ii  bind-dnsutils [dnsutils]  1:9.13.2-1~exp0
ii  echoping  6.0.2-10
ii  libsocket6-perl   0.29-1+b1

Versions of packages smokeping suggests:
ii  curl7.64.0-1
pn  libauthen-radius-perl   
ii  libio-socket-ssl-perl   2.060-3
ii  libnet-dns-perl 1.19-1
pn  libnet-ldap-perl
ii  libnet-telnet-perl  3.04-1
ii  openssh-client  1:7.9p1-6
ii  postfix [mail-transport-agent]  3.3.2-1+b1

-- Configuration Files:
/etc/smokeping/basepage.html changed:

http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>





SmokePing Latency Page for <##title##>



  







  
  
  SmokePing Targets:
  <##menu##>
  
  
   
   
  <##title##>
<##remark##>
<##overview##>
<##body##>
   



  Maintained by <##owner##>
  Running on <##smokeping##> by <##author##>
  <##smokelogo##>
  
  <##rrdlogo##>






/etc/smokeping/config.d/Probes changed:
*** Probes ***
+ FPing
binary = /usr/bin/fping
+ FPing6
binary = /usr/bin/fping

/etc/smokeping/config.d/Targets changed:
[removed for privacy reasons]

/etc/smokeping/smokeping_secrets [Errno 13] Permission denied: 
'/etc/smokeping/smokeping_secrets'


-- no debconf information

Bug#922345: marked as done (msmtp: CVE-2019-8337)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 11:50:32 +
with message-id 
and subject line Bug#922345: fixed in msmtp 1.8.3-1
has caused the Debian Bug report #922345,
regarding msmtp: CVE-2019-8337
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.)


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

Hi,

The following vulnerability was published for msmtp.

CVE-2019-8337[0]:
| In msmtp 1.8.2, when tls_trust_file has its default configuration,
| certificate-verification results are not properly checked.

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-2019-8337
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8337
[1] https://marlam.de/msmtp/news/
[2] 
https://gitlab.marlam.de/marlam/msmtp/commit/a81d0a5126304f9f8b29a75d058044dc67d07663

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: msmtp
Source-Version: 1.8.3-1

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

Debian distribution maintenance software
pp.
Emmanuel Bouthenot  (supplier of updated msmtp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Feb 2019 10:52:11 +
Source: msmtp
Binary: msmtp msmtp-dbgsym msmtp-gnome msmtp-gnome-dbgsym msmtp-mta 
msmtp-mta-dbgsym
Architecture: source amd64
Version: 1.8.3-1
Distribution: unstable
Urgency: medium
Maintainer: Emmanuel Bouthenot 
Changed-By: Emmanuel Bouthenot 
Description:
 msmtp  - light SMTP client with support for server profiles
 msmtp-gnome - light SMTP client with support for server profiles - with GNOME k
 msmtp-mta  - light SMTP client with support for server profiles - the regular
Closes: 883349 922345
Changes:
 msmtp (1.8.3-1) unstable; urgency=medium
 .
   [ Emmanuel Bouthenot ]
   * New upstream release
 * Fix CVE-2019-8337 : improper certificate verification when
   tls_trust_file=system (Closes: #922345)
 .
   [ Simon Deziel ]
   * Add/delete msmtp user/group on install/purge
   * Make msmtp's binary execute as msmtp group (setgid)
- This allow restricting access to /etc/msmtprc (Closes: 883349)
Checksums-Sha1:
 a0d4c11a404970a7e73fbbce7f4cb38285090d27 1978 msmtp_1.8.3-1.dsc
 1e44836b56133251155c34144ff186c2a3a7780d 260469 msmtp_1.8.3.orig.tar.gz
 30501a39ad8109395261d1a57610829d1a198a54 17776 msmtp_1.8.3-1.debian.tar.xz
 ec34695112ce20729b3b5cd82d3de1e1565074e9 109660 msmtp-dbgsym_1.8.3-1_amd64.deb
 6ba90f9adc9b2fe13915224e7b8162ec1e84763b 113372 
msmtp-gnome-dbgsym_1.8.3-1_amd64.deb
 1fc18f430b23dcdf57a154a42df041fe9085bf54 45792 msmtp-gnome_1.8.3-1_amd64.deb
 6af3d47181cca43808c42abd4ba95815ba31ec1e 14208 
msmtp-mta-dbgsym_1.8.3-1_amd64.deb
 8e19610b2603af61a03d55c1a44bcd8eec371f5b 19148 msmtp-mta_1.8.3-1_amd64.deb
 c26f2e0f714cc52b55db14d7d512a049a8fcfac3 9160 msmtp_1.8.3-1_amd64.buildinfo
 6dabf609d135982f646935b77f01e4477725b714 136808 msmtp_1.8.3-1_amd64.deb
Checksums-Sha256:
 b967e33396c5278ebeb5a587866742c11f0f7c3c3f36f3d94b10949bce23166f 1978 
msmtp_1.8.3-1.dsc
 96abf247360f66b4a6c368448ea4191d0c7f05a350b54aa0d70c839a0f1560a5 260469 
msmtp_1.8.3.orig.tar.gz
 af2f7a7cf07dfe4af15dbdea1527ae4e75dc9fe39b56d247aa6420006cb37c93 17776 
msmtp_1.8.3-1.debian.tar.xz
 918fd8141ddf86d3af6f0af332b169a28786a1319f0d3f4870739586a51a94df 109660 
msmtp-dbgsym_1.8.3-1_amd64.deb
 a34c64334a5f25c02821be474c10d1df316106922a5090ac5cf32950c5509e8a 113372 
msmtp-gnome-dbgsym_1.8.3-1_amd64.deb
 bff1c1a874dc411acb381f519e30788466b7c1e14931d92e29d53fd9f3cc8d2e 45792 
msmtp-gnome_1.8.3-1_amd64.deb
 f74787c426d17ec9411d50baf47342fdd6d84a25660ea9be8e1ee259e845742f 14208 
msmtp-mta-dbgsym_1.8.3-1_amd64.deb
 5ac273bb4166d82a3411f3345e7f88956e8b30c17b02ef6aab5b0b9aa32397be 19148 
msmtp-mta_1.8.3-1_amd64.deb
 

Bug#922333: marked as done (libmail-message-perl 3.008 breaks (the testsuite of) libmail-box-perl)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 11:34:16 +
with message-id 
and subject line Bug#922333: fixed in libmail-box-perl 3.006-1
has caused the Debian Bug report #922333,
regarding libmail-message-perl 3.008 breaks (the testsuite of) libmail-box-perl
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.)


-- 
922333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmail-message-perl
Version: 3.008-1
Severity: serious
Tags: upstream sid
Justification: breaks other package

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, libmail-message-perl 3.008-1 breaks
libmail-box-perl's test suite (which causes a build failure):

https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmail-box-perl/1925858/log.gz

Also locally:

#   Failed test 'begin 1'
#   at t/100mbox-read.t line 73.
#  got: 2973
# expected: 2974
#   Failed test 'begin 2'
#   at t/100mbox-read.t line 73.
#  got: 6953
# expected: 6954
#   Failed test 'begin 3'
#   at t/100mbox-read.t line 73.
#  got: 10871
# expected: 10872
#   Failed test 'begin 4'
#   at t/100mbox-read.t line 73.
#  got: 13775
# expected: 13776
#   Failed test 'begin 5'
#   at t/100mbox-read.t line 73.
#  got: 17767
# expected: 17768
#   Failed test 'begin 6'
#   at t/100mbox-read.t line 73.
#  got: 22665
# expected: 22666
#   Failed test 'begin 7'
#   at t/100mbox-read.t line 73.
#  got: 29863
# expected: 29864
#   Failed test 'begin 8'
#   at t/100mbox-read.t line 73.
#  got: 38796
# expected: 38797
#   Failed test 'begin 9'
#   at t/100mbox-read.t line 73.
#  got: 40538
# expected: 40539
#   Failed test 'begin 10'
#   at t/100mbox-read.t line 73.
#  got: 44810
# expected: 44811
#   Failed test 'begin 11'
#   at t/100mbox-read.t line 73.
#  got: 46327
# expected: 46328
#   Failed test 'begin 12'
#   at t/100mbox-read.t line 73.
#  got: 49339
# expected: 49340
#   Failed test 'begin 13'
#   at t/100mbox-read.t line 73.
#  got: 52673
# expected: 52674
#   Failed test 'begin 14'
#   at t/100mbox-read.t line 73.
#  got: 54352
# expected: 54353
#   Failed test 'begin 15'
#   at t/100mbox-read.t line 73.
#  got: 57547
# expected: 57548
#   Failed test 'begin 16'
#   at t/100mbox-read.t line 73.
#  got: 59213
# expected: 59214
#   Failed test 'begin 17'
#   at t/100mbox-read.t line 73.
#  got: 61534
# expected: 61535
#   Failed test 'begin 18'
#   at t/100mbox-read.t line 73.
#  got: 65036
# expected: 65037
#   Failed test 'begin 19'
#   at t/100mbox-read.t line 73.
#  got: 66386
# expected: 66387
#   Failed test 'begin 20'
#   at t/100mbox-read.t line 73.
#  got: 68334
# expected: 68335
#   Failed test 'begin 21'
#   at t/100mbox-read.t line 73.
#  got: 70568
# expected: 70569
#   Failed test 'begin 22'
#   at t/100mbox-read.t line 73.
#  got: 71836
# expected: 71837
#   Failed test 'begin 23'
#   at t/100mbox-read.t line 73.
#  got: 73183
# expected: 73184
#   Failed test 'begin 24'
#   at t/100mbox-read.t line 73.
#  got: 74555
# expected: 74556
#   Failed test 'begin 25'
#   at t/100mbox-read.t line 73.
#  got: 77122
# expected: 77123
#   Failed test 'begin 26'
#   at t/100mbox-read.t line 73.
#  got: 82226
# expected: 82227
#   Failed test 'begin 27'
#   at t/100mbox-read.t line 73.
#  got: 84092
# expected: 84093
#   Failed test 'begin 28'
#   at t/100mbox-read.t line 73.
#  got: 87420
# expected: 87421
#   Failed test 'begin 29'
#   at t/100mbox-read.t line 73.
#  got: 89463
# expected: 89464
#   Failed test 'begin 30'
#   at t/100mbox-read.t line 73.
#  got: 90624
# expected: 90625
#   Failed test 'begin 31'
#   at t/100mbox-read.t line 73.
#  got: 93511
# expected: 93512
#   Failed test 'begin 32'
#   at t/100mbox-read.t line 73.
#  got: 96480
# expected: 96481
#   Failed test 'begin 33'
#   at t/100mbox-read.t line 73.
#  got: 99700
# expected: 99701
#   Failed test 'begin 34'
#   at t/100mbox-read.t line 73.
#  got: 102318
# expected: 102319
#   Failed test 'begin 35'
#   at t/100mbox-read.t line 73.
#  got: 102710
# expected: 102711
#   Failed test 'begin 36'
#   at t/100mbox-read.t line 73.
#  got: 103354
# expected: 103355
#   Failed 

Bug#922390: hydroffice.bag: FTBFS (Could not import extension sphinx.ext.pngmath)

[Santiago Vila]

Package: src:hydroffice.bag
Version: 0.2.15-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice
copying hydroffice/__init__.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/uncertainty.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/helper.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/__init__.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/base.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/elevation.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/meta.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/bbox.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/tracklist.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/bag.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_tracklist.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_bbox.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_elevation.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/__init__.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_validate.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_metadata.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_uncertainty.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/favicon.png -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/hyo_button.png -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/BAG.ico -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/BAG.icns -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
copying hydroffice/bag/iso19139/bag/bagCodelists.xml -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
copying hydroffice/bag/iso19139/bag/extension.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
copying hydroffice/bag/iso19139/bag/bag.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco
copying hydroffice/bag/iso19139/gco/gcoBase.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco
copying hydroffice/bag/iso19139/gco/basicTypes.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco
copying hydroffice/bag/iso19139/gco/gco.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco
copying hydroffice/bag/iso19139/gco/readme.txt -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd
copying hydroffice/bag/iso19139/gmd/maintenance.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd
copying hydroffice/bag/iso19139/gmd/spatialRepresentation.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd
copying hydroffice/bag/iso19139/gmd/dataQuality.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd
copying hydroffice/bag/iso19139/gmd/metadataApplication.xsd -> 

Bug#914223: marked as done (solr-jetty: doesn't remove records from statoverride after purge)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 11:05:06 +
with message-id 
and subject line Bug#914223: fixed in lucene-solr 3.6.2+dfsg-17
has caused the Debian Bug report #914223,
regarding solr-jetty: doesn't remove records from statoverride after purge
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.)


-- 
914223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: solr-jetty
Version: 3.6.2+dfsg-10+deb9u2
Severity: serious
Justification: Policy 10.9

solr-jetty was installed and purged from host. I'm not able to
dist-upgrade more:

dpkg: unrecoverable fatal error, aborting:
 unknown user 'jetty' in statoverride file


% dpkg -l | grep solr
% dpkg -l | grep jett
%
--- End Message ---
--- Begin Message ---
Source: lucene-solr
Source-Version: 3.6.2+dfsg-17

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated lucene-solr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Feb 2019 11:21:49 +0100
Source: lucene-solr
Architecture: source
Version: 3.6.2+dfsg-17
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 914223 917739
Changes:
 lucene-solr (3.6.2+dfsg-17) unstable; urgency=medium
 .
   * Team upload.
   * Do not build the lucene3 javadocs anymore. Very low popcon and build
 failures. (Closes: #917739)
   * Remove TODO.Debian.
   * Add web.xml.patch and use a correct DTD schema otherwise jasper will abort
 the build process.
   * Remove el-api.jar from the classpath to avoid a conflict with jasper-el.
   * Execute postrm commands in solr-jetty and solr-tomcat on purge too.
 (Closes: #914223)
Checksums-Sha1:
 d821a1c858c1f431262a49f584eabe9ecffeb848 3315 lucene-solr_3.6.2+dfsg-17.dsc
 73f292381b4c904155bcf9df259cf1bc6bb94ea4 53264 
lucene-solr_3.6.2+dfsg-17.debian.tar.xz
 9decbac6d7940055a76bef6e51b399c0a9f17ee7 14466 
lucene-solr_3.6.2+dfsg-17_amd64.buildinfo
Checksums-Sha256:
 fb234296d8037506d1a9081dc6595ec1ba40a989e5302bea00bc17d40346cea3 3315 
lucene-solr_3.6.2+dfsg-17.dsc
 2c123f0787cee3932dea52503cefc964e1b3914d0656df754148fb6acf7dd3cd 53264 
lucene-solr_3.6.2+dfsg-17.debian.tar.xz
 e45967a10cf4bbcae52f0e7eb61ad8e56e490fb9d2829bba3b77df03db3c75c5 14466 
lucene-solr_3.6.2+dfsg-17_amd64.buildinfo
Files:
 68516ad7ce87ffb60c24c30ab4eade72 3315 java optional 
lucene-solr_3.6.2+dfsg-17.dsc
 4f5ce670a8f53a7786ce383f05bd1b3f 53264 java optional 
lucene-solr_3.6.2+dfsg-17.debian.tar.xz
 43ca63b023bdb547d1d6d47d9021aa69 14466 java optional 
lucene-solr_3.6.2+dfsg-17_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlxmlulfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkUCoP/iSSLmA/jOcPZwF+XboYQA2naDbCKE0Kl/C9
R4tZFgDKQEoZ5wUBi64H2kKlm3hIlUm2rAy9RM2Ik3xQ7KjSR0k4SIO1XIPrsJvy
qLAlloe/uIU7kT67daU2vSqZ/QWfhj9YvYyXJhy0VZSKWrg9yEYvb+zDBlI5uet/
nXHflmY9RVAD8of9WLZ6FyxbPtA/I5d3DkVfGUSFeT9GlZOWzMf9+p90ahZckFD2
NtmB7yiJ7XsjjdTmZBuhszTHTBv+7QyuFSV2yAL9fxTknDy6vUlBpo9E2undgWKm
He7K/VA8Jr8c80FRxS0A9IlDG2XbYiMTByWbzALzcYhGe7Q7F880y61fj6YhXwEa
2EUyX0+MIApsHps6Y4MECdJu7MuS+ixh1AUkNwnm7gHCWpAQzp/7LmqH/KtSn+fZ
ag4o2WVwnQXAZRvMB7qCldVbqiFQPAgxav+74uisdDp2azBkeCIF6Kvzkt21oqLT
EKKu2vFhROmgW3NgX+qR+76qnWyZnBQ1BocxKCizcj+9m5wHcK5JU11xwuXIURgW
hWBDQIPEl7kxlCqd+y/qku/IPoM0xZ9wCNePTEPmBOxRE9eRhx7kxg4tuQCC9hHb
jqk3eUBD3aH3PODm4iZXpnH7Jk+D+YoXGaln5vsWgiSFi37aOpHhP541WBbLEXqz
ynp3G9QU
=uoVb
-END PGP SIGNATURE End Message ---

Bug#922389: golang-protobuf-extensions: FTBFS (cannot find package "github.com/golang/protobuf/proto/testdata")

[Santiago Vila]

Package: src:golang-protobuf-extensions
Version: 1.0.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
github.com/matttproud/golang_protobuf_extensions/ext 
github.com/matttproud/golang_protobuf_extensions/pbtest 
github.com/matttproud/golang_protobuf_extensions/pbutil
github.com/matttproud/golang_protobuf_extensions/ext
github.com/matttproud/golang_protobuf_extensions/pbtest
errors
internal/race
internal/cpu
internal/bytealg
runtime/internal/atomic
runtime/internal/sys
runtime
sync/atomic
sync
io
math
math/bits
unicode/utf8
strconv
unicode
reflect
encoding/binary
bytes
bufio
encoding
encoding/base64
syscall
time
internal/poll
internal/syscall/unix
internal/testlog
os
fmt
sort
strings
unicode/utf16
encoding/json
log
github.com/golang/protobuf/proto
github.com/matttproud/golang_protobuf_extensions/pbutil
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/matttproud/golang_protobuf_extensions/ext 
github.com/matttproud/golang_protobuf_extensions/pbtest 
github.com/matttproud/golang_protobuf_extensions/pbutil
# github.com/matttproud/golang_protobuf_extensions/pbutil
src/github.com/matttproud/golang_protobuf_extensions/pbutil/all_test.go:22:2: 
cannot find package "github.com/golang/protobuf/proto/testdata" in any of:
/usr/lib/go-1.11/src/github.com/golang/protobuf/proto/testdata (from 
$GOROOT)

/<>/obj-x86_64-linux-gnu/src/github.com/golang/protobuf/proto/testdata
 (from $GOPATH)
FAILgithub.com/matttproud/golang_protobuf_extensions/pbutil [setup failed]
?   github.com/matttproud/golang_protobuf_extensions/ext[no test files]
?   github.com/matttproud/golang_protobuf_extensions/pbtest [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/matttproud/golang_protobuf_extensions/ext 
github.com/matttproud/golang_protobuf_extensions/pbtest 
github.com/matttproud/golang_protobuf_extensions/pbutil returned exit code 1
make: *** [debian/rules:6: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-protobuf-extensions.html

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

Thanks.

Processed: reassign 922333 to libmail-box-perl

[Debian Bug Tracking System]

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

> reassign 922333 libmail-box-perl 3.005-2
Bug #922333 [libmail-message-perl] libmail-message-perl 3.008 breaks (the 
testsuite of) libmail-box-perl
Bug reassigned from package 'libmail-message-perl' to 'libmail-box-perl'.
No longer marked as found in versions libmail-message-perl/3.008-1.
Ignoring request to alter fixed versions of bug #922333 to the same values 
previously set
Bug #922333 [libmail-box-perl] libmail-message-perl 3.008 breaks (the testsuite 
of) libmail-box-perl
Marked as found in versions libmail-box-perl/3.005-2.
> thanks
Stopping processing here.

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

Bug#922391: isso: (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.min.js)

[Santiago Vila]

Package: src:isso
Version: 0.12.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild --test-nose
   dh_update_autotools_config -i -O--buildsystem=pybuild -O--test-nose
   dh_autoreconf -i -O--buildsystem=pybuild -O--test-nose
   dh_auto_configure -i -O--buildsystem=pybuild -O--test-nose
pybuild --configure --test-nose -i python{version} -p 3.7
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
nodejs /usr/lib/nodejs/requirejs/r.js -convert /usr/lib/nodejs/jade/lib/ 
isso/js/components/jade/
/usr/bin/make RJS="nodejs /usr/lib/nodejs/requirejs/r.js" LC_ALL=C.UTF-8 
SASS="sass --sourcemap=none"
make[2]: Entering directory '/<>'
/bin/sh: 1: git: not found
sphinx-build -b man docs/ -d debian/doctrees man/
Running Sphinx v1.8.3
making output directory...
building [mo]: targets for 0 po files that are out of date
building [man]: all manpages
updating environment: 17 added, 0 changed, 0 removed
reading sources... [  5%] contribute
reading sources... [ 11%] docs/configuration/client
reading sources... [ 17%] docs/configuration/server
reading sources... [ 23%] docs/extras/advanced-integration
reading sources... [ 29%] docs/extras/advanced-migration
reading sources... [ 35%] docs/extras/api
reading sources... [ 41%] docs/extras/deployment
reading sources... [ 47%] docs/index
reading sources... [ 52%] docs/install
reading sources... [ 58%] docs/man/index
reading sources... [ 64%] docs/quickstart
reading sources... [ 70%] docs/setup/multiple-sites
reading sources... [ 76%] docs/setup/sub-uri
reading sources... [ 82%] docs/troubleshooting
reading sources... [ 88%] faq
reading sources... [ 94%] news
reading sources... [100%] releasing

/<>/docs/docs/extras/advanced-migration.rst:12: WARNING: Error in 
"code-block" directive:
1 argument(s) required, 0 supplied.

.. code-block::

A list of threads, each item being a dict with the following data:

- id: a text representing the unique thread id (note: by default isso
  associates this ID to the article URL, but it can be changed on
  client side with "data-isso-id" - see :doc:`client configuration 
<../configuration/client>` )
- title: the title of the thread
- comments: the list of comments

Each item in that list of comments is a dict with the following data:

- id: an integer with the unique id of the comment inside the thread
  (it can be repeated among different threads); this will be used to
  order the comment inside the thread
- author: the author's name
- email: the author's email
- website: the author's website
- remote_addr: the author's IP
- created: a timestamp, in the format "%Y-%m-%d %H:%M:%S"
/<>/docs/docs/extras/advanced-migration.rst:35: WARNING: Error in 
"code-block" directive:
maximum 1 argument(s) allowed, 50 supplied.

.. code-block:: json
[
{
"id": "/blog/article1",
"title": "First article!"
comments": [
{
"author": "James",
"created": "2018-11-28 17:24:23",
"email": "em...@mail.com",
"id": "1",
"remote_addr": "127.0.0.1",
"text": "Great article!",
"website": "http://fefzfzef.frzr;
},
{
"author": "Harold",
"created": "2018-11-28 17:58:03",
"email": "ema...@mail.com",
"id": "2",
"remote_addr": "",
"text": "I hated it...",
"website": ""
}
]
}
]
looking for now-outdated files... none found
pickling environment... done
checking consistency... /<>/docs/contribute.rst: WARNING: document 
isn't included in any toctree
/<>/docs/docs/configuration/client.rst: WARNING: document isn't 
included in any toctree
/<>/docs/docs/configuration/server.rst: WARNING: document isn't 
included in any toctree
/<>/docs/docs/extras/advanced-integration.rst: WARNING: document 
isn't included in any toctree
/<>/docs/docs/extras/advanced-migration.rst: WARNING: document 
isn't included in any toctree
/<>/docs/docs/extras/api.rst: WARNING: document isn't included in 
any toctree
/<>/docs/docs/extras/deployment.rst: WARNING: document isn't 
included in any toctree
/<>/docs/docs/man/index.rst: WARNING: document isn't included in 
any toctree
/<>/docs/docs/setup/multiple-sites.rst: WARNING: document isn't 
included in any toctree
/<>/docs/docs/setup/sub-uri.rst: WARNING: document isn't included 
in any toctree
/<>/docs/faq.rst: WARNING: document isn't 

Bug#922376: marked as done (can't find executable chromedriver-helper for gem chromedriver-helper)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 10:49:11 +
with message-id 
and subject line Bug#922376: fixed in ruby-chromedriver-helper 2.1.0-2
has caused the Debian Bug report #922376,
regarding can't find executable chromedriver-helper for gem chromedriver-helper
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.)


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

Package: ruby-chromedriver-helper
version: 2.1.0-1
Severity: serious
justification: unable use the package
Control: affects -1 ruby-rails

Bundler::GemRequireError: There was an error while trying to load the 
gem 'chromedriver-helper'.
Gem Load Error is: can't find executable chromedriver-helper for gem 
chromedriver-helper

Backtrace for gem load error is:
/usr/lib/ruby/vendor_ruby/bundler/rubygems_integration.rb:462:in `block 
in replace_bin_path'
/usr/lib/ruby/vendor_ruby/bundler/rubygems_integration.rb:493:in `block 
in replace_bin_path'

/usr/lib/ruby/vendor_ruby/chromedriver-helper.rb:4:in `'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:71:in 
`require'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:71:in 
`block in require_with_bootsnap_lfi'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/loaded_features_index.rb:65:in 
`register'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:70:in 
`require_with_bootsnap_lfi'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:79:in 
`require'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:81:in `block (2 levels) in 
require'

/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:76:in `each'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:76:in `block in require'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:65:in `each'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:65:in `require'
/usr/lib/ruby/vendor_ruby/bundler.rb:114:in `require'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'

/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:703:in `raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:104:in `block in 
load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in 
`standard_exception_handling'

/usr/lib/ruby/vendor_ruby/rake/application.rb:103:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:82:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in 
`standard_exception_handling'

/usr/lib/ruby/vendor_ruby/rake/application.rb:80:in `run'
/usr/bin/rake:27:in `'
Bundler Error Backtrace:
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'


Caused by:
Gem::Exception: can't find executable chromedriver-helper for gem 
chromedriver-helper
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'

(See full trace by running task with --trace)
--- End Message ---
--- Begin Message ---
Source: ruby-chromedriver-helper
Source-Version: 2.1.0-2

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-chromedriver-helper 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: Fri, 15 Feb 2019 14:55:53 +0530
Source: ruby-chromedriver-helper
Binary: ruby-chromedriver-helper
Architecture: 

Processed: Bug #917739 in lucene-solr marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917739 [src:lucene-solr] lucene-solr: FTBFS:  [exec] Execute failed: 
java.io.IOException: Cannot run program "svnversion" (in directory 
"/<>/lucene-solr-3.6.2+dfsg/solr/contrib/dataimporthandler"): 
error=2, No such file or directory
Ignoring request to alter tags of bug #917739 to the same tags previously set

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

Bug#917739: Bug #917739 in lucene-solr marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/lucene-solr/commit/ffa0210c49e61094d4de67ac03b022d2a9c937d5


Do not build the lucene3 javadocs anymore. Very low popcon and build failures.

Closes: #917739


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917739

Processed: tagging 919138

[Debian Bug Tracking System]

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

> tags 919138 + pending
Bug #919138 [wpasupplicant] wpasupplicant: Fails to connect to some Wifi 
networks on version 2:2.7-3
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 919138

[Debian Bug Tracking System]

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

> tags 919138 + upstream patch
Bug #919138 [wpasupplicant] wpasupplicant: Fails to connect to some Wifi 
networks on version 2:2.7-3
Added tag(s) patch and upstream.
> thanks
Stopping processing here.

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

Bug#922356: marked as done (nbd: FTBFS in sid (rm: cannot remove 'gitstatus': No such file or directory))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 11:25:29 +0100
with message-id <20190215102529.mw77evbjgsmtquzm@nucold>
and subject line Re: Accepted nbd 1:3.19-2 (source amd64) into unstable
has caused the Debian Bug report #922356,
regarding nbd: FTBFS in sid (rm: cannot remove 'gitstatus': No such file or 
directory)
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
test -f nbd.h
if [ -d .git ]; then if [ $(git status --porcelain | tee gitstatus | wc -l) -ne 
1 ]; then echo "GIT STATUS:"; echo "==="; cat gitstatus; exit 1; fi; fi
rm gitstatus
rm: cannot remove 'gitstatus': No such file or directory
make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Version: 1:3.19-2

This upload effectively fixes Bug #922356.

Thanks.--- End Message ---

Bug#922383: nbd: FTBFS in sid (docbook2man: command not found)

[Santiago Vila]

Package: src:nbd
Version: 1:3.19-2
Severity: serious
Tags: ftbfs

Hello Wouter.

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


[...]

Making all in man
make[3]: Entering directory '/<>/man'
sh nbd-server.1.sh > nbd-server.1
sh nbd-server.5.sh > nbd-server.5
sh nbd-client.8.sh > nbd-client.8
sh nbd-trdump.1.sh > nbd-trdump.1
LC_ALL=C docbook2man nbdtab.5.in.sgml
/bin/bash: docbook2man: command not found
make[3]: *** [Makefile:677: nbdtab.5.sh.in] Error 127
make[3]: Leaving directory '/<>/man'
make[2]: *** [Makefile:837: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:481: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

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

[ Please consider uploading in source-only form (dpkg-buildpackage -S). It 
should work
  as far as there is no NEW processing ].

Thanks.

Bug#922145: closed by Rhonda D'Vine (Bug#922145: fixed in irssi 1.2.0-2)

[Rhonda D'Vine]

   Hey,

On 2/14/19 3:24 PM, Diederik de Haas wrote:
> On woensdag 13 februari 2019 15:51:04 CET you wrote:
>> #922145: irssi: trying to overwrite '/usr/share/irssi/help/otr', which is
>> also in package irssi-plugin-otr
>>
>> It has been closed by Rhonda D'Vine .
> 
> I think it's not actually fixed as I just got the error again.
> Now with version 1.2.0-2, but 'the other way around'.

 Yes, that's correct.  When fixing it in -2 I didn't do the things with
respect to Breaks+Replaces, and given that this affects only people
upgrading from 1.2.0-1 to 1.2.0-2 I consider it an acceptable tradeoff
to not roll out a -3. The -1 was only a bit more than half a day in the
archive, so ...

 So upgrading from testing (or former stable) to the 1.2.0 packages
should work without any troubles yet.  I'll specifically try that out,
especially also with respect to partial upgrades (like, only -otr
package, only irssi, both at the same times), and if something still
pops up I'll do the Breaks+Replaces dance. :)

 Cheers,
Rhonda

Processed: Re: solr-jetty: doesn't remove records from statoverride after purge

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #914223 [solr-jetty] solr-jetty: doesn't remove records from statoverride 
after purge
Added tag(s) pending.

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

Bug#914223: solr-jetty: doesn't remove records from statoverride after purge

[Markus Koschany]

Control: tags -1 pending

On Tue, 20 Nov 2018 21:11:14 +0300 sergio  wrote:
> Package: solr-jetty
> Version: 3.6.2+dfsg-10+deb9u2
> Severity: serious
> Justification: Policy 10.9
> 
> solr-jetty was installed and purged from host. I'm not able to
> dist-upgrade more:
> 
> dpkg: unrecoverable fatal error, aborting:
>  unknown user 'jetty' in statoverride file
> 
> 
> % dpkg -l | grep solr
> % dpkg -l | grep jett
> %

I believe this is caused by insufficient postrm scripts.

dpkg-statoverride --quiet --remove /var/lib/solr

and

dpkg-statoverride --quiet --remove /var/lib/solr/data

are only called when solr-jetty is removed but not on purge. The purge
command must be handled as well.





signature.asc
Description: OpenPGP digital signature

Processed: Re: lucene-solr: FTBFS: [exec] Execute failed: java.io.IOException: Cannot run program "svnversion" (in directory "/<>/lucene-solr-3.6.2+dfsg/solr/contrib/dataimporthandler"): err

[Debian Bug Tracking System]

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

> tags 917739 pending
Bug #917739 [src:lucene-solr] lucene-solr: FTBFS:  [exec] Execute failed: 
java.io.IOException: Cannot run program "svnversion" (in directory 
"/<>/lucene-solr-3.6.2+dfsg/solr/contrib/dataimporthandler"): 
error=2, No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#921718: marked as done (spring is broken /usr/lib/ruby/vendor_ruby/spring/client/run.rb:76:in `spawn': No such file or directory - /usr/lib/ruby/bin/spring (Errno::ENOENT))

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 09:19:59 +
with message-id 
and subject line Bug#921718: fixed in ruby-spring 2.0.2-2
has caused the Debian Bug report #921718,
regarding spring is broken /usr/lib/ruby/vendor_ruby/spring/client/run.rb:76:in 
`spawn': No such file or directory - /usr/lib/ruby/bin/spring (Errno::ENOENT)
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.)


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

Package: ruby-spring
version: 2.0.2-1
severity: serious
justification: breaks rails newapp autopkgtest

Bundle complete! 18 Gemfile dependencies, 76 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
run  bundle exec spring binstub --all
* bin/rake: spring inserted
* bin/rails: spring inserted
+ cd foo
+ rails runner puts "Empty Rails %s app booted correctly" % 
Rails.version
Warning: Running `gem pristine --all` to regenerate your installed 
gemspecs (and deleting then reinstalling your bundle if you use bundle 
--path) will improve the startup performance of Spring.
/usr/lib/ruby/vendor_ruby/spring/client/run.rb:76:in `spawn': No such 
file or directory - /usr/lib/ruby/bin/spring (Errno::ENOENT)

from /usr/lib/ruby/vendor_ruby/spring/client/run.rb:76:in `boot_server'
from /usr/lib/ruby/vendor_ruby/spring/client/run.rb:56:in `cold_run'
	from /usr/lib/ruby/vendor_ruby/spring/client/run.rb:33:in `rescue in 
call'

from /usr/lib/ruby/vendor_ruby/spring/client/run.rb:30:in `call'
from /usr/lib/ruby/vendor_ruby/spring/client/command.rb:7:in `call'
from /usr/lib/ruby/vendor_ruby/spring/client/rails.rb:24:in `call'
from /usr/lib/ruby/vendor_ruby/spring/client/command.rb:7:in `call'
from /usr/lib/ruby/vendor_ruby/spring/client.rb:30:in `run'
from /usr/bin/spring:49:in `'
from /usr/lib/ruby/vendor_ruby/spring/binstub.rb:31:in `load'
	from /usr/lib/ruby/vendor_ruby/spring/binstub.rb:31:in `(required)>'
	from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
	from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
	from 
/tmp/autopkgtest-lxc.y861r_eq/downtmp/autopkgtest_tmp/foo/bin/spring:15:in 
`'

from bin/rails:3:in `load'
from bin/rails:3:in `'
autopkgtest [16:28:40]: test newapp: ---]
autopkgtest [16:28:40]: test newapp:  - - - - - - - - - - results - - - 
- - - - - - -

newapp   FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: ruby-spring
Source-Version: 2.0.2-2

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-spring 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: Fri, 15 Feb 2019 14:06:22 +0530
Source: ruby-spring
Binary: ruby-spring
Architecture: source all
Version: 2.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-spring - Rails application preloader
Closes: 921718
Changes:
 ruby-spring (2.0.2-2) unstable; urgency=medium
 .
   * Use dh_ruby --gem-install option to fix relative path to bin
 (Closes: #921718)
   * Add autopkgtest
   * Add myself as uploader
Checksums-Sha1:
 8a5d70e759d6ed571cfb043034f708eb6f4559ab 2118 ruby-spring_2.0.2-2.dsc
 c54e18aa95258a6b6228f042ba8906382c99ea03 3596 ruby-spring_2.0.2-2.debian.tar.xz
 856238637c1a6f2c64b4abf5a7a32f354c22c952 40604 ruby-spring_2.0.2-2_all.deb
 af696bae386582738de82996bde227c630e6060b 10105 
ruby-spring_2.0.2-2_amd64.buildinfo
Checksums-Sha256:
 0d24fb73a3a5e6f93208a6241d1d443de283763979e7123666b421f6ff8c0d2d 2118 
ruby-spring_2.0.2-2.dsc
 28d05a862141f83408968af1194e3755e153ac86f7549c4272820c3403bac592 3596 
ruby-spring_2.0.2-2.debian.tar.xz
 bbf7e48419f94271547e7402ae6d80cc1ba8d954e2e5e959e61ee4915b83431c 40604 
ruby-spring_2.0.2-2_all.deb
 

Processed: can't find executable chromedriver-helper for gem chromedriver-helper

[Debian Bug Tracking System]

Processing control commands:

> affects -1 ruby-rails
Bug #922376 [ruby-chromedriver-helper] can't find executable 
chromedriver-helper for gem chromedriver-helper
Added indication that 922376 affects ruby-rails

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

Bug#922376: can't find executable chromedriver-helper for gem chromedriver-helper

[Pirate Praveen]

Package: ruby-chromedriver-helper
version: 2.1.0-1
Severity: serious
justification: unable use the package
Control: affects -1 ruby-rails

Bundler::GemRequireError: There was an error while trying to load the 
gem 'chromedriver-helper'.
Gem Load Error is: can't find executable chromedriver-helper for gem 
chromedriver-helper

Backtrace for gem load error is:
/usr/lib/ruby/vendor_ruby/bundler/rubygems_integration.rb:462:in `block 
in replace_bin_path'
/usr/lib/ruby/vendor_ruby/bundler/rubygems_integration.rb:493:in `block 
in replace_bin_path'

/usr/lib/ruby/vendor_ruby/chromedriver-helper.rb:4:in `'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:71:in 
`require'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:71:in 
`block in require_with_bootsnap_lfi'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/loaded_features_index.rb:65:in 
`register'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:70:in 
`require_with_bootsnap_lfi'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_require.rb:79:in 
`require'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:81:in `block (2 levels) in 
require'

/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:76:in `each'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:76:in `block in require'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:65:in `each'
/usr/lib/ruby/vendor_ruby/bundler/runtime.rb:65:in `require'
/usr/lib/ruby/vendor_ruby/bundler.rb:114:in `require'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'

/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:703:in `raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:104:in `block in 
load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in 
`standard_exception_handling'

/usr/lib/ruby/vendor_ruby/rake/application.rb:103:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:82:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in 
`standard_exception_handling'

/usr/lib/ruby/vendor_ruby/rake/application.rb:80:in `run'
/usr/bin/rake:27:in `'
Bundler Error Backtrace:
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'


Caused by:
Gem::Exception: can't find executable chromedriver-helper for gem 
chromedriver-helper
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/config/application.rb:7:in 
`'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`require_relative'
/tmp/autopkgtest-lxc.xf40v1iy/downtmp/autopkgtest_tmp/foo/Rakefile:4:in 
`'

(See full trace by running task with --trace)

Bug#871105: marked as done (debian-faq: FTBFS: Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml (translation discarded).)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 09:05:48 +
with message-id 
and subject line Bug#871105: fixed in debian-faq 9.0
has caused the Debian Bug report #871105,
regarding debian-faq: FTBFS: Addendum po4a/add_fr/commentaires.add does NOT 
apply to fr/debian-faq.sgml (translation discarded).
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.)


-- 
871105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-faq
Version: 8.1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> echo "" > faqdynamic.ent
> if [ -f debian/changelog ]; then \
>   echo " '^Version: ' | sed 's/^Version: *//'`\">" >> faqdynamic.ent; \
> else \
>   echo "" >> faqdynamic.ent; \
> fi
> PERL_PERTURB_KEYS=0 PERL_HASH_SEED=0 po4a --keep 0 --previous --rm-backups 
> po4a/po4a.cfg # --localized-charset UTF-8
> Negative repeat count does nothing at /usr/share/perl5/Locale/Po4a/Sgml.pm 
> line 1103,  line 8143.
> Negative repeat count does nothing at /usr/share/perl5/Locale/Po4a/Sgml.pm 
> line 1103,  line 8143.
> No candidate position for the addendum po4a/add_fr/commentaires.add.
> Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml 
> (translation discarded).
> Makefile:53: recipe for target 'po4a-translate' failed
> make[1]: *** [po4a-translate] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/debian-faq_8.1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated debian-faq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Nov 2018 23:41:33 +0100
Source: debian-faq
Binary: debian-faq debian-faq-de debian-faq-fr debian-faq-it debian-faq-nl 
debian-faq-ru debian-faq-zh-cn
Architecture: source all
Version: 9.0
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernandez-Sanguino Peña 
Changed-By: Dr. Tobias Quathamer 
Description:
 debian-faq - Debian Frequently Asked Questions
 debian-faq-de - Debian Frequently Asked Questions, in German
 debian-faq-fr - Debian Frequently Asked Questions, in French
 debian-faq-it - Debian Frequently Asked Questions, in Italian
 debian-faq-nl - Debian Frequently Asked Questions, in Dutch
 debian-faq-ru - Debian Frequently Asked Questions, in Russian
 debian-faq-zh-cn - Debian Frequently Asked Questions, in Chinese
Closes: 762167 787152 806994 851414 871105 873264 881647
Changes:
 debian-faq (9.0) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Holger Wansing ]
   * 2017-11-12: Add Dutch translation by Frans Spiesschaert (Closes: #881647)
 .
   [ Joost van Baal-Ilić ]
   * debian/changelog: update old changelog entries 5.0.2+nmu1 and 8.1
 (Closes: #762167, #806994)
   * 2017-11-30: debian/control: remove Simon Paillard from Uploaders; he hasn't
 been working on this package for 3 years.  As requested by Mattia Rizzolo /
 MIA team.  Thanks Mattia.  Simon: thanks and please do keep committing!
 (Closes: #873264)
   * 2017-11-30: customizing.sgml: Add section "booting": "How does a Debian
 system boot?", with patch with notes on systemd contributed by Alan Lee,
 and further improved by Vincent McIntyre and Justin B Rye.  Thanks!
 Add pointers to relevant