Bug#1004144: marked as done (transition: mbedtls)

2022-03-11 Thread Debian Bug Tracking System 
Your message dated Fri, 11 Mar 2022 22:18:08 +0100
with message-id 
and subject line Re: Bug#1004144: transition: mbedtls
has caused the Debian Bug report #1004144,
regarding transition: mbedtls
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.)


-- 
1004144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi, I'm trying to transition the MbedTLS library to the latest supported LTS
version, bumping the version from 2.16 to 2.28. All the libraries received a
SONAME bump, and only some really minor API incompatibilities were introduced.
I tested all the reverse dependencies of the library and all the ones that
built fine before still build fine now. Some of them fail to build, but they
also failed before upgrading MbedTLS; here's the list of currently failing
packages:

bctoolbox, #983985
charybdis, #978782
dolphin-emu, #976530
haxe, unsatisfiable build dependencies
srslte, #993701
julia, segmentation fault during tests (happens also when not using MbedTLS
2.28, maybe it's an issue of my computer)

My sponsor, Wookey, is going to take a look at the failing packages to see if
MbedTLS 2.28 introduces additional build issues for the already failing
packages (e.g. building bctoolbox with gcc-10).

This is the first time I do something like this, I hope I have not messed up
anything :)

Ben file:

title = "mbedtls";
is_affected = .depends ~ "libmbedcrypto3" | .depends ~ "libmbedtls12" |
.depends ~ "libmbedx509-0" | .depends ~ "libmbedcrypto7" | .depends ~
"libmbedtls14" | .depends ~ "libmbedx509-1";
is_good = .depends ~ "libmbedcrypto7" | .depends ~ "libmbedtls14" | .depends ~
"libmbedx509-1";
is_bad = .depends ~ "libmbedcrypto3" | .depends ~ "libmbedtls12" | .depends ~
"libmbedx509-0";


-BEGIN PGP SIGNATURE-

iIoEARYIADIWIQSlw/BqXszDGx3GlQz/yQfijUdG7QUCYeroyxQcYW5kcmVhQHBh
cHBhY29kYS5pdAAKCRD/yQfijUdG7SnlAQDgR6neeL+EPxebJYR1iNYrMwIy4HFD
Xl5FSqY7tWUAFgEAtsZ6h0RE7eRbRrI3LvMSAeBhx+a6hX8jYa4Dcd/AdgY=
=Syq2
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On 2022-01-23 12:53:02 +0100, Sebastian Ramacher wrote:
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-mbedtls.html
> Control: tags -1 confirmed
> 
> On 2022-01-21 18:09:32 +0100, Andrea Pappacoda wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Hi, I'm trying to transition the MbedTLS library to the latest supported LTS
> > version, bumping the version from 2.16 to 2.28. All the libraries received a
> > SONAME bump, and only some really minor API incompatibilities were 
> > introduced.
> > I tested all the reverse dependencies of the library and all the ones that
> > built fine before still build fine now. Some of them fail to build, but they
> > also failed before upgrading MbedTLS; here's the list of currently failing
> > packages:
> > 
> > bctoolbox, #983985
> > charybdis, #978782
> > dolphin-emu, #976530
> > haxe, unsatisfiable build dependencies
> > srslte, #993701
> > julia, segmentation fault during tests (happens also when not using MbedTLS
> > 2.28, maybe it's an issue of my computer)
> > 
> > My sponsor, Wookey, is going to take a look at the failing packages to see 
> > if
> > MbedTLS 2.28 introduces additional build issues for the already failing
> > packages (e.g. building bctoolbox with gcc-10).
> > 
> > This is the first time I do something like this, I hope I have not messed up
> > anything :)
> 
> Please go ahead

The old binaries got removed, so that's done.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#1007098: transition: liquid-dsp

2022-03-11 Thread Sebastian Ramacher 
Control: tags -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-liquid-dsp.html

On 2022-03-11 04:22:54 +0100, Andreas Bombe wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi release team,
> 
> I request a transition slot for a small transition for liquid-dsp. Just
> 2 reverse dependencies, and both build and run fine with the new library
> version. The auto-liquid-dsp tracker looks good.

Please go ahead

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#1007098: transition: liquid-dsp

2022-03-11 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 confirmed
Bug #1007098 [release.debian.org] transition: liquid-dsp
Added tag(s) confirmed.
> forwarded -1 https://release.debian.org/transitions/html/auto-liquid-dsp.html
Bug #1007098 [release.debian.org] transition: liquid-dsp
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-liquid-dsp.html'.

