[PKG-Openstack-devel] [MoM] Packaging manila

[Malihe Asemani]

Hey All,

Thank you Thomas and Andreas. The comments were very helpful.
Andreas, I renamed manila_Mali to manila on server. I tried to create a
list of task based on your and Thomas's comments. They are:

   1.  Merge new upstream version to current git
   2. rip-off Ubuntu part of changelog, and create just one entry as first
   debian members work on Manila
   3. Update Uploades field in Control file
   4. Remove Orig Recipe from rules file
   5. add OSLO_PACKAGE_VERSION to rule file
   6. Move python-pbr from Build-Depends-Indep to Build-Depends in control
   file
   7. adapt watch file in such a way to be compatible with
   tag-base-packaging
   8. Use pkgos-reqsdiff to check and correct Manila dependencies

Until now, I have done the first 7 steps, and pushed the results on git.

The current result of pkgos-bop on Manila is attached. An error related to
pyversions is still remained:
"...
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
running clean
'build/lib.linux-x86_64-2.7' does not exist -- can't clean it ...."

And another noticeable part is:
"...
E: Core build dependencies not satisfied; skipping
gbp:error: 'sbuild -v --no-apt-update' failed: it exited with 3
..."

I guess I should do step 8 (I mean pkgos-reqsdiff), to be able to resolve
this dependency issue. What do you think?

BTW, cinder watch file reads from https://github.com/openstack/*nova*/tags.
I think it should be changed to https://github.com/openstack/*cinder*/tags


Warmest regards
Mali

On Sun, May 3, 2015 at 9:53 PM, Andreas Tille <andreas at an3as.eu> wrote:

> Hi Thomas,
>
> On Sun, May 03, 2015 at 10:03:15AM +0200, Thomas Goirand wrote:
> > > thanks for helping out with the MoM project.
> >
> > My pleasure!
>
> :-)
>
> > > OK.  However, I think the debian/watch file should be fixed anyway to
> > > report the latest upstream version.  Verifying this by using
> > >
> > >    uscan --verbose --report
> >
> > Yes. You can take the watch file from nova or cinder as example, it
> handles both beta and rc releases.
> >
> > > So the question I now have is:  How to pull this from upstream.  My
> > > repository now looks like:
> > >
> > > $ cat .git/config
> > > [core]
> > >         repositoryformatversion = 0
> > >         filemode = true
> > >         bare = false
> > >         logallrefupdates = true
> > > [remote "origin"]
> > >         url = ssh://git.debian.org/git/openstack/manila.git
> > >         fetch = +refs/heads/*:refs/remotes/origin/*
> > > [branch "debian/kilo"]
> > >         remote = origin
> > >         merge = refs/heads/debian/kilo
> >
> > Simply do:
> > ./debian/rules fetch-upstream-remote
> > git merge -X theirs 2015.1.0
> > [ edit debian/changelog and commit the new version ]
> > git push
>
> OK, sounds sensible.  Malihe, I think its time we start working on one
> common Git repository.  I have deleted /git/openstack/manila.git and I
> think it is the best idea if you rename manila_Mali.git to manila.git.
>
> Please update this as suggested above to the latest upstream releases
> and commit your work.  Then we should start with the real packaging
> stuff.
>
> Kind regards
>
>       Andreas.
>
> --
> http://fam-tille.de
>
> _______________________________________________
> Openstack-devel mailing list
> Openstack-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/openstack-devel
>



-- 
------------
you can't start the next chapter if you keep re-reading the last one

mali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20150507/3205d4bc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pkgos-bop-result-2
Type: application/octet-stream
Size: 4851 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20150507/3205d4bc/attachment-0001.obj>