Bug#1052807: lmod: FTBFS: testsuite fails if 'hostname -f' fails
tags 1052807 - ftbfs thanks El 18/10/24 a las 12:16, Andreas Beckmann escribió: Lowering the severity since I don't consider an environment without working 'hostname -f' a proper build environment. Hello. Actually, this is a bug that Lucas fixed in the collab-qa-tools repository here: https://salsa.debian.org/lucas/collab-qa-tools/-/commit/6d75fa24ecf5f2c9e1378e9d0804190ca56fec82 and was refined a little bit here: https://salsa.debian.org/lucas/collab-qa-tools/-/commit/182d02914edc58fd14293ae9bedb022d2e8e54cb Those fixes are from late 2023-10 and this bug report was filed in late 2023-09, so I'm almost sure that using the current framework, this bug would not have been reported at all. So, I'm dropping the ftbfs tag because IMO this is not a "proper" FTBFS bug. Sorry that this package was undeservedly removed from testing because of this bug. Should not really have happened. [ I'm keeping the bug open because you said it happens in Salsa, but maybe it could be reassigned to some salsa pseudopackage, if any. The problem in AWS was in the images (or their default behavior), and the collab-qa-tools fix was just a workaround. Maybe the nature of the problem in Salsa is similar ]. Thanks.
Bug#1085334: dbusada: calls dbus_get_local_machine_id() which has bad error-handling
Source: dbusada Version: 0.6.2-6 Severity: normal Tags: upstream Based on my limited understanding of the Ada language, it looks as though dbusada calls dbus_get_local_machine_id(), which has no good mechanism for reporting an error, and therefore will spam warnings to standard error (and possibly crash) if the D-Bus machine ID has not been set up correctly. This function should be considered deprecated. Please prefer to use dbus_try_get_local_machine_id(), which takes a DBusError parameter and therefore can be used to report errors in whatever way is considered to be most appropriate by the caller. This has been available in upstream stable releases since dbus 1.12.0 (2017). Thanks, smcv
Bug#1082683: marked as done (kxd: FTBFS: certificate is valid for *, not localhost)
Control: fixed 1082683 0.17-1
Bug#1085348: upstream-ontologist: FTBFS: error[E0432]: unresolved import `debian_copyright::lossless`
Package: src:upstream-ontologist
Version: 0.1.44-1
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --buildsystem=pybuild --with=python3
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mv Cargo.lock Cargo.lock.saved
dh_auto_build
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12/build/upstream_ontologist
copying py/upstream_ontologist/__init__.py ->
/<>/.pybuild/cpython3_3.12/build/upstream_ontologist
copying py/upstream_ontologist/vcs.py ->
/<>/.pybuild/cpython3_3.12/build/upstream_ontologist
copying py/upstream_ontologist/guess.py ->
/<>/.pybuild/cpython3_3.12/build/upstream_ontologist
copying py/upstream_ontologist/_upstream_ontologist.pyi ->
/<>/.pybuild/cpython3_3.12/build/upstream_ontologist
copying py/upstream_ontologist/py.typed ->
/<>/.pybuild/cpython3_3.12/build/upstream_ontologist
running build_ext
running build_rust
Locking 433 packages to latest compatible versions
Adding bitflags v1.3.2 (latest: v2.6.0)
Adding cfg-if v0.1.10 (latest: v1.0.0)
Adding syn v1.0.109 (latest: v2.0.77)
Adding toml v0.5.11 (latest: v0.8.19)
cargo rustc --lib --message-format=json-render-diagnostics --manifest-path
upstream-ontologist-py/Cargo.toml --release -v --features pyo3/extension-module
debcargo extension-module --crate-type cdylib --
warning: /<>/Cargo.toml: unused manifest key: package.exlcude
Compiling proc-macro2 v1.0.86
Running `rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/proc-macro2-1.0.86/build.rs --error-format=json
--json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg
'feature="default"' --cfg 'feature="proc-macro"' --check-cfg 'cfg(docsrs)' --check-cfg 'cfg(feature, values("default",
"nightly", "proc-macro", "span-locations"))' -C metadata=07ed13e6c1e4e0a7 -C extra-filename=-07ed13e6c1e4e0a7 --out-dir
/<>/target/release/build/proc-macro2-07ed13e6c1e4e0a7 -C strip=debuginfo -L dependency=/<>/target/release/deps
--cap-lints allow`
Running
`/<>/target/release/build/proc-macro2-07ed13e6c1e4e0a7/build-script-build`
[...]
Compiling configparser v3.0.3
Running `rustc --crate-name configparser --edition=2021 /usr/share/cargo/registry/configparser-3.0.3/src/lib.rs
--error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib
--emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --check-cfg 'cfg(docsrs)' --check-cfg 'cfg(feature,
values("async-std", "indexmap"))' -C metadata=3f2003b5c3330bec -C extra-filename=-3f2003b5c3330bec
--out-dir /<>/target/release/deps -C strip=debuginfo -L
dependency=/<>/target/release/deps --cap-lints allow`
Running `rustc --crate-name upstream_ontologist --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="cargo"' --cfg 'feature="debcargo"' --cfg 'feature="debian"' --cfg 'feature="default"' --cfg 'feature="dist-ini"' --cfg 'feature="git-config"' --cfg 'feature="launchpad"' --cfg 'feature="opam"' --cfg 'feature="pyo3"' --cfg 'feature="pyproject-toml"' --cfg 'feature="python-pkginfo"' --cfg 'feature="r-description"' --cfg 'feature="setup-cfg"' --check-cfg 'cfg(docsrs)' --check-cfg 'cfg(feature, values("cargo", "cli", "debcargo",
"debian", "default", "dist-ini", "git-config", "launchpad", "opam", "pyo3", "pyproject-toml", "python-pkginfo", "r-description", "setup-cfg"))' -C metadata=dd70b7ac2c732ca7 -C extra-filename=-dd70b7ac2c732ca7 --out-dir /<>/target/release/deps -C strip=debuginfo -L dependency=/<>/target/release/deps --extern breezyshim=/<>/target/release/deps/libbreezyshim-78227d7d396a7cb2.rmeta --extern chrono=/<>/target/release/deps/libchrono-3744e702965ffd4d.rmeta --extern configparser=/<>/target/release/deps/libconfigparser-3f2003b5c3330bec.rmeta --extern
debbugs=/<>/target/release/deps/libdebbugs-2941ef845ca22f85.rmeta --extern debcargo=/<>/target/release/deps/libdebcargo-9f5853211008abf1.rmeta --extern debian_changelog=/<>/target/release/deps/libdebian_changelog-8177175a389f9edc.rmeta --extern debian_control=/<>/target/release/deps/libdebian_control-6cf5680c1d7f6722.rmeta --extern debian_copyright=/<>/target/release/deps/libdebian_copyright-3b8f2cf89d967a2b.rmeta --extern debian_watch=/<>/target/release/deps/libdebian_watch-8a3f227bfc19e753.rmeta --extern distro_info=/<>/target/release/deps/libdistro_info-6da18eba494
Bug#1085349: knot dies on start, symbol lookup error
Package: knot Verdion 3.4.1-2 Severity: critical When starting knot in Debian Unstable, I get the following error message: /usr/sbin/knotc: symbol lookup error: /usr/sbin/knotc: undefined symbol: knot_tls_session_available Also: pawal@dns:/usr/sbin$ ./knotd ./knotd: symbol lookup error: ./knotd: undefined symbol: knot_tls_session_available pawal@dns:/usr/sbin$ ./knotc ./knotc: symbol lookup error: ./knotc: undefined symbol: knot_tls_session_available
Bug#1085321: advocate: Python SyntaxWarning
Source: advocate Version: 1.0.0-6 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/a/advocate.html Setting up python3-advocate (1.0.0-6) ... /usr/lib/python3/dist-packages/advocate/api.py:99: SyntaxWarning: invalid escape sequence '\*' """Sends a GET request. /usr/lib/python3/dist-packages/advocate/api.py:112: SyntaxWarning: invalid escape sequence '\*' """Sends a OPTIONS request. /usr/lib/python3/dist-packages/advocate/api.py:125: SyntaxWarning: invalid escape sequence '\*' """Sends a HEAD request. /usr/lib/python3/dist-packages/advocate/api.py:138: SyntaxWarning: invalid escape sequence '\*' """Sends a POST request. /usr/lib/python3/dist-packages/advocate/api.py:152: SyntaxWarning: invalid escape sequence '\*' """Sends a PUT request. /usr/lib/python3/dist-packages/advocate/api.py:165: SyntaxWarning: invalid escape sequence '\*' """Sends a PATCH request. /usr/lib/python3/dist-packages/advocate/api.py:178: SyntaxWarning: invalid escape sequence '\*' """Sends a DELETE request.
Bug#1085331: auto-07p: Python SyntaxWarning
Source: auto-07p
Version: 0.9.2+dfsg-3
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/a/auto-07p.html
Setting up python3 (3.12.5-1) ...
/usr/lib/auto-07p/python/auto/interactiveBindings.py:220:
SyntaxWarning: invalid escape sequence '\s'
pre = re.match('^(\s*)(.*)',line).groups()[0]
/usr/lib/auto-07p/python/auto/interactiveBindings.py:373:
SyntaxWarning: invalid escape sequence '\.'
"--ignore-matching-lines='.*ab\.o.*'",
/usr/lib/auto-07p/python/auto/interactiveBindings.py:374:
SyntaxWarning: invalid escape sequence '\.'
"--ignore-matching-lines='.*cir\.o.*'",
/usr/lib/auto-07p/python/auto/interactiveBindings.py:375:
SyntaxWarning: invalid escape sequence '\.'
"--ignore-matching-lines='.*wav\.o.*'",
/usr/lib/auto-07p/python/auto/interactiveBindings.py:439:
SyntaxWarning: invalid escape sequence '\#'
cfg.PromptManager.out_template="Out[\#]: "
/usr/lib/auto-07p/python/auto/interactiveBindings.py:464:
SyntaxWarning: invalid escape sequence '\#'
'-po','Out[\#]: ',
/usr/lib/auto-07p/python/auto/parseD.py:84: SyntaxWarning: invalid
escape sequence '\s'
result = re.findall("Eigenvalue\s.*",solution)
/usr/lib/auto-07p/python/auto/parseD.py:90: SyntaxWarning: invalid
escape sequence '\s'
result = re.findall("Multiplier\s.*",solution)
/usr/lib/auto-07p/python/auto/runAUTO.py:118: SyntaxWarning: invalid
escape sequence '\*'
value = re.findall("(Saved as|Appended to) \*\.(\w*)",text)
/usr/lib/auto-07p/python/auto/runDemo.py:32: SyntaxWarning: invalid
escape sequence '\.'
"--ignore-matching-lines='.*ab\.o.*'",
Bug#734190: [Pkg-tcltk-devel] Bug#734190: Bug of the Day contribution: Fix for bug #734190 and modernising the package
Hi Sergei, Am Fri, Oct 18, 2024 at 11:59:46AM +0300 schrieb Sergei Golovan: > > I have added you to the members of tcltk-team on salsa. Now you can merge > the request for tclodbc yourself. Thank you for the work! Merged and uploaded to unstable. Thank you Andreas. -- https://fam-tille.de
Bug#1085193:
Works now with 0.3.21 in Debian Unstable. Thanks for the quick response!
Bug#1085092: libglib2.0-0: segfault after installing shared-mime-info from Homebrew
On 18-10-2024 19:44, Simon McVittie wrote:
Does this happen for literally any JSON file (for example
`echo "{}" > object.json`) or does the JSON file that is required to
reproduce the crash have non-trivial contents?
Any non-empty file that ends in ".json" causes a segfault. It doesn't
even have to be valid json.
Is there a single file or combination of files that reproduce this without
installing arbitrary software from outside Debian?
Yes! I've attached a minimal version of freedesktop.org.xml that causes
a segfault. It seems it has something to do with the interaction between
multiple mime-type definitions, since the problem goes away after
removing a single json or javascript related mime-type.
Best,
Lennart
http://www.freedesktop.org/standards/shared-mime-info";>
]>
http://www.freedesktop.org/standards/shared-mime-info";>
ECMAScript program
ECMAScript 程式
ECMAScript 程序
Chương trình ECMAScript
програма мовою ECMAScript
ECMAScript programı
ECMAScript-program
програм ЕЦМАСкрипте
program ECMAScript
Programska datoteka ECMAScript
ECMAScript වැඩසටහන
Program ECMAScript
Программа ECMAScript
Program ECMAScript
Programa ECMAScript
programa ECMAScript
Pogram ECMAScript
programa ECMAEscript
ECMAScript-program
ECMAScript-programma
ECMAScript-program
ECMAScript programma
ECMAScript programa
ECMAScript 프로그램
ECMAScript программасы
ECMAScript პროგრამა
ECMAScript プログラム
Programma ECMAScript
ECMAScript forrit
Program ECMAScript
Programma ECMAScript
ECMAScript program
ECMAScript program
תכנית EMCAScript
programa en ECMAScript
ríomhchlár ECMAScript
program ECMAScript
programme ECMAScript
ECMAScript forrit
ECMAScript-ohjelma
ECMAScript programa
programa en ECMAScript
ECMAScript program
Πρόγραμμα ECMAScript
ECMAScript-Programm
ECMAScript-program
program v jazyce ECMAScript
programa ECMAScript
Програма — ECMAScript
Prahrama ECMAScript
праграма ECMAScript
برنامج ECMAScript
ECMAScript-program
JSON document
JSON 文件
JSON 文档
документ JSON
JSON belgesi
JSON-dokument
ЈСОН документ
dokument JSON
Dokument JSON
JSON ලේඛනය
Dokument JSON
Документ JSON
Documento JSON
documento JSON
Dokument JSON
document JSON
JSON-document
JSON 문서
JSON құжаты
JSON ドキュメント
Documento JSON
JSON skjal
Dokumen JSON
Documento JSON
JSON dokumentum
JSON dokument
מסמך JSON
Documento JSON
cáipéis JSON
document JSON
document JSON
JSON-asiakirja
JSON dokumentua
documento JSON
JSON document
Έγγραφο JSON
JSON-Dokument
JSON-dokument
dokument JSON
document JSON
Документ — JSON
дакумент JSON
Documentu JSON
مستند JSON
JSON-dokument
JSON
JavaScript Object Notation
JSON5 document
документ JSON5
JSON5-dokument
Документ JSON5
Dokument JSON5
documento JSON5
JSON5-Dokument
JSON5
JavaScript Object Notation 5
JRD document
JRD 文件
JRD 文档
документ JRD
JRD belgesi
JRD-dokument
ЈРД документ
dokument JRD
Dokument JRD
JRD ලේඛනය
Dokument JRD
Документ JRD
Documento JRD
doxumento JRD
Dokument JRD
document JRD
JRD-document
JRD 문서
JRD құжаты
JRD ドキュメント
Documento JRD
JRD skjal
Dokumen JRD
Documento JRD
JRD dokumentum
JRD dokument
מסמך JRD
Documento JRD
cáipéis JRD
document JRD
document JRD
JRD-asiakirja
JRD dokumentua
documento JRD
JRD document
Έγγραφο JRD
JRD-Dokument
JRD-dokument
dokument JRD
document JRD
Документ — JRD
дакумент JRD
Documentu JRD
مستند JRD
JRD-dokument
JRD
JSON Resource Descriptor
JSON patch
JSON 修補檔
JSON 补丁
латка JSON
JSON yaması
JSON patch
ЈСОН закрпа
arnë JSON
Popravek JSON
JSON පැච්
Záplata JSON
Патч JSON
Patch JSON
patch JSON
Łata JSON
correctiu JSON
JSON-patch
JSON 패치
JSON өзгерісі
JSON パッチ
Patch JSON
JSON kóðabót
Patch JSON
Patch JSON
JSON javítócsomag
JSON zakrpa
טלאי JSON
Parche JSON
paiste JSON
blec JSON
correctif JSON
JSON-paikkatiedosto
JSON adabakia
parche en JSON
JSON patch
JSON-Patch
JSON-rettelse
cesta JSON
pedaç de JSON
Кръпка — JSON
патч JSON
رقعة JSON
JSON
JavaScript Object Notation
JSON-LD document
JSON-LD 文件
JSON-LD 文档
документ JSON-LD
JSON-LD belgesi
JSON-LD-dokument
ЈСОН-ЛД документ
dokument JSON-LD
Dokument JSON-LD
JSON-LD ලේඛනය
Dokument JSON-LD
Документ JSON-
Bug#1085388: ITP: einops -- Flexible and powerful tensor operations for readable and reliable code.
Package: wnpp Severity: wishlist Owner: Mo Zhou X-Debbugs-Cc: debian-de...@lists.debian.org * Package name : einops * URL : https://einops.rocks * License : MIT/Expat Programming Lang: Python Description : Flexible and powerful tensor operations for readable and reliable code. Flexible and powerful tensor operations for readable and reliable code. Supports numpy, pytorch, tensorflow, jax, and others. Thank you for using reportbug
Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost
On Fri, Oct 18, 2024 at 08:04:59PM +0200, Paul Gevers wrote: > > The sysctl is namespaced, so it should suffice to set it in the > > testbed container. > > So, this should be done by src:backuppc then. That'll work, obviously, but I do think it should be considered system-wide on the debci lxc environment. On a common Debian installation, this isn't something a package maintainer or user should need to care about, as the defaults should result in ping working out of the box. noah
Bug#1085391: python3-google-api-python-client has an undeclared file conflict
Package: python3-google-api-python-client Version: 2.149.0-1.1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + python3-googleapi python3-google-api-python-client has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/python3/dist-packages/apiclient/__init__.py * /usr/lib/python3/dist-packages/googleapiclient/__init__.py * /usr/lib/python3/dist-packages/googleapiclient/_auth.py * /usr/lib/python3/dist-packages/googleapiclient/_helpers.py * /usr/lib/python3/dist-packages/googleapiclient/channel.py * /usr/lib/python3/dist-packages/googleapiclient/discovery.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/__init__.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/appengine_memcache.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/base.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/file_cache.py * /usr/lib/python3/dist-packages/googleapiclient/errors.py * /usr/lib/python3/dist-packages/googleapiclient/http.py * /usr/lib/python3/dist-packages/googleapiclient/mimeparse.py * /usr/lib/python3/dist-packages/googleapiclient/model.py * /usr/lib/python3/dist-packages/googleapiclient/sample_tools.py * /usr/lib/python3/dist-packages/googleapiclient/schema.py are contained in the packages * python3-google-api-python-client/2.149.0-1.1 as present in unstable * python3-googleapi * 1.7.11-4 as present in bullseye * 1.7.12-1 as present in bookworm The files * /usr/lib/python3/dist-packages/apiclient/__init__.py * /usr/lib/python3/dist-packages/googleapiclient/__init__.py * /usr/lib/python3/dist-packages/googleapiclient/_auth.py * /usr/lib/python3/dist-packages/googleapiclient/_helpers.py * /usr/lib/python3/dist-packages/googleapiclient/channel.py * /usr/lib/python3/dist-packages/googleapiclient/discovery.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/__init__.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/appengine_memcache.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/base.py * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/abusiveexperiencereport.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/acceleratedmobilepageurl.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/accessapproval.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/accesscontextmanager.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/accesscontextmanager.v1beta.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/acmedns.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/addressvalidation.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adexchangebuyer.v1.2.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adexchangebuyer.v1.3.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adexchangebuyer.v1.4.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adexchangebuyer2.v2beta1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adexperiencereport.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admin.datatransfer_v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admin.datatransferv1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admin.directory_v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admin.directoryv1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admin.reports_v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admin.reportsv1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admob.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/admob.v1beta.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adsense.v2.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adsensehost.v4.1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adsenseplatform.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/adsenseplatform.v1alpha.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/advisorynotifications.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/aiplatform.v1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/aiplatform.v1beta1.json * /usr/lib/python3/dist-packages/googleapiclient/discovery_cache/documents/airquality.v1.j
Bug#1085389: python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py
Package: python3-pyvkfft-cuda Version: 2024.1.4+ds1-3 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + python3-pyvkfft python3-pyvkfft-cuda has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/pyvkfft/cuda.py is contained in the packages * python3-pyvkfft * 2022.1.1-3+b1 as present in bookworm * 2024.1.2+ds1-2~bpo12+1 as present in bookworm-backports * python3-pyvkfft-cuda/2024.1.4+ds1-3 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Bug#1085390: gkrellm-thinkbat FTCBFS: hard codes the build architecture pkg-config
Source: gkrellm-thinkbat Version: 0.2.3-1 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs gkrellm-thinkbat fails to cross build from source, because the upstream Makefile hard codes the build architecture pkg-config and thus fails to locate dependencies that are only requested for the host architecture by Build-Depends. I'm attaching a patch for your convenience. Helmut --- gkrellm-thinkbat-0.2.3.orig/Makefile +++ gkrellm-thinkbat-0.2.3/Makefile @@ -1,8 +1,9 @@ VERSION = 0.2.3 CC = gcc +PKG_CONFIG ?= pkg-config CPPFLAGS += CFLAGS += -I. -Wall -pedantic -O2 -INCLUDE = `pkg-config gtk+-2.0 --cflags` -fPIC -DVERSION=\"$(VERSION)\" +INCLUDE = `$(PKG_CONFIG) gtk+-2.0 --cflags` -fPIC -DVERSION=\"$(VERSION)\" LDFLAGS += -shared -lm INSTALL ?= install INSTALLDIR = $(DESTDIR)/usr/lib/gkrellm2/plugins/
Bug#1085370: disable unmerged-bin taint (when /bin and /sbin not merged)
On Fri, Oct 18, 2024 at 17:51:21 +0100, Luca Boccassi wrote: > They cannot be disabled, there are no options to do so, feel free to > send a patch upstream to implement such a feature if you want to do so An option doesn't seem like the right way to handle this. It would complicate configuration parsing and documentation for little benefit, and then we'd still need the package to ship a Debian-specific drop-in or something like that. The warning itself has no obvious benefit to users, given that almost everyone seeing it will be using a distribution and thus be un-able to fix it (without breaking their package managers). This makes me think that the feature exists mostly to pressure distributors, and that an up-stream discussion is not likely to be productive. I conclude that it's Debian that needs to make the decision: either merge the directories as the systemd developers want, or carry a patch to disable the warning. Having a Debian package warn that the system follows the Debian-mandated layout is not reasonable. If you still don't agree with patching systemd, I guess this will need to be reported against the debian-policy package. I'll do that if you don't want to. -- Michael signature.asc Description: PGP signature
Bug#1081988: Proceeding with removal of xrstools
Control: severity 1081988 normal Control: retitle 1081988 RM: xrstools -- RoQA; rc-buggy Control: reassign 1081988 ftp.debian.org Control: affects 1081988 + src:xrstools Dear xrstools maintainer and ftp team, a month has passed since filing a suggestion to remove xrstools from Debian. It was suggested for removal due to not being part of bookworm nor trixie and having accumulated a long-standing RC bug. * #1022504: xrstools: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command Last modified: 1 year, 4 months Since the suggestion bug was neither closed nor tagged in a month, silent consent to proceed with removal is assumed. Kind regards A tool for automatically removing packages from unstable This bug reply has been automatically sent with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1081990: Proceeding with removal of mod-gnutls
Control: severity 1081990 normal Control: retitle 1081990 RM: mod-gnutls -- RoQA; rc-buggy Control: reassign 1081990 ftp.debian.org Control: affects 1081990 + src:mod-gnutls Dear mod-gnutls maintainer and ftp team, a month has passed since filing a suggestion to remove mod-gnutls from Debian. It was suggested for removal due to not being part of bookworm nor trixie and having accumulated 2 long-standing RC bugs. * #942737: libapache2-mod-gnutls: mod_gnutls consumes 100% cpu (CVE-2023-25824) Last modified: 1 year, 7 months * #1050670: mod-gnutls: FTBFS: GnuTLS: Failed to initialize: (-1250) An unimplemented or disabled feature has been requested. Last modified: 1 year, 1 month Since the suggestion bug was neither closed nor tagged in a month, silent consent to proceed with removal is assumed. Kind regards A tool for automatically removing packages from unstable This bug reply has been automatically sent with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1081991: Proceeding with removal of jquery-simpletreemenu
Control: severity 1081991 normal Control: retitle 1081991 RM: jquery-simpletreemenu -- RoQA; rc-buggy Control: reassign 1081991 ftp.debian.org Control: affects 1081991 + src:jquery-simpletreemenu Dear jquery-simpletreemenu maintainer and ftp team, a month has passed since filing a suggestion to remove jquery-simpletreemenu from Debian. It was suggested for removal due to not being part of bookworm nor trixie and having accumulated a long-standing RC bug. * #979940: jquery-simpletreemenu: node-uglify is deprecated in favor of uglifyjs Last modified: 1 year, 4 months Since the suggestion bug was neither closed nor tagged in a month, silent consent to proceed with removal is assumed. Kind regards A tool for automatically removing packages from unstable This bug reply has been automatically sent with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1085392: Should zmodemjs be removed from unstable?
Source: zmodemjs Severity: important User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing zmodemjs from Debian for the following reasons: * It accumulated one RC-bug: + #1005454: zmodemjs: FTBFS: Can't exec "webpack": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 523. Last modified: 1 year, 4 months * It is not part of bookworm or trixie and is not a key package. This bug serves as a pre-removal warning. After one month, the bug will be reassigned to ftp.debian.org to actually request removal of the package. In case the package should be kept in unstable, please evaluate each of the RC-bugs listed above. * If the bug is meant to permanently prevent the package from entering testing or a stable release, but this package should stay part of unstable, please add a usertag: user helm...@debian.org usertags NNN + sidremove-ignore * If the bug no longer applies, please close it. If it is closed, check whether the fixed version is correct and adjust if necessary. * Is the bug really release-critical? If not, please downgrade. * If the bug still applies, please send a status update at least once a year. Once all of the mentioned RC bugs have been acted upon in one way or another, please close this bug. In case the package should be removed from unstable, you may reassign this bug report: Control: severity -1 normal Control: retitle -1 RM: zmodemjs -- RoM; rc-buggy Control: reassign -1 ftp.debian.org Control: affects -1 + src:zmodemjs Alternatively, you may wait a month and have it reassigned. In case you disagree with the above, please add a wontfix tag to this bug. Control: tags -1 + wontfix Doing so will also prevent automatic reassignment. Kind regards A tool for automatically removing packages from unstable This bug report has been automatically filed with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1081985: Proceeding with removal of irssi-plugin-robustirc
Control: severity 1081985 normal Control: retitle 1081985 RM: irssi-plugin-robustirc -- RoQA; rc-buggy Control: reassign 1081985 ftp.debian.org Control: affects 1081985 + src:irssi-plugin-robustirc Dear irssi-plugin-robustirc maintainer and ftp team, a month has passed since filing a suggestion to remove irssi-plugin-robustirc from Debian. It was suggested for removal due to not being part of bookworm nor trixie and having accumulated a long-standing RC bug. * #1015080: irssi-plugin-robustirc: FTBFS: robustsession.c:599:25: error: âG_INPUT_READâ undeclared (first use in this function); did you mean âI_INPUT_READâ? Last modified: 1 year, 4 months Since the suggestion bug was neither closed nor tagged in a month, silent consent to proceed with removal is assumed. Kind regards A tool for automatically removing packages from unstable This bug reply has been automatically sent with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1081984: Proceeding with removal of kryo-serializers
Control: severity 1081984 normal Control: retitle 1081984 RM: kryo-serializers -- RoQA; rc-buggy Control: reassign 1081984 ftp.debian.org Control: affects 1081984 + src:kryo-serializers Dear kryo-serializers maintainer and ftp team, a month has passed since filing a suggestion to remove kryo-serializers from Debian. It was suggested for removal due to not being part of bookworm nor trixie and having accumulated a long-standing RC bug. * #875594: FTBFS with Java 9: test failures around reflection on core classes Last modified: 1 year, 4 months Since the suggestion bug was neither closed nor tagged in a month, silent consent to proceed with removal is assumed. Kind regards A tool for automatically removing packages from unstable This bug reply has been automatically sent with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1081989: Proceeding with removal of shotdetect
Control: severity 1081989 normal Control: retitle 1081989 RM: shotdetect -- RoQA; rc-buggy Control: reassign 1081989 ftp.debian.org Control: affects 1081989 + src:shotdetect Dear shotdetect maintainer and ftp team, a month has passed since filing a suggestion to remove shotdetect from Debian. It was suggested for removal due to not being part of bookworm nor trixie and having accumulated a long-standing RC bug. * #1004719: shotdetect: FTBFS with ffmpeg 5.0 Last modified: 1 year, 4 months Since the suggestion bug was neither closed nor tagged in a month, silent consent to proceed with removal is assumed. Kind regards A tool for automatically removing packages from unstable This bug reply has been automatically sent with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1085387: iwlwifi: wifi does not work at startup, starts working after 2-3 reboots and then works fine
Package: firmware-iwlwifi Version: 20230210-5 Severity: important File: iwlwifi X-Debbugs-Cc: se...@ymail.com, se...@php.net -- System Information: Debian Release: 12.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-26-amd64 (SMP w/8 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 firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.142+deb12u1 -- no debconf information
Bug#1081987: Proceeding with removal of ruby-diaspora-federation
Control: severity 1081987 normal Control: retitle 1081987 RM: ruby-diaspora-federation -- RoQA; rc-buggy Control: reassign 1081987 ftp.debian.org Control: affects 1081987 + src:ruby-diaspora-federation Dear ruby-diaspora-federation maintainer and ftp team, a month has passed since filing a suggestion to remove ruby-diaspora-federation from Debian. It was suggested for removal due to not being part of bookworm nor trixie and having accumulated a long-standing RC bug. * #1006031: ruby-diaspora-federation: FTBFS: ERROR: Error installing /tmp/d20220218-85959-ao9ro1/diaspora_federation-0.2.7.gem: diaspora_federation-0.2.7 requires Ruby version ~> 2.1. The current ruby version is 3.0.2.107. Last modified: 1 year, 4 months Since the suggestion bug was neither closed nor tagged in a month, silent consent to proceed with removal is assumed. Kind regards A tool for automatically removing packages from unstable This bug reply has been automatically sent with little human intervention. If the filing is unclear or in error, don't hesitate to contact Helmut Grohne for assistance.
Bug#1085350: azure-devops-cli-extension: Python SyntaxWarning
Source: azure-devops-cli-extension Version: 1.0.1-1 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/a/azure-devops-cli-extension.html Setting up python3-azext-devops (1.0.1-1) ... /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v5_0/feed/models.py:101: SyntaxWarning: invalid escape sequence '\,' """FeedCore. /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v5_0/feed/models.py:209: SyntaxWarning: invalid escape sequence '\,' """FeedUpdate. /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v5_0/feed/models.py:985: SyntaxWarning: invalid escape sequence '\,' """Feed. /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v5_1/feed/models.py:101: SyntaxWarning: invalid escape sequence '\,' """ /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v5_1/feed/models.py:220: SyntaxWarning: invalid escape sequence '\,' """ /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v5_1/feed/models.py:1049: SyntaxWarning: invalid escape sequence '\,' """ /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v6_0/feed/models.py:101: SyntaxWarning: invalid escape sequence '\,' """ /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v6_0/feed/models.py:224: SyntaxWarning: invalid escape sequence '\,' """ /usr/lib/python3/dist-packages/azext_devops/devops_sdk/v6_0/feed/models.py:1080: SyntaxWarning: invalid escape sequence '\,' """
Bug#1085334: dbusada: calls dbus_get_local_machine_id() which has bad error-handling
On 10/18/24 15:27, Simon McVittie wrote: Based on my limited understanding of the Ada language, it looks as though dbusada calls dbus_get_local_machine_id(), which has no good mechanism for reporting an error, and therefore will spam warnings to standard error (and possibly crash) if the D-Bus machine ID has not been set up correctly. This function should be considered deprecated. dbusada does not call dbus_get_local_machine_id() on its own initiative, see the source code of the library. This function is part of the auto-generated thin binding though. How do you deduce that dbusada calls this function? Please prefer to use dbus_try_get_local_machine_id(), which takes a DBusError parameter and therefore can be used to report errors in whatever way is considered to be most appropriate by the caller. This has been available in upstream stable releases since dbus 1.12.0 (2017). The dbus_try_get_local_machine_id() is also part of the thin layer and can be used by an application if it desires. Kind regards, - reto
Bug#1085351: camo: Permission for team upload of camo
Source: camo Version: 2.3.0+dfsg-1.1 Severity: important X-Debbugs-Cc: Zulip Debian Packaging Team , Luke Faraone , 845...@bugs.debian.org, Package Salvaging Team , 732...@bugs.debian.org Hi Luke, Your package camo was highlighted in the Bug of the Day[1] initiative, which aims to introduce newcomers to manageable tasks and guide them through the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to familiarize newcomers with a consistent Git-based workflow. Usually we file Intend To Salvage bugs[2] if we move some package from invalid VCS (=old Alioth) to Salsa. However, I have seen the maintainer is just a team (Zulip Debian Packaging Team) and it seems well located inside this team. Thus salvaging is not the correct procedure since we do not intend to change the team - just make it available on Salsa to enable better cooperation between developers. I'm just filing this ITS-like bug report to formalise and document the procedure. Since there is no team space on Salsa for the Zulip Debian Packaging Team (yet) I have migrated the packaging to debian team[3] (which perfectly fits its former location under collab-maint). I've fixed the two bugs that are in CC and modernised the packaging. The package salvage team is also busy adding systemd support which would fix the last open bug. I just want to ask you kindly to permit a team upload to make those fixes and the new Vcs location public. Kind regards Andreas. [1] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks [2] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [3] https://salsa.debian.org/debian/camo -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.10.11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1085340: fcitx: calls dbus_get_local_machine_id() which has bad error-handling
Control: tags 1085340 +wontfix 在 2024-10-18五的 14:40 +0100，Simon McVittie写道： > Source: fcitx > Version: 1:4.2.9.9-2 > Severity: normal > Tags: upstream > > Several files in fcitx contain calls to dbus_get_local_machine_id(), > which has no good mechanism for reporting an error, and therefore will > spam warnings to standard error (and possibly crash) if the D-Bus machine > ID has not been set up correctly. This function should be considered > deprecated. > > Please prefer to use dbus_try_get_local_machine_id(), which takes a > DBusError parameter (same calling convention as e.g. dbus_validate_path()) > and therefore can be used to report errors in whatever way is considered > to be most appropriate by the caller. This has been available in upstream > stable releases since dbus 1.12.0 (2017). As the fcitx upstream development has ceased [1], no upstream patch can be expected. Tagging it as wontfix. [1] https://lists.debian.org/debian-input-method/2024/10/msg00042.html Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1085330: astrometry.net: Python SyntaxWarning
Source: astrometry.net Version: 0.96+dfsg-1 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/a/astrometry.net.html Setting up python3-astrometry (0.96+dfsg-1) ... /usr/lib/python3/dist-packages/astrometry/sdss/yanny.py:777: SyntaxWarning: invalid escape sequence '\`' """Converts text into tables that users can use.
Bug#1085329: astlib: Python SyntaxWarning
Source: astlib
Version: 0.12.0-1
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/a/astlib.html
Setting up python3-astlib (0.12.0-1) ...
/usr/lib/python3/dist-packages/astLib/astPlots.py:77: SyntaxWarning:
invalid escape sequence '\p'
PRIME = "$^\prime$"
/usr/lib/python3/dist-packages/astLib/astPlots.py:79: SyntaxWarning:
invalid escape sequence '\p'
DOUBLE_PRIME = "$^{\prime\prime}$"
/usr/lib/python3/dist-packages/astLib/astPlots.py:908:
SyntaxWarning: invalid escape sequence '\s'
rString=hString+"$^{\sf{h}}$"
/usr/lib/python3/dist-packages/astLib/astPlots.py:910:
SyntaxWarning: invalid escape sequence '\s'
rString=hString+"$^{\sf{h}}$"+mString+"$^{\sf{m}}$"
/usr/lib/python3/dist-packages/astLib/astPlots.py:910:
SyntaxWarning: invalid escape sequence '\s'
rString=hString+"$^{\sf{h}}$"+mString+"$^{\sf{m}}$"
/usr/lib/python3/dist-packages/astLib/astPlots.py:912:
SyntaxWarning: invalid escape sequence '\s'
rString=hString+"$^{\sf{h}}$"+mString+"$^{\sf{m}}$"+sString+"$^{\sf{s}}$"
/usr/lib/python3/dist-packages/astLib/astPlots.py:912:
SyntaxWarning: invalid escape sequence '\s'
rString=hString+"$^{\sf{h}}$"+mString+"$^{\sf{m}}$"+sString+"$^{\sf{s}}$"
/usr/lib/python3/dist-packages/astLib/astPlots.py:912:
SyntaxWarning: invalid escape sequence '\s'
rString=hString+"$^{\sf{h}}$"+mString+"$^{\sf{m}}$"+sString+"$^{\sf{s}}$"
Bug#1085317: acpica-tools: acpixtract fails to extract SSDT: `Table [SSDT] was not found in …`
Package: acpica-tools Version: 20240827-1 Severity: important Forwarded: https://github.com/acpica/acpica/issues/978 Dear Debian folks, Release 20240827 regressed and `acpixtract` fails to extract the SSDT: Table [SSDT] was not found in … I bisected the issue to commit ad5755dd8 (acpixtract: don't abort AxExtractTables for AX_OPTIONAL_TABLES) and reported the issue upstream [1]. It might make sense to revert the commit in the Debian package. Kind regards, Paul [1]: https://github.com/acpica/acpica/issues/978
Bug#1085332: ariba: Python SyntaxWarning
Source: ariba
Version: 2.14.7+ds-2
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/a/ariba.html
Setting up ariba (2.14.7+ds-2+b1) ...
/usr/lib/python3/dist-packages/ariba/external_progs.py:34:
SyntaxWarning: invalid escape sequence '\.'
'cdhit': ('', re.compile('CD-HIT version ([0-9\.]+) \(')),
/usr/lib/python3/dist-packages/ariba/external_progs.py:35:
SyntaxWarning: invalid escape sequence '\.'
'nucmer': ('--version', re.compile('([0-9]+\.[0-9\.]+.*$)')),
/usr/lib/python3/dist-packages/ariba/external_progs.py:36:
SyntaxWarning: invalid escape sequence '\.'
'spades': ('--version', re.compile('SPAdes.*v([0-9\.]+)'))
Bug#1078734: ITP: legacycrypt -- The legacycrypt module is a standalone version of https://docs.python.org/3/library/crypt.html (deprecated), to ease 3.13 transition.
Thank you for keeping an eye on this. There was an even more specific proposal of the Python Team to use the "python-zombie-*" namespace for all the modules removed by PEP594 and further future deprecation PEPs; this is based on the model of existing python-zombie-imp. https://peps.python.org/pep-0594/ I packaged python-zombie-telnetlib as a "native" package; it's a single file that will likely never change anymore. Someone could create a project on Pypi, maybe... we'll see. Here legacycrypt is an already established name, it can stay as python-legacycrypt. (?) Greetings Le ven. 18 oct. 2024 à 14:36, Guillem Jover a écrit : > > * URL : https://github.com/tiran/legacycrypt > > Description : The legacycrypt module is a standalone version of > > https://docs.python.org/3/library/crypt.html (crypt was removed in Python > > 3.13). > > This seems to be a python module only package, but its source package > name is not currently namespaced. Given that it has not yet passed NEW, > please namespace it with python- to avoid taking on the global namespace, > so that we do not "prevent" packaging something that for example installs > a command with the same name (or having to end up using a non-obvious one > for that, or requiring a future rename), so that it's easier to see what > it is about when doing archive-wide analysis from Sources, or dd-lists, > or even reading changelogs via stuff like apt-listchanges, like the rest > of the language specific teams are doing. :)
Bug#1085333: rust-dbus: calls dbus_get_local_machine_id() which has bad error-handling
Source: rust-dbus Version: 0.9.7-1 Severity: normal Tags: upstream rust-dbus calls dbus_get_local_machine_id(), which has no good mechanism for reporting an error, and therefore will spam warnings to standard error (and possibly crash) if the D-Bus machine ID has not been set up correctly. This function should be considered deprecated. Please prefer to use dbus_try_get_local_machine_id(), which takes a DBusError parameter and therefore can be used to report errors in whatever way is considered to be most appropriate by the caller. This has been available in upstream stable releases since dbus 1.12.0 (2017). Thanks, smcv
Bug#1085375: node-markdown-to-jsx: CVE-2024-21535
Source: node-markdown-to-jsx X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for node-markdown-to-jsx. CVE-2024-21535[0]: | Versions of the package markdown-to-jsx before 7.4.0 are vulnerable | to Cross-site Scripting (XSS) via the src property due to improper | input sanitization. An attacker can execute arbitrary code by | injecting a malicious iframe element in the markdown. https://security.snyk.io/vuln/SNYK-JS-MARKDOWNTOJSX-6258886 https://github.com/quantizor/markdown-to-jsx/commit/8eb74da825c0d8d2e9508d73c672bcae36ba555a (v7.4.0) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-21535 https://www.cve.org/CVERecord?id=CVE-2024-21535 Please adjust the affected versions in the BTS as needed.
Bug#1084909: catch2: diff for NMU version 3.7.1-0.2
user debian-rele...@lists.debian.org
usertag 1084909 + bsp-2024-10-at-sbg
tags 1084909 + patch
thank you
Dear maintainer,
I've prepared an NMU for catch2 (versioned as 3.7.1-0.2). The diff
is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru catch2-3.7.1/debian/changelog catch2-3.7.1/debian/changelog
--- catch2-3.7.1/debian/changelog 2024-10-06 09:33:35.0 +0200
+++ catch2-3.7.1/debian/changelog 2024-10-18 19:30:29.0 +0200
@@ -1,3 +1,12 @@
+catch2 (3.7.1-0.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Increase alignment to maximum to work around build issues
+(Closes: #1084909)
+ * debian/rules: Build without -Werror
+
+ -- Sebastian Ramacher Fri, 18 Oct 2024 19:30:29 +0200
+
catch2 (3.7.1-0.1) unstable; urgency=medium
* Non-maintainer upload
diff -Nru catch2-3.7.1/debian/patches/fix-alignment.patch catch2-3.7.1/debian/patches/fix-alignment.patch
--- catch2-3.7.1/debian/patches/fix-alignment.patch 1970-01-01 01:00:00.0 +0100
+++ catch2-3.7.1/debian/patches/fix-alignment.patch 2024-10-18 17:39:47.0 +0200
@@ -0,0 +1,20 @@
+--- a/src/catch2/benchmark/catch_constructor.hpp
b/src/catch2/benchmark/catch_constructor.hpp
+@@ -18,7 +18,7 @@
+ namespace Benchmark {
+ namespace Detail {
+ template
+-struct ObjectStorage
++struct alignas(alignof(T)) ObjectStorage
+ {
+ ObjectStorage() = default;
+
+@@ -67,7 +67,7 @@
+ #pragma GCC diagnostic pop
+ #endif
+
+-alignas( T ) unsigned char data[sizeof( T )]{};
++alignas( alignof(T) ) unsigned char data[sizeof( T )]{};
+ };
+ } // namespace Detail
+
diff -Nru catch2-3.7.1/debian/patches/series catch2-3.7.1/debian/patches/series
--- catch2-3.7.1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ catch2-3.7.1/debian/patches/series 2024-10-18 17:15:37.0 +0200
@@ -0,0 +1 @@
+fix-alignment.patch
diff -Nru catch2-3.7.1/debian/rules catch2-3.7.1/debian/rules
--- catch2-3.7.1/debian/rules 2024-10-06 09:31:32.0 +0200
+++ catch2-3.7.1/debian/rules 2024-10-18 17:51:16.0 +0200
@@ -16,4 +16,5 @@
dh_auto_configure -- \
-DCMAKE_INSTALL_LIBDIR=lib \
-DCMAKE_INSTALL_DOCDIR=/usr/share/doc/libcatch2-dev/docs \
- -DCATCH_DEVELOPMENT_BUILD=$(ENABLE_SELFTEST)
+ -DCATCH_DEVELOPMENT_BUILD=$(ENABLE_SELFTEST) \
+ -DCATCH_ENABLE_WERROR=OFF
Bug#1085381: xraylarch: ships coverage data directly under /usr/lib/python3/dist-packages
Source: xraylarch
Version: 0.9.81+ds1-1
Severity: important
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed that
xraylarch could not be built reproducibly.
This is because it ships a HTML-based test coverage report that contains
timestanos. However, it ships these files into a globally-shared namespace:
/usr/lib/python3/dist-packages/htmlcov/
... which is, of course, not great.
Patch attached.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/rules 2024-10-18 09:37:56.866610855 -0700
--- b/debian/rules 2024-10-18 09:56:33.295808799 -0700
@@ -2,6 +2,7 @@
export DH_VERBOSE=1
export PYBUILD_NAME=xraylarch
+export PYBUILD_AFTER_TEST=rm -rfv {build_dir}/htmlcov/
%:
dh $@ --buildsystem=pybuild
Bug#1085364: bkchem: Python SyntaxWarning
Source: bkchem
Version: 0.14.0~pre4+git20211228-4
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/b/bkchem.html
Setting up python3 (3.12.5-1) ...
/usr/share/bkchem/bkchem/arrow.py:431: SyntaxWarning: invalid escape
sequence '\ '
"""arrow head at 2
/usr/share/bkchem/bkchem/dom_extensions.py:81: SyntaxWarning:
invalid escape sequence '\s'
empty = re.compile('^\s*$')
/usr/share/bkchem/bkchem/edit_pool.py:152: SyntaxWarning: invalid
escape sequence '\d'
self._setText( re.sub( "\d+", '\g<0>', self.editPool.get()))
/usr/share/bkchem/bkchem/edit_pool.py:152: SyntaxWarning: invalid
escape sequence '\g'
self._setText( re.sub( "\d+", '\g<0>', self.editPool.get()))
/usr/share/bkchem/bkchem/group.py:132: SyntaxWarning: invalid escape
sequence '\d'
x = re.sub( "\d+", '\g<0>', self.symbol)
/usr/share/bkchem/bkchem/group.py:132: SyntaxWarning: invalid escape
sequence '\g'
x = re.sub( "\d+", '\g<0>', self.symbol)
/usr/share/bkchem/bkchem/group.py:133: SyntaxWarning: invalid escape
sequence '\g'
x = re.sub( "[+-]", '\g<0>', x)
/usr/share/bkchem/bkchem/misc.py:104: SyntaxWarning: invalid escape
sequence '\d'
cutter = re.compile( "([+-]?\d*\.?\d*)\s*([a-zA-Z]*)")
/usr/share/bkchem/bkchem/oasa/oasa/coords_generator.py:532:
SyntaxWarning: invalid escape sequence '\O'
sm = "C/C(Cl)=C(\O)C"
/usr/share/bkchem/bkchem/oasa/oasa/dom_extensions.py:80:
SyntaxWarning: invalid escape sequence '\s'
empty = re.compile('^\s*$')
/usr/share/bkchem/bkchem/oasa/oasa/inchi.py:282: SyntaxWarning:
invalid escape sequence '\('
re_for_brackets = "\([H\d,\-]+?\)"
/usr/share/bkchem/bkchem/oasa/oasa/inchi.py:299: SyntaxWarning:
invalid escape sequence '\('
re_for_brackets = "\([H\d,\-]+?\)"
/usr/share/bkchem/bkchem/oasa/oasa/inchi.py:498: SyntaxWarning:
invalid escape sequence '\d'
for a1,a2,sign in re.findall( "(\d+)-(\d+)([-+?u])", layer):
/usr/share/bkchem/bkchem/oasa/oasa/inchi.py:536: SyntaxWarning:
invalid escape sequence '\('
re_for_brackets = "\([H\d,\-]+?\)"
/usr/share/bkchem/bkchem/oasa/oasa/inchi_key.py:1278: SyntaxWarning:
invalid escape sequence '\d'
m = re.match( "(\d)(S)?", parts[0])
/usr/share/bkchem/bkchem/oasa/oasa/misc.py:115: SyntaxWarning:
invalid escape sequence '\d'
cutter = re.compile( "([+-]?\d*\.?\d*)\s*([a-zA-Z]*)")
/usr/share/bkchem/bkchem/oasa/oasa/molfile.py:101: SyntaxWarning:
invalid escape sequence '\s'
m = re.match( "M\s+RAD\s+(\d+)(.*)", prop)
/usr/share/bkchem/bkchem/oasa/oasa/molfile.py:103: SyntaxWarning:
invalid escape sequence '\d'
for at,rad in re.findall( "(\d+)\s+(\d+)", m.group( 2)):
/usr/share/bkchem/bkchem/oasa/oasa/molfile.py:107: SyntaxWarning:
invalid escape sequence '\s'
m = re.match( "M\s+CHG\s+(\d+)(.*)", prop)
/usr/share/bkchem/bkchem/oasa/oasa/molfile.py:109: SyntaxWarning:
invalid escape sequence '\d'
for at,chg in re.findall( "(\d+)\s+(-?\d+)", m.group( 2)):
/usr/share/bkchem/bkchem/oasa/oasa/periodic_table.py:347:
SyntaxWarning: invalid escape sequence '\d'
a = re.match( '^([a-z]{1,2})(h)(\d*)$', text.lower())
/usr/share/bkchem/bkchem/oasa/oasa/periodic_table.py:352:
SyntaxWarning: invalid escape sequence '\d'
a = re.match( '^(h)(\d*)([a-z]{1,2})$', text.lower())
/usr/share/bkchem/bkchem/oasa/oasa/query_atom.py:111: SyntaxWarning:
invalid escape sequence '\['
matcher = re.compile( "\[([A-Z][a-z]?,)*[A-Z][a-z]?\]")
/usr/share/bkchem/bkchem/oasa/oasa/smiles.py:97: SyntaxWarning:
invalid escape sequence '\['
chunks = re.split( "(\[.*?\]|[A-Z][a-z]?|%[0-9]{1,2}|[^A-Z]|[a-z])", text)
/usr/share/bkchem/bkchem/oasa/oasa/smiles.py:193: SyntaxWarning:
invalid escape sequence '\['
bracketed_atom = re.compile("^\[(\d*)([A-z][a-z]?)(.*?)\]")
/usr/share/bkchem/bkchem/oasa/oasa/smiles.py:206: SyntaxWarning:
invalid escape sequence '\d'
_hydrogens = re.search( "H(\d*)", rest)
/usr/share/bkchem/bkchem/oasa/oasa/smiles.py:224: SyntaxWarning:
invalid escape sequence '\d'
_charge = re.search( "([-+])(\d?)", rest)
/usr/share/bkchem/bkchem/oasa/oasa/structure_database.py:166:
SyntaxWarning: invalid escape sequence '\['
if re.search( "\[\d", smile):
/usr/share/bkchem/bkchem/oasa/test.py:19: SyntaxWarning: invalid
escape sequence '\C'
mol = oasa.smiles.text_to_mol( "c1c1\C=C/CC")
/usr/share/bkchem/bkchem/plugins/piddle/pdfgen.py:173:
SyntaxWarning: invalid escape sequence '\('
s = string.replace(s, '(','\(')
/usr/share/bkchem/bkchem/plugins/piddle/pdfgen.py:174:
SyntaxWarning: invalid escape sequence '\)'
s = string.replace(s, ')','\)')
/usr/share/bkchem/bkchem/plugins/piddle/pdfutils.py:57:
SyntaxWarning: invalid escape sequence '\m'
"""accepts either a filespec ('C:\mydir\*.jpg') or a list
/usr/share/bkchem/bkchem/plugins/piddle/pdfutils.py:101:
S
Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost
Control: reassign -1 debci Control: retitle -1 Please set net.ipv4.ping_group_range sysctl on debci test hosts On Thu, Oct 17, 2024 at 10:06:06PM +0200, Paul Gevers wrote: > system /bin/ping6 -c 1 localhost > 57s CheckHostAlive: first ping (/bin/ping6 -c 1 localhost) failed (512, ) > 57s no ping response from localhost > 57s can't ping localhost (client = localhost); exiting In bookworm and earlier, ping uses CAP_NET_RAW file capabilities in order to obtain permission to transmit ICMP. The version in trixie and later no longer sets file based capabilities, instead relying on the net.ipv4.ping_group_range sysctl. This is a system-wide configuration, not controlled by ping. The default value, as set by the linux-sysctl-defaults package in trixe+ and listed as a Recommends by iputils-ping, grants permission for unprivileged users to run ping. Based on the above, I don't see this as a bug in ping, but rather an issue with the particular environment in which it's being executed. My recommendation is to ensure that you've got the sysctl value set appropriately as from https://salsa.debian.org/kernel-team/linux-base/-/blob/master/sysctl.d/50-default.conf?ref_type=heads#L39-45 Re-assigning this to the debci package so the change can be made there. noah
Bug#1085382: libconfig-model-dpkg-perl: scan-copyrights crashes when non ascii 7 chars are present in debian/fill.copyright.blanks.yml
Package: libconfig-model-dpkg-perl Version: 2.165 Severity: normal Dear Maintainer, I noticed that libconfig-model-dpkg-perl 3.005 crashes if non ascii 7 chars are found in debian/fill.copyright.blanks.yml with Attribute (main_grant_weight) does not pass the type constraint because: Validation failed for 'Int' with value undef at /usr/lib/x86_64-linux- gnu/perl5/5.38/Mouse/Util.pm line 395. Mouse::Util::throw_error(Mouse::Meta::Attribute=HASH(0x57cd418daee8), "Attribute (main_grant_weight) does not pass the type constrai"..., "data", undef, "depth", -1) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 278 Dpkg::Copyright::Grant::ByDir::main_grant(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41ab1270)) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 221 Dpkg::Copyright::Grant::ByDir::count_dir_grant(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41ab1188), HASH(0x57cd41a9d5a8), HASH(0x57cd419dd5e8)) called at ../../pkg- debian/libconfig-model-dpkg-perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 199 Dpkg::Copyright::Grant::ByDir::count_grant(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41ab1188)) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 271 Dpkg::Copyright::Grant::ByDir::main_grant(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41ab1188)) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 221 Dpkg::Copyright::Grant::ByDir::count_dir_grant(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41995fc0), HASH(0x57cd418be2f8), HASH(0x57cd418be310)) called at ../../pkg- debian/libconfig-model-dpkg-perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 199 Dpkg::Copyright::Grant::ByDir::count_grant(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41995fc0)) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 271 Dpkg::Copyright::Grant::ByDir::main_grant(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41995fc0)) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 385 Dpkg::Copyright::Grant::ByDir::debian_full_data(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41995fc0)) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Grant/ByDir.pm line 418 Dpkg::Copyright::Grant::ByDir::debian_full_record(Dpkg::Copyright::Grant::ByDir=HASH(0x57cd41995fc0)) called at ../../pkg-debian/libconfig-model-dpkg- perl/lib/Dpkg/Copyright/Scanner.pm line 56 Dpkg::Copyright::Scanner::generate_copyright() called at ../../pkg- debian/libconfig-model-dpkg-perl/lib/Dpkg/Copyright/Scanner.pm line 64 Dpkg::Copyright::Scanner::print_copyright() called at ../../pkg- debian/libconfig-model-dpkg-perl/bin/scan-copyrights line 37 as an example of the file $ cat debian/fill.copyright.blanks.yml debian/: copyright: "\xA9 1999-2023 Jordi Mallach " license: GPL-3+ -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-44-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libconfig-model-dpkg-perl depends on: ii debhelper 13.11.6ubuntu1 ii libapt-pkg-perl0.1.40build3 ii libarray-intspan-perl 2.004-2 ii libconfig-model-backend-yaml-perl 2.134-2 ii libconfig-model-perl 2.153-3 ii libdata-compare-perl 1.29-1 ii libexporter-lite-perl 0.09-2 ii liblog-log4perl-perl 1.57-1 ii libmouse-perl 2.5.10-1build5 ii libparse-debcontrol-perl 2.005-6 ii libparse-recdescent-perl 1.967015+dfsg-4 ii libsoftware-licensemoreutils-perl 1.009-1 ii libsort-versions-perl 1.62-3 ii libtext-autoformat-perl1.75-2 ii libtext-levenshtein-damerau-perl 0.41-3 ii libtoml-tiny-perl 0.16-1 ii liburi-perl5.19-2 ii libwww-perl6.72-1 ii libyaml-libyaml-perl 0.86+ds-1 ii licensecheck 3.3.9-1ubuntu1 ii lintian2.116.3ubuntu3.2 ii perl [libmodule-corelist-perl] 5.36.0-9ubuntu1.1 Versions of packages libconfig-model-dpkg-perl recommends: ii libconfig-model-tkui-perl 1.376-1 libconfig-model-dpkg-perl suggests no packages. -- no debconf information
Bug#1081005: closed by Debian FTP Masters (reply to Thomas Lange ) (Bug#1081005: fixed in dracut 103-2)
Hi Thomas, * Thomas Lange [2024-10-17 14:21]: The only solution would be to have a patch for upstream that will remove the need of gawk, by replacing the strtonum() function by some other code. Done that: https://github.com/dracut-ng/dracut-ng/pull/734 What is the reason to get rid of the gawk dependency? Only to keep dependencies low. Cheers Jochen signature.asc Description: PGP signature
Bug#1085092: libglib2.0-0: segfault after installing shared-mime-info from Homebrew
Control: retitle -1 libglib2.0-0: segfault after installing shared-mime-info
from Homebrew
Control: tags -1 + moreinfo
On Fri, 18 Oct 2024 at 18:50:46 +0200, Lennart Ackermans wrote:
> So full steps to reproduce are:
>
> - Install homebrew (https://brew.sh/)
> - brew install shared-mime-info
> - Ensure /home/linuxbrew/.linuxbrew/share is in $XDG_DATA_DIRS
> - Run a file manager like Thunar and navigate to a directory with a
> non-empty json file
Does this happen for literally any JSON file (for example
`echo "{}" > object.json`) or does the JSON file that is required to
reproduce the crash have non-trivial contents?
Is there a single file or combination of files that reproduce this without
installing arbitrary software from outside Debian?
For example as a starting point you could try excluding
/home/linuxbrew/.linuxbrew/share from XDG_DATA_DIRS, and copying
some file installed by Homebrew (possibly
/home/linuxbrew/.linuxbrew/share/mime/packages/freedesktop.org.xml?)
into ~/.local/share/mime/packages?
If that probably-multi-megabyte XML file reproduces the crash, it would
also be very useful if you're able to narrow it down to some smaller part
of the file as the trigger for this crash. Extracting the MIME type
definitions for formats that match the glob *.json, like application/json
and application/schema+json, might be a good first step.
smcv
Bug#1085383: libngspice0 should depends ngspice in the same version
Package: libngspice0 Version: 43+ds-1~bpo12+1 Severity: normal libngspice uses configuration and model files provided by ngspice package (/usr/share/ngspice/scripts/spinit and /usr/lib/x86_64-linux-gnu/ngspice/*.cm). * running software used libngspice0 without ngspice installed may results in error "MIF-ERROR - unable to find definition of model and Simulation interrupted due to error!" (with previous warning "Warning: can't find the initialization file spinit") * running software used libngspice0 with installed ngspice in version different than libngspice0 version (for example libngspice0 43+ds-1~bpo12+1 and ngspice 39.3+ds-1) may cause segmentation fault. Segmentation fault occurs only while referring to standard models provided by *.cm files, for example while simulating digital systems using: A1 [in1 in2] out AND .model AND d_and -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libngspice0 depends on: ii libc6 2.36-9+deb12u4 ii libgcc-s1 12.2.0-14 ii libgomp112.2.0-14 ii libstdc++6 12.2.0-14 libngspice0 recommends no packages. libngspice0 suggests no packages. -- no debconf information
Bug#1085384: strongswan: Installing strongswan on debian is highly confusing and prone to errors
Package: strongswan Version: 5.9.8-5+deb12u1 Severity: normal X-Debbugs-Cc: and...@napalm.hu Dear Maintainer, Packages related to strongswan are very hard to understand, and to use them properly. Currently it is possible to have the strongswan, strongswan-starter and strongswan-charon triplet installed alongside with charon-systemd and strongswan-swanctl. While in rare cases it might make sense, i think most of the users only needs one set of them. Either they want to use the legacy ipsec.conf or the newer swanctl.conf. Also there may be differences whether they use systemd or not. And maybe more factors, i really do not know. When I install everything, two copies of charon daemon are trying to run at the same time, and it leads to a lot of problems. The error messages in 5.9.8 are not helpful in any way. It took me 2 days to figure out that there are two deamons. Even the upstream developer has a separate section regarding debian packages: https://docs.strongswan.org/docs/5.9/install/install.html " When installing the strongswan metapackage, the legacy daemon and configuration backend are installed. To use swanctl/vici instead, install the charon-systemd and strongswan-swanctl packages and remove both the strongswan-starter and strongswan-charon packages. Make sure you only have either the charon-systemd or the strongswan-starter package installed (or at least disable one of the systemd units they install, which are strongswan.service and strongswan- starter.service, respectively). " There was a time when they were conflicting packages, but not any more: strongswan-libcharon Breaks: strongswan-starter (<= 5.6.1-2) Replaces: strongswan-starter (<= 5.6.1-2) strongswan-swanctl Breaks: strongswan-starter (<< 5.8.0-1) Replaces: strongswan-starter (<< 5.8.0-1) I doubt this is the intended behaviour. Also the names of the packages makes no sense to me. see also: https://github.com/strongswan/strongswan/discussions/2502 https://github.com/strongswan/strongswan/discussions/2282 -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-23-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages strongswan depends on: pn strongswan-charon pn strongswan-starter strongswan recommends no packages. strongswan suggests no packages.
Bug#1085224: dpkg: Please clarify Conffiles list output from dpkg --status
Hi! On Wed, 2024-10-16 at 22:34:34 +0200, Nis Martensen wrote: > Package: dpkg > Version: 1.22.11 > Severity: wishlist > X-Debbugs-Cc: nis.marten...@web.de > Reportbug uses `dpkg --status $package` to collect information about a > package, including the list of configuration files. It assumes that the > output in each line under Conffiles is always a space-separated tuple of > filename and md5sum. However, this is not always true, as indicated in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080336 Ah, if this was due to the remove-on-upgrade, that is only documented by proxy in deb-conffiles(5). > What should users of the dpkg --status output expect regarding the > conffiles list? E.g., how many fields can there be on each line? Why are > non-existent files sometimes included in the list? See > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085130 > for an example of confusion. When can removed configuration files be > expected to no longer be listed? Right, there is missing documentation for this. The entries always have at least two elements separated by a space, the filename and its md5sum from the .deb (or «newconffile» if the file was not present on the .deb). The entries can have an optional flag element that can be either «obsolete» or «remove-on-upgrade». The conffiles can be missing because they have been cleaned up by a maintscript, or removed during upgrade due to the «remove-on-upgrade» flag, but can also be missing because the local admin has removed them (which counts as a normal user modification to be preserved), so programs should not error out if a conffile is missing (dpkg does not). Currently there might be entries for obsolete conffiles left behind, but those will be "garbage collected" the next time a package is configured and the conffiles are not on disk anymore. > I'm wondering if reportbug should be changed to notice when the > remove-on-upgrade flag is printed and then ignore the corresponding line. It should never error out on missing conffiles. It might be nice to still print that the file is not present (with a nicer error than ENOENT) though. For obsolete and remove-on-upgrade it might make sense to print the conffiles in case they are present (as an abnormality) and otherwise not even present them at all? > Clarification or advice is appreciated. Would the deb-conffiles man page > be a good place to add clarifying documentation? Thanks! I don't think deb-conffiles(5) would be the correct place. Probably adding a section for some of the internal dpkg fields into dpkg-query(1), before the description of the virtual fields might make sense. So I'll try to do that. Thanks, Guillem
Bug#1085405: Unresolvable dependency for libpetsc-real3.21-dev (Sid)
Package: libpetsc-real3.21-dev Version: 3.21.6+dfsg1-1 I am using open build system (https://build.opensuse.org) to provide packages of my application (damask) for Debian. Builds for unstable/sid fail now with the following error message """ nothing provides libopenmpi-dev << 4.2 needed by libpetsc-real3.21-dev, (got version 5.0.5-3) """ Indeed, https://packages.debian.org/sid/libpetsc-real3.21-dev requires libopenmpi-dev (<< 4.2) [not armel, armhf, i386, m68k, sh4, x32] while https://packages.debian.org/sid/libopenmpi-dev is at 5.0.5-3 sorry for not using debugreport, it can't easily install it on my (non- Debian) OS. Hope this is still helpful. -- KU Leuven Department of Computer Science Department of Materials Engineering Celestijnenlaan 200a 3001 Leuven, Belgium signature.asc Description: This is a digitally signed message part
Bug#1085122: quota cron.daily job wants to see "quota" in /etc/fstab
On Mon, 14 Oct 2024 23:54:39 +0200 Francesco Poli (wintermute) wrote: [...] > I added a "quota" option to '/etc/fstab', just to make the cron.daily > job happy [...] Turns out that adding a "quota" mount option in 'etc/fstab' to the filesystem which has the quota feature enabled makes the quotaon systemd unit fail at boot. So I decided to go for a "noquota" mount option in 'etc/fstab'. Very counter-intuitive. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpcWLGM32E7Q.pgp Description: PGP signature
Bug#1085402: RM: latencytop -- RoQA; orphaned, abandoned upstream, ftbfs
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: latency...@packages.debian.org Control: affects -1 + src:latencytop Please remove latencytop. upstream git is gone, last release was in 2009. Orphaned in Debian. FTBFS with gcc14. Thanks, Chris
Bug#1085401: RM: icmpush -- RoQA; orphaned, abandoned upstream, ftbfs
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: icmp...@packages.debian.org Control: affects -1 + src:icmpush Please remove icmpush. Last upstream release in the year 2000. ftbfs with gcc14. scapy can be used to generate arbitrary packets including ICMP. Thanks, Chris
Bug#1085399: exchange-calendars: FTBFS: failing tests (probably due to recent tzdata)
Package: src:exchange-calendars
Version: 4.5.6-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.12_exchange-calendars
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
[... snipped ...]
from .exchange_calendar_xdus import XDUSExchangeCalendar
exchange_calendars/exchange_calendar_xdus.py:65: in
class XDUSExchangeCalendar(ExchangeCalendar):
exchange_calendars/exchange_calendar_xdus.py:97: in XDUSExchangeCalendar
tz = ZoneInfo("CET")
/usr/lib/python3.12/zoneinfo/_common.py:24: in load_tzdata
raise ZoneInfoNotFoundError(f"No time zone found with key {key}")
E zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key CET'
_ ERROR collecting
.pybuild/cpython3_3.12_exchange-calendars/build/tests/test_xtks_calendar.py _
/usr/lib/python3.12/zoneinfo/_common.py:12: in load_tzdata
return resources.files(package_name).joinpath(resource_name).open("rb")
/usr/lib/python3.12/importlib/resources/_common.py:46: in wrapper
return func(anchor)
/usr/lib/python3.12/importlib/resources/_common.py:56: in files
return from_package(resolve(anchor))
/usr/lib/python3.12/functools.py:907: in wrapper
return dispatch(args[0].__class__)(*args, **kw)
/usr/lib/python3.12/importlib/resources/_common.py:82: in _
return importlib.import_module(cand)
/usr/lib/python3.12/importlib/__init__.py:90: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1387: in _gcd_import
???
:1360: in _find_and_load
???
:1310: in _find_and_load_unlocked
???
:488: in _call_with_frames_removed
???
:1387: in _gcd_import
???
:1360: in _find_and_load
???
:1324: in _find_and_load_unlocked
???
E ModuleNotFoundError: No module named 'tzdata'
During handling of the above exception, another exception occurred:
tests/test_xtks_calendar.py:4: in
from exchange_calendars.exchange_calendar_xtks import XTKSExchangeCalendar
exchange_calendars/__init__.py:16: in
from .calendar_utils import (
exchange_calendars/calendar_utils.py:26: in
from .exchange_calendar_xdus import XDUSExchangeCalendar
exchange_calendars/exchange_calendar_xdus.py:65: in
class XDUSExchangeCalendar(ExchangeCalendar):
exchange_calendars/exchange_calendar_xdus.py:97: in XDUSExchangeCalendar
tz = ZoneInfo("CET")
/usr/lib/python3.12/zoneinfo/_common.py:24: in load_tzdata
raise ZoneInfoNotFoundError(f"No time zone found with key {key}")
E zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key CET'
_ ERROR collecting
.pybuild/cpython3_3.12_exchange-calendars/build/tests/test_xtks_calendar.py _
/usr/lib/python3.12/zoneinfo/_common.py:12: in load_tzdata
return resources.files(package_name).joinpath(resource_name).open("rb")
/usr/lib/python3.12/importlib/resources/_common.py:46: in wrapper
return func(anchor)
/usr/lib/python3.12/importlib/resources/_common.py:56: in files
return from_package(resolve(anchor))
/usr/lib/python3.12/functools.py:907: in wrapper
return dispatch(args[0].__class__)(*args, **kw)
/usr/lib/python3.12/importlib/resources/_common.py:82: in _
return importlib.import_module(cand)
/usr/lib/python3.12/importlib/__init__.py:90: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1387: in _gcd_import
???
:1360: in _find_and_load
???
:1310: in _find_and_load_unlocked
???
:488: in _call_with_frames_removed
???
:1387: in _gcd_import
???
:1360: in _find_and_load
???
:1324: in _find_and_load_unlocked
???
E ModuleNotFoundError: No module named 'tzdata'
During handling of the above exception, another exception occurred:
tests/test_xtks_calendar.py:4: in
from exchange_calendars.exchange_calendar_xtks import XTKSExchangeCalendar
exchange_calendars/__init__.py:16: in
from .calendar_utils import (
exchange_calendars/calendar_utils.py:26: in
from .exchange_calendar_xdus import XDUSExchangeCalendar
exchange_calendars/exchange_calendar_xdus.py:65: in
class XDUSExchangeCalendar(ExchangeCalendar):
exchange_calendars/exchange_calendar_xdus.py:97: in XDUSExchangeCalendar
tz = ZoneInfo("CET")
/usr/lib/python3.12/zoneinfo/_common.py:24: in load_tzdata
raise ZoneInfoNotFoundError(f"No time zone found with key {key}")
E zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key CET'
_ ERROR collecting
Bug#1084649: buildbot: removal of Python standard libraries in Python 3.13
tags 1084649 ftbfs severity 1084649 serious thanks Hi. Thanks for the report. I'm raising the severity because I've noticed that the package already FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/buildbot.html (If you know why it worked before and it does not work anymore, I'd like to know. Is this already failing with python 3.12?). Thanks.
Bug#1083073: emacs-goodies-el: Use Recommends instead of Depends to provide more flexibility in choosing packages
Sean Whitton writes: > Hello, > > On Thu 17 Oct 2024 at 10:22pm -07, Xiyue Deng wrote: > >> Sean Whitton writes: >> >>> Hello, >>> >>> Reusing the emacs-goodies-el source package just seemed convenient. >>> Making a separate source package is fine with me. Xiyue? >>> >> >> Ack. Let me make a new source package then. Is >> `emacs-editing-major-mode' good for the source package name? >> >> [ BTW, as I mentioned I was thinking about introducing more metapackages >> for various useful tools/minor modes/etc., so I would have suggested >> something more generic for the source package name. Now I think the >> Debtag system Nicholas mentioned may work better, and we can also set up >> a Debian Wiki page for an overview of packaged Addons in Debian, which >> would also serve the purpose. ] > > Note that debtags has been sunset and is officially unmaintained. It > might go away at any time. > > How about calling it emacs-addons-metapackages just in case we want > something else some day? > Sounds good. This makes the intention to only have metapackages clear. I took the liberty to have created the repo and added emacs-editing-major-modes[1]. I have also reverted the change in emacs-goodies-el[2]. PTAL. > -- > Sean Whitton [1] https://salsa.debian.org/emacsen-team/emacs-addons-metapackages [2] https://salsa.debian.org/emacsen-team/emacs-goodies-el/-/commit/54b3d4413eb9b7dcc80fd4c48c3af720c2e30a08 -- Regards, Xiyue Deng signature.asc Description: PGP signature
Bug#1085353: cdparanoia does not build with distro build flags
Package: cdparanoia
Version: 3.10.2+debian-14
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch
Dear Maintainer,
In Ubuntu, we found that cdparanoia was not using the distro build
flags. These patches fix this problem, and two FTBFS issues that we saw
as a result.
* Build with distro build flags, and fix resulting FTBFS (LP: #2073149)
- debian/rules: use *_MAINT_APPEND to add to {C,LD}FLAGS
- d/p/fix-format-security-warnings.patch: fix fprintf warnings
- d/p/check-seteuid-and-setegid-return-value.patch: fix unused result
warning
Thanks for considering the patch.
-Nick
diff -Nru
cdparanoia-3.10.2+debian/debian/patches/check-seteuid-and-setegid-return-value.patch
cdparanoia-3.10.2+debian/debian/patches/check-seteuid-and-setegid-return-value.patch
---
cdparanoia-3.10.2+debian/debian/patches/check-seteuid-and-setegid-return-value.patch
1969-12-31 19:00:00.0 -0500
+++
cdparanoia-3.10.2+debian/debian/patches/check-seteuid-and-setegid-return-value.patch
2024-07-15 15:17:24.0 -0400
@@ -0,0 +1,26 @@
+Description: Do not continue if seteuid or setegid fail
+ This fixes a warning revealed by using distro build flags.
+Author: Nick Rosbrook
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/2073149
+Forwarded: no
+Last-Update: 2024-07-15
+--- a/main.c
b/main.c
+@@ -1204,8 +1204,15 @@
+ paranoia_seek(p,cursor=first_sector,SEEK_SET);
+
+ /* this is probably a good idea in general */
+- seteuid(getuid());
+- setegid(getgid());
++ if (seteuid(getuid()) < 0) {
++report("seteuid: %s", strerror(errno));
++exit(1);
++ }
++
++ if (setegid(getgid()) < 0) {
++report("setegid: %s", strerror(errno));
++exit(1);
++ }
+
+ /* we'll need to be able to read one sector past user data if we
+have a sample offset in order to pick up the last bytes. We
diff -Nru
cdparanoia-3.10.2+debian/debian/patches/fix-format-security-warnings.patch
cdparanoia-3.10.2+debian/debian/patches/fix-format-security-warnings.patch
--- cdparanoia-3.10.2+debian/debian/patches/fix-format-security-warnings.patch
1969-12-31 19:00:00.0 -0500
+++ cdparanoia-3.10.2+debian/debian/patches/fix-format-security-warnings.patch
2024-07-15 15:17:24.0 -0400
@@ -0,0 +1,20 @@
+Description: Fix format-security warnings about fprintf
+Author: Nick Rosbrook
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/2073149
+Forwarded: no
+Last-Update: 2024-07-15
+--- a/main.c
b/main.c
+@@ -594,10 +594,10 @@
+ buffer[aheadposition+19]='>';
+ }
+
+- fprintf(stderr,buffer);
++ fprintf(stderr, "%s", buffer);
+
+ if (logfile != NULL && function==-1) {
+-fprintf(logfile,buffer+1);
++fprintf(logfile, "%s", buffer+1);
+ fprintf(logfile,"\n\n");
+ fflush(logfile);
+ }
diff -Nru cdparanoia-3.10.2+debian/debian/patches/series
cdparanoia-3.10.2+debian/debian/patches/series
--- cdparanoia-3.10.2+debian/debian/patches/series 2021-03-12
23:58:25.0 -0500
+++ cdparanoia-3.10.2+debian/debian/patches/series 2024-07-15
15:17:24.0 -0400
@@ -7,3 +7,5 @@
07-jpmanfix.patch
cdparanoia-force-progress-bar.diff
0009-dh-autoconf-generate-config-files.patch
+check-seteuid-and-setegid-return-value.patch
+fix-format-security-warnings.patch
diff -Nru cdparanoia-3.10.2+debian/debian/rules
cdparanoia-3.10.2+debian/debian/rules
--- cdparanoia-3.10.2+debian/debian/rules 2021-03-12 23:58:25.0
-0500
+++ cdparanoia-3.10.2+debian/debian/rules 2024-07-15 15:17:24.0
-0400
@@ -1,7 +1,7 @@
#!/usr/bin/make -f
-export CFLAGS += -fPIC -g
-export LDFLAGS += -fPIC
+export DEB_CFLAGS_MAINT_APPEND = -fPIC -g
+export DEB_LDFLAGS_MAINT_APPEND = -fPIC
%:
dh $@ --no-parallel
Bug#1085352: bls-standalone: Permission to upload bls-standalone with Vcs fields set to Salsa
Source: bls-standalone Version: 0.20151231 Severity: important X-Debbugs-Cc: Bernhard R. Link , 988...@bugs.debian.org, Paul Wise , Package Salvaging Team Hi Bernhard, your package bls-standalone was highlighted in the Bug of the Day[1] initiative, which aims to introduce newcomers to manageable tasks and guide them through the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to familiarize newcomers with a consistent Git-based workflow. Usually we file Intend To Salvage bugs[2] if we move some package from no VCS to Salsa. Your package clearly does not fit the ITS criteria and there are no bugs open that urgently need attention. However, the topic of this package is Debian QA and its referencing bls from Paul Wise (in CC). For this reason I consider it helpful to have the package maintained on Salsa. There are quite a number of wishlist bugs and having the repository of this native package in Git on Salsa might motivate developers to contribute. (BTW, the bug tagged patch is fixed in Git.) Thus I've took the freedom to set up a repository within the QA team space[3] to assist you with this initial setup. I'm not sure whether this is the best final location - maybe debian/ team space is a good fit as well and surely this can be moved. I hope this service helps make the transition to using a Git repository on Salsa smoother and more convenient for you. If your time might be limited and you have no capacity to upload the change despite you agree with the new location in principle I can happily do some team upload to announce the new Vcs location (and close bug #988265). Kind regards Andreas. [1] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks [2] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [3] https://salsa.debian.org/qa/bls-standalone -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.10.11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1084827: speech-dispatcher: systemd .service file using Alias= and not symlink
On Wed, 09 Oct 2024 10:44:59 +0200 Laurent Bigonville wrote: Package: speech-dispatcher Version: 0.11.4-2 Severity: serious Tags: sid trixie Hello, The systemd .service file using Alias= and not symlink but as service is not enabled, the symlink is not created. That means that the LSB script and the systemd service are not linked together. Correct, such aliasing symlinks to align sysv and systemd names should be shipped as static symlinks in the package and not be created dynamically. Best is to drop the Alias= statement of the service and create a symlink next to it (speech-dispatcher.service -> speech-dispatcherd.service) In addition to that, any existing, dynamically created symlink in /etc should be removed on upgrades, i.e. /etc/systemd/system/speech-dispatcher.service OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1085354: mbedtls FTBFS on arm64 with gcc 14
Source: mbedtls Version: 3.6.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mbedtls&arch=arm64&ver=3.6.0-3&stamp=1729201458&raw=0 ... In file included from /<>/library/ctr_drbg.c:13: In function ‘mbedtls_xor’, inlined from ‘ctr_drbg_update_internal’ at /<>/library/ctr_drbg.c:372:5: /<>/library/common.h:235:17: error: array subscript 48 is outside array bounds of ‘unsigned char[48]’ [-Werror=array-bounds=] 235 | r[i] = a[i] ^ b[i]; |~^~~ /<>/library/ctr_drbg.c: In function ‘ctr_drbg_update_internal’: /<>/library/ctr_drbg.c:335:19: note: at offset 48 into object ‘tmp’ of size 48 335 | unsigned char tmp[MBEDTLS_CTR_DRBG_SEEDLEN]; | ^~~ In function ‘mbedtls_xor’, inlined from ‘ctr_drbg_update_internal’ at /<>/library/ctr_drbg.c:372:5: /<>/library/common.h:235:24: error: array subscript 48 is outside array bounds of ‘const unsigned char[48]’ [-Werror=array-bounds=] 235 | r[i] = a[i] ^ b[i]; | ~^~~ /<>/library/ctr_drbg.c: In function ‘ctr_drbg_update_internal’: /<>/library/ctr_drbg.c:333:57: note: at offset 48 into object ‘data’ of size [0, 48] 333 | const unsigned char data[MBEDTLS_CTR_DRBG_SEEDLEN]) | ^~ In function ‘mbedtls_xor’, inlined from ‘ctr_drbg_update_internal’ at /<>/library/ctr_drbg.c:372:5: /<>/library/common.h:235:14: error: array subscript 48 is outside array bounds of ‘unsigned char[48]’ [-Werror=array-bounds=] 235 | r[i] = a[i] ^ b[i]; | ~^ /<>/library/ctr_drbg.c: In function ‘ctr_drbg_update_internal’: /<>/library/ctr_drbg.c:335:19: note: at offset 48 into object ‘tmp’ of size 48 335 | unsigned char tmp[MBEDTLS_CTR_DRBG_SEEDLEN]; | ^~~ ... Upstream might be qualified to determine whether this is an mbedtls or gcc bug. The easiest short-term workaround to unblock the transition is export DEB_CFLAGS_MAINT_APPEND = -Wno-error=array-bounds
Bug#1085380: ITP: ciborium -- Lomiri external storage devices manager
Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: ciborium Version : 1.0.0 Upstream Contact: UBports Developers * URL : https://gitlab.com/ubports/development/core/ciborium * License : GPL-3, LGPL-3 Programming Lang: Go, C++ Description : Lomiri external storage devices manager Automatically mounts external storage media such as SD Cards and USB thumbdrives in Lomiri and notifies the user. It also provides a tool for unmounting a formatting media. . This package will be maintained under the umbrella of the Debian UBports Packaging Team.
Bug#1080271: #1080271: podman: please ship the upstream podman-compose.1 manual
On Mon, 9 Sep 2024 14:00:56 +0300 Faidon Liambotis wrote: > On Sun, Sep 01, 2024 at 01:08:07PM +0100, James Addison wrote: > > I'd like to request that we ship the upstream libpod manual[1] instead, and > > optionally that we could retain the podman-compose version of the manual in > > section 7 (misc). Most installers of podman-compose would be provided with > > the > > libpod manual thanks to the Recommends dependency that podman-compose has on > > libpod. >From an user's point of view, I'd rather have them the other way around. Upstream podman manual is just a manual telling users its subcommand does nothing but forwarding the command to an external composer (with a given precedence), and instructing on how to disable the warning. Debian's manual page for podman-compose itself should be more meaningful as a "Executable programs or shell commands" (section 1) manual page. (Although it is currently only a help2man generated page.) Also, this makes more convenient for users, since section 1 has precedence by default over section 7. Doing so would require shipping it as a section 7 manpage, and patching podman source to make messages consistent. I'm afraid upstreaming this might not make sense, though, as podman-compose does not want to maintain a manual page yet [1]; thus no conflict actually exists upstream (yet). Well, this should be way more work to do, though. It would also mean taking care of yet another patch in podman package. It is understandable if it is chosen not to. [1] https://github.com/containers/podman-compose/pull/481 > I actually agree with this, and was also bitten by it recently! It's > worth noting that podman-compose upstream does not ship a manpage at all > -- this is a Debian modification and divergence from upstream. > > For podman to ship this manpage again, podman-compose needs to stop > shipping it, so reassigning the bug to the podman-compose source > package. > > Athos & other podman-compose contributors, what do you think? I'm not a podman-compose contributor myself, but I hope you find my comments useful. Best regards, Henrique F. Simoes
Bug#1081430: FTBFS with Python 3.13
Hi, I've just upload a fix for this bug, but I have not objection to remove it if you consider it. Cheers, Emmanuel signature.asc Description: PGP signature
Bug#1085397: hacktv FTCBFS: uses non-standard variable PKGCONF not passed by debhelper
Source: hacktv Version: 0+git20240812+ds-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs hacktv fails to cross build from source, because it uses the non-standard variable PKGCONF for pkgconf (formerly pkg-config) and debhelper only passes PKG_CONFIG. I'm attaching a patch that performs the renaming for your convenience. Helmut diff --minimal -Nru hacktv-0+git20240812+ds/debian/changelog hacktv-0+git20240812+ds/debian/changelog --- hacktv-0+git20240812+ds/debian/changelog2024-08-12 14:19:43.0 +0200 +++ hacktv-0+git20240812+ds/debian/changelog2024-10-18 21:42:12.0 +0200 @@ -1,3 +1,10 @@ +hacktv (0+git20240812+ds-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Seed PKGCONF variable into the build. (Closes: #-1) + + -- Helmut Grohne Fri, 18 Oct 2024 21:42:12 +0200 + hacktv (0+git20240812+ds-1) unstable; urgency=medium * New upstream version. (Closes: #1072422) diff --minimal -Nru hacktv-0+git20240812+ds/debian/rules hacktv-0+git20240812+ds/debian/rules --- hacktv-0+git20240812+ds/debian/rules2024-08-12 14:19:43.0 +0200 +++ hacktv-0+git20240812+ds/debian/rules2024-10-18 21:42:10.0 +0200 @@ -19,7 +19,7 @@ dh $@ --sourcedirectory=src override_dh_auto_build: - dh_auto_build -- CROSS_HOST=$(DEB_HOST_GNU_TYPE)- + dh_auto_build -- 'PKGCONF=$$(or $$(PKG_CONFIG),pkg-config)' override_dh_auto_test: @echo skipping test
Bug#1085398: RM: agda [armhf] -- ROM; FTBFS due to GHC bug
Package: ftp.debian.org Severity: normal Tags: ftbfs X-Debbugs-Cc: a...@packages.debian.org Control: affects -1 + src:agda User: ftp.debian@packages.debian.org Usertags: remove The agda package FTBFS on armhf, most probably due to a GHC bug. Please remove agda from armhf to allow it to migrate to testing. Thanks, Ilias
Bug#1085383: libngspice0 should depends ngspice in the same version
Carsten,, Robert, libngspice is a shared library version of ngspice, a full simulator like standard ngspice, but depending on a caller for control. libngspice reads spinit, and loads (using the commands 'codemodel ...' in spinit) the shared libraries *.cm at runtime, thus behaving the same as standard ngspice. Due to ongoing development and functions added to the libngspice interface (not deleting or changing existing functions), older versions may not be compatible when the caller (e.g. KiCad Eeschema) is making use of the new functions. Ideally ngspice exe and libngspice would be distributed together with a single compatible version of the *.cm shared library code models. Currently there are Ubuntu users not being able to install standard ngspice (with *cm) and then KiCad (with libngspice and again *.cm) . Overwriting is not allowed, and the ngspice and libngspice versions may be grossly different. Regards Holger Am 18.10.2024 um 20:34 schrieb Carsten Schoenert: Hello Robert, Am Fri, Oct 18, 2024 at 05:41:44PM + schrieb Robert Paciorek: libngspice uses configuration and model files provided by ngspice package (/usr/share/ngspice/scripts/spinit and /usr/lib/x86_64-linux-gnu/ngspice/*.cm). I disagree, the libngsice0 package is only containing the shared libray parts and if the libary would use some external things without depending on it would be programmed in a bad way. $ dpkg -L libngspice0 /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libngspice.so.0.0.10 /usr/share /usr/share/doc /usr/share/doc/libngspice0 /usr/share/doc/libngspice0/changelog.Debian.gz /usr/share/doc/libngspice0/changelog.gz /usr/share/doc/libngspice0/copyright /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/libngspice0 /usr/lib/x86_64-linux-gnu/libngspice.so.0 While the ngspice package is containing the files you mentioned. $ dpkg -S /usr/share/ngspice/scripts/spinit ngspice: /usr/share/ngspice/scripts/spinit $ dpkg -S /usr/lib/x86_64-linux-gnu/ngspice/* ngspice: /usr/lib/x86_64-linux-gnu/ngspice/analog.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/digital.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/spice2poly.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/table.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/xtradev.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/xtraevt.cm * running software used libngspice0 without ngspice installed may results in error "MIF-ERROR - unable to find definition of model and Simulation interrupted due to error!" (with previous warning "Warning: can't find the initialization file spinit") The ngspice binary isn't even depending on any symbol from libngspice libary so dpkg-shlibdeps isn't filling in the library as an dependency. https://packages.debian.org/unstable/ngspice If there is a symbol from there needed then this needs to get fixed upstream. But I'm sure this isn't the case here. Maybe Holger (CCed) can give a better explanation. * running software used libngspice0 with installed ngspice in version different than libngspice0 version (for example libngspice0 43+ds-1~bpo12+1 and ngspice 39.3+ds-1) may cause segmentation fault. You do not provide an example where we could prove your assumption. Without it's impossible to re-adjust a potential misbehavior. Segmentation fault occurs only while referring to standard models provided by *.cm files, for example while simulating digital systems using: A1 [in1 in2] out AND .model AND d_and You might provide what you try to do in detail, Holger can then have a look at this. Holger, I assume you are interested in some samples so you could have a look at? Thanks! Regards Carsten
Bug#1084135: iputils-ping: wrong error message when linux-sysctl-defaults is not installed
On Sat, Oct 05, 2024 at 03:33:19PM +0200, Alban Browaeys wrote: > " > ping argos > ping: socktype: SOCK_RAW > ping: socket: Opération non permise > ping: => missing cap_net_raw+p capability or setuid? > " > > from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008281 I learnt > that it was due to me missing the recommended pacakge > linux-sysctl-defaults (as I have recommends disabled by defaults by the > default DebOps ansible I use to manage my boxes, "APT::Install-Recommends > "false";"). > > But the error from the ping command is misleadingf in that it tells to > revert to set the capability instead of telling to install the > recommended package. (it could tell both as setting the cap could sitll > be a valid local administation policy). Ack. > THis is another bug, probably in linux-sysctl-defaults, I found but > installing linux-sysctl-defaults > does not apply its sysctl settings. Ie one either has to reboot or run > "sysctl --system" to have ping working even after having > linux-sysctl-defaults installed. > Do you know if this is a bug in linux-sysctl-defaults or a Debian > policy not to apply sysctl settings on package install? This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085160 noah
Bug#1085257: diffoscope: Compare ar(1) archives
Hey Alejandro, >> Do you not get the same thing? You may need to install the binutils >> package. > > Humm. I might be in front of a bug? I was trying to see what was the > difference between an archive before and after running ranlib(1) on it. > Maybe that was the issue? Oh, I didn't realise you were seeing a traceback. Could you share your liba2i.a and liba2i_ranlibbed.a files (or provide a way for me to generate these myself) so I can reproduce this locally? Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#1085395: bookworm-pu: package texlive-bin/2022.20220321.62855-5.1+deb12u2
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: texlive-...@packages.debian.org
Control: affects -1 + src:texlive-bin
[ Reason ]
- Fix a security leak.
- Fix a bug, which could lead to data loss (text in documents).
[ Impact ]
The texlive-bin package in Debian stable currently suffers from
the (low) security leak and the bug, which could lead to unexpected
results, when typesettings documents.
[ Tests ]
The texlive-bin package has an own test suite, which is provided
by upstream. It is called at the end of the build.
[ Risks ]
Both patches are contained in Debian unstable for a while, and
thouroughly tested.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in stable
[X] the issue is verified as fixed in unstable
[ Changes ]
- Fix for CVE-2024-25262, which is listes in the Debian Tracker.
- As described in https://tex.stackexchange.com/q/652458
https://tex.stackexchange.com/q/652458, luatex loses or changes
text (not formatting!) in particular circumstances.
[ Other ]
The debdiff is not really minimal, it contains a disabled patch. This
is how it is currently in the git repo. Let me know, if I should create
another package and remove that patch.
diff -Nru texlive-bin-2022.20220321.62855/debian/changelog texlive-bin-2022.20220321.62855/debian/changelog
--- texlive-bin-2022.20220321.62855/debian/changelog 2023-06-27 22:07:12.0 +0200
+++ texlive-bin-2022.20220321.62855/debian/changelog 2024-10-11 22:47:45.0 +0200
@@ -1,3 +1,11 @@
+texlive-bin (2022.20220321.62855-5.1+deb12u2) bookworm; urgency=medium
+
+ * Add patches from upstream for "luatex loses or changes text when
+discretionaries with priorities are used" (Closes: #1041441).
+ * Add patch for CVE-2024-25262.
+
+ -- Hilmar Preuße Fri, 11 Oct 2024 22:47:45 +0200
+
texlive-bin (2022.20220321.62855-5.1+deb12u1) bookworm; urgency=medium
* Stop building *jit* binaries on i386 based arches to make TL installable
diff -Nru texlive-bin-2022.20220321.62855/debian/patches/ad3b0d706c71bb6f3309a236e98e8fb644121bc6.patch texlive-bin-2022.20220321.62855/debian/patches/ad3b0d706c71bb6f3309a236e98e8fb644121bc6.patch
--- texlive-bin-2022.20220321.62855/debian/patches/ad3b0d706c71bb6f3309a236e98e8fb644121bc6.patch 1970-01-01 01:00:00.0 +0100
+++ texlive-bin-2022.20220321.62855/debian/patches/ad3b0d706c71bb6f3309a236e98e8fb644121bc6.patch 2024-10-11 22:41:06.0 +0200
@@ -0,0 +1,90 @@
+From ad3b0d706c71bb6f3309a236e98e8fb644121bc6 Mon Sep 17 00:00:00 2001
+From: Luigi Scarso
+Date: Sat, 30 Jul 2022 14:48:29 +
+Subject: [PATCH] Take exception pre/port disc font from wordstart (H.Hagen).
+ Fixed some missed files in trunk from latest update from TexLive
+
+[[Split portion of a mixed commit.]]
+---
+ source/texk/web2c/luatexdir/ChangeLog | 3 ++
+ source/texk/web2c/luatexdir/lang/texlang.c| 28 +--
+ .../texk/web2c/luatexdir/luatex_svnversion.h | 2 +-
+ 3 files changed, 24 insertions(+), 9 deletions(-)
+
+diff --git a/source/texk/web2c/luatexdir/lang/texlang.c b/source/texk/web2c/luatexdir/lang/texlang.c
+index 67ef25ca1..f9e53bbba 100644
+--- a/texk/web2c/luatexdir/lang/texlang.c
b/texk/web2c/luatexdir/lang/texlang.c
+@@ -358,7 +358,9 @@ static halfword insert_discretionary(halfword t, halfword pre, halfword post, ha
+ f = get_cur_font();
+ }
+ for (g = pre; g != null; g = vlink(g)) {
+-font(g) = f;
++if (! font(g)) {
++font(g) = f;
++}
+ if (attr != null) {
+ delete_attribute_ref(node_attr(g));
+ node_attr(g) = attr;
+@@ -366,7 +368,9 @@ static halfword insert_discretionary(halfword t, halfword pre, halfword post, ha
+ }
+ }
+ for (g = post; g != null; g = vlink(g)) {
+-font(g) = f;
++if (! font(g)) {
++font(g) = f;
++}
+ if (attr != null) {
+ delete_attribute_ref(node_attr(g));
+ node_attr(g) = attr;
+@@ -531,9 +535,14 @@ char *exception_strings(struct tex_language *lang)
+ The sequence from |wordstart| to |r| can contain only normal characters it
+ could be faster to modify a halfword pointer and return an integer
+
++We now take the font from the wordstart (as in \LUAMETATEX) but leave the
++rest as it is, because we don't want to break compatibility (end June 2022).
++We make a copy now of the parent and hope for the best. Backporting would be
++too intrusive so this has to do. It went unnoticed for ages anyway.
++
+ */
+
+-static halfword find_exception_part(unsigned int *j, unsigned int *uword, int len)
++static halfword find_exception_part(unsigned int *j, unsigned int *uword, int len, halfword parent)
+ {
+ halfword g = null, gg = null;
+ register unsigned i = *j;
+@@ -541,13 +550,16 @
Bug#1085355: icinga2-common: command-plugins.conf defines command line options for check_dns which do not exist
Package: icinga2-common
Version: 2.14.2-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
in /usr/share/icinga2/include/command-plugins.conf there is a definition
for a "dns" check using /usr/lib/nagios/plugins/check_dns (from
monitoring-plugins-basic) and defines a command line option which
the check_dns does not support - For example the "-q" for
query type (I didnt try more).
I am unshure whether this is an issue in an old check_dns beeing
distributed by monitoring-plugins-basic - or the "-q" beeing falsely
added to the icinga2-common plugins definition:
object CheckCommand "dns" {
import "ipv4-or-ipv6"
command = [ PluginDir + "/check_dns" ]
arguments = {
"-H" = {
value = "$dns_lookup$"
description = "The name or address you want to query."
}
"-s" = {
value = "$dns_server$"
description = "Optional DNS server you want to use for
the lookup."
}
"-q" = {
value = "$dns_query_type$"
description = "Optional DNS record query type where
TYPE =(A, , SRV, TXT, MX, ANY). The default query type is 'A' (IPv4 host
entry)"
}
[ ... ]
root@trixie-95838:# /usr/lib/nagios/plugins/check_dns -q
/usr/lib/nagios/plugins/check_dns: invalid option -- 'q'
Usage:
check_dns -H host [-s server] [-a expected-address] [-n] [-A] [-t timeout] [-w
warn] [-c crit] [-L]
Flo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEdb9o7oebX2papQ/KkN1BIMsJ8i8FAmcShaoACgkQkN1BIMsJ
8i9+lA//eHGIgbXOls0DiC8Cd51P7q8W3aQRu8sAcExbbqtUc8aFnoFsAw5BldWk
PBmhDOYKVllNHsN1j30sh6RvSPKzF2KvgTJ8CduiQInJzKaenCv3iY6yaduflQIS
AgjyQHiQI+xlMIjHyAVMWdNHy6IuC1Wd6ju4WSrAF4xern4Lhh6bhNoELJVpv5/Q
WdL8vd1CMIyWpldkuuH+xm3GTATBSrO946i+diUoC0FvZ5xTbOmvInWcfcTN0GEh
DW3jp2fl5G85/Gw+caAe1wLwqcLNKeIGBCaovqhRDtRLnX89m/K3GFzZDTaAVWhU
Ns3fzvNU8OP5xlf1l6lwRBiQMLtvyYyFxwEvQJaWeZ8E1I4VHj97gr0KHhJuCYsc
eGjcIzyJQp/d/4UT92udybmtNLsjuFu5TB0O4dbNzYR9X/3826SOEbTydi4oB4h5
PeyrSSaadreZROVYxt2VRTJOj8EdvUom/GWsxEB7Mdwfy0NOgiVk+rZ5hueFfA3M
02r5+uoeLDbxpUbqrStaowOA4UkCrariGRaL1N263YtCr5jBW2CMQzk+FQ9rg+Ta
/Qx/4/WkouuySU38TNI8BhQpwLE3EB5F/Tu5zyCX3Yzc+BVNTo6ujVCxrkROuBaA
1IHZtVmrw0m2tLRwWWh8P1pWrdWla2Cq/P/p2yY8pILWkNGpwO0=
=IaCs
-END PGP SIGNATURE-
Bug#1085228: zutty should not Provides: x-terminal-emulator
Am Wed, Oct 16, 2024 at 07:58:16PM -0400, schrieb Jesse Rhodes: > I believe this is actually an apt bug, so copying deity, but maybe you'll see > my point: > > There is a difficult-to-reproduce condition where some other package > Depends/Recommends x-terminal-emulator, and via dependency resolution, apt > installs zutty to satisfy it. […] > I suspect without evidence that apt is reverse sorting the list with the goal > of selecting xterm. apt has no such goal. It doesn't know nor cares what a terminal emulator is nor has it a preference for one. Sorting provides is indeed a complicated matter and MIGHT produce something that looks like a reverse sorting, but that is neither the goal nor intended as such. https://salsa.debian.org/apt-team/apt/-/blob/main/apt-pkg/depcache.cc?ref_type=heads#L1139-1227 We have mainly four options here: 1. The bug is in "some package" that "Depends/Recommends x-terminal-emulator" (your words) as it should mention the default [which one?] first according to Debian Policy §7.5. Perhaps that default [again, which one?] should have a higher priority. 2. User error, they should pick a x-terminal-emulator first 3. apt should implement something akin to mind reading figuring out somehow which x-terminal-emulator is the right one given this particular system (which is so unspecific that it doesn't even have an x-terminal-emulator installed) and especially the user operating it. 4. Somewhat mix 2 and 3 by having apt somehow figure out that for this user the choice in this case is important enough to bother them with it. (While other users will be annoyed if not downright confused by it) Never mind that the concept of asking back doesn't exist in apt nor that something like that would never work with less linear/heuristic solver strategies. While I would theoretically prefer 3 (failing that 4) the most practical option is 2 – because the overwhelming amount of users has long 'picked' up at least one if not many x-terminal-emulators by installing one or twenty of the more popular desktop environments shipped by Debian before an apt call has to reason about resolving x-terminal-emulator. > [1] https://file.sney.ca/txt/1cq4/ Looks like aptitude output… anyway, that is one possible route, maybe even the quickest to find, but even if that feature is called "why" very often it is not printing the reason for why something was installed because IF (and that is a really big if) that information was ever known, it is not recorded, but "why" something is not autoremoved. I wonder a bit if libfile-desktopentry-perl really needs to have that recommends, but it probably is not technically wrong. I haven't looked at all at zutty, so I can't comment on if the Provides is correct or not – Debian policy is rather specific on what is needed to set that Provides, so if it doesn't this bug would be RC level: https://www.debian.org/doc/debian-policy/ch-customized-programs.html#packages-providing-a-terminal-emulator Best regards David Kalnischkies signature.asc Description: PGP signature
Bug#1085400: glab: FTBFS: src/gitlab.com/gitlab-org/cli/api/project.go:24:48: not enough arguments in call to client.Projects.DeleteProject
Package: src:glab Version: 1.47.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- -ldflags "-X main.version=v1.47.0 -X main.build=1728109175 -X main.usageMode=prod" cd _build && go install -trimpath -v -p 2 -ldflags "-X main.version=v1.47.0 -X main.build=1728109175 -X main.usageMode=prod" gitlab.com/gitlab-org/cli/api gitlab.com/gitlab-org/cli/api/request gitlab.com/gitlab-org/cli/cmd/gen-docs gitlab.com/gitlab-org/cli/cmd/glab gitlab.com/gitlab-org/cli/commands gitlab.com/gitlab-org/cli/commands/alias gitlab.com/gitlab-org/cli/commands/alias/delete gitlab.com/gitlab-org/cli/commands/alias/expand gitlab.com/gitlab-org/cli/commands/alias/list gitlab.com/gitlab-org/cli/commands/alias/set gitlab.com/gitlab-org/cli/commands/api gitlab.com/gitlab-org/cli/commands/auth gitlab.com/gitlab-org/cli/commands/auth/authutils gitlab.com/gitlab-org/cli/commands/auth/login gitlab.com/gitlab-org/cli/commands/auth/status gitlab.com/gitlab-org/cli/commands/changelog gitlab.com/gitlab-org/cli/commands/changelog/generate gitlab.com/gitlab-org/cli/commands/ci gitlab.com/gitlab-org/cli/commands/ci/artifact gitlab.com/gitlab-org/cli/commands/ci/ciutils gitlab.com/gitlab-org/cli/commands/ci/config gitlab.com/gitlab-org/cli/commands/ci/config/compile gitlab.com/gitlab-org/cli/commands/ci/delete gitlab.com/gitlab-org/cli/commands/ci/get gitlab.com/gitlab-org/cli/commands/ci/legacyci gitlab.com/gitlab-org/cli/commands/ci/lint gitlab.com/gitlab-org/cli/commands/ci/list gitlab.com/gitlab-org/cli/commands/ci/retry gitlab.com/gitlab-org/cli/commands/ci/run gitlab.com/gitlab-org/cli/commands/ci/run_trig gitlab.com/gitlab-org/cli/commands/ci/status gitlab.com/gitlab-org/cli/commands/ci/trace gitlab.com/gitlab-org/cli/commands/ci/trigger gitlab.com/gitlab-org/cli/commands/ci/view gitlab.com/gitlab-org/cli/commands/cluster gitlab.com/gitlab-org/cli/commands/cluster/agent gitlab.com/gitlab-org/cli/commands/cluster/agent/agentutils gitlab.com/gitlab-org/cli/commands/cluster/agent/bootstrap gitlab.com/gitlab-org/cli/commands/cluster/agent/check_manifest_usage gitlab.com/gitlab-org/cli/commands/cluster/agent/get_token gitlab.com/gitlab-org/cli/commands/cluster/agent/list gitlab.com/gitlab-org/cli/commands/cluster/agent/update_kubeconfig gitlab.com/gitlab-org/cli/commands/cmdtest gitlab.com/gitlab-org/cli/commands/cmdutils gitlab.com/gitlab-org/cli/commands/completion gitlab.com/gitlab-org/cli/commands/config gitlab.com/gitlab-org/cli/commands/duo gitlab.com/gitlab-org/cli/commands/duo/ask gitlab.com/gitlab-org/cli/commands/flag gitlab.com/gitlab-org/cli/commands/help gitlab.com/gitlab-org/cli/commands/incident gitlab.com/gitlab-org/cli/commands/incident/close gitlab.com/gitlab-org/cli/commands/incident/list gitlab.com/gitlab-org/cli/commands/incident/note gitlab.com/gitlab-org/cli/commands/incident/reopen gitlab.com/gitlab-org/cli/commands/incident/subscribe gitlab.com/gitlab-org/cli/commands/incident/unsubscribe gitlab.com/gitlab-org/cli/commands/incident/view gitlab.com/gitlab-org/cli/commands/issuable gitlab.com/gitlab-org/cli/commands/issuable/close gitlab.com/gitlab-org/cli/commands/issuable/list gitlab.com/gitlab-org/cli/commands/issuable/note gitlab.com/gitlab-org/cli/commands/issuable/reopen gitlab.com/gitlab-org/cli/commands/issuable/subscribe gitlab.com/gitlab-org/cli/commands/issuable/unsubscribe gitlab.com/gitlab-org/cli/commands/issuable/view gitlab.com/gitlab-org/cli/commands/issue gitlab.com/gitlab-org/cli/commands/issue/board gitlab.com/gitlab-org/cli/commands/issue/board/create gitlab.com/gitlab-org/cli/commands/issue/board/view gitlab.com/gitlab-org/cli/commands/issue/close gitlab.com/gitlab-org/cli/commands/issue/create gitlab.com/gitlab-org/cli/commands/issue/delete gitlab.com/gitlab-org/cli/commands/issue/issueutils gitlab.com/gitlab-org/cli/commands/issue/list gitlab.com/gitlab-org/cli/commands/issue/note gitlab.com/gitlab-org/cli/commands/issue/reopen gitlab.com/gitlab-org/cli/commands/issue/subscribe gitlab.com/gitlab-org/cli/commands/issue/unsubscribe gitlab.com/gitlab-org/cli/commands/issue/update gitlab.com/gitlab-org/cli/commands/issue/view gitlab.com/gitlab-org/cli/commands/job gitlab.com/gitlab-org/cli/commands/job/artifact gitlab.com/gitlab-org/cli/commands/label gitlab.com/gitlab-org/cli/commands/label/create gitlab.com/gitlab-org/cli/commands/label/list gitlab.com/gitlab-org/cli/commands/mr gitlab.
Bug#1085383: libngspice0 should depends ngspice in the same version
Hi Carsten,
thanks for reply!
On 2024-10-18 20:34:26 Carsten Schoenert wrote:
> Hello Robert,
>
> Am Fri, Oct 18, 2024 at 05:41:44PM + schrieb Robert Paciorek:
>
> > libngspice uses configuration and model files provided by ngspice
> > package (/usr/share/ngspice/scripts/spinit and
> > /usr/lib/x86_64-linux-gnu/ngspice/*.cm).
>
> I disagree, the libngsice0 package is only containing the shared
> libray parts and if the libary would use some external things without
> depending on it would be programmed in a bad way.
These files are part of the official library archives from
sourceforge.net
(https://sourceforge.net/projects/ngspice/files/ng-spice-rework/43/ngspice-43_dll_64.7z).
> > * running software used libngspice0 without ngspice installed may
> > results in error "MIF-ERROR - unable to find definition of model
> > and Simulation interrupted due to error!" (with previous warning
> > "Warning: can't find the initialization file spinit")
>
> The ngspice binary isn't even depending on any symbol from libngspice
> libary so dpkg-shlibdeps isn't filling in the library as an
> dependency.
>
> https://packages.debian.org/unstable/ngspice
Yes, ngspice is not depending on symbols from libngspice.
It is libngspice that (in some scenarios) uses files provided only with
ngspice package (perhaps they should be in a separate package, e.g.
ngspice-data, because they are used also by the ngspice executable).
> If there is a symbol from there needed then this needs to get fixed
> upstream. But I'm sure this isn't the case here. Maybe Holger (CCed)
> can give a better explanation.
>
> > * running software used libngspice0 with installed ngspice in
> > version different than libngspice0 version (for example libngspice0
> > 43+ds-1~bpo12+1 and ngspice 39.3+ds-1) may cause segmentation
> > fault.
>
> You do not provide an example where we could prove your assumption.
> Without it's impossible to re-adjust a potential misbehavior.
>
> > Segmentation fault occurs only while referring to standard models
> > provided by *.cm files, for example while simulating digital
> > systems using:
> >
> > A1 [in1 in2] out AND
> > .model AND d_and
>
> You might provide what you try to do in detail, Holger can then have a
> look at this.
I'm attaching the source code of simple program used libngspice
(gdspice.cpp) and two netlist files:
- digital.netlist - simple digital circuit (used standard ngspice model
for AND gate via `.model` command)
- analog.netlist - similar (but analog, without `.model` command)
circuit
`gdspice.cpp` can load libngspice via dlopen (default, build via `g++
gdspice.cpp`) or can be linked with libngspice on build time (unset
USE_DLOPEN macro and build via `g++ gdspice-nogodot.cpp -lngspice`).
This allow test all 3 scenarios:
1. The same version (43+ds-1~bpo12+1) of libngspice0 and ngspice
packages:
-> both circuit are simulated.
2. Installed only libngspice0 (still 43+ds-1~bpo12+1, but ngspice is not
installed):
-> analog circuit produce warning about spinit, but is simulated,
-> digital circuit produce error about missed definition of model
and is not simulated.
3. Different version of libngspice0 (43+ds-1~bpo12+1) and ngspice
(39.3+ds-1):
-> analog circuit is simulated (no warning),
-> digital circuit cause segmentation fault inside libngspice0.
Using strace shows that *.cm files are opened even though they are not
referenced in the program source code (they are used internally by the
library, due to content of the default `spinit` file, also internally
referenced via libngspice).
Regards
Robert
> Holger, I assume you are interested in some samples so you could have
> a look at? Thanks!
>
> Regards
> Carsten
>
digital.netlist
Description: Binary data
analog.netlist
Description: Binary data
// SPDX-FileCopyrightText: Robert Ryszard Paciorek
// SPDX-License-Identifier: MIT
#include
#include
#define USE_DLOPEN
#ifdef USE_DLOPEN
#include
extern "C" {
typedef int (*ngSpice_Init_Type) (SendChar*, SendStat*, ControlledExit*, SendData*, SendInitData*, BGThreadRunning*, void*);
typedef int (*ngSpice_Init_Sync_Type) (GetVSRCData*, GetISRCData*, GetSyncData*, int*, void*);
typedef int (*ngSpice_Command_Type) (char*);
}
#endif
struct GdSpice {
GdSpice(const char* libngspice = "libngspice.so") {
#ifdef USE_DLOPEN
ngSpice_dll = dlopen(libngspice, RTLD_NOW);
if (!ngSpice_dll) {
throw std::runtime_error("can't load libngspice.so");
}
ngSpice_Init = reinterpret_cast(dlsym(ngSpice_dll, "ngSpice_Init"));
ngSpice_Init_Sync = reinterpret_cast(dlsym(ngSpice_dll, "ngSpice_Init_Sync"));
ngSpice_Command = reinterpret_cast(dlsym(ngSpice_dll, "ngSpice_Command"));
if (!ngSpice_Init || !ngSpice_Command) {
throw std::runtime_error("missed function in libngspice.so");
}
#endif
int ret = ngSpice_Init(on_getchar, /*on_getstat*/ nullptr, /*on_exit*/ nullptr, /*on_data*/ nullptr, /*on_initdata*/ nullptr, /*on_thread_runs*/ nullptr
Bug#1085396: ttyplot FTCBFS: hard codes the build architecture pkg-config
Source: ttyplot Version: 1.6.1-1 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs ttyplot fails to cross build from source, because the upstream Makefile hard codes the build architecture pkg-config. I'm attaching a patch to make it substitutable for your convenience. Helmut --- ttyplot-1.6.1.orig/Makefile +++ ttyplot-1.6.1/Makefile @@ -1,9 +1,10 @@ DESTDIR ?= PREFIX?= /usr/local MANPREFIX ?= $(PREFIX)/man +PKG_CONFIG ?= pkg-config CFLAGS += -Wall -Wextra -CFLAGS += `pkg-config --cflags ncursesw` -LDLIBS += `pkg-config --libs ncursesw` -lm +CFLAGS += `$(PKG_CONFIG) --cflags ncursesw` +LDLIBS += `$(PKG_CONFIG) --libs ncursesw` -lm all: ttyplot stresstest @@ -21,7 +22,7 @@ rm -f ttyplot stresstest .c: - @pkg-config --version > /dev/null + @$(PKG_CONFIG) --version > /dev/null $(CC) $(CFLAGS) $(LDFLAGS) $< $(LDLIBS) -o $@ .PHONY: all clean install uninstall
Bug#1085403: aardvark-dns - upcoming rust-nix update.
Package: aardvark-dns
Version: 1.12.2-1
I hope to update rust-nix to version 0.29 soon. I've prpared a patch
for aardvark-dns. The patch is pretty trivial but unfortunately the
nature of the API change made it impractical to support both old
and new versions in the patch.
I was able to succesfully build the package, if you want to do
further testing, the new rust-nix is available in experimental.
Debdiff is attatched.diff -Nru aardvark-dns-1.12.2/debian/cargo-checksum.json
aardvark-dns-1.12.2/debian/cargo-checksum.json
--- aardvark-dns-1.12.2/debian/cargo-checksum.json 1970-01-01
00:00:00.0 +
+++ aardvark-dns-1.12.2/debian/cargo-checksum.json 2024-10-19
01:11:38.0 +
@@ -0,0 +1 @@
+{"package":"dcbb59495599b679d9e729ebf985b08b482823209f91e7a5a82032d31183acbb","files":{}}
diff -Nru aardvark-dns-1.12.2/debian/changelog
aardvark-dns-1.12.2/debian/changelog
--- aardvark-dns-1.12.2/debian/changelog2024-09-06 00:50:47.0
+
+++ aardvark-dns-1.12.2/debian/changelog2024-10-19 01:11:38.0
+
@@ -1,3 +1,10 @@
+aardvark-dns (1.12.2-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch for nix 0.29.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 01:11:38 +
+
aardvark-dns (1.12.2-1) unstable; urgency=medium
* New upstream relase.
diff -Nru aardvark-dns-1.12.2/debian/control aardvark-dns-1.12.2/debian/control
--- aardvark-dns-1.12.2/debian/control 2024-09-06 00:50:47.0 +
+++ aardvark-dns-1.12.2/debian/control 2024-10-19 01:11:38.0 +
@@ -15,7 +15,7 @@
librust-hickory-client-dev,
librust-hickory-proto-dev,
librust-hickory-server-dev,
- librust-nix-dev,
+ librust-nix-0.29-dev,
librust-resolv-conf-dev,
librust-signal-hook-dev,
librust-strsim-dev,
diff -Nru aardvark-dns-1.12.2/debian/patches/nix-0.29.patch
aardvark-dns-1.12.2/debian/patches/nix-0.29.patch
--- aardvark-dns-1.12.2/debian/patches/nix-0.29.patch 1970-01-01
00:00:00.0 +
+++ aardvark-dns-1.12.2/debian/patches/nix-0.29.patch 2024-10-19
01:11:38.0 +
@@ -0,0 +1,27 @@
+Index: aardvark-dns-1.12.2/Cargo.toml
+===
+--- aardvark-dns-1.12.2.orig/Cargo.toml
aardvark-dns-1.12.2/Cargo.toml
+@@ -31,7 +31,7 @@ hickory-client = "0.24.1"
+ futures-util = { version = "0.3.30", default-features = false }
+ tokio = { version = "1.39.2", features = ["macros", "rt-multi-thread", "net",
"signal"] }
+ resolv-conf = "0.7.0"
+-nix = { version = "0.27", features = ["fs", "signal"] }
++nix = { version = "0.29", features = ["fs", "signal"] }
+ libc = "0.2.154"
+ arc-swap = { version = ">= 1.6" }
+ flume = "0.11.0"
+Index: aardvark-dns-1.12.2/src/server/serve.rs
+===
+--- aardvark-dns-1.12.2.orig/src/server/serve.rs
aardvark-dns-1.12.2/src/server/serve.rs
+@@ -92,8 +92,7 @@ pub async fn serve(
+ // to work but this is not really possible with the current code flow and
needs more changes.
+ daemonize()?;
+ let msg: [u8; 1] = [b'1'];
+-let ready_fd = ready.as_raw_fd();
+-unistd::write(ready_fd, &msg)?;
++unistd::write(&ready, &msg)?;
+ drop(ready);
+
+ loop {
diff -Nru aardvark-dns-1.12.2/debian/patches/series
aardvark-dns-1.12.2/debian/patches/series
--- aardvark-dns-1.12.2/debian/patches/series 2024-09-06 00:50:47.0
+
+++ aardvark-dns-1.12.2/debian/patches/series 2024-10-19 01:10:39.0
+
@@ -1,3 +1,4 @@
relax-deps.patch
nix-0.27.patch
0003-Disable-failing-tests.patch
+nix-0.29.patch
Bug#1085404: bpftop - upcoming rust-nix update
Package: bpftop
Version: 0.5.2.9.ga1b99d7-1
I hope to update rust-nix to version 0.29 soon, the Debian
build-dependencies for your package allow the new version
but the cargo dependencies do not. After relaxing the
Cargo dependency I was able to build bpftop succesfully
against the new version of nix.
A debdiff is attatched and the new version of nix is
available in experimental if you want to do further
testing.diff -Nru bpftop-0.5.2.9.ga1b99d7/debian/changelog
bpftop-0.5.2.9.ga1b99d7/debian/changelog
--- bpftop-0.5.2.9.ga1b99d7/debian/changelog2024-10-01 21:07:58.0
+
+++ bpftop-0.5.2.9.ga1b99d7/debian/changelog2024-10-19 01:40:22.0
+
@@ -1,3 +1,10 @@
+bpftop (0.5.2.9.ga1b99d7-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax cargo dependency on nix.
+
+ -- Peter Michael Green Sat, 19 Oct 2024 01:40:22 +
+
bpftop (0.5.2.9.ga1b99d7-1) unstable; urgency=medium
* Run autopkgtest on isolation-machine.
diff -Nru bpftop-0.5.2.9.ga1b99d7/debian/patches/fix-version.patch
bpftop-0.5.2.9.ga1b99d7/debian/patches/fix-version.patch
--- bpftop-0.5.2.9.ga1b99d7/debian/patches/fix-version.patch2024-10-01
21:06:57.0 +
+++ bpftop-0.5.2.9.ga1b99d7/debian/patches/fix-version.patch2024-10-19
01:39:52.0 +
@@ -10,7 +10,7 @@
+anyhow = "1.0.86"
ratatui = { version = "0.28.1", default-features = false, features =
['crossterm'] }
-nix = { version = "0.29.0", features = ["user"] }
-+nix = { version = "0.27.1", features = ["user"] }
++nix = { version = ">= 0.27.1", features = ["user"] }
circular-buffer = "0.1.7"
-procfs = "0.16.0"
+procfs = "0.14.2"
Bug#1085160: linux-sysctl-defaults: apply setting after installation
Control: severity -1 important Control: affects -1 iputils-ping On Tue, Oct 15, 2024 at 07:04:51PM +0300, sergio wrote: > please call `sysctl -p /usr/lib/sysctl.d/50-default.conf` after installation +1 Not doing so is leading to confusing/broken behavior during upgrades. By deferring the application of the sysctl settings until reboot, we're effectively leaving the system in a half-upgraded state where applications that depend on sysctls set here will misbehave for confusing reasons until a reboot happens. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085289 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084135 for instances of issues caused during upgrades. noah
Bug#1085388: ITP: einops -- Flexible and powerful tensor operations for readable and reliable code.
Hi! On Fri, 2024-10-18 at 12:03:46 -0700, Mo Zhou wrote: > Package: wnpp > Severity: wishlist > Owner: Mo Zhou > X-Debbugs-Cc: debian-de...@lists.debian.org > > * Package name : einops > * URL : https://einops.rocks > * License : MIT/Expat > Programming Lang: Python > Description : Flexible and powerful tensor operations for readable and > reliable code. > > Flexible and powerful tensor operations for readable and reliable code. > Supports numpy, pytorch, tensorflow, jax, and others. This seems to be a python module only upstream, but the source package name listed above is not currently namespaced. Given that it has not yet been uploaded nor passed NEW, please namespace it with python- to avoid taking on the global namespace, so that we do not "prevent" packaging something that for example installs a command with the same name (or having to end up using a non-obvious one for that, or requiring a future rename), so that it's easier to see what it is about when doing archive-wide analysis from Sources, or dd-lists, or even reading changelogs via stuff like apt-listchanges, like the rest of the language specific teams are doing. :) Thanks, Guillem
Bug#1084506: closed by Debian FTP Masters (reply to Petter Reinholdtsen ) (Bug#1084506: fixed in suck 4.3.5-2)
I am very happy to see you also took the package under your wings and that the salsa git repo was helpful. :) -- Happy hacking Petter Reinholdtsen
Bug#1085328: arriero: Python SyntaxWarning
Source: arriero
Version: 0.7~20161228-1.2
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/a/arriero.html
Setting up arriero (0.7~20161228-1.2) ...
/usr/lib/python3/dist-packages/arriero/actions.py:1031:
SyntaxWarning: invalid escape sequence '\+'
m = re.match('^(.*)\+b[0-9]+$', version)
/usr/lib/python3/dist-packages/arriero/config.py:240: SyntaxWarning:
"is not" with 'str' literal. Did you mean "!="?
value = filter(lambda x: x is not '', value.split('\n'))
/usr/lib/python3/dist-packages/arriero/util.py:232: SyntaxWarning:
"is not" with 'str' literal. Did you mean "!="?
return list(filter(lambda x: x is not '', re.split(r'[\s,]+', values)))
Bug#1085326: arden: Python SyntaxWarning
Source: arden
Version: 1.0-5
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/a/arden.html
Setting up python3 (3.12.6-1) ...
/usr/share/arden/core/AnalyseMapping.py:169: SyntaxWarning: invalid
escape sequence '\d'
mism = sum([i.size for i in cigar if i.type=="M"]) -
getsum(re.findall("(\d+)", alngt.optional_field("MD")))
/usr/share/arden/core/AnalyseMapping.py:252: SyntaxWarning: invalid
escape sequence '\d'
deletions = getsum(re.findall("(\d+)D", cigar))
/usr/share/arden/core/AnalyseMapping.py:253: SyntaxWarning: invalid
escape sequence '\d'
insertions = getsum(re.findall("(\d+)I", cigar))
/usr/share/arden/core/AnalyseMapping.py:260: SyntaxWarning: invalid
escape sequence '\d'
mismatch = getsum(re.findall("(\d+)M", cigar)) -
getsum(re.findall("(\d+)", mdtag))
/usr/share/arden/core/AnalyseMapping.py:260: SyntaxWarning: invalid
escape sequence '\d'
mismatch = getsum(re.findall("(\d+)M", cigar)) -
getsum(re.findall("(\d+)", mdtag))
/usr/share/arden/core/AnalyseMapping.py:651: SyntaxWarning: invalid
escape sequence '\d'
m = re.search(tag + ":i:(\d+)", line)
/usr/share/arden/core/AnalyseMapping.py:717: SyntaxWarning: invalid
escape sequence '\d'
match = re.findall("(\d+)[MDN]", cigar)
/usr/share/arden/core/AnalyseMapping.py:917: SyntaxWarning: invalid
escape sequence '\s'
mdtag = re.search("MD:Z:([^\s]+)", tags).group(1)
/usr/share/arden/core/AnalyseMapping.py:919: SyntaxWarning: invalid
escape sequence '\s'
mdtag = re.search("MD:Z:([^\s]+)", tags).group(1)
Bug#1081111: ITP: sphinx-toolbox -- Box of handy tools for Sphinx
Hi! On Sun, 2024-09-08 at 08:55:58 +0530, Kathara Sasikumar wrote: > Package: wnpp > Severity: wishlist > Owner: Kathara Sasikumar > X-Debbugs-Cc: debian-de...@lists.debian.org > > * Package name: sphinx-toolbox > Version : 3.8.0 > Upstream Contact: Dominic Davis-Foster > * URL : https://github.com/sphinx-toolbox/sphinx-toolbox > * License : Expat > Programming Lang: Python > Description : Box of handy tools for Sphinx > > Sphinx-Toolbox is a collection of extensions that improve Sphinx's > features, making it easier to organize and present Python projects. > > I intend to maintain this package within the DPT. This seems to be a python module only package, but its source package name is not currently namespaced. Given that it has not yet passed NEW, please namespace it with python- to avoid taking on the global namespace, so that we do not "prevent" packaging something that for example installs a command with the same name (or having to end up using a non-obvious one for that, or requiring a future rename), so that it's easier to see what it is about when doing archive-wide analysis from Sources, or dd-lists, or even reading changelogs via stuff like apt-listchanges, like the rest of the language specific teams are doing. :) Thanks, Guillem
Bug#1085325: apycula: Python SyntaxWarning
Source: apycula
Version: 0.14+dfsg1-1
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/a/apycula.html
Setting up python3-apycula (0.14+dfsg1-1) ...
/usr/lib/python3/dist-packages/apycula/gowin_pack.py:68:
SyntaxWarning: invalid escape sequence '\{'
return f"\{retname} "
Bug#1083034: fuseiso: bizarre restrixion on where -o options go?
Control: tags -1 + wontfix On Mon, 30 Sep 2024 12:47:08 +0200 наб wrote: > Package: fuseiso > Version: 20070708-4 > Severity: normal > Tags: upstream > > Dear Maintainer, > > $ fuseiso solaris_2.2_sparc.iso . > init: primary volume descriptor already found, skipping.. > fuse: mountpoint is not empty > fuse: if you are sure this is safe, use the 'nonempty' mount option > $ fuseiso -o nonempty solaris_2.2_sparc.iso . > fuseiso: invalid option -- 'o' > > I was as surprised as anyone to see that the SYNOPSIS says > fuseiso [options] [FUSE library options] > and the only accepted usage is > $ fuseiso solaris_2.2_sparc.iso . -o nonempty > which is inconsistent with every other FUSE program, > and ideologically violates the USG > (since you're passing options and option-arguments > (a) not where they go, and (b) as-if they were arguments). You are absolutely right. I stumbled over this misfeature myself a while ago. Unfortunately a complete rewrite of the command line parsing code would be necessary to fix it while upstream has been inactive for more than a decade. Given that noone brought this up during all these years I am opposed to correct it now myself. Sven
Bug#1064886: Fixed #1064886
Fixed during BSP 2024 in Salzburg
diff -Nru sqlite-utils-3.30/debian/changelog sqlite-utils-3.30/debian/changelog
--- sqlite-utils-3.30/debian/changelog 2024-10-18 14:32:50.0 +0200
+++ sqlite-utils-3.30/debian/changelog 2022-11-01 16:02:33.0 +0100
@@ -1,11 +1,3 @@
-sqlite-utils (3.30-1.1) UNRELEASED; urgency=medium
-
- * Non-maintainer upload.
- * Fixed missing dependency on python3-click-default-group (closes:
-#1064886).
-
- --Fri, 18 Oct 2024 14:32:50 +0200
-
sqlite-utils (3.30-1) unstable; urgency=medium
* New upstream release.
diff -Nru sqlite-utils-3.30/debian/control sqlite-utils-3.30/debian/control
--- sqlite-utils-3.30/debian/control 2024-10-18 14:27:28.0 +0200
+++ sqlite-utils-3.30/debian/control 2022-10-01 16:30:20.0 +0200
@@ -25,10 +25,7 @@
Package: sqlite-utils
Architecture: all
-Depends: python3-click-default-group,
- ${misc:Depends},
- ${python3:Depends},
- ${sphinxdoc:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}, ${sphinxdoc:Depends}
Built-Using: ${sphinxdoc:Built-Using}
Description: CLI tool and Python utility functions for manipulating SQLite
Feature highlights:
Bug#1085327: arpys: Python SyntaxWarning
Source: arpys Version: 1:1.0.0~git20230217101414.07b63b3-1 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/a/arpys.html Setting up python3-arpys (1:1.0.0~git20230217101414.07b63b3-1) ... /usr/lib/python3/dist-packages/arpys/postprocessing.py:1650: SyntaxWarning: invalid escape sequence '\ ' """ Implement a perfect step function f(x) with step at `step_x`:: /usr/lib/python3/dist-packages/arpys/postprocessing.py:1684: SyntaxWarning: invalid escape sequence '\ ' """ Implement a step function f(x) with step at `step_x`:: /usr/lib/python3/dist-packages/arpys/postprocessing.py:1709: SyntaxWarning: invalid escape sequence '\ ' """ /usr/lib/python3/dist-packages/arpys/postprocessing.py:1741: SyntaxWarning: invalid escape sequence '\ ' """ /usr/lib/python3/dist-packages/arpys/postprocessing.py:1785: SyntaxWarning: invalid escape sequence '\ ' """ Implement (as a broadcastable np.ufunc) a sort-of convolution of a /usr/lib/python3/dist-packages/arpys/postprocessing.py:2365: SyntaxWarning: "is not" with 'int' literal. Did you mean "!="? if len(kxs_ib) is not 0 : /usr/lib/python3/dist-packages/arpys/postprocessing.py:2370: SyntaxWarning: "is not" with 'int' literal. Did you mean "!="? if len(kys_ib) is not 0 :
Bug#1085360: behave: Python SyntaxWarning
Source: behave Version: 1.2.6-6 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/b/behave.html Setting up python3-behave (1.2.6-6) ... /usr/lib/python3/dist-packages/behave/formatter/ansi_escapes.py:57: SyntaxWarning: invalid escape sequence '\[' _ANSI_ESCAPE_PATTERN = re.compile(u"\x1b\[\d+[mA]", re.UNICODE) /usr/lib/python3/dist-packages/behave/matchers.py:267: SyntaxWarning: invalid escape sequence '\d' """Registers a custom type that will be available to "parse"
Bug#1085362: bibtexparser: Python SyntaxWarning
Source: bibtexparser
Version: 2.0.0b5+really1.4.1-1
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/b/bibtexparser.html
Setting up python3-bibtexparser (2.0.0b5+really1.4.1-1) ...
/usr/lib/python3/dist-packages/bibtexparser/latexenc.py:93:
SyntaxWarning: invalid escape sequence '\g'
string = re.sub('([^{]|^)([A-Z])([^}]|$)', '\g<1>{\g<2>}\g<3>', string)
Bug#1085361: berrynet: Python SyntaxWarning
Source: berrynet
Version: 3.10.2-2
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/b/berrynet.html
Setting up python3-berrynet (3.10.2-2) ...
/usr/lib/python3/dist-packages/berrynet/engine/openvino_engine.py:254:
SyntaxWarning: invalid escape sequence '\A'
logger.debug('Inference time: N\A for async mode')
Bug#1085363: bioxtasraw: Python SyntaxWarning
Source: bioxtasraw
Version: 2.2.2-2
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/b/bioxtasraw.html
Setting up python3-bioxtasraw (2.2.2-2) ...
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:467:
SyntaxWarning: invalid escape sequence '\s'
five_col_fit =
re.compile('\s*\d*[.]\d*[+eE-]*\d+\s+-?\d*[.]\d*[+eE-]*\d+\s+\d*[.]\d*[+eE-]*\d+\s+\d*[.]\d*[+eE-]*\d+\s+\d*[.]\d*[+eE-]*\d+\s*$')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:468:
SyntaxWarning: invalid escape sequence '\s'
three_col_fit =
re.compile('\s*\d*[.]\d*[+eE-]*\d+\s+-?\d*[.]\d*[+eE-]*\d+\s+\d*[.]\d*[+eE-]*\d+\s*$')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:469:
SyntaxWarning: invalid escape sequence '\s'
two_col_fit =
re.compile('\s*\d*[.]\d*[+eE-]*\d+\s+-?\d*[.]\d*[+eE-]*\d+\s*$')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:471:
SyntaxWarning: invalid escape sequence '\s'
results_fit =
re.compile('\s*Current\s+\d*[.]\d*[+eE-]*\d*\s+\d*[.]\d*[+eE-]*\d*\s+\d*[.]\d*[+eE-]*\d*\s+\d*[.]\d*[+eE-]*\d*\s+\d*[.]\d*[+eE-]*\d*\s+\d*[.]\d*[+eE-]*\d*\s*\d*[.]?\d*[+eE-]*\d*\s*$')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:473:
SyntaxWarning: invalid escape sequence '\s'
te_fit =
re.compile('\s*Total\s+[Ee]stimate\s*:\s+\d*[.]\d+\s*\(?[A-Za-z\s]+\)?\s*$')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:474:
SyntaxWarning: invalid escape sequence '\d'
te_num_fit = re.compile('\d*[.]\d+')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:475:
SyntaxWarning: invalid escape sequence '\s'
te_quality_fit = re.compile('[Aa][A-Za-z\s]+\)?\s*$')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:477:
SyntaxWarning: invalid escape sequence '\s'
p_rg_fit =
re.compile('\s*Real\s+space\s*\:?\s*Rg\:?\s*\=?\s*\d*[.]\d+[+eE-]*\d*\s*\+-\s*\d*[.]\d+[+eE-]*\d*')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:478:
SyntaxWarning: invalid escape sequence '\s'
q_rg_fit =
re.compile('\s*Reciprocal\s+space\s*\:?\s*Rg\:?\s*\=?\s*\d*[.]\d+[+eE-]*\d*\s*')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:480:
SyntaxWarning: invalid escape sequence '\s'
p_i0_fit =
re.compile('\s*Real\s+space\s*\:?[A-Za-z0-9\s\.,+-=]*\(0\)\:?\s*\=?\s*\d*[.]\d+[+eE-]*\d*\s*\+-\s*\d*[.]\d+[+eE-]*\d*')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:481:
SyntaxWarning: invalid escape sequence '\s'
q_i0_fit =
re.compile('\s*Reciprocal\s+space\s*\:?[A-Za-z0-9\s\.,+-=]*\(0\)\:?\s*\=?\s*\d*[.]\d+[+eE-]*\d*\s*')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:629:
SyntaxWarning: invalid escape sequence '\s'
iq_pattern =
re.compile('\s*\d*[.]\d*[+eE-]*\d+\s+-?\d*[.]\d*[+eE-]*\d+\s+\d*[.]\d*[+eE-]*\d+\s*')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:713:
SyntaxWarning: invalid escape sequence '\s'
iq_pattern =
re.compile('\s*\d*[.]\d*[+eE-]*\d+\s+-?\d*[.]\d*[+eE-]*\d+\s+\d*[.]\d*[+eE-]*\d+\s*')
/usr/lib/python3/dist-packages/bioxtasraw/DENSS.py:788:
SyntaxWarning: invalid escape sequence '\s'
iq_pattern =
re.compile('\s*\d*[.]\d*[+eE-]*\d+\s+-?\d*[.]\d*[+eE-]*\d+\s+\d*[.]\d*[+eE-]*\d+\s*')
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:395:
SyntaxWarning: invalid escape sequence '\l'
self.subplotLabels = [('Guinier', '$q^2$', '$\ln(I(q))$', .1),
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:396:
SyntaxWarning: invalid escape sequence '\D'
('Normalized Residual', '$q^2$', '$\Delta \ln (I(q))/\sigma (q)$', 0.1)]
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:398:
SyntaxWarning: invalid escape sequence '\l'
self.subplotLabels = [('Guinier', '$q^2$', '$\ln(I(q))$', .1),
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:399:
SyntaxWarning: invalid escape sequence '\D'
('Residual', '$q^2$', '$\Delta \ln (I(q))$', 0.1)]
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:3780:
SyntaxWarning: invalid escape sequence '\i'
subplotLabels = [('Integrated Area of q*I(q)', 'q', '$\int q \cdot
I(q) dq$', 'VC')]
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:4095:
SyntaxWarning: invalid escape sequence '\D'
'$\Delta I(q)/\sigma (q)$', 0.1))
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:4097:
SyntaxWarning: invalid escape sequence '\D'
subplotLabels.append(('Residual', '$q$', '$\Delta I(q)$', 0.1))
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:7839:
SyntaxWarning: invalid escape sequence '\D'
ax1.set_ylabel('$\Delta I(q)/\sigma (q)$')
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:7841:
SyntaxWarning: invalid escape sequence '\D'
ax1.set_ylabel('$\Delta I(q)$')
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:10339:
SyntaxWarning: invalid escape sequence '\c'
ax0.set_ylabel('$\chi^2$', fontsize='small')
/usr/lib/python3/dist-packages/bioxtasraw/RAWAnalysis.py:1
Bug#1085365: blaeu: Python SyntaxWarning
Source: blaeu
Version: 2.1.1-1
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/b/blaeu.html
Setting up blaeu (2.1.1-1) ...
/usr/lib/python3/dist-packages/Blaeu.py:120: SyntaxWarning: invalid
escape sequence '\?'
(url, key) = re.split("\?key=", url)
Bug#1085367: bookletimposer: Python SyntaxWarning
Source: bookletimposer
Version: 0.3.1-4
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/b/bookletimposer.html
Setting up bookletimposer (0.3.1-4) ...
/usr/lib/python3/dist-packages/bookletimposer/backend.py:87:
SyntaxWarning: invalid escape sequence '\.'
result = re.search("(.+)\.\w*$", value)
Bug#1085366: bmtk: Python SyntaxWarning
Source: bmtk
Version: 1.1.1+ds-2
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/b/bmtk.html
Setting up python3-bmtk (1.1.1+ds-2) ...
/usr/lib/python3/dist-packages/bmtk/simulator/bionet/modules/comsol.py:177:
SyntaxWarning: invalid escape sequence '\s'
headers = pd.read_csv(comsol_file, sep="\s{3,}", header=None,
skiprows=8, nrows=1, engine='python')
/usr/lib/python3/dist-packages/bmtk/simulator/bionet/modules/comsol.py:179:
SyntaxWarning: invalid escape sequence '\s'
data = pd.read_csv(comsol_file, sep="\s+", header=None, skiprows=9)
/usr/lib/python3/dist-packages/bmtk/simulator/filternet/lgnmodel/util_fns.py:51:
SyntaxWarning: invalid escape sequence '\D'
gr_fnames_ord = sorted(gr_fnames, key=lambda x: (int(re.sub('\D',
'', x)), x))
/usr/lib/python3/dist-packages/bmtk/utils/io/cell_vars.py:19:
SyntaxWarning: invalid escape sequence '\*'
"""A small struct to keep track of different \*/data (and buffer) tables"""
/usr/lib/python3/dist-packages/bmtk/utils/sonata/config/sonata_config.py:400:
SyntaxWarning: invalid escape sequence '\$'
variables = [m for m in re.finditer('\$\{?[\w]+\}?', json_str)]
Bug#1085368: buildstream: Python SyntaxWarning
Source: buildstream Version: 1.6.9-1 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/b/buildstream.html Setting up python3-buildstream (1.6.9-1) ... /usr/lib/python3/dist-packages/buildstream/utils.py:164: SyntaxWarning: invalid escape sequence '\*' """A generator to yield paths which match the glob pattern
Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost
Control: reassign -1 src:backuppc 4.4.0-10 Control: affects -1 src:perl Hi, On 18-10-2024 20:00, Noah Meyerhans wrote: The sysctl is namespaced, so it should suffice to set it in the testbed container. So, this should be done by src:backuppc then. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1085385: 0ad: FTBFS with Python 3.12
Package: 0ad Version: 0.0.26-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: oliv...@tilloy.net Dear Maintainer, This is a follow-up bug to #1064726. 0ad fails to build from source on testing and unstable. This is mostly caused by the antiquated version of the vendored copy of spidermonkey in the source package that is in many ways incompatible with Python 3.12. I have spent some time working out these incompatibilities, and I have submitted a merge request that addresses them, allowing the package to build: https://salsa.debian.org/games-team/0ad/-/merge_requests/5. For testing purposes I also built the package on Ubuntu 24.04 (see https://bugs.launchpad.net/ubuntu/+source/0ad/+bug/2071550) and successfully tested the game on amd64. -- System Information: Debian Release: trixie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386
Bug#1085010: lintian: make appstream optional
On 2024-10-17 21:30, Philippe Cerfon wrote: Hi. On Thu, Oct 17, 2024 at 3:53 PM Louis-Philippe Véronneau wrote: I'm not sure not issuing tags based on the presence of optional dependencies is a good idea. I think it would lead to confusion and output reproducibility problems. Would that still be a problem if lintian would just exit with a general error in case appstream was about to be invoked but not present? Debian does something like that already with program in the devscripts package, where many of them depend on packages which devscripts only recommends. So if someone actually wants to check a package with lintian that makes use of appstream metadata and if appstream is not installed, lintian could just generally fail before doing any further checks. That should make things reproducible, I guess. But people which don't use appstream in their packages could then still install and use lintan without appstream. I feel like that would generate more frustration than installing appstream by default. What kind of issues having appstream installed on a system creates? I'm generally rather skeptical about systems like flatpack/snap/appimage that substitute/circumvent Debian’s true package management system (APT/dpkg). Sure appstream is mostly about metadata, but it seems conceptually related to the former. In the end, APT/dpkg work without appstream just fine, so ideally there should be no need to install it. Appstream really is about metadata and it's super useful for automated menu creation and such. If you've ever installed a package with a GUI and see it pop in your DE's menu, that's how it's done. DEP-11 aimed to do this before Appstream took over. I don't really think we make sure it works in Debian for reasons related to alternative package management, although some other projects might. In any case, looking at the apt integration [1], it seems very unobtrusive. Barring more substantial arguments against installing appstream by default, I would be inclined to closing this bug as "wontfix". [1]: https://salsa.debian.org/pkgutopia-team/appstream/-/blob/debian/master/contrib/apt-conf/50appstream -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Bug#1085153: rrdtool: diff for NMU version 1.7.2-4.2
user debian-rele...@lists.debian.org
usertag 1085153 + bsp-2024-10-at-sbg
tags 1085153 + patch
thanks
Dear maintainer,
I've prepared an NMU for rrdtool (versioned as 1.7.2-4.2). The diff
is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru rrdtool-1.7.2/debian/changelog rrdtool-1.7.2/debian/changelog
--- rrdtool-1.7.2/debian/changelog 2024-02-29 16:29:46.0 +0100
+++ rrdtool-1.7.2/debian/changelog 2024-10-18 20:17:15.0 +0200
@@ -1,3 +1,10 @@
+rrdtool (1.7.2-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Fix build on armel and armhf (Closes: #1085153)
+
+ -- Sebastian Ramacher Fri, 18 Oct 2024 20:17:15 +0200
+
rrdtool (1.7.2-4.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru rrdtool-1.7.2/debian/patches/address-t64.patch rrdtool-1.7.2/debian/patches/address-t64.patch
--- rrdtool-1.7.2/debian/patches/address-t64.patch 1970-01-01 01:00:00.0 +0100
+++ rrdtool-1.7.2/debian/patches/address-t64.patch 2024-10-18 20:16:08.0 +0200
@@ -0,0 +1,274 @@
+From 5f954c9aa84420dca3c05caea5feb0f918d6bc47 Mon Sep 17 00:00:00 2001
+From: Andreas Hasenack
+Date: Mon, 26 Aug 2024 18:41:27 -0300
+Subject: [PATCH 1/2] Address the case when time_t is 64bits
+
+Fixes: #1264
+
+Signed-off-by: Andreas Hasenack
+---
+ bindings/tcl/tclrrd.c | 6 +++-
+ src/rrd_fetch_libdbi.c | 66 +-
+ src/rrd_graph_helper.c | 2 +-
+ src/rrd_lastupdate.c | 2 +-
+ src/rrd_tool.c | 6 ++--
+ 5 files changed, 75 insertions(+), 7 deletions(-)
+
+--- a/bindings/tcl/tclrrd.c
b/bindings/tcl/tclrrd.c
+@@ -510,7 +510,11 @@
+ sprintf(s, " %28s", ds_namv[i]);
+ Tcl_ListObjAppendElement(interp, listPtr,
+ Tcl_NewStringObj(s, -1));
++#if SIZEOF_TIME_T == 8
++sprintf(s, "\n\n%10llu:", last_update);
++#else
+ sprintf(s, "\n\n%10lu:", last_update);
++#endif
+ Tcl_ListObjAppendElement(interp, listPtr,
+ Tcl_NewStringObj(s, -1));
+ for (i = 0; i < ds_cnt; i++) {
+--- a/src/rrd_fetch_libdbi.c
b/src/rrd_fetch_libdbi.c
+@@ -53,14 +53,22 @@
+ } else if (attr & DBI_INTEGER_SIZE4) { value=dbi_result_get_int_idx(result,idx);
+ } else if (attr & DBI_INTEGER_SIZE8) { value=dbi_result_get_longlong_idx(result,idx);
+ } else { value=DNAN;
+-if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %li: column %i unsupported attribute flags %i for type INTEGER\n",time(NULL),idx,attr ); }
++#if SIZEOF_TIME_T == 8
++if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %lli: column %i unsupported attribute flags %u for type INTEGER\n",time(NULL),idx,attr ); }
++#else
++if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %li: column %i unsupported attribute flags %u for type INTEGER\n",time(NULL),idx,attr ); }
++#endif
+ }
+ break;
+ case DBI_TYPE_DECIMAL:
+ if(attr & DBI_DECIMAL_SIZE4) { value=floor(dbi_result_get_float_idx(result,idx));
+ } else if (attr & DBI_DECIMAL_SIZE8) { value=floor(dbi_result_get_double_idx(result,idx));
+ } else { value=DNAN;
+-if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %li: column %i unsupported attribute flags %i for type DECIMAL\n",time(NULL),idx,attr ); }
++#if SIZEOF_TIME_T == 8
++if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %lli: column %i unsupported attribute flags %u for type DECIMAL\n",time(NULL),idx,attr ); }
++#else
++if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %li: column %i unsupported attribute flags %u for type DECIMAL\n",time(NULL),idx,attr ); }
++#endif
+ }
+ break;
+ case DBI_TYPE_BINARY:
+@@ -82,7 +90,11 @@
+value=dbi_result_get_datetime_idx(result,idx);
+break;
+ default:
+- if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %li: column %i unsupported type: %i with attribute %i\n",time(NULL),idx,type,attr ); }
++#if SIZEOF_TIME_T == 8
++ if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %lli: column %i unsupported type: %u with attribute %u\n",time(NULL),idx,type,attr ); }
++#else
++ if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %li: column %i unsupported type: %u with attribute %u\n",time(NULL),idx,type,attr ); }
++#endif
+ value=DNAN;
+ break;
+ }
+@@ -116,14 +128,23 @@
+ } else if (attr & DBI_INTEGER_SIZE4) { value=dbi_result_get_int_idx(result,idx);
+ } else if (attr & DBI_INTEGER_SIZE8) { value=dbi_result_get_longlong_idx(result,idx);
+ } else { value=DNAN;
+-if (getenv("RRDDEBUGSQL")) { fprintf(stderr,"RRDDEBUGSQL: %li: column %i unsupported attribute flags %i for type INTEGER\n",time(NULL),idx,attr ); }
++#if SIZEOF_TIME_T == 8
++if (getenv("RRDDEBUGSQL")
Bug#1064726: follow-up bug filed
I filed bug #1085385 to track the FTBFS with Python 3.12.
Bug#910920: Fixed #1064886
Fixed during BSP 2024 in Salzburg diff -Nru tinc-1.1~pre18/debian/changelog tinc-1.1~pre18/debian/changelog --- tinc-1.1~pre18/debian/changelog 2021-06-27 20:10:22.0 +0200 +++ tinc-1.1~pre18/debian/changelog 2024-10-18 19:59:48.0 +0200 @@ -1,3 +1,10 @@ +tinc (1.1~pre18-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Re-add tinc.dirs. Closes: #910920 + + --Fri, 18 Oct 2024 19:59:48 +0200 + tinc (1.1~pre18-1) experimental; urgency=medium * New upstream release. diff -Nru tinc-1.1~pre18/debian/tinc.dirs tinc-1.1~pre18/debian/tinc.dirs --- tinc-1.1~pre18/debian/tinc.dirs 1970-01-01 01:00:00.0 +0100 +++ tinc-1.1~pre18/debian/tinc.dirs 2024-10-18 19:59:48.0 +0200 @@ -0,0 +1,7 @@ +usr/sbin +usr/share +etc +etc/init.d +usr/share/locale +usr/share/doc/tinc +etc/tinc
Bug#1085386: catch2 FTBFS on i386: 30 - ApprovalTests (Failed)
Source: catch2
Version: 3.7.1-0.2
Severity: serious
Tags: ftbfs patch
X-Debbugs-Cc: Sebastian Ramacher
https://buildd.debian.org/status/fetch.php?pkg=catch2&arch=i386&ver=3.7.1-0.2&stamp=1729275595&raw=0
...
71/71 Test #30: ApprovalTests
***Failed Error regular
expression found in output. Regex=[Results differed] 6.62 sec
/<>/tools/scripts/approvalTests.py:124: SyntaxWarning: invalid
escape sequence '\g'
line = filelocParser.sub('\g:', line)
/<>/tools/scripts/approvalTests.py:133: SyntaxWarning: invalid
escape sequence '\g'
line = tapTestNumParser.sub("\g<1> {test-number} -", line)
/<>/tools/scripts/approvalTests.py:151: SyntaxWarning: invalid
escape sequence '\g'
line = specialCaseParser.sub('file:\g<1>', line)
Running approvals against executable:
/<>/obj-i686-linux-gnu/tests/SelfTest
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '--order', 'lex', '--rng-seed',
'1', '--colour-mode', 'none']
console.std:
[92mResults matched[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions', '-x',
'4', '--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none']
console.swa4:
[92mResults matched[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'console']
console.sw:
--- console.sw.approved.txt
+++ console.sw.unapproved.txt
- 0.13015979861484195
+ 0.13015979861484198
[91mResults differed[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'junit']
junit.sw:
[92mResults matched[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'xml']
xml.sw:
--- xml.sw.approved.txt
+++ xml.sw.unapproved.txt
-0.13015979861484195
+0.13015979861484198
[91mResults differed[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'compact']
compact.sw:
--- compact.sw.approved.txt
+++ compact.sw.unapproved.txt
-InternalBenchmark.tests.cpp:: passed: normal_quantile(0.551780)
== Approx(0.13015979861484198) for: 0.13015979861484195
+InternalBenchmark.tests.cpp:: passed: normal_quantile(0.551780)
== Approx(0.13015979861484198) for: 0.13015979861484198
[91mResults differed[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'sonarqube']
sonarqube.sw:
[92mResults matched[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'tap']
tap.sw:
--- tap.sw.approved.txt
+++ tap.sw.unapproved.txt
-ok {test-number} - normal_quantile(0.551780) == Approx(0.13015979861484198)
for: 0.13015979861484195 == Approx( 0.13015979861484198 )
+ok {test-number} - normal_quantile(0.551780) == Approx(0.13015979861484198)
for: 0.13015979861484198 == Approx( 0.13015979861484198 )
[91mResults differed[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'teamcity']
teamcity.sw:
[92mResults matched[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r', 'automake']
automake.sw:
[92mResults matched[0m
['/<>/obj-i686-linux-gnu/tests/SelfTest',
'~[!nonportable]~[!benchmark]~[approvals] *', '-s', '-w', 'NoAssertions',
'--order', 'lex', '--rng-seed', '1', '--colour-mode', 'none', '-r',
'console::out=/<>/obj-i686-linux-gnu/tests/ApprovalTests/_console.sw.multi.tmp',
'-r',
'junit::out=/<>/obj-i686-linux-gnu/tests/ApprovalTests/_junit.sw.multi.tmp',
'-r',
'xml::out=/<>/obj-i686-linux-gnu/tests/ApprovalTests/_xml.sw.multi.tmp',
'-r',
'compact::out=/<>/obj-i686-linux-gnu/tests/ApprovalTests/_compact.sw.multi.tmp',
'-r',
'sonarqube::out=/<>/obj-i686-linux-gnu/tests/ApprovalTests/_sonarqube.sw.multi.tmp',
'-r',
'tap::out=/<>/obj-i686-linux-gnu/tests/ApprovalTests/_tap.sw.multi.tmp',
'-r',
'teamcity::out=/<>/obj-i686-linux-gnu/tests/ApprovalTests/_teamcity.sw.multi.tmp',
'-r',
'automake::out=/<>/obj-i686-linux-gnu/tests/ApprovalT
Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost
On Fri, Oct 18, 2024 at 07:48:43PM +0200, Paul Gevers wrote: > Hi Noah, > > On 18-10-2024 19:43, Noah Meyerhans wrote: > > In bookworm and earlier, ping uses CAP_NET_RAW file capabilities in > > order to obtain permission to transmit ICMP. The version in trixie and > > later no longer sets file based capabilities, instead relying on the > > net.ipv4.ping_group_range sysctl. This is a system-wide configuration, > > not controlled by ping. The default value, as set by the > > linux-sysctl-defaults package in trixe+ and listed as a Recommends by > > iputils-ping, grants permission for unprivileged users to run ping. > > > > Based on the above, I don't see this as a bug in ping, but rather an > > issue with the particular environment in which it's being executed. My > > recommendation is to ensure that you've got the sysctl value set > > appropriately as from > > https://salsa.debian.org/kernel-team/linux-base/-/blob/master/sysctl.d/50-default.conf?ref_type=heads#L39-45 > > I don't follow from the above how the test can be flagged as a regression > between unstable and testing then. The test in trixie passes, while if fails > with binaries from unstable. Did the change you refer to above really > already happened in trixie? No, sorry, I thought the change had already propagated. But it turns out that this issue is blocking it because of the impact to backuppc and some others. Apologies for not noticing this already. > As we currently test with lxc, do these settings really need to be set on > the host, or should the test set them in the testbed? The sysctl is namespaced, so it should suffice to set it in the testbed container. noah
Bug#1085383: libngspice0 should depends ngspice in the same version
Hello Robert, Am Fri, Oct 18, 2024 at 05:41:44PM + schrieb Robert Paciorek: > libngspice uses configuration and model files provided by ngspice package > (/usr/share/ngspice/scripts/spinit and > /usr/lib/x86_64-linux-gnu/ngspice/*.cm). I disagree, the libngsice0 package is only containing the shared libray parts and if the libary would use some external things without depending on it would be programmed in a bad way. $ dpkg -L libngspice0 /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libngspice.so.0.0.10 /usr/share /usr/share/doc /usr/share/doc/libngspice0 /usr/share/doc/libngspice0/changelog.Debian.gz /usr/share/doc/libngspice0/changelog.gz /usr/share/doc/libngspice0/copyright /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/libngspice0 /usr/lib/x86_64-linux-gnu/libngspice.so.0 While the ngspice package is containing the files you mentioned. $ dpkg -S /usr/share/ngspice/scripts/spinit ngspice: /usr/share/ngspice/scripts/spinit $ dpkg -S /usr/lib/x86_64-linux-gnu/ngspice/* ngspice: /usr/lib/x86_64-linux-gnu/ngspice/analog.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/digital.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/spice2poly.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/table.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/xtradev.cm ngspice: /usr/lib/x86_64-linux-gnu/ngspice/xtraevt.cm > * running software used libngspice0 without ngspice installed may results in > error "MIF-ERROR - unable to find definition of model and Simulation > interrupted due to error!" (with previous warning "Warning: can't find the > initialization file spinit") The ngspice binary isn't even depending on any symbol from libngspice libary so dpkg-shlibdeps isn't filling in the library as an dependency. https://packages.debian.org/unstable/ngspice If there is a symbol from there needed then this needs to get fixed upstream. But I'm sure this isn't the case here. Maybe Holger (CCed) can give a better explanation. > * running software used libngspice0 with installed ngspice in version > different > than libngspice0 version (for example libngspice0 43+ds-1~bpo12+1 and ngspice > 39.3+ds-1) may cause segmentation fault. You do not provide an example where we could prove your assumption. Without it's impossible to re-adjust a potential misbehavior. > Segmentation fault occurs only while referring to standard models provided by > *.cm files, for example while simulating digital systems using: > > A1 [in1 in2] out AND > .model AND d_and You might provide what you try to do in detail, Holger can then have a look at this. Holger, I assume you are interested in some samples so you could have a look at? Thanks! Regards Carsten
