Ubuntu
incron package

How do I file an update request in a repository?

Asked by Christian-Philipp Worring

There is a bug in incron 0.5.9-5 which is in the Precise Universe-Repositories (see http://bts.aiken.cz/view.php?id=691). In incron 0.5.10-1 (in the Repositories of Raring, Saucy and Trusty) this bug is fixed.

Now I'd like to request an update in Precise Universe - how do I do that? Do I file a bug report for incron or is there any other specific way?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu incron Edit question
Assignee:
No assignee Edit question
Solved by:
Warren Hill
Solved:
Last query:
Last reply:
Revision history for this message
Warren Hill (warren-hill) said : 		#1

If the bug is already fixed in a newer version then you want a Backport.

Details on finding out if its already been backported and how to request one if it hasn't can be found here:

https://help.ubuntu.com/community/UbuntuBackports

Revision history for this message
Christian-Philipp Worring (worring) said : 		#2

Thanks for the answer, but I don't get why this would be a backport. Wouldn't that go to precise-updates, as it has no new functionality whatsoever and just fixes a bug?

Revision history for this message
Best Warren Hill (warren-hill) said : 		#3

If the bug had not been fixed then the correct way would be to file a bug report. You can still do that including a note that it has been fixed in a later release.

However, the Ubuntu developers tend to update packages as little as possible saving all but security fixes and problems that affect a lot of users until the next official release. The reason for this is that Ubuntu is a complex set of programs and nobody wants to take the risk of breaking lots of peoples systems. Once a fix is found for a problem and its ready for the next release the Bug squad will often consider it to be job Done.

Requesting a backport does at least make it clear that its needed now in an earlier release and its a different group of people that deal with it.

Part of the problem is that we don't have enough developers and since its a free open source project many (though not all) of us are doing it in our own free time and for no money so I don't expect this to change soon; if ever.

Making it clear that its already fixed in the latest version may convince the backport team that its safe to update and get it included.

Revision history for this message
Christian-Philipp Worring (worring) said : 		#4

Thanks Warren Hill, that solved my question.