Bug#969768: marked as done (libio-socket-ip-perl: do not release with bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 23:48:27 +
with message-id 
and subject line Bug#969768: fixed in libio-socket-ip-perl 0.41-1
has caused the Debian Bug report #969768,
regarding libio-socket-ip-perl: do not release with 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.)


-- 
969768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libio-socket-io-perl
Version: 0.39-2
Severity: serious
Justification: maintainer

IO-Socket-IP is bundled with perl 5.30, so there is no need to ship
this separately.
--- End Message ---
--- Begin Message ---
Source: libio-socket-ip-perl
Source-Version: 0.41-1
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libio-socket-ip-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Sep 2020 01:22:57 +0200
Source: libio-socket-ip-perl
Architecture: source
Version: 0.41-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 969768
Changes:
 libio-socket-ip-perl (0.41-1) unstable; urgency=medium
 .
   * Import upstream version 0.41.
 Fixes "do not release with bullseye": this release is newer than the
 bundled version in src:perl. (Closes: #969768)
   * Update years of upstream and packaging copyright.
   * Declare compliance with Debian Policy 4.5.0.
   * Set Rules-Requires-Root: no.
   * Annotate test-only build dependencies with .
   * Bump debhelper-compat to 13.
   * Refresh patches (offset).
   * Use HTTPS for repository URL in debian/upstream/metadata.
Checksums-Sha1:
 a396da0820aedcb7b613537265ebb88c258f6c8b 2592 libio-socket-ip-perl_0.41-1.dsc
 0618286bd209c37c7a7eee0f6348d3f122fbe464 44692 
libio-socket-ip-perl_0.41.orig.tar.gz
 41ecd71bcf7b3f7aed1c4f84369967bb4b75950d 5348 
libio-socket-ip-perl_0.41-1.debian.tar.xz
Checksums-Sha256:
 f293bbf34dffe736aa04b5d32787ce703a8e3371f95418362a1a5c387331b76e 2592 
libio-socket-ip-perl_0.41-1.dsc
 849a45a238f8392588b97722c850382c4e6d157cd08a822ddcb9073c73bf1446 44692 
libio-socket-ip-perl_0.41.orig.tar.gz
 014fe3537911f7e7b5a45280b8351b39cca63a2b0f1381850a111f6522c16029 5348 
libio-socket-ip-perl_0.41-1.debian.tar.xz
Files:
 12c4c0845eb9f60320be84cc9528f5d0 2592 perl optional 
libio-socket-ip-perl_0.41-1.dsc
 629947f8b86b08b7a636bd7ccc3d4925 44692 perl optional 
libio-socket-ip-perl_0.41.orig.tar.gz
 daa1686ca8ff2ce1ebb658b48e192035 5348 perl optional 
libio-socket-ip-perl_0.41-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl9vzmpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZIzg//eY9y/IpZzQiwC800I5Z8KXyTeuXsDDvwf+zIY/TY8pg4RE8+ZMJGSOTB
SW1TP0lFwc1xMsKL1AMBvvO5E95npKWiibI1yYwFfDYQUzTplfEWdc/WHtDK0zeH
/Z+pV5WgmnGy0k34sxgw/f6azoMucmSsJBoKT4WgRCql0vxwPgjoQUyEtEB+uUN9
IZRt7oLMSlHbaqcnEWKm248SfdCyTUfWTTf8xiJKBVdzUTOfjCALOwz45yDWpkRL
Vtwu8uMUU541IUQkxGdAohx2LrOOSNjNsMj0wPI4S/or6KTOeMQXf16kLzKiQjGc
6/rSq0c6e5JmGhoy95nl+Q9C0NUuxpDtLdVAj5n5ti5K9ukWpQMSW8QdaWiaxn3J
5QHbaQNiTCFvFAaHlyyEZbpTyvdmtkbAxS5xTHbaY7hTE/xoPqsWlB1tzGPcupI4
HOmE8TLOwBUqloofVpMxex9w16cqTI019z+rjoQgpqPSo/3pkSI7NIBK5XCZRIey
yIwydIlNSPHPSEb8Oo/chltaHYN6MbY9gFFFxgmuaZjR6Dldm4ufMNz9FA80+SIf
5jX0TZRFx3BPI45MTRYB0RkpEaHxopt+Bn1XzGhDdhGd7hDzDWTNvPb9Hn3K106v
A86NU8yazMAmeyqKiyCxyMf8d8dUlRRz+XvO1ZHs44m/ViQQe5s=
=0El4
-END PGP SIGNATURE End Message ---

Bug#917485: ckermit: relax openssl version check or tighten libssl1.x.y dependencies

[Paul Wise]

On Sat, 2020-09-26 at 10:12 +0200, Sébastien Villemot wrote:

> The bug was fixed by a patch in 302-5.3+deb9u1. The reintroduction of
> the package, even if it no longer contains the patch, did not
> reintroduce the bug, because upstream fixed it in another way: the
> dynamic check against the version of OpenSSL has been improved, in the
> sense that it accept changes in the patchlevel version (e.g. if the
> package was compiled against OpenSSL 1.1.0, the dynamic check will
> allow execution against 1.1.1, since there is ABI stability).

At first glance the code didn't seem to have fixed the issue.
Thanks for the info and the clarification and sorry for the noise.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#969967: marked as done (libtest-tcp-perl: bogus dependency libio-socket-ip-perl (>= 0.39-3~))

[Debian Bug Tracking System]

Your message dated Sun, 27 Sep 2020 01:28:54 +0200
with message-id <20200926232854.ga18...@jadzia.comodo.priv.at>
and subject line Re: Bug#969967: libtest-tcp-perl: bogus dependency 
libio-socket-ip-perl (>= 0.39-3~)
has caused the Debian Bug report #969967,
regarding libtest-tcp-perl: bogus dependency libio-socket-ip-perl (>= 0.39-3~)
to be marked as done.

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

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


-- 
969967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtest-tcp-perl
Version: 2.22-2
Severity: serious

libtest-tcp-perl 2.22-2 depends on libio-socket-ip-perl (>= 0.39-3~),
but libio-socket-ip-perl, as bundled with perl 5.30, will not be in
bullseye. See

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

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

Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libtest-tcp-perl depends on:
ii  libio-socket-ip-perl  0.39-3
ii  libtest-sharedfork-perl   0.35-1
ii  perl  5.30.3-4
ii  perl-base [libio-socket-ip-perl]  5.30.3-4

libtest-tcp-perl recommends no packages.

libtest-tcp-perl suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
On Wed, 09 Sep 2020 15:17:58 +0200, Vincent Lefevre wrote:

> libtest-tcp-perl 2.22-2 depends on libio-socket-ip-perl (>= 0.39-3~),
> but libio-socket-ip-perl, as bundled with perl 5.30, will not be in
> bullseye. See
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969768

#969768 is closed by the upload of libio-socket-ip-perl 0.41-1, hence
closing this bug as well.

Cheers,
gregor

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


signature.asc
Description: Digital Signature
--- End Message ---

Bug#969768: lib-io-socket-ip-perl: do not release with bullseye

[gregor herrmann]

On Sat, 26 Sep 2020 23:52:42 +0100, Dominic Hargreaves wrote:

> > I guess we should update libio-socket-ip-perl to 0.41 and close this
> > bug with the upload (and close #969967 in libtest-tcp-perl as well).
> > 
> > I've pushed libio-socket-ip-perl_0.41-1 to git but wanted to give
> > others a chance to comment before the actual upload.
> 
> Fine by me!

Thanks Dom!

libio-socket-ip-perl 0.41-1 uploaded (and #969967 closed manually).


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#970258: marked as done (openafs-modules-dkms: Does not build on bullseye with kernel 5.8.7)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 23:04:12 +
with message-id 
and subject line Bug#970258: fixed in openafs 1.8.6-3
has caused the Debian Bug report #970258,
regarding openafs-modules-dkms: Does not build on bullseye with kernel 5.8.7
to be marked as done.

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

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


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

DKMS fails to build the module on bullseye with kernel 5.8.7



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

Kernel: Linux 5.7.17-ivybridge (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openafs-modules-dkms depends on:
ii  dkms   2.8.3-4
ii  libc6-dev  2.31-3
ii  perl   5.30.3-4

Versions of packages openafs-modules-dkms recommends:
ii  openafs-client  1.8.6-2

openafs-modules-dkms suggests no packages.

-- no debconf information
-- 
Robert Senger 
PGP/GPG Public Key ID: 8714E1A3
DKMS make.log for openafs-1.8.6 for kernel 5.8.7-ivybridge (x86_64)
So 13. Sep 22:35:01 CEST 2020
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for flex... no
checking for lex... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libxslt... no
checking for saxon... no
checking for xalan-j... no
checking for xsltproc... no
checking for fop... no
checking for dblatex... no
checking for docbook2pdf... no
configure: WARNING: Docbook stylesheets not found; some documentation can't be built
checking for kindlegen... no
checking for doxygen... no
checking for dot... no
checking for library containing strerror... none required
checking for pid_t... yes
checking for size_t... yes
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for bison... no
checking for byacc... no
checking if lex is flex... yes
checking whether byte order is known at compile time... yes
checking whether byte ordering is bigendian... no
checking whether printf understands the %z length modifier... yes
checking your OS... linux
checking your AFS sysname... amd64_linux26
checking for ranlib... (cached) ranlib
checking for as... as
checking for mv... mv
checking for rm... rm
checking for ld... ld
checking for cp... cp
checking for gencat... gencat
checking if gcc accepts -march=pentium... no
checking if gcc needs -fno-strength-reduce... yes
checking if gcc needs -fno-strict-aliasing... yes
checking if gcc supports -fno-common... yes
checking if gcc supports -pipe... yes
checking if linux kbuild requires EXTRA_CFLAGS... no
checking if linux kernel module build works... yes
checking operation follow_link in inode_operations... no
checking operation put_link in inode_operations... no
checking operation rename in inode_operations... yes
checking for linux/cred.h... yes
checking for linux/config.h... no
checking for linux/exportfs.h... yes
checking for linux/freezer.h... yes
checking for linux/key-type.h... yes
checking for linux/semaphore.h... yes
checking for linux/seq_file.h... yes
checking for linux/sched/signal.h... yes
checking for linux/uaccess.h... yes
checking for struct vfs_path... no
checking for kuid_t... yes

Bug#954503: marked as done (ruby-mustache: FTBFS: ERROR: Test "ruby2.7" failed.)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 23:04:28 +
with message-id 
and subject line Bug#954503: fixed in ruby-mustache 1.1.1-2
has caused the Debian Bug report #954503,
regarding ruby-mustache: FTBFS: ERROR: Test "ruby2.7" failed.
to be marked as done.

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

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


-- 
954503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mustache
Version: 1.0.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rb 
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-mustache/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-mustache/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 debian/ruby-tests.rb
> Run options: --seed 47874
> 
> # Running:
> 
> FFF
> 
> Finished in 0.041855s, 2269.7384 runs/s, 2986.4979 assertions/s.
> 
>   1) Failure:
> AutoloadingTest#test_autoload [/<>/test/autoloading_test.rb:12]:
> Expected: Comments
>   Actual: nil
> 
>   2) Failure:
> AutoloadingTest#test_autoload_lowercase 
> [/<>/test/autoloading_test.rb:17]:
> Expected: Comments
>   Actual: nil
> 
>   3) Failure:
> AutoloadingTest#test_folder_autoload 
> [/<>/test/autoloading_test.rb:40]:
> Expected: TestViews::Namespaced
>   Actual: nil
> 
> 95 runs, 125 assertions, 3 failures, 0 errors, 0 skips
> ERROR: Test "ruby2.7" failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/ruby-mustache_1.0.2-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-mustache
Source-Version: 1.1.1-2
Done: =?utf-8?q?C=C3=A9dric_Boutillier?= 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Sep 2020 00:15:55 +0200
Source: ruby-mustache
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 954503
Changes:
 ruby-mustache (1.1.1-2) unstable; urgency=medium
 .
   * Team upload
   * Move debian/watch to gemwatch.debian.net
   * Add 003_no_simplecov.patch to remove usage of simplecov in tests
   * Add 004_fix_race_condition_tests.patch to fix order-related test failures
 (Closes: #954503)
   * Use the rake method to run tests
   * Update Team name
   * Explicitly mention that d/rules does not require root
   * Set debhelper-compat level to 13
Checksums-Sha1:
 55b42a144ca664fd6893503a01e237e79c1f5f0d 1663 ruby-mustache_1.1.1-2.dsc
 aadd08625861194ebf1b92a307ced468378f1d51 39342 ruby-mustache_1.1.1.orig.tar.gz
 1312ce243a012c15688f907e170da751e5433957 4304 
ruby-mustache_1.1.1-2.debian.tar.xz
 c3df5c5f957bf66ff98b6a33b682de5edadb33c4 8296 
ruby-mustache_1.1.1-2_amd64.buildinfo
Checksums-Sha256:
 66ccfa4f852fe57b21a579cd4d1343a2598702ed6616077ca51d8512cde46c03 1663 
ruby-mustache_1.1.1-2.dsc
 

Bug#969768: lib-io-socket-ip-perl: do not release with bullseye

[Dominic Hargreaves]

On Sat, Sep 26, 2020 at 05:07:13PM +0200, gregor herrmann wrote:
> Control: tag -1 + pending
> 
> On Mon, 07 Sep 2020 23:50:03 +0100, Dominic Hargreaves wrote:
> 
> > IO-Socket-IP is bundled with perl 5.30, so there is no need to ship
> > this separately.
> 
> IO-Socket-IP 0.41 has been released, without the patch for #964902
> but with some other changes:
> https://metacpan.org/pod/IO::Socket::IP
> 
> IO::Socket::IP 0.41 is bundled with perl ony starting with v5.33.2,
> which won't be in Debian any time soon.
> 
> I guess we should update libio-socket-ip-perl to 0.41 and close this
> bug with the upload (and close #969967 in libtest-tcp-perl as well).
> 
> I've pushed libio-socket-ip-perl_0.41-1 to git but wanted to give
> others a chance to comment before the actual upload.

Fine by me!

Processed: Bug#954503 marked as pending in ruby-mustache

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954503 [src:ruby-mustache] ruby-mustache: FTBFS: ERROR: Test "ruby2.7" 
failed.
Added tag(s) pending.

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

Bug#954503: marked as pending in ruby-mustache

[Cédric Boutillier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-mustache/-/commit/41a55f76ceadc0e33fe9ee315d788b6bf7e6f9a9


Add 004_fix_race_condition_tests.patch to fix order-related test failures 
(Closes: #954503)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954503

Processed: bug 954503 is forwarded to https://github.com/mustache/mustache/pull/258

[Debian Bug Tracking System]

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

> forwarded 954503 https://github.com/mustache/mustache/pull/258
Bug #954503 [src:ruby-mustache] ruby-mustache: FTBFS: ERROR: Test "ruby2.7" 
failed.
Set Bug forwarded-to-address to 'https://github.com/mustache/mustache/pull/258'.
> thanks
Stopping processing here.

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

Bug#960265: s390x install Debootstrap warning: Failure while configuring base packages. s390-tools depends on perl:any.

[Philipp Kern]

On 14.06.20 17:20, Philipp Kern wrote:
> On 11.05.20 11:53, Winfried Münch wrote:
>> package: s390-tools
>>
>> Version: current Installer from 04.05.2020 21:14
>> http://ftp.halifax.rwth-aachen.de/debian/dists/buster/main/installer-s390x/current/images/generic/
>>
>>
>> When I install debian I run in this Problem (from console 4):
>>
>> May 11 09:43:43 debootstrap: Errors were encountered while processing:
>> May 11 09:43:43 debootstrap:  s390-tools
>> May 11 09:43:44 debootstrap: dpkg: dependency problems prevent
>> configuration of s390-tools:
>> May 11 09:43:44 debootstrap:  s390-tools depends on perl:any.
>> May 11 09:43:44 debootstrap:
>> May 11 09:43:44 debootstrap: dpkg: error processing package s390-tools
>> (--configure):
>> May 11 09:43:44 debootstrap:  dependency problems - leaving unconfigured
>>
>> Installation failed in step install base system.
> 
> perl:any is not part of the transitive closure that debootstrap
> calculates. To me it looks like a bug in debootstrap in that it does not
> find a deb to download because it does not drop the :any - either in
> pkgdetails or before.
> 
> This was presumably broken by 2.3.0-1 which packaged ziomon and included
> a ${perl:Depends} on the main package as well - possibly because Lintian
> alerted about the missing dependency. That was technically correct, as
> it includes binaries that require modules from perl rather than
> perl-base. And it would presumably have worked if "perl:any" had instead
> been substituted as "perl".
> 
> It's pretty telling how late this was discovered, sort of pointing out
> that Debian s390x has no users at all if that kind of bug slips into a
> stable release. Ubuntu forked the base tooling and thus was not
> affected. To be honest, that tells me that the port should be demoted
> and not be part of the next release. Especially given the lack of
> (motivated) porters.

The good news is that with Debian stable 10.6 that was released today
the installation actually works again and I was able to conduct a
successful one from within z/VM.

Kind regards
Philipp Kern



signature.asc
Description: OpenPGP digital signature

Bug#970102: marked as done (src:barman: fails to migrate to testing for too long: maintainer built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 19:18:23 +
with message-id 
and subject line Bug#970102: fixed in barman 2.11-1.1
has caused the Debian Bug report #970102,
regarding src:barman: fails to migrate to testing for too long: maintainer 
built arch:all binaries
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.)


-- 
970102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: barman
Version: 2.10-2
Severity: serious
Control: close -1 2.11-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:barman in its
current version in unstable has been trying to migrate for 60 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=barman




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: barman
Source-Version: 2.11-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated barman package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Sep 2020 20:21:45 +0200
Source: barman
Architecture: source
Version: 2.11-1.1
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini 
Changed-By: Paul Gevers 
Closes: 970102
Changes:
 barman (2.11-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #970102)
Checksums-Sha1:
 e96b36fd68a72ba57ac47ca9680aac9d60e63ccb 2067 barman_2.11-1.1.dsc
 035278176fe8fc66de29c2a31ed3e578bed2fbe1 11036 barman_2.11-1.1.debian.tar.xz
Checksums-Sha256:
 c8282da414512ac0716db951bcd6b2dc665b7d82aca428ebbdcc04663d78eebb 2067 
barman_2.11-1.1.dsc
 8b04182fcd546db42707f8e4353043186c59d68dd3deee969673cd5400db8fa3 11036 
barman_2.11-1.1.debian.tar.xz
Files:
 6034dd7e492d658c17387872afc68b3b 2067 database optional barman_2.11-1.1.dsc
 e57e42f2fb5a52001e650c65c0a97691 11036 database optional 
barman_2.11-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl9bwFQACgkQnFyZ6wW9
dQoE4ggAnFQieC/iP4RlS9/gd+jJeci8/q3cko9KKCTOCPUVZFOMjKdHOInmTSyE
TAwMuRiQ15ORtiAZiB8j7WtiJqNkDnDmG2jw/kcq6jHoOQtBLwpFlqaj6mGuW8Tp
0rrMcOYUUu0bX0r0NcfP7wGYxa/DzDhTrIS1Vs4gA6sp51Idx09CCkxCFcfs2Bls
1wGQ+Hvq73IJl3BZAwGCPxgwmtF/Dl46fa8dBoje3JKozdSndGjt5hYwTHezzUZA
fny2mwhQhcICdy+kr+8WOZfqGeE10TOiTEJQWs+eIXxdJwRc8uy+lQRHMAKZ7Fvf
ghcvkXY7mm6rxkGM2KS/mhHkLjmNAA==
=nXDX
-END PGP 

Bug#971048: samba: CVE-2020-1472

[Salvatore Bonaccorso]

Source: samba
Version: 2:4.12.5+dfsg-3
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole
Forwarded: https://bugzilla.samba.org/show_bug.cgi?id=14497
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2:4.9.5+dfsg-5+deb10u1
Control: found -1 2:4.9.5+dfsg-5
Control: found -1 2:4.5.16+dfsg-1+deb9u2
Control: found -1 2:4.5.16+dfsg-1

Hi,

The following vulnerability was published for samba.

CVE-2020-1472[0]:
| An elevation of privilege vulnerability exists when an attacker
| establishes a vulnerable Netlogon secure channel connection to a
| domain controller, using the Netlogon Remote Protocol (MS-NRPC), aka
| 'Netlogon Elevation of Privilege Vulnerability'.

I realize that setting the RC severity might be disputed, given by
default since 4.8 versions are not 'vulnerable' unless admins have
switched to 'server schannel = no' or 'server schannel = auto' from
the default.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-1472
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1472
[1] https://bugzilla.samba.org/show_bug.cgi?id=14497
[2] https://www.openwall.com/lists/oss-security/2020/09/17/2
[3] https://www.samba.org/samba/security/CVE-2020-1472.html

Regards,
Salvatore

Processed: samba: CVE-2020-1472

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:4.9.5+dfsg-5+deb10u1
Bug #971048 [src:samba] samba: CVE-2020-1472
Marked as found in versions samba/2:4.9.5+dfsg-5+deb10u1.
> found -1 2:4.9.5+dfsg-5
Bug #971048 [src:samba] samba: CVE-2020-1472
Marked as found in versions samba/2:4.9.5+dfsg-5.
> found -1 2:4.5.16+dfsg-1+deb9u2
Bug #971048 [src:samba] samba: CVE-2020-1472
Marked as found in versions samba/2:4.5.16+dfsg-1+deb9u2.
> found -1 2:4.5.16+dfsg-1
Bug #971048 [src:samba] samba: CVE-2020-1472
Marked as found in versions samba/2:4.5.16+dfsg-1.

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

Processed: gnome-shell-extension-hard-disk-led: incompatible with GNOME Shell 3.38

[Debian Bug Tracking System]

Processing control commands:

> block 969321 by -1
Bug #969321 [release.debian.org] transition: GNOME 3.38, libmutter-7-0
969321 was blocked by: 971038 971040
969321 was not blocking any bugs.
Added blocking bug(s) of 969321: 971041

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

Bug#971041: gnome-shell-extension-hard-disk-led: incompatible with GNOME Shell 3.38

[Simon McVittie]

Package: gnome-shell-extension-hard-disk-led
Version: 19-1
Severity: grave
Tags: upstream bullseye sid
Justification: renders package unusable in unstable (as of today)
Control: block 969321 by -1

This extension doesn't seem to be compatible with Shell 3.38 (coming soon
to an unstable mirror near you, or already available in experimental). It
fails to load with this traceback:

JS ERROR: Extension harddisk...@bijidroid.gmail.com: Error: No property x_fill 
on StBin
init@/usr/share/gnome-shell/extensions/harddisk...@bijidroid.gmail.com/extension.js:32:14
_callExtensionInit@resource:///org/gnome/shell/ui/extensionSystem.js:428:50
loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:345:27
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:586:18
collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:28
_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:565:19
_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:595:18
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:626:18
init@resource:///org/gnome/shell/ui/extensionSystem.js:56:14
_initializeUI@resource:///org/gnome/shell/ui/main.js:269:22
start@resource:///org/gnome/shell/ui/main.js:159:5
@:1:47

If this is not straightforward to fix, then the extension should be
removed from testing when GNOME 3.38 migrates.

Regards,
smcv

Bug#970245: marked as done (gnome-core: gnome-core/s390x has unsatisfiable dependency)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 17:04:13 +
with message-id 
and subject line Bug#970245: fixed in gdm3 3.38.0-2
has caused the Debian Bug report #970245,
regarding gnome-core: gnome-core/s390x has unsatisfiable 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.)


-- 
970245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-core
Version: 1:3.30+3
Severity: serious

The last uploaded added the dependency on gdm3 back:

   * d/control.in: Remove special-case fallbacks for s390x
 gjs, gdm and gnome-shell are now available on s390x (although whether
 they have been successfully run there is anyone's guess), so we can pull
 in the full GNOME desktop on all release architectures again.

While the source package gdm3 built successfully on s390x, it does not
build the gdm3 binary there (even though it declares gdm to be available
on linux-any). From its debian/rules:

dh_options =
just_the_library = no
ifneq (,$(filter $(DEB_HOST_ARCH_CPU),s390x))
dh_options += -Ngdm3
just_the_library = yes
endif

Also verified on zelenka:

% dd-schroot-cmd -c sramacher-gnome apt-get install gnome-core
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnome-core : Depends: gdm3 (>= 3.30) but it is not installable
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gdm3
Source-Version: 3.38.0-2
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gdm3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Sep 2020 16:52:06 +0100
Source: gdm3
Architecture: source
Version: 3.38.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 970245
Changes:
 gdm3 (3.38.0-2) unstable; urgency=medium
 .
   * Team upload
   * d/rules: Set runtime configuration path.
 In Autotools, the default runtime configuration path used to be
 ${GDM_RUN_DIR}/custom.conf, but in the Meson build system the fallback
 changed to be the same as the custom.conf path in /etc (set to
 /etc/gdm3/daemon.conf in Debian for historical reasons).
 Explicitly set it to the path we used before switching to Meson, so
 that configuration changes by gdm-disable-wayland are temporary as
 intended, and do not persist to a subsequent boot.
   * Revert "debian/watch: Monitor unstable versions"
   * d/upstream/metadata: Add
   * Merge packaging from unstable
   * Release to unstable
 .
 gdm3 (3.38.0-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release
   * Remove patches that were applied upstream (in some cases differently)
   * Remove special case for s390x.
 gjs and gnome-shell now exist there, so we no longer need to avoid
 depending on them. In particular this makes the GNOME metapackages
 installable on that architecture again. (Closes: #970245)
 .
 gdm3 (3.37.90-2) experimental; urgency=medium
 .
   * Team upload
 .
   [ Simon McVittie ]
   * Add patch to remove deprecated StandardOutput=syslog from systemd unit
   * Build-Depend on systemd, for /usr/share/pkgconfig/systemd.pc
 .
   [ Iain Lane ]
   * debian/control: Bump depends on gnome-{session,settings-daemon,shell}
 We require the newly rearranged systemd units that are in these
 versions.
   * debian/control: Make gdm depend on gnome-session-common ≥ 3.37.0-2~
 This is where the 

Bug#971040: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency

[Simon McVittie]

Package: gnome-shell-extension-easyscreencast
Version: 1.1.0-2
Severity: grave
Justification: renders package unusable
Control: block 969321 by -1

GNOME Shell 3.38 is on its way into unstable, which makes
gnome-shell-extension-easyscreencast uninstallable. Please test with GNOME
Shell 3.38, and if possible upload a version that is compatible.

If it isn't possible to make this extension compatible, then this
extension will need to be removed from testing to let the new GNOME
release migrate.

A new version 1.2.0 seems to be available upstream. I don't know whether
it will work with 3.38, but it seems more likely than 1.1.0.

Thanks,
smcv

Processed: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency

[Debian Bug Tracking System]

Processing control commands:

> block 969321 by -1
Bug #969321 [release.debian.org] transition: GNOME 3.38, libmutter-7-0
969321 was blocked by: 971038
969321 was not blocking any bugs.
Added blocking bug(s) of 969321: 971040

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

Bug#969565: marked as done (python3-azure-cli: dependency unsatisfiable in sid and questionable in testing.)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 15:18:35 +
with message-id 
and subject line Bug#969565: fixed in azure-cli 2.11.1-1
has caused the Debian Bug report #969565,
regarding python3-azure-cli: dependency unsatisfiable in sid and questionable 
in testing.
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.)


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

Package: python3-azure-cli
Version: 2.10.1-1
Severity: serious

python3-azure-cli depends on python3-cryptography << 3.0.0 . In unstable this 
dependency is unsatisfiable
because python3-cryptography is now at version 3.1-1 .

In testing the dependency is strictly-speaking satisfiable because testing has 
version 3.0-1 of
python3-cryptography and per Debian version number comparision rules 3.0-1 << 
3.0.0, however it seems
unlikely that this was what was intended by the person writing the dependency.
--- End Message ---
--- Begin Message ---
Source: azure-cli
Source-Version: 2.11.1-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated azure-cli package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Sep 2020 14:49:48 +0100
Source: azure-cli
Architecture: source
Version: 2.11.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Luca Boccassi 
Closes: 969565
Changes:
 azure-cli (2.11.1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Luca Boccassi ]
   * Merge tag 'azure-cli-2.11.1' into debian/sid
   * Bump dependencies requirements for version 2.11.1
   * Drop antlr4_workaround.patch, merged upstream
   * Add crypto_dependency.patch to remove upper python3-cryptography
 version limit (Closes: #969565)
   * Skip new flaky tests
   * Add more tests and caches to d/not-installed
   * azure/cli/__init__.py is not installed anymore
Checksums-Sha1:
 2077b9c15b477d63981968ba1787387713ebc3bc 3014 azure-cli_2.11.1-1.dsc
 7fac4d9ffd0603438c60b2c3d4fd7e6ec3ff9394 43963703 azure-cli_2.11.1.orig.tar.gz
 7e3e2d2cfeb6ef9cb93abca88099dfbc4f614a06 6344 azure-cli_2.11.1-1.debian.tar.xz
 7d6c279c01d574d753c8d7dd2c471921406c6473 6942 
azure-cli_2.11.1-1_source.buildinfo
Checksums-Sha256:
 a3552c533c013ab34e8f7e4602cba263536958d9d5f7033f381e9d2f3e602a26 3014 
azure-cli_2.11.1-1.dsc
 2d5e5530daf643bcef9e6eb34afe1e8104a7c2b97046c9773efd904739d680f3 43963703 
azure-cli_2.11.1.orig.tar.gz
 8658211b524b5db642ee2fff99883258929cf438265715f2c1a18c574363b7a7 6344 
azure-cli_2.11.1-1.debian.tar.xz
 5e62a32a9a2c2afe6c07b8a27b15c41cd51b5ef80a87ca1e5ebf1bb54437e669 6942 
azure-cli_2.11.1-1_source.buildinfo
Files:
 3187dbe884b3b68ee3d3d5e4a84da942 3014 python optional azure-cli_2.11.1-1.dsc
 a2e99efc654dd319b58d143cd6bc8c8a 43963703 python optional 
azure-cli_2.11.1.orig.tar.gz
 f8930eff1b3be286369bd4576d2b841b 6344 python optional 
azure-cli_2.11.1-1.debian.tar.xz
 1ae3144adfe75cf57309fc1c9eabf87d 6942 python optional 
azure-cli_2.11.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAl9vUhYRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQSylmgFB4UWLpkgf+Nhpfjy87m7HSxcDjGXFYLuXPONyMdsXV
nM3gzXAK0ugugXShJ8JQNOHmzzeYkHDFEUTDC6f60+EY2gV/WHKwaQ/yS2pS5BpS
BnJEettT3jaRTnyUOSCYuch+jB4bEAI+d+ObAHsN4x3zYZGpDhBIDAYZsy01ChJe
fRKTwgFaW4ZBvfa26+bVRImG19XP1xN7xNhZCP41KD1vrO/ACVU1eCbFV1BOieAm
+cekxb8/pE8pC7yYEh02zC4LWlaR8KQm/RGVm1MDdq8K/+dzagZ794mxMUlKn+9w
LmGLwPfMW4lg5MzW5bopxbdcm8Ga8I+5zgVQDKDl9INcKsSnsnHTIQ==
=ozX4
-END PGP SIGNATURE End Message ---

Bug#969768: lib-io-socket-ip-perl: do not release with bullseye

[gregor herrmann]

Control: tag -1 + pending

On Mon, 07 Sep 2020 23:50:03 +0100, Dominic Hargreaves wrote:

> IO-Socket-IP is bundled with perl 5.30, so there is no need to ship
> this separately.

IO-Socket-IP 0.41 has been released, without the patch for #964902
but with some other changes:
https://metacpan.org/pod/IO::Socket::IP

IO::Socket::IP 0.41 is bundled with perl ony starting with v5.33.2,
which won't be in Debian any time soon.

I guess we should update libio-socket-ip-perl to 0.41 and close this
bug with the upload (and close #969967 in libtest-tcp-perl as well).

I've pushed libio-socket-ip-perl_0.41-1 to git but wanted to give
others a chance to comment before the actual upload.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Status Quo: Anniversary Waltz Part 2 (Medley)


signature.asc
Description: Digital Signature

Processed: Re: Bug#969768: lib-io-socket-ip-perl: do not release with bullseye

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #969768 [libio-socket-ip-perl] libio-socket-ip-perl: do not release with 
bullseye
Added tag(s) pending.

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

Processed: found 969768 in 0.39-2

[Debian Bug Tracking System]

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

> found 969768 0.39-2
Bug #969768 [libio-socket-ip-perl] libio-socket-ip-perl: do not release with 
bullseye
Marked as found in versions libio-socket-ip-perl/0.39-2.
> thanks
Stopping processing here.

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

Processed: block 969967 with 969768

[Debian Bug Tracking System]

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

> block 969967 with 969768
Bug #969967 [libtest-tcp-perl] libtest-tcp-perl: bogus dependency 
libio-socket-ip-perl (>= 0.39-3~)
969967 was not blocked by any bugs.
969967 was not blocking any bugs.
Added blocking bug(s) of 969967: 969768
> thanks
Stopping processing here.

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

Bug#957191: marked as done (fact++: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 13:33:24 +
with message-id 
and subject line Bug#957191: fixed in fact++ 1.6.5~dfsg-3
has caused the Debian Bug report #957191,
regarding fact++: ftbfs with GCC-10
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.)


-- 
957191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fact++
Version: 1.6.5~dfsg-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/fact++_1.6.5~dfsg-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
ConceptWithDep.h:43:2: note: because ‘ConceptWDep’ has user-provided 
‘ConceptWDep::ConceptWDep(const ConceptWDep&)’
   43 |  ConceptWDep ( const ConceptWDep& c ) : Concept(c.Concept), 
depSet(c.depSet) {}
  |  ^~~
g++  -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wdate-time -D_FORTIFY_SOURCE=2 -ffast-math 
-W -Wall -Wextra -O3 -fomit-frame-pointer -fPIC  -o obj/Actor.o Actor.cpp
g++  -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wdate-time -D_FORTIFY_SOURCE=2 -ffast-math 
-W -Wall -Wextra -O3 -fomit-frame-pointer -fPIC  -o obj/tDag2Interface.o 
tDag2Interface.cpp
g++  -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wdate-time -D_FORTIFY_SOURCE=2 -ffast-math 
-W -Wall -Wextra -O3 -fomit-frame-pointer -fPIC  -o obj/tDLAxiom.o tDLAxiom.cpp
g++  -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wdate-time -D_FORTIFY_SOURCE=2 -ffast-math 
-W -Wall -Wextra -O3 -fomit-frame-pointer -fPIC  -o obj/AtomicDecomposer.o 
AtomicDecomposer.cpp
AtomicDecomposer.cpp: In member function ‘AOStructure* 
AtomicDecomposer::getAOS(TOntology*, ModuleType)’:
AtomicDecomposer.cpp:143:6: error: no match for ‘operator<<’ (operand types are 
‘std::ostream’ {aka ‘std::basic_ostream’} and ‘const char [13]’)
  143 |   LL << "\nThere were " << pModularizer->getNNonLocal() << " non-local 
axioms out of " << pModularizer->getNChecks() << " totally checked\n";
  |   ~~ ^~ ~~~
  |   | |
  |   | const char [13]
  |   std::ostream {aka std::basic_ostream}
In file included from /usr/include/c++/10/string:55,
 from tDLExpression.h:24,
 from tDLAxiom.h:23,
 from tOntologyAtom.h:26,
 from AtomicDecomposer.h:23,
 from AtomicDecomposer.cpp:20:
/usr/include/c++/10/bits/basic_string.h:6428:5: note: candidate: 
‘template std::basic_ostream<_CharT, 
_Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&)’
 6428 | operator<<(basic_ostream<_CharT, _Traits>& __os,
  | ^~~~
/usr/include/c++/10/bits/basic_string.h:6428:5: note:   template argument 
deduction/substitution failed:
AtomicDecomposer.cpp:143:9: note:   mismatched types ‘const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>’ and ‘const char [13]’
  143 |   LL << "\nThere were " << pModularizer->getNNonLocal() << " non-local 
axioms out of " << pModularizer->getNChecks() << " totally checked\n";
  | ^~~
In file included from /usr/include/c++/10/bits/ios_base.h:46,
 from /usr/include/c++/10/streambuf:41,
 from /usr/include/c++/10/bits/streambuf_iterator.h:35,
 from 

Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies

[Markus Koschany]

Am 26.09.20 um 10:27 schrieb Emmanuel Bourg:
> On 25/09/2020 13:50, Markus Koschany wrote:
> 
>> Why did you upgrade hibernate-validator to version 5.x when
>> no other package in Debian requires it? Wouldn't it have been 
>> simpler to revert the upgrade instead of creating a separate
>> hibernate-validator4 package?
> 
> The version 5.x is a prerequisite to upgrade Spring to the next major
> release. Also the version 4.x is no longer supported and security issues
> are frequently reported. The idea is to use libhibernate-validator4-java
> as a transitional package until all reverse dependencies are updated to
> use the version 5.x.

That sounds like a sensible reason to upgrade a package. Though when I
look closer into the details I find only four reported security
vulnerabilities in the past six years. The last two in 2019 and 2020 did
only affect the 5.x and later versions specifically which is rather an
argument against upgrading hibernate-validator.

So the real reason for 5.x is to upgrade Spring which is also fine.
However the update has not materialized so far but in the meantime
pdfsam was broken in two Ubuntu releases and unstable. I would recommend
to upload such a package to experimental first or release it to unstable
when the complete work is done. I believe this all could have been
avoided if you had outlined your goals beforehand or if you had
responded to this bug report in time. Then we both could actually seek
for a solution to make this work. The current situation is a bit
demotivating though because I don't want to guess why something is
broken and I don't want to invest time to clean up the fallout when the
key problem is communication.

I will switch pdfsam to use libhibernator-validator4-java now but I can
only address this problem when libsejda-commons-java has been approved
by the ftp team. This may take a while.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#968681: [Pkg-javascript-devel] Bug#968681: nodejs: regresses in ppc64el ( node-create-hash, node-crypto-browserify, node-sha.js)

[Jérémy Lal]

Le sam. 26 sept. 2020 à 14:18, Gianfranco Costamagna <
locutusofb...@debian.org> a écrit :

> Hello,
>
> On Wed, 19 Aug 2020 22:39:03 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?= <
> kapo...@melix.org> wrote:
> > Le mer. 19 août 2020 à 21:12, Gianfranco Costamagna <
> > locutusofb...@debian.org> a écrit :
> >
> > > Source: nodejs
> > > Version: 12.18.2~dfsg-1
> > > Severity: serious
> > >
> > > Hello, looks like node-create-hask, node-crypto-browserify, node-sha.js
> > > have autopkgtests failures on ppc64el.
> > >
> > > there might be an upstream patch according to Ubuntu bug [1]  and v8
> > > commits
> > >
> > >
> > >
> https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-crypto-browserify/6740061/log.gz
> > >
> > >
> > >
> https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-sha.js/6740057/log.gz
> > >
> > >
> > >
> https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-create-hash/6738537/log.gz
> > >
> > >
> > > the attached diff (based on upstream changes) might help in fixing the
> > > failures.
> > >
> > > [1]
> > >
> https://bugs.launchpad.net/ubuntu/+source/node-create-hash/+bug/1887144
> > >
> > > I just uploaded in Ubuntu, will see in 24h or so if the problem is
> fixed
> > > or not.
> > >
> >
> > Thanks, i'll apply the patch later this week, then.
> >
> > Jérémy
>
>
> ping please?
>

Oops sorry i really thought i dealt with it :(
Anyway now this fix has been backported to upstream 12.x
and they planned a release in a few days:
https://github.com/nodejs/Release/issues/494

Jérémy

Bug#968681: [Pkg-javascript-devel] Bug#968681: nodejs: regresses in ppc64el ( node-create-hash, node-crypto-browserify, node-sha.js)

[Gianfranco Costamagna]

Hello,

On Wed, 19 Aug 2020 22:39:03 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?= 
 wrote:
> Le mer. 19 août 2020 à 21:12, Gianfranco Costamagna <
> locutusofb...@debian.org> a écrit :
> 
> > Source: nodejs
> > Version: 12.18.2~dfsg-1
> > Severity: serious
> >
> > Hello, looks like node-create-hask, node-crypto-browserify, node-sha.js
> > have autopkgtests failures on ppc64el.
> >
> > there might be an upstream patch according to Ubuntu bug [1]  and v8
> > commits
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-crypto-browserify/6740061/log.gz
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-sha.js/6740057/log.gz
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-create-hash/6738537/log.gz
> >
> >
> > the attached diff (based on upstream changes) might help in fixing the
> > failures.
> >
> > [1]
> > https://bugs.launchpad.net/ubuntu/+source/node-create-hash/+bug/1887144
> >
> > I just uploaded in Ubuntu, will see in 24h or so if the problem is fixed
> > or not.
> >
> 
> Thanks, i'll apply the patch later this week, then.
> 
> Jérémy


ping please?

G.

Bug#970901: black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

[Chris Lamb]

tags 970901 + patch
thanks

Hi,

> black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

The following patch works for me, but there is likely a cleaner
solution; seems like the Black package maintainers are doing special
things with the version handling and I am missing some nuance.

  --- a/debian/rules
  +++ b/debian/rules
  @@ -16,6 +16,8 @@ export VERSION=$(shell dpkg-parsechangelog -S Version|cut 
-d- -f1)

   %:
  echo "version = '$(VERSION)'" > _black_version.py
  +   mkdir -p src
  +   cp _black_version.py src/
  dh $@ --with sphinxdoc,python3 --buildsystem=pybuild

   override_dh_auto_build:


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-diff --git a/debian/rules b/debian/rules
index 09908f4..1a70969 100755
--- a/debian/rules
+++ b/debian/rules
@@ -16,6 +16,8 @@ export VERSION=$(shell dpkg-parsechangelog -S Version|cut -d- 
-f1)
 
 %:
echo "version = '$(VERSION)'" > _black_version.py
+   mkdir -p src
+   cp _black_version.py src/
dh $@ --with sphinxdoc,python3 --buildsystem=pybuild
 
 override_dh_auto_build:

Processed: Re: black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

[Debian Bug Tracking System]

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

> tags 970901 + patch
Bug #970901 [black] black: cannot run, "ModuleNotFoundError: No module named 
'_black_version'"
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#970900: marked as done (depends on non-existing qml-module-qtqml-modules2 (typo?))

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 11:34:09 +
with message-id 
and subject line Bug#970900: fixed in nextcloud-desktop 3.0.1-3
has caused the Debian Bug report #970900,
regarding depends on non-existing qml-module-qtqml-modules2 (typo?)
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.)


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

Dear Maintainer,

now with the added dependencies to fix #969576 it's uninstallable on sid.

qml-module-qtqml-modules2 doestn't exist.
But maybe it's a typo and you actually meant qml-module-qtqml-models2? 

Kind regards
Felix Zielcke

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nextcloud-desktop depends on:
ii  libc6 2.31-3
ii  libcloudproviders00.3.0-3
ii  libgcc-s1 10.2.0-9
ii  libglib2.0-0  2.66.0-2
ii  libnextcloudsync0 3.0.1-1
ii  libqt5core5a  5.14.2+dfsg-6
ii  libqt5dbus5   5.14.2+dfsg-6
ii  libqt5gui55.14.2+dfsg-6
ii  libqt5keychain1   0.10.0-1
ii  libqt5network55.14.2+dfsg-6
ii  libqt5qml55.14.2+dfsg-3
ii  libqt5quick5  5.14.2+dfsg-3
ii  libqt5quickcontrols2-55.14.2+dfsg-2
ii  libqt5sql5-sqlite 5.14.2+dfsg-6
ii  libqt5svg55.14.2-2
ii  libqt5webenginecore5  5.14.2+dfsg1-5
ii  libqt5webenginewidgets5   5.14.2+dfsg1-5
ii  libqt5webkit5 5.212.0~alpha4-5
ii  libqt5widgets55.14.2+dfsg-6
ii  libstdc++610.2.0-9
ii  nextcloud-desktop-common  3.0.1-2
ii  nextcloud-desktop-l10n3.0.1-2

Versions of packages nextcloud-desktop recommends:
pn  nextcloud-desktop-doc  

nextcloud-desktop suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nextcloud-desktop
Source-Version: 3.0.1-3
Done: =?utf-8?q?Sandro_Knau=C3=9F?= 

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

Debian distribution maintenance software
pp.
Sandro Knauß  (supplier of updated nextcloud-desktop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Sep 2020 13:18:40 +0200
Source: nextcloud-desktop
Architecture: source
Version: 3.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: ownCloud for Debian maintainers 

Changed-By: Sandro Knauß 
Closes: 970900
Changes:
 nextcloud-desktop (3.0.1-3) unstable; urgency=medium
 .
   * Fix typo: qml-module-qtqml-modules2 -> qml-module-qtqml-models2.
 (Closes: #970900)
Checksums-Sha1:
 23dfcd9c9f326af555da14d1bd5988abd347d886 3355 nextcloud-desktop_3.0.1-3.dsc
 e6a0d8f41ff19f9bac2f3c328ad2fb665dc63021 14744 
nextcloud-desktop_3.0.1-3.debian.tar.xz
 276d1a9108b29a41b5de037eca7446a3f2c07c71 19618 
nextcloud-desktop_3.0.1-3_source.buildinfo
Checksums-Sha256:
 959419fe582434c93001658acf84743fb075b9bf0513d477715469edc1e7238c 3355 
nextcloud-desktop_3.0.1-3.dsc
 283c90f0de028eb586d627d7c3385c04b479128f11dca481a8d6b519f63021cf 14744 
nextcloud-desktop_3.0.1-3.debian.tar.xz
 0317cf085997f5086f8ed7a549db5ec27e3c20048175cbd02026dc572ba0e7f5 19618 
nextcloud-desktop_3.0.1-3_source.buildinfo
Files:
 4b8a10ecc26dfc15b3e5c32aeb78978d 3355 net optional 
nextcloud-desktop_3.0.1-3.dsc
 1d4f6aa0940343dac810ff29b6617b53 14744 net optional 
nextcloud-desktop_3.0.1-3.debian.tar.xz
 8c5ce71d25e9c83cd8e91982ffa919fa 19618 net optional 
nextcloud-desktop_3.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#970900: marked as pending in nextcloud-desktop

[Hefee]

Control: tag -1 pending

Hello,

Bug #970900 in nextcloud-desktop 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/owncloud-team/nextcloud-desktop/-/commit/5bc3fcd39b4b2bba1e3997859438fc0fd536eb58


Fix typo: qml-module-qtqml-modules2 -> qml-module-qtqml-models2.

Closes: #970900


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/970900

Processed: Bug#970900 marked as pending in nextcloud-desktop

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #970900 [nextcloud-desktop] depends on non-existing 
qml-module-qtqml-modules2 (typo?)
Added tag(s) pending.

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

Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

[José Luis Blanco-Claraco]

On Sat, Sep 26, 2020 at 3:30 AM Scott Talbert  wrote:
> If you don't mind, please do a new package upload to mentors.

Sure! Done here:
https://mentors.debian.net/debian/pool/main/m/mrpt/mrpt_2.1.0-2.dsc

Best,
JL

Processed: ITP: node-rollup-plugin-inject -- Scan modules for global variables and inject import statements

[Debian Bug Tracking System]

Processing control commands:

> block 970550 by -1
Bug #970550 [libjs-autoprefixer] diaspora installation fails with 
ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined
970550 was not blocked by any bugs.
970550 was not blocking any bugs.
Added blocking bug(s) of 970550: 971020

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

Bug#971019: accidental chaining of debconf commands

[Wilco Baan Hofman]

Package: cdebconf
Version: 0.249
Severity: critical

I have a problem with the debian installer, at the finish-install stage
in the udeb clock-setup.

The following code path produces a strange protocol interaction:


if db_fget clock-setup/utc seen && [ "$RET" = true ]; then
# keep preseeded value
:
else
probed=""

if arch_has_os_needing_local_clock; then
# os-prober may not yet be installed...
anna-install os-prober-udeb || true

probed=$(os-prober) || true

if [ -z "$probed" ]; then
# installing the only OS, so use UTC
db_set clock-setup/utc true
pri=low
fi
fi

db_input $pri clock-setup/utc || true
if ! db_go; then
|   exit 10 # back to main menu
fi

The interaction in the syslog during install (manually copied from screen):
finish-install: info: Running /usr/lib/finish-install.d/10clock-setup
debconf: --> FGET clock-setup/utc seen
debconf: <-- 0 true
debconf: --> SET clock-setup/utc true INPUT low clock-setup/utc
debconf: <-- 0 value set
debconf: --> GO
debconf: <-- 0 ok
debconf: --> GET clock/setup/utc
debconf: <-- 0 true INPUT low clock-setup/utc
debconf: --> GET clock-setup/system-time-changed
debconf: <-- 0 false
finish-install: /usr/lib/finish-install.d/10clock-setup: return: line
46: illegal number: INPUT
finish-install: warning: /usr/lib/finish-install.d/10clock-setup
returned error code 2


For reproducing the error if that's required:
This is a preseeded Debian Buster install on VMWare ESXi, relevant
preseed config:

### Clock and timezone setup
# Controls whether or not the hardware clock is set to UTC.
d-i clock-setup/utc boolean true

# You may set this to any valid setting for $TZ; see the contents of
# /usr/share/zoneinfo/ for valid values.
d-i time/zone string Europe/Amsterdam

# Controls whether to use NTP to set the clock during the install
d-i clock-setup/ntp boolean true
# NTP server to use. The default is almost always fine here.
#d-i clock-setup/ntp-server string ntp.example.org


I can't really see why this path would be hit, "db_fget clock-setup/utc
seen" should return true and this whole thing should be skipped, but
somehow that is not how it works out.. and the debconf confmodule just
chains 2 commands together without any separation or wait time, causing
an error during finish-install, effectively halting all installs.

seems like either a clear separator is missing (newline?) or a buffer
must be flushed after every SET..

Kind regards,

Wilco Baan Hofman

Bug#971018: libgnatcoll-db: FTBFS on mips(64)el with assembler message: branch out of range

[Nicolas Boulenguez]

Source: libgnatcoll-db
Version: 20.0-1
Severity: serious
Justification: fails to build from scratch on previously built architectures

Hello.

libgnatcoll-db/20.0-1 in experimental fails to build on
mipsel and mips64el with the following messages [1].
  /tmp/ccl8IVnY.s: Assembler messages:
  /tmp/ccl8IVnY.s:692755: Error: branch out of range
  /tmp/ccl8IVnY.s:693545: Error: branch out of range
  /tmp/ccl8IVnY.s:693669: Error: branch out of range

The problem seems related to a previous bug [2] with similar symptoms [3].
  xref/gnatcoll-xref.adb: In function ‘GNATCOLL.XREF’:
  xref/gnatcoll-xref.adb:40:1: note: variable tracking size limit exceeded with 
‘-fvar-tracking-assignments’, retrying without
  Assembler messages:
  678119: Error: branch out of range

CFLAGS+=-mxgot has fixed the issue then, but does not seem sufficient
anymore.

Any advice would be welcome.

[1] 
https://buildd.debian.org/status/package.php?p=libgnatcoll-db=experimental
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953069
[3] 
https://buildd.debian.org/status/fetch.php?pkg=libgnatcoll-db=mipsel=19.2-2=1584014543=0

Bug#970910: [Pkg-javascript-devel] Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

[Gianfranco Costamagna]

Hello,

On Sat, 26 Sep 2020 08:41:38 + (UTC) Gianfranco Costamagna 
 wrote:
> Hello,
> 
> >debian/tests/autopkgtest-pkg-nodejs.conf contains
> >
> >  "extra_depends=mocha, node-tape, node-rollup-plugin-json (>= 4.1.0)"
> >
> >which should be enough for autodep8 ≥ 0.23. If you use autodep8 ≥ 0.23,
> >this bug should be reassigned to autodep8.
> 
> 
> interesting, I don't see autodep8 installed in both Debian and Ubuntu, but 
> maybe its outside the build log (of course)
> https://autopkgtest.ubuntu.com/packages/n/node-rollup-plugin-babel/groovy/amd64
> 
> Do you have any clue?
> 
> Gianfranco
> 
> 

I confirm it works on my machine after updating autodep8.

Thanks for the help!
I hope Ubuntu folks will update autodep8 soon too.
(for now I workarounded adding the 3 dependencies as build-deps)

G.

Processed: forcibly merging 744113 934191

[Debian Bug Tracking System]

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

> forcemerge 744113 934191
Bug #744113 [ftp.debian.org] don't include uploaded binary packages (build on 
developer machines) in the archive
Bug #934191 [ftp.debian.org] ftp.debian.org: Should reject/ignore/auto-binNMU 
binary uploads
Severity set to 'normal' from 'serious'
Merged 744113 934191
> thanks
Stopping processing here.

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

Bug#953426: marked as done (python-apt: Hasjes problem)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2020 11:24:24 +0200
with message-id <87y2kw99h3@43-1.org>
and subject line Re: Bug#953426: python-apt: Hasjes problem
has caused the Debian Bug report #953426,
regarding python-apt: Hasjes problem
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.)


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

Dear Maintainer,

Probably related that now apt use libgcrypt.

Output come from dak. Bug should be reassigned to ftp.debian.org is needed.


dak process-upload -a -p -d 

dak_1.0.db122~20200307.git9dac010a-dmo1_amd64.changes

dak (1.0.db122~20200307.git9dac010a-dmo1) unstable; urgency=medium
 .
   * New upstream release.



Reason:
Processing raised an exception: 'apt_pkg.Hashes' object has no attribute 'md5'.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/daklib/archive.py", line 1019, in check
chk().check(self)
  File "/usr/lib/python2.7/dist-packages/daklib/checks.py", line 146, in check
self._check_hashes(upload, changes.filename, changes.files.itervalues())
  File "/usr/lib/python2.7/dist-packages/daklib/checks.py", line 179, in 
_check_hashes
f.check(upload.directory)
  File "/usr/lib/python2.7/dist-packages/daklib/upload.py", line 174, in check
self.check_fh(fh)
  File "/usr/lib/python2.7/dist-packages/daklib/upload.py", line 188, in 
check_fh
if hashes.md5 != self.md5sum:
AttributeError: 'apt_pkg.Hashes' object has no attribute 'md5'


Christian

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

Kernel: Linux 4.19.108 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-apt depends on:
ii  dirmngr2.2.19-2
ii  gnupg  2.2.19-2
ii  libapt-pkg6.0  2.0.0
ii  libc6  2.29-10
ii  libgcc-s1  10-20200304-1
ii  libstdc++6 10-20200304-1
ii  python-apt-common  1.9.10
ii  python22.7.17-2

Versions of packages python-apt recommends:
ii  iso-codes4.4-1
ii  lsb-release  11.1.0
ii  xz-utils 5.2.4-1+b1

Versions of packages python-apt suggests:
ii  apt 2.0.0
pn  python-apt-dbg  
pn  python-apt-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: retitle -1 dak: support new Hashes interface in python-apt

Hi,

support for the new interface in testing/unstable's version of
python-apt was added recently[1].

Ansgar

  [1]: 
https://salsa.debian.org/ftp-team/dak/-/commit/e43972358b6c8d50bf09d469015af954255e2f66--- End Message ---

Bug#970910: [Pkg-javascript-devel] Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

[Gianfranco Costamagna]

Hello,

>debian/tests/autopkgtest-pkg-nodejs.conf contains
>
>  "extra_depends=mocha, node-tape, node-rollup-plugin-json (>= 4.1.0)"
>
>which should be enough for autodep8 ≥ 0.23. If you use autodep8 ≥ 0.23,
>this bug should be reassigned to autodep8.


interesting, I don't see autodep8 installed in both Debian and Ubuntu, but 
maybe its outside the build log (of course)
https://autopkgtest.ubuntu.com/packages/n/node-rollup-plugin-babel/groovy/amd64

Do you have any clue?

Gianfranco

Processed: RFS: vim-ultisnips/3.1-3.1 [NMU] [RC] -- snippet solution for Vim

[Debian Bug Tracking System]

Processing control commands:

> block 938777 by -1
Bug #938777 [src:vim-ultisnips] vim-ultisnips: Python2 removal in sid/bullseye
938777 was not blocked by any bugs.
938777 was blocking: 937695
Added blocking bug(s) of 938777: 971015

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

Processed: close 970265

[Debian Bug Tracking System]

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

> close 970265
Bug #970265 [src:python3.8] python3.8: FTBFS on arch:all, causing python3.8-doc 
to be unavailable and python3-doc uninstallable
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies

[Emmanuel Bourg]

On 25/09/2020 13:50, Markus Koschany wrote:

> Why did you upgrade hibernate-validator to version 5.x when
> no other package in Debian requires it? Wouldn't it have been 
> simpler to revert the upgrade instead of creating a separate
> hibernate-validator4 package?

The version 5.x is a prerequisite to upgrade Spring to the next major
release. Also the version 4.x is no longer supported and security issues
are frequently reported. The idea is to use libhibernate-validator4-java
as a transitional package until all reverse dependencies are updated to
use the version 5.x.

Emmanuel Bourg

Bug#917485: ckermit: relax openssl version check or tighten libssl1.x.y dependencies

[Sébastien Villemot]

Control: notfound -1 305~alpha02-1
Control: close -1

Hi Paul,

There was no need to reopen this bug. The metadata was correct.

The bug was fixed by a patch in 302-5.3+deb9u1. The reintroduction of
the package, even if it no longer contains the patch, did not
reintroduce the bug, because upstream fixed it in another way: the
dynamic check against the version of OpenSSL has been improved, in the
sense that it accept changes in the patchlevel version (e.g. if the
package was compiled against OpenSSL 1.1.0, the dynamic check will
allow execution against 1.1.1, since there is ABI stability).

Closing again and fixing versions accordingly.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Processed: Re: Bug#917485: ckermit: relax openssl version check or tighten libssl1.x.y dependencies

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 305~alpha02-1
Bug #917485 [ckermit] ckermit: relax openssl version check or tighten 
libssl1.x.y dependencies
No longer marked as found in versions ckermit/305~alpha02-1.
> close -1
Bug #917485 [ckermit] ckermit: relax openssl version check or tighten 
libssl1.x.y dependencies
Marked Bug as done

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