Hi David, I am sorry, but I don't have a time to monitor yet another mailing list. My interest here doesn't go beyond "link with db5.1 please", which should be fairly straightforward in most case. I see that the latest uploader of xastir was Joop Stakenborg, so I guess you should probably speak with him about sponsoring an upload to Debian unstable since the current uploader (Hamish Moffatt) seems to be inactive for xastir since 2008.
O. 2011/4/7 David A Aitcheson <david.aitche...@gmail.com>: > Ondřej, > > xastir version 1.9.4-3.1 is no longer a valid release. The latest > version on SourceForge is 2.0.0 and can be found at > http://sourceforge.net/projects/xastir/files/ I am not certain which > "db" is currently used in the current release. > > Due to the non-availability of on-line Tiger maps OSM is now fully > integrated and the default. > > Please kindly refer yourself to http://www.xastir.org/wiki/Main_Page for > the latest information regarding Xastir. > > I would also suggest that you join/subscribe to the Xastir reflector at > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir at the least and > introduce yourself. > > Others here and on the Ubuntu hams list and Ubuntu hams devel list have > done some significant advancement of the package and have very up to > date releases available on PPA's. I am certain that they well chime in > with more definitive information. > > Sincerely, > David Aitcheson - KB3EFS > > > On 04/06/11 16:57, Ondřej Surý wrote: >> Package: xastir >> Version: 1.9.4-3.1 >> Severity: normal >> User: pkg-db-de...@lists.alioth.debian.org >> Usertags: db5.1 >> >> Your package currently still uses Berkeley DB version 4.8 (libdb4.8). >> >> However, there is a newer Berkeley DB version in the archive (libdb5.1), >> with a compatible API. Berkeley DB version 4.8 will be eventually >> removed from unstable in favor of version 5.1. >> >> Please port your package to libdb5.1 as soon as possible. In most cases >> only change required is to update build depends from libdb4.8-dev >> to libdb-dev, or just recompile the package. >> >> More complicated scenarios: >> >> - Package does check for DB_VERSION_MAJOR == 4 - this should be updated >> to (DB_VERSION_MAJOR > 4) || ((DB_VERSION_MAJOR == 4) && >> (DB_VERSION_MINOR >= XX)). >> >> - Configure checks - sometime there is a list of db-4.8 db-4.6 db-4.2, >> etc., this >> needs to be updated to just db (or db-5.1 db-5 db), or at least list >> the 'db' >> in the front >> >> You can see example patch in cyrus-imapd-2.2: >> http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.2.git;a=blob;f=debian/patches/99-berkelydb-5.1.dpatch;hb=HEAD >> >> - The packages which use Berkeley DB transactional mode need to upgrade >> the database files before the upgrade. This is fairly straightforward >> and is well documented on the Berkeley DB website. But you probably >> already know that because it's not the first Berkeley DB transition. >> >> The example script can be found in the cyrus-imapd-2.4 (not yet released): >> http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db;hb=HEAD >> >> Thanks, >> -- >> OndÅ™ej Surý <ond...@debian.org> >> >> -- System Information: >> Debian Release: squeeze/sid >> APT prefers maverick-updates >> APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), >> (500, 'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores) >> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> >> >> > > > > > -- > David A Aitcheson > david.aitche...@gmail.com > david.aitcheson on google and skype > -- Ondřej Surý <ond...@sury.org> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org