I've released the newest version of BasKet Note pads, with some fixes (mainly it won't constantly access the disk when a key is pressed in most notes); I've also applied the GCC 4.3 patch from the last version. Reproducible: Always
Created attachment 157009 [details] ebuild
Created attachment 158907 [details] basket-1.0.3-desktop-entry-fix.diff
Please pick up the attached patch, Kelvie.
(In reply to comment #3) > Please pick up the attached patch, Kelvie. > Thanks for the patch. I'll push out a 1.0.3.1 release probably tomorrow (after a bit of testing).
Hmm, with your patch, Portage tells me this: * /usr/share/applications/kde/basket.desktop: value "application/x-basket-archive;application/x-basket-template;;" for key "MimeType" in group "Desktop Entry" contains value "" which does not look like a MIME type Is that normal? Portage 2.1.5.4 (default-linux/amd64/2007.0/desktop, gcc-4.2.4, glibc-2.7-r1, 2.6.25-gentoo-r4 x86_64)
(In reply to comment #5) Silly me. I removed the line from the ebuild that works around the bug that this patch fixes.
Okay, I've released 1.0.3.1 with some more minor fixes: - your patch - Danish translations. The src_unpack function just needs to be remove from the ebuild (of course).
Thanks for the fast response! 1.0.3.1 is now in CVS.
Any reason this is still marked as unstable?
(In reply to comment #9) > Any reason this is still marked as unstable? > Open a stable request if you want some application stable.
(In reply to comment #10) > (In reply to comment #9) > > Any reason this is still marked as unstable? > > > > Open a stable request if you want some application stable. Is there a procedure to do this, or do I just open a new bug with the title saying "Please mark stable"?
(In reply to comment #11) > (In reply to comment #10) > > (In reply to comment #9) > > > Any reason this is still marked as unstable? > > > > > > > Open a stable request if you want some application stable. > > Is there a procedure to do this, or do I just open a new bug with the title > saying "Please mark stable"? > See you deduced it correctly on the first run. So chop chop ;]