I instaled Fedora 41 Beta workstation on a tablet and initially,
iio-sensor-proxy was working to update screen orientation. The screen rotated
automatically as in previous Fedora releases and the screen brightness updated
based on the surrounding light levels.
However, after upgrading via dnf
I instaled Fedora 41 Beta workstation on a tablet and initially,
iio-sensor-proxy was working to update screen orientation. The screen rotated
automatically as in previous Fedora releases and the screen brightness updated
based on the surrounding light levels.
However, after upgrading via dnf
*attending*
Den ons 5 juni 2024 kl 14:44 skrev Sumantro Mukherjee :
>
> Hey Folks,
>
> Many of you by now know that in Fedora, we try to open up more
> opportunities to test upcoming features which are currently being
> developed. This time DNF team is working closely with Fedo
Hey Folks,
Many of you by now know that in Fedora, we try to open up more
opportunities to test upcoming features which are currently being
developed. This time DNF team is working closely with Fedora QA to run
the DNF 5.2 test week[0].
As a part of this test week, we will be specifically
Testing Rawhide in a virtual machine. I have a repo file on a usb that
collects all the rpms. DNF complains if the repo is not available but
does not load the rpms. Is there some setting to get the repo processed?
--
___
test mailing list -- test
On Sat, 2023-10-21 at 12:20 +, Neil Chetty wrote:
> I have disabled fractional scaling and i use 200 percent as default scaling
> option.
>
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/XPJMMYAZKXYBT562BBQ5SO7O2BKKSILO/
>
> After a
So i downgraded few packages ( https://ibb.co/zszMJRJ ) Please see the image.
Now it is working fine. So any of the above packages is causing issue
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedo
# System Details Report
---
## Report details
- **Date generated:** 2023-10-21 17:52:19
## Hardware Information:
- **Hardware Model:** ASUSTeK COMPUTER INC.
VivoBook_ASUSLaptop K3402ZA_S3402ZA
- **Memory:**
I have disabled fractional scaling and i use 200 percent as default scaling
option.
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/XPJMMYAZKXYBT562BBQ5SO7O2BKKSILO/
After a recent dnf update which updated following packages. Whenever i open
apps all jetbrain
> Can you display the GRUB menu (listing all the installed kernels), when you
> repeatedly press F8 after starting the laptop?
I tried, and as far as I could tell repeatedly pressing F8 did not display the
GRUB menu. I started pressing as soon as I selected the partition.
> (A question is whethe
On Wed, Oct 18, 2023 at 7:37 PM Osama Albahrani via test <
test@lists.fedoraproject.org> wrote:
> Hi!
>
> I wanted to test Fedora Rawhide so I ran `dnf system-upgrade download
> --releasever rawhide --exclude=sdubby` (as per
> https://bugzilla.redhat.com/show_bug.cgi?id=22
Hi!
I wanted to test Fedora Rawhide so I ran `dnf system-upgrade download
--releasever rawhide --exclude=sdubby` (as per
https://bugzilla.redhat.com/show_bug.cgi?id=2243872#c12) to upgrade from
Fedora 39 and it finished successfully. However after I ran `dnf
system-upgrade reboot` and got a black
gt; >
> > > Den fre 11 aug. 2023 kl 05:27 skrev Sumantro Mukherjee
> > > :
> > >>
> > >> Hey Folks,
> > >>
> > >> DNF 5 landed in rawhide sometime back and has now been taken off F39
> > >> schedule. DNF 5 awaits testing and feedback b
to help next week too
> > if i am not too busy
> >
> > Den fre 11 aug. 2023 kl 05:27 skrev Sumantro Mukherjee
> > :
> >>
> >> Hey Folks,
> >>
> >> DNF 5 landed in rawhide sometime back and has now been taken off F39
> >> schedule.
ro Mukherjee
> :
>>
>> Hey Folks,
>>
>> DNF 5 landed in rawhide sometime back and has now been taken off F39
>> schedule. DNF 5 awaits testing and feedback before it can be
>> considered stable for Fedora users. DNF and Fedora Quality are hosting
>> a week-long
Have helped a bit today and yesterday, will try to help next week too
if i am not too busy
Den fre 11 aug. 2023 kl 05:27 skrev Sumantro Mukherjee :
>
> Hey Folks,
>
> DNF 5 landed in rawhide sometime back and has now been taken off F39
> schedule. DNF 5 awaits testing and feedbac
Infra
at this moment and will take some time. Nonetheless, we have something
called Heroes of Fedora, that
I will be running for F39 and you will get a mention when I pull up
all the test day data.
Thanks for testing!
>
>
> On Fri Aug 11, 2023 at 4:26 AM WAT, Sumantro Mukherjee wrote:
12, 2023 at 10:12 AM Ian Laurie wrote:
> On 8/1/23 09:55, Ian Laurie wrote:
> > In DNF5 how do you do this DNF4 style command?
> >
> > sudo dnf remove --oldinstallonly
> >
> > I'm guessing there must be a way but it's eluding me so far.
>
> Doe
On 8/1/23 09:55, Ian Laurie wrote:
In DNF5 how do you do this DNF4 style command?
sudo dnf remove --oldinstallonly
I'm guessing there must be a way but it's eluding me so far.
Does anyone know if this functionality will be added to DNF5 at some point?
--
Ian Laurie
FAS: nix
Yes! This is something I'd like to do, considering that DNF5 frustrated me last
week. Do we get badges for this one?
On Fri Aug 11, 2023 at 4:26 AM WAT, Sumantro Mukherjee wrote:
> Hey Folks,
>
> DNF 5 landed in rawhide sometime back and has now been taken off F39
> sched
Hey Folks,
DNF 5 landed in rawhide sometime back and has now been taken off F39
schedule. DNF 5 awaits testing and feedback before it can be
considered stable for Fedora users. DNF and Fedora Quality are hosting
a week-long testing period from Friday, August 11th through Thursday,
August 17th
In DNF5 how do you do this DNF4 style command?
sudo dnf remove --oldinstallonly
I'm guessing there must be a way but it's eluding me so far.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
test mailing li
I've heard a couple of folks report that they tried updating a Rawhide
system or container and it failed with:
Problem: The operation would result in removing the following protected
packages: dnf
The problem seems to be caused by doing the upgrade with an older dnf
installed. dnf-4.15.1-1
On Thu, Mar 16, 2023 at 11:54 AM Kamil Paral wrote:
>
> On Thu, Mar 16, 2023 at 10:14 AM Peter Robinson wrote:
>>
>>
>> On Wed, Mar 15, 2023 at 2:20 PM Frantisek Zatloukal
>> wrote:
>>>
>>> But that's microdnf, not the current default dnf. I
On Thu, Mar 16, 2023 at 10:14 AM Peter Robinson
wrote:
>
> On Wed, Mar 15, 2023 at 2:20 PM Frantisek Zatloukal
> wrote:
>
>> But that's microdnf, not the current default dnf. I don't think microdnf
>> was used by default in any of our blocking spins/images.
On Wed, Mar 15, 2023 at 2:20 PM Frantisek Zatloukal
wrote:
> But that's microdnf, not the current default dnf. I don't think microdnf
> was used by default in any of our blocking spins/images.
>
We ship microdnf in the arm minimal image due to issues with dnf and memory
usa
On Wed, Mar 15, 2023 at 3:20 PM Frantisek Zatloukal
wrote:
> But that's microdnf, not the current default dnf. I don't think microdnf
> was used by default in any of our blocking spins/images.
>
Totally correct. Thanks for the clarification.
_
Dnf5 as default is a f39 proposal
https://fedoraproject.org/wiki/Releases/39/ChangeSet
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
Em qua, 15 de mar de 2023 04:32, Sumantro Mukherjee
escreveu:
> DNF5 test day is running and we have figured that dnf modules command
> is
But that's microdnf, not the current default dnf. I don't think microdnf
was used by default in any of our blocking spins/images.
On Wed, Mar 15, 2023 at 1:44 PM Sumantro Mukherjee
wrote:
>
>
> On Wed, Mar 15, 2023 at 2:09 PM Frantisek Zatloukal
> wrote:
>
>>
On Wed, Mar 15, 2023 at 2:09 PM Frantisek Zatloukal
wrote:
> But the dnf > dnf5 switch will happen in F39, not F38, so that shouldn't
> be an issue that it's not supported in DNF 5, no?
>
I checked and it says F38 as target release
https://fedoraproject.org/wiki/Changes/
But the dnf > dnf5 switch will happen in F39, not F38, so that shouldn't be
an issue that it's not supported in DNF 5, no?
On Wed, Mar 15, 2023 at 8:32 AM Sumantro Mukherjee
wrote:
> DNF5 test day is running and we have figured that dnf modules command
> is being worked on.
DNF5 test day is running and we have figured that dnf modules command
is being worked on.
The functionality can be tracked [0] and this is targeted to be complete in F39.
If users, have modules enabled in F37 and upgrade to F38, things will be fine.
However, fresh installs or installations which
Hey Folks,
Since the brand new dnf5 package[0] has landed in F38, the Fedora QA
and DNF teams are organizing a test day to get some initial feedback
on it. We will be testing DNF 5 to iron out any rough edges.
We will be testing microdnf's all basic functionality from a user
perspective and
On Sun, 2023-01-29 at 02:40 +, George R Goffe via test wrote:
> Hi,
>
> Running dnf upgrade during periods of system instability seems to
> leave the system in an unknown state.
>
> How does one recover from this situation?
>
checkdupes:
package-cleanup --dupes
packa
On Sun, 29 Jan 2023, George R Goffe via test wrote:
Running dnf upgrade during periods of system instability seems to leave the
system in an unknown state.
How does one recover from this situation?
I believe the standard advice is to make a backup and reinstall.
Making a backup likely
On Sun, 29 Jan 2023 02:40:58 + (UTC)
George R Goffe via test wrote:
> Running dnf upgrade during periods of system instability seems to
> leave the system in an unknown state.
>
> How does one recover from this situation?
I assume you are on rawhide, since you are asking on t
Hi,
Running dnf upgrade during periods of system instability seems to leave the
system in an unknown state.
How does one recover from this situation?
Best regards,
George...
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send
On 12/20/22 11:45, Adam Williamson wrote:
On Tue, 2022-12-20 at 08:26 +1100, Ian Laurie wrote:
On 12/20/22 06:25, Kevin Fenzi wrote:
You can change your crypto policy:
sudo update-crypto-policies --set LEGACY
kevin
Thanks Kevin.
Of course, this reduces your security somewhat. It would als
On Tue, 2022-12-20 at 08:26 +1100, Ian Laurie wrote:
> On 12/20/22 06:25, Kevin Fenzi wrote:
> > You can change your crypto policy:
> >
> > sudo update-crypto-policies --set LEGACY
> >
> > kevin
>
> Thanks Kevin.
Of course, this reduces your security somewhat. It would also be a good
idea to co
On 12/20/22 06:25, Kevin Fenzi wrote:
You can change your crypto policy:
sudo update-crypto-policies --set LEGACY
kevin
Thanks Kevin.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
test mailing list -- test@lists.fedoraproject.o
On Mon, Dec 19, 2022 at 12:17:22PM +1100, Ian Laurie wrote:
> In testing and playing with Rawhide 20221217.n.0 I found I was unable to
> install the 3rd party program bcompare (Beyond Compare) for which I am
> licensed.
>
> With their repo installed "sudo dnf install bcompare
Is there a way to get around this problem and force the install?
I managed to install it by playing around with rpm.
But of course I now have the same issue as the other system, DNF doesn't
believe it's installed.
I am guessing the issue will prevent updates from working.
--
In testing and playing with Rawhide 20221217.n.0 I found I was unable to
install the 3rd party program bcompare (Beyond Compare) for which I am
licensed.
With their repo installed "sudo dnf install bcompare" produces the error:
Error: GPG check FAILED
However, if I use "s
On Sat, 2022-10-29 at 01:29 +, George R Goffe via test wrote:
> Hi,
>
> I've been seeing this problem for a few days now.
>
> I start a "normal" dnf upgrade that fails to complete because something in
> dnf or perhaps a script that triggers an oom-kill eve
Hi,
I've been seeing this problem for a few days now.
I start a "normal" dnf upgrade that fails to complete because something in dnf
or perhaps a script that triggers an oom-kill event.
I have seen this in a VM host (8G swap) and in a VM guest (2G swap)... both
FC38.
I wro
On 2022-07-14 11:35, George R Goffe via test wrote:
I experienced other problems during this "project", namely the command line
length problem in the grub menu entry (extensive cursor movement caused an apparent
system freeze). Should I write this up?
I've never seen that. Certain systems ca
Hi,
Thanks to those who responded! Sam, Dan, Adam, Sergio...
The problem has been resolved. I removed all but the kernel-headers package and
paused there to run vboxconfig. I got lucky so I stopped... Otherwise I would
have done the suggested "dnf distro-sync kernel-headers" c
ng to take the chance. Sigh...
>
> Am I missing something here?
You can do what Sergio suggested - `dnf distro-sync kernel-headers`. If
you now have only the official repos enabled, that should downgrade it
to the 'correct' current version for your release.
--
Adam W
l-headers package... 503 packages affected. Sigh.
>
yes , you should keep kernel-headers , you may do
dnf distro-sync kernel-headers
> What are your thoughts?
>
> Best regards,
>
> George...
>
> Sam wrote, "Try uninstalling ea
On 2022-07-10 08:34, George R Goffe via test wrote:
Thanks for responding to this plea for help... It's appreciated.
As expected, all kernel packages would have been successful... EXCEPT for the
kernel-headers package... 503 packages affected. Sigh.
What are your thoughts?
Delete them all ex
ed. Sigh.
>
yes , you should keep kernel-headers , you may do
dnf distro-sync kernel-headers
> What are your thoughts?
>
> Best regards,
>
> George...
>
> Sam wrote, "Try uninstalling each one sep
Sam,
Thanks for responding to this plea for help... It's appreciated.
As expected, all kernel packages would have been successful... EXCEPT for the
kernel-headers package... 503 packages affected. Sigh.
What are your thoughts?
Best regards,
George...
Sam wrote, "Try uninstalling each one sep
s,
George...
On Sunday, July 10, 2022 at 02:59:54 AM PDT, Dan Horák wrote:
On Sun, 10 Jul 2022 00:28:07 + (UTC)
George R Goffe via test wrote:
> Hi,
>
> I'm having trouble with dnf and the 5.19 kernel.
>
> I have tried to exclude the 5.19 kernel on this system (FC3
On Sun, 10 Jul 2022 00:28:07 + (UTC)
George R Goffe via test wrote:
> Hi,
>
> I'm having trouble with dnf and the 5.19 kernel.
>
> I have tried to exclude the 5.19 kernel on this system (FC37) because 1)
> Virtual box doesn't seem to support it yet, 2)
On 2022-07-09 17:28, George R Goffe via test wrote:
I'm having trouble with dnf and the 5.19 kernel.
I have tried to exclude the 5.19 kernel on this system (FC37) because 1)
Virtual box doesn't seem to support it yet, 2) the system gets stuck during
boot and the boot will NOT s
Hi,
I'm having trouble with dnf and the 5.19 kernel.
I have tried to exclude the 5.19 kernel on this system (FC37) because 1)
Virtual box doesn't seem to support it yet, 2) the system gets stuck during
boot and the boot will NOT succeed (It seems to be running a list of UUIDs).
T
On Fri, 2022-03-04 at 07:14 -0500, Neal Gompa wrote:
>
> It is planned to fix it: https://pagure.io/fesco/issue/2765
Oh. Great.
Thank you.
A.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedora
On Fri, Mar 4, 2022 at 6:46 AM Alessio wrote:
>
> It is not the first time that performing a system-upgrade from 35 to
> 36, I get:
>
> Error:
> Problem: problem with installed package mlocate-0.26-31.fc35.x86_64
> - package plocate-1.1.15-2.fc36.x86_64 conflicts with mlocate
> provided by mloc
It is not the first time that performing a system-upgrade from 35 to
36, I get:
Error:
Problem: problem with installed package mlocate-0.26-31.fc35.x86_64
- package plocate-1.1.15-2.fc36.x86_64 conflicts with mlocate
provided by mlocate-0.26-46.fc36.x86_64
- mlocate-0.26-31.fc35.x86_64 does
On Tue, Jul 27, 2021 at 9:00 AM stan via test
wrote:
>
> On Sun, 11 Jul 2021 12:50:56 -0700
> stan wrote:
>
> > I am running rawhide. When I do a dnf update, it goes at normal
> > speed, but the verify step takes a long time. I had an update of 789
> > MB, and
On Sun, 11 Jul 2021 12:50:56 -0700
stan wrote:
> I am running rawhide. When I do a dnf update, it goes at normal
> speed, but the verify step takes a long time. I had an update of 789
> MB, and it took ~ 30 minutes to verify. A 123 MB kernel install took
> between 10 and 15 minut
I am running rawhide. When I do a dnf update, it goes at normal speed,
but the verify step takes a long time. I had an update of 789 MB, and
it took ~ 30 minutes to verify. A 123 MB kernel install took between
10 and 15 minutes to verify. During these verify proceedings, dnf is
writing
On 4/1/21 8:25 AM, wang_chen wrote:
dnf -y groupinstall "C Development Tools and Libraries" "Development Tools"
Fedora Modular 34 - x
dnf -y groupinstall "C Development Tools and Libraries" "Development Tools"
Fedora Modular 34 - x86_64 - Test Updates
On 3/31/21 2:47 AM, Joachim Backes wrote:
I tried to upgrade from fc33 to fc34 BETA by usage of dnf system-upgrade
which I did successfully
for the last 4 or 5 fedora versions by the usage of that dnf plugin. But
for fc33, I was not successful:
The finalizing command "sudo dnf system-up
On 3/31/21 12:05 PM, Thomas Mittelstaedt wrote:
Am 31.03.2021 11:47 schrieb Joachim Backes
:
Hi,
I tried to upgrade from fc33 to fc34 BETA by usage of dnf
system-upgrade
which I did successfully
for the last 4 or 5 fedora versions by the usage of that dnf
plugin
Am 31.03.2021 11:47 schrieb Joachim Backes :Hi,
I tried to upgrade from fc33 to fc34 BETA by usage of dnf system-upgrade
which I did successfully
for the last 4 or 5 fedora versions by the usage of that dnf plugin. But
for fc33, I was not successful:
The finalizing command "sud
Hi,
I tried to upgrade from fc33 to fc34 BETA by usage of dnf system-upgrade
which I did successfully
for the last 4 or 5 fedora versions by the usage of that dnf plugin. But
for fc33, I was not successful:
The finalizing command "sudo dnf system-upgrade reboot" did a reboot,
b
Chris,
For some reason I did a "which sqlinte3" and discovered that my tool chain
contained a version fron 2013. OMG!
I'm so embarrassed.
Please accept my apologies for wasting your time with this problem.
Best regards,
George...
--
Chris Murphy
__
On Sun, Mar 14, 2021 at 4:05 PM George R Goffe via test
wrote:
>
> Chris,
>
> The inode is NOT the same one. I tried a sqlite dump | restore operation but
> it didn't work...
>
> With your journalctl -f and trying dnf history, dnf reported I/O errors but
> n
First, this shouldn't be necessary, therefore I'm kinda suspicious.
But it's inspecific suspicion. Maybe it is conversion.
I also don't know if this will fix the SQLite I/O errors, or make
things worse, in which case you'd lose dnf history (probably not a big
loss).
On Sat, Mar 13, 2021 at 8:03 PM George R Goffe via test
wrote:
>
> Chris,
>
> I see NO I/O messages.
You previously reported them.
>History database is not writable: SQLite error on
>"/var/lib/dnf/history.sqlite": Executing an SQL statement failed: disk I/O
>
Chris,
I see NO I/O messages.
I used less to look at history.sqlite. The file looks like a log file around
the time of a system crash. LOTS of unprintable characters. Some text at the
end that looks like they might be from dnf
e:776.00MiB, Used:105.33MiB (13.57%)
>/dev/sda5 776.00MiB
>
> System,single: Size:32.00MiB, Used:16.00KiB (0.05%)
>/dev/sda5 32.00MiB
>
> Unallocated:
>/dev/sda5 65.68MiB
>
>
>
>
> dmesg buffer, recent boot:
yeah what I'm looking for
On Fri, Mar 12, 2021 at 10:14 PM George R Goffe via test
wrote:
>
> Hi,
>
> Trying to upgrade this system with "dnf upgrade" gives messages:
>
> /usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
> --setopt=zchunk=0 --exclude=*kernel
Hi,
Trying to upgrade this system with "dnf upgrade" gives messages:
/usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
--setopt=zchunk=0 --exclude=*kernel* --exclude=environment-modules*
--exclude=Lmod upgrade
Fedora rawhide openh264 (From Cisco
Interesting. In 2016, when I filed
Bug 1397174 dnf history undo doesn't work even with keepcache=1 *
https://bugzilla.redhat.com/show_bug.cgi?id=1397174
the recommended workaround was to install the 'local' dnf plugin (package:
python3-dnf-plugin-local).
Installing the
the repo (fedora-repos-archive) are enabled by default
$ grep "enabled" /etc/yum.repos.d/fedora-updates-archive.repo
enabled=1
$ dnf history info 15
Transaction ID : 15
Begin time : Thu 31 Dec 2020 09:31:29 AM +08
Begin rpmdb: 1448:392d27370be7608526fcef0475d4bee78ebffc2
On Thu, Dec 31, 2020 at 12:20:35PM -0500, James Cassell wrote:
> To make downgrade work, you can install the fedora-repos-archive package
> and pass --enablerepo=fedora-archive when you attempt the downgrade/undo.
Huh. Learn something every day. Thanks :)
--
Matthew Miller
Fedora Project Leader
older packager version not available
>
To make downgrade work, you can install the fedora-repos-archive package and
pass --enablerepo=fedora-archive when you attempt the downgrade/undo.
> are there is someway to see verbose/debug of `dnf history` ? I tried
> with `-v` but nothing much
&
On Thursday, December 31, 2020 8:35:17 AM WET Robbi Nespu wrote:
> Hello Samuel, I don't get what you want show to me.
Although I am not Samuel I expected this to be related to your initial
message:
> are there is someway to see verbose/debug of `dnf history` ? I tried
> with `-
Hello Samuel, I don't get what you want show to me.
On 31/12/2020 1:20 pm, Samuel Sieb wrote:
On 12/30/20 6:15 PM, Robbi Nespu wrote:
# dnf history list
ID | Command line | Date
and time | Action(s) | Al
On 12/30/20 6:15 PM, Robbi Nespu wrote:
are there is someway to see verbose/debug of `dnf history` ? I tried
with `-v` but nothing much
# dnf history list
ID | Command line
| Date and time| Action(s)
| Altered
On Thu, Dec 31, 2020 at 10:15:27AM +0800, Robbi Nespu wrote:
> Do fedora only keep latest package version on repository?
Yes, generally.
You can get older packages from Koji, our build system, either by browsing
the web interface
https://koji.fedoraproject.org/koji/packageinfo?packageID=19055
or
`dnf history` ? I tried
with `-v` but nothing much
$ sudo dnf history undo last -v
Loaded plugins: builddep, changelog, config-manager, copr, debug,
debuginfo-install, download, generate_completion_cache,
needs-restarting, playground, repoclosure, repodiff, repograph,
repomanage, reposync
DNF
Adam,
Cool. Thanks for responding.
George...
On Monday, August 17, 2020, 10:49:53 AM PDT, Adam Williamson
wrote:
On Mon, 2020-08-17 at 17:40 +, George R Goffe via test wrote:
> Hi,
>
> Recently "we" switched to FC 34. I have upgraded my system several
> times but each time I d
On Mon, 2020-08-17 at 17:40 +, George R Goffe via test wrote:
> Hi,
>
> Recently "we" switched to FC 34. I have upgraded my system several
> times but each time I do so I get the enclosed messages.
>
> Is this a known problem?
Hi George! It's not uncommon, it just means either Cisco hasn't
Hi,
Recently "we" switched to FC 34. I have upgraded my system several times but
each time I do so I get the enclosed messages.
Is this a known problem?
THANKS FOR ALL YOUR HELP!
Best regards,
George...
/usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
On Wed, 2020-03-11 at 15:25 +0100, Kamil Paral wrote:
> On Wed, Mar 11, 2020 at 8:49 AM Felix Miata wrote:
>
> > From Adam's description I thought no modules were supposed to get reset,
> > and I
> > don't know what module dwm is about.
> >
>
> The reverse. All modules are getting reset during
On Wed, Mar 11, 2020 at 8:49 AM Felix Miata wrote:
> From Adam's description I thought no modules were supposed to get reset,
> and I
> don't know what module dwm is about.
>
The reverse. All modules are getting reset during upgrade, that's intended.
_
19
>> Upgrade 1169
>> Downgrade33
>> Total download size: 909M
>> DNF will only download...
> That looks fine to me, where do you think the problem is?
From Adam's description I thought no modules were supposed to get reset, and I
don't know what
On 3/11/20 12:28 AM, Felix Miata wrote:
I tried pulling the 31 to 32 trigger, but see this:
...
vim-minimal
Resetting modules:
dwm
Transaction summary
...
Install 19
Upgrade 1169
Downgrade 33
Total download size: 909M
DNF will only download...
That looks fine to me
then* run an upgrade
> to F32 with `dnf system-upgrade` (see
> https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ).
> Of course, since F32 is pre-Beta ATM, don't do this on important or
> production systems unless you're really sure you want to run a pre-
> rel
nstall the updates on F30/F31, *then* run an upgrade
> to F32 with `dnf system-upgrade` (see
> https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ).
> Of course, since F32 is pre-Beta ATM, don't do this on important or
> production systems unless you're really
shouldn't; they do this by resetting all
modules as part of the upgrade. We need folks to test that upgrading to
F32 after installing these updates works OK.
To test, *first* install the updates on F30/F31, *then* run an upgrade
to F32 with `dnf system-upgrade` (see
https://docs.fedoraproject.org/
Harold,
Thank you for your response.
I'll give your suggestion a try.
Thanks again,
George...
On Saturday, February 22, 2020, 12:23:50 AM PST, Harold Dost
wrote:
Your command is "dnf upgrade kernel'*'"
I'd try changing it to "dnf upgrade &
Your command is "dnf upgrade kernel'*'"
I'd try changing it to "dnf upgrade 'kernel*'" instead as there might be
something weird with it getting parsed.
Le sam. 22 févr. 2020 à 04:37, George R Goffe via test <
test@lists.fedoraproject.org> a écr
Adam,
Thanks for your response.
I'm not sure what you mean about "More context might help.". Here's the whole
command line + what dnf responds with. Do you want other info? Would
--debugsolve help?
dnf upgrade kernel'*'
Fedora - Rawhide - Developmental packag
ovide is not the problem. More context might help...
> Regards,
>
> George...
>
>
> dnf distro-sync
> Last metadata expiration check: 0:25:21 ago on Wed 19 Feb 2020 10:09:39 PM
> PST.
> Error:
> Problem: package kernel-modules-extra-5.6.0-0.rc1.git0.1.fc32.x86_64
Hi,
This message looks wrong to me. Of course there could be something I don't
understand. :-)
Notice the text after "requires" below. Is there a syntax error in the
"requires" part of the pkg?
Regards,
George...
dnf distro-sync
Last metadata expiration check:
1 - 100 of 612 matches
Mail list logo