the mistery of 'testing'...

hermit · 2010-02-13 23:17:36

what's the big deal about using [testting] repo? ain't no newbie on penguin(3 years using it) i've tested all the distros/bsd-pc and free-...
i no testing it is equivalent to xperimental on debian...
is there just one thing to take care on testing?

Allan · 2010-02-13 23:44:27

The only thing you need to do is read the arch-dev-public mailing list before upgrading. Otherwise, enjoy the "fun" testing can bring.

hermit · 2010-02-13 23:52:00

homies...how can i get kernel 33rc7? according to this: http://www.kernel.org/

Last edited by hermit (2010-02-15 14:26:04)

hermit · 2010-02-15 14:20:03

...?...

rson451 · 2010-02-15 14:25:21

By compiling it.

tomk · 2010-02-15 14:25:53

Build it yourself - it's not in any Arch repo.

wonder · 2010-02-15 14:27:57

hermit wrote:

homies...how can i get kernel 33rc7? according to this: http://www.kernel.org/

compiling yourself. we are not providing in testing release candidate but kernel 2.6.33 will hit testing first when is released.

sHyLoCk · 2010-02-15 14:40:11

Better you grab the PKGBUILD of2.6.32 and edit it to compile and install 2.6.33rc for you. Also you can check AUR for a number of kernels including rc kernels!
http://aur.archlinux.org/packages.php?ID=31932

Pierre · 2010-02-15 14:48:11

Btw: I plan to write an article about using testing properly. It doesn't seem to be documented in detail somewhere.

sHyLoCk · 2010-02-15 14:54:03

Pierre wrote:

Btw: I plan to write an article about using testing properly. It doesn't seem to be documented in detail somewhere.

That would be awesome. I was planning to put one in my blog someime, but I'll wait and steal yours.

Vi0L0 · 2010-02-15 17:03:45

Newest rc is here: http://aur.archlinux.org/packages.php?ID=31932 Edit: aww sorry, sHyLoCk wrote about that, but still:
you can also download git patch (daily released) from kernel.org and patch rc with it. Easiest way to do this is to copy patch into 'src' directory and to add appropriate line to PKGBUILD, so it may look like in this example:

build() {
cd ${srcdir}/linux-$_basekernel
# Add -ARCH patches
# See http://projects.archlinux.org/linux-2.6-ARCH.git/
patch -Np1 -i ${srcdir}/${_patchname} || return 1
patch -Np1 -i ${srcdir}/patch-2.6.33-rc8-git1 || return 1 #this line has been added

Last edited by Vi0L0 (2010-02-15 17:13:27)

hermit · 2010-02-15 19:43:40

it'd be nice to have on repos kernel 33...:cool:

tomk · 2010-02-15 21:34:57

And we will... as soon as it's released.

Misfit138 · 2010-02-16 01:09:43

You spelled 'mystery' incorrectly.

sHyLoCk · 2010-02-16 02:26:51

Misfit138 wrote:

You spelled 'mystery' incorrectly.

for some reason I read it as "misery" now that you mentioned I noticed the "t"

Daenyth · 2010-02-16 04:20:03

Pierre wrote:

Btw: I plan to write an article about using testing properly. It doesn't seem to be documented in detail somewhere.

A while back I added the following to the official repos wiki page, but it could use some expanding:

The [testing] repo is not for the "newest of the new" package versions. Part of its purpose is to hold package updates that have the potential to cause system breakage, either by being part of the [core] set of packages, or by being critical in other ways. As such, users of the [testing] repository are strongly encouraged to subscribe to the arch-dev-public mailing list, and to report all bugs to the bug tracker.

david84 · 2010-04-09 10:42:12

Hey, im new to Arch - going on 2 weeks i think - btw arch is also my very first linux distro believe it or not
so, as some1 this new, is it just dumb trying 'testing'? just thougt id take the chance, get the newest stuff and help out testing on my x86 64 machine.. i have led myself to believe that if all goes to hell, i could use the rollback option in the boot loader and all would be nice and shiny again.. have joined the mailing list btw but if im wrong in my assumption and ill be forced to reinstall or buy a new computer ina few days cuz im a n00b, please let me know asap so i can off the testing list while there is still time

cheers

ngoonee · 2010-04-09 10:51:36

david84 wrote:

Hey, im new to Arch - going on 2 weeks i think - btw arch is also my very first linux distro believe it or not
so, as some1 this new, is it just dumb trying 'testing'? just thougt id take the chance, get the newest stuff and help out testing on my x86 64 machine.. i have led myself to believe that if all goes to hell, i could use the rollback option in the boot loader and all would be nice and shiny again.. have joined the mailing list btw but if im wrong in my assumption and ill be forced to reinstall or buy a new computer ina few days cuz im a n00b, please let me know asap so i can off the testing list while there is still time
cheers

If you can read/search, go ahead. I'm not sure what 'rollback' option you're talking about, probably the fallback? That doesn't do much, honestly, its mainly if your mkinitcpio gets messed up, its not a 'restore point' like in Windows or whatever.

tomk · 2010-04-09 11:07:38

david84 - I'd recommend you stay away from testing for the foreseeable future. Even Archers who have enough experience to know better still screw up their systems with testing every now and then. You're just two weeks in, not just with Arch but with linux, so stick with core/extra.

More generally, don't make assumptions about how things work or what they do e.g. your "rollback" option. If you're in doubt, check the wiki, search the forums - if you still need help, ask.

david84 · 2010-04-09 12:19:15

thanks for the quick replys
i think i might get off the testing list, i just had some programs etc that didnt work before going to testing that works now..even tho im not sure if it just me messing around that did it.. if the pacman -Uu or whatever it was cant revert possible errors (im thinking no screen/no keyboard?/stuff like that) ill get off the list when i get home..

cheers

Gen2ly · 2010-04-10 00:03:39

Daenyth wrote:

Pierre wrote:
Btw: I plan to write an article about using testing properly. It doesn't seem to be documented in detail somewhere.
A while back I added the following to the official repos wiki page, but it could use some expanding:
The [testing] repo is not for the "newest of the new" package versions. Part of its purpose is to hold package updates that have the potential to cause system breakage, either by being part of the [core] set of packages, or by being critical in other ways. As such, users of the [testing] repository are strongly encouraged to subscribe to the arch-dev-public mailing list, and to report all bugs to the bug tracker.

This is also covered in the [wiki]pacman[/wiki] page though I think the wording is a little better here.

Arch Linux

#1 2010-02-13 23:17:36

the mistery of 'testing'...

#2 2010-02-13 23:44:27

Re: the mistery of 'testing'...

#3 2010-02-13 23:52:00

Re: the mistery of 'testing'...

#4 2010-02-15 14:20:03

Re: the mistery of 'testing'...

#5 2010-02-15 14:25:21

Re: the mistery of 'testing'...

#6 2010-02-15 14:25:53

Re: the mistery of 'testing'...

#7 2010-02-15 14:27:57

Re: the mistery of 'testing'...

#8 2010-02-15 14:40:11

Re: the mistery of 'testing'...

#9 2010-02-15 14:48:11

Re: the mistery of 'testing'...

#10 2010-02-15 14:54:03

Re: the mistery of 'testing'...

#11 2010-02-15 17:03:45

Re: the mistery of 'testing'...

#12 2010-02-15 19:43:40

Re: the mistery of 'testing'...

#13 2010-02-15 21:34:57

Re: the mistery of 'testing'...

#14 2010-02-16 01:09:43

Re: the mistery of 'testing'...

#15 2010-02-16 02:26:51

Re: the mistery of 'testing'...

#16 2010-02-16 04:20:03

Re: the mistery of 'testing'...

#17 2010-04-09 10:42:12

Re: the mistery of 'testing'...

#18 2010-04-09 10:51:36

Re: the mistery of 'testing'...

#19 2010-04-09 11:07:38

Re: the mistery of 'testing'...

#20 2010-04-09 12:19:15

Re: the mistery of 'testing'...

#21 2010-04-10 00:03:39

Re: the mistery of 'testing'...

Board footer