Project

General

Profile

Feature #6424

Port tails-persistence-setup to Gtk3

Added by intrigeri almost 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Persistence
Target version:
Start date:
11/15/2013
Due date:
% Done:

100%

Feature Branch:
t-p-s:feature/jessie,perl5lib:feature/jessie
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:

Description

In the next years, Gtk2 will see less and less maintenance, and more and more breakage. Some initial porting work was done already in the feature/gtk3 branch in the persistence-setup Git repository. It depends on the branch with the same name in the Tails-Perl5lib repository.


Related issues

Blocked by Tails - Feature #6015: Tails based on Wheezy Resolved 07/28/2013

History

#1 Updated by intrigeri over 5 years ago

  • % Done changed from 0 to 10

Merged current master into feature/gtk3, and finished the first part of the porting work: the test suite now entirely passes. Note that it depends on the feature/gtk3 branch of our perl5lib. Now needs to be tested live in a Tails/Wheezy image.

If anyone wants to take it from here, it could be a great way to dive into the persistence-setup code and get up to speed for more involved missions in this area.

#2 Updated by BitingBird over 5 years ago

  • Type of work changed from Code to Test

Intri said the next step is to test, changing type of work accordingly :)

#3 Updated by intrigeri over 5 years ago

  • Type of work changed from Test to Code

BitingBird wrote:

Intri said the next step is to test, changing type of work accordingly :)

I beg to disagree. Sure, the next thing to do is to test, but to do that one needs to build 2 Debian packages from a custom branch, and install it into a custom ISO. I doubt anyone who is not interested into fixing the bugs the tests will detect can do that efficiently. IMHO, the kind of test work that is needed belongs more to a usual programming process (write code, test, go back to writing code) than to the kind of work we usually point our testers at. To sum up, on that one, I'd rather the "Type of work" field indicate the kind of skills needed to do the task.

#4 Updated by intrigeri over 5 years ago

  • Feature Branch changed from feature/gtk3 to t-p-s:feature/gtk3,perl5lib:feature/gtk3

Merged latest master again, fixed more porting issues (both in perl5lib and t-p-s), at a time I didn't feel doing something urgent.

#5 Updated by BitingBird over 5 years ago

  • Status changed from Confirmed to In Progress

#6 Updated by intrigeri about 5 years ago

  • Description updated (diff)

#7 Updated by intrigeri over 4 years ago

  • Assignee set to intrigeri
  • Target version set to Tails_2.0
  • % Done changed from 10 to 20
  • Feature Branch changed from t-p-s:feature/gtk3,perl5lib:feature/gtk3 to t-p-s:feature/jessie,perl5lib:feature/jessie
  • Starter changed from Yes to No

Hopefully completed the porting work in feature/jessie branch in these two repos.

#8 Updated by intrigeri over 4 years ago

  • % Done changed from 20 to 30

Seems to work just fine in Tails/Jessie, except:

  • Text is not wrapped in some of our dialog boxes, resulting in very long lines.

#9 Updated by intrigeri over 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 30 to 100

Resolved the last problem I could see.

Also available in: Atom PDF