I'm aware of the upstream bug, but it says "fix committed" so we should push for deprecating this workaround. It also caused a build failure for me while trying to port games-board/pioneers to gnome-games.eclass.
The problem is that intltool upstream still didn't released a fixed version/tarball and, then, all games tarballs are still generated with wrong files from old/broken version. We need then to: 1. Get upstream to release a new version with the fix (I tried a lot without success) 2. Wait for the other upstreams to generate their tarballs with fixed version
how does that make this bug report invalid?
(In reply to Julian Ospald (hasufell) from comment #2) > how does that make this bug report invalid? Because it's run on purpose until the bug is solved as explained in comment #2, and it's with gnome-games.eclass, not gnome2.eclass (otherwise, where are you seeing that unconditional call in gnome2.eclass)
Right, it's gnome-games.eclass However, that still does not make the bug report INVALID.
upstream?
or "CANTFIX" (for now) :/, but I think we have better things than discussing the exact "term" to be used... CANTFIX looks better to me
well... I guess we have conflicting workflows then. I use bug reports to TRACK progress and keep them open until the problem is actually FIXED and not "MAY BE FIXED SOME DAY". Guess this was a waste of time then.
We will remember to drop that when we stop needing it ;), nobody wants to run eautoreconf forever if not needed
