When I click the big download button at
http://github.com/subsonic/SubSonic-3.0
I don't know what version I'm getting. On the download panel there are 3 additional versions listed for download. Which is the most recent, the default or 3.0.0.3?
And does the big download button get me everything for that version?
On GitHub, when you click the "Download" button (not the tab), you will download the latest revision (known as the master branch in Git) in the repository. This is potentially untested code and should be avoided in production environments.
To answer your question specifically, you should download 3.0.0.3 unless you want potentially untested, beta-quality code.
For more reliable information, check the SubSonic Download page.
Related
Is there a way to search the Subversion repository of a project hosted on SourceForge? I see that I can Browse Commits/Files but I'd like to perform a full text search. If no such feature exist, is there a workaround like a way to export the entire SVN repo (I'm not the project owner)?
An example, I'm a user (not project owner) trying to find changes involving the ORB_ID_STRING literal on the omniORB project.
I unsuccessfully attempted to answer this question by: searching stackoverflow, searching using various Google keywords like "sourceforge how to search SVN". I also submitted this SourceForge support ticket: https://sourceforge.net/p/forge/site-support/20997/.
Here is the reply I got from SourceForge Support on Monday July 20, 2020:
Dave Brondsema -
Hello,
We do not currently offer an option to search the full text of a code repository. You
can download the repository yourself though and do a search yourself. The easiest option
is to use the "Download Snapshot" link in the upper right of a code repository. Note:
you probably want to be in the "trunk" folder first or it will be a very large download
including copies of all the branches and tagged versions of the code. Alternatively, you
can install SVN on your computer and do an SVN checkout of the repository.
Sincerely,
SourceForge Support
I have accidentally deleted a Wiki-page from our repository in Azure DevOps.
(How) can I recover it?
That is not an option for us, since we will loose many changes that
were made after the last version no. up until the date I accidentally
deleted the wiki page.
You can choose Clone wiki to download the wiki repo to local machine.
Then use git commands(git revert or what) locally to get the deleted page, once you find the deleted page, publish it and add it back to Wiki page as a new commit.
I was just able to do this without too much fanfare. The resource that was helpful was this VS community topic. There is an answer that provides a solution that doesn't require you to clone the repo.
The key insight is that you can navigate to the Azure DevOps repo UI for the Git repo that's backing the wiki. The solution author says that the shape of the URL is something like https://dev.azure.com/<organization-name>/<project-name>/_git/<wiki-name>.wiki. This didn't quite work for me because we have a different URL scheme in our organization, but I was able to figure it out after a little trial and error. I later saw that you can get the URL by using the Clone Repo UI in the wiki - it gives you the URL, so you can just copy it and navigate to it.
Anyway, the steps were:
Figure out the URL of the git repo that backs the wiki
Navigate to the revision history for the entire wiki
the current UI shows you the Contents tab by default - switch to History
Scroll until you find the commits that deleted the pages you want to restore
it's one of those list views that populate themselves as you scroll, so you won't be able to use the browser page search efficiently, unfortunately
Revert the commits
In my case, this required clicking on them and creating pull requests to revert, but I was able to merge them myself without involving code reviewers. YMMV
All in all, not a wholly terrible experience, but completely undiscoverable.
Assuming you're managing a provisioned wiki (vs using published code as a wiki):
Look in the top-right corner for the vertical 3-dot menu, where there's an option to view revisions:
Choose the revision you want to revert to (e.g. the one prior to deleting the needed wiki page), from the list (click on its version hash):
From the revision details, select "Revert":
At this point, your wiki should be at its prior state, and your wiki page should once again be available.
Note: If you're using published code as a wiki, you would recover/revert your changes as you would with any other code commit.
More details may be found here.
I couldn't find a way to do this through the Azure DevOps web interface but you can restore the page by reverting the commit that deleted it if you clone the wiki locally.
Clone the wiki to your computer - find the clone wiki option in the menu at the top of the left bar which shows the wiki contents, copy the URL and use to clone locally using your usual git client.
Find the commit that deleted the page, the commit message will start with "Deleted page" then the name of the page you deleted.
Restore the page and commit the change. There are various ways to do this - I reverted the commit, you could checkout the commit and copy the page out to make a new commit. You may get a merge conflict on '.order', I'm not sure what the best thing to do is but I kept the current version and haven't had any problems.
Push the changes to Azure DevOps, refresh and you'll see the page has been restored.
This works even for Project Wikis. I wonder if Azure DevOps has added the functionality that enabled this since some of the other answers have been written.
I have a problem with my releases in GitLab.
I created them in my project with tags. Now I want to remove them, so I deleted the associated tags but my releases are always displayed. I searched on Google and Stack Overflow but I can't find any solutions.
How can I remove these releases without their tags?
Go to Project Overview -> Releases
Click the release you want to delete
Scroll to the bottom. Find the tag icon. Click on the tag.
There is a trash can button for the tag. Deleting the tag will delete the release as well.
By now you can delete releases properly using the API:
https://docs.gitlab.com/ee/api/releases/#delete-a-release
Currently (GitLab v11.9.8) you can't. It's silly, I know, but you can't.
Ivan came up with a workaround if you have only a few releases to delete. His steps are copied below.
Ivan Kostrubin (#ovitente):
For fixing this issue you have to go through those steps
Create tag with the same name and release message that was in release, you will be able to edit this tag.
Open tag's release message for editing
Remove all text
Save it
And release has gone from the release list.
Then you can freely delete tag.
Source:
https://gitlab.com/gitlab-org/gitlab-ce/issues/58549#note_160000873
Check out these GitLab issues:
[#58549] Deleting releases with removed TAG in Release API
[#56026] Make it possible to add/edit/delete a release using the UI
Maybe I'm late but I've created a chrome extension that allows you to do just that, hope it helps :)
https://github.com/tuanddd/grru
Go to Repository -> Tags on the left side Collapse sidebar. Then click on the delete icon on the right of the tag name.
Example:
GitLab 15.3 (August 2022) should improve release management:
Releases usability improvements
In 15.3, we made several improvements that made GitLab Releases easier to use.
Users can now:
delete a release directly in the UI,
set the release date in the UI,
edit the release_at date in the UI, and
easily identify a historical release.
See Documentation, Issue, Issue, Issue and Issue.
For instance: Delete a release, starting with GitLab 15.2:
When you delete a release, its assets are also deleted. However, the associated Git tag is not deleted.
Prerequisites:
You must have at least the Developer role. Read more about Release permissions.
To delete a release in the UI:
On the top bar, select Menu > Projects and find your project.
On the left sidebar, select Deployments > Releases.
In the top-right corner of the release you want to delete, select Edit this release ().
On the Edit Release page, select Delete.
Select Delete release
gitlab-scripts repo
I created a bash script that will remove all releases given a repo name,
purge/releases.sh
There are similarly named purge/tags.sh and purge/packages.sh in the repo. You can call any of them like this,
GITLAB_TOKEN="mytoken" ./reset-repo.sh <repo>
Use the gitlab gem.
gem install gitlab
gitlab delete_project_release 1234 'v1.2.3'
I am facing a problem with TortoiseSVN (my client version is 1.6.16 and the SVNversion is 1.4.6.28521).
The projectA project has the classical architecture, with three folder: trunk, branches and tags.
I have rights to Read and Write from a projectA folders (tags,branches and trunk).
While working in the trunk, there is no issue, everything works fine. The only problem is that when a release time comes (or branching time comes), and I want to create a tag (a branch), I want to use the TortoiseSVN dialog "branch/tag". Then I choose the origin from the trunk or the revision o nthe trunk i need, and choose the "To URL" like "http://..../projectA/tags/v2.0".
After clicking "OK", it will let me know that the access to "http://...../projectA/" is forbidden.
The only solution right now, is to checkout the "projectA/tags" folder to a local folder. Then in this "projectA/tags" folder I will create one new folder with the name of the tag I want to create, and I am able to commit it without any problem.
I don't want to manually create the folder of the tag/branch like this, andwould rather like to use the "branch/tag" feature of TortoiseSVN.
Anyone has an idea about this issue ?
There is a recommendation in Subversion (at least on Windows with TortoiseSVN) to use the same major version as the server. You are allowed to ignore that recommendation, and most of the time, it does not hurt, but here you may have a case where it makes a difference. You should at least check if
the server could be upgraded to 1.6.x XOR
the client (your installation) could be downgraded to 1.4.x
However, your client will ( in the second case ) no longer work with your checkout directories. Branching has changed a lot from version 1.4.x to 1.6.x, so you will face a hard time if you have to use a 1.6.x client with a 1.4.x server.
I have svn repoistory of the project on which I am working in company's server. Today I got different version of software through zip files which I have extracted in my local folder in C drive. Now how will i compare between projects on svn repository and the one I have downloaded in my local folder. I am using SVN tortoise on windows platform. Now when i rightclick on my local folder it doesnt show merge or diff option. Please throw some light on it.
thanks
One option is to compare the two versions directly using a file/directory comparison tool like WinMerge. You could then merge changes from the zipped archive into your SVN working copy.
With modern versions of TortoiseSVN, there's a fairly straightforward way of doing this:
Make sure that you're using TortoiseSVN 1.7.0 or later.
Make sure that your working copy has been upgraded to the 1.7 format. If you right click on the working copy and it gives you the option "SVN upgrade working copy" then use that option.
Copy and paste the .svn directory from your working copy into the same part of the hierarchy of the version you got via Zip files.
You should now be able to use regular TortoiseSVN actions in the zip version, such as "Diff with previous version", etc.