| Summary: | net-wireless/gr-osmosdr-0.2.0 infinite rebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | John (EBo) David <ebo> |
| Component: | Current packages | Assignee: | Gentoo Radio project <radio> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info as required | ||
we need to collect some more information. Is only net-wireless/gr-osmosdr-0.2.0 rebuilt, or are there other packages too? We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/ Yes. It is only gr-osmosdr at the moment. I have had this happen before many years ago, and will say that I see this type of error maybe a couple of times a decade (I've been a Gentoo user since 2001). My experience is that it normally happens during major portage tree changes, and often resolve itself after a couple of months. Since this type of bug is so intermittent and difficult to track down, I understand if you wish to close it. I was just bring it to people's attention. If "this is only happening to me", then I will flush and regen the portage/repo trees, as well as look at my package accept keywords -- to see if I have some weird dependencies. Ping. In meantime the old gr-osmosdr-0.2.0 version is gone. Actual versions are gr-osmosdr-0.2.3 and 0.2.3_p20210128-r1. Do you still observe the above problem? Otherwise we will close the bug in next days. My last gentoo machine died a couple of months ago (after running continually for 8 years), and I have at least temporarily moved to Pop_OS (on a System76 machine). I might end up dual booting it to Gentoo, but for now I have no way to test this. I will go ahead and mark this as resolved/obsolete, and revisit if/when I get an appropriate machine running gentoo again. BTW, I started running Gentoo in December of 2001. I am missing it, but setting up a new machine has always been such a pain (particualry multi-user sound), that I figured I would give a vender supported hardware/Linux-distro a try (hense System76's Pop_OS). To bad no venders ever picked up Gentoo... |
Created attachment 679368 [details] emerge --info as required After running emerge --sync, and then '-uDNp', it told me: [ebuild rR ~] net-wireless/gr-osmosdr-0.2.0 After successfully rebuilding it, portage tells me it needs to be rebuilt again. I've retried it a couple of times. Any suggestions on how to fix this? At the moment it is not a problem, but it would be nice to fix.