qutebrowser 2.3.1 was released on July 28, 2021: https://github.com/qutebrowser/qutebrowser/releases/tag/v2.3.1 Comparing the source tarball to that of 2.3.0 reveals only minor changes, none of which affect requirements.txt or setup.py. Version 2.3.1 installs and runs fine using the unmodified 2.3.0 ebuild for a simple version bump.
Is there any progress on this? I actually created a pull request two weeks ago to speed things up, but there is still no activity.
(In reply to Christian Schroeder from comment #1) > Is there any progress on this? I actually created a pull request two weeks > ago to speed things up, but there is still no activity. Think the primary maintainer been away, unless there's a urgency I'd normally prefer the maintainer to acknowledge it before merging given they're more familiar with it (I don't use this) -- although it could be done if this keeps dragging.
(In reply to Ionen Wolkens from comment #2) > Think the primary maintainer been away, unless there's a urgency I'd > normally prefer the maintainer to acknowledge it before merging given > they're more familiar with it (I don't use this) -- although it could be > done if this keeps dragging. Well we are also listed as maintainers so go for it :) I usually runtime test and merge if it's fine. (In reply to Christian Schroeder from comment #1) > Is there any progress on this? I actually created a pull request two weeks > ago to speed things up, but there is still no activity. And thanks for that! We don't have many people go through these PRs, but we have hundreds of PRs open and dozen being opened each day. Sorry for your experience, but we'll get there.
(In reply to Joonas Niilola from comment #3) > Well we are also listed as maintainers so go for it :) I usually runtime > test and merge if it's fine. Yeah, I see we have a few people wanting this earlier than later so I'll have a look at it soon.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8f6b04f21535a396baee7d2651887ce7934452f3 commit 8f6b04f21535a396baee7d2651887ce7934452f3 Author: Christian Schroeder <chris.schroeder.public@gmail.com> AuthorDate: 2021-09-07 17:56:17 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2021-09-21 06:32:54 +0000 www-client/qutebrowser: version bump to 2.3.1 Closes: https://bugs.gentoo.org/808648 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Christian Schroeder <chris.schroeder.public@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/22239 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> www-client/qutebrowser/Manifest | 1 + www-client/qutebrowser/qutebrowser-2.3.1.ebuild | 90 +++++++++++++++++++++++++ 2 files changed, 91 insertions(+)
Hm, while I dislike the idea of using qtwebengine for daily browsing use, I don't dislike this browser from a quick look. If current maintainers don't have enough time to, I wouldn't be against just maintaining this myself -- or at least, if I decide to use it anyway.
Thanks for taking care of this! (In reply to Joonas Niilola from comment #3) > And thanks for that! We don't have many people go through these PRs, but we > have hundreds of PRs open and dozen being opened each day. Sorry for your > experience, but we'll get there. No problem. Is there a recommended (better) way to contribute an ebuild? I thought of a PR as probably the most efficient method. (In reply to Ionen Wolkens from comment #6) > Hm, while I dislike the idea of using qtwebengine for daily browsing use, I > don't dislike this browser from a quick look. Is it that you have reservations regarding qtwebengine in general or is this more of a Gentoo-specific perspective? I did notice it takes new versions of qtwebengine a while to get stabilized in the Gentoo repo.
(In reply to Christian Schroeder from comment #7) > > No problem. Is there a recommended (better) way to contribute an ebuild? I > thought of a PR as probably the most efficient method. Github PRs are definitely the easiest for us to review, test and merge. So yes it's the most efficient way, but still always an uphill battle for us ;) > > I did notice it takes new versions of > qtwebengine a while to get stabilized in the Gentoo repo. There's most likely some amount of reservation (and common sense) applied due to the sheer amount of compile time qtwebengine takes. To see if upstream comes up with other major, critical updates. (Just a guess, I'm not involved with qt in any way)
