Bug#1030209: pytorch-vision FTBFS with Python 3.11 only

2023-01-31 Thread Adrian Bunk
Source: pytorch-vision
Version: 0.13.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pytorch-vision&ver=0.13.1-1%2Bb1

...
   dh_auto_configure -a -O-Spybuild
py3versions: empty set of versions
E: py3versions failed at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm line 53.
make: *** [debian/rules:6: binary-arch] Error 1



Bug#1030208: statsmodels: FTBFS with scipy 1.10 on 32-bit: int64 -> int32 cast

2023-01-31 Thread Rebecca N. Palmer

Package: python3-statsmodels
Version: 0.13.5+dfsg-4
Severity: serious

Since scipy 1.10, some statsmodels tests fail on 32-bit with a message 
that int64 -> int32 casting is unsafe.  I haven't yet had time to 
investigate further.




Bug#1030207: ITP: libstatistics-topk-perl -- Implementation of the top-k streaming algorithm

2023-01-31 Thread mtj
Package: wnpp
Owner: Mason James 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libstatistics-topk-perl
  Version : 0.02
  Upstream Author : gray 
* URL : https://metacpan.org/release/Statistics-TopK
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Implementation of the top-k streaming algorithm

The Statistics::TopK module implements the top-k streaming algorithm, also
know as the "heavy hitters" algorithm. It is designed to process data streams
and probabilistally calculate the k most frequent items while using limited
memory.

A typical example would be to determine the top 10 IP addresses listed in an
access log. A simple solution would be to hash each IP address to a counter
and then sort the resulting hash by the counter size. But the hash could
theoretically require over 4 billion keys.

The top-k algorithm only requires storage space proportional to the number of
items of interest. It accomplishes this by sacrificing precision, as it is
only a probabilistic counter.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



Bug#1030206: mir-platform-graphics-eglstream-kms is not installable on !amd64/i386

2023-01-31 Thread Adrian Bunk
Package: mir-platform-graphics-eglstream-kms
Version: 2.12.0+dfsg-1
Severity: serious

The following packages have unmet dependencies:
 mir-platform-graphics-eglstream-kms : Depends: 
mir-platform-graphics-eglstream-kms20 but it is not installable

Due to:

Package: mir-platform-graphics-eglstream-kms
...
Depends: ..., mir-platform-graphics-eglstream-kms20, ...


Package: mir-platform-graphics-eglstream-kms20
...
Architecture: amd64 i386



Bug#1030205: scilab: Could not find Java package '/usr/share/java/batik-all-1.14.jar'

2023-01-31 Thread MohammadSaleh Kamayb

Package: scilab

version: 6.1.1+dfsg2-4

Severity: important


I have Debian testing and after installing scilab, it shows that log and 
does not open:


Picked up _JAVA_OPTIONS: 
-Djava.class.path=/usr/share/java/flexdock.jar:/usr/sha

re/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar
:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/jav
a/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.j
ar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar
:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/
share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian
.jar:/usr/share/java/freehep-graphicsio-emf.jar:/usr/share/java/freehep-graphics
2d.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine.jar:/usr
/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.ja
r:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop.jar:/usr/share
/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/jav
a/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-co
mmons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath.jar:/u
sr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-
runtime.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar:/usr/
share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/u
sr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/sh
are/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr
/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modul
es/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/
modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/scirend
erer/jar/scirenderer.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modul
es.scinotes.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules
.history_manager.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.co
mmons.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules
.external_objects_java.jar:/usr/share/scilab/modules/graphic_objects/jar/org.sci
lab.modules.graphic_objects.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.mod
ules.jvm.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr
/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/sc
ilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/module
s/preferences/jar/org.scilab.modules.preferences.jar:/usr/share/scilab/modules/j
avasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/console/jar/
org.scilab.modules.console.jar:/usr/share/scilab/modules/localization/jar/org.sc
ilab.modules.localization.jar:/usr/share/scilab/modules/types/jar/org.scilab.mod
ules.types.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helpto
ols.jar:/usr/share/scilab/modules/helptools/jar/scilab_ru_RU_help.jar:/usr/share
/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/he
lptools/jar/scilab_images.jar:
Warning: Could not find Java package '/usr/share/java/batik-all-1.14.jar'.
Some problems during the loading of the Java libraries occurred.
This could lead to inconsistent behaviours.
Please check SCI/etc/classpath.xml.
The native library scilocalization does not exist or cannot be found.
no scilocalization in java.library.path:
java.lang.UnsatisfiedLinkError: no scilocalization in java.library.path:
   at 
java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2429)

   at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:818)
   at java.base/java.lang.System.loadLibrary(System.java:1989)
   at org.scilab.modules.localization.MessagesJNI.(Unknown 
Source)

   at org.scilab.modules.localization.Messages.gettext(Unknown Source)
   at 
org.scilab.modules.commons.xml.XConfiguration.(Unknown Source

)
   at org.scilab.modules.core.Scilab.(Unknown Source)
Could not access to the Main Scilab Class:
Exception in thread "main" java.lang.UnsatisfiedLinkError: 
'java.lang.String org

.scilab.modules.localization.MessagesJNI.gettext(java.lang.String)'
   at org.scilab.modules.localization.MessagesJNI.gettext(Native 
Method)

   at org.scilab.modules.localization.Messages.gettext(Unknown Source)
   at 
org.scilab.modules.commons.xml.XConfiguration.(Unknown Source

)
   at org.scilab.modules.core.Scilab.(Unknown Source)

Scilab cannot create Scilab Java Main-Class (we have not been able to 
find the m
ain Scilab class. Check if the Scilab and thirdparty packages are 
available).




Bug#1030204: ITP: libcatmandu-exporter-table-perl -- Catmandu modules for exporting data in tabular MultiMarkdown

2023-01-31 Thread mtj
Package: wnpp
Owner: Mason James 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcatmandu-exporter-table-perl
  Version : 0.3.0
  Upstream Author : Jakob Voß
* URL : https://metacpan.org/release/Catmandu-Exporter-Table
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Catmandu modules for exporting data in tabular MultiMarkdown

format
Catmandu::Exporter::Table provides modules for exporting data in tabular
MultiMarkdown format.

The output can be used for simple display, for instance to preview Excel
files on the command line. Use Pandoc to further convert to other table
formats, e.g. LaTeX, html5, mediawiki:

 catmandu convert XLS to Table < sheet.xls | pandoc -t html5

See also:
 http://johnmacfarlane.net/pandoc
 https://metacpan.org/pod/Text::MarkdownTable

Catmandu provides a suite of Perl modules to ease the import, storage,
retrieval, export and transformation of metadata records.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



Bug#1030203: netdata: Netdata exits immediately after start with exit code 1

2023-01-31 Thread Markus Grunwald
Package: netdata
Version: 1.37.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
 I installed the netdata package

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Nothing was effective. I tried a reinstall with `apt purge`, `apt install`.

   * What was the outcome of this action?
 netdata still immediately exits with error code 1

   * What outcome did you expect instead?
 A running netdata service

Now that we got the template, here are the details:

[gru:~] % sudo systemctl start netdata
[gru:~] % systemctl status netdata
× netdata.service - netdata - Real-time performance monitoring
 Loaded: loaded (/lib/systemd/system/netdata.service; enabled; preset: 
enabled)
 Active: failed (Result: exit-code) since Wed 2023-02-01 07:49:50 CET; 5s 
ago
   Duration: 121ms
   Docs: man:netdata
 file:///usr/share/doc/netdata/html/index.html
 https://github.com/netdata/netdata
Process: 34968 ExecStart=/usr/sbin/netdata -D (code=exited, 
status=1/FAILURE)
   Main PID: 34968 (code=exited, status=1/FAILURE)
CPU: 149ms

Feb 01 07:49:50 tmh-gru systemd[1]: Started netdata - Real-time performance 
monitoring.
Feb 01 07:49:50 tmh-gru netdata[34968]: CONFIG: cannot load cloud config 
'/var/lib/netdata/cloud.d/cloud.conf'. Running with internal defaults.
Feb 01 07:49:50 tmh-gru netdata[34968]: 2023-02-01 07:49:50: netdata INFO  : 
MAIN : CONFIG: cannot load cloud config '/var/lib/netdata/cloud.d/cloud.conf'. 
Running with internal defaults.
Feb 01 07:49:50 tmh-gru systemd[1]: netdata.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 01 07:49:50 tmh-gru systemd[1]: netdata.service: Killing process 34977 
(netdata) with signal SIGKILL.
Feb 01 07:49:50 tmh-gru systemd[1]: netdata.service: Failed with result 
'exit-code'.

journalctl did not offer more information.

I didn't manage to configure more verbose debug output. Happy to try again if 
someone tells me how.

I ran `netdata -W unittest` with the result "ALL TESTS PASSED". Funny.

I used the upstream installer from 
https://learn.netdata.cloud/docs/agent/packaging/installer which worked without 
a problem.


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

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

Versions of packages netdata depends on:
ii  netdata-core  1.37.1-2
ii  netdata-plugins-bash  1.37.1-2
ii  netdata-web   1.37.1-2

Versions of packages netdata recommends:
ii  netdata-plugins-python  1.37.1-2

netdata suggests no packages.

-- no debconf information


Bug#1029566: transition: shibboleth-sp

2023-01-31 Thread Ferenc Wágner
Ferenc Wágner  writes:

> Sebastian Ramacher  writes:
>
>> ACK, please go ahead.
>
> Great, shibboleth-sp was uploaded and is already fully green in the
> transition tracker.  Please schedule the binNMUs for
> shibboleth-resolver.

Hi,

The transition tracker is already all green.
-- 
Thanks for your help!
Feri.



Bug#1030202: ITP: libcatmandu-stat-perl -- Catmandu modules for working with statistical data

2023-01-31 Thread mtj
Package: wnpp
Owner: Mason James 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcatmandu-stat-perl
  Version : 0.13
  Upstream Author : Patrick Hochstenbach 
* URL : https://metacpan.org/release/Catmandu-Stat
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Catmandu modules for working with statistical data

Catmandu::Stat contains modules for calculating statistics on the availablity
of fields in a data file.

 Provides modules:
  Catmandu::Exporter::Stat
  Catmandu::Fix::stat_mean
  Catmandu::Fix::stat_median
  Catmandu::Fix::stat_stddev
  Catmandu::Fix::stat_variance

See also:
 https://metacpan.org/pod/Catmandu::Breaker
 https://metacpan.org/pod/Statistics::Descriptive
 https://metacpan.org/pod/Statistics::TopK
 https://metacpan.org/pod/Algorithm::HyperLogLog

Catmandu provides a suite of Perl modules to ease the import, storage,
retrieval, export and transformation of metadata records.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

2023-01-31 Thread Diederik de Haas
On Wednesday, 1 February 2023 02:52:13 CET Dr. David Alan Gilbert wrote:
> bisected:
> GOOD [37fcacb50be7071d146144a6c5c5bf0194b9a1cf] phy: PHY_FSL_LYNX_28G should
> depend on ARCH_LAYERSCAPE BAD [f5ff79fddf0efecca538046b5cc20fb3ded2ec4f]
> dma-mapping: remove CONFIG_DMA_REMAP GOOD
> [e62c17f0455a74b182ce6373e2777817256afaa1] MAINTAINERS: update maintainer
> list of DMA MAPPING BENCHMARK GOOD
> [0fb3436b4b36cf69f4544385aa2bb8c5a4913509] sparc: Remove usage of the
> deprecated "pci-dma-compat.h" API GOOD
> [fba09099c6e506608e05e08ac717bf34501f821b] media: v4l2-pci-skeleton: Remove
> usage of the deprecated "pci-dma-compat.h" API
> 
> dg@major:~/kernel/kernel-clone$ git bisect good
> f5ff79fddf0efecca538046b5cc20fb3ded2ec4f is the first bad commit
> commit f5ff79fddf0efecca538046b5cc20fb3ded2ec4f
> Author: Christoph Hellwig 
> Date:   Sat Feb 26 16:40:21 2022 +0100
> 
> dma-mapping: remove CONFIG_DMA_REMAP
> 
> That sounds like a believable cause given that it's IOMMU related
> and device related.

Thanks for that thorough analyses!
If you're 'penguin42' on IRC, then I'd suggest to present your findings to
io...@lists.linux.dev as both the author and the reviewer are highly likely 
subscribed to that list.

scripts/get_maintainer.pl drivers/iommu/dma-iommu.c
scripts/get_maintainer.pl kernel/dma/Makefile

list them both and both results have also that ML in their result.

HTH

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


Bug#1030201: ITP: libcatmandu-solr-perl -- Catmandu modules for working with SOLR endpoints

2023-01-31 Thread mtj
Package: wnpp
Owner: Mason James 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcatmandu-solr-perl
  Version : 0.0304
  Upstream Author : Nicolas Steenlant 
* URL : https://metacpan.org/release/Catmandu-Solr
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Catmandu modules for working with SOLR endpoints

Catmandu::SOLR contains modules for working with SOLR endpoints.

Provides modules:
 Catmandu::Importer::Solr
 Catmandu::Store::Solr
 Catmandu::Store::Solr::CQL

See also:
 http://lucene.apache.org/solr/
 https://metacpan.org/pod/WebService::Solr

Catmandu provides a suite of Perl modules to ease the import, storage,
retrieval, export and transformation of metadata records.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



Bug#1030199: ITP: libcatmandu-ris-perl -- Modules for handling RIS data within the Catmandu framework

2023-01-31 Thread mtj
Package: wnpp
Owner: Mason James 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcatmandu-ris-perl
  Version : 0.13
  Upstream Author : Vitali Peil
* URL : https://metacpan.org/release/Catmandu-RIS
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Modules for handling RIS data within the Catmandu framework

Catmandu::RIS contains modules for handling RIS data.

RIS is a standardized tag format developed by Research Information Systems,
Incorporated to enable citation programs to exchange data.

Provides modules:
 Catmandu::Exporter::RIS
 Catmandu::Importer::RIS

See also:
 https://en.wikipedia.org/wiki/RIS_(file_format)

Catmandu provides a suite of Perl modules to ease the import, storage,
retrieval, export and transformation of metadata records.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



Bug#1030198: RFP: zonefs-tools -- Linux zonefs tools

2023-01-31 Thread Tommy McGee
Package: wnnp
Severity: wishlist

 Package name : zonefs-tools
 Version  : 1.6.0
 URL :https://github.com/westerndigitalcorporation/zonefs-tools
 License  : GPL
  Programming Language: C and Shell
  Description : zonefs is a very simple file system exposing
  each zone of a zoned block device as a file. zonefs does not have
  complex on-disk metadata. Its implementation relies solely on a super
  block stored at LBA 0 of the device. On mount, zonefs uses zone
  configuration information obtained directly from the device to
  populate the mount point with files representing the device zones.

The kernel support for this package is already enabled . 

I am a part of ZonedStorage team, I do have an interest in building /
maintaining this package. Other members of our team maintain this
package for OpenSuse and Fedora. 
Debian would be in my area of responsibility  

It would be  nice if this package was available for those users who
prefer Debian as their platform. Otherwise they need to compile from
source to use the tools.

Thank you,
Tommy McGee



Bug#1030197: RFP: zonefs-tools -- Linux zonefs tools

2023-01-31 Thread Tommy McGee


Package: wnnp
Severity: wishlist

 Package name : zonefs-tools
 Version  : 1.6.0
 URL :https://github.com/westerndigitalcorporation/libzbd
 License  : GPL
  Programming Language: C
  Description : zonefs is a very simple file system exposing
  each zone of a zoned block device as a file. zonefs does not have
  complex on-disk metadata. Its implementation relies solely on a super
  block stored at LBA 0 of the device. On mount, zonefs uses zone
  configuration information obtained directly from the device to
  populate the mount point with files representing the device zones.

The kernel support for this package is already enabled . 

I am a part of ZonedStorage team, I do have an interest in building /
maintaining this package. Other members of our team maintain this
package for OpenSuse and Fedora. 
Debian would be in my area of responsibility  

It would be  nice if this package was available for those users who
prefer Debian as their platform. Otherwise they need to compile from
source to use the tools.

Thank you,
Tommy McGee



Bug#1030196: RFP: libzbd Zoned Block device Manipulation library and tools

2023-01-31 Thread Tommy McGee


Package: wnnp
Severity: wishlist

* Package name: libzbd
* Version : 2.0.4
* URL :https://github.com/westerndigitalcorporation/libzbd
* License : GPL
  Programming Language: C
  Description :libzbd is a library providing functions
  simplifying access to zoned block device information and the
  execution of zone management operations.

