Previously Russell Coker wrote:
> Wichert, how are plans for getting a public repository for these things going?
It's online now at ftp://ftp.valinux.com/pub/people/wichert/ . It has
all the magic that apt needs to download binary and source packages.
I also split the archive in two sections: one
Previously Russell Coker wrote:
> Wichert, how are plans for getting a public repository for these things going?
It's online now at ftp://ftp.valinux.com/pub/people/wichert/ . It has
all the magic that apt needs to download binary and source packages.
I also split the archive in two sections: on
Previously Russell Coker wrote:
> Wichert, how are plans for getting a public repository for these things going?
They should appear at ftp://ftp.valinux.com/pub/people/wichert/
somewhere in the next 30 hours.
Please note that I do expect everyone who uses them to subscribe
to the va-debian-users
Previously Russell Coker wrote:
> Wichert, how are plans for getting a public repository for these things going?
They should appear at ftp://ftp.valinux.com/pub/people/wichert/
somewhere in the next 30 hours.
Please note that I do expect everyone who uses them to subscribe
to the va-debian-users
Previously Russell Coker wrote:
> Wichert, how are plans for getting a public repository for these things going?
I pretty much have everything ready to go. There are two bugs I would like
to fix first:
1. update-devfsd in my devfs package isn't executable. I suspect the
debian/rules
script cop
Previously Russell Coker wrote:
> Wichert, how are plans for getting a public repository for these things going?
I pretty much have everything ready to go. There are two bugs I would like
to fix first:
1. update-devfsd in my devfs package isn't executable. I suspect the debian/rules
script cop
On Tuesday 13 March 2001 11:40, Neale Banks wrote:
> > I have .deb's of the latest LDAP stuff for Potato. I didn't build them
> > though. Hopefully we can establish some sort of official repository for
> > such things and manage them properly...
>
> They're possibly the ones at http://people.debi
On Thu, 8 Mar 2001, Russell Coker wrote:
> On Thursday 08 March 2001 04:29, Neale Banks wrote:
[...]
> > Then starts the slippery slope... the libldap2 in unstable depends on
> > libsasl7, which in its turn recommends libsasl-modules (the only
> > consolation here is that libsasl7 etc is also in t
On Tuesday 13 March 2001 11:40, Neale Banks wrote:
> > I have .deb's of the latest LDAP stuff for Potato. I didn't build them
> > though. Hopefully we can establish some sort of official repository for
> > such things and manage them properly...
>
> They're possibly the ones at http://people.deb
On Thu, 8 Mar 2001, Russell Coker wrote:
[...]
> > Any suggestions other than building all of those for potato (and no, I
> > don't want to upgrade yet).
>
> I have .deb's of the latest LDAP stuff for Potato. I didn't build them
> though. Hopefully we can establish some sort of official reposi
> I'm prepared to concede defeat and upgrade the slink system to potato
> (there are other motivating factors here too - things too old just become
> too hard sooner or later - OTOH >400 days uptime can be strong motivation
> to just "let it be").
I agree -- it is hard to upgrade a system when it
On Thursday 08 March 2001 04:29, Neale Banks wrote:
> Inded, as well as (unsuccessfully) attempting to build current BIND for
> slink (separate story), I'm motivated to try to build the latest postfix
> (postfix_0.0.20010228-2, which includes LDAP support) for *potato*.
>
> I'm prepared to concede
On Thursday 08 March 2001 04:29, Neale Banks wrote:
> Inded, as well as (unsuccessfully) attempting to build current BIND for
> slink (separate story), I'm motivated to try to build the latest postfix
> (postfix_0.0.20010228-2, which includes LDAP support) for *potato*.
>
> I'm prepared to concede
On Wed, 7 Mar 2001, Russell Coker wrote:
[...]
> I think that we need some separate projects for maintaining outdated
> distributions of Debian. There's no way I'll touch slink but I have a great
> need for potato to be usable with the latest stuff.
Inded, as well as (unsuccessfully) attemptin
On Wed, 7 Mar 2001, Russell Coker wrote:
[...]
> I think that we need some separate projects for maintaining outdated
> distributions of Debian. There's no way I'll touch slink but I have a great
> need for potato to be usable with the latest stuff.
Inded, as well as (unsuccessfully) attempti
On Wednesday 07 March 2001 17:22, I. Forbes wrote:
> > Isn't there a security update for that?
>
> There is, but the update has not been released for slink, just potato,
> thats why I needed to recompile it.
Sorry, I misread your email. My brain translates "!=woody" to "==potato". ;)
> > Greppi
Hello Russell
On 6 Mar 2001, at 8:09, Russell Coker wrote:
> Isn't there a security update for that?
There is, but the update has not been released for slink, just potato,
thats why I needed to recompile it.
> > The compilation bombs out with the following message:
> >
> > make[3]: Entering di
On Wednesday 07 March 2001 17:22, I. Forbes wrote:
> > Isn't there a security update for that?
>
> There is, but the update has not been released for slink, just potato,
> thats why I needed to recompile it.
Sorry, I misread your email. My brain translates "!=woody" to "==potato". ;)
> > Grepp
Hello Russell
On 6 Mar 2001, at 8:09, Russell Coker wrote:
> Isn't there a security update for that?
There is, but the update has not been released for slink, just potato,
thats why I needed to recompile it.
> > The compilation bombs out with the following message:
> >
> > make[3]: Entering d
On Monday 05 March 2001 16:01, I. Forbes wrote:
> I am trying to compile the latest "bind" on a slink system.
>
> (It is a production system that I don't wish to upgrade right now, and
> I am also not happy running the old vulnerable version ...)
Isn't there a security update for that?
> The comp
On Monday 05 March 2001 16:01, I. Forbes wrote:
> I am trying to compile the latest "bind" on a slink system.
>
> (It is a production system that I don't wish to upgrade right now, and
> I am also not happy running the old vulnerable version ...)
Isn't there a security update for that?
> The com
Hello All
I am trying to compile the latest "bind" on a slink system.
(It is a production system that I don't wish to upgrade right now, and
I am also not happy running the old vulnerable version ...)
The compilation bombs out with the following message:
make[3]: Entering directory `/home/ia
Hello All
I am trying to compile the latest "bind" on a slink system.
(It is a production system that I don't wish to upgrade right now, and
I am also not happy running the old vulnerable version ...)
The compilation bombs out with the following message:
make[3]: Entering directory `/home/i
23 matches
Mail list logo
