[chirp_devel] [patch] [py3] fixed collections traceback
It's for the py3 branch. I tested it with the UV-5R and it worked without traceback.
This change was already committed on March 7. See:
https://github.com/kk7ds/chirp/commit/8bc8553ccc169405044f27a1037380fe427997...
Perhaps your local tree was out of date?
Martin. KD6YAM
On Sun, Aug 28, 2022 at 4:18 PM Jaroslav Skarvada via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
It's for the py3 branch. I tested it with the UV-5R and it worked without traceback. _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
I cannot find it here: https://chirp.danplanet.com/projects/chirp/repository/show?rev=py3
What's the official repository for the py3 port?
thanks & regards
Jaroslav
On Mon, Aug 29, 2022 at 3:02 AM Martin Cooper mfncooper@gmail.com wrote:
This change was already committed on March 7. See:
https://github.com/kk7ds/chirp/commit/8bc8553ccc169405044f27a1037380fe427997...
Perhaps your local tree was out of date?
Martin. KD6YAM
On Sun, Aug 28, 2022 at 4:18 PM Jaroslav Skarvada via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
It's for the py3 branch. I tested it with the UV-5R and it worked without traceback. _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
Oh, that's very strange. The Mercurial and GitHub repos are supposed to be mirrors of each other. It looks like there might be an issue with the mirroring process. I'm not sure if it's automated or manual. Dan, any thoughts?
Martin. KD6YAM
On Mon, Aug 29, 2022 at 7:17 AM Jaroslav Skarvada jskarvad@redhat.com wrote:
I cannot find it here: https://chirp.danplanet.com/projects/chirp/repository/show?rev=py3
What's the official repository for the py3 port?
thanks & regards
Jaroslav
On Mon, Aug 29, 2022 at 3:02 AM Martin Cooper mfncooper@gmail.com wrote:
This change was already committed on March 7. See:
https://github.com/kk7ds/chirp/commit/8bc8553ccc169405044f27a1037380fe427997...
Perhaps your local tree was out of date?
Martin. KD6YAM
On Sun, Aug 28, 2022 at 4:18 PM Jaroslav Skarvada via chirp_devel <
chirp_devel@intrepid.danplanet.com> wrote:
It's for the py3 branch. I tested it with the UV-5R and it worked without traceback. _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs:
So to be clear, is the [1] the official upstream github CHIRP repository? Currently, I don't care about the sync, and personally git is better for me than mercurial, so I will just update my links. But I think the wiki should also be updated. And another question: is it OK to PR the patches through the github, or is it required to send them to this mailing list?
thanks & regards
Jaroslav
[1] https://github.com/kk7ds/chirp
On Mon, Aug 29, 2022 at 4:42 PM Martin Cooper mfncooper@gmail.com wrote:
Oh, that's very strange. The Mercurial and GitHub repos are supposed to be mirrors of each other. It looks like there might be an issue with the mirroring process. I'm not sure if it's automated or manual. Dan, any thoughts?
Martin. KD6YAM
On Mon, Aug 29, 2022 at 7:17 AM Jaroslav Skarvada jskarvad@redhat.com wrote:
I cannot find it here: https://chirp.danplanet.com/projects/chirp/repository/show?rev=py3
What's the official repository for the py3 port?
thanks & regards
Jaroslav
On Mon, Aug 29, 2022 at 3:02 AM Martin Cooper mfncooper@gmail.com wrote:
This change was already committed on March 7. See:
https://github.com/kk7ds/chirp/commit/8bc8553ccc169405044f27a1037380fe427997...
Perhaps your local tree was out of date?
Martin. KD6YAM
On Sun, Aug 28, 2022 at 4:18 PM Jaroslav Skarvada via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
It's for the py3 branch. I tested it with the UV-5R and it worked without traceback. _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
That GitHub repo was created by Dan (Chirp project owner) to encourage contributors more familiar with Git(Hub) than Mercurial to get involved with Chirp, so it's certainly the official GitHub repo. I'd say that probably most of the people who've contributed to the py3 branch recently have done so via the GitHub repo.
People contributing to Chirp via the GitHub repo have been doing so via PRs, so I think that's fine. No need to also mail them to the list.
Martin. KD6YAM
On Thu, Sep 1, 2022 at 3:04 AM Jaroslav Skarvada via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
So to be clear, is the [1] the official upstream github CHIRP repository? Currently, I don't care about the sync, and personally git is better for me than mercurial, so I will just update my links. But I think the wiki should also be updated. And another question: is it OK to PR the patches through the github, or is it required to send them to this mailing list?
thanks & regards
Jaroslav
[1] https://github.com/kk7ds/chirp
On Mon, Aug 29, 2022 at 4:42 PM Martin Cooper mfncooper@gmail.com wrote:
Oh, that's very strange. The Mercurial and GitHub repos are supposed to
be mirrors of each other. It looks like there might be an issue with the mirroring process. I'm not sure if it's automated or manual. Dan, any thoughts?
Martin. KD6YAM
On Mon, Aug 29, 2022 at 7:17 AM Jaroslav Skarvada jskarvad@redhat.com
wrote:
I cannot find it here: https://chirp.danplanet.com/projects/chirp/repository/show?rev=py3
What's the official repository for the py3 port?
thanks & regards
Jaroslav
On Mon, Aug 29, 2022 at 3:02 AM Martin Cooper mfncooper@gmail.com
wrote:
This change was already committed on March 7. See:
https://github.com/kk7ds/chirp/commit/8bc8553ccc169405044f27a1037380fe427997...
Perhaps your local tree was out of date?
Martin. KD6YAM
On Sun, Aug 28, 2022 at 4:18 PM Jaroslav Skarvada via chirp_devel <
chirp_devel@intrepid.danplanet.com> wrote:
It's for the py3 branch. I tested it with the UV-5R and it worked without traceback. _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs:
http://chirp.danplanet.com/projects/chirp/wiki/Developers
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
Oh, that's very strange. The Mercurial and GitHub repos are supposed to be mirrors of each other. It looks like there might be an issue with the mirroring process. I'm not sure if it's automated or manual. Dan, any thoughts?
Yeah, I guess I haven't pushed the py3 branch from git to mercurial, and on to the main repo that redmine looks at. TBH it's a pain, and I'd be happy to just keep the py3 stuff on the github side to avoid having to sync that stuff.
--Dan
participants (3)
-
Dan Smith -
Jaroslav Skarvada -
Martin Cooper