Skip to content
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

When $PBUILDER_CONFIG is set we should use --override-config #175

Open
laeti-tia opened this issue Feb 23, 2017 · 2 comments
Open

When $PBUILDER_CONFIG is set we should use --override-config #175

laeti-tia opened this issue Feb 23, 2017 · 2 comments

Comments

@laeti-tia
Copy link
Contributor

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.

@mika
Copy link
Owner

mika commented Feb 23, 2017

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!

@laeti-tia
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants