View previous topic :: View next topic |
Author |
Message |
lekto Apprentice
Joined: 20 Sep 2014 Posts: 207 Location: Ancient Rome
|
Posted: Thu Jul 18, 2024 2:17 pm Post subject: Get commit on genlop. |
|
|
When running genlop -t on a package that is installed in a git version, I get only the version number from portage:
Code: | lekto@lapek ~ $ genlop -t transgui
* net-p2p/transgui
Sun Sep 18 07:57:02 2022 >>> net-p2p/transgui-9999
merge time: 56 seconds.
Thu Mar 23 18:36:03 2023 >>> net-p2p/transgui-9999
merge time: 29 seconds.
Sat Apr 29 15:40:07 2023 >>> net-p2p/transgui-9999
merge time: 27 seconds.
Sun May 21 10:44:34 2023 >>> net-p2p/transgui-9999
merge time: 31 seconds.
Sun May 28 21:44:55 2023 >>> net-p2p/transgui-9999
merge time: 33 seconds.
Fri Nov 3 20:04:56 2023 >>> net-p2p/transgui-9999
merge time: 1 minute and 20 seconds.
Tue Mar 12 19:28:27 2024 >>> net-p2p/transgui-9999
merge time: 30 seconds.
Thu Jun 6 17:41:32 2024 >>> net-p2p/transgui-9999
merge time: 27 seconds. |
Is there a way to show exactly what commit each merge was? |
|
Back to top |
|
|
logrusx Advocate
Joined: 22 Feb 2018 Posts: 2405
|
Posted: Thu Jul 18, 2024 2:24 pm Post subject: Re: Get commit on genlop. |
|
|
lekto wrote: | When running genlop -t on a package that is installed in a git version, I get the version number from portage:
Code: | lekto@lapek ~ $ genlop -t transgui
* net-p2p/transgui
Sun Sep 18 07:57:02 2022 >>> net-p2p/transgui-9999
merge time: 56 seconds.
Thu Mar 23 18:36:03 2023 >>> net-p2p/transgui-9999
merge time: 29 seconds.
Sat Apr 29 15:40:07 2023 >>> net-p2p/transgui-9999
merge time: 27 seconds.
Sun May 21 10:44:34 2023 >>> net-p2p/transgui-9999
merge time: 31 seconds.
Sun May 28 21:44:55 2023 >>> net-p2p/transgui-9999
merge time: 33 seconds.
Fri Nov 3 20:04:56 2023 >>> net-p2p/transgui-9999
merge time: 1 minute and 20 seconds.
Tue Mar 12 19:28:27 2024 >>> net-p2p/transgui-9999
merge time: 30 seconds.
Thu Jun 6 17:41:32 2024 >>> net-p2p/transgui-9999
merge time: 27 seconds. |
Is there a way to show exactly what commit each merge was? |
No. If you haven't cleaned your distfiles, you may be able to find out what commit was the last build from, bu all the previous are lost.
You may be able to cross check the date in emerge.log and git history to see approximately what commit was used. If you're lucky and there weren't other commits in that day, you could even find out the exact one.
Best Regards,
Georgi |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6145 Location: Dallas area
|
Posted: Thu Jul 18, 2024 2:25 pm Post subject: |
|
|
emerge --info -v and look for EGIT3_STORE_DIR
Go to that directory, find git repo, cd to that, do "git log" to see commits.
for wlroots, it's "wlroots_wlroots.git" _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Chiitoo Administrator
Joined: 28 Feb 2010 Posts: 2728 Location: Here and Away Again
|
Posted: Thu Jul 18, 2024 9:42 pm Post subject: |
|
|
The log file for the actualy build would also show the commit, if still available. _________________ Kindest of regardses. |
|
Back to top |
|
|
|