GNOME 3.4beta2 is available in [gnome-unstable] repository. To use this version you need to enable [gnome-unstable] repository, as top repository to pacman.conf, along with [testing] repository.

[gnome-unstable]
Include = /etc/pacman.d/mirrorlist
[testing]
Include = /etc/pacman.d/mirrorlist
[core]
...

Have fun testing these packages. Like always packaging bugs should be reported on our bugtracker, anything else considered bugs should be reported to GNOME bugzilla. Before reporting an upstream bug, be sure you search first on bugzilla in the appropriate project. I keep track on bugs discovered by our community on this todo list.
If you report an issue, please let me know to add it on my todo list.

Let me start with a quick joke that I saw on reddit:

Q:How do you know that somebody runs Arch?

A: They will tell you…

Now, let me tell you my Arch history.  I tried it for the fist time back in 2005 when somebody from university used it while teaching about operating systems. It didn’t stayed more than 1 hour on my computer because it didn’t had any GUI and I didn’t read anything about installation (go figure).  After using gentoo for about a year and getting angry for compiling 6 hours my system because I broke it, my good friend cippp, who used Arch and was a contributor, pushed me to start using Arch. This time I read the wiki before installing for about a week and since 2006 I’m a happy Arch user.

Here is a brief summary of my involvement with Arch Linux:

• 2006-07-05 – registered on forums
• 2009-04-04 – applied to became a TU because some packages that Allan had are not maintained anymore
• 2009-04-18 -  I’m a TU now (17 yes, 0 no, 0 abstain)
• 2009-07-03 – I launched Arch Linux Romania
• 2009-10-31 – I was invited to became a developer by JGC because I maintained telepathy and empathy in community
• 2009-11-04 – FS#16922, first contribution as developer
• 2010-01-21 -  firefox 3.6 was out and I’m the new Mozilla guy
• 2010-03-09 – GNOME 2.30 was released and it was my first time doing GNOME. At that time i wasn’t prepared at all to be the new GNOME maintainer. Somebody screwed me over!
• 2011-03-15 – resigned as TU
• 2011-04-30 – GNOME 3.0 moves in extra. This was my biggest challenge ever and the most controversial move. We were the first distro to push the major version to users. I don’t want to remember the flames…

This are the moments that I’m most proud along with a lot of trolling in the #archlinux @ freenode channel

I’m glad that I’m a part of this community,  I saw it grow from being a hipster distribution to a mainstream one, I helped growing Arch.  What is really incredible how we managed to still keep the same principles as it were laid down by Judd. Is nice to hear from time to time that people really appreciate our work.

Adobe are you crazy?! With this move you are dropping the availability of flashplugin, from a lot of browsers to only ONE(ahem Chrome), browser that cannot be distributed in linux distributions.

As a package maintainer I have some wishes:
1) ADOBE GO TO HELL
2) MOZILLA please step out and add this new, crazy Pepper API since flash is not going anywhere.
3) GOOGLE please do proper releases of flashplugin that can be downloaded and packaged nicely in linux distributions and NOT only as bundled in your Chrome browser. You do know that you have Chromium right?
4) Companies please adopt HTML5 video, clearly Adobe wants to ditch flash.

I’m starting with explaining first why is breaking. It does it because our users have full control over their systems and they customize it in any possible and impossible ways.

I’m a developer and a contributor in Arch Linux for about 3 years and an arch user for about 6 years now and I noticed that the number one reason for “arghh updates screwed up my system”, is replacing important stock packages with unsupported ones. With unsupported, I mean, mostly builds from AUR, but it can include 3rd party repositories that cannot keep up with us. (yes, i’m looking at you archlinuxfr )

So what can you do to increase your system stability?

1. Always read the news entries, subscribe to the rss feed, arch-announce mailing list
2. Know your system more. If I’m replacing a stock package, I know that I have to take care of it if a news entry specifies something.
3. Don’t use 3rd party repos and always install packages from AUR using makepkg manually. This allows you to know your system better and yaourt and other scripts that “helps” you, in fact does a lot of disservice.
4. Always do pacman -Syu and never use -f along with it.

Behold, the greatest era in Arch Linux trolling history has now ended. pacman 4.0 was released last night having package signing.

What’s next? Is there something out there, so powerful, that can be compared with package signing trolls?

As promised multiple times on forums, GNOME 3.2 beta2 was just released and guess what? We got it! Shinier and full of new features, noticeable are gdm’s brand new look, gnome-online-accounts, gnome-contacts, gnome-documents, epiphany web application support, new user menu and better chat integration. Along with that, nautilus received a new file previewer named sushi, feature that I like the most.

To use this new version you need to enable gnome-unstable repository, as top repository to pacman.conf:

[gnome-unstable]
Include = /etc/pacman.d/mirrorlist

Have fun testing these packages. Like always packaging bugs should be reported on our bugtracker, anything else considered bugs should be reported to GNOME bugzilla.

NVIDIA users be aware that xorg-server 1.11 from testing is incompatible with the current nvidia driver, even with IgnoreABI. You can switch to nouveau or add xf86-input-evdev xf86-input-synaptics xorg-server-common xorg-server to Ignorepkg.

Discuss this repo on our forums.

With me in the #archlinux-tu channel was td123, Bluewind, louipc, CryptoCrack, teiresias, schuay and we started to talk about the show, doing bets and live commenting about what is happening. I said that they would bitch a lot about our python move and in general about our distribution.

Usually i anticipate very well the community reaction but this time i was wrong. Epic fail.

Instead Bryan and Chris  gave us a positive feedback and it seems, we, developers and trusted users, do a pretty damn good job.

Show notes and video

Youtube

P.S: You know what, stop, don’t use arch!

Recently five new TUs were joining us!

• Brad Fanella (itsbrad212) from the US, sponsored by Chris Brannon
• Florian Pritz (bluewind), from Austria, sponsored by Thorsten Töpper
• Lukáš Jirkovský (stativ), from Czech Republic, sponsored by Thomas Dziedzic
• Jonathan Conder (PirateJonno), from New Zealand, sponsored by Ionuț Bîru
• Jakob Gruber (schuay), from Austria, sponsored by Laurent Carlier

We give you a warm welcome and wish you to have fun in our team.

A multilib toolchain that supports both the 32bit (x86) and 64bit (x86_64) formats. This was the only requirement that we missed until now.

pacman -S virtualbox-ose

P.S for all users that are using  my unofficial vbox repo, i suggest to remove it from your pacman.conf because i would shutdown it in the next days.

So what happens in a bug day? We join #archlinux-bugs@Freenode and we work together on bugs submitted on our tracker, trying to see if is still valid, writing builds, searching patches and building packages.

Thanks to td123 (he’s our new TU member) who requested to do this action and doing a lot of work in community project, angvp (our new dev member) who did his first contributions in the main repository, Bluewind for directing and building packages along with us, keenerd making a bot that announce all kind of actions about bugs(opening, closing, edit) and everybody else who participated.

We ended up with something like this: