mapcache - Debian Package Tracker

general

source: mapcache (main)
version: 1.10.0-2
maintainer: Debian GIS Project (archive) (DMD)
uploaders: Francesco Paolo Lovergine [DMD] – Alan Boudreault [DMD] – Bas Couwenberg [DMD]
arch: any
std-ver: 4.5.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.4.1-3
o-o-bpo: 1.6.1-1~bpo9+1
oldstable: 1.6.1-3
old-bpo: 1.10.0-1~bpo10+1
stable: 1.10.0-2
testing: 1.10.0-2
unstable: 1.10.0-2

versioned links

1.4.1-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.6.1-1~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.6.1-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.10.0-1~bpo10+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.10.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libapache2-mod-mapcache
libmapcache1
libmapcache1-dev
mapcache-cgi
mapcache-tools

action needed

Problems while searching for a new upstream version high

uscan had problems while searching for a new upstream version:

In debian/watch no matching files for watch line
  https://github.com/mapserver/mapcache/releases (?:.*?/archive/)?(?:rel|v|mapcache)?[\-\_]?(\d[\d\-\.]+)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))

Created: 2021-03-23 Last update: 2021-09-18 03:54

16 security issues in sid high

There are 16 open security issues in sid.

16 important issues:

CVE-2019-20005: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr() starting with a pointer after a '\0' character (where the processing of a string was finished).
CVE-2019-20006: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content puts a pointer to the internal address of a larger block as xml->txt. This is later deallocated (using free), leading to a segmentation fault.
CVE-2019-20007: An issue was discovered in ezXML 0.8.2 through 0.8.6. The function ezxml_str2utf8, while parsing a crafted XML file, performs zero-length reallocation in ezxml.c, leading to returning a NULL pointer (in some compilers). After this, the function ezxml_parse_str does not check whether the s variable is not NULL in ezxml.c, leading to a NULL pointer dereference and crash (segmentation fault).
CVE-2019-20198: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_ent_ok() mishandles recursion, leading to stack consumption for a crafted XML file.
CVE-2019-20199: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to NULL pointer dereference while running strlen() on a NULL pointer.
CVE-2019-20200: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing crafted a XML file, performs incorrect memory handling, leading to a heap-based buffer over-read in the "normalize line endings" feature.
CVE-2019-20201: An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxml_parse_* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.
CVE-2019-20202: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content() tries to use realloc on a block that was not allocated, leading to an invalid free and segmentation fault.
CVE-2021-26220: The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26221: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26222: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-30485: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd(), while parsing a crafted XML file, performs incorrect memory handling, leading to a NULL pointer dereference while running strcmp() on a NULL pointer.
CVE-2021-31229: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd() performs incorrect memory handling while parsing crafted XML files, which leads to an out-of-bounds write of a one byte constant.
CVE-2021-31347: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (writing outside a memory region created by mmap).
CVE-2021-31348: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (out-of-bounds read after a certain strcspn failure).
CVE-2021-31598: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap-based buffer overflow.

Created: 2021-06-14 Last update: 2021-08-15 00:00

16 security issues in bookworm high

There are 16 open security issues in bookworm.

16 important issues:

CVE-2019-20005: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr() starting with a pointer after a '\0' character (where the processing of a string was finished).
CVE-2019-20006: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content puts a pointer to the internal address of a larger block as xml->txt. This is later deallocated (using free), leading to a segmentation fault.
CVE-2019-20007: An issue was discovered in ezXML 0.8.2 through 0.8.6. The function ezxml_str2utf8, while parsing a crafted XML file, performs zero-length reallocation in ezxml.c, leading to returning a NULL pointer (in some compilers). After this, the function ezxml_parse_str does not check whether the s variable is not NULL in ezxml.c, leading to a NULL pointer dereference and crash (segmentation fault).
CVE-2019-20198: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_ent_ok() mishandles recursion, leading to stack consumption for a crafted XML file.
CVE-2019-20199: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to NULL pointer dereference while running strlen() on a NULL pointer.
CVE-2019-20200: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing crafted a XML file, performs incorrect memory handling, leading to a heap-based buffer over-read in the "normalize line endings" feature.
CVE-2019-20201: An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxml_parse_* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.
CVE-2019-20202: An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content() tries to use realloc on a block that was not allocated, leading to an invalid free and segmentation fault.
CVE-2021-26220: The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26221: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26222: The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-30485: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd(), while parsing a crafted XML file, performs incorrect memory handling, leading to a NULL pointer dereference while running strcmp() on a NULL pointer.
CVE-2021-31229: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd() performs incorrect memory handling while parsing crafted XML files, which leads to an out-of-bounds write of a one byte constant.
CVE-2021-31347: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (writing outside a memory region created by mmap).
CVE-2021-31348: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (out-of-bounds read after a certain strcspn failure).
CVE-2021-31598: An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap-based buffer overflow.

