Re: calm: cygwin package report for Brian Inglis
Brian Inglis via Cygwin-apps <[email protected]> Tue, 28 Apr 2026 14:32:26 -0600
| Newsgroups | gmane.os.cygwin.applications |
|---|---|
| Organization | Systematic Software |
| Message-ID | <[email protected]> |
On 2026-04-26 23:23, [email protected] wrote: > INFO: package 'tzdata': errors in license expression: ['Unknown license key(s): LicenseRef-IANA-TZ-Public-Domain'] > ERROR: package 'man-pages-linux' has non-existent keep: version '6.12-2' > ERROR: package 'man-pages-linux' has non-existent keep: version '6.6-1' > ERROR: package 'man-pages-linux' has non-existent keep: version '6.1-1' > ERROR: package 'man-pages-linux' has non-existent keep: version '5.15-1' > ERROR: package 'man-pages-linux' has non-existent keep: version '5.10-1' > ERROR: package 'man-pages-linux-src' has non-existent keep: version '6.12-2' > ERROR: package 'man-pages-linux-src' has non-existent keep: version '6.6-1' > ERROR: package 'man-pages-linux-src' has non-existent keep: version '6.1-1' > ERROR: package 'man-pages-linux-src' has non-existent keep: version '5.15-1' > ERROR: package 'man-pages-linux-src' has non-existent keep: version '5.10-1' > INFO: adding 3 package(s) > INFO: move from Brian Inglis's upload area to release area: > INFO: deploying noarch/release/tzdata/tzdata-2026b-1-noarch.hint > INFO: deploying noarch/release/tzdata/tzdata-2026b-1-noarch.tar.xz > INFO: deploying noarch/release/tzdata/tzdata-2026b-1-src.hint > INFO: deploying noarch/release/tzdata/tzdata-2026b-1-src.tar.xz > INFO: deploying noarch/release/tzdata/tzdata-posix/tzdata-posix-2026b-1-noarch.hint > INFO: deploying noarch/release/tzdata/tzdata-posix/tzdata-posix-2026b-1-noarch.tar.xz > INFO: deploying noarch/release/tzdata/tzdata-right/tzdata-right-2026b-1-noarch.hint > INFO: deploying noarch/release/tzdata/tzdata-right/tzdata-right-2026b-1-noarch.tar.xz > INFO: vaulting 3 old package(s) > INFO: move from release area to vault: > INFO: vaulting noarch/release/tzdata/tzdata-2025b-2-noarch.hint > INFO: vaulting noarch/release/tzdata/tzdata-2025b-2-noarch.tar.xz > INFO: vaulting noarch/release/tzdata/tzdata-2025b-2-src.hint > INFO: vaulting noarch/release/tzdata/tzdata-2025b-2-src.tar.xz > INFO: vaulting noarch/release/tzdata/tzdata-posix/tzdata-posix-2025b-2-noarch.hint > INFO: vaulting noarch/release/tzdata/tzdata-posix/tzdata-posix-2025b-2-noarch.tar.xz > INFO: vaulting noarch/release/tzdata/tzdata-right/tzdata-right-2025b-2-noarch.hint > INFO: vaulting noarch/release/tzdata/tzdata-right/tzdata-right-2025b-2-noarch.tar.xz > SUMMARY: 21 INFO(s), 10 ERROR(s) Hi folks/Jon, Added man-pages-linux override.hint keeps intending to ensure that all current and any LTS release manpages are retained until their extended support expires. But calm or the setup infrastructure objects to references to previously vaulted releases, every time I upload or deploy *any* of my packages. So I ask, is it easy enough for someone with access to move old releases from the vault back into the release area, to be worth while doing so? Or should I upload another override.hint with the keeps reduced to the current release only, extending that only as I upload/deploy packages for future LTS releases? And could we perhaps change calm/infrastructure to only check and complain about a package override.hint when a release of that package is uploaded? I am managing the override.hint in CYGWIN_FILES and manually copying it from $C to .../inst/$PN/ $distdir/$PN/, before upload. I checked whether I could perhaps set PKG_HINTS=override but thought that might suppress auto-generation of $PF-$ARCH.hint? -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut -- Antoine de Saint-Exupéry