[11:44] <N`importe_qui> MarwenDo: ah you're not from the insat
[11:45] <MarwenDo> ok
[11:45] <N`importe_qui> esprit
[11:45] <N`importe_qui> got you
[11:45] <MarwenDo> ok
[11:46] <N`importe_qui> marwen doukh c'est ça?
[11:46] <N`importe_qui> lewl it's obvious
[11:48] <N`importe_qui> meh you're boring
[11:48] <MarwenDo> thank you , you too
[14:13] <elacheche> Salam!
[14:20] <MarwenDo> Salem
[14:23] <elacheche> Wassup MarwenDo :)
[14:23] <MarwenDo> 7amdoullah elacheche
[14:29] <elacheche> :)
[17:10]  * N`importe_qui pats Na3iL .
[17:26] <elacheche> N`importe_qui: You can use a better nickname :)
[18:19] <N`importe_qui> elacheche: o...key
[18:29] <elacheche> elacheche_X: how old are you? 5?
[18:30] <elacheche_X> 5 decades? yep
[18:33] <damascene> elacheche, a member of your family here 😊
[18:34] <elacheche> Nope damascene.. That's a fake one :) There is only 2 family members joins here.. And everyone knows them very well.. damascene I'll be happy to introduce them to you someday :)
[18:35] <damascene> elacheche, it's my honor to know more elacheches 😊
[18:36] <elacheche> :) Thank you dude :)
[18:36] <elacheche> Yo Dro !!! Sliktich inti wil apt? x)
[18:36] <Dro> hhhhhhhh nn
[18:37] <Dro> bonsoir tlm
[18:37] <Dro> elacheche, dima n3ani 5ouk :p
[18:37] <elacheche> Iltaw! Really!
[18:37] <Dro> oui , pas de solution :/
[18:38] <Dro> mabrouk el shell :p
[18:38] <elacheche> May I get a ssh access to your machine? It can be easier for me to debug the issue
[18:38] <elacheche> Dro | mabrouk el shell :p    → I don't get it!
[18:38] <Dro> zayed ya elacheche il y a pas de solution :/
[18:39] <elacheche> Dro: There is always a solution.. It's not a WinBugs :p
[18:39] <elacheche> :D
[18:39] <Dro> mela chnowa hetha, blinkenshell :p
[18:39] <elacheche_X> i'm sorry what?
[18:39] <elacheche_X> disgusting
[18:39] <elacheche> x)
[18:39] <Dro> N`importe_qui, you can install a bnc instead of using irssi :p
[18:40] <Dro> welcome Na3iL :D
[18:41] <Na3iL> Hey Dro
[18:41] <Na3iL> wassup
[18:41] <Dro> nestannaw fik
[18:41] <N`importe_qui> Dro: what? what do you think i'm using here
[18:42] <Na3iL> abay! why :p
[18:42] <N`importe_qui> Dro: blinkenshell is a whole shell service for the elites, nab
[18:43] <Dro> Na3iL, 3anna zarda
[18:43] <Na3iL> I can see
[18:43] <Dro> elacheche, bech yathb7elna djeja ! xD
[18:50] <N`importe_qui> apt-get install djeja
[18:50] <Dro> lool
[18:56] <elacheche> N`importe_qui: You liked our channel?
[19:22] <N`importe_qui> elacheche: not bad, not bad.
[19:22] <elacheche> :)
[19:43]  * Dro enjoying Ubuntu without errors for the first time since a couple of months ~~
[19:44] <N`importe_qui> Dro: why, what was happening there
[19:45] <Dro> N`importe_qui, errors everywhere! :P
[19:46] <N`importe_qui> Dro: what kind of errors, elaborate
[19:46] <Dro> + I changed my HDD with all my files .... etc
[19:46] <N`importe_qui> don't gimme that crap
[19:46] <Dro> I loosed everything :/
[19:46] <N`importe_qui> you mean you lost your files ?
[19:46] <Dro> my files, my time, my projects... everything almost
[19:47] <Dro> getting :@ this days ..
[19:50] <N`importe_qui> i'm asking you what kind of errors you have been facing
[19:51] <Dro> i can tell you about the kind of errors that i have not faced yet :D
[19:51] <N`importe_qui> 'key whateva'
[19:52] <Dro> whatever
[20:13] <elacheche> N`importe_qui: When the HD fails, you'll see all kind of errors.. :)
[20:13] <N`importe_qui> meh, he was not clear at all anyway
[20:13] <N`importe_qui> not that i'm interested now
[20:23] <elacheche> N`importe_qui: We almost live here in this channel.. So we know each others, we know each others issues, backgrounds, assets, and we built the ability to understand each others faster :)
[20:23] <elacheche> You'll get used to that if you're planning to stay here..
[20:23] <elacheche> am I wrong Dro :)
[20:23] <elacheche> ?
[20:25] <N`importe_qui> you are.
[20:26] <Dro> N`importe_qui, you are
[20:26] <Dro> :D
[20:26] <elacheche> You have no idea N`importe_qui :) I even know 80% of people you met here IRL :)
[20:27] <N`importe_qui> elacheche: okey, we'll meet IRL then
[20:27] <Dro> N`importe_qui, who are you?
[20:28] <N`importe_qui> Dro: whoeva'
[20:28] <N`importe_qui> elacheche: imma head to Valomnia, and knock your office's door
[20:28] <N`importe_qui> lulz
[20:28] <N`importe_qui> or Apptiv-it
[20:28] <N`importe_qui> or wherever you work
[20:28] <N`importe_qui> lewl
[20:28] <Dro> lewl
[20:30] <elacheche> I have no idea with that.. I meet tens of people every day, in the street, in fast foods, but people I know from here and from the FOSS community are special..  :D
[20:37] <N`importe_qui> Dro: deal with that
[20:37] <N`importe_qui> ahah
[20:37] <elacheche> 1 hour 30 min ago Dro :)
[20:37] <Dro> N`importe_qui have you ever worked with FBI ?
[20:37] <N`importe_qui> Dro: lulz, fo i look like some fbi agent?
[20:37] <N`importe_qui> rofl
[20:38] <Dro> lets see if u can find any data about me :P
[20:43] <N`importe_qui> Dro: you reside in /dev/null , you don't..exist.
[20:44] <Dro> col
[20:44] <Dro> cool :D
[20:44] <Dro> just like you
[21:18] <N`importe_qui> Dro: ah bon ?
[21:24] <Na3iL> elacheche, you think I should nominate myself for the Ubuntu Irc Council?
[21:25] <elacheche> why not :)
[21:25] <elacheche> I'm thinking about that too x)
[21:25] <nizarus> salam
[21:25] <elacheche> I missed the cc nomination withen a day x(
[21:26] <elacheche> salam nizarus :)
[21:26] <Na3iL> salam nizarus o/
[21:26] <nizarus> ça va les exams elacheche :)
[21:26] <Na3iL> okay, then I will do it
[21:27] <elacheche> yep :D Just 2 more next week and I hope that everything gonna be alright for this semester
[21:28] <elacheche> yep :D Just 2 more next week and I hope that everything gonna be alright for this semester
[21:29] <elacheche> How are you nizarus
[21:30] <nizarus> :)
[21:30] <nizarus> ça va
[21:33] <elacheche> :)
[21:42] <Na3iL> elacheche, btw, should I grab new testimonials for it, or just the old testimonials of Ubuntu membership are enough?
[21:52] <elacheche> not idea Na3iL
[21:53] <Na3iL> okay


