SEO

I'm stumped. Can someone explain how it's done?

Thanks.

dave <daf@a64.comcast.net> writes:

> I'm stumped. Can someone explain how it's done?

From here it looks like their ftp server isn't entirely reachable at
the moment. Then again, judging from your domain it looks like you're
in the US, while the openbsd.nu people seem to be based in Sweden, so
unless you're looking for packages which are unique to OpenBSD.nu,
there may be other mirrors which would be closer to you.

--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
"First, we kill all the spammers" The Usenet Bard, "Twice-forwarded tales"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Peter N. M. Hansteen <peter@bsdly.net> wrote:
> dave <daf@a64.comcast.net> writes:
>
>> I'm stumped. Can someone explain how it's done?
>
> From here it looks like their ftp server isn't entirely reachable at
> the moment. Then again, judging from your domain it looks like you're
> in the US, while the openbsd.nu people seem to be based in Sweden, so
> unless you're looking for packages which are unique to OpenBSD.nu,
> there may be other mirrors which would be closer to you.

Well, I'm interested in downloading the latest packages for tin and
mplayer. It looked to me like the mirrors are for source only and I would
have to build the packages myself. I'd be happy to be wrong about that.

On Sat, 27 Jan 2007 07:35:22 -0600, dave wrote:

On Sat, 27 Jan 2007 07:35:22 -0600, dave wrote:

> Well, I'm interested in downloading the latest packages for tin and
> mplayer. It looked to me like the mirrors are for source only and I would
> have to build the packages myself. I'd be happy to be wrong about that.

I don't understand, Dave. What is it you are looking for, exactly?

In any mirror's /pub/OpenBSD/4.0/packages/amd64,
you can find tin-1.6.2; the packages were built September 23.

If you're running amd64-current, you can find the same tin-1.6.2, built
yesterday, if you go to a mirror which has snapshots.

For mplayer, you can find 1.0pre8p2 or 1.0pre8p3 in the 4.0 package
directory. p2 was also built September 23, but p5, a -stable package, was
built January 3. You can find 1.0pre8p5 in the snapshots package
directory, built yesterday.

--
Replying directly will get you locally blacklisted.
Change the address; use my first name in front of the @ if you want to
communicate privately.

Josh Grosse <spamtrap@jggimi.homeip.net> wrote:
> On Sat, 27 Jan 2007 07:35:22 -0600, dave wrote:
>
> On Sat, 27 Jan 2007 07:35:22 -0600, dave wrote:
>
>> Well, I'm interested in downloading the latest packages for tin and
>> mplayer. It looked to me like the mirrors are for source only and I would
>> have to build the packages myself. I'd be happy to be wrong about that.
>
> I don't understand, Dave. What is it you are looking for, exactly?
>
> In any mirror's /pub/OpenBSD/4.0/packages/amd64,
> you can find tin-1.6.2; the packages were built September 23.

openbsd.nu/ports lists packages newer than what I am running.
at nu tin is listed as rev 1.8, newer than the 1.6 I am running.
Ditto for mplayer and ffmpeg.

I just got email saying I can download the (newer) ports from
openbsd.org, but that has not been my experience. At any rate,
nu/ports is a very nice ports interface.

> If you're running amd64-current, you can find the same tin-1.6.2, built
> yesterday, if you go to a mirror which has snapshots.

I'm still running 4.0 release with a couple of security fixes.

> For mplayer, you can find 1.0pre8p2 or 1.0pre8p3 in the 4.0 package
> directory. p2 was also built September 23, but p5, a -stable package, was
> built January 3. You can find 1.0pre8p5 in the snapshots package
> directory, built yesterday.

Many Thanks for the info.

On Sat, 27 Jan 2007 13:53:37 -0600, dave wrote:

>>> Well, I'm interested in downloading the latest packages...
> I'm still running 4.0 release with a couple of security fixes.

As you must know from having read
http://openbsd.rt.fm/faq/faq15.html#NoFun already, you will likely be
unsuccessful trying use any package built for -current on -release, due to
dependent library changes. If the package has no dependencies, it may
still not install, or if you force the install, it may not work properly,
due to different releases of dynamic libraries in Userland (/usr/lib).

You are, as they say, ON YOUR OWN.

> openbsd.nu/ports lists packages newer than what I am running. at nu tin
> is listed as rev 1.8, newer than the 1.6 I am running. Ditto for mplayer
> and ffmpeg.

