Your message dated Sat, 12 Nov 2016 17:51:50 +0000
with message-id <[email protected]>
and subject line Re: Bug#843430: RFS: ocrmypdf/4.3-1
has caused the Debian Bug report #843430,
regarding RFS: ocrmypdf/4.3.2-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
843430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843430
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for a new release of ocrmypdf.
I have DM upload rights for this package, but this revision introduces a
new binary package, ocrmypdf-doc.
* Package name : ocrmypdf
Version : 4.3-1
Upstream Author : James R. Barlow <[email protected]>
* URL : https://github.com/jbarlow83/OCRmyPDF
* License : Expat
Section : graphics
Changes since the last upload:
* New upstream release.
- Remove dropped tasks.py from d/copyright.
* New ocrmypdf-doc binary package: upstream's new HTML documentation.
- Set PYBUILD_DESTDIR in d/rules.
- Add override_dh_{auto_build,installdocs,sphinxdoc} targets to d/rules.
- ocrmypdf suggests python-watchdog.
See "Cookbook" documentation entry.
- New build dependencies:
- python3-sphinx
- python3-sphinx-rtd-theme
* Add doc-base registration.
* Add patch-docs-for-Debian.patch
* Add path-to-docs-for-Debian.patch
* Add disable-mathjax.patch
* Add pip-to-apt-get.patch
* Bump debhelper compat & build-dep to 10.
I normally upload ocrmypdf with dgit, so I'd like to request sponsorship
using dgit so that the git history on dgit-repos is not interrupted.
% git clone https://git.spwhitton.name/ocrmypdf
% cd ocrmypdf
% git rev-parse HEAD
14ee9e157b2347d13c0dc90316514db8c36cb9c5
% origtargz # invokes pristine-tar to extract orig.tar
% sha256sum ../ocrmypdf_4.3.orig.tar.xz
dc79c4078e1fd0cb8fa5c010f418fc00a7683da3f27add7477289e38daf07b02
../ocrmypdf_4.3.orig.tar.xz
% dgit fetch
% git diff dgit/dgit/sid..HEAD # review my changes
% git diff dgit/dgit/sid..HEAD -- debian # review just debian/ changes
% dgit sbuild || dgit gbp-build --git-pbuilder
# ^ no source-only uploads to binNEW!
% dgit push
If you have any trouble with this, I'd appreciate if you'd ask me about
it rather than doing an upload that bypasses dgit, as that would break
the history on dgit-repos. I'm interested in making sponsorship with
dgit a smooth and well-documented process.
Thanks.
--
Sean Whitton
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sat, Nov 12, 2016 at 08:26:48AM -0700, Sean Whitton wrote:
> That's a perfectly reasonable way to use dgit. Don't use -b/-F.
-F is the deafault if you don't specify anything, so well, I've used -F
:P
> Do you think this could be better documented? I guess there is no
> manpage corresponding to your workflow. Maybe it could be added to
> dgit-maint-merge(7)?
I think I'm going to think about it and maybe open a bug or two.
> Please try turning off your pbuilder tmpfs. That worked last time, when
> you originally sponsored ocrmypdf. Or you could just use deb-o-matic.
oh...
I forgot about this!
you know, a lot of stuff happened since that time :)
| dgit ok: pushed and uploaded 4.3.2-2
\o/
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