libzbd provides data structures for describing zones of a zoned block
device (struct zbd_zone) and providing information about the device
itself (struct zbd_info).

The kernel support for this package is already enabled . 

I am a part of ZonedStorage team, I do have an interest in building /
maintaining this package. Other members of our team maintain this
package for OpenSuse and Fedora. 
Debian would be in my area of responsibility  

It would be a nice this package available for those users who prefer
Debian as their platform. Otherwise they need to compile from source to
use the tools.

Thank you,
Tommy McGee



Bug#1030191: dracut: default name when generating from dracut(1) is /boot/initrd-$kver instead of /boot/initrd.img-$kver, contrary to everything else

2023-01-31 Thread наб
The same also applies to lsinitrd, which very helpfully says
-- >8 --
$ lsinitrd
No  specified and the default image 
'/boot/efi/731b69f0dac147efadfed92f12712736/6.0.0-5-amd64/initrd' cannot be 
accessed!

Usage: lsinitrd [options] [ [ [ [...] ]]]
Usage: lsinitrd [options] -k 
...
-- >8 --

Applied
136 elif [[ -f /boot/initrd.img-${KERNEL_VERSION} ]]; then
137 image="/boot/initrd.img-${KERNEL_VERSION}"
locally

наб


signature.asc
Description: PGP signature


Bug#1030195: RM: pytango [s390x] -- RoQA; NBS; no arch-specific reverse-dependencies

2023-01-31 Thread Jeremy Bicha
Package: ftp.debian.org
X-Debbugs-Cc: pyta...@packages.debian.org
Affects: src:pytango

Please remove the binary package python3-tango on s390x. This will
allow the package to migrate back into Testing. No s390x package
depends on it.

python3-tango is not arch:all because it builds an
architecture-dependent file (C extension for Python).

python3-tango arch:all reverse dependencies
-
pan-control-systems (recommends)
python3-itango
python3-sardana
python3-taurus
python3-taurus-pyqtgraph (indirect)

This leaves one other reverse (build) dependency, python3-xrstools
which is only built on amd64 and all (and currently is not in
Testing).

There was a Debian bug filed against the package for the s390x issue
but there has been no response: https://bugs.debian.org/1017990

Thanks,
Jeremy Bicha



Bug#1030194: abi-dumper: Examples concatenated in man page

2023-01-31 Thread Wookey
Package: abi-dumper
Version: 1.2-2
Severity: minor

The man page for this page has two examples which should look like this:
abi-dumper libTest.so -o ABI.dump 
abi-dumper Module.ko.debug -o ABI.dump

But actually look like this:
abi-dumper libTest.so -o ABI.dump abi-dumper Module.ko.debug -o ABI.dump
which is quite ocnfusing on first read, until you realise what has
gone wrong.

Looking at the source I see the manpage is generated from help2man
It comes out right if you do 'abi-dumper --help':
EXAMPLES:
  abi-dumper libTest.so -o ABI.dump
  abi-dumper Module.ko.debug -o ABI.dump

So apparently help2man is messing this up.

I've not investigated further (to find out why other linefeeds are
preserved but this one is lost), but running help2man on the binary
just built is a great way to make something un-crossbuildable so maybe
just making a manpage once and getting rid of help2man is the best
approach here? Help2man is 'handy' but it's also problematic. This
isn't a fast-moving project where the man page will go out of date all
the time so converting to a simple man page, or packaging-time
generation, rather than a build-time generation, would be good for
reproducibility and cross-buildability.

Would a patch to that effect be accepted?

-- 
Wookey



Bug#1029968: Info received (Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0))

2023-01-31 Thread Dr. David Alan Gilbert
Note that the oops at this bisect point is messier than on the newer
kernels; the newer kernels hit a WARN in __vmap_pages_range_noflush, where
as at this point it slams into a BUG, but the rest of the backtrace is similar;

[   78.988024] BUG: unable to handle page fault for address: bd7fc110
[   78.988033] #PF: supervisor write access in kernel mode
[   78.988036] #PF: error_code(0x000b) - reserved bit violation
[   78.988038] PGD 10067 P4D 10067 PUD 1001a6067 PMD 22b791067 PTE 
8000270800cb9063
[   78.988046] Oops: 000b [#1] PREEMPT SMP PTI
[   78.988050] CPU: 7 PID: 879 Comm: cat Tainted: G  I   
5.17.0-rc1dg+ #20
[   78.988054] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./P55M Pro, BIOS P1.50 09/10/2009
[   78.988056] RIP: 0010:__memset+0x24/0x30
[   78.988063] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 
07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6  48 ab 
89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
[   78.988067] RSP: 0018:bd7fc0cc7d50 EFLAGS: 00010206
[   78.988071] RAX:  RBX: 9679eb788a88 RCX: 2000
[   78.988073] RDX:  RSI:  RDI: bd7fc110
[   78.988076] RBP: 8000 R08:  R09: bd7fc110
[   78.988079] R10: 0001 R11: bd7fc110 R12: 0010
[   78.988081] R13: 0010 R14: 9679ec8e4130 R15: 0010
[   78.988084] FS:  7f91fb65a740() GS:9679efdc() 
knlGS:
[   78.988087] CS:  0010 DS:  ES:  CR0: 80050033
[   78.988090] CR2: bd7fc110 CR3: 00022ce02000 CR4: 06e0
[   78.988093] Call Trace:
[   78.988096]  
[   78.988100]  __videobuf_iolock+0x5cd/0x659 [videobuf_dma_sg]
[   78.988110]  vbi_buffer_prepare+0x1aa/0x2b0 [bttv]
[   78.988125]  __videobuf_read_start+0xb9/0x1d0 [videobuf_core]
[   78.988133]  videobuf_read_stream+0x2cb/0x330 [videobuf_core]
[   78.988140]  bttv_read+0xc5/0x1d0 [bttv]
[   78.988151]  v4l2_read+0x6b/0x80 [videodev]
[   78.988169]  vfs_read+0x97/0x190
[   78.988175]  ksys_read+0x63/0xe0
[   78.988179]  do_syscall_64+0x3a/0x80
[   78.988185]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   78.988191] RIP: 0033:0x7f91fb7550ed
[   78.988194] Code: 31 c0 e9 c6 fe ff ff 50 48 8d 3d f6 54 0a 00 e8 39 fe 01 
00 66 0f 1f 84 00 00 00 00 00 80 3d f1 24 0e 00 00 74 17 31 c0 0f 05 <48> 3d 00 
f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec
[   78.988198] RSP: 002b:7ffdad058348 EFLAGS: 0246 ORIG_RAX: 

[   78.988202] RAX: ffda RBX: 0002 RCX: 7f91fb7550ed
[   78.988204] RDX: 0002 RSI: 7f91fb35 RDI: 0003
[   78.988207] RBP: 0002 R08:  R09: 
[   78.988209] R10: 7f91fb66cb40 R11: 0246 R12: 7f91fb35
[   78.988212] R13: 0003 R14: 0002 R15: 
[   78.988216]  
[   78.988218] Modules linked in: rfkill qrtr tuner_simple tuner_types 
intel_powerclamp coretemp tuner snd_hda_codec_via tda7432 kvm_intel 
snd_hda_codec_generic snd_hda_codec_hdmi tvaudio ledtrig_audio msp3400 
snd_hda_intel kvm snd_intel_dspcfg bttv snd_intel_sdw_acpi snd_hda_codec 
irqbypass tea575x snd_hda_core tveeprom videobuf_dma_sg intel_cstate 
videobuf_core videodev snd_hwdep snd_bt87x intel_uncore snd_pcm serio_raw 
pcspkr iTCO_wdt i7core_edac mc joydev intel_pmc_bxt snd_timer 
iTCO_vendor_support snd watchdog soundcore sg evdev acpi_cpufreq firewire_sbp2 
fuse msr configfs efi_pstore ip_tables x_tables autofs4 ext4 crc32c_generic 
crc16 mbcache jbd2 nouveau sd_mod t10_pi crc_t10dif crct10dif_generic 
ata_generic crct10dif_common hid_generic usbhid hid mxm_wmi wmi video 
i2c_algo_bit drm_ttm_helper ttm drm_kms_helper cec rc_core drm ahci libahci 
pata_via libata ehci_pci ehci_hcd psmouse r8169 usbcore scsi_mod crc32c_intel 
realtek i2c_i801 mdio_devres i2c_smbus libphy firewire_ohci
[   78.988301]  firewire_core lpc_ich usb_common scsi_common crc_itu_t button
[   78.988311] CR2: bd7fc110
[   78.988314] ---[ end trace  ]---
[   78.988316] RIP: 0010:__memset+0x24/0x30
[   78.988320] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 
07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6  48 ab 
89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
[   78.988324] RSP: 0018:bd7fc0cc7d50 EFLAGS: 00010206
[   78.988327] RAX:  RBX: 9679eb788a88 RCX: 2000
[   78.988329] RDX:  RSI:  RDI: bd7fc110
[   78.988332] RBP: 8000 R08:  R09: bd7fc110
[   78.988334] R10: 0001 R11: bd7fc110 R12: 0010
[   78.988337] R13: 0010 R14: 9679ec8e4130 R15: 0010
[   78.988340] FS:  7f91fb65a740() GS:9679efdc00

Bug#1030193: lintian: Overriding for prefer-uscan-symlink is not possible

2023-01-31 Thread Joao Eriberto Mota Filho
Package: lintian
Version: 2.116.2
Severity: normal

Dear maintainer,

In my package obs-move-transition I needed to make an override using
filenamemangle[1][2] option.

[1] 
https://salsa.debian.org/debian/obs-move-transition/-/blob/debian/master/debian/watch
[2] 
https://salsa.debian.org/debian/obs-move-transition/-/commit/2482783eb472483f4cec0f0a330712aa6891e692

After this change[2], lintian said me:

X: obs-downstream-keyer source: prefer-uscan-symlink filenamemangle 
s/.*muted..([\d\.]+)..span./@PACKAGE@-$1\.tar\.gz/ [debian/watch:19]

After I make an override, litian said me:

W: obs-downstream-keyer source: mismatched-override prefer-uscan-symlink 
filenamemangle s/.*muted..([\d\.]+)..span./@PACKAGE@-$1\.tar\.gz/ 
[debian/watch:19] [debian/source/lintian-overrides:4]
X: obs-downstream-keyer source: prefer-uscan-symlink filenamemangle 
s/.*muted..([\d\.]+)..span./@PACKAGE@-$1\.tar\.gz/ [debian/watch:19]

Consequently, is not possible to make an override for prefer-uscan-symlink
filenamemangle. I think that lintian is interpreting my REGEX.

Regards,

Eriberto



Bug#1030192: RFS: alien-arena-data/7.71.3+ds-1 [ITA] -- Game data files for Alien Arena

2023-01-31 Thread Raoul de Raadt

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "alien-arena-data":

* Package name : alien-arena-data
Version : 7.71.3+ds-1
Upstream contact : Raoul de Raadt 
* URL : https://martianbackup.com
* License : alien-arena-data
* Vcs : https://salsa.debian.org/games-team/alien-arena-data
Section : non-free/games

The source builds the following binary packages:

alien-arena-data - Game data files for Alien Arena

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


https://mentors.debian.net/package/alien-arena-data/

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

dget -x 
https://mentors.debian.net/debian/pool/non-free/a/alien-arena-data/alien-arena-data_7.71.3+ds-1.dsc


Changes since the last upload:

alien-arena-data (7.71.3+ds-1) unstable; urgency=medium
.
[ Raoul de Raadt ]
* Team upload.
* Files-Excluded method for data
* Added watch file as in alien-arena
* Fixed issue with Files-Excluded not working
* Removed separate botinfo, changed some links/email addresses

Regards,

Raoul de Raadt



Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

2023-01-31 Thread Dr. David Alan Gilbert
bisected:
GOOD [37fcacb50be7071d146144a6c5c5bf0194b9a1cf] phy: PHY_FSL_LYNX_28G should 
depend on ARCH_LAYERSCAPE
BAD [f5ff79fddf0efecca538046b5cc20fb3ded2ec4f] dma-mapping: remove 
CONFIG_DMA_REMAP
GOOD [e62c17f0455a74b182ce6373e2777817256afaa1] MAINTAINERS: update maintainer 
list of DMA MAPPING BENCHMARK
GOOD [0fb3436b4b36cf69f4544385aa2bb8c5a4913509] sparc: Remove usage of the 
deprecated "pci-dma-compat.h" API
GOOD [fba09099c6e506608e05e08ac717bf34501f821b] media: v4l2-pci-skeleton: 
Remove usage of the deprecated "pci-dma-compat.h" API

dg@major:~/kernel/kernel-clone$ git bisect good
f5ff79fddf0efecca538046b5cc20fb3ded2ec4f is the first bad commit
commit f5ff79fddf0efecca538046b5cc20fb3ded2ec4f
Author: Christoph Hellwig 
Date:   Sat Feb 26 16:40:21 2022 +0100

dma-mapping: remove CONFIG_DMA_REMAP

That sounds like a believable cause given that it's IOMMU related
and device related.

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/



Bug#1030161: roundcube: Fix short date test before and after ICU 72.1

2023-01-31 Thread Guilhem Moulin
Control: tag -1 pending

On Tue, 31 Jan 2023 at 13:38:20 -0500, Amin Bandali wrote:
> Would you please consider adopting the attached patch (also forwarded
> and applied upstream) for fixing the test suite breakage both before
> and after ICU 72.1?  Though Debian unstable and testing already have
> ICU 72.1, Ubuntu lunar (devel) is still on 71.1, and it would be great
> if this failure was fixed such that roundcube would build with ICU
> both older or newer than 72.1.

Applied, thanks!

-- 
Guilhem.


signature.asc
Description: PGP signature


Bug#1030191: dracut: default name when generating from dracut(1) is /boot/initrd-$kver instead of /boot/initrd.img-$kver, contrary to everything else

2023-01-31 Thread наб
Package: dracut
Version: 059-3
Severity: normal

Dear Maintainer,

I just ran dracut --kver 6.1.0-3-amd64, knowing I already had an initrd
there; it didn't stop me! And what's worse, I got this:
-- >8 --
nabijaczleweli@babtop:~$ l /boot/
total 72M
-rw-r--r-- 1 root root 252K Nov 26 16:06 config-6.0.0-5-amd64
-rw-r--r-- 1 root root 254K Jan 29 13:33 config-6.1.0-3-amd64
drwxr-xr-x 4 root root 1.5K Jan  1  1970 efi
-rw--- 1 root root  19M Feb  1 02:21 initrd-6.1.0-3-amd64
-rw-r--r-- 1 root root  19M Feb  1 01:52 initrd.img-6.0.0-5-amd64
-rw-r--r-- 1 root root  19M Feb  1 01:52 initrd.img-6.1.0-3-amd64
-rw-r--r-- 1 root root   83 Nov 26 16:06 System.map-6.0.0-5-amd64
-rw-r--r-- 1 root root   83 Jan 29 13:33 System.map-6.1.0-3-amd64
-rw-r--r-- 1 root root 7.5M Nov 26 16:06 vmlinuz-6.0.0-5-amd64
-rw-r--r-- 1 root root 8.0M Jan 29 13:33 vmlinuz-6.1.0-3-amd64
-- >8 --

Please consider fixing this because if I wasn't paying attention to it
(having just removed /boot/initrd-6.0.0-5-amd64 from Dec  4 15:48)
I'd be pulling my hair out for hours to come.

Consider this Found in whatever the current dracut version was on
Dec  4 15:48, too.
Presumably the Debian patch got broken around that time;
for my usage I made
1144 elif [[ -e $dracutsysrootdir/boot/vmlinuz-${kernel} ]]; 
then
1145 outfile="$dracutsysrootdir/boot/initrd-${kernel}"
&
1155 outfile="$dracutsysrootdir/boot/initrd-${kernel}"
into
1144 elif [[ -e $dracutsysrootdir/boot/vmlinuz-${kernel} ]]; 
then
1145 outfile="$dracutsysrootdir/boot/initrd.img-${kernel}"
&
1155 outfile="$dracutsysrootdir/boot/initrd.img-${kernel}"
(only the first hunk is required).

Best,
наб

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

Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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

Versions of packages dracut depends on:
ii  dracut-core  059-3

dracut recommends no packages.

Versions of packages dracut suggests:
pn  dracut-network  

-- no debconf information


signature.asc
Description: PGP signature


Bug#1030190: mplayer uninstallable

2023-01-31 Thread Dan Jacobson
Also:
The following packages have unmet dependencies:
 libavformat58 : Depends: libsrt1.4-gnutls (>= 1.4.4) which is a virtual 
package and is not provided by any available package



Bug#1030190: mplayer uninstallable

