Dear ca-certificates maintainers,
On 2013-07-20 23:05, Andreas Beckmann wrote:
Installing sympa in a minimal system using
apt-get install sympa
fails, but changing this to
apt-get install ca-certificates
apt-get install sympa
succeeds.
This seems to indicate that sympa depends on a
Hi Emmanuel,
On 2013-07-21 20:09, Emmanuel Bouthenot wrote:
This bug is already fixed in git repository[1]. I'm currently working on
packaging Sympa 6.1.17, hence it will be fixed with the next upload.
[1]
forcemerge 706965 717435
thanks
Hi Andreas,
On Sat, Jul 20, 2013 at 11:05:01PM +0200, Andreas Beckmann wrote:
[...]
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
On Sun, Jul 21, 2013 at 04:03:23PM +0200, Andreas Beckmann wrote:
[...]
While this can be fixed with a Pre-Depends, I'm not sure whether this is
the correct approach. There might be more packages affected by similar
bugs in the future.
I'd like to avoid as much as possible the usage of
On 2013-07-20 23:05, Andreas Beckmann wrote:
This seems to indicate that sympa depends on a successful run of the
ca-certificates trigger *before* configuring sympa ... no idea how this
can be achieved. Cc:ed the ca-certificates maintainer.
Pre-Depends?
Kind regards
Philipp Kern
--
To
On 2013-07-21 11:22, Philipp Kern wrote:
On 2013-07-20 23:05, Andreas Beckmann wrote:
This seems to indicate that sympa depends on a successful run of the
ca-certificates trigger *before* configuring sympa ... no idea how this
can be achieved. Cc:ed the ca-certificates maintainer.
Package: sympa
Version: 6.1.11~dfsg-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
7 matches
Mail list logo
