Re: Another orphaned game: shisen.app
On 17/12/2007, Barry deFreese <firstname.lastname@example.org> wrote:
> Eddy Petrișor wrote:
> > On 14/12/2007, Barry deFreese <email@example.com> wrote:
> >> Jon Dowland wrote:
> >>> On Thu, Dec 13, 2007 at 10:38:16PM +0100, Vincent Fourmond wrote:
> >>>> Did you use svn-inject to import the packages ? Please do use it, as
> >>>> it takes care of many small details you definitely don't want to do
> >>>> yourself.
> >>> Also remember the -2 flag for repo layout type 2 (I'm pleased to see
> >>> this is finally supported)
> >> I didn't inject shisen.app or xbattle, I did them manually. :-( Is
> >> there any way to fix them up after the fact?
> > Yes, but is not documented. Your comments are welcome to the
> > svn-buildpackage corresponding bug:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346000
> > Adding them will help me document the procedure so is possible to
> > reproduce manually svn-bp's behaviour.
> Here is what I have been doing. I'll add them to the bug if they seem
Please mention also the scenario for which your instructions fit when
adding that info to the BR (i.e. layout 2 repo, upstream source not
> Make sure there is a tags dir:
> svn mkdir svn+ssh://svn.debian.org/svn/pkg-games/packages/tags/<package>
> Make sure you have uploaded the orig.tar.gz:
> scp <package_name_and_version>.orig.tar.gz \
This is somewhat DGT specific, but I intent to add some support for
this in the future.
> Set the properties:
> svn propset mergeWithUpstream 1 debian
> svn propset svn-bp:origUrl
> svn propset svn-bp:tagsUrl
> "svn+ssh://svn.debian.org/svn/pkg-games/packages/tags/<package>" debian
> The last part is the worst. If the package has source modified outside
> of the Debian dir. I personally have been moving those to quilt patches
> (after Vincent pointed them out to me) as I think that is the best way
> to handle them. Others may have a different opinion. So I don't really
> know how to handle them properly if you want to just leave them in the diff.
If they are left in the diff, you need to add the entire patched
file(s) to the repo.
for a diff like:
Besides the entire debian/ directory, you will need to commit also the
*patched* versions of the files foo/src/src1.c, foo/src/src2.c and
I am not 100% sure if using later svn-upgrade would take care of the
files to be updated[*].
[*] although it might have bugs or might be dumb enough not o touch
them; I haven't actually worked enough on that script to know its
indsides, but I remember Jon having issues during DebConf with a
source after a supposed upgrade; I am not sure he used svn-upgrade
when he got into that situation, but I'm sure he can clear that up.
"Imagination is more important than knowledge" A.Einstein