[Pkg-sssd-devel] priv-wrapper?

Timo Aaltonen tjaalton at debian.org
Fri Aug 4 10:11:59 BST 2023


Timo Aaltonen kirjoitti 4.8.2023 klo 11.42:
> Simon Josefsson kirjoitti 3.8.2023 klo 22.55:
>> Timo Aaltonen <tjaalton at debian.org> writes:
>>> I had a brief look at priv-wrapper packaging, and noticed it only
>>> keeps the debian/ dir in git? The sssd-team packages have the full
>>> upstream git as the base, with packaging added to the packaging
>>> branch. I prefer those will remain like that :)
>>
>> I usually also do the full git repo with upstream branch for most of the
>> packages I maintain, but for this new package I wanted to see if keeping
>> only debian/ in git worked, as I've had success with that in another
>> package.  What is really the upside of having upstream code in Debian's
>> git?  One downside is that it wastes space, although I don't think that
>> matters a lot these days.  Another downside is that it confuses what is
>> really the "upstream" in case the Debian git-repo's view of what
>> "upstream" is differs from the real upstream.
> 
> How do you pull a new upstream release, download the tarball? I don't 
> like working with upstream tarballs as the source of a new release, git 
> is much nicer. And it allows using snapshots when needed etc.

Okay, now I see that the new uid-wrapper release was imported from a 
tarball? :)

The way I've handled them is to have the upstream git as a remote, then 
pull the new release in the 'upstream' branch, with upstream history. 
That is then merged to the packaging branch.

-- 
t




More information about the Pkg-sssd-devel mailing list