Processed (with 2 errors): Re: Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

[Debian Bug Tracking System]

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

> retitle 943401 C++ Unit tests failing (Failure instantiating protector
Bug #943401 [src:libreoffice] libreoffice: Autopkgtests are failing since 
2019-10-21
Changed Bug title to 'C++ Unit tests failing (Failure instantiating protector' 
from 'libreoffice: Autopkgtests are failing since 2019-10-21'.
> "/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.3.1/workdir/LinkTarget/Library/unoexceptionprotector.so",
Unknown command or malformed arguments to command.
> "unoexceptionprotector")
Unknown command or malformed arguments to command.
> severity 943401 serious
Bug #943401 [src:libreoffice] C++ Unit tests failing (Failure instantiating 
protector
Severity set to 'serious' from 'important'
> tag 943401 + sid
Bug #943401 [src:libreoffice] C++ Unit tests failing (Failure instantiating 
protector
Added tag(s) sid.
> tag 943401 + help
Bug #943401 [src:libreoffice] C++ Unit tests failing (Failure instantiating 
protector
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#943438: marked as done (src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 05:34:00 +
with message-id 
and subject line Bug#943438: fixed in icinga2 2.11.1-2
has caused the Debian Bug report #943438,
regarding src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency
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.)


-- 
943438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:icinga2
Version: 2.11.1-2~exp1
Severity: serious
Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

According to the transition tracker, the wxwidgets3.0-gtk3 transition is
96% and the only remaining blockers are a missing mips64el build of
codelite (currently building) and a missing mipsel build of mrpt (due
for AUTORM from testing on 2019-10-28):

https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html

However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
your package has a build-dependency on libwxgtk3.0-dev which doesn't
result in any shlib dependencies in the built packages.  If this package
is not actually used this build dependency should be dropped; if it's
used during the build then you want to update to use
libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
please debug!

