tag 659026 moreinfo thanks On Tue, 2012-04-24 at 00:55:16 +0200, Aurelien Jarno wrote: > On Sat, Feb 18, 2012 at 06:21:38PM +0100, lo...@van-belle.nl wrote: > > Le 07/02/2012 16:19, Aurelien Jarno a écrit : > > > On Tue, Feb 07, 2012 at 03:48:49PM +0100, Louis wrote: > > > > Package: lm-sensors > > > > Version: 1:3.3.1-2 > > > > Severity: normal
> > > > * What led up to the situation? > > > > my customs sensors output is now thedefault again. > > > > * What exactly did you do (or not do) that was effective (or > > > > ineffective)? > > > > apt-get update && apt-get upgrade was what i did. > > > > * What was the outcome of this action? > > > > custom file in /etc/sensors.d was remove while upgrading. > > > > * What outcome did you expect instead? > > > > own files created in /etc/sensors.d should never be deleted. > > > > The own file i created for my mainboard, placed in /etc/sensors.d > > > > was removed after upgrading to this version. This should not happen. > > > From which version to which version did you upgrade? Are you sure it is > > > not related to another issue (like a fsck on the filesystem)? There is > > > nothing in lm-sensors that can remove this file. > > Concerning this upgrade. > > my setup is a basic debian wheezy installation, used for XBMC setup. ( > > look here for more info about that, http://thuis.van-belle.nl > > lm-sensors installed, made no changes to the default files > > i created my own file, this one here. > > http://thuis.van-belle.nl/asrock-m350_usb3.conf > > i did put this file in the /etc/sensors.d/ folder. > > after upgrading to this version of lm-sensors. > > > > > Package: lm-sensors > > > > > Version: 1:3.3.1-2 > > the file i created in /etc/sensors.d was deleted from the system > > after/while upgrading. > > since i didnt remove this file, the upgrade procedure must have done this. > > > > upgrade was from version : 1:3.3.1-1 > > im running amd64 brance. > Here is a bug report concerning a file non handled by dpkg, in a > directory installed by a package (namely /etc/sensors.d/) that has been > lost during an upgrade. Given there is a .placeholder file in this > directory and that nothing in the maintainer scripts remove files, it > might be a dpkg issue. Therefore I am reassigning the bug there. Well, I don't really see how dpkg can be doing this, I've tried to reproduce it anyway by upgrading from libsensors4, lm-sensors 1:3.3.1-1 to 1:3.3.1-2 (just in case), and I don't get the file to disappear. My take is that either the submitter accidentaly removed the file w/o noticing, there was some kind of disk corruption, or something else removed that file during that upgrade, maybe a package from a third party repository... W/o more information and a reproducible test case, I fear there's not much more that can be done, and as consequence the only remaining course of action would be to close this report in a bit. thanks, guillem -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
