Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Mon, Jan 07, 2008 at 03:58:41AM +, Frank Shute wrote: On Sun, Jan 06, 2008 at 09:24:15PM +0100, Erik Trulsson wrote: On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote: On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: Hi Upon reading chapters of the Handbook about the Ports collection and CVSup, I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using the wrong tag (tag=.), I erroneously but successfully installed the CURRENT version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the sake of learning and training myself I did not. You used the right tag. There is only a current tag as you only have a current ports tree to be used for all releases ie 6.2,6.3 7.0 (The ports might work with older releases too). Wrong. The ports tree is not branched, but it is tagged and it does have tags corresponding to each FreeBSD release. So if it's not branched but tagged, what's the difference between the ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags in my ports supfile? None whatsoever. Neither tag is a valid tag for the ports tree, so you will end up with an empty ports tree in either case. If you were instead to use the valid tags RELEASE_4_8_0 or RELEASE_7_0_0 you would get the ports tree that shipped with 4.8-RELEASE or the ports tree that will (barring last minute changes) ship with 7.0-RELEASE respectively. Problem: - I ran CVSup again with the correct tag but though everything in the process looked normal, the map usr/ports remains empty and nor with whereis nor with pkg_xxx any information about ports can be found. You ran cvsup again with the wrong tag. Questions: - What did I do wrong in the process?. Used the wrong tag second time around. - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea anyway (technically) ? No. Although there is no 6.2 ports collection, just CURRENT. Of course there is a 6.2 ports collection. What else would you call the ports tree shipped with FreeBSD 6.2? A snapshot of the ports tree when the release was made. Proces: - I use the recently installed cvsup-without-gui, installed from ports Use csup(1) it's identical to cvsup but no dependencies as it's in base written in C. Not quite identical. There are a couple of features that cvsup(1) has, but which csup(1) does not yet have. To just check out a copy of the ports tree either should work fine though. Features that a newbie wouldn't use. It's also difficult to build cvsup when you don't necessarily have a ports tree. But you do not need a ports tree to install cvsup as a package. In either case csup(1) is not identical to cvsup(1) in functionality even if it can often be used as a drop-in replacement. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank Shute wrote: So if it's not branched but tagged, what's the difference between the ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags in my ports supfile? Probably not a very great deal -- you'll get equally disappointing results for both of those. RELENG_X and RELENG_X_Y tags / branches apply to the src collection *only*. If you try and use them on the ports you'll end up with a whole lot of nothing. None of the ports tree is intentionally tagged with anything matching 'RELENG' In general, you always want the HEAD of the ports tree. There's very little point in using anything else. However it is possible to use RELEASE_X_Y_0 to match the state of the ports tree used to generate the packages distributed with X.Y RELEASE, or if you still haven't upgraded all your 4.x machines yet, you can use RELEASE_4_EOL to match the last state of the tree before the 4.x compatability code was stripped out. Note that cvsup'ing an old version of the ports tree is not guaranteed to provide a workable ports collection: the dist files the ports rely upon are not in the control of the FreeBSD project and there is no assurance that old versions of software are still available for download. Plus you will be struggling with unfixed security bugs if you've installed portaudit -- or installing vulnerable software if you haven't. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHgerP8Mjk52CukIwRCFAlAKCNmQAfP3JDHdBde/s4VWwcs3BGsACeNG/d kbfd4wXcBsG1U6tYvwIXmD0= =3Rc0 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Mon, Jan 07, 2008 at 09:03:12AM +, Matthew Seaman wrote: Frank Shute wrote: So if it's not branched but tagged, what's the difference between the ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags in my ports supfile? Probably not a very great deal -- you'll get equally disappointing results for both of those. RELENG_X and RELENG_X_Y tags / branches apply to the src collection *only*. If you try and use them on the ports you'll end up with a whole lot of nothing. None of the ports tree is intentionally tagged with anything matching 'RELENG' This is where the original poster went wrong, he first off used tag=. which got him current ports, decided he wanted 6.2 ports and used RELENG_6_2 as a tag in his ports supfile and got nothing. In general, you always want the HEAD of the ports tree. There's very little point in using anything else. I was trying to make the point you should use tag=. in ports supfile. However it is possible to use RELEASE_X_Y_0 to match the state of the ports tree used to generate the packages distributed with X.Y RELEASE, or if you still haven't upgraded all your 4.x machines yet, you can use RELEASE_4_EOL to match the last state of the tree before the 4.x compatability code was stripped out. This I didn't know. It used to be AFAIR that because of disk constraints only head was available. But I see from the CVS tags page that you can get the tree in it's old state with tags such as: RELENG_6_2_0_RELEASE http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html A.7.2 Note that cvsup'ing an old version of the ports tree is not guaranteed to provide a workable ports collection: the dist files the ports rely upon are not in the control of the FreeBSD project and there is no assurance that old versions of software are still available for download. Plus you will be struggling with unfixed security bugs if you've installed portaudit -- or installing vulnerable software if you haven't. I can't see the point in holding old versions of the ports tree except for nostalgic reasons and masochists. Although, I suppose portdowngrade works with it (never used it). Even the oldest machine you can usually upgrade to something new. E.g Tags for my webserver (300MHz Celeron 128MB) is tag=. for ports and RELEASE_6_3 for src. Works fine. Used to have problems building ruby due to the low memory so just built a package on my workstation and copied it over. Cheers, Matthew Thanks for explaining how things currently stand, Matthew. Regards, -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: Hi Upon reading chapters of the Handbook about the Ports collection and CVSup, I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using the wrong tag (tag=.), I erroneously but successfully installed the CURRENT version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the sake of learning and training myself I did not. Problem: - I ran CVSup again with the correct tag but though everything in the process looked normal, the map usr/ports remains empty and nor with whereis nor with pkg_xxx any information about ports can be found. Questions: - What did I do wrong in the process?. You used the wrong tag. If you want the exact version of the ports tree that shipped with 6.2 the correct tag to use is RELEASE_6_2_0. RELENG_6_2_0_RELEASE is the tag used for the base system corresponding to 6.2-RELEASE. - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea anyway (technically) ? If you actually want the ports tree as it was when 6.2-RELEASE was made, then it is not a bad idea. Most of the time one would like a more updated version of the ports tree though. Proces: - I use the recently installed cvsup-without-gui, installed from ports - I deleted all entries and maps in/under /usr/ports (as recommended in the Handbook) - I modified the ports-supfile in usr/share/examples/cvsup and copied it to portswj-supfile in the same map (not good practice I know now) The settings in the -supfile where: *default host=cvsup15.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6_2_0_RELEASE (the handbook suggests that this is a valid tag for ports) I doubt the handbook suggests that. If it does it is wrong. *default delete use-rel-suffix (I could not find a meaning for this in the books, anyone can tell me please?) Read the cvsup(1) manpage. *default compress ports-all - I ran: cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile The conversation looked OK, no error messages but also no scrolling list of files There is a logfile in /var/db/sup ports-all, something like n.cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the ports collection that looks normal and every record shows also RELENG_6_2_0_RELEASE. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
Erik Trulsson wrote: On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: Hi Upon reading chapters of the Handbook about the Ports collection and CVSup, I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using the wrong tag (tag=.), I erroneously but successfully installed the CURRENT version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the sake of learning and training myself I did not. Problem: - I ran CVSup again with the correct tag but though everything in the process looked normal, the map usr/ports remains empty and nor with whereis nor with pkg_xxx any information about ports can be found. Questions: - What did I do wrong in the process?. You used the wrong tag. If you want the exact version of the ports tree that shipped with 6.2 the correct tag to use is RELEASE_6_2_0. RELENG_6_2_0_RELEASE is the tag used for the base system corresponding to 6.2-RELEASE. - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea anyway (technically) ? If you actually want the ports tree as it was when 6.2-RELEASE was made, then it is not a bad idea. Most of the time one would like a more updated version of the ports tree though. Proces: - I use the recently installed cvsup-without-gui, installed from ports - I deleted all entries and maps in/under /usr/ports (as recommended in the Handbook) - I modified the ports-supfile in usr/share/examples/cvsup and copied it to portswj-supfile in the same map (not good practice I know now) The settings in the -supfile where: *default host=cvsup15.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6_2_0_RELEASE (the handbook suggests that this is a valid tag for ports) I doubt the handbook suggests that. If it does it is wrong. *default delete use-rel-suffix (I could not find a meaning for this in the books, anyone can tell me please?) Read the cvsup(1) manpage. *default compress ports-all - I ran: cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile The conversation looked OK, no error messages but also no scrolling list of files There is a logfile in /var/db/sup ports-all, something like n.cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the ports collection that looks normal and every record shows also RELENG_6_2_0_RELEASE. One idiotic question on the top of his troubles. According to the disclaimer posted on the ports web-site. The ports tree supports only Stable and Current version of the OS. Since Release is sort of more stable than the Stable I wonder if there is a frozen ports three with frozen packages for 6.2 release? Personally, I was always following stable branch which is moving target as you know. One needs to portsnap fetch and update ports three before every build up and also portupgrade has to be done fairly regularly. Personally, I could not care less for the newest versions of the programs as long as the old one are stable so for me staying with release would be perfectly OK. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: Hi Upon reading chapters of the Handbook about the Ports collection and CVSup, I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using the wrong tag (tag=.), I erroneously but successfully installed the CURRENT version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the sake of learning and training myself I did not. You used the right tag. There is only a current tag as you only have a current ports tree to be used for all releases ie 6.2,6.3 7.0 (The ports might work with older releases too). Problem: - I ran CVSup again with the correct tag but though everything in the process looked normal, the map usr/ports remains empty and nor with whereis nor with pkg_xxx any information about ports can be found. You ran cvsup again with the wrong tag. Questions: - What did I do wrong in the process?. Used the wrong tag second time around. - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea anyway (technically) ? No. Although there is no 6.2 ports collection, just CURRENT. Proces: - I use the recently installed cvsup-without-gui, installed from ports Use csup(1) it's identical to cvsup but no dependencies as it's in base written in C. - I deleted all entries and maps in/under /usr/ports (as recommended in the Handbook) All you need is the empty dir /usr/ports and c(v)sup will fill it. - I modified the ports-supfile in usr/share/examples/cvsup and copied it to portswj-supfile in the same map (not good practice I know now) The settings in the -supfile where: *default host=cvsup15.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6_2_0_RELEASE (the handbook suggests that this is a valid tag for ports) *default delete use-rel-suffix (I could not find a meaning for this in the books, anyone can tell me please?) *default compress ports-all Try this as your ports-supfile: *default host=cvsup15.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all and run: csup -L 2 /usr/share/examples/cvsup/ports-supfile and it should download the current ports tree. For the src supfile you should use the tag: *default release=cvs tag=RELENG_6_3 as 6.3 is pretty close to release and you'll get 6.3RC2 probably. or if you want 7.0RC2(?) *default release=cvs tag=RELENG_7_0 For the src-supfile you only need to set that tag and the default host and it should work. Regards, -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote: On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: Hi Upon reading chapters of the Handbook about the Ports collection and CVSup, I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using the wrong tag (tag=.), I erroneously but successfully installed the CURRENT version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the sake of learning and training myself I did not. You used the right tag. There is only a current tag as you only have a current ports tree to be used for all releases ie 6.2,6.3 7.0 (The ports might work with older releases too). Wrong. The ports tree is not branched, but it is tagged and it does have tags corresponding to each FreeBSD release. Problem: - I ran CVSup again with the correct tag but though everything in the process looked normal, the map usr/ports remains empty and nor with whereis nor with pkg_xxx any information about ports can be found. You ran cvsup again with the wrong tag. Questions: - What did I do wrong in the process?. Used the wrong tag second time around. - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea anyway (technically) ? No. Although there is no 6.2 ports collection, just CURRENT. Of course there is a 6.2 ports collection. What else would you call the ports tree shipped with FreeBSD 6.2? Proces: - I use the recently installed cvsup-without-gui, installed from ports Use csup(1) it's identical to cvsup but no dependencies as it's in base written in C. Not quite identical. There are a couple of features that cvsup(1) has, but which csup(1) does not yet have. To just check out a copy of the ports tree either should work fine though. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Sun, Jan 06, 2008 at 09:24:15PM +0100, Erik Trulsson wrote: On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote: On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: Hi Upon reading chapters of the Handbook about the Ports collection and CVSup, I wanted to CVSup the ports collection for the RELEASE 6.2. Stupidly using the wrong tag (tag=.), I erroneously but successfully installed the CURRENT version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the sake of learning and training myself I did not. You used the right tag. There is only a current tag as you only have a current ports tree to be used for all releases ie 6.2,6.3 7.0 (The ports might work with older releases too). Wrong. The ports tree is not branched, but it is tagged and it does have tags corresponding to each FreeBSD release. So if it's not branched but tagged, what's the difference between the ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags in my ports supfile? Problem: - I ran CVSup again with the correct tag but though everything in the process looked normal, the map usr/ports remains empty and nor with whereis nor with pkg_xxx any information about ports can be found. You ran cvsup again with the wrong tag. Questions: - What did I do wrong in the process?. Used the wrong tag second time around. - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea anyway (technically) ? No. Although there is no 6.2 ports collection, just CURRENT. Of course there is a 6.2 ports collection. What else would you call the ports tree shipped with FreeBSD 6.2? A snapshot of the ports tree when the release was made. Proces: - I use the recently installed cvsup-without-gui, installed from ports Use csup(1) it's identical to cvsup but no dependencies as it's in base written in C. Not quite identical. There are a couple of features that cvsup(1) has, but which csup(1) does not yet have. To just check out a copy of the ports tree either should work fine though. Features that a newbie wouldn't use. It's also difficult to build cvsup when you don't necessarily have a ports tree. Regards, -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port collection RELEASE6.2 lost after reinstall with CVSUP
On Mon, Jan 07, 2008 at 12:34:50AM +0100, Walter Jansen wrote: Thanks for your effort Fank, but unfortunately the Handbook shows that your answer does not reflect the actual use of tags for fetching ports with cvsup. Your answer triggers me to look for other places where information can be found in order to reduce the confusion, and that is what I am grateful for. Walter, show me in the handbook where my answer doesn't reflect the reality of using tags for fetching ports. Thanks. Read this (I know it's old): http://www.freebsddiary.org/ports.php // NOTE: Don't worry about releases/version when cvsup'ing your ports. There is only one version of the Ports collection. All versions of FreeBSD use the same ports collection. Therefore, when updating your ports use this tag: tag=. // You can use that tag for your src supfile too but you will get 8.0 which you don't want to do unless you are a developer. Have a good day! Walter You too. -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
