Closed palash-gandhi closed 1 year ago
We can do it this way, or we can preserve the misc-debs
package, and just remove the tar
package from it.. i.e. so it'd be empty.. the idea being, the "infrastructure" will be there if we need to do this in the future..
Do we have thoughts if it'd be useful to keep the package definition around, for potential future use? or remove it, and if needed later, it can be resurrected (like I did)?
We can do it this way, or we can preserve the
misc-debs
package, and just remove thetar
package from it.. i.e. so it'd be empty.. the idea being, the "infrastructure" will be there if we need to do this in the future..Do we have thoughts if it'd be useful to keep the package definition around, for potential future use? or remove it, and if needed later, it can be resurrected (like I did)?
I think it makes sense to leave the infra behind.
I think it makes sense to leave the infra behind.
Let's verify that actually works, since I never tested it, with git-ab-pre-push -b misc-debs
This change unpins the
tar
package from 6.0/stage. It was added as part of DLPX-85006 in 6.0/release due to a CVE. We leave the infrastructure behind for future possibilities. Not that branching for the new release has already completed, we are seeing some failures, unrelated to this change but that reminded me that we need to revert this on both these branches.ab-pre-push -b misc-debs: http://selfservice.jenkins.delphix.com/job/appliance-build-orchestrator-pre-push/4834/