Re: uniq: missing option -W / --check-fields=N

2006-06-22 Thread Matt Keenan


Eric Blake wrote:
uniq(1) used to have an option for checking only a certain number of 
fields. I have since noticed that some scripts I wrote some time ago 
have stopped working because the -W / --check-fields=N option has 
disappeared. Can it please be put back in?



It's still there in the latest stable version, 5.96:
$ uniq --version | head -n1
uniq (GNU coreutils) 5.96
$ uniq --help | grep check
  -w, --check-chars=N   compare no more than N characters in lines

  

not --check-chars=N, I'm talking about --check-fields=N.
I am happy to write a patch 
to do so if no-one else wants to do it. Is there a reason why it 
disappeared?



Probably because you switched systems or PATH, and are no
longer using the GNU coreutils version of uniq.

  


I upgraded recently from Debian Sarge to Ubuntu Dapper, and I noticed 
that the -W (note the caps!) flag had disappeared. Maybe it was a Debian 
distro patch. Paul Eggert has mentioned that upstream uniq has never had 
a -W flag. Would you be receptive to a patch? I'm happy to write one.


Matt



___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


Re: uniq: missing option -W / --check-fields=N

2006-06-22 Thread Pádraig Brady
Matt Keenan wrote:
 Greetings all,
 
 uniq(1) used to have an option for checking only a certain number of
 fields. I have since noticed that some scripts I wrote some time ago
 have stopped working because the -W / --check-fields=N option has
 disappeared. Can it please be put back in? I am happy to write a patch
 to do so if no-one else wants to do it. Is there a reason why it
 disappeared?

Debian specific:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344577

Pádraig.


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


error: conflicting types for 'tee'

2006-06-22 Thread Andreas Schwab
The next release of GNU libc will have a declaration of a function tee in
fcntl.h (only under _GNU_SOURCE, of course).  This will cause a conflict
with the use of this name in tee.c:

tee.c:34: error: conflicting types for 'tee'
/usr/include/bits/fcntl.h:226: error: previous declaration of 'tee' was here

Since coreutils always defines _GNU_SOURCE such types of conflicts can
happen any time.

Andreas.

-- 
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
And now for something completely different.


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


Re: error: conflicting types for 'tee'

2006-06-22 Thread Jim Meyering
Andreas Schwab [EMAIL PROTECTED] wrote:
 The next release of GNU libc will have a declaration of a function tee in
 fcntl.h (only under _GNU_SOURCE, of course).  This will cause a conflict
 with the use of this name in tee.c:

 tee.c:34: error: conflicting types for 'tee'
 /usr/include/bits/fcntl.h:226: error: previous declaration of 'tee' was here

 Since coreutils always defines _GNU_SOURCE such types of conflicts can
 happen any time.

Thanks.
I've just fixed this on the trunk and branch.

2006-06-22  Jim Meyering  [EMAIL PROTECTED]

* src/tee.c (tee_files): Rename from tee, to avoid conflict with
the function in glibc's fcntl.h.  Reported by Andreas Schwab.


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


