Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture.
The decision means that February ISO will be the last that allows to install 32 bit Arch Linux. The next 9 months are deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging and repository tools will no longer require that from maintainers, effectively making i686 unsupported.
However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. The arch-ports mailing list and #archlinux-ports IRC channel on Freenode will be used for further coordination.
The [multilib] repository will not be affected by this change.
mesa-17.0.0-3 can now be installed side-by-side with
nvidia-378.13 driver without any libgl/libglx hacks, and with the help of Fedora and upstream xorg-server patches.
First step was to remove the libglx symlinks with xorg-server-1.19.1-3 and associated mesa/nvidia drivers through the removal of various libgl packages. It was a tough moment because it was breaking optimus system,
xorg-server configuration needs manual updating.
The second step is now here, with an updated 10-nvidia-drm-outputclass.conf file that should help to have an "out-of-the-box" working
xorg-server experience with optimus system.
The upgrade to ca-certificates-utils 20170307-1 requires manual intervention because a symlink which used to be generated post-install has been moved into the package proper.
As deleting the symlink may leave you unable to download packages, perform this upgrade in three steps:
# pacman -Syuw # download packages # rm /etc/ssl/certs/ca-certificates.crt # remove conflicting file # pacman -Su # perform upgrade
Due to high maintenance cost of scripts related to the Arch Build
System, we have decided to deprecate the
abs tool and thus rsync
as a way of obtaining PKGBUILDs.
asp tool, available in [extra], provides similar functionality to
asp export pkgname can be used as direct alternative; more
information about its usage can be found in the documentation.
Additionally Subversion sparse checkouts, as described here, can
be used to achieve a similar effect. For fetching all PKGBUILDs, the
best way is cloning the svntogit mirrors.
extra/abs package has been already dropped, the rsync
endpoint (rsync://rsync.archlinux.org/abs) will be disabled by the end
of the month.
The perl package now uses a versioned path for compiled modules. This means that modules built for a non-matching perl version will not be loaded any more and must be rebuilt.
A pacman hook warns about affected modules during the upgrade by showing output like this:
WARNING: '/usr/lib/perl5/vendor_perl' contains data from at least 143 packages which will NOT be used by the installed perl interpreter. -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/vendor_perl'
You must rebuild all affected packages against the new perl package before you can use them again. The change also affects modules installed directly via CPAN. Rebuilding will also be necessary again with future major perl updates like 5.28 and 5.30.
Please note that rebuilding was already required for major updates prior to this change, however now perl will no longer try to load the modules and then fail in strange ways.
If the build system of some software does not detect the change automatically,
you can use
perl -V:vendorarch in your PKGBUILD to query perl for the
correct path. There is also
sitearch for software that is not packaged with
Following 9 months of deprecation period, support for the i686 architecture effectively ends today. By the end of November, i686 packages will be removed from our mirrors and later from the packages archive. The [multilib] repository is not affected.
For users unable to upgrade their hardware to x86_64, an alternative is a community maintained fork named Arch Linux 32. See their website for details on migrating existing installations.
The zita-resampler 1.6.0-1 package was missing a library symlink that has been readded in 1.6.0-2. If you installed 1.6.0-1, ldconfig would have created this symlink at install time, and it will conflict with the one included in 1.6.0-2. In that case, remove /usr/lib/libzita-resampler.so.1 manually before updating.
The new version of glibc removes support for NIS and NIS+. The default
/etc/nsswitch.conf file provided by
filesystem package already
reflects this change. Please make sure to merge pacnew file if it exists
prior to upgrade.
NIS functionality can still be enabled by installing
package. There is no replacement for NIS+ in the official repositories.
pam 1.3.0-2 no longer ships pam_unix2 module and
compatibility symlinks. Before upgrading, review PAM configuration files
/etc/pam.d directory and replace removed modules with
pam_unix.so. Users of pam_unix2 should also reset their passwords
after such change. Defaults provided by
pambase package do not need
Due to the SONAME of
/usr/lib/libmozjs-52.so not matching its file name, ldconfig created an untracked file
/usr/lib/libmozjs-52.so.0. This is now fixed and both files are present in the package.
To pass the upgrade, remove
/usr/lib/libmozjs-52.so.0 prior to upgrading.
The libutf8proc package prior to version 2.1.1-3 had an incorrect soname link. This has been fixed in 2.1.1-3, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error
libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem
when updating, use
pacman -Suy --overwrite usr/lib/libutf8proc.so.2
to perform the upgrade.
Today is the official launch day of Astro Pi Mission Zero, part of the 2018–2019 European Astro Pi Challenge, an ESA Education programme run in collaboration with us at Raspberry Pi. In this challenge, students and young people get the chance to have their computer programs run in space on the International Space Station!
Students and young people will have until 20 March 2019 to form teams and write a simple program to display their personal message to the astronauts onboard. The Mission Zero activity can be completed in a couple of hours with just a computer and an internet connection. You don’t need any special equipment or prior coding skills, and all participants that follow the guidelines are guaranteed to have their programs run in space.
This year, to help many more people take part in their native language, we have translated the Mission Zero resource, guidelines, and web page into 19 different languages! Head to our languages section to find your version of Mission Zero.
To participate, the teams’ teacher or mentor needs to register for a classroom code that will let students submit their programs. Teams then follow our online resource to write their programs using the browser-based Trinket emulator: with just a few lines of Python, your team will create a program for one of the two Astro Pi computers aboard the ISS!
Each team’s program will run for 30 seconds aboard the Space Station, visible for all the astronauts including this year’s challenge ambassadors: ESA astronaut and ISS Commander Alexander Gerst and CSA astronaut David Saint-Jacques.
Ever wanted to run your own experiment in space? Then you’re in luck! ESA Education, in collaboration with the Raspberry Pi Foundation, is pleased to announce the launch of the 2018/2019 European Astro Pi Challenge!
Every team that submits a valid Mission Zero entry will also receive a certificate showing the flight path of the ISS above Earth at the exact time their code ran!
The challenge is open to teams of students and young people who are aged 14 years or younger (at the time of submission) and from ESA Member or Associate Member States*. The teams must have at least two and no more than four members, and they must be supervised by an adult teacher or mentor.
Have fun, and say hi to the astronauts from us!
The European Astro Pi Challenge is an ESA Education project run in collaboration with the Raspberry Pi Foundation. It offers students and young people the amazing opportunity to conduct scientific investigations in space by writing computer programs that run on Raspberry Pi computers on board the International Space Station (ISS). The Astro Pi Challenge is divided into two separate missions with different levels of complexity: Mission Zero (the basic mission), and Mission Space Lab (one step further). This year’s Mission Space Lab is closing for applications at the end of October. Click here for more information about it.
*ESA Member States in 2018:
Austria, Belgium, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Luxembourg, The Netherlands, Norway, Poland, Portugal, Romania, Spain, Sweden, Switzerland, United Kingdom.
ESA Associate States in 2018: Canada, Slovenia
In the framework of the current collaboration agreement between ESA and the Republic of Malta, teams from Malta can also participate in the European Astro Pi Challenge. ESA will also accept entries from primary or secondary schools located outside an ESA Member or Associate State only if such schools are officially authorised and/or certified by the official Education authorities of an ESA Member or Associate State (for instance, French school outside Europe officially recognised by the French Ministry of Education or delegated authority).
The post Astro Pi Mission Zero: guarantee your code’s place in space appeared first on Raspberry Pi.
Apologies to our daily visitors (we love you guys); we don’t have a proper blog post for you today because we’re all really ill. (I have food poisoning, Helen is coughing up goo and can barely speak or breathe, and Alex is being sick.)
You’ve got a day until Halloween; if you’re looking for inspiration, we’ve got several years of archived spooky project posts for you to check out. And now, if you’ll excuse me, I’m going to go and have a little lie down.
I’ll keep today’s blog post short and sweet, because Liz, Helen, and I are all still under the weather.
Don’t tell Eben, Liz, or the rest of the team I showed you this, but here’s your Halloween ‘trick or treat’ gift: an exclusive sneak peek at the Raspberry Pi 4.
We’ll be back to our regularly scheduled programming from tomorrow.
FreeBSD is a free and open source operating system for many different kinds of computers. FreeBSD's based upon BSD, the version of UNIX developed at the University of California, Berkeley. FreeBSD is an alternative to Linux or Windows-based system. You can run almost all apps written in Perl, Python, PHP and other programming languages. FreeBSD heavily used by Netflix, EMC, IBM, Juniper, NetApp, Apple, Sony, and others. Absolute FreeBSD (3rd ed) book aims to be the complete guide to FreeBSD. Let us see why Michael W. Lucas' FreeBSD system administration books so favorite among Unix lovers.