-- 
1007098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1006456: transition: openldap

2022-03-11 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 confirmed
Bug #1006456 [release.debian.org] transition: openldap
Added tag(s) confirmed.

-- 
1006456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1006456: transition: openldap

2022-03-11 Thread Sebastian Ramacher 
Control: tags -1 confirmed

On 2022-02-26 19:50:47 -0800, Ryan Tandy wrote:
> Wine has been fixed. I confirmed a successful build with openldap 2.5.

Please go ahead

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1006814: marked as done (transition: astc-encoder)

2022-03-11 Thread Debian Bug Tracking System 
Your message dated Fri, 11 Mar 2022 22:12:56 +0100
with message-id 
and subject line Re: Bug#1006814: transition: astc-encoder
has caused the Debian Bug report #1006814,
regarding transition: astc-encoder
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.)


-- 
1006814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

I'd like to transition astc-encoder after some backwards-incompatible
changes to a user-visible struct. I verified that filament, the only
reverse dependency, still builds on amd64.

The ben tracker at
https://release.debian.org/transitions/html/auto-astc-encoder.html
is fine.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmIjpgYACgkQ+C8H+466
LVmTaAv/dz08edid89bdSTXYokXlE5KDItHVfzZvj6OQ3G2fBje5yavaeD75ISMK
TnMO5HS5eMoSCrHSjDY7nNyB1tfOg2zjSf0/ZXTIiPtJmREohklv6+qIx7BD8oUL
8uP5fqKkWD8vsfqgZOO17Cn3jH84U0sj/MHQPAbEyhA9OsXNFmKD6ZOzRkYWqDZk
38HA8V4k4F8+W0mk4s1Fl0KyQB5Iraql0ahUGS61M0WOqc0FcLG2xl6IhbpisOs/
MQtcZmb66VuBMXp81Yd1XUPMrblu74MqacgWcvrWWlcAbs3Qme8Bn/sEApc6RzwU
TGCSSN5jg2m4RmMOC3BPx63vJaxe7VSDl7qMYyxMlN4z6ckQP7GEdWEWSdmJp/2b
jJ/1oqDPXVmRhZWujdkpKuXQflQ1jugYntDkz0IHy0Ox97ZEsCHD4Q34aD1LDclP
tzpQGkbRoJPvhikIAKOK4Ja32b5vL5wRTtvbl+btbW9C06cpqkjDd+2DsgiWwj+I
jvcXD96X
=Tpkl
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On 2022-03-06 10:18:31 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2022-03-05 19:03:55 +0100, Timo Röhling wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Dear release team,
> > 
> > I'd like to transition astc-encoder after some backwards-incompatible
> > changes to a user-visible struct. I verified that filament, the only
> > reverse dependency, still builds on amd64.
> > 
> > The ben tracker at
> > https://release.debian.org/transitions/html/auto-astc-encoder.html
> > is fine.
> 
> Please go ahead

That's done.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#1006599: marked as done (transition: capnproto)

2022-03-11 Thread Debian Bug Tracking System 
Your message dated Fri, 11 Mar 2022 22:12:23 +0100
with message-id 
and subject line Re: Bug#1006599: transition: capnproto
has caused the Debian Bug report #1006599,
regarding transition: capnproto
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.)


-- 
1006599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: deb...@tomlee.co tmanc...@debian.org
Severity: normal

Hi,

Requesting a transition for capnproto 0.9.1. It's in experimental and there
is
an auto transition page here:

https://release.debian.org/transitions/html/auto-capnproto.html

clickhouse is the only reverse dependency that FTBFS but it was already
broken
prior to the 0.8.0 transition due to issues unrelated to the capnproto
package:

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

clickhouse was removed from testing in 2021 because of this issue and there
has been no movement since. Since it's not likely to be fixed soon and we're
again receiving requests for new capnproto packaging we'd like to proceed
with the transition.

Let me know if I can provide any further details.

Ben file:

title = "capnproto";
is_affected = .depends ~ "libcapnp-0.8.0" | .depends ~ "libcapnp-0.9.1";
is_good = .depends ~ "libcapnp-0.9.1";
is_bad = .depends ~ "libcapnp-0.8.0";

