[10:20]  * cjwatson accidentally adds images to the tracker with bogus dates, and fixes
[10:21] <cjwatson> (Ubuntu precise alternate/desktop/server, if anyone's keeping track)
[10:57] <seb128> can a python LGPL 3+ source import a LGPL2.1 .py or is that buggy?
[11:02] <xnox> seb128: i think that's fine. one cannot copy it into their source tree and modify lgpl2.1 only and redistribute the whole thing under lgpl3 though ( i think that's the restriction)
[11:03] <xnox> i.e. patches to lgpl2.1 .py should be licensed under lgpl2.1.
[11:03] <seb128> xnox, can they copy it in the source, not modify it, and ship the source as LGPL3 ?
[11:03] <xnox> seb128: yes, if they do not modify it.
[11:04] <xnox> seb128: in debian/copyright, I'd suggest to spell out that file as lgpl2.1
[11:04] <seb128> hum
[11:04] <seb128> they did modify it
[11:05] <seb128> they imported in source to port in to python3, the time upstream would review/include their patch
[11:05] <seb128> so I guess that doesn't work?
[11:05] <xnox> seb128: then those patches to that file only, should be licensed under 2.1 or (dual-license under 2.1 and 3)
[11:06] <xnox> seb128: it's all fine, as long as 2.1 is still granted on those patches. One can link lgpl2.1, lgpl3 and gpl3 code together.
[11:07] <seb128> xnox, how does that work, if you have sources that are lgpl2.1 (only, not "+") and lgpl3 ... what's the license of the binary?
[11:07] <xnox> the combined work will get the combined licensed in that order.
[11:08] <xnox> seb128: just lgpl2.1 by itself -> binary lgpl2.1, lgpl2.1 + 3 -> lgpl3, lgpl2.1 + 3 + gpl3 -> gpl3
[11:09] <xnox> it's only gpl2-only which is incompatible with gpl3, lgpl2.1-only on the other hand is compatible.
[11:10]  * seb128 opens http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility and look at it again
[11:10] <seb128> xnox, thanks ;-)
[11:11] <seb128> xnox, the tab says to transfert the code to GPLv3 in that case?
[11:11] <xnox> seb128: https://www.gnu.org/licenses/quick-guide-gplv3.html
[11:11] <xnox> is better.
[11:12] <xnox> seb128: sure FSF is pushing everyone to v3 =)
[11:14] <xnox> seb128: it would be easier if it was not modified.....
[11:15] <seb128> xnox, right, well I'm reviewing ibus-cangjie in the sponsoring queue
[11:15] <seb128> their source is LGPL3
[11:15] <seb128> and they need python-canberra which is LGPL2.1
[11:15] <seb128> or that one is not available for python3
[11:15] <seb128> so they did copy it in source and ported it to python3
[11:16] <xnox> thus clearly the only way they could have modified it, under lgpl2.1. Did they change the license headers?
[11:17] <seb128> no they didn't
[11:17] <seb128> xnox, but http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility says you can't ship LGPL2.1 code under LGPL3
[11:17] <xnox> seb128: hence they are all golden -  all modifications to lgpl2.1 code are provided back under lgpl2.1
[11:17] <seb128> so the project can't be redistributed this way
[11:17] <seb128> or I read that wrong...
[11:20] <xnox> seb128: sure but we are not releasing the project under LGPLv3, we are releasing it under mixed lgpl2.1 & 3 (e.g. linking only). The 2.1 bits are staying 2.1 bits, and just like before one is allowed to link against lgpl2.1 in lgpl3 one continious to do so.
[11:21] <seb128> xnox, well, both got mixed in one process no? and the COPYING in that source says LGPL3
[11:21] <xnox> seb128: plus a third-party cannot relicense code to a different. Look at that table the lower part "I want to use a library under LGPLv2.1 only" and it's OK across the board.
[11:21] <seb128> xnox, ok with quite some cases where it says "you need to transfert the code to GPLv3"
[11:21] <xnox> it doesn't matter if I use original lgpl2.1 library, or lgpl2.1 library with lgpl2.1 licensed patches library (they are the same).
[11:22] <xnox> seb128: i'd be using the 'i want to use a library under"
[11:23] <xnox> seb128: as they kept the library separate.
[11:23] <xnox> seb128: that one does not have any convey for lgplv2.1
[11:23] <seb128> ah, right
[11:24] <xnox> seb128: take their patches & sponsor into our canberra package, unapply patches from their packages and upload \o/
[11:24] <seb128> I was considering the python import of a copy as a code change
[11:24] <seb128> ;-)
[11:24] <seb128> that's an idea
[11:24] <seb128> or just push the canberra guys to just take that patch and release and updated version
[11:25] <xnox> seb128: python import is mostly equivalent of shared library linking, it's not for example static library or C++ template....
[11:25] <seb128> except that's a modified copy in source
[11:25] <seb128> so it's a bit the equivalent of copying the source of a shared lib, copying it inline, changing it, and linking against it for building your binary
[11:26] <seb128> that's not really "using a library" at this point, it's "using the code of a library for your private benefit"
[11:26] <xnox>  \o/ /o\
[11:26] <seb128> anyway, I will wave hands and sponsor and see what the archive admin of the day think of the situation ;-)
[11:27] <seb128> xnox, thanks for the discussion
[12:30] <ScottK> seb128: re your comments in https://bugs.launchpad.net/ubuntu/+bug/1055435/comments/22 - I think it's fair to say that if the licensing is clear and it's in common licenses, a missing license is not a reason to reject a package, but I also think it's still a bug that should be fixed.  When was the discussion you refer to because I don't see it in my backscroll?
[12:30] <ubot2> Launchpad bug 1055435 in ubuntu "[FFe][needs-packaging] new package classicmenu-indicator" [Wishlist,Fix committed]
[12:31] <seb128> ScottK, on this channel, around 11am UTC between xnox and me
[12:31] <seb128> oh, sorry
[12:31] <seb128> I'm mixing bugs
[12:31] <ScottK> OK.  Would you please comment again in that one.
[12:33] <seb128> ScottK, sure
[12:33] <seb128> ScottK, http://irclogs.ubuntu.com/2013/01/30/%23ubuntu-release.html#t12:29
[12:33] <seb128> was the discussion
[12:33] <seb128> some "recent" might not be that recent :p
[12:34] <ScottK> Right.
[12:34] <ScottK> "Of course, it might still be a good idea to contact upstream and get them to spell out the licensing more clearly in their tarball - I just don't think it's cause for rejection"
[12:34] <ScottK> That aligns with my thinking on the matter.
[12:35] <ScottK>  !rejected != bug free
[12:35] <ubot2> ScottK: I am only a bot, please don't think I'm intelligent :)
[12:35] <ScottK> Sigh.
[12:35] <seb128> ScottK, sorry, what do you want me to add to the bug? I said that it's not a blocker and that they can upload and that it would still be good to have the issue fixed with the next upload
[12:36] <ScottK> seb128: Your last comment says, in part, "the full license doesn't need to be included in the tarball as long as the intend is clear".
[12:36] <seb128> well, I added "even if it would be good to have in a next update"
[12:36] <seb128> but I can change that to a "please get it fixed for the next update"
[12:37] <ScottK> I think that would be clearer.
[12:37] <seb128> ScottK, https://bugs.launchpad.net/ubuntu/+bug/1055435/
[12:37] <ubot2> Launchpad bug 1055435 in ubuntu "[FFe][needs-packaging] new package classicmenu-indicator" [Wishlist,Fix committed]
[12:37] <seb128> comment #23
[12:37] <seb128> works for you?
[12:38] <ScottK> seb128: perfect.  Thanks.
[12:38] <seb128> yw, thanks for pointing it out ;-)
[12:38] <ScottK> no problem.
[13:07] <cjwatson> infinity: Didn't our buildd chroot configuration use to preseed man-db/auto-update to false in the debconf database, to stop man-db bothering to update its database during builds?
[13:07] <cjwatson> infinity: I certainly put that in there for the benefit of buildds
[13:15]  * xnox ponders if mk-sbuild does that as well?!
[13:21] <plars> cjwatson: psivaa just pointed out to me that the precise jobs are failing because report.html is just in pending, not in current
[13:21] <plars> cjwatson: is it intentional that those are not copied over to current?
[13:22] <plars> I thought it was just going to be a link actually
[13:22] <plars> for example: http://cdimage.ubuntu.com/ubuntu-server/precise/daily/
[13:28] <cjwatson> plars: not entirely intentional, but I'm going to have to regenerate those files - it can't be a simple copy/link because the set of architectures involved isn't necessarily the same
[13:29] <cjwatson> plars: however, you could avoid the job failure by switching the jobs over to look at pending rather than current
[13:29] <cjwatson> plars: which AIUI is the intention anyway
[13:29] <plars> cjwatson: yes, indeed
[14:17] <jamespage> Daviey, ^^ those are the correct new versions for openstack updates; I notice other versions of keystone, nova and cinder in the queue from +1 month ago - those can be rejected please.
[14:18] <jamespage> Daviey, there is also a quantum fix that could also do with accepting if possible
[14:41] <infinity> cjwatson: Probably not.  Happy to twiddle that when I refresh the chroots.
[15:34] <bdrung> hi, what do you think about bug #1158845?
[15:34] <ubot2> Launchpad bug 1158845 in Ubuntu "[FFe] Pseudo sync nemo 1.7.2-1 from Debian unstable (in NEW queue)" [Undecided,New] https://launchpad.net/bugs/1158845
[17:18] <cjwatson> Laney: I'm working on haskell-cryptohash/powerpc - making progress, slightly to my surprise
[17:23] <infinity> Oh hey, look at that, someone's logged into my machine.
[17:24] <xnox> oh, is that how colin gets powerpc hw ? =)
[17:24]  * xnox kept on imagining that there is a garage on greenend in cambridge full of machines of all architectures ever made.
[17:25] <Daviey> jamespage: I think it will have to wait until Monday now.  Don't really want to do anything taxing right now :)
[17:25] <cjwatson> fixed sha3; working on skein256
[17:25] <jamespage> Daviey, thats fine
[17:25] <jamespage> (thought that might be the case)
[17:29] <infinity> xnox: Yeah, he's actually using two of my PPC machines right now...
[17:58] <cjwatson> Laney: https://github.com/vincenthz/hs-cryptohash/pull/13 - I'm tempted to go ahead and upload that to Ubuntu; what do you think?
[17:58] <cjwatson> obviously aiming to get it into experimental too once it's accepted upstream, but I'd like to get our transition chart cleaner
[18:06] <olli> ScottK, ping
[18:06] <ScottK> olli: Yes?
[18:07] <olli> ScottK, thostr_ and I wanted to discuss FFe https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1154229 with you
[18:07] <ubot2> Launchpad bug 1154229 in unity-scope-gdrive "[FFE] New Unity Dash" [Undecided,Triaged]
[18:08] <olli> there are imho 3 issues that we'd need your opinion on
[18:08] <ScottK> OK.
[18:08]  * olli looks for his notes ;)
[18:09] <olli> didrock's ppa has now the scopes changes as well as the in dash payments changes merged (now: for days)
[18:09] <olli> in dash payments FFe https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1154176
[18:09] <ubot2> Launchpad bug 1154176 in unity "[FFE] Add payment preview for music" [Undecided,Fix committed]
[18:10] <olli> the ppa is building against the raring trunk automatically
[18:10] <olli> and updating itself
[18:10] <olli> we still show a few regressions in the integration suite compared to 12.10 results
[18:10] <olli> which the team is working on
[18:11] <olli> (#1^)
[18:11] <olli> issue #2: due to these failing integration tests we didn't get the packages to the -validated ppa to get more community testing
[18:12] <olli> we had a few brave ppl look at it, but not what we'd expect from a proper testing done by balloons
[18:13] <olli> issue #3: we are feature complete, but the overall bug situation is not satisfying (see https://bugs.launchpad.net/unity/+bugs?field.tag=100scopes)
[18:14] <olli> traditionally, we'd now argue with you to just get it in
[18:14] <olli> and fix bugs later
[18:15] <olli> but we'd like to break with that tradition in favor of the user experience
[18:15] <olli> ScottK, the big question is what options (if any) do you see
[18:16] <olli> thostr_, did I miss anything?
[18:16] <thostr_> olli: no
[18:16] <ScottK> I've expressed my opinion that we're well past feature freeze and things like this should have been landed already.
[18:16] <ScottK> What you're telling me reinforces that opinion.
[18:17] <olli> and there is nothing I can say against that, unfortunately
[18:17] <ScottK> I'm not sure what you mean by breaking that tradition.
[18:18] <olli> I don't want to pull the sabdfl card and just push it in the state it is at right now
[18:18] <olli> for Monday
[18:18] <olli> which was our targeted landing date
[18:18] <ScottK> Then I'd suggest waiting until you think it's mature.
[18:18] <thostr_> ... which means a couple of more days or bugfixing
[18:18] <olli> I think the preferred solution is to figure out a date that works for you to land it in a mature state
[18:18] <ScottK> If Mark says it goes in, it goes in, so make sure you're ready for that to happen.
[18:18] <olli> I am not worried about the Mark side
[18:19] <olli> just trying to work with you guys to resolve this situation in the best way
[18:20] <ScottK> I think anything after the end of next week would be insane.
[18:20] <ScottK> However, Mark routinely approves stuff I think is just crazy.
[18:20] <ScottK> So I don't know what to tell you.
[18:21] <olli> well, ok
[18:22] <olli> we are hitting the Easter Holidays in Europe next week and I believe didrocks is gone (he is on the critical path for us to land it)
[18:23] <cjwatson> Laney: I've just gone ahead.  I think this is a fairly obvious improvement - we should be able to overwrite it with a Debian package soon enough
[18:24] <olli> ScottK, we might have hit didrocks' EOD already
[18:24] <didrocks> not yet, writing an email to sum up today's status :)
[18:24] <olli> ha
[18:24] <ScottK> olli: I don't know what to tell you.  We have feature freeze for a reason and now you're running all over the kinds of problems that happen when it gets ignored.
[18:24] <didrocks> ScottK: the thing is that we have some kind of raring + extension right now
[18:25] <didrocks> which is the ppa
[18:25] <didrocks> so, this is giving us a better feeling of what we are actually experiencing
[18:25] <didrocks> and we rebase everytime we land an unity or any component that we touched in the distro
[18:25] <ScottK> didrocks: I understand.  The 100 scopes/Unity next thing is already approved by Mark.
[18:25] <didrocks> ScottK: I would really prefer that we land with a better quality state than what we had in the past
[18:25] <ScottK> The new payments stuff is not.
[18:26] <didrocks> meaning "shipping something half working"
[18:26] <olli> ScottK, my last concern was that dumping it in on Thu and then have everybody gone over the long weekend might not be preferable
[18:26] <didrocks> and then "upload everydays to fix things"
[18:26] <didrocks> I would rather prefer delaying a little bit and be more proud of the first shot
[18:26] <didrocks> does this make sense ^
[18:26] <didrocks> ScottK: oh right, I've taken great care that we can revert the in dash payments
[18:26] <didrocks> ScottK: no worry on that one :) just acting as Mark asked, to get it testing
[18:26] <ScottK> Sure.
[18:27] <didrocks> it will be reverted whenever we ship the 100scopes if there is no +1
[18:27] <olli> sorry if I was ambigous on that one
[18:27] <olli> good catch didrocks
[18:27] <didrocks> no worry ;)
[18:27] <didrocks> ScottK: so now I think we want to have your tought
[18:27] <didrocks> is it better to ship it on a hurry
[18:27] <didrocks> just to "meat the deadline" (meaning what was written in the FFe)
[18:27] <ScottK> And I hate to sound like a broken record, but my answer to "when should we land this" is "two weeks ago before feature freeze".
[18:28] <didrocks> knowing that we will have to rush and get things "somewhat ready" later
[18:28] <didrocks> or just delaying
[18:28] <ScottK> I think it'd be better to plan on landing a mature product by feature freeze.
[18:28] <didrocks> ScottK: we all agree on this, we can't deny it :)
[18:28] <didrocks> so delaying by a few days and ensuring that the first shot will make us more proud of the delivery
[18:29] <ScottK> Right.
[18:29] <olli> scottk that's out preference and if that's ok with you then we'd like to go that way
[18:29] <ScottK> olli: Which way?
[18:29] <olli> what didrocks just said: rather delay and have the experience we want
[18:30] <olli> than to dump something now to meet the deadline
[18:30] <infinity> olli: The bottom line is that you shouldn't knowingly ship broken code *and* if it's a new feature not already approved, you'll need to argue an FFe or sabdfl it in.  How the timing for all of that works isn't really up to us, we're not writing the code.
[18:31] <infinity> olli: The deadling, as Scott said, is "two weeks ago", so you've already missed it.  So, if you're going to get something sabdfled in, please make sure it doesn't suck.
[18:31] <infinity> s/deadling/deadline/
[18:31] <didrocks> which will translate in favor of "wait for some additional days and get the first shot in a better shape"
[18:31] <olli> infinity, alright, that's the statement I was hoping to get
[18:31] <didrocks> (not telling awesome, but better)
[18:32] <cjwatson> For things that haven't been sabdfled, "slip to next release" should be on the table.
[18:32] <infinity> Absolutely, yes.
[18:32] <ScottK> cjwatson: Absolutely.
[18:32] <olli> no such things here though
[18:32] <cjwatson> There absolutely is such a thing in Ubuntu.
[18:33] <olli> here:=on my plate
[18:33] <cjwatson> Oh, I see what you mean.
[18:33] <cjwatson> OK.
[18:34] <olli> alright, well, I wanted to reach out and do some better communication than in the past, thx infinity and scottk for your comments and help
[18:34] <ScottK> Thanks.
[18:34] <olli> I guess it's up to us now to deliver
[18:34] <olli> and work on not having that type of conversation in 6mo
[18:34] <ScottK> I think it's up to you to convince Mark if you think you've delivered.
[18:35] <olli> Mark leaves that decision to me
[18:35] <olli> so, I really wanted to make sure I don't screw up more with the release team
[18:35] <ScottK> It takes him saying he's approved it for him to have approved it.
[18:35] <olli> with an emphasis on "more"
[18:36] <olli> ScottK, which is in place for 1154229, isn't it?
[18:37] <ScottK> olli: Yes, but not for Bug #1154176
[18:37] <ubot2> Launchpad bug 1154176 in Unity "[FFE] Add payment preview for music" [Undecided,Fix committed] https://launchpad.net/bugs/1154176
[18:37] <olli> ScottK, true, that's a different story
[18:37] <ScottK> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1154176/comments/13 in particular.
[18:40] <ScottK> So none of the payment stuff has a sabdfl override at the moment.
[18:44] <jtaylor> hi, I have a question concerning scilab
[18:45] <jtaylor> we had it hanging in proposed because it fails to build with a new matio also in proposed
[18:45] <ScottK> Fixing that doesn't need an FFe.
[18:45] <jtaylor> now a few days ago someone uploaded a snapshot which has new features
[18:45] <jtaylor> which ftbs
[18:46] <jtaylor> should we remove the proposed version and instead fix what we have in release?
[18:46] <jtaylor> or now its to late, skip the ffe and fix what is in proposed?
[18:46] <ScottK> Fix what's in proposed unless that's somehow a lot harder.
[18:47] <jtaylor> its probably easier
[18:47] <jtaylor> k, thx just wanted to check
[18:47] <jtaylor> thx
[18:50] <olli> ScottK, ack at 1154176, will see if I can help that team
[18:51]  * olli waves goodbye
[19:33] <sconklin> is there anyone here who can kill some in-progress builds in the kernel PPA for me? I just uploaded a package that supercedes it and I want to free the build resources
[19:33] <cjwatson> possibly.  links?
[19:34] <sconklin> https://launchpad.net/~canonical-kernel-team/+archive/ppa?field.series_filter=lucid
[19:34] <cjwatson> (in general #webops on internal irc is a quicker/better place to ask, but now that you've asked here ...)
[19:34] <sconklin> 2.6.32-46.106
[19:34] <cjwatson> oh, that's a devirt ppa?
[19:34] <sconklin> 107 is uploading now
[19:34] <sconklin> cjohnston: yes
[19:34] <cjwatson> you have to ask webops then - we don't have a webby/api cancel mechanism for devirt ppas
[19:34] <cjohnston> no
[19:35] <cjohnston> ?
[19:35] <sconklin> cjohnston: thanks
[19:35] <sconklin> I meant cjohnston
[19:36] <sconklin> autocomplete fail
[19:36] <cjohnston> 1 + 2 + 3 + tab :-)
[19:37]  * ogra_ guesses sconklin simply didnt read xnox' blog :)
[19:38] <ogra_> (xchat got a cj<tab> fix) .... but you need to set it manually if you used xchat before already
[21:19] <infinity> Huh.  I learned something new today.  Thanks, NEW queue.
[21:20] <ogra_> no armhf ? :(
[21:20] <infinity> (libcangjie1 immediately made me think of Kanji and, lo and behold, Cangjie and Kanji are etymologically related)
[21:20] <infinity> ogra_: I let amd64 through early intentionally so linux-signed can build while I'm waiting on armhf.
[21:20] <ogra_> ah
[21:20] <ogra_> right, takes longer
[21:36] <slangasek> infinity: is that a pinyin spelling?
[21:36] <slangasek> apparently yes
[21:37] <infinity> slangasek: Yeah, pretty much everything I know about Chinese I know from Japanese, so it's fun to see the parallels in anglicisation of matching concepts.
[21:38] <ogra_> btw, do we now all have to learn chinese ?
[21:39] <ogra_> to read code contribution comments and the like ?
[21:39] <infinity> ogra_: You probably should have been doing so for the last decade or so, if you're keen on remaining relavant.
[21:39] <infinity> relevant, too.
[21:39] <slangasek> ogra_: 没有
[21:39] <ogra_> argh
[21:39] <infinity> If you threw in the character for "horse" again by accident, I'm not reading that.
[21:40] <ogra_> ha !
[21:40] <ogra_> now i know how no looks like
[21:40] <ogra_> slangasek, thanks !
[21:40] <slangasek> :)
[21:41] <infinity> I don't even remember the phrase you munged in the meeting now.
[21:41] <infinity> Was it just short a stroke?
[21:41] <infinity> Whatever it was, it turned out rather.  Uhm.  Wrong.
[21:42] <slangasek> yeah, it was short a stroke :)
[21:42] <slangasek> 吗 vs. 马
[21:43] <infinity> Which IME are you using?
[21:43] <infinity> Do we actually have something non-crap now?
[21:43] <slangasek> ibus-pinyin
[21:43] <slangasek> seems to work well enough
[21:43] <slangasek> though kylin want to avoid ibus altogether in favor of fcitx, I don't know why :)
[21:44] <infinity> I haven't looked at all of this for ~5y or so, since I lost any need to write in Japanese, but it was all pretty unfriendly back then compared to Windows, and Windows was bad enough.


