sys-apps/pmount-0.9.9 stable request - works fine on x86 for 1 month - no-bugs-in-zilla
Actually, before this could go stable, cryptsetup-luks needs to go stable.
cryptsetup-luks is stable now and pmount-0.9.9 is supposed to fix issues that arise when using it with hal-0.5.7 which is now stable.
seconded/thirded: * checking 11 files for package collisions existing file /media/.keep is not owned by this package * spent 0.00102686882019 seconds checking for file collisions [...] package sys-apps/pmount-0.9.6 NOT merged hemlock ~ # equery b /media/.keep [ Searching for file(s) /media/.keep in *... ] sys-apps/hal-0.5.7-r1 (/media/.keep)
ppc stable
Stable on SPARC
Stable for HPPA.
amd64 stable owns you all!!
x86 is happy and content *burp* ^.^;;
ppc64 stable
(In reply to comment #0) > sys-apps/pmount-0.9.9 stable request > > - works fine on x86 for 1 month > - no-bugs-in-zilla After this became stable (for amd64), the pmount functionality of my system failed (see bug#143499), i.e., it is not stable on my system. A filed a bug report (see bug#143499), hoping this would get fixed. In the meantime, I masked all pmount packages >0.9.6 (which works perfectly for me). Recently, pmount-0.9.6 was _removed_ from the portage tree, causing me all kinds of unnecessary updating woes (emerge world blocks because there now exists no more stable ebuild for me). So please, in the future, before throwing out (stable) packages, see if no bugs have been filed after a package has been declared stable. If anybody would take a look at bug#143499, I would very much appreciate it, because I fear that from now on, my situation can only get worse.
arm/ia64 done, closing bug