Trying to build wine-devel in poudriere but cannot fetch distfile: =======================<phase: fetch >============================ => i386-wine-devel-6.12,1.txz doesn't seem to exist in /portdistfiles/FreeBSD:12:amd64. => Attempting to fetch http://Alexander88207.de/Homura/Winebuilds/FreeBSD:12:amd64/i386-wine-devel-6.12,1.txz fetch: http://Alexander88207.de/Homura/Winebuilds/FreeBSD:12:amd64/i386-wine-devel-6.12,1.txz: Not Found => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/FreeBSD:12:amd64/i386-wine-devel-6.12,1.txz fetch: http://distcache.FreeBSD.org/ports-distfiles/FreeBSD:12:amd64/i386-wine-devel-6.12,1.txz: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /portdistfiles/FreeBSD:12:amd64 and try again. *** Error code 1 Other ports fetch and build OK.
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 ***