Let me know if you'd like me to NMU a fix for this.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Source: icinga2
Source-Version: 2.11.1-2

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated icinga2 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, 25 Oct 2019 06:24:43 +0200
Source: icinga2
Architecture: source
Version: 2.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Bas Couwenberg 
Closes: 943438
Changes:
 icinga2 (2.11.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Don't add -latomic, didn't fix the FTBFS.
   * Switch to wxWidgets GTK 3 implementation.
 (closes: #943438)
   * Move from experimental to unstable.
Checksums-Sha1:
 b935bbc7d66c05019da6e95369a17082b48aae89 2779 icinga2_2.11.1-2.dsc
 7e0eaa7518edd96d3c162a08d1889e9a3fb1709c 22872 icinga2_2.11.1-2.debian.tar.xz
 3b1620109f41ce9ac824be96e66ac2515acad98b 16987 icinga2_2.11.1-2_amd64.buildinfo
Checksums-Sha256:
 c6c1f5c854e9cb883624fefdf05b97768ab34e64d77593ef7ff8953fcfdab336 2779 
icinga2_2.11.1-2.dsc
 753d1495fc2fef5f2b8ca509598b6d0178fc0c662f12dbb2ba68728f54b8201d 22872 
icinga2_2.11.1-2.debian.tar.xz
 9955dd4d9a043cd336291c754c785e1c34b9c7d7aee0b227e29675fe9660 16987 
icinga2_2.11.1-2_amd64.buildinfo
Files:
 7cf6e32b9ffc721a1dffc356c533dd51 2779 admin optional icinga2_2.11.1-2.dsc
 5b7acc854d08264b9b84998868a2d5cc 22872 admin optional 
icinga2_2.11.1-2.debian.tar.xz
 19d1482172ff2908cc2a28774b4d7efa 16987 admin optional 
icinga2_2.11.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl2yhVUACgkQZ1DxCuiN
SvEo9g/7BZ5FlnkmLwmIbWZzWUqK0t48FaDXdqQh1tiBXwi/zTrULy5mFTBqNACG
nb8J9gFTLCbBBg0Yq50e+tO11tDDC22daW2ljQQx1iWJKOTlSI4FDQleveH2lEbE
qkj1bv5tRMGUQeKUgvXtg+z9ZjVeuN843Qbuf7+nOCYViSRjEW1tO3NPVtDNwMCR
u6eTX+vzgGogEDGSBn+QUv+vKkwrQ3B9ZpVmpTphmg2/Vsyr2h/hhgjgfql0TipF
YRcOSZoADb8B5aGdYNFdWGB4JsuZV7hrun35mhnoSrHxEGYjf7zNfMkbfbdj5eWU
RdmL16u/I6gB5njcGmO3LoJqgnxHR97KEw4b8JEcOQkQA7BNpuzhmzm4tFbi9DGx
KdAEB2fZEBkEhAVzHAC1uPS2lqzYh7EbVkPStUoQywGolkWe0Mb4oY/VFGwp3Lwg
2N3nxIfnxsY2ioLxlvbfRYZocB41R1jYE58ymqWObFlvghJwBWyCqbQeFaZ1coTO
oozHVVeKLHlOiQTZWNwG31uwhjjoUTVJz0dxlBRSvTNSELE+oVHq5O1GKGZmxGdf
qLq1+bLmLvB9mHXIgPyLoAKsKfx4mnyHoyphXsBqGGo9+FxCG6otNEjimhRn+8Ym
VfzFzcbuDoCQr87bSuh8jj7kT2Kui6u4LvOxxeVzNihU+wsOiWs=
=rPUj
-END PGP SIGNATURE End Message ---

Bug#943440: marked as done (src:grass: Please update/remove libwxgtk3.0-dev build-dependency)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 05:19:13 +
with message-id 
and subject line Bug#943440: fixed in grass 7.8.0-2
has caused the Debian Bug report #943440,
regarding src:grass: Please update/remove libwxgtk3.0-dev build-dependency
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.)


-- 
943440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:grass
Version: 7.8.0-1
Severity: serious
Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

According to the transition tracker, the wxwidgets3.0-gtk3 transition is
96% and the only remaining blockers are a missing mips64el build of
codelite (currently building) and a missing mipsel build of mrpt (due
for AUTORM from testing on 2019-10-28):

https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html

However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
your package has a build-dependency on libwxgtk3.0-dev which doesn't
result in any shlib dependencies in the built packages.  If this package
is not actually used this build dependency should be dropped; if it's
used during the build then you want to update to use
libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
please debug!

Let me know if you'd like me to NMU a fix for this.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Source: grass
Source-Version: 7.8.0-2

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated grass 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, 25 Oct 2019 06:20:37 +0200
Source: grass
Architecture: source
Version: 7.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 943440
Changes:
 grass (7.8.0-2) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.4.1, no changes.
   * Switch to wxWidgets GTK 3 implementation.
 (closes: #943440)
Checksums-Sha1:
 23ea1cea7842aa7873f921f2cedb414c1fd8ffe1 2814 grass_7.8.0-2.dsc
 75cdadd3cc98be76d947cdbeb706792871e0f7bb 33488 grass_7.8.0-2.debian.tar.xz
 872756acc6669ff0d6127ffa6ad0b044ecf6daf5 21787 grass_7.8.0-2_amd64.buildinfo
Checksums-Sha256:
 1bb27bf502fb3720f99aa45e0a7003cfd1652f8874438c3edf46fdcefb8e7fe5 2814 
grass_7.8.0-2.dsc
 2e8a792b8b48c6c23e08d3f72839cd89ccc2ef2c54453d9c308a6be512fdd46c 33488 
grass_7.8.0-2.debian.tar.xz
 da7a5b93df8a22e256e6e004008f9ba77c977d428151196b5daccc91d5880afb 21787 
grass_7.8.0-2_amd64.buildinfo
Files:
 46edaee7b0bc423dfc94d6469954e9bf 2814 science optional grass_7.8.0-2.dsc
 6a4b9d219207ac7be43da9c488eabe74 33488 science optional 
grass_7.8.0-2.debian.tar.xz
 b694acd4d291a0ec81270a6a7b5da40e 21787 science optional 
grass_7.8.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl2ygL8ACgkQZ1DxCuiN
SvFbvxAAiSkEC/PTAUBBVUVcpqoIxAdsShudzjqb1+I0acV/8m9UU7ENWeYeVN+i
hInh5OfVSnhvV998ZZeRprKdb1Ale61b8HHJ62dTeGP7lHTUXsGGP3ZX4xHazsSp
3qhM2iRthiNiQP5qoR85NI69ePHAslA5RPSZWzLPZ4YuJ9rheGmqKs3p9GlMysXz
8erM/H9OMG/Hl+ZydTQnsTXfILHho/ktUeA63O+bG8Tymohs34GQUCN+NtXKndDf
1uW18VL28ga5245ohl/jaakcyyqujJctuyL0o+3Et9khBzJFpd3TNeaEfNshaolV
agQhDmOYHDMCYebU9Dy6gxwGu0gOKygl6Ik6XPvltpk774xk/MMNtPercRN07kCf
zSptxFsb2pRCAdESR1RtuOsm7zEXhQy0XqodMlnBqwJ/MdtI7gR1JCPhCPzJXZcr
/UTuey6ASFdCluIezuCYJWxMc3S5IIb30/KBldxfaaz7m1vAsJb/4rYmeItaAiSS
TSzf/bMTj+SbAyat6Vz2vTC4uL/18ZYtyLNLZ/giIIFdhp9AVWAzUZODmhjwqrTd
w8M/wZvFpG5Zf5WAiWBwL17NkCFzL7JK/3gv9ay0u3hKSl+qq9WINHQoClTqYQy9
tUMC6mpzhJ6zWhczLlSvvu1ErHfnHuuxs38zNMEBioCcItwiBU0=
=4nsz
-END PGP SIGNATURE End Message ---

Processed: Re: [Pkg-nagios-devel] Bug#943438: src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #943438 [src:icinga2] src:icinga2: Please update/remove libwxgtk3.0-dev 
build-dependency
Added tag(s) pending.

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

Bug#943438: [Pkg-nagios-devel] Bug#943438: src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 10/24/19 9:36 PM, Olly Betts wrote:
> However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
> your package has a build-dependency on libwxgtk3.0-dev which doesn't
> result in any shlib dependencies in the built packages.  If this package
> is not actually used this build dependency should be dropped; if it's
> used during the build then you want to update to use
> libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
> please debug!

The build dependency has been updated, and an upload to unstable will
follow shortly.

Kind Regards,

Bas

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

Bug#943440: src:grass: Please update/remove libwxgtk3.0-dev build-dependency

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 10/24/19 9:24 PM, Olly Betts wrote:
> However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
> your package has a build-dependency on libwxgtk3.0-dev which doesn't
> result in any shlib dependencies in the built packages.  If this package
> is not actually used this build dependency should be dropped; if it's
> used during the build then you want to update to use
> libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
> please debug!

The build dependency has been updated, and an upload to unstable will
follow shortly.

Kind Regards,

Bas

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

Processed: Re: Bug#943440: src:grass: Please update/remove libwxgtk3.0-dev build-dependency

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #943440 [src:grass] src:grass: Please update/remove libwxgtk3.0-dev 
build-dependency
Added tag(s) pending.

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

Bug#927747: [Pkg-samba-maint] Bug#927747: bind9_dlz backend is entirely broken in Debian

[Cameron Davidson]

I would like to add my observations on this bug after upgrading from
stretch to 10.1.

The apparmor fixes seem OK so far.

My samba system was originally created by moving a samba-3 system from
CentOS 6 to Debian 9 and then using the samba tools to migrate to an
ad-dc system. I mention this, because that migration path, while
surprisingly smooth, was not without a need for some manual
intervention.  So some of what I obseved might be specific  to my
situation, since it was not installed on Debian from scratch.

At the end of the Buster upgrade, everything seemed to be running OK,
however once I needed to make some changes to and check the bind9 config
the problems became apparent.

1. the bind config was still pointing at
/var/lib/samba/private/named.conf and that file was still loading the
9.10 library, rather than 9.11.

2. After fixing that, I ran the suggested test of  "samba_dnsupdate 
--verbose --all-names"  and every line reported "failed".

3. I then tried the suggestion from the samba wiki of "samba_upgradedns
--dns-backend=BIND9_DLZ"

That failed due to the non-existence of the /var/lib/samba/bind-dns
directory, which led me to this bug report.

I manually created that directory, gave it what I guessed might be
suitable group ownership and permissions, and reran the samba_upgradedns
script.

The result of that was that there were no errors, and the program
reported that I needed to manually adjust the two entries in the bind9
config files to point to the new directory.


So it seems to me that the problem could be safely fixed by changing the
samba_upgradedns script to check for and create the bind-dns folder if
necessary. (I suppose that is an upstream issue and the full
ramifications would need to be considered)

Running this script in postinst would be appropriate, but you would
somehow need to determine that the user was already using the bind9_dlz
backend.


The result of the upgrade script running is that:

1. the new config file is created, that loads the correct version dlz
library (but "including" that file needs to be manually edited in main
bind9 config (options or local - wiki says .local, but mine was in
.options))

2. the gssapi-key  file is created as a hard link between private and
bind-dns locations, so old config still works, but user is advised to
manually update the bind9 .options file.


Cameorn.

Bug#943462: [polkit-kde-agent-1] Fails to start with elogind

[Alex Volkov]

Package: polkit-kde-agent-1
Version: 4:5.14.5-1
Severity: serious

--- Please enter the report below this line. ---

I'm using elogind 239.3+20190131-1+debian1 and the agent fails to start
at the kde launch with the following diagnostics:

===
New PolkitAgentListener  0xbfaf9ca0
Adding new listener  PolkitQt1::Agent::Listener(0x7fb730017260) for  
0xbfaf9ca0
Listener online
"Cannot create unix session: No session for pid 17113"

** (process:17113): CRITICAL **: 06:38:20.880: 
polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT 
(subject)' failed
"Cannot register authentication agent!"
Authentication agent result: false
Couldn't register listener!
===

(This may or may not have connection to bug #850778 in plasma-desktop,
which seems to be the issue with polkit not recognizing a logged-in user.)

--- System information. ---
Architecture: 
Kernel:   Linux 5.2.17-bootes2-iommu-p-1000

Debian Release: 10.1
  991 stable  security.debian.org 
  991 stable  ftp.fi.debian.org 
  990 buster-backports ftp.debian.org 
   99 stable-backports www.deb-multimedia.org 
   99 stable  www.deb-multimedia.org 
  500 stable  dl.google.com 
  500 stable  deb.torproject.org 
  100 testing ftp.fi.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-
policykit-1  | 0.105-26
libc6   (>= 2.4) | 
libkf5coreaddons5   (>= 4.100.0) | 
libkf5crash5 (>= 4.96.0) | 
libkf5dbusaddons5(>= 4.97.0) | 
libkf5i18n5  (>= 4.97.0) | 
libkf5iconthemes5(>= 4.96.0) | 
libkf5widgetsaddons5 (>= 4.96.0) | 
libkf5windowsystem5  (>= 4.96.0) | 
libpolkit-qt5-1-1   (>= 0.112.0) | 
libqt5core5a (>= 5.11.0~rc1) | 
libqt5dbus5 (>= 5.11.0~) | 
libqt5gui5  (>= 5.11.0~) | 
libqt5widgets5  (>= 5.11.0~) | 
libstdc++6(>= 4.1.1) | 


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

[Olly Betts]

On Thu, Oct 24, 2019 at 10:12:08PM +0100, Olly Betts wrote:
> On Fri, Oct 25, 2019 at 12:02:11AM +0300, Jussi Pakkanen wrote:
> > https://mentors.debian.net/package/meson
> > 
> > Feel free to upload it to the archive.
> 
> Thanks for the quick response.  Building now.

It seems this package requires more diskspace to build than my build
chroot partition has (or perhaps I've just managed to break my chroot
recently).

I'll try to sort out my chroots over the weekend, but meanwhile if you
can get somebody else to sponsor please go for it.

Cheers,
Olly

Bug#942674: marked as done (git: FTBFS on big-endian targets - testsuite failure)

[Debian Bug Tracking System]

Your message dated Fri, 25 Oct 2019 00:49:17 +
with message-id 
and subject line Bug#942674: fixed in git 1:2.24.0~rc1-1
has caused the Debian Bug report #942674,
regarding git: FTBFS on big-endian targets - testsuite failure
to be marked as done.

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

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


-- 
942674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git
Version: 1:2.24.0~rc0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
User: debian-s...@lists.debian.org
Usertags: s390x

Hi!

git currently fails to build from source on all big-endian targets due
to test suite failures. This includes powerpc, ppc64, sparc64 and s390x
which is why this bug has severity serious [1].

There have been testsuite failures on big-endian in the past before,
see [2]. I will also notify upstream.

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=git=s390x=1%3A2.24.0%7Erc0-1=1571440098=0
> [2] https://www.spinics.net/lists/git/msg363527.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.24.0~rc1-1

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

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated git 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: Thu, 24 Oct 2019 15:44:01 -0700
Source: git
Architecture: source
Version: 1:2.24.0~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Jonathan Nieder 
Closes: 942674
Changes:
 git (1:2.24.0~rc1-1) unstable; urgency=medium
 .
   * new upstream release candidate.
 * test-tool: read --total as an int, not uint64 (thx John Paul Adrian
   Glaubitz; closes: #942674)
Checksums-Sha1:
 c268ff963a186136e397734c60400c579ba767cf 2919 git_2.24.0~rc1-1.dsc
 f282663a0681984d216f5120fb397d2159332c07 5753612 git_2.24.0~rc1.orig.tar.xz
 0a9351a59280cbb094e2941ab6168ff139819a5a 628388 git_2.24.0~rc1-1.debian.tar.xz
 3f86a5f84e807edc54988d2e97d875c6c123f0d5 12563 git_2.24.0~rc1-1_amd64.buildinfo
Checksums-Sha256:
 fcfd18a79763dd0242fcc3b829ffa615436d0f5e9915f6500d4ea6a8623eb0ff 2919 
git_2.24.0~rc1-1.dsc
 508c6d35302ee6279613c494f7d49f784b7b702e0e5e1a828399f5df3ab04483 5753612 
git_2.24.0~rc1.orig.tar.xz
 17ac38a53b168878de947dde9ae0d7b58fe756540574cd0ea80500608d458273 628388 
git_2.24.0~rc1-1.debian.tar.xz
 70d3b96493f4f61eff784969d649de6d9754cd28305b5c3464a3db6aa887d6d1 12563 
git_2.24.0~rc1-1_amd64.buildinfo
Files:
 856458f2ae33857709fa05746922b95b 2919 vcs optional git_2.24.0~rc1-1.dsc
 18464fac19326a5f29655d9d1cf0c1f8 5753612 vcs optional 
git_2.24.0~rc1.orig.tar.xz
 b718490002c263f07d8487b4ece585e6 628388 vcs optional 
git_2.24.0~rc1-1.debian.tar.xz
 3f72312c985705413b9e9740e00aaf1a 12563 vcs optional 
git_2.24.0~rc1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEUh5Y8X6W1xKqD/EC38Zx7rMz+iUFAl2yQ2QTHGpybmllZGVy
QGdtYWlsLmNvbQAKCRDfxnHuszP6JY9KEACjf4G404/VGIr/6tV65FQg5BsudgxC
H4QPmTUA41Lb5SSA7sbaImJxp/x2sLO2FAVVOBUK08WrWUPiNLMc/Ujoq7SUNTk6
zWI5BoBf9RY/h90gerTrR34ZOmZi4oje53ivwAgFGcNYove/BIPj8W98TDxPyoOV
0wWaMkLbv9kVaeoOi7eBfa00y4uKW85/hqQXNaQJpZIFbunGgX9UtdJvi51my2mT
2v7L/ARtLHtdJk741jA/o5iei0uRpXP7Z9iNLAr9co028c1Az3VDz7aupKodO+bY
uCopq/UEYuKz8FigpEXEuP/HvrELMYu70xi2b0+jsTZS5B9n+9FmMttzdko2M7G3
1DCcjzQH44iUk8YJDloyGKZ3Nd9LLarDhO3uQ12cc1Tjlr8R54OKfimRi9kte+61
106JiuyorpMSsMRKjSmCrA+jIHJm9MUepgT865qGCzHhE4H8zEu+J/uQz4syfZxC
wBgqiO/aHhvW6wTwbIw6e4Ae3xR2ah/aI8+r0GRkH34wHScchheT0YcRK8DycNB6
4Qt41hOrbc7rFPHcHEAyekTb3umZ4LVPgfXzIc6mjhmL9idoakNIvCnwwnz39ELM
WBUDtEaQVWCIlbCUTG1sc9VP0YbsjDvXL2Fekq+Nj+pwDk9NI5uoN43UZIJ+NcWD
oJ1Ja8pMQzeu9A==
=9nYN
-END PGP SIGNATURE End Message ---

Bug#943439: marked as done (src:asc: Please update/remove libwxgtk3.0-dev build-dependency)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 22:04:21 +
with message-id 
and subject line Bug#943439: fixed in asc 2.6.1.0-6
has caused the Debian Bug report #943439,
regarding src:asc: Please update/remove libwxgtk3.0-dev build-dependency
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.)


-- 
943439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:asc
Version: 2.6.1.0-5
Severity: serious
Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

According to the transition tracker, the wxwidgets3.0-gtk3 transition is
96% and the only remaining blockers are a missing mips64el build of
codelite (currently building) and a missing mipsel build of mrpt (due
for AUTORM from testing on 2019-10-28):

https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html

However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
your package has a build-dependency on libwxgtk3.0-dev which doesn't
result in any libwxgtk* shlib dependencies in the built packages.

The asc binary package does get a dependency on libwxbase3.0-0v5,
which suggests that your package should actually build-depend on
libwxbase3.0-dev.  However trying a build with that change it fails
due to not finding autotools macros 'AM_OPTIONS_WXCONFIG' and
'AM_PATH_WXCONFIG', so the correct fix is to update your package to
use libwxgtk3.0-gtk3-dev instead.

Let me know if you'd like me to NMU a fix for this.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Source: asc
Source-Version: 2.6.1.0-6

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated asc 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, 24 Oct 2019 22:58:03 +0200
Source: asc
Architecture: source
Version: 2.6.1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 943439
Changes:
 asc (2.6.1.0-6) unstable; urgency=medium
 .
   * Switch to debhelper-compat = 12.
   * Declare compliance with Debian Policy 4.4.1.
   * Replace libwxgtk3.0-dev build-dependency with libwxgtk3.0-gtk3-dev.
 (Closes: #943439)
Checksums-Sha1:
 ed3f6dfd4fcff4619919192250a914ada78b6896 2481 asc_2.6.1.0-6.dsc
 60654e7b9769f46347b0650c183f38f79ef3b61a 21416 asc_2.6.1.0-6.debian.tar.xz
 02d16355cec54330c6d96c3a383cbb0751af8d5e 15659 asc_2.6.1.0-6_amd64.buildinfo
Checksums-Sha256:
 b62899b3ba34d73ef2fa0365c19e46f33473d2ecbbdea9ee728d87db280e085b 2481 
asc_2.6.1.0-6.dsc
 2a228d7fa7f0dbcda9d103a35269e4e40ebf1fb78e401c50f972fa0c67a1f4c6 21416 
asc_2.6.1.0-6.debian.tar.xz
 9c324dd67141824fd68710c291271cf5058771c0d09ef50f1c71ef08e0bba536 15659 
asc_2.6.1.0-6_amd64.buildinfo
Files:
 cdfe4203aaa8c00e339bfbde1193202e 2481 games optional asc_2.6.1.0-6.dsc
 314d3d2b9d66ac0b391d9eb67e8a4d91 21416 games optional 
asc_2.6.1.0-6.debian.tar.xz
 5f6e605d6a9014deacb4638276f2c0c5 15659 games optional 
asc_2.6.1.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl2yHadfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk5s4QAJVw901s6SUnpSI42KI5q5iFG4ryx59moCJ3
rJnGYSLEb+bBsW96asLN9BlEaI06KVwpuKW5jCYd4BzAi/x7Nc2Z86jJ6Hyhu9VS
X59NpCNP74xfWYeWMgvQoSm9998QGs1hLS4iNa0sz9sf1DQBKA2El2rhiwCYIDyV
970xFL9GPYzrh7WHWjQX0nrS0nFCzZSH5nG9cZbthYIj/qyZUPVY9Y43NbWU0BrC
XRPBGF49lm62wwt03M9tSLrYLmqvu071QoDLEoONgkZ/1lEJbiCLwa1ZTyLR/W4V
9PSe75KaM32mAYhPO6Jl7BqiO4qNbFoPSGziFi9jGkyMxUlcl8E82866u/Uqkulh
r/Npa7LxKqlPoupX6a0mDP3jLbad3qOW0CI7l93LxoS9ZZoji2DcfBRHk/OZ2MRe
OnXtpHcJTIc22jY2XygZvrFwieL1d89RCH83SVFo5oT7o/JaCI3dNKDL7QV8bPeA
+/dkYoh5o5gKCMfVDZ7l3hEUuKNXfVet18HlZKa9m1BrcpGUe+5kQbFAqSxLPuTX
9zk4bOMV4QoCTF/5SsUsKOfCjQ8NleH5amgOJdigSBr64WNwO0HAee19+EPSsGur
fkjlPxs42wfbOgnGL9h5n70WWuYFUAWvJcr3dJqocn7QJvCH9/ryoodnF6YugLD0
GhL8+Izp
=zoXl
-END PGP SIGNATURE End Message 

Bug#942768: marked as done (lcl-units-2.0: file conflict with lazarus-src-2.0 (versin 2.0.2+dfsg-5))

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 22:05:40 +
with message-id 
and subject line Bug#942768: fixed in lazarus 2.0.2+dfsg-7
has caused the Debian Bug report #942768,
regarding lcl-units-2.0: file conflict with lazarus-src-2.0 (versin 
2.0.2+dfsg-5)
to be marked as done.

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

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


-- 
942768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lcl-units-2.0
Version: 2.0.2+dfsg-5
Severity: important

Dear Maintainer,

The new version of the package cannot be installed together with lazarus-src-2.0
because both packages contain the file

 /usr/lib/lazarus/2.0.2/components/IdeInspector/ideinspector.lpk


Best wishes,

Jan

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

Kernel: Linux 5.3.6-xanmod5 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lcl-units-2.0 depends on:
ii  fp-units-rtl-3.0.4 [fpc-abi-3.0.4]  3.0.4+dfsg-22
ii  lcl-gtk2-2.02.0.2+dfsg-5
ii  lcl-qt5-2.0 2.0.2+dfsg-5

Versions of packages lcl-units-2.0 recommends:
ii  fpc  3.0.4+dfsg-22
ii  fpc-3.0.4 [fpc]  3.0.4+dfsg-22

Versions of packages lcl-units-2.0 suggests:
ii  gdb  8.3.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lazarus
Source-Version: 2.0.2+dfsg-7

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

Debian distribution maintenance software
pp.
Abou Al Montacir  (supplier of updated lazarus 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, 24 Oct 2019 23:33:59 +0200
Source: lazarus
Architecture: source
Version: 2.0.2+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Abou Al Montacir 
Closes: 942768
Changes:
 lazarus (2.0.2+dfsg-7) unstable; urgency=medium
 .
   * Fixed version upon upgrade to create files diversion for lpk files.
 (Closes: Bug#942768)
   * Fixed logic to remove diversion of lpk files as per policy requirements.
   * Bumped standard version to 4.4.1.
Checksums-Sha1:
 e4a237adf11176d6d25520b6c8d1744b41f0eb0b 2990 lazarus_2.0.2+dfsg-7.dsc
 1031581f23404ac0a49439ded87ef89e7f85f4cd 71508 
lazarus_2.0.2+dfsg-7.debian.tar.xz
 37931e41e34ad60fcd8eb22717d94b4e278378a9 19663 
lazarus_2.0.2+dfsg-7_amd64.buildinfo
Checksums-Sha256:
 dfa26c574aa2347c608cbc887e30bc8249bdf3ba49425d618cc4df577102d128 2990 
lazarus_2.0.2+dfsg-7.dsc
 a42b9693faae851cc69cd97cc36dd2cdffe74af17c5751d30d0b0ba8db4add5d 71508 
lazarus_2.0.2+dfsg-7.debian.tar.xz
 bcca1e2da60ef751a036b4f78ae61342171a625446f82be2f38127ef039f3c0f 19663 
lazarus_2.0.2+dfsg-7_amd64.buildinfo
Files:
 41ec15066e08c13442ea8260c1c1b629 2990 devel optional lazarus_2.0.2+dfsg-7.dsc
 4bcb96188544125851bcb1c33730a2cd 71508 devel optional 
lazarus_2.0.2+dfsg-7.debian.tar.xz
 46062663b3f4af03d7a890236704cf13 19663 devel optional 
lazarus_2.0.2+dfsg-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iI0EAREKADUWIQS69sZENhB4UNQicQazJVxtVYeNjAUCXbIe6BccYWJvdS5hbG1v
bnRhY2lyQHNmci5mcgAKCRCzJVxtVYeNjBBgAP9J6AottXrvlyjyrvqFjeB+HdP+
am0V10C8UY7K7n7ASAD/V0nbySn9MsjIJZm5LtcLGQdLlQEdu5QjtcuPbrO9B4o=
=kZZo
-END PGP SIGNATURE End Message ---

Bug#943439: src:asc: Please update/remove libwxgtk3.0-dev build-dependency

[Markus Koschany]

Hi Olly,

Am 24.10.19 um 21:31 schrieb Olly Betts:
> Package: src:asc
> Version: 2.6.1.0-5
> Severity: serious
> Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

[...]

Thanks for reporting. I have uploaded a new revision of asc that uses
libwxgtk3.0-gtk3-dev instead of libwxgtk3.0-dev and it seems to make no
difference.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#943439: marked as pending in asc

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #943439 in asc 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/games-team/asc/commit/3d482be76754148688721f79e23aa93c59198a20


Replace libwxgtk3.0-dev build-dependency with libwxgtk3.0-gtk3-dev.

Closes: #943439


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943439

Processed: Bug#943439 marked as pending in asc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #943439 [src:asc] src:asc: Please update/remove libwxgtk3.0-dev 
build-dependency
Added tag(s) pending.

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

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

[Olly Betts]

Control: tags -1 +pending

On Fri, Oct 25, 2019 at 12:02:11AM +0300, Jussi Pakkanen wrote:
> On Thu, Oct 24, 2019 at 11:03 PM Olly Betts  wrote:
> 
> > However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
> > your package has a build-dependency on libwxgtk3.0-dev which doesn't
> > result in any shlib dependencies in the built packages.  If this package
> > is not actually used this build dependency should be dropped; if it's
> > used during the build then you want to update to use
> > libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
> > please debug!
> 
> The reason for this is that Meson only needs wxwidgets to build and
> execute its unit tests. They are not installed or used, because we
> only test that people can find and build against wxwidgets libraries.
> 
> I have updated the packaging to use the new package. It can be found in 
> mentors:
> 
> https://mentors.debian.net/package/meson
> 
> Feel free to upload it to the archive.

Thanks for the quick response.  Building now.

> You should note that the FPGA tests don't pass now. This has nothing
> to do with this change, it seems that Icestorm packages are broken in
> some way.

Presumably these are autopkgtests rather than tests run during the
package build?

Cheers,
Olly

Processed: Re: Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #943437 [src:meson] src:meson: Please update/remove libwxgtk3.0-dev 
build-dependency
Added tag(s) pending.

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

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

[Jussi Pakkanen]

On Thu, Oct 24, 2019 at 11:03 PM Olly Betts  wrote:

> However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
> your package has a build-dependency on libwxgtk3.0-dev which doesn't
> result in any shlib dependencies in the built packages.  If this package
> is not actually used this build dependency should be dropped; if it's
> used during the build then you want to update to use
> libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
> please debug!

The reason for this is that Meson only needs wxwidgets to build and
execute its unit tests. They are not installed or used, because we
only test that people can find and build against wxwidgets libraries.

I have updated the packaging to use the new package. It can be found in mentors:

https://mentors.debian.net/package/meson

Feel free to upload it to the archive. You should note that the FPGA
tests don't pass now. This has nothing to do with this change, it
seems that Icestorm packages are broken in some way.

Bug#943447: the autopkg test calls python instead of python2

[Matthias Klose]

Package: src:gexiv
Version: 0.10.9-1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support.


http://launchpadlibrarian.net/448276453/gexiv2_0.10.9-1_0.10.9-1ubuntu1.diff.gz

Bug#943446: the autopkg test calls python instead of python2

[Matthias Klose]

Package: src:last-align
Version: 983-1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support.


http://launchpadlibrarian.net/448278213/last-align_983-1_983-1ubuntu1.diff.gz

Bug#943445: the autopkg test calls python instead of python2

[Matthias Klose]

Package: src:python-fann2
Version: 1:1.1.2+ds-1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support.


http://launchpadlibrarian.net/448288137/python-fann2_1%3A1.1.2+ds-1build1_1%3A1.1.2+ds-1ubuntu1.diff.gz

Bug#943444: the autopkg test calls python instead of python2

[Matthias Klose]

Package: src:tlsh
Version: 3.4.4+20151206-1.1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support.


http://launchpadlibrarian.net/448289063/tlsh_3.4.4+20151206-1.1build1_3.4.4+20151206-1.1ubuntu1.diff.gz

Bug#941537: Merge request

[Dr. Tobias Quathamer]

control: tag -1 pending

Am 24.10.19 um 20:35 schrieb Adrian Heine:
> I opened a merge request:
> https://salsa.debian.org/debian/lilypond/merge_requests/1

Merged, thanks.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Processed: Re: Merge request

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941537 [lilypond] lilypond: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) pending.

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

Processed: block 894663 with 943437 943438 943439 943440

[Debian Bug Tracking System]

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

> block 894663 with 943437 943438 943439 943440
Bug #894663 [release.debian.org] transition: wxwidgets3.0-gtk3
894663 was blocked by: 934099 933415 933454 933430 933447 933452 933463 933423 
933434 933436 933432 933426 933455 933469 933445 895134 933472 933424 933418 
933476 933413 933417 933429 933435 933462 933461 933456 934098 933477 933465 
933448 933458 933446 933474 933480 933466 933411 933473 933433 933425 933440 
933420 934097 933407 933416 933451 933442 933450 933470 933467 933478 933479 
933441 933459 934096 933444 933457 933453 933475 933421 933419 933468 933422 
933464 933412 933431 933471 933414 933427 933439 933428 933443 933438 933408 
933460 933409
894663 was not blocking any bugs.
Added blocking bug(s) of 894663: 943439, 943437, 943438, and 943440
> thanks
Stopping processing here.

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

Bug#943439: src:asc: Please update/remove libwxgtk3.0-dev build-dependency

[Olly Betts]

Package: src:asc
Version: 2.6.1.0-5
Severity: serious
Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

According to the transition tracker, the wxwidgets3.0-gtk3 transition is
96% and the only remaining blockers are a missing mips64el build of
codelite (currently building) and a missing mipsel build of mrpt (due
for AUTORM from testing on 2019-10-28):

https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html

However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
your package has a build-dependency on libwxgtk3.0-dev which doesn't
result in any libwxgtk* shlib dependencies in the built packages.

The asc binary package does get a dependency on libwxbase3.0-0v5,
which suggests that your package should actually build-depend on
libwxbase3.0-dev.  However trying a build with that change it fails
due to not finding autotools macros 'AM_OPTIONS_WXCONFIG' and
'AM_PATH_WXCONFIG', so the correct fix is to update your package to
use libwxgtk3.0-gtk3-dev instead.

Let me know if you'd like me to NMU a fix for this.

Cheers,
Olly

Bug#943440: src:grass: Please update/remove libwxgtk3.0-dev build-dependency

[Olly Betts]

Package: src:grass
Version: 7.8.0-1
Severity: serious
Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

According to the transition tracker, the wxwidgets3.0-gtk3 transition is
96% and the only remaining blockers are a missing mips64el build of
codelite (currently building) and a missing mipsel build of mrpt (due
for AUTORM from testing on 2019-10-28):

https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html

However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
your package has a build-dependency on libwxgtk3.0-dev which doesn't
result in any shlib dependencies in the built packages.  If this package
is not actually used this build dependency should be dropped; if it's
used during the build then you want to update to use
libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
please debug!

Let me know if you'd like me to NMU a fix for this.

Cheers,
Olly

Bug#943438: src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency

[Olly Betts]

Package: src:icinga2
Version: 2.11.1-2~exp1
Severity: serious
Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

According to the transition tracker, the wxwidgets3.0-gtk3 transition is
96% and the only remaining blockers are a missing mips64el build of
codelite (currently building) and a missing mipsel build of mrpt (due
for AUTORM from testing on 2019-10-28):

https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html

However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
your package has a build-dependency on libwxgtk3.0-dev which doesn't
result in any shlib dependencies in the built packages.  If this package
is not actually used this build dependency should be dropped; if it's
used during the build then you want to update to use
libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
please debug!

Let me know if you'd like me to NMU a fix for this.

Cheers,
Olly

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

[Olly Betts]

Package: src:meson
Version: 0.52.0-1
Severity: serious
Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition

According to the transition tracker, the wxwidgets3.0-gtk3 transition is
96% and the only remaining blockers are a missing mips64el build of
codelite (currently building) and a missing mipsel build of mrpt (due
for AUTORM from testing on 2019-10-28):

https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html

However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that
your package has a build-dependency on libwxgtk3.0-dev which doesn't
result in any shlib dependencies in the built packages.  If this package
is not actually used this build dependency should be dropped; if it's
used during the build then you want to update to use
libwxgtk3.0-gtk3-dev instead; if it should result in a shlib dependency,
please debug!

Let me know if you'd like me to NMU a fix for this.

Cheers,
Olly

Bug#943396: FTBFS on armhf: testsuite segfault

[Andreas Beckmann]

On Thu, 24 Oct 2019 13:13:43 +0100 Iain Lane  wrote:
> Package: src:fftw3
> Version: 3.3.8-2

> We found this in an Ubuntu test rebuild, but I just confirmed on
> harris.d.o:

Is this reproducible in buster, too, or limited to sid/bullseye?

Andreas

Processed: tagging 943372, tagging 943410, tagging 943394

[Debian Bug Tracking System]

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

> tags 943372 + sid bullseye
Bug #943372 [scim] Can not active scim after Debian testing upgrade on 10 Oct 
2019
Added tag(s) bullseye and sid.
> tags 943410 + experimental
Bug #943410 [src:xapian-bindings] autopkg test calls python instead of python2
Added tag(s) experimental.
> tags 943394 + sid bullseye
Bug #943394 [src:libkeduvocdocument] libkeduvocdocument FTBFS: symbol errors
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package ibus

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package ibus
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #941018 (http://bugs.debian.org/941018)
> # Bug title: ibus: Regression from CVE-2019-14822 fix: does not work with qt5 
> applications
> #  * https://github.com/ibus/ibus/issues/2137
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 941018 + fixed-upstream
Bug #941018 [ibus] ibus: Regression from CVE-2019-14822 fix: does not work with 
qt5 applications
Added tag(s) fixed-upstream.
> usertags 941018 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 941018 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#942533: marked as done (sardana: needs a source-only upload.)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 18:41:22 +
with message-id 

and subject line 
has caused the Debian Bug report #942533,
regarding sardana: needs a source-only upload.
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.)


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

Package: sardana
Version: 3.0.0a+3.f4f89e+dfsg-1
Severity: serious

The release team have decreed that non-buildd binaries cannot migrate to 
testing. Please make a source-only upload so your package can migrate.
--- End Message ---
--- Begin Message ---
done--- End Message ---

Bug#941537: Merge request

[Adrian Heine]

I opened a merge request:
https://salsa.debian.org/debian/lilypond/merge_requests/1



signature.asc
Description: OpenPGP digital signature

Processed: py2removal blocks updates - 2019-10-24 18:36:20.581302+00:00

[Debian Bug Tracking System]

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # ldtp
> block 933025 by 936833
Bug #933025 [src:ldtp] ldtp: Porting to python3, or removing?
933025 was blocked by: 936833
933025 was blocking: 937388
Ignoring request to alter blocking bugs of bug #933025 to the same blocks 
previously set
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools: Python2 removal in sid/bullseye
936813 was blocked by: 939106 936812
936813 was blocking: 936371 936485 936757 936812 937448 937695 937703 938305 
939106 943104
Ignoring request to alter blocking bugs of bug #936813 to the same blocks 
previously set
> # pygobject
> block 937448 by 939112 942966
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 943093 936221 943103 938885 938596 943252 936900 943245 
936981 939109 936173 936619 936166 943300 942941 939104 942919 938583 938614 
937181 936813 938623 943117 938837 938327 936371 936748 943178 937688 936601 
937956 937422 936758 937114 937454 938665 942966 936841 942988 938084 939112 
938584 942956 926244 936632 938799 938511 936539 937339 936398 939115 938591 
938160 943023 938780 943294 938464 943110 936225 943230 938590 936624 935358 
938637 938604 936265 936670 943186 936721 936717 943076 937099 943146 938586 
936833 937419 943108 943129 883161 938361 936718 942904 936266 937388 938803 
938582 938593 938293 939114 943216 938329 942916 938789 939106 943123 93 
937628 936531 943151 937703 937457 937115 936995 938884 943291 937405 943270 
936789 937803 943131
937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 
942941 943104
Ignoring request to alter blocking bugs of bug #937448 to the same blocks 
previously set
> # python-distutils-extra
> block 937703 by 936641 937114 943270 936119
Bug #937703 [src:python-distutils-extra] python-distutils-extra: Python2 
removal in sid/bullseye
937703 was blocked by: 939107 937114 943270 937457 939111 939109 939106 939104 
939115 936641 936107 939105 936813 939114 939112 939113 936225 938885 849087 
936119 939103 939110 926244 938623 939108 938450
937703 was blocking: 937448 937695 937817 938168 943104
Ignoring request to alter blocking bugs of bug #937703 to the same blocks 
previously set
>
End of message, stopping processing here.

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

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Jonas Smedegaard]

[ sent again with ASCII-only headers to please Debian mail servers ]

Quoting Jérémy Lal (2019-10-24 19:47:48)
> Le jeu. 24 oct. 2019 à 19:33, Jonas Smedegaard  a écrit :
> 
> > Quoting Pirate Praveen (2019-10-24 19:12:22)
> > >
> > >
> > > On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard  wrote:
> > > > Quoting Pirate Praveen (2019-10-24 18:42:17)
> > > >>  On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard  > > >> > wrote:
> > > >>  > Quoting Pirate Praveen (2019-10-24 15:34:15)
> > > >>  >>  All files derived from source have their corresponding 
> > > >>  >>  source code and it is regenerated during build.
> > > >>  >
> > > >>  > It may very well be "source" but not "upstream source".
> > > >>  >
> > > >>
> > > >>  Then I fail to see how this is a serious bug.
> > > >
> > > > I listed Policy § 2.1 as being the reason for severity of this 
> > > > bug.
> > > >
> > > > Let me quote the part I find relevant:
> > > >
> > > >>  The program must include source code, and must allow 
> > > >>  distribution in source code as well as compiled form.
> > > >
> > > > If this package _does_ contain source code but just from a 
> > > > _different_ upstream project than the one currently listed in 
> > > > debian/copyright then the bug is easily fixed by simply 
> > > > correcting what upstream project this package claims to ship 
> > > > source code from.
> > >
> > > Lets ask the team what they think about the issue.
> > >
> > > Hi js-team,
> > >
> > > Do you think this is really an rc bug? Do you think Source field 
> > > in debian/copyright should be changed to 
> > > https://github.com/lodash/lodash/releases ?
> >
> > For the record, I did not say that above URL solves this bug.
> >
> 
> Does the problem Jonas refer to is that embedded component lodash-cli 
> is downloaded (by watch file) from 
> https://registry.npmjs.org/lodash-cli ?

This bugreport is generally about upstream source missing.

If upstream source really is multiple things e.g. due to embedded code, 
then sure embedding comes into the picture _too_ but to simplify the 
conversation here I choose to begin with looking at the _main_ source.

[snipped note relevant for embedding but not directly for this bug]

> Jérémy, trying to help.

Thanks for trying :-)

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Jérémy Lal]

Le jeu. 24 oct. 2019 à 19:33, Jonas Smedegaard  a écrit :

> Quoting Pirate Praveen (2019-10-24 19:12:22)
> >
> >
> > On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard  wrote:
> > > Quoting Pirate Praveen (2019-10-24 18:42:17)
> > >>  On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard  > >> > wrote:
> > >>  > Quoting Pirate Praveen (2019-10-24 15:34:15)
> > >>  >>  All files derived from source have their corresponding source
> > >>  >>  code and it is regenerated during build.
> > >>  >
> > >>  > It may very well be "source" but not "upstream source".
> > >>  >
> > >>
> > >>  Then I fail to see how this is a serious bug.
> > >
> > > I listed Policy § 2.1 as being the reason for severity of this bug.
> > >
> > > Let me quote the part I find relevant:
> > >
> > >>  The program must include source code, and must allow distribution
> > >>  in source code as well as compiled form.
> > >
> > > If this package _does_ contain source code but just from a
> > > _different_ upstream project than the one currently listed in
> > > debian/copyright then the bug is easily fixed by simply correcting
> > > what upstream project this package claims to ship source code from.
> >
> > Lets ask the team what they think about the issue.
> >
> > Hi js-team,
> >
> > Do you think this is really an rc bug? Do you think Source field in
> > debian/copyright should be changed to
> > https://github.com/lodash/lodash/releases ?
>
> For the record, I did not say that above URL solves this bug.
>

Does the problem Jonas refer to is that embedded component lodash-cli
is downloaded (by watch file) from https://registry.npmjs.org/lodash-cli ?

Side note: downloading from npmjs.org should be avoided and maybe a
good candidate for a lintian error; for it is an unreliable source
(no checksum, no guarantee, unlike git, afaik).

Jérémy, trying to help.

PS: Pirate, no need to cc pkg-javascript-devel we already receive all bug
reports.

Bug#943389: [Pkg-javascript-devel] Bug#943389: Bug#943389: node-lodash: source package does not contain upstream source

[Xavier]

Le 24 octobre 2019 19:12:22 GMT+02:00, Pirate Praveen 
 a écrit :
>
>
>On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard  wrote:
>> Quoting Pirate Praveen (2019-10-24 18:42:17)
>>>  On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard >> > wrote:
>>>  > Quoting Pirate Praveen (2019-10-24 15:34:15)
>>>  >>  All files derived from source have their corresponding source 
>>> code
>>>  >>  and it is regenerated during build.
>>>  >
>>>  > It may very well be "source" but not "upstream source".
>>>  >
>>> 
>>>  Then I fail to see how this is a serious bug.
>> 
>> I listed Policy § 2.1 as being the reason for severity of this bug.
>> 
>> Let me quote the part I find relevant:
>> 
>>>  The program must include source code, and must allow distribution
>in
>>>  source code as well as compiled form.
>> 
>> If this package _does_ contain source code but just from a
>_different_
>> upstream project than the one currently listed in debian/copyright 
>> then
>> the bug is easily fixed by simply correcting what upstream project 
>> this
>> package claims to ship source code from.
>
>Lets ask the team what they think about the issue.
>
>Hi js-team,
>
>Do you think this is really an rc bug? Do you think Source field in 
>debian/copyright should be changed to 
>https://github.com/lodash/lodash/releases ?
>
>Thanks
>Praveen


+1 minor/normal

Bug#934599: Pricing needed

[Jerry Wilson]

Good day,  Can you please provide me with quote for the below.
 7 HP 651A Magenta Original LaserJet Toner Cartridge, CE343A Original
Microsoft Surface Book 2 MFR #: HN6-1 x 9 
 Thank you
 Jerry Wilson
Director of Purchasing
Contemporary Plan
2741 W 21st St,
Erie, PA 16506
814 208 9313
www.contemporaryplan.com 

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Jonas Smedegaard]

Quoting Pirate Praveen (2019-10-24 19:12:22)
> 
> 
> On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard  wrote:
> > Quoting Pirate Praveen (2019-10-24 18:42:17)
> >>  On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard  >> > wrote:
> >>  > Quoting Pirate Praveen (2019-10-24 15:34:15)
> >>  >>  All files derived from source have their corresponding source 
> >>  >>  code and it is regenerated during build.
> >>  >
> >>  > It may very well be "source" but not "upstream source".
> >>  >
> >> 
> >>  Then I fail to see how this is a serious bug.
> > 
> > I listed Policy § 2.1 as being the reason for severity of this bug.
> > 
> > Let me quote the part I find relevant:
> > 
> >>  The program must include source code, and must allow distribution 
> >>  in source code as well as compiled form.
> > 
> > If this package _does_ contain source code but just from a 
> > _different_ upstream project than the one currently listed in 
> > debian/copyright then the bug is easily fixed by simply correcting 
> > what upstream project this package claims to ship source code from.
> 
> Lets ask the team what they think about the issue.
> 
> Hi js-team,
> 
> Do you think this is really an rc bug? Do you think Source field in 
> debian/copyright should be changed to 
> https://github.com/lodash/lodash/releases ?

