Your message dated Sat, 22 Apr 2017 06:45:21 -0700
with message-id <[email protected]>
and subject line Re: Bug#860466: RFS: equivs/2.0.10 [QA] -- Circumvent Debian
package dependencies
has caused the Debian Bug report #860466,
regarding RFS: equivs/2.0.10~exp1 [QA] -- Circumvent Debian package dependencies
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.)
--
860466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860466
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: [email protected]
Dear mentors,
I am looking for a sponsor for my package "equivs"
* Package name : equivs
Version : 2.0.10
Upstream Author : Debian Native Package
* URL : https://tracker.debian.org/pkg/equivs
* License : GPL-2+
Section : admin
It builds those binary packages:
equivs - Circumvent Debian package dependencies
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/equivs
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/e/equivs/equivs_2.0.10.dsc
or you can use git-buildpackage:
git clone https://github.com/rogers0/equivs
cd equivs
git checkout qa_upload
gbp buildpackage -uc -us --git-ignore-branch
Changes since the last upload:
equivs (2.0.10) unstable; urgency=medium
* QA upload.
* Strip subdirectories before installing file listed in "Files:".
Thanks to RjY <[email protected]> and
Euan Thoms <[email protected]>. (Closes: #662946)
* Fix that equivs-build doesn't work if & is part of PWD.
Thanks to Martin Mrazik and era eriksson <[email protected]>.
(Closes: #679101) (LP: #881153, #1016402)
* debian/README.Debian:
- Fix typos. Thanks to Regid Ichira <[email protected]> (Closes: #724608)
* debian/rules:
- Thanks to Reiner Herrmann <[email protected]>, this package should be
reproducible now. (Closes: #786714)
* debian/copyright:
- Make DEP5 copyright
* debian/{control,compat}
- Bump debhelper to version 9.
* Bump versions in template:
- standard version to 3.9.8
- debhelper version to 9
- source version to 3.0 (quilt)
* debian/control:
- Bump stardard version to 3.9.8 (no change required)
* debian/source/format:
- Bump to 3.0 (native).
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
pgp535aB1zNjL.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Dear Roger,
On Fri, Apr 21, 2017 at 10:15:06PM +0900, Roger Shimizu wrote:
> > I'd like to note that I'm planning to upload with dgit, so you shouldn't
> > rebase after the upload. It's okay to rebase before the upload.
>
> Understand.
> I always cut the final releasing commit and append with new commit, or amend
> the last commit, which you may call it rebase, and finally add a new releasing
> commit and push to a new branch, such as mentors2 or qa_upload2.
>
> Old branch is also kept, you you can easily "git show-branch" or "git diff"
> between branches. So you can know what has been changed.
Yes, it was definitely the right thing to do to retain the old branches.
Uploaded -- thanks again.
--
Sean Whitton
signature.asc
Description: PGP signature
--- End Message ---
