On 31 March 2013 at 20:25, Ansgar Burchardt wrote:
| Dirk Eddelbuettel <e...@debian.org> writes:
| > On 31 March 2013 at 19:41, Ansgar Burchardt wrote:
| > | Dirk Eddelbuettel <e...@debian.org> writes:
| > | > On 31 March 2013 at 19:12, Ansgar Burchardt wrote:
| > | > | However the binaries seem to claim they would also work with the
newer R
| > | > | versions? I looked at r-cran-rsymphony and it has
| > | > | Depends: [...], r-base-core (>= 2.14.1)
| > | >
| > | > You looked at the code from before the update of that package:
| > | >
| > | > Package: r-cran-rsymphony
| > | > Architecture: any
| > | > Depends: ${shlibs:Depends}, ${R:Depends}
| > | >
| > | > leading to
| > | >
| > | > edd@max:~$ dpkg -f
/var/cache/pbuilder/result/r-cran-rsymphony_0.1-15-2_i386.deb |grep Depends
| > | > Depends: libatlas3-base, libc6 (>= 2.1.3), libgcc1 (>= 1:4.1.1), \
| > | > libgfortran3 (>= 4.3), libquadmath0 (>= 4.6), libstdc++6 (>= 4.4.0), \
| > | > r-base-core (>= 3.0.0~20130330-1)
| > | > edd@max:~$
| > | >
| > | > | which would still be satisfied by r-base-core 3.0.0~20130330-1...
| > | >
| > | > Not an issue as seen above.
| > |
| > | That just means you cannot use the new r-cran-rsymphony with the old
| > | r-base-core. But it looks like you can use the *old* r-cran-rsymphony
| > | with the *new* r-base-core, although you said that a rebuild is required
| > | (and thus this combination shouldn't be allowed by the dependencies).
| >
| > No, sorry, that is precisely where the restriction comes in. Here is a log
| > from my laptop, running the R 3.0.0 pre-release and trying to load a
non-CRAN
| > package (of mine, at R-Forge) built with an earlier version:
|
| Please read again. You have only restrictions in *one* direction,
| i.e. you *cannot* install an *old* version of r-base-core and a *new*
| version of r-cran-rsymphony.
|
| It is however possible to install the *new* r-base-core together with
| the *old* r-cran-rsymphony. However r-cran-rsymphony will not work:
That is the very reason the 100+ r-cran-* are being updated.
| ----
| $ R
| [...]
| > library(Rsymphony)
| Error: package 'Rsymphony' was built before R 3.0.0: please re-install it
| ----
|
| For reference, the installed versions are:
| r-base-core 3.0.0~20130330-1
| r-cran-rsymphony 0.1-15-1
If you run an update and try r-cran-rsymphony 0.1-15-2 then it will work.
| I assume this means that a non-working set of packages could also
| migrate to testing (if there was no freeze). This should probably get
| fixed, maybe with something similar to the perlapi-5.14.2 virtual
| package provided by perl(-base)?
That is why we have a meta-variable
${R:Depends}
in Depends: which gets filled by the R version that compiling the package,
currently 3.0.0~20130330-1. And which prevents the migration.
The same scheme worked before so I am not convinced we need something more
complicated or formal.
Say six month from now we may have an R patch release 3.0.1. The packages
being built now (using the rc for R 3.0.0) will work.
But none of the R 2.* packages will, now or then, which is why we need this
rebuild process now.
Testing is fine, but within unstable the transition has to be done.
I hope this helps and clarifies.
Dirk
--
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20824.33290.289506.149...@max.nulle.part
