Re: OT Re: [gentoo-dev] Re: [gentoo-project] [RFC] Splitting developer-oriented and expert user mailing lists
On Mon, Dec 4, 2017 at 3:39 PM, Kristian Fiskerstrand wrote: > On 12/04/2017 10:36 PM, William L. Thomson Jr. wrote: >> Sorry last one, directed to Alec, but all should read. > > I hope you really mean that, we've all heard you complaining about this > too many times already. > Inasmuch as a random person is likely to care, glancing at the messages shows wltjr is the more convincing of the parties involved. Having actually wasted time trying to figure out what is going on there is no mention of what ever happened from Gentoo that indicates anything improper took place. Not So Respectfully, R0b0t1
Re: [gentoo-dev] last rites: app-office/hamster-time-tracker
On Thu, Dec 07, 2017 at 09:20:43AM +0100, Geaaru wrote: Hi, I'm not sure that is correct to reply to this thread, sorry if not. I currently use hamster and yes master tree is unmaintained but scenario is difficult for this package. From old tree are been created different fork: * one that split module in different modules (hamster-lib, hamster-gtk, hamster-dbus,etc) * one that rebuild module on ruby * if I remember correctly one that continue python implementation But, it isn't so clear at least for me, what is the best fork or stable (I currently use old implememtation). So, I think that could be a choice try to identify a more stable fork and move ebuild to this new implementation (maybe with a rename of the package) and move ebuild to proxy-maintainer group. I will try to investigate on it in the christmas holidays and see if I can take care of ebuild maintenance. Hi Geaaru, yes, you raise good points here and I found what's going on upstream pretty confusing too :) I really appreciate you wanting to investigate this further. We can help you or work with you to create a new package in case you need it. Thanks, Nick My cent Thanks G. On Dec 6, 2017 11:42 PM, "Nicolas Bock" wrote: # Nicolas Bock (6 Dec 2017) # Development has ceased, the last commit to the upstream repository was # on 16 July 2016 with a note stating that its status is unmaintained [1]. # See also Bug 640034. # # [1] https://github.com/projecthamster/hamster/commit/c3e5fb761c8 8fdecfd1566cac8b6836228a27cce -- Nicolas Bock -- Nicolas Bock signature.asc Description: PGP signature
Re: OT Re: [gentoo-dev] Re: [gentoo-project] [RFC] Splitting developer-oriented and expert user mailing lists
On Mon, 4 Dec 2017 22:39:04 +0100 Kristian Fiskerstrand wrote: > On 12/04/2017 10:36 PM, William L. Thomson Jr. wrote: > > Sorry last one, directed to Alec, but all should read. > > I hope you really mean that, we've all heard you complaining about > this too many times already. The day everyone wanted has come, after this message. I will unsubscribe not to return. You all won in 2008, and again in 2017. Though this time I will not be back. I tried more than most anyone else would for a very long time. Gentoo wins I lose, I am fine with that. Please do not contact me off list in IRC or at all. I am done with the Gentoo community! Thank you and have a nice day! -- William L. Thomson Jr. pgp24Zi7cM0nL.pgp Description: OpenPGP digital signature
[gentoo-dev] Last rites: net-ftp/oneclickftp
# Michael Palimaka (07 Dec 2017) # Dead upstream. Requires dead Qt4. # Masked for removal in 30 days. Bug #640138. net-ftp/oneclickftp
Re: [gentoo-dev] last rites: app-office/hamster-time-tracker
Dear Geaaru, > I will try to investigate on it in the christmas holidays and see if I can > take care of ebuild maintenance. To me it looks like a completely new ebuild is required in that case. Nice to hear that you want to proxy maintain it, you will find everything on our overhauled wiki site https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers Best, Jonas signature.asc Description: OpenPGP digital signature
[gentoo-dev] Last rites: dev-vcs/qct
# Michael Palimaka (07 Dec 2017) # Dead upstream. Requires dead Qt4. # Masked for removal in 30 days. Bug #640138. dev-vcs/qct
Re: [gentoo-dev] last rites: app-office/hamster-time-tracker
Hi, I'm not sure that is correct to reply to this thread, sorry if not. I currently use hamster and yes master tree is unmaintained but scenario is difficult for this package. From old tree are been created different fork: * one that split module in different modules (hamster-lib, hamster-gtk, hamster-dbus,etc) * one that rebuild module on ruby * if I remember correctly one that continue python implementation But, it isn't so clear at least for me, what is the best fork or stable (I currently use old implememtation). So, I think that could be a choice try to identify a more stable fork and move ebuild to this new implementation (maybe with a rename of the package) and move ebuild to proxy-maintainer group. I will try to investigate on it in the christmas holidays and see if I can take care of ebuild maintenance. My cent Thanks G. On Dec 6, 2017 11:42 PM, "Nicolas Bock" wrote: > # Nicolas Bock (6 Dec 2017) > # Development has ceased, the last commit to the upstream repository was > # on 16 July 2016 with a note stating that its status is unmaintained [1]. > # See also Bug 640034. > # > # [1] https://github.com/projecthamster/hamster/commit/c3e5fb761c8 > 8fdecfd1566cac8b6836228a27cce > > -- > Nicolas Bock >
