| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove versioned remote-ids.
Upstream:
- Add APIs v201708-v201710
- Remove APIs v201607-v201609
- Logging updated so failed messages are logged as INFO
while successful messages are logged as DEBUG
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
|
|
| |
Remove versions affected by '.' in @INC
Bug: https://bugs.gentoo.org/613404
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Added patch for '.' in @INC (#613404)
- Added patch for unescaped {
Upstream:
- Add support/examples for v201705
- Add more situation examples
Bug: https://bugs.gentoo.org/613404
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream:
- Add API v201702
- Remove API v2001605
- Update summary and SOAP logging to include more detailed
messages
- Update ErrorUtils.pm to make error discovery clearer
- Renamed approval_prompt param to prompt in OAuth flow
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
|
|
|
|
|
|
| |
I initially thought I was going to have to EOL 2.x without
giving much time for consumers to migrate to 4.x, but it
turns out upstream shipped an identical tar.gz to CPAN.
So this simply changes the SRC_URI and relevant naming
glue code to use the same tar.gz when shipped under a different
name.
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
|
|
|
|
| |
- EAPI6
- Add USE=examples
- Restore tests (working)
- Upstream -> CPAN instead of GoogleCode
- Deps cleaned up
Package-Manager: portage-2.3.2
|
|
Migrating to CPAN naming scheme as upstream origins are changing.
Package-Manager: portage-2.3.2
|