Re: svn/git repositories, and clean:: target in cdbs.
Stefano Zacchiroli a écrit :
On Sun, Feb 08, 2009 at 04:34:36PM +0100, Guillaume Yziquel wrote:
Stefano Zacchiroli a écrit :
Then something is broken:
yziquel@seldon:~/sandbox$ svn co svn+ssh://svn.debian.org/svn/pkg-ocaml-maint
Password: Password: Password: Permission denied
(publickey,keyboard-interactive).
svn: Connexion fermée de façon inattendue
yziquel@seldon:~/sandbox$
It is simply you that are not using the right interface. If you have
an alioth account you can use svn+ssh and then use your alioth
credentials. You can debug that ssh connection by plainly doing "ssh
alioth.debian.org" and see if that works or not.
Otherwise, you can access svn in read-only mode by using the access
path svn://svn.debian.org//.... which will not require any
password. Again this is nothing Debian OCaml specific, but plain
alioth access rule, you can find more info on wiki.debian.org/Alioth
or something.
OK. Fine. My point was not that the svn repository is broken, but that
the documentation/policy could be amended in order for things to be clearer.
Currently the policy states:
http://pkg-ocaml-maint.alioth.debian.org/ocaml_packaging_policy.html/x565.html
C.2. How to obtain a copy of the SVN repository
You can obtain a copy of debian-ocaml-maint SVN repository by
svn co svn+ssh://svn.debian.org/svn/pkg-ocaml-maint
You must be member of the Debian OCaml Task Force in order to have write access to the repository.
It could be modified like this:
C.2. How to obtain a copy of the SVN repository
You can obtain a copy of debian-ocaml-maint SVN repository by
svn co svn://svn.debian.org/svn/pkg-ocaml-maint
In order to have write access to the repository, you can access it by
svn co svn+ssh://svn.debian.org/svn/pkg-ocaml-maint
You must be member of the Debian OCaml Task Force in order to have write access to the repository.
This way, I could have had a copy of the repository without wondering
what has been going wrong.
Nevertheless, I've had a look a ocaml-csv and ocaml-inotify, and
they have it in the order I proposed. And it did not work for me in
the order of the policy.
So, to be sure, you mean that switching the order make building fail?
If so, please tell us which order works and which doesn't, so that we
can try to reproduce the problem.
Building the files themselves is going rather fine.
Building the *package* is not fine, since the
~/src/pgocaml/deb/ocaml-pgocaml-1.1/debian/libpgocaml-ocaml-dev/usr/lib/ocaml/3.10.2/
directory does not exist when the findlib_install target of the Makefile
is invoked. ocamlfind does not find this directory and thus throws an error.
If you want to reproduce the problem, you can download the packaged i've
built for pgocaml from the following URL:
http://yziquel.homelinux.org/debian/unstable/
Please note that this is very far from being a 100% uptime server.
This apt repository is available by putting
deb http://localhost/debian stable/
deb-src http://localhost/debian stable/
deb http://localhost/debian testing/
deb-src http://localhost/debian testing/
deb http://localhost/debian unstable/
deb-src http://localhost/debian unstable/
in the /etc/apt/sources.list file, and the public key can be found at
http://yziquel.homelinux.org/debian/yziquel-debian-packages.asc
You can also get the relevant files at:
http://yziquel.homelinux.org/ocaml/libpgocaml-ocaml-dev_1.1-1_amd64.deb
http://yziquel.homelinux.org/ocaml/ocaml-pgocaml-1.1-being-packaged.tar.gz
http://yziquel.homelinux.org/ocaml/ocaml-pgocaml_1.1-1.diff.gz
http://yziquel.homelinux.org/ocaml/ocaml-pgocaml_1.1-1.dsc
http://yziquel.homelinux.org/ocaml/ocaml-pgocaml_1.1-1_amd64.build
http://yziquel.homelinux.org/ocaml/ocaml-pgocaml_1.1-1_amd64.changes
http://yziquel.homelinux.org/ocaml/ocaml-pgocaml_1.1.orig.tar.gz
You can simply untar ocaml-pgocaml-1.1-being-packaged.tar.gz, and try it
by reverting the include statements in the debian/rules file.
The one that does not work is the one from the policy:
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/makefile.mk
include /usr/share/cdbs/1/class/ocaml.mk
include /usr/share/cdbs/1/rules/dpatch.mk
and the one that works is the one in the
ocaml-pgocaml-1.1-being-packaged.tar.gz file:
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/rules/dpatch.mk
include /usr/share/cdbs/1/class/makefile.mk
include /usr/share/cdbs/1/class/ocaml.mk
I hope this will help you reproduce the problem I encountered.
yziquel@seldon:~/src/pgocaml/deb/ocaml-pgocaml-1.1$ debuild -i -us -uc -b
I'm missing something here, where are you getting pgocaml from? I
can't find it in our svn or git ... Is that a package of yours or
what?
It's a package I built this week-end. It packages the PG'OCaml library from:
http://developer.berlios.de/projects/pgocaml/
It works on my box, and I'd like to get it into Debian at one point in time.
If you put dpatch.mk in second position, as I've proposed, the output is:
OK, I see have you had a look at
http://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml#id2527938 ? It
is stated that dpatch.mk must always come after autotools.mk, maybe it
is that your problem?
I do not use autotools. My setup is only:
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/rules/dpatch.mk
include /usr/share/cdbs/1/class/makefile.mk
include /usr/share/cdbs/1/class/ocaml.mk
and it has been lamely borrowed from the ocaml-inotify package.
So, in the former output (includes according to policy), you do not
have the creation of the
/home/yziquel/src/pgocaml/deb/ocaml-pgocaml-1.1/debian/libpgocaml-ocaml-dev/usr/lib/ocaml/3.10.2/pgocaml
directory, and ocamlfind complains. In the latter output, the
directory has been created correctly, and ocamlfind doesn't
complain.
Please give us a link to the package you are working on, as I'd like
to debug it a bit more.
See above for the links.
Thanks for taking the time of investigating this.
Cheers.
It was my pleasure.
--
Guillaume Yziquel
http://yziquel.homelinux.org/
Reply to: