$subject to adress bug 248247, in 30 days from now Thanks
It should be safe to do this now, no problems have appeared since 2012-06-02.
Engage, plz.
x86 stable
Stable on ppc pp64. @maintainer. Should djbdns depend on daemontools since you need the latter to run the server? Maybe even conditonally on USE="server"?
(In reply to comment #4) > Stable on ppc pp64. > > @maintainer. Should djbdns depend on daemontools since you need the latter > to run the server? Maybe even conditonally on USE="server"? Doesn't it? RDEPEND="${DEPEND} virtual/daemontools ... " Some of the tools will work without it, but I think almost everyone who's going to install djbdns will "want" (i.e. put up with) daemontools as well.
(In reply to comment #5) > (In reply to comment #4) > > Stable on ppc pp64. > > > > @maintainer. Should djbdns depend on daemontools since you need the latter > > to run the server? Maybe even conditonally on USE="server"? > > Doesn't it? > > RDEPEND="${DEPEND} > virtual/daemontools > ... > " > Some of the tools will work without it, but I think almost everyone who's > going to install djbdns will "want" (i.e. put up with) daemontools as well. Yeah I see that now. I don't know what I did that made me think that I didn't get daemontools. Sorry for the noise.
Stable for HPPA.
Created attachment 319596 [details] daemontools stuff missing? When I run djbdns-setup, errors suggesting that daemontools are _not_ installed appear, this happens here wheather I emerge it with USE="static" or not. Is this expected, e.g. my fault? /usr/bin/djbdns-setup: line 298: ebegin: command not found /usr/bin/djbdns-setup: line 300: eend: command not found ....
(In reply to comment #8) > Created attachment 319596 [details] > daemontools stuff missing? > > When I run djbdns-setup, errors suggesting that daemontools are _not_ > installed appear, this happens here wheather I emerge it with USE="static" > or not. > Is this expected, e.g. my fault? > > /usr/bin/djbdns-setup: line 298: ebegin: command not found > /usr/bin/djbdns-setup: line 300: eend: command not found > .... Not intended, of course. The switch to baselayout2 broke all of the foo-setup scripts. Previously, the ebegin, eend, etc. functions were located in /sbin/functions.sh. In baselayout2, they moved to /etc/init.d/functions.sh and the two setup scripts that sourced /sbin/functions.sh were updated in bug #389667. But, djbdns-setup (then: djbdns-setup-r17) didn't ever inherit /sbin/functions.sh, so I guess it never worked at all! These setup scripts are a nightmare anyway; I've opened both bug #428582 and bug #428588 to deal with them.
amd64 stable
alpha/sparc stable