[04:19] <jam> wallyworld_: I figured out what broke the test suite for the "no such variable hostname".
[04:19] <jam> The issue is that "hostname" is defined in service_test.go, but used in "service_http.go".
[04:19] <wallyworld_> ah ok, i looked but didn't see how i broke it
[04:19] <jam> So everything works fine when you run tests in novaserviec
[04:19] <wallyworld_> i found that too
[04:20] <jam> because it imports the test files to run the test suite.
[04:20] <jam> but when "nova" tests import "service_http"
[04:20] <jam> it doesn't import the test files
[04:20] <jam> (because it shouldn't)
[04:20] <wallyworld_> makes sense
[04:20] <jam> so it is one of those cases where test definitions leak and make real code pass
[04:20] <jam> when it is broken if you try to use it directly.
[04:21] <wallyworld_> too bad go fmt doesn't check compilation
[04:21] <wallyworld_> there's also another breakage
[04:21] <jam> wallyworld_: right, so "go build" doesn't work in the novaservice directory
[04:21] <wallyworld_> to do with nova something or other not implementinng HTTPServe
[04:21] <jam> so we should be using: go build ./... && go test ./...
[04:21] <wallyworld_> go test ./... fails if there is a compile error
[04:22] <wallyworld_> so perhaps go build is redundant there
[04:22] <jam> and, as I've said before, global state is terrible, we shouldn't have it in the first place.
[04:22] <wallyworld_> yeah, agree
[04:22] <jam> wallyworld_: As I just said, cd testservice/novaservice ; go test passes
[04:22] <jam> go build fails
[04:22] <jam> we didn't *notice* until we used novaservice in nova testing.
[04:22] <wallyworld_> hmm, i've never seen go test not have an error if go build fails
[04:22] <jam> because nova doesn't import the novaservice test package
[04:23] <jam> wallyworld_: try it right now with trunk
[04:23] <wallyworld_> i'm prototyping in trunk, so it's a bt hard atm
[04:23] <wallyworld_> i need to create a new branch to work in
[04:23] <jam> wallyworld_: essentially, we had a latent build failure that we didn't see at r40, in r41 you started importing the code, and triggered the failure.
[04:23] <jam> wallyworld_: "bzr shelve" ?
[04:24] <wallyworld_> yeah, but i don't want to disrupt my train of thought just atm
[04:24] <jam> wallyworld_: np
[04:24] <wallyworld_> thanks for looking into that further, i was going to mention itagain at the standup
[04:25] <hazmat> so for updating the juju-core src tree w. goose .. what do folks do.. go get -u ?
[04:26] <jam> hazmat: yes
[04:26] <jam> its not perfect, but it seems to be the best we have right now
[04:26] <hazmat> jam.. with what value/pkg name?
[04:26] <jam> hazmat: "go get -u launchpad.net/juju-core/..."
[04:26] <jam> should also update all dependencies
[04:26] <hazmat> jam, thanks
[04:27]  * hazmat always forgets where to put ...
[04:28] <hazmat> i'm sure its easy once your used to it
[04:30]  * hazmat wonders if roger published his api callee tool
[04:32] <hazmat> aha http://godoc.org/code.google.com/p/rog-go/exp/cmd/gosym
[12:01] <jam> wallyworld_: poke if you are still around
[12:02] <wallyworld_> hi
[12:03] <jam> wallyworld_: so it might just be naming, but I'm looking over the code you pushed up, and it doesn't quite sit right.
[12:03] <wallyworld_> which bit?
[12:03] <jam> "unauthenticatedClient": IMO unauthenticated is a state that can be remedied by authenticating
[12:04] <wallyworld_> ok, i am happy to change names
[12:04] <jam> and having an Authenticator that doesn't authenticate...
[12:04] <wallyworld_> it's a means to allow code to be shared
[12:05] <wallyworld_> so the core logic to send requests can be ignorant of if it is running with somwthing that needs authenticatin
[12:05] <wallyworld_> so the authentication stuff is just noops
[12:05] <jam> so, nonAuthenticatingClient seems to me like a client that wouldn't try to authenticate (naming), but I don't know that it would be an Authenticator.
[12:05] <jam> wallyworld_: but is that better than just having a boolean about whether it *needs* to authenticate?
[12:06] <wallyworld_> hmmm. i could look at that for sure
[12:06] <wallyworld_> the AUthentication interface though also provides MakeServiceURL
[12:07] <wallyworld_> since that is different depending on the type of client
[12:07] <wallyworld_> and go doesn't support virtual methods :-(
[12:07] <wallyworld_> i really wanted to do it differently, like I would have in Java or C++, but alas
[12:08] <jam> wallyworld_: I agree that we likely need an interface at that level, I'm just trying to sort out how the pieces fit. And at least the naming of things meant it didn't quite fit well in my head.
[12:08] <wallyworld_> i did struggle with the naming
[12:09] <wallyworld_> the auth client needs to provide Authernticate(), UserId(), Token() etc
[12:10] <wallyworld_> and the non auth client needs to provide noops for those if we want to allow the same client interface to be used everywhere
[12:10] <wallyworld_> unless I cast when needed
[12:10] <wallyworld_> which I can do
[12:11] <jam> wallyworld_: since we won't have any of that actual data, it seems like we should be doing it differently.
[12:11] <jam> we shouldn't return fake data for each one.
[12:11] <jam> like, if we don't have an authenticator, we try to do the request without authentication
[12:11] <jam> vs we have one that may just not have auth'd yet
[12:11] <wallyworld_> i was trying to avoid type casts but i think i will need to do that
[12:11] <wallyworld_> i'll rework it and resubmit
[12:12] <jam> c.auth != nil doesn't need a type cast :)
[12:12] <wallyworld_> i wasn't 100% happy with the result, but I was happy that it all worked
[12:12] <wallyworld_> no not there, in other places
[12:12] <wallyworld_> like tests
[12:13] <wallyworld_> but let me rework it - the 2nd version should be better
[12:13] <Aram> > go doesn't support virtual methods
[12:13] <wallyworld_> yeah i know :-(
[12:13] <Aram> what? dynamic dispatch is an extremely used idiom in Go.
[12:13] <jam> Aram: go doesn't support subclassing in the standard sense
[12:14] <jam> is I think more what he was talking about
[12:14] <wallyworld_> methods are staically bound to classes
[12:14] <Aram> use an interface.
[12:14] <wallyworld_> it's a limitation Java and C++ refugees initially have to learn to deal with
[12:15] <wallyworld_> yes, the zgo idiom is an interface but sometimes it would be easier not to have to do that
[12:15] <Aram> you don't have to do anything. you define an interface and type i := c somewhere instead of typing C implements I somewhere else.
[12:16] <wallyworld_> you do have to rearrange your business logic sometimes
[12:17] <wallyworld_> if you are used to virtual methods and expect a subclass to invoke the right method, you need to extract the business logic when you discover it doesn't work
[12:17] <wallyworld_> to get it off the class and into an interface created just because virtual methods aren't supported
[12:17] <Aram> i.m() always invokes the right method if you set up i correctly (equivalent to setting a subclass correctly)
[12:18] <Aram> s/ui i/it up/
[12:18] <wallyworld_> yes, but it's a different arrangement of business logic and sometimes it means that stuff which belongs together on a class has to be split
[12:19] <wallyworld_> because of non support for virtual methods
[12:19] <wallyworld_> it's not such a big issue, just different to other languages which support such things
[12:19] <Aram> have to go buy some bread.
[12:19] <Aram> rogpeppe: ^ ^
[12:19] <jam> wallyworld_: if you can set the MP to WIP (I can do it, but I'd rather not do that to other people's MPs)
[12:20] <wallyworld_> jam: sure, thanks for the input, i'm glad you brought up the same issues i was having when i hit submit :-)
[12:20] <jam> wallyworld_: I'm glad you felt the same way, too. :)
[12:21] <wallyworld_> jam: yeah, it was EOD and I just wanted to feel i had something done, so i thought it would be worth getting input
[12:21] <rogpeppe> jam, wallyworld: i'll have a look at this
[12:22] <wallyworld_> rogpeppe: thanks, although i'm setting it back to wip to clean up some stuff, so don't look too hard just yet
[12:22] <rogpeppe> jam: in my experience, when these kinds of issues are resolved, the result is better structured.
[12:22] <rogpeppe> s/jam/wallyworld/ :-)
[12:23] <wallyworld_> which issues? the virtual method dicussion?
[12:23] <rogpeppe> wallyworld_: yes
[12:23] <rogpeppe> wallyworld_: presumably we're talking about https://codereview.appspot.com/6962052/ here?
[12:24] <rogpeppe> wallyworld_: (i haven't looked at it yet)
[12:24] <wallyworld_> yes
[12:24] <wallyworld_> i do like virtual methods, but if they are no supported, then stuff needs to be done differently
[12:26] <rogpeppe> wallyworld_: i'm not sure what you mean. all interface methods are virtual
[12:27] <wallyworld_> i mean on classes
[12:27] <wallyworld_> stucts
[12:27] <wallyworld_> structs
[12:27] <rogpeppe> wallyworld_: ah, you mean a class hierarchy isn't supported. that's true.
[12:28] <wallyworld_> yeah, so logic in a bases class calls method foo() and if it is a subclass, the subclass's foo() get invoked
[12:28] <wallyworld_> since that's not supported, you are forced to rip logic out of a class where it might be considered to belong
[12:28] <wallyworld_> and put it elsewhere
[12:30] <rogpeppe> wallyworld_: this is actually a good thing, although it's probably difficult to see that currently...
[12:30] <wallyworld_> yeah, difficult to see :-) since if everything else does it, it can't be that bad :-)
[12:31] <rogpeppe> wallyworld_: each type does what it does completely.
[12:31] <wallyworld_> and it causes issues when you loose access to class state when the logic is removed
[12:31] <wallyworld_> it's not necessarily bad, just different
[12:31] <rogpeppe> wallyworld_: in the end, IMHO, you get a better separation of concerns and more modular code.
[12:32] <wallyworld_> i'll take your word for it, i'm still to come around to that way of thinking :-) not enough Go experience yet
[12:33] <wallyworld_> i guess many people new to go have to unlearn past habits
[12:34] <rogpeppe> wallyworld_: it's certainly a different way of thinking. i think perhaps the crux is moving from thinking, when designing, "what *is* this?" to "what does this *do*?"
[12:34] <rogpeppe> wallyworld_: Go doesn't do "is a" relationships, other than when implementing interfaces
[12:35] <wallyworld_> sure, i guess at the moment i don't see that "what does this do" way of thinking is mutually exclusive to having virtual methods. but maybe i'll get there
[12:36] <wallyworld_> i'm actually having more of an issue with go's dependency version management
[12:36] <rogpeppe> wallyworld_: AFAICS, virtual methods are about defining something that is *almost* something else (but for the virtual methods).
[12:37] <rogpeppe> wallyworld_: yes, that's unfortunate - i have an idea for a little tool that might help with that.
[12:38] <wallyworld_> rogpeppe: it seems that many go people will defend the current state of affairs with go get etc, even though it just seems so wrong
[12:39] <wallyworld_> mixing what you are importing with the version you are import in the url which is then spread through every source file seems crazy to me
[12:39] <wallyworld_> violates the dry principal big time
[12:40] <rogpeppe> wallyworld_: i'm not sure. it doesn't seem too different from having the version in some metadata file somewhere in the same source tree
[12:40] <wallyworld_> big difference - you change the meta file in one place
[12:40] <wallyworld_> not update each and every import
[12:40] <rogpeppe> wallyworld_: sure, it's repeated info, but what if it was a single two-word command to change all the paths (and check consistency)?
[12:41] <wallyworld_> it introduces revision noise for starters
[12:41] <rogpeppe> wallyworld_: in the CL diffs?
[12:41] <wallyworld_> yes, and source revision history
[12:42] <rogpeppe> wallyworld_: i'm not sure that's a big issue. you're going to have a revision change there anyway (for the metadata) - the only question is the size of the diff.
[12:43] <wallyworld_> when reviewing or looking at past revisions, any excess noise distracts from trying to get to the heart of any changes
[12:44] <wallyworld_> and why repeat something all throughout the source code?
[12:44] <rogpeppe> wallyworld_: because it makes the version dependency clear in every piece of code that has it?
[12:45] <rogpeppe> wallyworld_: i agree it's verbose, but i'm not sure that i see a better alternative currently.
[12:45] <wallyworld_> that is true but i feel the cost outweighs the benefit
[12:45] <wallyworld_> there's lots of better alternatives :-)
[12:46] <wallyworld_> other languages/environments have solutions used successfully
[12:47] <rogpeppe> wallyworld_: there are quite a few benefits from having the package path as a universal currency that works independently of anything else.
[12:47] <wallyworld_> perhaps if it weren't copy and pasted throughout the source code
[12:48] <rogpeppe> wallyworld_: honestly, i think that's a benefit. each piece of source code completely describes its own dependencies.
[12:49] <wallyworld_> each peice of source code doesn't need to do that though - it's surperfulous boiler plate
[12:49] <wallyworld_> humans make mistakes and i would be surprised if someone didn't miss changing one import somewhere, or worse, 2 people committed at around the same time with different imports
[12:50] <wallyworld_> since the imports are repeated, someone might write a new source file with the "old" import version
[12:50] <wallyworld_> and commit that not realising someone else has committed a change which updates the imports elsewhere
[12:50] <rogpeppe> wallyworld_: ok, here's my plan for a tool
[12:51] <rogpeppe> wallyworld_: called, say, godep
[12:51] <rogpeppe> wallyworld_: usage: godep pkg....
[12:52] <rogpeppe> wallyworld_: it will look in all the source files under the current directory, and find any that have a version-independent matching package path
[12:52] <rogpeppe> wallyworld_: and change it to the specified package path
[12:52] <dimitern> wallyworld_, jam, etc. PTAL - just some comments and improved docs -  https://codereview.appspot.com/6968051
[12:52] <rogpeppe> wallyworld_: where a versioned package path is defined to be anything with an intermediate path name matching v[0-9]+
[12:53] <rogpeppe> s/intermediate path name/intermediate path element/
[12:53] <wallyworld_> rogpeppe: so the first time it is run, version independent paths get changed, but what about the next time?
[12:53] <rogpeppe> wallyworld_: it will also check all dependencies and make sure that they all import the same version
[12:53]  * dimitern >> lunch
[12:53] <rogpeppe> wallyworld_: all paths are versioned
[12:54] <rogpeppe> wallyworld_: just that labix.org/v2/mgo will match labix.org/v3/mgo, for example
[12:54] <wallyworld_> ah ok
[12:54] <rogpeppe> actually, govers was the name i was thinking of originally
[12:55] <wallyworld_> rogpeppe: that all sounds reasonable. it's the go equivalent of editing versions.cfg and changing mgo v2 to mgo v3 and comitting :-)
[12:55] <rogpeppe> wallyworld_: so then, to make juju-core use a new version of goose, you'd cd to juju-core root, and do govers launchpad.net/goose/v2
[12:56] <rogpeppe> wallyworld_: yes, but without the commit
[12:56] <wallyworld_> right
[12:58] <wallyworld_> rogpeppe: late here, off to bed, thanks for the interesting discussion. too bad it wasn't at a pub over some beers
[12:58] <rogpeppe> wallyworld_: too right
[12:58] <wallyworld_> next UDS maybe :-)
[12:58] <rogpeppe> wallyworld_: lets!
[12:58] <rogpeppe> wallyworld_: sweet dreams :-)
[12:58] <wallyworld_> be warned, i start dancing on the table after i have 1 or 2 pints
[12:59] <rogpeppe> wallyworld_: lol
[13:30] <rogpeppe> Aram, dimitern, fwereade_: i'd be interested to know what you think of the above idea
[14:58] <hazmat> rogpeppe, would you have any time today or tomorrow to discuss api
[14:58] <rogpeppe> hazmat: definitely
[14:59] <rogpeppe> hazmat: could do it now if you'd like
[14:59] <hazmat> rogpeppe, sounds good
[15:00] <rogpeppe> hazmat: https://plus.google.com/hangouts/_/2887f22fb3213cc9e9ccd07cd3569c8e06a255ee?authuser=0&hl=en-GB
[17:01] <fwereade__> rogpeppe, I hate to be a bore, but I think that https://codereview.appspot.com/6944058/ is uncontroversial in the light of our discussions online, and so I hope it should be an easy re-review
[17:02] <rogpeppe> fwereade__: ok. i thought you were on hols! :-)
[17:02] <rogpeppe> fwereade__: am on it
[17:02] <fwereade__> rogpeppe, I am, but, y'know -- laura is painting, cath's out buying booze, I am otherwise at a loose end ;p
[17:03] <rogpeppe> fwereade__: here's a little one for you (preparatory to losing flags from jujud): https://codereview.appspot.com/6972048/
[17:03] <fwereade__> rogpeppe, cool
[17:03] <fwereade__> rogpeppe, except that CL apparently does not exist
[17:04] <rogpeppe> fwereade__: oh bugger, one mo
[17:04] <rogpeppe> fwereade__: https://codereview.appspot.com/6963050/
[17:04] <rogpeppe> fwereade__: (i proposed it against a badly named branch originally)
[17:08] <rogpeppe> fwereade__: LGTM
[17:09] <fwereade__> rogpeppe, thanks -- and likewise :)
[17:09] <fwereade__> rogpeppe, I won;t merge it for a bit yet, so go ahead with yours if it's convenient
[17:10] <rogpeppe> fwereade__: it's fine - i'm actually knocking up a quick tool to try to ease the goose versioning pains
[17:10] <rogpeppe> fwereade__: i'd be interested in your views on the idea actually
[18:33]  * rogpeppe is off for the night.
[18:33] <rogpeppe> g'night anyone who's around
[20:03] <arosales> jcastro_: ping
[20:13] <hazmat> arosales, aren't you on holiday
[20:16] <arosales> hazmat:  sudo holiday :-)
[20:49] <jcastro_> that should be pseudo holiday, heh


