[ITCoM] coreutils

[Brian Inglis]

[ISP being sold outsourced miltering to idiots who drop messages, so 
pasting from archives!]

On Wed May 4 11:25:44 GMT 2022, Jon Turney wrote:
> On 2022-05-04 01:49, Corinna Vinschen wrote:
>> On May  2 23:15, Brian Inglis wrote:
>>> Eric Blake no longer seems to have free time available for Cygwin
>>> package upgrades, so I would like to offer to co-maintain
>>> coreutils and provide upgrades as they are now five years old.

> Done. Thanks.

>>> I would like to provide an upgrade to the final version 8 release
>>> 8.32, initially as a TEST release, before working on the latest
>>> release 9.1.
>>> Package sources and archives are available online at:
>>> https://drive.google.com/drive/folders/1z_giKv3QIUbYvSNOiTtMMr644v-wOG_k
>>> and builds in playground from:
>>> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/playground

> Since it didn't already exist, I've created 
> git://cygwin.com/git/cygwin-packages/coreutils.git using a new tool
> I've been working on ('ctm2git') which synthesizes a git history of
> the packaging for a package from the source package history in the
> CTM.
> If that's not wanted, please let me know and I'll remove it.

That's really nice, thanks, I'll drop my two version playground.

>>> https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=playground&status=&user=Brian+Inglis&id=4119
>>> https://github.com/cygwin/scallywag/actions/runs/2239985902
>>> The jobs appear to fail because some checks fail and return 
>>> non-zero status.
>>> Comparing checks between current and proposed releases and across
>>> x86/_64/CI jobs, there appear to be fewer failures despite more
>>> tests.
>>> All feedback is encouraged and gratefully received.

>> Thanks for picking up coreutils, which is not only by name a core
>> package.
>> I think this is at least worthy of a pink hippo ;)

Thanks, hopefully I can be worthy of *IT*!

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]