Skip to content

Packages without version number no longer map to snapshot #39823

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kimgr opened this issue Jan 26, 2019 · 4 comments
Closed

Packages without version number no longer map to snapshot #39823

kimgr opened this issue Jan 26, 2019 · 4 comments
Assignees
Labels
bugzilla Issues migrated from bugzilla packaging platform:linux

Comments

@kimgr
Copy link
Contributor

kimgr commented Jan 26, 2019

Bugzilla Link 40477
Version unspecified
OS Linux
CC @wbbradley

Extended Description

We use Travis for CI builds, and rely on their llvm-toolchain-trusty source.

I'm not entirely sure how that's wired, but ever since the LLVM/Clang 8 branch was made and trunk switched to 9, installing e.g. clang no longer works:

https://travis-ci.org/include-what-you-use/include-what-you-use/builds/483638279?utm_source=github_status&utm_medium=notification

So it looks like something needs to be done to make the default packages point back to the -snapshot builds for trunk/master.

Thanks for any ideas!

@kimgr
Copy link
Contributor Author

kimgr commented Mar 9, 2020

This looks like it's working for the most important packages now (llvm-dev, libclang-dev and clang).

Some ancillary packages (llvm-11-tools, *-11-examples, etc) still don't have any snapshot packages to track them. Here's a dump of all 'Package:' lines in https://apt.llvm.org/xenial/dists/llvm-toolchain-xenial/main/binary-amd64/Packages:

--
48 matches for "Package: " in buffer: Packages
1:Package: clang
27:Package: clang-11
53:Package: clang-11-doc
78:Package: clang-11-examples
102:Package: clang-format
130:Package: clang-format-11
157:Package: clang-tidy
183:Package: clang-tidy-11
204:Package: clang-tools-11
229:Package: clangd
257:Package: clangd-11
282:Package: libc++-11-dev
315:Package: libc++1-11
349:Package: libc++abi-11-dev
378:Package: libc++abi1-11
407:Package: libclang-11-dev
433:Package: libclang-common-11-dev
459:Package: libclang-cpp11
490:Package: libclang-cpp11-dev
526:Package: libclang-dev
551:Package: libclang1
582:Package: libclang1-11
613:Package: libfuzzer-11-dev
644:Package: liblld-11
666:Package: liblld-11-dev
688:Package: liblldb-11
710:Package: liblldb-11-dev
732:Package: libllvm-11-ocaml-dev
766:Package: libllvm-ocaml-dev
787:Package: libllvm11
810:Package: libomp-11-dev
835:Package: libomp-11-doc
859:Package: libomp5-11
884:Package: lld
903:Package: lld-11
923:Package: lldb
944:Package: lldb-11
964:Package: llvm
985:Package: llvm-11
1025:Package: llvm-11-dev
1056:Package: llvm-11-doc
1086:Package: llvm-11-examples
1117:Package: llvm-11-runtime
1148:Package: llvm-11-tools
1178:Package: llvm-dev
1199:Package: llvm-runtime
1220:Package: python3-clang-11
1248:Package: python3-lldb-11

Not sure if there's any intentional discrimination, or if some of them just don't have snapshot versions?

If the former, feel free to close this as fixed as of llvm-11. Thanks!

@kimgr
Copy link
Contributor Author

kimgr commented Mar 9, 2020

Ah, and to clarify, we no longer use Travis' llvm-toolchain-trusty, but use the apt.llvm.org packaging directly.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
@firewave
Copy link

firewave commented May 7, 2025

@kimgr Is this issue still present?

@kimgr
Copy link
Contributor Author

kimgr commented May 7, 2025

@firewave I don't think so, let's close this! Thanks for keeping an eye out.

@kimgr kimgr closed this as completed May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla packaging platform:linux
Projects
None yet
Development

No branches or pull requests

3 participants