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 source from the Edgy source archives and apply this Debdiff and recompile?
Please can you confirm/deny? Shuvam On 2/23/07, Steve Kowalik <[EMAIL PROTECTED]> wrote: > 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 re-spawned by the master process, and proceed to die > again. Rinse and repeat. > > The debdiff fixes the bug by patching configure (which the Debian build > does anyway) to not include db4.4 in it's list of libdb versions. > > ** Attachment added: "debdiff" > http://librarian.launchpad.net/6516492/cyrus-edgy-proposed.debdiff > > -- > Cyrus linked against db4.4 compiled against 4.3 ? > https://launchpad.net/bugs/67111 > -- [SRU]: 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
