In both windows and linux how to find installed mercurial is 32 or 64 bit using cmd line ?
hg version doesnt show.
C:\Users\dkanagaraj>hg --version
Mercurial Distributed SCM (version 3.4.2)
(see http://mercurial.selenic.com for more information)
Copyright (C) 2005-2015 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
On Debian or Ubuntu Linux you can query the "mercurial" package using dpkg -l mercurial.
Here is some sample output:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii mercurial 2.8.2-1ubunt amd64 easy-to-use, scalable distributed
Notice the amd64, it shows that it's a 64bit version.
On RedHat or Fedora and other RPM-based distributions the command is probably
rpm -qi mercurial
Related
I am having a problem configuring the automatic update for the TeXLive
even though I am pretty sure that I downladed the 2018 TeXLive version
I get is this error
$ ls -l /usr/local/texlive$ sudo tlmgr update --self --all
[sudo] Passwort :
(running on Debian, switching to user mode!)
tlmgr: Remote repository is newer than local (2017 < 2018)
Cross release updates are only supported with
update-tlmgr-latest(.sh/.exe) --update
Please see https://tug.org/texlive/upgrade.html for details.
looking for my TexLive version it shows that it is the 2018 version
$ ls -l /usr/local/texlive
insgesamt 8
drwxr-xr-x 9 root root 4096 Nov 20 17:50 2018
drwxr-xr-x 10 root root 4096 Nov 20 16:13 texmf-local
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
But running this command it shows another version of it
$ tlmgr version
(running on Debian, switching to user mode!)
tlmgr revision 46207 (2018-01-04 19:34:36 +0100)
tlmgr using installation: /usr/share/texlive
TeX Live (http://tug.org/texlive) version 2017
$ tex --version
TeX 3.14159265 (TeX Live 2017/Debian)
kpathsea version 6.2.3
Copyright 2017 D.E. Knuth.
There is NO warranty. Redistribution of this software is
covered by the terms of both the TeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the TeX source.
Primary author of TeX: D.E. Knuth.
$ latex --version
pdfTeX 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
kpathsea version 6.2.3
Copyright 2017 Han The Thanh (pdfTeX) et al.
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Han The Thanh (pdfTeX) et al.
Compiled with libpng 1.6.34; using libpng 1.6.34
Compiled with zlib 1.2.11; using zlib 1.2.11
Compiled with poppler version 0.62.0
Change the repository to an older version fixed this for me.
tlmgr option repository ftp://tug.org/historic/systems/texlive/2017/tlnet-final
After that, I can run the update command.
Found this solution in a comment at stackoverflow.com, but I don't know the thread anymore.
Fedora 23 provides the odb-2.4.0 package.
This git repo
git://pkgs.fedoraproject.org/odb.git
is probably where a fedora-modified copy of the sources exist.
The upstream git repo exists here
git://scm.codesynthesis.com/odb/odb.git
I need the newer upstream version which doesn't crash for some code i have, while odb 2.4 does.
How can I go about building and installing the newer version, and potentially, after more commits in upstream, rebuild and reinstall the newer version?
Do I make a source rpm and install on my machine, and another with an identical fedora?
I am reading
https://fedoraproject.org/wiki/How_to_create_an_RPM_package
but I do not need to deploy this package to fedora, i just would use the RPM mechanism to facilitate installing unreleased versions?
Can I use COPR for that, add my own repo, and install from it instead?
In COPR, can I reuse the SPEC file from the odb2.4.0 rpm and update it to the newer odb?
I successfully installed caffe on my dual-boot laptop (GTX 860M, Windows 7 + Ubuntu 14.04.2). All the tests were successfully passed. When I restarted, however, the ubuntu got stuck on the opening screen (the one with ubuntu logo and five red dots). Don't know what to do with it.
Has anyone run into the same issue before? I reckon something is wrong with graphic card driver booting. I installed newest CUDA 7 Toolkit with nvidia drivers built inside. Since all tests were passed before I restarted, it seems that the driver would work once successfully booted.
the stuck screen is like this: http://i.stack.imgur.com/pRtEF.jpg
I had a similar issue when trying to install Caffe on my system. The steps below worked for me, but it has at least one known issue (documented below).
I'm not sure what precisely caused this problem, but it surely has something to do with the Nvidia Driver and Cuda Toolkit installation and is not caused by Caffe.
After completing the steps below, I've been able to successfully install Caffe on my system with the following tutorials and guides:
Official Install Guide
Github Install Guide
Update
Recently, I had the exact same problem trying to make Cuda 7.5 work on Ubuntu 14.04; this approach also solved that problem. Specs:
CPU: Intel Core i7-4700MQ (4x 2.40 GHz with Hyperthreading)
GPU: NVidia GT 940M
RAM: 8 GB
HDD: 52.7 GB (of which 6.7 GB used after installation)
INSTALL NVIDIA DRIVER AND CUDA ON UBUNTU 14.04
Source: ubuntuforums.org/showthread.php?t=2246526
!! Known Issues !!
After the system has been suspended (or hibernated, not confirmed), all applications using the Nvidia Driver and Cuda 6.5 Toolkit will freeze. When this happens, the command sudo shutdown -r now will print the reboot message but nothing will happen.
Executed and tested on a fresh 64-bit Ubuntu 14.04 install with the following hardware specifications:
CPU: Intel Core i5-2410m (2x 2.30 GHz with Hyperthreading)
GPU: NVidia GT 540M
RAM: 6 GB
HDD: 52.7 GB (of which 8.6 GB used after installation)
The following command was executed before installation:
sudo apt-get -y build-essential vim git llvm clang
The following steps resulted in a stable system with the latest Nvidia Driver and Cuda 6.5 Toolkit installed:
Remove all traces of previous/legacy Nvidia Drivers and Cuda Toolkits or perform a fresh Ubuntu 14.04 install.
Download the latest Nvidia Driver .run file for Ubuntu 14.04 and your system specifications to the ~/Downloads directory.
e.g.: NVIDIA-Linux-x86_64-346.35.run
Download the latest Cuda 6.5 Toolkit .run file for Ubuntu 14.04 and your system specifications to the ~/Downloads directory.
e.g.: cuda_6.5.14_linux_64.run
Blacklist the 'nouveau' Driver by appending the following lines to /etc/modprobe.d/blacklist.conf (nouveau is a free open-source driver for Nvidia cards, it is the default for Ubuntu 14.04):
blacklist nouveau
options nouveau modeset=0
Reboot the system, do NOT log in but drop to the terminal with CTRL+ALT+F1
Kill lightdm (replace 'lightdm' with your own Display Manager if you have changed it, lightdm is the default for Ubuntu 14.04):
sudo service lightdm stop
The next step is critical, make sure to check twice before continuing!
Run the Nvidia Driver installer with the --no-opengl-files option (the option prevents OpenGL files from being overwritten; without this option, Unity would not function properly and the screen would freeze after login):
sudo chmod +x ~/Downloads/NVIDIA-Linux-x68_64-346.35.run
sudo ~/Downloads/NVIDIA-Linux-x68_64-346.35.run --no-opengl-files
Accept the EULA and acknowledge all further warnings but deny to install anything extra.
Reboot and login to the desktop, verify with the 'Additional Drivers' (System Settings > Software & Updates > Additional Drivers) utility that the manually installed driver is in use.
Open a terminal and install the Cuda 6.5 Toolkit:
sudo chmod +x ~/Downloads/cuda_6.5.14_linux_64.run
sudo ~/Downloads/cuda_6.5.14_linux_64.run
Accept the EULA, do NOT install the driver, install the Toolkit and the Examples (if you want to), leave all default directories in place.
Add the Cuda 6.5 Toolkit environment variables by appending the following lines to ~/.bashrc:
# For 32-bit systems, append these:
export PATH=$PATH:/usr/local/cuda-6.5/bin
export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib
# For 64-bit systems, append these:
export PATH=$PATH:/usr/local/cuda-6.5/bin
export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64
The Nvidia Driver and Cuda 6.5 Toolkit should now be correctly installed.
Optional: confirm your Nvidia Driver and Cuda 6.5 Toolkit installation.
Confirm the Nvidia Driver installation by running the following command:
nvidia-smi
Confirm the Cuda Compiler installation by running the following command:
nvcc -V
Confirm everything works by building and running the optionally installed Cuda Examples: (build-essential is required to use 'make')
sudo apt-get install -y build-essential
cd ~/NVIDIA_CUDA-6.5_SAMPLES/1_Utilities/deviceQuery
make
./deviceQuery
cd ~/NVIDIA_CUDA-6.5_SAMPLES/1_Utilities/bandwidthTest
make
./bandwidthTest
This problem is not related to caffe.
The problem is that the nVidia driver that is installed from the ubuntu software center does not support your card.
Uninstall any nvidia package (sudo apt-get purge nvidia-*) and install the latest driver version from the nvidia website.
I recommend you to change the cuda 7.5 ubuntu 15.04 version. I try it on the ubuntu 14.04, it solves this problem. And when I install cuda 7.5 ubuntu 14.04 version on ubuntu 14.04 I countered the exactly problem.
I am trying to install mercurial 2.2 on CentOs 6.3, however I feel that repository of centos is a bit outdated because of which it yum installation always shows that your mercurial is up to date.
Now searched some forum and found some other repository to update mercurial client by using following command and repository:
**
rpm -Uvh
http://pkgs.repoforge.org/mercurial/mercurial-2.2.2-1.el6.rfx.i686.rpm
**
However it results in following error:
hg = 1.4-3.el6 is needed by (installed) emacs-mercurial-1.4-3.el6.i686
hg = 1.4-3.el6 is needed by (installed) mercurial-hgk-1.4-3.el6.i686
I think due to some package dependency, I am not able to install.
Any help/pointers will be highly appreciated.
From the Blog: Install Mercurial Centos 6 VPS Mercurial 2.2.2 Centos 6.4 setup
This the only package you're able to install because other RPM packages require python 2.4 whereas Centos 6 has python 2.6 installed.
rpm -Uvh http://pkgs.repoforge.org/mercurial/mercurial-2.2.2-1.el6.rfx.x86_64.rpm
Test your install:
[root#~]# hg version
Mercurial Distributed SCM (version 2.2.2)
(see http://mercurial.selenic.com for more information)
Copyright (C) 2005-2012 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I think you will need to uninstall an older (1.4.3) version of Mercurial. Or at least get rid of the emacs-mercurial and mercurial-hgk packages first.
echo -e "[mercurial.selenic.com]\nname=mercurial.selenic.com\nbaseurl=https://www.mercurial-scm.org/release/centos\$releasever\nenabled=1\ngpgcheck=0" > /etc/yum.repos.d/mercurial.selenic.com.repo \
&& yum install -y mercurial
As described in the mercurial wiki. Although, as gpgcheck=0 is kind of evil, I'd skip it if possible.
When I installed TortoiseHg thro synaptic in my Ubuntu system, the HG Workbench was spontaneously installed into my main menu.
However, when I installed TortoiseHg thro synaptic in my debian 6.0 system, HG Workbench was not found in the main menu and neither was the thg comannd found anywhere.
The TortoiseHG version is 1.1.1-1.
How can I get to invoke the thg or workbench command in debian?
Are there additional modules I had installed in ubuntu which I did not in debian (which I might have forgotten)?
Thank you.
In Debian you may have TortoiseHG 2, where command is just hg
To my dismay, Debian is not as up-to-date as Ubuntu. And support is not as comfortable a level I have been having with Ubuntu. However, Ubuntu has become rather slow to boot up and is eating too much resources (might as well go back to Win 7). Also, Ubuntu obsessively+compulsively insists on providing horrendous desktop/colour schemes.
Answering my own question ...
The latest stable Debian is Squeeze which allows only Mercurial 1.6.4, TortoiseHg 1.1.1. Whereas, in Ubuntu 12.04 LTS I am having 2.0.2, TortoiseHg 2.2.
Attempting to install Debian Squeeze backport for Mercurial 2.2/TortoiseHg 2.4 resulted in unresolved dependencies. Need to investigate if that is due to dependency on Qt4.8.
TortoiseHg 1.1.1 does not have thg workbench. It has hgtk and hgview. I prefer thg over hgtk. To mitigate the circumstances, I installed TortoiseHg 2.6 in my Win7 Virtualbox in my Debian machine, where I would use my Win7 TortoiseHg to operate on a shared folder. Using 2 cpu threads out of 16 for Win7 should not hurt my Debian machine very much.