Bug 231458 - pkg(8) defaults to quarterly, portsnap(8) doesn't
Summary: pkg(8) defaults to quarterly, portsnap(8) doesn't
Status: Closed FIXED
Alias: None
Product: Services
Classification: Unclassified
Component: Portsnap (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Many People
Assignee: Colin Percival
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-18 16:55 UTC by Edward Tomasz Napierala
Modified: 2020-08-11 14:49 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Edward Tomasz Napierala freebsd_committer freebsd_triage 2018-09-18 16:55:18 UTC 
On releases (as opposed to CURRENT), pkg(8) defaults to the quarterly branch.  The portsnap(8), however, doesn't.  This means the user who wants to build a port from source (for whatever reasons) might hit a conflict.  The portsnap(8) should either default to quarterly as well, or it should warn the user about the situation.
Comment 1 Brad Davis freebsd_committer freebsd_triage 2018-09-19 09:53:35 UTC 
Portsnap does not handle branches at all, so cannot help with this.  The user should use svn to checkout a tree.

Is this documented somewhere?
Comment 2 Jack-Benny Persson 2018-11-03 03:34:25 UTC 
I think the best solution would be to implement a way to choose which branch to follow with portsnap (just as with pkg). And then, as Edward pointed out, a warning if portsnap isn't following the same branch as pkg.
Comment 3 Jack-Benny Persson 2018-11-03 03:38:54 UTC 
(In reply to Jack-Benny Persson from comment #2)

Sorry, I missed Brad's comment that Portsnap dosen't handle branches at all...
Comment 4 Jack-Benny Persson 2018-11-03 06:08:17 UTC 
(In reply to Brad Davis from comment #1)

Unfortunately no, see bug #228333
Comment 5 Jochen Neumeister freebsd_committer freebsd_triage 2019-02-15 18:33:38 UTC 
what is the current status?
Does ports-secteam have to be active here?
Comment 6 Jason W. Bacon freebsd_committer freebsd_triage 2020-04-18 00:07:26 UTC 
Portsnap doesn't currently support quarterly branches - you'd have to check one out with svn.

You may be interested in a broader discussion about the issue you've brought up:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245667

https://forums.freebsd.org/threads/find-out-the-quartly-branch-from-which-packages-are-installed.74977/#post-459586

It would be nice if portsnap could be used for quarterly (just the most recent quarter).  It wouldn't do much most of the time since versions are frozen through each quarter, but it could be a nice tool for smoothly transitioning the ports tree into the next quarter along with the pkg repo.
Comment 7 Jochen Neumeister freebsd_committer freebsd_triage 2020-07-23 16:29:07 UTC 
I'll close up here. If there are any problems, please reopen.
Comment 8 Edward Tomasz Napierala freebsd_committer freebsd_triage 2020-07-25 19:03:35 UTC 
But what's the solution then?  Have portsnap repos been switched to following quarterly instead of head?
Comment 9 Jochen Neumeister freebsd_committer freebsd_triage 2020-07-26 08:34:53 UTC 
(In reply to Edward Tomasz Napierala from comment #8)

The PR has now been open for 2 years. 
Antoine (part of portmgr) has passed it on from portmgr to cperciva without comment. He has not commented on it until today. So there seems to be no interest in it.
if you could direct the PR to pkg@FreeBSD.org, which maintains pkg.
Comment 10 Jochen Neumeister freebsd_committer freebsd_triage 2020-07-26 08:36:31 UTC 
Sorry, still too little coffee ... I didn't mean pkg, but portsnap, which is probably maintained by cperciva. But since no comment has been posted here for the last 2 years, there seems to be no interest in it.
Comment 11 Edward Tomasz Napierala freebsd_committer freebsd_triage 2020-08-11 14:49:47 UTC 
Just for the record, a bit of context: portsnap is going away (https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html), so this really is getting overcome by events.