On Fri, Feb 26, 2021 at 09:42:22PM -0000, Sergio Durigan Junior wrote:
> On Friday, February 26 2021, Utkarsh Gupta wrote:
>
> >> About the PPA: we usually upload using the "~ppa1" suffix, which
> >> helps to "version" the PPA uploads and makes it easier to deal with
> >> multiple uploads of the same package.
> >
> > Eeks, my bad. Thanks for bringing this up. The only bad side I guess is
> > that I need to build it again (with different version string) for PPA,
> > but that's okay, I guess?
>
> No need to build it again. The package has been uploaded already, so
> everything is fine. This is an advice for next time :-).
(I prefer to use ~hirsute1, etc. rather than ~ppa1 for cases where I'm
doing an SRU and want to put the same debian version of a package into
two different releases. It's rare, but happened to me a couple times so
I adopted this approach.)
On Fri, Feb 26, 2021 at 09:42:22PM -0000, Sergio Durigan Junior wrote:
> On Friday, February 26 2021, Utkarsh Gupta wrote:
>
> >> About the PPA: we usually upload using the "~ppa1" suffix, which
> >> helps to "version" the PPA uploads and makes it easier to deal with
> >> multiple uploads of the same package.
> >
> > Eeks, my bad. Thanks for bringing this up. The only bad side I guess is
> > that I need to build it again (with different version string) for PPA,
> > but that's okay, I guess?
>
> No need to build it again. The package has been uploaded already, so
> everything is fine. This is an advice for next time :-).
Here's the workflow I use:
$ ppa_ver=1 name}.$ {codename} ${ppa_ver}
$ git checkout ${branch_name} -b ${branch_
$ dch -l ~${codename} --distribution ${codename} "ppa build for ${codename}"
$ git commit debian/changelog -m "changelog for ppa"
$ debuild -S -i
$ git checkout ${branch_name}
(I prefer to use ~hirsute1, etc. rather than ~ppa1 for cases where I'm
doing an SRU and want to put the same debian version of a package into
two different releases. It's rare, but happened to me a couple times so
I adopted this approach.)
Bryce