On Tue, 2024-10-22 at 22:59 -0700, Samuel Sieb wrote:
> You could keep your /home directory (assuming you aren't the person that
> said they don't separate that), but yes, a wipe and re-install of the
> root partition.
Long ago, probably back before Fedora existed, I did installs in place
by boo
On 10/22/24 8:04 PM, ToddAndMargo via users wrote:
On 10/22/24 13:57, Samuel Sieb wrote:
I highly recommend a re-install at this point or when you decide to go
to F41.
Do yo mean wipe and reinstall? Or is there
an in place reinstall?
You could keep your /home directory (assuming you aren't
On 10/22/24 20:04, ToddAndMargo via users wrote:
On 10/22/24 13:57, Samuel Sieb wrote:
I highly recommend a re-install at this point or when you decide to go
to F41.
Do yo mean wipe and reinstall? Or is there
an in place reinstall?
My backups have most of the offending thing on
them that ca
On 10/22/24 16:25, Samuel Sieb wrote:
On 10/22/24 4:21 PM, ToddAndMargo via users wrote:
On 10/22/24 6:51 AM, Felix Miata wrote:
I would expect
dnf distro-sync --releasever=40
to fix it.
# dnf distro-sync --releasever=40
Last metadata expiration check: 0:41:28 ago on Tue 22 Oct 2024
0
On 10/22/24 13:57, Samuel Sieb wrote:
I highly recommend a re-install at this
point or when you decide to go to F41.
Do yo mean wipe and reinstall? Or is there
an in place reinstall?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsu
ToddAndMargo composed on 2024-10-22 16:21 (UTC-0700):
> Felix Miata wrote:
>> I would expect
>> dnf distro-sync --releasever=40
>> to fix it.
> # dnf distro-sync --releasever=40
> Last metadata expiration check: 0:41:28 ago on Tue 22 Oct 2024 03:39:09
> PM PDT.
> Error:
> Problem: The
(f-40; gnome; stand-alone dual-boot workstation; kernel 6.11.3)
Selected command output...
-bash.2[~]: rpm -qa kernel
kernel-6.10.12-200.fc40.x86_64
kernel-6.11.3-200.fc40.x86_64
-bash.3[~]:
-bash.3[~]: rpm -qa kernel-core
kernel-core-6.10.12-200.fc40.x86_64
kernel-core-6.11.3-200.fc40.x86_64
-
On 10/22/24 6:19 PM, Samuel Sieb wrote:
On 10/22/24 5:15 PM, home user via users wrote:
On 10/22/24 4:20 PM, Samuel Sieb wrote:
On 10/22/24 3:11 PM, Joe Zeff wrote:
On 10/22/2024 03:17 PM, home user via users wrote:
ok. I'll assume the messages are gone and move on to the next problem.
If
On 10/22/24 5:15 PM, home user via users wrote:
On 10/22/24 4:20 PM, Samuel Sieb wrote:
On 10/22/24 3:11 PM, Joe Zeff wrote:
On 10/22/2024 03:17 PM, home user via users wrote:
ok. I'll assume the messages are gone and move on to the next problem.
If you want to save any messages, add this t
On 10/22/24 4:20 PM, Samuel Sieb wrote:
On 10/22/24 3:11 PM, Joe Zeff wrote:
On 10/22/2024 03:17 PM, home user via users wrote:
ok. I'll assume the messages are gone and move on to the next problem.
If you want to save any messages, add this to the command:
> tee output.txt
This will let
ToddAndMargo via users wrote:
> Fedora 40 (perhaps)
> bash-completion-2.11-14.fc40.noarch
>
> When I open a (bash) terminal, I get the following errors
>
[...]
> bash: _comp_deprecate_func: command not found
> bash: _comp_deprecate_var: command not found
Searching the fine web tells you that thi
On 10/22/24 4:21 PM, ToddAndMargo via users wrote:
On 10/22/24 6:51 AM, Felix Miata wrote:
I would expect
dnf distro-sync --releasever=40
to fix it.
# dnf distro-sync --releasever=40
Last metadata expiration check: 0:41:28 ago on Tue 22 Oct 2024 03:39:09
PM PDT.
Error:
Problem: The
On 10/22/24 6:51 AM, Felix Miata wrote:
I would expect
dnf distro-sync --releasever=40
to fix it.
# dnf distro-sync --releasever=40
Last metadata expiration check: 0:41:28 ago on Tue 22 Oct 2024 03:39:09
PM PDT.
Error:
Problem: The operation would result in removing the following
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
Hi All,
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade
Unknown argument "--skip-broken" for command "dnf5". Add "--help" for
more information about the arguments.
-T (T/Mr.T/Todd/Dude/His Resplendence)
Hi All,
Fedora 40 (perhaps)
bash-completion-2.11-14.fc40.noarch
When I open a (bash) terminal, I get the following errors
bash: _comp_deprecate_func: command not found
bash: _comp_deprecate_func: command not found
bash: _comp_deprecate_func: command not found
bash: _comp_deprecate_func: command
On 10/22/24 3:11 PM, Joe Zeff wrote:
On 10/22/2024 03:17 PM, home user via users wrote:
ok. I'll assume the messages are gone and move on to the next problem.
If you want to save any messages, add this to the command:
> tee output.txt
This will let you both see the output and save it to a
On 10/22/2024 03:17 PM, home user via users wrote:
ok. I'll assume the messages are gone and move on to the next problem.
If you want to save any messages, add this to the command:
> tee output.txt
This will let you both see the output and save it to a file. HTH HAND.
--
On 10/22/24 3:00 PM, Samuel Sieb wrote:
On 10/22/24 1:56 PM, home user via users wrote:
On 10/22/24 2:51 PM, Samuel Sieb wrote:
On 10/22/24 1:47 PM, home user via users wrote:
On 10/22/24 12:06 AM, Samuel Sieb wrote:
On 10/21/24 7:25 PM, home user via users wrote:
(f-40; gnome; stand-alone w
On 10/22/24 1:56 PM, home user via users wrote:
On 10/22/24 2:51 PM, Samuel Sieb wrote:
On 10/22/24 1:47 PM, home user via users wrote:
On 10/22/24 12:06 AM, Samuel Sieb wrote:
On 10/21/24 7:25 PM, home user via users wrote:
(f-40; gnome; stand-alone workstation)
During this past Saturday's
On 10/22/24 2:46 AM, ToddAndMargo via users wrote:
On 10/22/24 02:38, Samuel Sieb wrote:
On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --sk
On 10/22/24 2:51 PM, Samuel Sieb wrote:
On 10/22/24 1:47 PM, home user via users wrote:
On 10/22/24 12:06 AM, Samuel Sieb wrote:
On 10/21/24 7:25 PM, home user via users wrote:
(f-40; gnome; stand-alone workstation)
During this past Saturday's "dnf upgrade", I saw a lot of problem messages
d
On 10/22/24 1:47 PM, home user via users wrote:
On 10/22/24 12:06 AM, Samuel Sieb wrote:
On 10/21/24 7:25 PM, home user via users wrote:
(f-40; gnome; stand-alone workstation)
During this past Saturday's "dnf upgrade", I saw a lot of problem
messages during the clean-up phase. I was distract
On 10/22/24 12:06 AM, Samuel Sieb wrote:
On 10/21/24 7:25 PM, home user via users wrote:
(f-40; gnome; stand-alone workstation)
During this past Saturday's "dnf upgrade", I saw a lot of problem messages
during the clean-up phase. I was distracted and therefore forgot to copy the relevant
mes
On Tue, Oct 22, 2024 at 03:13:01AM -0400, Jeffrey Walton wrote:
>
> It is not valid, and you won't find a RFC authorizing it. And it
> breaks SPF and DKIM authentications.
It's perfectly valid.
This is the DMARC mitigation in mailman3.
Before/without:
sender -> list -> subscriber
If sender h
> On 22 Oct 2024, at 15:54, Neal Becker wrote:
>
> Doesn't 41 still offer dnf? I have both installed on 40.
on f40 dnf4 is default and recommended. You can experiment with dnf5, but
beware of bugs.
on f41 dnf5 is default and recommanded. You can fall back to dnf4 if something
important brea
On Tue, Oct 22, 2024 at 5:46 AM ToddAndMargo via users <
users@lists.fedoraproject.org> wrote:
> On 10/22/24 02:38, Samuel Sieb wrote:
> > On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
> >> On 10/22/24 02:22, Samuel Sieb wrote:
> >>> On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
> W
ToddAndMargo composed on 2024-10-22 03:58 (UTC-0700):
> Tim wrote:
>> On Tue, 2024-10-22 at 02:37 -0700, ToddAndMargo wrote:
>>> I am temporarily gettig around it with dnf's
>>> "--setopt=excludepkgs=systemd"
>> You do realise that, in this day and age, that's akin to trying to
>> install Linux
On 10/22/24 3:08 AM, Samuel Sieb wrote:
On 10/21/24 11:28 PM, Jeffrey Walton wrote:
On Tue, Oct 22, 2024 at 1:58 AM Samuel Sieb wrote:
On 10/21/24 9:09 PM, ToddAndMargo via users wrote:
Why does my "From:" come out "Community support for
Fedora users" when my posts show on this list?
Ther
On 10/22/24 03:54, Tim wrote:
On Tue, 2024-10-22 at 02:37 -0700, ToddAndMargo via users wrote:
I am temporarily gettig around it with dnf's
"--setopt=excludepkgs=systemd"
You do realise that, in this day and age, that's akin to trying to
install Linux without any kernel.
# rpm -qa systemd
s
On Tue, 2024-10-22 at 02:37 -0700, ToddAndMargo via users wrote:
> I am temporarily gettig around it with dnf's
> "--setopt=excludepkgs=systemd"
You do realise that, in this day and age, that's akin to trying to
install Linux without any kernel.
--
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_6
Samuel Sieb:
> > There are certain providers who have spam protection settings that cause
> > problems with mailing lists. I assume yours is one of them. For email
> > addresses with those providers, the mailing list rewrites the From to be
> > from the mailing list and puts your original email a
On 10/22/24 02:20, Samuel Sieb wrote:
On 10/22/24 2:14 AM, ToddAndMargo via users wrote:
In file /etc/yum.repos.d/fedora.repo,
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-
$releasever&arch
Where does the "$releasever" come from? how can
I reproduce it from the command li
On 10/22/24 02:38, Samuel Sieb wrote:
On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade
Unknown argument "--skip-broken" f
On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade
Unknown argument "--skip-broken" for command "dnf5". Add "--help" for
mo
On 10/22/24 02:34, ToddAndMargo via users wrote:
# dnf remove systemd-254.18-1.fc39.x86_64
Failed to resolve the transaction:
Problem: installed package systemd-udev-254.18-1.fc39.x86_64 requires
libsystemd-shared-254.18-1.fc39.so()(64bit), but none of the providers
can be installed
- instal
On Tue, 22 Oct 2024 at 10:20, Samuel Sieb wrote:
> On 10/22/24 2:14 AM, ToddAndMargo via users wrote:
> > In file /etc/yum.repos.d/fedora.repo,
> >
> > metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-
> > $releasever&arch
> >
> > Where does the "$releasever" come from? how can
>
Hi All,
I am on Fedora 40 now.
I have a bunch of 39 packages still. I amn update them one at a time,
but there a ton of them
A global updates get me this:
# dnf --releasever=40 upgrade --skip-unavailable
Updating and loading repositories:
Repositories loaded.
Failed to resolve the transacti
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade
Unknown argument "--skip-broken" for command "dnf5". Add "--help" for
more information about the arguments.
How did you en
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade
Unknown argument "--skip-broken" for command "dnf5". Add "--help" for
more information about the arguments.
How did you end up with dnf5? That might explain som
On 10/22/24 2:14 AM, ToddAndMargo via users wrote:
In file /etc/yum.repos.d/fedora.repo,
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-
$releasever&arch
Where does the "$releasever" come from? how can
I reproduce it from the command line? (It is different
than /etc/redhat-
Hi All,
In file /etc/yum.repos.d/fedora.repo,
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch
Where does the "$releasever" come from? how can
I reproduce it from the command line? (It is different
than /etc/redhat-release.)
Many thanks,
-T (T/Mr.T/Todd/Dude/H
Hi All,
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade
Unknown argument "--skip-broken" for command "dnf5". Add "--help" for
more information about the arguments.
-T (T/Mr.T/Todd/Dude/His Resplendence)
--
~~
Computers are
On 10/22/24 00:08, Samuel Sieb wrote:
The spam settings of the sender's provider causes some receiving
providers to reject the email. Neither user on either end wants this to
happen. So the mailing list becomes the sender, which is completely
valid, and then there is no issue for those receivi
On Tue, Oct 22, 2024 at 3:09 AM Samuel Sieb wrote:
>
> On 10/21/24 11:28 PM, Jeffrey Walton wrote:
> > On Tue, Oct 22, 2024 at 1:58 AM Samuel Sieb wrote:
> >>
> >> On 10/21/24 9:09 PM, ToddAndMargo via users wrote:
> >>> Why does my "From:" come out "Community support for
> >>> Fedora users" when
On 10/21/24 11:28 PM, Jeffrey Walton wrote:
On Tue, Oct 22, 2024 at 1:58 AM Samuel Sieb wrote:
On 10/21/24 9:09 PM, ToddAndMargo via users wrote:
Why does my "From:" come out "Community support for
Fedora users" when my posts show on this list?
There are certain providers who have spam prot
45 matches
Mail list logo
