You are not logged in.
Pages: 1
I am wondering how many users are really using test repository when upgrading. It's not the first repo by default (current will be the first).
Offline
You didn't give me my option which is: I don't use it -- uses too much bandwidth.
I don't want to:
a) download several broken versions of an untested package
b) download the testing version and then the current version when its released
c) download the testing db every time I Syu
Offline
You didn't give me my option which is: I don't use it
I added the option. Its a good point.
I will if devs or someone encourage to do so. Not with option -Syu but through download and -A.
Markku
Offline
another option not added:
I use it when there's a specific package i want to grab in there. Otherwise, no.
Offline
I've used it for a long time.
Been burned occasionally, too, by not-quite-finished packages. However, using [testing] lets you influence packaging more since you have an early stage to give bug reports.
Plus lots of cool stuff is in there, sometimes for a long time. I get worried when testing is close-to-empty
Offline
Though i promote it i don't use it. I don't have time to fix bugs or seek out my own solutions. Actually i don't really need to anymore as most people can do it themselves now
AKA uknowme
I am not your friend
Offline
since this discussion came up (two weeks) I've used it,
Edit: My fonts improved in quality since I started using Testing.
Could be a tip for people struggling....
arch + gentoo + initng + python = enlisy
Offline
Yep I use it, happy to help arch with pkging problems. I really havn't had any big problems from it; I especially don't worry since I never clean my cache.
Offline
I wanted to test evolution 2.0 but the trouble caused when trying to install, I am concluding testing is for those who plan to do it, not for "I use it when there's a specific package i want".
For one or two individual packages its fine, but not when required many dependency packages. Option -S requires to tag both current and extra thereby not accessible to install any dependency packages if required by the test package. Also option -Su doesn't work... confused by testing's own dep. packages.
I don't know if there is a way how to go around having both current and testing without having more trouble configuring pacman than doing the actual testing. :?: The testing configure in pacman has to be changed if we want to engourage users to test. Would it be possible to have in pacman script some kind of "IF and ELSE" detecting if a package is in both current/extra and testing?
Markku
Offline
Would it be possible to have in pacman script some kind of "IF and ELSE" detecting if a package is in both current/extra and testing?
Better not, I think it will give us more troubles than ones it solved. We could encourage or advocate in our forum or website instead of tweaking pacman directly, users want to join test will do it themself, if they know how to do it (uncommenting part of the test repo in the pacman.conf is really simple enough).
Offline
Better not.... uncommenting part of the test repo in the pacman.conf is really simple enough.
I agree if it would also work with testing packages with large number of dependency pkgs, what it does not, when required to be installed from current (or extara), which is tagged. With an "IF and ELSE" script all repos can be untagged. Only what the user needs to tag (or untag) if wanting to use testing.
Markku
Offline
Ok, I found the solution how to configure testing without dependency error described by apeiro. It works fine.
http://bbs.archlinux.org/viewtopic.php?t=7153
Markku
Offline
Testing repository?
Booyah! That's my bread and butter while using Arch. I use it quite often with few (if any) noteworthy problems. In my case, it should be renamed the "Impatient" repository...
Offline
i don't use it since everything works just fine for me and the software is bleeding-edge enough i think.
I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell
Offline
Pages: 1