[00:22] <Jim`> 2023-03-07T18:13:33-06:00 INFO Waiting for automatic snapd restart...
[00:22] <Jim`> so the update seems stuck?
[00:22] <Jim`> nah it's actually using the CPU
[00:24] <Jim`> it picked back up after like.. 15 mins
[01:05] <Jim`> What's a Expanded Security Maintenance for Applications is not enabled. ?
[01:10] <arraybolt3> Jim`: You can probably just ignore that.
[01:10] <Jim`> arraybolt3: I guess the machine upgraded OK, let me turn on the TV and see
[01:11] <arraybolt3> esm-apps, also known as Ubuntu Pro, is a new service fro m Canonical that provides security updates for a bunch of packages that Ubuntu didn't previously provide reliable security updates for. It's not necessary to have a reasonably secure system, though it is somewhat of a nice-to-have if you use a lot of apps from Ubuntu's Universe repository.
[01:11] <arraybolt3> It's free for up to five systems, but personally I don't use it since I don't really care, and Ubuntu already provides security updates for everything important.
[01:15] <Jim`> anddd the GUI died
[01:15] <Jim`> wait now it works
[01:17] <Jim`> arraybolt3: it displays some random errors at first but goes away and runs and boots?
[01:17] <Jim`> I'd call that a succcessful upgrade?
[01:17]  * Jim` shrugs
[01:19] <arraybolt3> Seems good!
[01:20] <arraybolt3> The "errors" are something about "integrity" and "X.509", right?
[01:20] <arraybolt3> If so, that's normal.
[01:30] <tomreyn> FatPhil: just to make sure you are aware: usb sticks are simple flash media with limited write cycles, it's normal for them to break sooner or later (but rather sooner). this is probably the experience you're making there. you can use a portable ssd for this purpose (but obviously that's more pricey, because it's proper storage)
[01:31] <tomreyn> in the meantime you can run fsck with the badblocks option. but this will only fix things temporarily.
[07:57] <FatPhil> it's a presistent live stick, so the fs is an overlay of the underlying RO image and any changes done to that sitting on top. I'm really not sure how fsck copes with such filesystems (unionfs?)
[07:58] <FatPhil> because it's just a stick, I can analyse it on my laptop at leisure, of course, it's not my "live" system.
 No idea what you're talking about. If you're replying to me, I'm certainly not knowledgeable about it 😄


