On 25 Nov 2024 at 8:10, ToddAndMargo via users wrote:

Date sent:              Mon, 25 Nov 2024 08:10:18 -0800
To:                     Community support for Fedora users 
<users@lists.fedoraproject.org>
Subject:                winehq.repo baseurl not update revision
Send reply to:          Community support for Fedora users 
<users@lists.fedoraproject.org>
From:                   ToddAndMargo via users 
<users@lists.fedoraproject.org>
Copies to:              ToddAndMargo <toddandma...@zoho.com>

> Hi All,
> 
> Fedora 41 (from fc 40)
> wine-staging 9.21 & 9.17 (WineHQ)
> 
> I noticed that `dnf upgrade wine-staging` left me on 9.17. On
> investigation, I found that my /etc/yum.repos.s/winehq.repo's
> baseurl was still on "40". vi'ing (editing) it to "41" solved
> the issue.

Just to note. Generally there is a delay between Fedora coming out 
with a new release, and winehq creating the repo for the new 
version.  So, can be an issue with updating the winehq.repo.

This was also a bigger issue this time, since upgrading to 41 had a 
dependency issue that caused the wine to be downgraded to 9.17? 
Seems 9.18 and above were not compatiable to 41?

If you chane the winehq.repo to 41, it would get error, since that 
repo didn't yet exist. Then when it did, the winehq was upgraded.

I use a script to do version upgrade and have it edit the wineq.repo
(Have to manually change it. This notebook is still on 40 so doesn't 
have the 41. Also, found that the --skip-broken and --allowerasing 
where not needed with the 40 to 41 upgrate.

geany /etc/yum.repos.d/winehq.repo
dnf system-upgrade download --releasever=40 
#--skip-broken --allowerasing

First time I have had a downgrade issue with winehq, but they got 
the 41 repo out after a little delay.





> 
> Question: when I upgrade Fedora from a prior Fedora release,
> am I required to manually vi my winehq.repo to the new release
> or was this a fluke? I need this info for my notes of Fedora
> release upgrades.
> 
> Many thanks,
> -T
> 
> -- 
> _______________________________________________
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue


+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:mi...@guam.net                            
 mailto:msetze...@gmail.com
 mailto:msetze...@gmx.com
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+



-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to