Bug#887794: New version of MusE

[Nicholas D Steeves]

Hi Tim,

On Sat, Oct 13, 2018 at 06:56:17PM -0400, Tim wrote:
> 
> 
> On 10/13/2018 05:51 PM, Nicholas D Steeves wrote:
> > 
> > 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?
> 
> Yes, confirmed fixed in 3.0.2 source, the two stoppages
>  that I can see listed in 853565 have been fixed:
> 
> /<<PKGBUILDDIR>>/muse/ctrl/ctrlcanvas.cpp:575:9: warning: 'n' may be used
> uninitialized in this function [-Wmaybe-uninitialized]
>          if(i->second->num() == n)
>          ^~
> /<<PKGBUILDDIR>>/muse/ctrl/ctrlcanvas.cpp:525:25: warning: 'mp' may be used
> uninitialized in this function [-Wmaybe-uninitialized]
>      MusECore::MidiPort* mp;
> 
> We now initialize n to zero and mp to NULL in version 3.0.2
> 
> 
> > 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
> 
> No problem, we went all Qt5 quite a while ago, there shouldn't
>  be any trouble with Qt5, nor any Qt4 dependencies.
> 

Thank you for confirming!

> 
> Thank you much for the quick reply.
> Hopefully MusE can move forward now.
> 
> I know the best would be for us to at least try to make a package
>  and propose it so you could look at it. If I get up the nerve
>  to try I will certainly submit one but it might be quite a while.
> I am examining the existing package now.

Sorry I can't help out more at this time, because it looks like I'll
have high to severe work hours until late November, possibly even
later.  If the repository has a pristine-tar branch, and/or a
debian/gbp.conf on the master branch then you'll import the new
version with 'gbp import-orig --uscan' and then 'gbp dch
--new-version=3.0.2-1~'.  Leave the suite as UNRELEASED.  In this case
the tilde is just an extra safety measure to insure the official
3.0.2-1 will evaluate to being > 3.0.2-1~.  For the purposes of
updating a package it's probably alright to use a sid system (without
a chroot) and plain old "dpkg-buildpackage -us -uc", because someone
else will have to sponsor the upload and that person will build the
package in a clean chroot.  If the cleanup script doesn't clean
everything "git clean -xdf" is the fastest way to take care of this.
Assuming your branch is forked from the Debian project and is
fast-forwardable someone could merge your updates, build the package
in a clean chroot, and upload it.  Oh, and "apt-get build-dep" from
the packaging branch will get the build dependencies.

For additional guidance, see #debian-mentors on irc.oftc.net

> PS: If this helps: Some RPM packagers contacted us because the
>  packagers wanted to use -no-undefined linker flag.
> But this also requires our own cmake -DMODULES_BUILD_STATIC flag,
>  be sure to include that flag if -no-undefined is desired.
> With those flags given, there were a lot of errors at the time
>  but they were fixed as of 28.01.2018, thankfully
>  included in release 3.0.2.

Thank you for the tip!

> There are exciting and important changes in MusE,
>  and much more in git master on the way, but we're
>  pretty slow with releases. Due for a new release soon :-)

That's great news! :-) Regarding Debian deadlines: On the devel
mailing list there was a recent announcement to the affect of this:
close release critical bugs now and wrap up your projects, if you
don't think you'll be able to complete them on time then unset
yourself as owner so other people can work on them.  I would guess a
December release would give someone on the multimedia team a full
month to package that new release before the soft freeze.

Please ping me the ~28th Nov if 3.0.2 hasn't been uploaded to Debian
by then, notwithstanding I still might be fully booked at that time.
Sorry I can't provide more certainty wrt to finding the time to help
out.

Cheers,
Nicholas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-multimedia-maintainers/attachments/20181021/8c05b7fa/attachment-0001.sig>