Bug#1005503: [Help] Re: Bug#1005503: cdkr: FTBFS: [javac] /<>/rcdkjar/src/org/guha/rcdk/util/Misc.java:14: error: package org.openscience.cdk.inchi does not exist

2022-02-13 Thread Andreas Tille
Hi Andrius,

Am Mon, Feb 14, 2022 at 08:25:58AM +0200 schrieb Andrius Merkys:
> 
> Thanks for pinging me here. This issue is indeed Debian-specific, so the
> upstreams should not be bothered by it.

OK.
 
> In the upload of cdk 1:2.7.1-1 I have disabled InChI support once again
> due to cdk requirement of DFSG-incompatible version of InChI reference
> library. Thus cdkr is not able to find the related cdk classes no more.
> 
> The only viable solution in cdkr is disabling InChI support too, most
> likely by patching out the related classes. I will give it a look either
> before or during Debian Med Sprint.

Thanks a lot

  Andreas. 

PS: Onkar Shinde  removed from CC since e-mail
is bouncing.

-- 
http://fam-tille.de



Bug#1005735: lbreakouthd: Core dump and error messages

2022-02-13 Thread Uwe Steinmann
Package: lbreakouthd
Version: 1.0.8-2
Severity: important

Dear Maintainer,

lbreakouthd quits early with a segm fault.
Right after starting lbreakouthd I get the following on the console:


lbreakouthd 1.0.8
Copyright 2018-2021 Michael Speck
Published under GNU GPL
---
Loading configuration /home/steinm/.lbreakouthd/lbreakouthd.conf
ERROR: tools.cpp:52: FileParser(): Could not open 
/home/steinm/.lbreakouthd/lbreakouthd.conf
Loading hiscores /var/games/lbreakouthd.hscr
Initializing SDL
Mixer opened (16 channels, 1024 buf size)
ERROR: tools.cpp:181: readDir(): Could not open 
/usr/share/games/lbreakouthd/themes
No game controller found...
Speicherzugriffsfehler


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

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

Versions of packages lbreakouthd depends on:
ii  libc62.33-5
ii  libgcc-s111.2.0-16
ii  libsdl2-2.0-02.0.20+dfsg-2
ii  libsdl2-image-2.0-0  2.0.5+dfsg1-3
ii  libsdl2-mixer-2.0-0  2.0.4+dfsg1-4+b1
ii  libsdl2-ttf-2.0-02.0.18+dfsg-2
ii  libstdc++6   11.2.0-16

lbreakouthd recommends no packages.

lbreakouthd suggests no packages.

-- no debconf information



Bug#1005734: Acknowledgement (gdb 11 requires gmp to build)

2022-02-13 Thread Matthias Klose
so this only affects the gdbserver build, and the indep target. binary-arch only
build succeed with 11.1.



Bug#1005658: unison-2.51+4.11.1: FTBFS: detects changes in debian/control

2022-02-13 Thread Stéphane Glondu
Le 13/02/2022 à 13:50, Lucas Nussbaum a écrit :
> Source: unison-2.51+4.11.1
> Version: 2.51.3-1
> Severity: serious
> Justification: FTBFS
> [...]

Unison binary protocol depends on OCaml version (for the moment; this
will probably change in the next version), hence this failure.

The replacement, unison-2.51+4.13.1, has been in the NEW queue for 3
weeks. I am waiting for its acceptance before updating meta-unison and,
eventually, ask for unison-2.51+4.11.1 removal.


Cheers,

-- 
Stéphane



Bug#895440: jabref: The problem continues in Debian 11 bullseye

2022-02-13 Thread Pep Roca
Hello, Tony:

I'm sorry. Now I put the full output.

El dg. 13 de 02 de 2022 a les 09:39 -0800, en/na tony mancill va
escriure:
> Hello Pep,
> 
> On Sat, Feb 12, 2022 at 09:47:41AM +0100, Pep Roca wrote:
> > Package: jabref
> > Version: 3.8.2+ds-15
> > Followup-For: Bug #895440
> > X-Debbugs-Cc: pep.r...@gmail.com
> > 
> > I have problems to connect JabRef and LibreOffice in the jabref
> > bullseye version.
> > 
> > I do manual connection and I get the error:
> > 
> > “File not found:
> > /usr/lib/libreoffice/program/classes/program/classes/unoil.jar”
> 
> Can you please provide the output from the program start to the time
> when you attempt the connection and it fails?
> 
> DEBUG_WRAPPER=true /usr/bin/jabref

$ DEBUG_WRAPPER=true /usr/bin/jabref
[debug] /usr/bin/jabref: Picking up the JVM designated by the
alternatives system: 
[debug] /usr/bin/jabref:   JAVA_HOME = '/usr/lib/jvm/java-11-openjdk-
amd64'
[debug] /usr/bin/jabref: Found JAVA_HOME = '/usr/lib/jvm/java-11-
openjdk-amd64'
[debug] /usr/bin/jabref: Found JAVA_CMD = '/usr/lib/jvm/java-11-
openjdk-amd64/bin/java'
[debug] /usr/bin/jabref: Environment variable CLASSPATH is ''
[debug] /usr/bin/jabref: Runnning /usr/lib/jvm/java-11-openjdk-
amd64/bin/java  -classpath
/usr/share/java/jabref.jar:/usr/share/java/bcprov.jar:/usr/share/java/a
ntlr3-runtime.jar:/usr/share/java/antlr4-
runtime.jar:/usr/share/java/com.android.json.jar:/usr/share/java/common
s-cli.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-
lang3.jar:/usr/share/java/commons-
logging.jar:/usr/share/java/fontbox.jar:/usr/share/java/glazedlists.jar
:/usr/share/java/guava.jar:/usr/share/java/httpasyncclient.jar:/usr/sha
re/java/httpclient.jar:/usr/share/java/httpcore.jar:/usr/share/java/htt
pcore-nio.jar:/usr/share/java/httpmime.jar:/usr/share/java/java-string-
similarity.jar:/usr/share/java/jaxb-
runtime.jar:/usr/share/java/jempbox.jar:/usr/share/java/jgoodies-
common.jar:/usr/share/java/jgoodies-forms.jar:/usr/share/java/jgoodies-
looks.jar:/usr/share/java/jhlabs-
filters.jar:/usr/share/java/jsoup.jar:/usr/share/java/juh.jar:/usr/shar
e/java/jurt.jar:/usr/share/java/log4j-api.jar:/usr/share/java/log4j-
core.jar:/usr/share/java/log4j-
jcl.jar:/usr/share/java/microba.jar:/usr/share/java/mariadb-java-
client.jar:/usr/share/java/pdfbox.jar:/usr/share/java/postgresql.jar:/u
sr/share/java/ridl.jar:/usr/share/java/spin.jar:/usr/share/java/swingx.
jar:/usr/share/java/swing-layout.jar:/usr/share/java/unirest-
java.jar:/usr/share/java/unoil.jar --add-
opens=java.desktop/java.awt=ALL-UNNAMED net.sf.jabref.JabRefMain
22:20:39.017 [AWT-EventQueue-0] WARN  net.sf.jabref.JabRefGUI - There
seem to be problems with OpenJDK and the default GTK Look Using
Metal L instead. Change to another L with caution.
22:20:47.775 [AWT-EventQueue-0] WARN 
net.sf.jabref.gui.openoffice.OpenOfficePanel - Could not connect to
running OpenOffice/LibreOffice
java.io.IOException: File not found:
/usr/lib/libreoffice/program/classes/program/classes/unoil.jar
at
net.sf.jabref.gui.openoffice.OpenOfficePanel.connect(OpenOfficePanel.ja
va:415) ~[JabRef-3.8.2.jar:?]
at
net.sf.jabref.gui.openoffice.OpenOfficePanel.lambda$initPanel$1(OpenOff
icePanel.java:142) ~[JabRef-3.8.2.jar:?]
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967
) [?:?]
at
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:
2308) [?:?]
at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.j
ava:405) [?:?]
at
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
[?:?]
at
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonLis
tener.java:279) [?:?]
at
java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297
) [?:?]
at java.awt.Component.processMouseEvent(Component.java:6635)
[?:?]
at
javax.swing.JComponent.processMouseEvent(JComponent.java:3342) [?:?]
at java.awt.Component.processEvent(Component.java:6400) [?:?]
at java.awt.Container.processEvent(Container.java:2263) [?:?]
at java.awt.Component.dispatchEventImpl(Component.java:5011)
[?:?]
at java.awt.Container.dispatchEventImpl(Container.java:2321)
[?:?]
at java.awt.Component.dispatchEvent(Component.java:4843) [?:?]
at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
[?:?]
at
java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
[?:?]
at
java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) [?:?]
at java.awt.Container.dispatchEventImpl(Container.java:2307)
[?:?]
at java.awt.Window.dispatchEventImpl(Window.java:2772) [?:?]
at java.awt.Component.dispatchEvent(Component.java:4843) [?:?]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
[?:?]
at java.awt.EventQueue$4.run(EventQueue.java:721) [?:?]
at java.awt.EventQueue$4.run(EventQueue.java:715) 

Bug#1005734: gdb 11 requires gmp to build

2022-02-13 Thread Matthias Klose
Package: src:gdb-mingw-w64
Version: 11
Severity: important
Tags: sid bookworm

gdb 11.1 release notes read:

* Building GDB now requires GMP (The GNU Multiple Precision Arithmetic
  Library).

Please package gmp for mingw. It's unlikely that bookworm will ship with gdb
10.x, and Ubuntu already uses gdb 11.1.



Bug#1005503: [Help] Re: Bug#1005503: cdkr: FTBFS: [javac] /<>/rcdkjar/src/org/guha/rcdk/util/Misc.java:14: error: package org.openscience.cdk.inchi does not exist

2022-02-13 Thread Andrius Merkys
Control: tags -1 - help
Control: owner -1 !

Hi Andreas,

On 2022-02-13 20:14, Andreas Tille wrote:
> I noticed that a new version (2.7.1) of cdk was uploaded which is
> possibly responsible for the issue reported below.  Before I'll contact
> cdkr authors I want to make sure that its not a Debian packaging issue
> which is causing the problem below.

Thanks for pinging me here. This issue is indeed Debian-specific, so the
upstreams should not be bothered by it.

In the upload of cdk 1:2.7.1-1 I have disabled InChI support once again
due to cdk requirement of DFSG-incompatible version of InChI reference
library. Thus cdkr is not able to find the related cdk classes no more.

The only viable solution in cdkr is disabling InChI support too, most
likely by patching out the related classes. I will give it a look either
before or during Debian Med Sprint.

Best,
Andrius



Bug#1005640: Packaging effort of python3-unicodedata2

2022-02-13 Thread Yao Wei (魏銘廷)
Uh,

I just uploaded the same package to NEW queue yesterday

https://salsa.debian.org/fonts-team/python-unicodedata2

I removed the duplicated parts and linked the source files from unicode-data to 
regenerate headers to avoid having another copy of it.

Yao Wei

(This email is sent from a phone; sorry for HTML email if it happens.)

> On Feb 14, 2022, at 13:03, Boyuan Yang  wrote:
> 
> Hi all,
> 
> Please check out current progress on python3 unicode2 module packaging at
> https://salsa.debian.org/python-team/packages/python-unicodedata2 . I have
> pushed it onto NEW queue. Having another copy of unicode-data might not be
> ideal, but let's wait for the response from FTP Masters first.
> 
> Thanks,
> Boyuan Yang


Bug#1003865: Missing key

2022-02-13 Thread Kamil Jońca
Also checked:

rsync -az --progress keyring.debian.org::keyrings/keyrings/ .
for q in *; do gpg --list-packets <$q ; done |grep 648ACFD622F3D138

[...empty...]

-- 
http://wolnelektury.pl/wesprzyj/teraz/



Bug#863293: libjs-jquery-atwho: consider providing node-at.js

2022-02-13 Thread Ben Finney
Control: retitle -1 libjs-jquery-atwho: consider providing node-at.js
Control: tags -1 - confirmed
Control: tags -1 + moreinfo

On 17-Aug-2019, Ben Finney wrote:

> I'm confused; this bug report (bug#863255) is closed as resolved.

Bug#863293, on the other hand, is still being discussed, so I'm
altering the control fields accordingly.

Is the package name requested ‘node-at.js’, or ‘note-atwho’, or
something else?

