Created attachment 1930421 [details] SRPM of purple-googlechat, which should replace purple-hangouts Description of problem: Google in its infiinite wisdom shut down hangouts and replaced it with Google Chat (same features; contact lists got transferred). This renders purple-hangouts disfunctional and obsolete. It should be removed from future versions of Fedora. How reproducible: all the time, because Hangouts is not coming back Steps to Reproduce: 1. dnf install purple-hangouts 2. make hangouts account in pidgin 3. send a message Actual results: It seems to work (no errors on sending a message), but it just drops messages without warning, since they can't be delivered Expected results: Functionality or at least a warning about non-delivery! Additional info: I'd recommend removing all files from the RPM, and making it depend on purple-googlechat (which I'm currently in the process of packaging, see attached SRPM). purple-googlechat has a built in "hey, you seem to have an old google hangouts account. Want to migrate?" dialog in pidgin. Very nice.
Honest question: If I give you a ready-to-use fedpkg-compatible git repo, would you want to be packager/maintainer for purple-googlechat, @vitaly ?
> This renders purple-hangouts disfunctional and obsolete. It should be removed from future versions of Fedora. I agree. > I'd recommend removing all files from the RPM This package must be obsoleted by purple-googlechat: Provides: purple-hangouts = %{?epoch:%{epoch}:}%{version}-%{release} Obsoletes: purple-hangouts < %{?epoch:%{epoch}:}%{version}-%{release} Then I will retire this package. > SRPM of purple-googlechat, which should replace purple-hangouts Do you want to maintain it in Fedora? > Honest question: If I give you a ready-to-use fedpkg-compatible git repo, would you want to be packager/maintainer for purple-googlechat Only in Fedora main repository.
> Only in Fedora main repository. You'd be most welcome to do that :) You can find the repo (for as long as you need it there) on https://github.com/marcusmueller/purple-googlechat ; please feel free to import it into pagure/rpms. Is that what you had in mind? > This package must be obsoleted by purple-googlechat: > … Proposed changes can be found in the repo above.
> You can find the repo (for as long as you need it there) on https://github.com/marcusmueller/purple-googlechat ; please feel free to import it into pagure/rpms. Is that what you had in mind? Do you want to maintain it in Fedora? I can sponsor you to packagers group.
> I can sponsor you to packagers group. Already am in that group; `signify`, `verilator`. > Do you want to maintain it in Fedora? Truth be told, I'd prefer if you did that – it's really more of a continuation of purple-hangouts, and I have 0 experience with GTK-adjacent packaging. Plus, my track record as maintainer in terms of reaction times has been super bad – I always need to figure out anew how to do simple things like updates. And in the case of a purple protocol plugin, frequent updates might be paramount to functionality… But. I'd feel super bad letting someone else maintain the software that someone else wrote which I just packaged so that I get chat functionality. Hence my honest question whether you *want* to maintain purple-googlechat. It's just fitting best with you.
OK, I will open a new review request for purple-googlechat and obsolete purple-hangouts.
Thank you very much.
FEDORA-2022-9375a9deeb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9375a9deeb
FEDORA-2022-9375a9deeb 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-9375a9deeb \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9375a9deeb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-9375a9deeb has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.