On 2024-05-09 14:12, Tim Evans wrote:
On 5/9/24 5:02 PM, Samuel Sieb wrote:
On 2024-05-09 13:59, Tim Evans wrote:
Since (I think) the gnome-software app is flat-pack based, have I
messed anything up by running its upgrade instead of the
dnf/rpm-based one?
There are no flatpacks installed by
On 5/9/24 5:02 PM, Samuel Sieb wrote:
On 2024-05-09 13:59, Tim Evans wrote:
Since (I think) the gnome-software app is flat-pack based, have I
messed anything up by running its upgrade instead of the dnf/rpm-based
one?
There are no flatpacks installed by default. The gnome-software app is
On 2024-05-09 13:59, Tim Evans wrote:
Since (I think) the gnome-software app is flat-pack based, have I messed
anything up by running its upgrade instead of the dnf/rpm-based one?
There are no flatpacks installed by default. The gnome-software app is
definitely not flatpack unless you've
On 5/9/24 4:20 PM, Samuel Sieb wrote:
On 2024-05-09 12:50, Tim Evans wrote:
Command-line dnf upgrade (F39->F40) failed yesterday, barfing on a
missing GPG key for Fedora 40, leaving 2.5GB of rpms sitting in
/var/lib/dnf/system-upgrade. 'dnt clean' does not remove these.
dnf system-upgr
On 2024-05-09 12:50, Tim Evans wrote:
Command-line dnf upgrade (F39->F40) failed yesterday, barfing on a
missing GPG key for Fedora 40, leaving 2.5GB of rpms sitting in
/var/lib/dnf/system-upgrade. 'dnt clean' does not remove these.
dnf system-upgrade clean
Is it safe to manually clear
On 5/9/24 4:00 PM, Jeffrey Walton wrote:
On Thu, May 9, 2024 at 3:51 PM Tim Evans <mailto:tkev...@tkevans.com>> wrote:
Command-line dnf upgrade (F39->F40) failed yesterday, barfing on a
missing GPG key for Fedora 40,
The key is automatically imported when followin
On Thu, May 9, 2024 at 3:51 PM Tim Evans wrote:
> Command-line dnf upgrade (F39->F40) failed yesterday, barfing on a
> missing GPG key for Fedora 40,
The key is automatically imported when following dnf-system-upgrade, <
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fe
Command-line dnf upgrade (F39->F40) failed yesterday, barfing on a
missing GPG key for Fedora 40, leaving 2.5GB of rpms sitting in
/var/lib/dnf/system-upgrade. 'dnt clean' does not remove these.
Is it safe to manually clear out this subdirectory?
(FWIW, I tried the now-recommended
On Wed, 3 Apr 2024, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also has to
be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be explicitly told
the EFI partition is the
On 4/8/24 08:19, Robert McBroom via users wrote:
On 4/3/24 5:45 PM, Stephen Morris wrote:
On 4/4/24 00:50, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also
has to be mounted at /boot/efi as indicated.
Ah!
On 4/3/24 5:45 PM, Stephen Morris wrote:
On 4/4/24 00:50, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also
has to be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be
On 4/4/24 00:50, Michael Hennebry wrote:
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also
has to be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be explicitly told
the EFI partition is the EFI
On Tue, 2 Apr 2024, Samuel Sieb wrote:
The efi partition probably needs to be bigger than that, but it also has to
be mounted at /boot/efi as indicated.
Ah! With custom partitioning,
anaconda needs to be explicitly told
the EFI partition is the EFI partition.
--
Michael
On 4/2/24 22:19, Michael Hennebry wrote:
While trying to install from Fedora-Workstation-Live-x86_64-39-1.5.iso ,
I got the following:
Failed to find a suitable stage1 device:
EFI System Partition must be mounted on one of /boot/efi.;
EFI System Partition cannot be of type None;
EFI System
While trying to install from Fedora-Workstation-Live-x86_64-39-1.5.iso ,
I got the following:
Failed to find a suitable stage1 device:
EFI System Partition must be mounted on one of /boot/efi.;
EFI System Partition cannot be of type None;
EFI System Partition cannot be of type NTFS;
EFI System
> On 13 Mar 2024, at 17:12, Neal Becker wrote:
>
> I need to see the lines before this, and maybe after. Any ideas?
Once I find a time of interest I have use the —since and - before to get a time
bounded slice of logs.
Barry
--
___
users
On 3/13/24 14:42, Joe Zeff wrote:
On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has
-A and -B for showing "n" number of lines After or Before the matched
context.
If you need to pass options to grep, consider piping the output
On 3/13/24 10:10, Neal Becker wrote:
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff <mailto:j...@zeff.us>> wrote:
On 03/12/2024 12:33 PM, Neal Becker wrote:
> Failed to start jobs: Failed to enqueue some jobs, see logs for
details:
> Invalid argument
>
On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has
-A and -B for showing "n" number of lines After or Before the matched
context.
If you need to pass options to grep, consider piping the output of
journalctl through grep instead.
On 3/13/24 10:10, Neal Becker wrote:
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff wrote:
On 03/12/2024 12:33 PM, Neal Becker wrote:
Failed to start jobs: Failed to enqueue some jobs, see logs for details:
Invalid argument
Should I worry? I don't even know what armadillo is.
Did you look
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff wrote:
> On 03/12/2024 12:33 PM, Neal Becker wrote:
> > Failed to start jobs: Failed to enqueue some jobs, see logs for details:
> > Invalid argument
> >
> > Should I worry? I don't even know what armadillo is.
&
On 03/12/2024 12:33 PM, Neal Becker wrote:
Failed to start jobs: Failed to enqueue some jobs, see logs for details:
Invalid argument
Should I worry? I don't even know what armadillo is.
Did you look at the logs and if not, why not? Checking Wikipedia,
armadillo is a C++ library for linear
Running today's dnf update:
...
Running scriptlet: grub2-common-1:2.06-118.fc39.noarch
32/32
Running scriptlet: armadillo-12.8.0-1.fc39.x86_64
32/32
Failed to start jobs: Failed to enqueue
Thomas Horsley wrote:
> Finally found this bugzilla:
> https://bugzilla.redhat.com/show_bug.cgi?id=2254986
>
> Create empty file /etc/default/wsdd and it is happy (sheesh!)
The root of the issue is that the package installs the
defaults file in the wrong location. Here's a patch to the
On Mon, 12 Feb 2024 12:23:41 +
Patrick O'Callaghan wrote:
> It has nothing on the classic IBM message:
>
> Wrong Error
I always liked IEF020I: DCB erropt=ABE and/or no SYNAD exit specified
(which I eventually learned meant the damn operator mounted the wrong tape).
--
On Sun, 2024-02-11 at 19:11 -0500, Tom Horsley wrote:
> What on earth does that mean? Is there a contest to see who can
> generate the least useful error message? :-).
>
It has nothing on the classic IBM message:
Wrong Error
poc
--
___
users mailing
Finally found this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2254986
Create empty file /etc/default/wsdd and it is happy (sheesh!)
On Sun, Feb 11, 2024 at 7:11 PM Tom Horsley wrote:
>
> What on earth does that mean? Is there a contest to see who can
> generate the least useful error
What on earth does that mean? Is there a contest to see who can
generate the least useful error message? :-).
My best guess is that it is trying to use ipv6 and I have ipv6
turned off? Or is it trying to use a bridge I have that isn't
normally connected to anything?
--
Op Tue, 02 Jan 2024 17:36:51 +0100 schreef Ralf Corsépius
:
Am 29.12.23 um 15:40 schrieb Chris Adams:
Once upon a time, Ralf Corsépius said:
IMNSHO, it's time to demand FESCO to take consequences against these
persons.
On what basis?
Respect and reason?
The way the guys, who are
Am 29.12.23 um 21:54 schrieb Samuel Sieb:
On 12/29/23 07:02, Jeffrey Walton wrote:
It seems like (to me) lack of communication or coordination between
Fedora and RPMFusion is one of the root causes of the breaks.
I should have checked before making a comment like that. I don't know
Am 29.12.23 um 15:40 schrieb Chris Adams:
Once upon a time, Ralf Corsépius said:
IMNSHO, it's time to demand FESCO to take consequences against these
persons.
On what basis?
Respect and reason?
The way the guys, who are conducting the rebaser of ffmpeg on Cisco are
behaving rude,
RPMFusion has now pushed the packages to stable, for example see
https://download1.rpmfusion.org/free/fedora/updates/39/x86_64/g/ .
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
On 12/29/23 07:02, Jeffrey Walton wrote:
On Fri, Dec 29, 2023 at 4:02 AM Samuel Sieb wrote:
On 12/29/23 00:52, Frank Elsner via users wrote:
How can I solve this problem?
Error: Transaction test error:
file /usr/lib64/gstreamer-1.0/libgstasf.so from install of
On 12/29/23 05:12, Jonathan Billings wrote:
On Dec 29, 2023, at 04:16, Ralf Corsépius wrote:
Some overzealous RHAT employees are pushing incompatible and apparently
insufficently changes into released Fedoras.
IMNSHO, it's time to demand FESCO to take consequences against these persons.
On Fri, Dec 29, 2023 at 4:02 AM Samuel Sieb wrote:
>
> On 12/29/23 00:52, Frank Elsner via users wrote:
> > How can I solve this problem?
> >
> > Error: Transaction test error:
> >file /usr/lib64/gstreamer-1.0/libgstasf.so from install of
> > gstreamer1-plugins-ugly-free-1.22.8-2.fc39.x86_64
Once upon a time, Ralf Corsépius said:
> IMNSHO, it's time to demand FESCO to take consequences against these
> persons.
On what basis?
Not everybody uses RPMFusion, and there's absolutely nothing in the
Fedora guidelines about RPMFusion. Someone opened a BZ that said "hey,
looks like these
On Dec 29, 2023, at 04:16, Ralf Corsépius wrote:
>
> Some overzealous RHAT employees are pushing incompatible and apparently
> insufficently changes into released Fedoras.
>
> IMNSHO, it's time to demand FESCO to take consequences against these persons.
I have a hard time believing this was
See https://bodhi.fedoraproject.org/updates/FEDORA-2023-d9bca05694 . The
problem is that the gstreamer1-plugins-bad-freeworld and
gstreamer1-plugins-ugly from RPMFusion haven't yet been updated to be
compatible, though they have been built and signed and are waiting to be pushed
stable. If you
On 12/29/23 01:33, Frank Elsner wrote:
On Fri, 29 Dec 2023 01:02:20 -0800 Samuel Sieb wrote:
On 12/29/23 00:52, Frank Elsner via users wrote:
How can I solve this problem?
Error: Transaction test error:
file /usr/lib64/gstreamer-1.0/libgstasf.so from install of
On Fri, 29 Dec 2023 01:02:20 -0800 Samuel Sieb wrote:
> On 12/29/23 00:52, Frank Elsner via users wrote:
> > How can I solve this problem?
> >
> > Error: Transaction test error:
> >file /usr/lib64/gstreamer-1.0/libgstasf.so from install of
> >
Am 29.12.23 um 10:02 schrieb Samuel Sieb:
On 12/29/23 00:52, Frank Elsner via users wrote:
How can I solve this problem?
Error: Transaction test error:
file /usr/lib64/gstreamer-1.0/libgstasf.so from install of
gstreamer1-plugins-ugly-free-1.22.8-2.fc39.x86_64 conflicts with file
from
On 12/29/23 00:52, Frank Elsner via users wrote:
How can I solve this problem?
Error: Transaction test error:
file /usr/lib64/gstreamer-1.0/libgstasf.so from install of
gstreamer1-plugins-ugly-free-1.22.8-2.fc39.x86_64 conflicts with file from
package
Hello,
How can I solve this problem?
Error: Transaction test error:
file /usr/lib64/gstreamer-1.0/libgstasf.so from install of
gstreamer1-plugins-ugly-free-1.22.8-2.fc39.x86_64 conflicts with file from
package gstreamer1-plugins-ugly-1:1.22.7-1.fc39.x86_64
This is not the only file involved
On 9/25/23 23:46, Kaushal Shriyan wrote:
I am running Red Hat Enterprise Linux release 8.7 (Ootpa) OS in
production environment. I have enabled both epel in /etc/yum.repos.d
directory
There is a proxy server setup in the network. I have whitelisted the
below wildcard URLs as listed as per
Hi,
I am running Red Hat Enterprise Linux release 8.7 (Ootpa) OS in production
environment. I have enabled both epel in /etc/yum.repos.d directory
There is a proxy server setup in the network. I have whitelisted the below
wildcard URLs as listed as per epel repo.
https://*.fedoraproject.org
On 22 Sep 2023 at 8:04, George N. White III wrote:
From: "George N. White III"
Date sent: Fri, 22 Sep 2023 08:04:24 -0300
Subject:Re: Noticed Failed message with selinux-policy-targeted on 3 of
5 machines??
To: mi...@guam.net,
Community support for Fedora u
On Thu, Sep 21, 2023 at 3:30 PM Michael D. Setzer II via users <
users@lists.fedoraproject.org> wrote:
> On 21 Sep 2023 at 20:09, Zdenek Pytela wrote:
>
> From: Zdenek Pytela
>
[...]
>
> > It looks like you have quite an old container-selinux installed. (I
> already
> > asked twice to
On 21 Sep 2023 at 20:09, Zdenek Pytela wrote:
From: Zdenek Pytela
Date sent: Thu, 21 Sep 2023 20:09:44 +0200
Subject:Re: Noticed Failed message with selinux-policy-targeted on 3 of
5 machines??
To: mi...@guam.net
Copies to: Community support for Fedora users
Send reply
On Thu, Sep 21, 2023 at 7:21 PM Michael D. Setzer II wrote:
> On 21 Sep 2023 at 16:23, Zdenek Pytela wrote:
>
> From: Zdenek Pytela
> Date sent: Thu, 21 Sep 2023 16:23:01 +0200
> Subject: Re: Noticed Failed message with selinux-policy-targeted on
> 3 of 5 machi
On 21 Sep 2023 at 16:23, Zdenek Pytela wrote:
From: Zdenek Pytela
Date sent: Thu, 21 Sep 2023 16:23:01 +0200
Subject:Re: Noticed Failed message with selinux-policy-targeted on 3 of
5 machines??
To: mi...@guam.net
Copies to: Community support for Fedora users
Send reply
On Thu, Sep 21, 2023 at 12:28 AM Michael D. Setzer II
wrote:
> On 20 Sep 2023 at 19:57, Zdenek Pytela wrote:
>
> From: Zdenek Pytela
> Date sent: Wed, 20 Sep 2023 19:57:31 +0200
> Subject: Re: Noticed Failed message with selinux-policy-targeted on
> 3 of 5 machi
On 20 Sep 2023 at 19:57, Zdenek Pytela wrote:
From: Zdenek Pytela
Date sent: Wed, 20 Sep 2023 19:57:31 +0200
Subject:Re: Noticed Failed message with selinux-policy-targeted on 3 of
5 machines??
To: mi...@guam.net,
Community support for Fedora users
Send reply
c38.noarch
> 2/8
> Running scriptlet : selinux-policy-minimum-38.28-1.fc38.noarch
> 2/8
> Running scriptlet : selinux-policy-targeted-38.28-1.fc38.noarch
> 3/8
> Reinstalling : selinux-policy-targeted-38.28-1.fc38.noarch
> 3/8
> Running scriptlet : seli
Reinstalling : selinux-policy-targeted-38.28-1.fc38.noarch 3/8
Running scriptlet : selinux-policy-targeted-38.28-1.fc38.noarch 3/8
Failed to resolve allow statement at
/var/lib/selinux/targeted/tmp/modules/200/container/cil:1186
Failed to resolve AST
/usr/sbin/semodule
On Thu, 2023-07-27 at 17:36 +, Cătălin George Feștilă wrote:
> I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
> dnf group install tells me : Failed to resolve the transaction :
> Is Deepin Desktop Environment available on Fedora 39 ?
F39 is unreleased software. Y
I test again today with the same command and return more than 0 B, ...
dnf install deepin-desktop
and works well, you can find the result on my blogspot about fedora linux.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an
On 7/27/23 10:36, Cătălin George Feștilă wrote:
I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
dnf group install tells me : Failed to resolve the transaction :
Is Deepin Desktop Environment available on Fedora 39 ?
Paste the full error message
On Thu, 2023-07-27 at 17:36 +, Cătălin George Feștilă wrote:
> I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
The Chinese spyware?
Well, who knows if that's really true (then, now, or in the future).
But considering it's Chinese heritage, I wouldn't touch it with a ten
If I run :
dnf group list
the deepin-desktop is show with yes on Instaled column.
I try to update or install again but the result is :
...
Deepin Desktop Environment
...
After this operation 0 B will be used (install 0 B, remove 0 B).
Is this ok ...
and the result is nothing happend.
I try to install with dnf and dnf5 the Deepin Desktop Enviromnent.
dnf group install tells me : Failed to resolve the transaction :
Is Deepin Desktop Environment available on Fedora 39 ?
___
users mailing list -- users@lists.fedoraproject.org
On 17 Jul 2023 at 17:29, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 17:29:17 -0400
Subject:works fine - Re: F38 install fails on a Lenovo x120e - Failed
to set
new efi boot traget
From: Robert Moskowitz
To: Community support for Fedora users ,
Roger
is working!
On 7/17/23 15:40, Robert Moskowitz wrote:
I was getting ready to try again.
I pulled the CD drive and tried to get into bios setup, but was not
fast enough and it started booting F38!
It got as far as a things like
[Failed] Failed to start systemd-login.service - User Login Management
On 7/17/23 16:07, Michael D. Setzer II wrote:
First computer was a 1963 IBM 1130 with punch cards back in
1975. So started with old machines that still were working.. High
School..
I started with a teletype 55 baudot to a GE MarkV in '66. Best I can
figure out was our school (Euclid OH)
On 17 Jul 2023 at 11:25, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 11:25:31 -0400
To: Community support for Fedora users
From: Robert Moskowitz
Subject:F38 install fails on a Lenovo x120e - Failed to set
new efi boot
I was getting ready to try again.
I pulled the CD drive and tried to get into bios setup, but was not fast
enough and it started booting F38!
It got as far as a things like
[Failed] Failed to start systemd-login.service - User Login Management.
then a bunch more and hung.
So I am going
on "Installing boot
> loader".
> >>
> >> If finally came back with a dialog box with an error of:
> >>
> >> The following error occurred while installing the boot loader. The
> >> system will not be bootable. Would you like to ignore this an
re this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No|Yes
What should I do at this point. It IS an old system that has had a
number of ver of Fedora on it. It was booting F22 just fine, it seemed
but now it is all go
an hour with the spindizzy on "Installing boot loader".
If finally came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to s
On Mon, Jul 17, 2023 at 1:56 PM Robert Moskowitz wrote:
>
> I just recalled. There was a /boot/efi partition on the old F22 setup.
>
> But booting up F37 live now.
If you haven't done so, now would be a good time to update the
laptop's firmware. Get on the latest version.
And the kernel docs
d continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No|Yes
What should I do at this point. It IS an old system that has had a
number of ver of Fedora on it. It was booting F22 just fine, it seemed
but now it is all gone...
You
came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No
t; If finally came back with a dialog box with an error of:
>
> The following error occurred while installing the boot loader. The
> system will not be bootable. Would you like to ignore this and continue
> with the installation?
>
> Failed to set new efi boot target. This is most
It has the AMD E-350 duo core CPU which I am pretty sure is x64.
On 7/17/23 12:58, Barry wrote:
On 17 Jul 2023, at 16:26, Robert Moskowitz wrote:
What should I do at this point. It IS an old system that has had a number of
ver of Fedora on it. It was booting F22 just fine, it seemed but
oader".
If finally came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and
continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel o
> On 17 Jul 2023, at 16:26, Robert Moskowitz wrote:
>
> What should I do at this point. It IS an old system that has had a number of
> ver of Fedora on it. It was booting F22 just fine, it seemed but now it is
> all gone...
Is it a 64bit system or 32bit? Fedora needs 64bit now.
Barry
uot;.
>
> If finally came back with a dialog box with an error of:
>
> The following error occurred while installing the boot loader. The
> system will not be bootable. Would you like to ignore this and
> continue
> with the installation?
>
> Failed to set new efi boo
installing the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No|Yes
What should I do at this point. It IS an old system that has had a
num
are)(userdn="ldap:///anyone;);)
-
```
I also add those steps in my GitHub repo if you would like to check:
https://github.com/kresnasatya/migrate-openldap-to-389-ds-failed/blob/main/README.md
___
389-users mailing list -- 389-users@lists.fedorapro
(objectClass=organizationalUnit)")(version 3.0; acl
"Enable anyone ou read"; allow (read, search,
compare)(userdn="ldap:///anyone;);)
-
```
I also add those steps in my GitHub repo if you would like to check:
https://github.com/kresnasatya/migrate-openldap-to-389-ds-fail
> On 15 Mar 2023, at 02:32, Mark Reynolds wrote:
>
>
> On 3/13/23 10:08 PM, Kresna Satya wrote:
>> Hi everyone, currently I would like to move the LDAP tool from OpenLDAP and
>> 389 Directory Server. The data and configuration are saved in OpenLDAP and I
>> would like to migrate to 389
y GitHub repo to reproduce the migration steps from OpenLDAP
to 389 Directory
Server:https://github.com/kresnasatya/migrate-openldap-to-389-ds-failed
I also follow the YouTube tutorial from this video presented by
William Brownhttps://www.youtube.com/watch?v=qrbtWOXOhtA.
Unfortunately, it does
enLDAP to 389
Directory Server:
<https://github.com/kresnasatya/migrate-openldap-to-389-ds-failed>
https://github.com/kresnasatya/migrate-openldap-to-389-ds-failed
I also follow the YouTube tutorial from this video presented by William
Brown https://www.youtube.com/watch?v=qrbtWOXOhtA. U
On 1/16/23 14:10, Grant Gainey wrote:
On Mon, Jan 16, 2023 at 1:33 PM Grant Gainey wrote:
I'm not sure where to report the problem. Yes, F35 is EOL - but
the metalink for it returning 404 implies something is Not Right
in the infrastructure somewhere?
Just to close this loop -
On Mon, Jan 16, 2023 at 1:33 PM Grant Gainey wrote:
> I'm not sure where to report the problem. Yes, F35 is EOL - but the
> metalink for it returning 404 implies something is Not Right in the
> infrastructure somewhere?
>
Just to close this loop - asked in #fedora, has already been reported,
On Mon, Jan 16, 2023 at 9:49 AM Robert Moskowitz
wrote:
> Wanted to install enscript and it failed:
>
> Installing:
> enscript x86_64 1.6.6-27.fc35 fedora 413 k
>
> T
, the install worked fine on the new F37 I am setting up.
On 1/16/23 09:48, Robert Moskowitz wrote:
Wanted to install enscript and it failed:
Am I doing something wrong or is this prgm broken?
You could go to koji, download the binary rpm for F35,
https://koji.fedoraproject.org/koji/packageinfo
ok at this.
Barry
>
>> On 1/16/23 11:23, stan via users wrote:
>> On Mon, 16 Jan 2023 10:04:59 -0500
>> Robert Moskowitz wrote:
>>
>>> BTW, the install worked fine on the new F37 I am setting up.
>>>
>>> On 1/16/23 09:48, Robert Moskowitz wrote:
am setting up.
On 1/16/23 09:48, Robert Moskowitz wrote:
Wanted to install enscript and it failed:
Am I doing something wrong or is this prgm broken?
You could go to koji, download the binary rpm for F35,
https://koji.fedoraproject.org/koji/packageinfo?packageID=367
and manually install it from
On Mon, 16 Jan 2023 10:04:59 -0500
Robert Moskowitz wrote:
> BTW, the install worked fine on the new F37 I am setting up.
>
> On 1/16/23 09:48, Robert Moskowitz wrote:
> > Wanted to install enscript and it failed:
> > Am I doing something wrong or is this prgm broken?
BTW, the install worked fine on the new F37 I am setting up.
On 1/16/23 09:48, Robert Moskowitz wrote:
Wanted to install enscript and it failed:
Installing:
enscript x86_64 1.6.6-27.fc35 fedora 413 k
Transaction Summary
Wanted to install enscript and it failed:
Installing:
enscript x86_64 1.6.6-27.fc35 fedora 413 k
Transaction Summary
Install 1 Package
Total download size: 413 k
Installed size: 1.8 M
commands did nothing. Somewhat expected, but depends where in the upgrade
it failed - if it was during the download, they might be enough:
dnf upgrade
dnf history redo NN (NN being the "dnf upgrade" that did not complete)
I eneded up using dnf reinstall of all the packages involved
On Tue, 8 Nov 2022 08:03:55 -0800
Scott Beamer wrote:
> Greetings,
>
> I recently read somewhere that there is a dnf command to finish
> upgrading when an upgrade crashes during an upgrade. I tried Googling
> to find it just now and have come up empty.
>
> Does anyone know what it is?
Others
On Tue, 2022-11-08 at 08:03 -0800, Scott Beamer wrote:
> Greetings,
>
> I recently read somewhere that there is a dnf command to finish
> upgrading when an upgrade crashes during an upgrade. I tried Googling
> to
> find it just now and have come up empty.
>
> Does anyone know what it is?
I
On Tue, Nov 8, 2022 at 12:04 PM Scott Beamer
wrote:
> Greetings,
>
> I recently read somewhere that there is a dnf command to finish
> upgrading when an upgrade crashes during an upgrade. I tried Googling to
> find it just now and have come up empty.
>
> Does anyone know what it is?
>
I don’t
On 11/8/22 08:03, Scott Beamer wrote:
I recently read somewhere that there is a dnf command to finish
upgrading when an upgrade crashes during an upgrade. I tried Googling to
find it just now and have come up empty.
Does anyone know what it is?
yum had an option for that, but not dnf. Just
On 9/11/22 03:03, Scott Beamer wrote:
Greetings,
I recently read somewhere that there is a dnf command to finish
upgrading when an upgrade crashes during an upgrade. I tried Googling
to find it just now and have come up empty.
Does anyone know what it is?
I'm not sure you actually need a
On Tue, Nov 08, 2022 at 08:03:55AM -0800, Scott Beamer wrote:
Greetings,
I recently read somewhere that there is a dnf command to finish
upgrading when an upgrade crashes during an upgrade. I tried Googling to
find it just now and have come up empty.
Does anyone know what it is?
No, but
On 11/8/22 8:09 AM, Doug Herr wrote:
On Tue, Nov 8, 2022, at 8:03 AM, Scott Beamer wrote:
Greetings,
I recently read somewhere that there is a dnf command to finish
upgrading when an upgrade crashes during an upgrade. I tried Googling to
find it just now and have come up empty.
Does anyone
On Tue, Nov 8, 2022, at 8:03 AM, Scott Beamer wrote:
> Greetings,
>
> I recently read somewhere that there is a dnf command to finish
> upgrading when an upgrade crashes during an upgrade. I tried Googling to
> find it just now and have come up empty.
>
> Does anyone know what it is?
Not sure
1 - 100 of 1274 matches
Mail list logo
