Bug 1523099 - Replace Hamster with gsobczyk fork
Summary: Replace Hamster with gsobczyk fork
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: hamster-time-tracker
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1415781
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-07 08:45 UTC by Ivan Romanov
Modified: 2019-02-03 17:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-03 17:19:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Original Hamster (12.96 KB, image/png)
2017-12-07 08:45 UTC, Ivan Romanov
no flags Details
gsobczyk Hamster (24.33 KB, image/png)
2017-12-07 08:46 UTC, Ivan Romanov
no flags Details

Description Ivan Romanov 2017-12-07 08:45:02 UTC
Created attachment 1364110 [details]
Original Hamster

Current Hamster is not usable in Fedora 26. No Stop/Start buttons, no tray icon. Probably many others bugs. Also project is not maintained as said in README and last commit was in 2016. See repo on github for details: https://github.com/projecthamster/hamster.

I tried to use fork https://github.com/gsobczyk/hamster. Seems it works fine and it live, latest commit was 10 days ago. Can we use this for package in Fedora?

Comment 1 Ivan Romanov 2017-12-07 08:46:13 UTC
Created attachment 1364111 [details]
gsobczyk Hamster

Comment 2 Ankur Sinha (FranciscoD) 2017-12-07 12:56:32 UTC
Hrm, I don't have an opinion on this. What do the other maintainers think? Are we going to replace hamster-time-tracker with the new bits (-cli,-gtk, and so on) in the long term, or will those be separate packages etc.?

Comment 3 Felix Schwarz 2017-12-12 10:51:41 UTC
Not sure if replacing the Fedora package by a fork is the best idea (unless the fork developers and the hamster2 developer are coordinating so that data upgrade etc is possible).

I'd suggest reaching out to both upstreams to check on their compatibility story with regards to each other. Otherwise Fedora might end up in a world of incompatible data+hurt (even though the "hamster2" upgrade left Fedora in a pretty bad state anyway)...

Comment 4 Fedora End Of Life 2018-02-20 15:29:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 5 Raphael Groner 2018-12-14 04:39:13 UTC
Upstream is active, see latest commits to GitHub. No need to use a fork.

Comment 6 Raphael Groner 2018-12-17 07:29:09 UTC
https://github.com/projecthamster/hamster/releases/tag/v2.1.1

Are there any plans to update?

Comment 7 Ankur Sinha (FranciscoD) 2018-12-17 11:28:43 UTC
Not really. As upstream also clearly mentions in the readme, hamster is undergoing a major re-write. I intend to orphan this when I have the time. If anyone would like to take over and maintain this "maintenance release", please apply for co-maintainership.

Comment 8 Raphael Groner 2018-12-17 12:46:49 UTC
Sadly. I remember to have orphaned this package (and other packages) for the same reason.

Comment 9 Ankur Sinha (FranciscoD) 2019-02-03 17:19:51 UTC
I have orphaned this package. Closing. When the re-write is complete, someone who uses it can package it up again.

Comment 10 Raphael Groner 2019-02-03 17:36:42 UTC
See also for python3 migration: https://github.com/projecthamster/hamster/issues/369


Note You need to log in before you can comment on or make changes to this bug.