Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 788394 - app-portage/smart-live-rebuild: media-libs/freetype-9999: [KeyError] "Environment does not declare: ['EGIT_REPO_URI']"
Summary: app-portage/smart-live-rebuild: media-libs/freetype-9999: [KeyError] "Environ...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Lars Wendler (Polynomial-C)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-05 16:55 UTC by Vincent Grande
Modified: 2021-06-29 20:58 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
freetype-9999 log of @smart-live-rebuild (freetype-9999log.txt,18.72 KB, text/plain)
2021-05-05 16:55 UTC, Vincent Grande
Details
new freetype2-9999 log (newfreetype-9999log.txt,19.61 KB, text/plain)
2021-05-05 19:52 UTC, Vincent Grande
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Grande 2021-05-05 16:55:55 UTC
Created attachment 706206 [details]
freetype-9999 log of @smart-live-rebuild

When im doing a @smart-live rebuild. I get this error in my terminal for the freetype-9999 ebuild. freetype always needs to be updated after i do a @smart-live-rebuild, it is actually pulling the latest git master?

Error enumerating =media-libs/freetype-9999: [KeyError] "Environment does not declare: ['EGIT_REPO_URI']"

Log is attached.
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-05-05 16:58:20 UTC
Interestingly it doesn’t define it in global scope.
Comment 2 Sergei Trofimovich (RETIRED) gentoo-dev 2021-05-05 17:09:05 UTC
> media-libs/freetype-9999:2::localrepo 

Can you attach your ebuild of freetype-9999? It looks like it's not a ::gentoo one.
Comment 3 Vincent Grande 2021-05-05 19:51:14 UTC
Thats very odd, I check my localrepo and didnt have a freetype ebuild in any directory. So I re emerged freetype-9999 and now it does indeed say gentoo. It still doesnt sync git master properly though. 

New log attached.
Comment 4 Vincent Grande 2021-05-05 19:52:05 UTC
Created attachment 706218 [details]
new freetype2-9999 log
Comment 5 Lars Wendler (Polynomial-C) gentoo-dev 2021-05-05 23:05:16 UTC
Please post the output of

  emerge --info freetype

to this bug.

May I ask where the target "@smart-live-rebuild" comes from? All I can find in my portage installation is the "@live-rebuild" target.
Comment 6 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-05-05 23:07:30 UTC
(In reply to Lars Wendler (Polynomial-C) from comment #5)
> 
> May I ask where the target "@smart-live-rebuild" comes from? All I can find
> in my portage installation is the "@live-rebuild" target.

https://packages.gentoo.org/packages/app-portage/smart-live-rebuild

It’s a delight. It checks upstreams for changes so you only rebuild live ebuilds where the content has actually changed!
Comment 7 Lars Wendler (Polynomial-C) gentoo-dev 2021-05-05 23:12:57 UTC
Yeah, found this right now. This seems to be a problem specific to app-portage/smart-live-rebuild package.

@Michał: freetype-9999 does not globally declare EGIT_REPO_URI because it needs to conditionally access a second git repo depending on the "utils" USE flag.
Comment 8 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2021-05-05 23:45:55 UTC
The package doesn't come with a crystal ball.  It needs the data in the environment in order to operate.
Comment 9 Vincent Grande 2021-05-06 01:16:17 UTC
So does the this ebuild still pull form git master, it just cant fetch the latest commit, is that corrent? Meaning, I can use --exclude freetype if need be since it builds from master everytime?
Comment 10 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2021-05-06 07:00:51 UTC
Ok, with a morning brain: the solution is simple.  Put the main URL in the global scope (either by declaring it globally, or not using 'local'), then make sure to always fetch it second, so that the data in the environment corresponds to that.
Comment 11 Lars Wendler (Polynomial-C) gentoo-dev 2021-05-10 09:31:53 UTC
(In reply to Michał Górny from comment #10)
> Ok, with a morning brain: the solution is simple.  Put the main URL in the
> global scope (either by declaring it globally, or not using 'local'), then
> make sure to always fetch it second, so that the data in the environment
> corresponds to that.

Okay, will give that a spin. Do you mind if I ask you for review?
Comment 12 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2021-05-10 14:45:45 UTC
Sure, no problem.