[11:44] <Furao> is there anyway to ask d-i to no fill the console with progress bar and stuff? I want to see in the console the output of each commands
[12:00] <cjwatson> DEBIAN_FRONTEND=text
[12:01] <cjwatson> Or you could just switch to tty4
[12:03] <Furao> I don't have a frame buffer, only a serial console
[12:03] <Furao> thanks I'll try
[12:04] <cjwatson> I'd expect it to use the text frontend on sercon anyway
[12:04] <cjwatson> maybe you don't mean the full-screen progress bar?
[12:05] <cjwatson> actually thinking about it output may well be directed to the logs regardless
[12:05] <cjwatson> you might be better off using remote syslog and watching the log on your remote server
[12:09] <Furao> I'm still lucid, and remote syslog never worked
[12:09] <Furao> but I'm trying and I think I'll be able to get what I need
[12:09] <Furao> I just need to have the MAC address of the eth0 at the end of the installation
[12:28] <Furao> and no luck like you said, it all ends in the logs
[12:28] <Furao> there should be a log frontend :)
[12:49] <Furao> f*ck stdout: /bin/ip link > /dev/console
[12:49] <Furao> that work :)
[15:54] <cjwatson> xnox: is bug 1009973 still required in the quantal release notes, or was that just for precise?
[15:54] <ubot2> Launchpad bug 1009973 in mdadm "SRU upstream bugfix micro point release 3.2.5" [Wishlist,Fix released] https://launchpad.net/bugs/1009973
[15:56] <xnox> cjwatson: no, that was just precise.
[15:56] <cjwatson> xnox: OK, adjusting metadata accordingly
[15:57] <xnox> cjwatson: imho it's done and dusted, as it did make it into 12.04.1
[15:58] <xnox> not sure what the release notes task was for at all tbh.
[15:58] <cjwatson> Dunno.  Feel free to clean up :)


[03:56] <micahg> for the hugday,are we opening upstream tasks for the bugs?
[03:57] <micahg> joshuahoover: ^^
[12:36] <kamusin> :)
[15:30] <arand> I have an interesting "bug" where a fsck, on a messy unbootable / ext4, moved _everything_ to lost+found, how would I best go about reporting this?
[15:38] <dholbach> final day of https://wiki.ubuntu.com/UbuntuDeveloperWeek starting in 22 minutes in #ubuntu-classroom on irc.freenode.net (first up: "Writing Beautiful Code")
[15:46] <LimCore> hello
[15:47] <LimCore> Im founding still this OpenPGP bugs in kmail.
[15:48]  * kyubutsu notes: ubuntudeveloperweek. 20 minutes: start topic 'writing beautiful code'
[15:49] <BUGabundo_remote> LimCore: bugs as in: IT DOESN'T FREAKING work ?
[15:49] <LimCore> bug as in https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/514338
[15:49] <ubot4> LimCore: Error: This bug is private
[15:49] <LimCore> public now
[15:50] <jpds> LimCore: Report it to kmail upstream at bugs.kde.org
[15:53] <kyubutsu> kmail doesnt want to read gpg key here..  at least its listed in kgpg but i still had to use terminal to import my key
[15:53] <LimCore> kyubutsu: hmm. perhaps comment my bug the please
[15:54] <kyubutsu> it might be a different bug though, havent debugged it really
[15:57] <LimCore> also gnome panel is buggy
[15:57] <LimCore> it attempts to statart programs like firefoxfox
[15:57] <LimCore> which is really annoyingng
[17:07] <duanedesign> could someone set a bug to wishlist please. bug 505632
[17:07] <ubot4> Launchpad bug 505632 in couchdb-glib "Add support for views" [Undecided,New] https://launchpad.net/bugs/505632
[17:13] <vish> duanedesign: that is not an Ubuntu bug... :) its couch-glib upstream bug
[17:14] <vish> couchdb-glib*
[17:15] <vish> only the maintainers can set the importance for that
[17:21] <kklimonda> good evening :)
[17:22] <BUGabundo_remote> hey buddy
[17:23] <om26er> If a bug was reported against old netbook launcher( about its interface) and now that bug don't apply. so should it be marked invalid or won't fix?
[17:24] <charlie-tca> invalid, if it doesn't apply to anything now
[17:24] <om26er> charlie-tca, thank you
[17:24] <charlie-tca> with comments about why
[17:25] <om26er> charlie-tca, if it was marked medium should I also change it to undecided?
[17:26] <charlie-tca> not needed to change importance
[17:26] <om26er> ok
[17:26] <charlie-tca> You can just change status.
[17:27] <vish> charlie-tca: wouldnt that be needed for the older release? [but if om26er had quoted the bug it would have been better to judge ;) ]
[17:28] <charlie-tca> Wouldn't what be needed?
[17:28] <vish> charlie-tca: if the bug was reported about the old netbook launcher.. wouldnt it be valid for the older release
[17:29] <charlie-tca> Depends on what release, and whether or not the launcher is still usable. , thus the "if it doesn't apply to anything now"
[17:30] <vish> yeah , depends.. om26er usually  asks without mentioning bug.. [mysterious fella ;)]
[17:31] <charlie-tca> heh
[17:31] <om26er> vish, https://bugs.launchpad.net/ubuntu/+source/netbook-launcher/+bug/267448
[17:31] <ubot4> Launchpad bug 267448 in netbook-launcher "Home folder in the right sidebar should sit just above Places folders (Documents, Music etc.)" [Medium,Invalid]
[17:33] <vish> meh.. that is a very old bug :s
[17:35] <om26er> vish, so its fine ?
[17:36] <vish> om26er: i guess so , it was an old suggestion
[17:46] <duanedesign> vish: ahh, thank you for pointing that out. Me thinks i need another cup of coffee. :)
[18:06] <bcurtiswx> om26er: if i haven't done so already.  Thanks for all the triage you do with empathy :D i just took 215 bug-mails down to 150 with your help
[18:07] <om26er> bcurtiswx, I am happy to help
[18:07] <bcurtiswx> thats supposed to say 275.. not 215.. lol
[18:08] <hggdh> it was still a nice number
[18:12] <mrand> very nice.  great job om26er!
[18:13] <om26er> mrand, thanks :)
[18:17] <bcurtiswx> om26er: is there a PPA for empathy to test in karmic?
[18:17] <arand_> I have an interesting "bug" where a fsck, on a messy unbootable / ext4, moved _everything_ to lost+found, how would I best go about reporting this?
[18:17] <om26er> bcurtiswx, yes.
[18:18] <bcurtiswx> om26er: and that is?
[18:18] <om26er> bcurtiswx, it has empathy 2.29.5
[18:19] <om26er> bcurtiswx, i think I gave it to someone as I thought It had empathy 2.29.6
[18:20] <hggdh> arand_: probably to the kernel, linux
[18:20] <bcurtiswx> om26er: yeah I imagine they would update it to 2.29.6 if it was just released
[18:21] <om26er> they updated the ppa to 2.29.6 for lucid only
[18:22] <om26er> https://launchpad.net/~telepathy/+archive/ppa
[18:22] <arand_> hggdh: Yea, is there any info I would be able to extract from the kaputt filesystem or is it just kernel/ubuntu version, harddisk make, and that's it?
[18:23] <hggdh> better to run ubuntu-bug linux -- it will get all basic data for the kernel. Then make sure the fsck errors are in the uploaded data
[18:23] <hggdh> arand_: ^
[18:25] <arand_> hggdh: the filesystem where all those data would be is gone, it is one big 5GB lost+found dir, nothing more. To run ubuntu-bug on correct kernel version I would have to fresh-install.
[18:26] <hggdh> arand_: you reinstalled ubuntu after the error?
[18:27] <arand_> hggdh: no
[18:27] <hggdh> in other words -- what you lost was root, and everything was under root?
[18:30] <arand_> I had one ext4 partition that was "/" after errors and a fsck it is now a 5GB lost+found directory.
[18:31] <hggdh> OK. So you lost all logs, correct?
[18:32] <arand_> hggdh: yes (along with everything),  unless there is some way to find them in lost+found,
[18:33] <hggdh> do you at least remeber what linux version you were running (full version string, down to the end)?
[18:33] <arand_> Yes, was the latest for jaunty, -17
[18:34] <hggdh> OK. Open a bug on Linux, state what happened, and the Linux version. Make sure you state you still have the lost+found with 5G of recovered files
[18:35] <hggdh> arand_: I am sure there are some forensic tools available to parse the lost+found mess. Worst scenario is you can grep for some string you know will be in a certain type of file, and recover them this way
[18:35] <hggdh> Now I have to get to the airport, sorry
[18:35] <arand_> hggdh: Ok, will do, wanted to see if there was anything I could do to make the report more helpful.
[18:36] <hggdh> not really, except combing the l+f for logs
[18:42] <bcurtiswx> om26er: instead of saying "do you face this", it's probably better to say "We are wondering if you have faced this issue anymore?"
[18:43] <om26er> bcurtiswx, ok sure
[19:27] <kamusin> Can anyone help me to reproduce this bug 494400 please
[19:27] <ubot4> Launchpad bug 494400 in gksu "Opening folder with nautilus-gksu change desktop wallpaper to root one" [Undecided,New] https://launchpad.net/bugs/494400
[19:37] <bcurtiswx> what package in launchpad is mission-control a part of
[19:37] <bcurtiswx> i can't find it
[19:54] <bcurtiswx> nvm
[19:57] <vish> charlie-tca: hmm , ..  papercuts is only for apps in the default install , just a task to track usability fixes/problems... there isnt anyone who is actually fixing the bugs[someone from community has to fix them eventually]
[20:19] <charlie-tca> which one is that?
[20:21] <vish> charlie-tca: i thought it was you, who added the papercuts task Bug 398509
[20:21] <ubot4> Launchpad bug 398509 in subcommander "html guide referenced in man page is not there" [Undecided,New] https://launchpad.net/bugs/398509
[20:22] <charlie-tca> That is usability (but I suppose, not in main)
[20:22] <charlie-tca> I did do that. I just can't remember those things anymore, even for 5-10 minutes
[20:23] <vish> lol ... but yeah , if not in main install it is not included
[20:23] <charlie-tca> Well.... I guess you should disapprove the papercut
[20:23] <charlie-tca> or you want me to?
[20:23] <vish> just wanted to mention it to you , you can do it too :)
[20:24] <charlie-tca> It just seems like such a simple thing, move docs from suggested to recommends
[20:24] <charlie-tca> done
[20:24] <vish> thanks..
[20:25] <vish> charlie-tca: we are lacking papercuts from xubuntu :(  .. you can nominate some bugs in the default which are design flaws
[20:25] <charlie-tca> Thank you for catching it
[20:25] <charlie-tca> ummm, all of xubuntu is universe
[20:26] <vish> well , if its in the default install and a design flaw it doesnt matter
[20:27] <charlie-tca> I will see if I can come up with any. Most of what we have is in the "hard to fix" category
[20:28] <vish> ;)
[20:28] <mr_pouit> (and patches should be reported upstream)
[20:29] <vish> mr_pouit: they are ... :)
[20:29] <mr_pouit> then that's fine
[21:35] <arand_> Just reported Bug #514498 , any pointers on improving the report (or logfiles to look for)?
[21:35] <ubot4> Launchpad bug 514498 in linux "whole filesystem lost to corruption " [Undecided,New] https://launchpad.net/bugs/514498
[22:43] <greg-g> so, should I unsubscribe from bugcontrol? :)
[23:03] <Incubuss> Anyone else not able to log into a guest session with Lucid (just left with a blank screen)?
[23:03] <Incubuss> More importantly, anyone else find that if they switch to a virtual terminal to kill X that everything you typed also went into wherever you last had focus? Such as pidign in my case...
[23:24] <yofel> Incubuss: you should ask that in #ubuntu+1
[23:25] <Incubuss> ah, thanks
[23:26] <Incubuss> not really too sure how to go about reporting it correctly, slight shocked since my login details (inc password) were sent to the person I was talking to previously...
[23:40] <BUGabundo> need package for keyboard repeat function in gnome
[23:40] <BUGabundo> its broken in lucid
[23:40] <BUGabundo> thanks
[23:45] <BUGabundo> FYI https://bugs.edge.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/514562
[23:45] <ubot4> Launchpad bug 514562 in gnome-settings-daemon "keyboard no longer repeats" [Undecided,New]