-- 
*Tom Lee */ http://tomlee.co / @tglee 
--- End Message ---
--- Begin Message ---
On 2022-03-04 20:54:02 +0100, Sebastian Ramacher wrote:
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-capnproto.html
> Control: tags -1 confirmed
> 
> On 2022-02-27 21:07:00 -0800, Tom Lee wrote:
> > Package: release.debian.org
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: deb...@tomlee.co tmanc...@debian.org
> > Severity: normal
> > 
> > Hi,
> > 
> > Requesting a transition for capnproto 0.9.1. It's in experimental and there
> > is
> > an auto transition page here:
> > 
> > https://release.debian.org/transitions/html/auto-capnproto.html
> > 
> > clickhouse is the only reverse dependency that FTBFS but it was already
> > broken
> > prior to the 0.8.0 transition due to issues unrelated to the capnproto
> > package:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996130
> > 
> > clickhouse was removed from testing in 2021 because of this issue and there
> > has been no movement since. Since it's not likely to be fixed soon and we're
> > again receiving requests for new capnproto packaging we'd like to proceed
> > with the transition.
> > 
> > Let me know if I can provide any further details.
> 
> Please go ahead.

capnproto migrated and the old binaries got removed.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#1006905: bullseye-pu: package ostree/2020.8-2+deb11u1

2022-03-11 Thread Simon McVittie 
On Tue, 08 Mar 2022 at 01:04:17 +, Simon McVittie wrote:
> This update isn't finalized yet, but does it look like something of a
> scale that you would be likely to accept in a point release?

I've tested and uploaded the proposed update (no changes except for
d/changelog, updated diff attached), but please let me know if any of
it needs to be reverted.

> all are straightforward backports, either from upstream release 2022.2
> (in unstable, not in testing yet)

The version I'm backporting from is now in testing.

> I will give this some real-world testing via Flatpak on bullseye
> before upload (in particular to confirm that the eCryptFS fix has been
> successful), but so far it has only had automated tests.

I confirm that the eCryptFS issue is indeed fixed by these changes.

Thanks,
smcv
diffstat for ostree-2020.8 ostree-2020.8

 debian/changelog   |   27 
 debian/control |2 
 debian/gbp.conf|2 
 debian/patches/Fall-back-if-copy_file_range-fails-with-EINVAL.patch|   31 +
 debian/patches/Fix-marking-static-delta-commits-as-partial.patch   |   60 ++
 debian/patches/Fix-translation-of-file-URIs-into-paths.patch   |   57 +
 debian/patches/lib-Fix-a-bad-call-to-g_file_get_child.patch|   39 ++
 debian/patches/libotutil-Avoid-infinite-recursion-during-error-unwinding.patch |   36 ++
 debian/patches/series  |5 
 libglnx/glnx-fdio.c|2 
 src/libostree/ostree-repo-checkout.c   |2 
 src/libostree/ostree-repo-pull.c   |7 -
 src/libotutil/ot-variant-builder.c |2 
 13 files changed, 265 insertions(+), 7 deletions(-)

