[01:18] <klepas> msikma: ping
[01:18] <klepas> troy_s: ping
[01:18] <klepas> Trae: ping
[01:43] <msikma> pong
[01:43] <lizardking> ping all
[01:48] <darkmatter> yo'
[01:56] <klepas> hey chaps
[01:56] <klepas> msikma: what time suits you in regards to meeting online for an hour or two?
[02:09] <PingunZ> troy_s, poke
[02:10] <PingunZ> I'm back :)
[04:06] <troy_s> pingunz
[04:07] <troy_s> greets friend
[04:07] <troy_s> msikma
[04:08] <troy_s> pingunz i see you made it official on the team :)
[04:11] <PingunZ|afk> troy_s, yup
[04:11] <PingunZ|afk> troy_s, I'm _back_
[04:12] <PingunZ|afk> but I'm afk again ^^
[04:12] <PingunZ|afk> later
[04:29] <troy_s> pm me when you are in pingunz
[04:29] <troy_s> msikma -- pm me when you are around.
[05:26] <troy_s> lizardking__: you should wiki your knowledge over getting oransoda into shape
[05:26] <troy_s> lizardking__:  it would be helpful and go one more step towards getting some infrastructure in place.
[05:28] <kwwii> hi troy_s
[05:28] <lizardking__> troy_s: hi
[05:28] <troy_s> greets kwwii
[05:28] <kwwii> lizardking__: we based the example artwork package on your stuff...might want to look into that
[05:29] <kwwii> dholbach simplified stuff a bit
[05:29] <troy_s> the artwork autopackager needs to extend beyond artwork of course.
[05:29] <troy_s> as sound design, etc. all are viable targets.
[05:29] <kwwii> troy_s: very true
[05:29] <troy_s> i was discussing with dholbach about working on getting a better set of syntax rules in place
[05:30] <troy_s> but alas, last week I had to go shoot minis.
[05:30] <kwwii> I think my first work on this stuff will be to get an html preview of available packages ready
[05:30] <lizardking__> troy_s: So by now autopacker is not ablt to package my art, right?
[05:31] <troy_s> lizardking__: well theoretically yes
[05:31] <troy_s> lizardking__: because it is nothing more than automake etc
[05:31] <troy_s> which can be made to do anything...
[05:31] <kwwii> lizardking__: if you look into the example-artwork package you'll find that all we ded was take yours and change the names everywhere
[05:31] <lizardking__> troy_s:  What Should I add to wiki? I will do it if I undestand..
[05:31] <troy_s> but in the more practical sense
[05:31] <troy_s> we need some macros to handle easy bits like ADD_FILE(source, dest) type structure
[05:31] <troy_s> in a singular file
[05:32] <troy_s> so that your 'average' artist can handle the syntaxing.
[05:32] <troy_s> but again, it still needs to accommodate audio, cursors, python scripts, etc.
[05:32] <troy_s> and have them all land in the proper directories.
[05:32] <troy_s> python is probably going to be a heavy player
[05:32] <kwwii> troy_s: yeah, it would be cool if we could get is to be as easy as writing a wiki page
[05:32] <lizardking__> troy_s: Yes, this is the first difficult for Gnome artist. There isn't a main all theme manager. and Ubuntu artist staff should hacks with theese macros
[05:33] <lizardking__> kwwii: yes it would be cool as wiki! I agree
[05:34] <troy_s> lizardking__: macros are probably as a good spot to start as any
[05:34] <troy_s> macros in a singular file... as automake poops out files everywhere that are confusing for typical folks.
[05:36] <troy_s> probably need to brainstorm a good set of possible targets, and build from that.
[05:37] <lizardking__> troy_s: Adding one features to current blubuntu-look is so difficult, because artis needs knowledge about editing makefile.am et simlia. It is a average knowlede. We must abstract the adding mechanis to simplify things
[05:37] <lizardking__> troy_s: yes I agree we must make a brainstorm on that
[05:39] <lizardking__> kwwii: What is the example staff based on mine?
[05:39] <kwwii> erm, i was wrong
[05:39] <kwwii> just saw that
[05:39] <kwwii> we used blubuntu
[05:40] <kwwii> I thought otherwise because we looked at ornasoda quite a bit
[05:40] <kwwii> as it is, you only have to edit a line of files to be installed
[05:40] <lizardking__> kwwii: ok ok
[05:41] <kwwii> in setup.py
[05:41] <lizardking__> it Seems goods this way
[05:41] <kwwii> time for dinner
[05:41] <kwwii> bbl
[05:42] <lizardking__> Good dinner! for me it is time to go
[05:42] <kwwii> yeah, we need to test it out and add a lot of stuff probably
[05:42] <lizardking__> kwwii: yes, well said
[05:42] <kwwii> but we can improve it through time and testing
[05:42] <lizardking__> kwwii: sure
[05:43] <lizardking__> kwwii: Have yet some similar python script or it will be done froms scratch?
[05:44] <lizardking__> I must go out . however I always stay on channel with other computer in the user called lizardking
[05:44] <lizardking__> if you want to report me something wirte there
[05:47] <lizardking__> Where I can find logs of this irc channel?
[07:53] <troy_s> probably easily accomplished with a syntax parser that Daniel would develop -- as he is the build meister.
[07:54] <troy_s> It needs to work for _him_
[07:54] <troy_s> and that means that ultimately he needs to think it through.
[07:58] <torrrrr> hi
[07:58] <torrrrr> my new ubuntu keep forgeting its DNS setup
[07:59] <torrrrr> I have made a location in thet network tool
[07:59] <torrrrr> and set up nicely the network DNS
[07:59] <torrrrr> and it keeps forgetting about them!!!
[08:14] <troy_s> uh
[08:14] <troy_s> wrong forum
[08:14] <troy_s> but i could probably helpy ou
[08:14] <troy_s> make sure that your DEFAULT /etc/network/interfaces file is set to auto
[08:14] <troy_s> for everytihng
[08:28] <PingunZ|afk> troy_s, can I pm you ?
[08:28] <troy_s> go PingunZ|afk
[08:28] <troy_s> ill get back to you if you idle on.
[08:29] <PingunZ|afk> ok
[08:41] <torrrrr> I am a bit dislectic aparently ... though artwork for network
[08:41] <torrrrr> anyway troy_s, I have there: auto eth0
[08:41] <torrrrr> iface eth0 inet static
[09:50] <troy_s> torrrrr: Your wireless will be eth1
[09:50] <troy_s> PingunZ: back momentarily.
[09:50] <PingunZ> troy_s, hey
[09:50] <PingunZ> pm ?
[09:51] <PingunZ> this channel is fine as well
[09:51] <lizardking> Hi all
[09:51] <PingunZ> hey lizardking
[09:51] <troy_s> go pingunz... you can pm me if you wish.
[09:52] <PingunZ> ok
[09:52] <troy_s> lizardking: You might want to lend your thoughts to that spec
[09:54] <darkmatter> afternoon all
[09:55] <troy_s> greetings darkmatter.
[09:56] <lizardking> troy_s: I'm reading the wiki spec. i'm quite busy now
[09:56] <troy_s> lizardking: ditto.
[09:58] <troy_s> oh god
[09:58] <troy_s> not joejaxx
[09:58] <joejaxx> LOL!
[09:58] <troy_s> Everyone hide.
[10:01] <lizardking> troy_s: I do agree with the spec. One thing that I don't undestand it s the LizardK's use case.. Who is the persone that accept or reject the spec?
[10:03] <troy_s> Well it is more a brainstorming page for us
[10:03] <troy_s> so that we have something to take to daniel
[10:03] <troy_s> and he can think it through and see if it is a possibility
[10:04] <troy_s> if _anyone_ can make it happen, Daniel can.
[10:04] <lizardking> troy_s: mHH daniel is quite a boss :D
[10:06] <troy_s> He is darn skilled at making things reality.
[10:06] <lizardking> troy_s: I think we must realize this spec to provide wide theme development from usplash to fonts..
[10:07] <troy_s> Well... wide theme spec is a level of abstraction higher
[10:07] <troy_s> we first need a technique for swiftly integrating elements.
[10:07] <troy_s> the likelihood that anyone with any skillset is going to contribute to the default ubuntu pattern is low.
[10:07] <lizardking> it is a good features for Daniel! Troy I'm leaving.. See u afer or tomorrow..
[10:07] <troy_s> so it will require an infrastructure in place to allow for outside community based work.
[10:07] <troy_s> lizardking: chat soon.
[10:09] <lizardking> yes infact I said wide theme develpoment not wide theme switching ;) it is a lower layer ;D
[10:10] <troy_s> i agree.
[10:11] <troy_s> but yes... we need to brainstorm what would be required and possible 'easy' syntax for the creative design framework.
[10:12] <lizardking> troy_s : Yes the keyword is brainstorm..brainstorm! i'm leaving because my girlfriend is requesting me :D see U later
[10:14] <troy_s> lizardking: chat soon my friend.
[10:14] <troy_s> lizardking: if you get a second or two, see if you can make that idea better.


[03:45] <studio-user645> join
[03:47] <studio-user645> New here
[17:25] <JoseJavier> Hi! I just have installed Ubuntu Studio 15.1 (I upgraded it from Ubuntu 15.1) and my network doesn't want to work, specially WiFi (appears the message "enp5s0 no wireless extensions" and "lo no wireless extensions" when I write iwconfig)
[17:25] <JoseJavier> Can anybody help me with this?
[17:26] <JoseJavier> Please, if somebody knows how to fix this, write me at<EMAIL_ADDRESS>[18:55] <bresteau> 14121969
[22:07] <Demian> hi
[22:09] <Demian> please i need help; somebody can help me? i want to restore my desktop like are the ubuntu when we instaled
[22:12] <Demian> Alguien puede ayudarme a restaurrar los iconos que vienen por defecto en ubuntu studio?
[22:18] <Demian> guys
[22:18] <Demian> can you hel me?
[22:18] <Unit193> You want to restore to installed state?  Perhaps re-install?
[22:20] <Demian> hi, thanks for answer. I would restore the "iconos" for the resent installed state
[22:20] <Demian> sorry if my english is bad.
[22:21] <Unit193> !es | You can always try your native Language
[22:22] <Demian> gracias
[22:22] <Unit193> Da nada.


