Hello.
I'm not a gentoo-dev, so sorry if I shouldn't express my thoughts with
my lame English here. Please tell me if it's so.
On 08/11/2015 12:06 AM, Michał Górny wrote:
>> 3. Too many text, hard to read. Some bugs may refer to a dozen of
>> URLs.
>
> And how is a dozen numbers b
On Mon, Aug 10, 2015, at 22:56 CDT, Kent Fredric wrote:
> So how is GPG verifying "The whole repository" ?
You can verify the state of the repository via
$ git fsck
after that you can verify that the current HEAD is tagged with a valid
and singed tag with something like
$ git tag -v `git
On 11 Aug 2015 15:23, Kent Fredric wrote:
> On 11 August 2015 at 15:06, Mike Frysinger wrote:
> > it would have to re-use the same tag name every time otherwise we end up
> > with
> > 17.5k/8.7k/4.3k/whatever new tags per year ... a really bad idea
>
> I was very much under the impression git is
On 11 August 2015 at 15:44, Matthias Maier wrote:
>
> No, a signed tag verifies that the whole integrirty of the entire
> repository, whereas a signed commit only authenticates the differences
> introduced by a single commit.
git tag -s test
cat ./.git/refs/tags/test
456d216e3d1894d62429daf0ec4
> it would have to re-use the same tag name every time otherwise we end up with
> 17.5k/8.7k/4.3k/whatever new tags per year ... a really bad idea
Or we supply a signature of the sha1-sum of the tag in question by some
external procedure...
Best,
Matthias
signature.asc
Description: PGP signat
> That is, I was under the impression signing a tag only signs the
> references themselves, and then relies on SHA1 referential integrity
> beyond that.
No, a signed tag verifies that the whole integrirty of the entire
repository, whereas a signed commit only authenticates the differences
introduc
On 11 August 2015 at 15:06, Mike Frysinger wrote:
> it would have to re-use the same tag name every time otherwise we end up with
> 17.5k/8.7k/4.3k/whatever new tags per year ... a really bad idea
I was very much under the impression git is not designed with repeated
tag replication in considera
On 11 August 2015 at 09:05, Matthias Maier wrote:
> We could also provide automatic signed tags every 30min/1h/2h/whatever
> (signed with a suitable infrastructure key). With that, the integrity of
> a tagged git checkout can be easily verified on client side.
I'm distinctly under the impression
On 10 Aug 2015 16:05, Matthias Maier wrote:
> > Users can fetch/pull from Github.
>
> We could also provide automatic signed tags every 30min/1h/2h/whatever
> (signed with a suitable infrastructure key). With that, the integrity of
> a tagged git checkout can be easily verified on client side.
it
Ryan Hill posted on Mon, 10 Aug 2015 18:17:30 -0600 as excerpted:
> On Mon, 10 Aug 2015 12:25:58 + (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>> What about:
>>
>> * bug number in summary strongly recommended
>
> Making the bug number in the summary manditory or strongly encouraged
> leads
Gordon Pettey posted on Mon, 10 Aug 2015 17:57:56 -0500 as excerpted:
> On Mon, Aug 10, 2015 at 7:25 AM, Duncan <1i5t5.dun...@cox.net> wrote:
>
>> ** summary bug number standardized to GB#xx or #xx or similar,
>> short enough for summary, easily identified. GB# would be distinctly
>> gent
On Mon, 10 Aug 2015 23:43:29 +0300
Andrew Savchenko wrote:
> On Mon, 10 Aug 2015 15:11:02 +0200 Michał Górny wrote:
> > > > > 2. Bug number can be easily typed, URL has to be copied or
> > > > > generated by some tool.
> > > >
> > > > So, please remind me, how many times the 'easy typing' got th
On Mon, 10 Aug 2015 12:25:58 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:
> What about:
>
> * bug number in summary strongly recommended
> ** summary bug number standardized to GB#xx or #xx or similar,
> short enough for summary, easily identified. GB# would be distinctly
> gentoo an
On Mon, Aug 10, 2015 at 7:25 AM, Duncan <1i5t5.dun...@cox.net> wrote:
> ** summary bug number standardized to GB#xx or #xx or similar,
> short enough for summary, easily identified. GB# would be distinctly
> gentoo and could be expanded to KDEB#, GNB# (gnome), FDOB#, etc, for
>
If you're
All,
this variable can be computed in the eclass using ${EGO_PN/%*}, so there
is no need to have a separate variable.
This patch removes it.
William
From ded07bc7b61183a737d2bf6a911f29639617b015 Mon Sep 17 00:00:00 2001
From: William Hubbs
Date: Sun, 9 Aug 2015 12:04:36 -0500
Subject: [PATCH]
Dnia 2015-08-10, o godz. 23:43:29
Andrew Savchenko napisał(a):
> On Mon, 10 Aug 2015 15:11:02 +0200 Michał Górny wrote:
> > > > > 2. Bug number can be easily typed, URL has to be copied or
> > > > > generated by some tool.
> > > >
> > > > So, please remind me, how many times the 'easy typing' go
> Users can fetch/pull from Github.
We could also provide automatic signed tags every 30min/1h/2h/whatever
(signed with a suitable infrastructure key). With that, the integrity of
a tagged git checkout can be easily verified on client side.
Best,
Matthias
signature.asc
Description: PGP signatu
Dnia 2015-08-10, o godz. 23:49:55
Andrew Savchenko napisał(a):
> On Mon, 10 Aug 2015 23:47:21 +0300 Andrew Savchenko wrote:
> > On Mon, 10 Aug 2015 22:13:23 +0200 hasufell wrote:
> > > On 08/10/2015 05:09 PM, Rich Freeman wrote:
> > > > On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert
> > > > wro
Dnia 2015-08-10, o godz. 23:47:21
Andrew Savchenko napisał(a):
> On Mon, 10 Aug 2015 22:13:23 +0200 hasufell wrote:
> > On 08/10/2015 05:09 PM, Rich Freeman wrote:
> > > On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
> > >>
> > >> Expanding on this: the rsync master creates the following
On 2015-08-10 23:49, Andrew Savchenko wrote:
> Another issue: we will have to setup git mirrors as well (probably
> reusing hosts providing rsync mirrors). I really doubt current
> infrastructure will survive if all users will sync from its git.
Users can fetch/pull from Github.
https://github.co
On 08/10/2015 10:47 PM, Andrew Savchenko wrote:
> On Mon, 10 Aug 2015 22:13:23 +0200 hasufell wrote:
>> On 08/10/2015 05:09 PM, Rich Freeman wrote:
>>> On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
Expanding on this: the rsync master creates the following
files/directories u
On Mon, 10 Aug 2015 23:47:21 +0300 Andrew Savchenko wrote:
> On Mon, 10 Aug 2015 22:13:23 +0200 hasufell wrote:
> > On 08/10/2015 05:09 PM, Rich Freeman wrote:
> > > On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
> > >>
> > >> Expanding on this: the rsync master creates the following
> > >>
On Mon, 10 Aug 2015 22:13:23 +0200 hasufell wrote:
> On 08/10/2015 05:09 PM, Rich Freeman wrote:
> > On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
> >>
> >> Expanding on this: the rsync master creates the following
> >> files/directories under metatdata. On my own system, I like to symlink
On Mon, 10 Aug 2015 15:11:02 +0200 Michał Górny wrote:
> > > > 2. Bug number can be easily typed, URL has to be copied or
> > > > generated by some tool.
> > >
> > > So, please remind me, how many times the 'easy typing' got the bug
> > > number wrong? This is not a real argument, just another of
On 08/10/2015 05:09 PM, Rich Freeman wrote:
> On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
>>
>> Expanding on this: the rsync master creates the following
>> files/directories under metatdata. On my own system, I like to symlink
>> them to locations outside my repo so that related portage
Monday 10 Aug 2015 12:02:25, Daniel Campbell (zlg) wrote :
> On 08/10/2015 06:15 AM, Doug Goldstein wrote:
> > On Mon, Aug 10, 2015 at 3:36 AM, Chí-Thanh Christopher Nguyễn
> > wrote:
> >> Doug Goldstein schrieb:
> >>> gpg: cancelled by user gpg: skipped "0xA2BC03DC87ED1BD4":
> >>> Operation canc
On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
> On Mon, Aug 10, 2015 at 2:42 AM, Mike Frysinger wrote:
>> On 10 Aug 2015 08:28, Justin (jlec) wrote:
>>> how do we maintain this file?
>>
>> like any other file. git add && git commit.
>>
>>> I like to propose to add the md5-cache into it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/10/2015 06:15 AM, Doug Goldstein wrote:
> On Mon, Aug 10, 2015 at 3:36 AM, Chí-Thanh Christopher Nguyễn
> wrote:
>> Doug Goldstein schrieb:
>>> gpg: cancelled by user gpg: skipped "0xA2BC03DC87ED1BD4":
>>> Operation cancelled gpg: signing fai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michał Górny schrieb:
>> I prefer the
>>
>> Bugzilla: https://bugs.gentoo.org/show_bug.cgi?id=333531
>>
>> format even though not all bug trackers are running Bugzilla. "Bug: "
>> works fine with me too, and we could make
>> "https://bugs.gentoo.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/10/2015 08:09 AM, Rich Freeman wrote:
> On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert
> wrote:
>>
>> Expanding on this: the rsync master creates the following
>> files/directories under metatdata. On my own system, I like to
>> symlink them
On Mon, Aug 10, 2015 at 11:04 AM, Mike Gilbert wrote:
>
> Expanding on this: the rsync master creates the following
> files/directories under metatdata. On my own system, I like to symlink
> them to locations outside my repo so that related portage features
> continue to work.
>
> I would like to
On Mon, Aug 10, 2015 at 2:42 AM, Mike Frysinger wrote:
> On 10 Aug 2015 08:28, Justin (jlec) wrote:
>> how do we maintain this file?
>
> like any other file. git add && git commit.
>
>> I like to propose to add the md5-cache into it. Which other files are of
>> interest?
>
> /distfiles/
> /local
On 08/10/2015 03:19 PM, Michał Górny wrote:
>
> Thanks, this is exactly what I wanted.
>
> "Fixes", "References", "Bug" are all good. "Bugzilla" goes against your
> proposal diverging keyword depending on bug tracker software.
>
Afaik "Fixes: " is for referencing commits, not bug reports.
And
This is now committed.
William
signature.asc
Description: Digital signature
On 8/10/15 3:35 AM, Justin (jlec) wrote:
On 10/08/15 08:42, Mike Frysinger wrote:
On 10 Aug 2015 08:28, Justin (jlec) wrote:
how do we maintain this file?
like any other file. git add && git commit.
I rather meant, if this file should only be modified after a discussion in a bug
or on a ml.
Dnia 2015-08-10, o godz. 11:45:33
Chí-Thanh Christopher Nguyễn napisał(a):
> Ulrich Mueller schrieb:
> >> This is not a matter of going l33t, this is a matter of getting rid of
> >> redundant and pretty much useless data all the same through almost all
> >> commit messages.
> >
> > +1
> >
> > "
On Mon, Aug 10, 2015 at 3:36 AM, Chí-Thanh Christopher Nguyễn
wrote:
> Doug Goldstein schrieb:
>> gpg: cancelled by user
>> gpg: skipped "0xA2BC03DC87ED1BD4": Operation cancelled
>> gpg: signing failed: Operation cancelled
>> error: gpg failed to sign the data
>
> There was an IRC discussion yeste
On Sun, Aug 9, 2015 at 9:00 PM, Kent Fredric wrote:
> On 10 August 2015 at 13:40, Doug Goldstein wrote:
>> $ git push --signed origin master
>>
>> You need a passphrase to unlock the secret key for
>> user: "Doug Goldstein "
>> 4096-bit RSA key, ID 0xA2BC03DC87ED1BD4, created 2015-04-24
>>
Dnia 2015-08-10, o godz. 02:16:01
Andrew Savchenko napisał(a):
> On Mon, 10 Aug 2015 00:40:44 +0200 Michał Górny wrote:
> > > > Which is terribly redundant. Just put the whole bug URL. Advantages:
> > > >
> > > > - keeps the bug namespaced to bugs.gentoo.org,
> > > > - has the bug no inside,
> >
hasufell posted on Mon, 10 Aug 2015 03:02:43 +0200 as excerpted:
> On 08/10/2015 02:51 AM, Ulrich Mueller wrote:
>>> On Mon, 10 Aug 2015, Andrew Savchenko wrote:
>>
>>> This is not a matter of going l33t, this is a matter of getting rid of
>>> redundant and pretty much useless data all the sa
On 08/10/2015 10:00 AM, Mike Frysinger wrote:
> commit: 2f168392284fec294f9bfbb06d1c0a8a46f5a7d5
> Author: Mike Frysinger gentoo org>
> AuthorDate: Mon Aug 10 07:39:36 2015 +
> Commit: Mike Frysinger gentoo org>
> CommitDate: Mon Aug 10 07:59:50 2015 +
> URL:https://
> On Mon, 10 Aug 2015, Chí-Thanh Christopher Nguyễn wrote:
> I prefer the
> Bugzilla: https://bugs.gentoo.org/show_bug.cgi?id=333531
> format even though not all bug trackers are running Bugzilla.
> "Bug: " works fine with me too,
There are bug trackers other than bugzilla, for example
debb
Ulrich Mueller schrieb:
>> This is not a matter of going l33t, this is a matter of getting rid of
>> redundant and pretty much useless data all the same through almost all
>> commit messages.
>
> +1
>
> "Gentoo-Bug: 123456" or even "Bug: 123456" is enough to uniquely
> identify a bug. Also it is
Doug Goldstein schrieb:
> gpg: cancelled by user
> gpg: skipped "0xA2BC03DC87ED1BD4": Operation cancelled
> gpg: signing failed: Operation cancelled
> error: gpg failed to sign the data
There was an IRC discussion yesterday about this. Probably your pinentry
tries to talk to a GUI and fails. Try:
On 10/08/15 08:42, Mike Frysinger wrote:
> On 10 Aug 2015 08:28, Justin (jlec) wrote:
>> how do we maintain this file?
>
> like any other file. git add && git commit.
>
I rather meant, if this file should only be modified after a discussion in a bug
or on a ml. Or if only QA is modifying this f
On Sun, 9 Aug 2015 17:02:27 -0700 Daniel Campbell (zlg) wrote:
> I don't know about you guys, but I have a "smart bookmark" in Firefox
> where I type "bgo xx" and it'll take me to the relevant bug. It'd
> be trivial to set that up as a bash alias, too. There are tons of ways
> to get to a bug;
On 10 Aug 2015 09:17, Michał Górny wrote:
> Dnia 2015-08-10, o godz. 02:42:21 Mike Frysinger napisał(a):
> > On 10 Aug 2015 08:28, Justin (jlec) wrote:
> > > I like to propose to add the md5-cache into it. Which other files are of
> > > interest?
> >
> > /distfiles/
> > /local/
> > /packages/
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/08/15 21:38, Sergey Popov wrote:
>
>
> In short - apropriate REQUIRED_USE with setting recommended
> USE-flag(e.g. USE="+qt4 qt5" or USE="qt4 +qt5")
>
>
Strong -1.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
--
Dnia 2015-08-10, o godz. 02:42:21
Mike Frysinger napisał(a):
> On 10 Aug 2015 08:28, Justin (jlec) wrote:
> > how do we maintain this file?
>
> like any other file. git add && git commit.
>
> > I like to propose to add the md5-cache into it. Which other files are of
> > interest?
>
> /distfi
49 matches
Mail list logo