2023-01-31 Thread Dan Jacobson
Package: mplayer
Version: 2:1.4+ds1-3+b2
Severity: critical

The following packages have unmet dependencies:
 mplayer : Depends: libavcodec58 (>= 7:4.4) which is a virtual package and is 
not provided by any available package
   Depends: libavformat58 (>= 7:4.4) which is a virtual package and is 
not provided by any available package
   Depends: libavutil56 (>= 7:4.4) which is a virtual package and is 
not provided by any available package
   Depends: libpostproc55 (>= 7:4.4) which is a virtual package and is 
not provided by any available package
   Depends: libswresample3 (>= 7:4.4) which is a virtual package and is 
not provided by any available package
   Depends: libswscale5 (>= 7:4.4) which is a virtual package and is 
not provided by any available package

The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) mplayer [Not Installed]

*** No more solutions available ***

In sources.list I have
deb http://.../debian/ unstable main contrib non-free non-free-firmware



Bug#1024638: opencv: embeds build path in Python extension

2023-01-31 Thread Victor Westerhuis
Vagrant Cascadian  schreef op 22 november 2022 
19:56:07 CET:
>On 2022-11-22, Victor Westerhuis wrote:
>> Stripping the rpath from the Python extension makes its BuildId
>> reproducible. The extension still works and both arch:all and arch:any
>> builds succeed locally.
>...
>> diff --git a/debian/rules b/debian/rules
>> index b4d654102..6bd845023 100755
>> --- a/debian/rules
>> +++ b/debian/rules
>> @@ -151,6 +151,7 @@ override_dh_auto_configure:
>>  -- --name=opencv --system=custom --configure-args "\
>>  dh_auto_configure -S cmake -D modules/python -B 
>> {build_dir} -- \
>>  -GNinja \
>> +-DCMAKE_SKIP_RPATH=ON \
>>  -DOpenCV_BINARY_DIR=$(CURDIR)/$(BUILDDIR) \
>>  
>> -DOPENCV_PYTHON_STANDALONE_INSTALL_PATH={install_dir} \
>>  -DOPENCV_SKIP_PYTHON_LOADER=ON \
>
>I would recommend using -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON instead of
>-DCMAKE_SKIP_RPATH=ON.
Unfortunately the Python modules are built as a separate module via a separate 
Cmake invocation, so this has not worked. The rpaths passed to the linker of 
the Python libraries are absolute build paths, so they are not reproducible. 
>
>This is the default behavior with (the currently experimental) debhelper
>compat level 14. A little more detail on the issue is available here:
>
>  
> https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
>
>The main advantage of CMAKE_BUILD_RPATH_USE_ORIGIN is it is more likely
>to work with test suites that depend on the full path.
OpenCV does not ship tests for its Python module, so this is not an issue. 
>
>live well,
>  vagrant

Control: reopen -1

I would suggest to change the d/rules files to my original proposal. 
-- 
Groet, Regards,

Victor Westerhuis



Bug#1030189: Let regular users know need to put non-free-firmware in sources.list

2023-01-31 Thread Dan Jacobson
Package: general

The average user will not notice his firmware is not updating any more.

Some users, if they do
$ apt-show-versions |grep 'No available version in archive'
will see
firmware-amd-graphics:all 20221214-3 installed: No available version in archive
firmware-brcm80211:all 20221214-3 installed: No available version in archive...

And if they check
/var/lib/apt/lists/*_debian_dists_unstable_non-free_i18n_Translation-en.diff_Index
will notice something funny happened...
 137480 T-2023-01-30-2019.16-F-2023-01-14-1406.12
 137194 T-2023-01-30-2019.16-F-2023-01-14-2004.08
 137161 T-2023-01-30-2019.16-F-2023-01-16-0203.33
 137036 T-2023-01-30-2019.16-F-2023-01-16-2003.44
  73251 T-2023-01-30-2019.16-F-2023-01-18-2013.57
  73217 T-2023-01-30-2019.16-F-2023-01-19-2008.34
  72676 T-2023-01-30-2019.16-F-2023-01-20-2016.02

So he must do Google Search.
https://www.google.com/search?q=debian+firmware+non-free
which leads to
https://wiki.debian.org/Firmware
which says
...a new repository component non-free-firmware...

So that means he needs to add it to /etc/apt/sources.list.d/
Ah ha!

Yes, he should be regularly subscribed to debian-user, but that's too
much.
Or https://lists.debian.org/debian-announce/, but that's too many boring
messages too.

Yes, he uses apt-listchanges, but that won't tell him this.

So I'm saying that Debian needs a mechanism to have his computer tell
him to do this.

Maybe the next time he uses apt*, somehow the system should tell him...



Bug#1030188: PyQt5.Qt is empty

2023-01-31 Thread Zipdox
Package: python3-pyqt5
Version: 5.15.8
 
PyQt5.Qt is empty. This causes gnuradio-companion to fail running, as well as 
problems with other packages.
 
To reproduce the bug:
import PyQt5.Qt
PyQt5.Qt.QValidator
 
Please look at the Arch bug report for more details: 
https://bugs.archlinux.org/task/77315
 
Debian sid, kernel 6.1.0-2-rt-amd64, libc6 2.36-8



Bug#1030187: adv-17v35x-dkms: module fails to build for Linux 6.1

2023-01-31 Thread Andreas Beckmann
Package: adv-17v35x-dkms
Version: 5.0.6.0-4
Severity: serious

Hi,

adv-17v35x-dkms fails to build the kernel module for Linux 6.1:

DKMS make.log for adv-17v35x-5.0.6.0 for kernel 6.1.0-2-amd64 (x86_64)
Tue Jan 31 16:13:56 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.1.0-2-amd64'
  CC [M]  /var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c:2162:27: error: 
initialization of ‘void (*)(struct uart_port *, struct ktermios *, const struct 
ktermios *)’ from incompatible pointer type ‘void (*)(struct uart_port *, 
struct ktermios *, struct ktermios *)’ [-Werror=incompatible-pointer-types]
 2162 | .set_termios= serialadv_set_termios,
  |   ^
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c:2162:27: note: (near 
initialization for ‘serialadv_pops.set_termios’)
cc1: some warnings being treated as errors
make[1]: *** [/usr/src/linux-headers-6.1.0-2-common/scripts/Makefile.build:255: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o] Error 1
make: *** [/usr/src/linux-headers-6.1.0-2-common/Makefile:2017: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.1.0-2-amd64'

full log at
https://ci.debian.net/data/autopkgtest/testing/amd64/a/adv-17v35x/30877035/log.gz


Andreas


Bug#973990: #973990: recap

2023-01-31 Thread Jeremy Sowden
I think there may be some confusion about where the problem lies with
this bug.  Let me summarize my understanding.

The original bug-report was created against shorewall because shorewall
had stopped working:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973990#5

However, Vincas Dargis, the reporter, observed that shorewall worked
with Linux 5.8 and did not with 5.9 and proposed #972454 as the culprit:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973990#15

On that basis, I reassigned the report to xtables-addons and closed it,
since Linux 5.9 support was added in a later version of xtables-addons:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973990#26

However, the bug was reopened by Vincas because even with the latest
version of xtables-addons (3.23-1), shorewall is still not working
correctly.

I believe, therefore, that the failure of xtables-addons to build with
Linux 5.9 was merely coincidental, and so we can rule out it as the
cause of the bug and should assign the bug back to shorewall.

J.


signature.asc
Description: PGP signature


Bug#1030186: enigmail: FTBFS (Error: Cannot find module 'chalk')

2023-01-31 Thread Santiago Vila

Package: src:enigmail
Version: 2:2.2.4-0.3
Severity: serious
Tags: ftbfs

Dear maintainer:

I've just noticed that enigmail currently fails to build in bookworm:

make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1
make[1]: Entering directory '/<>'
static_analysis/eslint package
There was a problem loading formatter: 
/usr/share/nodejs/eslint/lib/cli-engine/formatters/stylish
Error: Cannot find module 'chalk'
Require stack:
- /usr/share/nodejs/eslint/lib/cli-engine/formatters/stylish.js
- /usr/share/nodejs/eslint/lib/cli-engine/cli-engine.js
- /usr/share/nodejs/eslint/lib/cli-engine/index.js
- /usr/share/nodejs/eslint/lib/cli.js
- /usr/share/nodejs/eslint/bin/eslint.js
make[1]: *** [Makefile:37: eslint] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j1 test "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 
returned exit code 2
make: *** [debian/rules:5: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2

There is a full log here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/enigmail.html

What I don't know is why is this package available in bookworm at all, given 
that
it had a serious bug #975926 to prevent the migration.

If this is really a bug in another package (i.e. some build-dependency),
please reassign and use "affects" on src:enigmail.

Thanks.



Bug#975926: enigmail should not be shipped in bookworm

2023-01-31 Thread Santiago Vila

Hi.

Something strange just happened which led me to this bug
report which you filed in 2020 (and last touched in May 2021).

enigmail is available in bookworm right now.

$ rmadison enigmail
enigmail   | 2:1.9.9-1~deb8u1| oldoldoldstable | source, all
enigmail   | 2:2.2.4-0.2~deb10u1 | oldstable   | source, all
enigmail   | 2:2.2.4-0.3 | stable  | source, all
enigmail   | 2:2.2.4-0.3 | testing | source, all
enigmail   | 2:2.2.4-0.3 | unstable| source, all

(Bug in britney?)

Thanks.



Bug#1030153: [pkg-apparmor] Bug#1030153: complaining

2023-01-31 Thread Christian Boltz
Hello,

Am Dienstag, 31. Januar 2023, 19:20:38 CET schrieb Antoine Beaupré:
> so something is happening with apparmor here. it looks like profile
> are "piling up" in some way, with something like this:
> 
> /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/sudo//null-/usr/bin/
> apt//null-/usr/bin/dash//null-/usr/bin/etckeeper//null-/etc/etckeeper/
> pre-install.d/50uncommitted-changes//null-/usr/bin/etckeeper//null-/us
> r/bin/perl

That means sshd executed /usr/bin/bash (without having an execute rule), 
and bash executed /usr/bin/sudo, which executed /usr/bin/apt, and so on.

I'm somewhat surprised about that because the upstream profile for sshd 
has the following rule since Dec 3 2016 :

  /{usr/,}bin/bash Uxr,

This rule should allow to execute /bin/bash and /usr/bin/bash in 
unconfined mode (= without AppArmor restrictions) - and therefore should 
also avoid the long chain you see.

However, your log looks like your profile does not allow executing 
/usr/bin/bash.

Now I wonder - does your sshd profile lack this line/rule?
(If in doubt, please attach the complete profile.)


Regards,

Christian Boltz
-- 
But you are probably also complaining if local root exploits in the
kernel are fixed, because now you no longer can use that to become root
easily... [Stefan Seyfried in opensuse-factory]



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


Bug#1030185: qutebrowser: Suggest or recommend the Hunspell dictionary packages

2023-01-31 Thread Soren Stoutner
Package: qutebrowser
Version: 2.5.2-2
Severity: wishlist
Tags: upstream

Debian recently added support for Hunspell .bdic binary dictionaries used by Qt 
WebEngine.

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

https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/merge_requests/12

There is an upstream request to handle the `QTWEBENGINE_DICTIONARIES_PATH` in a 
way that is compatible with Debian's implementation.

https://github.com/qutebrowser/qutebrowser/issues/4966

Once that is in place, it might make sense to either recommend or suggest the 
Hunspell language packages.



Bug#1030092: nvme-cli: nvme list json output contains wrapped-around negative integers

2023-01-31 Thread Daniel Swarbrick

Hi Daniel,

On 01.02.23 09:48, Daniel Baumann wrote:
I've reproduced the bug with 2.2 and can confirm that 2.3 does fix it. 
Did you notice that nvme-cli 2.3-1 is FTBFS on the buildds? The build 
appears to be failing due to a missing "libnvme-mi".


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1029461: Processed (with 1 error): xemacs21-packages: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)

2023-01-31 Thread Hilmar Preuße

Control: reassign -1 texlive-latex-base
Control: forcemerge -1 1029438

Am 31.01.2023 um 23:50 teilte Santiago Vila mit:

Well, I feared the merge could fail, and yes, it did.
I have not gotten the hang of it.

If you could merge them properly, that would be great.

Thanks a lot.




--
sigfault



Bug#1029461: Processed (with 1 error): xemacs21-packages: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)

2023-01-31 Thread Santiago Vila

Well, I feared the merge could fail, and yes, it did.
I have not gotten the hang of it.

If you could merge them properly, that would be great.

Thanks a lot.



Bug#1030184: ezquake FTBFS

2023-01-31 Thread Judit Foglszinger
Source: ezquake
Version: 3.6.1-1
Severity: serious
Tags: ftbfs

Hi,

ezquake fails to build from source on the buildds.

https://buildd.debian.org/status/package.php?p=ezquake&suite=sid

(log eg 
https://buildd.debian.org/status/fetch.php?pkg=ezquake&arch=amd64&ver=3.6.1-1&stamp=1674575852&raw=0)
...
FAILED: ezquake.p/common.c.o 
cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 
-I/usr/include/opus -I/usr/include/libpng16 -I/usr/include/minizip 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -Werror -Wno-deprecated-declarations 
-Wno-misleading-indentation -Wno-format-truncation -Wno-unused-function 
'-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 '-DVERSION="r666"' 
-DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 -DWITH_ZIP 
-Wno-strict-aliasing -Wno-int-to-pointer-cast -Wno-pointer-to-int-cast -msse2 
-DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG -DWITH_SPEEX -DWITH_ZLIB 
-DX11_GAMMA_WORKAROUND -DRENDERER_OPTION_CLASSIC_OPENGL 
-DRENDERER_OPTION_MODERN_OPENGL -MD -MQ ezquake.p/common.c.o -MF 
ezquake.p/common.c.o.d -o ezquake.p/common.c.o -c ../common.c
../common.c: In function ‘COM_WriteToUniqueTempFile’:
../common.c:429:17: error: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Werror=unused-result]
  429 | write(fd, buffer, bytes);
  | ^~~~
cc1: all warnings being treated as errors
[128/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu 
-I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 
-I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror 
-Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation 
-Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 
'-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 
-DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast 
-Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG 
-DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND 
-DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ 
ezquake.p/com_msg.c.o -MF ezquake.p/com_msg.c.o.d -o ezquake.p/com_msg.c.o -c 
../com_msg.c
[129/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu 
-I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 
-I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror 
-Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation 
-Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 
'-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 
-DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast 
-Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG 
-DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND 
-DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ 
ezquake.p/config_manager.c.o -MF ezquake.p/config_manager.c.o.d -o 
ezquake.p/config_manager.c.o -c ../config_manager.c
[130/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu 
-I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 
-I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror 
-Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation 
-Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 
'-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 
-DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast 
-Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG 
-DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND 
-DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ 
ezquake.p/console.c.o -MF ezquake.p/console.c.o.d -o ezquake.p/console.c.o -c 
../console.c
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v 
returned exit code 1
make: *** [debian/rules:12: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

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


Bug#1029461: xemacs21-packages: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)

2023-01-31 Thread Santiago Vila

reassign 1029461 texlive-base
affects 1029461 src:xemacs21-packages
found 1029461 2022.20220923-1
fixed 1029461 2022.20230122-1
forcemerge 1029461 1029438
thanks

Hi. I've just built "xemacs21-packages" in bookworm and it failed.
Then I built it in sid, and it worked.

The error message is the same as the one in auctex.
Therefore, I believe all the above is correct.

I'm doing CC to Hilmar and Mark just in case.

Thanks.



Bug#1029621: Related bug

2023-01-31 Thread Soren Stoutner
This has some relation to the integration of the Hunspell .bdic files into 
Debian.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030183[1] and 
the links it contains.

-- 
Soren Stoutner
so...@stoutner.com


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


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


Bug#1030172: game-data-packager: no suitable mirror for etqw found

2023-01-31 Thread Simon McVittie
On Tue, 31 Jan 2023 at 20:40:12 +, Simon McVittie wrote:
> A user who does not want to use reportbug writes:
> > WARNING:game_data_packager.download:Failed to download 
> > "http://www.mirrorservice.org/sites/distfiles.gentoo.org/distfiles/ETQW-client-1.5-full.x86.run":
> >  HTTP Error 404: Not Found

(etc.)

This appears to be because Gentoo no longer hosts copies of ETQW patches.

The company behind ETQW now has them on a CDN, so we can change g-d-p
to point to that, meaning no special workaround will be needed.

> > First, after having found a working download for the missing file at 
> > https://ftp.jeuxlinux.fr/files/ETQW-client-1.5-full.x86.run, I copied it 
> > into ~/Downloads/ETQW.
> > Then, with the help of some knowledgeable guys from #debian-games on 
> > irc.debian.org, I modified step 3.) to the following terminal command:
> > 
> > game-data-packager --binary-executables -d ~/Downloads/ETQW 
> > --save-downloads ~/Downloads/ETQW etqw /path/to/ETQWDVD

In fact --save-downloads is only necessary if you want any other
auto-downloaded files to end up in ~/Downloads/ETQW - and as a
convenient side-effect, it also tells g-d-p to search that directory
before downloading anything. You were using that side-effect as your
workaround here.

If you just want g-d-p to consider a pre-downloaded game file as something
it can use, it's sufficient to list that file, or a directory containing
that file, on the command line (like you did for /path/to/ETQWDVD).

smcv



Bug#909567: ITP: opensnitch -- Port of the Little Snitch application firewall

2023-01-31 Thread Alias
On lintian warnings - I can adapt the project's github wiki pages into 
man pages, if necessary.



On Sun, Jan 29, 2023 at 11:43 am, Petter Reinholdtsen  
wrote:

[Petter Reinholdtsen]
 Just for fun, I tried to build the source from Chris on Bullseye, 
but it

 had a few issues.  I cloned it to
 https://salsa.debian.org/debian/pkg-opensnitch.git> > and 
applied a

 few fixed to get it to build.  Sadly it is not working.


Just for the record, as the package git repo currently is the upstream
repo at github, and the plan is to move the Debian packaging to the
golang team, I got the git repo
https://salsa.debian.org/debian/pkg-opensnitch.git> > removed. 
 All

relevant Debian packaging parts where already in upstreams repo.

--
Happy hacking
Petter Reinholdtsen




Bug#1030183: falkon: Add support for system-wide dictionaries

2023-01-31 Thread Soren Stoutner
Package: falkon
Version: 22.12.0-3
Severity: wishlist
Tags: upstream

Debian recently added support for system-wide .bdic binary dictionaries used by 
Qt WebEngine.

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

https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/merge_requests/12

To support this, Falkon needs to look for dictionaries in the same manner as 
the Qt WebEngine, as can be seen on line 235 of the following file:

https://sources.debian.org/src/qtwebengine-opensource-src/5.15.12%2Bdfsg-2/src/core/web_engine_library_info.cpp/

I have reported this upstream at https://bugs.kde.org/show_bug.cgi?id=465094

In addition to adding the correct detection logic, Falkon can also choose to 
suggest or recommend the various Hunspell language dictionary packages.



Bug#1030173: Document breaking changes in NEWS.Debian

2023-01-31 Thread Lee Garrett

On 31/01/2023 22:08, Vincent Bernat wrote:

On 2023-01-31 21:44, Lee Garrett wrote:

with release 2.6 haproxy has dropped the "ssl-engine" keyword by 
default. Would

be nice to document that in NEWS.Debian so it gets shown by tools such as
apt-listchanges during upgrade from bullseye to bookworm.

In my case haproxy failed to start with my bullseye config since it 
still had

the "ssl-engine" keyword in it.


I understand this would be useful, but it opens me to get bugs like 
"NEWS.Debian says something about ssl-engine, but not about some other 
change". I would need to make a summary of upstream's CHANGELOG file. 
This seems a tedious task.


I've written a NEWS file for you:

haproxy (2.6.8-2) unstable; urgency=medium

  Starting with haproxy 2.6, the "ssl-engine" keyword has been removed. 
You will

  need to remove this setting for your previous config to continue to work.

  Previously, clients sending an invalid request header like "Version: 
rtsp/1.1"
  would still get their request being served. Starting with haproxy 
2.6, this
  will result in a 502 response. If you depend on the old, buggy 
behaviour, set

  "option accept-invalid-http-requests" in the relevant config section.

 -- Lee Garrett   Tue, 31 Jan 2023 22:57:05 +0100



Bug#1030173: Document breaking changes in NEWS.Debian

2023-01-31 Thread Lee Garrett

On 31/01/2023 22:08, Vincent Bernat wrote:

On 2023-01-31 21:44, Lee Garrett wrote:

with release 2.6 haproxy has dropped the "ssl-engine" keyword by 
default. Would

be nice to document that in NEWS.Debian so it gets shown by tools such as
apt-listchanges during upgrade from bullseye to bookworm.

In my case haproxy failed to start with my bullseye config since it 
still had

the "ssl-engine" keyword in it.


I understand this would be useful, but it opens me to get bugs like 
"NEWS.Debian says something about ssl-engine, but not about some other 
change". I would need to make a summary of upstream's CHANGELOG file. 
This seems a tedious task.
I wouldn't list all changes there, only those that break existing 
setups. So stuff where admins need to get active.


AFAICS there are only three backwards-incompatible changes [0]:
- "ssl-engine" being dropped
- openssl 0.9.8 support being dropped (irrelevant, as the package is 
built against a newer version)
- previously, clients sending an invalid "Version: rtsp/1.1" header 
would still get their request served, this is now caught and a 502 
served. The old behaviour can be enabled with "option 
accept-invalid-http-request"


All other changes add new options, or improve on existing behaviour, so 
nothing that breaks existing config during upgrade.


I'm fine with writing a NEWS.Debian for you as I think users would 
benefit from it. I think the ssl-engine drop is a bigger speedbump, as 
configs with that setting will silently fail on upgrade, as there 
doesn't seem to be any validation of it when it gets restarted. I only 
noticed a bit later as some of my services weren't reachable.


[0] https://www.mail-archive.com/haproxy@formilux.org/msg42371.html, 
grep for "potentially user-visible changes"




Bug#1025907: package-update-indicator no longer alerts user to available updates

2023-01-31 Thread Julian Groß
I looked into it a little and I also think that this is most likely a 
packagekit issue.
I reported the issue towards the packagekit package with some additional 
info. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030179



Greetings
Julian Groß


OpenPGP_0xAF605C87F9E5AE94.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1030182: unifrac: FTBFS:

2023-01-31 Thread Sebastian Ramacher
Source: unifrac
Version: 1.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=unifrac&arch=amd64&ver=1.2-2%2Bb1&stamp=1675069851&raw=0

I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_unifrac/build; 
python3.11 -m unittest discover -v 
unifrac (unittest.loader._FailedTest.unifrac) ... ERROR

==
ERROR: unifrac (unittest.loader._FailedTest.unifrac)
--
ImportError: Failed to import test module: unifrac
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 440, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in 
_get_module_from_name
__import__(name)
  File 
"/<>/.pybuild/cpython3_3.11_unifrac/build/unifrac/__init__.py", 
line 11, in 
from unifrac._methods import (unweighted,
  File 
"/<>/.pybuild/cpython3_3.11_unifrac/build/unifrac/_methods.py", 
line 15, in 
import skbio
  File "/usr/lib/python3/dist-packages/skbio/__init__.py", line 11, in 
import skbio.io  # noqa
^^^
  File "/usr/lib/python3/dist-packages/skbio/io/__init__.py", line 248, in 

import_module('skbio.io.format.lsmat')
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "/usr/lib/python3/dist-packages/skbio/io/format/lsmat.py", line 77, in 

from skbio.stats.distance import DissimilarityMatrix, DistanceMatrix
  File "/usr/lib/python3/dist-packages/skbio/stats/distance/__init__.py", line 
197, in 
from ._mantel import mantel, pwmantel
  File "/usr/lib/python3/dist-packages/skbio/stats/distance/_mantel.py", line 
16, in 
from scipy.stats import PearsonRConstantInputWarning
ImportError: cannot import name 'PearsonRConstantInputWarning' from 
'scipy.stats' (/usr/lib/python3/dist-packages/scipy/stats/__init__.py)


--
Ran 1 test in 0.001s

FAILED (errors=1)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_unifrac/build; python3.11 -m unittest 
discover -v 
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:8: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher



Bug#1030180: tiledb-py: FTBFS: E: pybuild pybuild:388: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build

2023-01-31 Thread Sebastian Ramacher
Source: tiledb-py
Version: 0.19.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=tiledb-py&arch=amd64&ver=0.19.1-1%2Bb1&stamp=1675121783&raw=0

x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g 
-fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python3/dist-packages/pybind11/include 
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11 
-c tiledb/cc/array.cc -o build/temp.linux-x86_64-cpython-311/tiledb/cc/array.o 
-fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++17 
-Wno-deprecated-declarations -fvisibility=hidden
tiledb/cc/array.cc: In function ‘void 
libtiledbcpp::init_array(pybind11::module&)’:
tiledb/cc/array.cc:149:11: error: no matching function for call to 
‘pybind11::class_::def(const char [13], )’
   15 |   py::class_(m, "Array")
  |   ~
   16 |   //.def(py::init())
  |   ~~
   18 |   .def(
  |   ~
   19 |   py::init(),
  |   
~~
   20 |   py::keep_alive<1, 2>() /* Array keeps Context alive */)
  |   ~~~
   21 |   // TODO capsule Array(const Context& ctx, tiledb_array_t* carray,
  |   ~
   22 |   // tiledb_config_t* config)
  |   ~~~
   23 |   .def("is_open", &Array::is_open)
  |   
   24 |   .def("uri", &Array::uri)
  |   
   25 |   .def("schema", &Array::schema)
  |   ~~
   26 |   //.def("ptr", [](Array& arr){ return py::capsule(arr.ptr()); } )
  |   
   27 |   // open with encryption key
  |   ~~~
   28 |   .def("open",
  |   
   29 |(void (Array::*)(tiledb_query_type_t, 
tiledb_encryption_type_t,
  |
~~~
   30 | const std::string &)) &
  | ~~~
   31 |Array::open)
  |
   32 |   // open with encryption key and timestamp
  |   ~
   33 |   .def("open",
  |   
   34 |(void (Array::*)(tiledb_query_type_t, 
tiledb_encryption_type_t,
  |
~~~
   35 | const std::string &, uint64_t)) &
  | ~
   36 |Array::open)
  |
   37 |   .def("reopen", &Array::reopen)
  |   ~~
   38 |   .def("set_open_timestamp_start", &Array::set_open_timestamp_start)
  |   ~~
   39 |   .def("set_open_timestamp_end", &Array::set_open_timestamp_end)
  |   ~~
   40 |   .def_property_readonly("open_timestamp_start",
  |   ~~
   41 |  &Array::open_timestamp_start)
  |  ~
   42 |   .def_property_readonly("open_timestamp_end", 
&Array::open_timestamp_end)
  |   

   43 |   .def("set_config", &Array::set_config)
  |   ~~
   44 |   .def("config", &Array::config)
  |   ~~
   45 |   .def("close", &Array::close)
  |   
   46 |   .def("consolidate",
  |   ~~~
   47 |py::overload_cast(&Array::consolidate))
  |  
   49 |   .def("consolidate",
  |   ~~~
   50 |py::overload_cast(&Array::consolidate))
  |  
   53 |   //(void (Array::*)(const Context&, const std::string&,
  |   ~~
   54 |   // tiledb_encryp

