Gnome unstable arch linux

Official repositories

A software repository is a storage location from which software packages are retrieved for installation.

Arch Linux official repositories contain essential and popular software, readily accessible via pacman. They are maintained by package maintainers.

Packages in the official repositories are constantly upgraded: when a package is upgraded, its old version is removed from the repository. There are no major Arch releases: each package is upgraded as new versions become available from upstream sources. Each repository is always coherent, i.e. the packages that it hosts always have reciprocally compatible versions.

Contents

Stable repositories

This repository can be found in . /core/os/ on your favorite mirror.

core contains packages for:

as well as dependencies of the above (not necessarily makedepends) and the base meta package.

core has fairly strict quality requirements. Developers/users need to signoff on updates before package updates are accepted. For packages with low usage, a reasonable exposure is enough: informing people about update, requesting signoffs, keeping in #testing up to a week depending on the severity of the change, lack of outstanding bug reports, along with the implicit signoff of the package maintainer.

extra

This repository can be found in . /extra/os/ on your favorite mirror.

extra contains all packages that do not fit in core. Example: Xorg, window managers, web browsers, media players, tools for working with languages such as Python and Ruby, and a lot more.

community

This repository can be found in . /community/os/ on your favorite mirror.

community contains packages that have been adopted by Trusted Users from the Arch User Repository. Some of these packages may eventually make the transition to the core or extra repositories as the developers consider them crucial to the distribution.

multilib

This repository can be found in . /multilib/os/ on your favorite mirror.

multilib contains 32-bit software and libraries that can be used to run and build 32-bit applications on 64-bit installs (e.g. wine , steam , etc).

With the multilib repository enabled, the 32-bit compatible libraries are located under /usr/lib32/ .

Enabling multilib

To enable multilib repository, uncomment the [multilib] section in /etc/pacman.conf :

Then upgrade the system and install the desired multilib packages.

Disabling multilib

Execute the following command to remove all packages that were installed from multilib:

If you have conflicts with gcc-libs reinstall the gcc-libs package and the base-devel group.

Comment out the [multilib] section in /etc/pacman.conf :

Then upgrade the system.

Testing repositories

The intended purpose of the testing repository is to provide a staging area for packages to be placed prior to acceptance into the main repositories. Package maintainers (and general users) can then access these testing packages to make sure that there are no problems integrating the new package. Once a package has been tested and no errors are found, the package can then be moved to the primary repositories.

Not all packages need to go through this testing process. However, all packages destined for the core repository must go to testing first. Packages that can affect many packages (such as perl or python ) should be tested as well. Testing is also usually used for large collections of packages such as GNOME and KDE.

testing

This repository can be found in . /testing/os/ on your favorite mirror.

testing contains packages that are candidates for the core or extra repositories.

New packages go into testing if:

• They are destined for the core repo. Everything in core must go through testing

• They are expected to break something on update and need to be tested first.

testing is the only repository that can have name collisions with any of the other official repositories. If enabled, it has to be the first repository listed in your /etc/pacman.conf file.

community-testing

This repository is similar to the testing repository, but for packages that are candidates for the community repository.

multilib-testing

This repository is similar to the testing repository, but for packages that are candidates for the multilib repository.

gnome-unstable

This repository contains testing packages for the next stable or stable release candidate version of the GNOME desktop environment, before they are moved to the main testing repository.

To enable it, add the following lines to /etc/pacman.conf :

The gnome-unstable entry should be first in the list of repositories (i.e., above the testing entry).

Please report packaging related bugs in our bug tracker, while anything else should be reported upstream to GNOME Gitlab.

kde-unstable

This repository contains the latest beta or Release Candidate of KDE Plasma and Applications.

To enable it, add the following lines to /etc/pacman.conf :

The kde-unstable entry should be first in the list of repositories (i.e., above the testing entry).

Make sure you make bug reports if you find any problems.

Disabling testing repositories

If you enabled testing repositories, but later on decided to disable them, you should:

1. Remove (comment out) them from /etc/pacman.conf
2. Perform a pacman -Syuu to «rollback» your updates from these repositories.

The second item is optional, but keep it in mind if you notice any problems.

Staging repositories

This repository contains broken packages and is used solely by developers during rebuilds of many packages at once. In order to rebuild packages that depend on, for example, a new shared library, the shared library itself must first be built and uploaded to the staging repositories to be made available to other developers. As soon as all dependent packages are rebuilt, the group of packages is then moved to testing or to the main repositories, whichever is more appropriate.

See [1] for more historical details.

Historical background

Most of the repository splits are for historical reasons. Originally, when Arch Linux was used by very few users, there was only one repository known as official (now core). At the time, official basically contained Judd Vinet’s preferred applications. It was designed to contain one of each «type» of program — one DE, one major browser, etc.

