Control: tag -1 upstream Control: forwarded -1 https://github.com/crowdsecurity/crowdsec/issues/2125
Cyril Brulebois <cy...@debamax.com> (2023-02-15): > This was spotted during the final stages of 1.4.2-* preparations but it > seemed not important enough to delay an upload: > > E: golang-github-crowdsecurity-crowdsec-dev: symlink-target-in-build-tree > /build/crowdsec-1.4.2/_build/src/github.com/crowdsecurity/crowdsec/pkg/cwhub/hubdir/collections/crowdsecurity/test_collection.yaml > > [usr/share/gocode/src/github.com/crowdsecurity/crowdsec/pkg/cwhub/install/collections/test_collection.yaml] > E: golang-github-crowdsecurity-crowdsec-dev: symlink-target-in-build-tree > /build/crowdsec-1.4.2/_build/src/github.com/crowdsecurity/crowdsec/pkg/cwhub/hubdir/scenarios/crowdsecurity/barfoo_scenario.yaml > > [usr/share/gocode/src/github.com/crowdsecurity/crowdsec/pkg/cwhub/install/scenarios/barfoo_scenario.yaml] > > Those are test files, and they don't trigger a test suite failure > within an autopkgtest test bed, that's why I proceeded with an upload > without a fix. > > That being said, that means the build is not reproducible, and it'd be > far better to have that addressed once we have 1.4.2 into testing. It looks like the existence of those symlinks is just a symptom of a slightly bigger problem: some test files (and symlinks) created by the test suite are left over, and they end up being shipped in the -dev package. I've forwarded this upstream (link above), and I plan on removing those files manually via debian/rules; I'll wait a little to get an ACK from upstream before doing so though. I'll probably check that an autopkgtest run with the amended packaging still succeeds. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
signature.asc
Description: PGP signature
