[00:00] <savvas> bug 340816 for python transition :)
[00:05] <_cooper_> Hi.
[00:05] <_cooper_> I'm about to generate an ubuntu package and found in the PackagingGuide how to name the package.
[00:05] <_cooper_> "If a Debian package has been changed in Ubuntu, it has ubuntuX (where X is the Ubuntu revision number) appended to the end of the Debian version. So if the Debian hello 2.1.1-1 package was changed by Ubuntu, the version string would be 2.1.1-1ubuntu1. If a package for the application does not exist in Debian, then the Debian revision is 0 (e.g., 2.1.1-0ubuntu1)."
[00:06] <_cooper_> The package I'm about to generate exists neither in Ubuntu nor in Debian.
[00:06] <_cooper_> Should I better generate a debian package first and then the one for Ubuntu?
[00:07] <cody-somerville> nhandler, I see your subscribed to gnome-scan (which should be gnomescan) on revu
[00:07] <_cooper_> Of course this would cause some delay.
[00:07] <savvas> _cooper_: it's probably better to include it in debian as well :)
[00:08] <nhandler> cody-somerville: I subscribe to all packages I comment on ;)
[00:08] <savvas> _cooper_: nothing stops you from trying in both "fronts" :)
[00:08] <_cooper_> savvas: That's what I'm planning to do.
[00:08] <_cooper_> Provide packages for both distros.
[00:08] <savvas> _cooper_: and when it is included in debian, you can bump the version from 2.1.1-0ubuntu1 to 2.1.1-1ubuntu1 :)
[00:09] <cody-somerville> nhandler, How was the package the last time you looked at it? I'
[00:09] <_cooper_> The quoted paragraph just made me think if I'm doing it in the wrong order.
[00:09] <cody-somerville> nhandler, I'd like to get gnomescan into jaunty
[00:09] <nhandler> cody-somerville: I honestly can't remember. I can take another look at it if you want
[00:09] <cody-somerville> nhandler, that would be great
[00:10] <savvas> _cooper_: just follow my suggestion, I think there won't be any problems! :) you can send your ubuntu version to be reviewed at http://revu.ubuntuwire.org
[00:10] <_cooper_> Ah. If this won't cause confusion, then I'll do both.
[00:10] <nhandler> cody-somerville: Isn't gnomescan already in the repositories?
[00:11] <cody-somerville> nhandler, it is, yup
[00:11] <nhandler> cody-somerville: So why are you going through REVU?
[00:11] <cody-somerville> nhandler, I'm not
[00:11] <cody-somerville> nhandler, someone else is
[00:11] <nhandler> Why?
[00:12] <cody-somerville> nhandler, "
[00:12] <cody-somerville> onkarshinde, this packaging is completely rewritten, just like the software itself, this is why i pass the process from the beginning. "
[00:12] <_cooper_> savvas: Thanks.
[00:12] <james_w> directhex: hey, were you Cced on the reject of monodevelop-debugger-gdb
[00:12] <james_w> ?
[00:12] <nhandler> cody-somerville: I guess that is what I get for not actually opening up the REVU page ;)
[00:12] <_cooper_> savvas: Any other hints saving me to be flamed all over when submitting my first package? #-)
[00:12] <directhex> no, i wasn't
[00:13] <directhex> unless it happened since i last ran my mail client
[00:13] <directhex> mmm, no, nothing here
[00:16] <persia> _cooper_, I'd recommend mostly focusing on the Debian route until after the Jaunty release.  Before then, few people are likely to review new packages targeting Ubuntu.
[00:16]  * ScottK seconds to _cooper_ what persia suggested.
[00:18]  * pochu seconds ScottK's second :)
[00:18] <savvas> _cooper_: yes, when using debuild to build the package or the source, read the lintian errors and try to google them :)
[00:20] <_cooper_> Good pont.
[00:20] <_cooper_> +i
[00:20] <cody-somerville> nhandler, do you want to take on getting gnomescan into jaunty? :)
[00:20] <cody-somerville> nhandler, it would be much appreciated.
[00:21] <_cooper_> due I'm using ubuntu on my laptop, I'm interested in an Ubuntu package myself to do some more longrun tests.
[00:22] <_cooper_> I think I'll do two packages and send them off when they're done.
[00:23] <james_w> directhex: I got a REJECT, but no accompanying explanation
[00:23] <nhandler> cody-somerville: I'm looking at it now. Is bersace still working on it?
[00:24] <cody-somerville> nhandler, He commented on a bug recently hoping it isn't too late for jaunty
[00:24] <directhex> james_w, and monodevelop-debugger-mdb?
[00:24] <james_w> directhex: -gdb
[00:25] <directhex> james_w, you're right - mdb passed NEW
[00:25] <nhandler> cody-somerville: Glad to hear that. I'll add a comment to the bug sometime tonight. If he keeps making the changes, I'll keep reviewing
[00:26] <cody-somerville> nhandler, awesome.
[00:28] <savvas> er..
[00:28] <savvas> gapti - do we need it?
[00:28] <savvas> its trunk wasn't updated since 2006: https://code.edge.launchpad.net/~gapti-dev/gapti/trunk
[00:28] <ScottK> savvas: Is it broken?
[00:29] <savvas> ScottK: it needs python transition, I think it's easy, but I also think that it's not maintained upstream
[00:29] <ScottK> If it's easy and not otherwise broken, then I'd transition it.
[00:29] <savvas> ah cool :)
[00:30] <persia> Might be worth checking with asac or mvo to see if it's part of the current ThirdPartyApt plan.
[00:31] <persia> If it's just duplicate to gdebi and friends, then dropping it might be useful, as it's Ubuntu-local.
[00:32] <savvas> never tried it, I'll give it a go :)
[00:34] <lfaraone> Hi, I'm seeing multiple additional LOAD_CYCLES on my laptop after about 2 minutes, should I be concerned?
[00:37] <savvas> wrong channel :p
[00:53] <binarymutant> opinion question: what would be faster, running my debian package through revu to update a package already in Jaunty or waiting for Debian's ftp-masters to move it out of the new queue?
[00:54] <_cooper_> Thanks for help, I think I'll return with some questions later...
[00:54] <ScottK> binarymutant: We're past Feature Freeze for Jaunty, so is this a bug fix only change?
[00:55] <binarymutant> ScottK, there aren't any bugs in the package but the one in Debian is much more "cleaner"
[00:55] <binarymutant> should I just leave it alone?
[00:56] <ScottK> So you got it into Ubuntu, then got an improved version into Debian that's still in New?
[00:56] <ScottK> binarymutant: ^^
[00:56] <binarymutant> ya
[00:56] <binarymutant> it conforms better to Debian's python-policy
[00:57] <ScottK> I'd file a bugg with a debdiff to a fixed version in it.  We generally only use REVU for new packages.
[00:57] <ScottK> Then subscribe ubuntu-universe-sponsors.
[00:57] <ScottK> Also make sure it works with Python 2.6 ....
[00:58] <binarymutant> I should send a post to ubuntu-universe-sponsors with a debdiff ?
[01:00] <binarymutant> cool thanks for the help, I found the wiki page for it
[05:09] <kostmo> Is there an official "metapackage" that includes all of the tools listed here: https://wiki.ubuntu.com/PackagingGuide/Complete#Packaging%20Tools
[05:09] <kostmo> ?
[05:11] <kostmo> I think it would be cool to have such a metapackage linked to from that wiki
[05:21] <JanC> kostmo: file a wishlist bug (of it doesn't exist yet) and maybe create it  ;-)
[05:21] <kostmo> sure, I'll look
[05:28] <savvas> bug 340901 for python transition :)
[05:29] <JanC> savvas: your debdiff is a bit ugly (seems like your editor changed a lot of "empty" lines)
[05:30] <savvas> JanC: + Replaced lines with spaces (\s+) with empty lines
[05:30] <savvas> :)
[05:31] <savvas> I said that since I'm fixing the source, I might as well fix most of it :P
[05:33] <savvas> JanC: here's the build in case you need it: http://launchpadlibrarian.net/23743844/buildlog_ubuntu-jaunty-i386.gapti_0.0.2ubuntu4_FULLYBUILT.txt.gz
[05:33] <JanC> I don't need it, I just think it's wrong to make such changes...
[05:35] <savvas> JanC: the upstream hasn't updated the trunk/main series since 2006
[05:37] <JanC> savvas: I think a patch to "fix" whitespace/empty-lines should be applied upstream (or in case upstream is dead, you could maybe fork it) and then pulled in in karmic koala
[05:37] <JanC> but that's just my "humble opinion"  ;)
[05:40] <fabrice_sp_> savvas, your changes makes a lot more complicated to review the changes. And I would say that to change the source, you should use a patch system, as it makes easier to identify where a change comes from
[05:40] <fabrice_sp_> but I'm not a MOTU, so I could be wrong
[05:41] <savvas> well.. if anyone wants to make them as patches, be my guest :)
[05:42] <fabrice_sp_> not the changes of spaces, for sure
[05:42] <fabrice_sp_> I already patched a lot of sources, and I always used a patch system
[05:43] <fabrice_sp_> anyway: you subscribed U-U-S, so let's wait for a MOTU to comment it
[05:44] <savvas> I've notified the original author about that bug as well
[05:44] <fabrice_sp_> about the spaces, you mean?
[05:44] <wgrant> savvas: You seem to have rewritten debian/rules, and made a whole lot excessive changes.
[05:44] <wgrant> It's unlikely that anybody will sponsor that.
[05:45] <savvas> but dh_python is deprecated as far as I could read
[05:46] <wgrant> Then you just remove it, without rewriting the build system and half of the upstream code.
[05:46] <savvas> oh well, the author might want to patch it upstream :)
[05:46] <wgrant> We prefer to keep the tiniest possible diff against Debian.
[05:46] <savvas> the upstream code had to be rewritten, it wasn't working otherwise
[05:47] <savvas> it's not a debian package: https://edge.launchpad.net/ubuntu/+source/gapti
[05:47] <wgrant> There are lots of spacing changes and importing things under different names, and using the print statement (which doesn't exist yet) and that sort of thing.
[05:47] <wgrant> The same applies to the diff between as and upstream.
[05:48] <wgrant> As much as it can be nice to play upstream sometimes, we are not upstream for gapti.
[05:49] <wgrant> And doing this will ensure that merging the next upstream release is very, very difficult.
[05:50] <savvas> I suppose you're all right
[05:51] <savvas> wgrant: can you unsubscribe u-u-s until I sort this out?
[05:51] <wgrant> savvas: I'm not in u-u-s, I'm afraid.
[05:52] <savvas> darn :\ well, I'll just put a comment to disregard that patch
[05:54] <wgrant> savvas: Given the sad state of the old debian/rules, and the lack of the package in Debian, you can (and probably should) replace it.
[05:55] <wgrant> I'm surprised it has gone so long without python-(support|central)... we were meant to get rid of them all years ago.
[05:56] <savvas> well I asked if it should be dropped from ubuntu, the general reply was "if you want to patch it, do it" - I guess they meant without so many changes :)
[05:57] <savvas> wgrant: but either way, I could do a patch without the empty spaces changes, but it still needs to be tampered with upstream code change, some modules have changed unfortunately
[05:58] <JanC> wgrant: I think you mean the print function instead of th print statement?
[05:59] <JanC> wgrant: I think that's not really an issue (although not needed yet) as it will work even in older python versions (normally)
[05:59] <wgrant> JanC: That is of course what I meant.
[06:00] <wgrant> But it's an unnecessary change, as it's not required yet, so we shouldn'
[06:00] <wgrant> ... shouldn't do it.
[06:00] <JanC> OTOH, no need for it in jaunty yet, and an upstream change would be more useful indeed
[06:00] <wgrant> savvas: Most of the files don't require any changes.
[06:00]  * wgrant -> gone.
[06:04] <savvas> eh, it was good for practise at least
[06:05] <JanC> ツ
[06:10] <fabrice_sp_> Does anybody knows if we should repack upstream tarball if it's a bz2 instead of a gz?
[06:11] <savvas> I think that you can use bunzip2 for that fabrice_sp_ - and gzip to make a tar.gz :)
[06:14] <fabrice_sp_> savvas, I was already repacking the tarball, as upstream was including debian directory, but with the new version, it's not the case anymore, so I wanted to get rid of that 'repacking'. Will play with watch options... thanks anyway!
[06:21] <savvas> fabrice_sp: you're using watch to update it? you could try debian uupdate with watch, I think it automatically transforms tar.bz2 to tar.gz if I'm not wrong :P
[06:22] <fabrice_sp> savvas, yes: a watch file, with uscan in a get-orig-source in debian/rules
[06:22] <fabrice_sp> there is an option to uscan --repack that does the job ;-)
[06:22] <savvas> ah yeah :)
[06:34] <persia> fabrice_sp, When using uscan --repack, please create a get-orig-source to do that anyway, and document it as a repack in debian/README.source.  The md5sum won't match, so without the documentation, someone may feel impelled to investigate.
[06:35] <fabrice_sp> persia, ok. I'll update the README.debian to explain that. Thanks for the info!
[06:35] <persia> Please don't.
[06:36] <persia> README.Debian is intended to be packaging-specific end-user documentation.  It should be used when the behaviour of the packaged software differs from the upstream behaviour.
[06:36] <persia> debain/README.source is the appropriate place to put packaging-specific developer documentation, when it is useful to document what one has done for fellow developers.
[06:38]  * persia hopes the timing isn't such that that was missed
[06:38] <fabrice_sp> persia, I meant README.source. Sorry for the mistake
[06:38] <fabrice_sp> README.source is the file I was editing
[06:39] <persia> Excellent :)
[06:39] <fabrice_sp> :-)
[06:41] <JanC> hm, I'm currently looking at a package coming from Debian without changes which doesn't have README.source like that despite being repackaged (AFAICS)   ;)
[06:41] <fabrice_sp> Have to go now. Bye!
[06:42] <persia> JanC, If it claims Standards-Version: 3.8.0, that's a bug.  If it claims a lower standards version, it just needs to be updated.
[06:43] <JanC> it does say 3.8.0
[06:43] <JanC> I'll contact the people involved as I know them
[06:43] <persia> Double-check by reading debian-policy 3.8.0, but I believe that's a bug.
[06:44] <persia> On the other hand, debian/README.source might still be optional with <IP_ADDRESS> (I forget precisely).
[06:44] <JanC> BTW: why should a bz2 source be repacked?
[06:44]  * JanC is a new at this
[06:45] <savvas> I think the debian packaging system needs an orig.tar.gz file
[06:45] <JanC> I wish all upstreams & distros would use lzma to minimize bandwidth  ;)
[06:47] <savvas> I heard about a different system with patches for updates
[06:47] <savvas> delta packages ? or something like that
[06:48] <JanC> savvas: that's for binary packages
[06:49] <JanC> and fedora & opensuse are already using something like that AFAIK
[06:50] <persia> There's ongoing work on the various archive software and build tools to use alternate compression mechanisms, but nothing widely adopted yet.
[06:51] <savvas> ah :)
[07:05] <savvas> hm.. I think I have a minimalistic patch now :P
[07:05] <savvas> http://paste.ubuntu.com/129654/
[07:06] <dholbach> good morning
[07:06] <savvas> good morning dholbach :)
[07:06] <dholbach> hiya savvas
[07:32] <savvas> dholbach: you think the patch is good? :P
[07:32] <dholbach> savvas: I think you put quite some work into it - as others said already: it's a good idea to get upstream to accept it and then make use of it, so we don't have to maintain a huge delta
[07:33] <dholbach> savvas: I think you're doing great work
[07:33] <dholbach> my motu-release friends: what do you think about bug 340008?
[07:33] <savvas> ah ok :)
[07:33] <savvas> thanks!
[07:34] <dholbach> ROCK ON! :)
[07:34] <savvas> I've send an email to wasabi, Jerome Haltom - https://edge.launchpad.net/gapti
[07:34] <dholbach> ahhh ok, didn't know he's maintaining it
[07:34] <savvas> maybe I should send that patch as a bzr merge
[07:35] <savvas> he's not, the trunk wasn't touched since 2006 :P
[07:35] <savvas> but with a great message: "* Cleaned up and made first upload.* Cleaned up and made first upload.* Cleaned up and made first upload.* Cleaned up and made first upload.* Cleaned up and made first upload.* Cleaned up and made first upload.* Cleaned up and made first upload.* Cleaned up and made first upload.* Cleaned up and made first upload."
[07:35] <savvas> hehehe
[07:36] <savvas> anyway, I'll wait for wasabi to respond, then see what to do :)
[08:48] <directhex> james_w, any luck seeing why -gdb was rejected?
[08:49] <Toadstool> good morning!
[08:50] <savvas> does anyone know what does "-include" do in a makefile? is it like a comment "#include" ?
[08:53] <liw> savvas, it changes how make reacts if the included file does not exist
[08:54] <liw> savvas, install make-doc, and run "info doc" and type control-s and then "-include" (without the quotes) for the full story
[08:54] <savvas> ah cool
[08:54] <savvas> thanks liw :)
[09:03] <bersace_nerim> nhandler: hi
[09:23] <savvas> I think gdesklets needs just a rebuild, bug 336200 - someone should double check though, I always tend to make mistakes :)
[09:25]  * savvas bbl
[11:18] <blizzkid> lo all. I've a bit of a nasty issue with ipod-convenience in jaunty alpha 5:
[11:18] <blizzkid> ipod-convenience: Depends: python-gpod but it is not going to be installed
[11:19] <blizzkid> python-gpod: Depends: python (< 2.6) but 2.6.1-0ubuntu1 is to be installed
[11:19] <DktrKranz> blizzkid: python-gpod has to be rebuilt against python 2.6
[11:20] <blizzkid> DktrKranz: so, basically I download the source of python-gpod and build it myself?
[11:20] <DktrKranz> blizzkid: basically that's what needs to be done
[11:21] <DktrKranz> we do exactly that in the buildds
[11:21] <gaspa> dholbach: DktrKranz wants to invite you at our meeting... :P do you want to have a trip in italy, this month?
[11:21] <hggdh> blizzkid, you can. apt-get source python-gpod, and go from there. Of course, this will solve your immediate issue, but not the general one -- unless you open a bug on it.
[11:21] <gaspa> DktrKranz: right? :)
[11:21] <DktrKranz> yup!
[11:22] <blizzkid> ok DktrKranz, is there a _good_ howto on how to start with src and build a .deb out of what I created? If I build it, I can as well build a .deb from it...
[11:22] <blizzkid> hggdh: I could maybe build a deb, and attach that to the bug report? ;)
[11:23] <hggdh> blizzkid, a debdiff would be better, or even just a diff
[11:23] <blizzkid> hggdh: if you can point me to a howto on creating a (deb)diff, I'll gladly try to provide one :)
[11:23] <dholbach> gaspa: when? I'm going to be quite busy
[11:24] <hggdh> blizzkid, see (for starters) https://wiki.ubuntu.com/PackagingGuide/Maintenance
[11:24] <DktrKranz> blizzkid: you can look at pbuilderhowto in the wiki, or better wait for a proper fix (it won't take too long)
[11:24] <dholbach> but trip to Italy sounds great... in general :)
[11:24] <gaspa> dholbach: :) 28th of march, the end of this month
[11:25] <DktrKranz> dholbach: we're going to make it a cross-meeting, we plan to invite some DDs to work together with them, so both distros can receive attention :)
[11:25] <dholbach> sounds great, not sure if I'll be able to attend though
[11:25] <blizzkid> k, I'll have a look hggdh and DktrKranz thx
[11:26] <DktrKranz> blizzkid: I can't promise anything right now, but I will be able to look at it in the next few days for an official fix
[11:26] <dholbach> DktrKranz, gaspa: Ma io non parlano italiano!
[11:26] <gaspa> dholbach: well, we'll be pleased, but of course do as you can. :)
[11:26] <gaspa> LOL
[11:26] <gaspa> "parlo"
[11:27] <DktrKranz> dholbach: it's not a problem, we have google translate in place :)
[11:27] <dholbach> DktrKranz: guess what I used ;-)
[11:27] <blizzkid> that would be cool DktrKranz
[11:28] <blizzkid> btw, let me take this opportunity to thank all motu's for the great work. Been using Ubuntu since it appeared, and still loving it
[11:28] <DktrKranz> gaspa: we need to setup a simultaneous translation for dholbach, what about totopalma? :)
[11:28] <gaspa> DktrKranz: totopalma would be great!
[11:28] <gaspa> :D
[11:28] <dholbach> totowhat?
[11:28]  * DktrKranz moves to lunch now
[11:30] <gaspa> dholbach: our trustworthy translator
[11:30] <dholbach> ahh ok
[11:31] <dholbach> DktrKranz: Bon appetit!
[11:41] <nhandler> dholbach: How soon are you planning on starting those packaging lessons?
[11:44] <dholbach> nhandler: I was thinking of waiting a bit to get more input and leave a bit of time until everybody read the proposal, then mail all the people who are interested to start planning
[11:44] <dholbach> nhandler: what do you think?
[11:45] <nhandler> dholbach: Sounds fine by me. Just be sure to give the people interested in leading a session enough time to prepare
[11:45] <dholbach> nhandler: sure... thanks a lot for volunteering already!
[11:45] <nhandler> :)
[11:46] <dholbach> nhandler: as long as we don't have too high expectations on what people should deliver there and we're very inviting, we should be fine :)
[11:49] <nhandler> dholbach: I think these will be a big success. Some will have more audience participation than others, but I think many people are interested in learning about packaging
[11:50] <dholbach> yeah, I hope so :)
[11:56] <blizzkid> hmmz, I installed libgdk-pixbuf2 and libgdk-pixbuf-dev, but when running configure I get "checking for GDKPIXBUF... no". Am I missing something here?
[12:16] <lfaraone> What's the chance I could get this in jaunty+1? http://www.vergenet.net/~conrad/scripts/pants.html
[12:17] <ScottK> lfaraone: Almost none.
[12:17] <ScottK> lfaraone: Package it for Karmic and then have a backport.
[12:20] <ia> hello. could you tell me, please, after i've done with building packages, is it safely to remove /var/cache/pbuilder/build/* dirs?
[12:20] <lfaraone> ScottK: that's *exactly* what I said, I was talking about getting it into karmic. jaunty + 1 == karmic :)
[12:20] <lfaraone> ia: I'd assume so.
[12:20] <ScottK> lfaraone: Ah.  I missed the +1.  Sorry.
[12:22] <lfaraone> ScottK: I was refering to whether the package would be rejected for serving no useful purpose. (akin to "sl")
[12:30] <ScottK> lfaraone: It's a game.  I think games are fine.
[13:03] <ChrisBuchholz> Hi, I'm all new to packaging and whatever term you can mention, but I would like to learn how I can pack an app and send it off to a repo and whatever is between that. Can you guide me in the right directions with some references or something?
[13:06] <soren> ChrisBuchholz: I believe https://wiki.ubuntu.com/UbuntuDevelopment is the canonical starting point.
[13:07] <soren> ChrisBuchholz: there's also #ubuntu-nordic-dev if you'd rather discuss in Danish/Swedish/Norwegian.
[13:08] <soren> ...or Finnish/Icelandic, I suppose, but I don't think you'll get a lot of response that way :)
[13:14] <ChrisBuchholz> Many thanks, Soren, I'll give it a shot, bye;)
[13:30] <soren> persia, geser: I won't be able to attend the MC call today. Due to premature DST in the US, I have a conflict.
[13:33] <ripps> Does anybody know where I can get some documentation on the Gnome dbus multimedia keys framework?
[13:51] <dholbach> ripps: tried asking in #ubuntu-desktop?
[14:24] <slytherin> persia: any idea what all changes are needed to visualvm packaging to compile it against latest netbeans packages?
[14:28] <persia> slytherin, None at all, I'm afraid.
[14:29] <slytherin> It is not a simple rebuild that is for sure. I tried some packaging changes the other day but was stuck and I have limited knowledge about visualvm
[14:30] <persia> From the limited information I received, I think visualvm was one of the reasons that libnb-platform was versioned at a source level.
[15:03] <bddebian> Heya gang
[15:04] <geser> Hi bddebian
[15:04] <bddebian> Heya geser
[15:07] <savvas> geser: hi, could you check bug 336200 when you find some spare time? I'm almost certain that it just needs a rebuild :)
[15:08] <savvas> this is the pbuilder log of gdesklets_0.36-5 (the already existing version): http://launchpadlibrarian.net/23747311/last_operation.log
[15:10] <ScottK> savvas: What are you expecting geser to do that you can't/haven't already done yourself?
[15:10] <savvas> ah so it's done?
[15:11] <savvas> Well I thought I need a second opinion just to be sure I am correct :)
[15:11] <ScottK> OK.  Fair enough
[15:11] <savvas> sorry to poke around :)
[15:16] <savvas> hm...
[15:16] <savvas> it seems to depend on python 2.4 still
[15:18] <savvas> ScottK: is there an environment variable I can set to use a specific python version?
[15:18] <savvas> or anyone?
[15:19] <geser> savvas: specify it at the shebang of the script
[15:21] <savvas> I'll try that
[15:21] <savvas> thanks
[15:23] <savvas> hmm Could not import tiling module!
[15:24] <savvas> /usr/lib/gdesklets/utils/tiling.la
[15:24]  * savvas looks at the source code
[16:11] <savvas> er..
[16:11] <savvas> after reading http://bugs.archlinux.org/task/12217 and a bunch of other sites, the error I get seems to be fixed in gdesklets 0.36.1
[16:14] <savvas> I'll file a bug
[16:51] <savvas> nope, the debian version isn't working either heh
[16:56] <rulus> Hello, I'm trying to package a daemon. It provides an initscript which should go in /etc/init.d/. The problem is that dpkg thinks this script is a configfile, so it doesn't get removed unless --purged. Is this normal behaviour and how to get passed it? Is there a good (easy) example of a packaged daemon?
[16:57] <TheMuso> rulus: THats what happens normally, any package tat has an initscript doesn't have the script remove unless the package is purged.
[16:58] <rulus> ah ok, so nothing to worry about then :)
[16:58] <savvas> true, it's in /etc/ :)
[16:58] <TheMuso> rulus: no
[16:58] <rulus> thanks!
[16:59] <TheMuso> rulus: WHich is why you will see many initscripts depending on the binaries they need to function before they actually do anything.
[16:59] <TheMuso> rulus: s/depending on/checking for/
[17:00] <rulus> TheMuso: ok, seems a good thing to do indeed
[17:06] <cristi> i am not so familiar with python, so how do i know what changes should be done for the python transition again?
[17:06] <cristi> the 2.6 transition
[17:46] <cristi> i only modified something in the control of a package, and run dch -i. however debdiff says debdiff: fatal error at line 266: Can't read file: ../espeak_1.32-0ubuntu1.dsc . What is the problem? i am just a beginner
[18:01] <cristi> come on? can't anyone give me a hand?
[18:02] <ScottK> cristi: What did you feed debdiff?
[18:02] <cristi> ScottKi run it in the file with /debian
[18:02] <cristi> the problem is that it asks for espeak 1.32 and i have 1.36 as a .dsc
[18:05] <ScottK> Generally it works best if you debdiff libmail-dkim-perl_0.32-1.dsc libmail-dkim-perl_0.33-1.dsc (for example) when both files are in the current dir.
[18:06] <cristi> ScottK: what are the 2 debdiff parameters? the i didn't see that in the wiki
[18:06] <ScottK> It's the .dsc for the two package revisions your are trying to diff.
[18:07] <ScottK> If you look at man debdiff you'll see there's lots of ways to do it, but that's what I always use.
[18:07] <cristi> ScottK: the second .diff is done by debuild ?
[18:08] <ScottK> Yes.  Debuild -S -us -uc your knew revision first.
[18:08] <ScottK> Then you'll have a .dsc in the parent dir for the new revision.
[18:16] <cristi> ScottK: yes, thank you, it worked, but i don't know how the first debuild didn't create the right .dsc
[18:17] <ScottK> cristi: Then look at the top entry in debian/changelog and make sure it refers to the correct version.
[18:17] <cristi> ScottK however, is there any point in submitting a debdiff to this bug ? https://bugs.launchpad.net/debian/+source/espeak/+bug/250860
[18:18] <cristi> i guess not, but at least i am starting to get used with the tools
[18:19] <ScottK> cristi: That one is already fixed in Ubuntu anyway.
[18:22] <cristi> ScottK: how do i know what changes should be done to the python packages for the python transition again? sorry for bugging you with this :-s
[18:22] <ScottK> cristi: At this point just playing with the tools is good.  It's a strong learning curve at the beginning.
[18:22] <ScottK> Didn't we go over this yesterday?
[18:22] <ScottK> If your IRC client doesn't log there is irclogs.ubuntu.com.
[18:23] <ScottK> I'll be glad to answer specific questions, but don't have time today to redo the tutorial.
[18:23] <cristi> ScottK ok
[18:30] <savvas> cristi: hi :)
[18:32] <cristi> savvas: hey there
[18:36] <savvas> Would you prefer to make a patch for a Makefile that uses python setup.py or just include the commands in debian/rules ?
[18:37] <cristi> savvas: if i see setup.py in the package, but however it is not mentioned in rules, i don't have to change anything?
[18:38] <savvas> cristi: if it's mentioned in the install rule, I think you have to add a parameter --install-layout=deb
[18:39] <cristi> savvas: yes, but i don't see it in install rule
[18:39] <savvas> cristi: paste the debian/rules
[18:40] <cristi> savvas: http://pastebin.com/maf3a3de
[18:42] <savvas> cristi: I don't know about that one :\ I've never seen one like it so far!
[18:42] <savvas> it seems it uses configure.py
[18:42] <cristi> savvas: i'll just leave rules untouched
[18:42] <cristi> ?
[18:43] <savvas> cristi: well, try, but if you see your files installed in /usr/local/... then something is wrong ;)
[18:43] <savvas> when the binary package is built, check it: dpkg-deb -c yourfile.deb
[18:43] <savvas> it shows the contents of the package
[18:44] <cristi> ok
[18:46] <porthose> when preparing an FFe would PPA build logs be sufficient?
[18:59] <savvas> ScottK: I forgot got to thank you about pbuilder-dist recommendation, it's great, thanks! :)
[18:59] <ScottK> savvas: YW.  Thank RainCT as he wrote it.
[19:00] <savvas> RainCT: thanks for the pbuilder-dist script, very useful hehe, saves me a lot of keystrokes :)
[19:01] <cristi> savvas: i don't see it anywhere it /usr/local/
[19:01] <savvas> cristi: it's built in: cd $HOME/pbuilder/jaunty_result
[19:01] <savvas> and you do: dpkg-deb -c *.deb
[19:02] <cristi> savvas: i used pbuilder-dist jaunty login
[19:02] <cristi> savvas: that's no good?
[19:02] <RainCT> savvas: great, I'm happy that you like it :)
[19:02] <RainCT> ls
[19:02] <savvas> cristi: type: cd $HOME/pbuilder/jaunty_result
[19:03] <savvas> cristi: and then: dir
[19:03] <savvas> do you see any .deb files?
[19:03] <cristi> savvas: bash: cd: /home/cristi/pbuilder/jaunty_result: No such file or directory
[19:03] <cristi> lol
[19:06] <savvas> cristi: ls ~/pbuilder
[19:07] <savvas> cristi: I think you can figure it out, find a *result* folder inside ~/pbuilder :)
[19:07] <savvas> cristi: nautilus ~/pbuilder
[19:07] <savvas> :P
[19:08] <savvas> use cd to get into that folder
[19:08] <savvas> and then when you see .deb files: dpkg-deb -c *.deb
[19:08] <cristi> savvas: ok, thanks
[19:09] <ScottK> savvas: Do you know about debc?
[19:09] <cristi> savvas: i see only for pystatgrab
[19:09] <cristi> savvas: i was working on pyqwt
[19:11] <savvas> debc?
[19:11] <savvas> ScottK: what's that? :)
[19:11] <savvas> cristi: paste the output of the dpkg-deb -c *.deb command at pastebin :)
[19:11] <savvas> cristi:  ah wait
[19:12] <savvas> cristi: you mean you don't see your package?
[19:12] <cristi> savvas: yes..
[19:12] <ScottK> savvas: It's a decent utility for doing what you're after here.
[19:12] <savvas> then it's probably not built correctly
[19:12] <ScottK> debc the binary.changes file.
[19:12] <savvas> were there any errors in the log of pbuilder?
[19:13] <cristi> dh_install: python-qwt5-qt3 missing files (usr/lib/python*/Qwt5/*), aborting
[19:13] <cristi> make: *** [binary-arch] Error 1
[19:13] <cristi> savvas:it's because of one of the .install files i edited i guess
[19:13] <savvas> cristi: paste the whole output so we can see where the problem is :)
[19:13] <savvas> ScottK: thanks! I'll check/try it out once we get it built hehe :)
[19:14] <cristi> savvas: it was larger than my scroll. should i rebuild with a bigger scroll, or the one i have will do?
[19:16] <cristi> savvas: http://pastebin.com/m7d5d0c61 this is what i have
[19:16] <savvas> cristi: the latest log file is saved somewhere in the ~/pbuilder folder :)
[19:16] <savvas> mine is last_operation.log
[19:17] <savvas> cristi: paste debian/control too
[19:17] <cristi> savvas: the error comes from a .install file. you sure you want debian/control?
[19:18] <savvas> cristi: which package you said it was?
[19:18] <cristi> pyqwt
 i modified usr/lib/python*/site-packages/Qwt5/* to usr/lib/python*/Qwt5/*
[19:21] <savvas> use this: usr/lib/python*/*-packages/Qwt5/*
[19:22] <savvas> site-packages is used for python versions 2.5 (or less up to some point :P)
[19:22] <savvas> dist-packages is used by 2.6
[19:22] <savvas> so *-packages grabs both :)
[19:23] <cristi> savvas: i see, i wish i had more general knowledge about this matter
[19:23] <cristi> modifief usr/lib/python*/site-packages/PyQt4/Qwt5/* to usr/lib/python*/PyQt4/Qwt5/* is ok?
[19:24] <cristi> or like this usr/lib/python*/-packages/PyQt4/Qwt5/*
[19:25] <maxb> You're still missing a *
[19:25] <cristi> usr/lib/python*/*-packages/PyQt4/Qwt5/*
[19:26] <cristi> maxb: is this ok?
[19:26] <maxb> Assuming you've just changed "site" to "*", yes
[19:26] <cristi> maxb: thank you
[19:29] <savvas> cristi: all in time, I didn't know about this either a week ago :)
[19:31]  * quadrispro working at Python 2.6 transition
[19:34] <ScottK> apt-cache rdepends python2.5|grep -c "  "
[19:35] <ScottK> = 119
[19:35] <ScottK> Plenty more to do
[19:36] <cristi> that's kind of good news for me, i have to get used with editing packages
[19:37] <mrooney> ScottK: and those are just the packages that explicitly list their < 2.6 dependency :)
[19:47] <maxb> And then there's the packages which install, but spew DeprecationWarnings :-)
[19:56] <savvas> man, when dpatch is in build-depends it should fail to allow direct patches :P
[19:57] <maxb> lintian will whine already :-)
[19:58] <savvas> it does, but I just found a package with 3 files edited directly with dpatch installed :)
[20:45] <ScottK> savvas: Were the direct edits done in Debian or Ubuntu?
[21:12] <cristi> does this lintian error pose any problems ? bad-ubuntu-distribution-in-changes-file jaunty
[21:13] <nhandler> cristi: No, you can ignore that. It just has to do with the version of lintian you have
[21:13] <ScottK> cristi: No.  It just means you might want a newer lintian.  There is one that know about Jaunty in hardy-backports.
[21:13] <cristi> nhandler ScottK: thank you
[21:15] <cody-somerville> ScottK, I'd like to extend the Xubuntu delegation to include mr_pouit
[21:15] <cody-somerville> (for FFe's)
[21:15] <ScottK> cody-somerville: Personally I'm fine with that, but we need to get concurrence from MOTU release more generally.
[21:16] <ScottK> cody-somerville: Would you write an email to all of us cc the MOTU ml?
[21:16] <cody-somerville> Can I just send it to the motu ml instead of tracking down e-mail addresses for all the release members? :P
[21:16] <ScottK> I suppose that's fine.
[21:16]  * cody-somerville assumes motu-release is subscribed to -motu ml
[21:17] <ScottK> Although if you look at the MC list today there's a mail to all of us right there.
[21:18] <nhandler> cody-somerville: You can also use the Contact this Team feature on Launchpad
[21:18] <cody-somerville> Not to be difficult but I believe the motu mailing list is the best place for this
[21:18] <cody-somerville> and if motu-release members aren't subscribed to that mail list, they shouldn't be in that team
[21:20] <cristi> can anyone take a look at this pbuilder build output and tell me if there is anything wrong with it? i see some warnings about the changelog are those important?
[21:20] <cristi> http://paste.ubuntu.com/129934/
[21:20] <iulian> nhandler: Doing that will send a mail to all members from ~ubuntu-release as well.
[21:21] <nhandler> iulian: True. I forgot that they were part of motu-release on LP. However, sending to the MOTU mailing list would also result in all of these people getting an email ;)
[21:21] <iulian> nhandler: Indeed.
[21:22] <nhandler> cody-somerville: Do whatever you want. As long as I get the email, I am fine
[21:23] <ScottK> cristi: Yes, you need to worry about those.
[21:24] <ScottK> cristi: Would you pastebin your debian/changelog
[21:24] <cristi> ScottK http://paste.ubuntu.com/129935/
[21:25] <cristi> ScottK too many characters/line? tabs not allowed? what's wrong with it
[21:25] <ScottK> Don't use tabs.  Use spaces.
[21:26] <ScottK> Debian/changelog is supposed to be machine parseable, so the formatting is pretty fiddly.
[21:26] <cristi> ScottK should i edit only changelog or the changelog.dch and rerun debuild ?
[21:26] <ScottK> Just edit it and then rerun debuild.
[21:28] <iulian> And don't mention in the changelog that you modified the Maintainer field.
[21:28] <iulian> cristi: ^
[21:29] <cristi> iulian: argh damn it now i have to do it again xD
[21:31] <cody-somerville> ScottK, nhandler, etc. sent
[21:31] <cristi> ScottK since the changelog warnings were the only errors is it necessary to rebuild?
[21:31] <vollepulle1_> ioioio
[21:31] <cody-somerville> oh crap
[21:31] <vollepulle1_> hallo
[21:31] <cody-somerville> I sent using the wrong e-mail address
[21:31] <cody-somerville> Anyone here a moderator for the motu ml?
[21:32] <ScottK> cristi: If you update your ubuntu-dev-tools from hardy-backports I think update-maintainer won't add that anymore.
[21:41] <cristi> this is the output of pbuilder build http://pastebin.com/m531d706a i'm a bit confused about what am i suppose to do with it. Last time there was a bug whici i reported. now i only get some warnings. Can anyone tell me what should i do when i reach this point: the output of pbuilder build?
[21:43] <maxb> cristi: As in, you have a change, and you want to request that it be uploaded? Then https://wiki.ubuntu.com/SponsorshipProcess
[21:44] <cristi> maxb: thanks!
[22:02] <cristi> maxb: so i simply attach the debdiff to a bug report?
[22:03] <maxb> that's what the wiki page says...
[22:09] <cristi> so, it's like this https://bugs.launchpad.net/ubuntu/+source/sonata/+bug/341409
[22:12] <cristi> thank you for the help, bye
[22:48] <amikrop> Greetings.
[22:48] <amikrop> Canonical, or even better, The Linux Foundation, should seriously collaborate with major software vendors like EA sports, Blizzard or Adobe.
[22:48] <amikrop> It's unacceptable to be unable to use very popular and useful applications.
[22:49] <lucas> (lol)
[22:50] <directhex> amikrop, typically those companies won't get out of bed for less than 7 figures
[22:50] <broonie> amikrop: It's mostly up to them seeing enough market to make it worth their while to support Linux; there has been commercial binary only software for Linux since forever (see some of the stuff in the partners repo for example)
[22:50] <broonie> But in any case, you probably want to find a more relevant channel.
[22:51] <amikrop> broonie: commercial binary only? Does Football Manager have linux binaries? What about Warcraft? What about almost *any* widespread game?
[22:51] <amikrop> directhex: excuse me, I didn't quite understand that
[22:52] <directhex> amikrop, most commercial app vendors won't commit a single resource to a linux port of something without being paid in advance for it.
[22:52] <directhex> see also: valve's demands to apple for mac half-life
[22:53] <amikrop> OK. The Linux Foundation, or linux and specific distro sponsors should pay.
[22:53] <amikrop> In advance.
[22:53] <ajmitch> amikrop: I trust you'll be donating then
[22:53] <amikrop> ajmitch: No.
[22:53] <broonie> amikrop: Oracle and stuff; in terms of games iD software have done Linux builds since Doom and I actually have copies of some of the Civ games for Linux.
[22:54] <directhex> broonie, loki went bust!
[22:54] <amikrop> It's really sad, anyway. You have to use Windows, which is tragically crap, in order to have access to major software applications and games. That has to dramatically change. Very soon.
[22:55] <broonie> directhex: I know; tends to suggest that the folks who say there's no market have a point :)
[22:55] <directhex> amikrop, i'm aware of the situation, i'm still on the front page of google if you look for "linux gaming"< 5 years after writing an article
[22:55]  * ajmitch is wondering what the MOTUs are expected to do about this dire catastrophe
[22:55] <directhex> broonie, there's a limited market. question of deciding size of fish for size of pond.
[22:56] <directhex> ajmitch, port gears of war please, kkthx. no source, but disassemblers are great, i hear
[22:56] <ajmitch> directhex: mmk, I'll get right on it
[22:56] <directhex> ta
[22:57] <ajmitch> I won't port world of warcraft, because that'll just cause everyone to stop developing & start playing WoW
[22:57] <broonie> directhex: Don't be stuipid, we just need a full speed XBox emulator.
[22:57] <amikrop> directhex: I see.
[22:57] <directhex> broonie, and moar mhz
[22:57] <broonie> I'll come round and paint go faster stripes on your CPU, will that work?
[22:58] <directhex> amikrop, to some extent, you're right. but the financials are not promising. especially in the current climate, and given the people being talked about
[22:58] <amikrop> directhex: Which article of them is yours, by the way?
[22:58] <directhex> amikrop, the one on hexus.net
[23:00] <directhex> amikrop, you're right that more games would be great. but the financials right now aren't great for a very large percentage of titles. indie titles get done (e.g. world of goo recently), or games with highly cross-platform engines & a need for friendly sysadmins to run servers (e.g. id software).
[23:02] <andresmujica> Hi MOTUs!
[23:02] <andresmujica> i wonder if someone can help me with this bug #317860
[23:03] <andresmujica> the lastest 3g profiles reported at launchpad and all around are at upstream SVN, a quick update to the package would be great for Jaunty a6
[23:03] <amikrop> directhex: Aha. Well, let's hope something will make the big difference and things will change. :-)
[23:04] <directhex> amikrop, short version: moar users. you could help andresmujica, i'm sure that's worth a couple of users
[23:05] <amikrop> directhex: help him with what?
[23:08] <andresmujica> amikrop: 317960
[23:08] <andresmujica> bug
[23:08] <andresmujica> bug #317860
[23:22] <dtchen> DktrKranz: WRT #339541, does `sudo /etc/init.d/alsa-utils reset' resolve the issue?
[23:26] <amikrop> andresmujica: And how is that bug related to our conversation?
[23:31] <DktrKranz> dtchen: no, I still can hear sound from left speaker only
[23:33] <dtchen> DktrKranz: ok, if you have a moment, i'll continue the debugging
[23:33] <DktrKranz> dtchen, sure, thanks for your interest in it :)
[23:34] <dtchen> DktrKranz: first thing is to `sudo fuser -k /dev/dsp* /dev/snd/*'
[23:34] <DktrKranz> /dev/snd/controlC0:   3611
[23:34] <dtchen> DktrKranz: then, sudo cp /var/lib/alsa/asound.state /var/lib/alsa/asound.state.orig
[23:35] <dtchen> DktrKranz: sorry, s/cp/mv/
[23:35] <DktrKranz> done
[23:35] <dtchen> DktrKranz: next, sudo modprobe -r snd_via82xx
[23:36] <DktrKranz> done with a warning: "WARNING: All config files need .conf: /etc/modprobe.d/alsa-base-blacklist, it will be ignored in a future release."
[23:36] <dtchen> DktrKranz: ok, if you can reboot, please reboot.
[23:36] <DktrKranz> ok, back in a while
[23:37] <dtchen> the codec needs at least a re-init
[23:40] <DktrKranz> dtchen, rebooted, but with no improvements
[23:40] <dtchen> DktrKranz: and you did use mv and not cp, correct?
[23:40] <DktrKranz> yes
[23:41] <dtchen> ok, thanks. i'll look into it further.
[23:41] <DktrKranz> thank *you* :)


[15:51] <blackboxsw> holmanb: falcojr upstream 23.3 is good for review and includes ec2/mantic integration test fixes
[15:51] <blackboxsw> https://github.com/canonical/cloud-init/pull/4388
[15:51] -ubottu:#cloud-init- Pull 4388 in canonical/cloud-init "Release 23.3" [Open]
[18:21] <blackboxsw> [community notice] Release of cloud-init 23.3 published. Thanks again for all the hard work!!! https://github.com/canonical/cloud-init/releases/tag/23.3
[18:25] <minimal> great news
[18:39] <blackboxsw> falcojr: holmanb https://github.com/canonical/cloud-init/pull/4391 for upload to Ubuntu mantic development release
[18:39] -ubottu:#cloud-init- Pull 4391 in canonical/cloud-init "Ubuntu/devel" [Open]
[20:01] <meena> I need to submit an update for the ports
[20:01] <meena> and a report
[20:08] <inflatador> qq re: network-config. Is the "id0 match:" stuff in the docs expected to work for all Linux OS, or just Ubuntu? I'm having issues on Debian and just wanted to rule out the obvious.
[20:09] <inflatador> network-config file here: https://paste.opendev.org/show/821328/
[22:46] <minimal> inflatador: from the docs https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.ht
[22:46] <minimal> oop,s https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.html#common-properties-for-physical-device-types
[22:46] <minimal> "Note that currently only networkd supports globbing, NetworkManager does not."
[22:50] <minimal> meena: was chatting to someone in another channel who is trying to get c-i working with OpenBSD and hit some issues
[22:50] <meena> minimal: oy
[22:51] <meena> i have neglected OpenBSD quite a bit, since it's not really a daily environment for me.
[22:51] <meena> what problems where they having?
[22:51] <minimal> meena: the current one they're seeing (now that they're trying 23.3) is that, unlike for freebsd, there is not specific netbsd or openbsd code for running "dhclient" and so options are being used that are not supported by OpenBSD dhclient
[22:52] <minimal> unlike FreeBSD's dhclient apparently OpenBSD's does not support either "-l" or "-p" (and also doesn't support "-1" that __init__.py tries)
[22:54] <meena> good grief, how do they have an even older code base than we do??
[22:54] <meena> ours is from like 1997
[22:55] <minimal> I#m just going from https://man.openbsd.org/dhclient.8
[22:55] <minimal> the point is currently FreeBSD dhclient is handled by freebsd.py, for netbsd and openbsd it is not
[22:55] <minimal> and the "standard" option of "-1" is not recognised by OpenBSD
[22:56] <meena> aye
[22:56] <meena> i don't even see a dhclient man page for netbsd.
[22:56] <minimal> haven't checked that, was only helping them with openbsd
[22:56] <meena> aye.
[22:57] <meena> can they open a bug, and I'll take a look at this tomorrow, when I'm not a meter and a half in nroff and virtio code?
[22:58] <minimal> they had earlier problems (i.e. iproute being used) until they moved to 23.3 so obviously those were addressed by your recent changes
[22:58] <meena> (btw, i was gonna steal some baseline virtio documentation from NetBSD or OpenBSD, but it turns out, they have as much virtio documentation as FreeBSD)
[22:59] <meena> minimal: i really didn't think that there could be an Operating system out there with an older dhclient codebase, with even less options with FreeBSD, so I didn't even bother checking.
[23:00] <minimal> they're hoping to work on cloud-init packaging for OpenBSD
[23:01] <minimal> I've pinged them to open a github issue but they're "idle" currently
[23:07] <meena> minimal: they could also join this channel…
[23:08] <meena> anyway, i think i'm giving up on documentation for tonight, and will try again tomorrow. brain is not cooperating.
[23:08] <minimal> yes ~I was going to suggest that once they're no longer idle


[14:50] <zohan> night all
[19:58] <pitti> kees, mdz, soren, stgraber, cjwatson: anyone here for TB meeting? (US holiday, etc.)
[19:59] <cjwatson> I believe I'm no longer on the TB so wasn't planning to attend ...
[20:00] <pitti> right
[20:00] <soren> I'm here.
[20:00] <stgraber> I'm around but not really on the TB at this point :)
[20:00] <soren> ..but also wasn't really sure about the state of things.
[20:00] <cjwatson> well, I mean, I'm not even standing
[20:01] <stgraber> I don't think there's much we can discuss or do until sabdfl gets things to move forward...
[20:02] <pitti> the only thing that I see is "SRU Request for Heat and Ceilometer", which we can also do by mail
[20:02] <pitti> I won't mind skipping this meeting and doing the sleep thing instead :)
[20:02] <soren> pitti: Didn't sabdfl +1 that already anyway?
[20:03] <pitti> not sure how serious that was, but it seemed rather straightforward anyway
[20:03] <pitti> I'm still interested in kees' MRE review, if/once it actually happens
[20:03] <stgraber> there's really no point in having a meeting since we're not technically on the board anyway... the only thing we can do at this point is wait for (and nag) sabdfl so we can have a TB again ASAP
[20:03] <pitti> ack
[20:04] <pitti> I'll try to catch him tomorrow on IRC
[20:04] <pitti> seems mail doesn't quite help
[20:04] <pitti> so, good night everyone!
[20:04] <stgraber> good night!
[20:05] <soren> o/


[16:30] <Guest76874> hi
[16:32] <AlanBell> hi Guest76874
[16:32] <Guest76874> i have two problems in ubuntu 12.04
[16:33] <Guest76874> can u help me?
[16:33] <IdleOne> #ubuntu can help you
[16:33] <holstein> Guest76874: for support? you should try /join #ubuntu
[16:33] <holstein> Guest76874: lots of volunteers there ready to help :)
[16:36] <Guest76874> so can i describe my problems?
[16:37] <genii-around> Not in here.
[16:37] <Pici> Guest76874: You are in #ubuntu-ops, you need to ask in #ubuntu
[16:37] <IdleOne> Guest76874: This channel is not for ubuntu support
[16:37] <holstein> Guest76874: sure, in #ubuntu you can describe them and a volunteer will help :)
[16:37] <Guest76874> ok
[16:37] <Guest76874> thanks
[16:38] <IdleOne> Please remember to /part this channel
[16:51] <Myrtti> Guest76874: hi
[16:52] <Guest76874> hello
[16:52] <Myrtti> Guest76874: you're being helped in #ubuntu?
[16:52] <Guest76874> yes
[16:53] <Myrtti> please leave this channel then.


[00:54] <Eickmeyer> OvenWerks: I went ahead and did a thing: https://launchpad.net/carla
[00:56] <OvenWerks> Eickmeyer: cool. So is it going to stay yours or should it belong to ubuntustudio-dev?
[00:57] <Eickmeyer> I can make it ubuntustudio-dev.
[00:57] <Eickmeyer> Done.
[00:57] <OvenWerks> as you wish one way or the other, it just means that if you get tired of it you can have someone else take over.
[00:57] <Eickmeyer> Yep, true.
[01:47] <Eickmeyer> OvenWerks: And now, it's in our autobuilds.
[02:18] <OvenWerks> Eickmeyer: I will see about adding a man page. Are we changing the source directly or using a .debian diff thing?
[07:41] <sakrecoer> hi!
[07:42] <sakrecoer> i'm pretty sure i added you tiÃ³ the core team Eickmeyer, so you should be able to do everything you need to. I didn't make you owner striahgt away, waiting for returns from the mailing list.
[07:43] <sakrecoer> Eickmeyer: if you need me to talk to someone, just tell me who and i'll do it in an acceptable span of time.
[07:44] <sakrecoer> regarding the website backend, i'v never had other access to it than the WP-admin thingy. for anything else, there is this ticket service... i don't have the URL at hand but that's where you file tickets for the WP backend.
[07:45] <sakrecoer> Eickmeyer: you are part of the core-team, show this to the people you discuss with if they doubt your clearance.
[07:46] <sakrecoer> to be honnest, i was also handed the keys a bit like "voila"... and i know it's hard to get in some places. but i suppose i'm happy about that: i would not feel comfy about this thing if it was easy.
[07:47] <sakrecoer> either way, send me an email with whatever it is you want me to do to facilitate transition.
[07:47] <sakrecoer> I'll be on holliday during all of july so at that point i'll be able to respond very quickly
[08:01] <sakrecoer> ok, i had failed to give you admin persmission Eickmeyer
[08:01] <sakrecoer> i fixed it. PLease don't hesitate to write me personally if you need this kindof assitance. :) <3
[08:03] <sakrecoer> i'm rarley reading anything public-forum lately, for personal reasons.
[08:05] <sakrecoer> Eickmeyer: found the URL in my brain somehwere under a rock: https://rt.ubuntu.com/
[08:05] <sakrecoer> this is where you file tickets for the website.
[08:07] <sakrecoer> my experience shows that being very polite and mindfull is the best way to get things done quickly. Although, for the WP theme thing, last time we tried to adress it, it ended up in a loop of "fix this so we can fix this". which ultimately led to abandon
[08:12] <sakrecoer> for reference, here is the thread: https://rt.ubuntu.com/Ticket/Display.html?id=29028
[08:13] <sakrecoer> hope that helps. And again: do not hesitate to email me to my personal mail if you have any need of assitance. :)
[08:15] <sakrecoer> Happy Tuesday y'all!
[16:05] <Eickmeyer> OvenWerks: I've been pulling from the main Github, making changes, then pushing to our repo. So pull from falktx, push to our repo. I can pull from our repo if you make any changes.
[16:07] <OvenWerks> so it effectively becomes a fork rather than just a package?
[16:17] <Eickmeyer> Not exactly. More of a branch and rejoin. Git is smart enough not to pull in anything that overwrites what I have done locally.
[16:18] <Eickmeyer> It treats anything I pull-in from github as a merge.