If you'd like to follow -current ports developments, there are several
alternatives:

1. CVS and the various CVS-related tools, including the ports-ctm
mailing list.

2. The ports-changes@ mailing list

3. The ports tree web interface

4. Daily tarball updates

-------

If you don't have the -current ports tree handy on one of your
systems, it is available for perusal and review on-line, via web
interface. It lags the changes to the official tree by about 2 hours,
which is about the same as primary mirrors.

In addition to having -current in there, it has all of the cvs logs, so
you can see every change to every Makefile or patch file, over time, and
between various -releases, between -release and -stable ... whatever.

Here is a handy link to the ports tree:

http://www.openbsd.org/cgi-bin/cvsweb/ports

And all you need do is change that last word from "ports" to "src" to see
the OS tree. This is the same web interface you can find from the
website's home page, under "Getting Source."

> I just got email saying I can download the (newer) ports from
> openbsd.org, but that has not been my experience. At any rate, nu/ports
> is a very nice ports interface.

If you don't use cvs, or the web, you can find a -current ports tarball
updated every day on ftp.openbsd.org and all of the mirrors that carry
snapshots, in /pub/OpenBSD/snapshots.

--------

As I mentioned in my last post, -current *packages* are built and
available for some of the more popular architectures, on an irregular
basis. But they are designed for the convenience of -current users, and
you are not running -current.

And, because these "snapshot packages" are not directly synchronized with
snapshots of the OS, or snapshots of X (which are often done separately,
and of course, far more frequently than package builds), the user must be
able to manage inconsistancies, and perhaps do some manual rebuilding on
their own.

> Many Thanks for the info.

You're very welcome. Good luck, whether you decide to force these
packages on (lotsa luck!), or whether you decide to learn about -current,
or whether you just decide to track developments of your favorite packages.

--
Replying directly will get you locally blacklisted.
Change the address; use my first name in front of the @ if you want to
communicate privately.

Josh Grosse <spamtrap@jggimi.homeip.net> wrote:
> On Sat, 27 Jan 2007 13:53:37 -0600, dave wrote:
>
>>>> Well, I'm interested in downloading the latest packages...
>> I'm still running 4.0 release with a couple of security fixes.
>
> As you must know from having read
> http://openbsd.rt.fm/faq/faq15.html#NoFun already, you will likely be
> unsuccessful trying use any package built for -current on -release, due to
> dependent library changes. If the package has no dependencies, it may
> still not install, or if you force the install, it may not work properly,
> due to different releases of dynamic libraries in Userland (/usr/lib).
>
> You are, as they say, ON YOUR OWN.
>
>> openbsd.nu/ports lists packages newer than what I am running. at nu tin
>> is listed as rev 1.8, newer than the 1.6 I am running. Ditto for mplayer
>> and ffmpeg.
>
> If you'd like to follow -current ports developments, there are several
> alternatives:
>
> 1. CVS and the various CVS-related tools, including the ports-ctm
> mailing list.
>
> 2. The ports-changes@ mailing list
>
> 3. The ports tree web interface
>
> 4. Daily tarball updates
>
> -------
>
> If you don't have the -current ports tree handy on one of your
> systems, it is available for perusal and review on-line, via web
> interface. It lags the changes to the official tree by about 2 hours,
> which is about the same as primary mirrors.
>
> In addition to having -current in there, it has all of the cvs logs, so
> you can see every change to every Makefile or patch file, over time, and
> between various -releases, between -release and -stable ... whatever.
>
> Here is a handy link to the ports tree:
>
> http://www.openbsd.org/cgi-bin/cvsweb/ports
>
> And all you need do is change that last word from "ports" to "src" to see
> the OS tree. This is the same web interface you can find from the
> website's home page, under "Getting Source."
>
>> I just got email saying I can download the (newer) ports from
>> openbsd.org, but that has not been my experience. At any rate, nu/ports
>> is a very nice ports interface.
>
> If you don't use cvs, or the web, you can find a -current ports tarball
> updated every day on ftp.openbsd.org and all of the mirrors that carry
> snapshots, in /pub/OpenBSD/snapshots.
>
> --------
>
> As I mentioned in my last post, -current *packages* are built and
> available for some of the more popular architectures, on an irregular
> basis. But they are designed for the convenience of -current users, and
> you are not running -current.
>
> And, because these "snapshot packages" are not directly synchronized with
> snapshots of the OS, or snapshots of X (which are often done separately,
> and of course, far more frequently than package builds), the user must be
> able to manage inconsistancies, and perhaps do some manual rebuilding on
> their own.
>
>> Many Thanks for the info.
>
> You're very welcome. Good luck, whether you decide to force these
> packages on (lotsa luck!), or whether you decide to learn about -current,
> or whether you just decide to track developments of your favorite packages.

