Proposed MBF: wxwidgets3.2 transition

2022-09-12 Thread Scott Talbert
Hi, wxWidgets 3.2 (a new API/ABI stable release) has been released a few months ago and is now packaged in unstable as wxwidgets3.2. Upstream has stopped supporting wxWidgets 3.0, so the Debian wx team would like to migrate all wx package users to wxwidgets3.2 for bullseye, with the plan to

Re: transition to usrmerge to start around 2022-09-15 (next Thursday)

2022-09-12 Thread Luca Boccassi
On Mon, 12 Sept 2022 at 07:35, Marc Haber wrote: > > On Sun, 11 Sep 2022 11:08:44 -0400, Marvin Renich > wrote: > >* Ansgar [220910 09:37]: > >> the transition to usrmerge as described in [1] is planned to start > >> around 2022-09-15 (next Thursday). > >[snip] > >> We will send an announcement

Re: Switch default from PulseAudio to PipeWire (and WirePlumber) for audio

2022-09-12 Thread Jeremy Bicha
On Thu, Sep 8, 2022 at 11:59 AM Dylan Aïssi wrote: > I have been asked several times regarding when Debian will switch its default > sound server from PulseAudio to PipeWire without having an official answer. I think it's a good idea to switch the Debian GNOME default sound service to PipeWire no

Re: packages expected to fail on some archs

2022-09-12 Thread Samuel Thibault
Tobias Frost, le lun. 12 sept. 2022 18:36:09 +0200, a ecrit: > On Mon, Sep 12, 2022 at 05:11:46PM +0200, Samuel Thibault wrote: > > Tobias Frost, le lun. 12 sept. 2022 16:08:08 +0200, a ecrit: > > > The problem is that if you want to exclude an arch explicitly, you have to > > > list all archs you

Re: packages expected to fail on some archs

2022-09-12 Thread Tobias Frost
On Mon, Sep 12, 2022 at 05:11:46PM +0200, Samuel Thibault wrote: > Hello, > > Tobias Frost, le lun. 12 sept. 2022 16:08:08 +0200, a ecrit: > > The problem is that if you want to exclude an arch explicitly, you have to > > list all archs you want to build it on. IOW, I'm missing an easy way to say

Re: packages expected to fail on some archs

2022-09-12 Thread Samuel Thibault
Hello, Tobias Frost, le lun. 12 sept. 2022 16:08:08 +0200, a ecrit: > The problem is that if you want to exclude an arch explicitly, you have to > list all archs you want to build it on. IOW, I'm missing an easy way to say > "not on THIS architecture", somthing like "[!armel]" Yes, but see below

Re: packages expected to fail on some archs

2022-09-12 Thread Tobias Frost
On Sun, Sep 11, 2022 at 11:07:13PM +0300, Adrian Bunk wrote: > On Sun, Sep 11, 2022 at 05:08:57PM +0200, Samuel Thibault wrote: > >... > > The issue we see is that some DDs end up setting a hardcoded list in > > the "Architecture" field, rather than just letting builds keep failing > > on these arc

Re: libgeos++-dev intentionally broken

2022-09-12 Thread Lisandro Damián Nicanor Pérez Meyer
Hi, On Mon, 12 Sept 2022 at 09:02, Enrico Zini wrote: > > Hello, > > GEOS upstream[1] explicitly offers a C++ API, with no API stability > across different versions, and a C API, as a stable wrapper to the C++ > API with API and API stability guarantees. > > The Debian libgeos++-dev package has i

Re: libgeos++-dev intentionally broken

2022-09-12 Thread Sebastiaan Couwenberg
On 9/12/22 14:01, Enrico Zini wrote: The Debian libgeos++-dev package has intentionally stopped[2] shipping some include files that are needed to build programs with the C++ API, stating: Upstream removed the .inl files in 3.11.0: https://github.com/libgeos/geos/blob/3.11.0/NEWS.md?plain=1#L2

libgeos++-dev intentionally broken

2022-09-12 Thread Enrico Zini
Hello, GEOS upstream[1] explicitly offers a C++ API, with no API stability across different versions, and a C API, as a stable wrapper to the C++ API with API and API stability guarantees. The Debian libgeos++-dev package has intentionally stopped[2] shipping some include files that are needed to