<div dir="ltr"><div><div><div><div><div><div><div><div><div>Hi!<br><br></div>Good news. Maybe I'm almost there.<br><br></div>After your suggestion to change the debian/rules I've proceed with small modifications of other files in debian directory. I like to list them here to avoid mistakes.<br><br></div>In debian/rules I've added a rule "override_dh_auto_test:" with no action. I understand that what this produces is to avoid the step of unit tests, isn't it? I'm not sure if this is a good idea, but it allows me to continue. Before I've removed, from the "override_dh_auto_configure:" rule the parameter '-- --enable-gtk-doc' because it was making fail the configure, but I suspect this is an issue that would have relation with packages I've installed. I'm a kde user.<br><br></div>In debian/libufo-dev.install I've modified the paths to remove the intermediate starts. That is, I've modified 'usr/lib/*/lib*.so' to 'usr/lib/lib*.so', and also 'usr/lib/*/pkgconfig' to 'usr/lib/pkgconfig'. As well as in debian/libufo0.install I've modified 'usr/lib/*/lib*.so.*' to 'usr/lib/lib*.so.*', and in debian/gir1.2-ufo-0.0.install modify 'usr/lib/*/girepository-1.0' to 'usr/lib/girepository-1.0'.<br><br></div>With this changes and the execution of 'dch -v 0.8.0-1 "Update to version 0.8.0." && debcommit -a && git-buildpackage', the process completes with the generation of the expected *.deb files: [gir1.2-ufo-0.0_0.8.0-1_amd64.deb, libufo0_0.8.0-1_amd64.deb, libufo0-dbg_0.8.0-1_amd64.deb, libufo-bin_0.8.0-1_amd64.deb, libufo-data_0.8.0-1_all.deb, libufo-dev_0.8.0-1_amd64.deb, libufo-doc_0.8.0-1_all.deb], all of them described in debian/control.<br><br></div>I've managed also two environment variables (DEBEMAIL & DEBFULLNAME) to avoid a misconfiguration of them due to local definitions, and It has been able to request to sign those packages. This also has an effect on the debian/changelog file.<br><br></div>Having this *.deb files, is now the time to commit to the remote?<br><br></div>Thanks!<br><br></div>/Sergi.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 30, 2015 at 11:34 AM, PICCA Frederic-Emmanuel <span dir="ltr"><<a href="mailto:frederic-emmanuel.picca@synchrotron-soleil.fr" target="_blank">frederic-emmanuel.picca@synchrotron-soleil.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Sergi,<br>
<span class=""><br>
<br>
> I think it has work and now I should contact the developer for unit test issue. Well, with the last indications I've installed some dependencies I haven't installed and git-buildpackage almost works. And I say almost because when it enters test process, it<br>
remains there with no more interaction. Last lines are:<br>
<br>
> Running tests...<br>
<br>
> /usr/bin/ctest --force-new-ctest-process -j1<br>
<br>
> Test project /home/serguei/src/debian/ufo-core/obj-x86_64-linux-gnu<br>
<br>
> Start 1: test-suite<br>
<br>
</span>If you want to skip the unit test for now to check that the rest of the pacakging is ok just add<br>
<br>
override_dh_auto_test:<br>
<br>
in the debian/rules file.<br>
<br>
<br>
Indeed at the end it would be a must to have the unit test during the build and also to add the autopkgtest :)<br>
<span class=""><br>
> And it doesn't consume an appreciable cpu resource, memory neither anything. *dsc, *debian.tar.gz and *amd64.build files are well created in the parent directory.<br>
<br>
> I think I'm getting closer and I start understanding how the packaging process is.<br>
<br>
</span>Great to hear that it is not that difficult ;)<br>
<span class=""><br>
> Thanks, I hope soon I'll do the commit to have the auto made package.<br>
<br>
</span>Cheers<br>
<br>
Fred<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
/Sergi.<br>
<br>
<br>
<br>
<br>
On Mon, Jun 29, 2015 at 10:16 AM, PICCA Frederic-Emmanuel<br>
<<a href="mailto:frederic-emmanuel.picca@synchrotron-soleil.fr">frederic-emmanuel.picca@synchrotron-soleil.fr</a>> wrote:<br>
<br>
<br>
Hello Sergi,<br>
<br>
<br>
<br>
<br>
<br>
> I surrender... I've been playing this weeks trying to understand how can I include in the git repository with the debian sources of the ufo-core the tag 0.8.0 from the author's repository and I can find how. I've tried > every thing I thought useful, and<br>
almost everything I read, starting from the traces from Frédéric followed by many howto searches.<br>
<br>
<br>
<br>
Freeze ;)<br>
<br>
<br>
<br>
> I can summarize it in to main paths that I thing have possibilities.<br>
<br>
<br>
<br>
> a) Using both repos to merge them.<br>
<br>
> $ git clone<br>
<a href="https://github.com/ufo-kit/ufo-core" rel="noreferrer" target="_blank">https://github.com/ufo-kit/ufo-core</a> && cd ufo-core<br>
<br>
> $ git remote add debian git+ssh://<a href="http://git.debian.org/git/debian-pan/packages/ufo-core.git" rel="noreferrer" target="_blank">git.debian.org/git/debian-pan/packages/ufo-core.git</a><<a href="http://git.debian.org/git/debian-pan/packages/ufo-core.git" rel="noreferrer" target="_blank">http://git.debian.org/git/debian-pan/packages/ufo-core.git</a>><br>
&& git fetch debian<br>
<br>
> $ git checkout -b v0.8.0<br>
<br>
<br>
<br>
> What blocks me in this option has been how to merge the tag with a new upstream branch.<br>
<br>
<br>
<br>
> b) Using the watch file. It's the option that looks more promising because it looks made to do that:<br>
<br>
> $ git clone git+ssh://<a href="http://git.debian.org/git/debian-pan/packages/ufo-core.git" rel="noreferrer" target="_blank">git.debian.org/git/debian-pan/packages/ufo-core.git</a><<a href="http://git.debian.org/git/debian-pan/packages/ufo-core.git" rel="noreferrer" target="_blank">http://git.debian.org/git/debian-pan/packages/ufo-core.git</a>><br>
&& cd ufo-core<br>
<br>
> $ uscan --download --verbose<br>
<br>
<br>
<br>
> Then I have a file ../ufo-core-0.8.0.tar.gz together with a symlink with the *orig* label. But after that I cannot find how to have an upstream branch with the newer code.<br>
<br>
<br>
<br>
Here I will describe how I add a new upstream release to the debian repository.<br>
<br>
<br>
<br>
- First I do not put the real git upstream in the debian package repository. (If I rememmber correctly there was some discussion about how to put the upstream repository into the debian repo but with no official consensus, the other way arround is another<br>
quetion...)<br>
<br>
<br>
<br>
- for now the simplest things to do is to clone only the debian repository (your second solution).<br>
<br>
- use uscan to download the lastest version. (already done by you nice :). A working watch file is really import for the debian infrastructure.<br>
<br>
it facilitate a lot the upstream integration :)<br>
<br>
<br>
<br>
- and then integrate this new version in the debian repository.<br>
<br>
<br>
<br>
in order to integrate the new upstream, you need at least two branches (master + upstream)<br>
<br>
<br>
<br>
so<br>
<br>
<br>
<br>
git checkout -t origin/upstream<br>
<br>
git checkout master<br>
<br>
git-import-orig --pristine-tar ../ufo-core-0.8.0.targ.gz<br>
<br>
<br>
<br>
then you should have to answer the question of the version<br>
<br>
just put 0.8.0<br>
<br>
<br>
<br>
once done you should have a new upstream/0.8.0 tag<br>
<br>
<br>
<br>
you should be on the master branch<br>
<br>
<br>
<br>
then you can start to fix the debian files.<br>
<br>
<br>
<br>
build your package with<br>
<br>
<br>
<br>
git-buildpackage<br>
<br>
<br>
<br>
if you do not want to commit you change until it is ok<br>
<br>
<br>
<br>
git-buildpckage --git-ignore-new<br>
<br>
<br>
<br>
Just tell me if it works for you.<br>
<br>
<br>
<br>
Cheers<br>
<br>
<br>
<br>
Fred<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>