clone 704805 -1
retitle -1 Partial upgrades from wheezy to jessie are broken
severity -1 normal
thanks

Le 29/05/2013 13:56, Julian Gilbey a écrit :
> On Wed, May 29, 2013 at 01:02:02PM +0200, Vincent Danjean wrote:
>> 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?
> 
> You are correct - it would not work.
[...]
> I personally think (and I am not an R maintainer) that a very long
> list (potentially thousands if external packages are included) of
> breaks is unhelpful and an unnecessary effort.
> 
> The breakage that a broken partial upgrade will cause is local and
> easily identifiable (as R tells you it's broken when you try to use an
> old module).  Not nice, for sure; not ideal, agreed. But it's
> survivable, the issue will affect very few people (only those doing
> partial upgrades), and is easy to fix.

* R users on a machine are not always root users.
* the problems will occurs to more and more users that will do
  an "apt-get install r-cran-newpackage-in-jessie" that will
  pull r-base-core from jessie and let all old incompatible r-* packages
  on the machine.
  If the root user do not want to upgrade the whole machine to jessie,
  it will need to do something as:
  cd /usr/share/doc ; apt-get install -t jessie r-*
  And a bad side-effect will be that all r-package switches to a
  "manually installed" state...

So no, the problem of broken partial upgrade must be solved.

>  But as long as there is only
> one version of R in Debian (and I can't personally think of a reason
> why one would want more than one version), the idea of renaming the
> core R package to fix this one partial breakage, and then being stuck
> with this ugly new package naming convention and the technical issues
> it will bring with it for the rest of the life of Debian (a
> potentially very long time) seems unpleasant at least.
> 
>> 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.
> 
> Or the third non-ideal-but-simplest solution: keep the current
> status quo and allow partial upgrades to break on this occasion.
> 
>>   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.
> 
> Indeed, and this is what this bug report is focusing on - fixing
> things for future transitions.

The status quo seems very suboptimal to me. So I'm cloning this
bug so that we can track this issue (partial upgrade from wheezy
to jessie) separately.
  Note: I put the severity "normal" to this new bug, but I'm fairly
confident that it should be higher. Partial upgrade from release n
to release n+1 must be supported by Debian packages.

  Regards,
    Vincent


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

Reply via email to