Control: block 875049 853565 by -1 Control: severity -1 important Moving thread from pkg-multimedia-maintain...@alioth-lists.debian.net to this bug report (it will be CCed to the mailing list).
Hi Tim, On Sat, Oct 13, 2018 at 04:38:29PM -0400, Tim wrote: > Hello, I am a primary developer of MusE. > We're getting requests for a new deb package. > We released source version 3.0.2 early 2018. At this time no version of Muse will included in Debian 10 (buster) due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853565 Would you please confirm that the GCC-7 failure to build from source is fixed in muse-3.0.2 at bug #853565? Additionally, it would also be nice to have a comment about the status of the QT5 port at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875049 > There is a request to Debian in January to update > to the newer version: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887794 > > I can see is that it is being 'watched': > https://qa.debian.org/cgi-bin/watch?pkg=muse Thank you for reaching out, I can understand how frustrating it must be for the Debian package to not reflect the last year of work. Great timing, by the way! Now is the time to fix these issues for the next Debian release. :-) > Although I was an experienced .spec file and RPM maker > years ago, I know absolutely nothing about making > Debian packages. Getting up to speed with Debian packaging requires reading more than for RPMs, (eg: Debian Policy, plus other resources like New Maintainers Guide or Debian Packaging Tutorial) and I'd be happy to furnish links to this material. That said, there's no need to learn how to build a package from scratch when one already exists. Options: 1. Wait for someone to fix the package, or 2. Set up a Debian development environment and a) Fork https://salsa.debian.org/multimedia-team/muse and submit your changes as a merge request, or b) Join the Debian Multimedia Team. > But I am highly active in MusE's development. > I am usually available for quick response. > > We'd like to see a new deb package for users. > Anything you need us to do - questions, fixes, > you name it, just ask! I've bumped the priority of this new version bug and blocked two others, because I think everyone will agree that this is the best way forward. Unfortunately I am swamped with work until sometime in early November. I hope that someone else can work on this asap, just in case any issues emerge, because it sounds like you're on call to be able to help out :-) Cheers! Nicholas
signature.asc
Description: PGP signature