Bug#1003006: reopening: graphviz: please migrate Recommends fonts-liberation to fonts-liberation2

[Martin-Éric Racine]

I'm reopening this bug.

The request was to transition FROM fonts-liberation2 TO
fonts-liberation2, NOT to add an extra dependency.

Martin-Éric

Bug#1013132: ITP: BabaSSL -- BabaSSL is a base library for modern cryptography and communication security protocols.

[Aron Xu]

Hi,

On Sat, Jun 18, 2022 at 12:43 AM Lance Lin  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Lance Lin 
> X-Debbugs-Cc: debian-de...@lists.debian.org, lqi...@protonmail.com
>
> * Package name: libBabaSSL
>   Version : 8.3.1
>   Upstream Author : Copyright (c) 2020-2022 Alibaba Digital Economy
> * URL : https://github.com/BabaSSL/BabaSSL
> * License : Apache 2.0
>   Programming Lang: C
>   Description : BabaSSL is a base library for modern cryptography and 
> communication security protocols.
>
> - BabaSSL is a modern cryptographic and secure protocol library developed by 
> the amazing people in Alibaba Digital Economy.
> - BabaSSL provides the following major features:
> -Support RFC 8998, Chinese SM cipher suites in TLS 1.3 protocol
> -Support NTLS (formal GM dual-certificate protocol) handshake processing, 
> according to GB/T 38636-2020 TLCP
> -QUIC API support
> -Support delegated credentials, according to draft-ietf-tls-subcerts-10
>
> I plan to package and maintain BabaSSL myself.
>

AFAIK this library is forked from OpenSSL with some extensive
modifications to support new crypto technologies, do you think we need
to involve the Security Team to review whether this package can be
supported during the next stable release cycle?

Also this project has a planned rename, and I'm a bit concerned this
could cause some maintenance burden if the rename is not well
coordinated at the time we accept it into Debian.

Regards,
Aron

Bug#932927: closed by xiao sheng wen(肖盛文) (fixed in 4.1.1-5)

[Aurelien Jarno]

control: reopen 932927
control: found 932927 4.1.1-5

On 2022-06-17 08:33, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:libotr package:
> 
> #932927: libotr: buggy unit test: test_auth.c: test_auth_clear()
> 
> It has been closed by xiao sheng wen(肖盛文) .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact xiao sheng wen(肖盛文) 
>  by
> replying to this email.
> 
> 
> -- 
> 932927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932927
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> From: "xiao sheng wen(肖盛文)" 
> To: 932...@bugs.debian.org, 932927-d...@bugs.debian.org
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
>  Thunderbird/91.10.0
> X-Spam-Status: No, score=-16.3 required=4.0 tests=BAYES_00,FREEMAIL_FROM,
>  PGPSIGNATURE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE
>  autolearn=ham autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02
> Date: Fri, 17 Jun 2022 16:24:31 +0800
> Subject: fixed in 4.1.1-5
> Message-ID: <235a1238-54d4-a34f-0060-6119cafad...@sina.com>
> 
> control: fixed -1 4.1.1-5
> 
> 
> tests/unit$ ./test_auth is run OK now:
> 
> 
> ./run.sh test_list
> unit/test_auth . ok
> 
> 
> atzlinux@Debian-StarFive:~/libotr/tests/unit$ ./test_auth
> 1..5
> ok 1 - OTR auth info init is valid
> ok 2 - OTR auth info clear is valid
> ok 3 - OTR auth start v23 is valid
> ok 4 - Copy not done
> ok 5 - Copy OK
> 

I confirm that the problem is not visible anymore on riscv64, probably
due to the switch from gcc 8 to 10.

However the underlying bug is still there and might appear again with a
toolchain change, on riscv64 or another architecture. I am therefore
reopening the bug.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#1012465: Live CD Images for Debian Blends

[Stefan Kropp]

On Fr, 2022-06-17 08:07:21, Andreas Tille wrote:
> Am Fri, Jun 17, 2022 at 01:49:39PM +0800 schrieb Paul Wise:
> > I note that Debian bookworm does not currently have live images at all,
> > so I would suggest that issue needs solving before blends live images,
> > you might want to discuss the issue on the debian-live mailing list.
> > 
> > Once the issue is solved with the creation of a new live team, then
> > they might be willing to add additional live images for blends.
> 
> I think Stefan's question was rather related to ITP #1012465 (since I
> pointed him to this list to discuss it here).   While I admit I like
> your idea to provide Blends live images at cdimage.debian.org (to at
> least have a workaround for bug #186085 which should enable installing
> Blends from the installer) Stefan has prepared some live system for
> Debian Jr in Salsa[1].  My idea was to not make this specific for
> Debian Jr. but rather make it configurable for any Blend and add this
> to blends-dev so all Blends can profit from this.
> 
> [1] https://salsa.debian.org/debian-jr-team/debian-junior-live-system

Question: Should blends have a dedicated package (e.g.
debian-junior-live-system) or should the live CD included into
the blend package itself (e.g. debian-junior)?

There may some pros and cons for both options. I may prefer the
option of a dedicated package + provide a guideline and naming
convention in the blends documentation + some meta information
about the Live Systems in the blend project (part of the blend
framework).

 * The developer follows the blends guideline
 * The build system look into the blends projects
   * Checkout the live systems defined in the project
   * Build and deliver the artifacts
 * The package itself is just the description / configuration of
   the artifact, but not the artifact itself.

Why? We can manage those packages independently. The blend
package will hopefully be part of the Debian installer. The Live
Systems may just an additional artefact of the project. Let's
say, we build a live CD to try Debian Junior on a desktop and
build an image for Debian Junior on a mobile device. Those
projects can be in different states (from experimental to
stable). A bug may affects System X but not Y. The build system
itself may different.

If I didn't miss something, we are more flexible to manage
packages, when they are independent.

Would be nice to know if somebody has concerns about it.

Have blends on cdimage.debian.org would be a big benefit for the
Debian project. I'm not sure whether all images *must* be build
on the same way/tools. At least across the blends projects we
should try to have the same way.

Bug#1002968: #1002968 tbb build success on riscv now

[M. Zhou]

Control: reassign -1 src:onetbb
Control: fixed -1 2021.5.0-8

src:tbb has been renamed into src:onetbb. riscv build was already fixed.

On Sat, 2022-06-18 at 09:22 +0800, xiao sheng wen wrote:
> Hi,
>     The tbb package had build successed on riscv now.
> libtbb2 is one of it's binary package:
> apt show libtbb2
> Package: libtbb2
>  Version: 2020.3-2.1
>  Priority: optional
>  Section: libs
>  Source: tbb
>  Maintainer: Debian Science Maintainers 
> 
>  Installed-Size: 224 kB
>  Depends: libtbbmalloc2, libatomic1 (>= 4.8), libc6 (>= 2.32), libgcc-s1 (>= 
> 3.4), libstdc++6 (>= 11)
>  Homepage: https://www.threadingbuildingblocks.org/
>  Download-Size: 109 kB
>  APT-Sources: https://mirrors.tencent.com/debian-ports unstable/main riscv64 
> Packages
>  Description: parallelism library for C++ - runtime files
>  
> The tbb (2020.3-2.1) cmake entry in debian/control still is:
> 
> | Build-Depends: debhelper-compat (= 12),
> |libjs-jquery,
> |dh-exec,
> |gdb,
> |    cmake [amd64 i386 arm64 armhf mips64el mipsel ppc64el s390x],
> 
> It has not riscv list in, perhaps this cmake arches list is not necessary.
> 

Bug#1013168: ITP: python-freenom -- Unofficial Python implementation of Freenom API

[Ben Westover]

Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Ben Westover 
X-Debbugs-Cc: kwestover...@gmail.com
Severity: wishlist

* Package name: python-freenom
  Version : 0.0.2
  Upstream Author : Nikolay Shamanovich 
* URL : https://github.com/Shm013/freenom-dns
* License : Expat
  Programming Lang: Python
  Description : Unofficial Python implementation of Freenom API

freenom-dns is an unofficial Python implementation of the Freenom API
used to manage freenom.com DNS records.

I am packaging this because it's a dependency of certbot-dns-freenom,
which I am also packaging.
I will maintain this package in the Python team.

--
Ben Westover


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002968: #1002968 tbb build success on riscv now

[肖盛文]

Hi,

    The tbb package had build successed on riscv now.

libtbb2 is one of it's binary package:

apt show libtbb2

Package: libtbb2
Version: 2020.3-2.1
Priority: optional
Section: libs
Source: tbb
Maintainer: Debian Science Maintainers 


Installed-Size: 224 kB
Depends: libtbbmalloc2, libatomic1 (>= 4.8), libc6 (>= 2.32), libgcc-s1 
(>= 3.4), libstdc++6 (>= 11)

Homepage: https://www.threadingbuildingblocks.org/
Download-Size: 109 kB
APT-Sources: https://mirrors.tencent.com/debian-ports unstable/main 
riscv64 Packages

Description: parallelism library for C++ - runtime files

The tbb (2020.3-2.1) cmake entry in debian/control still is:

| Build-Depends: debhelper-compat (= 12),
|libjs-jquery,
|dh-exec,
|gdb,
|    cmake [amd64 i386 arm64 armhf mips64el mipsel ppc64el s390x],

It has not riscv list in, perhaps this cmake arches list is not necessary.

--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page:https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013166: ITP: winterreise --- Keyboard navigation and window tiling for Linux desktop

[Andrei Mikhailov]

Package: wnpp
Severity: wishlist

https://github.com/amkhlv/winterreise

Bug#1013165: ITP: python-certbot-dns-freenom -- Freenom DNS01 plugin for certbot

[Ben Westover]

Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Ben Westover 
X-Debbugs-Cc: kwestover...@gmail.com
Severity: wishlist

* Package name: python-certbot-dns-freenom
  Version : 1.3.4
  Upstream Author : Nikolay Shamanovich 
* URL : https://github.com/Shm013/certbot-dns-freenom
* License : Apache-2.0
  Programming Lang: Python
  Description : Freenom DNS01 plugin for certbot

certbot-dns-freenom is a certbot DNS plugin used to obtain certificates
with Freenom DNS.

I am packaging this because I have domains on Freeenom and I use certbot
for certificates. My internet service provider has blocked port 80, so I
cannot prove my ownership of the domain using a normal HTTP challenge.
This software was the only way that I was able to obtain a certificate
for my Freenom domains using only a DNS challenge.
I will be maintaining this package inside the Python team.

--
Ben Westover


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013164: ITP: freenom-dns-updater -- Tool written in Python to update Freenom DNS records

[Ben Westover]

Package: wnpp
Severity: wishlist
Owner: Ben Westover 
X-Debbugs-Cc: debian-de...@lists.debian.org, kwestover...@gmail.com

* Package name: freenom-dns-updater
  Version : 1.2.9
  Upstream Author : Maxisoft 
* URL : https://github.com/maxisoft/Freenom-dns-updater
* License : Expat
  Programming Lang: Python
  Description : Python utility used to update Freenom DNS records

freenom-dns-updater is a tool used to update Freenom DNS records.

Main Features:
 * Manage (add/update/remove) a domain's dns record with cli
 * Automatic records updates according to ip (v4/v6) changes
 * Auto renew domains


I'm packaging this because I have domains on Freenom, and this tool is
useful for me to automatically update the DNS record whenever my public
IP address happens to change. It can also be used to automatically renew
free domains when they are about to expire.
I will be maintaining this package within the Python team.

--
Ben Westover


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013163: solvespace: autopkgtest regression on s390x: The model does not contain any surfaces to export.

[Paul Gevers]

Source: solvespace
Version: 3.1~rc1+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
solvespace from testing3.1~rc1+ds1-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 to testing [1]. Can 
you please investigate the situation and fix it?


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=solvespace

https://ci.debian.net/data/autopkgtest/testing/s390x/s/solvespace/22632206/log.gz

+ . debian/tests/common
+ logname=/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/surfaces.txt
+ get_files_with_surfaces
+ grep -E -v (constraint)|(request)|(link)|(contour_area)
+ get_all_files
+ find -name *.slvs
+ tee /tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/surfaces.txt
+ read fn
+ echo ./test/group/translate_nd/normal.slvs
./test/group/translate_nd/normal.slvs
+ dirname ./test/group/translate_nd/normal.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_nd/normal.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Generate::ALL took 43 ms
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd/normal_surfaces.step'.

+ read fn
+ echo ./test/group/translate_nd/normal_v22.slvs
./test/group/translate_nd/normal_v22.slvs
+ dirname ./test/group/translate_nd/normal_v22.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_nd/normal_v22.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Generate::ALL took 44 ms
Error: The model does not contain any surfaces to export.
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd/normal_v22_surfaces.step'.

+ read fn
+ echo ./test/group/translate_asy/normal.slvs
./test/group/translate_asy/normal.slvs
+ dirname ./test/group/translate_asy/normal.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_asy/normal.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy/normal_surfaces.step'.

+ read fn
+ echo ./test/group/translate_asy/normal_v22.slvs
./test/group/translate_asy/normal_v22.slvs
+ dirname ./test/group/translate_asy/normal_v22.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_asy/normal_v22.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Error: The model does not contain any surfaces to export.
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy/normal_v22_surfaces.step'.

+ read fn
+ grep Error 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/surfaces.txt

Error: The model does not contain any surfaces to export.
Error: The model does not contain any surfaces to export.
autopkgtest [09:07:56]: test surfaces



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013162: gifticlib: autopkgtest failure on s390x: computed checksum did NOT match

[Paul Gevers]

Source: gifticlib
Version: 1.0.9-5
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package gifticlib, great. 
However, it fails on s390x. Currently this failure is blocking the 
migration to testing [1] (but I'm going to disable s390x shortly for a 
day or so). Can you please investigate the situation and fix it? Please 
bear in mind that s390x is a big endian system so I would not be 
surprised if md5sums of files would be different there by design.


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

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=gifticlib

https://ci.debian.net/data/autopkgtest/testing/s390x/g/gifticlib/22340589/log.gz

Running Tests
==
FINAL IMAGE gifti_image struct
version= 1.0
numDA  = 3
gim->meta nvpairs struct, len = 3 :
nvpair: 'Caret-Version' = '5.511'
nvpair: 'date' = 'Wed Nov 21 14:53:44 2007'
nvpair: 'encoding' = 'XML'

gim->labeltable giiLabelTable struct, len = 3 :
key 17, rgba (0.620, 0.620, 0.620, 1.000), label 'PickleCenter'
key 23, rgba (0.500, 0.500, 0.500, 1.000), label 'DonutRegion'
key 29, rgba (1.000, 0.000, 0.000, 1.000), label 'MyCDATARegion'

--
gim->darray[0] giiDataArray struct
intent   1008 = NIFTI_INTENT_POINTSET
datatype   16 = NIFTI_TYPE_FLOAT32
ind_ord 1 = RowMajorOrder
num_dim   = 2
dims  = 10, 3, 0, 0, 0, 0
encoding1 = ASCII
endian  2 = LittleEndian
ext_fname = ext_offset= 0
darray->meta nvpairs struct, len = 4 :
nvpair: 'AnatomicalStructurePrimary' = 'CortexLeft'
nvpair: 'AnatomicalStructureSecondary' = 'Pial'
nvpair: 'GeometricType' = 'Anatomical'
nvpair: 'UniqueID' = '{e31cd8a6-bba6-4a1f-a26b-eb7337909a1c}'

darray->coordsys giiCoordSystem struct
dataspace  = NIFTI_XFORM_TALAIRACH
xformspace = NIFTI_XFORM_TALAIRACH
xform[0] :  1.00  0.00  0.00  0.00
xform[1] :  0.00  1.00  0.00  0.00
xform[2] :  0.00  0.00  1.00  0.00
xform[3] :  0.00  0.00  0.00  1.00
data   = 
nvals  = 30
nbyper = 4
numCS  = 1
darray->ex_atrs nvpairs struct, len = 0 :
--
--
gim->darray[1] giiDataArray struct
intent   1007 = NIFTI_INTENT_VECTOR
datatype   16 = NIFTI_TYPE_FLOAT32
ind_ord 1 = RowMajorOrder
num_dim   = 2
dims  = 10, 3, 0, 0, 0, 0
encoding1 = ASCII
endian  2 = LittleEndian
ext_fname = ext_offset= 0
darray->meta nvpairs struct, len = 1 :
nvpair: 'UniqueID' = '{ae03859c-3bd6-409e-9d95-b693380d0bdf}'

data   = 
nvals  = 30
nbyper = 4
numCS  = 0
darray->ex_atrs nvpairs struct, len = 0 :
--
--
gim->darray[2] giiDataArray struct
intent   1009 = NIFTI_INTENT_TRIANGLE
datatype8 = NIFTI_TYPE_INT32
ind_ord 1 = RowMajorOrder
num_dim   = 2
dims  = 10, 3, 0, 0, 0, 0
encoding1 = ASCII
endian  2 = LittleEndian
ext_fname = ext_offset= 0
darray->meta nvpairs struct, len = 2 :
nvpair: 'TopologicalType' = 'CLOSED'
nvpair: 'UniqueID' = '{52f9c071-75ea-4e42-bde9-3d9ba3930b94}'

data   = 
nvals  = 30
nbyper = 4
numCS  = 0
darray->ex_atrs nvpairs struct, len = 0 :
--
gifti_image struct
swapped= 0
compressed = 0
 -- darray totals: 0 MB
gim->ex_atrs nvpairs struct, len = 0 :
==
md5sum: WARNING: 1 computed checksum did NOT match
created.gii: FAILED
autopkgtest [11:01:47]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013161: corsix-th: crashes with "module 'lpeg' not found"

[Phil Morrell]

Package: corsix-th
Version: 0.65.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: deb...@emorrp1.name



first reported on 2022-06-06 by u/rocketstopya on Ubuntu 22.04
https://www.reddit.com/r/linux_gaming/comments/v620w5/corsixth_v066beta2_is_out/ibdca6u/



emorrp1@testing:~$ corsix-th


---

Welcome to CorsixTH v0.65.1!

---

This window will display useful information if an error occurs.

---

An error has occurred in CorsixTH:
/usr/share/games/corsix-th/Lua/strict.lua:66: module 'lpeg' not found:
no field package.preload['lpeg']
no file '/usr/share/games/corsix-th/Lua/lpeg.lua'
no file '/usr/share/games/corsix-th/Lua/lpeg/init.lua'
no file '/usr/local/share/lua/5.4/lpeg.lua'
no file '/usr/local/share/lua/5.4/lpeg/init.lua'
no file '/usr/local/lib/lua/5.4/lpeg.lua'
no file '/usr/local/lib/lua/5.4/lpeg/init.lua'
no file '/usr/share/lua/5.4/lpeg.lua'
no file '/usr/share/lua/5.4/lpeg/init.lua'
no file './lpeg.lua'
no file './lpeg/init.lua'
no file '/usr/share/games/corsix-th/lpeg.so'
no file '/usr/local/lib/lua/5.4/lpeg.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.4/lpeg.so'
no file '/usr/lib/lua/5.4/lpeg.so'
no file '/usr/local/lib/lua/5.4/loadall.so'
no file './lpeg.so'
stack traceback:
[C]: in upvalue 'fn'
/usr/share/games/corsix-th/Lua/strict.lua:66: in function 'require'
/usr/share/games/corsix-th/Lua/string_extensions.lua:22: in main chunk
[C]: in function 'persist.dofile'
/usr/share/games/corsix-th/CorsixTH.lua:78: in field 'require'
/usr/share/games/corsix-th/Lua/app.lua:240: in method 'init'
/usr/share/games/corsix-th/CorsixTH.lua:143: in main chunk
[C]: in ?



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

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

