On Wed, 23 Apr 2025 21:25:07 +0100, Jon Turney via Cygwin <cygwin@cygwin.com> wrote:
>On 22/04/2025 22:06, Andrew Schulman via Cygwin wrote: >> On Wed, 23 Apr 2025 03:48:19 +0900, ggl329 via Cygwin <cygwin@cygwin.com> >> wrote: >> >>> Hi all, >>> >>> As Jon mentioned in the following mail, something may go wrong in the VM >>> for building packages. >>> https://cygwin.com/pipermail/cygwin/2025-April/257948.html >>> >>> Many files/directories don't have permissions for non-privileged users. >>> These packages are examples I found. Other packages may have same issues. >>> >>> * emacs-common-30.1-1 (subdirs.el is not readable) >>> * libpng16-1.6.47-1 (The impact is minor) >>> * screen-5.0.0-1 (utf8 settings?) > >Thanks for the reminder of this issue, which I'd forgotten about... > >> Thanks for flagging this. I've always understood that setup (or cygport?) >> sets >> suitable permissions on package files, but if that's not true, we maintainers >> will need guidance on how to set them. > >I think this is technically all under the control of the cygport, it's >just that usually 'make install' (or it's equivalent) sets things up >correctly. > >However, there was a breakage in the package builder, which led to some >packages being made wrongly: > >[1] https://cygwin.com/pipermail/cygwin-apps/2025-April/044226.html > >Apologies for the inconvenience. OK. I just verified that when I build a local package tarball with cygport all of the files are world-readable. So I don't seem to be doing anything actively wrong. I'll bump the version number and try scallywag again. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
