FreeBSD use bugzilla for PRs management, you need to use browser to send-pr now. But, if you use Mothra, you could send-pr from command line as you want. Usage: - mothra search <keyword>, <days_ago=180> - mothra submit <summary>, <file_path> - mothra attach <bug_id>, <file_path> - mothra browse <bug_id> - mothra create <summary> - mothra get <bug_id>

1. Mothra
A FreeBSD send-pr tool for bugzilla system
Daniel Lin (pct), BSDTW 2017
https://github.com/pct/mothra
https://github.com/pct/freebsd_utils

2. Preface
When I was 20, I was a
journalism student.

3. Preface
Because of the School
BBS system, I start
using FreeBSD.
// do you ever make world everyday?

4. Preface
Thanks for FreeBSD, I
got my first job as a
sysadmin. I like the job
better than be a
reporter.

5. Preface
I love FreeBSD so
much, want to improve
it, then I start learning
programming.

6. Preface
There are some ports maintained by me:
- benchmarks/tsung
- devel/rubygem-rodzilla
- graphics/p5-Image-ExifTool-devel
- sysutils/py-pywatchman
- sysutils/py-ranger
- sysutils/rsyncrypto
- sysutils/rubygem-mothra
- sysutils/watchman
- www/node (until 2016/4/11, been very busy)
- www/phalcon

7. Preface
I love to using porttools to
send-pr in early years, but
FreeBSD using bugzilla to
manage PRs for these years,
I just could not send-pr from
command line as before.

8. Preface
I develop a send-pr tool
named “Mothra” (to battle
bugZilla).
// Project since 2014/12/29

9. Preface
Mothra
Godzilla
My next project?
http://www.alternateending.com/images/l6WyL0fZW8wkNEzZLIRWUFQdMEk.

10. Normal send-pr flow
At normal send-pr flow, you may switch to browser
and terminal (ex: www/phalcon):
1. Open Browser, go to https://bugs.freebsd.org,
check if there is already a new version update pr.
2. Open terminal, `cd /usr/ports/www/; cp -rpf
phalcon phalcon.orig` to save original ports.
3. `cd phalcon`, update Makefile, set PORTVERSION.
4. `make makesum`, to update distinfo file.
5. make port patch files and test.

11. Normal send-pr flow
6. `genplist test` and check pkg-plist file.
7. `genplist clean`
8. `cd ..; diff -ruN phalcon.orig phalcon >
phalcon-3.2.5.diff`
9. scp phalcon-3.2.5.diff to your desktop.
10. Back to browser, sign in bugzilla.
11. File a bug: fill complex form, add attachment
(phalcon-3.2.5.diff).
12. Submit Bug.

12. Normal send-pr flow
Hmmm…
12 steps.

13. Mothra
What’s the Mothra way?

14. Mothra
Install:
# gem install mothra
Get setting example:
# curl https://raw.githubusercontent.com/
pct/mothra/master/.mothra.yml >
~/.mothra.yml

15. Mothra
Setting (~/.mothra.yml):
BZ_URL: https://bugs.freebsd.org/bugzilla/
BZ_USER: test@example.com
BZ_PASSWD: test ### IT’S DANGER HERE!!! ###
PRODUCT: Ports & Packages
COMPONENT: Individual Port(s)
STATUS: ['New', 'Open', 'In Progress', 'UNCONFIRMED']

16. Mothra
Usage:
- mothra search <keyword>, <days_ago=180>
- mothra submit <summary>, <file_path>
- mothra attach <bug_id>, <file_path>
- mothra browse <bug_id>
- mothra create <summary>
- mothra get <bug_id>

17. Mothra
Mothra, with my `up2` scripts, save 12 -> 4 steps:
1. `mothra search phalcon` to check if already a update PR
2. `. up2 www/phalcon 3.2.4 3.2.5`, and check and
fix files
3. `diff -ruN phalcon.orig phalcon >
phalcon-3.2.5.diff`
4. `mothra submit “[MAINTAINER] www/phalcon
update to 3.2.5” phalcon-3.2.5.diff`

18. Mothra
Lazy, but save more time to
maintain more ports :-)
ex: I just send-pr this noon.

19. But…
I just know “pgollucci/
freebsd-bugzilla-cli” this
week.
You could try It also, it
seems more functional.

20. One more thing
The https://bsdtw.org/ website is designed by my team, 4Point
Design. We provide Graphic Design, Printing, Web and iOS/
Android App Design/Develop.
Hope to have the opportunity to work with you!

21. Source Code
GitHub:
- pct/mothra
- pct/freebsd_utils (send-pr)