I had forgotten the part about package updates being only for current.
The differences between -current and -stable have been by far the
subject I have had the most trouble sorting out. I have, as a result,
stuck to -release in order to stay out of trouble. But I expect at some
point to start tracking -current when I think I can do so without
blowing myself out of the water. Thanks again for the very complete
explanation of this issue.

dave <daf@a64.comcast.net> wrote:
> Josh Grosse <spamtrap@jggimi.homeip.net> wrote:
>> On Sat, 27 Jan 2007 07:35:22 -0600, dave wrote:
>>> Well, I'm interested in downloading the latest packages for tin and
>>> mplayer. It looked to me like the mirrors are for source only and I would
>>> have to build the packages myself. I'd be happy to be wrong about that.
>>
>> I don't understand, Dave. What is it you are looking for, exactly?
>>
>> In any mirror's /pub/OpenBSD/4.0/packages/amd64,
>> you can find tin-1.6.2; the packages were built September 23.
>
> openbsd.nu/ports lists packages newer than what I am running.
> at nu tin is listed as rev 1.8, newer than the 1.6 I am running.
> Ditto for mplayer and ffmpeg.
>
> I just got email saying I can download the (newer) ports from
> openbsd.org, but that has not been my experience. At any rate,
> nu/ports is a very nice ports interface.

You either wait a couple of days, or build them from ports. Exactly what
is the problem? Tin is rather small, you already have all it's build
dependencies installed if you can run it, and so on.

I can see why one would prefer using packages for mplayer, but I don't
see a pressing need to hurry there.

Joachim

Joachim Schipper <joachim@melpomene.jschipper.dynalias.net> wrote:
> dave <daf@a64.comcast.net> wrote:
>> Josh Grosse <spamtrap@jggimi.homeip.net> wrote:
>>> On Sat, 27 Jan 2007 07:35:22 -0600, dave wrote:
>>>> Well, I'm interested in downloading the latest packages for tin and
>>>> mplayer. It looked to me like the mirrors are for source only and I would
>>>> have to build the packages myself. I'd be happy to be wrong about that.
>>>
>>> I don't understand, Dave. What is it you are looking for, exactly?
>>>
>>> In any mirror's /pub/OpenBSD/4.0/packages/amd64,
>>> you can find tin-1.6.2; the packages were built September 23.
>>
>> openbsd.nu/ports lists packages newer than what I am running.
>> at nu tin is listed as rev 1.8, newer than the 1.6 I am running.
>> Ditto for mplayer and ffmpeg.
>>
>> I just got email saying I can download the (newer) ports from
>> openbsd.org, but that has not been my experience. At any rate,
>> nu/ports is a very nice ports interface.
>
> You either wait a couple of days, or build them from ports. Exactly what
> is the problem? Tin is rather small, you already have all it's build
> dependencies installed if you can run it, and so on.

My problem is that I've got too many irons in the fire. That makes me
forget things I should remember - eg package updates are for current.

> I can see why one would prefer using packages for mplayer, but I don't
> see a pressing need to hurry there.
>
> Joachim

I agree. I'm quite prepared to wait for 4.1 to get the updates.
In the meantime I'm having lots of fun with video capture.

dave <daf@a64.comcast.net> writes:

> My problem is that I've got too many irons in the fire. That makes me
> forget things I should remember - eg package updates are for current.

Not strictly true. Package updates for -current may be more frequent
(roughly in sync with snapshots), but -stable packages do get updated.

Then it's usually a matter of

$ export PKG_PATH=ftp://ftp.your.favorite.mirror.tld/pub/OpenBSD/$release/packages/$platform/

(where you fill in appropriate values), then

$ sudo pkg_add -ui

some ports do need to be built locally though.

--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
"First, we kill all the spammers" The Usenet Bard, "Twice-forwarded tales"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.