[Piuparts-devel] Bug#847277: lava-server: fails to upgrade from jessie to stretch

[Holger Levsen]

On Wed, Feb 08, 2017 at 09:17:14PM +0000, Holger Levsen wrote:
> On Wed, Feb 08, 2017 at 09:03:20PM +0100, Andreas Beckmann wrote:
> > > (alternatively, admins can just install python-django
> > > python-django-tables2 from jessie-backports and run `lava-server
> > > managedb migrate` manually.)
> > > There's nothing wrong AFAICT with requiring a step via jessie-backports.
> > That's a *very* uncommon requirement (lava-server is the first package
> > doing this).
> 
> yeah, besides being pretty uncommon it's also pretty wrong I think, as it
> implies the version in jessie-backports cannot be upgraded to the version
> in stretch, as this would make the intermediate step in jessie-backports
> mood… :-)
> 
> That said, I can see how this could be more *convinient* (in the case where
> there are 3 very different versions involved, in stable, stable-bpo and
> testing/future stable but IMO this is broken unreliable design. What if the
> version in stable-bpo needs to be upgraded due to security issues and the only
> suitable version is the one in testing?)
> 
> That said, there is nothing wrong with this is this is *optional*.

                                             _if_ this is optional…


-- 
cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20170208/feb110a9/attachment.sig>