[05:57] <Kilos> hi superfly and others
[06:05] <kbmonkey> hello hello
[06:06] <kbmonkey> Kilos, I am eating big fat red grapes
[06:07] <Kilos> ooo yummy kbmonkey
[06:07] <Kilos> morning
[06:07] <superfly> morning Kilos and kbmonkey
[06:07] <kbmonkey> morning Kilos and superfly
[06:08] <Kilos> best way to enjoy grapes, much healthier than waiting for them to forment first
[06:08]  * superfly gets things ready for church
[06:08] <superfly> later folks
[06:08] <Kilos> pray for us please superfly
[06:08] <kbmonkey> later!
[06:08] <superfly> I'm always praying for you Kilos
[06:09] <Kilos> ty my friend
[08:36] <oupateddie> Goood morning
[08:36] <Kilos> hello oupateddie
[08:36] <Kilos> you have a good dance
[08:36] <oupateddie> Howzit on this Sunday morning?
[08:36] <Kilos> good ty and there?
[08:37] <oupateddie> Dance... not really as there were very few people, but the music was good.
[08:37] <Kilos> ah
[08:37] <oupateddie> The West Coast is overcast but humid, looks like a 28C today
[08:38] <Kilos> we 34°c today
[08:38] <oupateddie> Let me see if anybody is up to speed with Firefox 26.... and the blocking of JavaScript(s)
[08:38] <oupateddie> Ouch that's hot
[08:39] <Kilos> oh you dont want java
[08:39] <Kilos> i had to install it here to see some sites
[08:39] <Kilos> but i use opera browser
[08:39] <oupateddie> How do I "accept" javascript on FF26. It is showing me that Javascript is not active on the FF26.
[08:40] <oupateddie> I have Chrone and Opera but Opera is not so Joomla friendly when updating CMS Websites
[08:40] <Kilos> doesnt it give a popup for accept
[08:40] <oupateddie> And the nice part is that FF has an Afrikaans spell checker which I could not find in Chrome
[08:40] <oupateddie> Nope Kilos
[08:40] <Kilos> ah
[08:41] <Kilos> do you want to see the java stuff?
[08:41] <oupateddie> Well my Facebook page is all screwed as I cannot enter anything in the fields. It doesn't accept anything.
[08:42] <oupateddie> Also my google page is not displayed correctly
[08:42] <Kilos> sec im looking
[08:43] <oupateddie> That is on the laptop, but on the desktop it is OK
[08:44] <Kilos> sudo aptitude install oracle-java7-installer
[08:44] <Kilos> most stuff works with just openjdk
[08:45] <oupateddie> I'm not sure if openjdk is installed let me chack
[08:46] <Kilos> and sun-java-something or other
[08:46] <oupateddie> It seems as if opnjdk is not installed on the machine
[08:46] <Kilos> have you got synaptic?
[08:46] <oupateddie> must still do that on 13.04
[08:47] <oupateddie> its the laptop which played up yesterday
[08:47] <Kilos> whew
[08:47] <Kilos> so you now on 13.04
[08:47] <oupateddie> yeh on the laptop
[08:48] <oupateddie> on the desktop I cleaned up a l;ot with a magic prog ubuntu-tweak
[08:48] <Kilos> you shoulda gone with 13.10 i think 13.04 isnt supported anymore
[08:49] <Kilos> thats why im staying with 12.04. 3 years support is better than 6 months
[08:49] <oupateddie> I did not have 13.10 on a stick. Perhaps I mus download it and install it. In fact I do get updates for 13.04 regularly
[08:49] <oupateddie> Is 13.10 at all friendly as 12.04..
[08:49] <oupateddie> Also when is the next LTS coming
[08:50] <Kilos> you need to do some work to get extra workspaces and so on and it has lots of animated stuff i killed
[08:50] <Kilos> 14.04
[08:50] <oupateddie> On my main machine it is still 12.04
[08:51] <oupateddie> Rather stay as I am till 14.04
[08:51] <Kilos> if you got space to play, try 13.10 kubuntu
[08:51] <Kilos> very fast
[08:51] <Kilos> installs in 12 mins
[08:51] <oupateddie> What about Mint?
[08:51] <Kilos> i prefer kde
[08:52] <oupateddie> Never used it before
[08:52] <Kilos> they have worked on speed which was the main draw back
[08:52] <oupateddie> Will download an load onto another old machine standing garthering dust
[08:52] <oupateddie> *gathering
[08:52] <Kilos> took some getting used to but very lekker once you know the basics
[08:53] <oupateddie> where do I download the kubuntu iso
[08:53] <Kilos> Maaz, get ubuntu
[08:53] <Maaz> Kilos: 301 Moved Permanently to http://www.ubuntu.com/, which gets a 200 OK "The world's most popular free OS | Ubuntu"
[08:53] <Kilos> hmm...
[08:53] <oupateddie> My problemis that I have clients running Ubuntu 12 and 13 and I have to give support so I need machines to run on them
[08:53] <Kilos> Maaz, google kubuntu 13.10 iso download
[08:53] <Maaz> Kilos: "Kubuntu 13.10 (Saucy Salamander)" http://cdimage.ubuntu.com/kubuntu/releases/13.10/release/ :: "Kubuntu 14.04 (Trusty Tahr) Daily Build" http://cdimage.ubuntu.com/kubuntu/daily-live/current/ :: "Download Kubuntu | Kubuntu" http://www.kubuntu.org/getkubuntu :: "Kubuntu 13.10 | Kubuntu" http://www.kubuntu.org/news/kubuntu-13.10 :: "Download Kubuntu | Kubuntu"
[08:53] <Maaz> http://www.kubuntu.org/getkubuntu/download :: "Kubuntu | Friendly Computing" http://www.…
[08:56] <Kilos> oh you still on java thing too
[08:56] <oupateddie> Busy installing openjdk
[08:56] <oupateddie> Was not installed on the laptop
[08:57] <Kilos> here is the whole java thing
[08:57] <Kilos> https://launchpad.net/~webupd8team/+archive/java
[08:57] <Kilos> that opens anything using java
[08:58] <oupateddie> Stupid question for anybody... can I boot up more than one ubuntu one one machine at the same time. I have a ps with two hdd's each with a different version.
[08:58] <oupateddie> on* - one
[08:58] <Kilos> yes i have 3 drives that boot here
[08:59] <oupateddie> OK how do I  boot up the two disk as two "pc's " simultaneously
[08:59] <Kilos> 12.04 unity and 10.10 and kubuntu 12.04 on an external
[08:59] <Kilos> in one you type in sudo update-grub
[09:00] <Kilos> thats on your first bootable drive
[09:00] <oupateddie> OK I have update grub on the primary drive which brings up the grub menu
[09:00] <Kilos> then you will get the option which one to boot from
[09:00] <oupateddie> that's I get
[09:01] <Kilos> oh sorry man i misread your question
[09:01] <oupateddie> But is it possible to boot the primary as a machine and the secondary at the same time as a second machine
[09:01] <Kilos> i dont know
[09:02] <Kilos> dont think you can run 2 at once
[09:02] <oupateddie> This means that by "switching" between hdd's I can actually run two "workstations" simultaneously from one pc
[09:03] <Kilos> im lost with that
[09:03] <Kilos> if you find out how tell me too
[09:04] <oupateddie> well if you hear anything let me know. It might be possible if you run a virtual machine within the 1st instance similar to WINE for windows applic's
[09:04] <Kilos> oh you can run virtualbox
[09:04] <oupateddie> just thought of that now
[09:05] <Kilos> then install os of choice on there
[09:05] <oupateddie> that would mean your primaty machine would vbe your work machine and the virtual the other "play" disk
[09:05] <oupateddie> then I can run a 12.04, 13.04 and Kubuntu all at the same time no?
[09:06] <Kilos> virtualbox opens on your running drive
[09:06] <Kilos> dunno how to make it use a second drive
[09:07] <Kilos> ask that kinda question here tonight when the brains are here
[09:07] <oupateddie> worthwhile trying to get it done though
[09:07] <oupateddie> Do you know about crossover?
[09:07] <Kilos> nope
[09:08] <oupateddie> It is a codeweavers product to run windows under linux.
[09:08] <oupateddie> It basically allows you to run .exe.'s in linux without  wine
[09:13] <Kilos> eish i try keep any ms stuff away from here, apart from xp on first 20g to use up the bad sectors on this drive
[09:47] <Kilos> hi aquarat
[09:47] <Kilos> wb
[10:04] <confluency> CrossOver *is* Wine. It's a proprietary fork.
[10:04] <Kilos> oh ty confluency
[10:16] <kbmonkey> hallo
[10:16] <Kilos> hi kbmonkey
[10:17] <kbmonkey> you lurking lekker Kilos
[10:18] <Kilos> haha
[10:18] <Kilos> ive already done my bit today
[10:19] <kbmonkey> ya, some people have the strangest problems when they come from a windows environment
[10:20] <kbmonkey> mostly because they just dont stop to read the instructions :]
[10:21] <kbmonkey> but Kilos you must never tell anyone to rm -rf, that is looking for trouble. he he
[10:21] <kbmonkey> especially with sudo
[10:22] <Kilos> oh sorry. ive use it for stubborn stuff
[10:22] <Kilos> i said rm not rm -rf didnt i
[10:23] <Kilos> you must read the part this morning about running virtualbox on another drive
[10:23] <Kilos> im lost there
[10:24] <kbmonkey> no you didnt say rf, only sudo rm :]
[10:24] <kbmonkey> why should I read about virtualbox? I use qemu!
[10:24] <Kilos> i didnt know it was unsafe
[10:25] <Kilos> tell oupa then
[10:25] <Kilos> see what he wants to do
[10:26] <Kilos> if you help him lekker we can maybe push for some snoek
[10:26] <Kilos> email smoked snoek
[10:26] <kbmonkey> haha
[10:26] <kbmonkey> if you rm the wrong thing you can destroy your system files :(
[10:27] <Kilos> ai!
[10:29] <kbmonkey> ja I see oupa wants to run a virtual machiine using the hard disk instead of a image file
[10:29] <kbmonkey> I have not done that before myself
[10:29] <kbmonkey> but the virtualbox wiki has a tutorial on that as I recall
[10:30] <Kilos> good
[11:21] <charl> good afternoon
[11:21] <charl> Maaz: coffee on
[11:21]  * Maaz puts the kettle on
[11:24] <charl> oh my goodness, this is just plain brilliant http://i2.kym-cdn.com/photos/images/original/000/658/580/aca.jpg
[11:24] <Kilos> hi charl
[11:25] <charl> i love the south african way - problem - steal a solution
[11:25] <Maaz> Coffee's ready for charl!
[11:26] <charl> especially the belgian way - first start with a solution and end with a problem
[11:26] <charl> and the french way is also hilarious
[11:29] <charl> this is so true this one i am laughing tears of joy
[15:07] <Kilos> Maaz, coffee on
[15:07]  * Maaz washes some mugs
[15:08] <Kilos> you still here kbmonkey ? gonna rain
[15:08] <kbmonkey> yes, gonna rain here too. temp is dropping fast.
[15:09] <kbmonkey> Maaz, koffie asseblief
[15:09] <Maaz> Eish kbmonkey  Die engelse het tot ons boeretroos oorgeneem. Vra asseblief in engels.
[15:09] <kbmonkey> Maaz, coffee please
[15:09] <Maaz> kbmonkey: Sure
[15:11] <Maaz> Coffee's ready for Kilos and kbmonkey!
[15:11] <kbmonkey> yey koffie
[15:18] <Kilos> Maaz, danke
[15:18] <Maaz> Bitteschön
[15:19] <Kilos> we got boom booms here but most likely that is just gonna kill the power and rain somewhere else
[15:19] <Kilos> grrr
[15:20] <kbmonkey> eish
[16:39] <Kilos> hmm...
[16:45] <kbmonkey> agreed
[16:45] <Kilos> lol
[16:45] <Kilos> gonna be a small meet on the 23rd methinks
[16:46] <Kilos> oh ya kbmonkey you inna dog box
[16:46] <Kilos> you missed your own first open meet
[16:47] <Kilos> you lucky the pro hasnt sent the mafia after you yet'
[17:19] <Kilos> see now he hides
[17:22] <oupateddie> Evening all
[17:22] <Kilos> hi oupateddie
[17:22] <Kilos> wb
[17:22] <oupateddie> Kilos what is the syntax of that fix broken command you sent yesterday?
[17:23] <Kilos> the monkey said there is info on the wiki on using virtualbox to another drive
[17:23] <Kilos> umm
[17:23] <oupateddie> I'll check that out
[17:23] <Kilos> sudo apt-get --fixbroken i think it was
[17:24] <oupateddie> I'll see as I had it differently and it did not work
[17:24] <Kilos> lemme try find it again
[17:24] <Kilos> but also in synaptic there is a fix broken button
[17:26] <Kilos> sudo dpkg --configure -a
[17:26] <Kilos> sudo apt-get install -f
[17:28] <Kilos> ill have to hunt again. not sure where i have it saved
[17:30] <oupateddie> Not a problem
[17:30] <oupateddie> I found it in aptitude manual
[17:31] <Kilos> what is it?
[17:31] <Kilos> you must make a file to save all these commands
[17:32] <Kilos> i do but on different drives and places
[17:32] <Kilos> sigh
[17:33] <Kilos> but the synaptic you got to edit and then fix broken
[17:35] <oupateddie> I am trying to save all the command yes
[17:35] <oupateddie> I'm trying to collect all these now into one file
[17:36] <Kilos> what did you break now
[17:37] <Kilos> oh also there are man pges
[17:37] <Kilos> pages
[17:38] <Kilos> you type in mad apt or whatever program you looking for info on
[17:38] <Kilos> i battle to understand man though
[17:40] <oupateddie> I check with aptitude and these are a number of obsolete progs which I want to remove
[17:41] <oupateddie> My cousin's machine has broken packages and I'm trying to help him how to fix these.
[17:49] <Kilos> aha
[17:50] <Kilos> what error messages do you see?
[17:50] <oupateddie> No, I have left him to fight on by himself... If he needs more help I'll have a look.
[17:51] <Kilos> you can let him come here too you know
[17:51] <oupateddie> I have downloaded Kubuntu, want to see how it looks on the laptop.
[17:51] <Kilos> cool
[17:52] <Kilos> if you need help there ill need to swap drives
[17:53] <Kilos> button bottom left is the launcher
[17:53] <oupateddie> first have to make a bootable stick for it
[17:53] <Kilos> you use unetbootin or startup disk creator
[17:54] <oupateddie> yep that I have done
[17:58] <oupateddie> Well now I'll probably do a clean install on the laptop with Kubuntu. At this stage I'm basically creating a new Kubuntu machine instead of Ubutnu. Let's see if I am going to become insane again
[17:58] <Kilos> lol go for it
[18:00] <oupateddie> I have been wanting to try kubuntu but always no time,  now it's plunge time
[18:00] <Kilos> first time i tried it i was totally lost but now i love it
[18:01] <Kilos> totally different
[18:02] <oupateddie> does it also have libre office in it
[18:02] <Kilos> all packages are common to all ubuntu
[18:02] <oupateddie> obviously all the linux logic holds good it is just a kde based instead of gnome
[18:03] <Kilos> only the gui differs
[18:03] <Kilos> yip
[18:03] <oupateddie> ok I understand that it is better and faster but it is not user friendly
[18:03] <Kilos> you could actually even have tried it by just installing kubuntu-desktop
[18:04] <oupateddie> can still do that
[18:04] <Kilos> but 13.10 is much faster than earlier versions
[18:04] <oupateddie> then it runs kde instead of gnome?
[18:04] <Kilos> i install it in 12 mins on a dual core p4 with 1.5g ram
[18:04] <Kilos> yes
[18:05] <oupateddie> if I then want to revert back to gnome I just reinstall the gnome desktop?
[18:05] <Kilos> you can choose in the bootup screen where you type in your password
[18:06] <Kilos> you leave gnome there for starters
[18:06] <oupateddie> ok so if i install kubuntu then it will keep gnome and have kubuntu as an extra option.
[18:07] <Kilos> you tick a little thing top right where you type in password and choose
[18:07] <oupateddie> what if I now install 13.10 kubuntu  and then later needs gnoem I can install the gnome desktop as well?
[18:07] <Kilos> yip
[18:07] <Kilos> ubuntu-desktop
[18:08] <oupateddie> will try that instead, then the laptop is at least on 13.10
[18:08] <oupateddie> that basically is sudo apt-get install ubuntu-desktop as a command
[18:09] <Kilos> yes
[18:10] <Kilos> lots of peeps dont like kde but once you are used to it it is very lekker
[18:11] <Kilos> ask superfly for an opinion
[18:11] <oupateddie> Murphy time.... startup crashes so now I am installing kubuntu on 13.04
[18:12] <Kilos> what crashes
[18:12] <Kilos> sjoe murphy move from me to you
[18:12] <Kilos> yay
[18:13] <oupateddie> dtartup disk creator
[18:13] <Kilos> use unetbootin
[18:13] <Kilos> much better
[18:13] <Kilos> makes a good boot stick
[19:27] <Kilos> oupateddie, what happened
[19:28] <oupateddie> still busy installing
[19:28] <oupateddie> the whole world and all are sitting on adls tonight
[19:28] <Kilos> oh on top of gnome?
[19:28] <oupateddie> adsl*
[19:29] <oupateddie> The entire world is in Yzerfontein busy with adsl and the exchange is just dying
[19:29] <oupateddie> yep on top of gnome
[19:29] <Kilos> lol
[19:29] <oupateddie> my 2Mb line is running at 30 kB's
[19:29] <Kilos> ouch
[19:37] <oupateddie> Yep that hurts
[19:37] <oupateddie> wonder why the kubuntu download site is so slow, other stuff are doing well though
[20:03] <Kilos> im gonna sleep now. ballies cant stay up late
[20:03] <Kilos> will be on kde in the morning if i dont forget
[20:04] <Kilos> night all. sleep tight


[08:14] <PaulW2U> 10 summaries to go - will work through them slowly in case anyone else shows up :)
[17:55] <PaulW2U> that's all from me for today, 4 Canonical summaries still to be done
[17:55] <pleia2> thanks PaulW2U


