Upload rejected with "unsupported operand type(s) for -: 'datetime.datetime' and 'NoneType'"

today, the exact same 3 uploads failed (i mean, same src package name, same dist, but newer version).
No other src package in my numerous PPA uploads seem to be affected.

So in ~ubuntu-mozilla-daily/ppa, xulrunner-1.9.2/{jaunty,hardy} and firefox/karmic are repeatedly failing.
I'm not sure why those 3 are different though, they are supposed to be exactly the same as the others.

I'm also affected by this bug.

Here's some more information:

I have a debian source package (ladish-git) and I've uploaded it to 2 different PPAs.
1 - https://launchpad.net/~ladi-team/+archive/ppa
2 - https://launchpad.net/~falk-t-j/+archive/lucid-latest

It fails to upload on the 2nd PPA, but fine on the first one
(link to package on 1st PPA - https://launchpad.net/~ladi-team/+archive/ppa/+sourcepub/1167978/+listing-archive-extra)

I tried to go the the 1st PPA then copy it to the 2nd one (using Lucid version, rebuild sources)
That gives me this error:
" Sorry, something just went wrong in Launchpad.
We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.
(Error ID: OOPS-1621L614) "
which links to - https://lp-oops.canonical.com/oops.py/?oopsid=1621L614

Hope this is helpful

Thanks falkTX - the oops is very helpful, as it's the same issue, but with a stack-trace :)

Based on the oops, it seems we have some completed builds (BuildStatus.FULLYBUILT), who's date_started is not set. Checking the destination PPA, here is the culprit:

https://launchpad.net/~falk-t-j/+archive/lucid-latest/+build/1768191

Note that that build was built on the same day as its amd64 counterpart:
https://launchpad.net/~falk-t-j/+archive/lucid-latest/+build/1768190

which has both date_started and date_finished.

oh, this means the package was actually accepted, it's just the mail that was misleading...

anyway, thanks for working on this

OK, after racking my brains with wgrant, I found that all the examples of successful builds without timestamps that we know of, finished around: 20100602-1154

For example:
https://launchpad.net/~falk-t-j/+archive/lucid-latest/+build/1768191
https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+build/1768594
https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+build/1768591
https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+build/1768601

which indicates that when the rollout started, perhaps data was not properly replicated.

But anyway, it means we can fix this error message itself trivially :)

Running some queries on staging show that as expected, there are 9 builds that completed since 2010-06-01 where date_started is None.

Fix committed with r10981 devel.

Fixed in stable r10981 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/10981>

QA'd on dogfood by

1. updating to db-devel r9444
2. Applying a patch to reverse the fix: http://pastebin.ubuntu.com/448192/
3. Manually remove the date_started of i386 build of hello 2.4-4ppa1: https://dogfood.launchpad.net/~michael.nelson/+archive/pocketsphinx/+build/1693756
4. Uploading 2.4-4ppa2
5. ppa-run.sh and watch process upload fail with the expected error: http://pastebin.ubuntu.com/448190/

Then,

1. Revert patch to pristine 9444
2. Upload 2.4-4ppa2 again.
3. ppa-run.sh and watch process upload continue as expected: http://pastebin.ubuntu.com/448194/

I still get the error:
"Rejected:
unsupported operand type(s) for -: 'datetime.datetime' and 'NoneType'"

As before, the same package compiles fine in 1 PPA, but not in the other.

Successful build:
https://launchpad.net/~ladi-team/+archive/ppa/+sourcepub/1172311/+listing-archive-extra

No build:
https://launchpad.net/~falk-t-j/+archive/lucid-latest

Hi falkTX,

Yes, the fix has not landed in production, so you will continue to see the error for uploads for the specific package until the next release (unless it's cherry-picked), or we manually fix the missing date_started (which we should do, given the circumstances).

However, if you use the edge system to copy the package as you mentioned at:

https://bugs.launchpad.net/soyuz/+bug/589068/comments/2

it should copy now without oopsing, but *only* if all your requests are via the edge system:

https://edge.launchpad.net/~ladi-team/+archive/ppa

Thanks!
It works!

It's not perfect, but it's a nice workaround.

I can now say that the bug seems fixed.

Recent upload has been successful:
https://launchpad.net/~falk-t-j/+archive/lucid-latest/+sourcepub/1180109/+listing-archive-extra

(this is the PPA that had problems)

not fixed for me. the exact same 3 src packages have been rejected today.
I guess the fix didn't land in production yet. did it?

The fix is not in production until the status changes to "Fix Released". This should be in about a week.

On Wed, Jun 23, 2010 at 9:26 AM, Fabien Tassin <email address hidden> wrote:
> not fixed for me. the exact same 3 src packages have been rejected today.
> I guess the fix didn't land in production yet. did it?

No, it'll be in the 10.06 rollout. I haven't looked into why falkTX
can now upload his package, but it's not related to this fix.

changing this to fixed too

yep, confirmed fixed. Thanks!