Re: RFU: apngopt 1.1-2 (recent archive problem)

2012-11-02 Thread Corinna Vinschen
On Nov  1 18:20, Jari Aalto wrote:
 2012-11-01 12:29 Corinna Vinschen
 | It would probably be helpful to bump the subversion to 2 and push
 | another package, though, just in case.
 
 Here,
 
 wget --recursive --no-host-directories --cut-dirs=3 \
 http://cante.net/~jaalto/tmp/cygwin/apngopt/apngopt-1.1-2-src.tar.bz2 \
 http://cante.net/~jaalto/tmp/cygwin/apngopt/apngopt-1.1-2.tar.bz2 \
 http://cante.net/~jaalto/tmp/cygwin/apngopt/setup.hint

Uploaded.


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat


Re: Command line arguments

2012-11-02 Thread Earnie Boyd
On Thu, Nov 1, 2012 at 4:48 PM, Andrew DeFaria wrote:
 On 11/1/2012 10:54 AM, Brian Wilson wrote:

 I got in the habbit of always using the {} (even if they aren't
 absolutely necessary) to avoid such issues on general principal.

 I don't think it's conducive to productivity to constantly type things that
 aren't needed for the simple sake of consistency - especially special
 characters which are by nature harder to type. As they say a foolish
 consistency is the hobglobin of little minds. I add syntactic sugar only
 when required, much like a native English speaker doesn't shy away from
 things like contractions under a habit of always spelling out all words even
 if they aren't absolutely necessary... YMMV.

YMMV when it comes time for maintenance by someone other than the code
creator.  Consistency helps reduce cost and reducing company cost
helps increase my pay check.  Taking a few seconds to use {} to
delimit all variables is priceless in the world of maintenance.  As a
native English (American) speaker, I find myself more than once
expanding contractions to make myself more clear about what I want to
convey.  Contractions for contraction sake is not always a good thing.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

--
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: Command line arguments

2012-11-02 Thread Andrew DeFaria

On 11/02/2012 05:36 AM, Earnie Boyd wrote:

YMMV when it comes time for maintenance by someone other than the code creator. 
 Consistency helps reduce cost and reducing company cost helps increase my pay 
check.
I disagree. A [emphasis on] *foolish* consistency doesn't do anything to 
reduce cost. It's something programmers believe helps, then they spend a 
lot of time making things consistent for consistency's sake based upon 
this myth and thus adds cost not reduces it. Sprinkling syntactic sugar 
obscures the clarity of things, again, IMHO.


Don't get me wrong - some forms of consistency are good and do help 
reduce cost because readability increases. But syntactic sugar is there 
for the computer - not the human.


As for paycheck, I can assure you that mine is at an all time high and 
way above the average (like 3x).

Taking a few seconds to use {} to delimit all variables is priceless in the 
world of maintenance.
No, IMHO it's wasteful to spend time doing this non-productive activity 
when it's the rare case that it is truly needed.

As a native English (American) speaker, I find myself more than once expanding 
contractions to make myself more clear about what I want to convey.
And it probably ain't any clearer to anybody. If consistency in language 
was that much of a concern and you really wanted to make it such that 
you are absolutely clear then you should drop English ( 
http://defaria.com/Jokes/Plan4ImprovementOfEnglishSpelling.php and 
http://defaria.com/Jokes/CrazyLanguage.php) and pick up Lojban ( 
http://en.wikipedia.org/wiki/Lojban). Of course then you'd be talking to 
yourself pretty much.

Contractions for contraction sake is not always a good thing.
Nobody said it was. This was an *example* - intended to convey a higher 
and deeper meaning. Think about it instead of simply taking it literally.


And with that I think we should end this, pretty much off topic 
discussion (take it to email if you'd like).

--
Andrew DeFaria http://defaria.com
One time a cop pulled me over for running a stop sign. He said Didn't 
you see the stop sign. I said Yeah, but I don't believe everything I 
read.



--
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: Command line arguments

2012-11-02 Thread Eliot Moss

On 11/2/2012 10:32 AM, Andrew DeFaria wrote:

On 11/02/2012 05:36 AM, Earnie Boyd wrote:


Can we declare an end to the philosophical flames
on how to write uses of parameters in bash scripts,
please?

Maybe if we're friendly enough the OP will actually
share what the real problem was and we can offer
some specific help ...

Regards -- Eliot Moss

--
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: Command line arguments

2012-11-02 Thread Christopher Faylor
On Fri, Nov 02, 2012 at 10:54:25AM -0400, Eliot Moss wrote:
On 11/2/2012 10:32 AM, Andrew DeFaria wrote:
On 11/02/2012 05:36 AM, Earnie Boyd wrote:

Can we declare an end to the philosophical flames on how to write uses
of parameters in bash scripts, please?

I know that I, of all people, shouldn't be encouraging this type of
thing but I actually found the discussion interesting.  But, you're
right, and Andrew even acknowledged that the discussion had strayed
and should be taken elsewhere.

But, if anyone wants to continue the philosophy, I'll grant a TITTL
waiver.

Maybe if we're friendly enough the OP will actually share what the real
problem was and we can offer some specific help ...

Or, we could even call this whole discussion closed since it seems to
have nothing to do with Cygwin and even the non-philosophical part seems
to have been beaten to death.

cgf

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



Domain User getting Permission Denied for anything outside of /home/user/

2012-11-02 Thread Cameron Gunnin
Hi,

I've been struggling with this for the past week to no avail.  As the
title suggests, if I am logged in under a user that is not the user
who installed Cygwin (regardless of the user's windows permissions),
then I cannot modify near anything outside of /home/user/.  Here's
what I'm trying to get working.

1a) Install Cygwin as a Local Administrator.  Run mkpasswd -l 
/etc/passwd and mkgroup -l  /etc/group
OR (I would prefer 1a, but 1b is acceptable as well)
1b) Install Cygwin as Domain Administrator.  Run mkpasswd -d 
/etc/passwd and mkgroup -d  /etc/group

2) Login as Domain User (has administrative privileges on local
machine AND can access the AD).
NOTE: At this point, I get the message:

