> I think this namespace is something that belongs to the maintainer(s)
> of the package in Debian and you should not have simply created it
> without asking.  I think it can be made into what I would have
> preferred, but I expect that if you do this kind of thing a lot you
> may get annoyed reactions.

I deleted it, it was meant as example, I should have created it into my 
personal namespace, of course
 
> In particular, pushing to
>   https://salsa.debian.org/debian/PACKAGE#master 
> is an operation which cannot be undone without rewinding the branch,
> and rewinding is often undesirable.

got it yes

> I think it is better to work completely within git.  adns upstream is
> git, and it would be better to use that upstream git.
> 
> The workflow I would suggest would be that described here:
>   dgit-maint-merge(7)
> > I created a quick and dirty packaging repo, importing mostly all the
> > old revisions in git (not all, because debsnap started after this
> > package was introduced in Debian)
> 
> Oh, tarball/dsc imports ?  They're a very poor history.  The complete
> package history is available in upstream and Debian git.
> Before your upload, "dgit clone adns" would produce the complete
> upstream + Debian history...
> 

nice to know, I cloned it a few minutes ago


> My preference would be for the source format change to be reverted,
> and for us to go back to the proper (not debsnap-imported) git history
> (dgit push --overwrite will be needed to stitch in the .dsc import).
> 
> And I guess we should either rewind/overwrite the salsa master branch
> from Gianfranco, or stitch in with "git merge -s ours" ?

lets do this way:
1) forget about salsa.d.o (branches are empty deletion ongoing)
2) go with dgit and if you can help me in understanding how to import the new 
release it would be appreciated a lot
3) revert the quilt format change
4) fix this bug:812763 (unless you have a different opinion)

upload once the current one migrates

I did clone with dgit, and it created a debian/sid branch with the new release 
imported...

I think I have to "discard" that branch, go back in master, merge the upstream 
repo and then add my changes, right?

(sorry it is the first time I approach dgit, and I don't even understand why it 
is not mentioned on some VCS fields)

thanks so far

Gianfranco

Reply via email to