Bug#850527: marked as done (unblock: frescobaldi/3.0.0~git20161001.0.eec60717+ds1-2)
Your message dated Wed, 18 Jan 2017 00:00:40 +0100
with message-id <7a7e563b-3f18-fcad-ec38-d782f7b988b7@debian.org>
and subject line Re: Bug#850527: unblock: frescobaldi/3.0.0~git20161001.0.eec60717+ds1-2
has caused the Debian Bug report #850527,
regarding unblock: frescobaldi/3.0.0~git20161001.0.eec60717+ds1-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
850527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850527
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Please unblock package frescobaldi.
Frescobaldi, which has been released with Debian since squeeze,
was removed from testing due to Qt 4's WebKit removal.
It took the upstream authors some time to migrate the old
Frescobaldi 2.x to Python 3 and Qt 5, now called Frescobaldi 3.
Due to my inexperience, I had assumed that my 2016-12-17 upload
of Frescobaldi 3.0.0 prerelease would safely migrate to testing.
It was not until 12 days later when I realize that the migration
was blocked due to LilyPond, which in turn was blocked because
guile-1.8 was removed from stretch, and upstream has experienced
problems migrating to with guile-2.0.
Once again, due to my ignorance, I did not know that I could have
requested a shortening of the 10-day hold to let the 2016-12-29 upload
of Frescobaldi, which only "Recommends: lilypond", to enter testing
before 2017-01-05.
I hope it is not too late, but it would really be wonderful if
Frescobaldi could be let in Debian 9 stretch especially since it really
is a wonderful software for typesetting sheet music.
Here are the two recent changelog entries for your reference:
===========================================================================
frescobaldi (3.0.0~git20161001.0.eec60717+ds1-2) unstable; urgency=medium
* Change "Depends: lilypond" to "Recommends: lilypond" since LilyPond
is not absolutely necessary for Frescobaldi to run, but moreover,
to get Frescobaldi into Debian "stretch" (testing), i.e. the upcoming
Debian 9.0 stable release, in case lilypond does not make it into
"stretch". See http://bugs.debian.org/746005 for details.
-- Anthony Fok <foka@debian.org> Thu, 29 Dec 2016 13:52:18 -0700
frescobaldi (3.0.0~git20161001.0.eec60717+ds1-1) unstable; urgency=medium
* New upstream snapshot of the future Frescobaldi 3.0.0 release
which is now fully migrated to Python 3 and Qt 5.
Incidentally, this allows Frescobaldi to enter Debian 9 (stretch)
where Qt 4's WebKit has been removed. (Closes: #784610)
-- Anthony Fok <foka@debian.org> Sat, 17 Dec 2016 06:55:19 -0700
===========================================================================
Thank you for your kind consideration!
Cheers,
Anthony
unblock frescobaldi/3.0.0~git20161001.0.eec60717+ds1-2
- -- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAlhw7csACgkQ6iUAtBLF
ms/9jg/9HZX37QUcl4RziVoHxtZOI9MUJxQl1gSsxDDuCj+ECv/nf39ig1DcIwZM
xA9+fXCPHSPKo/QUWTmhCSsmIqdG5c4xX5XdbL9+QD+D989V3UqFbcC/yt22qVho
lRukNPt4B+tvUPERzF3OhlnI9moIjcN9OymH2cD5A6f9V9wN0xmmcPUnHiAm4dIL
rSNlNAdA9nbZfefOdTvFVzzhoiSPlZJ0s+SmPBSZ7Ycf1FIGssQL2aiTpTHzfQp9
WI+wkC6VJsbopq1D7zh2sa+3x5EZiRD9B3w3UzqQCpxkfiq4WNQRHA/K31hI/q7J
RJNefrUL+kcn6bsHUYk5R8JxM97D0RC6h+oHIvWmS+Bj6Hw6mZeEhECdByJJVA7s
C/t7AODPZscBy+xgKbvnvZtBWbtjhF7mPa3yLeUvXG4TQS9s9NNfTZnYE2jgQCtY
oPtEGLIe8XsPJIPnqg7k5heQq26ptnnzf6ivWgO/l5W90Wgx6+3BhTBHUBpDxaBI
mUUzpMt0U8FH+Tjax+/BdGC4UQw7c9fA4hzRmA1valIpPVw6xq9JhRZnM266xS61
9tK+zlLP964xZpcnXCQTD9kvzS0vVFgkCUVnWudQE+/61IZyDqft+bDrMfMIdcFf
gEghfcnEZZbrXn1l9lxol0gZUKRP1ZP7psjrPsORpppzqXhPXOM=
=ikWz
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 07/01/17 14:32, Anthony Fok wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
>
> Please unblock package frescobaldi.
>
> Frescobaldi, which has been released with Debian since squeeze,
> was removed from testing due to Qt 4's WebKit removal.
> It took the upstream authors some time to migrate the old
> Frescobaldi 2.x to Python 3 and Qt 5, now called Frescobaldi 3.
>
> Due to my inexperience, I had assumed that my 2016-12-17 upload
> of Frescobaldi 3.0.0 prerelease would safely migrate to testing.
> It was not until 12 days later when I realize that the migration
> was blocked due to LilyPond, which in turn was blocked because
> guile-1.8 was removed from stretch, and upstream has experienced
> problems migrating to with guile-2.0.
>
> Once again, due to my ignorance, I did not know that I could have
> requested a shortening of the 10-day hold to let the 2016-12-29 upload
> of Frescobaldi, which only "Recommends: lilypond", to enter testing
> before 2017-01-05.
>
> I hope it is not too late, but it would really be wonderful if
> Frescobaldi could be let in Debian 9 stretch especially since it really
> is a wonderful software for typesetting sheet music.
>
> Here are the two recent changelog entries for your reference:
>
> ===========================================================================
>
> frescobaldi (3.0.0~git20161001.0.eec60717+ds1-2) unstable; urgency=medium
>
> * Change "Depends: lilypond" to "Recommends: lilypond" since LilyPond
> is not absolutely necessary for Frescobaldi to run, but moreover,
> to get Frescobaldi into Debian "stretch" (testing), i.e. the upcoming
> Debian 9.0 stable release, in case lilypond does not make it into
> "stretch". See http://bugs.debian.org/746005 for details.
>
> -- Anthony Fok <foka@debian.org> Thu, 29 Dec 2016 13:52:18 -0700
>
> frescobaldi (3.0.0~git20161001.0.eec60717+ds1-1) unstable; urgency=medium
>
> * New upstream snapshot of the future Frescobaldi 3.0.0 release
> which is now fully migrated to Python 3 and Qt 5.
> Incidentally, this allows Frescobaldi to enter Debian 9 (stretch)
> where Qt 4's WebKit has been removed. (Closes: #784610)
>
> -- Anthony Fok <foka@debian.org> Sat, 17 Dec 2016 06:55:19 -0700
>
> ===========================================================================
>
> Thank you for your kind consideration!
>
> Cheers,
> Anthony
>
> unblock frescobaldi/3.0.0~git20161001.0.eec60717+ds1-2
Unblocked, given I kinda feel responsible that we're releasing without lilypond
(but don't tell the angry users!).
Emilio
--- End Message ---
Reply to: