Project

General

Profile

Feature #12185

Run Dogtail using Python 3

Added by anonym over 1 year ago. Updated 3 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
01/28/2017
Due date:
% Done:

0%

QA Check:
Info Needed
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Currently we install python-dogtail, which uses Python 2 and makes it impossible to deal with objects containing unicode character (e.g. "Save As…" (note the triple dots)).

The Debian packaging repo for dogtail has switched to Python 3 since almost a year back, but there has been no release since then. However, I tried building a package and installing it, and it worked fine vs unicode strings at least.

Part of the "Make test suite survive tech changes" roadmap item.


Related issues

Blocks Tails - Feature #8788: Automatically test the "Tails documentation" link on the Desktop In Progress 01/24/2015
Blocked by Tails - Feature #14585: Investigate Dogtail's long-term viability Resolved 09/02/2017
Blocks Tails - Bug #15953: Make our test suite survive changes in the surrounding environment Confirmed 09/14/2018

History

#1 Updated by intrigeri over 1 year ago

  • Priority changed from Normal to Low

(Indicating that this is not a blocker for 3.0. If it doesn't make it into 3.0, then it should go back to priority Normal.)

#2 Updated by intrigeri over 1 year ago

  • Priority changed from Low to Normal
  • Target version changed from Tails_3.0 to Tails_3.2

I think we'll be plenty busy with other matters during this cycle.

#3 Updated by anonym over 1 year ago

  • Subject changed from Generate Python 3 code for Dogtail to Run Dogtail using Python 3
  • Description updated (diff)

Please see the updated description. With that as background, I guess we might want to consider building our own python3-dogtail from version 0.9.9-1, until we can make Debian release it for stretch backports.

#4 Updated by spriver over 1 year ago

  • Blocks Feature #8788: Automatically test the "Tails documentation" link on the Desktop added

#5 Updated by anonym about 1 year ago

  • Blocks Feature #13239: Core work 2017Q3: Test suite maintenance added

#6 Updated by intrigeri about 1 year ago

Looking at your 3.2 plate, I suggest you postpone this to another major release.

#7 Updated by intrigeri about 1 year ago

  • Target version changed from Tails_3.2 to Tails_3.3

#8 Updated by intrigeri about 1 year ago

  • Blocked by Feature #14585: Investigate Dogtail's long-term viability added

#9 Updated by intrigeri about 1 year ago

Please check #14585 before investing lots more time into dogtail.

#10 Updated by intrigeri 12 months ago

  • Blocks Feature #13240: Core work 2017Q4: Test suite maintenance added

#11 Updated by intrigeri 12 months ago

  • Blocks deleted (Feature #13239: Core work 2017Q3: Test suite maintenance)

#12 Updated by intrigeri 11 months ago

  • Target version changed from Tails_3.3 to Tails_3.5

#13 Updated by intrigeri 10 months ago

  • Target version deleted (Tails_3.5)

#14 Updated by intrigeri 9 months ago

  • Blocks deleted (Feature #13240: Core work 2017Q4: Test suite maintenance)

#15 Updated by u 8 months ago

If this is still needed, I suggest instead to ask Debian packagers to provide such a package. Outsource!

#16 Updated by anonym 8 months ago

  • Assignee changed from anonym to u
  • QA Check set to Info Needed

u wrote:

If this is still needed

It is! The limitations with unicode has already required a couple ugly workarounds.

I suggest instead to ask Debian packagers to provide such a package. Outsource!

Absolutely! Can I outsource this outsourcing to you? :P Correct me if I am wrong, but my current understanding is that your role includes interfacing with Debian for things like this (?).

#17 Updated by u 8 months ago

  • QA Check deleted (Info Needed)

Sure. I'll take care of it.

#18 Updated by u 8 months ago

  • Target version set to Tails_3.6

#19 Updated by bertagaz 6 months ago

  • Target version changed from Tails_3.6 to Tails_3.7

#20 Updated by bertagaz 4 months ago

  • Target version changed from Tails_3.7 to Tails_3.8

#21 Updated by u 4 months ago

@anonym, are you aware that Dogtail is missing a maintainer in Debian? See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777382

This not only means that we cannot ask any Debian maintainer to put out a new version, but we could theoretically commit to updating this package ourselves. As it is not actively developed, this could be a one-timer.

The tracker page currently shows no VCS information: https://tracker.debian.org/pkg/dogtail.

Upstream code seems to be living here nowadays: https://gitlab.com/dogtail/dogtail I could still ask the question there..

#22 Updated by intrigeri 4 months ago

u wrote:

Upstream code seems to be living here nowadays: https://gitlab.com/dogtail/dogtail I could still ask the question there..

I don't think it's worth spending any more time on this before #14585 is done so feel free to reassign to anonym. It's not urgent anyway.

#23 Updated by intrigeri 3 months ago

  • Target version changed from Tails_3.8 to Tails_3.9

#24 Updated by u 18 days ago

  • Assignee changed from u to anonym
  • Target version changed from Tails_3.9 to Tails_3.11

#26 Updated by intrigeri 18 days ago

  • Assignee changed from anonym to intrigeri

#27 Updated by intrigeri 7 days ago

  • Description updated (diff)
  • Target version changed from Tails_3.11 to 2019

#28 Updated by intrigeri 7 days ago

  • Blocks Bug #15953: Make our test suite survive changes in the surrounding environment added

#29 Updated by intrigeri 3 days ago

  • 0.9.9 was uploaded to Debian but 0.9.10 was not.
  • There's still no python3-dogtail in Debian.

#30 Updated by intrigeri 3 days ago

If we want to make this happen, at this point I think we need to start maintaining the package in Debian ourselves. At this point, that's a useful data point for #14585, not an action item.

#31 Updated by intrigeri 3 days ago

  • Assignee changed from intrigeri to u
  • Target version changed from 2019 to Tails_3.10
  • QA Check set to Info Needed

I've reached a conclusion on #14585 and I think we should start contributing to the maintenance of Dogtail in Debian.

First action items would be:

  1. Ensure the RC bug is forwarded upstream and its patch becomes an upstream MR.
  2. Add a python3-dogtail binary package and verify it fixes https://bugs.debian.org/728658. Once we have a WIP package I'm happy to test this in our test suite.
  3. Package upstream 0.9.10.
  4. If needed, clean up and modernize the packaging, but don't aim for perfection here and leave the package orphaned for now (it's unclear whether we'll keep using Dogtail on the long-term).

My questions for today are:

  • Would this fit in your Debian maintenance budget?
  • Any chance this is done in time for the Buster freeze?

Also available in: Atom PDF