You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by "Tanvir786123 (via GitHub)" <gi...@apache.org> on 2023/09/14 16:19:15 UTC

[GitHub] [buildstream] Tanvir786123 opened a new issue, #1871: Buildbox release

Tanvir786123 opened a new issue, #1871:
URL: https://github.com/apache/buildstream/issues/1871

   ### Context
   
   When building the `freedesktop-sdk.bst:components/cryptsetup-base.bst`, we receive the following compile errors:
   ```
       touch stamp-po
       make[2]: Leaving directory '/buildstream-build/bst_build_dir/po'
       Making all in tests
       make[2]: Entering directory '/buildstream-build/bst_build_dir/tests'
       ../../tests/generate-symbols-list ../../lib/libcryptsetup.sym > ./test-symbols-list.h
       ../../tests/generate-symbols-list: line 9: /dev/fd/63: No such file or directory
       make[2]: *** [Makefile:1204: test-symbols-list.h] Error 1
       make[2]: Leaving directory '/buildstream-build/bst_build_dir/tests'
       make[1]: *** [Makefile:2685: all-recursive] Error 1
       make[1]: Leaving directory '/buildstream-build/bst_build_dir'
       make: *** [Makefile:1302: all] Error 2
       Command 'if [ -n "bst_build_dir" ]; then
         cd bst_build_dir
       fi
       make ' failed with exitcode 2
       [00:00:17] FAILURE freedesktop-sdk.bst:components/cryptsetup-base.bst: Running commands
       [--:--:--] START   [206a1e6e] freedesktop-sdk.bst:components/cryptsetup-base.bst: Caching artifact
       [00:00:00] FAILURE [206a1e6e] freedesktop-sdk.bst:components/cryptsetup-base.bst: Command failed
   ```
   
   This is **virtually identical** to [this issue](https://gitlab.com/cryptsetup/cryptsetup/-/issues/829).
   
   ### Description
   
   I have been told a new release of Buildbox is needed.
   
   ### Acceptance Criteria
   
   We provide evidence that `freedesktop-sdk.bst:components/cryptsetup-base.bst` compiles correctly
   
   CC:
   - @jjardon
   - @abderrahim
   - @nanonyme


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [buildstream] nanonyme commented on issue #1871: Buildbox release

Posted by "nanonyme (via GitHub)" <gi...@apache.org>.
nanonyme commented on issue #1871:
URL: https://github.com/apache/buildstream/issues/1871#issuecomment-1720131044

   The problem here is BuildStream package bundles buildbox rather than latter having freedom of being released when needed. There has now been overlong period since last refresh of buildbox components in BuildStream wheels and it's resulting in breakage 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [buildstream] gtristan commented on issue #1871: New Buildstream release

Posted by "gtristan (via GitHub)" <gi...@apache.org>.
gtristan commented on issue #1871:
URL: https://github.com/apache/buildstream/issues/1871#issuecomment-1730843382

   We already have an issue for de-prioritizing the static buildbox binaries included in the complimentary wheels we generate (along side our official tarball releases) for added convenience.
   
   I'll close this given that we have today release 2.1.0.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [buildstream] gtristan closed issue #1871: New Buildstream release

Posted by "gtristan (via GitHub)" <gi...@apache.org>.
gtristan closed issue #1871: New Buildstream release
URL: https://github.com/apache/buildstream/issues/1871


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [buildstream] Tanvir786123 commented on issue #1871: New Buildstream release

Posted by "Tanvir786123 (via GitHub)" <gi...@apache.org>.
Tanvir786123 commented on issue #1871:
URL: https://github.com/apache/buildstream/issues/1871#issuecomment-1722195610

   I have updated the title and description to be more accurate @jjardon 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [buildstream] Tanvir786123 commented on issue #1871: New Buildstream release

Posted by "Tanvir786123 (via GitHub)" <gi...@apache.org>.
Tanvir786123 commented on issue #1871:
URL: https://github.com/apache/buildstream/issues/1871#issuecomment-1732415729

   > We already have an issue for de-prioritizing the static buildbox binaries included in the complimentary wheels we generate (along side our official tarball releases) for added convenience.
   > 
   > I'll close this given that we have today released 2.1.0.
   
   Can indeed confirm that the new release has enabled me to compile GNOME.
   
   Thank you :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org