Title
Why do software packages conflict?
Abstract
Determining whether two or more packages cannot be installed together is an important issue in the quality assurance process of package-based distributions. Unfortunately, the sheer number of different configurations to test makes this task particularly challenging, and hundreds of such incompatibilities go undetected by the normal testing and distribution process until they are later reported by a user as bugs that we call "conflict defects". We performed an extensive case study of conflict defects extracted from the bug tracking systems of Debian and Red Hat. According to our results, conflict defects can be grouped into five main categories. We show that with more detailed package meta-data, about 30 % of all conflict defects could be prevented relatively easily, while another 30 % could be found by targeted testing of packages that share common resources or characteristics. These results allow us to make precise suggestions on how to prevent and detect conflict defects in the future.
Year
DOI
Venue
2012
10.1109/MSR.2012.6224274
MSR
Keywords
Field
DocType
distributed processing,localization,computer bugs,software quality,android,l10n,tracking system,translation,quality assurance,i18n,databases,testing
Data mining,Android (operating system),Software engineering,Computer science,Tracking system,Software,Language localisation,Software quality,Program testing,Database,Mining software repositories,Quality assurance
Conference
ISBN
Citations 
PageRank 
978-1-4673-1761-0
13
0.61
References 
Authors
11
5
Name
Order
Citations
PageRank
Cyrille Artho158844.46
Kuniyasu Suzaki212713.85
Roberto Di Cosmo349646.59
Ralf Treinen445734.08
Stefano Zacchiroli542637.60