On 4/25/23 13:24, Samuel Sieb wrote:
On 4/25/23 06:12, Robert Moskowitz wrote:
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As some
On 4/25/23 06:12, Robert Moskowitz wrote:
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As someone else pointed out:
# dnf -y --exclud
Den 2023-04-25 kl. 15:12, skrev Robert Moskowitz:
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As someone else pointed out:
# dnf -
On 4/25/23 08:59, Tim Evans wrote:
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb
that is triggering the dependency.
As someone else pointed out:
# dnf -y --exclude='*heif*' update
Sure, that has gotten
On 4/25/23 08:21, Robert Moskowitz wrote:
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb that
is triggering the dependency.
As someone else pointed out:
# dnf -y --exclude='*heif*' update
___
users mailin
Still no fix on this.
How do I notify the proper people about this? For me, it is gthumb that
is triggering the dependency.
On 4/23/23 16:07, Samuel Sieb wrote:
On 4/23/23 13:04, Robert Moskowitz wrote:
On a F37 system I have not updated in maybe a month or more, I get
the error:
Runni
On 4/23/23 13:34, Robert Moskowitz wrote:
Guess I will have to wait, as I got the same error after a "clean
packages" and then the update with --skip-broken.
Right, that error happens after dependency resolution.
Try "--exclude='*heif*'" instead.
___
Guess I will have to wait, as I got the same error after a "clean
packages" and then the update with --skip-broken.
And maybe I will just take this system up to a fresh install with F38
since it hit the doorstep.
On 4/23/23 16:07, Samuel Sieb wrote:
On 4/23/23 13:04, Robert Moskowitz wrote:
On 4/23/23 13:04, Robert Moskowitz wrote:
On a F37 system I have not updated in maybe a month or more, I get the
error:
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'
On a F37 system I have not updated in maybe a month or more, I get the
error:
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction test error:
file /us
On Saturday 12 December 2015 14:34:13 John Pilkington wrote:
> Perhaps try
>
> rpm -e --nodeps libkworkspace5-5.4.3-3.fc23.x86_64
>
> ... but I forget exactly how much of the package name is
> appropriate.
That's fixed it. Thanks very much.
--
Richard
--
users mailing list
users@lists.fedorap
On 12/12/2015 06:34 AM, John Pilkington wrote:
Perhaps try
rpm -e --nodeps libkworkspace5-5.4.3-3.fc23.x86_64
... but I forget exactly how much of the package name is appropriate.
John P
Generally speaking, you need just enough to identify it. Unless the OP
has more than one version instal
On 12/12/15 14:17, Richard Ibbotson wrote:
Hi
Anyone any idea how to deal with this one ? FC23. I've tried 'dnf
clean packages' and this still happens after running 'dnf
update'..
Delta RPMs reduced 127.7 MB of updates to 104.6 MB (18.1% saved)
Running transaction check
Transaction check
Hi
Anyone any idea how to deal with this one ? FC23. I've tried 'dnf
clean packages' and this still happens after running 'dnf
update'..
Delta RPMs reduced 127.7 MB of updates to 104.6 MB (18.1% saved)
Running transaction check
Transaction check succeeded.
Running transaction test
The dow
14 matches
Mail list logo
