Le 29/01/2016 13:21, Paul Gevers a écrit :
> Hi Guy,
>
> On 28-01-16 23:13, Guy Durrieu wrote:
>>>> "MySQL database support detected, but apparently missing Depends on
>>>> dbconfig-
>>>> mysql packages. Please report this issue to the package maintainer.."
>>>>
>>>> That's done.
>>> Good. Out of curiosity, which bug number?
>> Don't understand the question... There were no more information than the
>> message itself, which appeared twice: one at the beginning of the
>> upgrade process, one when upgrading phpmyadmin...
> I understood you reported the issue to the package maintainer. But
> apparently you meant something else. What did you mean with "That's done"?

I guess you are the package maintainer, are you ?

Excuse-me for not being clear. You understood right; but I still don't
see which bug number you refer to.I didn't get any bug number, only the
message.

>>>> Having a sight to my install, dbconfig-mysql actually isn't installed,
>>>> and when I ask to install it, the package "dbconfig-no-thanks" need to
>>>> be uninstalled.
>>> dbconfig-mysql and dbconfig-no-thanks conflict on purpose, so can't be
>>> installed together. But are you now saying that you saw the message
>>> above while dbconfig-no-thanks is installed?
>> Yes, that's what happened.
> Do you still have logging? If you reinstall the package (eg. phpmyadmin,
> does it still say this?) Could you send me the logging of that with
> dbc_debug=true set? Be sure to remove your password from the logging though.

(Do you mean the upgrade/reinstall log ?I am now at office, I shall do
that after going back to home).

As I said yesterday in a later message, phpmyadmin doesn't work anymore.
I tried to reinstall it after also installing dbconfig-mysql, there is
no more message, but phpmyadmin still doesn't work.(Depending on the
browser, I get either a blank window (iceweasel) or a "error 500"
message (chromium) [configuration problem ?].)

>>> That is a severe bug, as
>>> dbconfig-no-thanks is supposed to prevent dbconfig-common from doing
>>> anything (including emitting the warning you see above.
>> Well, mySQL still works anyway :)
> dbconfig-common has nothing to do with the MySQL package itself.
> dbconfig-common is a helper package for packages like phpmyadmin to
> manage the connection to MySQL (or some other database).

OK. I now understand why phpmyadmin doesn't work anymore. I was confused
by the first part of the message: "MySQL database support detected"...
>>>> Is it now necessary to do so ?
>>> Yes, unless you don't want dbconfig-common support.Than you should leave
>>> dbconfig-no-thanks installed and leave dbconfig-mysql uninstalled.
>>>
>>> How and why did you install dbconfig-no-thanks in the first place?
>> As far as I know, this was done the first time I installed LAMP, a while
>> ago. I didn't specifically require dbconfig-no-thanks, I suppose it came
>> with all the stuff. Until today, I wasn't aware there were possible
>> alternatives, and my question was about what is the right thing to do (I
>> only use mySQL and don't clearly see the advantages of installing
>> dbconfig-mysql).
> This is worrying. dbconfig-no-thanks should not be pulled in by default.
> It is an alternative that should always come after a dbconfig-<dbtype>
> package in the list of dependencies. I would really like to learn why
> this package got installed. dbconfig-no-thanks doesn't exist very long
> yet, so it must be installed not too long ago.
>
> Paul
>
My first install on the related computer was near december, 2014.I don't
remember having explicitely done this kind of choice during the
install.  And all worked fine until this last upgrade. Is it a mean to
know what happened ?

Thanks for your help !

Regards.

-- GD.

Reply via email to