Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] user editable weather API (weather and clock applet) #662

Open
pirate486743186 opened this issue Dec 3, 2023 · 4 comments
Open

Comments

@pirate486743186
Copy link

Right now the weather applet and the weather in the clock applet in bookworm are broken. This is not too uncommon since it relies on an API from some website to function.

It would be nice, that the API part resides in a script/text file, so that end users can easily fix it when it brakes.

@raveit65
Copy link
Member

raveit65 commented Dec 4, 2023

I did update fedora and rhel with fixed libmateweather.
Why debian maintainer didn't do the same?
.....ahh i forgot, debian politics don't allow quick fixes......

@pirate486743186
Copy link
Author

It's possible they didn't notice. You are part of the dev team while the bug is not critical. Usually Debian packagers actually use sid and i think the sid version is updated.

@pirate486743186
Copy link
Author

they updated it, i think it was in the point release.

@rubyFeedback
Copy link

rubyFeedback commented Feb 7, 2024

I did update fedora and rhel with fixed libmateweather.
Why debian maintainer didn't do the same?
.....ahh i forgot, debian politics don't allow quick fixes......

Upstream developers should not follow what downstream distribution maintainers do.

Instead the downstream distribution maintainers should pursue their own policy without
bothering upstream developers. The latter should just make sure that the source file
can be compiled; and, if possible, allow for enough flexibility to allow downstream
distribution maintainers to adjust to their liking. Both GNU configure and meson should
allow for that. I could see this issue with ruby, where new people use an ancient ruby
provided by debian stable, and then came to ruby devs asking why things don't work.
It always takes a while to explain to them that they need to ask the debian maintainers
(usually, unless it is a bug of course, and bugs happen, but debian has had an annoying
policy, e. g. removing mkmf and changing other things to "fit" within the debian ecosystem
aggressively).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants