© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hi @gstrauss
sorry about your frustration with the time_t transition. It was very hard on Ubuntu due to the noble release, and even though debian has more time, I'm sure it's difficult for them as well.
lighttpd in Ubuntu is in the universe repository, meaning it's maintained by the community at large. That being said, we try to avoid really hard to go ahead of debian in a new upstream release, and we generally don't do that for universe packages.
I see you attached many patches to this bug, and it's bit convoluted now. The original intent of this bug is to update to the latest upstream release. For the ubuntu development release, I can say we will only update to a new upstream version on top of a new debian update, i.e., if debian updates to (say) 1.4.76, then ubuntu can rebase on top of that. That's because since the package is in universe, there is no specific team committed to maintaining it.
For stable releases, updating the package goes through a different mechanism. We have the SRU[1] process for such updates, and each one has to be analized, justified, end evaluated, against that criteria. Version changes are generally frowned upon, with individual patches being preferred. There are pros and cons, and the documentation goes over them at length. If you wish to propose an SRU for lighttpd for some ubuntu release, then that process must be followed.
I'll leave this bug open because at some point debian will get 1.4.76 (or later), and when we rebase on top of that, we can close the bug.
Hope this helps.
1. https:/