-- 
 \ “Time flies like an arrow. Fruit flies like a banana.” —Groucho |
  `\  Marx |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature


Bug#1005733: g++-11 internal compiler error when building onetbb on riscv64

2022-02-13 Thread M. Zhou
Package: g++-11
Version: 11.2.0-16
Severity: normal
Justification: not release architecture, lowering severity from important

https://buildd.debian.org/status/fetch.php?pkg=onetbb=riscv64=2021.5.0-5=1644817169=0

excerpt:

[55/315] /usr/bin/c++  -I/<>/test/.. -I/<>/test 
-I/<>/src/tbb/../../include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-Wfatal-errors -Wshadow -Wcast-qual -Woverloaded-virtual -Wnon-virtual-dtor 
-pthread -std=c++11 -MD -MT 
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o
 -MF 
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o.d
 -o 
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o
 -c /<>/test/tbb/test_concurrent_unordered_map.cpp
FAILED: 
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o
 
/usr/bin/c++  -I/<>/test/.. -I/<>/test 
-I/<>/src/tbb/../../include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-Wfatal-errors -Wshadow -Wcast-qual -Woverloaded-virtual -Wnon-virtual-dtor 
-pthread -std=c++11 -MD -MT 
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o
 -MF 
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o.d
 -o 
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o
 -c /<>/test/tbb/test_concurrent_unordered_map.cpp
malloc(): unaligned tcache chunk detected
malloc(): unaligned tcache chunk detected
c++: internal compiler error: Aborted signal terminated program cc1plus
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.



Bug#1003865: Missing key

2022-02-13 Thread Kamil Jońca
Today I also faced this issue. 
I tried with and without apt-cacher-ng.

moreover (I do not know if I check properly)

%gpg --keyserver keyring.debian.org --recv-key 0x648ACFD622F3D138
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html



Bug#1005640: Packaging effort of python3-unicodedata2

2022-02-13 Thread Boyuan Yang
Hi all,

Please check out current progress on python3 unicode2 module packaging at
https://salsa.debian.org/python-team/packages/python-unicodedata2 . I have
pushed it onto NEW queue. Having another copy of unicode-data might not be
ideal, but let's wait for the response from FTP Masters first.

Thanks,
Boyuan Yang


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


Bug#1005732: RM: pgrouting [mipsel] -- ROM; sfcgal FTBFS

2022-02-13 Thread Bas Couwenberg
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pkg-grass-de...@lists.debian.org
Control: block 1005731 by -1

Please remove pgrouting from mipsel where sfcgal FTBFS as reported in #1005696.

Kind Regards,

Bas



Bug#1005731: RM: postgis [mipsel] -- ROM; sfcgal FTBFS

2022-02-13 Thread Bas Couwenberg
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pkg-grass-de...@lists.debian.org
Control: block 1005730 by -1

Please remove postgis from mipsel where sfcgal FTBFS as reported in #1005696.

Kind Regards,

Bas



Bug#1005730: RM: sfcgal [mipsel] -- ROM; FTBFS (blocks testing migration)

2022-02-13 Thread Bas Couwenberg
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pkg-grass-de...@lists.debian.org

Please remove sfcgal from mipsel where it FTBFS as reported in #1005696.

Kind Regards,

Bas



Bug#1005721: [Pkg-samba-maint] Bug#1005721: samba: Intermittent segfault+coredump when volume_label calls strlen

2022-02-13 Thread Richard Allen
Thanks Andrew,

I've done so, resulting in https://bugzilla.samba.org/show_bug.cgi?id=14978 .

https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1914420 seems to
have the same backtrace as well.

-Richard



Bug#1005729: Automatic partitioning fails on arm64 d-i with error message partman: mkfs.vfat: Not enough or too many clusters for filesystem

2022-02-13 Thread Thomas Glanzmann
Source: partman-efi
X-Debbugs-Cc: tho...@glanzmann.de
Version: 94
Severity: normal
Tags: d-i patch

Hello,
when installing Debian on an arm64 m1 machine, I get the following error during
auto partitioning or when creating a EFI System Partition with more than 256 MB:

partman: mkfs.vfat: Not enough or too many clusters for filesystem - try less 
or more sectors per cluster

When I try to manually create mkfs.vfat on the same system it works:

(air) [~] lsblk
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:00 465.9G  0 disk
├─nvme0n1p1 259:10   500M  0 part
├─nvme0n1p2 259:20 371.6G  0 part
├─nvme0n1p3 259:30   2.3G  0 part
├─nvme0n1p4 259:40 1G  0 part /boot/efi
├─nvme0n1p5 259:50  85.5G  0 part /
└─nvme0n1p6 259:60 5G  0 part
nvme0n2 259:70 3M  0 disk
nvme0n3 259:80   128M  0 disk
(air) [~] umount /boot/efi
(air) [~] mkfs.vfat /dev/nvme0n1p4
mkfs.fat 4.2 (2021-01-31)
(air) [~] mkfs.vfat -F 16 /dev/nvme0n1p4
mkfs.fat 4.2 (2021-01-31)

The sector size is report as 4096:

(air) [~] blockdev --getss /dev/nvme0n1
4096

The issue seems to be related to:

https://sources.debian.org/src/partman-efi/94/commit.d/format_efi/?hl=15#L66

Since mkfs.vfat don't have issue with creating file systems on block devices
with a sector size other than 4096, it is probably best to remove the whole code
block that sets the sectors per cluster and sector size. Find attached a patch.

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

Kernel: Linux 5.16.0-asahi-next-20220118-g5fa3c85b5f14 (SMP w/8 CPU threads; 
PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Report will be sent to Debian Bug Tracking System 

--- ./wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml.orig  2022-02-13 
09:33:30.099608502 +0100
+++ ./wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml   2022-02-13 
09:33:51.187037059 +0100
@@ -45,8 +45,8 @@
   EAP-TLS as work network.
 
 
-# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+# allow frontend (e.g., wpa_cli) to be used by all users in 'root' group
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 #
 # home network; allow all valid ciphers
 network={
@@ -79,7 +79,7 @@
 Aegis, Interlink RAD-Series)
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="example"
scan_ssid=1
@@ -101,7 +101,7 @@
 
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="example"
scan_ssid=1
@@ -123,7 +123,7 @@
 authentication
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="1x-test"
scan_ssid=1
@@ -148,7 +148,7 @@
 use.
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="example"
scan_ssid=1
@@ -178,7 +178,7 @@
 (-Dwired or -Droboswitch on command line).
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 ap_scan=0
 network={
key_mgmt=IEEE8021X
--- format_efi.orig 2022-02-14 04:42:29.023205868 +0100
+++ format_efi  2022-02-14 04:46:31.407838463 +0100
@@ -62,22 +62,8 @@
db_progress START 0 3 partman/text/formatting
db_progress INFO $template
db_progress SET 1
-   log_sector_size="$(blockdev --getss "$(cat device)")"
-   if [ "$log_sector_size" = 512 ]; then
-   mkdosfs_opts=
-   else
-   # mkdosfs has trouble handling cluster
-   # calculations for non-512-byte logical
-   # sectors.  Forcing one sector per cluster
-   # avoids this as long as the filesystem
-   # isn't too large, but that shouldn't be a
-   # problem for EFI System Partitions.
-   mkdosfs_opts='-s 1'
-   fi
if log-output -t partman --pass-stdout \
   $MKFS_FAT -F "${new_efi_fs#fat}" \
--S "$log_sector_size" \
-$mkdosfs_opts \
 "$device" >/dev/null; then
sync
status=OK


Bug#1005206: Split into separate C and C++ API packages

2022-02-13 Thread nurupo
It looks like starting with 4.0.0, C and C++ libraries got split in
separate codebases and their version numbers have decoupled -- the
latest msgpack-c release is 4.0.0, while C++ had 4.0.0, 4.0.1, 4.0.2,
4.0.3 and 4.1.0 releases[1].

[1] https://github.com/msgpack/msgpack-c/releases



Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-13 Thread Scott Talbert

On Thu, 10 Feb 2022, Andreas Tille wrote:


Control: tags -1 help

Hi,

I've updated python-envisage in Salsa[1] to the latest upstream version
and bumped its failing predepends to their according latest upstream and
fixed all bugs in those.  For envisage I'm stumbling upon a Python3.10
related bug I'd like to ask for help:

...
==
ERROR: test_exclude_multiple 
(envisage.tests.test_egg_plugin_manager.EggPluginManagerTestCase)
exclude multiple
--
Traceback (most recent call last):
 File 
"/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_plugin_manager.py",
 line 115, in test_exclude_multiple
   self._add_eggs_on_path([self.egg_dir])
 File 
"/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_based.py",
 line 59, in _add_eggs_on_path
   raise SystemError("Cannot find eggs %s" % errors)
SystemError: Cannot find eggs {}


I spent some time looking into this.  The problem is that upstream 
includes binary eggs (which are Python version specific) as part of its 
test suite.  The problem here is that there are no eggs included for 
Python 3.10.  Upstream is aware of this[1] but unfortunately, that patch 
can't be applied because it is a binary patch.  They have also later[2] 
removed the binary eggs completely, but that patch can't be applied either 
because it involves files that are not in the PyPI distribution.  The best 
solution might be do what Fedora did[3], but for that we'd probably have 
to switch to using a GitHub tarball instead of the PyPI tarball because 
the PyPI tarball is missing files.


Scott

[1] 
https://github.com/enthought/envisage/commit/d29e6f438d16fc6ac6ede5381ba12d9849187b14
[2] 
https://github.com/enthought/envisage/commit/6e5c7ba004e8700bd009c3d2b9444d543709a4d7
[3] 
https://src.fedoraproject.org/rpms/python-envisage/c/a20fa2cf6fe0eaf7604394a8b93bf8d3b48bc599?branch=rawhide



Bug#995026: Update

2022-02-13 Thread Jeremy Hendricks
Correction to above:

Option #1 is preferable as I don't know if installing updates down the road
for Option #2 would cause libnvidia-cfg1 to be installed. I assume it will
be fine but you know what they say about 'assume'.


Bug#995026: Update

2022-02-13 Thread Jeremy Hendricks
I was able to finally track down this issue. The issue is due to the
32bit packages being installed if you have 'sudo dpkg --add-architecture
i386'. If you do, 'sudo apt install nvidia-legacy-390xx-driver' will
install libnvidia-cfg1 (which is an nvidia 460 component) that causes the
initial issue and you won't have the driver installed properly.

Two workarounds if you need 32bit support like I do:

1. 'sudo apt install libnvidia-legacy-390xx-cfg1
nvidia-legacy-390xx-driver' This will prevent libnvidia-cfg1 from being
installed and things will be happy for your nvidia 400/500 series like mine.

2. Install normally and ignore the warning about the GPU not being
supported. Once it's installed, do this before you reboot: 'sudo apt purge
--autoremove libnvidia-cfg1' then reboot. You should be good now.

Option #1 is preferable as I don't know if installing updates down the road
for Option #1 would cause libnvidia-cfg1 to be installed. I assume it will
be fine but you know what they say about 'assume'.


Bug#1005404: Kernel modules fail to build with Linux 5.16 onward

2022-02-13 Thread Benjamin Kaduk
Hi Ben,

Thanks for detecting and reporting the build errors.
I'm a bit confused as to how this is "grave", though -- I would have
classified it as merely "serious" as for, e.g., 970258 and 995134.

For upstream, we went with a slightly different patch owing to the
unreliability of the linux version macros due to distros backporting many
patches --
https://github.com/openafs/openafs/commit/3daa6e97330d23ae46c4389e4041c61c1a1d76d9

I will take this as a trigger to package upstream 1.8.8.1 that includes the
fix.

-Ben

On Sat, Feb 12, 2022 at 10:53:31PM +0100, Ben Hutchings wrote:
> Source: openafs
> Version: 1.8.2-1+deb10u1
> Severity: grave
> Tags: patch upstream
> 
> The openafs modules fail to build, with the compiler reporting that
> "stdarg.h" is not found.
> 
> This is due to an intentional change in Linux 5.16 removing user-space
> headers from the kernel include path:
> .
> 
> Kernel code must use  instead of .
> 
> The attached patch fixes this and allows the build to complete.
> 
> Ben.
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 
> 'unstable'), (500, 'oldstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.15.0-3-amd64 (SMP w/2 CPU threads)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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

> From: Ben Hutchings 
> Date: Sat, 12 Feb 2022 22:25:47 +0100
> Subject: openafs: Fix  inclusion on Linux
> 
> There was an intentional change in Linux 5.16 removing user-space
> headers from the kernel include path:
> .
> 
> Kernel code must use  instead of .
> ---
> --- a/src/rx/rx_kcommon.h
> +++ b/src/rx/rx_kcommon.h
> @@ -145,6 +145,8 @@ typedef unsigned short etap_event_t;
>  /* if sys/systm.h includes varargs.h some versions of solaris have conflicts 
> */
>  # if defined(AFS_FBSD_ENV)
>  #  include "machine/stdarg.h"
> +# elif defined(AFS_LINUX26_ENV) && LINUX_VERSION_CODE >= 
> KERNEL_VERSION(5,16,0)
> +#  include 
>  # else
>  #  include "stdarg.h"
>  # endif



Bug#1005728: RM: gitlab-workhorse/experimental -- RoQA; gitlab-workhorse binary package is now built from src:gitlab

2022-02-13 Thread Andreas Beckmann
Package: ftp.debian.org
Severity: normal

See https://bugs.debian.org/991745 for the removal from sid:

On Sat, 31 Jul 2021 22:06:56 +0530 Pirate Praveen  
wrote:
> gitlab-workhorse binary package is now built by src:gitlab, but since 


Andreas



Bug#867290: ITP: libjs-blueimp-md5 -- MD5 implementation in JavaScript

2022-02-13 Thread Jonas Smedegaard
Control: owner -1 !
Control: tags -1 +pending

Quoting Johannes Schauer (2017-07-05 16:28:20)
> * Package name: libjs-blueimp-md5

Package has been prepared and should now be in NEW queue.

 - Jonas

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

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

signature.asc
Description: signature


Bug#867288: ITP: libjs-toastr -- Javascript library for non-blocking notifications

2022-02-13 Thread Jonas Smedegaard
Control: owner -1 !
Control: tag -1 +pending

Quoting Johannes Schauer (2017-07-05 16:13:50)
> * Package name: libjs-toastr

Package has been prepared and is now in NEW queue: 
https://ftp-master.debian.org/new/libjs-toastr_2.1.4~ds-3.html

 - Jonas

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

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

signature.asc
Description: signature


Bug#965436: bidiui: diff for NMU version 0.9.7-2.2

2022-02-13 Thread Jonas Smedegaard
Control: tags 965436 + patch
Control: tags 965436 + pending

Dear maintainer,

I've prepared an NMU for bidiui (versioned as 0.9.7-2.2) and
uploaded it - without delay, due to fixing RC bug.

Regards,

 - Jonas

diff -Nru bidiui-0.9.7/debian/changelog bidiui-0.9.7/debian/changelog
--- bidiui-0.9.7/debian/changelog   2021-01-05 11:57:38.0 +0100
+++ bidiui-0.9.7/debian/changelog   2022-02-14 02:22:09.0 +0100
@@ -1,3 +1,11 @@
+bidiui (0.9.7-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * use debhelper compatibility level 9 (not 5);
+closes: bug#965436, thanks to Niels Thykier
+
+ -- Jonas Smedegaard   Mon, 14 Feb 2022 02:22:09 +0100
+
 bidiui (0.9.7-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru bidiui-0.9.7/debian/compat bidiui-0.9.7/debian/compat
--- bidiui-0.9.7/debian/compat  2018-07-30 09:31:42.0 +0200
+++ bidiui-0.9.7/debian/compat  2022-02-14 02:20:35.0 +0100
@@ -1 +1 @@
-5
+9
diff -Nru bidiui-0.9.7/debian/control bidiui-0.9.7/debian/control
--- bidiui-0.9.7/debian/control 2018-07-31 08:43:56.0 +0200
+++ bidiui-0.9.7/debian/control 2022-02-14 02:20:29.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Hebrew Packaging Team 
 Uploaders: Lior Kaplan , Shachar Shemesh 
, Tzafrir Cohen 
-Build-Depends: debhelper (>= 5), zip, unzip, perl
+Build-Depends: debhelper (>= 9), zip, unzip, perl
 Standards-Version: 3.9.4
 Vcs-Browser: https://salsa.debian.org/hebrew-team/bidiui
 Vcs-Git: https://salsa.debian.org/hebrew-team/bidiui.git



Bug#466064: xserver-xorg-core: -novtswitch is still broken

2022-02-13 Thread Elliott Mitchell
found 466064 2:1.20.11-1+deb11u1
quit

I almost wonder whether I'm seeing a distinct bug since #466064 is so
old.  -novtswitch continues(?) to be problematic.  Current version the
option doesn't work.

Not switching VTs is rather valuable for having multiple X-servers
started by init and running on distinct VTs.  Combined with VMs all sorts
of interesting things become possible.

Having a broken -novtswitch option causes all sorts of trouble for such a
setup.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445



Bug#1005727: ruby-tioga: reproducible builds: Embedded date in sty file

2022-02-13 Thread Vagrant Cascadian
Source: ruby-tioga
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The tioga.sty.gz embeds the current date:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/ruby-tioga.html

  ./usr/share/doc/ruby-tioga/tioga.sty.gz

  \ProvidesPackage{tioga}[2023/03/16]
vs.
  \ProvidesPackage{tioga}[2022/02/12]

The attached patch fixes this by using the SOURCE_DATE_EPOCH environment
variable instead of the current time, which is typically set from the
timestamp in debian/changelog.


With this patch applied, ruby-tioga should build reproducibly on
tests.reproducible-builds.org!


Thanks for maintaining ruby-tioga!


live well,
  vagrant
From 59fec7800e70a9dc93a52121a813b8d1226222c6 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Mon, 14 Feb 2022 00:19:12 +
Subject: [PATCH] misc/mk_tioga_sty.rb: Use a consistent date when generating
 the sty file.

If the SOURCE_DATE_EPOCH environment variable is available, use that
instead of the current time to set the date.

https://reproducible-builds.org/docs/source-date-epoch/
---
 misc/mk_tioga_sty.rb | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/misc/mk_tioga_sty.rb b/misc/mk_tioga_sty.rb
index dcbe275..6bb4fc0 100644
--- a/misc/mk_tioga_sty.rb
+++ b/misc/mk_tioga_sty.rb
@@ -42,7 +42,11 @@ color_specs + "\nEnd_of_preamble\n" +
 
 out.close
 
-date = Date::today
+if ENV['SOURCE_DATE_EPOCH'].nil?
+  date = Date::today
+else
+  date = Time.at(ENV['SOURCE_DATE_EPOCH'].to_i).gmtime
+end
 str_date = sprintf "%04d/%02d/%02d", date.year, date.month, date.day
 
 
-- 
2.34.1



signature.asc
Description: PGP signature


Bug#1001371: pytest-twisted: (autopkgtest) needs update for python3.10: E {'warnings': 2} != {'warnings': 1}

2022-02-13 Thread peter green

On 25/01/2022 23:22, peter green wrote:

The upstream report at
https://github.com/pytest-dev/pytest-twisted/issues/146 was closed as the
additional warning is produced by Twisted. The Twisted fix isn't merged yet.


It looks like the twisted fix has now been merged upstream, does it make
sense to apply it as a patch to the Debian twisted patch to solve this bug?


The good news is that the twisted fix has been incorporated into a new
upstream version, which has been uploaded to Debian. I told debci to
re-run the test in unstable and it confirmed it was fixed.

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pytest-twisted/19192829/log.gz

The not so good news is it's currently blocked from migrating to testing
by an autopkgtest failure in gavodachs. I just filed a rc bug report
for that.

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



Bug#1005726: ruby-github-markup: reproducible builds: Embedded timestamps in documentation file

2022-02-13 Thread Vagrant Cascadian
Source: ruby-github-markup
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps timezone
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The file created.rid file shipped in the documentation embeds timestamps
that appear to be timezone dependent:

│ │ │ ├── 
./usr/share/rubygems-integration/all/gems/github-markup-1.7.0/doc/created.rid
│ │ │ │ -lib/github/markup.rb   Sun, 13 Feb 2022 11:19:23 -1200 
  
...
│ │ │ │ +lib/github/markup.rb   Mon, 14 Feb 2022 13:19:23 +1400


The attached patch fixes this by removing the file in debian/rules
before building the .deb packages, as it does not appear to be
referenced in any of the documentation.


With this patch applied, ruby-github-markup should build
reproducibly on tests.reproducible-builds.org!


Thanks for maintaining ruby-github-markup!


live well,
  vagrant
From 4318eea5612f0338558a4cdc59849264b8c1ad06 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 13 Feb 2022 23:46:55 +
Subject: [PATCH] debian/rules: Remove created.rid file from documentation.

This file contains various timestamps of the generated documentation
files, but appears otherwise unused.

https://reproducible-builds.org/docs/timestamps/
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 0161df7..4b17d23 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,7 +14,7 @@ override_dh_auto_build:
 	dh_auto_build
 	# build documentation
 	rdoc --main=README.md --exclude=commands lib
-	rm -f doc/js/*.js.gz
+	rm -f doc/js/*.js.gz doc/created.rid
 
 override_dh_auto_install:
 	# use utf-8 locale so test cases work
-- 
2.34.1



signature.asc
Description: PGP signature


Bug#1005725: gavodachs2-server: fails to install with new python3-twisted.

2022-02-13 Thread peter green

Package: gavodachs2-server
Version: 2.5+dfsg-1
Severity: serious
Tags: bookworm, sid

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gavodachs/19190406/log.gz


Setting up gavodachs2-server (2.5+dfsg-1) ...
createdb: error: database creation failed: ERROR:  database "gavo" already 
exists
Creation of gavo database failed; assuming it's already there
and carrying on.
createuser: error: creation of new role failed: ERROR:  role "dachsroot" 
already exists
*** Error: Oops.  Unhandled exception AttributeError.

Exception payload: module 'twisted.web.template' has no attribute
'_ToStan'
dpkg: error processing package gavodachs2-server (--configure):
 installed gavodachs2-server package post-installation script subprocess 
returned error exit status 1


I attempted to fix that error (debdiff attatched), however it then failed with
a "TypeError: 'Tag' object is not subscriptable", I modified the error handling
to get a backtrace, but it didn't leave me any the wiser as to what the actual
problem was.

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gavo/user/cli.py", line 152, in main
sys.exit(initdachs.main())
  File "/usr/lib/python3/dist-packages/gavo/user/initdachs.py", line 461, in 
main
initDB(dsn)
  File "/usr/lib/python3/dist-packages/gavo/user/initdachs.py", line 433, in 
initDB
_importBasicResources()
  File "/usr/lib/python3/dist-packages/gavo/user/initdachs.py", line 405, in 
_importBasicResources
from gavo.user import importing
  File "/usr/lib/python3/dist-packages/gavo/user/importing.py", line 14, in 

from gavo import api
  File "/usr/lib/python3/dist-packages/gavo/api.py", line 19, in 
from gavo import rscdesc
  File "/usr/lib/python3/dist-packages/gavo/rscdesc.py", line 27, in 
from gavo import registry
  File "/usr/lib/python3/dist-packages/gavo/registry/__init__.py", line 34, in 

from gavo.registry import oaiinter  # registration of RegistryCore
  File "/usr/lib/python3/dist-packages/gavo/registry/oaiinter.py", line 23, in 

from gavo import svcs
  File "/usr/lib/python3/dist-packages/gavo/svcs/__init__.py", line 35, in 

from gavo.svcs.common import (Error, UnknownURI, ForbiddenURI, WebRedirect,
  File "/usr/lib/python3/dist-packages/gavo/svcs/common.py", line 18, in 

from gavo.formal import nevowc
  File "/usr/lib/python3/dist-packages/gavo/formal/__init__.py", line 22, in 

from .form import Form, Field, Group, ResourceWithForm, FORMS_KEY
  File "/usr/lib/python3/dist-packages/gavo/formal/form.py", line 121, in 

class FieldFragment(nevowc.CommonRenderers, template.Element):
  File "/usr/lib/python3/dist-packages/gavo/formal/form.py", line 127, in 
FieldFragment
T.label(class_='label', for_=template.slot('id'))[template.slot('label')],
TypeError: 'Tag' object is not subscriptable
--- gavodachs-2.5+dfsg/gavo/user/errhandle.py	2021-02-18 11:44:39.0 +
+++ /usr/lib/python3/dist-packages/gavo/user/errhandle.py	2022-02-13 23:47:17.499599771 +
@@ -170,7 +170,8 @@
 			messages.append("Snafu in %s, %s\n"%(msg.excRow, msg.excCol))
 			messages.append("")
 		messages.append("Oops.  Unhandled exception %s.\n"%msg.__class__.__name__)
-		messages.append("Exception payload: %s"%utils.safe_str(msg))
+		import traceback
+		messages.append("Exception payload: %s"%repr(msg)+" "+traceback.format_exc())
 		base.ui.notifyError("Uncaught exception at toplevel")
 
 	if getattr(opts, "enablePDB", False):
diff -Nru gavodachs-2.5+dfsg/debian/changelog 
gavodachs-2.5+dfsg/debian/changelog
--- gavodachs-2.5+dfsg/debian/changelog 2021-11-17 12:55:14.0 +
+++ gavodachs-2.5+dfsg/debian/changelog 2022-02-13 23:23:02.0 +
@@ -1,3 +1,10 @@
+gavodachs (2.5+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Adapt code to support new version of twisted.
+
+ -- Peter Michael Green   Sun, 13 Feb 2022 23:23:02 +
+
 gavodachs (2.5+dfsg-1) unstable; urgency=medium
 
   [ Markus Demleitner ]
diff -Nru gavodachs-2.5+dfsg/debian/patches/series 
gavodachs-2.5+dfsg/debian/patches/series
--- gavodachs-2.5+dfsg/debian/patches/series2021-11-17 12:55:14.0 
+
+++ gavodachs-2.5+dfsg/debian/patches/series2022-02-13 23:23:02.0 
+
@@ -1 +1,2 @@
 0001-Fixing-setup.py-version-check-to-work-with-python-3..patch
+twisted-22.patch
diff -Nru gavodachs-2.5+dfsg/debian/patches/twisted-22.patch 
gavodachs-2.5+dfsg/debian/patches/twisted-22.patch
--- gavodachs-2.5+dfsg/debian/patches/twisted-22.patch  1970-01-01 
00:00:00.0 +
+++ gavodachs-2.5+dfsg/debian/patches/twisted-22.patch  2022-02-13 
23:23:02.0 +
@@ -0,0 +1,22 @@
+Description:  Adapt code to support new version of twisted.
+Author: Peter Michael Green 
+
+--- gavodachs-2.5+dfsg.orig/gavo/formal/nevowc.py
 gavodachs-2.5+dfsg/gavo/formal/nevowc.py
+@@ -41,8 +41,15 @@ class NoDataError(Exception):
+ """
+ pass
+ 
++#newer versions of twisted moved _ToStan from 

Bug#987266: The preinst check for kernel release >255 broke my LTS upgrade

2022-02-13 Thread Nikolaus Schulz
Hi,

this check just broke the dist-upgrade of my server, going from jessie
to stretch.

While my machine is a vserver with a kernel 4.4.268 which is not part of
the Debian OS that I control, the current Debian kernel in stretch is
4.9.290-1 if I'm not mistaken, so I guess it's also affected.

So it looks to me like this is breaking any updates of glibc in stretch?

But breaking updates in a vserver scenario like above is also bad IMO.

I'm not sure if the preinst check is entirely obsolete, but if not, it
may at least additionally check if the current kernel has the version
clamping fix by upstream applied[1], which is true for -stable versions 
>=4.4.257
and >=4.9.257.

Best regards,
Nikolaus

[1] 
https://lwn.net/ml/linux-kernel/20210208145805.898658...@linuxfoundation.org/



Bug#699746: #699746 x11-utils: xprop assumes that WM_ICON_NAME and WM_NAME are encoded in ISO-8859-1

2022-02-13 Thread Thomas Dickey
I was recently reminded of this one, and can see that it's no longer relevant:

+ The bug-report made incorrect assumptions about what xprop ought to be doing.
  So it's not relevant to xprop.

+ Cloos' comment about xterm was interesting but not useful for xterm, because
  the encoding as STRING rather than COMPOUND_STRING is done by the X Toolkit
  library.
  
  Reading the Shell.c file in libXt, arguably an application _could_ set the
  resources titleEncoding and iconNameEncoding while setting the title and
  icon-name, but even setting those to COMPOUND_STRING (which does _not_
  hold UTF-8) wouldn'd make the server transmute those into EWMH names (which
  _does_ hold UTF-8).

+ Regarding xterm, my changes in patch #349 make it do by default what Vincent
  assumed.

 Patch #349 - 2019/09/22
 * improve title-string feature:
  + if any of allowC1Printable, utf8Title or titleModes hint that
an  application  might  send a title-string encoded in UTF-8,
check  if  that  is  the  case,  and  if it is recodable into
ISO-8859-1, use that for the ICCCM-style title.
  + check  if the title given by a control sequence happens to be
already  encoded  in UTF-8, to avoid double-encoding (FreeBSD
#240393).
  + Make sameName resource work for the EWMH titles.
  + Modify menu-state of utf8Title to be consistent with the utf8
source,  i.e., setting the EWMH properties automatically when
UTF-8 is active.

just for grins, I'll close this (expecting the usual response from Vincent).

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature


Bug#997120:

2022-02-13 Thread Jose Luis Rivero
Hello!

>
> Am Mon, Feb 07, 2022 at 10:57:36PM +0100 schrieb Emmanuel Promayon:
> > Thank you very much for this patch, you are absolutely right: your patch
> > fixes the problem!
>
> Possibly it fixes camitk for the current package in Debian.  So thanks a
> lot in any case.
>

You are welcome. This bug is preventing one of my packages (Gazebo) from
being
migrated to testing. Could we please upload a revision bump of the current
version to solve this issue while we work on 5.0.2?

> > It should also work perfectly well to make the last upstream version
(5.0.2)
> > build properly. Andreas started to check on last month but with your
patch,
> > it should work.
> > I can confirm anyway that camitk version 5.0.2 builds well with ITK5
with
> > the help of your patch.
>
> I've pushed an adapted patch to Git but I can't confirm that it builds.
> May be you can have another look and compare the status in Git with your
> local build?  There are about 100 failed tests in the build time test
> suite.  Unfortunately salsa-ci chokes in source extration (no idea why
> so I can only provide my local build log if you can't verify this.
>

I think that the problem in salsa is that the artifact handling between
steps
is broken due to the high number of files of camitk. We can probably copy
the
workaround that the linux kernel team has in place, see:

https://www.decadent.org.uk/ben/blog/ci-for-the-debian-kernel-team.html

Running the salsa catmik code in my sbuild run seems fine to me:

"""
100% tests passed, 0 tests failed out of 526
...
+--+
| Summary
   |
+--+

Autopkgtest: pass
Build Architecture: amd64
Build Type: full
Build-Space: 6680544
Build-Time: 743
Distribution: unstable
Host Architecture: amd64
Install-Time: 74
Job: /home/jrivero/code/debian/camitk_5.0.2-1.dsc
Lintian: warn
Machine Architecture: amd64
Package: camitk
Package-Time: 823
Piuparts: fail
Source-Version: 5.0.2-1
Space: 6680544
Status: successful
Version: 5.0.2-1

"""

The Piuparts failure I think is something related to my local setup but
compilation, test and autopkgtest seems fine to my eyes.

Thanks.


Bug#837878: dh-python: support for running test suites with pytest-runner

2022-02-13 Thread Stefano Rivera
Hi Sean (2016.09.15_00:55:08_-0400)

tox is a good way to test against an installed version of the module.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Bug#943580: dh_python3 doesn't recognize typing

2022-02-13 Thread Stefano Rivera
Hi Russ (2019.10.26_16:25:35_-0400)
> I: dh_python3 pydist:228: Cannot find package that provides typing. Please 
> add package that provides it to Build-Depends or add "typing python3-typing" 
> line to debian/py3dist-overrides or add proper dependency to Depends by hand 
> and ignore this info.
> 
> typing is part of the standard library as of Python 3.5.

Generally when something available in PyPI gets added to the stdlib, we
don't do anything special in pybuild to support packages that depend on
the PyPI lib. Either the module is packaged in Debian, and unnecessarily
installed, or the package maintainer should patch-out the dependency.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Bug#949285: src:dh-python: should parse DH_OPTIONS

2022-02-13 Thread Stefano Rivera
Hi Andrej (2020.01.19_06:40:37_-0400)
> dh-python* does not currently parse DH_OPTIONS.

It does, but was appending rather than prepending them.

We can fix that.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Bug#1005724: python3-clang-13: python package not advertised enough

2022-02-13 Thread Marc Glisse
Package: python3-clang-13
Version: 1:13.0.1-2
Severity: normal

Dear Maintainer,

I have python3-clang-13 version 1:13.0.1-2 installed and can import it
just fine. However, some tools fail to find the package

$ pip3 check
tensorflow 2.8.0 requires libclang, which is not installed.
$ python3 -c 'from importlib.metadata import version; 
print(version("libclang"))'
[...]
importlib.metadata.PackageNotFoundError: libclang

If I run `pip3 install libclang`, those errors disappear. I think it may
be because you don't include libclang-13.0.0.dist-info in the package,
but I am not a pro of python packaging.

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

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

Versions of packages python3-clang-13 depends on:
ii  libclang-13-dev  1:13.0.1-2
ii  python3  3.9.7-1

python3-clang-13 recommends no packages.

python3-clang-13 suggests no packages.

-- no debconf information



Bug#1005722: ITP: mistune0 -- Markdown parser for Python 3

2022-02-13 Thread Jonas Smedegaard
Quoting Pierre-Elliott Bécue (2022-02-13 22:55:42)
> * Package name: mistune0

Since this source package produces only python module packages, please 
name the source package "python-mistune0" instead, to avoid needless 
pollution of the global package namespace.

Thanks for packaging this!

 - Jonas

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

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

signature.asc
Description: signature


Bug#985661: libboostM.mm-dev no .pc file

2022-02-13 Thread Valerio Messina

thank you,
I think libboost can be the last notable lib that miss the pc file



Bug#1005232: xterm 366-1+deb11u1 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1005232 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: xterm
Version: 366-1+deb11u1

Explanation: fix buffer overflow issue [CVE-2022-24130]



Bug#1005355: ldap2zone 0.2-11+deb11u1 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1005355 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: ldap2zone
Version: 0.2-11+deb11u1

Explanation: use "mktemp" rather than the deprecated "tempfile", avoiding 
warnings



Bug#1005351: apache-log4j2 2.17.1-1~deb11u1 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1005351 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: apache-log4j2
Version: 2.17.1-1~deb11u1

Explanation: fix remote code execution issue [CVE-2021-44832]



Bug#1005723: RFS: rednotebook/2.23+ds-1 -- Modern desktop diary and personal journaling tool

2022-02-13 Thread Philip Wyett
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "rednotebook":

 * Package name: rednotebook
   Version : 2.23+ds-1
   Upstream Author : Jendrik Seipp 
 * URL : https://rednotebook.app
 * License : LGPL-3+, PSF-2, CC0-1.0, GPL-2+, GPL-3+
 * Vcs : https://github.com/jendrikseipp/rednotebook
   Section : text

It builds those binary packages:

  rednotebook - Modern desktop diary and personal journaling tool

To access further information about this package, please visit the following 
URL:

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

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_2.23+ds-1.dsc

Changes since the last upload:

 rednotebook (2.23+ds-1) unstable; urgency=medium
 .
   * New upstream version 2.23.
   * Drop/Delete patches as unneeded.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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


Bug#1005722: ITP: mistune0 -- Markdown parser for Python 3

2022-02-13 Thread Pierre-Elliott Bécue
Package: wnpp
Severity: wishlist
Owner: Pierre-Elliott Bécue 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: mistune0
  Version : 0.8.4
  Upstream Author : 2014-2018 Hsiaoming Yang 
* URL : https://github.com/lepture/mistune
* License : BSD-3-Clause
  Programming Lang: Python3
  Description : Markdown parser for Python 3

This is a source repackaging of mistune to allow a coexistence of
mistune v 2 or more (in src:mistune) along with mistune 0.8.4 (in
src:mistune0), as reverse dependencies won't be able to move forward as
fast as one would expect.

This repackaging is the result of a discussion in bug 1003567.


Bug#1005721: [Pkg-samba-maint] Bug#1005721: samba: Intermittent segfault+coredump when volume_label calls strlen

2022-02-13 Thread Andrew Bartlett
On Sun, 2022-02-13 at 15:12 -0600, Richard Allen wrote:
> 
> It seems 4.13 is out of maintenance with upstream, but when I have
> time I'll try
> to pull down the latest from upstream and see if I can reproduce and
> create a bug
> there if needed or otherwise report back.

Either way this is exactly the kind of bug to report upstream, as an
initial position all patches applied in Debian first have to be
accepted upstream.

I've sent you an invite to bugzilla.

Ideally do check with current master, as if it works you can then find
the patch that fixes in and just propose that to Debian.

Andrew Bartlett

-- 
Andrew Bartlett (he/him)   https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Team Lead, Catalyst IT   https://catalyst.net.nz/services/samba

Samba Development and Support, Catalyst IT - Expert Open Source
Solutions



Bug#1005466: chromium: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'gen/chrome/browser/resources/pdf/pdf_internal_plugin_wrapper.rollup.js'

2022-02-13 Thread Andres Salomon

On Sun, 13 Feb 2022 03:12:03 -0500 Andres Salomon wrote:
> On Sun, 13 Feb 2022 08:16:32 +0100 Lucas Nussbaum wrote:
> > Source: chromium
> > Version: 98.0.4758.80-1
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20220212 ftbfs-bookworm
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
>
> >
>
>
> Thanks, I'm aware (and cranky about it). Something broke with nodejs,
> and I'm testing fixed packages now.
>


I pushed the working fix to 
https://salsa.debian.org/chromium-team/chromium/-/commits/master


However, the chromium release calendar says that a new security release 
will go out on Feb 15th, so at this point I think I'll wait for that to 
do an upload.





Bug#996624: node-getobject 0.1.0-2+deb10u1 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 996624 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: node-getobject
Version: 0.1.0-2+deb10u1

Explanation: fix prototype pollution issue [CVE-2020-28282]



Bug#1005374: apache-log4j1.2 1.2.17-8+deb10u2 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1005374 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: apache-log4j1.2
Version: 1.2.17-8+deb10u2

Explanation: resolve security issues [CVE-2021-4104 CVE-2022-23302 
CVE-2022-23305 CVE-2022-23307], by removing support for the JMSSink, 
JDBCAppender, JMSAppender and Apache Chainsaw modules



Bug#1005353: apache-log4j2 2.17.1-1~deb10u1 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1005353 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: apache-log4j2
Version: 2.17.1-1~deb10u1

Explanation: fix remote code execution issue [CVE-2021-44832]



Bug#1005000: atftp 0.7.git20120829-3.2~deb10u3 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1005000 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: atftp
Version: 0.7.git20120829-3.2~deb10u3

Explanation: fix information leak issue [CVE-2021-46671]



Bug#1005233: xterm 344-1+deb10u2 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1005233 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: xterm
Version: 344-1+deb10u2

Explanation: fix buffer overflow issue [CVE-2022-24130]



Bug#895440: jabref: The problem continues in Debian 11 bullseye

2022-02-13 Thread Pep Roca
Hello, Tony:

Thanks so much for this quick response.

El dg. 13 de 02 de 2022 a les 09:39 -0800, en/na tony mancill va
escriure:
> Hello Pep,
> 
> On Sat, Feb 12, 2022 at 09:47:41AM +0100, Pep Roca wrote:
> > Package: jabref
> > Version: 3.8.2+ds-15
> > Followup-For: Bug #895440
> > X-Debbugs-Cc: pep.r...@gmail.com
> > 
> > I have problems to connect JabRef and LibreOffice in the jabref
> > bullseye version.
> > 
> > I do manual connection and I get the error:
> > 
> > “File not found:
> > /usr/lib/libreoffice/program/classes/program/classes/unoil.jar”
> 
> Can you please provide the output from the program start to the time
> when you attempt the connection and it fails?
> 
> DEBUG_WRAPPER=true /usr/bin/jabref

Here it is:

$ DEBUG_WRAPPER=true /usr/bin/jabref
[debug] /usr/bin/jabref: Picking up the JVM designated by the
alternatives system: 
[debug] /usr/bin/jabref:   JAVA_HOME = '/usr/lib/jvm/java-11-openjdk-
amd64'
[debug] /usr/bin/jabref: Found JAVA_HOME = '/usr/lib/jvm/java-11-
openjdk-amd64'
[debug] /usr/bin/jabref: Found JAVA_CMD = '/usr/lib/jvm/java-11-
openjdk-amd64/bin/java'
[debug] /usr/bin/jabref: Environment variable CLASSPATH is ''
[debug] /usr/bin/jabref: Runnning /usr/lib/jvm/java-11-openjdk-
amd64/bin/java  -classpath
/usr/share/java/jabref.jar:/usr/share/java/bcprov.jar:/usr/share/java/a
ntlr3-runtime.jar:/usr/share/java/antlr4-
runtime.jar:/usr/share/java/com.android.json.jar:/usr/share/java/common
s-cli.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-
lang3.jar:/usr/share/java/commons-
logging.jar:/usr/share/java/fontbox.jar:/usr/share/java/glazedlists.jar
:/usr/share/java/guava.jar:/usr/share/java/httpasyncclient.jar:/usr/sha
re/java/httpclient.jar:/usr/share/java/httpcore.jar:/usr/share/java/htt
pcore-nio.jar:/usr/share/java/httpmime.jar:/usr/share/java/java-string-
similarity.jar:/usr/share/java/jaxb-
runtime.jar:/usr/share/java/jempbox.jar:/usr/share/java/jgoodies-
common.jar:/usr/share/java/jgoodies-forms.jar:/usr/share/java/jgoodies-
looks.jar:/usr/share/java/jhlabs-
filters.jar:/usr/share/java/jsoup.jar:/usr/share/java/juh.jar:/usr/shar
e/java/jurt.jar:/usr/share/java/log4j-api.jar:/usr/share/java/log4j-
core.jar:/usr/share/java/log4j-
jcl.jar:/usr/share/java/microba.jar:/usr/share/java/mariadb-java-
client.jar:/usr/share/java/pdfbox.jar:/usr/share/java/postgresql.jar:/u
sr/share/java/ridl.jar:/usr/share/java/spin.jar:/usr/share/java/swingx.
jar:/usr/share/java/swing-layout.jar:/usr/share/java/unirest-
java.jar:/usr/share/java/unoil.jar --add-
opens=java.desktop/java.awt=ALL-UNNAMED net.sf.jabref.JabRefMain
21:58:31.744 [AWT-EventQueue-0] WARN  net.sf.jabref.JabRefGUI - There
seem to be problems with OpenJDK and the default GTK Look Using
Metal L instead. Change to another L with caution.

I hope it's useful. Thank you very much.

Pep

> 
> Thank you,
> tony



Bug#1005720: mysql-8.0: FTBFS with OpenSSL 3.0

2022-02-13 Thread Sebastian Andrzej Siewior
Source: mysql-8.0
Version: 8.0.23-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
control: forwarded -1 

Your package is failing to build using OpenSSL 3.0 with the
following error:

| -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
| -- ZLIB_VERSION (system) is 1.2.11
| -- ZSTD_VERSION (system) is 1.4.8
| -- OPENSSL_INCLUDE_DIR = /usr/include
| -- OPENSSL_LIBRARY = /usr/lib/x86_64-linux-gnu/libssl.so
| -- CRYPTO_LIBRARY = /usr/lib/x86_64-linux-gnu/libcrypto.so
| -- OPENSSL_MAJOR_VERSION =
| -- OPENSSL_MINOR_VERSION =
| -- OPENSSL_FIX_VERSION =
| -- Looking for SHA512_DIGEST_LENGTH
| -- Looking for SHA512_DIGEST_LENGTH - found
| --
| Cannot find appropriate system libraries for WITH_SSL=system.
| Make sure you have specified a supported SSL version.
| Valid options are :
| system (use the OS openssl library),
| yes (synonym for system),
| 
| 
| CMake Error at cmake/ssl.cmake:61 (MESSAGE):
|   Please install the appropriate openssl developer package.
| 
| Call Stack (most recent call first):
|   cmake/ssl.cmake:315 (FATAL_SSL_NOT_FOUND_ERROR)
|   CMakeLists.txt:1378 (MYSQL_CHECK_SSL)
| 
| 
| -- Configuring incomplete, errors occurred!
| See also "/<>/builddir/CMakeFiles/CMakeOutput.log".
| See also "/<>/builddir/CMakeFiles/CMakeError.log".
| make[1]: *** [debian/rules:80: configure-stamp] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:228: build] Error 2

For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html

Sebastian



Bug#1005719: mumble: FTBFS with OpenSSL 3.0

2022-02-13 Thread Sebastian Andrzej Siewior
Source: mumble
Version: 1.3.4-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0

Your package is failing to build using OpenSSL 3.0 with the
following error:

| g++ -c -include release/mumble -pipe -g -O2 
-ffile-prefix-map=/<>/src/mumble=. -fstack-protector-strong 
-Wformat -Werror=format -security -fvisibility=hidden -Wall -Wextra 
-Wno-deprecated -g -O2 -ffile-prefix-map=/<>/qmake=. 
-fstack-protector-strong -Wfor mat -Werror=format-security -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=2 -I../mumble_proto -isystem ../mumble_proto 
-I../../3rdparty/celt-0.7.0-src /libcelt -isystem 
../../3rdparty/celt-0.7.0-src/libcelt -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werro 
r=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -pthread -Wall 
-Wextra -D_REENTRANT -fPIC -DNO_UPDATE_CHECK -DPLUGIN_PATH=/us r/lib/mumble 
-DMUMBLE_VERSION=1.3.4-1 -DHAVE_LIMITS_H -DHAVE_ENDIAN_H 
-DRESTRICT=__restrict__ -DMUMBLE_VERSION_STRING=1.3.4 -DMUMBLE -DUSE_M 
ANUAL_PLUGIN -DNO_CRASH_REPORT -DUSE_OPUS -DUSE_RNNOISE -DUSE_ALSA -DUSE_OSS 
-DUSE_PULSEAUDIO -DUSE_JACKAUDIO -DUSE_BONJOUR -DUSE_DBUS -DUSE _SPEECHD 
-DUSE_SPEECHD_PKGCONFIG -D_REENTRANT -DQT_NO_DEBUG -DQT_SVG_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_XM L_LIB 
-DQT_DBUS_LIB -DQT_CORE_LIB -I. -I../../src -I. -I../mumble_proto 
-I../../3rdparty/arc4random-src -I/usr/include/speech-dispatcher -I. 
./../3rdparty/qqbonjour-src -I../../3rdparty/smallft-src -Iwidgets 
-I../../3rdparty/celt-0.7.0-src/libcelt -I../../3rdparty/rnnoise-src/incl ude 
-I/usr/lib/oss/include -I/usr/include/opus 
-I/usr/include/avahi-compat-libdns_sd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/gli b-2.0/include 
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I 
/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtSql -I/usr/inclu 
de/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I../../release/.moc/mum ble 
-I../../release/.ui/mumble -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
../../release/.obj/mumble/FFDHE.o ../FFDHE.cpp
| ../SelfSignedCertificate.cpp: In static member function ‘static bool 
SelfSignedCertificate::generate(CertificateType, QString, QString, QSsl 
Certificate&, QSslKey&)’:
| ../SelfSignedCertificate.cpp:48:29: error: ‘CRYPTO_MEM_CHECK_ON’ was not 
declared in this scope
|48 | if (CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON) == -1) {
|   | ^~~
| g++ -c -include release/mumble -pipe -g -O2 
-ffile-prefix-map=/<>/src/mumble=. -fstack-protector-strong 
-Wformat -Werror=format -security -fvisibility=hidden -Wall -Wextra 
-Wno-deprecated -g -O2 -ffile-prefix-map=/<>/qmake=. 
-fstack-protector-strong -Wfor mat -Werror=format-security -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=2 -I../mumble_proto -isystem ../mumble_proto 
-I../../3rdparty/celt-0.7.0-src /libcelt -isystem 
../../3rdparty/celt-0.7.0-src/libcelt -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werro 
r=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -pthread -Wall 
-Wextra -D_REENTRANT -fPIC -DNO_UPDATE_CHECK -DPLUGIN_PATH=/us r/lib/mumble 
-DMUMBLE_VERSION=1.3.4-1 -DHAVE_LIMITS_H -DHAVE_ENDIAN_H 
-DRESTRICT=__restrict__ -DMUMBLE_VERSION_STRING=1.3.4 -DMUMBLE -DUSE_M 
ANUAL_PLUGIN -DNO_CRASH_REPORT -DUSE_OPUS -DUSE_RNNOISE -DUSE_ALSA -DUSE_OSS 
-DUSE_PULSEAUDIO -DUSE_JACKAUDIO -DUSE_BONJOUR -DUSE_DBUS -DUSE _SPEECHD 
-DUSE_SPEECHD_PKGCONFIG -D_REENTRANT -DQT_NO_DEBUG -DQT_SVG_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_XM L_LIB 
-DQT_DBUS_LIB -DQT_CORE_LIB -I. -I../../src -I. -I../mumble_proto 
-I../../3rdparty/arc4random-src -I/usr/include/speech-dispatcher -I. 
./../3rdparty/qqbonjour-src -I../../3rdparty/smallft-src -Iwidgets 
-I../../3rdparty/celt-0.7.0-src/libcelt -I../../3rdparty/rnnoise-src/incl ude 
-I/usr/lib/oss/include -I/usr/include/opus 
-I/usr/include/avahi-compat-libdns_sd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/gli b-2.0/include 
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I 
/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtSql -I/usr/inclu 
de/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I../../release/.moc/mum ble 
-I../../release/.ui/mumble -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
../../release/.obj/mumble/arc4random_uniform.o ../../3rd 
party/arc4random-src/arc4random_uniform.cpp
| ../SelfSignedCertificate.cpp:48:13: error: ‘CRYPTO_mem_ctrl’ was not declared 
in this scope; did you mean ‘CRYPTO_memcmp’?
|   

Bug#1005718: mosh: FTBFS with OpenSSL 3.0

2022-02-13 Thread Sebastian Andrzej Siewior
Source: mosh
Version: 1.3.2-2.1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0

Your package is failing to build using OpenSSL 3.0 with the
following error:

| c++ -DHAVE_CONFIG_H -I. -I../..  -I./../util  -Wdate-time -D_FORTIFY_SOURCE=2 
-Wall -Werror -Wextra -pedantic -Wno-long-long -Weffc++ -Wmissing-declarations 
-fno-strict-overflow -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-Wstack-protector --param ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g 
-O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -c -o 
ocb.o ocb.cc
| ocb.cc: In function ‘void AES_ecb_encrypt_blks(block*, unsigned int, 
AES_KEY*)’:
| ocb.cc:360:80: error: ‘void AES_encrypt(const unsigned char*, unsigned 
char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   360 |   AES_encrypt((unsigned char *)(blks+nblks), (unsigned char 
*)(blks+nblks), key);
|   |   
 ^
| In file included from ocb.cc:354:
| /usr/include/openssl/aes.h:57:6: note: declared here
|57 | void AES_encrypt(const unsigned char *in, unsigned char *out,
|   |  ^~~
| ocb.cc: In function ‘void AES_ecb_decrypt_blks(block*, unsigned int, 
AES_KEY*)’:
| ocb.cc:367:80: error: ‘void AES_decrypt(const unsigned char*, unsigned 
char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   367 |   AES_decrypt((unsigned char *)(blks+nblks), (unsigned char 
*)(blks+nblks), key);
|   |   
 ^
| In file included from ocb.cc:354:
| /usr/include/openssl/aes.h:60:6: note: declared here
|60 | void AES_decrypt(const unsigned char *in, unsigned char *out,
|   |  ^~~
| ocb.cc: In function ‘int ae_init(ae_ctx*, const void*, int, int, int)’:
| ocb.cc:804:75: error: ‘int AES_set_encrypt_key(const unsigned char*, int, 
AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
|   804 | AES_set_encrypt_key((unsigned char *)key, key_len*8, 
>encrypt_key);
|   |   
^
| In file included from ocb.cc:354:
| /usr/include/openssl/aes.h:51:5: note: declared here
|51 | int AES_set_encrypt_key(const unsigned char *userKey, const int bits,
|   | ^~~
| ocb.cc:808:82: error: ‘int AES_set_decrypt_key(const unsigned char*, int, 
AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
|   808 | AES_set_decrypt_key((unsigned char *)key, (int)(key_len*8), 
>decrypt_key);
|   |   
   ^
| In file included from ocb.cc:354:
| /usr/include/openssl/aes.h:54:5: note: declared here
|54 | int AES_set_decrypt_key(const unsigned char *userKey, const int bits,
|   | ^~~
| ocb.cc:817:76: error: ‘void AES_encrypt(const unsigned char*, unsigned 
char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   817 | (unsigned char *)>Lstar, 
>encrypt_key);
|   |   
 ^
| In file included from ocb.cc:354:
| /usr/include/openssl/aes.h:57:6: note: declared here
|57 | void AES_encrypt(const unsigned char *in, unsigned char *out,
|   |  ^~~
| ocb.cc: In function ‘block gen_offset_from_nonce(ae_ctx*, const void*)’:
| ocb.cc:854:72: error: ‘void AES_encrypt(const unsigned char*, unsigned 
char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|   854 |   AES_encrypt(tmp.u8, (unsigned char *)>KtopStr, 
>encrypt_key);
|   |   
 ^
| In file included from ocb.cc:354:
| /usr/include/openssl/aes.h:57:6: note: declared here
|57 | void AES_encrypt(const unsigned char *in, unsigned char *out,
|   |  ^~~
| ocb.cc: In function ‘int ae_decrypt(ae_ctx*, const void*, const void*, int, 
const void*, int, void*, const void*, int)’:
| ocb.cc:1338:68: error: ‘void AES_encrypt(const unsigned char*, unsigned 
char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|  1338 | AES_encrypt((unsigned char *), tmp.u8, >encrypt_key);
|   |^
| In file included from ocb.cc:354:
| /usr/include/openssl/aes.h:57:6: note: declared here
|57 | void AES_encrypt(const unsigned char *in, unsigned char *out,
|   |  ^~~
| ocb.cc:1376:48: error: ‘void AES_encrypt(const unsigned char*, unsigned 
char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 
[-Werror=deprecated-declarations]
|  1376 |   AES_encrypt(tmp.u8, 

Bug#1005499: openscad: FTBFS: src/cgalutils-tess.cc:22:15: error: ‘Triangulation_2_filtered_projection_traits_3’ in namespace ‘CGAL’ does not name a template type; did you mean ‘Triangulation_2_projec

2022-02-13 Thread Torsten Paul

Caused by file and class rename in CGAL 5.4.

Fix:
https://github.com/openscad/openscad/commit/71f2831c0484c3f35cbf44e1d1dc2c857384100b

ciao,
  Torsten.



Bug#1005717: : FTBFS with OpenSSL 3.0

2022-02-13 Thread Sebastian Andrzej Siewior


Source: nzbget
Version: 21.0+dfsg-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0

Your package is failing to build using OpenSSL 3.0 with the
following error:

| daemon/connect/TlsSocket.cpp: In static member function ‘static void 
TlsSocket::Final()’:
| daemon/connect/TlsSocket.cpp:192:9: error: ‘FIPS_mode_set’ was not declared 
in this scope
|   192 | FIPS_mode_set(0);
|   | ^
| daemon/connect/TlsSocket.cpp: In member function ‘bool TlsSocket::Start()’:
| daemon/connect/TlsSocket.cpp:392:56: warning: ‘EC_KEY* 
EC_KEY_new_by_curve_name(int)’ is deprecated: Since OpenSSL 3.0 
[-Wdeprecated-declara tions]
|   392 | EC_KEY* ecdh = 
EC_KEY_new_by_curve_name(NID_X9_62_prime256v1);
|   |
^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:996:31: note: declared here
|   996 | OSSL_DEPRECATEDIN_3_0 EC_KEY *EC_KEY_new_by_curve_name(int nid);
|   |   ^~~~
| daemon/connect/TlsSocket.cpp:402:36: warning: ‘void EC_KEY_free(EC_KEY*)’ is 
deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
|   402 | EC_KEY_free(ecdh);
|   | ~~~^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:1001:28: note: declared here
|  1001 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
|   |^~~
| daemon/connect/TlsSocket.cpp:406:28: warning: ‘void EC_KEY_free(EC_KEY*)’ is 
deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
|   406 | EC_KEY_free(ecdh);
|   | ~~~^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:1001:28: note: declared here
|  1001 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
|   |^~~
| daemon/connect/Connection.cpp: In function ‘hostent* 
android_read_hostent(FILE*, hostent*, char*, size_t)’:
| daemon/connect/Connection.cpp:1196:22: warning: ignoring return value of 
‘size_t fread(void*, size_t, size_t, FILE*)’ declared with attribut e 
‘warn_unused_result’ [-Wunused-result]
|  1196 | fread(, 1, sizeof(size), proxy);
|   | ~^~~
| make[2]: *** [Makefile:1774: daemon/connect/TlsSocket.o] Error 1

For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html

Sebastian



Bug#1005716: ntpsec: FTBFS with OpenSSL 3.0

2022-02-13 Thread Sebastian Andrzej Siewior
Source: ntpsec
Version: 1.2.1+dfsg1-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0

| Your package is failing to build using OpenSSL 3.0 with the
| following error:
| 
| ../../attic/cmac-timing.c: In function ‘One_EVP_MAC’:
| ../../attic/cmac-timing.c:249:18: error: too few arguments to function 
‘EVP_MAC_init’
|   249 | if (0 == EVP_MAC_init(ctx)) {
|   |  ^~~~
| In file included from /usr/include/openssl/cmac.h:25,
|  from ../../attic/cmac-timing.c:29:
| /usr/include/openssl/evp.h:1220:5: note: declared here
|  1220 | int EVP_MAC_init(EVP_MAC_CTX *ctx, const unsigned char *key, size_t 
keylen,
|   | ^~~~
| ../../attic/cmac-timing.c: In function ‘One_EVP_MAC2’:
| ../../attic/cmac-timing.c:310:18: error: too few arguments to function 
‘EVP_MAC_init’
|   310 | if (0 == EVP_MAC_init(ctx)) {
|   |  ^~~~
| In file included from /usr/include/openssl/cmac.h:25,
|  from ../../attic/cmac-timing.c:29:
| /usr/include/openssl/evp.h:1220:5: note: declared here
|  1220 | int EVP_MAC_init(EVP_MAC_CTX *ctx, const unsigned char *key, size_t 
keylen,
|   | ^~~~
| 
| Waf: Leaving directory `/<>/build/main'
| Build failed

