Re: Perl 5.22.0
On 7/14/2015 10:40 PM, Marco Atzeri wrote: On 7/14/2015 9:51 PM, Achim Gratz wrote: Achim Gratz writes: There are a few Perl distribution packages that are captive in another source package. The hopefully complete list of such packages: perl-Graphics-Magick perl-gv perl-Image-Magick perl-ming perl-Net-Libproxy perl-Xfce4-Xfconf perl-zinnia This means that again Yaakov as well as Marco and Volker need to re-release those. Yaakov has volunteered to update Volker's packages while he's away, I hope the offer still stands. perl-Graphics-Magick perl-Image-Magick are already available as test These packages place module files into vendor_perl while the package name has nothing to do with Perl (not all of them are available for both architectures): amanda biber git-svn git irssi net-snmp-perl po4a pristine-tar sendxmpp subversion-perl irssi postgresql-plperl are also available as test And lastly, two packages put files in site_perl which should not happen for official packages, so that should be corrected anyway: grepmail stow Regards MArco
Re: missing 64bit ports
On Jul 15, 2015, at 8:24 AM, Marco Atzeri marco.atz...@gmail.com wrote: I spent a bit of time checking the real situation of the packages still missing as 64 bit port. Thank you for doing this research. ...we are down to ~44. ...half of them are dead upstream so we can directly obsolete and don't worry anynore. Wow. I’ve updated my related answer on Stack Overflow (http://goo.gl/yOAqAn) to reflect this drastic shrinkage of this list’s size.
Re: missing 64bit ports
On Jul 15, 2015, at 11:39 AM, Marcos Vives Del Sol socram8...@gmail.com wrote: Reason I didn't port libnfc was because I lost my SSH key due to a hard drive crash. Any procedure on how to get a new one so I can compile and upload it? $ ssh-keygen I assume those in charge of maintaining the list of allowed keys will be willing to accept a different key from you, so just resubmit it as if you were doing it for the first time.
Re: missing 64bit ports
Reason I didn't port libnfc was because I lost my SSH key due to a hard drive crash. Any procedure on how to get a new one so I can compile and upload it? 2015-07-15 16:24 GMT+02:00 Marco Atzeri marco.atz...@gmail.com: Dear All, I spent a bit of time checking the real situation of the packages still missing as 64 bit port. After xdelta, bsdiff and iperf porting, without counting the few mingw ones, the duplicates we are down to ~44. Please see here the analysis : https://docs.google.com/spreadsheets/d/1Hn7Eaq6djEN9X0jS_AM8-DH_LvP43G9_DXnpTt09Asc/edit#gid=0 Feel free to insert comments on the cells. For what I found : - half of them are dead upstream so we can directly obsolete and don't worry anynore. - Few are Jary's scripts, so the only porting issue is Jary's time. - Very few have real porting issue The only one really interesting for me is Mathomatic and eventually catdoc if works with latest word documents. (of course I will port pure-ftpd) Regards Marco -- Marcos Vives Del Sol https://github.com/socram miniLock: NscWdW8fh2E5SBoRtrnXWrDwmQmwaR5awMKE78tQW1Ffx
Re: [ADOPT] iperf 2.0.8
You are the new maintainer Congratulation. Gold star awarded! https://cygwin.com/goldstars/#JJ
Re: missing 64bit ports
On 7/15/2015 2:28 PM, Corinna Vinschen wrote: On Jul 15 16:24, Marco Atzeri wrote: Dear All, I spent a bit of time checking the real situation of the packages still missing as 64 bit port. After xdelta, bsdiff and iperf porting, without counting the few mingw ones, the duplicates we are down to ~44. Please see here the analysis : https://docs.google.com/spreadsheets/d/1Hn7Eaq6djEN9X0jS_AM8-DH_LvP43G9_DXnpTt09Asc/edit#gid=0 Feel free to insert comments on the cells. For what I found : - half of them are dead upstream so we can directly obsolete and don't worry anynore. - Few are Jary's scripts, so the only porting issue is Jary's time. - Very few have real porting issue The only one really interesting for me is Mathomatic and eventually catdoc if works with latest word documents. (of course I will port pure-ftpd) Thanks for looking into this. Two points: - Shall we remove all 32b-bit only orphaned packages for which we don't get a maintainer until, say, end of August? That seems reasonable, as long as there are exceptions for packages where the lack of a 64-bit package is due to genuine porting difficulties. libsigsegv was in that category until yesterday. Another one I'm aware of is ffcall. - We should probably consider to remove the mingw.org packages. All of them. They are hopelessly outdated and mingw-w64 does the same job better hands down. +1 Ken
Re: missing 64bit ports
On Jul 15, 2015, at 12:28 PM, Corinna Vinschen corinna-cyg...@cygwin.com wrote: - Shall we remove all 32b-bit only orphaned packages for which we don't get a maintainer until, say, end of August? If a package is available only for 32-bit, there should be a place to learn that prior to running setup.exe. The fact that some items are on that list because they’re orphaned and thus have no immediate prospect of getting off the list is inconsequential to the end users who consult it. If your goal is to evaporate this list, I’d prefer that you just removed orphaned packages from both the 32- and 64-bit repositories on the justification that Cygwin should only offer packages available for both architectures. And going forward, refuse new uploads if packages for both architectures aren’t provided promptly. There can be exceptions, as with the recent libsigsegv thing. I also thought I saw some talk about Perl currently being somewhat desynchronized at the moment. I’m not talking about such cases. The existing packages are maintained, and ownership of the solution for the missing packages is known. I think this is going to far, but it would be well within your prerogative. - We should probably consider to remove the mingw.org packages. All of them. They are hopelessly outdated and mingw-w64 does the same job better hands down. I can’t see why anyone would adopt those old abandoned packages. Not only do I have no objection to you nuking them, I think it would be an actual improvement, since it removes a point of confusion in the setup.exe package selection screen.
Re: missing 64bit ports
On Jul 15 16:24, Marco Atzeri wrote: Dear All, I spent a bit of time checking the real situation of the packages still missing as 64 bit port. After xdelta, bsdiff and iperf porting, without counting the few mingw ones, the duplicates we are down to ~44. Please see here the analysis : https://docs.google.com/spreadsheets/d/1Hn7Eaq6djEN9X0jS_AM8-DH_LvP43G9_DXnpTt09Asc/edit#gid=0 Feel free to insert comments on the cells. For what I found : - half of them are dead upstream so we can directly obsolete and don't worry anynore. - Few are Jary's scripts, so the only porting issue is Jary's time. - Very few have real porting issue The only one really interesting for me is Mathomatic and eventually catdoc if works with latest word documents. (of course I will port pure-ftpd) Thanks for looking into this. Two points: - Shall we remove all 32b-bit only orphaned packages for which we don't get a maintainer until, say, end of August? - We should probably consider to remove the mingw.org packages. All of them. They are hopelessly outdated and mingw-w64 does the same job better hands down. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpTFG2_nwsGB.pgp Description: PGP signature
SSH key for upload access
Name: Joel Johnson Package: iperf BEGIN SSH2 PUBLIC KEY B3NzaC1yc2EDAQABAAABAQDKriVs95VDFMOF8u2QeRNWKF/MamVoL9CTP20SUs IScF6up0c1U6TiNCgcPHXPw6QCPafaE73AoMIojKly5lr2N6LbspfcSiu4/USau/gAGLsS xyG7Zq/P8S3GmOVP5i/INjWJwB3AjIfIJx5JAUS49QC6iI+3BXxNczihIXUQmJoQDlKQnf 21epPiMXbscS7mEvYtV7IBOcS9M4eonlcDhGeVOJDOCIl0D8qkDLZdoEK90QA7VgHNQCKZ ZR2YNBycwPGucK90xJH5mHk1nlOInVWHe4OdVrKrXmBczU1kXsy74sOGm24r6uL4d8i3vV 2YQYl6WJU8byhEz6hf5srl END SSH2 PUBLIC KEY
Re: Perl 5.22.0
On 7/15/2015 1:34 AM, Achim Gratz wrote: Ken Brown writes: On 7/14/2015 3:51 PM, Achim Gratz wrote: biber This all set and uploaded to my release area. Thanks. Just to be sure, this build uses the system supplied Unicode modules or did you fatpack them? I've downgraded Unicode-Normalize to 1.17 just for Biber, so I'd be a bit bummed if the latter… :-) I used Unicode-Normalize-1.17 that I had built myself, using the cygport file attached here: https://cygwin.com/ml/cygwin-apps/2015-07/msg00036.html Ken
missing 64bit ports
Dear All, I spent a bit of time checking the real situation of the packages still missing as 64 bit port. After xdelta, bsdiff and iperf porting, without counting the few mingw ones, the duplicates we are down to ~44. Please see here the analysis : https://docs.google.com/spreadsheets/d/1Hn7Eaq6djEN9X0jS_AM8-DH_LvP43G9_DXnpTt09Asc/edit#gid=0 Feel free to insert comments on the cells. For what I found : - half of them are dead upstream so we can directly obsolete and don't worry anynore. - Few are Jary's scripts, so the only porting issue is Jary's time. - Very few have real porting issue The only one really interesting for me is Mathomatic and eventually catdoc if works with latest word documents. (of course I will port pure-ftpd) Regards Marco
