On Monday 16 November 2015 17:32:56 Rich Freeman wrote:
>On Mon, Nov 16, 2015 at 4:49 PM, Marc Joliet wrote:
>> Don't forget that in Gentoo all commits are also GPG signed.
>
>Sure, but to be fair those signatures are only bound to the content of
>the commit by an sha1 hash.
Ah! Thanks, I didn't
On Mon, Nov 16, 2015 at 4:49 PM, Marc Joliet wrote:
>
> Don't forget that in Gentoo all commits are also GPG signed.
>
Sure, but to be fair those signatures are only bound to the content of
the commit by an sha1 hash.
--
Rich
On Monday 16 November 2015 17:21:07 Martin Vaeth wrote:
>cov...@ccs.covici.com wrote:
>> I have thinmanifests=true as specified in some news item or post, I
>> think this was a mandatory change some time ago using rsync.
>
>If you really use rsync/webrsync and not git, this is unlikely:
>The file
cov...@ccs.covici.com wrote:
>
> I have thinmanifests=true as specified in some news item or post, I
> think this was a mandatory change some time ago using rsync.
If you really use rsync/webrsync and not git, this is unlikely:
The file containing this line (metadata/layout.conf) should be
overri
On Mon, 16 Nov 2015 03:48:52 -0600, Dale wrote:
> > According to https://bugs.gentoo.org/show_bug.cgi?id=565694 it has
> > been fixed, I synced too early this morning to pick that up.
> I synced again just a hour or two ago and I must have missed it too. It
> spit out the same error as before.
Neil Bothwick wrote:
> On Sun, 15 Nov 2015 17:39:29 -0800, walt wrote:
>
>
>> I hope the gentoo devs will fix this bug before you have a chance to
>> test my advice :)
> According to https://bugs.gentoo.org/show_bug.cgi?id=565694 it has been
> fixed, I synced too early this morning to pick that up.
On Sun, 15 Nov 2015 17:39:29 -0800, walt wrote:
> > I have the same wrong size recorded in the Manifest!
> > No idea why portage didn't yell at me - there seems
> > to be another bug involved...
>
> I did the same thing today (15 Nov) and it succeeded.
>
> However, I ran the ebuild command on
Grant Edwards wrote:
> On 2015-11-15, Dale wrote:
>
>> Wasn't there a emerge option to ignore the manifest? I seem to recall
>> there used to be one but it was a LONG time ago. Of course, if someone
>> has tinkered with something that would be a bad thing to do.
> If the digest failures are for
Martin Vaeth wrote:
> Simon Thelen wrote:
> > I sync from git and none of my Manifests track the ebuilds, so this
> > could be a thing.
>
> No. git has (probably, I didn't check)
> thin-manifests = true
> in its metadata/layout.conf, but for rsync this should
> not be the case for security reas
Simon Thelen wrote:
> I sync from git and none of my Manifests track the ebuilds, so this
> could be a thing.
No. git has (probably, I didn't check)
thin-manifests = true
in its metadata/layout.conf, but for rsync this should
not be the case for security reasons. I double-checked,
and I have inde
On Sun, 15 Nov 2015 19:05:26 + (UTC)
Martin Vaeth wrote:
> Neil Bothwick wrote:
> >
> > I deleted the busybox directory from the tree then ran emerge
> > --sync. The error is still there
>
> You have the same files that I have.
> Unfortunately, only now I actually did:
>
> $ grep busybox
On 15 November 2015 09:59:28 GMT+00:00, Alan Mackenzie wrote:
> On Thu, Nov 12, 2015 at 06:45:44PM +0200, Alan McKinnon wrote:
> > On 12/11/2015 18:42, Grant Edwards wrote:
> > > On 2015-11-12, wrote:
> > >> Grant Edwards wrote:
>
> > >>> After an emerge --sync that appeared to work with no pr
> On Nov 15, 2015, at 21:33, Alan Mackenzie wrote:
>
> Hello, Matti.
>
> I deleted my /usr/portage (with the exception of
> /usr/portage/distfiles), and ran emerge --sync again. I get precisely
> the same error message, still.
I rsync with rsync.europe.gentoo.org and with me the manifest with
On 15-11-15 at 15:29, cov...@ccs.covici.com wrote:
> Dale wrote:
> > Martin Vaeth wrote:
> > > Neil Bothwick wrote:
[..]
> > > As a temporary hack, calling "ebuild manifest" on that file is
> > > probably the only reasonable way to proceed, but this problem
> > > must be fixed, of course...
> > W
On 2015-11-15, Dale wrote:
> Wasn't there a emerge option to ignore the manifest? I seem to recall
> there used to be one but it was a LONG time ago. Of course, if someone
> has tinkered with something that would be a bad thing to do.
If the digest failures are for packages you don't have inst
Dale wrote:
> Martin Vaeth wrote:
> > Neil Bothwick wrote:
> >> I deleted the busybox directory from the tree then ran emerge --sync.
> >> The error is still there
> > You have the same files that I have.
> > Unfortunately, only now I actually did:
> >
> > $ grep busybox- Manifest
> > EBUILD
Martin Vaeth wrote:
> Neil Bothwick wrote:
>> I deleted the busybox directory from the tree then ran emerge --sync.
>> The error is still there
> You have the same files that I have.
> Unfortunately, only now I actually did:
>
> $ grep busybox- Manifest
> EBUILD busybox-.ebuild 8580 [...]
Hello, Matti.
On Sun, Nov 15, 2015 at 01:15:16PM +0200, Matti Nykyri wrote:
> > On Nov 15, 2015, at 13:01, Alan Mackenzie wrote:
> >> Well it's not. It just checks all the manifests and complains about
> >> errors. It doesn't affect the building of 1.23.1-r1.
> Ok. I must be using some differen
Hello, Martin.
On Sun, Nov 15, 2015 at 02:56:42PM +, Martin Vaeth wrote:
> Alan Mackenzie wrote:
> >!!! /usr/portage/sys-apps/busybox/busybox-.ebuild
> >!!! Got: 8493
> >!!! Expected: 8580
> Do you use the default (rsync) for syncing, or have you changed
> the method?
rsync
Neil Bothwick wrote:
>
> I deleted the busybox directory from the tree then ran emerge --sync.
> The error is still there
You have the same files that I have.
Unfortunately, only now I actually did:
$ grep busybox- Manifest
EBUILD busybox-.ebuild 8580 [...]
???
I have the same wrong siz
On Sun, 15 Nov 2015 14:56:42 + (UTC), Martin Vaeth wrote:
> >!!! /usr/portage/sys-apps/busybox/busybox-.ebuild
> >!!! Got: 8493
> >!!! Expected: 8580
>
> Do you use the default (rsync) for syncing, or have you changed
> the method?
>
> I have the above claimed filesize (849
Alan Mackenzie wrote:
>!!! /usr/portage/sys-apps/busybox/busybox-.ebuild
>!!! Got: 8493
>!!! Expected: 8580
Do you use the default (rsync) for syncing, or have you changed
the method?
I have the above claimed filesize (8493), but the Manifest
I obtained from rsync is correct.
Th
On Sunday 15 Nov 2015 12:56:16 Matti Nykyri wrote:
> > On Nov 15, 2015, at 12:43, Peter Humphrey
wrote:
> > I'm getting the same thing as Alan, and have been for several days.
> >
> >> If I were you I'ld download the latest portage snapshot. That should
> >> take care of any remaining issues. Is
On Sun, 15 Nov 2015 09:59:28 +, Alan Mackenzie wrote:
> [ebuild R] sys-apps/busybox-1.23.1-r1 USE="-pam*"
>
> , and the error message I get on actually trying to start the update is
>
> !!! Digest verification failed:
> !!! /usr/portage/sys-apps/busybox/busybox-.ebuild
> On Nov 15, 2015, at 13:01, Alan Mackenzie wrote:
>
>> Well it's not. It just checks all the manifests and complains about
>> errors. It doesn't affect the building of 1.23.1-r1.
Ok. I must be using some different switch then.
> Ah, OK. But it causes emerge to bail out, so never gets round to
Hello, Matti
On Sun, Nov 15, 2015 at 12:22:39PM +0200, Matti Nykyri wrote:
> > On Nov 15, 2015, at 11:59, Alan Mackenzie wrote:
> >> On Thu, Nov 12, 2015 at 06:45:44PM +0200, Alan McKinnon wrote:
> >>> On 12/11/2015 18:42, Grant Edwards wrote:
> On 2015-11-12, wrote:
> Grant Edwards
> On Nov 15, 2015, at 12:43, Peter Humphrey wrote:
>
> On Sunday 15 Nov 2015 12:22:39 Matti Nykyri wrote:
>>> On Nov 15, 2015, at 11:59, Alan Mackenzie wrote:
> --->8
>>> Three days later. I'm still getting this error message, but with a
>>> nasty
>>> twist in the tail. emerge -puND @world rep
On Sunday 15 Nov 2015 12:22:39 Matti Nykyri wrote:
> > On Nov 15, 2015, at 11:59, Alan Mackenzie wrote:
--->8
> > Three days later. I'm still getting this error message, but with a
> > nasty
> > twist in the tail. emerge -puND @world reports (amongst others) the
> >
> > following update:
> >
> On Nov 15, 2015, at 11:59, Alan Mackenzie wrote:
>
>> On Thu, Nov 12, 2015 at 06:45:44PM +0200, Alan McKinnon wrote:
>>> On 12/11/2015 18:42, Grant Edwards wrote:
On 2015-11-12, wrote:
Grant Edwards wrote:
>
> After an emerge --sync that appeared to work with no problems, my
>
On Thu, Nov 12, 2015 at 06:45:44PM +0200, Alan McKinnon wrote:
> On 12/11/2015 18:42, Grant Edwards wrote:
> > On 2015-11-12, wrote:
> >> Grant Edwards wrote:
> >>> After an emerge --sync that appeared to work with no problems, my
> >>> "emerge -auvND world" command is reporting that the Change
Grant Edwards wrote:
> On 2015-11-12, wrote:
>> Grant Edwards wrote:
>>
>>> After an emerge --sync that appeared to work with no problems, my
>>> "emerge -auvND world" command is reporting that the Changelong files
>>> are broken for about 2/3 of the packages it wants to update:
>>>
>>> !!! Dige
On Thursday 12 Nov 2015 18:45:44 Alan McKinnon wrote:
> On 12/11/2015 18:42, Grant Edwards wrote:
> > On 2015-11-12, wrote:
> >> Grant Edwards wrote:
> >>> After an emerge --sync that appeared to work with no problems, my
> >>> "emerge -auvND world" command is reporting that the Changelong files
On 12/11/2015 18:42, Grant Edwards wrote:
> On 2015-11-12, wrote:
>> Grant Edwards wrote:
>>
>>> After an emerge --sync that appeared to work with no problems, my
>>> "emerge -auvND world" command is reporting that the Changelong files
>>> are broken for about 2/3 of the packages it wants to upd
On 2015-11-12, wrote:
> Grant Edwards wrote:
>
>> After an emerge --sync that appeared to work with no problems, my
>> "emerge -auvND world" command is reporting that the Changelong files
>> are broken for about 2/3 of the packages it wants to update:
>>
>> !!! Digest verification failed:
>> !!
34 matches
Mail list logo