[01:14] <handsome_feng> By any chance, could someone help check the ukui-menus in bionic new queue? Thanks a lot!
[02:11] -queuebot:#ubuntu-release- New source: python-libmaas (bionic-proposed/primary) [0.5.0-0ubuntu1]
[05:12] -queuebot:#ubuntu-release- New binary: flask-login [amd64] (bionic-proposed/universe) [0.4.0-2] (no packageset)
[06:27] -queuebot:#ubuntu-release- New binary: poco [s390x] (bionic-proposed/universe) [<IP_ADDRESS>-1ubuntu1] (no packageset)
[06:28] -queuebot:#ubuntu-release- New binary: poco [i386] (bionic-proposed/universe) [<IP_ADDRESS>-1ubuntu1] (no packageset)
[06:30] -queuebot:#ubuntu-release- New binary: poco [ppc64el] (bionic-proposed/universe) [<IP_ADDRESS>-1ubuntu1] (no packageset)
[06:31] -queuebot:#ubuntu-release- New binary: poco [amd64] (bionic-proposed/universe) [<IP_ADDRESS>-1ubuntu1] (no packageset)
[06:36] -queuebot:#ubuntu-release- New: accepted poco [s390x] (bionic-proposed) [<IP_ADDRESS>-1ubuntu1]
[06:36] -queuebot:#ubuntu-release- New: accepted poco [amd64] (bionic-proposed) [<IP_ADDRESS>-1ubuntu1]
[06:36] -queuebot:#ubuntu-release- New: accepted poco [ppc64el] (bionic-proposed) [<IP_ADDRESS>-1ubuntu1]
[06:36] -queuebot:#ubuntu-release- New: accepted poco [i386] (bionic-proposed) [<IP_ADDRESS>-1ubuntu1]
[06:43] -queuebot:#ubuntu-release- New binary: poco [armhf] (bionic-proposed/universe) [<IP_ADDRESS>-1ubuntu1] (no packageset)
[06:46] -queuebot:#ubuntu-release- New binary: poco [arm64] (bionic-proposed/universe) [<IP_ADDRESS>-1ubuntu1] (no packageset)
[07:20] -queuebot:#ubuntu-release- New: accepted meta-kde [amd64] (bionic-proposed) [5:99]
[07:20] -queuebot:#ubuntu-release- New: accepted meta-kde [armhf] (bionic-proposed) [5:99]
[07:20] -queuebot:#ubuntu-release- New: accepted meta-kde [ppc64el] (bionic-proposed) [5:99]
[07:20] -queuebot:#ubuntu-release- New: accepted meta-kde [arm64] (bionic-proposed) [5:99]
[07:20] -queuebot:#ubuntu-release- New: accepted meta-kde [s390x] (bionic-proposed) [5:99]
[07:20] -queuebot:#ubuntu-release- New: accepted meta-kde [i386] (bionic-proposed) [5:99]
[07:20] -queuebot:#ubuntu-release- New: accepted gcc-3.3 [amd64] (bionic-proposed) [1:3.3.6ds1-30]
[07:20] -queuebot:#ubuntu-release- New: accepted qpack [amd64] (bionic-proposed) [0.0.17-1]
[07:20] -queuebot:#ubuntu-release- New: accepted qpack [armhf] (bionic-proposed) [0.0.17-1]
[07:20] -queuebot:#ubuntu-release- New: accepted qpack [ppc64el] (bionic-proposed) [0.0.17-1]
[07:20] -queuebot:#ubuntu-release- New: accepted gcc-3.3 [i386] (bionic-proposed) [1:3.3.6ds1-30]
[07:20] -queuebot:#ubuntu-release- New: accepted qpack [i386] (bionic-proposed) [0.0.17-1]
[07:20] -queuebot:#ubuntu-release- New: accepted qpack [arm64] (bionic-proposed) [0.0.17-1]
[07:20] -queuebot:#ubuntu-release- New: accepted qpack [s390x] (bionic-proposed) [0.0.17-1]
[07:21] -queuebot:#ubuntu-release- New: accepted flask-login [amd64] (bionic-proposed) [0.4.0-2]
[07:21] -queuebot:#ubuntu-release- New: accepted python-aiomeasures [amd64] (bionic-proposed) [0.5.14-1]
[07:21] -queuebot:#ubuntu-release- New: accepted ibm-3270 [amd64] (bionic-proposed) [3.6ga4-1]
[07:21] -queuebot:#ubuntu-release- New: accepted python-libmaas [source] (bionic-proposed) [0.5.0-0ubuntu1]
[07:23] -queuebot:#ubuntu-release- New binary: python-libmaas [amd64] (bionic-proposed/none) [0.5.0-0ubuntu1] (no packageset)
[07:46] <slangasek> jbicha: do you have any idea about the gtk-doc FTBFS? I haven't been able to reproduce it here so far
[07:50] <fossfreedom_> Anyone around who can have a look why http://people.canonical.com/~ubuntu-archive/seeds/ubuntu-budgie.bionic/ hasn't been updated since December?  I'm trying to work out why our meta binary package ubuntu-budgie-desktop is not being installed on our daily iso's.  TIA
[07:50] <valorie> fossfreedom_: imo you just need to ask someone to update it
[07:51] <valorie> I don't believe it is automatic
[07:51] <fossfreedom_> valorie, who can I ping?
[07:52] <slangasek> those are certainly automatic
[07:52] <valorie> hmmm, I was misinformed then
[07:52] <valorie> sorry
[07:53] <slangasek> I've just manually pulled and it worked, but it shouldn't have needed to be manual; digging
[07:53] <fossfreedom_> thanks slangasek
[08:03] <handsome_feng> By any chance, could someone help check the ukui-menus in bionic new queue? Thanks a lot!
[08:03] <slangasek> fossfreedom: it's because the support for pulling seeds from git didn't reset a variable, and any branches appearing after the first git branch in the list are attempted via git, which fails
[08:05] <slangasek> handsome_feng: I plan to look at it in my morning if no one does before that
[08:05] <handsome_feng> slangasek: Thank you very much! :)
[08:07] <fossfreedom> ah.  Would this somehow explain why our meta binary isn't being installed on our ISO slangasek ?  Is the seed web-page and the iso build linked?
[08:07] <slangasek> fossfreedom: no
[08:09] <doko> now I removed the ruby-ferret armhf binary, but the autopkg test still refers to the test failure. how to fix that?
[08:12] <slangasek> doko: MP against lp:~ubuntu-release/britney/hints-ubuntu to mark it badtest with rationale
[08:13] <doko> slangasek: which user should be used?
[08:13] <slangasek> doko: doesn't matter
[08:18] <doko> ok, in general, why isn't that removal not done automatically?
[08:19] <slangasek> because it's complex software with corner cases
[08:21] -queuebot:#ubuntu-release- New binary: python-molotov [amd64] (bionic-proposed/universe) [1.4-1] (no packageset)
[08:32] -queuebot:#ubuntu-release- New: accepted python-libmaas [amd64] (bionic-proposed) [0.5.0-0ubuntu1]
[08:32] -queuebot:#ubuntu-release- New: accepted python-molotov [amd64] (bionic-proposed) [1.4-1]
[08:55] <tjaalton> cpaelzer: apparently nss upstream changed the default cert database format to SQL, which is why things blew up with dogtag/freeipa..
[08:55] <tjaalton> on debian too, it seems
[08:56] <cpaelzer> tjaalton: oh really
[08:57] <cpaelzer> yeah that would "explain" :-/
[08:57] <cpaelzer> but then my +really approach might be the best short term solution to not bust a lot of things
[08:58] <cpaelzer> thdo you happen to know if there is any migration action defined by upstream?
[08:58] <tjaalton> for nss?
[08:58] <cpaelzer> tjaalton: ^^
[08:58] <cpaelzer> sorry thdo
[08:58] <cpaelzer> yes for nss
[08:58] <tjaalton> upstream of freeipa?
[08:58] <tjaalton> yse
[08:58] <tjaalton> yes
[08:58] <cpaelzer> yeah I'd turn back nss to 3.34 to not break, and give things some time to solve that
[08:59] <cpaelzer> I already started some tests in that regard
[09:17] -queuebot:#ubuntu-release- New: accepted poco [arm64] (bionic-proposed) [<IP_ADDRESS>-1ubuntu1]
[09:17] -queuebot:#ubuntu-release- New: accepted poco [armhf] (bionic-proposed) [<IP_ADDRESS>-1ubuntu1]
[09:51] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (artful-proposed/main) [1:17.10.9 => 1:17.10.10] (core)
[10:07] <fossfreedom_> think we have an oops moment for ubuntu budgie artful - our meta package ubuntu-budgie-desktop doesnt appear to be installed on our ISO.  That's needed for upgrading correct? Any thoughts on how to retrospectively fix this?  Maybe add a "recommends" to another package that will be always installed like "budgie-desktop-environment" ?
[10:18] <ginggs> would someone please 'force-badtest octave-symbolic/amd64/2.6.0-2 octave-symbolic/ppc64el/2.6.0-2' ?  i believe it has regressed in release, and blocks octave + gdal from migrating
[10:24] <krytarik> fossfreedom_: You could add Budgie here, which would be a good idea anyway: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/trunk/view/head:/data/DistUpgrade.cfg
[10:29] <cpaelzer> tjaalton: after a lot of other distractions I got to the test of the revert of nss to 3.34
[10:29] <cpaelzer> tjaalton: worked in the tests as expected, see updates to bug 1746947
[10:30] <cpaelzer> I think I upload the 3.34 now to unbreak things for now
[10:30] <cpaelzer> tjaalton: would you mind taking a look and ack'ing if you are ok with that approach?
[10:33] <tjaalton> cpaelzer: reverting this might be enough https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3
[10:33] <cpaelzer> yeah, this could make the new code with all old things for now
[10:33] <cpaelzer> taking a look
[10:33] <cpaelzer> thanks tjaalton
[10:44] <infinity> fossfreedom_: Was your meta not part of the desktop task?
[10:45] <infinity> Sure isn't.
[10:50] <infinity> fossfreedom_: Fixed in your seeds for bionic.  But yes, the workaround for dist-upgrader will be to key on budgie-desktop-environment to detect that it's a budgie install, and then install ubuntu-budgie-desktop
[10:54] <fossfreedom_> infinity: I added "ubuntu-budgie-desktop" on line 33 of the desktop seed yesterday and ran a rebuild of the 64bit ISO - it unfortunately didnt add the package to the rebuilt ISO.  I'll double check again on todays daily though
[10:55] <infinity> fossfreedom_: Oh, so you did, now it's there twice. :P
[10:55]  * infinity fixes.
[10:55] <infinity> Not sure how I missed that.
[10:56] <infinity> fossfreedom_: You'll know it's working when "apt-cache show ubuntu-budgie-desktop" shows it in Task: ubuntu-budgie-desktop
[10:56] <fossfreedom_> krytarik: ta - I'll have look later and will do a pull-request
[10:57] <infinity> fossfreedom_: I'm poking at ubuntu-release-upgrader now.
[10:58] <fossfreedom_> cheers
[10:58] <krytarik> I'd sling in another, Ubuntu Budgie specific, package there though.
[11:00] <infinity> http://paste.ubuntu.com/26523910/
[11:00] <infinity> Something like that was what I was thinking.
[11:01] <infinity> As for the seed change not taking, it may just be that bionic hasn't been re-published since.
[11:02] <infinity> Unsticking something from proposed will fix that. :P
[11:02] <fossfreedom_> sure - "budgie-desktop-environment" will always be installed for Ubuntu Budgie
[11:04] <fossfreedom_> late last night I did a no change rebuild of ubuntu-budgie-meta.  That has now migrated from proposed to release.  As you say - hopefully things will kick into gear on the next build
[11:05] <infinity> fossfreedom_: Rebuilding the meta shouldn't be necessary.  It's really just a question of LP deciding to add that Task tag in Packages.gz
[11:05] <krytarik> Funnily enough, I thought one could, like with the other desktop environments, install Budgie without the Ubuntu Budgie bits. :P
[11:06] <fossfreedom_> krytarik: yep you can - just install "budgie-desktop" - that is the vanilla desktop
[11:08] <krytarik> Ok yeah, seems like indeed - I'd have thought budgie-desktop-common would be ranked *below* that, as usual. :P
[11:09] -queuebot:#ubuntu-release- New binary: dashel [i386] (bionic-proposed/none) [1.3.3-2] (no packageset)
[11:09] -queuebot:#ubuntu-release- New binary: el-ixir [amd64] (bionic-proposed/none) [3.0-1] (no packageset)
[11:09] -queuebot:#ubuntu-release- New binary: dashel [s390x] (bionic-proposed/none) [1.3.3-2] (no packageset)
[11:09] -queuebot:#ubuntu-release- New binary: jupyter-core [amd64] (bionic-proposed/universe) [4.4.0-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: csvkit [amd64] (bionic-proposed/universe) [1.0.2-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: dashel [ppc64el] (bionic-proposed/none) [1.3.3-2] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: el-ixir [i386] (bionic-proposed/none) [3.0-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: pytest-remotedata [ppc64el] (bionic-proposed/none) [0.2.0-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: swiglpk [ppc64el] (bionic-proposed/none) [1.4.4-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: dashel [amd64] (bionic-proposed/none) [1.3.3-2] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: pcre2 [s390x] (bionic-proposed/universe) [10.22-6] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: swiglpk [s390x] (bionic-proposed/none) [1.4.4-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: el-ixir [arm64] (bionic-proposed/none) [3.0-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: pytest-remotedata [s390x] (bionic-proposed/none) [0.2.0-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: el-ixir [armhf] (bionic-proposed/none) [3.0-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: enki-aseba [s390x] (bionic-proposed/none) [1:1.6.0-2] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: chemps2 [s390x] (bionic-proposed/universe) [1.8.5-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: enki-aseba [ppc64el] (bionic-proposed/none) [1:1.6.0-2] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: pcre2 [ppc64el] (bionic-proposed/universe) [10.22-6] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: dashel [arm64] (bionic-proposed/none) [1.3.3-2] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: pcre2 [amd64] (bionic-proposed/universe) [10.22-6] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: fcitx [s390x] (bionic-proposed/universe) [1:<IP_ADDRESS>-1] (input-methods, kubuntu, ubuntu-desktop)
[11:12] -queuebot:#ubuntu-release- New binary: golang-github-disintegration-imaging [amd64] (bionic-proposed/none) [1.3.0-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: chemps2 [amd64] (bionic-proposed/universe) [1.8.5-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: dashel [armhf] (bionic-proposed/none) [1.3.3-2] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: golang-go4 [amd64] (bionic-proposed/none) [0.0~git20180103.fba789b-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: swiglpk [amd64] (bionic-proposed/none) [1.4.4-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: chemps2 [ppc64el] (bionic-proposed/universe) [1.8.5-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: pcre2 [i386] (bionic-proposed/universe) [10.22-6] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: enki-aseba [amd64] (bionic-proposed/none) [1:1.6.0-2] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: swiglpk [i386] (bionic-proposed/none) [1.4.4-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: chemps2 [i386] (bionic-proposed/universe) [1.8.5-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: geany-plugins [s390x] (bionic-proposed/universe) [1.32+dfsg-3] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: fcitx [ppc64el] (bionic-proposed/universe) [1:<IP_ADDRESS>-1] (input-methods, kubuntu, ubuntu-desktop)
[11:13] -queuebot:#ubuntu-release- New binary: pytest-remotedata [amd64] (bionic-proposed/none) [0.2.0-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: pcre2 [armhf] (bionic-proposed/universe) [10.22-6] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: pytest-remotedata [i386] (bionic-proposed/none) [0.2.0-1] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: fcitx [amd64] (bionic-proposed/universe) [1:<IP_ADDRESS>-1] (input-methods, kubuntu, ubuntu-desktop)
[11:14] -queuebot:#ubuntu-release- New binary: pcre2 [arm64] (bionic-proposed/universe) [10.22-6] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: chemps2 [arm64] (bionic-proposed/universe) [1.8.5-1] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: enki-aseba [arm64] (bionic-proposed/none) [1:1.6.0-2] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: chemps2 [armhf] (bionic-proposed/universe) [1.8.5-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: enki-aseba [i386] (bionic-proposed/none) [1:1.6.0-2] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: fcitx [i386] (bionic-proposed/universe) [1:<IP_ADDRESS>-1] (input-methods, kubuntu, ubuntu-desktop)
[11:16] -queuebot:#ubuntu-release- New binary: golang-1.10 [s390x] (bionic-proposed/none) [1.10~rc1-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: geany-plugins [ppc64el] (bionic-proposed/universe) [1.32+dfsg-3] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: fcitx [arm64] (bionic-proposed/universe) [1:<IP_ADDRESS>-1] (input-methods, kubuntu, ubuntu-desktop)
[11:16] -queuebot:#ubuntu-release- New binary: pytest-remotedata [armhf] (bionic-proposed/none) [0.2.0-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: pytest-remotedata [arm64] (bionic-proposed/none) [0.2.0-1] (no packageset)
[11:16] -queuebot:#ubuntu-release- New binary: swiglpk [arm64] (bionic-proposed/none) [1.4.4-1] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: geany-plugins [i386] (bionic-proposed/universe) [1.32+dfsg-3] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: gsoap [s390x] (bionic-proposed/universe) [2.8.60-2] (no packageset)
[11:17] -queuebot:#ubuntu-release- New: accepted golang-1.10 [s390x] (bionic-proposed) [1.10~rc1-1]
[11:17] -queuebot:#ubuntu-release- New: accepted swiglpk [amd64] (bionic-proposed) [1.4.4-1]
[11:18] -queuebot:#ubuntu-release- New: accepted golang-github-disintegration-imaging [amd64] (bionic-proposed) [1.3.0-1]
[11:19] -queuebot:#ubuntu-release- New binary: fcitx [armhf] (bionic-proposed/universe) [1:<IP_ADDRESS>-1] (input-methods, kubuntu, ubuntu-desktop)
[11:19] -queuebot:#ubuntu-release- New binary: swiglpk [armhf] (bionic-proposed/none) [1.4.4-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- New: accepted csvkit [amd64] (bionic-proposed) [1.0.2-1]
[11:19] -queuebot:#ubuntu-release- New: accepted jupyter-core [amd64] (bionic-proposed) [4.4.0-1]
[11:19] -queuebot:#ubuntu-release- New binary: golang-1.10 [ppc64el] (bionic-proposed/none) [1.10~rc1-1] (no packageset)
[11:19] -queuebot:#ubuntu-release- New: accepted el-ixir [amd64] (bionic-proposed) [3.0-1]
[11:19] -queuebot:#ubuntu-release- New binary: geany-plugins [amd64] (bionic-proposed/universe) [1.32+dfsg-3] (no packageset)
[11:19] -queuebot:#ubuntu-release- New: accepted chemps2 [amd64] (bionic-proposed) [1.8.5-1]
[11:19] -queuebot:#ubuntu-release- New: accepted chemps2 [armhf] (bionic-proposed) [1.8.5-1]
[11:19] -queuebot:#ubuntu-release- New: accepted chemps2 [ppc64el] (bionic-proposed) [1.8.5-1]
[11:20] -queuebot:#ubuntu-release- New binary: golang-1.10 [i386] (bionic-proposed/none) [1.10~rc1-1] (no packageset)
[11:20] -queuebot:#ubuntu-release- New: accepted chemps2 [arm64] (bionic-proposed) [1.8.5-1]
[11:20] -queuebot:#ubuntu-release- New binary: golang-1.10 [amd64] (bionic-proposed/none) [1.10~rc1-1] (no packageset)
[11:20] -queuebot:#ubuntu-release- New: accepted chemps2 [i386] (bionic-proposed) [1.8.5-1]
[11:20] -queuebot:#ubuntu-release- New: accepted chemps2 [s390x] (bionic-proposed) [1.8.5-1]
[11:20] -queuebot:#ubuntu-release- New binary: openmsx [s390x] (bionic-proposed/universe) [0.14.0-2] (no packageset)
[11:20] -queuebot:#ubuntu-release- New: accepted pcre2 [arm64] (bionic-proposed) [10.22-6]
[11:20] -queuebot:#ubuntu-release- New: accepted pcre2 [i386] (bionic-proposed) [10.22-6]
[11:20] -queuebot:#ubuntu-release- New: accepted pcre2 [armhf] (bionic-proposed) [10.22-6]
[11:20] -queuebot:#ubuntu-release- New binary: geany-plugins [arm64] (bionic-proposed/universe) [1.32+dfsg-3] (no packageset)
[11:21] -queuebot:#ubuntu-release- New: accepted pcre2 [amd64] (bionic-proposed) [10.22-6]
[11:21] -queuebot:#ubuntu-release- New: accepted pcre2 [s390x] (bionic-proposed) [10.22-6]
[11:21] -queuebot:#ubuntu-release- New: accepted pcre2 [ppc64el] (bionic-proposed) [10.22-6]
[11:21] -queuebot:#ubuntu-release- New binary: geany-plugins [armhf] (bionic-proposed/universe) [1.32+dfsg-3] (no packageset)
[11:21] -queuebot:#ubuntu-release- New: accepted dashel [arm64] (bionic-proposed) [1.3.3-2]
[11:22] -queuebot:#ubuntu-release- New: accepted dashel [armhf] (bionic-proposed) [1.3.3-2]
[11:22] -queuebot:#ubuntu-release- New: accepted dashel [amd64] (bionic-proposed) [1.3.3-2]
[11:22] -queuebot:#ubuntu-release- New: accepted dashel [ppc64el] (bionic-proposed) [1.3.3-2]
[11:22] -queuebot:#ubuntu-release- New: accepted dashel [i386] (bionic-proposed) [1.3.3-2]
[11:22] -queuebot:#ubuntu-release- New: accepted dashel [s390x] (bionic-proposed) [1.3.3-2]
[11:23] -queuebot:#ubuntu-release- New: accepted geany-plugins [amd64] (bionic-proposed) [1.32+dfsg-3]
[11:23] -queuebot:#ubuntu-release- New: accepted geany-plugins [armhf] (bionic-proposed) [1.32+dfsg-3]
[11:23] -queuebot:#ubuntu-release- New: accepted geany-plugins [s390x] (bionic-proposed) [1.32+dfsg-3]
[11:23] -queuebot:#ubuntu-release- New: accepted geany-plugins [arm64] (bionic-proposed) [1.32+dfsg-3]
[11:23] -queuebot:#ubuntu-release- New binary: gsoap [amd64] (bionic-proposed/universe) [2.8.60-2] (no packageset)
[11:23] -queuebot:#ubuntu-release- New: accepted geany-plugins [ppc64el] (bionic-proposed) [1.32+dfsg-3]
[11:23] -queuebot:#ubuntu-release- New: accepted geany-plugins [i386] (bionic-proposed) [1.32+dfsg-3]
[11:23] -queuebot:#ubuntu-release- New: accepted fcitx [amd64] (bionic-proposed) [1:<IP_ADDRESS>-1]
[11:23] -queuebot:#ubuntu-release- New: accepted fcitx [armhf] (bionic-proposed) [1:<IP_ADDRESS>-1]
[11:23] -queuebot:#ubuntu-release- New: accepted fcitx [ppc64el] (bionic-proposed) [1:<IP_ADDRESS>-1]
[11:24] -queuebot:#ubuntu-release- New: accepted pytest-remotedata [amd64] (bionic-proposed) [0.2.0-1]
[11:24] -queuebot:#ubuntu-release- New: accepted pytest-remotedata [armhf] (bionic-proposed) [0.2.0-1]
[11:24] -queuebot:#ubuntu-release- New: accepted pytest-remotedata [ppc64el] (bionic-proposed) [0.2.0-1]
[11:24] -queuebot:#ubuntu-release- New binary: gsoap [ppc64el] (bionic-proposed/universe) [2.8.60-2] (no packageset)
[11:24] -queuebot:#ubuntu-release- New: accepted fcitx [arm64] (bionic-proposed) [1:<IP_ADDRESS>-1]
[11:24] -queuebot:#ubuntu-release- New: accepted fcitx [s390x] (bionic-proposed) [1:<IP_ADDRESS>-1]
[11:24] -queuebot:#ubuntu-release- New: accepted pytest-remotedata [i386] (bionic-proposed) [0.2.0-1]
[11:24] -queuebot:#ubuntu-release- New: accepted fcitx [i386] (bionic-proposed) [1:<IP_ADDRESS>-1]
[11:24] -queuebot:#ubuntu-release- New: accepted pytest-remotedata [s390x] (bionic-proposed) [0.2.0-1]
[11:24] -queuebot:#ubuntu-release- New: accepted pytest-remotedata [arm64] (bionic-proposed) [0.2.0-1]
[11:25] -queuebot:#ubuntu-release- New: accepted swiglpk [arm64] (bionic-proposed) [1.4.4-1]
[11:25] -queuebot:#ubuntu-release- New: accepted swiglpk [i386] (bionic-proposed) [1.4.4-1]
[11:25] -queuebot:#ubuntu-release- New: accepted swiglpk [s390x] (bionic-proposed) [1.4.4-1]
[11:25] -queuebot:#ubuntu-release- New: accepted swiglpk [armhf] (bionic-proposed) [1.4.4-1]
[11:25] -queuebot:#ubuntu-release- New binary: gsoap [i386] (bionic-proposed/universe) [2.8.60-2] (no packageset)
[11:25] -queuebot:#ubuntu-release- New: accepted swiglpk [ppc64el] (bionic-proposed) [1.4.4-1]
[11:25] -queuebot:#ubuntu-release- New binary: openmsx [ppc64el] (bionic-proposed/universe) [0.14.0-2] (no packageset)
[11:27] <infinity> fossfreedom_: New ubuntu-release-upgrader uploaded that might get the upgrade right.
[11:27] <fossfreedom_> ah - good.  much appreciation for your help today.
[11:29] -queuebot:#ubuntu-release- New binary: golang-1.10 [arm64] (bionic-proposed/none) [1.10~rc1-1] (no packageset)
[11:30] <infinity> fossfreedom_: And ubuntu-budgie-desktop is in the ubuntu-budgie-desktop on ftpmaster, so that should be fixed when mirrors catch up.
[11:30] <infinity> s/in the ubuntu-budgie-desktop/in the ubuntu-budgie-desktop task/
[11:30] -queuebot:#ubuntu-release- New binary: openmsx [i386] (bionic-proposed/universe) [0.14.0-2] (no packageset)
[11:32] <infinity> fossfreedom_: For people upgrading without uru (which we don't recommend, but it's still a thing), you could also consider making budgie-desktop-environment Recommends ubuntu-budgie-desktop just for 18.04, then drop that weird circular dep for 18.10.
[11:33] -queuebot:#ubuntu-release- New binary: openmsx [amd64] (bionic-proposed/universe) [0.14.0-2] (no packageset)
[11:34] <fossfreedom_> will do - and that will force me to create the 18.10 TO-DO list as well
[11:34] <infinity> fossfreedom_: But given your user base probably wasn't huge in artful and the release-upgrader path should do the right thing, maybe adding weird deps isn't necessary.
[11:34] <infinity> fossfreedom_: But your call.
[11:36] <infinity> (base)adconrad@nosferatu:~$ apt-cache show ubuntu-budgie-desktop | grep ^Task
[11:36] <infinity> Task: ubuntu-budgie-desktop
[11:36] <infinity> fossfreedom_: ^-- Your next daily should be fixed.
[11:36] <fossfreedom_> +1
[11:38] -queuebot:#ubuntu-release- New: accepted enki-aseba [amd64] (bionic-proposed) [1:1.6.0-2]
[11:38] -queuebot:#ubuntu-release- New: accepted enki-aseba [i386] (bionic-proposed) [1:1.6.0-2]
[11:38] -queuebot:#ubuntu-release- New: accepted enki-aseba [s390x] (bionic-proposed) [1:1.6.0-2]
[11:38] -queuebot:#ubuntu-release- New: accepted enki-aseba [arm64] (bionic-proposed) [1:1.6.0-2]
[11:38] -queuebot:#ubuntu-release- New binary: gsoap [arm64] (bionic-proposed/universe) [2.8.60-2] (no packageset)
[11:38] -queuebot:#ubuntu-release- New: accepted enki-aseba [ppc64el] (bionic-proposed) [1:1.6.0-2]
[11:39] -queuebot:#ubuntu-release- New: accepted el-ixir [armhf] (bionic-proposed) [3.0-1]
[11:39] -queuebot:#ubuntu-release- New binary: gsoap [armhf] (bionic-proposed/universe) [2.8.60-2] (no packageset)
[11:39] -queuebot:#ubuntu-release- New: accepted el-ixir [i386] (bionic-proposed) [3.0-1]
[11:40] -queuebot:#ubuntu-release- New: accepted gsoap [amd64] (bionic-proposed) [2.8.60-2]
[11:40] -queuebot:#ubuntu-release- New: accepted gsoap [armhf] (bionic-proposed) [2.8.60-2]
[11:40] -queuebot:#ubuntu-release- New: accepted gsoap [ppc64el] (bionic-proposed) [2.8.60-2]
[11:40] -queuebot:#ubuntu-release- New: accepted gsoap [arm64] (bionic-proposed) [2.8.60-2]
[11:40] -queuebot:#ubuntu-release- New: accepted gsoap [s390x] (bionic-proposed) [2.8.60-2]
[11:40] -queuebot:#ubuntu-release- New: accepted gsoap [i386] (bionic-proposed) [2.8.60-2]
[11:40] -queuebot:#ubuntu-release- New: accepted el-ixir [arm64] (bionic-proposed) [3.0-1]
[11:41] -queuebot:#ubuntu-release- New: accepted golang-1.10 [amd64] (bionic-proposed) [1.10~rc1-1]
[11:41] -queuebot:#ubuntu-release- New: accepted golang-1.10 [i386] (bionic-proposed) [1.10~rc1-1]
[11:41] -queuebot:#ubuntu-release- New: accepted golang-1.10 [arm64] (bionic-proposed) [1.10~rc1-1]
[11:41] -queuebot:#ubuntu-release- New: accepted golang-1.10 [ppc64el] (bionic-proposed) [1.10~rc1-1]
[11:42] -queuebot:#ubuntu-release- New: accepted golang-go4 [amd64] (bionic-proposed) [0.0~git20180103.fba789b-1]
[11:42] <cpaelzer> tjaalton: tests look good and that seems a much more reasonable fix
[11:43] <cpaelzer> tjaalton: I wanted to "get out nss" asap by not being an nss-expert and missed this most obvious revert as a fix - thank you!
[11:43] <cpaelzer> tests are all good now
[11:45] <tjaalton> cool
[11:46] -queuebot:#ubuntu-release- New: accepted openmsx [amd64] (bionic-proposed) [0.14.0-2]
[11:46] -queuebot:#ubuntu-release- New: accepted openmsx [ppc64el] (bionic-proposed) [0.14.0-2]
[11:46] -queuebot:#ubuntu-release- New: accepted openmsx [i386] (bionic-proposed) [0.14.0-2]
[11:46] -queuebot:#ubuntu-release- New: accepted openmsx [s390x] (bionic-proposed) [0.14.0-2]
[12:05] <ginggs> would someone please 'force-badtest octave-symbolic/amd64/2.6.0-2 octave-symbolic/ppc64el/2.6.0-2' ?  i believe it has regressed in release, and blocks octave + gdal from migrating
[12:05] <ginggs> infinity: ^ in case you are still around
[12:07] <tjaalton> cpaelzer: we should probably have a bug for the db transition to verify that packages are fixed before that revert can be dropped
[12:09] <cpaelzer> I'll split something off of mine
[12:10] <cpaelzer> I'll mark those packages that I know of as affected
[12:10] <cpaelzer> as mor turn up we can mark them as well
[12:10] <tjaalton> libapache2-mod-nss, certmonger, dogtag-pki at least
[12:10] <cpaelzer> ok I'll add those direct
[12:10] <cpaelzer> ly
[12:10] <tjaalton> thanks
[12:11] <tjaalton> fixes are pending upstream'
[12:11] <tjaalton> just waiting for a release
[12:14] <cpaelzer> tjaalton: FYI bug 1747411
[12:17] <tjaalton> cpaelzer: great, thanks
[12:24] -queuebot:#ubuntu-release- New binary: optlang [amd64] (bionic-proposed/universe) [1.3.0-1] (no packageset)
[13:39] -queuebot:#ubuntu-release- New binary: libzstd [s390x] (bionic-proposed/universe) [1.3.3+dfsg-1ubuntu1] (ubuntustudio)
[13:41] -queuebot:#ubuntu-release- New binary: libzstd [ppc64el] (bionic-proposed/universe) [1.3.3+dfsg-1ubuntu1] (ubuntustudio)
[13:50] -queuebot:#ubuntu-release- New binary: libzstd [amd64] (bionic-proposed/universe) [1.3.3+dfsg-1ubuntu1] (ubuntustudio)
[13:50] -queuebot:#ubuntu-release- Unapproved: ceilometer (artful-proposed/main) [1:9.0.2-0ubuntu1 => 1:9.0.4-0ubuntu1] (openstack, ubuntu-server) (sync)
[13:50] -queuebot:#ubuntu-release- Unapproved: heat (artful-proposed/main) [1:9.0.1-0ubuntu1 => 1:9.0.2-0ubuntu1] (openstack, ubuntu-server) (sync)
[13:50] -queuebot:#ubuntu-release- Unapproved: cinder (artful-proposed/main) [2:11.0.1-0ubuntu1 => 2:11.0.2-0ubuntu1] (openstack, ubuntu-server) (sync)
[13:50] -queuebot:#ubuntu-release- Unapproved: nova (artful-proposed/main) [2:16.0.3-0ubuntu1 => 2:16.0.4-0ubuntu1] (openstack, ubuntu-server) (sync)
[13:52] -queuebot:#ubuntu-release- New binary: libzstd [arm64] (bionic-proposed/universe) [1.3.3+dfsg-1ubuntu1] (ubuntustudio)
[13:52] -queuebot:#ubuntu-release- New binary: libzstd [i386] (bionic-proposed/universe) [1.3.3+dfsg-1ubuntu1] (ubuntustudio)
[13:53] -queuebot:#ubuntu-release- New binary: libzstd [armhf] (bionic-proposed/universe) [1.3.3+dfsg-1ubuntu1] (ubuntustudio)
[14:28] -queuebot:#ubuntu-release- New source: openssl1.0 (bionic-proposed/primary) [1.0.2n-1ubuntu2]
[14:29] <xnox> fire in the hole!
[14:33] -queuebot:#ubuntu-release- New binary: openssl [s390x] (bionic-proposed/main) [1.1.0g-2ubuntu1] (core)
[14:35] -queuebot:#ubuntu-release- New binary: openssl [ppc64el] (bionic-proposed/main) [1.1.0g-2ubuntu1] (core)
[14:39] -queuebot:#ubuntu-release- New binary: openssl [i386] (bionic-proposed/main) [1.1.0g-2ubuntu1] (core)
[14:41] -queuebot:#ubuntu-release- New binary: openssl [amd64] (bionic-proposed/main) [1.1.0g-2ubuntu1] (core)
[14:41] -queuebot:#ubuntu-release- New binary: openssl [arm64] (bionic-proposed/main) [1.1.0g-2ubuntu1] (core)
[14:46] -queuebot:#ubuntu-release- New binary: openssl [armhf] (bionic-proposed/main) [1.1.0g-2ubuntu1] (core)
[14:50] -queuebot:#ubuntu-release- New binary: ubuntu-keyring [amd64] (bionic-proposed/main) [2018.02.05] (core)
[14:57]  * mdeslaur braces for impact
[14:58] <jbicha> slangasek: sorry, I don't know more about the gtk-doc ftbfs
[14:59] -queuebot:#ubuntu-release- New: accepted openssl [amd64] (bionic-proposed) [1.1.0g-2ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted openssl [armhf] (bionic-proposed) [1.1.0g-2ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted openssl [ppc64el] (bionic-proposed) [1.1.0g-2ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted openssl [arm64] (bionic-proposed) [1.1.0g-2ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted openssl [s390x] (bionic-proposed) [1.1.0g-2ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted openssl [i386] (bionic-proposed) [1.1.0g-2ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted openssl1.0 [source] (bionic-proposed) [1.0.2n-1ubuntu2]
[15:00] -queuebot:#ubuntu-release- New: accepted ubuntu-keyring [amd64] (bionic-proposed) [2018.02.05]
[15:00] -queuebot:#ubuntu-release- New: accepted optlang [amd64] (bionic-proposed) [1.3.0-1]
[15:00] -queuebot:#ubuntu-release- New: accepted libzstd [amd64] (bionic-proposed) [1.3.3+dfsg-1ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted libzstd [armhf] (bionic-proposed) [1.3.3+dfsg-1ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted libzstd [ppc64el] (bionic-proposed) [1.3.3+dfsg-1ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted libzstd [arm64] (bionic-proposed) [1.3.3+dfsg-1ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted libzstd [s390x] (bionic-proposed) [1.3.3+dfsg-1ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted libzstd [i386] (bionic-proposed) [1.3.3+dfsg-1ubuntu1]
[15:54] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (artful-proposed) [20180129+dfsg1-0ubuntu1~17.10.0]
[16:00] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (xenial-proposed) [20180129+dfsg1-0ubuntu1~16.04.0]
[16:07] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (trusty-proposed) [20180129+dfsg1-0ubuntu1~14.04.0]
[16:39] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu5 => 2.02-2ubuntu5] (core)
[16:52] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (artful-proposed) [1:17.10.10]
[17:00] <juliank> Can we add a tracker for the ongoing cryptsetup transition? Something like this:
[17:00] <juliank> is_affected =  .build-depends ~ /libcryptsetup-dev/;
[17:00] <juliank> is_good = .depends ~ /libcryptsetup12/;
[17:00] <juliank> is_bad = .depends ~ /libcryptsetup4/;
[17:02]  * juliank is loosing track a bit
[17:04] <jbicha> juliank: do you want to add that yourself? :) https://code.launchpad.net/~ubuntu-transition-trackers/ubuntu-transition-tracker/configs
[17:04] <juliank> sure
[17:11] <xnox> apw, please RM linux from bionic-proposed..... for some reason it got picked up for openssl abi transtion and i should not be uploading linux packages....
[17:13] -queuebot:#ubuntu-release- New binary: knot-resolver [arm64] (bionic-proposed/universe) [2.0.0-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: knot-resolver [armhf] (bionic-proposed/universe) [2.0.0-1] (no packageset)
[17:13] <apw> xnox, i don't see anything linux'y in bionic-proposed
[17:14] <xnox> apw, i'm guessing it is "nowhere" just yet, but should be accepted soon =/
[17:14]  * xnox refreshes
[17:15] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (artful-proposed) [1:17.10.13]
[17:18] -queuebot:#ubuntu-release- New binary: uhd [s390x] (bionic-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (xenial-proposed) [1:16.04.11]
[17:21] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (trusty-proposed) [1:0.196.25]
[17:27] <xnox> apw, https://launchpad.net/ubuntu/+source/linux/4.13.0-32.35build1
[17:27]  * xnox cancelled builds, but removing this would be nice.
[17:29] <slangasek> jbicha: ok. are you able to reproduce it?
[17:33] <jbicha> slangasek: not locally :(
[17:33] <doko> xnox: why did you cancel?
[17:34] <xnox> doko, it will FTBFS
[17:34] <xnox> 4.13 is not buildable in bionic, and I should not be making kernel uploads, as they need to match with the rest of uploads (signed, etc)
[17:35] <doko> why not buildable?
[17:36] <xnox> debhelper miscompat that was fixed up in v4.14, which got purged in favor of meltdown/spectre patched v4.13 kernels
[17:36] <xnox> we are targetting v4.15 for bionic
[17:37] <doko> right, but nothing will migrate until they rebuild against current binutils
[17:38] <xnox> doko, eggcelent
[17:38] <doko> so now everything blocked on the kernel too ...
[17:38] <xnox> doko, i think i want to call it a day.
[17:40] <doko> xnox: I will undo your systemd workaround once binutils is built on arm64
[17:40] <xnox> doko, well, it will not migrate, because of autopkgtest failures.
[17:40] <xnox> doko, and there are things to fix up in v237
[17:41]  * xnox was going back to that, after loading up builders with openssl1.1
[17:41] <doko> ok, your upload
[17:41] <slangasek> doko (et al): FYI there will be s390x compute downtime tomorrow lasting up to 24h.  So if you have any transition-related uploads that are going to trigger a bunch of autopkgtests, now might be a good time to do them
[17:41] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-142.191] (core, kernel)
[17:41] <slangasek> (so s390x can clear the backlog before the maintenance window)
[17:42] <slangasek> xnox: ^^ you perhaps already know about this
[17:42] <xnox> =)
[17:42] <slangasek> doko, xnox: I want linux-tools fixed to statically link libbfd
[17:42] <slangasek> this was also blocking us from being able to have linux-kvm in bionic
[17:45] <doko> slangasek: doesn't help now with the migration
[17:45] <doko> Missing build dependencies: linux-image-amd64
[17:45] <doko> how is that supposed to work in Ubuntu?
[17:45] <doko> I see that at least twice
[17:45] <slangasek> doko: it helps in the sense that if we're blocked anyway, the time might be better spent fixing the current breakage "right"
[17:46] <slangasek> (by getting the fix landed in artful kernel, binary copied forward, and promoted)
[17:46] <slangasek> doko: where do you see that?
[17:46] <doko> slangasek: b-d of nbdkit
[17:47] <slangasek> surely a package build-depending on a linux-image is wrong, including in Debian?
[17:49] <doko> the changelog doesn't speak about that
[17:53] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (artful-proposed) [3:12.0.2-0ubuntu1]
[17:54] -queuebot:#ubuntu-release- Unapproved: accepted nova [sync] (artful-proposed) [2:16.0.4-0ubuntu1]
[17:55] -queuebot:#ubuntu-release- Unapproved: accepted heat [sync] (artful-proposed) [1:9.0.2-0ubuntu1]
[17:55] <ginggs> slangasek: hi, if you get the chance, please 'force-badtest octave-symbolic/amd64/2.6.0-2 octave-symbolic/ppc64el/2.6.0-2' ?  i believe it has regressed in release, and blocks octave + gdal + grass from migrating
[17:56] -queuebot:#ubuntu-release- Unapproved: accepted cinder [sync] (artful-proposed) [2:11.0.2-0ubuntu1]
[17:56] -queuebot:#ubuntu-release- Unapproved: accepted ceilometer [sync] (artful-proposed) [1:9.0.4-0ubuntu1]
[17:59] <slangasek> ginggs: done
[17:59] <ginggs> slangasek: thanks!
[18:06] <xnox> somebody just broke the ssl trackers
[18:06] <xnox> or fixed?
[18:06]  * xnox fixes
[18:11] <xnox> jbicha, note the ssl1.1 tracker you have removed, is kind of the one we actually need. As I have been using that one to schedule binNMUs, which the openssl1.0-rm one does not provide.
[18:11] <xnox> jbicha, also we will not remove openssl1.0 in bionic.
[18:20] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu6 => 2.02-2ubuntu6] (core)
[18:33] <doko> if I remove the recent -build1 linux upload from -proposed, does the previous source package still exist in -proposed?
[18:35] -queuebot:#ubuntu-release- New binary: openvswitch [amd64] (bionic-proposed/main) [2.9.0~git20180205.5a39582ca-0ubuntu1] (ubuntu-server)
[18:35] <infinity> doko: There was no previous version in proposed.
[18:36] <infinity> 4.13.0-32.35 migrated last week.
[18:36] <doko> ohh
[18:36] <doko> would -build1 actually hurt?
[18:36] <infinity> doko: But to answer the spirit of your question, no, it wouldn't resurrect a previous upload automatically, you'd have to copy it back in with binaries and --force-same-destination
[18:37] <infinity> doko: build1 won't work.  But the part where it's not building also won't hurt anything. :P
[18:37]  * infinity just deletes it.
[18:38] <doko> so with the current mess it seems to be safe to upload glibc too ... ;p
[18:38] <infinity> Was planning to wait until after the s390x downtime.
[18:38] <infinity> So autopkgtests can actually run.
[18:38] <infinity> Of which there will be many.
[18:38] <doko> s390x doesn't seem to be the issue, arm64 is
[18:39] <infinity> No, but it will be an issue when it's offline.
[18:39] <infinity> Anyhow, post-s390x-downtime was my plan.  I'm sticking to it.
[18:39] <doko> when would that be?
[18:40] <infinity> doko: 36-48h, ish.
[18:40] <doko> what's the issue with the buildds? currently no builds picked up
[18:41] <infinity> They're all disabled.  You'd have to ask William or Colin if that's intentional or openstack being openstack.
[18:50] <cjwatson> mostly fixed.  also love that exaggeration.
[18:50] <cjwatson> 72 builds dispatched in the ten minutes before "currently no builds picked up"
[18:51] <cjwatson> it wasn't great, but not dead either ...
[18:55] <infinity> cjwatson: TBF, when he asked, I saw "138 avail, 118 disabled", which looked reasonably dire.
[18:56] <infinity> cjwatson: Though, I guess a ton are legit disabled right now, which skews that view.
[19:12] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu6 => 2.02-2ubuntu6] (core)
[19:19] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-142.191]
[19:26] -queuebot:#ubuntu-release- New binary: canl-c [s390x] (bionic-proposed/universe) [3.0.0-2] (no packageset)
[19:57] -queuebot:#ubuntu-release- Unapproved: walinuxagent (artful-proposed/main) [2.2.17-0ubuntu1 => 2.2.21-0ubuntu1~17.10.1] (ubuntu-cloud, ubuntu-server)
[19:57] -queuebot:#ubuntu-release- Unapproved: walinuxagent (xenial-proposed/main) [2.2.17-0ubuntu1~16.04.1 => 2.2.21-0ubuntu1~16.04.1] (ubuntu-cloud, ubuntu-server)
[19:57] -queuebot:#ubuntu-release- Unapproved: walinuxagent (trusty-proposed/main) [2.2.17-0ubuntu1~14.04.1 => 2.2.21-0ubuntu1~14.04.1] (ubuntu-cloud, ubuntu-server)
[19:57] -queuebot:#ubuntu-release- New binary: knot-resolver [i386] (bionic-proposed/universe) [2.0.0-1] (no packageset)
[20:02] -queuebot:#ubuntu-release- New binary: python-networkmanager [amd64] (bionic-proposed/universe) [2.0.1-1] (no packageset)
[20:04] -queuebot:#ubuntu-release- New binary: canl-c [i386] (bionic-proposed/universe) [3.0.0-2] (no packageset)
[20:06] -queuebot:#ubuntu-release- New binary: canl-c [amd64] (bionic-proposed/universe) [3.0.0-2] (no packageset)
[20:14] -queuebot:#ubuntu-release- New binary: uhd [i386] (bionic-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[20:35] -queuebot:#ubuntu-release- New binary: knot-resolver [ppc64el] (bionic-proposed/universe) [2.0.0-1] (no packageset)
[20:41] -queuebot:#ubuntu-release- New binary: canl-c [ppc64el] (bionic-proposed/universe) [3.0.0-2] (no packageset)
[20:45] -queuebot:#ubuntu-release- New binary: uhd [amd64] (bionic-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[20:53] -queuebot:#ubuntu-release- New binary: uhd [ppc64el] (bionic-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[20:54] -queuebot:#ubuntu-release- New binary: canl-c [arm64] (bionic-proposed/universe) [3.0.0-2] (no packageset)
[20:54] -queuebot:#ubuntu-release- New binary: canl-c [armhf] (bionic-proposed/universe) [3.0.0-2] (no packageset)
[20:56] -queuebot:#ubuntu-release- New: accepted canl-c [amd64] (bionic-proposed) [3.0.0-2]
[20:56] -queuebot:#ubuntu-release- New: accepted canl-c [armhf] (bionic-proposed) [3.0.0-2]
[20:56] -queuebot:#ubuntu-release- New: accepted canl-c [ppc64el] (bionic-proposed) [3.0.0-2]
[20:56] -queuebot:#ubuntu-release- New: accepted openvswitch [amd64] (bionic-proposed) [2.9.0~git20180205.5a39582ca-0ubuntu1]
[20:56] -queuebot:#ubuntu-release- New: accepted canl-c [arm64] (bionic-proposed) [3.0.0-2]
[20:56] -queuebot:#ubuntu-release- New: accepted canl-c [s390x] (bionic-proposed) [3.0.0-2]
[20:56] -queuebot:#ubuntu-release- New: accepted canl-c [i386] (bionic-proposed) [3.0.0-2]
[20:56] -queuebot:#ubuntu-release- New: accepted python-networkmanager [amd64] (bionic-proposed) [2.0.1-1]
[21:04] <acheronuk> hi, can someone rebuild whatever is required to fix this?
[21:04] <acheronuk> https://paste.ubuntu.com/26526608/
[21:05] <acheronuk> lintian being uninstallable is NOT good!
[21:21] <slangasek> acheronuk: in -proposed?
[21:21] <acheronuk> yes
[21:23] <slangasek> are you seeing that in a package build in LP?
[21:25] <acheronuk> slangasek: yes, I had a build failures against proposed. that paste is what I discovered when I logged into a bionic pbuilder to investigate
[21:26] <acheronuk> perl-openssl-defaults now Provides: perl-openssl-abi-1.1
[21:26] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu5]
[21:26] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu6]
[21:26] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu5]
[21:27] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu6]
[21:27] <acheronuk> so I would guess libnet-ssleay-perl needs a rebuild against that?
[21:29] <slangasek> yeah, looks like a few things do
[21:32] -queuebot:#ubuntu-release- New binary: uhd [armhf] (bionic-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[21:33] -queuebot:#ubuntu-release- New binary: uhd [arm64] (bionic-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[21:41] <slangasek> acheronuk: packages uploaded
[21:41] <acheronuk> slangasek: thank you.
[21:54] <tsimonq2> infinity: hmm, s390x downtime? How long will that last?
[22:01] <tsimonq2> slangasek: Hi, (sorry for poking if it's already in your queue but) did the recent commit I made here fix things? https://code.launchpad.net/%7Etsimonq2/ubuntu-cdimage/add-lubuntu-css/+merge/337123
[22:02] <nacc> tsimonq2: up to 24 hrs from start
[22:02] <tsimonq2> nacc: ack, thanks
[22:05] <tsimonq2> Can an archive admin please look at src:ukui-menus in Bionic NEW? It would be good to get that through so I can upload some other UKUI packages which depend on that.
[22:17] <xnox> tsimonq2, 24h
[22:19] <tsimonq2> xnox: thanks :)
[22:35] <nacc> slangasek: i think i'm confused by something obvious: freedombox-setup 0.11 has removed its dep8 tests. How is it possible for that to be a regression? http://autopkgtest.ubuntu.com/packages/f/freedombox-setup/bionic/amd64 Specifically
[22:35] <nacc><EMAIL_ADDRESS>[22:57] <slangasek> nacc: perhaps someone manually triggered the autopkgtest for the version of the package that has no tests?
[23:02] <slangasek> nacc: alternate possibility is a bug in britney
[23:02] <slangasek> acheronuk: libnet-ssleay-perl should be installable now if you want to retry things
[23:04] <nacc> slangasek: err, sorry, yes, plinth and freedombox-setup need to go together; so i had triggred the job to use the version from proposed. However, why is it  aregression to go from passing tests to no tests?
[23:05] <xnox> slangasek, i believe disaapearing tests is deliberate regression in britney sense.
[23:06] <xnox> one shall not remove tests - pitti or some such
[23:06] <nacc> xnox: ah that woulld make sense
[23:06] <nacc> xnox: however, in this case, the removall is from debian, so it feels like ... it should be ignored?
[23:07] <nacc> not sure
[23:07] <acheronuk> slangasek: apt is not seeing the new version yet on main archive.ubuntu.com
[23:07] <xnox> nacc, make a merge proposal against the hints-ubuntu branch to badtest it
[23:08] <acheronuk> but LP builder got it
[23:09] <nacc> xnox: i should make it versioned on the one curretly in b-p?
[23:09] <xnox> acheronuk, lp builders use internal mirror, that can be ahead of public archive.ubuntu.com.
[23:09] <xnox> acheronuk, check rmadison?
[23:10] <slangasek> nacc: that part seems like it's a bug in britney
[23:10] <slangasek> or what xnox said
[23:10] <slangasek> anyway, MP welcome against hints
[23:10] <acheronuk> right. might build ran ok, so I'm happy
[23:10] <acheronuk> *my build
[23:12] -queuebot:#ubuntu-release- New binary: knot-resolver [ppc64el] (bionic-proposed/universe) [2.0.0-2] (no packageset)
[23:13] -queuebot:#ubuntu-release- New binary: knot-resolver [armhf] (bionic-proposed/universe) [2.0.0-2] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: knot-resolver [i386] (bionic-proposed/universe) [2.0.0-2] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: knot-resolver [arm64] (bionic-proposed/universe) [2.0.0-2] (no packageset)
[23:18]  * xnox debates rebuilding php7.2 or not
[23:34] <nacc> slangasek: thanks
[23:44] <nacc> xnox: i woulld prefer you didn't ;)


