subunit should depend on python3-junitxml

In case anyone cares, here is what happens when you try to just run subunit2junitxml in saucy with the python2.7 target (I don't care if this works, I just was trying to workaround):

$ trial --reporter=subunit landscape/lib/tests/test_bpickle.py | python /usr/bin/subunit2junitxml
�!@stdout�$��!@stdouteb"�!@stdouts���.�!@@Lstdout;t: landscape.lib.tests.test_bpickle.BPickleTest.test_bool
s�G�!@@Ustdout@Cuccessful: landscape.lib.tests.test_bpickle.BPickleTest.test_bool
tE�>��!@stdouteb"�!@stdouts���.�!@@Lstdout;t: landscape.lib.tests.test_bpickle.BPickleTest.test_dict
s���>�!@@�stdout@�uccessful: landscape.lib.tests.test_bpickle.BPickleTest.test_dict
test: landscape.lib.tests.test_bpickle.BPickleTest.test_float
sj��!@stdoutu�stdoutc�A�J�!@stdoutc�A�J�!@stdouteb"�!@stdouts���.�!@stdouts���.�!@stdoutf�+Uų!@stdoutu�stdoutlstdout:��H�!@stdout d��`�!@stdoutlstdoutaeO�f�!@stdoutn���!@stdoutd%4@stdouts���.�!@stdoutc�A�J�!@stdoutaeO�f�!@stdoutp����!@stdouteb"�!@stdout.�,�g�!@stdoutlstdoutik�HT�!@stdoutb�F�ܳ!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdouts���.�!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout_�.�!@stdoutb�F�ܳ!@stdoutp����!@stdoutik�HT�!@stdoutc�A�J�!@stdoutk��)x�!@stdoutlstdouteb"�!@stdout.�,�g�!@stdoutB��!@stdoutP4��\�!@stdoutik�HT�!@stdoutc�A�J�!@stdoutk��)x�!@stdoutlstdouteb"�!@stdoutT3�E�!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout_�.�!@stdoutf�+Uų!@stdoutlstdouto���!@stdoutaeO�f�!@stdout�$��!@stdout
�/x��!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout:��H�!@stdout d��`�!@stdoutlstdoutaeO�f�!@stdoutn���!@stdoutd%4@stdouts���.�!@stdoutc�A�J�!@stdoutaeO�f�!@stdoutp����!@stdouteb"�!@stdout.�,�g�!@stdoutlstdoutik�HT�!@stdoutb�F�ܳ!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdouts���.�!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout_�.�!@stdoutb�F�ܳ!@stdoutp����!@stdoutik�HT�!@stdoutc�A�J�!@stdoutk��)x�!@stdoutlstdouteb"�!@stdout.�,�g�!@stdoutB��!@stdoutP4��\�!@stdoutik�HT�!@stdoutc�A�J�!@stdoutk��)x�!@stdoutlstdouteb"�!@stdoutT3�E�!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout_�.�!@stdoutf�+Uų!@stdoutlstdouto���!@stdoutaeO�f�!@stdout�$��!@stdout_�.�!@stdouts���.�!@stdoutc�A�J�!@stdoutik�HT�!@stdouteb"�!@stdoutn���!@stdout�$��!@stdoutik�HT�!@stdoutf�+Uų!@stdoutik�HT�!@stdoutc�A�J�!@stdout_�.�!@stdoutn���!@stdouto���!@stdout�$��!@stdoutaeO�f�!@stdout�$��!@stdoutik�HT�!@stdouto���!@stdoutn���!@stdout
�/x��!@stdouts���.�!@stdoutu�stdoutc�A�J�!@stdoutc�A�J�!@stdouteb"�!@stdouts���.�!@stdouts���.�!@stdoutf�+Uų!@stdoutu�stdoutlstdout:��H�!@stdout d��`�!@stdoutlstdoutaeO�f�!@stdoutn���!@stdoutd%4@stdouts���.�!@stdoutc�A�J�!@stdoutaeO�f�!@stdoutp����!@stdouteb"�!@stdout.�,�g�!@stdoutlstdoutik�HT�!@stdoutb�F�ܳ!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdouts���.�!@stdout.�,�g�!@stdout�$��!@stdouteb"�!@stdouts���.�!@stdout�$��!@stdout_�.�!@stdoutb�F�ܳ!@stdoutp����!@stdoutik�HT�!@stdoutc�A�J�!@stdoutk��)x�!@stdoutlstdouteb"�!@stdout.�,�g�!@stdoutB��!@stdoutP4��\�!@stdoutik�HT�!@stdoutc�A�J�!@std...

This is a packaging issue; upstream code has python3 support just fine.

Status changed to 'Confirmed' because the bug affects multiple users.

FWIW there *is* a Python 3 version of subunit2junitxml in the Saucy repositories

⟫ apt-cache policy python3-junitxml
python3-junitxml:
  Installed: 0.6-1.1
  Candidate: 0.6-1.1
  Version table:
 *** 0.6-1.1 0
        500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

note the output still looks malformed as per comment #1

This appears to be just subunit v1 output. subunit2junitxml only parses subunit v2 output. You can use the following fix:

Starting with 13.09, you can address this to parse the old output:

 ./run-my-old-tests | subunit-1to2 | subunit2junitxml

I'm closing this bug now, as this is just an old subunit format that is supported by the tool included in 13.09.

Thanks!

Actually, I guess I'll leave this open to address the packaging issue. subunit in trusty should include a dependency of python3-junitxml

Sorry for the noise....

The attachment "Patch to the ubuntu/subunit packaging branch (trusty)" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

Is this an ubuntu specific issue? subunit2junitxml on Debian just use #!/usr/bin/python - in other words, Python 2.

[Expired for subunit (Ubuntu) because there has been no activity for 60 days.]