Fritz, When sponsoring a package, I usually like to built it myself from the Git repository. When cloning from
https://github.com/qutebrowser/qutebrowser-debian.git it looks like your recent changes have not yet been pushed to the repository. Could you please do so? (It is customary to push the changes to the repository but not tag the release until after the package has been sponsored. That way, if any changes are needed, they can be committed before it is tagged.) Thanks, Soren On Tuesday, July 9, 2024 2:45:35 PM MST Fritz Reichwald wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "qutebrowser": > > * Package name : qutebrowser > Version : 3.1.0-1 > Upstream contact : Florian Bruhin <m...@qutebrowser.org> > * URL : https://qutebrowser.org/ > * License : MPL-1.1 or GPL-2+ or LGPL-2.1+, GPL-3+, CC-BY-SA-3.0, > Expat, BSD-3-Clause, MIT * Vcs : > https://github.com/qutebrowser/qutebrowser-debian Section : web > > The source builds the following binary packages: > > qutebrowser - Keyboard-driven, vim-like browser based on Python and Qt > qutebrowser-qtwebengine - QtWebEngine backend dependency package for > qutebrowser qutebrowser-qtwebkit - QtWebKit backend dependency package for > qutebrowser > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/qutebrowser/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/q/qutebrowser/ qutebrowser_3.1.0-1 > .dsc > > Changes since the last upload: > > qutebrowser (3.1.0-1) unstable; urgency=medium > . > [ Fritz Reichwald ] > * Add upstream signing key to debian/upstream/signing-key.asc > * New upstream version 3.1.0 (Closes: #1062231) > * Add debian changes for release 3.1.0 > > Regards, > Fritz -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