[06:53] <mvip> wgrant, I am the project maintainer and I have set it to MIT
[06:55] <wgrant> mvip: Which project?
[06:56] <wgrant> And why do you say it is miscategorised as commercial?
[06:58] <mvip> wgrant, https://code.launchpad.net/~wott/+snap/wott-agent
[06:58] <mvip> and https://launchpad.net/~vpetersson/+archive/ubuntu/wott-agent
[06:58] <mvip> I'm not sure how the relationship is between the two
[07:01] <wgrant> mvip: You initially created the project with a proprietary license, which created a commercial subscription trial. You later changed the license to MIT, and weren't using any commercial features, so when the trial expired after a month nothing really happened.
[07:01] <mvip> wgrant, ah gotcha - so everything's fine?
[07:01] <mvip> just got an email yesterday saying that it will stop working, which is why i was concerned
[07:02] <wgrant> mvip: Yeah, the email probably doesn't consider the case where somebody has changed the license from proprietary to something else within the trial period.
[07:02] <mvip> Got it. Perfect. Thanks wgrant.
[07:04] <wgrant> np
[22:30] <seb128> hey, is launchpad having issues? it seems to timeout on bugs editing here
[22:31] <mwhudson> me too


[21:22] <dch> meena: where did we get to with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274260 ?
[21:22] -ubottu:#cloud-init- bugs.freebsd.org bug 274260 in Ports & Packages "net/cloud-init: fix broken DataSource identification" [Affects Some People, Open]
[21:24] <dch> aah its sitting with me ... "to do before 14.0-RELEASE"
[21:24] <dch> dammit
[21:36] <dch> this is in 23.3.3 maybe we should just get that ported
[21:36] <dch> sigh
[21:40] <meena> dch: yeah, it was fixed in main, but we didn't release it yet. A release is going to be cut in about a week
[21:40] <dch> looks like I went on holiday during maintainer-approval and missed it getting back to me
[21:41] <dch> I will apply the patch to quarterly, leave the additional version bump to maintainer
[22:08] <dch> dammit again,  patch doesn't fix quarterly
[22:17] <dch> or maybe it does, but only when run via service
[22:17] <dch> ah
[23:18] <meena> where is cloudinit.net._rename_interfaces() used?
[23:18] <meena> i don't see any direct call to it, only in unittests.
[23:19] <meena> oh
[23:19] <meena> apply_network_config_names()


