Re: [Cooker] Orphan files ?

2003-11-13 Thread Guillaume Cottenceau
Frank Griffin [EMAIL PROTECTED] writes:

 I'm looking for some guidance on trying to find the package which
 owns a file.
 
 Several times now when I've had a problem with a particular
 executable or one of the initialization script files, I've tried
 to find the owning package for purposes of filing a bug report by
 using rpmdrake's seach on filename feature, only to get no hits
 from the search.

 The latest example is /usr/bin/update-menus.

In install mode, it searches files in packages that you can
install, thus of course this won't find the owner of installed
file /usr/bin/update-menus.

In remove mode, it would work if menu was allowed to be removed,
but it's not the case (we don't want you break your system).

Anyway, rpm -qf is the easiest way for such a question, as others
answered.

-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/



Re: [Cooker] Orphan files ?

2003-11-13 Thread Dennis Veatch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 12 November 2003 07:38 pm, Leon Brooks wrote:
 On Thu, 13 Nov 2003 08:13, Frank Griffin wrote:
  It appears that I have a /usr/bin/update-menus without having the
  menus package installed.  I've also got the man page.

 Try this:

 rm -vf /var/lib/rpm/__db.00*
 rpm --rebuilddb

 Cheers; Leon

I'm trying to rebuild the rpm database and keep running into an error about 
failing to remove directory /var/lib/rpmrebuilddb.19602. Says the directory 
is not empty. It contains a file RPMLOCK. So I delete run rpm --rebuilddb and 
get the same error only the directory name changed.


- -- 
Registered Linux user 193414
http://counter.li.org

Trying? My contribution was much closer to a feeble wave in the general 
direction of something that might lead you one step closer to a solution 
if you squint really hard and do all of the work.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/s2qvZkF4+BJ00wcRAk+IAKDYWMhpPkzFVXYJEHb8dwBUMzojQACeLtnm
BJe0F0VYl5+iwXPzTSw0cOQ=
=UOoP
-END PGP SIGNATURE-




[Cooker] Orphan files ?

2003-11-12 Thread Frank Griffin
I'm looking for some guidance on trying to find the package which owns a 
file.

Several times now when I've had a problem with a particular executable 
or one of the initialization script files, I've tried to find the owning 
package for purposes of filing a bug report by using rpmdrake's seach on 
filename feature, only to get no hits from the search.

The latest example is /usr/bin/update-menus.

Should this technique work, or should I be doing something else ?




Re: [Cooker] Orphan files ?

2003-11-12 Thread James Sparenberg
On Wed, 2003-11-12 at 15:24, Frank Griffin wrote:
 I'm looking for some guidance on trying to find the package which owns a 
 file.
 
 Several times now when I've had a problem with a particular executable 
 or one of the initialization script files, I've tried to find the owning 
 package for purposes of filing a bug report by using rpmdrake's seach on 
 filename feature, only to get no hits from the search.
 
 The latest example is /usr/bin/update-menus.
 
 Should this technique work, or should I be doing something else ?

urpmf /usr/bin/update-menus 

will give you the package that includes that file.

James

 
 




Re: [Cooker] Orphan files ?

2003-11-12 Thread Michael Altizer
Frank Griffin wrote:

I'm looking for some guidance on trying to find the package which owns 
a file.

Several times now when I've had a problem with a particular executable 
or one of the initialization script files, I've tried to find the 
owning package for purposes of filing a bug report by using rpmdrake's 
seach on filename feature, only to get no hits from the search.

The latest example is /usr/bin/update-menus.

Should this technique work, or should I be doing something else ?



It seems as though this should work.  Using urpmf --files update-menus 
returns the following results:
menu:/usr/bin/update-menus
menu:/usr/share/man/man1/update-menus.1.bz2
So, /usr/bin/update-menus belongs to the menu package. (menu-2.1.5-124mdk)
Note: Obviously, this is only going to work 100% if your urpmi database 
matches your currently installed packages since packages are often 
removed and, though less frequent an occurance, files may switch between 
packages (eg. all the recent KDE changes).
-Michael




Re: [Cooker] Orphan files ?

2003-11-12 Thread James Sparenberg
On Wed, 2003-11-12 at 15:42, Michael Altizer wrote:
 Frank Griffin wrote:
 
  I'm looking for some guidance on trying to find the package which owns 
  a file.
 
  Several times now when I've had a problem with a particular executable 
  or one of the initialization script files, I've tried to find the 
  owning package for purposes of filing a bug report by using rpmdrake's 
  seach on filename feature, only to get no hits from the search.
 
  The latest example is /usr/bin/update-menus.
 
  Should this technique work, or should I be doing something else ?
 
 
 
 It seems as though this should work.  Using urpmf --files update-menus 
 returns the following results:
 menu:/usr/bin/update-menus
 menu:/usr/share/man/man1/update-menus.1.bz2
 So, /usr/bin/update-menus belongs to the menu package. (menu-2.1.5-124mdk)
 Note: Obviously, this is only going to work 100% if your urpmi database 
 matches your currently installed packages since packages are often 
 removed and, though less frequent an occurance, files may switch between 
 packages (eg. all the recent KDE changes).
 -Michael

