Re: [PRQ#45699] Merge Request for archey3-git

A fork is a fork. It does not mean it has been superseded. https://wiki.archlinux.org/title/Archey3 Archey3 is on the wiki, not Archey4. You have already mentioned Archey4 on the Archey3 AUR page, one year ago. And you spammed yesterday the Archey3 AUR page, by flagging it out-of-date while this

[PRQ#45699] Merge Request for archey3-git Rejected

Request #45699 has been Rejected by muflone [1]: let's keep them both actually [1] https://aur.archlinux.org/account/muflone/

Re: [PRQ#45699] Merge Request for archey3-git

Sure ok, you did spam and I considered you misappropriated comments from me and the upstream archey3 dev. I consider this merge request inappropriate as you requested to merge a VCS package into a non-VCS package from a different upstream author with a different package. And you did not give e

Re: [PRQ#45699] Merge Request for archey3-git

You said I want to steal, referred to me as "hippies like MarsSeed", you said I was lying. You falsely accused me of spamming, to disqualify my legitimate answers. That's flaming, fair and square. Please try to aim for a more civil tone in the future. Explain your side without derogatory state

Re: [PRQ#45699] Merge Request for archey3-git

Sure. I’ll do the same. I did not insult you in any way. Flaming is about "posting insults, often including profanity or other offensive language”. I considered you spammed by flagging out-of-date an up-to-date package, submitting too many comments on the archey3 AUR page, submitting a merge r

Re: [PRQ#45699] Merge Request for archey3-git

I will let trusted users deal with this package and with your messages from now on. But please don't flame anymore. Thank you. On 4 August 2023 12:20:05 GMT+02:00, Gaspard d'Hautefeuille wrote: >https://terms.archlinux.org/docs/code-of-conduct/#spamadvertisingsolicitation > >Spamming is forbi

Re: [PRQ#45699] Merge Request for archey3-git

https://terms.archlinux.org/docs/code-of-conduct/#spamadvertisingsolicitation Spamming is forbidden which you continue to do on this page: https://aur.archlinux.org/packages/archey3-git. You also flagged out-of-date the archey3-git package while it was in sync with the upstream archey3 repo in

Re: [PRQ#45699] Merge Request for archey3-git

# Do not flame # Flaming, in the most common sense definition, is directing negative, disrespectful, and/or insulting comments toward someone. An equally or more negative response, resulting in a cycling exchange of insults is often the consequence. Flaming fellow members (including the Arch te

Re: [PRQ#45699] Merge Request for archey3-git

> You are lying. > > He did not comment about the merge request. You are not quoting him on that > because he did not comment specifically on it. You mentioned the proposed merge to the archey3 dev and asked, among other things, if he would support in any way the archey4 fork. And he replied su

Re: [PRQ#45699] Merge Request for archey3-git

You are lying. He did not comment about the merge request. You are not quoting him on that because he did not comment specifically on it. He said he will no longer develop archey3 and that he will soon archive his repo. https://github.com/lclarkmichalek/archey3/issues/52#issuecomment-166377732

Re: [PRQ#45699] Merge Request for archey3-git

Maintainer @HLFH also asked the archery3 fork's developer if he plans to get back to it and develop it further, and he replied that he won't be doing so any longer, and in fack he only considers archiving the repo. His "archeying days are over", he said. [a] The developer also indicated he has

Re: [PRQ#45699] Merge Request for archey3-git

Arguments against the merge request: 1) archey3 is on the wiki , not archey4 2) archey3 is maintained in the [extra] repo , not archey4 3) archey3-git is maintained on the AUR

[PRQ#45699] Merge Request for archey3-git

MarsSeed [1] filed a request to merge archey3-git [2] into archey4 [3]: As discussed with maintainer @HLFH in comments 10+ months ago, this application has been superseded by continuation fork archey4. He posted a link to the new AUR package then, so users should be well- informed at this point.