[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1110852: ITP: phoenix-esr -- A Firefox-ESR config designed to put the user first.



Hello Seyed,

you should please check the bug reports against the wnpp pseudo package first before you start to write an ITP bug report.

There is a RFP for this package already existing and so far I see this was opened by you.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094389

You can also use the website wnpp.debian.net to check for RFP or also ITP bug reports. This website is a bit more convenient to use.

https://wnpp.debian.net/?type%5B%5D=ITA&type%5B%5D=ITP&type%5B%5D=O&type%5B%5D=RFA&type%5B%5D=RFH&type%5B%5D=RFP&project=phoenix&description=&owner%5B%5D=yes&owner%5B%5D=no&col%5B%5D=dust&col%5B%5D=type&col%5B%5D=description&col%5B%5D=installs&col%5B%5D=owner&sort=installs%2Fdesc

You have now basically two options, 1.) close your ITP bug report and make the RFP report a ITP then plus take over the ownership, or 2.) merge the two bug reports together plus adjusting ownership afterwards.

You can use the needed commands by using the magic word "Control: " within your emails or you use the bts command on the command line to archive the same. Using a "Control: " statement in your emails is probably easier for you.
You will need multiple lines to get the various commands fired.

E.g. to get the two bugs merged you will need to write something like this to merge the two reports "Control: forcemerge bugnumer1 bugnumber1", to make the existing bug report an ITP "Control: retitle 1094389 ITP: phoenix-esr -- A Firefox-ESR config designed to put the user first", and make you owning this report "Control: owner 1094389 !"

Have a look at to see how the email needs to be controlled and written with the Control command.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092108#15

You will to read https://www.debian.org/Bugs/server-control more in detail!

To get the bug report closed you use the email address bugnumber-done@bugs.debian.org.

Am 11.08.25 um 15:32 schrieb Seyed Mohamad Amin Modaresi:
Package: wnpp
Severity: wishlist
Owner: wnpp <modaresisofthard@proton.me>
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name : phoenix-esr
Version : 2025.07.11.1-1
* URL : https://phoenix.celenity.dev
* License : GPL-3+
Description :  phoenix-esr - A Firefox-ESR config designed to put the user first.

phoenix-esr - A Firefox-ESR config designed to put the user first.
> Phoenix works by leveraging Firefox's AutoConfig & Enterprise
Policies functionality, and is installed on top of your standard,
official Firefox installation. This allows us to go above and beyond
what a simple user.js file can offer, without the security risks a
fork can introduce. For example, forks often fall behind on Firefox
updates, which can leave users open to severe, detrimental
vulnerabilities. Phoenix's approach allows users to continue
receiving immediate updates, directly from Mozilla.

Phoenix's approach also provides users with a seamless experience
that is accessible and easy to use. Gone are the days of creating
override files, manually keeping track of updates, resetting old
preferences, & adding your user.js file to each and every profile
you make. Not only is Phoenix the most effective & comprehensive
approach to configuring Firefox, it is also the most accessible &
easiest to use. Phoenix's changes to Firefox are carefully
considered based on extensive research & studying of Firefox's inner
workings. Phoenix is designed to maintain website compatibility and
to avoid breakage as much as possible, while still substantially
improving privacy & security compared to vanilla Firefox & most
other web browsers. For users who are fine with breakage and want to
go even further in enhancing their privacy & security, Phoenix also
offers an Extended config. This is completely optional and primarily
recommended for advanced users. For more information on Phoenix's
compatibility with websites and known issues, please see here.

BTW: Your template is again some parts missing!
The template is asking also for the upstream contact and the programming language.

And how the package is intended to get maintaned. These are importaned information so other memebers can decide to jump in or give some advice.

--
Regards
Carsten


Reply to: