On 2/3/2015 4:17 AM, Corinna Vinschen wrote:
On Feb 2 10:46, Ken Brown wrote:
I've now begun working on the 64-bit build. I found a few minor things I
had to change, and the build was pretty far along, when I apparently hit a
gcc bug:
[...]
Oh, that's too bad. I hope somebody fr
On 2/11/2015 7:50 PM, Yaakov Selkowitz wrote:
On Thu, 2015-01-15 at 16:46 -0500, Ken Brown wrote:
On 1/5/2015 12:52 PM, Achim Gratz wrote:
Ken Brown writes:
Do you have an opinion about that? I suggested /etc/texmf/postinstall
or /var/lib/texmf/postinstall, but Achim had other ideas. The
On 2/11/2015 11:10 PM, Ken Brown wrote:
On 2/11/2015 7:50 PM, Yaakov Selkowitz wrote:
On Thu, 2015-01-15 at 16:46 -0500, Ken Brown wrote:
On 1/5/2015 12:52 PM, Achim Gratz wrote:
Ken Brown writes:
Do you have an opinion about that? I suggested /etc/texmf/postinstall
or /var/lib/texmf
On 2/10/2015 11:14 PM, Yaakov Selkowitz wrote:
clispORPHANED (Reini Urban)
As I mentioned in the "libopenssl098" thread, I have a build of clisp-2.48
(32-bit only for now) that seems to work and that links against current versions
of all libraries. Sho
On 2/15/2015 1:40 PM, Marco Atzeri wrote:
On 2/15/2015 7:29 PM, Ken Brown wrote:
On 2/10/2015 11:14 PM, Yaakov Selkowitz wrote:
clispORPHANED (Reini Urban)
As I mentioned in the "libopenssl098" thread, I have a build of
clisp-2.48 (32-bit on
This builds easily on both arches, using essentially the same cygport
file as Yaakov used for icu-51.2-1 on x86_64. I tested it by rebuilding
the TeX Live binaries against libicu54.
D=http://sanibeltranquility.com/cygwin/x86/release/icu
wget -x -nH --cut-dirs=1 \
${D}/icu-54.1-1-src.tar.xz \
$
The x86 build is the same as Reini's build of 2.4.0-2, except for (a) a
tweak to allow it to build with the current gcc and (b) a minor
packaging change: The package provides some example C/C++ files in
/usr/share/doc/fcgi/examples, and the build process compiles these.
Reini put the correspond
I've been trying to adopt Reini's packages that have not yet been ported to
64-bit Cygwin and that have some connection to packages I already maintain. The
next one on my list is ffcall.
Unfortunately, the source has a lot of assembler code in it, so I will almost
certainly need help from som
On 2/18/2015 2:28 PM, Yaakov Selkowitz wrote:
On Wed, 2015-02-18 at 13:49 -0500, Ken Brown wrote:
I've been trying to adopt Reini's packages that have not yet been ported to
64-bit Cygwin and that have some connection to packages I already maintain. The
next one on my list is ffc
On 2/18/2015 3:08 PM, Corinna Vinschen wrote:
On Feb 18 13:28, Yaakov Selkowitz wrote:
On Wed, 2015-02-18 at 13:49 -0500, Ken Brown wrote:
I've been trying to adopt Reini's packages that have not yet been ported to
64-bit Cygwin and that have some connection to packages I alread
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did it for Cygwin with help
from Kai Tietz.
The main difference to Linux you have to look out for is the different
calling
On 2/19/2015 11:46 AM, Ken Brown wrote:
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did it for Cygwin with help
from Kai Tietz.
The main difference to Linux you have to
On 2/19/2015 12:44 PM, Corinna Vinschen wrote:
On Feb 19 12:19, Ken Brown wrote:
On 2/19/2015 11:46 AM, Ken Brown wrote:
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did
On 2/19/2015 2:46 PM, Reini Urban wrote:
On 02/19/2015 06:19 PM, Ken Brown wrote:
On 2/19/2015 11:46 AM, Ken Brown wrote:
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did
On 2/19/2015 2:46 PM, Reini Urban wrote:
And the deal with the latest clisp 2.49 was that modules can be dynaloaded.
If the gnulib steps would work. I never did for me. And I fixed most of
the other
module compilation problems before.
But I just discovered that clisp-2.49 builds fine with the c
On 2/21/2015 5:03 AM, David Billinghurst wrote:
On 20/02/2015 9:30 AM, Ken Brown wrote:
In that case, I think I'll go ahead and release what I have and see if it's of
use to anyone.
Ken
I have built and tested maxima-5.43.1 with your clisp release on cygwin64.
Perfect test res
On 2/21/2015 7:59 AM, Reini Urban wrote:
On 02/21/2015 04:44 AM, Ken Brown wrote:
On 2/19/2015 2:46 PM, Reini Urban wrote:
And the deal with the latest clisp 2.49 was that modules can be
dynaloaded.
If the gnulib steps would work. I never did for me. And I fixed most of
the other
module
This is needed for the upcoming clisp-2.49. [*]
D=http://sanibeltranquility.com/cygwin/x86/release/svm
wget -x -nH --cut-dirs=1 \
${D}/svm-3.20-1-src.tar.xz \
${D}/svm-3.20-1.tar.xz \
${D}/setup.hint \
${D}/svm-debuginfo/svm-debuginfo-3.20-1.tar.xz \
${D}/svm-debuginfo/setup.hint \
${D}/libsvm2/l
Reini,
Do you plan to resume development of the gdi module? If not, I think
clisp-gdi will have to be dropped from the distribution the next time
there's a new release of clisp. gdi no longer compiles with the current
clisp development trunk, and I don't have the interest or the expertise
t
I've succeeded in making dynamic loading of modules work in clisp on
Cygwin, and I'll be issuing a new release soon.
My work was based on the tip of the upstream Mercurial repository, which
shows a version number of 2.49+ and is at revision 15623. So I was
thinking of using 2.49+hg15623 as th
On 3/11/2015 6:20 PM, Yaakov Selkowitz wrote:
On Wed, 2015-03-11 at 17:35 -0400, Ken Brown wrote:
I've succeeded in making dynamic loading of modules work in clisp on
Cygwin, and I'll be issuing a new release soon.
Yeah!
My work was based on the tip of the upstream Mercurial
On 3/12/2015 2:52 AM, Achim Gratz wrote:
To the maintainers of other Perl distributions: if there's any you want
to part with, please let me know and I'll most likely adopt them.
Please take all of mine.
Thanks.
Ken
On 3/12/2015 7:00 PM, Achim Gratz wrote:
Achim Gratz writes:
Ken, would you still know if the Log-Log4Perl and Text-BibTeX tests were
clean previously? I'm getting what looks like an encoding problem from
Text-BibTeX and an offset in some file sizes(?) for Log-Log4Perl.
No, sorry. I don't ev
On 3/12/2015 2:43 AM, Achim Gratz wrote:
Yaakov Selkowitz writes:
My work was based on the tip of the upstream Mercurial repository, which
shows a version number of 2.49+ and is at revision 15623. So I was
thinking of using 2.49+hg15623 as the version number. Will upset be
happy with that? Or
On 3/15/2015 12:40 PM, Achim Gratz wrote:
Ken Brown writes:
My work was based on the tip of the upstream Mercurial repository,
which shows a version number of 2.49+ and is at revision 15623. So I
was thinking of using 2.49+hg15623 as the version number. Will upset
be happy with that? Or is
On 3/15/2015 2:19 PM, Yaakov Selkowitz wrote:
On Sun, 2015-03-15 at 13:37 -0400, Ken Brown wrote:
This sounds like a packaging error on my part. First of all, lisp.dll
is new with the latest clisp; it was part of my solution to the dynamic
loading problem. But from what you say, it sounds
On 3/15/2015 3:14 PM, Achim Gratz wrote:
Ken Brown writes:
I think my new proposal (with /usr/bin/cyglisp.dll and
/usr/lib/liblisp.dll.a) will work better. I don't know whether it's
best to split off libclisp and clisp-devel subpackages. Fedora has a
separate clisp-devel packa
On 3/16/2015 3:41 PM, Achim Gratz wrote:
Achim Gratz writes:
The loading of memory images via clisp works, so I'll pull the
maxima-exec-clisp package until we get to the bottom of this.
Hmm. Scratch that, I think I got the maxima.exe (dumped image) to work.
Let's see if it survives installati
On 3/16/2015 4:07 PM, Achim Gratz wrote:
Yaakov Selkowitz writes:
Is there an issue with stripping clisp executables?
Yes, with the executable dumps.
Is there a magic
number we can use to detect these automatically?
File identifies them as plain executables. CLisp knows which runtime
they
On 3/17/2015 3:20 PM, Achim Gratz wrote:
Ken Brown writes:
Great. Thanks for testing. There's probably no reason for me to
upload a new clisp package right now (unless it would help you). But
I'll give you a heads up when I'm ready to do that.
I've now drilled to the
On 3/17/2015 5:40 PM, Yaakov Selkowitz wrote:
On Tue, 2015-03-17 at 17:15 -0400, Ken Brown wrote:
On 3/17/2015 3:20 PM, Achim Gratz wrote:
Ken Brown writes:
Great. Thanks for testing. There's probably no reason for me to
upload a new clisp package right now (unless it would help you).
On 3/17/2015 8:17 PM, Jon TURNEY wrote:
On 17/03/2015 22:40, Ken Brown wrote:
Yes. But that makes me wonder if I made things too complicated and
could have avoided building lisp.dll. The native Windows build of clisp
creates a lisp.def file, containing the symbols of lisp.exe, and it just
On 3/17/2015 8:54 PM, Ken Brown wrote:
On 3/17/2015 8:17 PM, Jon TURNEY wrote:
On 17/03/2015 22:40, Ken Brown wrote:
Yes. But that makes me wonder if I made things too complicated and
could have avoided building lisp.dll. The native Windows build of clisp
creates a lisp.def file, containing
On 3/17/2015 9:47 PM, Yaakov Selkowitz wrote:
A .def file can be used for two purposes:
1) to specify which symbols to export in a DLL/EXE, in place of
dllexport or -Wl,--export-all-symbols (EXPORTS)
2) to resolve symbols by declaring them in other DLL/EXE(s), in place of
a .dll.a (IMPORTS)
T
On 3/22/2015 4:50 PM, Achim Gratz wrote:
Ken Brown writes:
And indeed it does. I've still got a couple of things to clean up,
but I expect to upload a new clisp soon that no longer uses lisp.dll.
I hope that will solve the Maxima problem
It doesn't… Instead of lisp.dll it no
On 3/22/2015 6:33 PM, Ken Brown wrote:
On 3/22/2015 4:50 PM, Achim Gratz wrote:
Ken Brown writes:
And indeed it does. I've still got a couple of things to clean up,
but I expect to upload a new clisp soon that no longer uses lisp.dll.
I hope that will solve the Maxima problem
It do
On 3/23/2015 2:45 AM, Achim Gratz wrote:
As I said, I've revoked the maxima-exec-clisp package for now, so
whether you either come up with a solution for that problem or conclude
that dumping of executables isn't going to be supported on Cygwin, I'm
fine.
OK, that's good. I'd still like to get
Hi Achim,
I'm wondering what your plans are for Perl 5.22, which I think is due to
be released in a couple weeks. I'm expecting to release TeX Live 2015
in mid June, and it would be nice to be able to update Biber to the
current version at the same time.
Do you think you will have released
Now that we've moved from cygwin-1.7.x to cygwin-2.x.y, line 681 of
pkg_pkg.cygpart no longer filters out "cygwin". Presumably you just
want to replace "cygwin-1" by "cygwin-2", unless there's a reason to
allow for the possibility that maintainers are building without having
the latest version
On 5/8/2015 7:16 PM, Yaakov Selkowitz wrote:
On Wed, 2015-05-06 at 14:33 -0400, Ken Brown wrote:
Now that we've moved from cygwin-1.7.x to cygwin-2.x.y, line 681 of
pkg_pkg.cygpart no longer filters out "cygwin". Presumably you just
want to replace "cygwin-1" by &qu
On 5/20/2015 3:39 PM, Achim Gratz wrote:
Ken Brown writes:
I'm wondering what your plans are for Perl 5.22, which I think is due
to be released in a couple weeks.
I've just built perl-5.33-RC1. I need to do some changes to actually be
able to package the result and then of cour
On 5/24/2015 4:02 PM, Achim Gratz wrote:
I've built perl-5.22.0-RC2 and bootstrapped the Perl distributions for
Cygwin (well, most of them -- I will send another ITA for some
additional ones I've hat to build later). It doesn't make much sense to
try a test release on sourceware, so I've upload
On 5/25/2015 3:00 AM, Achim Gratz wrote:
Ken Brown writes:
The latest version of Biber requires autovivification, XML::Writer,
and Text::Roman. And Test::Difference is required for running the
tests. Can you add those?
I have the first two already from my last look at Biber… OK, the rest is
On 5/25/2015 9:12 AM, Ken Brown wrote:
On 5/25/2015 3:00 AM, Achim Gratz wrote:
I don't know if it's still possible to build on 5.22, depending on where
in the deprecation cycle we are with that function. But the earlier
module versions have been pulled from CPAN anyway and on
On 5/25/2015 2:31 PM, Achim Gratz wrote:
Ken Brown writes:
biber-1.8 seems fine with perl-5.22.0. Since I may be out of town
with poor internet access when you're ready for the transition, I went
ahead and uploaded it to sourceware (x86_64 only), along with a new
release of texlive-colle
On 5/28/2015 2:15 PM, Yaakov Selkowitz wrote:
Ken,
An insecure usage of /tmp has been reported in mktexlsr:
https://bugzilla.redhat.com/show_bug.cgi?id=1181167
http://pkgs.fedoraproject.org/cgit/texlive.git/plain/texlive-bz979176.patch
Thanks for the heads-up. I'm on vacation, but I'll look
On 5/28/2015 2:14 PM, Yaakov Selkowitz wrote:
Ken,
See $SUBJECT. emacs-auctex's copy is in texmf-site and texlive's is in
texmf-dist, so while they don't physically clobber each other I suspect
we only want one of them; I'm just not sure which.
I agree. I think emacs-auctex should be the pro
On 5/28/2015 2:15 PM, Yaakov Selkowitz wrote:
Ken,
An insecure usage of /tmp has been reported in mktexlsr:
https://bugzilla.redhat.com/show_bug.cgi?id=1181167
http://pkgs.fedoraproject.org/cgit/texlive.git/plain/texlive-bz979176.patch
This was discussed upstream starting at
http://tug.org
The syntax for 'fmtutil' has changed in TeX Live 2015. The attached
patch accommodates that change.
Ken
From b2b0d8aa5d773c3da340e1466d280e0507692072 Mon Sep 17 00:00:00 2001
From: Ken Brown
Date: Tue, 16 Jun 2015 09:47:53 -0400
Subject: [PATCH] texlive: fix calls to fmtutil for TeX
On 6/16/2015 7:52 PM, Yaakov Selkowitz wrote:
On Tue, 2015-06-16 at 10:24 -0400, Ken Brown wrote:
The syntax for 'fmtutil' has changed in TeX Live 2015. The attached
patch accommodates that change.
Just curious, what changed? AFAICS the fmtutil-sys in 20140523-2 also
accepts --by
According to the documentation of SSH_KEY, "You'll need to set this if
your private key isn't already loaded into a running ssh-agent(1), and
it doesn't have one of the expected file names such as ~/.ssh/id_rsa."
But I don't see in the source that cygport checks for one of the
expected file nam
On 6/27/2015 3:18 PM, Andrew Schulman wrote:
According to the documentation of SSH_KEY, "You'll need to set this if
your private key isn't already loaded into a running ssh-agent(1), and
it doesn't have one of the expected file names such as ~/.ssh/id_rsa."
But I don't see in the source that cygp
On 7/5/2015 2:02 AM, Achim Gratz wrote:
David Rothenberger writes:
I've rebuilt the package as curr and not test and uploaded to my area. I
did not create the !ready file.
Is this the right way to do this? Or should I release a test package?
As long as you remember what you did it's going to
On 7/5/2015 2:31 PM, Yaakov Selkowitz wrote:
On Sun, 2015-07-05 at 09:26 -0400, Ken Brown wrote:
On 7/5/2015 2:02 AM, Achim Gratz wrote:
David Rothenberger writes:
I've rebuilt the package as curr and not test and uploaded to my area. I
did not create the !ready file.
Is this the righ
On 5/25/2015 2:45 PM, Ken Brown wrote:
BTW, I contacted Philip Kime, the author of Biber, about
Unicode::Normalize. He told me that version 1.18 is unusably slow.
Here's a bug report he filed about it:
https://rt.cpan.org/Public/Bug/Display.html?id=102766
I think he's planning to
On 7/10/2015 3:33 PM, Yaakov Selkowitz wrote:
On Fri, 2015-07-10 at 14:30 -0400, Ken Brown wrote:
On 5/25/2015 2:45 PM, Ken Brown wrote:
BTW, I contacted Philip Kime, the author of Biber, about
Unicode::Normalize. He told me that version 1.18 is unusably slow.
Here's a bug report he
On 7/14/2015 3:51 PM, Achim Gratz wrote:
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):
biber
This all set and uploaded to my release area. I'll just have to either change
the setup
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-Norm
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
On 7/17/2015 3:32 AM, Corinna Vinschen wrote:
On Jul 15 16:12, Ken Brown wrote:
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
n 3 is wasted effort.
How many applications would need to be rebuilt? I see:
diffutils [me]
m4 [me]
clisp [Ken Brown]
I was planning to rebuild 64-bit clisp anyway, to take advantage of the
new libsigsegv, so I can rebuild on 32-bit also. But there's no big
rush, so I'll probably wai
On 7/20/2015 7:20 AM, Corinna Vinschen wrote:
On Jul 19 10:37, Corinna Vinschen wrote:
On Jul 18 14:41, Eric Blake wrote:
On 07/18/2015 02:11 PM, Corinna Vinschen wrote:
OTOH, calling certain Cygwin functions might require lots of stack.
E.g. open/read/write/close requires more than 2K stack,
On 7/20/2015 9:03 AM, Ken Brown wrote:
On 7/20/2015 7:20 AM, Corinna Vinschen wrote:
I uploaded snapshots as well as a 2.2.0-0.1 test release. Please
give it a try.
Everything is fine as far as emacs is concerned. I'll rebuild clisp and
test it later today.
I've rebuilt clisp
On 7/21/2015 4:25 PM, Achim Gratz wrote:
Ken Brown writes:
I've rebuilt clisp on both 32-bit and 64-bit, now using libsigsegv on
64-bit, and I don't see any regressions. In particular, it passes the
test suite. I don't know enough about clisp to test it further.
Does maxima
On 7/22/2015 4:16 AM, Corinna Vinschen wrote:
On Jul 21 16:47, Ken Brown wrote:
On 7/21/2015 4:25 PM, Achim Gratz wrote:
Ken Brown writes:
I've rebuilt clisp on both 32-bit and 64-bit, now using libsigsegv on
64-bit, and I don't see any regressions. In particular, it passes the
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives the following error:
configure.ac:255: Something is trying to use the C compiler. Since
this is a C++ project, this should not
On 7/23/2015 5:04 PM, Alexey Sokolov wrote:
23.07.2015 21:49, Alexey Sokolov пишет:
23.07.2015 14:24, Ken Brown пишет:
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives the
On 7/26/2015 1:55 PM, Achim Gratz wrote:
Ken Brown writes:
In that case there's probably no reason for me to wait, unless Achim
wants more time for maxima. Achim, what's your preference? If you
want, you can install the new clisp from my repository
(http://sanibeltranquility.com/c
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access will be able to
post the !ready cookies all at the same time.
Corinna or Yaakov,
On 7/28/2015 12:40 PM, Corinna Vinschen wrote:
On Jul 28 12:36, Ken Brown wrote:
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware a
On 7/31/2015 2:01 PM, Achim Gratz wrote:
Andrew Schulman writes:
I have a filter set up to flag messages with HEADSUP in the subject line as
important. So I always read those. Other maintainers are probably filtering on
HEADSUP in a similar way.
I wasn't aware that this was an agreed-upon ke
On 7/31/2015 2:44 PM, Ken Brown wrote:
On 7/31/2015 2:01 PM, Achim Gratz wrote:
Andrew Schulman writes:
I have a filter set up to flag messages with HEADSUP in the subject line as
important. So I always read those. Other maintainers are probably filtering on
HEADSUP in a similar way.
I
On 6/16/2015 9:27 PM, Ken Brown wrote:
On 6/16/2015 7:52 PM, Yaakov Selkowitz wrote:
On Tue, 2015-06-16 at 10:24 -0400, Ken Brown wrote:
The syntax for 'fmtutil' has changed in TeX Live 2015. The attached
patch accommodates that change.
Just curious, what changed? AFAICS the fmtu
On 8/25/2015 7:37 AM, Andrew Schulman wrote:
I have a package in test, that I want to promote to current. If I just upload
the revised setup.hint and !ready, is that enough?
Yes.
Ken
In case this got lost in the thread about font reorganization, I'm
attaching the patch I proposed in
https://cygwin.com/ml/cygwin/2015-09/msg00223.html
Ken
From 6d8d74bcca48f3b5ce31e6cf9121eb204adb37a8 Mon Sep 17 00:00:00 2001
From: Ken Brown
Date: Fri, 25 Sep 2015 10:18:31 -0400
Su
On 10/20/2015 3:31 PM, Achim Gratz wrote:
Ken Brown writes:
On 5/25/2015 2:45 PM, Ken Brown wrote:
It doesn't look like anything is going to change in the near
future. According to the bug report I cited, Biber runs slower by a
factor of 20 with version 1.18 of Unicode::Normalize than
On 10/20/2015 3:31 PM, Achim Gratz wrote:
Ken Brown writes:
On 5/25/2015 2:45 PM, Ken Brown wrote:
It doesn't look like anything is going to change in the near
future. According to the bug report I cited, Biber runs slower by a
factor of 20 with version 1.18 of Unicode::Normalize than
On 11/3/2015 3:06 AM, Yaakov Selkowitz wrote:
I just created a new 'announce' feature branch in cygport git:
https://github.com/cygwinports/cygport/tree/announce
The new 'announce' command generates an announcement template from
the .cygport file based on NAME/VERSION/RELEASE, PKG_NAMES, and
DE
On 11/3/2015 7:10 PM, Yaakov Selkowitz wrote:
On Tue, 2015-11-03 at 18:23 -0500, Ken Brown wrote:
If there's no mailserver configured, I'd like to see cygport save the
mbox file in the current directory and give an informational message,
rather than saving it in /tmp and giving an err
On 11/5/2015 5:12 PM, Andrew Schulman wrote:
I'm seeing what seems to be some very odd behaviour from Cygport when
uploading noarch packages: Cygport uploads all the packages for the
64-bit architecture, but only the main and source packages for 32-bit
architecture.
Thanks for the troubleshooti
On 11/4/2015 11:12 AM, Ken Brown wrote:
On 11/3/2015 7:10 PM, Yaakov Selkowitz wrote:
On Tue, 2015-11-03 at 18:23 -0500, Ken Brown wrote:
If there's no mailserver configured, I'd like to see cygport save the
mbox file in the current directory and give an informational message,
r
Name: Ken Brown
Package: emacs
BEGIN SSH2 PUBLIC KEY
Comment: "4096-bit RSA, converted by kbrown@moufang from OpenSSH"
B3NzaC1yc2EDAQABAAACAQDbwGV+UhwWh/TxVcu3kbFhZSAPyWcLY3RQE77mQu
6p+tcqLkVwEkxhRbtbCEF2IheX96Xi4+njgnztaiiG0djibH4u6K0CwPA9/GOj
On 1/13/2016 9:31 AM, Corinna Vinschen wrote:
Hi Ken,
On Jan 13 08:23, Ken Brown wrote:
Name: Ken Brown
Package: emacs
BEGIN SSH2 PUBLIC KEY
Installed. Can you check if it works for you?
It works. Thanks.
Ken
On 1/28/2016 12:33 PM, Jon Turney wrote:
Future work: I can't see any reason why this script now needs an
independent existence, so it could be absorbed by the info package.
That's fine with me. There will be a new version of texinfo soon (it's
currently in pretest), so we can make the transi
On 1/28/2016 3:06 PM, Eric Blake wrote:
> On 01/28/2016 11:42 AM, Ken Brown wrote:
>> On 1/28/2016 12:33 PM, Jon Turney wrote:
>>> Future work: I can't see any reason why this script now needs an
>>> independent existence, so it could be absorbed by the info pa
On 1/29/2016 9:22 AM, Jon Turney wrote:
On 28/01/2016 20:22, Eric Blake wrote:
On 01/28/2016 01:17 PM, Ken Brown wrote:
install-info $f /usr/share/info/dir ||
install-info --entry="* $$f ($f): $$f" $$f /usr/share/info/dir
First, what do those double dollar signs mean?
On 1/29/2016 2:17 PM, Achim Gratz wrote:
Ken Brown writes:
[…]
Now for something completely different: when you pull that script into
some info package, could you please swicth it to dash?
Will do.
Ken
On 1/29/2016 9:53 AM, Ken Brown wrote:
On 1/29/2016 9:22 AM, Jon Turney wrote:
On 28/01/2016 20:22, Eric Blake wrote:
On 01/28/2016 01:17 PM, Ken Brown wrote:
install-info $f /usr/share/info/dir ||
install-info --entry="* $$f ($f): $$f" $$f /usr/share/info/dir
First, wha
Achim,
I have a new release of clisp ready to go (x86_64 only) [*]. If I
remember correctly, this means you will need to rebuild maxima. The new
release is available at
http://sanibeltranquility.com/cygwin/
I won't upload it until I get the OK from you.
Ken
[*] The gcc bug that was pre
On 3/15/2016 5:02 PM, Achim Gratz wrote:
Achim Gratz writes:
Achim Gratz writes:
I won't upload it until I get the OK from you.
Let me see when I get to that.
How about now? :-) I'm standby with the files on cygwin.com, I just
need to place the !ready cookie.
Please put your files in pl
On 3/18/2016 7:29 PM, Yaakov Selkowitz wrote:
On 2016-03-18 18:05, Yaakov Selkowitz wrote:
On 2016-03-18 17:25, Ken Brown wrote:
On 3/18/2016 5:45 PM, Corinna Vinschen wrote:
On Mar 18 16:58, Ken Brown wrote:
On 3/18/2016 4:34 PM, Corinna Vinschen wrote:
I released a new Cygwin TEST version
On 3/18/2016 5:45 PM, Corinna Vinschen wrote:
[CCed cygwin-apps to reach out to all package maintainers]
On Mar 18 16:58, Ken Brown wrote:
On 3/18/2016 4:34 PM, Corinna Vinschen wrote:
I released a new Cygwin TEST version 2.5.0-0.8.
If things are not going very wrong, this is basically what
On 3/18/2016 6:25 PM, Ken Brown wrote:
On 3/18/2016 5:45 PM, Corinna Vinschen wrote:
[CCed cygwin-apps to reach out to all package maintainers]
On Mar 18 16:58, Ken Brown wrote:
On 3/18/2016 4:34 PM, Corinna Vinschen wrote:
I released a new Cygwin TEST version 2.5.0-0.8.
If things are
On 3/19/2016 6:32 AM, Corinna Vinschen wrote:
On Mar 18 22:24, Ken Brown wrote:
On 3/18/2016 7:29 PM, Yaakov Selkowitz wrote:
On 2016-03-18 18:05, Yaakov Selkowitz wrote:
On 2016-03-18 17:25, Ken Brown wrote:
On 3/18/2016 5:45 PM, Corinna Vinschen wrote:
On Mar 18 16:58, Ken Brown wrote
On 3/19/2016 8:34 AM, Ken Brown wrote:
On 3/19/2016 6:32 AM, Corinna Vinschen wrote:
On Mar 18 22:24, Ken Brown wrote:
On 3/18/2016 7:29 PM, Yaakov Selkowitz wrote:
On 2016-03-18 18:05, Yaakov Selkowitz wrote:
On 2016-03-18 17:25, Ken Brown wrote:
On 3/18/2016 5:45 PM, Corinna Vinschen
On 3/20/2016 11:26 AM, Corinna Vinschen wrote:
On Mar 19 14:03, Ken Brown wrote:
On 3/19/2016 8:34 AM, Ken Brown wrote:
On 3/19/2016 6:32 AM, Corinna Vinschen wrote:
On Mar 18 22:24, Ken Brown wrote:
On 3/18/2016 7:29 PM, Yaakov Selkowitz wrote:
On 2016-03-18 18:05, Yaakov Selkowitz wrote
On 3/20/2016 4:24 PM, Yaakov Selkowitz wrote:
On 2016-03-20 12:29, Ken Brown wrote:
Never mind. I just sent a report to bug-gnulib, so you can follow up
there.
http://lists.gnu.org/archive/html/bug-gnulib/2016-03/msg00054.html
Please check what I wrote in response to Paul and correct any
On 3/21/2016 9:06 AM, Corinna Vinschen wrote:
Hi Ken,
On Mar 21 08:05, Ken Brown wrote:
On 3/20/2016 4:24 PM, Yaakov Selkowitz wrote:
On 2016-03-20 12:29, Ken Brown wrote:
Never mind. I just sent a report to bug-gnulib, so you can follow up
there.
http://lists.gnu.org/archive/html/bug
On 3/22/2016 5:30 AM, Corinna Vinschen wrote:
On Mar 21 10:13, Ken Brown wrote:
On 3/21/2016 9:06 AM, Corinna Vinschen wrote:
Hi Ken,
On Mar 21 08:05, Ken Brown wrote:
On 3/20/2016 4:24 PM, Yaakov Selkowitz wrote:
On 2016-03-20 12:29, Ken Brown wrote:
Never mind. I just sent a report to
On 3/30/2016 8:51 AM, Corinna Vinschen wrote:
On Mar 22 08:32, Ken Brown wrote:
On 3/22/2016 5:30 AM, Corinna Vinschen wrote:
On Mar 21 10:13, Ken Brown wrote:
On 3/21/2016 9:06 AM, Corinna Vinschen wrote:
Hi Ken,
On Mar 21 08:05, Ken Brown wrote:
On 3/20/2016 4:24 PM, Yaakov Selkowitz
401 - 500 of 1095 matches
Mail list logo
