What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running cf curl /v2/info && cf version?
cf.exe version 6.53.0+8e2b70a4a.2020-10-01
What version of the buildpack you are using?
Apt Buildpack version 0.2.2
If you were attempting to accomplish a task, what was it you were attempting to do?
Attempting to include deb files that are not in a repository, I'd like to install the deb files from a directory located in the app upload ($HOME) path.
The application that I push contains a directory deb_files containing the deb packages.
What did you expect to happen?
The apt buildpack would recognize / accept a path instead of a URL or repo package name
What was the actual behavior?
Packaging files to upload...
Uploading files...
48.88 KiB / 48.88 KiB [=========================================================================================================================================================================================================] 100.00% 1s
Waiting for API to complete processing files...
Staging app and tracing logs...
Downloading python_buildpack...
Downloading apt-buildpack...
Downloaded python_buildpack
Downloaded apt-buildpack (2.5M)
...
Downloading app package...
Downloading build artifacts cache...
Downloaded app package (4.4M)
Downloaded build artifacts cache (105.4M)
-----> Apt Buildpack version 0.2.2
-----> Updating apt cache
-----> Downloading apt packages
**ERROR** Error running supply: Get $HOME/deb_files/x.deb: unsupported protocol scheme ""
Failed to run all supply scripts: exit status 14
Perhaps this is in fact already possible, and I just don't understand the correct protocol / method of defining the needed packages in the apt.yml, if thats the case, maybe a simple documentation update would help.
ola-Dell
commented
2 years ago
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version? cf.exe version 6.53.0+8e2b70a4a.2020-10-01What version of the buildpack you are using? Apt Buildpack version 0.2.2
If you were attempting to accomplish a task, what was it you were attempting to do? Attempting to include deb files that are not in a repository, I'd like to install the deb files from a directory located in the app upload ($HOME) path.
My apt.yml looks like this:
The application that I push contains a directory
deb_filescontaining the deb packages.What did you expect to happen? The apt buildpack would recognize / accept a path instead of a URL or repo package name
What was the actual behavior?
Perhaps this is in fact already possible, and I just don't understand the correct protocol / method of defining the needed packages in the apt.yml, if thats the case, maybe a simple documentation update would help.
Please confirm where necessary: