=== s1aden is now known as sladen
[00:45] <mwhudson> what the heck is going on here? https://launchpadlibrarian.net/318753835/buildlog_ubuntu-artful-amd64.paste_1.7.5.1-6ubuntu3_BUILDING.txt.gz
[00:45] <mwhudson> dpkg-genbuildinfo: error: cannot fstat file ../python-paste_1.7.5.1-6ubuntu3_all.deb: No such file or directory
=== wendar_ is now known as wendar
[02:55] <cjwatson> mwhudson: read up slightly above that - need to stop using -Z bzip2 (default is now xz which is generally better)
[02:56] <mwhudson> cjwatson: ah ok
[04:05] <mwhudson> wgrant: do you (or anyone else) know stuff about python packaging?
[04:06] <mwhudson> the story is that the current jinja2 package doesn't install some files that have syntax that python 3.5 doesn't accept
[04:06] <mwhudson> but without them, jinja2 doesn't install under python 3.6
[04:06] <mwhudson> er doesn't import
[04:06] <mwhudson> so i changed the package to include them but now it doesn't install properly because errors get spat out by python3.5 during install
[04:09] <mwhudson> oh wait, man dh_python3 explains this
=== Spads_ is now known as Spads
=== kitterma is now known as ScottK
=== zyga_ is now known as zyga
[07:32] <mwhudson> no, that doesn't work
[07:46] <Skuggen> Is there some way to get dput (for uploading to a launchpad ppa) working behind a proxy?
[07:49] <infinity> Skuggen: If it's a proxy that forwards active FTP but fails miserably at passive you could try twiddling passive_ftp to 0 in /etc/dput.cf
[07:50] <infinity> Skuggen: Alternately, sftp might work better, see https://help.launchpad.net/Packaging/PPA/Uploading#Uploading_with_SFTP
[08:04] <Skuggen> infinity: Thanks, I'll give it a try :)
[08:05] <Skuggen> I tried changing a ~/.dput.cf before, but according to the debug output it was still using passive, but can try with the file in /etc instead
=== tyhicks` is now known as tyhicks
[15:06] <rbasak> !dmb-ping
[15:06] <ubottu> bdmurray, BenC, cyphermox, infinity, micahg, rbasak, sil2100: DMB ping.
[15:27] <nacc> gsilvapt: i'm around now
[16:23] <nacc> tjaalton: do you know if the dogtag trac moved somewhere else with fedorahosted reitrement (re: LP: #1662654)
[16:23] <ubottu> Launchpad bug 1662654 in tomcat8 (Ubuntu) "Please remove resteasy (3.1.0) from zesty-proposed" [Undecided,Fix released] https://launchpad.net/bugs/1662654
[16:23] <nacc> the link goes to the retirement page
[16:25] <nacc> tjaalton: and do you have the link to the resteasy bug
[17:04] <sarnold> gsilvapt: now that the update is pushed, you can go through the pull-ubuntu-source, patch, build, test, iterations
[17:17] <gsilvapt> ah. okay. I can try to do that now. Thanks, sarnold
[17:17] <gsilvapt> I need help solving a community issue. Can someone forward me to the right place?
[17:18] <wxl> what's up gsilvapt ? also hey :)
[17:18] <gsilvapt> hey wxl, long time no see
[17:19] <nacc> gsilvapt: what community issue?
[17:19] <gsilvapt> There's this guy that I'm not sure what the hell is his goal. He started my suggesting an edit that had swastikas in the page and thought it was okay and now he removed content from Wiki pages that were useful and he didn't ask anyone before doing any changes
[17:20] <nacc> gsilvapt: spammer?
[17:20] <gsilvapt> Of course we can revert that back but it's getting extremely ridiculous at this point
[17:20] <nacc> gsilvapt: on the wiki?
[17:20] <gsilvapt> I have no idea. I once emailed him suggesting to keep his cool, get to know the people around, ask & suggest stuff in the *proper* way and not spam/do stuff right-of-the-box because nobody would listen to him
[17:20] <wxl> links may be helpful
[17:21] <gsilvapt> He said he had been contributing for 9 years and he would be fine. lol
[17:21] <gsilvapt> s/page/wiki
[17:21] <cjwatson> swastikas in pages are just a matter of banning, IMO.  the Ubuntu code of conduct does not require you to negotiate with Nazis
[17:21] <nacc> heh
[17:21] <nacc> sad that it's even a thing
[17:22] <wxl> what if it's the more eastern persuastion of swastika?
[17:22] <cjwatson> (OK, unless it's explicitly in one of the relevant Asian religious contexts, but I can't see why that would be on-topic in the Ubuntu wiki either)
[17:22] <wxl> that
[17:22] <wxl> i guess someone could use them for bulletpoints
[17:22] <cjwatson> ... but shouldn't
[17:22] <gsilvapt> link to page where he deleted content, according to Brian Murray: https://lists.ubuntu.com/archives/ubuntu-quality/2017-May/006887.html
[17:22] <wxl> i don't see it as RELEVANT, but that doesn't mean someone wouldn't use them
[17:23] <cjwatson> I don't think it's interesting playing the what-if game on this.  If it was actually a relevant non-Nazi use then I assume gsilvapt would have said
[17:23] <cjwatson> don't be played by trolls
[17:24] <gsilvapt> And this all started here: https://lists.ubuntu.com/archives/ubuntu-quality/2017-April/006847.html
[17:24] <gsilvapt> He later removed the images of swastikas, FYI
[17:24] <cjwatson> where was the swastika thing?
[17:25] <jbicha> I think original was https://commons.wikimedia.org/wiki/File:Blueprint_of_Victory._Avoid_the_Black_Widow_of_war_production_-_NARA_-_534556.jpg
[17:25] <jbicha> tweaked to https://wiki.ubuntu.com/es20490446e/Reporting%20bugs?action=AttachFile&do=view&target=Blueprint.jpg
[17:25] <tjaalton> nacc: oh right, I'll update that
[17:25] <nacc> tjaalton: thanks!
[17:25] <wxl> um, equating windows (?) to nazis?
[17:26] <cjwatson> ok, I guess that's super bad taste rather than Nazi advocacy
[17:27] <wxl> where did you find that btw, jbicha ?
[17:27] <jbicha> wxl: by digging through https://wiki.ubuntu.com/es20490446e/Reporting%20bugs?action=info
[17:27] <cjwatson> though I would not defend it and perhaps the poster needs a cooling-off period
[17:28] <nacc> also, i think there is a general issue with es20490446e on bugs :)
[17:28] <wxl> yeah i hadn't seen it when i searched through there
[17:28] <wxl> XD
[17:28] <nacc> gsilvapt: so it's not like you are unique here :)
[17:28] <wxl> nacc: that is a WHOLE different story XD
[17:28] <nacc> wxl: :)
[17:29] <gsilvapt> Look, I stopped reading his stuff a long ago. I feel he is trying to troll us. He sends youtube videos as replies to emails on the mailing list
[17:29] <wxl> um
[17:29] <gsilvapt> Today I got another email from someone complaining he removed parts he considered important in the Wiki
[17:29] <wxl> so Alberto is the one who did that?
[17:29] <gsilvapt> Yes, wxl
[17:29] <nacc> wxl: it appears so (the original image)
[17:29]  * wxl sighs
[17:29] <cjwatson> see also https://bugs.launchpad.net/launchpad/+bug/1686518
[17:29] <ubottu> Launchpad bug 1686518 in Launchpad itself "The reporting guidelines aren't well fitted" [Undecided,New]
[17:30] <cjwatson> the "just a joke" defence he used for the swastika bit is unacceptable
[17:30] <jbicha> https://help.ubuntu.com/community/ReportingBugs
[17:31] <jbicha> https://help.ubuntu.com/community/ReportingBugs?action=recall&rev=299
[17:31] <gsilvapt> And I thought this had to stop. I have no clue if I'm just being too naggy or if this is actually crossing the line of reason and thus asked for help for some to check this
[17:31] <gsilvapt> I emailed the council once, I don't want to email again if they did nothing on this before
[17:31] <gsilvapt> (before being the Swastika and his "just a joke" comment)
[17:31] <cjwatson> this certainly seems like a matter for the CC, anyway
[17:31] <wxl> he's a very avid contributor, it seems, at least in terms of the frequency of contributions
[17:31] <wxl> quality of contributions may be open for discussion..
[17:32] <nacc> SNR is low, in my experience
[17:32] <nacc> not that they are not making ubuntu better, admittedly
[17:32] <wxl> and i've found him entirely convinced of his own opinion and unwilling to listen otherwise
[17:32] <wxl> this has come up more than once
[17:32] <wxl> i'm sure the cc looks at the former point as trumping the latter ones, though
[17:33] <cjwatson> they may do, but they should actually respond
[17:33] <cjwatson> rather than leaving people to guess
[17:33] <nacc> yep
[17:34] <gsilvapt> yea wxl, I was surprised to see his LP karma page. He might have been around for 9 years after all but it seems most of his contributions are more setbacks rather than progress. What he is doing is not aligned with anything other than his opinions
[17:34] <wxl> karma is of no real value :)
[17:34] <gsilvapt> Sure but it says if a person is active or not
[17:34] <wxl> right
[17:35] <nacc> seb128: will you be merging/fixing gnome-menus this cycle? just tracking stuff in merges i'm associated with :)
[17:36] <nacc> slangasek: are you doing an lvm2 merge? rbalint's fix for LP: #1576341 will add to the delta and i wonder if we should just send it to Debian?
[17:36] <ubottu> Launchpad bug 1576341 in systemd (Ubuntu) "systemd in degraded state on startup in LXD containers" [High,Confirmed] https://launchpad.net/bugs/1576341
[17:36] <wxl> what i would suggest is contacting them again with https://bugs.launchpad.net/launchpad/+bug/1686518 being a really concrete example of the problems he causes. you might want to check out #ubuntu-community-team as some cc members hang out there
[17:36] <ubottu> Launchpad bug 1686518 in Launchpad itself "The reporting guidelines aren't well fitted" [Undecided,New]
[17:36] <wxl> gsilvapt: ^^
[17:36] <wxl> with popey, mhall119 being the most active
[17:37] <cjwatson> https://bugs.launchpad.net/launchpad/+bug/1686518 is an "annoys Colin" kind of thing, not a "should be banned" kind of thing; I think it's at most illustrative
[17:37] <wxl> cjwatson: well, i'm not suggesting the cc ban him. but suggesting better behavior might be appropriate.
[17:37] <cjwatson> I think the terrible stuff around the proposed wiki edit is a much better example, but it's probably worth accumulating things
[17:38] <wxl> he may think he can just bully people around, but i doubt he would be so inclined with the cc.
[17:38] <gsilvapt> Okay, I can try to get in touch with them again and bring this example to the table
[17:39] <wxl> also, colin, you really eloquently reflect my feelings about video. the post that drove me crazy was https://lists.ubuntu.com/archives/ubuntu-quality/2017-May/006888.html
[17:39] <cjwatson> (I've encountered this user a few times, but before seeing the stuff gsilvapt posted here I only considered them annoying rather than anything more)
[17:39] <wxl> gsilvapt: feel free to cc me in further emails. i certainly agree with your concerns and would be willing to support you
[17:41] <jbicha> he also annoyed GNOME recently, https://bugzilla.gnome.org/782002
[17:41] <ubottu> Gnome bug 782002 in general "Making GNOME really pleasant to use" [Normal,Resolved: incomplete]
[17:41] <gsilvapt> cjwatson, yep, that's my problem. I stopped reading his stuff a while back, when he posted a private video entitled "I feel Ubuntu is facing doom". From thereon, I just ignored his stuff. Then some answers started getting my attention. First the swastika, now the user complaining he deleted important parts of the wiki page. Men... Trolls are trolls, this is something else
[17:42] <gsilvapt> Thank you wxl, I think I'll reply to my own email to add this another example and keep the previous message
[17:42] <infinity> I kinda feel like he's using Ubuntu mailing lists to get impressions on his youtube channel. :P
[17:42] <gsilvapt> Who knows....
[17:43] <wxl> cjwatson: my concern is that even annoying can be severely problematic. what's annoying to us might be infuriating to others. maybe even causing them to give up contributions and/or assume the community consists of and supports people with similar attitudes
[17:43] <slangasek> nacc: am I doing an lvm2 merge> grep-merges tells me that you TIL; I don't particularly care who does it, it's been a pretty trivial merge up to now
[17:43] <nacc> infinity: heh
[17:43] <nacc> slangasek: ack, i was just going to remerge it now and pull in rbalint's fix at the same time
[17:43] <wxl> "I know this project doesn't like reports in video, but I think this is the exception rather than the rule:"
[17:43] <nacc> slangasek: if it wasn't on your plate, you had just done the last merge
[17:43]  * wxl facepalms
[17:43] <slangasek> nacc: yeah, go for it :)
[17:44] <nacc> slangasek: thanks
[17:45] <cjwatson> wxl: yes
[17:45] <slangasek> gsilvapt, wxl: uh... what's this about swastikas and wiki page deletions?
[17:45] <slangasek> fwiw bdmurray has a lot of context on this particular contributor
[17:47] <wxl> gsilvapt: if you read the CoC, i think there are some points where there is clear violation. i'd be willing to reply to your initial email with further elaboration on that.
[17:47] <wxl> slangasek: i didn't know about it, but jbicha summarized the relevant links above. tl;dr ReportingBugs wiki :(
[17:49] <cjwatson> feels like a more or less well-intentioned contributor whose idea of being constructive is at right-angles to everyone else's and isn't listening to feedback, which is one of the most difficult cases to deal with
[17:49] <nacc> rbalint: are you ok with me pulling your fix for the above bug into the merge?
[17:49] <rbalint> nacc: perfectly, thanks :-)
[17:49] <nacc> rbalint: might do the same for open-iscsi if that's ok with you
[17:49] <nacc> rbalint: also, thank you very much for the bug feedback!
[17:49] <slangasek> cjwatson: not counting that one time when he tried to troll debian-devel into fighting with the Ubuntu community for him
[17:51] <cjwatson> slangasek: I don't remember that one
[17:52] <rbalint> nacc: sure, please update open-iscsi
[17:52] <nacc> rbalint: thanks!
[17:52] <rbalint> nacc: i'm building the systemd, but some tests are failing
[17:52] <nacc> rbalint: fun :)
[17:53] <infinity> cjwatson: Well-intentioned or not, I've just wasted several minutes of my life on more than one video response of his from that thread that amount to "sorry, not sorry", and "people will always be angry about something, so you should let me publish swastikas in the wiki, you fascists".
[17:53] <bdmurray> I was hoping the video re "ubuntu is facing down" would lead to a walking away.
[17:54] <cjwatson> infinity: yeah, quite
[17:54] <cjwatson> slangasek: was that https://lists.debian.org/debian-user/2013/11/msg00410.html ?
[17:54] <slangasek> cjwatson: yeah
[17:54] <slangasek> wait
[17:54] <slangasek> cjwatson: no
[17:55] <cjwatson> (my "more or less well-intentioned" comment is not intended as a defence BTW; regardless of intention this person is currently wasting people's time and IMO needs to shape up or ship out)
[17:55] <slangasek> cjwatson: https://lists.debian.org/debian-devel/2014/04/msg00319.html
[17:56] <nacc> the most annoying thing to me, is he sets the priority of bugs (which results in an e-mail) without ever (afaict) actually fixing anything. And the priority hover text claims to be about when bugs will get fixed
[17:57] <nacc> so it ends up lying to users about when to expect a fix
[17:57] <cjwatson> slangasek: whee
[17:57] <gsilvapt> I can't stand his name or email address anymore, oh lord
[17:57] <gsilvapt> It's decided, I'll gather these links and send them to the CC, wxl
[18:09] <gsilvapt> When running dpkg-buildpackage -S -nc -d it returns clearsign failed: "No secret key"
[18:09] <gsilvapt> Any help?
[18:09] <nacc> gsilvapt: did you insert a changelog entry?
[18:10] <nacc> gsilvapt: you can't sign a package with a changelog entry for a different user -- you can pass -us -uc to not sign the .dsc and .changes files
[18:11] <gsilvapt> Hum, I thought it was because of that. I didn't write anything because the log is not changed since 2016. Not sure if I should or not write something
[18:11] <nacc> gsilvapt: are you making a change?
[18:12] <gsilvapt> editing the man pages to remove the hyphens
[18:13] <nacc> gsilvapt: then you need to add a changelog entry :)
[18:13] <nacc> gsilvapt: dch -i
[18:13] <gsilvapt> Okay, I'm in the changelog file. Lets see if I don't mess this one up
[18:13] <nacc> gsilvapt: i would recommend using dch
[18:13] <nacc> gsilvapt: as inserting by hand can be error-prone
[18:14] <gsilvapt> yes, I used that command
[18:14] <gsilvapt> I had it before in the step-by-step guide you sent over
[18:14] <nacc> gsilvapt: ack, ok
[18:14] <gsilvapt> Now, I'm afraid I have no clue about the software version, lol
[18:15] <nacc> gsilvapt: `dch -i` should have done the right thing already
[18:15] <gsilvapt> The LP is confusing, the github page is only upstream
[18:15] <nacc> gsilvapt: what is the prior version in the srcpkg?
[18:16] <gsilvapt> is there a command to check that? I have no clue where/how to find it
[18:16] <nacc> gsilvapt: just look in the changelog?
=== fossfreedom_ is now known as fossfreedom
[18:17] <nacc> gsilvapt: it will be the one just below what you're entering
[18:17] <gsilvapt> 1:4.2-3.2Ubuntu1 yakkety
[18:17] <gsilvapt> Right, I froze there because there are no entries since september
[18:18] <nacc> gsilvapt: what release are you trying to work on?
[18:18] <gsilvapt> Viviv
[18:19] <nacc> gsilvapt: vivid??
[18:19] <nacc> gsilvapt: vivid is eol
[18:19] <nacc> sarnold: ping -- i just saw your shadow update went out for y and z but not a (per rmadison)?
[18:19] <nacc> sarnold: so a is behind z now
[18:19] <gsilvapt> Wait, not vivid. Should be artful
[18:19] <nacc> sarnold: is that a latency thing?
[18:20] <sarnold> nacc: two pronged -- (a) I don't have upload privs to -devel, only released releases (b) since they're fixed in debian, a merge from debian would handle that well
[18:21] <nacc> sarnold: sure, just wasn't sure if it's what was expected
[18:21] <nacc> sarnold: and  means gsilvapt's artful upload is missing context that will be dropped on the next update
[18:21] <nacc> sarnold: but it's ok
[18:21] <sarnold> nacc: :(
[18:21] <nacc> sarnold: and (a), understood, makes sense
[18:22] <nacc> gsilvapt: ok, so for artful, since it's in development
[18:23] <nacc> gsilvapt: your version will be 1:4.2-3.2ubuntu2. But note that it is probably better to wait for a merge
[18:23] <nacc> gsilvapt: as i think the merge will pick up the thing you want to backport anyways, right? (bumps upstream version to 4.4)
[18:23] <gsilvapt> When they merge with upstream, the man pages will be fixed. So yes, I believe the answer is yes
[18:24] <nacc> gsilvapt: to be clear, not just upstream, but specfically 4.4
[18:24] <gsilvapt> Only upstream has this fix, as far as I could see
[18:24] <nacc> gsilvapt: in a released version?
[18:25] <gsilvapt> Nor Ubuntu or Debian had this fix yet but it was fixed in November last year upstream
[18:25] <gsilvapt> Not sure if it is in a released version, apparently not, nacc.
[18:25] <nacc> gsilvapt: how have you checked?
[18:26] <nacc> gsilvapt: oh i see 4.4 is from september, but the fix was in november?
[18:26] <nacc> gsilvapt: ok so it won't be fixed by the merge, got it
[18:26] <nacc> gsilvapt: merge is not with upstream, but with debian
[18:26] <nacc> gsilvapt: and debian is at 4.4
[18:26] <gsilvapt> Wait, you're way over my head :D
[18:26] <nacc> gsilvapt: i'll start over
[18:27] <gsilvapt> Lets recap: I've recreated the bug in my system and it confirmed. I download all source deos from Debian and Ubuntu and neither have the fix. The upstream source has the fix, made in November last year.
[18:27] <nacc> gsilvapt: what i'm trying to understand is if this particular change you've found from upstream is present in the version packaged in Debian right now
[18:27] <nacc> gsilvapt: and an ubuntu merge is merging with debian, not with upstream
[18:27] <gsilvapt> s/deos/packages
[18:27] <nacc> gsilvapt: so, back to your srcpkg
[18:27] <nacc> your veresion will be what i said before
[18:28] <nacc> and insert an appropriate chagnelog entry
[18:28] <nacc> target it for artful
[18:28] <nacc> then dpkg-buildpackage should work, it will try to sign it with gpg
[18:29] <gsilvapt> But shouldn't I wait for a merge? Or because it is not in a debian release there is no use in that?
[18:30] <nacc> gsilvapt: right, unless debian is also planning on bumping it's version, a merge doesn't help
[18:30] <nacc> gsilvapt: but that's gated by an upstream release anyways
[18:30] <nacc> gsilvapt: we can do multiple merges too
[18:31] <gsilvapt> Okay, I think I understood. Thanks! I'll give it a try to, at least, finish the first fix I made
[18:31] <nacc> gsilvapt: sounds good, feel free to ping if you want a review
[18:33] <gsilvapt> I have to do dpkg-buildpackage before doing that, right, nacc?
[18:34] <gsilvapt> Ahum... Invalid user id :D
[18:35]  * gsilvapt faceplam
[18:35] <gsilvapt> Did the entry, forgot to add details for gpg
[18:40] <gsilvapt> I think I've broken the changelog... Oh dear me
[18:48] <gsilvapt> nacc, how do I ask for review?
[18:48] <gsilvapt> Post it anyways in LP bug report or is there another way?
[18:51] <nacc> gsilvapt: from me or generally?
[18:52] <gsilvapt> I understood you were going to do it but if you're too busy I can request a general review. After all, that's the right process, isn't it?
[18:56] <nacc> gsilvapt: yeah, so upload a debdiff to the bug and subscribe ubuntu-sponsors
[18:59] <gsilvapt> Okay, thanks, nacc
[18:59] <gsilvapt> I think I've done it right: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1427807
[18:59] <ubottu> Launchpad bug 1427807 in shadow (Ubuntu) "usermod's man refers to --*-sub-uids but accepts only --*-subuids" [Medium,Fix committed]
[19:07] <nacc> gsilvapt: i don't think 'fix committed' is right
[19:07] <nacc> gsilvapt: notyour  fault
[19:08] <nacc> gsilvapt: ok, few things i see with https://launchpadlibrarian.net/318864267/remove-extra-hyphens-as-LP427807-suggests%2A
[19:08] <nacc> gsilvapt: lots of trailing newlines in the changelog entry
[19:08] <nacc> gsilvapt: it's not targetting a release (UNRELEASED rather than artful)
[19:08] <nacc> gsilvapt: you made it 1:4.2-3.2ubuntu3 rather than ubuntu2
[19:08] <nacc> gsilvapt: and you changed an unrelated chagnelog entry
[19:09] <nacc> gsilvapt: finally there is no content to debdiff, that's just the changelog changes :)
[19:28] <rbasak> slashd: thanks for the ping. Sorry, it keeps being bumped by things :-/
[19:29] <rbasak> slashd: it's been long enough now I'll add it to my list of immediate highlighted todos.
[19:29] <rbasak> It had almost fell off the page :-/
[19:53] <slashd> rbasak, no problem thanks for looking at it
[20:42] <slangasek> gsilvapt, wxl, jbicha: when all is said and done, is someone reverting the changes on https://help.ubuntu.com/community/ReportingBugs, or...?
[20:43] <wxl> slangasek: bdmurray asked that same question on the mailing list, so i take it he's leading the charge
[20:43] <slangasek> wxl: I bet he, like I, was trying to get somebody else to do it ;)
[20:44] <bdmurray> Honestly, I'm not happy with either version but sorting it out isn't a high priority yet.
[20:45] <jbicha> I defer to bdmurray :)
=== manjo` is now known as manjo
[22:23] <gsilvapt> oh, so I need to work a lot on those. The UNRELEASED entry is not mine, or is it?
[22:26] <gsilvapt> nacc, first and foremost, thank you for the time reviewing this. Loads of lessons are being learned thanks to you!
[22:27] <gsilvapt> is there a way to cancel that commit so that I can start over? It somehow feels more adequate, considering I did changes to unrelated entries that I didn't even realize :|
[22:29] <infinity> gsilvapt: rm -r shadow-4.2 ; dpkg-source -x shadow_4.2-3.2ubuntu1.dsc
[22:29] <infinity> ginggs: And try again from there.
[22:29] <infinity> gsilvapt: ^
[22:29] <infinity> ginggs: Tab completion fail, ignore me.
[22:29] <gsilvapt> will give that a try. Thanks, infinity
[22:29] <infinity> gsilvapt: Also, "Do the stuff bug #foo requests" isn't a useful changelog entry.
[22:30] <infinity> gsilvapt: You want something more like "foo.xml: Correct type in --switch-thing docs (LP: #12356)"
[22:30] <ubottu> Launchpad bug 8012 in linux-source-2.6.15 (Ubuntu) "duplicate for #12356 other devices (sound, wireless?) fail to work when lp/parport modules are loaded due to IRQ conflict" [High,Fix released] https://launchpad.net/bugs/8012
[22:31] <Unit193> type → typo
[22:31] <infinity> gsilvapt: Changelogs should document the changes done, not just document that "some change" was done. ;)
[22:31] <infinity> Unit193: That's the one problem you had with that? ;)
[22:31] <gsilvapt> Hum, it makes sense. Thanks!
[22:31] <Unit193> infinity: Well that's the issue that jumped out at me enough to fix! :P
[22:31] <gsilvapt> I'll try to do it again
[22:31] <infinity> ;)
[22:33] <infinity> gsilvapt: If you're ever use Windows and been frustrated by the fact that literally every Windows Update changelog entry is "Update Product: see KB123456", you'll understand why some people prefer changelogs to actually have useful information.
[22:33] <gsilvapt> Yes, I understand. Was in a hurry at the time and did a poor job :)
[22:33] <gsilvapt> Sorry. I'm starting over now
[22:43] <gsilvapt> Creating the changelog entry is actually really difficult
[22:44] <gsilvapt> I think I know how/why I deleted/changed an entry without even realizing it
[22:44] <gsilvapt> when doing dpkg-source --commit and after entering the patch name, it opens a menu with some info to fill in. Can/Should you remove anything in that file aside from those you have to actually edit?
[22:46] <gsilvapt> infinity ^ (I keep forgetting to reference the people I'm calling out :D )
[22:47] <infinity> gsilvapt: Creating the changelog entry should be a simple matter of calling "dch -i"
[22:48] <infinity> gsilvapt: As for the patch headers, you should keep the relevant ones and delete the ones that don't make sense for your patch, yes.
[22:49] <nacc> gsilvapt: i'm around again
[22:49] <nacc> gsilvapt: yes, by default `dch -i` inserts an UNRELEASED entry
[22:49] <nacc> i believe i said earlier, you need to mark it for artful
[22:51] <nacc> rbalint: did you see my comment in the systemd bug? as to whether or not it's correct to never allow systemd-remount-fs.service to run in containers?
[22:51] <nacc> rbalint: as i think there are advanced container configurations that use real disks
[22:51] <nacc> rbalint: where we do want to remount them to match fstab
[23:07] <rbalint> nacc: yes, but one can easily override the stock .service file
[23:10] <rbalint> nacc: i see no clean solution here :-(
[23:10] <nacc> rbalint: yeah, neither do I, but we'd need to document that in the 17.04 release notes, i think, as it's a change in behavior
[23:10] <nacc> rbalint: if we decided to go that route, i mean
[23:14] <rbalint> nacc: one other not too clean option is diverting /lib/systemd/systemd-remount-fs in image generation to check "mount -f /" before actually doing the remount and reporting success when  "mount -f /"  fails
[23:15] <rbalint> nacc: quite ugly, but if there is a working / in fstab it gets remounted
[23:16] <nacc> rbalint: yeah -- nothing is great. I was just reading `man systemd-remount-fs` and it indicates more than just / is handled by it (all kernel virtual fs, e.g.)
[23:16] <nacc> rbalint: and specifically /usr for some reason
[23:18] <nacc> cpaelzer: just to be sure, your lvm2 upload to zesty of 2.02.167-1ubuntu5, that was because ubuntu4 was accidentally uploaded?
[23:24] <rbalint> nacc: those mount points are typically set up properly in containers
[23:24] <infinity> nacc: Why do people have containers with bogus info in /etc/fstab to begin with?
[23:27] <nacc> infinity: cloud-image generation
[23:27] <nacc> rbalint: i agree, they should be -- i just don't want to break anyone :))
[23:27] <nacc> rbalint: if you're confident in the change, i'm cool with it, tbh
[23:27] <infinity> nacc: fstab(5) isn't a random dumping ground for garbage, it's a list of filesystems that the system *can* mount successfully, and the onus is on the sysadmin to make sure it's accurate (or on the image creator, if you're creating bogus ones out of the gate).
[23:27] <rbalint> infinity: some ubuntu container images are preset with fstab containing LABEL=cloudimg-rootfs : LP: #1576341
[23:27] <ubottu> Launchpad bug 1576341 in open-iscsi (Ubuntu) "systemd in degraded state on startup in LXD containers" [High,In progress] https://launchpad.net/bugs/1576341
[23:27] <nacc> infinity: CPC image generation that is :)
[23:27] <nacc> infinity: it's hardcoded in the CPC code
[23:28] <infinity> Code can change. :P
[23:28] <nacc> infinity: yeah, i have a note in there to figure that out
[23:28] <nacc> infinity: i think it's needed for VMs, possibly
[23:28] <nacc> infinity: but in containers it doesnt make sense
[23:28] <infinity> I'm just saying systemd isn't buggy here.  Perhaps a bit overzealous, but it's not a bug to assume entries in fstab should be mountable.
[23:28] <nacc> infinity: agree, and i wasn't suggesting to fix systemd in my original request
[23:28] <nacc> more that we needed to understand the issue and figure out the 'right fix'
[23:29] <nacc> Odd_Bloke: rcj: --^ you may have input on the above too
[23:30] <rbalint> infinity: if  generating separate container and vm images for cloud would be an option then we could go that way
=== Guest7204 is now known as RAOF
[23:41] <rbalint> nacc: maybe adding the diversion to only remount working / would be better, let's collect some feedback on the various options
[23:42] <nacc> rbalint: ack, i'd like to hear from CPC too
[23:44] <infinity> rbalint: Is it really "the same image"?
[23:44] <infinity> rbalint: On cloud-images dailies, I see a -lxd.tar.gz, which would imply otherwise.
[23:45] <infinity> Oh, that's also only 848 bytes. :P
[23:45] <rbalint> infinity: definitely different :-)
[23:46] <infinity> Well.  That appears to be metadata about mangling/overwriting files.
[23:46] <infinity> So, if could also whack fstab.
[23:46] <nacc> infinity: oh that's a good point
[23:46] <nacc> so maybe stgraber *is* the one to ask :)
[23:55] <infinity> nacc: If official lxd images are our only concern, I think that's the right place to fix it.  If we want people to download our generic cloud images and run them in "any container" without that metadata mangling, a first-boot job that accomplishes the same thing would also be sane.
[23:55] <infinity> nacc: Which would need to run early enough that it gets there before systemd-remount-fs, obviously.
[23:56] <rbalint> infinity: the image i got with the lxc command seems to be built with livecd-rootfs:
[23:56] <rbalint> root@unified-ox:~# cat /etc/init/ttyS0.conf  | grep Cloud
[23:56] <rbalint> # CLOUD_IMG: This file was created/modified by the Cloud Image build process
[23:57] <rbalint> infinity: but yes, probably it was post-processed
[23:58] <rbalint> infinity: how do you feel about the local diversion?
[23:59] <rbalint> infinity: "fstab(5) : stab is only read by programs, and not written;" :-)