[02:46] <lotuspsychje> good morning
[06:16] <ducasse> good morning
[09:02] <akemhp> I have this running on my system right now "14927 ?        S<Ls   0:48 /usr/bin/atop -R -w /var/log/atop/atop_20200909 600", isn't atop manually started? I mean i know i never started that since i booted, how comes i have this in my process list, any idea?
[09:16] <akemhp> Nevermind i think i have some service that kickstart this stuff.


[06:23] <jekin> hey anyone there ?  ?
[06:31] <jekin> hey need a help ... I have some problem with Ubuntu ..... I have a Nvidia FX5500 card which causes the booting from hard disk or live CD to fail ...... when i try the text mode this following message is comming up
[06:31] <jekin> 	jekin	No init found try parsing init=bootarg
[22:17] <snowed>  When i use update-grub there will not add windows to boot loader. Windows is on other HDD than ubuntu. Can someone give me solution


[02:09] <bashfulrobot> Mo418: we don't use Wayland. We only ship xorg. Was this an install from our ISO?
[04:16] <rob000018> hey folks, tried to install budgie-desktop from unity in 18.04 but failed, get: E: Sub-process /usr/bin/dpkg returned an error code (1)
[04:17] <rob000018> The following packages have unmet dependencies:  budgie-desktop-environment : Depends: budgie-desktop-common but it is not going to be installed
[04:17] <rob000018> tried to repair but gives same errors
[13:05] <w4o3i> Hello, I just tried installing Ubuntu Budgie 18.04
[13:06] <w4o3i> When the install routine was finished it tried to install grub, but made an error and tried to install grub to the device of the SSD card that I used to boot the Budgie live system from for installation
[13:07] <w4o3i> I then had it manually install grub to /dev/sda instead of /dev/mmcblk0
[13:07] <w4o3i> When I try to boot it now, it just gives me a blank screen with a blinking cursor. Nothing happens.
[13:07] <w4o3i> How do I fix this? And why does it try to install grub to my installation medium?
[13:09] <w4o3i> Furthermore, when I made a test installation of Ubuntu 18.04 LTS Desktop, the default installation parameters installed the system in a btrfs partition. Budgie defaults to ext4 instead. Is this intentional?
[14:08] <fossfreedom_> w4o3i: That doesnt sound right - ubuntu default should be ext4 - same as all the flavours
[14:10] <fossfreedom_> when you were installing was it a clean wipe type install or a something else partition install?
[20:05] <lynks> hello. I need to u2f support for non-yubikey devices on ubuntu budgie
[20:05] <lynks> any idea how to add this?
[21:31] <Bikos> Dears, if you can help me with this one, or point me somehwere to start digging ...
[21:32] <Bikos> 2.37 No IRQ handler for vector
[21:32] <Bikos> i think it hppens when my Laptop going to hibernate, the whole display server crashes with this error massage
[21:33] <Bikos> followed by: Swap Header not Found


