Re: [solved]: to move csup 90 to subversion 91rc
Darrel writes: > Also, on my amd64 kernel I had to remove 'device atapicam'. > > The failed kernel build might be a bug, perhaps I should file a > report. As far as I know, this is completely unrelated to subversion/c(v)sup. Please check for other issues. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
On Mon, 3 Sep 2012, Darrel wrote: Next, I will decide whether to keep /usr/ports with portsnap or move ports to svn as well. I just did this (ports and docs) and - modulo an error on my part - it has been remarkably painless. (Make sure you eradicate all vesitges of c(v)sup activity. Hello Robert, Other than my csup-file, I found these: /home/var.db/sup/src-all/checkouts.cvs:RELENG_9 /home/var.db/sup/src-all/checkouts.cvs:RELENG_9_0 /.snap /home/.snap /home/var.db/portsnap /home/var.db/portsnap/* /tmp/.snap /usr/.snap /var/.snap Also, on my amd64 kernel I had to remove 'device atapicam'. The failed kernel build might be a bug, perhaps I should file a report. Thank you, Darrel I found these files as well: /var/db/portsnap/ /var/db/sup/ Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Next, I will decide whether to keep /usr/ports with portsnap or move ports to svn as well. I just did this (ports and docs) and - modulo an error on my part - it has been remarkably painless. (Make sure you eradicate all vesitges of c(v)sup activity. Hello Robert, Other than my csup-file, I found these: /home/var.db/sup/src-all/checkouts.cvs:RELENG_9 /home/var.db/sup/src-all/checkouts.cvs:RELENG_9_0 /.snap /home/.snap /home/var.db/portsnap /home/var.db/portsnap/* /tmp/.snap /usr/.snap /var/.snap Also, on my amd64 kernel I had to remove 'device atapicam'. The failed kernel build might be a bug, perhaps I should file a report. Thank you, Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Darrel writes: > Next, I will decide whether to keep /usr/ports with portsnap or > move ports to svn as well. I just did this (ports and docs) and - modulo an error on my part - it has been remarkably painless. (Make sure you eradicate all vesitges of c(v)sup activity.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Is anyone working on documenting this for the "cutting edge" section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). If you do decide to write a new section, I could possibly offer help on "dumbing it down". :) At least with the English version. http://www.freebsd.org/cgi/query-pr.cgi?pr=171292 I don't think "dumbing it down" is an issue. What I may have left out that beginners wouldn't think of... more of a concern. I apologize- that comment was intended to be taken with a grain of salt. As I am asking just now changing from csup to svn, it seems like I might have the insight of a beginner in this instance. - considering my file server: It appears that buildkernel is going well. Next, I will decide whether to keep /usr/ports with portsnap or move ports to svn as well. Peace be to you, Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Darrel writes: > On Mon, 3 Sep 2012, Lowell Gilbert wrote: > >> Matthew Seaman writes: >> >>> On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. >>> >>> stable/9 is the SVN equivalent of RELENG_9 >> >> Ah, yes, that makes sense. I hadn't looked higher than the releng part >> of the path. >> >> Is anyone working on documenting this for the "cutting edge" section of >> the Handbook? I could take a shot at it myself, but I likely couldn't >> produce anything intelligible for beginners (at least, not before 9.1 is >> out). >> > > If you do decide to write a new section, I could possibly offer help > on "dumbing it down". :) At least with the English version. http://www.freebsd.org/cgi/query-pr.cgi?pr=171292 I don't think "dumbing it down" is an issue. What I may have left out that beginners wouldn't think of... more of a concern. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
stable/9 is the SVN equivalent of RELENG_9 src only, understood now. Thanks, Matthew. Yes. There is never any branching in the ports tree. The latest (i.e., head) version is, at any given time, expected to work for all (then) supported versions of the base system. This is not a change -- this has always been the case, and the current (cvsup-centric) text in the Handbook describes it explicitly. same as nbsd, then. I probably need to read fbsd handbook again It turns out that mergemaster would have been alright in my case, due to .mergemasterrc, I can not recall why this was selected, comments are welcomed: # cat .mergemasterrc FREEBSD_ID=YES Equivalent to -F. VERBOSE=YES AUTO_INSTALL=YES RUN_UPDATES=YES COMP_CONFS=YES PRESERVE_FILES_DIR=/var/tmp/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` DELETE_STALE_RC_FILES=YES A reasonable set of defaults, although I prefer a little more human interaction on major changes. Why it "would have been alright(sic)" in your case isn't clear, because you don't describe the alternative, but the manual for mergemaster(8) almost certainly has the answer. Hopefully not to have bored you too much, Matthew's mention of -F with mergemaster solved this problem of conversion from csup to svn- yet as you saw it was already in my .mergemasterrc , that is why I wrote that it "would have been alright". I like human interaction in every case where it is beneficial. If you want to send some guidance, it is welcomed. Other than that, I will let it be and also study the manual again; i.e. man 8 mergemaster. Kind regards, Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
On Mon, 3 Sep 2012, Matthew Seaman wrote: On 03/09/2012 19:00, Darrel wrote: Could I then run: svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ or | and svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? Why don't you try it and see? All you'll get is an error message essentially saying 'file not found.' After reading so many of your intelligent posts, then I typically default to believing in your methods. To get svn:// to work then the fileserver, i.e., -fbsd9 and at the moment becoming -fbsd91 required service svn added outbound in pf.conf. The gateway is -obsd51 and needed the port number out in pf.conf, since svn is not included in /etc/services. :) Simply put, there isn't a path ports/releng/9.1 or ports/stable/9 in the FreeBSD SVN repository. Look here if you don't believe me: http://svnweb.freebsd.org/ Click on 'ports' and look at the subdirectories under there. The *only* bit of the SVN repository that follows the branching structure you seem so enamoured of is base -- the system sources. Get that clear in your head, and you will have a much better time of it. The releases seem neat to me because fbsd reports to have security officers tracking the specified version. I am not necessarily enamoured with it. I have followed -stable and -current before. I can use portsnap as before, or experiment. I might try: svn co svn://svn.freebsd.org/ports /usr/ports I probably know everything for my purposes at this point. As the fileserver is building, some of the points seem obvious now. Thanks to you and Lowell. Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Darrel writes: For ports would it be better to match -fbsd91, like this: svn co http://svn.freebsd.org/ports/releng/9.1 ports >> >> >> On 03/09/2012 17:29, Lowell Gilbert wrote: >>> I'm not sure whether there's any equivalent to tracking RELENG_9 (as >>> opposed to tracking RELENG_9_1) under the branching scheme being used >>> with subversion. >> >> stable/9 is the SVN equivalent of RELENG_9 >> >> > > Could I then run: > > svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ > > or | and > > svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? No. > Since in the past several years I installed minimal fbsd and then used > portsnap for ports, so I was not aware that -head was the only option > for ports- is that what Lowell was pointing out? Yes. There is never any branching in the ports tree. The latest (i.e., head) version is, at any given time, expected to work for all (then) supported versions of the base system. This is not a change -- this has always been the case, and the current (cvsup-centric) text in the Handbook describes it explicitly. > It turns out that mergemaster would have been alright in my case, due > to .mergemasterrc, I can not recall why this was selected, comments > are welcomed: > > # cat .mergemasterrc > FREEBSD_ID=YES Equivalent to -F. > VERBOSE=YES > AUTO_INSTALL=YES > RUN_UPDATES=YES > COMP_CONFS=YES > PRESERVE_FILES_DIR=/var/tmp/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` > DELETE_STALE_RC_FILES=YES A reasonable set of defaults, although I prefer a little more human interaction on major changes. Why it "would have been alright(sic)" in your case isn't clear, because you don't describe the alternative, but the manual for mergemaster(8) almost certainly has the answer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
On 03/09/2012 19:00, Darrel wrote: > Could I then run: > > svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ > > or | and > > svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? > Why don't you try it and see? All you'll get is an error message essentially saying 'file not found.' Simply put, there isn't a path ports/releng/9.1 or ports/stable/9 in the FreeBSD SVN repository. Look here if you don't believe me: http://svnweb.freebsd.org/ Click on 'ports' and look at the subdirectories under there. The *only* bit of the SVN repository that follows the branching structure you seem so enamoured of is base -- the system sources. Get that clear in your head, and you will have a much better time of it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [solved]: to move csup 90 to subversion 91rc
For ports would it be better to match -fbsd91, like this: svn co http://svn.freebsd.org/ports/releng/9.1 ports On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Could I then run: svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ or | and svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? Since in the past several years I installed minimal fbsd and then used portsnap for ports, so I was not aware that -head was the only option for ports- is that what Lowell was pointing out? It turns out that mergemaster would have been alright in my case, due to .mergemasterrc, I can not recall why this was selected, comments are welcomed: # cat .mergemasterrc FREEBSD_ID=YES VERBOSE=YES AUTO_INSTALL=YES RUN_UPDATES=YES COMP_CONFS=YES PRESERVE_FILES_DIR=/var/tmp/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` DELETE_STALE_RC_FILES=YES Kind regards, Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
On Mon, 3 Sep 2012, Lowell Gilbert wrote: Matthew Seaman writes: On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Ah, yes, that makes sense. I hadn't looked higher than the releng part of the path. Is anyone working on documenting this for the "cutting edge" section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). If you do decide to write a new section, I could possibly offer help on "dumbing it down". :) At least with the English version. Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Lowell Gilbert writes: > Is anyone working on documenting this for the "cutting edge" > section of the Handbook? I could take a shot at it myself, but I > likely couldn't produce anything intelligible for beginners (at > least, not before 9.1 is out). That would be hugely appreciated; none of the current references (I'm aware of) carry the imprimitur of the Handbook. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Matthew Seaman writes: > On 03/09/2012 17:29, Lowell Gilbert wrote: >> I'm not sure whether there's any equivalent to tracking RELENG_9 (as >> opposed to tracking RELENG_9_1) under the branching scheme being used >> with subversion. > > stable/9 is the SVN equivalent of RELENG_9 Ah, yes, that makes sense. I hadn't looked higher than the releng part of the path. Is anyone working on documenting this for the "cutting edge" section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved]: to move csup 90 to subversion 91rc
Darrel wrote: >> For ports would it be better to match -fbsd91, like this: >> svn co http://svn.freebsd.org/ports/releng/9.1 ports 404. There are no branches in the ports, in exactly the same way that there wasn't a RELENG_9 tag you could use in a ports supfile. Head is the only option with ports. On 03/09/2012 17:29, Lowell Gilbert wrote: > I'm not sure whether there's any equivalent to tracking RELENG_9 (as > opposed to tracking RELENG_9_1) under the branching scheme being used > with subversion. stable/9 is the SVN equivalent of RELENG_9 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [solved]: to move csup 90 to subversion 91rc
Darrel writes: > Thanks, Matthew- and especially for mentioning to use -F on the first > subsequent run of mergemaster. > >> >> svn co http://svn.freebsd.org/base/releng/9.1 src >> > > For ports would it be better to match -fbsd91, like this: > svn co http://svn.freebsd.org/ports/releng/9.1 ports > > or can the most recent ports be run with a release, like this: > svn co http://svn.freebsd.org/ports/head ports > > Someone off of the list recommended something like this: > > svn co svn://svn.penx.com/base/releng/9.1 /usr/src > svn co svn://svn.penx.com/ports/head /usr/ports I would expect ports to still be best with head, as I haven't heard anything about branching it. I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
