Le Dimanche 13 Novembre 2005 15:40, Ming Hua a écrit : > If you mean the backported scim 1.4.1-1 packages for sarge, I would > suggest you consider the C++ ABI issue. The package 1.4.1-1 in sid > builds binary package libscim8, which uses the GCC 4.0 new ABI. If you > backport it to sarge, the right thing to do is to build a library > package of different name, and have it conflict with libscim8. If you > don't take care of the C++ ABI issue, I think there may be many strange > and hard-to-dectect error happening when users mix scim packages built > in different environments.
According to the instructions from www.backports.org, I have changed the name of the source directory from scim-1.4.1-1 to scim-1.4.1-backports.org.1 After the construction of the package, I obtain libscim8_1.4.1-backports.org.1_i386.deb Is it that you recommended ? I can't see any libscim8 in sarge so I don't see how I can make a conflict. I am a beginner in making debian packages so I apologise for disturbing you. > But as www.backports.org is not an official part of Debian, it's up to > you and the admins for www.backports.org. As long as you change the > package version to some distinguishable unofficial version, and specify > your change in debian/changelog, I don't mind your uploading or > distributing them at all. > > > By the way, I need to have a gpg key in the official Debian keyring > > in order to have my backport uploaded, does it mean I have to apply as > > an official maintainer or I just need to have a kind debian member to > > sign it ? I couldn't find a clear answer in the documentation, can > > you bring some lights please ? > > As I don't upload to www.backports.org at all, I have no idea. You'll > have to ask the admins there. > > Ming > 2005.11.13 I will ask them. Thanks you. Sebastien Marbrier.