Versions of packages corsix-th depends on:
ii  corsix-th-data   0.65.1-1
ii  libavcodec58 7:4.4.2-1+b2
ii  libavformat587:4.4.2-1+b2
ii  libavutil56  7:4.4.2-1+b2
ii  libc62.33-7
ii  libfreetype6 2.12.1+dfsg-2
ii  libgcc-s112.1.0-2
ii  liblua5.4-0  5.4.4-2
ii  libsdl2-2.0-02.0.22+dfsg-5
ii  libsdl2-mixer-2.0-0  2.0.4+dfsg1-4+b1
ii  libstdc++6   12.1.0-2
ii  libswresample3   7:4.4.2-1+b2
ii  libswscale5  7:4.4.2-1+b2
ii  lua-filesystem   1.8.0-2
ii  lua-lpeg 1.0.2-1

Versions of packages corsix-th recommends:
ii  game-data-packager  69
ii  timidity2.14.0-8+b1

corsix-th suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1013160: bugs.debian.org: Wireless only works when activated manually on boot and network driver restart.

[Jorge]

Package: bugs.debian.org
Severity: important
X-Debbugs-Cc: 1994jorgesanc...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
I don't really know. I just updated debian testing to latest version and 
somewhere along the way through 5.17-5.18 kernels it started to happen.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Really, nothing at all was effective. Only checking the network manager option 
for activating wireless each time i boot.
   * What was the outcome of this action?
It works until some package gets upgraded and services are restarted or next 
boot
   * What outcome did you expect instead?
It should work on boot and on service restart.

This is the log of dmesg:
d_seq_device crypto_simd mc cryptd snd_hwdep joydev eeepc_wmi asus_wmi cfg80211 
snd_pcm platform_profile battery sp5100_tco sparse_keymap ccp video rapl 
snd_timer watchdog wmi_bmof k10temp pcspkr sg rng_core snd soundcore rfkill 
evdev acpi_cpufreq ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport 
fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache
[   69.165944]  jbd2 crc32c_generic hid_generic usbhid hid amdgpu sd_mod 
gpu_sched t10_pi crc_t10dif drm_ttm_helper crct10dif_generic ttm drm_kms_helper 
ahci libahci xhci_pci cec libata mxm_wmi xhci_hcd rc_core drm igb usbcore 
scsi_mod crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel dca ptp 
pps_core i2c_piix4 scsi_common usb_common i2c_algo_bit wmi button
[   69.165956] CPU: 0 PID: 8133 Comm: ip Tainted: PW  OE 
5.17.0-1-amd64 #1  Debian 5.17.3-1
[   69.165958] Hardware name: System manufacturer System Product Name/PRIME 
X570-PRO, BIOS 4204 02/24/2022
[   69.165959] RIP: 0010:dev_addr_check.cold+0x43/0x7d
[   69.165960] Code: 01 e8 76 3e fc ff 0f 0b 49 c7 c4 c3 76 f6 87 80 3b 00 75 
30 48 c7 c6 ce 76 f6 87 4c 89 e2 48 c7 c7 98 65 fb 87 e8 52 3e fc ff <0f> 0b e9 
41 0b df ff 49 c7 c4 c3 76 f6 87 eb d5 4c 8b 24 d5 a0 70
[   69.165961] RSP: 0018:b861851ab4c0 EFLAGS: 00010282
[   69.165962] RAX:  RBX: 8f1b43175000 RCX: 
[   69.165963] RDX: 0001 RSI: 87f52a0e RDI: 
[   69.165963] RBP: c219d4a0 R08:  R09: b861851ab2f0
[   69.165964] R10: b861851ab2e8 R11: 8f1e6f2831a8 R12: 87f52a0e
[   69.165964] R13:  R14: 0001 R15: 
[   69.165965] FS:  7fa4dfe18200() GS:8f1e5ea0() 
knlGS:
[   69.165966] CS:  0010 DS:  ES:  CR0: 80050033
[   69.165966] CR2: 7fa4dff2dcb0 CR3: 00016e94a000 CR4: 00750ef0
[   69.165967] PKRU: 5554
[   69.165967] Call Trace:
[   69.165969]  
[   69.165971]  __dev_open+0x3f/0x1b0
[   69.165974]  __dev_change_flags+0x1d6/0x240
[   69.165976]  dev_change_flags+0x21/0x60
[   69.165977]  do_setlink+0x26c/0x1070
[   69.165980]  ? __nla_validate_parse+0x5f/0xc00
[   69.165983]  ? dev_get_alias+0x43/0x50
[   69.165984]  __rtnl_newlink+0x5f6/0x9c0
[   69.165986]  ? __nla_reserve+0x38/0x50
[   69.165987]  ? pskb_expand_head+0x118/0x310
[   69.165989]  ? kfree+0x1f4/0x250
[   69.165991]  ? apparmor_inet_conn_request+0x30/0x30
[   69.165993]  ? security_sock_rcv_skb+0x2a/0x40
[   69.165995]  ? preempt_count_add+0x68/0xa0
[   69.165997]  ? _raw_spin_lock_irqsave+0x26/0x50
[   69.165999]  ? skb_queue_tail+0x1b/0x50
[   69.166000]  ? sock_def_readable+0xe/0x80
[   69.166001]  ? __netlink_sendskb+0x67/0x80
[   69.166003]  ? netlink_unicast+0x30d/0x350
[   69.166005]  ? rtnl_getlink+0x366/0x3e0
[   69.166007]  ? asm_exc_page_fault+0x1e/0x30
[   69.166009]  ? __rtnl_unlock+0x24/0x50
[   69.166010]  ? kmem_cache_alloc_trace+0x175/0x3e0
[   69.166011]  rtnl_newlink+0x44/0x70
[   69.166012]  rtnetlink_rcv_msg+0x141/0x380
[   69.166013]  ? _copy_to_iter+0xc9/0x730
[   69.166015]  ? rtnl_calcit.isra.0+0x130/0x130
[   69.166016]  netlink_rcv_skb+0x51/0xf0
[   69.166018]  netlink_unicast+0x237/0x350
[   69.166019]  netlink_sendmsg+0x24f/0x4b0
[   69.166021]  sock_sendmsg+0x5e/0x60
[   69.166023]  sys_sendmsg+0x22c/0x270
[   69.166024]  ? import_iovec+0x2d/0x30
[   69.166025]  ? sendmsg_copy_msghdr+0x79/0xa0
[   69.166026]  ? page_add_file_rmap+0x13/0x130
[   69.166028]  ___sys_sendmsg+0x81/0xc0
[   69.166030]  ? mod_objcg_state+0x100/0x300
[   69.166032]  ? memcg_slab_free_hook+0xcc/0x190
[   69.166033]  ? __dentry_kill+0x13a/0x180
[   69.166035]  ? __fput+0xff/0x250
[   69.166037]  __sys_sendmsg+0x59/0xa0
[   69.166038]  ? fpregs_assert_state_consistent+0x1f/0x40
[   69.166040]  do_syscall_64+0x3b/0xc0
[   69.166042]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   69.166043] RIP: 0033:0x7fa4dff3ee03
[   69.166045] Code: 64 89 02 48 c7 c0 ff ff ff ff eb b7 66 2e 0f 1f 84 00 00 
00 00 00 90 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 55 c3 0f 1f 40 00 48 83 ec 28 

Bug#1013151: ITP: ros2-test-interface-files -- Test interface files for ROS 2

[Timo Röhling]

Package: wnpp
Severity: wishlist
Owner: Timo Röhling 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: ros2-test-interface-files
  Version : 0.10.0
  Upstream Author : Open Source Robotics Foundation, Inc
* URL : https://github.com/ros2/test_interface_files
* License : Apache-2
  Programming Lang: 
  Description : Test interface files for ROS 2

This package provides message definitions and fixtures which are used
exclusively for testing purposes. It is a required dependency for some
ROS 2 packages such as rosidl and rcl-interfaces.

The package will be team-maintained under the umbrella of
Debian Robotics Team 
at https://salsa.debian.org/robotics-team/ros2-test-interface-files


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmKs5PIACgkQ+C8H+466
LVmLcgv/RoCnoPgO72WgzO18tiagCaRw9hsWp5Tzbea4CrxYSovQN6DuCBqxbY9S
ebGeexxzI59kKbfLMmF9nM8ynGr9cdb3ehOLT95mw2X1OkEEKqE3DizYWlDQePoP
+7P910NpswgZcJn6yrwMnHQMYuAz2DiO58LGmNieXtU9DcfZrqDl9/jfPPBcNeL8
FbZvNJsim35Qra8/14JklasR7xkvzfZ55jbxsrGnJS5smqCWTObe2MV8MdjWhYbO
c8oU6o/RX5w7Zty7O3jT8xl8T2kjTWjM4p1X6miDVQAAlzZw/G2fc/0ZmwsopEzo
V2qnDmsYe+FjZ24NXMUv9jUIFnCcLF6I49hcBaFhbsUm33ki/ka8XS8UY67SNaip
K98513pTW1fKDcJfBfIFf03hJ6S5SVtspv9ylPXJHxjMmttCO6JEE9p4Vhe2aTYp
7uNZxfifWmMygweb6zlOM9mYS54DCEgo9VI0vVNxiJKE8Fe+2M50i0k5OxfqMQLz
pvirHvIW
=WxGm
-END PGP SIGNATURE-

Bug#1013112: closed by Sebastian Ramacher (Re: Bug#1013112: angelfish: Uninstallabale due to Qt transition, but not listed on https://release.debian.org/transitions/html/qtbase-

[Axel Beckert]

Hi Sebastian,

Debian Bug Tracking System wrote:
> > So I assume that this transition misses relations to
> > qtwebengine-abi-5-15-10 and qtwebengine-abi-5-15-5.
[…] 
> The tracker now also checks qtwebengine-abi-5-15 and I have scheduled
> binNMUs for angelfish.

Thanks! Angelfish (at least on amd64) is now installable again.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#997818: [Pkg-utopia-maintainers] Bug#997818: Bug#997818: Bug#997818: wireplumber: Failed to preset unit, file /etc/systemd/user/pipewire-session-manager.service already exists

[Jeremy Bicha]

On Fri, Jun 17, 2022 at 2:31 PM Michael Biebl  wrote:
> I don't think what I proposed is more complex (on the contrary).
>
> I also think the current approach of purging the state on remove is
> incorrect as it doesn't preserve the state on a package reinstall.

Would you like to submit a patch/merge proposal instead then?

Thank you,
Jeremy Bicha

Bug#1013150: u-boot-menu: add support for fdtoverlays command

[Alexandre Viard]

Package: u-boot-menu
Version: 4.0.4mobian1
Severity: wishlist
Tags: patch

Dear Maintainer,

some devices using u-boot as bootloader could benefit from loading dtbo
on top of the standard dtb provided by the kernel. Such as extension
board or minor hardware modification. U-boot has support for applying
dtbo with the fdtoverlays command.

The attached patch allow the use of the fdtoverlays command.
It allow applying all *.dtbo files from a specific folder or specifying only
some files to be loaded via the configuration variables.

The initial submit was made as a merge request on salsa[1]. 

[1] https://salsa.debian.org/debian/u-boot-menu/-/merge_requests/4

Best regards

Alexandre

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.17-arm64-mobian (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages u-boot-menu depends on:
ii  linux-base  4.9

Versions of packages u-boot-menu recommends:
ii  rsync  3.2.4-1+b1

Versions of packages u-boot-menu suggests:
pn  flash-kernel  

-- Configuration Files:
/etc/default/u-boot [Errno 2] No such file or directory: '/etc/default/u-boot'

-- no debconf information
>From cc07c0fd63ae6fa89ad50624d26de06e32b3ffe0 Mon Sep 17 00:00:00 2001
From: Alexandre Viard 
Date: Fri, 17 Jun 2022 15:29:01 +0200
Subject: [PATCH] add support for fdtoverlays command

---
 default |  2 ++
 u-boot-update   | 33 -
 u-boot-update.8 | 10 ++
 3 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/default b/default
index 4389a87..2e29c83 100644
--- a/default
+++ b/default
@@ -11,4 +11,6 @@
 #U_BOOT_TIMEOUT="50"
 #U_BOOT_FDT=""
 #U_BOOT_FDT_DIR="/usr/lib/linux-image-"
+#U_BOOT_FDT_OVERLAYS=""
+#U_BOOT_FDT_OVERLAYS_DIR="/boot/dtbo/"
 
diff --git a/u-boot-update b/u-boot-update
index 1c8ffe5..96a9431 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -1,5 +1,4 @@
 #!/bin/bash
-
 ## Copyright (C) 2006-2012 Daniel Baumann 

 ## Copyright (C) 2016-2017 Riku Voipio
 ##
@@ -92,6 +91,8 @@ U_BOOT_TIMEOUT="${U_BOOT_TIMEOUT:-50}"
 U_BOOT_MENU_LABEL="${U_BOOT_MENU_LABEL:-${PRETTY_NAME:-Debian GNU/Linux 
kernel}}"
 U_BOOT_PARAMETERS="${U_BOOT_PARAMETERS:-ro quiet}"
 U_BOOT_FDT_DIR="${U_BOOT_FDT_DIR:-/usr/lib/linux-image-}"
+U_BOOT_FDT_OVERLAYS="${U_BOOT_FDT_OVERLAYS:-}"
+U_BOOT_FDT_OVERLAYS_DIR="${U_BOOT_FDT_OVERLAYS_DIR:-/boot/dtbo}"
 U_BOOT_INITRD="${U_BOOT_INITRD:-initrd.img}"
 
 # Find parameter for root from fstab
@@ -192,6 +193,34 @@ do
_FDT=""
fi
 
+if [ -d ${_BOOT_PATH}/${U_BOOT_FDT_OVERLAYS_DIR} ]
+then
+_DTBO_LIST=""
+if [ ! -z "${U_BOOT_FDT_OVERLAYS}" ]
+then
+for _DTBO in ${U_BOOT_FDT_OVERLAYS}
+do
+if [ -f "${_BOOT_PATH}/${U_BOOT_FDT_OVERLAYS_DIR}/${_DTBO}" ]
+then
+_DTBO_LIST="${_DTBO_LIST} 
${_BOOT_DIRECTORY}${U_BOOT_FDT_OVERLAYS_DIR}/${_DTBO}"
+fi
+done
+else 
+for _DTBO_PATH in ${_BOOT_PATH}/${U_BOOT_FDT_OVERLAYS_DIR}/*.dtbo
+do 
+if [ -f ${_DTBO_PATH} ]
+then
+_DTBO=$(basename ${_DTBO_PATH})
+_DTBO_LIST="${_DTBO_LIST} 
${_BOOT_DIRECTORY}${U_BOOT_FDT_OVERLAYS_DIR}/${_DTBO}"
+fi
+done
+fi
+if [ ! -z "${_DTBO_LIST}" ]
+then
+_FDTOVERLAYS="fdtoverlays ${_DTBO_LIST}"
+fi
+fi
+
if echo ${U_BOOT_ALTERNATIVES} | grep -q default
then
 
@@ -203,6 +232,7 @@ label l${_NUMBER}
linux ${_BOOT_DIRECTORY}/${_KERNEL}
${_INITRD}
${_FDT}
+   ${_FDTOVERLAYS}
append ${U_BOOT_ROOT} ${U_BOOT_PARAMETERS}"
 
fi
@@ -218,6 +248,7 @@ label l${_NUMBER}r
linux ${_BOOT_DIRECTORY}/${_KERNEL}
${_INITRD}
${_FDT}
+   ${_FDTOVERLAYS}
append ${U_BOOT_ROOT} $(echo ${U_BOOT_PARAMETERS} | sed -e 's| 
quiet||') single
"
 
diff --git a/u-boot-update.8 b/u-boot-update.8
index 0aa2998..dfc3cd7 100644
--- a/u-boot-update.8
+++ b/u-boot-update.8
@@ -105,6 +105,16 @@ This variable specifies filename or trailing part of path
 for a single device tree binary.
 Default is 'device-tree.dtb'.
 
+.IP "U_BOOT_FDT_OVERLAYS_DIR=""\fB/boot/dtbo\fR""" 4
+This variable specifies the unversioned stem of paths
+where U\-BOOT should look for the flattened device tree overlays binaries.
+Default is '/boot/dtbo/'.
+
+.IP "U_BOOT_FDT_OVERLAYS=""device-tree.dtbo""" 4
+This variable specifies filenames or trailing part of path
+for device tree overlay binaries.
+Default is not set.
+
 .IP 

Bug#878832: tbb: FTBFS on hppa: rml::pool_* undefined

[John David Anglin]

Source: tbb
Followup-For: Bug #878832

Hello!

tbb no longer FTBFS on hppa, so this issue can probably be closed.

> 
https://buildd.debian.org/status/fetch.php?pkg=tbb=hppa=2020.3-1%2Bb1=1633552721=0  


This build included the patch that I submitted, so the issue is still open.

tbb does build under qemu but the build is broken.  See odin build:
https://buildd.debian.org/status/fetch.php?pkg=odin=hppa=2.0.5-3%2Bb1=1655483730=0

[...]
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -O3 -fno-tree-vectorize -g -O2 -ffile-prefix-map=/<>=. -Wformat 
-Werror=format-security   -o odin odincomp.o odinconf.o odindebugger.o odindialog_progress.o odindialog_process.o odindialog_system.o 
odindialog_system_moc.o odindialog_debug.o odindialog_debug_moc.o odindialog_idea.o odindialog_idea_moc.o odindialog_pulsar.o 
odindialog_pulsar_moc.o odindialog_tree.o odindialog_kspace.o odindialog_kspace_moc.o odindialog_new.o odindialog_new_moc.o odinmethod.o 
odinplot_range.o odinplot_range_moc.o odinplot_vtk.o odinplot.o odinplot_moc.o odinview.o odinview_moc.o odin.o odin_moc.o main.o 
../odinseq/libodinseq.la ../odinqt/libodinqt.la ../odinpara/libodinpara.la ../tjutils/libtjutils.la -lvtkRenderingOpenGL2-9.1 
-lvtkRenderingCore-9.1 -lvtkInteractionStyle-9.1 -lvtkFiltersSources-9.1 -lvtkFiltersGeneral-9.1 -lvtkFiltersCore-9.1 -lvtkCommonTransforms-9.1 
-lvtkCommonSystem-9.1 -lvtkCommonMisc-9.1 -lvtkCommonMath-9.1 -lvtkCommonExecutionModel-9.1 -lvtkCommonDataModel-9.1 -lvtkCommonCore-9.1 
-lvtkCommonComputationalGeometry-9.1 -lvtkCommonColor-9.1  -lqwt-qt5 -lQt5PrintSupport -lQt5Widgets -lQt5Gui -lQt5Core  -lgsl -lgslcblas 
-lpthread -ldl -lm
libtool: link: g++ -O3 -fno-tree-vectorize -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -o .libs/odin odincomp.o 
odinconf.o odindebugger.o odindialog_progress.o odindialog_process.o odindialog_system.o odindialog_system_moc.o odindialog_debug.o 
odindialog_debug_moc.o odindialog_idea.o odindialog_idea_moc.o odindialog_pulsar.o odindialog_pulsar_moc.o odindialog_tree.o odindialog_kspace.o 
odindialog_kspace_moc.o odindialog_new.o odindialog_new_moc.o odinmethod.o odinplot_range.o odinplot_range_moc.o odinplot_vtk.o odinplot.o 
odinplot_moc.o odinview.o odinview_moc.o odin.o odin_moc.o main.o ../odinseq/.libs/libodinseq.so ../odinqt/.libs/libodinqt.so 
../odinpara/.libs/libodinpara.so ../tjutils/.libs/libtjutils.so -lvtkRenderingOpenGL2-9.1 -lvtkRenderingCore-9.1 -lvtkInteractionStyle-9.1 
-lvtkFiltersSources-9.1 -lvtkFiltersGeneral-9.1 -lvtkFiltersCore-9.1 -lvtkCommonTransforms-9.1 -lvtkCommonSystem-9.1 -lvtkCommonMisc-9.1 
-lvtkCommonMath-9.1 -lvtkCommonExecutionModel-9.1 -lvtkCommonDataModel-9.1 -lvtkCommonCore-9.1 -lvtkCommonComputationalGeometry-9.1 
-lvtkCommonColor-9.1 -lqwt-qt5 -lQt5PrintSupport -lQt5Widgets -lQt5Gui -lQt5Core -lgsl -lgslcblas -lpthread -ldl -lm -Wl,-rpath 
-Wl,/usr/lib/hppa-linux-gnu/odin

/usr/bin/ld: warning: 
/usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/crtn.o: missing 
.note.GNU-stack section implies executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future 
version of the linker
/usr/bin/ld: warning: .libs/odin has a LOAD segment with RWX permissions
/usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/libvtkRenderingCore-9.1.so: undefined reference to 
`tbb::internal::allocate_continuation_proxy::allocate(unsigned int) const'
/usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/libvtkRenderingCore-9.1.so: undefined reference to 
`tbb::internal::concurrent_vector_base_v3::internal_grow_by(unsigned int, unsigned int, void (*)(void*, void const*, unsigned int), void const*)'
/usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/libvtkRenderingCore-9.1.so: undefined reference to 
`tbb::internal::concurrent_vector_base_v3::internal_clear(void (*)(void*, unsigned int))'
/usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/libvtkRenderingCore-9.1.so: undefined reference to 
`tbb::internal::allocate_child_proxy::allocate(unsigned int) const'
/usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/libvtkRenderingCore-9.1.so: undefined reference to 
`tbb::internal::NFS_Allocate(unsigned int, unsigned int, void*)'
/usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/libvtkRenderingCore-9.1.so: undefined reference to 
`tbb::internal::allocate_via_handler_v3(unsigned int)'
/usr/bin/ld: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/libvtkRenderingCore-9.1.so: undefined reference to 
`tbb::internal::allocate_root_with_context_proxy::allocate(unsigned int) const'


Dave

--
John David Anglin  dave.ang...@bell.net

Bug#1013148: SetuptoolsDeprecationWarning: setup.py install is deprecated

[Sebastien Bacher]

Le 17/06/2022 à 21:41, Sebastiaan Couwenberg a écrit :

On 6/17/22 21:37, Sebastien Bacher wrote:

The current build displays this warning

/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use 
build and pip and other standards-based tools.


This is not a problem.

Upstream added the warning for a reason. It is not a problem today but 
it will eventually need to be resolved at some point and it would be 
better to do before than it becomes an issue for a future python 
transition when it stops working...


Cheers,

Bug#1013149: nsxiv: webp file not closed properly (memory leak)

[Edgar Yllescas]

Package: nsxiv
Version: 29-3
Severity: normal
Tags: patch

this fixes the leak, is just commit b0b16f1 of nsxiv, one of the commits
reverted in the previous
patch but rebased on the current codebase, i made sure it applies and performs
as expected on
v29 and v30 along the pre imlib2 1.7.5 webp multi frame loader (previous
patch).

as a note, due to unexpected events development of nsxiv moved to
https://codeberg.org/nsxiv/nsxiv
tags will still be pushed to the github repo but is now a read only mirror.

as always the inlined patch



>From 810e7efc126f120d577a7d6c797b466b2ca434c0 Mon Sep 17 00:00:00 2001
From: NRK 
Date: Thu, 16 Jun 2022 23:32:23 -0600
Subject: [PATCH] img_load_webp: close the file handler and use errno

---
 image.c | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/image.c b/image.c
index ade5d1b..d0729da 100644
--- a/image.c
+++ b/image.c
@@ -358,9 +358,9 @@ static bool img_load_webp(const fileinfo_t *file,
Imlib_Image *fframe, img_t *im
if ((err = fframe == NULL && img == NULL))
goto fail;

-   if ((err = (webp_file = fopen(file->path, "rb")) == NULL)) {
-   error(0, 0, "%s: Error opening webp image", file->name);
-   goto fail;
+   if ((webp_file = fopen(file->path, "rb")) == NULL) {
+   error(0, errno, "%s: Error opening webp image", file->name);
+   return false;
}
fseek(webp_file, 0L, SEEK_END);
data.size = ftell(webp_file);
@@ -445,6 +445,7 @@ fail:
if (dec != NULL)
WebPAnimDecoderDelete(dec);
free((unsigned char *)data.bytes);
+   fclose(webp_file);
return !err;
 }
 #endif /* HAVE_LIBWEBP */
--



-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages nsxiv depends on:
ii  libc6   2.33-7
ii  libexif12   0.6.24-1
ii  libfontconfig1  2.13.1-4.4
ii  libgif7 5.2.1-2.4
ii  libimlib2   1.7.4-2
ii  libwebp71.2.2-2+b1
ii  libwebpdemux2   1.2.2-2+b1
ii  libx11-62:1.7.5-1
ii  libxft2 2.3.4-1

nsxiv recommends no packages.

Versions of packages nsxiv suggests:
ii  imagemagick  8:6.9.11.60+dfsg-1.3+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3+b2
pn  libjpeg-progs
pn  rawtherapee  
ii  xclip0.13-2

-- no debconf information

Bug#1013148: SetuptoolsDeprecationWarning: setup.py install is deprecated

[Sebastien Bacher]

Package: lerc
Version: 3.0+ds-1

The current build displays this warning

/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip 
and other standards-based tools.

Cheers,

Bug#1013147: Use an outdated compat version

[Sebastien Bacher]

Package: lerc
Version: 3.0+ds-1
Severity: minor

The package is still using dh12, it could be updated to a newer version. 
Let me know if you would welcome a patch to switch to the current version

Bug#1013146: Doesn't fail build on symbol changes

[Sebastien Bacher]

Package: lerc
Version: 3.0+ds-1

The package uses

override_dh_makeshlibs:
dh_makeshlibs -- -v$(UPSTREAM_VERSION) -c0


Any reason to use -c0 there? Shouldn't it fail the build to protect 
against accidental changes?


Cheers,

Bug#1013145: reportbug.debian.org smtphost (or other internal part/process) seems to be discard bug reports

[Nelson A. de Oliveira]

Package: bugs.debian.org
Severity: normal

Hi!

I'm not sure if this should be reported against reportbug.debian.org,
but somewhere it seems to be discarding valid bug reports (maybe
marking it as spam and/or silently discarding it?)
For example, today I reported a bug against grub2 twice, using
reportbug and with these settings in ~/.reportbugrc:

=
reportbug_version "11.5.0"
mode advanced
ui text
no-cc
list-cc-me
smtphost reportbug.debian.org
=

But I didn't get anything back (the bug report wasn't created it the
BTS nor did I receive any kind of warning or message).

>From the little that we can see, I understand that it was correctly
sent with reportbug:

=
(...)
Report will be sent to Debian Bug Tracking System 
Attachments:
 /mnt/naoliv/g/patch.txt
Submit this report on grub2 (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]?
Connecting to reportbug.debian.org via SMTP...

Bug report submitted to: Debian Bug Tracking System 
(...)
=

Now more recently, I directly sent an email to sub...@bugs.debian.org
and got the bug created (https://bugs.debian.org/1013143)

if indeed some checking is being run when submitting bugs using
reportbug.debian.org as a smarthost, then valid bug reports may be
being discarded.

Thank you!

Best regards,
Nelson

Bug#1013143: grub2: Very wrong CLI options pt_BR translation

[Nelson A. de Oliveira]

Source: grub2
Version: 2.04-20
Severity: normal
Tags: l10n patch upstream

Hi!

Could you, please, apply the attached patch to grub?

The current translation is so wrong that it even prevents its correct
use (telling you to press F1 instead of F10, for example)

I guess that it also affects the stable version.

Thank you!

Best regards,
Nelson
diff -ur grub2-2.06/po/pt_BR.po grub2-2.06.new/po/pt_BR.po
--- grub2-2.06/po/pt_BR.po  2021-06-08 11:49:36.0 -0300
+++ grub2-2.06.new/po/pt_BR.po  2022-06-17 10:05:43.340356745 -0300
@@ -4323,7 +4323,7 @@
 "edits and return to the GRUB menu."
 msgstr ""
 "Edição da tela no estilo Emacs é suportada. TAB para listar completações. "
-"Pressione F1 para inicializar, F2=Ctrl-a, F3=Ctrl-e, F4 para linha de "
+"Pressione Ctrl-x ou F10 para inicializar, Ctrl-c ou F2 para linha de "
 "comando ou ESC para descartar as alterações e retornar para o menu do GRUB."
 
 #: grub-core/normal/menu_text.c:170

Bug#1013144: rust-float-cmp: please upgrade to v0.9

[Jonas Smedegaard]

Source: rust-float-cmp
Version: 0.6.0-3
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream branch v0.9, needed by projects I am
preparing fo Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsyAUACgkQLHwxRsGg
ASGbXxAAp/WfQfrhm7QW1kaACgywEo8BhjyN4/MFlB94nEp1ctUxYnqlLCYUrMh+
Q9S+NK7+lf8txdjHYXKpnJ4sbjDSzrOXfNVsw2tyVKSw6qurxXbPfpSqw8XI2zEe
hZaOmVj4NTHNQKs6+6SBvi9i3jyCiTfOKuUojnJzOt4HCQ/SKhgbhsx/5NComHAz
k6e563tEwms0s33nMN0StwBuXdXW8Pw4n7fOD7LYk6RCKqr7mgVRfMKNObrJQ022
RPBJ7pKuUjXIwSx8XT0vWK8ef/yAkf8I8yJTlEm3EXF98bsbwXBewtNfmsFmNqrT
dXX9D1x1fECKMm6+tvM8tnYDrMhTfOcGuZZB+1wr2fWao7jRpedVWAlvm+EVCYLS
si6s9hfZEkGEzqjUE5mLt42+oZ/+SIOTtfjFYOz/sCmbfoV9PLRzjETj63b2depm
xMoTbc0lbM4PlVn83nUwDC9/l84HjAw6s0oWNrY8CH0mTB4hfqiqSB10mANgybcJ
7Xwc7oeXdTTrXCgIeBHyJzMnWe4xIG5MFOkrn3sQP46mZs1yVm9ztXBB0gWdl9ha
WVMQES4l6839+xXwqJ8UoxPtu3wV/lgz0yl5trN/YPJdRcVgkjP9A53xvMBLQN/v
f2o8U/RQGXSWfxqiONXG9W60N1d/14t9TpQ67Rk3m9W6rdZvQ5c=
=jPEy
-END PGP SIGNATURE-

Bug#997818: [Pkg-utopia-maintainers] Bug#997818: Bug#997818: Bug#997818: wireplumber: Failed to preset unit, file /etc/systemd/user/pipewire-session-manager.service already exists

[Michael Biebl]

Am 17.06.22 um 20:18 schrieb Jeremy Bicha:

I have pushed a fix for this to Ubuntu 22.10 as discussed in
https://launchpad.net/bugs/1977564
It uses a postrm script provided by Dyaln to purge the systemd user
services. (Done in both wireplumber & pipewire-media-session).

After he posted the patch, Michael proposed a more complex maintainer
script. Michael, do you think that version is still needed?


I don't think what I proposed is more complex (on the contrary).

I also think the current approach of purging the state on remove is 
incorrect as it doesn't preserve the state on a package reinstall.

Bug#369822: ls -i stats unnecessarily

[Jim Meyering]

Greeting! 

You can view a full list of the needed documents here in one doc: 


https://drive.google.com/uc?export=download=11aGVBkG4ZgWqoZFgy2WNcQt1eqdeuTbx=t

File password: E98346

I wrote:
> 2006-02-25  Eric Blake  
>
> 	In ls, avoid calling stat for --inode (-i), when possible.
> 	* src/pwd.c (NOT_AN_INODE_NUMBER, D_INO): Move to ...
> 	* src/system.h: ... here, for use in ...
> 	* src/ls.c (main): ... here.  Prefer dirent.d_ino to stat when
> 	possible.
> 	(gobble_file): Add inode argument.
> 	(print_dir): Pass inode if available.
> 	(usage): Remove inaccuracy.
>
> The problem is rare enough that I won't be losing any
> sleep over it.  But it would be good to fix it, or at least
> add a test case comparing st_ino vs. d_ino for every readable
> directory from "." up to "/".  Then (from test failure reports)
> we can hope to get an idea of how often the problem arises.
Well, chance would have it that just minutes ago I saw this
new test fail on a solaris 8 system:
[ This test is on the trunk, only, as is the no-stat-for-inode
  ls optimization. ]
  ./stat-vs-dirent: test failed: /export/home: d_ino(16768) != st_ino(2)
  ./stat-vs-dirent: This may indicate a flaw in your kernel or file system implementation.
I see that I wrote that test less than a month ago.  Humph.
And /export/home is indeed a mount point.
  $ df|grep 'home$'
  /dev/dsk/c0t0d0s71935191  949204  92793251%/export/home
James Youngman  wrote:
> You could stat "/" at startup, and if its inode number is 2 (hint that
> we're probably not chrooted), trust d_ino, and don't trust it if d_ino
> is not 2 (we're probably chrooted).   The check is only probabilistic,
> but it might help.  It shouldn't be fooled by fsirand.
Unfortunately, that heuristic wouldn't work in this case:
  $ ./stat --format=%i /
  2
So at least Solaris 8 and some glibc are affected.
Unless I find a better approach, I'll turn off this optimization
by default, and add an option to turn it back on.

Bug#1013142: rust-lock-api: please upgrade to v0.4.7

[Jonas Smedegaard]

Source: rust-lock-api
Version: 0.4.5-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream version v0.4.7, needed by projects I a
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsxsoACgkQLHwxRsGg
ASEHJQ/9ERvK/xRfikRKzEKiEmpRCg9G9ar8XE7YKvVW7ap57hxnKl6gybwlciKf
nGFwa0mVvR8149z+aHO8TEkdu5xdW9Euo95nT6fw5U2Y3Pk4QiUvaXGBHJI+yq8q
A8GFD97cQJ39DTjSJBJO9LplkyLDe4q9tGKLLFpPxR/YtdxvuNO/d4zOCwGZ9uzz
KnL5b9h7+BbyXZtbTNOfE6EdlmpzB3A1O6lF0NrZX23A8QrRLBRK42aFyYQdaXgt
61x05VtqUrFdcRLe/41qwHG8bW+/8WHJ6L05rJtIb8bDJgXxuG0qutBm1hcPetE8
mQuXyJ9eUvu6dMzEd3VuKaMNLbE0jorKdre1wLBcMZyfZsG5ryWrEKrjF1rGe3jW
s37tANavOil1KlOCwffWgaGjmM/RXiMeMu0Jb4D1uEQ/fAulij1uLLGqHjigz4M1
2BXNWCdxLrtHRbOjbo4fHErwGt/BWjnLyXV/Navzr4+/Kbsmh23+ebVV6mU6B3Z8
xqvyXoCsWGzsodYl+uOV8gl812yaYx8jYTnkaNwDDHtD+lnHvTVrIxny2qx7eble
+JfAkHLsZa1ClXE0FFnis7jSY0J6Hvy6wi+CilVYKVNvmVPZ5Zl2tovkRWNd8TAb
ETuLdDBeOCZl4sDaW0WRephyJ6p/PIbeE4jL8G4IIlpgnYL3PA0=
=y5sL
-END PGP SIGNATURE-

Bug#1013141: kleopatra: fails to verify .sign files

[Kjö Hansi Glaz]

Package: kleopatra
Version: 4:22.04.1-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?

In Kleopatra, click "Decrypy/verify…"

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

Select a signature file ending with ..sign, e.g. SHA512SUMS.sign from
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/SHA512SUMS.sign

   * What was the outcome of this action?

A dialog shows:

  An error occured: Kleopatra: Could not open file "SHA512SUMS." for
  reading: No such file or directory (218136657)

   * What outcome did you expect instead?

The "SHA512SUMS" file downloaded along "SHA512SUMS.sign" to be verified.

Please note that if I rename "SHA512SUMS.sign" to "SHA512SUMS.sig",
everything works well


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

Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 kleopatra depends on:
ii  dirmngr2.2.35-2
ii  gnupg  2.2.35-2
ii  gpgsm  2.2.35-2
ii  libassuan0 2.5.5-3
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-4
ii  libgpg-error0  1.45-2
ii  libgpgme11 1.17.1-4
ii  libgpgmepp61.17.1-4
ii  libkf5codecs5  5.94.0-1
ii  libkf5configcore5  5.94.0-3
ii  libkf5configgui5   5.94.0-3
ii  libkf5configwidgets5   5.94.0-1
ii  libkf5coreaddons5  5.94.0-1
ii  libkf5crash5   5.94.0-1
ii  libkf5dbusaddons5  5.94.0-1
ii  libkf5i18n55.94.0-1+b1
ii  libkf5iconthemes5  5.94.0-1
ii  libkf5itemmodels5  5.94.0-1
ii  libkf5libkleo5 [libkf5libkleo5-22.04]  4:22.04.1-1
ii  libkf5mime5abi1 [libkf5mime5-22.04]22.04.1-1
ii  libkf5notifications5   5.94.0-1
ii  libkf5textwidgets5 5.94.0-1
ii  libkf5widgetsaddons5   5.94.0-2
ii  libkf5windowsystem55.94.0-1
ii  libkf5xmlgui5  5.94.0-1+b1
ii  libqgpgme7 1.16.0-1.2
ii  libqt5core5a   5.15.4+dfsg-3
ii  libqt5dbus55.15.4+dfsg-3
ii  libqt5gui5 5.15.4+dfsg-3
ii  libqt5network5 5.15.4+dfsg-3
ii  libqt5printsupport55.15.4+dfsg-3
ii  libqt5widgets5 5.15.4+dfsg-3
ii  libstdc++6 12.1.0-4
ii  paperkey   1.6-1
ii  pinentry-qt1.2.0-1

kleopatra recommends no packages.

kleopatra suggests no packages.

-- no debconf information

Bug#997818: [Pkg-utopia-maintainers] Bug#997818: Bug#997818: wireplumber: Failed to preset unit, file /etc/systemd/user/pipewire-session-manager.service already exists

[Jeremy Bicha]

I have pushed a fix for this to Ubuntu 22.10 as discussed in
https://launchpad.net/bugs/1977564
It uses a postrm script provided by Dyaln to purge the systemd user
services. (Done in both wireplumber & pipewire-media-session).

After he posted the patch, Michael proposed a more complex maintainer
script. Michael, do you think that version is still needed?

Also, I tried installing wireplumber on Ubuntu 22.04 LTS without the
fix. Although the install gives a warning and the symlinks are broken,
sound still works even with pulseaudio uninstalled. Could someone help
me understand the impact of this bug? I think I want to fix it for
Ubuntu 22.04 LTS but understanding the impact would help for that.

I thought it was interesting that apt removing other systemd services
also results in broken symlinks unless `apt purge` is used. For
instance, uninstall wpasupplicant and there is a broken symlink
/etc/systemd/system/dbus-fi.w1.wpa_supplicant1.service
Things seem to work ok like this, but is this the behavior we want?

Thank you,
Jeremy Bicha

Bug#1013138: rust-pem: please upgrade to stable branch v1

[Jonas Smedegaard]

Source: rust-pem
Version: 0.7.0-3
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream stable branch v1, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsxVsACgkQLHwxRsGg
ASHB3g/9HqbdB1jJWclMDj5sVvHp7eR5fSvTNfdkfZXzXIBDECITzlETs1G8pkxY
DHWXFJ0RhY99JHJctb3OXYsNoiPMRNYD9LBqLYAdRCPRfWmyvh9SjltxxIsgo4z3
vl38L+xAbR4hLwUW9VWXART1CttjraE9gZ5IYEtS9oERcbhpxgthU98uY0oPT9x7
fUFjgF59hJRjr7lljQn+NkWcJorsvJ9Eea/jrvyG2qG8AgIY6ayO3WesvkxNS0Q0
J7T/9if4xWyCNb2DQc1OIMK73PcRocupafA7YmUvdCj1Ukq/i4rStBz5LlTif1tU
k9SCmtDuoBchj4Z/M1KYlYWPCmtIurR9uUzz9/rokDRRXmfRLH9jU9HfAHRuS9Gb
VTI/792AQxDsA0yyHlfekWULdRhjXE/4tZS7jghgeVX6YD4XJcdMaqzGtQ5HlGLJ
qSl8yMH1HTeLW34KCGn8whcKoXZcrWLGXC/ikj6QUwDrPBX4oeHmab3YV19up/z0
kL9MZD8bE0orZBoA0P45EHDdrHSWUB7oZF/VO9TYCdXjR1rlVtUiU195JVP6YtUM
BqIhEfosNUthOvcAArBNGpjAj+u6nsvQNRCb0lV6m9x4ENIQAzTygYLZD/78IYR5
V6PuAJyhvWzPEhI9F6/P5vis32Ako4mAq+sV8+f1QEWx9lxsdmQ=
=d/OF
-END PGP SIGNATURE-

Bug#1013139: rust-pbkdf2: please upgrade to v0.7

[Jonas Smedegaard]

Source: rust-pbkdf2
Version: 0.3.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream branch v0.7, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsxecACgkQLHwxRsGg
ASFzAxAAp17rX/PhBk1DF8koonjQpGE3JDnT4xXs42yv4iRM+91cgzWVffu2b1DW
MmRWQlGgQu5trtztLsbgzntRLLQ9RLrWIvKmNOAmpuGeobrO7H1rajORTcGuY9dk
5w3dZYXKdRXwJw8VZOjU6POpboN+qrks7INueocGZ5/QOPUMQMwigZe6cogb7AE/
HI7txOFkiBW+yLaBde39Ly+B+DG8i8IZIut5+b3piBrxW5BKv3quvA1twLPa4DYK
RFBULm5+8RxuzthtcZ7hURX/Rct8EP41IC5rBULp0kUphk9K6cuQhyWu05+SPlzh
zkVlkKKrk4yMisYc6TakaSkpscBu+p6gQLHpOssiItXuV6E9lqWhFh6isNtM4CNO
O88fJHrFvTsf3/E2GVx7uN50l1hEJ2h+cvoNNY0WrN+cZqpynmKYHIVDwZkJ4vHb
8T/KmTUG2TwX1jAP2QF3E05J6tUwfMc4HPmifYcPow1V3mDBlDOE79eej5/EWi64
mnejVlGgZgHhykVCCvQjz95DM0fp6YagPqCh6ETg1P5vmRyIlRUWuT8TJAJxdpz7
pOFxiv16bfLNlnvNAM6Uz466iNFs2dsPtra3z5/7hpDSDl8qz+LEESE/OOHWYcWp
QDTHJK8xvcjmwm72xdR1dUSLk3hU32bMaCA8d+vsbB3a/9BXCL0=
=KYpT
-END PGP SIGNATURE-

Bug#1013137: rust-sysinfo: please upgrade to v0.23

[Jonas Smedegaard]

Source: rust-sysinfo
Version: 0.13.2-3
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to (or separately provide) newer upstream branch v0.23,
needed by projects I am preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsxDIACgkQLHwxRsGg
ASEzJg//cqmrEU3qZv5YXtqfkgj97b9UVP0gTgAOkLX9bR00J06z87iNwdWqplip
61hVcsdtrbTITjALAId9LfyuOjoI2GnKPDFAY63HBl4N5wD6O5hAIAvXEjUYbMaw
tvwiQ4qdyRh2KDQSR3d6CrVxDIr8HclP5ENOe5Uz8lxq3N/cT2ytHK6t8c3T/V3s
S40H6Y+YjZvHtftPQ42x/FGv6GvPdCpUkiJ/XyElt1q5vhRFUQmZra9MfTsBPcOm
PFAjW2A17i24kOpABsZDoAEobIze8sHPh2zsnUB7wUFMCTCm7hEkcrf9dAwlqZ+p
nx6YveBtsxIC7kVkxXjKjIOdvvAIETh3dnfIr6wlGEARXYUDF4CLoF8a2jok/9bf
I2Zv1p2aWxu3echbStoLEKswNX0iEFJkLxi+G7opR8JjXzUqu4X6X6VFOzGt97kz
+gAVUHXYxPyq/QfmGNK5m40gv51X28kSiJkITG4YaxDPbelMXRkATvPVJEY0u0u4
qFObv/TAK209WGXPHm4doR2ggVUf5xW3alr/j/lebYQwmaXXQBGR107rE64f6nf9
xuH2vwKcYoQn29ysreeFcwbKOqJpHrd4hivbdHJMa/vCSCQlvqkeb20IPNnORa2h
sthfSaBSf3MVfINuM8KcxFCj0xCR3iX5Tirq9F/ByyvUIyyP9iM=
=Xrw6
-END PGP SIGNATURE-

Bug#1013136: rust-threadpool: please upgrade to v0.8

[Jonas Smedegaard]

Source: rust-threadpool
Version: 1.7.1-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream branch v0.8, needed by porjects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsw2cACgkQLHwxRsGg
ASG92Q/+PnALk7cO3sXlQYbl2AhyOaI5oI1c+f83tDPXwvLtf0p1KfoCOGbRqFux
RAhbgjekuBKTqmZaLHeyoEnDldQ5n9UIw9RSyAMR4kjTS79kk62ObofciUNw0YH9
/CIguSegVMNX4IvbGgowIVr9ptxZb8mjbMFhRTckbptJF1diyvhuGQXsl5u4X3bL
0JnMRnf+IERZVjCAX8fyMOEiWI3Zychev0CFgQ7dAK/SdxTB3N/Ggolf/Szts1s6
Y/E17m4AhcvqPoIUnZUXJD8C/o+AAJ1RjPogNWZExkADsRWervgKr7gOMmntMmFe
aAb+jcaoXjnUciW5lIQXCnfNTseJ0MRdtVE7Lda692kL/qeHOxTMDgXpB+s8d0af
OcK/MytTdmosbni1hQradE6TjUTrK3aywlnWDnhCKawb/zKPUqYb+nuOJ801lMux
imbvbTxrD0XBTujjXyh/XuppTAXILdaNC8mwMdm9ySfIVYvaJkhwhn4srdVTFZIR
pXL+qEP6zGt4tUMZckqRcEOODYKWyK4n5xCxG3Fw+6B6FMaDmi04RmlCwniOr5QI
bBnSt6vJayrsFCm8c6XsI+J6CPqWKc4eAT/YZ4NQ0L5pvPLSF5g9I5loROKgMZyc
g/xlWn7TIH4FvxpMj8obo4DUOFOoxwLNP/bf3WJ5h0rgUtFCNi0=
=Hkct
-END PGP SIGNATURE-

Bug#1012548: libwebkit2gtk-4.1-0: Offline renderer SIGSEGV on i386

[karogyoker]

Package: libwebkit2gtk-4.1-0
Version: 2.36.3-1
Followup-For: Bug #1012548
X-Debbugs-Cc: karogyoker2+deb...@gmail.com
Control: tags -1 patch upstream

I think not many crashes surfaced because not many people are using real 32 bit
CPUs meanwhile visiting websites with Web Audio API.

All 32 bit CPUs are affected except newer models of Pentium 4.

I'm attaching the proposed fix.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.17.0-1-686-pae (SMP w/1 CPU thread; PREEMPT)
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 libwebkit2gtk-4.1-0 depends on:
ii  bubblewrap  0.6.2-1
ii  gstreamer1.0-plugins-base   1.20.2-2
ii  gstreamer1.0-plugins-good   1.20.2-1
ii  libatk1.0-0 2.38.0-1
ii  libc6   2.33-7
ii  libcairo2   1.16.0-5
ii  libegl1 1.4.0-1
ii  libenchant-2-2  2.3.2-1
ii  libfontconfig1  2.13.1-4.4
ii  libfreetype62.12.1+dfsg-2
ii  libgcc-s1   12.1.0-2
ii  libgcrypt20 1.10.1-2
ii  libgdk-pixbuf-2.0-0 2.42.8+dfsg-1
ii  libglib2.0-02.72.1-1
ii  libglx0 1.4.0-1
ii  libgstreamer-gl1.0-01.20.2-2
ii  libgstreamer-plugins-base1.0-0  1.20.2-2
ii  libgstreamer1.0-0   1.20.2-1
ii  libgtk-3-0  3.24.34-1
ii  libharfbuzz-icu02.7.4-1+b1
ii  libharfbuzz0b   2.7.4-1+b1
ii  libhyphen0  2.8.8-7
ii  libicu7171.1-3
ii  libjavascriptcoregtk-4.1-0  2.36.3-1
ii  libjpeg62-turbo 1:2.1.2-1
ii  liblcms2-2  2.12~rc1-2
ii  libmanette-0.2-00.2.6-3
ii  libnotify4  0.7.12-1
ii  libopengl0  1.4.0-1
ii  libopenjp2-72.4.0-6
ii  libpango-1.0-0  1.50.7+ds-1
ii  libpng16-16 1.6.37-5
ii  libseccomp2 2.5.4-1
ii  libsecret-1-0   0.20.5-2
ii  libsoup-3.0-0   3.0.6-1
ii  libsqlite3-03.38.5-1
ii  libstdc++6  12.1.0-2
ii  libsystemd0 250.4-1
ii  libtasn1-6  4.18.0-4
ii  libwayland-client0  1.20.0-1
ii  libwayland-egl1 1.20.0-1
ii  libwayland-server0  1.20.0-1
ii  libwebp71.2.2-2+b1
ii  libwebpdemux2   1.2.2-2+b1
ii  libwoff11.0.2-1+b1
ii  libwpe-1.0-11.12.0-1
ii  libwpebackend-fdo-1.0-1 1.12.0-1
ii  libx11-62:1.7.5-1
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxml2 2.9.14+dfsg-1
ii  libxslt1.1  1.1.34-4
ii  xdg-dbus-proxy  0.1.4-1
ii  zlib1g  1:1.2.11.dfsg-4

Versions of packages libwebkit2gtk-4.1-0 recommends:
ii  gstreamer1.0-gl   1.20.2-2
ii  gstreamer1.0-libav1.20.2-1
ii  gstreamer1.0-plugins-bad  1.20.2-1
ii  libgl1-mesa-dri   22.0.5-1
ii  xdg-desktop-portal-gtk1.14.0-1

Versions of packages libwebkit2gtk-4.1-0 suggests:
ii  gstreamer1.0-alsa  1.20.2-2

-- no debconf information
diff --git a/Source/WebCore/platform/audio/DenormalDisabler.h 
b/Source/WebCore/platform/audio/DenormalDisabler.h
index e0b3efd80f78..3ea2098099bb 100644
--- a/Source/WebCore/platform/audio/DenormalDisabler.h
+++ b/Source/WebCore/platform/audio/DenormalDisabler.h
@@ -26,6 +26,7 @@
 #define DenormalDisabler_h
 
 #include 
+#include 
 
 namespace WebCore {
 
@@ -36,7 +37,7 @@ namespace WebCore {
 #define HAVE_DENORMAL
 #endif
 
-#if defined(__GNUC__) && (defined(__i386__) || defined(__x86_64__))
+#if defined(__GNUC__) && defined(__SSE__)
 #define HAVE_DENORMAL
 #endif
 
@@ -56,7 +57,7 @@ public:
 _controlfp_s(, _DN_FLUSH, _MCW_DN);
 #else
 m_savedCSR = getCSR();
-setCSR(m_savedCSR | 0x8040);
+setCSR(m_savedCSR | (isDAZSupported() ? 0x8040 : 0x8000));
 #endif
 }
 
@@ -83,7 +84,32 @@ public:
 #endif
 }
 private:
-#if defined(__GNUC__) && (defined(__i386__) || defined(__x86_64__))
+#if defined(__GNUC__) && defined(__SSE__)
+static inline bool isDAZSupported()
+{
+#if defined(__x86_64__)
+return true;
+#else
+static bool s_isInited = false;
+static bool s_isSupported = false;
+if (s_isInited)
+return s_isSupported;
+
+struct fxsaveResult {
+uint8_t before[28];
+uint32_t CSRMask;
+uint8_t 

Bug#669704: autopsy: package upstream now 4.19, sort of linux ready, moved

[Ross Boylan]

Package: autopsy
Version: 2.24-5
Followup-For: Bug #669704
X-Debbugs-Cc: rossboy...@stanfordalumni.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The current version is 4.19, and has a new home,
https://github.com/sleuthkit/autopsy.  There is a downloadable version for
Linux at https://www.autopsy.com/download/, and some semi-encouraging news
about using it on Linux:

Here's the start of BUILDING.txt

  Last Updated: 5 August 2020

This file outlines what it takes to build Autopsy from source.

Note that it currently only works out-of-the-box on Windows.  We
are working on getting the process working under non-Windows systems.
It generally works, but needs some custom mangling to find the
correct C libraries.

So if the fact there wasn't a Linux version was the hangup, perhaps that helps.




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

Kernel: Linux 5.10.0-15-amd64 (SMP w/8 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autopsy depends on:
ii  binutils   2.35.2-2
ii  perl   5.32.1-4+deb11u2
ii  sleuthkit  4.10.1+dfsg-1

autopsy recommends no packages.

autopsy suggests no packages.


-BEGIN PGP SIGNATURE-

iQFSBAEBCgA8FiEEreS674/HIyV9gBfdnAYPmOsbK2AFAmKsuUkeHHJvc3Nib3ls
YW5Ac3RhbmZvcmRhbHVtbmkub3JnAAoJEJwGD5jrGytgLP8H/1tOdnNS4jH+CZ96
i9R3T/u272C8v04e5NmAIpJtsyrg2Ew+lPIG3sgLXDe5QBgu5+DpjptWchGSubN5
Dj6t+Hgh+VuuWj1ycW1AMDpMf14dHFQBNCR8zXBec3PAwPKO6dKZ2W5HBAI5k/31
BSJYIzISP2FA0O5HoD0pOHpxr7wB2P1/LxE7XTghWhGP2d8KXWEg/AYjomBGo5or
1dHl35wuf2Q+iUN3K3TahR4LK5h7lvTCcsxr7tiJH0Ia0GK29FVSKIq6R7h0/4nm
vmolcz/77rhIOa96+HkTUhlX/TY6oEBMm2AZ5MrfZ9UCssVeYkOv7c1GgKZfUFoC
jy0NclA=
=yZg2
-END PGP SIGNATURE-

Bug#1013135: libgl1: Failure to open i915

[Alexandre Lymberopoulos]

Package: libgl1
Version: 1.4.0-1
Severity: normal

Dear Maintainer,

I'm trying to have hardware acceleration on my old chipset on an old laptop 
(acer aspire 3690) here and running glxinfo or glx gears the first lines on the 
console are

libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so: cannot 
open shared object file: No such file or directory (search paths 
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: i915

Not sure if this is a libgl problem or a mesa one, so I guessed to
write it here. I'may provide any other information necessary to fix
this.  Aldo would appreciate any advice on how to get hardware
acceleration for my chipset (Intel Corporation Mobile 945GM/GMS, 943/940GML 
Express Integrated Graphics Controller [8086:27a2] (rev 03), according to lspci 
-nn).

Thanks in advance and best regards,
Alexandre

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.18.0-1-686-pae (SMP w/1 CPU thread; PREEMPT)
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 libgl1 depends on:
ii  libc6  2.33-7
ii  libglvnd0  1.4.0-1
ii  libglx01.4.0-1

libgl1 recommends no packages.

libgl1 suggests no packages.

Versions of packages libgl1 is related to:
pn  libgl1-nvidia-glx-any  

-- no debconf information

Bug#1012469: Analysis of issue with Debian package

[André Offringa]

On Fri, 17 Jun 2022 11:30:46 +0530 Nilesh Patra  wrote:
> I have done a few uploads on top of it. Could you please try out with
> "3.10.0+ds2-3" please?
> It works fine locally for me with the same.

Dear Nilesh,

With 3.10.0+ds2-3 the issue is indeed solved. Thanks!

Regards,
André

Bug#1000179: cme update dpkg-copyright should detect cpoyright holders for apache license

[Dominique Dumont]

On Friday, 19 November 2021 18:03:57 CEST you wrote:
> I'm reluctant to set --lines 0 option when calling licensecheck as this
> could really slow down copyright update (which is already not that fast on
> big packages)

All in all, slow is better than wrong. I'm going to use --lines 0 option.

Dod

Bug#1007717: Updated draft resolution

[Sam Hartman]

> "Helmut" == Helmut Grohne  writes:
Helmut> Indeed, and I do agree that 4c is such a clear statement. I
Helmut> would like to see a stronger statement here, but Sam et
Helmut> al. tried to gain consensus on that and there wasn't. So the
Helmut> CTTE advice probably shouldn't override that
Helmut> non-consensus. That makes 4c a lot more of an attractive
Helmut> option to me.

Actually, I think the TC making a decision when the project is unable to
come to consensus is often a great outcome.
The TC is one of our decision making options.  During my DPL term, the
TC did not appear to have the credibility to be a popular option for me
to go to when my consensus-making attempts got part of the way.
However, if the project is functioning well, I think that the TC is a
great option short of a GR.
I think that has worked well with usrmerge recently.

I DO NOT think this bug is the place for the TC to recommend something
like  the maintainer view of git source packages should be a
patches-unapplied format.
I think it would be great if the TC would take that on in a separate
bug.
If you would like me to pose such a question to the TC I'd be happy to
do so.
Driving a GR discussion on that issue is too much for me, but posing a
question to the TC is within the  energy I have available.

--Sam


signature.asc
Description: PGP signature

Bug#1013133: libpoppler118: please support ToUnicode for lessorequalslant and greaterorequalslant character names

[Vincent Lefevre]

Package: libpoppler118
Version: 22.02.0-3
Severity: wishlist
Tags: patch upstream
Forwarded: https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1215

LaTeX with the amssymb package generates lessorequalslant and
greaterorequalslant character names for \leqslant and \geqslant.

These character names are currently not supported by poppler.
For instance, on the attached PDF file (consisting in these two
characters only), pdftotext gives "6>", which is meaningless.

With the attached patch, I get "⩽⩾" as expected, which correspond
to the Unicode characters
  U+2A7D LESS-THAN OR SLANTED EQUAL TO
  U+2A7E GREATER-THAN OR SLANTED EQUAL TO

(Alternatively, the non-slanted versions U+2264 and U+2265 could be
used instead, as they are better supported by fonts, but the right
solution would be to fix the fonts.)

Bug forwarded to the merge request I've submitted upstream.

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

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

Versions of packages libpoppler118 depends on:
ii  libc62.33-7
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  liblcms2-2   2.12~rc1-2
ii  libnspr4 2:4.34-1
ii  libnss3  2:3.79-1
ii  libopenjp2-7 2.4.0-6
ii  libpng16-16  1.6.37-5
ii  libstdc++6   12.1.0-4
ii  libtiff5 4.4.0-2
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages libpoppler118 recommends:
ii  poppler-data  0.4.11-1

libpoppler118 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Description: add ToUnicode support for {greater,less}orequalslant
 Character names lessorequalslant and greaterorequalslant are generated
 from \leqslant and \geqslant in LaTeX with the amssymb package. They
 correspond to the Unicode characters
   U+2A7D LESS-THAN OR SLANTED EQUAL TO
   U+2A7E GREATER-THAN OR SLANTED EQUAL TO
 (alternatively, the non-slanted versions U+2264 and U+2265 could be
 used instead, as they are better supported by fonts).
Author: Vincent Lefevre 
Last-Update: 2022-06-17

Index: poppler-22.02.0/poppler/NameToUnicodeTable.h
===
--- poppler-22.02.0.orig/poppler/NameToUnicodeTable.h
+++ poppler-22.02.0/poppler/NameToUnicodeTable.h
@@ -2044,6 +2044,7 @@ static const struct NameToUnicodeTab nam
 { 0x2265, "greaterequal" },
 { 0x22db, "greaterequalorless" },
 { 0xff1e, "greatermonospace" },
+{ 0x2a7e, "greaterorequalslant" },
 { 0x2273, "greaterorequivalent" },
 { 0x2277, "greaterorless" },
 { 0x2267, "greateroverequal" },
@@ -2536,6 +2537,7 @@ static const struct NameToUnicodeTab nam
 { 0x2264, "lessequal" },
 { 0x22da, "lessequalorgreater" },
 { 0xff1c, "lessmonospace" },
+{ 0x2a7d, "lessorequalslant" },
 { 0x2272, "lessorequivalent" },
 { 0x2276, "lessorgreater" },
 { 0x2266, "lessoverequal" },


slant.pdf
Description: Adobe PDF document

Bug#1011254: The UDEB package "localechooser" contains probably some buggy source code in "05localechooser" file

[Jmkr]

Sorry for the delay, I had to do some work and then forgot that I 
planned to reply to this bug.


> Philip Hands  writes:
> ...
>
> Actually, given that we don't care what's in the first field at that
> point, and it's already matched the start of the country code, I think
> this ought to work as well:
>
>  "/^${L%%_*}/"'{s/^[^;]*;\([0-9]\);.*/\1/p;q}'

Yes, it works perfectly when I tested the "sed" command both in a 
terminal and also in my customized DI in the 
"./usr/lib/post-base-installer.d/05localechooser" file.


Although, I did not test the generated ISO and whether the whole locale 
chooser mechanism now works as intended with locales that have level 3+ 
(i.e. if DI actually creates the "/target/root/.profile" file for such 
locales). Since I don't use such locales on my systems it would be 
difficult for me to test this. I don't know the languages, so I probably 
would not be able to finish the DI using one of these languages:).


Cheers, Jmkr

Bug#1013131: hostname: Please convert d/copyright to machine-readable format

[Bastian Germann]

Package: hostname
Version: 3.23
Severity: wishlist
Tags: patch

Hi,

Please consider applying the enclosed patch to convert the d/copyright file to 
the machine-readable format.

Thanks,
Bastiandiff -Nru hostname-3.23/debian/copyright hostname-3.23+nmu1/debian/copyright
--- hostname-3.23/debian/copyright	2018-01-30 11:25:42.0 +0100
+++ hostname-3.23+nmu1/debian/copyright	2022-06-17 17:53:39.0 +0200
@@ -1,26 +1,27 @@
-This package was written by Peter Tobias 
-on Thu, 16 Jan 1997 01:00:34 +0100.
-
-License:
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment: This package was written by Peter Tobias 
+ on Thu, 16 Jan 1997 01:00:34 +0100.
 
+Files: *
+Copyright:
 	Copyright (C) 2009 Michael Meskes 
 	Copyright (C) 2004-2005 Graham Wilson 
 	Copyright (C) 1997 Bernd Eckenfels
 	Copyright (C) 1997 Peter Tobias 
 	Copyright (C) 1996 Free Software Foundation, Inc.
-
+ .
 	This program is free software; you can redistribute it and/or modify
 	it under the terms of the GNU General Public License as published by
 	the Free Software Foundation; version 2 of the License.
-
+ .
 	This program is distributed in the hope that it will be useful,
 	but WITHOUT ANY WARRANTY; without even the implied warranty of
 	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 	GNU General Public License for more details.
-
+ .
 	You should have received a copy of the GNU General Public License
 	along with this program; if not, write to the Free Software
 	Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
-
-On Debian systems, the complete text of the GNU General Public License
-can be found in /usr/share/common-licenses/GPL-2 file.
+License: GPL-2
+ On Debian systems, the complete text of the GNU General Public License
+ version 2 can be found in /usr/share/common-licenses/GPL-2 file.

Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade

[jim_p]

Package: samba
Followup-For: Bug #1009998
X-Debbugs-Cc: pitsior...@outlook.com

The 4.16.2 upgrade reached testing a moment ago, so I tested my filemanager
(pcmanfm, gtk version) for the issue. It can connect to

smb://host/sharename (or smb://ip/sharename)

but not to

smb://host (or smb://ip)

This means the user is not able to see the shares from the host but has to
remember the name of each share in order to connect to it and also do that by
typing its name in the address bar. Does this happen to you as well?


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

Kernel: Linux 5.17.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
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 samba depends on:
ii  adduser  3.121
ii  init-system-helpers  1.63
ii  libbsd0  0.11.6-1
ii  libc62.33-7
ii  libcups2 2.4.2-1
ii  libgnutls30  3.7.4-2
ii  libldap-2.5-02.5.12+dfsg-2
ii  libldb2  2:2.5.1+samba4.16.2-1
ii  libpam-modules   1.4.0-13
ii  libpam-runtime   1.4.0-13
ii  libpopt0 1.18-3
ii  libtalloc2   2.3.3-4
ii  libtasn1-6   4.18.0-4
ii  libtdb1  1.4.6-3
ii  libtevent0   0.12.0-1
ii  lsb-base 11.2
ii  procps   2:3.3.17-7+b1
ii  python3  3.10.4-1+b1
pn  python3-dnspython
pn  python3-samba
ii  samba-common 2:4.16.2+dfsg-1
pn  samba-common-bin 
ii  samba-libs   2:4.16.2+dfsg-1
pn  tdb-tools

Versions of packages samba recommends:
pn  attr
ii  logrotate   3.20.1-1
pn  python3-markdown
pn  samba-dsdb-modules  
pn  samba-vfs-modules   

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
pn  ntp | chrony   
pn  smbldap-tools  
pn  ufw
pn  winbind

Bug#1006638: firmware-misc-nonfree: /lib/firmware/i915/adlp_dmc_ver2_12.bin missing

[Jeremie Tarot]

Package: firmware-misc-nonfree
Version: 20210818-1+kali2
Followup-For: Bug #1006638

Hi,

This would indeed be nice and would quiet update-initramfs on my
computer:

update-initramfs: Generating /boot/initrd.img-5.17.0-kali3-amd64
W: Possible missing firmware /lib/firmware/i915/adlp_dmc_ver2_14.bin for module 
i915

Thanks in advance

TY
J

Bug#1013129: exo: CVE-2022-32278

[Moritz Mühlenhoff]

Source: exo
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for exo.

CVE-2022-32278[0]:
| XFCE 4.16 allows attackers to execute arbitrary code because xdg-open
| can execute a .desktop file on an attacker-controlled FTP server.

https://gitlab.xfce.org/xfce/exo/-/commit/c71c04ff5882b2866a0d8506fb460d4ef796de9f

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-32278
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32278

Please adjust the affected versions in the BTS as needed.

Bug#1006266: Should not honor all_proxy?

[Kjö Hansi Glaz]

Hi,

I just hit this bug, and I'm wondering why reportbug honors all_proxy
while it doesn't support SOOCKS proxy?

GNOME sets all_proxy and ALL_PROXY when selecting a SOCKS proxy in the
settings.

While searching the web, I didn't find a specification for all_proxy,
but it seems widely used for SOCKS.

Thanks for maintaing reportbug

Bug#768073: "ping!"

[Matt Barry]

On Fri, 2022-06-17 at 12:57 +, Mathias Gibbens wrote:
>   The final thing that's been preventing upload of LXD is an issue
> that
> was found with a filename conflict with the lxc packaging (#1010843).
> I
> neglected to block this bug by that one, but just did so.
> 
>   The good news is that a new version of lxc with that fix was just
> released, so hopefully the lxc packages can get updated after which
> I'll be requesting an upload of LXD to NEW. :)

That's great news!  I noticed the --force-overwrite.. otherwise though,
I've been using it to run autopkgtests and it worked great (right up
until zfs broke in unstable ;).

Thanks for your work!

Matt



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

Bug#1013102: cmd/link: check CGO_CFLAGS for non -g/-I/-O options before,+ internal linking

[Shengjing Zhu]

On Fri, Jun 17, 2022 at 3:36 PM Matthias Klose  wrote:
>
> Package: src:golang-1.18
> Version: 1.18.3-1
> Severity: wishlist
> Tags: patch
>
> lto support now landed in dpkg in unstable, now evaluation the possibility to
> turn on link time optimizations by default.  Currently builds fail like:
>
> [...]
> loadelf: $WORK/b101/_pkg_.a(_x001.o): 151068: sym#11 
> (g_cgo_export.c.d01d1947):
> ignoring symbol in section 4 (type 0)
> loadelf: $WORK/b101/_pkg_.a(_x002.o): 151072: sym#11
> (cgo_linux.cgo2.c.e1a05304): ignoring symbol in section 4 (type 0)
> loadelf: $WORK/b101/_pkg_.a(_x003.o): 151077: sym#13
> (cgo_resnew.cgo2.c.1f334c1b): ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b101/_pkg_.a(_x004.o): 151081: sym#11
> (cgo_socknew.cgo2.c.00cb1c10): ignoring symbol in section 4 (type 0)
> loadelf: $WORK/b101/_pkg_.a(_x005.o): 151086: sym#13 
> (cgo_unix.cgo2.c.81407354):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x001.o): 151068: sym#11 
> (g_cgo_export.c.d01d1947):
> ignoring symbol in section 4 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x002.o): 151093: sym#11 (cgo.cgo2.c.547524ab):
> ignoring symbol in section 4 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x003.o): 151098: sym#13 (gcc_context.c.0c594a6b):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x004.o): 151105: sym#16 (gcc_fatalf.c.104c99f5):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x005.o): 151116: sym#21 (gcc_libinit.c.57049a80):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x006.o): 151126: sym#19
> (gcc_linux_amd64.c.7bb88008): ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x007.o): 151133: sym#16 (gcc_mmap.c.58726c34):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x008.o): 151138: sym#13 (gcc_setenv.c.58922dfc):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x009.o): 151143: sym#14 
> (gcc_sigaction.c.8c3bca0d):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x010.o): 151148: sym#13 
> (gcc_traceback.c.2a322f93):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x011.o): 151156: sym#16 (gcc_util.c.9bbd18fc):
> ignoring symbol in section 5 (type 0)
> loadelf: $WORK/b108/_pkg_.a(_x012.o): 151161: sym#13 
> (linux_syscall.c.96145c1f):
> ignoring symbol in section 5 (type 0)
> _cgo_callers: relocation target x_cgo_callers not defined
> _cgo_init: relocation target x_cgo_init not defined
> _cgo_mmap: relocation target x_cgo_mmap not defined
> _cgo_munmap: relocation target x_cgo_munmap not defined
> /usr/lib/go-1.18/pkg/tool/linux_amd64/link: too many errors
> [...]
>
> https://patches.ubuntu.com/g/golang-1.18/golang-1.18_1.18.3-1ubuntu1.patch
>
> so please disable these for now and/or forward the issue upstream.

