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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
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 debian-python@lists.debian.org 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 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 debian-python@lists.debian.org mailing list.

From https://hub.displaycal.net/issue/17813/

,----
| Around end of the year-ish is also the latest date I plan to have moved everything to Py3
`----

Christian

It looks like upstream doesn't seem to be making much progress on this.  Do you think that we need to start working on Python 3 support ourselves?

Scott

On 17 avril 2020 11:32, Scott Talbert <swt@techie.net> wrote:

[...]

Duplicate work is a bad idea.

Otherwise upstream is still active in displaycal forums (18/04/2020) :

https://hub.displaycal.net/forums/topic/battery-life/

Christian

It wouldn't be duplicative work.  It could be provided to upstream.

There doesn't appear to be any upstream commits since 2020-01-14...

Scott

Hey, just letting you know upstream is indeed still alive.

As you have noticed, things take longer than expected, and not all is
due to the move to Python3. While I appreciate the offer to help, at the
moment it would make things harder to juggle for me.

The reason there is no commits over at SF is also that I'm going to move
code repos. Too much going on atm.

Thanks Florian for the feedback.

Christian

I've been a happy user of dispcalgui for years. I just rebooted my machine
(Debian testing, uptime > 140 days) and went to recalibrate, only to find
that displaycal had disappeared.

Looking at this thread upstream ( https://hub.displaycal.net/issue/17813/ )
it appears that the ETA for a port to Python3 is somewhere between 1/1/2020
and "when it's done".

As far as I am aware, displaycal is the premier display calibration gui for
linux. It works and works well. How can we help upstream bring it into
alignment with Debian requirements? Is a beta python3 port available for
community contributions/testing/debugging? Will donations help free up
upstream-maintainer's time to finish the port?

In the interim -- are there any workarounds for both generating new monitor
profiles and installing them?  Is calibration straightforward for a Spyder
5 via ArgyllCMS and the command line? A quick survey suggests I have a
bunch of unexpected learning to do.

Thanks!

Charlie

Argyll is scheduled to be removed from Debian https://bugs.debian.org/966416
and displaycal will also removed.

Could you tell us if displaycal will be ready for python 3 one day ?

Christian

Dear submitter,

as the package displaycal has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1012750

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)