| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
|
|
| |
nv_*detect apps
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
|
|
| |
nv_*detect apps
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
| |
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
| |
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
|
| |
need to use dodir first
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
|
| |
need to use dodir first
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
|
| |
need to use dodir first
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
| |
|
|
|
|
|
|
|
| |
'/usr/lib64' to '4'.
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
|
|
| |
'/usr/lib64' to '4'.
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
|
|
| |
'/usr/lib64' to '4'.
(Portage version: 2.0.51.22-r1)
|
| |
|
|
|
|
|
|
| |
moz_pis_startstop_scripts work for -bin installations
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
|
| |
moz_pis_startstop_scripts work for -bin installations
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
|
| |
moz_pis_startstop_scripts work for -bin installations
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Signed Manifest commit)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.0.51.22-r1)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
keyword-happy developer. There have been numerous
instances of untested unapproved packages being
keyworded, this was discussed time and again, the
issue is mentioned in developer documentation,
added to developer quiz, and voila, we have it again..
This time multiple packages in dev-dotnet/ category
were marked as mips, ~mips, sparc, ~sparc, as well as
working on other arches. It was confirmed that dotnet
doesn't even build on most of these, yet they were
keyworded. Oh well... There seems to be no way to teach
some people.
Removing mips and sparc keywords
(Manifest recommit)
(Portage version: 2.0.51.19) (Manifest recommit)
(Portage version: 2.0.51.19)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
keyword-happy developer. There have been numerous
instances of untested unapproved packages being
keyworded, this was discussed time and again, the
issue is mentioned in developer documentation,
added to developer quiz, and voila, we have it again..
This time multiple packages in dev-dotnet/ category
were marked as mips, ~mips, sparc, ~sparc, as well as
working on other arches. It was confirmed that dotnet
doesn't even build on most of these, yet they were
keyworded. Oh well... There seems to be no way to teach
some people.
Removing mips and sparc keywords
(Manifest recommit)
(Portage version: 2.0.51.19)
|