Bug 267830 - ports-mgmt/poudriere bulk canceled due to expired port
Summary: ports-mgmt/poudriere bulk canceled due to expired port
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Bryan Drewery
URL: https://www.freshports.org/www/grafana7/
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-17 16:42 UTC by Boris Tassou
Modified: 2022-12-22 07:01 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (bdrewery)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Tassou 2022-11-17 16:42:09 UTC
Hi,

With poudriere-3.3.7_1 on 13.1-RELEASE-p2.

Is it possible to build even if a port is expired?
[00:00:39] Gathering ports metadata
[00:00:39] Error: MOVED: www/grafana7 2022-11-07 Has expired: EOLed upstream, unfixed vulnerabilities
[00:00:39] Error: Fatal errors encountered gathering initial ports metadata
[00:00:39] Cleaning up

By excluding it from the list for example?

Thanks!
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2022-11-17 22:12:18 UTC
(In reply to Boris Tassou from comment #0)

You could methodically put your copy of the tree into a state that preceded the move. 

Alternatively, re: <https://www.freshports.org/www/grafana7/#history>, is it not preferable to use a replacement – a version that is not vulnerable? 

<https://www.freshports.org/www/grafana8/>
<https://www.freshports.org/www/grafana9/>

----

Generally, I see this as not a bug; the type of thing that might be better discussed at <https://github.com/freebsd/poudriere/discussions> or in some other FreeBSD community support area. 

HTH
Comment 2 Bryan Drewery freebsd_committer freebsd_triage 2022-11-17 23:57:23 UTC
Yeah we should fix this to be considered a IGNORED/SKIPPED port. It would still need to cause a build failure since a port you wanted isn't being built.
Comment 3 Boris Tassou 2022-11-18 08:17:55 UTC
A build failure it's understandable yes, not to stop the bulk at the beginning.

I didn't know this space https://github.com/freebsd/poudriere/discussions, i can open a discussion there if you want.
Comment 4 Bryan Drewery freebsd_committer freebsd_triage 2022-11-19 03:10:53 UTC
(In reply to Boris Tassou from comment #3)

Haha I didn't know about that either.

I totally agree with you. It shouldn't stop at the beginning. I would definitely remember to handle this better if it were entered in github issues.
Comment 5 Boris Tassou 2022-11-21 09:49:34 UTC
Issue is opened : https://github.com/freebsd/poudriere/issues/1026

Thanks for your answers and your work!
Comment 6 Bryan Drewery freebsd_committer freebsd_triage 2022-12-21 20:40:37 UTC
Replying here and github.

It occurred to me today that I don't see how this *cannot* be a hard error. In the "expired" case the port directory is *deleted*. There is no replacement. What should be done instead? A package that was requested to be built cannot be satisfied. It could build everything else but in the end it will consider it a failure since it could not satisfy the request.