If you'd like to join, there's a number of free tickets available. Go to this website to register and use the code WELOVEOWNCLOUD.
See you there!
This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.
To have your blog added to this aggregator, please read the instructions.
Note that you may use those keys with or without pressing the alt key.
The wait is over, the report of the latest Scrum sprint of the YaST Team is here! In the previous post we promised that after this sprint we would have much more to show… and now we do. This sprint was quite productive, so let’s go straight to the most interesting bits.
At this gist (with screenshots) you can see some of the fixes done when going back and forward in the work-flow after an installer self-update.
But even more important are the improvements done in AutoYaST to properly handle the new feature. If you want to use your own self-update repository you have to specify it on the boot command line. This is easy in a single installation, but if you want to install many machines using AutoYaST then writing the possibly long URL at each installation again sounds annoying.
In this sprint we improved handling of the custom update URL so that it can be read from the AutoYaST XML profile. Now you need to write the custom URL only once into the profile and it will be used automatically in every AutoYaST installation.
There is not much to show in the UI, the log proves that the self update was really loaded.
You can find more details about specifying the URL in the profile and evaluating the self-update repository URL at the documentation.
For quite some time, we have had the plan to stop using Perl-Bootloader as library for yast2-Bootloader and finally we managed to make it happen. There were many reasons for this change.
From the user point of view, the most visible reasons were speed and size. Getting rid of Perl-Bootloader means that we not longer perform hardware probing twice (one for Perl-Bootloader and another one for
grub2-config), making kernel updates faster. In addition, we are not only simplifying and reducing the size of yast2-bootloader itself. Dropping the Perl libraries and other associated dependencies, makes possible to have a smaller minimal system, something quite relevant in various environments and scenarios.
From the developer point of view, the main reason was to unify the used programming languages and also reuse existing solution for file reading and parsing. Now yast2-bootloader uses an Augeas file parser and serializer, which does not only allow us to have less code to maintain, but also offers smarter editing and better handling of the comments in the configuration files.
As nice side effects, this change also leaded to the removal of a lot of work-arounds, the simplification of the installation work-flow for bootloader and a very visible improvement in the source code quality. In addition, we improved the test coverage of the whole module to make sure we didn’t break things too much. But all those would be bold statements if we wouldn’t have some geeky numbers to prove …
The first round of proposals for the openSUSE Conference have been accepted and people who submitted a call for papers should log-in to events.opensuse.org and check to see if their talk has been accepted as part of the first round of proposals.
For proposals that have been accepted, users should confirm their proposal as soon as possible and also register for the conference if they had not done so already.
About 20 proposals have been confirmed, but there are about 45 proposals from the first round proposals that need to be confirmed.
There will be a second round of accepted proposals announced next week.
A new version of Danbooru Client is now available!
Danbooru Client is an application to access Danbooru-based image boards (Wikipedia definition).
It offers a convenient, KF5 and Qt5-based GUI coupled with a QML image view to browse, view, and download images hosted in two of the most famous Danbooru boards (konachan.com and yande.re).
Sooner or later I’ll get to finish the multiple API support, but given that there’s close to no interest for these programs (people are happy to use a browser) and that I work on this very irregularly (every 6-7 months at best), there’s no ETA at all. It might be done this year, perhaps the next.
Currently, there is only a source tarball. For security, I have signed it with my public GPG key (A29D259B) and I have also provided a SHA-512 hash of the release.
A new snapshot of Tumbleweed arrived today and the reason for not having one the past week is that the entire rolling release distribution was rebuilt on the Open Build Service and thoroughly tested by openQA.
Snapshot 20160422 updated glibc to version 2.23 and libvirt to 1.3.3. The libraries provide new compatibility and remove some obsolete functions. Several patches were removed from glibc and libvirt. Libvirt’s update also improved support for ppc64.
GCC 5 upgraded to version 5.3.1+r234891 and kernel-firmware updated to 20160412.
Php7 has been added and is available in the the repositories.
Other updates of interest are to openssl with new patches from SUSE Linux Enterprise 12 and cmake 3.5.2. YaST had several updates with yast2 upgrading to 3.1.185, yast2-vm upgrading to 3.1.26, and yast2-bootloader upgrading to 3.1.176 among others YaST updates.
The openSUSE Board announced today a call to action for a Community Release Team to assist with tasks associated to the development of the next Leap version 42.2.
The announcement was made in an email to the project’s development mailing list opensuse-factory (at) opensuse.org.
“In the past, these tasks were… distributed among the SUSE employed openSUSE team, which tried to incorporate community and in the end made sure that everything gets done,” wrote Tomáš Chvátal, a newly elected board member.
Contributors can help Leap’s new release manager Ludwig Nussel with a variety of tasks associated with the development of 42.2, but the opportunities for contributing are more than just development.
“We would like the community to be directly responsible for ensuring these tasks get carried out,” Chvátal wrote. “To accomplish this we intend to create a full team of people taking care about what needs to be done for the release. We expect the people in this Community Release Team to be the ones responsible for the tasks in their respective areas of responsibility.”
The tasks are split into several areas like marketing, design, infrastructure, documentation, translations and quality assurance.
Tasks for marketing include creating and following a marketing plan and taking care of social media among other things. Design tasks include making sure the desktops are consistently branded and the the look and feel is consistent. Infrastructure tasks include making sure critical infrastructure works.
The documentation tasks include updating content on the wiki and ensuring release notes are updated. Translations for 42.2 will be needed and QA tasks include creating a test plan for milestones, monitoring bugzilla and escalating important regressions to the release manager.
People interested in joining the Community Release Team should contact the board and Nussel.
A link to the action items from the last release can be found at http://tinyurl.com/grg5szf and volunteers are welcomed to expand the tasks.
Going back to faster release cycle, Weblate 2.6 has been just released. There is improved support for Python 3 or brand new HTTP REST API.
Full list of changes for 2.6:
If you are upgrading from older version, please follow our upgrading instructions.
You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with
demo account using
demo password or register your own user. Weblate is also being used https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Aptoide, FreedomBox, Weblate itself and many other projects.
Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.
Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.
For most documents about kernel module building just need a Makefile like this,
HELLO = helloworld
obj-m += $(HELLO).o
$(HELLO)-objs := hello.o world.o
KERNEL_SOURCE := /lib/modules/`uname -r`/build/
$(MAKE) -C $(KERNEL_SOURCE) M=`pwd` modules
$(MAKE) -C $(KERNEL_SOURCE) M=`pwd` clean
$(RM) Module.markers modules.order
Then type “make” will make everything set. (Of cause source of current kernel is ready at /lib/modules/`uname -r`/build).
But yesterday when I tried to build a kernel module for Linux-4.6-rc5 (openSUSE vanilla) kernel, I observed an error never saw before.
make -C /lib/modules/`uname -r`/build/ M=`pwd` modules
make: Entering directory ‘/home/colyli/source/suse-kernel/patched/linux-4.6-rc5-vanilla’
make: *** No rule to make target ‘/home/colyli/source/tmp/helloworld/hello.o’, needed by ‘/home/colyli/source/tmp/helloworld/helloworld.o’. Stop.
Makefile:1428: recipe for target ‘_module_/home/colyli/source/tmp/helloworld’ failed
make: *** [_module_/home/colyli/source/tmp/helloworld] Error 2
make: Leaving directory ‘/home/colyli/source/suse-kernel/patched/linux-4.6-rc5-vanilla’
Makefile:10: recipe for target ‘default’ failed
make: *** [default] Error 2
It seems nothing missed, but the error message was there. Today a friend (Chang Liu from Memblaze) tells me maybe I should check the output of “make modules_prepare” in the kernel source directory, here is my result,
linux-4.6-rc5-vanilla> make modules_prepare
Makefile:1016: “Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev or elfutils-libelf-devel”
This is an informative clue, so I install libelf-dev package and re-run “make modules_prepare”,
linux-4.6-rc5-vanilla> make modules_prepare
CC /home/colyli/source/suse-kernel/patched/linux-4.6-rc5-vanilla/tools/objtool/elf …
This is a question raised quite quite often, the last time in a blogpost by Thomas, so I thought it is a good idea to give a slightly longer explanation (and also create an article to link to…).
There are basically three reasons for using XML as the default format for metainfo files:
This is a matter of extending the AppStream metainfo files with new entries, or adapt existing entries to new needs.
Take this example XML line for defining an icon for an application:
and now the equivalent YAML:
Icons: cached: foobar.png
Now consider we want to add a width and height property to the icons, because we started to allow more than one icon size. Easy for the XML:
<icon type="cached" width="128" height="128">foobar.png</icon>
This line of XML can be read correctly by both old parsers, which will just see the icon as before without reading the size information, and new parsers, which can make use of the additional information if they want. The change is both forward and backward compatible.
This looks differently with the YAML file. The “foobar.png” is a string-type, and parsers will expect a string as value for the
cached key, while we would need a dictionary there to include the additional width/height information:
Icons: cached: name: foobar.png width: 128 height: 128
The change shown above will break existing parsers though. Of course, we could add a
cached2 key, but that would require people to write two entries, to keep compatibility with older parsers:
Icons: cached: foobar.png cached2: name: foobar.png width: 128 height: 128
Less than ideal.
While there are ways to break compatibility in XML documents too, as well as ways to design YAML documents in a way which minimizes the risk of breaking compatibility later, keeping the format future-proof is far easier with XML compared to YAML (and sometimes simply not possible with YAML documents). This makes XML a good choice for this usecase, since we can not do transitions with thousands of independent upstream projects easily, and need to care about backwards compatibility.
A property of AppStream metainfo files is that they can be easily translated into multiple languages. For that, tools like intltool and itstool exist to aid with translating XML using Gettext files. This can be done at project build-time, keeping a clean, minimal XML file, or before, storing the translated strings directly in the XML document. Generally, YAML files can be translated too. Take the following example (shamelessly copied from Dolphin):
<summary>File Manager</summary> <summary xml:lang="bs">Upravitelj datoteka</summary> <summary xml:lang="cs">Správce souborů</summary> <summary xml:lang="da">Filhåndtering</summary>
This would become something like this in YAML:
Summary: C: File Manager bs: Upravitelj datoteka cs: Správce souborů da: Filhåndtering
Looks manageable, right? Now …
Two weeks ago was the GNOME Software hackfest in London, and I’ve been there! And I just now found the time to blog about it, but better do it late than never .
After being stuck in trains for the weekend, but fortunately arriving at the airport in time, I finally made it to London with quite some delay due to the slow bus transfer from Stansted Airport. After finding the hotel, the next issue was to get food and a place which accepted my credit card, which was surprisingly hard – in defence of London I must say though, that it was a Sunday, 7 p.m. and my card is somewhat special (in Canada, it managed to crash some card readers, so they needed a hard-reset). While searching for food, I also found the Red Hat offices where the hackfest was starting the next day by accident. My hotel, the office and the tower bridge were really close, which was awesome! I have been to London in 2008 the last time, and only for a day, so being that close to the city center was great. The hackfest didn’t leave any time to visit the city much, but by being close to the center, one could hardly avoid the “London experience” .
That’s basically the summary for the hackfest . It was awesome to meet with Richard Hughes again, since we haven’t seen each other in person since 2011, but work on lots of stuff together. This was especially important, since we managed to solve quite some disagreements we had over stuff – Richard even almost managed to make me give in to adding <kudos/> to the AppStream spec, something which I was pretty against supporting (it didn’t make it yet, but I am no longer against the idea of having that – the remaining issues are solvable).
Meeting Iain Lane again (after FOSDEM) was also very nice, and also seeing other people I’ve only worked with over IRC or bug reports (e.g. William, Kalev, …) was great. Also lots of “new” people were there, like guys from Endless, who build their low-budget computer for developing/emerging countries on top of GNOME and Linux technologies. It’s pretty cool stuff they do, you should check out their website! (they also build their distribution on top of Debian, which is even more awesome, and something I didn’t know before (because many Endless people I met before were associated with GNOME or Fedora, I kind of implicitly assumed the system was based on Fedora )).
The incarnation of GNOME Software used by endless looks pretty different from what the normal GNOME user sees, since it’s adjusted for a different audience and input method. But it looks great, and is a good example for how versatile GS already is! And for upstream GNOME, we’ve seen some pretty great mockups done by Endless too – I …
Google made an announcement April 22 that 1,206 students were selected for the Google Summer of Code and six of those students will be mentored through the openSUSE Project, which is one of 178 mentoring organizations in this year’s GSoC.
The six university students will spend their summer break writing code and learning about open source developments through six projects with the openSUSE Project while earning money through Google’s international program.
“I believe that one of the most important tasks for a Free Software hacker is to bring new people with new perspectives, backgrounds and fresh ideas into the community,” said Hendrik Vogelsang, who is one of the mentors for the openSUSE Project. “GSoC provides the perfect opportunity for a project like openSUSE to build new relationships with students from all over the world.”
Those new relationships and fresh ideas will develop within six projects for openSUSE, which are titled Alternatives YaST Module, Enhancing visitor experience of OSEM, Implementing Ticket payment feature for OSEM, Improve One-Click Installer, Improve the UI of Portus and Port Jangouts from AngularJS 1.4.
Students wrote more than 20 project proposals to participate with openSUSE as a mentoring organization. A list of available project that were available to students can be viewed at 101.opensuse.org.
The next phase of GSoC will be the Community Bonding phase and the students will begin working on the projects May 23. The students will have a mid-term evaluation between June 20 – 27 and will submit their code for evaluation between August 15 -23.
Google Summer of Code is open to post-secondary students, age 18 and older in most countries.
I recently learned about VulnHub, a site where you can download and attack some demo machines that others have shared. It is very useful if you are looking to learn about security or advance your existing skills. In this post I was targeting the LAMPSecurity: CTF6 machine. Setup is pretty simple, I downloaded the VM, converted it into qcow2 format and then fired it up with kvm.
To start off I wanted to see what ports and services are running so I decided to run a scan to see if I could get more information.
The first issue is that the machine uses a DHCP so I need to determine its ip address.
# nmap -sP 192.168.1.0/24 Starting Nmap 7.12 ( https://nmap.org ) at 2016-04-22 21:03 EDT Nmap scan report for 192.168.1.211 Host is up (0.00011s latency). MAC Address: 52:54:00:2E:EF:25 (QEMU virtual NIC) Nmap scan report for 192.168.1.1 Host is up. Nmap done: 256 IP addresses (2 hosts up) scanned in 6.38 seconds
Now I know the IP of the gateway is 192.168.1.1 so the IP address of the target machine is 192.168.1.211. Now that I know that I can perform a scan on the ports to see what is open.
# nmap -sS -sV 192.168.1.211 Nmap scan report for 192.168.1.211 Host is up (0.00013s latency). Not shown: 991 closed ports PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 4.3 (protocol 2.0) 80/tcp open http Apache httpd 2.2.3 ((CentOS)) 110/tcp open pop3 Dovecot pop3d 111/tcp open rpcbind 2 (RPC #100000) 143/tcp open imap Dovecot imapd 443/tcp open ssl/http Apache httpd 2.2.3 ((CentOS)) 993/tcp open ssl/imap Dovecot imapd 995/tcp open ssl/pop3 Dovecot pop3d 3306/tcp open mysql MySQL 5.0.45 MAC Address: 52:54:00:2E:EF:25 (QEMU virtual NIC)
The website seems to have Apache running so I decided to try scanning it with nikto to see if there are any interesting pages avaliable.
# nikto -h http://192.168.1.211/ - Nikto v2.1.6 --------------------------------------------------------------------------- + Target IP: 192.168.1.211 + Target Hostname: 192.168.1.211 + Target Port: 80 + Start Time: 2016-04-22 21:25:05 (GMT-4) --------------------------------------------------------------------------- + Server: Apache/2.2.3 (CentOS) + Cookie PHPSESSID created without the httponly flag + Retrieved x-powered-by header: PHP/5.2.6 + The anti-clickjacking X-Frame-Options header is not present. + The X-XSS-Protection header is not defined. This header can hint to the user agent to protect against some forms of XSS + The X-Content-Type-Options header is not set. This could allow the user agent to render the content of the site in a different fashion to the MIME type + Apache/2.2.3 appears to be outdated (current is at least Apache/2.4.12). Apache 2.0.65 (final release) and 2.2.29 …
Dear Tumbleweed users and hackers,
Tumbleweed seems to have found its rhythm at around 4 snapshots per week. I will cover the snapshots 0414, 0415, 0416 and 0417. After that, it took unfortunately a bit of effort to get more stagings ready. This then lead now to the fact that the next snapshot (0422) will be rather large. I will mention more about this further down.
What were the 4 last snapshots about:
The next snapshot (20160422) will be rather large and quite some packages will have new release numbers. Glibc 2.23 finally found its way through staging, which was the perfect time to change OBS to do a full rebuild of the distribution, ensuring all packages are again built against each other. Further, we disabled the support script that “removed the .desktop file translations in favor of gettext based language overlays”. Even though this was an interesting feature, it lead to quite some issues in the past with the fast pace of Tumbleweed. Sometimes upstream shipped a .desktop file with correct translations, but we stripped those ‘in favor of our own’ (which often were based on older strings). No longer doing this means eliminating all kind of such issues. But it was another reason for full package rebuilds. In an attempt to minimize how often we trigger such large updates, we scheduled this intentionally together with the glibc update.
There are still a couple of things prepared in staging, most notably:
Let’s all work on all those great additions and many more
This morning I could not launch SMPlayer as it would complain about a ‘relocation error’.
smplayer: relocation error: /usr/lib64/samba/libauthkrb5-samba4.so: symbol tevent_req_is_unix_error, version TEVENT_UTIL_0.0.1 not defined in file libtevent-util.so.0 with link time reference
It’s been quite a few days I did not use SMPlayer and somehow a recent update of Tumbleweed could have updated that Samba library. Yes, it comes from the samba-libs package.
ish@coffee-bar:~> rpm -qf /usr/lib64/samba/libauthkrb5-samba4.so samba-libs-4.4.2-1.1.x86_64
I ran the above command when writing this blog post, which was after a Samba update. Therefore I guess a previous version of the samba-libs was behind the apps-breaking incident. Yup! SMPlayer would work just fine after the update. Reading from the openSUSE forums, a couple of days ago other geekos complained about some items failing to launch after Tumbleweed update.
— Ish Sookun (@IshSookun) April 22, 2016
Ideally, one could run
zypper up to update the system rather than just the Samba package.
There are no good, paper cycling maps for my region. There are 1:20,000 street maps for car navigation within the city, but they have absolutely no detail in the rural areas. There are 1:200,000 maps for long trips by car, but that's too big of a scale.
Ideally there would be high-quality printed maps at 1:50,000 scale (i.e. 1 Km in the real world is 2 cm in the map), with enough detail and some features:
Contour lines. Xalapa is in the middle of the mountains, so it's useful to plan for (often ridiculously steep) uphills/downhills.
Where can I replenish my water/food? Convenience stores, roadside food stands.
What's the quality and surface of the roads? This region is full of rural tracks that go through coffee and sugarcane plantations. The most-transited tracks can be ridden with reasonable "street" tyres. Others require fatter tyres, or a lot of skill, or a mountain bike, as they have rocks and roots and lots of fist-sized debris.
Any interesting sights or places? It's nice to have a visual "prize" when you reach your destination, apart from the mountainous landscape itself. Any good viewpoints? Interesting ruins? Waterfalls?
As many references as possible. The rural roads tend to look all the same — coffee plants, bananas, sugarcane, dirt roads. Is there an especially big tree at the junction of two trails so you know when to turn? Is there one of the ubiquitous roadside shrines or crosses? Did I just see the high-voltage power lines overhead?
For a couple of years now, I have been mapping the rural roads around here in OpenStreetMap. This has been an interesting process.
For example, this is the satellite view that gets shown in iD, the web editor for OpenStreetMap:
One can make out rural roads there between fields (here, between the blue river and the yellow highway). They are hard to see where there are many trees, and sometimes they just disappear in the foliage. When these roads are just not visible or 100% unambiguous in the satellite view, there's little else to do but go out and actually ride them while recording a GPS track with my phone.
These are two typical rural roads here:
Once I get back home, I'll load the GPS track in the OpenStreetMap editor, trace the roads, and add some things by inference (the road crosses a stream, so there must be a bridge) or by memory (oh, I remember that especially pretty stone bridge!). Behold, a bridge in an unpaved road:
The openSUSE Conference in Nuremberg, Germany, June 22 – 26 is just nine weeks away and attendee might want to start planning their trip to this year’s conference.
With a pre-conference party planned for June 21 at the Kater Murr at 7 p.m., attendees might want to consider arriving on June 21; arriving a day before the conference is a good idea.
The conference will begin at 10 a.m. on June 22, which should give people time to recovery either jet lag or the pre-conference party.
People who take the train will arrive in downtown Nuremberg. People coming in on a flight can go downtown using the subway (U-Bahn) from the airport. U2 is the train that goes too and from downtown (Hauptbahnhof).
People who plan on driving to Nuremberg will find plenty of parking garages around the city. Parking at the Z Bau is free.
People who plan on using the Travel Support Program can start submitting their requests now via Connect and need to have it submitted six weeks before the start of oSC16. (May 9 at the latest).
Learn more about the Travel Support Program and be informed of the policies to make your process easy and to understand the requirements for receiving support funds.
Attendees should look for the cheapest tickets available so that the funds can be used to accommodate the largest amount of attendees requesting support.
Besides the pre-conference party, there will be a couple social events scheduled throughout the week.
There will be a city tour and a cellar tour available in Nuremberg at two different times (6:30 p.m. and 8 p.m.) on June 22, 23 and 25. Each tour has the capacity of 25 people and people who want to attend these tours will need to reserve a seat through events.opensuse.org. Reserving a seat for the tours is not currently available, but will be before the conference starts; an announcement will be sent out to attendees about reserving a seat.
The SUSE Band will play live music on stage at the Z Bau June 24 from 6:45 p.m. The band has been practicing for this for some time is hyped to be playing in front of a live audience.
The conference is scheduled to end at 2 p.m. on June 26 so attendees can have enough time to get to the airport for a flight leaving at 5 p.m. or later. There are several flights leaving Nuremberg after 5 p.m. Three hours is more than enough time to get to the airport from the Z Bau. Using public transportation takes a little under 30 minutes from the Z Bau to Nuremberg Airport.
There will be a Hack Week for those who would like to stay and hack in Nuremberg. Give it some thought before making travel plans and maybe stay a few days to hack with people at the SUSE headquarters in Nuremberg.