Bug 24121 - Mageia Welcome several weblinks link to incorrect Mageia webpages
Summary: Mageia Welcome several weblinks link to incorrect Mageia webpages
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords: 7beta1
Depends on:
Blocks:
 
Reported: 2019-01-04 08:01 CET by Ben McMonagle
Modified: 2019-01-31 06:51 CET (History)
2 users (show)

See Also:
Source RPM: MageiaWelcome
CVE:
Status comment:

Attachments
install report (175.96 KB, application/x-xz)
2019-01-04 08:07 CET, Ben McMonagle 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ben McMonagle 2019-01-04 08:01:59 CET 
Description of problem: clicking the following buttons: 
bugs tracker, community center, contribute, donations link to Mageia Forum
join us button links to Mageia wiki URPMI  webpage 


Version-Release number of selected component (if applicable):


How reproducible:every time


Steps to Reproduce:
1.open Mageia Welcome
2.Choose "more information" tab
3.click the above buttons
Ben McMonagle 2019-01-04 08:05:20 CET

Keywords: (none) => 7beta1

Comment 1 Ben McMonagle 2019-01-04 08:07:19 CET 
Created attachment 10635 [details]
install report
Comment 2 Marja Van Waes 2019-01-05 17:22:21 CET 
I can confirm this for a Dutch MageiaWelcome.

(Ben did a en_NZ install)

Assignee: bugsquad => mageiatools
CC: (none) => marja11, yves.brungard_mageia

Comment 3 papoteur 2019-01-05 18:24:37 CET 
The problem is a en_GB translation file which is updated from gettext with wrong link. The same occurs also with other languages.
I have cleaned all translation files, I hope it will not be erased by next update.
To check with the next release, coming soon.
Papoteur
Comment 4 Ben McMonagle 2019-01-31 06:51:13 CET 
looks good Mageia-7-beta2-x86_64
DATE.txt: Wed Jan 30 22:33:06 CET 2019

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.