Re: [gpgmepy] Release a new version?

Ingo Klöcker <[email protected]>
Newsgroups gmane.comp.encryption.gpg.devel
Message-ID <26916990.1r3eYUQgxm@daneel>
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

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCaEAJaQAKCRCxb1mVFkdK
utUgAQDcRFicd21I3vGCMhT0NR+HAxqPedpUlfoT8P8BAIU3TgD/c/C4jCLL7b0n
ZyN3dfQYO/3v0L+QpkFU1HdMgAL2+QU=
=k/Pv
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.