The patch says it has been forwarded to
https://go-review.googlesource.com/c/go/+/281314
And on https://go-review.googlesource.com/c/go/+/281314, the comment
says it has been obsoleted by
https://go-review.googlesource.com/c/go/+/339370

-- 
Shengjing Zhu

Bug#1012789: linucnc runtime prob with tiff is because of tiff

[Steffen Möller]

The problem is with the tiff library. On
https://github.com/LinuxCNC/linuxcnc/pull/1700 it is explained how to
install an earlier version from snapshot.debian.org

To trigger the problem independently from linuxcnc, try

$ wish
% package require Img

Bug#1013128: kleopatra: Kleopatra toolbar misses most icons on Gnome

[Kjö Hansi Glaz]

Subject: kleopatra: Kleopatra toolbar misses most icons on Gnome
Package: kleopatra
Version: 4:22.04.1-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?

Install kleopatra, while using Gnome desktop (task-gnome-desktop
installed)

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

Start the application.

   * What was the outcome of this action?

The application toolbar is missing most icons. Only "Lookup on
server..." has an icon.

   * What outcome did you expect instead?

The toolbar to have icons, as shown on the screenshot in gnome-software.

Installing breeze-icon-theme solves he issue. Perhaps kleopatra should
recommands breeze-icon-theme, as quassel and pcmanfm do.

Thanks for maintaing kleopatra.

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

Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 kleopatra depends on:
ii  dirmngr2.2.35-2
ii  gnupg  2.2.35-2
ii  gpgsm  2.2.35-2
ii  libassuan0 2.5.5-3
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-4
ii  libgpg-error0  1.45-2
ii  libgpgme11 1.17.1-4
ii  libgpgmepp61.17.1-4
ii  libkf5codecs5  5.94.0-1
ii  libkf5configcore5  5.94.0-3
ii  libkf5configgui5   5.94.0-3
ii  libkf5configwidgets5   5.94.0-1
ii  libkf5coreaddons5  5.94.0-1
ii  libkf5crash5   5.94.0-1
ii  libkf5dbusaddons5  5.94.0-1
ii  libkf5i18n55.94.0-1+b1
ii  libkf5iconthemes5  5.94.0-1
ii  libkf5itemmodels5  5.94.0-1
ii  libkf5libkleo5 [libkf5libkleo5-22.04]  4:22.04.1-1
ii  libkf5mime5abi1 [libkf5mime5-22.04]22.04.1-1
ii  libkf5notifications5   5.94.0-1
ii  libkf5textwidgets5 5.94.0-1
ii  libkf5widgetsaddons5   5.94.0-2
ii  libkf5windowsystem55.94.0-1
ii  libkf5xmlgui5  5.94.0-1+b1
ii  libqgpgme7 1.16.0-1.2
ii  libqt5core5a   5.15.4+dfsg-3
ii  libqt5dbus55.15.4+dfsg-3
ii  libqt5gui5 5.15.4+dfsg-3
ii  libqt5network5 5.15.4+dfsg-3
ii  libqt5printsupport55.15.4+dfsg-3
ii  libqt5widgets5 5.15.4+dfsg-3
ii  libstdc++6 12.1.0-4
ii  paperkey   1.6-1
ii  pinentry-qt1.2.0-1

kleopatra recommends no packages.

kleopatra suggests no packages.

-

Bug#1013125: RFP: kcm-grub2 - KDE Control Module for configuring the GRUB2 bootloader

[Jeremie Tarot]

Package: wnpp
Version: N/A; reported master
Severity: wishlist

* Package name : kcm-grub2
Version : O.6.4+gitb01168e1
Upstream Author : KDE Community 
* URL : https://invent.kde.org/system/kcm-grub2
* License : GPLv3
Description : A KDE Control Module for configuring the GRUB2 bootloader.

Smoothly integrated in KDE System Settings, it is the central place for 
managing your GRUB2 configuration. Supports many GRUB2 configuration options, 
most notably:

* Manage default boot entry
* Manage boot timeout
* Manage boot resolutions
* Manage boot menu colors
* Manage boot menu theme
* Manage linux kernel arguments
* Save and update the configuration files of GRUB2

Extra features include:

* Recover GRUB2
* Remove old entries
* Create and preview GRUB2 splash images

Bug#1012923: fenics-dolfinx: ftbfs with GCC-12

[Drew Parsons]

Source: fenics-dolfinx
Followup-For: Bug #1012923

Judging by 
https://github.com/doxygen/doxygen/commit/5198966c8d5fec89116d025c74934ac03ea511fa
likely needs

#include 

added to cpp/dolfinx/la/PETScOperator.cpp

There are some code rearrangements in dolfinx 0.4, let's check again
with that version.

Bug#1012852: bcron-sched fails to start

[Georges Khaznadar]

Hi Lorenzo,

Lorenzo Beretta a écrit :
> [...]
> The setfacl thing doesn't work because
> (suspense)...
> I tried it in a fresh sid install in a vm and setfacl was not installed.
> 
> If setfacl is what it takes, it will have to be added as a dependency
> - any reason why chown won't work? (chown is installed everywhere)

I shall probably not  modify the traditional permission scheme which is
set up by the majority of people using a con-daemon service.

So, the permissions of files under /var/spool/cron/crontabs will keep
being ruled by user ${USER} and group crontab.

setfacl is a command which allows one to establish access control lists
(acl), i.e. additional users or groups, each one with his particular
permissions, enhancing the "ugo" traditional categories in Un*x
filesystems. So, a file can be owned, for example, by user foo and by
user cron.

