On Wed, Dec 14, 2016 at 10:52 AM, M. J. Everitt wrote:
> I would tend to agree that in a sysadmin role this would be very helpful.
>
> At the risk of repeating myself, is there any einfo/elog displayed when
> portage is (first) updated, to alert users of this functionality? A link
> to the wiki pa
On 14/12/16 15:45, Rich Freeman wrote:
> On Wed, Dec 14, 2016 at 10:27 AM, M. J. Everitt wrote:
>> I do, but only usually if its the last package of an emerge because
>> otherwise its lost many many thousands of lines upwards. Thank goodness
>> for portage's savelog feature. - Actually that remind
On Wed, Dec 14, 2016 at 10:27 AM, M. J. Everitt wrote:
>
> I do, but only usually if its the last package of an emerge because
> otherwise its lost many many thousands of lines upwards. Thank goodness
> for portage's savelog feature. - Actually that reminds me .. someone
> mentioned a useful tweak
On 14/12/16 14:57, Mike Gilbert wrote:
> On Wed, Dec 14, 2016 at 9:07 AM, M. J. Everitt wrote:
>> On 14/12/16 13:53, Mike Gilbert wrote:
>>> On Wed, Dec 14, 2016 at 7:56 AM, Mart Raudsepp wrote:
Ühel kenal päeval, K, 14.12.2016 kell 15:35, kirjutas Andrew Savchenko:
> This is not a worka
On Wed, Dec 14, 2016 at 9:07 AM, M. J. Everitt wrote:
> On 14/12/16 13:53, Mike Gilbert wrote:
>> On Wed, Dec 14, 2016 at 7:56 AM, Mart Raudsepp wrote:
>>> Ühel kenal päeval, K, 14.12.2016 kell 15:35, kirjutas Andrew Savchenko:
This is not a workaround, but officially recommended practice, f
On 14/12/16 13:53, Mike Gilbert wrote:
> On Wed, Dec 14, 2016 at 7:56 AM, Mart Raudsepp wrote:
>> Ühel kenal päeval, K, 14.12.2016 kell 15:35, kirjutas Andrew Savchenko:
>>> This is not a workaround, but officially recommended practice, from
>>> man gpg-agent:
>>>
>>> You should always add the fol
On Wed, Dec 14, 2016 at 7:56 AM, Mart Raudsepp wrote:
> Ühel kenal päeval, K, 14.12.2016 kell 15:35, kirjutas Andrew Savchenko:
>> On Wed, 14 Dec 2016 11:16:58 +0200 Mart Raudsepp wrote:
>> >
>> > Ühel kenal päeval, K, 14.12.2016 kell 13:08, kirjutas Sam Jorna:
>> > >
>> > > On Mon, Dec 12, 2016 a
Ühel kenal päeval, K, 14.12.2016 kell 15:35, kirjutas Andrew Savchenko:
> On Wed, 14 Dec 2016 11:16:58 +0200 Mart Raudsepp wrote:
> >
> > Ühel kenal päeval, K, 14.12.2016 kell 13:08, kirjutas Sam Jorna:
> > >
> > > On Mon, Dec 12, 2016 at 02:35:28PM +1100, Sam Jorna wrote:
> > > >
> > > >
> > >
On Wed, 14 Dec 2016 11:16:58 +0200 Mart Raudsepp wrote:
> Ühel kenal päeval, K, 14.12.2016 kell 13:08, kirjutas Sam Jorna:
> > On Mon, Dec 12, 2016 at 02:35:28PM +1100, Sam Jorna wrote:
> > >
> > > On Mon, Dec 12, 2016 at 09:34:21AM +0700, gro...@gentoo.org wrote:
> > > >
> > > > On Sun, 11 Dec 2
On 14-12-2016 11:16:58 +0200, Mart Raudsepp wrote:
> Ühel kenal päeval, K, 14.12.2016 kell 13:08, kirjutas Sam Jorna:
> > If anyone else is getting this, it seems to be resolved by exporting
> > GPG_TTY=$(tty) either immediately before attempting to sign or in
> > your
> > shell ~/.*rc file.
>
>
Ühel kenal päeval, K, 14.12.2016 kell 13:08, kirjutas Sam Jorna:
> On Mon, Dec 12, 2016 at 02:35:28PM +1100, Sam Jorna wrote:
> >
> > On Mon, Dec 12, 2016 at 09:34:21AM +0700, gro...@gentoo.org wrote:
> > >
> > > On Sun, 11 Dec 2016, Kristian Fiskerstrand wrote:
> > > >
> > > > On 12/11/2016 03:
On Mon, Dec 12, 2016 at 02:35:28PM +1100, Sam Jorna wrote:
> On Mon, Dec 12, 2016 at 09:34:21AM +0700, gro...@gentoo.org wrote:
> > On Sun, 11 Dec 2016, Kristian Fiskerstrand wrote:
> > > On 12/11/2016 03:13 PM, gro...@gentoo.org wrote:
> > >> gpg: signing failed: Inappropriate ioctl for device
> >
On Mon, Dec 12, 2016 at 09:34:21AM +0700, gro...@gentoo.org wrote:
> On Sun, 11 Dec 2016, Kristian Fiskerstrand wrote:
> > On 12/11/2016 03:13 PM, gro...@gentoo.org wrote:
> >> gpg: signing failed: Inappropriate ioctl for device
> > this might indicate a want for export GPG_TTY=$(tty)
> I don't und
On Sun, 11 Dec 2016, Kristian Fiskerstrand wrote:
On 12/11/2016 03:13 PM, gro...@gentoo.org wrote:
gpg: signing failed: Inappropriate ioctl for device
this might indicate a want for export GPG_TTY=$(tty)
I don't understand what has really happened. I removed my last commit, an
attempt to commi
On 12/11/2016 03:13 PM, gro...@gentoo.org wrote:
> gpg: signing failed: Inappropriate ioctl for device
this might indicate a want for export GPG_TTY=$(tty)
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
On 2016-12-11 15:13, gro...@gentoo.org wrote:
> But this commit sits in my copy of the tree, and I cannot
> push it. What can I do?
You can't push because the commit isn't signed?
If it is the last commit, just run `git commit --amend -S`
If it isn't the last commit, try `git log` to get the com
Hello *,
Today, when trying to push my commit to the repo, I got
gpg: signing failed: Inappropriate ioctl for device
gpg: signing failed: Inappropriate ioctl for device
error: gpg failed to sign the data
fatal: failed to sign the push certificate
fatal: The remote end hung up unexpectedly
When
17 matches
Mail list logo