apt-package-safelist
apt-package-safelist copied to clipboard
travis-ci
APT whitelist request for libmediainfo0
Hi @BanzaiMan how long does it take for the whitelist to be propagated to the production build environment? https://travis-ci.org/sbraz/pymediainfo/jobs/128236962
@sbraz The PR added libmediainfo0v5, which was found by examining the source package.
The current workflow may be deficient in this situation. I do not have a good answer for it.
My bad, I didn't realise this was the full package name. It still fails with the right name though: https://travis-ci.org/sbraz/pymediainfo/jobs/128239921
Right. There are a few cases like this, when the originally requested package's source package does not contain the original package name. This is what I meant in the last commit.
I think I can manually allow this, but I intend to do it next week. Sorry for the delay.
@BanzaiMan No hurry, thanks :) Can you re-open the issue so you won't forget?
@BanzaiMan Hi again, sorry to bother you once again, do you think you'll have some time to look at it in the near future?
@sbraz I'm afraid not. If you need a particular package that isn't addressed by the whitelist, your best bet is to use sudo: required. You can either call sudo apt-get install … directly, or continue to use the addon (https://docs.travis-ci.com/user/installing-dependencies#Installing-Packages-with-the-APT-Addon). (That is to say, if you use the addon on a sudo-enabled infrastructure, the addon will bypass the whitelist to install any package.)
Should I keep the issue opened in case you add it manually or should I close it now?