Moving on from Cygwin

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

Moving on from Cygwin

David Stacey
Sadly, the time has come for me to step back from being a Cygwin package
maintainer. I'm keen to take on a new project, and I need to free up
some time in what is already a fairly hectic life! This has meant some
difficult decisions about letting some things go in order to free up the
time needed, and my work as a Cygwin package maintainer is one of the
things I need to set aside.

So with immediate effect, all of my packages are available for adoption.
All are (more or less) up-to-date. Corinna has asked that I stay on the
list for a while to help any prospective maintainer in adopting one or
more of my packages, so I will remain subscribed to 'cygwin' and
'cygwin-apps' for at least a fortnight.

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 users
over the years. I know the work done here is genuinely appreciated by
the community, and I wish the programme every success in the future.

Dave.

SPC
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

SPC
2018-06-26 20:34 GMT+02:00 David Stacey <[hidden email]>:


> So with immediate effect, all of my packages are available for adoption.
> All are (more or less) up-to-date. Corinna has asked that I stay on the
> list for a while to help any prospective maintainer in adopting one or more
> of my packages, so I will remain subscribed to 'cygwin' and 'cygwin-apps'
> for at least a fortnight.
>
>
First of all, good luck with your new projects.​

About the adoption of some package(s) to maintain, I have more free time
than previously, so I could assume the maintenance of at least one. We can
talk about it privately if you want, despite of other procedures to make
this effective.

Kind Regards

Sergio
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

marco atzeri-4
Am 26.06.2018 um 21:55 schrieb SPC:
> 2018-06-26 20:34 GMT+02:00 David Stacey <[hidden email]>:
>
>
>> So with immediate effect, all of my packages are available for adoption.

>
> About the adoption of some package(s) to maintain, I have more free time
> than previously, so I could assume the maintenance of at least one. We can
> talk about it privately if you want, despite of other procedures to make
> this effective.
>
> Kind Regards
>
> Sergio
>

the pkg list is here:
https://cygwin.com/cygwin-pkg-maint

---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com

SPC
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

SPC
2018-06-26 22:28 GMT+02:00 Marco Atzeri <[hidden email]>:

> Am 26.06.2018 um 21:55 schrieb SPC:
>
>> 2018-06-26 20:34 GMT+02:00 David Stacey <[hidden email]>:
>>
>>
>> So with immediate effect, all of my packages are available for adoption.
>>>
>>
>
>> About the adoption of some package(s) to maintain, I have more free time
>> than previously, so I could assume the maintenance of at least one. We can
>> talk about it privately if you want, despite of other procedures to make
>> this effective.
>>
>> the pkg list is here:
> https://cygwin.com/cygwin-pkg-maint
>
>
​Thank you. I will review the list and check every package purpose.

Regards
Sergio

Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

Yaakov Selkowitz
In reply to this post by David Stacey
On 2018-06-26 13:34, David Stacey wrote:
> Sadly, the time has come for me to step back from being a Cygwin package
> maintainer. I'm keen to take on a new project, and I need to free up
> some time in what is already a fairly hectic life! This has meant some
> difficult decisions about letting some things go in order to free up the
> time needed, and my work as a Cygwin package maintainer is one of the
> things I need to set aside.
>
> So with immediate effect, all of my packages are available for adoption.

cygwin-pkg-maint has been updated accordingly.

> All are (more or less) up-to-date. Corinna has asked that I stay on the
> list for a while to help any prospective maintainer in adopting one or
> more of my packages, so I will remain subscribed to 'cygwin' and
> 'cygwin-apps' for at least a fortnight.
>
> 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 users
> over the years. I know the work done here is genuinely appreciated by
> the community, and I wish the programme every success in the future.

Thank you very much for your contributions over the years, and for being
willing to help make a smooth transition.  Much success in your future
endeavours.

Andrew, could you please polish a gold watch in honour of David's
retirement?

--
Yaakov
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

