Skip to content

Update repositories.txt for new URL of CodeDebugScope Library #5019

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

Merged
merged 1 commit into from
Sep 12, 2024

Conversation

boseji
Copy link
Contributor

@boseji boseji commented Aug 23, 2024

Hello,

On behalf of the Author - Albert van Dalen http://www.avdweb.nl

Requesting a URL Update the Library CodeDebugScope

New Repository Location:

https://github.com/avdwebLibraries/avdweb_CodeDebugScope

Kindly help us out.

Copy link
Contributor

Hi @boseji.
Your pull request has been detected as something other than a Library Manager submission.
A maintainer will need to review it before it can be merged.

If you intended to submit a library, please check the instructions and update your pull request if necessary:
https://github.com/arduino/library-registry/blob/main/README.md#instructions

@github-actions github-actions bot added the topic: modification Change existing list entry label Aug 23, 2024
@github-actions github-actions bot requested a review from per1234 August 23, 2024 15:13
@boseji
Copy link
Contributor Author

boseji commented Aug 23, 2024

Please guide me if I made any mistake in this pull request.

This is first time I am requesting for an Update the repository name.

The reason being that the Author has decide to shift all their libraries to a new organization.

This is to enable more engagement with their community and open-source development.

Kindly help us on this.

Copy link
Contributor

@per1234 per1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @boseji. I am confirming your request.

Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will merge this pull request when it is done. You will get a notification from GitHub at that time.

After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager

@per1234 per1234 added topic: URL change Change library repository URL status: pending backend Depends on backend maintenance operations and removed topic: modification Change existing list entry labels Aug 23, 2024
@boseji
Copy link
Contributor Author

boseji commented Aug 23, 2024

Thank you for the Help.

I have prepared the special Library URL as demonstrated in the Help document.

Old Repository logs available from:

http://downloads.arduino.cc/libraries/logs/github.com/avandalen/avdweb_CodeDebugScope/

New Repository logs that will be available when the new URL becomes active

http://downloads.arduino.cc/libraries/logs/github.com/avdwebLibraries/avdweb_CodeDebugScope/

The new release has already got picked up thanks to github re-routing:

2024/08/23 15:37:13 Checking out tag: 0.0.1
2024/08/23 15:37:13 Release CodeDebugScope:0.0.1 already loaded, skipping

Just one more question :

Do I update all the repository URL in one pull request or do it sequentially for each library ?

(as there are multiple libraries being moved)

Thanks again for the generous help and guidance.

@per1234
Copy link
Contributor

per1234 commented Aug 23, 2024

The new release has already got picked up thanks to github re-routing:

Yeah, when the library repository URL changes as the result of the library maintainer using GitHub's rename or transfer features, GitHub automatically creates a redirect and this allows the Library Manager indexer to continue to be able to monitor the repository even though it has the old URL.

However, it is still recommended for the library maintainer to submit a URL update as you have done here so that we aren't reliant on that redirect (for which which we don't have any guarantees of working forever).

Do I update all the repository URL in one pull request or do it sequentially for each library ?

You can take whichever approach you prefer. I personally prefer to use a separate pull request for each library because this way if there was a problem with the operation for one library it wouldn't block the operation for the other libraries. But such a situation rarely occurs.

@boseji
Copy link
Contributor Author

boseji commented Aug 24, 2024

Thanks a lot for your guidance,

I will follow the step by step approach.
And will do One library at a time.

Ensure that the migration happens from the Logs as well.
Then move to the next one.

Looking forward to follow suit for my older libraries also.
I had quite a few before the malicious 2021 take-down notices.

Thanks to Arduino and the whole open-source we will prevail and prosper.

@MatteoPologruto MatteoPologruto self-assigned this Sep 12, 2024
Copy link
Contributor

@MatteoPologruto MatteoPologruto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done:

2024/09/12 16:03:57 Loaded 7292 libraries from DB
Changing URL of library CodeDebugScope from https://github.com/avandalen/avdweb_CodeDebugScope.git to https://github.com/avdwebLibraries/avdweb_CodeDebugScope.git
Success!

@MatteoPologruto MatteoPologruto merged commit 4c7d876 into arduino:main Sep 12, 2024
12 checks passed
@MatteoPologruto MatteoPologruto added the conclusion: resolved Issue was resolved label Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: resolved Issue was resolved status: pending backend Depends on backend maintenance operations topic: URL change Change library repository URL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants