On 12/22/20 3:47 PM, Thorsten Glaser wrote: > Hi Matthias, > >> this is an ITP which didn't see any progress for the past eight months. > > yes, sorry about that… I found some issues with it back then, > but don’t remember precisely which ones now. Could’ve been > network, not code-related. > > Ah: #686777 blocks removal of the embedded libopus in favour > of the system-provided one. This was something I considered > a blocker for getting this into testing/next-stable. Looking > at the currently packaged opus though it’s the same upstream > version with no patches, so, identical code. > > Fix blocked by [7]686777: libopus-dev: libopus misses opus-custom modes > > Outlook: I have an experimental package with embedded libopus, but it > needs more fixes especially upstream before I consider it suitable > for Debian > > This is what the ITP says… > >> Do you still plan to get this included for bullseye? If not, I'll try >> to get packages into the archive in time for bullseye. > > If you have interest and time, I’d agree to hand it over.
so this bug discussion started in 2013, and stopped in 2016. Do you really think that this will pick up again? > git clone https://evolvis.org/anonscm/git/alioth/jamulus.git > to retrieve my last WIP state. The package was working last > time I tried, but it needs updating to latest upstream, of > course. I was just taking the upstream packaging, also providing a -headless package for the server. What's wrong with this approach? > Otherwise I’ll jump in once the opus issue gets fixed, or > perhaps upload to sid with an RC bug to prevent testing > migration. that last option isn't suitable for "in time for bullseye". Matthias