[00:38] <bluesabre> Unit193: migrated a couple website things. When I tried migrating https://code.launchpad.net/xubuntu-development-server it turned into a mess, so I deleted the resulting git repo
[00:38] <bluesabre> fast-export/import didn't do the job this time :\
[00:40] <Unit193> OK, let me take a look real quick.
[00:45] <bluesabre> Seems like the static-assets branch of xubuntu-website failed similarly
[00:45] <Unit193> bluesabre: I seem to have got it?  What was the issue?
[00:45] <bluesabre> Folder structure got out of whack
[00:46] <Unit193> bluesabre: https://git.unit193.net/cgit/users/unit193/xubuntu-development-server.git/ ?
[00:46] <bluesabre> That looks right
[00:46] <Unit193> Then I'll do the website too for you.
[00:46] <bluesabre> Awesome
[00:47] <Unit193> ...makes me actually useful.
[00:47] <bluesabre> I'll clone both from there to github so they're correct
[00:47] <bluesabre> Nah, you're always useful :)
[00:47] <Unit193> OK, so you want assets/plugins in branches or?
[00:49] <bluesabre> It probably makes more sense to make them separate projects
[00:49] <bluesabre> xubuntu-website-assets, xubuntu-website-plugins
[00:50] <Unit193> ...Heh, so I should start over. ;D
[00:53] <Unit193> bluesabre: Done, I think!
[00:55] <bluesabre> Unit193: looks good!
[00:55] <bluesabre> I'll let you know once they're all pushed
[00:55] <bluesabre> Thanks a bunch
[00:56] <Unit193> Sure thing, any more I can do while I'm at it?  Happy to help.
[00:59] <Unit193> bluesabre: So to explain.  I presume you're on current Ubuntu, thus you're using brz?  That has issues with fastimport and files re-appearing, the only way to fix this is to use the version of bzr-fastimport that I fixed, which is https://launchpad.net/ubuntu/+source/bzr-fastimport/0.13.0+bzr361-4ubuntu1 and thus you must use the python 2 version of bzr.
[01:00] <bluesabre> Yep, that sounds like exactly what it was.
[01:01] <Unit193> I already knew this because I had done some testing with brz and fastimport, but for the life of me I can't remember why.
[01:02] <bluesabre> Maybe just being proactive because py2 was finally officially EOL?
[01:03] <Unit193> I thought I tried to convert a repo.
[01:04] <bluesabre> Unit193: and they're now up at https://github.com/Xubuntu-Team
[01:04] <bluesabre> Thanks again
[01:04] <bluesabre> Time to go back to doing some IRL work
[01:04] <Unit193> Sure thing, always try to be helpful.  I'll delete them off mine now.
[01:04] <bluesabre> bbl
[01:35] <bluesabre> Oh, Unit193, want to convert one more?
[01:35] <bluesabre> https://code.launchpad.net/xubuntu-marketing
[01:36] <bluesabre> I think that's the last "main" xubuntu repo
[01:51] <bluesabre> Yay!
[01:51] <bluesabre> https://github.com/xubuntu
[02:01] <jphilips_> bluesabre: congrats on getting the github url and for the move
[02:02] <jphilips_> here's pleia2's github https://github.com/pleia2
[02:02] <jphilips_> here's mine https://github.com/philipzae
[02:05] <bluesabre> thanks jphilips, added you to the website team
[02:06] <bluesabre> Time for bed for me, night all
[02:06] <jphilips> is the move completed?
[02:07] <jphilips> night
[02:07] <bluesabre> There's one more repo to pull into github, then I gotta tweak a bunch of things on Launchpad
[02:07] <bluesabre> I should finish tomorrow, I think
[02:10] <jphilips> invite accepted
[02:15] <jphilips> not sure if this would be useful, but i saw some github repos that are simply issue trackers or point users to issue trackers hosted elsewhere
[03:18] <Unit193> bluesabre: Sure thing!
[10:27] <jphilips> bluesabre: my cellphone blew up with notifications :D
[10:27] <bluesabre> Oh
[10:27] <bluesabre> Yeah
[10:27] <bluesabre> Migrating issues to things that are not packages
[10:27] <bluesabre> So probably lots of noise :D
[10:29] <Unit193> Got the new repo so I can rm it?
[10:29] <bluesabre> Unit193: sure did, thanks!
[10:29] <Unit193> \o/
[10:31] <Unit193> !info hub
[10:33] <bluesabre> That's pretty cool
[10:33] <Unit193> Oh, should I be in docs too or no?
[10:34] <bluesabre> Looks like you're not currently in it, somehow, https://launchpad.net/~xubuntu-doc/+members#active
[10:36] <bluesabre> And now you are
[10:36] <Unit193> I really need to push that so translations work again.. :/
[10:36] <bluesabre> Please do :)
[10:38] <Unit193> I guess there's something I'm not really happy with, but I guess it's better than the current state.
[10:41] <bluesabre> Unit193: what is it?
[10:42] <Unit193> Not sure, maybe with how the translations all take a percentage hit?
[10:43] <bluesabre> That should be fine, so we're redoing the docs currently anyway
[10:43] <bluesabre> They're all going to be < 50%
[10:43] <bluesabre> *since
[10:44] <Unit193> Hopefully this doesn't mean things are changing and it won't break turning it back into XML. :>
[10:44]  * bluesabre believes in Unit193
[10:44] <Unit193> OK, I'll look into it later today.
[10:44] <bluesabre> Thanks a bunch
[10:45] <Unit193> !info itstool
[10:46] <bluesabre> ochosi: nagging to accept the invite to the github team
[10:46] <bluesabre> :)
[10:47] <Unit193> He thinks he ran away to Xfce upstream.
[10:47] <bluesabre> :D
[10:49] <bluesabre> All that's left for the migration now is setting up import branches on Launchpad and updating all the project descriptions to push people to GitHub for the code.
[10:49] <bluesabre> Pretty cool.
[10:49] <bluesabre> Time to do other things, bbl
[10:51] <bluesabre> jphilips: I think I'll use your landing page project idea to point people to the slideshow project and translations. All flavor slideshows are translated together: https://translations.launchpad.net/ubuntu/focal/+source/ubiquity-slideshow-ubuntu
[10:54] <jphilips> great
[10:54] <Unit193> Oh, anything I need to know about transifex?
[10:55] <bluesabre> Unit193: I can add you as a collaborator there... what's your username
[10:55] <Unit193> Wanna guess?
[10:56] <bluesabre> Guess its too short to look you up
[10:56] <bluesabre> Wanna send me your email address used there instead?
[10:56] <Unit193> Dang, well I should be unit193, I think.  But gmail.com?
[10:56] <Unit193> Yep, username is 'unit193'
[10:57] <bluesabre> Cool
[10:57] <bluesabre> Sent you an invite
[10:57] <Unit193> !info transifex-client
[10:57] <Unit193> bluesabre_xubuntu, eh?
[10:58] <bluesabre> I have another account there... but one account can only have one organization
[10:58] <bluesabre> So I had to ... cheat
[10:58] <Unit193> Huh.  Gotcha.
[11:13] <jphilips> bluesabre: noticed that importing doesn't seem to bring everything from launchpad
[11:14] <jphilips> https://github.com/Xubuntu/xubuntu-website/issues/9#issuecomment-632005906
[11:14] <jphilips> https://bugs.launchpad.net/xubuntu-website/+bug/1842182/comments/1
[11:14] <jphilips> it brought in 'This has been resolved.' but not the rest
[12:56] <ochosi> bluesabre: somehow doesnt work on phone, gotta do it tonight
[16:09] <bluesabre> jphilips: yeah, did those comments after the bug migration
[16:17] <jphilips> pleia2, bluesabre: i think this bug by knome can be closed https://github.com/Xubuntu/xubuntu-website/issues/1
[16:17] <jphilips> or am i missing something
[18:41] <jphilips> bluesabre: any thoughts why when i'm searching with catfish in the /usr/share/icons/ folder, its being up results from the /mnt/ folder?
[21:30] <bluesabre> jphilips: my guess would be that something in there has a questionable symlink
[22:27] <Unit193> bluesabre: Do we want to switch to ubot93 for bugsnarfing?  It additionally has support for GitLab installations (xfce) and GitHub.
[22:30] <Unit193> Got ubottu's !info default updated to groovy.
[22:35] <genii> Unit193: For +1 and the -devel channels?
[22:38] <Unit193> genii: Just for here.
[22:42] <genii> Just curious :)
[22:44] <Unit193> See -irc.


