Bug#987568: open-iscsi-udeb: uninstallable udeb: non-udeb dependencies

[Cyril Brulebois]

Hi,

Ritesh Raj Sarraf  (2021-04-30):
> The upload I prepped failed on some of the architectures.
> https://buildd.debian.org/status/logs.php?pkg=open-iscsi=2.1.3-3

It's lacking a push to the Git repository (git fetch didn't get anything
new from a few days ago).

> In d/control, there is:
> 
> ```
> Package: open-iscsi-udeb
> # Note: the (virtual) udeb package scsi-modules (provided by different
> #   linux kernel udebs) must exist for these architectures - so
> #   check that before adding them to this list; the other
> #   scsi-(core|common|...)-modules are NOT sufficient!
> Architecture: amd64 arm64 armhf i386 ia64 mips mipsel powerpc ppc64
> ppc64el s390x
> Section: debian-installer
> Package-Type: udeb
> ```
> 
> 
> The udeb package was introduced by Colin Watson from Ubuntu. I extended
> the architecture list, based on the supported architectures by d-i. But
> I really don't use or test this functionality of the package.
> 
> 
> How would you like to see this fixed Cyril ?
> 
> The easiest option, if d-i supports, would be to extend architecture
> list to: `linux-any`, keeping it in line with what the actual open-
> iscsi package supports.

Yes, I think that would be a good idea, so that you don't have to keep
the list in sync between debian/control and debian/rules. We don't have
many examples of packages maintained by the d-i team that use it, but
at least src:haveged and src:systemd have similar udebs (after all, that
only matters at build-time, d-i only sees the results of the build).

Regarding your conditional, you could check whether you're building for
linux (once you switch to linux-any) or you could check whether the udeb
is being built: dh_listpackages (-a) can be use to determine that.


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


signature.asc
Description: PGP signature

Bug#936935: libvirt-sandbox: Python2 removal in sid/bullseye

[Christoph Anton Mitterer]

Hey.

AFAICS, all python script have been adapted to Python3 upstream (or
dropped)... so I guess this could be solved by upgrading to the current
version.


Cheers,
Chris.

Bug#987858: FTBFS: dh_makeshlibs: error: The udeb open-iscsi-udeb does not contain any shared libraries but --add-udeb=open-iscsi-udeb was passed!?

[Aurelien Jarno]

Package: open-iscsi
Version: 2.1.3-3
Severity: serious
Tags: d-i ftbfs patch
Justification: fails to build from source (but built successfully in the past)

open-iscsi fails to build on mips64el:

| dh_missing --fail-missing
| make[1]: Leaving directory '/<>'
|dh_strip -a
|debian/rules override_dh_makeshlibs
| make[1]: Entering directory '/<>'
| dh_makeshlibs --add-udeb=open-iscsi-udeb
| dh_makeshlibs: error: The udeb open-iscsi-udeb does not contain any shared 
libraries but --add-udeb=open-iscsi-udeb was passed!?
| make[1]: *** [debian/rules:104: override_dh_makeshlibs] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:13: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build-log is available here:
https://buildd.debian.org/status/fetch.php?pkg=open-iscsi=mips64el=2.1.3-3=1619796879=0

This happens as the open-iscsi-udeb package is not build on this
architecture. The reason for that is indicated in the debian/control
file:

| Package: open-iscsi-udeb
| # Note: the (virtual) udeb package scsi-modules (provided by different
| #   linux kernel udebs) must exist for these architectures - so
| #   check that before adding them to this list; the other
| #   scsi-(core|common|...)-modules are NOT sufficient!
| Architecture: amd64 arm64 armhf i386 ia64 mips mipsel powerpc ppc64 ppc64el 
s390x

However it happens that mips64el do have such scsi-module packages
containing the iscsi and libiscsi modules:
- 
https://packages.debian.org/search?suite=sid=mips64el=scsi-modules
 

At least the following architectures also have this package:
- alpha: 
https://packages.debian.org/search?suite=sid=alpha=scsi-modules
- hppa: 
https://packages.debian.org/search?suite=sid=hppa=scsi-modules
- m68k: 
https://packages.debian.org/search?suite=sid=m68k=scsi-modules
- riscv64: 
https://packages.debian.org/search?suite=sid=riscv64=scsi-modules 
- sparc64: 
https://packages.debian.org/search?suite=sid=sparc64=scsi-modules

The patch below therefore updates the debian/control file so that
open-iscsi builds correctly on those architecture:

--- open-iscsi-2.1.3/debian/control
+++ open-iscsi-2.1.3/debian/control
@@ -139,7 +139,7 @@
 #   linux kernel udebs) must exist for these architectures - so
 #   check that before adding them to this list; the other
 #   scsi-(core|common|...)-modules are NOT sufficient!
-Architecture: amd64 arm64 armhf i386 ia64 mips mipsel powerpc ppc64 ppc64el 
s390x
+Architecture: alpha amd64 arm64 armhf hppa i386 ia64 m68k mips mipsel mips64el 
powerpc ppc64 ppc64el riscv64 s390x sparc64
 Section: debian-installer
 Package-Type: udeb
 Depends: ${misc:Depends},


Regards,
Aurelien

Bug#986286: marked as done (diaspora-installer: fails to install: Your bundle is locked to mimemagic (0.3.5), but that version could not be found)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 23:03:22 +
with message-id 
and subject line Bug#986286: fixed in diaspora-installer 0.7.14.0+debian2+nmu2
has caused the Debian Bug report #986286,
regarding diaspora-installer: fails to install: Your bundle is locked to 
mimemagic (0.3.5), but that version could not be found
to be marked as done.

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

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


-- 
986286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora-installer
Version: 0.7.14.0+debian2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Setting up diaspora-installer (0.7.14.0+debian2) ...
  Download diaspora tarball version 0.7.14.0 from github.com...
  --2021-04-02 11:03:54--  
https://github.com/diaspora/diaspora/archive/v0.7.14.0.tar.gz
  Resolving github.com (github.com)... 140.82.121.4
  Connecting to github.com (github.com)|140.82.121.4|:443... connected.
  HTTP request sent, awaiting response... 302 Found
  Location: https://codeload.github.com/diaspora/diaspora/tar.gz/v0.7.14.0 
[following]
  --2021-04-02 11:03:54--  
https://codeload.github.com/diaspora/diaspora/tar.gz/v0.7.14.0
  Resolving codeload.github.com (codeload.github.com)... 140.82.121.9
  Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443... 
connected.
  HTTP request sent, awaiting response... 200 OK
  Length: unspecified [application/x-gzip]
  Saving to: '/var/cache/diaspora-installer/diaspora-0.7.14.0.tar.gz'
  
  
  /var/cach [<=> ]   0  --.-KB/s   
 /var/cache [ <=>]   1.45M  7.11MB/s   
/var/cache/ [  <=>   ]   3.79M  9.36MB/s   
   /var/cache/d [   <=>  ]   8.59M  14.2MB/s   
/var/cache/diaspora [<=> ]   9.45M  14.0MB/sin 0.7s
  
  2021-04-02 11:03:55 (14.0 MB/s) - 