Bug#1030181: python-iow: FTBFS: FAILED (errors=1)

2023-01-31 Thread Sebastian Ramacher
Source: python-iow
Version: 1.0.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=python-iow&arch=amd64&ver=1.0.6-1%2Bb1&stamp=1675071622&raw=0

   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_iow/build; 
python3.11 -m unittest discover -v 
bp (unittest.loader._FailedTest.bp) ... ERROR

==
ERROR: bp (unittest.loader._FailedTest.bp)
--
ImportError: Failed to import test module: bp
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 440, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in 
_get_module_from_name
__import__(name)
  File "/<>/.pybuild/cpython3_3.11_iow/build/bp/__init__.py", line 
10, in 
from ._conv import to_skbio_treenode, from_skbio_treenode, 
to_skbio_treearray
  File "bp/_conv.pyx", line 1, in init bp._conv
  File "/usr/lib/python3/dist-packages/skbio/__init__.py", line 11, in 
import skbio.io  # noqa
^^^
  File "/usr/lib/python3/dist-packages/skbio/io/__init__.py", line 248, in 

import_module('skbio.io.format.lsmat')
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "/usr/lib/python3/dist-packages/skbio/io/format/lsmat.py", line 77, in 

from skbio.stats.distance import DissimilarityMatrix, DistanceMatrix
  File "/usr/lib/python3/dist-packages/skbio/stats/distance/__init__.py", line 
197, in 
from ._mantel import mantel, pwmantel
  File "/usr/lib/python3/dist-packages/skbio/stats/distance/_mantel.py", line 
16, in 
from scipy.stats import PearsonRConstantInputWarning
ImportError: cannot import name 'PearsonRConstantInputWarning' from 
'scipy.stats' (/usr/lib/python3/dist-packages/scipy/stats/__init__.py)


--
Ran 1 test in 0.001s

FAILED (errors=1)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_iow/build; python3.11 -m unittest 
discover -v 
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:12: binary-arch] Error 25


Cheers
-- 
Sebastian Ramacher



Bug#1030179: packagekit: update to 1.2.6 breaks package package-update-indicator

2023-01-31 Thread Julian Groß
Package: packagekit
Version: 1.2.6-2
Severity: normal

Dear Maintainer,


the update from 1.2.5 to 1.2.6 broke the package-update-indicator package.
There is a bug report on the affected package here: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025907

After looking at the debug looks and glancing at the code, it looks to me like 
the newest packagekit version just ends up telling it that there is no updates 
available (even if there are updates available).

Attached are package-update-indicator debug logs with 1.2.5 and 1.2.6.
While it says that it is using the "apt" backend instead of "aptcc", I *think* 
it gets that backend name from packagekit. It isn't defined anywhere in the 
package-update-indicator source code.


Greetings
Julian Groß


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

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

Versions of packages packagekit depends on:
ii  init-system-helpers 1.65.2
ii  libappstream4   0.16.0-1
ii  libapt-pkg6.0   2.5.5
ii  libc6   2.36-8
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.5-1
ii  libglib2.0-bin  2.74.5-1
ii  libgstreamer1.0-0   1.20.5-1
ii  libpackagekit-glib2-18  1.2.6-2
ii  libpolkit-gobject-1-0   122-2
ii  libsqlite3-03.40.1-1
ii  libstdc++6  12.2.0-14
ii  libsystemd0 252.4-2
ii  policykit-1 122-2

Versions of packages packagekit recommends:
pn  packagekit-tools  
ii  systemd   252.4-2

Versions of packages packagekit suggests:
ii  appstream  0.16.0-1

-- no debconf information
$ package-update-indicator --debug
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.172: 
property "update-command" set to "/usr/bin/synaptic-pkexec --dist-upgrade-mode"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.172: 
property "always-active" set to "TRUE"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.173: 
indicator icon: system-software-update, notification title: "", notification 
body: ""
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.173: 
indicator icon: system-software-update, notification title: "", notification 
body: ""
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
backend: aptcc
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
roles: 
cancel;depends-on;get-details;get-files;get-packages;get-repo-list;required-by;get-update-detail;get-updates;install-files;install-packages;install-signature;refresh-cache;remove-packages;repo-enable;resolve;search-details;search-file;search-group;search-name;update-packages;what-provides;download-packages;get-old-transactions;repair-system;get-details-local;get-files-local;repo-remove
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
network-state: online
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
scheduled first check in: 180s
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
property "refresh-interval" set to 28800
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
property "use-mobile-connection" set to false
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
state initial -> up-to-date
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.174: 
indicator icon: system-software-update, notification title: "Auf dem neuesten 
Stand", notification body: "Das System ist auf dem neuesten Stand"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.197: 
setting HTTP proxy to "(null)"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.197: 
setting HTTPS proxy to "(null)"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.197: 
setting FTP proxy to "(null)"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.197: 
setting SOCKS proxy to "(null)"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.197: 
setting the list of download IPs which should not go through a proxy to "(null)"
(package-update-indicator:71692): package-update-indicator-DEBUG: 22:15:13.197: 
setting the PAC string to "(null)"

(package-update-indicator:71692): Gdk-CRITICAL **: 22:15:14.321: 
gdk_window_thaw_toplevel_updates: assertion 
'window->update_and_descendants_freeze_count > 0' failed
(package-update-indicator:71692): pack

Bug#1016919: lintian: bash-term-in-posix-shell false positive for `. "$(dirname "$0")/functions.sh"`

2023-01-31 Thread Diederik de Haas
On Tuesday, 31 January 2023 22:27:24 CET Russ Allbery wrote:
> Diederik de Haas  writes:
> > I looked a little deeper/further and specifically into
> > `lib/coresight.sh` and that file does contain `echo -n`, which
> > ShellCheck does flag as it's undefined in POSIX.  So maybe it was
> > actually triggered by the 'included' file?
> > 
> > I don't know if that could also be the case for the original reporter.
> 
> Although echo -n is undefined in POSIX, Debian requires it to work in all
> shells that are eligible to be /bin/sh.  See:
> 
> https://www.debian.org/doc/debian-policy/ch-files.html#scripts

