Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed
Indeed the transitional mariadb-server-10.5 fixes the issue. What do you Andreas suggest we do now? It is already past freeze for Bookworm, and this is not just a small fix but also introduces a new package (albeit transitional). Let me know how you want to proceed and I can immediately tomorrow push this to experimental or unstable if that is aligned with your plan. Alternatively we can ask for pre-approval from the release team.
Bug#1036359: crashes with (wrong-type-argument consp nil)
Nicholas D Steeves writes: > I also confirmed that both the patched version (in the staging branch) > and unpatched version (in bookworm) work correctly with > > > https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-36-gitolite-gitweb-retirement.md > > when one loads markdown-toc and generates the toc before native comp > kicks in. Sorry for not being clear. What I mean is that I believe that this bug is triggered by native compilation, and that it's unlikely that I'll find enough time figure out what the upstream issue is before the autoremoval. Also, upstream hasn't seen any activity since 2021... Feel free to forward this bug and/or adopt this package (I don't use it). Cheers, Nicholas signature.asc Description: PGP signature
Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed
I adjusted your patch a bit as it didn't apply cleanly and pushed it to https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/47 to replace the transitional mariadb-client-10.5 I had earlier. Thanks for diving deep in piuparts testing for MariaDB 10.11 and for the patch! Ideally the CI itself had all the install/upgrade scenarios that are relevant. Contributions to the debian/salsa-ci.yml file are also very welcome!
Processed: Re: Bug#1037077: tryton-modules-account-payment-sepa: Non-free xsd schemas
Processing control commands: > forwarded -1 https://foss.heptapod.net/tryton/tryton/-/issues/12304 Bug #1037077 [src:tryton-modules-account-payment-sepa] tryton-modules-account-payment-sepa: Non-free xsd schemas Set Bug forwarded-to-address to 'https://foss.heptapod.net/tryton/tryton/-/issues/12304'. > severity -1 normal Bug #1037077 [src:tryton-modules-account-payment-sepa] tryton-modules-account-payment-sepa: Non-free xsd schemas Severity set to 'normal' from 'serious' -- 1037077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037077: tryton-modules-account-payment-sepa: Non-free xsd schemas
Control: forwarded -1 https://foss.heptapod.net/tryton/tryton/-/issues/12304 Control: severity -1 normal > Source: tryton-modules-account-payment-sepa > Version: 5.0.1-2 > Severity: serious > > The tests/*.xsd files are non-free. They are probably distributed under terms > specified at https://www.iso20022.org/intellectual-property-rights or > https://www.iso20022.org/terms-use > > Modified distribution is not allowed uder these terms. > > Please exclude the mentioned files. Waiting for the feedback of the upstream project as the origin of the files is not clear. -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
Processed: Bug#1036943 marked as pending in dh-python
Processing control commands: > tag -1 pending Bug #1036943 [dh-python] dh-python: please reinstate Breaks+Replaces: python2 (<< 2.7.18-2) Added tag(s) pending. -- 1036943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036943: marked as pending in dh-python
Control: tag -1 pending Hello, Bug #1036943 in dh-python reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/tools/dh-python/-/commit/f5e867022a03df5f76259a89d914650269158a2d Reintroduce Breaks+Replaces on python2 needed to help apt in some upgrade scenarios. (Closes: #1036943) (this message was generated automatically) -- Greetings https://bugs.debian.org/1036943
Bug#1037077: tryton-modules-account-payment-sepa: Non-free xsd schemas
Source: tryton-modules-account-payment-sepa Version: 5.0.1-2 Severity: serious The tests/*.xsd files are non-free. They are probably distributed under terms specified at https://www.iso20022.org/intellectual-property-rights or https://www.iso20022.org/terms-use Modified distribution is not allowed uder these terms. Please exclude the mentioned files.
Processed: Re: Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12
Processing control commands: > severity -1 important Bug #1036799 [sylpheed] sylpheed: unable to send or read email after upgrading to Debian 12 Severity set to 'important' from 'grave' > tags -1 confirmed Bug #1036799 [sylpheed] sylpheed: unable to send or read email after upgrading to Debian 12 Added tag(s) confirmed. > forwarded -1 https://www.sraoss.jp/pipermail/sylpheed/2023-May/007127.html Bug #1036799 [sylpheed] sylpheed: unable to send or read email after upgrading to Debian 12 Set Bug forwarded-to-address to 'https://www.sraoss.jp/pipermail/sylpheed/2023-May/007127.html'. -- 1036799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12
control: severity -1 important control: tags -1 confirmed control: forwarded -1 https://www.sraoss.jp/pipermail/sylpheed/2023-May/007127.html Hi José Luis, On Fri, 26 May 2023 17:46:44 +0200 José Luis González wrote: > Package: sylpheed > Version: 3.8.0~beta1-1 > Severity: grave > > After upgrading to Debian 12 and booting again the computer I am > unable to use sylpheed to neither send email with both accounts I > have set up, nor read new messages, just with the IMAP one in this > case. > > Both accounts are from Gmail. > > The error message I get trying to send with the POP3 is > > Error > > Hubo un error enviando el mensaje: > 501 5.5.2 Cannot Decode response > r11-20020a5d494b00b00300aee6c9cesm5425569wrs.20 - gsmtp > > while with the IMAP one is > > Hubo un error enviando el mensaje: > 501 5.5.2 Cannot Decode response > j13-20020a5d604d00b00306344eaebfsm5456150wrt.28 - gsmtp > > Whereas, trying to open the inbox of the IMAP one, or any other > folder, gets this: > > Error > > No se pudo establecer una conexión con el servidor. > > making it impossible to read or query new mail. Right, but that doesn't deserve a 'grave' severity as only gsmtp users are affected and no data is lost or security hole is introduced. I've adjusted this accordingly. That has been reported on the list that downgrading to 3.7.0 fixes the problem: https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html Can you check if downgrading fixes it? best regards, -- Ricardo Mones http://people.debian.org/~mones «Tempt not a desperate man. -- William Shakespeare, "Romeo and Juliet"»
Bug#1037064: maven-verifier depends on downloading sources at build time
On Fri, 02 Jun 2023 21:40:10 -0700, Steve Langasek wrote: > While this is not a build failure, it does mean building the package has a > dependency on software outside of main, which I believe is a serious policy > violation. The network access during build is a policy violation in itself: 4.9 … For packages in the main archive, required targets must not attempt network access, except, via the loopback interface, to services on the build host that have been started by the build. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1036575: marked as done (groonga-bin: missing Depends: libjs-jquery-flot, libjs-jquery-ui)
Your message dated Sat, 03 Jun 2023 10:50:06 + with message-id and subject line Bug#1036575: fixed in groonga 13.0.0+dfsg-3 has caused the Debian Bug report #1036575, regarding groonga-bin: missing Depends: libjs-jquery-flot, libjs-jquery-ui to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: groonga-bin Version: 13.0.0+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks: 0m16.6s ERROR: FAIL: Broken symlinks: /usr/share/groonga/html/admin/assets/images -> ../../../../javascript/jquery-ui/themes/base/images (groonga-bin) /usr/share/groonga/html/admin/assets/jquery-ui.js -> ../../../../javascript/jquery-ui/jquery-ui.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery-ui.min.css -> ../../../../javascript/jquery-ui/themes/base/jquery-ui.min.css (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.axislabels.js -> ../../../../javascript/jquery-flot/jquery.flot.axislabels.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.browser.js -> ../../../../javascript/jquery-flot/jquery.flot.browser.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.composeImages.js -> ../../../../javascript/jquery-flot/jquery.flot.composeImages.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.drawSeries.js -> ../../../../javascript/jquery-flot/jquery.flot.drawSeries.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.errorbars.js -> ../../../../javascript/jquery-flot/jquery.flot.errorbars.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.fillbetween.js -> ../../../../javascript/jquery-flot/jquery.flot.fillbetween.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.flatdata.js -> ../../../../javascript/jquery-flot/jquery.flot.flatdata.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.hover.js -> ../../../../javascript/jquery-flot/jquery.flot.hover.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.js -> ../../../../javascript/jquery-flot/jquery.flot.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.legend.js -> ../../../../javascript/jquery-flot/jquery.flot.legend.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.logaxis.js -> ../../../../javascript/jquery-flot/jquery.flot.logaxis.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.navigate.js -> ../../../../javascript/jquery-flot/jquery.flot.navigate.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.saturated.js -> ../../../../javascript/jquery-flot/jquery.flot.saturated.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.selection.js -> ../../../../javascript/jquery-flot/jquery.flot.selection.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.stack.js -> ../../../../javascript/jquery-flot/jquery.flot.stack.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.symbol.js -> ../../../../javascript/jquery-flot/jquery.flot.symbol.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.time.js -> ../../../../javascript/jquery-flot/jquery.flot.time.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.touch.js -> ../../../../javascript/jquery-flot/jquery.flot.touch.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.touchNavigate.js -> ../../../../javascript/jquery-flot/jquery.flot.touchNavigate.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.flot.uiConstants.js -> ../../../../javascript/jquery-flot/jquery.flot.uiConstants.js (groonga-bin) /usr/share/groonga/html/admin/assets/jquery.js -> ../../../../javascript/jquery/jquery.js (groonga-bin) This looks to me like some part of the code (not documentation) is missing. cheers, Andreas --- End Message --- --- Begin Message --- Source: groonga Source-Version: 13.0.0+dfsg-3 Done: Kentaro Hayashi We believe that the bug you reported is fixed in the latest version of groonga, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution
Bug#1037068: sysrepo: world-writable /etc/sysrepo/* after upgrade from 1.4.70-4 in bullseye
Package: sysrepo Version: 2.0.53-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package has world-writable configutation files after upgrading from 1.4.70-4 in bullseye to 2.0.53-6 in sid. >From the attached log (scroll to the bottom...): ERROR: BAD PERMISSIONS drwxrwxrwx 4 root root 100 Jun 2 14:28 /etc/sysrepo drwxrwxrwx 3 root root 240 Jun 2 14:28 /etc/sysrepo/data -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-datastores.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-netconf-notifications.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-netconf-with-defaults.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-netconf.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-origin.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-yang-library.startup drwxrwxrwx 2 root root 40 Jun 2 14:28 /etc/sysrepo/data/notif -rw-rw-rw- 1 root root 388 Jun 2 14:28 /etc/sysrepo/data/sysrepo.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/yang.startup -rw-rw-rw- 1 root root 0 Jun 2 14:28 /etc/sysrepo/sr_main_lock drwxrwxrwx 2 root root 180 Jun 2 14:28 /etc/sysrepo/yang cheers, Andreas sysrepo_2.0.53-6+b3.log.gz Description: application/gzip
Bug#1037067: libocct-data-exchange-dev,libocct-foundation-dev: both ship /usr/lib/x86_64-linux-gnu/libTKXDE.so
Package: libocct-data-exchange-dev,libocct-foundation-dev Version: 7.7.1+dfsg1-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../125-libocct-data-exchange-dev_7.7.1+dfsg1-1~exp1_amd64.deb ... Unpacking libocct-data-exchange-dev:amd64 (7.7.1+dfsg1-1~exp1) ... dpkg: error processing archive /tmp/apt-dpkg-install-ENsvnk/125-libocct-data-exchange-dev_7.7.1+dfsg1-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKXDE.so', which is also in package libocct-foundation-dev:amd64 7.7.1+dfsg1-1~exp1 Errors were encountered while processing: /tmp/apt-dpkg-install-ENsvnk/125-libocct-data-exchange-dev_7.7.1+dfsg1-1~exp1_amd64.deb cheers, Andreas libocct-foundation-dev=7.7.1+dfsg1-1~exp1_libocct-data-exchange-dev=7.7.1+dfsg1-1~exp1.log.gz Description: application/gzip
Bug#1035542: libreswan: CVE-2023-30570: Incorrect aggressive mode interaction causes the pluto daemon to crash
Hi Daniel, On Fri, Jun 02, 2023 at 06:59:35PM -0400, Daniel Kahn Gillmor wrote: > Hi Salvatore-- > > On Fri 2023-06-02 21:20:50 +0200, Salvatore Bonaccorso wrote: > > Thanks for having a closer look and for your assessment. Then I > > believe we can have a fix scheduled via respective point releases, I > > do not see an urgency for it requiring a DSA. Initially I was not > > completely sure about it. > > i'm fine with a fix in the point release approach. I've gone ahead and > uploaded 4.11-1 to unstable, and 4.3-1+deb11u4 to bullseye for > proposed-updates (#1037054). And I've uploaded 4.10-1+deb12u1 to bookworm's > proposed-updates too (#1037056). > > I recognize that i missed the window for bookworm, and i'm bummed about > that, but i think this approach should reach users with reasonable speed > (and most users shouldn't have IKEv1 enabled at all on bookworm anyway). > > Please don't hesitate to nudge here if there's more that needs doing. Thank you for hawing worked trough all three updates! Regards, Salvatore
