| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
...in preparation for next commit.
|
| |
|
|
| |
...as that defeats the purpose of using QARepo.
|
| |
|
|
|
|
| |
Automatically add the arch/noarch and .rpm extension, but don't allow
incomplete or missing version numbers. We have wildcards and fuzzy
versions for that.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This version supports simultaneous 32-bit and 64-bit local repos.
They will be (unimaginatively) named 'QA Testing (32-bit)' and 'QA Testing (64-bit)'.
The repos will be stored in 'i586' and 'x86_64' subdirectories of the directory
specified in the QA Repo box.
Each repo can be independently enabled/disabled. The repos can have different contents.
When you switch between them in the GUI, the RPMs box will be updated to show the current
contents of the selected repo.
Before using the new version, make sure the old 'QA Testing' repo is disabled, and, if you
want to save redownloading lots of files, move the the contents of your current repo down one
level into the appropriately named (i586 or x86_64) subdirectory.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've added a couple of extra options:
1. "fuzzy version" will automatically replace the package
version/release in each requested package with a wildcard.
If there are multiple versions in the remote repository,
you'll get them all (and MageiaUpdate will then select the newest).
Note this only happens if the requested package name includes
the Mageia release (e.g. mga6) and if the package version
starts with a digit, to avoid false matches.
2. "add deps" will automatically add all dependencies of the
requested packages that can be satisfied from the updates_testing
repositories.
If you want to see what's actually been selected,
either quit the app. and restart it, or use
urpmq --list --media 'QA Testing'
I would only use these options whilst things are in a state of flux.
You really want to test against a definitive package list before you
finally validate an update.
I've also added a couple of check boxes to let you enable/disable use
of the nonfree and tainted repositories.
|
| |
|
|
|
|
|
|
|
|
|
| |
A few more changes:
- enables 'QA Testing' as an updates repository
(fixes regression in v1.1)
- ignores leading/trailing white space in entries
- discards duplicates in RPMs list
(so T.J.'s wildcard list is handled properly now)
- reports errors in a pop-up dialogue window
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So, following initial feedback, I've made a few changes:
- incomplete names and simple wildcards (? and *) are accepted in
the RPMs box
- the Clear button just clears the RPMs box (use the Update button
to clear the local repo as well)
- the current status is shown, which can be one of
Enabled : 'QA Testing' is enabled in the urpmi media and the
local repo contains what you see in the GUI
Needs update : 'QA Testing' is enabled in the urpmi media, but the
local repo is out of sync with what you see
Updating : what it says
Update failed : one or more of the requested RPMs couldn't be fetched
from the remote repo (or some other error occurred).
You can try updating again in case it was a temporary
download error
Disabled : 'QA Testing' has been removed from the urpmi media
(but the local repo remains intact)
- the dual-function button is now Enable/Update, depending on the current
status (this should all become clear when you use the app.). In reality
it does exactly the same thing in both cases - it's just another visual
clue to show whether or not the local repo is in sync
|
| |
|
