Bug 1380972 - Package metadata for mingw-libsoup lists the wrong URL.
Summary: Package metadata for mingw-libsoup lists the wrong URL.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-libsoup
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-02 02:10 UTC by Audrey Yeena Toskin
Modified: 2018-02-23 22:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-23 22:29:02 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Audrey Yeena Toskin 2016-10-02 02:10:15 UTC 
Hello, epienbro

This is a fairly minor problem, but the package metadata for the following packages are out-of-date.

* mingw32-libsoup
* mingw32-libsoup-static
* mingw64-libsoup
* mingw64-libsoup-static

They currently list the projects' URL as

  https://live.gnome.org/LibSoup

but GNOME no longer uses the "live" subdomain; requests now get redirected to the wiki. I believe the new URL should be

  https://wiki.gnome.org/Projects/libsoup

(I'm filing this same bug report for multiple packages, so I apologize if you see this issue twice.)
Comment 1 Fedora Admin XMLRPC Client 2017-01-05 20:54:13 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Fedora Admin XMLRPC Client 2017-01-05 21:09:14 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Fedora End Of Life 2017-02-28 10:23:08 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
Comment 4 Audrey Yeena Toskin 2018-02-23 22:29:02 UTC 
This was fixed at some point. Thanks!
Note You need to log in before you can comment on or make changes to this bug.