On 9/28/2022 11:59 AM, Dan Mick wrote:
but not for deb releases:
http://download.ceph.com/debian-17.2.3/pool/main/c/ceph/
https://4.chacra.ceph.com/r/ceph/wip-yuri4-testing-2022-09-27-1405/cee7690a0
a431bd223254670505200901fccbd16/ubuntu/jammy/flavors/default/pool/main/c/cep
h/
so something further apparently needs to be done to the deb repo build.
The hope was that, if anything about the build process ever evolved
(like, say, making the cephadm file a zipfile instead of a Python script
As noted above it "just worked" for the RPM version. I'm not sure how
to start
debugging it... if you would be so kind to help us (me) start
debugging it I'd
really appreciate it.
Well, it's the Jenkins build that creates and uploads the packages to
shaman, and then shaman builds the repos. I thought I had once verified
that a non-deb file could sit alongside the .debs, just like it does for
the rpms, but maybe something changed about how shaman builds/publishes
the repos since I determined that, or maybe I was just wrong. We'd need
to examine the flow and see where it drops out.
FWIW, the binary is posted to chacra, so it must be chacra/shaman's repo
build that drops it (not particularly surprisingly):
curl -L
https://1.chacra.ceph.com/binaries/ceph/wip-yuri-testing-2022-09-28-0934-pacific/47fd39ae960cea9c341d8aee03d98d8f6f4cc834/ubuntu/focal/x86_64/flavors/default/cephadm
will get you a recent build's version
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
