Re: poudriere: Ports a01debe78c6a results in failure: (devel/py-zope.configuration): Error: devel/py-zope.configuration depends on nonexistent origin

2023-08-27 Thread Kurt Jaeger 
Hi!

> On our poudriere build hosts poudriere fails out of the blue with the error 
> shown below.

Recently, many zope-related ports were removed:

https://lists.freebsd.org/archives/dev-commits-ports-all/2023-August/078541.html
https://lists.freebsd.org/archives/dev-commits-ports-all/2023-August/078545.html
https://lists.freebsd.org/archives/dev-commits-ports-all/2023-August/078546.html

That is the reason. You should be able to check out a git tree
with an older version of the ports tree and try to build there.

-- 
p...@freebsd.org +49 171 3101372  Now what ?

Re: poudriere: Ports a01debe78c6a results in failure: (devel/py-zope.configuration): Error: devel/py-zope.configuration depends on nonexistent origin

2023-08-27 Thread FreeBSD User 
On Sun, 27 Aug 2023 17:40:22 +0200
Kurt Jaeger  wrote:

Hello.


> Hi!
> 
> > On our poudriere build hosts poudriere fails out of the blue with the error 
> > shown
> > below.  

I realised that, but to the contrary, EoL'ing ports never resulted in a 
complete failure
of the build tree in poudriere.

An error warning was issued usually when a port has been EoL'ed and deleted and 
the local
list of to-be-build-ports still refered to it. I do not have any zope-related 
stuff in
the list or being aware of having ports depending on it (I simply do not know 
...).

Also, I tried to "grep -r" through etc/poudriere.d/ and its subfolders to find 
anything
useful as a hint referring to devel/py-zope or "py39-zope*" - nothing. So I 
concluded
this must be a serious error in some of the ports tree files ... I might be 
mistaken.
 
> 
> Recently, many zope-related ports were removed:
> 
> https://lists.freebsd.org/archives/dev-commits-ports-all/2023-August/078541.html
> https://lists.freebsd.org/archives/dev-commits-ports-all/2023-August/078545.html
> https://lists.freebsd.org/archives/dev-commits-ports-all/2023-August/078546.html
> 
> That is the reason. You should be able to check out a git tree
> with an older version of the ports tree and try to build there.
>

make index fails: no entry for /usr/ports/textproc/py-zope.i18nmessageid

2023-08-27 Thread Philipp Ost 

Hi everyone,

as the subject line says: make index fails with the following message

make_index: /usr/ports/devel/py-zope.configuration: no entry for 
/usr/ports/textproc/py-zope.i18nmessageid


The commit that caused this seems to be 
1daa5c9c40262b9dd10186c92bc3e250ff1bcc2b.


Kind regards
Philipp

Re: make index fails: no entry for /usr/ports/textproc/py-zope.i18nmessageid

2023-08-27 Thread Philipp Ost 

On 8/27/23 18:27, Philipp Ost wrote:

Hi everyone,

as the subject line says: make index fails with the following message

make_index: /usr/ports/devel/py-zope.configuration: no entry for 
/usr/ports/textproc/py-zope.i18nmessageid


The commit that caused this seems to be 
1daa5c9c40262b9dd10186c92bc3e250ff1bcc2b.


Kind regards
Philipp



This patch fixes it:

diff --git a/devel/py-zope.configuration/Makefile 
b/devel/py-zope.configuration/Makefile

index c6ce7f659cb3..d87bb7395c36 100644
--- a/devel/py-zope.configuration/Makefile
+++ b/devel/py-zope.configuration/Makefile
@@ -13,7 +13,6 @@ WWW=  https://pypi.org/project/zope.configuration/
 LICENSE=   ZPL21

 RUN_DEPENDS= 
${PYTHON_PKGNAMEPREFIX}zope.interface>=0:devel/py-zope.interface@${PY_FLAVOR} 
\
- 
${PYTHON_PKGNAMEPREFIX}zope.i18nmessageid>=0:textproc/py-zope.i18nmessageid@${PY_FLAVOR} 
\


${PYTHON_PKGNAMEPREFIX}zope.schema>=0:devel/py-zope.schema@${PY_FLAVOR}

 USES=  python


Best
Philipp

Re: poudriere: Ports a01debe78c6a results in failure: (devel/py-zope.configuration): Error: devel/py-zope.configuration depends on nonexistent origin

2023-08-27 Thread Ruslan Makhmatkhanov 
I partially reverted affecting commit (ce4a9c438d2c80e2625d207bdc9b52861ea62288).Everything should be ok now. Sorry for the mess. 27.08.2023, 18:33, "FreeBSD User" :On our poudriere build hosts poudriere fails out of the blue with the error shown below.I have no clue how to fix this problem. Even deleting the whole "All" folder (ergo:purging all built pkg packages) does not have any effect.I'm not familiar with the depedencies within the ports tree and how they are managed, itseems something serious affecting poudriere only (usual/traditional make on the portstree seems to work). [...][00:00:03] Inspecting ports tree for modifications to git checkout... no[00:00:04] Ports top-level git hash: a01debe78c6a[00:00:04] Gathering ports metadata===[00:01:26] Warning: (devel/py-zope.configuration): Error: devel/py-zope.configurationdepends on nonexistent origin 'textproc/py-zope.i18nmessageid' (port EXPIRED: 2023-08-27Remove leaf zope ports that have no sense in absence of zope itself); Please contactmaintainer of the port to fix this.[00:01:28] Error: Fatal errors encountered gathering ports metadataThanks in advaneceoh   -- Regards,Ruslan 

