On Sun, 2012-04-29 at 00:39 +0200, Michał Piotrowski wrote:
2012/4/28 Michał Piotrowski <mkkp4x4(a)gmail.com>:
> Hi,
>
> W dniu 28 kwietnia 2012 09:52 użytkownik Adam Williamson
> <awilliam(a)redhat.com> napisał:
>> On Fri, 2012-04-27 at 14:18 -0500, Bruno Wolff III wrote:
>>> On Thu, Apr 26, 2012 at 20:05:50 +0200,
>>> Michał Piotrowski <mkkp4x4(a)gmail.com> wrote:
>>> >
>>> >Are there any serious known problems with apache, python, php, mysql,
>>> >postgresql?
>>>
>>> I am using F17 on a machine that use postgres and perl scripts (not
>>> mod_perl though) to generate web pages using apache. Things seem to
>>> be working fine.
>>
>> As long as
http://www.happyassassin.net is running, you can take it that
>> a basic LAMP stack on F17 is working. =)
>
> Thanks for the info. I'll try to do an update today - if there are any
> problems, then I will let you know.
I'm still using grub1 on this machine, so I got small problem
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Preparing system to boot into installer
DEBUG /sbin/grubby --title="Upgrade to Fedora 17 (Beefy Miracle)"
--remove-kernel="/boot/upgrade/vmlinuz"
--add-kernel="/boot/upgrade/vmlinuz"
--initrd="/boot/upgrade/initrd.img" --args="preupgrade
repo=hd::/var/cache/yum/preupgrade
ks=hd:UUID=daad74d1-728f-42dc-b4ee-456174f83d99:/boot/upgrade/ks.cfg
stage2=hd:UUID=daad74d1-728f-42dc-b4ee-456174f83d99:/boot/upgrade/squashfs.img"
error opening /boot/grub/grub.cfg for read: No such file or directory
Probing devices to guess BIOS drives. This may take a long time.
All finished. The upgrade will begin when you reboot.
So AIUI, you're saying preupgrade wasn't able to add an entry to grub1's
config for performing the upgrade? That could be filed as a bug, though
it probably wouldn't get high priority unless it also affects F15.
I added this config to grub menu manually and performed update.
After
update I still have 297 packages to update with yum. I think it was
outdated mirror or something like that.
I explained that in my other mail. AIUI, what happens is that preupgrade
uses the 'release' and 'updates' repositories, it doesn't use
updates-testing. After preupgrade, updates-testing is enabled, because
that's the default in fedora-release for pre-releases. So as soon as the
upgrade is complete, a bunch of new packages from updates-testing is
immediately 'available'.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net