[09:34] <faenil> mzanetti: I understand you don't want to commit or you're too busy sprinting...but please at least give me an alternative
[09:35] <faenil> give me an ETA, or just tell me it's not going to happen and I should try with a tablet instead, or with vivid+ppa, I don't know
[09:35] <faenil> peace :)
[15:07] <rhuddie> mterry, hi, I noticed that the 'no sim inserted' page is no longer being displayed in the startup settings wizard
[15:07] <rhuddie> mterry, do you know is this an intended change, or bug?
[15:10] <mterry> rhuddie, sounds like a bug
[15:10] <mterry> ltinkl, do you know anything about this? ^
[15:14] <josharenson> greyback: what is the env variable? to make qtmir log input events?
[15:15] <greyback> josharenson: QT_LOGGING_RULES="qQT_LOtmir.*.debug=true"
[15:15] <greyback> eep
[15:15] <greyback> josharenson: QT_LOGGING_RULES="qtmir.*.debug=true"
[15:15] <josharenson> greyback: ah, thanks
[15:17] <mzanetti> faenil, good morning. will try to get it running here now
[15:19] <faenil> mzanetti: <3 thanks man
[15:19] <mzanetti> (fwiw, I still struggle with starting the unity8 session at all)
[15:20] <faenil> mzanetti: previous issues I had that caused those problems (on other laptops) were due to multiple kms packages installed
[15:20] <faenil> check /usr/lib/blabla/mir/client-platforms
[15:20] <faenil> ideally you should only have one, afaik
[15:20] <faenil> if you have more , uninstall those packages
[15:21] <mzanetti> I do have 2
[15:29] <faenil> mzanetti: also check if you have mesa (or mesa2) mir platform installed
[15:29] <faenil> I think that was causing issues as well
[15:31] <mzanetti> faenil, that must be it, yes
[15:31] <mzanetti> thanks a lot
[15:32] <mzanetti> trying now (did an upgrade first)
[15:32] <mzanetti> rather still doing... sloooow network
[15:37] <cimi> Saviq, https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1536372
[15:45] <faenil> mzanetti: np :)
[15:45] <faenil> at least we save each other's time :D
[17:41] <dandrader> dednick, https://code.launchpad.net/~dandrader/qtmir/appRestart-lp1527737/+merge/281701
[17:41] <dandrader> dednick, appQuitsRightAfterBeingSuspended test
[19:46] <mterry> mzanetti, engine->setObjectOwnership(as, QQmlEngine::CppOwnership);
[19:47] <mterry> confirmed it works, even before passing the object back to qml
[20:13] <Pursche01> Hello there, I have what could be a stupid question. I am looking for the correct IRC room to ask about Ubuntu's mouse handling, Unity was listed as the keyboard menu. Do you have any idea where I could ask questions about the mouse?
[20:19] <mzanetti> mterry, really? I thought the registerSingletonType() wouldn't care about it
[20:21] <mterry> mzanetti, well I haven't confirmed it's worked in *practice* -- I chased the code and confirmed that someone else on the internet said it works...
[20:22] <mterry> mzanetti, that's like the same thing
[20:22] <mzanetti> this usually works, but I think the singleton one is a bit special... you want to try tho


