Suggestion: widelands-daily should not only include bzr revision, but also date/time in the package name
Bug #1204462 reported by
Jens Beyer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
widelands |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Everytime one triggers a build outside the daily auto-build routine of widelands-daily, we get upload errors (in many mails).
I think we can get rid of that by specifying the date/time of the build in the version of the package. This can be done by altering the recipe.
I just don't know and want to ask if that's a good thing (TM) or not... so basically, ask for opinions.
(a more theoretical, but possible problem may be that a build may run fine, but the version is useless due to a bug - people using the PPA will need to wait until the auto-build runs again - this suggestion can solve this problem)
tags: | added: ppa |
Changed in widelands: | |
status: | In Progress → Fix Committed |
assignee: | Jens Beyer (Qcumber-some) (qcumber-some) → nobody |
To post a comment you must log in.
Sounds reasonable to me. Actually, a time stamp might better convey how old/new the package is rather than revision numbers which you either need to pay close attention to or look up to know.
By adding more stuff, it gets awfully long and complex though, so I have another suggestion. The "+trunk+" part in "1:17-ppa0- bzr6663+ trunk+~ lucid1" seems like clutter to me. I think we could drop that part, without sacrificing anything. Also, it might be slightly misleading now that we are merging translations instead of building a pristine trunk. Thus, we would end up something like: bzr6663- 201307241337~ lucid1
1:17-ppa0-
PS. How often do we request builds manually, it thought we for the most part just let the automatic builds run?