Jeff Spaleta wrote:

On Dec 7, 2007 10:07 AM, Will Woods <wwoods@redhat.com> wrote:

We've probably talked about this before but.. how hard would it be to
change yum to update itself (and its deps) before attempting the rest of
the transaction, for simple updates?

There've been a lot of bugs lately where "update yum before updating
everything else" was the solution. Seems like that would be the Right
Thing To Do in general.


If you are going to go down this road... do you want to go further and
have yum look for a yum update no matter what the specified
install/update transaction is?



No in that case I want it to do as I've told it. But when I tell it to update
everything first updating itself and then exec-ing its new self to continue
with the rest of the updates isn't a bad idea IMHO, but then the GUI tools need
to be thought to do the same.


Regards,

Hans

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Dec 7, 2007 8:17 PM, Hans de Goede <j.w.r.degoede@hhs.nl> wrote:
> Jeff Spaleta wrote:
> > On Dec 7, 2007 10:07 AM, Will Woods <wwoods@redhat.com> wrote:
> >> We've probably talked about this before but.. how hard would it be to
> >> change yum to update itself (and its deps) before attempting the rest of
> >> the transaction, for simple updates?
> >>
> >> There've been a lot of bugs lately where "update yum before updating
> >> everything else" was the solution. Seems like that would be the Right
> >> Thing To Do in general.
> >
> > If you are going to go down this road... do you want to go further and
> > have yum look for a yum update no matter what the specified
> > install/update transaction is?
> >
>
> No in that case I want it to do as I've told it. But when I tell it to update
> everything first updating itself and then exec-ing its new self to continue
> with the rest of the updates isn't a bad idea IMHO, but then the GUI tools need
> to be thought to do the same.
+1

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, 07 Dec 2007 19:07:26 +0000, Will Woods wrote:

> On Thu, 2007-12-06 at 16:37 -0500, seth vidal wrote:
> > On Thu, 2007-12-06 at 16:32 -0500, Dr. Diesel wrote:
> > >
> > > Is this a packaging error on Livna's part or some new policy I missed?
> > >
> >
> > it was a yum bug and it is fixed in yum 3.2.8 which is out in
> > updates.
>
> We've probably talked about this before but.. how hard would it be to
> change yum to update itself (and its deps) before attempting the rest of
> the transaction, for simple updates?
>
> There've been a lot of bugs lately where "update yum before updating
> everything else" was the solution. Seems like that would be the Right
> Thing To Do in general.

"yum -y update" prior to "yum install ..." also fixes many dependency
problems.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, 2007-12-07 at 19:07 +0000, Will Woods wrote:
> On Thu, 2007-12-06 at 16:37 -0500, seth vidal wrote:
> > On Thu, 2007-12-06 at 16:32 -0500, Dr. Diesel wrote:
> > >
> > > Is this a packaging error on Livna's part or some new policy I missed?
> > >
> >
> > it was a yum bug and it is fixed in yum 3.2.8 which is out in
> > updates.
>
> We've probably talked about this before but.. how hard would it be to
> change yum to update itself (and its deps) before attempting the rest of
> the transaction, for simple updates?
>
> There've been a lot of bugs lately where "update yum before updating
> everything else" was the solution. Seems like that would be the Right
> Thing To Do in general.

So far, I've been doing that manually (ie. if I see yum or one of its
libs about to be updated, I cancel the yum update and manually update
yum first).

Sometimes it's a question of there being a correct order in the first
place and if it's known what it is, then it should be automated.
--

Richi Plana

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

seth vidal <skvidal <at> fedoraproject.org> writes:
> except when you jump distro versions b/c then updating yum might be more
> like:
> yum
> python
> glibc
> theworld.

Python is more likely to be the one to drag in "the world" than glibc in such a
scenario. Glibc is backward-compatible, so packages built for the old one are
supposed to run on the new one, it should not be necessary to upgrade
everything to upgrade glibc. And glibc itself has few to no deps, for obvious
reasons. ;-) Python on the other hand has several dependencies which could need
upgrading.

Kevin Kofler

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list