Bug 200314 - sysutils/linux-crashplan: update to 4.2.0
Summary: sysutils/linux-crashplan: update to 4.2.0
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: William Grzybowski
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-19 03:06 UTC by Nuno Subtil
Modified: 2015-08-01 17:00 UTC (History)
3 users (show)

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


Attachments
Patch sysutils/linux-crashplan to 4.2.0 (3.77 KB, text/plain)
2015-05-19 03:06 UTC, Nuno Subtil
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nuno Subtil 2015-05-19 03:06:19 UTC
Created attachment 156920 [details]
Patch sysutils/linux-crashplan to 4.2.0

Updates sysutils/linux-crashplan to version 4.2.0 (latest upstream version)
Comment 1 db5331 2015-05-21 06:17:59 UTC
Comment on attachment 156920 [details]
Patch sysutils/linux-crashplan to 4.2.0

PCs with crashplan clients have auto-updated to v4.2 and can lon longer connect to servers running this port until the port is updated. Thus importance is understated - affects all users.
Comment 2 Nuno Subtil 2015-05-22 16:57:51 UTC
Upgrading importance based on db5331's comments.
Comment 3 William Grzybowski freebsd_committer freebsd_triage 2015-05-22 17:00:30 UTC
I wont have time to commit this for the next two weeks, any committer is free to take it.
Comment 4 darrendavid 2015-07-09 20:44:30 UTC
Is this patch still on the roadmap? Just curious.

Thanks in advance.
Comment 5 William Grzybowski freebsd_committer freebsd_triage 2015-07-09 20:50:46 UTC
Yes, I'll get it committed next week.
Comment 6 Nuno Subtil 2015-07-10 04:03:07 UTC
Just FYI, this is now out of date. Crashplan 4.3.0 is available.

I haven't updated the port yet since these patches have been sitting here for a long time.
Comment 7 William Grzybowski freebsd_committer freebsd_triage 2015-07-10 12:25:13 UTC
Patches are always welcome.
Comment 8 Nuno Subtil 2015-07-10 20:37:40 UTC
I'm sure that's the intent, but there's no incentive for me to do so if patches take so long to be accepted that they're no longer relevant by the time they get committed.

What was the hold-up in getting this submitted? Is it just lack of time? I wouldn't mind taking over this port if you think that's appropriate, it seems I've done the last few updates anyway.

I'll have to update this to 4.3.0 this weekend. At this point it's probably best not to submit the 4.2.0 patch anymore, since it'll just cause unnecessary churn.
Comment 9 William Grzybowski freebsd_committer freebsd_triage 2015-07-10 20:43:40 UTC
If thats the case submit the patch and I will change the maintainership to you.
Comment 10 Nuno Subtil 2015-08-01 17:00:24 UTC
There was a snag updating to 4.3.0 due to protocol changes that require client-side configuration changes. This has now been sorted out by the vendor.

I filed bug 202027 with the 4.3.0 patch. Closing this one.