During uploading the autobuilder should check the package version. Package should only be upgradable if an package with
the same version has been uploaded but did not build successfully or if the package has an higher version than any existing
package version in the same repository.

I was able to upload packages witht he version number 0.1-<date>-1 while the same package with version 0.6-<earlier
date>-1 was already uploaded and did build (and was even promoted). This should not be possible.

Date: 2009-01-17 14:31
Sender: Ed Bartosh

Fixed couple of months ago.

Date: 2008-08-04 19:36
Sender: Tim Teulings

That sounds OK. Go for it!

Date: 2008-08-04 17:42
Sender: Ed Bartosh

I almost agree with what you're saying. Will implement it this
way:
 - autobuilder will build packages in any case, without restrictions
 - before uploading to repository versions will be checked. Packages
with versions <= those, which already present in repository
will not be uploaded there.
 - email with explanations will be sent to uploader

Is this OK from your point of view? 

Date: 2008-08-03 19:41
Sender: Tim Teulings

I created the ticket because I uploaded newer packages with an
old version (broken script) by accident. This was not intended
and I was very suprised that it did work and packages were build.

So why should it not? Two reasons:
IMHO the mayor goal is to build to test (first) or publish (tested
packages). If packages with an older versions than the current
will never be automatically installed, so why should I buil one?
For what reason? IMHO it can only be a mistake.

The otehr reason is that one uses package versions to define
a process, create the possibility to test and improve packages
and make things reproducable and differentiatable.

On special case "the bug" is, that I can repeately
can upload sources again and again keeping the *same* package
version. Depending of the time of install diffierent people can
get different behaving versions that all have the same build
version. That will create a lot of problems and definitely does
not have any good reason to allow (of cause I can repeately upload
package sources with the same version if they do not build).
Packages have a similar contect and process model as sourcve
control tools like subversion and similar. You would never allow
to check in different source code with the same version number.

IMHO one has to argue why this should be a feature instead I
have to argue why we should remove this feature. And changing
in a neccessary step to improve so change is not an argument
against somthing per se.

Of course this is only a suggestion, you are chef, you decide :-)

Date: 2008-07-29 09:08
Sender: Ed Bartosh

So, what's the harm in building packages with version less than
in repository if they will never be installed and why we should
introduce this restriction to the autobuilder?

Date: 2008-07-29 09:01
Sender: Tim Teulings

Yes, If the package version is less the package version already
in the repository, this package can be build but would never
be installed, ebcause the application manager on the device will
(or at least should not) never show it.

To summerize: These packages can be build but will never be installed
by device (automatically). New packages with changes must always
have a higher version number than the last packages. Else funny
things can happen...

Date: 2008-07-28 20:04
Sender: Ed Bartosh

Can you explain why this restriction is needed?
Current implementation allows user to build any package. I think
people will be confused if we change this without explanation.