Private archive flag needs to be passed to build slaves

Bug #219330 reported by Muharem Hrnjadovic
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Muharem Hrnjadovic
launchpad-buildd
Fix Released
Undecided
Muharem Hrnjadovic

Bug Description

For builds in private archives the build slaves need to sanitize the URLs in the buildlog file (see also https://bugs.edge.launchpad.net/launchpad-buildd/+bug/214485) because these URLs may have authentication credentials embedded in them. Since this sanitization is only to occur for private archives the build master has to provide the archive.private flag when starting the build.

Changed in launchpad-buildd:
assignee: nobody → al-maisan
status: New → In Progress
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

RF 6122

Changed in soyuz:
assignee: nobody → al-maisan
milestone: none → 1.2.4
status: New → In Progress
status: In Progress → Fix Committed
Changed in soyuz:
status: Fix Committed → Fix Released
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

RF 6489

Changed in launchpad-buildd:
status: In Progress → Fix Released
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

Please ignore my previous comment (#2) above; the launchpad-buildd package version is:
launchpad-buildd (46)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.