There was a typo in my previous mail. On Sat, Aug 29, 2015 at 12:43 AM, Akshita Jha <[email protected]> wrote: > > Hi, > > On Wed, Aug 26, 2015 at 4:48 PM, Andreas Tille <[email protected]> wrote: > > > > > Another > > > option could be to ignore the duplicated package (implying the package > > > which comes second) and keep inserting other packages in the table. But, > > > the problem here can be that the first package we get (the package which is > > > inserted), is older than the one that is ignored. What do you think is a > > > better implementation ? > > > > The latter is better since it only affects one package and not the whole > > set of packages in the queue. We could even try to find out which > > instance of the duplicate is the newer one since we usually have a > > version number attached. I'd take the later version number and throw a > > warning into the importer log. > > > > I've sent a patch implementing this. If there is a duplicate patch, the package which has the latest chlog_date is inserted in UDD. I am assuming this is the latest package. Please test and confirm. >
*duplicate package Regards, Akshita
