[01:00] <dtchen> anyone with i386 -- bare metal, not vm -- lying about?
[02:06]  * jdong scratches head at bug 475891
[02:08] <dtchen> heh, I remember eagle.
[02:13] <jdong> dtchen: heh the proposed fix is one of the more amusing ones I'v eseen
[02:13] <jdong> especially when it seems like neither the SRU submitter nor the Debian uploader seem to give a second thought to it
[03:12] <JonyBlaze> maybe it uses relative paths?
[03:17] <JonyBlaze> still though...heh
[04:18] <jgoppert1> how best to make a package that is just a super package that makes other package ?
[04:18] <jgoppert1> install
[04:20] <sbalneav> jgoppert1: Take a look at one of the existing metapackages
[04:20] <sbalneav> something like ubuntu-desktop.
[04:21] <jgoppert1> thanks i'll check it out
[04:21] <sbalneav> apt-get source ubuntu-desktop.
[04:29] <jgoppert1> exec germinate-update-metapackage --bzr ??
[04:29] <jgoppert1> i think this is probably not needed for me, but wondered if anyone knows that this command does
[04:33] <jgoppert1> has anyone used dh --with germinate, i think it must be used to pipe files in somehow Depends: ${misc:Depends}, ${germinate:Depends}
[04:42] <jgoppert1> found the equivs package, looks very helpful, thanks guys
[04:45] <JonyBlaze> is there a way I can delete a package I uploaded to REVU?
[04:50] <nhandler_> JonyBlaze: What is the package?
[04:50] <nhandler_> JonyBlaze: And why do you want to delete it?
[04:51] <JonyBlaze> nhandler_: pep8, after I made it I relized there is a Debian package with the same name (unrelated)
[04:51] <JonyBlaze> I need to rename it
[04:52] <JonyBlaze> I will rename it to pep8simulator
[04:53] <JonyBlaze> http://revu.ubuntuwire.com/p/pep8
[04:54] <JonyBlaze> http://packages.debian.org/sid/pep8
[04:54] <JonyBlaze> thats not good :(
[04:55] <nhandler_> JonyBlaze: Done
[04:55] <JonyBlaze> thank you!
[04:56] <nhandler_> JonyBlaze: You are welcome
[05:56] <ScottK> jgoppert1: If you think equivs is a solution to your problem you are almost certainly not considering the solution correctly.  In almost all cases, including the one you're considering, it's a horrible hack and not the write way to go.
[05:58] <jgoppert1> Scottk: what do you recommend? I can do it manually. I have built other packages
[05:58] <ScottK> It depends on how often it will change.
[05:59] <ScottK> For most in archive metapackages we use seeds and germinate, but if it'll rarely change, manually is fine.
[05:59] <jgoppert1> its a set of packages that i want to install on my computer network, maybe every month or so
[06:00] <jgoppert1> i've been looking at ubuntu-meta, but have yet to figure out how germinate:Depends is supposed to pull in what file
[06:00] <ScottK> But if the set isn't going to change, then just do it manually and make the packages you want a depends of the metapackage.
[06:00] <jgoppert1> the set will change every month
[06:05] <austin_laptop> so at wineconf, Scott Richie mentioned that there is a list of ~1000 packages that don't compile on Karmic, anyone know where that is? google doesn't show much
[06:07] <siretart> austin_laptop: see the topic, last link
[06:07] <austin_laptop> ah, crap, I'm blind
[06:07] <austin_laptop> thanks
[06:30] <jmarsden> Package version numbering confusion: bible-kjv is one of those "doesn't build on Karmic" packages.  I just fixed it.  It was version 4.23.  No -1, no -1ubuntu1, etc.  Just 4.23.  What should I number the fixed package?
[06:31] <ScottK> jmarsden: If it's a native package in Debian, leave it that way.
[06:32] <jmarsden> So ... does that mean I can bump it to 4.24 myself?
[06:34] <siretart> no, that would clash if debian publishes 4.24. this would then confuse everyone
[06:35] <AnAnt> should one sign the new CoC ?
[06:35] <siretart> ScottK: TBH, converting it to non-native does not sound like the worst idea to me.
[06:36] <jmarsden> I know a friendly DD I can probably get to upload it to Debian unstable for me... should I bump to 4.24 and do things that way??
[06:37] <siretart> jmarsden: the cleanest way: get 4.24 sponsored to debian and then have it synced to ubuntu. in that order
[06:37] <jmarsden> OK, makes sense.  Will do.  Thanks.
[07:56] <dholbach> good morning
[08:29] <iulian> Morning dholbach.
[08:30] <dholbach> hi iulian
[09:07] <wrapster> I recently added a few changes to bintuils pkg that i was working on... I fixed/uploaded the latest one .. but on some machine via the APT if i try to install them I get this error... http://pastie.org/689890
[09:33] <LucidFox> Why does mc have such weird defaults for file associations?
[09:34] <LucidFox> It tries to run gqview for image files, for one
[09:42] <siretart`> LucidFox: I see that you work a lot on multimedia packages in
[09:42] <siretart`> ubuntu. have you considered joining pkg-multimedia and maintain the
[09:42] <siretart`> ubuntu packages there?
[09:54] <LucidFox> siretart`> In Debian?
[09:55] <siretart`> well, sort-of yes.
[09:57] <slytherin> NCommander: ping
[09:59] <directhex> poke pokey poke poke. is TheMuso about?
[10:07] <LucidFox> siretart`, won't all the packages depending on libmp4v2 in Ubuntu also be able to use it in Debian?
[10:08] <siretart`> LucidFox: probably yes
[10:22] <\sh> moins
[10:24] <siretart`> hi \sh!
[11:02] <\sh> bah...office power outage and the whole infrastructure inhouse doesn't work anymore...dear god of sysadmins, please give me pros to work with
[11:11] <mok0> \sh: no UPS'es?
[11:27] <\sh> mok0, not in this office...and it's internal it which is responsible for this mess
[11:38] <dpm> hey dholbach, I've got a question on SRUs on the sponsorship queue. I'm looking at http://people.canonical.com/~dholbach/sponsoring/ I filed an SRU at https://bugs.edge.launchpad.net/ubuntu-translations/+bug/460984 and it doesn't appear on the list. I'm not sure I did the nomination for karmic correctly. What do you think it could be?
[11:39] <dholbach> it doesn't have the sponsoring team on it? :)
[11:39] <dholbach> ubuntu-main-sponsors in this case
[11:49] <dpm> dholbach, argh! I had not noticed I had only subscribed ubuntu-sru. Thanks! :)
[11:49] <dpm> sorted
[12:19] <\sh> ttx, pingeling ;) bug #475457 :)
[12:25] <ttx> \sh: yo
[12:26] <\sh> ttx, I wanted to put this topic as start of a discussion about this...I wonder if the patch I did is sane, or if it's better, to move $JSVC_CLASSPATH from /etc/default/tomcat6 after the default startup classes
[12:27] <ttx> \sh: the way you did it allows to override the default classes, which sounds cool...
[12:28] <ttx> only unknown is whther starting a classpath with ":" is allowed/harmful or not
[12:33] <\sh> ttx, imho it is, but we can go with a better solution with some shell magic..e.g. setting JSVC_CLASSPATH in default to empty... and in /etc/init.d/tomcat6 if [ -z "$JSVC_CLASSPATH" ]; then JSVC_CLASSPATH="<the standard stuff>" else JSVC_CLASSPATH="$JSVC_CLASSPATH:<the standard stuff>" fi
[12:33] <ttx> \sh: sure.
[12:34] <\sh> ttx, or just set the default settings in /etc/default/tomcat6 and use it as well in the init script...so we are clean...all defaultsettings are set where it really belongs :)
[12:35] <ttx> \sh: yes, that's even better... then you can add your stuff before and/or after the regular stuff.
[12:35] <\sh> ttx, yepp...
[12:51] <sebner> hiuhu \sh, everything fine? :D
[12:52] <ThreeOfEight> Hallo, can anyone help me build a package, step by step?
[12:53] <\sh> sebner, if you ask in such a tone, no ;)
[12:53] <sebner> ThreeOfEight: that always differ from source to source. have you read the packaging guide?
[12:53] <ThreeOfEight> Yes I have.
[12:54] <ThreeOfEight> In two languages
[12:54] <sebner> \sh: "such tone" ?
[12:54] <sebner> ThreeOfEight: ok, where do you have problems?
[12:54] <ThreeOfEight> Well first of all, I'm not entirely sure how to start
[12:55] <ThreeOfEight> The programme I'm trying to build a package of is a small game a friend of mine wrote, I've got the source and a binary
[12:55] <ThreeOfEight> So what do I do? Put both in one package? Or build two separate ones?
[12:55] <sebner> ThreeOfEight: https://wiki.ubuntu.com/MOTU/GettingStarted
[12:57] <ThreeOfEight> oh, okay, I haven't read that one.
[12:57] <directhex> ThreeOfEight, you don't package binaries. you create source packages, which define how binaries should be built and packaged by the build servers
[12:59] <ThreeOfEight> ah okay, that makes sense
[13:00] <ThreeOfEight> however, when I tried to build my source package, I had a weird error
[13:00] <ThreeOfEight> It said that "changes could not be applied because the binary file was changed"
[13:00] <ThreeOfEight> but I'll try again from scratch
[13:01] <directhex> ThreeOfEight, if your "clean" rule in debian/rules doesn't revert everything back to before-you-tried-compiling status, then you get that error
[13:01] <ThreeOfEight> Oh yes, that was weird, too
[13:01] <ThreeOfEight> it first said that there was no rule to make clean
[13:01] <ThreeOfEight> but there was a clean: in the rules file
[13:08] <geser> clean from debian/rules often calls clean from the upstream makefile, perhaps it's that what's missing
[13:08] <ThreeOfEight> There is no upstream makefile
[13:08] <ThreeOfEight> because there's really nothing to clean
[13:08] <ThreeOfEight> Where am I, that is my script, supposed to put the compiled binary?
[13:12] <joaopinto> ThreeOfEight, aren't you building from source ? there should be a resulting binary to clean
[13:12] <ThreeOfEight> Well, what do I do with that binary?
[13:12] <ThreeOfEight> Where do I put it?
[13:12] <ThreeOfEight> The root directory of the package?
[13:13] <directhex> ThreeOfEight, the "binary" rule in debian/rules should take the binary produced in the "build" rule, and place it inside an appropriate pretend path (usually debian/tmp/usr/bin/fooapp or something like that), and send the right commands to turn that path into a package
[13:13] <joaopinto> ThreeOfEight, to start, was the binary built from the source as part of the package build process ?
[13:13] <joaopinto> directhex, I believe he is trying to install a precompiled binary
[13:13] <ThreeOfEight> it was.
[13:13] <ThreeOfEight> no, I'm not
[13:13] <ThreeOfEight> I am compiling, and that works
[13:13] <joaopinto> ThreeOfEight, so you already fixed the binary on changes error, right ?
[13:14] <directhex> let me find a simple example of a makefile-free package
[13:14] <ThreeOfEight> yes
[13:14] <joaopinto> ok
[13:14] <ThreeOfEight> I just don't know where to put the compiled binary now
[13:14] <joaopinto> ThreeOfEight, are you using cdbs or debhelper ?
[13:14] <ThreeOfEight> er
[13:14] <joaopinto> with cdbs it's simpler
[13:14] <ThreeOfEight> right now I just call dpkg-buildpackage
[13:14] <joaopinto> ok, and how is your debian/rules ?
[13:14] <ThreeOfEight> Well it compiles it
[13:15] <joaopinto> a long list of dh_* calls ?
[13:15] <ThreeOfEight> It cleans it up
[13:15] <ThreeOfEight> Yes
[13:15] <directhex> joaopinto, cdbs is never simpler than dh7 unless you are doing *just* the right voodoo
[13:15] <joaopinto> ok, so it's using debhelper
[13:15] <ThreeOfEight> I just modified the original one created by dh_make
[13:15] <ThreeOfEight> ah, yes
[13:15] <ThreeOfEight> right, I am. sorry.
[13:15] <directhex> joaopinto, dh7, that is. dh5 is complex
[13:15] <joaopinto> directhex, right, but most people still use dh5
[13:15] <ThreeOfEight> and I removed all the Makefile calls
[13:15] <directhex> well, they're sillypants! dh5 is hard!
[13:15] <ThreeOfEight> so what I need to know now is where to put the binary. It's supposed to go into /usr/share/games/ttmine
[13:16] <joaopinto> I personally found cdbs easier to understand :P
[13:16] <directhex> binaries don't go in /usr/share. /usr/share is for cross-platform code
[13:16] <directhex> or non-code, more commonly
[13:16] <ThreeOfEight> Really? But all the other games install in there.
[13:16] <directhex> in part
[13:16] <directhex> things like art assets go in /usr/share
[13:16] <directhex> as art is cross-platform
[13:17] <ThreeOfEight> heh... true...
[13:17] <ThreeOfEight> okay
[13:17] <ThreeOfEight> so /usr/bin/?
[13:17] <directhex> but libraries go in /usr/lib, and executables in /usr/bin
[13:17] <ThreeOfEight> alright
[13:17] <joaopinto> games binaries go into /usr/games
[13:17] <directhex> oh, yes
[13:17] <directhex> silly distinction IMHO
[13:17] <ThreeOfEight> I am a bit of a newbie in Linux, especially to package building
[13:17] <ThreeOfEight> so where do I put the binary in the package
[13:18] <ThreeOfEight> ttmine-0.51/games?
[13:18] <ThreeOfEight> or ttmine-0.51/debian/games?
[13:18] <directhex> ThreeOfEight, typically into debian/tmp/usr/games/
[13:18] <ThreeOfEight> Why tmp?
[13:20] <directhex> think of debian/tmp as a "staging area" where you construct your ideal installation, with everything in its nice little folders as expected, before you issue the appropriate command to turn debian/tmp/* into * inside a package
[13:20] <ThreeOfEight> ah okay
[13:20] <ThreeOfEight> so in the final package, I will just move all the contents of tmp up directly into debian?
[13:21] <directhex> well, the dh_builddeb command is what does that, whether you call it manually or via a layer like cdbs or dh7
[13:22] <directhex> dh_builddeb reads a list of files or folders in debian/install, removes debian/tmp from the start of them, and shoves them in a .deb file
[13:22] <ThreeOfEight> what is debian/install then?
[13:22] <directhex> just a list of files & folders to put in the package
[13:23] <ThreeOfEight> so I have to create that, too?
[13:23] <directhex> yes
[13:24] <ThreeOfEight> so okay
[13:24] <ThreeOfEight> I have rules in build so that all the stuff created goes into debian/tmp/and so on
[13:24] <ThreeOfEight> Where and what do I have to put stuff into debian/install?
[13:24] <directhex> debian/install is just a text file
[13:25] <directhex> it should contain lines like "debian/tmp/usr/bin"
[13:26] <ThreeOfEight> okay, thanks, I thought it was a director
[13:26] <ThreeOfEight> +y
[13:27] <directhex> it's just a list of what you want to go into a package. sometimes build processes make lots of extra crap you want to skip - or you have multiple install files to send different files into different packages in the event that you want multiple packages from a single sourcwe
[13:27] <ThreeOfEight> Are the contents of the tmp directory (and the directory structure itself) supposed to be created during build or can I create that before, too?
[13:27] <directhex> they should be created during the build
[13:27] <ThreeOfEight> alright
[13:28] <directhex> makes life easier - your clean rule can just go "rm -r debian/tmp"
[13:29] <ThreeOfEight> unrelated question, is there an easy way to construct an entire path?
[13:29] <ThreeOfEight> like, one command instead of mkdir debian/tmp; mkdir debian/tmp/usr and so on
[13:29] <directhex> try "-p"
[13:30] <directhex> as in "mkdir -p debian/tmp/usr/lib/foogame/" will create every piece of that chain
[13:30] <ThreeOfEight> Aaah
[13:30] <ThreeOfEight> I just read the man file, but it seems like I failed to see that option
[13:30] <ThreeOfEight> thanks
[13:32] <joaopinto> directhex, doesn't dh_clean rm debian/tmp already ?
[13:32] <ThreeOfEight> I think so
[13:32] <directhex> joaopinto, maybe. even better
[13:32] <ThreeOfEight> That's why I thought it's supposed to be created during build
[13:32] <ThreeOfEight> I built it and tmp was gone
[13:32] <joaopinto> ThreeOfEight, you can also use debian/dirs
[13:32]  * directhex runs deprecated dh_prep calls on joaopinto
[13:32] <ThreeOfEight> For what?
[13:32] <joaopinto> which takes care of the dirs creation
[13:32] <ThreeOfEight> ah okay
[13:33] <joaopinto> assumming your rules call dh_installdirs somehow
[13:33] <ThreeOfEight> yes
[13:33] <ThreeOfEight> so I just but, er
[13:34] <ThreeOfEight>  /usr/games into dirs?
[13:56] <ThreeOfEight> I don't get it... I did move my binary to debian/tmp/usr/games, but it doesn't get included into the package
[13:57] <joaopinto> ThreeOfEight, do you have debian/install with the file you need ?
[13:57] <Laney> you have to copy from there to the package build directories
[13:57] <Laney> debian/tmp is just a staging area
[13:57] <joaopinto> and your rules call  dh_install  ?
[13:57] <ThreeOfEight> oh
[13:57] <ThreeOfEight> right right...
[13:58] <ThreeOfEight> so what exactly do I put into debian/install
[13:58] <joaopinto> ThreeOfEight, debian/tmp/usr/games
[13:58] <Laney> debian/tmp/usr/games
[13:58] <ThreeOfEight> okay
[13:58] <joaopinto> dh_install will strip the debian/tmp...
[13:58] <Laney> "the stuff you want in your package"
[13:58] <joaopinto> for the target name
[13:58] <ThreeOfEight> well then I could just as well write debian/tmp, aye
[13:59] <joaopinto> on you case yes, since you want it all :p
[14:00] <ThreeOfEight> Okay, thanks everyone, I think it works
[14:01] <joaopinto> :)
[14:19] <qense> The Guake package is using "gconf-schemas --register guake.schemas > /dev/null" to install the file /data/guake/guake.schemas in its postinst script. Now there is bug #366621, with some people reporting that the schemas are not properly installed. Could this be fixed by switching to "gconftool-2 --makefile-install-rule {path}", and which of the two ways is encouraged?
[15:06] <cemc> is there a way to tell pbuilder to use something other than tar+gzip for the base.tgz ?
[15:09] <hyperair> cemc: try reimplementing the function create_basetgz() in your .pbuilderrc
[15:09] <hyperair> it may or may not work
[15:09] <hyperair> the original is in /usr/lib/pbuilder/pbuilder-modules
[15:09] <hyperair> hmm no it won't work
[15:09] <hyperair> well you could dpkg-divert it away and edit it directly =p
[15:11] <cemc> I just thought why not try to use pigz for example
[15:12] <hyperair> is it better?
[15:12] <hyperair> hmm parallel eh
[15:12] <hyperair> interesting
[15:13] <cemc> well honestly I didn' try it,
[15:13] <cemc> but I tried pbzip2 on a quad-core,
[15:13] <cemc> and it is ~4x faster
[15:13] <hyperair> in all honesty, gzip is pretty damn fast, so the bottleneck is probably already your disk i/o
[15:13] <hyperair> bz is something else entirely
[15:13] <cemc> with 4gb ram it's likely cached
[15:13] <hyperair> bzip2 takes damn long.
[15:15] <cemc> and with tmpfs as buildplace I think it would be worth a try :)
[15:16] <bddebian> Heya gang
[15:16] <\sh> anyone needs a hand regarding merging?
[15:16] <hyperair> cemc: i was talking more of the writing.
[15:17] <hyperair> cemc: tar -czf reads the entire chroot, tarballs it, gzips it, and writes it to disk
[15:17] <hyperair> the bottleneck is probably writing
[15:17] <hyperair> since the files are probably cached, as you said
[15:17] <hyperair> cemc: if you've got enough disk space, i'd suggest cowbuilder instead.
[15:18] <bddebian> Hey if you folks are merging any packages that are orphaned in Debian, let me know and I'll try to upload changes to Debian so you can sync. :)
[15:19] <cemc> hyperair: tar -czf is rarely used, only when building the base, right? if one does a lot of package building, it gets tar -xzf 'd more, without changing. that's what I was thinking about. but I can try cowbuilder too
[15:20] <cemc> of course -x'ing is not that cpu intensive as -c'ing ;)
[15:20] <hyperair> cemc: but even -xzf writes a lot of data. in fact, it writes more than it reads
[15:20] <hyperair> -xzf writes more than it reads, and -czf reads more than it writes.
[15:20] <hyperair> but both involve quite a lot of writing
[15:22] <cemc> that's true. but I have a tmpfs /cache where all the -x'ing and compiling/building is going on, so there's no real writing when -x'ing
[15:22] <cemc> how's cowbuilder different anyway?
[15:25] <geser> cemc: a pbuilder on a tmpfs is pretty fast
[15:26] <cemc> geser: I know ;)
[15:26] <\sh> sbuild with local archive on a dl385 with 10k hds is fast too ,-)
[15:27] <hyperair> but it's more of a pain to setup
[15:27] <\sh> hyperair, hmm..no...mk-sbuild-lv is doing that for you, but right, you need to use debmirror to mirror the archives ;)
[15:27] <hyperair> see? what a pain >_>
[15:27] <hyperair> and there's no --autocleanaptcache
[15:28] <hyperair> besides, i don't like the idea of a fix-sized volume
[15:28] <geser> I use apt-cacher-ng for my pbuilder to cache the needed debs
[15:28] <hyperair> but why?
[15:29] <cemc> hyperair: so what would I need to hack exactly to use something other than tar+gzip?
[15:29] <cemc> just for the heck of it :)
[15:29] <\sh> hyperair, http://paste.ubuntu.com/314164/ <- it's enough for me ;)
[15:30] <hyperair> cemc: change tar -czf and -xzf to tar -c | pigz -c > file and cat file | tar -x | pigz -dc respectively
[15:30] <hyperair> cemc: dig around in /usr/lib/pbuilder
[15:30] <hyperair> \sh: that is HUGE
[15:31] <\sh> hyperair, no :)
[15:31] <hyperair> well for the time being, as long as i'm on this campus, i live on the same LAN as a full ubuntu mirror so i don't really care about caching really =\
[15:32] <hyperair> \sh: 450G is not big to you?!
[15:32] <\sh> hyperair, there is still place on the iscsi msa ;)
[15:32] <\sh> hyperair, nope
[15:32]  * hyperair whacks \sh
[15:32] <hyperair> hmph
[15:32] <hyperair> i've only got 320G
[15:33] <hyperair> and i get touchy when my pbuilder's aptcache exceeds 1G
[15:33] <\sh> hyperair, hd space is one thing I have enough of
[15:33] <hyperair> blargh!
[15:34] <hyperair> i used to live on a 160G hard disk
[15:34] <hyperair> then it died prematurely
[15:34] <\sh> next week I'll reactivate some of my old 7TB machines
[15:34]  * hyperair wants.
[15:34] <\sh> let's see if they are stable with a new raid controller
[15:35] <\sh> and a new backplane
[15:58] <ThreeOfEight> Bloody hell... okay, for some reason, my files still don't get moved into the package, even though I created a debian/install file which lists the directory
[16:02] <ThreeOfEight> sorry, did anyone reply? I was gone for some time
[16:02] <joaopinto> TheMuso, is dh_install invoked when you run debuild ?
[16:02] <joaopinto> ops, was ThreeOfEight
[16:03] <ThreeOfEight> I'm calling dpkg-buildpackage
[16:03] <ThreeOfEight> but... wait, I'll look
[16:05] <ThreeOfEight> it calls dh_installdirs, installchangelogs, installdocs, installman and installdeb
[16:05] <gnomefreak> anyone know if pulseaudio-module-udev was replaced by another package?
[16:06] <gnomefreak> sorry in lucid
[16:09] <ThreeOfEight> When am I supposed to call dh_install?
[16:14] <shankao> hi, I'm trying to get a new package uploaded to REVU, but although I get dput success, my revu page shows no uploaded packages by me... I have my keys correctly configured and used to sing the package that also contain the original sources
[16:14] <shankao> is there anything missing?
[16:19] <gnomefreak> shankao: IIRC it will show up on next refresh on revus end
[16:21] <ThreeOfEight> Where and how am I supposed to call dh_install if I want it to put everything in debian/tmp into the right place?
[16:22] <shankao> gnomefreak: ok, thanks... is that something automatic (like periodic refresh each hour) or manual?
[16:23] <gnomefreak> shankao: yes its automatic but its been a while sinc ei used revu
[16:25] <directhex> ThreeOfEight, how much of your "binary" rule is abnormal? is it just assorted dh_* commands?
[16:25] <ThreeOfEight> What do you mean abnormal?
[16:25] <directhex> ThreeOfEight, things that aren't just dh_* commands
[16:25] <ThreeOfEight> binary: binary-indep binary-arch
[16:26] <ThreeOfEight> binary-indep and binary-arch both call install
[16:26] <ThreeOfEight> and binary-arch also has lots of dh_'s
[16:26] <ThreeOfEight> but that's it
[16:26] <ThreeOfEight> anyway, I got it working now, somehow
[16:26] <directhex> okay. delete binary, binary-indep and binary-arch. then just write
[16:26] <directhex> binary:
[16:27] <directhex>         dh $@
[16:27] <ThreeOfEight> By removing dh_prep and manually including dh_install in install:
[16:27] <ThreeOfEight> erm
[16:27] <ThreeOfEight> okay I'll try
[16:27] <directhex> (make sure debian/compat contains the number 7)
[16:27] <ThreeOfEight> it does
[16:27] <directhex> then the "dh" command works
[16:27] <ThreeOfEight> what about that .PHONY part down there
[16:28] <directhex> shouldn't be needed in simple cases, really
[16:28] <ThreeOfEight> and what am I supposed to put in install and build?
[16:29] <directhex> given you don't have a makefile, i'd leave them be for now
[16:29] <ThreeOfEight> Right now, I have build calls build-stamp (for some reason)
[16:29] <ThreeOfEight> okay
[16:33] <cemc> hyperair: ok, I'll try that, thx
[16:33] <hyperair> cemc: np
[16:33] <ThreeOfEight> okay, now dh_install (automatically called by dh $@) doesn't find the directory I specified in debian/install anymore
[16:34] <ThreeOfEight> ...because dh_prep deletes it before dh_install is called
[16:34] <ThreeOfEight> odd
[16:45] <ThreeOfEight> Never mind, I worked around it, just left out dh_prep
[17:09] <Vorador> Hi. Could someone help with PPA builds? The problem is that the build-bot installs the wrong version of software (I have the needed version in my ppa already built, but it installs ubuntu version instead) and package building fails because of that. Build log -> http://launchpadlibrarian.net/35424976/buildlog_ubuntu-karmic-lpia.audacious-plugins_1.5.1-2ubuntu3~ppa1_FAILEDTOBUILD.txt.gz Package list -> https://launchpad.net/~sandshrew/+
[17:09] <Vorador> archive/ppa/+packages
[17:14] <Adri2000> RainCT: do you know someone called chancellor? (he unassigned you from bug #161762)
[17:14] <jgoppert> anyone know why my pbuilder would pick up some packages on my mirror but say that others are virtual packages and fail out ??
[17:16] <jgoppert> I did the obvious stuff like apt-get update. The packages install fine through apt, have my ppa set as the other mirror in my pbuilderrc
[17:20] <jgoppert> lol pbuilder update, stupid me
[17:24] <pkern> jdong: Well, just changing the version number and the suite target on LP: #365770 can hardly require resubscription of motu-sru, no?  I don't see any "ACK otherwise" there.
[17:29] <Vorador> So, nobody knows how to fix the issue with dependences?
[17:33] <ScottK> Vorador: Without looking, I'd guess you uploaded something with a lower version number than what's in the archive.
[17:33] <ScottK> Vorador: We work on developing Ubuntu here, so PPA questions aren't a priority for a lot of people.
[17:34] <Vorador> ScottK, yes I uploaded lower version.  Anyway, where I could ask PPA questions? Is there anything better than #ubuntu?
[17:35] <Vorador> [lower than the one in ubuntu default repos]
[17:35] <ScottK> Vorador: #launchpad maybe.  They seem to think we should anwswer the world's packaging questions for PPAs, so not sure.
[17:36] <Vorador> Ok, i'll try...
[17:36] <RainCT> Adri2000: uh? No, I don't think so
[17:37] <Adri2000> RainCT: that's what I thought. well, dunno what he is doing with the bug...
[17:44] <jdong> pkern: one can certainly argue a re-ack is superfluous
[17:45] <jdong> and I'd agree with that ;-)
[17:45] <jdong> it was more of "please resubscribe -sru if my attention is needed again" to reduce the clutter of subscribed bugs
[17:46] <RainCT> Adri2000: well, anyway I haven't started doing any of the Ajax yet (waiting for Scott to merge the design stuff)
[17:46] <pkern> jdong: So I fix that and upload?
[17:48] <jdong> pkern: yes please; I just commented on the ticket to the same effect
[17:55] <ScottK> jdong: You and probably TheMuso need to decide what to do about the currently pending lmms SRU upload.  It got shoved in the queue at the last second when upstream said "Oh, you want these patches too", but doesn't have a proper bug/test cases/etc.
[18:04] <Adri2000> RainCT: ok
[18:24] <jdong> ScottK: I'll take a look at that tonight
[18:24] <jdong> got a midterm in an hour
[18:24] <jdong> [which I'm gonna fail]
[18:24] <ScottK> Then you may as well keep working on Ubuntu.  ;-)
[18:24] <ScottK> jdong: OK.  Thanks.
[18:26] <jdong> LOL
[18:26] <jdong> I feel the same way at times
[18:26] <jdong> stop putting evil thoughts in my head
[18:27] <jdong> *starts filling out drop-subject form in preparation for the midterm*
[20:05] <DktrKranz> james_w: have you access to sync-blacklist?
[20:06] <james_w> yes
[20:13] <DktrKranz> james_w: mind add entries for gdebi (which already slipped in, luckily with no harm) and ubuntu-dev-tools (actually in Debian NEW)
[20:14] <james_w> nope
[20:14] <james_w> can you version ubuntu-dev-tools such that it won't happen?
[20:14] <james_w> just makes more sense that way
[20:15] <DktrKranz> are there special versions which are excluded from autosync?
[20:16] <DktrKranz> (for native packages)
[20:16] <james_w> done
[20:16] <james_w> don't think so
[20:17] <DktrKranz> I could eventually use ~debian1
[20:18] <Laney> DktrKranz: so what's the plan there?
[20:18] <Laney> do we upload to debian now?
[20:19] <Laney> what about getting other scripts into eg devscripts?
[20:48] <ScottK> Many of the scripts in u-d-t aren't really Ubuntu specific.
[20:53] <DktrKranz> Laney: some of them could be eventually proposed for merging into devscripts, some are really Ubuntu-specific, some have already some counterpart in devscripts (or similar packages)
[20:54] <DktrKranz> nhandler's summary is a good starting point
[20:56] <DktrKranz> james_w: FYI, I updated launchpadlib and dependant packages to latest version, most of them (if not all) could be synced now
[20:56] <james_w> DktrKranz: great, thanks
[20:57] <DktrKranz> I have only discovered a drawback in restfulclient unicode implementation which breaks u-d-t (buildd, at least), patch to fix it is http://people.debian.org/~dktrkranz/u-d-t_unicode.patch
[20:57] <DktrKranz> s/patch/workaround/
[21:03]  * RoAkSoAx is happy... lucid pbuilder creation succeeded...
[21:12] <jgoppert_> can anyone tell me why launchpad fails to import my git repository from sourceforge?
[21:13] <cody-somerville> ask in #launchpad
[21:13] <jgoppert_> thanks
[22:07] <ari-tczew> any sponsors are now working on lucid?
[22:25] <geser> if I find time then yes
[22:30] <chrisccoulson> i'm still working on karmic SRU's :(
[22:31] <RaXOR> hi 2 all, may be it's not right to start my speech like that, but i want to know how can usual person join soft developers team for ubuntu in gnome or kde ??
[22:32] <RaXOR> or if you can give me any information about i searching... please
[22:33] <RaXOR> i'm a programmer and very interested in ubuntu project
[22:33] <ScottK> RaXOR: For KDE, see #kubuntu-devel and ask.
[22:33] <RaXOR> thx
[22:33] <RaXOR> and for gnome ?
[22:34] <RaXOR> i have asked for kde cose of using qt libraries
[22:35] <RaXOR> thx #ubuntu-devel is a nice room... i hope =) buy
[22:36] <geser> for gnome: #ubuntu-desktop
[22:36] <RaXOR> thx 2 u =)
[22:36] <geser> there are the persons working on the gnome packages
[22:50] <jgoppert_> i've got a .so that depends on another .so, works fine, make dist check works, but when running debuild when trying to build some shared libraries it fails, can you guys help?
[22:52] <jgoppert_> i think i spotted it, missing \ in my automake file :-)
[22:53] <TheMuso> directhex: You wre after me last night?
[22:54] <directhex> TheMuso, yeah, prematurely it seems
[22:55] <directhex> TheMuso, banshee with a11y is un banshee-daily ppa... but it's disabled in build due to needing an exact version of gtk# which isn't in the archive
[22:59] <TheMuso> directhex: ah ok
[23:00] <jgoppert_> dh_shlibdeps
[23:00] <jgoppert_> dpkg-shlibdeps: error: no dependency information found for /usr/lib/libcxcore.so.4 (used by debian/uvsim1/usr/lib/libuvsimSensing.so.0.0.0).
[23:00] <jgoppert_> have you guys seeen this sort of thing?
[23:19] <jgoppert_> looks like i left out .shlibs.local
[23:33] <Laney> DktrKranz: I mean, do we upload to debian and sync now
[23:33] <Laney> or are you going to sync back from debian or or or?
[23:33] <Laney> from ubuntu to debian even
[23:40] <jgoppert_> how do you get the shlib file to install should it be lib lib1.shlib?
[23:40] <jcastro> ScottK, ok talked to elmo and he agrees that keeping old gobby is the sanest thing. I've updated the wiki page and I've asked jono to mention it at the opening plenary.
[23:42] <ScottK> jcastro: Excellent.
[23:42] <ScottK> At least it's decided in advance
[23:42] <DktrKranz> Laney: I asked to sync-blacklist u-d-t for now, I don't plan to have many changes in Debian that I won't push back to trunk, but it could happen (as happened in gdebi, for instance)
[23:42] <jgoppert_> got it, uncomment dh_makeshlibs and my life is easy.. whew
[23:43] <DktrKranz> Laney: I think it's better upload in Ubuntu as upstream first, and then in Debian if needed
[23:43] <Laney> hmm
[23:45] <Laney> yeah I think it makes more sense to treat this as a special case reversal of the normal package flow
[23:45] <Laney> so you as Debian maintainer can take care of syncing it back to unstable
[23:46] <DktrKranz> the main reason I listed as maintainer is to avoid bouncing
[23:46] <DktrKranz> *myself
[23:48] <Laney> well someone has to take care of it


[00:41] <pepperhead> Anyone alive out there? Trying to install SabNZBD to ubuntu server 18.04, it is refusing connections
[00:41] <pepperhead> Status says it is active and running
[00:44] <tomreyn> !info sabnzbdplus
[00:45] <tomreyn> use netcat -vv to connect to its default port and see whether the connection is exatblished successfully.
[00:46] <tomreyn> do this locally on the server first of all, to work around firewalling and NAT issues, then do it from remote.
[00:46] <pepperhead> netcat?
[00:46] <pepperhead> Appreciate the reply BTW
[00:47] <pepperhead> My server is headless, will it require a GUI?
[00:50] <pepperhead> So like "netcat -v <IP_ADDRESS> 8080"?
[00:51] <pepperhead> Returns: netcat: connect to <IP_ADDRESS> port 8080 (tcp) failed: Connection refused
[00:53] <pepperhead> same for "netcat -v <IP_ADDRESS> 8080"
[00:57] <pepperhead> shouldnt be any NAT, so maybe a firewall thing?
[01:01] <sarnold> connection refused could be firewall or it could be the application isn't listening on the port
[01:01] <sarnold> you can check what ports it is listening on with netstat -tlnp or ss
[01:02] <tomreyn> or lsof -i :8080
[01:02] <tomreyn> make sure the port number is correct, too
[01:02] <tomreyn> pepperhead ^
[01:02] <sarnold> woah
[01:02] <sarnold> tomreyn: that's handy
[01:02] <sarnold> way less typing :)
[01:02] <tomreyn> :)
[01:03] <pepperhead> HAH!
[01:04] <pepperhead> You guys are awesome
[01:04] <pepperhead> I ASSUMED it defaulted to 8080 so I didnt set the port in the service configuration as it said (optional)
[01:05] <pepperhead> Set it to 8080 and restarted the service...POOF
[01:06] <tomreyn> \o/
[01:06] <sarnold> nice :)
[01:11] <pepperhead> I was going to run these in docker containers, but that was totally not happening
[01:12] <pepperhead> Two down(Plex/Sab), one to go (Radarr)
[01:13] <sarnold> pepperhead: give lxd a quick look, I think it's easier to work with than docker
[01:14] <sarnold> docker feels like "here's a tarball of stuff I don't want to understand, give it a socket please" and lxd feels like "I'd like a bunch of systems that appear to be clean slates but with less overhead than qemu"
[01:15] <tomreyn> :) ^this
[01:15] <pepperhead> I started down that road, but ran into networking issues with the LXC to host thing. I may go back to it once I know the apps better.
[01:16] <pepperhead> The firewall tweeks are easier here, and on less thing to work on with LXC
[01:16] <pepperhead> I have LXC installed
[01:16] <tomreyn> s/lxc/lxd/
[01:17] <pepperhead> I like lxc/lxd, I am more familiar with freebsd jails
[01:17] <pepperhead> so might be easier to pick up
[01:18] <sarnold> I enjoyed reading https://blog.ubuntu.com/2016/04/07/lxd-networking-lxdbr0-explained
[01:18] <sarnold> wow, that's from 2016? it felt newer than that.. heh
[01:19] <pepperhead> lol
[01:19] <sarnold> so, uh, maybe take anything in there with a big-ass grain of salt :)
[03:15] <l4m8d4> Is there a reason why tasksel is not installed by default on ubuntu server 18.04? Are we supposed to use something else instead of it? Is there a more modern replacement or has everyone started to just install metapackages for what they need?
[03:16] <l4m8d4> I remember that back in the old days it was used by the installer so one could choose if they wanted ssh server, lamp stack, mail server etc.
[04:53] <cpaelzer> moin
[05:04] <shahrokh> I install ubuntu server 18.04 on virtualBox but dont working network. virtualbox netconfiguration is NAT and Hosy-only(<IP_ADDRESS>)
[05:11] <shahrokh> Do you have idea?
[05:13] <ChmEarl> shadoxx, do you have any /etc/netplan/*.yml ? and does it use dhcp?
[05:17] <ChmEarl> shadoxx, you may need to rewrite that *.yaml file for a static config that uses gateway <IP_ADDRESS>
[05:18] <shahrokh> chmearl, yes i have 2 *.yaml config
[05:21] <shahrokh> https://gist.github.com/shahroukh/7ffc516ffbf606a5f7171b392038b7f5
[05:22] <ChmEarl> connect at <IP_ADDRESS>
[05:22] <ChmEarl> shahrokh, can you ping or ssh to that IP from host?
[05:23] <shahrokh> i connect to <IP_ADDRESS> with ssh but dont have ping to google ot <IP_ADDRESS>
[05:25] <shahrokh> result of networkctl: https://gist.github.com/shahroukh/7ffc516ffbf606a5f7171b392038b7f5#gistcomment-2632154
[05:26] <shahrokh> networkctrl status ofcource
[05:28] <ChmEarl> shahrokh, in the *.yaml, add <IP_ADDRESS> to the 2 other nameserver addresses
[05:29] <ChmEarl> then `netplan apply`
[05:29] <shahrokh> netplan apply result: Error in network definition //etc/netplan/01-netcfg.yaml line 8 column 19: address '<IP_ADDRESS>' is missing /prefixlength
[05:32] <ChmEarl> no , add it here: addresses: [<IP_ADDRESS>, <IP_ADDRESS>]
[05:32] <ChmEarl> line 8 is wrong place
[05:38] <shahrokh> i dont understant, is correct?: https://gist.github.com/shahroukh/7ffc516ffbf606a5f7171b392038b7f5#file-01-netcfg-yaml
[05:39] <ChmEarl> yes, 02-netcfg looks better, might work, unless a route is needed too
[05:41] <ChmEarl> shahrokh, you still have an error in 01-netcfg
[05:41] <shahrokh> yes
[05:42] <ChmEarl> remove  addresses: [<IP_ADDRESS>] from 01-netcfg... you added there earlier
[05:42] <ChmEarl> remove  `addresses: [<IP_ADDRESS>]` from 01-netcfg... you added there earlier
[05:43] <shahrokh> comment addresses and gateway in 01-netcfg.. but netplan result: Error in network definition //etc/netplan/01-netcfg.yaml line 10 column 19: address '<IP_ADDRESS>' is missing /prefixlength
[05:43] <shahrokh> :-D
[05:46] <ChmEarl> should be no extra <IP_ADDRESS> in 01-netcfg
[05:47] <ChmEarl> no changes to original 01-netcfg are needed. Only change 02-netcfg
[05:52] <shahrokh> commnet nameservers in 01-netcfg and netplan apply restault is ok
[05:53] <shahrokh> what am i doing??
[05:54] <shahrokh> dont ping <IP_ADDRESS>
[05:58] <shahrokh> @ChmEarl
[05:58] <ChmEarl> shadoxx, you started out showing me 02-netcfg, then you made mods to 01-netcfg too, why?
[05:59] <lordievader> Good morning
[06:00] <ChmEarl> sorry, meant for shahrokh , not shadoxx
[06:01] <shahrokh> what do you mean? start by 02 but made mode 01? i dont understand
[06:01] <shahrokh> no problem my dear :-D shadoxx or shahrokh
[06:02] <ChmEarl> shahrokh, your edits are track in github, so use the features and back out the change to 01-netcfg
[06:04] <shahrokh> do you edit code in my github link?
[06:05] <shahrokh> i have 2 files for any ethernet
[06:06] <shahrokh> https://gist.github.com/shahroukh/7ffc516ffbf606a5f7171b392038b7f5
[06:20] <shahrokh> ChmEarl
[06:52] <shahrokh> do have any idea for my use case?
[07:06] <oe1skw> good morning
[08:49] <trippeh_> hum. Network Manager is refusing to manage any ethernet interfaces
[08:49] <trippeh_> enp5s0  ethernet  unmanaged  --
[08:49] <trippeh_> nmcli dev set enp5s0 managed yes -> succeeds
[08:49] <trippeh_> still unamanged
[08:52] <trippeh_>  unmanaged-devices=*,except:type:wifi,except:type:wwan
[08:52] <trippeh_> ha wow
[08:52] <lordievader> trippeh_: Is the interface defined in `/etc/network/interfaces`?
[08:52] <trippeh_> nope.
[08:52] <trippeh_> not in networkd or "netplan" either
[08:53] <trippeh_> but I think I figured it out now. ubuntu has started blacklisting all non-wifi/wwan devices.
[08:53] <lordievader> Err, does the * in `unmanaged-devices` not match the ethernet adapter?
[08:55] <trippeh_> lordievader: yes, it matches, it is a blacklist.
[08:57] <lordievader> So, that is why the ethernet device keeps being unmanaged?
[09:00] <trippeh_> yup.
[09:00] <trippeh_> this also broke usb ethernet dongles on my laptop. so has been a long running annoyance.
[09:01] <lordievader> Does this mean your issue is solved?
[09:02] <trippeh_> yes, by touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf to override the ubuntu shipped configuration.
[09:02] <lordievader> Ok, good to hear 👍
[09:17] <trippeh_> surprise, now my VPNs work too ;)
[12:38] <cyphermox> trippeh: fwiw, when you set 'renderer: NetworkManager' in netplan when you configure network devices there, it does set things to be managed by NM (ie. touching /run/NetworkManager/conf.d/10-globally-...)
[12:39] <cyphermox> desktop installs ship a file that make sure NetworkManager manages everything: https://netplan.io/examples#network-manager
[12:40] <trippeh_> netplan is not installed
[12:40] <cyphermox> trippeh_: if you have a server on which you install NetworkManager, and then use it to manage VPN and whatnot, then it will indeed explain why these devices did not work. by default, only wifi/wwan are managed by NM, as networkd can't do them well
[12:41] <cyphermox> netplan.io is installed everywhere. if you remove it yourself, you are still left with distro defaults that may be installed, such as that 10-globally- file.
[12:49] <trippeh_> supposedly the file is set on upgrades as well, but that had not happened here for whatever reason
[12:49] <trippeh_> maybe some fallout from running betas.
[12:56] <rbasak> cpaelzer or ahasenack: would you mind reviewing https://code.launchpad.net/~racb/usd-importer/+git/usd-importer/+merge/347299 for me please?
[12:56] <rbasak> It's fairly trivial.
[13:01] <cpaelzer> rbasak:  looking
[13:03] <cpaelzer> rbasak: did you see the call for mysql migration assitance?
[13:03] <cpaelzer> I did not yet get to it today
[13:04] <rbasak> Yeah but it didn't seem immediately actionable to me. doko had already uploaded a no change rebuild and it was still building
[13:05] <cpaelzer> ok
[13:05] <trippeh_> cyphermox: network manager still failing silently after purge and reinstall was very confusing until I found that file. :)
[13:06] <trippeh_> no hints in logs or anything.
[13:33] <rbasak> cpaelzer: I didn't think a re-raise was needed because that's exactly what the stack trace is for. Given that all the re-raise would do is say "it was re-raised from _here_".
[13:45] <cpaelzer> rbasak: so you want it explicitly uncatched to get the builtin stacktrace - I see that
[13:45] <cpaelzer> but I wanted the log message before the trace
[13:46] <cpaelzer> that is what I thought to achive by the re-raise
[13:46] <cpaelzer> if the original trace is lost by the re-raise the log message isn't worth it
[13:49] <rbasak> We can log and reraise if we want.
[13:50] <rbasak> But what would that really achieve?
[13:50] <rbasak> 'Cannot get all versions from changelog' doesn't tell us any more than the knowledge that we're in a function called get_all_changelog_versions_from_treeish, and that knowledge is provided by the stack trace.
[14:00] <cpaelzer> rbasak: one day there will be two checks in there
[14:00] <cpaelzer> and then you'll be happy to see immediately which one triggers
[14:01] <cpaelzer> rbasak: but this is rather soft feedback, you had no real issues - so feel free to commit as is if you prefer otherwise
[14:04] <rbasak> OK. Thank you for the review!
[14:44] <njbair> i'm having the hardest time getting conjure-up to work. it keeps timing out at different points during the build while trying to access api.jujucharms.com, but every time i try the timeout happens at a different point in the process
[14:44] <njbair> seems like intermittent network trouble, but i'm not sure if it's on my end or a known issue with the api?
[17:38] <ahasenack> rbasak: hi, if you are still around, could you please push the upload tag for this mp? https://code.launchpad.net/~ahasenack/ubuntu/+source/apache2/+git/apache2/+merge/348632
[17:38] <ahasenack> rbasak: I couldn't find the right Author, so I'm going with just Origin in the dep3 header
[17:38] <Ussat> in 16.04 wgat version of cacti is there ?
[17:39] <ahasenack> Ussat: "rmadison cacti" tells me it's 0.8.8f+ds1-4ubuntu<IP_ADDRESS>
[17:40] <Ussat> wow....big jump from 16 to 18.04
[17:41] <Ussat> what is rmadison ?
[17:41] <nacc> !info cacti xenial
[17:41] <nacc> ahasenack: --^ fyi you can do that :)
[17:41] <Ussat> I did not know, thanks
[17:41] <ahasenack> figured :)
[17:41] <Ussat> appreciated
[17:43] <Ussat> the cacti 1.1.38 in 18.04 wont graph at all.....known issue with that version of cacti according to the forums and some emails
[17:43] <nacc> Ussat: rmadison is the archive database available over the network
[17:43] <nacc> s/is/queries/
[17:43] <Ussat> ahh
[17:44] <Ussat> !info cacti-spine xenial
[17:44] <nacc> Ussat: is there an ubuntu bug filed?
[17:44] <Ussat> I have not had time to take a proper dump, let alone fikle a bug...its on my todo list
[17:45] <Ussat> sorry so short...shit goin really sideways here
[17:46] <nacc> Ussat: understood
[17:47] <nacc> Ussat: so it's knonw upstream? fixed already?
[17:47] <Ussat> upstream and not fix, ack'd though
[17:48] <nacc> Ussat: ok, hard for us to do anything without an upstream fix :)
[17:50] <Ussat> yup
[17:52] <Ussat> Just ack'd the bug yesterday...so I would not expect anything soon
[17:57] <sruli> time on my server is out of sync - "timedatectl: Failed to query server: Failed to activate service 'org.freedesktop.timedate1': timed out"  - - "systemctl status systemd-timesyncd: ... ... systemd-timesyncd[742]: Timed out waiting for reply from <IP_ADDRESS>:123 (ntp.ubuntu.com)" - - "ping <IP_ADDRESS>: 64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=55 time=80.1 ms"
[18:01] <blackflow> ping's irrelevant if there's an issue with the ntp service. Try another pool, like pool.ntp.org
[18:01] <blackflow> sruli: ^^^
[18:02] <sruli> how do i change it?
[18:02] <blackflow> sruli: /etc/systemd/timesyncd.conf
[18:05] <sruli> NTP=pool.ntp.org or FallbackNTP=pool.ntp.org ?
[18:06] <blackflow> NTP is primary
[18:06] <sruli> same, i get a timeout
[18:06] <nacc> `man timesyncd.conf`
[18:06] <blackflow> so yeah you could set FallbackNTP in case ntp.ubuntu.com for some reason isn't accessible
[18:07] <sruli> pool.ntp.org is also not working, womething else seems to be the issue
[18:09] <blackflow> sruli: firewall? is that a hosted server? some DCs don't allow outbound ntp due to it being easy to abuse, and require you to use their own servers
[18:10] <sruli> my own server, its a vm, just tested on another few on same network, cant find anything in touter iptables to block it
[18:12] <blackflow> residential ISP?
[18:12] <nacc> iirc, you can use ntpdate by hand to query an ntp server?
[18:13] <sruli> not residential but other servers (all 18.04) work fine
[18:14] <sruli> 28 Jun 18:14:27 ntpdate[29101]: no servers can be used, exiting
[18:15] <blackflow> speaking of "outer iptables", how's that set up for established,related  flows? the firewall needs to track UDP packets otherwise you'll have to open port 123 for inbound response UDP packets
[18:16] <sruli> established,related accept. will try to run a tcpdump now and see if i see anything
[18:20] <sruli> blackflow: its not hitting my router, also ntpdate exits so fast its not possible that its even trying to ake a connection
[18:21] <blackflow> sruli: I think if you disable ntp and then enable it (timedatectl set-ntp on|off) it should start syncing up when it's enabled again.
[18:21] <blackflow> if not, the nuke that carp and install proper ntp daemon. openntpd is recommended.
[18:21] <blackflow> !info openntpd
[18:21] <blackflow> *then
[18:24] <sruli> cant even turn it off "Failed to set ntp: Failed to activate service 'org.freedesktop.timedate1': timed out"
[18:24] <blackflow> ¯\_(ツ)_/¯  SystemD
[18:27] <sruli> openntpd not much in the man page, how do i query the time with it?
[18:28] <sdeziel> sruli: I believe you cannot
[18:28] <sdeziel> sruli: but check man ntpctl
[18:28] <nacc> i don't think openntpd is really the answer here
[18:28] <nacc> if ntpdate can't query the ntp server, something else is wrong
[18:29] <sruli> nacc: ntpdate isnt even trying, its exits faster than its possible to establish a connection
[18:29] <nacc> sruli: how did you run it?
[18:29] <sruli> ntpdate
[18:30] <nacc> sruli: right, so you didn't tell it to query any servers :)
[18:30] <nacc> sruli: hint, `man ntpdate`
[18:30] <sdeziel> ntpdate -q -v pool.ntp.org
[18:30] <sruli> No manual entry for nptdate
[18:30] <sdeziel> sruli: s/npt/ntp/ ;)
[18:31] <sruli> ;-)
[18:33] <sruli> time is adjusted, but how do i set it for summer time?
[18:34] <nacc> sruli: so manual ntpdate worked?
[18:34] <sruli> yes
[18:34] <sdeziel> sruli: this is not related to NTP, it's a TZ (timezone) setting
[18:35] <nacc> sruli: or was that a joke re: summer time? :)
[18:35] <sdeziel> sruli: could you run "ntpdate -q -v <IP_ADDRESS>"
[18:35] <sruli> nacc, i need to set it to current local time, cant do it with timedatectl as its timing out
[18:36] <sruli> sdeziel: worked
[18:36] <sdeziel> sruli: that's weird as that was the IP systemd-timesyncd couldn't reach
[18:37] <nacc> yeah something seems off
[18:37] <sruli> as far as i understand the timezone is supposed to be set in timedatectl... something is broke witht he timedatectl.. any other way i can change the tz?
[19:03] <l4m8d4> sruli: Have you read the server manual? You're not supposed to install ntpd or any other time sync package if you use timedatectl
[19:04] <l4m8d4> So just remove ntpd and try again with timedatectl
[19:24] <l4m8d4> If you configure link aggregation of two ethernet ports with netplan, does the network switch have to support that explicitly?
[19:25] <tomreyn> how would you do link aggregation on a single side of the transfer only?
[19:25] <sruli> l4m8d4: i started off with timedatectl it doesnt work thats why i needed something else!
[19:26] <dlloyd> there are some super naive implementations that do not require switch participation, but are not really aggregation
[19:26] <sruli> l4m8d4: for link agg switch needs to support 802.3ad.. else you can use other bonding methods
[19:26] <l4m8d4> tomreyn: Yeah, that was the question. I just wanted to know if that is possible or if both deviced need to be "informed" of the bond
[19:27] <l4m8d4> Okay thank you
[19:27] <tomreyn> you can also run a mirror raid with just a single raid device. but does it make sense? not a lot.
[19:27] <blackflow> ntpdate is just a temporary solution, you have to figure out why continuous syncing is not working
[19:27] <sruli> l4m8d4: it needs to be setup on both sides
[19:28] <sruli> blackflow: i know, don't know how to troubleshoot this.. hever has a issue with time sync in the past
[19:29] <sarnold> if timedatectl thing isn't sufficient for you, try chrony next
[19:29] <sruli> sarnold: it's not that it's not sufficient, it's just broke, doesnt work
[19:29] <sruli> and i would like to fix it if poss
[19:30] <l4m8d4> sruli: Are you sure that neither chrony nor ntpd is installed? Because if that were the case, timedatectl would be disabled automatically to prevent conflicts
[19:30] <blackflow> sruli: apparently you can't start or stop the daemon. that's why I recommended you nuke the systemd component and use an external one. systemd is init + process manager, anything else is half assed, constantly broken insecure reinvention. as observed with resolved and I'm pretty sure that timesyncd went belly up because something something dbus.
[19:31] <sruli> l4m8d4: ntpd was installed to check if there a problem with reaching npt protocol on the server.. timedatectl was broke before that, will remove it now and test timedatectl again
[19:33] <l4m8d4> blackflow: timedatectl is configured on ubuntu to be disabled automatically if other means of sync are present, so there should be no need to "nuke" the component
[19:34] <blackflow> l4m8d4: with "org.freedesktop.timedate1" timing out if attempted?
[19:34] <sruli> l4m8d4: removed ntpd - :~# timedatectl Failed to query server: Connection timed out
[19:34] <blackflow> you don't say.
[19:34] <sarnold> blackflow: something something dbus :)
[19:34] <blackflow> x-actly :)
[19:35] <l4m8d4> sruli: What is the output of systemctl status systemd-timesyncd.service
[19:35] <sruli> "systemctl status systemd-timesyncd: ... ... systemd-timesyncd[742]: Timed out waiting for reply from <IP_ADDRESS>:123 (ntp.ubuntu.com)"
[19:36] <sruli> ^^^ that was before.. now its just deat
[19:36] <l4m8d4> sruli: What happens if you start it manually?
[19:37] <sruli> times out.. in the process of timing out now
[19:38] <blackflow> openntpd is nice. you can even peg it to a https domain to validate the ntp response so your time can't be messed with by rogue ntp servers
[19:38] <sruli> systemd[1]: systemd-timesyncd.service: Start operation timed out. Terminating.
[19:38] <sruli> systemd[1]: systemd-timesyncd.service: Failed with result 'timeout'.
[19:38] <sruli> systemd[1]: Failed to start Network Time Synchronization.
[19:39] <blackflow> been using it on all linux and freebsd machines, never needed anything else. it's less precise than ISC ntpd but you don't need nanosecond precision do you? you aren't running HFT or something
[19:40] <sruli> all i need is the correct time, not asking for much
[19:40] <l4m8d4> sruli: But ntp.ubuntu.com is reachable otherwise, right?
[19:40] <sarnold> sruli: you don't happen to have funny firewall rules dropping udp packets or something?
[19:40] <blackflow> been through all that, and ntpdate worked.
[19:40] <sdeziel> the "start operation timed out" doesn't seem like NTP related to me, more like systemd having a bad day
[19:41] <blackflow> duh!  :)
[19:41] <blackflow> bad day, week, month and past 10 years actually :)
[19:41] <sruli> i was able to use ntpd and ntpdate... and i ran a tcpdump to see if any packets were being dropped by the router timedatectl did not send any packets out of the vm
[19:41] <sdeziel> I love systemd, for real ;)
[19:41] <sruli> i also love it (when it works)
[19:41] <blackflow> process management is good, the power of unit files awesome. but evrything ELSE, suxxxxxxxx
[19:42] <sdeziel> sruli: beware that timesyncd will back down if any other ntpd daemon is even present on the system
[19:42] <blackflow> resolved, timesyncd, nspawn, firewalld.... ughd!
[19:42] <sdeziel> sruli: did you pastebin "journalctl -u systemd-timesyncd" earlier?
[19:44] <l4m8d4> sdeziel: That's also what I would guess. Maybe they can't rely upon other packages stopping the service properly, so they decided to weirdly detect different timesync services and just time out if one is detected.
[19:44] <blackflow> WHAT!
[19:44] <sruli> http://termbin.com/t2f8
[19:45] <sdeziel> sruli: thx, have you made some changes to timesyncd.conf that were not reverted?
[19:46] <sdeziel> sruli: cause at "Jun 28 17:49:17" you manually stopped the service and tried to start it back... and it never worked
[19:47] <sarnold> so uh what changed between Jun 28 16:25:11 and Jun 28 17:49:17?
[19:48] <blackflow> sruli: btw, are there any errors showing up wrt resolving ntp.ubuntu.com domain for systemd-resolved service?  you tried ntpdate against an IP, but not against a pool name....
[19:49] <sdeziel> l4m8d4: I find timesyncd very well behaved as it doesn't try to concurrently manage my clock if I opt in for another NTP implementation :)
[19:49] <sruli> blackflow: just tried with poo.ntp.org worked
[19:49] <l4m8d4> Yeah, it is strange because 1) sometimes it timed out waiting for some servers, which I never experience and 2) in the end it doesn't seem to try to sync anymore
[19:50] <sdeziel> I still think it's not NTP related ;)
[19:50] <sdeziel> systemd complains that the daemon doesn't starts properly
[19:50] <sdeziel> and IIRC, timesyncd can cope with the inability to resolve DNS at startup
[19:51] <LaserAllan_> hey guys, just a stupid question, what package do I need to install php-fpm on ubuntu 1804?, I think i tried it sometime ago and it wanted ot install apache, which i don't really use
[19:51] <sruli> sarnold: it stopped working Jun 27 02:19:52, no clue what happend at that time
[19:52] <blackflow> LaserAllan_: incredibly, but....   php-fpm
[19:53] <blackflow> LaserAllan_: also note that php-fpm is orthogonal to apache. you can install nginx first and php-fpm wouldn't pull in apache.
[19:54] <LaserAllan_> blackflow: So tha tis why
[19:54] <LaserAllan_> Weird, i think i installed nginx first thought but i might be wrong :)
[19:54] <LaserAllan_> I will try that thank you
[19:55] <l4m8d4> sruli: I think it really started to break at Jun 28 17:50:48
[19:55] <blackflow> LaserAllan_: in fact, on Bionic it's now completely separate from httpd it seems. on 16.04 there use to be .... .issues.
[19:55] <l4m8d4> Before then it still tried to sync
[19:55] <l4m8d4> After that it just failed silently
[19:56] <blackflow> sruli: hey, you want good, stable, secure, no shenanigans, ntp client service?  try out openntpd! you won't regret it ;)
[19:56] <LaserAllan_> blackflow: Sounds good, I have been using quite allot of CentOS and FreeBSd before so this is kinda new to me. But I thought id give Ubuntu 1804 a spin now that my 1404 machine is very old and needs to slowly ie.
[19:56] <sruli> l4m8d4: lol thats when i started investigating why my time is wrong, and just tried to restart it
[19:57] <sdeziel> sruli: IIRC, at some point you edited it's conf file, no?
[19:57] <l4m8d4> sruli: You may want to adjust the systemd log level to get more details on this
[19:58] <sruli> sdeziel: yes i tried to change to pool.ntp.org, reverted later
[19:58] <sruli> l4m8d4: where do i change the log level for this?
[19:58] <LaserAllan_> l4m8d4: How do adjust the systemd log level? (just curious)
[19:58] <blackflow> or! or! here's a wild idea! install an ntpd developed by people who know what they're doing. :)  also, bonus https-based constraint check!
[20:00] <l4m8d4> sruli: systemd-analyze log-level
[20:00] <l4m8d4> Without parameter, it just gives you the current log level
[20:01] <l4m8d4> Otherwise you pass a log level, one of "emerg, alert,crit, err, warning, notice, info, debug"
[20:01] <l4m8d4> In this verbosity order I guess, where emerg is the least verbose, debug the most verbose
[20:03] <sdeziel> l4m8d4: thanks, I didn't know that one!
[20:03] <l4m8d4> blackflow: Still, it would be interesting to know why the problem occurs, don't you think?
[20:03] <ahasenack> hm, autopkgtest-build-lxd tries to install a kernel into the container :/
[20:03] <ahasenack> that just hangs here
[20:04] <blackflow> l4m8d4: after all these years, it's no longer interesting to me to find out its' because something something over dbus via xml :)
[20:07] <l4m8d4> Well, I think if possible you should always investigate why something doesn't work as intended on your system. In my case, I often find out interesting things in the process at least.
[20:09] <blackflow> l4m8d4: thats' true, but with systemd, in my experience, that has mostly been a carnival ride that burns you out.
[20:10] <blackflow> I've minimized that pain by using only the most minimum: init + process management, w/ journal (and only as a short in-memory buffer before syslog-ng).
[20:10] <blackflow> _that_ works quite well, indeed.
[20:10] <l4m8d4> blackflow: Then we have a different experience. For me, systemd has made managing the systemd a lot easier.
[20:10] <l4m8d4> blackflow: In that case, maybe you should consider going with a distribution that doesn't ship systemd by default, that might make you happy
[20:11] <blackflow> oh yes, no systemd is default in our shop. but sometimes, for some clients, you need to maintain systemd :)
[20:11] <l4m8d4> *managing the system, funny typo though
[20:14] <blackflow> the features and kernel capabilities (AND CAP capabilities) exposed through simple ini files really is awesome, yes. that part of systemd I like.
[20:15] <blackflow> but lets' be real. systemd-resolved? that thing has been nothing but a wild ride of vulns and half assed implementations. ubuntu 17.04 got burnt pretty good for defaulting to it.   systemd-timesyncd? also half-assed and vulnerable, and why on earth would I remove working quality ntpd clients that have worked well for years.
[20:16] <sruli> i rebooted and magically it works now
[20:16] <blackflow> until it breaks again. :)
[20:16] <sruli> blackflow: i know
[20:21] <blackflow> btw, systemd-timesyncd.service on Bionic.... there aren't ConditionFileIsExecutable  conditions defined by default?
[20:21] <blackflow> on debian they're in /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[20:23] <blackflow> how does that work then
[20:26] <l4m8d4> blackflow: I guess that the system will just call "systemctl stop systemd-timesyncd.service && systemctl disable systemd-timesyncd.service" if you install something else
[20:27] <blackflow> where's that trigger defined?
[20:29] <blackflow> sdeziel: "sruli: beware that timesyncd will back down if any other ntpd daemon is even present on the system"   -- how, on Bionic?
[20:32] <sdeziel> blackflow: I don't know, I just checked chrony's postinst and there is nothing in there
[20:33] <blackflow> I thought ubuntu wsa based on debian? :)
[20:33] <nacc> blackflow: what do you think "based on" means?
[20:33] <blackflow> on debian there's a nice list of ConditionFileIsExecutable   that prevents start up if the other daemons (virtualbox included) are present
[20:33] <blackflow> nacc: debs taken from debian unstable?
[20:34] <nacc> blackflow: at some point in time
[20:34] <blackflow> is there any other definition?
[20:34] <nacc> blackflow: is the debian changes more recent than bionic?
[20:34] <blackflow> nope
[20:34] <blackflow> it's actually years old
[20:34] <blackflow> in fact, I believe even Xenial had those, but I have no xenial systems now to check
[20:36] <nacc> blackflow: checking git
[20:36] <sdeziel> blackflow: yes, xenial has that disable-with-time-daemon.conf snippet
[20:36] <blackflow> so, huge regression on Bionic?
[20:36] <sarnold> https://patches.ubuntu.com/s/systemd/systemd_237-3ubuntu10.patch
[20:36] <sarnold> +  * Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf.
[20:36] <sarnold> +    All major NTP implementations ship a native service file nowadays with a
[20:37] <sarnold> +    Conflicts=systemd-timesyncd.service so this drop-in is no longer
[20:37] <sarnold> +    necessary. (Closes: #873185) (LP: #1721204)
[20:37] <nacc> sarnold: thanks
[20:37] <blackflow> I see.
[20:40] <l4m8d4> Yeah, I guess thats a more clean way of preventing conflicts there
[20:57] <blackflow> l4m8d4: yeah it's cleaner if individual packages conflicted on timesyncd, and packages amongthemselves are not installable together.
[20:58] <blackflow> the old method required one package to know all installable variants, hardcoded in teh config


[08:40] <ravage> https://www.youtube.com/watch?v=REdxblQpsDE missed chance for the IRC link in  the description again. but i really like the video :)
[08:40] <ravage> (was on vacation. discovered it today)
[20:39] <lotuspsychje> ravage: thats a pretty nifty ubuntu demo!
[21:07] <bwyazel> Yep it was fun being a part of the making of that video. Lots of thought went into each of the demos


[05:17] <pitti> Good morning
[05:32] <infinity> pitti: Just the man I've been waiting for.
[05:32] <pitti> hey infinity
[05:33] <infinity> pitti: We need adt-britney love for wily.
[05:33] <pitti> infinity: yep, jibel will set up the wily jobs this morning
[05:34] <pitti> I'll create VMs in the meantime (with the usual dist-upgrade hackery until we have daily cloud images)
[05:49] <pitti> wgrant, infinity: is the ddeb magic turned on in LP now?
[05:50] <pitti>  pkg-create-dbgsym | 0.65        | wily             | source, all
[05:50] <pitti> oops!
[05:50]  * pitti copies from vivid-updates
[05:55] <infinity> pitti: I'm not sure what the state of the magic is.
[05:59] <pitti> https://launchpad.net/ubuntu/+source/dfc/3.0.5-0.1/+build/7385174
[05:59] <pitti> that's a recent build
[05:59] <pitti> apparently it's on \o/
[06:03] <Unit193> You're going to want to talk to Debian about ddebs soon, I believe.
[06:07] <pitti> infinity: all the old stuff in vivid-proposed is going to be moved to wily, right? so that enabling -proposed stops being a potential disaster
[06:07] <pitti> wily-proposed, I mean
[06:08] <infinity> pitti: It's all moved as of about now.
[06:08] <infinity> pitti: Plus a publisher cycle.
[06:08] <pitti> yay, thanks
[06:09] <RAOF> Now's probably a reasonable time for some AA training...
[06:09] <infinity> RAOF: A few hours ago before I copied all of thise stuff by hand would have been a better time.
[06:09] <RAOF> infinity: Hah!
[06:10] <infinity> pitti: I *think* britney is ready to go, but hard to tell since it explodes with "OMG ADT NO WORKIE, POOF".
[06:11] <infinity> pitti: But, I'm working on the theory that once that's fixed, it'll Just Work.
[06:11] <wgrant> pitti: ddebs are enabled on most archives that matter, but I haven't done a recheck that I caught all of them.
[06:11] <wgrant> Will do so now.
[06:11] <pitti> wgrant: at least looks good for wily builds
[06:11] <pitti> wgrant: I copied the latest mangler now
[06:11] <infinity> Something's actually built in wily that created ddebs?
[06:11] <pitti> infinity: yes, e. g. https://launchpad.net/ubuntu/+source/dfc/3.0.5-0.1/+build/7385174
[06:11] <wgrant> pitti: Yeah, the primary archive, security PPAs and silos have all been enabled since Thur/Fri.
[06:12] <pitti> wgrant: I'll walk through https://launchpad.net/ubuntu/+source/dfc/3.0.5-0.1/+build/7385174 and see if any of the failures were due to the old mangler
[06:12] <pitti> wgrant: sorry, through https://launchpad.net/ubuntu/wily/+builds?build_text=&build_state=failed&arch_tag=all
[06:12] <infinity> Oh wow, that magically started building.  Huh.
[06:12] <infinity> Must have missed a mass give-back right before release. :/
[06:12] <infinity> Oh well.
[06:12] <wgrant> infinity: Copied to proposed.
[06:12] <wgrant> Oh, right, that's what you mean.
[06:17] <pitti> wgrant: ok, all the FTBFSes are not due to the old mangler, so all good
[06:32] <pitti> wily testbed VMs created in CI
[06:39] <pitti> infinity: https://launchpad.net/ubuntu/+source/jemalloc/3.6.0-3 looks like a leftover, ok to remove that from vivid-proposed?
[06:40] <pitti> or was that on purpose by any chance? (I suppose you moved over with a script, so odd that this one got stuck halfway)
[06:40] <infinity> pitti: Script.  Hah.  No, it was by hand, I just missed deleting that one.
[06:41] <pitti> infinity: well, script == for p in <packages>; do copy-package; remove-package; done
[06:41] <infinity> pitti: I should script it, but it needs to be smarter than "copy to x, delete from y" because LP treats with and without binaries differently depending on if there are completed builds or not.
[06:41] <infinity> pitti: Anyhow, deleting.
[06:41] <pitti> ah, ouch
[06:42] <pitti> infinity: ah, for built ones we need to copy the binaries, I see
[06:42] <infinity> pitti: We do, and you can't say "copy with binaries" for all of them, cause LP tosses a fit if there are no binaries. :P
[06:43] <infinity> Still, not that hard to script, just do the binary check first, I'm just allergic to the LP API, and doing it by hand gives me a chance to examine what's in proposed.
[07:50] <pitti> jibel, infinity: I'm not sure if the snakefruit setup is complete -- http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html still points to adt-vivid-* jobs, not adt-wily-* ?
[07:51] <infinity> pitti: It's not running, because it crashes when your end doesn't work. :P
[07:51] <infinity> pitti: Lemme try one by hand.
[07:51] <pitti> infinity: right, jibel is setting that up right now; he just wondered who set up britney, and I wondered if it needs more changes
[07:52] <infinity> pitti: I did, but it might not be completely right.  No idea.
[07:52] <pitti> infinity: nah, don't bother yet
[07:55] <jibel> pitti, infinity the CI infra doesn't know about wily yet, and I am not allowed to update the code on jenkins master
[07:56] <pitti> meh - CI vanguard o'clock?
[07:57] <jibel> someone's on it
[07:57] <LocutusOfBorg1> sil2100, was it ok to review? I don't remember
[07:57] <LocutusOfBorg1> oops s/ sil2100 / Unit193
[07:58] <sil2100> !
[07:58] <pete-woods> pitti: just nagging you about this MR again https://github.com/martinpitt/python-dbusmock/pull/9/files
[07:58] <pitti> pete-woods: ack, nag taken :)
[07:58] <pete-woods> :)
[08:08] <Laney> @pilot in
[08:09] <Laney> mdeslaur / arges: ↑ lies?
[09:29] <infinity> pitti: When the autopkgtest stuff is all working, can you let cjwatson know?  I'm handing off to him, since it's 3:30am here.
[09:29] <pitti> infinity: ack, will do
[09:29] <pitti> infinity: sleep well!
[09:30] <pitti> infinity: looks mostly ok now, just the queue is awfully long
[09:52] <Laney> jamespage: hiya, could you take a peek at bug #1374999 - nothing to sponsor currently, right? could unsubscribe ubuntu-sponsors then.
[09:53] <jamespage> Laney, agreed - I'll get tinoco to ping me directly once he has something ready - I need to coordinate that with other openstack updates anyway
[09:53] <jamespage> Laney, unsubbed sponsors
[09:53] <Laney> thanks!
[09:53]  * Laney is Purging Old Stuff
[09:56] <jamespage> Laney, nice one
[10:00] <LocutusOfBorg1> is the wily import started?
[10:01] <LocutusOfBorg1> I see something has been built for vivid
[10:01] <LocutusOfBorg1> s/vivid/wily
[10:02] <cjwatson> only sort of
[10:02] <cjwatson> please stop asking for the time being, we'll tell people when it starts
[10:05] <LocutusOfBorg1> thanks, sorry if I'm bothering, I asked many syncs from experimental, I would like to see if they are now sync'd from unstable again
[10:05] <pitti> LocutusOfBorg1: they will be
[10:06] <LocutusOfBorg1> thanks!
[10:54] <pitti> cjwatson, infinity: ah, distro-info bug fixed, and the queue is catching up -- first wily test results! http://d-jenkins.ubuntu-ci:8080/view/Wily/view/AutoPkgTest/
[10:56] <pitti> aptdaemon failure seems genuine, I figure some distro-info/python-apt/whatever needing an update for wily
[11:01] <mdeslaur> @pilot out
[11:01] <mdeslaur> Laney: thanks, forgot to check out apparently
[12:02] <tinoco> jamespage: hello james, freyes has taken this case. i remember my fix did not fix it entirely (at least for all cases, emc backend did work though)
[12:02] <tinoco> freyes: pls update james regarding the iscsi volume detach issue whenever you have something
[12:02] <tinoco> jamespage: thank you!
[12:47] <cjwatson> pitti: So I'm a little confused, do you know why http://people.canonical.com/~ubuntu-archive/proposed-migration/wily/update_excuses.html thinks aptdaemon passed?
[12:48] <cjwatson> oh, maybe that just needs to be rerun
[12:48] <pitti> jibel: ^ could it be that vivid's results.history was copied after that ran?
[12:48] <pitti> cjwatson: me too
[12:49] <cjwatson> I'll try rerunning p-m
[12:53] <cjwatson> 2015-05-05 12:52:54,113 DEBUG cmd: ['rsync', '-a', '--remove-source-files', 'rsync://tachash.ubuntu-ci/boottest/wily/out/', '/home/ubuntu-archive/proposed-migration/boottest/data/boottest/wily-proposed/krillin/work']
[12:53] <cjwatson> rsync: change_dir "/wily/out" (in boottest) failed: No such file or directory (2)
[12:53] <cjwatson> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1536) [Receiver=3.0.9]
[12:53] <cjwatson> pitti,jibel: ^- noticed by chance in p-m logs
[12:53] <pitti> oh, I specifically didn't change RELEASE= for boottest
[12:53] <jibel> psivaa, fginther ^
[12:53] <pitti> in lp:a-p-t
[12:54] <pitti> AFAIUI we do *not* want to move the phone to wily
[12:54] <pitti> but keep vivid, or vivid+PPA, or a vivid-based RTM release or something
[12:54] <pitti> so boottest should not run on wily, at least not right now
[12:54] <cjwatson> we don't want to move the phone to wily yet, but we also don't want to let the quality of wily drift
[12:54] <pitti> psivaa, fginther ^
[12:54] <cjwatson> (per slangasek)
[12:55] <pitti> ah, so will we have a channel for wily touch builds, but don't advertise it?
[12:55] <cjwatson> that was my understanding
[12:55] <cjwatson> ICBW
[12:58] <jibel> pitti, cjwatson a possible explanation is that aptdaemon/policykit passed in vivid, and the result is still valid in wily because policykit didn't retrigger a test of aptdaemon in wily ie policykit in wily didn't break aptdaemon.
[12:58] <pitti> ok; so I guess CI needs to create these dirs
[13:24] <fginther> pitti, jibel, I've created the rsync dirs on tachash for boottest. Will take a closer look at what boottest should really be testing in a moment
[13:38] <dholbach> slangasek, can you join #ubuntu-uds and #ubuntu-uds-core-1?
[13:39] <Laney> @pilot out
[13:40]  * dholbach hugs Laney and arges
[13:40] <arges> oops I forgot to pilot out : )
[13:41] <arges> @pilot out
[13:42]  * Laney hugs dholbach back
[13:45] <cjwatson> jibel: I guess that makes sense, but why did aptdaemon run in wily at all then?
[13:49] <slangasek> dholbach: done
[13:49] <dholbach> great
[13:53] <Orphis> Hey, does anybody know what's the progress of apt "by-hash" update status?
[13:54] <rbasak> "chdist create" for wily, when running on vivid, didn't seem to create or populate .chdist/.../etc/apt/trusted.gpg.d/ I get gpgv failure warnings. Is this a bug?
[13:54] <jibel> cjwatson, I don't know yet, 8 package tests have been triggered because packages were considered newer in wily, but the version is the same in vivid, and there is no new upload in wily
[13:54] <Orphis> And is there any plan on using it in future Ubuntu release?
[13:55] <rbasak> Orphis: I think support in apt will get synced this cycle. Then it needs to be enabled in the archive, and we need to switch to InRelease. I'm not sure about the status of those two parts. I think we're still planning on switching to it. mvo may know more but I don't see him online right now.
[13:55] <Orphis> rbasak: Do you know if apt-ftparchive supports generating repositories for this format?
[13:55] <rbasak> I don't think it does right now.
[13:56] <rbasak> I did have a script that takes a regular archive and adds the by-hash information.
[13:56] <rbasak> Not sure what happened to it.
[13:56] <Orphis> That's "easy" to add on top of existing index generation scripts though
[13:56] <rbasak> Right. The by-hash design allows for the extra stuff to be added to downstream mirrors even without upstream support.
[13:56] <cjwatson> We'd certainly want to support it in Launchpad, rather than messing about on mirrors.
[13:57] <Orphis> Is Launchpad the main ubuntu repository?
[13:57] <rbasak> Sure - it's easier to test by decoupling that though.
[13:57] <cjwatson> Orphis: Yes.
[13:57] <rbasak> (eg. on a local mirror)
[13:57] <cjwatson> Rather, Launchpad is the software that (among other things) publishes the repository.
[13:58] <Orphis> Mirrors will probably have to be smarter when mirroring, like handle packages first, then by-hash, then (In)Release(.gpg)
[13:58] <rbasak> "cp -a ~/.chdist/{vivid,wily}/etc/apt/trusted.gpg.d" fixed my chdist issue. Not sure if it's a bug in chdist or not.
[13:58] <cjwatson> Orphis: Mirrors already have to mirror pool then dists.
[13:59] <Orphis> Right, but they should still do a smart dists mirroring not to break everything :)
[13:59] <ev> can you statically link LGPL v2 code in a GPLv3 codebase?
[13:59] <cjwatson> I think they already have to do that too.
[13:59] <Orphis> Great
[13:59] <rbasak> Orphis: or, simplify the smarts to say "sync new files first, then modified files, then deleted files". Pool then dists would also work but best to sync deleted files last in that case.
[13:59] <Orphis> Do you know what software they're using?
[14:00] <rbasak> Oh, and InRelease last after everything else in dists.
[14:00] <Orphis> rbasak: That's a smarter way to do it too, yes
[14:00] <Orphis> Indeed
[14:00]  * zyga wonders what generates https://ftp-master.debian.org/new.html
[14:00] <zyga> and if there's an API for it
[14:01] <cjwatson> software> varies but we recommend https://wiki.ubuntu.com/Mirrors/Scripts
[14:01] <cjwatson> deletion isn't a big issue due to the stay of execution
[14:03] <Orphis> To serve the internal repository at my company, I have some software that is smart enough to keep a session based on the IP address of the client and keeps multiple versions of the index. When an update session starts (through Release.gpg or InRelease download), it tracks which index it should serve and avoids all issues. And on the other side, the index is updated automically using a smart symbolic link
[14:04] <cjwatson> yeah nobody wants to do that on public Ubuntu mirrors though :)
[14:04] <Orphis> It works great even for frequent updates of the repository and serves the right index, provided no 2 machines with the same IP are updating at the same time during an update
[14:04] <Orphis> Indeed
[14:04] <cjwatson> and anyway NAT
[14:04] <Orphis> I'm just looking for a solution that would work for my infrastructure to mirror your packages properly in different sites
[14:05] <Orphis> Yes, it's good for a private infra, not so much for external people, although that would reduce errors for people and shouldn't add more
[14:05] <Orphis> It's not 100% fail-safe and is transparent to old clients
[14:06] <Orphis> When it works, it works, when it doesn't, there would have been an error anyway without it
[14:07] <Orphis> How often is the ubuntu index regenerated? And how long does it usually take?
[14:07] <cjwatson> usually multiple times per hour
[14:07] <cjwatson> how long> depends exactly what you mean by that question ...
[14:08] <Orphis> How much time is spent between the moment you ask for the index to be built and it's actually done?
[14:09] <cjwatson> ev: yes, http://www.erisian.com.au/wordpress/2007/07/06/gplv3-and-debian has a summary
[14:11] <cjwatson> Orphis: (a) nobody asks for it explicitly (b) varies quite a bit depending on how much work it has to do; typical would be around 5-15 minutes
[14:11] <cjwatson> Orphis: that isn't relevant to mirrors though ...
[14:12] <cjwatson> I mean, frequency can be, but publisher runtime isn't
[14:12] <Orphis> No, but it's interesting to compare infrastructures of big repositories :)
[14:12] <cjwatson> right
[14:13] <Orphis> We have continuous deployment for some software, so we publish it in our repository and we block on the indexing. Having a fast indexing is always nice then
[14:13] <smoser> hey. bug 1446767
[14:13] <smoser> is in vivid-proposed.
[14:14] <smoser> is it acceptable to sign and upload 4.3.1-5ubuntu2.1  ? to wily ?
[14:14] <smoser> or.. how should that be done.
[14:14] <smoser> binary copy?
[14:15] <cjwatson> just copy with binaries to wily-proposed, if it isn't there already.
[14:16] <cjwatson> Orphis: small repositories there isn't really a good excuse for taking more than a small number of seconds :)
[14:16] <Orphis> cjwatson: Well, I have a big one!
[14:17] <Orphis> With multiple copies of some packages for gradual rollouts and stuff
[14:20] <Orphis> cjwatson: While you're around, something a bit related I couldn't get an answer for. Is trusty-updates a superset of trusty-security?
[14:20] <smoser> cjwatson, i don't do this very often.. can you confirm http://paste.ubuntu.com/10990160/ is right?
[14:21] <smoser> er.. do i coyp to wily-proposed
[14:22] <cjwatson> smoser: You should copy to wily-proposed, indeed.
[14:22] <cjwatson> smoser: Otherwise it's fine.
[14:22] <smoser> thanks
[14:23] <cjwatson> Orphis: More or less.  All updates to -security are automatically copied into -updates provided that they don't clash.
[14:24] <doko_> xnox, barry: isn't the python session now ongoing?
[14:24] <cjwatson> Orphis: There's a slight delay on that, and in any case -security still exists separately in part because that means we can point users' sources.list files at security.ubuntu.com for that suite, so that they get security updates quickly regardless of the vagaries of mirroring.
[14:24] <Orphis> cjwatson: So one should be safe enough to use only updates and not security, provided the updates repository is properly mirrored
[14:25] <cjwatson> Orphis: I can't recommend it, but I've explained the behaviour.
[14:25] <Orphis> Thank you
[14:25] <Orphis> Updates aren't applied automatically, so the slight delay is probably not relevant in that case
[14:25] <Orphis> Well, in *my* case
[14:25] <cjwatson> Probably not.
[14:27] <barry> doko: in 90m i think
[14:27] <xnox> doko: UTC time is 14:27
[14:28] <dholbach> doko, http://summit.ubuntu.com/uos-1505/2015-05-05/ - as barry said
[14:28] <doko> argh, won't be there then
[14:28] <xnox> doko: that's alright, it's not like we've been planning python3-only for a few years now....
[14:28] <ev> cjwatson: thanks!
[14:28] <barry> doko: darn.  can you pvtmsg me any links you want to share?  e.g. py3 work needing done?
[14:32] <xnox> where can i get recent go for 14.04 ?
[14:33] <doko> xnox, apt-get install gccgo
[14:34] <xnox> doko: what version of go does that translate to on 14.04?
[14:34] <doko> ahh, 14.04, the ubuntu-toolchain-r/test PPA
[14:34] <doko> 1.4.2
[14:35] <xnox> well i need at least 1.3 i think
[14:37] <xnox> hm i wonder if there is environment variable to do -compiler gccgo
[14:38] <doko> barry, xnox: for python3.5 in 15.10, somebody would need to sit down and see, if we have the resources to do 3.5 as supported version, or if it's too early (will be beta status at this time)
[14:38] <doko> xnox, GCCGO
[14:50] <cjwatson> pitti: do you know of any reason not to open at this point?  there's the lack of boottests, but I think we can live with that in the short term
[14:51] <pitti> cjwatson: fine from my POV;  if the toolchain (gcc 5?) is set?
[14:52] <cjwatson> apparently set, gcc 5 not default yet
[14:52] <cjwatson> (and not for opening)
[14:52] <cjwatson> I just want to get branch-distro sorted
[14:54] <pitti> cjwatson: do we have a newer distro-info and debootstrap already?
[14:54] <pitti> quite some stuff will fail without that, I figure
[14:54] <cjwatson> pitti: no, but be my guest
[14:54] <cjwatson> pitti: well, we do have a newer distro-info-data
[14:54] <pitti> cjwatson: ok; I have two UOS sessions now, noted for tomorrow morning
[14:54] <pitti> cjwatson: yes, that's what I meant
[14:54] <cjwatson> debootstrap isn't opening-critical
[14:54] <pitti> right, I locally added the symlink to the CI machines
[14:55] <pitti> they have wily containers now
[15:22] <rbasak> http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.vivid/rdepends/python2.7/ works but http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.vivid/rdepends/python2.7 redirects to http://people.canonical.com/germinate-output/ubuntu.vivid/rdepends/python2.7/ which then 404s (dropped off ~ubuntu-archive)
[15:22] <cjwatson> we'll start up auto-syncs soon
[15:22] <cjwatson> rbasak: sounds like a bug in the IS-managed proxy on lillypilly
[15:22] <rbasak> cjwatson: I'll file an RT then I guess? Thanks.
[15:22] <cjwatson> I think
[15:23] <cjwatson> it probably needs to rewrite the redirect or something
[15:29] <dholbach> woohooo!
[15:55] <pitti> cjwatson: \o/
[15:56] <pitti> cjwatson: https://launchpad.net/ubuntu/wily/+builds?build_text=&build_state=built&arch_tag=amd64 doesn't have builds with ddebs that are more than 30 mins old yes, but I'll check tomorrow that the ddeb import worked
[15:56] <pitti> cjwatson: at least they are being produced and published in LP now, so we won't lose them \o/
[16:00] <bdmurray> barry: where are we with the python-pip SRU?
[16:37] <smoser> anyone have thoughts on http://paste.ubuntu.com/10990807/
[16:37] <cjwatson> smoser: I'd strongly suggest talking with the Debian vim maintainers
[16:37] <cjwatson> they may have past experience
[16:38] <smoser> essentially replace python with python3 in vim. it doesn't actually build (a python3 test fails), but wonder if its the  right thing to do to replace Provides.
[16:38] <cjwatson> and Debian is targeting a pretty widespread switch to python3 for stretch so there's no good reason for this to be Ubuntu-specific
[16:38] <cjwatson> also, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729924
[16:38] <cjwatson> past history there you're skating over :)
[16:39] <smoser> cjwatson, thanks.
[16:47] <pitti> stgraber: lxc/wily failed because of debootstrap missing wily, I'll upload that
[16:48] <stgraber> pitti: yeah, I assumed it'd be something like that so I didn't even bother checking
[16:48] <stgraber> pitti: I usually start worrying about adt around a week after the series opened :)
[16:49] <pitti> cjwatson: uploaded debootstrap FTR
[16:50] <pitti> oh, Laney beat me to it
[16:50] <pitti> meh @ pull-lp-source not working yet
[16:50] <Laney> pow pow pow
[17:25] <zyga> barry: do you know, perhaps, what generates the debian NEW index? https://ftp-master.debian.org/new.html
[17:25] <zyga> barry: I wanted to write an app that loads the same data and presents it in a QML app
[18:00] <Laney> zyga: you could parse https://ftp-master.debian.org/new.822
[18:08] <zyga> Laney: fantastic, that's excactly what I wanted!
[19:47] <Noskcaj> How can i see what packages i have upload rights for?
[20:12] <bdmurray> seb128: In case you didn't notice the vivid line is fixed now.
[20:36] <seb128> bdmurray, did notice; thanks
[21:25] <utlemming> pitti, stgraber: which package provides the preseed files on the cdrom?


[04:10] <mup> Bug #1450296 was opened: Cannot remove if user maas does not exist <amd64> <apport-bug> <vivid> <maas (Ubuntu):New> <https://launchpad.net/bugs/1450296>
[12:14] <mup> Bug #1450450 was opened: 1.8b4 Cluster status can be changed <ui> <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1450450>
[12:23] <mup> Bug #1450450 changed: 1.8b4 Cluster status can be changed <ui> <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1450450>
[12:32] <mup> Bug #1450450 was opened: 1.8b4 Cluster status can be changed <ui> <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1450450>
[14:27] <mup> Bug #1450488 was opened: MAAS does not list all the tags <oil> <MAAS:New> <https://launchpad.net/bugs/1450488>
[20:01] <bmorriso> My first failed deployment with MAAS :( http://paste.ubuntu.com/10955562/
[20:22] <bmorriso> I have no idea where this command is getting ran from. I don't see this block in any curtin files