Eric "Shubes" wrote:
Ray Lance wrote:
Eric "Shubes" wrote:
Ray Lance wrote:
How can I force a sandbox rebuild after the failure of djbdns (cnt40)?
I tried chrooting into the sandbox and removing a component, but that
doesn't do it.
Simply run qtp-newmodel again from the top. It'll ask you if you want to
keep the sandbox or build a new one.
No, this is the one where I answer no or skip to djbdns, then it quits,
having nothing to do.
That sounds peculiar. What do you get from
# qtp-ami-up2date
No New QMail-Toaster Packages Available
# rpm -qa | grep toaster
?
ucspi-tcp-toaster-0.88-1.3.3
qmail-toaster-1.03-1.3.12
autorespond-toaster-2.0.4-1.3.2
qmailadmin-toaster-1.2.9-1.3.3
isoqlog-toaster-2.1-1.3.2
clamav-toaster-0.88.7-1.3.7
qmailtoaster-plus-0.2-1.3.2
daemontools-toaster-0.76-1.3.2
vpopmail-toaster-5.4.13-1.3.3
libsrs2-toaster-1.0.18-1.3.2
ripmime-toaster-1.4.0.6-1.3.2
qmail-pop3d-toaster-1.03-1.3.12
courier-imap-toaster-4.1.2-1.3.6
control-panel-toaster-0.5-1.3.3
ezmlm-cgi-toaster-0.53.324-1.3.2
qmailmrtg-toaster-4.2-1.3.2
maildrop-toaster-devel-2.0.3-1.3.4
spamassassin-toaster-3.1.7-1.3.6
vqadmin-toaster-2.3.4-1.3.2
libdomainkeys-toaster-0.68-1.3.2
courier-authlib-toaster-0.59-1.3.4
ezmlm-toaster-0.53.324-1.3.2
maildrop-toaster-2.0.3-1.3.4
squirrelmail-toaster-1.4.9a-1.3.5
simscan-toaster-1.3.1-1.3.4
