You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When $PBUILDER_CONFIG is set we should use --override-config when calling cowbuilder update or at least when the pbuilder is adding new apt sources, otherwise those sources are not used.
The text was updated successfully, but these errors were encountered:
Could you please expand/be more verbose what problem you're actually running into? (The --override-config is quite poorly documented and I'd like to make sure I understand its consequences.) Thanks!
Sorry for the late answer... The problem I'm trying to solve with this is that I need to use a different apt repository when I build production level packages and nightly packages (so that the dependencies get solved with packages from the production repo or the nightly repo).
What I do, is that before calling build-and-provide-package I build a pbuilderrc file that contains a OTHERMIRROR variable pointing to the corresponding repository. But this works only if cowbuilder --update is called with --override-config.
Another way to solve that would be to be able to define different pbuilder chroot to be used by jenkins-debian-glue right from the start... Or use 2 different building host for production packages and nightly packages... But I'd like to avoid that.
When $PBUILDER_CONFIG is set we should use
--override-config
when callingcowbuilder update
or at least when the pbuilder is adding new apt sources, otherwise those sources are not used.The text was updated successfully, but these errors were encountered: