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
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
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
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
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
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
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:
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
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
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
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:
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
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
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
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
15 matches
Mail list logo
