Re: bug in Solaar 1.1.5
I see no reason to hold up any Ubuntu release for Solaar. I'm not even sure that there is a problem with Solaar in Ubuntu. All that I have is a single report from a user - I have not looked at the distribution at all. peter On 10/17/22 18:47, Steve Langasek wrote: Hi Peter, On Tue, Oct 11, 2022 at 05:45:33AM -0400, Peter F. Patel-Schneider wrote: Hi: I'm the maintainer of Solaar. It appears that Solaar for Ubuntu was recently upgraded from version 1.1.1 to version 1.1.5. I have a report that something went wrong when he ran Solaar 1.1.5 - https://github.com/pwr-Solaar/Solaar/issues/1785 I'm not sure why he ended up with an empty ~/.config/solaar/config.yaml file. I don't see a path in the code that would make this file empty. I'm going to patch the file to handle this issue though. Unfortunately, we are now 3 days away from the Ubuntu 22.10 release. It's unclear to me if any Ubuntu Developers will step up and have an opportunity to upload a fix to this for inclusion in the 22.10 release before then. (As a member of the Release Team, I personally would definitely not!) Given that you say it's unclear how this broken config file ever happened, unless there are more users reporting the same breakage we might just have to accept this defect for 22.10. If you think it's important enough to warrant a post-release update of the package, the Ubuntu process is here: https://wiki.ubuntu.com/StableReleaseUpdates -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: bug in Solaar 1.1.5
Hi Peter, On Tue, Oct 11, 2022 at 05:45:33AM -0400, Peter F. Patel-Schneider wrote: > Hi: > I'm the maintainer of Solaar. It appears that Solaar for Ubuntu was > recently upgraded from version 1.1.1 to version 1.1.5. I have a report that > something went wrong when he ran Solaar 1.1.5 - > https://github.com/pwr-Solaar/Solaar/issues/1785 > I'm not sure why he ended up with an empty ~/.config/solaar/config.yaml > file. I don't see a path in the code that would make this file empty. I'm > going to patch the file to handle this issue though. Unfortunately, we are now 3 days away from the Ubuntu 22.10 release. It's unclear to me if any Ubuntu Developers will step up and have an opportunity to upload a fix to this for inclusion in the 22.10 release before then. (As a member of the Release Team, I personally would definitely not!) Given that you say it's unclear how this broken config file ever happened, unless there are more users reporting the same breakage we might just have to accept this defect for 22.10. If you think it's important enough to warrant a post-release update of the package, the Ubuntu process is here: https://wiki.ubuntu.com/StableReleaseUpdates -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
bug in Solaar 1.1.5
Hi: I'm the maintainer of Solaar. It appears that Solaar for Ubuntu was recently upgraded from version 1.1.1 to version 1.1.5. I have a report that something went wrong when he ran Solaar 1.1.5 - https://github.com/pwr-Solaar/Solaar/issues/1785 I'm not sure why he ended up with an empty ~/.config/solaar/config.yaml file. I don't see a path in the code that would make this file empty. I'm going to patch the file to handle this issue though. peter -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
