py-pytest missing?

H

hannsmattes

Hi,

for some days I get "debendency incomplete" errors for a ton of packages. An example:

Code: 
postgresql13-client-13.21: "/usr/ports/devel/py-pytest-runner" non-existent -- dependency list incomplete
postgresql13-client-13.21: "/usr/ports/devel/py-pytest4" non-existent -- dependency list incomplete

Any help appreciated

Regards Hanns
Forgot to mention: Running 13-p5
 
These missing packages are both expired (deleted).

FreshPorts -- devel/py-pytest4: Simple powerful testing with Python (legacy version 4)

The pytest testing tool makes it easy to write small tests, yet scales to support complex functional testing. Features: * Detailed info on failing assert statements * Auto-discovery of test modules and functions * Modular fixtures to manage small or parametrized long-lived test resources...
www.freshports.org www.freshports.org

ports - FreeBSD ports tree

cgit.freebsd.org cgit.freebsd.org

FreshPorts -- devel/py-pytest-runner: Test support for pytest runner in setup.py

Setup scripts can use pytest-runner to add setup.py test support for pytest runner. Notice: pytest-runner depends on deprecated features of setuptools and relies on features that break security mechanisms in pip. It is recommended that you: - Remove 'pytest-runner' from your setup_requires...
www.freshports.org www.freshports.org

ports - FreeBSD ports tree

cgit.freebsd.org cgit.freebsd.org

hannsmattes said:
for some days I get "debendency incomplete" errors for a ton of packages.
Click to expand...
Where do you get this output from?

I could be able to build postgresql13-client-13.21 successfully with Poudriere.
 
Thank for Your reply.

I get tons of this errors running poudriere options. They're ranging fom php-modules to mariadb and postgresql.

Regards Hanns
 
hannsmattes said:
Thank for Your reply.

I get tons of this errors running poudriere options. They're ranging fom php-modules to mariadb and postgresql.

Regards Hanns
Click to expand...
I doubt something is wrong in your side. Can you share all the error logs together with the commands they are caused by?
 
hannsmattes said:
I get tons of this errors running poudriere options. They're ranging fom php-modules to mariadb and postgresql.
Click to expand...
You might want to check out a fresh copy of the ports tree. It sounds like something got messed up in Mk/Uses/.
 
nxjoseph said:
I doubt something is wrong in your side. Can you share all the error logs together with the commands they are caused by?
Click to expand...
Hi,

I'm sure, it's on my side. Im running:

poudriere options -j amd64-13-5 -p devel -f /usr/local/etc/poudriere.d/pkglist
Click to expand...

As far as I see the Outpu ist not helpful, it's just a Bunch of errors as reported.

I'll follow the advice of SirDice, as soon, as I know how to do.

Thanks for Your help

Regards Hanns
 
Hi,

so far thank You for Your help.

What I did to no avail:

Deleted all poudriere jails and created:

poudriere jail -c -j amd64-13-5 -v 13.5-RELEASE
Click to expand...

Deleted existing ports collection, then running
portsnap fetch extract
Click to expand...

Installing ports tree with
poudriere ports -c p devel -F -M /usr/ports -f none
Click to expand...

Don't know, what I've messed up. Here's my make.conf
DEFAULT_VERSIONS+=mysql=10.11m
OPTIONS_SET+=LDAP DOCS
OPTIONS_UNSET+=GSSAPI
LICENSES_ACCEPTED+=DCC
WITH_CCACHE_BUILD=yes
Click to expand...

Regards Hanns
 
Hi,
/usr/local/etc/poudriere.d/make.conf

deleting and recreating the ports tree didn't solve the problem.

By the way: Is there a recommended replacement portsnap? GIT?

Regards Hanns
 
I think that you don't need WITH_CCACHE_BUILD=yes in make.conf because if you set CCACHE_DIR in poudriere.conf, it's enough.

I'd recommend git over portsnap.
 
