Custom Query (1438 matches)
Results (325 - 327 of 1438)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1424 | fixed | drivedb.h: Add VERSION information which works without $Id$ expansion | ||
| Description |
In Debian smartmontools#976696, to avoid the monthly debsums cron job complaining that the files in the Debian smartmontools package had been modified after update-smart-drivedb got run, I requested that the Debian maintainer install the drivedb.h from the smartmontools tarball into /usr and then in the postinstall script run at package install time, copy it to the canonical location in /var. The package maintainer implemented that with unconditional copying of the file, with a TODO item to improve that. I noticed that the update-smart-drivedb script also does unconditional copying. The unconditional copying in both the Debian postinstall script and in update-smart-drivedb means that they will both clobber each other's changes. So there needs to be some more sophisticated mechanism to figure out whether or not to update the drivedb.h file. Possibly the branch name plus the revision number or date from the $Id$ expansion could be useful for checking if the drivedb.h file should be updated, however... I noticed that some of the URLs used by the update-smart-drivedb script do not have $Id$ expansion and the drivedb.h on my system downloaded by update-smart-drivedb does not have $Id$ expansion. Also the drivedb.h file within the Debian package does have $Id$ expansion. So if the URLs with missing $Id$ expansion could be fixed or removed, then the branch name plus the revision number or date from the $Id$ expansion could potentially be removed for a version. Alternatively, a manually committed revision number could be added to the file. In addition, I think it would be nice if the Debian package maintainer did not have to re-implement the proposed version checks in the Debian postinstall script, so I suggest that a --local option for update-smart-drivedb could be used to make it look at a local directory for drivedb.h, check the versions and then update the canonical drivedb.h. Then the Debian postinstall script could just run that. I have CCed onlyjob, the Debian package maintainer. |
|||
| #1423 | duplicate | Micron_5300_MTFDDAK480TDS | ||
| Description |
Micron_5300_MTFDDAK480TDS |
|||
| #1421 | fixed | C300-MTFDBAK128MAG | ||
| Description |
Attached you find the txt output file according to FAQ if the drive is not in the smartctl/smartd database. Under the following link there is some further device specification. https://www.newegg.com/micron-realssd-c300-128gb/p/N82E16820363001 |
|||
