> 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
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 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'd like to adopt the package wavpack.
> Thanks in advance.
3 gold stars! For limbsamplerate, soxr, and wavpack.
https://cygwin.com/goldstars/#TY
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
> 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
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
> 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 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
> 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 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:
> > -
> 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
> &
> 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 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
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 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
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
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
> > 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
> 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
>
> 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
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.
> 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
> 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:
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
> > 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
> 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
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
>
> 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
>
> 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
E51GAO7toxiCMM8BNHX3fnDj6rgydpjC
> 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
> 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
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
> 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.
> 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
> 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
> 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:
> 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
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
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 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
> 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 en
> > 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
Name: Andrew Schulman
Package: screen
BEGIN SSH2 PUBLIC KEY
E2VjZHNhLXNoYTItbmlzdHAzODQIbmlzdHAzODQAAABhBIh5WtQRqhzLyhiCds
BhExlJjXY+NeKxt7tp3l4ViEOwGAPmiMp9keikNzVrpBy2poorumkZDCJrCxx3855UxdnV
E51GAO7toxiCMM8BNHX3fnDj6rgydpjCNRStBQUqWQ==
END SSH2 PUBLIC KEY
>
> 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
> 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!
> 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
> 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
>
> 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
> 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
> 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
> On 12/04/2019 15:26, Andrew Schulman wrote:
> > calm sent me the below after I uploaded screen-4.6.2-3. Do I need to do
> > anything about the warnings? I'm not sure what they're about. I don't think
> > I have any packages that depend on libgfortran5 or libgnat8, bu
calm sent me the below after I uploaded screen-4.6.2-3. Do I need to do
anything about the warnings? I'm not sure what they're about. I don't think
I have any packages that depend on libgfortran5 or libgnat8, but maybe I'm
wrong.
Thanks,
Andrew
WARNING: package 'libgfortran5' doesn't have a curr
> Am 12.11.2018 um 23:51 schrieb Ken Brown:
> > My cygport file and the one for the current release are attached. There's
> > no
> > test suite, but I tested it by building asymptote.
> >
> > Ken
> >
>
> updated the cygwin-pkg-maint
Gold star awarded! https://cygwin.com/goldstars/#KB
> Am 11.11.2018 um 22:25 schrieb Ken Brown:
> > Although there's been no new upstream release since the last Cygwin release,
> > there have been some bug fixes (including one that I just found to fix a
> > crash
> > on 32-bit Cygwin), which warrant a new release.
> >
> > I'm attaching my cygport
> Am 11.11.2018 um 23:38 schrieb Ken Brown:
> > There's no need for a new release at the moment, but I'm attaching the
> > cygport
> > file I would use if there were. It differs in only very minor ways from the
> > current cygport file (also attached).
> >
> > I've tested that the upstream git
> Am 11.11.2018 um 23:38 schrieb Ken Brown:
> > There's no need for a new release at the moment, but I'm attaching the
> > cygport
> > file I would use if there were. It differs in only very minor ways from the
> > current cygport file (also attached).
> >
> > I've tested that the upstream git
Name: Andrew Schulman
Package: screen
BEGIN SSH2 PUBLIC KEY
Comment: "2048-bit RSA, converted from OpenSSH"
B3NzaC1yc2EDAQABAAABAQDJHwg85y9fnaw7qYzRF32vmwY2GW5Bwcgc/hOxsG
AWrpQJ9wsfFK5yHUmQnTmyyuttXhrOjrGsrUK1vtv59bFdJwsbh/i3jwnajBConXZwo3lU
rMBnqn5rXTiG/TM4zX18
> Am 13.10.2018 um 20:49 schrieb Jon Turney:
> >
> > A new setup release candidate is available at:
> >
> > https://cygwin.com/setup/setup-2.894.x86_64.exe (64 bit version)
> > https://cygwin.com/setup/setup-2.894.x86.exe (32 bit version)
> >
> > Please test and report any problems
> It seems that the advice I gave was wrong, and that '-override.hint'
> works, but an empty 'override.hint' is (silently) considered invalid
> (because it uses the same parser as other .hint files, which aren't
> expected to be empty)
>
> I've added some output so this failure isn't hidden,
> On 29/08/2018 19:16, Andrew Schulman wrote:
> > I just uploaded lftp-4.8.4-1 for x86_64, and got these error notices back
> > from calm:
> >
> > ERROR: package 'lftp' version '4.8.4-1' is most recent non-test version,
> > but version '4.7.8-2' is curr:
&
> I think all of this isn't needed any more, so you can add an empty
> override.hint to your upload to supersede that.
Got it. Thanks.
' is curr:
ERROR: error while validating merged x86_64 packages for Andrew Schulman
SUMMARY: 3 ERROR(s)
I guess this is because we pinned 4.7.8-2 as curr: some time last year,
when I had to forcibly roll back from 4.8.0-1. Is that right? Is this
something you can fix, or do I need to do something
orpie recently changed to an opam-based build system. So I want to use opam
to update it for Cygwin, but I've never used opam before and I have some
questions about how to use it.
The orpie build instructions say just to run "opam install orpie". When I
do that, opam complains that I haven't set
> I would like to take over the maintenance of rsh package, which is
> currently orphaned.
3 gold stars, for inetutils, rsh, and tcp_wrappers!
https://cygwin.com/goldstars/#TY
Andrew
> > I've been a Cygwin package maintainer for nearly six years, and I've
> > learned a lot in my time here. Special thanks to Corinna for leading the
> > programme, and to Yaakov for somehow managing to maintain a ridiculous
> > number of packages. Cygwin has made a big difference to so many
> On 28/06/2018 18:09, Andrew Schulman wrote:
> > Scratching my head. This used to work. Now I get an inscrutable error
> > message:
> >
> >$ git remote -v
> >origin ssh://sourceware.org/git/cygwin-htdocs.git (fetch)
> >origin ssh://sou
Scratching my head. This used to work. Now I get an inscrutable error message:
$ git remote -v
originssh://sourceware.org/git/cygwin-htdocs.git (fetch)
originssh://sourceware.org/git/cygwin-htdocs.git (push)
$ git fetch
FATAL: R any git/cygwin-htdocs Andrew_Schulman
> Andrew Schulman writes:
> > When I run setup-x86_64.exe or setup-x86.exe with --prune-install as shown
> > below, it crashes. An error dialog pops up saying "setup-x86.exe has
> > stopped working". No other debug information appears on the console - the
&
When I run setup-x86_64.exe or setup-x86.exe with --prune-install as shown
below, it crashes. An error dialog pops up saying "setup-x86.exe has
stopped working". No other debug information appears on the console - the
whole session is shown below.
When I run the same command without
> > configure.ac:9: error: version mismatch. This is Automake 1.15.1,
> > configure.ac:9: but the definition used by this AM_INIT_AUTOMAKE
> > configure.ac:9: comes from Automake 1.15. You should recreate
> > configure.ac:9: aclocal.m4 with aclocal and run automake again.
>
> you've patched
Prior to stunnel 5.42, I could build stunnel in Cygport with no src_compile
function, just
CYGCONF=--disable-fips
Beginning with stunnel 5.42, the build fails with errors about "possibly
undefined macro" AC_MSG_NOTICE and AC_DEFINE:
$ cygport stunnel.cygport build
>>> Compiling
I'm going to package unison2.51 for Cygwin. It's a new member of the Unison
family - same as the other unison* packages, but it gets its own new
package since it's incompatible with the other versions.
So please add unison2.51 to the package list with me as the maintainer.
Thanks,
Andrew
> On 2017-11-27 10:04, Ken Brown wrote:
> > My cygport file is attached.
>
> GTG; package is yours now. Thanks!
Gold star awarded! https://cygwin.com/goldstars/#KB
> On 15/11/2017 17:30, Ken Brown wrote:
> > My cygport file and other files needed for reproducing the build are
> > attached.
>
> I added this to your uploads,
Gold star awarded! https://cygwin.com/goldstars/#KB
> On 30/10/2017 19:43, Ken Brown wrote:
> > My cygport files and patch are attached. The two fonts packages
> > don't need updating, but their cygport files had to be updated, so I'm
> > attaching them for future reference.
> >
> > In the case of ghostscript, the current version is 9.22, but it
> On 09/10/2017 17:19, Ken Brown wrote:
> > My cygport file and patches are attached. Note that there has been a
> > change in the build system since the last release. It now uses cmake
> > and libQt. For comparison, I'm also attaching the cygport file from the
> > previous release.
>
>
> Corinna Vinschen writes:
> >> Any comments?
> >
> > ship it?
>
> An option I hadn't considered so far. :-)
>
>
> Regards,
> Achim.
Gold stars awarded! https://cygwin.com/goldstars/#AG
> On 11/10/2017 18:35, Ken Brown wrote:
> > On 10/11/2017 1:14 PM, Andrew Schulman wrote:
> >> As I described elsewhere here, I'm trying to dump lftp 4.8.0-1, which is
> >> partly broken, and promote 4.7.8-1 to current. I thought I could do
> >>
' is most recent non-test version,
but version '4.7.8-1' is curr:
ERROR: package 'lftp-debuginfo' version '4.8.0-1' is most recent non-test
version, but version '4.7.8-1' is curr:
ERROR: error while validating merged x86 packages for Andrew Schulman
So I guess I need a manual intervention. Can someone
> Andrew Schulman writes:
> > Ooh, how about this:
> >
> > cygport lftp.cygport all
> > cygport lftp.cygport override curr=4.7.7-1 test=4.7.8-1
> > cygport lftp.cygport up
> >
> > That would create override.hint and upload it with the package, le
> On 10/5/2017 10:23 AM, Andrew Schulman wrote:
> > Sometimes more complicated situations come up. We have one with lftp right
> > now:
> >
> > prev: 4.7.7-1
> > curr: 4.8.0-1
> > test: 4.7.8-1
> >
> > This happened because 4.8.0-1 turns out to
> On 03/10/2017 21:01, Andrew Schulman wrote:
> >> This patch (originally by Achim Gratz) adds a mechanism for generating
> >> packages marked as 'test' as described in [1].
> >>
> >> I'm not committed to any of the details, but I would like to get
> &
> On 03/10/2017 17:00, Andrew Schulman wrote:
> >> Unfortunately, we haven't heard from Dr. Volker Zell in quite some time,
> >> and a number of his packages are in need of updates or rebuilds. I have
> >> marked them ORPHANED in the maintainer list. ITAs welcome.
> Somewhat clearer as to it's purposes, and pluralized for consistency with
> REQUIRES.
Yes! Thank you!
I'd like to adopt this from Dr Volker Zell. I've tested the cygport script
with the latest version, 6.4.2, and it works fine, so I have a new package
ready to upload. Andrew
> Unfortunately, we haven't heard from Dr. Volker Zell in quite some time,
> and a number of his packages are in need of updates or rebuilds. I have
> marked them ORPHANED in the maintainer list. ITAs welcome.
I use multitail so I can adopt it if the package is in good shape. I'll
take a look.
> > Achim, thanks for the testcase. Ken, thanks for bisecting. You're
> > my hero!
> >
> > I reverted the patch and created new developer snapshots.
>
> I forgot the gold star. Thanks again, Ken!
Awarded!
https://cygwin.com/goldstars/#AG
https://cygwin.com/goldstars/#KB
> On 01/07/2017 12:31, Andrew Schulman wrote:
> >> On Apr 17 12:34, Jon Turney wrote:
> >>>
> >>> I recently deployed an update to calm which should causes it to run
> >>> on-demand after a maintainer SFTP upload.
> >>>
> >>>
> On Apr 17 12:34, Jon Turney wrote:
> >
> > I recently deployed an update to calm which should causes it to run
> > on-demand after a maintainer SFTP upload.
> >
> > Hopefully this reduces the inconvenience of having to wait till the next
> > scheduled run, after an upload is made which fails
> I am uploading all except gpa, that will follow later.
Is that the gpg-agent? That'd be great to have. Save me half or 2/3 of the
typing when I'm signing packages.
I've opened two pull requests for cygport on github. No action has been taken on
them. One of them is a fairly trivial bug fix.
Are github pull requests a supported way of proposing changes to cygport? Or
should we post patches to cygwin-apps?
Thanks,
Andrew
1 - 100 of 609 matches
Mail list logo
