update 1.2.1 fails

[rdaneel]

Hi,
i cant seem to do the update. i get an error

Failures found in package (dpkg) database, unable to continue with upgrade.
iF bubba-album 1.2.0.4 The codeigniter based album public interface

Error!
Failed to access MySQL with default root login, unable to continue with upgrade.
DBI connect('mysql','root',...) failed: Access denied for user 'root'@'localhost' (using password: NO) at /usr/share/perl5/Bubba/Apt.pm line 299

any idea how to fix this?

tnx

[carl]

Hi,
i cant seem to do the update. i get an error

Failures found in package (dpkg) database, unable to continue with upgrade.
iF bubba-album 1.2.0.4 The codeigniter based album public interface

Error!
Failed to access MySQL with default root login, unable to continue with upgrade.
DBI connect('mysql','root',...) failed: Access denied for user 'root'@'localhost' (using password: NO) at /usr/share/perl5/Bubba/Apt.pm line 299

any idea how to fix this?

tnx

This indicates you have changed the default password for mysql some time in the past; You will need to update the system via the command line; e.g.

Code: Select all

apt-get update
apt-get dist-upgrade

And when it asks for the mysql password, enter it.

We decided to make this restriction in the web-based updater due to the severe problems failed upgrades can result in. In the future hopefully the system will be able to handle non-blank mysql root passwords, but that work will have to be taken under debian as whole (especially the dbconfig-common package).

Currently there are three checks made before eventual automatic upgrade, first it checks so that no current installed package is in a failed state (iF above), second it checks if it can connect to the mysql database with blank password, and third, it controlls that the apache2 config is sound (as a failed apache2 config will disable the web interface totally on an attempted upgrade).

/Carl

[rdaneel]

Hi CArl,

Tnx doing this manualy worked.
Does this mean i have tot do this manualy every time?
or is there a way to enter the password during update?

Tnx ,
Rdg

[carl]

Hi CArl,

Tnx doing this manualy worked.
Does this mean i have tot do this manualy every time?
or is there a way to enter the password during update?

Tnx ,
Rdg

At the moment you will have to update it manually; We are trying to work with the debian folks to fix this problem, but I can't guarantee any ETA.

/Carl

[rdaneel]

Hi,

How can i set the SQL password back to default? what is the default pwd?
Or is this problem allready solved in the next update?

tnx
R

[asparak]

I believe the default is no password. This is a major security risk though, so personally I wouldn't recommend it.

[rdaneel]

Hi,

thanks for the reply So the only way to do this properly is through the terminal ?
the update function from the bubba admin screen relies on an blank password which in turn is a major security risk.. do i understand correctly?

@ Excito: Why not run Mysql under the admin account. the only way to use the update functionality of bubba is when loggged in in the admin account so it shouldn't be to hard to pass that along to the update function.
Automatic update works and mySql is password protected.

R

[asparak]

Hi,

thanks for the reply So the only way to do this properly is through the terminal ?
the update function from the bubba admin screen relies on an blank password which in turn is a major security risk.. do i understand correctly?

@ Excito: Why not run Mysql under the admin account. the only way to use the update functionality of bubba is when loggged in in the admin account so it shouldn't be to hard to pass that along to the update function.
Automatic update works and mySql is password protected.

R

because running MySQL as an admin user is also a security risk

just open a terminal window and use apt-get. Personally, I think its a fair trade off for now - until we figure out a fix - between security and ease of use.

[rdaneel]

Hi,

apt-get update
apt-get dist-upgrade

doesn't seem to update bubba to 1.2.3?
the update screen in the admin site says

Package name Package version
bubba-frontend 1.2.2.0.3
bubba-backend 1.2.2.0.7
bubba-album 1.2.0.4
filetransferdaemon 0.50.16
squeezecenter 7.4.0.dfsg1-2

any idea how to do the updates?
tnx
Ralph

[carl]

Hi,

apt-get update
apt-get dist-upgrade

doesn't seem to update bubba to 1.2.3?
the update screen in the admin site says

Package name Package version
bubba-frontend 1.2.2.0.3
bubba-backend 1.2.2.0.7
bubba-album 1.2.0.4
filetransferdaemon 0.50.16
squeezecenter 7.4.0.dfsg1-2

any idea how to do the updates?
tnx
Ralph

Can you post the output of the command "apt-cache policy"? also the output of "apt-cache policy bubba"

/Carl

[rdaneel]

Here it is.
//---------------------------------------------
bubba:/home/ralph# apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ftp.se.debian.org etch/non-free Packages
release v=4.0r8,o=Debian,a=oldstable,l=Debian,c=non-free
origin ftp.se.debian.org
500 http://ftp.se.debian.org etch/main Packages
release v=4.0r8,o=Debian,a=oldstable,l=Debian,c=main
origin ftp.se.debian.org
600 http://update.excito.org upstream_etch/main Packages
release v=1.0,o=Debian Etch,a=upstream_stable,l=Debian Etch subset,c=main
origin update.excito.org
999 http://update.excito.org marielle/main Packages
release v=1.0,o=Excito,a=stable,l=BubbaTwo stable,c=main
origin update.excito.org
Pinned packages:
//---------------------------------------------

bubba:/home/ralph# apt-cache policy bubba
bubba:
Installed: 1.2.3
Candidate: 1.2.3
Version table:
*** 1.2.3 0
999 http://update.excito.org marielle/main Packages
100 /var/lib/dpkg/status
//---------------------------------------------

tnx Rd

[carl]

Here it is.
//---------------------------------------------
bubba:/home/ralph# apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ftp.se.debian.org etch/non-free Packages
release v=4.0r8,o=Debian,a=oldstable,l=Debian,c=non-free
origin ftp.se.debian.org
500 http://ftp.se.debian.org etch/main Packages
release v=4.0r8,o=Debian,a=oldstable,l=Debian,c=main
origin ftp.se.debian.org
600 http://update.excito.org upstream_etch/main Packages
release v=1.0,o=Debian Etch,a=upstream_stable,l=Debian Etch subset,c=main
origin update.excito.org
999 http://update.excito.org marielle/main Packages
release v=1.0,o=Excito,a=stable,l=BubbaTwo stable,c=main
origin update.excito.org
Pinned packages:
//---------------------------------------------

bubba:/home/ralph# apt-cache policy bubba
bubba:
Installed: 1.2.3
Candidate: 1.2.3
Version table:
*** 1.2.3 0
999 http://update.excito.org marielle/main Packages
100 /var/lib/dpkg/status
//---------------------------------------------

tnx Rd

That seems to be correct; We discontinued to upgrade the version on the subpackages and relies only on the version fo the "bubba" package instead.

/Carl

[rdaneel]

Hi,

so it is just the Admin screen that shows the wrong information?

Rdg