Re: How to track port updates in stable?
On 8/4/07, Todd Pytel [EMAIL PROTECTED] wrote: I don't spend as much time following OpenBSD as I used to, so perhaps I'm missing something. But there used to be a ports-security mailing list used for announcing updated ports. That list doesn't exist any more, or at least doesn't appear to have had anything posted to it in a very long time. Is there some other official way to track changes to ports? Absent that, has anyone come up with a simple hack to feed to cron to accomplish the same thing? I use http://flirble.disruptiveproactivity.com/rss/openbsd_stable_ports.rss and google reader It was given by a kind individual on this list :-) Related feeds are http://flirble.disruptiveproactivity.com/rss/openbsd_stable_XF4.rss http://flirble.disruptiveproactivity.com/rss/openbsd_stable_src.rss http://undeadly.org/cgi?action\x3derrata hope this helps :-) Kind Regards Siju
Re: How to track port updates in stable?
Will Maier wrote: On Fri, Aug 03, 2007 at 06:35:51PM -0500, Todd Pytel wrote: I don't spend as much time following OpenBSD as I used to, so perhaps I'm missing something. But there used to be a ports-security mailing list used for announcing updated ports. That list doesn't exist any more, or at least doesn't appear to have had anything posted to it in a very long time. It exists, but is inactive. Is there some other official way to track changes to ports? By looking at the output of `cvs up`? By watching commits via [EMAIL PROTECTED] I do both, and find it sufficient. Absent that, has anyone come up with a simple hack to feed to cron to accomplish the same thing? I pull updated ports and src daily via cron, and read (ports|source)-changes@ for commit messages, etc. Does that not achieve what you need? This is not yet finished but already working: http://www.markus-hennecke.de/downloads/list_updated_ports.pl Just feed the script a cvs logfile from a ports update and it will print each port that has a changed Makefile and a changed version number. I am keeping track of current ports with this script. There are still some things missing like reading more than one cvs log in one pass and some command line switches. Greetings Markus
How to track port updates in stable?
I don't spend as much time following OpenBSD as I used to, so perhaps I'm missing something. But there used to be a ports-security mailing list used for announcing updated ports. That list doesn't exist any more, or at least doesn't appear to have had anything posted to it in a very long time. Is there some other official way to track changes to ports? Absent that, has anyone come up with a simple hack to feed to cron to accomplish the same thing? --Todd
Re: How to track port updates in stable?
On Fri, Aug 03, 2007 at 06:35:51PM -0500, Todd Pytel wrote: I don't spend as much time following OpenBSD as I used to, so perhaps I'm missing something. But there used to be a ports-security mailing list used for announcing updated ports. That list doesn't exist any more, or at least doesn't appear to have had anything posted to it in a very long time. It exists, but is inactive. Is there some other official way to track changes to ports? By looking at the output of `cvs up`? By watching commits via [EMAIL PROTECTED] I do both, and find it sufficient. Absent that, has anyone come up with a simple hack to feed to cron to accomplish the same thing? I pull updated ports and src daily via cron, and read (ports|source)-changes@ for commit messages, etc. Does that not achieve what you need? -- o--{ Will Maier }--o | web:...http://www.lfod.us/ | [EMAIL PROTECTED] | *--[ BSD Unix: Live Free or Die ]--*
Re: How to track port updates in stable?
On 2007/08/03 18:54, Will Maier wrote: On Fri, Aug 03, 2007 at 06:35:51PM -0500, Todd Pytel wrote: I don't spend as much time following OpenBSD as I used to, so perhaps I'm missing something. But there used to be a ports-security mailing list used for announcing updated ports. That list doesn't exist any more, or at least doesn't appear to have had anything posted to it in a very long time. It exists, but is inactive. Is there some other official way to track changes to ports? By looking at the output of `cvs up`? By watching commits via [EMAIL PROTECTED] I do both, and find it sufficient. Absent that, has anyone come up with a simple hack to feed to cron to accomplish the same thing? I pull updated ports and src daily via cron, and read (ports|source)-changes@ for commit messages, etc. Does that not achieve what you need? Or there's odc/owc if you prefer summaries: http://www.squish.net/mailman/listinfo Even looking at output of a cron-scripted 'cvs up' or cvsync is useful.
Re: How to track port updates in stable?
On Sat, Aug 04, 2007 at 01:10:24AM +0100, Stuart Henderson wrote: On 2007/08/03 18:54, Will Maier wrote: On Fri, Aug 03, 2007 at 06:35:51PM -0500, Todd Pytel wrote: I don't spend as much time following OpenBSD as I used to, so perhaps I'm missing something. But there used to be a ports-security mailing list used for announcing updated ports. That list doesn't exist any more, or at least doesn't appear to have had anything posted to it in a very long time. It exists, but is inactive. Is there some other official way to track changes to ports? By looking at the output of `cvs up`? By watching commits via [EMAIL PROTECTED] I do both, and find it sufficient. Absent that, has anyone come up with a simple hack to feed to cron to accomplish the same thing? I pull updated ports and src daily via cron, and read (ports|source)-changes@ for commit messages, etc. Does that not achieve what you need? Or there's odc/owc if you prefer summaries: http://www.squish.net/mailman/listinfo Even looking at output of a cron-scripted 'cvs up' or cvsync is useful. If you want some sort of web interface you could also subscribe to http://ports.openbsd.nu/rss.php. -- James Turner BSD Group Consulting http://www.bsdgroup.org
Re: How to track port updates in stable?
On Fri, 2007-08-03 at 18:35 -0500, Todd Pytel wrote: Is there some other official way to track changes to ports? Thanks for all the responses. I went with the tracking system on ports.openbsd.nu. While I understand and admire the whole follow the source approach of watching cvs, my servers are hobby machines and family commitments mean that I can't geek out as much as I used to. While I don't run any high-profile ports that I would expect to be attacked, it's still nice to get a notification about a security update in case I haven't had time to check the lists in a while. Thanks again. --Todd
Re: How to track port updates in stable?
Todd Pytel wrote: On Fri, 2007-08-03 at 18:35 -0500, Todd Pytel wrote: Is there some other official way to track changes to ports? Thanks for all the responses. I went with the tracking system on ports.openbsd.nu. While I understand and admire the whole follow the source approach of watching cvs, my servers are hobby machines and family commitments mean that I can't geek out as much as I used to. While I don't run any high-profile ports that I would expect to be attacked, it's still nice to get a notification about a security update in case I haven't had time to check the lists in a while. If you're only interested in updated packages for the stable branch, and you have limited geek-out time (don't we all), there's always http://www.openbsd.org/pkg-stable.html You can see the changes to it in reverse chronological order at: http://www.openbsd.org/cgi-bin/cvsweb/www/build/packages-4.1 (assuming you're tracking 4.1-stable) Hope it helps, Lawrence -- Lawrence Teo Calyptix Security http://www.calyptix.com/
Re: How to track port updates in stable?
On Fri, Aug 03, 2007 at 06:35:51PM -0500, Todd Pytel wrote: I don't spend as much time following OpenBSD as I used to, so perhaps I'm missing something. But there used to be a ports-security mailing list used for announcing updated ports. That list doesn't exist any more, or at least doesn't appear to have had anything posted to it in a very long time. Is there some other official way to track changes to ports? Absent that, has anyone come up with a simple hack to feed to cron to accomplish the same thing? --Todd I think the easiest is: If you must use ports: regularly cvs update or cvs up your local ports tree and run the /usr/ports/infrastructure/build/out-of-date script to find things to update. If you use packages (recommended) just make sure $PKG_PATH is set and pkg_add -ui. It will prompt you to install any updated versions.