emerge libgzz-0.0.7.ebuild error output: In file included from hashfunc.c:4: /usr/include/gcrypt.h:227: parse error before "ulong" hashfunc.c: In function `hash_create_private': hashfunc.c:12: `GcryMDHd' undeclared (first use in this function) hashfunc.c:12: (Each undeclared identifier is reported only once hashfunc.c:12: for each function it appears in.) hashfunc.c:12: parse error before "handle" hashfunc.c:24: warning: implicit declaration of function `strcmp' hashfunc.c:35: `handle' undeclared (first use in this function) hashfunc.c:42: warning: implicit declaration of function `strlen' make[4]: *** [hashfunc.lo] Error 1
I can reproduce this.
Fixed it - it depends on libgcrypt-1.1.8 which is not yet marked as stable. Mike, I also marked libgzz-0.0.7 as ~arch instead of stable. Think this was an accident?
dont add me to cc's ... i'm on the games team
it was not an accident i put it in as stable ... i just missed the fact that it required an unstable ver of gcrypt if you marked libggz as ~ you're gonna have to mark the other 4 ggz ebuilds that depend on it as ~ too ;)
I added you to CC: because it was you who made the change that caused this bug. You did not announce this version becoming stable as you should have if it was intended. You made 0.0.7 immediately stable which - please correct me if I am wrong - is against our development policy, paragraph after "Moving package versions from ~ARCH to ARCH" - or is 0.0.7 an important bugfix or security update? That's why I thought it was an accident. You are right, I didn't check what depends on this version, but I thought it riskless because I was too sure it was just a mistake. Please decide if you'd prefer to get libgcrypt 1.1.8 to stable or make ggz 0.0.7 ~arch. If you do the former, don't forget to announce on -core.
dont add me to cc's ... i'm on the games team games owns this bug ... thus i get 2 e-mails ;)
