Hi,
Am 13.01.2017 um 03:22 schrieb niya levi via arch-general:
> how do i go about diagnosing and fixing the problem,
> any suggestions or guidance would be appreciated.
> shadrock
Check all cables and re-plug them. To narrow down the problem you can
also swap arond disks, so you know whether it
So my current workflow allows doing everything on soyuz. I tried it
out for a couple of packages, it works well and FWICT it's secure.
Writeup on the setup below as requested on IRC the other day.
Local prerequisites:
- Extra socket must be enabled. In arch, that seems to be the case by
def
On Wed, Jan 18, 2017 at 8:21 PM Lukas Jirkovsky via arch-general <
arch-general@archlinux.org> wrote:
> I use only the ssh agent forwarding ("ForwardAgent yes" in
> .ssh/config). On pkgbuild.com I build packages using the *-*-build as
> always. When a package is built, I use a script [1] that down
On Tue, Jan 17, 2017 at 11:39:10PM +0600, Rashif Ray Rahman wrote:
> Thanks guys for all the info you have been sharing, I got sloppy again
> and went into full panic mode in preparation for my master's thesis
> and subsequent defense (19th).
Good luck, break a leg, etc. !
--
FA
A world of e
On 17 January 2017 at 08:42, Jerome Leclanche wrote:
> What is the current intended way to sign packages on the pkgbuild.com server?
I don't think there's any.
> I spent the past day setting up agent forwarding
> (https://wiki.gnupg.org/AgentForwarding) for it. Had a lot of trouble
> setting it
5 matches
Mail list logo
