[Pkg-Cyrus-imapd-Debian-devel] Upload to debian/experimental?
Sven Mueller
pkg-cyrus-imapd-debian-devel@lists.alioth.debian.org
Mon, 02 May 2005 23:09:13 +0200
Henrique de Moraes Holschuh wrote on 02/05/2005 22:15:
> On Mon, 02 May 2005, Sven Mueller wrote:
(autogen.sh)
>>Mostly because I don't trust it regarding regeneration of some files,
>
> Heh, the debian/deletable.files hack needs some work, and it *requires* the
> .orig.tar.gz tarball in the parent directory of the build tree for proper
> updating :) Most of the time, it should be empty, only at final build
> should it look at the svn/cvs export, compare to what is in the tarball, and
> promptly rm the difference.
Well, I already guessed that that's what it should do. However, after
porting from your latest 2.1.* cyrus package to the 2.2 branch, I
initially had a lot of trouble with unrepresentable changes in the
diff.gz and I was unable to run dpkg-buildpackage twice from within the
same directory (i.e. after patching some file when the buildprocess
didn't have the result I intended).
> If it is causing trouble with your svn setup, just comment the part of
> autogen.sh that writes a non-empty deletable.files. It is better to keep
> the code in debian/rules that deals with autotools-dev and autogen.sh
> active.
I reactivated autogen.sh calling and currently check it's result. I have
no doubt that the resulting binary packages will be OK, but I also want
reproducable source packages ;-)
>>especially debian/deletable.files (or whatever it is actually called).
>>It creates an empty file there. Any hint from the author? ;-)
>
> I have yet to try to use svn-buildpackage. I will soon, and when that
> happens, expect a lot of patches to make it work as neatly as it did with
> cvs-buildpackage. Then you will see why I like those hacks :)
I can guess why. However, It seems to have deleted a few more files for
me than it should have.
Anyway, I repacked the upstream source anyway, removing auto-generated
files and empty directories mostly. Those simply increased the size of
the debian sources (diff.gz) a lot and made it impossible to read/check
it. And with the repacked upstream, we don't delete that many files
anymore ;-)
Only problem I see with my repacked upstream is that I (initially by
accident, but I didn't correct it yet) removed config.guess and
config.sub from there, too. I'm not sure wether I should just mention
that in the README.repacked file (along with a documentation how to get
uptodate copies) as it is now or to include the files there (and make
debian diff.gz much larger).
cu,
sven
PS: After updating the readme.repacked, I write-protected the
orig.tar.gz in the SVN repository, so if we need to change it in the
future, I have to drop that restriction temporarily.