Your message dated Mon, 1 Feb 2021 09:55:18 -0700
with message-id <[email protected]>
and subject line Bug#936946: fixed in lilypond 2.22.0-1
has caused the Debian Bug report #936946,
regarding lilypond: Python2 removal in sid/bullseye
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 [email protected]
immediately.)
--
936946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936946
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:lilypond
Version: 2.19.81+really-2.18.2-13
Severity: normal
Tags: sid bullseye
User: [email protected]
Usertags: py2removal
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests. Please stop using Python2, and fix this issue
by one of the following actions.
- Convert your Package to Python3. This is the preferred option. In
case you are providing a Python module foo, please consider dropping
the python-foo package, and only build a python3-foo package. Please
don't drop Python2 modules, which still have reverse dependencies,
just document them.
This is the preferred option.
- If the package is dead upstream, cannot be converted or maintained
in Debian, it should be removed from the distribution. If the
package still has reverse dependencies, raise the severity to
"serious" and document the reverse dependencies with the BTS affects
command. If the package has no reverse dependencies, confirm that
the package can be removed, reassign this issue to ftp.debian.org,
make sure that the bug priority is set to normal and retitle the
issue to "RM: PKG -- removal triggered by the Python2 removal".
- If the package has still many users (popcon >= 300), or is needed to
build another package which cannot be removed, document that by
adding the "py2keep" user tag (not replacing the py2remove tag),
using the [email protected] user. Also any
dependencies on an unversioned python package (python, python-dev)
must not be used, same with the python shebang. These have to be
replaced by python2/python2.7 dependencies and shebang.
This is the least preferred option.
If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like
affects <bug number of blocking py2removal bug> + src:lilypond
If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).
If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the [email protected] mailing list.
--- End Message ---
--- Begin Message ---
Source: lilypond
Source-Version: 2.22.0-1
Done: Anthony Fok <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lilypond, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anthony Fok <[email protected]> (supplier of updated lilypond package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 14 Jan 2021 02:53:46 -0700
Source: lilypond
Architecture: source
Version: 2.22.0-1
Distribution: unstable
Urgency: medium
Maintainer: Anthony Fok <[email protected]>
Changed-By: Anthony Fok <[email protected]>
Closes: 746005 852871 951801 979839
Changes:
lilypond (2.22.0-1) unstable; urgency=medium
.
* New upstream version 2.22.0 (Closes: #979839, #951801)
* Remove embedded guile-1.8 and migrate to system guile-2.2
(Closes: #746005, #852871)
* debian/gbp.conf: Remove guile18 component
* debian/{control,rules}: Migrate from python2 to python3
* debian/rules:
- Run "make doc" with "-j" option in addition to CPU_COUNT
as suggested in INSTALL.txt for even faster build
- Remove "nuke the parser files" workaround
as lily/out/parser.* no longer exist in upstream source
- Remove empty override_dh_auto_test-arch
as the tests no longer fail without built documentation
- Remove override_dh_auto_test-indep as the added "make test-baseline"
is not suited for automated Debian builds
- Try to "git restore configure" in override_dh_auto_clean
* debian/control:
- lilypond-doc: Add Replaces: lilypond-doc-html (<< 2.21.82-1~)
to avoid upgrade error due to web files reorganization
- Build-depend imagemagick-6.q16 instead of imagemagick.
"imagemagick" became a dummy package in Debian 9 "stretch",
and the aspcud resolver used by experimental buildd would install
graphicsmagick-imagemagick-compat (which Provides: imagemagick)
which is not that compatible after all and caused lilypond to FTBFS
- Remove Authors paragraph from package description
as the development team is much larger than before
- Bump Standards-Version to 4.5.1 (no change)
* debian/lilypond.docs: Rename README.txt to README.md as per upstream
* Adjust documentation install file lists for LilyPond 2.21/2.22:
- debian/doc_languages.txt: Add PDF package for Portuguese
- debian/update_doc_packages: Adjust install file lists for new version
- debian/lilypond-doc.install: Remove the no-longer-existing
usr/share/doc/lilypond/html/Documentation/*.txt entry
- Run "debian/rules update-doc-packages"
- Add debian/not-installed to avoid dh_missing errors with debhelper 13
* debian/patches: Delete obsolete patches and disable others for now
* debian/remove_w3c_callback: Recognize https too, to fix Lintian
privacy-breach-w3c-valid-html errors
* Adjust debian/lilypond-doc.install and debian/rules
so that the PNG files stay with lilypond-doc package
* debian/README.Debian: Minor editing
* Cherry-pick upstream fixes for potential crashes with Guile 2.2
- 0001-Protect-against-GC-when-constructing-a-System.patch
- 0002-System-Initialize-all-member-variables.patch
Checksums-Sha1:
cf8313d328e6bb7c99584ab786a5847b2856a4b0 4081 lilypond_2.22.0-1.dsc
cc27af8efa977e632932d2633e665381fe24f44e 49320 lilypond_2.22.0-1.debian.tar.xz
61ecd1f6bbbb7c6504c11856a6dcf140b384ac17 13942
lilypond_2.22.0-1_source.buildinfo
Checksums-Sha256:
2be2e6c7f27807368a3230a2d0c912429cff7cf894366c8028361450d951dd92 4081
lilypond_2.22.0-1.dsc
d3990d84eb50fb2261a807d91687a43bcf4c8dbaa471b95a968dbeb84913f215 49320
lilypond_2.22.0-1.debian.tar.xz
0071df91c6b9320d822a0349f10310831f2ad2e6fb5987a60c0be806ab714d5f 13942
lilypond_2.22.0-1_source.buildinfo
Files:
7aea8a028c6deddd798dac49088fd75e 4081 tex optional lilypond_2.22.0-1.dsc
13a87a0d824778503cb5f711394c4f55 49320 tex optional
lilypond_2.22.0-1.debian.tar.xz
d2abfe5ddf3d9ba51a0ce85282f9e858 13942 tex optional
lilypond_2.22.0-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmAAFQUQHGZva2FAZGVi
aWFuLm9yZwAKCRDqJQC0EsWaz8nyEACdwYlm2YjYtmGr166sb+iWVwBdTDzXs7nm
sR3vct0DEKTW+lqoBYIJGfZJe9UIw9HoknBC85gztFIrntwccoON/0ipW4DMeV+Z
68/zlPZ15htDguEC0WNkGVmBy43d7JgfKYlVHky35ZZM0fUKjKuCJ76MmbR5WvwU
hyzeO3/6aiOKiQXhM193aa9ap3NK5xoEyAXtMvOiz/cAp8ZXmmjifBWLciRZVi2r
uPhGhUtvMFAhxosA0xBQpoGzfrW87r5RSqerO/7PTwyGVv8e3ljnnmLpr418joBB
gGRl7m0+BRHsjkNcTJRiNaRwo6rsg9dYuljr6S/zu4tEfud4mv10LL3dU6EvxOBl
ALUvUwIbG69bt1zjHTOo1jYY7SaGJetDFcDXwvRnM9P+QKHovFp7GQjRl8tRaIuW
M62FDzYCCap0VSIUsLEvB5aEy78e2vyWEr5oXfqyxviVJwr7sRFaOBKFYBM7vMVz
Iy58SmGuiE7CMLG87s02lrFRVLDEAO/ewJju5hPqEc/Asj0cU7MeeE/KlVWjnTcC
FZ1R2V6r8yFoLdXyGw4NVdg7HbRd+SXU6dLBhwI+Y1LR8NsK6BDpG7BAgoaURC37
9PTK+AEaR18HeRcAV2AlQ+TmR+AWeTmoTojgy8h74wDUa2g1BDZukkn9BMl8GUt0
JPo6SjA8OQ==
=Egci
-----END PGP SIGNATURE-----
--- End Message ---
