Signed-off-by: Göktürk Yüksek
---
metadata.dtd | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/metadata.dtd b/metadata.dtd
index a3c06ff..8ef1396 100644
--- a/metadata.dtd
+++ b/metadata.dtd
@@ -68,9 +68,10 @@
--
2.7.3
Signed-off-by: Göktürk Yüksek
---
metadata.dtd | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/metadata.dtd b/metadata.dtd
index 8ef1396..6d38729 100644
--- a/metadata.dtd
+++ b/metadata.dtd
@@ -20,7 +20,10 @@
-
+
--
2.7.3
Also mention that the attribute value must be a valid ISO 639-1
language code.
Signed-off-by: Göktürk Yüksek
---
metadata.dtd | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/metadata.dtd b/metadata.dtd
index b608852..a3c06ff 100644
--- a/metadata.dtd
+++ b/
Signed-off-by: Göktürk Yüksek
---
metadata.dtd | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/metadata.dtd b/metadata.dtd
index 7626a57..b608852 100644
--- a/metadata.dtd
+++ b/metadata.dtd
@@ -3,7 +3,7 @@
-
+
@@ -13,9 +13,6 @@
explicit type) for Gentoo
On Sat, Apr 30, 2016 at 8:53 PM, Daniel Campbell wrote:
>
> As you said, however, it's a choice of the maintainer. Things like Perl
> and Python may be less prone to this issue since they're meant to be
> portable.
>
The concept is that the maintainer will only use this when this is the
case. Th
Hi all,
The gitolite hooks for GPG-signed pushes have been very successful since
we launched them with the Gentoo repo, so I'd like to roll them out to
more repos.
Additionally, in an effort to simplify configuration, we're going to
default to a number of hooks being enabled (but they will do not
On 04/30/2016 07:53 PM, Daniel Campbell wrote:
> On 04/30/2016 02:16 PM, Andreas K. Huettel wrote:
>>
>> Hi all,
>>
>> just as a small reminder, to ease the load on all arch teams:
>>
>> If a stablerequest has the keyword ALLARCHES set, then
>> * the first arch that tests successfully and stabilize
On 04/30/2016 02:16 PM, Andreas K. Huettel wrote:
>
> Hi all,
>
> just as a small reminder, to ease the load on all arch teams:
>
> If a stablerequest has the keyword ALLARCHES set, then
> * the first arch that tests successfully and stabilizes
> * can and *should* immediately stabilize for all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
just as a small reminder, to ease the load on all arch teams:
If a stablerequest has the keyword ALLARCHES set, then
* the first arch that tests successfully and stabilizes
* can and *should* immediately stabilize for all requested arch
Hi all,
I'm currently developping a patch for user.eclass, but I'm
banging my head against a wall...
So for testing first, I've setup an overlay, and I now that
it is taken in account by portage (If I rename portage's
user.eclass, emerge is still working. If I remove my
overlay, emerge co
On 28 Apr 2016 13:28, Leno Hou wrote:
> --- a/dev-lang/go/go-1.6.2.ebuild
> +++ b/dev-lang/go/go-1.6.2.ebuild
> @@ -88,6 +88,16 @@ go_arch()
> case "${portage_arch}" in
> x86)echo 386;;
> x64-*) echo amd64;;
> + ppc64)
> + case
On Sat, 30 Apr 2016 02:36:18 -0400
Göktürk Yüksek wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Michał Górny:
> > On Thu, 28 Apr 2016 19:41:06 -0400 Göktürk Yüksek
> > wrote:
> >
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
> >>
> >> Brian Dolbec:
> >>> On Thu, 28
12 matches
Mail list logo