Correct I am making two assumptions.  

1.  That current state of the urpmi database is == current installed
status.
2.  That this method is more usefull on a stable system than a dev
system.

An alternative.

rpm -q --whatprovides /usr/bin/update-menus

I've often found that giving full path to a file results in fewer orphan
statements than normal.  

James


 
 




Re: [Cooker] Orphan files ?

2003-11-12 Thread Frank Griffin
James Sparenberg wrote:

urpmf /usr/bin/update-menus 

will give you the package that includes that file.

 

Michael Altizer wrote:

It seems as though this should work.  Using urpmf --files update-menus 
returns the following results:
menu:/usr/bin/update-menus
menu:/usr/share/man/man1/update-menus.1.bz2


Hmm. 

It appears that I have a /usr/bin/update-menus without having the menus 
package installed.  I've also got the man page.  However

If I do what you suggested, I get:

[EMAIL PROTECTED] ftg]# urpmf --files update-menus
majesty-demo:/usr/local/games/maj_demo/.manifest/scripts/update-menus.sh
mindrover-demo:/usr/games/mindrover_demo/.manifest/scripts/update-menus.sh
[EMAIL PROTECTED] ftg]# urpmf /usr/bin/update-menus
[EMAIL PROTECTED] ftg]# urpmi menu
Everything already installed
[EMAIL PROTECTED] ftg]#
In addition, if I look in my cooker tree, I have
  menu-2.1.5-124mdk.i586.rpm
but neither rpmdrake install nor rpmdrake remove lists the package when 
I select list all packages, alphabetical.

A urpmi.update -a made absolutely no difference in these results.

Is there some lower-level query I can do to discern why urpmi thinks the 
package is installed and I can see that the files are present, but 
rpmdrake thinks it is neither here nor there ?






Re: [Cooker] Orphan files ?

2003-11-12 Thread Leon Brooks
On Thu, 13 Nov 2003 07:24, Frank Griffin wrote:
 The latest example is /usr/bin/update-menus.

$ rpm -qf /usr/bin/update-menus
menu-2.1.5-123mdk
$

Cheers; Leon




Re: [Cooker] Orphan files ?

2003-11-12 Thread Frank Griffin
James Sparenberg wrote:

An alternative.

rpm -q --whatprovides /usr/bin/update-menus

 

[EMAIL PROTECTED] ftg]# rpm -q --whatprovides /usr/bin/update-menus
menu-2.1.5-124mdk





Re: [Cooker] Orphan files ?

2003-11-12 Thread Frank Griffin
Leon Brooks wrote:

$ rpm -qf /usr/bin/update-menus
menu-2.1.5-123mdk
 

[EMAIL PROTECTED] ftg]# rpm -qf /usr/bin/update-menus
menu-2.1.5-124mdk



Re: [Cooker] Orphan files ?

2003-11-12 Thread Leon Brooks
On Thu, 13 Nov 2003 08:13, Frank Griffin wrote:
 It appears that I have a /usr/bin/update-menus without having the
 menus package installed.  I've also got the man page.

Try this:

rm -vf /var/lib/rpm/__db.00*
rpm --rebuilddb

Cheers; Leon




Re: [Cooker] Orphan files ?

2003-11-12 Thread Frank Griffin
Leon Brooks wrote:

Try this:

   rm -vf /var/lib/rpm/__db.00*
   rpm --rebuilddb
 

I'll be happy to, but one of the reasons to post this was to see if 
anybody wanted a snapshot of the existing files that seem to cause urpmi 
to recognize that the package is installed but neither urpmf nor 
rpmdrake to recognize the files included in it, or in the case of 
rpmdrake, that the package even exists (since it isn't recognized as 
being either installed or not).

If somebody can tell me which files to copy off to the side for 
inclusion with a bug report, I'll be happy to move on.  If the 
responsible parties aren't interested, then please just say so, and I'll 
abandon trying to preserve evidence




Re: [Cooker] Orphan files ?

2003-11-12 Thread Leon Brooks
On Thu, 13 Nov 2003 08:49, Frank Griffin wrote:
 Leon Brooks wrote:
Try this:

rm -vf /var/lib/rpm/__db.00*
rpm --rebuilddb

 I'll be happy to, but one of the reasons to post this was to see if
 anybody wanted a snapshot of the existing files that seem to cause
 urpmi to recognize that the package is installed but neither urpmf
 nor rpmdrake to recognize the files included in it, or in the case of
 rpmdrake, that the package even exists (since it isn't recognized as
 being either installed or not).

 If somebody can tell me which files to copy off to the side for
 inclusion with a bug report, I'll be happy to move on.  If the
 responsible parties aren't interested, then please just say so, and
 I'll abandon trying to preserve evidence

Since RPM itself seems to be happy, the contents of /var/lib/urpmi would 
seem to be what's required (about 20MB on my machine). If you wanted to 
be safe, put aside /var/lib/rpm as well (about 23MB here).

Cheers; Leon