[bug #16913] sleep fails to detect overflow on amd64 / linux 2.6

2006-06-22 Thread anonymous

URL:
  http://savannah.gnu.org/bugs/?func=detailitemitem_id=16913

 Summary: sleep fails to detect overflow on amd64 / linux 2.6
 Project: GNU Core Utilities
Submitted by: None
Submitted on: Thursday 06/22/2006 at 14:54 UTC
Category: None
Severity: 3 - Normal
  Item Group: None
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open

___

Details:


sleep 100  - returns immediately with exit code 0
sleep 10   - sleeps
sleep 1000 - sleeps

Not really sane amounts of seconds to sleep but on the other hand there is
some code in xnanosleep.c to handle overflow conditions.

More details about the underlying bug in nanosleep() in 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374983








___

Reply to this item at:

  http://savannah.gnu.org/bugs/?func=detailitemitem_id=16913

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


Re: make install using -j

2006-06-22 Thread Paul Eggert
Ralf Wildenhues [EMAIL PROTECTED] writes in
http://lists.gnu.org/archive/html/bug-automake/2006-06/msg00025.html:

 Not sure about an easy way to fix the first bug as well here.
   * lib/install-sh: HP-UX 11.23 `mkdir -m u=rwx,[...],u+wx -p'
   may exit 0 but create intermediate directories with bogus
   permissions.  So change the `$mkdirprog -m $test_mode' test to
   create actual directories, and test for readability of the
   intermediate one.  Clean up afterwards.

This patch assumes the working directory is writable, which isn't a
safe assumption.  Also, it won't work as root, since 'test -r D'
succeeds as root even if D has mode d-wx-w--w-.  And, as you mentioned,
the patch doesn't work around the mkdir -m u=rwx,g=rx,o=rx -p -- foo/bar
bug on UP-UX 11.23 and IRIX 6.5 that you reported in
http://lists.gnu.org/archive/html/bug-automake/2006-06/msg00024.html.

On my list of things to do is to fix GNU install to be safer and more
compatible with BSD install, with respect to the modes of intermediate
directories and temporary files.  Among other things, GNU install
should use mode 755 as modified by the umask to create temporary
directories, instead of what it currently does (which is an
undocumented algorithm that is similar to, but not quite identical to,
mkdir -p's algorithm).  I'll CC: this message to bug-coreutils to give
them a heads-up on this.

Anyway, to get back to install-sh: it needs a similar patch, so your
email prompted me to write it.  As a side effect I think this patch
works around both bugs you reported.  So I propose the following
Automake patch instead.  Does it work for you?

Index: ChangeLog
===
RCS file: /cvs/automake/automake/ChangeLog,v
retrieving revision 1.2901
diff -p -u -r1.2901 ChangeLog
--- ChangeLog   7 Jun 2006 06:01:22 -   1.2901
+++ ChangeLog   22 Jun 2006 21:08:06 -
@@ -1,3 +1,20 @@
+2006-06-22  Paul Eggert  [EMAIL PROTECTED]
+
+   * lib/install-sh: Don't incorrectly claim that this implementation
+   can install only one file at a time.
+   (test_mode, intermediate_mode): Remove.
+   Use octal modes if the invoker specifies an octal mode, and use
+   octal umask values if 'umask' outputs octal values; in the usual
+   case this works around bugs with symbolic modes with HP-UX 11.23
+   and IRIX 6.5 mkdir as reported by Ralf Wildenhues in
+   http://lists.gnu.org/archive/html/bug-automake/2006-06/msg00024.html
+   since Automake uses octal modes.
+   (cp_umask, mkdir_umask, mkdir_mode): New variables, to avoid
+   temporarily creating files or directories with too-permissive modes.
+   Use the FreeBSD method for computing modes of intermediate directories.
+   (posix_mkdir): Use ':' for true, not 'true'; this is a bit faster on
+   traditional implementations.
+
 2006-06-07  Alexandre Duret-Lutz  [EMAIL PROTECTED]
 
* automake.in (handle_LIBOBJS): Don't rely on the caller defining $1.
@@ -508,6 +525,9 @@
* doc/automake.texi (limitations on file names): New section.
* lib/install-sh: Rewrite to support '*' in file names.
Also, tune so that we don't invoke so many commands in the usual case.
+   This has the side effect of fixing `install-sh -d' to not fail if it
+   loses the race in creating the last path component against another
+   process.
* tests/instspc.test: The * test is now fixed.
 
 2005-09-13  Stepan Kasal  [EMAIL PROTECTED]
Index: lib/install-sh
===
RCS file: /cvs/automake/automake/lib/install-sh,v
retrieving revision 1.34
diff -p -u -r1.34 install-sh
--- lib/install-sh  11 May 2006 19:52:08 -  1.34
+++ lib/install-sh  22 Jun 2006 21:08:06 -
@@ -39,8 +39,7 @@ scriptversion=2006-05-11.20
 # when there is no Makefile.
 #
 # This script is compatible with the BSD install script, but was written
-# from scratch.  It can only install one file at a time, a restriction
-# shared with many OS's install programs.
+# from scratch.
 
 nl='
 '
@@ -50,6 +49,10 @@ IFS=  $nl
 
 # Don't use :- since 4.3BSD and earlier shells don't like it.
 doit=${DOITPROG-}
+case $doit in
+  '') doit_exec=exec ;;
+  ?*) doit_exec=$doit ;;
+esac
 
 # Put in absolute file names if you don't have them in your path;
 # or use environment vars.
@@ -66,17 +69,9 @@ mkdirprog=${MKDIRPROG-mkdir}
 posix_glob=
 posix_mkdir=
 
-# Symbolic mode for testing mkdir with directories.
-# It is the same as 755, but also tests that u+ works.
-test_mode=u=rwx,g=rx,o=rx,u+wx
-
 # Desired mode of installed file.
 mode=0755
 
-# Desired mode of newly created intermediate directories.
-# It is empty if not known yet.
-intermediate_mode=
-
 chmodcmd=$chmodprog
 chowncmd=
 chgrpcmd=
@@ -191,7 +186,31 @@ if test $# -eq 0; then
   exit 0
 fi
 
-test -n $dir_arg || trap '(exit $?); exit' 1 2 13 15
+if test -z $dir_arg; then
+  

Re: uniq: missing option -W / --check-fields=N

2006-06-22 Thread Paul Eggert
Matt Keenan [EMAIL PROTECTED] writes:

 Paul Eggert has mentioned that upstream uniq has never had a -W
 flag. Would you be receptive to a patch?

I'm not sure.  Does any distribution other than Debian-derived
distributions have it?  More importantly, what's it used for and
useful for?


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


[bug #16913] sleep fails to detect overflow on amd64 / linux 2.6

2006-06-22 Thread Paul Eggert

Update of bug #16913 (project coreutils):

  Status:None = Wont Fix   
 Open/Closed:Open = Closed 

___

Follow-up Comment #1:

xnanosleep's overflow checking merely catches the usual
problems with integer overflow in xnanosleep's own
calculations.  It's not designed to work around bugs in the
implementation of nanosleep.  Offhand, I don't see an easy way
to work around this bug so I'd say you just need to get your
kernel fixed.  (In the meantime you can rest easy knowing that
coreutils sleep is a good way to check for the kernel bug.
:-)


___

Reply to this item at:

  http://savannah.gnu.org/bugs/?func=detailitemitem_id=16913

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


f0und aff0rdable medicati0n prices

2006-06-22 Thread Meghan
  http://gniiku.weardesk.com/?62783622 
  o1zxzlghEStXoDpIHJpIW3lN6LK1eOa3kKADbR42Q5SYovOJxImtKWE69nma87fXi6jieYBeqWAw
  
awlUEGNgR9iKHPJ7yqH5L53ZVEmgvrq0j69mkhVBaHNd599FX8Cd2sKPDH58Va8mmW7HsAJuxMVQS6P
  7rzJ344OqTCI39hwSAMnWV2scWl55cLGcl16QAEW3OIQ0lt97w1vZ7ROFuv9AKwfzZd89F
  uOCk3tPvGZaNUlrN6280H4xWWjp5Spa2SXQyAuBB7GHNjR39yXLHqzT5YG1nW8SLC8y4MgB
  tXoJlBado5Hsr7Af5gwknD9pTa8wHmymb9o9x4N26ldbjlgEK4LuelGLi6ayqIV7chpulE7M
  pvYruVHrRe8Hk3c2QNvud8Ggk38LejHrgT7hW6CpARSxjlHrWV7m1ZgJt7Qj4Sid6vHqR3YsFg8Ms
  XWW2g8Dqf3yPmE3FXuGUDmr0zMq3R2ION595cpslxf4fQI69enqx3NHoSHkST8xJY7j5dm7OU5D9pw
  M9SJklrG4eM5hzxxygh7m6MaHSbREgcmnLr9wIj8b1T4iLIWB9WJxGi1k4AGmH3hxzf44hPbZ
  Rq3IvUuuJG0OUJ3u3ZPi88OFiiLdjcz3zxx4FfG5HXGzXuFJYKiJlcMXsWZFeJveWjkhABQmEX
  kclwlFyNLutNdw8T7jjW4fn5AK2HWbiL9KrCHqnD3XiHC2M2onp7xsdAYH6ODwJalhdM04E1xNn





image537.gif
Description: image537.gif
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils