Thanks Patrick. This isn't really considered out-of-date by our standards, since packages aren't typically updated starting from a couple months BEFORE the new version of Ubuntu is released (ie Hardy packages were updated to the most recent version roughly 6 months ago, so if THEY themselves hadn't been updated for a few months, a 10 month old package is not hard to imagine). This is to keep everything stable, as the packages released in Ubuntu have been tested for months before the release so we know they work. If we just upgrade to a new version, no one has tested it, and it could break functionality for the entire userbase, which isn't acceptable. I would suggest reading https://help.ubuntu.com/community/UbuntuBackports, I think it will explain things well.
Basically, there are two options, not mutually exclusive: 1) There are bugs that a new version fixed. If the new version is bugfix only, we can upgrade to it. Otherwise, we can just patch our version based on the changes for the specific bugs that affect Ubuntu. 2) The new version can be put in backports. So, is there a specific bug affecting you in pvpgn that you would like fixed? If so, then you want to make a bug report about it, and if it is fixed in a later version, we will take the patch and apply it to our current version. Also if you think the new version should be put in backports, then that approach can be considered as well. I hope this explains some things! -- package out of date https://bugs.launchpad.net/bugs/253336 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
