On Wed, Nov 19, 2025 at 9:43 AM Alberto Garcia <[email protected]> wrote: > > On Wed, Nov 19, 2025 at 08:48:21AM -0500, Jeremy Bícha wrote: > > > If this bug isn't able to be fixed in Debian yet, could you consider > > uploading event-dance and filetea to Experimental? Then we could > > remove event-dance, filetea, and libsoup2.4 from Unstable, but you > > wouldn't need to go through the source NEW queue when you upload > > event-dance later. > > I think that we'd need to go through NEW anyway with event-dance > because as soon as soup3 support lands we'll have new binary packages.
Yes, I think binary NEW usually gets processed within days, while source NEW is likely to take months currently. > But sure, I can upload event-dance and filetea to experimental in the > meantime, but what happens to soup2 in this case? I think these are our options: 1. Wait for event-dance upstream 2. Upload event-dance (ported to libsoup3) to Unstable without waiting for upstream 3. Ask ftpmasters to remove libsoup2.4 from Unstable even though this will break event-dance and filetea. I know pcre3 was removed from Unstable early this year even though some things in Unstable hadn't been ported away from it. 4. My suggestion is to upload event-dance and filetea to experimental as is (still using libsoup2.4) and then ask ftpmasters to remove event-dance, filetea, and libsoup2.4 from Unstable. To use event-dance or filetea from Experimental, someone would need to install libsoup2.4 from Debian 13. I don't plan to upload libsoup2.4 to Experimental. Thank you, Jeremy Bícha
