[09:04] <clobrano> hi, looking at the bug list I've found quite often issues like "failed install/upgrade, package x is already installed and configured". This message alone,  does not seems a reason to issue a bug, to me. So, out of curiosity, what kind of error is this? Thanks?
[09:04] <clobrano> *Thanks without question mark :D
[10:33] <tsimonq2> clobrano: I can give some insight on this
[10:33] <tsimonq2> clobrano: tl;dr apt throws up :P
[10:34] <tsimonq2> clobrano: Got an example bug report?
[10:34] <clobrano> tsimonq2: :D
[10:34] <clobrano> tsimonq2: yes, I'll check again for the one I saw last
[10:34] <tsimonq2> clobrano: Ok :)
[10:35] <clobrano> tsimonq2: Bug #1703548
[10:35] <ubot5> bug 1703548 in m4 (Ubuntu) "package m4 1.4.17-5 failed to install/upgrade: package m4 is already installed and configured" [Undecided,New] https://launchpad.net/bugs/1703548
[10:40] <tsimonq2> clobrano: Huh, that is very interesting...
[10:40] <tsimonq2> From waht I can tell, apt gets confused when it's configuring the package
[10:41] <tsimonq2> *what
[10:42] <tsimonq2> clobrano: Interesting, I don't know what to say
[10:43] <tsimonq2> Weird...
[10:43] <clobrano> tsimonq2: :D, yeah but, generically speaking is "APT: I cannot configure this, since is already configured" to be considered an error?
[10:44] <clobrano> I mean, it's configured so it's ok, or am I oversimplifying?
[10:46] <tsimonq2> clobrano: It all depends if it's something that makes apt stop dead in its tracks or if it's just a warning.
[10:46] <tsimonq2> I can't reproduce it though.
[10:48] <clobrano> tsimonq2: I see, I actually didn't try reproducing this particular bug
[10:49] <clobrano> well, I don't know apt as well, but I was curious, because there are a lot of bugs like this one
[10:51] <tsimonq2> Yeah
[11:56] <clobrano> tsimonq2: btw, this is really a good example of function name that documents itself (dpkg, not apt): ohshit(_("package %.250s is already installed and configured")  :D
[12:09] <tsimonq2> :D
=== jtaylor_ is now known as jtaylor