For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html

Sebastian



Bug#1005344: Update falkon to new upstream version 3.2

2022-02-13 Thread Georges Khaznadar
Dear Praveen,

thank you for your work! I could enjoy the enhancements you made for the
debian packaging.

I uploaded the package to debian a few minutes before.

Would you like to be a regular uploader for this package? Or do you
think that this package should be part of some team maintenance?

Best regards,   Georges.

Pirate Praveen a écrit :
> On Fri, 11 Feb 2022 23:40:23 +0530 Pirate Praveen 
> wrote:
> > Please update to 3.2. I'd be happy to help with the update as well.
> 
> I have prepared an update at https://salsa.debian.org/praveen/falkon feel
> free to pull.

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature


Bug#1005060: transition: ace

2022-02-13 Thread Sebastian Ramacher
Control: tags -1 confirmed

On 2022-02-13 18:52:08 +, Sudip Mukherjee wrote:
> Hi,
> 
> Just to add here, diagnostics FTBFS has been fixed and I have verified
> that it builds fine with ace 7.0.6+dfsg-1 version in experimental.

Please go ahead

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#1005715: dahdi-linux: autopkgtest suggests breakage due to new linux kernel

2022-02-13 Thread Paul Gevers
Source: dahdi-linux
Version: 1:2.11.1.0.20170917~dfsg-7.4
Severity: serious
Tags: sid bookworm

