[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#748434: libreoffice-help-en-us: No graphics in the help.



Hi,

On Tue, May 20, 2014 at 03:09:39PM +0200, Jacek Sobczak wrote:
> On Mon, May 19, 2014 at 10:59 PM, Rene Engelhard <rene@debian.org> wrote:
> 
> > Actually I apparently had -style-sifr lying around before I did the tests.
> >
> > After  cleaning that up apt-get install libreoffice libreoffice-help-en-us always
> > installs galaxy. So it should work?
> >
> > Did you specify any other theme explicitly or did you install something else
> > and remove galaxy after it? That also would explain it. (And there's no APT bug at all.)
> 
> from LO 4.1.6 to 4.2.4. As you can see from the aptitude log below I
> did it in two steps on the same day. In the log all the LO packages

Why two steps? And how did you upgrade?

apt-get dist-upgrade should have done the right thing...
(Yes, I tested that.)

> libreoffice-style-tango was removed from my system when I upgraded
[...]
> [INSTALL, DEPENDENCIES] libreoffice-style-sifr:amd64
> [REMOVE, DEPENDENCIES] libreoffice-style-galaxy:amd64

OK, clear.

-sifr installed and -galaxy removed so you ended up with only -sifr -
which exhibits this because it seems to be incomplete...[1]

> [HOLD] libreoffice-calc:amd64
> [HOLD] libreoffice-impress:amd64
> [HOLD] libreoffice-writer:amd64

Why? Did you do apt-get upgrade (which would explain this given they need
new packages installed) and _only_ then dist-upgrade? This is weird steps.
(I've seen documentation suggesting that, I still think this is questionable..)

> Will install 11 packages, and remove 7 packages.
> 8859 kB of disk space will be freed
> ===============================================================================
> [REMOVE, NOT USED] libcdr-0.0-0:amd64
> [REMOVE, NOT USED] libmspub-0.0-0:amd64
> [REMOVE, NOT USED] libvisio-0.0-0:amd64
[...]
> [REMOVE, DEPENDENCIES] libreoffice-draw:amd64
> [REMOVE, DEPENDENCIES] libreoffice-impress:amd64
> [REMOVE, DEPENDENCIES] libreoffice-math:amd64

And what did you do here? Or did you in some way enforce this manually?

Regards,

Rene

[1] https://bugs.freedesktop.org/show_bug.cgi?id=75256


Reply to: