If /etc/make.conf contains an APACHE2_MODULES="..." line, then flaggie fails to even query the global USE flags: $ flaggie ?xattr Traceback (most recent call last): File "/usr/bin/flaggie-2.7", line 25, in <module> sys.exit(main(sys.argv)) File "/usr/lib64/python2.7/site-packages/flaggie/cli.py", line 205, in main actset(pfiles) File "/usr/lib64/python2.7/site-packages/flaggie/action.py", line 246, in __call__ a(self.pkgs, pfiles) File "/usr/lib64/python2.7/site-packages/flaggie/action.py", line 183, in __call__ for pe in puse[p]: File "/usr/lib64/python2.7/site-packages/flaggie/packagefile.py", line 308, in __getitem__ for e in self.makeconfvar: File "/usr/lib64/python2.7/site-packages/flaggie/makeconf.py", line 277, in __iter__ self.parseflags() File "/usr/lib64/python2.7/site-packages/flaggie/makeconf.py", line 234, in parseflags self._useexpanded[t.use_expanded].remove(flag.name) KeyError: u'apache2_modules_so'
Ok, the exact problem here is that 'apache2_modules_so' USE is not described in profiles/desc/apache2_modules.desc. Please report that as well. For flaggie, I'll take a look at it in the next few days. As a temporary solution, you may either describe 'so' in the file mentioned above or just drop it from APACHE2_MODULES.
[master 07cb063] Fix failure when USE_EXPAND vars contain invalid flags. 1 files changed, 1 insertions(+), 1 deletions(-) If you could test the -9999 version (from mgorny overlay), that'd be great. You can also manually look for 'remove(' in makeconf.py and replace it with 'discard('.
> If you could test the -9999 version (from mgorny overlay), that'd be great. You > can also manually look for 'remove(' in makeconf.py and replace it with > 'discard('. Doing the replacement of s/remove(/discard(/ worked. Thanks.
Fixed in 0.1.3.
