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

[aur-requests] [PRQ#16805] Deletion Request for the-darkmod-tweaked

by notify＠aur.archlinux.org

eschwartz [1] filed a deletion request for the-darkmod-tweaked [2]: After discussion in the package comments for thedarkmod-bin, it was determined that the custom installer used in the former package "darkmod" violated the rules of submission on numerous levels. The package was reimplemented by a Trusted User, and for good measure cleaned up and renamed to something more closely matching upstream intentions, but for all this, the core issue with https://gitlab.com/es20490446e/the-darkmod-tweaked had nothing to do whether mv is better than cp, or whatever else this justification entails: ``` So I'm providing an alternative version for this package, called "the- darkmod-tweaked", with the following enhancements over the official bundle: Separated saved games and downloaded mission repository for each user. Missions cache auto-cleanup. Enhanced installation speed compared with the official installer. ``` No, this is not acceptable. Your new package is still obfuscation and violates the rules of submission. Your "tweaks" in comparison with thedarkmod-bin do not answer the question: "why was the previous package orphaned via moderator action". You may not re-upload a package which was deemed inadmissible to the AUR, and simply rename the pkgname in order to justify its existence. You are REQUIRED to either: - first defend your claim that the initial judgment "this is unfit for the AUR" was incorrect, or - fix the problems You have done neither. [1] https://aur.archlinux.org/account/eschwartz/ [2] https://aur.archlinux.org/pkgbase/the-darkmod-tweaked/

6 years

[PRQ#52569] Deletion Request for 7plus

by notify＠aur.archlinux.org

xiota [1] filed a deletion request for 7plus [2]: This package should be deleted because it compromises the security of the systems on which it is installed. This package uses Electron as a web browser to navigate a streaming media website. Electron is *not* a web browser. Although it uses the same rendering engine as Chromium, it is not Chromium, and it does not have the same security features Chromium does. On the contrary, Electron intentionally has reduced security because it is intended for desktop apps, not web browsing. At [Security](https://www.electronjs.org/docs/latest/tutorial/security), Electron developers state: > A security issue exists whenever you receive code from an untrusted source (e.g. a remote server) and execute it locally. As an example, consider a remote website being displayed inside a default BrowserWindow. If an attacker somehow manages to change said content (either by attacking the source directly, or by sitting between your app and the actual destination), they will be able to execute native code on the user's machine. This apps does what Electron devs describe avoiding: ``` const mainWindow = new BrowserWindow(...) ... mainWindow.loadURL('https://...') ``` Further, this package is named in a way that some users may think it is an official package, which it is not. [1] https://aur.archlinux.org/account/xiota/ [2] https://aur.archlinux.org/pkgbase/7plus/

1 year, 11 months

Re: [PRQ#69847] Deletion Request for bitwarden-bin

by Mark Wagie

Yes, I'm aware bitwarden is in the extra repo. However, it sometimes takes days, weeks or months before our friendly Arch PM has time to update it. Building it from source is not such an easy task. I helped out libertylocked (original AUR maintainer) with it before it was imported into the Arch repos. Either way, users besides myself are finding it quite useful to have the latest binary version available in the AUR. I much prefer the repo version depending on the system Electron package, however it's always nice to have be able to have mobile, browser and system packages all in sync with various security updates, bug fixes and new features in a timely manner. That's just my two cents. If the decision is made to delete the package, that's fine. I'll just manage my own package locally and others can install it from my GitHub if they wish. Sent with Proton Mail secure email. On Thursday, February 13th, 2025 at 9:30 PM, notify(a)aur.archlinux.org <notify(a)aur.archlinux.org> wrote: > matthewq337 [1] filed a deletion request for bitwarden-bin [2]: > > it's in extra https://archlinux.org/packages/extra/x86_64/bitwarden/ > > [1] https://aur.archlinux.org/account/matthewq337/ > [2] https://aur.archlinux.org/pkgbase/bitwarden-bin/

10 months

Re: [aur-requests] [PRQ#34934] Deletion Request for run-mailcap

by Erik Johnson

This is still a useful package, as it provides a useful utility to open attachments in Mutt in external applications, based on mime type. I will update it the package, not delete it. On Sun, May 29, 2022 at 7:22 AM <notify(a)aur.archlinux.org> wrote: > m040601 [1] filed a deletion request for run-mailcap [2]: > > This is a very old PKGBUILD that references a obsolete 2014 Ubuntu > version. It should be removed. It only confuses archlinux users > looking for mailcap related tools. > > > ```` > Conflicts: mime-support > ```` > > There is no PKGBUILD "mime-support" anymore. > > > ```` > Upstream URL: http://packages.ubuntu.com/utopic/mime-support > ```` > > references a 2014, Ubuntu 14.10 (Utopic Unicorn) version. > > And leads to a non existing page, > > ```` > Error > two or more packages specified (mime-support utopic) > ```` > > > > As of 2022 there is no "run-mailcap" package in recent versions of > Ubuntu. The only thing related to "mailcap" in Ubuntu is, according > to, https://packages.ubuntu.com/ a package called "mailcap", > https://packages.ubuntu.com/source/jammy/mailcap > > [1] https://aur.archlinux.org/account/m040601/ > [2] https://aur.archlinux.org/pkgbase/run-mailcap/ -- -Erik "For me, it is far better to grasp the universe as it really is than to persist in delusion, however satisfying and reassuring." -- Carl Sagan

3 years, 6 months

[PRQ#52570] Deletion Request for binge

by notify＠aur.archlinux.org

xiota [1] filed a deletion request for binge [2]: This package should be deleted because it compromises the security of the systems on which it is installed. This package uses Electron as a web browser to navigate a streaming media website. Electron is *not* a web browser. Although it uses the same rendering engine as Chromium, it is not Chromium, and it does not have the same security features Chromium does. On the contrary, Electron intentionally has reduced security because it is intended for desktop apps, not web browsing. At [Security](https://www.electronjs.org/docs/latest/tutorial/security), Electron developers state: > A security issue exists whenever you receive code from an untrusted source (e.g. a remote server) and execute it locally. As an example, consider a remote website being displayed inside a default BrowserWindow. If an attacker somehow manages to change said content (either by attacking the source directly, or by sitting between your app and the actual destination), they will be able to execute native code on the user's machine. This apps does what Electron devs describe avoiding: ``` const mainWindow = new BrowserWindow(...) ... mainWindow.loadURL('https://...') ``` Further, this package is named in a way that some users may think it is an official package, which it is not. [1] https://aur.archlinux.org/account/xiota/ [2] https://aur.archlinux.org/pkgbase/binge/

1 year, 11 months

[PRQ#52571] Deletion Request for crunchyroll

by notify＠aur.archlinux.org

xiota [1] filed a deletion request for crunchyroll [2]: This package should be deleted because it compromises the security of the systems on which it is installed. This package uses Electron as a web browser to navigate a streaming media website. Electron is *not* a web browser. Although it uses the same rendering engine as Chromium, it is not Chromium, and it does not have the same security features Chromium does. On the contrary, Electron intentionally has reduced security because it is intended for desktop apps, not web browsing. At [Security](https://www.electronjs.org/docs/latest/tutorial/security), Electron developers state: > A security issue exists whenever you receive code from an untrusted source (e.g. a remote server) and execute it locally. As an example, consider a remote website being displayed inside a default BrowserWindow. If an attacker somehow manages to change said content (either by attacking the source directly, or by sitting between your app and the actual destination), they will be able to execute native code on the user's machine. This apps does what Electron devs describe avoiding: ``` const mainWindow = new BrowserWindow(...) ... mainWindow.loadURL('https://...') ``` Further, this package is named in a way that some users may think it is an official package, which it is not. [1] https://aur.archlinux.org/account/xiota/ [2] https://aur.archlinux.org/pkgbase/crunchyroll/

1 year, 11 months

[PRQ#52572] Deletion Request for disneyplus

by notify＠aur.archlinux.org

xiota [1] filed a deletion request for disneyplus [2]: This package should be deleted because it compromises the security of the systems on which it is installed. This package uses Electron as a web browser to navigate a streaming media website. Electron is *not* a web browser. Although it uses the same rendering engine as Chromium, it is not Chromium, and it does not have the same security features Chromium does. On the contrary, Electron intentionally has reduced security because it is intended for desktop apps, not web browsing. At [Security](https://www.electronjs.org/docs/latest/tutorial/security), Electron developers state: > A security issue exists whenever you receive code from an untrusted source (e.g. a remote server) and execute it locally. As an example, consider a remote website being displayed inside a default BrowserWindow. If an attacker somehow manages to change said content (either by attacking the source directly, or by sitting between your app and the actual destination), they will be able to execute native code on the user's machine. This apps does what Electron devs describe avoiding: ``` const mainWindow = new BrowserWindow(...) ... mainWindow.loadURL('https://...') ``` Further, this package is named in a way that some users may think it is an official package, which it is not. [1] https://aur.archlinux.org/account/xiota/ [2] https://aur.archlinux.org/pkgbase/disneyplus/

1 year, 11 months

[PRQ#52573] Deletion Request for foxtelgo

by notify＠aur.archlinux.org

xiota [1] filed a deletion request for foxtelgo [2]: This package should be deleted because it compromises the security of the systems on which it is installed. This package uses Electron as a web browser to navigate a streaming media website. Electron is *not* a web browser. Although it uses the same rendering engine as Chromium, it is not Chromium, and it does not have the same security features Chromium does. On the contrary, Electron intentionally has reduced security because it is intended for desktop apps, not web browsing. At [Security](https://www.electronjs.org/docs/latest/tutorial/security), Electron developers state: > A security issue exists whenever you receive code from an untrusted source (e.g. a remote server) and execute it locally. As an example, consider a remote website being displayed inside a default BrowserWindow. If an attacker somehow manages to change said content (either by attacking the source directly, or by sitting between your app and the actual destination), they will be able to execute native code on the user's machine. This apps does what Electron devs describe avoiding: ``` const mainWindow = new BrowserWindow(...) ... mainWindow.loadURL('https://...') ``` Further, this package is named in a way that some users may think it is an official package, which it is not. [1] https://aur.archlinux.org/account/xiota/ [2] https://aur.archlinux.org/pkgbase/foxtelgo/

1 year, 11 months

[PRQ#52574] Deletion Request for googlekeep

by notify＠aur.archlinux.org

xiota [1] filed a deletion request for googlekeep [2]: This package should be deleted because it compromises the security of the systems on which it is installed. This package uses Electron as a web browser to navigate a streaming media website. Electron is *not* a web browser. Although it uses the same rendering engine as Chromium, it is not Chromium, and it does not have the same security features Chromium does. On the contrary, Electron intentionally has reduced security because it is intended for desktop apps, not web browsing. At [Security](https://www.electronjs.org/docs/latest/tutorial/security), Electron developers state: > A security issue exists whenever you receive code from an untrusted source (e.g. a remote server) and execute it locally. As an example, consider a remote website being displayed inside a default BrowserWindow. If an attacker somehow manages to change said content (either by attacking the source directly, or by sitting between your app and the actual destination), they will be able to execute native code on the user's machine. This apps does what Electron devs describe avoiding: ``` const mainWindow = new BrowserWindow(...) ... mainWindow.loadURL('https://...') ``` Further, this package is named in a way that some users may think it is an official package, which it is not. [1] https://aur.archlinux.org/account/xiota/ [2] https://aur.archlinux.org/pkgbase/googlekeep/

1 year, 11 months

[PRQ#52575] Deletion Request for messages

by notify＠aur.archlinux.org

xiota [1] filed a deletion request for messages [2]: This package should be deleted because it compromises the security of the systems on which it is installed. This package uses Electron as a web browser to navigate a streaming media website. Electron is *not* a web browser. Although it uses the same rendering engine as Chromium, it is not Chromium, and it does not have the same security features Chromium does. On the contrary, Electron intentionally has reduced security because it is intended for desktop apps, not web browsing. At [Security](https://www.electronjs.org/docs/latest/tutorial/security), Electron developers state: > A security issue exists whenever you receive code from an untrusted source (e.g. a remote server) and execute it locally. As an example, consider a remote website being displayed inside a default BrowserWindow. If an attacker somehow manages to change said content (either by attacking the source directly, or by sitting between your app and the actual destination), they will be able to execute native code on the user's machine. This apps does what Electron devs describe avoiding: ``` const mainWindow = new BrowserWindow(...) ... mainWindow.loadURL('https://...') ``` Further, this package is named in a way that some users may think it is an official package, which it is not. [1] https://aur.archlinux.org/account/xiota/ [2] https://aur.archlinux.org/pkgbase/messages/

1 year, 11 months

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