search for: 1bionic

...gt; >>>> > >>>> Viktor > >>>> > >>>> > >>> Then why isn't it trying to upgrade libldb1 ? > >>> > >>> Louis's repo has: > >>> > >>> bionic-samba410|main|amd64: libldb1 2:1.5.5-1bionic~1 > >>> > >>> A bit more searching in your initial post turns this up: > >>> > >>> Unpacking libldb1:amd64 (2:1.5.5-1bionic~1) over > >>> (2:1.5.4-1ubuntu1.2) ... > >>> dpkg: error processing archive > >>> /var/cac...

...? >>> >>> Rowland >>> >>> >> Yes, apt update, then apt upgrade, as usual. >> >> Viktor >> >> > Then why isn't it trying to upgrade libldb1 ? > > Louis's repo has: > > bionic-samba410|main|amd64: libldb1 2:1.5.5-1bionic~1 > > A bit more searching in your initial post turns this up: > > Unpacking libldb1:amd64 (2:1.5.5-1bionic~1) over (2:1.5.4-1ubuntu1.2) ... > dpkg: error processing archive > /var/cache/apt/archives/libldb1_2%3a1.5.5-1bionic~1_amd64.deb (--unpack): > trying to overwrite '/...

...and this appeared to work. Next I did sudo apt update and this seemed to run OK; lots of output, but no error messages. Finally I did sudo apt-get install r-base This too seemed to run without complaint. It *said* it was installing r-base 3.5.2: > Preparing to unpack .../r-base_3.5.2-1bionic_all.deb ... > Unpacking r-base (3.5.2-1bionic) ... > Setting up r-base (3.5.2-1bionic) ... But when, after having done this install, I typed "R" I again got "R: Command not found." And typing "whereis R" produced "R:". I.e., nowhere. The install pro...

...fle, with which I have been boring this list, I managed to do: sudo apt-get dist-upgrade without getting error messages. I was told that there was nothing to do. I then (to make sure?) did: sudo apt-get install r-base and was told: > r-base is already the newest version (3.5.2-1bionic). > 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. However when I run R I get version 3.5.1. I did: whereis R and got: > /usr/bin/R /usr/lib/R /usr/lib64/R /etc/R /usr/local/lib/R /usr/share > /usr/share/man/man1/R.1.gz /usr/share/man/man1/R.1 I have tried a...

...ked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++-================-=============-=============-====================================== > ii r-base-core 3.5.2-1bionic amd64 GNU R core of statistical computation So indeed the installation had not actually been done. The nature of the message prompted me to try sudo apt purge r-base-core which ran and said that it was removing a whole lot of stuff. I then tried sudo apt-get install r-base...

...t; |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > | > | > ||/ Name Version Architecture Description > | > | > > +++-================-=============-=============-====================================== > | > | > ii r-base-core 3.5.2-1bionic amd64 GNU R core of > statistical computation > | > | > | > | So indeed the installation had not actually been done. > | > > | > Why do you say that? That is the __normal__ display after a > successful installation. > | > | I interpreted the "Status...

Rolf, I think it may help to read-up on dpkg and apt. Instead of 'whereis' do dpkg -l r-base-core to see the content of that package. Use apt-cache policy r-base-core to see what the package cache says about where it gets the package from. And so on. Also type -p R which R will tell where your system thinks R comes from. If you install R 3.5.2 you should not see R 3.5.1.

...rig-pend | > | > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) | > | > ||/ Name Version Architecture Description | > | > +++-================-=============-=============-====================================== | > | > ii r-base-core 3.5.2-1bionic amd64 GNU R core of statistical computation | > | | > | So indeed the installation had not actually been done. | > | > Why do you say that? That is the __normal__ display after a successful installation. | | I interpreted the "Status=Not/Inst ...." to mean that the...

On 22.09.2019 15:07, Rowland penny via samba wrote: > On 22/09/2019 13:53, Viktor Trojanovic via samba wrote: >> I just ran "apt upgrade" on my DC (Ubuntu 18.04, Samba 4.10 from Louis >> Repo) and it ended with error messages about unmet dependencies in >> regards >> to libldb1. >> > Yes, but did you run 'apt-get update' first ? > >

...-aWait/Trig-pend > | > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > | > ||/ Name Version Architecture Description > | > +++-================-=============-=============-====================================== > | > ii r-base-core 3.5.2-1bionic amd64 GNU R core of statistical computation > | > | So indeed the installation had not actually been done. > > Why do you say that? That is the __normal__ display after a successful installation. I interpreted the "Status=Not/Inst ...." to mean that the package was...

