Bug#1067660: wireplumber: Wireplumber 0.5.0 breaks asahi-audio 1.x
Hello Andreas, Le mar. 30 avr. 2024 à 17:26, Andreas Henriksson a écrit : > > We now have asahi-audio 2.x in experimental. Please poke us again when > we should upload to unstable (or feel free to NMU asahi-audio to > unstable when you upload wireplumber 0.5.x to unstable). > The release team agreed to go ahead with this transition, so I am going to upload wireplumber in unstable and I will do a nmu for asahi-audio at the same time. Best regards, Dylan
Bug#1067660: wireplumber: Wireplumber 0.5.0 breaks asahi-audio 1.x
Hello Dylan, On Mon, Apr 29, 2024 at 11:53:50AM +0200, Dylan Aïssi wrote: > Hello, > > Le dim. 31 mars 2024 à 15:41, Andreas Henriksson a écrit : > > > > PLEASE NOTIFY US WHEN YOU UPLOAD wireplumber 0.5.x to UNSTABLE, so we > > can do a coordinated transition (uploading asahi-audio 2.x to unstable). > > (You might also want to contact release-team to set up a transition > > tracker, even if this might not be a normal transition where binNMUs are > > useful etc.) > > > > The autogenerated tracker for transition was removed (don't know why). > I asked for a new one (#1070043). The only other package (waybar) > affected by this transition has now a compatible version in unstable. We now have asahi-audio 2.x in experimental. Please poke us again when we should upload to unstable (or feel free to NMU asahi-audio to unstable when you upload wireplumber 0.5.x to unstable). > So, I think except the t64 transition nothing else is blocking, I am > waiting the green light from the release team for next step, and I > will ping here before uploading wireplumber 0.5 in unstable. > > Best regards, > Dylan Regards, Andreas Henriksson
Bug#1067660: wireplumber: Wireplumber 0.5.0 breaks asahi-audio 1.x
Hello, Le dim. 31 mars 2024 à 15:41, Andreas Henriksson a écrit : > > PLEASE NOTIFY US WHEN YOU UPLOAD wireplumber 0.5.x to UNSTABLE, so we > can do a coordinated transition (uploading asahi-audio 2.x to unstable). > (You might also want to contact release-team to set up a transition > tracker, even if this might not be a normal transition where binNMUs are > useful etc.) > The autogenerated tracker for transition was removed (don't know why). I asked for a new one (#1070043). The only other package (waybar) affected by this transition has now a compatible version in unstable. So, I think except the t64 transition nothing else is blocking, I am waiting the green light from the release team for next step, and I will ping here before uploading wireplumber 0.5 in unstable. Best regards, Dylan
Bug#1067660: wireplumber: Wireplumber 0.5.0 breaks asahi-audio 1.x
Control: fixed -1 1.7-2
On Mon, Mar 25, 2024 at 10:13:57AM +0100, Dylan Aïssi wrote:
> Control: reassign -1 asahi-audio
> Control: notfound -1 0.4.17-1
> Control: found -1 1.7-1
why this version? Every asahi-audio version ever
uploaded to the archive is only compatible with
wireplumber << 0.5.0.
> Control: affects -1 wireplumber
>
> Hello,
> Thanks for this bug report, I reassign it to asahi-audio since the versioned
> dependency is on it and not on wireplumber.
[...]
Hmm... wireplumber was the one who changed the configuration language
and thus broke everything using the existing config language. I thus
think it should declare Breaks against everything shipping old config
language files (as well as warn users via debian/NEWS about needing
to manually fix custom config).
FWIW I've just uploaded asahi-audio 1.7-2 with "wireplumber (<< 0.5.0)".
We'll make sure to upload asahi-audio 2.x (with
"wireplumber (>= 0.5.0)") to EXPERIMENTAL as soon as an upstream release
is available.
PLEASE NOTIFY US WHEN YOU UPLOAD wireplumber 0.5.x to UNSTABLE, so we
can do a coordinated transition (uploading asahi-audio 2.x to unstable).
(You might also want to contact release-team to set up a transition
tracker, even if this might not be a normal transition where binNMUs are
useful etc.)
For the future, if you still think it's asahi-audio which should have
strict dependencies on wireplumber - please help figure out which
version we should put in (<< x.y.z) for future breakage. How long does
wireplumber intend to keep compatibility with 0.5.0 config language (or
make other breaking/incompatible changes)?
Regards,
Andreas Henriksson
Bug#1067660: wireplumber: Wireplumber 0.5.0 breaks asahi-audio 1.x
Control: reassign -1 asahi-audio Control: notfound -1 0.4.17-1 Control: found -1 1.7-1 Control: affects -1 wireplumber Hello, Thanks for this bug report, I reassign it to asahi-audio since the versioned dependency is on it and not on wireplumber. Le lun. 25 mars 2024 à 09:45, Thomas Renard a écrit : > > According to the new api in wireplumber asahi-audio 1.x breaks. The asahi > developer tries to fix this upstream in asahi-audio during this week but > because of the > api change asahi-audio 2.x will break with wireplumber <0.5.0. > > So there is/will be a direct dependency: > > wireplumber 0.4.x compatible to asahi-audio 1.x > wireplumber >= 0.5.0 comaptible to asahi-audio 2.x > > Source; fedora-asahi-dev channel on matrix 24.03.2024, @chadmed around 01.24. > https://matrix.to/#/#asahi-devel:fedoraproject.org > > Please consider this I don't plan to upload wireplumber 0.5.0 to unstable soon because it's kind of blocked by waybar which is not yet compatible with it, it's fixed in git upstream but no release and also because of the t64 transition. So, since asahi-audio seems to want to fix this bug this week, we should have a new compatible version of asahi-audio in due course. Best, Dylan
Bug#1067660: wireplumber: Wireplumber 0.5.0 breaks asahi-audio 1.x
Package: wireplumber Version: 0.4.17-1+b1 Severity: normal Dear Maintainer, According to the new api in wireplumber asahi-audio 1.x breaks. The asahi developer tries to fix this upstream in asahi-audio during this week but because of the api change asahi-audio 2.x will break with wireplumber <0.5.0. So there is/will be a direct dependency: wireplumber 0.4.x compatible to asahi-audio 1.x wireplumber >= 0.5.0 comaptible to asahi-audio 2.x Source; fedora-asahi-dev channel on matrix 24.03.2024, @chadmed around 01.24. https://matrix.to/#/#asahi-devel:fedoraproject.org Please consider this -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 6.6.0-asahi-00915-ge3707768193f (SMP w/10 CPU threads) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC 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 wireplumber depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-4 ii dbus-x11 [dbus-session-bus] 1.14.10-4 ii init-system-helpers 1.66 ii libc6 2.37-15 ii libglib2.0-0t64 [libglib2.0-0]2.78.4-3 ii libpipewire-0.3-0 1.0.3-1 ii libwireplumber-0.4-0 0.4.17-1+b1 ii pipewire 1.0.3-1 Versions of packages wireplumber recommends: ii pipewire-pulse 1.0.3-1 Versions of packages wireplumber suggests: ii libspa-0.2-bluetooth 1.0.3-1 pn libspa-0.2-libcamera pn wireplumber-doc -- no debconf information
