[20:08] <jayfly> Hello there what is the mirrors url for armhf boards for security ?  for debootstrap.
[20:27] <infinity> jayfly: http://ports.ubuntu.com/ubuntu-ports
[20:28] <jayfly> infinity:  so  there is no secutiy url  for surces list like debian ?
[20:29] <jayfly> Like after I run second-stage and use qemu-arm-static.  then alter sources.list.
[20:29] <jayfly> via chroot
[20:32] <infinity> jayfly: We publish security to the main archive too.  The only reason we *also* provide a security.ubuntu.com is if you're using a mirror that updates slowly, our security mirror is always up to date.
[20:32] <infinity> jayfly: But that doesn't matter for ports, since it's always up to date too, and no one mirrors it. :P
[20:32] <jayfly> sweet thanks a bunch !!
[20:32] <infinity> jayfly: (You want wily-security in your sources.list, of course, but it can be from the same ports.u.c)
[20:32] <infinity> And wily-updates
[20:32] <jayfly> my web app builds for all the odroids and pi's having a lot of fun with it.
[20:32] <infinity> s/wily/trusty/ or whatever you're using.
[20:33] <jayfly> got it
[20:33] <jayfly> I will just right a case statment to say hey if ubuntu just add the main urll
[20:33] <jayfly> url *
[20:34] <infinity> jayfly: If the above was unclear, it should look something like this:
[20:34] <infinity> http://paste.ubuntu.com/12276398/
[20:35] <infinity> jayfly: And you can get away with the same trick for x86 too, if you use Canonical mirrors (archive.ubuntu.com), but if you use non-Canonical mirrors (TLD.archive.ubuntu.com or other), then you want security.u.c for security, because mirrors aren't guaranteed to be up to the minute.
[20:35] <jayfly> that is what I was looking for thanks again    trusty-security
[20:36] <jayfly> thanks again infinity  :)
[20:36] <jayfly> now I can add Ubuntu to the autobuilder's nice webinterface
[20:38] <jayfly> lol pixz keeps on overheating my crappy computer lol.  I should check the arch and mem
[20:38] <infinity> jayfly: FWIW, the reason Debian needs to have a security mirror and we don't really is because Debian's ftpmaster only publishes once or twice a day (and pushes to mirrors), while security.debian.org publishes instantly whenever the security team pushes an update.  So, if you had to wait for ftpmaster, you might be a sad panda.
[20:39] <infinity> jayfly: In Ubuntu, we just publish the whole lot every 15m or so, but only push to non-Canonical mirrors every 4h.
[20:39] <jayfly> No one likes sad panda's
[20:39] <jayfly> well maybe panda hunters but not sure that most people like them
[20:39] <jayfly> whoa every 15 minutes that is great !!
[20:39] <infinity> Great, or insane, take your pick.
[20:40] <infinity> Despite being one of the people behind that, I'm never quite sure if it's crazy. ;)
[20:40] <jayfly> I will go 51-50 on that one
[20:40] <infinity> But it works for us.  You can also understand why we limit how often we push that outside our network. :P
[20:40] <infinity> Mirror operators would strangle us if we triggered them every 15m.
[20:41] <jayfly> infinity:  sometimes debian mirror gives me 404 and build fails half way between stage two of debootstrap.  I should just bite the bullet get some TB drives and clone mirror
[20:41] <jayfly> but I think my network can not handle
[20:42] <infinity> Some mirrors are certainly more reliable than others.
[20:42] <infinity> And if you're using a round-robin DNS alias, you might get screwed if you're in the middle of a push, cause you get Packages from mirror A, and the /pool/ of mirror B.
[20:42]  * jayfly afk 5 minutes to look for fan to put next to autobuilder on this hot day in CA 
[20:42] <infinity> Usually best to pick a specific reliable mirror that's near you and just abuse that one.
[20:46]  * jayfly back 
[22:04] <jayfly>  /join #odroid