Re: graphics/gmic missing binary

2022-07-16 Thread Yuri

Hi Andrea,


You have asked in a wrong place.
For port issues like this you should either create Bugzilla issues 
(https://bugs.freebsd.org/bugzilla/), or e-mail maintainers directly.


I'll take a look at this problem.


Yuri



On 7/11/22 08:52, Andrea Venturoli wrote:


Hello.

I was using gmic last month from command line.
After the switch to 2022Q3 branch I see the port does not provide a 
binary anymore (although, curiously, the man page is still there).


What's the reason?
Can I get it back somehow?
Has it been moved to another port?

 bye & Thanks
av.






Strange failure message in poudriere: pkg-static: pkg_checksum_hash_sha256_file(read failed): Is a directory

2022-07-16 Thread Yuri

Hi,


The port science/yoda fails in poudriere with this message:

===
===>  Building package for yoda-1.9.4
pkg-static: pkg_checksum_hash_sha256_file(read failed): Is a directory
*** Error code 1


How can this be cured?


Log: 
http://beefy18.nyi.freebsd.org/data/main-amd64-default/p2f8a7d1d15ce_s2b766d5e5a/logs/yoda-1.9.4.log



Thanks,

Yuri





Re: Strange failure message in poudriere: pkg-static: pkg_checksum_hash_sha256_file(read failed): Is a directory

2022-07-16 Thread Christoph Moench-Tegeder
## Yuri (y...@freebsd.org):

> The port science/yoda fails in poudriere with this message:
> 
> ===
> ===>  Building package for yoda-1.9.4
> pkg-static: pkg_checksum_hash_sha256_file(read failed): Is a directory
> *** Error code 1

I believe I remember that means that a file listed in pkg-plist is
actually a directory. poudriere testport helps (why wasn't this
detected in the first place?)

Regards,
Christoph

-- 
Spare Space



Re: graphics/gmic missing binary

2022-07-16 Thread Mark Millard


Yuri  wrote on
Date: Sat, 16 Jul 2022 19:37:01 UTC :
 
> Hi Andrea,
> 
> 
> You have asked in a wrong place.

https://docs.freebsd.org/en/articles/problem-reports/ says:

QUOTE (2nd bullet under "3. Preparations"):
. . . If the problem has not been discussed on the lists, you might
try posting a message about it and waiting a few days to see if
someone can spot something that has been overlooked.
END QUOTE

It looks to me like the list submittal fits the above but could
end up still leading to a later need for a bugzilla submittal.
The same page has more material about doing such.

> For port issues like this you should either create Bugzilla issues 
> (https://bugs.freebsd.org/bugzilla/), or e-mail maintainers directly.
> 
> I'll take a look at this problem.
> 
> 
> Yuri
> 
> 
> 
> On 7/11/22 08:52, Andrea Venturoli wrote:
> >
> > Hello.
> >
> > I was using gmic last month from command line.
> > After the switch to 2022Q3 branch I see the port does not provide a 
> > binary anymore (although, curiously, the man page is still there).
> >
> > What's the reason?
> > Can I get it back somehow?
> > Has it been moved to another port?
> >
> >  bye & Thanks
> > av.

===
Mark Millard
marklmi at yahoo.com




Re: problem with "make index"

2022-07-16 Thread Charlie Li

Stefan Esser wrote:
The reason that I have committed the port at this time was that "make 
index"

is broken with LLVM_DEFAULT set to 14. I have considered this a fix of the
port system, but forgot to mention that detail in the commit log.

Not when the other components of the WASI toolchain are also required to 
actually function. The default LLVM_DEFAULT is still not 14, so those 
who change the settings on their setups have to bear at least some 
responsibility for any fallout (despite best efforts on maintainers' to 
qualify other option/setting combinations).> The problem with a missing 
wasi-compile-rt14 port is that it breaks "make

index" even for users that are not interested in WASI at all ...

Maybe, a port should have been committed marked

 IGNORE= Not ready, see https://reviews.freebsd.org/D35288

in order to not break "make index" with the non-default LLVM_DEFAULT?

This has now been remedied in commit 
6b2cf7d799d86f3e577d45a11b1010305e79351f ostensibly to hinder those who 
don't know what they are doing from this, unless interested in actually 
figuring out how to make it all work (like myself). So unless there 
existed use cases or consumers outside or not appropriate for the ports 
tree, not committing this port was the only correct choice.
There is no mention of related revisions in 
https://reviews.freebsd.org/D35288,
maybe you could connect this review to others that are required for WASI 
with

LLVM 14?

I see that D35286 to D35389 cover this whole topic, and that there still 
are

unresolved run-time issues that prevent them from actually being used.


Those are the related reviews, and all must be congruent.

BTW: I see that wasi-libc and wasi-libc++ do not contain the LLVM version
in their ${PKGBASE} values. I'd have expected that only wasi-libc built 
with
LLVM 14 could be used in wasi-compile-rt14 and thus that it would be 
good to

have some mention of LLVM_DEFAULT in the package base name?

wasi-libc doesn't do releases, just commits/snapshots. Any quick look at 
the source reveals that they effectively support only one LLVM version 
at a time, and since earlier this year that has been LLVM 14. The 
current port has not been updated so as to ensure LLVM 13 compatibility.


wasi-libcxx on the other hand could switch to version suffixes, however, 
since it uses the same LLVM sources.
But that doesn't address an even bigger issue that's still being 
figured out: how to make this whole situation, LTO or not, less 
fragile to deal with.


I see - do you want me to revert this commit?


Please do.

--
Charlie Li
…nope, still don't have an exit line.


OpenPGP_signature
Description: OpenPGP digital signature


RE: Strange failure message in poudriere: pkg-static: pkg_checksum_hash_sha256_file(read failed): Is a directory

2022-07-16 Thread Mark Millard
The fix was checked in to main a few days ago. The text of that
shows what the problem was:

author  Po-Chuan Hsieh 2022-07-13 00:19:32 +
committer   Po-Chuan Hsieh 2022-07-13 00:19:32 
+
commit  e9638f8da96894984567102be601f60ee89fe50f (patch)
tree3af6b4ffeff331103ec3fb6e7fda58b461de498d /science/yoda
parent  94c675d58d181cdc28afbc2b5ad1924521c053f5 (diff)
downloadports-e9638f8da96894984567102be601f60ee89fe50f.tar.gz
ports-e9638f8da96894984567102be601f60ee89fe50f.zip
science/yoda: Fix build with setuptools 58.0.0+
- Bump PORTREVISION for package change

With hat:   python

Diffstat (limited to 'science/yoda')
-rw-r--r--  science/yoda/Makefile   1   
-rw-r--r--  science/yoda/pkg-plist  5   
2 files changed, 5 insertions, 1 deletions
diff --git a/science/yoda/Makefile b/science/yoda/Makefile
index 8da3306bd55f..87d8cdfe8fd5 100644
--- a/science/yoda/Makefile
+++ b/science/yoda/Makefile
@@ -1,5 +1,6 @@
 PORTNAME=  yoda
 DISTVERSION=   1.9.4
+PORTREVISION=  1
 CATEGORIES=science
 MASTER_SITES=  https://yoda.hepforge.org/downloads/
 DISTNAME=  ${PORTNAME:tu}-${DISTVERSION}
diff --git a/science/yoda/pkg-plist b/science/yoda/pkg-plist
index cbca54e826d6..c6cca163a887 100644
--- a/science/yoda/pkg-plist
+++ b/science/yoda/pkg-plist
@@ -78,7 +78,10 @@ include/YODA/WriterMethods.icc
 include/YODA/WriterYODA.h
 include/YODA/YODA.h
 lib/libYODA.so
-%%PYTHONPYTHON_SITELIBDIR%%/yoda-%%VERSION%%-py%%PYTHON_VER%%.egg-info
+%%PYTHONPYTHON_SITELIBDIR%%/yoda-%%VERSION%%-py%%PYTHON_VER%%.egg-info/PKG-INFO
+%%PYTHONPYTHON_SITELIBDIR%%/yoda-%%VERSION%%-py%%PYTHON_VER%%.egg-info/SOURCES.txt
+%%PYTHONPYTHON_SITELIBDIR%%/yoda-%%VERSION%%-py%%PYTHON_VER%%.egg-info/dependency_links.txt
+%%PYTHONPYTHON_SITELIBDIR%%/yoda-%%VERSION%%-py%%PYTHON_VER%%.egg-info/top_level.txt
 %%PYTHONPYTHON_SITELIBDIR%%/yoda/__init__.py
 
%%PYTHONPYTHON_SITELIBDIR%%/yoda/__pycache__/__init__%%PYTHON_EXT_SUFFIX%%.pyc
 
%%PYTHONPYTHON_SITELIBDIR%%/yoda/__pycache__/plotting%%PYTHON_EXT_SUFFIX%%.pyc


===
Mark Millard
marklmi at yahoo.com