Are you a maintainer of the package or an actual code contributor for the project? Raising the license seems silly if you're not a core dev or significant contributor. *GPL3 were driven by politics and contain language not well tested in court (particularly, the completely ineffective patent language); so a third-party relicense of someone else's code would seem political and ill-conceived. <blockquote type="cite">On Aug 7, 2010 8:24 AM, "Francesco Fumanti" <<a href="mailto:francesco.fumanti@gmx.net">francesco.fumanti@gmx.net</a>> wrote: Hi, I was indeed aware that by raising the license of files that did not change, there would later be two different license versions for a same file; that was also what made me wonder whether it is allowed to raise it. As the LGPL 2 license included the "or later" and the copyright holder agrees with the change, I am going to also raise the license of the files that did not change. Many thanks for your help, Francesco. On 08/07/2010 01:15 PM, Siegfried-Angel Gevatter Pujals wrote: > 2010/8/7 Francesco Fumanti<france...Ubuntu-devel-discuss mailing list <a href="mailto:Ubuntu-devel-discuss@lists.ubuntu.com">Ubuntu-devel-discuss@lists.ubuntu.com</a> Modify settings or unsubscri...</blockquote>