jaunty: update-motd doesn't clear previous runs if a script is removed/disabled

[Andreas Hasenack]

Binary package hint: update-motd

In jaunty, I don't think the files in /var/run/$NAME/<scriptoutput> are ever cleared

I removed landscape-sysinfo and /var/run/motd keeps the old output forever, and /var/run/$NAME/50-landscape-sysinfo still exists from previous runs

This doesn't happen in intrepid.

[Dustin Kirkland  (kirkland)]

Well, "never" cleared isn't quite correct...

/var/run is cleared on every reboot. So at the very worst, those
items are removed on reboot.

That said, I can see where this might be a problem on Jaunty. But it
should never be a problem in Karmic.

Can you try to reproduce there? I think this bug will be a "Fix
Released" for Karmic, and a "Won't Fix" for Jaunty (in that I don't
think this rises to the SRU requires for a stable release fix.)

:-Dustin

[Andreas Hasenack (ahasenack)]

Right, it doesn't happen in karmic.

[Dustin Kirkland  (kirkland)]

Okay, in that case, I'm marking 'fix released' in karmic, and 'won't fix' in jaunty. Thanks for the report, but I don't think we're going to be able to get an SRU through for something like this for jaunty.

Cheers,
:-Dustin