/srv/irclogs.ubuntu.com/2017/08/14/#ubuntu-server.txt

cpaelzergood morning05:38
enick_997good morning07:11
cpaelzerhi enick_99707:28
cpaelzergood mornign to you as well07:28
cpaelzerrbasak: on the virt-manger merge https://code.launchpad.net/~paelzer/ubuntu/+source/virt-manager/+git/virt-manager/+merge/328824 you already commented a bit in IRC07:28
cpaelzerrbasak: I made the reason to not drop the gir1 dependency explicitly mentioned in the MP07:29
cpaelzerrbasak: I also have good user feedback on the ppa07:29
cpaelzerrbasak: if you could afford a few minutes to review for formal or overlooked issues this morning that would be great07:29
=== enick_997 is now known as lordievader
lordievaderThis nick is better :)07:50
lordievaderHey cpaelzer, how are you doing?07:50
cpaelzergood07:54
cpaelzerI almost thought somebody other than us would care about a good morning at this time reading the other nick name :-)07:54
lordievaderYeah, the matrix-irc bridge had a restart. Changes nicks. But for me that is not allways obvious that it happened.07:55
rbasakahasenack: so I'm about to start looking at https://code.launchpad.net/~paelzer/ubuntu/+source/virt-manager/+git/virt-manager/+merge/328824 for cpaelzer. Should I be clicking "Claim review" against either of the two requested reviewers?11:08
cpaelzerrbasak: yes11:56
cpaelzerrbasak: in this case the MOTU is for the actual review by a group that could sponsor11:56
cpaelzerrbasak: and the generic server team is to have it on the active reviews list11:56
cpaelzerrbasak: you can only take one, but that is fine - doesn't matter to much which one you claim11:57
cpaelzerahasenack: or did we agree already which of the two we take?11:57
cpaelzerrbasak: and finally - thanks rbasak for looking into that11:57
rbasakPresumably I should claim the MOTU one, so the ~canonical-server one remains, so we can see all outstanding requests still in ~canonical-server's active reviews queue?11:58
cpaelzerrbasak: I'd think vice versa11:59
cpaelzerrbasak: claim the one on the team - because then on the overview it is visible that one took a look11:59
cpaelzerI think if you approve/deny/comment those will be counted no matter from which review slot they come from12:00
cpaelzerso it isn't too important12:00
cpaelzerI'll look in the samba or bind one so that andreas can also be unblocked12:00
cpaelzerbut samba is "take 4" maybe there is too much history on that already by whoever reviewed before12:00
ahasenackrbasak: yes, please claim the motu one12:05
ahasenackas unclaimed reviews requested from that group won't appear in the ~canonical-server queue12:05
ahasenackand good morning :)12:05
cpaelzerhi andol12:06
cpaelzerstill hi andol, but I actually meant ahasenack - hi12:06
ahasenackhi cpaelzer12:07
cpaelzerahasenack: I try to digest "unclaimed reviews requested from that group won't appear in the ~canonical-server queue" - so reviews that have MOTU + Server team and are unclaimed in both do not show up on the active reviews?12:08
ahasenackcpaelzer: no, that's not it12:08
cpaelzergood because that sentence puzzled me12:09
ahasenackcpaelzer: if an MP has only non-canonical-server requests, it won't shoud up in ~canonical-serve12:09
cpaelzerack12:09
ahasenackthe only way for it to keep appearing in the canonical-server queue is for there to be an unclaimed slot for canonical-server12:09
cpaelzerbut if it has (canonical-server = c-s) c-s-motu and c-s then why claim c-s-motu preferrably?12:10
cpaelzerwill it not go away from he c-s list when you only claim c-s-motu ?12:10
ahasenackif you claim c-s, it will disappear from the queue and we won't see it. It's a visibility thing12:10
cpaelzerso the rule is more or less to never anybody claim c-s (only there for visibility)12:11
cpaelzer?12:11
ahasenackyes12:11
cpaelzerthanks for clarification12:11
ahasenackdoesn't mean a c-s person cannot review it, I'd say that's encouraged even12:11
ahasenackjust never claim the slot, or give a +1 or -112:11
ahasenackjust "comment"12:11
ahasenackunfortunately12:11
rbasakcpaelzer: AIUI, the sole reason we have a review slot for c-s is because ahasenack wanted a single place to see all pending MPs. So we're using it as a tag really, rather than a review slot.12:11
ahasenackyeah, it's a workaround12:11
ahasenackI filed a bug in launchpad about it12:12
* rbasak claims the MOTU slot in https://code.launchpad.net/~paelzer/ubuntu/+source/virt-manager/+git/virt-manager/+merge/32882412:12
ahasenackI would like the same view for ~team/+activereviews that already exists for <project>/+activereviews12:12
rbasakThank you (both) for the clarification/discussion.12:12
ahasenacklet's give it a try, and re-evaluate12:12
cpaelzerahasenack: I want to unblock you as well - which one would you like me to take a look more - bind or samba ?12:13
ahasenackcpaelzer: can you upload either?12:13
ahasenackmdeslaur manifested interest in the bind one12:13
ahasenackoh, nacc grabbed the bind9 uploader slot12:14
ahasenackhm, the "claims" don't show up in the +activereviews page either12:14
cpaelzerahasenack: can't upload either until the DMB aggrees12:14
cpaelzer-g12:15
ahasenackcpaelzer: I think samba might be the most confusing one, because of a reverse patch that was incomplete. Might be the most enlightening one for that reason, though12:15
ahasenackcpaelzer: bind is interesting because I split two debian patches to remove test cases from them and make them individual new patches12:16
ahasenackcpaelzer: ssd-krb5 is an sru, and a very simple one, would be cool to get that unblocked12:17
cpaelzerthen lets start there12:17
cpaelzerlow hanging foul fruits and such :-)12:17
cpaelzerand I at least somewhat looked in that soruce before12:17
ahasenackhaha, great analogy :)12:19
cpaelzerahasenack: does the ppa of this still lvie somehwere?12:26
ahasenackcpaelzer: it should12:26
ahasenackcpaelzer: ppa:ahasenack/ssd-krb5-locator-path-1664566 ?12:26
cpaelzerno link in the bug or MP12:26
cpaelzerthanks12:27
cpaelzerah in the mp description it is12:27
ahasenackit's hidden in the test case, let me make that more clear12:27
cpaelzerahasenack: I'm done with the sssd review - all good, one spin off question in the MP12:45
ahasenackok, will check12:45
cpaelzerahasenack: since I can't tag do you mind loosing the rich history on that minimal change?12:45
cpaelzerahasenack: otherwise I'd sponsor12:45
ahasenackcpaelzer: go for it, I don't mind12:45
cpaelzerahasenack: done and bug updated12:51
cpaelzerand MP12:51
ahasenackthanks cpaelzer12:51
cpaelzerahasenack: do you claim the team review slot so it goes away on the active reviews?12:51
cpaelzerI can't take two12:51
ahasenackinteresting12:51
ahasenackI hadn't thought about this case :)12:51
ahasenackwill do12:52
ahasenackcpaelzer: about your MP comment, you mean that the directory from the libkrb5 package exists, and supposedly is meant for plugins, and is now empty?12:59
cpaelzerahasenack: yes13:00
ahasenackok13:00
cpaelzerahasenack: I just spun forward the thought if the dir is wrong as well13:00
cpaelzerahasenack: but it is not from sssd packages but krb5 itself13:00
ahasenackit may be dedicated to plugins coming from the krb5 package itself, like its ldap backend13:00
ahasenacklet me try installing all binaries13:00
ahasenackyes13:00
cpaelzerlet me apt-file that13:00
ahasenackgood idea13:01
cpaelzerno ither hit but for the sssd-common file13:01
cpaelzerso at least no other pkg places anything there today13:02
ahasenackxenial?13:02
cpaelzeryes13:02
cpaelzerahasenack: artful as well13:04
ahasenackplugins/kdb has content, plugins/tls has content13:05
ahasenackjust not plugins/krb513:05
cpaelzerahasenack: apt-file can only ifnd files, so this only tells us that there is no file in the archive that uses this path13:05
cpaelzerahasenack: it seems to me that after your fix /usr/lib/x86_64-linux-gnu/krb5/plugins/krb5/ is an empty wasteland13:06
cpaelzerand my uneducated guess was that it might be the case that it (the path) shouldn't exist at all13:06
cpaelzerthats all I can say13:07
cpaelzerand that is is unused over the entirety of the archive other than the wrong path in sssd-common seems to confirm13:07
ahasenackso far I found only this on mit's site:13:07
ahasenackPlugin base directoryLIBDIR/krb5/plugins13:07
cpaelzeralthough one would have to look (deep) in krb513:07
ahasenackafter installing a few more plugin packages, they seem to create their own subdirectories13:08
cpaelzer-e "s\"@MODULEDIR\"/usr/lib/x86_64-linux-gnu/krb5/plugins\""13:08
cpaelzerthat is from the build13:08
ahasenackmaybe there just doesn't exist a krb5 plugin yet, whatever that means. Sounds client-side13:08
cpaelzerbut if it would take from "anywhere" in there then ...plugins/krb5 and ...plugins/libkrb5 wouldn't makea a difference in your fix13:09
cpaelzermaybe worth a mail to Debian and/or upstream krb?13:10
cpaelzernot entriely sue since this came up as "guess" I don't feel convinced enough to ring a lot of bells and whistles13:10
cpaelzerrbasak: thanks for the review - would you mind tagging this before I upload?13:12
cpaelzerthis is a rich history that helps to be preserved for next time13:12
cpaelzers/helpswould be useful/13:13
ahasenackcpaelzer: checking this comment: "You're right, running 'strings /usr/lib/../libkrb5.so.3|grep plugins' shows that it's ../krb5/plugins/libkrb5. For some reason I changed it to plugins/krb5 some years ago, without a bug reference.."13:13
rbasakcpaelzer: of course. Sorry I had forgotten that.13:13
cpaelzerPEBKAC error in my typing :-/13:13
cpaelzerahasenack: where is that comment?13:13
cpaelzerin the bug that ws fixed?13:14
ahasenackcpaelzer: comment #2 in https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/166456613:14
ubottuLaunchpad bug 1664566 in sssd (Ubuntu Xenial) "sssd_krb5_locator_plugin.so is not loaded (installed at wrong path)" [Medium,In progress]13:14
ahasenackfunny that there are two major libkrb5 files13:14
ahasenack.so.26 and .so.313:14
cpaelzeryep13:14
cpaelzerI saw that, well sover compat and it seems krb5 can build both so helps the old dependencies13:14
ahasenackoh, .26 is from heimdal13:14
cpaelzeruh - ok13:14
ahasenacka whole lot of stuff links against heimdal13:15
ahasenackapt-transport-https, reportbug, curl, to name a few interesting ones13:15
rbasakcpaelzer: hitting a few bugs in "git ubuntu tag --upload" - I may be a few minutes.13:16
cpaelzerrbasak: ok, please ping me once it is done or if you give up the immediate try13:16
rbasakack13:16
rbasakcpaelzer: upload tag pushed13:20
cpaelzerrbasak: and on the format of merge-bug closing I already have an improved style for multiple fixes due to a merge - let me make a pastebin to show you13:20
cpaelzerrbasak: thanks13:20
cpaelzerrbasak: http://paste.ubuntu.com/25312255/13:21
cpaelzerrbasak: you are right there is no policy, but this is my personal new oen for now13:21
cpaelzerfor better readability13:21
cpaelzerIt also easens to take over the line if a change is "remaining" on the next merge13:21
rbasakcpaelzer: I like it13:21
ahasenackcpaelzer: libkrb5 is definitely the correct directory for krb5 plugins,13:27
ahasenack./src/lib/krb5/os/locate_kdc.c:static const char *objdirs[] = { LIBDIR "/krb5/plugins/libkrb5", NULL };13:27
ahasenackthe bug was just an incorrect assumption from sssd13:27
ahasenackwhich seems to be the only libkrb5 plugin we have13:27
ahasenackcpaelzer: debian/libkrb5-3.dirs.in in the krb5 source package lists the incorrect plugins/krb5 directory13:29
ahasenackthat's the bug (task) we need now?13:29
ahasenackto fix that?13:29
cpaelzerahasenack: I would not mind to fix that in any SRU13:30
cpaelzerahasenack: nor for Debian delta13:30
cpaelzerbut a simple patch to Debian would be nice13:30
ahasenacklet me check the debian status13:31
cpaelzerand link the Debian bug on the bug you had13:31
cpaelzerso one can find the whole context in one place13:31
cpaelzerjust checking if that comes fromd debian/* or from the upstream build system13:32
cpaelzerrbasak: I checked on your correct request for a tracker WRT the package names in virt-manager13:35
cpaelzerrbasak: "libvirtd" is the correct service name since Yakkety - so that is a no-op and we don't want a change13:35
cpaelzerrbasak: I'll submit something upstream that fixes this now and forever13:35
cpaelzerrbasak: dropping the need to make this proper names for every dirsto (there might be more differences)13:36
rbasakcpaelzer: ah, OK. I hadn't really considered the service name message. I was thinking more of the message listing the package names that needed installing.13:36
rbasakcpaelzer: but I didn't really think too hard about it. As long as a bug exists for anything you think you dropped that would be nice to upstream (to Debian or upstream upstream), I'm happy :)13:37
cpaelzerI think it is wrong to call it "package X" which leads to all this13:38
cpaelzerand will propose something saying th packages containing kvm, qemu, ...13:38
cpaelzerthat way it applies to all distros13:38
rbasakThat is less helpful to users though, who mostly don't know how to look up what package provides a particular command.13:39
cpaelzerhmm, true as well13:39
cpaelzer\ | / - ... processing13:40
rbasakBut a distro delta is also bad13:40
rbasakSo I don't really know what a great solution would be.13:40
cpaelzerI check if the configure has any distro detect already13:40
rbasakA hook into command-not-found perhaps?13:40
rbasakBut that's probably not worth the effort.13:40
cpaelzerall but a simple change is over engineering13:40
cpaelzergive me a few minutes13:40
rbasakYeah :)13:40
rbasakI'm fine for you to just leave a bug open on it somewhere, importance wishlist, and call it done :)13:41
cpaelzerrbasak: my soul wants things done not tracked :-)13:41
cpaelzerbut yeah I might end up that way13:41
cpaelzerrbasak: I have a whishlist bug to track but also a submission to upstream now14:10
cpaelzercoldn#t leave it like that14:10
rbasakcpaelzer: thank you!14:11
cpaelzerahasenack: thanks for the debian bug on the cleanup14:17
ahasenacko/14:22
ahasenackit feels good to have everything explained14:22
ahasenackrbasak: hi, could you please import cifs-utils?14:27
rbasakahasenack: running14:31
rbasakHmm. It failed very quickly.14:31
rbasakI think it's a regression in master. Going back a bit in the state of the repo works.14:34
rbasakBut nacc isn't here right now.14:34
rbasakRunning with an older importer version14:35
ahasenackrbasak: could be, I'm getting a weird error with merge start:14:37
ahasenack(ubuntu/devel)andreas@nsn7:~/git/packages/cyrus-sasl2$ git ubuntu merge start ubuntu/devel14:37
ahasenack08/14/2017 11:36:54 - ERROR:ubuntu/devel is not a defined object in this git repository.14:37
ahasenackwe need unit tests :/14:37
rbasakahasenack: that's a separate regression I found earlier and I have an MP fixing it awaiting nacc's review.14:37
rbasakahasenack: we're busy polishing up the code so it can be testable. That's what's causing the regressions right now. It'll get better soon.14:37
ahasenacknice14:40
rbasakahasenack: done14:53
ahasenackrbasak: thx14:53
ahasenacklet me try to revert to the previous snap14:53
ahasenackrbasak: the snap seems a bit busted now, or the store15:03
ahasenack$ snap install git-ubuntu --classic15:03
ahasenackerror: cannot perform the following tasks:15:03
ahasenack- Download snap "git-ubuntu" (117) from channel "stable" (received an unexpected http response code (404) when trying to download https://api.snapcraft.io/api/v1/snaps/download/VAGSRAriUyDDlqsLunShJTe7503Uw4GF_117.snap)15:03
hypermistim getting a grep: broken pipe error when running a certain python file anyone able to help ?15:29
ahasenacknacc: rbasak: git ubuntu clone (r119) working again, but it spits out this fatal-not-fatal error at the end15:37
ahasenackfatal: remote error: Repository '~ahasenack/ubuntu/+source/cifs-utils' not found.15:37
ahasenack$? is 0 at least15:38
ahasenacknacc: wrt snap error, snap logout;snap login to fix it15:38
naccahasenack: that's a message when it can't find your personal repo15:38
naccahasenack: that's propogated directly from `git clone`-like output15:38
naccahasenack: i agree it's a bit messy15:38
ahasenackyep, no biggie15:39
naccahasenack: fyi, 121 is out :)15:40
ahasenackyay15:40
nacc(artful based snap)15:40
drab.o/ moin15:58
ahasenacknacc: rbasak: known? http://pastebin.ubuntu.com/25313513/ ValueError: ubuntu/devel17:44
ahasenacksnap r12217:44
naccahasenack: thanks, fixing, one sec17:45
naccahasenack: fix pushed to master, triggered a snap build, sorry abou thtat17:50
ahasenackthx17:50
ahasenacknacc: r126 still fails, your last push is newer?17:53
naccahasenack: yeah, give it a bit17:54
ahasenackok17:54
naccahasenack: 129 should be avail.17:58
naccahasenack: 130 even17:58
=== JanC is now known as Guest47969
=== JanC_ is now known as JanC
* ahasenack refrehes17:58
ahasenackinteresting, the download is slower now17:59
ahasenackmaybe a cold cache17:59
ahasenack5min eta17:59
naccahasenack: if i had to guess cyrus-sasl2 can be syncd18:00
naccahasenack: the delta is a backport from upstream18:01
ahasenackwe have a patch18:01
naccahasenack: ?18:01
ahasenackthe patch we have comes from upstream, not debian18:01
naccahasenack: right.18:01
naccoh i see, i though it was a new upstream version18:01
ahasenackno, the upstream change is barely worth it18:01
naccahasenack: not really important to merge that18:02
ahasenacksorry, s/upstream/debian/18:02
ahasenackI'm doing it for the exercise18:02
naccahasenack: there are more importnat merges, i mean :)18:02
naccack18:02
ahasenackfirst time in my life git rebase new/debian completed on its own18:02
=== Epx998- is now known as Epx998
ahasenacknacc: in which step do you adjust the indentation of the d/changelog lines: deconstruct, logical, or when rebasing on new/debian? Or something else?18:06
ahasenackfor a remaining change, for example18:06
ahasenackd/changelog has it as a *18:06
ahasenackI'd guess new/debian rebase18:08
naccahasenack: meaning something that was new before, but is now part of remaining?18:09
naccahasenack: yeah, i usually do the adjustment in the rebase to new/debian18:09
ahasenackyes18:09
ahasenackk18:09
ahasenacknacc: got a lint backtrace: http://pastebin.ubuntu.com/25313636/ NameError: name 'treeish' is not defined18:13
ahasenackthat was after i created a branch from my detached head18:13
ahasenackthat sentence sounds funny18:13
naccahasenack: thanks, fixing and pushing, give it about 5 minutes for the snap to build & publish18:19
ahasenackok18:19
ahasenacknacc: I'm seeing other "new" errors, maybe not fatal18:21
ahasenacknacc: http://pastebin.ubuntu.com/25313688/ in merge start:18:21
ahasenack"08/14/2017 15:20:15 - ERROR:ubuntu/devel version (2:6.6-5ubuntu1) is after debian/sid version (None). Are you sure you want to merge? (Pass -f to force the merge)."18:21
ahasenackcifs-utils was just imported this morning by rbasak, and I think he had to revert to an older snap to do it18:21
ahasenackmaybe something failed and wasn't caught18:21
ahasenackor it's just a new harmless error18:21
ahasenacksince I do have a local debian/sid branch after that clone process finished18:22
naccahasenack: let me look18:22
ahasenackthat's with snap r13018:24
naccahasenack: fixing18:24
ahasenack:)18:24
ahasenacknacc: in snap r131, ubuntu lint broke differently: http://pastebin.ubuntu.com/25313712/ AttributeError: module 'enum' has no attribute 'IntFlag'18:27
ahasenackmaybe once this is stabilized we should start using the edge channel18:27
drabrandom question since snaps were mentioned... despite having tried to understand what's going on I still don't get when and why I'd want to use snaps18:28
drabis it just IoT stuff?18:28
ahasenackno18:28
drabsometimes it almost sounds like a dockerish thing for self-container deployments18:28
drabcontained*18:28
ahasenackthere are feature that appeal more to one group of people than the other, sure18:28
ahasenackone example: you have a software that you want to make available to ubuntu lts18:28
ahasenackyou have xenial and trusty18:28
ahasenackthese two have different versions of supporting libraries18:29
ahasenackyou would have different packages of your software for each probably18:29
ahasenackwith snaps, you can have just one snap for both18:29
ahasenackthink of the snap as being self-contained18:29
ahasenackalso, you push it to the store, and it's instantly available18:29
ahasenackwell, minus build time :)18:30
drabcan i run my own store to push things around local boxes?18:30
ahasenackI *think* yes18:30
ahasenackbetter check with #snappy18:30
drabmaybe becuase I'm used to it, but I'm thinking of them as "special" .debs with dependencies included and so I'm thinking "oh, run a local repo"18:30
ahasenackI'm not entirely sure about all aspects of the store18:30
drabbut maybe I'm off/stuck on a diff framework18:30
ahasenackyou can think of them as being some sort of "static" debs, if you want to compare with libraries and such18:31
ahasenackbut that's just one aspect of snaps18:31
ahasenackyou can easily rollback, for real18:31
ahasenackthat's another cool feature18:32
naccahasenack: grr, i see what's wong with lint, one sec18:32
drabah, so things are sort of installed in parallel? back in the days we used to do sw deployments installing from git and symlinking to current18:32
drabso that a rollback was just a re-link away18:32
drabpretty handy18:32
ahasenackdrab: you get common areas where to store your data, and versioned areas18:32
drabthat sounds pretty sweat18:32
dpb1drab: if that part is interesting, this page makes it nice a clear: https://snapcraft.io/docs/core/versions18:32
drabis there a substantial push from canonical to move to this kind of thing over debs?18:33
drabthanks dpb118:33
ahasenackdrab: you also have different distribution channels for your snap: stable, candidate, beta, edge18:33
naccahasenack: do you have the branch that's ailing to lint anywher?18:33
ahasenackby default people get stable, but they can pass flags to get more and more bleeding edge18:33
ahasenacknacc: let me check18:34
ahasenacknacc: let me push, lint was the last step before pushing18:34
drabyeah seems you can run your own store: https://github.com/noise/snapstore/18:34
drablinked from the docs dpb1 shared, looks useful18:34
naccahasenack: thx18:35
ahasenacknacc: I'm afraid now, last time the linter failed on a branch of mine it was because I did something silly :)18:35
ahasenacknacc: https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+ref/artful-sasl2-merge-171068418:35
ahasenackdrab: http://pastebin.ubuntu.com/25313769/18:36
dpb1drab: no effort that I know of to bring this kind of thing to debs, no.  But, debs aren't going anywhere, Canonical and Ubuntu continue to be built on debs, and even the first step many snaps do when building is to install debs to download versioned dependencies they need.18:36
ahasenackdrab: followed by http://pastebin.ubuntu.com/25313777/18:36
ahasenacknacc: fwiw, git ubuntu clone is also failing with that AttributeError18:38
ahasenackso not just the linter18:38
drabah, heh, same principle, good to know, I always liked that way of doing deployments, even if in some places we packged that into debs, the uidea remained the same, post-install scripts would change the symlinks etc18:38
naccahasenack: yeah i see why18:38
dpb1drab: btw, if you like information and have just a few minutes of time, https://snapcraft.io/ -- the tutorial linked off there is very nice having followed it myself a few months back.18:39
drabdpb1: will do so, thank you18:39
naccahasenack: the reason you're seeing this is i fixed the snap to actually use only the snap's internals18:39
* dpb1 takes off snap pushing hat.18:39
dpb1lol18:39
naccahasenack: so it's leading to some more nasty debugging18:39
drabheh18:39
ahasenackoh, we had a leak18:39
naccahasenack: yeah18:39
drabspeaking of time, I forgot to take the time to upload the csv for tomreyn...18:39
naccahasenack: and we have a mixed python env because of gbp (python2)18:39
* drab goes doing that18:39
naccahasenack: i *think* i fixed the snap python paths, building now18:51
naccahasenack: not sure why perl isn't getting put in the snap yet18:51
DammitJimis there a proper way to remove an upstart job?18:58
naccahasenack: i *think* the correct chnages have been pusehd for the two issues you hit, in r136, i'm testing it a bit now19:01
ahasenackok19:01
DammitJimactually, I might not need to do anything... I just upgraded from 14.04 to 16.04 and upstart just doesn't work19:02
DammitJimI guess I just need to create a new conf for systemd19:02
ahasenacknacc: clone and merge start worked19:03
ahasenacknacc: lint failed with AttributeError: 'GitUbuntuLint' object has no attribute 'pkg_remote_branch'19:04
ahasenackhttp://pastebin.ubuntu.com/25313927/ (r136)19:04
ahasenacknacc: ^19:04
naccahasenack: ok, have a fix for that queued19:05
drabtomreyn: dropped you a msg with the link to the csv stuff, lemme know19:08
naccahasenack: i think the lint issue is fixed (importer is still broken)19:40
ahasenackok19:40
ahasenacknacc: finding all the missing deps the hard way, huh19:41
nacc#!/usr/bin/python19:43
naccf.19:43
naccrbasak: suggestions for how to workaround gbp harcoding the path to python?19:43
nacci *think* that's why it's not working in the snap, but not 100% yet19:43
rbasaknacc: IMHO, that's up to snapcraft to patch. If it can't, then maybe that's something for the snappy forums?19:45
rbasakOr convince upstream to use /usr/bin/env?19:45
naccrbasak: classic snaps don't get that help :)19:49
tsgloveHello, I have a question: I want to create a user in my server, so a remote computer can connect to the server with that user, and rsync some files.     Yet I would like for this user (on the server-side) NOT to have a shell.19:51
tsgloveDoes rsync use the shell for its operations, or can I put the user's shell as /bin/false ?19:52
ahasenacknacc: hm, I got a silly situation where our delta is just different permissions in two files in debian/: http://pastebin.ubuntu.com/25314155/19:53
ahasenacknew/debian has postinst.in, prerm.in as 0755, we have those 064419:53
naccahasenack: is there a reason (from d/changelog) as to why they are different?19:54
ahasenackno19:54
naccahasenack: then you can probalby sync it19:54
ahasenackit's a silent change19:54
naccahasenack: i'd ping the person who introduced it,if you're not sure19:54
ahasenackit was introduced from 6.6-5 to 6.6-5ubuntu1:  -- Dave Chiluk <chiluk@ubuntu.com>  Tue, 03 May 2016 17:30:11 +000019:54
naccchiluk: --^ :)19:55
ahasenackchiluk: around?19:55
ahasenackthat 5ubuntu1 version is supposed to have introduced debian/patches/stat_systemd-ask-password.patch, but I didn't see that in the delta19:56
ahasenackchecking19:56
ahasenackoh, that patch was introduced in 201319:56
ahasenackn/m19:56
ahasenackok, so no sync19:56
sdezieltsglove: rsync needs a shell to function. As an alternative, if you don't need rsync specifically but only care about uploading files, you may want to try SFTP19:56
ahasenackit's just this deconstruct phase that got silly because of the chmoded files19:57
ahasenackso, what I said before, that our delta was just the chmod change, is not correct19:57
ahasenackthat is the change in the 5ubuntu1 merge19:57
ahasenackI guess I'll use "previously undocumented"19:57
tsglovesdeziel, true... sftp can very much work!  I just thought rsync because of familiarity.     So, question: if I create a user, and set the shell to /bin/false,   rsync will fail?19:58
sdezieltsglove: yes, rsync will fail if the user's shell is /bin/false19:58
tsglovesdeziel, ok thanks!  I'm reading up on sftp now.19:58
tsgloveI didn't know sftp ran over ssh19:58
sdezieltsglove: for sftp, you can even have the user chrooted to a given dir19:59
tsglovesdeziel, that would be ideal!  searching for that now19:59
ahasenacknacc: can you verify if the import of cifs-utils done earlier today is correct? I'm seeing some strange stuff20:01
naccahasenack: such as?20:01
ahasenackI know rbasak had to downgrade git-ubuntu to get it to work, but maybe there was some subtle error or bug20:01
ahasenacknacc: git status says debian/patches is untracked20:01
sdezieltsglove: http://paste.ubuntu.com/25314208/20:01
naccahasenack: untracked where?20:02
ahasenackwhen I rebase on old/debian20:02
ahasenackthat patch is a remaining change20:02
naccahasenack: debian/patches doesn't exist in debian/sid20:02
naccahasenack: so you'd need to `git add` it20:02
tsglovesdeziel, reading that now... and trying to figure it out.  Thank you!20:03
sdezieltsglove: np20:03
ahasenackI guess that's the case when there is only one patch20:04
ahasenackand debian had none20:04
ahasenackok20:05
chilukahasenack: here.. reading backscroll20:07
ahasenackchiluk: just a chmod 0644 in d/postinst.in and d/prerm.in, they are 0755 in debian20:08
ahasenackremember anything about that? It's an old change :)20:08
ahasenacknacc: linter is working again (r138)20:12
chilukahasenack: checking.20:12
ahasenackchiluk: I mean, no chmod command. Just that "a" chmod was run20:13
ahasenackin debian those files are 0755, in ubuntu they are 064420:13
ahasenackjust metadata change20:13
chiluk   - debian/patches/stat_systemd-ask-password.patch: also check for20:13
chiluk      /bin/systemd-ask-password before trying to use systemd's tools.20:13
chilukshould be a remaining change.20:13
chilukahasenack: I probably submitted-to-debian the changes.20:14
ahasenackok20:14
chilukahasenack: is it possible that the remaining change was merged into debian after our merge for zesty?20:14
ahasenacklet me check current20:14
ahasenackno, debian unstable still has them as 075520:15
ahasenackactually, 775 even20:15
chilukand I introduced this change?20:16
ahasenackI think so, I compared 6.6-5 with 6.6-5ubuntu120:17
naccahasenack: excellent20:17
ahasenackhm, I should check the previous ubuntu pkg20:18
chilukahasenack: that was back before I had upload permissions.. so that was a sponsored upload of this debdiff.20:18
chilukhttps://launchpadlibrarian.net/304461726/lp1660372.zesty.debdiff20:18
ahasenackyou are right, zesty has them 0644 already20:18
chilukI don't see where my debdiff would have futzed with the perms.20:19
ahasenacksorry20:19
tsglovesdeziel, bouncing an idea off you: Could I create that chrooted user, and setup their home directory as   /var/www/html/files/userFoo?    The idea is that these users will upload files that will be seen from the website (published at /var/www/html)20:20
sdezieltsglove: the chroot dir doesn't have to be a home dir. Could be anything that's only writable by root. You could use  /var/www/html/files/%u, where % would expand to the connecting username20:21
tsgloveAhhh... so  %u  expands to the connecting username... ok ok!20:22
sdezieltsglove: when I need someone to be able to upload to a web root, I let them ssh as "www-data" and add a config snippet to have the www-data chrooted to where I want20:22
chilukahasenack: yeah I still see the persistent stat_systemd-ask-password.patch patch in ubuntu..20:22
ahasenackyep20:22
tsglovesdeziel, ok.  I thought sftp (and previously, rsync) so they don't have shell access... just file uploads/replacements.20:22
chilukahasenack: so I'm confused.. Is there still something amiss?20:23
ahasenackchiluk: no, there is not. The perms were changed probably a long while ago and just never mentioned in d/changelog20:23
chilukyes very likely.20:23
ahasenackchiluk: this git workflow tends to find undocumented changes :)20:23
ahasenackI just jumped the gun when I compared the previous *debian* package with ubuntu, but that's just the delta being carried over20:23
chilukwell that's interesting..20:24
chilukahasenack:  that actually looks like a minor bug in debian.20:25
chilukand maybe in Ubuntu..20:25
ahasenackthe perms?20:25
chilukyeah ... maybe..20:25
chilukwell good luck have fun... thanks for doing that merging..20:26
sdezieltsglove: yeah, I understand. The "www-data" example is if you don't need to have the uploaded file owned by anyone in particular20:27
tsglovesdeziel, ok ok.  Thanks20:27
ahasenackchiluk: thx :)20:27
ahasenacknacc: is this related to the snap? http://pastebin.ubuntu.com/25314333/ I have never seen that error before20:28
naccahasenack: hrm, it could be that it's using artful now, so there might be more leakage20:34
naccahasenack: that's with your branch? i can try and debug it in a second20:34
ahasenackok20:34
ahasenackI'm on xenial fwiw20:34
ahasenacknacc: that was with https://code.launchpad.net/~ahasenack/ubuntu/+source/cifs-utils/+git/cifs-utils/+ref/artful-cifs-utils-merge-171068820:35
naccahasenack: ok20:36
naccahasenack: yeah it's a perl-thing, let me debug20:42
ahasenackok20:42
naccahasenack: i think it's actually a packaging bug, dpkg-architecutre can't work without dpkg being installed20:46
ahasenackand there is no dpkg inside the snap?20:46
naccahasenack: can you see if you can reproduce that in a lxd (artful or even sid) and report it?20:46
naccahasenack: not yet :) i'm adding it20:46
naccit's one file from the dpkg binary package (tupletable)20:46
ahasenackI can't install the snap in an lxd container :/20:46
naccahasenack: not the snap20:46
naccahasenack: install dpkg-architecture20:46
naccremove dpkg20:46
ahasenackah20:46
ahasenackok, hang on20:46
naccor something like that20:46
ahasenackremove dpkg, that shall be fun20:46
naccand i think d-a will fail20:47
naccit's probably an impossible state outside of snaps, but i'm not 100%20:47
tomreyndrab: it's still not urgent, but i'm still looking forward to it ;)20:47
naccahasenack: and i need to set DPKG_DATADIR in my wrapper(s)20:48
drabtomreyn: I did it, you dind't see the query?20:49
ahasenacknacc: dpkg-dev (which has dpkg-architecture) doesn't depend on dpkg20:49
ahasenacknor recommends or suggests it20:49
naccahasenack: right, i think that's the bug20:49
DammitJimthis must be the most ridiculous question asked here, but is it normal that one has to worry about each package installed where one defined an ubuntu version?20:49
naccahasenack: as it does, in practice, as it seems to call out to a file from dpkg20:49
ahasenackyeah20:50
DammitJimso, I'm looking at erlang and it seems there is a hard coded apt list with ubuntu trusty20:50
drabDammitJim: ? so installed a specific version rather than latest?20:50
DammitJimso, if I was to upgrade to 16.04, I'd have to manually change all those, right?20:50
ahasenackubuntu@artful-no-dpkg:~$ sudo mv /usr/share/dpkg/tupletable /root20:50
ahasenackubuntu@artful-no-dpkg:~$ dpkg-architecture20:50
ahasenackdpkg-architecture: error: cannot open tupletable: No such file or directory20:50
ahasenacklooks straightforward20:50
DammitJimsorry, not specific version, but the repo was specified according to the version of ubuntu20:50
ahasenackfurthermore, it does20:51
ahasenackdpkg-architecture: error: dpkg --print-architecture failed: No such file or directory20:51
naccahasenack: yeah, it seems like  amissing binary-depends (at least for that package)20:52
drabDammitJim: it depends what put the repo there? for 3rd party repos I believe so, yes20:53
drabDammitJim: as the strings are not known20:53
naccahasenack: kicking off a fresh build, with i think that what should fix it20:53
drabfor the official standard repo the do-release-upgrade should handle it20:53
sarnoldDammitJim: I believe the do-release-upgrade system will disable non-standard repos as part of upgrading. but using non-standard repos might indeed complicate or prevent upgrades entirely20:54
naccahasenack: will hopefully be in r141/220:54
ahasenackok20:55
DammitJimsarnold, that's just part of knowing what you are running on your servers, huh?20:57
sarnoldDammitJim: yeah; if you choose to use third-party repos you better be prepared to understand why :)20:57
DammitJimugh... I feel overwhelmed20:57
DammitJimthanks, though20:57
sarnoldDammitJim: just out of curiosity what features were in the third-party erlang repo that you wanted?20:58
DammitJimit's actually not just erlang20:59
DammitJimthe devs requested to run rabbitmq with the latest20:59
naccahasenack: build-source works now20:59
DammitJimthat worked fine with the default erlang20:59
ahasenacknacc: same here20:59
DammitJimbut in the last update or not sure when, rabbitmq stopped working right when receiving ssl connections20:59
DammitJimupdating erlang from the erlang repos fixed the issue21:00
sarnoldugh21:01
DammitJim?21:02
sarnoldthat just sounds like a really frustrating thing to try to debug21:05
hehehegood21:23
naccahasenack: ha! finally beat the snap back into submission, import now succeeds21:25
ahasenack\o/21:25
naccrbasak: --^ fyi21:26
ahasenackhm, our openssl is quite old21:26
ahasenackbut that's a can of worms21:27
ahasenackdebian is ahead21:27
ahasenackeven debian stable (!)?21:27
ahasenack"! DO NOT MERGE !" :)21:28
ahasenackok, so we still need the cyrus-sasl2 patch for an old ssl21:29
ahasenackin artful21:29
ahasenackjust no need to submittodebian21:29
naccahasenack: that sounds right21:32
=== Chrisfu- is now known as Chrisfu
docmurHey guys, I'm trying to run Jira on my Ubuntu Server but I keep running into this error: java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory  I think it's a Java Bug based off looking at with google, does anyone have a solution?23:54
naccdocmur: libjli.so comes from openjdk-8-jre-headless (or -jdk-headless)23:55
naccdocmur: s/8/7 if on an older ubuntu23:55
=== Chrisfu is now known as 32NAAT2HW
docmurHmmm okay, that's what I'm using, I'll trying updating it23:56
=== alfred is now known as 21WAACIDD
naccdocmur: i guess it depends on what is loading and from where23:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!