| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(should have been caught by perl_checker but it didn't)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(g)urpmi will install priority upgrades first then restart itself.
If the priority upgrades happen to be installed in more than one transaction
code in the rpm packages %post script to clear out the rpmdb index files
could be run after the first transaction and then the second transaction
could regenerate these indexes using the current libdb version in memory.
This results in the rpmdb not being readable and requires manual intervension.
If the initial priority upgrades are handled in a single transaction this does
not occur and the rpmdb indexes are regenerated with the correct libdb.
This is a workaround to ensure that the first (g)urpmi run is completed in
a single transaction but it shoud only update enough to ensure urpmi and rpm
are upgraded. The normal --auto-select cycle can continue thereafter.
Ideally this would actually be fixed in urpmi to ensure that any priority updates
are handled within a single transaction.
|
| |
|
|
|
| |
The arguments are currently split up between run_gurpmi and fork_gurpmi
for no particular reason.
|
| |
|
|
|
|
|
|
| |
Patch from Maarten Vanraes and Dave Hodgins and tweaked by me for
trunk.
mga#6061
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The basic principle of this is to do the following:
1. Check the releases webservice API to see if the distro version 'needs_preparation'.
2. If it does, check for a file /var/lib/mageia-prepare-upgrade/state.
If it says 'ready' then we are ready and the user is not questioned further.
3. If it does not exist or says anything else, the user is prompted to install the
package 'mageia-prepare-upgrade'.
4. After package installation, check the state file again as this may be
all that is required. If the state file does not yet say 'ready', then
display the text from the /usr/share/doc/mageia-prepare-upgrade/README.prepare
file (todo: add i18n)
5. Assuming that further action is required by the user (e.g. rebooting to
convert the filesystem), then the upgrade helper will exit.
6. After the user has taken the action required to do the preparation,
the state file should contain 'ready'. The next time the distro upgrade
dialog shows, the preparation checks will pass and the user can continue.
TODO:
Handle i18n in the README.prepare file.
v1: First Revision
v2: Check immediately if an upgrade state file exists (don't wait 5 mins)
Ensure config file is parsed (ensures the testing variable is read)
Show user-visible messages when bailing out due to unexpected errors
|
| | |
|
| | |
|
| |
|
|
| |
(spot by Colin)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
- replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop
- replace MIME Type application/x-mdv-exec by application/x-mga-exec
- extend $MGA_YEARS in mgaupdate to 2012
- delete MANDRIVA_VERSION variable as not used
|
| | |
|
| | |
|
| | |
|
|
|
with Mageia.
This commit consitsts of the following subversion commits:
------------------------------------------------------------------------
r1310 | dmorgan | 2011-05-14 01:22:07 +0100 (Sat, 14 May 2011) | 1 line
Import cleaned mgaonline
------------------------------------------------------------------------
|
