4 messages · Liviu Andronic, Dirk Eddelbuettel
Dear all Recently I noticed that there are name clashes between the packages proposed in the Debian testing repos and cran2deb. For example, Synaptic proposes to upgrade from xtable 1.5-6-1cran1 (cran2deb, up-to-date CRAN version) to 1.5.5-1 (testing, older version). Is there anything that can be done about these clashes? Liviu
Do you know how to read? http://www.alienetworks.com/srtest.cfm Do you know how to write? http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail
| Dear all | Recently I noticed that there are name clashes between the packages | proposed in the Debian testing repos and cran2deb. For example, | Synaptic proposes to upgrade from xtable | 1.5-6-1cran1 (cran2deb, up-to-date CRAN version) to | 1.5.5-1 (testing, older version). | | Is there anything that can be done about these clashes? Fix the version number in the (manually packaged) xtable package? So maybe you want to file a Debian bug report. And this is not a 'name clash'. This is the same package from two different repositories, which happens all the time (eg when you look at Debian testing and unstable, or Debian and CRAN, or...). It is simply bug in the version number chosen that leads to 1.5.5 sorting higher than 1.5-6. Unfortunately we used to default to a.b.c (ie all dots) before we switched to adopting whatever CRAN has: a.b-c, a-b-c, .... so there may be more cases. Dirk
Three out of two people have difficulties with fractions.
Hello
Fix the version number in the (manually packaged) xtable package? So maybe you want to file a Debian bug report.
I checked several packages and it seems that generally Debian-supported packages follow CRAN numbering. A bug report would indeed make sense.
And this is not a 'name clash'. This is the same package from two different repositories, which happens all the time (eg when you look at Debian testing and unstable, or Debian and CRAN, or...). It is simply bug in the version number chosen that leads to 1.5.5 sorting higher than 1.5-6.
Would it be possible to make the cran2deb repository preferred over the Debian testing one? Similar to setting, for example, 'testing' as the target distribution (that is preferred over 'unstable', 'stable', etc.). Thank you Liviu
| Hello |
| > Fix the version number in the (manually packaged) xtable package? So maybe | > you want to file a Debian bug report. | > | I checked several packages and it seems that generally | Debian-supported packages follow CRAN numbering. A bug report would | indeed make sense. And bug report #556295 appears to have been filed. | > And this is not a 'name clash'. This is the same package from two different | > repositories, which happens all the time (eg when you look at Debian testing | > and unstable, or Debian and CRAN, or...). It is simply bug in the version | > number chosen that leads to 1.5.5 sorting higher than 1.5-6. | > | Would it be possible to make the cran2deb repository preferred over | the Debian testing one? Similar to setting, for example, 'testing' as | the target distribution (that is preferred over 'unstable', 'stable', | etc.). Yes, Maybe you can work it out with the apt-pinning documentation? I am not sure if this can overcome the sort logic of dpkg et al though. For packages that you notice that are sorting wrongly, maybe you have to resort to installing neither version with the package management system but rather fall back to CRAN and install.packages() ? Dirk
Three out of two people have difficulties with fractions.