Starting module-rebuild from sys-kernel/module-rebuidl-0.6 without portage installed gives the following error: $ module-rebuild ** FATAL: Unable to find portageq. Apparently module-rebuild requires portage and thus needs a run dependency on it. Reproducible: Always Steps to Reproduce: 1. Uninstall portage 2. Run module-rebuild Expected Results: sys-kernel/module-rebuild-0.6 should depend on portage, so that the package manager can prevent the uninstallation of portage, if module-rebuild is installed.
fixed in 0.7 (in cvs), since it was a fix I did not revbump.
(In reply to comment #1) > fixed in 0.7 (in cvs), since it was a fix I did not revbump. You're serious? I'm not using Gentoo anymore since over two years, and now I get bugged by this tracker, because you fixed a god-damn dependency issue? After three(!) fucking years? Unbelievable…
Actually, this package is assigned to a herd but has not been maintained for a while since this is now in Portage itself covered under `emerge -1 @module-rebuild`; therefore updates to a deprecated package are rare, they are done for users that haven't upgraded to the new approach yet or have reasons not to use the newer approach. But it was clear you don't care about this history, so feel free to click "Disable All Mail" on https://bugs.gentoo.org/userprefs.cgi?tab=email so we don't bother you any further with our "in our free time" contributions.
(In reply to comment #3) > Actually, this package is assigned to a herd but has not been maintained for > a while since this is now in Portage itself covered under `emerge -1 > @module-rebuild`; therefore updates to a deprecated package are rare, they > are done for users that haven't upgraded to the new approach yet or have > reasons not to use the newer approach. So this package is even deprecated?! You're fixing an issue, that *none ever cared for* since it was reported, in a *deprecated* package, after *three* years of ignorance? Why didn't you bother to fix it *three years ago*, when it (likely, I don't know actually) wasn't deprecated, and when I apparently (really can't remember now) needed it fixed? > But it was clear you don't care about this history, so feel free to click > "Disable All Mail" on https://bugs.gentoo.org/userprefs.cgi?tab=email so we > don't bother you any further with our "in our free time" contributions. Don't talk to me of your "free time"... apparently you've got enough of it to not only dig up three years old issues for deprecated package, but actually fix them, too! I am envious about the amount of free time you seem to possess. Though, thinking of it, this fix can't have taken more than... say, five minutes or so. Anyway, I thank you for your advice, which I promptly followed. By now all mail is disabled, so please do not feel encouraged to reply. I won't notice it anyway. I'll be available under my mail address, though, in case you still see a need for discussion. To cool down matters eventually: I really appreciate your contributions, I just can't help but wonder about the objective of your efforts.
(In reply to comment #4) > (In reply to comment #3) > > Actually, this package is assigned to a herd but has not been maintained for > > a while since this is now in Portage itself covered under `emerge -1 > > @module-rebuild`; therefore updates to a deprecated package are rare, they > > are done for users that haven't upgraded to the new approach yet or have > > reasons not to use the newer approach. > > So this package is even deprecated?! You're fixing an issue, that *none > ever cared for* since it was reported, in a *deprecated* package, after > *three* years of ignorance? > > Why didn't you bother to fix it *three years ago*, when it (likely, I don't > know actually) wasn't deprecated, and when I apparently (really can't > remember now) needed it fixed? I didn't fix it. And the other dev reason probably has a good reason to do so... It only deprecated recently, so if you replace years to something in between weeks and months it probably makes more sense; this is still used in scripts on systems that don't have the Portage that support @module-rebuild, or people with a different package manager (similar to your use case). Though we generally don't support other package managers, this one benefits them for once... > > But it was clear you don't care about this history, so feel free to click > > "Disable All Mail" on https://bugs.gentoo.org/userprefs.cgi?tab=email so we > > don't bother you any further with our "in our free time" contributions. > > Don't talk to me of your "free time"... apparently you've got enough of it > to not only dig up three years old issues for deprecated package, but > actually fix them, too! I am envious about the amount of free time you seem > to possess. Though, thinking of it, this fix can't have taken more than... > say, five minutes or so. Pursuing productivity and fixing that 1% to increase overall Portage tree reliability are fun goals if you turn them into a game; ignoring that, changing one line of code barely takes any time for someone who has been doing this years. We've probably wasted 100 times more time together than it would require to fix it for prometheanfire. > Anyway, I thank you for your advice, which I promptly followed. By now all > mail is disabled, so please do not feel encouraged to reply. I won't notice > it anyway. I'll be available under my mail address, though, in case you > still see a need for discussion. Thanks. > To cool down matters eventually: I really appreciate your contributions, I > just can't help but wonder about the objective of your efforts. I've explained one assumption, but I can't tell for sure; maybe he'll respond on the bug, or maybe he doesn't care and fixes some more bugs instead.
Thank you for your mail, for your efforts to explain this, and above all for your civil replies to my admittedly not so civil comments. Being a developer, too, I can understand why this issue was fixed, however late. With regards to the deprecation of the package, I do consider this as a last house-keeping task to get the package into good state before abandoning it. As a (ex-)user of your distribution however, I cannot but wonder that this issue was too hard to fix *right away*, but not too hard however to be fixed after years, even after the deprecation of the affected package, and long after I actually left your distribution. I understand that this kind of house keeping is for the greater good, so to say, but to me myself this was not helpful. Nonetheless, I apologize for being so caustic. Your work is appreciated, even though I do not use Gentoo any more. I learned a lot while doing so, and still profit from this experience.
