On 14/01/2008, Mauro Lizaur wrote: > Hello there, 'lo.
> I recently adopted the python module python-osd, i could say that i've > already finished the work needed but i have a couple of question > though: First, I'd like to point you to the DPMT[1,2], which might act like a mentor with specific knowledge of python-specific troubles. 1. http://python-modules.alioth.debian.org/ 2. http://wiki.debian.org/Teams/PythonModulesTeam > 2) > ------ > python-osd: arch-independent-package-contains-binary-or-object > /usr/lib/python-support/python-osd/python2.4/_pyosd.so > The package contains a binary or object file but is tagged > 'Architecture: all'. > ------ > > With the 2nd lintian warning, i had to fix some mistakes i found on > the debian/control file, such as 'Architecture: any' i changed that to > all, (the prev version didn't had this error because the arch wasn't > "all") So again, what should i do with this? How was that an error? Why do you think that “Architecture: all” is more appropriate. I guess you should be able to say for yourself after having double-checked Policy 5.6.8. > the previous version used python 2.3 and python 2.4, but now i just > use 'current' which is python 2.4. Should i use python 2.4 and 2.5, > leave with 2.3 and 2.4 or just use 2.4? If possible, you should build modules for all supported versions, see “pyversions -s” output. That works fine in most cases AFAICT. > Any recomendations is welcome :) Double-checking what the Architecture field is for should be #1 on your priorities list. ;) Cheers, -- Cyril Brulebois
pgp68rSx9LNEk.pgp
Description: PGP signature