'/var/cache/diaspora-installer/diaspora-0.7.14.0.tar.gz' saved [9911008]
  
  Checking integrity of download...
  /var/cache/diaspora-installer/diaspora-0.7.14.0.tar.gz: OK
  Extracting files...
  Copying files to /usr/share/diaspora...
  diaspora archive to copy: diaspora-0.7.14.0
  Copying source tarball to /var/lib/diaspora/public...
  Setting up environment varibales...
  Using /etc/diaspora/diaspora.conf...
  DB_NAME=diaspora_production
  Using system bundler...
  Installing gems with rubygems ...
  [ESC][33m[DEPRECATED] The `--frozen` flag is deprecated because it relies on 
being remembered across bundler invocations, which bundler will no longer do in 
future versions. Instead please use `bundle config set --local frozen 'true'`, 
and stop using this flag[ESC][0m
  [ESC][33m[DEPRECATED] The `--path` flag is deprecated because it relies on 
being remembered across bundler invocations, which bundler will no longer do in 
future versions. Instead please use `bundle config set --local path 
'vendor/bundle'`, and stop using this flag[ESC][0m
  [ESC][33m[DEPRECATED] The `--without` flag is deprecated because it relies on 
being remembered across bundler invocations, which bundler will no longer do in 
future versions. Instead please use `bundle config set --local without 
'development test'`, and stop using this flag[ESC][0m
  [ESC][33m[DEPRECATED] The `--with` flag is deprecated because it relies on 
being remembered across bundler invocations, which bundler will no longer do in 
future versions. Instead please use `bundle config set --local with 
'postgresql'`, and stop using this flag[ESC][0m
  Fetching gem metadata from https://gems.diasporafoundation.org/..
  Fetching gem metadata from https://rubygems.org/..
  [ESC][31mYour bundle is locked to mimemagic (0.3.5), but that version could 
not be found
  in any of the sources listed in your Gemfile. If you haven't changed sources,
  that means the author of mimemagic (0.3.5) has removed it. You'll need to 
update
  your bundle to a version other than mimemagic (0.3.5) that hasn't been removed
  in order to install.[ESC][0m
  dpkg: error processing package diaspora-installer (--configure):
   installed diaspora-installer package post-installation script subprocess 
returned error exit status 7
  Processing triggers for libc-bin (2.31-11) ...
  Processing triggers for ca-certificates (20210119) ...

Processed (with 1 error): unacrhive, reopen, mark found #982904

[Debian Bug Tracking System]

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

> unarchive 982904
> found 982904 1.3.0~git20190125.440b173+dfsg-2
Bug #982904 {Done: Christopher Knadle } [src:mumble] 
mumble: CVE-2021-27229
Ignoring request to alter found versions of bug #982904 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed (with 1 error): unacrhive, reopen, mark found #982904

[Debian Bug Tracking System]

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

> unarchive 982904
> found 982904 1.3.0~git20190125.440b173+dfsg-2
Bug #982904 {Done: Christopher Knadle } [src:mumble] 
mumble: CVE-2021-27229
Marked as found in versions mumble/1.3.0~git20190125.440b173+dfsg-2.
> thanks
Stopping processing here.

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

Bug#982904: mumble: CVE-2021-27229

[Chris Knadle]

Note: for the three messages recently sent (Benedikt, Salvatorie, Chris/me) that 
have recently been sent, none went to #982904 because the bug had been archived. 
I've unarchived the bug since fixing it for Buster is still pending.


  -- Chris

--
Chris Knadle
chris.kna...@coredump.us

Processed: unarchive #982904

[Debian Bug Tracking System]

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

> unarchive 982904
Bug #982904 {Done: Christopher Knadle } [src:mumble] 
mumble: CVE-2021-27229
Unarchived Bug 982904
> thanks
Stopping processing here.

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

Bug#987844: marked as done (libtangence-perl: flaky autopkgtest: Lost 135168 bytes of memory over 1000 calls, average of 135.17 per call)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 20:18:56 +
with message-id 
and subject line Bug#987844: fixed in libtangence-perl 0.25-2
has caused the Debian Bug report #987844,
regarding libtangence-perl: flaky autopkgtest: Lost 135168 bytes of memory over 
1000 calls, average of 135.17 per call
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.)


-- 
987844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtangence-perl
Version: 0.25-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] and I noticed it fails regularly
(all with the same error) amd64, arm64 and armhf.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Paul

[1] https://ci.debian.net/packages/libt/libtangence-perl/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/9968742/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/10158148/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/11511120/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/12014480/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libt/libtangence-perl/12009148/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libt/libtangence-perl/11400077/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libt/libtangence-perl/10694595/log.gz


   Failed test 'Connect/watch/disconnect does not grow memory'
#   at t/90close-leak.t line 40.
# Lost 135168 bytes of memory over 1000 calls, average of 135.17 per call
1..1
# Looks like you failed 1 test of 1.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests

Test Summary Report
---
t/90close-leak.t (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=15, Tests=573,  4 wallclock secs ( 0.08 usr  0.04 sys +  3.88 cusr
 0.22 csys =  4.22 CPU)
Result: FAIL



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libtangence-perl
Source-Version: 0.25-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libtangence-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: Fri, 30 Apr 2021 21:55:10 +0200
Source: libtangence-perl
Architecture: source
Version: 0.25-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 987844
Changes:
 libtangence-perl (0.25-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since stretch:
 + Build-Depends-Indep: Drop versioned constraint on libstruct-dumb-perl.
 .
   [ gregor herrmann ]
   * Don't run t/90close-leak.t during build and autopkgtests.
 The test is flaky, and was probably meant as a release test for the
 upstream author in the first place.
 Thanks to Paul Gevers for the bug report. (Closes: #987844)
   * Drop libtest-memorygrowth-perl from Build-Depends-Indep.
 It was only needed for t/90close-leak.t which is now skipped.
Checksums-Sha1:
 d6d2ef2e822fde789501191280cfd7302ca05eaf 2652 libtangence-perl_0.25-2.dsc
 0dd828ada4669d0c0c548cf6aa7205a007caada0 2564 
libtangence-perl_0.25-2.debian.tar.xz
Checksums-Sha256:
 08920f0c4a50664e94fd135f7944db152dc68b4962fe8a7c92bc3f278e4e9d96 2652 
libtangence-perl_0.25-2.dsc
 2e5c9d9d90f7cd8316380e618af393d9eda8a7cf70b35ff8f56a8eb5e6f43be6 2564 
libtangence-perl_0.25-2.debian.tar.xz

Bug#949767: arrayfire update fails in configure step

[Andreas Tille]

On Thu, Apr 29, 2021 at 04:45:20PM +0200, Gard Spreemann wrote:
> The capitalization typo seems to be present also in arrayfire's
> use_debian_packaged_libs.patch: I believe line 64 of
> 
>  
> https://salsa.debian.org/science-team/arrayfire/-/blob/a11a6fef7dadf8ce594920626058990fe0caeb2a/debian/patches/use_debian_packaged_libs.patch#L64
> 
> should read
> 
>  +find_package(CLBlast)
> 
> instead of
> 
>  +find_package(CLBLast)
> 
> as it currently does.

This works now.  I decided to commit
   libclblast-dev (>= 1.5.2-2~)
assuming you will upload this version sooner or later.  Now I / someone
who intends to keep on maintaining this package (ping Ghislain are you
actively maintaing this package any more?) needs to deal with the Debian
packaged gtest - I'm afraid I'm currently busy with other things since
I think it is OK to remove clblas from Debian since arrayfire probably
can go without it.  This was the main purpose why I checked this package.
 
> > BTW, It would be great if [1] would feature a pristine-tar branch.
> 
> I'll look into creating pristine-tar branches for my packages. Thanks
> for the nudge!

You are welcome.  I'd recommend reading the chapter about importing
upstream sources of Debian Science policy[1].

Thanks a lot for your very helpful hints

  Andreas.


[1] https://science-team.pages.debian.net/policy/#idm306

-- 
http://fam-tille.de

Processed: Bug#987844 marked as pending in libtangence-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #987844 [src:libtangence-perl] libtangence-perl: flaky autopkgtest: Lost 
135168 bytes of memory over 1000 calls, average of 135.17 per call
Added tag(s) pending.

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

Bug#987844: marked as pending in libtangence-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #987844 in libtangence-perl 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/perl-team/modules/packages/libtangence-perl/-/commit/fc6d47491adf4f7943ecd2ca2a2e567c959a327f


Don't run t/90close-leak.t during build and autopkgtests.

The test is flaky, and was probably meant as a release test for the upstream
author in the first place.

Thanks: Paul Gevers for the bug report.
Closes: #987844


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/987844

Bug#987844: libtangence-perl: flaky autopkgtest: Lost 135168 bytes of memory over 1000 calls, average of 135.17 per call

[Paul Gevers]

Source: libtangence-perl
Version: 0.25-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] and I noticed it fails regularly
(all with the same error) amd64, arm64 and armhf.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Paul

[1] https://ci.debian.net/packages/libt/libtangence-perl/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/9968742/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/10158148/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/11511120/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/12014480/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libt/libtangence-perl/12009148/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libt/libtangence-perl/11400077/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/libt/libtangence-perl/10694595/log.gz


   Failed test 'Connect/watch/disconnect does not grow memory'
#   at t/90close-leak.t line 40.
# Lost 135168 bytes of memory over 1000 calls, average of 135.17 per call
1..1
# Looks like you failed 1 test of 1.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests

Test Summary Report
---
t/90close-leak.t (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=15, Tests=573,  4 wallclock secs ( 0.08 usr  0.04 sys +  3.88 cusr
 0.22 csys =  4.22 CPU)
Result: FAIL



OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 987798 is important

[Debian Bug Tracking System]

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

> severity 987798 important
Bug #987798 [src:linux] general: TG3 fails without repair when applying high 
load to NIC
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#987842: ifenslave: non-trivial bonding configuration fails

[Chris Hofstaedtler]

Package: ifenslave
Version: 2.11
Severity: serious

Only trivial configurations with no per-slave configurations seem to
work. I.e. the example in /usr/share/doc/ifenslave/examples/two_ethernet
works.

However, the example in /usr/share/doc/ifenslave/examples/two_hotplug_ethernet
does not - the slave devices are never added to the bondX device.

I believe this is caused by ifup bringing up the slave interfaces,
and the kernel refuses to add "UP" interfaces to a bondX device.

Version 2.9 in buster does not exhibit this problem, and can be used
on bullseye to demonstrate this regression from buster.

Chris

Processed: Re: Bug#986866: apacheds: ApacheDS fails to start after clean install

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #986866 [apacheds] apacheds: ApacheDS fails to start after clean install
Severity set to 'serious' from 'important'
> tags -1 + confirmed
Bug #986866 [apacheds] apacheds: ApacheDS fails to start after clean install
Added tag(s) confirmed.

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

Bug#952899: marked as done (pillow: d/copyright issues)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 18:18:30 +
with message-id 
and subject line Bug#952899: fixed in pillow 8.1.2+dfsg-0.1
has caused the Debian Bug report #952899,
regarding pillow: d/copyright issues
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.)


-- 
952899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pillow
Version: 6.2.1-2
Severity: serious
Justification: Policy 2.3, 4.5, 12.5

During review in binary-NEW, I found the following issues with
d/copyright.  Since the issues already exist in the archive I did not
REJECT, but they should be fixed.

Note that I am filing an identical list of problems against
src:pillow-python2 as the orig.tar is now in the archive twice.

- Needs "Alex Clark **and contributors**" from LICENSE

- Copyright information for Tests/fonts not in d/copyright.

- Google suggests that Tests/images/bmp is GPL-3 and also that the files
  are generated using C code.  If that's right, we would need to at
  least include that code for generating the images in
  debian/missing-sources/ (and ideally regenerate them).

- Tests/images/pillow3.icns looks like it contains a colour space
  copyright 1998 Hewlett-Packard Company; unclear how licensed.

- Tests/test_file_fli.py says that Tests/images/a.fli came from the web
  and I cannot see any free license; probably needs to be filtered out.

- Tests/test_file_mcidas.py says something similar for some other
  images; this should be accounted for.

- Several files matching {docs/example,src/PIL}/*ImagePlugin.py and
  src/libImaging/BcnDecode.c are public domain/CC0.

- Most files matching
  src/PIL/{ImageMorph,MspImagePlugin,SpiderImagePlugin,_binary}.py and
  src/libImaging/{Jpeg2K*,Quant*,SgiRleDecode.c,UnsharpMask.c} have
  different copyright holders.

- src/Tk/_tkmini.h has different copyright holders and license; possibly
  not DFSG-free due to "GOVERNMENT USE" section.

- src/libImaging/{QuantOctree.c,raqm.h,nmake.opt} have different
  licenses and copyright holders.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pillow
Source-Version: 8.1.2+dfsg-0.1
Done: Romain Porte 

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

Debian distribution maintenance software
pp.
Romain Porte  (supplier of updated pillow 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, 24 Apr 2021 15:51:24 +0200
Source: pillow
Architecture: source
Version: 8.1.2+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Romain Porte 
Closes: 952899
Changes:
 pillow (8.1.2+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Repack for DFSG compliance and update d/copyright. Closes: #952899.
   * Update d/watch for +dfsg repack.
Checksums-Sha1:
 9f4522ce08d2c0d426a558864f5245b6a024ed9b 2440 pillow_8.1.2+dfsg-0.1.dsc
 957d022b56eb23dba18eb69225a3acc53ddad92d 37523796 pillow_8.1.2+dfsg.orig.tar.xz
 fef8e0253c5d162b267cb4b5f804013363a36a76 17512 
pillow_8.1.2+dfsg-0.1.debian.tar.xz
 683be99330613b9ad58da61cfb3f659f5b4c1554 8352 
pillow_8.1.2+dfsg-0.1_source.buildinfo
Checksums-Sha256:
 d779addceb921bd6465ba24580a5e7b3a0544b8eaa04a509dcf757d5ffad40d0 2440 
pillow_8.1.2+dfsg-0.1.dsc
 7fb9b5e9306bfc30990322314cd92b6befd8e6ab9af6ef5bbccca18f938e4e49 37523796 
pillow_8.1.2+dfsg.orig.tar.xz
 6b315095adef83e07a54603f5edefe584ac3892df8ac19a93f7ad2a2a0cb24ab 17512 
pillow_8.1.2+dfsg-0.1.debian.tar.xz
 250450c131d88c7ce76a73838a23825d7f7b3997b17ac15b17a67cd513276aa8 8352 
pillow_8.1.2+dfsg-0.1_source.buildinfo
Files:
 4f8fe6a7c7bbc2989ef68368edad6645 2440 python optional pillow_8.1.2+dfsg-0.1.dsc
 d59ebd25220f5a7cff9a17232ca3701e 37523796 python optional 
pillow_8.1.2+dfsg.orig.tar.xz
 df45acacd5366a033db56d67af0b3032 17512 python optional 
pillow_8.1.2+dfsg-0.1.debian.tar.xz
 21b2416c06c9194fa714d0aa35603ad6 8352 python optional 
pillow_8.1.2+dfsg-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#987608: marked as done (shibboleth-sp: CVE-2021-31826: Session recovery feature contains a null pointer deference)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 16:47:41 +
with message-id 
and subject line Bug#987608: fixed in shibboleth-sp 3.0.4+dfsg1-1+deb10u2
has caused the Debian Bug report #987608,
regarding shibboleth-sp: CVE-2021-31826: Session recovery feature contains a 
null pointer deference
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.)


-- 
987608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shibboleth-sp
Version: 3.0.2+dfsg1-1
Severity: important
Tags: upstream patch security
Forwarded: https://issues.shibboleth.net/jira/browse/SSPCPP-927

Shibboleth Service Provider Security Advisory [26 April 2021]

An updated version of the Service Provider software is now
available which corrects a denial of service vulnerability.

Session recovery feature contains a null pointer deference
==
The cookie-based session recovery feature added in V3.0 contains a
flaw that is exploitable on systems *not* using the feature if a
specially crafted cookie is supplied.

This manifests as a crash in the shibd daemon/service process.

Because it is very simple to trigger this condition remotely, it
results in a potential denial of service condition exploitable by
a remote, unauthenticated attacker.

Versions without this feature (prior to V3.0) are not vulnerable
to this particular issue.

Recommendations
===
Update to V3.2.2 or later of the Service Provider software, which
is now available.

In cases where this is not immediately possible, configuring a
DataSealer component in shibboleth2.xml (even if used for nothing)
will work around the vulnerability.

For example:



This workaround is only possible after having updated the
core configuration to the V3 XML namespace.

Other Notes
===
The cpp-sp git commit containing the fix for this issue is
5a47c3b9378f4c49392dd4d15189b70956f9f2ec


URL for this Security Advisory:
https://shibboleth.net/community/advisories/secadv_20210426.txt
--- End Message ---
--- Begin Message ---
Source: shibboleth-sp
Source-Version: 3.0.4+dfsg1-1+deb10u2
Done: Ferenc Wágner 

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

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated shibboleth-sp 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, 26 Apr 2021 15:37:15 +0200
Source: shibboleth-sp
Architecture: source
Version: 3.0.4+dfsg1-1+deb10u2
Distribution: buster-security
Urgency: high
Maintainer: Debian Shib Team 
Changed-By: Ferenc Wágner 
Closes: 987608
Changes:
 shibboleth-sp (3.0.4+dfsg1-1+deb10u2) buster-security; urgency=high
 .
   * [2dd45b3] New patch: SSPCPP-927 - Check for missing DataSealer during
 cookie recovery.
 Fix a denial of service vulnerability: Session recovery feature contains
 a null pointer dereference
 The cookie-based session recovery feature added in V3.0 contains a
 flaw that is exploitable on systems *not* using the feature if a
 specially crafted cookie is supplied.
 This manifests as a crash in the shibd daemon.
 Because it is very simple to trigger this condition remotely, it
 results in a potential denial of service condition exploitable by
 a remote, unauthenticated attacker.
 Thanks to Scott Cantor (Closes: #987608)
Checksums-Sha1:
 aa91efd3b9c6f26b0ad95dfae340a49f41e8923c 3034 
shibboleth-sp_3.0.4+dfsg1-1+deb10u2.dsc
 936ea173fc1b0c9998f657b897650b9f7fdd84d1 79896 
shibboleth-sp_3.0.4+dfsg1-1+deb10u2.debian.tar.xz
 d74e5e9b65ef48c88c4294cf5a0d0ece4da1667c 14116 
shibboleth-sp_3.0.4+dfsg1-1+deb10u2_amd64.buildinfo
Checksums-Sha256:
 82ce3e5b624c34754807c76a70fc5549dc535e9c5d01af396b76966d9f9cf39d 3034 
shibboleth-sp_3.0.4+dfsg1-1+deb10u2.dsc
 01a3257b10e940430af70754daeccc29c08c091ae04a1fd519ff67cefb83b878 79896 
shibboleth-sp_3.0.4+dfsg1-1+deb10u2.debian.tar.xz
 74fdf85b4918fd5867fc5c858dd13c222327ca9dda34ed8901c1187ff07c0d56 14116 

Bug#986910: marked as done (gst-plugins-good1.0: CVE-2021-3497)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 16:47:22 +
with message-id 
and subject line Bug#986910: fixed in gst-plugins-good1.0 1.14.4-1+deb10u1
has caused the Debian Bug report #986910,
regarding gst-plugins-good1.0: CVE-2021-3497
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.)


-- 
986910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-good1.0
Version: 1.18.3-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: fixed -1 1.18.4-1

Hi,

The following vulnerability was published for gst-plugins-good1.0.

CVE-2021-3497[0]:
| gstreamer-plugins-good: Use-after-free in matroska demuxing

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-2021-3497
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3497
[1] https://gstreamer.freedesktop.org/security/sa-2021-0002.html
[2] 
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/commit/9181191511f9c0be6a89c98b311f49d66bd46dc3?merge_request_iid=903

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gst-plugins-good1.0
Source-Version: 1.14.4-1+deb10u1
Done: Sebastian Dröge 

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

Debian distribution maintenance software
pp.
Sebastian Dröge  (supplier of updated gst-plugins-good1.0 
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, 22 Apr 2021 21:32:31 +0300
Source: gst-plugins-good1.0
Binary: gstreamer1.0-gtk3 gstreamer1.0-plugins-good 
gstreamer1.0-plugins-good-dbg gstreamer1.0-plugins-good-doc 
gstreamer1.0-pulseaudio gstreamer1.0-qt5
Architecture: source amd64 all
Version: 1.14.4-1+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Maintainers of GStreamer packages 

Changed-By: Sebastian Dröge 
Description:
 gstreamer1.0-gtk3 - GStreamer plugin for GTK+3
 gstreamer1.0-plugins-good - GStreamer plugins from the "good" set
 gstreamer1.0-plugins-good-dbg - GStreamer plugins from the "good" set
 gstreamer1.0-plugins-good-doc - GStreamer documentation for plugins from the 
"good" set
 gstreamer1.0-pulseaudio - GStreamer plugin for PulseAudio
 gstreamer1.0-qt5 - GStreamer plugin for Qt5
Closes: 986910 986911
Changes:
 gst-plugins-good1.0 (1.14.4-1+deb10u1) buster-security; urgency=high
 .
   * 
debian/patches/0001-matroskademux-Initialize-track-context-out-parameter-to-NULL.patch:
 + Fix use-after free and stack corruption in Matroska demuxer
   (CVE-2021-3497) (Closes: #986910).
   * 
debian/patches/0002-matroskademux-Fix-extraction-of-multichannel-WavPack.patch:
 + Fix extraction of multichannel WavPack in Matroska demuxer, which caused 
heap corruption
   (CVE-2021-3498) (Closes: #986911).
Checksums-Sha1:
 ee05cd178b4d5da891502933d336b3598fdfb453 4027 
gst-plugins-good1.0_1.14.4-1+deb10u1.dsc
 382f7e424437ea8a3d1d7701569eddea76b18375 3792524 
gst-plugins-good1.0_1.14.4.orig.tar.xz
 07de251fde7689e8a849248652b4c03693963f95 39600 
gst-plugins-good1.0_1.14.4-1+deb10u1.debian.tar.xz
 03e1f9181b54ab7f38bc5959fd3d6565b19ec6a6 21561 
gst-plugins-good1.0_1.14.4-1+deb10u1_amd64.buildinfo
 d0985a06541ea449854d29b01f2923f32a92ae48 1269568 
gstreamer1.0-gtk3_1.14.4-1+deb10u1_amd64.deb
 dcab63498f77ab2dfaf5f613ae750752e86c2e42 10402304 
gstreamer1.0-plugins-good-dbg_1.14.4-1+deb10u1_amd64.deb
 33fc662a18bb7a25629e2329d0c3e8e13e50547a 1464332 
gstreamer1.0-plugins-good-doc_1.14.4-1+deb10u1_all.deb
 a2b8b9d229ce4fae175cf3b55e73a6fbaad4ee39 2922780 
gstreamer1.0-plugins-good_1.14.4-1+deb10u1_amd64.deb
 6c8d1fe8ef6a89922a8fbc76952777411a7a96d0 1292596 
gstreamer1.0-pulseaudio_1.14.4-1+deb10u1_amd64.deb
 636fbcc5bce4be77514b57c459048622d1b7c0f0 1282096 

Bug#986911: marked as done (gst-plugins-good1.0: CVE-2021-3498)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 16:47:22 +
with message-id 
and subject line Bug#986911: fixed in gst-plugins-good1.0 1.14.4-1+deb10u1
has caused the Debian Bug report #986911,
regarding gst-plugins-good1.0: CVE-2021-3498
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.)


-- 
986911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-good1.0
Version: 1.18.3-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: fixed -1 1.18.4-1

Hi,

The following vulnerability was published for gst-plugins-good1.0.

CVE-2021-3498[0]:
| gstreamer-plugins-good: Heap corruption in matroska demuxing

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-2021-3498
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3498
[1] https://gstreamer.freedesktop.org/security/sa-2021-0003.html
[2] 
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/commit/02174790726dd20a5c73ce2002189bf240ad4fe0?merge_request_iid=903

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gst-plugins-good1.0
Source-Version: 1.14.4-1+deb10u1
Done: Sebastian Dröge 

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

Debian distribution maintenance software
pp.
Sebastian Dröge  (supplier of updated gst-plugins-good1.0 
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, 22 Apr 2021 21:32:31 +0300
Source: gst-plugins-good1.0
Binary: gstreamer1.0-gtk3 gstreamer1.0-plugins-good 
gstreamer1.0-plugins-good-dbg gstreamer1.0-plugins-good-doc 
gstreamer1.0-pulseaudio gstreamer1.0-qt5
Architecture: source amd64 all
Version: 1.14.4-1+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Maintainers of GStreamer packages 

Changed-By: Sebastian Dröge 
Description:
 gstreamer1.0-gtk3 - GStreamer plugin for GTK+3
 gstreamer1.0-plugins-good - GStreamer plugins from the "good" set
 gstreamer1.0-plugins-good-dbg - GStreamer plugins from the "good" set
 gstreamer1.0-plugins-good-doc - GStreamer documentation for plugins from the 
"good" set
 gstreamer1.0-pulseaudio - GStreamer plugin for PulseAudio
 gstreamer1.0-qt5 - GStreamer plugin for Qt5
Closes: 986910 986911
Changes:
 gst-plugins-good1.0 (1.14.4-1+deb10u1) buster-security; urgency=high
 .
   * 
debian/patches/0001-matroskademux-Initialize-track-context-out-parameter-to-NULL.patch:
 + Fix use-after free and stack corruption in Matroska demuxer
   (CVE-2021-3497) (Closes: #986910).
   * 
debian/patches/0002-matroskademux-Fix-extraction-of-multichannel-WavPack.patch:
 + Fix extraction of multichannel WavPack in Matroska demuxer, which caused 
heap corruption
   (CVE-2021-3498) (Closes: #986911).
Checksums-Sha1:
 ee05cd178b4d5da891502933d336b3598fdfb453 4027 
gst-plugins-good1.0_1.14.4-1+deb10u1.dsc
 382f7e424437ea8a3d1d7701569eddea76b18375 3792524 
gst-plugins-good1.0_1.14.4.orig.tar.xz
 07de251fde7689e8a849248652b4c03693963f95 39600 
gst-plugins-good1.0_1.14.4-1+deb10u1.debian.tar.xz
 03e1f9181b54ab7f38bc5959fd3d6565b19ec6a6 21561 
gst-plugins-good1.0_1.14.4-1+deb10u1_amd64.buildinfo
 d0985a06541ea449854d29b01f2923f32a92ae48 1269568 
gstreamer1.0-gtk3_1.14.4-1+deb10u1_amd64.deb
 dcab63498f77ab2dfaf5f613ae750752e86c2e42 10402304 
gstreamer1.0-plugins-good-dbg_1.14.4-1+deb10u1_amd64.deb
 33fc662a18bb7a25629e2329d0c3e8e13e50547a 1464332 
gstreamer1.0-plugins-good-doc_1.14.4-1+deb10u1_all.deb
 a2b8b9d229ce4fae175cf3b55e73a6fbaad4ee39 2922780 
gstreamer1.0-plugins-good_1.14.4-1+deb10u1_amd64.deb
 6c8d1fe8ef6a89922a8fbc76952777411a7a96d0 1292596 
gstreamer1.0-pulseaudio_1.14.4-1+deb10u1_amd64.deb
 636fbcc5bce4be77514b57c459048622d1b7c0f0 1282096 

Bug#987568: open-iscsi-udeb: uninstallable udeb: non-udeb dependencies

[Ritesh Raj Sarraf]

On Fri, 2021-04-30 at 21:20 +0530, Ritesh Raj Sarraf wrote:
> 
> How would you like to see this fixed Cyril ?
> 
> The easiest option, if d-i supports, would be to extend architecture
> list to: `linux-any`, keeping it in line with what the actual open-
> iscsi package supports.

Here's what I've done. And propose.

rrs@priyasi:~/.../open-iscsi (wip/ritesh/fix-armel)$ git diff
master..HEAD
diff --git a/debian/changelog b/debian/changelog
index acfa52e..8365844 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+open-iscsi (2.1.3-4) unstable; urgency=medium
+
+  * [98b0d39] Add check for architectures where open-iscsi-udeb is
built
+  * [bf3d0f5] Add armel to support architecture for d-i
+
+ -- Ritesh Raj Sarraf   Fri, 30 Apr 2021 22:07:27
+0530
+
 open-iscsi (2.1.3-3) unstable; urgency=medium
 
   * [47645a5] Make open-iscsi-udeb compatible with d-i.
diff --git a/debian/control b/debian/control
index a69ce2c..3df235f 100644
--- a/debian/control
+++ b/debian/control
@@ -139,7 +139,7 @@ Package: open-iscsi-udeb
 #   linux kernel udebs) must exist for these architectures - so
 #   check that before adding them to this list; the other
 #   scsi-(core|common|...)-modules are NOT sufficient!
-Architecture: amd64 arm64 armhf i386 ia64 mips mipsel powerpc ppc64
ppc64el s390x
+Architecture: amd64 arm64 armel armhf i386 ia64 mips mipsel powerpc
ppc64 ppc64el s390x
 Section: debian-installer
 Package-Type: udeb
 Depends: ${misc:Depends},
diff --git a/debian/rules b/debian/rules
index 60211b8..17ef5d8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -101,4 +101,9 @@ override_dh_missing:
dh_missing --fail-missing
 
 override_dh_makeshlibs:
+ifneq (,$(filter $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 ia64
mips mipsel powerpc ppc64 ppc64el s390x))
dh_makeshlibs --add-udeb=open-iscsi-udeb
+else
+   dh_makeshlibs
+endif
+



I noticed that d-i seems to have gained support for armel too. So my
proposed changes introduce support for armel. And the conditional check
also ensures to call the correct dh_makeshlibs on the respective host
architecture.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#987568: open-iscsi-udeb: uninstallable udeb: non-udeb dependencies

[Ritesh Raj Sarraf]

The upload I prepped failed on some of the architectures.
https://buildd.debian.org/status/logs.php?pkg=open-iscsi=2.1.3-3

In d/control, there is:

```
Package: open-iscsi-udeb
# Note: the (virtual) udeb package scsi-modules (provided by different
#   linux kernel udebs) must exist for these architectures - so
#   check that before adding them to this list; the other
#   scsi-(core|common|...)-modules are NOT sufficient!
Architecture: amd64 arm64 armhf i386 ia64 mips mipsel powerpc ppc64
ppc64el s390x
Section: debian-installer
Package-Type: udeb
```


The udeb package was introduced by Colin Watson from Ubuntu. I extended
the architecture list, based on the supported architectures by d-i. But
I really don't use or test this functionality of the package.


How would you like to see this fixed Cyril ?

The easiest option, if d-i supports, would be to extend architecture
list to: `linux-any`, keeping it in line with what the actual open-
iscsi package supports.





On Thu, 2021-04-29 at 13:36 +0530, Ritesh Raj Sarraf wrote:
> 
> Thank you. I find your reworded comment proper and have applied the
> same.
> 
> I will now work with the release team.
> 

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#987568: marked as done (open-iscsi-udeb: uninstallable udeb: non-udeb dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 15:18:27 +
with message-id 
and subject line Bug#987568: fixed in open-iscsi 2.1.3-3
has caused the Debian Bug report #987568,
regarding open-iscsi-udeb: uninstallable udeb: non-udeb 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.)


-- 
987568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-iscsi-udeb
Version: 2.1.3-2
Severity: serious
Justification: not installable
X-Debbugs-Cc: debian-b...@lists.debian.org

Hi,

The udeb isn't installable at the moment, due to:

Depends: libc6-udeb (>= 2.31), libcrypto1.1-udeb (>= 1.1.1i), libisns-udeb, 
libkmod2-udeb (>= 28), libmount1-udeb (>= 2.33), libopeniscsiusr, libsystemd0 
(>= 247.3), udev, scsi-modules

In an installer context, that leads to:

The following packages have unmet dependencies:
 open-iscsi-udeb : Depends: libopeniscsiusr but it is not installable
   Depends: libsystemd0 (>= 247.3) but it is not installable
   Depends: udev but it is not installable

I'm currently chasing other blocking bugs for the installer, but I'll
add this bug to the list, and try to get back to it later.

Feel free to cc debian-b...@lists.debian.org to get help/feedback from
other members of the installer team in the meanwhile.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: open-iscsi
Source-Version: 2.1.3-3
Done: Ritesh Raj Sarraf 

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated open-iscsi 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, 29 Apr 2021 13:43:35 +0530
Source: open-iscsi
Architecture: source
Version: 2.1.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian iSCSI Maintainers 
Changed-By: Ritesh Raj Sarraf 
Closes: 987568
Changes:
 open-iscsi (2.1.3-3) unstable; urgency=medium
 .
   * [47645a5] Make open-iscsi-udeb compatible with d-i.
 Thanks to Cyril Brulebois (Closes: #987568)
Checksums-Sha1:
 c4680b81ef03f75a96a30973c74091536376eb6e 2578 open-iscsi_2.1.3-3.dsc
 04e3d4a3a5d9011b04b8456059bb1a7dad7e8e6e 53672 open-iscsi_2.1.3-3.debian.tar.xz
 a59d2b925b11bcab4ab0c338df0a98cd35e16e7b 5635 
open-iscsi_2.1.3-3_source.buildinfo
Checksums-Sha256:
 88abcaab191e58b4a9d7a5e90fecbb67f7b229f345ae184cddbbf085161661ec 2578 
open-iscsi_2.1.3-3.dsc
 76818258ccfd0651e1e8b90e5b2a3071b5512d59c9ef8af045ee1fb5a184098a 53672 
open-iscsi_2.1.3-3.debian.tar.xz
 d2339dd9edb23a0b943236847ff6058e5ebdf1b5939381f60b6cea8fe6a865d9 5635 
open-iscsi_2.1.3-3_source.buildinfo
Files:
 d68fc059cacd1a890347b146bfd67db2 2578 net optional open-iscsi_2.1.3-3.dsc
 15eadb5c62fc05c4d8fabd2011336403 53672 net optional 
open-iscsi_2.1.3-3.debian.tar.xz
 fe4d59a02b330f3825db09689d0afa72 5635 net optional 
open-iscsi_2.1.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAmCMHJMACgkQpjpYo/Lh
dWl+IxAAjTN75IO2OI+HDaga0DC3JnaFaFafs3VhmiRcPasv8DQfON46F0cqbRQT
+oG26iqPKS4Ydxts/AeGFzuMnPOUDL3c3+YSmp1vvOsZpYZ4Mr+C3+tT9FJigyTI
nbF3nq1NECHkzfS/tFHBljl6GOCUUSH5FFDsdGYr8X/8lFZp9VL/2WzYOW3LhRcF
M2vj2qBifDcoMIP4eeIHoRqfxNqLvv6gI+LLWBdZOxn5aX2V5KZj6NvvLbgiQM9/
Fi7WNG2MDni3HF6DC+/56z6V2fZUqwdFpaUuWxflyokL3IHqhLcaYFrkXHRPBQlP
+KVMC1bHT+D9mZNLN4hqgnvDBsWdVESNgRm7SDeGDiWj/j3h17BHcJp7syavi3QS
69f2/Vj2XA6gmr/6RoxI10kIgpN0CTLwstMp0EF3+xPL/bh3c5D9nv8nO+AHwEtj
CglikQnv+h5fsbweh7f5CN5aCS6o6i9IMQlhPMt9p1z9keFTqKb5cEXN1sBm5eBE
lSEzrQrHC+0Cn5t/NFQ2+Rf+msOJClWa/9+v1/PIYIuAlBMXZI1F+aROSRpXekXL
m/+jTutj4kC1YwcgK2Mlr0O5s1kR+8CZmus3kwBwEtY5sRLr+6SwlWUyzzEcGMp9
xbS7g8J1vK44VJE3U0J27qAaU3nUV/Zanu2XLKGs+S2ff9L4V5k=
=tndV
-END PGP SIGNATURE End Message ---

Bug#985297: libreoffice-common: do not use dir_to_symlink for /usr/lib/libreoffice/share/registry

[Andreas Beckmann]

Followup-For: Bug #985297
Control: tag -1 patch

Hi Rene,

I've been experimenting a lot to fix this bug.
One problem is Breaks in one package being handled first (by
deconfiguratio) and subsequent occurrences of Conflicts in another
package will be ignored for deconfigured packages (and removal will not
happen).

We can fix most of the upgrade issues by propagating the Conflicts to
the package with the Breaks, s.t. deconfiguration does not happen but
removal does happen immediately. Unfortunately this does not work if
there are too many packages the would need to be removed together since
dpkg does not get the optimal ordering for doing that. These are mostly
upgrade paths with libreoffice-impress or libreoffice-report-builder
installed.

So in the end I resorted to not using
  dpkg-maintscript-helper dir_to_symlink
as I had initially suggested but fixing it up manually in the postinst.

I've running various buster->bullseye upgrade scenarios (with and
without recommends, direct distupgrade vs upgrade && dist-upgrade)
with the patched packages as upgrade targets. I've rerun all piuparts
tests that had libreoffice-common installed and haven't seen any more
problems with the patched packages.

The attached patch does only patch debian/control.in, please regenerate
debian/control as this caused a lot of noise (I did nocheck builds).
It also contains adding some weird symbols with symbol version GLIBCXX_3.4
that looks weird, because libreoffice should not provide symbols with
such a version. This could also be an artefact of how I did build the
packages. Please decide what should happen to them.

Andreas
diff -Nru libreoffice-7.0.4/debian/changelog libreoffice-7.0.4/debian/changelog
--- libreoffice-7.0.4/debian/changelog  2021-01-03 18:54:17.0 +0100
+++ libreoffice-7.0.4/debian/changelog  2021-04-07 09:42:18.0 +0200
@@ -1,3 +1,16 @@
+libreoffice (1:7.0.4-4) UNRELEASED; urgency=medium
+
+  * libreoffice-core: Copy some Conflicts from libreoffice-common for smoother
+upgrades from buster. Dpkg will otherwise ignore Conflicts that are
+encountered later against a package that is already deconfigured.
+  * libreoffice-common: Do not use dir_to_symlink for
+/usr/lib/libreoffice/share/registry, the Breaks/Conflicts cascade does not
+work reliable here to ensure all packages previously shipping files there
+are either removed or upgraded first, but not just deconfigured. Fix up
+the symlink in postinst instead.  (Closes: #985297)
+
+ -- Andreas Beckmann   Wed, 07 Apr 2021 09:42:18 +0200
+
 libreoffice (1:7.0.4-3) unstable; urgency=medium
 
   * debian/tests/control.in: *really* add libreoffice-writer dependency
diff -Nru libreoffice-7.0.4/debian/control.in 
libreoffice-7.0.4/debian/control.in
--- libreoffice-7.0.4/debian/control.in 2020-12-31 11:27:09.0 +0100
+++ libreoffice-7.0.4/debian/control.in 2021-04-07 09:42:18.0 +0200
@@ -236,6 +236,15 @@
 libreoffice-common (<< 1:5.4.1),
 libreoffice-avmedia-backend-gstreamer (<< ${binary:Version})
 Conflicts: libreoffice-filter-binfilter, libreoffice-avmedia-backend-vlc, 
libreoffice-mysql-connector (<< 1:6.2.0~), libreoffice-core-nogui
+# for bullseye, copied from libreoffice-common, see #985297
+ ,
+ libreoffice-base (<< 1:7.0.0~alpha~),
+ libreoffice-calc (<< 1:7.0.0~alpha~),
+ libreoffice-draw (<< 1:7.0.0~alpha~),
+ libreoffice-impress (<< 1:7.0.0~alpha~),
+ libreoffice-math (<< 1:7.0.0~alpha~),
+ libreoffice-report-builder (<< 1:7.0.0~alpha~),
+ libreoffice-writer (<< 1:7.0.0~alpha~),
 Replaces: libreoffice-pdfimport (<< 1:5.4~), libreoffice-common (<< 
1:6.3.0~rc1~), libreoffice-avmedia-backend-gstreamer, libreoffice-core-nogui
 Description: office productivity suite -- arch-dependent files
  LibreOffice is a full-featured office productivity suite that provides
diff -Nru libreoffice-7.0.4/debian/libreoffice-common.maintscript 
libreoffice-7.0.4/debian/libreoffice-common.maintscript
--- libreoffice-7.0.4/debian/libreoffice-common.maintscript 2020-12-31 
11:27:09.0 +0100
+++ libreoffice-7.0.4/debian/libreoffice-common.maintscript 2021-04-07 
09:42:18.0 +0200
@@ -2,4 +2,10 @@
 mv_conffile /etc/apparmor.d/usr.lib.libreofficeprogram.senddoc 
/etc/apparmor.d/usr.lib.libreoffice.program.senddoc 1:5.4.3-1
 mv_conffile /etc/apparmor.d/usr.lib.libreofficeprogram.soffice.bin 
/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin 1:5.4.3-1
 mv_conffile /etc/apparmor.d/usr.lib.libreofficeprogram.xpdfimport 
/etc/apparmor.d/usr.lib.libreoffice.program.xpdfimport 1:5.4.3-1
-dir_to_symlink /usr/lib/libreoffice/share/registry /etc/libreoffice/registry 
1:7.0.2~rc1-1 
+
+# do this manually since dpkg-maintscript-helper dir_to_symlink
+# does not work reliably in this case because we cannot ensure that all
+# conflicting packages previously shipping files in
+# /usr/lib/libreoffice/share/registry are either upgraded or removed
+# but not just deconfigured, see #985297
+#dir_to_symlink 

Processed: Re: libreoffice-common: do not use dir_to_symlink for /usr/lib/libreoffice/share/registry

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #985297 [libreoffice-common] libreoffice-common: do not use dir_to_symlink 
for /usr/lib/libreoffice/share/registry
Added tag(s) patch.

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

Bug#959022: cgroup-tools: does not work in cgroup2 / unified hierarchy

[Santiago Ruano Rincón]

user debian-rele...@lists.debian.org
usertags -1 + bsp-2021-03-latinoamerica
thank you


signature.asc
Description: PGP signature

Bug#987364: marked as done (/usr/bin/node: segfaults regularly in node-opencv autopkgtest on ppc64el)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 12:48:58 +
with message-id 
and subject line Bug#987364: fixed in node-opencv 7.0.0+git20200310.6c13234-2
has caused the Debian Bug report #987364,
regarding /usr/bin/node: segfaults regularly in node-opencv autopkgtest on 
ppc64el
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.)


-- 
987364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs
Version: 12.20.2~dfsg-2
Severity: serious
Justification: segfaults
File: /usr/bin/node

Hi maintainer,

As can be seen in the autopkgtest history of node-opencv [1], that
autopkgtest regularly fails, and all failures with logs still present
are due to the same issue: node segfaults. The output from one of these
logs is at the bottom of this mail.

I ran the lines from d/t/unittest manually upto the last call and next I
ran $(node readimage.js) twice. The second time already triggered the
issue, see below.

root@elbrus:/tmp/autopkgtest-lxc.h7end76k/downtmp/autopkgtest_tmp/unittest6FSsAh/examples#
node readimage.js
Synchronous readImage("./files/mona.png")500x756
callback readImage("./files/mona.png", fn(){})500x756
Synchronous readImage(100, 100) (create mat)100x100 type 6
callback readImage(100, 100, fn(){}) (create mat)100x100
Synchronous readImage(imgdata:Buffer)500x756
callback readImage(imgdata:Buffer, fn(){})500x756
Now with flags
Synchronous readImage("./files/mona.png", 0) (monochrome)500x756 type 0
callback readImage("./files/mona.png", 1, fn(){}) (colour)500x756 type 16
Synchronous readImage(100, 100, cv.Constants.CV_8UC3) (create 8 bit 3
channel mat)100x100 type 16
callback readImage(100, 100, cv.Constants.CV_8UC1, fn(){}) (create
mat)100x100 type 0
Synchronous readImage(imgdata:Buffer, 0) (monochrome)500x756 type 0
callback readImage(imgdata:Buffer, 1, fn(){}) (colour)500x756 type 16
Now with readImageAsync
Synchronous readImageAsync("./files/mona.png")500x756
Synchronous readImageAsync(100, 100) (create mat)100x100 type 6
!!Synchronous!! callback readImageAsync(100, 100, fn(){}) (create
mat)100x100
Synchronous readImageAsync(imgdata:Buffer)500x756
Now Async with flags
Synchronous readImageAsync("./files/mona.png", 0) (monochrome)500x756 type 0
Synchronous readImageAsync(100, 100, cv.Constants.CV_8UC3) (create 8 bit
3 channel mat)100x100 type 16
!!Synchronous!! callback readImageAsync(100, 100, cv.Constants.CV_8UC1,
fn(){}) (create mat)100x100 type 0
Synchronous readImageAsync(imgdata:Buffer, 0) (monochrome)500x756 type 0

Truely Async callbacks should be after this line

Asynchronous callback readImageAsync("./files/mona.png", fn(){})500x756
Asynchronous callback readImageAsync(imgdata:Buffer, fn(){})500x756
Asynchronous callback readImageAsync("./files/mona.png", 1, fn(){})
(colour)500x756 type 16
Segmentation fault

Please let me know if you need more info or if I can you more useful
info (step by step please, I have no clue how node works).

Paul

[1] https://ci.debian.net/packages/n/node-opencv/testing/ppc64el/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/n/node-opencv/11596356/log.gz

# Example: ./examples/readimage.js
not ok 200 Error: Command failed: node
/tmp/autopkgtest-lxc._lzaasr1/downtmp/autopkgtest_tmp/unittesthM8OC4/examples/readimage.js
Segmentation fault
  ---
operator: error
expected: |-
  undefined
actual: |-
  { [Error: Command failed: node
/tmp/autopkgtest-lxc._lzaasr1/downtmp/autopkgtest_tmp/unittesthM8OC4/examples/readimage.js
Segmentation fault
] killed: false, code: 139, signal: null, cmd: 'node
/tmp/autopkgtest-lxc._lzaasr1/downtmp/autopkgtest_tmp/unittesthM8OC4/examples/readimage.js'
}
at: 
(/tmp/autopkgtest-lxc._lzaasr1/downtmp/autopkgtest_tmp/unittesthM8OC4/test/examples.js:18:16)
stack: |-
  Error: Command failed: node
/tmp/autopkgtest-lxc._lzaasr1/downtmp/autopkgtest_tmp/unittesthM8OC4/examples/readimage.js
  Segmentation fault

  at ChildProcess.exithandler (child_process.js:308:12)
  at ChildProcess.emit (events.js:314:20)
  at maybeClose (internal/child_process.js:1022:16)
  at Socket. (internal/child_process.js:444:11)
  at Socket.emit (events.js:314:20)
  at Pipe. (net.js:676:12)
  ...



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-opencv
Source-Version: 7.0.0+git20200310.6c13234-2
Done: Jérémy Lal 

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

Processed: Re: Bug#987364: [Pkg-javascript-devel] Bug#987364: /usr/bin/node: segfaults regularly in node-opencv autopkgtest on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-opencv
Bug #987364 [opencv] /usr/bin/node: segfaults regularly in node-opencv 
autopkgtest on ppc64el
Bug reassigned from package 'opencv' to 'node-opencv'.
Ignoring request to alter found versions of bug #987364 to the same values 
previously set
Ignoring request to alter fixed versions of bug #987364 to the same values 
previously set

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

Bug#987364: [Pkg-javascript-devel] Bug#987364: /usr/bin/node: segfaults regularly in node-opencv autopkgtest on ppc64el

[Jochen Sprickerhof]

Control: reassign -1 node-opencv

Hi,

* Jérémy Lal  [2021-04-22 18:38]:

(gdb) bt
#0  __memcpy_power7 () at ../sysdeps/powerpc/powerpc64/power7/memcpy.S:235
#1  0x70145254 in memcpy (__len=4, __src=,
__dest=0x7fffc779d480) at
/usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:34
#2  cv::PngDecoder::readDataFromBuf (_png_ptr=0x7fffbd20,
dst=0x7fffc779d480 "\226\341l\204", size=4) at
../modules/imgcodecs/src/grfmt_png.cpp:138
#3  0x7fffdb5799ac in png_read_data (png_ptr=,
data=, length=) at pngrio.c:37
#4  0x7fffdb581b2c in png_crc_error (png_ptr=0x7fffbd20) at
pngrutil.c:275
#5  0x7fffdb581c70 in png_crc_finish (png_ptr=0x7fffbd20,
skip=) at pngrutil.c:229
#6  0x7fffdb5882a8 in png_read_IDAT_data (png_ptr=0x7fffbd20,
output=, avail_out=) at pngrutil.c:4351
#7  0x7fffdb57608c in png_read_row (png_ptr=0x7fffbd20,
row=0x7fffc697c300 "", dsp_row=0x0) at pngread.c:623
#8  0x7fffdb5782d8 in png_read_image (png_ptr=0x7fffbd20,
image=0x7fffb000b910) at pngread.c:833
#9  0x70145fc8 in cv::PngDecoder::readData (this=0x7fffbc20,
img=...) at ../modules/imgcodecs/src/grfmt_png.cpp:284
#10 0x70128e4c in cv::imdecode_ (buf=..., flags=flags@entry=1,
mat=...) at ../modules/imgcodecs/src/loadsave.cpp:860
#11 0x70129a70 in cv::imdecode (_buf=..., flags=) at
../modules/imgcodecs/src/loadsave.cpp:900
#12 0x70539ec8 in AsyncImDecodeWorker::Execute (this=0x100253b00)
at /usr/include/opencv4/opencv2/core/mat.inl.hpp:92
#13 0x70530ba4 in Nan::AsyncExecute (req=) at
../../../../usr/lib/nodejs/nan/nan.h:2284
#14 0x760aac84 in uv__queue_work (w=) at
../deps/uv/src/threadpool.c:321
#15 0x760aad9c in worker (arg=0x0) at
../deps/uv/src/threadpool.c:122
#16 0x754a956c in start_thread (arg=0x7fffc779f140) at
pthread_create.c:477
#17 0x753b8044 in clone () at
../sysdeps/unix/sysv/linux/powerpc/powerpc64/clone.S:82


This is in the async version of node-opencv cleaning up the buffer 
during the memcpy. I was not able to reproduce it anymore with the 
attached hack (you probably want to commit a clean version).


Cheers Jochen
diff --git a/src/OpenCV.cc b/src/OpenCV.cc
index b9f779c..f84f249 100755
--- a/src/OpenCV.cc
+++ b/src/OpenCV.cc
@@ -37,6 +37,7 @@ public:
 cv::Mat mbuf(len, 1, CV_64FC1, buf);
 outputmat = cv::imdecode(mbuf, flags);
 success = 1;
+free(buf);
   } catch(...){
 success = 0;
   }
@@ -224,8 +225,10 @@ NAN_METHOD(OpenCV::ReadImageAsync) {
 // async
 uint8_t *buf = (uint8_t *) Buffer::Data(Nan::To(info[0]).ToLocalChecked());
 unsigned len = Buffer::Length(Nan::To(info[0]).ToLocalChecked());
+uint8_t *buf_new = (uint8_t *)malloc(len);
+memcpy(buf_new, buf, len);
 Nan::Callback *callback = new Nan::Callback(cb.As());
-Nan::AsyncQueueWorker(new AsyncImDecodeWorker(callback, buf, len, flags));
+Nan::AsyncQueueWorker(new AsyncImDecodeWorker(callback, buf_new, len, flags));
 return;
   }
   // WILL have returned by here unless exception


signature.asc
Description: PGP signature

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Ralf Jung]

Hi Sergei,


When we prepared the fix, we were not aware that this would become an RC bug, so
we didn't strive for a minimal fix.


Okay. Then I'll open a bugreport with release.debian.org and ask if
this not so minimal
update can propagate to testing. If yes, I'll reupload it.


That sounds great, thanks for your help. :)

Kind regards,
Ralf

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Sergei Golovan]

Hi Ralf,

On Fri, Apr 30, 2021 at 2:07 PM Ralf Jung  wrote:
>
> Hi Sergei,
>
> Our current problem is that we cannot even upload the package to unstable 
> since
> my key in the debian keyring expired (and the updated key missed the April
> keyring update), and Sebastien is not yet allowed to upload osspd.
> I've done the upload before figuring this out, so now revision 12 is sitting 
> on
> the ftp server and waiting for my key to become valid...
>
> If you are a DD, maybe you can help by uploading the package for us? I guess
> we'd have to prepare a revision 13, but that should be easy.

Yes, I'm a DD, sorry if I wasn't clear about this.

>
> When we prepared the fix, we were not aware that this would become an RC bug, 
> so
> we didn't strive for a minimal fix.

Okay. Then I'll open a bugreport with release.debian.org and ask if
this not so minimal
update can propagate to testing. If yes, I'll reupload it.

Cheers!
-- 
Sergei Golovan

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Ralf Jung]

Hi Sergei,

Our current problem is that we cannot even upload the package to unstable since 
my key in the debian keyring expired (and the updated key missed the April 
keyring update), and Sebastien is not yet allowed to upload osspd.
I've done the upload before figuring this out, so now revision 12 is sitting on 
the ftp server and waiting for my key to become valid...


If you are a DD, maybe you can help by uploading the package for us? I guess 
we'd have to prepare a revision 13, but that should be easy.


When we prepared the fix, we were not aware that this would become an RC bug, so 
we didn't strive for a minimal fix.


Kind regards,
Ralf

On 30.04.21 12:02, Sergei Golovan wrote:

Hi Ralf, Sebastien,

If you need any help with uploading the osspd package, please let me
know. I've looked at the current 1.3.2-12 in Git, and it looks fine
with the exception that it adds more changes than the fix of this bug
(which is not advisable during freeze periods). So, I'd start to ask
the release team if they are willing to grant a freeze exception for
the new version prior to upload.

Cheers!

Bug#987213: pypy-stem: fails to upgrade from buster: prerm uses pypy in unconfigured state

[Adrian Bunk]

On Mon, Apr 19, 2021 at 08:41:14PM +0200, Andreas Beckmann wrote:
>...
>   Preparing to unpack .../pypy-stem_1.8.0-3_all.deb ...
>   /usr/bin/pypy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not 
> found (required by /usr/lib/pypy/bin/libpypy-c.so)
>   dpkg: warning: old pypy-stem package pre-removal script subprocess returned 
> error exit status 1
>   dpkg: trying script from the new package instead ...
>   /usr/bin/pypy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not 
> found (required by /usr/lib/pypy/bin/libpypy-c.so)
>   dpkg: error processing archive 
> /var/cache/apt/archives/pypy-stem_1.8.0-3_all.deb (--unpack):
>new pypy-stem package pre-removal script subprocess returned error exit 
> status 1
>   /usr/bin/pypy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not 
> found (required by /usr/lib/pypy/bin/libpypy-c.so)
>   dpkg: error while cleaning up:
>installed pypy-stem package post-installation script subprocess returned 
> error exit status 1
>   Errors were encountered while processing:
>/var/cache/apt/archives/pypy-stem_1.8.0-3_all.deb
> 
> The problem: at the point where pypy-stem gets unpacked (und thus
> 'prerm upgrade' is run), the new pypy has already been unpacked but 
> the new libc6 is not yet unpacked.
> This should be solvable by adding Pre-depends: pypy to pypy-stem
> (to ensure pypy is in a usable state).
> But this looks more like a general problem that could happen in all
> pypy packages ...

The solution to the general problem would be to turn the pypy and pypy3 
Depends into Pre-Depends?

> cheers,
> 
> Andreas

cu
Adrian

Bug#987819: mate-optimus: Program is broken on Debian as prime-select doesn't exist

[Raibo Quadrofus]

Package: mate-optimus
Version: 20.10.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: raibo.quadro...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

The program that this package packages doesn't work 100% of the time,
and fails with an error about prime-select not existing when you try to use it 
any way.

It suggests the nvidia-prime package, which is required for it to work,
however nvidia-prime isn't packaged for Debian, only for Ubuntu. (Also,
there is an unresolved open wishlist item/similar to package nvidia-prime).

And the Ubuntu specific nvidia-prime package provides the required
prime-select tool.

This renders the program it packages completely unusable.

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

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
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=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-optimus depends on:
ii  gir1.2-ayatanaappindicator3-0.1  0.5.5-2
ii  gir1.2-gtk-3.0   3.24.24-3
ii  gir1.2-notify-0.70.7.9-3
ii  glew-utils   2.1.0-4+b1
ii  python3  3.9.2-3
ii  python3-gi   3.38.0-2
ii  python3-setproctitle 1.2.1-1+b1

mate-optimus recommends no packages.

Versions of packages mate-optimus suggests:
pn  nvidia-prime   
pn  ubuntu-drivers-common  

-- no debconf information

Bug#987306: marked as done (python3-libtorrent: move_storage did not match C++ signature)

[Debian Bug Tracking System]

Your message dated Fri, 30 Apr 2021 12:18:46 +0200
with message-id 
and subject line Accepted libtorrent-rasterbar 1.2.9-0.3 (source) into unstable
has caused the Debian Bug report #987306,
regarding python3-libtorrent: move_storage did not match C++ signature
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.)


-- 
987306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-libtorrent
Version: 1.2.9-0.2+b2
Severity: important
Tags: patch upstream

Dear Maintainer,

Trying to move a torrent using deluge-console results in the following
error:

ArgumentError
Python argument types in
torrent_handle.move_storage(torrent_handle, str)
did not match C++ signature:
move_storage(libtorrent::torrent_handle {lvalue},
std::__cxx11::basic_string, std::allocator >
path, libtorrent::move_flags_t
flags=libtorrent.move_flags_t.always_replace_files): Traceback (most recent
call last):
  File "/usr/lib/python3/dist-packages/deluge/core/torrent.py", line 1246, in
move_storage
self.handle.move_storage(dest.encode('utf8'), flags=2)
Boost.Python.ArgumentError: Python argument types in
torrent_handle.move_storage(torrent_handle, bytes)
did not match C++ signature:
move_storage(libtorrent::torrent_handle {lvalue},
std::__cxx11::basic_string, std::allocator >
path, libtorrent::move_flags_t
flags=libtorrent.move_flags_t.always_replace_files)


Upstream fixed this issue in patch [1]


[1]:
https://github.com/arvidn/libtorrent/pull/5093/commits/370da7df0a6624333ad92f43f79c8a385d928f48


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

Kernel: Linux 5.10.0-6-amd64 (SMP w/12 CPU threads)
Kernel taint flags: 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
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-libtorrent depends on:
ii  libboost-python1.74.0 [libboost-python1.74.0-py39]  1.74.0-9
ii  libc6   2.31-11
ii  libgcc-s1   10.2.1-6
ii  libssl1.1   1.1.1k-1
ii  libstdc++6  10.2.1-6
ii  libtorrent-rasterbar10  1.2.9-0.2+b2
ii  python3 3.9.2-2

python3-libtorrent recommends no packages.
--- End Message ---
--- Begin Message ---

Version: 1.2.9-0.3

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Apr 2021 07:51:42 +0200
Source: libtorrent-rasterbar
Architecture: source
Version: 1.2.9-0.3
Distribution: unstable
Urgency: medium
Maintainer: Cristian Greco 
Changed-By: Petter Reinholdtsen 
Changes:
 libtorrent-rasterbar (1.2.9-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Added d/patches/ README suggesting patch ordering and naming.
   * Added patch from upstream to make python move_storage() match C++ signature
Checksums-Sha1:
 8cb6177b4f2b3e0cce9fe20504eefb1429d208e1 2571 
libtorrent-rasterbar_1.2.9-0.3.dsc
 66864659604f2dd9c5fc53a2c35f1508b6a9cef0 1 
libtorrent-rasterbar_1.2.9-0.3.debian.tar.xz
 e524ebd01e105aabf4b93a3f679747fedeb0dd2c 8906 
libtorrent-rasterbar_1.2.9-0.3_source.buildinfo
Checksums-Sha256:
 8e616c42ad847abb77bba68abb214dc6f0db7e3635d9b8177e7568decea59ddc 2571 
libtorrent-rasterbar_1.2.9-0.3.dsc
 9ab1fb439b681f900bc20dbea302d43eef9110901cb8de1eeb783d4edcb03770 1 
libtorrent-rasterbar_1.2.9-0.3.debian.tar.xz
 d32f975a2d246350c704a535e6393a2833655b8a877a719f2ac302a0aee3e8e0 8906 
libtorrent-rasterbar_1.2.9-0.3_source.buildinfo
Files:
 46eeb34533a82173761cf9fec55ee42c 2571 libs optional 
libtorrent-rasterbar_1.2.9-0.3.dsc
 a7ca8ba1b58281462c58cafabe766aba 1 libs optional 
libtorrent-rasterbar_1.2.9-0.3.debian.tar.xz
 78cc42638438261e5d588377ac627989 8906 libs optional 
libtorrent-rasterbar_1.2.9-0.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmCLnKoACgkQgSgKoIe6
+w6WoBAAo45OO2/KtIDJ0s94NcHePzneZQAMrbECJ3V26AktQ2lyDXgn80GAlJaw
KwVVQJg55l50ULRkoMwRJxvHgm616Wjr8QyV//DD6SCdHf7H5qHIFSCJvVQAgjBD
YuVp4PFG68E/B11x/aI4DgaP4mnlQDqEJOeDQK7pN/z+b6iZcIITXdaOi4rY4Qo4

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Sergei Golovan]

Hi Ralf, Sebastien,

If you need any help with uploading the osspd package, please let me
know. I've looked at the current 1.3.2-12 in Git, and it looks fine
with the exception that it adds more changes than the fix of this bug
(which is not advisable during freeze periods). So, I'd start to ask
the release team if they are willing to grant a freeze exception for
the new version prior to upload.

Cheers!
-- 
Sergei Golovan

Bug#987587: libpango1.0-udeb: hangs the installer in various situations

[Chris Hofstaedtler]

* Cyril Brulebois  [210430 09:47]:
> Anyway, looking at the diffstat between 1.43.0 (last known good) and
> 1.44.4 (first known bad), we have this:
>  179 files changed, 19157 insertions(+), 7045 deletions(-)
> 
> Between 1.43.0 and 1.44 (if it were an earlier known bad):
>  165 files changed, 11006 insertions(+), 6766 deletions(-)
> 
> which is a huge diff still.

Indeed :-(

> From your earlier report on #987449[1], something around
> pango_default_break seemed to be happening. (In passing, I'd love to
> learn how you generated it so that I can try my luck with #987377.)

Quick steps:
- I created a Debian bullseye install with a kernel version matching
  the installer, and also installed linux-perf(-5.10)
- From the running, already stuck installer, I mounted the existing
  install, did the whole mount --bind stuff for sys, proc, dev.
  I cannot remember if one needs to actually chroot.
- And then its mostly `perf top` and/or `perf record` + `perf
  report`. The former gives you an immediate view, while the latter
  writes into a file which you can look at later.

Having more debug symbols would have been useful, but I did not
manage to set that up.

Chris

Bug#987587: libpango1.0-udeb: hangs the installer in various situations

[Cyril Brulebois]

Chris Hofstaedtler  (2021-04-29):
> > Alright, I think I'm hitting my limits here.
> > 
> > Versions 1.44, 1.44.2, and 1.44.3 all fail in a similar way:
>  ../pango/pangofc-font.c:371:44: error: ‘HB_OT_METRICS_UNDERLINE_SIZE’ 
> undeclared (first use in this function); did you mean 
> ‘HB_OT_METRICS_TAG_UNDERLINE_SIZE’?
> [..]
> 
> Just passing by, but I can build 1.44.0 with Debians 1.44.6 debian/
> directory, when adding this patch from upstream:
> https://gitlab.gnome.org/GNOME/pango/-/commit/d835004502c801a8a16cc436a38900e548ecde52.patch

Yes, the earlier stable releases from the 1.44.x series looked like
build-side stabilization and I suppose I could end up cherry-picking one
or more patches to get a bit further.

Anyway, looking at the diffstat between 1.43.0 (last known good) and
1.44.4 (first known bad), we have this:
 179 files changed, 19157 insertions(+), 7045 deletions(-)

Between 1.43.0 and 1.44 (if it were an earlier known bad):
 165 files changed, 11006 insertions(+), 6766 deletions(-)

which is a huge diff still.

From your earlier report on #987449[1], something around
pango_default_break seemed to be happening. (In passing, I'd love to
learn how you generated it so that I can try my luck with #987377.)

 1. https://bugs.debian.org/987449#15

and that helps a lot dig into that huge diff, which touched the file
holding that function, adding e.g. this hunk:

+   /* Dependent Vowels for Indic language */
+   if (_pango_is_Virama (prev_wc) ||
+   _pango_is_Vowel_Dependent (prev_wc))
+ attrs[i].backspace_deletes_character = TRUE;

Not knowing anything about it:
  https://en.wikipedia.org/wiki/Indic_languages

redirects to:
  https://en.wikipedia.org/wiki/Indo-Aryan_languages

which lists Sinhala, Marathi, but neither Persian nor Kannada.

There are a lot of other changes in that file anyway…


In the end, I might try and bisect deeper, if I can get stuff to build
without too much hassle…


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


signature.asc
Description: PGP signature