Hi Simon,

Thanks for your reply, much appreciated!

On Sat, Sep 07, 2024 at 07:20:14PM +0100, Simon McVittie wrote:
> On Sat, 07 Sep 2024 at 12:13:20 +0200, Salvatore Bonaccorso wrote:
> > We discussed this, if we should release the update for ikiwiki-hosting
> > (real impact) and fcgiwrap (only autopkgtests) via a corresponding
> > update or a proposed-update is enough. We prpoose the later, and let
> > it go through the upcoming point release.
> 
> Thanks for preparing this. The changes seem good to me, unless someone with
> more git knowledge knows a better way to achieve this (see #1076750).

At least this matches what we currently have in unstable, so I
proceeded with the actual upload afer your above "looks good to me"
(and pushed it as well to the git repo, but let me know if I did
something you do not like that way in the repo).

> > the proposed debdiff [...] still
> > contains the debian/.gitignore removal
> 
> I assume you're using debuild -I, which excludes various files including
> .gitignore, resulting in a diff between the git tree on Salsa and the
> source package in the archive (and therefore also the dgit view).
> 
> I normally build source packages with just -I.git (plus some other
> specific patterns like vim swapfiles, but not -I) to avoid having
> debian/**/.gitignore disappear, so the 0.20220716-2 currently in bookworm
> will have been built like that. But that isn't a functional change and
> shouldn't have any effect on the built binaries.

Yes the final upload done now was done via dpkg-buildpackage -S -d -nc
-I.git now to have the .gitignore files still included as previously.

(fcgiwrap has been uploaded as well, but that is for the other bug).

That means I think we now could release the git update through
security, knowning at least the fallouts for handle for the next point
release.

Thanks again a lot for your time!

Regards,
Salvatore

Reply via email to