[Erp5-dev] svn-buildpackage - proper way to use SVN for .deb packages

[Łukasz Nowak]

Hello,

Right in in spec/debian and spec/ubuntu repository paths packages are
kept as .dsc file, uncompressed package sources, its source and binary
builds. That way of using repository is inconvenient:
- it is very hard to see changes made to original sources
- it is very hard to see changes in package definition
- there is not automatic builder support

There is 'svn-buildpackage' system, designed specially to track changes
of packages (and its original sources) in version control system.

svn-buildpackage is avaiable for debian (etch (aka testing) and up) and
its derivatives like Ubuntu (dapper and up). This set of scripts
automates changes of package and its original sources, builds package,
creates new debian-way revision, etc. All (uncompressed) package
information are kept in repository so it is very is to track changes in
package, create branches and tags. Typical package tree generated by
svn-buildpackage is attached.

There is need to made conversion from current system to
svn-buildpackage. But there are scripts (attached tree was initially
imported from https://svn.erp5.org/repos/public\
/spec/debian/unstable/python-reportlab/python-reportlab_1.20debian-2.dsc)
which allows easy conversion from non-versioned system to versioned one.

I hope that I'll provided enough information about svn-buildpackage. I'm
testing it right now on our SVN server - it is quite good, works on
debian/unstable and ubuntu/dapper without any problems.

Because such conversion has high impact on current /spec repository I'm
requesting for approval. After one I'll take actions:
* convert python-reportlab in Nexedi's repository to svn-buildpackage
system, by replacing contents of /spec/debian/unstable/python-reportlab
with generated by svn-buildpackage tree
* create HowTo about building packages for such repository on ERP5 wiki
* convert rest of *external* packages (!^erp5-) to svn-buildpakcage system
* after proper policy of ^erp5- snapshotting - convert them (well -
this is another topic)

Additionally there is svn-autoreleasedeb system for automagic build of
released debs.

Thanks,
Luke

[Łukasz Nowak]

Hello,

?ukasz Nowak napisa?(a):
(...)

Some references about svn-buildpackage:
* http://workaround.org/moin/SvnBuildpackage
* http://packages.debian.org/unstable/devel/svn-buildpackage

Luke

[Łukasz Nowak]

Hello,

Post by Łukasz Nowak
Hello,

(...)

Are there any decisions taken for .deb builder? Is svn-buildpackage
acceptable? I'd like to continue my community work with packages.

Thanks,
Luke

[Yoshinori Okuji]

Post by Łukasz Nowak
Hello,

Post by Łukasz Nowak
Hello,

(...)
Are there any decisions taken for .deb builder?

No.

Post by Łukasz Nowak
Is svn-buildpackage
acceptable?

I am not sure if it is so good. But if there is no other way, we must live
with it.

YO

[Łukasz Nowak]

Hello,

Yoshinori Okuji napisa?(a):
(...)

Post by Yoshinori Okuji

Post by Łukasz Nowak
Are there any decisions taken for .deb builder?

No.

Post by Łukasz Nowak
Is svn-buildpackage acceptable?

I am not sure if it is so good. But if there is no other way, we must
live with it.

I've set up svn-buildpackage-based[1] repository on our server, which is
available for external use[2]

I used script:

for d in * ; do
cd $d
svn-inject -q `ls -r *dsc | head -n1 ` \
https://gpl.ventis.pl/svn/spec/debian/unstable/
cd ..
done

run from https://svn.erp5.org/repos/public/spec/debian/unstable/ checkout.

I know (feel is better maybe ;) ) that such conversion has big impact
for repository structure, so for now I'll make changes to packages on
our repository, then import them to Nexedi with Nexedi's layout.

I think that it will be possible to synchronize svn-builpackage changes
from our repository structure to Nexedi, eg. by using tools like svk.

That way allow me to master in svn-buildpackage mechanisms, which allow
to use "upstream sources" stored in svn-buildpackage repository (eg.
Zope Products developed by Nexedi). Our gpl repository is in state
experimental, so if it's needed I may create accounts to hack with
svn-buildpackage system and/or recreate repository from scratch. If
account is needed please contact me personally.

Bye,
Luke

[1]https://gpl.ventis.pl/doc/svn-buildpackage/HOWTO.html/index.html
[2]https://gpl.ventis.pl/svn/spec/debian/unstable/