Tuesday, February 23, 2021

[389-devel] Re: failed to build rpms

Should we update the contributing/build docs to reflect these steps?

> On 24 Feb 2021, at 07:10, Mark Reynolds <mreynolds@redhat.com> wrote:
>
> You have to skip the npm audit check "SKIP_AUDIT_CI=1" for now, and the rust stuff is a pain and it is hardcoded to be enabled. You always have to update and download the latest Rust dependencies:
>
> SKIP_AUDIT_CI=1 make -f rpm.mk update-cargo-dependencies download-cargo-dependencies rpms
>
> HTH,
>
> Mark
>
> On 2/23/21 1:40 PM, Ludwig Krispenz wrote:
>> Hi,
>>
>> since a long time I was trying to build rpms and failed, here are the issues I run into:
>>
>> 1] problem with npm/audit
>>
>> I followed the suggestions here: https://www.port389.org/docs/389ds/contributing.html (pushd/npm fix/popd), but this didn't help, only commenting out audit-ci in src/cockpit/389-console/node_modules.mk got me over this
>>
>> 2] rust
>>
>> 2.1]
>>
>> rpm build failed with:
>>
>> error: failed to get `concread` as a dependency of package `librslapd v0.1.0 (/home/elkris/DEV/gh/two/389-ds-base/rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/src/librslapd)`
>>
>> Caused by:
>> failed to load source for dependency `concread`
>>
>> Caused by:
>> Unable to update registry `https://github.com/rust-lang/crates.io-index`
>>
>> Caused by:
>> failed to update replaced source registry `https://github.com/rust-lang/crates.io-index`
>>
>> Caused by:
>> failed to read root of directory source: /home/elkris/DEV/gh/two/389-ds-base/rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/vendor
>>
>> Caused by:
>> No such file or directory (os error 2)
>> make[1]: *** [Makefile:12715: .../rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/rs/rslapd/release/librslapd.a] Error 101
>>
>>
>> ,
>>
>> It was right that there wasno rs/rslapd/release/librslapd.a file, not even the directory rs existed. After configuring --enable-rust the directory was created and populated.
>>
>> Q1: why does it try to pack rust stuff if it is not enabled ?
>>
>> 2.2] Now the directory was there, but I still did get the same error. A closer look showed that it was looking for .../rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/rs/rslapd/release/librslapd.a ,but what existed was .../rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/rs/rslapd/debug/librslapd.a. Note "debug" -- "release". configure was run with --enable-debug
>>
>> Q2: Is there somewhere a hardcoded/default assumpion of "release" ? in the cargo spec?
>>
>> Thanks for any suggestions
>>
>>
>> Regards,
>>
>> Ludwig
>> _______________________________________________
>> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
>> To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org
>> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
>> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> --
>
> 389 Directory Server Development Team
> _______________________________________________
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure


Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
_______________________________________________
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

No comments:

Post a Comment