[00:05] <asac> let me ceck
[00:06] <asac> yes
[00:06] <asac> i often do it that way too
[00:06] <asac> sometimes not if i am the only one
[00:06] <asac> but its more beautiful ;)
[00:07] <micahg> asac: pushed xul again
[00:07] <micahg> working on ff3.5
[00:09] <bdrung> asac: m-d 0.19 with dh 7 makefile: http://paste.debian.net/55730/
[00:09] <bdrung> asac: do you like it?
[00:10] <asac> yes ;)
[00:10] <micahg> asac: pushed ff3.5 as well
[00:10] <bdrung> asac: the best: it works already :)
[00:10] <asac> cool. lets hope it doesnt cause regressions ;)
[00:11] <asac> to earn credits we should do an extension respin ;)
[00:11] <micahg> ooops
[00:11] <micahg> forgot to check for targetted bugs
[00:11] <asac> hehe
[00:11] <asac> see what i mean ;)
[00:11] <asac> micahg: include them in firefox only then
[00:11] <micahg> asac: now I see why this is so complicated :)
[00:11] <micahg> asac: nothing for 3.5.7
[00:11] <micahg> so we're good
[00:11] <micahg> 3.5.8 has some
[00:12] <asac> good.
[00:12] <asac> so just prep release and then wait ;) ... i am currently doing the tarballs. that will take a bit ;)
[00:14] <micahg> k, I need to get back to what I was working on
[00:15] <micahg> asac: so you normally merge the rev's from head for the update into the older releases?
[00:15] <asac> no
[00:15] <asac> the stable release branches are stable
[00:15] <asac> they are independent
[00:16] <asac> however, if i find that i need a patch updated
[00:16] <asac> i cherry pick that change down usually
[00:16] <asac> because of lazyness
[00:16] <asac> (to all branches that all have that patch)
[00:16] <asac> so i start on .karmic branch ... if there are patch adjustments needed i do that by copying those from .head manually
[00:16] <asac> then on jaunty intrepid hardy branches i bzr merge -c REVNO lp:....karmic
[00:16] <asac> them
[00:17] <bdrung> asac: updated http://wiki.debian.org/mozilla-devscripts
[00:18] <asac> why do you use $(null) ... we use $(NULL) everywhere ;)
[00:19] <bdrung> asac: where do we use $(NULL)?
[00:19] <micahg> ah, so you merge in the stable branches
[00:19] <micahg> I see
[00:20] <asac> in all mozilla packages
[00:20] <asac> micahg: only if i need to merge something
[00:20] <asac> but only using -c (e.g. one commit cherry picks)
[00:20] <asac> and only for patches
[00:20] <asac> or for something critical needed everywhere in a stable update
[00:21] <micahg> k, BTW there was a patch dropped for 3.5
[00:21] <micahg> 1.9.1.7
[00:21] <bdrung> asac: in xpi.mk is no $(NULL) - so i can't know it ;)
[00:21] <bdrung> asac: correct it if you want
[00:22] <asac> hmm need to login ;)
[00:22] <asac> no idea what credentials i had
[00:22] <asac> or if i had any at all ever
[00:23] <asac> super. it doesnt tell me if a mail was sent ;)
[00:23] <asac> for recovering pass
[00:23] <asac> hmm. when creating an account there are two buttons:
[00:23] <asac> "Create Profile" ... "Create Profile + Email"
[00:23] <asac> hell
[00:23] <asac> usability ftw
[00:24]  * asac hits the first button ... hoping for the best
[00:25] <asac> done
[00:31] <bdrung> asac: can "rdf_graph.parse" work directly on text (and not filenames)?
[00:33] <asac> i am a drive-by contributor ... i dont know nothing about rdflib api and work by using APIDOC for every step :)
[00:36] <and`> asac: some ppl is complaining for the rfkill thing not working anymore, any news that side?
[00:42] <asac> and`: depends on hardware etc.
[00:43] <asac> most dell stuff should be fixed
[00:43] <asac> but afaik there are still issues
[00:44] <asac> ok off
[00:44] <asac> ttyt
[00:44] <asac> bdrung: i will see if i can find something for buffer tomorrow
[00:44] <bdrung> asac: thanks
[00:45] <bdrung> asac: then i could check the install.rdf before extracting everything
[00:48] <micahg> asac: do you need me to do anything more later tonight?
[00:51] <asac> bdrung: use a StringInputSource
[00:51] <micahg> asac: release was an hour ago
[00:51] <asac> http://www.rdflib.net/rdflib-2.4.0/html/private/_xmlplus.sax.xmlreader.InputSource-class.html
[00:52] <asac> bdrung: ^^
[00:52] <asac> subclass of that
[00:52] <asac> and then you can use that in the parse argument from what i understand
[00:52] <bdrung> ok
[00:53] <asac> parse(self, source, publicID, format, **args)
[00:53] <asac> so for source
[00:53] <asac> not sure what we have now
[00:53] <bdrung> asac: we have "rdf_graph.parse(install_rdf)" no
[00:53] <bdrung> w
[00:54] <asac> yeah. apidoc is messy
[00:55] <asac> maybe it type checks for a string and implicitly makes a URLINputSource out of it
[00:55] <asac> so try the StringInputSource approach
[00:55] <asac> you need to pass a publicID most likely because buffers have no pubID ;)
[01:02] <bdrung> :)
[01:03] <bdrung> will test it tomorrow
[01:03] <bdrung> it's now bed time
[01:04] <micahg> asac: you need me to do anything when I get home?
[01:05] <asac> micahg: prepare all the stable branches ;)?
[01:05] <asac> hehe
[01:05] <asac> well. basically its just the changelog entry. and then trying if all patches apply
[01:05] <asac> oh and the patch drop
[01:05] <asac> if you dont want to do that
[01:05] <micahg> asac: if you want me too
[01:05] <micahg> I can try
[01:06] <micahg> asac: what about the m-dev change in ff35.head?
[01:06] <micahg> and dh_xul
[01:06] <asac> micahg: i would expect each branch to be three commits ... first commit is new changelog with UNRELEASED and the USN-.. stuff ... second commit is the patch droppage (like i usually document)
[01:07] <asac> micahg: changing packaging in any way is off for stability/security updates
[01:07] <asac> so no
[01:07] <asac> just bumping changelog ... doing the minimal changes needed (like dropping patches dropped upstream, rebasing patches) ... and then releasing
[01:07] <micahg> asac: so how can we call it the same version?
[01:07] <asac> if you look at the .jaunty or .intrepid branches you will see that its always really simple
[01:08] <asac> micahg: if you checkout the branches you will see how the versioning is done
[01:08] <micahg> asac: yes, I know
[01:08] <asac> basically same upstream version, but with 0ubuntu0.9.10.1
[01:08] <asac> for first upload to 9.10
[01:08] <asac> while head is ubuntu1
[01:08] <micahg> yes, but how can the lucid and karmic version be essentially the same (think same contents) but have different contents?
[01:08] <asac> micahg: the man page is buggy. it must say: "available since 1.9.1.7 in lenny"
[01:08] <asac> or lucid
[01:09] <asac> debian probably wont push that to security either ;)
[01:09] <asac> micahg: we have two parts for packages: a) upstream ... b) packaging
[01:09] <asac> upstream gets bumped to new upstream
[01:09] <asac> while packaging gets forked when released
[01:09] <asac> all new stuff we do will not be done on the stable branches
[01:10] <asac> like dh_... here is a good example of what doesnt happen in stable branches
[01:10] <micahg> asac: is it mozilla team specific that 1.9.1.7-0ubuntu1 and 1.9.1.7-0ubuntu0.09.10.1 aren't the same?
[01:10] <asac> similarly we wouldnt rename or move around files
[01:10] <asac> etc.
[01:10] <asac> while we might do that in lucid
[01:11] <asac> micahg: we are kid of unique because we bump upstream
[01:11] <asac> usually upstream is never bumped in stable releases
[01:11] <asac> only backported patches added
[01:11] <micahg> k, that's what I was wondering because I never saw this before in other packages
[01:11] <asac> but mozilla needs full new upstream
[01:11] <asac> so we are a bit special, yes.
[01:11] <micahg> asac: what about the slovak translation thing we said we'd do for karmic
[01:11] <asac> otherwise you would have to add up to 300 patches or something ;)
[01:11] <asac> (happened in the past)
[01:11] <asac> well... maybe too much. but i definitly saw 200+ bug fixes in security updates
[01:12] <asac> when we still had the long security cycle
[01:12] <asac> micahg: what did we say?
[01:12] <micahg> asac: nothing officially :)
[01:13] <micahg> originally targetted to karmic-updates but released to lucid
[01:13] <asac> hmm. not sure ;)
[01:13] <asac> in doubt drop it
[01:13] <asac> and wait for someone complaining ;)
[01:13] <micahg> k, well, there's always 3.6 :)
[01:14] <asac> or lucid ;)
[01:14] <asac> so .desktop file translations probably can be added. but we shouldnt do that while preparing the release ;)
[01:14] <micahg> asac: so, I'll try to do the stable 1.9.1 and 3.5 branches
[01:14] <asac> rather directly
[01:14] <micahg> a little later
[01:14] <asac> if i didnt commit it to other branches, i would say i didnt want it there for now
[01:15] <asac> yes. that would be great
[01:15] <asac> i will upload the lucid bits to the -security PPA now :)
[01:15] <asac> for 1.9.1 and 3.5
[01:16]  * asac checks builders status
[01:16] <asac> micahg: oh. did we drop the patch because it was applied upstream?
[01:16] <micahg> asac: yep
[01:16] <asac> or because i was annoyed by it?
[01:16] <asac> ok
[01:16] <asac> then we need to drop it
[01:16] <asac> or you dropped it ... just thought that only me would drop patches for being annoyed ;)
[01:17] <asac> but it hink that was on 1.9.2 and 1.9.3
[01:17] <micahg>  Drop patch after upstream landing of (bmo: 521780)  :)
[01:19] <asac> micahg: oh. ffox 3.5 and xul 1.9.1 get the _same_ USN
[01:19] <asac> in case you didnt do that on 3.5
[01:19]  * asac should check
[01:19] <micahg> asac: I did
[01:19] <asac> the other USN is for 3.0 and 1.9
[01:19] <asac> because they have a different set of security issues usually
[01:19] <micahg> asac: so technically 1 bug should have been targeted, but it was fix released already with our patch
[01:20] <asac> ok pushing to http://launchpad.net/~ubuntu-mozilla-security/+archive/ppa
[01:20] <asac> micahg: yes. thats ok. we dont need to mention as "dropping because of upstream fix" already implies that
[01:20] <asac> maybe we should explicitly rename the bug number in such a comment
[01:21] <asac> but well ;)
[01:21] <asac> thinks must be imperfect
[01:22] <asac> hmm. somehow feel the urge to also do a 3.0/1.9 upload now
[01:22] <asac> to get these orig beasts up ;)
[02:28] <asac> ffox orig also up
[02:28] <asac> in sec
[03:37] <ripps> fta: okay, the change actually builds the source packages now, but the .changes files are still have the epoch in the name and for some reason, dput wouldn't upload them at the end.
[03:38] <ripps> okay, it seems the dput upload at the end was expecting an epoch, but the actual .changes in /ppa didn't have an epoch
[05:00] <asac> micahg: already started?
[05:00] <asac> on xul?
[05:00] <micahg> no, trying to fix a bug in something else
[05:00] <asac> ok
[05:01] <asac> so i will do karmic now
[05:01] <micahg> asac: I started building 1.9.2~rc1 :)
[05:01] <asac> for xulrunner
[05:01] <micahg> right cause those take a while
[05:01] <asac> just noticed that we only have 1 hppa builder
[05:01] <micahg> I can do jaunty right now then
[05:01] <asac> so better get the big stuff up ;)
[05:01] <asac> ok cool
[05:02]  * micahg is still at work
[05:02] <micahg> and you're either up early or late :)
[05:04] <asac> early and late
[05:05] <asac> wanted to finish xul 1.9
[05:05] <asac> then bandwidth broken and so on :)
[05:06] <asac> micahg: last dch before release commit is dch -r -Dkarmic-security fwiw and jaunty-security etc. ;)
[05:07] <micahg> asac: we never had the patch in jaunty
[05:07] <asac> thats even better then
[05:08] <asac> so no need to do that ... just simple changelog ;)
[05:08] <asac> i usually try a bzr bd ... --builder='debuild -b' and abort after patches
[05:08] <micahg> asac: the patch would be the same name, right?
[05:08] <asac> e.g. if they applied
[05:08] <asac> micahg: most likely
[05:08] <asac> br the debuild -b and wait for patches test should reveal that
[05:08] <asac> ;)
[05:09] <asac> maybe we have something else there etc.
[05:09]  * micahg doesn't ahve the tarball
[05:10] <asac> micahg: its in ppa
[05:10] <asac> https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa/+files/xulrunner-1.9.1_1.9.1.7+nobinonly.orig.tar.gz
[05:11] <micahg> k
[05:11] <micahg> thaqnks
[05:11] <micahg> *thanks
[05:12] <asac> i am taking jaunty firefox too i guess ;)
[05:13] <micahg> you're faster than I am :)
[05:14] <asac> parallelizing ;)
[05:14] <asac> not faster
[05:14] <micahg> oh, I can do that
[05:14]  * micahg has learned how to use byobu
[05:14] <asac> also i did that a hundred times :(
[05:15] <asac> nah ;)
[05:15] <asac> i am parallelizing by working on four/five branches at the same time ;)
[05:15] <asac> and by not doing a full test build ;)
[05:15] <asac> just waiting till patches are done. thats fine
[05:15] <asac> we will see the result in the staging ppa soon enough :)
[05:18] <micahg> asac: dies after patches with autoconf
[05:19] <asac> dies?
[05:19] <asac> paste?
[05:19] <micahg> I don't have the build deps
[05:20] <asac> micahg: i run that on karmic ;)
[05:20] <micahg> asac: http://pastebin.ubuntu.com/352144/
[05:20] <asac> i do everything on karmic without chroots ;)
[05:20] <asac> micahg: its ok i guess
[05:20] <asac> just finish the commit stuff ... i cna do a quick test -b
[05:20] <asac> before uploading
[05:21] <asac> but looks weird
[05:21] <asac> did you do bzr bd?
[05:21] <micahg> yeah, but I don't have the build deps
[05:21] <asac> that should check for deps
[05:21] <micahg> I ran -d
[05:21] <asac> how did it build then?
[05:21] <asac> oh
[05:21] <asac> ok
[05:21] <micahg> :)
[05:21] <asac> yeah. go ahead then
[05:21] <asac> let me know so i can pull ;)
[05:21]  * micahg is running these jobs on a headless server
[05:22] <micahg> asac: done
[05:22]  * asac checks
[05:24] <micahg> asac: lp refreshed
[05:25] <asac> uploadewd
[05:25] <asac> everything happily spinning i hope
[05:25] <asac> at least we are still dominating builders ;) ... https://edge.launchpad.net/builders
[05:26] <asac> 50% xulrunner ... other 50% is chromium-browser :)
[05:26] <micahg> ugh, lucky for us no one else is building anything
[05:26] <asac> good ... 9.04.1 is also there
[05:26] <asac> micahg: well. thats not really true ;)
[05:26] <asac> the queues are growing
[05:26] <asac> i think our ppa gets "main" priority
[05:26] <asac> so all universe has to wait
[05:27] <micahg> asac: I think the security PPA uses the distro builders
[05:27] <asac> we use
[05:27] <asac> but look at the distro builders ;)
[05:27] <asac> Official distributions build statu
[05:27] <asac> powerpc2 306 jobs (20 hours)
[05:28] <asac> sparc2 239 jobs (26 hours)
[05:28] <asac> hehe
[05:28] <asac> but not that bad
[05:28] <asac> i think most are probably universe packages so they start with 1000 lower build score ;)
[05:30] <micahg> asac: what to do about sqlite conf test causing FTBFS on xul193 Lucid?
[05:30] <micahg> should I bump sqlite system requirement to 3.6.22 since that's what they're aiming for?
[05:31] <asac> sure
[05:32] <asac> sounds sane
[05:32] <micahg> asac: there's no official bug yet for that afaik
[05:32] <micahg> nm
[05:32] <micahg> mozilla 530667
[05:33] <asac> why would that fix it?
[05:34] <micahg> asac: should I say bump in advance of landing of bmo...
[05:34] <asac> did they patch their sqlite in-source already?
[05:34] <micahg> asac: no, but it'll use their version for right now
[05:34] <asac> or because they have higher requirements for system libs ;) :-Ü
[05:34] <micahg> we only have 3.6.21-2
[05:34] <asac> i think its ok.
[05:34] <asac> we most likely will get that
[05:34] <micahg> what about the comment?
[05:34] <asac> in lucid
[05:34] <asac> comment?
[05:35] <micahg> bump in advance of landing of
[05:35] <asac> bump sqlite for anticipated landing of 3.6.22 upstream - also workaround temporary configure bustage for system sqlite
[05:35] <asac> something like that
[05:36] <micahg> asac: in changelog or bzr or both?
[05:37] <asac> i dont think we have anything in changelog for .3?
[05:37] <asac> then just bzr
[05:37] <micahg> yep, we have a changelog :)
[05:38] <micahg> asac: Bump system sqlite to 3.6.22 for anticipated upstream Mozilla landing
[05:38] <micahg>     Also temporarily workaround broken configure test due to (bmo: 445164)
[05:39] <asac> sure
[05:40] <micahg> asac: also, what to do if do people bump something like sqlite, do we keep both changelog entries?
[05:40] <micahg> *two people
[05:40] <asac> we replace the previous entry if its in the same UNRELEASED cycle
[05:40] <micahg> ok
[05:41] <asac> but we can check when that happens
[05:41] <micahg> I removed the old entry
[05:41] <micahg> debcommit is a lot easier than trying to edit the bzr commit
[05:42] <micahg> k, xul193 should build on lucid tomorrow night
[05:43] <asac> cool.
[05:43] <asac> ok i am off
[05:43] <asac> taking a nap beffore i have to start ;)
[05:43] <asac> in like 4h
[05:43] <micahg> heh, I need to get home so I can get some sleep too
[05:44] <asac> guess tomorrow will be a short day for me
[05:44] <asac> yes. thanks for your help ;)
[05:44] <micahg> asac: thanks for the training
[07:42] <Adri2000> hi
[07:44] <Adri2000> does anyone here use mozplugger? I noticed that it doesn't open .xls files correctly
[07:44] <Adri2000> it opens them with ooo writer instead of ooo calc
[07:46] <Adri2000> actually it calls ooffice on the file, which calls oowriter
[07:46] <Adri2000> anyone noticed this?
[07:53] <Adri2000> in any case, that really seems like an ooo bug
[07:54] <Adri2000> ooffice on foobar.xls works as expected, but ooffice foobar (without the extension, as are the files in the firefox cache) it doesn't
[08:23] <Deathvalley122> hello I have a odd question will the configs on thunderbird from Linux work on windows?
[08:23] <Deathvalley122> just the configs from thunderbird
[08:51] <eagles0513875> hey guys
[08:51] <eagles0513875> i have a question i have a friend who is migrating a pc to windows and would like ot keep the tbird configs will they also work on the windows version of tbird
[10:21] <fta> ripps, strange, it worked for me. could you please show me the full logs + the content of the ppa dir (*dsc, *change, ..)?
[10:35] <BUGabundo_work> morning
[10:43] <eagles0513875> morning BUGabundo_work
[11:07] <ripps> fta: hmm.... it seems I'm going to need to run it again, because the ppa seems to be cleaned out when I run daily.sh on another pocket
[11:08] <ripps> ^ppa^ppa dir
[11:08] <fta> yes, you have build_dir for that
[11:15] <ripps> fta: daily.sh log: http://pastebin.com/f23f87cfd
[11:16] <ripps> contents of ppa: http://pastebin.com/m77004c6
[11:17] <ripps> pssh... poor time to try this, launchpad was experiencing problems at the time
[11:18] <asac> jdstrand: so i have an action to figure out what kernel pieces from .32 we need on .31 for apparmor in lucid (we have .31 for some arm boards)
[11:18] <asac> jdstrand: can you help me with that?
[11:18] <asac> or is all fine in .31?
[11:21] <fta> ripps, oh, i see. it's all fine except the final dput..  yesterday, i tested everything except that :P
[11:21] <fta> fix is trivial, i'll do that later today
[11:22] <ripps> okay, that's all I was trying to say :)
[11:22] <ripps> thanx
[14:22] <jdstrand> asac: the karmic kernel should be generally ok, but there are fixes in .32. best to talk to jjohansen about it (he does all the kernel bits)
[14:24] <asac> ok
[14:24] <asac> thx
[14:30] <BUGabundo_work> jdstrand: u know what kernel Lucid is expected to have?
[14:31] <asac> BUGabundo_work: .32
[14:31] <asac> everyone knows that ;) ... how come not you?
[14:32] <BUGabundo_work> i've been spoty at covering lucid :\
[14:33] <BUGabundo_work> and ppl have been asking for .33 for some reason
[14:33] <asac> most usually dont even know why they want it
[14:33] <asac> just ask for the latest version that might be on market
[14:33] <asac> this is LTS cycle
[14:34] <asac> so we wont go or bleeding edge kernel
[14:34] <asac> rather bake .32 till its most solid
[15:08] <fta2> ripps, could you try this: http://paste.ubuntu.com/352356/ ? i trashed my test package yesterday after my patch :(
[15:16] <fta2> [reed], https://bugzilla.mozilla.org/show_bug.cgi?id=531160   ignored :(
[15:16] <asac> fta2: wah-teh certainly knows how to escalate stuff he he really wants it
[15:17] <asac> he is long term nspr/nss developer that only recently moved to google
[15:18] <fta2> http://code.google.com/p/chromium/wiki/LinuxCertManagement
[15:23] <[reed]> fta2: yeah, wtc is a NSS/NSPR developer
[15:23] <[reed]> has been for years
[15:23] <[reed]> asac: he's been at Google for a while now
[15:23] <asac> sure
[15:24] <asac> recently is relative
[15:24] <asac> is was in the twenties recently too ;)
[15:24] <micahg> asac: we don't want Firefox to display local PHP  source code, right?
[15:24] <asac> stick to upstream behaviour
[15:24] <asac> it should open that in an editor i guess
[15:24] <micahg> k, that's what I thought, I
[15:25] <micahg> 'll close it invalid (bug 503259) if you're interested
[15:26] <asac> if it opens that in editor its fine
[15:26] <asac> its server job to send special mime type if the website wants to display inline
[15:27] <micahg> right, but it's a local file, so file:/// won't be getting a mime type
[15:27] <micahg> maybe I should dupe the Open With bug?
[15:29]  * micahg thinks he'll ask for more info...
[15:49] <ripps> fta2: patch works, it's dputting now
[15:52] <fta2> good, committing
[16:09] <asac> jdstrand: the updates are up (and all build afaict). but i am out now because of lack of sleep so unless you want to test all we have to finish this tomorrow
[16:10] <jdstrand> asac: I'll work through them, but I think waiting til tomorrow and getting more testing would be good anyway
[17:23] <bdrung> asac: i have news for you
[17:23] <bdrung> *drum roll*
[17:24] <bdrung> i pushed my changes to m-d and merged the dh_xul-ext branch back into trunk
[17:24] <bdrung> asac: can you please have a look at it and check if you find bugs? i will write the man pages and then it's ready for upload.
[18:04] <[reed]> jdstrand: hey, I cc'd you on a secbug on bmo
[18:04] <[reed]> and asked for some help
[18:04] <[reed]> so, I'd appreciate if you would take a look sometime :)
[19:21] <Pavlov> hey guys, can you help me with a debian package version numbering problem?
[19:21] <sebner> Pavlov: just ask :)
[19:22] <Pavlov> hey
[19:22] <Pavlov> so, we have had fennec packages.. fennec-1.0b4, b5, etc up to fennec-1.0rc1
[19:22] <Pavlov> now we've dropped rc1
[19:22] <Pavlov> and we're not getting updates from rc1 to 1.0
[19:23] <Pavlov> i'm assuming something thinks that 1.0rc1 is newer than 1.0
[19:23] <sebner> Pavlov: yep, you should have used 1.0~rc1
[19:23] <Pavlov> so i'm wondering if you guys either know how version numbers are compared for these things, or can point me to some place with info on it?
[19:23] <Pavlov> hmm
[19:23] <Pavlov> how does the ~ work?
[19:23] <sebner> Pavlov: dpkg --compare-versions.
[19:24] <sebner> Pavlov: ~ means lower
[19:24] <sebner> Pavlov: man dpkg :)
[19:24] <Pavlov> its not in there;)
[19:24] <sebner> Pavlov: what?
[19:24] <Pavlov> in my dpkg manpage
[19:25] <Pavlov> anything about ~
[19:25] <sebner> Pavlov: yeah, but --compare-versions
[19:25] <Pavlov> oh, i see, these take strings
[19:26] <sebner> Pavlov: I don't know how mozilla guys handle this but you could use 1.0+something, ~ is lower and + is higher
[19:27] <Pavlov> we can change it
[19:29] <Pavlov> ah
[19:29] <Pavlov> hmm
[19:30] <Pavlov> ok, so we've had these versions: http://pastebin.mozilla.org/695132
[19:31] <Pavlov> i'm testing now, but would all of those upgrade properly if we'd put a ~ after 1.0
[19:31] <Pavlov> ?
[19:31] <Pavlov> or should it be more complicated?
[19:31] <sebner> Pavlov: might work, just test with dpkg --compare-versions
[19:32] <micahg> Pavlov: for pre builds in the dailies we use version~hgYMD
[19:33] <Pavlov> ah
[19:33] <Pavlov> ok
[19:33] <micahg> so 1.0~b5~hg20100104
[19:33] <micahg> will upgrade to 1.0~b5
[19:34] <micahg> Pavlov: but the best way to be sure is to use dpkg to check like sebner said
[19:34] <Pavlov> yeah, i am, just trying to understand where i can use ~s and such
[19:34] <Pavlov> micahg: so the 2nd ~ applies to the b5?
[19:34] <micahg> right, it's like before b5
[19:35] <Pavlov> ok
[19:36] <Pavlov> so ideally (will test), 1.0 > 1.0~rc1 > 1.0~b5 > 1.0~b5~date > 1.0~b4
[19:36] <micahg> Pavlov: yep
[19:36] <Pavlov> ok, that makes sense
[19:37] <Pavlov> so, since we screwed up already and need to get 1.0rc1 people on to 1.0, any suggestions?
[19:37] <Pavlov> 1.0.0?
[19:37] <micahg> Pavlov: that should work, but test
[19:37] <micahg> Pavlov: we have a similar issue with prism
[19:37] <Pavlov> yeah it showed correctly
[19:37] <Pavlov> are theere any other operators i should be aware of?
[19:38] <micahg> there should be documentation somewhere...
[19:42] <Pavlov> is the version number just in the file name or in part of the rules or info?
[19:45] <micahg> Pavlov: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
[19:57] <Pavlov> ok
[19:57] <Pavlov> so one last question, in the past we've not seen any problems going from same version to same version
[19:57] <Pavlov> our nightlies right now have been 1.0b6pre for the whole b6pre time
[19:59] <micahg> Pavlov: you can't upload the same version twice
[19:59] <Pavlov> we do!
[20:00] <Pavlov> and it updates ;/
[20:00] <micahg> Pavlov: where?
[20:02] <Pavlov> http://ftp.mozilla.org/pub/mozilla.org/mobile/repos/1.9.2_multi/dists/chinook/extras/binary-armel/ for example
[20:02] <Pavlov> the thing is we've updated the xulrunner which has a date in it
[20:02] <Pavlov> maybe that brings the other along?
[20:02] <Pavlov> brb
[20:05] <micahg> Pavlov: if it's your own repo, you can upload what you want, but idk how your fennec package would update
[20:19] <Pavlov> yeah, im not sure either tbh ;/
[20:19] <Pavlov> it does though!
[20:21] <micahg> Pavlov: are you aure
[20:21] <micahg> sure
[20:22] <Pavlov> yeah
[20:33] <Pavlov> for for our xulrunner packages, would bumping the epoch number to 1 and changing to a ~ make sense?
[20:38] <micahg> Pavlov: well, that's up to you guys how you want the versioning in your repo to work
[20:46] <Pavlov> i'd be happier without the epoch number, but not sure how to make it do what we want otherwise
[20:47] <micahg> 1.9.2+build1 would do it once the release happens
[20:52] <Pavlov> ah
[20:53] <Pavlov> interesting
[20:56] <Pavlov> thanks for your help
[20:56] <micahg> Pavlov: np
[23:00] <bdrung> asac: i want to release mozilla-devscripts 0.19 on sunday at the latest (if i have enough time, i want to do it tomorrow)
[23:05] <bdrung> asac: btw, there are some package still using MOZ_XPI_MOZILLA_DIRS - i will take care once 0.19 hits lucid
[23:08] <bdrung> asac: these values are specified: "thunderbird seamonkey xulrunner-addons icedove iceweasel firefox-addons". can they all be dropped? do all these xul apps support the new layout?