Summary: | =app-admin/webapp-config-1.52 - Shows outdated entries | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | twitch153, web-apps |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
2013-11-02 09:09:35 UTC
I know how I've made this bug occur, may I ask how you have? The way I can reproduce this is by deleting an entry with rm instead of webapp-config -C. I believe it might also occur if you unemerge a webapp while it's "still in" the vhost. That one I'm not too sure of though. It is something I plan on fixing though. Hopefully soon. AFAICR I never called webapp-config directly - I "just" used it via emerge. However the user mode linux image was created years ago (and daily/weekly updated) - but nevertheless, migth be just rubbish from the past. (In reply to Toralf Förster from comment #2) > AFAICR I never called webapp-config directly - I "just" used it via emerge. > > However the user mode linux image was created years ago (and daily/weekly > updated) - but nevertheless, migth be just rubbish from the past. You might very well be right, nonetheless the bug is still valid and I will be working on it :) Please don't manually CC maintainers to avoid more mail, thank you in advance. In the next release there will be a flag called the --prune-database flag. What this should do is remove database entries that shouldn't be listed (ie. If they are removed manually or if they were overwritten by portage). It's been tested by myself but I will leave this bug open until the release and others can confirm that it works for them. webapp-config-1.53 has been out for quite some time now and along with it the --prune-database function. Closing the bug as resolved. |