There were users back then that did not like Judd’s selection, so since the Arch Build System is so easy to use, they created packages of their own. These packages went into a repository called unofficial, and were maintained by developers other than Judd. Eventually, the two repositories were both considered equally supported by the developers, so the names official and unofficial no longer reflected their true purpose. They were subsequently renamed to current and extra sometime near the release version 0.5.

Shortly after the 2007.8.1 release, current was renamed core in order to prevent confusion over what exactly it contains. The repositories are now more or less equal in the eyes of the developers and the community, but core does have some differences. The main distinction is that packages used for Installation CDs and release snapshots are taken only from core. This repository still gives a complete Linux system, though it may not be the Linux system you want.

Some time around 0.5/0.6, there were a lot of packages that the developers did not want to maintain. Jason Chu set up the «Trusted User Repositories», which were unofficial repositories in which trusted users could place packages they had created. There was a staging repository where packages could be promoted into the official repositories by one of the Arch Linux developers, but other than this, the developers and trusted users were more or less distinct.

This worked for a while, but not when trusted users got bored with their repositories, and not when untrusted users wanted to share their own packages. This led to the development of the AUR. The TUs were conglomerated into a more closely knit group, and they now collectively maintain the community repository. The Trusted Users are still a separate group from the Arch Linux developers, and there is not a lot of communication between them. However, popular packages are still promoted from community to extra on occasion. The AUR also allows untrusted users to submit PKGBUILDs.

After a kernel in core broke many user systems, the «core signoff policy» was introduced. Since then, all package updates for core need to go through a testing repository first, and only after multiple signoffs from other developers are then allowed to move. Over time, it was noticed that various core packages had low usage, and user signoffs or even lack of bug reports became informally accepted as criteria to accept such packages.

In late 2009/the beginning of 2010, with the advent of some new filesystems and the desire to support them during installation, along with the realization that core was never clearly defined (just «important packages, handpicked by developers»), the repository received a more accurate description.

Источник

Arch Linux

You are not logged in.

#1 2009-09-07 22:09:19

gnome unstable repository

GNOME 2.27.91 packages have been uploaded to the Archlinux FTP. To use this repository, you should add this as top repository to pacman.conf:

The packages in the repository have been built in a chroot with testing enabled. Dependencies are mostly versioned.

Note that packaging GNOME 2.27.x isn’t completely done yet. Some things:
— gmime has been updated to 2.4, which is incompatible to 2.2. Expect some existing packages to break
— gdm, gnome-games, gnome-user-share, gnome-user-docs are not updated yet. These will follow shortly
— gnome-bluetooth should be packaged to replace bluez-gnome
— update most packages to 2.27.92
— maybe fiddle around with pulseaudio
— x86_64 packages

Have fun testing these packages. So far they’ve been working fine on my i686 laptop, so there shouldn’t be much problems using these packages.

Last edited by JGC (2009-09-22 08:13:38)

#2 2009-09-07 22:57:59

Re: gnome unstable repository

64-bit.

Thanks anyway JGC.

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

#3 2009-09-07 23:02:26

Re: gnome unstable repository

You got +1 tester when 64bit packages are ready, we got only 2weeks b4 2.28 goes stable.

#4 2009-09-07 23:53:35

Re: gnome unstable repository

Oh. thanks to packing gnome beta. I’ll test it. 🙂

#5 2009-09-08 14:06:56

Re: gnome unstable repository

No issues installing the packages but I miss a lot of icons here and there: In the main menu, in the contextual menus, in the bottons etc etc. Maybe I need to refresh/recreate the icon cache? How do I do it?
Example:
http://imagebin.org/63034
Thanks

UPDATE: sorry i forgot to check «Show the icons in the menus» under appearance. My fault

Last edited by piccolotux (2009-09-08 14:20:03)

#6 2009-09-08 22:18:03

Re: gnome unstable repository

The missing images is an upstream change and has been reverted for gnome-panel. The new code just hasn’t been released yet.

#7 2009-09-08 23:02:27

Re: gnome unstable repository

Shouldn’t we follow along with upstream on this? I don’t agree with the idea that lack of icons is more streamlined, but wouldn’t it be easier to maintain if upstream’s decisions were followed? Those who want icons could just check the appropriate box, perhaps just mentioning it in post-install or in the wiki would be enough.

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

#8 2009-09-08 23:59:23

Re: gnome unstable repository

I got these errors during installation. I thought I’d post them here and come back to them after I restart Gnome.

