<div dir="ltr">Hey Andreas,<br><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 30, 2015 at 6:41 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi Malihe,<br>
<span><br>
On Wed, Apr 29, 2015 at 01:51:15AM +0430, Malihe Asemani wrote:<br>
> root@mali-Lenovo-IdeaPad-Z410:/git/debian/Debian-ops# gbp-clone ssh://<br>
> <a href="http://git.debian.org/git/openstack/manila_Mali.git" target="_blank">git.debian.org/git/openstack/manila_Mali.git</a><br>
<br>
</span>I was able to clone this.<br>
<br>
One first important remark: Please never ever do your packaging work as<br>
root. All steps you do should be done by a normal user.<br>
<span><br></span></blockquote><div>Okay. But may I know what is wrong with do it as root?<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span>
</span><span><br>
</span>I'd like to repeat: Please never use your root account.<br>
</blockquote><div>Sure :)<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Moreover I'd suggest to use ssh-agent to not need to provide the<br>
password all the time. If you once use<br>
<br>
ssh-add ${HOME}/.ssh/id_rsa_debian_2<br>
<br>
this should do the trick.<br>
<br></blockquote><div>Uhum. tnx<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
> root@mali-Lenovo-IdeaPad-Z410:/git/manila_Mali# git tag<br>
<span>> 2014.2<br>
> 2014.2.b3<br>
> 2014.2.rc1<br>
> 2014.2.rc2<br>
> 2015.1.0b1<br>
> 2015.1.0b2<br>
> 2015.1.0b3<br>
> 2015.1.0rc1<br>
> 2015.1.0rc2<br>
><br>
</span>> #I removed tag 2015.1.0rc2 because the last stable version of Manila in ubuntu is tag 2015.1.0rc1.<br>
<br>
Ahhh, I see your intention. However, we do not want to package the last<br>
stable version of Manila in Ubuntu but rather the last stable version<br>
provided by *upstream*. (I hope you are comfortable with the Debian<br>
"slang" that upstream are the authors of the software we are packaging.)<br>
<br>
> #I guess as the first step, it is better to work with the same version which is used in Ubuntu.<br>
<br>
I do not see any advantage in this - neither for learning the packaging<br>
(assume we would start from scratch we would have no orientation like<br>
this) nor for the result (why packaging old software and how should<br>
Ubuntu profit from our work if they do just have what we are working on)<br>
<br>
> #After first release of manila*.deb packages for Debian, we can pull other commits on Manila and merge them too.<br>
> #What do you think about this aproach?<br>
<br>
I see you point but lets be a bit more brave. ;-)<br>
<br></blockquote><div>:))) Okay. Let's do it :)<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
The other things are looking good so far. Would you agree with my<br>
arguments for taking the last upstream version? If yes, you have<br>
two options. Either you use as I suggested<br>
<br>
gbp-clone ssh://<a href="http://git.debian.org/git/openstack/manila.git" target="_blank">git.debian.org/git/openstack/manila.git</a><br>
<br>
and continue to work from here or you redo what you did but stick<br>
to the latest tag. This should give you the same repository.<br>
<br></blockquote><div>I cloned your repo.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
The next step should be to use git-buildpackage. Did you tried this<br>
on your repository? Did you also run into<br>
<span><br>
<br>
dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future<br>
fakeroot debian/rules clean<br>
</span>debian/rules:6: /usr/share/openstack-pkg-tools/pkgos.make: No such file or directory<br>
dh /usr/share/openstack-pkg-tools/pkgos.make --with python2,systemd<br>
<span>dh: unable to load addon systemd: Can't locate Debian/Debhelper/Sequence/<a href="http://systemd.pm" target="_blank">systemd.pm</a> in @INC (you may need to install the Debian::Debhelper::Sequence::systemd module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 12) line 2.<br>
BEGIN failed--compilation aborted at (eval 12) line 2.<br>
<br>
<br>
</span>If yes, what's your take on fixing this. I could provide a simple clue<br>
for this but I would like you to reproduce this kind of steps and learn<br>
the ways to solve it.<br>
<br></blockquote><div>Firstly, I should say I installed <i>openstack-pkg-tools</i> from Experimental Repository, but there was not /usr/bin/pkgos-pob on system after installing the package. After a little search I found out Thomas has added a link for openstack-package-tools on <b><a href="http://openstack.alioth.debian.org/" target="_blank">http://openstack.alioth.debian.org/</a></b></div><div>So, I did 'wget' on "<a href="http://kilo-jessie.pkgs.mirantis.com/debian/pool/jessie-kilo-backports/main/o/openstack-pkg-tools">http://kilo-jessie.pkgs.mirantis.com/debian/pool/jessie-kilo-backports/main/o/openstack-pkg-tools</a>", then installed the package and its dependencies. </div><div> <br></div><div>The result of running pkgso-bop on Manila in this state was:<br><br><font size="1"><span style="font-family:'arial narrow',sans-serif">mali@buildEnv:/home/mali/manila$ pkgos-bop<br>===> Cleaning-up old builds<br>debian/rules:12: warning: overriding recipe for target 'get-orig-source'<br>/usr/share/openstack-pkg-tools/pkgos.make:76: warning: ignoring old recipe for target 'get-orig-source'<br>git tag -v 2015.1_b2 || true<br>error: tag '2015.1_b2' not found.<br>if [ ! -f ../manila_2015.1~b2.orig.tar.xz ] ; then \<br> git archive --prefix=manila-2015.1~b2/ 2015.1_b2 | xz >../manila_2015.1~b2.orig.tar.xz ; \<br>fi<br>[ ! -e ../build-area ] && mkdir ../build-area || true<br>[ ! -e ../build-area/manila_2015.1~b2.orig.tar.xz ] && cp ../manila_2015.1~b2.orig.tar.xz ../build-area<br><br>===> Building using git-buildpackage<br>dch warning: new version (2015.1~b2-0ubuntu1~bpo80+1) is less than<br>the current version number (2015.1~b2-0ubuntu1).<br>[debian/kilo d6bf29c] Rebuilt by bop.<br> </span>1 file changed, 6 insertions(+)<br>gbp:info: Exporting 'HEAD' to '/home/mali/build-area/manila-tmp'<br><span style="font-family:'arial narrow',sans-serif">gbp:info: Moving '/home/mali/build-area/manila-tmp' to '/home/mali/build-area/manila-2015.1~b2'<br> dpkg-buildpackage -rfakeroot -D -us -uc -i -I<br>dpkg-buildpackage: source package manila<br>dpkg-buildpackage: source version 2015.1~b2-0ubuntu1~bpo80+1<br>dpkg-buildpackage: source distribution UNRELEASED<br>dpkg-buildpackage: source changed by malihe <<a href="mailto:mali@mirror.xamin.ir" target="_blank">mali@mirror.xamin.ir</a>><br> dpkg-source -i -I --before-build manila-2015.1~b2<br>dpkg-buildpackage: host architecture amd64<br>dpkg-checkbuilddeps: Unmet build dependencies: dh-systemd python-all (>= 2.6) alembic (>= 0.7.2) python-amqplib python-anyjson python-babel (>\<br>= 1.3) python-cinderclient python-ddt (>= 1.0.0) python-eventlet (>= 0.16.1) python-glanceclient python-greenlet (>= 0.3.2) python-hacking pyt\<br>hon-hp3parclient python-httplib2 (>= 0.7.5) python-iso8601 python-keystoneclient python-lxml python-manilaclient python-migrate python-mock py\<br>thon-mox python-neutronclient python-nose python-novaclient python-oslo-concurrency (>= 1.4.1) python-oslo-config (>= 1.6.0) python-oslo-conte\<br>xt (>= 0.1.0) python-oslo-db (>= 1.4.1) python-oslo-i18n (>= 1.3.0) python-oslo-messaging (>= 1.4.0) python-oslo-rootwrap (>= 1.3.0) python-os\<br>lo-serialization (>= 1.2.0) python-oslo-utils (>= 1.2.0) python-oslotest python-paramiko python-paste python-pastedeploy python-pbr python-rou\</span><br><span style="font-family:'arial narrow',sans-serif">tes python-sqlalchemy python-stevedore python-swiftclient python-testresources python-testtools python-webob subunit testrepositor<br>dpkg-buildpackage: warning: (Use -d flag to override.)<br>debuild: fatal error at line 1376:<br>dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed<br>gbp:error: 'debuild -i -I' failed: it exited with 29<br>HEAD is now at 73cc358 Add gbp.conf<br>There was an error when bop called git-buildpackage: exiting.</span><br></font><br></div><div>I noticed to 3 part of the result:<span style="color:rgb(255,0,0)"><br></span><ul><li><span style="color:rgb(255,0,0)">debian/rules:12: warning: overriding recipe for target 'get-orig-source' /usr/share/openstack-pkg-tools/pkgos.make:76: warning: ignoring old recipe for target 'get-orig-source' : </span>I checked <font color="#000000">pkgos.make</font> and found "<font color="#000000">get-orig-source</font> recipe". I wondered if it is better to remove 'get-orig-source' from manila/debian/rule or not?</li><li><span style="color:rgb(255,0,0)">error: tag '2015.1_b2' not found. </span>reading pkgos.make, I found out the code finds the last tag of package from last entry of changelog. The last entry on changelog was some s/th like "manila (2015.1~b2-0ubuntu1) " so the script try to find tag 2015.1_b2. <font color="#6aa84f">Therefore, I added an entry to changelog like this "manila (2015.1~rc2-0)" (BTW, It seems the tag 2015.1.0rc2 should be re-tagged by 2015.1_rc2 instead of 2015.1.0_rc2. Do u agree?)</font></li><li><span style="color:rgb(255,0,0)">Unmet build dependencies: </span>so, I installed the proposed packages to resolve dependency issues.</li></ul><p><span style="font-family:'arial narrow',sans-serif"><font size="1">mali@buildEnv:/home/mali/manila$ <font color="#6aa84f">sudo apt-get install</font><span style="color:rgb(0,255,0)"> </span><font color="#000000">dh</font>-systemd python-all alembic python-amqplib python-anyjson python-babel python-cinde\<br>rclient python-ddt python-eventlet python-glanceclient python-greenlet python-hacking python-hp3parclient python-httplib2 python-iso8601 p\<br>ython-keystoneclient python-lxml python-manilaclient python-migrate python-mock python-mox python-neutronclient python-nose python-novaclient \<br>python-oslo-concurrency python-oslo-config python-oslo-context python-oslo-db python-oslo-i18n python-oslo-messaging python-oslo-rootwra\<br>p python-oslo-serialization python-oslo-utils python-oslotest python-paramiko python-paste python-pastedeploy python-pbr python-routes pytho\<br>n-sqlalchemy python-stevedore python-swiftclient python-testresources python-testtools python-webob subunit testrepository<br>[sudo] password for mali:<br>Reading package lists... Done<br>Building dependency tree<br>Reading state information... Done<br>Package python-oslo-config is a virtual package provided by:<br> python-oslo.config-doc 1:1.3.0-2<br> python-oslo.config 1:1.3.0-2<br> You should explicitly select one to install.<br><br>E: Unable to locate package python-manilaclient<br>E: Unable to locate package python-oslo-concurrency<br>E: Package 'python-oslo-config' has no installation candidate<br>E: Unable to locate package python-oslo-context<br>E: Unable to locate package python-oslo-db<br>E: Unable to locate package python-oslo-i18n<br>E: Unable to locate package python-oslo-messaging<br>E: Unable to locate package python-oslo-rootwrap<br>E: Unable to locate package python-oslo-serialization<br>E: Unable to locate package python-oslo-utils</font></span><br></p><font color="#6aa84f"><br></font></div><div><font color="#6aa84f">I removed the packages which were not on the repository, from list of packaged that should be installed, and installed the other packages. Then I </font><span style="font-family:'arial narrow',sans-serif"><font color="#6aa84f">rebuild-ed the package.</font> Result is:</span></div><div><span style="font-family:'arial narrow',sans-serif"><br>===> <font size="1">Building using git-buildpackage<br>dch warning: new version (2015.1~b2-0ubuntu1~bpo80+1) is less than<br>the current version number (2015.1~b2-0ubuntu1).<br>[debian/kilo d6bf29c] Rebuilt by bop.<br> 1 file changed, 6 insertions(+)<br>gbp:info: Exporting 'HEAD' to '/home/mali/build-area/manila-tmp'<br>gbp:info: Moving '/home/mali/build-area/manila-tmp' to '/home/mali/build-area/manila-2015.1~b2'<br> dpkg-buildpackage -rfakeroot -D -us -uc -i -I<br>dpkg-buildpackage: source package manila<br>dpkg-buildpackage: source version 2015.1~b2-0ubuntu1~bpo80+1<br>dpkg-buildpackage: source distribution UNRELEASED<br>dpkg-buildpackage: source changed by malihe <<a href="mailto:mali@mirror.xamin.ir" target="_blank">mali@mirror.xamin.ir</a>><br> dpkg-source -i -I --before-build manila-2015.1~b2<br>dpkg-buildpackage: host architecture amd64<br>dpkg-checkbuilddeps: Unmet build dependencies: alembic (>= 0.7.2) python-ddt (>= 1.0.0) python-eventlet (>= 0.16.1) python-manilaclient python\<br>-oslo-concurrency (>= 1.4.1) python-oslo-config (>= 1.6.0) python-oslo-context (>= 0.1.0) python-oslo-db (>= 1.4.1) python-oslo-i18n (>= 1.3.0\<br>) python-oslo-messaging (>= 1.4.0) python-oslo-rootwrap (>= 1.3.0) python-oslo-serialization (>= 1.2.0) python-oslo-utils (>= 1.2.0)<br>dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting<br>dpkg-buildpackage: warning: (Use -d flag to override.)<br>debuild: fatal error at line 1376:<br>dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed<br>gbp:error: 'debuild -i -I' failed: it exited with 29<br>HEAD is now at 73cc358 Add gbp.conf<br>There was an error when bop called git-buildpackage: exiting.</font></span><br><br></div><div>I don t know how can I resolve the remained dependencies problems.<br></div><div><br></div><div>After doing these steps, I checked '<b><a href="http://openstack.alioth.debian.org/" target="_blank">http://openstack.alioth.debian.org/</a></b>' page again. Thomas has mentioned there that before doing a build for openstack packges, run 'pkgos-setup-sbuild dev USER_NAME'. So, I did it. But I had different problems with this script every time that i tried to run it. </div><div>I guess I should read about sbuild and how it works. I am doing packaging on a debootstrap-ed jessie. It seems sbuild do a debootstrap too. I need to know what does 'setup-sbuild dev USER_NAME' do, exactly, to be able to resolve its issue. </div><div>Or I can just forget setup-sbuild for now, and continue resolving dependencies problems when run 'pkos-bop' in manila dir. </div><div>which one is better to be selected as next step, in ur mind?</div><div><br></div><div><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
Kind regards<br>
<div><div><br>
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"><br>-- <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.7273px;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.7273px;line-height:18px"><br></span></div><div>mali</div></div></div></div></div>
</div></div></div>