Re: New SSH key for upload access
On Tue, Aug 25, 2020 at 7:36 PM Marco Atzeri via Cygwin-apps wrote: > On 25.08.2020 17:34, Jon Turney wrote: > > On 25/08/2020 15:14, Michael Wild via Cygwin-apps wrote: > >> Name: Michael Wild > >> Packages: tmux, python-bcrypt, python-nacl, python-paramiko, ssh-pageant > > >> --- END SSH2 PUBLIC KEY --- > > > > This doesn't look like a key export made with 'ssh-keygen -e', so I had > > to import it manually, hopefully correctly. > > > > Done. > > Michael, > I recently updated python-bcrypt, > and I built but not uploaded yet python-nacl > > are you planning to upload python-paramiko ? > > Regards > Marco > Hi Marco Sorry, I was AWOL for some time, work was just overwhelming and Cygwin was basically useless with the corporate spyware... Now I changed employer and I intend picking things up again. Yes, I intend to update paramiko, and its dependencies, also for Python 3.7 and 3.8. Kind regards Michael
New SSH key for upload access
Name: Michael Wild Packages: tmux, python-bcrypt, python-nacl, python-paramiko, ssh-pageant --- BEGIN SSH2 PUBLIC KEY --- ssh-rsa B3NzaC1yc2EDAQABAAACAQDU+zzguNEciNwsMPnPJVsSh0ZNpfTjgpZH/7t1SdLK6wFEO4Q59D1a82NkRAfN3TRQFDuAqvHr5xWrA7S5jraQbTM569gRwvAKWJoiSd6ascJXx/P0Rnb6Idf+M7Cg+TKRCLfPqrX8gtoirZmIBkR6wld8iUqH/mYcTPVpmXr/NwWp4G242WrFn2uhoKGqct8cxYyzqKqgbi4bAOpxH8TsEMsodKBP0ETBDcR/9MJclH6RuQTsYFEwth6iN2pZaUofSMiJTtlxCbXIOFwI4CIccTp/3uaFdkKBmvlw+gIU5mnGchvi/AR1XrA+2nz9aI2m0LeDGLitKZR7ymzSKWfa7BqiSYwf+nzEGHbKQtYDDS9rIUFChdzOoM/9uhF/EbF7mqQZXSvciCvsLIOrHOqIXJcdL8dzK0iWTYgYmgFbSj3zx0xY9KO4vO0v1m+3k0kkKCFwcyiIJ6sjFZVJighttbPClhsLm/UCzvFg4WHFb+55zQQLXufs/R6ysn8jalNp4KIeFkpm9XFUXGVGjTAn+uIyrJPm7X8kga5a8ukq5yTFg7TbpqCRx6mtrorrZyepXz9zfNfjq9kuSVYlNXM50DVBQwkKrgn6EtgXR06sdtNMlxjEeptVSpsCoqPsMrKAl/RB+3QIKLc9Fsws9XZYVVR1OZ/nu2Q1cwyTWgnnCw== --- END SSH2 PUBLIC KEY ---
Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
On Thu, Aug 2, 2018 at 7:16 PM Michael Wild wrote: > On Thu, 2 Aug 2018, 19:04 Marco Atzeri, wrote: > >> [...] >> >> Michael >> you are now the maintainer for the 3 packages. >> >> Regards >> Marco >> >> --- >> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. >> https://www.avast.com/antivirus > > > Cool, thanks. Will upload tomorrow. > > Michael > Dear all I just tried to upload my new packages. The new python-bcrypt and python-nacl went through, but the updated python-paramiko gives me below error. Could it be because the existing version is not noarch? Calm sends me below message. Cheers Michael -- Forwarded message - From: Date: Fri, Aug 3, 2018 at 10:50 PM Subject: calm: cygwin package upload report from sourceware.org for Michael Wild To: ERROR: package 'python-paramiko' is at paths x86/release/python-paramiko and noarch/release/python-paramiko ERROR: error while merging uploaded x86 packages for Michael Wild SUMMARY: 2 ERROR(s)
Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
On Thu, 2 Aug 2018, 19:04 Marco Atzeri, wrote: > Am 30.07.2018 um 10:59 schrieb Marco Atzeri: > > Am 23.07.2018 um 23:13 schrieb Yaakov Selkowitz: > >> On Fri, 2018-07-20 at 13:15 +0200, Michael Wild wrote: > >>> I would like to adopt the orphaned package python-paramiko. In order > >>> to bring it to its current version, additional dependencies need to be > >>> packaged, namely python-bcrypt and python-PyNaCl. > > > > > I built all the 3 packages and they seem fine. > > As they are missing testsuites I assume Michael tested them. > > > > I would say GTG. > > > > Michael > you are now the maintainer for the 3 packages. > > Regards > Marco > > --- > Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. > https://www.avast.com/antivirus Cool, thanks. Will upload tomorrow. Michael > >
Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
On Thu, Jul 26, 2018 at 3:15 PM Michael Wild wrote:
> On Wed, Jul 25, 2018 at 9:52 PM Yaakov Selkowitz
> wrote:
>
>> On Tue, 2018-07-24 at 10:17 +0200, Michael Wild wrote:
>> > Another question: if you look at the cygport file
>> >
>> https://github.com/themiwi/cygwin/blob/master/python-paramiko/python-paramiko.cygport
>> ,
>> > I jump through some hoops to get
>> > /usr/share/doc/Cygwin/python{2,3}-paramiko.README generated from a
>> single
>> > patch and installed. Am I missing something? Particularly, the
>> python-wheel
>> > cygclass does not seem to include files in /usr/share/doc/Cygwin.
>>
>> TBH those "Cygwin READMEs" are not required and I generally do not
>> include them in any of my packages. Therefore, cygport isn't
>> completely automated when it comes to those.
>>
>
> Ah, what a relief. I was starting to worry that I have to include them in
> my other packages too :-)
>
> Pushed the simplifications and uploaded the packages to Dropbox for final
> review and waiting for GTG.
>
> Michael
>
Ping... Yaakov, is it you giving the GTG for the ITA for python-paramiko?
Michael
Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
On Wed, Jul 25, 2018 at 9:52 PM Yaakov Selkowitz
wrote:
> On Tue, 2018-07-24 at 10:17 +0200, Michael Wild wrote:
> > Another question: if you look at the cygport file
> >
> https://github.com/themiwi/cygwin/blob/master/python-paramiko/python-paramiko.cygport
> ,
> > I jump through some hoops to get
> > /usr/share/doc/Cygwin/python{2,3}-paramiko.README generated from a single
> > patch and installed. Am I missing something? Particularly, the
> python-wheel
> > cygclass does not seem to include files in /usr/share/doc/Cygwin.
>
> TBH those "Cygwin READMEs" are not required and I generally do not
> include them in any of my packages. Therefore, cygport isn't
> completely automated when it comes to those.
>
Ah, what a relief. I was starting to worry that I have to include them in
my other packages too :-)
Pushed the simplifications and uploaded the packages to Dropbox for final
review and waiting for GTG.
Michael
Re: How to package a Python script
Ok, thanks! That clears things up for me.
On Wed, Jul 25, 2018 at 7:59 PM Yaakov Selkowitz
wrote:
> On Wed, 2018-07-25 at 16:55 +0200, Michael Wild wrote:
> > How should I go about packaging a Python executable? Separate packages
> > for python2 and python3? Only one of them? If so, which? If for both,
> > is there any advice how to achieve this? I don't think that the
> > python-wheel.cygclass deals with scripts in /usr/bin/ as the docs say
> > that scripts should be added to PKG_CONTENTS by the maintainer. How
> > would I go about making sure that I get a *2 and *3 version, also
> > possibly with a symlink from * to *2? Is there a cannonical example I
> > can look into? My casual trawling through my own Cygwin installation
> > didn't turn up anything useful...
>
> Depends on the package. Most python-based scripts also include
> modules, and sometimes those modules are generally usable and the
> script is just a convenient entrypoint thereto (in which case it should
> be named 'python-foo', *2 and *3 should be made via python-
> wheel.cygclass, and the script packaged with *3), and sometimes they
> serve only themselves (in which case it should be named 'foo' and
> packaged with the appropriate choice of python{2,3}-
> {distutils,wheel}.cygclass).
>
> --
> Yaakov Selkowitz
> Software Engineer - Platform Enablement Group
> Red Hat, Inc.
>
>
>
How to package a Python script
Dear all How should I go about packaging a Python executable? Separate packages for python2 and python3? Only one of them? If so, which? If for both, is there any advice how to achieve this? I don't think that the python-wheel.cygclass deals with scripts in /usr/bin/ as the docs say that scripts should be added to PKG_CONTENTS by the maintainer. How would I go about making sure that I get a *2 and *3 version, also possibly with a symlink from * to *2? Is there a cannonical example I can look into? My casual trawling through my own Cygwin installation didn't turn up anything useful... Cheers Michael
Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
On Wed, Jul 25, 2018 at 9:42 AM Marco Atzeri wrote: > Am 25.07.2018 um 09:25 schrieb Michael Wild: > > Dear all > > > > I uploaded new builds of python-nacl and python-paramiko to > > > https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0. > > > > BTW: Do I need a "good to go" or is it OK if I go ahead with uploading > > since I already maintain tmux and ssh-pageant? > > > > Michael > > > > Michael, > bottom post here please. > > You need a GTG and a change of assignement in > > http://www.cygwin.com/cygwin-pkg-maint > > otherwise you can not upload it. > > Regards > Marco > > Thanks Marco, Sorry about the top-post; I got tricked by Google Inbox which doesn't show the original text when replying... Ok, waiting for the GTG... Michael
Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
Dear all
I uploaded new builds of python-nacl and python-paramiko to
https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0.
BTW: Do I need a "good to go" or is it OK if I go ahead with uploading
since I already maintain tmux and ssh-pageant?
Michael
On Tue, Jul 24, 2018 at 10:17 AM Michael Wild wrote:
>
>
> On Mon, 23 Jul 2018, 23:13 Yaakov Selkowitz,
> wrote:
>
>> On Fri, 2018-07-20 at 13:15 +0200, Michael Wild wrote:
>> > I would like to adopt the orphaned package python-paramiko. In order
>> > to bring it to its current version, additional dependencies need to be
>> > packaged, namely python-bcrypt and python-PyNaCl.
>> >
>> > Debian packages:
>> >
>> > * https://packages.debian.org/stretch/python-paramiko
>> > * https://packages.debian.org/stretch/python-bcrypt
>> > * https://packages.debian.org/stretch/python-nacl
>> >
>> > For the latter I have the problem that upstream calls it PyNaCl, but
>> > distros seem to drop the "Py" prefix. What is the preferred naming
>> > scheme for Cygwin?
>>
>> python-nacl for the sources, python{2,3}-nacl for the binaries.
>>
>> > For those wanting to review the packages, I uploaded them to
>> >
>> https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0
>> .
>>
>> --
>> Yaakov
>>
>
> Thanks Yaakov.
>
> Another question: if you look at the cygport file
> https://github.com/themiwi/cygwin/blob/master/python-paramiko/python-paramiko.cygport,
> I jump through some hoops to get
> /usr/share/doc/Cygwin/python{2,3}-paramiko.README generated from a single
> patch and installed. Am I missing something? Particularly, the python-wheel
> cygclass does not seem to include files in /usr/share/doc/Cygwin.
>
> Michael
>
>>
Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
On Mon, 23 Jul 2018, 23:13 Yaakov Selkowitz, wrote:
> On Fri, 2018-07-20 at 13:15 +0200, Michael Wild wrote:
> > I would like to adopt the orphaned package python-paramiko. In order
> > to bring it to its current version, additional dependencies need to be
> > packaged, namely python-bcrypt and python-PyNaCl.
> >
> > Debian packages:
> >
> > * https://packages.debian.org/stretch/python-paramiko
> > * https://packages.debian.org/stretch/python-bcrypt
> > * https://packages.debian.org/stretch/python-nacl
> >
> > For the latter I have the problem that upstream calls it PyNaCl, but
> > distros seem to drop the "Py" prefix. What is the preferred naming
> > scheme for Cygwin?
>
> python-nacl for the sources, python{2,3}-nacl for the binaries.
>
> > For those wanting to review the packages, I uploaded them to
> >
> https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0.
>
> --
> Yaakov
>
Thanks Yaakov.
Another question: if you look at the cygport file
https://github.com/themiwi/cygwin/blob/master/python-paramiko/python-paramiko.cygport,
I jump through some hoops to get
/usr/share/doc/Cygwin/python{2,3}-paramiko.README generated from a single
patch and installed. Am I missing something? Particularly, the python-wheel
cygclass does not seem to include files in /usr/share/doc/Cygwin.
Michael
>
[ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1
Dear all I would like to adopt the orphaned package python-paramiko. In order to bring it to its current version, additional dependencies need to be packaged, namely python-bcrypt and python-PyNaCl. Debian packages: * https://packages.debian.org/stretch/python-paramiko * https://packages.debian.org/stretch/python-bcrypt * https://packages.debian.org/stretch/python-nacl For the latter I have the problem that upstream calls it PyNaCl, but distros seem to drop the "Py" prefix. What is the preferred naming scheme for Cygwin? For those wanting to review the packages, I uploaded them to https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0. All the best and a nice weekend! Michael
Re: Moving on from Cygwin
On Wed, Jun 27, 2018 at 11:48 AM, Corinna Vinschen 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
Re: [ITP] ssh-pageant 1.4
On Mon, Feb 2, 2015 at 10:18 AM, Corinna Vinschen corinna-cyg...@cygwin.com wrote: On Jan 30 19:26, Michael Wild wrote: On Tue, Jan 27, 2015 at 6:53 PM, Andrew Schulman schulman.and...@epa.gov wrote: Dear all I would like to package ssh-pageant and propose it for inclusion in Cygwin. The small tool acts like an ssh-agent, but instead of storing its own keys, it is connecting to the PuTTY Pageant tool. This way the very useful Pageant tool can be used from Cygwin and no separate ssh-agent is required. +1 Since this package is not in any Linux distro, I need five GTG's, right? So keep 'em coming :-) I was unclear in my reply. What I was trying to say is, you don't need the votes. Just go ahead, you should be able to upload this package already. Thanks, I just uploaded it right now.
Re: [ITP] ssh-pageant 1.4
On Tue, Jan 27, 2015 at 6:53 PM, Andrew Schulman schulman.and...@epa.gov wrote: Dear all I would like to package ssh-pageant and propose it for inclusion in Cygwin. The small tool acts like an ssh-agent, but instead of storing its own keys, it is connecting to the PuTTY Pageant tool. This way the very useful Pageant tool can be used from Cygwin and no separate ssh-agent is required. +1 Since this package is not in any Linux distro, I need five GTG's, right? So keep 'em coming :-) Michael
[ITP] ssh-pageant 1.4
Dear all I would like to package ssh-pageant and propose it for inclusion in Cygwin. The small tool acts like an ssh-agent, but instead of storing its own keys, it is connecting to the PuTTY Pageant tool. This way the very useful Pageant tool can be used from Cygwin and no separate ssh-agent is required. ssh-pageant being developed specifically for Cygwin/MSYS it is naturally not included in Linux distros. My proposed setup.hint: category: Net requires: sdesc: SSH agent for Cygwin/MSYS that links to PuTTY's Pageant ldesc: ssh-pageant is a tiny tool for Windows that allows you to use SSH keys from PuTTY's Pageant in Cygwin and MSYS shell environments. You can use ssh-pageant to automate SSH connections from those shells, which is useful for services built on top of SSH, like SFTP file transfers or pushing to secure git repositories. ssh-pageant works like ssh-agent, except that it leaves the key storage to PuTTY's Pageant. It sets up an authentication socket and prints the environment variables, which allows OpenSSH connections to use it. The package build successfully and everything works for me. The package files are available for inspection from: https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.i686/setup.hint https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.i686/ssh-pageant-1.4-1-src.tar.xz https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.i686/ssh-pageant-1.4-1.tar.xz https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.i686/setup-debuginfo.hint https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.i686/ssh-pageant-debuginfo-1.4-1.tar.xz https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.x86_64/setup.hint https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.x86_64/ssh-pageant-1.4-1-src.tar.xz https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.x86_64/ssh-pageant-1.4-1.tar.xz https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.x86_64/setup-debuginfo.hint https://github.com/themiwi/cygwin/releases/download/cyg-ssh-pageant-1.4-1.x86_64/ssh-pageant-debuginfo-1.4-1.tar.xz Once I get the required GTG's, I will upload the package. Kind regards Michael
Updated: tmux-1.9a-2
Version 1.9a-2 of tmux has been uploaded. tmux is a terminal multiplexer, similar to GNU screen. It enables a number of terminals (or windows) to be accessed and controlled from a single terminal like GNU screen. tmux runs as a server-client system. Moreover tmux provides a consistent and well-documented command interface, with the same syntax whether used interactively, as a key binding, or from the shell. It offers a choice of vim or Emacs key layouts. This revision temporarily fixes (or papers over...) an issue that was introduced when the cygwin DLL was updated to version 1.7.30-1. Apparently this update introduced a change in the way that the connect(2) function handles errors, that caused tmux to output failed to connect to server: No error if the socket file in /tmp/tmux* already existed. Deeper analysis of the issue is pending. Refer to the following mailing list threads for more information: https://cygwin.com/ml/cygwin/2014-04/msg00539.html http://sourceforge.net/p/tmux/mailman/message/32396655/ http://sourceforge.net/p/tmux/mailman/message/32400834/ https://cygwin.com/ml/cygwin/2014-06/msg8.html *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com at cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Re: [ITP] tmux 1.9a (was 1.8-271-gb3de4a3)
On Mon, Mar 3, 2014 at 3:43 PM, Christopher Faylor wrote: On Mon, Mar 03, 2014 at 12:19:09PM +0100, Corinna Vinschen wrote: Thanks. Just go ahead as soon as cgf sent you the confirmation that your account is set up. Remember that the account can't be set up unless Michael is in cygwin-pkg-maint. Really, they should be in this file before a request is sent or the instructions at https://sourceware.org/cygwin-apps/package-upload.html can't be followed. cgf That left me also a bit wondering ;-) I assumed that this would be done together with the request. So, how do I get in there? Michael
Re: SSH key for upload access
On Mon, Mar 3, 2014 at 8:54 PM, Christopher Faylor wrote: On Mon, Mar 03, 2014 at 08:48:36AM +0100, Michael Wild wrote: Name: Michael Wild Package: tmux BEGIN SSH2 PUBLIC KEY B3NzaC1yc2EDAQABAAACAQDXSw+vo3bC3xBiXB+q1csKoosY29+t1Rcs1Lu4mp DmZ2gYRqSHkGeFTXtCeAsC+QfwoNzQwvU3/IHUyxZQxREZbBkaNdYM86Ys7+kpcOAUABOo +aFersL24CcmirhyWorjfI13bLmviu52XUqKd5VKjNAV5J00iQSUVr+xhcVprpeNg9/wWn NIuHPB/kmj/tAnK+Ssqx1MWpE+EicXam9FS9/8DGTuW6aTI4mm2aMDj3tdZmS+QO9L/RaU 9S9X+aHxzD101DgrtJjCHBA/aJ7Lv9NSNXdhGasSkIRMESVqyCw6+fXl3Xqb5qIKuLijs0 AvYCO5Iwx3xjlOwWrxIsDElumrDvNaSRomgb0q7Czwx2KBLWrc0qTR3GuJBCdbB7BTtUK1 fn3S3lu5+g40cfYCTekBAhoJrR3beOH9v/LYZNphfzRwXRmOcoldvChMKzqW+VJ+chi0/C qY9TCo9nc1sKcTnyHpAwKuAm3tzo+4WktQ93OeezcwvPWNWoh16K4BYkG6OBkGaSsSc+3O LV0a1kvEquMDcYBWj7j1FUeWI2U28Ns/HBnb/NluK59hFHC8PoJ2zkViRgYVlpkWb9+0KW uSKEX6pHz144juVvs5tCFXBJl1RJ5WokxXbAjwKy9fNk8pEFNZ1bz3j1RhB0O0coO5uzz+ TPbyVOvT6Zwraw== END SSH2 PUBLIC KEY Added to cygwin-pkg-maint and account activated. cgf Many thanks! Michael
SSH key for upload access
Name: Michael Wild Package: tmux BEGIN SSH2 PUBLIC KEY B3NzaC1yc2EDAQABAAACAQDXSw+vo3bC3xBiXB+q1csKoosY29+t1Rcs1Lu4mp DmZ2gYRqSHkGeFTXtCeAsC+QfwoNzQwvU3/IHUyxZQxREZbBkaNdYM86Ys7+kpcOAUABOo +aFersL24CcmirhyWorjfI13bLmviu52XUqKd5VKjNAV5J00iQSUVr+xhcVprpeNg9/wWn NIuHPB/kmj/tAnK+Ssqx1MWpE+EicXam9FS9/8DGTuW6aTI4mm2aMDj3tdZmS+QO9L/RaU 9S9X+aHxzD101DgrtJjCHBA/aJ7Lv9NSNXdhGasSkIRMESVqyCw6+fXl3Xqb5qIKuLijs0 AvYCO5Iwx3xjlOwWrxIsDElumrDvNaSRomgb0q7Czwx2KBLWrc0qTR3GuJBCdbB7BTtUK1 fn3S3lu5+g40cfYCTekBAhoJrR3beOH9v/LYZNphfzRwXRmOcoldvChMKzqW+VJ+chi0/C qY9TCo9nc1sKcTnyHpAwKuAm3tzo+4WktQ93OeezcwvPWNWoh16K4BYkG6OBkGaSsSc+3O LV0a1kvEquMDcYBWj7j1FUeWI2U28Ns/HBnb/NluK59hFHC8PoJ2zkViRgYVlpkWb9+0KW uSKEX6pHz144juVvs5tCFXBJl1RJ5WokxXbAjwKy9fNk8pEFNZ1bz3j1RhB0O0coO5uzz+ TPbyVOvT6Zwraw== END SSH2 PUBLIC KEY
Re: [ITP] tmux 1.9a (was 1.8-271-gb3de4a3)
Hi Corinna Sorry for the late response, I was on vacation and then punished by a nasty cold... On Fri, Feb 21, 2014 at 10:05 AM, Corinna Vinschen wrote: Neat. Apart from proposing to include the package, are you willing to maintain this package in the Cygwin distro and help users on the cygwin AT cygwin DOT com mailing list? Also, did you see https://sourceware.org/cygwin-apps/package-upload.html? Yes, I am willing to do so. I read this document, but will probably need to revisit it again from time to time ;-) These are only 32 bit packages? Would you mind to provide the 64 bit packages as well, please? I now also built using Cygwin64. However, in order to do so, I had to change the dependency on ARCH_x86_64 to libncursesw-devel. Otherwise I still depend on libncurses-devel. Is this the correct procedure? I was a bit confused that there is no libncurses-devel package on Cygwin64. In the meantime version 1.9a was released, so I updated the package. It being an official release, I removed the test version tag from the setup.hint. ARCH_i686: category: Utils requires: libevent2.0_5 libncurses10 sdesc: Terminal multiplexer ldesc: tmux enables a number of terminals (or windows) to be accessed and controlled from a single terminal like screen. tmux runs as a server-client system. A server is created automatically when necessary and holds a number of sessions, each of which may have a number of windows linked to it. Any number of clients may connect to a session, or the server may be controlled by issuing commands with tmux. Communication takes place through a socket, by default placed in /tmp. Moreover tmux provides a consistent and well-documented command interface, with the same syntax whether used interactively, as a key binding, or from the shell. It offers a choice of vim or Emacs key layouts. ARCH_x86_64: category: Utils requires: libevent2.0_5 libncursesw10 sdesc: Terminal multiplexer ldesc: tmux enables a number of terminals (or windows) to be accessed and controlled from a single terminal like screen. tmux runs as a server-client system. A server is created automatically when necessary and holds a number of sessions, each of which may have a number of windows linked to it. Any number of clients may connect to a session, or the server may be controlled by issuing commands with tmux. Communication takes place through a socket, by default placed in /tmp. Moreover tmux provides a consistent and well-documented command interface, with the same syntax whether used interactively, as a key binding, or from the shell. It offers a choice of vim or Emacs key layouts. The package files can be obtained from: * http://wildcodes.com/cygwin/tmux/setup.hint * http://wildcodes.com/cygwin/tmux/tmux-1.9a-1-src.tar.xz * http://wildcodes.com/cygwin/tmux/tmux-1.9a-1.tar.xz * http://wildcodes.com/cygwin/tmux/tmux-debuginfo/setup.hint * http://wildcodes.com/cygwin/tmux/tmux-debuginfo/tmux-debuginfo-1.9a-1.tar.xz * http://wildcodes.com/cygwin64/tmux/setup.hint * http://wildcodes.com/cygwin64/tmux/tmux-1.9a-1-src.tar.xz * http://wildcodes.com/cygwin64/tmux/tmux-1.9a-1.tar.xz * http://wildcodes.com/cygwin64/tmux/tmux-debuginfo/setup.hint * http://wildcodes.com/cygwin64/tmux/tmux-debuginfo/tmux-debuginfo-1.9a-1.tar.xz Kind regards Michael PS: @Balaji Thanks for pointing me to the 1.9a version. It was released while I was struggling with the mailing list to get my mails through, that's why I hadn't noticed it.
