On Mon, 2023-09-04 at 23:16 +0100, Polarian wrote:
>On Mon, 2023-09-04 at 12:20 -0700, Xavier Baez wrote:
> > I would like to know what the rules are, today at Labor Day 3 AM the change
> > requests arrive again, yesterday I had to leave church to come home and do
> > more changes Test the package,
AUR TUs are kinda busy and they don't delete things immediately. I'm not
sure why they want you to remove the conflicts before it is deleted but
that's not why xiota accused you of incompetence either.
Also, please include aur-general in your replies. If your email client
has a "reply to list"
Il 05/09/23 00:56, Xavier Baez ha scritto:
I want to maintain the package.
motivewave-latest-bin was supposed to be deleted yesterday.
If that package is removed then motivewave wouldn’t have any conflicting
packages.
motivewave-latest-bin package was removed in order to make you sleep wel
I want to maintain the package.
motivewave-latest-bin was supposed to be deleted yesterday.
If that package is removed then motivewave wouldn’t have any conflicting
packages.
motivewave has motivewave-latest-bin listed as conflicts (which is accurate)
And motivewave-latest-bin has motivewave lis
I don't see why you're that infuriated. xiota is indeed a bit combative
with language but save for removing `conflicts` their suggestions all
look good. Simply adding the "no same owner" removes the need for all
that find chmod and chown stuff and just put the conflicting packing
name under "c
Hello Xavier, for the fifth time today
Hello
I would like the community to help and decide on what to do.
I am the maintainer of motivewave
There is a person that went and created a duplicate motivewave-latest-bin
and went and publicly said I am incompetent and insinuated I was stupid.
The
On 23/09/02 01:24AM, Christian Heusel wrote:
> On 8/28/23 21:01, Christian Heusel wrote:
> > On 8/24/23 13:08, Christian Heusel wrote:
> > > On 23/08/24 01:33AM, Christian Heusel wrote:
> > > > Most of our worflows have moved from mailing lists and patches to merge
> > > > requests on gitlab. Until
The variable they recommended was build_id
but that didn't create a clean
makepkg --printsrcinfo > .SRCINFO
Here are some of the comments, it's like
https://aur.archlinux.org/packages/motivewave#comment-932313
https://aur.archlinux.org/packages/motivewave#comment-932245
https://aur.archlinux.org
Hello
I would like the community to help and decide on what to do.
I am the maintainer of motivewave
There is a person that went and created a duplicate motivewave-latest-bin
and went and publicly said I am incompetent and insinuated I was stupid.
Even today, labor day, when I want to spend time