Created: 2021-08-15 Last update: 2021-08-15 00:00

Depends on packages which need a new maintainer normal

The packages that mapcache depends on which need a new maintainer are:

docbook-xml (#802368)
- Build-Depends: docbook-xml
docbook-xsl (#802370)
- Build-Depends: docbook-xsl

Created: 2019-11-22 Last update: 2021-09-18 03:56

Multiarch hinter reports 1 issue(s) normal

There are issues with the multiarch metadata for this package.

libmapcache1 could be marked Multi-Arch: same

Created: 2017-10-01 Last update: 2021-09-16 08:40

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 1.10.0-3, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit b61a27b5acdaaa9cc64dbf00f9b069a03dce0566
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Tue Sep 14 18:46:49 2021 +0200

    Drop --autodest from dh_install.

commit cdbcd391fc133946f829cab80e08922d093b1467
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Sun Sep 12 16:52:14 2021 +0200

    Update lintian overrides.

commit 91cbd6f3093a103e4c2ad2ae6205aa33f63e8d91
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Sun Sep 12 16:43:39 2021 +0200

    Bump debhelper compat to 12.
    
    Changes:
    - Drop --list-missing from dh_install

commit 5e4207cb47f753d41cbb018a4f8eac3a085fec9b
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Wed Sep 8 16:38:14 2021 +0200

    Bump Standards-Version to 4.6.0, no changes.

commit bf63176c0487b91dd67921a36f97d63570e11125
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Mon Aug 9 18:40:38 2021 +0200

    Apply patch by Chris Lamb to make the build reproducible. (closes: #992039)

commit 44413c887df3c1ad21f46022db33ecbcb750bdff
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Sat Mar 20 08:41:44 2021 +0100

    Update watch file for GitHub URL changes.

commit 96bb41eb838000a91054063353b95743cf62adc3
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Tue Jan 26 18:08:03 2021 +0100

    Update upstream metadata.

commit 4735d0acff2145f1061b6e61548cfc27ab22b47b
Author: Bas Couwenberg <sebastic@xs4all.nl>
Date:   Sat Nov 28 13:49:15 2020 +0100

    Bump Standards-Version to 4.5.1, no changes.

Created: 2020-11-28 Last update: 2021-09-14 17:35

16 low-priority security issues in buster low

There are 16 open security issues in buster.

16 issues left for the package maintainer to handle:

CVE-2019-20005: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr() starting with a pointer after a '\0' character (where the processing of a string was finished).
CVE-2019-20006: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content puts a pointer to the internal address of a larger block as xml->txt. This is later deallocated (using free), leading to a segmentation fault.
CVE-2019-20007: (needs triaging) An issue was discovered in ezXML 0.8.2 through 0.8.6. The function ezxml_str2utf8, while parsing a crafted XML file, performs zero-length reallocation in ezxml.c, leading to returning a NULL pointer (in some compilers). After this, the function ezxml_parse_str does not check whether the s variable is not NULL in ezxml.c, leading to a NULL pointer dereference and crash (segmentation fault).
CVE-2019-20198: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_ent_ok() mishandles recursion, leading to stack consumption for a crafted XML file.
CVE-2019-20199: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to NULL pointer dereference while running strlen() on a NULL pointer.
CVE-2019-20200: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing crafted a XML file, performs incorrect memory handling, leading to a heap-based buffer over-read in the "normalize line endings" feature.
CVE-2019-20201: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxml_parse_* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.
CVE-2019-20202: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content() tries to use realloc on a block that was not allocated, leading to an invalid free and segmentation fault.
CVE-2021-26220: (needs triaging) The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26221: (needs triaging) The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26222: (needs triaging) The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-30485: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd(), while parsing a crafted XML file, performs incorrect memory handling, leading to a NULL pointer dereference while running strcmp() on a NULL pointer.
CVE-2021-31229: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd() performs incorrect memory handling while parsing crafted XML files, which leads to an out-of-bounds write of a one byte constant.
CVE-2021-31347: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (writing outside a memory region created by mmap).
CVE-2021-31348: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (out-of-bounds read after a certain strcspn failure).
CVE-2021-31598: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap-based buffer overflow.

You can find information about how to handle these issues in the security team's documentation.

Created: 2021-06-14 Last update: 2021-08-15 00:00

16 low-priority security issues in bullseye low

There are 16 open security issues in bullseye.

16 issues left for the package maintainer to handle:

CVE-2019-20005: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr() starting with a pointer after a '\0' character (where the processing of a string was finished).
CVE-2019-20006: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content puts a pointer to the internal address of a larger block as xml->txt. This is later deallocated (using free), leading to a segmentation fault.
CVE-2019-20007: (needs triaging) An issue was discovered in ezXML 0.8.2 through 0.8.6. The function ezxml_str2utf8, while parsing a crafted XML file, performs zero-length reallocation in ezxml.c, leading to returning a NULL pointer (in some compilers). After this, the function ezxml_parse_str does not check whether the s variable is not NULL in ezxml.c, leading to a NULL pointer dereference and crash (segmentation fault).
CVE-2019-20198: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_ent_ok() mishandles recursion, leading to stack consumption for a crafted XML file.
CVE-2019-20199: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to NULL pointer dereference while running strlen() on a NULL pointer.
CVE-2019-20200: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing crafted a XML file, performs incorrect memory handling, leading to a heap-based buffer over-read in the "normalize line endings" feature.
CVE-2019-20201: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxml_parse_* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.
CVE-2019-20202: (needs triaging) An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content() tries to use realloc on a block that was not allocated, leading to an invalid free and segmentation fault.
CVE-2021-26220: (needs triaging) The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26221: (needs triaging) The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-26222: (needs triaging) The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
CVE-2021-30485: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd(), while parsing a crafted XML file, performs incorrect memory handling, leading to a NULL pointer dereference while running strcmp() on a NULL pointer.
CVE-2021-31229: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd() performs incorrect memory handling while parsing crafted XML files, which leads to an out-of-bounds write of a one byte constant.
CVE-2021-31347: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (writing outside a memory region created by mmap).
CVE-2021-31348: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (out-of-bounds read after a certain strcspn failure).
CVE-2021-31598: (needs triaging) An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap-based buffer overflow.

You can find information about how to handle these issues in the security team's documentation.

Created: 2021-08-14 Last update: 2021-08-15 00:00

Build log checks report 1 warning low

Build log checks report 1 warning

Created: 2017-10-26 Last update: 2017-10-26 07:22

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.0 instead of 4.5.0).

Created: 2020-11-17 Last update: 2021-08-18 14:02

news

[rss feed]

[2020-11-17] mapcache 1.10.0-2 MIGRATED to testing (Debian testing watch)
[2020-11-11] Accepted mapcache 1.10.0-2 (source) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2020-03-01] Accepted mapcache 1.10.0-1~bpo10+1 (source) into buster-backports (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2020-03-01] mapcache 1.10.0-1 MIGRATED to testing (Debian testing watch)
[2020-02-24] Accepted mapcache 1.10.0-1 (source) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2019-07-30] Accepted mapcache 1.8.0-1~bpo10+1 (source amd64) into buster-backports, buster-backports (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2019-07-30] mapcache 1.8.0-1 MIGRATED to testing (Debian testing watch)
[2019-07-25] Accepted mapcache 1.8.0-1 (source) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2019-07-17] mapcache 1.6.1-4 MIGRATED to testing (Debian testing watch)
[2019-07-11] Accepted mapcache 1.6.1-4 (source) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2018-08-06] mapcache 1.6.1-3 MIGRATED to testing (Debian testing watch)
[2018-07-31] Accepted mapcache 1.6.1-3 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2018-07-23] mapcache 1.6.1-2 MIGRATED to testing (Debian testing watch)
[2018-07-20] Accepted mapcache 1.6.1-2 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2017-10-05] Accepted mapcache 1.6.1-1~bpo9+1 (source amd64) into stretch-backports (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2017-10-05] mapcache 1.6.1-1 MIGRATED to testing (Debian testing watch)
[2017-09-30] Accepted mapcache 1.6.1-1 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2017-07-04] Accepted mapcache 1.6.0-2~bpo9+1 (source amd64) into stretch-backports, stretch-backports (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2017-06-23] mapcache 1.6.0-2 MIGRATED to testing (Debian testing watch)
[2017-06-18] Accepted mapcache 1.6.0-2 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2017-04-13] Accepted mapcache 1.6.0-1 (source amd64) into experimental (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2016-05-11] mapcache 1.4.1-3 MIGRATED to testing (Debian testing watch)
[2016-05-05] Accepted mapcache 1.4.1-3 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2016-03-07] Accepted mapcache 1.4.1-2~bpo8+1 (source amd64) into jessie-backports (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2016-03-07] mapcache 1.4.1-2 MIGRATED to testing (Debian testing watch)
[2016-02-26] Accepted mapcache 1.4.1-2 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2016-02-25] Accepted mapcache 1.4.1-1 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2015-09-06] mapcache 1.4.0-4 MIGRATED to testing (Britney)
[2015-08-29] Accepted mapcache 1.4.0-4 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)
[2015-08-25] Accepted mapcache 1.4.0-3 (source amd64) into unstable (Bas Couwenberg) (signed by: Sebastiaan Couwenberg)

bugs [bug history graph]

all: 2
RC: 0
I&N: 1
M&W: 0
F&P: 1
patch: 0

links

homepage
lintian
buildd: logs, checks, clang, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.10.0-2build1