Custom Query (308 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (7 - 9 of 308)

1 2 3 4 5 6 7 8 9 10 11 12 13
Ticket Resolution Summary Owner Reporter
#330 fixed os2-base spec diver
Description

after the new libc release we should remove the fhs part completely. as we never have a /@unixroot/bin directory anymore.

#329 duplicate libc spec diver
Description

the db1-devel and gettext-devel stuff needs to be removed, as we have db4 which includes db1 support and gettext itself. The installation of the 2 above rpm will lead to issues, as the same files exists in the corresponding newer rpm.

#328 fixed Python does not recognize OS/2 Chinese codepage (1386) ataylor
Description

YUM unfortunately fails when run on OS/2 Simplified Chinese version using the standard codepage (1386).

Traceback (most recent call last):
  File "/@unixroot/usr/lib/python2.7/site.py", line 550, in <module>
    main()
  File "/@unixroot/usr/lib/python2.7/site.py", line 540, in main
    setencoding()
  File "/@unixroot/usr/lib/python2.7/site.py", line 494, in setencoding
    sys.setdefaultencoding(encoding) # Needs Python Unicode build !
LookupError: unknown encoding: CP1386

I wonder if this is because (being ported software) it expects the GBK encoding to be codepage 936 instead? (936 is the GBK codepage under Windows. OS/2 uses codepage number 1386 instead.)

Perhaps an alias or mapping needs to be added somewhere?

(In spite of the superficial similarity to ticket #88, I suspect this is not actually the same error condition. However, similarly to #88, yum can be forced to run by changing the process codepage to 850 and setting LANG=en_US.)

1 2 3 4 5 6 7 8 9 10 11 12 13
Note: See TracQuery for help on using queries.