Bug 195617 - [patch] deskutils/gcalcli: Update to latest v3.1
Summary: [patch] deskutils/gcalcli: Update to latest v3.1
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Li-Wen Hsu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-03 16:18 UTC by Lawrence Chen
Modified: 2015-02-19 17:32 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (lwhsu)


Attachments
patch to update gcalcli to 3.1 (2.33 KB, patch)
2014-12-03 16:18 UTC, Lawrence Chen
no flags Details | Diff
poudriere testport results (15.17 KB, text/plain)
2014-12-03 16:19 UTC, Lawrence Chen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lawrence Chen 2014-12-03 16:18:34 UTC
Created attachment 150144 [details]
patch to update gcalcli to 3.1

On November 17th, Google turned off its deprecated V2 Calendar API.  When I checked github, the latest tagged release was still 2.4.2, but v3 had been in the works for some time.  And, it had last been touched October 31st.  So, I had initially created a patch to fetch it at that point in time.

Back from holidays, I decided that I should probably test and submit my patch... where I found v3.0 and v3.1 tags (where v3.1's most recent files had times of 'a day ago'.)  So, I updated it....
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2014-12-03 16:18:34 UTC
Auto-assigned to maintainer lwhsu@FreeBSD.org
Comment 2 Lawrence Chen 2014-12-03 16:19:17 UTC
Created attachment 150145 [details]
poudriere testport results
Comment 3 Li-Wen Hsu freebsd_committer freebsd_triage 2014-12-06 00:59:36 UTC
Much thanks for the patch, would you like to be the maintainer of this port?
Comment 4 Lawrence Chen 2015-02-19 17:00:13 UTC
Sorry for delay, but I was in a period where all the problems in keeping systems current w.r.t. FreeBSD life cycle and Ports is making it difficult to justify its continued existence personally and professionally.

Plus not sure what it really means to be a maintainer or why other ports move in directions away from established use.

So, given that I am listed as maintainer of other ports, though it hasn't helped in keeping those ports working/usable.  And, that for the moment I at least have somewhat usable personal FreeBSD systems (except for one system, my workstation at work, that is stuck as FreeBSD 9.2 + gnome2, because I can't rebuild all my ports as needed with upgrade to FreeBSD 9.3....which is also delaying upgrade of work servers from FreeBSD 9.1.)

Though the recent EOL of my nvidia Quadro (FX 1700) graphics card at home, and the problems of ports depending on x11/nvidia-driver...while my needing to use x11/nvidia-driver-340, is starting to be an issue.  At work, we've been stuck with x11/nvidia-driver-304 for a long time at work, so this issue had mostly been ignored/tolerated until now, in keeping old Sun Ultra 20 workstations (which contain nvidia Quadro FX 1400 cards) usable.

Though the the Linuxulator doesn't come close to challenging Linux there, its more about the notion that Unix is antiquated and obsolete.... just as the mainframe had been shoved out a few years ago.

Though it seems to haven returned as the solution to run lots of Linux, but not FreeBSD, VMs....even though I thought I saw a big ad in FreeBSD Journal about Isilon and FreeBSD.

But, that ZFS is a wonderful filesystem that should be used everywhere (except on Linux where it has been unreliable to be accepted for production use.)  ZFS had entered production use at work shortly after Solaris 10 update 6. 

Though we did get a couple Sun Engineers to camp out in our datacenter, due to issues we were having then... though it was more that our 32 or 64 vCPU [T1/T2] servers were impaired by I/O interrupt handling being limited to only one vCPU. They gave us an experimental setting to allow interrupts to spread out across one core -- 4 or 8 vCPUs, though turning ZIL off had greater improvement then (something we haven't done since, possibly due to replacing our HDS 9985 with HDS 9990 V...or that large (> 1TB) filesystem NFS is now left to NAS appliances, our current device is a 7420.)
Comment 5 Li-Wen Hsu freebsd_committer freebsd_triage 2015-02-19 17:31:36 UTC
Thanks for support and using FreeBSD, and sorry that I forgot this ticket.  This port is updated to 3.2 in r379142, and Henrik Hudson <henrik@thelanman.net> kindly offers the maintainership.

BTW, I would personally suggest you try new 10.1 and new pkg system, maybe they will make difference.