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
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
