You are not logged in.
The recent LibreOffice update (4.0.2-1 -> 4.0.2-2) does not work for me:
1 :: Synchronizing package databases...
2 core is up to date
3 extra is up to date
4 community is up to date
5 multilib is up to date
6 :: Starting full system upgrade...
7 resolving dependencies...
8 looking for inter-conflicts...
9 Packages (15): libreoffice-base-4.0.2-2 libreoffice-calc-4.0.2-2 libreoffice-common-4.0.2-2 libreoffice-draw-4.0.2-2 libreoffice-gnome-4.0.2-2 libreoffice-impress-4.0.2-2 libreoffice-kde4-4.0.2-2 libreoffice-math-4.0.2-2 libreoffice-postgresql-connector-4.0.2-2 libreoffice-sdk-4.0.2-2 libreoffice-sdk-doc-4.0.2-2 libreoffice-writer-4.0.2-2 psmisc-22.20-1 subversion-1.7.9-1 youtube-dl-2013.04.03-1
10 Total Installed Size: 408.96 MiB
11 Net Upgrade Size: 80.77 MiB
12 checking keyring...
13 checking package integrity...
14 loading package files...
15 checking for file conflicts...
16 libreoffice-sdk-doc: /usr/lib/libreoffice/sdk/docs exists in filesystem
17 libreoffice-sdk-doc: /usr/lib/libreoffice/sdk/examples/CLI/CSharp/Spreadsheet/GeneralTableSample.cs exists in filesystem
18 libreoffice-sdk-doc: /usr/lib/libreoffice/sdk/examples/CLI/CSharp/Spreadsheet/Makefile exists in filesystem
19 libreoffice-sdk-doc: /usr/lib/libreoffice/sdk/examples/CLI/CSharp/Spreadsheet/SpreadsheetDocHelper.cs exists in filesystem
20 libreoffice-sdk-doc: /usr/lib/libreoffice/sdk/examples/CLI/CSharp/Spreadsheet/SpreadsheetSample.cs exists in filesystem
.....
10140 libreoffice-writer: /usr/lib/libreoffice/program/libmswordlo.so exists in filesystem
10141 libreoffice-writer: /usr/lib/libreoffice/program/libswdlo.so exists in filesystem
10142 libreoffice-writer: /usr/lib/libreoffice/program/libswuilo.so exists in filesystem
10143 libreoffice-writer: /usr/lib/libreoffice/program/libt602filterlo.so exists in filesystem
10144 libreoffice-writer: /usr/lib/libreoffice/program/libwpftwriterlo.so exists in filesystem
10145 libreoffice-writer: /usr/lib/libreoffice/program/libwriterfilterlo.so exists in filesystem
10146 libreoffice-writer: /usr/lib/libreoffice/program/swriter exists in filesystem
10147 libreoffice-writer: /usr/lib/libreoffice/program/vbaswobj.uno.so exists in filesystem
10148 libreoffice-writer: /usr/share/applications/libreoffice-writer.desktop exists in filesystem
10149 libreoffice-writer: /usr/share/man/man1/loweb.1.gz exists in filesystem
10150 libreoffice-writer: /usr/share/man/man1/lowriter.1.gz exists in filesystem
10151 Errors occurred, no packages were upgraded.According to e.g.
pacman -Qo /usr/share/doc/libreoffice/sdk/index.html
all those files are apparently not owned by any package anymore. So now I'm not sure how to fix this. Manually removing 10,000 files is not really an option.
Last edited by Morn (2013-04-07 18:23:12)
Offline
You've either manually installed those files yourself, or you've deleted pacman's database entry for those packages, or you've got bigger problems (filesystem corruption or a disk failing). Establish which problem you have before preceding, if you have a bad disk then you should migrate to a new one asap.
Last edited by WorMzy (2013-04-07 11:23:23)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I have not installed those files manually, and so far there have never been problems with LibreOffice updates. Could this be a pacman 4.1 issue?
Oh well, I suppose checking the hard disk is always a good idea, so I'll start with that.
P.S. The drive has passed the short S.M.A.R.T. test; the long test will take about 90 minutes…
Last edited by Morn (2013-04-07 11:50:12)
Offline
since this is no major package, forcing it should be totally safe. worst that can happen is to have some corpse-files in your filesystem that are not used anymore.
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
Sure, I could ignore the errors and force the update, but I agree with Wormzy that it's better to get to the bottom of this—especially as I've never seen this problem before. It might be due to a hardware or filesystem issue or an obscure pacman 4.1 bug, so it's better to narrow this down a bit…
Offline
Results from the extended S.M.A.R.T. test have also been OK. So I think this is a software issue.
Offline
Have you checked the files with pacman -Qo?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Online
Have you checked the files with pacman -Qo?
Yes (see the first post), they do not seem to belong to any package at the moment.
When I try to list files for an affected package, the listing is empty :
$ pacman -Ql libreoffice-writer
$although libreoffice-writer 4.0.2-1 is still installed:
$ pacman -Q|grep writer
libreoffice-writer 4.0.2-1But installation size is zero KB:
$ pacman -Qi libreoffice-writer
Name : libreoffice-writer
Version : 4.0.2-1
Description : None
Architecture : None
URL : None
Licenses : None
Groups : None
Provides : None
Depends On : None
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 0.00 KiB
Packager : None
Build Date : None
Install Date : None
Install Reason : Explicitly installed
Install Script : Yes
Validated By : UnknownLast edited by Morn (2013-04-07 14:58:25)
Offline
Your pacman database got damaged, there could be more of these ghost packages. Out of curiosity, what are SMART values of Reallocated_Sector_Ct, Current_Pending_Sector, Offline_Uncorrectable, also 'ATA Error Count'? This is a rough indicator of your drive's overall health. If it's fine, something else damaged the database. You should definitely check if there's more of packages like that.
Last edited by kaszak696 (2013-04-07 15:12:25)
'What can be asserted without evidence can also be dismissed without evidence.' - Christopher Hitchens
'There's no such thing as addiction, there's only things that you enjoy doing more than life.' - Doug Stanhope
GitHub Junkyard
Offline
I have checked all installed packages now —three packages have an installed size of zero: ld-lsb, libreoffice-sdk-doc, and libreoffice-writer.
Name : ld-lsb
Version : 3-5
Description : Faking a Linux Standard Base runtime
Architecture : any
URL : http://www.linuxfoundation.org/
Licenses : GPL
Groups : None
Provides : None
Depends On : lib32-glibc
Optional Deps : None
Required By : google-earth
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 0.00 KiB
Packager : Unknown Packager
Build Date : Sat Jan 5 21:10:57 2013
Install Date : Sat Jan 5 21:11:03 2013
Install Reason : Explicitly installed
Install Script : No
Validated By : Unknown
Name : libreoffice-sdk-doc
Version : 4.0.2-1
Description : None
Architecture : None
URL : None
Licenses : None
Groups : None
Provides : None
Depends On : None
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 0.00 KiB
Packager : None
Build Date : None
Install Date : None
Install Reason : Explicitly installed
Install Script : No
Validated By : UnknownThe HD sector counts seem to be OK (zero). I don't see ATA Error Count though:
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 120 099 006 Pre-fail Always - 242853749
3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1252
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 24532724
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1839
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1251
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 154
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 065 057 045 Old_age Always - 35 (Min/Max 26/37)
194 Temperature_Celsius 0x0022 035 043 000 Old_age Always - 35 (0 20 0 0 0)
195 Hardware_ECC_Recovered 0x001a 037 025 000 Old_age Always - 242853749
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 6910602384235
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1349605584
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3014763168Last edited by Morn (2013-04-07 15:58:10)
Offline
I suppose I should have posted this thread under "Pacman & Package Upgrade Issues". Is there a way to move this?
Offline
I suppose I should have posted this thread under "Pacman & Package Upgrade Issues". Is there a way to move this?
Done. In the future, go ahead and use the 'report' link and leave a request for the moderators. That way the request is obvious to us rather than our just having stumbling across them.
Thanks.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Done. In the future, go ahead and use the 'report' link and leave a request for the moderators. That way the request is obvious to us rather than our just having stumbling across them.
Thanks ewaller!
As for the three damaged packages, I've now reinstalled them with "--force" from the local pacman cache. Maybe I should run "pacman -Qi|grep ' 0.00'" from time to time to check if any new database corruption occurs.
Last edited by Morn (2013-04-07 17:19:11)
Offline
P.S. Today the problem has occured again, this time with python2:
Name : python2
Version : 2.7.4-1
Description : None
Architecture : None
URL : None
Licenses : None
Groups : None
Provides : None
Depends On : None
Optional Deps : None
Required By : bluez boodler fontforge gdb grailbrowser inkscape iotop ipython2 kdesdk-dev-scripts
kdesdk-kcachegrind lash libieee1284 libkate libplist lilv lyx mercurial mididings
mlt-python-bindings mutagen mypaint perf pkgbrowser pyching pycups pyglet pygoocanvas
pyscape pysmbc pysol-sound-server pysolfc python-pmw python-xynehttpserver python2-cairo
python2-crypto python2-dateutil python2-dbus python2-distribute python2-feedparser
python2-gnomevfs python2-gobject2 python2-httplib2 python2-imaging python2-lxml python2-numpy
python2-protobuf python2-pyaudio python2-pycurl python2-pyenchant python2-pytz
python2-reportlab python2-sip python2-six python2-sympy python2-xdg python2-zope-interface
scons trelby wxpython
Optional For : alsa-lib boost cegui claws-mail git glib2 graphviz libevent libglade libnewt libproxy
lirc-utils mediawiki net-snmp openimageio subversion talloc tdb texlive-core usbutils
Conflicts With : None
Replaces : None
Installed Size : 0.00 KiB
Packager : None
Build Date : None
Install Date : None
Install Reason : Explicitly installed
Install Script : No
Validated By : UnknownThis happened after I had to power cycle the machine manually because either the 3.8.5 kernel or systemd got stuck during powerdown and failed to reboot. So it looks like this will also corrupt the pacman database, even though pacman wasn't running at the time of reboot.
Offline