Upgrade community/py3-pydot and community/py3-pygraphviz

This PR upgrade community/py3-pydot from 1.4.1 to 2.0.0 and community/py3-pygraphviz from 1.10 to 1.13. Both of these packages are optional dependencies of community/py3-networkx and are below the minimum version required by networkx.

This PR removes the py3-pygraphviz-doc subpackage because it wasn't actually docs. The subpackage just contained some example code; building pygraphviz's actual documentation depends on some packages not yet in aports.

added 1 commit

• 0adbaff8 - Upgrade community/py3-pydot and community/py3-pygraphviz

Compare with previous version

added 44 commits

• 0adbaff8...5261dfaa - 43 commits from branch alpine:master
• b496d39d - Upgrade community/py3-pydot and community/py3-pygraphviz

Compare with previous version

@michaelfm1211 Thanks for your contribution. Could you please split this commit up into 2 separate commits, one for each package? See also our commit style guide.

added status:mr-changes-requested label

added 2 commits

• 98ab924a - community/py3-pydot: upgrade to 2.0.0
• bed4bff6 - community/py3-pygraphviz: upgrade to 1.13

Compare with previous version

resolved all threads

added 511 commits

• bed4bff6...a8740c96 - 509 commits from branch alpine:master
• f1073fc3 - community/py3-pydot: upgrade to 2.0.0
• 5577eb0a - community/py3-pygraphviz: upgrade to 1.13

Compare with previous version

removed status:mr-changes-requested label

CC: @itoffshore for py3-pygraphviz

added status:mr-waiting-maintainer-feedback label

added status:mr-stale label

Sorry to bother you @michaelfm1211,

but we've detected that this merge request hasn't seen any recent activity. If you need help or want to discuss your approach with developers you can ping @team/mentors. You can also ask on IRC on #alpine-devel on irc.oftc.net. If no further activity occurs in this MR, Alpine developers may close it in the future.

Thanks for your contribution.

@itoffshore Have you had a chance to look at this PR yet?

@michaelfm1211 - as Kevin mentioned please split these changes into 2 x commits. Updates to packages in aports should always be in a single commit so they are easier to search for & view changes (I mostly put each change in a single PR)

I would copy the updated APKBUILD's to somewhere outside of aports & revert the changes on one library (by copying the current APKBUILD into your feature branch) - & rebase / rename this commit:

# example fixup / rebase of 2 x commits
git add .
git commit # I always put 'fixup' in the commit message
git rebase -i HEAD~2

in the EDITOR that opens:

• change your fixup commit operation from pick to fixup
• change the operation of the first commit in the EDITOR to reword & fix the commit message (for the single library) - after you save these 2 x changes the EDITOR will open again allowing you to change / reword the original commit message
• force update the remote branch: git push -u origin +my-branch-name

& make the 2nd commit for the 2nd library you reverted changes for.

Using Alpine LXD containers has always worked very well for me as a build environment. I made building custom LXD containers quite easy:

• https://github.com/itoffshore/distrobuilder-menu - & include an Alpine Edge environment

not sure what happened here, as at the time of writing the last comment the commits were already split; with no other comments, i'll treat this as an ACK and commence with the merge ( it's been far too long, to be honest )

added 7966 commits

• 5577eb0a...fdb045f2 - 7964 commits from branch alpine:master
• 9dc57e62 - community/py3-pydot: upgrade to 2.0.0
• e51bd792 - community/py3-pygraphviz: upgrade to 1.13

Compare with previous version

enabled an automatic merge when the pipeline for e51bd792 succeeds

merged