On 03/29/2011 11:23 PM, José Matos wrote:
> On Wednesday 30 March 2011 06:27:41 JD wrote:
>> Well, I had no such problems in fc13. How come that interplay
>> did not cause conflicts in fc13?
> Because the repositories that you now using are from f14.
>
> There could be several reason for the proble
On Wednesday 30 March 2011 06:27:41 JD wrote:
> Well, I had no such problems in fc13. How come that interplay
> did not cause conflicts in fc13?
Because the repositories that you now using are from f14.
There could be several reason for the problems you see. One example, imagine
that a package h
On 03/29/2011 09:39 PM, José Matos wrote:
> On Wednesday 30 March 2011 00:09:58 JD wrote:
>> Yum simply does not seem to be able to handle this chain
>> of dependencies scenario.
>> I consider it broken!
> Use the --skip-broken parameter to see if the dependency resolution goes
> further.
>
> FWIW
On 03/29/2011 04:29 PM, JB wrote:
> JD gmail.com> writes:
>
>> ...
>> I did that. I did update a lot of fc13 packages to fc14.
>> But it still chocked on the dependencies that had other
>> packages depending on the very dependencies it tries
>> to update.
>> Yum simply does not seem to be able to
On Wednesday 30 March 2011 00:09:58 JD wrote:
> Yum simply does not seem to be able to handle this chain
> of dependencies scenario.
> I consider it broken!
Use the --skip-broken parameter to see if the dependency resolution goes
further.
FWIW the interplay between the packages that you have ins
JD gmail.com> writes:
> ...
> I did that. I did update a lot of fc13 packages to fc14.
> But it still chocked on the dependencies that had other
> packages depending on the very dependencies it tries
> to update.
> Yum simply does not seem to be able to handle this chain
> of dependencies scenar
On 03/29/2011 01:55 PM, JB wrote:
> JD gmail.com> writes:
>
>> On 03/29/2011 12:18 PM, JB wrote:
>>> JD gmail.com> writes:
>>>
...
>>> This is my cure-all medicine:
>>>
>>> # yum-complete-transaction
>>> # yum clean all
>>> # yum distro-sync
>>> # yum check
>>> # package-cleanup --dupes
On 03/29/2011 01:38 PM, JD wrote:
> I merely thought that since you did not know that one
> can boot directly into single user mode, (i.e. without
> booting into the normal level 5, and then using a shell
> terminal to "sudo init s")
I not only know how to boot into single-user mode, I know how to
JD gmail.com> writes:
>
> On 03/29/2011 12:18 PM, JB wrote:
> > JD gmail.com> writes:
> >
> >> ...
> > This is my cure-all medicine:
> >
> > # yum-complete-transaction
> > # yum clean all
> > # yum distro-sync
> > # yum check
> > # package-cleanup --dupes | problems | orphans
> >if any dup
On 03/29/2011 12:36 PM, Joe Zeff wrote:
> On 03/29/2011 12:18 PM, JD wrote:
>> Which init level?
>> I said I rebooted into single user mode!!
>> If you do not know how to do that, you need to read the wiki.
> Instead of getting hysterical and trying (unsuccessfully) to insult me,
> you might have n
On 03/29/2011 12:18 PM, JB wrote:
> JD gmail.com> writes:
>
>> ...
> This is my cure-all medicine:
>
> # yum-complete-transaction
> # yum clean all
> # yum distro-sync
> # yum check
> # package-cleanup --dupes | problems | orphans
>if any dupes or problems show up, show us the output; ignore
On 03/29/2011 12:18 PM, JD wrote:
> Which init level?
> I said I rebooted into single user mode!!
> If you do not know how to do that, you need to read the wiki.
Instead of getting hysterical and trying (unsuccessfully) to insult me,
you might have noticed that I mentioned both init 1 and init 3.
JD gmail.com> writes:
> ...
This is my cure-all medicine:
# yum-complete-transaction
# yum clean all
# yum distro-sync
# yum check
# package-cleanup --dupes | problems | orphans
if any dupes or problems show up, show us the output; ignore orphans for now.
# find /etc -iname "*.rpm*"
and re
On 03/29/2011 12:10 PM, Joe Zeff wrote:
> On 03/29/2011 11:57 AM, JD wrote:
>> Upon reboot (into single user mode),
>> I brought up the network - no problems there.
> First, I presume you meant you went from F 13 to F 14. Second, did you
> actually boot into single-user mode (init 1) or simply a
On 03/29/2011 11:57 AM, JD wrote:
> Upon reboot (into single user mode),
> I brought up the network - no problems there.
First, I presume you meant you went from F 13 to F 14. Second, did you
actually boot into single-user mode (init 1) or simply a CLI instead of
a GUI, which is init 3? I ask
I upgraded from F13 to F13 using the installation DVD
downloaded from
http://mirrors.kernel.org/fedora/releases/14/Fedora/i386/iso/Fedora-14-i386-DVD.iso
The checksum was good.
I burned and booted with the DVD I burned, and I let Anaconda perform
integrity check. All went well.
I selected to upgra
16 matches
Mail list logo
