| Git Clone URL: | https://aur.archlinux.org/microsoft-edge-stable-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | microsoft-edge-stable-bin |
| Description: | A browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier |
| Upstream URL: | https://www.microsoftedgeinsider.com/en-us/download |
| Licenses: | custom |
| Conflicts: | edge, edge-stable, edge-stable-bin, microsoft-edge-stable |
| Provides: | edge-stable, microsoft-edge-stable |
| Submitter: | nicomix |
| Maintainer: | nicomix (aakashhemadri) |
| Last Packager: | aakashhemadri |
| Votes: | 104 |
| Popularity: | 2.64 |
| First Submitted: | 2021-10-29 02:42 (UTC) |
| Last Updated: | 2023-11-13 17:00 (UTC) |
119.0.2151.97 was released [1], and builds successfully.
Hopefully this AUR package will get some love by the packager/maintainer soon.
Per the release notes[2], this version contains a security fix[3] for CVE-2023-6345.
[3] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-6345
@wxt1221,
I flagged the package out of date when I noticed 119.0.2151.72 was in the repo.
We'll have to wait for @aakashhemadri to commit a fix to the CI script.
Easy enough to just modify the PKGBUILD ourselves, and build new version(s) in the meanwhile.
Why not update!
Thanks for mentioning everyone, set it to the latest available and shutdown the update CI, will fix and turn it back on, thanks for the suggestion to use vercmp @petronny
@aakashhemadri Is the auto update CI fixed? Please call vercmp in your CI to ensure no downgrade.
What happened to this. What caused that?
Age Commit message (Expand) Author
14 min. Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
9 hours Update microsoft-edge-stable to v119.0.2151.58 Aakash Hemadri
10 hours Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
11 hours Update microsoft-edge-stable to v119.0.2151.58 Aakash Hemadri
12 hours Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
19 hours Update microsoft-edge-stable to v119.0.2151.58 Aakash Hemadri
22 hours Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
27 hours Update microsoft-edge-stable to v119.0.2151.58 Aakash Hemadri
29 hours Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
31 hours Update microsoft-edge-stable to v119.0.2151.58 Aakash Hemadri
34 hours Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
45 hours Update microsoft-edge-stable to v119.0.2151.58 Aakash Hemadri
47 hours Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
2 days Update microsoft-edge-stable to v119.0.2151.58 Aakash Hemadri
9 days Update microsoft-edge-stable to v119.0.2151.44 Aakash Hemadri
Age Commit message (Expand)
55 min. Update microsoft-edge-stable to v119.0.2151.58
115 min. Update microsoft-edge-stable to v119.0.2151.44
9 hours Update microsoft-edge-stable to v119.0.2151.58
12 hours Update microsoft-edge-stable to v119.0.2151.44
17 hours Update microsoft-edge-stable to v119.0.2151.58
19 hours Update microsoft-edge-stable to v119.0.2151.44
21 hours Update microsoft-edge-stable to v119.0.2151.58
24 hours Update microsoft-edge-stable to v119.0.2151.44
35 hours Update microsoft-edge-stable to v119.0.2151.58
37 hours Update microsoft-edge-stable to v119.0.2151.44
43 hours Update microsoft-edge-stable to v119.0.2151.58
9 days Update microsoft-edge-stable to v119.0.2151.44
Why bump to microsoft-edge-stable_119.0.2151.44-1_amd64.deb ?
microsoft-edge-stable_119.0.2151.58-1_amd64.deb is still exist.
Since installed PWA app are hard code to launch by /opt/microsoft/msedge/microsoft-edge, maybe change the #User flag aware launcher part in PKGBUILD to:
# User flag aware launcher
readflag_script=$(sed -z 's|\n|\\n|g' <<- "SHELL"
# Make script fail if `cat` fails for some reason
set -e
# Set default value if variable is unset/null
XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-${HOME}/.config}"
# Attempt to read a config file if it exists
if [ -r "${XDG_CONFIG_HOME}/microsoft-edge-stable-flags.conf" ]; then
EDGE_USER_FLAGS="$(cat "$XDG_CONFIG_HOME/microsoft-edge-stable-flags.conf")"
fi
SHELL
) && sed -i -z "s|#\n|$readflag_script|; /exec/{s|\"\$@\"|\$EDGE_USER_FLAGS \$@|}" \
"${pkgdir}/opt/microsoft/${_pkgshortname}/${_pkgname}"
Will be better? Just edit /opt/microsoft/msedge/microsoft-edge to add ${XDG_CONFIG_HOME}/microsoft-edge-stable-flags.conf support, so flags will also be applied to PWA apps.
@ItachiSan now I just merge script /usr/bin/microsoft-edge-stable into /opt/microsoft/msedge/microsoft-edge to make my command line work
Pinned Comments
aakashhemadri commented on 2022-03-29 13:23 (UTC) (edited on 2022-03-29 13:24 (UTC) by aakashhemadri)
Please wait 30 minutes after a new update is released by Microsoft. The out-of-date flag sends an email notification to all those subscribed. If after a day the package stays out-of-date then please go ahead and flag the package as out-of-date to notify us.