This is the basc version 1.5.9. There were only trivial changes: - modified the wm-detection to detect the windowmaker correctly (one new regexp) - modified the detection of the install-date to the filedate of /etc/gentoo-release instead of /etc/localtime - added the submission of user modified locale (LC_TIME) For more details, please take a look into the changelog: http://www.gentoo-stats.org/index.php?c=changelog This is also a request for stable keywords. It is very good tested on x86 and it's absolutly stable. Please test it again on the other arches and mark it stable if you can and want. The last bug related to the client itself was at 2005-01-22 and it was fixed in 1.5.8, later bugs were cosmetic bugs only and related to the gentoo-stats.org page only and are also fixed too (the last one was at 2005-02-14). Thanks. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 51621 [details] basc-1.5.9
Well it would be really nice if something could happen here...
hmmmmm... Okay, is there any reason not to add this version to the tree and/or not to mark it as stable? Would be really nice to know what's wrong.
Runs witout problems on P4 Xeon (kernel 2.6.10) and AMD64 (kernel 2.6.11.2).
Soryy, forgot a minor change to the ebuid. sys-apps/time is now sys-process/time
Created attachment 53418 [details] basc-1.5.9 Thanks for the note. I've changed this in the ebuild, here's the new one.
Taking this bug. I've commited version 1.5.9 of basc to portage, after going through the code and the ebuild with the package creator. I've cc'ed the arches that had previously marked basc, as well as mips to please consider re-evaluating the package. Yes, previous versions were removed that did have other keywords besides ppc and x86, but I believe that the latest version should eliviate all the issues behind it (ie. it has been code audited), and become the stable target. Should any problems occur, do not hessitate to contact me/add to the bug and I will get it fixed (ebuild or code wise). Thank you.
First of all, we're not re-evaluating this on mips. The main problem still hasn't been addressed, that being, the program does not report to an official gentoo website. Secondly, why are you even messing with this? A quick review of metadata.xml shows pvdabeel as the package maintainer. Didn't you get in trouble for messing with other parts of the portage tree that weren't maintained by you before?
The mips thing wasn't meant as a jab. I read the ChangeLog and it said that the mips keyword was removed for some reason and to let them know later when things have been fixed, that was simply what I was trying to do. I'm cc-ing pvdabell in case what I did was wrong, but afaik he really only does stable markings and what not. Secondly I've also added myself as co maintainer in metadata.xml to show that it isn't a "touch the package and run" situation. So once again, it wasn't meant to be agressive in any way, my appoligies if it was.
chriswhite has commitet the ebuild, so this bug should be closed (FIXED) now.
This won't run on ppc64. (CPU vendor unknown, so basc won't run) I've contacted the author in #gentoo-stats and he want's to release 1.6.0 with a fix for that. I'll test and mark that version stable as soon as it hits portage.
Why were all stable versions removed? Now there are only testing versions in the tree,
Eh? I still need the arches to mark it. To answer your question, 1.5.9 has been audited completly, and due to QA, I'd like to have it marked stable, and not the other versions which where not audited / could be insecure / whatever.
i added ~amd64, there was no keyword before
Thanks for testing and adding, Simon.
as gentoo-stats.org is dead, I removed ppc64 from CC. please readd if anything changes.
same for amd64
and mips
given that the site has been shut down no point in keeping this package.
