On Sun, Aug 14, 2005 at 09:40:50PM +0100, Rob Bradford wrote: > On Sun, Aug 14, 2005 at 08:57:59PM +0200, Jens Seidel wrote: > > On Sun, Aug 14, 2005 at 11:18:06AM -0700, Debian Bug Tracking System wrote: > I'd closed the screem version of the bug in the anjuta changelog. Doh!. Even > though i'd included the patch in the last anjuta upload.
screem (= scream?)?? There was no new upload together with closing this bug according to http://packages.qa.debian.org/a/anjuta.html. > > I have a local GNOME CVS copy and noticed that my patch is not yet > > applied (yeah, the last CVS log of de.po mentions me, but this patch > > was found by checking GNOME CVS - independent of the patch in this > > bug!). > > I produced my own version of this patch against 1.2.3 vs 1.2.2. And then > forwarded the patch upstream and the German translation co-ordinator is > looking at it since the the release manager didn't want to apply it himself. No much work for him to do. I got my CVS account access a few minutes ago and applied the remaining parts of my patch. Please note that I checked the complete GNOME CVS too for typos in German translations, patches are still pending (since nearly 2 months). So you see the German coordinator is quite busy. > > Since I will get a CVS access soon it is OK for me to keep this bug > > closed. I will apply the remaining parts of my patch when I get my > > account. > > What remaining parts of the patch? Its quite possible that something got > missed when I forward ported to 1.2.3. If I have please let me know and file a > new bug or reopen this one. I talk about GNOME CVS, module anjuta (not anjuta2), HEAD, and you about the Debian source? For example s/ is ein / ist ein / was missing in upstream CVS. > Please note however that there will probably not be any more releases in the > 1.2.x branch for Anjuta and that 2.0.x is radically different. I know, but this is no reason for me not to solve open issues. Nothing of my patch applied for anjuta2. It seems also that I have no separate patch against anjuta2, strange :-)) Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
