=== tasdomas is now known as tasdomas_afk
=== kb3gtn|2 is now known as kb3gtn
[01:14] <ScottK> Seems to be a limitation Debian doesn't have.  Oh well.
[01:33] <stgraber> ScottK: Debian stores the epoch in the file names?
[01:34] <stgraber> doesn't look like it does (checked a random example on ftp.debian.org, zlib), so they should have the same kind of problem as Ubuntu would
[02:50] <ScottK> No, but the dupe doesn't seem to have been a problem.
[02:56] <wgrant> Launchpad archives do not allow filename conflicts.
=== tasdomas_afk is now known as tasdomas
=== dayangkun is now known as dayangkun_715
=== Sweetsha1k is now known as Sweetshark
=== marcoceppi__ is now known as marcoceppi
[14:50] <qengho> Weird.  My PPA stopped trying to build on ARM lately.  I wonder what happened.
=== Gwaihir_ is now known as Gwaihir
=== tasdomas is now known as tasdomas_afk
=== Kyle_ is now known as Kyle
[19:06] <dobey> qengho: your ppa in question wouldn't happen to be for chromium? i am seeing arm ppa builds here, so i would guess either a hiccup or what you were building was too resource heavy and had to be disabled (but i don't have whatever access is needed to check the latter)
[19:07] <qengho> dobey: Yeah, I think I gave up native on my personal PPA, and the "~chromium-daily" ppa is virtualized, so I need to figure out what to do.
[19:08] <qengho> virtualized makes it run for two days and then hang.  Which is awesome.
[19:10] <dobey> beg for one of those machines you could do make -j192 on? :)
[19:11] <Sonderblade> when you upload a new version of a source package, can you have launchpad not remove the old builds before the new ones are complete?
[19:16] <dobey> Sonderblade: i don't think so. the old builds remain published in the archive though until new builds are published to it (which requires successful builds)
[19:23] <Sonderblade> dobey: really? it deletes the queued builds and replaces them with your most recent upload anyway
[19:24] <dobey> yes of course it does
[19:26] <dobey> well, it's a little more complicated than that (and i don't know the exact heuristics off the top of my head), but why does it matter if it deletes a previously queued build when you upload a new version? you just uploaded a new version, so obviously the older one is wrong
[20:21] <nagyz> hi
[20:22] <nagyz> after changing the e-mail address and deleting the one used at registration, is it normal that I still can only log in with that old, deleted e-mail address?
[20:22] <nagyz> if I want to get a password reset to my new e-mail address, it even tells me in the e-mail that it's not associated with any accounts...
[20:30] <nagyz> ah, ok, it's confusing.
[20:30] <nagyz> found that launchpad.net and login.launchpad.net are two different services...
[20:40] <dobey>  yes, you need to do it on login.launchpad.net (or login.ubuntu.com)
[20:41] <dobey> bzr: ERROR: An error (1) occurred running quilt: None
[20:41] <dobey> err, wrong channel
[20:43] <Sonderblade> dobey: it replaced all binary debs when the first source build started. which i guess is reasonable but not optimal since the i386 build still has to wait 3 hours in the build queue
[20:46] <dobey> Sonderblade: replaced? you mean the view on the web page i presume?
[20:47] <Sonderblade> dobey: correct
[20:47] <dobey> Sonderblade: that's merely a view. the published binaries are still published in the apt archive
[20:48] <dobey> and the previous build doesn't go away immediately on the +packages view either. it takes a little time
[20:48] <Sonderblade> oh i didnt know that
=== cprov is now known as cprov_afk