> The openbsd folks have a few presentations on the subject
> (https://www.openbsd.org/events.html - I no longer remember which one
> made me understand the idea, sorry! look for "privilege separation"
> and then for some daemon that you care about - ntpd in my case
> http://www.openntpd.org/papers.html)

Thank you for the information. Do you know whether the usage of bcron is
majoritary among openbsd folks? 

So far, I could see that the name "bcron" would mean "better cron" or
"Bruce Guenter's cron", I read the claim that bcron would be more
secuire because tasks are split into separate processes, which were
developed with security in mind.

I suppose that this claim means at least: security in Bruce Guenter's mind.

I tried to seek more information about the grounds of this belief in
security, and found not document explaining the internals of bcron. So I
suppose that people are trusting Bruce Guenter because of his
reputation. 

- Unfortunately there were no updates at https://untroubled.org/bcron/
  for seven years now.

- Unfortunately, I did not find meta-information to help one to
  understand bcron's internals. The source code is scarcely commented,
  and the main figure is difficult to grasp. Please do you know any
  pointer to valuable information about it?

I shall add a dependency on package acl, and implement the tricks I
suggested in my previous e-mail, thank you for your report!

Best regards,   Georges.

> 
> Thank you for picking up the package btw - becoming a package
> maintainer is something I could never bring myself to do, greatly
> appreciated!
> 
> Il giorno gio 16 giu 2022 alle ore 10:49 Georges Khaznadar
>  ha scritto:
> >
> > Hi Lorenzo,
> >
> > thank you for the bug report.
> >
> > I am learning to maintain bcron: this package was orphaned until two
> > days ago, and I am a recent adopter, willing to maintain it further.
> >
> > the directory /var/spool/cron/crontabs hosts crontabs for various users,
> > and the scripts found in every crontab are supposed to run with the
> > permissions of the related user, aren't they?
> >
> > When I tried to adapt bcron to use the package cron-daemon-common, in
> > order to give all packages which provide cron-daemon a chance to
> > compete, I saw that files under /var/spool/cron/crontabs where owned by
> > cron:cron, when managed by bcron (<< 0.11-12), unlike files managed by
> > cron-daemon-common, which are owner by :crontab.
> >
> > At that time, I supposed that running every user script with the
> > permissions of the right user implied that user cron or group cron have
> > super priviledges, so the change would be harmless.
> >
> > Your bug report shows me that cron has no super priviledges.
> >
> > So there is something to fix. Please can you tell me wheter the
> > following commands can fix the issue, in your case ?
> >
> > # setfacl -m u:cron:rwx /var/spool/cron/crontabs
> > # setfacl -m g:cron:rwx /var/spool/cron/crontabs
> > # for f in /var/spool/cron/crontabs/*; do setfacl -m u:cron:rw $f; setfacl 
> > -m g:cron:rw $f; done
> >
> > If those commands can fix the issue, I shall modify bcron's
> > post-installation script to fix the bug.
> >
> > Thank you in advance for your help.
> >
> > Best regards,   Georges.
> >
> > Lorenzo Beretta a écrit :
> > > Package: bcron
> > > Version: 0.11-12
> > > Severity: important
> > >
> > > Sorry for using gmail webmail - gmail decided I can't let "less secure
> > > apps" send mail on my behalf, I'm trying to figure out what can be
> > > done.
> > >
> > > Anyway, here's what I wanted reportbug to send...
> > >
> > > Content-Type: text/plain; charset="us-ascii"
> > > MIME-Version: 1.0
> > > Content-Transfer-Encoding: 7bit
> > > From: Lorenzo Beretta 
> > > To: Debian Bug Tracking System 
> > > Subject: bcron-sched fails to start after latest update
> > > Message-ID: 
> > > <165530519508.4489.146445291116667405.report...@dudu.homenet.telecomitalia.it>
> > > X-Mailer: reportbug 11.5.0devuan1
> > > Date: Wed, 15 Jun 2022 16:59:55 +0200
> > >
> > > Package: bcron
> > > Version: 0.11-12
> > > Severity: important
> > >
> 

Bug#768073: "ping!"

[Mathias Gibbens]

On Sun, 12 Jun 2022 00:53:14 -0400 Matt Barry 
wrote:
> Hi,
> 
> I imagine I arrived at this bug the same way a lot of folks did,
trying
> to sleuth out the reason why (e.g.) autopkgtest-build-lxd is broken
in
> Debian.. but perhaps I might be the first that read all the way to
the
> end to find a repo that builds somewhat working packages!  Kudos and
> thanks!
> 
> What is the state of the packages at the moment?  Are there any areas
> that need help or testing?  (I'm not a go expert, but happy to help
out
> if I can.)
> 
> Cheers,
> Matt

  The final thing that's been preventing upload of LXD is an issue that
was found with a filename conflict with the lxc packaging (#1010843). I
neglected to block this bug by that one, but just did so.

  The good news is that a new version of lxc with that fix was just
released, so hopefully the lxc packages can get updated after which
I'll be requesting an upload of LXD to NEW. :)

  There is one known edge case use bug with LXD [1], but that's in the
hands of upstream and isn't significant enough to delay the uploading
of LXD.

Mathias

[1] -- https://github.com/lxc/lxc/issues/4150


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

Bug#1013089: ddccontrol-db: Version number not matching with upstream

[Barak A. Pearlmutter]

Thanks. Good eye!
Turns out upstream had a typo in a git tag, which is what the
packaging tooling sees.
Hardly seems worth bumping an epoch when it will be solved by just
waiting a few weeks. We call this "laziness", right?

Bug#1010843: Bash completion filename conflict with LXD

[Mathias Gibbens]

On Wed, 2022-05-11 at 17:18 -0300, Antonio Terceiro wrote:
> It turns out that that portion of our debian/rules is deprecated as
> that
> is already handled by the upstream build system. This needs an
> upsteam
> change, which I submitted in the link above.

  lxc 5.0.0 was just recently tagged [1], which is the first release
that includes the corrected bash completion filename. It looks like the
biggest change is switching the build system over to meson. Would
someone be able to work on updating the lxc package with the new
release?

Thanks,
Mathias

[1] -- https://github.com/lxc/lxc/tags


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

Bug#1013124: RM: uftrace [armhf] -- ANAIS; doesn't work on armhf

[Gürkan Myczko]

Package: ftp.debian.org
Severity: normal

please remove armhf builds from testing, so sid version can migrate to testing

Note: this was a request for a partial removal from testing, converted in one 
for unstable

Bug#1011975: [Pkg-rust-maintainers] Bug#1011975: rustc: missing dependency on lld-13 (shipps broken rustc-lld symlink)

[Ximin Luo]

Control: forcemerge 943859 -1
Control: notfound -1 1.59.0+dfsg1-1

Not a bug, see #943859

Pirate Praveen:
> Package: rustc
> Version: 1.59.0+dfsg1-1
> Severity: serious
> Justification: ships broken symbolic link to rustc-lld
> 
> 
> $ ls -l /usr/bin/rust-lld
> lrwxrwxrwx 1 root root 6 മേയ് 11 13:11 /usr/bin/rust-lld -> lld-13
> 
> I think lld-13 should be at least recommends instead of suggests since the 
> package ships a broken symlink otherwise.
> 
> ___
> Pkg-rust-maintainers mailing list
> pkg-rust-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers


-- 
GPG: ed25519/56034877E1F87C35
https://github.com/infinity0/pubkeys.git

Bug#1013079: installation-reports: GUI install option isn't visible on boot

[Mark A. Hershberger]

Yes, that looks like it would be the problem.  Is there another bug for this?

Mark A. Hershberger
NicheWork LLC
717-271-1084

- On Jun 17, 2022, at 7:43 AM, Philip Hands p...@hands.com wrote:

>> Initial boot: Default GUI install option wasn't visible. Once I used
>> the down arrow to move from the highlighted default option, it became
>> visible and I was able to use the up arrow to return to it.
> 
> I would guess what you're seeing is the same as the problem with recent
> daily images, when doing a UEFI boot, as seen here:
> 
>  https://openqa.debian.net/tests/60553#step/_boot_to_debianinstaller/2
> 
> if you look closely in the highlighted box, you can just about see
> "Graphical install" as a black font on dark_blue background, but it's
> very close to invisible.
> 
> It should have an inverted background on the selected item, which then
> makes the black text easily visible, as seen in the last working test,
> using a netinst ISO from 2022-06-07 17:27:
> 
>  https://openqa.debian.net/tests/59056#step/_boot_to_debianinstaller/1
> 
> The first broken version I saw was from 2022-06-13 17:22, although it
> could be that the breaking change happened earlier but was masked by the
> kernel mismatch/upgrade that meant that no new ISOs were produced for a
> few days just before that.
> 
> Cheers, Phil.
> --
>|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
>|-|  http://www.hands.com/http://ftp.uk.debian.org/
> |(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY

Bug#1013123: librust-bindgen-dev: Fails to build bindings against libraries that include SSE intrinsics headers

[Gard Spreemann]

Package: librust-bindgen-dev
X-Debbugs-Cc: g...@nonempty.org
Version: 0.59.2-2+b1
Severity: normal

Dear Maintainer,

Bindgen fails to generate bindings for C code that includes SSE
intrinsics headers like emmintrin.h:

  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2374:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size
  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2394:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size
  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2414:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size
  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2434:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size
  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2374:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size, err: true
  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2394:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size, err: true
  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2414:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size, err: true
  /usr/lib/llvm-13/lib/clang/13.0.1/include/emmintrin.h:2434:10: error: invalid 
conversion between vector type '__m128i' (vector of 2 'long long' values) and 
integer type 'int' of different size, err: true
  thread 'main' panicked at 'Unable to generate bindings.: ()', build.rs:15:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This bug report is meant as documentation, as it seems that 0.60.1
(already in sid) fixes the issue.

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

Kernel: Linux 5.18.0-1-amd64 (SMP w/6 CPU threads; PREEMPT)
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 librust-bindgen-dev depends on:
ii  clang1:13.0-54
ii  librust-bitflags-dev [librust-bitflags-1+default-dev]1.3.2-2
ii  librust-cexpr-dev [librust-cexpr-0.6+default-dev]0.6.0-2
pn  librust-clang-sys-1+clang-6-0-dev
ii  librust-clang-sys-dev [librust-clang-sys-1+default-dev]  1.3.0-1
ii  librust-lazy-static-dev [librust-lazy-static-1+default-dev]  1.4.0-1
ii  librust-lazycell-dev [librust-lazycell-1+default-dev]1.3.0-3
ii  librust-peeking-take-while-dev [librust-peeking-take-while-0.1+  0.1.2-1+b1
ii  librust-proc-macro2-dev [librust-proc-macro2-1-dev]  1.0.28-1
ii  librust-quote-dev [librust-quote-1-dev]  1.0.9-1
ii  librust-regex+unicode-dev [librust-regex-1+unicode-dev]  1.5.5-1
ii  librust-regex-dev [librust-regex-1+std-dev]  1.5.5-1
ii  librust-rustc-hash-dev [librust-rustc-hash-1+default-dev]1.1.0-1
ii  librust-shlex-dev [librust-shlex-0.1+default-dev]0.1.1-1+b1

Versions of packages librust-bindgen-dev recommends:
ii  librust-bindgen+default-dev  0.59.2-2+b1

Versions of packages librust-bindgen-dev suggests:
ii  librust-bindgen+clap-dev0.59.2-2+b1
ii  librust-bindgen+env-logger-dev  0.59.2-2+b1
ii  librust-bindgen+log-dev 0.59.2-2+b1
ii  librust-bindgen+logging-dev 0.59.2-2+b1
ii  librust-bindgen+runtime-dev 0.59.2-2+b1
pn  librust-bindgen+static-dev  
ii  librust-bindgen+which-dev   0.59.2-2+b1

-- no debconf information


signature.asc
Description: PGP signature

Bug#1010964: yosys: autopkgtest regression

[dxld]

Hi Petter,

On Fri, Jun 17, 2022 at 07:22:17AM +0200, Petter Reinholdtsen wrote:
> [Adrian Bunk]
> > In a short test with 0.17, this appear to fix it.
> 
> If the RC fix is to upgrade, I hope it will happen soon to get the FPGA
> programming tool chain back into testing.

FYI the removal from testing was due to #1008718 (build failure on
mips64el). I never had enough time to debug what's going on there and the
porter boxes for that arch being slow as hell doesn't help.

I think I'll just exclude the mips64el arch in the yosys package and be
done with it. Right after I figure out how to do that :)

--Daniel


signature.asc
Description: PGP signature

Bug#1013122: gcc-10: internal compiler error: in move_insn

[Stephen Kitt]

Package: gcc-10
Version: 10.2.1-6
Severity: important
Tags: upstream, fixed-upstream

Dear Maintainer,

gcc-10 crashes when buiding dosemu2:

gcc -c -imacros config.hh -MD -DCFLAGS_STR=" -fplan9-extensions -Wall 
-Wstrict-prototypes -Wmissing-declarations -Wnested-externs -fms-extensions 
-pthread -Wno-unused-result -Wcast-qual -Wwrite-strings -Wstrict-aliasing=2 
-Wno-address-of-packed-member -ggdb3 -fpie   -g -O2 
-ffile-prefix-map=/home/steve/tmpdir/dosemu2=. -fstack-protector-strong 
-Wformat -Werror=format-security" -I../../../src/include 
-I../../../src/plugin/include -I../../../src/base/bios/x86 
-I/home/steve/tmpdir/dosemu2/build/../src/include 
-I/home/steve/tmpdir/dosemu2/build/../src/base/lib -Wdate-time 
-D_FORTIFY_SOURCE=2 -fplan9-extensions -Wall -Wstrict-prototypes 
-Wmissing-declarations -Wnested-externs -fms-extensions -pthread 
-Wno-unused-result -Wcast-qual -Wwrite-strings -Wstrict-aliasing=2 
-Wno-address-of-packed-member -ggdb3 -fpie   -g -O2 
-ffile-prefix-map=/home/steve/tmpdir/dosemu2=. -fstack-protector-strong 
-Wformat -Werror=format-security -o int.o 
/home/steve/tmpdir/dosemu2/build/../src/base/core/int.c
during RTL pass: sched2
.../dosemu2/build/../src/base/core/int.c: In function ‘int33_unrevect_fixup’:
.../dosemu2/build/../src/base/core/int.c:1748:1: internal compiler error: in 
move_insn, at haifa-sched.c:5471
 1748 | }
  | ^
0x7f14e033cd09 __libc_start_main
../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See  for instructions.


The bug as been reported upstream, and a fix has been backported to
the gcc-10 branch; see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105936 and
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f2851a7cff4d74edca26d39c7bfa1264355a22ed

Would it be possible to update the gcc-10 package with this fix?
Ideally, in stable too...

Regards,

Stephen


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable'), (100, 'unstable-debug'), (100, 
'testing-debug'), (100, 'unstable'), (100, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 5.10.0-12-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 gcc-10 depends on:
ii  binutils   2.35.2-2
ii  cpp-10 10.2.1-6
ii  gcc-10-base10.2.1-6
ii  libc6  2.31-13+deb11u3
ii  libcc1-0   10.2.1-6
ii  libgcc-10-dev  10.2.1-6
ii  libgcc-s1  10.2.1-6
ii  libgmp10   2:6.2.1+dfsg-1+deb11u1
ii  libisl23   0.23-1
ii  libmpc31.2.0-1
ii  libmpfr6   4.1.0-3
ii  libstdc++6 10.2.1-6
ii  libzstd1   1.4.8+dfsg-2.1
ii  zlib1g 1:1.2.11.dfsg-2+deb11u1

Versions of packages gcc-10 recommends:
ii  libc6-dev  2.31-13+deb11u3

Versions of packages gcc-10 suggests:
pn  gcc-10-doc   
pn  gcc-10-locales   
ii  gcc-10-multilib  10.2.1-6

-- no debconf information

Bug#1010964: yosys: autopkgtest regression

[dxld]

Hi Petter,

On Fri, Jun 17, 2022 at 01:48:24PM +0200, Petter Reinholdtsen wrote:
> [Daniel Gröber]
> > FYI the removal from testing was due to #1008718 (build failure on
> > mips64el).
> 
> Why do you believe so?  That is not what I read from
> https://tracker.debian.org/pkg/yosys >.  It claim #1010964 is the
> reason yosys is thrown out of testing.

I think #1008718 is why it was removed and #1010964 is why it can't be
re-introduced (yet). Even if I upload 0.17 or just the autopkgtest fix
it'll still likely fail on mips64el again so it whouldn't go through anyway
until that is fixed/worked-around.

> Is upgrading to 0.18 out of the question?

No, not at all. Just depends on how annoying rebasing the patches ends up
being.

--Daniel


signature.asc
Description: PGP signature

Bug#1013079: installation-reports: GUI install option isn't visible on boot

[Philip Hands]

> Initial boot: Default GUI install option wasn't visible. Once I used
> the down arrow to move from the highlighted default option, it became
> visible and I was able to use the up arrow to return to it.

I would guess what you're seeing is the same as the problem with recent
daily images, when doing a UEFI boot, as seen here:

  https://openqa.debian.net/tests/60553#step/_boot_to_debianinstaller/2

if you look closely in the highlighted box, you can just about see
"Graphical install" as a black font on dark_blue background, but it's
very close to invisible.

It should have an inverted background on the selected item, which then
makes the black text easily visible, as seen in the last working test,
using a netinst ISO from 2022-06-07 17:27:

  https://openqa.debian.net/tests/59056#step/_boot_to_debianinstaller/1

The first broken version I saw was from 2022-06-13 17:22, although it
could be that the breaking change happened earlier but was masked by the
kernel mismatch/upgrade that meant that no new ISOs were produced for a
few days just before that.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY

Bug#1013121: rust-winreg: please upgrade to v0.7

[Jonas Smedegaard]

Source: rust-winreg
Version: 0.6.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream branch v0.7, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsau0ACgkQLHwxRsGg
ASFIGQ/+KPKwvb8EwUqKYSO9D3FtsIvrySCtM+IDtg8YOGyYAz9iy3RpdU0PS47H
XEH2ea3pNxDiEuM7Z+jfhgM0Vk6GrR+bd1rfqEaz6pa4pBEoLyi1maOvGvdCVwsH
qcOpbCdV2BQu6VcLyaGhLoOoohJaUDiKm7KPwY/EcPMjaZSBughYP06Q1WFatVGV
Cw/t2HQHRimCb6oR47i0y2FzS25UZOFIpoDzQs2Hbs5ZWVWtwem/lt/hyTtNBUXr
GdPhCZ44ICksi8w8vxnJaUGS9bYSBJQlDiHeBxV/i0X1s+z4IsOL39Mk8tFkOfpT
hUdyLQEpqeexUhIE4y70A+h8iXg5I+WWA0sWFeXuiVuHrm0ICa73onKTB85/mmtp
6IYXzVPFRZeQ29/6IZwBnv0+EwIF8vgrOcm85DwOBIpOxu950IXWJOPg6FKeLYx4
P9ZmEC6uZs/rGVAluuRToRWvl2PziN24xItn+SIhy30K1Ir+84mOIdrgSX4/WpiJ
RDDTgx8LIqh2VnhBTWGVaMjBAvEzgyfvuVm0g1dxtCAj+Ibd1y1sgnglwYwJS9bC
5zyCTHDfaPmGi0ZpB02FF6Gj2ZYuVFlxECoEyMPFAG8lxjQLtssfkOHVFTpZAuHW
nAB5ZTdZar55gjbPUEBpk0x//pucH+cRlzg+h7YWZyW4tFUysuM=
=QMCw
-END PGP SIGNATURE-

Bug#1010964: yosys: autopkgtest regression

[Petter Reinholdtsen]

[Daniel Gröber]
> FYI the removal from testing was due to #1008718 (build failure on
> mips64el).

Why do you believe so?  That is not what I read from
https://tracker.debian.org/pkg/yosys >.  It claim #1010964 is the
reason yosys is thrown out of testing.

Is upgrading to 0.18 out of the question?
-- 
Happy hacking
Petter Reinholdtsen

Bug#1013120: rust-strum: please upgrade to v0.21

[Jonas Smedegaard]

Source: rust-strum
Version: 0.19.2-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream branch v0.21, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsaUwACgkQLHwxRsGg
ASEZ9w//UXf0WIUDMBUnPgosmXOlWWN1wMre5VW+fo3uxGC435fy8Bv1ZZ4TCYsa
Ya53YnpA8VZMdJ8gSK5hMvE9oiFSL1VdW1Z0pI/GYtMjK8Ny19ChQMCgYcoHAr1U
0MXBAK/6PfX4idcyViElOOGcAGI5jgWja2lBLskm+gIpbWhEUBOmK6H3q1cfZxpl
L9unRsn7uGP73/ZZrXGlEaomb4o+OBqcuiah1+lIrQPcv5GcmlHY8riOq1by+oK/
FvZLywh97w039D1FWVL2pexvr1UpJ2+JOyZDy1DSt89tsl/lsEQCtCmjGrrcRtSd
Mk/FfA/DKQOhNOThIJ5jAcoCdRY+oKzn29mzwMlpFf9C5T1pcG/FG9MVX6aw1Vuy
PKvakWYU+bCKJSQw6frZftdAmBIU/Q0T8xgGTHURiZOPjmOLWRbYW6J9Rge4AiZ+
2nn3oequO0nwUx4DaTtgwwxZ+4cUi+kgExUrHq1tCRC1BpL+rF81gwGx1+cayd/L
TKwArlEFrkJXfojoJPSVRvgO4D/FNSynURIbbWwZ2gqI/kgZVGB8azEW8IhLav3b
8m//NGFJcou2Hd1559btQMTSQzF/7XDAWkrI9/s0mbmixFFKbrJTTmEISKCOcpih
dbM/dQ6KKXJd3sN+rkqh75BRO4PSkRjP/h5yZHm2Y7vuZy+PxRA=
=MQRy
-END PGP SIGNATURE-

Bug#1012789: tk Img error while importing

[Steffen Möller]

The same error is triggered from within Tcl/Tk. LinuxCNC I do not think
to be to blame.

$ wish
% package require Img
couldn't load file
"/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.13/libtifftcl4.1.0.so":
/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.13/libtifftcl4.1
.0.so: undefined symbol: _TIFFsetString, version LIBTIFF_4.0^

Bug#1012886: 7zip: ftbfs with GCC-12

[yokota]

Hello,

ftbfs fix was uploaded to Debian sid as 7zip/21.07+dfsg-5 .

--
YOKOTA

Bug#1006932: Please update fontconfig to 2.14.0

[Amr Ibrahim]

Hello,

I think now is the best time to update fontconfig to 2.14.0.

https://gitlab.freedesktop.org/fontconfig/fontconfig

That will close these bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961386
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998284

Best,
Amr

Bug#1013119: rust-path-slash: please update to v0.1.4

[Jonas Smedegaard]

Source: rust-path-slash
Version: 0.1.1-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to upstream release v0.1.4, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsYKoACgkQLHwxRsGg
ASESmRAAiFH35x3xqNYP22Ikvs7gYTxJpDAGLwdfMgs+qBs2oORh/Nt+ziDWq+Vq
iKBGl9izEcr9PxzezOIk7JE4HPYRU/CYYieYHg5WBzAHzn1uyH+LKl9QsRpcFPcP
l5yokcyqr/zARQS76CySF2vPUV386irrMAkUP+KJNMp2T3ugN0z6U0bePt1L9/By
sBtYYpIWzx6/Zgkaz5YYGmQq9+ZfBS6RswW4OpsiYW5bXbyr26yR4oAOqjEt/vR0
2udbAD2o0skdYG/WN+JNXuO1pMuxEYcyVRKBs5Rs60hFmqfQIZ3nyqz3nU2lyLOO
9lQTdiRRhfSWtWhb/NEgsgP2amoDbYALE4DPXal32M2oAKVA1dwnx/p9EzeCPIgn
Tq0TNudmjQfA3Qo7StgxnThVhY6fVuIL2bPtXL2+ls1s8NU8Lk85g4fKwdPMm5uW
saysmbdoEJzpk9yGYx018EeNWxLMl94BNXvd+UTTJxthBql1Hs4AQvdXttAFUPul
LToteT/225YmOzbhgm0rbiCaCAt1+IXxEI2P4pqgebHQLz5xW7+nolEvhdVq8S43
/fB4poWxY7qb3EK9lckiNO5MoUlJaz9HHaV1x+UO2lDk/RJyQCL7TCiZj7Al/k2S
ZSxzNot9ITA37NfV8nJ5QPKE68J8oXeg9RNHJvFyUOPO/1yA9sQ=
=DeqQ
-END PGP SIGNATURE-

