Processed: Re: Fw: Message with no Package: tag cannot be processed! (Debian Lenny to Squeeze upgrade)

[Debian Bug Tracking System]

reassign 633159 upgrade-reports

Bug #633159 [general] Fw: Message with no Package: tag cannot be processed! (Debian Lenny to Squeeze upgrade)
Bug reassigned from package 'general' to 'upgrade-reports'.

tags 633159 squeeze

Bug #633159 [upgrade-reports] Fw: Message with no Package: tag cannot be processed! (Debian Lenny to Squeeze upgrade)
Added tag(s) squeeze.

quit

Stopping processing here.

Please contact me if you need assistance.

[Jonathan Nieder]

retitle 633159 lenny->squeeze: TeX breakage, upgrade-from-grub-legacy disables greeter
quit

Hi,

The bug is that after I installed Squeeze, the Tex distribution
totally died. And after I ran "upgrade-from-grub-legacy", the
graphical interface and greeter no long work.

One more pointer:
http://www.debian.org/releases/stable/amd64/release-notes/ch-about.en.html#upgrade-reports

Thanks again for your work to make Debian a little better.

Regards,
Jonathan

[Debian Bug Tracking System]

Post by Jonathan Nieder
retitle 633159 lenny->squeeze: TeX breakage, upgrade-from-grub-legacy disables greeter

Bug #633159 [upgrade-reports] Fw: Message with no Package: tag cannot be processed! (Debian Lenny to Squeeze upgrade)
Changed Bug title to 'lenny->squeeze: TeX breakage, upgrade-from-grub-legacy disables greeter' from 'Fw: Message with no Package: tag cannot be processed! (Debian Lenny to Squeeze upgrade)'

Post by Jonathan Nieder
quit

Stopping processing here.

Please contact me if you need assistance.

[Debian Bug Tracking System]

Your message dated Mon, 27 Feb 2017 21:34:36 +0200
with message-id <***@localhost>
and subject line Closing squeeze-only bugs
has caused the Debian Bug report #633159,
regarding lenny->squeeze: TeX breakage, upgrade-from-grub-legacy disables greeter
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)