[Evolution] Bug#462642: package versions in debian testing

Patrick ragamuffin at datacomm.ch
Wed Jan 30 10:24:11 UTC 2008


Hello Gentlemen

The reason of my writing to you is that the package versions of
"evolution" and "evolution-data-server" in "debian
testing" (/debian/dists/testing/main/binary-amd64/Packages.bz2) seem to
be "out of sync".

Downloading
ftp://ftp.debian.org/debian/dists/testing/main/binary-i386/Packages.bz2
(also i386) shows the following:

> bzcat Packages-i386.bz2 | grep -A7 "^Package: evolution\(-data-server
\)\?$"
Package: evolution
Priority: optional
Section: gnome
Installed-Size: 7735
Maintainer: Debian Evolution Maintainers
<pkg-evolution-maintainers at lists.alioth.debian.org>
Architecture: i386
Version: 2.12.3-1
Replaces: evolution-common (<< 2.6.2-3), evolution-plugins (<= 2.6.1-2)
--
Package: evolution-data-server
Priority: optional
Section: gnome
Installed-Size: 1080
Maintainer: Debian Evolution Maintainers
<pkg-evolution-maintainers at lists.alioth.debian.org>
Architecture: i386
Source: evolution-data-server (1.12.2-1)
Version: 1.12.2-1+b1

If I install these Versions (just "apt-get upgrade", in my case) the
following problem comes up in Evolution:

When trying to connect to a pop mailbox, using ssl, the "sending &
receiving..." dialog doesn't appear any more, but a error message,
saying "Cannot connect to pop.postmail.ch: SSL unavailable" appears
instead and the mails are not fetched.

If I do "apt-get install -t unstable evolution-data-server", version
1.12.3-1 gets installed and everything is fine.

But it took me quiet a long time to find that simple solution! It
doesn't make sense to me that the two Packages are not "in sync" (with
evolution-data-server version always being "evolution version minus
one", which is also not clear to me, but at least systematic). Obviously
the two Packages heavily depend on each other and should always be in
sync.

Hopefully the problem will soon be solved for others and maybe a bit
more care be taken in the future. Also, I think, evolution, is not the
only place where such things happen, when packages are descending from
"unstable" to "testing" - things sometimes stop working as seamlessly as
they did in "unstable" - or am I missing something?


Yours sincerely

Patrick

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20080130/9da0c95e/attachment-0001.htm 


More information about the Pkg-evolution-maintainers mailing list