Hi,
Am Freitag, 18. Juni 2021, 17:21:43 CEST schrieb alad via aur-general:
> On 18/06/2021 16:43, Jonathon Fernyhough via aur-general wrote:
> > On 18/06/2021 14:05, Jan Kohnert via aur-general wrote:
> >> a new version of a (binary) package I'm maintaining (clockify-desktop)
> >> requires an exec
Le ven. 18 juin 2021 20:00, Caleb Maclennan via aur-general <
aur-general@lists.archlinux.org> a écrit :
> On 2021-06-11 03:16, Archange wrote:
> > so let’s start the discussion period.
>
> This message is a short public service announcement reminding all
> current TUs that today is the halfway po
On 18/06/2021 18:59, Caleb Maclennan via aur-general wrote:
> On 2021-06-11 03:16, Archange wrote:
>> so let’s start the discussion period.
>
> This message is a short public service announcement reminding all
> current TUs that today is the halfway point of the discussion period on
> my applica
On 2021-06-11 03:16, Archange wrote:
> so let’s start the discussion period.
This message is a short public service announcement reminding all
current TUs that today is the halfway point of the discussion period on
my application. I know packagers tend to be the easily distracted types
that wander
On 18/06/2021 16:21, alad via aur-general wrote:
> On 18/06/2021 16:43, Jonathon Fernyhough via aur-general wrote:
>> ...
>> Or, is an executable /tmp a reasonable assumption? 🤔
>
> I don't see anything in file-hierarchy(7) that mandates an executable
> /tmp. That said, it contains a hint that som
On 18/06/2021 16:43, Jonathon Fernyhough via aur-general wrote:
On 18/06/2021 14:05, Jan Kohnert via aur-general wrote:
Hi,
a new version of a (binary) package I'm maintaining (clockify-desktop) requires
an
executable /tmp directory to run.
My immediate questions would be why, and is this an
On 18/06/2021 14:05, Jan Kohnert via aur-general wrote:
> Hi,
>
> a new version of a (binary) package I'm maintaining (clockify-desktop)
> requires an
> executable /tmp directory to run.
>
My immediate questions would be why, and is this an upstream issue?
Or, is an executable /tmp a reasonab
On June 18, 2021 9:05:31 AM EDT, Jan Kohnert via aur-general
wrote:
> Hi,
>
> a new version of a (binary) package I'm maintaining (clockify-desktop)
> requires an
> executable /tmp directory to run.
>
> So I'd thought about adding a warning to the PKGBUILD if /tmp is
> mounted
> noexec (as on
On 2021-06-18 14:35:24 (+0100), Morgan Adamiec via aur-general wrote:
> Hey there!
>
> I'm Morgan, Morganamilo in most places and I'd like to apply to become a
> Trusted User with dvzrv and kpcyrd's sponsorship.
I confirm my sponsorship.
Let the discussion period begin! :)
--
https://sleepmap.
On Fri, Jun 18, 2021 at 02:35:24PM +0100, Morgan Adamiec via aur-general wrote:
> I'm Morgan, Morganamilo in most places and I'd like to apply to become a
> Trusted User with dvzrv and kpcyrd's sponsorship.
I confirm my sponsorship.
signature.asc
Description: PGP signature
Hey there!
I'm Morgan, Morganamilo in most places and I'd like to apply to become a
Trusted User with dvzrv and kpcyrd's sponsorship.
I've been an avid Arch user for the past 5 or so years. I started
dipping my toes into the community with some wiki edits, bug reporting
and submitted my first AUR
Hi,
a new version of a (binary) package I'm maintaining (clockify-desktop) requires
an
executable /tmp directory to run.
So I'd thought about adding a warning to the PKGBUILD if /tmp is mounted
noexec (as on all of my maschines). Unfortunately I could not find a hint in
the
documentation if
12 matches
Mail list logo