[Bug 57811] New: wikis/Building-Wine contains broken/obsolete link

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57811

Bug ID: 57811
           Summary: wikis/Building-Wine contains broken/obsolete link
           Product: WineHQ.org
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: www-unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

As per instruction on the 404 website
"If you followed a link from a WineHQ.org page and reached this page in error,
please report it to the WineHQ.org Bugzilla.":

The link on the Wine Wiki
https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine
  https://www.winehq.org/pipermail/wine-devel/2016-January/111245.html
is broken resulting in 404.

[Bug 57811] wikis/Building-Wine contains broken/obsolete link

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57811

Bernhard Übelacker  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Bernhard Übelacker  ---
This is the latest version from archive.org:

https://web.archive.org/web/20230528053503/https://www.winehq.org/pipermail/...

And this would be this message from list.winehq.org:

https://list.winehq.org/mailman3/hyperkitty/list/[e-mail]/messa...

[Bug 57811] wikis/Building-Wine contains broken/obsolete link

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=57811

--- Comment #2 from Renzo de Paoli  ---
I saw that the wiki has been updated to include this link now.

(See https://www.winehq.org/pipermail/wine-devel/2016-January/111245.html).

I would consider this closed.

[Bug 57811] wikis/Building-Wine contains broken/obsolete link

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=57811

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Ken Sharp  ---
You can mark your own bug reports as fixed.