[ATrpms-users] Re: mythtv-0.15 upgrade problems

[Axel Thimm]

On Fri, May 28, 2004 at 05:19:57PM -0700, Jarod C. Wilson wrote:
> On Friday 28 May 2004 14:01, Axel Thimm wrote:
> > On Fri, May 28, 2004 at 12:43:02PM -0700, Jarod C. Wilson wrote:
> >
> > > No problems here, upgrading a Fedora Core 2 machine from pre-0.15 CVS of
> > > a few days ago to 0.15, when using dist-upgrade.
> >
> > > However, I did get this when
> > > trying to simply use apt-get install mythtv-suite:
> > >
> > > Preparing...                ###########################################
> > > [100%] 1:mythtvsetup           
> > > ########################################### [ 50%] 2:mythtv-suite        
> > >   ########################################### [100%] Done.
> > >
> > >
> > > None of the deps were upgraded, which I presume is because the cvs
> > > version tag satisfies mythtv-suite's dependencies...
> >
> > Yes, that's right. It is difficult to decide what version to adorne to
> > a snapshot in between two releases. Perhaps 14.99 would have been more
> > appropriate. Anyway apt-get upgrade will finish this off :)
> 
> Yes, nothing major to overcome, could have also run apt-get install against 
> all the package individually to get them updated. For the future, I think 
> perhaps something along the lines of 0.14.99 (or maybe 0.14.5) would be good 
> for CVS releases. The third number could be something of an indicator of 
> whether the CVS cut was closer to the prior release or the next release, like 
> 0.14.1 not long after the 0.14 release, 0.14.9 shortly before the 0.15 
> release (although, without a set release schedule, that could get tricky, 
> with 0.14.999999 or something, for the 4mo between 0.14 and 0.15 ;-).
> 
> Okay, after pondering that mess, my vote is for the next CVS cut being 
> 0.15.5-1, followed by 0.15.5-2, etc. Does that work, or will it break the 
> build number for the release packages? (as in, the current -71, I'm not sure 
> I've got my terms all correct).

Perhaps this should be discussed on mythtv-dev. I see the following
problem: If we start adorning versions to CVS, we could be wrongly
guessing the next version. There was once a .1 release, and it could
happen again. So we would have 0.17.5 and suddenly we would need to
"upgrade" to 0.17.1 which would require epochs etc.

I would tend to use the version mentioned in settings.pro in the
LIBVERSION variable, and try to convince mythtv developers to use
something less than the next final release. What do you think?
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20040529/f8ed702d/attachment.bin