topic title: problem of dependencies
Posts: 10
franky69
Joined: 17 Jun 2009
#1
Hello there
to use QLandkarte i 've to install gdal and I have downgrade libsqlite.

Code: Select all

root@mxfranky:/home/franky/trunk/cmake/Modules# aptitude install libgdal-dev
Les NOUVEAUX paquets suivants vont être installés : 
  libgdal-dev libgdal1{a} libspatialite-dev{a} libsqlite3-dev{ab} 
0 paquets mis à jour, 4 nouvellement installés, 0 à enlever et 53 non mis à jour.
Il est nécessaire de télécharger 7 681 ko/12,5 Mo d'archives. Après dépaquetage, 39,9 Mo seront utilisés.
Les paquets suivants ont des dépendances non satisfaites :
 libsqlite3-dev : Dépend: libsqlite3-0 (= 3.7.13-1+deb7u1) mais 3.7.16.2-1~bpo70+1 est installé.
Les actions suivantes permettront de résoudre ces dépendances :

     Conserver les paquets suivants dans leur version actuelle :
1)     libgdal-dev [Non installé]                               
2)     libspatialite-dev [Non installé]                         
3)     libsqlite3-dev [Non installé]                            
Accepter cette solution ? [Y/n/q/?] n
Les actions suivantes permettront de résoudre ces dépendances :

     Réinstaller à une version antérieure les paquets suivants :                  
1)     libsqlite3-0 [3.7.16.2-1~bpo70+1 (now, stable) -> 3.7.13-1+deb7u1 (stable)]
Accepter cette solution ? [Y/n/q/?] y
Les paquets suivants vont être RÉINSTALLÉS à une VERSION ANTÉRIEURE : 
  libsqlite3-0 
Les NOUVEAUX paquets suivants vont être installés : 
  libgdal-dev libgdal1{a} libspatialite-dev{a} libsqlite3-dev{a}
but now I can not launch kmail

Code: Select all

Akonadi Server Self-Test Report
===============================

Test 1:  ERROR
--------

Database driver not found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE, QSQLITE3.
Make sure the required driver is installed.

File content of '/home/franky/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

Test 5:  ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/franky/.local/share/akonadi/db_data/mysql.err'>/home/franky/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/franky/.local/share/akonadi/db_data/mysql.err':
140714 11:32:14 [Note] Plugin 'FEDERATED' is disabled.
140714 11:32:14 [Note] Plugin 'FEDERATED' is disabled.
140714 11:32:14140714 11:32:14 InnoDB: The InnoDB memory heap is disabled
 InnoDB: The InnoDB memory heap is disabled
140714 11:32:14140714 11:32:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140714 11:32:14140714 11:32:14 InnoDB: Compressed tables use zlib 1.2.7
 InnoDB: Compressed tables use zlib 1.2.7
140714 11:32:14140714 11:32:14 InnoDB: Using Linux native AIO
 InnoDB: Using Linux native AIO
140714 11:32:14 InnoDB: Initializing buffer pool, size = 80.0M
140714 11:32:14 InnoDB: Initializing buffer pool, size = 80.0M
140714 11:32:14 InnoDB: Completed initialization of buffer pool
140714 11:32:14 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140714 11:32:14  InnoDB: Retrying to lock the first data file
140714 11:32:14 InnoDB: highest supported file format is Barracuda.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140714 11:32:17  InnoDB: Waiting for the background threads to start
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140714 11:32:18 InnoDB: 5.5.37 started; log sequence number 17536824
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140714 11:32:18 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
140714 11:32:18 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
140714 11:32:18 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.37-0+wheezy1'  socket: '/home/franky/.local/share/akonadi/socket-mxfranky/mysql.socket'  port: 0  (Debian)
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140714 11:33:54  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
140714 11:33:54  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
140714 11:33:54 InnoDB: Could not open or create data files.
140714 11:33:54 InnoDB: If you tried to add new data files, and it failed here,
140714 11:33:54 InnoDB: you should now edit innodb_data_file_path in my.cnf back
140714 11:33:54 InnoDB: to what it was, and remove the new ibdata files InnoDB created
140714 11:33:54 InnoDB: in this failed attempt. InnoDB only wrote those files full of
140714 11:33:54 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
140714 11:33:54 InnoDB: remove old data files which contain your precious data!
140714 11:33:54 [ERROR] Plugin 'InnoDB' init function returned error.
140714 11:33:54 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140714 11:33:54 [ERROR] Unknown/unsupported storage engine: innodb
140714 11:33:54 [ERROR] Aborting

