Bug#365613: [pkg-wpa-devel] Bug#365613: wpasupplicant: Upgrading remote system makes it unmaintainable after reboot

[Felix Homann]

severity 365613 important
retitle 365613 Upgrading remote system makes it unmaintainable after reboot
unmerge 365613

On Monday 01 May 2006 17:19, Reinhard Tartler wrote:
> Severity wishlist, this does not break your whole system, but your
> network connection.

Making a system unmaintainable without warning seems very much like 
"critical" to me.

I set the severity to "important" as a compromise. 

> So I'm merging this with 360387, which is the same 
> issue.

It is not remotely the same issue. Unmerged the bug.

> This is a quite extreme and constructed example.

It is not constructed at all. It happened.

> You did know in advance 
> that this would break, as would have anyone who uses apt-listchanges,
> since this is written in Debian.NEWS.

I don't have apt-listchanges installed. But even in 
/usr/share/doc/wpasupplicant/NEWS.Debian there is not a single word about 
renaming /etc/wpa_supplicant.conf.

Sure, I could have known this would break due to all the discussion lately.
But since this setup did not involve the init script I forgot about 
the /etc/wpa_supplicant.conf issue for a moment.

(wpa_supplicant was started from an old fashioned 'pre-up' in /e/n/i )

> > Solution: Don't rename /etc/wpa_supplicant.conf on upgrade.
>
> And you exactly know why this isn't feasible.

No, I don't have the slightest idea why this is not feasible, really. But if 
it is not feasible then you could at least display a word of warning. 

> You still need some kind 
> of system service, since this is what you rely on. 

Wrong! See above.

> please finally stop filing more duplicates on issues we are already
> aware of.

Could you please point me to the duplicate bug report!


Kind regards,

Felix