Ah, yeah, then lintian shouldn't trip over that.
I lack any Perl knowledge to (properly) understand the code snippet you posted 
earlier or what lintian does in code, so I can't help with that.

Cheers,
  Diederik

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


Bug#961508: ifupdown: RTNETLINK answers: File exists

2023-01-31 Thread ael
On Tue, Jan 31, 2023 at 02:10:46PM -0500, Antoine Beaupré wrote:
> I have a similar problem with ifupdown on my home server which has
> accumulated a rather unfortunate pile of crap...
> 
> iface eth0 inet static
>   # fix RTNETLINK errors on boot see https://bugs.debian.org/961508
> pre-up ip addr flush dev eth0 || true
>   address 192.168.0.3
>   netmask 255.255.255.0
>   gateway 192.168.0.1

 I have not encountered this for a long time now. It looks as if ipdown
 now flushes:

# ifdown -v eth0
...
 ip -4 addr flush dev eth0
...

ael



Bug#999485: firmware-brcm80211: Please add brcmfmac43456-sdio.* files as it's not just used in RPi devices

2023-01-31 Thread Diederik de Haas
Hi Salvatore and Gunnar,

On Tuesday, 31 January 2023 19:17:43 CET Salvatore Bonaccorso wrote:
> > Gunnar indicated that he's willing to remove the files from
> > raspi-firmware,
> > but they still need to be added to firmware-brcm80211, so pretty please?
> 
> So I looked at this, and don't think the firmware-nonfree packages
> should take it over. Why?
> The firmware files are not part of linux-firmware.git .

I understand that reasoning and as said on IRC, that was the reason that I did 
not know how to deal with that and therefor couldn't make a MR myself.

> Would they fit into a separate source package not associated with
> raspi-config?

I do strongly think they do not belong in the raspi-firmware package for the 
reason I retitled this bug and retitled my response Subject. Another reason is 
that the raspi-firmware package makes (several) assumptions, namely that they 
are only used/usable on RPi devices and have a /boot/firmware directory (where 
a FAT partition is mounted, although that part is not checked for).
I have previously expressed my concerns/doubts about that, but that's outside 
the scope of this bug.
It also looks 'weird' to install the raspi-firmware package while you only care 
about the wifi firmware and not care about RPi's at all.

> The other option is that they get included upstream in
> linux-firmware.git by upstream?

Gunnar knows I'm not much of a fan of Raspberry Pi Foundation (RPF) and that 
was confirmed once again by their typical reaction to this exact request. 

I'm too 'lazy' to look it up, so I'll paraphrase it:
"It works for us (so fsck off). Can't you just use our files?"

Regards,
  Diederik

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


Bug#1029845: harfbuzz: non-distributable font included in source

2023-01-31 Thread James Addison
Source: harfbuzz
Followup-For: Bug #1029845

Based on the previous: I think that the font was probably accidentally
committed to source control while testing a fix for the issue reported on
GitHub - and so following upstream's removal of the font seems to make sense,
given that there doesn't appear to be any explicit public permission provided
by the owner/successors of the license on the Debian mailing lists.



Bug#1030159: dpkg: Please add future:+time64 option for y2038 support on 32-bit platforms

2023-01-31 Thread Guillem Jover
Hi!

On Tue, 2023-01-31 at 18:41:09 +0100, Helge Deller wrote:
> Package: dpkg
> Severity: wishlist
> Tags: lfs, patch, hppa
> Version: 1.21.17

> Binaries on most (all?) 32-bit platforms will have the y2038 problem, if
> they haven't been compiled with the "_TIME_BITS=64" define.

I think very recent architectures might by default have already 64-bit
time_t, will need to check.

> This bug report is about the request to add a dpkg option similar to
> the "future=+lfs" option, and which can be added to DEB_BUILD_MAINT_OPTIONS
> by package maintainers if they can and want their binaries compiled for 
> y2038-readiness.
> 
> My proposal is to call this option "future=+time64", which should be disabled
> by default.

Ah! I've had in mind adding support for this, but I got the impression
the 64-bit time_t support in glibc was still being worked on. In any case,
thanks! I've queued the attached patch for 1.22.x, tracked at the branch
.

Thanks,
Guillem
From 78fd2b85741a4a8adc6c654635032cb38a50fab8 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 31 Jan 2023 22:07:51 +0100
Subject: [PATCH] Dpkg::Vendor::Debian: Add time64 feature in the future area

This feature (disabled by default) enables 64-bit time on 32-bit
architectures where their ABI does not define it by default. This
feature automatically enables the lfs one as it is required by it.

FIXME: Check for recent 32-bit arches with 64-bit time_t, which might
need to be ignored?

Closes: #1030159
Based-on-patch-by: Helge Deller 
---
 man/dpkg-buildflags.pod   |  7 +++
 scripts/Dpkg/Vendor/Debian.pm | 19 ---
 scripts/t/Dpkg_BuildFlags.t   |  1 +
 3 files changed, 24 insertions(+), 3 deletions(-)

diff --git a/man/dpkg-buildflags.pod b/man/dpkg-buildflags.pod
index 7ec5db192..5f672f2b2 100644
--- a/man/dpkg-buildflags.pod
+++ b/man/dpkg-buildflags.pod
@@ -341,6 +341,13 @@ This setting (disabled by default) enables Large File Support on 32-bit
 architectures where their ABI does not include LFS by default, by adding
 B<-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64> to B.
 
+=item B
+
+This setting (since dpkg 1.22.0; disabled by default) enables 64-bit time_t
+support on 32-bit architectures where their ABI does not include it by
+default, by adding B<-D_TIME_BITS=64> to B.
+This setting automatically enables the B feature as it requires it.
+
 =back
 
 =head2 qa