[01:38] <smoser> hm..
[01:38] <smoser> anyone still awake?
[01:39] <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1061977
[01:39] <ubot2> Launchpad bug 1061977 in cloud-init "Machine fails to commission when console=ttyS0 is present on kernel opts" [Undecided,New]
[02:02] <smoser> smb`, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1061977 . i'd appreciate your input when you awake.
[02:02] <ubot2> Launchpad bug 1061977 in cloud-init "Machine fails to commission when console=ttyS0 is present on kernel opts" [Undecided,New]
[07:55] <rbasak> ikepanhc: around? May I have some help compiling a test highbank kernel please? With "fakeroot debian/rules binary-highbank" (cross compile), I get this: http://paste.ubuntu.com/1261463/ . A zImage does exist but it doesn't seem to work. How should I be building test kernels instead?
[07:56]  * ikepanhc reads
[07:57] <ikepanhc> rbasak: do you `fakeroot debian/rules clean` before fdr binary-highbank?
[07:57] <ikepanhc> `fdr clean` will generate changelog, control in debian folder
[07:57] <rbasak> ikepanhc: when I tried that it wouldn't even start a build. I'll do that now and paste the error.
[07:58] <ikepanhc> rbasak: you using cross-compiler?
[07:58] <rbasak> ikepanhc: yes
[07:59] <ikepanhc> rbasak: try `export $(dpkg-architecture -aarmhf)` then `fdr clean` then `CROSS_COMPILE=<toolchain prefix> fdr binary-highbank`
[08:00] <ikepanhc> alias fdr="fakeroot debian/rules" first
[08:00] <rbasak> Hmm.
[08:00] <rbasak> It seems to be working now
[08:00] <rbasak> I swear I got an error doing the clean step first yesterday
[08:01] <rbasak> So I tried using git clean only instead
[08:02] <ikepanhc> fdr clean is not only to clean those objects, but also generate control and changelog which we need for make
[08:02] <rbasak> I see
[08:03]  * rbasak waits for the build to finish
[08:58]  * ppisati needs to go out for ~30mins, brb
[11:17] <apw> henrix is having ISP issues
[11:43] <psivaa> when i run ubuntu-bug linux today, it's reports 'Problem in linux-image-3.5.0-16-generic
[11:43] <psivaa> The problem cannot be reported
[11:44] <psivaa> This is not an official Ubuntu package. Please remove any third party package and try again'
[11:44] <psivaa> message box is popping up
[11:47] <psivaa> this is a fresh install btw
[12:18]  * rtg thinks that was quite a large update for barely being post beta
[13:06] <smoser> smb, around ?
[13:07] <smb> smoser, yup
[13:07] <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1061977
[13:07] <ubot2> Launchpad bug 1061977 in cloud-init "Machine fails to commission when console=ttyS0 is present on kernel opts" [Undecided,New]
[13:07] <smoser> you have any thoughts there?
[13:08] <smoser> i would really rather not take 'console=ttyS0' off the cmdline (as I really want output there by default rather than to any graphical console which has no chance of being logged), but that is about the only option i see.
[13:08]  * rtg uploaded  linux-lts-quantal 25 hours ago and it _just_ started building.
[13:09] <smb> smoser, well my first thought was that the first pastebin does not look like console output
[13:09] <smoser> smb, on random other note, i know in your cloud-images testing you've had to add ways to get into an image, and that is more involved than you'd like.
[13:09] <smoser> i put together http://bazaar.launchpad.net/~smoser/+junk/backdoor-image/view/head:/backdoor-image
[13:10] <smoser> that basically can mount an image, inject a user into it and then unmount it in one command.
[13:10] <smoser> smb which pastebin ?
[13:10] <smb> smoser, By now I have made my scripts add a nocloud file for newer releaes
[13:11] <smoser> its not console output, its cloud-init output. he couldn't get console output as it is going to a video console.
[13:11] <smb> smoser, http://paste.ubuntu.com/1261109/ shows the cloud-init log.
[13:11] <smoser> oh, for "nocloud" there is a util in cloud-utils called 'cloud-localds' that will basically do it also.
[13:12] <smoser> this one actually modifies the image to add the user, so cloud-init isnt involved/required at all
[13:13] <smoser> let me see if i can get it, smb, but its not really important. (the output of running it)
[13:13] <smoser> it fails
[13:13] <smoser> and 'echo "hi" | sudo tee /dev/console' fails also
[13:13] <smoser> the issue is /dev/console writes fail
[13:13] <smoser> which causes all sorts of stuff to be unhappy
[13:14] <smb> smoser, I think I saw something for this nocloud thing and at least at that point in time it was still too complicated to get working. Still having run some of the cloud init code is usefull to find problems, so this is what gets done right now.
[13:15] <smb> smoser, Yeah I think it probably makes sense to move some of the info from later comments into the description. I think I just stopped somewhere at the top as I could not really guess what you/the report is up to
[13:17] <smoser> smb, well, run 'cloud-localds' it gives a full example of booting an image even.  iss simple for 12.04+.
[13:17] <smb> smoser, So for the question: as far as I remember everytime you do a console= the kernel assigns a console device, just the last one I believe is a bit different as there is one sort of preferred console
[13:17] <smoser> smb, well, comment 4 has just about everything you need.
[13:17] <smb> smoser, You assume I care to read that far
[13:18] <smoser> no, I SAY YOU CARE!
[13:18] <smoser> :)
[13:18] <smb> You *hope*
[13:18] <smoser> if you' dlike i can move the explanation up to the description.
[13:18] <smb> :)
[13:18] <smoser> but anwya.
[13:18] <smoser> yeah, each 'console=' ends up receiving kernel printk
[13:18] <smoser> which is good.
[13:19] <smoser> and it is good that 'console=ttyS0' when there is no serial device present does not stop the kernel from booting.
[13:19] <smoser> however.
[13:19] <smoser> the final console= parameter gets assigned to /dev/console
[13:19] <smoser> and init writes output to /dev/console, and cloud-init inherits that as its stdout
[13:19] <smb> the preferred console thing, yeah
[13:19] <smoser> and any writes to stdout then fail
[13:20] <smoser> which can cause problems :)
[13:20] <smoser> what i had *thought* (apparently wrong) the kernel did was assign /dev/console to the last *good* console= on the cmdline.
[13:20] <smoser> but i guess it only makes intelligent decisions if you give no console=
[13:21] <smoser> otherwise it does exactly what you tell it to do.
[13:21] <smoser> the basic problem is, then:
[13:21] <smb> Not sure it makes any great decisions on its own.
[13:21] <smoser>  * if there is a serial device, i want output to go there (including /dev/console)
[13:22] <smoser>  * if there is no serial device, i would rather writes to /dev/console not give IO error.
[13:22] <smoser> smb, well  http://www.kernel.org/doc/Documentation/serial-console.txt says "If no console device is specified, the first device found capable of acting as a system console will be used."
[13:23] <smoser> "At this time, the system first looks for a VGA card and then for a serial port. So if you don't have a VGA card in your system the first serial port will automatically become the console."
[13:23] <smoser> i'd really just like that order switched.
[13:24] <smoser> and i kind of thought that is what i was getting by adding multiple console=. but i guess not.
[13:24] <smoser> so i think i understand the issue, and i'm just bothering you in a hope that you know something i do not.
[13:24] <smoser> and you can come up with a solution
[13:24] <smoser> and i have not read any kernel code, only doc.
[13:24] <smb> smoser, Really you want a decision about something the kernel does not know until it finds out done before it can find out.  So normal boot might siddenly go wrong
[13:24] <phillw> hi good people, I'm sorry to say that my suggested patch from RedHat does not seem to work on all Nvidia chipsets. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518 As the RC is up coming. PPC needs a bit of help. Arguing with 'X' does not solve the issue, it is a kernel change that was undertaken and has serious regression issues. My ask? please make it work, the PPC people are runnning around getting patches in. the kernel is where
[13:24] <ubot2> Launchpad bug 1043518 in linux "live cd is unusable due to video degradation with the splash boot option enabled" [High,Fix released]
[13:25] <smoser> smb, right. i know its tricky.
[13:25] <smoser> but the doc says it already does such trickyness.
[13:25] <smoser> if you dont pass any console=
[13:26] <smoser> smb, the other option i considered was that I could have the initramfs notice that /dev/console was busted and "fix it".
[13:26] <smb> Yeah, using a VGA (compatible) card which really is there most of the time and then try on serial (just in case)
[13:26] <smoser><EMAIL_ADDRESS>discusses changing it
[13:26] <smoser> but i dont think it really seems to work.
[13:26] <smoser> at least it wasn't extremely simple to change the target device of /dev/console
[13:29] <smb> smoser, I think that part of the kernel "suffers" from not needing much special cleverness as long as you stick to a certain architecture. And it gets even more complicated when there are things like grub in between passing some information or setting up stuff
[13:29] <smoser> well, in this case the thing thats pasin the cmdline is pxe boot
[13:30] <smoser> and i really, *really* want a "one set reasonably fits all" solution.
[13:30] <smoser> as on the first pxe boot of a node, i know zero information about that node.
[13:30] <smoser> s/pasin/passed in/
[13:31] <smb> Yeah, I understand the issue. (btw grub seems to do the passing not by cmdline but directly transferring some structure). I just don't think it will be an easy solution.
[13:32] <smoser> smb, well, could you at least read a bit and see if there is a way i could change /dev/console during initramfs ?
[13:32] <smoser> that'd be sufficient for me, if i could recognize its busted and poke around to fix it.
[13:33] <smoser> before /sbin/init came up.
[13:34] <smoser> then, my solution would be to just do what i'm doing (multiple console= parms) and have initramfs walk them backwards until it finds one that does not give io error.
[13:34] <smoser> and then fix to that.
[13:35] <smb> smoser, I put it on my list but I cannot really say when I get to it. There are enough other things broken that take up time.
[13:36] <smoser> smb, well, at least read that thread on lkml, and tell me if it looks like it is possible or not.
[13:36] <smoser> because i came away with "um... maybe"
[14:15] <diwic> I'm trying to track down a regression between two ubuntu kernels, what's the easiest way to see what patches there are between two kernel versions?
[14:16] <henrix> diwic: git log?
[14:16] <rtg> diwic, it also depends on whether there has been a rebase between them.
[14:17] <diwic> the person claims "<IP_ADDRESS>" is not working and "<IP_ADDRESS>" is.
[14:18] <rtg> diwic, vanilla stable is linear. git log -p v<IP_ADDRESS>..v<IP_ADDRESS>
[14:19] <rtg> you can also restrict your search to just sound, e.g., 'git log -p v<IP_ADDRESS>..v<IP_ADDRESS> -- sound'
[14:19] <diwic> rtg, should that be working on a precise tree? I get "unkown revision or path not in working tree"
[14:19] <rtg> diwic, lemme check
[14:20] <smb> smoser, Hm, *if* it is correct, I would think that it only will work when the current /dev/console driver is a pty. Which would need the console=tty0 last. And there can only be one re-assignment active and not sure whether it can be done when upstart already has changed its stdin and out there.
[14:20] <smoser> yeah. oh well.
[14:20] <rtg> diwic, oh, likely not since stables patches are rebased onto ubnutu. clone the real stable repo at git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
[14:20] <smoser> thanks for reading, smb. thanks for your time.
[14:20] <rtg> s/are/are not/
[14:22] <rtg> diwic, hmm, you're talking about Ubuntu versions, not stable versions, right ? i.e., Ubuntu-3.2.0-30.48
[14:23] <diwic> rtg, okay, so replacing v3.2.0 with Ubuntu tags should do it
[14:23] <diwic> Sometimes you just get unsure of what a command really does
[14:24] <rtg> so then you can get a list of patches by doing 'git log --reverse -p Ubuntu-3.2.0-30.48..Ubuntu-3.2.0-31.49'
[14:24] <rtg> diwic, you can also look in the changelog
[14:25] <diwic> hmm, it seems there are no relevant patches in the sound directory that could have caused this error AFAICS
[14:26] <diwic> I'm reassinging it to the linux package and let someone of you bisect it, chances are it's something completely unrelated
[14:27] <rtg> diwic, make sure jsalisbury is aware of the bug number. note that he's out today.
[14:28] <diwic> rtg, ack
[14:29]  * henrix -> brb
[15:24]  * henrix -> out for ~20mins
[15:38] <sconklin> apw: what triggers the CVE tracker to move a CVE from "triage needed"? I've looked at 1012-4467 and updated the break-fix. Do I need to nudge it in any other way?
[15:50] <hallyn> hi - bug 1057024, last comment - those messages about /dev/sda, are they serious?  serious enough to disregard other bugs from that system (when they can't be reproduced elsewhere)?
[15:50] <ubot2> Launchpad bug 1057024 in libvirt "internal error Process exited while reading console log output: char device redirected to /dev/pts/1 error when creating a vm" [High,Confirmed] https://launchpad.net/bugs/1057024
[15:51] <apw> sconklin, if its pushed to kernel it should be found in an hour sort of thing
[15:51] <hallyn> smb: ^ do you mind taking a quick look?
[15:51] <smb> hallyn, just opening
[15:51] <hallyn> thx!
[15:52] <apw> sconklin, the processing kicks off at :20 and if there is a change can take some time, when did you do the update
[15:53] <hallyn> (note the msgs go on, you can see more in the dmesg file in the tar.gz she appended)
[15:53] <smb> hallyn, serious in the sense that a write failed. not much more info info that piece of output.
[15:53] <smb> hallyn, Let me check the full log
[15:54] <hallyn> smb: thanks.  (i also see kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround)
[15:55] <smb> hallyn, I think I see that in some of my machines too. Without any apparent effect. I would say it *does* us a work-around. :)
[15:57] <hallyn> smb: ok, thanks.  just making sure
[16:02] <smb> hallyn, But yeah, there seems to be quite a bit of trouble with that disk. Might be worth trying to check all cabling and maybe trying to limit the speed to 1.5G...
[16:04] <hallyn> smb: i think it's a laptop
[16:05] <smb> hallyn, Ok harder to check cables. But something is wrong even before
[16:05] <smb> [  975.481263] ata1.00: exception Emask 0x0 SAct 0x3f SErr 0x0 action 0x6 frozen
[16:05] <smb> [  975.481274] ata1.00: failed command: WRITE FPDMA QUEUED
[16:05] <sconklin> apw: I did the update around 30-40 mins ago I think
[16:06] <apw> so perhaps just missed it
[16:06] <apw> worst case delay
[16:06] <sconklin> probably. no worries, I'll wait
[16:06] <apw> bzr: ERROR: Invalid http response for https://xmlrpc.launchpad.net/bazaar/: Unable to handle http code 502: Bad Gateway
[16:06] <apw> or perhaps something bad happened
[16:07] <apw> i'll watch it for the next run
[16:07] <apw> is bzr down for maintenance perhaps
[16:08] <ogasawara> apw: I was hearing grumbling recently within the hour about LP issues
[16:08] <apw> could be that too
[16:10] <ogasawara> apw: in other news, I'm discovering that in order to use the --include-removal flag for packaging, we have to change our debian/source/format to 3.0 (quilt)
[16:11] <apw> ogasawara, thats not going to work well for us, as we have debian.* outside our debian directory
[16:11] <ogasawara> apw: yep, I'd then have to shove an --auto-commit flag in there as well, or it vomits because of that fact
[16:12] <hallyn> smb: dunno what that means
[16:12] <apw> ogasawara, i wish we had chose debian/branch not debian.branch ... with hindsight
[16:12] <smb> hallyn, Don't know in detail but looks like some dma write timed out
[16:13] <apw> apw@dm:~/git2/ubuntu-quantal$ cat debian/debian.env
[16:13] <apw> DEBIAN=debian.master
[16:13] <apw> though as its encoded that way we ought to be able to move it, yeah right
[16:13] <apw> something to talk about at uds in teh bar
[16:13] <ogasawara> apw: indeed.  I think its harmless for now for us to leave things as they are for now.  that highbank clock.c file is never used, and the redundant firmware is not a huge issu
[16:14] <apw> its not ending up in the binaries which is mostly what we care about
[16:14]  * ppisati -> gym
[16:15] <smb> hallyn, Just one other note that apw recently had to reboot to get virt-manager working. We have not really found why that was
[16:16] <apw> indeed, logging out and in was not enough for sure
[16:16] <apw> as i tried that before giving up and doing a windoze on it
[16:17] <hallyn> smb: after installing libvirtd, you do have to log out and back in to be in the libvirtd group (or run newgrp).  had he tried that first?
[16:17] <hallyn> a reboot would of course effect the same thing :)
[16:17] <apw> yes logging out and in changed nothing
[16:17] <smb> hallyn, Yep.
[16:17] <hallyn> apw: hm
[16:17] <apw> i know i was pissed
[16:17] <smb> apw, Did you not also have the complaint about not being able to load the kvm module (though it was loaded)
[16:18] <hallyn> apw: can you reproduce that?  i've been doing these tests for awhile the last two days and haven't seen that
[16:18] <apw> that rings a bell but you test my memory
[16:18] <hallyn> so if you can reproduce, can you give as much detail as possible?
[16:18] <hallyn> apw: oh, hey, did you install kvm *after* installing libvirt by chance?
[16:18] <apw> hallyn, very possible yes
[16:20] <smb> hallyn, While I usually go for "apt-get install virt-host^" which takes care of those details
[16:20] <apw> i think i assumed kvm would be a dependancy
[16:20] <apw> though thinking about it clearly it will not be
[16:20] <apw> so i think i did do them in that order
[16:20] <hallyn> apw: ok, then that makes sense.  and iiuc 'restart libvirt-bin' wouldn't even work, you'd have to 'stop libvirt-bin; start libvirt-bin' to get it to work
[16:21] <apw> that i wouldn't have tried indeed
[16:21]  * smb cannot remember whether we tried the one or the other
[16:22] <apw> sconklin, this is not the right format:
[16:22] <apw>  break-fix: 644595f89620ba8446cc555be336d24a34464950 - ed6fe9d614fc1bca95eb8c0ccd0e92db00ef9d5d
[16:22] <apw> its a two field thing
[16:22] <sconklin> huh, ok. I copied what I found in another file.
[16:23] <sconklin> Oh wait. I'll bet the '-' was a placeholder for a nonexistent break
[16:23] <sconklin> I'll fic it
[16:25] <hallyn> perhaps upstart should warn you when it knows 'restart' won't restart
[16:26] <smb> Maybe restart should restart
[16:27] <sconklin> apw: pushed. Now we wait another cycle. I have to run a quick errand anyway
[17:19]  * apw is about done ...
[19:43]  * rtg -> EOW


[06:07] <jibel> Good morning
[06:27] <callmepk> morning jibel
[06:29] <jibel> Hi callmepk
[07:05] <oSoMoN> good morning desktoppers
[07:11] <jibel> Salut oSoMoN
[07:11] <callmepk> hi oSoMoN
[07:16] <seb128> hey oSoMoN, jibel, callmepk, how are you?
[07:17] <callmepk> seb128, I am fine, just completed my morning class...
[07:19] <oSoMoN> salut jibel, seb128
[07:19] <oSoMoN> hey callmepk
[07:20] <oSoMoN> I'm doing alright, caught in the morning rush to take my daughters to school…
[07:37] <jibel> Salut seb128
[08:11] <marcustomlinson> morning jibel callmepk oSoMoN seb128
[08:14] <jibel> Hi marcustomlinson
[08:32] <didrocks> good morning
[08:35] <marcustomlinson> hey didrocks
[08:38] <didrocks> hey marcustomlinson
[08:44] <jibel> Salut didrocks
[08:44] <didrocks> salut jibel
[08:49] <callmepk> hi marcustomlinson
[09:02] <Laney> heya
[09:04] <marcustomlinson> hey Laney
[09:30] <jamesh> marcustomlinson: I know you did some work a while back on shrinking snaps, so you might find this interesting: https://github.com/snapcore/snapcraft/pull/3413
[09:51] <seb128> callmepk, did you see my review comments on the wslu merge request?
[10:01] <marcustomlinson> jamesh: nice! what about dependencies that are linked at runtime though?
[10:02] <marcustomlinson> dlopen() and the like
[10:03] <jamesh> marcustomlinson: it tries to add plugin-style shared libraries to the starting kernel when determining what libraries are used.
[10:04] <jamesh> marcustomlinson: at first I was using the heuristic of "elf files without sonames", but that didn't work so well, so the current version is "elf files not directly in a lib/ or lib/${arch_triplet} directory"
[10:05] <jamesh> which also isn't perfect, but gets closer
[10:05] <marcustomlinson> ah, very cool
[10:07] <jamesh> it turns out there are a lot of dlopen() style plugins that have a soname set, and a few libraries linked with DT_NEEDED without a soname
[10:07] <jamesh> it's a bit of a mess
[10:20] <marcustomlinson> oh absolutely it’s a mess
[10:23] <callmepk> seb128, yep I see it, I am right now switching to the patch method on wslutilities/wslu.git at ubuntu/master branch, would that be better?
[10:24] <seb128> callmepk, yes, better to the use the upstream patch if possible
[11:14] <oSoMoN> ricotz, FYI, I just pushed 2 revisions to the firefox-beta.xenial branch (and the corresponding package to the firefox-next PPA): I did some patch cleanup, and updated the test expectations
[11:14] <oSoMoN> I am doing the same for other releases now
[11:22] <ricotz> oSoMoN, did you actually runtime tested those changes
[11:23] <oSoMoN> ricotz, autopkgtests passed for all the architectures
[11:23] <ricotz> e.g. ppc-no-static-sizes.patch and s390x-ycbcr.patch are not build fixes
[11:25] <oSoMoN> ppc-no-static-sizes.patch is already upstream
[11:26] <ricotz> autopkgtests doesn't cover rendering issues like what s390x-ycbcr.patch is for
[11:27] <oSoMoN> true, but the patch didn't have any metadata and it really looked like a build fix, I'm happy to add it back if you have a pointer to a bug or a description of the problem it solves
[11:27] <oSoMoN> and we should upstream it
[11:29] <ricotz> so don't remove it without having any feedback
[11:29] <oSoMoN> ricotz, was there someone who reported the problem and verified the fix at the time you added the patch?
[11:31] <oSoMoN> ricotz, the changelog entry for when that patch was added says "Fix skia build on arm64 and s390x", which is why I assumed it was a build fix
[11:34] <ricotz> oSoMoN, there are likely more color conversion issue regarding big-endian archs, e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1672395
[11:34] <ricotz> sorry I don't have time now
[11:35] <ricotz> might be better to postpone such a clean up until after xenial is EOL
[11:36] <ricotz> oSoMoN, I am going to force push and revert you updates
[11:38] <oSoMoN> ricotz, please don't
[11:38] <oSoMoN> I'll revert it myself
[11:38] <ricotz> no
[11:39] <oSoMoN> why not?
[11:39] <ricotz> because I haven't pushed my local change yet anyway
[11:39] <ricotz> (I wanted to wait for beta 9)
[11:40] <oSoMoN> I have taken that into account and your changelog entries are there
[11:40] <ricotz> basically a simple question before doing this, would have been nice
[11:42] <oSoMoN> I should have asked indeed, but the changelog entry really implied it was a build-time fix and my test builds without the patch succeeded, so I didn't really think that required further discussion
[11:42] <oSoMoN> I'll add back the patch with better metadata so this doesn't happen again
[11:44] <ricotz> please cancel all the ppa builds
[11:44] <seb128> ricotz, sounds like an honest mistake, errors happen...
[11:44] <ricotz> seb128, hi, I realize that
[11:47] <oSoMoN> builds cancelled
[11:48] <ricotz> oSoMoN, thank you for looking into cleaning things up, but you are usually not pushing to the beta branches or beta ppa build, so there is more than just a warning wanted from my side
[12:59] <callmepk> hey seb128, messed up the local git during the patch, so delayed a bit... I had to create a new MR here: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/396311
[13:07] <ItzSwirlz> good morning/afternoon :D
[13:09] <seb128> hey ItzSwirlz
[13:09] <seb128> callmepk, I saw it, no conflict and it seems to address the review issues, I will sponsor it today
[13:09] <ItzSwirlz> o/
[13:11] <callmepk> thanks seb128
[13:11] <seb128> np!
[13:55] <oSoMoN> ricotz, re firefox on s390x, there's also https://bugzilla.mozilla.org/show_bug.cgi?id=1626236
[13:56] <oSoMoN> but none of these two bugs mention or link to the patch that we currently have in our packages
[13:57] <oSoMoN> I'm guessing it is coming from https://chromium.googlesource.com/chromium/src/+/fbf038170dc0bd29ead8630013b28c6008047ec1, but I would like to see/read a confirmation from someone who actually tested it that it makes things better
[13:57] <oSoMoN> and then we could upstream it
[13:57] <oSoMoN> otherwise I feel like we're carrying a patch for no real added value
[13:58] <oSoMoN> but I'm fine leaving it there until we figure it out
[15:22] <ricotz> oSoMoN, I don't remember where it came from, but it serves a purpose. I don't have a s390x instance to give a build some runtime testing, I am going to try setting one up with qemu if that is possible
[15:22] <oSoMoN> ricotz, cool
[15:23] <ricotz> oSoMoN, afair seb gave s390x some runtime testing last time when the bigendian icu patches were merged
[15:24] <ricotz> it better to target the ff trunk builds here
[15:31] <cpaelzer> ricotz: oSoMoN: I'd not recommend to try s390x-qemu emulation; by far the simplest way is getting an s390x instance on canonistack
[15:31] <oSoMoN> yeah, I got one of those running, I'll see if I can run tests
[15:34] <ricotz> cpaelzer, I see, I assume it would be very slow?
[15:36] <ricotz> oSoMoN, thanks
[15:39] <cpaelzer> ricotz: it is  not supporting all instructions a new kernel&glibc might issue, so expect breakage in the worst case
[15:56] <oSoMoN> ricotz, here are some screenshots taken on s390x: https://people.canonical.com/~osomon/ff-s390x/
[15:57] <oSoMoN> the first 3 are with the version in the hirsute archive (84.0.2), the 4th one is a 85.0~b8 from my PPA without the s390x patch
[15:57] <oSoMoN> I'm not seeing any difference in image rendering between the two versions
[15:57] <oSoMoN> i.e. image colors are wrong in both cases
[16:03] <xnox> we don't care about s390x though =)
[16:07] <hellsworth> good morning desktopers
[16:11] <oSoMoN> good morning hellsworth
[16:11] <hellsworth> hi there oSoMoN
[16:11] <marcustomlinson> hey hellsworth
[16:11] <hellsworth> o/ marcustomlinson
[16:15] <ricotz> oSoMoN, I assumed this color format is used in videos, but its might be obsolete
[16:23] <ricotz> oSoMoN, could you compare these https://people.ubuntu.com/~ricotz/firefox/
[16:34] <ricotz> oSoMoN, could you compare these https://people.ubuntu.com/~ricotz/firefox/
[16:39] <xnox> horay! new laptop bad screen resolution =)
[16:40] <xnox> i'm confused if i have hidh-dpi laptop or not, and if i should have scaling or not, and how things should look like on it
[21:24] <oSoMoN> ricotz, it looks like my last messages didn't go through as I was having issues connecting to my IRC bouncer
 ricotz, see the first 4 screenshots in https://people.canonical.com/~osomon/ff-s390x/
 (ff84 is the archive build, ff85 is my custom build without the patch)
 looks the same to me
 oSoMoN, I assumed this color format is used in videos, but its might be obsolete
 oSoMoN, could you compare these https://people.ubuntu.com/~ricotz/firefox/
[21:27] <oSoMoN> ricotz, yes, and the above was my answer to your request for comparison
[21:28] <ricotz> ok
[22:12] <ricotz> oSoMoN, uploaded beta 9
[22:12] <oSoMoN> ack, thanks


[14:45] <xnox> jodh: nice one. Have a review knit-pick.
[14:55] <jodh> xnox: ack. thanks - branch updated again ;)
[14:57] <xnox> jodh: right =) off by not error.


[00:41] <wilee-nilee> Not sure if this is appropriate channel, however I'm a fairly experienced ubuntu user except in this area.  So I have a smart tv, I have minidlna working with home and, video, but can't get it to read an external usb HD, not sure the pathway. I
[02:33] <crass> weird, I have been able to use resize2fs on a live filesystem in the past
[02:33] <crass> but now it appears to be requiring that the block device is not in use...
[02:34] <crass> any ideas why now resize2fs fails when opening the device because its in use?
[05:44] <gartral> alright all, i've been fighting this all night, even with ddrescue I can't get the superblock of my booting partition from my server to transfer to a new drive, any advice?
[06:15] <sarnold> gartral: (just a quick note before I go to bed...) if you really can't get the superblock there tend to be superblock backups made around 8192 or 8193 or something, there's a whole string of superblock backups. Probably you can't get your master boot record or partition boot record to copy over instead, but those might be easier to create anew anyhow. Hope this helps :) have fun
[06:47] <darkXplo_> hi guysss
[06:48] <darkXplo_> can anyone help me with UPW
[06:49] <darkXplo_> https://gist.github.com/anonymous/39e070dbc70c45c48502
[06:50] <darkXplo_> UFW
[07:48] <Jinxed-> Anyone know of a video conferencing server for a private network that would allow android mobile devices to connect
[08:01] <gartral> sarnold: yea, none were working
[08:10] <gartral> Jinxed-: asterisk should allow that
[09:54] <chmac> Added eth1 to /etc/network/interfaces with a static ip for a private subnet (<IP_ADDRESS>/24), but the route for that subnet is not being created...
[09:54] <chmac> Do I need to manually add the route somewhere?
[09:54] <chmac> I think on my other machine it "just works"...
[09:56] <Svetlana> http://multipath-tcp.org/pmwiki.php/Users/ConfigureRouting has some details about how this is done. Is it how you do it on both machines?
[09:58] <Svetlana> Looking at http://manpages.ubuntu.com/manpages/precise/man5/interfaces.5.html I think you can add a command into interfaces file directly... like 'IFACE OPTIONS' section says. Is this how you do it?
[10:00] <chmac> Svetlana: http://pastie.org/8381455
[10:00] <chmac> Svetlana: Yeah, I'm reading here and there that I could add a `post up route add foo`
[10:01] <chmac> But that seems like a hack, and I'm not sure why it's working on one machine but not another
[10:01] <chmac> These are both ubuntu-server instances running inside virtualbox
[10:02] <Svetlana> Is this how your interfaces file looks under both machines? Does any of them have different files in /etc/network/if-up.d/?
[10:03] <Svetlana> (I gave you two links. https://wiki.merproject.org/wiki/Nemo/USBNetworking is an example for the second one: you would have to replace the stuff after 'up' and 'down' with 'route bla bla' commands.)
[10:03] <chmac> Svetlana: The machine that works has a postfix file in there, let me see if there's anything useful in it...
[10:04] <chmac> Otherwise, the md5s match on all the files on both machines
[10:04] <chmac> Svetlana Nothing about routing in the postfix file
[10:04] <Svetlana> And while the route is not bring created, is the connection activated at all? 'sudo ifconfig' shows 'inet addr' line for the active ones.
[10:04] <chmac> I think I could solve it with the `post up route add` option, but it's a Sunday morning and I'm inclined to spend a little time to see if I can figure out the issue!
[10:05] <chmac> Svetlana: Hmm, let me restart the vm and see...
[10:05] <chmac> Svetlana: Yeah, the interface is up
[10:06] <Svetlana> what IP address does ifconfig show?
[10:06] <chmac> <IP_ADDRESS>
[10:06] <Svetlana> Okay, that looks fine.
[10:06] <chmac> Shows a netmask of <IP_ADDRESS> though...
[10:06] <chmac> Aha, while my other machine shows <IP_ADDRESS>
[10:07] <chmac> Crazy, typo in the interfaces file, I wrote netmasT instead of netmasK :-)
[10:07] <chmac> Svetlana: Thanks a lot for your help, I really appreciate it
[10:08] <Svetlana> http://manpages.ubuntu.com/manpages/precise/man5/interfaces.5.html in 'static method' it does not list 'network' rule, but you have it. It is a bit strange.
[10:09] <chmac> Svetlana: Hmm, good point, probably ignores it, I guess it ignored the netmasT line! :-)
[10:10] <Svetlana> When you said 'Nothing about routing in the postfix file', you meant the interfaces file, right? Or were you referring to the if-up.d/* files, which you compared?
[11:45] <eagles0513875_> hey guys i am trying to change the php upload size and for some reason even after changing the upload_max_filesize and restarting apache the filesize has not changed
[15:48] <AntelopeSalad> hey guys, i'm setting up my first server and i'm curious if init.d and upstart scripts will conflict with each other
[15:48] <AntelopeSalad> basically i've installed things like nginx through apt-get (after updating my source list) and that seems to setup an init.d script but i've been following guides that create a custom upstart config
[15:49] <AntelopeSalad> is there a way to somehow disable the init.d version so it doesn't run double the processes?
[15:50] <qman__> most packages which have upstart scripts install a dummy init.d script, verify first that there isn't an upstart script already
[15:50] <qman__> that said, if the package includes an init.d script and not an upstart script, adding your own in will conflict with the package contents
[15:51] <AntelopeSalad> qman__: what can i do to fix it? i made the upstart config afterwards
[15:51] <qman__> it's possible to manually remove/disable the init.d script and install the upstart script, but this will break every time you update the package
[15:51] <qman__> the correct way to change this is to rebuild the package using the upstart script instead
[15:51] <AntelopeSalad> what do you think is the most sane way to ensure that the process stays up?
[15:52] <qman__> the most sane way is to stick to the distro default and not touch it
[15:52] <AntelopeSalad> i didn't build anything, all i did was apt install nginx
[15:52] <AntelopeSalad> but i wasn't sure if that came with any type of process monitoring
[15:52] <qman__> it doesn't; neither does upstart
[15:53] <AntelopeSalad> but i setup process monitoring with upstart (i think)
[15:53] <qman__> if you need process monitoring, implement that separately, either with a simple cron job or to full on systems like nagios
[15:54] <AntelopeSalad> this is what i setup by following some tutorial http://pastie.org/8381932
[15:55] <AntelopeSalad> i thought upstart was the standard way to make sure stuff loads on startup and doesn't die
[15:55] <qman__> upstart provides service management the same as traditional sysvinit did; it has different features
[15:55] <qman__> it is not a monitoring system
[15:56] <AntelopeSalad> maybe i'm using the wrong termonology
[15:56] <qman__> it can be used by your monitoring system, though
[15:56] <AntelopeSalad> all i want to do is make sure if nginx dies that it gets restarted
[15:56] <AntelopeSalad> and that it starts when the system boots up
[15:56] <qman__> in a traditional init script you'd manually implement respawn on failure in the service itself
[15:56] <qman__> where upstart provides rudimentary functionality to respawn on failure
[15:57] <AntelopeSalad> so i should use the default init.d script and not touch it, and that will take care of it loading on startup?
[15:57] <qman__> yes
[15:57] <AntelopeSalad> but then use something other than upstart to make sure it doesn't die?
[15:57] <qman__> yes, if you care about monitoring, implement it
[15:58] <qman__> that can be anything from a simple cron job that checks if it's running to a full featured monitoring system like nagios
[15:58] <AntelopeSalad> if i delete the config file in the /init/ dir is that good enough to completely reverse the mistake i made?
[15:58] <qman__> if that's all you created, then yes
[15:58] <AntelopeSalad> (and reboot the machine of course)
[15:58] <qman__> no reboot necessary
[16:00] <qman__> while converting to upstart is a good thing long term, sticking to the system defaults wherever possible is the most sane way to manage a system, because then updates won't break things
[16:00] <qman__> nginx will more than likely be converted to upstart in a future release if it hasn't already
[16:00] <AntelopeSalad> ok thanks, so it's really up to the tool to handle supplying the startup scripts
[16:00] <qman__> correct; you can do it yourself but there's a lot to take into consideration
[16:01] <qman__> and it involves building your own packages
[16:01] <AntelopeSalad> that sounds like the opposite of what i want to do haha
[16:01] <qman__> if you want set and forget, sticking to defaults is best
[16:01] <AntelopeSalad> btw is it standard to run "service nginx start" or should i be using sudo?
[16:02] <qman__> you generally need root privileges to run the service command
[16:02] <AntelopeSalad> ok, i actually didn't try it without it but i wasn't sure if running a process as root was a good idea
[16:02] <qman__> it doesn't run nginx as root
[16:03] <qman__> or at least it shouldn't, that would be a very bad bug
[16:03] <qman__> generally the init script handles deescalation of privileges
[16:03] <AntelopeSalad> i think it's running it as root
[16:04] <AntelopeSalad> http://pastie.org/8381963
[16:04] <qman__> ah, I see
[16:05] <qman__> only the main binary is using root, the subprocesses are running unprivileged
[16:05] <AntelopeSalad> i'm not sure though
[16:05] <qman__> which looks to be by design
[16:05] <AntelopeSalad> yeah
[16:05] <qman__> I'm not intimately familiar with nginx
[16:05] <AntelopeSalad> the worker is what gets touched by the public maybe?
[16:05] <qman__> but that's a sane setup
[16:05] <qman__> right
[16:05] <AntelopeSalad> because in the nginx conf i had to supply the # of workers
[16:05] <AntelopeSalad> i chose 1 in this case
[16:06] <qman__> apache does the same thing
[16:06] <qman__> there's one root process and everything else is unprivileged
[16:07] <AntelopeSalad> ok, thanks for the advice, i'll continue to install everything as i did before and look into nagios for making sure they don't explode
[16:07] <AntelopeSalad> (minus the upstart confs)
[16:07] <qman__> http://pastie.org/8381969
[16:07] <qman__> there's lots of ways to do it, nagios is just one popular one
[16:08] <AntelopeSalad> is it lightweight?
[16:08] <qman__> not really, it's made to be comprehensive
[16:08] <AntelopeSalad> i'm running quite a bit on a micro instance, coming really close to the ram limitation
[16:08] <qman__> well there's two main ways to run nagios
[16:08] <qman__> you can run with a client, or clientless
[16:09] <qman__> clientless, your nagios server just makes connection attempts to see if the service is up
[16:09] <qman__> you can http request and based on the result, either say it's up, or failed
[16:09] <AntelopeSalad> oh, so i can't even run nagois on the same server as the deployed web app?
[16:09] <qman__> right
[16:09] <AntelopeSalad> yeah that's definitely not going to work in this case
[16:10] <qman__> well, you can, but it's not the best design setup
[16:10] <qman__> if you just want local monitoring, you'd be better off with a simple shell script
[16:10] <AntelopeSalad> atm i'm dealing with 1 instance
[16:10] <AntelopeSalad> maybe i should look into something tied into the language the app is written in?
[16:12] <qman__> this is about the most basic script: http://pastie.org/8381973
[16:12] <qman__> you'd then set that script up to run as root in the crontab every X minutes depending on your need
[16:13] <AntelopeSalad> oh
[16:13] <qman__> you can get more complicated by checking pids or logs
[16:14] <qman__> or add a line to email you when it's down
[16:14] <qman__> whatever you need
[16:14] <AntelopeSalad> would the pid be in /var/run/nginx.pid?
[16:15] <AntelopeSalad> i'm comparing your script to that upstart conf and it seems similar, except the upstart one handles the workers
[16:15] <AntelopeSalad> i'm not sure what happens if nginx crashes, it might be possible for it to be alive but with no workers in which case that's bad
[16:15] <qman__> probably, I don't have any nginx servers to check
[16:15] <qman__> well, one thing you can do
[16:16] <qman__> http://pastie.org/8381986
[16:16] <qman__> er, want that to say restart
[16:17] <AntelopeSalad> is restart smart enough to also start if it can't find something to restart?
[16:18] <qman__> should be, you can test it
[16:18] <qman__> kill nginx without stopping the service, then try
[16:19] <qman__> if it isn't, you could stop then start
[16:19] <qman__> then if stop failed it would continue to start
[16:19] <AntelopeSalad> it seems to be ok, i killed the master manually
[16:19] <AntelopeSalad> and it restarted
[16:19] <AntelopeSalad> yep it works, i killed both the master+worker manually and restart still worked
[18:13] <AntelopeSalad> a sources.list.d file is saying to use "squeeze" for an ubuntu code name for a certain tool i'm trying to install, they don't seem to have one for raring or precise -- is this going to be bad if i use squeeze?
[18:13] <AntelopeSalad> i'm using ubuntu 13.x
[18:17] <genii> AntelopeSalad: What exactly are you trying to install?
[18:17] <AntelopeSalad> genii: redis, and after some googling it seems like the dotdeb.org list is my best hope for a recent version
[18:18] <TJ-> AntelopeSalad: The biggest challenge can be what the package depends on (other packages and their versions) because they may not be correct in Ubuntu. The other issue is slight difference in  package config installation practices / locations between Debian and Ubuntu
[18:19] <AntelopeSalad> i decided to take a risk and just tried it using "stable" as the code and it seems to have installed correctly, do you think i'm in the clear if it happened to complete without errors?
[18:20] <TJ-> AntelopeSalad: Well you've managed to avoid the dependency issues so just monitor it, its log-files, and the system log-files until you're satisfied
[18:20] <AntelopeSalad> ok thanks
[18:20] <genii> There seems to be a popular PPA for it which is maintained
[18:20] <AntelopeSalad> genii: which?
[18:21] <genii> AntelopeSalad: https://launchpad.net/~rwky/+archive/redis
[18:21] <genii> Last build was 5 weeks ago which is pretty recent
[18:21] <AntelopeSalad> ah yes, i saw this earlier but it didn't contain the steps on how to get it into the sources list
[18:23] <genii> AntelopeSalad: sudo add-apt-repository ppa:rwky/redis     ..in this case. DISCLAIMER: USE PPAs AT YOUR OWN RISK
[18:24] <AntelopeSalad> yeah i got hung up on doing the key step
[18:24] <AntelopeSalad> most other tools i've used had a url that had the key
[18:24] <AntelopeSalad> this one links to the key but it's not something i can just wget
[18:24] <genii> But in this scenario, the PPA is far less dangerous than adding Debian repositories
[18:25] <AntelopeSalad> oh, so this ppa method bypasses having to do the sources.list steps?
[18:25] <genii> AntelopeSalad: It makes an entry in /etc/apt/sources.list.d/ directory with the PPA name
[18:26] <AntelopeSalad> if i delete that file in the sources.list.d dir does that completely wipe it out after i run apt-get update?
[18:26] <genii> AntelopeSalad: This way no foreign entries make it into /etc/apt/sources.list main file and you can always later do ppa-purge command if it was problemmatic
[18:26] <AntelopeSalad> because if this launchpad version works i'd like to delete the dotdev one
[18:27] <genii> AntelopeSalad: No, just deleting the file there doesn't remove the app if it was already installed. You need to do the ppa-purge as described. Alternately with ppa name, like: sudo ppa-purge <name>
[18:31] <AntelopeSalad> ok
[18:31] <AntelopeSalad> it seems to have worked using the launchpad's ppa, thanks
[18:32] <AntelopeSalad> that version it has is the latest stable one too
[18:35] <genii> AntelopeSalad: Just remember that if you experience some issue with it, you probably won't find support here and will need to talk to the PPA maintainer or to the redis people instead :)
[18:36] <AntelopeSalad> genii: yeah
[18:37] <AntelopeSalad> also 1 one last thing if you don't mind...
[18:37] <AntelopeSalad> if i do a dpkg -i foobar.deb , this still gives me an init.d script right?
[18:38] <genii> AntelopeSalad: If the package installs one
[18:38] <AntelopeSalad> ok, so that's up to the package -- gotcha
[18:39] <AntelopeSalad> thanks again, in this i guess i got lucky and it did (elasticsearch)
[19:59] <zexcriz> what is the difference between hosting our data on our VPS and in the other in the cloud ? i doubt there is any difference
[20:05] <bekks> zexcriz: How important is that data?
[20:06] <zexcriz> bekks, currently hosting a VPS and now i was curious what are advantages or disadvantages if any if go for cloud
[20:06] <zexcriz> so just need some advice, what to go for as i am totaly confused over here.
[20:06] <bekks> I'd not use a cloud for anything that might be important.
[20:07] <soren> Uh..
[20:07] <soren> So you'd not put anything important in the cloud, but a VPS is fine?
[20:07] <zexcriz> bekks, data security in cloud is a prob ?
[20:07] <bekks> soren: I am not using a VPS either.
[20:07] <soren> bekks: Then your argument is nonsense.
[20:08] <bekks> soren: If you think so: please take over the conversation.
[20:10] <zexcriz> so thinking about efficiency and security which is the best option ?
[20:12] <pmatulis_> bekks: why do you say the cloud is not good for important data?
[20:13] <bekks> pmatulis_: Because there is no guarantee whatsoever that you actually can access your data when you need it. There is somethin like 99.9xy% -- but thats lower than 100%.
[20:13] <soren> Same for anything else.
[20:13] <soren> Even stuff you control yourself.
[20:14] <soren> But certainly for any other type of storage managed by someone else, whether it's called "cloud" or just "VPS" or whatnot.
[20:16] <soren> zexcriz: "Cloud" basically means that you can control "it" with an API. It also typically means that you're charged in very small increments and only for exactly how much you're actually consuming.
[20:16] <soren> zexcriz: In terms of security for instance, cloud and VPS is the same thing.
[20:18] <zexcriz> soren, getting your point.
[20:18] <soren> zexcriz: Being able to control things with an API means that you can very easily acquire (and get rid of) resources. If your resource requirements are almost entirely static, you might as well stay with what you've got.
[20:19] <zexcriz> soren, ok :)
[20:19] <soren> If, on the other hand, your resource demand varies (over the course of a day, or over the course of a week or over the course of a year, for instance) and you applications scale well horizontally, "cloud" might be a good option for you.
[20:19]  * soren has to run
[20:20] <pmatulis_> good intro to cloud ^^^
[20:21] <zexcriz> yeah that was really a good intro..!! :) thanks soren :)
[20:23] <pmatulis_> a main point is trust.  you implicitly place your trust in a cloud provider.  as opposed to building your own (private) cloud
[20:24] <zexcriz> imp point.
[20:26] <ersi> Magic eightball says: Outlook cloudy.


[03:23] <valorie> Katnip: yes, they are nice for testing apps
[04:01] <Scottbert> Okay does ANYONE know how to enable KMS with Nvidia's drivers?
[11:08] <BluesKaj> Hi folks
 https://youtu.be/A42NLMjG05k … Please like and subscribe please
[12:25] <jackcy> Greetings community. Request for support: I want to upgrade/install Kubuntu 18.10 to 19.04 on my Asus zenbook 14 (new kernel for sound issue fix). Problem is that booting only works approximately one out of 15 times (live usb stick too, only with luck and nomoedset option). As screen freezes at stage loading initial ramdisk I do not have logs or anythind. There are other Asus users with same problem https://askubuntu.com/questions/
[12:25] <jackcy> 1136264/ubuntu-19-04-stuck-on-boot. AFAIK there was also a intel bug with HP devices that was fixed for final release. Any recommendations? thank you in advance.
[12:54] <BluesKaj> jackcy, you didn't indicate clearly if the OS is already installed or the problem occurs when booting the usb stick
[12:58] <jackcy> thank you. This happens in all three constellations. After upgrading the restart does not work. Booting with live usb stick only works with boot option nomodeset and notevery time. I also managed to install 19.04 but here also boot sequence freezes with loading initial ramdisk. After several boot attempts I was able to boot into GUI but next boot its stuck again. Meanwhile I reinstalled 18.10.
[13:01] <BluesKaj> jackcy, check your firmware/uefi/bios settings, perhaps secure boot is not enabled and that can cause problems at boot not allowing nomodeset to apply.
[13:02] <jackcy> OK, I'll try that. Thank you for the hint
[13:03] <BluesKaj> and in other cases the reverse is true, disabling secure boot might help too, it's a coin toss with the firmware setting on some machines
[13:04] <jackcy> then i check for a firmware upgrade as well :)
[13:06] <BluesKaj> ok
[15:05] <Newfangled> Trying Kubuntu for the first time in years. Love the polish of the UI!
[15:05] <Newfangled> Sysinfo for 'Kubuntu': Running inside KDE Plasma 5.15.4 on Ubuntu 19.04 (Disco Dingo) powered by Linux 5.0.0-13-generic, CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz at 953-1214/3200 MHz, RAM: 3440/3821 MB, Storage: 8/686 GB, 175 procs, 1.2h up
[15:42] <nikita> hi
[15:43] <nikita__> l
[15:43] <nikita__> hi
[15:43] <nikita__> who are here&
[15:43] <nikita__> ?
[15:43] <nikita__> fuc
[15:44] <BluesKaj> nikita__, do you have a kubuntu support question?


[05:48] <ailo> tanders12: Hey..
[15:08] <scott-work> falktx_bad_net: firstly, lol @ your name, secondly i posted in the ubuntu forums post
[15:09] <falktx_bad_net> yes, scott-work, I'm *trying* to reply...
[15:10] <scott-work> falktx_bad_net: to help keep the post currently (and at the top of the list) and to help explain the concept/educate people would you like me to post some questions to which you can respond?
[15:12] <falktx_bad_net> scott-work: now or on the thread ?
[15:12] <falktx_bad_net> oh, post
[15:12] <falktx_bad_net> falktx_bad_net: yes, ask anything you want
[15:13] <falktx_bad_net> lol, scott-work ^
[15:13] <scott-work> lol
[17:25] <rexbron> hey everyone
[17:31] <scott-work> hi rexbron
[17:31] <rexbron> hey scott-work
[17:31] <scott-work> hey, does anyone want to dig into why the ubuntustudio-video package keeps creating uninstallable binaries?
[17:31] <scott-work> if not i'll make time next week to check it out
[17:33] <ailo> scott-work: do you know which cause the problem?
[17:34] <scott-work> ailo: i'm not really sure, i was going to first check to see if one of the individual packages was having trouble building, but that might not be the right path forward?
[17:34] <scott-work> ailo: after that (just so i had done the most basic homework for it) i was going to ask in #ubuntu-motu for some suggestions
[17:34] <scott-work> of what to look at
[17:37] <ailo> scott-work: I still don't know anything about the build procedure. I'm pretty ignorant of how Ubuntu works on that level. I guess I would need to find out about some things before I could assist?


[04:21] -queuebot:#ubuntu-release- Unapproved: fwupdate-signed (xenial-proposed/main) [1.11 => 1.11.1] (core)
[04:23] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate-signed [source] (xenial-proposed) [1.11.1]
[09:25]  * LocutusOfBorg each morning, an Ubuntu developer wakes up, and wonders about the auto import being slow or broken, will it work today? should I report it? is anybody aware? pytest is in Debian since ~20 hours, but no signs of it in Ubuntu :)
[09:28] <tsimonq2> I do agree that it's not fast...
[09:29] <tsimonq2> (feel free to not take my suggestion :P) maybe someone should make the cronjob run more often? ;)
[09:32] <LocutusOfBorg> tsimonq2, I'm wondering about it being broken, not slow :) there have been changes in some infra on the Debian side I guess, that inRelease stuff
[09:33] <tsimonq2> LocutusOfBorg: Fair :P
[09:35] <cjwatson> LocutusOfBorg: Snideness just makes me want to /ignore you TBH
[09:37] <LocutusOfBorg> sorry, it wasn't mean to be offensive, just I don't want to report stuff if not broken, and if you are already aware of it
[09:38] <cjwatson> LocutusOfBorg: I know what the current set of problems is and there's no need to report them.  One is that debmirror sometimes fails due to the equivalent of hash sum mismatches (which I'll fix upstream once I get some time).  The other is that the cron jobs aren't sequenced properly so that sometimes debmirror succeeds but takes long enough that the actual LP import after it doesn't pick it ...
[09:38] <cjwatson> ... up and so it ends up waiting about six hours, which is the state it's currently in; I have an outstanding merge proposal to fix that
[09:39] <LocutusOfBorg> ok thanks, I just would like to see it running over the weekend, I plan to fix in Debian some of the failures in testsuites, and I would like to avoid uploading them directly in Ubuntu, and see autopkgtest run again twice
[09:39] <LocutusOfBorg> queues are overloaded, and the pytest fixes are useful
[09:40] <cjwatson> I see no particular reason it wouldn't run over the weekend, even if not every single run succeeds
[09:40] <cjwatson> And I'm poking sysadmins about the MPs to fix the second problem above
[09:41] <LocutusOfBorg> so that sum mismatch is not a permanent blocker, this is nice then
[09:42] <cjwatson> No, it depends on relative timing of our cron job with the upstream mirror update, but it indeed doesn't leave things permanently broken, just makes that run fail
[09:43] -queuebot:#ubuntu-release- New: accepted kicad [amd64] (artful-proposed) [4.0.6+dfsg1-1]
[09:43] -queuebot:#ubuntu-release- New: accepted lazarus [arm64] (artful-proposed) [1.8.0~rc3+dfsg-2]
[09:43] -queuebot:#ubuntu-release- New: accepted lazarus [i386] (artful-proposed) [1.8.0~rc3+dfsg-2]
[09:43] -queuebot:#ubuntu-release- New: accepted node-sshpk [amd64] (artful-proposed) [1.13.0+dfsg-1]
[09:43] -queuebot:#ubuntu-release- New: accepted lazarus [amd64] (artful-proposed) [1.8.0~rc3+dfsg-2]
[09:43] -queuebot:#ubuntu-release- New: accepted node-parse-asn1 [amd64] (artful-proposed) [5.1.0-1]
[09:43] <LocutusOfBorg> awesome thanks! have a great day, I promise to not bother you again hopefully for some days, promised :D
[09:43] -queuebot:#ubuntu-release- New: accepted lazarus [armhf] (artful-proposed) [1.8.0~rc3+dfsg-2]
[10:07] -queuebot:#ubuntu-release- New binary: cg3 [ppc64el] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[10:08] -queuebot:#ubuntu-release- New binary: cg3 [s390x] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[10:09] -queuebot:#ubuntu-release- New binary: cg3 [amd64] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[10:10] -queuebot:#ubuntu-release- New binary: cg3 [i386] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[10:11] -queuebot:#ubuntu-release- New binary: cg3 [arm64] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[10:11] -queuebot:#ubuntu-release- New binary: cg3 [armhf] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[10:16] -queuebot:#ubuntu-release- New binary: openmama [ppc64el] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[10:19] -queuebot:#ubuntu-release- New binary: openmama [s390x] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[10:20] -queuebot:#ubuntu-release- New binary: openmama [amd64] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[10:22] -queuebot:#ubuntu-release- New binary: openmama [i386] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[10:25] -queuebot:#ubuntu-release- New binary: openmama [arm64] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[10:35] -queuebot:#ubuntu-release- New binary: openmama [armhf] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: hfst-ospell [ppc64el] (artful-proposed/universe) [0.4.5~r343-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: hfst-ospell [s390x] (artful-proposed/universe) [0.4.5~r343-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: golang-etcd [amd64] (artful-proposed/universe) [2.0.0-3] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: libbtbb [s390x] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: libbtbb [ppc64el] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: gexiv2 [amd64] (artful-proposed/main) [0.10.6-1] (ubuntu-desktop)
[11:14] -queuebot:#ubuntu-release- New binary: hfst-ospell [amd64] (artful-proposed/universe) [0.4.5~r343-1] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: hfst-ospell [i386] (artful-proposed/universe) [0.4.5~r343-1] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: haskell-base-prelude [ppc64el] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: haskell-multiset-comb [ppc64el] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: haskell-base-prelude [s390x] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: haskell-natural-transformation [ppc64el] (artful-proposed/none) [0.4-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: haskell-lazy-csv [ppc64el] (artful-proposed/none) [0.5.1-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: haskell-lazy-csv [s390x] (artful-proposed/none) [0.5.1-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: haskell-permutation [ppc64el] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: knot [s390x] (artful-proposed/universe) [2.5.1-4] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: haskell-multiset-comb [s390x] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: haskell-xmlgen [ppc64el] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: haskell-permutation [s390x] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: knot [ppc64el] (artful-proposed/universe) [2.5.1-4] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: haskell-xmlgen [s390x] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:18] -queuebot:#ubuntu-release- New binary: haskell-natural-transformation [s390x] (artful-proposed/none) [0.4-1] (no packageset)
[11:18] -queuebot:#ubuntu-release- New binary: setuptools-scm [amd64] (artful-proposed/universe) [1.15.6-1] (no packageset)
[11:18] -queuebot:#ubuntu-release- New binary: hfst-ospell [arm64] (artful-proposed/universe) [0.4.5~r343-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- New binary: golang-github-chaseadamsio-goorgeous [amd64] (artful-proposed/none) [0.0~git20170427.0.677defd-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- New binary: hfst-ospell [armhf] (artful-proposed/universe) [0.4.5~r343-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- New binary: golang-github-jlaffaye-ftp [amd64] (artful-proposed/none) [0.0~git20170707.0.a05056b-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- New binary: xandikos [amd64] (artful-proposed/universe) [0.0.6-1] (no packageset)
[11:20] -queuebot:#ubuntu-release- New binary: golang-github-gorilla-rpc [amd64] (artful-proposed/none) [0.0~git20160927.0.22c016f-1] (no packageset)
[11:20] -queuebot:#ubuntu-release- New binary: golang-github-oneofone-xxhash [amd64] (artful-proposed/none) [1.2+git20161215.1.5d8fefa-1] (no packageset)
[11:20] -queuebot:#ubuntu-release- New binary: golang-github-xiaq-persistent [amd64] (artful-proposed/none) [0.0~git20170614.0.06adb7b-1] (no packageset)
[11:20] -queuebot:#ubuntu-release- New binary: golang-github-manyminds-api2go [amd64] (artful-proposed/none) [1.0-RC2+git20161229.31.dc368bb-1] (no packageset)
[11:20] -queuebot:#ubuntu-release- New binary: golang-github-xanzy-ssh-agent [amd64] (artful-proposed/none) [0.0~git20151215.0.ba9c9e3-1] (no packageset)
[11:21] -queuebot:#ubuntu-release- New binary: libbtbb [amd64] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[11:21] -queuebot:#ubuntu-release- New binary: libbtbb [i386] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[11:22] -queuebot:#ubuntu-release- New binary: golang-github-minio-dsync [amd64] (artful-proposed/none) [0.0~git20170209.0.b9f7da7-1] (no packageset)
[11:23] -queuebot:#ubuntu-release- New binary: haskell-lazy-csv [i386] (artful-proposed/none) [0.5.1-1] (no packageset)
[11:23] -queuebot:#ubuntu-release- New binary: haskell-multiset-comb [i386] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: haskell-base-prelude [amd64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: haskell-lazy-csv [amd64] (artful-proposed/none) [0.5.1-1] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: haskell-permutation [i386] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: haskell-base-prelude [i386] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: knot [amd64] (artful-proposed/universe) [2.5.1-4] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: haskell-permutation [amd64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:24] -queuebot:#ubuntu-release- New binary: haskell-natural-transformation [i386] (artful-proposed/none) [0.4-1] (no packageset)
[11:25] -queuebot:#ubuntu-release- New binary: haskell-natural-transformation [amd64] (artful-proposed/none) [0.4-1] (no packageset)
[11:25] -queuebot:#ubuntu-release- New binary: knot [i386] (artful-proposed/universe) [2.5.1-4] (no packageset)
[11:25] -queuebot:#ubuntu-release- New binary: haskell-xmlgen [i386] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:26] -queuebot:#ubuntu-release- New binary: haskell-multiset-comb [amd64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:26] -queuebot:#ubuntu-release- New binary: haskell-xmlgen [amd64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:28] -queuebot:#ubuntu-release- New binary: libbtbb [armhf] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[11:31] -queuebot:#ubuntu-release- New binary: eso-midas [amd64] (artful-proposed/universe) [17.02pl1.2-2] (no packageset)
[11:31] -queuebot:#ubuntu-release- New binary: libbtbb [arm64] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[11:35] -queuebot:#ubuntu-release- New binary: haskell-base-prelude [arm64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:35] -queuebot:#ubuntu-release- New binary: qgis [ppc64el] (artful-proposed/universe) [2.14.16+dfsg-1] (no packageset)
[11:35] -queuebot:#ubuntu-release- New binary: haskell-base-prelude [armhf] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:36] -queuebot:#ubuntu-release- New binary: haskell-multiset-comb [arm64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:36] -queuebot:#ubuntu-release- New binary: haskell-natural-transformation [arm64] (artful-proposed/none) [0.4-1] (no packageset)
[11:37] -queuebot:#ubuntu-release- New binary: haskell-lazy-csv [arm64] (artful-proposed/none) [0.5.1-1] (no packageset)
[11:37] -queuebot:#ubuntu-release- New binary: haskell-natural-transformation [armhf] (artful-proposed/none) [0.4-1] (no packageset)
[11:38] -queuebot:#ubuntu-release- New binary: knot [armhf] (artful-proposed/universe) [2.5.1-4] (no packageset)
[11:38] -queuebot:#ubuntu-release- New binary: node-http-signature [amd64] (artful-proposed/universe) [1.1.1-1] (no packageset)
[11:39] -queuebot:#ubuntu-release- New binary: haskell-multiset-comb [armhf] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:41] -queuebot:#ubuntu-release- New binary: haskell-permutation [armhf] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:42] -queuebot:#ubuntu-release- New binary: haskell-lazy-csv [armhf] (artful-proposed/none) [0.5.1-1] (no packageset)
[11:43] -queuebot:#ubuntu-release- New binary: knot [arm64] (artful-proposed/universe) [2.5.1-4] (no packageset)
[11:44] -queuebot:#ubuntu-release- New binary: haskell-xmlgen [armhf] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:45] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-86.109] (core, kernel)
[11:47] -queuebot:#ubuntu-release- New binary: haskell-permutation [arm64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[11:47] -queuebot:#ubuntu-release- New binary: haskell-xmlgen [arm64] (artful-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[12:01] -queuebot:#ubuntu-release- New binary: qgis [s390x] (artful-proposed/universe) [2.14.16+dfsg-1] (no packageset)
[12:03] <teward> is there a way to access the environment where an autopkgtest ran and failed?
[12:03] <teward> because i'm seeing error log information from systemctl in the failed build here<EMAIL_ADDRESS>- but it's ellipsized so it's not useful.
[12:03] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-86.109]
[12:09] -queuebot:#ubuntu-release- New binary: qgis [amd64] (artful-proposed/universe) [2.14.16+dfsg-1] (no packageset)
[12:19] -queuebot:#ubuntu-release- New: accepted eso-midas [amd64] (artful-proposed) [17.02pl1.2-2]
[12:19] -queuebot:#ubuntu-release- New: accepted golang-etcd [amd64] (artful-proposed) [2.0.0-3]
[12:19] -queuebot:#ubuntu-release- New binary: openmama [s390x] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[12:19] -queuebot:#ubuntu-release- New: accepted gexiv2 [amd64] (artful-proposed) [0.10.6-1]
[12:19] -queuebot:#ubuntu-release- New binary: openmama [ppc64el] (artful-proposed/universe) [<IP_ADDRESS>-11.1ubuntu1] (no packageset)
[12:20] -queuebot:#ubuntu-release- New: accepted golang-github-chaseadamsio-goorgeous [amd64] (artful-proposed) [0.0~git20170427.0.677defd-1]
[12:20] -queuebot:#ubuntu-release- New: accepted golang-github-jlaffaye-ftp [amd64] (artful-proposed) [0.0~git20170707.0.a05056b-1]
[12:20] -queuebot:#ubuntu-release- New: accepted golang-github-minio-dsync [amd64] (artful-proposed) [0.0~git20170209.0.b9f7da7-1]
[12:20] -queuebot:#ubuntu-release- New: accepted golang-github-xanzy-ssh-agent [amd64] (artful-proposed) [0.0~git20151215.0.ba9c9e3-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-base-prelude [amd64] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-base-prelude [armhf] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-base-prelude [ppc64el] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-lazy-csv [amd64] (artful-proposed) [0.5.1-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-lazy-csv [armhf] (artful-proposed) [0.5.1-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-lazy-csv [ppc64el] (artful-proposed) [0.5.1-1]
[12:20] -queuebot:#ubuntu-release- New: accepted golang-github-gorilla-rpc [amd64] (artful-proposed) [0.0~git20160927.0.22c016f-1]
[12:20] -queuebot:#ubuntu-release- New: accepted golang-github-oneofone-xxhash [amd64] (artful-proposed) [1.2+git20161215.1.5d8fefa-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-base-prelude [arm64] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-base-prelude [s390x] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-lazy-csv [i386] (artful-proposed) [0.5.1-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-multiset-comb [amd64] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-multiset-comb [armhf] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-multiset-comb [ppc64el] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New binary: cg3 [amd64] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[12:20] -queuebot:#ubuntu-release- New binary: cg3 [i386] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[12:20] -queuebot:#ubuntu-release- New: accepted golang-github-manyminds-api2go [amd64] (artful-proposed) [1.0-RC2+git20161229.31.dc368bb-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-base-prelude [i386] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-lazy-csv [s390x] (artful-proposed) [0.5.1-1]
[12:20] -queuebot:#ubuntu-release- New: accepted haskell-multiset-comb [i386] (artful-proposed) [<IP_ADDRESS>-1]
[12:20] -queuebot:#ubuntu-release- New binary: cg3 [armhf] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[12:20] -queuebot:#ubuntu-release- New binary: cg3 [s390x] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[12:20] -queuebot:#ubuntu-release- New binary: sane-backends [armhf] (artful-proposed/main) [1.0.27-1~experimental1ubuntu1~artful1] (desktop-core, ubuntu-server)
[12:20] -queuebot:#ubuntu-release- New source: unity-mail (artful-proposed/primary) [<IP_ADDRESS>]
[12:21] -queuebot:#ubuntu-release- New: accepted golang-github-xiaq-persistent [amd64] (artful-proposed) [0.0~git20170614.0.06adb7b-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-multiset-comb [arm64] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New binary: cg3 [ppc64el] (artful-proposed/universe) [1.0.0~r12254-1ubuntu1] (no packageset)
[12:21] -queuebot:#ubuntu-release- New binary: sane-backends [i386] (artful-proposed/main) [1.0.27-1~experimental1ubuntu1~artful1] (desktop-core, ubuntu-server)
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-lazy-csv [arm64] (artful-proposed) [0.5.1-1]
[12:21] -queuebot:#ubuntu-release- New binary: sane-backends [amd64] (artful-proposed/main) [1.0.27-1~experimental1ubuntu1~artful1] (desktop-core, ubuntu-server)
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-multiset-comb [s390x] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-natural-transformation [arm64] (artful-proposed) [0.4-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-natural-transformation [i386] (artful-proposed) [0.4-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-natural-transformation [s390x] (artful-proposed) [0.4-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-permutation [arm64] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-permutation [i386] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-permutation [s390x] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-xmlgen [arm64] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-xmlgen [i386] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-xmlgen [s390x] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-natural-transformation [amd64] (artful-proposed) [0.4-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-natural-transformation [ppc64el] (artful-proposed) [0.4-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-permutation [armhf] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-xmlgen [amd64] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-xmlgen [ppc64el] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-natural-transformation [armhf] (artful-proposed) [0.4-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-permutation [ppc64el] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted hfst-ospell [armhf] (artful-proposed) [0.4.5~r343-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-permutation [amd64] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted haskell-xmlgen [armhf] (artful-proposed) [<IP_ADDRESS>-1]
[12:21] -queuebot:#ubuntu-release- New: accepted hfst-ospell [amd64] (artful-proposed) [0.4.5~r343-1]
[12:21] -queuebot:#ubuntu-release- New: accepted hfst-ospell [i386] (artful-proposed) [0.4.5~r343-1]
[12:21] -queuebot:#ubuntu-release- New: accepted hfst-ospell [s390x] (artful-proposed) [0.4.5~r343-1]
[12:21] -queuebot:#ubuntu-release- New: accepted hfst-ospell [arm64] (artful-proposed) [0.4.5~r343-1]
[12:21] -queuebot:#ubuntu-release- New: accepted hfst-ospell [ppc64el] (artful-proposed) [0.4.5~r343-1]
[12:23] -queuebot:#ubuntu-release- New: accepted knot [amd64] (artful-proposed) [2.5.1-4]
[12:23] -queuebot:#ubuntu-release- New: accepted knot [armhf] (artful-proposed) [2.5.1-4]
[12:23] -queuebot:#ubuntu-release- New: accepted knot [ppc64el] (artful-proposed) [2.5.1-4]
[12:23] -queuebot:#ubuntu-release- New: accepted libbtbb [arm64] (artful-proposed) [2017.03.R2-1]
[12:23] -queuebot:#ubuntu-release- New: accepted knot [arm64] (artful-proposed) [2.5.1-4]
[12:23] -queuebot:#ubuntu-release- New: accepted knot [s390x] (artful-proposed) [2.5.1-4]
[12:23] -queuebot:#ubuntu-release- New: accepted knot [i386] (artful-proposed) [2.5.1-4]
[12:23] -queuebot:#ubuntu-release- New: accepted libbtbb [armhf] (artful-proposed) [2017.03.R2-1]
[12:23] -queuebot:#ubuntu-release- New: accepted libbtbb [amd64] (artful-proposed) [2017.03.R2-1]
[12:23] -queuebot:#ubuntu-release- New: accepted libbtbb [ppc64el] (artful-proposed) [2017.03.R2-1]
[12:23] -queuebot:#ubuntu-release- New: accepted node-http-signature [amd64] (artful-proposed) [1.1.1-1]
[12:23] -queuebot:#ubuntu-release- New: accepted qgis [s390x] (artful-proposed) [2.14.16+dfsg-1]
[12:23] -queuebot:#ubuntu-release- New: accepted xandikos [amd64] (artful-proposed) [0.0.6-1]
[12:23] -queuebot:#ubuntu-release- New: accepted libbtbb [i386] (artful-proposed) [2017.03.R2-1]
[12:23] -queuebot:#ubuntu-release- New: accepted qgis [ppc64el] (artful-proposed) [2.14.16+dfsg-1]
[12:23] -queuebot:#ubuntu-release- New: accepted libbtbb [s390x] (artful-proposed) [2017.03.R2-1]
[12:23] -queuebot:#ubuntu-release- New: accepted setuptools-scm [amd64] (artful-proposed) [1.15.6-1]
[12:30] -queuebot:#ubuntu-release- New binary: qgis [i386] (artful-proposed/universe) [2.14.16+dfsg-1] (no packageset)
[12:34] -queuebot:#ubuntu-release- New binary: qgis [arm64] (artful-proposed/universe) [2.14.16+dfsg-1] (no packageset)
[12:52] <LocutusOfBorg> apw, please reject openmama :)
[12:53] <LocutusOfBorg> or I can upload an ubuntu2 with no new queue
[12:53] -queuebot:#ubuntu-release- New binary: qgis [armhf] (artful-proposed/universe) [2.14.16+dfsg-1] (no packageset)
[12:53] <tsimonq2> LocutusOfBorg: But why?
[12:54] <LocutusOfBorg> nvm, it is good
[12:54] <LocutusOfBorg> I did look at the diff and it was somewhat scary, I thought about a mistake on my process
[12:54] <tsimonq2> LocutusOfBorg: Nope :)
[12:54] <LocutusOfBorg> you are right, apw, please forget
[12:55] <LocutusOfBorg> so you are trying to go in sync with that one, instead of keeping the rename
[12:56] -queuebot:#ubuntu-release- New: accepted qgis [amd64] (artful-proposed) [2.14.16+dfsg-1]
[12:56] -queuebot:#ubuntu-release- New: accepted qgis [armhf] (artful-proposed) [2.14.16+dfsg-1]
[12:56] -queuebot:#ubuntu-release- New: accepted qgis [arm64] (artful-proposed) [2.14.16+dfsg-1]
[12:56] -queuebot:#ubuntu-release- New: accepted qgis [i386] (artful-proposed) [2.14.16+dfsg-1]
[13:49] -queuebot:#ubuntu-release- New binary: ubertooth [ppc64el] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[13:50] -queuebot:#ubuntu-release- New binary: golang-github-cespare-xxhash [amd64] (artful-proposed/universe) [0.0~git20170604.0.1b6d2e4-1] (no packageset)
[13:50] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-86.109~14.04.1] (kernel)
[13:51] -queuebot:#ubuntu-release- New binary: ubertooth [i386] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[13:52] -queuebot:#ubuntu-release- New binary: ubertooth [s390x] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[13:53] -queuebot:#ubuntu-release- New binary: ubertooth [amd64] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[13:53] -queuebot:#ubuntu-release- New binary: ubertooth [armhf] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[13:53] -queuebot:#ubuntu-release- New binary: ubertooth [arm64] (artful-proposed/universe) [2017.03.R2-1] (no packageset)
[14:04] <LocutusOfBorg> infinity, how to you feel about removing openscenegraph on armhf? it fails to build because of missing gles stuff, and I honestly don't think the effort for enabling it qt side is worth something
[14:05] <LocutusOfBorg> IIRC you already removed some armhf gles-related failures a while ago
[14:06] -queuebot:#ubuntu-release- New: accepted golang-github-cespare-xxhash [amd64] (artful-proposed) [0.0~git20170604.0.1b6d2e4-1]
[14:06] -queuebot:#ubuntu-release- New: accepted ubertooth [amd64] (artful-proposed) [2017.03.R2-1]
[14:06] -queuebot:#ubuntu-release- New: accepted ubertooth [armhf] (artful-proposed) [2017.03.R2-1]
[14:06] -queuebot:#ubuntu-release- New: accepted ubertooth [ppc64el] (artful-proposed) [2017.03.R2-1]
[14:07] -queuebot:#ubuntu-release- New: accepted ubertooth [arm64] (artful-proposed) [2017.03.R2-1]
[14:07] -queuebot:#ubuntu-release- New: accepted ubertooth [s390x] (artful-proposed) [2017.03.R2-1]
[14:07] -queuebot:#ubuntu-release- New: accepted ubertooth [i386] (artful-proposed) [2017.03.R2-1]
[16:45] -queuebot:#ubuntu-release- Unapproved: miral (zesty-proposed/main) [1.3.2+17.04.20170330.5-0ubuntu1 => 1.3.3+17.04.20170714.1-0ubuntu1] (ubuntu-desktop) (sync)
[16:47] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-86.109~14.04.1]
[17:01] -queuebot:#ubuntu-release- Unapproved: accepted variety [source] (xenial-proposed) [0.6.0-1ubuntu2]
[19:33] -queuebot:#ubuntu-release- Unapproved: grub2 (trusty-proposed/main) [2.02~beta2-9ubuntu1.12 => 2.02~beta2-9ubuntu1.14] (core)
[19:40] -queuebot:#ubuntu-release- Unapproved: grub2-signed (trusty-proposed/main) [1.34.14 => 1.34.16] (core)
[19:56] <xnox> launchpad is busy, i guess i will not manage to finish ocaml transition today
[23:10] -queuebot:#ubuntu-release- New binary: radvd [amd64] (artful-proposed/main) [1:2.16-3] (ubuntu-server)
[23:12] -queuebot:#ubuntu-release- New binary: radvd [i386] (artful-proposed/main) [1:2.16-3] (ubuntu-server)
[23:12] -queuebot:#ubuntu-release- New binary: radvd [s390x] (artful-proposed/main) [1:2.16-3] (ubuntu-server)
[23:14] -queuebot:#ubuntu-release- New binary: libetpan [s390x] (artful-proposed/universe) [1.8.0-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: radvd [ppc64el] (artful-proposed/main) [1:2.16-3] (ubuntu-server)
[23:14] -queuebot:#ubuntu-release- New binary: libtgvoip [ppc64el] (artful-proposed/universe) [1.0~git20170704.445433f-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: libtgvoip [s390x] (artful-proposed/universe) [1.0~git20170704.445433f-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: libetpan [ppc64el] (artful-proposed/universe) [1.8.0-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: kpmcore [ppc64el] (artful-proposed/universe) [3.1.2-1] (kubuntu)
[23:16] -queuebot:#ubuntu-release- New binary: radvd [arm64] (artful-proposed/main) [1:2.16-3] (ubuntu-server)
[23:16] -queuebot:#ubuntu-release- New binary: haskell-cabal-doctest [ppc64el] (artful-proposed/universe) [1.0.2-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: haskell-weigh [s390x] (artful-proposed/universe) [0.0.4-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: haskell-neat-interpolation [ppc64el] (artful-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: haskell-neat-interpolation [s390x] (artful-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: haskell-weigh [ppc64el] (artful-proposed/universe) [0.0.4-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: haskell-cabal-doctest [s390x] (artful-proposed/universe) [1.0.2-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: libtgvoip [i386] (artful-proposed/universe) [1.0~git20170704.445433f-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: kpmcore [s390x] (artful-proposed/universe) [3.1.2-1] (kubuntu)
[23:18] -queuebot:#ubuntu-release- New binary: libetpan [i386] (artful-proposed/universe) [1.8.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: radvd [armhf] (artful-proposed/main) [1:2.16-3] (ubuntu-server)
[23:18] -queuebot:#ubuntu-release- New binary: libtgvoip [amd64] (artful-proposed/universe) [1.0~git20170704.445433f-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: liburcu [i386] (artful-proposed/main) [0.10.0-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[23:18] -queuebot:#ubuntu-release- New binary: movit [s390x] (artful-proposed/universe) [1.5.2-1] (kubuntu)
[23:19] -queuebot:#ubuntu-release- New binary: etherape [amd64] (artful-proposed/universe) [0.9.15-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: libetpan [amd64] (artful-proposed/universe) [1.8.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: kpmcore [amd64] (artful-proposed/universe) [3.1.2-1] (kubuntu)
[23:19] -queuebot:#ubuntu-release- New binary: liburcu [amd64] (artful-proposed/main) [0.10.0-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[23:19] -queuebot:#ubuntu-release- New binary: ros-catkin-pkg [amd64] (artful-proposed/universe) [0.3.5-3] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: kpmcore [i386] (artful-proposed/universe) [3.1.2-1] (kubuntu)
[23:20] -queuebot:#ubuntu-release- New binary: movit [ppc64el] (artful-proposed/universe) [1.5.2-1] (kubuntu)
[23:20] -queuebot:#ubuntu-release- New binary: liburcu [ppc64el] (artful-proposed/main) [0.10.0-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[23:20] -queuebot:#ubuntu-release- New binary: node-browserify-cipher [amd64] (artful-proposed/universe) [1.0.0-2] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: node-browserify-sign [amd64] (artful-proposed/universe) [4.0.4-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: haskell-cabal-doctest [amd64] (artful-proposed/universe) [1.0.2-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: haskell-cabal-doctest [i386] (artful-proposed/universe) [1.0.2-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: haskell-neat-interpolation [amd64] (artful-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: mumps [s390x] (artful-proposed/universe) [5.1.1-2] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: haskell-weigh [i386] (artful-proposed/universe) [0.0.4-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: node-public-encrypt [amd64] (artful-proposed/universe) [4.0.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: liburcu [s390x] (artful-proposed/main) [0.10.0-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[23:24] -queuebot:#ubuntu-release- New binary: haskell-neat-interpolation [i386] (artful-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: liburcu [arm64] (artful-proposed/main) [0.10.0-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[23:24] -queuebot:#ubuntu-release- New binary: movit [i386] (artful-proposed/universe) [1.5.2-1] (kubuntu)
[23:24] -queuebot:#ubuntu-release- New binary: haskell-weigh [amd64] (artful-proposed/universe) [0.0.4-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: movit [amd64] (artful-proposed/universe) [1.5.2-1] (kubuntu)
[23:25] -queuebot:#ubuntu-release- New binary: mumps [ppc64el] (artful-proposed/universe) [5.1.1-2] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: liburcu [armhf] (artful-proposed/main) [0.10.0-2] (kubuntu, ubuntu-desktop, ubuntu-server)
[23:28] -queuebot:#ubuntu-release- New binary: gnuastro [i386] (artful-proposed/universe) [0.3.23-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: gnuastro [amd64] (artful-proposed/universe) [0.3.23-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: mumps [amd64] (artful-proposed/universe) [5.1.1-2] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: mumps [i386] (artful-proposed/universe) [5.1.1-2] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: libtgvoip [arm64] (artful-proposed/universe) [1.0~git20170704.445433f-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: ruby-gnome2 [amd64] (artful-proposed/universe) [3.1.6-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: libetpan [arm64] (artful-proposed/universe) [1.8.0-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: libtgvoip [armhf] (artful-proposed/universe) [1.0~git20170704.445433f-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: libetpan [armhf] (artful-proposed/universe) [1.8.0-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: kpmcore [armhf] (artful-proposed/universe) [3.1.2-1] (kubuntu)
[23:43] -queuebot:#ubuntu-release- New binary: haskell-cabal-doctest [arm64] (artful-proposed/universe) [1.0.2-1] (no packageset)
[23:44] -queuebot:#ubuntu-release- New binary: haskell-weigh [armhf] (artful-proposed/universe) [0.0.4-1] (no packageset)
[23:45] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (zesty-proposed/main) [1:17.04.8 => 1:17.04.9] (core)
[23:45] -queuebot:#ubuntu-release- New binary: haskell-cabal-doctest [armhf] (artful-proposed/universe) [1.0.2-1] (no packageset)
[23:45] -queuebot:#ubuntu-release- New binary: haskell-weigh [arm64] (artful-proposed/universe) [0.0.4-1] (no packageset)
[23:46] -queuebot:#ubuntu-release- New binary: haskell-neat-interpolation [armhf] (artful-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[23:46] -queuebot:#ubuntu-release- New binary: kpmcore [arm64] (artful-proposed/universe) [3.1.2-1] (kubuntu)
[23:47] -queuebot:#ubuntu-release- New binary: haskell-neat-interpolation [arm64] (artful-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[23:49] -queuebot:#ubuntu-release- New binary: movit [armhf] (artful-proposed/universe) [1.5.2-1] (kubuntu)
[23:54] -queuebot:#ubuntu-release- New binary: movit [arm64] (artful-proposed/universe) [1.5.2-1] (kubuntu)