Le 29/05/2013 11:46, Julian Gilbey a écrit :
> On Tue, May 28, 2013 at 04:20:28PM +0200, Vincent Danjean wrote:
>> Of course, all of this will really works once all packages
>> in testing/unstable depending on "r-base-core (>=3.xxx)" will
>> have disappear (ie once all of them will have been rebuilt
>> with the new dependency).
>
> There's no particular need to remove the r-base-core (>= 3.xxx)
> dependency; it could be generated *in addition to* the r-api-3.0
> dependency.
This remarks was done in the context of the rename of the
r-base-core into r-base-core3 (for example) that would conflict
with r-base-core... So, in this context, depends on
"r-base-core (>=3.xxx)" will disappear when rebuilding with
R 3.x (incompatible with previous R releases) and be replaced by
something as either:
A: "r-base-core3 (>=3.xxx)"
B: "r-base-core3 (>=3.xxx), r-base-debianapi-3"
C: "r-base-debianapi-3"
A will require another package rename if a new (abi-)incompatible R
appears.
>> Note: is you really do not want to rename you r-base-core package,
>> you can keep it but you then will need to add a versionned Breaks:
>> dependency for all previous (before R 3.x) Debian R-packages.
>> As I know that there exists lots of Debian R packages outside
>> of the main archive, it seems to me that this is a worst solution
>> as a rename of r-base-core.
>
> That is probably not necessary. Someone using testing has to be aware
> of the possibility of breakages. By the time jessie is released, in
> two or three years' time, this issue will have been resolved
How ?
Currently, R debian packages in wheezy have something as
"depends: r-base-core (>= 2.X)"
How partial upgrade to jessie would work if r-base-core is not renamed
(and conflicting with r-base-core) or if a new r-base-core does not
add a versionned breaks for all old (wheezy) R debian package?
Do you see another solution?
> everyone building external packages should have figured out the new
> system. Also, the breakages are very obvious: R tells you explicitly
> that the package needs recompiling with R 3.0.0.
I would be very disappointed if Debian does not use its dependencies
to ensure good (partial) upgrades. Having to run a software (R) and to
test each of its 'library' to know if they still work after a partial
upgrade seems plainly wrong.
> Having to rename
> r-base-core every time there is an API upgrade seems like a kludge,
The rename (or the long list of breaks) if only necessary now because
no virtual package have been used yet.
When a virtual package encoding an abi version will be introduced,
no rename will be required anymore.
So, I ask again:
What are R maintainers idea for ensuring that partial upgrades
from wheezy to jessie will work?
For myself, I see two technical solution: r-base-core rename
or long list of versionned breaks into r-base-code. Perhaps you
see other solutions.
Then, there is the problem for future transitions. Adding a
virtual abi package would allow to efficiently solve future
transitions. I also recommend this. But this is a different
problem.
Regards,
Vincent
> and there would need to be a meta-package which depends on the correct
> API version, and then people would depend on that meta-package rather
> than the correct API package....
>
> Julian
>
--
Vincent Danjean Adresse: Laboratoire LIG - Bât. INRIA Rhône-Alpes
Téléphone: +33 4 76 61 55 10 655 avenue de l'Europe
Fax: +33 4 76 61 52 52 Montbonnot Saint Martin
Email: vincent.danj...@imag.fr 38334 Saint-Ismier cedex
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