Your group is currently mkpasswd.  This indicates that your
gid is not in /etc/group and your uid is not in /etc/passwd.

The /etc/passwd (and possibly /etc/group) files should be rebuilt.
See the man pages for mkpasswd and mkgroup then, for example, run

mkpasswd -l [-d]  /etc/passwd
mkgroup -l [-d]  /etc/group

Note that the -d switch is necessary for domain users.

3) Attempt to run mkpasswd -d  /etc/passwd and mkgroup -d  /etc/group
However, I get the message:

$ mkpasswd -d  /etc/passwd
-sh: /etc/passwd: Permission Denied

If I run ls -al / then I get an odd (but expected, I think) list of
permissions on several root folders.
eg. drwxr-xr-x+  mkpasswd 0 Oct 31 14:16 etc

I cannot even touch a file inside the directories with  listed
as their user.

$ touch /etc/myfile
touch: cannot touch 'myfile': PermissionDenied

HOWEVER, I can touch/edit files under the windows file system.
$ touch /cygdrive/c/myfile
$ echo data  /cygdrive/c/myfile
$ echo data  /cygdrive/c/existing file with  user

Any help is appreciated, as I've been stuck on this for just over a week now.

Thanks.

--
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: Cygcheck says w3m 0.5.3-1 package incomplete, file type mismatch messages

2012-11-02 Thread Keith Christian
On Thu, Oct 25, 2012 at 9:20 AM, Bob Heckel bhec...@gmail.com wrote:
 I just noticed that uninstalling w3m-img reduces w3m's local file load time.

 Still working on repackaging to possibly address the other issue.


Hi Bob,

I have some timing data courtesy of Sysinternals Procmon that has the
time from invocation of w3m to display at 6 to 7 seconds, if that
helps any.  Package: w3m-0.5.3-2 was installed a few days ago, haven't
noticed any load time changes (the test this morning was on a 28 kb
local HTML file to avoid any network delay factors.

No hurry, if you ever find out the issue (assuming it' reproducable on
your machine) it'd be interesting to know,

The machine I'm using is a Windows 7 64 bit, 3 Ghz, 3+ Gig machine, so
it should be sufficient for the task.

Thanks for your efforts and investigations.

Keith

--
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: A cygwin mosh question

2012-11-02 Thread Reini Urban
On Thu, Nov 1, 2012 at 8:14 PM, Eliot Moss wrote:
 On 11/1/2012 9:05 PM, Eliot Moss wrote:
 On 10/31/2012 1:46 PM, Eliot Moss wrote:

 After seeing the announcement on mosh, I decided to install it and
 try it out.  I installed it on a remote server running Red Hat style
 Linux using yum, and on my laptop using cygwin.  Sadly, I have run
 into some problems:

 1) The cygwin install does not include the dependency on the
 IO:Tty package.  I installed that manually, using cpan.

Because I removed the perl wrapper, yes.

 2) When I try to mosh to my remote server, all I ever get is
 Hangup.  Since there does not seem to be any verbose mode,
 I am not sure how to diagnose this further.

 I installed the latest version today and was able to get things
 working.  (It prints out more about issues connecting, which
 allowed me to resolve them.)

 - The remote end was not setting LANG for UTF-8.  I had to do this
by: mosh --server='mosh-server new -l LANG=en_US.UTF-8'

 - I discovered that mosh does not support an xterm escape sequence
that I use, namely one to *read* the window icon label: CSI 20 t
and also CSI 11 t (reports whether the window is iconified).  My
main purpose is to save and use the icon label as the base for
setting a longer label or title

 I have worked around this by setting an extra environment variable
 when using mosh, and skipping the reading of the icon label in that
 case.

 However, all of this is not really cygwin-specific, so I'll stop
 there.

