<div dir="ltr">Hey Andreas,<br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 12, 2015 at 12:25 PM, Andreas Tille <span dir="ltr"><<a href="mailto:andreas@an3as.eu" target="_blank">andreas@an3as.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Malihe,<br>
<span><br>
On Tue, May 12, 2015 at 09:27:36AM +0430, Malihe Asemani wrote:<br>
> ><br>
> > Did you created a GPG key?<br>
><br>
> The pkgos-setup-sbuild creates GPG key. Wrong part of this process was the<br>
> uid information in the key. I dont know how can i configure<br>
> pkgos-setup-sbuild for creating a GPG key with my information. I think it<br>
> is using User and Hostname for crating key-uid information. Anyway, I<br>
> updated the key with the information which I had added to changelog before.<br>
> Therefore, this problem is solved now. Thank you for your hint :)<br>
<br>
</span>Nice that this is solved.<br>
<span><br></span></blockquote><div>Yes :) </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
> ><br>
> > cme fix dpkg-control<br>
> ><br>
> > which does a similar thing regarding formatting first. After this I<br>
> > would try the suggested `pkgos-reqsdiff`. The rationale is that I<br>
> > prefer generic packaging (see in Debian Med policy what packages are<br>
> > needed to install cme).<br>
> ><br>
> Interesting tool ! I used it and push the results to git. Thank you.<br>
<br>
</span>Hmmm, did you really pushed or just commited and forgot to push by<br>
chance? I see:<br>
<br>
commit 266df93ff2e60659fd7c6092dae73a1a875215b0<br>
Author: Malihe Asemani <<a href="mailto:ml.asemani@gmail.com" target="_blank">ml.asemani@gmail.com</a>><br>
Date: Thu May 7 11:05:06 2015 +0000<br>
<br>
Adapt watch file with tag-base-packaging<br>
<br>
<br>
as last commit.<br>
<span><br></span></blockquote><div>OMG! I'm really sorry. I've forgotten to push it! I push it just now.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
> > If you ask me please try also:<br>
> ><br>
> > ./debian/rules gen-orig-xz<br>
> > gbp buildpackage<br>
> ><br>
> > This should also build the package without any wrapper. I'd prefer at<br>
> > least knowing what happens behind the scenes (even if gbp is also a<br>
> > non-trival wrapper - but it is a generic packaging tool working in all<br>
> > teams).<br>
> ><br>
> first I used pkgos-reqdiff and then cme. Afterwards, I did 'debuild -us<br>
> -uc', 'gpg buildpackage', and 'pkgos-bop'. if I remove<br>
> "override_dh_auto_test" from the rule file,<br>
<br>
</span>Its a valid procedure to temporarily deactivate testing when developing<br>
a package. However, in the end we should approach to run the test suite<br>
at build time.<br>
<span><br></span></blockquote><div>uhum. Thanks for comment :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
> 'debuld -us -uc' and 'gbp<br>
> buildpackage' will create the package with no more errors.<br>
<br>
</span>Seems you are using debuild / gbp on your local machine and not with<br>
sbuild. </blockquote><div>I use all of these three ways to build the package. </div><div>It helps me to find out is the problem related to building the package, or it is related to other processes like some special openstack or gbp process.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I tried using cowbuilder (an alternative to sbuild which I have<br>
simply installed on my build machine) and was running into an issue.<br>
<br>
The rationale why any serious package should be build in a minimal<br>
chroot environment (which is what sbuild / cowbuilder are creating) is,<br>
that any package should be able to build with the specified<br>
Build-Dependends (and not additional random software installed on your<br>
system) and *offline* since the build process should not depend from any<br>
data fetched from some random location in the internet.<br>
<br>
When doing so I'm running into the issue mentioned by Thomas:<br>
<br>
Depends: python-oslo-concurrency (>= 1.8.0) which is a virtual package.<br>
Depends: python-oslo-config (>= 1:1.9.3) which is a virtual package.<br>
Depends: python-oslo-context (>= 0.2.0) which is a virtual package.<br>
Depends: python-oslo-db (>= 1.7.0) which is a virtual package.<br>
Depends: python-oslo-i18n (>= 1.5.0) which is a virtual package.<br>
Depends: python-oslo-log (>= 1.0.0) which is a virtual package.<br>
Depends: python-oslo-messaging (>= 1.8.0) which is a virtual package.<br>
Depends: python-oslo-rootwrap (>= 1.6.0) which is a virtual package.<br>
Depends: python-oslo-serialization (>= 1.4.0) which is a virtual package.<br>
Depends: python-oslo-utils (>= 1.4.0) which is a virtual package.<br>
Unable to resolve dependencies! Giving up...<br>
<br>
Please replace this by the python-oslo.* packages. May be you just did<br>
so and simply forgot to push?<br>
<span><br></span></blockquote><div>Yes. I've done it. and it is pushed now :P</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
> 'pkgos-bop' will<br>
> create package too, but just it fails in the steps after creating package:<br>
><br>
> Finished running lintian.<br>
> Now signing changes and any dsc files...<br>
> signfile manila_2015.1.0-1~bpo80+1.dsc Malihe Asemani <<a href="mailto:ml.asemani@gmail.com" target="_blank">ml.asemani@gmail.com</a><br>
> ><br>
><br>
> signfile manila_2015.1.0-1~bpo80+1_amd64.changes Malihe Asemani <<br>
> <a href="mailto:ml.asemani@gmail.com" target="_blank">ml.asemani@gmail.com</a>><br>
><br>
> Successfully signed dsc and changes files<br>
> HEAD is now at df2a176 remove test part<br>
> W: python-manila: latest-debian-changelog-entry-without-new-version<br>
> P: python-manila: no-homepage-field<br>
> W: manila-common: latest-debian-changelog-entry-without-new-version<br>
> P: manila-common: no-homepage-field<br>
> P: manila-common: maintainer-script-without-set-e postinst<br>
> W: manila-scheduler: latest-debian-changelog-entry-without-new-version<br>
> P: manila-scheduler: no-homepage-field<br>
> W: manila-api: latest-debian-changelog-entry-without-new-version<br>
> P: manila-api: no-homepage-field<br>
<br>
</span>Try `lintian -i` (as well as the relevant severity levels since P is not<br>
default but helpful anyway) if you need a more detailed explanation what<br>
this means and how to fix it. As always feel free to ask if something<br>
remains unclear.<br>
<br></blockquote><div>let me dig into that. I need time </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The good thing is, that you now *have* a package at least which is some<br>
point we can continue working from. :-)<br>
<span><br></span></blockquote><div>Yeap. Exactly :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
> ===> Updating schroot jessie-amd64<br>
> jessie-amd64: Performing update.<br>
> Hit <a href="http://mirror.xamin.ir" target="_blank">http://mirror.xamin.ir</a> jessie InRelease<br>
> Hit <a href="http://mirror.xamin.ir" target="_blank">http://mirror.xamin.ir</a> jessie/main Sources<br>
> Hit <a href="http://mirror.xamin.ir" target="_blank">http://mirror.xamin.ir</a> jessie/main amd64 Packages<br>
> Hit <a href="http://mirror.xamin.ir" target="_blank">http://mirror.xamin.ir</a> jessie/main Translation-en<br>
> Ign <a href="http://kilo-jessie.pkgs.mirantis.com" target="_blank">http://kilo-jessie.pkgs.mirantis.com</a> jessie-kilo-backports-nochange<br>
> InRelease<br>
> Ign <a href="http://kilo-jessie.pkgs.mirantis.com" target="_blank">http://kilo-jessie.pkgs.mirantis.com</a> jessie-kilo-backports InRelease<br>
> Get:1 <a href="http://kilo-jessie.pkgs.mirantis.com" target="_blank">http://kilo-jessie.pkgs.mirantis.com</a> jessie-kilo-backports-nochange<br>
</span>> ...<br>
<br>
Looks as if pkgos tools also do the backporting here. While this is<br>
nice it does not bring us forward in *learning* how to package. May be<br>
it makes sense to skip this somehow for the moment to save time and come<br>
back once we are successful with a package for unstable.<br>
<span><br></span></blockquote><div>Uhum. Agree.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
> FAIL:<br>
> unittest.loader.ModuleImportFailure.manila.tests.network.neutron.test_neutron_plugin<br>
> ----------------------------------------------------------------------<br>
> Traceback (most recent call last):<br>
> _StringException: Traceback (most recent call last):<br>
> ImportError: Failed to import test module:<br>
> manila.tests.network.neutron.test_neutron_plugin<br>
><br>
> FAIL:<br>
> unittest.loader.ModuleImportFailure.manila.tests.share.drivers.netapp.dataontap.client.test_client_cmode<br>
> ----------------------------------------------------------------------<br>
> Traceback (most recent call last):<br>
> _StringException: Traceback (most recent call last):<br>
> ImportError: Failed to import test module:<br>
> manila.tests.share.drivers.netapp.dataontap.client.test_client_cmode<br>
><br>
> FAIL:<br>
> unittest.loader.ModuleImportFailure.manila.tests.share.drivers.netapp.dataontap.cluster_mode.test_lib_multi_svm<br>
> ----------------------------------------------------------------------<br>
> Traceback (most recent call last):<br>
> _StringException: Traceback (most recent call last):<br>
> ImportError: Failed to import test module:<br>
> manila.tests.share.drivers.netapp.dataontap.cluster_mode.test_lib_multi_svm<br>
<br>
</span>Hmmmm. I admit this goes beyond my knowledge. May be Debian Openstack<br>
people could give a hint here or you might ask upstream. It might<br>
mean a missing (Build-)Dependency (either packaged or missing).<br>
<br></blockquote><div>good hint. I will check Dependencies again. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Kind regards and nice that you are making progress<br>
<div><div></div></div></blockquote><div><br></div><div>Thank you for helping me to make some progress :)</div><div><br></div><div>Warmest regards,</div><div>Mali </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div> <br></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
Andreas.<br>
<br>
--<br>
<a href="http://fam-tille.de" target="_blank">http://fam-tille.de</a><br>
<br>
_______________________________________________<br>
Openstack-devel mailing list<br>
<a href="mailto:Openstack-devel@lists.alioth.debian.org" target="_blank">Openstack-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/openstack-devel" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/openstack-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr">------------<br><div><span style="color:rgb(51,51,51);font-family:Verdana,sans-serif;font-size:12.7272720336914px;line-height:18px">you can't start the next chapter if you keep re-reading the last one</span><br></div><div><span style="color:rgb(51,51,51);font-family:Verdana,sans-serif;font-size:12.7272720336914px;line-height:18px"><br></span></div><div>mali</div></div></div></div></div>
</div></div>