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

Fix colon followed by number #26773

Merged
merged 2 commits into from
Dec 12, 2016
Merged

Fix colon followed by number #26773

merged 2 commits into from
Dec 12, 2016

Conversation

PVince81
Copy link
Contributor

@PVince81 PVince81 commented Dec 6, 2016

Description

Related Issue

Fixes #25479

Motivation and Context

How Has This Been Tested?

Just run the integration test

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Backports:

  • stable9.1
  • stable9

@owncloud/qa

@PVince81 PVince81 added this to the 9.2 milestone Dec 6, 2016
@mention-bot
Copy link

@PVince81, thanks for your PR! By analyzing the history of the files in this pull request, we identified @SergioBertolinSG, @DeepDiver1975 and @davitol to be potential reviewers.

@SergioBertolinSG
Copy link
Contributor

@PVince81 will you upgrade sabre/uri on this PR ?

This one is already merged sabre-io/uri#13

Tests are ok 👍

@PVince81
Copy link
Contributor Author

PVince81 commented Dec 7, 2016

Yes, I'll upgrade sabre-uri in this PR.

@PVince81
Copy link
Contributor Author

PVince81 commented Dec 7, 2016

Added commit with the upgrade, let's see what CI says

@PVince81
Copy link
Contributor Author

@DeepDiver1975 tests fail because of expected VObject version. Two possible solutions:

  1. We don't update vobject in this PR
    or
  2. Adjust test to expect the new version

Since this is on master I think it's fine to update vobject for now, so I'll adjust the tests

@PVince81
Copy link
Contributor Author

Oh well... while rebasing I had to do a composer update sabre/uri anyway which seems to have only updated sabre/uri, so we'll go with that.

@PVince81
Copy link
Contributor Author

All tests passed now, merge ? @SergioBertolinSG @DeepDiver1975

@SergioBertolinSG
Copy link
Contributor

👍

@PVince81 PVince81 merged commit 6bfe5bc into master Dec 12, 2016
@PVince81 PVince81 deleted the fix-colon-issue branch December 12, 2016 11:25
@PVince81
Copy link
Contributor Author

To backport:

  • stable9.1
    • backport tests
    • backport lib update to 3rdparty repo
    • adjust 3rdparty commit
  • stable9:
    • backport tests
    • backport lib update to 3rdparty repo
    • adjust 3rdparty commit

@PVince81
Copy link
Contributor Author

@SergioBertolinSG can you backport the tests ?
I'll take care of the 3rdparty repo if we see them failing.

@SergioBertolinSG
Copy link
Contributor

Sure.

@SergioBertolinSG
Copy link
Contributor

SergioBertolinSG commented Dec 12, 2016

@lock
Copy link

lock bot commented Aug 4, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Colon in folder name followed by a number creates fatal error
3 participants