The LANG issue needs to be reported upstream, yes.
The special icon getter, hmm. You can try to add a patch upstream for
this weird use-case.

 However, the failure to install the IO:Tty dependency may be relevant.
 Is there an easy way I can test that again?  What would I uninstall
 and reinstall to check?  That is, cpan will install things, but how
 would I *un*-install IO:Tty to check whether cygwin install of mosh
 loads it?


 Oh, I think I get it now, after digging further into what the install
 of mosh actually does: the newer versions do not use perl, but work
 directly -- is that right?  If so, then the lack of dependence is
 correct, and I apologize for the extra chatter!

Yes. Perl caused problems in forks using IO::Pty and reading from STDIN.
This was explained in the announcement of the experimental mosh-1.2.2-2 package.
http://sourceware.org/ml/cygwin-announce/2012-07/msg00021.html
-- 
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

--
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: Cygcheck says w3m 0.5.3-1 package incomplete, file type mismatch messages

2012-11-02 Thread Bob Heckel
On Fri, Nov 2, 2012 at 1:12 PM, Keith Christian wrote:
 I have some timing data courtesy of Sysinternals Procmon that has the
 time from invocation of w3m to display at 6 to 7 seconds, if that
 helps any.  Package: w3m-0.5.3-2 was installed a few days ago, haven't
 noticed any load time changes (the test this morning was on a 28 kb
 local HTML file to avoid any network delay factors.

Hi Keith,

Just to confirm, have you uninstalled w3m-img?  I'm no expert at
Cygwin/X and I don't use it normally, I compiled in X11 support since
it was a nice addition and it actually worked for 0.5.3 :)

In the past when I had Cygwin/X gvim installed it would take console
vim longer to startup, no idea if it's the same issue.

Anyway, here are my tests on an average, WinXP box with a fresh Cygwin
non-X install (except for w3m-img).  I used
http://www.gnu.org/software/bash/manual/bashref.html saved locally, I
typed Q as soon as the page loaded, not very scientific...:

1. Uninstalled w3m-img

$ time w3m ./bashref.html

real0m1.875s
user0m0.559s
sys 0m0.231s

2. Re-installed w3m-img

real0m5.016s
user0m0.887s
sys 0m0.293s

3. Uninstalled w3m-img (just to make sure)

real0m1.812s
user0m0.747s
sys 0m0.184s

If it's still a problem for you and others, I'm not sure how to replicate it.

Bob

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



mosh 1.2.3 error when using on Cygwin

2012-11-02 Thread nyc4bos
Hi,

After starting up mosh on Cygwin and then attempting to type
`ls', I see the following on my screen:

$ ls select: No error


mosh did not shut down cleanly. Please note that the
mosh-server process may still be running on the server.

[mosh is exiting.]
  1 [main] mosh-client 4524 cygthread::detach: called detach but inuse 0, th
read 0xF7C?


Sometimes I am able to type a few commands but mostly it is only
after one command before I see the select: No error message.

The mosh-server.exe process is still running.

I am on Windows XP and I am running a freshly installed Cygwin using
Cygwin setup 1.7.17-1

Thanks.



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



[ANNOUNCEMENT] Obsolete Package: mlcscope-99-1

2012-11-02 Thread Dave And Diane
The package mlcscope-99-1 has been obsoleted and replaced by 
cscope-15.8.0.1-1


mlcscope was a Lucent Technologies implementation of cscope which is no 
longer maintained.


cscope is commonly found in Linux distributions such as Debian and other 
Unix O/S's.


Cygwin setup has been updated to automatically install cscope if 
mlcscope was installed.


Instead of using 'mlcscope' to interrogate source code, use 'cscope' 
going forward.


Cheers
Dave


--

Diane  Dave
http://www.velvetstarbears.com/  http://www.kringlecottage.com/
Fortune: The difference between America and England is that the
English think 100 miles is a long distance and the Americans
think 100 years is a long time.


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



Obsolete Package: mlcscope-99-1

2012-11-02 Thread Dave And Diane
The package mlcscope-99-1 has been obsoleted and replaced by 
cscope-15.8.0.1-1


mlcscope was a Lucent Technologies implementation of cscope which is no 
longer maintained.


cscope is commonly found in Linux distributions such as Debian and other 
Unix O/S's.


Cygwin setup has been updated to automatically install cscope if 
mlcscope was installed.


Instead of using 'mlcscope' to interrogate source code, use 'cscope' 
going forward.


Cheers
Dave


--

Diane  Dave
http://www.velvetstarbears.com/  http://www.kringlecottage.com/
Fortune: The difference between America and England is that the
English think 100 miles is a long distance and the Americans
think 100 years is a long time.