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 with my 3 kids, I have to be on the computer basically doing code review. During the last 12 days, the package has 1) always compiled and built Now, I was recommended to make some changes source=("${pkgname}-${pkgver}.deb:: https://downloads.motivewave.com/builds/${build_id}/motivewave${pkgver}_amd64.deb ") then: makepkg --printsrcinfo > .SRCINFO But that would break my package. I found a solution with a custom variable, but 1) The other package is not being deleted: motivewave-latest-bin 2) My package is being basically spammed. 3) I am call the spammer I would like the community to let me know if someone recommends you to add code, and the code doesn't work, then why is there a pushover from Xiota to orphan the package. I have also received threads to have my account suspended/deleted but I wake up today at 3:00 AM my phone is beeping again because the person that copied the package, Xiota, cannot stop. -- Regards Xavier
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 community can't do anything to help you, retaliation would be a breach of CoC, we physically can't support you in that way. It sounds like you need package maintainer (formerly trusted user) support on this matter, they will be able to sort it out. If you don't mind me asking where are you being insulted/harassed? If its on IRC, contact one of the following opers for support: https://wiki.archlinux.org/title/Arch_IRC_channels#Channel_operators If its on the mailing list, a moderator will pick it up (be patient) or you can contact the mailing list admins (sorry don't know who they are). If it is offlisted, forward the emails to a moderator and make a complaint about the harassment, or spam their emails, or even better if you own a mail server (which unfortunately you don't) you could bounce them.
Even today, labor day, when I want to spend time with my 3 kids, I have to be on the computer basically doing code review.
Arch Linux is volunteering, not a full time job, you do not have any requirement to contribute, especially on holidays. Even if you are slapped with an orphan request, you will be given time to respond and explain how you have been busy, package maintainer (trusted users) are not arseholes, they aren't going to yank packages from you for spending time with your family.
During the last 12 days, the package has 1) always compiled and built
Now, I was recommended to make some changes
If the package works, there is no rush to make changes. Sure its always good to strive for clean, efficient packaging which follows standards, but just having it working is good enough, you don't need to stress over juggling time to simply improve a package. Also if they want said changes (if they are larger than "add x dependency" or "remove y dependency", then they should really give you a patch to contribute, complaining is unhelpful).
1) The other package is not being deleted: motivewave-latest-bin
The application seems to be proprietary, this package does not follow the packaging guidelines, proprietary apps do not have source code and thus do not need to be marked as binaries, thus "motiveware" is the correct name. I assume the -latest was so that they could claim a different package name to obsolete the package your maintain because they got fed up of waiting for you to be orphaned?
2) My package is being basically spammed.
They will get moderated, don't stress about it. If the email notifications are annoying just disable it until a staff member has time to help you :)
3) I am call the spammer
Then take the moral high ground and do not take revenge, wait for a staff member to help you, if you spam you will be caught in the moderation too!
I would like the community to let me know if someone recommends you to add code, and the code doesn't work, then why is there a pushover from Xiota to orphan the package.
People submit a bunch of orphan requests for selfish reasons, whether it is because they simply want to maintain the package, whether they think their PKGBUILD is better, or they simply do not want to collaborate with others. Remember, the AUR requires collaboration, and I have met some of the nicest people through helping fix packages, or by them giving me patches to fix a problem they encountered with a package. Everyone must pull the rug in the same direction, or we get nowhere. However this doesn't stop people trying to orphan when they gave you 3 days to respond while you were busy with something else. But also bare in mind, taking your time to fix a problem is fine, but do not blank emails or messages on the AUR, that is a quick way to get orphaned, just be transparent and you should have no issues with being orphaned.
I have also received threads to have my account suspended/deleted
Unless you have done something wrong you don't need to worry :)
but I wake up today at 3:00 AM my phone is beeping again because the person that copied the package, Xiota, cannot stop.
You have reported it now, a lot of Arch Staff monitor this mailing list, just give it time. For the time being turn off notifications and wait until someone is available to help you. Good luck, nothing I can do here but I wanted to give you suggestions anyways :) Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev
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 duplicated package was already solved and it's awaiting your fixes, like it was explained you multiple times by me. Unfortunately you continue to repeat this duplicated package story that's entirely irrelevant. xiota was already notified the package will be removed, awaiting your fixes. I've sent you more than 10 messages between email and comments explaining what you're doing wrong.
Now, I was recommended to make some changes
source=("${pkgname}-${pkgver}.deb::https://downloads.motivewave.com/builds/${build_id}/motivewave${pkgver}_amd64.deb <https://downloads.motivewave.com/builds/${build_id}/motivewave${pkgver}_amd64.deb>")
then: makepkg --printsrcinfo > .SRCINFO
But that would break my package.
This wouldn't break anything if you typed the variable name properly. In your PKGBUILD you declared the variable _build_id and in the URL you used the variable spelled wrongly as build_id This is the issue for making you believe xiota is sabotaging you, YOUR OWN TYPO is the root of your issues. So please don't blame others for any sabotaging. Luckily this was fixed few hours ago. So this whole discussion, now is pointless. Why are you writing it here? It was your typo, not xiota's fault.
I found a solution with a custom variable, but 1) The other package is not being deleted: motivewave-latest-bin
When the duplicated package will be removed was already explained you, so why are you raising this question again? You first fix the issues in your package and stop accusations towards the people wasting their time in HELPING YOU. Later the duplicated package will be removed, this was well explained you multiple times.
2) My package is being basically spammed. 3) I am call the spammer
On 2023/08/26 you wrote 13 comments in your own package page On 2023/09/03 you wrote 24 comments in your own package page without even realizing your own errors This is what's called spam, to send 13+24 useless notifications (with ZERO valid content for your users) to any users subscribed to your package.
I would like the community to let me know if someone recommends you to add code, and the code doesn't work, then why is there a pushover from Xiota to orphan the package.
The code xiota gently wrote you multiple times was correct, until you make typos or forget to give the variables a value. Also this was explained you by me also by private email.
I have also received threads to have my account suspended/deleted
Now move the focus on your bad behavior: 1) it was kindly asked to stop spamming your users with tens of messages. This was partially solved today 2) it was asked you to fix the URL with a valid URL and you started to accuse xiota of sabotage to make your package defective. This wasn't solved at all, at the point I asked you to remove the offending comments or I'll suspend your AUR account 3) it was asked you to unpin the TENS of pinned messages, with unrelated content, your own questions, other people questions and other unrelated stuff. This wasn't solved at all, today I unpinned the messages 4) it was told to remove the variable $pkgname_scammer which you used to denote xiota package This was partially solved yesterday, renaming the variable but not removing the package conflict 5) I wrote you by email to send me your PKGBUILD which has the issues, in order to help you on finding the reason but unfortunately you continued to blame xiota of insulting you and trying to steal the package and acting like a terrorist 6) me and MarsSeed asked you to relax and don't panic, no one was attempting to steal your package but you continue to repeat xiota is trying to steal your package Also xiota sent you multiple times a fixed PKGBUILD but you haven't considered it. So, finally, I wrote you something which I'll regret soon: I'll fix your package, as you don't seem to see your own errors. As response to my offer you wrote two emails in aur-general asking help to other people, like someone (me?) was offending you. If you don't stop this childish and aggressive behavior towards people helping you your account will be suspended. This was well explained you two times, so consider this message of mine like a final warning. Be thankful, relaxed and stop accusing other people. Apart creating a duplicated package for which he agreed the deletion, xiota gave you his help MULTIPLE TIMES as you weren't able to fix the package by yourself. So please, for the last time, stop this useless war against your ghosts. No one insulted you and no one wanted or tried to steal your package. It was only your fault, your own errors (typo, spam, aggressive behaviour, low packaging skill), if you followed my advices two days ago, you had your package fixed. Finally I repeat my last hint I gave you today: I'd suggest you to add a co-maintainer to this package to help you in fixing it as you need to learn a lot in packaging. Best regards -- Fabio Castelli aka Muflone
participants (3)
-
Muflone
-
Polarian
-
Xavier Baez