[Debian-med-packaging] Bug#686376: Bug#684990: ginkgocadx: Cadx 2.14 avaiable
andreas at an3as.eu
Mon Sep 3 06:22:21 UTC 2012
On Mon, Sep 03, 2012 at 09:13:53AM +1000, Dmitry Smirnov wrote:
> Hi Andreas,
> On Mon, 3 Sep 2012 07:17:59 Andreas Tille wrote:
> > I could upload to experimental if you think it helps and so we will not
> > undermine some unstable -> testing migration of a fixed package.
> Please correct me if I misunderstand but I think if we had a library with
> planned transition or -dev dependency it would certainly go to experimental.
That's in the usual development period but we are currently in freeze.
> For standalone application it's not much use to upload to experimental, right?
In freeze time it could happen that you need to upload a fix for an RC
problem that might occure. You can not fix this by simply upload a new
upstream version but you should rather fix it in the version in testing.
If in unstable exists an upstream version higher than the version in
testing you need to fiddle with epochs and kick the later version from
unstable which is suboptimal.
> > BTW, as far as I can see the open bugs are not RC, right?
> Correct, we have one that do not qualify for RC. :)
So if you are really sure that the current version in testing will not
show any RC bug in freeze time we can upload to unstable this new
version (or some later version fixing this bug). If you are not really
sure perhaps experimental is better.
> > Just tell me whether you want me to sponsor - I do not think that we should
> > do a panic upload just because there is a new upstream version.
> That's exactly why I didn't bother you. :)
> Let's give upstream a bit more time to fix #684990 and then see how it goes.
Fine for me.
More information about the Debian-med-packaging