basc-1.5.3 is out. On details on which changes were made, please look into the ChangeLog: http://www.gentoo-stats.org/index.php?c=changelog There were many bug fixed. One bug caused basc to exit. Please test and add this ebuild to the tree. There were no platform-dependent changes made, so all arches, which are marked as stable in the ebuild are still tested and stable. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 47337 [details] basc-1.5.3.ebuild
Created attachment 47338 [details] basc-1.5.3.ebuild first ebuild was the wrong one, please excuse...
Running the client for the first time: - einfo " \"basc -u\"." + einfo " \"basc\"" Crontab entry: - einfo " \"0 0 * * * /usr/bin/basc -q >/dev/null 2>&1\"" + einfo " \"0 0 * * * /usr/bin/basc -q -y >/dev/null 2>&1\"" Do users upgrading from 1.5.2 need to change this?
They *need* to change nothing. But the options were new in 1.5.2, not in 1.5.3, and if the users always want to submit their x11-config and kernel-config too, *then* they have to add the -y option to the crontab. But as I said, this was new in 1.5.2, not in 1.5.3 To run the client, only `basc` is needed, because the -u option only does a forced update, which also updates the data in the database, if the time between two updates is less than 24h. To prevent the server in being slow, the client should not update more than once every 24h. But this option is also not new too. It was added somewhere in 1.3.x.
in cvs