[05:10] -lugito:#lubuntu-devel- [T207: Some manual partition file systems do not work in Calamares] svinoba (Sai Vinoba) commented on the task: https://phab.lubuntu.me/T207#4561
[05:25] -lugito:#lubuntu-devel- [Lubuntu CI] jobgenerator just succeeded after failing: https://ci.lubuntu.me/job/jobgenerator/981/
[05:26] -lugito:#lubuntu-devel- [Lubuntu CI] merger_sddm FAILURE: https://ci.lubuntu.me/job/merger_sddm/334/
[05:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-globalkeys/868/
[05:47] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt just failed after being unstable: https://ci.lubuntu.me/job/groovy_stable_liblxqt/466/
[05:47] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/203/
[05:47] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/203/
[05:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-globalkeys/868/
[22:52] <tomreyn> "wemoved" on freenode is mine btw


[01:46] <bryce> tjaalton: is there a workaround to get xserver to build?
[01:49] <wgrant> bryce: With the libdrm conflict?
[01:50] <bryce> yeah
[01:50] <wgrant> I downgraded it manually in my chroot, but I don't think there's any workaround for the buildds...
[01:50] <wgrant> Other than hunting kernel guys.
[01:52] <bryce> mm, according to bug 308387 it *should* be fixed
[01:52] <bryce> or worked-around at least
[01:53] <wgrant> Ah, very recently.
[01:54] <bryce> funny my pbuilder chroot failed since I'd just updated it...  retrying
[01:54] <bryce> wgrant: btw how was your flight home?
[01:54] <wgrant> It was good - fairly uneventful, though we almost missed the Sydney->Melbourne connection.
[01:54] <wgrant> Yours?
[01:54] <bryce> it was perfect; eerily so.
[01:55] <bryce> short, no babies, no one in the seat next to me, no security line waits, etc.
[01:55] <bryce> hmm
[01:55] <bryce> dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy:
[01:55] <bryce>  pbuilder-satisfydepends-dummy depends on libdrm-dev (>= 2.3.1); however:
[01:55] <bryce>   Package libdrm-dev is not installed.
[01:55] <bryce> dpkg: error processing pbuilder-satisfydepends-dummy (--configure):
[01:55] <bryce>  dependency problems - leaving unconfigured
[01:55] <bryce> Setting up bsdmainutils (6.1.10ubuntu3) ...
[01:56] <wgrant> Oh, and the bus to the BART station didn't come, so we had to walk. That was inconvenient.
[01:58] <bryce> ahh now it's going
[02:00] <bryce> portland got hit by a snowstorm a day after I arrived home; about 10cm in some places, and streets are iced over
[02:01] <bryce> it was cold but sunny today, with the roads passable, so  we were able to get out and go to the market this afternoon.  But another storm's coming tomorrow morning so I think that'll lock us in the rest of the week :-)
[02:01] <superm1> i just got sent back home because my flight from AUS->ORD got canceled because of some snowstorm at ORD (probably remnants of what you saw bryce :))
[02:01] <bryce> superm1: wow
[02:01] <bryce> superm1: hey btw, you'd mentioned something early last week about a touchscreen machine or something that I needed to look at?
[02:02] <superm1> bryce, yeah, BenC is supposed to give it to you
[02:02] <superm1> bryce, he was using it all week at UDS
[02:02] <bryce> ah ok
[02:02] <superm1> it should have fully support by the kernel evdev driver.  the X driver is lacking though
[02:03] <bryce> I'm off next week, so probably won't get a chance to do much with it until january anyway
[02:03] <bryce> (unless it turns out to be something simple)
[02:03] <superm1> yeah that should be fine.  we're not rushing on it, but just want to make sure the support lands sometime by when jaunty is out since we'll have other products after jaunty using the same display
[02:03]  * bryce nods
[02:04] <superm1> i looked at it a little bit and with a few hackish quirks it looks like you can get the pen moving, but i dont know the code that well, and just wanted to see if i could get it that far before handing the hardware off
[02:04] <bryce> I just had a call with one of our oem guys about this; sounds like we're going to give touch good attention for jaunty
[02:04] <superm1> yeah by fixing the evdev driver rather than hacking on wacom everything should start to just work :)
[02:05] <superm1> (that is for non wacom displays)
[02:05]  * bryce nods
[02:07] <superm1> also whenever you've got it to a satisfactory functionality, mirco muller had an interest in it, so you'll be passing it on to him when it gets to that point probably
[02:08] <bryce> okay
[02:58] <bryce> tjaalton: ok fixed up the signal patch (bug 226668), and committed to git.
[03:27] <pwnguin> aww, nouveau is broke
[03:27] <pwnguin> well, missing
[05:08] <bryce> missing?
[05:24] <pwnguin> the modules thing is mia
[05:24] <pwnguin> linux-nouveau-modules
[05:43] <tjaalton> bryce: ok, excellent. I've now requested rebuilds of x86/amd64
[05:43] <pwnguin> tjaalton: fyi, i think wacom works in jaunty
[05:44] <tjaalton> pwnguin: nice
[05:44] <pwnguin> i sent a mail to the list, lemme know if you think i'm wrong ;)
[05:45] <tjaalton> I haven't tested it but if tom thinks it works.. :)
[05:45] <tjaalton> bryce: you marked xorg-server for release, did you upload it?
[05:46] <tjaalton> ah there it is
[05:46] <tjaalton> cool
[05:48] <bryce> yep
[05:51] <pwnguin> on a scale from 0 to finished, does anyone know where nouveau in jaunty is at?
[05:57] <bryce> pwnguin: 7E
[06:00] <pwnguin> =/
[06:01] <pwnguin> mostly, I'd like to know whether I'm doing something wrong or it's just too early to expect installable packages
[06:02] <bryce> what exactly is your question?
[06:02] <tjaalton> it should be installable on jaunty
[06:02] <pwnguin> The following packages have unmet dependencies: xserver-xorg-video-nouveau: Depends: linux-nouveau-modules but it is not installable
[06:02] <pwnguin> E: Broken packages
[06:02] <tjaalton> hmm ok
[06:09] <bryce> tjaalton: do you have an idea on that?
[06:10] <bryce> does -nouveau depend on kernel stuff?
[06:10] <tjaalton> sure, it needs newer drm stuff, so there's a package which builds those
[06:16] <tjaalton> I'm not sure which source package provides that though. the package description suggests to use module-assistant first
[06:17] <tjaalton> pwnguin: grab the package, drop the dep and test :)
[06:17] <pwnguin> heh
[06:18] <tjaalton> hmm no, the kernel doesn't have any version of the module
[06:19] <tjaalton> off to work ->
[06:43] <pwnguin> so was i really supposed to fiddle with the package and test again?
[06:56] <bryce> pwnguin: yeah
[06:57] <bryce> fwiw, -nouveau is not officially supported by us yet (we won't triage bugs against it this release for example)
[06:57] <bryce> we'll accept and upload fixes of course, but at this stage it's considered completely experimental
[07:05] <tjaalton> pwnguin: it'll refuse to work without the drm module
[07:07] <tjaalton> raof should know the state of the package, but he's not online atm
[07:49] <pwnguin> thats what i figured; i'll ping him later
[08:26] <bryce> tjaalton: bug 308410 could use your attention
[08:27] <tjaalton> bryce: expected, and rebuilding those wouldn't help much, since they don't work with the new xserver without force
[08:27] <bryce> tjaalton: could you comment on the bug about this?
[08:29] <tjaalton> done
[08:31] <bryce> heh, no more ctrl-alt-backspace on my dev box
[08:31] <tjaalton> -retro ftw!
[08:38] <bryce> fwiw, with all of today's updates my eaglelake box is working much better
[08:44] <tjaalton> good
[08:53] <tjaalton> bryce: heh, good move to delete the comments :)
[08:53] <tjaalton> from the spec
[08:54] <bryce> tjaalton: I moved them to the wiki page
[08:54] <tjaalton> ah
[08:54] <bryce> whiteboard != forum
[08:54] <tjaalton> yeah
[08:55] <bryce> we're going to get a *lot* of comments about this once people become aware of the change
[09:00] <tjaalton> sure, let them come
[09:10] <lool> tjaalton: Is there an upstream bug for intel not building against linux' drm headers?
[09:10] <tjaalton> lool: I don't know
[09:13] <tjaalton> although I could file one
[09:19] <lool> tjaalton: Well they might not be aware of this if they still use libdrm's headers
[09:19] <tjaalton> they are aware, airlied is trying to persuade intel to get their act together
[09:29] <tjaalton> 2.6rc1 fails to build as well, using libdrm master
[09:34] <tjaalton> freedesktop bug 19132
[09:34] <tjaalton> same error as with 2.5.1
[09:36] <pwnguin> are we finally dispensing with control-alt-bksp?
[09:39] <pwnguin> cleverly hidden
[09:41] <tjaalton> yes
[09:44] <pwnguin> i gotta say, blueprints is confusing as hell
[09:59] <tjaalton> in general or this particular one
[10:10] <tseliot> tjaalton: is the new intel driver available now?
[10:10] <tseliot> the one with the fix to my problem
[10:10] <tjaalton> tseliot: it was a bug in the server
[10:10] <tjaalton> and it's available
[10:11] <tseliot> ok, thanks :-)
[10:14] <lool> tjaalton: thanks
[11:24] <tseliot> seb128: I gave mvo all the patches you need and he merged them. Now you can push gnome ;)
[11:25] <seb128> tseliot: ok thanks!
[11:50] <jcristau> lool: upstream knows about it, they'll probably fix up the kernel headers at some point. until then just build against libdrm?
[12:36] <tseliot> tjaalton: 3D effects (Compiz or Kwin) are very slow with the Intel driver now
[12:36] <tseliot> but hey, at least X starts now
[12:39] <tjaalton> tseliot: check the permissions on /dev/dri/card0
[12:41] <tseliot> tjaalton: crw-rw---- 1 root video 226
[12:41] <tjaalton> ..and if you're not on video-group -> fail
[12:42] <tjaalton> tseliot: btw, are you on linuxwacom-discuss?
[12:42] <tseliot> tjaalton: no, where is it?
[12:43] <tjaalton> the mailing list?
[12:43] <tseliot> tjaalton: aah, ok
[12:43] <tjaalton> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
[12:43] <tseliot> I'll post there soon
[12:44]  * tseliot > lunch
[12:44] <tjaalton> well, alexia death has looked into using dbus for hotplugging
[12:45] <tjaalton> and looks like it's possible to write a callout script which does things once you plug a tablet
[12:45] <tjaalton> +in
[12:50] <tjaalton> so, wacom hotplug should be around the corner, but there still are issues about where to store the config options etc.
[13:12] <lool> jcristau: Yup just what we're doing
[14:04] <tseliot> tjaalton: that would be interesting
[14:11] <tseliot> tjaalton: compositing is so slow that even KWin noticed and told me that it was better to disable it
[14:12] <tjaalton> tseliot: well, did you fix the permissions then?
[14:12] <tjaalton> you need to have rw-access to /dev/dri/card0
[14:12] <tseliot> tjaalton: I added myself to the video group
[14:13] <tjaalton> and logged out & in?
[14:13] <tseliot> tjaalton: I restarted Ubuntu
[14:13] <tjaalton> ok
[14:13] <tjaalton> dunno what's wrong then
[14:14] <tseliot> and I get direct rendering
[14:16] <tseliot> tjaalton: can you enable dbus in the xserver?
[14:23] <tjaalton> done in git
[14:27] <jcristau> tjaalton: it's called enable-config-dbus
[14:31] <tjaalton> jcristau: hah, so it is
[14:46] <tseliot> tjaalton: that will allow me wacom hotplug
[14:46] <tseliot> allow me to do
[14:47] <jcristau> you can't do wacom hotplug with config/hal?
[14:47] <tjaalton> jcristau: only one device (stylus/eraser/..)
[14:47] <tjaalton> to fully use wacom you need to set up at least three devices
[14:48] <jcristau> i thought NIDR was exported just for that reason?
[14:48] <tseliot> NIDR?
[14:48] <tjaalton> well I don't know what the details are
[14:48] <jcristau> tseliot: the function that creates a new input device
[14:48] <tjaalton> NewInputDeviceRequest
[14:49] <tseliot> jcristau: ok but does the wacom driver work with it?
[14:49] <tjaalton> http://sourceforge.net/mailarchive/forum.php?thread_name=200812162159.29671.alexiadeath%40gmail.com&forum_name=linuxwacom-discuss
[14:49] <jcristau> dunno. that's not the point though. if it doesn't, it can presumably be made to work
[14:50] <tseliot> tjaalton: I replied to her
[14:51] <tseliot> btw do you know why I get this is my Xorg.0.log? Failed to set tiling on front buffer rejected by the kernel
[14:52] <tseliot> it says the same about back and depth buffer
[14:53] <tjaalton> nope, no idea
[14:54] <tseliot> http://pastebin.com/m4606b1d9
[14:54] <tseliot> the full log ^^
[14:58] <tjaalton> upgrade your kernel
[14:58] <tjaalton> check dmesg for segfaults
[15:09] <tseliot> tjaalton: upgrade my kernel to which version?
[15:15] <tjaalton> to the latest one, yours is -2 while there is -3 available
[15:19] <tseliot> tjaalton: I can't see it in the repository
[15:20] <tjaalton> then change your mirror, preferably to just archive.u.c
[15:20] <tjaalton> gone ->
[15:22] <tseliot> found
[15:41] <tseliot> hmm, it doesn't seem to solve the problem
[15:48] <tjaalton> ok
[15:53] <tseliot> also I can't switch to vt without corrupting the screen
[15:54] <tjaalton> disable usplash
[16:09] <tseliot> right
[17:29] <bryce> superm1: erf, ATI is changing the bug escalation rules again
[17:30] <bryce> superm1: now they are no longer accepting new bugs once we've reached 5 (non-feature) EPR's
[17:42] <lool> Hi folks
[17:43] <crevette> salut lool
[17:43] <lool> On ATI R500 I had screen corruption all over the place until I forced EXA
[17:43] <lool> I'm using compiz
[17:43] <lool> Should we make EXA the new default for ati?
[17:48] <bryce> lool: yep
[17:48] <bryce> lool: in fact I've a blueprint open on doing exactly that... probably post-alpha2 I'll switch us over
[17:49] <bryce> I'd have done it already by now, but just been busy
[18:03] <lool> bryce: ok cool
[18:51] <bryce> tjaalton, tseliot, should bug #308410 get a mention on the alpha-2 release notes?
[19:19] <geeksquad> how do you restore the icons folder in /usr/share
[19:20] <geeksquad> hello
[19:21] <bryce> geeksquad: wrong channel.
[19:21] <geeksquad> whitch is the right channl
[19:22] <geeksquad> other than #ubuntu
[19:23] <geeksquad> bryce
[19:23] <bryce> dunno
[19:23] <bryce> this channel is only for X.org in ubuntu though.
[19:24] <geeksquad> oh maybe #gnome will work
[20:53] <tjaalton> bryce: just mention that blobs don't work. jockey doesn't offer them anymore
[20:55] <bryce> tjaalton: I think once alpha-2 is out, I'm going to pull a new -ati git snapshot and flip EXA on by default
[20:55] <bryce> *hopefully* that will be Friday
[20:55] <tjaalton> bryce: yeah
[21:00] <tjaalton> so, alexia tells me that she (?) managed to get wacom hotplug working using the dbus-script as a hal callout-script like debian-setup-keyboard is
[21:01] <tjaalton> the driver is a bit buggy so that some options are wrong, and of course no user settings are set, but that can be fixed while the device is plugged in
[21:02] <tseliot> yes, I talked to Alexia and I think we can work together
[21:04] <tseliot> bryce: do you know what can make my 965 slow when using 3D effects in Jaunty?
[21:05] <tseliot> bryce: log: http://pastebin.com/m4606b1d9
[21:21] <tseliot> videos have no tearing any more though
[21:24] <bryce> tseliot: mm, in your log I see some errors about tiling buffers rejected by the kernel
[21:25] <bryce> (WW) intel(0): Existing errors found in hardware state. <-- doesn't sound good either
[21:26] <bryce> however, I'm not familiar with these errors yet so don't know their significance
[21:26] <tseliot> ok
[22:19] <bryce> tjaalton: https://wiki.ubuntu.com/Hotkeys has a 'should be' diagram there now too.  let me know if there are any inaccuracies in it
[23:26] <tjaalton> bryce: nice pics, looks good so far :)
[23:26] <tjaalton> btw, now my laptop (965) refuses to start X properly :)
[23:27] <bryce> tjaalton: what did you run into?
[23:28] <bryce> I'm doing another ->intrepid upgrade on another 965 system (my laptop)
[23:28] <bryce> after alpha-2 I think I'm going to try a from-scratch reinstall
[23:28] <tjaalton> the display just goes blank, flashes a couple of times before that
[23:28] <tjaalton> maybe it didn't like me booting into xp to update my phone & remote
[23:30] <bryce> tjaalton: run intel_reg_dumper to collect the register settings while it's blank, then again when you get it working with vesa or a livecd or something, and send both to jesse
[23:31] <bryce> mm, could windows have left the gfx card registers in an inconsistent state for linux?
[23:31] <tjaalton> or just the fact that I have master snapshot of libdrm
[23:32] <bryce> tjaalton: btw I got confirmation that we are *not* doing KMS for jaunty.  That rumor we heard friday was apparently just a rumor
[23:33] <tjaalton> bryce: ok
[23:34] <tjaalton> yeah, downgrading libdrm helped


