Bug#1012279: php-horde-turba: CVE-2022-30287

[Salvatore Bonaccorso]

Hi,

On Mon, Jun 06, 2022 at 09:16:53AM +0200, Salvatore Bonaccorso wrote:
> Source: php-horde-turba
> Source-Version: 4.2.25-6
> 
> On Mon, Jun 06, 2022 at 05:50:33AM +0200, Juri Grabowski wrote:
> > Hello together,
> > 
> > On 2022-06-05 14:35 7, Salvatore Bonaccorso wrote:
> > > it looks that the force pushed commit two days ago adjusted two
> > > further create() -> createTrusted() stances in lib/Application.php,
> > > can you double check?
> > functions backup and _restoreContact are only available on turba/master
> > for future release.
> 
> Thanks for checking. In this case let's close this bug with the
> 4.2.25-6 version.

Upstream has released v4.2.26 which contains fixes for the issue (done
bit differently).

Regards,
Salvatore

Processed: tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream ftbfs
Bug #1010430 [src:skimage] tifffile breaks skimage autopkgtest: asarray() got 
an unexpected keyword argument 'multifile'
Added tag(s) ftbfs and fixed-upstream.
> unblock -1 by 1010595
Bug #1010430 [src:skimage] tifffile breaks skimage autopkgtest: asarray() got 
an unexpected keyword argument 'multifile'
1010430 was blocked by: 1010595
1010430 was not blocking any bugs.
Removed blocking bug(s) of 1010430: 1010595

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

Bug#1010430: tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile'

[Graham Inggs]

Control: tags -1 + fixed-upstream ftbfs
Control: unblock -1 by 1010595

Fixed by the following commit, not in 0.19.2 release:

https://github.com/scikit-image/scikit-image/commit/6c4294c76ab1dcbd230d3c71414761248a83bce0

Bug#1011297: marked as done (please prevent successful build on ppc64el until it works)

[Debian Bug Tracking System]

Your message dated Tue, 07 Jun 2022 03:18:51 +
with message-id 
and subject line Bug#1011297: fixed in luajit 2.1.0~beta3+git20220320+dfsg-2
has caused the Debian Bug report #1011297,
regarding please prevent successful build on ppc64el until it works
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.)


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

Source: luajit, knot-resolver
Control: found -1 luajit/2.1.0~beta3+git20210112+dfsg-2
Control: found -1 knot-resolver/5.4.4-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of luajit the autopkgtest of knot-resolver fails in 
testing when that autopkgtest is run with the binary packages of luajit 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
luajit from testing2.1.0~beta3+git20210112+dfsg-2
knot-resolver  from testing5.4.4-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of luajit to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=luajit

https://ci.debian.net/data/autopkgtest/testing/ppc64el/k/knot-resolver/18781119/log.gz

/usr/sbin/kresd + /usr/bin/kdig roundtrip tests

workdir: /tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts
IP addr: 127.148.62.213
 kresd args: --addr=127.148.62.213@8053 --tls=127.148.62.213@8853 
--noninteractive 
--config=/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.conf 
--verbose --verbose --verbose


make Certificate Authority key and certificate
--
Generating a 3072 bit RSA private key...
Generating a self signed certificate...
X.509 Certificate Information:
Version: 3
Serial Number (hex): 2b34f0d7e93fd713653dda432ddeffed7f9f834b
Validity:
Not Before: Fri Jan 28 19:35:43 UTC 2022
Not After: Wed Feb 09 19:35:43 UTC 2022
Subject: CN=testing certificate authority (NOT FOR PRODUCTION)
Subject Public Key Algorithm: RSA
Algorithm Security Level: High (3072 bits)
Modulus (bits 3072):
00:98:66:36:e9:ce:d2:58:89:bc:a9:ec:ac:21:5e:4b
d2:f3:70:af:5c:41:11:d2:0f:fa:e2:f1:54:65:bc:86
06:4c:55:9f:0e:c3:72:8a:81:75:c3:be:2a:37:20:6a
ce:45:4d:22:00:92:d8:f3:ff:0c:d1:c3:9e:1b:0e:f9
c4:48:38:22:84:f7:a0:6a:bd:e9:34:9d:91:35:00:7b
97:28:c7:6b:49:14:ed:50:81:07:7e:cc:cb:3c:79:cb
fb:52:3d:3c:e0:c5:d9:1d:b5:1f:49:f4:55:74:db:a9
e7:58:fd:83:b6:56:ef:82:07:8f:6f:af:ec:26:b5:40
b4:23:1f:5c:b5:13:47:28:13:8a:58:58:19:f4:8f:3d
7e:12:c2:75:0c:7e:bd:f3:7d:89:f6:b6:3f:8f:63:99
1b:9d:e6:0c:63:fa:a5:5c:5e:08:27:d7:fd:af:3f:7c
54:74:4d:44:3b:ed:66:1a:05:ca:60:94:87:6d:47:c2
5e:8c:3f:1b:d9:60:21:4f:a4:30:1c:0a:21:da:34:0d
a5:cc:df:70:f4:82:71:d4:05:eb:31:0a:2f:59:db:dd
5a:38:15:2a:39:c0:1c:14:2c:cc:3e:b1:dc:97:3d:d7
ff:95:3c:b7:9a:c9:e4:e4:d1:ee:8e:5f:f0:41:d1:f8
2d:4b:6a:36:8d:e8:33:ad:92:b1:7d:65:07:29:56:36
4a:ee:62:75:58:70:f0:99:31:b5:d9:08:8c:68:13:a2
f6:93:38:a9:d7:f9:84:a2:06:29:6f:c8:4c:53:ec:de
37:4b:0a:3c:a9:69:df:57:fd:f0:94:da:d1:a8:5a:8d
40:80:e4:80:5d:85:4c:4a:2f:94:81:9f:e5:a6:a2:49
10:bf:ff:10:11:9f:c6:9d:4d:04:d4:46:f3:25:7c:62
93:7a:43:c9:2d:6a:d5:5a:f2:4a:b7:35:5e:a1:08:f4
a7:30:7a:50:a2:67:c1:f7:2b:17:43:29:0e:3b:34:48
c5
Exponent (bits 24):
01:00:01
 

Processed: severity of 1012074 is serious

[Debian Bug Tracking System]

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

> severity 1012074 serious
Bug #1012074 [src:python-rocksdb] python-rocksdb: FTBFS with rocksdb 7.2+
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1012373: marked as done (dulwich breaks breezy autopkgtest: command loaded forbidden modules ['shutil', 'ssl', 'tempfile'])

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 23:48:51 +
with message-id 
and subject line Bug#1012373: fixed in dulwich 0.20.43-1
has caused the Debian Bug report #1012373,
regarding dulwich breaks breezy autopkgtest: command loaded forbidden modules 
['shutil', 'ssl', 'tempfile']
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.)


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

Source: dulwich, breezy
Control: found -1 dulwich/0.20.42-1
Control: found -1 breezy/3.2.2-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of dulwich the autopkgtest of breezy fails in 
testing when that autopkgtest is run with the binary packages of dulwich 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
dulwichfrom testing0.20.42-1
breezy from testing3.2.2-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of dulwich to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=dulwich

https://ci.debian.net/data/autopkgtest/testing/amd64/b/breezy/22354009/log.gz

FAIL: 
breezy.tests.test_import_tariff.TestImportTariffs.test_simple_local_git

