I am trying to have Launchpad mirror a Bazaar branch on SourceForge but failing. Is it at all possible? The Launchpad shows this log for the process:
2012-02-26 12:44:20 INFO Starting job.
2012-02-26 12:44:20 INFO Getting exising bzr branch from central store.
2012-02-26 12:44:20 INFO [chan bzr SocketAsChannelAdapter] Opened sftp connection (server version 3)
2012-02-26 12:44:20 INFO Invalid URL: bzr://log4cplus.bzr.sourceforge.net/bzrroot/log4cplus/trunk/
Please file a bug against the Launchpad project about this.
Related
I'm running Sonatype Nexus 3 inside a docker container, with the following startup command:
docker run -d -p 80:8081 --ulimit nofile=65536:65536 --name nexus -v nexus-data:/nexus-data -e INSTALL4J_ADD_VM_PARAMS="-Xms4g -Xmx4g -XX:MaxDirectMemorySize=6717m -Djava.util.prefs.userRoot=${NEXUS_DATA}/javaprefs" sonatype/nexus3
After updating the docker image version from 3.30.0 to 3.40.1, I keep getting the following warnings regarding user prefs.
2022-07-18 13:14:45,860+0000 WARN [Timer-0] *SYSTEM java.util.prefs - Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.
2022-07-18 13:15:15,860+0000 WARN [Timer-0] *SYSTEM java.util.prefs - Could not lock User prefs. Unix error code 2.
As you can see from the startup command, the user prefs directory is inside the docker volume and at directory /nexus-data/javaprefs . I have tried looking for existing locks inside the directory, but found none. I've also tried completely deleting the directory and saw that the warning still came up and the folder itself wasn't being created by Nexus.
I honestly don't even know if this is an important issue or not, since there is little to no documentation about the user preferences folder.
Even a way to turn off the warning log which fires every 30s would be useful.
----UPDATE----
I've tried doing a clean installation of Nexus through Docker, following the simple instructions inside the github sonatype nexus3 docker repository, and still find these warnings.
I even tried on a different OS (Windwos instead of linux, through Docker Desktop) and with and without a volume for /nexus-data.
At this point I believe it to be a bug in a newer Nexus version.
TLDR: Adding -Djava.util.prefs.userRoot=/nexus-data/javaprefs should solve the problem, assuming the nexus data directory is at /nexus-data/.
Just had the same issue after upgrading from 3.38.1 to 3.42.0. After some investigation found that indeed the java.util.prefs.userRoot property got lost somewhere between those versions. The default value in the vanilla Nexus 3.38.1 is /nexus-data/javaprefs.
I'm following this guide to download the Repo for client, mirror and master.
My doubt concerns that when i run:
repo sync
download me:
For repo client: ~ 150GB
For repo mirror: more than 320GB (I don't know how match, because I have no more memory space)
For repo master: I don't know but the web page says that is similar to repo mirror
So, my question is: is this huge amount of data being downloaded normal? I would like to understand this since my pc only has 500GB.
I have launchpad repo which I'm pushing commits, and my friend wants to push a patch file into it but when he tried he got this error.
$ bzr push :parent
bzr: ERROR: Cannot lock LockDir(chroot-90567632:///~catchsudheera/maria/pcre_regex_enhance/.bzr/branch/lock): Transport operation not possible: readonly transport
How would I give him the required permissions? thank you very much.
PS : bzr info results:
sudheera#Dr-HOUSE-PC:~/Gsoc/mariadb/repo5/maria$ bzr info
Standalone tree (format: 2a)
Location:
branch root: .
Related branches:
push branch: bzr+ssh://bazaar.launchpad.net/~catchsudheera/maria/pcre_regex/
parent branch: bzr+ssh://bazaar.launchpad.net/+branch/maria/
Branches starting with address lp:~catchsudheera are your private branches on Launchpad. It is not common to let other users push to these branches.
Ask your friend to push to his own Launchpad account, for example lp:~hisusername/maria/pcre_regex_enhance. After that, he can visit the page of his branch on Launchpad, https://code.launchpad.net/~hisusername/maria/pcre_regex_enhance, and use the Propose for merging link to propose the branch for merging into yours. You can then merge his branch in your workspace and push it to your own branch.
I try to clone a GIT repository with EGit using SSH. I can log on to the machine, see the available branches and choose where to put everything locally. Then when I proceed to actually do the cloning, I get an Eclipse "Problem Occured" box stating:
"Cloning from ssh://[my user name]#[my address] has encountered a problem. ssh://[my user name]#[my address]: Password:". The details for the problem only list "ssh://[my user name]#[my address]: Password:" twice.
The only possible reason I can think of, might be that on the remote compute only Git 1.6.0.x is installed - and I don't have the rights to update it.
Can you clone the repository using native git? If you can do that, just clone it using native git and then import the project into eclipse using:
File -> Import -> Projects from Git -> Local
If your eclipse runs on Windows, you will need a linux machine (virtual machine will do) and clone the repo into a NTFS or Fat32 formatted storage. Then you will be able to copy the cloned repo into your git folder on the windows machine.
I have a problem with the deployment of the project on the production server. We use Capistrano and Passenger. The problem is that we moved the project repository on GitHub to another account. I changed the repository address in the file deploy.rb, however, during the 'cap production deploy ", after authentication by the production server, Capistrano is looking for an old repository, which fails. I suspect that this is a change in the repository. git on production, but I do not know how to do it.
servers: ["85.xxx.xxx.xxx"]
Password:
[85.xxx.xxx.xx] executing command
** [85.xxx.xxx.xx:: err] ERROR: repo / repo.git does not exist. Did you enter it correctly?
** [85.xxx.xxx.xx:: err] fatal: The remote end hung up unexpectedly
command finished in 4220ms
*** [deploy: update_code] rolling back
Try editing shared/cached-copy/.git/config and modify the git repo listed there. If you're using the remote_cache method, it keeps a local git repo and updates that on the remote machine. Repoint that to your new git repo and you should be good to go.