You are not logged in.
Pages: 1
I searched this site via google - the bbs search mechanism is weird - and returned three threads that weren't especially relevant.
So anybody have an explanation for this?
[ j@althea ][ 07-13 23:50 ][ ~ ]
:pacman -Qo id3info
error: id3info is not a file.
[ j@althea ][ 07-13 23:50 ][ ~ ]
:locate id3info
/usr/bin/id3info
[ j@althea ][ 07-13 23:50 ][ ~ ]
:cdp
[ j@althea ][ 07-13 23:50 ][ /var/lib/pacman/local ]
:grep -r id3info *
id3lib-3.8.3-4/files:usr/bin/id3info
I was pretty sure I knew what owned it but thought pacman would be faster. Turned out I was right about the first and way wrong about the second. Same results for id3tag, id3convert, etc.
The only thing I can think of is that I yanked easytag and then decided I at least wanted id3lib:
[ j@althea ][ 07-14 00:03 ][ /var/lib/pacman/local ]
:grep id3lib /var/log/pacman.log
[07/04/05 15:28] installed id3lib (3.8.3-4)
[07/10/05 10:18] removed id3lib (3.8.3-4)
[07/10/05 10:27] installed id3lib (3.8.3-4)
[ j@althea ][ 07-14 00:03 ][ /var/lib/pacman/local ]
:grep '07/10/05 10:18' /var/log/pacman.log
[07/10/05 10:18] removed easytag (1.1-1)
[07/10/05 10:18] removed flac (1.1.2-2)
[07/10/05 10:18] removed id3lib (3.8.3-4)
but that's no excuse. The package is still there and pacman should still know it.
Offline
Try putting in the full search path next time... seems pacman by default doesn't search for you (which, logically, makes total sense when you think about it).
-[travis@Cerebral]-[~]-
12:05am $ pacman -Qo id3info
error: id3info is not a file.
-[travis@Cerebral]-[~]-
12:05am $ pacman -Qo /usr/bin/id3info
/usr/bin/id3info is owned by id3lib 3.8.3-4
-[travis@Cerebral]-[~]-
12:05am $
Offline
[ j@althea ][ 07-14 00:03 ][ /var/lib/pacman/local ]
:pacman -Qo `which id3info`
/usr/bin/id3info is owned by id3lib 3.8.3-4
Bingo. Thanks. But, actually, it doesn't make any sense. Pacman is supposed to know what everything is - might as well know where everything is. And I could have sworn I've used -Qo with a bare filename before. (I usually just grep for it, though - the '-Qo' is a new practice for me, so maybe I imagined it.)
Anyway - that's the solution. Thanks again. At least I don't have to worry that pacman's broken or something.
-- [edit] Ah. I must have just happened to be in the current directory of the programs/files I was querying about when I got results with just the name and that gave me the idea a path wasn't required.
Offline
Heh, no prob. When I say it makes perfect sense, all I mean is I can't think of any other program that searches out a filename for you... ie "gvim filename" assumes filename is in the pwd; same for any other program I can think of.
I personally wouldn't expect pacman to behave any other way -- what if two different packages installed a file called 'id3info' to seperate folders? That could get confusing.
Offline
Heh, no prob. When I say it makes perfect sense, all I mean is I can't think of any other program that searches out a filename for you... ie "gvim filename" assumes filename is in the pwd; same for any other program I can think of.
Well, I was thinking of it as a specialized tool. Like 'man' is an example of something that doesn't need a /usr/man/man1/foo.1.gz.
I personally wouldn't expect pacman to behave any other way -- what if two different packages installed a file called 'id3info' to seperate folders? That could get confusing.
Good point. Though it could do something like 'man -a' to list all or just spit out all matching entries. But, yeah, I'll just think of it as giving vim a filename.
Offline
Pages: 1