Dear Debian persons I would like enquire about whether the repository deb https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ I tried to follow the instructions and I cannot get R3.5.1 - I get R3.4.4??? I have been able to install R3.5.1 on Ubuntu 16.02 using the xenial-cran35/ repository & so not sure if the bionic link is up to date? thanks in advance Regards Alison

...ards to libldb1. root at DC1:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-ldb : Depends: libldb1 (= 2:1.5.5-1bionic~1) but 2:1.5.4-1ubuntu1.2 is installed python3-samba : Depends: libldb1 (>= 2:1.5.5~) but 2:1.5.4-1ubuntu1.2 is installed Recommends: python3-gpg but it is not installed samba : Depends: libldb1 (>= 2:1.5.5~) but 2:1.5.4-1ubuntu1.2 is installed samba-dsdb-modules : Depends...

...-conf/Half-inst/trig-aWait/Trig-pend | > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) | > ||/ Name Version Architecture Description | > +++-================-=============-=============-====================================== | > ii r-base-core 3.5.2-1bionic amd64 GNU R core of statistical computation | | So indeed the installation had not actually been done. Why do you say that? That is the __normal__ display after a successful installation. | The nature of the message prompted me to try | | sudo apt purge r-base-core | | which ra...

...> >>>> >>> Yes, apt update, then apt upgrade, as usual. >>> >>> Viktor >>> >>> >> Then why isn't it trying to upgrade libldb1 ? >> >> Louis's repo has: >> >> bionic-samba410|main|amd64: libldb1 2:1.5.5-1bionic~1 >> >> A bit more searching in your initial post turns this up: >> >> Unpacking libldb1:amd64 (2:1.5.5-1bionic~1) over (2:1.5.4-1ubuntu1.2) >> ... >> dpkg: error processing archive >> /var/cache/apt/archives/libldb1_2%3a1.5.5-1bionic~1_amd64.deb >>...

...t;> Yes, but did you run 'apt-get update' first ? >> >> Rowland >> >> > Yes, apt update, then apt upgrade, as usual. > > Viktor > > Then why isn't it trying to upgrade libldb1 ? Louis's repo has: bionic-samba410|main|amd64: libldb1 2:1.5.5-1bionic~1 A bit more searching in your initial post turns this up: Unpacking libldb1:amd64 (2:1.5.5-1bionic~1) over (2:1.5.4-1ubuntu1.2) ... dpkg: error processing archive /var/cache/apt/archives/libldb1_2%3a1.5.5-1bionic~1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/ldb/libl...

...gt;>>>>> > >>>>>> > >>>>> Then why isn't it trying to upgrade libldb1 ? > >>>>> > >>>>> Louis's repo has: > >>>>> > >>>>> bionic-samba410|main|amd64: libldb1 2:1.5.5-1bionic~1 > >>>>> > >>>>> A bit more searching in your initial post turns this up: > >>>>> > >>>>> Unpacking libldb1:amd64 (2:1.5.5-1bionic~1) over > >>>>> (2:1.5.4-1ubuntu1.2) ... > >>>>> dpkg: erro...

...r me on multiple machines: | | edd at rob:~$ lsb_release -a | No LSB modules are available. | Distributor ID: Ubuntu | Description: Ubuntu 18.04 LTS | Release: 18.04 | Codename: bionic | edd at rob:~$ apt-cache policy r-base-core | r-base-core: | Installed: 3.5.1-1bionic | Candidate: 3.5.1-1bionic | Version table: | *** 3.5.1-1bionic 500 | 500 https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ Packages | 100 /var/lib/dpkg/status | 3.5.0-1bionic 500 | 500 https://cloud.r-project.org/bin/linux/ubuntu bionic-cra...

...an.r-project.org/bin/linux/ubuntu/README.html to install R 3.5 and 3.6 (R 3.4 comes as part of Ubuntu bionic). Recently a user reported that R 3.5 builds had stopped working with the following error message: The following packages have unmet dependencies: r-base : Depends: r-recommended (= 3.5.3-1bionic) but 3.6.1-3bionic is to be installed Recommends: r-base-html but it is not going to be installed E: Unable to correct problems, you have held broken packages. Which is the output of running (something like) `apt-get install --yes r-base=3.5.3-1bionic r-base-dev=3.5.3-1bionic libclang-de...

...bution 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_ o...

...debconf: delaying package configuration, since apt-utils is not installed (Reading database ... 19227 files and directories currently installed.) Preparing to unpack .../r-base-core_3.6.0-2bionic_amd64.deb ... Unpacking r-base-core (3.6.0-2bionic) over (3.6.0-1bionic) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up r-base-core (3.6.0-2bionic) ... Installing new version of config file /etc/R/Makeconf ... Installing new version of config file /etc/R/Renviron.site ... root at 940cde4f092f:/# -- http://dirk.eddelbuettel.com | @eddelbuettel |...