Dear maintainer,

The latest src:linux upload to unstable caused the autopkgtest of
dahdi-linux to fail. The test was added "to tell us if the modules are
broken by newer kernel versions". So, that's probably the case.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dahdi-linux/19188684/log.gz

Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-7.4) ...
Loading new dahdi-2.11.1.0.20170917~dfsg-7.4 DKMS files...
It is likely that 4.19.0-18-amd64 belongs to a chroot's host
Building for 5.16.0-1-amd64
Building initial module for 5.16.0-1-amd64
Error! Bad return status for module build on kernel: 5.16.0-1-amd64 (x86_64)
Consult /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.4/build/make.log for more 
information.
dpkg: error processing package dahdi-dkms (--configure):
 installed dahdi-dkms package post-installation script subprocess returned 
error exit status 10


https://ci.debian.net/data/autopkgtest/testing/i386/d/dahdi-linux/19177982/log.gz

Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-7.4) ...
Loading new dahdi-2.11.1.0.20170917~dfsg-7.4 DKMS files...
It is likely that 5.10.0-11-cloud-amd64 belongs to a chroot's host
Building for 5.16.0-1-686-pae
Building initial module for 5.16.0-1-686-pae
Error! Bad return status for module build on kernel: 5.16.0-1-686-pae (i686)
Consult /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.4/build/make.log for more 
information.
dpkg: error processing package dahdi-dkms (--configure):
 installed dahdi-dkms package post-installation script subprocess returned 
