Public bug reported:
Running lucid, with the lucid-updates repository enabled. The qemu-
common package refuses to install:
The following packages have unmet dependencies:
qemu-common: Depends: vgabios (>= 0.6c-2ubuntu2) but it is not going to be
installed
The last version available for vgabi
Ugh. You can close this. I had a PPA for KVM for hardy (which was
converted to lucid on upgrade) that I thought I had disabled in the
sources.list file for this computer, but the change I did on my master
sources.list file didn't get propagated correctly, due to an operator
error.
Thanks for the
Public bug reported:
The version of rabbitmq-server in lucid warns in its preinst about
migrating from an older version of rabbitmq even when doing a clean
install. I have a script that creates Ubuntu 10.04 virtual machines with
the packages I need, and this is the only place where I need to press
A solution I found is simply to add openldap user to the ssl-cert group,
which is the group that is allowed to read certificate key files under
/etc/ssl/private, at least in a default hardy install.
--
dapper upgrade to hardy: openldap silently refuses to start when unable to open
SSL certificat
Public bug reported:
Binary package hint: apache2
When only the apache2.2-common package is left installed (at least in
hardy), I get an email fron cron every day saying:
/etc/cron.daily/logrotate:
error: error accessing /var/log/apache2: No such file or directory
error: apache2:1 glob failed fo
Andreas Olsson wrote:
> How did you manage to have the packaget manager remove /var/log/apache2
> without touching /etc/logrotate.d/apache2? The only way I've managed to
> get apt to remove /var/log/apache2 is by purging apache2.2-common, and
> that also removes /etc/logrotate.d/apache2.
>
> Was it
Andreas Olsson wrote:
> Which of these events took place when you ran Dapper and what was done
> after the upgrade to Hardy?
>
Probably the install (and use to compile stuff) was done on dapper and
the removal on hardy. But as far as I see, it's still possible to get
the same problem on hardy
Andreas Olsson wrote:
> I'll see if I can recreate the scenario going back to dapper.
>
> Regarding getting the same problem on Hardy by simpling installing and
> removing apache2.2-common; have you actually tried it? I have, and I
> wrote about it in my first comment.
>
> Well, I guess there still
