Re: SSH key for upload access
On Tue, Oct 29, 2013 at 03:20:08PM -0700, Peter A. Castro wrote: >Name: Peter A. Castro >Package: zsh >SSHkey: ssh-rsa >B3NzaC1yc2EDAQABAAAEAQDFdqRkJQbjhJeoggEzOym1belbKv1IIJn+gAzqufl7BwOYcvtZ9hrqZLIdD4QtZLMJbGDRYzEEeXJqCcOy3OJjJ3PUq4q0CuZwiVppNlytxLlim7/0Ex+6gPTHS02nae9aFlMqIx+VVLn10yPj4N/wp/oNKKocWGi7cac42VTmwn6UadhznvkWu0q/f7lJbw4VdpdQz4w/I03C2x5rmuWW9W34GNkhtFudRkUfSaj+WPp2oabsN0EgdUnhcHB8K57y3oXAXMmHDGaf1SVLmlewZVYrKngmW3U9E6yFE20K+Di6I6yAeBmcfyUa7XlRZMO6s4GkqJI7wPa0CzUDv7wkn+RRr7SpHfI6dbGasFdJqgplOwPwjg0F4UN7Pn57MzgHGa9RFIWp7hiieuwh21rmWVQCqi7cLvCDC+734m51XYi21KzZT9OWOZGQELkYOpE5PXmuaIPDWJUWompqqu6blgvRKs5VRjimy7dcjQIni25Hj0Ai/81HKoMAOtaTrbx2LCg6zHQ9vkGK42do3DC8W93QNfPeAOFI14uTx35NYJagAEltiCAZp0wRZMlxVzECpX0LEdKRhAzYpMtpH+nkLKrWHiGISJIlFXKVc3Jr1H8gNW7BBtA/rKzeAXJa0vetYuO9ErGpnFwxC7jQIKg+Im2Nut0zMwmiXzvwo1XM/1x5lCf9EUDxs42CkPIh8GgUA6gnrGk0SmGaByZfyT0IrTrXo9INM+tZzHOGQK2/3WQPPP/mbTj6GgHFPMT/MfnIrwA1/r2N3U2GAQN6k5/QbgRG9blQw1Ukd2X4TKJLITKTnYN1VsTgCrwcotS2fQ7y2yVdHmTBxcNdO7f3lGa18v0dvpZXx1HcF4wbSsx4AYVHKWUlyuvLMzamT85bxDlABu7KKZddJrSS660W3Ts7vwEutc9oWluStBRB06doIDlyk! > SS3PdogX+bB/W/MkNEN9HY2iMTxc+YyoLnH8Oi4Ibvv+/j8N4MJkHCxWPA/m3FkHdweXmls2IPmaLcFtdL2b53smH/cTVMq3eyg3yOEus5232fKOZYx0gMlyu8EsuSCkbYMk4QHDnlH2cwCoFNb5sXcYpkbuOO7YUzLWnGorzFdEzr3xxYjWjYessXrjPdkHRQbPibu30dP2XTzoM91f60KjI/7Ys3alPquofDuF9PFYOEy9YOQeREHGfhpIafRYybyhz0YSW1M5lsowIpzv/AM/rtGfvd97nIiRCIAR+ZBPOKmaJWBLKV7nJcYs5V/euqauvIJ9KPldgTpAbh+mZdqorBxZTFwTqdBloPCjXI2powYyWzIvVMKN2eNPakqdgM+J0LzJZw/jm4O4LDPMps+L3faKmJRmxFf9bdl > CygwinUploads Uploaded after modifying the software to treat a "!\n " as (apparently) something special. Anyone know if there is an RFC which specifies this?
SSH key for upload access
Name: Peter A. Castro Package: zsh SSHkey: ssh-rsa B3NzaC1yc2EDAQABAAAEAQDFdqRkJQbjhJeoggEzOym1belbKv1IIJn+gAzqufl7BwOYcvtZ9hrqZLIdD4QtZLMJbGDRYzEEeXJqCcOy3OJjJ3PUq4q0CuZwiVppNlytxLlim7/0Ex+6gPTHS02nae9aFlMqIx+VVLn10yPj4N/wp/oNKKocWGi7cac42VTmwn6UadhznvkWu0q/f7lJbw4VdpdQz4w/I03C2x5rmuWW9W34GNkhtFudRkUfSaj+WPp2oabsN0EgdUnhcHB8K57y3oXAXMmHDGaf1SVLmlewZVYrKngmW3U9E6yFE20K+Di6I6yAeBmcfyUa7XlRZMO6s4GkqJI7wPa0CzUDv7wkn+RRr7SpHfI6dbGasFdJqgplOwPwjg0F4UN7Pn57MzgHGa9RFIWp7hiieuwh21rmWVQCqi7cLvCDC+734m51XYi21KzZT9OWOZGQELkYOpE5PXmuaIPDWJUWompqqu6blgvRKs5VRjimy7dcjQIni25Hj0Ai/81HKoMAOtaTrbx2LCg6zHQ9vkGK42do3DC8W93QNfPeAOFI14uTx35NYJagAEltiCAZp0wRZMlxVzECpX0LEdKRhAzYpMtpH+nkLKrWHiGISJIlFXKVc3Jr1H8gNW7BBtA/rKzeAXJa0vetYuO9ErGpnFwxC7jQIKg+Im2Nut0zMwmiXzvwo1XM/1x5lCf9EUDxs42CkPIh8GgUA6gnrGk0SmGaByZfyT0IrTrXo9INM+tZzHOGQK2/3WQPPP/mbTj6GgHFPMT/MfnIrwA1/r2N3U2GAQN6k5/QbgRG9blQw1Ukd2X4TKJLITKTnYN1VsTgCrwcotS2fQ7y2yVdHmTBxcNdO7f3lGa18v0dvpZXx1HcF4wbSsx4AYVHKWUlyuvLMzamT85bxDlABu7KKZddJrSS660W3Ts7vwEutc9oWluStBRB06doIDlyk! SS3PdogX+bB/W/MkNEN9HY2iMTxc+YyoLnH8Oi4Ibvv+/j8N4MJkHCxWPA/m3FkHdweXmls2IPmaLcFtdL2b53smH/cTVMq3eyg3yOEus5232fKOZYx0gMlyu8EsuSCkbYMk4QHDnlH2cwCoFNb5sXcYpkbuOO7YUzLWnGorzFdEzr3xxYjWjYessXrjPdkHRQbPibu30dP2XTzoM91f60KjI/7Ys3alPquofDuF9PFYOEy9YOQeREHGfhpIafRYybyhz0YSW1M5lsowIpzv/AM/rtGfvd97nIiRCIAR+ZBPOKmaJWBLKV7nJcYs5V/euqauvIJ9KPldgTpAbh+mZdqorBxZTFwTqdBloPCjXI2powYyWzIvVMKN2eNPakqdgM+J0LzJZw/jm4O4LDPMps+L3faKmJRmxFf9bdl CygwinUploads
Re: SSH key for upload access
On Tue, Oct 29, 2013 at 09:36:44PM +0100, Konrad Borowski wrote: >Name: Konrad Borowski >Package: fish >SSHkey: ssh-rsa >B3NzaC1yc2EDAQABAAABAQC+7ew29lRE9nanr9fgceGZ4trqUhil+e2NpxlHzdct+60nn/Juz94hCrVRZdZbpsIgFdfwiKnsQWQ4kmXA7YE8VpfZp0NFTOikyQsakKJmYKr2VyBwdCi6EW8In91b5FjJZfh3G10WpXyKmy3Qim48jibAI8AhWJXSAZOPf45MyDBHVKkbwQnoKtH5BvYIt0R1ayPP4TM2Zu3DpIsNE4IjDFYlF0j5obWk6gahYjn3iiCHsxvuSU5JiK6z8l1z/ejqjJtIkH4Si6TPjOMf0Ufxb33HkRMZy6WIO6i8tDZiC1kKKDXQ9JC/FtPRtyR0pu+ZURsXPym6IOzb3rPQCDXF >glitchmr@pineapple This has been activated. You will be able to upload after your package is given the green light. cgf
Re: [ITP] fish shell 2.1.0
On Tue, Oct 29, 2013, at 06:57 PM, Christopher Faylor wrote: > > Since this is converging on a release of fish, don't forget to > provide upload information at some point: > > https://sourceware.org/cygwin-apps/package-upload.html I'm not sure. Does my package to be accepted first? Well, I assume that sending a thread to the group cannot hurt, can it? On Tue, Oct 29, 2013, at 06:53 PM, Corinna Vinschen wrote: > Do you want to try again? I guess I should, now that I went so far. Thanks for hint about LDFLAGS (I already tried changing CPPFLAGS, but failed because I forgot about LDFLAGS). The locations are the same as before. http://olive.undo.it/fish/32/fish-2.1.0-1.tar.xz http://olive.undo.it/fish/32/fish-2.1.0-1-src.tar.xz http://olive.undo.it/fish/32/setup.hint http://olive.undo.it/fish/32/fish-debuginfo/fish-debuginfo-2.1.0-1.tar.xz http://olive.undo.it/fish/32/fish-debuginfo/setup.hint http://olive.undo.it/fish/64/fish-2.1.0-1.tar.xz http://olive.undo.it/fish/64/fish-2.1.0-1-src.tar.xz http://olive.undo.it/fish/64/setup.hint http://olive.undo.it/fish/64/fish-debuginfo/fish-debuginfo-2.1.0-1.tar.xz http://olive.undo.it/fish/64/fish-debuginfo/setup.hint
Re: Deleting old versions of packages
On Tue, Oct 29, 2013 at 09:02:56PM +0100, Achim Gratz wrote: >Leave everything as is at the upload side, but add two cleanup passes on >the release directory; a first that deletes zero-sized files and a >second that removes empty directories. That way a maintainer can >"upload" a file that he wants to be deleted. Then upset will see the >cleaned up release directory and setup.ini won't have to specify tzhe >exact versions of files most of the time. I don't think I have to worry about empty directories. Those are easy to purge. I was trying to avoid the zero-length file scenario but maybe that's the best that can be done. The ordering would have to be right so that upset doesn't first reference a file and then delete it of course. In another discussion someone suggested a web-based form for deletion but if I was going to use that, I might as well use that method for upload too. I don't think I'm ready to scrap sftp now that this is implemented.
SSH key for upload access
Name: Konrad Borowski Package: fish SSHkey: ssh-rsa B3NzaC1yc2EDAQABAAABAQC+7ew29lRE9nanr9fgceGZ4trqUhil+e2NpxlHzdct+60nn/Juz94hCrVRZdZbpsIgFdfwiKnsQWQ4kmXA7YE8VpfZp0NFTOikyQsakKJmYKr2VyBwdCi6EW8In91b5FjJZfh3G10WpXyKmy3Qim48jibAI8AhWJXSAZOPf45MyDBHVKkbwQnoKtH5BvYIt0R1ayPP4TM2Zu3DpIsNE4IjDFYlF0j5obWk6gahYjn3iiCHsxvuSU5JiK6z8l1z/ejqjJtIkH4Si6TPjOMf0Ufxb33HkRMZy6WIO6i8tDZiC1kKKDXQ9JC/FtPRtyR0pu+ZURsXPym6IOzb3rPQCDXF glitchmr@pineapple
Re: Deleting old versions of packages
Christopher Faylor writes: > So your proposal is basically to do "I can't think of any way to do this > short of..." Well, it was you who was taking options from the table. > That's not a very inspired proposal given the fact that I already > mentioned the idea and implied that I wasn't keen on doing it that way. Sorry for failing to be inspired or inspiring or whatever it was you were expecting. Two proposals shot down, here's the third: Leave everything as is at the upload side, but add two cleanup passes on the release directory; a first that deletes zero-sized files and a second that removes empty directories. That way a maintainer can "upload" a file that he wants to be deleted. Then upset will see the cleaned up release directory and setup.ini won't have to specify tzhe exact versions of files most of the time. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [ITP] fish shell 2.1.0
Since this is converging on a release of fish, don't forget to provide upload information at some point: https://sourceware.org/cygwin-apps/package-upload.html
Re: new version of ocaml package (4.01.0-1)
On Oct 29 12:30, Yaakov (Cygwin/X) wrote: > On 2013-10-29 04:14, Corinna Vinschen wrote: > >On Oct 28 15:17, Yaakov (Cygwin/X) wrote: > >>I started working on porting flexdll-0.31, but the testsuite is > >>failing with "cannot relocate, target is too far" errors; IIUC the > >>issue has to do with our use of the medium code model. In the > > > >In theory, the usage of the medium code model was supposed to *fix* > >the issue. Can the testsuite problem be reduced into a STC which we > >can have a look at? > > I was referring to a FlexDLL error message, not a Cygwin one. The > former only supports relocs within the lower 32-bit range (even with > 64-bit binaries), so this will need to be fixed upstream first. Ouch. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpAxsCNZb35h.pgp Description: PGP signature
Re: [ITP] fish shell 2.1.0
On Oct 29 15:31, Konrad Borowski wrote:
> On Tue, Oct 29, 2013, at 10:12 AM, Corinna Vinschen wrote:
> > Hi Konrad,
> >
> > thanks for the new package ITP. Comments inline.
>
> Thanks for pointing out the problems. I believe problems you have found
> out are now fixed. I had problems with 32-bit Cygwin (to be exact, with
> compilation on it, the package itself appears to work), so I hope it's
What problems? Usually, if the cross-compiler built the package but
the native one doesn't, you have probably just forgotten to install some
of the required -devel packages or so.
> not a problem that the package contains cross compiled version with
> cygwin32-gcc-core dependency removed. As for links, I'm going to include
One problem with this approach is that you can't be sure that cygport
got all the right packages. For instance, libgcc1 is often required by
a 32 bit package while it isn't for the 64 bit package.
Oh, I just saw some other small problem (sorry!). You're using the
current cygport style, but file is called "fish-2.1.0-1.cygport", which
you should only do when using the old cygport style. These days, with
all the VERSION, RELEASE, etc information present *in* the file, just
call it "fish.cygport".
Hmm, your "DEPEND" requires libiconv-devel, but on 32 bit it's all in
the libiconv package. I changed that to
if [ "${ARCH}" = "x86_64" ]
then
DEPEND="autoconf gcc-g++ make libncursesw-devel libiconv-devel
gettext-devel"
else
DEPEND="autoconf gcc-g++ make libncursesw-devel libiconv gettext-devel"
fi
which avoids the warning.
[...more time passes...]
ncurses.h not found. That's because you must add the include and lib
paths to ncursesw to your build. I added
export CPPFLAGS="-I/usr/include/ncursesw"
export LDFLAGS="-L/usr/lib/ncursesw"
before calling
cygconf
cygmake
and now it builds.
Do you want to try again?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
pgpycqFrbbG2T.pgp
Description: PGP signature
Re: new version of ocaml package (4.01.0-1)
On 2013-10-29 04:14, Corinna Vinschen wrote: On Oct 28 15:17, Yaakov (Cygwin/X) wrote: I started working on porting flexdll-0.31, but the testsuite is failing with "cannot relocate, target is too far" errors; IIUC the issue has to do with our use of the medium code model. In the In theory, the usage of the medium code model was supposed to *fix* the issue. Can the testsuite problem be reduced into a STC which we can have a look at? I was referring to a FlexDLL error message, not a Cygwin one. The former only supports relocs within the lower 32-bit range (even with 64-bit binaries), so this will need to be fixed upstream first. Yaakov
Re: [ITP] fish shell 2.1.0
On Tue, Oct 29, 2013, at 10:12 AM, Corinna Vinschen wrote: > Hi Konrad, > > thanks for the new package ITP. Comments inline. Thanks for pointing out the problems. I believe problems you have found out are now fixed. I had problems with 32-bit Cygwin (to be exact, with compilation on it, the package itself appears to work), so I hope it's not a problem that the package contains cross compiled version with cygwin32-gcc-core dependency removed. As for links, I'm going to include them now. I don't know if the format is correct, but I believe it can be fixed with a simple regular expression if it's not. http://olive.undo.it/fish/32/fish-2.1.0-1.tar.xz http://olive.undo.it/fish/32/fish-2.1.0-1-src.tar.xz http://olive.undo.it/fish/32/setup.hint http://olive.undo.it/fish/32/fish-debuginfo/fish-debuginfo-2.1.0-1.tar.xz http://olive.undo.it/fish/32/fish-debuginfo/setup.hint http://olive.undo.it/fish/64/fish-2.1.0-1.tar.xz http://olive.undo.it/fish/64/fish-2.1.0-1-src.tar.xz http://olive.undo.it/fish/64/setup.hint http://olive.undo.it/fish/64/fish-debuginfo/fish-debuginfo-2.1.0-1.tar.xz http://olive.undo.it/fish/64/fish-debuginfo/setup.hint
Re: new version of ocaml package (4.01.0-1)
On Oct 28 15:17, Yaakov (Cygwin/X) wrote: > On 2013-10-25 04:25, Damien Doligez wrote: > >So, here it is: I have a new version of the OCaml package (4.01.0-1), > >both for 32 and 64 bits. I have uploaded the files to cygwin.com, > >but I haven't put the !ready files yet. > > > >Both packages are marked as "test": > > > >- For 32 bits, because I don't want to hurt you again. I'm guessing > >that a "test" version of the package will let you recompile the > >libraries in Ports, and then when you tell me you're ready, I'll make > >a "curr" version. > > Ack, I'll let you know when I'm finished the rebuild (but see below). > > >- For 64 bits, because we don't have Flexdll yet, so dynlink is not > >supported, which means that many OCaml programs won't work. I've > >already prodded the Flexdll upstream. I'm publishing this because > >it's the best we can have on 64-bit for the moment. > > I started working on porting flexdll-0.31, but the testsuite is > failing with "cannot relocate, target is too far" errors; IIUC the > issue has to do with our use of the medium code model. In the In theory, the usage of the medium code model was supposed to *fix* the issue. Can the testsuite problem be reduced into a STC which we can have a look at? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp1eCU4zbHoZ.pgp Description: PGP signature
Re: [ITP] fish shell 2.1.0
Hi Konrad, thanks for the new package ITP. Comments inline. On Oct 28 19:31, Konrad Borowski wrote: > Hello. I would like to add fish shell to Cygwin. It's already available > in Ubuntu and Debian. The 2.1.0 adds support for Cygwin, so I assume > it's good occasion to actually send the package. > > http://packages.debian.org/search?keywords=fish > http://packages.ubuntu.com/search?keywords=fish > > This is my first time making package using cygport, so feel free to let > me know in case something is wrong. > > All files are available at the following location (in both 32-bit and > 64-bit versions, 32-bit was cross compiled, as I don't have 32-bit > Windows). You can install a 32 bit version of Cygwin nevertheless, that's what we all did before the 64 bit Cygwin version existed. That allows users of 64 bit machines to build both, 32 and 64 bit versions natively. > http://olive.undo.it/fish/ Would you mind to give us lazy people the full paths to the files in a way which is easy to use with wget? Thanks. > The setup.hint is identical in both versions and looks like this. > > category: Shells > requires: libgcc1 libiconv2 libintl8 libncursesw10 libstdc++6 python > libgcc1 libiconv2 libintl8 libncursesw10 libstdc++6 python libncursesw > libiconv util-linux coreutils The requires is wrong. It contains a couple of entries twice. The problem is that you added REQUIRES="libgcc1 libiconv2 libintl8 libncursesw10 libstdc++6 python \ libncursesw libiconv util-linux coreutils" to your cygport file. REQUIRES should only contain requirements which are not added automatically by cygport. There's also no such package called libncursesw or libiconv. Something like this seems more appropriate: REQUIRES="util-linux coreutils" Your setup.hint files are not identical, btw. Your setup.hint file for the 32 bit version contains a dependency to cygwin32-gcc-core. This is a result of the cross compile and should get manually removed. Other than that, packaging looks good to me. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpj7m5zv4YsA.pgp Description: PGP signature
