Created attachment 874072 [details] new ebuild for 3.0.0 app-misc/resolve-march-native is now at version 3.0.0 which contains a bug fixed 11/3/2023 for the arm64 architecture. I copied the 2.2.0 version in its entirety and renamed 3.0.0. No edits to the file. Log of session building and installing the 3.0.0 version at: https://pastebin.com/x2nu2JHR (6 month life)
The upstream maintainer is also the Gentoo one. And it's already in tree: commit d4d5c2d0f81876b9ab6cf82b02f6b173aa150fd9 Author: Sebastian Pipping <sping@gentoo.org> Date: Sat Nov 4 15:10:52 2023 +0100 app-misc/resolve-march-native: 3.0.0 with -mcpu= support Closes: https://bugs.gentoo.org/916486 Signed-off-by: Sebastian Pipping <sping@gentoo.org>
I checked Bug and updated my portage tree after the item was fixed. Is there something else in the future I should have checked so that I do not submit "invalid" bugs? ares /home/jlpoole # eix-sync * Running emerge --sync >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... * PGP verification method: gemato * Fetching most recent snapshot ... * Trying to retrieve 20231103 snapshot from https://gentoo.osuosl.org ... * Fetching file gentoo-20231103.tar.xz.md5sum ... --2023-11-04 10:13:27-- https://gentoo.osuosl.org/snapshots/gentoo-20231103.tar.xz.md5sum Resolving gentoo.osuosl.org... 64.50.233.100, 64.50.236.52, 140.211.166.134, ... Connecting to gentoo.osuosl.org|64.50.233.100|:443... connected. HTTP request sent, awaiting response... 200 OK .... ares /home/jlpoole # eix resolve-march * app-misc/resolve-march-native Available versions: 1.0.0-r1^t ~2.1.0^t ~2.1.0-r1^t 2.2.0^t {test PYTHON_TARGETS="python3_10 python3_11"} Homepage: https://github.com/hartwork/resolve-march-native Description: Resolve GCC flag -march=native ares /home/jlpoole #
(In reply to John L. Poole from comment #2) > I checked Bug and updated my portage tree after the item was fixed. > > Is there something else in the future I should have checked so that I do not > submit "invalid" bugs? You can search for "ALL resolve-march-native" instead, I suppose. If you prefix with "ALL", it includes closed bugs. > > ares /home/jlpoole # eix-sync > * Running emerge --sync > >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... > * PGP verification method: gemato > * Fetching most recent snapshot ... > * Trying to retrieve 20231103 snapshot from https://gentoo.osuosl.org ... > * Fetching file gentoo-20231103.tar.xz.md5sum ... > --2023-11-04 10:13:27-- > https://gentoo.osuosl.org/snapshots/gentoo-20231103.tar.xz.md5sum > Resolving gentoo.osuosl.org... 64.50.233.100, 64.50.236.52, 140.211.166.134, > ... > Connecting to gentoo.osuosl.org|64.50.233.100|:443... connected. > HTTP request sent, awaiting response... 200 OK > .... You're using sync-type=webrsync which only updates nightly, so you'll have to wait until midnight UTC if you keep using that.
(In reply to Sam James from comment #3) > (In reply to John L. Poole from comment #2) > > I checked Bug and updated my portage tree after the item was fixed. > > > > Is there something else in the future I should have checked so that I do not > > submit "invalid" bugs? > > You can search for "ALL resolve-march-native" instead, I suppose. If you > prefix with "ALL", it includes closed bugs. > > > > > ares /home/jlpoole # eix-sync > > * Running emerge --sync > > >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... > > * PGP verification method: gemato > > * Fetching most recent snapshot ... > > * Trying to retrieve 20231103 snapshot from https://gentoo.osuosl.org ... > > * Fetching file gentoo-20231103.tar.xz.md5sum ... > > --2023-11-04 10:13:27-- > > https://gentoo.osuosl.org/snapshots/gentoo-20231103.tar.xz.md5sum > > Resolving gentoo.osuosl.org... 64.50.233.100, 64.50.236.52, 140.211.166.134, > > ... > > Connecting to gentoo.osuosl.org|64.50.233.100|:443... connected. > > HTTP request sent, awaiting response... 200 OK > > .... > > You're using sync-type=webrsync which only updates nightly, so you'll have > to wait until midnight UTC if you keep using that. Thank you.
Yet another way to check, visit the package URL: https://packages.gentoo.org/packages/app-misc/resolve-march-native So going forward a procedure to avoid duplicative effort: 1) update portage tree, 2) check Bug with "ALL", & 3) visit the packages URL to see if updates have been submitted. (I am assuming the packages URL gives the current state of the portage tree and is not subject to the delay that propagating server, i.e. OSU, would have.)
Checking the source at e.g. https://gitweb.gentoo.org/repo/gentoo.git/ would get rid of any delay questions.
(In reply to Sebastian Pipping from comment #6) > Checking the source at e.g. https://gitweb.gentoo.org/repo/gentoo.git/ would > get rid of any delay questions. Note: need to escape the hyphen, otherwise the server fails to produce relevant search results, so, for example: resolve\-march
