DragonFlyBSD

:Can someone put these two lines in their /etc/mk.conf:
:
:BINPKG_SITES+=http://pkgbox.dragonflybsd.org
:DEPENDS_TARGET+=bin-install
:
:And then go to some package you want in the pkgsrc tree, and perform a:
:
:'bmake bin-install'
:
:This should install whatever package and its dependencies, building from
:source only when the package needed isn't present as an existing binary at
:one of our mirrors. If it does or does not work, please tell me.
:
:Make sure that you have a version of pkg_install from this year; pkg_add
:-V will tell you and 'bmake install' in /usr/pkg/pkgtools/pkg_install will
:upgrade it.

It has to be /usr/pkg/etc/mk.conf now.  /etc/mk.conf is obsolete and
    pkgsrc no longer parses it.

When I stuck the lines in /usr/pkg/etc/mk.conf it did work, but this
    isn't the best test since my machines are on the same LAN as pkgbox.

test28# bmake clean
===> Cleaning for mtools-3.9.10nb1
test28# bmake bin-install
===> Binary install for mtools-3.9.10nb1
=> Installing mtools-3.9.10nb1 from /usr/pkgsrc/packages/All;http://pkgbox.dragonflybsd.org/All
pkg_add: Warning: package `http://pkgbox.dragonflybsd.org/All/mtools-3.9.10nb1.tgz' was built for a different version of the OS:
pkg_add: DragonFly/i386 1.10.1 (pkg) vs. DragonFly/i386 1.11.0 (this host)
mtools-3.9.10nb1: registering info file /usr/pkg/info/mtools.info
mtools-3.9.10nb1 successfully installed.
test28#

-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>

I just tried to use it to install dependencies for devel/mercurial.
It worked for some packages, but failed for others, say asciidoc:

$ pkg_add -V
20070730
$ cd /usr/pkgsrc/textproc/asciidoc
$ bmake bin-install
===> Binary install for asciidoc-8.1.0nb2
=> Becoming ``root'' to make su-do-bin-install (/usr/bin/su)
=> Installing asciidoc-8.1.0nb2 from /home/pkgsrc/packages/All;http://pkgbox.dragonflybsd.org/All
ftp>

Here it dropped to interactive prompt of ftp command. If I type `exit'
it gives up and tries to build the package from source. But I'm doing
this on DragonFly snapshot inside VMware fusion, so it may have something
to do with its NAT connection. I'll try this on a real machine later.

Thanks.

I think it is caused by the way pkg_add interacts with one of the mirror sites -
I had seen this previously, but it was fixed by updating pkg_install to a recent
version.

Ok, it turned out that it's becauase our ftp command is not compatible
to NetBSD version. pkg_add command uses ftp command to obtain the file
list like this:
ftp -V -o - theURL

OTOH pkgbox.dragonflybsd.org can redirect us to one of two locations:
http://ipv4.theshell.com/pub/DragonFly/packages/DragonFly-1.10.1/i386/All/
ftp://ftp.dragonflybsd.kiev.ua/pub/DragonFlyBSD/packages/DragonFly-1.10.1/i386/All/

but apparently our ftp command drops to an interactive prompt instead of
giving us the list if theURL is an ftp one. So if we use ftp server
for one of our bin-install sources, we need to port the fix from
NetBSD as their command does the job unlike ours.

Cheers.

Sorry, the same thing happened to NetBSD version; probably I made a pasto
when I was trying wget or curl:

$ ftp -o - ftp://ftp.dragonflybsd.kiev.ua/pub/DragonFlyBSD/packages/DragonFly-1.10.1/i386/All/
  Connected to ftp.dragonflybsd.kiev.ua.
  220 Welcome to ftp.h0.org.ua FTP service.
  331 Please specify the password.
  230 Login successful.
  Remote system type is UNIX.
  Using binary mode to transfer files.
  200 Switching to Binary mode.
  250 Directory successfully changed.
  250 Directory successfully changed.
  250 Directory successfully changed.
  250 Directory successfully changed.
  250 Directory successfully changed.
  250 Directory successfully changed.
  ftp>

Yep - it looks like it's how the ftp command understands the URL to a
directory; instead of downloading the content as with a HTTP URL, it
navigates to that spot and the last thing it does is 'PWD'.

Watching it with tcpdump on two different ftpds shows this. Returning a
directory listing when supplied a URL seems like the 'correct' behavior,
but I'm biased. I'll mail Luke Mewburn and ask.

This no longer even works with our current pkgbox.

sudo bmake bin-install

===> Binary install for wget-1.11.4
=> Installing wget-1.11.4 from
/home/source/pkgsrc/packages/All;http://pkgbox.dragonflybsd.org/All
pkg_add: Can't process http://pkgbox.dragonflybsd.org:80/All/wget-1*: Not Found
pkg_add: no pkg found for 'wget-1.11.4', sorry.
pkg_add: 1 package addition failed
=> No binary package found for wget-1.11.4; installing from source.

Maybe we're missing /All (alias) on http://pkgbox.dragonflybsd.org

Not Found
The requested URL /All was not found on this server.

Apache/1.3.37 Server at pkgbox.dragonflybsd.org Port 80

• Antonio Huete Jimenez (via DragonFly issue tracker) wrote:

Antonio Huete Jimenez <tuxillo@quantumachine.net> added the comment:

This no longer even works with our current pkgbox.

sudo bmake bin-install

===> Binary install for wget-1.11.4
=> Installing wget-1.11.4 from
/home/source/pkgsrc/packages/All;http://pkgbox.dragonflybsd.org/All
pkg_add: Can't process http://pkgbox.dragonflybsd.org:80/All/wget-1*: Not Found
pkg_add: no pkg found for 'wget-1.11.4', sorry.
pkg_add: 1 package addition failed
=> No binary package found for wget-1.11.4; installing from source.

Maybe we're missing /All (alias) on http://pkgbox.dragonflybsd.org

Please do not use pkgbox any longer. Avalon is now the master (or use a
mirror nearby). We should remove the packages/ stuff from pkgbox ASAP
and redirect the DNS to avalon.

Cheers

Matthias

Setting to resolved; Apache on pkgbox.dragonflybsd.org has been set to
automatically redirect older versions of pkg_radd to the correct location on
avalon.dragonflybsd.org.

The original steps in this bug report date to before our current by-release
hierarchy, so you'd have to manually construct the path in any case. pkg_radd
does that automatically.