[00:15] -queuebot:#ubuntu-release- New binary: r-cran-vdiffr [amd64] (focal-proposed/universe) [0.3.1+dfsg-1] (no packageset)
[00:15] -queuebot:#ubuntu-release- New binary: r-cran-vdiffr [s390x] (focal-proposed/universe) [0.3.1+dfsg-1] (no packageset)
[00:15] -queuebot:#ubuntu-release- New binary: r-cran-vdiffr [ppc64el] (focal-proposed/universe) [0.3.1+dfsg-1] (no packageset)
[00:17] -queuebot:#ubuntu-release- New binary: r-cran-vdiffr [arm64] (focal-proposed/universe) [0.3.1+dfsg-1] (no packageset)
[00:17] -queuebot:#ubuntu-release- New binary: r-cran-vdiffr [armhf] (focal-proposed/universe) [0.3.1+dfsg-1] (no packageset)
[01:43] <vorlon> RikMills: Unable to obtain lock file:///srv/ubuntu-archive/public_html/seeds/kubuntu.disco/ held by Ubuntu Archive<EMAIL_ADDRESS>on snakefruit (process #14802), acquired 563 hours, 57 minutes ago.
[01:43] <vorlon> RikMills: (sorted)
[03:46] -queuebot:#ubuntu-release- New: accepted r-cran-vdiffr [amd64] (focal-proposed) [0.3.1+dfsg-1]
[03:46] -queuebot:#ubuntu-release- New: accepted r-cran-vdiffr [armhf] (focal-proposed) [0.3.1+dfsg-1]
[03:46] -queuebot:#ubuntu-release- New: accepted r-cran-vdiffr [s390x] (focal-proposed) [0.3.1+dfsg-1]
[03:46] -queuebot:#ubuntu-release- New: accepted r-cran-vdiffr [arm64] (focal-proposed) [0.3.1+dfsg-1]
[03:46] -queuebot:#ubuntu-release- New: accepted raysession [source] (focal-proposed) [0.8.3-0ubuntu2]
[03:46] -queuebot:#ubuntu-release- New: accepted r-cran-vdiffr [ppc64el] (focal-proposed) [0.3.1+dfsg-1]
[03:49] -queuebot:#ubuntu-release- New binary: raysession [amd64] (focal-proposed/universe) [0.8.3-0ubuntu2] (no packageset)
[03:49] <teward> thank you to whoever accepted raysession :)
[03:53] -queuebot:#ubuntu-release- New: accepted raysession [amd64] (focal-proposed) [0.8.3-0ubuntu2]
[05:18] -queuebot:#ubuntu-release- New binary: avogadro [amd64] (focal-proposed/none) [1.91.0-1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: libfec [amd64] (focal-proposed/none) [1.0+20161003-1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: vmatch [amd64] (focal-proposed/none) [2.3.0+git20200101.0.b1bd228+dfsg-1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: golang-k8s-sigs-yaml [amd64] (focal-proposed/none) [1.1.0-1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: python-exchangelib [amd64] (focal-proposed/none) [2.1.1-1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: plink2 [amd64] (focal-proposed/none) [2.00~a2-191128+dfsg-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: avogadro [arm64] (focal-proposed/none) [1.91.0-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: libfec [arm64] (focal-proposed/none) [1.0+20161003-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: avogadro [armhf] (focal-proposed/none) [1.91.0-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: avogadro [ppc64el] (focal-proposed/none) [1.91.0-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: libfec [armhf] (focal-proposed/none) [1.0+20161003-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: avogadro [s390x] (focal-proposed/none) [1.91.0-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: libfec [s390x] (focal-proposed/none) [1.0+20161003-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: vmatch [s390x] (focal-proposed/none) [2.3.0+git20200101.0.b1bd228+dfsg-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: vmatch [ppc64el] (focal-proposed/none) [2.3.0+git20200101.0.b1bd228+dfsg-1] (no packageset)
[06:21] -queuebot:#ubuntu-release- New: accepted python-exchangelib [amd64] (focal-proposed) [2.1.1-1]
[06:21] -queuebot:#ubuntu-release- New: accepted golang-k8s-sigs-yaml [amd64] (focal-proposed) [1.1.0-1]
[06:22] -queuebot:#ubuntu-release- New: accepted avogadro [amd64] (focal-proposed) [1.91.0-1]
[06:22] -queuebot:#ubuntu-release- New: accepted avogadro [armhf] (focal-proposed) [1.91.0-1]
[06:22] -queuebot:#ubuntu-release- New: accepted avogadro [s390x] (focal-proposed) [1.91.0-1]
[06:22] -queuebot:#ubuntu-release- New: accepted avogadro [arm64] (focal-proposed) [1.91.0-1]
[06:22] -queuebot:#ubuntu-release- New: accepted plink2 [amd64] (focal-proposed) [2.00~a2-191128+dfsg-1]
[06:22] -queuebot:#ubuntu-release- New: accepted avogadro [ppc64el] (focal-proposed) [1.91.0-1]
[06:23] -queuebot:#ubuntu-release- New: accepted libfec [amd64] (focal-proposed) [1.0+20161003-1]
[06:23] -queuebot:#ubuntu-release- New: accepted libfec [armhf] (focal-proposed) [1.0+20161003-1]
[06:23] -queuebot:#ubuntu-release- New: accepted libfec [arm64] (focal-proposed) [1.0+20161003-1]
[06:23] -queuebot:#ubuntu-release- New: accepted libfec [s390x] (focal-proposed) [1.0+20161003-1]
[06:23] -queuebot:#ubuntu-release- New: accepted vmatch [amd64] (focal-proposed) [2.3.0+git20200101.0.b1bd228+dfsg-1]
[06:23] -queuebot:#ubuntu-release- New: accepted vmatch [s390x] (focal-proposed) [2.3.0+git20200101.0.b1bd228+dfsg-1]
[06:23] -queuebot:#ubuntu-release- New: accepted vmatch [ppc64el] (focal-proposed) [2.3.0+git20200101.0.b1bd228+dfsg-1]
[09:07] <doko> apw, sforshee: kpatch ping
[09:16] <Laney> gscan2pdf/arm64 is looking weird, hang on, I'll look into that
[09:22] <apw> doko, i think that go passed to our livepatch folk for action
[09:24] <doko> apw: who could I ping? e.g. the package has no rdeps, could we demote it to proposed for a while?
[09:24] <apw> doko, i suspect that will be a yes, but start with ben_r
[09:41] <Laney> hmm it's hanging in the build
[09:41] <Laney> but why don't we detect that
[09:52] -queuebot:#ubuntu-release- Unapproved: glibc (eoan-proposed/main) [2.30-0ubuntu2 => 2.30-0ubuntu2.1] (core)
[10:27] <Laney> do not understand
[10:27] <Laney> something is killing the instance
[10:27] <Laney> but i don't think it is the regular timeout
[10:28]  * Laney runs with --debug and default timeouts
[10:28] <Laney> going to kill those in progress test requests
[10:28] <Laney> if someone wanted to debug gscan2pdf/arm64 directly that would also be helpful since it is failing
[10:43] <tjaalton> I've mistakenly rejected an upload to proposed, how to recover it back to the unapproved queue?
[10:43] <apw> tjaalton, you can't; you can accept it from rejected though
[10:43] <tjaalton> apw: but it bypasses the tooling?
[10:44] <apw> tjaalton, if you want it to remain unapproved; i don't think there is any way to do that other than re-upload it
[10:44] <apw> tjaalton, you can sru-review -q Rejected i believe
[10:44] <tjaalton> ah, nice
[10:45] <apw> tjaalton, or accept it manually, and use the sru-accept backend directly
[10:45] <tjaalton> yeah the rejected queue had more than one upload so -q didn't qork
[10:45] <tjaalton> work
[10:49] <apw> sru-accept then, but you need the list of bugs from the _changes
[10:52] <LocutusOfBorg> hello cjwatson, looks like the service diff from version x to x+1 on launchpad stopped again, do you have a long enough stick with you?
[10:52] <tjaalton> apw: yep
[10:55] <cjwatson> LocutusOfBorg: Looks like that job is running to me, so probably just backlogged.
[10:56] <cjwatson> I can't make it go faster.
[10:56] <cjwatson> (seems to be processing kernel diffs and such)
[10:57] <apw> kernels diffs are horribly slow
[11:09] <rbalint> hi, i'd like to start the libnfs 4.0.0 mini transition in Ubuntu, rebuilds went ok: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3798
[11:18] <LocutusOfBorg> ok thanks, I tried to wait half an hour, and nothing appeared, so I'm happy to know minions are working
[11:25] -queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.3 => 1.2.10-1ubuntu2~ubuntu18.04.3] (desktop-core)
[11:26] -queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.3 => 1.2.10-1ubuntu2~ubuntu18.04.3] (desktop-core)
[11:26] -queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.3 => 1.2.10-1ubuntu2~ubuntu18.04.3] (desktop-core)
[11:30] -queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.3 => 1.2.10-1ubuntu2~ubuntu18.04.3] (desktop-core)
[12:25] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-76.86] (core, kernel)
[12:25] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (eoan-proposed/main) [5.3.0-29.31] (core, kernel)
[12:25] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (eoan-proposed/main) [5.3.0-29.31] (core, kernel)
[12:25] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-76.86] (core, kernel)
[12:25] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (eoan-proposed/main) [5.3.0-29.31] (core, kernel)
[12:27] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (eoan-proposed/main) [5.3.0-29.31] (core, kernel)
[12:30] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (eoan-proposed) [5.3.0-29.31]
[12:30] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (eoan-proposed) [5.3.0-29.31]
[12:30] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (eoan-proposed) [5.3.0-29.31]
[12:30] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (eoan-proposed) [5.3.0-29.31]
[12:30] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-76.86]
[12:30] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-76.86]
[13:44] <mfo> sil2100, hey Lukasz! If you happen to have a chance, I'd like to ask for checking/review on the util-linux SRUs in the e/b/x upload queues, please.  Thank you!
[13:52] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-amdgpu-hwe-18.04 (bionic-proposed/main) [19.0.1-1~18.04.1 => 19.0.1-1ubuntu1~18.04.1] (no packageset)
[13:52] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-ati-hwe-18.04 (bionic-proposed/main) [1:19.0.1-0ubuntu1~18.04.1 => 1:19.0.1-1ubuntu1~18.04.1] (no packageset)
[13:52] <tjaalton> sil2100: hi, these were unfortunately left out of the hwe stack update, please check when convenient.. basically a single commit added on top of the current version ^
[14:36] -queuebot:#ubuntu-release- New binary: rhythmbox [amd64] (focal-proposed/main) [3.4.4-1ubuntu1] (ubuntu-desktop)
[15:11] <Laney> just saw st_graber demo lxd clustering
[15:11] <Laney> seems like we could use this to make our lives easier in autopkgtest
[16:00] <rbalint> doko, i'm starting the libnfs transition ~half hour from now if no one objects
[16:18] -queuebot:#ubuntu-release- New binary: plasma-discover [ppc64el] (focal-proposed/universe) [5.17.90-0ubuntu2] (kubuntu)
[16:19] -queuebot:#ubuntu-release- New binary: plasma-discover [s390x] (focal-proposed/universe) [5.17.90-0ubuntu2] (kubuntu)
[16:23] -queuebot:#ubuntu-release- New binary: plasma-discover [amd64] (focal-proposed/universe) [5.17.90-0ubuntu2] (kubuntu)
[16:27] -queuebot:#ubuntu-release- New binary: plasma-discover [arm64] (focal-proposed/universe) [5.17.90-0ubuntu2] (kubuntu)
[16:27] -queuebot:#ubuntu-release- New binary: plasma-discover [armhf] (focal-proposed/universe) [5.17.90-0ubuntu2] (kubuntu)
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.3]
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.3]
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.3]
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [i386] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.3]
[17:10] -queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu543.14 => 20101020ubuntu543.15] (core)
[17:18] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (eoan-proposed) [1.2.10-1ubuntu4]
[17:18] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (eoan-proposed) [1.2.10-1ubuntu4]
[17:18] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (eoan-proposed) [1.2.10-1ubuntu4]
[17:18] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [i386] (eoan-proposed) [1.2.10-1ubuntu4]
[17:19] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-ati-hwe-18.04 [source] (bionic-proposed) [1:19.0.1-1ubuntu1~18.04.1]
[17:21] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-amdgpu-hwe-18.04 [source] (bionic-proposed) [19.0.1-1ubuntu1~18.04.1]
[17:22] -queuebot:#ubuntu-release- New binary: prometheus-hacluster-exporter [amd64] (focal-proposed/universe) [0.4.0-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: flatbuffers [amd64] (focal-proposed/universe) [1.11.0+dfsg1-1.1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: lablgtk-extras [amd64] (focal-proposed/universe) [1.6-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: light [amd64] (focal-proposed/universe) [1.2.1-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: lablgtk-extras [s390x] (focal-proposed/universe) [1.6-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: light [s390x] (focal-proposed/universe) [1.2.1-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: light [ppc64el] (focal-proposed/universe) [1.2.1-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (eoan-proposed) [1:20200114.1-0ubuntu<IP_ADDRESS>]
[17:24] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (disco-proposed) [1:20200114.1-0ubuntu<IP_ADDRESS>]
[17:26] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (bionic-proposed) [1:20200114.1-0ubuntu<IP_ADDRESS>]
[17:26] -queuebot:#ubuntu-release- New binary: lablgtk-extras [ppc64el] (focal-proposed/universe) [1.6-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: prometheus-hacluster-exporter [s390x] (focal-proposed/universe) [0.4.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: prometheus-hacluster-exporter [ppc64el] (focal-proposed/universe) [0.4.0-1] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: flatbuffers [arm64] (focal-proposed/universe) [1.11.0+dfsg1-1.1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: light [arm64] (focal-proposed/universe) [1.2.1-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: flatbuffers [armhf] (focal-proposed/universe) [1.11.0+dfsg1-1.1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: lablgtk-extras [armhf] (focal-proposed/universe) [1.6-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: lablgtk-extras [arm64] (focal-proposed/universe) [1.6-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: light [armhf] (focal-proposed/universe) [1.2.1-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: prometheus-hacluster-exporter [arm64] (focal-proposed/universe) [0.4.0-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: prometheus-hacluster-exporter [armhf] (focal-proposed/universe) [0.4.0-1] (no packageset)
[17:58] -queuebot:#ubuntu-release- New binary: camitk [amd64] (focal-proposed/universe) [4.1.2-4] (no packageset)
[18:08] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (bionic-proposed) [20101020ubuntu543.15]
[18:48] <Eickmeyer[m]> doko: Can you explain to me why Ardour, a key application for Ubuntu Studio, wasn't on the list of those applications affected by the removal of Python 2 and why I'm now having to SCRAMBLE to get its build system (waf) to build with Python 3?
[18:48]  * Eickmeyer[m] is extremely unhappy
[18:50] <Eickmeyer[m]> If it were on that list, I would have raised an objection to the Python2 removal, but now it's too late, and our key Digital Audio Workstation is in jeopardy. To say I'm livid is an understatement.
[18:54] <doko> Eickmeyer[m]: removed in testing on 2020-01-11. and then in focal. If you want to have it back without porting, make it working with the python2 packages, not the unversioned python packages
[18:54] -queuebot:#ubuntu-release- Unapproved: flash-kernel (bionic-proposed/main) [3.90ubuntu<IP_ADDRESS> => 3.98ubuntu<IP_ADDRESS>] (core)
[18:58] <Eickmeyer[m]> doko: The attitude is that Ubuntu Studio isn't important to this release team. Would you like the project shuttered? Because I don't have the know-how to do that (I've been porting with help of the Ardour team for over 24 hours now), and everyone on my team has lives outside of Ubuntu. Having 20.04 LTS without Ardour would be a disaster.
[19:00] <doko> Eickmeyer[m]: it's not release time yet.
[19:00] <Eickmeyer[m]> Every time I come in here, and ask for a review of a new package, I'm met with silence. Only when I raise a ruckus like this does anything happen.
[19:01] <doko> Eickmeyer[m]: this is a different story, and maybe you should raise this issue on the ML or the tech-board
[19:01] <Eickmeyer[m]> doko: Agreed, but Feature Freeze is just over a month away, and Ardour, at this point, will be sourceNEW. Last time I submitted something sourceNEW, it took over a month for a review. I can't wait that long for this package, and I'm not even close to fixing it yet.
[19:01] <doko> I'm fine to help restoring it
[19:02] <doko> even after feature freeze
[19:03] <Eickmeyer[m]> Ok then. And by the way, I realize it was removed on 1-11, but it wasn't on the initial list to be removed. I had zero advance notice. That's why this is frustrating as I would have had more time.
[19:04] <Eickmeyer[m]> doko: Would you mind meeting in #ubuntustudio-devel about this to keep it off the release team?
[19:05] <doko> Eickmeyer[m]: sure, but please not today. can we do that net week?
[19:05] <doko> next even
[19:05] <Eickmeyer[m]> doko: Sure. I'm ok with that as long as we can get this done.
[19:05] <doko> ok
[19:17] -queuebot:#ubuntu-release- New: accepted camitk [amd64] (focal-proposed) [4.1.2-4]
[19:17] -queuebot:#ubuntu-release- New: accepted flatbuffers [arm64] (focal-proposed) [1.11.0+dfsg1-1.1]
[19:17] -queuebot:#ubuntu-release- New: accepted lablgtk-extras [amd64] (focal-proposed) [1.6-1]
[19:17] -queuebot:#ubuntu-release- New: accepted lablgtk-extras [armhf] (focal-proposed) [1.6-1]
[19:17] -queuebot:#ubuntu-release- New: accepted lablgtk-extras [s390x] (focal-proposed) [1.6-1]
[19:17] -queuebot:#ubuntu-release- New: accepted light [arm64] (focal-proposed) [1.2.1-1]
[19:17] -queuebot:#ubuntu-release- New: accepted light [ppc64el] (focal-proposed) [1.2.1-1]
[19:17] -queuebot:#ubuntu-release- New: accepted prometheus-hacluster-exporter [arm64] (focal-proposed) [0.4.0-1]
[19:17] -queuebot:#ubuntu-release- New: accepted flatbuffers [amd64] (focal-proposed) [1.11.0+dfsg1-1.1]
[19:17] -queuebot:#ubuntu-release- New: accepted lablgtk-extras [arm64] (focal-proposed) [1.6-1]
[19:17] -queuebot:#ubuntu-release- New: accepted light [amd64] (focal-proposed) [1.2.1-1]
[19:17] -queuebot:#ubuntu-release- New: accepted light [s390x] (focal-proposed) [1.2.1-1]
[19:17] -queuebot:#ubuntu-release- New: accepted flatbuffers [armhf] (focal-proposed) [1.11.0+dfsg1-1.1]
[19:17] -queuebot:#ubuntu-release- New: accepted light [armhf] (focal-proposed) [1.2.1-1]
[19:17] -queuebot:#ubuntu-release- New: accepted lablgtk-extras [ppc64el] (focal-proposed) [1.6-1]
[19:17] -queuebot:#ubuntu-release- New: accepted prometheus-hacluster-exporter [armhf] (focal-proposed) [0.4.0-1]
[19:17] -queuebot:#ubuntu-release- New: accepted prometheus-hacluster-exporter [amd64] (focal-proposed) [0.4.0-1]
[19:17] -queuebot:#ubuntu-release- New: accepted prometheus-hacluster-exporter [s390x] (focal-proposed) [0.4.0-1]
[19:17] -queuebot:#ubuntu-release- New: accepted prometheus-hacluster-exporter [ppc64el] (focal-proposed) [0.4.0-1]
[20:33] -queuebot:#ubuntu-release- New binary: libnfs [amd64] (focal-proposed/main) [4.0.0-1] (i386-whitelist, ubuntu-desktop)
[20:34] -queuebot:#ubuntu-release- New binary: libnfs [i386] (focal-proposed/main) [4.0.0-1] (i386-whitelist, ubuntu-desktop)
[22:20] -queuebot:#ubuntu-release- New binary: libnfs [arm64] (focal-proposed/main) [4.0.0-1] (i386-whitelist, ubuntu-desktop)
[22:21] -queuebot:#ubuntu-release- New binary: libnfs [armhf] (focal-proposed/main) [4.0.0-1] (i386-whitelist, ubuntu-desktop)
[22:25] -queuebot:#ubuntu-release- New binary: libnfs [ppc64el] (focal-proposed/main) [4.0.0-1] (i386-whitelist, ubuntu-desktop)
[22:26] -queuebot:#ubuntu-release- New: accepted libnfs [amd64] (focal-proposed) [4.0.0-1]
[22:26] -queuebot:#ubuntu-release- New: accepted libnfs [armhf] (focal-proposed) [4.0.0-1]
[22:26] -queuebot:#ubuntu-release- New: accepted libnfs [ppc64el] (focal-proposed) [4.0.0-1]
[22:26] -queuebot:#ubuntu-release- New: accepted libnfs [arm64] (focal-proposed) [4.0.0-1]
[22:26] -queuebot:#ubuntu-release- New: accepted libnfs [i386] (focal-proposed) [4.0.0-1]
[22:28] -queuebot:#ubuntu-release- New binary: libnfs [s390x] (focal-proposed/main) [4.0.0-1] (i386-whitelist, ubuntu-desktop)
[22:31] -queuebot:#ubuntu-release- New: accepted libnfs [s390x] (focal-proposed) [4.0.0-1]
[23:17] -queuebot:#ubuntu-release- New binary: fonts-le-murmure [amd64] (focal-proposed/none) [0.2-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: golang-github-powerman-check [amd64] (focal-proposed/none) [1.2.1-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: wob [amd64] (focal-proposed/none) [0.6-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: golang-github-mattn-go-ieproxy [amd64] (focal-proposed/none) [0.0~git20191113.7c0f686-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: pacvim [amd64] (focal-proposed/none) [1.1.1-1~exp1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: boxfort [amd64] (focal-proposed/none) [0.0.0-git20200105-3e16c0a-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: golang-github-youmark-pkcs8 [amd64] (focal-proposed/none) [1.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: node-jquery-textcomplete [amd64] (focal-proposed/none) [1.7.3+dfsg-2] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: pacvim [ppc64el] (focal-proposed/none) [1.1.1-1~exp1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: comskip [amd64] (focal-proposed/none) [0.82.009+ds.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: ocaml-astring [amd64] (focal-proposed/none) [0.8.3-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: mopidy-gmusic [amd64] (focal-proposed/none) [4.0.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: thesias [amd64] (focal-proposed/none) [3.1.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: comskip [s390x] (focal-proposed/none) [0.82.009+ds.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: ocaml-astring [ppc64el] (focal-proposed/none) [0.8.3-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: antlr4-cpp-runtime [amd64] (focal-proposed/universe) [4.8+dfsg-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: dark-gtk-themes [amd64] (focal-proposed/universe) [0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: wob [ppc64el] (focal-proposed/universe) [0.6-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: comskip [ppc64el] (focal-proposed/universe) [0.82.009+ds.1-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: thesias [ppc64el] (focal-proposed/universe) [3.1.1-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: mecab [amd64] (focal-proposed/main) [0.996-7] (i386-whitelist, ubuntu-server)
[23:20] -queuebot:#ubuntu-release- New binary: nng [amd64] (focal-proposed/universe) [1.2.3-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: comskip [arm64] (focal-proposed/universe) [0.82.009+ds.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: nng [ppc64el] (focal-proposed/universe) [1.2.3-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: comskip [armhf] (focal-proposed/universe) [0.82.009+ds.1-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: fonts-solide-mirage [amd64] (focal-proposed/universe) [0.2-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: ocaml-astring [armhf] (focal-proposed/universe) [0.8.3-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: pacvim [s390x] (focal-proposed/universe) [1.1.1-1~exp1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: ocaml-astring [arm64] (focal-proposed/universe) [0.8.3-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: thesias [s390x] (focal-proposed/universe) [3.1.1-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: ocaml-astring [s390x] (focal-proposed/universe) [0.8.3-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: wob [s390x] (focal-proposed/universe) [0.6-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: nng [s390x] (focal-proposed/universe) [1.2.3-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: pacvim [arm64] (focal-proposed/universe) [1.1.1-1~exp1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: pacvim [armhf] (focal-proposed/universe) [1.1.1-1~exp1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: plastimatch [amd64] (focal-proposed/universe) [1.8.0+dfsg.1-2] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: wob [arm64] (focal-proposed/universe) [0.6-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: nng [arm64] (focal-proposed/universe) [1.2.3-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: thesias [arm64] (focal-proposed/universe) [3.1.1-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: nng [armhf] (focal-proposed/universe) [1.2.3-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: wob [armhf] (focal-proposed/universe) [0.6-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: thesias [armhf] (focal-proposed/universe) [3.1.1-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (bionic-proposed) [3.98ubuntu<IP_ADDRESS>]


[01:29] <ayush> hello
[01:34] <ayush> ...
[03:57] <Tyr> hello
[06:30] <abimael> HOLA
[12:31] <red_1990> Hello
[12:35] <michel> how can i activate the numbers block on my acer aspire 7750 laptop
[12:39] <jc> bonjour tout le monde, hi everybody
[12:39] <jc> i have a little problem with ubuntu mate 16.04
[12:40] <jc> the problem is when i close the computer with /usr/lib/at-spi2-core/at-spi2-registryd
[12:40] <jc> how can i disable that ?
[12:57] <alkisg> michel: are you asking how to activate numlock?
[12:57] <alkisg> There should be an Fn key in your laptop
[12:58] <alkisg> Fn + someother key will activate numlock
[12:58] <alkisg> Usually they are marked with blue color, the other keys that function with Fn
[13:03] <alexs> hola q tal
[13:03] <alexs> hello
[13:06] <michel> Yes ,it is an azerty
[13:08] <michel> the fn function is responding all the way
[13:10] <michel> it does not work
[13:10] <michel> the fn function is not working
[13:27] <alkisg> michel: read your laptop manual about the fn key, it's not related to ubuntu
[13:27] <alkisg> You just need to learn how it works
[13:33] <michel> i used to use the fn key all the time for volume and brightnes settings but with mate it does not work any more
[13:35] <michel> in ubuntu i fixed it with unity-tweek tool -keybord- optios -set number block - ok -and it worked
[13:37] <michel>  so i downloaded the unity tweek -tool but i cant find it anywhere
[13:37] <alkisg> the fn/numlock key are not related  to the os
[13:37] <alkisg> You can set numlock on with numlockx tool too
[13:37] <alkisg> But the normal way is to just press fn + numlock on the laptop
[13:38] <alkisg> It works in any os, linux, windows, dos, bios...
[13:38] <alkisg> Just read the laptop manual
[13:39] <michel> fn  key works but not like it has can only put volume and brightness up but not down again
[13:42] <michel> i am serching for solusion for days now , dont now it anymore
[13:43] <michel> sorry for the english but my languages is dutch
[15:25] <nikunj_> Where will i find the devices menu in Mate, cause i need to select the 'Install Guest Additions' option from there
[15:25] <nikunj_> ??
[15:28] <masnell_> nikunj_: are you running Ubuntu MATE in a VM? if so, the option is on the VM window to load, not inside the VM environment
[15:35] <nikunj_> Oh is it
[15:35] <nikunj_> let me check
[15:35] <nikunj_> sorry i was busy
[15:37] <nikunj_> Getting this error
[15:37] <nikunj_> Unable to install virtual optical disk
[15:39] <masnell_> When you set up the VM, did you leave the default on for a Optical drive to exist? if not, you probably have to shut down the VM, edit the VM system configuration to include one, then reboot and retry
[15:40] <masnell_> reboot the VM (not your system)
[15:42] <nikunj_> eDIT IT FROM THE BASE OS?
[15:44] <masnell_> yes, when you select the VM image, you should have an option to edit the VM system configuration eg, RAM, CPUs, etc, one option will be a Optical/CD/DVD or BluRay drive
[15:45] <masnell_> .. and they are gone...
[15:57] <dylan_> HI
[19:23] <peteyy> hey, I've just read that ubuntu mate doesn't have a compositor, what are compositors are exactly for? I know they provide functionallity like, window transparency, but other than that what am I missing out on? :)
[19:36] <peteyy> Is there anyone around? :|
[20:30] <sixwheeledbeast> as in window manager compositor?
[20:30] <peteyy> yes
[20:32] <sixwheeledbeast> It's mainly used for effects and transitions upon window selection. There are options for compositors for Ubuntu-MATE, Marco Compiz etc.
[20:34] <peteyy> So they are optional but can be enabled right? :)
[20:35] <sixwheeledbeast> In MATE Tweak there are options to enable CPU or GPU Marco and Compiz. I prefer without myself.
[20:38] <peteyy_> I managed to crash it :D maybe I should also stick with the default settings
[20:39] <alkisg> The default is to have composition
[20:39] <alkisg> (in ubuntu; while in debian mate it's not)
[21:37] <Altom> Hello, I installed canon capt driver 2.70 (latest) for my printer and got it working. But on shutdown the daemon hangs and there is a 5 minutes delay before it gets killed
[21:38] <Altom> I tried to look up the config files, but I couldn't find anything to reduce this delay to 5 seconds
[21:40] <Altom> Can anyone helps me either reduce the delay to 5 seconds or  investigate the origin of the problem ?
[21:45] <sixwheeledbeast> where did the driver come from?
[21:46] <Altom> Canon website
[21:46] <Altom> It's 2 debs
[21:46] <Altom> It's working very well beside this problem
[21:46] <neals> hey, i have ubuntu MATE and recently notifications are not running and when i try to listen to some audio . it doesn't work neither.
[21:47] <neals> apps that works as tray icons no longer opens up.
[21:47] <neals> or rather not showing up
[21:48] <neals> anybody knows how i can fix this issue?
[21:49] <sixwheeledbeast> Never used Canon printer, can you pull any information from your logs about the hang on shutdown?
[21:50] <sixwheeledbeast> I know I had fun installing some Epson drivers in the past had to install debs with --force-arch IIRC.
[21:52] <sixwheeledbeast> Have you checked the settings for your notifications?


[06:47] <Jentsch> Hi everyone,
[06:48] <Jentsch> I have found a bug within the configuration of phppgadmin package, could some one point me to place where to report it?
[06:48] <Jentsch> sry, but new to the contibution stuff
[06:49] <Jentsch> It should be very easy to fix, just a file needs to be moved
[06:54] <brendand> Jentsch, looks like they are on sourceforge: http://phppgadmin.sourceforge.net/doku.php
[06:55] <Jentsch> brendand, thank
[06:57] <Jentsch> brendand, but the bug depends on the apache2 configuration so may it isn't charge of the phppgadmin team.
[06:57] <Jentsch> sry, I'm just not shure
[06:58] <brendand> Jentsch, maybe just report i on apache2 in ubuntu and someone might pick it up
[06:59] <brendand> ubuntu-bug apache2
[07:03] <Jentsch> brendand, thanks again. I will do that
[14:57] <ianward> Hello, I see debian jessie/sid have eglibc 2.19.1.  14.04 LTS has 2.19.0.  Does anyone know when 14.04 updates will have 2.19.1?  I can see on https://launchpad.net/ubuntu/trusty 2.19.1 is listed as a "packages with differences".  I don't understand when the updated packages from Debian get rectified and make it into trusty updates, and whether there's anything I can do to help with this.
[15:06] <rbasak> ianward: this isn't really the right channel, but unless there are specific high impact bugs to fix a eglibc update is unlikely - we have new releases for that kind of thing. See https://wiki.ubuntu.com/StableReleaseUpdates for policy and rationale.
[15:10] <ianward> rbasak: thanks. do you know what channel i should use?  This is the upstream bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722075
[15:12] <rbasak> ianward: ah, great - you have a specific bug. Try #ubuntu-devel - eglibc being a bit special I'm not really sure about it.
[15:13] <ianward> rbasak: ok thanks
[15:13] <rbasak> ianward: also, if there isn't a Launchpad bug, you should create one and link the Debian bug. Then we can track progress of the issue in Ubuntu - which is clearly a valid issue if Debian have acknowleged it.
[15:14] <ianward> rbasak: ok great i'll check
[15:15] <jtaylor> the trusty package does have a few backports
[15:15] <jtaylor> e.g. the math issues are fixed
[15:16] <rbasak> It looks like bugfixes have been backported in previous releases, too - so this one could well be a candidate for that.


[03:42] <Loeb> How exactly does cloud-init determine where the cloud config file is read from?
[03:45] <blackboxsw> Loeb: it depends on the datasource detected where the cloud-config sources are. `cloud-init status --long` will show you what your datasource is and may show you where the seed files for user-data is read for that datasource. `sudo cloud-init query userdata` will tell you what userdata values were read.
[03:45] <blackboxsw> ... some datasources support multiple locations for cloud-config userdata.
[03:46] <blackboxsw> your datasource docs might describe those locations https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
[03:48] <Loeb> ok so, in this case I'm PXE booting and appending what I believe to be the location info in the pxelinux config. "ds=nocloud-net;s=<URL>" I believe is what is supposed to determine the location
[03:48] <Loeb> but digging through the logs it only appears to look for the "meta-data" file there, which (I think) isn't relevant in my case?
[03:49] <Loeb> That's the only thing I see it failing to read, anyhow. I also saw it didn't see a leading "#cloud-config" line at the URL pointing towards the ISO.
[03:53] <Loeb> and what I'm seeing for the nocloud config is WAY different from the config file/examples I was seeing
[03:54] <Loeb> I've been trying to set up a bare metal unattended install. From what I've seen it appears that the way to do this on ubuntu nowadays is cloud-init???
[03:55] <Loeb> I've seen documentation for anaconda, debian-installer, and now cloud-init. I could be wrong on this but the docs are a bit of a mess.
[03:55] <Loeb> The docs for the ubuntu unattended install, that is.
[04:32] <Loeb> blackboxsw, for funsies I named my config yaml file "meta-data" and touched "user-data" and "vendor-data" to see what the installer did... and I don't see any explicit errors in /var/log/cloud-init.log ? Not sure what' it's doing at this point, it drops me into the interactive ubuntu gui installer each time.
[04:33] <Loeb> I do see it grabbing the files from the network and reading them in
[09:13] <Loeb> I did have the right config, but the info needed to reside in "user-data" not "meta-data". I still find the documentation for this a bit lacking, along with cloud-init not spitting out particularly useful error messages when it say, reads an empty config file like this and defaults to something else.
[09:14] <Loeb> Regardless, it does appear to be functional now.  It's problematic.
[13:49] <krysenn> Hi,
[13:49] <krysenn> I'm new with cloud-init, and i'm trying to configure an ssh key on my instance through meta-data with a NoCloud datasource, but it not works.
[13:49] <krysenn> Anybody can help me ? Thanks :)
[15:08] <meena> uh… i was gonna say they're too impatient for quitting before getting an answer, but it's been over an hour
[15:14] <Odd_Bloke> Maybe they fixed it. :p
[15:19] <testcla234> is possible to achieve this :
[15:19] <testcla234> curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add -
[15:19] <testcla234> with <sources:?
[15:19] <testcla234> * with <sources:>
[15:35] <Odd_Bloke> testcla234: I don't believe so, no, unfortunately.  I think your best bet is probably to fetch the key and include it as `key` in the appropriate `sources` section.  Looks like the keys get cycled every 2/3 years, so that's not totally impossible to manage.  Not ideal, certainly!
[15:36] <testcla234> on ubuntu the 2 keys need to be store in here
[15:36] <testcla234> ls -al /usr/share/keyrings/cloud.google.gpg
[15:36] <testcla234> -rw-r--r-- 1 root root 2054 Feb 26 15:16 /usr/share/keyrings/cloud.google.gpg
[15:36] <testcla234> otherwise failed on apt update
[15:37] <testcla234> I just avoid using <source:> and use runcmd
[15:37] <Odd_Bloke> That's not the correct path for user-installed keys, /etc/apt/trusted.gpg.d/ is preferred.
[15:38] <Odd_Bloke> `runcmd` will work fine, but the key won't be in place in time for cloud-init's apt installation, I believe.
[15:38] <Odd_Bloke> If you aren't using that, not a problem, ofc.
[15:40] <testcla234> unfortunately that is the path using by google - https://cloud.google.com/sdk/docs/quickstart#installing_the_latest_version
[15:41] <testcla234> on `runcmd` I just use :
[15:41] <testcla234>  echo "deb [signed-by=/usr/share/keyrings/cloud.google.gpg] http://packages.cloud.google.com/apt cloud-sdk main" | tee -a /etc/apt/sources.list.d/google-cloud-sdk.list && curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key --keyring /usr/share/keyrings/cloud.google.gpg  add - && apt-get update -y && apt-get install
[15:41] <testcla234> google-cloud-sdk -y
[15:41] <testcla234> testing now
[15:41] <Odd_Bloke> Yeah, I expect that will work.
[15:42] <Odd_Bloke> Just that's not the preferred path for keyrings that aren't installed by system packages.
[15:42] <Odd_Bloke> (And I don't know if there might be other consequences of putting it there.)
[15:47] <testcla234> is not possible to use LVM on disk_setup , right?
[16:05] <Odd_Bloke> testcla234: Correct.
[16:08] <testcla234> strange this
[16:08] <testcla234> [   35.315499] cloud-init[866]: 2021-02-26 15:54:19,903 - __init__.py[WARNING]: Unable to add group member 'user1' to group 'docker'; user does not exist.
[16:08] <testcla234> grep -i user1 /etc/passwd
[16:08] <testcla234> user1:x:1000:1001:Ubuntu:/home/user1:/bin/bash
[16:10] <testcla234> ignore this on azure the user1 seems to create after cloud-init
[16:10] <Odd_Bloke> cloud-init creates groups before it creates users (so that user definitions can refer to those groups); doing, roughly, `groups: [docker]` and `users: [{..., "groups": ["docker"]}, ...]` should work.
[16:11] <Odd_Bloke> But yeah, if that's not created by cloud-init then bets are off. :)


[09:17] <kevko> Hello folks, please could someone advice me how to fix my cloudinit setup ? Point is that I have several interfaces and I want to have control in networking ..so I have own python script which generate netplan and set udev rules (names of interface) ...but cloudinit somehow set ip addresses of interfaces and moreover set default gateways several times for several interfaces and some interfaces don't have connectivity outside ..so cloudinit will fail
[09:17] <kevko> because of resolve problems and apt problems...
[09:19] <kevko> now I am using heat + heat software deployment in openstack ... first I am waiting for cloudinit is done and then I run networkconfigurator to setup network and apply netplan ... it worked by accident almost always ..because order of interfaces was resolved in corrrect way ..but now the order was different ..so i am tryig to find a way how to configure network before cloudinit will do things which neeed to be connected to internet ...apt ..etc
[10:23] <aciba> kevko: Hello. I think the following might work. Disabling cloud-init network configuration: https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/network-config.html#cloud-config
[10:23] <aciba> and running your net config script in https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/modules.html#bootcmd
[10:26] <aciba> kevko: could you try something in the lines of: https://pastebin.ubuntu.com/p/KD95yscZ5G/ ?
[10:33] <kevko> aciba: yeah, this is scenario i was thinking about that should work .... googled 5 minutes ago :P
[15:10] <holmanb> SuperLag: getting back to this now
[15:29] <holmanb> SuperLag: it looks like you have invalid yaml
[15:29] <holmanb> SuperLag: see https://dpaste.org/FkSKX
[16:08] <SuperLag> I just now got the chance to try, and that did the trick. 🙌🏻
[16:08] <SuperLag> and here I thought that yaml syntax was correct.
[16:12] <SuperLag> holmanb: is there a way with using cloud images to set it up for resizing? 10GB usually isn't enough. :D
[16:23] <meena> SuperLag: https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/modules.html#growpart & https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/modules.html#resizefs
[16:25] <meena> what is cloud-initramfs-tools?
[16:26] <meena> https://launchpad.net/cloud-initramfs-tools
[17:21] <minimal> meena: Ubuntu-specific tool for adding stuff to the initramfs for things like growing partition - nothing to do with cloud-init AFAIK
[17:35] <meena> minimal: funnily enough, OpenBSD and NetBSD would need that too, cuz their growfs doesn't work online
[17:37] <minimal> meena: it is doing *partition* growing, don't think it also does fs growing
[17:40] <minimal> from a quick glance its "growroot" is basically just calling "growpart"
[17:48] <meena> minimal: i do wonder what the point of that is
[18:01] <minimal> to grow partition in an initramfs? ;-) Anyway it is unconnected to cloud-init beyond the fact that they both use growpart from cloud-utils
[21:47] <noahm> Hi folks. I'm not sure when it happened, but the migration of the docs from cloudinit.readthedocs.io to canonical-cloud-init.readthedocs-hosted.com has dropped all documentation for older releases.  With many distros continuing to ship older releases, losing the version specific documentation is problematic.
[21:47] <noahm> I didn't see a bug report for this on launchpad, but figured I'd check here first before opening one.
[22:43] <SuperLag> holmanb: thank you, thank you, thank you!!
[22:44] <SuperLag> holmanb: in that paste, line 19... does that already come with the cloud-init bits?
[22:45] <SuperLag> holmanb: if not, can you tell me what I need to get the tools to do that test on my own?


