Bug#1085988: iso-codes: 2 message catalogs installed in wrong location
control: tag -1 pending Am 24.10.24 um 12:09 schrieb Bruno Haible: Dear Maintainer, 2 message catalogs installed in wrong location The message catalogs iso_639-5.mo for Chinese are installed in /usr/share/locale/zh_Hans/LC_MESSAGES/iso_639-5.mo /usr/share/locale/zh_Hant/LC_MESSAGES/iso_639-5.mo Hi Bruno, thanks for spotting and reporting this. I've now renamed the files in the git repository, the fix will be part of the next upload of iso-codes. Regards, Tobias
Bug#1086235: lyx-common: csv2lyx.py "U" flag not supported, nor needed
Am 29.10.24 um 13:57 schrieb Pavel Sanda: On Tue, Oct 29, 2024 at 01:12:29PM +0100, Per Eric Rosén wrote: Running csv2lyx.py from within Lyx Import -> Table (CSV) gives an error that the flag "U" in open() calls is not supported. Editing the script and removing the now unsupported "U" mode flag from open() calls makes it work again. Right. Another workaround is to install lyx 2.4 from backports, python3 should be handled more gracefully there. Tobias, do you want this fix for 2.3 in bookworm? If so, cherry-picking bf4ba774c65 from lyx git tree would do the job. Pavel Hi Pavel, thanks for investigating. I don't think that this fix would be allowed in an update for the stable distribution. We have fairly strict rules on what can and cannot go into stable, and mostly those are security related fixes. After all, that is one of the reasons why there is a backports repository. :-) Regards, Tobias
Bug#1075069: hplip: ftbfs with GCC-14
On Tue, 22 Oct 2024 19:29:36 +0200 Thorsten Alteholz wrote: Hi Faidon, On 21.10.24 11:47, Faidon Liambotis wrote: > What are you intentions with regards to this patch? hplip is on top of my TODO list now and I will upload it this week. Thorsten Hi Thorsten, ping? :-) Regards, Tobias
Bug#1069903: gssproxy: directory /tmp/gssproxy/clients not available at service start
Am Sonntag, 27. Oktober 2024, 10:35:30 CET schrieben Sie: > Tobias Rupf writes: > > > Am Samstag, 26. Oktober 2024, 20:37:06 CET schrieb Simon Josefsson: > >> Tobias Rupf writes: > >> > >> > I'm using gssproxy at my client for automatically getting a kerberos > >> > ticket for > >> > a service, without user intervention. I installed and startet the > >> > service but > >> > it was not working until i figured, that I need to create this > >> > directory as it > >> > is references in the default config file 99-nfs-client.config. And it > >> > has to be > >> > recreated after each restart of my client as files in /tmp do not > >> > survive a > >> > reboot. > >> > So I have added an override to /etc/systemd/system/gssproxy.service.d: > >> > > >> > [Service] > >> > ExecStartPre=/bin/mkdir -p /tmp/gssproxy/clients > >> > PrivateTmp=true > >> > >> Hi and thanks for the report. The /tmp/gssproxy/clients directory looks > >> weird, where is that path coming from? I looked a bit in gssproxy > >> source code but didn't find what would create it. Is this coming from > >> some kerberos configuration? Could you give some step-by-step > >> instructions on how to reproduce this problem, from a freshly installed > >> debian system? > >> > > Of course this directory does not exist as systemd uses and creates > > private tmp directories. You should instead find a directory like > > /tmp/systemd-private--gssproxy.service- > > on your system which is created by systemd at startup of gssproxy- > > service. Gssproxy needs it to place krb5cc credentials there. > > The override creates the neccessary sub folders inside this directory. > > Without the override the subfolders are missing and gssproxy can not find > > a location to place the credential-files for the users (hence gssproxy does > > not create subfolders in /tmp resp. its private /tmp itself) > > What is creating the files in that directory? What software and > configuration is responsible for using /tmp/gssproxy/clients as the > intended path? I can't find anything in the gssproxy package that > refers to that path, but I may be missing it. What I suspect is that > something else is configured to use that path, and that is the component > that is responsible for also creating the directory. > > We have a good regression testing of a Apache2+gssproxy setup that is > tested in debci/autopkgtest of the gssproxy package, and no extra > directory is necessary there. See output: > > https://salsa.debian.org/debian/gssproxy/-/jobs/6490012 > https://salsa.debian.org/debian/gssproxy/-/blob/master/debian/tests/gssproxy-apache > > Having a similar script for your use-case would be nice, to make sure it > keeps working. I think your use-case is different from the apache2 > use-case since you want the service to acquire user tickets? I'm not > sure if getting tickets as the apache2 server on behalf of the user is > possible to do, and if so maybe doing so in this script will trigger > your use-case. > I'm using it gssproxy for kerberos with nfsv4 and the config file /etc/gssproxy/99-nfs-client.conf is telling to use this directory in it's cred_store line: cred_store = ccache:FILE:/tmp/gssproxy/clients/krb5cc_%U A similiar file is included in the doc as example: /usr/share/doc/gssproxy/examples/99-network-fs-clients.conf Of course you could modify the line to use the /tmp directory without sub directories, or add a comment to the file to make the user aware, that he must make sure himself to create the subdirectories... > >> > To actually be used by rpc-gssd.service a second overriide is neccessary > >> > for > >> > this service: > >> > > >> > [Service] > >> > Environment=GSS_USE_PROXY=yes > >> > > >> > Without these two additions gssproxy was not working on my client, so I > >> > think > >> > they should be included in the package - or at least be mentioned in the > >> > docs > >> > and may be as a comment in the configuration file. > >> > >> I believe the requirement to add GSS_USE_PROXY is fairly well > >> documented, see /usr/share/doc/gssproxy/docs/README.md.gz or URL below. > >> There is a systemd service file example that matches your setup. > >> > >> https://github.com/gssapi/gssproxy/tree/main/docs#configuring-the-application > >> > > Yes it is well documented, nevertheless the override is required a
Bug#1069903: gssproxy: directory /tmp/gssproxy/clients not available at service start
Am Samstag, 26. Oktober 2024, 20:37:06 CET schrieb Simon Josefsson: > Tobias Rupf writes: > > > I'm using gssproxy at my client for automatically getting a kerberos ticket > > for > > a service, without user intervention. I installed and startet the service > > but > > it was not working until i figured, that I need to create this directory > > as it > > is references in the default config file 99-nfs-client.config. And it has > > to be > > recreated after each restart of my client as files in /tmp do not survive a > > reboot. > > So I have added an override to /etc/systemd/system/gssproxy.service.d: > > > > [Service] > > ExecStartPre=/bin/mkdir -p /tmp/gssproxy/clients > > PrivateTmp=true > > Hi and thanks for the report. The /tmp/gssproxy/clients directory looks > weird, where is that path coming from? I looked a bit in gssproxy > source code but didn't find what would create it. Is this coming from > some kerberos configuration? Could you give some step-by-step > instructions on how to reproduce this problem, from a freshly installed > debian system? > Of course this directory does not exist as systemd uses and creates private tmp directories. You should instead find a directory like /tmp/systemd-private--gssproxy.service- on your system which is created by systemd at startup of gssproxy- service. Gssproxy needs it to place krb5cc credentials there. The override creates the neccessary sub folders inside this directory. Without the override the subfolders are missing and gssproxy can not find a location to place the credential-files for the users (hence gssproxy does not create subfolders in /tmp resp. its private /tmp itself) > > To actually be used by rpc-gssd.service a second overriide is neccessary for > > this service: > > > > [Service] > > Environment=GSS_USE_PROXY=yes > > > > Without these two additions gssproxy was not working on my client, so I > > think > > they should be included in the package - or at least be mentioned in the > > docs > > and may be as a comment in the configuration file. > > I believe the requirement to add GSS_USE_PROXY is fairly well > documented, see /usr/share/doc/gssproxy/docs/README.md.gz or URL below. > There is a systemd service file example that matches your setup. > > https://github.com/gssapi/gssproxy/tree/main/docs#configuring-the-application > Yes it is well documented, nevertheless the override is required and I think it should be included in the Debian gssproxy package. With override a mean a file should be installed in /etc/systemd/system/rpc-gssd.service.d containing the 2 lines: [Service] Environment=GSS_USE_PROXY=yes as described in my original report. A common user would expect gssproxy to work and to be used right after installation of the package. That's why the report is targeted to Debian project and not the gssproxy creator... Tobias signature.asc Description: This is a digitally signed message part.
Bug#1086081: src:onevpl: Please push package versions 1:2.13.0-1 to the packaging repository
Source: onevpl Severity: normal Dear Maintainer, salsa is currently at 2023.1.1-1, please push your changes to the repo. Thanks! BTW, upstream claims that some of the vulnerabilties are fixed in a version 23.3.5 (eg. SAA 00935, [1]), do you have any idea where to find that version, or has Intel stopped releasing the source? [1] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00935.html Cheers, -- tobi
Bug#1086036: libgio-2.0-dev: error processing archive /tmp/apt-dpkg-install-vCerzj/09-libgio-2.0-dev_2.82.1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/aclocal/glib-2.0.m4', which is also
Package: libgio-2.0-dev Version: 2.82.1-1 Severity: serious Justification: undeclared conflict/depends Hi, during update dpkg failed with: Unpacking libgio-2.0-dev:amd64 (2.82.1-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-vCerzj/09-libgio-2.0-dev_2.82.1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/aclocal/glib-2.0.m4', which is also in package libglib2.0-dev-bin 2.81.1-3 -- tobi -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.10.4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgio-2.0-dev depends on: ii libffi-dev3.4.6-1 iu libglib2.0-0t64 2.82.1-1 iu libmount-dev 2.40.2-9 ii libpcre2-dev 10.42-4+b1 iu libselinux1-dev 3.7-3 iu libsysprof-capture-4-dev 47.0-2 iu pkgconf 1.8.1-4 ii zlib1g-dev1:1.3.dfsg+really1.3.1-1 Versions of packages libgio-2.0-dev recommends: iu libgio-2.0-dev-bin 2.82.1-1 iu libglib2.0-bin 2.82.1-1 Versions of packages libgio-2.0-dev suggests: pn gir1.2-glib-2.0-dev pn libglib2.0-doc
Bug#1085432: src:php-horde-mime-viewer: Missing sources / invalid lintian override
Source: php-horde-mime-viewer Version: 2.2.4+debian0-2 Severity: important Dear Maintainer, while looking to update the package for LTS, I've found that src:php-horde-mime-viewer contains some minified javascript. There are lintian overrides for those, claiming that the minified javascript is source, but they are not source in the preferred form for modifications. They are not in the form for preferred modifcations, as there source is available on the Internet, namely on https://github.com/syntaxhighlighter/syntaxhighlighter/tree/3.0.83 -- Cheers, tobi
Bug#1085432: src:php-horde-mime-viewer: Missing sources / invalid lintian override
Control: found -1 2.2.2-3 Control: fixed -1 2.2.4+debian0-2 Control: close -1 Sorry for the noise, I had versions swapped when compared and this has actually been fixed in the version in stable.
Bug#1083237: r-cran-medasherence: standardize homepage
Control: tags -1 wontfix Control: close -1 On Thu, 03 Oct 2024 14:26:47 + benatt...@gezapig.nl wrote: > Source: r-cran-medadherence > Version: 1.03-6 > Severity: wishlist > > > I think its better nicer to use the standard CRAN link. > > This. > https://cran.r-project.org/src/contrib/Archive/medAdherence/ > To. > https://cran.r-project.org/package=medAdherence > > > https://tracker.debian.org/pkg/r-cran-medadherence > The the proposed homepage is NOT the upstreams homepage, but only a message that the package has been removed from CRAN. Closing as invalid.
Bug#1083249: standardize homepage bugs
Control: close -1 the old urls works just fine. not a bug, closing. Ben, As there are plenty bugs filed with the same topic: - this constitutes a Mass Bug Filing (MBF) please note that you are required to discuss a MBF on the debian-devel mailing list before filing the bugs. (See the Developes's reference for details: https://www.debian.org/doc/manuals/developers-reference/beyond-pkging.html#reporting-lots-of-bugs-at-once-mass-bug-filing - please only file bugs that actually adresses problems. In the concrete case of this bug reports I'm closing, A missing slash in a URL, without any effect on usabilty is not a bug. However, this is true for many other bugs you have filed, and I want you to re-read the mail from David sent to debian-devel: https://lists.debian.org/debian-devel/2024/09/msg00205.html This all feels like that you are filing bugs for the purpose of filing bugs only, without really understanding the processes and conventions in Debian. Please do not do that, this only creates extra work and noise, which is simply not helpful. I strongly recommend you to only file bugs where: - you are an user of the package, - you have can provide actual reason why you are filing the bug, for example what actual problem you are experiencing with the current package in Debian and how the bug are you filing will help with those. (For example, why do you think the CRAN homepage is more suitable than the upstream homepage?) - please do not file bugs for the purpose of filing bugs (sorry for repeating myself, but this is key) It seems you have at least semi-automated the filing, don't do that. This is why MBF needs to be discussed, often there are other options to filing bugs. Some bugs you have filed are tagged "moreinfo" expecting additional information provided by you. Please follow up on those. Please avoid creating noise and cause extra work cleaning up after you. As David said already: it's great that you want to help Debian, but I'm sorry to say your current bug filing strategy is not (in my opinion as an individual maintainer) very helpful. -- tobi signature.asc Description: PGP signature
Bug#1081841: r-cran-mpoly: standardize homepage
Control: close -1 The homepage fields are already pointing to appropiate *upstream* homepages. Closing as invalid. -- tobi
Bug#1083272: standardize homepage bugs
Control: close -1 the old urls works just fine. not a bug, closing.
Bug#1083278: r-bioc-txdbmaker: standardize homepage, tiny
control: close -1 the old url works just fine. not a bug, closing
Bug#1083024: teg: new upstream release fixes frequent segfault
Control: tags -1 upstream Control: fixed -1 0.13.0-1 Control: forwarded -1 https://github.com/wfx/teg/issues/53 (Tagging as fixed in unstable already, the mentioned commit is in 0.13.0) Patch: https://github.com/wfx/teg/commit/d16e8c31be5aeea52c71490c5f68e4e07155cc68 -- tobi On Mon, Sep 30, 2024 at 10:11:15AM +0200, Rémi Letot wrote: > Package: teg > Version: 0.12.0-2+b1 > Severity: important > X-Debbugs-Cc: hob...@poukram.net > > Dear Maintainer, > > I recently launched teg after a while, and couldn't finish a game since > it segfaults very often. > > I looked upstream, and indeed that bug has been identified, patched, and > a new release has been tagged: 0.13.0 two weeks ago. > > The gh issue for the segfault: > https://github.com/wfx/teg/issues/53 > > Could you please package the new release so that the bug is fixed ? > > Thanks, > Rémi > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.10.11-amd64 (SMP w/8 CPU threads; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_BE:fr > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages teg depends on: > ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2 > ii libc62.40-3 > ii libcairo21.18.2-2 > ii libedit2 3.1-20240808-1 > ii libgdk-pixbuf-2.0-0 2.42.12+dfsg-1 > ii libglib2.0-0t64 2.82.1-1 > ii libgoocanvas-2.0-9 2.0.4-1.1 > ii libgtk-3-0t643.24.43-4 > ii libpango-1.0-0 1.54.0+ds-2 > ii libpangocairo-1.0-0 1.54.0+ds-2 > ii libxml2 2.12.7+dfsg+really2.9.14-0.1 > > Versions of packages teg recommends: > ii yelp 42.2-1+b2 > > teg suggests no packages. > > -- no debconf information
Bug#1053877: [ftpmas...@ftp-master.debian.org: Accepted zabbix 1:5.0.44+dfsg-1+deb11u1 (source) into oldstable-security]
Control: fixed -1 1:5.0.44+dfsg-1+deb11u1 - Forwarded message from Debian FTP Masters - Date: Thu, 03 Oct 2024 17:30:21 + From: Debian FTP Masters To: dispa...@tracker.debian.org, debian-lts-chan...@lists.debian.org Subject: Accepted zabbix 1:5.0.44+dfsg-1+deb11u1 (source) into oldstable-security -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Sep 2024 18:44:08 +0200 Source: zabbix Architecture: source Version: 1:5.0.44+dfsg-1+deb11u1 Distribution: bullseye-security Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Tobias Frost Closes: 1014992 1014994 1026847 1053877 1055175 1078553 Changes: zabbix (1:5.0.44+dfsg-1+deb11u1) bullseye-security; urgency=medium . * Non maintainer upload by the LTS team. * Updating to latest upstream LTS release of the 5.0.x series. - Updating patches that do no longer apply. - This upload addresses, with potential effects: CVE-2022-23132 - bypass file permissions check CVE-2022-23133 - Cross-site Scripting (XSS) CVE-2022-24349 - Cross-site Scripting (XSS) CVE-2022-24917 - Cross-site Scripting (XSS) CVE-2022-24918 - Cross-site Scripting (XSS) CVE-2022-24919 - Cross-site Scripting (XSS) CVE-2022-35229 - Cross-site Scripting (XSS) (Closes: #1014992) CVE-2022-35230 - Cross-site Scripting (XSS) (Closes: #1014994) CVE-2022-43515 - Improper input validation (Closes: #1026847) Closes: #1055175: CVE-2023-29449 - Resource Exhaustion CVE-2023-29450 - Accessing local files CVE-2023-29454 - Persistent XSS CVE-2023-29455 - Reflected XSS CVE-2023-29456 - Inefficient URL schema validation CVE-2023-29457 - Insufficient validation of Action form input fields CVE-2023-29458 - Denial of Service Closes: #1053877: CVE-2023-32721 - Stored XSS CVE-2023-32722 - buffer overflow, potential for RCE CVE-2023-32724 - Remote code execution CVE-2023-32726 - Possible buffer overread CVE-2023-32727 - Code execution by authenticated, privileged user Closes: #1078553: CVE-2024-22114 - Information disclosure to unprivileged user CVE-2024-22116 - Code execution by authenticated, privileged user CVE-2024-22122 - AT(GSM) Command Injection CVE-2024-22123 - Information disclosure CVE-2024-36460 - Front-end audit log shows passwords in plaintext CVE-2024-36461 - Remote Code Excetution by users CVE-2024-22119 - Stored XSS * Enable salsa CI for LTS * Remove config.guess and config.sub in d/clean. * d/rules: usr/share/zabbix/local/app/ is no longer shipped, but needed for symlinking to /var/lib/zabbix/appü later, so create it during the build. Checksums-Sha1: 43134c30a14d2f4a72c58bc7fd7cf9eea3f2ad3e 3211 zabbix_5.0.44+dfsg-1+deb11u1.dsc c8509938e7e57c902d8ac64bfbe3e4a33481e74d 11122040 zabbix_5.0.44+dfsg.orig-templates.tar.xz db172a8421b91acd8de08a388e5c9881a013dee5 12136496 zabbix_5.0.44+dfsg.orig.tar.xz ffa014d096b2780c9e20b9848471f514b6051ffa 207312 zabbix_5.0.44+dfsg-1+deb11u1.debian.tar.xz d7816d1effcc4da27b92cf3e9318452c635f4f05 18155 zabbix_5.0.44+dfsg-1+deb11u1_amd64.buildinfo Checksums-Sha256: cd7ed0b34d2b967196e231a19fb7f21ae991b704d620534a1f605816c3b987af 3211 zabbix_5.0.44+dfsg-1+deb11u1.dsc d86702cee875dfccd4bbd8923dd0acef58678f2d8ef406f4c0c07b12eddbf858 11122040 zabbix_5.0.44+dfsg.orig-templates.tar.xz 1e54bc6e0fac46eae79fa4236fa980c721dd75e86f45869bb71d551b480d1b05 12136496 zabbix_5.0.44+dfsg.orig.tar.xz 251ccff45aa6af5c0664b416892385185ba1db5a3f3204b7b9e50da69e69dc0c 207312 zabbix_5.0.44+dfsg-1+deb11u1.debian.tar.xz 4f8f1f859aaf448c47da301b7ca1589f71c4a46f70c42d0e5e27c375e67cf7a4 18155 zabbix_5.0.44+dfsg-1+deb11u1_amd64.buildinfo Files: 01e5eddb51df5586ce1080d15adafe27 3211 net optional zabbix_5.0.44+dfsg-1+deb11u1.dsc 01f56c2836ab620f9b428287d9e274ac 11122040 net optional zabbix_5.0.44+dfsg.orig-templates.tar.xz 9cebc231530feb1e81ba6fbc485f6a85 12136496 net optional zabbix_5.0.44+dfsg.orig.tar.xz ed957bd9a45a5eed3c6406e922cfddd9 207312 net optional zabbix_5.0.44+dfsg-1+deb11u1.debian.tar.xz 24ec6a79359e73ccf2e721949736f345 18155 net optional zabbix_5.0.44+dfsg-1+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmb+0DsACgkQkWT6HRe9 XTYEKQ//frkFOjLjXY8Cc2mINgD9jvUitdJ9yXdiZRQe+yeJmcDV2jZcb1wCV4E4 pEkopQmMmojAplQLaYQwx3l/wjetSG05smibTmYfpLKiawzViMNJsmf9Y4JAXUTO 3pefLdIsYePfYHf8d2h/n6GGWepAbU2yVdOqNzKVRoG7QihT6OOy94H1X+prAYAe BngZD4Wxsy8+HVTQA/Pt72otf7XhBbVDTdwVSNjUnfYFYctunZ7eGH6BJen/vSYv NgRcBmx7gmme48Fc6SL4gbLUrDhIKmxRp+Nd7QiF/XnefS25SH1YwkdjKmfMrv7/ qZ2dxbNfqGN4zeT8cxIgE0Sh1K1Mg0GgI4SXh8IiP1Yr4oVL1JwfkmXpyucZN/Ib g0OOtX29WcpX56UpGTZdu4at/e8Pt53PJ+GrbYX1sO6HDv2HfhQCXqkWx/K8cA3B WK+RnZwEgf++rC1/L1JYzc5KYzVXgksQTZ0pWuBKIR7nVPJZDJGFwMT6IKt+drnV DS52/cUqy1HUbjWyBhyPe+kNAITLncFTewsQARp/EhZCG0LD3eZ
Bug#1014994: [ftpmas...@ftp-master.debian.org: Accepted zabbix 1:5.0.44+dfsg-1+deb11u1 (source) into oldstable-security]
Control: fixed -1 1:5.0.44+dfsg-1+deb11u1 - Forwarded message from Debian FTP Masters - Date: Thu, 03 Oct 2024 17:30:21 + From: Debian FTP Masters To: dispa...@tracker.debian.org, debian-lts-chan...@lists.debian.org Subject: Accepted zabbix 1:5.0.44+dfsg-1+deb11u1 (source) into oldstable-security -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Sep 2024 18:44:08 +0200 Source: zabbix Architecture: source Version: 1:5.0.44+dfsg-1+deb11u1 Distribution: bullseye-security Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Tobias Frost Closes: 1014992 1014994 1026847 1053877 1055175 1078553 Changes: zabbix (1:5.0.44+dfsg-1+deb11u1) bullseye-security; urgency=medium . * Non maintainer upload by the LTS team. * Updating to latest upstream LTS release of the 5.0.x series. - Updating patches that do no longer apply. - This upload addresses, with potential effects: CVE-2022-23132 - bypass file permissions check CVE-2022-23133 - Cross-site Scripting (XSS) CVE-2022-24349 - Cross-site Scripting (XSS) CVE-2022-24917 - Cross-site Scripting (XSS) CVE-2022-24918 - Cross-site Scripting (XSS) CVE-2022-24919 - Cross-site Scripting (XSS) CVE-2022-35229 - Cross-site Scripting (XSS) (Closes: #1014992) CVE-2022-35230 - Cross-site Scripting (XSS) (Closes: #1014994) CVE-2022-43515 - Improper input validation (Closes: #1026847) Closes: #1055175: CVE-2023-29449 - Resource Exhaustion CVE-2023-29450 - Accessing local files CVE-2023-29454 - Persistent XSS CVE-2023-29455 - Reflected XSS CVE-2023-29456 - Inefficient URL schema validation CVE-2023-29457 - Insufficient validation of Action form input fields CVE-2023-29458 - Denial of Service Closes: #1053877: CVE-2023-32721 - Stored XSS CVE-2023-32722 - buffer overflow, potential for RCE CVE-2023-32724 - Remote code execution CVE-2023-32726 - Possible buffer overread CVE-2023-32727 - Code execution by authenticated, privileged user Closes: #1078553: CVE-2024-22114 - Information disclosure to unprivileged user CVE-2024-22116 - Code execution by authenticated, privileged user CVE-2024-22122 - AT(GSM) Command Injection CVE-2024-22123 - Information disclosure CVE-2024-36460 - Front-end audit log shows passwords in plaintext CVE-2024-36461 - Remote Code Excetution by users CVE-2024-22119 - Stored XSS * Enable salsa CI for LTS * Remove config.guess and config.sub in d/clean. * d/rules: usr/share/zabbix/local/app/ is no longer shipped, but needed for symlinking to /var/lib/zabbix/appü later, so create it during the build. Checksums-Sha1: 43134c30a14d2f4a72c58bc7fd7cf9eea3f2ad3e 3211 zabbix_5.0.44+dfsg-1+deb11u1.dsc c8509938e7e57c902d8ac64bfbe3e4a33481e74d 11122040 zabbix_5.0.44+dfsg.orig-templates.tar.xz db172a8421b91acd8de08a388e5c9881a013dee5 12136496 zabbix_5.0.44+dfsg.orig.tar.xz ffa014d096b2780c9e20b9848471f514b6051ffa 207312 zabbix_5.0.44+dfsg-1+deb11u1.debian.tar.xz d7816d1effcc4da27b92cf3e9318452c635f4f05 18155 zabbix_5.0.44+dfsg-1+deb11u1_amd64.buildinfo Checksums-Sha256: cd7ed0b34d2b967196e231a19fb7f21ae991b704d620534a1f605816c3b987af 3211 zabbix_5.0.44+dfsg-1+deb11u1.dsc d86702cee875dfccd4bbd8923dd0acef58678f2d8ef406f4c0c07b12eddbf858 11122040 zabbix_5.0.44+dfsg.orig-templates.tar.xz 1e54bc6e0fac46eae79fa4236fa980c721dd75e86f45869bb71d551b480d1b05 12136496 zabbix_5.0.44+dfsg.orig.tar.xz 251ccff45aa6af5c0664b416892385185ba1db5a3f3204b7b9e50da69e69dc0c 207312 zabbix_5.0.44+dfsg-1+deb11u1.debian.tar.xz 4f8f1f859aaf448c47da301b7ca1589f71c4a46f70c42d0e5e27c375e67cf7a4 18155 zabbix_5.0.44+dfsg-1+deb11u1_amd64.buildinfo Files: 01e5eddb51df5586ce1080d15adafe27 3211 net optional zabbix_5.0.44+dfsg-1+deb11u1.dsc 01f56c2836ab620f9b428287d9e274ac 11122040 net optional zabbix_5.0.44+dfsg.orig-templates.tar.xz 9cebc231530feb1e81ba6fbc485f6a85 12136496 net optional zabbix_5.0.44+dfsg.orig.tar.xz ed957bd9a45a5eed3c6406e922cfddd9 207312 net optional zabbix_5.0.44+dfsg-1+deb11u1.debian.tar.xz 24ec6a79359e73ccf2e721949736f345 18155 net optional zabbix_5.0.44+dfsg-1+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmb+0DsACgkQkWT6HRe9 XTYEKQ//frkFOjLjXY8Cc2mINgD9jvUitdJ9yXdiZRQe+yeJmcDV2jZcb1wCV4E4 pEkopQmMmojAplQLaYQwx3l/wjetSG05smibTmYfpLKiawzViMNJsmf9Y4JAXUTO 3pefLdIsYePfYHf8d2h/n6GGWepAbU2yVdOqNzKVRoG7QihT6OOy94H1X+prAYAe BngZD4Wxsy8+HVTQA/Pt72otf7XhBbVDTdwVSNjUnfYFYctunZ7eGH6BJen/vSYv NgRcBmx7gmme48Fc6SL4gbLUrDhIKmxRp+Nd7QiF/XnefS25SH1YwkdjKmfMrv7/ qZ2dxbNfqGN4zeT8cxIgE0Sh1K1Mg0GgI4SXh8IiP1Yr4oVL1JwfkmXpyucZN/Ib g0OOtX29WcpX56UpGTZdu4at/e8Pt53PJ+GrbYX1sO6HDv2HfhQCXqkWx/K8cA3B WK+RnZwEgf++rC1/L1JYzc5KYzVXgksQTZ0pWuBKIR7nVPJZDJGFwMT6IKt+drnV DS52/cUqy1HUbjWyBhyPe+kNAITLncFTewsQARp/EhZCG0LD3eZ
Bug#1083127: opencascade FTBFS: error: invalid conversion from ‘unsigned char*’ to ‘const char*’ [-fpermissive]
On Wed, Oct 02, 2024 at 07:16:18PM +0200, Santiago Vila wrote:
> El 2/10/24 a las 7:44, Francesco Ballarin escribió:
> > FYI, I am reasonably sure that
> > https://github.com/Open-Cascade-SAS/OCCT/commit/7236e83dcc1e7284e66dc61e612154617ef715d6.patch
> > will fix the issue.
>
> Great. I've converted the above patch to Debian form (see attach).
> (but it's untested yet).
>
> Tobias: Can you handle this as the usual uploader?
>
> Or maybe it would help if I make a "team upload"?
I can handle it tomorrow, but be very welcome to do an team upload as well!
Cheers,
tobi
> Thanks.
> commit e16744ea146ef4a39fe2f3c0f7b4dfb3ad14be95
> Author: Santiago Vila
> Date: Wed Oct 2 15:05:00 2024 +0200
>
> Use auto instead of specific type. Closes: #1083127.
>
> diff --git a/debian/patches/0013-use-auto-instead-of-specific-type.patch
> b/debian/patches/0013-use-auto-instead-of-specific-type.patch
> new file mode 100644
> index 0..aa18f6187
> --- /dev/null
> +++ b/debian/patches/0013-use-auto-instead-of-specific-type.patch
> @@ -0,0 +1,20 @@
> +From: dpasukhi
> +Subject: [PATCH] 0033808: Coding - FreeType Use unsigned point and contour
> indexing in `FT_Outline`
> +Bug-Debian: https://bugs.debian.org/1083127
> +
> +Changes to auto instead of specific type
> +---
> + src/StdPrs/StdPrs_BRepFont.cxx | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +--- a/src/StdPrs/StdPrs_BRepFont.cxx
> b/src/StdPrs/StdPrs_BRepFont.cxx
> +@@ -457,7 +457,7 @@
> + for (short aContour = 0, aStartIndex = 0; aContour <
> anOutline->n_contours; ++aContour)
> + {
> + const FT_Vector* aPntList = &anOutline->points[aStartIndex];
> +-const char* aTags = &anOutline->tags[aStartIndex];
> ++const auto* aTags = &anOutline->tags[aStartIndex];
> + const short anEndIndex = anOutline->contours[aContour];
> + const short aPntsNb= (anEndIndex - aStartIndex) + 1;
> + aStartIndex = anEndIndex + 1;
> diff --git a/debian/patches/series b/debian/patches/series
> index 6e3d95104..054544d09 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -12,3 +12,4 @@ do-not-use-doxygen-searchengine.patch
> 0010-fix-cmake-module.patch
> 0011-cmake-workaround-tbbmemory.patch
> 0012-cmake-do-not-export-ffile-prefix.patch
> +0013-use-auto-instead-of-specific-type.patch
Bug#1081217: Keep this package in unstable
Control: tags -1 + wontfix Hi, thanks for asking about fava. There are currently two RC bugs, but I'd like to keep this package in unstable very much. I use it, so I'll try to fix the RC bugs. In the meantime, please don't remove fava from unstable. Regards, Tobias
Bug#1081711: pfm: was succeeded by PostSqlForms (psf)
Control: tags -1 moreinfo Control: severity -1 wishlist On Sat, 14 Sep 2024 09:03:27 +0200 Ben Tris wrote: > Source: pfm > Version: 2.0.8-3 > Severity: normal > > Dear Maintainer, > > psf > Last version AFAIK was v1.04 feb-2014. > https://sourceforge.net/projects/postsqlforms/ > https://postsqlforms.sourceforge.net/en/index.html > > pfm > https://web.archive.org/web/2019122328/http://pgfoundry.org/projects/pfm/ > https://web.archive.org/web/20170213185557/http://pfm.projects.pgfoundry.org/ > Can you elaborate what the purpose of this bug is? If you want psf to be packaged this should be a RFP bug against the wnpp pseudo package. If you think pfm should be retired, and replaced by psf, you should do the RFP thing and explain at least (in this bug) if pfm/psf are compatible and what to be done to replace it. If you think psf should be retired, but not replaced, you should explain that too. (FTR, psf has no reverse dependencies, so it could be easily removed from Debian. popcon is quite low, around 40, so it is probably not in wide use too) -- tobi
Bug#792580: chromium: Chromium calls home even in incognito mode with safe browsing turned off
Control: close -1 Control: archive -1 As this bug is marked wontfix, closing and archiving this bug does no harm; it only accumlates spam (Can be reopene if needed any time) -- tobi
Bug#1082507: RM: squizz -- RoM, RoQA, obsolete
Source: squizz Severity: serious Justification: QA Control: user tobi-rm-proposals@d.o Control: usertags -1 rm-proposal (as pointed out in #1081297), squizz has been planned to remove once mobyle has been removed, but appearantly that hasn't happened yet. Confirmed with dak, there are no reverse dependencies. This is to query if that is still the case, in this case please reassign this bug to ftp.debian.org. If there is no answer, I will reassing the bug for removal in exactly 3 months. If you disagree, just|please close this bug, -- tobi
Bug#1082506: RM: squizz -- RoM, RoQA, obsolete
Source: squizz Severity: severity Justification: QA User: tobi-rm-proposals@d.o Usertags: rm-proposal (as pointed out in #1081297), squizz has been planned to remove once mobyle has been removed, but appearantly that hasn't happened yet. Confirmed with dak, there are no reverse dependencies. This is to query if that is still the case, in this case please reassign this bug to ftp.debian.org. If there is no answer, I will reassing the bug for removal in exactly 3 months. If you disagree, just|please close this bug, -- tobi
Bug#1082243: qqwing: maybe interesting new edits original repo
Control: tags -1 moreinfo Control: severity -1 wishlist On Thu, 19 Sep 2024 13:36:22 + benatt...@gezapig.nl wrote: > Source: qqwing > Version: 1.3.4-1.1 > Severity: normal > > > The version in Debian is from apr-2015. > There are edits until mar-2021 on original repo, maybe its interesting to look. > https://github.com/stephenostermiller/qqwing > > > https://tracker.debian.org/pkg/qqwing > What are the changes that you see as interesting? What is the problem you are thinking those are fixing? If you think they are important, probably approaching upstream with that information is more sensible than a Debian bug report, so that the whole FOSS ecosystem will benefit, do you agree? -- tobi
Bug#1082283: pypureomapi: maybe interesting new edits original repo
Control: tags -1 moreinfo Control: severity -1 wishlist On Thu, 19 Sep 2024 16:35:48 + benatt...@gezapig.nl wrote: > Source: pypureomapi > Version: 0.8-1 > Severity: normal > > > The version in Debian is from mar-2019. > There are edits until may-2022 on original repo, maybe its interesting to look. > https://github.com/CygnusNetworks/pypureomapi > > > https://tracker.debian.org/pkg/pypureomapi > What are the changes that you see as interesting? What is the problem you are thinking those are fixing? If you think they are important, probably approaching upstream with that information is more sensible than a Debian bug report, so that the whole FOSS ecosystem will benefit, do you agree? -- tobi
Bug#1082303: sxiv: original repo archived
Control: severity -1 wishlist Control: forwarded -1 https://github.com/xyb3rt/sxiv/issues/463 Control: retitle -1 sxiv: upstream has ceased development The linked issue has some upstream discussions on successors, but seem not to have gained momentum. Github lists several forks, but some seems to change focus. There seems not to be "the" fork.
Bug#1082294: wordplay: maybe interesting new edits original repo
Control: tags -1 moreinfo Control: severity -1 wishlist Conrtol: close -1 On Thu, 19 Sep 2024 17:47:46 + benatt...@gezapig.nl wrote: > Source: wordplay > Version: 8.0-1 > Severity: normal > > > The version in Debian is from may-2019. > There are edits until feb-2024 on original repo and fork, > maybe its interesting to look. > https://github.com/mendelmunkis/wordplay > https://github.com/ScoreUnder/wordplay > > > https://tracker.debian.org/pkg/wordplay > No, this seems to be fork for the purpose of a fix, not for the purpose of a sustained fork. Please file an upstream issue and let upstream know that there are this fixes, and/or ask the forker to create a merge request to get their changes upstream. This is not actionable for Debian; it seems that the crash this seems to fix is not easily observed, at least there is no issue report on this.
Bug#1082299: python-setuptools-git: maybe interesting (old) pull request original repo
Control: tags -1 moreinfo Control: severity -1 wishlist On Thu, 19 Sep 2024 18:20:44 + benatt...@gezapig.nl wrote: > Source: python-setuptools-git > Version: 1.2-3 > Severity: minor > > > The version in Debian is from feb-2017. > There is a pull request from sep-2017 on original repo, > maybe its interesting to look. > https://github.com/msabramo/setuptools-git > > > https://tracker.debian.org/pkg/python-setuptools-git > What are the changes that you see as interesting? What is the problem you are thinking those are fixing? If you think they are important, probably approaching upstream with that information is more sensible than a Debian bug report, so that the whole FOSS ecosystem will benefit, do you agree? -- tobi
Bug#1081738: vdk2-tutorial: no homepage field
Control: severity -1 minor > note: vdk2 was removed from Debian aug-2023. I've suggested removal of this package; filed as #1082502.
Bug#1082502: RM: vdk2-tutorial -- RoQM, obsolete
Source: vdk2-tutorial Severity: severity Justification: QA User: tobi-rm-proposals@d.o Usertags: rm-proposal Dear Maintainer, as pointed out in #1081738, vdk2 has been removed from Debian a year ago, so it seems that this package should be retired as well. (I've checked with dak, there are no reverse dependencies) If you also think that it should be removed, just reassign it to the ftp.debian.org pseudo package. If there is no answer, I will reassing the bug for removal in exactly 3 months. If you disagree, just|please close this bug, Thanks! -- tobi
Bug#1081671: unagi: maybe interesting edits original repo
Control: tags -1 moreinfo Control: severity -1 wishlist On Fri, 13 Sep 2024 19:07:58 +0200 Ben Tris wrote: > Source: unagi > Version: 0.3.4-1 > Severity: normal > > Dear Maintainer, > > Maybe interesting lots of edits after the last version date until mar- 2014. > https://projects.mini-dweeb.org/projects/unagi/repository What are the changes that you see as interesting? Have you tried contacting upstream to see if they could cut a new version? -- tobi
Bug#1081513: dhcpstarv: maybe interesting merge request original repo
Control: tags -1 moreinfo On Thu, 12 Sep 2024 12:35:52 +0200 Ben Tris wrote: > Source: dhcpstarv > Version: 0.2.2-2 > Severity: normal > > Dear Maintainer, > > Maybe interesting SourceForge repo merge request aug-2018. > https://sourceforge.net/p/dhcpstarv/git/merge-requests/ > Please describe the problem you have, to understand what this would solve (for you). (Possibly better would be to approach upstream and ask them to merge it, and possibly cut a new release.) -- tobi
Bug#1082252: cc65: ask for new version tag or release
Control: forwarded -1 https://github.com/cc65/cc65/issues/2281 Control: close -1 On Thu, 19 Sep 2024 13:59:30 + benatt...@gezapig.nl wrote: > Source: cc65 > Version: 2.19-1 > Severity: wishlist > > > The version in Debian is from may-2020. > Since then there are many edits to this day. > Maybe there can be asked to make a tag or release. > > > https://tracker.debian.org/pkg/cc65 > Upstream has release pleans, See https://github.com/cc65/cc65/issues/2281 and https://github.com/cc65/wiki/wiki/Before-the-next-release Closing as non-actionable.
Bug#1053254: ries: new version available
retitle 1053254 ries: new upstream vesion 2024.05.20 severity 1053254 wishlist Ben, your modifications to the bug metadata were incorrect, please refrain from changing them again. Thanks. -- tobi
Bug#1053174: Block Ben Tris
Hi Don, Ben is again actice on the BTS and even after called out by David on debian-devel and myself in e.g in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999649#22 They started to undo the correction on the BTS I made earlier, and wrote me in private mail to "Do not fool around with the bugs I make and control", while clearly not understanding the processes in Debian with often comments that feel out of place commentary (e.g 994649#29 or 999649#17) This is repeated behaviour, I had the same experience in September 2023 where I tried to tell Ben about e.g the correct usage of severities for new upstream release bugs and related topic, after which they mass- closed their filed bugs (I had the impression this was kind of rage-quit action...) Now, they are doing the same thing (filing barely actionable bugs) again that has been topic of this bug, for example lot of "Missing homepage" I think it would be appropiate for some cool-down period. Thanks! -- tobi On Fri, 29 Sep 2023 21:28:22 -0700 Don Armstrong wrote: > On Thu, 28 Sep 2023, Christoph Berg wrote: > > we keep seeing non-actionable bug reports from Ben Tris that look like > > this: > > Hi Ben, please don't file bugs like this which aren't actionable. If you > find something minor wrong with a package like this, please provide a > patch so that maintainers can see what you think is wrong and how they > should fix it. > > It looks like you've closed the non-actionable bugs that you had filed, > so I won't immediately be putting in a block for you, but if it happens > again, I will. > > Thanks! > > -- > Don Armstrong https://www.donarmstrong.com > > Thanks be to God, that he gave me Stubbornness, when I know I am right. > -- John Adams (Letter to Edmund Jennings, 27 September 1782) > > signature.asc Description: This is a digitally signed message part
Bug#999649:
Control: reopen -1 On Fri, 20 Sep 2024 09:41:37 + benatt...@gezapig.nl wrote: > This is already fixed in repo I have enough bugs to care for. This is NOT how the BTS is to be interacted with.
Bug#999649:
Control: reopen -1 On Sun, 01 Sep 2024 08:41:11 + benatt...@gezapig.nl wrote: > fixed in repo takes to long Ben, pretty please, with sugar on top, refrain from changing bugs with that attitude. Especially: Don't change severity and bug titles if it is not giving more accurate information, for example #958287, #1053097 and others. Especially with the snarky comments given on the bugs, this makes a impression this is not compatible with the CoC: We expect from you that your interaction with the project is constructive and that you are honoring the feedback you are receiving -- I point you to the mail exchange we had a year ago.
Bug#1071090: iso-codes: installs broken symbolic links
control: retitle -1 localepurge: should remove symlinks as well control: tag -1 -unreproducible Am 16.09.24 um 06:50 schrieb Martin-Éric Racine: I checked and noticed the same issue on all of my hosts, not just that Sid chroot. Anyhow, I think that I found the cause: I use 'localepurge' to have APT automatically remove unused localizations and save disk space. As far as I can tell, the bug is that it removes any unused FILE shipped by a package, but not symbolic links. We are therefore left with 2 symbolic links pointing to nothing, and 'adequate' complains about them. 'localepurge' should probably manage those too. Hi, thanks for digging deeper and finding the cause. Now it makes sense. :-) Regards, Tobias
Bug#1071090: iso-codes: installs broken symbolic links
control: reopen -1 control: tag -1 unreproducible Am 15.09.24 um 10:11 schrieb Martin-Éric Racine: This IS in a Sid chroot. I have tried purging and re-installing. Same result. Martin-Éric Thanks for investigating again. I'm reopening the bug, but it's not reproducible by me, so tagging accordingly. Maybe I'll get another report about a similar problem with some hints where the problem might be -- right now, I don't have a clue what's going on in your sid chroot versus mine. Regards, Tobias
Bug#1071090: iso-codes: installs broken symbolic links
Am 14.09.24 um 07:48 schrieb Martin-Éric Racine: $ LC_ALL=C ls -l /usr/share/locale/fil/LC_MESSAGES/ total 0 lrwxrwxrwx 1 root root 13 2024-09-13 22:45 iso_3166.mo -> iso_3166-1.mo lrwxrwxrwx 1 root root 13 2024-09-13 22:45 iso_3166_2.mo -> iso_3166-2.mo You might wanna check whether other files failed to install. Martin-Éric This is the output on my system: $ adequate iso-codes $ $ LC_ALL=C ls -l /usr/share/locale/fil/LC_MESSAGES/ total 44K -rw-r--r-- 1 root root 11K Jan 14 2024 iso_15924.mo -rw-r--r-- 1 root root 24K Jan 14 2024 iso_3166-1.mo -rw-r--r-- 1 root root 3.0K Jan 14 2024 iso_3166-2.mo lrwxrwxrwx 1 root root 13 Jan 14 2024 iso_3166.mo -> iso_3166-1.mo lrwxrwxrwx 1 root root 13 Jan 14 2024 iso_3166_2.mo -> iso_3166-2.mo $ So I cannot reproduce this. Also, I'm not convinced that there is an actual problem in the iso-codes package, because I can see both files in the created .deb package. They are also listed in the package's contents, see e. g. https://packages.debian.org/sid/all/iso-codes/filelist. I would guess that there is some strange error in the system you are using for this test. Did you try to create a clean sid chroot and install iso-codes from scratch? Are those files still missing in that environment? Regards, Tobias
Bug#1072742: On Romanian translations in the iso-codes package
control: tag -1 pending Am 05.08.24 um 19:57 schrieb Remus-Gabriel Chelu: Last night, I tried to upload the corrected "iso-3166-2-ro.po" file into "iso-codes_Weblate", but ... I couldn't do it! Hi Remus-Gabriel, thanks again for this update, I've now committed the file to the repository, which in turn should appear on Weblate soon. Regards, Tobias
Bug#1079750: setuptools test command is removed
Hi, we encountered this issue in Ubuntu too, the attached patch should to fix it. Cheers, Tobias >From 9b7ce9d05185ec427fbb12ff0bf9a8f49c8506ed Mon Sep 17 00:00:00 2001 From: Tobias Heider Date: Tue, 10 Sep 2024 21:26:41 +0200 Subject: [PATCH] Run tests without setuptools setuptools dropped support for tests_require and fails so run tests directly instead. --- debian/tests/testsuite | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/tests/testsuite b/debian/tests/testsuite index 23403ad..aa9f280 100755 --- a/debian/tests/testsuite +++ b/debian/tests/testsuite @@ -1,2 +1,2 @@ #!/bin/bash -python3 setup.py test +python3 -m unittest prometheus_xmpp.tests.test_suite -- 2.45.2
Bug#1041004: firmware-b43-installer: Drivers in this package are not available in debian-12.0.0-amd64-netinst.iso at time of writing.
Control: tags -1 wontfix Control: close -1 Hi David, Not sure if I got your report correcty; firmware-b43-installer merley downloads the firmware files, as the firmware files cannot be distributed IIUIC due to no redistributions rights granted by Broadcom. If my understanding is correct that you'd expect the firmware files to be present without downloading them, that would be undortunatly if my IIUIC is right, not fixable. (If I misunderstood, please feel free to reopen this bug and expand a bit, thanks) -- tobi On Thu, 13 Jul 2023 16:52:06 -0400 David Peacock wrote: > Package: firmware-b43-installer > Severity: normal > X-Debbugs-Cc: david.j.peac...@gmail.com > > Dear Maintainer, > > Upon attempting to install Debian 12 using [0] on my early 2013 Retina > Macbook Pro, I discovered that the drivers needed to operate the > Broadcom wireless card included were not available. It was my > understanding that these drivers should be included in the newly > established non-free-firmware repository. > > I'm raising this bug report purely to bring this to attention in hope > that it's possible to add these drivers to the Bookworm netinst image to > avoid having to deal with this when installing on various models of > Macbook Pro. > > Thank you > David > > [0] https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.0.0-amd64-netinst.iso > > -- System Information: > Debian Release: 12.0 > APT prefers stable-security > APT policy: (500, 'stable-security'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-10-amd64 (SMP w/24 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages firmware-b43-installer depends on: > pn b43-fwcutter > ii bzip2 1.0.8-5+b1 > ii ca-certificates 20230311 > ii pciutils 1:3.9.0-4 > ii wget 1.21.3-1+b2 > > firmware-b43-installer recommends no packages. > > firmware-b43-installer suggests no packages. > >
Bug#1079404: gnucash: warnings for incompatible bytecode version
Package: gnucash Version: 1:5.8-1 Severity: normal Dear Maintainer, since upgrading to trixie, when I launch gnucash from the command line, I get ~200 warnings like this: ;;; WARNING: loading compiled file /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/gnucash/qif-import/qif-file.go failed: ;;; In procedure load-thunk-from-memory: incompatible bytecode version -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (420, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnucash depends on: ii gnucash-common 1:5.8-1 ii guile-3.0 3.0.9-1+b2 ii guile-3.0-libs 3.0.9-1+b2 ii libaqbanking44 6.5.12beta-1 ii libboost-filesystem1.83.0 1.83.0-3.1 ii libboost-locale1.83.0 1.83.0-3.1 ii libboost-program-options1.83.0 1.83.0-3.1 ii libc6 2.39-6 ii libcairo2 1.18.0-3+b1 ii libcrypt-ssleay-perl0.73.06-2+b3 ii libdate-manip-perl 6.95-1 ii libdbi1t64 0.9.0-6.1 ii libfinance-quote-perl 1.62-1 ii libgcc-s1 14.2.0-1 ii libgdk-pixbuf-2.0-0 2.42.12+dfsg-1 ii libglib2.0-0t64 2.81.1-3 ii libgtk-3-0t64 3.24.43-1 ii libgwengui-gtk3-79t64 5.11.2beta-2 ii libgwenhywfar79t64 5.11.2beta-2 ii libhtml-tableextract-perl 2.15-2 ii libhtml-tree-perl 5.07-3 ii libicu7272.1-5 ii libofx7t64 1:0.10.9-1.1+b1 ii libpango-1.0-0 1.54.0+ds-1 ii libpangocairo-1.0-0 1.54.0+ds-1 ii libpython3.12t643.12.4-3 ii libsecret-1-0 0.21.4-1+b1 ii libstdc++6 14.2.0-1 ii libwebkit2gtk-4.1-0 2.44.2-1+b2 ii libwww-perl 6.77-1 ii libxml2 2.9.14+dfsg-1.3+b3 ii perl5.38.2-5 ii zlib1g 1:1.3.dfsg+really1.3.1-1 Versions of packages gnucash recommends: ii gnucash-docs 5.6-1 ii python3-gnucash 1:5.8-1 pn yelp Versions of packages gnucash suggests: pn libdbd-mysql pn libdbd-pgsql pn libdbd-sqlite3 -- no debconf information
Bug#1075105: jxrlib: diff for NMU version 1.2~git20170615.f752187-5.3
Control: tags 1075105 + pending Dear maintainer, I've prepared an NMU for jxrlib (versioned as 1.2~git20170615.f752187-5.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru jxrlib-1.2~git20170615.f752187/debian/changelog jxrlib-1.2~git20170615.f752187/debian/changelog --- jxrlib-1.2~git20170615.f752187/debian/changelog 2024-03-17 05:12:37.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/changelog 2024-08-17 09:05:27.0 +0200 @@ -1,3 +1,11 @@ +jxrlib (1.2~git20170615.f752187-5.3) unstable; urgency=medium + + * Non-maintainer upload. + * Apply patch to fix building with GCC-14s, thanks to YOKOTA Hiroshi for +preparing it. (Closes: #1075105) + + -- Tobias Frost Sat, 17 Aug 2024 09:05:27 +0200 + jxrlib (1.2~git20170615.f752187-5.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,33 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 15:03:31 +0900 +Subject: jxrlib: ftbfs with GCC-14 +MIME-Version: 1.0 +Content-Type: text/plain; charset="utf-8" +Content-Transfer-Encoding: 8bit + +Bug-Debian: https://bugs.debian.org/1075105 + +_byteswap_ulong() is defined in image/sys/strcodec.c + + +/usr/bin/cc -DDISABLE_PERF_MEASUREMENT -D__ANSI__ -Djpegxr_EXPORTS -I"/<>/common/include" -I"/<>/image/sys" -I"/<>/jxrgluelib" -I"/<>/jxrtestlib" -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -MF CMakeFiles/jpegxr.dir/image/encode/strenc.c.o.d -o CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -c "/<>/image/encode/strenc.c" +/<>/image/decode/segdec.c: In function ‘_load4’: +/<>/image/decode/segdec.c:68:12: error: implicit declaration of function ‘_byteswap_ulong’ [-Wimplicit-function-declaration] + 68 | return _byteswap_ulong(v); + |^~~ +--- + image/decode/segdec.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/image/decode/segdec.c b/image/decode/segdec.c +index 3c890af..5d55f06 100644 +--- a/image/decode/segdec.c b/image/decode/segdec.c +@@ -63,6 +63,7 @@ static U32 _FORCEINLINE _load4(void* pv) + v |= ((U32)((U16 *) pv)[1]) << 16; + return _byteswap_ulong(v); + #else // _M_IA64 ++U32 _byteswap_ulong(U32 bits); // from image/sys/strcodec.c + U32 v; + memcpy(&v, pv, sizeof(U32)); + return _byteswap_ulong(v); diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,88 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 16:00:12 +0900 +Subject: FTBFS fix for pointer type mismatch + +Bug-Debian: https://bugs.debian.org/1075105 +--- + jxrencoderdecoder/JxrDecApp.c | 2 +- + jxrtestlib/JXRTest.c | 10 +- + jxrtestlib/JXRTestTif.c | 4 ++-- + 3 files changed, 8 insertions(+), 8 deletions(-) + +diff --git a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +index 5779eb8..f07b3c4 100644 +--- a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +@@ -428,7 +428,7 @@ ERR WmpDecAppCreateEncoderFromExt( + Call(GetTestEncodeIID(szExt, &pIID)); + + // Create encoder +-Call(PKTestFactory_CreateCodec(pIID, ppIE)); ++Call(PKTestFactory_CreateCodec(pIID, (void **)ppIE)); + + Cleanup: + return err; +diff --git a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +index b2a9b64..790b0de 100644 +--- a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +@@ -198,7 +198,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + ERR err = WMP_errSuccess; + + char *pExt = NULL; +-PKIID* pIID = NULL; ++const PKIID* pIID = NULL; + + struct WMPStream* pStream = NULL; + PKImageDecode* pDecoder = NULL; +@@ -214,7 +214,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + Call(CreateWS_File(&pStream, szFilename, "rb")); + + // Create decoder +-C
Bug#1075105: jxrlib: diff for NMU version 1.2~git20170615.f752187-5.3
Control: tags 1075105 + pending Dear maintainer, I've prepared an NMU for jxrlib (versioned as 1.2~git20170615.f752187-5.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru jxrlib-1.2~git20170615.f752187/debian/changelog jxrlib-1.2~git20170615.f752187/debian/changelog --- jxrlib-1.2~git20170615.f752187/debian/changelog 2024-03-17 05:12:37.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/changelog 2024-08-17 09:05:27.0 +0200 @@ -1,3 +1,11 @@ +jxrlib (1.2~git20170615.f752187-5.3) unstable; urgency=medium + + * Non-maintainer upload. + * Apply patch to fix building with GCC-14s, thanks to YOKOTA Hiroshi for +preparing it. (Closes: #1075105) + + -- Tobias Frost Sat, 17 Aug 2024 09:05:27 +0200 + jxrlib (1.2~git20170615.f752187-5.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0013-jxrlib-ftbfs-with-GCC-14.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,33 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 15:03:31 +0900 +Subject: jxrlib: ftbfs with GCC-14 +MIME-Version: 1.0 +Content-Type: text/plain; charset="utf-8" +Content-Transfer-Encoding: 8bit + +Bug-Debian: https://bugs.debian.org/1075105 + +_byteswap_ulong() is defined in image/sys/strcodec.c + + +/usr/bin/cc -DDISABLE_PERF_MEASUREMENT -D__ANSI__ -Djpegxr_EXPORTS -I"/<>/common/include" -I"/<>/image/sys" -I"/<>/jxrgluelib" -I"/<>/jxrtestlib" -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -MF CMakeFiles/jpegxr.dir/image/encode/strenc.c.o.d -o CMakeFiles/jpegxr.dir/image/encode/strenc.c.o -c "/<>/image/encode/strenc.c" +/<>/image/decode/segdec.c: In function ‘_load4’: +/<>/image/decode/segdec.c:68:12: error: implicit declaration of function ‘_byteswap_ulong’ [-Wimplicit-function-declaration] + 68 | return _byteswap_ulong(v); + |^~~ +--- + image/decode/segdec.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/image/decode/segdec.c b/image/decode/segdec.c +index 3c890af..5d55f06 100644 +--- a/image/decode/segdec.c b/image/decode/segdec.c +@@ -63,6 +63,7 @@ static U32 _FORCEINLINE _load4(void* pv) + v |= ((U32)((U16 *) pv)[1]) << 16; + return _byteswap_ulong(v); + #else // _M_IA64 ++U32 _byteswap_ulong(U32 bits); // from image/sys/strcodec.c + U32 v; + memcpy(&v, pv, sizeof(U32)); + return _byteswap_ulong(v); diff -Nru jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch --- jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 1970-01-01 01:00:00.0 +0100 +++ jxrlib-1.2~git20170615.f752187/debian/patches/0014-FTBFS-fix-for-pointer-type-mismatch.patch 2024-08-17 09:00:32.0 +0200 @@ -0,0 +1,88 @@ +From: YOKOTA Hiroshi +Date: Thu, 25 Jul 2024 16:00:12 +0900 +Subject: FTBFS fix for pointer type mismatch + +Bug-Debian: https://bugs.debian.org/1075105 +--- + jxrencoderdecoder/JxrDecApp.c | 2 +- + jxrtestlib/JXRTest.c | 10 +- + jxrtestlib/JXRTestTif.c | 4 ++-- + 3 files changed, 8 insertions(+), 8 deletions(-) + +diff --git a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +index 5779eb8..f07b3c4 100644 +--- a/jxrencoderdecoder/JxrDecApp.c b/jxrencoderdecoder/JxrDecApp.c +@@ -428,7 +428,7 @@ ERR WmpDecAppCreateEncoderFromExt( + Call(GetTestEncodeIID(szExt, &pIID)); + + // Create encoder +-Call(PKTestFactory_CreateCodec(pIID, ppIE)); ++Call(PKTestFactory_CreateCodec(pIID, (void **)ppIE)); + + Cleanup: + return err; +diff --git a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +index b2a9b64..790b0de 100644 +--- a/jxrtestlib/JXRTest.c b/jxrtestlib/JXRTest.c +@@ -198,7 +198,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + ERR err = WMP_errSuccess; + + char *pExt = NULL; +-PKIID* pIID = NULL; ++const PKIID* pIID = NULL; + + struct WMPStream* pStream = NULL; + PKImageDecode* pDecoder = NULL; +@@ -214,7 +214,7 @@ ERR PKTestFactory_CreateDecoderFromFile(const char* szFilename, PKImageDecode** + Call(CreateWS_File(&pStream, szFilename, "rb")); + + // Create decoder +-C
Bug#1078747: python3-cryptography: cryptography.exceptions fails to import
Package: python3-cryptography Version: 42.0.5-2+b1 Followup-For: Bug #1078747 Hi, This was caused by the recent split of legacy providers from the main OpenSSL package. Installing openssl-provider-legacy "fixes" the error. These are the aloorithms considered "legacy": Hashing: MD2, MD4, MDC2, WHIRLPOOL, RIPEMD160 Ciphers: Blowfish, CAST, DES, IDEA, RC2, RC4, RC5, SEED KDF: PBKDF1, PVKKDF (From https://manpages.debian.org/bookworm/openssl/OSSL_PROVIDER-legacy.7ssl.en.html) Some of the software I tried works with setting CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1, because they obviously don't use any of the legacy algorithms... I wonder if this really needs to be a hard fail in Debian? Or do we want to patch every cryptography-using tool with a line like os.environ['CRYPTOGRAPHY_OPENSSL_NO_LEGACY'] = "1" to "promise" not to require the legacy ciphers? And every package which needs these ciphers must add a dependency on openssl-provider-legacy? I currently don't have a good solution. Making python3-cryptography depend on openssl-provider-legacy feels kinda wrong to me... Regargs, Tobias -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.4-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_GB:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-cryptography depends on: ii libc62.39-7 ii libgcc-s114.2.0-2 ii libssl3t64 3.3.1-6 ii python3 3.12.5-1 ii python3-cffi-backend [python3-cffi-backend-api-min] 1.17.0-1 pn python3-cffi-backend-api-max python3-cryptography recommends no packages. Versions of packages python3-cryptography suggests: pn python-cryptography-doc pn python3-cryptography-vectors -- no debconf information
Bug#1078342: pandoc: Memory leak when converting markdown files
Package: pandoc Version: 3.1.3+ds-3 Severity: normal Dear Maintainer, I have a large markdown file (11M) that I cannot convert to epub because pandoc runs out of memory. As far as i can see, this has already been fixed upstream: https://github.com/jgm/pandoc/blob/main/changelog.md#pandoc-315-2023-07-07 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (420, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pandoc depends on: ii libc62.39-6 ii libffi8 3.4.6-1 ii libgmp10 2:6.3.0+dfsg-2+b1 ii liblua5.4-0 5.4.6-3+b1 ii libyaml-0-2 0.2.5-1+b1 ii pandoc-data 3.1.3-2 ii zlib1g 1:1.3.dfsg+really1.3.1-1 pandoc recommends no packages. Versions of packages pandoc suggests: pn citation-style-language-styles pn context pn ghc pn groff pn libjs-katex pn libjs-mathjax pn librsvg2-bin ii nodejs 20.15.0+dfsg-1 pn pandoc-citeproc ii perl5.38.2-5 ii php8.2 [php]8.2.21-1 pn python pn r-base-core ii ruby1:3.1+nmu1 pn texlive-latex-extra ii texlive-latex-recommended 2024.20240706-1 pn texlive-luatex pn texlive-xetex pn wkhtmltopdf -- no debconf information
Bug#1072742: On Romanian translations in the iso-codes package
Hi, thanks for the updated file. I'm currently on vacation, but I'll look into the weblate issue next week when I'm back. If all else fails, I can always apply your fixes manually to iso-codes. Regards, Tobias 05.08.2024 19:58:07 Remus-Gabriel Chelu : > Hello, > > > În 24.07.2024 22:18, Remus-Gabriel Chelu a scris: > >> >> >> Hi, >> >> I just published on the mailing list of the Romanian Debian team >> <https://lists.debian.org/debian-l10n-romanian/2024/07/>, the corrected >> "iso-3166-2-ro.po" file, with a request for review [RFR]. >> >> I hope that at the beginning of next month (probably Sunday, the 4th day >> of the month), I will upload it to Weblate with the changes proposed by the >> team. > > Last night, I tried to upload the corrected "iso-3166-2-ro.po" file into > "iso-codes_Weblate", but ... I couldn't do it! > > On the project page, in fact on the page of each component of the project, > there is a warning message > > "The translation is temporarily closed for contributions due to maintenance, > please come back later. > The translation was automatically locked due to following alerts: Could not > push the repository."; > clicking on the «Could not push the repository.» link will display the > message: > > "Could not push the repository. > > Weblate could not push changes to the upstream repository. > > kex_exchange_identification: Connection closed by remote host > Connection closed by 2607:f8f0:614:1::1274:44 port 22 > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > (128) > > Weblate will retry the operation once it is needed again, > so the alert might disappear for the temporary issues. > Appeared 3 months ago, last seen 3 months ago" > > > That's why I'm attaching the corrected file here, so as not to open another > bug report on the "iso-codes" project. > > -- > Greetings, > Remus-Gabriel
Bug#1072381: Provide gtk4-client package
On Sun, 4 Aug 2024 07:57:32 +0300 Marko Lindqvist wrote: > You may want to backport https://redmine.freeciv.org/issues/750 > It's a fix to gtk4-client crash occurring on some environments > (avoided by luck in others). Last I tested, Trixie was affected. > Thanks for the info! I see that there are many patches listed on the issue... Do I need all of them?
Bug#1072381: Provide gtk4-client package
Package prepared and uploaded -- as this introduces a new binary package this needs to pass the NEW queue, so it might take some time until it will be available. -- tobi
Bug#1077782: contributors.debian.org: users listed as "voters" but have not voted.
Package: contributors.debian.org Severity: normal While doing MIA work I saw people recorded as voters "until April 2024", but the voters list [1] does not list them as having actual having voted in the (only) vote in 2024, the DPL vote. For example: bossekr camrdale cowboy ccheney [1] https://www.debian.org/vote/2024/vote_001_voters.txt -- tobi
Bug#1077781: netsend: d/control Homepage is invalid
Source: netsend Severity: minor berlinos is dead since years. -- System Information: Debian Release: trixie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.9.11-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1077589: boost1.83: diff for NMU version 1.83.0-3.1
On Wed, Jul 31, 2024 at 10:20:45PM +0200, Anton Gladky wrote: > Hi Tobias, > > thanks for the update! Please go ahead with the immediate upload. > Please also update the git. Thanks. Regards Thanks for the heads up! Rescheduled to 0-day and salsa MR merged. -- tobi > > Anton > > > Am Di., 30. Juli 2024 um 10:48 Uhr schrieb Tobias Frost : > > > Package: boost1.83 > > Version: 1.83.0-3 > > Severity: normal > > Tags: patch pending > > > > > > Dear maintainer, > > > > I've prepared an NMU for boost1.83 (versioned as 1.83.0-3.1) and > > uploaded it to DELAYED/5. Please feel free to tell me if I > > should delay it longer. > > > > Regards. > > > >
Bug#1077589: boost1.83: diff for NMU version 1.83.0-3.1
Package: boost1.83
Version: 1.83.0-3
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for boost1.83 (versioned as 1.83.0-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru boost1.83-1.83.0/debian/changelog boost1.83-1.83.0/debian/changelog
--- boost1.83-1.83.0/debian/changelog 2024-05-27 06:59:36.0 +0200
+++ boost1.83-1.83.0/debian/changelog 2024-07-30 09:09:13.0 +0200
@@ -1,3 +1,13 @@
+boost1.83 (1.83.0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "Boost.Signals2 causes FTBFS", cherry-picking upstream patch
+ (Closes: #1056100)
+ * Fix "autopkgtest regression with CMake 3.30+", enforcing the new CMP0167
+policy. (Closes: #1076426)
+
+ -- Tobias Frost Tue, 30 Jul 2024 09:09:13 +0200
+
boost1.83 (1.83.0-3) unstable; urgency=medium
* [4b317f3] Add upstream fix for dogecoin. (Closes: #1059133)
diff -Nru boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch
--- boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch 1970-01-01 01:00:00.0 +0100
+++ boost1.83-1.83.0/debian/patches/70-boost-causing-ftbfs-signal2-part1.patch 2024-07-28 10:57:52.0 +0200
@@ -0,0 +1,128 @@
+From 2ba258f7b465e7bde14663ca3a966019b4ec3694 Mon Sep 17 00:00:00 2001
+From: Frank Mori Hess
+Date: Sat, 30 Dec 2023 14:34:58 -0500
+Subject: [PATCH] Fix disconnect by slot when the slot is another signal.
+
+---
+ .../boost/signals2/detail/signal_template.hpp | 48 +++
+ 1 file changed, 39 insertions(+), 9 deletions(-)
+
+diff --git a/libs/signals2/include/boost/signals2/detail/signal_template.hpp b/include/boost/signals2/detail/signal_template.hpp
+index a399883c..4546906d 100644
+--- a/libs/signals2/include/boost/signals2/detail/signal_template.hpp
b/libs/signals2/include/boost/signals2/detail/signal_template.hpp
+@@ -103,9 +103,9 @@ namespace boost
+ BOOST_SIGNALS2_FORWARDED_ARGS(BOOST_SIGNALS2_NUM_ARGS));
+ }
+ template
+- bool operator==(const T &other) const
++ bool contains(const T &other) const
+ {
+- return _fun == other;
++ return _fun.contains(other);
+ }
+ private:
+ BOOST_SIGNALS2_BOUND_EXTENDED_SLOT_FUNCTION_N(BOOST_SIGNALS2_NUM_ARGS)()
+@@ -115,6 +115,8 @@ namespace boost
+ boost::shared_ptr _connection;
+ };
+
++ template
++class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
+ template
+ class BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
+
+@@ -150,6 +152,8 @@ namespace boost
+ typedef GroupCompare group_compare_type;
+ typedef typename detail::slot_call_iterator_t > slot_call_iterator;
++typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
++ weak_signal_type;
+
+ BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)(const combiner_type &combiner_arg,
+ const group_compare_type &group_compare):
+@@ -531,13 +535,20 @@ namespace boost
+ {
+ (*it)->nolock_disconnect(lock);
+ }else
+-{
+- // check for wrapped extended slot
++{ // check for wrapped extended slot
+ bound_extended_slot_function_type *fp;
+ fp = (*it)->slot().slot_function().template target();
+- if(fp && function_equal(*fp, slot))
++ if(fp && fp->contains(slot))
+ {
+ (*it)->nolock_disconnect(lock);
++ }else
++ { // check for wrapped signal
++weak_signal_type *fp;
++fp = (*it)->slot().slot_function().template target();
++if(fp && fp->contains(slot))
++{
++ (*it)->nolock_disconnect(lock);
++}
+ }
+ }
+ }
+@@ -588,8 +599,6 @@ namespace boost
+ const boost::shared_ptr _mutex;
+ };
+
+- template
+-class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
+ }
+
+ template
+@@ -603,8 +612,7 @@ namespace boost
+ typedef detail::BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+ impl_class;
+ public:
+- typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+- weak_signal_type;
++ typedef typename impl_class::weak_signal_type weak_signal_type;
+ friend class detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+ ;
+
+@@ -746,12 +754,24 @@ namespace boost
+ using std::swap;
+ swap(_pimpl, other._pimpl);
+ }
++ bool operator==(const BOOST_SIGN
Bug#1056100: boost1.83: Boost.Signals2 causes FTBFS
Source: boost1.83
Followup-For: Bug #1056100
Control: tags -1 ftbfs patch
I've extraced the upsteam patches, they seem to work for swift-im.
Attached for your convenience.
--
tobi
-- System Information:
Debian Release: trixie/sid
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.9.11-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 2ba258f7b465e7bde14663ca3a966019b4ec3694 Mon Sep 17 00:00:00 2001
From: Frank Mori Hess
Date: Sat, 30 Dec 2023 14:34:58 -0500
Subject: [PATCH] Fix disconnect by slot when the slot is another signal.
---
.../boost/signals2/detail/signal_template.hpp | 48 +++
1 file changed, 39 insertions(+), 9 deletions(-)
diff --git a/libs/signals2/include/boost/signals2/detail/signal_template.hpp b/include/boost/signals2/detail/signal_template.hpp
index a399883c..4546906d 100644
--- a/libs/signals2/include/boost/signals2/detail/signal_template.hpp
+++ b/libs/signals2/include/boost/signals2/detail/signal_template.hpp
@@ -103,9 +103,9 @@ namespace boost
BOOST_SIGNALS2_FORWARDED_ARGS(BOOST_SIGNALS2_NUM_ARGS));
}
template
- bool operator==(const T &other) const
+ bool contains(const T &other) const
{
- return _fun == other;
+ return _fun.contains(other);
}
private:
BOOST_SIGNALS2_BOUND_EXTENDED_SLOT_FUNCTION_N(BOOST_SIGNALS2_NUM_ARGS)()
@@ -115,6 +115,8 @@ namespace boost
boost::shared_ptr _connection;
};
+ template
+class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
template
class BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
@@ -150,6 +152,8 @@ namespace boost
typedef GroupCompare group_compare_type;
typedef typename detail::slot_call_iterator_t > slot_call_iterator;
+typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
+ weak_signal_type;
BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)(const combiner_type &combiner_arg,
const group_compare_type &group_compare):
@@ -531,13 +535,20 @@ namespace boost
{
(*it)->nolock_disconnect(lock);
}else
-{
- // check for wrapped extended slot
+{ // check for wrapped extended slot
bound_extended_slot_function_type *fp;
fp = (*it)->slot().slot_function().template target();
- if(fp && function_equal(*fp, slot))
+ if(fp && fp->contains(slot))
{
(*it)->nolock_disconnect(lock);
+ }else
+ { // check for wrapped signal
+weak_signal_type *fp;
+fp = (*it)->slot().slot_function().template target();
+if(fp && fp->contains(slot))
+{
+ (*it)->nolock_disconnect(lock);
+}
}
}
}
@@ -588,8 +599,6 @@ namespace boost
const boost::shared_ptr _mutex;
};
- template
-class BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS);
}
template
@@ -603,8 +612,7 @@ namespace boost
typedef detail::BOOST_SIGNALS2_SIGNAL_IMPL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
impl_class;
public:
- typedef detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
- weak_signal_type;
+ typedef typename impl_class::weak_signal_type weak_signal_type;
friend class detail::BOOST_SIGNALS2_WEAK_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)
;
@@ -746,12 +754,24 @@ namespace boost
using std::swap;
swap(_pimpl, other._pimpl);
}
+ bool operator==(const BOOST_SIGNALS2_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS) & other) const
+ {
+return _pimpl.get() == other._pimpl.get();
+ }
protected:
virtual shared_ptr lock_pimpl() const
{
return _pimpl;
}
private:
+ // explicit private copy constructor to avoid compiler trying to do implicit conversions to signal
+ explicit BOOST_SIGNALS2_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS)(
+const BOOST_SIGNALS2_SIGNAL_CLASS_NAME(BOOST_SIGNALS2_NUM_ARGS) & other) BOOST_NOEXCEPT
+ {
+ // noncopyable
+ BOOST_ASSERT(false);
+ }
+
shared_ptr
_pimpl;
};
@@ -802,6 +822,16 @@ namespace boost
shared_pimpl(_weak_pimpl.lock());
return (*shared_pimpl)(BOOST_SIGNALS2_SIGNATURE_ARG_NAMES(BOOST_SI
Bug#1072226: RFS: serious-engine/0~git20230724+dfsg-1 [ITP]
Control: tags -1 moreinfo Hi, a short review: - You're repacking the source. It's not clear to me why you are removing the files. Can you expand? - d/patches: (more a hint, as maintaining patches in Debian will cause extra work down the road for you…): Please consider upstream the patches, the write-to-userdir and the use-system-zlib might be candidates. As serious-source is using CMake, the use-system-zlib patch could be rewritten that CMake is looking for the system's zlib, and if it is found use that, otherwise add the bundled zlib to the include path. (For illustration, I did something similar recently: https://github.com/codereader/DarkRadiant/pull/43) - (Another hint) Please upstream the manpages. - What is the copyright of the logos (debian/*svg)? Where are they from? - (optional) Please add a repository for the packaging on salsa, maybe even under the games team umbrella? (I can create one for you, if you want to go that route.) The README says: Running --- This version of the engine comes with a set of resources (`\SE1_10.GRO`) that allow you to freely use the engine without any additional resources required. However if you want to open or modify levels from Serious Sam Classic: The First Encounter or The Second Encounter (including most user-made levels), you will have to copy the game's resources (.GRO files) into the engine folder. You can buy the original games on Steam, as a part of a bundle with Serious Sam Revolution ( http://store.steampowered.com/app/227780 ) - Are the resources mentioned redistributeable or even DFSG licensed? - The README also mentions level editors. Do they compile for linux? If both could be answered yes, your package could go into main. -- tobi On Thu, May 30, 2024 at 07:34:07PM +0200, Sébastien Noel wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "serious-engine": > > * Package name : serious-engine >Version : 0~git20230724+dfsg-1 >Upstream contact : https://github.com/ptitSeb/Serious-Engine/issues > * URL : https://www.croteam.com/serious-sam-source-code-released/ > * License : GPL-2 > * Vcs : https://salsa.debian.org/twolife/serious-engine >Section : contrib/games > > The source builds the following binary packages: > > serious-sam-tfe - Serious Sam - The First Encounter > serious-sam-tse - Serious Sam - The Second Encounter > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/serious-engine/ > > Alternatively, you can download the package with 'dget' using this > command: > > dget -x > https://mentors.debian.net/debian/pool/contrib/s/serious-engine/serious-engine_0~git20230724+dfsg-1.dsc > > Changes for the initial release: > > serious-engine (0~git20230724+dfsg-1) unstable; urgency=low > . >* Initial release. Closes: #1034630 > > > This package alone isn't of any use; it only contains the game engine, > an engine that has no Free data and therefore is in contrib. > You will need a copy of the original game for this package to be > useful. > Please use game-data-packager to build a .deb of proprietary data (gog > or steam) to unleash the full potential of this code. > > Best Regards, > Sébastien >
Bug#1077252: RFS: tty-clock/2.3-git.2021.11.21.f2f847c-1 [ITA] -- simple terminal clock
Control: tags -1 moreinfo Hi, Thanks for your work on the package! (please not that I will NOT sponsor this upload with from a psedonym; this is a personal policy of mine, others might have different policies) A short review; - d/control VCS-* Please keep the package minimum on salsa, better even in the Debian namespace. If you need access rights, that can be done, just ask (with your salsa username) - d/changelog Please mention the dropped patch as well, as well the reason why it has been dropped. Has it been applied upstream? - d/copyright should transferred to DEP-5 style, ands needs updating, as copyright statments in the code a slightly different. -- tobi On Sat, Jul 27, 2024 at 08:08:56PM +0900, EiPiFun wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "tty-clock": > > * Package name : tty-clock > Version : 2.3-git.2021.11.21.f2f847c-1 > Upstream contact : xorg62 > * URL : https://github.com/xorg62/tty-clock > * License : BSD 3-Clause > * Vcs : https://github.com/EiPiFun/tty-clock > Section : utils > > The source builds the following binary packages: > > tty-clock - simple terminal clock > > It is a small clock using lib ncurses, which could be used as a clock > of course, and it could act as a simple screensaver for device without > desktop environment. It is easy to use and does have some functions. > But it was orphaned and I just want to maintain it. > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/tty-clock/ > > Alternatively, you can download the package with 'dget' using this > command: > > dget -x > https://mentors.debian.net/debian/pool/main/t/tty-clock/tty-clock_2.3-git.2021.11.21.f2f847c-1.dsc > > Changes since the last upload: > > tty-clock (2.3-git.2021.11.21.f2f847c-1) unstable; urgency=medium > . > * Adopting package (Closes: #1031941). > * New upstream release based on latest git commit. > * Add 0003-Makefile-improve_cross_build.patch: > - Improve cross build by change hardcoded pkgconf > > Regards, >
Bug#497888: backuppc bug triaging -- closing ancient bugs
Hi, I was going through those very old bugs and decided to close them, as BackupPC V4 has evolved a lot and a lot of those bugs seems to be feature requests, unsure if the problems still exist or otherwise not actionable. Please feel free to reopen the bugs, if think that is sensible, or maybe if it as feature request check directly with upstream. -- tobi
Bug#1076253: RFS: sosreport/4.7.2-1 [ITA] -- Set of tools to gather troubleshooting data from a system
Control: reassign -1 sponsorship-requests Control: merge 1076347 -1 This seems to be an duplicate of #1076347
Bug#1074596: (no subject)
Control: -1 moreinfo Hi Zixing Liu, > cpio (2.15+dfsg-2) UNRELEASED; urgency=medium > . > * Use compat level 13 (Closes: #1073111, #851631). > - Switch to use autoconf Debian Helper template. > - Switch to use dh generated alternatives scripts. > - Remove all manual installation steps from d/rules. > Those bugs seems to be out of scope for an NMU. Please see the developers reference about NMUs in general. Have you tried contacted the maintainer? On Thu, Jul 25, 2024 at 09:31:06PM -0600, Zixing Liu wrote: > Control: retitle -1 cpio/2.15+dfsg-1.1 [NMU] -- GNU cpio -- a program to > manage archives of files > > Hi, > > I have fixed the packaging and re-uploaded the fixed version to > mentors.debian.org. > Please see my previous message for the link. > > Thanks, > Zixing >
Bug#1077091: src:sosreport: d/copyright inaccurate
Source: sosreport Severity: serious Justification: Policy 4.5 (Found during reviewing RFS #1076347) On Thu, 25 Jul 2024 13:13:28 +0100 Arif Ali wrote: > I've delayed the copyright updates until we've discussed this upstream, so > no changes there for the time being. (It seems that part of the discussions are not on the bug (at least I do not see a Chris participating here)) d/copyright needs to reflect the code "verbatim" -- see Policy Checking a random file, (sos/report/archive.py) the file is licenses GPL2 *only*, while d/copyright says GPL2 *or later*. (An inaccurate d/copyright is a RC bug and a blocker for this RFS)
Bug#1076347: RFS: sosreport/4.7.2-1 [ITA]-- Set of tools to gather troubleshooting data from a system
Control: tags -1 moreinfo On Thu, 25 Jul 2024 13:13:28 +0100 Arif Ali wrote: > I've delayed the copyright updates until we've discussed this upstream, so > no changes there for the time being. (It seems that part of the discussions are not on the bug (at least I do not see a Chris participating here)) d/copyright needs to reflect the code "verbatim" -- see Policy Checking a random file, (sos/report/archive.py) the file is licenses GPL2 *only*, while d/copyright says GPL2 *or later*. (An inaccurate d/copyright is a RC bug and a blocker for this RFS) -- tobi
Bug#1075742: RFS: adminer/4.8.1-3 [RC] -- Web-based database administration tool
Control: tags -1 moreinfo Please remove the tag moreinfo once you've done investigating. Thanks! -- tobi On Mon, 8 Jul 2024 18:17:04 +0200 Alexandre Rossi wrote: > No clue as to where those directories come from, investigating.
Bug#1055431: RFS: scala-mode-el/1:1.1.0+git20221025.5d7cf21-1 [RC] [Team] -- transitional dummy package, scala-mode-el to elpa-scala-mode
Control: tags -1 moreinfo (Tagging moreinfo as the package seems not be ready , please remove tag when it is ready for the next round of review, or if I misunderstood the conversation and it is ready already now)
Bug#1076671: RFS: uriparser/0.9.8+dfsg-2 -- documentation files for uriparser
On Fri, Jul 26, 2024 at 03:01:43AM +0100, Phil Wyett wrote: > Hi, > > The current 'Standards-Version' is 4.7.0[1]. It is the packages in Debian > that have yet to catch up. Of course, my tired eyes had got that parsing backwards. Sorry for that part. > [1] https://www.debian.org/doc/debian-policy/ > > Regards > > Phil > > On Fri, 2024-07-26 at 03:49 +0200, Tobias Frost wrote: > > Control: tags -1 -confirmed +moreinfo > > > > Hi Jörg, > > > > > Version : 0.9.8+dfsg-2 > > > Package name : uriparser > > > > the only change seem to be that of VCS-Git; usually such kind of changes > > should be compared with others, it should be avoided to upload if this > > is the only change. As lintian has some suggetions: > > > > W: uriparser source: newer-standards-version 4.7.0 (current is 4.6.2) > > I: uriparser source: patch-not-forwarded-upstream > > [debian/patches/0001-missing_pthread.patch] > > > > can you solve those and then do the upload? > > > > TIA > > -- > > tobi > > > > On Sun, Jul 21, 2024 at 08:04:51PM +0200, Jörg Frings-Fürst wrote: > > > Package: sponsorship-requests > > > Severity: normal > > > > > > Dear mentors, > > > > > > I am looking for a sponsor for my package "uriparser": > > > > > > Upstream contact : [fill in name and email of upstream] > > > URL : http://uriparser.sourceforge.net > > > License : LGPL-2.1+, BSD-3-clause > > > Vcs : https://git.jff.email/cgit/uriparser.git > > > Section : libs > > > > > > The source builds the following binary packages: > > > > > > liburiparser1 - URI parsing library compliant with RFC 3986 > > > liburiparser-dev - development files for uriparser > > > liburiparser-doc - documentation files for uriparser > > > > > > To access further information about this package, please visit the > > > following > > > URL: > > > > > > https://mentors.debian.net/package/uriparser/ > > > > > > Alternatively, you can download the package with 'dget' using this > > > command: > > > > > > dget -x > > > https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.8+dfsg-2.dsc > > > > > > or from > > > > > > git > > > https://git.jff.email/cgit/uriparser.git?h=release%2Fdebian%2F0.9.8%2Bdfsg-2 > > > > > > > > > > > > > > > Changes since the last upload: > > > > > > uriparser (0.9.8+dfsg-2) unstable; urgency=medium > > > . > > > * debian/control: > > > - Fix Vcs-Git URL. > > > > > > CU > > > Jörg > > > > > > -- > > > New: > > > GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D > > > GPG key (long) : 09F89F3C8CA1D25D > > > GPG Key: 8CA1D25D > > > CAcert Key S/N : 0E:D4:56 > > > > > > > > > Jörg Frings-Fürst > > > D-54470 Lieser > > > > > > > > > git: https://git.jff.email/cgit/ > > > > > > Skype:jff-skype@jff.email > > > Jami: joergfringsfuerst > > > Telegram: @joergfringsfuerst > > > Matrix: @joergff:matrix.snct-gmbh.de > > > > > > My wish list: > > > - Please send me a picture from the nature at your home. > > > > > > > > > > > > > > > > -- > "I play the game for the game’s own sake" > > Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans > > -- > > Internet Relay Chat (IRC): kathenas > > Website: https://kathenas.org > > Instagram: https://instagram.com/kathenasorg/ > > Buy Me A Coffee: https://buymeacoffee.com/kathenasorg > > -- >
Bug#1073960: RFS: libmobi/0.12+dfsg-1 [RC] -- Tools for handling Mobipocket/Kindle ebook format documents
Control: tag -1 moreinfo -confirmed On Thu, Jun 20, 2024 at 07:14:45PM +0200, Bartek Fabiszewski wrote: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "libmobi": > > * Package name : libmobi >Version : 0.12+dfsg-1 >Upstream contact : Bartek Fabiszewski > * URL : https://github.com/bfabiszewski/libmobi > * License : ISC, BSD-4-Clause, Unlicense, public-domain, LGPL-3+ > * Vcs : https://salsa.debian.org/debian/libmobi >Section : libs (Review based on the upload 2024-07-21 18:39) - There are empty files: d/libmobi0.(install,docs,symbols) --> drop them - The patches could have dep3 information whether you have applied them upstream as well. - There are changes that are not documented in d/changelog, like (not exhaustive) - bump of SV to 4.7.0 (did you have to do any changes because of it?) and - update of d/copyright years (d/copyright should reflect the data in the source file "verbatim" - you update the copyright years in d/copyright 2024, but did not change the year in your source code. That violates the "verbatim". So either bump the year in your source code too, or record the years as they are in the source - usually d/changelog's purpose is to document the changes to the Debian *packaging*, not to document upstream changes. See Policy 4.6. (You've got your upstream changelog, that is where your upstream changes shoudl got to. In this case I'd write the changelog as: libmobi (0.12+dfsg-1) unstable; urgency=medium * New upstream release. (Closes: #1073331) * * Updated d/copyright years * New patches to fixing typo/tweak wording in the manpage * (...) -- Bartek Fabiszewski Mon, 17 Jun 2024 13:34:25 +0200 -- tobi
Bug#1076671: RFS: uriparser/0.9.8+dfsg-2 -- documentation files for uriparser
Control: tags -1 -confirmed +moreinfo Hi Jörg, > Version : 0.9.8+dfsg-2 > Package name : uriparser the only change seem to be that of VCS-Git; usually such kind of changes should be compared with others, it should be avoided to upload if this is the only change. As lintian has some suggetions: W: uriparser source: newer-standards-version 4.7.0 (current is 4.6.2) I: uriparser source: patch-not-forwarded-upstream [debian/patches/0001-missing_pthread.patch] can you solve those and then do the upload? TIA -- tobi On Sun, Jul 21, 2024 at 08:04:51PM +0200, Jörg Frings-Fürst wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "uriparser": > > Upstream contact : [fill in name and email of upstream] > URL : http://uriparser.sourceforge.net > License : LGPL-2.1+, BSD-3-clause > Vcs : https://git.jff.email/cgit/uriparser.git > Section : libs > > The source builds the following binary packages: > > liburiparser1 - URI parsing library compliant with RFC 3986 > liburiparser-dev - development files for uriparser > liburiparser-doc - documentation files for uriparser > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/uriparser/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.8+dfsg-2.dsc > > or from > > git > https://git.jff.email/cgit/uriparser.git?h=release%2Fdebian%2F0.9.8%2Bdfsg-2 > > > > > Changes since the last upload: > > uriparser (0.9.8+dfsg-2) unstable; urgency=medium > . > * debian/control: > - Fix Vcs-Git URL. > > CU > Jörg > > -- > New: > GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D > GPG key (long) : 09F89F3C8CA1D25D > GPG Key: 8CA1D25D > CAcert Key S/N : 0E:D4:56 > > > Jörg Frings-Fürst > D-54470 Lieser > > > git: https://git.jff.email/cgit/ > > Skype:jff-skype@jff.email > Jami: joergfringsfuerst > Telegram: @joergfringsfuerst > Matrix: @joergff:matrix.snct-gmbh.de > > My wish list: > - Please send me a picture from the nature at your home. > > > >
Bug#1072448: rbdoom3bfg: FTBFS with ffmpeg 7.0
Control: tags -1 pending Thanks for the patch! I've imported it into the git repo, so once the transition starts the fix can be uploaded. Cheers, tobi
Bug#1038895: freecad: 'Path' workbench throw 'marshal data too short' error.
Control: close -1 Hi Petter, I'm looking through old bugs and I am not sure if this bug is actionable, therefore I'm going to close it. (it can be reopened if new information makes it actionable) -- tobi
Bug#1032834: freecad: Segmentation fault while redoing
Control: tags -1 moreinfo Control: close -1 As not additional information has been provided, closing. (The bug can be reopened with addtional informations, if needed, of course)
Bug#1077021: RM: obs-scene-tree-view [ppc64el] -- RoQA; B-D not available for arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-scene-tree-v...@packages.debian.org Control: affects -1 + src:obs-scene-tree-view User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove the package for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1033695: freecad-python3: FreeCAD segfaults instantly
Control: close -1 As no addtional information has been provided, closing this bug.
Bug#1077015: RM: obs-color-monitor [ppc64el] -- RoQA; B-D no longer available on arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-color-moni...@packages.debian.org Control: affects -1 + src:obs-color-monitor User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove the package for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1077014: RM: obs-transition-table [ppc64el] -- RoQA; B-D not available on arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-transition-ta...@packages.debian.org Control: affects -1 + src:obs-transition-table User: ftp.debian@packages.debian.org Usertags: remove Hi, The package indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) -- tobi
Bug#1077013: RM: obs-source-copy [ppc64el] -- RoQA; B-D no longer available for arch
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-source-c...@packages.debian.org Control: affects -1 + src:obs-source-copy User: ftp.debian@packages.debian.org Usertags: remove Hi, please remove the package, it indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1077000: RM: obs-advanced-scene-switcher [ppc64el] -- RoQA; B-D not available
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-advanced-scene-switc...@packages.debian.org Control: affects -1 + src:obs-advanced-scene-switcher User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove obs-advanced-scene-switcher for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1076962: linux: Enable CONFIG_NETKIT=m
Subject: linux: Enable CONFIG_NETKIT=m Package: linux Severity: wishlist X-Debbugs-Cc: deb+net...@aibor.de Dear Maintainer, Recently, support for a new network device type "netkit" was added. Support must be explicitley enabled in the kernel with the config key CONFIG_NETKIT=m https://www.kernelconfig.io/config_netkit Please enable this new device type in the kernel config. Thank you in advance. Best regards, Tobias Böhm -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 6.9.7+bpo-arm64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1076783: linux-image: CONFIG_SENSORS_ADM1021=m dropped since 6.1
Package: linux-image Version: 6.1 Severity: normal Hi, it seems that the adm1021 driver module was dropped from the kernel config (CONFIG_SENSORS_ADM1021=m) starting from Debian Bookworm. There are several Siemens devices that use this chip for temperature monitoring and many of these devices rely on Debian. An absence of the driver is an issue for us that has to be fixed downstream at the moment. Is it possible to re-add the config switch? Was the omission of the ADM1021 driver part of a regular cleanup process or is there some technical reasons behind this decision? Thanks and all the best, Tobias
Bug#1076776: RM: obs-time-source [ppc64el] -- RoQA; B-D not available
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: obs-time-sou...@packages.debian.org, highvolt...@debian.org Control: affects -1 + src:obs-time-source User: ftp.debian@packages.debian.org Usertags: remove Dear ftp-masters, please remove obs-time-source for ppc64el. It indirectly B-D on luajit, which is not built anymore for pp64el (set by architecture list in its d/control) Thanks! -- tobi
Bug#1052101: gnome-shell-extension-hamster: diff for NMU version 0.10.0+git20240714-0.1
Control: tags 1052101 + patch
Control: tags 1052101 + pending
Dear maintainer,
I've prepared an NMU for gnome-shell-extension-hamster (versioned as
0.10.0+git20240714-0.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
The debdiff is available as MRs for the affected branches:
master:
https://salsa.debian.org/projecthamster-team/gnome-shell-extension-hamster/-/merge_requests/4
upstream:
https://salsa.debian.org/projecthamster-team/gnome-shell-extension-hamster/-/merge_requests/5
pristine-tar
https://salsa.debian.org/projecthamster-team/gnome-shell-extension-hamster/-/merge_requests/6
--
Regards,
tobi
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/data/metadata.json.in gnome-shell-extension-hamster-0.10.0+git20240714/data/metadata.json.in
--- gnome-shell-extension-hamster-0.10.0+git20230901/data/metadata.json.in 2023-08-10 18:33:38.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/data/metadata.json.in 2024-04-09 15:09:59.0 +0200
@@ -10,14 +10,8 @@
"gettext-domain": "hamster-shell-extension",
"settings-schema": "org.gnome.shell.extensions.project-hamster",
"shell-version": [
-"3.34",
-"3.36",
-"3.38",
-"40",
-"41",
-"42",
-"43",
-"44"
+ "45",
+ "46"
],
"url": "https://github.com/projecthamster/hamster-shell-extension.git";,
"uuid": @UUID@
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml gnome-shell-extension-hamster-0.10.0+git20240714/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml
--- gnome-shell-extension-hamster-0.10.0+git20230901/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml 2023-08-10 18:33:38.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/data/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml 2024-04-09 15:09:59.0 +0200
@@ -1,10 +1,10 @@
-
+
0
Placement in the panel.
-Position to place extension at. 0 - default, 1 - replace calendar, 2 - replace activities.
+Position to place extension at. 0 - default, 1 - replace calendar, 2 - replace activities, 3 - Center, next to calendar.
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/debian/changelog gnome-shell-extension-hamster-0.10.0+git20240714/debian/changelog
--- gnome-shell-extension-hamster-0.10.0+git20230901/debian/changelog 2023-09-01 08:43:28.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/debian/changelog 2024-07-14 09:43:35.0 +0200
@@ -1,3 +1,12 @@
+gnome-shell-extension-hamster (0.10.0+git20240714-0.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * New upstream git snaphsot with GNOME Shell 46 compat. (Closes: #1052101)
+ * Update version constraints on gnome-shell, as this version is only
+compatible with GNOME Shell 45 and up.
+
+ -- Tobias Frost Sun, 14 Jul 2024 09:43:35 +0200
+
gnome-shell-extension-hamster (0.10.0+git20230901-1) unstable; urgency=medium
* New upstream git snapshot with GNOME Shell 44 compat. (Closes: #1041574)
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/debian/control gnome-shell-extension-hamster-0.10.0+git20240714/debian/control
--- gnome-shell-extension-hamster-0.10.0+git20230901/debian/control 2023-09-01 08:43:28.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/debian/control 2024-07-14 09:43:35.0 +0200
@@ -18,8 +18,8 @@
Architecture: all
Depends:
hamster-time-tracker,
- gnome-shell (>= 3.38),
- gnome-shell (<< 45~),
+ gnome-shell (>= 45),
+ gnome-shell (<< 47~),
${misc:Depends}
Description: GNOME Shell extension for the Hamster Time Tracker
Project Hamster helps you to keep track of how much time you spend on various
diff -Nru gnome-shell-extension-hamster-0.10.0+git20230901/extension/extension.js gnome-shell-extension-hamster-0.10.0+git20240714/extension/extension.js
--- gnome-shell-extension-hamster-0.10.0+git20230901/extension/extension.js 2023-08-10 18:33:38.0 +0200
+++ gnome-shell-extension-hamster-0.10.0+git20240714/extension/extension.js 2024-04-09 15:09:59.0 +0200
@@ -21,18 +21,14 @@
*/
-const GLib = imports.gi.GLib;
-const Shell = imports.gi.Shell;
-const Meta = imports.gi.Meta;
-const Main = imports.ui.main;
-const Gio = imports.gi.Gio;
-
-const Gettext = imports.gettext.domain('hamster-shell-extension');
-const _ = Gettext.gettext;
-
-const ExtensionUtils = imports.misc.extensionUtils;
-const Me = ExtensionUtils.getCurrentExtension();
-const PanelWidget = Me.imports.widgets.panelWidget.PanelWidget;
+import GLib fro
Bug#1065873: hamster-time-tracker: diff for NMU version 3.0.3-1.1
(Updated debdiff, also dropping python3-distutils from Depends:)
MR:
https://salsa.debian.org/projecthamster-team/hamster-time-tracker/-/merge_requests/3
Dear maintainer,
I've prepared an NMU for hamster-time-tracker (versioned as 3.0.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru hamster-time-tracker-3.0.3/debian/changelog hamster-time-tracker-3.0.3/debian/changelog
--- hamster-time-tracker-3.0.3/debian/changelog 2023-11-24 00:40:13.0 +0100
+++ hamster-time-tracker-3.0.3/debian/changelog 2024-07-14 08:56:19.0 +0200
@@ -1,3 +1,10 @@
+hamster-time-tracker (3.0.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python3-distutils from B-D (Closes: #1065873)
+
+ -- Tobias Frost Sun, 14 Jul 2024 08:56:19 +0200
+
hamster-time-tracker (3.0.3-1) unstable; urgency=medium
[ Raphaël Hertzog ]
diff -Nru hamster-time-tracker-3.0.3/debian/control hamster-time-tracker-3.0.3/debian/control
--- hamster-time-tracker-3.0.3/debian/control 2023-11-24 00:40:13.0 +0100
+++ hamster-time-tracker-3.0.3/debian/control 2024-07-14 08:56:19.0 +0200
@@ -15,7 +15,6 @@
python3,
python3-cairo,
python3-dbus,
- python3-distutils,
python3-gi
Standards-Version: 4.6.2
Homepage: https://github.com/projecthamster/hamster
@@ -31,7 +30,6 @@
libjs-jquery-ui,
python3-cairo,
python3-dbus,
- python3-distutils,
python3-gi,
python3-gi-cairo,
${misc:Depends},
Bug#1065873: hamster-time-tracker: diff for NMU version 3.0.3-1.1
Control: tags 1065873 + patch Control: tags 1065873 + pending Dear maintainer, I've prepared an NMU for hamster-time-tracker (versioned as 3.0.3-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru hamster-time-tracker-3.0.3/debian/changelog hamster-time-tracker-3.0.3/debian/changelog --- hamster-time-tracker-3.0.3/debian/changelog 2023-11-24 00:40:13.0 +0100 +++ hamster-time-tracker-3.0.3/debian/changelog 2024-07-14 08:49:38.0 +0200 @@ -1,3 +1,10 @@ +hamster-time-tracker (3.0.3-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Drop python3-distutils from B-D (Closes: #1065873) + + -- Tobias Frost Sun, 14 Jul 2024 08:49:38 +0200 + hamster-time-tracker (3.0.3-1) unstable; urgency=medium [ Raphaël Hertzog ] diff -Nru hamster-time-tracker-3.0.3/debian/control hamster-time-tracker-3.0.3/debian/control --- hamster-time-tracker-3.0.3/debian/control 2023-11-24 00:40:13.0 +0100 +++ hamster-time-tracker-3.0.3/debian/control 2024-07-14 08:49:38.0 +0200 @@ -15,7 +15,6 @@ python3, python3-cairo, python3-dbus, - python3-distutils, python3-gi Standards-Version: 4.6.2 Homepage: https://github.com/projecthamster/hamster signature.asc Description: PGP signature
Bug#743969: fl-cow: new upstream release 0.10
Hi Petter, On Thu, Jul 11, 2024 at 07:41:15AM +0200, Petter Reinholdtsen wrote: > [Tobias Frost 2014-04-08] > > Thanks for considering packaging the upstream release 0.10 > > I had a look for it, but could not find release 0.10 anywhere. Any idea > where to find it? Its homepage has a link at the bottom, (it blends/hides there quite good :)) http://www.xmailserver.org/fl-cow-0.10.tar.gz Cheers, -- tobi > -- > Happy hacking > Petter Reinholdtsen
Bug#1076031: pyside breaks reverse dependencies by renaming library file
X-Debbugs-Cc: debian-rele...@lists.debian.org Control: reassign -1 pyside2 Control: affects -1 freecad This has been introduced by the upload of pyside3, which changed the libary name without managing that reverse dependencies so that they rebuilt. Dear pyside2 maintainers, please be more thoughtful and manage your transistions more carefully. This happend already in the past, see #1013881. Thanks. -- tobi
Bug#1050030: Slow boot with 2020.11-2+deb11u1 and building OVMF from source
Hello all, As noted before, going back to 2020.11-2+deb11u1 allows booting HVM domains. However, for us it slowed down the boot from half a minute to two minutes, when using PCI passthrough. The Xen community pointed out to me that this may be due to a patch for Xen not being built in that version (https://github.com/tianocore/edk2/commit/c05de360ec614f71716a201760b91ee055a5ff28). I propose to either - ship a Xen specific version of OVMF (as suggested here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978595 and above and similar to Fedora https://packages.fedoraproject.org/pkgs/edk2/edk2-ovmf-xen/) or - build Xen with OVMF included (the Xen build should supports this). However, I myself could get neither package to compile this way from Debian sources. We mitigated the problem for us, by building OVMF ourselves from git://xenbits.xen.org/ovmf.git for "edk2-stable202305", the latest tag found there. It should actually be the same for https://github.com/tianocore/edk2.git, but I did not try. On Debian 12 to make it work we - removed "brotli" from BaseTools/Source/C/Makefile (otherwise the build will fail with warnings treated as errors) - apt-get build-dep -y ovmf # Build needs GCC 11 instead of version 12 shipped with Debian 12, because otherwise again the build will end with warnings treated as errors - apt-get install -y gcc-11 g++-11 libgcc-11-dev - update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-11 1 - update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-11 1 - cd BaseTools; make -C Source/C - cd ..; OvmfPkg/build.sh -a X64 -b RELEASE -p OvmfPkg/OvmfXen.dsc Then "Build/OvmfXen/RELEASE_GCC5/FV/OVMF.fd" must be placed at "/usr/share/ovmf/OVMF.fd", because the Debian package for Xen is compiled with "--with-system-ovmf=/usr/share/ovmf/OVMF.fd". Best regards, Tobias
Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
control: tag -1 unreproducible control: severity -1 normal On Fri, 14 Jun 2024 19:39:23 +1200 Mark Robinson wrote: On completing the database migration I created a new person, added birth and death information including a new death location and notes, and clicked OK. This resulted in the python error referred to in the headline which left the new person with the OK button greyed out and no way to save it. The record was lost. Hi Mark, sorry about that. I've tried to reproduce this bug, using the steps you've described above. It worked without any problem on my system, so I'm not able to reproduce the faulty behaviour of gramps. I'm therefore lowering the severity, because otherwise gramps would be removed from testing. I currently don't think that this would be necessary. However, there should be an automatic backup of your database, as printed in the status messages: 11723: WARNING: upgrade.py: line 2218: If upgrade and loading the Family Tree works, you can delete the zip file at /home/mark/.gramps/ROBINSON__Mark_Gregory_2024-06-14_12-07-04.zip Could you try to extract that database version of your family tree and open it with gramps? The program should then ask you again to convert the tree to the new database format. Afterwards, could you repeat the steps above, i. e. creating a new person, adding birth and death information etc.? Then please report back if the error still occurs. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1073827: (no subject)
Hi, I am seeing exactly the same with chromium since 126.0.6478.56-1~deb12u1 Best Regards, Toby
Bug#1073233: plasma-workspace: Regression fix for CVE-2024-36041 is missing
Hello, I notice the described bug (session restore not working) on plasma with X11 on Debian/sid, currently using 5.27.11.1-1+b1. Greetings Tobi signature.asc Description: This is a digitally signed message part.
Bug#1061743: Gramps in Debian
Am 03.06.24 um 06:55 schrieb Ross Gammon: I will try and take a look this week. But if I fail, either of you are welcome to lose patience, merge it to master, and upload it for me. :-) Hi Ross, I've decided to lose patience. :-) No, seriously, I've built Gramps locally and did some test runs with it. Everything seems to work fine, so I've pushed my latest changes to salsa, merged it into the master branch, and uploaded to unstable. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072742: On Romanian translations in the iso-codes package
Am 07.06.24 um 13:08 schrieb Alex: Hello, I’d like to report an issue in the Romanian translations of the iso-codes package. I’m not sure whether this is the right place. The README says to open a Salsa issue but that requires authentication and my account is yet to be approved. If this isn’t the place, please instruct me on where to post as linux.debian.bugs.dist on Google Groups seems to be read-only. In any case, I want to report that the Romanian translations for the ISO 3166-2 data have unnecessary prefixes indicating the type of the subdivision (and sometimes suffixes too.) For example, “Alaska” is translated as “Statul Alaska” (i.e. “The state of Alaska”); the Romanian county of “Bacău” is translated as “Județul Bacău, România” (i.e. “The county of Bacău, România”); “Thüringen” is translated to "Landul Turingia, Germania” (i.e. “The land of Turingia, Germany") etc. It goes on and on for virtually all subdivisions. On the one hand, that’s not how Romanians refer to countries' subdivisions. For example, I was born in "Onești, Bacău", not “Onești, Bacău County”. Similarly, “Paris" is just “Paris”, not “Orașul metropolitan Paris (capitala), Franța” (i.e. “Metropolitan city of Paris (capital), France”). On the other hand, it looks like it's only the Romanian translation that does this, making it very odd in comparison. To add to the weirdness, the Zimbabwean province of "Matabeleland South” is translated as "Provincia Matabeleland South”, not even “Provincia Matabeleland Sud”, though "South Australia” is fully translated to "Statul Australia de sud”. I can and am willing to invest some time in reviewing and cleaning up at least some of the translations. Considering there’s many of them, it would take a while to cover all of them, though. There is of course the question of whether the Debian team is willing to consider accepting such changes. Regards, Alex Hi Alex, thanks so much for your bug report! I'm not speaking Romanian, so I cannot judge the quality of the Romanian translation. However, what you've written seems plausible to me, and I can at least infer from your examples that what you're writing is correct. All those translations have come from Weblate, where the iso-codes translation is hosted. The changes (adding those prefixes) have been done by a translator named Remus-Gabriel Chelu, I've added them in CC of this mail. Remus-Gabriel, would you be so kind to join this discussion on the Debian BTS and share your point of view? You can just reply to this mail, keeping all addresses in the loop. Many thanks in advance! The bug report can be seen here: https://bugs.debian.org/1072742 Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072241: src:manpages: fails to migrate to testing for too long: RC bug and B-D not in testing
Am 31.05.24 um 10:32 schrieb Dr. Tobias Quathamer: I couldn't find any explanation in the commit messages or debian/changelog. What's the reason for all those additional dependencies? Can't we get rid of them? I don't see how they are needed for building the package. I did not get a response, so I went ahead and uploaded a version without all those extra Build-Dependencies. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072241: src:manpages: fails to migrate to testing for too long: RC bug and B-D not in testing
Am 30.05.24 um 22:30 schrieb Paul Gevers: Source: manpages Version: 6.05.01-1 Severity: serious Control: close -1 6.8-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1072158 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:manpages has been trying to migrate for 59 days [2]. Hence, I am filing this bug. The version in unstable has an unresolved RC bug (#1072158) and one of its Build-Depends isn't in testing and can't migrate. [...] Hi Marcos, I've seen that you've added quite a lot of new packages to the Build-Depends of manpages, therefore the migration to testing is currently not possible (due to missing Build-Depends in testing). The list of packages in Build-Depends changed considerably between manpages 6.05.01-1 and manpages 6.7-1 from Build-Depends: debhelper-compat (= 13), groff (>= 1.23.0), mandoc to Build-Depends: debhelper-compat (= 13), groff (>= 1.23.0), groff-base, bsdextrautils, bzip2, binutils, clang, clang-tidy, cpp, cppcheck, cpplint, diffoscope, git, iwyu, lzip, man, mandoc, moreutils, pkgconf, xz-utils I couldn't find any explanation in the commit messages or debian/changelog. What's the reason for all those additional dependencies? Can't we get rid of them? I don't see how they are needed for building the package. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061743: Gramps in Debian
Am 27.05.24 um 15:38 schrieb IOhannes m zmölnig (Debian GNU|Linux): On 5/26/24 23:56, Dr. Tobias Quathamer wrote: The package builds on my machine, although I had to disable a single test for now. You'll find it in the newly created patch. Maybe you have an idea what's causing the failure, so it can be fixed properly. https://gramps-project.org/bugs/view.php?id=13305 i think this is just a wrong assumption on the side of the upstream testsuite (shadowed by their workflows). upstream evades this by ensuring that "~/.gramps/" is there before running the tests (both in their GitHub action, and in their debian/ packaging). i think that for now the proper resolution for the problem is to simply do a `mkdir "$CURDIR)/build/.gramps` before running the tests. (which i've now pushed to the 'experimental' branch) Great, thanks! That's a cleaner approach. as a sidenote: the testsuite now creates a *very* verbose buildlog (~420MB). is that ok? gf,madsr IOhannes Hm, I guess that's because of the "--verbose" option when running the tests. However, the buildlog has been similarly large in v5.1.6 as well. Could that to be due to the switch from nosetest to unittest? Maybe the --verbose option should be dropped? The buildlog gets shrinked to 1.4 MB, but the tests are only displayed as dots. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061743: Gramps in Debian
Am 24.05.24 um 21:23 schrieb Ross Gammon: Hi Tobias, There are no blockers other than real life getting in the way. I did start working on 5.2.0 in the experimental branch on Salsa. From memory, there was a problem with fuzzy patches, and the tedious checking of copyrights still to do. But I should probably merge the changes into master, and then import 5.2.2. If you have some spare cycles you are welcome to help move things along. I use gbp + quilt. Regards, Ross Hi Ross, I took some time to update the experimental branch to v5.2.2 and fix some FTBFS with the new upstream version. I've pushed my work to Salsa, please take a look if you have some time. The package builds on my machine, although I had to disable a single test for now. You'll find it in the newly created patch. Maybe you have an idea what's causing the failure, so it can be fixed properly. I haven't looked at the copyrights for now. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068464: deal.ii: FTBFS: libgmp not linked, libdeal.ii.g.so.9.5.1: error: undefined reference to '__gmpn_neg'
Control: tags -1 unreproducible Control: close -1 Hi Drew, I've rebuilt deal.ii in the course of the opencascade transition, and I cannot reproduce this FTBFS; petsc 3.20 is now in unstable too, and the binNMU has been done ~4 days ago, also without the failure you've seen. Buildds works too... Therefore, I'm closing this bug as non-reproducible. (it can be reopened of course if it reappears.) -- tobi
Bug#1070377: frr: CVE-2024-34088
Control: tags -1 fixed-upstream Control: forwarded -1 https://github.com/FRRouting/frr/pull/15674 Upstream has merged a fix.
Bug#1071473: transition: opencascade
Hi Emilio, thanks for the head up! opencascade is now in unstable and has built for all archs except riscv64, where the buildds are just busy right now and as they are currently building huge packages, this could last a few days. I think a strategic Dep-Wait will help :) Level2 : - f3d and kicad could use a binNMU, with a Dep-Wait on libocct-data-exchange-dev (>= 7.8.1) - freecad, netgen has been (team) uploaded. - horizon-eda and slic3r-prusa are both in DELAYED/2. Level3 : - gmsh has been team uploaded. Level4: - deal.ii will be team-uploaded soon. Thanks! -- tobi On Wed, May 22, 2024 at 08:50:35AM +0200, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 19/05/2024 23:08, Tobias Frost wrote: > > Package: release.debian.org > > Severity: normal > > X-Debbugs-Cc: opencasc...@packages.debian.org > > Control: affects -1 + src:opencascade > > User: release.debian@packages.debian.org > > Usertags: transition > > Control: block 1071284 by -1 > > Control: block 1071223 by -1 > > Control: block 1071470 by -1 > > Control: block 1071451 by -1 > > Control: block 1071471 by -1 > > > > Hi Release team, > > > > opencascade has a new release with breaking ABI, upstream versionied them as > > 7.8. The transition tracker [1] correctly picked it up already after the > > upload > > to experimental. > > > > [1] https://release.debian.org/transitions/html/auto-opencascade.html > > > > building the reverse depenencies most FTBFS due to library naming changes, > > but I was able to come up with patches for most, but they will require > > sourceful > > uploads. Freecad will require either backporting the upstream fixes or > > package > > a new upstream snapshot. > > > > This is the result of the compilation tests: > > > > Dependency level 2: > > > > f3d ✔ > > freecad (sid only) FTBFS, fixed in upstream git. > > horizon-eda patch available, #1071284 > > kicad ✔ > > netgen patch available, #1071223 > > slic3r-prusa (sid only) patch available, #1071470 > > > > Dependency level 3: > > gmshpatch available, #1071451 > > > > Dependency level 4: > > deal.ii patch available, #1071471 > > Will you help upload those fixes? Perhaps through delayed NMUs or team > uploads? If so, go ahead. > > Cheers, > Emilio signature.asc Description: PGP signature
Bug#1071470: slic3r-prusa: diff for NMU version 2.7.4+dfsg-1.1
Control: tags 1071470 + pending Dear maintainer, I've prepared an NMU for slic3r-prusa (versioned as 2.7.4+dfsg-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru slic3r-prusa-2.7.4+dfsg/debian/changelog slic3r-prusa-2.7.4+dfsg/debian/changelog --- slic3r-prusa-2.7.4+dfsg/debian/changelog 2024-04-18 07:26:21.0 +0200 +++ slic3r-prusa-2.7.4+dfsg/debian/changelog 2024-05-24 22:12:57.0 +0200 @@ -1,3 +1,11 @@ +slic3r-prusa (2.7.4+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with opencasacade 7.8.1 (Closes: #1071470) and +add a versioned B-D on it. + + -- Tobias Frost Fri, 24 May 2024 22:12:57 +0200 + slic3r-prusa (2.7.4+dfsg-1) unstable; urgency=medium * [3cddded] New upstream version 2.7.4+dfsg diff -Nru slic3r-prusa-2.7.4+dfsg/debian/control slic3r-prusa-2.7.4+dfsg/debian/control --- slic3r-prusa-2.7.4+dfsg/debian/control 2024-04-18 07:26:21.0 +0200 +++ slic3r-prusa-2.7.4+dfsg/debian/control 2024-05-24 22:12:57.0 +0200 @@ -20,11 +20,11 @@ libheatshrink-dev, libnanosvg-dev, libnlopt-cxx-dev | libnlopt-dev (<< 2.4.2+dfsg-5~), - libocct-data-exchange-dev, - libocct-draw-dev, - libocct-foundation-dev, - libocct-modeling-algorithms-dev, - libocct-visualization-dev, + libocct-data-exchange-dev (>=7.8.1+dfsg1), + libocct-draw-dev (>=7.8.1+dfsg1), + libocct-foundation-dev (>=7.8.1+dfsg1), + libocct-modeling-algorithms-dev (>=7.8.1+dfsg1), + libocct-visualization-dev (>=7.8.1+dfsg1), libopenvdb-dev (>= 5.0), libopenvdb-tools, libpng-dev, diff -Nru slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch --- slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch 1970-01-01 01:00:00.0 +0100 +++ slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch 2024-05-24 22:12:57.0 +0200 @@ -0,0 +1,18 @@ +diff --git a/src/occt_wrapper/CMakeLists.txt b/src/occt_wrapper/CMakeLists.txt +index d8dd8e1..d27055f 100644 +--- a/src/occt_wrapper/CMakeLists.txt b/src/occt_wrapper/CMakeLists.txt +@@ -22,11 +22,8 @@ generate_export_header(OCCTWrapper) + find_package(OpenCASCADE REQUIRED) + + set(OCCT_LIBS +-TKXDESTEP +-TKSTEP +-TKSTEP209 +-TKSTEPAttr +-TKSTEPBase ++TKDESTEP ++TKDESTL + TKXCAF + TKXSBase + TKVCAF diff -Nru slic3r-prusa-2.7.4+dfsg/debian/patches/series slic3r-prusa-2.7.4+dfsg/debian/patches/series --- slic3r-prusa-2.7.4+dfsg/debian/patches/series 2024-04-18 07:26:21.0 +0200 +++ slic3r-prusa-2.7.4+dfsg/debian/patches/series 2024-05-24 22:12:57.0 +0200 @@ -8,3 +8,4 @@ Disable-preset-update-and-version-check-by-default.patch Patch-tests-for-Catch2-v3-compatibility.patch Explicit-wxWidgets-initializers.patch +occt-7.8.patch signature.asc Description: PGP signature
Bug#1071643: horizon-eda: diff for NMU version 2.6.0-2.1
Control: tags 1071643 + pending Dear maintainer, I've prepared an NMU for horizon-eda (versioned as 2.6.0-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. (note: the previous patch was by accident reversed.) Regards. diff -Nru horizon-eda-2.6.0/debian/changelog horizon-eda-2.6.0/debian/changelog --- horizon-eda-2.6.0/debian/changelog 2024-05-22 17:31:22.0 +0200 +++ horizon-eda-2.6.0/debian/changelog 2024-05-24 20:52:05.0 +0200 @@ -1,3 +1,10 @@ +horizon-eda (2.6.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS, add missing B-D on cppzmq-dev. Closes: #1071643 + + -- Tobias Frost Fri, 24 May 2024 20:52:05 +0200 + horizon-eda (2.6.0-2) unstable; urgency=medium * Fix build depend diff -Nru horizon-eda-2.6.0/debian/control horizon-eda-2.6.0/debian/control --- horizon-eda-2.6.0/debian/control 2024-05-22 17:30:29.0 +0200 +++ horizon-eda-2.6.0/debian/control 2024-05-24 20:52:01.0 +0200 @@ -9,7 +9,7 @@ libglm-dev, libgit2-dev, libcurl4-gnutls-dev, libocct-data-exchange-dev, libdxflib-dev (>> 3.17.0), libarchive-dev, libzip-dev, libglib2.0-dev, libpodofo-dev, python3-cairo-dev, libosmesa6-dev, - dh-python + dh-python, cppzmq-dev Standards-Version: 4.4.0 Homepage: https://horizon-eda.org/ Rules-Requires-Root: no signature.asc Description: PGP signature
