leaving aside the fact that I consider beclock the best clock in the world, better than rolex 
and that I cannot live without it.
how can I say to the people that fill suse repositories KDE extra that the version 0.14-1.5 is obsolete??
and that in the site of the developer there is the 0.16 version that works perfectly on my KDE4.7??
and that I will pay a couple of beers to have the last version on suse repos??
thankyouverymuch
On 01/26/2012 02:06 PM, pier andreit wrote:
> 0.14-1.5 is obsolete . . . there is the 0.16
what are the features available in .16 that you need?
and, how big is your need for them?
ā
DD http://tinyurl.com/DD-Caveat
have you TODAY checked what they say about us at
http://tinyurl.com/SUSEonDW
disappearing on mouse hoover, 0.14-1.5 doesnāt works with KDE4.7 and 4.8, and date as I like, 2012-jan-26 and not 2012/01/26
big, very big, like a loaf of bread, I cannot stay without bread, and beer 
On 01/26/2012 06:06 PM, pier andreit wrote:
> I cannot stay without bread, and beer:)
well then! if it is as important as bread and beer, then just go ahead
and compile it locallyā¦
the easy steps are here: http://kde-apps.org/content/show.php?content=117542
ā
DD
have you TODAY checked what they say about us at
http://tinyurl.com/SUSEonDW
of course Iāve already done:), I tried to survive with meat and wineā¦ , meat and bearā¦ , but I cannot survive without breadā¦
after compilation it works perfectly, but Iām on tumbleweed so when often I update sometimes updating involve beclock too, I have to recompile, and as I think 98% of suselinuxkde users use this marvellousgorgeaouscannotlivewithout clock:), they will be happy to have this new working version on our reposā¦
On 01/26/2012 09:06 PM, pier andreit wrote:
> 98% of suselinuxkde users
maybe you, or one of the others there would like to step up and be the
maintainer for that packageā¦and, get it ready for factoryā¦once there
(and has shown stability) it can move to Tumbleweed (but not before)ā¦
ā
DD http://tinyurl.com/DD-Caveat
have you TODAY checked what they say about us at
http://tinyurl.com/SUSEonDW
Iām only a user, I havenāt skill to be a maintainer 
I can test it, and in kde4.7 is about 1 month it is working, no crash, and it seem stable, but the question was also another, is to post here the proper/better way to ask to the maintainers (that I suppose are the people that fill the repos) to update/upgrade the beclock??
On 01/27/2012 01:56 PM, pier andreit wrote:
> in kde4.7 is about 1 month it is working, no crash,
> and it seem stable
so, if you have it running then why do you want it in the Tumbleweed repo?
ā
DD
Read about openSUSE
becouse I think is better to have the last well working version in repos, and Iām on tumbleweed so when often I update, sometimes updating involve beclock too, I have to recompileā¦
On 01/27/2012 06:16 PM, pier andreit wrote:
> becouse I think is better to have the last well working version in
> repos
wellā¦you idea of what should be in the repos and openSUSEās idea are
two different things, read this:
http://en.opensuse.org/openSUSE:Maintenance_policy
on the whole it says we fix bugs and security problem, we donāt just run
in the latest version because it is availableā¦now, i think there are
other distros which pander to the
must-have-the-newest-of-everythingā¦but, that is not openSUSEā¦
if you need the newest more than you need bread and beer you need to
learn how to compileāor find a distro with a different version update
strategyā¦
ā
DD
Read about openSUSE
but it also says
some cases it might be sensible to use the a new upstream version instead of applying a patch.
and I think it is the case
I donāt need the newest, I need a working version, I subscribed the maintenance mailing list, may be I can better understand policy and how to ask to upgrade many thanks :-))
On 01/28/2012 09:56 AM, pier andreit wrote:
>
> but it also says
> some cases it might be sensible to use the a new upstream version
> instead of applying a patch and I think it is the case.
noā¦the word āpatchā in used the context of a security patchā¦that
is, if there is found a security problem in (say) beclock, it will be
patched (in 11.4 and 12.1) as soon as possible.
however, and as an alternative: instead of patching 0.14 it might be
just as easy, or even a lot easier and quicker to lay 0.16 in the update
repo and fix the security problem that wayā¦
in other words: in general openSUSE does not update applications (like
beclock) in supported versions. but, that position is not held so
strongly that they wouldnāt take the easiest and quickest fix to solve
the security problem for 11.4 and 12.1
see the difference?
> I donāt need the newest, I need a working version
as far as i can tell from your posting there is a working version
(which is not needing a security patch) for 11.4 and 12.1, right?
DD
yes it doesnāt need of a security patch, but it doesnāt works well, the disappearing on mouse hoover is a need in this application, otherways it would be a simple clock plasmoid, better than plasmoid, but a simple clock. taking proper proportions it is as if kmail only receive email and donāt send, it works but not well.
On 01/28/2012 12:16 PM, pier andreit wrote:
>
> it doesnāt works well, the
> disappearing on mouse hoover is a need in this application
what? that is not a security problemā¦in fact it is not a problem that
anyone cares enough about to even log a bug:
https://bugzilla.novell.com/buglist.cgi?quicksearch=beclock
so, why should anyone even consider going to the trouble of packaging
0.16 for something so minor that even strong proponents of the
application (like yourself) will neither log a bug nor do more than ask
someone else to do more workā¦
ā
DD
Read about openSUSE
Yes, I didnāt say that it was a security problem only that is a no-well-working problem
becouse I donāt know how many problems involve a compilation of beclock, I ask to the beclock developer that there was a problem in beclock, he solved, and, as I am only a user, I supposed it was simple and automatic in suse upgrade a such simple application as that I succeed even to compile it by myself on my pcā¦
I didnāt know that for to have an upgraded application in the repos it needs to open a bug, I will open a bug in novellā¦ :-))
On 01/28/2012 04:26 PM, pier andreit wrote:
> I didnāt know that for to have an upgraded application in the repos it
> needs to open a bug, I will open a bug in novellā¦
you miss the point entirely.
openSUSE does not rotate in new versions just because they are available.
ā
DD
Read what Distro Watch writes: http://tinyurl.com/SUSEonDW
Iām not asking a new version because it is just available, Iām asking a new version because the old version works bad.
On 2012-01-28 16:54, DenverD wrote:
> On 01/28/2012 04:26 PM, pier andreit wrote:
>> I didnāt know that for to have an upgraded application in the repos it
>> needs to open a bug, I will open a bug in novellā¦
>
> you miss the point entirely.
>
> openSUSE does not rotate in new versions just because they are available.
Thatās entirely up to the repo maintainer. If it is an official repo, they
are quite conservative. Other repos are not.
ā
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 āCeladonā at Telcontar)
On 01/28/2012 11:03 PM, Carlos E. R. wrote:
>> openSUSE does not rotate in new versions just because they are available.
> Thatās entirely up to the repo maintainer. If it is an official repo, they
> are quite conservative. Other repos are not.
you are correct Carlos, what i meant to say was:
the oss and non-oss repos never change and openSUSE does not rotate new
versions of applications into the update repo just because a new version
was released somewhereā¦
and, new application donāt spring up in Tumbleweed until after they have
been added to and satisfactorily tested in Factoryā¦
however, openSUSE users are free to compile and install whatever they
want at anytimeā¦
ā
DD
Read what Distro Watch writes: http://tinyurl.com/SUSEonDW
On 2012-01-28 23:17, DenverD wrote:
> the oss and non-oss repos never change and openSUSE does not rotate new
> versions of applications into the update repo just because a new version
> was released somewhereā¦
>
> and, new application donāt spring up in Tumbleweed until after they have
> been added to and satisfactorily tested in Factoryā¦
All correct
> however, openSUSE users are free to compile and install whatever they want
> at anytimeā¦
Yep, we are. But there are so many repos that now Iām lazy and donāt build
anything. 
ā
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 āCeladonā at Telcontar)