Bug 30881 - package of wpa_supplicant has a wrong package website url configured
Summary: package of wpa_supplicant has a wrong package website url configured
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-23 11:54 CEST by Elmar Stellnberger
Modified: 2022-09-28 21:25 CEST (History)
1 user (show)

See Also:
Source RPM: wpa_supplicant-2.9-8.3.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Elmar Stellnberger 2022-09-23 11:54:52 CEST
correct up-to-date url: 
https://w1.fi[/wpa_supplicant/]

note: There is a good link from w1.fi/ to w1.fi/wpa_supplicant/ so you can link the main url which does also include the mailing list which is of great use to everyone who has a problem with wpa_supplicant 

old stale url currently still being used for this package (please crop):  
https://hostap.epitest.fi/wpa_supplicant/

Please update to the correct website! The old website contains an out of date reference to a no more used mailing list and several dead links instead of the sample configuration files.
Comment 1 Lewis Smith 2022-09-23 20:48:45 CEST
Thank you for this observation.

Assigning globally as 'wpa_supplicant' has no particular maintainer.

Assignee: bugsquad => pkg-bugs

Lewis Smith 2022-09-23 20:49:44 CEST

Whiteboard: (none) => CAULDRON TOO ?

Comment 2 Jani Välimaa 2022-09-28 08:46:23 CEST
I don't think we push updates just for an URL fix. In Cauldron it's fixed since November 2021.

https://svnweb.mageia.org/packages?view=revision&revision=1758737
Comment 3 Morgan Leijström 2022-09-28 09:38:37 CEST
Right.

If it is fixed in source for next build I think we can close this.

Or is it wrong to close before landing in updates repo?

CC: (none) => fri
Whiteboard: CAULDRON TOO ? => (none)

Comment 4 Elmar Stellnberger 2022-09-28 14:20:54 CEST
I would push an update, yes; at least if you are not already planning another one. Having the right url is definitely of value and not everyone is running Cauldron, especially if you need assistence. Nonetheless the decision shall be up to you.
Comment 5 Thomas Backlund 2022-09-28 21:25:32 CEST
We wont push an update for an url change in the description.

It's fixed in Cauldron and same fix is queued in svn for Mga8 so it will be part of next update whenever that is...

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.