Search results for "Deletion request for pkgbase" - Aur-requests

Re: [aur-requests] [PRQ#31497] Deletion Request for anbox-modules-dkms

by info＠sick.codes

Are you suggesting that every AUR package that is up to date with master where there is a -git package should be removed? bbswitch-ati-dkms-git 0.8.5.gddbd243-1 3 bbswitch-ati-git 0.8.5.gddbd243-1 darling r3131.fa5348c8a-1 darling-git r3131.fa5348c8a-1 yay 11.1.0-1 yay-git 11.1.0.r0.gac13060-1 AUR rules https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submiss… “If it is currently maintained, changes can be submitted in a comment for the maintainer's attention. If it is unmaintained or the maintainer is unresponsive, the package can be adopted and updated as required. Do not create duplicate packages.“ It’s not a duplicate, it’s the pegged non-git package which uses a specific commit. The package was merged because I removed myself from the mailing list and didn’t reply stating that the issues were resolved. Why did you merge instead of suggesting changes? And why do you want the package deleted so urgently? Jan 15, 2022, 20:00 by env252525(a)gmail.com: > It is still a duplicate. There are no releases upstream. What's the point of having a non git version if it's just going to follow the latest git commit anyway? > > Yes this matter was resolved. The package was merged. That is why anbox-modules-dkms should not exist. > > On Sat, Jan 15, 2022 at 4:08 PM <info(a)sick.codes> wrote: > >> Hey eNV25, >> >> Just because the non-git and git packages are on the same commit id does not mean the whole package should be wiped and its changelog, comments, AUR git history, and any other informative discussion should be deleted. >> >> Once master is updated, the non-git will be out of date. That's what Out of Date is for. >> >> # non-git >> source=("git+>> https://github.com/choff/${_pkgname}.git#commit=8148a162755bf5500a07cf41a65… <https://github.com/choff/$%7B_pkgname%7D.git#commit=8148a162755bf5500a07cf4…>>> " >> >> # git >> source=("git+$url#branch=master") >> >> As you know your original Merge Request reasons were already addressed. >> >> Merge request: >> https://lists.archlinux.org/pipermail/aur-requests/2021-December/063155.html >> >> Fixes: >> https://aur.archlinux.org/cgit/aur.git/commit/?h=anbox-modules-dkms&id=8790… >> >> And: >> https://aur.archlinux.org/cgit/aur.git/commit/?h=anbox-modules-dkms&id=20a6… >> >> - Removed the build function from previous 2017 maintainer >> - Removed linux-headers from previous 2017 maintainer >> - Removed /usr/lib/modules-load.d/ from previous 2017 maintainer >> >> I didn't create the original pkgbuild, I simply revived it as-is, including it's git history for transparency. I didn't write the original PKGBUILD. I re-uploaded it with accurate git history so that anyone else can actually see the commit history of the package: >> https://aur.archlinux.org/cgit/aur.git/log/?h=anbox-modules-dkms >> >> Given you are well aware I was actively maintaining the package, why would you submit a merge request instead of emailing me or submit a pull request? >> >> I really don't understand your sudden urgency to remove the package from the AUR. >> >> Why did you merge instead of suggesting changes? >> >> And why do you want the package deleted so urgently? >> >> In good faith, >> >> Sick Codes of the Security Research Team >> @SickCodes <https://twitter.com/sickcodes> >> >> https://sick.codes >> https://github.com/sickcodes >> https://twitter.com/sickcodes >> https://www.linkedin.com/in/sickcodes/ >> https://www.youtube.com/c/sickcodes >> https://parler.com/profile/sickcodes/ >> https://hackerone.com/sickcodes >> https://bugcrowd.com/sickcodes >> https://hub.docker.com/r/sickcodes >> >> >> >> >> >> >> Jan 15, 2022, 09:05 by >> env252525(a)gmail.com>> : >> >>> On Sat, Jan 15, 2022 at 11:10 AM <info(a)sick.codes> wrote: >>> >>>> >>>> This is a false deletion request, the maintainer knows this is a correct non-git dkms PKGBUILD >>>> >>> >>> I don't think so. >>> >>>> >>>> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=anbox-modules-dkms >>>> >>>> The maintainer discussion between myself and the other maintainer is on >>>> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=anbox-modules-dkms >>>> >>>> I don’t we know what the current maintainer is trying to achieve here but the two packages are distinct. >>>> >>>> 1) I personally maintain the fork with the GitHub user >>>> >>> >>> fine >>> >>>> >>>> 2) I had already made env25 a co maintainer >>>> >>> >>> And I made you a co-maintainer for anbox-modules-dkms-git >>> >>>> 3) I am on the WayDroid dev team >>>> >>> >>> It's not relevant who you are >>> >>>> 2) this fork was created by myself and Choff >>>> >>> >>> fine >>> >>>> 3) the non-git is perfectly fine now >>>> >>> >>> No it's not it's a duplicate of anbox-modules-dkms-git >>> >>>> 4) eNV25 has already merged requested this, in a rush, for no apparent reason. >>>> >>> >>> The TU ainola merged this. I submitted the request. >>> >>> https://lists.archlinux.org/pipermail/aur-requests/2021-December/063155.html >>> https://lists.archlinux.org/pipermail/aur-requests/2021-December/063596.html >>> >>>> >>>> Please reject this merge & deletion request for the following reasons: >>>> >>> >>> Please don't reject this deletion request. >>> >>>> >>>> And if possible please merge back the non-git repo comment history as you can clearly see >>>> >>>> I have been maintaining the WIKI on Anbox to be accurate >>>> https://wiki.archlinux.org/title/Anbox >>>> >>> >>> fine >>> >>> >>>> >>>> In good faith, >>>> >>>> Sick Codes of the Security Research Team @SickCodes >>>> >>>> https://sick.codes >>>> https://github.com/sickcodes >>>> https://twitter.com/sickcodes >>>> https://www.linkedin.com/in/sickcodes/ >>>> https://www.youtube.com/c/sickcodes >>>> https://parler.com/profile/sickcodes/ >>>> https://hackerone.com/sickcodes >>>> https://bugcrowd.com/sickcodes >>>> https://hub.docker.com/r/sickcodes >>>> >>>> >>>> >>>> >>>> >>>> >>>> Jan 14, 2022, 22:57 by >>>> notify(a)aur.archlinux.org>>>> : >>>> >>>> eNV25 [1] filed a deletion request for anbox-modules-dkms [2]: >>>> >>>> This package is a duplicate of anbox-modules-dkms-git. >>>> >>>> I previously submitted a merge request from anbox-modules-dkms to >>>> anbox-modules-dkms-git. >>>> >>>> I maintain anbox-modules-dkms-git. >>>> >>>> [1] >>>> https://aur.archlinux.org/account/eNV25/ >>>> [2] >>>> https://aur.archlinux.org/pkgbase/anbox-modules-dkms/ >>>> >> >>

3 years, 11 months

Re: [aur-requests] [PRQ#31497] Deletion Request for anbox-modules-dkms

by info＠sick.codes

anbox-modules-dkms follows last working commit with the patch for 5.10 anbox-modules-dkms-git follows master branch with sed instead of a patch https://wiki.archlinux.org/title/VCS_package_guidelines#Guidelines “Suffix pkgname with -cvs, -svn, -hg, -darcs, -bzr, -git etc. unless the package fetches a specific release.” The commit is in the PKGBUILD, as there are no releases. Said commit is 8148a162755bf5500a07cf41a65a02c8f3eb0af9" `source=("git+https://github.com/choff/${_pkgname}.git#commit=8148a162755bf5500a07cf4…"` Jan 15, 2022, 23:59 by env252525(a)gmail.com: > bbswitch-ati-dkms-git bbswitch-ati-git are split packages from the > same PKGBUILD. Of course they have same version. > > darling is a duplicate of darling-git > > yay follows upstream release, yay-git follows git branch > > On Sat, Jan 15, 2022 at 9:57 PM <info(a)sick.codes> wrote: > >> >> Are you suggesting that every AUR package that is up to date with master where there is a -git package should be removed? >> >> bbswitch-ati-dkms-git 0.8.5.gddbd243-1 3 >> bbswitch-ati-git 0.8.5.gddbd243-1 >> >> darling r3131.fa5348c8a-1 >> darling-git r3131.fa5348c8a-1 >> >> yay 11.1.0-1 >> yay-git 11.1.0.r0.gac13060-1 >> >> AUR rules https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submiss… >> >> “If it is currently maintained, changes can be submitted in a comment for the maintainer's attention. If it is unmaintained or the maintainer is unresponsive, the package can be adopted and updated as required. Do not create duplicate packages.“ >> >> It’s not a duplicate, it’s the pegged non-git package which uses a specific commit. >> >> The package was merged because I removed myself from the mailing list and didn’t reply stating that the issues were resolved. >> >> Why did you merge instead of suggesting changes? >> > > Your package is git package that does not have -git sufflix. > >> >> And why do you want the package deleted so urgently? >> > > It's not urgent. > >> Jan 15, 2022, 20:00 by env252525(a)gmail.com: >> >> It is still a duplicate. There are no releases upstream. What's the point of having a non git version if it's just going to follow the latest git commit anyway? >> >> Yes this matter was resolved. The package was merged. That is why anbox-modules-dkms should not exist. >> >> On Sat, Jan 15, 2022 at 4:08 PM <info(a)sick.codes> wrote: >> >> Hey eNV25, >> >> Just because the non-git and git packages are on the same commit id does not mean the whole package should be wiped and its changelog, comments, AUR git history, and any other informative discussion should be deleted. >> >> Once master is updated, the non-git will be out of date. That's what Out of Date is for. >> >> # non-git >> source=("git+https://github.com/choff/${_pkgname}.git#commit=8148a162755bf5500a07cf4…" >> >> # git >> source=("git+$url#branch=master") >> >> As you know your original Merge Request reasons were already addressed. >> >> Merge request: https://lists.archlinux.org/pipermail/aur-requests/2021-December/063155.html >> >> Fixes: https://aur.archlinux.org/cgit/aur.git/commit/?h=anbox-modules-dkms&id=8790… >> >> And: https://aur.archlinux.org/cgit/aur.git/commit/?h=anbox-modules-dkms&id=20a6… >> >> - Removed the build function from previous 2017 maintainer >> - Removed linux-headers from previous 2017 maintainer >> - Removed /usr/lib/modules-load.d/ from previous 2017 maintainer >> >> I didn't create the original pkgbuild, I simply revived it as-is, including it's git history for transparency. I didn't write the original PKGBUILD. I re-uploaded it with accurate git history so that anyone else can actually see the commit history of the package: https://aur.archlinux.org/cgit/aur.git/log/?h=anbox-modules-dkms >> >> Given you are well aware I was actively maintaining the package, why would you submit a merge request instead of emailing me or submit a pull request? >> >> I really don't understand your sudden urgency to remove the package from the AUR. >> >> Why did you merge instead of suggesting changes? >> >> And why do you want the package deleted so urgently? >> >> In good faith, >> >> Sick Codes of the Security Research Team @SickCodes >> >> https://sick.codes >> https://github.com/sickcodes >> https://twitter.com/sickcodes >> https://www.linkedin.com/in/sickcodes/ >> https://www.youtube.com/c/sickcodes >> https://parler.com/profile/sickcodes/ >> https://hackerone.com/sickcodes >> https://bugcrowd.com/sickcodes >> https://hub.docker.com/r/sickcodes >> >> >> >> >> >> >> Jan 15, 2022, 09:05 by env252525(a)gmail.com: >> >> On Sat, Jan 15, 2022 at 11:10 AM <info(a)sick.codes> wrote: >> >> >> This is a false deletion request, the maintainer knows this is a correct non-git dkms PKGBUILD >> >> >> I don't think so. >> >> >> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=anbox-modules-dkms >> >> The maintainer discussion between myself and the other maintainer is on https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=anbox-modules-dkms >> >> I don’t we know what the current maintainer is trying to achieve here but the two packages are distinct. >> >> 1) I personally maintain the fork with the GitHub user >> >> >> fine >> >> >> 2) I had already made env25 a co maintainer >> >> >> And I made you a co-maintainer for anbox-modules-dkms-git >> >> 3) I am on the WayDroid dev team >> >> >> It's not relevant who you are >> >> 2) this fork was created by myself and Choff >> >> >> fine >> >> 3) the non-git is perfectly fine now >> >> >> No it's not it's a duplicate of anbox-modules-dkms-git >> >> 4) eNV25 has already merged requested this, in a rush, for no apparent reason. >> >> >> The TU ainola merged this. I submitted the request. >> >> https://lists.archlinux.org/pipermail/aur-requests/2021-December/063155.html >> https://lists.archlinux.org/pipermail/aur-requests/2021-December/063596.html >> >> >> Please reject this merge & deletion request for the following reasons: >> >> >> Please don't reject this deletion request. >> >> >> And if possible please merge back the non-git repo comment history as you can clearly see >> >> I have been maintaining the WIKI on Anbox to be accurate https://wiki.archlinux.org/title/Anbox >> >> >> fine >> >> >> In good faith, >> >> Sick Codes of the Security Research Team @SickCodes >> >> https://sick.codes >> https://github.com/sickcodes >> https://twitter.com/sickcodes >> https://www.linkedin.com/in/sickcodes/ >> https://www.youtube.com/c/sickcodes >> https://parler.com/profile/sickcodes/ >> https://hackerone.com/sickcodes >> https://bugcrowd.com/sickcodes >> https://hub.docker.com/r/sickcodes >> >> >> >> >> >> >> Jan 14, 2022, 22:57 by notify(a)aur.archlinux.org: >> >> eNV25 [1] filed a deletion request for anbox-modules-dkms [2]: >> >> This package is a duplicate of anbox-modules-dkms-git. >> >> I previously submitted a merge request from anbox-modules-dkms to >> anbox-modules-dkms-git. >> >> I maintain anbox-modules-dkms-git. >> >> [1] https://aur.archlinux.org/account/eNV25/ >> [2] https://aur.archlinux.org/pkgbase/anbox-modules-dkms/ >> >>

3 years, 11 months

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

by Gaspard d'Hautefeuille

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 request into a different package rather than a deletion request which could have been relevant when the archey3 package in [extra] will be deleted. You misappropriated my comment when I said to you that archey4 is more relevant for Arch users. I considered as well you misappropriated in my opinion the comment from the upstream archey3 dev, if I got it wrong on that, I’m sorry. > On 4 Aug 2023, at 12:30, Marcell Meszaros <marcell.meszaros(a)runbox.eu> wrote: > > 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 <gaspard(a)dhautefeuille.eu> wrote: >> https://terms.archlinux.org/docs/code-of-conduct/#spamadvertisingsolicitati… >> >> 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 order to promote archey4. >> You should only flag out-of-date when the upstream has submitted a new release. >> As it is a VCS package that is maintained and the upstream has not submitted any breaking changes for the package, I’m not sure it was the right way to do things. >> >> Your interpretation of "Ship it” slang is only yours. >> >> Going ahead is only meaning this in my opinion: >> >> 1) I am currently maintaining archey4-git <https://aur.archlinux.org/packages/archey4-git>, if votes and comments should be merged into of the VCS package archey3-git, it should go there. But I don’t think merging is a good idea. >> >> 2) The TU maintaining archey3 in [extra] would have to delete archey3 and promote archey4 in [extra] >> >> 3) Then, I would submit archey3-git for deletion because as long as there is an archey3 official package and official archey3 wiki page, a VCS-equivalent package should still be offered to the Arch Linux users >> >> 4) It does not make really sense to merge archey3-git into archey4 on the AUR: not the same upstream package, not the same upstream dev, VCS vs normal releases... >> >> >>> On 4 Aug 2023, at 11:40, Marcell Meszaros <marcell.meszaros(a)runbox.eu> wrote: >>> >>> # 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 team) will not be tolerated. Avoid personal insults and sarcastic or patronizing language. Discussions can be productive, but quarreling is always destructive. >>> >>> https://terms.archlinux.org/docs/code-of-conduct/#do-not-flame >>> >>> >>> On 2 August 2023 10:32:16 GMT+02:00, Gaspard d'Hautefeuille <gaspard(a)dhautefeuille.eu> wrote: >>>> 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 archey3-git package is up-to-date with the upstream repo. https://github.com/lclarkmichalek/archey3 >>>> Not everyone wants to use Archey4, and forking by changing the number to make it seem like it has been superseded is not a good practice. >>>> >>>> Furthermore, you want to steal the 171 votes and comments of archey3 with this merge request. >>>> If the fork of archey4 was by the same author, we could have understood that, it is not the case here. >>>> >>>> Archey4 has 16 votes, does not have a wiki page (yet). >>>> >>>> It does seem too early to consider a deletion request for archey3-git in the AUR (Arch Linux User Repository). >>>> Maybe you could contact the author https://github.com/lclarkmichalek/archey3/issues and see what he is up to and if he really gives the seal of approval to archey4. >>>> AUR/archey3-git is not defunct and I am still maintaining it. >>>> >>>> >>>> >>>> >>>> You know that archey - first of his name - decided to remove archey4 as a listed fork on GitHub. >>>> https://github.com/djmelik/archey >>>> >>>> And even, djmelik is planning a complete re-write of Archey. >>>> >>>> It is very much too early to say 100% that the fork archey4 has to take the crown. >>>> >>>> >>>> Sincerely, >>>> >>>> HLFH >>>> >>>>> On 1 Aug 2023, at 17:26, notify(a)aur.archlinux.org wrote: >>>>> >>>>> 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. >>>>> >>>>> Archey3 has not been developed since 2018. [a] >>>>> >>>>> Arch repo still carries the last archey3 (however, devs would be >>>>> advised to consider adopting archey4 to [extra]). >>>>> >>>>> Though archey3-git is a VCS package and AUR/archey4 is not, there's no >>>>> VCS package for the latter but it would still be good to migrate the >>>>> high number of votes and comments to the successor application's >>>>> package rather than just deleting them. >>>>> >>>>> AUR/archey3-git is defunct so there's no harm in removing that in >>>>> favor of archey4. >>>>> >>>>> [a]: https://github.com/lclarkmichalek/archey3/commits/master >>>>> >>>>> [1] https://aur.archlinux.org/account/MarsSeed/ >>>>> [2] https://aur.archlinux.org/pkgbase/archey3-git/ >>>>> [3] https://aur.archlinux.org/pkgbase/archey4/ >>>> >>

2 years, 4 months

Re: [aur-requests] [PRQ#12066] Deletion Request for popcorntime

by Giovanni Santini (ItachiSan)

Hi Jean, Thank you for the analysis; it was really detailed and extensive. The only issue then is the prebuild nw.js binary build provided from the PopcornTime team, as we can't guarantee malware absence from it. So, as you suggested, I will substitute the binary with the official one (from the nw.js project). I also found on the AUR this package: https://aur.archlinux.org/packages/nwjs-ffmpeg-codecs-bin/ (https://link.getmailspring.com/link/1532263255.local-8b55aff9-0fcb-v1.3.0-f…) It should provide the necessary library for viewing multiple video formats. Can it be considered safe (as it is as a binary) or should I create a from scratch package? Thanks in advance, Giovanni SantiniComputer scientist and geek giovannisantini93(a)yahoo.it (https://link.getmailspring.com/link/1532263255.local-8b55aff9-0fcb-v1.3.0-f…) https://giovannisantini.tk (https://link.getmailspring.com/link/1532263255.local-8b55aff9-0fcb-v1.3.0-f…) On lug 21 2018, at 10:46 pm, Jean Lucas <jean(a)4ray.co> wrote: > > Agreed on suspicious claims. However, both sides point the finger at > each other, so I read the code. > > During build, gulp downloads a custom version of NW.js from > get.popcorntime.sh[1]. I have verified that various binaries in the > upstream and downstream NW.js packages vary in size. I haven't found a > statement by a Popcorn Time organization member saying that they use the > Butter Project's NW.js build script[2], only that a custom version is > used[3]. One might suppose that PT's NW.js is built from BP's script, > but I have not been able to confirm this via checksums, seeing as BP's > CI site[4] is down[5], and NW.js is a very heavy build. Until the CI > site comes back online and we are able to confirm checksum matches, the > get.popcorntime.sh NW.js package should be considered dangerous. A > negative clamscan alone should not be deemed proof that the various > binaries are not malicious. > > As for forks/alternatives, its worth noting that Popcorn Time built with > upstream NW.js[6] succeeds and runs, although the internal media player > will not be able to playback a lot of media due to lack of codecs, so > you'd have to use an external media player in many cases. In lieu of the > inconvenience, this seems to be the safest option for now. > > [1]: > https://github.com/popcorn-official/popcorn-desktop/blob/development/gulpfi… > > [2]: https://github.com/butterproject/nwjs-build > [3]: > https://github.com/popcorn-official/popcorn-desktop/issues/624#issuecomment… > > [4]: > https://github.com/butterproject/butter-desktop/issues/647#issuecomment-303… > > [5]: http://builds.butterproject.org/nw/ > [6]: > https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=popcorntime-git#n32 > > > On 07/21/2018 09:53 AM, Giovanni Santini (ItachiSan) wrote: > > I would like to point out the following facts: > > The package I do provide is built from source, based on the code hosted here: https://github.com/popcorn-official/popcorn-desktop (https://link.getmailspring.com/link/1532179678.local-251a76dc-d25e-v1.3.0-f…) > > You can report found spyware there (can you prove me is there any? A clamscan?) > > On my side, I do have no malware: > > $ clamscan /mnt/build/archlinux/chroots/bauerbill/popcorntime/popcorntime-0.3.10-8-x86_64.pkg.tar.xz > > /mnt/build/archlinux/chroots/bauerbill/popcorntime/popcorntime-0.3.10-7-x86_64.pkg.tar.xz: OK > > I could approve on redistributed binary builds, but this is not the case, as users build their package theirselves. > > > > The sources you provide are by far more suspicious, as the website you point to redirect to a Git repository which has as homepage an no-existing one. > > The claims provided in the link are quite general; there is no actual proof and the link provided by the 'spyware team', which is: > > https://blog.popcorntime.sh/popcorn-time-safety-and-ransomware/ (https://link.getmailspring.com/link/1532179678.local-251a76dc-d25e-v1.3.0-f…) > > provides by far better description and information. > > To finish up, deleting the package is something I wouldn't like to do; I would be glad to switch to another fork, if you can provide me a good one. > > > > Giovanni SantiniComputer scientist and geek > > giovannisantini93(a)yahoo.it (https://link.getmailspring.com/link/1532179678.local-251a76dc-d25e-v1.3.0-f…) > > https://giovannisantini.tk (https://link.getmailspring.com/link/1532179678.local-251a76dc-d25e-v1.3.0-f…) > > > > On lug 17 2018, at 8:18 am, notify(a)aur.archlinux.org wrote: > > > flacks [1] filed a deletion request for popcorntime [2]: > > > Package reportedly distributes viruses/spyware https://www.popcorn- > > > time.is/official-statement.html > > > > > > [1] https://aur.archlinux.org/account/flacks/ > > > [2] https://aur.archlinux.org/pkgbase/popcorntime/ > > > >

7 years, 4 months

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

by Marcell Meszaros

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 <gaspard(a)dhautefeuille.eu> wrote: >https://terms.archlinux.org/docs/code-of-conduct/#spamadvertisingsolicitati… > >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 order to promote archey4. >You should only flag out-of-date when the upstream has submitted a new release. >As it is a VCS package that is maintained and the upstream has not submitted any breaking changes for the package, I’m not sure it was the right way to do things. > >Your interpretation of "Ship it” slang is only yours. > >Going ahead is only meaning this in my opinion: > >1) I am currently maintaining archey4-git <https://aur.archlinux.org/packages/archey4-git>, if votes and comments should be merged into of the VCS package archey3-git, it should go there. But I don’t think merging is a good idea. > >2) The TU maintaining archey3 in [extra] would have to delete archey3 and promote archey4 in [extra] > >3) Then, I would submit archey3-git for deletion because as long as there is an archey3 official package and official archey3 wiki page, a VCS-equivalent package should still be offered to the Arch Linux users > >4) It does not make really sense to merge archey3-git into archey4 on the AUR: not the same upstream package, not the same upstream dev, VCS vs normal releases... > > >> On 4 Aug 2023, at 11:40, Marcell Meszaros <marcell.meszaros(a)runbox.eu> wrote: >> >> # 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 team) will not be tolerated. Avoid personal insults and sarcastic or patronizing language. Discussions can be productive, but quarreling is always destructive. >> >> https://terms.archlinux.org/docs/code-of-conduct/#do-not-flame >> >> >> On 2 August 2023 10:32:16 GMT+02:00, Gaspard d'Hautefeuille <gaspard(a)dhautefeuille.eu> wrote: >>> 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 archey3-git package is up-to-date with the upstream repo. https://github.com/lclarkmichalek/archey3 >>> Not everyone wants to use Archey4, and forking by changing the number to make it seem like it has been superseded is not a good practice. >>> >>> Furthermore, you want to steal the 171 votes and comments of archey3 with this merge request. >>> If the fork of archey4 was by the same author, we could have understood that, it is not the case here. >>> >>> Archey4 has 16 votes, does not have a wiki page (yet). >>> >>> It does seem too early to consider a deletion request for archey3-git in the AUR (Arch Linux User Repository). >>> Maybe you could contact the author https://github.com/lclarkmichalek/archey3/issues and see what he is up to and if he really gives the seal of approval to archey4. >>> AUR/archey3-git is not defunct and I am still maintaining it. >>> >>> >>> >>> >>> You know that archey - first of his name - decided to remove archey4 as a listed fork on GitHub. >>> https://github.com/djmelik/archey >>> >>> And even, djmelik is planning a complete re-write of Archey. >>> >>> It is very much too early to say 100% that the fork archey4 has to take the crown. >>> >>> >>> Sincerely, >>> >>> HLFH >>> >>>> On 1 Aug 2023, at 17:26, notify(a)aur.archlinux.org wrote: >>>> >>>> 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. >>>> >>>> Archey3 has not been developed since 2018. [a] >>>> >>>> Arch repo still carries the last archey3 (however, devs would be >>>> advised to consider adopting archey4 to [extra]). >>>> >>>> Though archey3-git is a VCS package and AUR/archey4 is not, there's no >>>> VCS package for the latter but it would still be good to migrate the >>>> high number of votes and comments to the successor application's >>>> package rather than just deleting them. >>>> >>>> AUR/archey3-git is defunct so there's no harm in removing that in >>>> favor of archey4. >>>> >>>> [a]: https://github.com/lclarkmichalek/archey3/commits/master >>>> >>>> [1] https://aur.archlinux.org/account/MarsSeed/ >>>> [2] https://aur.archlinux.org/pkgbase/archey3-git/ >>>> [3] https://aur.archlinux.org/pkgbase/archey4/ >>> >

2 years, 4 months

Re: [PRQ#43382] Deletion Request for openblas-lapack

by Guillaume Horel

The way dynamic arch.works with the official package is that they all get built, and the specific architecture will get selected at runtime for a slight penalty cost at startup. The package install is thus much bigger and loading time is slower. The community package is not "superior in every aspect", it makes different choices under different constraints. Same for the TLS use flag. This package has been updated regularly. I've submitted multiple changes upstream from the feedback of users using this package while the community package didn't exist. I think this package serves its purpose. I don't understand why you want to have it deleted, while this doesn't break anything as far as I know? Nobody forces you to use this package, feel free to use the official one. On Mon, Jul 3, 2023 at 1:42 PM Marcell Mészáros <meszaros.marcell(a)runbox.com> wrote: > Dynamic architecture support means one binary can take advantage of a wide > range of microarchitectures. > > Also, your build turns on USE_TLS, a "new, still somewhat experimental > code that uses thread-local storage instead of a central memory buffer". > > Which is exactly what it should not do in a production-targeted build. > > You should create a new package with a descriptive name suffix, like > '-experimental-tls' or something. > > > On 3 July 2023 19:33:04 GMT+02:00, Marcell Meszaros < > marcell.meszaros(a)runbox.eu> wrote: > >> Arch repo openblas is already built with multiple microarchitecture >> support through >> cmake '-DDYNAMIC_ARCH=ON'. >> >> https://gitlab.archlinux.org/archlinux/packaging/packages/openblas/ >> >> Your PKGBUILD, however, does not seem to enable the same for its build >> with make. >> >> The latter also does not build 64-bit precision libraries, whereas the >> repo buildscript does. >> >> So as of now, the new repo package is superior to this original AUR one, >> in every aspect that you mentioned. >> >> >> On 3 July 2023 19:11:20 GMT+02:00, Guillaume Horel < >> guillaume.horel(a)gmail.com> wrote: >> >>> Openblas is a performance oriented package, microarchitecture >>> optimization is exactly what it's about. Moreover this PKGBUILD has >>> different build options than the official one which is allowed by the >>> guidelines. >>> >>> On Mon, Jul 3, 2023 at 11:32 AM Marcell Meszaros < >>> marcell.meszaros(a)runbox.eu> wrote: >>> >>>> > The package in community provides the dynamic arch version, whereas >>>> this one will be specifically tuned for your current architecture. >>>> >>>> But this is not a good enough reason to keep PKGBUILDs for the same >>>> source in both Arch repo and on AUR. >>>> >>>> Arch is not a binary-only distribution: all the build scripts are >>>> availabe. >>>> >>>> One can always grab a couple of PKGBUILDs from Arch repo's GitLab for >>>> fine-tuned, microarchitecture-optimized rebuild, if that is what they want. >>>> >>>> But AUR submission guidelines are quite clear: they don't mention >>>> allowing duplication for this purpose. >>>> >>>> >>>> On 2 July 2023 17:34:03 GMT+02:00, Guillaume Horel < >>>> guillaume.horel(a)gmail.com> wrote: >>>> >>>>> This is not the exactly the same package. The package in community >>>>> provides the dynamic arch version, whereas this one will be specifically >>>>> tuned for your current architecture. >>>>> I've responded in the comments that there is nothing broken at the >>>>> moment with this package, and I don't see the need to delete it. >>>>> >>>>> On Sun, Jul 2, 2023 at 7:17 AM <notify(a)aur.archlinux.org> wrote: >>>>> >>>>>> MarsSeed [1] filed a deletion request for openblas-lapack [2]: >>>>>> >>>>>> Same package is now in [extra], named blas-openblas: >>>>>> >>>>>> https://archlinux.org/packages/extra/x86_64/blas-openblas/ >>>>>> >>>>>> See announcement about it: >>>>>> https://archlinux.org/news/openblas-0323-2-update-requires-manual- >>>>>> intervention/ >>>>>> <https://archlinux.org/news/openblas-0323-2-update-requires-manual-intervent…> >>>>>> >>>>>> I have notified AUR maintainers in comments about their need to review >>>>>> this change, and possibly adapt their PKGBUILD's. >>>>>> >>>>>> [1] https://aur.archlinux.org/account/MarsSeed/ >>>>>> [2] https://aur.archlinux.org/pkgbase/openblas-lapack/ >>>>> >>>>>

2 years, 5 months

Re: [aur-requests] [PRQ#1301] Deletion Request for update

by Colin Keenan

I disagree that it's necessary to merge pacnew files, read the front page news, or read install messages on updating already installed software. I've been intensely using Arch for a year and a half now. On my own machine, which I turn off several times a day, I have a script that automatically runs updating the system every time I turn it on (several times a day). I rarely merge pacnew files and when I do, it often leads to problems I would not have had if I had simply left them alone. I never read install messages that occur during a system update. I don't read the frontpage news unless there's a problem after an update, and then it has never had anything relevant to tell me. I've only experienced update issues a couple of times in the past 18 months, mostly early on. The last issue happened just in the past couple of weeks, didn't stop me from doing anything but looked ugly, and resolved itself after a few days when updates to the Xfce dev packages came through. The people I'm doing installs for won't ever be able to solve any real issue with their computer and will therefore come to me everytime. I've tried other solutions to getting them to update their system, and they simply don't do it. Originally I was trying to use the auto-update script, but discovered it's not a robust script and needs to be tweaked for each machine and only really works properly on machines with a fast processor and SSD. That's why I never put it in the AUR. This super simple script and desktop file, when put on a launcher for the Xfce panel, makes updates every bit as simple as in any distro, and they do at least see what's happening whether or not they ever pay attention. My own experience on Arch tells me there's no real problem doing regular system updates without understanding everything that's going on. When there's a problem, they will come to me and I'll take a look at the pacnew files and pacman.log etc. They don't need to know how to do that and more importantly, don't really seem capable of using a computer at that level. On the rare instance they need new software, they will also reach out to me. Why didn't I give them Ubuntu? Because Arch actually seems to have less issues than any other distro I've tried, and because for some reason, I'm having 100% success installing Arch while experiencing a lot of trouble installing Ubuntu. It just saves me time to install and maintain Arch. Even though Ubuntu doesn't expect you to manually mess with configuration files or read install notes etc., it has more issues on updates than if you just update Arch ignoring all that. On Fri, Nov 7, 2014 at 2:33 AM, Lukas Fleischer <archlinux(a)cryptocrack.de> wrote: > On Sat, 01 Nov 2014 at 00:47:30, Colin Keenan wrote: > > Please do not delete my package in the AUR, 'update'. Although the script > > contains only one line of relevant code that could better be done with an > > alias, the package also contains a desktop file which can easily be put > on > > a panel or other launcher for one-click updating similar to a GUI. When > > installing Arch to other people's computers, people who may not be all > that > > comfortable with the command line, it's much easier for me to install > this > > update package for them than to find and copy the script and desktop file > > onto their computer. > > > > The idea behind this package is to add the desktop launcher to your panel > > (for example the Xfce panel), and then just click on it when you want to > > update your computer. The user just enters their password when asked for, > > and the rest is done automatically (unless it takes so long that another > > password entry is required). By making updating as easy as possible, > users > > will update more frequently. > > > > This sounds like a bad idea. You should not run `pacman -Syu` (or even > `yaourt -Syu`) unless you know what you are doing. Arch Linux quite > often requires manual intervention. If people blindly run `pacman -Syu`, > they will not read (or not understand, at least) install messages, they > won't merge .pacnew files and will not take care of what is mentioned in > the frontpage news. By using yaourt, they will probably also install AUR > packages without reviewing the PKGBUILDs (I never used yaourt myself, so > I might be wrong here). > > > The script and desktop file are so simple that anyone can see it's safe. > > What would be the harm in leaving it in the AUR? > > > > On Fri, Oct 31, 2014 at 4:24 PM, <notify(a)aur.archlinux.org> wrote: > > > > > karol_007 [1] filed a deletion request for update [2]: > > > > > > A package is a bit of an overkill for this oneliner. > > > > > > [1] https://aur.archlinux.org/account/karol_007/ > > > [2] https://aur.archlinux.org/pkgbase/update/ > > > > > > >

11 years, 1 month

[aur-requests] [PRQ#4452] Deletion Request for 4kvideodownloader

by notify＠aur.archlinux.org

Sukumi [1] filed a deletion request for 4kvideodownloader [2]: ########### !!!! URGENT ACTION REQUIRED !!!!!!!!! ##################### ########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!! ############### NO SOURCE, PROPRIETARY SOFTWARE LICENSE, BINARIES ONLY The maintainer is responsible that the managed packaged adhere and comply with the community and ArchLinux philosophy and rules of package submission. ALL PRODUCTS OF COMPANY OpenMedia LLC US ARE AFFECTED I THINK THE COMPLIANCE AUDIT RULES NEED A REVIEW. LICENSE EXCERPT GIVEN BELOW ########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!!!!!!!!! ############### ########### !!!! URGENT ACTION REQUIRED !!!!!!!!!!!!!! ####################### IMPORTANT: THIS SOFTWARE END USER LICENSE AGREEMENT ("EULA") IS A LEGAL AGREEMENT BETWEEN YOU AND COMPANY ("OPEN MEDIA LLC"). USE OF THE SOFTWARE PROVIDED WITH THIS EULA (THE "SOFTWARE") CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS. READ IT CAREFULLY BEFORE COMPLETING THE INSTALLATION PROCESS AND USING THE SOFTWARE. IF YOU DO NOT AGREE TO THE TERMS OF THIS EULA, DO NOT INSTALL AND/OR USE THIS SOFTWARE. BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE PRODUCT, YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA. 1. LICENSE GRANT. The Software is licensed on per user basis. "User" means the company, entity or individual whose funds are used to pay the license fee. "Use" means storing, loading, installing, executing or displaying the Software. You may not modify the Software or disable any licensing or control features of the Software except as an intended part of the Software programming features. This license is not transferable to any other system, or to another organization or individual. 2. OWNERSHIP. The Software is owned and copyrighted by Open Media LLC. Your license confers no title or ownership in the Software and should not be construed as a sale of any right in the Software. 3. SOFTWARE COPYRIGHT. The Software and all rights, without limitation including proprietary rights therein, are owned by Open Media LLC or its suppliers and are protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The Software is licensed, not sold. You acknowledge that no title to the intellectual property in the Software is transferred to you. You further acknowledge that title and full ownership rights to the Software will remain the exclusive property of Open Media LLC and you will not acquire any rights to the Software except as expressly set forth in this license. You agree that any copies of the Software will contain the same proprietary notices which appear on and in the Software. 4. "PRO" VERSION. That which is established in this clause will only be applied to users of the "pro" version of the software. Open Media LLC. declares that the "pro" version of this software offers the following characteristics: * It is free of publicity/advertisements * It has all declared functions activated * It allows free updates from the date of acquisition. However the user understands that Open Media LLC does not have the obligation to execute these updates during this time or any whatsoever at any other moment. * Open Media LLC reserves the right to dissolve this agreement with the user of the pro version without previous notice if any of the clauses included in the document have been violated. 5. CONTENT COPYRIGHT AND OWNERSHIP. You agree that the owners, employees and volunteers of the Company are not responsible for any loss or damages which may result from your illegal use of images, video clips or music files. Make sure that you have the right to use the images, video clips and music files you upload to the service. The Company claims no intellectual property rights over the content you upload, create or provide to the Service. 6. REVERSE ENGINEERING. You agree that you will not attempt to reverse compile, modify, translate, or disassemble the Software in whole or in part. 7. NO OTHER WARRANTIES. THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. OPEN MEDIA LLC DISCLAIMS ALL OTHER WARRANTIES WITH RESPECT TO THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY MAY LAST, OR THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. 8. YOUR INFORMATION and OPEN MEDIA LLC'S PRIVACY POLICY 8.1 Privacy Policy. The personal information you provide to Open Media LLC during the ordering and registration process is used for Open Media LLC's internal purposes only. Open Media LLC uses the information it collects to learn what you like and to improve the Software. Except as otherwise expressly permitted by this EULA or as otherwise authorized by you, Open Media LLC will not give any of your personal information to any third party without your express approval except as reasonably required by law, as authorized by this provision or as necessary to protect Open Media LLC, its agents and other Participants. Open Media LLC can (and you authorize Open Media LLC to) disclose any information about you to private entities, law enforcement agencies or government officials, as Open Media LLC, in its sole discretion, believe necessary or appropriate to investigate or resolve possible problems or inquiries, or as otherwise required by law. 8.2 Email Communication. You agree that Open Media LLC may communicate with you via email and any similar technology for any purpose relating to the Software, other Open Media LLC products and any services or software which may in the future be provided by Open Media LLC or on Open Media LLC's behalf. If you do not want to receive communication from Open Media LLC, you can unsubscribe at any time following the instructions contained in any email received from Open Media LLC or by writing an opt-out request to Open Media LLC at support(a)4kdownload.com. 8.3 Statistics. In order to innovate and continuously improve its products, the company may collect some anonymous usage statistics from its Software including, without limitation, the collection of information on how software is used by users. STATISTICS POTENTIALLY COLLECTED IS ANONYMOUS AND CAN NOT IN ANY WAY LEAD TO IDENTIFY USERS. 9. SEVERABILITY. In the event of invalidity of any provision of this license, the parties agree that such invalidity shall not affect the validity of the remaining portions of this license. 10. NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL OPEN MEDIA LLC OR ITS SUPPLIERS BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, SPECIAL, INCIDENTAL OR INDIRECT DAMAGES OF ANY KIND ARISING OUT OF THE DELIVERY, PERFORMANCE OR USE OF THE SOFTWARE, EVEN IF OPEN MEDIA LLC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL OPEN MEDIA LLC's LIABILITY FOR ANY CLAIM, WHETHER IN CONTRACT, TORT OR ANY OTHER THEORY OF LIABILITY, EXCEED THE LICENSE FEE PAID BY YOU, IF ANY. 11. GENERAL PROVISION. This is the entire agreement between you and Open Media LLC, which supersedes any prior agreement or understanding, whether written, or oral, relating to the subject matter of this EULA. If any part of this EULA is found void and unenforceable, it will not affect the validity of the balance of the agreement, which shall remain valid and enforceable according to its terms. This EULA shall automatically terminate upon failure by you to comply with its terms. Open Media LLC, on its sole discretion, may modify this EULA in writing at any time. [1] https://aur.archlinux.org/account/Sukumi/ [2] https://aur.archlinux.org/pkgbase/4kvideodownloader/

10 years

[aur-requests] [PRQ#4453] Deletion Request for 4kslideshowmaker

by notify＠aur.archlinux.org

Sukumi [1] filed a deletion request for 4kslideshowmaker [2]: ########### !!!! URGENT ACTION REQUIRED !!!!!!!!! ##################### ########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!! ############### NO SOURCE, PROPRIETARY SOFTWARE LICENSE, BINARIES ONLY The maintainer is responsible that the managed packaged adhere and comply with the community and ArchLinux philosophy and rules of package submission. ALL PRODUCTS OF COMPANY OpenMedia LLC US ARE AFFECTED I THINK THE COMPLIANCE AUDIT RULES NEED A REVIEW. LICENSE EXCERPT GIVEN BELOW ########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!!!!!!!!! ############### ########### !!!! URGENT ACTION REQUIRED !!!!!!!!!!!!!! ####################### IMPORTANT: THIS SOFTWARE END USER LICENSE AGREEMENT ("EULA") IS A LEGAL AGREEMENT BETWEEN YOU AND COMPANY ("OPEN MEDIA LLC"). USE OF THE SOFTWARE PROVIDED WITH THIS EULA (THE "SOFTWARE") CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS. READ IT CAREFULLY BEFORE COMPLETING THE INSTALLATION PROCESS AND USING THE SOFTWARE. IF YOU DO NOT AGREE TO THE TERMS OF THIS EULA, DO NOT INSTALL AND/OR USE THIS SOFTWARE. BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE PRODUCT, YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA. 1. LICENSE GRANT. The Software is licensed on per user basis. "User" means the company, entity or individual whose funds are used to pay the license fee. "Use" means storing, loading, installing, executing or displaying the Software. You may not modify the Software or disable any licensing or control features of the Software except as an intended part of the Software programming features. This license is not transferable to any other system, or to another organization or individual. 2. OWNERSHIP. The Software is owned and copyrighted by Open Media LLC. Your license confers no title or ownership in the Software and should not be construed as a sale of any right in the Software. 3. SOFTWARE COPYRIGHT. The Software and all rights, without limitation including proprietary rights therein, are owned by Open Media LLC or its suppliers and are protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The Software is licensed, not sold. You acknowledge that no title to the intellectual property in the Software is transferred to you. You further acknowledge that title and full ownership rights to the Software will remain the exclusive property of Open Media LLC and you will not acquire any rights to the Software except as expressly set forth in this license. You agree that any copies of the Software will contain the same proprietary notices which appear on and in the Software. 4. "PRO" VERSION. That which is established in this clause will only be applied to users of the "pro" version of the software. Open Media LLC. declares that the "pro" version of this software offers the following characteristics: * It is free of publicity/advertisements * It has all declared functions activated * It allows free updates from the date of acquisition. However the user understands that Open Media LLC does not have the obligation to execute these updates during this time or any whatsoever at any other moment. * Open Media LLC reserves the right to dissolve this agreement with the user of the pro version without previous notice if any of the clauses included in the document have been violated. 5. CONTENT COPYRIGHT AND OWNERSHIP. You agree that the owners, employees and volunteers of the Company are not responsible for any loss or damages which may result from your illegal use of images, video clips or music files. Make sure that you have the right to use the images, video clips and music files you upload to the service. The Company claims no intellectual property rights over the content you upload, create or provide to the Service. 6. REVERSE ENGINEERING. You agree that you will not attempt to reverse compile, modify, translate, or disassemble the Software in whole or in part. 7. NO OTHER WARRANTIES. THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. OPEN MEDIA LLC DISCLAIMS ALL OTHER WARRANTIES WITH RESPECT TO THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY MAY LAST, OR THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. 8. YOUR INFORMATION and OPEN MEDIA LLC'S PRIVACY POLICY 8.1 Privacy Policy. The personal information you provide to Open Media LLC during the ordering and registration process is used for Open Media LLC's internal purposes only. Open Media LLC uses the information it collects to learn what you like and to improve the Software. Except as otherwise expressly permitted by this EULA or as otherwise authorized by you, Open Media LLC will not give any of your personal information to any third party without your express approval except as reasonably required by law, as authorized by this provision or as necessary to protect Open Media LLC, its agents and other Participants. Open Media LLC can (and you authorize Open Media LLC to) disclose any information about you to private entities, law enforcement agencies or government officials, as Open Media LLC, in its sole discretion, believe necessary or appropriate to investigate or resolve possible problems or inquiries, or as otherwise required by law. 8.2 Email Communication. You agree that Open Media LLC may communicate with you via email and any similar technology for any purpose relating to the Software, other Open Media LLC products and any services or software which may in the future be provided by Open Media LLC or on Open Media LLC's behalf. If you do not want to receive communication from Open Media LLC, you can unsubscribe at any time following the instructions contained in any email received from Open Media LLC or by writing an opt-out request to Open Media LLC at support(a)4kdownload.com. 8.3 Statistics. In order to innovate and continuously improve its products, the company may collect some anonymous usage statistics from its Software including, without limitation, the collection of information on how software is used by users. STATISTICS POTENTIALLY COLLECTED IS ANONYMOUS AND CAN NOT IN ANY WAY LEAD TO IDENTIFY USERS. 9. SEVERABILITY. In the event of invalidity of any provision of this license, the parties agree that such invalidity shall not affect the validity of the remaining portions of this license. 10. NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL OPEN MEDIA LLC OR ITS SUPPLIERS BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, SPECIAL, INCIDENTAL OR INDIRECT DAMAGES OF ANY KIND ARISING OUT OF THE DELIVERY, PERFORMANCE OR USE OF THE SOFTWARE, EVEN IF OPEN MEDIA LLC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL OPEN MEDIA LLC's LIABILITY FOR ANY CLAIM, WHETHER IN CONTRACT, TORT OR ANY OTHER THEORY OF LIABILITY, EXCEED THE LICENSE FEE PAID BY YOU, IF ANY. 11. GENERAL PROVISION. This is the entire agreement between you and Open Media LLC, which supersedes any prior agreement or understanding, whether written, or oral, relating to the subject matter of this EULA. If any part of this EULA is found void and unenforceable, it will not affect the validity of the balance of the agreement, which shall remain valid and enforceable according to its terms. This EULA shall automatically terminate upon failure by you to comply with its terms. Open Media LLC, on its sole discretion, may modify this EULA in writing at any time. [1] https://aur.archlinux.org/account/Sukumi/ [2] https://aur.archlinux.org/pkgbase/4kslideshowmaker/

10 years

[aur-requests] [PRQ#4454] Deletion Request for 4kstogram

by notify＠aur.archlinux.org

Sukumi [1] filed a deletion request for 4kstogram [2]: ########### !!!! URGENT ACTION REQUIRED !!!!!!!!! ##################### ########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!! ############### NO SOURCE, PROPRIETARY SOFTWARE LICENSE, BINARIES ONLY The maintainer is responsible that the managed packaged adhere and comply with the community and ArchLinux philosophy and rules of package submission. ALL PRODUCTS OF COMPANY OpenMedia LLC US ARE AFFECTED I THINK THE COMPLIANCE AUDIT RULES NEED A REVIEW. LICENSE EXCERPT GIVEN BELOW ########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!!!!!!!!! ############### ########### !!!! URGENT ACTION REQUIRED !!!!!!!!!!!!!! ####################### IMPORTANT: THIS SOFTWARE END USER LICENSE AGREEMENT ("EULA") IS A LEGAL AGREEMENT BETWEEN YOU AND COMPANY ("OPEN MEDIA LLC"). USE OF THE SOFTWARE PROVIDED WITH THIS EULA (THE "SOFTWARE") CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS. READ IT CAREFULLY BEFORE COMPLETING THE INSTALLATION PROCESS AND USING THE SOFTWARE. IF YOU DO NOT AGREE TO THE TERMS OF THIS EULA, DO NOT INSTALL AND/OR USE THIS SOFTWARE. BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE PRODUCT, YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA. 1. LICENSE GRANT. The Software is licensed on per user basis. "User" means the company, entity or individual whose funds are used to pay the license fee. "Use" means storing, loading, installing, executing or displaying the Software. You may not modify the Software or disable any licensing or control features of the Software except as an intended part of the Software programming features. This license is not transferable to any other system, or to another organization or individual. 2. OWNERSHIP. The Software is owned and copyrighted by Open Media LLC. Your license confers no title or ownership in the Software and should not be construed as a sale of any right in the Software. 3. SOFTWARE COPYRIGHT. The Software and all rights, without limitation including proprietary rights therein, are owned by Open Media LLC or its suppliers and are protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The Software is licensed, not sold. You acknowledge that no title to the intellectual property in the Software is transferred to you. You further acknowledge that title and full ownership rights to the Software will remain the exclusive property of Open Media LLC and you will not acquire any rights to the Software except as expressly set forth in this license. You agree that any copies of the Software will contain the same proprietary notices which appear on and in the Software. 4. "PRO" VERSION. That which is established in this clause will only be applied to users of the "pro" version of the software. Open Media LLC. declares that the "pro" version of this software offers the following characteristics: * It is free of publicity/advertisements * It has all declared functions activated * It allows free updates from the date of acquisition. However the user understands that Open Media LLC does not have the obligation to execute these updates during this time or any whatsoever at any other moment. * Open Media LLC reserves the right to dissolve this agreement with the user of the pro version without previous notice if any of the clauses included in the document have been violated. 5. CONTENT COPYRIGHT AND OWNERSHIP. You agree that the owners, employees and volunteers of the Company are not responsible for any loss or damages which may result from your illegal use of images, video clips or music files. Make sure that you have the right to use the images, video clips and music files you upload to the service. The Company claims no intellectual property rights over the content you upload, create or provide to the Service. 6. REVERSE ENGINEERING. You agree that you will not attempt to reverse compile, modify, translate, or disassemble the Software in whole or in part. 7. NO OTHER WARRANTIES. THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. OPEN MEDIA LLC DISCLAIMS ALL OTHER WARRANTIES WITH RESPECT TO THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY MAY LAST, OR THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. 8. YOUR INFORMATION and OPEN MEDIA LLC'S PRIVACY POLICY 8.1 Privacy Policy. The personal information you provide to Open Media LLC during the ordering and registration process is used for Open Media LLC's internal purposes only. Open Media LLC uses the information it collects to learn what you like and to improve the Software. Except as otherwise expressly permitted by this EULA or as otherwise authorized by you, Open Media LLC will not give any of your personal information to any third party without your express approval except as reasonably required by law, as authorized by this provision or as necessary to protect Open Media LLC, its agents and other Participants. Open Media LLC can (and you authorize Open Media LLC to) disclose any information about you to private entities, law enforcement agencies or government officials, as Open Media LLC, in its sole discretion, believe necessary or appropriate to investigate or resolve possible problems or inquiries, or as otherwise required by law. 8.2 Email Communication. You agree that Open Media LLC may communicate with you via email and any similar technology for any purpose relating to the Software, other Open Media LLC products and any services or software which may in the future be provided by Open Media LLC or on Open Media LLC's behalf. If you do not want to receive communication from Open Media LLC, you can unsubscribe at any time following the instructions contained in any email received from Open Media LLC or by writing an opt-out request to Open Media LLC at support(a)4kdownload.com. 8.3 Statistics. In order to innovate and continuously improve its products, the company may collect some anonymous usage statistics from its Software including, without limitation, the collection of information on how software is used by users. STATISTICS POTENTIALLY COLLECTED IS ANONYMOUS AND CAN NOT IN ANY WAY LEAD TO IDENTIFY USERS. 9. SEVERABILITY. In the event of invalidity of any provision of this license, the parties agree that such invalidity shall not affect the validity of the remaining portions of this license. 10. NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL OPEN MEDIA LLC OR ITS SUPPLIERS BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, SPECIAL, INCIDENTAL OR INDIRECT DAMAGES OF ANY KIND ARISING OUT OF THE DELIVERY, PERFORMANCE OR USE OF THE SOFTWARE, EVEN IF OPEN MEDIA LLC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL OPEN MEDIA LLC's LIABILITY FOR ANY CLAIM, WHETHER IN CONTRACT, TORT OR ANY OTHER THEORY OF LIABILITY, EXCEED THE LICENSE FEE PAID BY YOU, IF ANY. 11. GENERAL PROVISION. This is the entire agreement between you and Open Media LLC, which supersedes any prior agreement or understanding, whether written, or oral, relating to the subject matter of this EULA. If any part of this EULA is found void and unenforceable, it will not affect the validity of the balance of the agreement, which shall remain valid and enforceable according to its terms. This EULA shall automatically terminate upon failure by you to comply with its terms. Open Media LLC, on its sole discretion, may modify this EULA in writing at any time. [1] https://aur.archlinux.org/account/Sukumi/ [2] https://aur.archlinux.org/pkgbase/4kstogram/

10 years

Aur-requests search results for query "Deletion request for pkgbase"