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
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
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
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 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
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: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
>
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
12 matches
Mail list logo
