<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
Benjamin Seidenberg wrote:
<blockquote cite="mid451D59A5.7050501@dlgeek.net" type="cite">
<pre wrap="">Farzad FARID wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Sven Mueller wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Farzad, I'm not sure wether I understand you correctly. Does that mean
that you re-packaged the .orig.tar.gz? If so: You shouldn't do this,
</pre>
</blockquote>
<pre wrap="">Yes I did... Actually I tried to blindly do something similar to the 2.2
packaging. I think the 2.2 orig.tar.gz contains "configure" and
"automake" related files that are updated, therefore different, from the
upstream source. Is that right?
</pre>
</blockquote>
<pre wrap=""><!---->No. These are regenerated at build time. 2.2 is the exact tarball
released from upstream. (As is 2.3, I know because I double checked the
md5/sha1 sums)
</pre>
</blockquote>
Right, I *tought* I repackaged the files, but in fact I didn't, sorry.
Actually I was think of all the messy things I had to do to create
"99-update-autoconf.dpatch" correctly.<br>
<br>
<blockquote cite="mid451D59A5.7050501@dlgeek.net" type="cite">
<blockquote type="cite">
<pre wrap="">The problem *may* actually be that using snv-builpackage (or
pbuilder/cowbuilder for my part) hides theses problems.
I *think* (and then again I have to check this all again) that the
"debian/rules clean" suppresses files that are present in the upstream
cyrus-imapd 2.3 tar.gz. Therefore, because I didn't want to touch too
much to the "rules" file, and because "debuild" kept messing up my
source tree, I switched to pbuilder.
So, I asking for help and advise :) If we redo the orig.tar.gz the most
impacted file will be 99-update-autoconf.dpatch, but we also have to
update the "deletable files" list, right?
</pre>
</blockquote>
<pre wrap=""><!---->I'll take a look at your branch again, but I am fairly sure I was doing
multiple compiles of my 2.3 branch. Sorry, but I have to leave in 10
minutes and can't check it out now.
</pre>
</blockquote>
I can confirm that I can't compile cyrus 2.2 twice. I ran "debuild -uc
-us" once, and then tried to run it again and it failed: The problem is
that "debian/rules clean" cannot be run anymore after a build. This is
the same problem I have with cyrus 2.3. That's why I tried to fiddle
with the diffs, the tar.gz, etc. and thought erroneously that I had
modified the orig.tar.gz (which I didn't, luckily).<br>
<br>
Here is the result of my investigation on cyrus-imapd-2.2_2.2.13-7. If
there is anything false in my findings, it's because I don't know the
whole history of this package and I'm not a dpkg-dev expert yet, so
please excuse me in advance:<br>
- I think there is a bad interaction between "clean" and "patch",
"patch" can only be run after "clean", otherwise the patch #99 won't
apply. Therefore it's not reversible.<br>
- Furthermore, "configure-stamp" (which is executed after "patch")
deletes 2 files modified by "patch", config.sub and config.guess. This
is not reversible either.<br>
<br>
Are these problems that should be corrected, or features?<br>
<br>
Regards<br>
<pre class="moz-signature" cols="72">--
Farzad FARID <a class="moz-txt-link-rfc2396E" href="mailto:ffarid@pragmatic-source.com"><ffarid@pragmatic-source.com></a>
Architecte Open Source / Pragmatic Source
<a class="moz-txt-link-freetext" href="http://www.pragmatic-source.com/">http://www.pragmatic-source.com/</a></pre>
</body>
</html>