On Tue, Mar 15, 2011 at 07:44:04PM +0100, Alessandro Ghedini wrote: > On Tue, Mar 15, 2011 at 02:20:46PM +0200, Andriy Beregovenko wrote: > > I'm already create repo and now preparing source files to initial commit :) > > If somebody can check it, please do this :) I'll be very grateful :) > > I don't see any 'upstream' nor 'pristine-tar' branches. You should do > 'git push --all' to properly create all the branches that git-buildpackage > made, on the remote repository. Please tell me, where I can read complete manual about basic requirements to repo. > Also, since you have repackaged the orig.tar archive, you have also to > document it properly in the d/copyright (you can use a 'Comment:' field), or > in the d/README.source file, telling what and why you have removed (like > [0]). What do you mean under "orig.tar archive"? Archive from project owner ? It does not exist. There is only svn repo. But ok, I'll document "what and why" I remove or move. > As per Debian Policy you also have to provide a 'get-orig-source' target > in the d/rules file, which builds properly the new tarball (without the > files you decided to remove). This makes easier for future maintainance > (you won't have to repack the tarball manually every time you update the > package). > > Actually, the get-orig-source rule would have been required anyway, since > you are using directly the sources from a SVN repository (I have not much > experience in packaging directly from svn, so I missed this at the > beginning). Have a look at [1] for an example of what you should do. Right now I have sh-script which automate all this routine(i mean create from original sources debian tree), but I do not know how I can include it. And this script is present in original svn-repo: http://trac.rtmpd.com/browser/trunk/builders/packing/debian But I have some doubts about repacking. Currentrly I rebuild all tree for debian project. But original project have entirely different structure. (You can see it here: http://trac.rtmpd.com/browser/trunk) The main reason for this step was "too many unnecessary in builders dir and several not needed dirs", so I create source tree for deb package in "traditional cmake style". So I need advice on this issue.
> Another requirement for the repackaged upstream tarball is to add something > like '~dfsg' to both the source and binary packages version just to make > clear to everyone that you have modified it. The package versions would > look something like: > > 0.0~dfsg+revNNN for the source package > 0.0~dfsg+revNNN-1 for the binary package > > Finally, you don't need to Build-Depend on quilt, since it is implied by > the 3.0 (quilt) source format (was it there also in the previous versions > of the package? I think I missed it...). Ok, I'll do this. Also I remove quilt from deps. > Oh, and you didn't need to remove the lualib sources completely, since > they are DFSG-compliant. You just needed to patch the sources to use the > system-provided one and the build system to not build the local copy. > Since you would have repackaged the orig tarball anyway, IMHO, is not a > grave issue (but I may be wrong). Mostly lualib is needed to build embeded version of crtmpserver(not in debian environment). I do not see any reason to keep lualib sourses in project tree. > Cheers > > [0] > http://git.debian.org/?p=pkg-multimedia/deadbeef.git;a=blob;f=debian/README.source;h=ea7bb6b1dd7368aa7c5cd8813cf8996dc4e8b6ae;hb=HEAD > [1] http://wiki.debian.org/SandroTosi/Svn_get-orig-source > > -- > perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse' > > _______________________________________________ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
