[gpgmepy] Release a new version?

[Ingo Klöcker]

On Mittwoch, 4. Juni 2025 08:41:18 Mitteleuropäische Sommerzeit Paul 
Schwabauer via Gnupg-devel wrote:
> There have been many changes to the|gpgmepy|bindings recently. While not
> all issues are resolved yet, it would be helpful to tag a new release.
> This would allow to update the PyPI entry, making it easier for others
> to test the current state and identify any issues in their workflows.
> 
> Some fixes might unintentionally break things for other users, so I
> believe it's a good time to release a version that still allows building
> a working source distribution package.
> 
> I'm not familiar with the release process, so I'd appreciate it if
> someone else could handle the release.

Before we can consider a release you need to make sure that `make distcheck` 
succeeds. Currently, it fails because the following code in all-local
```
	for f in $(EXTRA_DIST); do \
		cp -v $(srcdir)/$$f $(builddir)/; \
	done
```
is run for each run of make and this fails because `make distcheck` makes the 
copied files read-only. After moving these lines to the `copystamp` target this 
problem is solved, but then `make distcheck` fails with
```
ERROR: files left in build directory after distclean:
./README
./MANIFEST.in
./VERSION
./autogen.sh
./autogen.rc
./gpgme.i
./helpers.c
./helpers.h
./private.h
./pyproject.toml
./libtool-patch.sed
./DCO
./HACKING
```

Please look into this. I think adding the files to CLEANFILES should help, but 
you cannot simply add $(EXTRA_DIST) because the simple for-loop that copies 
the files loses the directories (e.g. doc/HACKING -> HACKING). It might be 
better to list the files that actually need to be copied explicitly instead of 
copying all files listed in EXTRA_DIST. Or you need to fix the for-loop so that 
it preserves the directories when copying the files.

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250604/d25ef6d5/attachment.sig>