Re: file ownership in liblockfile1 1.01 (sparc)
On Wed, Oct 11, 2000 at 08:01:57AM -0700, andy wrote: > On Wed, 11 Oct 2000, Daniel Jacobowitz wrote: > > > On Wed, Oct 11, 2000 at 07:18:23AM -0700, andy wrote: > > > just ran tiger on a fresh debian (2.2) install, and received the following > > > warnings: > > > > > > # Performing check of PATH components... > > > # Only checking user 'root' > > > --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is > > > not owned by root (owned by dovienya). > > > > What uid is user dovienya on your machine? > > > > uid=1000(dovienya) > this is the user account set up during the install process. on the theory > that it was setting perms based on $SUDO_USER, i tried installing from the > console as root (w/o su, sudo, fakeroot, etc.) with the same results. -rwxr-sr-x buildd/mail 14228 1999-07-19 10:57:34 usr/bin/dotlockfile There's the problem. > all three boxes i have noticed this on are sparcs. i don't have a debian > x86 box around to check... This sort of error happens when building the package. It needs to be recompiled for sparc. I'll try to get it in 2.2r1. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/
Re: file ownership in liblockfile1 1.01 (sparc)
responses inline... On Wed, 11 Oct 2000, Daniel Jacobowitz wrote: > On Wed, Oct 11, 2000 at 07:18:23AM -0700, andy wrote: > > just ran tiger on a fresh debian (2.2) install, and received the following > > warnings: > > > > # Performing check of PATH components... > > # Only checking user 'root' > > --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is > > not owned by root (owned by dovienya). > > What uid is user dovienya on your machine? > uid=1000(dovienya) this is the user account set up during the install process. on the theory that it was setting perms based on $SUDO_USER, i tried installing from the console as root (w/o su, sudo, fakeroot, etc.) with the same results. > The liblockfile1 package contains no files not owned by root in Debian > 2.2 on i386 or powerpc - what architecture are you running? > all three boxes i have noticed this on are sparcs. i don't have a debian x86 box around to check... > > i verified that the same holds true on two other installs, and didn't find > > any information on this on the net at large... so i thought i'd send an > > email out debian-security way to get some feedback... > > Was anything unique about these installs? What are you installing > from? nothing unusual as far as i can tell. very minimal installs. installed from cd, updated from the net. i've removed and reinstalled liblockfile1, always with the same results. i am currently getting liblockfile1 from: Get:1 http://http.us.debian.org stable/main liblockfile1 1.01 [14.6kB] > I can't reproduce this. > > Dan > > /\ /\ > | Daniel Jacobowitz|__|SCS Class of 2002 | > | Debian GNU/Linux Developer__Carnegie Mellon University | > | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | > \/ \/ >
Re: file ownership in liblockfile1 1.01 (sparc)
On Wed, Oct 11, 2000 at 07:18:23AM -0700, andy wrote: > just ran tiger on a fresh debian (2.2) install, and received the following > warnings: > > # Performing check of PATH components... > # Only checking user 'root' > --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is > not owned by root (owned by dovienya). What uid is user dovienya on your machine? The liblockfile1 package contains no files not owned by root in Debian 2.2 on i386 or powerpc - what architecture are you running? > i verified that the same holds true on two other installs, and didn't find > any information on this on the net at large... so i thought i'd send an > email out debian-security way to get some feedback... Was anything unique about these installs? What are you installing from? I can't reproduce this. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/
file ownership in liblockfile1 1.01 (sparc)
just ran tiger on a fresh debian (2.2) install, and received the following warnings: # Performing check of PATH components... # Only checking user 'root' --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is not owned by root (owned by dovienya). --WARN-- [x] The following files have undefined groups ownership: /usr/doc/liblockfile1/changelog.gz /usr/doc/liblockfile1/copyright /usr/lib/liblockfile.so.1 /usr/lib/liblockfile.so.1.0 /usr/man/man1/dotlockfile.1 /var/lib/dpkg/info/liblockfile1.postinst /var/lib/dpkg/info/liblockfile1.shlibs and sure enough... -rwxr-sr-x1 dovienya mail /usr/bin/dotlockfile -rw-r--r--1 root 500 /usr/doc/liblockfile1/changelog.gz -rw-r--r--1 root 500 /usr/doc/liblockfile1/copyright lrwxrwxrwx1 root root /usr/lib/liblockfile.so.1 -> liblockfile.so.1.0 -rw-r--r--1 root 500 /usr/lib/liblockfile.so.1.0 -rw-r--r--1 root 500 /usr/man/man1/dotlockfile.1 -rwxr-xr-x1 root 500 /var/lib/dpkg/info/liblockfile1.postinst -rwxr-xr-x1 root 500 /var/lib/dpkg/info/liblockfile1.shlibs i verified that the same holds true on two other installs, and didn't find any information on this on the net at large... so i thought i'd send an email out debian-security way to get some feedback... thanks! andy
Re: file ownership in liblockfile1 1.01 (sparc)
On Wed, Oct 11, 2000 at 08:01:57AM -0700, andy wrote: > On Wed, 11 Oct 2000, Daniel Jacobowitz wrote: > > > On Wed, Oct 11, 2000 at 07:18:23AM -0700, andy wrote: > > > just ran tiger on a fresh debian (2.2) install, and received the following > > > warnings: > > > > > > # Performing check of PATH components... > > > # Only checking user 'root' > > > --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is > > > not owned by root (owned by dovienya). > > > > What uid is user dovienya on your machine? > > > > uid=1000(dovienya) > this is the user account set up during the install process. on the theory > that it was setting perms based on $SUDO_USER, i tried installing from the > console as root (w/o su, sudo, fakeroot, etc.) with the same results. -rwxr-sr-x buildd/mail 14228 1999-07-19 10:57:34 usr/bin/dotlockfile There's the problem. > all three boxes i have noticed this on are sparcs. i don't have a debian > x86 box around to check... This sort of error happens when building the package. It needs to be recompiled for sparc. I'll try to get it in 2.2r1. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: file ownership in liblockfile1 1.01 (sparc)
responses inline... On Wed, 11 Oct 2000, Daniel Jacobowitz wrote: > On Wed, Oct 11, 2000 at 07:18:23AM -0700, andy wrote: > > just ran tiger on a fresh debian (2.2) install, and received the following > > warnings: > > > > # Performing check of PATH components... > > # Only checking user 'root' > > --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is > > not owned by root (owned by dovienya). > > What uid is user dovienya on your machine? > uid=1000(dovienya) this is the user account set up during the install process. on the theory that it was setting perms based on $SUDO_USER, i tried installing from the console as root (w/o su, sudo, fakeroot, etc.) with the same results. > The liblockfile1 package contains no files not owned by root in Debian > 2.2 on i386 or powerpc - what architecture are you running? > all three boxes i have noticed this on are sparcs. i don't have a debian x86 box around to check... > > i verified that the same holds true on two other installs, and didn't find > > any information on this on the net at large... so i thought i'd send an > > email out debian-security way to get some feedback... > > Was anything unique about these installs? What are you installing > from? nothing unusual as far as i can tell. very minimal installs. installed from cd, updated from the net. i've removed and reinstalled liblockfile1, always with the same results. i am currently getting liblockfile1 from: Get:1 http://http.us.debian.org stable/main liblockfile1 1.01 [14.6kB] > I can't reproduce this. > > Dan > > /\ /\ > | Daniel Jacobowitz|__|SCS Class of 2002 | > | Debian GNU/Linux Developer__Carnegie Mellon University | > | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | > \/ \/ > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: file ownership in liblockfile1 1.01 (sparc)
On Wed, Oct 11, 2000 at 07:18:23AM -0700, andy wrote: > just ran tiger on a fresh debian (2.2) install, and received the following > warnings: > > # Performing check of PATH components... > # Only checking user 'root' > --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is > not owned by root (owned by dovienya). What uid is user dovienya on your machine? The liblockfile1 package contains no files not owned by root in Debian 2.2 on i386 or powerpc - what architecture are you running? > i verified that the same holds true on two other installs, and didn't find > any information on this on the net at large... so i thought i'd send an > email out debian-security way to get some feedback... Was anything unique about these installs? What are you installing from? I can't reproduce this. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
file ownership in liblockfile1 1.01 (sparc)
just ran tiger on a fresh debian (2.2) install, and received the following warnings: # Performing check of PATH components... # Only checking user 'root' --WARN-- [path002w] /usr/bin/dotlockfile in root's PATH from default is not owned by root (owned by dovienya). --WARN-- [x] The following files have undefined groups ownership: /usr/doc/liblockfile1/changelog.gz /usr/doc/liblockfile1/copyright /usr/lib/liblockfile.so.1 /usr/lib/liblockfile.so.1.0 /usr/man/man1/dotlockfile.1 /var/lib/dpkg/info/liblockfile1.postinst /var/lib/dpkg/info/liblockfile1.shlibs and sure enough... -rwxr-sr-x1 dovienya mail /usr/bin/dotlockfile -rw-r--r--1 root 500 /usr/doc/liblockfile1/changelog.gz -rw-r--r--1 root 500 /usr/doc/liblockfile1/copyright lrwxrwxrwx1 root root /usr/lib/liblockfile.so.1 -> liblockfile.so.1.0 -rw-r--r--1 root 500 /usr/lib/liblockfile.so.1.0 -rw-r--r--1 root 500 /usr/man/man1/dotlockfile.1 -rwxr-xr-x1 root 500 /var/lib/dpkg/info/liblockfile1.postinst -rwxr-xr-x1 root 500 /var/lib/dpkg/info/liblockfile1.shlibs i verified that the same holds true on two other installs, and didn't find any information on this on the net at large... so i thought i'd send an email out debian-security way to get some feedback... thanks! andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
