Re: libgit2

2025-06-01 Thread Jon Turney via Cygwin-apps
On 01/06/2025 06:17, Jeremy Drake via Cygwin-apps wrote: On Sat, 31 May 2025, Brian Inglis via Cygwin-apps wrote: Note that the previous releases are 0.23.4-2 libgit2_23, 0.24.6-1 libgit2_24, 0.25.1-1 libgit2_25, unfortunately, so 1.9.0-1 would have to be libgit2_109 for rpmvercmp to sort it h

Re: libgit2

2025-06-01 Thread Jon Turney via Cygwin-apps
On 01/06/2025 02:40, Jeremy Drake via Cygwin-apps wrote: On Sat, 31 May 2025, Jon Turney wrote: On 26/05/2025 19:41, Jeremy Drake via Cygwin-apps wrote: On Sun, 25 May 2025, Jon Turney wrote: [...] Should I add a big comment documenting the test failures, or a separate file? No wrong answ

Re: libgit2

2025-05-31 Thread Jeremy Drake via Cygwin-apps
On Sat, 31 May 2025, Brian Inglis via Cygwin-apps wrote: > > Note that the previous releases are 0.23.4-2 libgit2_23, 0.24.6-1 libgit2_24, > 0.25.1-1 libgit2_25, unfortunately, so 1.9.0-1 would have to be libgit2_109 > for rpmvercmp to sort it higher, with appropriate changes elsewhere! Does this

Re: libgit2

2025-05-31 Thread Brian Inglis via Cygwin-apps
On 2025-05-31 19:40, Jeremy Drake via Cygwin-apps wrote: On Sat, 31 May 2025, Jon Turney wrote: On 26/05/2025 19:41, Jeremy Drake via Cygwin-apps wrote: On Sun, 25 May 2025, Jon Turney wrote: Should I add a big comment documenting the test failures, or a separate file? No wrong answers. I gu

Re: libgit2

2025-05-31 Thread Jeremy Drake via Cygwin-apps
On Sat, 31 May 2025, Jon Turney wrote: > On 26/05/2025 19:41, Jeremy Drake via Cygwin-apps wrote: > > On Sun, 25 May 2025, Jon Turney wrote: > > > [...] > > > > Should I add a big comment documenting the test failures, or a separate > > file? > No wrong answers. > > I guess I'd go for a separate f

Re: libgit2

2025-05-31 Thread Jon Turney via Cygwin-apps
On 26/05/2025 19:41, Jeremy Drake via Cygwin-apps wrote: On Sun, 25 May 2025, Jon Turney wrote: [...] Should I add a big comment documenting the test failures, or a separate file? No wrong answers. I guess I'd go for a separate file, but I don't mind. PKG_NAMES="git2 libgit2_1_9 libgit2-d

Re: libgit2

2025-05-26 Thread Jeremy Drake via Cygwin-apps
On Sun, 25 May 2025, Jon Turney wrote: > On 24/05/2025 19:27, Jeremy Drake via Cygwin-apps wrote: > > On Sat, 24 May 2025, ASSI via Cygwin-apps wrote: > > > > > Jeremy Drake via Cygwin-apps writes: > > > > I made a little attempt to update libgit2 based on what MSYS2 did, since > > Thanks for look

Re: libgit2

2025-05-25 Thread Jon Turney via Cygwin-apps
On 24/05/2025 19:27, Jeremy Drake via Cygwin-apps wrote: On Sat, 24 May 2025, ASSI via Cygwin-apps wrote: Jeremy Drake via Cygwin-apps writes: I made a little attempt to update libgit2 based on what MSYS2 did, since Thanks for looking into this. I'm afraid our process for dealing with drive

Re: libgit2

2025-05-25 Thread Carlo B. via Cygwin-apps
Hello everyone, perhaps you will find this interesting: https://github.com/carlo-bramini/packages-cygwin/tree/main/libgit2 Sincerely, Carlo Bramini. Il giorno sab 24 mag 2025 alle ore 20:28 Jeremy Drake via Cygwin-apps ha scritto: > > On Sat, 24 May 2025, ASSI via Cygwin-apps wrote: > > > Jerem

Re: libgit2

2025-05-24 Thread Jeremy Drake via Cygwin-apps
On Sat, 24 May 2025, ASSI via Cygwin-apps wrote: > Jeremy Drake via Cygwin-apps writes: > > I made a little attempt to update libgit2 based on what MSYS2 did, since > > it is apparently needed for cargo (and it seems like it's getting close to > > possible to build cargo for Cygwin). Unfortunatel

Re: libgit2

2025-05-24 Thread ASSI via Cygwin-apps
Jeremy Drake via Cygwin-apps writes: > I made a little attempt to update libgit2 based on what MSYS2 did, since > it is apparently needed for cargo (and it seems like it's getting close to > possible to build cargo for Cygwin). Unfortunately, it failed to build in > scallywag: > https://github.com