Dave Plater
On 23/11/2017 15:13, Dominique Leuenberger / DimStar wrote:
Out of those only two packages are tracked as part of the rings (ffado and gpsd), which means from a Factory process perspective, once those two are fixed, the scons-switch to python3 could happen.
I've sorted out the rest of the print() errors, maybe I should submit it so long. I'm now stuck on a strange error: Checking for a working C-compiler TypeError : sequence item 0: expected str instance, bytes found Giving no indication of where the error is but a context.TryRun( to test the c compiler is the point that it's at. Unfortunately my scons and python2 to 3 skills are a bit rusty so any help will be appreciated. https://build.opensuse.org/package/show/home:plater/ffado I've failed to get a more verbose error so far.
This error is typically due to a mixup of raw bytes and unicode strings. In python 2, there were two types of strings: ascii strings and unicode strings. In practice, you'd read from a command line tool and get bytes which would be interpreted as an ascii string. In python 3, there are only unicode strings. All of the file reading or command line tool reading code now return bytes, that have to be decoded into unicode using a particular interpretation: ascii, utf-8, or something else. If the error had been reported with a file and line number, it'd be easier to figure out what was going wrong...
Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- // Kristoffer Grönlund // kgronlund@suse.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org