[00:13] <guiverc> and thanks krytarik (membership board post & missing italics)...    I corrected it this morning
[10:16] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Accelerate IT/OT convergence in Industry 4.0 [Part II] @ https://ubuntu.com//blog/industry-4-part-ii
[15:57] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: A New ‘KDE Control Centre’ Widget Inspired by iOS @ https://www.omgubuntu.co.uk/2022/10/kde-control-center-widget-macos-inspired (by Joey Sneddon)
[17:17] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Humans may be rational, or how to collect better documentation feedback with linguistic... @ https://ubuntu.com//blog/humans-may-be-rational-or-how-to-collect-better-documentation-feedback-with-linguistic-theory


[22:59] <tsimonq2> wxl: Just so it can be made aware, there is a membership pending for the lubuntu-qa Launchpad team
[23:08] <krytarik> wxl: Please have a look back at the logs of this channel from 15 - 17th Aug, reg. my MP as well as several bug reports that need their status changed (since fixed), and a possible further MP from me to fix one more.
[23:10] <krytarik> ( http://irclogs.ubuntu.com/2015/08/15/%23lubuntu-devel.html , http://irclogs.ubuntu.com/2015/08/16/%23lubuntu-devel.html , http://irclogs.ubuntu.com/2015/08/17/%23lubuntu-devel.html )
[23:23] <wxl> krytarik: could you email me a concise summary of what needs to happen?
[23:26] <krytarik> wxl: Hey, that's even colored! :P (and not too much anyway)
[23:26] <wxl> tl;dr krytarik :/
[23:28] <krytarik> Generally, I'd already be happy with merging  https://code.launchpad.net/~krytarik/lubuntu-default-settings/bug-1266138/+merge/268162  for now. :P
[23:28] <krytarik> The other stuff is just bug report cleanup really.
[23:29] <wxl> sadly i can't do much more than say "looks good"
[23:29] <wxl> you'll have to talk to the boss about htat :)
[23:33] <krytarik> wxl: Technically, you could; socially, maybe not. :)


[04:41] <ZachGibbens> JackFrost see if they'll take you to the original one in Chattanooga (or current HQ in Atlanta)