[02:08] <guiverc> Sorry Bashing-om, I just noticed a question on gdoc for me..  I occasionally get gdoc highlighting I've got unread mail but I tend to ignore it (it opens with a long list dating back to 2017.. which tends to make-useless chromium on this old 2009 dell box... so I usually ignore it).
[02:09] <guiverc> As for the 'pin' after other community; has it gone now?
[02:09]  * guiverc had nothing to do anyway... you'd added what i was gonna add already :)
[02:10] <Bashing-om> guiverc: No indea what it is - but yes I managed to delete it.
[02:10] <guiverc> :)
[02:12] <Bashing-om> guiverc: Starting the issue out with a load - We may have our work cut out for us come Friday ( My time).
[02:39] <guiverc> ack..
[16:33] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: StarBook Mk V Linux Laptop @ https://www.omgubuntu.co.uk/2021/05/starbook-mk-v-linux-laptop-specs-price (by Joey Sneddon)
[23:00] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Linux Release Roundup: elementary OS, Kdenlive & Cawbird Twitter App @ https://www.omgubuntu.co.uk/2021/05/linux-release-roundup-elementary-os-kdenlive-cawbird-twitter-app (by Joey Sneddon)


[06:09] <ducasse> good morning, everyone
[06:10] <jink> https://pbs.twimg.com/media/DaCKPlnW0AE9UjG.jpg:large
[07:02] <lordievader> Good morning
[07:02] <lordievader> jink: Nice one 😉
[07:07] <ducasse> hi lordievader - all well?
[07:07] <lordievader> Doing good here, how are you?
[07:11] <ducasse> all well here, thanks. snow finally melting.
[07:13] <lordievader> It got cold here again.
[07:14] <lordievader> Looked out the window this morning, sun was shining, I figured it would be warm. On my way to work it was damned cold -.-
[07:23] <ducasse> we've had warm weather for a few days, forecast says more to come.
[10:31] <BluesKaj> Hi folks


