Thanks Stephane, It was a subtle problem, which I was aware of before I uploaded the package.
Originally the package was called libcommoncpp2-1.0-0c102, but the soname changed (which I didn't notice) and uploaded libcomoncpp2-1.0-0c102 (1.3.10-1). Since the soname had changed I needed to rename, which is where libcommoncpp2-1.3 (1.3.10-2) came from. I uploaded this next version quicky, but didn't include a conflicts for the rare case that someone (like yourself) did download the 1.3.10-1 version of the package for the couple of days it was in the archive. Anyway I have now uploaded a new version which does have the conflicts statement and should ;-) work correctly for everyone. Thanks for your reports. Mark On Wednesday 01 June 2005 22:06, Stephane List wrote: > With : apt-get remove libcommoncpp2-1.0-0c102 > > I don't have the problem anymore. > I don't know where this version of the package comes from ??? > > For me, you can close the bug if I was the only one having the problem > on the planet. > > Regards > Stephane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
