Re: GHDL and Gnat-4.8.2
Joris van Rantwijk <firstname.lastname@example.org> writes:
> Hi Ludovic,
> On 2013-11-30, Ludovic Brenta wrote:
>> Note that gcc-4.6 and gcc-4.7 will be removed from Debian before the
>> next release becomes stable, so targetting gcc-4.7-source is probably
>> not going to allow transition to testing.
> I don't understand completely. At this moment gcc-4.7-source is
> available in testing. Does the upload queue nevertheless already know
> that gcc-4.7-source is going to be removed?
Yes, they (the human release managers) do.
>> It is OK to upload to unstable as a stop-gap measure, though. This
>> will allow the package to go through the NEW queue; this requires
>> manual review & approval by a Debian release manager, so normally
>> takes time.
> Why would the package go through the NEW queue? There is still an old
> ghdl package in unstable.
Ah, I wasn't aware of that. In that case, the next upload will bypass
the NEW queue and go directly to unstable. It might never transition to
testing, though; or it might transition and then be removed from testing
when gcc-4.7-source is removed.
> I'm probably asking beginners questions. The system of uploading
> Debian packages is completely new to me, so I will have to learn some
> things. I do understand the inside of Debian source packages though,
> and I'm aware of the policy that covers it. But uploading is another
>> So, please do not wait for the package to hit testing before you
>> upload an update that uses gcc-4.8-source; this is the official
>> target for Jessie.
> Ok, in that case I will just wait until upstream feels confident that
> the GCC 4.8 transition is done.
On the contrary, do not wait. Release early, release often.
Upstream is probably counting on you to perform the transition to
gcc-4.8-source, or at least to help with it. Also, by your own
admission, nobody is going to install GHDL based on gcc-4.8-source and
test it unless *you* provide the binary packages. You can work on this
transition while your package based on gcc-4.7-source awaits review and
upload. That's what version control systems are for :)
The initial review and upload might take time and Nicolas and myself
might bother you with pesky details like adherence to the Debian Policy.
And we didn't get our Debian Developer status by being lax about details
:) This work can also take place in parallel with the transition to