I've been having a weird issue with
This behavior is the same as what typically happens (correctly) when there's an *old* version of the package in that directory:
I have a guess as to what may be wrong, but I am not a porter and I don't have enough knowledge to say for sure that this is the issue:
This commit to
Again, I am an ignorant non-porter, but the impression I get from my brief reading about them is that this seems like something that could cause a ports management system (like
I assume that if my guess for the reason is correct, fixing it would be done by making a new commit with a new PORTREVISION? Is this the proper place to request such a thing? If not, where is? And in any case, whether I'm right or not, does anyone have any idea what's going wrong here, or how to fix it?
Thanks in advance.
devel/viewvc-devel@py39
recently. It seems to build fine (using synth
); synth
claims that everything (including this) built OK, gives no errors (as far as I can see) in its log files, and in fact does create a py39-viewvc-devel-1.3.0.20230104.pkg
file in /var/synth/live_packages/All
. But when I then do a synth rebuild-repository
, it tells me that this package (along with three packages that it depends on, subversion
, py39-subversion
, and mod_dav_svn
) "failed dependency check". After that, the package (and those other three) are no longer present in /var/synth/live_packages/All
.This behavior is the same as what typically happens (correctly) when there's an *old* version of the package in that directory:
synth
says that the old version "failed dependency check", and deletes it.I have a guess as to what may be wrong, but I am not a porter and I don't have enough knowledge to say for sure that this is the issue:
This commit to
viewvc-devel
, made last week, apparently broke something (not necessarily the issue I'm facing), as the next day, the same developer submitted this commit with the log message "Fix my broken patch". My suspicion is aimed at that second commit (the "Fix my broken patch" one) for perhaps causing the issue I'm facing. I suspect this because that commit changed neither the DISTVERSION nor the PORTREVISION.Again, I am an ignorant non-porter, but the impression I get from my brief reading about them is that this seems like something that could cause a ports management system (like
synth
) to not realize that the package it just built is the package it should have built.I assume that if my guess for the reason is correct, fixing it would be done by making a new commit with a new PORTREVISION? Is this the proper place to request such a thing? If not, where is? And in any case, whether I'm right or not, does anyone have any idea what's going wrong here, or how to fix it?
Thanks in advance.