Oliver Grawert schreef op 27-09-2016 18:35:
hi,
Am Dienstag, den 27.09.2016, 08:51 -0700 schrieb paulwhee...@cox.net:
Package info: Version: 1:5.1.4-0ubuntu1 (xenial-updates)
Unless I am mistaken, you are the package maintainers, so it does not
matter what Linux system it is installed on,
Here is some update. My script does not use linux-version anymore. But I named
the script linux-purge. It can remove kernels even in some problem cases where
e.g. there are dependency problems due to an unsuccessful kernel update (e.g.
due to full /boot partition). It provides optional UI for
On 27 September 2016 at 19:57, Jarno Suni wrote:
> Hi
>
> I have installed nautilus-dropbox on Trusty. Now it tells I have to update in
> order to continue using the product. If I follow instructions, I am guided to
> install a .deb that conflicts nautilus-dropbox. How to
Hi
I have installed nautilus-dropbox on Trusty. Now it tells I have to update in
order to continue using the product. If I follow instructions, I am guided to
install a .deb that conflicts nautilus-dropbox. How to proceed?
--
Jarno Suni - http://iki.fi/8/
--
Ubuntu-devel-discuss mailing
On Tue, 2016-09-27 at 08:51 -0700, paulwhee...@cox.net wrote:
> I attempted to install LibreOffice (office productivity suite
> (metapackage)) on my mint Linux system.
> 1. Synaptic said the package was broken - Image 1. I changed
> repositories and got it to install.
> 2. However, it would not
hi,
Am Dienstag, den 27.09.2016, 08:51 -0700 schrieb paulwhee...@cox.net:
>
> Package info: Version: 1:5.1.4-0ubuntu1 (xenial-updates)
>
>
> Unless I am mistaken, you are the package maintainers, so it does not
> matter what Linux system it is installed on, it should work, right?
yes, these
I attempted to install LibreOffice (office productivity suite
(metapackage)) on my mint Linux system.
1. Synaptic said the package was broken - Image 1. I changed
repositories and got it to install.
2. However, it would not start. Found that it had been installed as a
file owned by root, so
On Tue, Sep 27, 2016 at 12:48 AM, Simon Quigley wrote:
>> In other words, it was only committed to master after the gimp-2-8
>> branch was made; and there's no evidence that this was cherry-picked
>> onto the gimp-2-8 branch (from a quick log inspection). It indeed does
>>