On Jul 17 2015, Sam Hartman <hartm...@debian.org> wrote:
> If a package is not going to provide an upgrade from one debian
> release to the next, it should not generally be in the Debian release.
> It would be fine for it to continue to be in unstable.
>
> We need to figure out if someone is willing to commit to doing the
> necessary work for stretch and if not probably leave s3ql in unstable
> but pull from stretch and investigate whether it should be pulled from
> Jessie in a point release.

I agree. There shouldn't have been an s3ql package in Wheezy. This was
when I was young and inexperienced with Debian packaging. However, the
situation is different for Jessie. Now that it is much more mature,
there will be issues in keeping the stretch S3QL fully backwards
compatible with Jessie S3QL. 

>     Nikolaus> I guess it would have been better to package S3QL 2.x as a
>     Nikolaus> new s3ql2 package instead of it replacing the s3ql
>     Nikolaus> package. But I don't think there is a way to recticify
>     Nikolaus> that now - or is there?
>
> But then people still lose their data from wheezy->jessie.

No, in that case we could have kept the old S3QL 1.x package in jessie.

>     Nikolaus> Theoretically, it is possible to do all the upgrades in
>     Nikolaus> one step and integrate that into Jessie's s3ql package,
>     Nikolaus> but that would be a major coding effort.
>
> So, you talked about it being a lot of work to do the upgrade in one
> step.
> Why does that need to happen?
> Why can't the upgrade be handled in two steps and we just package  the
> necessary parts to do all the steps?

That would mean to package ~5 intermediate S3QL versions. Not a big deal
in terms of work (since these versions were already in testing at some
point), but do you think that would be acceptable for a point release?

> How much harder  are we talking about than getting the s3qladm and s3ql
> libraries from the 2.5 version of s3ql into Jessie?

I don't understand the question. 

Best,
-Nikolaus
-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to