teeny bug when doing make update on recent CVS snap

William F. Maton wmaton at ryouko.imsb.nrc.ca
Wed Jan 1 12:08:35 UTC 2003

On Mon, 30 Dec 2002, Russ Allbery wrote:

> > Bah-zooks!!!
> > make[1]: Leaving directory `/usr/src/news/inn-CURRENT-20021230/doc'
> > /var/news/bin/innupgrade /var/news/etc
> > inn.conf: backup inn.conf.OLD already exists
> > make: [update] Error 255 (ignored)
> You apparently already have a backup copy of inn.conf, and innupgrade
> conservatively doesn't want to delete it.  If you look at it and either
> remove it or rename it and then run the above command again, that should
> take care of things.


> What behavior would you have preferred?

If it's a make update, ideally it should leave things alone, as it does
with the rest of the confiuration files.  Howeverm it had been many months
that I had tinkered with the -CURRENT series, and when I resumed my IPv6
work, I thought of you guys first. :-)

Anyhow, the inn.conf.OLD file was createad by a recent make update from a
recent snapshot.  I'm was wondering if something unintentional had
happened, but I thought I saw a note in the output that a new config value
had been put in since April 2002's snapshots, and it *had* to move
inn.conf out of the way for the new value to been inserted.  I'm not sure

So there was some sort of test, which seems to still be getting applied to
inn.conf, creating inn.conf.OLD, which subsequent make updates fail on.  I
could be wrong as to the cause though.


More information about the inn-bugs mailing list