error exit status 10



Bug#1005714: RFS: analog/2:6.0-23 [QA] -- web server log analyzer

2022-02-13 Thread Lourisvaldo Figueredo Junior
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "analog":

 * Package name: analog
   Version : 2:6.0-23
   Upstream Author : [fill in name and email of upstream]
 * URL : http://www.analog.cx/
 * License : GD, BSD-4-clause, zlib, libpng, PCRE, GPL-2+, public-
domain
 * Vcs : https://salsa.debian.org/debian/analog
   Section : web

It builds those binary packages:

  analog - web server log analyzer

To access further information about this package, please visit the following 
URL:

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

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/a/analog/
analog_6.0-23.dsc

Changes since the last upload:

 analog (2:6.0-23) unstable; urgency=medium
 .
   * QA upload.
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped to 13.
   * debian/control:
   - Added 'Rules-Requires-Root: no' to source stanza.
   - Updated Vcs-* fields.
   - Bumped Standards-Version to 4.6.0.1.
   * debian/copyright:
   - Migrated to 1.0 format.
   - Updated all data.
   * debian/rules:
   - Removed 'export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed'
 line. No longer needed.
   * debian/salsa-ci.yml: created.
   * debian/tests/control: created to perform trivial CI tests. (LP: #1677701)
   * Fix FTCBFS: Pass cross compiler to Makefile. Thank you Helmut Grohne
 . (Closes: #812231)

The git repository is on my salsa account [1]. Please, import this to debian 
repository [2].
Any tips or suggestions given will be welcome.

Regards,
-- 
  Lourisvaldo Figueredo Junior

[1] https://salsa.debian.org/figueredo/analog
[2] https://salsa.debian.org/debian/analog


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


Bug#1005713: tensorflow FTBFS; bazel still tries to download during build.

2022-02-13 Thread M. Zhou
Source: tensorflow
Version: 2.3.1-1
Severity: serious
Justification: FTBFS; Bazel tries to download during build.

Building tensorflow locally with sbuild results in errors like the follows

ERROR:
/<>/tensorflow/compiler/mlir/tensorflow/BUILD:1249:11:
//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_p
asses depends on @llvm-project//mli
r:Parser in repository @llvm-project which failed to fetch. no such
package '@llvm-project//mlir': java.io.IOException: Error downloading
[https://storage.googleapis.com/mirror.tens
orflow.org/github.com/llvm/llvm-
project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz,
https://github.com/llvm/llvm-project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a
9.tar.gz] to
/tmp/.cache/bazel/_bazel_lumin/30c7b4fa2330f0b3b6e67535723f3f22/externa
l/llvm-project/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz: connect
timed out
ERROR:
/<>/tensorflow/compiler/mlir/tensorflow/BUILD:1249:11:
//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_p
asses depends on @llvm-project//mli
r:Pass in repository @llvm-project which failed to fetch. no such
package '@llvm-project//mlir': java.io.IOException: Error downloading
[https://storage.googleapis.com/mirror.tensor
flow.org/github.com/llvm/llvm-
project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz,
https://github.com/llvm/llvm-project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9
.
tar.gz] to
/tmp/.cache/bazel/_bazel_lumin/30c7b4fa2330f0b3b6e67535723f3f22/externa
l/llvm-project/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz: connect
timed out  
ERROR:
/<>/tensorflow/compiler/mlir/tensorflow/BUILD:1249:11:
//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_p
asses depends on @llvm-project//mli
r:Shape in repository @llvm-project which failed to fetch. no such
package '@llvm-project//mlir': java.io.IOException: Error downloading
[https://storage.googleapis.com/mirror.tenso
rflow.org/github.com/llvm/llvm-
project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz,
https://github.com/llvm/llvm-project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9
.tar.gz] to
/tmp/.cache/bazel/_bazel_lumin/30c7b4fa2330f0b3b6e67535723f3f22/externa
l/llvm-project/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz: connect
timed out 
ERROR:
/<>/tensorflow/compiler/mlir/tensorflow/BUILD:1249:11:
//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_p
asses depends on @llvm-project//mli
r:StandardOps in repository @llvm-project which failed to fetch. no
such package '@llvm-project//mlir': java.io.IOException: Error
downloading [https://storage.googleapis.com/mirror
.tensorflow.org/github.com/llvm/llvm-
project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz,
https://github.com/llvm/llvm-project/archive/7e825abd5704ce28b166f9463d4bd30434
8fd2a9.tar.gz] to
/tmp/.cache/bazel/_bazel_lumin/30c7b4fa2330f0b3b6e67535723f3f22/externa
l/llvm-project/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz: connect
timed out   
ERROR:
/<>/tensorflow/compiler/mlir/tensorflow/BUILD:1249:11:
//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_p
asses depends on @llvm-project//mli
r:TransformUtils in repository @llvm-project which failed to fetch. no
such package '@llvm-project//mlir': java.io.IOException: Error
downloading [https://storage.googleapis.com/mir
ror.tensorflow.org/github.com/llvm/llvm-
project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz,
https://github.com/llvm/llvm-project/archive/7e825abd5704ce28b166f9463d4bd30
4348fd2a9.tar.gz] to
/tmp/.cache/bazel/_bazel_lumin/30c7b4fa2330f0b3b6e67535723f3f22/externa
l/llvm-project/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz: connect
timed out
ERROR:
/<>/tensorflow/compiler/mlir/tensorflow/BUILD:1249:11:
//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_p
asses depends on @llvm-project//mli
r:Transforms in repository @llvm-project which failed to fetch. no such
package '@llvm-project//mlir': java.io.IOException: Error downloading
[https://storage.googleapis.com/mirror.
tensorflow.org/github.com/llvm/llvm-
project/archive/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz,
https://github.com/llvm/llvm-project/archive/7e825abd5704ce28b166f9463d4bd304348
fd2a9.tar.gz] to
/tmp/.cache/bazel/_bazel_lumin/30c7b4fa2330f0b3b6e67535723f3f22/externa
l/llvm-project/7e825abd5704ce28b166f9463d4bd304348fd2a9.tar.gz: connect
timed out
WARNING: errors encountered while analyzing target
'//tensorflow:tensorflow_cc': it will not be built
INFO: Analyzed target //tensorflow:tensorflow_cc (186 packages loaded,
10010 targets configured). 



Bug#1005712: hackrf_info prints "unknown" for version info

2022-02-13 Thread Eric Cooper
Package: hackrf
Version: 2021.03.1-2
Severity: normal

$ hackrf_info
hackrf_info version: unknown
libhackrf version: unknown (0.6)
Found HackRF
Index: 0
Serial number: 
Board ID Number: 2 (HackRF One)
Firmware Version: 2021.03.1 (API:1.04)
Part ID Number: 

It looks like this definition in host/cmake/set_release.cmake
set(RELEASE "2021.03.1")
is not being used when hackrf_info gets built.

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_WARN
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 hackrf depends on:
ii  libc6 2.33-5
ii  libfftw3-single3  3.3.8-2
ii  libhackrf02021.03.1-2

hackrf recommends no packages.

hackrf suggests no packages.

-- no debconf information



Bug#1005410: chromium: debug trap warning on browser start up

2022-02-13 Thread 10dmar10
Strange, with installed debug packages still no symbols:

#  aptitude search chromium

i   chromium - Webbrowser
p   chromium-bsu - Schneller, scrollender
Space Shooter im Arkadestil
p   chromium-bsu-data- data pack for the
Chromium B.S.U. game
p   chromium-bsu-dbgsym  - debug symbols for
chromium-bsu
i A chromium-common  - Webbrowser - gemeinsam
genutzte Ressourcen der Chro
i   chromium-common-dbgsym   - debug symbols for
chromium-common
i   chromium-dbgsym  - debug symbols for
chromium
p   chromium-driver  - Webbrowser -
WebDriver-Unterstützung
i   chromium-l10n- Webbrowser -
Sprachpakete
p   chromium-lwn4chrome  - Chromium-Erweiterung,
um LWN.net etwas einfacher zu
i   chromium-sandbox - Webbrowser - isolierter
»setuid«-Bereich (sandbox)
i   chromium-sandbox-dbgsym  - debug symbols for
chromium-sandbox
p   chromium-shell   - Webbrowser - minimale
Shell
p   chromium-shell-dbgsym- debug symbols for
chromium-shell
p   chromium-tt-rss-notifier - Chromium extension
providing toolbar button for TT-
p   node-electron-to-chromium- Provides a list of
electron-to-chromium version map
p   webext-ublock-origin-chromium- lightweight and
efficient ads, malware, trackers bl

# dmesg

[ 1682.348101] traps: chromium[4648] trap int3 ip:56195612fdd5
sp:7fff9fc7a7a0 error:0 in chromium[561952947000+8cda000]

# console

Crashing due to FD ownership violation:
#0 0x561956081da3 
#1 0x56195612fdcc 
#2 0x56195612fca0 
#3 0x561957f69b7c 
#4 0x561957f52792 
#5 0x561952948593 
#6 0x561955c132ac 
#7 0x561955c10e56 
#8 0x561955c116c4 
#9 0x56195294785b 
#10 0x7fc755bd57ed 
[4638:4638:0213/200619.575506:ERROR:gpu_init.cc(454)] Passthrough is
not supported, GL is desktop, ANGLE is
[4638:4638:0213/200619.609723:ERROR:sandbox_linux.cc(377)]
InitializeSandbox() called with multiple threads in process
gpu-process.
[4591:4762:0213/200621.829741:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END:
message, this is crbug.com/1216328.
[4591:4762:0213/200621.829771:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
Fontconfig error: Cannot load default config file
[4641:4:0213/200945.702572:ERROR:node_controller.cc(585)] Trying to
re-add dropped peer 17FB739E011C04B4.EB47E6C9783C



Bug#1004710: Invoke "useradd -r" when creating a system user

2022-02-13 Thread Jason Franklin
On Sun, 2022-02-13 at 19:18 +0100, Marc Haber wrote:
> On Sun, Feb 13, 2022 at 12:27:26PM -0500, Jason Franklin wrote:
> > That warning is not emitted here when "-r" is added to the call made
> > from within adduser. The range discrepancy needs to be sorted out with
> > discussion, I think.
> 
> Policy also helps here, it's rather explicit in defining the uid ranges.
> Are we in line with policy?

Adduser is in line with policy for the moment. Improvements can be made
in this regard.

For example, some UIDs are explicitly forbidden by policy, but adduser
and useradd allow them.  These should be blocked, and tests should be
written to prove this.

> Useradd is more and more taking over functionality that has
> traditionally been implemented in adduser. Maybe they're working towards
> adduser just being a shim for backwards compatibility. Do you want me to
> reach out to them?

Please do.

I am actually a bit worried that my work is in vain. The useradd utility
does have quite a few features that clash with or overtake those
previously offered by adduser.

If useradd is intended to replace adduser, I would like to know as most
of my work would be lessened in importance.

The questions is: Can adduser offer features that admins want and that
useradd lacks?

I think the answer to the above question is "yes", but we need to make
sure we know what these additional features are.  :/

I'm a bit uncertain as to where I stand in this regard.

Thanks,

-- 
Jason Franklin



Bug#992699: debian-installer: Firmwares required for some sound cards

2022-02-13 Thread Cyril Brulebois
Hi,

Samuel Thibault  (2022-02-13):
> Cyril, could you try on the actual hardware the resulting image:
> https://people.debian.org/~sthibault/tmp/debian-sid-amd64-NETINST-1.iso

Please don't block on me, I'm *very* low on free time, and I don't see
that improving until March or so.


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


signature.asc
Description: PGP signature


Bug#1005410: chromium: debug trap warning on browser start up

2022-02-13 Thread Andres Salomon



On 2/13/22 13:56, 10dmar10 wrote:

Hm, that's new.  What does that backtrace look like if you install the 
chromium-dbgsym package?

There is no such package available in testing...



Oh, you have to add the debug repository to apt (replacing "unstable" 
with testing or whatever you're using):


deb http://deb.debian.org/debian-debug/ unstable-debug main



Bug#1005060: transition: ace

2022-02-13 Thread Sudip Mukherjee
Hi,

Just to add here, diagnostics FTBFS has been fixed and I have verified
that it builds fine with ace 7.0.6+dfsg-1 version in experimental.

-- 
Regards
Sudip



Bug#992699: debian-installer: Firmwares required for some sound cards

2022-02-13 Thread Samuel Thibault
Control: reassign -1 debian-cd

Hello,

Cyril Brulebois, le dim. 22 août 2021 16:02:20 +0200, a ecrit:
> Samuel Thibault  (2021-08-22):
> > As mentioned in the Bullseye errata, there seems to be a number of
> > sound cards that require loading a firmware to be able to emit sound
> > (e.g. Intel SOF). Unfortunately currently the installer loads firmware
> > after loading the ISO image, while speech synthesis is needed at the
> > very first interaction with the user, which is usually before that. We'd
> > thus want (for the firmware-enabled image) to include firmware in the
> > initrd somehow.
> 
> For context, that's sof I was fighting with:
>   
> https://tracker.debian.org/news/1245087/accepted-hw-detect-1147-source-into-unstable/
> 
> > We discussed a bit on IRC, possibly we could just, at debian-cd step,
> > catenate the cpio archives, or unpack/assemble/repack, or ship several
> > initrds.
> 
> And once booted on my sof-enabled laptop, it starts speaking, so I
> suppose that's a successful PoC; next step is to confirm whether
> tweaking debian-cd to do the cat dance looks good to Steve as well.

I had a try at adding support to debian-cd, I can up with this:
https://salsa.debian.org/images-team/debian-cd/-/merge_requests/23

It actually follows the debian-edu way which uses cpio -oA to append
content. That makes it simpler for anybody who would be trying to gunzip
the initrd.gz

Cyril, could you try on the actual hardware the resulting image:
https://people.debian.org/~sthibault/tmp/debian-sid-amd64-NETINST-1.iso

debian-cd people, could you have a look?

It would be also very worth applying to the bullseye images.

Samuel



Bug#1005651: lbreakouthd: should depend on lbreakouthd-data

2022-02-13 Thread Brian Vaughan

Yes, it's a dependency.

I tried first installing both packages, and the game worked fine. Then I 
purged both, then installed only lbreakouthd and not lbreakouthd-data. 
From the application menu, LBreakoutHD silently failed to launch. From 
the command line, it failed on trying to read a directory installed with 
lbreakouthd-data:


$ lbreakouthd
lbreakouthd 1.0.8
Copyright 2018-2021 Michael Speck
Published under GNU GPL
---
Loading configuration /home/brian/.lbreakouthd/lbreakouthd.conf
Loading hiscores /var/games/lbreakouthd.hscr
Initializing SDL
Mixer opened (16 channels, 1024 buf size)
ERROR: tools.cpp:181: readDir(): Could not open 
/usr/share/games/lbreakouthd/themes

No game controller found...
Segmentation fault
[139]

Also, the description says that lbreakouthd supports all LBreakout2 
themes and level sets, so perhaps lbreakout2-data should be a suggested 
package.




Bug#1005711: ITP: lambdaisland-uri-clojure -- pure Clojure URI library

2022-02-13 Thread Louis-Philippe Véronneau
Package: wnpp
Severity: wishlist
Owner: Louis-Philippe Véronneau 

Package name: lambdaisland-uri-clojure
Version : 1.13.95
URL : https://github.com/lambdaisland/uri
License : MPL-2.0
Programming Lang: Clojure
Description : pure Clojure URI library

lambdaisland-uri-clojure provides a pure Clojure URI library. It is a
modern replacement for the now unmaintained url-clojure.

I'm planning to maintain this package in the Clojure Team.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature


Bug#906259: ITP: smartparens -- auto insertion, wrapping, and navigation of ()s, delimiters, and tags for Emacs

2022-02-13 Thread Nicholas D Steeves
Control: RFP: smartparens -- auto insertion, wrapping, and navigation of  ()s, 
delimiters, and tags for Emacs
Control: noowner -1

Elpa-scala-mode clears the path, but this ITP is still blocked by Auctex
#921328, and I've lost the motivation to resolve that.  There are also a
couple of other failing tests that I haven't been able to resolve.
Thus, I offer up my work to whoever would like to carry the baton to the
finish line.  Here's what I have so far:

  https://salsa.debian.org/sten/smartparens

Oh, and the upstream git snapshot tag was created by me.  The format is
similar to git-describe, eg: 1.11.0+180.g911cc89
$upstream_stable_version + $commits_since_stable_version . g $short_hash

It's a cool package that I'd love to see in Debian :-)

Regards,
Nicholas



Bug#1004710: Invoke "useradd -r" when creating a system user

2022-02-13 Thread Marc Haber
On Sun, Feb 13, 2022 at 12:27:26PM -0500, Jason Franklin wrote:
> That warning is not emitted here when "-r" is added to the call made
> from within adduser. The range discrepancy needs to be sorted out with
> discussion, I think.

Policy also helps here, it's rather explicit in defining the uid ranges.
Are we in line with policy?

Useradd is more and more taking over functionality that has
traditionally been implemented in adduser. Maybe they're working towards
adduser just being a shim for backwards compatibility. Do you want me to
reach out to them?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421



Bug#906259: RFA: mutt-alias-el -- Emacs package to lookup and insert expanded Mutt mail aliases

2022-02-13 Thread Nicholas D Steeves
control: retitle -1 RFA: mutt-alias-el -- Emacs package to lookup and insert 
expanded Mutt mail aliases

Odd, reportbug didn't fill out the template for this one

Package: elpa-mutt-alias
  Mutt-alias is an Emacs package that allows one to lookup Mutt aliases
  and insert the expanded alias as an email address.  The following
  functions are available:
* mutt-alias-insert - Insert the expanded alias into the current buffer.
* mutt-alias-lookup - Lookup and display the expansion for alias.

P.S. the package is in good condition.


signature.asc
Description: PGP signature


Bug#1005503: [Help] Re: Bug#1005503: cdkr: FTBFS: [javac] /<>/rcdkjar/src/org/guha/rcdk/util/Misc.java:14: error: package org.openscience.cdk.inchi does not exist

2022-02-13 Thread Andreas Tille
Control: tags -1 help

Hi CDK uploaders,

I noticed that a new version (2.7.1) of cdk was uploaded which is
possibly responsible for the issue reported below.  Before I'll contact
cdkr authors I want to make sure that its not a Debian packaging issue
which is causing the problem below.

Kind regards

 Andreas.

Am Sun, Feb 13, 2022 at 08:00:22AM +0100 schrieb Lucas Nussbaum:
> Source: cdkr
> Version: 3.6.0+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220212 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > ant -buildfile rcdkjar/build.xml
> > Buildfile: /<>/rcdkjar/build.xml
> > 
> > compile:
> > [mkdir] Created dir: /<>/rcdkjar/classes
> > [javac] Compiling 18 source files to /<>/rcdkjar/classes
> > [javac] warning: [options] bootstrap class path not set in conjunction 
> > with -source 8
> > [javac] /<>/rcdkjar/src/org/guha/rcdk/util/Misc.java:14: 
> > error: package org.openscience.cdk.inchi does not exist
> > [javac] import org.openscience.cdk.inchi.InChIGenerator;
> > [javac] ^
> > [javac] /<>/rcdkjar/src/org/guha/rcdk/util/Misc.java:15: 
> > error: package org.openscience.cdk.inchi does not exist
> > [javac] import org.openscience.cdk.inchi.InChIGeneratorFactory;
> > [javac] ^
> > [javac] Note: Some input files use or override a deprecated API.
> > [javac] Note: Recompile with -Xlint:deprecation for details.
> > [javac] 2 errors
> > [javac] 1 warning
> > 
> > BUILD FAILED
> > /<>/rcdkjar/build.xml:26: Compile failed; see the compiler 
> > error output for details.
> > 
> > Total time: 1 second
> > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
> 
> 
> The full build log is available from:
> http://qa-logs.debian.net/2022/02/12/cdkr_3.6.0+dfsg-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> If you reassign this bug to another package, please marking it as 
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
> 
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.
> 
> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
> 

-- 
http://fam-tille.de



Bug#1005710: RM: elastix [i386] -- ROM; No longer targets i386

2022-02-13 Thread Steve M. Robbins
Package: ftp.debian.org
Severity: normal

The ITK v5 package only builds for amd64, so the elastix i386 binaries need 
removing to allow it to get to testing.
At least that's how I understand the excuse output
https://qa.debian.org/excuses.php?package=elastix

Thanks,
-Steve



Bug#1005311:

2022-02-13 Thread Magnus Ekdahl
Thanks Dan,

$apt download xserver-xorg-video-nvidia nvidia-driver
$sudo dpkg -i --force-depends nvidia-driver*.deb
$sudo dpkg -i --force-depends xserver-xorg-video-nvidia*.deb

is indeed a workaround.

kind regards
Magnus


Den sön 13 feb. 2022 kl 15:54 skrev Dan Chokola :

> > This has been open for almost 2 days now. Is there a workaround for this 
> > bug?
>
> I used `dpkg --force-depends ...` to install the nvidia packages I needed
> alongside the current version of Xorg and all has been working fine for the
> past few days. If there is a difference in the ABI, it hasn't caused me any
> trouble yet.
>
> --
> Dan Chokola
>


-- 
Magnus Ekdahl


Bug#982055: dia Debian package and bug #982055

2022-02-13 Thread Philippe SWARTVAGHER

Hello,

Thank you Nicolas for the set of patches, I applied (and understood!)
them. Indeed, they reduce the number of Lintian warnings :)

Le 15/01/2022 à 19:01, François Mazen a écrit :

By the way, do you use a VCS where we could get the WIP package and
eventually contribute? Salsa [1] is usually the way to go.


I created a repository on Salsa: https://salsa.debian.org/phsw/dia.

I made some trivial changes on top of Debian package currently in the
archive. Next steps will be to update the package to use the more recent
upstream code and continue some housekeeping tasks, such as ones
reported on https://tracker.debian.org/pkg/dia. And then I will be able
to start looking for a sponsor! :)

Philippe.



Bug#895440: jabref: The problem continues in Debian 11 bullseye

2022-02-13 Thread tony mancill
Hello Pep,

On Sat, Feb 12, 2022 at 09:47:41AM +0100, Pep Roca wrote:
> Package: jabref
> Version: 3.8.2+ds-15
> Followup-For: Bug #895440
> X-Debbugs-Cc: pep.r...@gmail.com
> 
> I have problems to connect JabRef and LibreOffice in the jabref bullseye 
> version.
> 
> I do manual connection and I get the error:
> 
> “File not found: 
> /usr/lib/libreoffice/program/classes/program/classes/unoil.jar”

Can you please provide the output from the program start to the time
when you attempt the connection and it fails?

DEBUG_WRAPPER=true /usr/bin/jabref

Thank you,
tony


signature.asc
Description: PGP signature


Bug#1005709: RFA: muttrc-mode-el -- Emacs major mode for editing muttrc

2022-02-13 Thread Nicholas D Steeves
Package: wnpp
Severity: normal
X-Debbugs-Cc: Debian Emacsen team 
Control: affects -1 src:muttrc-mode-el

I request an adopter for the muttrc-mode-el package, because I no
longer use it, and because a newcomer may be inspired to maintain a
high popcon package.  The package is in good condition.

The package description is:
 This mode provides syntax highlighting for muttrc and /etc/aliases.
 Basic fontification (via font-lock) appears on strings, comments,
 command names, and variables.  Additional fontification for commands
 arguments can be enabled through the customisation buffer.

Regards,
Nicholas



Bug#1005708: RFA: mutt-alias-el

2022-02-13 Thread Nicholas D Steeves
Package: wnpp
Severity: normal
X-Debbugs-Cc: Debian Emacsen team 
Control: affects -1 src:mutt-alias-el

Hi,

I'm offering this package up for adoption because I no longer use it,
and because a newcomer may be inspired to maintain a high popcon
package.

Regards,
Nicholas



Bug#1005707: ITP: pyqt6-sip -- runtime module for Python extensions using SIP

2022-02-13 Thread Dmitry Shachnev
Package: wnpp
Severity: wishlist
Owner: Dmitry Shachnev 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: pyqt6-sip
  Version : 13.2.1
  Upstream Author : Riverbank Computing Limited 
* URL : https://pypi.org/project/PyQt6-sip/
* License : SIP or GPL-2 or GPL-3
  Programming Lang: C, C++, Python
  Description : runtime module for Python extensions using SIP

SIP is a collection of tools that makes it very easy to create Python bindings
for C and C++ libraries.

PyQt6.sip is a runtime module, it is used by PyQt6 and other Python extension
modules built with SIP.

I am going to maintain it in the Debian Python Team:
https://salsa.debian.org/python-team/packages/pyqt6-sip/

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Bug#1004710: Invoke "useradd -r" when creating a system user

2022-02-13 Thread Jason Franklin
On Sun, 2022-02-13 at 18:14 +0100, Marc Haber wrote:
> Should useradd emit a warning in this case? I mean, we WANT the low UID
> in this case. Is it inside the limits of a low-level tool to impose its
> own standards on the system or is this possible a bug in useradd?

As part of this bug, we will need to have a conversation with the
"login" maintainers about how these ranges are to be configured.

Currently, useradd has its own range settings in /etc/login.defs, and
adduser has its own in /etc/adduser.conf. adduser can be written to
ignore the former completely in its useradd invocation.

However, having such a setting in two places may be a bit confusing.

That warning is not emitted here when "-r" is added to the call made
from within adduser. The range discrepancy needs to be sorted out with
discussion, I think.

-- 
Jason Franklin



Bug#1005410: chromium: debug trap warning on browser start up

2022-02-13 Thread Andres Salomon

On Sat, 12 Feb 2022 23:30:48 +0100 10dmar10 <10dma...@gmail.com> wrote:
> Package: chromium
> Version: 98.0.4758.80-1
> Severity: minor
>
> Hi,
>
> since upgrading chromium to 97.0.4692.99-1 (and still present in 
98.0.4758.80-1)

> I noticed some debug breakpoint warnings in the system log.
> The messages appear on browser start only.
> There were no observable negative effects from this,
> but it might indicate some underlying problem.
> Therefore submitting this a minor bug :)
>
> # dmesg warnings:
>
> [ 79.283808] traps: chromium[1562] trap int3 ip:562e7ff40dd5 
sp:7ffcc1defc20 error:0 in chromium[562e7c758000+8cda000]
> [ 120.618070] traps: chromium[1792] trap int3 ip:558ebb322dd5 
sp:7ffe11bda1b0 error:0 in chromium[558eb7b3a000+8cda000]

>
> # startiung chromium from command line shows following messages:
>
> Crashing due to FD ownership violation:
> #0 0x557aafdbada3
> #1 0x557aafe68dcc
> #2 0x557aafe68ca0
> #3 0x557ab1ca2b7c
> #4 0x557ab1c8b792
> #5 0x557aac681593
> #6 0x557aaf94c2ac
> #7 0x557aaf949e56
> #8 0x557aaf94a6c4
> #9 0x557aac68085b
> #10 0x7fd901f687ed
> [2098:2098:0212/223606.273686:ERROR:gpu_init.cc(454)] Passthrough is 
not supported, GL is desktop, ANGLE is
> [2098:2098:0212/223606.295130:ERROR:sandbox_linux.cc(377)] 
InitializeSandbox() called with multiple threads in process gpu-process.
> 
[2051:2083:0212/223608.652561:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] 
START: ReportBluetoothAvailability(). If you don't see the END: message, 
this is crbug.com/1216328.
> 
[2051:2083:0212/223608.652593:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] 
END: ReportBluetoothAvailability()

>

>


Hm, that's new.  What does that backtrace look like if you install the 
chromium-dbgsym package?




Bug#1005706: sunpy: FTBFS when built with DEB_BUILD_OPTIONS=nocheck

2022-02-13 Thread Graham Inggs
Source: sunpy
Version: 3.1.3-1
Severity: important
Tags: ftbfs

Hi Maintainer

Sunpy FTBFS when built with DEB_BUILD_OPTIONS=nocheck due to missing files.

chmod a-x 
debian/python*-sunpy/usr/lib/python*/dist-packages/sunpy/data/test/*.fts
chmod: cannot access
'debian/python*-sunpy/usr/lib/python*/dist-packages/sunpy/data/test/*.fts':
No such file or directory

Regards
Graham



Bug#984114: liblastfm: diff for NMU version 1.0.9-1.2

2022-02-13 Thread Florian Ernst
Hello Stefan,

On Sun, Feb 13, 2022 at 11:30:07AM +, Stefan Ahlers wrote:
> I apologize for the very long delay. Thank you for preparing an NMU. Due to
> my private situation I'm unable to continue maintaining this package.
> Therefore, where is no reason to delay the upload any longer.

Thanks for the feedback! I have thus just rescheduled the upload from
DELAYED/7 to DELAYED/0.

Also thank you for your contributions, and all the best from my side.
I see that you have orphaned your remaining packages, and I'm sorry to
see you go.  Perhaps some other time again ...

Cheers,
Flo


signature.asc
Description: PGP signature


Bug#1004999: atftp 0.7.git20120829-3.3+deb11u2 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1004999 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: atftp
Version: 0.7.git20120829-3.3+deb11u2

Explanation: fix information leak issue [CVE-2021-46671]



Bug#1004966: dpdk 20.11.4-2~deb11u1 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1004966 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: dpdk
Version: 20.11.4-2~deb11u1

Explanation: new upstream stable release



Bug#1004895: e2guardian 5.3.4-1+deb11u1 flagged for acceptance

2022-02-13 Thread Adam D Barratt
package release.debian.org
tags 1004895 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: e2guardian
Version: 5.3.4-1+deb11u1

Explanation: fix missing SSL certificate validation  issue [CVE-2021-44273]



Bug#1004710: Invoke "useradd -r" when creating a system user

2022-02-13 Thread Marc Haber
On Sun, Feb 13, 2022 at 12:09:44PM -0500, Jason Franklin wrote:
> I also came across this warning when investigating this bug.
> 
> When I get this bug fixed, the warning will go away.

Should useradd emit a warning in this case? I mean, we WANT the low UID
in this case. Is it inside the limits of a low-level tool to impose its
own standards on the system or is this possible a bug in useradd?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421



Bug#1004710: Invoke "useradd -r" when creating a system user

2022-02-13 Thread Jason Franklin
On Sun, 2022-02-13 at 16:04 +0100, Ricardo Fraile wrote:
> Adding _tuptime user...
> useradd warning: _tuptime's uid 106 outside of the UID_MIN 1000 and UID_MAX 
> 6 range.
> Created symlink /etc/systemd/system/multi-user.target.wants/tuptime.service → 
> /lib/systemd/system/tuptime.service.
> Processing triggers for man-db (2.10.0-2) ...
> 
>* What outcome did you expect instead?
> Install the package without "useradd warning" prompt.

Ricardo:

I also came across this warning when investigating this bug.

When I get this bug fixed, the warning will go away.

Thanks!

-- 
Jason Franklin



Bug#983645: laminard crashing: Fixed upstream

2022-02-13 Thread Jan-Benedict Glaw
Hi!

> On Fri, 2022-02-11 10:54:55 +0100, meskio  wrote:
> Quoting Jan-Benedict Glaw (2022-02-10 11:09:57)
> > I had a few tickets with Oliver upstream. There were a few cornercases
> > that my (quite large) setup triggered quickly. Seems that's all fixed
> > by now. These included:
> > 
> [...]
> > 
> > So it would be nice to update the laminard/laminarc packages to
> > current versions, and possibly trigger a rebuild when there's a new
> > capnproto available? (I'm not sure how much of their *headers*
> > actually end up in the binary...)
> 
> Amazing, thank you for working the issues with upstream to fix them. I will 
> update the package in the coming days.

I'd like to suggest to roll an updated laminar{,c,d} soonish (or
with the next release --- I'd ask for one?) because that fixes two
issues (following the log and allowing to reorder queued jobs), while
waiting for the next capnproto will fix another issue (http server
socket becoming unavailable.)

  Reordering is always helpful (ie. in my setup, I tend to queue more
than 1000 jobs, with a runtime of over a week, so issueing some
additional build to test a bugfix will face a _long_ delay), and the
log following thingie is quite easy to hit (have a job that outputs a
_lot_; can be triggered with following the log when in the time the
client needs to fetch the already stored log some more log content
comes in from the build.) That's totally annoying.

> I see capnproto 0.9.1 is already in experimental[0], so hopefully it will get 
> into sid soon. I'm not sure about the rebuild, but it looks like we might 
> want 
> to depend on capnproto >= 0.9.0. Let's check with capnproto maintainer to see 
> their plans for it and if we should upload laminar to experimental or wait 
> for 
> it to be in sid.
> 
> [0] https://packages.debian.org/experimental/capnproto

I think 0.9.1 wouldn't even be enough to catch the fix for the server
socket being closed.

Thanks,
  Jan-Benedict

-- 


signature.asc
Description: PGP signature


Bug#1004946: Cannot hold down backspace to delete password

2022-02-13 Thread Jamie Zawinski
> Why did you switch to it? Or am I misunderstanding that you did?

For the new security model. No other way to increase the privilege separation.

--
Jamie Zawinski  https://www.jwz.org/  https://www.dnalounge.com/



Bug#1005705: ITP: r-cran-spatstat.random -- GNU R random generation functionality for the 'spatstat' family

2022-02-13 Thread Andreas Tille
Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-spatstat.random -- GNU R random generation functionality 
for the 'spatstat' family
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-spatstat.random
  Version : 2.1
  Upstream Author : Adrian Baddeley,
* URL : https://cran.r-project.org/package=spatstat.random
* License : GPL-2+
  Programming Lang: GNU R
  Description : GNU R random generation functionality for the 'spatstat' 
family
 Functionality for random generation of spatial data in the 'spatstat'
 family of packages. Generates random spatial patterns of points
 according to many simple rules (complete spatial randomness, Poisson,
 binomial, random grid, systematic, cell), randomised alteration of
 patterns (thinning, random shift, jittering), simulated realisations of
 random point processes (simple sequential inhibition, Matern inhibition
 models, Matern cluster process, Neyman-Scott cluster processes, log-
 Gaussian Cox processes, product shot noise cluster processes) and
 simulation of Gibbs point processes (Metropolis-Hastings birth-death-
 shift algorithm, alternating Gibbs sampler). Also generates random
 spatial patterns of line segments, random tessellations, and random
 images (random noise, random mosaics). Excludes random generation on a
 linear network, which is covered by the separate package
 'spatstat.linnet'.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-spatstat.random



Bug#1001082: qtbase-opensource-src: segfault when closing one windows in a multi window QT application

2022-02-13 Thread Dmitry Shachnev
Hi!

On Wed, Feb 09, 2022 at 01:58:05PM -0500, theofficialgman wrote:
> any updates on this? as referenced before, it should be fixable by picking
> these two commits:
> https://codereview.qt-project.org/c/qt/qtbase/+/264529
> https://codereview.qt-project.org/c/qt/qtbase/+/237817
> which were used to resolve this bug:
> https://bugreports.qt.io/browse/QTBUG-68393

In your first message you mentioned these two commits:

https://code.qt.io/cgit/qt/qtbase.git/commit/?id=ca991ee22d3509f8
Segfault when the exiting the application under platform eglfs
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e9e8d67e31b8b6a8
Fix segfault when closing widget and destroying window in QDialog::done

But these two codereviews are completely different commits:

https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81e298a51d08c510
QWidget: fix setTabOrder for compound widgets
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=a7cbb8c639487edb
QWidget: fix setTabOrder for compound widgets

Can you please clarify which of the commits I should cherry-pick?

Sorry for the delayed reply, our team has limited resources and we are
mostly focused on the current stable release and the development release,
your bug seems to affect only oldstable.

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Bug#1005704: Debian dict-gcide is missing all words starting with A and O

2022-02-13 Thread Bill Allombert
Package: dict-gcide
Version: 0.48.5+nmu1
Severity: important

Dear Ritesh, 

It seems there is a packaging error since dict-gcide is missing the
letters A and O.

for i in A B C D E F G H I J K L M N O P Q R S T U V W X Y Z;\
  do echo -n "$i:"; zgrep -i -c "^$i" /usr/share/dictd/gcide.dict.dz; done
A:10
B:6979
C:11943
D:7415
E:5316
F:4987
G:3936
H:4769
I:5540
J:1027
K:1094
L:4242
M:7293
N:2569
O:5
P:10732
Q:691
R:5400
S:13330
T:6235
U:5258
V:1936
W:2786
X:173
Y:413
Z:389

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



Bug#1005459: rdflib: FTBFS: dh_auto_test:...

2022-02-13 Thread Jonas Smedegaard
I highly suspect that this is same bug as bug#1005463 and that the cause 
is that rdflib v5 is incompatible with pyparser v3.

Please consider releasing rdflib v6 which in my brief testing is 
compatible with pyparser v3.

 - Jonas

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

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

signature.asc
Description: signature


  1   2   3   >