bugish: port not being rebuilt

Joe Marcus Clarke marcus at marcuscom.com
Thu Nov 27 13:07:26 EST 2008


On Thu, 2008-11-27 at 20:04 +0200, Ion-Mihai Tetcu wrote:
> On Thu, 27 Nov 2008 03:14:09 -0500
> Joe Marcus Clarke <marcus at marcuscom.com> wrote:
> 
> > On Thu, 2008-11-27 at 10:06 +0200, Ion-Mihai IOnut Tetcu wrote:
> > > [ writting from webmail, sorry for the bad formatting ]
> > > 
> > > On Thu, November 27, 2008 08:29, Joe Marcus Clarke wrote:
> > > > On Thu, 2008-11-27 at 07:52 +0200, Ion-Mihai Tetcu wrote:
> > > >> On Wed, 26 Nov 2008 20:41:10 -0500
> > > >> Joe Marcus Clarke <marcus at marcuscom.com> wrote:
> > > >>
> > > >> > On Wed, 2008-11-26 at 23:39 +0200, Ion-Mihai Tetcu wrote:
> 
>  [ .. ]
> 
> > > >> > > I have a feeling this situation (existent up-to-date package,
> > > >> > > uninitialized entry in the DB) can happen after an Tindy
> > > >> > > upgrade.
> > > >> >
> > > >> > No, this shouldn't be the case.  An upgrade will not reset port
> > > >> > build entries in the DB.
> > > >>
> > > >> Well, no, an update leaves you enough times w/o any entry in the
> > > >> tables. BTW, for the next updates I'll work on a "ALTER
> > > >> TABLE ..." instead of current "DROP TABLE / CREATE TABLE"
> > > >> upgrade for mysql since I  can't afford to lose QAT tables data.
> > > >
> > > > The 2.x to 3.0 upgrade was a special case.  Even in that case,
> > > > virtually all table data was preserved.  However, all other
> > > > upgrades (e.g. from 3.0.2 to 3.1) used ALTER TABLE syntax.
> > > 
> > > Speaking of which, I really think it would be nice to have the
> > > compleate DS version in the database (major.minor.micro); think of
> > > the port users that, for one reason or an other can't update
> > > immediatelly after a release is out and they end up doing the
> > > update from 3 releases behind.
> > 
> > The major.minor.micro dsversion is stored in the database.
> 
>  # /usr/local/tinderbox/scripts/tc configGet | grep DS
> __DSVERSION__=3.1
> 
> Where should I look for the micro?

It isn't needed yet.  If we add a port fail reason, config option, etc.
without doing any other schema changes, then we will tack on the micro
version.  For now, the micro version is 0.

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://marcuscom.com/pipermail/tinderbox-list/attachments/20081127/3946e0c9/attachment.bin>


More information about the tinderbox-list mailing list