So, wanting to access a USB device from python on Windows, I've spent the morning searching the web and it seems that the most popular, comprehensive and up to date (as of late 2014) combo is PyUSB (1.0.0-beta-2) on top of libusb-1.0 (1.0.19). In particular it took me a while to figure out the current status quo regarding all the politicking, forks, re-combinations and domain name changes that the libusb-1.0 project has undergone over the last couple of years.
So, AFAIK the current official/definitive libusb-1.0 project is hosted at
https://github.com/libusb
has download tarballs at
http://sourceforge.net/projects/libusb
and maintains a project page at
http://libusb.info/
Given all the ructions, looking at the SourceForge download page I was a bit suspicious to note that while 1.0.19 is the most recent release, 1.0.9 from a couple of years back is still the more popular download. Why?
I'm happy with TessellatingHeckler'e explanation. The zombie web site libusb.org that links to the old 1.0.9 version of the library on SourceForge has the highest Google page rank and is the first thing people find when searching for details on the project
Related
I have a ROS Indigo on a 64bit Kubuntu 14.04. Currently I'm facing a big issue - the missing module on_nurbs. I need it for the generation of meshes from point clouds.
My biggest problem here is the way ROS is hooked to PCL. Even though PCL is now more or less officially an external dependency the way ROS handles the situation is...Well, not very nice. I've experienced similar (maybe even the same - can't remember) issues with OpenCV - yet another dependency that was decided to be made completely external - when I decided to build it from source in order to add support Qt, OpenGL etc, which are not in the upstream packages of the library in the Ubuntu repositories. There is this thing ROS perception, which is supposed to add the glue between ROS and PCL.
The problem: Adding NURBS (part of the surface module)
What I have done so far:
I have
downloaded and built PCL 1.7.1 (the same version as the one shipped with Ubuntu 14.04 and ROS) with NURBS enabled
(1) installed PCL from source - ROS' PCL support broke
(2) replaced only the surface library (also added all the includes etc. dependencies for it and nurbs from my build) - ROS' PCL support broke
Currently I'm struggling to find out how to manually force CMake (and thus also catkin_make) to use my own version (not installed, only built). But I fear this will again interfere with ROS.
What is your advice for me in this situation? How can I proceed without yet again breaking my ROS installation? I would really like to learn how to add such missing bits and pieces - as mentioned above - I have already faced this issue once, now this and it will probably happen again.
PS for those who say "This is a ROS issue": I've already posted on ROS answers a week ago but there is still no reply and the views indicator of 11 (became so shortly after posting there - a week ago) is discouraging to say the least. The chances of any development there a week after posting the question are slim to none. I have been struggling with this issue for more then 2 weeks now...
I am working with erlang project which uses google protobuf via https://github.com/basho/erlang_protobuffs
After some time I've got not such good impresion about it (I've found usage of this technology in erlang very clumsy and inconvenient). But of course, I known that this is because I can not cook it properly.
Which open source erlang project are using erlang_protobuffs? I am interested in best (or at least sufficient) practices of its usage.
I assume that you mean http://github.com/basho/erlang_protobuffs library.
From major opensource projects I know only basho's riak using this library, although
Github code search gives a lot of different projects.
Note, that this library is not only one, take a look at this post
My standard route has been to go to confluence, find the docs sections, then navigate through to the install docs for the version, e.g. sakai 10:
https://confluence.sakaiproject.org/x/iYGLBQ
Through one means or another I happened across the source route to this too, so starting here....
http://source.sakaiproject.org/release/
You get redirected to the latest stuff, and appended version numbers to that url gives you other docs, e.g. adding 2.8.2 or 10 to the end of the url
But the links to what I should download are quite often not there, at the time of writing the 10 tar ball and zip in the confluence links are dead and the source.sakaiproject links doesn't have the 10 docs yet (redirects to 2.9.3) presumably this is because v10 is not released yet....
So, I'd like to evaluate a new version of a sakai source install, what's the best way to do this? (considering the official documentation for install is still being formed)
Do I download the latest SVN, or the latest RC or the latest beta or??? How do I know what's best to test against without being "too" bleeding edge? Is there a recommended tar ball/zip link to test against? Is there a "latest good" SVN branch?
The latest code is always in the Sakai trunk (currently svn):
https://source.sakaiproject.org/svn/sakai/trunk/
That code may very well not be stable though as it is where things are being actively developed. If you are not actively developing then you should stick to the releases as indicated on the project website here:
http://sakaiproject.org/current-release
If you want to use something in between (say an upcoming release) then you can grab the most recent tag or maybe use a recent branch (both currently in svn, latest shown below at the time I write this):
https://source.sakaiproject.org/svn/sakai/branches/sakai-10.x/
https://source.sakaiproject.org/svn/sakai/tags/sakai-10-rc02/
The reality of the situation is that if you want to use something other than the release then you should really participate in the dev community for Sakai. Joining the mailing lists and the weekly calls will provide the information you are asking about and much more.
I used to rely on the Novell ftp site to retrieve fully fledged Linux based Mono virtual machines.
Latest VM available is Mono-2.10.2, published on April, 26th 2011 (few days before the "Attachmate" incident).
The VMWare_Image page, on the Mono project site, states that "You can download the VMware image with Mono pre-installed and pre-configured from our Downloads page.". Unfortunately, I can't find anything relevant on the Downloads page.
Now that Xamarin has came to an agreement with Novell, is there a new source where one could download preconfigured Mono appliances?
I know what you mean, there used to be official images to grab from the mono-project.com page. The images were build using open(suse) build service and based on opensuse. The official builds are outdated, but you can try searching the SUSE Gallery, which is basically a public collection of user-build opensuse images, using different software selection.
A search for mono: http://susestudio.com/search?q=mono
I have not tested any of these myself, but you might want to look these in particular:
http://susestudio.com/a/LZOHnh/rudis-mono-appliance
http://susestudio.com/a/O6ALub/opensuse-114-gnome3-with-monodevelop
Depending on your need, you could also create your own spin of openSUSE, adding the xamarin rpm repo in the webclient and have SUSE studio built it for you.
I have installed a fresh install of XWiki on a Windows platform.
The XWiki instance was installed using hsql for data storage.
The XWiki instance is hosted on Apache Tomcat.
Some of my users entered an apostrophe into the title of a page as well as the page content.
I received the following error:
http://jira.xwiki.org/jira/browse/XE-767
What is my next step to fix my broken XWiki instance?
Is there a way to upgrade a XWiki instance to a version that works? How do I save my existing content?
From reviewing the developers comments, it appears that issue has been corrected.
I, however, do not have enough background in Java or XWiki to know how I can move forward.
Thank you in advance for your help.
Indeed, the best solution is to upgrade to a newer version. Don't worry, upgrades are not that difficult.
http://platform.xwiki.org/xwiki/bin/AdminGuide/Installation#HUpgradinganXWikiInstallation
There are two parts in an upgrade: the platform, meaning all the files on the filesystem, and the wiki content, since quite often things change in the default wiki documents. Your specific bug can be fixed by upgrading the platform part, so if you're not too confident about upgrading the wiki content, you can just leave the old content in place.
In order not to lose your current database, be sure to leave the old "database" folder in place, and just replace the "webapps\xwiki" part.
From the error report the versions that fix the issue are
2.7 - http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterprise27
2.6.1 - http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterprise261
You can upgrade to one of them or to any following version, like XE
3.0 - http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterprise30
All versions can be downloaded from http://forge.ow2.org/project/showfiles.php?group_id=170
In a project that has such a rapid development cycle is very good to upgrade often in order to benefit from the latest features and bug fixes.