/srv/irclogs.ubuntu.com/2012/10/24/#launchpad.txt

CrypticfortuneHi. Can anyone help me figure out what's going on with this package and its "Failed to upload" errors? https://launchpad.net/~cryptickrisp/+archive/samscope/+packages05:52
Crypticfortunethe upload logs say it has files with dates too far in the future (I suspect because I'm in Japan, and local time wise, I'm maybe a day-ish in the future...)05:53
Crypticfortunebut only one of the builds failed that way...05:53
wgrantCrypticfortune: The timestamps in that tarball are a bit odd05:58
wgrantThe one you uploaded, that is05:59
wgrantAll the files are dated about 7 hours in the future05:59
wgrantI suspect your clock is wrong05:59
Crypticfortunewgrant: that seems unlikely because it'd definitely 3pm here....06:03
wgrantCrypticfortune: Perhaps your timezone is incorrect06:03
wgrantWhat does 'date' say?06:03
CrypticfortuneWed Oct 24 15:04:02 JST 201206:04
wgrantIntriguing.06:04
wgrantHow did you construct the tarball?06:04
wgrantWhat do the file timestamps in the source directory look like locally?06:04
wgrantI know there's no general problem with timezones, since I've been building packages from +10/+11 for quite a number of years now :)06:05
Crypticfortunewgrant: "dpkg-buildpackage -S"06:05
Crypticfortunewgrant: yeah, all the previous packages worked fine, and you'll notice that for some reason the build on "preceise" worked (with the same tarball) =/06:06
wgrantIt's not the same tarball06:06
wgrantYou're using a native package (possibly accidentally), so it's always a different tarball06:06
Crypticfortunetrue, well it should be identical except for the -{series}~1 bits in debian/changelog06:08
wgrantHuh06:08
wgrantThe precise timestamps are in the future too06:08
wgrantIt should have been rejected, unless it's just over the threshold now06:08
wgrantAnyway, your system is creating tarballs with incorrect timestamps, so you should probably track that down06:08
wgrantThe threshold is 8 hours06:09
wgrantThat's probably why the precise build worked06:09
wgrantIt just happened to build late enough06:10
lifelessCrypticfortune: what does 'TZ=gmt date' output for you ?06:10
StevenKITYM date -u06:10
lifelessStevenK: blah06:10
wgrantHm, indeed, perhaps there's another definition of JST06:10
Crypticfortunelifeless StevenK : Wed Oct 24 06:10:43 UTC 201206:11
wgrantEvidently not06:11
StevenKClose enough06:11
lifelessCrypticfortune: thanks06:11
Crypticfortunewgrant: but whoah! before doing "dpkg-buildpackage" I check out a fresh copy of the source tree, and for some reason the files there are indeed in the future....06:11
Crypticfortunesomething weird's goin on...06:11
StevenKsteven@undermined:~% TZ=Japan date06:11
StevenKWed Oct 24 15:11:44 JST 201206:11
wgrantCrypticfortune: Hah06:12
StevenKLooks right to me06:12
wgrantCrypticfortune: That could do it06:12
lifelesswhat VCS ?06:12
wgrantCrypticfortune: How'd you check it out?06:12
Crypticfortunewgrant: hg clone.... dunno how that's screwing up, but  I know where to start looking now. thanks!06:13
wgrantPerhaps it sets the mtime to the last commit, and the last commit has a bad clock, or something like that06:13
Crypticfortunethat would be disturbing....06:13
lifelesslots of things about hg are disturbing :)06:13
wgrantLast committer, that is06:13
wgrant+++ b/.hgtagsWed Oct 24 12:50:24 2012 +090006:14
wgrantLooks fine :/06:14
CrypticfortuneAhahaha, found the problem. So for packaging, I was cloning into an NFS directory, and that NFS server's NTP is dead for some reason, and the clock is (almost) 7 hours in the future...must have been broken for a looong time... =/06:22
wgrantCrypticfortune: Ouch06:23
wgrantThat would do it, though!06:23
=== jtv1 is now known as jtv
aboudreaultlooks like the copy packages is broken?11:34
wgrantaboudreault: No, why?11:36
wgrantIt can take a couple of minutes for a copy to complete11:36
wgrantBut it's not broken11:36
aboudreaultwell, tried to copy a packages yesterday, it didn't work..... just retry, same error11:36
wgrantWhat's the error?11:36
aboudreaultLaunchpad encountered an internal error during the following operation: copying a package.  It was logged with id OOPS-02eefd0ef2b9e47058302b1c275a5504.  Sorry for the inconvenience.11:37
ubot5https://oops.canonical.com/?oopsid=OOPS-02eefd0ef2b9e47058302b1c275a550411:37
wgrantHm, that should have given you a more descriptive error message11:37
wgrantcjwatson: ^^11:37
wgrantaboudreault: CannotCopy: geos 3.3.3-2~precise2 in precise (same version already has published binaries in the destination archive)11:37
cjwatsonYeah, it should have done - please file a bug11:39
cjwatsonRather surprised it didn't, since I thought I'd QAed that specific case11:39
cjwatsonBut it was a while back11:40
aboudreaultwgrant, I see. thanks11:40
cjwatsonAnyway, yeah, you can't copy that because it already exists - or used to exist - in the destination11:40
cjwatsonBut please do file a bug and I'll see about fixing up the e-mail11:41
aboudreaultcjwatson, ok11:43
aboudreaultcjwatson, , where should I fill that bug?11:47
cjwatsonhttps://bugs.launchpad.net/launchpad/+filebug11:47
aboudreaultjust tried to copy another package, which is not in packages.ubuntu.com.... and got the same error11:48
aboudreaultCopied from: ubuntugis-unstable. Copied by: Alan Boudreault Target series: Quantal11:49
aboudreaultgdal 1.9.1-2~precise4 in precise (same version already has published binaries in the destination archive)11:49
aboudreaultthere is only 2 python packages in quantal in the ppa11:50
maxbaboudreault: The "has published binaries" check does not care about series11:50
maxbWhich is the destinatination archive?11:50
maxber, apparently I fail at typing. You get the idea, though11:51
aboudreaultso the copy/rebuild still doesn't work in the same PPA?11:52
aboudreaultanyway, will upload manually11:54
wgrantIt can't really just work, as we'd have to mangle the version in potentially evil ways11:55
cjwatsonaboudreault: the on-disk representation of a PPA has a single pool/ for all series, so you can never reuse versions in a single PPA (regardless of precise/quantal/etc.) because the filenames would clash12:03
cjwatsonaboudreault: version numbers are cheap, so just use a new one12:04
aboudreaultyeah12:04
=== dpm__ is now known as dpm
=== yofel_ is now known as yofel
=== dpm is now known as dpm-afk
=== Ursinha-afk is now known as Ursinha
=== glebihan_ is now known as glebihan
kanor_hello21:31
kanor_it is possible upload a meta package in a ppa ?21:31
cjwatsonkanor_: Sure.  Metapackages are just packages whose purpose is only to depend on other packages; there's nothing particularly special about them.21:33
kanor_i create my package with equivs-build21:36
kanor_easy21:37
kanor_but in the command21:37
kanor_dput ppa:your-lp-id/ppa <source.changes>21:37
kanor_i get how "source.change"21:38
kanor_(and excuse me for the bad english )21:40
sinzuiStevenK, wgrant https://bugs.launchpad.net/launchpad/+bug/35101122:27
ubot5Ubuntu bug 351011 in Launchpad itself "rosetta-pofile-stats.py needs optimizing" [Critical,Triaged]22:27
joeysinzui: I found some more timeouts for you. Just FYI, they don't impact me but I can repeat them23:20
joeysinzui: OOPS-eb5ac431223bfa1934d392bc09bdc9c923:20
ubot5https://oops.canonical.com/?oopsid=OOPS-eb5ac431223bfa1934d392bc09bdc9c923:20
joeysinzui:  OOPS-449e45477aef722fb6c8e6a507bb99f323:20
ubot5https://oops.canonical.com/?oopsid=OOPS-449e45477aef722fb6c8e6a507bb99f323:20
joeysinzui: from https://launchpad.net/ubuntu/gutsy23:20
TheLordOfTimetimeouts confirmed: OOPS-2664a79beb13cc06adeec95b1359669023:35
ubot5https://oops.canonical.com/?oopsid=OOPS-2664a79beb13cc06adeec95b1359669023:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!