Skip to content
Snippets Groups Projects

Upgrade to upstream v1.13.7

Merged nicoo requested to merge nicoo/repo:1.13.7/master into master
  • Upgrade to v1.13.7 (see !1 (merged) and !2 (merged) for the changes to upstream and pristine-tar)
  • Switch to using Python 3 (#938352)
  • Refresh shebang patch

I also did some routine maintenance tasks while I was at it:

  • Declare compliance with policy v4.4.1. (No change needed.)
  • Upgrade to dh compatibility level 12, use Build-Depends: debhelper-compat rather than old-style debian/compat.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Author Contributor

    @eighthave I can easily make the “cosmetic” changes into a separate MR if you would prefer.

    Moreover, if the mess of MRs is too annoying to merge (unfortunately, a MR can only target a single branch at the time, and the git-buildpackage workflow requires touching multiple branches), I can push those changes (if you approve of them and grant me access to the packaging repo).

  • These merge requests are OK as it is. We'd love to have you on the Android Tools team, please post a request to the list, that's our process for getting push access.

    I merged them, and uploaded a new version of this package.

  • Author Contributor

    @eighthave Thanks for the switch review, merge, and upload! :O

    Re: joining the team, that seems like a pretty large commitment, especially since I do not have the energy to spare for picking up maintainership of many packages. That said, if you all are OK with me only assuming co-maintainership of packages I'm using (like repo), I would be happy to help with that :)

    PS: Sorry for the slow reply, I wrote this on the same day and promptly forgot to hit “Comment”

Please register or sign in to reply
Loading