The set back I noticed was not due to ubuntu but due to the incompatibility of the bitcoin client. The bitcoin-qt program depends on libdb4.8 and boost 3.1, which are not part of ubuntu anymore (and most likely debian). So it seems that the ubuntu maintainers removed it from the distribution for that purpose. People on the forum were reasoning that the PPA maintainer doesn’t have time and he’s only one guy. I don’t think the guy can do anything if the dependencies are not there, I also don’t think that ubuntu distribution will accept a statically linked version of bitcoin-qt.
May be bitcoin should move the standard wallet to another format, which is not dependent on a certain libdb version. May be an XML format with the wallet encoded as hex strings.
Your work around: Download the statically linked version from the bitcoin.org website.
Just tried installing the beta of ubuntu trusty tahr, and being an xfce user I really didn’t notice much updates over there other than just being an LTS. I had to pin apt packages back to saucy to downgrade since the xfce indicator applet was crashing non stop.
Will definitely upgrade towards the end of the month once it stabilizes a bit more.
lxdm doesn’t work with mate. Once you select mate and try to login nothing happens. When I switch to a text console and do ps -ef | grep session it seems that there is no session running. wdm logs in fine, but sound does not work and the network applet appears as if there’s not network, but actually network is working.
gdm works fine and the other services work as well. I didn’t test lightdm but I don’t like it because I feel it is slow.
It seems that ubuntu raring 13.04 was released with a packaging problem in maven. I upgraded my home computer desktop quantal 12.10 to 13.04 raring and other some regular issues, which I usually solve by apt-get -f install, I got an error while installing maven. It seems that maven depends on both libwagon-java and libwagon2-java and both contain the same jar file. dpkg then will issue an error and stop.
I forced the installation of libwagon2 using dpkg -i –force-all /var…. and it worked. However, I know that now when one of those two packages gets removed the jar will be removed as well, and then I will need to purge then package then re-install it.
I’ve been going back and forth between IntelliJ’s idea, netbeans and eclipse for java development. I was able lately to setup eclipse with all the features I need, and performs all the compilation function required including pulling maven dependencies and hot deploying jetty’s code on save and the best thing was the ability to edit it’s colors using the CSS provided.
How to do that:
1. Using git clong jBug from http://github.com/mibrahim/jbug.git
2. Inside there, there’s a directory called “settings” in which there are two files: preferences.epf (which includes the editor settings and color theme) and e4_default_gtk.css and that will set the color and font sizes of the tabs.
3. Copy the css file over your eclipse/plugins/org.eclipse.platform_4.2.1.v201209141800/css/e4_default_gtk.css
For plugins, using the market place add the following:
1. egit (to integrate with git)
2. Run-jetty-run, will use in-place deployment with jetty and will close and open the handlers and contexts if you change any of your classes or their dependencies (excellent work)
3. m2e for maven
4. Eclipse color theme. In case you wanted to change the theme edit the wombatcss.xml then import it.
Since eclipse is not a limited edition as idea, you will be able to edit jsp and other files that you won’t be able to edit in idea. It is also much more efficient in terms of memory usage than netbeans and does not block or stop erratically like netbeans as well.
So IntelliJ says it compiled successfully a project. However, when I execute maven jetty plugin to run a small web project, I end up with jars not being found. So what does it exactly mean when IntelliJ says compile successfully ? It seems that it just compiles them, and it really does not make any difference whether you compile or Make the project both cases will result in missing jars if you run the project using maven jetty plugin.
There’s lots of crap in netbeans however it seems to be the only edit that does what it says it’s going to do in terms of maven compilation. It sill suffers from some issue like for example you won’t be able to disable tests if you compile with dependencies.
For the time being I have to accept the flaring white colors of netbeans until one day I can figure out a more consistent way of configuring it.
I admitted defeat in using netbeans for doing anything useful. I tend to waste my time trying to fix the colors so that I can read the code, and that if I didn’t get totally frustrated from simple actions not happening as expected. Simple things like dependencies between maven modules should be happening automatically. If you used intelliJ’s idea and set auto-compilation to true, and change a class in one module, it will automatically build the dependent modules and fire errors if necessary.
For their credit they have a very good core integration with maven. However, features are not finished nicely all the way to the end. I really don’t know if the project is losing volunteers and that’s why it is adequately tested or it is being steered to the death path to be replaced by an even slower and worse project aka JDeveloper.