diff --git a/scripts/Dpkg/Vendor/Debian.pm b/scripts/Dpkg/Vendor/Debian.pm
index 06aa49ad6..7b4db3362 100644
--- a/scripts/Dpkg/Vendor/Debian.pm
+++ b/scripts/Dpkg/Vendor/Debian.pm
@@ -105,6 +105,7 @@ sub set_build_features {
 my %use_feature = (
 future => {
 lfs => 0,
+time64 => 0,
 },
 qa => {
 bug => 0,
@@ -162,6 +163,8 @@ sub set_build_features {
 
 my $arch = Dpkg::Arch::get_host_arch();
 my ($abi, $libc, $os, $cpu) = Dpkg::Arch::debarch_to_debtuple($arch);
+my ($abi_bits, $abi_endian) = Dpkg::Arch::debarch_to_abiattrs($arch);
+my $cpu_bits = Dpkg::Arch::debarch_to_cpubits($arch);
 
 unless (defined $abi and defined $libc and defined $os and defined $cpu) {
 warning(g_("unknown host architecture '%s'"), $arch);
@@ -170,10 +173,16 @@ sub set_build_features {
 
 ## Area: future
 
-if ($use_feature{future}{lfs}) {
-my ($abi_bits, $abi_endian) = Dpkg::Arch::debarch_to_abiattrs($arch);
-my $cpu_bits = Dpkg::Arch::debarch_to_cpubits($arch);
+if ($use_feature{future}{time64}) {
+if ($abi_bits != 32 or $cpu_bits != 32) {
+$use_feature{future}{time64} = 0;
+} else {
+# On glibc 64-bit time_t support requires LFS.
+$use_feature{future}{lfs} = 1;
+}
+}
 
+if ($use_feature{future}{lfs}) {
 if ($abi_bits != 32 or $cpu_bits != 32) {
 $use_feature{future}{lfs} = 0;
 }
@@ -337,6 +346,10 @@ sub _add_build_flags {
'-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64');
 }
 
+if ($flags->use_feature('future', 'time64')) {
+$flags->append('CPPFLAGS', '-D_TIME_BITS=64');
+}
+
 ## Area: qa
 
 # Warnings that detect actual bugs.
diff --git a/scripts/t/Dpkg_BuildFlags.t b/scripts/t/Dpkg_BuildFlags.t
index c6e0ef8ff..1697d2787 100644
--- a/scripts/t/Dpkg_BuildFlags.t
+++ b/scripts/t/Dpkg_BuildFlags.t
@@ -87,6 +87,7 @@ ok($bf->is_maintainer_modified('DPKGFLAGS'), 'prepend marked flag as maint modif
 my %known_features = (
 future => [ qw(
 lfs
+time64
 ) ],
 hardening => [ qw(
 bindnow
-- 
2.39.1



Bug#1016919: lintian: bash-term-in-posix-shell false positive for `. "$(dirname "$0")/functions.sh"`

2023-01-31 Thread Russ Allbery
Diederik de Haas  writes:

> I looked a little deeper/further and specifically into
> `lib/coresight.sh` and that file does contain `echo -n`, which
> ShellCheck does flag as it's undefined in POSIX.  So maybe it was
> actually triggered by the 'included' file?

> I don't know if that could also be the case for the original reporter.

Although echo -n is undefined in POSIX, Debian requires it to work in all
shells that are eligible to be /bin/sh.  See:

https://www.debian.org/doc/debian-policy/ch-files.html#scripts

-- 
Russ Allbery (r...@debian.org)  



Bug#1029845: harfbuzz: non-distributable font included in source

2023-01-31 Thread James Addison
Source: harfbuzz
Followup-For: Bug #1029845

Potentially relevant context:

 - https://github.com/flutter/flutter/issues/16886
 - https://lists.debian.org/debian-legal/2011/05/msg5.html



Bug#1016919: lintian: bash-term-in-posix-shell false positive for `. "$(dirname "$0")/functions.sh"`

2023-01-31 Thread Diederik de Haas
On Tuesday, 31 January 2023 18:10:57 CET Russ Allbery wrote:
> > I: linux-perf: bash-term-in-posix-shell '. $(dirname
> > $0)/../lib/coresight.sh'
> > [usr/lib/perf-core/tests/shell/coresight/asm_pure_loop.sh:8]
> Yeah, I think it's a false positive in this check (check_line in
> Lintian::Check::Shell::NonPosix::BashCentric):

I looked a little deeper/further and specifically into `lib/coresight.sh` and 
that file does contain `echo -n`, which ShellCheck does flag as it's undefined 
in 
POSIX.  So maybe it was actually triggered by the 'included' file?

I don't know if that could also be the case for the original reporter.

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


Bug#1030173: Document breaking changes in NEWS.Debian

2023-01-31 Thread Vincent Bernat

On 2023-01-31 21:44, Lee Garrett wrote:


with release 2.6 haproxy has dropped the "ssl-engine" keyword by default. Would
be nice to document that in NEWS.Debian so it gets shown by tools such as
apt-listchanges during upgrade from bullseye to bookworm.

In my case haproxy failed to start with my bullseye config since it still had
the "ssl-engine" keyword in it.


I understand this would be useful, but it opens me to get bugs like 
"NEWS.Debian says something about ssl-engine, but not about some other 
change". I would need to make a summary of upstream's CHANGELOG file. 
This seems a tedious task.




Bug#1030178: Compilation of boost1.81 fails on x32 due to wrong compiler flag -march=i686

2023-01-31 Thread Mattias Ellert
Source: boost1.81
Version: 1.81.0-4
Severity: important
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: port-x32 ftbfs-x32

End of build log from buildd:

gcc.compile.c++ 
bin.v2/libs/chrono/build/gcc-12/release/debug-symbols-on/threading-multi/visibility-hidden/chrono.o

"g++"   -fvisibility-inlines-hidden -g -O2 
-ffile-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-unused-local-typedefs -fPIC -pthread -O3 -finline-functions -Wno-inline 
-Wall -Wextra -g -fvisibility=hidden -Wdate-time -D_FORTIFY_SOURCE=2 
-march=i686 -Wno-long-long -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG 
 -I"."  -c -o 
"bin.v2/libs/chrono/build/gcc-12/release/debug-symbols-on/threading-multi/visibility-hidden/chrono.o"
 "libs/chrono/src/chrono.cpp"

cc1plus: error: CPU you selected does not support x86-64 instruction set
...failed gcc.compile.c++ 
bin.v2/libs/chrono/build/gcc-12/release/debug-symbols-on/threading-multi/visibility-hidden/chrono.o...
gcc.compile.c++ 
bin.v2/libs/chrono/build/gcc-12/release/debug-symbols-on/threading-multi/visibility-hidden/thread_clock.o

"g++"   -fvisibility-inlines-hidden -g -O2 
-ffile-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-unused-local-typedefs -fPIC -pthread -O3 -finline-functions -Wno-inline 
-Wall -Wextra -g -fvisibility=hidden -Wdate-time -D_FORTIFY_SOURCE=2 
-march=i686 -Wno-long-long -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG 
 -I"."  -c -o 
"bin.v2/libs/chrono/build/gcc-12/release/debug-symbols-on/threading-multi/visibility-hidden/thread_clock.o"
 "libs/chrono/src/thread_clock.cpp"

cc1plus: error: CPU you selected does not support x86-64 instruction set
...failed gcc.compile.c++ 
bin.v2/libs/chrono/build/gcc-12/release/debug-symbols-on/threading-multi/visibility-hidden/thread_clock.o...
...failed updating 2 targets...
...updated 42 targets...
make[1]: *** [debian/rules:189: override_dh_auto_build-common] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:180: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2



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


Bug#1030177: pygame-sdl2: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '2.1.0-for-renpy-8.0.2'

2023-01-31 Thread Sebastian Ramacher
Source: pygame-sdl2
Version: 8.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=pygame-sdl2&arch=amd64&ver=8.0.2-1%2Bb2&stamp=1675116153&raw=0

running install_egg_info
Traceback (most recent call last):
  File "/<>/setup.py", line 143, in 
setup(
  File "/<>/setuplib.py", line 332, in setup
setuptools.setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 108, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/command/install.py", line 68, 
in run
return orig.install.run(self)
   ^^
  File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/install.py", line 
709, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
987, in run_command
cmd_obj.ensure_finalized()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111, 
in ensure_finalized
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/command/install_egg_info.py", 
line 31, in finalize_options
ei_cmd = self.get_finalized_command("egg_info")
 ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 305, 
in get_finalized_command
cmd_obj.ensure_finalized()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111, 
in ensure_finalized
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line 
219, in finalize_options
parsed_version = parse_version(self.egg_version)
 ^^^
  File 
"/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/version.py", 
line 266, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'2.1.0-for-renpy-8.0.2'
E: pybuild pybuild:388: install: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py install --root 
/<>/debian/python3-pygame-sdl2 
dh_auto_install: error: pybuild --install -i python{version} -p 3.11 --dest-dir 
/<>/debian/python3-pygame-sdl2 returned exit code 13
make: *** [debian/rules:6: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher



Bug#1030176: libvirt-python: E: pybuild pybuild:388: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build

2023-01-31 Thread Sebastian Ramacher
Source: libvirt-python
Version: 8.4.0-0.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=libvirt-python&arch=amd64&ver=8.4.0-0.1%2Bb3&stamp=1675112239&raw=0

Missing type converters: 
int *:1 
ERROR: failed virDomainFDAssociate
Traceback (most recent call last):
  File "/<>/setup.py", line 338, in 
setup(name = 'libvirt-python',
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 108, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", 
line 132, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/<>/setup.py", line 155, in run
subprocess.check_call([sys.executable, "generator.py", "libvirt", apis[0], 
"py"])
  File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', 'generator.py', 
'libvirt', '/usr/share/libvirt/api/libvirt-api.xml', 'py']' returned non-zero 
exit status 1.
E: pybuild pybuild:388: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:12: build-arch] Error 25

Cheers
-- 
Sebastian Ramacher



Bug#1030175: libgetdata: FTBFS: dh_install: error: missing files, aborting

2023-01-31 Thread Sebastian Ramacher
Source: libgetdata
Version: 0.11.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=libgetdata&arch=amd64&ver=0.11.0-5%2Bb1&stamp=1675112061&raw=0

   dh_install -a
install -m0755 -d debian/libgetdata-dev//usr/include
cp --reflink=auto -a debian/tmp/usr/include/getdata 
debian/tmp/usr/include/getdata.f debian/tmp/usr/include/getdata.h 
debian/libgetdata-dev//usr/include/
install -m0755 -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/
install -m0755 -d 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.so 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata/
install -m0755 -d 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/getdata.pc 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig/
install -m0755 -d debian/libgetdata8//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8.1.0 
debian/libgetdata8//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7.1.0 
debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libfgetdata6//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6.1.0 
debian/libfgetdata6//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libf95getdata7//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7.1.0 
debian/libf95getdata7//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libgetdata-tools//usr/bin
cp --reflink=auto -a debian/tmp/usr/bin/checkdirfile 
debian/tmp/usr/bin/dirfile2ascii debian/libgetdata-tools//usr/bin/
install -m0755 -d debian/libgetdata-tools//usr/share/man/man1
cp --reflink=auto -a debian/tmp/usr/share/man/man1/checkdirfile.1 
debian/tmp/usr/share/man/man1/dirfile2ascii.1 
debian/libgetdata-tools//usr/share/man/man1/
dh_install: warning: Cannot find (any matches for) 
"usr/local/lib/python3.10/dist-packages/*" (tried in ., debian/tmp)

dh_install: warning: python3-pygetdata missing files: 
usr/local/lib/python3.10/dist-packages/*
dh_install: error: missing files, aborting
make: *** [debian/rules:28: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher



Bug#1030174: iminuit: FTBFS: 5 failed, 427 passed, 5 skipped in 8.22s

2023-01-31 Thread Sebastian Ramacher
Source: iminuit
Version: 2.11.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=iminuit&arch=amd64&ver=2.11.2-3%2Bb1&stamp=1675110798&raw=0

=== short test summary info 
SKIPPED [1] tests/test_tabulate.py:4: could not import 'tabulate': No module 
named 'tabulate'
SKIPPED [1] tests/test_core.py:124: could not import 'numba': No module named 
'numba'
SKIPPED [1] tests/test_minuit.py:1348: could not import 'numba': No module 
named 'numba'
SKIPPED [1] tests/test_util.py:335: could not import 'numba': No module named 
'numba'
SKIPPED [1] tests/test_util.py:361: could not import 'numba': No module named 
'numba'
FAILED tests/test_scipy.py::test_scipy_method[TNC-False-False] - DeprecationW...
FAILED tests/test_scipy.py::test_scipy_method[TNC-False-True] - DeprecationWa...
FAILED tests/test_scipy.py::test_scipy_method[TNC-True-False] - DeprecationWa...
FAILED tests/test_scipy.py::test_scipy_method[TNC-True-True] - DeprecationWar...
FAILED tests/test_scipy.py::test_scipy_constraints_2[True] - ValueError: outp...
5 failed, 427 passed, 5 skipped in 8.22s
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_iminuit/build; python3.11 -m pytest 
tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
returned exit code 13
make: *** [debian/rules:16: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher



Bug#1030092: nvme-cli: nvme list json output contains wrapped-around negative integers

2023-01-31 Thread Daniel Baumann
close 1030092 2.3-1
thanks

On 1/31/23 05:30, Daniel Baumann wrote:
> I've just uploaed 2.3 that should indeed fix
> it.

I've reproduced the bug with 2.2 and can confirm that 2.3 does fix it.

Regards,
Daniel



Bug#1030000: fontconfig: after upgrade from 2.13.1-4.5 to 2.14.1-3 subpixel is enabled

2023-01-31 Thread Thorsten Glaser
Hi Andreas,

a bit out of order, but easier to respond (I’m a bit under the
weather so excuse any issues ahead of time):

>By 'disabled' I assume you mean 'Never', right?

Uhm, short walkthrough:

• Native
• Full
• Never
• Yes

>Did it also create 10-no-sub-pixel.conf ?

(sid-amd64)root@tglase:/etc # git status
On branch master
nothing to commit, working tree clean
(sid-amd64)root@tglase:/etc # ll fonts/conf.d/10*
lrwxrwxrwx 1 root root 53 Jan 31 21:25 fonts/conf.d/10-hinting-full.conf -> 
/usr/share/fontconfig/conf.avail/10-hinting-full.conf
lrwxrwxrwx 1 root root 53 Jan 31 21:25 fonts/conf.d/10-no-sub-pixel.conf -> 
/usr/share/fontconfig/conf.avail/10-no-sub-pixel.conf
lrwxrwxrwx 1 root root 54 Jan 13 21:30 fonts/conf.d/10-yes-antialias.conf -> 
/usr/share/fontconfig/conf.avail/10-yes-antialias.conf

>Have you experienced this problem in previous upgrades?

Unsure. My main system runs bullseye now to avoid UsrMove,
and this is a sid/amd64 chroot. Maybe.

>Can you reproduce the problem at all?

Let’s see ☻

(sid-amd64)root@tglase:/etc # dpkg -i 
/var/cache/apt/archives/fontconfig-config_2.14.1-3_amd64.deb
(Reading database ... 330670 files and directories currently installed.)
Preparing to unpack .../fontconfig-config_2.14.1-3_amd64.deb ...
Unpacking fontconfig-config (2.14.1-3) over (2.14.1-3) ...
Setting up fontconfig-config (2.14.1-3) ...
Processing triggers for man-db (2.11.2-1) ...
(sid-amd64)root@tglase:/etc # git status
On branch master
Untracked files:
  (use "git add ..." to include in what will be committed)
fonts/conf.d/10-sub-pixel-rgb.conf

nothing added to commit but untracked files present (use "git add" to track)


So, yes, I can easily reproduce it *and* I end up with *both*
10-no-sub-pixel.conf and 10-sub-pixel-rgb.conf symlinked (ouch).

Now here it comes:

(sid-amd64)root@tglase:/etc # rm fonts/conf.d/10-sub-pixel-rgb.conf
(sid-amd64)root@tglase:/etc # DPKG_MAINTSCRIPT_PACKAGE=fontconfig-config 
DPKG_MAINTSCRIPT_NAME=postinst sh /var/lib/dpkg/info/fontconfig-config.postinst 
configure 2.14.1-3
(sid-amd64)root@tglase:/etc # git status
On branch master
nothing to commit, working tree clean

It’s not the postinst alone…

(sid-amd64)root@tglase:/etc # DPKG_MAINTSCRIPT_PACKAGE=fontconfig-config 
DPKG_MAINTSCRIPT_NAME=prerm sh /var/lib/dpkg/info/fontconfig-config.prerm 
upgrade 2.14.1-3
(sid-amd64)root@tglase:/etc # DPKG_MAINTSCRIPT_PACKAGE=fontconfig-config 
DPKG_MAINTSCRIPT_NAME=preinst sh /var/lib/dpkg/info/fontconfig-config.preinst 
upgrade 2.14.1-3 2.14.1-3

It’s also not them, unless I’m calling them wrong?

I have another hunch:

/var/cache/apt/archives/fontconfig-config_2.14.1-3_amd64.deb/deb://CONTENTS/etc/fonts/conf.d/10-sub-pixel-rgb.conf
 exists.

And indeed, that’s it. While the symlink is shipped in /etc,
it is not listed in
/var/cache/apt/archives/fontconfig-config_2.14.1-3_amd64.deb/deb://DEBIAN/conffiles
and therefore not handled as conffile by dpkg but as regular
file that is always extracted when extracting the package,
overwriting what was there. (I’m not sure what Policy says to
conffile handling for symlinks; I vaguely recall that at some
point post etch or so, conffile handling was changed in Policy
to mandate inclusion of anything under /etc but I might mis‐
remember that.)

This will have to be today’s feedback from me, sorry.

Good luck,
//mirabilos
-- 
 exceptions: a truly awful implementation of quite a nice idea.
 just about the worst way you could do something like that, afaic.
 it's like anti-design.   that too… may I quote you on that?
 sure, tho i doubt anyone will listen ;)



Bug#1030173: Document breaking changes in NEWS.Debian

2023-01-31 Thread Lee Garrett
Package: haproxy
Version: 2.6.8-1
Severity: normal
X-Debbugs-Cc: deb...@rocketjump.eu

Hi,

with release 2.6 haproxy has dropped the "ssl-engine" keyword by default. Would
be nice to document that in NEWS.Debian so it gets shown by tools such as
apt-listchanges during upgrade from bullseye to bookworm.

In my case haproxy failed to start with my bullseye config since it still had
the "ssl-engine" keyword in it.

Thanks for maintaining haproxy!
- Lee


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

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

Versions of packages haproxy depends on:
ii  adduser3.118
ii  dpkg   1.20.12
ii  init-system-helpers1.60
ii  libc6  2.31-13+deb11u5
ii  libcrypt1  1:4.4.18-4
ii  libgcc-s1  10.2.1-6
ii  liblua5.3-05.3.3-1.1+b1
pn  libopentracing-c-wrapper0  
ii  libpcre2-8-0   10.36-2+deb11u1
ii  libssl1.1  1.1.1n-0+deb11u3
pn  libssl3
ii  libsystemd0247.3-7+deb11u1
ii  lsb-base   11.1.0
ii  zlib1g 1:1.2.11.dfsg-2+deb11u2

haproxy recommends no packages.

Versions of packages haproxy suggests:
pn  haproxy-doc  
pn  vim-haproxy  



Bug#1030056: qa.debian.org: The most recent lintian version known by UDD is 2.115.3

2023-01-31 Thread Lucas Nussbaum
Hi,

On 30/01/23 at 21:58 +0100, Francesco Poli wrote:
> On Mon, 30 Jan 2023 21:14:53 +0100 Lucas Nussbaum wrote:
> 
> > Hi Francesco,
> 
> Hi Lucas!   :-)
> 
> > 
> > On 30/01/23 at 20:45 +0100, Francesco Poli (wintermute) wrote:
> [...]
> > > Why is UDD outdated w.r.t. the lintian version?
> > > Shouldn't UDD be aware of the version currently in testing, or maybe
> > > even in unstable?
> [...]
> > 
> > The update to a newer lintian version on the UDD lintian worker is a
> > manual process.
> 
> Ah, I wasn't aware of that.

The reason is that it takes a few days to update the data, so it's
better to make an informed decision about it and not do it for releases
that are going to be superseded soon anyway.

> > I'll do that soon, but I have some other Debian stuff
> > queued up that looks more important.
> > Any reason in particular you need the latest version?
> 
> Well, one reason is that lintian/2.115.3 is incorrectly complaining
> about [many packages], stating that they declare compatibility with a
> non-existing Debian Policy version.
> This obviously happens, because a new Policy version (4.6.2) has been
> released after lintian/2.115.3, and all the updated packages are seen
> by lintian/2.115.3 as wrong...
> 
> [many packages]: 
> 

I updated lintian on the worker. The results will get updated over the
next few days (probably 3 to 5 days).

Progress can be checked using, for example:
udd=> select lintian_version, 
count(distinct(source,version,package,package_version,architecture)) from 
lintian_logs group by lintian_version;
 lintian_version | count
-+
 2.115.3 | 365203   <- that needs to get to 0
 2.116.2 |224
(2 rows)

I'll check again in a few days and close when the data is migrated.

Lucas



Bug#1030172: game-data-packager: no suitable mirror for etqw found

2023-01-31 Thread Simon McVittie
Package: game-data-packager
Version: 67
Severity: normal

A user who does not want to use reportbug writes:

> #
> The problem I faced trying to install "Quake Wars: Enemy Territory" on Debian 
> 11 (stable)
> #
> 
> I ran the following 3 terminal commands, one after the other:
> 
> 1.) sudo apt install etqw:i386
> 2.) mkdir ~/Downloads/ETQW && cd ~/Downloads/ETQW
> 3.) game-data-packager --binary-executables -d ~/Downloads/ETQW etqw 
> /path/to/ETQWDVD
> 
> Step 1.) and 2.) did not pose any problems. But step 3.) failed with the 
> following terminal output:
> 
> WARNING:game_data_packager.download:Failed to download 
> "ftp://62.8.228.162/pub/games/etqw/ETQW-client-1.4-1.5-update.x86.run": 
> 
> WARNING:game_data_packager.download:Failed to download 
> "http://www.mirrorservice.org/sites/distfiles.gentoo.org/distfiles/ETQW-client-1.5-full.x86.run":
>  HTTP Error 404: Not Found
> WARNING:game_data_packager.download:Failed to download 
> "ftp://ftp.ru.debian.org/gentoo-distfiles/distfiles/ETQW-client-1.5-full.x86.run":
>   change directory.')")>
> WARNING:game_data_packager.download:Failed to download 
> "ftp://ftp.fr.freshrpms.net/pub/linux/gentoo/distfiles/ETQW-client-1.5-full.x86.run":
>   change directory.')")>
> WARNING:game_data_packager.download:Failed to download 
> "ftp://ftp.kr.debian.org/gentoo/distfiles/ETQW-client-1.5-full.x86.run": 
>  change directory.')")>
> WARNING:game_data_packager.download:Failed to download 
> "ftp://ftp.linux.org.tr/gentoo/distfiles/ETQW-client-1.5-full.x86.run": 
>  change directory.')")>
> ERROR:game_data_packager.build:Failed to download necessary files for 
> etqw-pb-bin
> ERROR:game_data_packager.build:Failed to download necessary files for 
> etqw-data
> ERROR:game_data_packager.build:Failed to download necessary files for etqw-bin
> ERROR:game_data_packager.build:Unable to complete any packages because 
> downloads failed.
> 
> 
> The problem obviously was that not a single mirror for the file 
> "ETQW-client-1.5-full.x86.run" was available.
> 
> 
> ###
> How the problem trying to install "Quake Wars: Enemy Territory" on Debian 11 
> (stable) was solved
> ###
> 
> First, after having found a working download for the missing file at 
> https://ftp.jeuxlinux.fr/files/ETQW-client-1.5-full.x86.run, I copied it into 
> ~/Downloads/ETQW.
> Then, with the help of some knowledgeable guys from #debian-games on 
> irc.debian.org, I modified step 3.) to the following terminal command:
> 
> game-data-packager --binary-executables -d ~/Downloads/ETQW --save-downloads 
> ~/Downloads/ETQW etqw /path/to/ETQWDVD
> 
> With the added parameter of "--save-downloads ~/Downloads/ETQW", 
> game-data-packager could pick up the file "ETQW-client-1.5-full.x86.run" from 
> ~/Downloads/ETQW and create the functional "Quake Wars: Enemy Territory" .deb 
> files
> via the original steps 1.), 2.) and 3.) [modified, of course]
> 
> Problem solved. Quake Wars: Enemy Territory working on Debian 11 (stable).



Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2023-01-31 Thread Soren Stoutner
In discussion with the Qt 5 maintainer, we have found a solution that does not 
use a 
symlink, which will be included in the upcoming 5.15.12+dfsg-3 release.

More information can be found at:

https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/merge_requests/12[1]

On Monday, January 9, 2023 11:37:58 AM MST Soren Stoutner wrote:
> For sake of completeness, it was previously discussed that it would be
> possible to patch the Qt WebEngine source to directly look for the
> dictionaries in /usr/share/hunspell-bdic instead of the default upstream
> location.  It is unclear how much ongoing maintenance effort that would
> entail, but it is a possible solution if the symlink is unacceptable.

-- 
Soren Stoutner
so...@stoutner.com


[1] https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/merge_requests/12


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


Bug#1030171: clamav-daemon: clamav-clamonacc.service fails to start

2023-01-31 Thread Ben Goodwin
Package: clamav-daemon
Version: 1.0.0+dfsg-6
Severity: normal
X-Debbugs-Cc: vbgoodw...@gmail.com

systemctl reports that clamav-clamonacc.service failed to start.
Attempting to start the service results in failure.

I have never enabled On-Access Scanning, but systemctl has never
reported that clamav-clamonacc.service failed to start before.

systemctl reports the status as follows:

 clamav-clamonacc.service - ClamAV On-Access Scanner
 Loaded: loaded (/lib/systemd/system/clamav-clamonacc.service; enabled; 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2023-01-31 13:35:23 CST; 
39min ago
   Duration: 16ms
   Docs: man:clamonacc(8)
 man:clamd.conf(5)
 https://docs.clamav.net/
Process: 3031 ExecStartPre=/bin/bash -c while [ ! -S /run/clamav/clamd.ctl 
]; do sleep 1; done (code=exited, status=0/SUCCESS)
Process: 3032 ExecStart=/usr/sbin/clamonacc -F 
--log=/var/log/clamav/clamonacc.log --move=/root/quarantine (code=exited, 
status=2)
   Main PID: 3032 (code=exited, status=2)
CPU: 17ms


-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
AlertExceedsMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "5"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
ConcurrentDatabaseReload = "yes"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
GenerateMetadataJson disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
ScanPE = "yes"
ScanELF = "yes"
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
HeuristicAlerts = "yes"
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
AlertBrokenExecutables disabled
AlertBrokenMedia disabled
AlertEncrypted disabled
StructuredCCOnly disabled
AlertEncryptedArchive disabled
AlertEncryptedDoc disabled
AlertOLE2Macros disabled
AlertPhishingSSLMismatch disabled
AlertPhishingCloak disabled
AlertPartitionIntersection disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ForceToDisk disabled
MaxScanTime = "12"
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeRootUID disabled
OnAccessExcludeUID disabled
OnAccessExcludeUname disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
OnAccessCurlTimeout = "5000"
OnAccessMaxThreads = "5"
OnAccessRetryAttempts disabled
OnAccessDenyOnError disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled
AlgorithmicDetection = "yes"
BlockMax disabled
PhishingAlwaysBlockSSLMismatch disabled
PhishingAlwaysBlockCloak disabled
PartitionIntersection disabled
OLE2BlockMacros disabled
ArchiveBlockEncrypted disabled

Config file: freshclam.conf
---
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
PidFile disabled
DatabaseDirectory = "/var/lib/clamav"
Foreground disabled
Debug disabled
UpdateLogFile = "/var/log/clamav/freshclam.log"
DatabaseOwner = "clamav"
Checks = "24"
DNSDatabaseInfo = "current.cvd.clamav.net"
DatabaseMirror = "db.local.clamav.net", "database.clamav.net"
PrivateMirror disabled
MaxAttempts = 

Bug#1030170: dh-virtualenv: Broken on Python 3.11, AttributeError: module 'inspect' has no attribute 'getargspec'

2023-01-31 Thread Kunal Mehta
Package: dh-virtualenv
Version: 1.2.2-1.2
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: lego...@debian.org

Hi,

Using dh-virtualenv with bookworm's Python 3.11 breaks:

Traceback (most recent call last):
  File "/usr/bin/dh_virtualenv", line 111, in 
sys.exit(main() or 0)
 ^^
  File "/usr/bin/dh_virtualenv", line 60, in main
arguments = inspect.getargspec(DebHelper.__init__).args
^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?

This was fixed upstream last month: 
.

-- System Information:
Debian Release: 11.6
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.81-1.fc32.qubes.x86_64 (SMP w/4 CPU threads)
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 dh-virtualenv depends on:
ii  libjs-sphinxdoc   3.4.3-2
ii  perl  5.32.1-4+deb11u2
ii  python3   3.9.2-3
pn  sphinx-rtd-theme-common   
pn  virtualenv | python3-virtualenv | python3.9-venv  

dh-virtualenv recommends no packages.

dh-virtualenv suggests no packages.



Bug#799358: Angband 4.2.x is out and is Free

2023-01-31 Thread Chris Carr
Right, that's definitely a sign - two people contacting me in the space 
of a couple of weeks! I hereby undertake to update the Angband package 
in 2023, and if I fail I will orphan it. I have re-established contact 
with upstream, who are also keen to see a new package.


CC

On 30/01/2023 17:25, Sven Joachim wrote:

On 2019-12-01 20:34 +, Chris Carr wrote:


I've been meaning to do this for five or six years, so definitely any
year now!

Seriously, I might actually get round to it in 2020, life is getting a
bit easier ...

Life unfortunately got not easier for most of us in 2020 ff., I hope you
have survived the pandemic.  Currently angband upstream is at version
4.2.4, do you think you can package it this year?  If not, it might be
better to let the package go (i.e. orphan it).

Cheers,
Sven


On 28/11/2019 19:27, Matthew Vernon wrote:

Hi,

Any chance of a 4.2 package, please? It's quite a major rewrite of
the game, and it's DFSG-free, so could move this into main, which
would be really good :)

Thanks,

Matthew




Bug#755494: libmpd: diff for NMU version 11.8.90+git20130319-0.1

2023-01-31 Thread Boyuan Yang
X-Debbugs-CC: m...@emillon.org

Hi Etienne,

On Mon, 21 Jul 2014 13:16:23 +0200 Etienne Millon  wrote:
> Package: libmpd
> Version: 0.20.0-1.1
> Severity: normal
> Tags: patch pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for libmpd (versioned as
> 11.8.90+git20130319-0.1). As you are in the low threshold NMU list,
> I'm looking to upload it without delay. Sorry for the large diff, this
> is a new upstream version (reason is explained in #749055).
> 
> A source package can be found here while I am contacting sponsors:
> 
>
http://mentors.debian.net/debian/pool/main/libm/libmpd/libmpd_11.8.90+git20130319-0.1.dsc
> 
> It also seems that you are MIA; if that is confirmed I can adopt the
> package and freshen the packaging: hardening, watch file, S-V, remove
> quilt, etc.

I checked upstream homepage and could not find any link to the git
development repo. Instead, I could only find a released tarball of v11.8.17,
but it seems still earlier than the v11.8.90 you provided. Do you have any
idea about where I could find the upstream git repo that matches the
snapshot you provided?

Thanks,
Boyuan Yang


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


Bug#1030169: chirp: cannot open stock configs

2023-01-31 Thread Noah Engle
Package: chirp
Version: 1:20221106+py3-1
Severity: normal

Dear Maintainer,

Attempting to open a stock config (such as NOAA Weather Alert or US
Calling Frequencies) causes nothing to happen, and outputs this on the
console:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/chirp/wxui/main.py", line 580, in 
_menu_open_stock_config
fn = self.OPEN_STOCK_CONFIG_MENU.FindItemById(event.GetId()).GetLabel()
 
AttributeError: 'MenuItem' object has no attribute 'GetLabel'. Did you 
mean: 'GetAccel'?

The error is identical for any choice of stock config.


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

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

Versions of packages chirp depends on:
ii  python3   3.11.1-2
ii  python3-future0.18.2-6
ii  python3-requests  2.28.1+dfsg-1
ii  python3-serial3.5-1.1
ii  python3-six   1.16.0-4
ii  python3-wxgtk4.0  4.2.0+dfsg-1+b3

chirp recommends no packages.

chirp suggests no packages.

-- no debconf information



Bug#1030168: pesign: CVE-2022-3560: Local privilege escalation on pesign systemd service

2023-01-31 Thread Salvatore Bonaccorso
Source: pesign
Version: 0.112-6
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for pesign.

I'm filling it for now still as severity grave, but feel free to
downgrade if you do not agree on RC level bug. That said, it needs an
unprivileged with access to the pesign user or group.

The code has been substantial refactored upstream, and I think the
issue i still present in the older versions, where the service is
using the pesign-authorize-groups and pesign-authorize-users scripts.

CVE-2022-3560[0]:
| Local privilege escalation on pesign systemd service

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3560
https://www.cve.org/CVERecord?id=CVE-2022-3560
[1] https://www.openwall.com/lists/oss-security/2023/01/31/6
[2] 
https://github.com/rhboot/pesign/commit/d8a8c259994d0278c59b30b41758a8dd0abff998
 

Regards,
Salvatore



Bug#1030058: nvme output misquoting

2023-01-31 Thread Antoine Beaupré
Control: tags -1 +patch

Upstream has a PR pending in:

https://github.com/prometheus-community/node-exporter-textfile-collector-scripts/pull/132.patch

it looks good to me, but I haven't tested it.

a.
-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of speech
because I have nothing to say."
- Edward Snowden



Bug#1030165: python3-aiohttp-jinja2: Update to latest version

2023-01-31 Thread Piotr Ożarowski
Hi,

[Sam Bull, 2023-01-31]
> The package appears to be 1.2, which is starting to look quite out-of-date.
> Would be great to get a new package in time for bookworm.

it FTBFS due to some tests failing, I didn't have enought time to
investigate them, any help appreciated…



Bug#1030167: RFS: bats-file/0.3.0+git20230131-gbba751f-1 [ITP] -- Helper library providing filesystem-related assertions for Bats

2023-01-31 Thread Gioele Barabucci

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: deb...@onerussian.com

Dear mentors,

I am looking for a sponsor for my package "bats-file":

 * Package name : bats-file
   Version  : 0.3.0+git20230131-gbba751f-1
 * URL  : https://github.com/bats-core/bats-file
 * License  : CC0-1.0
 * Vcs  : https://salsa.debian.org/bats-team/bats-file
   Section  : devel

The source builds the following binary packages:

  bats-file - Helper library providing filesystem-related assertions 
for Bats


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


  https://mentors.debian.net/package/bats-file/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/bats-file/bats-file_0.3.0+git20230131-gbba751f-1.dsc


Changes for the initial release:

 bats-file (0.3.0+git20230131-gbba751f-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1029723)

Regards,

--
Gioele Barabucci



Bug#1030164: python3-sqlalchemy: Update to 2.0

2023-01-31 Thread Piotr Ożarowski
Hi,

[Sam Bull, 2023-01-31]
> It would be nice to have sqlalchemy 2.0 packaged in time for bookworm.
> It would be a shame to be stuck with legacy 1.4 for atleast 2.5 years longer.

I will not upload 2.0 to unstable now - there are way too many changes
in the API. There's not enough time to fix all reverse dependencies.
I can upload 2.0 to experimental for now if you're interested.



Bug#1028530: https://www.debian.org/Bugs/ says tag 'forky' exists, bugs.debian.org says it does not

2023-01-31 Thread Paul Gevers

Control: retitle -1 www.debian.org/Bugs should get tags from BTS

Hi,

On Thu, 12 Jan 2023 12:13:41 + Simon McVittie  wrote:

To reproduce:
- look at the list of valid tags in https://www.debian.org/Bugs/
- see that trixie, trixie-ignore, forky and forky-ignore are in the list
- try to tag a bug "+ trixie forky" (I tried to do this in #885563)

Expected result: either tagging a bug + forky succeeds, or the list of
valid tags does not include forky until it becomes relevant.

Actual result: https://www.debian.org/Bugs/ lists forky and forky-ignore,
but when I tried to use the forky tag, the BTS replied:


This is now fixed; I filed bug 1029978 without noticing this bug. 
1029978 got promptly fixed: thanks.



Ideally the web page would receive the list of valid tags from the BTS
instead of having its own idea of what is valid.


I think this remains true. I this case I pinged on IRC for an update of 
the tags and then continued to update the documents. In hindsight that 
wasn't too smart.


Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1030166: acpi-support: Reconsider inclusion in Debian (dropped by Ubuntu)

2023-01-31 Thread Boyuan Yang
Source: acpi-support
Severity: important
Version: 0.143-5.1
Tags: sid
X-Debbugs-CC: jo...@debian.org

Dear Debian acpi-support package maintainer,

As described in
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1970464 , Ubuntu
has ceased the development of acpi-support and dropped it from Ubuntu
archive after Ubuntu 22.04 LTS. Ubuntu claims that its functionality is
fully replaced by other packages.

Please re-analyze current condition of acpi-support in Debian. Thanks!

Best Regards,
Boyuan Yang


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


Bug#1030153: complaining

2023-01-31 Thread Antoine Beaupré
Control: reassign -1 apparmor-profiles-extra

I ended up working around this problem by purging the
apparmor-profiles-extra package and rebooting a bunch of times.

So I don't think this is apparmor per so, it could be *some* -extra
profiles that's breaking things...

a.
-- 
I'm no longer accepting the things I cannot change.
I'm changing the things I cannot accept.
- Angela Davis



Bug#1030165: python3-aiohttp-jinja2: Update to latest version

2023-01-31 Thread Sam Bull
Package: python3-aiohttp-jinja2
Severity: normal
X-Debbugs-Cc: bugs-deb...@sambull.org

Dear Maintainer,

The package appears to be 1.2, which is starting to look quite out-of-date.
Would be great to get a new package in time for bookworm.



Bug#1029578: Forwarded upstream without any reply

2023-01-31 Thread William Desportes
Control: forwarded -1 
https://salsa.debian.org/debian/shunit2/-/commit/513db89d3e5ad321a050fd40130f4c4674adc172

This is what I had sent as my last reply on this subject:
"
Hi Paul and Kate,

I worked a bit more onto this and found out more details, see: 
https://github.com/kward/shunit2/issues/164
I also added more tests for autopkgtests [1] to cover this bug. So let's see 
how upstream reacts (Kate as a CC here).
The output is like in failing packages: 
https://salsa.debian.org/debian/shunit2/-/jobs/3688066#L672
So assertTrue and assertFalse seem to be broken

[1] 
https://salsa.debian.org/debian/shunit2/-/blob/debian/latest/debian/tests/simple-script-tests

William
"

Kate is the upstream author.

For now I need some help, I had no reply

Here is the new autopkgtest for this bug: 
https://salsa.debian.org/debian/shunit2/-/commit/513db89d3e5ad321a050fd40130f4c4674adc172
 


--
William Desportes



Bug#961508: ifupdown: RTNETLINK answers: File exists

2023-01-31 Thread Antoine Beaupré
I have a similar problem with ifupdown on my home server which has
accumulated a rather unfortunate pile of crap...

I am not sure where the problem comes from. I suspect it might be
related to the initrd raising the interfaces before ifup actually runs,
and the RTNETLINK error is about the gateway already being set.

The workaround I found was to just flush the device before the setup:

iface eth0 inet static
# fix RTNETLINK errors on boot see https://bugs.debian.org/961508
pre-up ip addr flush dev eth0 || true
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.1

One might argue this should be the default and that ifup should clear
interfaces before bringing them up, but I'm not familiar enough with
ifup's intricacies to be certain.

Interestingly, I found this command on the raspi forum here:

https://raspberrypi.stackexchange.com/a/51947/32186

a.

-- 
To understand how any society functions you must understand the
relationship between the men and the women
- Angela Davis



Bug#1030164: python3-sqlalchemy: Update to 2.0

2023-01-31 Thread Sam Bull
Package: python3-sqlalchemy
Severity: wishlist
X-Debbugs-Cc: bugs-deb...@sambull.org

Dear Maintainer,

It would be nice to have sqlalchemy 2.0 packaged in time for bookworm.
It would be a shame to be stuck with legacy 1.4 for atleast 2.5 years longer.



Bug#1030163: RFS: ipmiutil/3.1.8-4 -- IPMI management utilities

2023-01-31 Thread Jörg Frings-Fürst
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

   Package name : ipmiutil
   Version  : 3.1.8-4
   Upstream contact : [fill in name and email of upstream]
   URL  : https://sourceforge.net/projects/ipmiutil/
   License  : GPL-2+, GPL-2+ with OpenSSL exception, Zlib, 
  BSD-3-clause, BSD-2-clause, Artistic-2.0
   Vcs  : https://jff.email/cgit/ipmiutil.git
   Section  : utils

The source builds the following binary packages:

  ipmiutil - IPMI management utilities

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

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

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

 dget -x 
https://mentors.debian.net/debian/pool/main/i/ipmiutil/ipmiutil_3.1.8-4.dsc

or from

 git https://jff.email/cgit/ipmiutil.git/?h=release%2Fdebian%2F3.1.8-4


Changes since the last upload:

 ipmiutil (3.1.8-4) unstable; urgency=medium
 .
   * debian/patches/0705-crontab.patch: Fix typo (Closes: #1030120).
   * debian/control:
 - Remove superseded package lsb-base.
 - Remove version information no longer needed.
   * Declare compliance with Debian Policy 4.6.2.0 (No changes needed).
   * debian/copyright:
 - Add year 2023 to myself.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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


Bug#1030159: dpkg: Please add future:+time64 option for y2038 support on 32-bit platforms)

2023-01-31 Thread Helge Deller

Just for the record:
The "tar" package is one example needs LFS- and 64-bit time support to 
sucessfully
run the built-in testcase and as such would be a good user for a new 
"future:+time64"
flag. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026204#42
Helge



Bug#1030162: dselect: [INTL:ru] Russian program translation update

2023-01-31 Thread Yuri Kozlov
Package: dselect
Version: 1.21.20
Severity: wishlist
Tags: l10n patch

Russian program translation update is attached.


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

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


ru.po.gz
Description: application/gzip


Bug#1027448: Bug#1027446: console-setup-l

2023-01-31 Thread Samuel Thibault
Hideki Yamane, le mar. 31 janv. 2023 23:10:24 +0900, a ecrit:
> > These are coming from unifont, so that's where we should be fixing it.
> 
>  Well, Samuel, let me confirm with it.
>  You said those glphs comes from unifont, do those glphs in 
> "Fonts/bdf/unifont.bdf"?
>  If so, it is very different from unifont package one, can we sync those
>  unifont.bdf?

That's what I already implemented in the to-be-released console-setup
version 1.216.

Samuel



Bug#1030160: chromium: FTBFS on arm64/armhf in bullseye-security (V4L issues)

2023-01-31 Thread Andres Salomon
On Tue, 31 Jan 2023 17:53:12 + "Adam D. Barratt" 
 wrote:

> Source: chromium
> Version: 109.0.5414.119-1~deb11u1
> Severity: serious
> Tags: FTBFS
> X-Debbugs-CC: t...@security.debian.org
> Control: affects -1 + security.debian.org
> Control: affects -1 + release.debian.org
>
> Hi,
>
> The most recent chromium upload to bullseye-security fails to build 
on

> arm64 and armhf due to issues with Video4Linux. Relevant-looking log
> output is included below.
>
> Regards,


Thanks! I forgot that it can only be enabled on sid when I merged the 
new release into bullseye. This will get fixed in the next security 
upload.


https://salsa.debian.org/chromium-team/chromium/-/commit/d4bcdc28a9313c76b8bfd91e368366c6c26ceee5



Bug#1030161: roundcube: Fix short date test before and after ICU 72.1

2023-01-31 Thread Amin Bandali
Source: roundcube
Version: 1.6.0+dfsg-1
Severity: normal
Tags: patch

Hello there,

Would you please consider adopting the attached patch (also forwarded
and applied upstream) for fixing the test suite breakage both before
and after ICU 72.1?  Though Debian unstable and testing already have
ICU 72.1, Ubuntu lunar (devel) is still on 71.1, and it would be great
if this failure was fixed such that roundcube would build with ICU
both older or newer than 72.1.

Thanks,
amin

>From 65c93a6d80218b288e5178ba2692da563bb5015e Mon Sep 17 00:00:00 2001
From: Amin Bandali 
Date: Tue, 31 Jan 2023 11:08:23 -0500
Subject: [PATCH] Fix broken short date test with ICU >= 72.1
Forwarded: https://github.com/roundcube/roundcubemail/pull/8904
Applied-Upstream: 5d99ffb766bdb49efb2a8fe9d611f02d5776d0f2
Last-Update: 2023-01-31

* tests/Rcmail/Rcmail.php (test_format_date): Starting with ICU 72.1,
a NARROW NO-BREAK SPACE (NNBSP) is used instead of an ASCII space
before the meridian.  So, check for an NNBSP when using ICU >= 72.1.

References:
* https://icu.unicode.org/download/72
* https://cldr.unicode.org/index/downloads/cldr-42
* https://github.com/unicode-org/icu/pull/2103
---
 tests/Rcmail/Rcmail.php | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/tests/Rcmail/Rcmail.php b/tests/Rcmail/Rcmail.php
index 48879b3a7..4a16b38d4 100644
--- a/tests/Rcmail/Rcmail.php
+++ b/tests/Rcmail/Rcmail.php
@@ -279,7 +279,14 @@ class Rcmail_Rcmail extends ActionTestCase
 $this->assertSame(' Mon', $rcmail->format_date($date, ' D'));
 $this->assertSame('D Monday', $rcmail->format_date($date, '\\D l'));
 $this->assertSame('Jun June', $rcmail->format_date($date, 'M F'));
-$this->assertSame('6/1/20, 12:20 PM', $rcmail->format_date($date, 
'x'));
+$date_x = '6/1/20, 12:20 PM';
+if (defined('INTL_ICU_VERSION')
+  && version_compare(INTL_ICU_VERSION, '72.1', '>=')) {
+// Starting with ICU 72.1, a NARROW NO-BREAK SPACE (NNBSP)
+// is used instead of an ASCII space before the meridian.
+$date_x = '6/1/20, 12:20 PM';
+}
+$this->assertSame($date_x, $rcmail->format_date($date, 'x'));
 $this->assertSame('1591014030', $rcmail->format_date($date, 'U'));
 $this->assertSame('2020-06-01T12:20:30+00:00', 
$rcmail->format_date($date, 'c'));
 }
-- 
2.37.2



Bug#1025642: RFS: d11amp/0.61-1 [ITP] -- Simple MP3 player

2023-01-31 Thread James Addison
Package: sponsorship-requests
Followup-For: Bug #1025642

The copyright file from the latest package on mentors.debian.net is clearer,
thanks!

However: I think we should still clarify that 'default_theme.c' is _also_
covered by the default-applied BSD-2-Clause license terms of the package.

The Debian copyright file format[1] supports multiple licenses within a single
file stanza, so my suggestion would be:

  - Move the 'BSD-2-Clause' text into a standalone[2] license field at the end
of the copyright file

  - Update the License field for 'default_theme.c' to 'CC0 and BSD-2-Clause'

Basically what that is trying to communicate to anyone who modifies the file(s)
in future is: please continue to convey the included Creative Commons Zero and
BSD two-clause licenses when distributing modifications.

That might confuse them at first, but the 'Comment' field you added should
provide some help for that.

And, fortunately, there is not any conflict between BSD-2-Clause and CC0
licensing as far as I'm aware.  Quoting the FSF on license compatibility[3]:

  "We say that a license A subsumes license B when compliance with license A 
implies compliance with license B."

  "The BSD licenses subsume the Expat, X11 and ISC licenses and CC0."

(to which you might ask: why mention both?  well, I think that in combination
with the comment, the presence of both clarifies the intended licensing for the
files that are produced from the code)

[1] - 
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-field

[2] - 
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#stand-alone-license-stanza

[3] - https://www.gnu.org/licenses/license-compatibility.html



Bug#1030153: complaining

2023-01-31 Thread Antoine Beaupré
so something is happening with apparmor here. it looks like profile are
"piling up" in some way, with something like this:

/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/sudo//null-/usr/bin/apt//null-/usr/bin/dash//null-/usr/bin/etckeeper//null-/etc/etckeeper/pre-install.d/50uncommitted-changes//null-/usr/bin/etckeeper//null-/usr/bin/perl

i have hundreds of such aa profiles piled up, and i have *just*
rebooted. so this may not just be a problem with journalctl but a more
general problem with my apparmor configuration...

here's the output of aa-status:

anarcat@marcos:apparmor.d[4]$ sudo aa-status
apparmor module is loaded.
436 profiles are loaded.
25 profiles are in enforce mode.
   /usr/bin/freshclam
   /usr/bin/man
   /usr/bin/pidgin
   /usr/bin/pidgin//sanitized_helper
   /usr/bin/totem
   /usr/bin/totem-audio-preview
   /usr/bin/totem-video-thumbnailer
   /usr/bin/totem//sanitized_helper
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/sbin/chronyd
   /{,usr/}sbin/dhclient
   apt-cacher-ng
   docker-default
   libvirtd
   libvirtd//qemu_bridge_helper
   lsb_release
   man_filter
   man_groff
   nvidia_modprobe
   nvidia_modprobe//kmod
   system_tor
   unbound
   virt-aa-helper
411 profiles are in complain mode.
   /bin/netstat
   /etc/cron.daily/logrotate
   /etc/cron.daily/slocate.cron
   /etc/cron.daily/tmpwatch
   /sbin/dhcpcd
   /sbin/portmap
   /sbin/resmgrd
   /sbin/rpc.lockd
   /sbin/rpc.statd
   /usr/NX/bin/nxclient
   /usr/X11R6/bin/acroread
   /usr/bin/apropos
   /usr/bin/evolution-2.10
   /usr/bin/fam
   /usr/bin/gaim
   /usr/bin/irssi
   /usr/bin/mlmmj-bounce
   /usr/bin/mlmmj-maintd
   /usr/bin/mlmmj-make-ml.sh
   /usr/bin/mlmmj-process
   /usr/bin/mlmmj-recieve
   /usr/bin/mlmmj-send
   /usr/bin/mlmmj-sub
   /usr/bin/mlmmj-unsub
   /usr/bin/opera
   /usr/bin/passwd
   /usr/bin/procmail
   /usr/bin/skype
   /usr/bin/spamc
   /usr/bin/svnserve
   /usr/bin/wireshark
   /usr/bin/xfs
   /usr/lib/GConf/2/gconfd-2
   /usr/lib/RealPlayer10/realplay
   /usr/lib/bonobo/bonobo-activation-server
   /usr/lib/evolution-data-server/evolution-data-server-1.10
   /usr/lib/firefox/firefox.sh
   /usr/lib/firefox/mozilla-xremote-client
   /usr/lib/firefox{,-[0-9]*}/firefox{,*[^s][^h]}
   /usr/lib/postfix/anvil
   /usr/lib/postfix/bounce
   /usr/lib/postfix/cleanup
   /usr/lib/postfix/discard
   /usr/lib/postfix/error
   /usr/lib/postfix/flush
   /usr/lib/postfix/lmtp
   /usr/lib/postfix/local
   /usr/lib/postfix/master
   /usr/lib/postfix/nqmgr
   /usr/lib/postfix/oqmgr
   /usr/lib/postfix/pickup
   /usr/lib/postfix/pipe
   /usr/lib/postfix/proxymap
   /usr/lib/postfix/qmgr
   /usr/lib/postfix/qmqpd
   /usr/lib/postfix/scache
   /usr/lib/postfix/showq
   /usr/lib/postfix/smtp
   /usr/lib/postfix/smtpd
   /usr/lib/postfix/spawn
   /usr/lib/postfix/tlsmgr
   /usr/lib/postfix/trivial-rewrite
   /usr/lib/postfix/verify
   /usr/lib/postfix/virtual
   /usr/lib64/GConf/2/gconfd-2
   /usr/sbin/dhcpd
   /usr/sbin/httpd2-prefork
   /usr/sbin/httpd2-prefork//DEFAULT_URI
   /usr/sbin/httpd2-prefork//HANDLING_UNTRUSTED_INPUT
   /usr/sbin/imapd
   /usr/sbin/in.fingerd
   /usr/sbin/in.ftpd
   /usr/sbin/in.ntalkd
   /usr/sbin/ipop2d
   /usr/sbin/ipop3d
   /usr/sbin/lighttpd
   /usr/sbin/oidentd
   /usr/sbin/popper
   /usr/sbin/postalias
   /usr/sbin/postdrop
   /usr/sbin/postmap
   /usr/sbin/postqueue
   /usr/sbin/sendmail
   /usr/sbin/sendmail.postfix
   /usr/sbin/sendmail.sendmail
   /usr/sbin/spamd
   /usr/sbin/spamd//null-/usr/bin/pwd
   /usr/sbin/spamd//null-/usr/bin/pyzor
   /usr/sbin/squid
   /usr/sbin/sshd
   /usr/sbin/sshd//AUTHENTICATED
   /usr/sbin/sshd//EXEC
   /usr/sbin/sshd//PRIVSEP
   /usr/sbin/sshd//PRIVSEP_MONITOR
   /usr/sbin/sshd//null-/usr/bin/bash
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-cache
   
/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-cache//null-/usr/bin/dpkg
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-file
   
/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-file//null-/usr/bin/apt-get
   
/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-file//null-/usr/bin/apt-get//null-/usr/bin/dpkg
   
/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-file//null-/usr/bin/grep
   
/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-file//null-/usr/bin/xargs
   
/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt-file//null-/usr/bin/xargs//null-/usr/lib/apt/apt-helper
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/apt//null-/usr/bin/dpkg
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/cat
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/cksum
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/cut
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/dircolors
   /usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/dpkg
   
/usr/sbin/sshd//null-/usr/bin/bash//null-/usr/bin/dpkg//null-/usr/

Bug#999485: firmware-brcm80211: Please add brcmfmac43456-sdio.* files for wifi support in Raspberry p400

2023-01-31 Thread Salvatore Bonaccorso
Hi Diederik, hi Gunnar,

On Mon, Dec 05, 2022 at 08:02:04PM +0100, Diederik de Haas wrote:
> Control: retitle -1 Please add brcmfmac43456-sdio.* files as it's not just 
> used in RPi devices
> 
> On 10 Nov 2022 11:40:06 +0100 Diederik de Haas  wrote:
> > On Sat, 9 Apr 2022 17:52:00 -0500 Gunnar Wolf  wrote:
> > > Please note I'm currenlty shipping the required files in
> > > raspi-firmware -- I believe their right place is in
> > > firmware-brcm80211, so please just ping me (or better, raise a bug on
> > > raspi-firmware) whent they are added to this package.
> > 
> > I opened https://bugs.debian.org/1023741 for it.
> 
> >From https://bugs.debian.org/1023741:
> > I completely agree that firmware-brcm80211 is the right place and
> > raspi-firmware is the wrong place as this is about firmware for wifi
> > devices which are f.e. also used on Pine64 devices.
> 
> Gunnar indicated that he's willing to remove the files from raspi-firmware,
> but they still need to be added to firmware-brcm80211, so pretty please?

So I looked at this, and don't think the firmware-nonfree packages
should take it over. Why? The firmware files are not part of
linux-firmware.git . 

Would they fit into a separate source package not associated with
raspi-config?

The other option is that they get included upstream in
linux-firmware.git by upstream? 

Regards,
Salvatore



Bug#1027448: Bug#1027446: console-setup-l

2023-01-31 Thread Hideki Yamane
 =?utf-8?Q?inux=3A_Super-Ugly_glyphs_inside_Greek-Fixed16=2Epsf=2Egz_for_c?=
  =?utf-8?B?aGFyYWN0ZXJzIM6zIM68IM62IM6+?= (with solution)
Message-Id: <20230131231024.f1526c8797f5f69ed3ea6...@iijmio-mail.jp>
In-Reply-To: <20221231163959.j2pufq32lwlvbysm@begin>
X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi,

On Sat, 31 Dec 2022 17:39:59 +0100 Samuel Thibault  wrote:
> Pavlos Gkesos, le sam. 31 déc. 2022 18:06:20 +0200, a ecrit:
> > Greek characters μ ξ ζ γ appears UGLY.
> > I fix them and I provide the new Greek-Fixed16.psf.gz
> 
> These are coming from unifont, so that's where we should be fixing it.

 Well, Samuel, let me confirm with it.
 You said those glphs comes from unifont, do those glphs in 
"Fonts/bdf/unifont.bdf"?
 If so, it is very different from unifont package one, can we sync those
 unifont.bdf?



-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp



Bug#610882: gpm: Unclear messages in syslog

2023-01-31 Thread Helge Kreutzmann
Hello Jakub,
On Tue, Jan 31, 2023 at 05:54:38PM +0100, Jakub Wilk wrote:
> * Helge Kreutzmann , 2011-01-23 18:23:
> > In the syslog I see messages like:
> > /usr/sbin/gpm[3519]: Request on 8 (console 10)
> 
> Another annoyed user here.

Well, I'm just reading my syslog and either something need fixing or
something needs filtering out …

> This seems to be emitted in src/daemon/processrequest.c, at the beginning of
> function processRequest.
> 
> To reproduce, just run mc(1).
> 
> > If these messages are harmless
> 
> As far as can I see, they are harmless.

I believe so, too. These are filtered out for a really long time on my
systems.

Greetings

  Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature


Bug#1030000: fontconfig: after upgrade from 2.13.1-4.5 to 2.14.1-3 subpixel is enabled

2023-01-31 Thread Andreas Henriksson
Hello Thorsten Glaser,

Thanks for your bug report.

On Mon, Jan 30, 2023 at 03:32:02AM +0100, Thorsten Glaser wrote:
> Package: fontconfig
> Version: 2.14.1-3
> Severity: serious
> Justification: Policy 10.7.3
> X-Debbugs-Cc: t...@mirbsd.de
> 
> > * local changes must be preserved during a package upgrade, and
> 
> After an upgrade, etckeeper reports that
> /etc/fonts/conf.d/10-sub-pixel-rgb.conf
> shows up again, despite the local admin
> choice to not have blurry fonts.

Ouch, no relevant changes to maintainer scripts has been done.
Have you experienced this problem in previous upgrades?
Can you reproduce the problem at all?

> 
> Running dpkg-reconfigure -plow fontconfig-config
> shows that the debconf database correctly remembers
> the admin-provided setting (subpixel disabled was
> pre-selected),

By 'disabled' I assume you mean 'Never', right?

> and just pressing Enter on every
> question makes it remove that file, 

Did it also create 10-no-sub-pixel.conf ?
(Which would be consistent with 'Never'.
If neither file exists, that's the 'Automatic' option
which is also the default.)

> so I believe that some maintainer script errorneously forcibly
> creates that file overriding local configuration.

Is there any chance you can try to find some additional information
on what happened on your system?

It sounds weird that you would end up with 'Always' option somehow
when default is 'Automatic' and you supposedly selected 'Never'.


The relevant code is here:
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.postinst/#L93-L116

Note that this is protected by:
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.postinst/#L32
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.postinst/#L13-L23
(Thus it should not have run at all on upgrade.)

See also:
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.config/#L49-L64


Possibly 'Always' option could have come from here:
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.config/#L56
But then again, the initial/re-configure should not have been run at all
because of
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.postinst/#L32
as mentioned earlier.



Regards,
Andreas Henriksson



  1   2   >