Skip to content

Problem with Ubuntu bionic R 3.5

10 messages · Ulrich Leuchtmann, Luke Tudge, Michael Rutter +1 more

#
I ran into a problem installing R 3.5 on Ubuntu Bionic Beaver. In file 
/etc/apt/sources.list I added the repository entry "deb 
https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/". But 
"apt-get update" now produces an error message:

W: Konflikt bei Distribution: 
https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ InRelease 
(bionic-cran35/ erwartet, aber bionic bekommen)

In english, this should read something like

W: conflict in distribution: 
https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ InRelease 
(bionic-cran35/ expected, but bionic received)

It seems as if the new bionic R-3.5 distribution is not set up properly. 
I wonder if the "Codename" entry or the "Suite" entry in the 
/bin/linux/ubuntu/bionic-cran35/InRelease file should read 
"bionic-cran35" instead of "bionic".

Uli
#
I have this too on Ubuntu Bionic. The English error message is:

W: Conflicting distribution: https://cran.rstudio.com/bin/linux/ubuntu
bionic-cran35/ InRelease (expected bionic-cran35/ but got bionic)

Though the error doesn't seem to prevent use of the repository. I could
apt-get install R 3.5 no problem.



On Wed, Jun 13, 2018 at 2:04 PM, Ulrich Leuchtmann <
ulrich.leuchtmann at t-online.de> wrote:

            

  
  
#
On 13 June 2018 at 14:17, Luke Tudge wrote:
| I have this too on Ubuntu Bionic. The English error message is:
| 
| W: Conflicting distribution: https://cran.rstudio.com/bin/linux/ubuntu
| bionic-cran35/ InRelease (expected bionic-cran35/ but got bionic)
| 
| Though the error doesn't seem to prevent use of the repository. I could
| apt-get install R 3.5 no problem.

Ok -- that may just be a label in the metadata file.

Michael is currently traveling but I am sure he'll take a look.

Dirk
#
Great. Many thanks. BTW: Synaptic is refusing to install R due to this 
issue.

Uli


Am 13.06.2018 um 14:32 schrieb Dirk Eddelbuettel:
3 days later
#
Hi Dirk.

I saw you installed a new release. Unfortunately the problem mentioned 
below does persist.

I know this is perhaps a minor issue, as users report they can install 
manually (see below). But under strict installation policies this can 
create an issue. Synaptic is refusing to install. The German error 
message is

"Die ?nderungen konnten nicht angewendet werden! Bitte zuerst die 
Probleme mit defekten Paketen beheben."

In English this should read something like "The change could not be 
applied. Solve problems with broken packages first."

Regards

Uli


Am 13.06.2018 um 14:32 schrieb Dirk Eddelbuettel:
#
Ulrich,
On 16 June 2018 at 15:04, Ulrich Leuchtmann wrote:
| Hi Dirk.
| 
| I saw you installed a new release. Unfortunately the problem mentioned 
| below does persist.

The Ubuntu side of things is mostly Michael's work.
 
| I know this is perhaps a minor issue, as users report they can install 
| manually (see below). But under strict installation policies this can 
| create an issue. Synaptic is refusing to install. The German error 
| message is
| 
| "Die ?nderungen konnten nicht angewendet werden! Bitte zuerst die 
| Probleme mit defekten Paketen beheben."
| 
| In English this should read something like "The change could not be 
| applied. Solve problems with broken packages first."

I can still read my native tongue :)

I think Michael works mostly with virtual machines where the installation is
not as minimal. We can (and should have) tested this some more with for
example a Docker container.  Sorry about the inconvenience but I think we can
get this sorted out in a few days.

Dirk
 
| Regards
| 
| Uli
| 
| 
| Am 13.06.2018 um 14:32 schrieb Dirk Eddelbuettel:
| > On 13 June 2018 at 14:17, Luke Tudge wrote:
| > | I have this too on Ubuntu Bionic. The English error message is:
| > |
| > | W: Conflicting distribution: https://cran.rstudio.com/bin/linux/ubuntu
| > | bionic-cran35/ InRelease (expected bionic-cran35/ but got bionic)
| > |
| > | Though the error doesn't seem to prevent use of the repository. I could
| > | apt-get install R 3.5 no problem.
| >
| > Ok -- that may just be a label in the metadata file.
| >
| > Michael is currently traveling but I am sure he'll take a look.
| >
| > Dirk
| >
|
#
On 06/16/2018 09:22 AM, Dirk Eddelbuettel wrote:
My apologizes, I had an error in the apt configuration file.  I have 
corrected the error and tested it in docker.  Should resolve itself the 
next time the CRAN servers sync.

Michael
1 day later
#
Hi Michael.

I fear I'm becoming a pain in your back. Sorry.

The problem with the "Components" and "Suite" name in the "InRelease" 
file for bionic-cran35 has been solved. *Many thanks for that.* However, 
"sudo apt-get install r-base" creates an error message (again here the 
German version):

ulrich at linuxdesktop:~$ sudo apt-get install r-base
Paketlisten werden gelesen... Fertig
Abh?ngigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unm?gliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu l?sen:

Die folgenden Pakete haben unerf?llte Abh?ngigkeiten:
 ?r-base : H?ngt ab von: r-recommended (= 3.5.0-1bionic) soll aber nicht 
installiert werden
E: Probleme k?nnen nicht korrigiert werden, Sie haben zur?ckgehaltene 
defekte Pakete.

That's something new. I know, I could probably solve this problem by

 ??? sudo apt-get install r-base r-recommended

But somehow I am puzzled that r-base now _depends_ on r-recommended. Is 
that the way it is supposed to be now? In this case I think the 
installation instruction on CRAN would need to get updated. Or is this 
an error in the dependencies?

Best regards

Uli




Am 17.06.2018 um 03:33 schrieb Michael Rutter:
#
On 18 June 2018 at 18:38, Ulrich Leuchtmann wrote:
| Hi Michael.
| 
| I fear I'm becoming a pain in your back. Sorry.
| 
| The problem with the "Components" and "Suite" name in the "InRelease" 
| file for bionic-cran35 has been solved. *Many thanks for that.* However, 
| "sudo apt-get install r-base" creates an error message (again here the 
| German version):
| 
| ulrich at linuxdesktop:~$ sudo apt-get install r-base
| Paketlisten werden gelesen... Fertig
| Abh?ngigkeitsbaum wird aufgebaut.
| Statusinformationen werden eingelesen.... Fertig
| Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
| Sie eine unm?gliche Situation angefordert haben oder, wenn Sie die
| Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
| nicht erstellt wurden oder Incoming noch nicht verlassen haben.
| Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu l?sen:
| 
| Die folgenden Pakete haben unerf?llte Abh?ngigkeiten:
|  ?r-base : H?ngt ab von: r-recommended (= 3.5.0-1bionic) soll aber nicht 
| installiert werden
| E: Probleme k?nnen nicht korrigiert werden, Sie haben zur?ckgehaltene 
| defekte Pakete.
| 
| That's something new. I know, I could probably solve this problem by
| 
|  ??? sudo apt-get install r-base r-recommended

That is normal.

r-base does not depend on r-recommended, but suggests it.

r-recommended however does depend on a given version of R, and apt just tells
you that _given that you have r-recommended installed_ it can not upgrade
r-base. As such your request of 'install me just r-base, please' was not
satisfiable.

I keep forgetting which of the two deals smoothly with it, but between
'apt-get dist-upgrade' and 'apt-get update' one does; I think it is the
former which I use way more.

Hth, Dirk
| 
| But somehow I am puzzled that r-base now _depends_ on r-recommended. Is 
| that the way it is supposed to be now? In this case I think the 
| installation instruction on CRAN would need to get updated. Or is this 
| an error in the dependencies?
| 
| Best regards
| 
| Uli
| 
| 
| 
| 
| Am 17.06.2018 um 03:33 schrieb Michael Rutter:
| >
| >
| > On 06/16/2018 09:22 AM, Dirk Eddelbuettel wrote:
| >>
| >> Ulrich,
| >>
| >> On 16 June 2018 at 15:04, Ulrich Leuchtmann wrote:
| >> | Hi Dirk.
| >> |
| >> | I saw you installed a new release. Unfortunately the problem mentioned
| >> | below does persist.
| >>
| >> The Ubuntu side of things is mostly Michael's work.
| >> ? | I know this is perhaps a minor issue, as users report they can 
| >> install
| >> | manually (see below). But under strict installation policies this can
| >> | create an issue. Synaptic is refusing to install. The German error
| >> | message is
| >> |
| >> | "Die ?nderungen konnten nicht angewendet werden! Bitte zuerst die
| >> | Probleme mit defekten Paketen beheben."
| >> |
| >> | In English this should read something like "The change could not be
| >> | applied. Solve problems with broken packages first."
| >>
| >> I can still read my native tongue :)
| >>
| >> I think Michael works mostly with virtual machines where the 
| >> installation is
| >> not as minimal. We can (and should have) tested this some more with for
| >> example a Docker container.? Sorry about the inconvenience but I 
| >> think we can
| >> get this sorted out in a few days.
| >>
| >> Dirk
| >
| > My apologizes, I had an error in the apt configuration file.? I have 
| > corrected the error and tested it in docker.? Should resolve itself 
| > the next time the CRAN servers sync.
| >
| > Michael
| >
| > _______________________________________________
| > R-SIG-Debian mailing list
| > R-SIG-Debian at r-project.org
| > https://stat.ethz.ch/mailman/listinfo/r-sig-debian
| 
| _______________________________________________
| R-SIG-Debian mailing list
| R-SIG-Debian at r-project.org
| https://stat.ethz.ch/mailman/listinfo/r-sig-debian
#
On Mon, Jun 18, 2018 at 12:38 PM Ulrich Leuchtmann <
ulrich.leuchtmann at t-online.de> wrote:

            
Uli,

Thanks for the email.  Confirmed the issue, but it took me a bit to find
the reason.  Turns out some of the packages have a label of "Bionic" vs.
"bionic" and my mirroring script missed those.  I believe the issues is now
fixed.  Things should work after the next mirror sync.

Michael