Barry, this seems to be the first "unexpected EOF" bug I've seen where
there someone was able to diagnose the problem. I'm seeing a *lot* of
this kind of bug report against the lsb package; I'm not convinced that
this is just filesystem corruption given the prevalence. Of course
since the submitter here has already deleted the corrupt file we
unfortunately can't analyze it now, but maybe some submitters of other
recent bugs would be able to help?
** Changed in: lsb (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093071
Title:
can't import lsb_release in python3 anymore
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1093071/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