diff -Nru ostree-2020.8/debian/changelog ostree-2020.8/debian/changelog
--- ostree-2020.8/debian/changelog	2020-11-22 13:24:35.0 +
+++ ostree-2020.8/debian/changelog	2022-03-10 11:59:18.0 +
@@ -1,3 +1,30 @@
+ostree (2020.8-2+deb11u1) bullseye; urgency=medium
+
+  * d/gbp.conf, d/control: Branch for Debian 11 updates
+  * Backport various bug fixes from newer libostree releases.
+Each of these fixes an issue that was reported against Flatpak when
+using the libostree from Debian 11, either via bullseye or
+buster-backports.
+- d/p/Fall-back-if-copy_file_range-fails-with-EINVAL.patch:
+  Add patch to fall back if copy_file_range fails with EINVAL.
+  This fixes an incompatibility with eCryptFS, in particular when
+  using Flatpak in an eCryptFS home directory. (Closes: #1004467)
+- d/p/libotutil-Avoid-infinite-recursion-during-error-unwinding.patch:
+  Avoid infinite recursion when recovering from certain errors, in
+  particular the one that was a symptom of #1004467.
+- d/p/Fix-marking-static-delta-commits-as-partial.patch:
+  Mark commits as partial before downloading, to avoid Flatpak and other
+  ostree users getting into a state where a failed download cannot be
+  resumed.
+- d/p/lib-Fix-a-bad-call-to-g_file_get_child.patch:
+  Fix an assertion failure when using a backport or local build of
+  GLib >= 2.71
+- d/p/Fix-translation-of-file-URIs-into-paths.patch:
+  Fix the ability to fetch OSTree content from paths containing
+  non-URI characters (such as backslashes) or non-ASCII
+
+ -- Simon McVittie   Thu, 10 Mar 2022 11:59:18 +
+
 ostree (2020.8-2) unstable; urgency=medium
 
   * d/p/test-pull-summary-sigs-Set-timestamps-to-serve-expected-f.patch:
diff -Nru ostree-2020.8/debian/control ostree-2020.8/debian/control
--- ostree-2020.8/debian/control	2020-11-22 13:24:35.0 +
+++ ostree-2020.8/debian/control	2022-03-10 11:59:18.0 +
@@ -49,7 +49,7 @@
 Rules-Requires-Root: no
 Standards-Version: 4.5.0
 Homepage: https://github.com/ostreedev/ostree/
-Vcs-Git: https://salsa.debian.org/debian/ostree.git
+Vcs-Git: https://salsa.debian.org/debian/ostree.git -b debian/bullseye
 Vcs-Browser: https://salsa.debian.org/debian/ostree
 
 Package: gir1.2-ostree-1.0
diff -Nru ostree-2020.8/debian/gbp.conf ostree-2020.8/debian/gbp.conf
--- ostree-2020.8/debian/gbp.conf	2020-11-22 13:24:35.0 +
+++ ostree-2020.8/debian/gbp.conf	2022-03-10 11:59:18.0 +
@@ -1,7 +1,7 @@
 [DEFAULT]
 pristine-tar = True
 compression = xz
-debian-branch = debian/master
+debian-branch = debian/bullseye
 upstream-branch = upstream/latest
 patch-numbers = False
 upstream-vcs-tag = v%(version)s
diff -Nru ostree-2020.8/debian/patches/Fall-back-if-copy_file_range-fails-with-EINVAL.patch

Bug#1006879: marked as done (RM: playitslowly/1.5.0-1.1)

2022-03-11 Thread Debian Bug Tracking System 
Your message dated Fri, 11 Mar 2022 10:44:25 -0500
with message-id 
and subject line Dropping request
has caused the Debian Bug report #1006879,
regarding RM: playitslowly/1.5.0-1.1
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.)


-- 
1006879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: ti...@debian.org

Hi, I'm requesting the removal of playitslowly package from stable and
oldstable due to an old RC bug as described in #1006017.

A RM for unstable has been requested as well in #1006761.

Thanks,

--
Tiago
--- End Message ---
--- Begin Message ---
Dropping request, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006017#39

Bests,

--
Tiago--- End Message ---

Re: Update of debian-archive-keyring in stretch?

2022-03-11 Thread Anton Gladky 
I have followed the steps described in README.maintainer,
added my key to the team for stretch and imported keys.

It looks like everything works.Testing it.

Regards

Anton

Am Fr., 11. März 2022 um 14:28 Uhr schrieb Utkarsh Gupta
:
>
> Hi Jonathan,
>
> On Mon, Oct 11, 2021 at 6:24 AM Utkarsh Gupta  wrote:
> > On Tue, Oct 5, 2021 at 1:26 PM Jonathan Wiltshire  wrote:
> > > You will need (but may not want) the commit removing jessie's keys as 
> > > well.
> > > Basically all intermediate commits which touch keyrings - a removal is
> > > really a move from the main keyring to the archive keyring, so it will
> > > change the makeup of the keyring and fail the validation.
> > >
> > > If you actually need the jessie keys kept, as I suspect you do, I can
> > > prepare a stretch branch with new signatures on it in a few days.
> >
> > That'd be really helpful, yes. Though I am still unsure what am I missing.
> > When you prep a branch for stretch, please let me know and as I said,
> > that'd be really helpful. Thank you so much!
>
> Friendly ping on this. Any status update on this, please? :)
> Do you think you can take a look at this sooner? Let me/us know.
>
> > > I intend to simplify the whole thing significantly in bookworm; this whole
> > > jetring and gpg validation thing makes for a lot of maintenance pain.
> >
> > Perfect, that'll indeed help a lot. :)
>
>
> - u
>

Re: Update of debian-archive-keyring in stretch?

2022-03-11 Thread Utkarsh Gupta 
Hi Jonathan,

