User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5) KHTML/3.5.5 (like Gecko) Build Identifier: When portage connects to the URL described in the ebuild to download the source code, it can't connect because the file not exists. Reproducible: Always Steps to Reproduce: 1.emerge styleclock 2. 3. Actual Results: It can't to download the sources. Expected Results: Download the tarball.
Kindly review https://bugs.gentoo.org/page.cgi?id=fields.html#bug_severity
I can't find a copy of this program anywhere. Cna you point me to where it can be found?
RESTRICT="nomirror" and homepage returns 404 = p.mask
I put up a copy of the sources at http://dev.gentoo.org/~truedfx/styleclock-0.5.1.tar.gz so if you are interested in keeping the package (I don't care much either way), you can put it on the mirrors.
Ok, we have the package, I can keep it on my box too. What can be done to rescue the package?
(In reply to comment #5) > Ok, we have the package, I can keep it on my box too. What can be done to > rescue the package? I'm not that happy keeping a package that has no upstream, and I'm still unsure why it had RESTRICT="mirror" when its license was GPL-2. As a compromise, I'd rather put it in my overlay/sunrise if people really want to , and take out of portage. If the kde team/other devs think differently, feel free to comment and we can try and thrash something out, but I imagine they will feel much the same way.
Maybe I cannot understand well what "no upstream" means... The only problem is that author's page gone for unknown reasons. The current version is working well, there's no single bug regarding styleclock (I understand that in famous xmms case it was different, there were bunch of unfixable bugs etc.). Why to remove package when you can just add local mirror and nobody will suffer? Latest version is not new (Dec 2004) but this is not a problem alone I guess.
(In reply to comment #7) > Maybe I cannot understand well what "no upstream" means... The only problem > is that author's page gone for unknown reasons. The problem is that the author ('upstream'), has vanished, and therefore won't be making any new releases. This means if there is a problem with the package, its not going to be fixed in a new version, because there won't be any new versions. > The current version is working > well, there's no single bug regarding styleclock That's true. > Why to remove package when you can just add local mirror and nobody will > suffer? Because I'm not interested in maintaining a package without an active upstream, and I doubt many other people are either. > Latest version is not new (Dec 2004) but this is not a problem alone I guess. > If we chose not to remove it, we could bump it... Do you have a problem with just getting it out of my overlay? Without an upstream there aren't going to be any bumps, so you could just move it locally if you wanted... Kde team, any thoughts?
> The problem is that the author ('upstream'), has vanished, and therefore won't > be making any new releases. In my world people don't vanish (tough sites sometimes do) ;) > This means if there is a problem with the package, > its not going to be fixed in a new version, because there won't be any new > versions. If the author is still not available the maintainer can fix it or wait for somebody to do it. But there are no bugs (I wouldn't object otherwise). > I'm not interested in maintaining a package without an active upstream, > and I doubt many other people are either. How much time does it take to maintain package that has no new versions and no bugs to fix? :) I really like the applet and I'd be willing to fix the problems (if they'd show up), I'm not the gentoo-dev but can submit patches via bugzilla. > Do you have a problem with just getting it out of my overlay? Without an > upstream there aren't going to be any bumps, so you could just move it locally > if you wanted... It's not a problem for me alone, I know how to use remote or local overlays etc. but from my point of view it's just bad PR - I work at unversity and many times I'm asked (by students or co-workers) about gentoo, my environment, suggestions etc. Frequently it's just "hey, what's that app? I'd love to have the same! How can I get it" - it's much easier to say "emerge styleclock" then explain overlays, layman etc. It's not the first application that was removed because of being too old. Portage-tree-cleaners should consider that number of supported packages is one of the main reasons people use gentoo.
Please keep this one in portage! I haven't had any problems with it ever. Are there any kde people to chime in? Styleclock is one of the nicest applets for KDE Panel and it would shame to loose it!
I a m interested in keeping this package too. Why not point the ebuild to: http://dev.gentoo.org/~truedfx/styleclock-0.5.1.tar.gz? We can always remove if it becomes defunct.
Let me rephrase the question. How can I participate in keeping this ebuild?
Due to all your comments, I've decided not to remove this package.
(In reply to comment #13) > Due to all your comments, I've decided not to remove this package. > Thanks! That's good news :D
