Is the Mercurial package still maintained?

[Ti Strga]

Hi.

Upstream is at v5.0.2.  The cygwin repo has been at 4.3.2 for almost two
years now, missing not only a lot of features but also the security fixes
in 4.7.2 and 4.9.

Is a new package blocked waiting on other support to be completed?  Or is
it simply orphaned and waiting for a new maintainer or NMU?

--
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

Re: [ANNOUNCEMENT] Updated: make-4.1-1

[Ti Strga]

BLUF:  either the new make package needs cygltdl-7 as one of its
dependencies, or Guile does, so that setup.exe can Do The Right Thing.

I updated to make-4.1-1 and the executable immediately broke:

$ make --version
/usr/bin/make.exe: error while loading shared libraries: ?: cannot
open shared object file: No such file or directory

Poked the current cygcheck at it:
$ cygcheck /usr/bin/make.exe
C:\cygwin\bin\make.exe
  C:\cygwin\bin\cygwin1.dll
C:\Windows\system32\KERNEL32.dll
  C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
  C:\Windows\system32\ntdll.dll
  C:\Windows\system32\KERNELBASE.dll
  C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  C:\cygwin\bin\cygguile-17.dll
C:\cygwin\bin\cygcrypt-0.dll
C:\cygwin\bin\cyggmp-3.dll
  C:\cygwin\bin\cyggcc_s-1.dll
C:\cygwin\bin\cygintl-8.dll
  C:\cygwin\bin\cygiconv-2.dll
cygcheck: track_down: could not find cygltdl-7.dll

I brought up setup.exe, found cygltdl-7 (which was not previously
installed), installed 2.4.6-1, and now all is well:

$ make --version
GNU Make 4.1
Built for i686-pc-cygwin
Copyright (C) 1988-2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ cygcheck /usr/bin/make.exe
C:\cygwin\bin\make.exe
  C:\cygwin\bin\cygwin1.dll
C:\Windows\system32\KERNEL32.dll
  C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
  C:\Windows\system32\ntdll.dll
  C:\Windows\system32\KERNELBASE.dll
  C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  C:\cygwin\bin\cygguile-17.dll
C:\cygwin\bin\cygcrypt-0.dll
C:\cygwin\bin\cyggmp-3.dll
  C:\cygwin\bin\cyggcc_s-1.dll
C:\cygwin\bin\cygintl-8.dll
  C:\cygwin\bin\cygiconv-2.dll
C:\cygwin\bin\cygltdl-7.dll

The indentation would seem to indicate that cygltdl-7 is needed by
cygguile-17 and not by make.exe directly.  This fits with what little
I know about Guile, however I did not have time to pursue the problem
any further, as I needed to go back to my original task (the one for
which I was running make).  So if/when the cygguile package is rebuilt
next time, this may all solve itself; for now this message is just an
FYI for future google users wondering why setup.exe isn't magically
doing a transitive closure.  :-)

Thanks to everyone involved!

-Ti

--
Problem reports:   http://cygwin.com/problems.ht

Re: pipe handling errors

[Ti Strga]

Christopher Faylor wrote:
> Increasing the size of the buffer should have been enough to fix the
> problem but, when possible, I like to use two forms of protection when I
> fix a bug.

I recall someone on a project here doing a bugfix with a commit log like:

-mm-dd The Guy's Name 

Fix #n
foo.cc (func1):  Belt.
bar.cc (func2):  Suspenders.

Anyhow, I'm looking forward to trying out the fix myself.  We've been
getting those errors here but not nearly as often.

--
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

Re: Mercurial 2.8 or 2.9?

[Ti Strga]

Jari Aalto wrote:
> later versions are being packaged soon (expect in a week)

Great news, thank you!

--
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

Mercurial 2.8 or 2.9?

[Ti Strga]

Upstream Mercurial is at 2.9.2, but looking in
http://cygwin.com/packages/x86/mercurial/ there's only 2.5.x
and 2.7.x.

Are there plans to package a more recent release?  Or alternatively,
is there anything in particular holding them back?  The only recent
hits for mercurial that mnogosearch could find in the archives for the
main cygwin and cygwin-apps lists were mentions in people's
cygcheck output, but I don't know what's been discussed in other
lists or IRC or etc.

--
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

Re: Install Bash 4.2 for Cygwin fails

[Ti Strga]

(GMail won't let me stick a References: header in; the thread here
was from [1].)

> Bash 4.2 is *still* using the old and long deprecated
> cygwin_conv_to_full_posix_path function.  It should long have changed
> the call to use the cygwin_conv_path or cygwin_create_path function.
>
> Eric?  Any chance to update bash?

The mailing list search engine can't find any further messages past
this one.  Were there any?  Bash 4.2 is three years old this month,
we'd love to start using it on Cygwin.  :-)

If there's work already done then we can wait; if not then one of us might
try and kludge something together locally.


[1] http://cygwin.com/ml/cygwin/2013-12/msg00215.html

--
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

Re: Issues downloading vim-minimal-7.4.182-1.tar.xz

[Ti Strga]

> > I've tried 3 different mirrors all with the same result - when I try
> > to update to vim-minimal-7.4.182-1.tar.xz via setup-x86.exe I get a
> > pop-up stating "Download Incomplete.  Try again?"  Is the file
> > truncated?
>
> Yet it installed.  For good measure I re-installed it again and all
> was good.  Dunno what happened the first time.

Seeing the exact same thing here.  Skipping the retry to allow the
rest of the installation to go through, then choosing 'Reinstall' for
vim-minimal, worked.

FWIW, the failed download popup always happened when the main
setup.exe said it was trying to download autorebase.

The setup log only contains:

2014/02/24 11:36:58 Starting cygwin install, version 2.831
2014/02/24 11:36:58 User has NO backup/restore rights
2014/02/24 11:36:58 Attempting to elevate to Administrator
2014/02/24 11:36:58 Writing messages to log files without exiting

(Dunno what the kvetching about permissions is, as I'm the only user
on this system, most definitely with all the privileges.  It's Windows 7
x64, but running a 32-bit Cygwin.)

--
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

postinstall reboots system; saving settings for reinstall?

[Ti Strga]

Hi.

Earlier today I was updating my cygwin installation (WinXP, cygwin 1.7
as of a couple weeks ago) when the computer suddenly rebooted.
Because there were so other things running at the time I assumed it
was just bad mojo, but after doing things slow and methodical-like, I
narrowed it down to a cygwin setup.exe postinstall step.  It's 100%
reproducible -- but I don't know which package is triggering it (as
the setup display is changing so quickly just before it all goes
black) or how far all the successful steps were (as the log file isn't
written out yet).

I started to gather cygcheck info to bring to this list for help...
but cygcheck segfaults as soon as it gets to the "Cygwin Package
Information" part.  So I'm thinking the installation ishosed at this
point, and I need to remove it all and reinstall from scratch, which
is fine.

But I've installed quite a few non-default packages since 1.7 came
out, plus some mount points and other customization bits.  Is there a
way to dump a listing of that stuff so that I can have something to
refer to afterwards, when I'm setting it all back up?  I could swear
I've seen command line to do things like "print a list of installed
packages" but searching the mailing list archives gets either zero
hits or a hojillion irrelevant hits.


-Ti

--
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