bug#22231: No upstream lm-sensors source

2016-01-09 Thread Leo Famulari
On Sat, Jan 09, 2016 at 06:45:06PM +0100, Ludovic Courtès wrote: > Also, when closing a bug, it’s a good idea to: > > 1. Write “Fixes .” in the commit log (see > ‘git log’ for examples.) D'oh! > > 2. Write the ID of the commit that closes the bug in the message

bug#22231: No upstream lm-sensors source

2016-01-09 Thread Ludovic Courtès
Leo Famulari skribis: > Let's close this bug. This is done by emailing nnn-d...@debbugs.gnu.org, as in this message. :-) See also and the emacs-debbugs package if Emacs is your thing. Thanks! Ludo’.

bug#22231: No upstream lm-sensors source

2016-01-09 Thread Ludovic Courtès
Also, when closing a bug, it’s a good idea to: 1. Write “Fixes .” in the commit log (see ‘git log’ for examples.) 2. Write the ID of the commit that closes the bug in the message to NNN-done. Ludo’.

bug#22231: No upstream lm-sensors source

2016-01-08 Thread Leo Famulari
On Thu, Dec 24, 2015 at 12:22:20PM -0500, Leo Famulari wrote: > The website lm-sensors.org has not been working for a few months now > [0]. > > This means we have no upstream source for the packages lm-sensors and > i2c-tools. I found the website of the primary author, and he maintains mirrors of

bug#22231: No upstream lm-sensors source

2015-12-24 Thread Leo Famulari
The website lm-sensors.org has not been working for a few months now [0]. This means we have no upstream source for the packages lm-sensors and i2c-tools. I've emailed the admin contact named by whois about the situation. [0] Some search engine results for "lm-sensors down" http://www.linux.org/