Re: ITA: tnef -- Tool to unpack MIME application/ms-tnef attachments
On Jun 15 12:57, Jari Aalto wrote: Adopting tnef (orpahaned, Jonathan C. Allen): https://cygwin.com/cygwin-pkg-maint I have new 1.4.9 ready for both x86 and x86_64. Let me know when I can upload. Please go ahead with this one and rsync. Thanks a lot for taking over! Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpP4jqUToGBV.pgp Description: PGP signature
Re: ITP: splitpatch -- split the patch up into files or hunks
On Jun 16 11:29, Jari Aalto wrote: wget --recursive --no-host-directories --cut-dirs=3 \ http://cante.net/~jaalto/tmp/cygwin/splitpatch/setup.hint \ http://cante.net/~jaalto/tmp/cygwin/splitpatch/splitpatch-0.0+20131223+gitb13d810-1-src.tar.xz \ http://cante.net/~jaalto/tmp/cygwin/splitpatch/splitpatch-0.0+20131223+gitb13d810-1.tar.xz GTG. Please upload. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgphlfqtBq6ZF.pgp Description: PGP signature
Re: [ITP] Regina-REXX-3.8-1
Hi Mark, On Jun 9 18:45, Mark Hessling wrote: Regina-REXX is an implementation of ANSI Standard Rexx available on many platforms. Regina-REXX is found on a number of Linux platforms, including Debian: http://packages.qa.debian.org/r/regina-rexx.html [...] Thanks for providing this package. I had a look and I have a few nits: - The DLLs in /usr/bin are not following the naming convention for Cygwin DLLs. They should start with the cyg prefix. - The files /usr/bin/rxtest1.dll and /usr/bin/rxtest2.dll look like stray files, which are not supposed to be distributed. They are not present in the Debian distro. - The Debian package is split into three subpackages, regina-rexx, libregina3, and libregina-dev. Apart from the fact that the devel package in Cygwin should be called libregina-devel, this layout seems to make a lot of sense. Wouldn't it be better to do this for the Cygwin package as well? - The package-specific directories are called Regina-REXX, while on debian they are lowercase only, regina-rexx. It's very much a matter of taste, but it might be nice to do this for Cygwin as well. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpB9CdtdKH48.pgp Description: PGP signature
Re: [ITP] Regina-REXX-3.8-1
Hi Corrina, Thanks for reviewing the proposal. Comments inline. Cheers, Mark On 17/06/14 18:12, Corinna Vinschen wrote: Hi Mark, On Jun 9 18:45, Mark Hessling wrote: Regina-REXX is an implementation of ANSI Standard Rexx available on many platforms. Regina-REXX is found on a number of Linux platforms, including Debian: http://packages.qa.debian.org/r/regina-rexx.html [...] Thanks for providing this package. I had a look and I have a few nits: - The DLLs in /usr/bin are not following the naming convention for Cygwin DLLs. They should start with the cyg prefix. Will fix. - The files /usr/bin/rxtest1.dll and /usr/bin/rxtest2.dll look like stray files, which are not supposed to be distributed. They are not present in the Debian distro. They are test extensions that go with the dynfunc.rexx demo program. I can remove them and the associated demo program. - The Debian package is split into three subpackages, regina-rexx, libregina3, and libregina-dev. Apart from the fact that the devel package in Cygwin should be called libregina-devel, this layout seems to make a lot of sense. Wouldn't it be better to do this for the Cygwin package as well? I was trying to make things simple for my first Cygwin package :-) - The package-specific directories are called Regina-REXX, while on debian they are lowercase only, regina-rexx. It's very much a matter of taste, but it might be nice to do this for Cygwin as well. The Regina-REXX name was based on the RPM packaging name that was a hangover from older RedHat and Fedora releases. I'll split the build into separate packages as for Debian and follow Debian's all lowercase naming as well. Thanks, Corinna -- * Mark Hessling, m...@rexx.org http://www.rexx.org/ * Author of THE, a Free XEDIT/KEDIT editor and, Rexx/SQL, Rexx/CURL, etc. * Maintainer of Regina Rexx interpreter * Use Rexx? join the Rexx Language Association: http://www.rexxla.org/
Re: [ITP] Regina-REXX-3.8-1
On Jun 17 21:50, Mark Hessling wrote: Hi Corrina, s/rrin/rinn/ Thanks for reviewing the proposal. Comments inline. Cheers, Mark On 17/06/14 18:12, Corinna Vinschen wrote: Hi Mark, On Jun 9 18:45, Mark Hessling wrote: Regina-REXX is an implementation of ANSI Standard Rexx available on many platforms. Regina-REXX is found on a number of Linux platforms, including Debian: http://packages.qa.debian.org/r/regina-rexx.html [...] Thanks for providing this package. I had a look and I have a few nits: - The DLLs in /usr/bin are not following the naming convention for Cygwin DLLs. They should start with the cyg prefix. Will fix. - The files /usr/bin/rxtest1.dll and /usr/bin/rxtest2.dll look like stray files, which are not supposed to be distributed. They are not present in the Debian distro. They are test extensions that go with the dynfunc.rexx demo program. I can remove them and the associated demo program. - The Debian package is split into three subpackages, regina-rexx, libregina3, and libregina-dev. Apart from the fact that the devel package in Cygwin should be called libregina-devel, this layout seems to make a lot of sense. Wouldn't it be better to do this for the Cygwin package as well? I was trying to make things simple for my first Cygwin package :-) It's not very complicated to define subpackages in the cygport file, in fact. You just define the names of the packages in the variable PKG_NAMES, and then you can define the per-package information like this: PKG_NAMES=foo bar foo_CATEGORY=...# categories of package foo foo_CONTENTS=...# list of files for package foo (glob pattern!) foo_SUMMARY=... # Summary for package foo foo_DESCRIPTION=... # Description for package foo bar_CATEGORY=...# categories of package bar bar_CONTENTS=...# list of files for package bar (glob pattern!) bar_SUMMARY=... # Summary for package bar bar_DESCRIPTION=... # Description for package bar You just have to make sure to catch all installed files in the CONTENTS variables. Files which get installed but are supposed to be not packed can be removed in the src_install stage. - The package-specific directories are called Regina-REXX, while on debian they are lowercase only, regina-rexx. It's very much a matter of taste, but it might be nice to do this for Cygwin as well. The Regina-REXX name was based on the RPM packaging name that was a hangover from older RedHat and Fedora releases. I'll split the build into separate packages as for Debian and follow Debian's all lowercase naming as well. Just take the path you like better. As I said, it's just a matter of taste anyway. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpjBwfJezm2N.pgp Description: PGP signature
Re: [ITP] Regina-REXX-3.8-1
On 17/06/14 22:27, Corinna Vinschen wrote: On Jun 17 21:50, Mark Hessling wrote: Hi Corrina, s/rrin/rinn/ Oops, sorry; it's late here! Will follow your advice below and build new packages in the next few days. Cheers, Mark Thanks for reviewing the proposal. Comments inline. Cheers, Mark On 17/06/14 18:12, Corinna Vinschen wrote: Hi Mark, On Jun 9 18:45, Mark Hessling wrote: Regina-REXX is an implementation of ANSI Standard Rexx available on many platforms. Regina-REXX is found on a number of Linux platforms, including Debian: http://packages.qa.debian.org/r/regina-rexx.html [...] Thanks for providing this package. I had a look and I have a few nits: - The DLLs in /usr/bin are not following the naming convention for Cygwin DLLs. They should start with the cyg prefix. Will fix. - The files /usr/bin/rxtest1.dll and /usr/bin/rxtest2.dll look like stray files, which are not supposed to be distributed. They are not present in the Debian distro. They are test extensions that go with the dynfunc.rexx demo program. I can remove them and the associated demo program. - The Debian package is split into three subpackages, regina-rexx, libregina3, and libregina-dev. Apart from the fact that the devel package in Cygwin should be called libregina-devel, this layout seems to make a lot of sense. Wouldn't it be better to do this for the Cygwin package as well? I was trying to make things simple for my first Cygwin package :-) It's not very complicated to define subpackages in the cygport file, in fact. You just define the names of the packages in the variable PKG_NAMES, and then you can define the per-package information like this: PKG_NAMES=foo bar foo_CATEGORY=... # categories of package foo foo_CONTENTS=... # list of files for package foo (glob pattern!) foo_SUMMARY=... # Summary for package foo foo_DESCRIPTION=... # Description for package foo bar_CATEGORY=... # categories of package bar bar_CONTENTS=... # list of files for package bar (glob pattern!) bar_SUMMARY=... # Summary for package bar bar_DESCRIPTION=... # Description for package bar You just have to make sure to catch all installed files in the CONTENTS variables. Files which get installed but are supposed to be not packed can be removed in the src_install stage. - The package-specific directories are called Regina-REXX, while on debian they are lowercase only, regina-rexx. It's very much a matter of taste, but it might be nice to do this for Cygwin as well. The Regina-REXX name was based on the RPM packaging name that was a hangover from older RedHat and Fedora releases. I'll split the build into separate packages as for Debian and follow Debian's all lowercase naming as well. Just take the path you like better. As I said, it's just a matter of taste anyway. Thanks, Corinna -- * Mark Hessling, m...@rexx.org http://www.rexx.org/ * Author of THE, a Free XEDIT/KEDIT editor and, Rexx/SQL, Rexx/CURL, etc. * Maintainer of Regina Rexx interpreter * Use Rexx? join the Rexx Language Association: http://www.rexxla.org/
Re: SSH key for upload access
On Tue, Jun 10, 2014 at 07:21:30PM +0200, Thomas Wolff wrote: Name: Thomas Wolff Package: mined BEGIN SSH2 PUBLIC KEY Comment: 2048-bit RSA, converted from OpenSSH by root@MyBookLive B3NzaC1yc2EBIwAAAQEAwMSnVCjNhyiGNhBC/+uPheB4BgG+n7RVmVMiBUJkIy 19fDeLc+0bWgzKLEXl00e0KytGgz6gS3sbDYfv8Ukh9eAnQ9iev31fZmb2UpmXtJCpQHrK tT3kT3FME+sDX3zYCnpXyOGUP0v0DwUSbRdsMyzH3YKw8XJ60b2gi5PX1wTENR0L4fnXUr +3Wya4jXUR5d5Az7/Yn9HrBc68qogHn+TwBFZUhXMtlcThKoRBA7160Td7sUeTc1FoqvlD saneqqnZCgX0qhWZp9V+eNHMnMkNoSwhdDtM+7IRI0doTI7BlzLbiZp1mZOUNWDtdaZwIn Jbtk5T/FDLw+VIQQWmcQ== END SSH2 PUBLIC KEY Activated.
Re: SSH key for upload access
On Fri, Jun 06, 2014 at 08:07:16PM -0400, Chris J. Breisch wrote: Name: Chris J. Breisch Package: man-db BEGIN SSH2 PUBLIC KEY Comment: 4096-bit RSA, converted by Chris@Chris-PC from OpenSSH B3NzaC1yc2EDAQABAAACAQCzGcbs64ShqbQOi1hpyrCVay5NAsV+DG+39LnIlv tiP07M8+92jo4UQUcXXLhXevoktmm6xPbzqote/TcNXUmjh7ZRCs5FW16X/++CqxKK3nMu lRrMoAVZ0+T8rNZ1FNFq11BsF5irJqtU3NetCOdo0ihCUCYxzjSWctolq98vLwIyb2VUnX BPPUH4Ez+1ZAyUIa7ppSMWDeny55sovGGqODbLrYbhhfiP5ubFwNqMr73BU8xN4W2tXkUl VBA8uIwdEMwsSzD1rfJ1BCLsgVc2Rh2CWSvcA4Ryj5ycD+Rn2r20ttbxK598JfYD5Lnw2H HYAZRmq16kmN1K6/WczBrcWAFIohlHVMIhr6LA7MSXXqPO7en/EGQ+XaIoAZdN3KjHFhxM FJGBRhmdrSSno9s9BsOKYABN1K08oLV0jOYzop/4dByVubkByaXJSzgyGD/ckISlndYkIz Nw1KkvP3Ta0iPiyxQpmHMtkVDEG8BDassr9MhH7WSgZcN1hKE9BmXgz36tepLP5jxKWlxb DsomiCokufHIJGJiuNiIuNwPDEoB8XeNCzKYEXnEFT03sGHrmjTc2236rM3lvkw+MfuGGo VmIhzcasQPlSdG64LZhOaX8pTHiGG5pHDK7NRtZZuFrhE5dFUV5LBiFFCP4lSXYMQ90O3k Me/IFsdBwJIqBQ== END SSH2 PUBLIC KEY Activated.
