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

Files transferred using Package Transfer retains GUID applied during staging #3060

Closed
zentron opened this issue Jan 10, 2017 · 4 comments
Closed
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@zentron
Copy link

zentron commented Jan 10, 2017

When the package transfer step runs, it simply copies the file from the staging directory uploaded during the package acquisition phase.

A result of this is that the guid that is applied as a prefix is retained on the file name. This guid is added to the package name during acquisition to ensure that there are no clashes with existing files that have been previously staged.

Whilst most software sees file extensions as irrelevant, this can be a problem for some Windows based programs which expect the original extension.

@zentron zentron added area/execution kind/bug This issue represents a verified problem we are committed to solving labels Jan 10, 2017
@zentron zentron self-assigned this Jan 10, 2017
@zentron
Copy link
Author

zentron commented Jan 10, 2017

@zentron zentron closed this as completed Jan 10, 2017
@octoreleasebot octoreleasebot added this to the 3.7.15 milestone Jan 10, 2017
@octoreleasebot
Copy link

octoreleasebot commented Jan 10, 2017

Release Note: Packages transferred using Package Transfer step retains original package name

@zentron
Copy link
Author

zentron commented Jan 11, 2017

If a package of the format <PackageId>.<PackageVersion>.<FileExtension> already exists at the transfer location it will be attempted to be overwritten

@lock
Copy link

lock bot commented Nov 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

2 participants