Salvo Tomaselli writes:
> I'm also annoyed at the default ci configuration for salsa, because importing
> a
> project makes a CI start to run, then fail. Then I have to one by one point
> the CI file to something else, but the project will forever be "CI failing"
> and
> will be reported for
Johannes Schauer Marin Rodrigues writes:
> I would be *very* interested in more in-depth write-ups of the workflows
> other DDs prefer to use, how they use them and what they think makes
> them better than the alternatives.
> Personally, I start packaging something without git, once I'm satisfie
My standard workflow
I use gbp and dgit
gbp import-orig --pristine-tar --uscan
gbp dch
lintian-brush
dgit --gbp sbuild (build and autopkgtest)
...work until it is ok on my computer
gbp dch
... hand edit the changelog
gbp push
git push (to push the UNRELEASE master branch)
... wait for salsa resu
Quoting Luca Boccassi (2024-05-22 01:45:54)
> On Wed, 22 May 2024 at 00:40, Russ Allbery wrote:
> > For what it's worth, what I do for the packages for which I'm also
> > upstream is that I just add Salsa as another remote and, after I upload
> > a new version of the Debian package, I push to Sals
4 matches
Mail list logo
