FS#28541 - subversion 1.7 depends on sqlite3 version, db version

Attached to Project: Arch Linux
Opened by Dima Q (dimaqq) - Monday, 20 February 2012, 09:30 GMT
Last edited by Pierre Schmitz (Pierre) - Monday, 20 February 2012, 10:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Updated subversion with pacman -S subversion, from 1.6.17 to 1.7.2-r2, pacman didn't insist on any other updates.

### sqlite3:

root@quilt ~ # svnversion some_local_checkout
svn: E200029: Couldn't perform atomic initialization
svn: E200030: SQLite compiled for 3.7.9, but running with 3.7.8

after manual pacman -S sqlite3, from 3.7.8 to sqlite3-3.7.10-1:

root@quilt ~ # svnversion nexus_svn_172r2
svn: E155036: Working copy '/root/nexus_svn_172r2' is too old (format 10, created by Subversion 1.6)
# 1.6/1.7 mismatch as expected


### db:

svn --version
svn: error while loading shared libraries: libdb-5.3.so: cannot open shared object file: No such file or directory

# after manual pacman -S db, from 5.2 to db-5.3.15-1

svn --version
svn, version 1.7.2 (r1207936)
compiled Jan 3 2012, 17:19:38





Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Monday, 20 February 2012, 10:08 GMT
Reason for closing:  Not a bug
Comment by Karol Błażewicz (karol) - Monday, 20 February 2012, 09:56 GMT
You should keep your system up to date.

A similar story: http://mailman.archlinux.org/pipermail/arch-general/2012-February/025118.html
Comment by Dima Q (dimaqq) - Monday, 20 February 2012, 10:01 GMT
I already fixed it by upgrading dependent packages, so I cannot easily roll back to reproduce it anymore.

I don't have a habit of doing full system upgrades (-Syu) too often, the issue is here is that pacman doesn't pull subversion's dependencies.

pacman itself is up to date.

Some day I will do system upgrade too, but I won't be able to answer your question.

I this ticket can be closed as a known pacman limitation?
Comment by Pierre Schmitz (Pierre) - Monday, 20 February 2012, 10:08 GMT
It's not a pacman limitation. Arch simply works this way: either update your whole system or don't. Cherry picking is not supported. (in a short: because making this work is way more complicated than one would think)

Loading...