140714 11:33:54 [Note] /usr/sbin/mysqld: Shutdown complete

Test 10:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12:  ERROR
--------

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.
an idea ?
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#2
Might get more joy at posting this thread at


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.mepiscommunity.org/"
linktext was:"http://forum.mepiscommunity.org/"
====================================


As there are more KDE users there than here. Just a suggestion though. I have no idea as I shy away from using Anything above a Window Manager usually instead of a Desktop enviornment.

That is not to say some other member may have a better suggestion.
nadir
Posts 0
nadir
#3
to use QLandkarte i 've to install gdal and I have downgrade libsqlite.
Why? iow: Are you sure?

1) dependencies should be installed automatically, no need to install them yourself (as far gdal is concernded). .

2)

Code: Select all

$ apt-cache show qlandkartegt | grep sqlite
$
And posting your sources.list, apt.conf or preferences for apt won't hurt.

Fooling with downgrading apps, pinning, installing third-party apps and what not is seldom a good idea (in the long run and if you _don't run a mixed testing/unstable system, then it might make sense). Imho, of course.
Posts: 452
Jerry
Joined: 12 Sep 2007
#4
In case it would help, we have a resource about using KDE with MX-14 based on user experience:


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepiscommunity.org/doc_mx/advanced_kde.html"
linktext was:"http://www.mepiscommunity.org/doc_mx/advanced_kde.html"
====================================


And a dedicated forum for MX-KDE issues:


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.mepiscommunity.org/viewforum.php?f=99"
linktext was:"http://forum.mepiscommunity.org/viewforum.php?f=99"
====================================


Viens nous poser tes questions!
Posts: 88
kmathern
Joined: 25 Aug 2012
#5
It's not really a KDE problem.

The 3.7.16.2-1~bpo70+1 version of libsqlite3-0 is currently installed (from the antix.daveserver.info repo).

The libgdal-dev package that franky69 is trying to install has a dependency for libsqlite3-dev.

The versions of libsqlite3-0 & libsqlite3-dev need to be the same, but a 3.7.16.2-1~bpo70+1 version libsqlite3-dev package isn't available in the repos.

The antix.daveserver.info repo only has the libsqlite3-0 package (in amd64 & i386 arch), it's missing several other packages including the 3.7.16.2-1~bpo70+1 version libsqlite3-dev package (
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.daveserver.info/stable/pool/main/s/sqlite3/"
linktext was:"http://antix.daveserver.info/stable/poo ... s/sqlite3/"
====================================
).

The libsqlite3-0 package is built from the sqlite3 source package (
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/source/wheezy/sqlite3"
linktext was:"https://packages.debian.org/source/wheezy/sqlite3"
====================================
).

A full upload would have included 11 additional 3.7.16.2-1~bpo70+1 version .deb packages:

lemon (amd64 & i386)
libsqlite3-dbg (amd64 & i386)
libsqlite3-dev (amd64 & i386)
libsqlite3-tcl (amd64 & i386)
sqlite3 (amd64 & i386)
sqlite3-doc
nadir
Posts 0
nadir
#6
That is right, and it is my fault, but only leads to the next question (now why libgdal-dev package is supposed to be installed):

Code: Select all

$ apt-rdepends qlandkartegt | grep dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
  Depends: libudev1
libudev1
  Depends: libudev1 (>= 183)
To me installing on a debian (based) system means:
apt-get install packagename
and thats it.
Before discussing what went wrong when and why and what to do about it, the info is needed what is wrong with that most basic operation (In other words: One will have to look at the problem, not at possible solutions and what are the problems of the - perhaps - wrong solution ).
If one"has to do X" (for example install another package or downgrade it or whatever) to install a package, then something is wrong (either with the package or with the approach to install it). It is really just apt-get install.

In short:
The OP said"I had to" and i still say"why?"
That is the info needed to troubleshoot a problem.