Problem with libreoffice-common upgrade

Started by linearJim, 2016/04/09, 08:26:34

Previous topic - Next topic

linearJim

hi,

[root@siduction ~]# apt-get check
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libreoffice-style-galaxy : Depends: libreoffice-common (= 1:5.1.2-2) but 1:5.1.2~rc1-1 is installed
libreoffice-style-tango : Depends: libreoffice-common (= 1:5.1.2-2) but 1:5.1.2~rc1-1 is installed


and


[root@siduction ~]# apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libreoffice-common
Suggested packages:
  libreoffice-style-breeze libreoffice-style-hicontrast libreoffice-style-oxygen libreoffice-style-sifr
The following packages will be upgraded:
  libreoffice-common
1 upgraded, 0 newly installed, 0 to remove and 130 not upgraded.
144 not fully installed or removed.
Need to get 0 B/23.2 MB of archives.
After this operation, 2,048 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 289450 files and directories currently installed.)
Preparing to unpack .../libreoffice-common_1%3a5.1.2-2_all.deb ...
Unpacking libreoffice-common (1:5.1.2-2) over (1:5.1.2~rc1-1) ...
dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a5.1.2-2_all.deb (--unpack):
trying to overwrite '/usr/lib/libreoffice/share/xdg/qstart.desktop', which is also in package libreoffice-gtk 1:5.1.2~rc1-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or directory
rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or directory
rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or directory
rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
Processing triggers for siduction-dynamic-dms (2016.01.31) ...
Errors were encountered while processing:
/var/cache/apt/archives/libreoffice-common_1%3a5.1.2-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


anyone else with this?

dibl

#1
Hmmmm -- with LO installed and working correctly, I never thought to look further.  Here is what I have (system updated earlier today):


root@Hibiscus:/# apt policy libreoffice-common
libreoffice-common:
  Installed: 1:5.1.2-2
  Candidate: 1:5.1.2-2
  Version table:
*** 1:5.1.2-2 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        500 http://httpredir.debian.org/debian unstable/main i386 Packages
        100 /var/lib/dpkg/status
root@Hibiscus:/# apt policy libreoffice-base-core
libreoffice-base-core:
  Installed: 1:5.1.2-2
  Candidate: 1:5.1.2-2
  Version table:
*** 1:5.1.2-2 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
root@Hibiscus:/# apt policy libreoffice-style-galaxy

libreoffice-style-galaxy:
  Installed: 1:5.1.2-2
  Candidate: 1:5.1.2-2
  Version table:
*** 1:5.1.2-2 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        500 http://httpredir.debian.org/debian unstable/main i386 Packages                                                             100 /var/lib/dpkg/status root@Hibiscus:/# apt policy libreoffice
libreoffice:
  Installed: (none)
  Candidate: 1:5.1.2-2
  Version table:
     1:5.1.2-2 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
     1:5.0.4~rc2-2 0
        100 /var/lib/dpkg/status



Writer and calc are all I use, and they both work correctly.
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

linearJim

thanks for replying dibl

that is strange...but i solved it by first pinning the package to testing which allowed me to to purge the packages, then reinstalled from unstable and i believe it ok now