--
testtools.testresult.real._StringException: log: {{{95.793  Setting env 
for bzr subprocess: {'PYTHONVERBOSE': '1', 'BRZ_PLUGIN_PATH': 
'-site:-user', 'BRZ_DISABLE_PLUGINS': None, 'BRZ_PLUGINS_AT': None

start_brz_subprocess-log-0: {{{
this is a debug log for diagnosing/reporting problems in brz
you can delete or truncate this file, or include sections in
bug reports to https://bugs.launchpad.net/brz/+filebug

Sat 2022-06-04 20:12:21 +
0.055  encoding stdout as sys.stdout encoding 'utf-8'
0.056  encoding stdout as sys.stdout encoding 'utf-8'
0.056  encoding stdout as sys.stdout encoding 'utf-8'
0.077  breezy version: 3.2.2
0.077  brz arguments: ['--no-plugins', 'st']
0.079  encoding stdout as sys.stdout encoding 'utf-8'
0.146  check paths: None
0.147  shelving not supported by tree, not displaying shelves.
0.147  return code 0
}}}

subprocess_stderr: {{{
import _frozen_importlib # frozen
import _imp # builtin
import '_thread' # 
import '_warnings' # 
import '_weakref' # 
import '_io' # 
import 'marshal' # 
import 'posix' # 
import '_frozen_importlib_external' # '_frozen_importlib.FrozenImporter'>

# installing zipimport hook
import 'time' # 
import 'zipimport' # 
# installed zipimport hook
# /usr/lib/python3.10/encodings/__pycache__/__init__.cpython-310.pyc 
matches /usr/lib/python3.10/encodings/__init__.py
# code object from 
'/usr/lib/python3.10/encodings/__pycache__/__init__.cpython-310.pyc'
# /usr/lib/python3.10/__pycache__/codecs.cpython-310.pyc matches 
/usr/lib/python3.10/codecs.py

# code object from '/usr/lib/python3.10/__pycache__/codecs.cpython-310.pyc'
import '_codecs' # 
import 'codecs' # <_frozen_importlib_external.SourceFileLoader object at 
0x7f556e9a3520>
# /usr/lib/python3.10/encodings/__pycache__/aliases.cpython-310.pyc 
matches /usr/lib/python3.10/encodings/aliases.py
# code object from 
'/usr/lib/python3.10/encodings/__pycache__/aliases.cpython-310.pyc'
import 'encodings.aliases' # 
<_frozen_importlib_external.SourceFileLoader object at 0x7f556e7fcb80>
import 'encodings' # <_frozen_importlib_external.SourceFileLoader object 
at 0x7f556e9a3190>
# /usr/lib/python3.10/encodings/__pycache__/utf_8.cpython-310.pyc 
matches /usr/lib/python3.10/encodings/utf_8.py
# code object from 
'/usr/lib/python3.10/encodings/__pycache__/utf_8.cpython-310.pyc'
import 'encodings.utf_8' # <_frozen_importlib_external.SourceFileLoader 
object at 0x7f556e9a3370>

import '_signal' # 
# /usr/lib/python3.10/__pycache__/io.cpython-310.pyc matches 
/usr/lib/python3.10/io.py

# code object from '/usr/lib/python3.10/__pycache__/io.cpython-310.pyc'
# /usr/lib/python3.10/__pycache__/abc.cpython-310.pyc matches 
/usr/lib/python3.10/abc.py

# code object from '/usr/lib/python3.10/__pycache__/abc.cpytho

Processed: Re: Fails to install; conflict with libdcmtk16: trying to overwrite '/usr/share/libdcmtk16/acrnema.dic', which is also in package libdcmtk16 3.6.6-5

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1012417 [libdcmtk17] Fails to install; conflict with libdcmtk16
Severity set to 'serious' from 'normal'
> retitle -1 libdcmtk17: Fails to install; conflict with libdcmtk16: trying to 
> overwrite '/usr/share/libdcmtk16/acrnema.dic', which is also in package 
> libdcmtk16 3.6.6-5
Bug #1012417 [libdcmtk17] Fails to install; conflict with libdcmtk16
Changed Bug title to 'libdcmtk17: Fails to install; conflict with libdcmtk16: 
trying to overwrite '/usr/share/libdcmtk16/acrnema.dic', which is also in 
package libdcmtk16 3.6.6-5' from 'Fails to install; conflict with libdcmtk16'.

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

Processed: Bug#1012373 marked as pending in dulwich

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1012373 [src:dulwich, src:breezy] dulwich breaks breezy autopkgtest: 
command loaded forbidden modules ['shutil', 'ssl', 'tempfile']
Added tag(s) pending.

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

Bug#1012373: marked as pending in dulwich

[Jelmer Vernooij]

Control: tag -1 pending

Hello,

Bug #1012373 in dulwich 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/python-team/packages/dulwich/-/commit/568cc3367f4e298b55a2f1d0ac5e6756a7093b68


Drops unnecessary imports. Closes: #1012373


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1012373

Bug#1012428: gnome-shell-common: drmModeAddFB2WithModifiers Failed

[Tim McConnell]

Package: gnome-shell-common
Version: 42.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation? Do not know, my logs are getting multiple reports
of this error(?)

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

What was the outcome of this action?
11433 lines of:
gnome-shell[4883]: Failed to scan out client buffer: drmModeAddFB2WithModifiers
failed: Invalid argument

What outcome did you expect instead?
Not getting all of those errors in one hour



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

Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell-common depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3

gnome-shell-common recommends no packages.

gnome-shell-common suggests no packages.

-- no debconf information

Bug#988630: NMU: onedrive: Please update to the latest version

[Norbert Preining]

Hi Bastian,

thanks, feel free to adopt it / salvage it / whatever you feel like
doing with it.

regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#988630: marked as done (onedrive: Please update to the latest version)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 23:05:02 +
with message-id 
and subject line Bug#988630: fixed in onedrive 2.4.18-0.1
has caused the Debian Bug report #988630,
regarding onedrive: Please update to the latest version
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.)


-- 
988630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: onedrive
Version: 2.4.10-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: pitsior...@gmail.com

Dear Maintainer,

As the title suggests, please update to the latest version (2.4.11 at the time
of writing). I am having a serious issue with 502 and 504 errors when using the
app. I have reported it to the project's github repo, asking for help, and they
said they only provide support for the latest version and simply closed AND
LOCKED my issue!

I know that debian is under freeze and that the new version was released at
that period too, so I can wait and use a web browser for my onedrive transfers
until the freeze is over.
On the other hand, if only the latest version is supported by upstream, maybe
the package is not suitable for the stable versions of debian (lack of security
updates and lack of support too).

Thank you in advance.

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/2 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 not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages onedrive depends on:
ii  init-system-helpers  1.60
ii  libc62.31-11
ii  libgcc-s110.2.1-6
ii  libglib2.0-0 2.66.8-1
ii  libnotify4   0.7.9-3
ii  libphobos2-ldc-shared94  1:1.24.0-2
ii  libsqlite3-0 3.34.1-3

onedrive recommends no packages.

onedrive suggests no packages.
--- End Message ---
--- Begin Message ---
Source: onedrive
Source-Version: 2.4.18-0.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated onedrive 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, 06 Jun 2022 21:38:54 +
Source: onedrive
Architecture: source
Version: 2.4.18-0.1
Distribution: unstable
Urgency: medium
Maintainer: Norbert Preining 
Changed-By: Bastian Germann 
Closes: 988630
Changes:
 onedrive (2.4.18-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #988630).
   * d/control: Remove Vcs because debian branch is dropped.
   * d/copyright: Convert to machine-readable format and add missing info.
Checksums-Sha1:
 9dc388d44b89598c0d0efe5b222bf05b9c8e8e93 1695 onedrive_2.4.18-0.1.dsc
 a1d20eff0561777a5918052fabe1db0d0381d9f7 1147175 onedrive_2.4.18.orig.tar.gz
 0d33463b69108ddb68786eb2f8e22724bbcb0784 5936 onedrive_2.4.18-0.1.debian.tar.xz
 4c7e9f81ec4df57c3f87881e55d2d35cbdfe7b55 8544 
onedrive_2.4.18-0.1_source.buildinfo
Checksums-Sha256:
 2f3360a444b6874222d09b9d29c35b26814b8493e8ed0278b364fa8acab170ac 1695 
onedrive_2.4.18-0.1.dsc
 e6dfd1644395c03bebfc5e68e3d0037644c0bcad5d732326df5cec00fbd05f3d 1147175 
onedrive_2.4.18.orig.tar.gz
 2eb775dc0a881d5276d6643b65a3edf51709a46a7e186a0ba3707d8e6ca6d94b 5936 
onedrive_2.4.18-0.1.debian.tar.xz
 2cb590a0ff401f6cb78c98f3f63eb3e8b13978e1d737edc3dc186974d877caa9 8544 
onedrive_2.4.18-0.1_source.buildinfo
Files:
 72736167c29516c5609af12cbce13c34 1695 net optional onedrive_2.4.18-0.1.dsc
 64516b82e56575e084dd6b51f9f9d983 1147175 net optional 
onedrive_2.4.18.orig.tar.gz
 d8bf117441a70978c52fd3a6f9cdbb4d 5936 net optional 
onedrive_2.4.18-0.1.debian.tar.xz
 79e43f776f36a6121c0bdcbf75bb69b7 8544 net optional 
onedrive_2.4.18-0.1_source.buildinfo

---

Processed: tagging 1012246, bug 1012246 is forwarded to private communication, unmerging 1012246 ...

[Debian Bug Tracking System]

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

> tags 1012246 + upstream
Bug #1012246 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Added tag(s) upstream.
Added tag(s) upstream.
> forwarded 1012246 private communication
Bug #1012246 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Set Bug forwarded-to-address to 'private communication'.
Set Bug forwarded-to-address to 'private communication'.
> unmerge 1012246
Bug #1012246 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Disconnected #1012246 from all other report(s).
> reassign 1012246 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Bug #1012246 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla-470' to 
'src:nvidia-graphics-drivers-tesla-510'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-470/470.129.06-3.
Ignoring request to alter fixed versions of bug #1012246 to the same values 
previously set
Bug #1012246 [src:nvidia-graphics-drivers-tesla-510] fails on ppc64el due to 
transitive GPL symbol usage
Marked as found in versions nvidia-graphics-drivers-tesla-510/510.47.03-1.
> retitle 1012246 nvidia-graphics-drivers-tesla-510: fails on ppc64el due to 
> transitive GPL symbol usage
Bug #1012246 [src:nvidia-graphics-drivers-tesla-510] fails on ppc64el due to 
transitive GPL symbol usage
Changed Bug title to 'nvidia-graphics-drivers-tesla-510: fails on ppc64el due 
to transitive GPL symbol usage' from 'fails on ppc64el due to transitive GPL 
symbol usage'.
> retitle 1012245 nvidia-graphics-drivers-tesla-470: fails on ppc64el due to 
> transitive GPL symbol usage
Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] fails on ppc64el due to 
transitive GPL symbol usage
Changed Bug title to 'nvidia-graphics-drivers-tesla-470: fails on ppc64el due 
to transitive GPL symbol usage' from 'fails on ppc64el due to transitive GPL 
symbol usage'.
> found 1012245 470.57.02-1
Bug #1012245 [src:nvidia-graphics-drivers-tesla-470] 
nvidia-graphics-drivers-tesla-470: fails on ppc64el due to transitive GPL 
symbol usage
Marked as found in versions nvidia-graphics-drivers-tesla-470/470.57.02-1.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1011696 fixed-upstream
Bug #1011696 [curl] python-tornado: FTBFS: dh_auto_test: error: pybuild --test 
-i python{version} -p "3.9 3.10" returned exit code 13
Added tag(s) fixed-upstream.
> forwarded 1011696 https://github.com/curl/curl/issues/8844
Bug #1011696 [curl] python-tornado: FTBFS: dh_auto_test: error: pybuild --test 
-i python{version} -p "3.9 3.10" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/curl/curl/issues/8844'.
> --
Stopping processing here.

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

Bug#1012403: python3-python-flask-jwt-extended,python3-flask-jwt-extended: duplicate packages

[Emmanuel Arias]

Hi,

I cc Joseph.

Joseph, flask-jwt-extended is in Debian from some time ago
https://tracker.debian.org/pkg/python-flask-jwt-extended.

On Mon, Jun 6, 2022 at 11:15 AM Andreas Beckmann  wrote:

> Package: python3-python-flask-jwt-extended,python3-flask-jwt-extended
> Version: 4.4.0-1
> Severity: serious
>
> looks like a duplicate package was just uploaded to the archive.
>
> Andreas
>
>

Processed: closing 1011305

[Debian Bug Tracking System]

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

> close 1011305 3.2-3
Bug #1011305 [src:rspamd] please replace (build) dependency luajit with lua on 
ppc64el
Marked as fixed in versions rspamd/3.2-3.
Bug #1011305 [src:rspamd] please replace (build) dependency luajit with lua on 
ppc64el
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1011305: closing 1011305

[Sebastien Badia]

close 1011305 3.2-3
thanks

Hello,

Just fixed this in the latest upload, but I used the wrong keyword in my 
changelog entry.

Cheers,

Bug#1012416: marked as done (biosig: FTBFS: accovf_mex.cpp:44:26: error: pragma or attribute ‘target("avx2")’ is not valid)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 21:04:18 +
with message-id 
and subject line Bug#1012416: fixed in biosig 2.4.0-2
has caused the Debian Bug report #1012416,
regarding biosig: FTBFS: accovf_mex.cpp:44:26: error: pragma or attribute 
‘target("avx2")’ is not valid
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=biosig&arch=arm64&ver=2.4.0-1&stamp=1654526631&raw=0

accovf_mex.cpp:44:26: error: pragma or attribute ‘target("avx2")’ is not valid
   44 | #pragma GCC target("avx2")
  |  ^
g++ -I/usr/include/octave-7.1.0/octave/.. -I/usr/include/octave-7.1.0/octave  
-pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g  -o 
physicalunits.mex  /tmp/oct-HoFmCA.o   -L.. -lbiosig -shared -Wl,-Bsymbolic 
-Wl,-z,relro -Wl,-z,now -shared  -L/usr/lib/aarch64-linux-gnu -shared 
-Wl,-Bsymbolic  -Wl,-z,relro 
/usr/bin/mkoctfile  -I.. -v -g --mex "mexSOPEN.cpp" -L.. -lbiosig -o 
"mexSOPEN.mex"
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/octave-7.1.0/octave/.. -I/usr/include/octave-7.1.0/octave  
-pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g   -I.. -I.  
-DMEX_DEBUG mexSOPEN.cpp -o /tmp/oct-QNax32.o
make[3]: *** [Makefile:203: accovf_mex.mex] Error 1
make[3]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: biosig
Source-Version: 2.4.0-2
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated biosig 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, 06 Jun 2022 22:21:51 +0200
Source: biosig
Architecture: source
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1012416
Changes:
 biosig (2.4.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Add arch.patch: fix baseline violation and ftbfs. (Closes: #1012416)
   * Standards-Version: 4.6.1 (routine-update)
Checksums-Sha1:
 89d1ecf7c247f822766d9e8f466ef95c552ebdf1 2582 biosig_2.4.0-2.dsc
 af22be6e8800ad5968e5a1b3a8c08575d973be52 15048 biosig_2.4.0-2.debian.tar.xz
Checksums-Sha256:
 d811b0ef56ee023f6e844f5d28fbd0d4b2fda55734450bd99f7234fa3d91199a 2582 
biosig_2.4.0-2.dsc
 536f66550043649cdf08e847a4a80ca5fcf1a1cd412d54f716a04dd481fe131a 15048 
biosig_2.4.0-2.debian.tar.xz
Files:
 4552c7b91bd6843610780d1a3dd908c3 2582 science optional biosig_2.4.0-2.dsc
 cfd5b0e3db457630f1c49a790f884843 15048 science optional 
biosig_2.4.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmKeZ9UUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdpGbA/7BY8a5UuaRN99VF0cspLQ1F3rwKm0
4sHjifTgEYPmRyRkASmRLtNKbuEch8uk2Ks2utZc1bSgX65UvCfMHu3XHO7ovBB3
HWMpCh1/HXb9reXthzQSsAK6bPOeqimRsW/Yk+JYe5SyfUMQUNletmhjcgmq0jls
zDCCyZMZHYEGJQGJpuUuNwvRKbBUSHoJ+YDp1H0IwcwTDcImFX5R/cSBtt58/KDB
n+/ppzcv1qaeFM2RIM1BE94XYNBtZ6/sS1P8ULgR1EbFImoOquybGZokwWiHeoxW
O0d8NdE7SggxJaGQoz/W3pBBwXsy/LNYohFbS3sQLk/pyl+Kdk4SGM9tSPXZ3g2s
6RTJWu95QKkoHNHhIB1zXQksh98MP/G5oV9dMLeA4By9MsdnN9gozj29ZRw802Tn
uh/CmuBuQVFG76faWxSYR7SWTm6oGpIdi10HEReY6ftH0lLhO5LrXvBv8IVLPUgk
mePuU3pwZSufO7KgGStSV6N4MFoDbeJnIVdat/r3XH+v4Nlp8vwQSFCJ2YGPec+P
e718GsAnZ0hDH4WUNKt/BVjW7Y7STI/Gnhv6sVEL/sm/xPTfuoEBITpKTTC5354a
aFgvgg1NGlLPOAKXf0HZcWErvSccoJARV3c6D2BtmC/uka9YYXwdPvvv1Y6BTzNW
58siaMd878ymDfo=
=B6G4
-END PGP SIGNATURE End Message ---

Processed: Bug#1012416 marked as pending in biosig4c

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1012416 [src:biosig] biosig: FTBFS: accovf_mex.cpp:44:26: error: pragma or 
attribute ‘target("avx2")’ is not valid
Added tag(s) pending.

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

Bug#1012416: marked as pending in biosig4c

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1012416 in biosig4c 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/med-team/biosig/-/commit/6cb42edde48fbfeabaa12e3b925f45925735e5c4


Add arch.patch: fix baseline violation and ftbfs.

Closes: #1012416


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1012416

Bug#1012383: marked as done (src:directfb: fails to migrate to testing for too long: FTBFS on armel and armhf)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 19:49:25 +
with message-id 
and subject line Bug#1012383: fixed in directfb 1.7.7-11
has caused the Debian Bug report #1012383,
regarding src:directfb: fails to migrate to testing for too long: FTBFS on 
armel and armhf
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.)


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

Source: directfb
Version: 1.7.7-9
Severity: serious
X-Debbugs-CC: Andreas Beckmann 
Control: close -1 1.7.7-10
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s), Andreas,

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:directfb has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The package fails to build from 
source on armel and armhf where it successfully built in the past.


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 bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: directfb
Source-Version: 1.7.7-11
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated directfb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 06 Jun 2022 21:26:27 +0200
Source: directfb
Architecture: source
Version: 1.7.7-11
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1012383
Changes:
 directfb (1.7.7-11) unstable; urgency=medium
 .
   * QA upload.
   * Ship c64xdump on armel/armhf.  (Closes: #1012383)
Checksums-Sha1:
 2226fda6eca0968af7e409b1de9385ae4001f123 2827 directfb_1.7.7-11.dsc
 db1478eb4044f3a6257978a5e7188beadcb2eee6 25940 directfb_1.7.7-11.debian.tar.xz
 a1262b2ab5f13b15d7882cd0fe4bb3c8f621d50b 7751 
directfb_1.7.7-11_source.buildinfo
Checksums-Sha256:
 47c8bef0e8b71910309f0d743eaefd5afc0ac499c15b82e9362e9e7e1d541d89 2827 
directfb_1.7.7-11.dsc
 ab5f7b9a55acc215ab725df67baee6cbd7380d6c9312a1a035d3d4493268d8ba 25940 
directfb_1.7.7-11.debian.tar.xz
 23eec230d4f9fa27968001e8ee77bbe71572ad957cf83e9e743c5e613a024fb1 7751 
directfb_1.7.7-11_source.buildinfo
Files:
 48178e326bd0dcb6c5e76d6808f65b73 2827 libs optional directfb_1.7.7-11.dsc
 6f9ec71bfb77c4552883407da19940a3 25940 libs optional 
directfb_1.7.7-11.debian.tar.xz
 0bbb2b0d890b3ca94160795148cfde8d 7751 libs optional 
directfb_1.7.7-11_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmKeVXgQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCPIAD/wKfCuho7VR6m40Zjrtd3VY95wx7XDSQ1PA
icgl1aCONR/i73y+lvgvpBJSpre3+0gvK+p3bf7J/zEhx6O2qsmVYynIL8S/CTUc
3wBn5mUHHG0yLDYiR85NAI1UPRXqmCnSrNZZvAEEIRvD+14Ni37K7fbbPY7rasOm
Ve

Processed: severity of 1012419 is serious

[Debian Bug Tracking System]

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

> severity 1012419 serious
Bug #1012419 [src:ceres-solver] name of shared lib package did not follow 
SOVERSION bump, which causes breakages
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1012418: librust-zbus-dev: Broken with nix 0.24.1

[Dorota Czaplejewicz]

Filling in the gaps.

On Mon, 06 Jun 2022 18:23:39 +
dcz  wrote:

> Package: librust-zbus-dev
> Version: 1.9.2-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 

zbus is broken since a couple days: 
https://gitlab.gnome.org/World/Phosh/squeekboard/-/jobs/2047130

in particular, it tries to call into nix::sendmsg, but it seems sendmsg 
parameters have changed:

   Compiling zbus v1.9.2
error[E0308]: mismatched types
  --> /usr/share/cargo/registry/zbus-1.9.2/src/raw/socket.rs:70:13
   |
70 | &iov,
   |  types differ in mutability
   |
   = note: expected mutable reference `&mut [IoSliceMut<'_>]`
  found reference `&[IoVec<&mut [u8]>; 1]`
error[E0308]: mismatched types
  --> /usr/share/cargo/registry/zbus-1.9.2/src/raw/socket.rs:99:41
   |
99 | match sendmsg(self.as_raw_fd(), &iov, &cmsg, MsgFlags::empty(), 
None) {
   |  expected slice, found array 
of 1 element
   |
   = note: expected reference `&[IoSlice<'_>]`
  found reference `&[IoVec<&[u8]>; 1]`
For more information about this error, try `rustc --explain E0308`.
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.17.5-200.fc35.x86_64 (SMP w/2 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_WARN
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /bin/dash
> Init: unable to detect
> 
> Versions of packages librust-zbus-dev depends on:
> pn  librust-async-io-1+default-dev 
> pn  librust-byteorder-1+default-dev
> pn  librust-derivative-2+default-dev   
> pn  librust-enumflags2-0.6+default-dev 
> pn  librust-enumflags2-0.6+serde-dev   
> pn  librust-fastrand-1+default-dev 
> pn  librust-futures-0.3+default-dev
> pn  librust-nb-connect-1+default-dev   
> pn  librust-nix+default-dev
> pn  librust-once-cell-1+default-dev
> pn  librust-polling-2+default-dev  
> pn  librust-scoped-tls-1+default-dev   
> pn  librust-serde-1+default-dev
> pn  librust-serde-1+derive-dev 
> pn  librust-serde-repr-0.1+default-dev 
> pn  librust-serde-xml-rs-0.4+default-dev   
> pn  librust-zbus-macros-1.9.2+default-dev  
> pn  librust-zvariant-2+enumflags2-dev  
> 
> librust-zbus-dev recommends no packages.
> 
> librust-zbus-dev suggests no packages.



pgpV8FJVFzgmA.pgp
Description: OpenPGP digital signature

Bug#1009733: src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf

[Paul Gevers]

Hi Bernhard,

On 06-06-2022 18:47, Bernhard Übelacker wrote:

Am 06.06.22 um 18:43 schrieb Bernhard Übelacker:

I came here due to the recent message to debian-arm.
Still unsure because this bug is already closed?


Yeah, sorry about that. I file those "fails to migrate for too long 
bugs" most often against the version in testing, hence I close it 
immediately. With FTBFS bugs I'm unsure what my default should be.



Forgot to mention the merge request with the actual change:
https://salsa.debian.org/bernhardu-guest/exempi/-/merge_requests/1


It looks like that archive is private and thus can't bee seen. Also, I'd 
hope/expect the merge_request would be against the s.d.o/debian/exempi 
archive.


Thanks for taking the time to look into the issue, much appreciated.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012418: librust-zbus-dev: Broken with nix 0.24.1

[dcz]

Package: librust-zbus-dev
Version: 1.9.2-1
Severity: grave
Justification: renders package unusable

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


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

Kernel: Linux 5.17.5-200.fc35.x86_64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages librust-zbus-dev depends on:
pn  librust-async-io-1+default-dev 
pn  librust-byteorder-1+default-dev
pn  librust-derivative-2+default-dev   
pn  librust-enumflags2-0.6+default-dev 
pn  librust-enumflags2-0.6+serde-dev   
pn  librust-fastrand-1+default-dev 
pn  librust-futures-0.3+default-dev
pn  librust-nb-connect-1+default-dev   
pn  librust-nix+default-dev
pn  librust-once-cell-1+default-dev
pn  librust-polling-2+default-dev  
pn  librust-scoped-tls-1+default-dev   
pn  librust-serde-1+default-dev
pn  librust-serde-1+derive-dev 
pn  librust-serde-repr-0.1+default-dev 
pn  librust-serde-xml-rs-0.4+default-dev   
pn  librust-zbus-macros-1.9.2+default-dev  
pn  librust-zvariant-2+enumflags2-dev  

librust-zbus-dev recommends no packages.

librust-zbus-dev suggests no packages.

Bug#1012416: biosig: FTBFS: accovf_mex.cpp:44:26: error: pragma or attribute ‘target("avx2")’ is not valid

[Sebastian Ramacher]

Source: biosig
Version: 2.4.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=biosig&arch=arm64&ver=2.4.0-1&stamp=1654526631&raw=0

accovf_mex.cpp:44:26: error: pragma or attribute ‘target("avx2")’ is not valid
   44 | #pragma GCC target("avx2")
  |  ^
g++ -I/usr/include/octave-7.1.0/octave/.. -I/usr/include/octave-7.1.0/octave  
-pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g  -o 
physicalunits.mex  /tmp/oct-HoFmCA.o   -L.. -lbiosig -shared -Wl,-Bsymbolic 
-Wl,-z,relro -Wl,-z,now -shared  -L/usr/lib/aarch64-linux-gnu -shared 
-Wl,-Bsymbolic  -Wl,-z,relro 
/usr/bin/mkoctfile  -I.. -v -g --mex "mexSOPEN.cpp" -L.. -lbiosig -o 
"mexSOPEN.mex"
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/octave-7.1.0/octave/.. -I/usr/include/octave-7.1.0/octave  
-pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g   -I.. -I.  
-DMEX_DEBUG mexSOPEN.cpp -o /tmp/oct-QNax32.o
make[3]: *** [Makefile:203: accovf_mex.mex] Error 1
make[3]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher

Bug#1006511: net-snmp: FTBFS with OpenSSL 3.0

[Sergio Durigan Junior]

On Sunday, May 15 2022, Craig Small wrote:

> Upstream should have a new version of net-snmp that compiles with
> OpenSSL v3.0 in May.  I've tested the RC1 release and it compiles
> fine.
>
> https://sourceforge.net/p/net-snmp/mailman/message/37642006/

FWIW, Ubuntu's net-snmp has been using the following two patches
(backported from upstream) in order to fix the FTBFS with openssl 3.0:

https://git.launchpad.net/ubuntu/+source/net-snmp/tree/debian/patches/lp1945960-Fix-the-build-against-OpenSSL-3.0.patch

https://git.launchpad.net/ubuntu/+source/net-snmp/tree/debian/patches/lp1945960-configure-static-linking-Fix-SSL-checks.patch

If you'd like I can submit an MR/debdiff with these backports for Debian
as well.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Processed: [bts-link] source package src:exaile

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:exaile
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #785897 (http://bugs.debian.org/785897)
> # Bug title: exaile: Please update to GStreamer 1.x
> #  * https://github.com/exaile/exaile/issues/3
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 785897 + fixed-upstream
Bug #785897 [src:exaile] exaile: Please update to GStreamer 1.x
Added tag(s) fixed-upstream.
> usertags 785897 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:ruby-gitlab-fog-azure-rm

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:ruby-gitlab-fog-azure-rm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #996235 (http://bugs.debian.org/996235)
> # Bug title: ruby-gitlab-fog-azure-rm: FTBFS with ruby3.0: ERROR: Test 
> "ruby3.0" failed: ArgumentError: tried to create Proc object without a block
> #  * https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/issues/1
> #  * remote status changed: opened -> closed
> #  * closed upstream
> tags 996235 + fixed-upstream
Bug #996235 [src:ruby-gitlab-fog-azure-rm] ruby-gitlab-fog-azure-rm: FTBFS with 
ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc 
object without a block
Added tag(s) fixed-upstream.
> usertags 996235 - status-opened
Usertags were: status-opened.
There are now no usertags set.
> usertags 996235 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1000929 serious
Bug #1000929 [src:ghc] Please upgrade to llvm-toolchain-13 or 14
Ignoring request to change severity of Bug 1000929 to the same value.
> severity 1001317 serious
Bug #1001317 [src:pocl] Please upgrade to llvm-toolchain-13 or 14
Ignoring request to change severity of Bug 1001317 to the same value.
> severity 1000927 serious
Bug #1000927 [src:creduce] Please upgrade to llvm-toolchain-13 or 14
Ignoring request to change severity of Bug 1000927 to the same value.
> thanks
Stopping processing here.

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

Bug#988630: onedrive: Please update to the latest version

[Bastian Germann]

Hi Norbert,

Are you saying you consider this to be orphaned?

Thanks,
Bastian

Processed: your mail

[Debian Bug Tracking System]

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

> block 1012404 by 1004882
Bug #1012404 [ftp.debian.org] RM: llvm-toolchain-12 -- ROM; Limit the number of 
llvm versions
1012404 was not blocked by any bugs.
1012404 was not blocking any bugs.
Added blocking bug(s) of 1012404: 1004882
> thanks
Stopping processing here.

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

Processed: Please switch to llvm-toolchain 13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1000922 [src:llvmlite] Please upgrade to llvm-toolchain-13 or 14
Severity set to 'serious' from 'important'

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

Processed: Please switch to llvm-toolchain 13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1001317 [src:pocl] Please upgrade to llvm-toolchain-13 or 14
Severity set to 'serious' from 'important'

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

Processed: Please switch to llvm-toolchain 13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1000929 [src:ghc] Please upgrade to llvm-toolchain-13 or 14
Severity set to 'serious' from 'important'

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

Processed: Please switch to llvm-toolchain 13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1000927 [src:creduce] Please upgrade to llvm-toolchain-13 or 14
Severity set to 'serious' from 'important'

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

Bug#1012407: libsingular4m2n1: changes SONAME without changing package name

[David Bremner]

Package: libsingular4m2n1
Version: 1:4.3.0-p1+ds-2
Severity: serious
Justification: violates policy MUST: section 8.1, first paragraph

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Version 4.3.0 of libsingular4m2n1 has an SONAME of 

libsingular-Singular-4.3.0.so

Version 4.2.1 has SONAME

libsingular-Singular-4.2.1.so

This means the package name has to change, otherwise packages built
against 4.2.1 will break on systems with 4.3.0 installed.

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

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

Versions of packages libsingular4m2n1 depends on:
ii  libc6   2.33-7
ii  libflint-2.8.5  2.8.5-2
ii  libgmp102:6.2.1+dfsg-3
ii  libmpfr64.1.0-3
ii  libntl4411.5.1-1+b1
ii  libreadline88.1.2-1.2
ii  libstdc++6  12.1.0-2

libsingular4m2n1 recommends no packages.

libsingular4m2n1 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmKeDmMACgkQA0U5G1Wq
FSGHzw//UV7FGyvisGdYJaHpl+OVZyvQ/lPrWZyelFM2U94o8hB+E4Mi6ZKvxX7/
jJ1G7U8yR5GSgkAmzNwrUTL2rO+F0db/qnQV7i5IgTOmtCOrSoDUKvf08daTTUMl
5/Fe1y7VrESL6aFljigYLf2HuO+uoXqQRmIP8hmr7Io4N4s01ipBojrQ1Kuj10PP
VaRi3hPX/FzkVk6exA6W8sVxh36mMu1S6tAy9kWjpF3asnmy7dks/byjBwei88rL
RKHVle59pjGghY3LscEesgHV05EiH1AFsc7h5XWpxKqaNpUtgunz0KSEsX3iAVqK
jg76WErZAgzmclXsGPqgtdtxUYs7qa28Yf51X2PUhsYNpcXhr7lsOn+VT0GxXIEm
Hp3T9QzNwXl51hXqy11ajPn2uZENUXF66UxAuxbTqbmuyxg8uCPg6s4i1UeLcYUI
HDT38SVBj44dHdO8DrzrLTuCxxHx0cUKqX7Jq/Ie/1++JRkEUFyVr6Ls60szhKKs
XPYLeRAZMtxk9Rg1Vbbsqnn7GAiq8C9OeiCgpBFGbXo9m2gMZkjrHOQjexT12vVw
5/my1wm3jpx8eGoJ+Trkz61aFqU0ohG+PWH0lwGnrkBahogdFMWkL6SKfS5r1bfO
c7mJ7FIjO0Sxtu/HQ3KUaOhLv0jxw1bENV3gfPFyid37Xo1eetg=
=IVAe
-END PGP SIGNATURE-

Bug#1012403: python3-python-flask-jwt-extended,python3-flask-jwt-extended: duplicate packages

[Andreas Beckmann]

Package: python3-python-flask-jwt-extended,python3-flask-jwt-extended
Version: 4.4.0-1
Severity: serious

looks like a duplicate package was just uploaded to the archive.

Andreas

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 1012275
Bug #1012275 {Done: Salvatore Bonaccorso } [firefox] 
firefox: new upstream version fixes possible RCE security holes
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 101.0-1.
> tags 1012275 patch
Bug #1012275 [firefox] firefox: new upstream version fixes possible RCE 
security holes
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1011051: libssl3: upgrade to libssl3 broke my dovecot setup

[Steven Robbins]

On Monday, June 6, 2022 6:11:38 A.M. CDT Bernhard Übelacker wrote:

> The recent dovecot upload contains this fix:
> 
>dovecot (1:2.3.19+dfsg1-1) unstable; urgency=medium
>  * [d223bbd] d/patches: add patch to support openssl 3.0 (Closes:
> #996273)
> 
>   
> https://salsa.debian.org/debian/dovecot/-/commit/d223bbd1d0968ad2b46c4316c1
> 02c11bde8c5075

That's good news.  Does it mean one can remove the workaround (commenting out 
"providers = provider_sect") ?

Regards,
-Steve
 

Bug#1012275: closing 1012275

[Julian Wollrath]

reopen 1012275
tags 1012275 patch


Hi,

On Sun, 05 Jun 2022 23:46:25 +0200 Christoph Anton Mitterer
 wrote:
> On Sat, 2022-06-04 at 14:42 +0200, Vincent Bernat wrote:
> > Unfortunately, Firefox is not buildable due to depending on a
> > version of
> > Cargo not available in unstable.
>
> Shouldn't that be reopened then?
>
> I wouldn't be surprised if quite a number of people use the non ESR
> FF, probably also DDs/DMs.
>
> And because of rust deps, it seems to happen more often now, that
> security critical upgrades cannot enter unstable. (And yes I'm well
> aware, that unstable has no official security support, but still).

I am not sure though why the packaging requires a newer cargo version
then available from unstable and not just a newer rustc version, I
tried lowering the required version (see patch below) and it builds
just fine for me.


Cheers,
Julian


Patch:

diff -upNr a/debian/control b/debian/control
--- a/debian/control2022-05-31 23:07:37.0 +0200
+++ b/debian/control2022-06-06 13:50:48.239713566 +0200
@@ -28,7 +28,7 @@ Build-Depends: autotools-dev,
yasm,
nasm (>= 2.14) [amd64 i386],
rustc (>= 1.59),
-   cargo (>= 0.60),
+   cargo (>= 0.57),
llvm-dev,
libclang-dev,
clang,
diff -upNr a/debian/control.in b/debian/control.in
--- a/debian/control.in 2022-05-31 23:04:04.0 +0200
+++ b/debian/control.in 2022-06-06 13:51:17.093109680 +0200
@@ -51,9 +51,9 @@ Build-Depends: autotools-dev,
rustc (>= 1.59),
 %endif
 %if DIST == bullseye || DIST == buster || DIST == stretch
-   cargo-mozilla (>= 0.60),
+   cargo-mozilla (>= 0.57),
 %else
-   cargo (>= 0.60),
+   cargo (>= 0.57),
 %endif
 %if DIST == stretch
gcc-mozilla (>= 7.1),
diff -upNr a/debian/patches/debian-hacks/Lower-cargo-version.patch 
b/debian/patches/debian-hacks/Lower-cargo-version.patch
--- a/debian/patches/debian-hacks/Lower-cargo-version.patch 1970-01-01 
01:00:00.0 +0100
+++ b/debian/patches/debian-hacks/Lower-cargo-version.patch 2022-06-06 
14:13:11.030629556 +0200
@@ -0,0 +1,13 @@
+diff --git a/python/mozboot/mozboot/util.py b/python/mozboot/mozboot/util.py
+index 86720993d0..fdbf48f3ed 100644
+--- a/python/mozboot/mozboot/util.py
 b/python/mozboot/mozboot/util.py
+@@ -23,7 +23,7 @@ if sys.version_info < (3,):
+ else:
+ from urllib.request import urlopen
+
+-MINIMUM_RUST_VERSION = "1.59.0"
++MINIMUM_RUST_VERSION = "1.56.0"
+
+
+ def get_tools_dir(srcdir=False):
diff -upNr a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series 2022-05-31 22:51:42.0 +0200
+++ b/debian/patches/series 2022-06-06 14:13:27.027350785 +0200
@@ -17,3 +17,4 @@ debian-hacks/Avoid-using-vmrs-vmsr-on-ar
 debian-hacks/Use-build-id-as-langpack-version-for-reproducibility.patch
 debian-hacks/Allow-to-build-with-older-versions-of-nodejs-10.patch
 debian-hacks/Fix-math_private.h-for-i386-FTBFS.patch
+debian-hacks/Lower-cargo-version.patch



--
 ()  ascii ribbon campaign - against html e-mail
 /\- against proprietary attachments

Processed: reopening 1012383

[Debian Bug Tracking System]

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

> reopen 1012383
Bug #1012383 {Done: Paul Gevers } [src:directfb] 
src:directfb: fails to migrate to testing for too long: FTBFS on armel and armhf
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions directfb/1.7.7-10.
> thanks
Stopping processing here.

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

Bug#1012402: gufw: Illegal instruction on startup with armhf

[Thomas Walther]

Package: gufw
Version: 20.04.1-1
Severity: serious
Justification: Binary package does not seem to work in stable distribution
X-Debbugs-Cc: walther...@gmx.de

when trying to start gufw remotely on armhf it crashes, output is:
/usr/bin/gufw: line 2: [: too many arguments

(polkit-gnome-authentication-agent-1:2758): polkit-gnome-1-WARNING **: 
15:26:18.963: Unable to get a pixbuf for GTK_STOCK_DIALOG_AUTHENTICATION 
(gtk-dialog-authentication) at size 48
ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file 
or directory

(gufw.py:2975): dbind-WARNING **: 15:26:31.061: Couldn't connect to 
accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_0: No 
such file or directory
/usr/bin/gufw-pkexec: line 10:  2975 Illegal instruction python3 
${LOCATIONS[${i}]} $1


-- System Information:
Debian Release: 11.3
Architecture: armhf (armv7l)

Kernel: Linux 5.10.109 (PREEMPT)
Kernel taint flags: TAINT_RANDSTRUCT
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gufw depends on:
ii  gir1.2-gtk-3.0  3.24.24-4+deb11u2
ii  gir1.2-webkit2-4.0  2.36.3-1~deb11u1
ii  policykit-1 0.105-31+deb11u1
ii  python3 3.9.2-3
ii  python3-gi  3.38.0-2
ii  ufw 0.36-7.1

gufw recommends no packages.

gufw suggests no packages.

-- debconf-show failed

Bug#988630: onedrive: Please update to the latest version

[Norbert Preining]

> Raising severity because of the unusable state.

I would recommend this:
https://github.com/abraunegg/onedrive/blob/master/docs/ubuntu-package-install.md#distribution-package-install-instructions

Up to date packages for Debian stable/testing/unstable, Ubuntu.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1011736: marked as done (opensaml: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 11:44:41 +0200
with message-id <87k09uf7na@lant.ki.iif.hu>
and subject line Re: Bug#1011736: opensaml: FTBFS: dh_auto_test: error: make 
-j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
has caused the Debian Bug report #1011736,
regarding opensaml: FTBFS: dh_auto_test: error: make -j8 check 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
1011736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensaml
Version: 3.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/samltest'
> ../build-aux/test-driver: line 112: 825974 Segmentation fault  "$@" >> 
> "$log_file" 2>&1
> FAIL: samltest
> =
>opensaml 3.2.1: samltest/test-suite.log
> =
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: samltest
> ==
> 
> Running cxxtest tests (316 tests)FAIL samltest (exit status: 139)
> 
> 
> Testsuite summary for opensaml 3.2.1
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See samltest/test-suite.log
> Please report to https://issues.shibboleth.net/
> 
> make[4]: *** [Makefile:2675: test-suite.log] Error 1
> make[4]: Leaving directory '/<>/samltest'
> make[3]: *** [Makefile:2783: check-TESTS] Error 2
> make[3]: Leaving directory '/<>/samltest'
> make[2]: *** [Makefile:2856: check-am] Error 2
> make[2]: Leaving directory '/<>/samltest'
> make[1]: *** [Makefile:588: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/opensaml_3.2.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Lucas Nussbaum  writes:

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

Hi Lucas,

With xmltooling_3.2.1-2 opensaml_3.2.1-1 builds fine for me in unstable.
If you can still reproduce the failure, please reopen this bug.
-- 
Thanks,
Feri.--- End Message ---

Bug#1010912: marked as done (libdcmtk16 version 3.6.7-1: ldd blender shows missing .so files)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 10:00:10 +
with message-id 
and subject line Bug#1010536: fixed in dcmtk 3.6.7-2
has caused the Debian Bug report #1010536,
regarding libdcmtk16 version 3.6.7-1: ldd blender shows missing .so files
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.)


-- 
1010536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdcmtk16
Version: 3.6.7-1
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: sat...@newdev.siduction.org

Dear Maintainer,

I have two debian sid computers. Blender stopped working after an update to
libdcmtk16 version 3.6.7-1 on one of them. It had a missing library error. "ldd
/usr/bin/blender" showed 5 missing libraries that were all in libdcmtk16.
"apt-file show libdcmtk16" displayed both so.16 and so.17 versions of the
packages. "dpkg -L libdcmtk16" only showed so.17 versions. The blender not
found error concerned so.16 files.

I went to the other sid install that had the earlier package version "3.6.6-5"
and copied its so.16 files onto the broken system and blender now works.


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

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

Versions of packages libdcmtk16 depends on:
ii  libc62.33-7
ii  libgcc-s112.1.0-1
ii  libpng16-16  1.6.37-5
ii  libssl1.11.1.1o-1
ii  libstdc++6   12.1.0-1
ii  libtiff5 4.3.0-7
ii  libwrap0 7.6.q-31
ii  libxml2  2.9.14+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

libdcmtk16 recommends no packages.

libdcmtk16 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dcmtk
Source-Version: 3.6.7-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dcmtk 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: Wed, 04 May 2022 09:08:00 +0200
Source: dcmtk
Binary: dcmtk dcmtk-dbgsym dcmtk-doc libdcmtk-dev libdcmtk17 libdcmtk17-dbgsym
Architecture: source amd64 all
Version: 3.6.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 dcmtk  - OFFIS DICOM toolkit command line utilities
 dcmtk-doc  - OFFIS DICOM toolkit documentation
 libdcmtk-dev - OFFIS DICOM toolkit development libraries and headers
 libdcmtk17 - OFFIS DICOM toolkit runtime libraries
Closes: 1010536
Changes:
 dcmtk (3.6.7-2) unstable; urgency=medium
 .
   * Team upload.
   * Upstream has bumped SONAME thus rename binary package for shared
 library
 Closes: #1010536
Checksums-Sha1:
 b6ad40c2c2378695957502dbd80db0656699a10b 2258 dcmtk_3.6.7-2.dsc
 7953afab0b55c4f0f96de4e8c38afc71eb60e708 37144 dcmtk_3.6.7-2.debian.tar.xz
 5a243af5bd0fc3249e376d3c49c6c9a34c0981b4 5605036 dcmtk-dbgsym_3.6.7-2_amd64.deb
 38c41ccc3b61737920701930bc6b4f5bc0670ac2 8826512 dcmtk-doc_3.6.7-2_all.deb
 c44bf79b40faf40de807b654663beb8034faab3b 10449 dcmtk_3.6.7-2_amd64.buildinfo
 8a2fa731a07d489eca6f1fa69b93f36a6b4ccc34 877216 dcmtk_3.6.7-2_amd64.deb
 aeb0ebfc3369925e9f0423be202ac24c67e17103 1019900 libdcmtk-dev_3.6.7-2_amd64.deb
 6f4b2c4e8dedf3e484c7a1238e292082a5f18028 63493908 
libdcmtk17-dbgsym_3.6.7-2_amd64.deb
 0594224c35b871d8e88bd2f8c1260de9b9912895 4916396 libdcmtk17_3.6.7-2_amd64.deb
Checksums-Sha256:
 e1ca6d8734cd236b5bbd3bcd8540c75cd1f41610dbdce0797b8d156f7ff27692 2258 
dcmtk_3.6.7-2.dsc
 1efaa7d6ea6a2c0c8b7cbfe580f6ea3487c71314a7aed7cd792d52456351ca3f 37144 
dcmtk_3.6.7-2.debian.tar.xz
 e44497e68fc10691f8d534e

Bug#1010536: marked as done (libdcmimage.so.16: cannot open shared object file: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 10:00:10 +
with message-id 
and subject line Bug#1010536: fixed in dcmtk 3.6.7-2
has caused the Debian Bug report #1010536,
regarding libdcmimage.so.16: cannot open shared object file: No such file or 
directory
to be marked as done.

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

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


-- 
1010536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dcmtk
Version: 3.6.6-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ti...@debian.org

Hi Andreas,

thanks for your upload of the new upstream version of dcmtk.
Unfortunately, I think this is missing a proper transition because the
ABI and thus the SONAME changed. This can also be seen in the
autopkgtests of biosig, odil and odin which all fail with a similar
error right now:

biosig & odil: ImportError: libdcmdata.so.16: cannot open shared object file: 
No such file or directory

odin: gencoil: error while loading shared libraries: libdcmimgle.so.16: cannot 
open shared object file: No such file or directory

This is because the new upstream version bumped the SONAME from 16 to
17. This means, that the binary package name should also change from
libdcmtk16 to libdcmtk17. This probably would've been caught by
lintian if package-name-doesnt-match-sonames wasn't overridden in
debian/libdcmtk16.lintian-overrides... :/

The package should've probably first been uploaded to experimental,
would go through binary-NEW and create a auto-dcmtk transition. I'm
unsure how to clean this up now that the package has already been
uploaded to unstable.

I'm going to rebuild all reverse dependencies and see if anything breaks
and report back to you in case I find any FTBFS caused by the new dcmtk
version.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: dcmtk
Source-Version: 3.6.7-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dcmtk 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: Wed, 04 May 2022 09:08:00 +0200
Source: dcmtk
Binary: dcmtk dcmtk-dbgsym dcmtk-doc libdcmtk-dev libdcmtk17 libdcmtk17-dbgsym
Architecture: source amd64 all
Version: 3.6.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 dcmtk  - OFFIS DICOM toolkit command line utilities
 dcmtk-doc  - OFFIS DICOM toolkit documentation
 libdcmtk-dev - OFFIS DICOM toolkit development libraries and headers
 libdcmtk17 - OFFIS DICOM toolkit runtime libraries
Closes: 1010536
Changes:
 dcmtk (3.6.7-2) unstable; urgency=medium
 .
   * Team upload.
   * Upstream has bumped SONAME thus rename binary package for shared
 library
 Closes: #1010536
Checksums-Sha1:
 b6ad40c2c2378695957502dbd80db0656699a10b 2258 dcmtk_3.6.7-2.dsc
 7953afab0b55c4f0f96de4e8c38afc71eb60e708 37144 dcmtk_3.6.7-2.debian.tar.xz
 5a243af5bd0fc3249e376d3c49c6c9a34c0981b4 5605036 dcmtk-dbgsym_3.6.7-2_amd64.deb
 38c41ccc3b61737920701930bc6b4f5bc0670ac2 8826512 dcmtk-doc_3.6.7-2_all.deb
 c44bf79b40faf40de807b654663beb8034faab3b 10449 dcmtk_3.6.7-2_amd64.buildinfo
 8a2fa731a07d489eca6f1fa69b93f36a6b4ccc34 877216 dcmtk_3.6.7-2_amd64.deb
 aeb0ebfc3369925e9f0423be202ac24c67e17103 1019900 libdcmtk-dev_3.6.7-2_amd64.deb
 6f4b2c4e8dedf3e484c7a1238e292082a5f18028 63493908 
libdcmtk17-dbgsym_3.6.7-2_amd64.deb
 0594224c35b871d8e88bd2f8c1260de9b9912895 4916396 libdcmtk17_3.6.7-2_amd64.deb
Checksums-Sha256:
 e1ca6d8734cd236b5bbd3bcd8540c75cd1f41610dbdce0797b8d156f7ff27692 2258 
dcmtk_3.6.7-2.dsc
 1efaa7d6ea6a2c0c8b7cbfe580f6ea3487c71314a7aed7cd792d52456351ca3f 37144 
dcmtk_3.6.7-2.debian.tar.xz
 e44497e68fc10691f8d534e8c045c8712ea59d542424146688b8861b9a73ebf2 5605036 
dcmtk-dbgsym_3.6.7-2_amd64.deb
 2811190911bdc50632a7bb4eb69240f832c67393c324d77eef459028096ddec4 8826512 
dcmtk-doc_3.6.7-2_all.deb
 eb79455e677613b10950f0606a9b2935cb4b14a79daa23e76ce9c7c01261f121 10449 

Processed: Re: onedrive: Please update to the latest version

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #988630 [onedrive] onedrive: Please update to the latest version
Severity set to 'serious' from 'normal'

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

Bug#1012279: php-horde-turba: CVE-2022-30287

[Salvatore Bonaccorso]

Hi Mike, Juri,

On Sun, Jun 05, 2022 at 07:50:20PM +, Mike Gabriel wrote:
> Hi Salvatore,
> 
> On  So 05 Jun 2022 14:35:03 CEST, Salvatore Bonaccorso wrote:
> 
> > Hi,
> > 
> > On Sun, Jun 05, 2022 at 12:02:54PM +, Mike Gabriel wrote:
> > > Hi Juri,
> > > 
> > > On  Sa 04 Jun 2022 00:13:11 CEST, debian wrote:
> > > 
> > > > Hello,
> > > >
> > > > here is draft for MR:
> > > > https://salsa.debian.org/horde-team/php-horde-turba/-/merge_requests/1
> > > > I would look after it next time on sunday evening.
> > > >
> > > > @Mike: Can you please review it?
> > 
> > it looks that the force pushed commit two days ago adjusted two
> > further create() -> createTrusted() stances in lib/Application.php,
> > can you double check?
> 
> I actually did double check already, applied 9f242132 and saw that it did
> not apply properly (and thus reverted). See Git history at [1]. It seems
> that the backup/restore API calls (where these two spots of create ->
> createTrusted had been added) were not part of the 4.2.25 upstream release
> of turba.
> 
> > https://github.com/horde/turba/commit/9f2521328aa7d0dbd905591eca138c8e7580d673
> > (which is not yet merged, but compare to the used
> > https://github.com/horde/turba/commit/784da95e0190321b08ceeb27e2cb6c7505f2057c).
> > 
> > p.s.: the upload did contain a non valid bug closer, which in case the
> > above is correct cha be simply closed in a 4.2.25-7 upload.
> 
> If you agree, we have to close the bug manually as Juri's approach already
> contained the right patch.

yes, thank you!

Salvatore

Bug#1012279: marked as done (php-horde-turba: CVE-2022-30287)

[Debian Bug Tracking System]

Your message dated Mon, 6 Jun 2022 09:16:53 +0200
with message-id 
and subject line Re: Bug#1012279: php-horde-turba: CVE-2022-30287
has caused the Debian Bug report #1012279,
regarding php-horde-turba: CVE-2022-30287
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.)


-- 
1012279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-horde-turba
Version: 4.2.25-5
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for php-horde-turba,
CVE-2022-30287[0].

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-2022-30287
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30287
[1] https://blog.sonarsource.com/horde-webmail-rce-via-email/
[2] https://lists.horde.org/archives/horde/Week-of-Mon-20220530/059225.html
[3] https://github.com/horde/turba/pull/7

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: php-horde-turba
Source-Version: 4.2.25-6

On Mon, Jun 06, 2022 at 05:50:33AM +0200, Juri Grabowski wrote:
> Hello together,
> 
> On 2022-06-05 14:35 7, Salvatore Bonaccorso wrote:
> > it looks that the force pushed commit two days ago adjusted two
> > further create() -> createTrusted() stances in lib/Application.php,
> > can you double check?
> functions backup and _restoreContact are only available on turba/master
> for future release.

Thanks for checking. In this case let's close this bug with the
4.2.25-6 version.

Regards,
Salvatore--- End Message ---

Bug#1012279: php-horde-turba: CVE-2022-30287

[Salvatore Bonaccorso]

Source: php-horde-turba
Source-Version: 4.2.25-6

On Mon, Jun 06, 2022 at 05:50:33AM +0200, Juri Grabowski wrote:
> Hello together,
> 
> On 2022-06-05 14:35 7, Salvatore Bonaccorso wrote:
> > it looks that the force pushed commit two days ago adjusted two
> > further create() -> createTrusted() stances in lib/Application.php,
> > can you double check?
> functions backup and _restoreContact are only available on turba/master
> for future release.

Thanks for checking. In this case let's close this bug with the
4.2.25-6 version.

Regards,
Salvatore

Bug#1011653: blender ftbfs: no matching functional for call to openvdb*

[Gianfranco Costamagna]

On Wed, 25 May 2022 19:44:40 -0400 "M. Zhou"  wrote:

Source: blender
Version: 2.83.5+dfsg-5
Severity: serious

I found it ftbfs during onetbb reverse dependency test,
although the reason irrelevant to onetbb.
Version 3.X is still not built for amd64.






The reason for this failure is in DCMTK, bug #1010536

G.

Bug#1012386: python-seqcluster: FTBFS: ModuleNotFoundError: No module named 'attr'

[Andreas Beckmann]

Source: python-seqcluster
Version: 1.2.8+ds-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

python-seqcluster recently started to FTBFS after some (transitive)
build-dependency got updated:

[...]
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bman   doc/source 
build/man # Manpage generator
Running Sphinx v4.5.0

Exception occurred:
  File "/usr/lib/python3/dist-packages/myst_parser/main.py", line 3, in 
import attr
ModuleNotFoundError: No module named 'attr'
The full traceback has been saved in /tmp/sphinx-err-3fkwfzes.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2
[...]

The sphinx error log contains:

# Sphinx version: 4.5.0
# Python version: 3.10.4 (CPython)
# Docutils version: 0.17.1 release
# Jinja2 version: 3.0.3
# Last messages:

# Loaded extensions:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 272, in 
build_main
app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 217, in 
__init__
self.setup_extension(extension)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 374, in 
setup_extension
self.registry.load_extension(self, extname)
  File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 438, in 
load_extension
metadata = setup(app)
  File "/usr/lib/python3/dist-packages/myst_parser/__init__.py", line 12, in 
setup
from myst_parser.sphinx_parser import MystParser
  File "/usr/lib/python3/dist-packages/myst_parser/sphinx_parser.py", line 15, 
in 
from myst_parser.main import default_parser
  File "/usr/lib/python3/dist-packages/myst_parser/main.py", line 3, in 
import attr
ModuleNotFoundError: No module named 'attr'


Andreas


python-seqcluster_1.2.8+ds-2.log.gz
Description: application/gzip