On Mon, Oct 11, 2021 at 6:24 AM Utkarsh Gupta  wrote:
> On Tue, Oct 5, 2021 at 1:26 PM Jonathan Wiltshire  wrote:
> > You will need (but may not want) the commit removing jessie's keys as well.
> > Basically all intermediate commits which touch keyrings - a removal is
> > really a move from the main keyring to the archive keyring, so it will
> > change the makeup of the keyring and fail the validation.
> >
> > If you actually need the jessie keys kept, as I suspect you do, I can
> > prepare a stretch branch with new signatures on it in a few days.
>
> That'd be really helpful, yes. Though I am still unsure what am I missing.
> When you prep a branch for stretch, please let me know and as I said,
> that'd be really helpful. Thank you so much!

Friendly ping on this. Any status update on this, please? :)
Do you think you can take a look at this sooner? Let me/us know.

> > I intend to simplify the whole thing significantly in bookworm; this whole
> > jetring and gpg validation thing makes for a lot of maintenance pain.
>
> Perfect, that'll indeed help a lot. :)


- u

Bug#1006835: marked as done (transition: sndio (NMU))

2022-03-11 Thread Debian Bug Tracking System 
Your message dated Fri, 11 Mar 2022 13:59:26 +0100
with message-id <8bcb7051-4c32-dd0a-77a1-465cc6f09...@debian.org>
and subject line Re: transition: sndio (NMU)
has caused the Debian Bug report #1006835,
regarding transition: sndio (NMU)
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.)


-- 
1006835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal

Hello, I would like to transition sndio from version 1.5.0 to 1.8.1,
bringing some new symbols (didn't touch any old symbol) and pkgconfig
file helping reverse-dependencies (such as vlc) find it.

All the reverse dependencies builds fine, and I would like to also do
libsoundio "transition" together with this one (the only
reverse-dependency is lmms)

11 packages are in the list:
scummvm
cubeb
lmms
openal-soft
ffmpeg
audacious-plugins
baresip
kodi
lebiniou
mpd
vlc

And all build fine (lmms builds fine with old and new libsoundio).

Ben file:

title = "sndio";
is_affected = .depends ~ "libsndio7.0" | .depends ~ "libsndio7.1";
is_good = .depends ~ "libsndio7.1";
is_bad = .depends ~ "libsndio7.0";
--- End Message ---
--- Begin Message ---

On Sun, 6 Mar 2022 13:54:48 +0100 Gianfranco Costamagna 
 wrote:

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal

Hello, I would like to transition sndio from version 1.5.0 to 1.8.1,
bringing some new symbols (didn't touch any old symbol) and pkgconfig
file helping reverse-dependencies (such as vlc) find it.

All the reverse dependencies builds fine, and I would like to also do
libsoundio "transition" together with this one (the only
reverse-dependency is lmms)

11 packages are in the list:
scummvm
cubeb
lmms
openal-soft
ffmpeg
audacious-plugins
baresip
kodi
lebiniou
mpd
vlc

And all build fine (lmms builds fine with old and new libsoundio).

Ben file:

title = "sndio";
is_affected = .depends ~ "libsndio7.0" | .depends ~ "libsndio7.1";
is_good = .depends ~ "libsndio7.1";
is_bad = .depends ~ "libsndio7.0";





closing, we don't change soname anymore.

G.--- End Message ---

Bug#1006867: marked as done (nmu: dovecot-antispam_2.0+20171229-1+b9)

2022-03-11 Thread Debian Bug Tracking System 
Your message dated Fri, 11 Mar 2022 08:59:07 +0100
with message-id 
and subject line Re: Bug#1006867: nmu: dovecot-antispam_2.0+20171229-1+b9
has caused the Debian Bug report #1006867,
regarding nmu: dovecot-antispam_2.0+20171229-1+b9
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.)


-- 
1006867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

dovecot-antispam needs to be rebuild against the latest dovecot ABI.

nmu dovecot-antispam_2.0+20171229-1+b9 . ANY . unstable . -m "rebuild for 
dovecot-abi-2.3.abiv18"
--- End Message ---
--- Begin Message ---
On 2022-03-07 00:00:27 -0500, Noah Meyerhans wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> dovecot-antispam needs to be rebuild against the latest dovecot ABI.
> 
> nmu dovecot-antispam_2.0+20171229-1+b9 . ANY . unstable . -m "rebuild for 
> dovecot-abi-2.3.abiv18"

Scheduled

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---