cyrus-imapd-2.2 (2.2.13-10ubuntu2) feisty; urgency=low
* Add missing semi-colon and correct a const in 61-64bit-quota.
* Add a patch to drop libdb4.4 detection, as it will always use that
if it's available. (LP: #67111)
* Update configure patching in 99-update-autoconf.
* Correct
Attached is a debdiff for uploading to edgy-proposed. This bug is a
regression from Dapper, and is actually quite nasty. The init script
fires off a master process which spawns off an imapd and/or pop3d
process. They die horribly with a SEGV due to this libdb brain damage,
are immediately
+1
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
+1 as well
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Uploaded to edgy-proposed.
** Changed in: cyrus-imapd-2.2 (Ubuntu Edgy)
Assignee: (unassigned) = Steve Kowalik
--
[SRU]: Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Am a little new to Debian and Ubuntu, hence don't know how
this bugfix process works. Am I reading you right if I conclude
that you are releasing the new, bugfixed version of Cyrus 2.2
only on Fiesty, and the Edgy release will not contain the bug-fix?
If I'm right, I'll have to download the Cyrus
Is there a way to increase the version of the self build binaries until
the fix is provided? Every update I perform it wants to overwrite the
version I have built with the broken version from the repository. I
would be nice to increase it just a little to prevent that.
--
Cyrus linked against
Is this bug resolved in feisty?
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
triplem schrieb:
Is this bug resolved in feisty?
so how can you find out?
- apt-cache showsrc shows you the build dependencies
- apt-cache showsrc shows you the names of the binary packages
- apt-cache show binary pkg shows you the dependencies
As an alternative, you can find all this
On the question of why the library dependency on libdb4.3-dev leads to
linking against libdb4.4: My guess is that the package's Makefiles link
using -ldb, rather than -ldb-3. When libdb4.4-dev (or libdb4.5-dev on
Feisty) is installed, /usr/lib/libdb.so points to the newer version. My
further
I was clearly not thinking clearly when I posted my previous comment.
The actual culprit seems to be the CYRUS_BERKELEY_DB_CHK_LIB autoconf
helper in cyrus-imapd-2.2*/cmulocal/berkdb.m4, which explicitly looks
for versioned shared libraries (-ldb-4.4, -ldb4.4, -ldb44, -ldb-4.3,
etc, in that order)
Thanks, Matthias. Good points.
I'm not entirely sure how the database works when moving from 4.3 to
4.4. I want to say that when I upgraded from dapper, they just picked
right up once cyrus started. I can't be quoted on that for sure, though.
Maybe I can get some time to setup a test environment
[away until January 2007]
- we need to figure out why the build dependency on 4.3
leads to a dependency on 4.4 (dapper didn't have this).
- upgrade scenaries become complicated; dapper has
the dependency on 4.3, edgy and feisty on 4.4. is
an existing database correctly upgraded?
--
Cyrus
When will you patch this bug in the official release? It is already
known for quite a time and a fix would be easily possible. This bug
already costed some errors that could have been avoided.
Regards,
sir-archimedes
--
Cyrus linked against db4.4 compiled against 4.3 ?
I emailed the creator, Matthias Klose. Hopefully, he can suggest someone
to get in touch with to get this fixed officially.
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I agree,
I chose ubuntu because of it's release cycles (used to have gentoo but
it is too maintenance intensive and before that debian but it is too
slow/old in it's stable tree).
Installing a package and having it immediately segfault (especially
something like cyrus) is kind of a show stopper
I can make working packages, but I need to know who I need to get in
contact with to get them submitted to the official repository. Please
contact me if you need either x86 or AMD64 packages.
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs
I'm on a ubuntu-minimal amd64 with edgy here and get exactly that error
** Changed in: cyrus-imapd-2.2 (Ubuntu Edgy)
Status: Unconfirmed = Confirmed
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
Since I don't know the proper way to submit a change, I have attached
the new control file. If you wish to build your own package from source,
you simply need to do the following:
1. Download the attached control patch file which simply changes the
build-depends from libdb4.3-dev to libdb4.4-dev.
Ignore the first patch. I messed it up. Get the one marked *CORRECT*.
** Attachment added: *CORRECT* Patch file.
http://librarian.launchpad.net/5153568/control.diff
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
Final note, change step 4 above to
# patch -p0 control.diff
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bug confirmed AND fix confirmed (hey cool, I learned something new, how
to build a package from source). Thanks a lot!
I am running an AMD64 version of Ubuntu, for what it's worth.
Furthermore, upon compiling and installing I got bad error messages from
cyrus, I imagine i could not read the
I confirm this bug too.
Moreover, on AMD64 as I execute cyrus it dies due to a segfault.
--
Cyrus linked against db4.4 compiled against 4.3 ?
https://launchpad.net/bugs/67111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I experienced this as well.
Fixed by downloading source package and changing libdb4.3-dev to
libdb4.4-dev as a Build-Depends in cyrus-
imapd-2.2-2.2.13/debian/control. Rebuilt the package, reinstalled new
debs and things worked.
** Changed in: cyrus-imapd-2.2 (Ubuntu)
Status: Unconfirmed
24 matches
Mail list logo