Reading the dpkg log I come to the following conclusion:
- During the question for the root password on the mysql database the wrong
password was provided, thus the removal of the database failed
- After continuing with reinstallation of the database, the OP was hit by
Table 'cdef' already
I believe that the php5 source package in Ubuntu (Debian) tries to make
sure that in Ubuntu this is not necessary (I see patches related to
using . Therefor I assume something is broken in those patches, and I
reassign to php5. If somebody with more php knowledge could look into
this...
Cacti
On 24-10-12 15:41, Robie Basak wrote:
I have verified that the test case fails in a quantal chroot running
5.4.6-1ubuntu1, and then passes after an upgrade to my test build of
5.4.6-1ubuntu2.
Just a stupid question. Reading the changelog of 5.4.6-2 in Debian [1],
it seems a lot of bugs were
Cacti asks dbconfig-common to handle the database, so this bug is really
in that package. Reassigning. I am quite sure that there is also a
Debian bug about this issue, but dbconfig-common really needs a
maintainer.
** Package changed: cacti (Ubuntu) = dbconfig-common (Ubuntu)
--
You received
@David Kranz: For a work around have a look at my comment 101 in the
Debian report: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=476946#101
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
Actually, it is not only the space character. I think dbconfig-common
should make sure that passwords are escaped properly. However,
phpmyadmin could add quotes to the config template, and only quotes
would be a problem in the password (but probably make it fail instead of
using a truncated
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It seems that you were running at least two install operations at the
same time. I am unsure which package this bug belongs, as I would say
that should not be possible, but it is not a failure of dconfig-common.
** Summary changed:
- package cacti 0.8.7e-2ubuntu0.1 failed to install/upgrade: subprocess
installed pre-removal script returned error exit status 1
+ drop database when requested by dpkg-reconfigure answer
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I'll try to see what better behavior is possible, but it may take a
while.
** Summary changed:
- package torrentflux 2.3-6 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
+ improve handling of the lack of a database
--
You received this bug
** Summary changed:
- package request-tracker3.8 3.8.4-1 failed to install/upgrade:
+ handle off-line database during upgrade more gracefully
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
** Bug watch added: Debian Bug tracker #706512
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706512
** Also affects: dbconfig-common (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706512
Importance: Unknown
Status: Unknown
--
You received this bug notification
Hmm, looking at the amount of duplicates and the fact that they all fall
in the same time frame I wonder if instead this being a bug in dbconfig-
common if this wasn't a bug in the software center which is long fixed.
I recall that I once had an issue that questions were not appropriately
asked in
Sorry that it took so long to follow up on this bug, but dbconfig-common
has been rather unmaintained last couple of years. I am taking over the
maintainership of dbconfig-common in Debian and will upload a new
version to debian/experimental in the next couple of days/weeks.
Although I think the
Just a remark as the new maintainer of dbconfig-common in Debian.
Unfortunately, the behavior that you want is the wrong solution to the
problem, as it would blindly overrule system administrators decisions.
Therefore this bug is in essence wontfix.
However, what is a legitimate question is that
Hi,
You dpkgTerminalLog.txt file shows a lot of errors. One of them being
that debconf questions could not be asked. This results in failure of
dbconfig-common to ask you the root password to log into the mysql
database.
For you to work around this, is to fix the issue with debconf not being
*** This bug is a duplicate of bug 243852 ***
https://bugs.launchpad.net/bugs/243852
** This bug has been marked a duplicate of bug 440430
handle off-line database during upgrade more gracefully
** This bug is no longer a duplicate of bug 440430
handle off-line database during upgrade
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, this bug report doesn't actually contain a
bug. The configuration asked the password of the administrator of the
mysql server, and the operator failed to provide a valid password. (Mind
you the
Can you please explain why this is considered a bug? If the database is
corrupt (or at least, the operator configured the package to use a wrong
database) isn't this expected behavior?
Relevant part of the DpkgTerminalLog.gz:
Creating config file /etc/dbconfig-common/bacula-director-mysql.conf
As I mentioned in my previous comment, I tend to think this issue (which
was never a dbconfig-common bug AFAICT) has been solved. It would help
if anybody could tell me if they still experience this issue or if they
don't. Marking this bug as incomplete until somebody responds.
** Changed in:
*** This bug is a duplicate of bug 563256 ***
https://bugs.launchpad.net/bugs/563256
Hmm, more looks like phpmyadmin had invalid mysql code, which caused
multiple trials of installation to fail.
Replacing config file /etc/dbconfig-common/phpmyadmin.conf with new version
granting access to
Error handling during removal strangely involved configuration. This
issue has been fixed in dbconfig-common 1.8.50.
** Also affects: dbconfig-common (Debian)
Importance: Undecided
Status: New
** Changed in: dbconfig-common (Debian)
Status: New = Fix Released
--
You received
From the changelog in 1.8.50:
* Make check for DEBIAN_FRONTEND case insensitive (LP: #1406700)
** Also affects: dbconfig-common (Debian)
Importance: Undecided
Status: New
** Changed in: dbconfig-common (Debian)
Status: New = Fix Released
--
You received this bug
Changelog from 1.8.48:
* Fix multiple db support install. Thanks to Sylvain Garcia and Soren
Hansen (LP: #252882)
** Changed in: dbconfig-common (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Upload of 1.8.51 will happen in about two weeks time. That gives
translators the time to update the templates.
It will be synced automatically to Ubuntu after that.
Paul
On 20-05-15 10:07, Robie Basak wrote:
dbconfig-common = 1.8.48 is still in experimental in Debian. I don't
want to sync it
The fixable part of this bug was fixed in version 1.8.50 which is part
of The Willy Werewolf. Closing this bug
** Changed in: dbconfig-common (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Error handling has been unified and improved in the package that is in
The Willy Werewolf. Closing this bug.
** Changed in: dbconfig-common (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
This was fixed in version 1.8.50 which is part of The Willy Werewolf.
Closing this bug
** Changed in: dbconfig-common (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in
This was fixed in version 1.8.48 which is part of The Willy Werewolf.
Closing this bug.
** Changed in: dbconfig-common (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in
This was fixed in 1.8.50 which is part of The Wily Werewolf. So closing
this bug.
** Changed in: dbconfig-common (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in
Thanks for reporting this issue. However, there is not enough
information to debug this issue.
What happens if you run (please copy/paste all the output):
apt-get install dbconfig-common
** Changed in: dbconfig-common (Ubuntu)
Status: New => Incomplete
--
You received this bug
This was fixed in version 1.8.50 which is part of The Willy Werewolf.
Closing this bug.
** Changed in: dbconfig-common (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in
Hi Graham and Robie
On 22-09-15 12:15, Robie Basak wrote:
> This bug was fixed in the package dbconfig-common - 1.8.53
> Sponsored for Graham Inggs (ginggs)
> * Add extended regression tests to autopkgtest list
It seems dbconfig-common is now hold back because of this new test
failing. I just
On 23-09-15 21:07, Graham Inggs wrote:
> If the fix is known, upload it to Debian first. From there we can try
> to sync again or upload a new Ubuntu version.
I believe I know the fix. However, if I can do that for Debian I like to
also get the second autopkgtest to run as intended (after the
Hi
On 23-09-15 21:07, Graham Inggs wrote:
> If the fix is known, upload it to Debian first. From there we can try
> to sync again or upload a new Ubuntu version.
I decided to not fix more than just this issue. In the mean time I even
received a patch from Martin Pitt.
Once the package is
On 25-09-15 12:26, Paul Gevers wrote:
> Once the package is accepted and shows up, I guess I have to request
> another sync right?
It now did, but I can't get requestsync to work on my system right now
(it used to work in the past). Graham, can you request the syn again?
Paul
--
You re
Hi Andres,
On 10-03-16 02:47, Andres Rodriguez wrote:
> So this confirms that because of the postrm bug, we would see the install
> issues.
Good that we nailed it down.
> however, I wonder if dbconfig-common should do
> something to not to write a new config ?
As dbconfig-common leaves this to
Hi Andres,
On 10-03-16 16:57, Paul Gevers wrote:
>> however, I wonder if dbconfig-common should do
>> something to not to write a new config ?
>
> As dbconfig-common leaves this to ucf, I think than it should be done
> there. Or do you have something else in mind?
It seem
Hi Andres,
On 06-03-16 17:42, Andres Rodriguez wrote:
> In MAAS, we make use of dbconfig common. We have been using it exactly
> the same way for awhile now and we have just starting seeing the
> following on install or upgrade:
>
> dbconfig-common: writing config to
>
Hi Andres,
On 07-03-16 06:07, Andres Rodriguez wrote:
> Sorry for not being clear enough.
NP, as long as you follow up on questions that is ok.
> The actual issue/concern I have is:
>
> stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No
> such file or directory
Ack. I
Andres,
This (in maas-region-controller.postrm) prevents dbconfig-common from
unregistring the file with ucf (so the fact that you see the ucf prompt
after purging and installing is at least caused by maas itself):
if [ -f /etc/dbconfig-common/maas.conf ]; then
if [ -f
Hi Andres,
Maybe unrelated and I may not understand your intentions, but I see the
following in your maas-region-controller.config:
set_question() {
if ! db_fget "$1" seen; then
db_register dbconfig-common/dbconfig-install "$1"
db_subst "$1" ID "$1"
db_fget "$1" seen
Hi Andres,
On 08-03-16 04:38, Andres Rodriguez wrote:
> So the reason we did this is because we wanted MAAS to be installed and we
> didn't want any question to be asked, so we decided to do the preseeding.
I recommend that you try to use dbc_prio_high=medium instead of your
current code. By
Hi Andres,
On 08-03-16 04:41, Andres Rodriguez wrote:
> Sorry for the delay and thanks for looking into it. Good catch on the
> postrm. At least I know that's my fault. That being said, I wonder if
> unregistering the file actually explains why it doesn't get re-created.
Hmm, I was a bit to
43 matches
Mail list logo
