Which ports tree through svn?
Hello list, I'm using: FreeBSD myhost.mydomain.com 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I want/need to use svn for my ports tree mainly because I need to downgrade ports. There is portdowngrade in the ports tree but that relies on cvs which is no longer available. The only way that I'm able to do this now is with svn log and svn up -r to the revision needed so I get the version that I need in the port. My problem is what do i need to checkout in the first place for 9.0-RELEASE? svn co svn://svn.freebsd.org/ports/head /usr/ports or svn co snv://svn.freebsd.org/tags/RELEASE_9_0_0 /usr/ports? The first one seems to be up to date but the latter has for eg apache version 2.2.21 from 2011; I presume from the portfreeze before 9 was released. Maybe there are any means to downgrade ports while using portsnap that I'm not aware of. Thank you, Andrei ___ 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: Which ports tree through svn?
On Jan 9, 2013, at 3:41 PM, Andrei Brezan andrei...@gmail.com wrote: Hello list, I'm using: FreeBSD myhost.mydomain.com 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I want/need to use svn for my ports tree mainly because I need to downgrade ports. There is portdowngrade in the ports tree but that relies on cvs which is no longer available. The only way that I'm able to do this now is with svn log and svn up -r to the revision needed so I get the version that I need in the port. My problem is what do i need to checkout in the first place for 9.0-RELEASE? svn co svn://svn.freebsd.org/ports/head /usr/ports or svn co snv://svn.freebsd.org/tags/RELEASE_9_0_0 /usr/ports? The first one seems to be up to date but the latter has for eg apache version 2.2.21 from 2011; I presume from the portfreeze before 9 was released. Maybe there are any means to downgrade ports while using portsnap that I'm not aware of. Thank you, Andrei http://svn.freebsd.org/ports/tags/RELEASE_9_0_0/ Note that, unless I'm mistaken, this branch is frozen so you won't be getting any update. ___ 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: Which ports tree through svn?
On Wed, 9 Jan 2013, Fleuriot Damien wrote: On Jan 9, 2013, at 3:41 PM, Andrei Brezan andrei...@gmail.com wrote: Hello list, I'm using: FreeBSD myhost.mydomain.com 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I want/need to use svn for my ports tree mainly because I need to downgrade ports. There is portdowngrade in the ports tree but that relies on cvs which is no longer available. The only way that I'm able to do this now is with svn log and svn up -r to the revision needed so I get the version that I need in the port. My problem is what do i need to checkout in the first place for 9.0-RELEASE? svn co svn://svn.freebsd.org/ports/head /usr/ports or svn co snv://svn.freebsd.org/tags/RELEASE_9_0_0 /usr/ports? The first one seems to be up to date but the latter has for eg apache version 2.2.21 from 2011; I presume from the portfreeze before 9 was released. Maybe there are any means to downgrade ports while using portsnap that I'm not aware of. Thank you, Andrei http://svn.freebsd.org/ports/tags/RELEASE_9_0_0/ Note that, unless I'm mistaken, this branch is frozen so you won't be getting any update. Might as well use the real ports tree, the first option shown above, since it also has the previous history. ___ 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: When Is The Ports Tree Going To Be Updated?
jb jb.1234abcd at gmail.com writes: ... I tested and compared results on FreeBSD 9.0 and FreeBSD 9.1-RC3 (done here earlier) and this is a summary. Please review it, in particular the conclusions, as they are intended to be the base for filing a PR#. Test on FreeBSD 9.0 --- $ uname -a FreeBSD localhost.localdomain 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 # ls /var/db/pkg/portmaster-3.11/ # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26912299 Nov 28 08:53 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26796230 Nov 28 08:53 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26777464 Nov 28 08:53 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portmaster -L | egrep '(ew|ort) version|total install' ... === New version available: xorg-7.5.2 === 452 total installed ports === 194 have new versions available # portmaster -L --index | egrep '(ew|ort) version|total install' ... === New version available: xorg-7.5.2 === 452 total installed ports === 194 have new versions available # portmaster -L --index-only | egrep '(ew|ort) version|total install' ... === New version available: xorg-7.5.2 === 452 total installed ports === 194 have new versions available # # rm -rf /usr/ports # portsnap extract ... Building new INDEX files... done. # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26912299 Nov 28 09:07 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26796230 Nov 28 09:07 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26777464 Nov 28 09:07 /usr/ports/INDEX-9 # portmaster -L | egrep '(ew|ort) version|total install' ... === New version available: xorg-7.5.2 === 452 total installed ports === 194 have new versions available # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-32794-index/INDEX-9.bz2100% of 1615 kB 173 kBps ... === New version available: xorg-7.5.2 === 452 total installed ports === 193 have new versions available # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26912299 Nov 28 09:07 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26796230 Nov 28 09:07 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26665016 Nov 28 09:12 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portmaster -L --index-only | egrep '(ew|ort) version|total install' ... === New version available: xorg-7.5.2 === 452 total installed ports === 193 have new versions available # The result shows that after this step: # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-32794-index/INDEX-9.bz2100% of 1615 kB 173 kBps the uncompressed INDEX-9 -rw-r--r-- 1 root wheel 26665016 Nov 28 09:12 /usr/ports/INDEX-9 is different from the prior original INDEX-9 -rw-r--r-- 1 root wheel 26777464 Nov 28 09:07 /usr/ports/INDEX-9 The cause of it could be: - either portmaster gets identical size-wise, but not necessarily content-wise INDEX-9.bz2 - or portmaster uncompresses INDEX-9.bz2 incorectly and loses some content Test on FreeBSD 9.1-RC3 --- $ uname -a ... 9.1-RC3 ... $ cat /usr/ports/ports-mgmt/portmaster/distinfo ... portmaster-portmaster-3.14-31009f6.tar.gz ... # portsnap fetch extract # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879597 Nov 26 15:37 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763600 Nov 26 15:38 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26744834 Nov 26 15:38 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. # portmaster -L | egrep '(ew|ort) version|total install' === New version available: java-zoneinfo-2012.j === New version available: liberation-fonts-ttf-2.00.1,1 === New version available: libxul-10.0.11 === New version available: firefox-17.0,1 === New version available: libreoffice-3.5.7 === New version available: vigra-1.9.0 === 545 total installed ports === 6 have new versions available # portmaster -L --index | egrep '(ew|ort) version|total install' === New version available: java-zoneinfo-2012.j === New version available: liberation-fonts-ttf-2.00.1,1 === New version available: libxul-10.0.11 === New version available: firefox-17.0,1
Re: When Is The Ports Tree Going To Be Updated?
On 26 November 2012 21:15, jb jb.1234a...@gmail.com wrote: Tim Daneliuk tundra at tundraware.com writes: ... One wonders if using svn to keep the ports tree up-to-date might not be simpler, and perhaps, more reliable ... As managed by portsnap: $ du -hs /usr/ports/ 850M/usr/ports/ As managed by svn (it took much longer to checkout/download it by comparison): $ du -hs /usr/local/ports/ 1.4G/usr/local/ports/ $ du -hs /usr/local/ports/.svn/ 702M/usr/local/ports/.svn/ One thing about svn is that it is a developer's tool, with its own commands set (that should never be mixed with UNIX commands w/r to dir/file manipulation), and that should not be expected to be learned by non-devs. For that reasons alone the portsnap-managed ports repo is more generic, flexible to be handled by user and add-on apps/utilities, looks like more efficient without that svn overhead resulting from its requirements and characteristics as a source control system. But, svn offers to a user a unique view into ports repo, e.g. history, logs, info, attributes, etc. jb While we're on the binary vs SVN topic, I'd like to point out I'm *actually running out of inodes* on a virtualized machine (we use these a lot for our dev and preproduction environments) with 5gb of space, when checking out the ports tree. Of course 5gb is quite small but then, this was installed a while back. The transition to SVN means I'm going to have to reinstall these firewalls. There are a lot of them it's going to be a major pain. idk, I'm loathe to use portsnap, I liked CSup just fine. ___ 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: When Is The Ports Tree Going To Be Updated?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/27/12 4:36 AM, Damien Fleuriot wrote: On 26 November 2012 21:15, jb jb.1234a...@gmail.com wrote: Tim Daneliuk tundra at tundraware.com writes: ... One wonders if using svn to keep the ports tree up-to-date might not be simpler, and perhaps, more reliable ... As managed by portsnap: $ du -hs /usr/ports/ 850M/usr/ports/ As managed by svn (it took much longer to checkout/download it by comparison): $ du -hs /usr/local/ports/ 1.4G /usr/local/ports/ $ du -hs /usr/local/ports/.svn/ 702M /usr/local/ports/.svn/ One thing about svn is that it is a developer's tool, with its own commands set (that should never be mixed with UNIX commands w/r to dir/file manipulation), and that should not be expected to be learned by non-devs. For that reasons alone the portsnap-managed ports repo is more generic, flexible to be handled by user and add-on apps/utilities, looks like more efficient without that svn overhead resulting from its requirements and characteristics as a source control system. But, svn offers to a user a unique view into ports repo, e.g. history, logs, info, attributes, etc. jb While we're on the binary vs SVN topic, I'd like to point out I'm *actually running out of inodes* on a virtualized machine (we use these a lot for our dev and preproduction environments) with 5gb of space, when checking out the ports tree. Of course 5gb is quite small but then, this was installed a while back. The transition to SVN means I'm going to have to reinstall these firewalls. There are a lot of them it's going to be a major pain. idk, I'm loathe to use portsnap, I liked CSup just fine. Unless you plan to use svn commands other than checkout in your ports tree, I would suggest switching to svn export or perhaps the svn-export script (http://xyne.archlinux.ca/projects/svn-export/) to fetch your ports tree. The export command will not create the .svn metadata directory and will save on inode usage. Of course, you could also create a new virtual disk for /usr/ports and tune it with more inodes if you'd rather use svn checkout. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC029MACgkQ0sRouByUApBC5QCfZeDivNGRMWB4DV4usXGLojrv lBsAoIWG4O/ekYRiGJI0M238v+J1y/Lx =wHdv -END PGP SIGNATURE- ___ 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: When Is The Ports Tree Going To Be Updated?
On Nov 27, 2012, at 4:27 PM, Greg Larkin glar...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/27/12 4:36 AM, Damien Fleuriot wrote: On 26 November 2012 21:15, jb jb.1234a...@gmail.com wrote: Tim Daneliuk tundra at tundraware.com writes: ... One wonders if using svn to keep the ports tree up-to-date might not be simpler, and perhaps, more reliable ... As managed by portsnap: $ du -hs /usr/ports/ 850M/usr/ports/ As managed by svn (it took much longer to checkout/download it by comparison): $ du -hs /usr/local/ports/ 1.4G /usr/local/ports/ $ du -hs /usr/local/ports/.svn/ 702M /usr/local/ports/.svn/ One thing about svn is that it is a developer's tool, with its own commands set (that should never be mixed with UNIX commands w/r to dir/file manipulation), and that should not be expected to be learned by non-devs. For that reasons alone the portsnap-managed ports repo is more generic, flexible to be handled by user and add-on apps/utilities, looks like more efficient without that svn overhead resulting from its requirements and characteristics as a source control system. But, svn offers to a user a unique view into ports repo, e.g. history, logs, info, attributes, etc. jb While we're on the binary vs SVN topic, I'd like to point out I'm *actually running out of inodes* on a virtualized machine (we use these a lot for our dev and preproduction environments) with 5gb of space, when checking out the ports tree. Of course 5gb is quite small but then, this was installed a while back. The transition to SVN means I'm going to have to reinstall these firewalls. There are a lot of them it's going to be a major pain. idk, I'm loathe to use portsnap, I liked CSup just fine. Unless you plan to use svn commands other than checkout in your ports tree, I would suggest switching to svn export or perhaps the svn-export script (http://xyne.archlinux.ca/projects/svn-export/) to fetch your ports tree. The export command will not create the .svn metadata directory and will save on inode usage. Of course, you could also create a new virtual disk for /usr/ports and tune it with more inodes if you'd rather use svn checkout. Hope that helps, Greg - -- Greg Larkin Well I definitely don't plan on making changes to local files or committing stuff, I'd just like to keep an updated ports tree and switch from CVS to SVN. I guess I'll have a look at svn export, thanks for the tip Greg. ___ 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: When Is The Ports Tree Going To Be Updated?
On Tue, 27 Nov 2012, Greg Larkin wrote: Unless you plan to use svn commands other than checkout in your ports tree, I would suggest switching to svn export or perhaps the svn-export script (http://xyne.archlinux.ca/projects/svn-export/) to fetch your ports tree. The export command will not create the .svn metadata directory and will save on inode usage. Of course, you could also create a new virtual disk for /usr/ports and tune it with more inodes if you'd rather use svn checkout. It should be added that a stock svn export will download the entire ports tree each time rather than just the diffs. svn-export from above looks interesting, with the ability to get just updates. No port yet, though. ___ 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: When Is The Ports Tree Going To Be Updated?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/27/12 11:11 AM, Warren Block wrote: On Tue, 27 Nov 2012, Greg Larkin wrote: Unless you plan to use svn commands other than checkout in your ports tree, I would suggest switching to svn export or perhaps the svn-export script (http://xyne.archlinux.ca/projects/svn-export/) to fetch your ports tree. The export command will not create the .svn metadata directory and will save on inode usage. Of course, you could also create a new virtual disk for /usr/ports and tune it with more inodes if you'd rather use svn checkout. It should be added that a stock svn export will download the entire ports tree each time rather than just the diffs. svn-export from above looks interesting, with the ability to get just updates. No port yet, though. Yeah, I have to add that to my to-do list, since I mentioned it first. :) Cheers, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC07GEACgkQ0sRouByUApBViQCgng+ByDROCHM8UnfK1YDbUanK g0kAnjf22mYmOw5J3JLC/KyfQqsbNz06 =4tof -END PGP SIGNATURE- ___ 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: When Is The Ports Tree Going To Be Updated?
Tim Daneliuk tundra at tundraware.com writes: ... I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Well, not quite ... # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Ports tree hasn't changed since last snapshot. No updates needed. Ports tree is already up to date. # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879548 Nov 26 11:50 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763551 Nov 26 11:50 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26665016 Nov 26 11:53 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portmaster -L | egrep '(ew|ort) version|total install'=== New version available: java-zoneinfo-2012.j === New version available: liberation-fonts-ttf-2.00.1,1 === New version available: libxul-10.0.11 === New version available: firefox-17.0,1 === New version available: libreoffice-3.5.7 === New version available: vigra-1.9.0 === 545 total installed ports === 6 have new versions available # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: libreoffice-3.5.7 === 545 total installed ports === 1 has a new version available # portmaster -L --index | egrep '(ew|ort) version|total install' === New version available: libreoffice-3.5.7 === 545 total installed ports === 1 has a new version available # ___ 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: When Is The Ports Tree Going To Be Updated?
On 11/25/2012 11:17 PM, Warren Block wrote: On Sun, 25 Nov 2012, Matthew Seaman wrote: On 25/11/2012 23:10, Tim Daneliuk wrote: After the recent security scare, I know the ports tree was temporarily frozen. Does anyone know when it will again be updates. I just upgraded to 9.1-PRE and need to rebuild Firefox Thunderbird against the new libraries and ... they're broken, marked as security hazards... It's been being updated normally since near enough a week ago. Normally means subject to the pre-9.1-RELEASE restrictions on sweeping changes as is usual at this point in a release cycle. FireFox 17 and Thunderbird 17 updates were committed to ports on 20th November. Hmm. Is the index file being rebuilt? With FF16 installed, and 17 in the port directory, portsdb -Fu portversion -vl'' shows nothing to update. After 'make index', it does show. The problem was that I was missing the 'fetch' verb in my portsnap command. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: When Is The Ports Tree Going To Be Updated?
On 11/26/2012 01:30 AM, Matthew Seaman wrote: On 26/11/2012 00:59, Tim Daneliuk wrote: I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Ummm... how long have you been using portsnap? If you haven't been running 'portsnap fetch' or 'portsnap cron' then you won't have received any updates to your ports tree, ever. This is all explained quite clearly in the portsnap(8) man page. Cheers, Matthew I just switched from csup last week and am still learning the ropes. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: When Is The Ports Tree Going To Be Updated?
On Mon, Nov 26, 2012 at 3:48 PM, Tim Daneliuk tun...@tundraware.com wrote: On 11/26/2012 01:30 AM, Matthew Seaman wrote: On 26/11/2012 00:59, Tim Daneliuk wrote: I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Ummm... how long have you been using portsnap? If you haven't been running 'portsnap fetch' or 'portsnap cron' then you won't have received any updates to your ports tree, ever. This is all explained quite clearly in the portsnap(8) man page. Cheers, Matthew I just switched from csup last week and am still learning the ropes. I am starting to switch, and after all the discussions in this thread, I replaced my csup cron entry with the following: portsnap fetch portsnap extract portsnap update Initially I just had `csup -z -L 2 /usr/share/examples/cvsup/9.x-ports` where 9.x-ports was an edited version of ports-supfile. Now I have an /etc/portsnap.con with the equivalent edits from my 9.x-ports Is this how best to do it? And now I need to find an alternative to handle the src updates using svn or something... -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. ___ 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: When Is The Ports Tree Going To Be Updated?
On 26/11/2012 13:49, Odhiambo Washington wrote: I am starting to switch, and after all the discussions in this thread, I replaced my csup cron entry with the following: portsnap fetch portsnap extract portsnap update You definitely don't want to do this. Most importantly, 'extract' and 'update' aren't compatible. 'extract' says 'take all the data you downloaded, synthesize a *complete* ports tree from it, and overwrite /usr/ports with that, never mind what might have been there before'. 'update' says 'just add the changed bits since the last time you ran portsnap' ie. you only need to run 'extract' *once*, then you keep up to date by running 'update' at intervals. Secondly, for the sake of the servers, please don't run 'portsnap fetch' from a cron job. You're not the only person to think of doing that, and most people who do have the job run at the top of the hour. This is bad. The servers really don't like it when several thousand cronjobs all fire off simultaneously and the system load goes through the roof. Which is why 'portsnap cron' exists -- it does exactly the same as fetch, except it waits for a random amount of time before pulling down any data. Thirdly, you can tell portsnap several commands at once. So change your cron invocation to just: portsnap cron update and you should be happy. Initially I just had `csup -z -L 2 /usr/share/examples/cvsup/9.x-ports` where 9.x-ports was an edited version of ports-supfile. Now I have an /etc/portsnap.con with the equivalent edits from my 9.x-ports Is this how best to do it? No. You almost never need to modify the default portsnap.conf at all. portsnap works best if you use it to maintain a complete ports tree. It also automatically uses a geographically close server for best performance. And now I need to find an alternative to handle the src updates using svn or something... SVN works, but isn't amazingly quick. If you're on a release branch you can get the src (and just the src) using freebsd-update(8), which should be pretty speedy and which I think is going to be the officially blessed method for non-developers to keep up to date. Although anyone will still be able to use SVN if they want to. You'll need to tweak /etc/freebsd-update.conf slightly to get just the system sources. It's pretty obvious what to do. Cheers, Matthew ___ 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: When Is The Ports Tree Going To Be Updated?
On Monday 26 November 2012 13:49:05 Odhiambo Washington wrote: I am starting to switch, and after all the discussions in this thread, I replaced my csup cron entry with the following: portsnap fetch portsnap extract portsnap update portsnap fetch should only be used interactively; for non-interactive use, you should use portsnap cron portsnap extract is only needed for initialising your portsnap-maintained ports tree. So, after your initial portsnap run, what you need in your cron file is just portsnap fetch update -- Mike Clarke ___ 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: When Is The Ports Tree Going To Be Updated?
jb schreef op : Tim Daneliuk tundra at tundraware.com writes: ... I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Well, not quite ... I think, after the security incident, you had to obtain a fresh snapshot of the ports tree, i.e. you had to do portsnap fetch extract before usual service continued. May this be your problem? ___ 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: When Is The Ports Tree Going To Be Updated?
On Mon, Nov 26, 2012 at 5:14 PM, Mike Clarke jmc-freeb...@milibyte.co.ukwrote: On Monday 26 November 2012 13:49:05 Odhiambo Washington wrote: I am starting to switch, and after all the discussions in this thread, I replaced my csup cron entry with the following: portsnap fetch portsnap extract portsnap update portsnap fetch should only be used interactively; for non-interactive use, you should use portsnap cron portsnap extract is only needed for initialising your portsnap-maintained ports tree. So, after your initial portsnap run, what you need in your cron file is just portsnap fetch update So is portsnap cron update and portsnap fetch update doing the same thing? Whichever way, it sounds like I need an initial run of portsnap extract before putting this in crontab. @Matthew, I do not need all ports (astro, hungarian, etc...) but you appear to suggest I need everything, right? My portsnap.conf contains: *REFUSE all arabic astro benchmarks biology cad chinese finance french games german hebrew REFUSE hungarian japanese korean palm polish portuguese russian science ukranian vietnamese* Is that a misnomer? Then coming to freebsd-update (I never thought I'd have to use it one day!), I am a little confused with what to tinker. There are these two lines: *# Components of the base system which should be kept updated. Components src world kernel # Example for updating the userland and the kernel source code only: # Components src/base src/sys world* I always did csup to get my src then manually did the buildworld, make kernel, reboot, installworld, then mergemaster. From the above lines, I am not sure what I need, but think the Components src world is what I need. How it comes to build my custom kernel is still not clear to me. My mergemaster.rc contained: *IGNORE_FILES=/etc/crontab /etc/fstab /etc/group /etc/hosts /etc/inetd.conf /etc/make.conf /etc/master.passwd /etc/motd /etc/newsyslog.conf /etc/ntp.conf /etc/ntp.drift /etc/profile /etc/rc.conf /etc/resolv.conf /etc/services /etc/shells /etc/syslog.conf /etc/ssh/sshd_config /etc/ssh/ssh_host_key /etc/ssh/ssh_host_key.pub /etc/ssh/ssh_host_rsa_key /etc/ssh/ssh_host_rsa_key.pub /etc/passwd /etc/rc.conf.local /etc/zfs/exports /etc//namedb/named.conf /etc/periodic.conf /etc/hosts.allow /etc/hosts /etc/pf.conf /etc/sysctl.conf /etc/make.conf /etc/src.conf /etc/mail/aliases /etc/mail/mailer.conf /etc/remote* How now do I deal with this? Hopefully you can explain to someone who has been keeping off freebsd-update. I know there are many like me who are in this situation now that csup is getting deprecated. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. ___ 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: When Is The Ports Tree Going To Be Updated?
Matthew Seaman wrote: [snip] And now I need to find an alternative to handle the src updates using svn or something... SVN works, but isn't amazingly quick. If you're on a release branch you can get the src (and just the src) using freebsd-update(8), which should be pretty speedy and which I think is going to be the officially blessed method for non-developers to keep up to date. Although anyone will still be able to use SVN if they want to. You'll need to tweak /etc/freebsd-update.conf slightly to get just the system sources. It's pretty obvious what to do. As a result of the security incident I switched away from csup and am now using portsnap for ports, and svn for source. The only disconcerting item I noticed is the 500-some MB .svn directory now under /usr/src/. Can using freebsd-update for source update(s) eliminate the need for this 500MB waste of space? Or is there some switch for svn which could accomplish same? Thanks - Mike ___ 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: When Is The Ports Tree Going To Be Updated?
Stas Verberkt legolas at legolasweb.nl writes: jb schreef op : Tim Daneliuk tundra at tundraware.com writes: ... I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Well, not quite ... I think, after the security incident, you had to obtain a fresh snapshot of the ports tree, i.e. you had to do portsnap fetch extract before usual service continued. May this be your problem? # portsnap fetch extract # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879597 Nov 26 15:37 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763600 Nov 26 15:38 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26744834 Nov 26 15:38 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. # This fixed it. But, let's see what happens with this test: # rm -rf /usr/ports/ # portsnap extract # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879563 Nov 26 16:07 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763566 Nov 26 16:07 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26744800 Nov 26 16:07 /usr/ports/INDEX-9 # portmaster -L | egrep '(ew|ort) version|total install' === New version available: java-zoneinfo-2012.j === New version available: liberation-fonts-ttf-2.00.1,1 === New version available: libxul-10.0.11 === New version available: firefox-17.0,1 === New version available: libreoffice-3.5.7 === New version available: vigra-1.9.0 === 545 total installed ports === 6 have new versions available # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-78227-index/INDEX-9.bz2100% of 1615 kB 176 kBps 00m00s === New version available: libreoffice-3.5.7 === 545 total installed ports === 1 has a new version available # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: libreoffice-3.5.7 === 545 total installed ports === 1 has a new version available # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879563 Nov 26 16:07 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763566 Nov 26 16:07 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26665016 Nov 26 16:12 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portsnap update Ports tree is already up to date. # Well, what do you say about this ? jb ___ 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: When Is The Ports Tree Going To Be Updated?
I don't get what you're trying to show here. What commands you've run indicate that: 1/ you have an up to date ports tree 2/ one of the installed ports needs to be updated So what ? Just run # portmaster libreoffice I think you might be confused, new version available means that you have version 1.2.3 installed and that 1.2.4 is available *from the local ports tree*. It does not indicate that there is a newer version of a package available remotely and that you should update your ports tree. Hope this helps. On Nov 26, 2012, at 4:21 PM, jb jb.1234a...@gmail.com wrote: Stas Verberkt legolas at legolasweb.nl writes: jb schreef op : Tim Daneliuk tundra at tundraware.com writes: ... I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Well, not quite ... I think, after the security incident, you had to obtain a fresh snapshot of the ports tree, i.e. you had to do portsnap fetch extract before usual service continued. May this be your problem? # portsnap fetch extract # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879597 Nov 26 15:37 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763600 Nov 26 15:38 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26744834 Nov 26 15:38 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. # This fixed it. But, let's see what happens with this test: # rm -rf /usr/ports/ # portsnap extract # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879563 Nov 26 16:07 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763566 Nov 26 16:07 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26744800 Nov 26 16:07 /usr/ports/INDEX-9 # portmaster -L | egrep '(ew|ort) version|total install' === New version available: java-zoneinfo-2012.j === New version available: liberation-fonts-ttf-2.00.1,1 === New version available: libxul-10.0.11 === New version available: firefox-17.0,1 === New version available: libreoffice-3.5.7 === New version available: vigra-1.9.0 === 545 total installed ports === 6 have new versions available # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-78227-index/INDEX-9.bz2100% of 1615 kB 176 kBps 00m00s === New version available: libreoffice-3.5.7 === 545 total installed ports === 1 has a new version available # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: libreoffice-3.5.7 === 545 total installed ports === 1 has a new version available # ls -al /usr/ports/IN* -rw-r--r-- 1 root wheel 26879563 Nov 26 16:07 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26763566 Nov 26 16:07 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26665016 Nov 26 16:12 /usr/ports/INDEX-9 -rw-r--r-- 1 root wheel 1654048 Nov 11 11:45 /usr/ports/INDEX-9.bz2 # portsnap update Ports tree is already up to date. # Well, what do you say about this ? jb ___ 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 ___ 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: When Is The Ports Tree Going To Be Updated?
On Mon, 26 Nov 2012, kpn...@pobox.com wrote: On Mon, Nov 26, 2012 at 02:08:52PM +, Matthew Seaman wrote: Secondly, for the sake of the servers, please don't run 'portsnap fetch' from a cron job. You're not the only person to think of doing that, and most people who do have the job run at the top of the hour. This is bad. The servers really don't like it when several thousand cronjobs all fire off simultaneously and the system load goes through the roof. Which is why 'portsnap cron' exists -- it does exactly the same as fetch, except it waits for a random amount of time before pulling down any data. More generally, a cron job can be run with a random delay added before the real job kicks off. Just prefix the command you want cron to run like so: sleep $(jot -r 1 1 900) command to run If you like, replace 900 with some other number to change the upper bound on the number of seconds to delay. portsnap has a cron command that does this. ___ 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: When Is The Ports Tree Going To Be Updated?
So is portsnap cron update and portsnap fetch update doing the same thing? Whichever way, it sounds like I need an initial run of portsnap extract before putting this in crontab. From scratch, you need to portsnap fetch extract to establish your ports directory. After that you either use portsnap fetch update to interactively update or use portsnap cron update for a cron script. Fetch and Cron are identical except Cron adds a randomized time delay so as not to fire off EXACTLY at the time you set. This helps prevent everyone and their brother nailing the update server exactly at midnight every night, but rather spread it out a few minutes. Do NOT use a randomizer on your cron timer with portsnap cron or you will be double randomizing and wondering why it seems to never be updating sometimes. ___ 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: When Is The Ports Tree Going To Be Updated?
Tim Daneliuk tundra at tundraware.com writes: ... One wonders if using svn to keep the ports tree up-to-date might not be simpler, and perhaps, more reliable ... As managed by portsnap: $ du -hs /usr/ports/ 850M/usr/ports/ As managed by svn (it took much longer to checkout/download it by comparison): $ du -hs /usr/local/ports/ 1.4G/usr/local/ports/ $ du -hs /usr/local/ports/.svn/ 702M/usr/local/ports/.svn/ One thing about svn is that it is a developer's tool, with its own commands set (that should never be mixed with UNIX commands w/r to dir/file manipulation), and that should not be expected to be learned by non-devs. For that reasons alone the portsnap-managed ports repo is more generic, flexible to be handled by user and add-on apps/utilities, looks like more efficient without that svn overhead resulting from its requirements and characteristics as a source control system. But, svn offers to a user a unique view into ports repo, e.g. history, logs, info, attributes, etc. jb ___ 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: When Is The Ports Tree Going To Be Updated?
On 26/11/2012 19:17, Warren Block wrote: It can be downloaded with 'make fetchindex', or built in place with 'make index' (slow--I think Mr. Seaman has a Perl version that's probably much faster). That's Dr Seaman if you're going to insist on being formal. Most people call me Matthew. And, yes I do have some perl code for index building. It's only faster on average because it understands how to do incremental updates. Just building an index from scratch is actually a bit slower than 'make index' Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
When Is The Ports Tree Going To Be Updated?
After the recent security scare, I know the ports tree was temporarily frozen. Does anyone know when it will again be updates. I just upgraded to 9.1-PRE and need to rebuild Firefox Thunderbird against the new libraries and ... they're broken, marked as security hazards... TIA, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: When Is The Ports Tree Going To Be Updated?
On 25/11/2012 23:10, Tim Daneliuk wrote: After the recent security scare, I know the ports tree was temporarily frozen. Does anyone know when it will again be updates. I just upgraded to 9.1-PRE and need to rebuild Firefox Thunderbird against the new libraries and ... they're broken, marked as security hazards... It's been being updated normally since near enough a week ago. Normally means subject to the pre-9.1-RELEASE restrictions on sweeping changes as is usual at this point in a release cycle. FireFox 17 and Thunderbird 17 updates were committed to ports on 20th November. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: When Is The Ports Tree Going To Be Updated?
On 11/25/2012 05:25 PM, Matthew Seaman wrote: On 25/11/2012 23:10, Tim Daneliuk wrote: After the recent security scare, I know the ports tree was temporarily frozen. Does anyone know when it will again be updates. I just upgraded to 9.1-PRE and need to rebuild Firefox Thunderbird against the new libraries and ... they're broken, marked as security hazards... It's been being updated normally since near enough a week ago. Normally means subject to the pre-9.1-RELEASE restrictions on sweeping changes as is usual at this point in a release cycle. FireFox 17 and Thunderbird 17 updates were committed to ports on 20th November. Cheers, Matthew Hmmm, something is amiss: [root] ~portsnap update Ports tree is already up to date. [root] ~cd /usr/ports/www/firefox [root] /usr/ports/www/firefoxmake === firefox-16.0.2,1 has known vulnerabilities: Affected package: firefox-16.0.2,1 Type of problem: mozilla -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/d23119df-335d-11e2-b64c-c8600054b392.html = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr1/ports/www/firefox. ** [build] Error code 1 Stop in /usr1/ports/www/firefox. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: When Is The Ports Tree Going To Be Updated?
On Sunday 25 November 2012 17:30:15 Tim Daneliuk wrote: On 11/25/2012 05:25 PM, Matthew Seaman wrote: On 25/11/2012 23:10, Tim Daneliuk wrote: After the recent security scare, I know the ports tree was temporarily frozen. Does anyone know when it will again be updates. I just upgraded to 9.1-PRE and need to rebuild Firefox Thunderbird against the new libraries and ... they're broken, marked as security hazards... It's been being updated normally since near enough a week ago. Normally means subject to the pre-9.1-RELEASE restrictions on sweeping changes as is usual at this point in a release cycle. FireFox 17 and Thunderbird 17 updates were committed to ports on 20th November. Cheers, Matthew Hmmm, something is amiss: [root] ~portsnap update Ports tree is already up to date. [root] ~cd /usr/ports/www/firefox [root] /usr/ports/www/firefoxmake === firefox-16.0.2,1 has known vulnerabilities: Affected package: firefox-16.0.2,1 Type of problem: mozilla -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/d23119df-335d-11e2-b64c-c8600054b392.html = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr1/ports/www/firefox. ** [build] Error code 1 Stop in /usr1/ports/www/firefox. I use portsnap fetch update and it works... Mitja http://www.redbubble.com/people/lumiwa ___ 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: When Is The Ports Tree Going To Be Updated?
On 11/25/2012 06:56 PM, ajtiM wrote: On Sunday 25 November 2012 17:30:15 Tim Daneliuk wrote: On 11/25/2012 05:25 PM, Matthew Seaman wrote: On 25/11/2012 23:10, Tim Daneliuk wrote: After the recent security scare, I know the ports tree was temporarily frozen. Does anyone know when it will again be updates. I just upgraded to 9.1-PRE and need to rebuild Firefox Thunderbird against the new libraries and ... they're broken, marked as security hazards... It's been being updated normally since near enough a week ago. Normally means subject to the pre-9.1-RELEASE restrictions on sweeping changes as is usual at this point in a release cycle. FireFox 17 and Thunderbird 17 updates were committed to ports on 20th November. Cheers, Matthew Hmmm, something is amiss: [root] ~portsnap update Ports tree is already up to date. [root] ~cd /usr/ports/www/firefox [root] /usr/ports/www/firefoxmake === firefox-16.0.2,1 has known vulnerabilities: Affected package: firefox-16.0.2,1 Type of problem: mozilla -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/d23119df-335d-11e2-b64c-c8600054b392.html = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr1/ports/www/firefox. ** [build] Error code 1 Stop in /usr1/ports/www/firefox. I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: When Is The Ports Tree Going To Be Updated?
On Sun, 25 Nov 2012, Matthew Seaman wrote: On 25/11/2012 23:10, Tim Daneliuk wrote: After the recent security scare, I know the ports tree was temporarily frozen. Does anyone know when it will again be updates. I just upgraded to 9.1-PRE and need to rebuild Firefox Thunderbird against the new libraries and ... they're broken, marked as security hazards... It's been being updated normally since near enough a week ago. Normally means subject to the pre-9.1-RELEASE restrictions on sweeping changes as is usual at this point in a release cycle. FireFox 17 and Thunderbird 17 updates were committed to ports on 20th November. Hmm. Is the index file being rebuilt? With FF16 installed, and 17 in the port directory, portsdb -Fu portversion -vl'' shows nothing to update. After 'make index', it does show. ___ 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: When Is The Ports Tree Going To Be Updated?
On 26/11/2012 00:59, Tim Daneliuk wrote: I use portsnap fetch update and it works... Ah, maybe that was the problem. That works for me as well. Ummm... how long have you been using portsnap? If you haven't been running 'portsnap fetch' or 'portsnap cron' then you won't have received any updates to your ports tree, ever. This is all explained quite clearly in the portsnap(8) man page. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: how to correct corrupted ports tree?
On Fri, 16 Nov 2012 21:56:21 -0700, Gary Aitken wrote: I don't see a way to force refetch of the actual ports files like distinfo when portsnap thinks the port is up to date. You cansolve the problem of few per-file mismatches by using the traditional CVS approach of updating the ports tree. Only files not matching the current (on-server) content will be updated. For example, if you can predict in which categories errors appear, only update those. Let's assume the problem you experience is only in the ports base directory. Create a file /etc/sup/ports.sup with the following content: *default host=cvsup.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-base You can use ports-lang to update the lang category only, or ports-all for the whole tree. Note that incorporating all those small deltas may take some time! An example file with all categories can be found here: /usr/share/examples/cvsup/ports-supfile Then add this to /etc/make.conf: SUP_UPDATE= yes SUP=/usr/bin/csup SUPFLAGS= -L 2 SUPHOST=cvsup.freebsd.org PORTSSUPFILE= /etc/sup/ports.sup Maybe choose a near mirror for better performance. Now do this: # cd /usr/ports # make update Now according to this example, the base files for /usr/ports will be checked for changes and (being different) will be updated. Also note that this approach sometimes is more current than using portsnap. There might be deltas in the CVS ports tree already that might not be yet in the most current ports snapshot. However, this is an old-fashioned approach; I'm not sure for how long it will work. :-) See man 5 make.conf for details, as well as man 7 ports. -- 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: how to correct corrupted ports tree?
On Sat, Nov 17, 2012 at 11:02 AM, Polytropon free...@edvax.de wrote: On Fri, 16 Nov 2012 21:56:21 -0700, Gary Aitken wrote: I don't see a way to force refetch of the actual ports files like distinfo when portsnap thinks the port is up to date. You cansolve the problem of few per-file mismatches by using the traditional CVS approach of updating the ports tree. Only files not matching the current (on-server) content will be updated. CVSup/csup is deprecated now and shouldn't be used anymore: http://www.freebsd.org/news/2012-compromise.html We should stop advertizing it as a way to update the ports tree. svn or portsnap is the way to go now. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: how to correct corrupted ports tree?
On Sun, 18 Nov 2012 05:57:40 +0100, Bernt Hansson wrote: 2012-11-18 05:14, Bernt Hansson skrev: There is a readme file too. ftp://ftp.sunet.se/pub/FreeBSD/ports/ports/README.TXT Which mentions the evil cvsup... :-) -- 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
how to correct corrupted ports tree?
so, after updating bios, repartitioning, etc,
things seem to be stable, modulo the following:
decided to rebuild ports for peace of mind,
but my basic ports tree is hosed:
# portmaster -t --clean-distfiles
...
/usr/ports/Mk/bsd.php.mk, line 335: Malformed conditional
(${_USE_PHP_VER${PHP_VER}:Myes} != )
...
make: fatal errors encountered -- cannot continue
=== No DISTINFO_FILE in /usr/ports/lang/php4-extensions
Makefile, line 20: Could not find
/usr/ports/mail/enigmail-thunderbird3/../enigmail/Makefile
make: fatal errors encountered -- cannot continue
Sure enough:
# ls /usr/ports/lang/php4-extensions
CVS Makefilepkg-descr
I didn't see anything in the handbook about how to get the ports tree itself
back to a sane condition. Do I have to blow the whole thing away and do a
fresh extract? I don't see a way to force refetch of the actual ports files
like distinfo when portsnap thinks the port is up to date.
Gary
___
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: how to correct corrupted ports tree?
On 17/11/2012 15:26, Gary Aitken wrote: decided to rebuild ports for peace of mind, but my basic ports tree is hosed: I didn't see anything in the handbook about how to get the ports tree itself back to a sane condition. Do I have to blow the whole thing away and do a fresh extract? I don't see a way to force refetch of the actual ports files like distinfo when portsnap thinks the port is up to date. portsnap extract will always install the entire tree, if you have made any modifications they will be overwritten, but new ports folders you have added should remain, sometimes this can also cause old folders to be left behind. Worst case is to delete the existing /usr/ports and extract a clean set. Another option is partial extraction - portsnap extract lang/php5-extensions will extract just the one port portsnap extract lang/php5 will match all lang ports starting with php5 portsnap extract lang will extract all the lang ports I think that you will find your issue comes from the fact that all the php4 ports have been deleted - you seem to have some old folders left behind. Could be from extracting over an existing cvs checkout. Maybe you want a clean start. If you still have php4 installed then you should be able to use portmaster -o lang/php5-extensions lang/php4-extensions to get it to update with the new version find /usr/ports -type d -and -name php4* | xargs rm -R will delete any remaining php4 folders find /usr/ports -name CVS | xargs rm -R will remove all the cvs garbage left behind. ___ 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
Updating ports tree with subversion behind an http proxy server
I am working on switching from updating my systems with csup to subversion, for the systems I have behind a proxy server. When I was using csup, I used an SSH connection, tunneling the 5999 port through the proxy server. Now that I am looking at subversion, I have found the ~/.subverison/servers file, edited the [global] section removed the comment # from the front of the http-proxy-host and http-proxy-port lines, and added the correct values. Realizing I may still have to add some configuration settings to allow the subversion http methods through to the proxy, I went ahead and tried to run a test check out command. However it doesn't try to hit the proxy server, I just get an immediate no route to host error returned. I know the server has access to the proxy, I was able to use pkg_add with the necessary environment variables to add subversion to this system. The system is a fresh clean install of FreeBSD 9.0-release, with only the packages added for subversion. Looking at the proxy server logs the check out doesn't log anything, which leads me to believe that svn isn't reading its configuration file, or is simply ignoring the http-proxy-host and http-proxy-port lines. Has anyone setup one of their FreeBSD systems to use subversion behind an http proxy, and know what I am missing? -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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: Updating ports tree with subversion behind an http proxy server
On 2012-10-05 10:16, dweimer wrote: I am working on switching from updating my systems with csup to subversion, for the systems I have behind a proxy server. When I was using csup, I used an SSH connection, tunneling the 5999 port through the proxy server. Now that I am looking at subversion, I have found the ~/.subverison/servers file, edited the [global] section removed the comment # from the front of the http-proxy-host and http-proxy-port lines, and added the correct values. Realizing I may still have to add some configuration settings to allow the subversion http methods through to the proxy, I went ahead and tried to run a test check out command. However it doesn't try to hit the proxy server, I just get an immediate no route to host error returned. I know the server has access to the proxy, I was able to use pkg_add with the necessary environment variables to add subversion to this system. The system is a fresh clean install of FreeBSD 9.0-release, with only the packages added for subversion. Looking at the proxy server logs the check out doesn't log anything, which leads me to believe that svn isn't reading its configuration file, or is simply ignoring the http-proxy-host and http-proxy-port lines. Has anyone setup one of their FreeBSD systems to use subversion behind an http proxy, and know what I am missing? Never mind, turns out I was just doing something stupid, had to use svn co http:// instead of svn co svn://... -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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
Scalable Opengroupware (SOGo) in FreeBSD ports tree
Hello, I am thinking about creating a port for SOGo[1]. Is there already someone working on it? Kind regards, Matthias [1] http://www.sogo.nu/english.html -- Matthias Petermann matth...@d2ux.net ___ 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: Scalable Opengroupware (SOGo) in FreeBSD ports tree
On Mon, Sep 10, 2012 at 10:55:22PM +0200, Matthias Petermann wrote: Hello, I am thinking about creating a port for SOGo[1]. Is there already someone working on it? Kind regards, Matthias [1] http://www.sogo.nu/english.html -- Matthias Petermann matth...@d2ux.net ___ freebsd-po...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I have done: http://people.freebsd.org/~bapt/sogo.tar.gz and http://people.freebsd.org/~bapt/sope.tar.gz One year ago. I have given up working on it :) Feel free to use it, or start from scratch. Regards, Bapt pgpAWxQRpyWPx.pgp Description: PGP signature
prune ports tree?
Is it possible to specify that parts of the ports tree should never be used? ___ 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: prune ports tree?
On 8 June 2012 23:06, Gary Aitken free...@dreamchaser.org wrote: Is it possible to specify that parts of the ports tree should never be used? yes, but don't do it. the ports tree needs to be complete to be guaranteed to function. -- Eitan Adler ___ 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: prune ports tree?
On Sat, 09 Jun 2012 00:06:39 -0600, Gary Aitken wrote: Is it possible to specify that parts of the ports tree should never be used? How do you want to understand by parts and not used? The easiest way to not use some part of the ports tree is to remove that part. You can do that by manually deleting the port(s) and even omitting them when updating your ports tree. If you use csup, you can make /etc/sup/ports.sup like this: Don't use ports-all, but only list the categories you want to have updated. This works category-wise. You'll find examples in /usr/share/examples/cvsup/ports-supfile which you can use as a template for your own configuration file. An example of /etc/sup/ports.sup could look like this: *default host=cvsup.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-base ports-accessibility #ports-arabic ports-archivers [ ... list shortened ... ] ports-x11-servers ports-x11-themes ports-x11-toolkits ports-x11-wm Only the listed ports categories will be updated. Then you can add this to /etc/make.conf: SUP=/usr/bin/csup --- SUP_UPDATE= /usr/bin/csup --- SUPFLAGS= -L 2--- SUPHOST=cvsup.freebsd.org SUPFILE=/etc/sup/stable.sup PORTSSUPFILE= /etc/sup/ports.sup --- DOCSUPFILE= /etc/sup/doc.sup DOC_LANG= en_US.ISO8859-1 de_DE.ISO8859-1 The important lines are marked with a ---. Now you can do this: # cd /usr/ports # make update and you'll get the latest ports tree _excluding_ what you have already removed. You can also use /usr/ports/.cvsignore to specify the directories csup should ignore; defaults are distfiles and packages. You can list offending ports here. This approach does _not_ work well when using portsnap. From the portsnap.conf manpage: Note that operating with an incomplete ports tree is not supported and may cause unexpected results. -- 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: prune ports tree?
On 8 June 2012 23:21, Polytropon free...@edvax.de wrote: On Sat, 09 Jun 2012 00:06:39 -0600, Gary Aitken wrote: Is it possible to specify that parts of the ports tree should never be used? This approach does _not_ work well when using portsnap. From the portsnap.conf manpage: Note that operating with an incomplete ports tree is not supported and may cause unexpected results. Note that the issue of incomplete ports trees has nothing to do with portsnap - it is unsupported no matter how you obtain ports. -- Eitan Adler ___ 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: prune ports tree?
Gary Aitken wrote: Is it possible to specify that parts of the ports tree should never be used? Yes. Although as others pointed out it depend quite what you mean by that :-) Example setenv DUDS SomeEndPortToSkip_eg_ghostview One could also do setenv DUDS `printenv DUDS` vietnamese chinese ; make fetch if for instance you wanted to fetch most but not all distiles It prevents a recusion into SUBDIR (either into the 30 main ports/ dirs, or the 20,000+ 2nd level dirs. How I find DUDS useful: When I do an upgrade, I copy (using my shell http://berklix.com/~jhs/bin/.csh/customise ) about 30 Makefile.local from my personal preference directory http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/jhs/ into /usr/ports/*/Makefile.local Then I let loose a monstrous make with something like cd /usr/ports ;\ nice make BERKLIX_CLIENT=YES \ all install package package-recursive ; bell that takes days always breaks a few times on route, ( using make -k or make -i is a bad idea, as it messes upports that other ports then think are built, but are not - so I avoid -i -k ) Sometimes I dont have time to immediately analyse each breakage, just want topush the compiles on, come back later to debug broken faults, so I then use (with csh setenv DUDS whatever_port_just_broke `printenv DUDS` start the make again. (PS later after most stuff is build I start the truly monster builds eg openoffice etc with eg nice make BERKLIX_AMBITIOUS=YES \ all install package package-recursive ; bell # http://www.berklix.com/~jhs/bin/.sh/bell ) For DUDS other ideas See: vi -c/DUDS /usr/ports/Mk/bsd.port.subdir.mk Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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
ports tree
Hi Would it be stupid idea to have publicly available, mountable (nfs) partition, with full port tree(s)? I think it would be good for systems with low storage space. I know hd space is cheap, but I run over and over to this problem. I don't know how easily it could be done, but some kind of session based temporary write permissions would be good too. To be able to make make install directly from mounted partition. I don't think very many people would need to have local personal copy of ports tree then. So, is this just stupid? ___ 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: ports tree
On 26/05/2012 07:57, Henri Reinikainen wrote: Would it be stupid idea to have publicly available, mountable (nfs) partition, with full port tree(s)? I think it would be good for systems with low storage space. I know hd space is cheap, but I run over and over to this problem. I don't know how easily it could be done, but some kind of session based temporary write permissions would be good too. To be able to make make install directly from mounted partition. I don't think very many people would need to have local personal copy of ports tree then. So, is this just stupid? Not stupid, but certainly impracticable. Remote mounting filesystems over the internet is not going to be anything like scalable, and the bandwidth requirements would be horrid. As an end-user, performance would suck -- inescapably, as you'ld be hit hard by latency. Basically, if you could afford the sort of network connectivity that would make such a setup feasible, then you could easily afford sufficient local storage that you wouldn't want to use a remote mount. Also, forget the idea of *writing* to any such share disk space. The security problems with that just don't bear thinking about. NFS mounting /usr/ports within a local network -- now, that's a completely different kettle of fish. You do need to tweak WRKDIRPREFIX if you're going to have several systems building from the same tree simultaneously, and it's probably going to be more effective for you to use one machine as a central package build server and just install from packages on your limited systems. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: ports tree
from Henri Reinikainen henr...@gmail.com: Would it be stupid idea to have publicly available, mountable (nfs) partition, with full port tree(s)? I think it would be good for systems with low storage space. I know hd space is cheap, but I run over and over to this problem. I don't know how easily it could be done, but some kind of session based temporary write permissions would be good too. To be able to make make install directly from mounted partition. I don't think very many people would need to have local personal copy of ports tree then. So, is this just stupid? What happens if the port a remote user is trying to build and install is updated in the middle of this remote activity? Users of ports tree then must deal with a moving target. Files from two different versions might get mixed together. I think maybe this thread should go to po...@freebsd.org list? Tom ___ 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: ports tree
Would it be stupid idea to have publicly available, mountable (nfs) partition, with full port tree(s)? I think it would be good for systems with low storage space. I know hd space is cheap, but I run over and over to this problem. read only or read write? public read write isn't smart. I don't know how easily it could be done, but some kind of session based temporary write permissions would be good too. To be able to make make install directly from mounted partition. man mount_unionfs I don't think very many people would need to have local personal copy of ports tree then. So, is this just stupid? no. ___ 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: ports tree
On Sat, May 26, 2012 at 4:48 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: Would it be stupid idea to have publicly available, mountable (nfs) partition, with full port tree(s)? I think it would be good for systems with low storage space. I know hd space is cheap, but I run over and over to this problem. read only or read write? public read write isn't smart. I was thinking unionfs kind of temporary layer which keeps physical content separated. Only write changes to memory file system or so.. session end will throw everything into bits heaven (/dev/null). :) I don't know how easily it could be done, but some kind of session based temporary write permissions would be good too. To be able to make make install directly from mounted partition. man mount_unionfs This was good to know. I don't think very many people would need to have local personal copy of ports tree then. So, is this just stupid? no. Is there such environment variables that can be pointed to writeable partition? That sources download and compiles on different partition. Then there is no bandwidth problem since only Makefile kind of files get readed from the server. Well, maybe this idea wont fly. I'm going to buy new hd anyways. :) Thanks anyways! ___ 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: ports tree
This was good to know. as others told there is smarter way to do this set WRKDIRPREFIX to somewhere else. no. Is there such environment variables that can be pointed to writeable partition? That sources download and compiles on different partition. Then there is no bandwidth problem since only Makefile kind of files get readed from the server. WRKDIRPREFIX solves work directory. if you properly regulate access rights and YOU administer that machines, i would do NFS mounted read-write /usr/ports/distfiles. ___ 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
is it possible to update ports tree via svn?
I have found: http://wiki.freebsd.org/PortsSVN but trying to update ports tree using svn co svn://svn.freebsd.org/ports says that there is no such repository is it possible to update ports tree via svn? ___ 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 it possible to update ports tree via svn?
2012/4/17 Eugen Konkov kes-...@yandex.ru I have found: http://wiki.freebsd.org/PortsSVN I believe this is just a proposal, and work is not yet finished. but trying to update ports tree using svn co svn://svn.freebsd.org/ports svn.freebsd.org does not have a ports tree in svn yet, per the PortsSVN page, a demo(?) server is available, I have tested the following, and it works as expected svn checkout http://svn.chruetertee.ch/ports/trunk/ says that there is no such repository is it possible to update ports tree via svn? ___ 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 -- regards, matt ___ 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: rsync and the ports tree
Sounds like a well-thought out backup strategy. I've started to use your methods here, and I'm building ports I need at the same time, but the wireless here is not password protected so is incredibly slow as there are lots of leaches on the system. But while I'm plodding along, I have a few more questions: On Wed, Oct 26, 2011 at 8:07 AM, C. P. Ghost cpgh...@cordula.ws wrote: On Wed, Oct 26, 2011 at 12:39 PM, Peter Kryszkiewicz tundra2b...@gmail.com wrote: I have several machines installed in my temporary location and only my laptop gets the internet through wireless. So far I've been building ports on the other machines by rsync'ing the distfiles from the laptop as I need them (all machines have the same FreeBSD 8.2 installed). The problem comes after I did a 'portupgrade -a' on the laptop. To ensure the other ports trees are in sync, can I rsync the /usr/ports directory to the other machines? Since some of them are different architectures (amd64 multicore for instance) I ran into situations where the distfiles are different (for gcc for example). First of all, rsync is working perfectly if you want to distribute /usr/ports/distfiles, /usr/ports to your internal machines, even when they are not of the same architecture. I'm doing this with a BIG farm of servers running i386, amd64, and sparc64 for a long, long time. You only need to make sure to rsync the *union* of your /usr/ports/distfiles directories, or else it won't work. Say, on amd64 you have /usr/ports/distfiles/some-distfile-for-amd64-only.tar.bz2 and on i386 you have /usr/ports/distfiles/some-distfile-for-i386-only.tar.bz2 Yes, that happens every now and then. So you have to rsync both ways, so that you end up with /usr/ports/distfiles/some-distfile-for-amd64-only.tar.bz2 /usr/ports/distfiles/some-distfile-for-i386-only.tar.bz2 on both i386 and amd64 machines. I've done that, it works well especially for the architecture differences. gcc requires an additional distfile for the amd64 build). The catch is: look out for rsync's --delete flag! When some port managers delete old/stale distfiles, they may also delete distfiles for the *other* arches because they (rightly) think they are not needed here... and when you then rsync with --delete, that would (wrongly) propagate such deletes to those arches, and you end up with missing distfiles on the targets. Since I have more than just two arches, I use a slightly different 2-layer workflow: 0. I have 3 servers that are allowed to fetch files from the outside: i386-master, amd64-master, sparc64-master. and a whole bunch of i386-slave-NNN, amd64-slave-NNN and sparc64-slave-NNN machines that would duplicate from their relative masters via rsync. On all -master(s), I keep $DISTFILES outside of /usr/ports (on /usr/local/distfiles, with a symbolic link in /usr/ports /usr/ports/distfiles - /usr/local/distfiles) Initial update of i386-master, as usual: 1. On i386-master, csup /usr/ports. Run portmaster as usual to upgrade everything. This may delete old stale distfiles and non-i386-distfiles. This may fetch additional generic and i386-specific distfiles. Copy the new /usr/ports (without distfiles) to the other arch masters: 2. rsync -av --delete i386-master:/usr/ports to amd64-master and sparc64-master. CAUTION: Use --delete is okay, but only because distfiles are not under /usr/ports, so as not to nuke non-i386-specific distfiles of the other arches. Copy i386-master's NEW distfiles to the other arch masters: 3. rsync -av i386-master:/usr/local/distfiles to amd64-master and sparc64-master. BEWARE: Don't use --delete here! Do this to copy new generic distfiles (and i386) from the i386-master build to amd64-master and sparc64-master. Update amd64-master and sparc64-master's ports as usual: 4. On amd64-master, run portmaster as usual to upgrade everything. This may delete old stale distfiles and non-amd64-distfiles. This may fetch additional (generic and) amd64-specific-distfiles. 5. On sparc64-master, run portmaster as usual to upgrade everything. This may delete old stale distfiles and non-sparc64-distfiles. This may fetch additional (generic and) sparc64-specific-distfiles. At this point, i386-master, amd64-master and sparc64-master are fully updated, and their /usr/local/distfiles directories are up to date w.r.t. their specific architectures. Now, copy everything from the masters to the slaves: 6. On every i386-slave-NNN, rsync -av --delete: /usr/ports, /usr/local (including /usr/local/distfiles), /var/db/pkg, /var/db/ports from i386-master. 7. On every amd64-slave-NNN, rsync -av --delete: /usr/ports, /usr/local (including /usr/local/distfiles) /var/db/pkg, /var/db/ports from amd64-master. I can see the need to sync /var/db/ports, but isn't /var/db/pkg specific to each machine? Same with /usr/local/distfiles (as far as
rsync and the ports tree
I have several machines installed in my temporary location and only my laptop gets the internet through wireless. So far I've been building ports on the other machines by rsync'ing the distfiles from the laptop as I need them (all machines have the same FreeBSD 8.2 installed). The problem comes after I did a 'portupgrade -a' on the laptop. To ensure the other ports trees are in sync, can I rsync the /usr/ports directory to the other machines? Since some of them are different architectures (amd64 multicore for instance) I ran into situations where the distfiles are different (for gcc for example). If not rsync, what is the best way to keep multiple ports trees on different hardware in sync, assuming everything runs FreeBSD 8.2? regards, Peter Kryszkiewicz ___ 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: rsync and the ports tree
On Wed, Oct 26, 2011 at 12:39 PM, Peter Kryszkiewicz tundra2b...@gmail.com wrote: I have several machines installed in my temporary location and only my laptop gets the internet through wireless. So far I've been building ports on the other machines by rsync'ing the distfiles from the laptop as I need them (all machines have the same FreeBSD 8.2 installed). The problem comes after I did a 'portupgrade -a' on the laptop. To ensure the other ports trees are in sync, can I rsync the /usr/ports directory to the other machines? Since some of them are different architectures (amd64 multicore for instance) I ran into situations where the distfiles are different (for gcc for example). The distfiles are not different between architectures. Rsyncing /usr/ports works fine. But if you will bump into problems if you also sync /usr/ports/packages and you have different archs (i386 vs amd64 for instance). -- chs, ___ 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: rsync and the ports tree
On Wed, Oct 26, 2011 at 12:39 PM, Peter Kryszkiewicz tundra2b...@gmail.com wrote: I have several machines installed in my temporary location and only my laptop gets the internet through wireless. So far I've been building ports on the other machines by rsync'ing the distfiles from the laptop as I need them (all machines have the same FreeBSD 8.2 installed). The problem comes after I did a 'portupgrade -a' on the laptop. To ensure the other ports trees are in sync, can I rsync the /usr/ports directory to the other machines? Since some of them are different architectures (amd64 multicore for instance) I ran into situations where the distfiles are different (for gcc for example). First of all, rsync is working perfectly if you want to distribute /usr/ports/distfiles, /usr/ports to your internal machines, even when they are not of the same architecture. I'm doing this with a BIG farm of servers running i386, amd64, and sparc64 for a long, long time. You only need to make sure to rsync the *union* of your /usr/ports/distfiles directories, or else it won't work. Say, on amd64 you have /usr/ports/distfiles/some-distfile-for-amd64-only.tar.bz2 and on i386 you have /usr/ports/distfiles/some-distfile-for-i386-only.tar.bz2 Yes, that happens every now and then. So you have to rsync both ways, so that you end up with /usr/ports/distfiles/some-distfile-for-amd64-only.tar.bz2 /usr/ports/distfiles/some-distfile-for-i386-only.tar.bz2 on both i386 and amd64 machines. The catch is: look out for rsync's --delete flag! When some port managers delete old/stale distfiles, they may also delete distfiles for the *other* arches because they (rightly) think they are not needed here... and when you then rsync with --delete, that would (wrongly) propagate such deletes to those arches, and you end up with missing distfiles on the targets. Since I have more than just two arches, I use a slightly different 2-layer workflow: 0. I have 3 servers that are allowed to fetch files from the outside: i386-master, amd64-master, sparc64-master. and a whole bunch of i386-slave-NNN, amd64-slave-NNN and sparc64-slave-NNN machines that would duplicate from their relative masters via rsync. On all -master(s), I keep $DISTFILES outside of /usr/ports (on /usr/local/distfiles, with a symbolic link in /usr/ports /usr/ports/distfiles - /usr/local/distfiles) Initial update of i386-master, as usual: 1. On i386-master, csup /usr/ports. Run portmaster as usual to upgrade everything. This may delete old stale distfiles and non-i386-distfiles. This may fetch additional generic and i386-specific distfiles. Copy the new /usr/ports (without distfiles) to the other arch masters: 2. rsync -av --delete i386-master:/usr/ports to amd64-master and sparc64-master. CAUTION: Use --delete is okay, but only because distfiles are not under /usr/ports, so as not to nuke non-i386-specific distfiles of the other arches. Copy i386-master's NEW distfiles to the other arch masters: 3. rsync -av i386-master:/usr/local/distfiles to amd64-master and sparc64-master. BEWARE: Don't use --delete here! Do this to copy new generic distfiles (and i386) from the i386-master build to amd64-master and sparc64-master. Update amd64-master and sparc64-master's ports as usual: 4. On amd64-master, run portmaster as usual to upgrade everything. This may delete old stale distfiles and non-amd64-distfiles. This may fetch additional (generic and) amd64-specific-distfiles. 5. On sparc64-master, run portmaster as usual to upgrade everything. This may delete old stale distfiles and non-sparc64-distfiles. This may fetch additional (generic and) sparc64-specific-distfiles. At this point, i386-master, amd64-master and sparc64-master are fully updated, and their /usr/local/distfiles directories are up to date w.r.t. their specific architectures. Now, copy everything from the masters to the slaves: 6. On every i386-slave-NNN, rsync -av --delete: /usr/ports, /usr/local (including /usr/local/distfiles), /var/db/pkg, /var/db/ports from i386-master. 7. On every amd64-slave-NNN, rsync -av --delete: /usr/ports, /usr/local (including /usr/local/distfiles) /var/db/pkg, /var/db/ports from amd64-master. 8. On every sparc64-slave-NNN, rsync -av --delete: /usr/ports, /usr/local (including /usr/local/distfiles) /var/db/pkg, /var/db/ports from sparc64-master. You may also need to update entries in /etc and /usr/local/etc on the slaves. If not rsync, what is the best way to keep multiple ports trees on different hardware in sync, assuming everything runs FreeBSD 8.2? regards, Peter Kryszkiewicz -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: rmconfig from all ports tree
--On Thursday, July 22, 2010 02:21:59 +0200 claudiu vasadi claudiu.vas...@gmail.com wrote: Hi Greg, Thanks for the rmconfig-recursive. I did not know about it. Nor did I. And it begs the question - is there a way to find out what all the make targets are in /usr/ports? Is this documented anywhere? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson ___ 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: rmconfig from all ports tree
On Thu, 22 Jul 2010 12:15:10 -0500, Paul Schmehl pschmehl_li...@tx.rr.com wrote: And it begs the question - is there a way to find out what all the make targets are in /usr/ports? Is this documented anywhere? Yes, man 7 ports, section TARGETS. -- 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: rmconfig from all ports tree
On 7/22/10 1:15 PM, Paul Schmehl wrote: --On Thursday, July 22, 2010 02:21:59 +0200 claudiu vasadi claudiu.vas...@gmail.com wrote: Hi Greg, Thanks for the rmconfig-recursive. I did not know about it. Nor did I. And it begs the question - is there a way to find out what all the make targets are in /usr/ports? Is this documented anywhere? Hi, This is documented in ports/Mk/bsd.port.mk - look for the string Default targets and their behaviors:. Regards, -- Glen Barber ___ 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
rmconfig from all ports tree
hello guys, is there a way to do make rmconfig for all ports at once ? ___ 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: rmconfig from all ports tree
one solution I just created would be: for i in `find /usr/ports/ -type directory -print`; do `cd $i make rmconfig`;done but I am wondering if there is a official way. man portsclean did not give me any options to do it. Another thing would be to make rmconfig in all dir's that are required to be installed by a particular meta-port, for instance kde/gnome/xfce. ___ 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: rmconfig from all ports tree
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 claudiu vasadi wrote: one solution I just created would be: for i in `find /usr/ports/ -type directory -print`; do `cd $i make rmconfig`;done but I am wondering if there is a official way. man portsclean did not give me any options to do it. Another thing would be to make rmconfig in all dir's that are required to be installed by a particular meta-port, for instance kde/gnome/xfce. Hi Claudiu, You can use one of these two targets: rmconfig - Remove the options config for this port. rmconfig-recursive - Remove the options config for this port and all dependencies. Or, if you want to use a big hammer and remove all configs for all ports, use: find /var/db/ports -type f -name options -print | xargs rm Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMR40E0sRouByUApARAiAxAJ4tTVUwd1HdU1ZqZsTZdpmmHfK5swCdG4CL OG68m0jqHWogajdG0rn/ZSU= =ns+l -END PGP SIGNATURE- ___ 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: rmconfig from all ports tree
On 07/21/2010 04:38 PM, claudiu vasadi wrote: hello guys, is there a way to do make rmconfig for all ports at once ? The fastest way is: rm -rf /var/db/ports/* but this breaks the abstraction. The right thing to do would be to make rmconfig in each port directory. -- Benjamin Lee http://www.b1c1l1.com/ signature.asc Description: OpenPGP digital signature
Re: rmconfig from all ports tree
Hi Greg, Thanks for the rmconfig-recursive. I did not know about it. ___ 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: rmconfig from all ports tree
in the meantime I wrote the following quick script: #!/bin/sh # Create a list of all dir's find /usr/ports/ -depth 2 -type directory -print ports_structure # for each discovered dir, cd into it and do rmconfig file=ports_structure while read dr1 do cd $dr1;make rmconfig done$file very simple script if you ask me. tested and working. Any suggestions/ideas/opinions are welcomed. ___ 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: rmconfig from all ports tree
Quoth claudiu vasadi on Thursday, 22 July 2010: in the meantime I wrote the following quick script: #!/bin/sh # Create a list of all dir's find /usr/ports/ -depth 2 -type directory -print ports_structure # for each discovered dir, cd into it and do rmconfig file=ports_structure while read dr1 do cd $dr1;make rmconfig done$file very simple script if you ask me. tested and working. Any suggestions/ideas/opinions are welcomed. ___ Since you asked, you don't really need to go to a file: find /usr/ports/ -depth 2 -type directory -print | while read dr1 do cd $dr1;make rmconfig done -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpRU5W8vo11k.pgp Description: PGP signature
Missing link in ports tree
Dear Sirs, I have just installed FreeBSD 7.2-Release from a dvd image I downloaded, with KDE windows manager. I immidiately cvsup'ed my ports-supfile, completeing with make fetchindex from /usr/ports. When trying to install hplip from /usr/ports/print, I am told to update several qt4 ports from version 4.5.2 to 4.5.3. The only trouble is: qt4-dbus-4.5.3 is not to be found in my ports tree, and I can not find the source-files on the net either. For instance, from this server list: http://www.freebsd.org/ports/devel.html, it is clear that there should be such a port, but the files are nowhere to be found. I have managed to download qt-x11-opensource-src-4.5.3.tar.gz now, so I will try to install the complete qt4-4.5.3 port and hope dbus is to be found there. I just wanted to let you know in case this is a minor bug to be dealt with outside my machine... :-p Best regards, Sverre Vegard Pettersen ___ 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: Missing link in ports tree
Sverre Vegard Pettersen wrote: Dear Sirs, I have just installed FreeBSD 7.2-Release from a dvd image I downloaded, with KDE windows manager. I immidiately cvsup'ed my ports-supfile, completeing with make fetchindex from /usr/ports. When trying to install hplip from /usr/ports/print, I am told to update several qt4 ports from version 4.5.2 to 4.5.3. The only trouble is: qt4-dbus-4.5.3 is not to be found in my ports tree, and I can not find the source-files on the net either. % pkg_info -ox qt4-dbus Information for qt4-dbus-4.5.3: Origin: devel/dbus-qt4 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
Re: eclipse install (broken ports tree)
On Wed, 2009-08-05 at 14:50 -0800, Mel Flynn wrote: On Wednesday 05 August 2009 13:53:22 Coert Waagmeester wrote: I tried it via the ports, but this error keeps popping up: Missing pkg-descr for patch-2.5.9. I believe you have a defective ports tree. You should have the following file: SHA256 (/usr/ports/devel/patch/pkg-descr) = 629097523839c5e305a4115c1b3629029b734166e5ff8f73923812e0149e9912 If you do not, then try updating your ports tree and look for errors/warnings with whatever method you're using. Hi Mel, In /usr/ports/ i deleted everything. Then I ran a portsnap fetch and then portsnap extract and portsnap update. But I still get Missing pkg-descr for dtach-0.8. my shasum on /usr/ports/devel/patch/pkg-descr is the same as yours How can I completely wipe out the ports and start over? Regards, Coert ___ 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: eclipse install (SOLVED broken ports tree)
On Thu, 2009-08-06 at 09:08 +0200, Coert Waagmeester wrote: On Wed, 2009-08-05 at 14:50 -0800, Mel Flynn wrote: On Wednesday 05 August 2009 13:53:22 Coert Waagmeester wrote: I tried it via the ports, but this error keeps popping up: Missing pkg-descr for patch-2.5.9. I believe you have a defective ports tree. You should have the following file: SHA256 (/usr/ports/devel/patch/pkg-descr) = 629097523839c5e305a4115c1b3629029b734166e5ff8f73923812e0149e9912 If you do not, then try updating your ports tree and look for errors/warnings with whatever method you're using. Hi Mel, In /usr/ports/ i deleted everything. Then I ran a portsnap fetch and then portsnap extract and portsnap update. But I still get Missing pkg-descr for dtach-0.8. my shasum on /usr/ports/devel/patch/pkg-descr is the same as yours How can I completely wipe out the ports and start over? Regards, Coert Hello all, I fixed the ports problem following this: http://lists.freebsd.org/pipermail/freebsd-ports/2006-December/037566.html I have PKGDIR variable exported. ___ 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: eclipse install (SOLVED broken ports tree)
On Thursday 06 August 2009 00:07:33 Coert Waagmeester wrote: I have PKGDIR variable exported. Ack, yeah. Should've thought of that. It's a badly chosen variable name for pkg_add. You could make an alias though: alias pkg_keep='env PKGDIR=/path/to/whatever pkg_add -K' -- Mel ___ 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: the 'make' command in the ports tree
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Polytropon wrote: On Sun, 12 Apr 2009 20:08:21 +0200, dede sserre...@gmail.com wrote: Hello, I'm a long time user of BSDs, and I don't find man pages or documentation on the way I can master the port collection (specialy the fonction of make). Did you try % man ports Don't miss % man portsnap I found this, interesting: http://www.freebsd.org/doc/en/books/handbook/ports-using.html, but some interogations persist. Which are those? I search a command that list all availables variables that afect program installation, [...] Those are usually specifig to the port and are, in most cases, listed in its Makefile. Sometimes, they're documented, e. g. in /usr/ports/multimedia/mplayer/Makefile you'll find a header with explainations for the variables. There may be globally set variables that do have an effect on a specific port. % man make.conf gives a good summary, and have a look at the explainations given in /usr/share/examples/etc/make.conf. [...] and all arguments I can give to the /usr/port/Makefile (I know about 'make search key= and name=' is there another?). Yes, make install, make deinstall, make reinstall, make config, make clean, make distclean, make package are very common ones for the ports. In /usr/ports, you can even use make update to update your ports collection. Could anyone give me some cool addresses to learn on the subject? The FreeBSD Handbook, 4.5 Using the Ports Collection is excellent: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html You mentioned it already. The FAQ, Chapter 7 User Applications, covers other activities: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/applications.html No, you don't really want any of them. The make man page isn't too bad as a reference, but to learn it, what you want is the postscript writeup that comes in FreeBSD's documents, in /usr/share/doc/psc/12.make/paper.ascii.gz. I think that that last directory can be parent to several different versions, depending on what you have PRINTERDEVICE set to, so you could get (say) postscript. Anyhow, whatever shows up at the bottom of that 12.make directory would be all about pmake which is the parent of today's make, and that's a damned good one. If you find things that are not documented enough, simply ask a question here. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknlF1gACgkQz62J6PPcoOkXwgCgmfm+caRmdDgSmp1dDaGTzN/Y m+kAnjlgslpnLaqv/eVblbUwQCesqn2g =cHUb -END PGP SIGNATURE- ___ 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: the 'make' command in the ports tree
At 2009-04-12T20:08:21+02:00, dede wrote: I search a command that list all availables variables that afect program installation, and all arguments I can give to the /usr/port/Makefile `make showconfig' displays all the options available for a port. (I know about 'make search key= and name=' is there another?). The ports(1) man page describes several targets that can be used with a port Makefile. Could anyone give me some cool addresses to learn on the subject? Apart from the above man page, there are the FreeBSD Handbook [Chapter 4] for information aimed at users, and the Porter's Handbook for technical information. HTH, Raghu. -- N. Raghavendra ra...@mri.ernet.in | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. ___ 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: the 'make' command in the ports tree
At 2009-04-13T10:48:51+05:30, N. Raghavendra wrote: The ports(1) man page describes several targets ^ Sorry, that is ports(7). Raghu. -- N. Raghavendra ra...@mri.ernet.in | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. ___ 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
the 'make' command in the ports tree
Hello, I'm a long time user of BSDs, and I don't find man pages or documentation on the way I can master the port collection (specialy the fonction of make). I found this, interesting: http://www.freebsd.org/doc/en/books/handbook/ports-using.html, but some interogations persist. I search a command that list all availables variables that afect program installation, and all arguments I can give to the /usr/port/Makefile (I know about 'make search key= and name=' is there another?). Could anyone give me some cool addresses to learn on the subject? Cordially sserre...@gmail.com ___ 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: the 'make' command in the ports tree
On Sunday 12 April 2009, dede wrote: I search a command that list all availables variables that afect program installation, and all arguments I can give to the /usr/port/Makefile (I know about 'make search key= and name=' is there another?). Could anyone give me some cool addresses to learn on the subject? Check out the ports(7) manual. Regards, Pieter de Goeje ___ 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: the 'make' command in the ports tree
On Sun, 12 Apr 2009 20:08:21 +0200, dede sserre...@gmail.com wrote: Hello, I'm a long time user of BSDs, and I don't find man pages or documentation on the way I can master the port collection (specialy the fonction of make). Did you try % man ports Don't miss % man portsnap I found this, interesting: http://www.freebsd.org/doc/en/books/handbook/ports-using.html, but some interogations persist. Which are those? I search a command that list all availables variables that afect program installation, [...] Those are usually specifig to the port and are, in most cases, listed in its Makefile. Sometimes, they're documented, e. g. in /usr/ports/multimedia/mplayer/Makefile you'll find a header with explainations for the variables. There may be globally set variables that do have an effect on a specific port. % man make.conf gives a good summary, and have a look at the explainations given in /usr/share/examples/etc/make.conf. [...] and all arguments I can give to the /usr/port/Makefile (I know about 'make search key= and name=' is there another?). Yes, make install, make deinstall, make reinstall, make config, make clean, make distclean, make package are very common ones for the ports. In /usr/ports, you can even use make update to update your ports collection. Could anyone give me some cool addresses to learn on the subject? The FreeBSD Handbook, 4.5 Using the Ports Collection is excellent: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html You mentioned it already. The FAQ, Chapter 7 User Applications, covers other activities: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/applications.html If you find things that are not documented enough, simply ask a question here. -- Polytropon From 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: the 'make' command in the ports tree
dede wrote: Hello, I'm a long time user of BSDs, and I don't find man pages or documentation on the way I can master the port collection (specialy the fonction of make). I found this, interesting: http://www.freebsd.org/doc/en/books/handbook/ports-using.html, but some interogations persist. I search a command that list all availables variables that afect program installation, and all arguments I can give to the /usr/port/Makefile (I know about 'make search key= and name=' is there another?). Could anyone give me some cool addresses to learn on the subject? Not sure if I understand your question fully, but this is a great place to learn about different options available when manipulating ports. http://www.freebsd.org/cgi/man.cgi?query=portsapropos=0sektion=0manpath=FreeBSD+7.1-RELEASE+and+Portsformat=html ___ 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
Support for parallel building hits ports tree
Hi, I remember people on this list being interested in parallel builds, so here's the link to my forum post that explains the details of the support that's been added to the ports tree last Sunday: http://forums.freebsd.org/showthread.php?p=17604#post17604 -- Mel ___ 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: ports tree build ignores /etc/make.conf
Anton Shterenlikht me...@bristol.ac.uk writes:
I have:
# uname -srm
FreeBSD 6.4-STABLE alpha
#
In /etc/make.conf I have
.if ${.CURDIR:M*/lang/gcc*}
NOT_FOR_ARCHS=
.endif
However, I get:
# cd /usr/ports/lang/gcc43
# make
=== gcc-4.3.3_20090101 does not run on alpha ia64, while you are running
alpha.
*** Error code 1
Stop in /usr/ports/lang/gcc43.
#
So it seems make ignores NOT_FOR_ARCHS= setting.
When I add this to the gcc43/Makefile directly, build
goes ahead.
What's the problem?
The port's makefile is overriding the setting you put in make.conf.
That variable is intended for use in ports, not by end-users (otherwise,
the port makefile would use a different assignment operator to avoid
overwriting existing settings).
If you really think you can fix the build for that architecture, you
should be modifying the original makefile.
--
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
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
ports tree build ignores /etc/make.conf
I have:
# uname -srm
FreeBSD 6.4-STABLE alpha
#
In /etc/make.conf I have
.if ${.CURDIR:M*/lang/gcc*}
NOT_FOR_ARCHS=
.endif
However, I get:
# cd /usr/ports/lang/gcc43
# make
=== gcc-4.3.3_20090101 does not run on alpha ia64, while you are running
alpha.
*** Error code 1
Stop in /usr/ports/lang/gcc43.
#
So it seems make ignores NOT_FOR_ARCHS= setting.
When I add this to the gcc43/Makefile directly, build
goes ahead.
What's the problem?
many thanks
anton
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233
Fax: +44 (0)117 929 4423
___
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
Can i update ports tree using SVN
Hi, Guys, i've updated the FreeBSD sources from svn.freebsd.org/ and it's speed is very good. i want to know can i update the ports tree through some svn server ? Best Regards. -wsw ___ 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: Can i update ports tree using SVN
On Fri, 19 Dec 2008 15:31:47 +0800, Shaowei Wang (wsw) wsw1w...@gmail.com wrote: Hi, Guys, i've updated the FreeBSD sources from svn.freebsd.org/ and it's speed is very good. i want to know can i update the ports tree through some svn server ? Unfortunately, no. Only the src/ tree has been converted to Subversion. pgpJ024AzKPDU.pgp Description: PGP signature
port math/libgmp4 depends on itself after ports tree upgrade
Perhaps this is portmaster issue, but it seems libgmp4 depends on itself: #portmaster -Btd libgmp [skip] === Recursive 'make config' check complete for math/libgmp4 === Starting build for math/libgmp4 === === Starting check for all dependencies === Gathering dependency list for math/libgmp4 from ports === Starting dependency check === Launching child to update libgmp-4.2.3 to libgmp-4.2.4 libgmp-4.2.3 libgmp-4.2.3 === Port directory: /usr/ports/math/libgmp4 === Starting check for all dependencies === Gathering dependency list for math/libgmp4 from ports === Starting dependency check === Launching child to update libgmp-4.2.3 to libgmp-4.2.4 libgmp-4.2.3 libgmp-4.2.3 libgmp-4.2.3 === Port directory: /usr/ports/math/libgmp4 === Starting check for all dependencies === Gathering dependency list for math/libgmp4 from ports ^C === Build/Install for math/libgmp4 exiting due to signal === Build/Install for math/libgmp4 exiting due to signal === Build/Install for math/libgmp4 exiting due to signal # If I don't abort upgrade the check for dependencies goes in circles, each time increasing the number of self dependencies by one. Anybody else seeing this? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 - End forwarded message - -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD way of installing old version from ports tree
Hi FreeBSD users Currently in /usr/ports/sysutils/syslog-ng there is version syslog-ng 1.6.12. I need version syslog-ng 1.6.5 (the same as in production environment) to test configuration changes. Is there an archive of the ports tree? Whats the FreeBSD way to install this old version integrated in the rest of the system? cheers Simon -- XMPP: [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: FreeBSD way of installing old version from ports tree
Simon Jolle wrote: What is the FreeBSD way to install this old version integrated in the rest of the system? If 1.6.12 was already installed, I would use portdowngrade. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD way of installing old version from ports tree
In response to Simon Jolle [EMAIL PROTECTED]: Hi FreeBSD users Currently in /usr/ports/sysutils/syslog-ng there is version syslog-ng 1.6.12. I need version syslog-ng 1.6.5 (the same as in production environment) to test configuration changes. Is there an archive of the ports tree? Whats the FreeBSD way to install this old version integrated in the rest of the system? Looks through the CVS logs (you can use the web interface or Dan's freshports: http://www.freshports.org/sysutils/syslog-ng/) Find the date of the version you want, then configure your supfile to grab the ports tree from that date. Something like: date=2004.08.28.10.00.00 should get what you want. When cvsup is done running, you'll be able to run make install from the syslog-ng directory to install that version ... assuming that distfile is still readily available. If it's not, you'll have to do some web searches until you find it manually. Some projects are really good about keeping old distfiles around, other are not. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD way of installing old version from ports tree
On Mon, 9 Jun 2008, Bill Moran wrote: In response to Simon Jolle [EMAIL PROTECTED]: Currently in /usr/ports/sysutils/syslog-ng there is version syslog-ng 1.6.12. I need version syslog-ng 1.6.5 (the same as in production environment) to test configuration changes. Is there an archive of the ports tree? Whats the FreeBSD way to install this old version integrated in the rest of the system? Looks through the CVS logs (you can use the web interface or Dan's freshports: http://www.freshports.org/sysutils/syslog-ng/) Find the date of the version you want, then configure your supfile to grab the ports tree from that date. Something like: date=2004.08.28.10.00.00 should get what you want. When cvsup is done running, you'll be able to run make install from the syslog-ng directory to install that version That's pretty much what /usr/ports/ports-mgmt/portdowngrade does, with a little bit of user interface on it. ... assuming that distfile is still readily available. If it's not, you'll have to do some web searches until you find it manually. Some projects are really good about keeping old distfiles around, other are not. And there could be dependency and version issues. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
list files in FreeBSD ports tree package
Hi FreeBSD users I am searching for something similar to Red Hat's rpm -q -l package and Debian's dpkg -L package. cheers Simon -- XMPP: [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: list files in FreeBSD ports tree package
El día Thursday, June 05, 2008 a las 03:35:01PM +0200, Simon Jolle escribió: Hi FreeBSD users I am searching for something similar to Red Hat's rpm -q -l package and Debian's dpkg -L package. cheers Simon Don't know nothing about Red Hat or Debian, but how about $ pkg_info -L stardict-2.4.8_5 or even $ man pkg_info HIH matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ «...una sola vez, que es cuanto basta si se trata de verdades definitivas.» «...only once, which is enough if it has todo with definite truth.» José Saramago, Historia del Cerca de Lisboa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: list files in FreeBSD ports tree package
On 6/5/08, Matthias Apitz [EMAIL PROTECTED] wrote: Don't know nothing about Red Hat or Debian, but how about $ pkg_info -L stardict-2.4.8_5 or even $ man pkg_info HIH matthias Thank you Matthias -- XMPP: [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: list files in FreeBSD ports tree package
The best way to do searches on a BSD system is to use good old 'locate,' or even 'find / -name package.' This will give you a result based on the ports package which you can then add using 'pkg_add -r package name.' Camilo Bono Vince Malum -- Message: 6 Date: Thu, 5 Jun 2008 15:35:01 +0200 From: Simon Jolle Subject: list files in FreeBSD ports tree package To: freebsd-questions@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=UTF-8 Hi FreeBSD users I am searching for something similar to Red Hat's rpm -q -l package and Debian's dpkg -L package. cheers Simon -- XMPP: [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: list files in FreeBSD ports tree package
On Thu, 5 Jun 2008 19:37:42 -0700 (PDT) Camilo Reyes [EMAIL PROTECTED] wrote: The best way to do searches on a BSD system is to use good old 'locate,' or even 'find / -name package.' i think you can also look in /var/db/pkg or do pkg_info | grep WHATEVER if i understood the original post correctly. -- In friendship, prad ... with you on your journey Towards Freedom http://www.towardsfreedom.com (website) Information, Inspiration, Imagination - truly a site for soaring I's ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
rsync'able ports tree instead of csup?
My usual workflow with the ports tree (and to a lesser extent, /usr/src) goes something like this: 1. download ports/src tree from cdrom/ftp site (usually done once) 2. use csup to update to HEAD 3. build The problem is step 2. It takes a very long time for csup to apply the latest changes from the cvsup servers to the tree, even if my previous csup session was only the previous day. IMO, something like rsync would be *way* faster for this task. I know csup is CVS-tags aware and such, but 99% of the time, I'm just tracking HEAD. Would it be a good idea to setup a server that does nothing but csup/cvsup ports, HEAD, and RELENG_7_0, and make that available via rsync? It could be done frequently enough (maybe every 15 minutes) such that most users would be fine with everything but the last 15 minutes. Has anyone done something like this already? thanks, joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync'able ports tree instead of csup?
On 2008-May-13, at 1:27 PM, Joachim Rosenfeld wrote: My usual workflow with the ports tree (and to a lesser extent, /usr/ src) goes something like this: 1. download ports/src tree from cdrom/ftp site (usually done once) 2. use csup to update to HEAD 3. build The problem is step 2. It takes a very long time for csup to apply the latest changes from the cvsup servers to the tree, even if my previous csup session was only the previous day. Have you tried using portsnap? It's a binary snapshot of the ports tree: http://www.freebsd.org/doc/en/books/handbook/portsnap.html Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync'able ports tree instead of csup?
On Tue, 13 May 2008 13:27:05 -0400 Joachim Rosenfeld [EMAIL PROTECTED] wrote: IMO, something like rsync would be *way* faster for this task. Take a look at portsnap. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/portsnap.html Andreas -- GnuPG key : 0x2A573565|http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 pgpBdIab9AdPe.pgp Description: PGP signature
Re: rsync'able ports tree instead of csup?
On Tue, May 13, 2008 at 10:27 AM, Joachim Rosenfeld [EMAIL PROTECTED] wrote: My usual workflow with the ports tree (and to a lesser extent, /usr/src) goes something like this: 1. download ports/src tree from cdrom/ftp site (usually done once) 2. use csup to update to HEAD 3. build The problem is step 2. It takes a very long time for csup to apply the latest changes from the cvsup servers to the tree, even if my previous csup session was only the previous day. IMO, something like rsync would be *way* faster for this task. I know csup is CVS-tags aware and such, but 99% of the time, I'm just tracking HEAD. Would it be a good idea to setup a server that does nothing but csup/cvsup ports, HEAD, and RELENG_7_0, and make that available via rsync? It could be done frequently enough (maybe every 15 minutes) such that most users would be fine with everything but the last 15 minutes. Has anyone done something like this already? thanks, joe man portsnap -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync'able ports tree instead of csup?
On Tue, May 13, 2008 at 1:46 PM, Derek Buttineau [EMAIL PROTECTED] wrote: Have you tried using portsnap? It's a binary snapshot of the ports tree: http://www.freebsd.org/doc/en/books/handbook/portsnap.html Awesome, this is exactly what I was looking for. I don't suppose there is something analagous to portsnap for the source tree? It doesn't matter all that much because I don't update /usr/src all that open, so running csup(1) when a new version comes out is not a terribly big pain. thanks, Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync'able ports tree instead of csup?
On Tue, 13 May 2008 13:27:05 -0400 Joachim Rosenfeld [EMAIL PROTECTED] wrote: My usual workflow with the ports tree (and to a lesser extent, /usr/src) goes something like this: 1. download ports/src tree from cdrom/ftp site (usually done once) 2. use csup to update to HEAD 3. build As I understand it, it's advisable do an initial csup to the exact version in the snapshot, before doing the csup to the latest version. If you skip this then csup wont delete files removed between the snapshot and the current tree. If you are unlucky that could lead to persistent problems that are hard to diagnose. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
