On 6/16/19 4:21 PM, Jonathon Fernyhough wrote:
> On 16/06/2019 21:12, Marc Ranolfi via arch-general wrote:
>> I think it's also possible to have only one package (and two config files
>> 'config.i686' and 'config.x86_64'). But I don't know if that is good
>> practice.
>
> This is definitely possib
On 16/06/2019 21:12, Marc Ranolfi via arch-general wrote:
> I think it's also possible to have only one package (and two config files
> 'config.i686' and 'config.x86_64'). But I don't know if that is good
> practice.
This is definitely possible and the approach Manjaro currently uses for
`arch=(i6
Thank you David.
If I may ask a related question - considering this package would be most
useful for Arch Linux 32, how should I provide support for both x86_64 and
i686?
The kernel packages I've seen in the AUR only support x86_64.
Should I make two separate packages - i.e. one like "i686-
linu
On June 16, 2019 5:57:34 PM GMT+02:00, Eli Schwartz via arch-general
wrote:
>That being said, if you have signed the repository db then as you
>mentioned the sha256 checksums for the package file are securely
>signed,
>so you are guaranteed that use of pacman -S pkgname will securely
>verify
>tha
On 6/15/19 5:12 PM, Genes Lists via arch-general wrote:
...
>
> I need to do more work ... perhaps test with the --madadmconf flag when
> building the initrd is next step.
>
I confirm that building the initrd with --mdadmconf fixes the problem
assembling the raid disks using dracut - this happen
On 6/16/19 10:44 AM, brent s. wrote:
> On 6/16/19 5:03 AM, Manuel Reimer wrote:
>> Hello,
>>
>> I run a repository locally that I would like to share to the public.
>>
>> The build is mostly automated. That's why I don't want to sign each
>> individual package. The private key is not stored on the
On 6/16/19 5:03 AM, Manuel Reimer wrote:
> Hello,
>
> I run a repository locally that I would like to share to the public.
>
> The build is mostly automated. That's why I don't want to sign each
> individual package. The private key is not stored on the build machine
> and I want to sign the resu
Hello,
I run a repository locally that I would like to share to the public.
The build is mostly automated. That's why I don't want to sign each
individual package. The private key is not stored on the build machine
and I want to sign the resulting stuff externally.
The easiest way would be a
8 matches
Mail list logo