[SOLVED] ttf-dejavu update question

mcloaked · 2016-10-31 13:09:11

In arch-announce I saw that there is a change to some symlinks in the package ttf-dejavu which needs a manual --force when updating that package for ttf-dejavu 2.35-1 -> 2.37-1. i.e. at https://www.archlinux.org/news/ttf-deja … d-upgrade/

However when I tried that I get the following:

# checkupdates 
dbus-glib 0.106-1 -> 0.108-1
libproxy 0.4.12-2 -> 0.4.13-1
libthai 0.1.24-1 -> 0.1.25-1
ttf-dejavu 2.35-1 -> 2.37-1
# pacman -S --force ttf-dejavu
warning: ttf-dejavu-2.35-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) ttf-dejavu-2.35-1

Total Installed Size:  9.18 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]

So I am perplexed - the check on updates says that ttf-dejavu should be updated to version 2.37-1 and yet trying to run the update as suggested says that it is already up to date and doesn't seem to see the new version.

Does anyone know a way around this to get ttf-dejavu to update correctly as suggested in arch-announce?

Edit: It turns out that doing:

# pacman -Syu --ignore ttf-dejavu

First and then once that is done then force updating ttf-dejavu solved the problem I posted above.

Last edited by mcloaked (2016-10-31 13:16:52)

WorMzy · 2016-10-31 13:17:23

Remember that checkupdates uses it's own package databases, so you will need to update your ~real~ package databases before you will be able to install the update. You can either:
1)

# pacman -Syu --ignore ttf-dejavu
# pacman -S --force ttf-dejavu

or 2)

# pacman -Syy
# pacman -S --force ttf-dejavu
# pacman -Su

mikaelbrun · 2016-11-01 09:11:10

I have backuped and deleted the conflicting files. I don't know if this is a safer way of doing it. I have done this with other updates lately too.
Is this not necessary, or should I have this as a good practice if I get this error in the future with other files?

Smoerrebroed · 2016-11-03 09:07:56

As the files are provided and reinstalled by another package, deleting them prior to installing/upgrading is just fine from my point of view. Works for me at least.

Lone_Wolf · 2016-11-03 09:59:05

backing up then deleting conflicting files is a good practice.

WorMzy · 2016-11-03 12:01:53

Smoerrebroed wrote:

As the files are provided and reinstalled by another package

Could you elaborate on this? Which other package provides these files?

Trilby · 2016-11-03 13:32:59

mikaelbrun wrote:

I have done this with other updates lately too.

What other updates? This should not normally happen. The ttf-dejavu package was in the front page news because this was an atypical situation. If you are getting conflicting files for other packages, something is wrong and you should figure out what it is.

fxlgore · 2016-11-05 19:56:44

thanks !! you saved my life

Leonid.I · 2016-11-05 22:14:17

WorMzy wrote:

Smoerrebroed wrote:
As the files are provided and reinstalled by another package
Could you elaborate on this? Which other package provides these files?

The files in question are located in /etc/fonts/conf.d:

: find /etc/fonts/conf.d -type l -name \*dejavu\* -exec pacman -Qo '{}' \;
error: No package owns /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf
error: No package owns /etc/fonts/conf.d/20-unhint-small-dejavu-sans.conf
error: No package owns /etc/fonts/conf.d/20-unhint-small-dejavu-serif.conf
error: No package owns /etc/fonts/conf.d/57-dejavu-sans-mono.conf
error: No package owns /etc/fonts/conf.d/57-dejavu-sans.conf
error: No package owns /etc/fonts/conf.d/57-dejavu-serif.conf

They were created by an install script in v2.35, but are owned by v2.37, hence the conflict. The safest approach, imho, is to just remove those. So, I don't understand why force upgrade is required.

mcloaked · 2016-11-06 15:19:47

Leonid.I wrote:

WorMzy wrote:
Smoerrebroed wrote:
As the files are provided and reinstalled by another package
Could you elaborate on this? Which other package provides these files?

The files in question are located in /etc/fonts/conf.d:
: find /etc/fonts/conf.d -type l -name \*dejavu\* -exec pacman -Qo '{}' \;
error: No package owns /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf
error: No package owns /etc/fonts/conf.d/20-unhint-small-dejavu-sans.conf
error: No package owns /etc/fonts/conf.d/20-unhint-small-dejavu-serif.conf
error: No package owns /etc/fonts/conf.d/57-dejavu-sans-mono.conf
error: No package owns /etc/fonts/conf.d/57-dejavu-sans.conf
error: No package owns /etc/fonts/conf.d/57-dejavu-serif.conf
They were created by an install script in v2.35, but are owned by v2.37, hence the conflict. The safest approach, imho, is to just remove those. So, I don't understand why force upgrade is required.

I used the method with --force recommended in the announce article and my output for that command is:

$ find /etc/fonts/conf.d -type l -name \*dejavu\* -exec pacman -Qo '{}' \;
/etc/fonts/conf.d/20-unhint-small-dejavu-serif.conf is owned by ttf-dejavu 2.37-1
/etc/fonts/conf.d/20-unhint-small-dejavu-sans.conf is owned by ttf-dejavu 2.37-1
/etc/fonts/conf.d/57-dejavu-sans-mono.conf is owned by ttf-dejavu 2.37-1
/etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf is owned by ttf-dejavu 2.37-1
/etc/fonts/conf.d/57-dejavu-sans.conf is owned by ttf-dejavu 2.37-1
/etc/fonts/conf.d/57-dejavu-serif.conf is owned by ttf-dejavu 2.37-1

So it looks like the announced recommendation did indeed give a good outcome/

Arch Linux

#1 2016-10-31 13:09:11

[SOLVED] ttf-dejavu update question

#2 2016-10-31 13:17:23

Re: [SOLVED] ttf-dejavu update question

#3 2016-11-01 09:11:10

Re: [SOLVED] ttf-dejavu update question

#4 2016-11-03 09:07:56

Re: [SOLVED] ttf-dejavu update question

#5 2016-11-03 09:59:05

Re: [SOLVED] ttf-dejavu update question

#6 2016-11-03 12:01:53

Re: [SOLVED] ttf-dejavu update question

#7 2016-11-03 13:32:59

Re: [SOLVED] ttf-dejavu update question

#8 2016-11-05 19:56:44

Re: [SOLVED] ttf-dejavu update question

#9 2016-11-05 22:14:17

Re: [SOLVED] ttf-dejavu update question

#10 2016-11-06 15:19:47

Re: [SOLVED] ttf-dejavu update question

Board footer