<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
line-height:normal;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
line-height:normal;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:7.2pt;
margin-left:0cm;
line-height:120%;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
line-height:normal;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.StyleNormalWebVerdana10ptPatternClearCustomColorR, li.StyleNormalWebVerdana10ptPatternClearCustomColorR, div.StyleNormalWebVerdana10ptPatternClearCustomColorR
{mso-style-name:"Style Normal \(Web\) + Verdana 10 pt Pattern\: Clear \(Custom Color\(R\.\.\.";
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:7.2pt;
margin-left:0cm;
line-height:120%;
font-size:10.0pt;
font-family:"Courier New";
background:#DDDDDD;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ES-AR link=blue vlink=purple><div class=WordSection1><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Hi All,<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Ellie, the patch that you've sent for the backup linking problem doesn't solve the issue, but you're right, I've just dug deeper: it's a matter of order of the library inclusion options and it's because in Ubuntu starting from 11.04 (and some versions of Debian too) the gcc invokes ld with </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>--as-needed</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> flag that makes the order of libraries quite important. There is a detailed explanation of the issue here: <a href="https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries">https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries</a> and here: <a href="https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition">https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition</a>.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Also it looks like newer versions of gcc/ld (mine is 4.8.4/2.24) treat the order of includes much more strictly than previous versions on most platforms.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>In a nutshell, a binary/library (A) which calls an external function defined in another library (B) should appear <i>before</i> the library (B) containing the function. The reason is that gcc/ld with </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>--as-needed</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> flag optimizes symbols that aren't referenced, so if it sees library B first, and no one has referenced it at that point then it won't link in anything from it at all. This is what happens with </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>-lcrypto</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> going before </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>libcyrus_backup.a</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>: the </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>SHA1_Update</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> function is only used inside </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>libcyrus_backup.a</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> but the linker has already stripped it from </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>-lcrypto</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>. If we include </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>-lcrypto</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> again <i>after</i> </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>libcyrus_backup.a</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>, everything builds fine.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>I've already proposed to Ken a slightly different patch than yours (Makefile.am.patch, attached to this email is its version with adaptations to apply smoothly to the latest master commit 9c8e8ea) that works well under these rules. <o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>The changes are: to add SSL_LIBS to the list of the libs for </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>libcyrus_backup</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> (currently there are none) and for the second error (that was mentioned in the initial mail about these problems) to add </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>lib/libcyrus.la</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> to the list of the libs for </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>cyr_backup</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>So, instead of expecting the include libs, that are required for certain parts of the binary/lib we're building, to make random appearance in the gcc line (in sometimes incorrect order under the strict/as-needed rules), we add in the Makefile.am the needed libs for each and every lib/block of code we use to compose the final output. As a result, at the linking stage they appear in the correct order.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><div style='mso-element:para-border-div;border:none;border-bottom:double black 1.0pt;padding:0cm 0cm 2.0pt 0cm'><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal;border:none;padding:0cm'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>Warning (mostly harmless): No library found for -lcrypto</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Indeed, it's a Makefile.PL warning as my perl installation LD path is not complete (doesn't include /usr/lib64 where crypto/ssl libs are). It should be fixed locally in my perl deployment. In any case it's indeed harmless as gcc/ld knows about this path and this is where it's used.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><div style='mso-element:para-border-div;border:none;border-bottom:double black 1.0pt;padding:0cm 0cm 2.0pt 0cm'><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal;border:none;padding:0cm'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>The yacc/lex dependency is actually not checked. Better to say configure tries to determine what yacc/lex progs are installed, but if it founds none, it continues as if everything's OK. The config.log I've sent you was for the build with the packages installed (otherwise you can't proceed with the make stage). Without the packages, in the config.log I get:<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19090: checking for bison<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19120: result: no<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19090: checking for byacc<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19120: result: no<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19133: checking for flex<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19163: result: no<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19133: checking for lex<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>configure:19163: result: no<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>but nothing more. So, configure reports no warnings/errors with respect to the missing tools and then with make I get:<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>./ylwrap: line 175: yacc: command not found<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>make: *** [sieve/addr.c] Error 127<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>make: *** Waiting for unfinished jobs....<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>./ylwrap: line 175: yacc: command not found<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'>make: *** [sieve/sieve.c] Error 127<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>I made a patch (configure.ac.patch, attached) to check for yacc/lex programs inside the Sieve option block as it's the only component (if I'm not wrong) that requires yacc/lex.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Then I went ahead and also changed the following (I've already mentioned both suggestions to Ken/list but received no response):<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Changed the behavior when no ICU4C lib is detected: from warning to error as its absence causes an error during make stage, and other similar required packages are reported inside configure with an error message.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Changed the type of message when com_err is absent or incomplete (lacking compile_et): from warning to notice, as this is the most common situation I believe (no or incomplete com_err) and it doesn't affect in anything the result of the build process (its sources are shipped with Cyrus sources and used when needed).<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Inside this patch there is also a fix for a typo in a comment (says "Build in <b>Sieve</b> support?" instead of "Build in <b>Squat</b> support?") introduced with my previous patch for </span><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";background:#DDDDDD'>--disable-squat</span><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> option fix. This typo doesn't affect anything (it's just a comment for config.h.in), but seizing the opportunity of fixing Makefile.am, here it is.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>With all this applied, I see no warning/errors for the entire build process when all needed packages are installed, and when not, configure notifies me about all of them, not allowing to continue to the make stage until all requirements are satisfied. Please apply the fixes as you see fit.<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Regards,<o:p></o:p></span></p><p style='margin:0cm;margin-bottom:.0001pt;line-height:normal'><span lang=EN-US style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Anatoli<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US style='mso-fareast-language:ES-AR'>-----Original Message-----<br>From: Cyrus-devel [mailto:cyrus-devel-bounces+me=anatoli.ws@lists.andrew.cmu.edu] On Behalf Of ellie timoney via Cyrus-devel<br>Sent: Sunday, May 15, 2016 23:28<br>To: cyrus-devel@lists.andrew.cmu.edu<br>Subject: Re: v3.0</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Hi Anatoli,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks for sending through the config.log and make output.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>For what it's worth, if you configure with --enable-silent-rules, the<o:p></o:p></p><p class=MsoPlainText>make output will be a lot less noisy (and a lot easier to read).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> Ken, the 2 errors that don't happen to you only happen to me when<o:p></o:p></p><p class=MsoPlainText>> compiling<o:p></o:p></p><p class=MsoPlainText>> with --enable-backup. I've tested the beta2 tarball as well as the<o:p></o:p></p><p class=MsoPlainText>> current<o:p></o:p></p><p class=MsoPlainText>> git, both errors still happen to me on 2 different machines. Without the<o:p></o:p></p><p class=MsoPlainText>> --enable-backup option these errors don't occur.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>As I mentioned in private email, I don't get these errors either<o:p></o:p></p><p class=MsoPlainText>(Debian).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Poking around on Google, I see a few other projects experiencing the<o:p></o:p></p><p class=MsoPlainText>"DSO missing from command line" error for Ubuntu builds. It looks like<o:p></o:p></p><p class=MsoPlainText>maybe Ubuntu's linker setup is more sensitive to correct order of<o:p></o:p></p><p class=MsoPlainText>dependencies?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I've attached an experimental patch which I think corrects the link<o:p></o:p></p><p class=MsoPlainText>dependency order for the backup tools. Can you try it out? The patch<o:p></o:p></p><p class=MsoPlainText>is against 3.0.0beta2 but should also apply cleanly against latest git<o:p></o:p></p><p class=MsoPlainText>master. This should hopefully resolve the "DSO missing from command<o:p></o:p></p><p class=MsoPlainText>line" errors when building with --enable-backup. Let me know how it<o:p></o:p></p><p class=MsoPlainText>goes.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> Warning (mostly harmless): No library found for -lcrypto<o:p></o:p></p><p class=MsoPlainText>> (same for -lssl)<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I dug around a bit and I think these come from the perl module build<o:p></o:p></p><p class=MsoPlainText>system. I'm not sure what they mean exactly, might be a red herring. <o:p></o:p></p><p class=MsoPlainText>Your config.log shows it's correctly detecting OpenSSL, anyway.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> I found another issue with the dependencies: the build requires yacc/lex<o:p></o:p></p><p class=MsoPlainText>> when building sieve, though in the Release Notes there is the following<o:p></o:p></p><p class=MsoPlainText>> text: Replaced the et (error table) libary with a version that doesn't<o:p></o:p></p><p class=MsoPlainText>> require lex or yacc. Remove the lex/yacc checking from Configure.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>That release note item is ancient (version 1.4!) and I doubt it's of<o:p></o:p></p><p class=MsoPlainText>much relevance now. Your config.log says:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> configure:19090: checking for bison<o:p></o:p></p><p class=MsoPlainText>> configure:19106: found /usr/bin/bison<o:p></o:p></p><p class=MsoPlainText>> configure:19117: result: bison -y<o:p></o:p></p><p class=MsoPlainText>> configure:19133: checking for flex<o:p></o:p></p><p class=MsoPlainText>> configure:19149: found /usr/bin/flex<o:p></o:p></p><p class=MsoPlainText>> configure:19160: result: flex<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>so configure is looking for, and finding, bison (supercedes yacc) and<o:p></o:p></p><p class=MsoPlainText>flex (supercedes lex).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>What problem are you seeing here?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Cheers,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>ellie<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On Fri, May 13, 2016, at 05:15 PM, Anatoli via Cyrus-devel wrote:<o:p></o:p></p><p class=MsoPlainText>> Hi all,<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Ken, the 2 errors that don't happen to you only happen to me when<o:p></o:p></p><p class=MsoPlainText>> compiling<o:p></o:p></p><p class=MsoPlainText>> with --enable-backup. I've tested the beta2 tarball as well as the<o:p></o:p></p><p class=MsoPlainText>> current<o:p></o:p></p><p class=MsoPlainText>> git, both errors still happen to me on 2 different machines. Without the<o:p></o:p></p><p class=MsoPlainText>> --enable-backup option these errors don't occur.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Ellie, I'll send the config.log and the resulting make output to you and<o:p></o:p></p><p class=MsoPlainText>> Ken<o:p></o:p></p><p class=MsoPlainText>> directly.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I can confirm that the latest master from the dev git has the patch for<o:p></o:p></p><p class=MsoPlainText>> --disable-squat correctly working and the ICU checking in configure is<o:p></o:p></p><p class=MsoPlainText>> present now too, but maybe it should be converted from a warning to an<o:p></o:p></p><p class=MsoPlainText>> error<o:p></o:p></p><p class=MsoPlainText>> when with --enable-http?<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> DKIM warning doesn't appearing anymore. It would be great to solve the<o:p></o:p></p><p class=MsoPlainText>> "Parts of com_err distribuion were found, but not compile_et" warning<o:p></o:p></p><p class=MsoPlainText>> too.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I'm also getting:<o:p></o:p></p><p class=MsoPlainText>> checking for BIO_accept in -lcrypto... yes<o:p></o:p></p><p class=MsoPlainText>> checking for crypt... no<o:p></o:p></p><p class=MsoPlainText>> checking for crypt in -lcrypt... yes<o:p></o:p></p><p class=MsoPlainText>> Warning (mostly harmless): No library found for -lcrypto<o:p></o:p></p><p class=MsoPlainText>> (same for -lssl)<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I found another issue with the dependencies: the build requires yacc/lex<o:p></o:p></p><p class=MsoPlainText>> when building sieve, though in the Release Notes there is the following<o:p></o:p></p><p class=MsoPlainText>> text: Replaced the et (error table) libary with a version that doesn't<o:p></o:p></p><p class=MsoPlainText>> require lex or yacc. Remove the lex/yacc checking from Configure.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I guess the lex/yacc checking should be placed in the configure again,<o:p></o:p></p><p class=MsoPlainText>> inside the enable-sieve block.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Regards,<o:p></o:p></p><p class=MsoPlainText>> Anatoli<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> From: Ken Murchison [</span><a href="mailto:murch@andrew.cmu.edu"><span lang=EN-US style='color:windowtext;text-decoration:none'>mailto:murch@andrew.cmu.edu</span></a><span lang=EN-US>] <o:p></o:p></span></p><p class=MsoPlainText>> Sent: Wednesday, May 11, 2016 15:44<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> To: Anatoli; </span><a href="mailto:cyrus-devel@lists.andrew.cmu.edu"><span lang=EN-US style='color:windowtext;text-decoration:none'>cyrus-devel@lists.andrew.cmu.edu</span></a><span lang=EN-US><o:p></o:p></span></p><p class=MsoPlainText>> Subject: Re: v3.0<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> On 05/09/2016 02:57 AM, Anatoli via Cyrus-devel wrote:<o:p></o:p></p><p class=MsoPlainText>> > Hi all,<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > I'm testing v3.0.0 beta2. Here goes the feedback, this time for the build<o:p></o:p></p><p class=MsoPlainText>> > process.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > 1. --disable-squat option in configure has no effect. Please see attached<o:p></o:p></p><p class=MsoPlainText>> a<o:p></o:p></p><p class=MsoPlainText>> > patch (configure.ac.patch).<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Patch applied.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > 2. Without icu-dev package make fails with:<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > unicode/ucal.h No such file or directory<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > It somehow depends on libical, i.e. it looks like icu-dev should be<o:p></o:p></p><p class=MsoPlainText>> > installed before building libical. In any case it should be detected in<o:p></o:p></p><p class=MsoPlainText>> > configure to avoid build errors.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> A check for ICU4C has been added to configure.ac<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > 3. With --enable-backup make fails with:<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > /usr/bin/ld: backup/.libs/libcyrus_backup.a(lcb_append.o): undefined<o:p></o:p></p><p class=MsoPlainText>> > reference to symbol 'SHA1_Update@@OPENSSL_1.0.0'<o:p></o:p></p><p class=MsoPlainText>> > //usr/lib64/libcrypto.so: error adding symbols: DSO missing from command<o:p></o:p></p><p class=MsoPlainText>> > line<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Problem: missing -lcrypto for libcyrus_backup.a<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > /usr/bin/ld: imap/.libs/libcyrus_imap.so: undefined reference to symbol<o:p></o:p></p><p class=MsoPlainText>> > 'cyrusdb_fetch'<o:p></o:p></p><p class=MsoPlainText>> > lib/.libs/libcyrus.so: error adding symbols: DSO missing from command line<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Problem: missing lib/libcyrus.la for cyr_backup.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Please see attached a patch for both errors (Makefile.am.patch).<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > With these fixes build completes without errors.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I'm not seeing this problem compiling on my machine. I wonder why?<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > Then I got this new warning:<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > configure: WARNING: Your version of OpenDKIM can not support iSchedule.<o:p></o:p></p><p class=MsoPlainText>> > Consider upgrading to OpenDKIM >= 2.7.0<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > I don't have DKIM on the box where Cyrus runs, in 2.5.7 there was no<o:p></o:p></p><p class=MsoPlainText>> warning<o:p></o:p></p><p class=MsoPlainText>> > about DKIM. Haven't investigated the details yet. DKIM is part of the<o:p></o:p></p><p class=MsoPlainText>> > iSchedule draft, but is it required? And should it be OpenDKIM only or any<o:p></o:p></p><p class=MsoPlainText>> > other DKIM package works too?<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I have commented out the check for DKIM since its not needed for <o:p></o:p></p><p class=MsoPlainText>> anything that sites will deploy any time soon.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > And then there is an old warning (also happens in 2.5.7):<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > configure: WARNING: Parts of com_err distribuion were found, but not<o:p></o:p></p><p class=MsoPlainText>> > compile_et.<o:p></o:p></p><p class=MsoPlainText>> > configure: WARNING: Will build com_err from included sources.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > What should be installed/changed to avoid it? Or maybe the warning itself<o:p></o:p></p><p class=MsoPlainText>> > should be converted to a notice as compile_et is shipped with cyrus-imap<o:p></o:p></p><p class=MsoPlainText>> and<o:p></o:p></p><p class=MsoPlainText>> > everything works as expected?<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Regards,<o:p></o:p></p><p class=MsoPlainText>> > Anatoli<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > -----Original Message-----<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> > From: Anatoli [</span><a href="mailto:me@anatoli.ws"><span lang=EN-US style='color:windowtext;text-decoration:none'>mailto:me@anatoli.ws</span></a><span lang=EN-US>]<o:p></o:p></span></p><p class=MsoPlainText>> > Sent: Tuesday, April 19, 2016 03:39<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> > To: </span><a href="mailto:cyrus-devel@lists.andrew.cmu.edu"><span lang=EN-US style='color:windowtext;text-decoration:none'>cyrus-devel@lists.andrew.cmu.edu</span></a><span lang=EN-US><o:p></o:p></span></p><p class=MsoPlainText>> > Subject: RE: v3.0<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Hi Ellie,<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Thanks for the link! This is the information I was looking for. Great,<o:p></o:p></p><p class=MsoPlainText>> > there's a new beta! I'll test it these days and if it behaves reasonably<o:p></o:p></p><p class=MsoPlainText>> > well, I'll try to deploy it in a small production environment where the<o:p></o:p></p><p class=MsoPlainText>> > users are OK being beta-testers. I'll post here any issues found.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > With respect to the specialuse flags issue, it's not possible to set these<o:p></o:p></p><p class=MsoPlainText>> > flags from cyradm in the latest release (2.5.7). I'll check if it's fixed<o:p></o:p></p><p class=MsoPlainText>> in<o:p></o:p></p><p class=MsoPlainText>> > the 3.0 beta.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > I have a feature suggestion with respect to these flags. I suppose that<o:p></o:p></p><p class=MsoPlainText>> most<o:p></o:p></p><p class=MsoPlainText>> > of the deployments use these flags on some folders from the<o:p></o:p></p><p class=MsoPlainText>> > autocreate_inbox_folders list. So, instead of writing scripts that set<o:p></o:p></p><p class=MsoPlainText>> these<o:p></o:p></p><p class=MsoPlainText>> > flags somehow, what if it would be possible to specify the specialuse flag<o:p></o:p></p><p class=MsoPlainText>> > for each autocreate folder as an optional param (with some (invalid for<o:p></o:p></p><p class=MsoPlainText>> > folder names) char (e.g. ':') as the delimiter)?<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Something like this:<o:p></o:p></p><p class=MsoPlainText>> > autocreate_inbox_folders:<o:p></o:p></p><p class=MsoPlainText>> > Sent:Sent|Trash:trash|Drafts:DRAFTS|Spam:Junk|OtherFolder1|OtherFolder2<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > The format would be defines as:<o:p></o:p></p><p class=MsoPlainText>> > folder[:<specialuse_flag>][|folder[:<specialuse_flag>]]... and<o:p></o:p></p><p class=MsoPlainText>> > <specialuse_flag> would be one of the options from the RFC6154 (section<o:p></o:p></p><p class=MsoPlainText>> 2),<o:p></o:p></p><p class=MsoPlainText>> > interpreted case-insensitively.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > So when the user logs in for the first time, he/she has all the folders<o:p></o:p></p><p class=MsoPlainText>> > created with the necessary flags. IMO, a significant simplification of the<o:p></o:p></p><p class=MsoPlainText>> > mbox creation process.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > I haven't analyzed the code for this feature yet, but it should be quite<o:p></o:p></p><p class=MsoPlainText>> > simple to implement. Just parse the optional params, check if the value is<o:p></o:p></p><p class=MsoPlainText>> > in a predefined array and after creation of the folder, set the requested<o:p></o:p></p><p class=MsoPlainText>> > flag. Every flag could be validated for uniqueness or it may be left up to<o:p></o:p></p><p class=MsoPlainText>> > the Cyrus administrator to decide and specify the correct values (I would<o:p></o:p></p><p class=MsoPlainText>> > prefer the later, the RFC explicitly says it's up to each server<o:p></o:p></p><p class=MsoPlainText>> > implementation (section 3)).<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Regards,<o:p></o:p></p><p class=MsoPlainText>> > Anatoli<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > -----Original Message-----<o:p></o:p></p><p class=MsoPlainText>> > From: Cyrus-devel<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> > [</span><a href="mailto:cyrus-devel-bounces+me=anatoli.ws@lists.andrew.cmu.edu"><span lang=EN-US style='color:windowtext;text-decoration:none'>mailto:cyrus-devel-bounces+me=anatoli.ws@lists.andrew.cmu.edu</span></a><span lang=EN-US>] On Behalf<o:p></o:p></span></p><p class=MsoPlainText>> Of<o:p></o:p></p><p class=MsoPlainText>> > ellie timoney via Cyrus-devel<o:p></o:p></p><p class=MsoPlainText>> > Sent: Sunday, April 17, 2016 22:37<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> > To: </span><a href="mailto:cyrus-devel@lists.andrew.cmu.edu"><span lang=EN-US style='color:windowtext;text-decoration:none'>cyrus-devel@lists.andrew.cmu.edu</span></a><span lang=EN-US><o:p></o:p></span></p><p class=MsoPlainText>> > Subject: Re: v3.0<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Hi Anatoli,<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> >> I'm quite interested in this release and I'd<o:p></o:p></p><p class=MsoPlainText>> >> like to help with testing, simple problems investigation and fixing, and<o:p></o:p></p><p class=MsoPlainText>> >> similar tasks,<o:p></o:p></p><p class=MsoPlainText>> > That would be greatly appreciated :)<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> >> but at least some insight to the current state of the<o:p></o:p></p><p class=MsoPlainText>> >> master is needed for that, i.e. how close it is to an RC, new<o:p></o:p></p><p class=MsoPlainText>> >> functionality expected to work, functionality/configuration changes<o:p></o:p></p><p class=MsoPlainText>> >> compared to v2.5.7, known limitations, etc.<o:p></o:p></p><p class=MsoPlainText>> > Have you looked at the 3.0.0-beta2 that was released last week? Its<o:p></o:p></p><p class=MsoPlainText>> > release notes compare it against the 2.5 series:<o:p></o:p></p><p class=MsoPlainText>> > <a href="http://cyrusimap.org/imap/release-notes/3.0/x/3.0.0-beta2.html"><span style='color:windowtext;text-decoration:none'>http://cyrusimap.org/imap/release-notes/3.0/x/3.0.0-beta2.html</span></a><o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> >> I see the T232 by Ellie has 4 issues that are apparently stopping this<o:p></o:p></p><p class=MsoPlainText>> >> release. Are they the only remaining issues for production-ready state?<o:p></o:p></p><p class=MsoPlainText>> > These are just the very narrow intersection of a) what I'm aware of,<o:p></o:p></p><p class=MsoPlainText>> > that has b) been logged at all, and c) is logged in phabricator where I<o:p></o:p></p><p class=MsoPlainText>> > can mark it as blocking (rather than in bugzilla, the mailing list,<o:p></o:p></p><p class=MsoPlainText>> > private email, etc).<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> >> The roadmap<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> >> (</span><a href="https://cyrusimap.org/overview/cyrus_roadmap.html#cyrus-roadmap"><span lang=EN-US style='color:windowtext;text-decoration:none'>https://cyrusimap.org/overview/cyrus_roadmap.html#cyrus-roadmap</span></a><span lang=EN-US>) says<o:p></o:p></span></p><p class=MsoPlainText>> >> nothing about v3.0 and looks a little outdated.<o:p></o:p></p><p class=MsoPlainText>> > This page looks like a direct import of the page from the old website.<o:p></o:p></p><p class=MsoPlainText>> > I'm not sure quite how old it is, but given it's referencing "2.6" as<o:p></o:p></p><p class=MsoPlainText>> > future, that suggests that it's over a year old...<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> >> I'm personally interested in resolving the "specialuse flags not working<o:p></o:p></p><p class=MsoPlainText>> >> from cyradm" (T199, 198, 191, 121; looks like still pending) issue<o:p></o:p></p><p class=MsoPlainText>> > Are these still issues? Or are they stale tasks that have been fixed<o:p></o:p></p><p class=MsoPlainText>> > but not closed? We've had a number of cyradm metadata patches<o:p></o:p></p><p class=MsoPlainText>> > contributed by a few different people over the last year, so it seems<o:p></o:p></p><p class=MsoPlainText>> > probable that at least some are fixed but the assignees don't know.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> >> Also I made a raw chroot patch for 2.5.7,<o:p></o:p></p><p class=MsoPlainText>> >> I'd like to polish and submit it for review and inclusion in v3.0.<o:p></o:p></p><p class=MsoPlainText>> > That'd be great!<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> >> Should I write to someone in particular to discuss the subject?<o:p></o:p></p><p class=MsoPlainText>> > Everyone working on Cyrus 3.0 is active on this list, so this is<o:p></o:p></p><p class=MsoPlainText>> > probably the best place for it.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > You're also welcome to join our conference calls, they happen at 11am<o:p></o:p></p><p class=MsoPlainText>> > UTC most Mondays on Google Hangouts. Probably the easiest way to join<o:p></o:p></p><p class=MsoPlainText>> > is to come into #cyrus on Freenode IRC at the meeting time and ask for<o:p></o:p></p><p class=MsoPlainText>> > the hangouts link, because it changes occasionally.<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > Cheers,<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > ellie<o:p></o:p></p><p class=MsoPlainText>> ><o:p></o:p></p><p class=MsoPlainText>> > On Sat, Apr 16, 2016, at 04:41 AM, Anatoli via Cyrus-devel wrote:<o:p></o:p></p><p class=MsoPlainText>> >> Hi folks,<o:p></o:p></p><p class=MsoPlainText>> >><o:p></o:p></p><p class=MsoPlainText>> >> Sorry for bothering you again with subj, I haven't received any answer to<o:p></o:p></p><p class=MsoPlainText>> >> the previous mails about it. I'm quite interested in this release and I'd<o:p></o:p></p><p class=MsoPlainText>> >> like to help with testing, simple problems investigation and fixing, and<o:p></o:p></p><p class=MsoPlainText>> >> similar tasks, but at least some insight to the current state of the<o:p></o:p></p><p class=MsoPlainText>> >> master is needed for that, i.e. how close it is to an RC, new<o:p></o:p></p><p class=MsoPlainText>> >> functionality expected to work, functionality/configuration changes<o:p></o:p></p><p class=MsoPlainText>> >> compared to v2.5.7, known limitations, etc.<o:p></o:p></p><p class=MsoPlainText>> >><o:p></o:p></p><p class=MsoPlainText>> >> I see the T232 by Ellie has 4 issues that are apparently stopping this<o:p></o:p></p><p class=MsoPlainText>> >> release. Are they the only remaining issues for production-ready state?<o:p></o:p></p><p class=MsoPlainText>> >> The roadmap<o:p></o:p></p><p class=MsoPlainText><span lang=EN-US>> >> (</span><a href="https://cyrusimap.org/overview/cyrus_roadmap.html#cyrus-roadmap"><span lang=EN-US style='color:windowtext;text-decoration:none'>https://cyrusimap.org/overview/cyrus_roadmap.html#cyrus-roadmap</span></a><span lang=EN-US>) says<o:p></o:p></span></p><p class=MsoPlainText>> >> nothing about v3.0 and looks a little outdated.<o:p></o:p></p><p class=MsoPlainText>> >><o:p></o:p></p><p class=MsoPlainText>> >> I'm personally interested in resolving the "specialuse flags not working<o:p></o:p></p><p class=MsoPlainText>> >> from cyradm" (T199, 198, 191, 121; looks like still pending) issue and in<o:p></o:p></p><p class=MsoPlainText>> >> XAPPLEPUSHSERVICE feature, but I know there are a lot of other<o:p></o:p></p><p class=MsoPlainText>> >> improvements and new libraries support (like LibiCal2.0) that are worth<o:p></o:p></p><p class=MsoPlainText>> >> the effort releasing it ASAP. Also I made a raw chroot patch for 2.5.7,<o:p></o:p></p><p class=MsoPlainText>> >> I'd like to polish and submit it for review and inclusion in v3.0.<o:p></o:p></p><p class=MsoPlainText>> >><o:p></o:p></p><p class=MsoPlainText>> >> Should I write to someone in particular to discuss the subject?<o:p></o:p></p><p class=MsoPlainText>> >><o:p></o:p></p><p class=MsoPlainText>> >> Regards,<o:p></o:p></p><p class=MsoPlainText>> >> Anatoli<o:p></o:p></p><p class=MsoPlainText>> >><o:p></o:p></p><p class=MsoPlainText>> >><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> -- <o:p></o:p></p><p class=MsoPlainText>> Kenneth Murchison<o:p></o:p></p><p class=MsoPlainText>> Principal Systems Software Engineer<o:p></o:p></p><p class=MsoPlainText>> Carnegie Mellon University<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p></div></body></html>