| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Package-Manager: portage-2.2_rc87/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.2_rc67/cvs/Linux i686
|
|
|
|
| |
Package-Manager: portage-2.1.6.13/cvs/Linux ia64
|
|
|
|
| |
Package-Manager: portage-2.2_rc56/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.6.13/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.6.13/cvs/Linux ia64
|
|
|
|
| |
Package-Manager: portage-2.2_rc51/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.6.13/cvs/Linux i686
|
|
|
|
| |
Package-Manager: portage-2.1.7.1/cvs/Linux ppc64
|
|
|
|
| |
Package-Manager: portage-2.2_rc46/cvs/Linux i686
|
|
|
|
| |
Package-Manager: portage-2.1.6.13/cvs/Linux x86_64
|
|
|
|
|
|
|
| |
could file collide with hal are gone now and it included the 2.22 versions in the blocker, which was not necessary and is problematic with HAL stabling but g-p-m staying at 2.22. This fixes bug 287037; Gracious revbump to ensure amd64 stable users get the blocker fixed in VDB, permission from mrpouet to keep the stable keyword
Package-Manager: portage-2.2_rc33/cvs/Linux x86_64
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: portage-2.2_rc38/cvs/Linux x86_64
|
|
Package-Manager: portage-2.2_rc33/cvs/Linux x86_64
|