For the record, I did not say that above URL solves this bug.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#943428: autopkg test calls python instead of python2

[Matthias Klose]

Package: src:pygobject
Version: 3.34.0-1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support. And it's probably too early 
to remove the python package.


http://launchpadlibrarian.net/448271617/pygobject_3.34.0-1ubuntu1_3.34.0-1ubuntu2.diff.gz

Bug#943427: autopkg test calls python instead of python2

[Matthias Klose]

Package: src:fast5
Version: 0.6.5-2
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support. And it's probably too early 
to remove the python package.


http://launchpadlibrarian.net/448270194/fast5_0.6.5-2build2_0.6.5-2ubuntu1.diff.gz

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Pirate Praveen]

On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard  wrote:

Quoting Pirate Praveen (2019-10-24 18:42:17)
 On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard > wrote:

 > Quoting Pirate Praveen (2019-10-24 15:34:15)
 >>  All files derived from source have their corresponding source 
code

 >>  and it is regenerated during build.
 >
 > It may very well be "source" but not "upstream source".
 >

 Then I fail to see how this is a serious bug.


I listed Policy § 2.1 as being the reason for severity of this bug.

Let me quote the part I find relevant:


 The program must include source code, and must allow distribution in
 source code as well as compiled form.


If this package _does_ contain source code but just from a _different_
upstream project than the one currently listed in debian/copyright 
then
the bug is easily fixed by simply correcting what upstream project 
this

package claims to ship source code from.


Lets ask the team what they think about the issue.

Hi js-team,

Do you think this is really an rc bug? Do you think Source field in 
debian/copyright should be changed to 
https://github.com/lodash/lodash/releases ?


Thanks
Praveen

Bug#943424: Plymouth prevents clean shutdown in some cases, which may result in data loss

[Алексей Шилин]

Package: plymouth
Version: 0.9.4-1.1
Severity: grave
Justification: may result in data loss

Hi,

I've noticed that when using offline-updates[1], remounting the root
filesystem read-only at shutdown fails with 'Device or resource busy'
(see the attached screenshot). As the result, the filesystem is left in
an unclean state, which may lead to data loss. Given that the installed
by default GNOME desktop environment currently provides no upgrade
method other than offline-updates, the impact is pretty wide.

It turned out that it is plymouth's fault. plymouthd runs early during
boot, typically from initrd. It runs with --mode=boot --attach-to-
session, so when the root filesystem is remounted read-write, it opens
/var/log/boot.log for writing and logs console messages there. When the
system is booting normally, this plymouthd instance is stopped either
by plymouth-quit.service in multi-user.target or by gdm.service which
stops plymouthd on its own. However, when performing offline-updates
the system doesn't boot any further than sysinit.target, so plymouthd
keeps running and logging to /var/log/boot.log. After all updates are
installed, a reboot is initiated, during which the running services are
stopped and remaining processes are killed. However, plymouthd uses a
trick to survive systemd's killing spree (see [2] or src/main.c:2240),
so it doesn't get killed, and by keeping /var/log/boot.log opened for
writing prevents remounting the root filesystem read-only.

I'm not sure how to best fix this issue. As a workaround, I added

ExecStartPre=-/bin/plymouth --wait quit

to plymouth-{halt,kexec,poweroff,reboot}.service-s (which run during
shutdown) to ensure that if plymouthd instance in --mode=boot is still
running, it is stopped before executing plymouthd in --mode=shutdown
(which doesn't do logging and therefor doesn't interfere with the
shutdown process). Aside from a small flicker during offline-updates
caused by reexecuting plymouthd, there should be no side effects. A
proposed patch is attached.

Another possible fix is to make plymouthd close the log file when its
mode changes to 'shutdown' by pk-offline-update. It makes sense and
seems trivial; however, it relies on the update service to switch
plymouth to that state, which doesn't look like a reliable solution in
the long term.

plymouthd can also be changed so that instead of just giving up if it
detects an already running instance, it will transfer its state
requested by command line options to that instance, so when, say,
plymouth-reboot.service runs plymouthd with --mode=shutdown, the
running instance actually switches to that mode and closes the log
file. Such change however, while looking like the most correct
solution, is likely not trivial, and is better be done by the upstream.

 [1] 
https://www.freedesktop.org/software/systemd/man/systemd.offline-updates.html
 [2] 
https://sources.debian.org/src/plymouth/0.9.4-1.1/src/main.c/#L2240
diff --git a/systemd-units/plymouth-halt.service.in b/systemd-units/plymouth-halt.service.in
index 38ae98c..ad7bafc 100644
--- a/systemd-units/plymouth-halt.service.in
+++ b/systemd-units/plymouth-halt.service.in
@@ -7,6 +7,8 @@ ConditionKernelCommandLine=!plymouth.enable=0
 ConditionVirtualization=!container
 
 [Service]
+# Terminate an already running plymouthd instance if there is one
+ExecStartPre=-@PLYMOUTH_CLIENT_DIR@/plymouth --wait quit
 ExecStart=@PLYMOUTH_DAEMON_DIR@/plymouthd --mode=shutdown --attach-to-session
 ExecStartPost=-@PLYMOUTH_CLIENT_DIR@/plymouth show-splash
 Type=forking
diff --git a/systemd-units/plymouth-kexec.service.in b/systemd-units/plymouth-kexec.service.in
index bed5eb7..df7b328 100644
--- a/systemd-units/plymouth-kexec.service.in
+++ b/systemd-units/plymouth-kexec.service.in
@@ -7,6 +7,8 @@ ConditionKernelCommandLine=!plymouth.enable=0
 ConditionVirtualization=!container
 
 [Service]
+# Terminate an already running plymouthd instance if there is one
+ExecStartPre=-@PLYMOUTH_CLIENT_DIR@/plymouth --wait quit
 ExecStart=@PLYMOUTH_DAEMON_DIR@/plymouthd --mode=shutdown --attach-to-session
 ExecStartPost=-@PLYMOUTH_CLIENT_DIR@/plymouth show-splash
 Type=forking
diff --git a/systemd-units/plymouth-poweroff.service.in b/systemd-units/plymouth-poweroff.service.in
index 7891e97..d4ebf28 100644
--- a/systemd-units/plymouth-poweroff.service.in
+++ b/systemd-units/plymouth-poweroff.service.in
@@ -7,6 +7,8 @@ ConditionKernelCommandLine=!plymouth.enable=0
 ConditionVirtualization=!container
 
 [Service]
+# Terminate an already running plymouthd instance if there is one
+ExecStartPre=-@PLYMOUTH_CLIENT_DIR@/plymouth --wait quit
 ExecStart=@PLYMOUTH_DAEMON_DIR@/plymouthd --mode=shutdown --attach-to-session
 ExecStartPost=-@PLYMOUTH_CLIENT_DIR@/plymouth show-splash
 Type=forking
diff --git a/systemd-units/plymouth-reboot.service.in b/systemd-units/plymouth-reboot.service.in
index 1d57789..f665740 100644
--- a/systemd-units/plymouth-reboot.service.in
+++ b/systemd-units/plymouth-reboot.service.in
@@ 

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Jonas Smedegaard]

Quoting Pirate Praveen (2019-10-24 18:42:17)
> On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard  wrote:
> > Quoting Pirate Praveen (2019-10-24 15:34:15)
> >>  All files derived from source have their corresponding source code 
> >>  and it is regenerated during build.
> > 
> > It may very well be "source" but not "upstream source".
> > 
> 
> Then I fail to see how this is a serious bug.

I listed Policy § 2.1 as being the reason for severity of this bug.

Let me quote the part I find relevant:

> The program must include source code, and must allow distribution in 
> source code as well as compiled form.

If this package _does_ contain source code but just from a _different_ 
upstream project than the one currently listed in debian/copyright then 
the bug is easily fixed by simply correcting what upstream project this 
package claims to ship source code from.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Pirate Praveen]

On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard  wrote:

Quoting Pirate Praveen (2019-10-24 15:34:15)
 On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard > wrote:

 > The source package src:node-lodash states in its debian/copyright
 > file that its upstream source is 
<>

 >

 I don't thik that is how DFSG is intrepreted. If that were the case,
 then we won't able to modify upstream tarball at all.


I am not surprised (but frustrated and sad) that you try to argue that
what is listed as upstream source need not be upstream source.



 You need to check with the release tarballs.
 


If upstream source is not  but 
instead
it is  then it is a(nother) bug 
that the

package points at the wrong place for its upstream source.



 We don't usually specify the releases page in debian/copyright only
 the project page. You can verify this against any other package in
 debian.


That's no bug if project page _also_ is upstream source, as is 
commonly

the case e.g. at Github.

It is a minor bug when project page clearly and unambiguously 
references

upstream source.

It is a severe bug when project page serves code which upstream use as
their prefered form for editing but the code distributed with Debian 
as

"upstream source" is *not* that same code but instead some other code,
regardless how clearly that other non-source code is referenced from
project page, and regardless if upstream labels that other code as 
their

"releases".



As far as I understood, the other code you mention here is the vendor 
directory. Please correct me if I'm mistaken. Or specify which specific 
files you have a problem with. Files in vendor directory usually have 
their own separate projects and version control systems.



This bug is about the code upstream treats as their source *not* being
what Debian distributes as upstream *source*.


 All files derived from source have their corresponding source code 
and

 it is regenerated during build.


It may very well be "source" but not "upstream source".



Then I fail to see how this is a serious bug. Serious bug is usually 
when the source package does not ship corresponding source code for the 
shipped binary. I don't think what you describe as a problem here can 
be considered serious.





 As for lodash-cli, it is included as another source tarball and you
 can see this in the dsc file.


This bug is *not* about embedded code, it is about the main code.


As far as I understand there is not a requirement to take a git 
snapshot. Can you tell which files you see as problematic? I can think 
of only vendor/* that was not seen in the git repo.

Processed: py2removal blocks updates - 2019-10-24 16:36:29.947841+00:00

[Debian Bug Tracking System]

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # ldtp
> block 933025 by 936833
Bug #933025 [src:ldtp] ldtp: Porting to python3, or removing?
933025 was blocked by: 936833
933025 was blocking: 937388
Ignoring request to alter blocking bugs of bug #933025 to the same blocks 
previously set
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools: Python2 removal in sid/bullseye
936813 was blocked by: 939106 936812
936813 was blocking: 936371 936485 936757 936812 937448 937695 937703 938305 
939106 943104
Ignoring request to alter blocking bugs of bug #936813 to the same blocks 
previously set
> # pygobject
> block 937448 by 939112 942966
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 943093 936221 943103 938885 938596 943252 936900 943245 
936981 939109 936173 936619 936166 943300 942941 939104 942919 938583 938614 
937181 936813 938623 943117 938837 938327 936371 936748 943178 937688 936601 
937956 937422 936758 937114 937454 938665 942966 936841 942988 938084 939112 
938584 942956 926244 936632 938799 938511 936539 937339 936398 939115 938591 
938160 943023 938780 943294 938464 943110 936225 943230 938590 936624 935358 
938637 938604 936265 936670 943186 936721 936717 943076 937099 943146 938586 
936833 937419 943108 943129 883161 938361 936718 942904 936266 937388 938803 
938582 938593 938293 939114 943216 938329 942916 938789 939106 943123 93 
937628 936531 943151 937703 937457 937115 936995 938884 943291 937405 943270 
936789 937803 943131
937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 
942941 943104
Ignoring request to alter blocking bugs of bug #937448 to the same blocks 
previously set
> # python-distutils-extra
> block 937703 by 936641 937114 943270 936119
Bug #937703 [src:python-distutils-extra] python-distutils-extra: Python2 
removal in sid/bullseye
937703 was blocked by: 939107 937114 943270 937457 939111 939109 939106 939104 
939115 936641 936107 939105 936813 939114 939112 939113 936225 938885 849087 
936119 939103 939110 926244 938623 939108 938450
937703 was blocking: 937448 937695 937817 938168 943104
Ignoring request to alter blocking bugs of bug #937703 to the same blocks 
previously set
>
End of message, stopping processing here.

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

Processed: Re: [Tts-project] Bug#943402: festival: calling festival --tts or text2wave aborts

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 festlex-ifd
Bug #943402 [festival] festival: calling festival --tts or text2wave aborts
Bug reassigned from package 'festival' to 'festlex-ifd'.
No longer marked as found in versions festival/1:2.5.0-4.
Ignoring request to alter fixed versions of bug #943402 to the same values 
previously set
> severity -1 grave
Bug #943402 [festlex-ifd] festival: calling festival --tts or text2wave aborts
Severity set to 'grave' from 'important'

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

Processed: block 938718 with 943409, block 943409 with 941722

[Debian Bug Tracking System]

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

> block 938718 with 943409
Bug #938718 [src:translate-toolkit] translate-toolkit: Python2 removal in 
sid/bullseye
938718 was blocked by: 938781
938718 was blocking: 936196 936289 936973 937410 937422 937558 937598 937695 
937700 937834 937875 937885 938022 938168 938251 938418 938484 938492 938528 
938578 938836
Added blocking bug(s) of 938718: 943409
> block 943409 with 941722
Bug #943409 [python3-cheroot] python3-cheroot: Missing dependency on 
python3-jaraco.functools
943409 was not blocked by any bugs.
943409 was blocking: 938718
Added blocking bug(s) of 943409: 941722
> thanks
Stopping processing here.

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

Bug#943412: the autopkg test calls python instead of python2

[Matthias Klose]

Package: src:pysvn
Version: 1.9.9-1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support. And it's probably too early 
to remove the python package.


patch at
http://launchpadlibrarian.net/448257614/pysvn_1.9.9-1build1_1.9.9-1ubuntu1.diff.gz

Bug#943357: marked as done (mypy, python3-mypy: Both ship /usr/bin/dmypy)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 15:22:09 +
with message-id 
and subject line Bug#943357: fixed in mypy 0.740-2
has caused the Debian Bug report #943357,
regarding mypy, python3-mypy: Both ship /usr/bin/dmypy
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.)


-- 
943357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mypy
Version: 0.730-1
Severity: serious
X-Debbugs-CC: michael.cru...@gmail.com

% LANG=C LC_ALL=C sudo apt install mypy python3-mypy
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  mypy-doc
The following NEW packages will be installed:
  mypy python3-mypy
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/5969 kB of archives.
After this operation, 28.6 MB of additional disk space will be used.
Selecting previously unselected package python3-mypy.
(Reading database ... 655302 files and directories currently installed.)
Preparing to unpack .../python3-mypy_0.740-1_amd64.deb ...
Unpacking python3-mypy (0.740-1) ...
Selecting previously unselected package mypy.
Preparing to unpack .../archives/mypy_0.740-1_all.deb ...
Unpacking mypy (0.740-1) ...
dpkg: error processing archive /var/cache/apt/archives/mypy_0.740-1_all.deb (-
-unpack):
 trying to overwrite '/usr/bin/dmypy', which is also in package python3-mypy
0.740-1
Errors were encountered while processing:
 /var/cache/apt/archives/mypy_0.740-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: mypy
Source-Version: 0.740-2

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated mypy 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, 24 Oct 2019 16:49:06 +0200
Source: mypy
Architecture: source
Version: 0.740-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 943357
Changes:
 mypy (0.740-2) unstable; urgency=medium
 .
   * Incorporate high quality hand written manual pages courtesy of
 Andrej Shadura 
   * Reduce optimization level during the build for the armel, alpha, m68k,
 powerpc, and sh4 archs
   * Added missing importlib-metadata build-dep for pytest on some archs where
 this isn't happening automatically: ppc64 riscv64 x32
   * /usr/bin/{mypy,dmypy,stubgen} was accidentally included in python3-mypy 
when
 build standalone. Fixed this and added a breaks & replaces on the older
 version. Closes: #943357
Checksums-Sha1:
 50fe7e1b6ebfebe31cd4c300864f980e38190439 2553 mypy_0.740-2.dsc
 b049026b986fdfc6c15b7260d7463375c1de7273 14196 mypy_0.740-2.debian.tar.xz
 ba85da9678e4b132a5cff92e3c273dca10a7 10301 mypy_0.740-2_source.buildinfo
Checksums-Sha256:
 99a4e67dc6d6da99121452d65c443007add761e3dae4c949491dc780375feb24 2553 
mypy_0.740-2.dsc
 2b7e52cb94e3bd604bab1cf4d832288be409445d7ab90f2d4e14afd4087f8ef9 14196 
mypy_0.740-2.debian.tar.xz
 d59106fb6a17e26f3ce2f932962d4406438930ff88d20ea8a27de3a024652188 10301 
mypy_0.740-2_source.buildinfo
Files:
 447ec23fdc013a74d241332245197b2f 2553 utils optional mypy_0.740-2.dsc
 b856c2b2a5d1f52f75b520dee84fccce 14196 utils optional 
mypy_0.740-2.debian.tar.xz
 042ca3f4ac2716df0f22d6faa376caad 10301 utils optional 
mypy_0.740-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl2xvBgACgkQPCZ2P2xn
5uK0jw//U91SJgrnem5wC4TMZGGrLYhYTwHKmzjd6C7PFyxYBMoLAaVtL/ao1ehv
XLVeSPUa9Ja8LkApHynvdVg7axohEm2l0hMGW/U5b++Id7UkytrsEFXtLekp6vR+
m1wf41OARctNeaiFYqa5T66wcrMNL/T9zh/Za31oaCg4JZhotIgv9yyxUm1Z/AZQ
1F2NNza5xvXY+K0kxJhdW6cobGpHWY2+316nkU/aVgURzSQwD6hG+I46SPO18IKh
MziJT4WXtzrTCq4MNn+h+a5Xx1dMZjfoEBUl9uSk/uTdZIVK/TaBGm03+z19hSeZ
lg260/SyoYm4CbUUYbJBzOxWniJ1cTW1JP00V9KjewAgBbUfIqqUFOIzEiCgICSX

Bug#943409: python3-cheroot: Missing dependency on python3-jaraco.functools

[Stuart Prescott]

Package: python3-cheroot
Version: 8.2.1+ds-1
Severity: serious
Justification: Policy 3.5 Packages must specify their dependencies

Dear Maintainer,

python3-cheroot appears to have grown a dependency on jaraco.functools;
python3-jaraco.functools versio 2.0-1 is in the NEW queue.

$ python3 -c "from cheroot.wsgi import Server"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/cheroot/wsgi.py", line 36, in 
from . import server
  File "/usr/lib/python3/dist-packages/cheroot/server.py", line 90, in 
from .workers import threadpool
  File "/usr/lib/python3/dist-packages/cheroot/workers/threadpool.py", line 15, 
in 
from jaraco.functools import pass_none
ModuleNotFoundError: No module named 'jaraco'

regards
Stuart

Bug#943410: autopkg test calls python instead of python2

[Matthias Klose]

Package: src:xapian-bindings
Version: 1.4.11-2
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support. And it's probably too early 
to remove the python package.


http://launchpadlibrarian.net/448258674/xapian-bindings_1.4.11-2build1_1.4.11-2ubuntu1.diff.gz

Bug#935300: marked as done (rsyslog: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 14:57:50 +
with message-id 
and subject line Bug#935300: fixed in rsyslog 8.1910.0-2
has caused the Debian Bug report #935300,
regarding rsyslog: FTBFS on s390x
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.)


-- 
935300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:rsyslog
version: 8.1908.0-1
severity: serious
tags: ftbfs

Hi,

The latest version of rsyslog in unstable fails on s390x:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: rsyslog
Source-Version: 8.1910.0-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated rsyslog 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: Thu, 24 Oct 2019 14:13:12 +0200
Source: rsyslog
Architecture: source
Version: 8.1910.0-2
Distribution: unstable
Urgency: medium
Maintainer: Michael Biebl 
Changed-By: Michael Biebl 
Closes: 935300
Changes:
 rsyslog (8.1910.0-2) unstable; urgency=medium
 .
   * Fix file handle leak in omfile (Closes: #935300)
Checksums-Sha1:
 c693426dfca609f270192dc66f4f6f7bde3beb3e 3060 rsyslog_8.1910.0-2.dsc
 23fee9e0f787686d718b1d7f3367ed4fcb6bcac8 31536 rsyslog_8.1910.0-2.debian.tar.xz
 58a6c6e9169b71e36646283e85f29a7306b83e47 9176 
rsyslog_8.1910.0-2_source.buildinfo
Checksums-Sha256:
 2887dde01d1dddf5ced29eedf819a93d6c29585d3209e74fd58c4cb18419e885 3060 
rsyslog_8.1910.0-2.dsc
 63da54929a0f468817bb97708eea7ccd191681e33aef7d3e5b9ea6fa3fcb4b11 31536 
rsyslog_8.1910.0-2.debian.tar.xz
 6413c0aaec3b7fad42b188937708ed0d798de8a1491b15aef493cbe441f71bb8 9176 
rsyslog_8.1910.0-2_source.buildinfo
Files:
 4a0daa79896b94f9efdcca2cd6bf0cc9 3060 admin important rsyslog_8.1910.0-2.dsc
 609b8ba049854a89df8efaa49884b674 31536 admin important 
rsyslog_8.1910.0-2.debian.tar.xz
 a29fdda8d0638ed4322db2b26d59203a 9176 admin important 
rsyslog_8.1910.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl2xrlgACgkQauHfDWCP
ItwAgw//Xj0MM5YcXu0R4g6erivGLRijo+vY8RhxSC6do7nkP15ML51HTacXzHtY
HkZEzmYVO98EBRehchWU7KZGS2LuD0QYTKVQg2fZBUYfQ2GtnnQ+lalnRC+REK4U
Fid4aK5NQDR9YZLPliRrkM85ijijHV+MDgMIJqMQFlQDUMh+YOaKrkWrDmg9FZYn
tXQQfJs8tWmnAFPeu21iGhCWEXXmVHURpijwIlOLEhFqsvhAMBiV0x790bFkFtlN
VOpiiMKTI2Mh3b1EaMMVpK+EAseYRFSGU5i7hHHJT89SfXXddG+kkPGpYH/rSMOq
Hf4lcNEIwhKarLu63ciaT3i/fNSSYHT0jBStvOok0LRSji1iBJT6/+BYPIa7gDQK
07DJgdBQsmChVXBIdRcwkK+u/eWwmM6F6SDBVHF1nwFsEspN+mE4YS1moT8S4L9I
swQOW7ll9VKuG4LhafF7VyR+5osEZA4nPC2EF2kSkBKQ9QoEVpr7jKHc2k1ncj/r
Knw0emqL+flqYrpmLmrnAXPB51GZbaZK7fYNbrEEKFWb6i4prz+D341hmeQYZpAf
aSPTn7NW83Cuk5w3Zc7i1QtKzY/HNggI3m4x0G3pQzddEZ2gzonGzXYSthdG94+G
1BCMbMbr9fEAzwuIHBcVwoyjbFJ9YHLtCUedRvDWIA5OJt63kO0=
=2i4Y
-END PGP SIGNATURE End Message ---

Bug#927481: marked as done (.help fails with "Sorry! Something went wrong.")

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 14:58:14 +
with message-id 
and subject line Bug#927481: fixed in sopel 6.6.9-1
has caused the Debian Bug report #927481,
regarding .help fails with "Sorry! Something went wrong."
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.)


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

Sopel, in stable and testing right now, cannot provide a "help" to its
users. It makes it really hard to use (hence the "grave" severity). I'm
also marking this as grave because upstream keeps on churning out
"patch" releases (according to semver) that are really "minor" releases
(according to semver again), so they are not suitable for stable
updates. For example right now there is 6.6.4 release that fixes this
bug:

https://sopel.chat/changelog/6.6.4/

... but it also includes changes like:

 * Cleaned up code in instagram and unicode modules
 * Core modules now use bot.channels instead of deprecated bot.privileges

Which couldn't be eligible for a stable update.

Because I do not want to maintain a fork of 6.6.3 the way I will
probably have to do with 6.5.0 in stretch (argh), i think it's better to
remove sopel from buster and maintain it from backports in the future
(if at all).

-- System Information:
Debian Release: 9.8
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages sopel depends on:
ii  adduser3.115
ii  lsb-base   9.20161125
ii  python33.5.3-1
ii  python3-geoip2 2.4.2+dfsg1-1
ii  python3-praw   3.3.0-1
ii  python3-requests   2.12.4-1
ii  python3-tz 2016.7-0.3
ii  python3-xmltodict  0.10.2-1

Versions of packages sopel recommends:
ii  ipython35.1.0-3
ii  python3-enchant 1.6.7-1
ii  python3-feedparser  5.1.3-3
ii  python3-lxml3.7.1-1

sopel suggests no packages.

-- Configuration Files:
/etc/sopel.cfg changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sopel
Source-Version: 6.6.9-1

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated sopel 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: Thu, 24 Oct 2019 09:52:59 -0400
Source: sopel
Architecture: source
Version: 6.6.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Antoine Beaupré 
Closes: 927481
Changes:
 sopel (6.6.9-1) unstable; urgency=medium
 .
   * orphan package:
 .
 I do not use Sopel anymore and therefore can't serve as a good
 maintainer. I also couldn't find a good reason to use this instead of
 more established codebase like Limnoria, which are seeing way more
 development and third-party packages.
 .
 Limnoria is also well-maintained in Debian, so I am not sure sopel is
 worth inclusion in Debian in the first place anymore.
   * new upstream release (Closes: #927481)
Checksums-Sha1:
 7034688b75f507e02a60d31a7ce7b10ca56b9247 1508 sopel_6.6.9-1.dsc
 e0e67304bb3a02d4c1da753ff16a89a016bab19e 175820 sopel_6.6.9.orig.tar.gz
 3ef5e7374808ba33af4e965ef9574e7ef752fbbd 7712 sopel_6.6.9-1.debian.tar.xz
 cc8fcd829f4e6087e34dd0a4f4fff9353da1b300 5979 sopel_6.6.9-1_amd64.buildinfo
Checksums-Sha256:
 ea6b1073b758e1541d3ed8f86eebebd8f9e0af3e17057763d31d1c3dd12c643e 1508 
sopel_6.6.9-1.dsc
 c9d1c7a1c1b25b6236dd47dc5f3160344ca89b0832715c4ab7a55c25ada3c807 175820 
sopel_6.6.9.orig.tar.gz
 b0c156c2fa66480d0343965c123647686107889907b217ce64687393ab3c378d 7712 
sopel_6.6.9-1.debian.tar.xz
 f07de18383add1f5a41a60dd89f24f3eebfefb2c51cb5b365b00c0e1434fab8a 5979 

Processed: py2removal blocks updates - 2019-10-24 14:36:17.169303+00:00

[Debian Bug Tracking System]

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # ldtp
> block 933025 by 936833
Bug #933025 [src:ldtp] ldtp: Porting to python3, or removing?
933025 was blocked by: 936833
933025 was blocking: 937388
Ignoring request to alter blocking bugs of bug #933025 to the same blocks 
previously set
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools: Python2 removal in sid/bullseye
936813 was blocked by: 936812
936813 was blocking: 936371 936485 936757 936812 937448 937695 937703 938305 
939106 943104
Added blocking bug(s) of 936813: 939106
> # markupsafe
> block 936994 by 938011
Bug #936994 [src:markupsafe] markupsafe: Python2 removal in sid/bullseye
936994 was blocked by: 936765 938015 942938 936985
936994 was blocking: 937695 938168
Added blocking bug(s) of 936994: 938011
> # pygobject
> block 937448 by 939112 942966
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 943093 936221 943103 938885 938596 943252 936900 943245 
936981 939109 936173 936619 936166 943300 942941 939104 942919 938583 938614 
937181 936813 938623 943117 938837 938327 936371 936748 943178 937688 936601 
937956 937422 936758 937114 937454 938665 942966 936841 942988 938084 939112 
938584 942956 926244 936632 938799 938511 936539 937339 936398 939115 938591 
938160 943023 938780 943294 938464 943110 936225 943230 938590 936624 935358 
938637 938604 936265 936670 943186 936721 936717 943076 937099 943146 938586 
936833 937419 943108 943129 883161 938361 936718 942904 936266 937388 938803 
938582 938593 938293 939114 943216 938329 942916 938789 939106 943123 93 
937628 936531 943151 937703 937457 937115 936995 938884 943291 937405 943270 
936789 937803 943131
937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 
942941 943104
Ignoring request to alter blocking bugs of bug #937448 to the same blocks 
previously set
> # python-coverage
> block 937665 by 938011
Bug #937665 [src:python-coverage] python-coverage: Python2 removal in 
sid/bullseye
937665 was blocked by: 937157 943014 937232 936585 936120 938102 938408 936560 
937159 938278 937718 937725 936335 938244 936340 937580 937666 939481 937156 
937609 936473 937823 938676 938407 937989 936745 937516 938009 938300
937665 was blocking: 937695 938168
Added blocking bug(s) of 937665: 938011
> # python-defaults
> block 937695 by 938011
Bug #937695 [src:python-defaults] python-defaults: Python2 removal in 
sid/bullseye
937695 was blocked by: 938887 938260 938736 938924 937679 943243 938885 938713 
937711 936321 936926 937209 936227 938464 938409 936132 937264 936225 937160 
936577 937548 943068 936938 936166 939478 937085 943141 938762 938164 937087 
943156 936669 943116 938276 938729 937896 943133 937476 936890 938108 938385 
936939 936274 938483 936821 943069 937549 943004 936242 938408 937176 937565 
937181 936524 943045 936170 943047 937751 936740 938753 936645 943231 937678 
938183 938096 939179 936593 937819 936887 936924 936736 937266 936885 937730 
937323 938390 938734 936464 937635 937425 938227 938502 936993 937427 942988 
938166 943182 938432 936539 938622 936762 936728 937125 938058 937318 936164 
937232 938019 936276 938669 938059 936729 936977 938470 938604 937823 938890 
943006 936975 936538 937270 937894 937600 943114 936483 942989 937474 936606 
943210 938094 937021 937090 936526 938645 936753 937174 942992 943198 936183 
938647 936902 938593 937337 937231 936214 936806 938797 937694 936557 937588 
937800 936761 938431 938621 938795 937433 943176 938690 938216 938233 937047 
943208 937069 938131 938847 938501 937618 936298 937004 938845 938322 883194 
939641 937116 936110 937503 937771 936901 936150 937141 937837 937156 942991 
937835 937300 937022 936685 936299 937619 935450 937658 936687 937068 937592 
938369 938241 938347 937441 936450 938256 938345 938443 937243 936282 938555 
943090 936797 938557 937414 943142 937198 936804 936216 936690 937379 936917 
938410 937989 943021 936869 936915 937696 937210 937498 936501 936847 937114 
936845 937712 937006 938306 938150 943232 938780 943125 938685 936304 938299 
937784 937182 937499 937903 936241 937250 936955 936868 937378 938450 936957 
936345 937454 938517 936443 937482 938515 943266 938718 937007 938759 937005 
938844 936612 938189 938492 936599 943012 938192 937697 936933 937910 938489 
934852 936215 937334 936311 936916 938040 938794 936217 937044 936663 938330 
938556 937072 942970 938807 936796 938541 883173 943138 938372 938516 943265 
937030 942932 937288 936956 938488 936941 937950 936514 937101 943052 938671 
937203 938686 937834 936652 938188 938305 938830 937673 943126 942966 938719 
938307 938758 936718 937328 937115 936872 938029 936759 937117 936844 936189 
938612 849087 936998 943102 883161 938846 938554 936489 938582 937417 938311 
942983 937051 936794 

Processed: upstream bug reference

[Debian Bug Tracking System]

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

> forwarded 943396 https://github.com/FFTW/fftw3/issues/182
Bug #943396 [src:fftw3] FTBFS on armhf: testsuite segfault
Set Bug forwarded-to-address to 'https://github.com/FFTW/fftw3/issues/182'.
> thanks
Stopping processing here.

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

Bug#935300: marked as pending in rsyslog

[Michael Biebl]

Control: tag -1 pending

Hello,

Bug #935300 in rsyslog 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/rsyslog/commit/67a5f0ed7f80ff1eddc03a2d6c2ffdd56346d9a9


Fix file handle leak in omfile

Closes: #935300


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935300

Processed: Bug#935300 marked as pending in rsyslog

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935300 [src:rsyslog] rsyslog: FTBFS on s390x
Added tag(s) pending.

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

Bug#943396: FTBFS on armhf: testsuite segfault

[Sebastien Bacher]

The bug also has been reported upstream on
https://github.com/FFTW/fftw3/issues/182 which includes a valgrind log.
Getting a backtrace is a bit tricky since the test hangs under gdb...

Cheers,

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Jonas Smedegaard]

Quoting Pirate Praveen (2019-10-24 15:34:15)
> On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard  wrote:
> > The source package src:node-lodash states in its debian/copyright 
> > file that its upstream source is 
> > 
> 
> I don't thik that is how DFSG is intrepreted. If that were the case, 
> then we won't able to modify upstream tarball at all.

I am not surprised (but frustrated and sad) that you try to argue that 
what is listed as upstream source need not be upstream source.


> You need to check with the release tarballs.
> https://github.com/lodash/lodash/releases

If upstream source is not https://github.com/lodash/lodash but instead 
it is https://github.com/lodash/lodash then it is a(nother) bug that the 
package points at the wrong place for its upstream source.


> We don't usually specify the releases page in debian/copyright only 
> the project page. You can verify this against any other package in 
> debian.

That's no bug if project page _also_ is upstream source, as is commonly 
the case e.g. at Github.

It is a minor bug when project page clearly and unambiguously references 
upstream source.

It is a severe bug when project page serves code which upstream use as 
their prefered form for editing but the code distributed with Debian as 
"upstream source" is *not* that same code but instead some other code, 
regardless how clearly that other non-source code is referenced from 
project page, and regardless if upstream labels that other code as their 
"releases".

This bug is about the code upstream treats as their source *not* being 
what Debian distributes as upstream *source*.


> All files derived from source have their corresponding source code and 
> it is regenerated during build.

It may very well be "source" but not "upstream source".


> As for lodash-cli, it is included as another source tarball and you 
> can see this in the dsc file.

This bug is *not* about embedded code, it is about the main code.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: severity of 943402 is important

[Debian Bug Tracking System]

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

> severity 943402 important
Bug #943402 [festival] festival: calling festival --tts or text2wave aborts
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#943402: [Tts-project] Bug#943402: festival: calling festival --tts or text2wave aborts

[Samuel Thibault]

Control: severity important
Control: tags -1 unreproducible moreinfo

Hello,

fulvio ciriaco, le jeu. 24 oct. 2019 15:38:11 +0200, a ecrit:
> calling festival --tts
> or 
> festival
> (SayText "test")
> only gives an error:
> SIOD ERROR: wrong type of argument to get_c_utt 
> the same happens if one calls text2wave.

I am not getting this issue. Which festival voice are you using?
Notably, what list does "dpkg -l \*fest\*" return? Do you have any
festival personal configuration, e.g. in /etc/festival.scm or
~/.festivalrc ?

Samuel

Processed (with 1 error): Re: [Tts-project] Bug#943402: festival: calling festival --tts or text2wave aborts

[Debian Bug Tracking System]

Processing control commands:

> severity important
Unknown command or malformed arguments to command.

> tags -1 unreproducible moreinfo
Bug #943402 [festival] festival: calling festival --tts or text2wave aborts
Added tag(s) unreproducible and moreinfo.

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

Bug#943405: unsuitable for release: no upstream patch releases

[Antoine Beaupre]

Package: sopel
Version: 6.6.2-1
Severity: serious
Tags: upstream

In bug #927481, I was bit by a bug that wasn't solved upstream in a
simple patch release. It would force me to maintain a fork of the
project for every supported debian release to fix any bug, because
upstream doesn't follow the semver.org convention of using "patch"
releases for critical bugfixes and security issues.

Instead, Sopel upstream releases x.y.z release with major changes in
"z" patch releases. An example from #927481 is:

> For example right now there is 6.6.4 release that fixes this bug:
> 
> https://sopel.chat/changelog/6.6.4/
> 
> ... but it also includes changes like:
> 
>  * Cleaned up code in instagram and unicode modules
>  * Core modules now use bot.channels instead of deprecated bot.privileges
> 
> Which couldn't be eligible for a stable update.

So I even though the original bug was fixed in the latest upload, I
don't think sopel should be shipped with bullseye until this situation
changes, especially since the package is orphaned.

Next step in this bug would be to open the discussion with upstream
about this, maybe this is something they could work on.

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

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

Versions of packages sopel depends on:
ii  adduser3.118
ii  lsb-base   10.2019051400
ii  python33.7.3-1
ii  python3-dnspython  1.16.0-1
pn  python3-geoip2 
pn  python3-praw   
ii  python3-requests   2.21.0-1
ii  python3-tz 2019.1-1
ii  python3-xmltodict  0.11.0-2

Versions of packages sopel recommends:
ii  ipython35.8.0-1
ii  python3-enchant 2.0.0-1
ii  python3-feedparser  5.2.1-1
ii  python3-lxml4.3.2-1

sopel suggests no packages.

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Pirate Praveen]

On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard  wrote:

Package: node-lodash
Version: 4.17.15+dfsg-1
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The source package src:node-lodash states in its debian/copyright file
that its upstream source is 


What I found relevant here is
If running dpkg-source -x on a source package doesn’t produce the 
source of the package, ready for editing, and allow one to make changes 
and run dpkg-buildpackage to produce a modified package without taking 
any additional steps, creating a debian/README.source documentation 
file is recommended.


https://www.debian.org/doc/debian-policy/ch-source.html#source-package-handling-debian-readme-source

I don't think even this requirement is not applicable here, as apt 
source does the required things and uscan does the right thing when 
updating to new upstream release.

Bug#943402: festival: calling festival --tts or text2wave aborts

[fulvio ciriaco]

Package: festival
Version: 1:2.5.0-4
Severity: grave
Justification: renders package unusable

calling festival --tts
or 
festival
(SayText "test")
only gives an error:
SIOD ERROR: wrong type of argument to get_c_utt 
the same happens if one calls text2wave.
Thanks
Fulvio


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

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

Versions of packages festival depends on:
ii  adduser3.118
ii  alsa-utils 1.1.8-2
ii  libc6  2.29-2
ii  libestools2.5  1:2.5.0-6
ii  libgcc11:9.2.1-8
ii  libgomp1   9.2.1-8
ii  libstdc++6 9.2.1-8
ii  lsb-base   11.1.0
ii  sgml-base  1.29.1

Versions of packages festival recommends:
ii  festvox-italp16k [festival-voice]  2.0+debian0-4
ii  festvox-itapc16k [festival-voice]  2.0+debian0-4

Versions of packages festival suggests:
pn  festival-freebsoft-utils  
pn  pidgin-festival   

-- no debconf information

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[Pirate Praveen]

On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard  wrote:

Package: node-lodash
Version: 4.17.15+dfsg-1
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The source package src:node-lodash states in its debian/copyright file
that its upstream source is 



I don't thik that is how DFSG is intrepreted. If that were the case, 
then we won't able to modify upstream tarball at all.



$ apt source node-lodash
$ cd node-lodash-4.17.15+dfsg
$ tree -ad -I .pc
.
├── debian
│   ├── source
│   ├── tests
│   └── upstream
├── dist
├── doc
├── fp
├── .github
├── lib
│   ├── common
│   ├── fp
│   │   └── template
│   │   ├── doc
│   │   └── modules
│   └── main
├── lodash-cli
│   ├── bin
│   ├── lib
│   └── template
├── perf
│   └── asset
├── test
│   └── asset
└── vendor
├── backbone
│   └── test
│   └── setup
├── firebug-lite
│   ├── skin
│   │   └── xp
│   └── src
├── json-js
└── underscore
└── test

34 directories

$ git clone 
$ cd lodash
$ tree -ad -I '.git*'
.
├── .internal
└── test

2 directories


The tarball distributed as the "source" for the Debian packaging 
clearly
is *not* what upstream considers its source nor is it what is stated 
in

debian/copyright was used as source.



You need to check with the release tarballs.
https://github.com/lodash/lodash/releases We don't usually specify the 
releases page in debian/copyright only the project page. You can verify 
this against any other package in debian.


All files derived from source have their corresponding source code and 
it is regenerated during build.


As for lodash-cli, it is included as another source tarball and you can 
see this in the dsc file.


For example you can see 
https://packages.debian.org/source/unstable/node-lodash lists


FileSize (in kB)MD5 checksum
node-lodash_4.17.15+dfsg-1.dsc  2.5 kB  7fe2561d015989f65c5fbb62363f796c
node-lodash_4.17.15+dfsg.orig-lodash-cli.tar.xz 	40.6 kB 
	b2217589333a9b2e1dd198bdfa1f3948
node-lodash_4.17.15+dfsg.orig.tar.xz 	586.6 kB 
	fedbf4804767031ddc8d34f43bc37dbe
node-lodash_4.17.15+dfsg-1.debian.tar.xz 	5.3 kB 
	4221804f94c6e7a19c62352d6045d1c7


If you are concerned about lack of a canonical place to document the 
embedded modules, then please be clear about it.


Can you be more specific which files do you think violate DFSG and be 
specific which section. I assume you meant section 2,


Source Code
   The program must include source code, and must allow distribution 
in source code as well as compiled form.


So you need to tell which files you think are not following this 
requirement.


Are you concerned about files in vendor directory?

If I remove vendor directory from upstream tarball would your concern 
be addressed?



 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl2xcaUACgkQLHwxRsGg
ASGnLg/+Lsiq8c+vzd/2x9lXH7SwucK3bNiYl8X5QJYpC3Wuh72jEOHjl1gWl5MZ
uYBnR9G8h3UQNm0Tn2lgUAudhtV7af3mYJkKxBA6FMfYGEwPvig+8SoX0i0C3sjE
+fU01KFebmRsxJ+Of278titobzfgX2MJzWVQtzN5VbIvfAfuaQ4hjun0NCyPdbeM
2GKH5vnfs9Woi6P6ZmixlCvyT3B6bwl71q+x7RCNtAa5NhB8GrBMBG07jehrpCvK
gmhYNDnQeFYVQLObS8M5r/bLvT/9K7EuaPZxyhAg73c2bMOxcElwVC/IuZA832IL
woRqco6pJVYhLZ59sngrtqP9f/dkUF8IJkkFHCiDSfkcyFv37Vr0tJYSur1q+bWB
2viX9k2Nh4xbQ/P9RrWBhAcjrLRqTh3KD94kIJ6iVVhYxcwqVY/E31p2lwBLZZVx
jAGmdb4fYF+3Qgkmv0Hn67rWMEz8cWW0QZocIRMD/PmJJNgOUuTBV8asdF3wLo87
FfLJeeL6B6+taXJKK7lGgPv6cOkgjWamFNh7c4K1xsMWC2jmbQ6nSv23NJh8AwqQ
fNvKe2wXYqK0vedy4Z1QwXYXhA2yTGY4FmMvo+nXSuJ8Cp7/hbt0xy/g6N84cybX
v2SA5RhlSN8Y7xBvrK1DW1U+bATi6zTiIUSrnElg1tkj1JkcaTs=
=kSoi
-END PGP SIGNATURE-
--
Pkg-javascript-devel mailing list
pkg-javascript-de...@alioth-lists.debian.net 

Bug#943396: FTBFS on armhf: testsuite segfault

[Iain Lane]

Package: src:fftw3
Version: 3.3.8-2
Severity: serious
Tags: patch

Hiya,

We found this in an Ubuntu test rebuild, but I just confirmed on
harris.d.o:

> perl -w ./check.pl -r --estimate -c=5 -v `pwd`/bench
> Executing "/home/laney/fftw3-3.3.8/tests/bench -o estimate --verbose=1   
> --verify '//obrd7560' --verify '//ibrd7560' --verify '//ofrd7560' --verify 
> '//ifrd7560' --verify 'obrd7560' --verify 'ibrd7560' --verify 'ofrd7560' 
> --verify 'ifrd7560' --verify '//obcd7560' --verify '//ibcd7560' --verify 
> '//ofcd7560' --verify '//ifcd7560' --verify 'obcd7560' --verify 'ibcd7560' 
> --verify 'ofcd7560' --verify 'ifcd7560' --verify 'okd5e00*18' --verify 
> 'ikd5e00*18' --verify 'obrd8x3x7v7' --verify 'ibrd8x3x7v7' --verify 
> 'ofrd8x3x7v7' --verify 'ifrd8x3x7v7' --verify '//obcd8x3x7v7' --verify 
> '//ibcd8x3x7v7' --verify '//ofcd8x3x7v7' --verify '//ifcd8x3x7v7' --verify 
> 'obcd8x3x7v7' --verify 'ibcd8x3x7v7' --verify 'ofcd8x3x7v7' --verify 
> 'ifcd8x3x7v7' --verify 'okd17472o00' --verify 'ikd17472o00' --verify 
> 'obr5x8x10x14v6' --verify 'ibr5x8x10x14v6' --verify 'ofr5x8x10x14v6' --verify 
> 'ifr5x8x10x14v6' --verify '//obc5x8x10x14v6' --verify '//ibc5x8x10x14v6' 
> --verify '//ofc5x8x10x14v6' --verify '//ifc5x8x10x14v6' --verify 
> 'obc5x8x10x14v6' --verify 'ibc5x8x10x14v6' --verify 'ofc5x8x10x14v6' --verify 
> 'ifc5x8x10x14v6'"
> //obrd7560 2.36623e-07 7.01972e-07 2.57654e-07
> //ibrd7560 2.70078e-07 7.01972e-07 2.48174e-07
> //ofrd7560 2.32727e-07 7.01972e-07 2.3547e-07
> Segmentation fault

I can try to get a backtrace if you want, or feel free to grab the build
from harris:~laney/fftw3-3.3.8 and poke at it. Daniel Van Vugt from the
Ubuntu team investigated this a little bit and found that disabling Neon
works around this problem. See the MR:

  https://salsa.debian.org/science-team/fftw3/merge_requests/1

Would appreciate your thoughts.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

Bug#940540: marked as done (codelite: Uninstallable due to conflicting dependencies)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 11:49:18 +
with message-id 
and subject line Bug#940540: fixed in codelite 13.0+dfsg-1
has caused the Debian Bug report #940540,
regarding codelite: Uninstallable due to conflicting dependencies
to be marked as done.

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

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


-- 
940540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codelite
Version: 12.0+dfsg-1
Severity: grave
Justification: renders package unusable

Attempting to install codelite fails for me using current unstable:

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

The following packages have unmet dependencies:
 codelite : Depends: libwxsqlite3-3.0-0 but it is not going to be
 installed
 E: Unable to correct problems, you have held broken packages.

This situation is also currently being reported by DOSE, so doesn't
appear to be specific to my machine:

https://qa.debian.org/dose/debcheck/unstable_main/latest/packages/codelite.html#40d19c199f7ed5a33995d52151783c11

Pasting that output here for posterity:

| Package: codelite
| Scenario: unstable_main
| Date: 2019-09-16 05:00:03
| 
| Architectures: amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, 
s390x
| 
| Summary: conflict between libwxsqlite3-3.0-0 and codelite
| 
| codelite (12.0+dfsg-1) [PTS] [ctrl]
|↓ libwxsqlite3-3.0-0
|   
| libwxsqlite3-3.0-0 (3.4.1~dfsg-4) [PTS] [ctrl]
|   codelite (12.0+dfsg-1) [PTS] [ctrl]
| CONFLICT

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Source: codelite
Source-Version: 13.0+dfsg-1

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

Debian distribution maintenance software
pp.
David Hart  (supplier of updated codelite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Oct 2019 10:10:27 +0100
Source: codelite
Binary: codelite codelite-plugins
Architecture: source
Version: 13.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: David Hart 
Description:
 codelite   - Powerful and lightweight IDE
 codelite-plugins - Powerful and lightweight IDE - plugins
Closes: 934096 940540
Changes:
 codelite (13.0+dfsg-1) unstable; urgency=medium
 .
   * QA upload.
 .
   * New upstream release:
 - Add new and missing plugins to codelite-plugins.
 - Refresh patches.
 - Patch out two non-free licenced svgs.
 .
   * debian/control:
 - Build against the GTK+3 version of wxWidgets (Closes: #934096, #940540).
 - Bump standards to 4.4.1 and remove debian/compat.
 - Add an upstream metadata file.
Checksums-Sha1:
 8144dd039678198e03e754508308fd6b1da46e9e 2380 codelite_13.0+dfsg-1.dsc
 ebc78eb9b6bb1bd09366e51c973663b571fe4f06 19298604 
codelite_13.0+dfsg.orig.tar.xz
 abb94d2be163e01848500a0b2db584cfcbfad430 26324 
codelite_13.0+dfsg-1.debian.tar.xz
 4091f3932ec16e3a1ec535f8a5c5688bcdabbb0b 17389 
codelite_13.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 80a7c7303be83c2bd4ec4f1fac73e576bff22a650ac2a152ef0a83cdc09b5989 2380 
codelite_13.0+dfsg-1.dsc
 753289a9e3f2624e7f023adc0248fea130703e9484d40b1e2a10aac621de746b 19298604 
codelite_13.0+dfsg.orig.tar.xz
 9a5a07488fa5814bb71ed55d5893e60a24a7fe05b347068cb6b1c5ec00f7f8f5 26324 
codelite_13.0+dfsg-1.debian.tar.xz
 87d55334620f4031c01ed9beb845c314e58e537e06e3eb30818e5a0d1a69ae84 17389 
codelite_13.0+dfsg-1_source.buildinfo
Files:
 830320d15552d09f199fc5a66edc9b69 2380 devel optional codelite_13.0+dfsg-1.dsc
 f2eb6eb344f08cd675406d1036e7917b 19298604 devel optional 
codelite_13.0+dfsg.orig.tar.xz
 b7ab4b139e211c3bed4516281a99c3d7 26324 devel optional 
codelite_13.0+dfsg-1.debian.tar.xz
 

Bug#934096: marked as done (codelite: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 11:49:18 +
with message-id 
and subject line Bug#934096: fixed in codelite 13.0+dfsg-1
has caused the Debian Bug report #934096,
regarding codelite: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Source: codelite
Source-Version: 13.0+dfsg-1

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

Debian distribution maintenance software
pp.
David Hart  (supplier of updated codelite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Oct 2019 10:10:27 +0100
Source: codelite
Binary: codelite codelite-plugins
Architecture: source
Version: 13.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: David Hart 
Description:
 codelite   - Powerful and lightweight IDE
 codelite-plugins - Powerful and lightweight IDE - plugins
Closes: 934096 940540
Changes:
 codelite (13.0+dfsg-1) unstable; urgency=medium
 .
   * QA upload.
 .
   * New upstream release:
 - Add new and missing plugins to codelite-plugins.
 - Refresh patches.
 - Patch out two non-free licenced svgs.
 .
   * debian/control:
 - Build against the GTK+3 version of wxWidgets (Closes: #934096, #940540).
 - Bump standards to 4.4.1 and remove debian/compat.
 - Add an upstream metadata file.
Checksums-Sha1:
 8144dd039678198e03e754508308fd6b1da46e9e 2380 codelite_13.0+dfsg-1.dsc
 ebc78eb9b6bb1bd09366e51c973663b571fe4f06 19298604 
codelite_13.0+dfsg.orig.tar.xz
 abb94d2be163e01848500a0b2db584cfcbfad430 26324 
codelite_13.0+dfsg-1.debian.tar.xz
 4091f3932ec16e3a1ec535f8a5c5688bcdabbb0b 17389 
codelite_13.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 80a7c7303be83c2bd4ec4f1fac73e576bff22a650ac2a152ef0a83cdc09b5989 2380 
codelite_13.0+dfsg-1.dsc
 753289a9e3f2624e7f023adc0248fea130703e9484d40b1e2a10aac621de746b 19298604 
codelite_13.0+dfsg.orig.tar.xz
 9a5a07488fa5814bb71ed55d5893e60a24a7fe05b347068cb6b1c5ec00f7f8f5 26324 
codelite_13.0+dfsg-1.debian.tar.xz
 87d55334620f4031c01ed9beb845c314e58e537e06e3eb30818e5a0d1a69ae84 17389 
codelite_13.0+dfsg-1_source.buildinfo
Files:
 830320d15552d09f199fc5a66edc9b69 2380 devel optional codelite_13.0+dfsg-1.dsc
 f2eb6eb344f08cd675406d1036e7917b 19298604 devel optional 
codelite_13.0+dfsg.orig.tar.xz
 b7ab4b139e211c3bed4516281a99c3d7 26324 devel optional 
codelite_13.0+dfsg-1.debian.tar.xz
 ff95efa7bfc8b8938809f780e24dff3e 17389 devel optional 
codelite_13.0+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#943394: libkeduvocdocument FTBFS: symbol errors

[Helmut Grohne]

Source: libkeduvocdocument
Version: 4:17.08.3-1
Severity: serious
Tags: ftbfs

libkeduvocdocument fails to build from source in unstable when using
sbuild natively on amd64. A log ends with:

| dh_makeshlibs '-Xusr/lib/libkdeinit5_*'
| dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
| dpkg-gensymbols: warning: debian/libkeduvocdocument5/DEBIAN/symbols doesn't 
match completely debian/libkeduvocdocument5.symbols
| --- debian/libkeduvocdocument5.symbols (libkeduvocdocument5_4:17.08.3-1_amd64)
| +++ dpkg-gensymbolsBsVKoI   2019-10-24 10:41:15.691855166 +
| @@ -339,21 +339,21 @@
|   
_ZNK22KEduVocPersonalPronoun15personalPronounE6QFlagsIN15KEduVocWordFlag5FlagsEE@Base
 14.11.95
|   _ZNK22KEduVocPersonalPronoun19maleFemaleDifferentEv@Base 14.11.95
|   _ZNK22KEduVocPersonalPronouneqERKS_@Base 14.11.95
| - _ZTI10KFilterDev@Base 4:16.08.0
| +#MISSING: 4:17.08.3-1# _ZTI10KFilterDev@Base 4:16.08.0
|   _ZTI13KEduVocLesson@Base 14.11.95
|   _ZTI15KEduVocDocument@Base 14.11.95
|   _ZTI15KEduVocWordType@Base 14.11.95
|   _ZTI16KEduVocContainer@Base 14.11.95
|   _ZTI16QXmlStreamReader@Base 14.11.95
|   _ZTI17KEduVocLeitnerBox@Base 14.11.95
| - _ZTS10KFilterDev@Base 4:16.08.0
| +#MISSING: 4:17.08.3-1# _ZTS10KFilterDev@Base 4:16.08.0
|   _ZTS13KEduVocLesson@Base 14.11.95
|   _ZTS15KEduVocDocument@Base 14.11.95
|   _ZTS15KEduVocWordType@Base 14.11.95
|   _ZTS16KEduVocContainer@Base 14.11.95
|   _ZTS16QXmlStreamReader@Base 14.11.95
|   _ZTS17KEduVocLeitnerBox@Base 14.11.95
| - _ZTV10KFilterDev@Base 4:16.08.0
| +#MISSING: 4:17.08.3-1# _ZTV10KFilterDev@Base 4:16.08.0
|   _ZTV13KEduVocLesson@Base 14.11.95
|   _ZTV15KEduVocDocument@Base 14.11.95
|   _ZTV15KEduVocWordType@Base 14.11.95
| dh_makeshlibs: failing due to earlier errors
| make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: 
pre_binary_dh_makeshlibs] Error 255
| make[1]: Leaving directory '/<>'
| make: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: 
debian/dhmk_binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

The failure is also reproduced by reproducible builds
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libkeduvocdocument_17.08.3-1.rbuild.log.gz
as well as crossqa.debian.net:
http://crossqa.debian.net/build/libkeduvocdocument_4:17.08.3-1_ppc64el_20190922053217.log

It appears to affect any architecture (at least amd64, arm64, ppc64el).

Helmut

Bug#943389: node-lodash: source package does not contain upstream source

[Jonas Smedegaard]

Package: node-lodash
Version: 4.17.15+dfsg-1
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The source package src:node-lodash states in its debian/copyright file
that its upstream source is https://github.com/lodash/lodash

$ apt source node-lodash
$ cd node-lodash-4.17.15+dfsg
$ tree -ad -I .pc
.
├── debian
│   ├── source
│   ├── tests
│   └── upstream
├── dist
├── doc
├── fp
├── .github
├── lib
│   ├── common
│   ├── fp
│   │   └── template
│   │   ├── doc
│   │   └── modules
│   └── main
├── lodash-cli
│   ├── bin
│   ├── lib
│   └── template
├── perf
│   └── asset
├── test
│   └── asset
└── vendor
├── backbone
│   └── test
│   └── setup
├── firebug-lite
│   ├── skin
│   │   └── xp
│   └── src
├── json-js
└── underscore
└── test

34 directories

$ git clone https://github.com/lodash/lodash
$ cd lodash
$ tree -ad -I '.git*'
.
├── .internal
└── test

2 directories


The tarball distributed as the "source" for the Debian packaging clearly
is *not* what upstream considers its source nor is it what is stated in
debian/copyright was used as source.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl2xcaUACgkQLHwxRsGg
ASGnLg/+Lsiq8c+vzd/2x9lXH7SwucK3bNiYl8X5QJYpC3Wuh72jEOHjl1gWl5MZ
uYBnR9G8h3UQNm0Tn2lgUAudhtV7af3mYJkKxBA6FMfYGEwPvig+8SoX0i0C3sjE
+fU01KFebmRsxJ+Of278titobzfgX2MJzWVQtzN5VbIvfAfuaQ4hjun0NCyPdbeM
2GKH5vnfs9Woi6P6ZmixlCvyT3B6bwl71q+x7RCNtAa5NhB8GrBMBG07jehrpCvK
gmhYNDnQeFYVQLObS8M5r/bLvT/9K7EuaPZxyhAg73c2bMOxcElwVC/IuZA832IL
woRqco6pJVYhLZ59sngrtqP9f/dkUF8IJkkFHCiDSfkcyFv37Vr0tJYSur1q+bWB
2viX9k2Nh4xbQ/P9RrWBhAcjrLRqTh3KD94kIJ6iVVhYxcwqVY/E31p2lwBLZZVx
jAGmdb4fYF+3Qgkmv0Hn67rWMEz8cWW0QZocIRMD/PmJJNgOUuTBV8asdF3wLo87
FfLJeeL6B6+taXJKK7lGgPv6cOkgjWamFNh7c4K1xsMWC2jmbQ6nSv23NJh8AwqQ
fNvKe2wXYqK0vedy4Z1QwXYXhA2yTGY4FmMvo+nXSuJ8Cp7/hbt0xy/g6N84cybX
v2SA5RhlSN8Y7xBvrK1DW1U+bATi6zTiIUSrnElg1tkj1JkcaTs=
=kSoi
-END PGP SIGNATURE-

Bug#935730: marked as done (kamcli: port to python 3 (or remove from Debian?))

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 09:07:32 +
with message-id 
and subject line Bug#935730: fixed in kamcli 2.0.0-1
has caused the Debian Bug report #935730,
regarding kamcli: port to python 3 (or remove from Debian?)
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.)


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

Hello,
kamcli is one of the only rdeps of python-tabulate; Debian has a target of
dropping Python 2 from Bullseye, so please port kamcli to python 3; an
alternative would be to drop kamcli entirely: it has a single popcon entry, so
i'm afraid it's not that populare of a package anyway.

Thanks,
Sandro

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

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

Versions of packages kamcli depends on:
ii  python  2.7.16-1
ii  python-click7.0-1
pn  python-pretty-yaml  
pn  python-sqlalchemy   
pn  python-tabulate 

kamcli recommends no packages.

kamcli suggests no packages.
--- End Message ---
--- Begin Message ---
Source: kamcli
Source-Version: 2.0.0-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Oct 2019 15:57:40 +0200
Source: kamcli
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Victor Seva 
Changed-By: Victor Seva 
Closes: 935730
Changes:
 kamcli (2.0.0-1) unstable; urgency=medium
 .
   * New upstream version 2.0.0
   * remove python2 support (closes: #935730)
   * refresh copyright file
   * update debhelper compat to 12. Update Standards-Version, no changes
   * add Vcs-* fields
   * add upstream fix for missing requirement
   * upstream fix, add kamgroup option
Checksums-Sha1:
 e9fea42bd39b7eb097e72af6f3798c8be15f0bd6 1486 kamcli_2.0.0-1.dsc
 42fbfeb57af003d63016aa749a803b02b9cffee6 30772 kamcli_2.0.0.orig.tar.gz
 bbd4405df8ad030678f8bf92aa8e7fa9231765f4 3372 kamcli_2.0.0-1.debian.tar.xz
 db5be966249b715180fa055e9723865c91e8e4a0 5562 kamcli_2.0.0-1_amd64.buildinfo
Checksums-Sha256:
 10e2f9e3b6c4afdd5532b2f92ff398e6647cbf22d09f45535029469197010b44 1486 
kamcli_2.0.0-1.dsc
 8a4920e17bd71bfaa912d8011b7a5bf61788ad930c61e92557ab66bc2ac0e4da 30772 
kamcli_2.0.0.orig.tar.gz
 095aeab975bce7049290f965ad43d674844041a37f7f8d3688e2efae24a151ae 3372 
kamcli_2.0.0-1.debian.tar.xz
 41c6bebbc0156557988f52c16327b965f4e5592334d1d97756b6f4bc9dbb2a02 5562 
kamcli_2.0.0-1_amd64.buildinfo
Files:
 9ece2e71ab19920bfe5dd3784f53d115 1486 misc optional kamcli_2.0.0-1.dsc
 fe60c48485c079b10c91a9e37d7515f3 30772 misc optional kamcli_2.0.0.orig.tar.gz
 a108c65440873b4881632301ff3452a0 3372 misc optional 
kamcli_2.0.0-1.debian.tar.xz
 7b7b22ec59d6a368649a55f8ffeccc65 5562 misc optional 
kamcli_2.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEDmBQEMrYIhRFqKAgIXSmjn2oLMcFAl2xZAIRHHZzZXZhQGRl
Ymlhbi5vcmcACgkQIXSmjn2oLMeK2Qf9E9gE/Gy2OmMN31oSyT1KLHmshsf3enY6
yC4+6YjXB4ADD/pivCW8mjSdnYQLkvTDk10mxFhyUT561v1RaO2uYP+2Ey3+2hgF
g9RK+yA2Tla7Rf9uH8DjURvoH8SP8EaC9gMOg0AFq/Uhz8n5VCApNWsUKZIpwsdm
0qYm7jBVB10QOAnkMudjHpVGfN0IO7e9zS7ddEJtXuQyb4ujtL2OuxIXJ1mhWs++
EnihtHV5OIhL9dVmcBqBd9sTfsbiyZUkSqYM7RFqYlF3l7X9uLThRaCugKkQGF6B
IysPhXBGO46bgJvP512WnyvRQmSQA7w0hOxSIr2M98OYrAK3/JIhWg==
=/ozJ
-END PGP SIGNATURE End Message ---

Bug#935845: [Pkg-javascript-devel] Bug#940708: Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

[Jonas Smedegaard]

Quoting Pirate Praveen (2019-10-24 10:46:20)
> 
> 
> On Thu, Oct 24, 2019 at 10:05, Jonas Smedegaard  wrote:
> > What I criticise is *zero* indication of bundling for the package 
> > lodash:
> > 
> >   src:lodash 4.17.15+dfsg-1
> > 
> > I would strongly prefer using current bundling scheme for that:
> > 
> >   src:lodash 4.17.15+dfsg+~4.17.5-1
> > 
> > If lodash had had such a version, I would not have wasted *hours* of
> > trying to figure out why the heck our 4.17.15 did not include what
> > upstream released in 4.17.13.
> > 
> 
> I think you are conveniently ignoring the root cause, lodash-cli did 
> not have a new release than what is bundled. How would have such a 
> version changed anything here?

In this cross-posted sub-thread I am solely reflecting on version numbering.

Please let's limit this madness of cross-posting and discuss 
lodash-specific original issue only at that one bugreport.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#942851: perl-modules-5.30: CPAN.pm is insecure by default, no warnings

[Vincent Lefevre]

On 2019-10-23 22:20:04 +0300, Niko Tyni wrote:
> So as I understand this, verifying CHECKSUMS would be the thing to do,
> and setting 'check_sigs' wouldn't really help (only deployed partially
> and no web of trust to the module authors).

Indeed, and even if check_sigs is set, it is ignored if the module is
not signed (instead of getting a failure). But CHECKSUMS needs to be
downloaded from a reliable website (I assume that www.cpan.org is) and
in a secure way (https, not http).

> From a cursory look it looks to me like cpanm from src:cpanminus verifies
> CHECKSUMS if Module::Signature (src:libmodule-signature-perl, bundles a
> recent PAUSE public key) is installed, but CPAN.pm doesn't. But I might
> be wrong.

I can see that, by default, CHECKSUMS is verified, if I understand
correctly:

[...]
Running install for module 'XML::TreePP'
Fetching with LWP:
http://www.cpan.org/authors/id/K/KA/KAWASAKI/XML-TreePP-0.43.tar.gz
Fetching with LWP:
http://www.cpan.org/authors/id/K/KA/KAWASAKI/CHECKSUMS
Checksum for 
/home/vlefevre/.cpan/sources/authors/id/K/KA/KAWASAKI/XML-TreePP-0.43.tar.gz ok
[...]

However, with the default urllist value, it is downloaded using http
(not https). One needs to set urllist to

  [q[https://www.cpan.org/]]

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

Bug#942851: perl-modules-5.30: CPAN.pm is insecure by default, no warnings

[Vincent Lefevre]

On 2019-10-23 22:20:04 +0300, Niko Tyni wrote:
> FWIW this has been the case since forever.

Yes, but almost no-one knows about this security issue. Using the
CPAN client is generally recommended on the web, but I have never
seen any mention of this security issue, not even on the cpan website:

  https://www.cpan.org/modules/INSTALL.html

The "quick start" starts with "cpan App::cpanminus"...

Even I was quite surprised. Security may not have been much concerned
10 - 15 years ago, but nowadays one expects that software is safe
(modulo bugs).

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

Bug#935845: [Pkg-javascript-devel] Bug#940708: Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

[Pirate Praveen]

On Thu, Oct 24, 2019 at 10:05, Jonas Smedegaard  wrote:
What I criticise is *zero* indication of bundling for the package 
lodash:


  src:lodash 4.17.15+dfsg-1

I would strongly prefer using current bundling scheme for that:

  src:lodash 4.17.15+dfsg+~4.17.5-1

If lodash had had such a version, I would not have wasted *hours* of
trying to figure out why the heck our 4.17.15 did not include what
upstream released in 4.17.13.



I think you are conveniently ignoring the root cause, lodash-cli did 
not have a new release than what is bundled. How would have such a 
version changed anything here?

Bug#936219: marked as done (blockdiag: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 08:42:45 +
with message-id 
and subject line Bug#936219: fixed in blockdiag 1.5.3+dfsg-5.3
has caused the Debian Bug report #936219,
regarding blockdiag: Python2 removal in sid/bullseye
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.)


-- 
936219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:blockdiag
Version: 1.5.3+dfsg-5.2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:blockdiag

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: blockdiag
Source-Version: 1.5.3+dfsg-5.3

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated blockdiag 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: Thu, 24 Oct 2019 09:23:00 +0200
Source: blockdiag
Architecture: source
Version: 1.5.3+dfsg-5.3
Distribution: unstable
Urgency: medium
Maintainer: Kouhei Maeda 
Changed-By: Thomas Goirand 
Closes: 936219
Changes:
 blockdiag (1.5.3+dfsg-5.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Removed Python 2 support (Closes: #936219).
   * Switched to debhelper-compat (= 11), as the package was using
 debian/compat with version 7, and debhelper >= 8.
Checksums-Sha1:
 21b20cba4daebe54c94a3eaae35d56ab1d9a6701 2094 blockdiag_1.5.3+dfsg-5.3.dsc
 76c86ac753eff4ee86fc873d7e278ff9a09c17a7 11228 
blockdiag_1.5.3+dfsg-5.3.debian.tar.xz
 0faf5baee38492b4a6044c38e2fd2cb6189534ea 8261 
blockdiag_1.5.3+dfsg-5.3_amd64.buildinfo
Checksums-Sha256:
 9582fefe82b5a3425fb9bb0d1ed15df58a3850c46ecaa203b9301958071f8c16 2094 
blockdiag_1.5.3+dfsg-5.3.dsc
 b45f9ab8ca125d9ce325ccd3000200781c87d80a7f1d41343f6d301d5981b5f4 11228 

Bug#935845: [Pkg-javascript-devel] Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

[Jonas Smedegaard]

Quoting Xavier (2019-10-24 09:18:38)
> 
> 
> Le 23 octobre 2019 22:07:55 GMT+02:00, Jonas Smedegaard  a 
> écrit :
> >Quoting Paolo Greppi (2019-10-23 21:18:37)
> >> First, I tripped on this one while testing yarnpkg 1.19.1 from
> >experimental.
> >> For the record, this is how I found that node-lodash was the culprit:
> >> 
> >> node --trace-deprecation /usr/bin/yarnpkg install
> >> yarn install v1.19.1
> >> [1/4] Resolving packages...
> >> (node:29081) [DEP0016] DeprecationWarning: 'root' is deprecated, use
> >'global'
> >> at Object.
> >(/usr/share/nodejs/lodash/_createRound.js:6:22)
> >> at Module._compile (internal/modules/cjs/loader.js:778:30)
> >> at Object.Module._extensions..js
> >(internal/modules/cjs/loader.js:789:10)
> >> at Module.load (internal/modules/cjs/loader.js:653:32)
> >> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> >> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> >> at Module.require (internal/modules/cjs/loader.js:692:17)
> >> at require (internal/modules/cjs/helpers.js:25:18)
> >> at Object. (/usr/share/nodejs/lodash/ceil.js:1:19)
> >> at Module._compile (internal/modules/cjs/loader.js:778:30)
> >> ...
> >> 
> >> Second, this should not be an RC bug.
> >> It's a deprecation **warning**.
> >> And it could be easily patched out by allowing stderr in the
> >autopkgtest.
> >> 
> >> But (and that's the third point) there's no need of that hack,
> >because the actual fix is easier.
> >> 
> >> The upstream commit that Jonas pointed to is on a branch
> >(4.17.15-npm) where upstream stores built artifacts ("binaries").
> >> You can rebuild those binaries locally in this package sources dir
> >with:
> >> NODE_PATH=. node lodash-cli/bin/lodash modularize exports=node -o
> >modules
> >> only to find that the generated modules/_createRound.js lacks the
> >root = require statement
> >> 
> >> The reason is that the bundled version of lodash-cli is out of date:
> >> grep version lodash-cli/package.json 
> >>   "version": "4.17.5",
> >> 
> >> if you replace the lodash-cli dir with the current version (which is
> >in sync with lodash itself, 4.17.15) you get the correct file
> >generated.
> >> 
> >> So in the future we should keep the bundled lodash-cli in sync with
> >lodash itself.
> >
> >More importantly: We should track versions!!!
> >
> >lodash embeds lodash-cli with "ignore" in its watch file.
> >
> >How many JavaScript packages are packaged that way?
> 
> Then what to answer to https://bugs.debian.org/940708 ?

I agree with Jonathan Dowland that tracking an upstream project by use 
of a version string like 
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-5
 
is painful and should be replaced.

I do not volunteer to implement an alternative, but imagine that a 
sensible alternative could look like 6.2.1+ds+~20191003+d4e91ce where 
the latter part would indicate day of bundling and tiny hash of bundle, 
and if there was ever a need to issue another bundle on same day then 
the scheme would support adding a serial: 6.2.1+ds+~20191003.1+d08d819

I find it less painful to use the current bundling scheme to track 
_bundles_ of a _limited_ set of relatively stale upstreams, like 
src:jsbundle-web-interfaces 4.0.2~1.1.0+~2.0.1~ds+~4.0.2+~0~20180821-2

What I criticise is *zero* indication of bundling for the package lodash:

  src:lodash 4.17.15+dfsg-1

I would strongly prefer using current bundling scheme for that:

  src:lodash 4.17.15+dfsg+~4.17.5-1

If lodash had had such a version, I would not have wasted *hours* of 
trying to figure out why the heck our 4.17.15 did not include what 
upstream released in 4.17.13.

I consider the watch file a helper tool, not part of the mandatory 
skeleton of a source package, and expect to have adequate information 
about what consitutes "the source" without needing to extrapolate hints 
from the watch file.

Oh, and please in future don't cross-post.  And when you do anyway then 
say so explicitly and state your plan for how to untangle it - e.g. 
"please follow up only at foobar@baz".


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#936219: diff of the NMU for this bug

[Thomas Goirand]

Hi,

Since you haven't replied to the previous mail, I've uploaded this
without delay, fixing the RC bug on blockdiag.

Cheers,

Thomas Goirand (zigo)
diff -Nru blockdiag-1.5.3+dfsg/debian/changelog 
blockdiag-1.5.3+dfsg/debian/changelog
--- blockdiag-1.5.3+dfsg/debian/changelog   2018-07-16 18:07:06.0 
+0200
+++ blockdiag-1.5.3+dfsg/debian/changelog   2019-10-24 09:23:00.0 
+0200
@@ -1,3 +1,12 @@
+blockdiag (1.5.3+dfsg-5.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Removed Python 2 support (Closes: #936219).
+  * Switched to debhelper-compat (= 11), as the package was using
+debian/compat with version 7, and debhelper >= 8.
+
+ -- Thomas Goirand   Thu, 24 Oct 2019 09:23:00 +0200
+
 blockdiag (1.5.3+dfsg-5.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru blockdiag-1.5.3+dfsg/debian/compat blockdiag-1.5.3+dfsg/debian/compat
--- blockdiag-1.5.3+dfsg/debian/compat  2017-05-29 05:24:55.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/compat  1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-7
diff -Nru blockdiag-1.5.3+dfsg/debian/control 
blockdiag-1.5.3+dfsg/debian/control
--- blockdiag-1.5.3+dfsg/debian/control 2017-05-26 15:06:27.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/control 2019-10-24 09:23:00.0 +0200
@@ -2,23 +2,12 @@
 Section: python
 Priority: optional
 Maintainer: Kouhei Maeda 
-Build-Depends: debhelper (>= 8.0.0),
+Build-Depends: debhelper-compat (= 11),
dh-python,
-   python-all,
-   python-setuptools,
-   python-configparser,
-   python-unittest2,
-   pep8 (>= 1.3),
-   python-nose,
-   python-zc.buildout,
-   python-funcparserlib (>= 0.3.4),
-   python-docutils,
-   python-pil,
-   python-webcolors,
-   python-reportlab,
-   python-mock,
-   python-wand,
-   python-pep8,
+   libmagickcore-6.q16-3-extra,
+   python3-unittest2,
+   python3-docutils,
+   python3-pep8,
python3-all,
python3-setuptools,
python3-pep8 (>= 1.3),
@@ -30,26 +19,11 @@
python3-reportlab,
python3-mock,
python3-wand,
-   libmagickcore-6.q16-3-extra,
+   python3-zc.buildout,
fonts-vlgothic | fonts-japanese-gothic
 Standards-Version: 3.9.8
-X-Python-Version: 2.7
 Homepage: http://blockdiag.com/
 
-Package: python-blockdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-funcparserlib (>= 0.3.4),
- python-pil,
- python-docutils,
- python-reportlab,
- python-webcolors
-Description: generate block-diagram image file from spec-text file
- Generate block-diagram from dot like text with multilingualization for
- node-label. But this supports utf-8 only. It is able to embed to sphinx with 
- using python-sphinxcontrib-blockdiag.
-
 Package: python3-blockdiag
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages 
blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages
--- blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages   2011-10-08 
08:20:33.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages   1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-blockdiag.1
diff -Nru blockdiag-1.5.3+dfsg/debian/rules blockdiag-1.5.3+dfsg/debian/rules
--- blockdiag-1.5.3+dfsg/debian/rules   2017-06-04 05:04:56.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/rules   2019-10-24 09:23:00.0 +0200
@@ -8,7 +8,7 @@
 export PYBUILD_AFTER_TEST=rm -rf {build_dir}/circle.*
 
 %:
-   dh $@ --with python2,python3 --buildsystem=pybuild
+   dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_python3:
dh_python3 --shebang=/usr/bin/python3

Bug#935845: [Pkg-javascript-devel] Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

[Xavier]

Le 23 octobre 2019 22:07:55 GMT+02:00, Jonas Smedegaard  a 
écrit :
>Quoting Paolo Greppi (2019-10-23 21:18:37)
>> First, I tripped on this one while testing yarnpkg 1.19.1 from
>experimental.
>> For the record, this is how I found that node-lodash was the culprit:
>> 
>> node --trace-deprecation /usr/bin/yarnpkg install
>> yarn install v1.19.1
>> [1/4] Resolving packages...
>> (node:29081) [DEP0016] DeprecationWarning: 'root' is deprecated, use
>'global'
>> at Object.
>(/usr/share/nodejs/lodash/_createRound.js:6:22)
>> at Module._compile (internal/modules/cjs/loader.js:778:30)
>> at Object.Module._extensions..js
>(internal/modules/cjs/loader.js:789:10)
>> at Module.load (internal/modules/cjs/loader.js:653:32)
>> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
>> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
>> at Module.require (internal/modules/cjs/loader.js:692:17)
>> at require (internal/modules/cjs/helpers.js:25:18)
>> at Object. (/usr/share/nodejs/lodash/ceil.js:1:19)
>> at Module._compile (internal/modules/cjs/loader.js:778:30)
>> ...
>> 
>> Second, this should not be an RC bug.
>> It's a deprecation **warning**.
>> And it could be easily patched out by allowing stderr in the
>autopkgtest.
>> 
>> But (and that's the third point) there's no need of that hack,
>because the actual fix is easier.
>> 
>> The upstream commit that Jonas pointed to is on a branch
>(4.17.15-npm) where upstream stores built artifacts ("binaries").
>> You can rebuild those binaries locally in this package sources dir
>with:
>> NODE_PATH=. node lodash-cli/bin/lodash modularize exports=node -o
>modules
>> only to find that the generated modules/_createRound.js lacks the
>root = require statement
>> 
>> The reason is that the bundled version of lodash-cli is out of date:
>> grep version lodash-cli/package.json 
>>   "version": "4.17.5",
>> 
>> if you replace the lodash-cli dir with the current version (which is
>in sync with lodash itself, 4.17.15) you get the correct file
>generated.
>> 
>> So in the future we should keep the bundled lodash-cli in sync with
>lodash itself.
>
>More importantly: We should track versions!!!
>
>lodash embeds lodash-cli with "ignore" in its watch file.
>
>How many JavaScript packages are packaged that way?

Then what to answer to https://bugs.debian.org/940708 ?
-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Bug#937926: Lowered severity

[Thomas Goirand]

Hi,

I've re-introduced python-pbr, so the severity of this bug can be
lowered back to just 'important'. We'll revisit Py2 removal from this
package once these are fixed:

http://sandrotosi.me/debian/py2removal/python-mock_1.svg

Cheers,

Thomas Goirand (zigo)

Processed: Lower python-mock severity

[Debian Bug Tracking System]

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

> severity 937926 important
Bug #937926 [src:python-mock] python-mock: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 936046 5.12.3+dfsg-3
Bug #936046 [python3-pyqt5] python3-pyqt5: does not depends on matching 
qtbase-abi
Marked as fixed in versions pyqt5/5.12.3+dfsg-3.
> thanks
Stopping processing here.

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

Bug#936046: python3-pyqt5: does not depends on matching qtbase-abi

[Gregor Riepl]

Looks like the dependency chain is fixed, python3-pyqt5 is installable again.

Thanks.

Bug#936046: marked as done (python3-pyqt5: does not depends on matching qtbase-abi)

[Debian Bug Tracking System]

Your message dated Thu, 24 Oct 2019 09:07:46 +0200
with message-id <07d8e1c7-0da2-da3a-feaa-57faf0c88...@gmail.com>
and subject line 
has caused the Debian Bug report #936046,
regarding python3-pyqt5: does not depends on matching qtbase-abi
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.)


-- 
936046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyqt5
Version: 5.12.3+dfsg-1


Quack,

I needed the QT5 version in experimental for some reason. Now i'd like
to install python3-pyqt5 but is still depend on qtbase-abi-5-11-3.

As it follows the same exact version as QT core I guess it's meant to
work together. Maybe I'm wrong but it would make things easier if these
experimental package would be installable together.

Regards.
\_o<




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 12029--- End Message ---