Summary: | emulators/i386-wine{-devel}: Delete ports (was: Fails to fetch: i386-wine-devel-6.12,1.txz: Not Found) | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Miroslav Lachman <000.fbsd> |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Closed DUPLICATE | ||
Severity: | Affects Many People | CC: | Alexander88207, gerald, koobs |
Priority: | --- | Flags: | Alexander88207:
maintainer-feedback+
gerald: merge-quarterly+ |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any | ||
URL: | https://reviews.freebsd.org/D32322 |
Description
Miroslav Lachman
2021-11-01 10:04:49 UTC
Hello Miroslav, the regular wine ports and wine-proton (emulators/wine, emulators/wine-devel) do have now i386 support. That means you can use now 32-bit and 64-bit ports at the same time. Thus, this port have gotten unnecessary and requested for removal. See: https://reviews.freebsd.org/D32322 (In reply to Alexander Vereeken from comment #1) Thank you for the information. Then I think this PR can be closed and port emulators/i386-wine-devel removed as soon as possible because it is unbuildable now. No problem. If there are any questions about this topic or other wine related things i am happy to help. (In reply to Alexander Vereeken from comment #3) 1) Is it possible to address the 404 in the short term, pending deprecation and removal? 2) Does this issue's summary need updating to 'Add DEPRECATED and EXPIRATION_DATE' ? (In reply to Kubilay Kocak from comment #4) The port should simply disappear. The port does not need an expiration date or anything else. I don't have the distfiles anymore anyway. Feel free to take over D32322. (In reply to Kubilay Kocak from comment #4) Maybe there should be an entry in MOVED if it helps with pkg upgrade? i386-wine-devel -> wine-devel (In reply to Miroslav Lachman from comment #6) Please update the review to include the MOVED entry (if this is the appropriate user path) (In reply to Kubilay Kocak from comment #7) Cancel that, already provided I'm closing this as duplicate of PR#259589 where the maintainer provided a patch (even though that other PR came later). *** This bug has been marked as a duplicate of bug 259589 *** |