Re: Please update bvi to 1.4.2
On 23/12/2023 04:45, Takashi Yano via Cygwin-apps wrote: +Jari Are you still with us ? Jari? Ping. On Thu, 14 Dec 2023 20:50:01 +0900 Takashi Yano via Cygwin-apps wrote: Hi, Current cygwin bvi package is 1.3.2 (release date 2004-02-14). However, the latest stable version is 1.4.2 (release date 2023-03-07). Could maitainer please update the package?
Re: Unmaintained packages in base package set
On 23/12/2023 04:42, Takashi Yano via Cygwin-apps wrote: On Wed, 20 Dec 2023 12:16:05 + Jon Turney via Cygwin-apps wrote: I tweaked the unmaintained packages report [1] a bit so it identifies 'base' and 'direct or indirect base dependencies'. (But you're quite right to point out that the build requirements for a native Cygwin build are also important) [1] https://cygwin.com/packages/reports/unmaintained.html I would like to take over: libass fontconfig fribidi gnutls openjpeg librsvg2 snappy libssh dbus gtk3 orc tdb db libid3tag libmad taglib if no one like to do that, because the packages I maintain use them. all in one shot ? I suggest to start with the smaller beasts one by one or small groups I suspect GTK3 needs a lot of effort I could be interested in librsvg2 for the same reason of you I also wonder what should we do for unchanged packaegs such as: libbs2b libmodplug lame libasyncns avahi musepack if unchanged, are for the time being less urgent and i they do not see critical anyway
Re: Please update bvi to 1.4.2
Jari? Ping. On Thu, 14 Dec 2023 20:50:01 +0900 Takashi Yano via Cygwin-apps wrote: > Hi, > > Current cygwin bvi package is 1.3.2 (release date 2004-02-14). > However, the latest stable version is 1.4.2 (release date 2023-03-07). > > Could maitainer please update the package? -- Takashi Yano
Re: Unmaintained packages in base package set
On Wed, 20 Dec 2023 12:16:05 + Jon Turney via Cygwin-apps wrote: > I tweaked the unmaintained packages report [1] a bit so it identifies > 'base' and 'direct or indirect base dependencies'. > > (But you're quite right to point out that the build requirements for a > native Cygwin build are also important) > > [1] https://cygwin.com/packages/reports/unmaintained.html I would like to take over: libass fontconfig fribidi gnutls openjpeg librsvg2 snappy libssh dbus gtk3 orc tdb db libid3tag libmad taglib if no one like to do that, because the packages I maintain use them. I also wonder what should we do for unchanged packaegs such as: libbs2b libmodplug lame libasyncns avahi musepack -- Takashi Yano
Re: [NMU] inkscape 0.92.3-2 (Test)
This test version of inkscape has been promoted to current. Apologies to JonT who probably has to help this through again. Next time I do this will be after I ITA the thing. Thanks & Regards, ..mark
Re: adopting
> On 22/12/2023 03:49, Marco Atzeri via Cygwin-apps wrote: > > Following the inputs from Jon > > https://cygwin.com/packages/reports/unmaintained.html > > > > I am taking over > > > > $ git diff | grep "^+" > > +++ b/cygwin-pkg-maint > > +alternatives Marco Atzeri > > +bzip2 Marco Atzeri > > +gdbm Marco Atzeri > > +libffi Marco Atzeri > > Very much appreciated. > > More gold stars for you! Yes indeed! https://cygwin.com/goldstars/#MA Especially thanks for taking over alternatives. I looked at that one myself a while back, and in the time I had I couldn't finish untangling where we got it and which parts we were using. The cygport script needs an overhaul I think.
Re: adopting
On 22/12/2023 03:49, Marco Atzeri via Cygwin-apps wrote: Following the inputs from Jon https://cygwin.com/packages/reports/unmaintained.html I am taking over $ git diff | grep "^+" +++ b/cygwin-pkg-maint +alternatives Marco Atzeri +bzip2 Marco Atzeri +gdbm Marco Atzeri +libffi Marco Atzeri Very much appreciated. More gold stars for you!
Re: Unmaintained packages in base package set
On 21/12/2023 04:27, Marco Atzeri via Cygwin-apps wrote: On 20/12/2023 13:16, Jon Turney via Cygwin-apps wrote: On 06/12/2023 17:19, Brian Inglis via Cygwin-apps wrote: On 2023-12-05 06:07, Jon Turney wrote: [...] I tweaked the unmaintained packages report [1] a bit so it identifies 'base' and 'direct or indirect base dependencies'. (But you're quite right to point out that the build requirements for a native Cygwin build are also important) [1] https://cygwin.com/packages/reports/unmaintained.html I could take over alternatives and bzip2. It seems our alternatives is a subset of upstream https://github.com/fedora-sysv/chkconfig I will need to look on the details of the implementation. I think to remember that upstream went for a road not feasible for us, but last I looked was long time ago, and I could remember totally wrong. Yeah, repology seems to think there are a couple of alternative implementations, so the upstream version number in that report (which is retrieved from repology) might not be accurate. Nice to have for alternatives is to manage in some ways also DLLs so for me to remove the Lapack PATH hack. I think the issue there is that we are dependent on the Windows loader to find DLLs when creating a process, and that doesn't understand Cygwin symlinks. Perhaps avoidable if we were to use native symlinks, but I think those are still not widely available enough to make that possible...