[17:38] <Unit193> canthus13: You find the cherokee group on Google?
[17:39] <canthus13> Nope.
[17:39] <canthus13> never looked.
[17:39] <canthus13> Got Nagios working on it, though.
[18:06] <Unit193> Alrighty.  I use that one, but I built a package for 1.2.103.
[18:24] <thafreak> nginx
[18:25] <Unit193> At least I'm not going with apache. :D
[22:33] <canthus13> Unit193: Heh. Cherokee wasn't THAT difficult to get nagios working under, except for the fact that it doesn't include htpasswd. :/
[22:35] <Unit193> Yeah, it comes in apache2-utils.
[22:37] <Unit193> And was more thinking that the channel is pretty inactive. :P
[22:53] <canthus13> Unit193: I'm really getting annoyed with the crappy documentation for nagios.  I can't find anything that really tells me how to talk to the NRPE plugins on other machines. :/


 <sil2100> RikMills, mitya57: hey! I see new qtbase and qtwebengine in the queue - those are bugfix only releases? How confident are you in those landing after beta?
 @mitya57 from #ubuntu-release
 which I am sure you got pinged by, but just covering bases here ;)
[09:05] <mitya57> Replied!
 cool. thanks


[00:51] <xnox> slangasek, https://code.launchpad.net/~xnox/britney/hints-ubuntu/+merge/354198
[00:52] <xnox> should kexec tools continue to be blogged because of a broken kernel in proposed? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790513
[00:52] <xnox> it is not possible to run tests on a non-proposed kernel.
[03:25] <slangasek> xnox: your bug asks a question, but above you seem to assume an answer about whose bug it is; which package needs changed in order to fix this?  Since as things stand, this bug will not block linux 4.18 from reaching cosmic
[03:27] <xnox> slangasek, i was not sure if i should be bold enough to block linux v4.18
[03:27] <xnox> imho cannot kdump is severe
[03:27] <xnox> but what do i know.....
[03:28] <slangasek> xnox: well, all three of linux, kexec-tools, and makedumpfile are the responsibility of the kernel team, so perhaps make it their problem :)
[03:34] <xnox> ha
[03:38] <slangasek> xnox: kdump not working is certainly a serious problem, but whether they want that to block the new kernel reaching cosmic is something I would leave to them to decide
[04:48] <cpaelzer> bdmurray: new ones on top of the two that I analyzed
[04:48] <cpaelzer> bdmurray: taking a look
[04:52] <cpaelzer> bdmurray: oh yeah, I'll update the upstream bug
[04:52] <cpaelzer> bdmurray: feel free to stop the phasing for now
[04:52] <cpaelzer> unfortunately without more data than the partial stack traces in the reports it is hard to go on atm
[04:52] <cpaelzer> grml
[04:52] <cpaelzer> thanks for the ping
[04:53] <cpaelzer> at the time I sent the mail this was quite different to what it looks now
[05:02] <cpaelzer> got to your mail now - ack
[05:02] <cpaelzer> I hope I find something with this scarce info we have :-/
[05:06] <cpaelzer> bdmurray: FYI spawned bug 1791220 for this
[05:07] <cpaelzer> I'll need to finalize a few other things on my plate for today and then will take a look at a disassembly
[05:07] <cpaelzer> it all is at the same spot, so maybe I can find disasm -> source -> review to find the bug
[08:05] <Laney> slangasek: I missed that, sorry - what's the problem? Seems to be running here.
[08:07] <slangasek> Laney: http://autopkgtest.ubuntu.com/running#pkg-r-cran-fastmatch
[08:09] <Laney> slangasek: That looks to be autopkgtest@bos02-ppc64el-20
[08:09] <slangasek> yes
[08:09] <Laney> OK, just checking, since you said<EMAIL_ADDRESS>earlier
[08:09] <slangasek> Laney: ah yes, I copy-pasted the wrong unit from history
[08:09] <Laney> :P
[08:10] <Laney> does Aug 25 07:44:36 correspond to some maintenance?
[08:11] <slangasek> not afaik; and there were a total of 7 units across multiple clouds in this state, with varying times
[08:13] <slangasek> cough, apologies for secureboot-db 1.2, it works fine if you install it on an actual secureboot system, notsomuch otherwise.  1.3 should fix this
[08:13] <Laney> right, I don't feel like I'll be able to be very lucky finding out what event caused the test to not finish
[08:13] <Laney> still at the very least sounds like a bug that autopkgtest hasn't timed out
[08:13] <slangasek> Laney: yeah, it was the latter I was more interested in
[08:20] <Laney> slangasek: I don't have any bright ideas for what I could do with this running process, do you?
[08:21] <slangasek> Laney: I tried everything I could with the running process and got nowhere
[08:21] <slangasek> so I left it in a state that you could inspect if you knew something I didn't
[08:21] <Laney> Guess we get to file a not so useful bug :(
[08:21] <slangasek> strace shows that one of the subprocesses is waiting on stdin
[08:50]  * Laney kills it
[09:22] <doko> Laney: thanks for enabling the gcc autopkg tests. Now that we check for an empty libgcc1 package, please can you remove the artificial libreoffice autopkg test trigger?
[09:24] <doko> apw: gcc-8 migrated, gcc-7 not yet
[09:33] -queuebot:#ubuntu-release- New binary: julia [ppc64el] (cosmic-proposed/universe) [1.0.0-0ubuntu2] (no packageset)
[09:52] -queuebot:#ubuntu-release- New binary: julia [arm64] (cosmic-proposed/universe) [1.0.0-0ubuntu2] (no packageset)
[10:39] -queuebot:#ubuntu-release- New: accepted julia [arm64] (cosmic-proposed) [1.0.0-0ubuntu1]
[10:39] -queuebot:#ubuntu-release- New: accepted julia [arm64] (cosmic-proposed) [1.0.0-0ubuntu2]
[10:39] -queuebot:#ubuntu-release- New: accepted nova-lxd [amd64] (cosmic-proposed) [18.0.0~rc2-0ubuntu2]
[10:39] -queuebot:#ubuntu-release- New: accepted julia [ppc64el] (cosmic-proposed) [1.0.0-0ubuntu1]
[10:39] -queuebot:#ubuntu-release- New: accepted julia [ppc64el] (cosmic-proposed) [1.0.0-0ubuntu2]
[10:40] -queuebot:#ubuntu-release- New: accepted darkmint-gtk-theme [sync] (cosmic-proposed) [2.0.0-1]
[10:40] -queuebot:#ubuntu-release- New: accepted numix-icon-theme-circle [sync] (cosmic-proposed) [18-04-04-1]
[10:40] -queuebot:#ubuntu-release- New: accepted ufonormalizer [sync] (cosmic-proposed) [0.3.5-1]
[10:40] -queuebot:#ubuntu-release- New: accepted fontpens [sync] (cosmic-proposed) [0.1.0-1]
[10:40] -queuebot:#ubuntu-release- New: accepted pipewire [sync] (cosmic-proposed) [0.2.2-1]
[10:42] -queuebot:#ubuntu-release- New binary: pipewire [s390x] (cosmic-proposed/none) [0.2.2-1] (no packageset)
[10:43] -queuebot:#ubuntu-release- New binary: pipewire [ppc64el] (cosmic-proposed/none) [0.2.2-1] (no packageset)
[10:44] -queuebot:#ubuntu-release- New binary: fontpens [amd64] (cosmic-proposed/none) [0.1.0-1] (no packageset)
[10:44] -queuebot:#ubuntu-release- New binary: darkmint-gtk-theme [amd64] (cosmic-proposed/none) [2.0.0-1] (no packageset)
[10:44] -queuebot:#ubuntu-release- New binary: ufonormalizer [amd64] (cosmic-proposed/none) [0.3.5-1] (no packageset)
[10:45] -queuebot:#ubuntu-release- New binary: numix-icon-theme-circle [amd64] (cosmic-proposed/none) [18-04-04-1] (no packageset)
[10:46] -queuebot:#ubuntu-release- New binary: pipewire [arm64] (cosmic-proposed/none) [0.2.2-1] (no packageset)
[10:48] -queuebot:#ubuntu-release- New binary: pipewire [armhf] (cosmic-proposed/none) [0.2.2-1] (no packageset)
[10:49] -queuebot:#ubuntu-release- New binary: pipewire [i386] (cosmic-proposed/universe) [0.2.2-1] (no packageset)
[10:51] -queuebot:#ubuntu-release- New binary: pipewire [amd64] (cosmic-proposed/universe) [0.2.2-1] (no packageset)
[10:55] -queuebot:#ubuntu-release- New: accepted pipewire [amd64] (cosmic-proposed) [0.2.2-1]
[10:55] -queuebot:#ubuntu-release- New: accepted pipewire [armhf] (cosmic-proposed) [0.2.2-1]
[10:55] -queuebot:#ubuntu-release- New: accepted pipewire [ppc64el] (cosmic-proposed) [0.2.2-1]
[10:55] -queuebot:#ubuntu-release- New: accepted pipewire [arm64] (cosmic-proposed) [0.2.2-1]
[10:55] -queuebot:#ubuntu-release- New: accepted pipewire [s390x] (cosmic-proposed) [0.2.2-1]
[10:55] -queuebot:#ubuntu-release- New: accepted pipewire [i386] (cosmic-proposed) [0.2.2-1]
[10:56] -queuebot:#ubuntu-release- New: accepted darkmint-gtk-theme [amd64] (cosmic-proposed) [2.0.0-1]
[10:56] -queuebot:#ubuntu-release- New: accepted numix-icon-theme-circle [amd64] (cosmic-proposed) [18-04-04-1]
[10:56] -queuebot:#ubuntu-release- New: accepted fontpens [amd64] (cosmic-proposed) [0.1.0-1]
[10:56] -queuebot:#ubuntu-release- New: accepted ufonormalizer [amd64] (cosmic-proposed) [0.3.5-1]
[11:04] <xnox> sforshee, apw - all the git clones, over https, were successful in the last couple of linux runs. le sigh. i mean great, linux/s390x passed.
[11:05] <xnox> but i fear the cloning thing might come back
[14:21] -queuebot:#ubuntu-release- New binary: mshr [s390x] (cosmic-proposed/universe) [2018.1.0+dfsg1-5] (no packageset)
[14:21] -queuebot:#ubuntu-release- New binary: mshr [ppc64el] (cosmic-proposed/universe) [2018.1.0+dfsg1-5] (no packageset)
[14:24] -queuebot:#ubuntu-release- New binary: mshr [i386] (cosmic-proposed/universe) [2018.1.0+dfsg1-5] (no packageset)
[14:27] -queuebot:#ubuntu-release- New binary: mshr [amd64] (cosmic-proposed/universe) [2018.1.0+dfsg1-5] (no packageset)
[14:28] -queuebot:#ubuntu-release- New binary: mshr [armhf] (cosmic-proposed/universe) [2018.1.0+dfsg1-5] (no packageset)
[14:55] <jbicha> please remove sysprof/s390x/cosmic : it only built because we ignored build test failures in the previous release
[15:11] -queuebot:#ubuntu-release- Unapproved: accepted openssh [source] (xenial-proposed) [1:7.2p2-4ubuntu2.5]
[15:11] -queuebot:#ubuntu-release- New: accepted mshr [amd64] (cosmic-proposed) [2018.1.0+dfsg1-5]
[15:11] -queuebot:#ubuntu-release- New: accepted mshr [i386] (cosmic-proposed) [2018.1.0+dfsg1-5]
[15:11] -queuebot:#ubuntu-release- New: accepted mshr [s390x] (cosmic-proposed) [2018.1.0+dfsg1-5]
[15:11] -queuebot:#ubuntu-release- New: accepted mshr [armhf] (cosmic-proposed) [2018.1.0+dfsg1-5]
[15:11] -queuebot:#ubuntu-release- New: accepted mshr [ppc64el] (cosmic-proposed) [2018.1.0+dfsg1-5]
[15:23] <didrocks> sil2100: is "building from a ppa" a new requirement for FFe?
[15:23] <didrocks> I have built it locally and tested it on cosmic (no build-dep changes btw)
[15:24] <didrocks> the "provide build logs" sound a little bit of lack of trust to the packager btw :p
[15:26] <didrocks> so, I can build it in a ppa and redo the whole manual testing from it, but this sounds like a waste of time to redo all this and ensuring it's stable as well
[15:41] <xnox> i wonder if the buildlogs req is there from before ppas...
[15:46] <sil2100> didrocks: I didn't invent that: https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_for_new_upstream_versions
[15:46] <sil2100> didrocks: it's been there since ages
[15:47] <sil2100> didrocks: when was the last time you checked it? You can provide any build logs, PPA seemed just convenient
[15:47] <didrocks> sil2100: right, but it's the first time that I was actually asked for a ppa and the build logs, sounds like other members and yourself in the past were more trusting us
[15:48] <didrocks> I mean, I can understand for a one time drive-by contributor, but it seems we are making things more and more full of paperwork, anyway…
[15:48] <sil2100> didrocks: ok, I guess if you say it builds then that's good enough-ish, I generally started following the procedures a bit more since I don't want to have double-standards, I guess it's better to be more strict than less
[15:49] <sil2100> didrocks: a PPA build is convenient because it tests more than one arch
[15:49] <didrocks> true, I'm not annoyed by pushing to a ppa, the second round of testing can be annoying though
[15:49] <sil2100> didrocks: we wouldn't want things to FTBFS suddenly on some untested arch and then delay things ;)
[15:50] <didrocks> won't be for today anymore though, we'll see on Monday now
[15:50] <sil2100> didrocks: anyway! Let's do it like this: just leave a comment stating that you have performed a successful local test build
[15:50] <didrocks> sil2100: if you prefer the ppa, I can do it… Just find it weird ;)
[15:51] <didrocks> the second round of testing will take more time as it's all manual and more "running and see it being stable", but oh my, that's for another week anyway
[15:51] <sil2100> didrocks: I guess it's fine this time, since it's early and I don't want you to feel untrusted!
[15:52] <sil2100> Like, by early I mean 'not that super late in the cycle'
[15:52] <didrocks> sil2100: ok, let me add the comment then! Thanks :)
[15:52] <didrocks> yep
[15:52] <sil2100> Just saying that I'm not inventing any new rules here, just going by the book here!
[15:53] <didrocks> oh, I didn't say that wasn't written on the wiki page, but this is the first time I saw it asked for a long time contributor
[15:53] <didrocks> we'll get used to it I guess :p
[15:53] <didrocks> sil2100: commented (but anyway, I'll only upload on Monday, don't want to break things during the week-end, just in case :p)
[15:56] <sil2100> didrocks: you know I trust you!
[15:57] <sil2100> didrocks: it's just you know, paperwork and such... ;p
[15:57] <sil2100> (and certainty that nothing's busted, but as said, there's still time to get things building in the worst case anyway)
[15:57] <didrocks> sil2100: no worry ;)
[15:57] <didrocks> and thanks!
[16:41] -queuebot:#ubuntu-release- New binary: gpaste [s390x] (cosmic-proposed/universe) [3.28.2-1] (no packageset)
[16:41] -queuebot:#ubuntu-release- New binary: gpaste [ppc64el] (cosmic-proposed/universe) [3.28.2-1] (no packageset)
[16:42] -queuebot:#ubuntu-release- New binary: gpaste [arm64] (cosmic-proposed/universe) [3.28.2-1] (no packageset)
[16:43] -queuebot:#ubuntu-release- New binary: gpaste [armhf] (cosmic-proposed/universe) [3.28.2-1] (no packageset)
[16:45] -queuebot:#ubuntu-release- New binary: gpaste [amd64] (cosmic-proposed/universe) [3.28.2-1] (no packageset)
[16:45] -queuebot:#ubuntu-release- New binary: gpaste [i386] (cosmic-proposed/universe) [3.28.2-1] (no packageset)
[18:15] -queuebot:#ubuntu-release- Unapproved: open-iscsi (bionic-proposed/main) [2.0.874-5ubuntu2.1 => 2.0.874-5ubuntu2.2] (ubuntu-desktop, ubuntu-server)
[20:38] -queuebot:#ubuntu-release- Unapproved: syslinux (bionic-proposed/main) [3:6.03+dfsg1-2 => 3:6.03+dfsg1-2ubuntu<IP_ADDRESS>] (core)
[21:20] <slangasek> I start processing the libreoffice SRU, and launchpad throws an oops trying to show me https://launchpad.net/ubuntu/+source/libreoffice
[21:20] <slangasek> it's an omen
[21:58] <xnox> slangasek, ok so i did $ sudo cat /proc/keys
[21:58] <xnox> slangasek, and I did not like this:
[21:58] <xnox> 30814288 I------     1 perm 1f030000     0     0 asymmetri sforshee: 00b28ddf47aef9cea7: X509.rsa []
[21:59] <slangasek> :D
[21:59] <slangasek> xnox: he's the upstream owner of the regdb key
[21:59] <slangasek> I've had this reaction before when watching him scroll by in dmesg
[22:05] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.35.1+18.04]
[22:49] -queuebot:#ubuntu-release- New sync: mozjs60 (cosmic-proposed/primary) [60.1.0-1]
[22:50] <jbicha> feel free to kill mozjs38 now, it never was in Debian LP: #1728184
[22:59] <jbicha> we know that mozjs60 has a build problem on i386 and we will file a FFe if we do switch to mozjs60 for 18.10