Compare commits

..
Author SHA1 Message Date
2d0544743a
topdir.mk: Remove --skip-excluded from install targets
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 5m0s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 5m31s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 5m6s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 5m21s
CI / Packaging test (push) Successful in 0s
Using --skip-excluded in pkg-install-*'s recipes breaks CI, and here's how:
During a CI run, a package is expected to be testable with only jw-pkg and
the package itself installed in the test environment. "testable" here means
that it's possible to install the necessary dependencies with make
pkg-install-* commands before building. That condition is inherently always
met by packages which have only jw-pkg as its only dependency. But it's not
true for packages with intermediate packages in their dependency tree. For
for those packages it's not advisable to pass --skip-excluded to the
dependency detection, because that will cause the resolver to try and find
the intermediate's project.conf to read its [build].excluded section.
Which fails because that intermediate is neither installed nor checked out.

So, until there's another mechansim in place which allows excluding
uninstalled packages (caller-supplied knowledge, reading remote
repositories, package-manager-like package metadata cache), drop
--skip-excluded from the pkg-install-* targets' recipes.

Signed-off-by: Jan Lindemann <jan@janware.com>
2026-10-18 18:09:53 +02:00
7ad7c55725
Release 1.0.0-277@suse-tumbleweed/x86_64
All checks were successful
CI / Packaging - Kali Linux (push) Successful in 4m50s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 5m13s
CI / Packaging test (push) Successful in 0s
2026-10-17 23:38:55 +00:00
25fea9ff18
Release 1.0.0-277@kali-rolling/amd64
All checks were successful
CI / Packaging - Kali Linux (push) Successful in 4m44s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 5m6s
CI / Packaging test (push) Successful in 0s
Signed-off-by: janware DevOps <devops@janware.com>
2026-10-17 23:12:45 +00:00
db77499915
Start version: 1.0.0-277
Signed-off-by: janware DevOps <devops@janware.com>
2026-10-17 23:11:32 +00:00
3 changed files with 5 additions and 5 deletions

4
HASH
View file

@ -1,4 +1,4 @@
suse-tumbleweed/x86_64: a3f1b3d12247230d92ca1b28b4746b7b
suse-tumbleweed/x86_64: f122b9cc30dbe98618bd781be63a5dfd
suse-tumbleweed/i586: 86ea923ca3861900dd03d4b1da44f8b6
debian-10/amd64: 47167eb2d7fe2d845a1b12e0702a6e9b
suse-42.3/x86_64: bd0e29fda82e38c89d2ed6f11797ce3a
@ -7,4 +7,4 @@ debian-8/amd64: b16e55fee0967a75aa67a4d859f0455d
ubuntu-18.04/amd64: 190b5c45953399fd93354db0621d6f5f
debian-10/armhf: 5d92c234d483deaf44c80cad168a8d5d
debian-2025.4/amd64: 977965179baa6fd24d0975a05d583eb6
kali-rolling/amd64: a3f1b3d12247230d92ca1b28b4746b7b
kali-rolling/amd64: f122b9cc30dbe98618bd781be63a5dfd

View file

@ -1,4 +1,4 @@
suse-tumbleweed/x86_64: 1.0.0-276
suse-tumbleweed/x86_64: 1.0.0-277
suse-tumbleweed/i586: 1.0.0-44
debian-10/amd64: 1.0.0-47
suse-42.3/x86_64: 1.0.0-48
@ -7,4 +7,4 @@ debian-8/amd64: 1.0.0-84
ubuntu-18.04/amd64: 1.0.0-99
debian-10/armhf: 1.0.0-102
debian-2025.4/amd64: 1.0.0-172
kali-rolling/amd64: 1.0.0-276
kali-rolling/amd64: 1.0.0-277

View file

@ -1 +1 @@
1.0.0-276-dev
1.0.0-277-dev