Re: is csup broken?
On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: is csup broken?
On Wed, Jan 02, 2013 at 04:20:25PM +0100, Polytropon wrote: Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? ISTM that SVN is not the default method for users; but portsnap is the preferred method for users. Developers, OTOH, may find SVN useful. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-portsnap.html I have no idea if the OP is a user or a developer; but I do know that at least a cursory reading of the Handbook is a good idea, since the OP question seems to be directly addressed in the Handbook. Regards, Joe ___ 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: is csup broken?
On Wednesday 02 January 2013 10:14:17 am Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 It must have to do with the security incident that took place a couple of months ago. It affects all package updates for 9.1 via pkg_add and csup, I guess. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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: is csup broken?
Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. Really between a rock and a hard place. What the heck are the Freebsd officials doing? They really mucked up 9.1 release big time. ___ 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: is csup broken?
Joe Altman wrote: On Wed, Jan 02, 2013 at 04:20:25PM +0100, Polytropon wrote: Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? ISTM that SVN is not the default method for users; but portsnap is the preferred method for users. Developers, OTOH, may find SVN useful. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-portsnap.html I have no idea if the OP is a user or a developer; but I do know that at least a cursory reading of the Handbook is a good idea, since the OP question seems to be directly addressed in the Handbook. Regards, Joe As the OP I see no need to pollute my system with a complete ports tree when I only have to compile php5 to enable the apache module. Thats over kill in my book. Sure the handbook says to use portsnap but that still loads the complete ports tree. crazy. My ports tree only has the ports I have to recompile to change defaults used in package. This approach saves disk and backup times. ___ 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: is csup broken?
On Wed, 02 Jan 2013 10:34:54 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. You actually don't _have_ to use CSV. You can install SVN from binary packages via the new pkg command (pkgng instead of traditional pkg_* tools). Or you can obtain a ports tree first with portsnap or from the installation media you've been using, install svn from this, and then continue using svn to obtain updates for ports (and src, if you want). However, you're right about the fact that svn isn't part of the base installation (yet?) and it doesn't fully integrate with what worked with CVS for many years. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: is csup broken?
Dimitri Yioulos wrote: On Wednesday 02 January 2013 10:14:17 am Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 It must have to do with the security incident that took place a couple of months ago. It affects all package updates for 9.1 via pkg_add and csup, I guess. Dimitri I am not talking about packages here. subject says is csup broken? I use csup to fetch individual ports not packages. ___ 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: is csup broken?
Polytropon wrote: On Wed, 02 Jan 2013 10:34:54 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. You actually don't _have_ to use CSV. You can install SVN from binary packages via the new pkg command (pkgng instead of traditional pkg_* tools). Or you can obtain a ports tree first with portsnap or from the installation media you've been using, install svn from this, and then continue using svn to obtain updates for ports (and src, if you want). However, you're right about the fact that svn isn't part of the base installation (yet?) and it doesn't fully integrate with what worked with CVS for many years. Still behind the 8 ball. The new pkg is not part of the base in 9.1 and there is no ftp packages for 9.1 and the disc1.iso media I installed from has no packages. I'm fubarbed Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. And doing a portsnap which may not contain my updated port for a few days if ever until all the other problem are addressed. This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. This is BAD public relations for FreeBSD. ___ 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: is csup broken?
On Wed, 02 Jan 2013 11:08:24 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:34:54 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. You actually don't _have_ to use CSV. You can install SVN from binary packages via the new pkg command (pkgng instead of traditional pkg_* tools). Or you can obtain a ports tree first with portsnap or from the installation media you've been using, install svn from this, and then continue using svn to obtain updates for ports (and src, if you want). However, you're right about the fact that svn isn't part of the base installation (yet?) and it doesn't fully integrate with what worked with CVS for many years. Still behind the 8 ball. The new pkg is not part of the base in 9.1 and there is no ftp packages for 9.1 and the disc1.iso media I installed from has no packages. I'm fubarbed There is an option, even thogh possibly considered unelegant in your situation: Install the ports tree from the installation media and then install the svn port from that outdated ports tree. Afterwards delete the ports tree and use svn to get the components you need. Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. And doing a portsnap which may not contain my updated port for a few days if ever until all the other problem are addressed. That's true - SVN (formerly CVS) provided you with ad hoc changes to the ports tree, whereas portsnap provides a snapshot that might not be enough up to date. I'd really like to see a svn command being part of the base installation, with integration into the comfortable make update mechanism for ports and system sources so it can _really and actually_ replace csup. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: is csup broken?
On Wed, 2 Jan 2013 11:08:24 -0500 fb...@a1poweruser.com wrote: This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. This is FUD. Stop being afraid of change. Users use portsnap Power users use svn There's no use trying to cover everyone's edge cases. You'll never keep everyone happy. Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. Please don't commit ports to the ports tree if you have not tested them! ___ 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: is csup broken?
Mark Felder wrote: On Wed, 2 Jan 2013 11:08:24 -0500 fb...@a1poweruser.com wrote: This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. This is FUD. Stop being afraid of change. Users use portsnap Power users use svn There's no use trying to cover everyone's edge cases. You'll never keep everyone happy. Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. Please don't commit ports to the ports tree if you have not tested them! Hay cutting out part of the post to make things look different than they are is just wrong. As the thread explains the situation which you conveniently cut out. If my words were not clear. My port works at my end, but I also check that the comment port process does not get kinked messing up the port at the ports system end. ___ 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: is csup broken?
On 01/02/13 10:08, Fbsd8 wrote: snip Still behind the 8 ball. No, I'm sorry but that's you. The new pkg is not part of the base in 9.1 and there is no ftp packages for 9.1 and the disc1.iso media I installed from has no packages. I don't know what crap you're talking, but if you would have installed the ports tree upon installation this wouldn't be an issue. Yes, you want to save space and cut down on back-up times, awesome goals, but you should have been following on the list and in the handbook where CVS has been deprecated (whether for good or bad, it's done) and portsnap/SVN are now the preferred methods. I'm fubarbed No, just too lazy to pull off a few extra steps for a one-off with portsnap or svn (which you will have to compile yourself, I'm afraid, though maybe someone will make a package for ya) Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. And? Pull it in with svn. I use svn to keep tabs on tk85 (and I only pull in tk85) in my user folder and I use svn to update my ports tree nightly. And doing a portsnap which may not contain my updated port for a few days if ever until all the other problem are addressed. portsnap shouldn't be affected by the pkgbeta site being down, someone else with more knowledge on the subject should feel free to correct me. This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. Prematurely? Depending on what source you go to it's at least two months behind. This is BAD public relations for FreeBSD. Now there is some FUD for ya. -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ 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