(54/94) upgrading gnome-control-center [###################################################] 100%
Unknown media type in type ‘all/all’

Unknown media type in type ‘all/allfiles’

Unknown media type in type ‘uri/mms’

Unknown media type in type ‘uri/mmst’

Unknown media type in type ‘uri/mmsu’

Unknown media type in type ‘uri/pnm’

Unknown media type in type ‘uri/rtspt’

Unknown media type in type ‘uri/rtspu’

Unknown media type in type ‘fonts/package’

Unknown media type in type ‘interface/x-winamp-skin’

Once I started up Gnome 2.27, I found the following:
File Management from the System > Preferences menu crashed (Nautilus), and was reported by Bug Buddy. Nautilus started from the Places menu works fine. EDIT: it’s actually nautilus-file-management-properties that’s crashing.

The Battery icon in the notification area is blank, but the tooltip is working. I have the preferences set to always display an icon.

The system beep is silent. The beep program still produces sound, however.

When I start Tomboy Notes, the icon in the notification area is the Firestarter icon. When i quit Tomboy, the extra Firestarter icon moves over to the empty space where the Battery icon should be. Any program I start that puts an icon in the notification area uses a Firestarter icon.

Inkscape needs to be recompiled due to the libpoppler upgrade. Bug report to follow (if I remember).

Last edited by tigrmesh (2009-09-09 05:13:01)

#9 2009-09-09 08:43:26

Re: gnome unstable repository

As for the lack of icons: that was reverted upstream and should be included in the 2.27.92 release.
About the mime errors: this is because of KDE. KDE includes some unknown mimetypes in their mime specifications, and if the update-mime-database command is not redirected to /dev/null, you’ll see that error output.

The file management properties dialog should be fixed in nautilus 2.27.92
The icon problems are unknown to me, but it looks like you have freaked icon caches or something like that. What icon theme do you use?
As for inkscape: this is just one of the apps that need a recompile for poppler/gmime/whatever.

#10 2009-09-09 17:50:27

Re: gnome unstable repository

no never mind

Last edited by urandom (2009-09-09 17:52:39)

#11 2009-09-09 18:00:51

Re: gnome unstable repository

sweet, installing now.

UPDATE:
nautilus-file-management-properties — crashes
nautilus-actions-config-tool — crashes with error [Duplicate object id ‘label1’ on line 1000 (previously on line 940)]

Last edited by hekel (2009-09-09 18:42:42)

#12 2009-09-10 15:14:34

Re: gnome unstable repository

@JGC — Thanks for the response. It seems that the notification icons have sorted themselves out without any intervention.

And thank you, JGC, for creating the unstable repo so we can help test this.

#13 2009-09-11 23:39:08

Re: gnome unstable repository

Some updates:
— apps are updated to 2.27.92
— gnome-bluetooth, gnome-user-share and gnome-games have been packaged for 2.27
— initial work on x86_64 has started (my brand new Q9550 has something to do now)

#14 2009-09-12 02:18:56

Re: gnome unstable repository

One thing I forgot to mention is that when I first log in, I get a notification dialog saying «Battery may be broken», and the panels and menus don’t appear until I have clicked the button in the dialog box. Sorry, but this isn’t a good time for me to log out, or I would tell you what exactly the button says. Not having the desktop available right away is very annoying.

#15 2009-09-12 05:56:54

Re: gnome unstable repository

Some updates:
— apps are updated to 2.27.92
— gnome-bluetooth, gnome-user-share and gnome-games have been packaged for 2.27
— initial work on x86_64 has started (my brand new Q9550 has something to do now)

good !

#16 2009-09-15 12:22:00

Re: gnome unstable repository

I think I use like 1% of gnome features, but that 1% have been working perfectly (i686)

That new release made me remind my disk have bad sectors. This new smart gui is quite cool.

pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))

#17 2009-09-15 12:33:36

Re: gnome unstable repository

I hope JGC to upload the x86_64 packages, I’d like to test GNOME and see if it works. (I use KDE4, but I ‘m curious to see what’s going on with GNOME 2.28).

#18 2009-09-19 16:19:43

Re: gnome unstable repository

Hey, thanks for packages! Anyway i found that in this version nautilus opens about 1.5 second later than on gnome 2.26. Is this slowdown normal?

#19 2009-09-20 06:42:19

Re: gnome unstable repository

I think I will wait till 2.6.28-1 before I upgrade, so what to put in pacman.conf to prevent all of gnome upgrade?

#20 2009-09-20 08:57:10

Re: gnome unstable repository

I think I will wait till 2.6.28-1 before I upgrade, so what to put in pacman.conf to prevent all of gnome upgrade?

nothing. those packages are in gnome-unstable repo. you don’t have it by default

Give what you have. To someone, it may be better than you dare to think.

#21 2009-09-20 18:11:06

Re: gnome unstable repository

I know that — but i prefer not to download the initial gnome upgrade the 2.28.0 when it hits extra — I want to wait until the second release of stable gnome is released.

#22 2009-09-20 18:19:43

Re: gnome unstable repository

I know that — but i prefer not to download the initial gnome upgrade the 2.28.0 when it hits extra — I want to wait until the second release of stable gnome is released.

pacman.conf, IgnoreGroup = gnome gnome-extra

Give what you have. To someone, it may be better than you dare to think.

Источник