Description of problem: chrome-gnome-shell GitLab repository used to have both browser extension and host connector, but the developer split in 'gnome-browser-extension' and 'gnome-browser-connector': - https://gitlab.gnome.org/GNOME/gnome-browser-extension - https://gitlab.gnome.org/nE0sIghT/gnome-browser-connector chrome-gnome-shell GitLab repository was renamed to 'gnome-browser-extension' and contains only extension-related stuff, while 'gnome-browser-connector' is the content that this package relies on. The extension bumped to version 11 and is already available in the browsers extension/add-on stores, and it is now incompatible with chrome-gnome-shell connector version 10. Therefore it is important to update this package name and content to gnome-browser-connector in order to allow that this package's users can make full correct use of its features. Version-Release number of selected component (if applicable): 10.1 See the merge request that renamed the project and split removed connector-related files from the browser extension repository: https://gitlab.gnome.org/GNOME/gnome-browser-extension/-/merge_requests/9 For reference, see Arch Linux AUR package: https://aur.archlinux.org/packages/gnome-browser-connector
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
Further, on F35 using `chrome-gnome-shell`, extensions.gnome.org reports: > Your native host connector do not support following APIs: v6. Probably you should upgrade native host connector or install plugins for missing APIs. Refer documentation for instructions.
I can confirm that rebuilding the SRPM from FPS with gnome-browser-extension v42.0 works with a additional patch, and updates in the .spec file including switching to meson, fixes the error reported by Rafael.
Created attachment 1905290 [details] Patch to spec file to update to v42.0
Created attachment 1905291 [details] Patch to disambiguate python binary
I have the same problem as #c2 on Fedora 36 with latest chrome-gnome-shell-10.1-15.fc36.x86_64. Please, consider fixing this before F37 is released since it is blocking basic functionality of Shell Extensions installation.
Proposed as a Blocker and Freeze Exception for 37-final by Fedora user asciiwolf using the blocker tracking app because: The chrome-gnome-shell package has been renamed to gnome-browser-connector in upstream. The chrome-gnome-shell package uses old api that is not supported anymore by the extensions.gnome.org website. I consider this being a F37 Final blocker since it blocks basic functionality of Shell Extensions installation.
(In reply to Fedora Blocker Bugs Application from comment #7) > Proposed as a Blocker and Freeze Exception for 37-final by Fedora user > asciiwolf using the blocker tracking app because: > > The chrome-gnome-shell package has been renamed to gnome-browser-connector > in upstream. The chrome-gnome-shell package uses old api that is not > supported anymore by the extensions.gnome.org website. I consider this being > a F37 Final blocker since it blocks basic functionality of Shell Extensions > installation. Agreed. I'm running Fedora 37 and this is a definite issue, but it looks like the Fedora 37 Beta has been greenlighted. :-(
(In reply to Scott Beamer from comment #8) > Agreed. I'm running Fedora 37 and this is a definite issue, but it looks > like the Fedora 37 Beta has been greenlighted. :-( You can vote for the Fedora 37 Final blocker here: https://pagure.io/fedora-qa/blocker-review/issue/903
(In reply to Rafael Fontenelle from comment #0) > Description of problem: > > chrome-gnome-shell GitLab repository used to have both browser extension and > host connector, but the developer split in 'gnome-browser-extension' and > 'gnome-browser-connector': > > - https://gitlab.gnome.org/GNOME/gnome-browser-extension > - https://gitlab.gnome.org/nE0sIghT/gnome-browser-connector > > chrome-gnome-shell GitLab repository was renamed to > 'gnome-browser-extension' and contains only extension-related stuff, while > 'gnome-browser-connector' is the content that this package relies on. > > The extension bumped to version 11 and is already available in the browsers > extension/add-on stores, and it is now incompatible with chrome-gnome-shell > connector version 10. Therefore it is important to update this package name > and content to gnome-browser-connector in order to allow that this package's > users can make full correct use of its features. > > Version-Release number of selected component (if applicable): > 10.1 > > See the merge request that renamed the project and split removed > connector-related files from the browser extension repository: > https://gitlab.gnome.org/GNOME/gnome-browser-extension/-/merge_requests/9 > > For reference, see Arch Linux AUR package: > https://aur.archlinux.org/packages/gnome-browser-connector Where is the gnome-browser-connector review request?, it isn't acceptable to change the spec file name and package source.
(In reply to leigh scott from comment #10) > Where is the gnome-browser-connector review request?, it isn't acceptable to > change the spec file name and package source. What about changing the chrome-gnome-shell to ship the new gnome-browser-connector package instead (but without renaming the current package)? There should not be any big differences between the two packages and we can rename the package later. It is still better than shipping a package that is a core part of Fedora Workstation and does not work anymore, at least in my opinion.
(In reply to Daniel Rusek from comment #11) > (In reply to leigh scott from comment #10) > > Where is the gnome-browser-connector review request?, it isn't acceptable to > > change the spec file name and package source. > > What about changing the chrome-gnome-shell to ship the new > gnome-browser-connector package instead (but without renaming the current > package)? There should not be any big differences between the two packages > and we can rename the package later. It is still better than shipping a > package that is a core part of Fedora Workstation and does not work anymore, > at least in my opinion. That would violate the packaging guidelines. https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages
Hi, we l have this problem since at least FC35 already. FC36 isn't an exception. Why “votes” for FC37, if it is a long existing issue already?!
(In reply to Alex. H. F. from comment #13) > Why “votes” for FC37, if it is a long existing issue already?! I think that this issue started happening some time after F36 was released.
Leigh: the spec file and source package name not matching the git repo name is not allowed, but I think it is allowed to have the chrome-gnome-shell source RPM generate only a binary package named `gnome-browser-connector`. There are plenty of other cases of source package foo not generating any binary package called foo, after all... Of course, doing a package rename request would be cleaner I guess, but if we don't have time to get it through, I think just changing the binary package name doesn't break any rules.
Discussed during the 2022-09-12 blocker review meeting: [0] The decision to delay the classification of this as a blocker bug and accept this as an AcceptedFreezeException (Final) was made as we agreed that current criteria do not cover this, but it's a serious issue and we may want to cover it. adamw will propose a new criterion for discussion, blocker decision is delayed while we do that. We certainly agree it's important enough for a freeze exception. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-09-12/f37-blocker-review.2022-09-12-16.01.txt
I talked to Pete Walter and he was fine with me packaging the renamed version, so I went ahead and submitted the new package for review: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2127314
I think we can call this POST, since the new package review is done and the repo is created...
FEDORA-2022-3e8733980f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3e8733980f
FEDORA-2022-9756945a87 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9756945a87
FEDORA-2022-9756945a87 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-9756945a87 \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9756945a87 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-3e8733980f has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-3e8733980f \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3e8733980f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-9756945a87 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-3e8733980f has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.