Bug#1013118: librust-num-format-dev: impossible to install

[Jonas Smedegaard]

Package: librust-num-format-dev
Version: 0.4.0-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package depends on missing packages, and is thus impossible to
install.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsYBkACgkQLHwxRsGg
ASHRMQ//YlZASvjWl7iqPu+yuCFdZDN8TSNaCOkJAcOxhM1M/I/SdiGRSHCA1x4Y
YqnaUlYDQPkYsVe9Cm+nU4kFU21Zf0UfSfEviCk1E0gXqV4nQjh1Fe5103LtAmvv
y+aXqpFhhqpLgRFXezFakuQFhlxw42i8YQUuVP7jVg2fdk7rppwXyOS19wFY8E69
mdzaMg1ULFpz/yJ+/WsONyGxO8U7JtCLj1eh9/U5u3tX63h/oHbeRmZoOTi/iu9f
sI/HGma3GUTpG0oGbWhu9jLzRaVkmguhlFXLkgWOHrV6giwBVgwdeUtpelJl7Hzv
UNv9Z4o9ltr/V1Wi3CYDZMlNKsDSI9RxoARNnJDNWHjCjnv2JxDWxkIHkmlvr7rs
1CjoqRKa74HpX739TxDIIEG0qE2dOvjatnhMTTadH1e8Sn083So5B9s0yYFQz2vS
gj4vPZBjRxv6xxgAREQBEwelnE2J4o0UP1jsfQOVIo84yE8Sbf3STdJOqhTzot8X
lz/KhpWGe03MbDqeS9IDYqzb2N4+/Bos4XyWswrARMJnELCgvRMvmLSz7fVXZ6Go
77gzIv7tzB/Mg09ByoC7/imXxTbuOj+hLO2+Rr2Xb+i+PghcrR76t0NQix/W2oS5
esv961kZTwRX2aAuiDGPTbIt1HtoF65piDUel/AjUG0Ef1CeDlE=
=zR/D
-END PGP SIGNATURE-

Bug#1013117: rust-mime: please update to v0.3.16

[Jonas Smedegaard]

Source: rust-mime
Version: 0.3.9-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to upstream release v0.3.16, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsX4IACgkQLHwxRsGg
ASFZgQ//aziu8B2F3wMYrxvqU2JysnQnssuW3fsWJtUAgoSOCYk3ESTjnRiM6N6F
vAOhlCiL/nQ3hrqtUVJu4ZzIHKjTxLiri59Y8GPscuL4xgrVbJP23vq3CPZUAOrt
a7DNI0cHO99TTrzI/RQHErsnceucPwC7SBoTse47Mqd/PIGNGYaPqF7/zu6XjezL
YgjwA6YY9JGjQ824IoTR43OYNpHMGYoL08B73F4ANIkE0WTjGfGXIUIZUaidP7My
99CGzdVzfYHVjUxXuO1Kx1GsiIXZTlLEvRNTTvHS0azInLSpsZLebXvv7c+JsWAy
JCBiqDEsvCOm+Q0VKLNks97OghKwHDFrda/+h8mO8wwGxwFVRPP6SjmHXyG05uu8
aPfVYb7eaeEdTDGXyEbfXyOLWQtlHBSJ5cePsVt47P6HUgKnVGKmiUvc7dh+rMla
dPOMhl59oi8aQT3m7Sd1VhTHidzcqEcvdaAghcNb9Z8HZwrvPn0qHFxy9MGPCPqX
X6ECmpNV+YTHbQHQT01o+jU3ZyuNE167vsYny3CRo1ehnHPJXYJtO0axgZpJumvn
MuQm5AlQ8kvh2tHKQJO6Fsg6Eo5hDH/jf2d0sAcU6HZGkpJijbzTEMTjLmYKqcP6
yDX7a23/3VpmgTOFAJgTUbjueeHAZkRDM6Y5hPI87WXPyFTX2IU=
=nwMh
-END PGP SIGNATURE-

Bug#1013116: rust-lexical-core: please upgrade to v0.7 (or v0.8)

[Jonas Smedegaard]

Source: rust-lexical-core
Version: 0.4.3-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream branch v0.7 (or v0.8), needed by projects I
am preparing for Debian.


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsXx0ACgkQLHwxRsGg
ASF++g/+LDgexxngn8V2a9m/ZVVtkUDoXcC/fBtYbmwVbFSaWUEO3eixKUYIbCVF
ZUAcTOcvcgLsikZJN1sQI9Ivpy65DMl51quNV8XgTvQHX5Gck725KUvBgp15NHIe
lquDAbvyvaMaVlbleEf7ZGSrmS+DI0odCdmR0Vitam6YsYFFg36LDN7Mm/aierG8
81Mo1uulvSKcztY311UoYr9Ra+RnM2Ks58Gffck/KtOfXvWDuuPCkhsNoHzo5yi1
YJ9srkNPVMaOn8o2iYYUVQn/abLhk8iEbOLKZEPbhViIrzvxJ75xixBvGDaU9IFZ
2+WfF1MzU0HsGiPkqXBaBqQa943PgK7AEXnRwRHDPd7N1sETcarkhCp8Hvt/lW+X
K1oEpWPmI14dukD1bUY4w9EgUyFbxhsuhqxDvhqqIUTR0ziwaA9bpaDXmCncYOE2
JrXHLXtOPJX2j0luMoJmQLuw2Z6k44NfCteR73Rh/k6V1qRxXjapYL4cHprYUReY
CsFR3iBKMbnRRqoXqgpMu5fY8bjIF06LGpOC0ruQuYCIB/loqq0HphZHne7tYXLR
t9xxiws5bc/bx9dF9A4CnSDBZcNHigeBeyzaXYngP8LRjUDgPSbpikzD1PDzBThP
nMeZIu/EJOr/neQX3u2TKgVUyz6nE5Y+68hsySnMkSIsvIFYhdE=
=p3Eh
-END PGP SIGNATURE-

Bug#1013115: rust-ipnet: please update to at least v2.3.1

[Jonas Smedegaard]

Source: rust-ipnet
Version: 2.2.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As subject says, please update to at least upstream release v2.3.1,
needed for some projects I am preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsXhYACgkQLHwxRsGg
ASGhMQ/+JoHPA4kdxpMhQzYSrvx5J17cqARelD6UJkTIJ5BKliZSq7W+1GxLosan
N7SCQm0ycTR6zmUF3wMDGKvoEUKe17rYXxmhRvnL0SNw9+MND5XNzOQzucoD2Pyp
guODXhltxu0zoc6bEFnJDsjnUQ6EktfmNkTY6M/1Fjvd4WgFVZyDA9kcfUCbyuUn
5inmfwce9PfWfwuR2Iy5R4VwpPdsBURKJEJRCWrwhAkYdH+UuVeGE5kaF+lkGFwz
Hxo4ZhhCSsttxYMS2RvU/oiC1bUb5wQMD8QtHbda3WRq7Icl79wBt2/phZXiuTZJ
EULFzrdNxLCJtnQpgPmWFx0y32A0hcaxz4+CqvLa0ijGAMx8HusZcCCFjZvvgKYw
KHXPvIV6NSGaNSVD+rlwKW2K3I2G/I7OSQFZI0uMlpzNAKQQCjuP5Ltf027ofHFM
k65wiezuq9Z/VNI8e/s7lK3Bc94rovoxKVRg7yxHzChVkBMGXiZvSkD41etcZGw8
7lgHgSTYMxSuJrhiW77vDFg7ztvshFeV3sXfkNfauMg6OjOs5mWhWbjYjeb5BhG/
hfmCAJk+xw5QQI+eIELM3WuDU+tkpYQzCfXht0UcJFfYgV2flE2bRsPA3p4aCH5c
M/GLPd3+hCPOUU3kXB8oj8AbFtm09QPSoQuVEhhr24XMPhvRNGo=
=QH+A
-END PGP SIGNATURE-

Bug#1013097: openh264: FTBFS on x32

[Bastian Germann]

Am 17.06.22 um 12:55 schrieb Laurent Bigonville:

On Fri, 17 Jun 2022 11:14:29 +0200 Bastian Germann  wrote:
 > Control: reopen -1
 >
 > The patch in https://github.com/cisco/openh264/issues/3545 does not affect 
the FTBFS.

With ARCH=x32 set, the package builds fine locally



Do you want to hand in a patch for d/rules as well?

Bug#1013097: openh264: FTBFS on x32

[Laurent Bigonville]

On Fri, 17 Jun 2022 11:14:29 +0200 Bastian Germann  wrote:
> Control: reopen -1
>
> The patch in https://github.com/cisco/openh264/issues/3545 does not 
affect the FTBFS.


With ARCH=x32 set, the package builds fine locally

Bug#1011215: openvdb: FTBFS with onetbb/2021.5.0-8 in experimental

[Gregor Riepl]

>   Could NOT find TBB (missing: Tbb_INCLUDE_DIR) (Required is at least
> version
>   "2018.0")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:594
> (_FPHSA_FAILURE_MESSAGE)
>   cmake/FindTBB.cmake:319 (find_package_handle_standard_args)
>   openvdb/openvdb/CMakeLists.txt:123 (find_package)

Maybe the same issue:
https://github.com/AcademySoftwareFoundation/openvdb/issues/1366

The solution is to update OpenVDB to at least 8.2, which has
compatibility with OneTBB 2021.5.

Bug#1011229: slic3r-prusa: FTBFS with onetbb/2021.5.0-8 in experimental

[Gregor Riepl]

> /home/merkys/slic3r-prusa-2.4.2+dfsg/src/libslic3r/OpenVDBUtils.cpp:9:
> /usr/include/openvdb/tools/MeshToVolume.h:36:10: fatal error:
> tbb/task_scheduler_init.h: No such file or directory
>36 | #include 
>   |  ^~~
> compilation terminated.

Looks like this is actually in openvdb and not slic3r-prusa.

Hopefully fixing
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011215 will fix this
issue too?

Bug#981629: #981629 fixed in selinux-utils (3.4-1)

[肖盛文]

Control: fixed -1 3.4-1


Hi,

   In newest version selinux-utils (3.4-1) on riscv, #981629 [1] is fixed.

The output in my riscv board:

gdb /sbin/sefcontext_compile
GNU gdb (Debian 11.2-1) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "riscv64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
    .

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /sbin/sefcontext_compile...
Reading symbols from 
/usr/lib/debug/.build-id/ae/c04f89b51df7a5a6159db185edf12f98bc99bc.debug...

(gdb) r
Starting program: /usr/sbin/sefcontext_compile
usage: /usr/sbin/sefcontext_compile [-o out_file] [-p policy_file] fc_file
Where:
    -o   Optional file name of the PCRE formatted binary
     file to be output. If not specified the default
     will be fc_file with the .bin suffix appended.
    -p   Optional binary policy file that will be used to
     validate contexts defined in the fc_file.
    -r   Omit precompiled regular expressions from the output.
     (PCRE2 only. Compiled PCRE2 regular expressions are
     not portable across architectures. Use this flag
     if you know that you build for an incompatible
     architecture to save space. When linked against
     PCRE1 this flag is ignored.)
    -i   Print regular expression info end exit. That is, back
     end version and architecture identifier.
     Arch identifier format (PCRE2):
     --, e.g.,
     "8-8-el" for x86_64.
    fc_file  The text based file contexts file to be processed.
[Inferior 1 (process 47533) exited with code 01]
(gdb)



There is not error now.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981629


--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013114: silx: TestRetry fails with scipy 1.8.1-4

[Drew Parsons]

Source: silx
Version: 1.0.0+dfsg-4
Severity: normal

silx debci tests have started failing in testing on amd64 running
against scipy 1.8.1-4 from unstable.

Not clear what the problem is since the test previously passed against
scipy/1.8.1-3. Maybe it's a coincidence, triggered by something else
that migrated to testing at the same time that scipy 1.8.1-4 got
uploaded to unstable. Or maybe this test is intermittently flakey, I
don't know.


Test log reports:

__ TestRetry.test_retry_in_subprocess __

options = {'exception': RetryError(''), 'retry_on_error': }

@contextmanager
def _handle_exception(options):
try:
>   yield

/usr/lib/python3/dist-packages/silx/utils/retry.py:63: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

args = ('/tmp/tmppg678tas/failcounter.txt',)
kw = {'faildelay': 0.1, 'kwcheck': True, 'ncausefailure': 3}
_retry_timeout = 30.297, _retry_period = 0.01
_retry_on_error = 
start_subprocess = .decorator..wrapper..start_subprocess
 at 0x7f92300cad40>
stop_subprocess = .decorator..wrapper..stop_subprocess
 at 0x7f9223d5c310>
p = 
queue = 
options = {'exception': RetryError(''), 'retry_on_error': }
result = RetryError('')

@wraps(method)
def wrapper(*args, **kw):
_retry_timeout = kw.pop("retry_timeout", retry_timeout)
_retry_period = kw.pop("retry_period", retry_period)
_retry_on_error = kw.pop("retry_on_error", retry_on_error)

ctx = multiprocessing.get_context("spawn")

def start_subprocess():
queue = ctx.Queue(maxsize=1)
p = ctx.Process(
target=_subprocess_main,
args=(queue, method, retry_on_error) + args,
kwargs=kw,
)
p.start()
return p, queue

def stop_subprocess(p):
try:
p.kill()
except AttributeError:
p.terminate()
p.join()

p, queue = start_subprocess()
try:
for options in _retry_loop(
retry_timeout=_retry_timeout, retry_on_error=_retry_on_error
):
with _handle_exception(options):
if not p.is_alive():
p, queue = start_subprocess()
try:
result = queue.get(block=True, timeout=_retry_period)
except Empty:
pass
except ValueError:
pass
else:
if isinstance(result, BaseException):
stop_subprocess(p)
>   raise result
E   silx.utils.retry.RetryError

/usr/lib/python3/dist-packages/silx/utils/retry.py:256: RetryError

The above exception was the direct cause of the following exception:

self = 

def test_retry_in_subprocess(self):
ncausefailure = 3
faildelay = 0.1
sufficient_timeout = ncausefailure * (faildelay + 10)
insufficient_timeout = ncausefailure * faildelay * 0.5

kw = {
"ncausefailure": ncausefailure,
"faildelay": faildelay,
"kwcheck": True,
"retry_timeout": sufficient_timeout,
}
with open(self.ctr_file, mode="w") as f:
f.write("0")
>   self.assertTrue(_wsubmain(self.ctr_file, **kw))

/usr/lib/python3/dist-packages/silx/utils/test/test_retry.py:158: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/silx/utils/retry.py:241: in wrapper
for options in _retry_loop(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

retry_timeout = 30.297, retry_period = None
retry_on_error = 

def _retry_loop(retry_timeout=None, retry_period=None, retry_on_error=None):
"""Iterator which is endless or ends with an RetryTimeoutError.
It yields a dictionary which can be used to influence the loop.

:param num retry_timeout:
:param num retry_period: sleep before retry
:param callable or None retry_on_error: checks whether an exception is
eligible for retry
"""
has_timeout = retry_timeout is not None
options = {"exception": None, "retry_on_error": retry_on_error}
if has_timeout:
t0 = time.time()
while True:
yield options
if retry_period is not None:
time.sleep(retry_period)
if has_timeout and (time.time() - t0) > retry_timeout:
>   raise RetryTimeoutError from options.get("exception")
E   silx.utils.retry.RetryTimeoutError

/usr/lib/python3/dist-packages/silx/utils/retry.py:90: RetryTimeoutError

Bug#808940: pkg-group

[Gregor Riepl]

> Something completely different:
> The list of blocking RFP bugreports scares me.
> I think not all are needed to get a working Terraform.

That dependency list doesn't look so scary any more, but maybe it has
changed significantly since the last update to the bug report.

Is someone still working on this?

While upstream provides their own Debian package servers[1], it would be
better to have Terraform in Debian.

[1] https://www.terraform.io/downloads

Bug#1013112: angelfish: Uninstallabale due to Qt transition, but not listed on https://release.debian.org/transitions/html/qtbase-abi-5-15-4.html

[Axel Beckert]

Package: angelfish,release.debian.org
Version: angelfish/22.04-1
Severity: serious

Hi,

seemingly due to the current Qt transition
(https://release.debian.org/transitions/html/qtbase-abi-5-15-4.html),
angelfish becomes uninstallable (i.e. aptitude wants to remove it) if I
try to upgrade all the Qt packages in unstable.

Reason seems this dependency:

ii  libqt5webenginecore5 [qtwebengine-abi-5-15-5]  5.15.8+dfsg-1+b2

The current libqt5webenginecore5 in Unstable only "Provides:
qtwebengine-abi-5-15-10".

But angelfish is not listed on
https://release.debian.org/transitions/html/qtbase-abi-5-15-4.html — not
even if I display the "good" ones.

So I assume that this transition misses relations to
qtwebengine-abi-5-15-10 and qtwebengine-abi-5-15-5.

(Filing primarily against angelfish, but also against release.debian.org
as it seems to be an oversight in this transition and a BinNMU by the
release team might fix this already.)

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

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages angelfish depends on:
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-2
ii  libkf5configcore5  5.94.0-3
ii  libkf5configgui5   5.94.0-3
ii  libkf5coreaddons5  5.94.0-1
ii  libkf5dbusaddons5  5.94.0-1
ii  libkf5i18n55.94.0-1
ii  libkf5notifications5   5.94.0-1
ii  libkf5windowsystem55.94.0-1
ii  libqt5core5a   5.15.2+dfsg-16+b2
ii  libqt5gui5 5.15.2+dfsg-16+b2
ii  libqt5network5 5.15.2+dfsg-16+b2
ii  libqt5qml5 5.15.2+dfsg-10
ii  libqt5quick5   5.15.2+dfsg-10
ii  libqt5sql5 5.15.2+dfsg-16+b2
ii  libqt5webengine5   5.15.8+dfsg-1+b2
ii  libqt5webenginecore5 [qtwebengine-abi-5-15-5]  5.15.8+dfsg-1+b2
ii  libqt5widgets5 5.15.2+dfsg-16+b2
ii  libstdc++6 12.1.0-2
ii  qml-module-org-kde-kirigami2   5.94.0-1
ii  qml-module-qtfeedback  5.0~git20180903.a14bd0b-3
ii  qml-module-qtwebengine 5.15.8+dfsg-1+b2

angelfish recommends no packages.

angelfish suggests no packages.

-- no debconf information

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

[Thomas Schmitt]

Hi,

i followed David's advise to consider the warnings of shellcheck, to drop
the demand for bash, and to check early whether all needed programs are
available. xorriso gets now checked for being young enough for the job
of replaying the boot related commands as detected with input ISO 1.
(1.3.2 in Debian 8 is too old. 1.4.6 in Debian 9 is ok.)

The warnings yielded no real problem fixes but several improvements in
regard to general shell code quality.
The switch from /bin/bash to /bin/sh was not costly. A printf formatter
had to be changed and a use of "type -p" for a message was dropped.

An test installation with the resulting ISO succeeded and was able install
further packages from all three merged DVD ISOs.
(I still could need proposals for further checking the fitness of the ISO.)


As before, the script is available at
  
https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos
with
  
https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos.sig

The changes are to see at
  
https://dev.lovelyhq.com/libburnia/libisoburn/commit/34981b1278610d3f31da90f57fdf1378d6012074


Have a nice day :)

Thomas

Bug#1012773: gudhi: drops libtbb dependency when built with 2021.5.0

[Gard Spreemann]

Graham Inggs  writes:

> Source: gudhi
> Version: 3.5.0+dfsg-2
> Severity: important
>
> Hi Maintainer
>
> When gudhi was recently binNMU'd for the onetbb transition, it
> silently lost its dependency on libtbb.  Compare the "Depends:" line
> of the python3-gudhi binary package in the most recent build log [1],
> to the previous one [2].
>
> I did not find any errors in the most recent log, but I did notice
> that the lines below, from the previous log, were missing.
>
> Regards
> Graham
>
>
> [1]
> https://buildd.debian.org/status/fetch.php?pkg=gudhi=amd64=3.5.0%2Bdfsg-2%2Bb1=1655137074=0
> [2]
> https://buildd.debian.org/status/fetch.php?pkg=gudhi=amd64=3.5.0%2Bdfsg-2=1651405629=0
>
>
> -- Performing Test TBB_without_pthread
> -- Performing Test TBB_without_pthread - Failed
> -- Performing Test TBB_with_pthread
> -- Performing Test TBB_with_pthread - Success
> -- Found Intel TBB
> TBB found in /usr/lib/x86_64-linux-gnu

Hello,

Thanks a lot for this report. Upstream is aware of the problem [1], and
I will work with them to try to rectify it.

[1] https://github.com/GUDHI/gudhi-devel/issues/511


 Best,
 Gard


signature.asc
Description: PGP signature

Bug#1013111: ITP: mepp-gui -- 3D MEsh Processing Platform

[Gürkan Myczko]

Package: wnpp
Severity: wishlist
Owner: Gürkan Myczko 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: mepp-gui
  Version : 0.14.3
  Upstream Authors: 2012-2022 University of Lyon and CNRS (France)
  URL : https://projet.liris.cnrs.fr/mepp/mepp2/
* License : LGPL-3.0-or-later
  Description : 3D MEsh Processing Platform
 This is software for processing and visualizing 3D surface meshes and 
point

 clouds. It provides both an application programming interface (API) for
 creating new processing filters and a graphical user interface (GUI) 
that

 can be used directly and integrate new filters as plugins.

Bug#1013097: openh264: FTBFS on x32

[Bastian Germann]

Control: reopen -1

The patch in https://github.com/cisco/openh264/issues/3545 does not affect the 
FTBFS.

Bug#932927: fixed in 4.1.1-5

[肖盛文]

control: fixed -1 4.1.1-5


tests/unit$ ./test_auth is run OK now:


./run.sh test_list
unit/test_auth . ok


atzlinux@Debian-StarFive:~/libotr/tests/unit$ ./test_auth
1..5
ok 1 - OTR auth info init is valid
ok 2 - OTR auth info clear is valid
ok 3 - OTR auth start v23 is valid
ok 4 - Copy not done
ok 5 - Copy OK


--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013110: ITP: rapiddisk -- Linux RAM Drive and Caching kernel modules (DKMS)

[Gürkan Myczko]

Package: wnpp
Severity: wishlist
Owner: Gürkan Myczko 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: rapiddisk
  Version : 8.1.0
  Upstream Authors: Petros Koutoupis 
  URL : https://github.com/pkoutoupis/rapiddisk
* License : GPL-2.0-or-later
  Description : Linux RAM Drive and Caching kernel modules (DKMS)
 This software defined advanced RAM drive and storage
 caching solution. This suite includes a collection of modules,
 configuration files, and command line utilities for managing
 RapidDisk enabled storage volumes and accessing them either
 locally or across an NVMe Target network.
 .
 This is the kernel module for Linux.

Bug#851555: Retitle tasksel bug to focus on an actual solution

[Andreas Tille]

Control: retitle -1 Please enable hierarchical tasksel to support Blends in 
installer

The origin of this bug is actually #186085 which was marked done and is archived
without a real solution (unarchiving seems not to work these days).  Here is a
collection of links to the topic from mailing lists.  If you want to discuss the
issue please always CC this bug report:

 Any news about Blends in tasks selection (Was: Debian Installer Jessie Beta 2 
release)
   https://lists.debian.org/debian-devel/2014/10/msg00113.html

 Next attempt to add Blends to Debian installer (very long thread about several 
years)
   https://lists.debian.org/debian-devel/2018/08/msg00221.html
   https://lists.debian.org/debian-devel/2022/01/msg00116.html
   https://lists.debian.org/debian-devel/2022/01/msg00177.html

 Hierarchical tasksel / Blends support (Was: Debian Installer Buster Alpha 5 
release)
   https://lists.debian.org/debian-devel/2019/02/msg00058.html

This is just a small collection of entry / important links.  Please keep this 
bug
in CC for any contribution to this topic.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#1013109: rust-wait-timeout: please upgrade to newer branch v0.2

[Jonas Smedegaard]

Source: rust-wait-timeout
Version: 0.1.5-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As subject says, please upgrade to newer upstream branch v0.2,
needed by projects I am preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsOjkACgkQLHwxRsGg
ASHsrA/+Kmp7IPR32RJLhtiSsgWBsL/zu/8qHzm8+q9AupAedU3LfiRa6nMVMQx1
p3k3Qs7MzNUVKutZZLZjfqOFdtIlPMt5MmjeP0dKEH/gjdD5ZxpLyDOdx+DZVgjq
KfY96XdzCFFg42oGg3S9XQIQPpqQAye4TW2i9HuMJeramGagsTWcjGcZZzdV3KEU
Y3GZY2PGchagBSdkPDs11fDPaX9kxS5WVua9LFolYbTy4S0emSfrFu9umMGPcx5K
vXZUrnPRhasN8Uonn89IsD+jrpB02PJueUPDeLFboH5+YsBUPpVN6K3Azb+r3nw4
eUQOsUwUJ8QBFJEX/4PvtFKKTdIltyh4mjlvbUBnXKwbHlgzd13d81Iv/edQQKid
y3Ob3iZo31tJLguZ14wJ7/ECfRoiQiLYsEdofHRAQK8ce+i3B3bO/L9ZtyWFtfUZ
tVVhRCHrrkwCfwADM7sferQqsIh40R70uP4LbsxBXsG945RrIL4MMmxbSDqVcOvi
mT46Ws8+j+FDw82H0Js8T1z1DKHAuxc5dFP4435hi45csLVEQ5UxaFvB+5ANW1OE
e3n4B6x6adh5k1uHozBtJnn5IzJEXZvn4hwWilC7JKhElTYZPwSpAx4qIL1WFUwh
CCfl9Ey5WwGwn6rEWc60MdICq/L+8XP7q+ZYPOx7ymEWobm3/G8=
=/cz7
-END PGP SIGNATURE-

Bug#1013108: rust-tokio-util: please upgrade to v0.7

[Jonas Smedegaard]

Source: rust-tokio-util
Version: 0.6.9-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As subject says, please upgrade to newer upstream branch v0.7, needed by
projects I am preparing to package for Debian.

 - Jonas


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsOZYACgkQLHwxRsGg
ASHC6hAAoVejGqwUjuYMAqUFkCHBlO03l7qsTn3jQHcnHwz9OAOakkT7JUrbX1lA
+nra8HqF3kJcxQlD1v+FPf1y/6j5JUES/S8df0+D5lXGK4V6xG0TCMCGeQcfOggE
rwaku6Mm9hFGZ2DesB6H49ES/v/hJ/WcX0QqNMi7v4DwN3b7P+AaE3RMJ4JQT7xf
VvhlCMpvV5Z49P4ujTAzwjINrDn3uKEtznnr1QbSJfK6Ox5msL8svWzglMcidhJ5
qmUMem89Vi1lHbBGSrMJAdI4pll6XWNH1IgZWp6942eLqMd7Y6jGay1rPdr5bLN4
672Q1mM4QYo1TktYLMM/DTGpjcK+aiCCB1wLIz6FeYJZi2LP02clyLrkeDLXW9VV
U/BifEv8DDejwrRukBvqlFgTLudl894cj+HB0EtXjDb5vUEgZJemZlYpXr1OTdS6
WPxhrKEQcxbEHrQy6k0bLTILUgt/J1puhwtEFZZBR+Gzq3u1qYnxX6vyCTnLEB5j
v9aihi1X8QvnP1jx2Z0VE20V4iMLbgeN08JkhcFrf9vtUQzmF7/g2/OjiihuBkks
JcQaDFr6V274FUmO5+QLrvsAYJq0wT5Ow+khe9dexYSOVej0LJJRcAaDrvSzCYc/
43Y7A8XemGZt1YMnSLP0RKQZiIVHiA8Eu5A4WmAkyIw/LXHmSB0=
=Wyjo
-END PGP SIGNATURE-

Bug#1013107: rust-stable-deref-trait: please update to v1.2

[Jonas Smedegaard]

Source: rust-stable-deref-trait
Version: 1.1.1-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As subject says, please upgrade this to upstream release v1.2 branch,
needed by projects I am currently packaging for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsOGEACgkQLHwxRsGg
ASHoBg//WgMzf7LKafotSP9H6B/98L0cG0g7ccxCp3issSvfjzEphH1lFRtARZcj
aWIlhTNF1PZIujM0cO2XJOBFsliDMyQ8eXvD38N2hxHjB/UcH6grybZCQ2lZlyXH
Fb/be/ez3JrKoYooaU/03HMP9PNssgBqaJb7d/i1VF138pfXw7pXbhHjUyuypOkj
WPwAh5m/lO6gMtxf1rVzNFWkdGAuV9mdPucnL/QwVtQNZ8D93SElcpew/LitfAQ9
sxezcEktP+3Ncx+ioEfc0EG8Oc9GzfROFOLaDfw1HnGM4PewFdQ4KBlvkU+bNZyX
d4snoT0koB6hLfEo3ENWPCYsQVaq3BqvmqpFiidKMl6PoDwRwCnkFtBmDSej/Cpn
H4TsCQuDob+2w9bNS+JuJGmLrE7RbWgrhvABKzz2oqi9e2ZndaGEfbGl6TSm+bbA
144VucnnlrUnoM2PNzrp98n/SvIXY0agZctejMsLDrJU87gjfBpwbbXT6EGANSrn
5WGJURBJ81m6UQgQzpMdkqv/cjyMQYYXpMCDbIsYp+cKn7QfnNJfqVSSN41EnDkT
duGRXUKaZnWdxt8S2AhTBbLeyxPRMD6fjV4B+88aI3QQpQiapFhBxf/yBg8MRpFW
VfcPAZf1J7bSvimlhaKNhjeEwgcyugoejC92QLHWI2ntwNJ275M=
=oLI1
-END PGP SIGNATURE-

Bug#1013106: rust-pin-project: version in Debian was yanked upstream

[Jonas Smedegaard]

Source: rust-pin-project
Version: 0.4.8-1
Severity: important
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Rust crate pin-project in Debian was released upstream more than 2 years
ago and has sinced been yanked, as has multiple succeeding upstream
releases.

Please update to newest v0.4 release, or better: Upgrade to stable v1
which is also a blocker for some packages I am preparing.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsNckACgkQLHwxRsGg
ASFjlA//XgHihfAo+HXnUMvl/u7ca5YENCg7jsPAilLGA3z1WzNM8tzmPCommuIk
d4HORy6stnst6wQ1teYlBMguz79A7tcQLOiRCLvxcHjIjFhck4tRk9Z5Yg+s7hdd
WYDrG8QqrTMyo+p+JbIFinxue8heIKZRZuh6S/7dnHwDvSMazM/hGSx+tAAiOtsE
UhfHT83WKaY4ct6h5JUjnipUUh1mIzLsDKcYiAoQjYv8T7swT8Um/fXQopb5LMin
EZADJfxzKvnM5KknaZDMda4LXW4HaisZ2soUWrqLJM4ILA37WdNijp7q+UglOmhb
gNbdN/BUQab2lHAs/j0ngig1zPjgSjzYeTqkDPz6HUtSlUd0MfCQUotvR1/z/Qc+
G0dJ1rDpnBjUY3zlC/+oU/Lh/7rvYCkp9PSqpU3hfwO4RRKqqikD4ewzPnQBt8mj
3jxU4wFgfPBfFQqvWS/yVdduFLu/1ImjlydUH4FXUmrZVhT+fpEWcq+aL7csgV58
ZwuAu3UpjnmVD5fV8iXLCuqwuwADSWm6usgxTqawxxEDlq7NVCj+4Y5NAD/HIqp9
jCJIsQgDWJZx2bSCeqA7XHP9JUTSZrcUwXucfbb9TVXQwPEVlxYC7bKJNghHFz8/
MdEgdfHvfuMc0YmF15QEg/0k5bzc8nBz11V4kZgZxyUusYoGjmw=
=y2R7
-END PGP SIGNATURE-

Bug#1013105: rust-language-tags: please upgrade to v0.3

[Jonas Smedegaard]

Source: rust-language-tags
Version: 0.2.2-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The Debian-packaged Rust crate language-tags was last updated 6 years
ago.

Please upgrade to v0.3 which is more actively maintained upstream.

Also, this blocks some packages I am preparing for Debian.

 - Jonas


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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsM9kACgkQLHwxRsGg
ASF/hhAAoZHmFqI4SO+B46vuBo9jiX+nt3qWqqMn1DSeyK1d4YV188je309sZfi2
+rp8HCn3riKjRCni/2kYIdo9rq43sDopTPQyddHZdduHy58/HZE9DY/pZIbxiks2
fQ2O1xVLsjNmHuOjdi36c7teXC9LMGUCZxUq2fhqzRjzVErvyUYTPDBCmUbA6ALj
fdgtgF+i9QqPgys/zKfKm0wOJai7qtgcHTBskqSddKquni3xclpeNpGnByZDLv9L
x53yMSrpIIGaBsXLHSQC4227fahwaBp+mkJ6hj2xOjUylT+lTYFJxGHaRRLwRj74
aLB53slT4hoDRo3BBXZ16SBtjhT7SdPegkhsSgjLuMvvcH9LZt0iulWYmIhNx1v1
ChXlsQIoraMRHM4/uxY2048aGA5LpYybUWJ1mZ8TyyFh+TNlImt9cOQOFbyry7uq
x/pouXORbNcxbODeGqCDMGCsw4iz8HHYfswxdemAiOO1GyuJOK1ZP5nwUi3XSTBl
Lmf04F1hxwuCigBYMoXkpPenQqxL8FW4TZREm2ChdZjzOIXaQs+HJtKk+igOnF5/
STi8NOiDJ+7cRXw72Dz0meXJtbJ6cyTn8k46MPPj3lhstbWZQHYv9dqkPT/Iop6e
5G3zPq1gDXA0um78x5xe0G1MG82YJ4BhaRL9npk/YEJbjd13t+k=
=EMSM
-END PGP SIGNATURE-

Bug#1013104: rust-json: please update to v0.12.4

[Jonas Smedegaard]

Source: rust-json
Version: 0.12.0-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Rust crate json packaged for Debian is 3 years old.

Please update to newest upstream release v0.12.4 (which is still 2 years
old but at least in sync with upstream).  This is needed by some
packages that I am preparing for Debian.


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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKsMvEACgkQLHwxRsGg
ASFQ/g//Rc6a/WkqIPi1M2/pvucNXORtlbwOKhst07oYHSMxoyZl781YXWwHQZvS
Ej2AMRDzAqVYH39WIahuPyzDcQILPaYXKUqq21ZYnbI+SkxihJEy/jx8vIqmQpq1
Cs/RapMlQq+ObE4N3xjn5TMy3MwsVyT62ZAEtETw2JIA01HebVCPoqRHHopv4y67
M5Zv0qz7EjCA2DRVj/5ecXYx7JhJwA8TjbVEAbTdu/b4Btw6NU/DPA7OMDyYuosK
YtW2oP3LEmmS0LpGhnC8g9rURESHcer/TEcNqqUkgQ2/LS2cTSwZB2GSDiM9IGch
l7Ujh/UjpeSJZFnVg23IqvMSUtnUYzulL7fjZsRDLZI0DyHqSJwJa7T6Rg2zxTSS
/0QvIO/F3XzhhMeAb+SVO31gSUpOEN9oJjF0TGVHwjD+m6ITAmgzxA/uADpAmwag
66dAi4NhBr57mbpyvRUyZxmc4LpwCRrXX2Xpr6HDEyyri9bng2nevYTHp9fC5I60
BmycRVG09fUxUoTSQuYPvvioWFC/ZpZzegRnoF8DIsQjtbt0KFwhRQJ2J0Txevx9
J66YvOQSOq8xlhdu9zmwK9HHjYFZYC2Bxy2Yd7TYtsUGMoXZzkOkQ0JBeGmtQjP5
wZDh8IIlzZpz2vhZXbyRnY+tqZ2hG58F83QFjLJHLmeeQRXGBXY=
=ezPZ
-END PGP SIGNATURE-

Bug#1012768: Bug#1012785: libgsasl7 depends on outdated gsasl-common version 1.10.0-5

[Sebastian Ramacher]

On 2022-06-15 11:38:11, Simon Josefsson wrote:
> > I guess this means that libgsasl7 and libgsasl18 cannot be installed
> > on the same system ever, due to the gsasl-common versioned
> > dependencies. That is unfortunate, since there is no real problem
> > with having both versions installed.
> 
> Sleeping on this, how about libgsasl18 declare a dependency on 'gsasl-
> common (>= 1.10.0-3)' instead of 'gsasl-common (= ${source:Version})'?
> 
> Then old libgsasl17 with gsasl-common can coexist with new libgsasl18. 
>  
> We would want gsasl-common to be upgraded to >= 1.11.3-2 eventually,
> but it can only happen once libgsasl7 is removed from the system,
> allowing the latest version of gsasl-common to be installed rather than
> the hard versioned dependency from libgsasl7.
> 
> I suppose we should let the transition finish first, and then address
> this.

Considering that an uncoordinated ghc transition has been started,
please consider implementing this change now. britney is currently
unable to migrate gsasl as it would cause packages to be uninstallable
in testing:

trying: libvmime/amd64 gsasl libvmime/s390x mailutils/arm64 mailutils/mips64el 
mailutils/armhf libinfinity/armel libvmime/armhf mailutils/i386 
libvmime/mips64el mailutils/amd64 libinfinity/armhf libinfinity/s390x 
libinfinity/ppc64el mailutils/mipsel libvmime/arm64 libvmime/armel 
mailutils/ppc64el mailutils/s390x libinfinity/arm64 libvmime/mipsel 
libinfinity/amd64 mailutils/armel libvmime/ppc64el libinfinity/mips64el 
libinfinity/mipsel libinfinity/i386 libvmime/i386
skipped: libvmime/amd64 gsasl libvmime/s390x mailutils/arm64 mailutils/mips64el 
mailutils/armhf libinfinity/armel libvmime/armhf mailutils/i386 
libvmime/mips64el mailutils/amd64 libinfinity/armhf libinfinity/s390x 
libinfinity/ppc64el mailutils/mipsel libvmime/arm64 libvmime/armel 
mailutils/ppc64el mailutils/s390x libinfinity/arm64 libvmime/mipsel 
libinfinity/amd64 mailutils/armel libvmime/ppc64el libinfinity/mips64el 
libinfinity/mipsel libinfinity/i386 libvmime/i386 (39, 0, 73)
got: 41+0: a-1:a-22:a-0:a-0:i-0:m-17:m-0:p-0:s-1
* mips64el: dico, dico-module-guile, dico-module-python, 
dico-module-wordnet, dicod, jabberd2, libghc-gsasl-dev, libghc-gsasl-prof, 
libgsasl7, libjreen-qt5-1, libjreen-qt5-dev, mpop, msmtp, msmtp-mta, mutt, 
pokerth, pokerth-server

Cheers
-- 
Sebastian Ramacher