On 5/1/19 3:06 AM, Patrick O'Callaghan wrote:
On Wed, 2019-05-01 at 02:48 -0700, ToddAndMargo via users wrote:
On 5/1/19 12:15 AM, Samuel Sieb wrote:
On 4/30/19 8:01 PM, ToddAndMargo via users wrote:
If you are upgrade from 29 to 30, make sure you
update dnf and libdnf first do to a bug that h
On Wed, 2019-05-01 at 02:48 -0700, ToddAndMargo via users wrote:
> On 5/1/19 12:15 AM, Samuel Sieb wrote:
> > On 4/30/19 8:01 PM, ToddAndMargo via users wrote:
> > > If you are upgrade from 29 to 30, make sure you
> > > update dnf and libdnf first do to a bug that has
> > > been fixed (my procedure
On 5/1/19 12:15 AM, Samuel Sieb wrote:
On 4/30/19 8:01 PM, ToddAndMargo via users wrote:
If you are upgrade from 29 to 30, make sure you
update dnf and libdnf first do to a bug that has
been fixed (my procedure below takes care of this).
Due to previous issues, I always make sure that at least
On 4/30/19 8:01 PM, ToddAndMargo via users wrote:
If you are upgrade from 29 to 30, make sure you
update dnf and libdnf first do to a bug that has
been fixed (my procedure below takes care of this).
Due to previous issues, I always make sure that at least dnf and systemd
are fully updated befo
Hi All,
If you are upgrade from 29 to 30, make sure you
update dnf and libdnf first do to a bug that has
been fixed (my procedure below takes care of this).
So far I have one virtual machine running FC30. Haven't
got a chance to torture it yet though.
This is my update procedure:
FC 29 -->>