SirDice said:
Can you try a build without CCACHE?
Click to expand...
Is it CCACHE used by poudriere options? Because these warnings appear only when poudriere options are invoked:
[default]# poudriere options -j 14x64 security/binwalk
[00:00:00] Ports supports: FLAVORS SUBPACKAGES SELECTED_OPTIONS
[00:00:00] Working on options directory: /usr/local/etc/poudriere.d/14x64-options
[00:00:00] Using ports from: /pkg/ports/default
[00:00:00] Appending to make.conf: /usr/local/etc/poudriere.d/14x64-make.conf
===> Setting user-specified options for binwalk-2.3.3_1 and dependencies
binwalk-2.3.3_1: "/pkg/ports/default/devel/py-pytest-runner" non-existent -- dependency list incomplete
binwalk-2.3.3_1: "/pkg/ports/default/devel/py-pytest4" non-existent -- dependency list incomplete
Click to expand...

I'm just wondering if USES=python does automatically implies USES=pytest - unfortunatelly older (deleted) version. That's why there are so many warnings

I've just deleted and recreated poudriere default ports tree - these warnings did not disappear :-(((

I've tried invoke sh -x `which poudriere` options... to see which dependency is generating these warnings - unfortunatelly no success

Any ideas?
 
Christo00 said:
Is it CCACHE used by poudriere options? Because these warnings appear only when poudriere options are invoked:


I'm just wondering if USES=python does automatically implies USES=pytest - unfortunatelly older (deleted) version. That's why there are so many warnings

I've just deleted and recreated poudriere default ports tree - these warnings did not disappear :-(((

I've tried invoke sh -x `which poudriere` options... to see which dependency is generating these warnings - unfortunatelly no success

Any ideas?
Click to expand...
No, poudriere options shouldn't use ccache.

Why my security/binwalk don't give these errors and yours are looking for deleted ports (dependencies)? is your ports trees are somewhat outdated? Also binwalk doesn't have any options to configure, it seems.

Code: 
freebsd:/usr/home/yusuf
# cipopt security/binwalk
[00:00:04] Ports supports: FLAVORS SUBPACKAGES SELECTED_OPTIONS
[00:00:04] Working on options directory: /usr/local/etc/poudriere.d/143amd64-default-options
[00:00:04] Using ports from: /usr/ports
[00:00:04] Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
[00:00:06] Re-run 'poudriere options' with the -c flag to modify the options.
===> Setting user-specified options for binwalk-2.3.3_1 and dependencies
freebsd:/usr/home/yusuf
# alias cipopt
cpuset -l 0-2 idprio 31 poudriere options -j 143amd64 -p default
 
hannsmattes said:
"/usr/ports/devel/py-pytest4" non-existent -- dependency list incomplete
Click to expand...
I see that in
Code: 
/usr/ports/sysutils/budgie-control-center %  make missing
budgie-control-center-1.3.0_5: "/usr/ports/devel/py-pytest4" non-existent -- dependency list incomplete

For the cause see Bug 287764 devel/py-pytest{4,-runner}: removal causes incomplete depends warnings

Apparently pytest4 from ports/Mk/Uses/python.mk does trigger the issue:
Code: 
pytest4        - Run tests with pytest 4.x (devel/py-pytest4)

See PR comments 3 and 4 in particular.
 
Well, what's unfortunate is that there's no alternative entitled in MOVED.
This usually mean that no more consumers are found in up-to-date main (latest) branch of ports tree, unless author/maintainer and/or committer (and reviewer when applicable) are overlooking something.

A good alternative for deprecated ports-mgmt/portsnap would be (I myself am not tried, though) net/gitup, while the alternative of svnlite (in base) was devel/git.

net/gitup can simply updating ports tree, without maintaining repo data in .git directory, while devel/git can manage changes, creating and maintaining local branches using /git directory.
So both (actually) cannot coexist for the same repo , same work directory.

Anyway, server-side functionalities of portsnap would be stopped in the future and maybe already has lower maintainance priorities than git repo.
(IIRC, the initial plan to stop portsnap was much more aggressive.)
 
You must log in or register to reply here.
Back
Top