[14:51] <thafreak> Anyone looking for a cheap desktop...
[14:51] <thafreak> These amd e-450 motherboard/cpu combos are pretty good
[14:51] <thafreak> doubt it will do THAT great gaming...but my kinda stuff...works REALLY well
[14:52] <thafreak> just no fullscreen full hd youtube
[14:52] <thafreak> but even though it's only a dualcore 1.6ghz, it has virtualization support
[14:53] <thafreak> I'm browsing the web, while installing windows xp in a kvm vm...and it's still responsive.
[14:55] <thafreak> actually bought this setup to run freenas, but while I'm waiting on more parts, I thought I'd test it out for running vm's
[15:52] <drkokandy> sounds like a good value
[15:52] <thafreak> specially at about $80
[15:52] <thafreak> with 8gb of ram it's just a hair over $100
[15:55] <drkokandy> I spent a bit more than that on my FreeNAS setup... but the great thing about FreeNAS is it'll probably run just great on that hardware
[15:55] <drkokandy> no reason to spend more
[15:55] <thafreak> i just got 4 of the wd red drives too...
[15:55] <drkokandy> nice
[15:55] <thafreak> haven't tested them for bad sectors yet though
[15:56] <thafreak> probably should have ordered 5, cause my luck there will be some DOA ones
[15:57] <drkokandy> hope not ... but a good idea to check
[15:59] <thafreak> so what all do you use your freenas box for?
[15:59] <thafreak> and any data corruption or other bad problems?
[16:00] <drkokandy> backup more than anything - I hold images of drives and redundant copies of things there
[16:01] <drkokandy> I really had just gotten sick of juggling little external drives
[16:01] <thafreak> gotcha...
[16:02] <thafreak> last year I built a new vm server...and was going to build a freenas box to store all the vms on
[16:02] <drkokandy> I have one drive in my setup that has been a little flaky, but nothing so far that a scrub hasn't fixed
[16:02] <drkokandy> but I did get a spare HD in case
[16:02] <thafreak> that's good to know...heard one horror story...but he was using old junk hardware
[16:03] <drkokandy> that would be cool. let us know how that goes. I never thought of trying to host VM files elsewhere
[16:05] <thafreak> i do it at work with our san...
[16:05] <thafreak> i ended up last year just combining the two machines, so I had a vm server with a bunch of disks
[16:06] <thafreak> talk about single point of failure...
[16:06] <drkokandy> yeah - it's been good to me, but mileage could vary. if they are critical vms, back them up - ZFS isn't a substitute for a backup - but it would be easy to set up an rsync periodically
[16:06] <drkokandy> holy cow, yeah
[16:06] <thafreak> right...nothing "critical" really
[16:07] <thafreak> the most critical vm is actually my storage vm...the one that shares out the data :)
[16:07] <thafreak> actually I have two, one for internal stuff and one that's externally accessible in my dmz
[16:08] <thafreak> but I can move most of that straight to the freenas box...
[16:08] <thafreak> I think I'm actually replacing my vm server too...it's too much of a power hog
[16:08] <drkokandy> yeah, that should be pretty easy
[16:08] <thafreak> 6 core phenom II
[16:08] <drkokandy> ah yeah
[16:09] <thafreak> and i don't think I really need that many cores...probably replace it with a couple amd e-350 type boards
[16:09] <thafreak> take that phenom and use it for something like gaming :)
[16:10] <drkokandy> yeah, that'll be a good use for that
[16:10] <thafreak> also, as hard as I tried, I couldn't get this e-450 machine to use more than 49w (measured with a kill-a-watt meter)
[16:10] <drkokandy> wow - that's great
[16:11] <thafreak> i think my phenom idles around 100 :)
[16:11] <thafreak> even with a couple kvm vm's running, it only peaked up in the 40's when heavy io happened
[16:12] <thafreak> mostly it idled around 36w
[16:12] <drkokandy> great value
[16:12] <thafreak> seriously...for folks who want to play with linux, <$200 and you have a vm server that uses very little power
[16:15] <drkokandy> very cool - maybe I'll recommend that to my brother
[16:15] <thafreak> and i think you can get most of it locally at microcenter too
[16:16] <thafreak> they have atleast one model of mini-itx board with an amd-e350 soldered on
[16:16] <thafreak> only thing they don't have is a good selection of power supplies...you can get a 80+ bronze at best for a good price there
[16:17] <thafreak> i ended up ordering an 80+ gold from newegg for about what a bronze normally costs...
[16:18] <drkokandy> microcenter is a bit of a drive so I do mostly Newegg - snagged a lot of good deals like that
[16:20] <thafreak> I'm lucky, it's only about an hour to the cleveland one...
[16:20] <thafreak> I still order things on newegg though, cause I don't like driving in cleveland
[16:20] <thafreak> but if I REALLY want something now...I know I can drive up there
[17:16] <drkokandy> Cheri703 - check this out! your dream is in the works l already... except as a phone, not a reader - http://techcrunch.com/2012/12/12/the-android-ecosystem-is-two-faced-yotaphone-has-lcd-on-one-side-electronic-paper-display-on-the-other/
[17:33] <Cheri703> oooooo
[17:33] <Cheri703> now if it only comes to a non-gsm carrier!
[17:33] <Cheri703> I have sprint at the moment
[17:33] <Cheri703> well, a sprint mvno
[21:25] <Cheri703> I think I'm going back to 12.04
[21:25] <Cheri703> (from 12.10)
[21:38] <thafreak> how come Cheri703
[21:41] <Cheri703> a few things that I (apparently) relied on heavily aren't available/working in 12.10. I didn't realize how much I'd miss them til lately I noticed it is taking me more time/effort to do things because certain notifications don't show up or such. also most of the "hey, maybe that'll be fixed/better/different in 12.10" things haven't lived up to the hope
[21:45] <thafreak> ah...that's how I am with most relases it seems :)
[21:45] <Cheri703> if 12.10 was the LTS, I'd probably stick it out, but...eh
[21:45] <Cheri703> I try out the new ones, then sometimes revert, sometimes stay
[21:50] <Cheri703> What I'm going to do with this one is once I've gotten it set up, make a virtual image from it, then move it over to my work laptop. Then if I set up DejaDup on the desktop, I can restore to the laptop, and after my work trip coming up, I can just backup the laptop and restore to the desktop (at least that's the goal)


[00:36] <dzho> a vw, you say?
[00:36] <dzho> <.<
[00:36] <dzho> >.>
[00:51] <Unit193> Yeah, this guy is smart, known him for a very long time.
[01:51] <thafreak> I was mostly joking, he's a pretty alright guy...
[01:52] <thafreak> I just usually give him a hard time about the vw, cause he talks about it alot


[08:45] <jeremiah> .c
[15:33] <janimo> ogra_, marvin24 did the 3.1 kernel issue have something in common with https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667 ?
[15:33] <ubot2> Ubuntu bug 936667 in upstart "Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")" [High,Fix released]
[15:34] <ogra_> janimo, well, we always have an initrd
[15:34] <janimo> any news on that particular nvidia kernel issue?
[15:34] <janimo> ogra_, is that still holding up quantal ac100 images?
[15:35] <ogra_> and  that bug is fixed since mid-precise
[15:35] <ogra_> no, what was holding up was my time to fix ac100-tarball-installer and additionally research the oops i get on boot
[15:36] <ogra_> the installer is fixed now
[15:36] <ogra_> tomorrow if i have new images i'll move on with the kernel issue
[15:36] <janimo> ogra_, kernel oops on install or first boot?
[15:36] <janimo> ok
[15:36] <ogra_> sadly ui cant quickly roll images manually atm
[15:36] <ogra_> we only have one builder thats constantly occupied
[15:37] <janimo> is that a regression?
[15:37] <ogra_> janimo, first boot, some initrd issue i think
[15:37] <ogra_> we dropped all non panda HW from the datacenter
[15:37] <janimo> I thought the builder situations was only going to get better
[15:37] <janimo> ah, a good move otherwise
[15:37] <janimo> and not enough new pandas?
[15:37] <ogra_> and until tere is a new mandabox server we only have one machine for livefs builds
[15:38] <ogra_> i think we have a lot of new pandas, but someone needs to set them up
[15:51] <hrw> ogra_: build iamge at home?
[15:51] <ogra_> no, thanks, i have better stuff to do than to set up the ubuntu build infrastructure at home
[16:22]  * GrueMaster has the infrastructure, but no loinger has the time or desire.
[16:28] <janimo> the fact our build insfrastructure is so involved as opposed to dead-simple live-build means noone can really take over properly without too much effort
[16:33] <marvin24> janimo, ogra_: I hope the console can be fixed soon
[16:33] <marvin24> otherwise we need to boot with console=tty1 as a workaround
[16:34] <marvin24> janimo: did you tried to compile a 3.5 kernel for tegra already?
[16:37] <janimo> marvin24, no, since Iheard from you it has no graphics :)
[16:39] <marvin24> it has, but a bit buggy
[16:40] <marvin24> maybe still makes no sense to try it
[16:40] <janimo> I may give arm-soc a try - it has more tegra stuff than 3.5
[16:41] <janimo> I just saw too many kernel tree lately that don't even build, so I am not too attracted to yet another one
[16:41] <janimo> :)
[16:42] <marvin24> janimo: yes, me too :-)
[16:47] <janimo> lilstevie, do you know anything about the status of the 3.1 jhinta kernel for tf101? It sort of boots here, but hangs on starting network manager
[16:48] <janimo> the xda forums are horrendous
[16:48] <marvin24> I wonder if tf101 also has the console problem
[16:50] <janimo> marvin24, I had to boot with --no-log
[16:51] <janimo> marvin24, , otherwise not sure how the console problem manifests itself, I did not boot ac100 with 3.1 yet
[16:51] <janimo> it just prints out the kernel logs, then starting init and a few scripts, pausing on NM
[16:51] <marvin24> yes, it oopes shortly after entering userspace boot
[16:52] <marvin24> but looks random
[16:52] <janimo> no oops on screen and no ramconsole built in this kernel
[16:52] <marvin24> is plymouth installed?
[16:53] <janimo> marvin24, yes. Should  I make it -x ?
[16:53] <janimo> meanwhile I'll rebuild the kernel with ramconsole on
[16:54] <marvin24> no, it hangs here only with plymouth installed
[16:55] <marvin24> but uninstall is also only a workaround
[16:55] <janimo> marvin24, iirc ogra said making lib/plymouthd or some unexecutable is a workaround
[16:55] <marvin24> yes, or add console=tty1
[16:55] <marvin24> and leave it executable
[16:56] <janimo> marvin24, do you know if tegra2 kernels can support multiple hw from the same build? Ie. ventana, harmony, ac100, tf101 all built in?
[16:56] <janimo> marvin24, thanks, I'll try that too
[16:56] <janimo> will that redirect console output to somewhere invisible?
[16:56] <marvin24> the kernel does, but the bootloader doesn't
[16:56] <marvin24> janimo: yes
[16:57] <marvin24> in mainline, everything will depend on device tree
[16:57] <marvin24> so you can boot the same kernel on all tegras
[16:57] <marvin24> but we ee
[16:57] <marvin24> ... need uboot for this
[16:58] <marvin24> uboot passes device tree to the kernel (same kernel for all)
[16:58] <marvin24> I don't know how other archs are doing it now
[16:58] <janimo> marvin24, in 3.1 there's no device tree yet afaik
[16:58] <marvin24> yep, only in mainline
[16:58]  * janimo wonders if a single zImage could be used on both ac100 and tf101
[16:59] <marvin24> sure, add tf101 to mainline
[16:59] <marvin24> or add a device-tree
[17:00] <marvin24> as I said, *all* tegras (tegra2 and tegra3) should be bootable from a single kernel
[17:00] <janimo> so with current 2.6.x/3.0 non-DT, what is uboot specific in the kernel? I see nothing in what I build for in the confis
[17:00] <janimo> configs
[17:00] <janimo> marvin24, yes in mainline, I was wondering pre-DT where we are and will likely still be in 12.10
[17:00] <marvin24> the current bootloader (fastboot) does not support device trees
[17:00] <marvin24> while u-boot does
[17:01] <marvin24> so, mainline + u-boot or fastboot + 3.1
[17:01] <marvin24> (uboot can also boot 3.1 kernels)
[17:01] <marvin24> but hw support is not finished
[17:02] <marvin24> we have to wait - again :-(
[17:02] <marvin24> but regarding DT support, tegra is pretty complete
[17:09] <janimo> marvin24, chmod -x /sbin/plymouthd made it boot into X. will try console= too thanks!
[17:10] <marvin24> janimo: good
[17:10] <janimo> marvin24, do you think it is a nvidia kernel bug?
[17:11] <marvin24> yes, I talked to an engineer from nvidia
[17:11] <marvin24> and he was able to reproduce it on ventana (tegra2 dev board)
[17:11] <marvin24> could also be ubuntu related ...
[17:11] <janimo> do they plan to address it in 3.1?
[17:11] <marvin24> but the kernel shouldn't oops
[17:11] <marvin24> janimo: yes
[17:11] <janimo> possibly, ubuntu userspace is a bit different
[17:12] <marvin24> we tried to track it down (and still try)
[17:13] <marvin24> janimo: I will request a new kernel build when it's fixed ;-)
[17:14] <janimo> marvin24, sure ;)
[17:14] <janimo> marvin24, back to the previous issue - the idea of single image for multiple kernels is _dependent_ on device tree? Since in menuconfig you can check any number of arches to support
[17:15] <marvin24> with "arches", do you mean omap, tegra, ...
[17:15] <marvin24> or boards?
[17:16] <marvin24> you can select different boards, but our bootloader is buggy and does not accept multi-board kernels
[17:17] <marvin24> janimo: no idea what tf101 bootloader does
[17:17] <janimo> marvin24, afacit just takes an android bootimg and starts it :)
[17:18] <janimo> like the ac100 one, not sure about details
[17:18] <janimo> marvin24, ah so the ac100 bootloader would choke on a kernel image that has any other board than paz00 enabled too?
[17:18] <janimo> I meant just tegra2 based ones (paz00 and tf101 in particular)
[17:22] <marvin24> in fact, no one knows what it does
[17:22] <marvin24> s*y
[17:31] <marvin24> I had the impression, that the bootloader reads the machine-id from the kernel and feeds it back to the kernel
[19:12] <LetoThe2nd> prpplague: howdy pardner
[19:12] <prpplague> greetings
[19:13] <LetoThe2nd> prpplague: found time to look at the video i told you?
[19:13] <prpplague> LetoThe2nd: sorry no, yesterday was crazy i had some car troubles from the previous afternoon
[19:13] <prpplague> LetoThe2nd: can you give me the link again? i have it at home
[19:13] <LetoThe2nd> prpplague: ah kay... hope you got things roted out?
[19:14] <prpplague> LetoThe2nd: yea
[19:14] <LetoThe2nd> sorted out, even :/
[19:14] <prpplague> LetoThe2nd: i had the car worked on friday, turns out they put one of the nuts back on without the cotter pin
[19:14] <LetoThe2nd> aw :(
[19:15] <prpplague> LetoThe2nd: damn near got killed by a large truck on monday afternoon after the front passenger tie rod came off while i was cross an highway intersection
[19:15] <LetoThe2nd> prpplague: http://www.youtube.com/watch?v=ufBCoHP-8Yk&list=UUXHs7mzjNipr-xp1Bps2zew&index=2&feature=plcp
[19:16]  * prpplague looks
[19:16] <prpplague> LetoThe2nd: you said about 50 seconds in?
[19:16] <LetoThe2nd> prpplague: interesting part is from 0:55 onwards or so.
[19:16] <LetoThe2nd> prpplague: glad nothing bad happened then
[19:16] <prpplague> LetoThe2nd: this video is work safe correct?
[19:16] <LetoThe2nd> prpplague: totally yes.
[19:17] <LetoThe2nd> prpplague: its from an educational fair near me.
[19:18] <prpplague> LetoThe2nd: ahh dandy!
[19:18] <LetoThe2nd> prpplague: and inside that rc car is a panda :)
[19:18] <prpplague> LetoThe2nd: yea i think those guys were in cambridge a while back at ELC
[19:18] <prpplague> LetoThe2nd: with an early prototype of the design
[19:20] <LetoThe2nd> prpplague: will meet those guys sometime in the next two weeks probably, was really surprised there are other panda users in this small town.
[19:22] <prpplague> LetoThe2nd: hehe
[19:22] <LetoThe2nd> prpplague: btw got one or two minutes for private?
[19:22] <LetoThe2nd> (just noticed we're not even in #pandaboard)
[19:22]  * prpplague checks the time
[19:22] <prpplague> LetoThe2nd: yea, got about 5-10 mintues
[21:04] <smplman> does anyone know where i can find the status of the SGX drivers on a BB XM running 12.04?
[21:04] <smplman> and audio also
[22:32] <xranby_ac100> smplman: check the linaro website
[22:32] <xranby_ac100> smplman: all the latest linaro releases are based on 12.04 with improved kernels and drivers where available
[22:34] <xranby_ac100> smplman: sorry i think i gave you bad advice.. they only support the pandaboard nowdays


[00:08] <Jordan_U> What should I do if I throw a regular baseball in the air and rather than coming back down, it simply keeps going up on its own power? What would a chef say if I asked them the same question?
[05:31] <h00k> lots of !es in #ubuntu
[05:38] <h00k> IdleOne: that
[05:38] <h00k> s who I was having issues with earlier
[05:38] <IdleOne> they joined -es now
[05:38] <h00k> they've had warning, and direction to /join #ubuntu-es
[07:42] <jussi01-nom> Hi everyone.
[07:43] <jussi01-nom> I am aware about the server, Im trying to get onto the guy.
[07:43] <Tm_T> oh goody
[09:12] <lhavelund> this is good news.
[09:16] <lhavelund> poor jussi. getting woken up to a dead bot, instantly put in charge of fixing it.
[09:18] <tonyyarusso> lhavelund: Better than a doctor being put in charge of fixing a dead patient.
[09:28] <lhavelund> tonyyarusso: I consider them similar situations.
[13:00] <dontknow> hi
[13:00] <dontknow> i banned from ubuntu and ubuntu offtopics
[13:01] <dontknow> i would like you to reverse it
[13:05] <dontknow> anyone here?
[13:07] <Tm_T> dontknow: hi, do you remember why you were banned?
[13:07] <dontknow> Tm_T: i said ubuntu 12.10 adding spyware and they will not have my root anymore
[13:10] <dontknow> i mentioned couple of times, i was angry
[13:14] <dontknow> Tm_T:?
[13:23] <chu> Hello dontknow
[13:25] <dontknow> chu: hello
[13:26] <dontknow> chu: do you have autority to take ban back?
[13:28] <chu> There are a few things I can comment on right now regarding your position. The first, and possibly the most important, is that there is a guideline for participating in Ubuntu related channels, which I gather you have not read. Corresponding to this guideline is an enforced code of conduct for using these IRC channels.
[13:29] <chu> dontknow: The guidelines for using the Ubuntu channels can be found here: http://wiki.ubuntu.com/IRC/Guidelines
[13:31] <dontknow> chu: i agree with guidelines
[13:32] <chu> The link to the guidelines above mentions the Ubuntu code of conduct too. Take note that this is taken *very* seriously.
[13:35] <dontknow> chu: i can criticise
[13:35] <chu> Sure, no one said you couldn't.
[13:39] <dontknow> chu: i read the code of conduct
[13:41] <chu> I am reading the log of your ban in #ubuntu-offtopic (on the 24th of September) and to be honest, I fail to see any evidence of you taking this seriously. First and foremost you have failed to acknowledge the topic in the guidelines titled "Language and Subject", so I doubt you have read (nor "agree") with the guidelines. While there's nothing wrong with criticism, the manner you present your criticisms in is incredibly hostile, simply
[13:41] <chu> this means there cannot be any constructive discussion resulting.
[13:42] <dontknow> chu: send me link please
[13:42] <dontknow> with pm
[13:43] <chu> You just told me that you have read (and agree) with the guidelines, but apparently you missed the first paragraph, which says: "Please also be aware that Ubuntu channels are logged"
[13:45] <dontknow> chu: yes. i wanted log link
[13:51] <dontknow> chu: do you take ban back or not?
[13:57] <dontknow> chu: i can't find ubuntu-offtopic logs there http://irclogs.ubuntu.com/2012/09/23/?C=N;O=D
[13:59] <dontknow> wow! amazing
[14:00] <DJones> Looks like he's lost connection for a bit, give him a bit of time to get reconnected
[14:01] <dontknow> chu: are you there?
[14:01] <chu> Yeah, sorry, internet dropped out.
[14:02] <dontknow> i can't find ubuntu-offtopic logs there http://irclogs.ubuntu.com/2012/09/23/?C=N;O=D
[14:02] <chu> Well here: http://paste.ubuntu.com/1391632/
[14:02] <chu> My mistake, I was under the impression that #ubuntu-offtopic was logged. But maybe not officially.
[14:07] <dontknow> chu: lol i read the log, i am behind what i said there. ikonia is overreacted
[14:09] <chu> Your style of communication is not very encouraging - I can completely understand the reason you were banned in the first place. Remember, we want #ubuntu* channels to be _friendly_ places for discussion.
[14:10] <dontknow> chu: i don't attack personally someone
[14:11] <ikonia> it is a waste of time to discuss this with dontknow
[14:11] <ikonia> he is a known troll and trake pride it in
[14:12] <ikonia> I suggest not wasting any more time with dontknow
[14:12] <dontknow> ikonia: who said that?
[14:12] <ikonia> me
[14:13] <dontknow> you are wrong then!
[14:14] <dontknow> when did i become troll? and "known troll" i am wondering
[14:15] <dontknow> ikonia: let's discuss then?
[14:15] <chu> Ok, dontknow I ask that you think about this a bit more and come back in due time, show some evidence you have "matured" (or more, acknowledge the reasons for your ban). I'm not going to lift the bans at this moment.
[14:15] <ikonia> no
[14:16] <dontknow> ikonia: what are the things that you disagree with me?
[14:18] <dontknow> chu: well, i am matured already. tell me what you disagree and lets discuss
[14:18] <ikonia> I don't wish to discuss it further, I've made my point in the logged channel. From that point of view, I'm done
[14:22] <dontknow> ikonia: what line shows your point in that log?
[14:22] <ikonia> I didn't paste a log
[14:22] <ikonia> I gave the channel my opinion.
[14:23] <dontknow> you gave the channel but me?
[14:23] <dontknow> after banning me?
[14:24] <chu> dontknow: I disagree that you have matured enough. I will not discuss this further with you. If you feel that you have been treated wrongly, you can consult the appeal process as described here: https://wiki.ubuntu.com/IRC/AppealProcess - But note that taking this later route could potentially do more harm than good in your case, so I strongly suggest just waiting it out and come back in due time.
[14:25] <dontknow> chu: there will be no need for that
[14:58] <ikonia> hello lufu
[17:07] <bazhang> a robin hood of sorts!
[17:09] <Pici> how, what uhh?
[17:19] <ikonia> hello nikolam
[17:20] <nikolam> hello ikonia . Resolving +g on #ubuntu by bazhang  , me not being shutting up instantly on swap file topic.
[17:20] <ikonia> ok, I'll try to look it up, but anything I should know ?
[17:21] <nikolam> ikonia, +q, sorry. I will send you log.
[17:21] <bazhang> nikolam, hi
[17:22] <ikonia> nikolam: no need, bazhang is here
[17:44] <bazhang> now he's joined #xubuntu
[17:44] <knome> who?
[17:44] <Pici> nikolam
[17:44] <knome> ah yes, he's been giving a bit trouble lately
[17:44] <bazhang> he likes to rant about adbuntu/google/privacy
[17:45] <knome> that's not what he's been ranting about in #x
[17:45] <bazhang> heh
[17:45] <knome> he's a "regular"
[18:00] <ikonia> hi nikolam, bazhang is still active
[18:01] <nikolam> ok will come back again. thank you.
[18:01] <ikonia> ?
[18:01] <Pici> nikolam: no. stay.
[18:01] <bazhang> nikolam, hi
[18:01] <nikolam> ok staying. Thanks.
[18:01] <ikonia> no, I mean bazhang is active so you can resolve your mute with him
[18:01] <nikolam> hi bazhang
[18:02] <bazhang> nikolam, I need you to read the channel guidelines and the code of conduct for Ubuntu channels
[18:03] <bazhang> !guidelines | nikolam
[18:03] <bazhang> !coc | nikolam
[18:05] <nikolam> i did not know about no away messages. thats new to me. ok.
[18:06] <bazhang> nikolam, just to be clear: #ubuntu is support only. not for complaints about privacy/google/amazon
[18:06] <nikolam> there is also reporters guide.
[18:06] <nikolam> supporters. sorry
[18:07] <nikolam> bazhang, so you think that responding to complaints is nont support itself
[18:08] <bazhang> nikolam, and when asked to move to the #ubuntu-offtopic channel /stay on topic, then one does that
[18:08] <IdleOne> #ubuntu is not the channel to make complaints in, responding to them is just as off topic.
[18:08] <nikolam> bazhang, I know, was not asked lately.
[18:09] <bazhang> nikolam, sure you were. thats one of the reasons for the +q
[18:09] <nikolam> Aha I see IdleOne . But does "ubuntu make unwanted connections
[18:09] <nikolam> classify as complaint / bug or technical issue.
[18:09] <nikolam> ok
[18:10] <nikolam> Hm complaints can then be channeled to bug reports?
[18:11] <nikolam> I think I signed CoC about 6 or more years ago. I hope things are not changed too much since.
[18:11] <AlanBell> nikolam: specifically bug 1054776
[18:13] <AlanBell> we tend to prefer people to add comments to bug reports when they have additional useful information to contribute to a solution, such as a patch or steps to reproduce the issue
[18:13] <nikolam> aha I see. maybe issue is just too big, bug adding to bug is best way to have them in place, Yes.
[18:14] <AlanBell> what you can certainly do is click the green text at the top and mark it as affecting you too
[18:14] <nikolam> uh, just reading that bug report makes me.. frighted. That is F from FUD
[18:15] <AlanBell> along with the 431 other people who did that. It isn't as if this issue is something that isn't known.
[18:15] <nikolam> AlanBell, of course. uh.
[18:15] <AlanBell> now, is there any other issue we can help you with relevant to this channel?
[18:17] <nikolam> AlanBell, i am re-reading CoC as per bazhang request Atm.
[18:19] <nikolam> I think `be respectfull ` part is very important.
[18:20] <IdleOne> The point of you reading both the guidelines and coc was not to get your opinion on them. We need you to understand them and follow both while in Ubuntu irc channels.
[18:22] <nikolam> ok IdleOne
[18:25] <nikolam> ok bazhang re-read and understand.
[18:29] <nikolam> I now need to go, because I have a date, I got to get part from channel. See you, bazhang
[18:29] <bazhang> ok...
[18:31] <IdleOne> issue resolved.
[18:32] <bazhang> I wonder if he knows that the +q is still there
[18:35] <IdleOne> of course not.
[18:56] <bazhang> * [{xmb}] (~alexmbott@80-218-123-178.dclient.hispeed.ch): fucked microsuxx bot
[18:56] <bazhang> wow annoying
[19:03] <bazhang> he's a better sheller
[20:30] <Pici> thats the best response I've seen for learning that we don't support webmin.
[20:30] <Pici> "woops?"
[21:35] <lhavelund> ghehehe.
[21:35]  * lhavelund hops for a test!
[21:35] <lhavelund> ohoho.
[22:05] <elky> we gave you ops? oh dear
[22:08] <lhavelund> elky: well, december 21st *is* coming up.
[22:36] <elky> oh of course
[22:44] <elky> looks like someone broke the -meeting topic


[10:41] <phillw> Hi, is it possible to add  the lubuntu "Product (Upgrade)" section of the ISO Tracker? One of the testers has found a bug, but can't allocate it to the tracker.
[13:19] <jibel> phillw, done
[13:20] <phillw> jibel thanks, Julien is working on the bug now, but I'll still add it for tracking purposes.
[15:06] <PaoloRotolo> Hi all!
[23:30] <MaskedEnigma> Hello?