[00:07] <tlm> what do we consider the primary web domain for juju? Need to inject a proper unique domain into kubernetes for the controller
[00:08] <timClicks> tlm: juju.is will be our home shortly
[00:08] <tlm> sold, thanks
[00:23] <hpidcock> tlm: inside k8s we use juju.io
[00:24] <hpidcock> but I think that is wrong
[00:24] <tlm> oh
[00:25] <timClicks> we never actually acquired that domain I think
[00:25] <hpidcock> yep
[00:26] <tlm> i am looking for refs in the code
[00:26] <tlm> we use it only in annotations now
[00:27] <tlm> should we change to something we own ?
[00:50] <anastasiamac> babbageclunk: https://github.com/juju/juju-restore/pull/6 has the one char read :)
[00:51] <babbageclunk> ok looking
[01:08] <babbageclunk> anastasiamac: neat! but the patches make me sad
[01:14] <babbageclunk> thumper: (or rick_h if you haven't gone to sleep yet) can you make one for juju/symlink as well? Otherwise juju/tar still depends on juju/utils/symlink
[01:56] <anastasiamac> babbageclunk: yeah :( i did not like ti eiether but i was not too keen to add yet another func as a property everywhere
[01:56] <anastasiamac> babbageclunk: anyway changed now.. PTAL ?
[01:58] <tlm> hey hpidcock hit a snag with ssl certs. Got time for HO ?
[01:59] <hpidcock> sure
[02:02] <babbageclunk> anastasiamac: approved!
[02:02] <anastasiamac> babbageclunk: \o/
[02:02] <anastasiamac> babbageclunk: wot's worng with 'in a raw mode"?
[02:02] <babbageclunk> anastasiamac: I know what you mean about passing in more things - it kind of means they end up leaky
[02:03] <anastasiamac> yeah main command call is growing :(
[02:03] <babbageclunk> anastasiamac: Well, there's only one raw mode, and the terminal's in it!
[02:03] <anastasiamac> i can honestly say that English articles r confusing!! :D
[02:04] <babbageclunk> yeah, that's probably fair
[02:11] <rick_h> babbageclunk:  https://github.com/juju/symlink
[02:21] <babbageclunk> yay thanks again rick_h - I think thumper's ignoring me.
[02:47] <thumper> babbageclunk: not ignoring, just busy
[02:48] <babbageclunk> thumper: I know, just hassling!
[02:48] <thumper> babbageclunk: the fileutils part was one of the next things I was wanting to extract
[02:48] <thumper> particularly the exec handling
[02:48] <thumper> but it was always just a bit "later"
[03:45] <thumper> wallyworld: seeing multiple intermittent test failures in ActionSuite.TestFindActionTagsByLegacyId trying to land in develop
[03:45] <wallyworld> ok
[03:46] <thumper> also in worker/caasoperator
[03:49] <thumper> jam: updated https://github.com/juju/juju/pull/11208 to use mark and sweep to indicate initialization step
[03:49] <thumper> to avoid calculating summaries while initializing
[04:56] <hpidcock> thumper: wallyworld: my pr fixes that intermittent failure
[04:57] <hpidcock> which has landed
[06:20] <tlm> hpidcock wallyworld: still sorting out stuff but start of PR https://github.com/juju/juju/pull/11089
[06:21]  * tlm will be back at 5
[09:35] <achilleasa> hpidcock: so is this block copied over from the uniter and not in use atm? (https://github.com/juju/juju/blob/develop/apiserver/facades/agent/caasoperator/operator.go#L187-L211). Are there any plans to use it in the future? I guess I might as well add a leadership check there too to be safe... just need to figure out what AuthOwner() returns when inside the operator facade
[09:56] <hpidcock> achilleasa: when I looked a few hours ago there is no call to that from the caasoperator worker. It sets up an interface, casts the client to that interface, stores it and that was all. Only the uniter runner context has any mention of calling setpodspec. It looks like its been there for two years and nothing used it. Or uses it anymore. So without going through the history, I can't say for sure. But what I can say is
[09:56] <hpidcock> that an application should only have one caasoperator worker, so the leadership check is unnecessary.
[10:13] <achilleasa> hpidcock: that was my thought exactly which is why I am currently bypassing the check there (and in the migration path)
[11:04] <stickupkid> manadart, quick ho around openstack
[11:04] <stickupkid> ?
[11:06] <manadart> stickupkid: OMW
[11:06] <achilleasa> jam: when we introduce new hook types do we need to also open PRs against charm tools (e.g. to populate the symlinks when building the charm?)
[12:00] <nammn_de> manadart: later time for a ho about move-to-space and fan networking?
[12:04] <manadart> nammn_de: Sure. Let's do it after stand-up. I have to relocate home before then.
[12:04] <nammn_de> manadart: rgr
[12:35] <stickupkid> achilleasa, i'm seriously thinking of adding multiple errors to pkg/err
[12:35] <stickupkid> achilleasa, i'm sure we roll our own everytime
[12:36] <achilleasa> stickupkid: params.ErrorResult is one place
[12:36] <achilleasa> and I think we do something similar for bundlechanges
[12:36] <stickupkid> achilleasa, just done a new one in provider/openstack \o/
[13:25] <achilleasa> can I get a quick CR on this tiny change? https://github.com/juju/charm/pull/304
[15:19] <zeestrat> Hey, we're hitting something strange with where deploying cs:ubuntu-14 in a bundle fails, but deploying it manually with `juju deploy ubuntu --series xenial` works. Could someone humor me and deploy http://paste.ubuntu.com/p/XFqtd6qc7q/ with Juju 2.7.2 on local LXD before I write up a bug?
[15:23] <zeestrat> https://www.irccloud.com/pastebin/J43EZZHw/
[15:46] <stickupkid> zeestrat, this might be related https://github.com/juju/charm-helpers/pull/434#pullrequestreview-361992024
[15:47] <zeestrat> stickupkid: thanks, looks that way. Still rather confused why it hits in bundle deploys but not CLI deploy. Thanks for the info!
[17:05] <achilleasa> stickupkid: can you take a look? https://github.com/juju/juju/pull/11237
[17:19] <achilleasa> stickupkid: added extra context for the uniter change
[17:20] <stickupkid> achilleasa, happy with that :+1:
[21:19] <thumper> aah... who changed history on the 2.7 branch?
[21:21] <thumper> also, how did the history get rewritten on the 2.7 branch
[21:21] <hml> thumper: when?
[21:21] <thumper> since Feb 1
[21:21] <thumper> which was the last time I pulled 2.7
[21:22] <thumper> https://github.com/juju/juju/commits/2.7?after=9da5b593fa1d096220230143f1e1fea5c4eb56ad+69
[21:22] <thumper> suspect there
[21:22] <hml> thumper: rick_h, we needed a backport from achilleasa  for 2.7.2 - there shoudl be 3 commits that got placed after his
[21:22] <thumper> Jan 23 looks right
[21:23] <hml> thumper: i’m not sure of the date though.
[21:25] <thumper> I'm not sure what has happened here
[21:27]  * thumper sighs
[21:27] <thumper> looks like the 2.7 branch was renaemd to 2.7-configoption
[21:27] <hml> thumper: it was around feb 10
[21:27] <thumper> and and older branch was pushed to 2.7
[21:27] <thumper> no idea what/why
[21:27] <thumper> not even sure if the 2.7-configoption is in 2.7
[21:28] <thumper> because one of my fixes doesn't appear to be in 2.7 any more
[21:28] <thumper> this needs more digging
[21:28] <hml> thumper: i don’t think that was us?  <crossing fingers>
[21:30] <thumper> FFS
[21:34] <thumper> and... those commits aren't in our latest release
[21:34] <thumper> so we are missing about four bug fixes in the 2.7 branch
[21:53] <babbageclunk> oh crap
[22:13] <timClicks_> wallyworld: which release notes template did you used for your 2.7.3 WIP post?
[22:13] <wallyworld> i copied 2.7.2 and hacked it up
[22:14] <wallyworld> there is a template somewher ei tihnk
[22:15] <timClicks_> which would have been copied from 2.7.1
[22:15] <timClicks_> they're using an old template
[22:15] <timClicks_> simon's release of 2.7.0 is using the current one
[22:23] <hpidcock> so turns out AWS instance pricing index.json is somewhat wrong. It shows prices for instance types for regions that don't fully support that type. It just means at least one AZ in that region supports that instance type...


[02:53] <dtchen> nhandler: mind looking at bug 313820? it has been verified for a couple months now
[02:54] <nhandler> Sure thing dtchen
[02:54] <dtchen> thanks
[02:57] <nhandler> dtchen: Have you talked to the Debian Maintainer about this issue?
[02:59] <dtchen> i pinged, but no response
[02:59] <dtchen> as you can see, it has been a couple months
[03:36] <nhandler> dtchen: What do you need to do to triger the buffer overflow?
[03:43] <nhandler> dtchen: I'm going to bed. Please add a comment explaining how to reproduce that bug, and I'll look at it tomorrow
[05:59] <dholbach> good morning
[05:59] <binarymutant> thanks for uploading that change dholbach :)
[06:00] <dholbach> binarymutant: no worries
[06:01] <dholbach> binarymutant: I added a changelog entry for 1ubuntu1 for you
[06:02] <binarymutant> thank you :)
[06:02] <fabrice_sp_> Hey dholbach ! :-)
[06:02] <fabrice_sp_> already sponsoring ;-)
[06:02] <dholbach> fabrice_sp_: I figured that's the best way to start the day :)
[06:03] <fabrice_sp_> dholbach, Well. I would say a coffee is not that bad ;-)
[06:04] <dholbach> fabrice_sp_: that too :)
[06:10] <dholbach> luisbg: can you recommend a club in Barcelona? :)
[06:14] <fabrice_sp_> dholbach, you mean nightclub? Because club can be misunderstood in Spain :-)
[06:14] <dholbach> fabrice_sp_: nightclub, music, dancing, yes :)
[06:14] <fabrice_sp_> (at least in Madrid. I don't know for Barcelona :-) )
[06:14]  * slangasek recommends a club soda
[06:14] <fabrice_sp_> ok ;-)
[06:15] <dholbach> fabrice_sp_: every other kind of club I leave to UDS attendees to figure out themeselves ;-)
[06:15] <fabrice_sp_> do't worry: in the air plane books, you generally have some addresses of other kind of clubs...
[06:15] <fabrice_sp_> lol
[06:21] <dholbach> fabrice_sp_: regarding te graphviz fix - is there no way to get it to build 2.5 and 2.6 modules?
[06:21] <dholbach> doko: ^ do you have an idea how to do it (bug 338553)
[06:23] <dholbach> fabrice_sp_: sugar-base: intrepid -> jaunty :-)
[06:25] <fabrice_sp_> dholbach, about graphviz: the package is not ready to deal with python26. We should modify at least configure and perhaps Makefile to deal with 2 build version (the build location is different in --enable-python and --enable-python2.5)
[06:26] <fabrice_sp_> what do you mean with sugar-base? I saw that a update request is there, but I didn't saw morgs to ask him the status
[06:26] <dholbach> fabrice_sp_: the sponsoring bug regarding python2.6
[06:28] <dholbach> hiya jono
[06:28] <fabrice_sp_> dholbach, the rebuild, yes. Sorry, but I don't get your point :-( Is there something also in Intrepid?
[06:28] <dholbach> fabrice_sp_: no, you had "intrepid" in the changelog entry
[06:28] <fabrice_sp_> ahhh
[06:28] <dholbach> just fixed it and re-uploaded
[06:29] <fabrice_sp_> dholbach, sorry about that: I use intrepid for building the package in a sbuild and jaunty chroot for the change. I sometime mix things :-/
[06:29] <fabrice_sp_> thanks! :-)
[06:29] <dholbach> https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases :)
[06:30] <doko> dholbach, fabrice_sp_ : fix the packaging, build it twice.
[06:31] <fabrice_sp_> dholbach,  yeah, I know, but it's a shared computer, and I already have 'family problems' to have Ubuntu accepted (especially because of flash in adm64), so using a 'non stable' version could be a reason of not having a family any more! :-)
[06:32] <dholbach> fabrice_sp_: that page explains how to do it in a "safe way"
[06:32] <fabrice_sp_> doko, should the rules file be generic, or we could use 'hardcoded' python version (ie: if python2.5 move that files and if python2.6, move that other files)
[06:33] <fabrice_sp_> dholbach, oh. I'll have a look then! :-)
[06:34] <dholbach> fabrice_sp_: in the synfigstudio request quilt would not have been necessary - the debian maintainer seems to patch the source directly, so you could have just done the same
[06:34] <dlynch> does anyone have any opinions on a good package name for a program called "rapid photo downloader" (I am the upstream author, and I'm doing my first package) http://damonlynch.net/rapid/
[06:35] <dlynch> two obvious choices are 'rapidphoto' or just 'rapid'
[06:35] <dholbach> dlynch: what's wrong with rapid-photo-downloader? :)
[06:35] <dlynch> it has not been packaged at all yet
[06:35] <dlynch> is that not too long?
[06:35] <dholbach> makes sure it's not being confused with anything else
[06:35] <dlynch> ok if the length is not a problem, it's not a problem with me! :)
[06:35] <dholbach> it's shorter than xserver-xorg-video-openchrome :)
[06:36] <dholbach> or system-config-printer-gnome
[06:36] <dholbach> or lots of others :)
[06:36] <dholbach> dlynch: rock on! :)
[06:36] <dlynch> ok that probably makes my life as a packaging novice easier then
[06:36] <dlynch> thanks!
[06:36] <dholbach> no worries
[06:36] <fabrice_sp_> dholbach, I have to say I always use quilt to patch, and never look at debian modifications. I'll check with kallery
[06:37] <dholbach> fabrice_sp_: it makes the patch shorter and is in line with what the debian maintainer does, so I thought that'd make sense :)
[06:38] <fabrice_sp_> dholbach, sure. Should I upload a new debdiff? By the way, for Bug #348160 should I subscribe u-u-s after each package or only when having all the debdiff
[06:38] <dholbach> fabrice_sp_: yeah, please attach a new debdoiff
[06:39] <dholbach> fabrice_sp_: I just try to keep the sponsoring overview as short as possible, so if there's nothing to sponsor, I unsubscribe the team - just re-subscribe if you want anything uploaded :)
[06:39] <fabrice_sp_> dholbach, will do. Thanks!
[06:40] <dholbach> rock on! :)
[06:40]  * dholbach hugs fabrice_sp_
[07:00] <didrocks> morning o/
[07:46] <slangasek> does someone who knows ruby want to fix ruby-gnome2 FTBFS?
[07:47] <slangasek> (maybe a merge from Debian?)
[07:55] <Elbrus> I like my package to "suggest" any internet browser. Is there a virtual package I could suggest (e.g. sensible-browser)?
[07:55] <Toadstool> good morning
[07:57] <Toadstool> Elbrus: Suggests: www-browser
[07:58] <Elbrus> Toadstool: thanks
[08:00] <Elbrus> is there something similar for pdf-readers?
[08:01] <Toadstool> Elbrus: pdf-viewer :)
[08:02] <Elbrus> great. I was trying to find it in debian-policy...
[08:03] <Toadstool> Elbrus: http://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt
[08:03] <Elbrus> Toadstool: just found it a second ago... Thanks
[09:00] <dlynch> I am having problems with the man page section of the debian/rules file, after following the instructions at https://wiki.ubuntu.com/PackagingGuide/Complete#Necessary%20packaging%20changes
[09:00] <dlynch> http://paste.ubuntu.com/137312/ , when running dpkg-buildpackage -us -uc I get this error :
[09:00] <dlynch>  fakeroot debian/rules clean \n debian/rules:12: *** missing separator (did you mean TAB instead of 8 spaces?).  Stop.
[09:01] <dlynch> (sorry I was d/c a few minutes ago)
[09:01] <liw> dlynch, you need to indent the commands in debian/rules (just like in a Makefile, for it is a Makefile) using tab characters, not spaces
[09:02] <dlynch> liw: thank you, I'll try that then
[11:41] <Mewcenary> Hi, can someone help me with a newbie packaging query please?
[11:42] <Mewcenary> lintian complains that I have files which are changed despite using quilt (I am taking over a package)...
[11:42] <Mewcenary> But one of those files is Makefile.in which seems to be changed whenever a build occurs.
[11:42] <Mewcenary> HOw can I get around that problem?
[11:57] <mok0> Mewcenary: delete Makefile.in in the clean rule
[11:58] <Mewcenary> Thanks for the tip, I'll try that out.
[11:58] <pmjdebruijn> soe packages so NOCONFIGURE=1 ./autogen.sh before creating the source tarball, I'm not sure whether that's applicable here
[12:38] <bddebian> Heya gang
[12:41] <jdstrand> btm, cjwatson, Laney: not sure what happened with bug #334065. I clearly didn't process the request... I'm pretty sure it was the day that I was doing requests manually (ie without syncbugbot). Regardless, it was a mistake and I apologize
[12:43] <siretart`> heya bddebian
[12:45] <bddebian> Hi siretart
[12:47] <sistpoty|work> hi folks
[12:49] <bddebian> Heya sistpoty|work
[12:49] <sistpoty|work> hi bddebian
[12:49] <bddebian> sistpoty|work: I don't know if  you noticed but I uploaded trigger-rally and -data :)
[12:49] <sistpoty|work> bddebian: yep, I saw that... thanks a lot! :)
[12:50] <bddebian> NP
[13:10] <jdstrand> btm, cjwatson, Laney: fyi-- bug #334065 is now synced
[13:11] <Laney> cool, thanks
[13:11] <jdstrand> sure. sorry again for the mix up
[14:22] <dlynch> is this the correct place to ask a question about a PPA build error?
[14:26] <maxb> Depends on whether you suspect the problem is with the PPA build environment (#launchpad) or the package source (here is reasonable)
[14:31] <dlynch> maxb: thanks given this is my first attempt to build a deb for a PPA, I strongly suspect the latter ;-)
[14:32] <dlynch> I got an 'ImportError: No module named gtk.gdk' in the dh_clean part of the build
[14:33] <dlynch> I'm hoping that by simplifying the imports in the setup.py, this problem will go away
[14:33] <maxb> Have you built the package locally in pbuilder prevu or sbuild ?
[14:33] <geser> dlynch: can you point us to the package?
[14:35] <dlynch> maxb: I'm not sure I understand your question, but when I built it locally, I ran dpkg-buildpackage -us -uc
[14:35] <maxb> dlynch: Then it sounds as if your problem is a build-time dependency that is not declared in your debian/control Build-Depends
[14:36] <dlynch> geser: I can point you  to the trunk on launchpad
[14:36] <maxb> Packages build on the automated builders in a very minimal environment, into which the dependencies explicitly asked for in Build-Depends have been added. If you don't ask for a package in Build-Depends, you don't get it available.
[14:37] <dlynch> maxb: I have cdbs (>= 0.4.49),  debhelper (>= 7), python-central (>= 0.5.6), perl in my build depends
[14:37] <maxb> pbuilder replicates this scenario locally to help you check your packages
[14:37] <maxb> dlynch: There's no mention of any python gtk stuff there, yet you're using it in your build process - so that's the problem
[14:38] <dlynch> maxb: ahhh ok. I think it merely came from the fact that my setup.py was importing the version number from the main script, which of course has many imports in it, including gtk
[14:39] <dlynch> so the solution is to store the version number somewhere with no imports, I think :D
[15:02] <cyberix> https://bugs.launchpad.net/ubuntu/+bug/348480
[15:03] <cyberix> This is actually probably not MOTUs fault, but maybe someone knows someone who knows something about this.
[15:06] <dlynch> please forgive me for asking such a super newbie question, but is the best (only?) way to add the ~ppan package suffix via the changelog in the debian directory?
[15:07] <geser> yes, the last entry in the changelog determines the package version/revision
[15:08] <cyberix> Should people really add ppa suffixes to their packages?
[15:08] <dlynch> geser: thanks! I already figured out that not rigidly adhering to the changelog format causes a build failure :)
[15:09] <radix> cyberix: see "Versioning" in https://help.launchpad.net/Packaging/PPA
[15:09] <geser> dlynch: when you use dch it helps you with the format of it
[15:09] <radix> cyberix: it has the rationale for ~ppaN
[15:10] <cyberix> right
[15:10] <dlynch> one thing I've come across is that my debian directory is part of my python setup.py sdist output
[15:10] <cyberix> custom packages
[15:10] <dlynch> which is all fine and good
[15:10] <cyberix> customized for ppas
[15:10] <dlynch> but the problem arises when launchpad rejects the orig.tar.gz
[15:10] <dlynch> saying it's different, even though the version didn't change
[15:11] <dlynch> but it is different only because the contents of the debian directory  have changed
[15:11] <dlynch> I'm only trying to update my packaging stuff, not the source code itself
[15:12] <dlynch> sorry if this is a confusing explanation
[15:14] <dlynch> my question is this: is it a bad idea to put the contents of the debian directory in the tarball created by python setup.py sdist ?
[15:14] <maxb> Generally, yes.
[15:15] <dlynch> aha
[15:15] <dlynch> maxb: so that means to do a build, I should copy the contents of that directory myself
[15:16] <maxb> Does this thing you're packaging have upstream releases?
[15:17] <dlynch> maxb: I am the upstream author, and this is my first time to package anything
[15:17] <maxb> The usual approach is to maintain the upstream release and the packaging separately
[15:18] <dlynch> so I should put things like the man page pod file and the .desktop file in the upstream, and practically everything else in the debian directory?
[15:20] <maxb> Well, presumably you'll want to release a tarball for people and/or other distributions to use?
[15:20] <dlynch> maxb: yes
[15:20] <maxb> That tarball, which would usually be foo-1.0.tar.gz gets renamed to foo_1.0.orig.tar.gz for the debian package
[15:21] <dlynch> I store the tarballs on launchpad
[15:21] <maxb> Then, you unpack that tarball, add a debian/ directory to it, and build a debian source package, which generates a .diff.gz and a .dsc file that go along with the .orig.tar.gz
[15:23] <dlynch> since this must be such a common procedure on launchpad python archives, has someone built a tool to automate as much of this as possible?
[15:24] <maxb> dpkg-buildpackage (or debuild) will build the source package from the unpacked directory
[15:25] <dlynch> thank you maxb, I will look into this tool more thoroughly... and thanks very much for your guidance, it makes a lot of sense
[15:41] <rgreening> ScottK: ping
[16:01] <dlynch> I'm confused by how to have a python package work for intrepid as well as jaunty. I've read the documentation at https://help.launchpad.net/Packaging/PPA, but it doesn't say what how the debian changelog entry should be entered to presumably allow the package to work on more than one release
[16:06] <geser> dlynch: you need an upload for jaunty and one upload for intrepid (and if you want to support other releases too and upload for them too)
[16:07] <dlynch> geser: and they should have separate changelogs, or the same?
[16:07] <geser> and each upload needs a different pkg revision (e.g. include the disto name in the revision, e.g. ~ppaN~intrepid1)
[16:08] <dlynch> geser: why do I need to do this when the program does not need to be recompiled?
[16:08] <geser> dlynch: the minimalistic way would be to change the release and the pkg version in the changelog but you can also add a new entry for those "backports"
[16:09] <geser> dlynch: often it's because of the runtime dependencies which are determined during build
[16:10] <dlynch> geser: you mean the launchpad build process is clever enough to determine whether the python program can be built across more than one release?
[16:11] <geser> dlynch: no, during the build some scripts scan the package and add the necessary dependecies e.g. on libraries or the python intepreter
[16:11] <dlynch> do they "hard code" in something like 'python2.6', or do they keep the version range I specified?
[16:12] <geser> dlynch: it depends on the package if it runs on several releases or not
[16:12] <geser> dlynch: depends on how you packaged it
[16:12] <dlynch> geser: my package does run on several releases
[16:12] <dlynch> and I did package it so it will install unchanged on both jaunty and intrepid
[16:12] <geser> what are the runtime dependencies on the binary package?
[16:13] <dlynch> ${python:Depends},         ${misc:Depends},        python-gnome2,         python-gtk2 (>= 2.10),  python-glade2 (>= 2.10),        python-pyexiv2 (>= 0.1.2),        python-notify
[16:14] <dlynch> XS-Python-Version: >= 2.5, << 2.7
[16:14] <geser> and now the same from the build package (from PPA)
[16:14] <dlynch> you mean from the one built by the PPA?
[16:14] <btm> jdstrand: thanks!
[16:15] <geser> dlynch: yes. is it rapid-photo-downloader?
[16:15] <dlynch> yes
[16:17] <dlynch> geser: it is the same, except python-central >= 0.6.11 is now explicitly specified
[16:17] <geser> dlynch: the depends on python itself are ok for intrepid, but the generated dependency on python-central (>= 0.6.11) can't be fulfilled on intrepid -> rebuild necessary to get the correct versioned dependency for intrepid
[16:18] <dlynch> geser: if I did the build from intrepid instead, would it work for both intrepid and jaunty automatically?
[16:18] <dlynch> or do I still need to make  two different packages?
[16:20] <geser> dlynch: if you build it on intrepid and "copy" then the debs to jaunty it should work on both
[16:20] <geser> copying debs forward has more success than copying backwards
[16:21] <dlynch> geser: great! thank you very much for your time!
[17:36] <BlackLukes> hi, yesterday I was asking about what code is used to display the partition bar in ubiquity as seen here: http://www.askdavetaylor.com/2-blog-pics/ubuntu-install-pic6.png
[17:36] <BlackLukes> I can't find it in the source, can anyone help me?
[17:53] <RainCT> Is there some GUI tool to sync directories on different PCs? (decentralized, not stuff like Dropbox)
[17:54] <mrooney> RainCT: version control?
[17:54] <mrooney> :)
[17:56] <RainCT> mrooney: well, but I don't really mind about revisions, I just want something fast and space efficient, and most important with monitoring (so that if I change something, and I'm connected to the other PC, it gets synced automatically)
[17:56] <RainCT> perhaps fsniper + bzr would do, but I was looking for something more ellaborated :P
[17:57] <RainCT> (uhmm no, fsniper is only for new files)
[17:58] <sistpoty|work> RainCT: maybe grsync? (no clue so, what it can do, haven't used it myself yet)
[18:01] <RainCT> Looks nice, but it doesn't have the file monitoring
[18:07] <RainCT> well, I think I'll get with plain rsync for now
[18:07] <RainCT> s/get/go.    thanks anyway
[18:07]  * sebner waves at sistpoty|work :)
[18:08] <sistpoty|work> hi sebner
[18:10] <geser> Hi sebner, you've now internet during the week again?
[18:10] <RainCT> hey sebner
[18:11] <geser> RainCT: have you had a look at unison?
[18:12] <sebner> hi geser RainCT
[18:12] <dtchen> nhandler: simply rebuilding the source package and starting the compiled daemon results in the symptom
[18:12] <sebner> geser: well, only if I return home (1h with the train). I won't do this that often. maybe 1-2 times a week
[18:12] <RainCT> geser: oh, that one looks great :)
[18:16]  * sistpoty|work calls it a day... cya
[18:21] <dtchen> nhandler: it's a case of toolchain skew; we can either leave it be for jaunty, or we can fix the source. it's fairly obvious to me that the correct thing is to fix the source, but eh, i leave it to you guys who have upload privileges.
[18:31] <iulian> RainCT: You might want to try giver.
[18:32] <directhex> cprov-afk, didn't know there WERE whiteboards. nuke 'em
[18:32]  * iulian is disappointed because it's unmaintained upstream.
[18:33] <cprov> directhex: right, that's the point :)
[18:34] <directhex> iulian, adopt upstream duties!
[18:35] <directhex> cprov, the only PPA wishlist for me right now is debian support
[18:35] <directhex> cprov, e.g. the dependency management stuff is great
[18:35] <cprov> directhex: really ? have you explored it ?
[18:36] <cprov> directhex: we've never had much feedback about it.
[18:36] <directhex> cprov, just added a dep on someone else's PPA to avoid needing to repackage some stuff myself. huge timesaver
[18:36] <directhex> also, dh7!
[18:37] <cprov> directhex: cool, it gets more useful when the PPAs for important projects (kde, gnome, bzr) are organized.
[18:38] <directhex> cprov, well, that ties into the debian question - if a ppa could build debian stuff natively, then it'd be much easier to convince migration from alioth for cross-distro teams
[18:40] <cprov> directhex: right, I see your point. Building debian sources natively (using debian chroots) is theoretically possible and is in our plans, but unfortunately not before July.
[18:40] <directhex> cprov, meh. it's been how many years so far? what's a few more months? :p
[18:41] <cprov> directhex: 'good things take time' seems appropriate here ;)
[18:42]  * cprov hides
[18:42] <directhex> cprov, the phrasology is "good things come to those who wait"
[18:45] <ScottK> directhex: For dh7 (I assume you're packaging for Hardy) you can also depend on hardy-backports to get it.
[18:45] <directhex> ScottK, exactly! like i said, PPAs are awesome ;)
[18:46]  * ScottK is a lot happier with them now that they are signed.
[18:51] <directhex> ScottK, i was under the impression there was a debate about the role PPAs were meant to serve - i.e. not signing was an intentional "don't use me!" flag
[18:53] <ScottK> directhex: I think there was a debate, but if it was meant that way, it was far too subtle for most users.
[18:54] <directhex> ScottK, "rm -fr /" is too subtle for most users ¬_¬
[18:54] <ScottK> Certainly.
[18:55] <directhex> hm, my benchmarks of vdpau are promising
[19:09] <ripps> Can someone help me figure out why a PPA plugin pack won't build on intrepid/hardy, but build perfectly on jaunty? I've already taken into account build-depends and autogen.sh scripts.
[19:09] <ScottK> ripps: #launchpad for PPA questions.
[19:35] <fabrice_sp> JontheEchidna, I've been able to build kallery to get rid of aRts. The problem you had is because in the clean target, it was executing the configure target :-/
[19:36] <fabrice_sp> I'll upload the debdiff soon (in Bug #348160)
[20:41] <phaidros> hi. a dependency for calendarserver (jaunty) is python-twisted-calendarserver_0.2.0.svn19773-5ubuntu1_amd64.deb which is trying to overwrite a file from python-twisted-core
[20:42] <phaidros> what to do about it?
[20:42] <phaidros> (I'm no dev, just user)
[20:43] <phaidros> packages.ubuntu.com states to ask @motu before contacting the maintainer :)
[20:47] <geser> please file a bug at launchpad against that package
[20:57] <phaidros> geser: ok
[21:07] <nhandler> dtchen: I am still unable to reproduce that bug inside of a jaunty chroot (pbuilder) on i386.
[21:08] <dtchen> nhandler: it's quite straightforward here. also, there's a known fix; it's unintrusive; it's trivially correct. it kinda makes sense to apply it *before* release.
[21:09] <nhandler> dtchen: I know. However, Luca also said he was unable to reproduce it, so I'm questioning if there is a need.
[21:09] <dtchen> well, that's really up to you guys
[21:10] <nhandler> dtchen: I have to run out for a little bit. I'll look at it again when I get back
[21:10] <dtchen> do you want me to write an exploit PoC or something? ;)
[21:13] <ScottK> nhandler: If dtchen says it needs fixed, I'd fix it.
[21:29] <fabrice_sp> JontheEchidna, I've update Bug #348160 with the patch for kallery (that drop aRts also). If you want to have a look
[21:31] <JontheEchidna> fabrice_sp: col, I can probably look at it after dinner
[21:31] <fabrice_sp> ok. I'll be in my bed at that time ;-)
[21:36] <khashayar> ScottK: TheMuso re-uploaded pencil with an updated copyright file :-)
[21:37] <ScottK> khashayar: Thanks.
[21:44] <khashayar> ScottK: I've been doing little more than pinging people. Thanks go to you.
[21:45] <ScottK> khashayar: Source is accepted.  It'll go to binary New after it builds.
[21:46] <ScottK> khashayar: The short description could be more gramatical.  Try pencil is a _________ and it should flow from that.  The current one is a bit awkward.
[21:46] <khashayar> ScottK: Thanks a lot!
[21:47] <ScottK> khashayar: Thank you for making Ubuntu better.
[21:48] <khashayar> ScottK: So, when I want to tidy things up (like the short description), do I file a bug against the package with a patch?
[22:11] <ScottK> khashayar: Yes.
[22:34] <ausimage> I am wondering if someone could look over a personal project of mine and help me get things up to standards for Jaunty... https://code.edge.launchpad.net/~ausimage/+junk/PbParser
[22:34] <Laney> fabrice_sp: I'm looking at synfigstudio, but the program crashes after the splash screen. Does it run for you?
[22:35] <ausimage> I have it working in with intrepid... but since the python changes in Jaunty I am unclear... I really would like to see this avaible in Karmic ;)
[22:50] <geser> ausimage: I gave it a quick look and it doesn't need any packaging changes due to the python2.6 transition
[22:50] <ausimage> what about the setup switch?
[22:50] <ausimage> to specify the different layout
[22:51] <ausimage> also I had questions if I am putting the icon where it is supposed to be
[22:52] <ausimage> geser?
[22:54] <geser> ausimage: cdbs is patched to do the right thing and you don't have any settings or custom targets which break it
[22:54] <ausimage> ok... I was not sure if the icon going into icon was correct or if it belongs in pixmaps
[22:55] <geser> looking at that icon now
[22:55] <geser> have you checked your desktop file with "desktop-file-validate"?
[22:55] <ausimage> also I a had a question about the best way to include the manpages...
[22:56] <ausimage> um no did not know it existed
[22:56] <geser> and you shouldn't hard-code the path to the icon as it breaks themeing and auto-selecting of the icon format
[22:56] <ausimage> how should I do it?
[22:57] <ausimage> how should I do it?
[22:57] <ausimage> sorry :/
[22:58]  * ausimage pulls up his desktop file
[22:58] <geser> install your pbparse.svg as /usr/share/pbparse.svg and use "Icon = pbparse"
[22:59] <geser> if I remember correctly at least Gnome should find the svg file and use it
[22:59] <ausimage> and cdbs puts it where it supposed?
[23:00] <ausimage> I thought icons should have a specific location under /usr/share??
[23:01] <geser> sorry, missed the pixmaps dir: /usr/share/pixmaps/pbparse.svg
[23:01] <ausimage> and gnome checks there for any images not in the current path?
[23:02] <geser> I don't know exactly the search order but yes, it should find it there (if your icon theme doesn't provide an own one)
[23:16]  * ausimage made geser changes and is awaiting the arrival on his ppa


[09:10] <Guest18389> brightness issue over here
[09:11] <Guest18389> everytime i plug in charger, brightness turns 100%
[09:12] <Guest18389> although that happens the indicator shows previous value itself
[09:13] <Guest18389> now when I change the brightness, the indicator also jumps to100% then adjustsfrom there


[02:04] <moriahnoelle> hello
[02:04] <tsimonq2> Ho
[02:04] <tsimonq2> *Hi
[05:29] <Kamilion> Good news; my ISO boots on an AMD Raven Ridge APU (2200G) to the desktop.
[05:30] <Kamilion> Not bad for 16.04 with 4.13!
[09:16] <sacarde> hi
[09:17] <sacarde> in alternate install Lubuntu, there is a singulare way to configure keyboard
[09:17] <sacarde> by pressing some keys to recognize keyboard
[09:18] <sacarde> is possible to start this in a installed system?
[09:19] <sacarde> something like: dpkg-reconfigure .......
[19:11] <Guest46> Does anybody know how to fix VPN on lubuntu?
[19:12] <wxl> Guest46: works for me. what's wrong?
[19:13] <Guest46> wxl well, no idea really, just that the setup wont read my saved conf file
[19:13] <Guest46> but it works in ubuntu srv 16.0.4
[19:13] <wxl> what version of lubuntu are you using, Guest46 ?
[19:14] <Guest46> 16.0.4
[19:14] <wxl> so assuming you use the same tools, it should work the same. i assume you're not using Network-Manager in ubuntu server, eh?
[19:15] <Guest46> When im trying to load a conf file in lubuntu it just gives me , configuration error: invalid 1th argument to 'reneg-sec' where number expected (line 18).
[19:15] <wxl> that seems like a pretty clear error.....
[19:15] <Guest46> yeah, but when im trying to fix it, i cant connect to it
[19:16] <wxl> how did you "fix it?"
[19:16] <wxl> and what's line 18?
[19:16] <Guest46> if u clear it and it will accept my conf, my connection wont go through
[19:16] <wxl> i'm sure that removing a configuration option isn't going to go well
[19:16] <wxl> most likely your vpn requires it
[19:16] <wxl> but you might need to set it correctly
[19:17] <Guest46> yeah, but to what
[19:17] <wxl> give me the EXACT error and the EXACT content of line 18
[19:18] <Guest46> reneg-sec 432000
[19:19] <wxl> i'm not sure if there's an upper end to it
[19:19] <wxl> the fact that it says it's expecting a number is strange
[19:19] <wxl> can you provide a copy of the file?
[19:20] <wxl> feel free to pull out identifying info. i just want to see the structure of the whole thing
[19:21] <wxl> one thing you can do is just avoid NetworkManager and do openvpn and networking in general just like how you did on server. i'd be shocked if there were a difference there, but maybe
[19:23] <wxl> you also might check for weird characters:
[19:23] <wxl> grep -P -n "[^\x00-\x7F]" /path/to/your/file
[19:26] <Guest4653> hey wxl, well there did i go
[19:26] <Guest4653> i tried something that cleary didnt work
[19:28] <Guest4653> Well okay
[19:28] <Guest4653> I have no idea
[19:28] <wxl> ?
[19:28] <Guest4653> Apparently im on the vpn now
[19:29] <Guest4653> No clear idea what fixed it tho
[19:30] <Guest4653> wxl how did u setup vpn?
[19:32] <wxl> in NetworkManager
[19:34] <Guest4653> well it works atleast
[19:36] <wxl> if it didn't work, some random things happened, and then it did work, there's not much that can be done, so yeah, be happy it works :)
[19:37] <Guest4653> @wxl well, yeah, but i dont really like it in the end
[19:38] <wxl> that's why you got to keep track of that random stuff
[19:38] <wxl> but mine worked right out of the box with no other changes
[19:38] <Guest4653> yeah, but i have been messing with it for a hour and just trying stupid shit
[19:38] <wxl> did you remove the line and rewrite it?
[19:39] <Guest4653> and then getting pinged-out from connection to the vpn and faling, then diconnected then connected and it started working
[19:39] <Guest4653> i just removed it entirely
[19:39] <Guest4653> gonna check if i put it back and set it to 0
[19:39] <wxl> could have been some change on the vpn end
[19:40] <wxl> but it could have been there were some non-printing characters in there that were causing parsing issues, which a rewrite might have fixed
[19:43] <Guest4653> well putting it to 0 works
[19:43] <Guest4653> atleast the conf file
[19:43] <wxl> that just turns it off
[19:43] <Guest4653> yeah
[19:43] <wxl> so there's never any renogiation
[19:44] <wxl> removing it should set it to 3600s
[19:44] <wxl> which means renegotiation every 3600s
[19:44] <wxl> you had it set to a monstrous value
[19:44] <wxl> admittedly the serve needs to match, too, so you should set it to whatever the server suggests
[19:46] <Guest4653> yeah, will try to chat with em tommorow
[19:46] <wxl> if you have further problems, i'd watch the openvpn logging
[19:46] <wxl> chances are the problem lies there
[19:49] <Guest4653> wxl yeah,wich networkmanager did u use?
[19:49] <Guest4653> did u just install gnome?
[19:49] <wxl> no. it's included with lubuntu
[19:50] <Guest4653> Yeah, but the included would allow me to add a VPN connection
[19:50] <wxl> the included is NetworkManager and it certainly does allow it
[19:51] <Guest4653> If u rightclick -> VPN connections -> its grey isnt it?
[19:52] <Guest4653> and if i go to edit connections -> create, vpn wasnt there
[19:52] <wxl> one second
[19:54] <wxl> ugh my virtualbox is being problematic. not in front of lubuntu currently, but i've set that up on two machines before with no problems. so i guess the short answer is: no.
[19:55] <Guest4653> hmm, and ur using the 16.0.4 lub?
[19:55] <wxl> yep
[19:55] <Guest4653> well, what
[19:56] <Guest4653> Now i feel like a reinstallation would be in order, but it was a clean install before also
[19:56] <linguini> I just installed and my M.2 SSD isn't detected.  What must I do to use the SSD?
[19:57] <wxl> linguini: not detected or not mounted?
[19:57] <linguini> wxl: Not detected AFAICT.
[19:57] <wxl> it's always good to start from a fresh state
[19:57] <wxl> linguini: is it showing up in `sudo fdisk -l`?
[19:57] <linguini> wxl: Nope
[19:58] <wxl> 1s
[19:58] <linguini> wxl: FWIW, I've had many problems with virtualbox.  But I don't see your original complaint.
[19:59] <wxl> linguini: in general, vbox is pretty good, but i'm running some bleeding edge stuff right now.
[20:00] <linguini> Oh yes, I love vbox.  But I've also had many problems with it.
[20:01] <redwolf> Guest4653, what VPN are yu using? the provider, I mean
[20:01] <Guest4653> redwolf ovpn
[20:01] <wxl> linguini: can you confirm the BIOS sees that SSD?
[20:01] <redwolf> Guest4653, that's the interface. who is giving you that connection? RiseUp?   I installed lubuntu 16.04.3 and that worked fine.  the kernel version was 4.x.28.  It updated to a 4.x.32 kernel.  the .28 kernel works.  that .32 kernel displays a garbaged gui
 I have an Acer Aspire E and it works nice. does it crash after booting or it never starts?
 anyways, try pressing shift while booting and choose another kernel, just for trying
[22:14] <blue1> lubot: yes the .28 kernel works just fine - I just nuked all the .32 stuff
 good, I guess newer releases have better support for your graphics card or motherboard
[22:19] <krytarik> blue1: Please see if it's LP bug 1724639.
[22:22] <blue1> krytarik: yup that's it
[22:22] <krytarik> Cool, then see the workaround mentioned there.
[22:22] <blue1> except mine is an acer aspire
[22:23] <blue1> okay let me see if I can find the work around
[22:24] <krytarik> The "GRUB_GFXPAYLOAD_LINUX=text" one, to be specific.
[22:26] <blue1> let me search for that b/c I have not found the work around yet
[22:26] <blue1> found it
[22:30] <blue1> okay the gfx_payload is NOT in the file, should I just add it then?
[22:30] <blue1> oh do not edit grub.cfg
[22:30] <krytarik> You edit "/etc/default/grub"
[22:32] <blue1> it's not in that file either -- okay to just add it at the end?
[22:33] <krytarik> Well yes, if it's not there..
[22:35] <blue1> kk
[22:35] <krytarik> Aha, the comments to the bug report indicate that indeed.
[22:35] <blue1> sorry I don't futz with boottime stuff that often.
[22:35] <blue1> thank you for your patience
[22:36] <krytarik> No problem.  And you are welcome. :)
[22:36] <blue1> okay regenerated the file - and re-installing the updates
[22:48] <blue1> It says it's up-to-date with the .28 stuff I will wait and try tomorrow -- thank you again.
[22:48] <blue1> not new to linux, just new to lubuntu
[22:54] <krytarik> blue1: Is the metapackage "linux-generic-hwe-16.04" still installed?  If not, reinstall it: "sudo apt install linux-generic-hwe-16.04"
[22:54] <blue1> krytarik: i think so let me ssh in
[22:55] <blue1> good catch - no it is not installed
[22:56] <blue1> that got it.
[22:56] <krytarik> Good good. :)
[23:04] <blue1> it works -- just like downtown!
[23:04] <krytarik> !yay
[23:05] <blue1> I had never heard of lubuntu till last week -- frankly xubuntu was pretty much taxing the limits of the machine -- this runs very well on this little netbook
[23:10] <hehehe> yes lubuntu is nice
[23:10] <hehehe> very nice
[23:10] <hehehe> who here is into blockchain?
[23:13] <blue1> ah there is no 32 bit skype anymore -- maybe hangouts will work


[00:00] -queuebot:#ubuntu-release- New: accepted flint [ppc64el] (jammy-proposed) [2.8.4-1]
[00:00] -queuebot:#ubuntu-release- New: accepted jquery-datetimepicker [amd64] (jammy-proposed) [2.5.20+ds-1]
[00:00] -queuebot:#ubuntu-release- New: accepted flint [s390x] (jammy-proposed) [2.8.4-1]
[00:30] -queuebot:#ubuntu-release- New binary: libstdc++-arm-none-eabi [amd64] (jammy-proposed/universe) [14] (no packageset)
[03:31] -queuebot:#ubuntu-release- New binary: opentracing-cpp [s390x] (jammy-proposed/universe) [1.6.0-2ubuntu1] (no packageset)
[03:32] -queuebot:#ubuntu-release- New binary: opentracing-cpp [amd64] (jammy-proposed/universe) [1.6.0-2ubuntu1] (no packageset)
[03:32] -queuebot:#ubuntu-release- New binary: opentracing-cpp [ppc64el] (jammy-proposed/universe) [1.6.0-2ubuntu1] (no packageset)
[03:33] -queuebot:#ubuntu-release- New binary: opentracing-cpp [armhf] (jammy-proposed/universe) [1.6.0-2ubuntu1] (no packageset)
[03:35] -queuebot:#ubuntu-release- New binary: opentracing-cpp [arm64] (jammy-proposed/universe) [1.6.0-2ubuntu1] (no packageset)
[03:53] -queuebot:#ubuntu-release- New binary: opentracing-cpp [riscv64] (jammy-proposed/universe) [1.6.0-2ubuntu1] (no packageset)
[04:01] <sergiodj> ubuntu-archive: hi, I need someone to approve opentracing-cpp for me please.  it's a fix for an FTBFS with glibc 2.34.   What hint do you suggest me to add to make its test ignored?
[08:29] <vorlon> mitya57: ah I meant to take care of that yesterday, sorry - I've just added a skiptest for sphinx
[08:30] <mitya57> Thanks a lot!
[08:36] <ricotz> vorlon, hello, is it possible to finish the poppler transition with rebuilds of gambas3 and gdal?
[09:59] -queuebot:#ubuntu-release- New binary: opentracing-c-wrapper [amd64] (jammy-proposed/universe) [1.1.3-3] (no packageset)
[09:59] -queuebot:#ubuntu-release- New binary: opentracing-c-wrapper [s390x] (jammy-proposed/universe) [1.1.3-3] (no packageset)
[10:00] -queuebot:#ubuntu-release- New binary: opentracing-c-wrapper [arm64] (jammy-proposed/universe) [1.1.3-3] (no packageset)
[10:00] -queuebot:#ubuntu-release- New binary: opentracing-c-wrapper [ppc64el] (jammy-proposed/universe) [1.1.3-3] (no packageset)
[10:00] -queuebot:#ubuntu-release- New binary: opentracing-c-wrapper [armhf] (jammy-proposed/universe) [1.1.3-3] (no packageset)
[10:16] -queuebot:#ubuntu-release- New binary: opentracing-c-wrapper [riscv64] (jammy-proposed/universe) [1.1.3-3] (no packageset)
[18:39] <vorlon> ricotz: I don't know what currently blocks the poppler transition, sorry
[18:40] <vorlon> ricotz: a quick glance shows that there are at least some unresolved autopkgtest regressions
[18:40] -queuebot:#ubuntu-release- New: accepted opentracing-c-wrapper [amd64] (jammy-proposed) [1.1.3-3]
[18:40] -queuebot:#ubuntu-release- New: accepted opentracing-c-wrapper [armhf] (jammy-proposed) [1.1.3-3]
[18:40] -queuebot:#ubuntu-release- New: accepted opentracing-c-wrapper [riscv64] (jammy-proposed) [1.1.3-3]
[18:40] -queuebot:#ubuntu-release- New: accepted opentracing-c-wrapper [arm64] (jammy-proposed) [1.1.3-3]
[18:40] -queuebot:#ubuntu-release- New: accepted opentracing-c-wrapper [s390x] (jammy-proposed) [1.1.3-3]
[18:40] -queuebot:#ubuntu-release- New: accepted opentracing-c-wrapper [ppc64el] (jammy-proposed) [1.1.3-3]
[18:41] <ricotz> vorlon, hi, I have pushed a new libreoffice in the meantime so this will take a while to finish
[18:42] <ricotz> I meant this missing rebuilds https://people.canonical.com/~ubuntu-archive/transitions/html/auto-poppler.html
[18:43] <ricotz> which will interfere with their respective transitions, gdal and glew
[18:43] <vorlon> yes
[18:51] <ricotz> vorlon, so finishing the underlying transitions first would be preferred instead of creating specials builds for gambas3/gdal
[18:51] <ricotz> regarding gdal, its blocker seems to be https://launchpad.net/ubuntu/+source/postgis/3.1.4+dfsg-3build1/+build/22346629
[18:51] <vorlon> if you mean a special build against new poppler without new glew, yes
[18:54] <ricotz> I guess there is way more to it to fix gdal :\
[23:20] -queuebot:#ubuntu-release- New binary: golang-github-go-git-go-billy [amd64] (jammy-proposed/none) [5.3.1-2] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: node-logform [amd64] (jammy-proposed/none) [2.2.0-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: node-fast-safe-stringify [amd64] (jammy-proposed/none) [2.0.7-2] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: postgresql-semver [ppc64el] (jammy-proposed/universe) [0.31.2-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: postgresql-semver [armhf] (jammy-proposed/universe) [0.31.2-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: postgresql-semver [s390x] (jammy-proposed/universe) [0.31.2-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: golang-github-andybalholm-brotli [amd64] (jammy-proposed/none) [1.0.4-2] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: golang-github-juju-mutex [amd64] (jammy-proposed/none) [0.0~git20180619.d21b13a-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: node-stack-trace [amd64] (jammy-proposed/none) [0.0.10-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: golang-github-juju-clock [amd64] (jammy-proposed/none) [0.0~git20190205.9c5c971-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: node-wikibase-sdk [amd64] (jammy-proposed/none) [7.14.0+ds-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: node-oauth-1.0a [amd64] (jammy-proposed/none) [2.2.6-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: golang-gopkg-juju-environschema.v1 [amd64] (jammy-proposed/none) [1.0.0-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: node-hsluv [amd64] (jammy-proposed/none) [0.1.0+dfsg1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: node-one-time [amd64] (jammy-proposed/none) [1.0.0-2] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: postgresql-semver [amd64] (jammy-proposed/universe) [0.31.2-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: node-colorspace [amd64] (jammy-proposed/none) [1.1.2-2] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: node-propagate [amd64] (jammy-proposed/none) [2.0.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: node-http-proxy [amd64] (jammy-proposed/none) [1.18.1-2] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: postgresql-semver [arm64] (jammy-proposed/universe) [0.31.2-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: node-kuler [amd64] (jammy-proposed/none) [2.0.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: node-mersenne [amd64] (jammy-proposed/none) [0.0.4-2] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: postgresql-semver [riscv64] (jammy-proposed/universe) [0.31.2-1] (no packageset)