Re: poudriere: Ports a01debe78c6a results in failure: (devel/py-zope.configuration): Error: devel/py-zope.configuration depends on nonexistent origin

2023-08-27 Thread FreeBSD User 
Am Sun, 27 Aug 2023 21:02:53 +0300
Ruslan Makhmatkhanov  schrieb:

> I partially reverted affecting commit 
> (ce4a9c438d2c80e2625d207bdc9b52861ea62288).
> Everything should be ok now. Sorry for the mess.

Thank you.
oh
>  
> 27.08.2023, 18:33, "FreeBSD User" :
> 
> > 
> > 
> > On our poudriere build hosts poudriere fails out of the blue with the error 
> > shown below.
> > 
> > I have no clue how to fix this problem. Even deleting the whole "All" 
> > folder (ergo:
> > purging all built pkg packages) does not have any effect.
> > 
> > I'm not familiar with the depedencies within the ports tree and how they 
> > are managed, it
> > seems something serious affecting poudriere only (usual/traditional make on 
> > the ports
> > tree seems to work).
> > 
> > 
> >  [...]
> > 
> > [00:00:03] Inspecting ports tree for modifications to git checkout... no
> > [00:00:04] Ports top-level git hash: a01debe78c6a
> > [00:00:04] Gathering ports metadata
> > ===
> > [00:01:26] Warning: (devel/py-zope.configuration): Error: 
> > devel/py-zope.configuration
> > depends on nonexistent origin 'textproc/py-zope.i18nmessageid' (port 
> > EXPIRED: 2023-08-27
> > Remove leaf zope ports that have no sense in absence of zope itself); 
> > Please contact
> > maintainer of the port to fix this.
> > [00:01:28] Error: Fatal errors encountered gathering ports metadata
> > 
> > Thanks in advanece
> > 
> > oh
> >  
>  
>  
> -- 
> Regards,
> Ruslan
>  



-- 
O. Hartmann

make index fails: no entry for /usr/ports/databases/mysql-connector-java

2023-08-27 Thread Philipp Ost 

Hi,

`make index` fails as follows:

make_index: /usr/ports/databases/isql-viewer: no entry for 
/usr/ports/databases/mysql-connector-java


The change has been introduced in commit 
99af02b5255468335cc65fba0c7c9d3e583d5244.


The following patch should fix the issue:

diff --git a/databases/isql-viewer/Makefile b/databases/isql-viewer/Makefile
index 85e4f296e070..e177d531a668 100644
--- a/databases/isql-viewer/Makefile
+++ b/databases/isql-viewer/Makefile
@@ -14,7 +14,7 @@ WWW=  https://www.isqlviewer.com/

 RUN_DEPENDS=   ${JYTHON_PREFIX}/${JYTHON_JAR}:lang/jython \
${JAVALIBDIR}/postgresql.jar:databases/postgresql-jdbc \
- 
${JAVALIBDIR}/mysql-connector-java.jar:databases/mysql-connector-java
+ 
${JAVALIBDIR}/mysql-connector-java.jar:databases/mysql-connector-j


 USE_JAVA=  yes
 NO_BUILD=  yes


Best
Philipp

Re: Portscout is stuck

2023-08-27 Thread Graham Perrin 

On 20/06/2023 13:06, Moin Rahman wrote:

…

Maybe we’re rate limited by one of the big sites (e.g., github). Is/are
auth token(s) valid?

In case it’s really hanging, you might be able to tell how far it got
based on the db.

I've decreased the timeout of HTTP and FTP requests.

Yesterday I cleaned up some MASTER_SITES that don't resolve DNS.

And the last portscout check I manually did today was faster.

Many entries still need to be fixed/removed; here is the current list so 
everyone can help.

https://people.freebsd.org/~dbaio/portscout_host_does_not_resolve-2023-06-18.txt

Thanks for the detailed debugging. I will try to see how many I can axe.



Please: does the omission below fall under the umbrella of what's above?


From :


…  last checked 
2023-08-27 03:39 GMT, showed 1.40.1 with nothing new. I might flag 
this omission under bug 229622.



: 



MASTER_SITES= 
https://github.com/${PORTNAME}/${PORTNAME}/releases/download/v${DISTVERSION}/

Unmaintained FreeBSD ports which are out of date

2023-08-27 Thread portscout 
Dear port maintainers,

The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this port.
If any ports have already been updated, you can safely ignore the entry.

An e-mail will not be sent again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
cad/ifcopenshell| 0.6.0   | 
blenderbim-230827
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Reported by:portscout!

Re: Portscout is stuck

2023-08-27 Thread Moin Rahman 
No.

> On Aug 28, 2023, at 5:51 AM, Graham Perrin  wrote:
> 
> https://github.com/freebsd/freebsd-ports/commit/1de26c726690f5947b21d73fc44b06988134ad94#diff-451f05a07a02becc45f689065a8be28b5deffbf38388e66cd64ecb55d4d56817R5



signature.asc
Description: Message signed with OpenPGP