#577 buildinfo --changelog prints bytestring
Closed: Fixed Opened by cqi.

As per title, an example is

* Mon Mar 14 2016 b'Lubom\xc3\xadr Sedl\xc3\xa1\xc5\x99 <lubomir.sedlar@gmail.com> - 1.41-1'
b"- Update upstream URL (lsedlar)\n- Fixes based on lsedlar's feedback (maxamillion)\n- add distgit namespacing for non-rpm content (docker, xdg-app, etc) (maxamillion)\n- Container-build: dont't allow to build with unpushed changes (araszka)\n- Suggest --dist option when can't get OS ver from branch (araszka)\n- fix: print all tags without filter (araszka)\n- Fix lookaside upload when --path is specified (araszka)\n- Lookaside: encoding repo name to UTF-8 (araszka)\n- Fix errors on Python 2.6 (lsedlar)\n- Add test and docstring to byte offset convertor (araszka)\n- Decode .spec file with UTF-8 (araszka)\n- 1271741 - add copr command (Recommends: copr-cli) (msuchy)\n- Suggest --target option when unknown target (araszka)"

Instead, following output would be more readable

* Mon Mar 14 2016 Lubomír Sedlář <lubomir.sedlar@gmail.com> - 1.41-1
- Update upstream URL (lsedlar)
- Fixes based on lsedlar's feedback (maxamillion)
- add distgit namespacing for non-rpm content (docker, xdg-app, etc) (maxamillion)
- Container-build: dont't allow to build with unpushed changes (araszka)
- Suggest --dist option when can't get OS ver from branch (araszka)
- fix: print all tags without filter (araszka)
- Fix lookaside upload when --path is specified (araszka)
- Lookaside: encoding repo name to UTF-8 (araszka)
- Fix errors on Python 2.6 (lsedlar)
- Add test and docstring to byte offset convertor (araszka)
- Decode .spec file with UTF-8 (araszka)
- 1271741 - add copr command (Recommends: copr-cli) (msuchy)
- Suggest --target option when unknown target (araszka)

@cqi Can you give me your build link?
And is Character Encoding of your terminal set to UTF-8?

Thanks

I used this build

koji buildinfo --changelog rpkg-1.50-1.fc28

Koji version: koji-1.13.0-2.fc25.noarch

~~Oddly enough, I cannot seem to replicate this with the client from HEAD (or for that matter the client from koji-1.13.0 release). Perhaps something is broken specifically in the Fedora build?~~

Nm, silly mistake

Metadata Update from @mikem:
- Issue set to the milestone: 1.15

Commit 62d4d1d1 fixes this issue

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/577

Please continue any further discussion there.

Metadata