David Stacey
In reply to this post by SPC
On 26/06/18 20:55, SPC wrote:
> 2018-06-26 20:34 GMT+02:00 David Stacey<drstacey[at]tiscali[dot]co[dot]uk>:
>
>> So with immediate effect, all of my packages are available for adoption.
>>
> First of all, good luck with your new projects.​

Thank you!

> About the adoption of some package(s) to maintain, I have more free time
> than previously, so I could assume the maintenance of at least one. We can
> talk about it privately if you want, despite of other procedures to make
> this effective.

The best thing to do is pick a package that you actually use (or would
start using). I maintain quite a varied collection, so there might be
something there that interests you! Search for my name in the link that
Marco sent you earlier.

Let's keep our discussion to this list - it's probably best to keep
these conversations open. And thank you for your interest in becoming a
package maintainer!

Dave.

Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

Corinna Vinschen-2
In reply to this post by Yaakov Selkowitz
On Jun 26 17:26, Yaakov Selkowitz wrote:

> On 2018-06-26 13:34, David Stacey wrote:
> > Sadly, the time has come for me to step back from being a Cygwin package
> > maintainer. I'm keen to take on a new project, and I need to free up
> > some time in what is already a fairly hectic life! This has meant some
> > difficult decisions about letting some things go in order to free up the
> > time needed, and my work as a Cygwin package maintainer is one of the
> > things I need to set aside.
> >
> > So with immediate effect, all of my packages are available for adoption.
>
> cygwin-pkg-maint has been updated accordingly.
>
> > All are (more or less) up-to-date. Corinna has asked that I stay on the
> > list for a while to help any prospective maintainer in adopting one or
> > more of my packages, so I will remain subscribed to 'cygwin' and
> > 'cygwin-apps' for at least a fortnight.
> >
> > 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 users
> > over the years. I know the work done here is genuinely appreciated by
> > the community, and I wish the programme every success in the future.
>
> Thank you very much for your contributions over the years, and for being
> willing to help make a smooth transition.  Much success in your future
> endeavours.
I'd like to emphasize what Yaakov wrote.  Thanks a lot for all your work
on the project.  It was really nice to have you on-board!

> Andrew, could you please polish a gold watch in honour of David's
> retirement?

Yeah, absolutely.


Thanks again and make sure to have fun in your new activity,
Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

Michael Wild
On Wed, Jun 27, 2018 at 11:48 AM, Corinna Vinschen
<[hidden email]> wrote:

> On Jun 26 17:26, Yaakov Selkowitz wrote:
>> On 2018-06-26 13:34, David Stacey wrote:
>> > Sadly, the time has come for me to step back from being a Cygwin package
>> > maintainer. I'm keen to take on a new project, and I need to free up
>> > some time in what is already a fairly hectic life! This has meant some
>> > difficult decisions about letting some things go in order to free up the
>> > time needed, and my work as a Cygwin package maintainer is one of the
>> > things I need to set aside.
>> >
>> > So with immediate effect, all of my packages are available for adoption.
>>
>> cygwin-pkg-maint has been updated accordingly.
>>
>> > All are (more or less) up-to-date. Corinna has asked that I stay on the
>> > list for a while to help any prospective maintainer in adopting one or
>> > more of my packages, so I will remain subscribed to 'cygwin' and
>> > 'cygwin-apps' for at least a fortnight.
>> >
>> > 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 users
>> > over the years. I know the work done here is genuinely appreciated by
>> > the community, and I wish the programme every success in the future.
>>
>> Thank you very much for your contributions over the years, and for being
>> willing to help make a smooth transition.  Much success in your future
>> endeavours.
>
> I'd like to emphasize what Yaakov wrote.  Thanks a lot for all your work
> on the project.  It was really nice to have you on-board!
>
>> Andrew, could you please polish a gold watch in honour of David's
>> retirement?
>
> Yeah, absolutely.
>
>
> Thanks again and make sure to have fun in your new activity,
> Corinna


Dear all

For me the following orphaned packages are of importance (not all of
them David's):

* asciidoc
* doxygen
* gcovr
* python-paramiko

If nobody else steps up, I can adopt one or the other.

Michael
Reply | Threaded
Open this post in threaded view
|

doxygen Notes (was: Re: Moving on from Cygwin)

David Stacey
On 27/06/18 11:14, Michael Wild wrote:
> For me the following orphaned packages are of importance (not all of
> them David's):
>
> * doxygen
>
> If nobody else steps up, I can adopt one or the other.

Some notes on 'doxygen' that might help you (or someone else) maintain
the package:

doxygen is split into two packages: the main programme in 'doxygen', and
the 'doxywizard' GUI in 'doxygen-doxywizard'. It GUI icon used for
doxywizard is borrowed from the Fedora package and is part of kdesdk.

New doxygen releases are put out upstream once or twice a year (pay
attention around Christmas Day!) [1]. Between releases, it's worth
checking the patches that get applied to doxygen in a major distro, e.g
[2], and pick up any that you feel are important.

Doxygen has it's own C++ parser, which is quite 'loose' in its
understanding of C++. It's generally OK, but I've tripped it up in the
past with some complex template specialisation. Thankfully, doxygen can
be built to use clang for its parsing (although you have to explicitly
enable this in your doxygen file [3]). I build doxygen in this way to
give users the option of a 'better' C++ parser should they need it
(although I'm not aware of any major distro doing likewise).

Doxygen has an experimental feature to store its internal data in an
sqlite3 database. This is turned off, and I'm not aware of any major
distro enabling this feature.

Doxygen fails to compile under 64-bit Cygwin with the default CFLAGS and
CXXFLAGS as populated by cygport. The compilation fails in the assembler
with 'too many sections'. The solution is to suppress the generation of
the 'debuginfo' package for 64-bit, and then the compilation completes
successfully. This doesn't affect 32-bit Cygwin, where a 'debuginfo'
package is generated.

Hope that helps,

Dave.

[1] - http://doxygen.org/manual/changelog.html
[2] - https://src.fedoraproject.org/cgit/rpms/doxygen.git/tree/
[3] - http://doxygen.org/manual/config.html#cfg_clang_assisted_parsing
SPC
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

SPC
In reply to this post by Michael Wild
2018-06-27 12:14 GMT+02:00 Michael Wild <[hidden email]>:

>
> For me the following orphaned packages are of importance (not all of
> them David's):
>
> * asciidoc
> * doxygen
> * gcovr
> * python-paramiko
>
> If nobody else steps up, I can adopt one or the other.
>
> Michael
>

​I have reviewed the list of packages maintained by David so far. I have
identified three packages of simple maintenance at least in appearance:

- mscgen
- ninvaders
- words

I prefer to be cautious since I do not know the rules of maintenance and
publication of packages under Cygwin. I would need to have information
about it.

On the other hand, any comment about the matter is appreciated and welcome.

Kind Regards
Sergio
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

David Stacey
On 27/06/18 23:09, SPC wrote:
> I have reviewed the list of packages maintained by David so far. I have
> identified three packages of simple maintenance at least in appearance:
>
> - mscgen
> - ninvaders
> - words

All of these are effectively dead upstream:

- The last release of 'mscgen' was in 2011. There have been a handful of
commits since then [1], but nothing since January 2015. I carry some of
these commits as patches. As well as being useful in its own right,
mscgen is needed in Cygwin to provide the '\msc' command in doxygen.

- 'ninvaders' was last released in 2003(!). I include three patches - I
neglected to note the source of these, but they were probably from Debian.

- 'words' is a dictionary from the Moby project. This doesn't exist
anymore, and so the source file is pulled from a 2006 mirror on the
Wayback Machine! I include a couple of patches from Fedora to correct
some misspelled words and add the names of US presidents.

So the actual maintenance of these packages is going to be extremely
light. There are unlikely to be any new upstream versions. You'll just
need to rebuild them for any change in their dependencies, or to add
patches from the major distros.

> I prefer to be cautious since I do not know the rules of maintenance and
> publication of packages under Cygwin. I would need to have information
> about it.
>
> On the other hand, any comment about the matter is appreciated and welcome.

Start here [2].

Hope this helps,

Dave.

[1] - https://code.google.com/archive/p/mscgen/source/default/commits
[2] - https://cygwin.com/packages.html

Reply | Threaded
Open this post in threaded view
|

Moving on from Cygwin

Brian Inglis
On 2018-06-27 17:24, David Stacey wrote:
> On 27/06/18 23:09, SPC wrote:
>> I have reviewed the list of packages maintained by David so far. I have
>> identified three packages of simple maintenance at least in appearance:
>> - words
> All of these are effectively dead upstream:
> - 'words' is a dictionary from the Moby project. This doesn't exist anymore, and
> so the source file is pulled from a 2006 mirror on the Wayback Machine! I
> include a couple of patches from Fedora to correct some misspelled words and add
> the names of US presidents.

Documented by the author at:
        https://en.wikipedia.org/wiki/Moby_Project
which says mirrored at:
        http://www.gutenberg.org/catalog/world/results?title=moby+list
in etexts 3201-6.

The Moby word list is also part of the Cygwin scowl package from
        http://wordlist.aspell.net/
        https://github.com/en-wl/wordlist

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

Andrew Schulman
In reply to this post by Yaakov Selkowitz
> > 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 users
> > over the years. I know the work done here is genuinely appreciated by
> > the community, and I wish the programme every success in the future.
>
> Thank you very much for your contributions over the years, and for being
> willing to help make a smooth transition.  Much success in your future
> endeavours.
>
> Andrew, could you please polish a gold watch in honour of David's
> retirement?

Awarded! https://cygwin.com/goldstars#DSt

Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

David Stacey
In reply to this post by Brian Inglis
On 28/06/18 13:15, Brian Inglis wrote:

> On 2018-06-27 17:24, David Stacey wrote:
>> All of these are effectively dead upstream:
>> - 'words' is a dictionary from the Moby project. This doesn't exist anymore, and
>> so the source file is pulled from a 2006 mirror on the Wayback Machine! I
>> include a couple of patches from Fedora to correct some misspelled words and add
>> the names of US presidents.
> Documented by the author at:
> https://en.wikipedia.org/wiki/Moby_Project
> which says mirrored at:
> http://www.gutenberg.org/catalog/world/results?title=moby+list
> in etexts 3201-6.

Thanks for the information. I used the same source URL as Fedora [1] -
in fact, I just translated Fedora's 'spec' file into 'cygport' form.

Obviously, a new maintainer is free to pick whichever source of the Moby
dictionary that he or she wishes. Note, however, that in the Gutenberg
mirror, the files have all been renamed meaning that Fedora's 'typos'
patch won't apply.

Dave.

[1] - https://src.fedoraproject.org/cgit/rpms/words.git/tree/words.spec

Reply | Threaded
Open this post in threaded view
|

Re: Moving on from Cygwin

David Stacey
In reply to this post by David Stacey
On 26/06/18 19:34, David Stacey wrote:
> Sadly, the time has come for me to step back from being a Cygwin
> package maintainer. Corinna has asked that I stay on the list for a
> while to help any prospective maintainer in adopting one or more of my
> packages, so I will remain subscribed to 'cygwin' and 'cygwin-apps'
> for at least a fortnight.

I'm unsubscribing from the Cygwin lists now, but I leave you with
parting gifts (see below). All are tested in both architectures, and if
I was still maintaining these packages I would upload them. I will leave
it to your judgement to decide whether to take them or not.

All the best,

Dave.



# gcovr-4.1 (noarch)
BASEURL=https://www.dropbox.com/s
mkdir -p noarch/release/gcovr
pushd noarch/release/gcovr
wget "${BASEURL}/ny5q6goa6xopgy9/gcovr-4.1-1-src.tar.xz"
wget "${BASEURL}/9u30xmioyxlic2v/gcovr-4.1-1.hint"
wget "${BASEURL}/v0aah48c935mq8s/gcovr-4.1-1.tar.xz"
popd



# ruby-puppet-lint-2.3.6 (noarch)
BASEURL=https://www.dropbox.com/s
mkdir -p noarch/release/ruby-puppet-lint/ruby-puppet-lint-doc
pushd noarch/release/ruby-puppet-lint
wget "${BASEURL}/dny3a4dqnl161fj/ruby-puppet-lint-2.3.6-1-src.tar.xz"
wget "${BASEURL}/cde6f42b9nnh1xu/ruby-puppet-lint-2.3.6-1.hint"
wget "${BASEURL}/rlq2bco9zym9ucy/ruby-puppet-lint-2.3.6-1.tar.xz"
cd ruby-puppet-lint-doc
wget "${BASEURL}/1q67qtbqx5yvqva/ruby-puppet-lint-doc-2.3.6-1.hint"
wget "${BASEURL}/4159ed32h994jb7/ruby-puppet-lint-doc-2.3.6-1.tar.xz"
popd



# mkvtoolnix-25.0.0 (x86)
BASEURL=https://www.dropbox.com/s
mkdir -p x86/release/mkvtoolnix/mkvtoolnix-debuginfo
mkdir -p x86/release/mkvtoolnix/mkvtoolnix-gui
pushd x86/release/mkvtoolnix
wget "${BASEURL}/bil2ods4dwzhb8t/mkvtoolnix-25.0.0-1-src.tar.xz"
wget "${BASEURL}/hli3l99i14rjoeo/mkvtoolnix-25.0.0-1.hint"
wget "${BASEURL}/agisva915of2jkh/mkvtoolnix-25.0.0-1.tar.xz"
cd mkvtoolnix-debuginfo
wget "${BASEURL}/5a9tvbjkp4ydi9d/mkvtoolnix-debuginfo-25.0.0-1.hint"
wget "${BASEURL}/5c17ovxdk06jd3a/mkvtoolnix-debuginfo-25.0.0-1.tar.xz"
cd ../mkvtoolnix-gui
wget "${BASEURL}/kb2f2jktux18dx2/mkvtoolnix-gui-25.0.0-1.hint"
wget "${BASEURL}/b1zv4fqdirbxjr6/mkvtoolnix-gui-25.0.0-1.tar.xz"
popd



# mkvtoolnix-25.0.0 (x86_64)
BASEURL=https://www.dropbox.com/s
mkdir -p x86_64/release/mkvtoolnix/mkvtoolnix-debuginfo
mkdir -p x86_64/release/mkvtoolnix/mkvtoolnix-gui
pushd x86_64/release/mkvtoolnix
wget "${BASEURL}/ypawzizaeo2y8l1/mkvtoolnix-25.0.0-1-src.tar.xz"
wget "${BASEURL}/y9ohlr3r0rmek1y/mkvtoolnix-25.0.0-1.hint"
wget "${BASEURL}/ow84ki9jqao5i60/mkvtoolnix-25.0.0-1.tar.xz"
cd mkvtoolnix-debuginfo
wget "${BASEURL}/t3zxql66ewoq7rf/mkvtoolnix-debuginfo-25.0.0-1.hint"
wget "${BASEURL}/8hus4yfx3t8oemp/mkvtoolnix-debuginfo-25.0.0-1.tar.xz"
cd ../mkvtoolnix-gui
wget "${BASEURL}/z201b1c1bho2qg0/mkvtoolnix-gui-25.0.0-1.hint"
wget "${BASEURL}/iqnqqo4sxl1b6px/mkvtoolnix-gui-25.0.0-1.tar.xz"
popd