Hi, On Sat, Jul 25, 2009 at 03:40:25PM +0200, Jan Christoph Nordholz wrote: > Hi. > > I'm still looking for an upgrade path that reproduces this bug. > Up to 4.0.3-0.3 /var/run/screen was part of the package tarball > (and mode 0775 root:utmp), then it got moved out of it and its > creation postponed to the initscript (for volatile /var/run mounts) > or postinst - also root:utmp and with permissions in accordance > to the setid bits on the binary. > > It would be great if you could show me a way to see this happen > myself. Until then I don't want to change the lines in the initscript > and probably "cover" the bug.
Sorry, I don't have an "upgrade path". I only do the sporadic "apt-get upgrade" and an "apt-get dist-upgrade" once in a blue moon. Sometimes things don't work out and when I report that they just say "upgrading from xxx to yyy is not supported" even though I have no intention to nor would I have know that my apt-get upgrade would have resulted in something unsupported. Basically I feel that this points to a design flaw in the apt system, but I have said that before and people had not agreed with me, though I cannot understand why. > > > Regards, > > Jan Regards, -- Ambrose Li <ambrose...@cccgt.org> Webmaster & de-facto in-house graphic artist Chinese Cultural Centre of Greater Toronto / http://www.cccgt.org/ 5183-5193 Sheppard Avenue East, Toronto, Ontario, Canada M1B 5Z5 +1 416 292 9293 / FAX +1 416 292 9215 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
