On Wed, 29 Nov 2017 15:39:45, Brian Inglis wrote:
> > On 2017-11-25 14:23, Houder wrote:
> > > Hi,
> > >
> > > Anyone seeing this as well? sort goes berzerk on my system when piped
> > > into
> > > head (or less) when it is fed with a 'specially prepared' input file.
>
On 2017-11-28 10:12, Houder wrote:
> On 2017-11-28 14:37, Doug Henderson wrote:
>
> On 2017-11-25 14:23, Houder wrote:
> > Hi,
> >
> > Anyone seeing this as well? sort goes berzerk on my system when piped
> > into
> > head (or less) when it is fed with a 'specially prepared
On 29/11/2017 21:34, Ivan Gagis wrote:
What is that timestamp? Is it when the package was uploaded?
Sorry, by timestamp, I just mean the mtime of the archive file.
Then it should not be possible, because lower version definitely was
uploaded earlier than higher version package.
Where are tho
hope to see this in Cygwin soon, I've been running a custom compilation
of cygwin1.dll for awhile using some of Thomas's patches.
On Wed, Nov 29, 2017, at 03:44 PM, Corinna Vinschen wrote:
> On Nov 29 20:56, Thomas Wolff wrote:
> > May I kindly remind of https://cygwin.com/ml/cygwin/2017-07/msg00
On Nov 29 20:56, Thomas Wolff wrote:
> May I kindly remind of https://cygwin.com/ml/cygwin/2017-07/msg00366.html,
> for which my patch proposal is still pending on the newlib mailing list?
You may want to ping the patch on the newlib ML.
I actually forgot about this patch, sorry.
Corinna
--
C
May I kindly remind of https://cygwin.com/ml/cygwin/2017-07/msg00366.html,
for which my patch proposal is still pending on the newlib mailing list?
While it's not as urgent anymore for mintty, where I've introduced a
native width option meanwhile (Charwidth, corresponding to xterm
-mk_width), it
Houder writes:
> No, I have not executed rebaseall. The reason is, that I have
> "reinstalled" Cygwin twice now, starting with an empty repo and an
> empty root directory.
I have seen the initial rebaseall after a fresh install go wrong due to
antivirus interference. Triggering another full rebas
On 29/11/2017 14:58, Ivan Gagis wrote:
Hi,
I found that in case packages validation fails the mksetup script just
returns success, though it prints a line in the console saying
"mksetupini: package set has errors, not writing setup.ini".
I think it should return some error code so that it would
On 29/11/2017 15:06, Ivan Gagis wrote:
I have an overlay cygwin repo where I publish my packages.
Recently I started getting errors from mksetupini script:
"
mksetupini: package 'mypackage' version '0.4.38-1' is most recent
non-test version, but version '0.4.43-1' is curr:
mksetupini: package s
(gdb) target exec regtool -w get "\HKCR\c\205\216c\205\216c\205\216c\205\216
regtool -w get "\HKCR\c▒▒c▒▒c▒▒c▒▒": No such file or directory.
The text are not written correctly, but there are no errors.
Mysterious error. T-T
There is an error in the Korean OS.
See error : mediafire.com/file/7vcaa
REMOVE
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On Nov 30 00:41, ViOLeT wrote:
> # OS Language
> Korean (Asia), CHCP Code 949
>
> # Locale Code
> LANG=
> LC_CTYPE="C.UTF-8"
> LC_NUMERIC="C.UTF-8"
> LC_TIME="C.UTF-8"
> LC_COLLATE="C.UTF-8"
> LC_MONETARY="C.UTF-8"
> LC_MESSAGES="C.UTF-8"
> LC_ALL=
>
> Is it an operating system language issue?
I
# OS Language
Korean (Asia), CHCP Code 949
# Locale Code
LANG=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_ALL=
Is it an operating system language issue?
2017-11-29 18:29 GMT+09:00 Corinna Vinschen :
> Hi ViOLeT,
>
Hi,
I have an overlay cygwin repo where I publish my packages.
Recently I started getting errors from mksetupini script:
"
mksetupini: package 'mypackage' version '0.4.38-1' is most recent
non-test version, but version '0.4.43-1' is curr:
mksetupini: package set has errors, not writing setup.ini
Hi,
I found that in case packages validation fails the mksetup script just
returns success, though it prints a line in the console saying
"mksetupini: package set has errors, not writing setup.ini".
I think it should return some error code so that it would not be
considered as success by CI scrip
Hi ViOLeT,
On Nov 29 15:33, ViOLeT wrote:
> Hello.
>
> Cygwin 2.9.0 regtool x64 exception error (W10) reporting. (But it seems to
> be an error in all (2.9.0 lower) versions.)
>
> Using the Unicode causes an exception error.
> But, regtool x86 is no error occurs.
>
> *Example :*
> regtool.exe -
16 matches
Mail list logo
