You are not logged in.
This new subforum is dedicated to users of the [testing] repo exclusively.
Note that all bugs must still be directed to the respective bugtracker, but please feel free to discuss any observations, issues and solutions thereof, unique to use of the [testing] repo, here.
Offline
Good idea -- hopefully this will encourage more users to use [testing].
Last edited by fwojciec (2008-12-29 00:44:10)
Offline
Sweet, it does encourage me...
Offline
I like.
Offline
this is a nice approce for making people to test packages more. it made me update to testing and i found several bugs.
Give what you have. To someone, it may be better than you dare to think.
Offline
Maybe i will use virtualbox to the [testing] , would be ideal for testing kde4
Offline
Offline
I would like a solution to view important messages and announcements concerning [testing], besides the mailinglist. All stuff in the mailinglists about repository maintainance are not really necessary for me and it is very hard to filter out important information if you use [testing]. A dedicated archlinux.org/testing page with news items, important information, warnings and the like would be very much appreciated. These news items could, for example, announce that kernel26-2.6.28 has hit [testing], that xorg-server-1.6 was added, which problems there still are, common errors that occur (including workarounds, if exist), maybe with rss feed.
Offline
I would like a solution to view important messages and announcements concerning [testing], besides the mailinglist. All stuff in the mailinglists about repository maintainance are not really necessary for me and it is very hard to filter out important information if you use [testing]. A dedicated archlinux.org/testing page with news items, important information, warnings and the like would be very much appreciated. These news items could, for example, announce that kernel26-2.6.28 has hit [testing], that xorg-server-1.6 was added, which problems there still are, common errors that occur (including workarounds, if exist), maybe with rss feed.
The goal of testing is actually to help the developers for preparing the move to core/extra by :
* finding bugs and helping to fix them
* finding out if there is any important information users should be aware about
So the important messages and announcements are already provided for users of core/extra, and the testing repo actually helps a lot to prepare them...
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
I would like a solution to view important messages and announcements concerning [testing], besides the mailinglist. All stuff in the mailinglists about repository maintainance are not really necessary for me and it is very hard to filter out important information if you use [testing]. A dedicated archlinux.org/testing page with news items, important information, warnings and the like would be very much appreciated. These news items could, for example, announce that kernel26-2.6.28 has hit [testing], that xorg-server-1.6 was added, which problems there still are, common errors that occur (including workarounds, if exist), maybe with rss feed.
shining covered the latter half of your questions, but I thought I would address it a bit as well. We no longer send repository maintenance messages to the arch-dev-public mailing list, so that is one less bit of stuff to read though. (If you want to be overwhelmed, signup for arch-commits.)
As shining said, developers can't form all these pretty news items and everything else until a package has gone through testing. Use of this repository is not for everyone, but if you are willing to follow along on the ML a bit you will rarely be surprised. I am comfortable for the most part running testing on two of my machines, and I haven't had a serious issue in almost a year.
Offline
I'd like to give testing a try, is it just a matter of enabling the testing repo? Or do I have to disable the other repos and use the testing one exclusively?
Cheers
Offline
I'd like to give testing a try, is it just a matter of enabling the testing repo? Or do I have to disable the other repos and use the testing one exclusively?
Cheers
You only need to enable Testing, but make sure it comes before the other repos in pacman.conf.
Offline
I'd like to give testing a try, is it just a matter of enabling the testing repo? Or do I have to disable the other repos and use the testing one exclusively?
Cheers
Place testing at top of other repos.
And be prepared for a lot more updates than normal.
My Linux Blog - http://TheSmallerBang.wordpress.com/
Offline
I would like to help out and run using the testing repo, however I get the following error when I do an update:
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
xorg-server: /usr/lib/xorg/modules/extensions/libdri.so exists in filesystem
xorg-server: /usr/lib/xorg/modules/libwfb.so exists in filesystem
Errors occurred, no packages were upgraded.
Any ideas?
Offline
Offline
wow, and I even subscribe to that RSS feed
Thanks though!
I resolved it by just re-naming those files and then doing the update...probably not the best approach but it worked for me.
Offline
Paul-S wrote:I'd like to give testing a try, is it just a matter of enabling the testing repo? Or do I have to disable the other repos and use the testing one exclusively?
Cheers
Place testing at top of other repos.
And be prepared for a lot more updates than normal.
If I do so and want to switch back to normal repos, is it enough to disable [testing] in pacman.conf and run "pacman -Syu" ?
Last edited by SiD (2010-12-18 18:36:22)
Offline
I believe
pacman -Syyuu
is better, iirc two u flags upgrade from current repos and yy will manually refresh the mirror to remove testing
Rauchen verboten
Offline
Sweet, it does encourage me...
Same here. I decided to give it a go on a desktop and a laptop (both i686). Just finished grabbing testing/libjpeg-turbo and it seems to be working well thus far without any issues.
Offline
That sounds like the road to breakage to me. You do realise you need to use *all* of testing, not cherrypick?
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Been using [testing] for about three months now, without any serious issues to speak of. After looking the first dozen posts here, though, this seems as good a place as any to stick this.
Offline
What is the deal with changes to udev and hooks? been reading about problems of users being dropped to reduced shell after updating.
Anything I should watch for when I update?
Mr Green
Offline
What is the deal with changes to udev and hooks? been reading about problems of users being dropped to reduced shell after updating.
Anything I should watch for when I update?
This is NOT a general-purpose 'ask any question about [testing]' thread.
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.
Offline
It will not happen again
Mr Green
Offline
I like how there are testing repos as you can get even more bleeding-edge.
-- SealsRock12
Offline