> I'd like to take over the orphaned openldap package. As with the
> previous maintainer, I don't use the server components myself, so I'm
> short on hands-on experience with these.
Gold star awarded! https://cygwin.com/goldstars/#AG
>
> While a number of maintainers keep their cygwin packaging under some
> sort of version control, there is currently no central collection of
> these repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package
> upload, package maintainers can now also push to git
> While a number of maintainers keep their cygwin packaging under some
> sort of version control, there is currently no central collection of
> these repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package
> upload, package maintainers can now also push to git
> Achim Gratz writes:
> > Jon Turney writes:
> >> I recently deployed a calm update which makes this process (and it's
> >> reverse, when a previously noarch package becomes archful) no longer
> >> require any manual steps.
> >>
> >> So, going forward, you may build each version of a package with
> Perl version 5.30.1 was just released. I will have an unexpected
> timeslot available at the beginning of next week that I plan to use to
> update Perl for Cygwin. This of course means all Perl distribution
> packages and any other packages that install into the Perl module
> directories will
> Achim Gratz writes:
> > Perl version 5.30.1 was just released. I will have an unexpected
> > timeslot available at the beginning of next week that I plan to use to
> > update Perl for Cygwin. This of course means all Perl distribution
> > packages and any other packages that install into the
>
> I have done another update of my private Perl repository over the
> weekend. While not all maintainers will immediately be ready with their
> updates due to external circumstances, I'd like to release the new Perl
> version at the end of this week or maybe over the weekend.
>
> In
Name: Andrew Schulman
Package: screen
BEGIN SSH2 PUBLIC KEY
E2VjZHNhLXNoYTItbmlzdHAzODQIbmlzdHAzODQAAABhBIh5WtQRqhzLyhiCds
BhExlJjXY+NeKxt7tp3l4ViEOwGAPmiMp9keikNzVrpBy2poorumkZDCJrCxx3855UxdnV
E51GAO7toxiCMM8BNHX3fnDj6rgydpjCNRStBQUqWQ==
END SSH2 PUBLIC KEY
> On 18/11/2019 23:24, David Rothenberger wrote:
> > Is anyone willing to adopt Subversion?
>
> Please accept this literally priceless gold star in acknowledgment of
> your efforts in maintaining subversion for the past 12 (!) years.
>
> Thanks for maintaining this package.
Gold star awarded!
> > OK, works. Can lftp or cygport be configured so that lftp does not ask
> > for a password? Or to use sftp instead?
>
> I don't know of any configuration for lftp to turn off that behaviour
> (which is arguably a defect in lftp), but that's probably something you
> could investigate for
> On Mar 19 23:47, Yaakov Selkowitz wrote:
> > Hello Cygwin package maintainers,
> > To that end, in the best interest of the community, please consider my
> > packages up for adoption.
> > Yaakov
>
> There's no number of goldstars or plush hippos which would do justice to
> what you did
cygport has automated a lot of the work of building and maintaining
packages for Cygwin. But one area where it doesn't help yet is in managing
the available releases of a package. For me as the maintainer of a dozen or
so packages, there are routine tasks that I still find to be painful:
*
Please create a new package socat2, with me as the maintainer. It seems
that socat versions 1 and 2 are long-term different, and creating a
separate socat2 package will allow me to stop treating socat 2.x releases
as perpetually in test.
Thanks,
Andrew
Please add me as the maintainer for two new Unison packages:
unison2.48+4.04.2
unison2.48+4.08.1
If you want to know why we need this, please see the thread starting at [1]
(and continuing at [2], thanks pipermail). I'm going to release them
initially as test packages, to see if they have the
> I'm very keen on reducing the maintainer workload by increasing the
> automation available to them.
Good.
> However, I'm not so sure about the approach proposed, which perpetuates
> the 'create strange files which have a special meaning when uploaded
> causing something non-obvious to
> On Apr 1 16:58, Yaakov Selkowitz wrote:
> > On Tue, 2020-03-24 at 16:19 -0400, Andrew Schulman wrote:
> > > > On Mar 19 23:47, Yaakov Selkowitz wrote:
> > > > > Hello Cygwin package maintainers,
> > >
> > > > > To that end, in the best interest of the community, please consider my
> > > > >
> Hello,
>
> [ITP] A new package proposal: no-more-secrets
>
> - no-more-secrets
>
>
>
> SUMMARY: Recreation of the decrypting text effect from the 1992 movie Sneakers
> HOMEPAGE: https://github.com/bartobri/no-more-secrets
> SRC_URL:
> The Perl 5.32 test repository is now updated with the stage 3 bootstrap
> packages at:
>
> root=http://cygwin.stromeko.net/
> $root/perl-5.32
Not sure I understand. In setup I entered
http://cygwin.stromeko.net/perl-5.32
as a mirror URL, but setup complains:
Mirror error: Setup.ini
> Achim Gratz writes:
> > The files are on the libargp branch of the playground repository:
> > https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/libargp
>
> I've updated the branch with a bugfix. Some parts had been refactored
> out of argp.h
> Andrew Schulman via Cygwin-apps writes:
> > Thank you. stow is ready now. And no, I hadn't seen the packaging error -
> > fixed in the next release.
>
> You mean the one that you've just readied or another one? I'd prefer if
> it was fixed in coincidence with the upd
> On 2/4/2021 9:04 AM, Ken Brown via Cygwin-apps wrote:
> > On 2/4/2021 7:10 AM, Andrew Schulman via Cygwin-apps wrote:
> >>> The Perl 5.32 test repository is now updated with the stage 3 bootstrap
> >>> packages at:
> >>>
> >>&g
I want to maintain pv, since it's being orphaned. I lightly updated the old
cygport script, and checked that the latest version, 1.6.6, builds OOTB.
Will upload the new release as soon as it's approved. Thanks, Andrew
> On Tue, 2021-01-05 at 15:06 +0100, Achim Gratz wrote:
> > Yaakov Selkowitz via Cygwin-apps writes:
> > > In fact, there are probably a bunch of other http: which could be
> > > converted to https: at this point. I would suggest anyone who does
> > > that (in separate commit(s)) should get a
> On Thu, 08 Apr 2021 19:26:44 -0400, Andrew Schulman via Cygwin-apps
> > Awarded!
> >
> > https://cygwin.com/goldstars/#LM
> > https://cygwin.com/goldstars/#AG
>
> Thank you!
>
> Lem
BTW I wanted to name you #LL in the Gold stars page, but that name is
> Andrew Schulman via Cygwin-apps writes:
> > Packaging error will be fixed in the forthcoming stow-2.3.1+5.32-1, which
> > will be compatible with perl-5.32. So same release as the perl update.
>
> Please let us know when you have uploaded the package. Thanks.
Uploaded stow-2.3.1+5.32-1.
> I ran my script to update your key, but it didn't seem to do anything,
> which confused me, until I noticed this appears to be the same as your
> current key [1].
>
> [1] https://cygwin.com/pipermail/cygwin-apps/2020-February/039822.html
Doh. Thanks.
Name: Andrew Schulman
BEGIN SSH2 PUBLIC KEY
Comment: "384-bit ECDSA, created by Andrew Schulman"
E2VjZHNhLXNoYTItbmlzdHAzODQIbmlzdHAzODQAAABhBIh5WtQRqhzLyhiCds
BhExlJjXY+NeKxt7tp3l4ViEOwGAPmiMp9keikNzVrpBy2poorumkZDCJrCxx3855UxdnV
E51GAO7toxiCMM8BNHX3fnDj6rgydpjCNRStBQUqWQ==
Please add me as maintainer of two new unison packages:
unison2.51+4.04.2
unison2.51+4.10.0
These will obsolete the current unison2.51 package.
Thanks, Andrew
> On 22.12.2021 17:21, Andrew Schulman via Cygwin-apps wrote:
> > Please add me as maintainer of two new unison packages:
> >
> > unison2.51+4.04.2
> > unison2.51+4.10.0
> >
> > These will obsolete the current unison2.51 package.
> >
> &
> On 22.12.2021 17:21, Andrew Schulman via Cygwin-apps wrote:
> > Please add me as maintainer of two new unison packages:
> >
> > unison2.51+4.04.2
> > unison2.51+4.10.0
> >
> > These will obsolete the current unison2.51 package.
> >
> > Thanks
> > Since I marked unison2.51+4.04.2 as obsoletes: unison2.51, it seems that
> > unison2.51 now needs to be removed as a separate package? calm says:
> >
> > ERROR: package 'unison2.51' is at paths unison2.51 and
> > unison2.51+4.10.0/unison2.51
>
> this says that unison2.51+4.10.0 obsolets
>
> We should get rid of dependencies to the obsolete OpensSSL 1.0 library
> that is no longer maintained upstream and has several critical bugs.
>
> Current and previous versions of the following packages depend on the
> outdated libopenssl100 (a lot of these have many packages depending on
>
After all this time I feel that I should know the answer to this, but here
goes.
I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
leaving fish-3.3.1-1 as the previous release.
What's the best way to do this? Should I create override.hint, with
keep: 3.3.1-1
> After all this time I feel that I should know the answer to this, but here
> goes.
>
> I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
> leaving fish-3.3.1-1 as the previous release.
>
> What's the best way to do this? Should I create override.hint, with
>
> keep:
> On 11/04/2022 14:02, Andrew Schulman via Cygwin-apps wrote:
> > After all this time I feel that I should know the answer to this, but here
> > goes.
> >
> > I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
> > leaving fis
I want to maintain a new Unison package, this time called - ready? -
unison.
Starting with the current release, version 2.52, the Unison project has
solved the version incompability problems that caused us to have to
maintain multiple packages, like unison2.49, unison2.51+4.04.2, and so on.
> I'd like to adopt the package wavpack.
> Thanks in advance.
3 gold stars! For limbsamplerate, soxr, and wavpack.
https://cygwin.com/goldstars/#TY
https://github.com/jqlang/jq/blob/master/COPYING
Most parts of this are "as is, do what you want but preserve this notice." That
has the spirit of the Beerware license[1], but it's not exactly that. I'm sure
there must be another license on the SPDX list[2] that fits better, but I can't
tell
> Hi, Andrew et al.,
>
> > https://github.com/jqlang/jq/blob/master/COPYING
>
> Debian uses the following in its /usr/share/doc/jq/copyright file:
>
> License: MIT
> License: CC-BY-3.0
> License: Expat
> License: GPL-2.0+
>
> That might help...
Thank you, and Achim!
And sorry for
I'd like to adopt the jq package. It's currently orphaned from Yaakov. I have an
updated build script ready to push up for the current release (1.6-1), and a new
release (1.7) is expected soon. Andrew
> > I've given you the adopted packages: libsndfile, mpg123, opus,
> > opus-tools, opusfile, SDL2. I'll look at the rest later.
>
> Please accept these literally priceless gold stars for adopting these
> packages.
Awarded! https://cygwin.com/goldstars/#TY
>
> Am 11.11.2022 um 17:16 schrieb Jon Turney:
> > On 11/11/2022 15:50, Jon Turney wrote:
> >>
> >> As has previously been announced, Cygwin is dropping support for x86
> >> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit)
> >> Windows, and the forthcoming Cygwin 3.4 will be
> On 11/11/2022 16:16, Jon Turney wrote:
> > On 11/11/2022 15:50, Jon Turney wrote:
> >>
> >> As has previously been announced, Cygwin is dropping support for x86
> >> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit)
> >> Windows, and the forthcoming Cygwin 3.4 will be released
In the next release of fish, I'm going to split the package into fish and
fish-doc. I can't remember if someone needs to add me to the maintainers list
for the new fish-doc package, or if that happens automatically since they're
created from the same source package.
If someone does need to add me
> On 2023-04-10 07:17, Andrew Schulman via Cygwin-apps wrote:
> > autossh comes with the license shown below. Is there an SPDX license
> > identifier
> > (https://spdx.org/licenses/) that I can associate with this? It looks most
> > like
> > public domain to me
I'm trying to rebuild pinfo 0.6.13. That's the current version in Cygwin, so I
know I was able to build it successfully a couple of years ago. But now when I
try, the build fails with
error: possibly undefined macro: AM_INTL_SUBDIR
I'm afraid my grasp of autotools is too weak for me to know
> On Apr 11 09:21, Andrew Schulman via Cygwin-apps wrote:
> > I'm trying to rebuild pinfo 0.6.13. That's the current version in Cygwin,
> > so I
> > know I was able to build it successfully a couple of years ago. But now
> > when I
> > try, the build fai
autossh comes with the license shown below. Is there an SPDX license identifier
(https://spdx.org/licenses/) that I can associate with this? It looks most like
public domain to me. Thanks, Andrew
autossh is copyright (c) Carson Harding, 2005.
All rights reserved.
Redistribution and use in source
> Recently I noticed that `cygport finish` has become really slow on some of my
> package source trees. After I run for example
>
> cygport libargp.cygport finish
>
> it waits for about 5 minutes without any message to the console, before the
> first "Removing work directory" message appears.
>
Recently I noticed that `cygport finish` has become really slow on some of my
package source trees. After I run for example
cygport libargp.cygport finish
it waits for about 5 minutes without any message to the console, before the
first "Removing work directory" message appears.
pstree shows
> On 06/07/2023 18:36, Andrew Schulman via Cygwin-apps wrote:
> >> Recently I noticed that `cygport finish` has become really slow on some of
> >> my
> >> package source trees. After I run for example
> >>
> >> cygport libargp.cygport finish
&g
> On 11.05.2023 15:57, Andrew Schulman via Cygwin-apps wrote:
> >> Entrusted with these strange superpowers, the following god-like beings
> >> walk unknown amongst us:
> >>
> >> Achim Gratz
> >> Corinna Vinschen
> >> Ken Brown
> &
> On 16/07/2023 20:32, ASSI via Cygwin-apps wrote:
> > Jon Turney via Cygwin-apps writes:
> >> The warning (error if RESTRICT=case_insensitive) should occur for all
> >> commands, not just prep.
> >
> > OK.
> >
> >> How about the attached.
> >
> > Looks promising.
>
> Ok. I made a cygport
> On 19/04/2023 23:42, Daisuke Fujimura via Cygwin-apps wrote:
> > Hello,
> >
> >
> >
> > Cygportfile:
> > -
> > https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/ruby
> >
> > Packages, logs:
> > -
> Entrusted with these strange superpowers, the following god-like beings
> walk unknown amongst us:
>
> Achim Gratz
> Corinna Vinschen
> Ken Brown
> Marco Atzeri
Hippos! https://cygwin.com/goldstars/
> 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
I need to update my maintainer email address, to
andrex_dot_e_dot_schulman_at_gmail_dot_com. I don't see my current address
stored anywhere in the cygwin-htdocs, so I guess it's stored somewhere else,
since calm sends me emails there. Thanks, Andrew
> On 03/01/2024 06:25, Takashi Yano via Cygwin-apps wrote:
> > On Wed, 3 Jan 2024 14:14:12 +0900
> > Takashi Yano via Cygwin-apps wrote:
> >> I'd like to adopt the pocl package.
> >>
> >> - Update to latest upstream release.
>
> $ git diff |grep "^+"
> +++ b/cygwin-pkg-maint
> +pocl
> On 12/01/2024 14:43, Andrew Schulman via Cygwin-apps wrote:
> > I need to update my maintainer email address, to
> > andrex_dot_e_dot_schulman_at_gmail_dot_com. I don't see my current address
> > stored anywhere in the cygwin-htdocs, so I guess it's stored somewhere else,
&g
59 matches
Mail list logo
